OptiX RTN 950 Maintenance Guide (V100R006)

OptiX RTN 950 Radio Transmission System
V100R006C10
Maintenance Guide
Issue 01
Date 2013-12-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. 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
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2013-12-15) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX RTN 950 V100R006C10
iManager U2000 V200R001C00

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 Network planning engineer
l Data configuration engineer
l 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.
Maintenance Guide About This Document
ii
Symbol Description

Indicates a hazard with a medium or low level
of risk, which if not avoided, could result in
minor or moderate injury.

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 Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in
boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New 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.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
iii
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
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.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface 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 01 (2013-12-15) Based on Product Version V100R006C10
This document is the first issue of the V100R006C10 product version.
iv
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 Network Monitoring...................................................................................................................29
4.1 Checking the NE Status................................................................................................................................................30
4.2 Checking the Board Status...........................................................................................................................................31
4.3 Alarm and Performance Data Query............................................................................................................................32
4.3.1 Browsing Current Alarms..........................................................................................................................................32
4.3.2 Browsing Historical Alarms......................................................................................................................................37
4.3.3 Browsing Current Performance Events.....................................................................................................................40
Maintenance Guide Contents
v
4.3.4 Browsing Historical Performance Events..................................................................................................................42
4.3.5 Browsing the Performance Event Threshold-Crossing Records...............................................................................43
4.3.6 Browsing UAT Events...............................................................................................................................................45
4.4 Microwave Link Performance Query...........................................................................................................................46
4.4.1 Querying the Historical Transmit Power and Receive Power...................................................................................46
4.4.2 Querying the SNR Values of a Radio Link...............................................................................................................47
4.4.3 Browsing Current Performance Events of the radio link...........................................................................................48
4.4.4 Browsing Historical Performance Data of a Radio Link...........................................................................................50
4.5 Ethernet Performance Query........................................................................................................................................51
4.5.1 Browsing Current Ethernet Performance..................................................................................................................51
4.5.2 Configuring Ethernet Performance Threshold-Crossing Parameters........................................................................55
4.5.3 Setting Parameters for Monitoring Historical Ethernet Performance........................................................................58
4.5.4 Browsing Historical Ethernet Performance Data......................................................................................................59
4.6 Ethernet Port Traffic Monitoring..................................................................................................................................62
4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports....................................................62
4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization............................................................................63
4.7 Long-term Network Performance Monitoring.............................................................................................................65
4.7.1 Creating a Performance Monitoring Template..........................................................................................................65
4.7.2 Creating a Performance Monitoring Instance............................................................................................................67
4.7.3 Browsing the Real-Time Data of a Performance Monitoring Instance.....................................................................71
4.7.4 Browsing the Historical Data of a Performance Monitoring Instance......................................................................72
4.8 Report Query................................................................................................................................................................73
4.8.1 Querying the Microwave Link Information Report...................................................................................................73
4.8.2 Querying the Network-wide License Report.............................................................................................................74
4.8.3 Querying the Microwave Configuration Report........................................................................................................76
4.8.4 Querying the Board Information Report...................................................................................................................77
4.8.5 Querying the Board Manufacturing Information Report...........................................................................................80
4.8.6 Querying the ODU Information Report.....................................................................................................................81
4.9 Alarm and Performance Management Setting..............................................................................................................82
4.9.1 Configuring the Performance Monitoring Status of NEs..........................................................................................82
4.9.2 Setting Severity and Auto Reporting Status of Alarms.............................................................................................83
4.9.3 Suppressing Alarms for Monitored Objects..............................................................................................................84
4.9.4 Suppressing Alarms for NEs.....................................................................................................................................85
4.9.5 Reversing Alarms for Service Ports..........................................................................................................................86
4.9.6 Setting Trigger Conditions of AIS Insertion.............................................................................................................87
4.9.7 Setting Trigger Conditions of UNEQ Insertion.........................................................................................................87
4.9.8 Setting Bit Error Thresholds for Service Ports..........................................................................................................88
4.9.9 Setting Monitoring and Auto-Report Status of Performance Events........................................................................89
4.9.10 Setting Performance Thresholds..............................................................................................................................90
4.9.11 Resetting Performance Registers.............................................................................................................................90
5 Troubleshooting..........................................................................................................................92
vi
5.1 General Troubleshooting Procedure.............................................................................................................................94
5.2 Troubleshooting Service Interruptions.........................................................................................................................96
5.3 Troubleshooting the Radio Link.................................................................................................................................103
5.4 Troubleshooting Bit Errors in TDM Services............................................................................................................110
5.5 Troubleshooting Pointer Justifications.......................................................................................................................115
5.6 Troubleshooting the Interconnection with SDH Equipment......................................................................................119
5.7 Troubleshooting the Interconnection with PDH Equipment......................................................................................123
5.8 Troubleshooting Native Ethernet Service Faults........................................................................................................126
5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane....................................................................................134
5.10 Troubleshooting MPLS Tunnels..............................................................................................................................140
5.11 Troubleshooting CES Services.................................................................................................................................144
5.12 Troubleshooting ATM Services...............................................................................................................................149
5.13 Troubleshooting Ethernet Services Carried by PWs................................................................................................153
5.14 Troubleshooting L3VPN Services............................................................................................................................160
5.15 Troubleshooting DCN Faults....................................................................................................................................163
5.16 Troubleshooting Orderwire Faults............................................................................................................................168
5.17 Typical Cases............................................................................................................................................................170
5.17.1 Transient Link Unavailability Due to Multi-path Fading......................................................................................170
5.17.2 Transoceanic Link Transient Unavailability Due to Insufficient Height Difference between Diversity Antennas
..........................................................................................................................................................................................172
5.17.3 Link Unavailability Due to Inter-building Reflection...........................................................................................173
5.17.4 Unidirectional Link Availability Due to Interference...........................................................................................174
5.17.5 Bit Errors on Microwave Links.............................................................................................................................175
5.17.6 Poor Reliability Due to Network Planning Errors.................................................................................................176
6 Part Replacement.......................................................................................................................178
6.1 Removing a Board......................................................................................................................................................180
6.2 Inserting a Board........................................................................................................................................................183
6.3 Replacing the SDH Optical Interface Board..............................................................................................................185
6.4 Replacing the Channelized STM-1 Processing Board...............................................................................................186
6.5 Replacing the PDH Interface Board...........................................................................................................................187
6.6 Replacing the Smart E1 Interface Board....................................................................................................................188
6.7 Replacing the Ethernet Interface Board......................................................................................................................189
6.8 Replacing the IF Board...............................................................................................................................................190
6.9 Replacing the CF Card...............................................................................................................................................192
6.10 Replacing the System Control, Switching and Timing Board..................................................................................193
6.11 Replacing the Auxiliary Board.................................................................................................................................198
6.12 Replacing the Fan Board..........................................................................................................................................198
6.13 Replacing the Power Board......................................................................................................................................200
6.14 Replacing the SFP....................................................................................................................................................202
6.15 Replacing the ODU..................................................................................................................................................203
6.16 Replacing the IF Cable.............................................................................................................................................205
vii
6.17 Erasing Data in the Repair Parts...............................................................................................................................206
6.17.1 Board Storage Media.............................................................................................................................................206
6.17.2 Removing the CF Card..........................................................................................................................................207
6.17.3 Formatting the Flash Memory...............................................................................................................................208
7 Database Backup and Restoration.........................................................................................210
7.1 NE Database...............................................................................................................................................................211
7.2 Backing Up the Database Manually...........................................................................................................................212
7.3 Setting the Database Backup Policy...........................................................................................................................214
7.3.1 Setting the User-Defined Backup Policy.................................................................................................................214
7.3.2 Enable the Backup Policy of the Device.................................................................................................................216
7.3.3 Disable the Backup Policy of the Device................................................................................................................217
7.4 Restoring the Database by NMS................................................................................................................................218
7.5 Recovering Databases from a USB Flash Drive........................................................................................................221
8 Common Maintenance Operations........................................................................................224
8.1 Microwave Link Troubleshooting..............................................................................................................................226
8.1.1 Monitoring Radio Link Indicators...........................................................................................................................226
8.1.2 Scanning Interfering Signals...................................................................................................................................227
8.1.3 Muting/Unmuting an ODU......................................................................................................................................228
8.1.4 Performing a PRBS Test for the IF Board...............................................................................................................229
8.2 Ethernet Service Troubleshooting..............................................................................................................................232
8.2.1 Querying the Attributes of an Ethernet Port............................................................................................................232
8.2.2 Searching for Service Paths Based on VLANs.......................................................................................................233
8.2.3 Searching for Service Paths Based on MAC Addresses..........................................................................................235
8.2.4 Checking the Layer 2 Protocols Used by Ethernet Services...................................................................................236
8.2.5 Performing Intelligent Service Fault Diagnosis for Ethernet Services....................................................................237
8.2.6 Performing E-LAN Service Loopback Detection....................................................................................................239
8.2.7 Monitoring Ethernet Service Performance and Traffic Volume Based on Service Paths.......................................240
8.2.8 Querying Ethernet Service QoS Configurations Based on Service Paths...............................................................242
8.2.9 Monitoring Ethernet Packets Through Port Mirroring............................................................................................244
8.2.10 Using the Ethernet Test Frames.............................................................................................................................246
8.2.11 Checking L3VPN Service Performance Using NQA............................................................................................248
8.3 TDM/CES Service Troubleshooting..........................................................................................................................255
8.3.1 Setting the On/Off State of the Laser......................................................................................................................255
8.3.2 Setting the ALS Function........................................................................................................................................256
8.3.3 Performing a PRBS Test for the Smart E1 Processing Board.................................................................................257
8.3.4 Performing a PRBS Test for the Tributary Board...................................................................................................260
8.3.5 Querying the Impedance of an E1 Channel.............................................................................................................263
8.4 Software Loopback.....................................................................................................................................................264
8.4.1 Setting Loopback for the SDH Optical Interface Board..........................................................................................264
8.4.2 Setting Loopback for the Channelized STM-1 Processing Board...........................................................................266
8.4.3 Setting Loopback for the Tributary Board..............................................................................................................268
viii
8.4.4 Setting a Loopback for the Smart E1 Processing Board.........................................................................................269
8.4.5 Setting a Loopback for the Packet-plane Ethernet Interface Board........................................................................271
8.4.6 Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board...............................................................273
8.4.7 Setting Loopback for the IF Board..........................................................................................................................275
8.4.8 Setting Software Loopback for the NE....................................................................................................................278
8.4.9 Setting Software Loopback for the Microwave Link..............................................................................................280
8.4.10 Locating a Fault by Performing Loopback Operations.........................................................................................280
8.5 Hardware Loopback...................................................................................................................................................282
8.6 Reset...........................................................................................................................................................................282
8.6.1 Cold Reset................................................................................................................................................................282
8.6.2 Warm Reset.............................................................................................................................................................283
8.7 Setting the Automatic Release Function....................................................................................................................284
8.8 Querying Power Consumption of Boards...................................................................................................................284
8.9 Switching the System Control Unit and the Cross-Connect Unit..............................................................................285
8.10 Cleaning Fiber Connectors and Adapters.................................................................................................................286
8.10.1 Cleaning Fiber Connectors by Using Cartridge Cleaners.....................................................................................286
8.10.2 Cleaning Fiber Connectors by Using Lens Tissue................................................................................................288
8.10.3 Cleaning Fiber Adapters by Using Optical Cleaning Sticks.................................................................................289
A Alarm Reference.......................................................................................................................291
A.1 Alarm List (in Alphabetical Order)...........................................................................................................................292
A.2 Alarm List (Classified by Logical Boards)................................................................................................................309
A.2.1 AUX........................................................................................................................................................................310
A.2.2 CQ1.........................................................................................................................................................................311
A.2.3 CSH.........................................................................................................................................................................312
A.2.4 CSHU/CSHUA.......................................................................................................................................................314
A.2.5 CST.........................................................................................................................................................................316
A.2.6 EFP8.......................................................................................................................................................................317
A.2.7 EG4.........................................................................................................................................................................317
A.2.8 EG4P.......................................................................................................................................................................318
A.2.9 EM6T......................................................................................................................................................................318
A.2.10 EM6TA.................................................................................................................................................................319
A.2.11 EM6F....................................................................................................................................................................319
A.2.12 EM6FA.................................................................................................................................................................320
A.2.13 EMS6....................................................................................................................................................................320
A.2.14 FAN......................................................................................................................................................................321
A.2.15 IF1.........................................................................................................................................................................321
A.2.16 IFU2......................................................................................................................................................................322
A.2.17 IFX2......................................................................................................................................................................322
A.2.18 ISU2......................................................................................................................................................................323
A.2.19 ISV3......................................................................................................................................................................324
A.2.20 ISX2......................................................................................................................................................................325
ix
A.2.21 ML1/MD1.............................................................................................................................................................326
A.2.22 ODU......................................................................................................................................................................326
A.2.23 PIU........................................................................................................................................................................326
A.2.24 PMU......................................................................................................................................................................327
A.2.25 SL1D/SL1DA.......................................................................................................................................................327
A.2.26 SP3S/SP3D...........................................................................................................................................................327
A.2.27 TCU......................................................................................................................................................................328
A.3 Alarms and Handling Procedures..............................................................................................................................328
A.3.1 A_LOC...................................................................................................................................................................328
A.3.2 ACR_LOCK_FAIL................................................................................................................................................329
A.3.3 ALM_E1RAI..........................................................................................................................................................330
A.3.4 ALM_GFP_dCSF...................................................................................................................................................331
A.3.5 ALM_GFP_dLFD...................................................................................................................................................332
A.3.6 ALM_IMA_LIF......................................................................................................................................................333
A.3.7 ALM_IMA_LODS.................................................................................................................................................335
A.3.8 ALM_IMA_RE_RX_UNUSABLE........................................................................................................................336
A.3.9 ALM_IMA_RE_TX_UNUSABLE........................................................................................................................337
A.3.10 ALM_IMA_RFI...................................................................................................................................................339
A.3.11 AM_DOWNSHIFT..............................................................................................................................................340
A.3.12 APS_FAIL............................................................................................................................................................341
A.3.13 APS_INDI.............................................................................................................................................................343
A.3.14 APS_MANUAL_STOP........................................................................................................................................344
A.3.15 ATMPW_UNKNOWNCELL_EXC....................................................................................................................345
A.3.16 AU_AIS................................................................................................................................................................346
A.3.17 AU_LOP...............................................................................................................................................................347
A.3.18 B1_EXC................................................................................................................................................................348
A.3.19 B1_SD...................................................................................................................................................................350
A.3.20 B2_EXC................................................................................................................................................................352
A.3.21 B2_SD...................................................................................................................................................................355
A.3.22 B3_EXC................................................................................................................................................................357
A.3.23 B3_EXC_VC3......................................................................................................................................................359
A.3.24 B3_SD...................................................................................................................................................................361
A.3.25 B3_SD_VC3.........................................................................................................................................................363
A.3.26 BAT1TEMP_SENSOR_FAIL.............................................................................................................................366
A.3.27 BAT2TEMP_SENSOR_FAIL.............................................................................................................................367
A.3.28 BD_NOT_INSTALLED.......................................................................................................................................368
A.3.29 BD_STATUS........................................................................................................................................................369
A.3.30 BDTEMP_SENSOR_FAIL..................................................................................................................................371
A.3.31 BGPBACKTRANSITION...................................................................................................................................372
A.3.32 BIOS_STATUS....................................................................................................................................................374
A.3.33 BIP_EXC..............................................................................................................................................................374
x
A.3.34 BIP_SD.................................................................................................................................................................376
A.3.35 BOOTROM_BAD................................................................................................................................................378
A.3.36 BUS_ERR.............................................................................................................................................................379
A.3.37 CES_ACR_LOCK_ABN.....................................................................................................................................381
A.3.38 CES_APS_INDI...................................................................................................................................................383
A.3.39 CES_APS_MANUAL_STOP..............................................................................................................................385
A.3.40 CES_JTROVR_EXC............................................................................................................................................386
A.3.41 CES_JTRUDR_EXC............................................................................................................................................387
A.3.42 CES_K1_K2_M....................................................................................................................................................388
A.3.43 CES_K2_M...........................................................................................................................................................389
A.3.44 CES_LOSPKT_EXC............................................................................................................................................391
A.3.45 CES_MALPKT_EXC...........................................................................................................................................392
A.3.46 CES_MISORDERPKT_EXC...............................................................................................................................393
A.3.47 CES_RDI..............................................................................................................................................................394
A.3.48 CES_STRAYPKT_EXC......................................................................................................................................395
A.3.49 CESPW_OPPOSITE_ACFAULT........................................................................................................................395
A.3.50 CESPW_OPPOSITE_RAI...................................................................................................................................396
A.3.51 CFCARD_FAILED..............................................................................................................................................397
A.3.52 CFCARD_OFFLINE............................................................................................................................................398
A.3.53 CHCS....................................................................................................................................................................400
A.3.54 CLK_LOCK_FAIL...............................................................................................................................................401
A.3.55 CLK_NO_TRACE_MODE..................................................................................................................................402
A.3.56 COMMUN_FAIL.................................................................................................................................................404
A.3.57 COM_EXTECC_FULL........................................................................................................................................406
A.3.58 CONFIG_NOSUPPORT......................................................................................................................................406
A.3.59 DBMS_DELETE..................................................................................................................................................409
A.3.60 DBMS_ERROR....................................................................................................................................................409
A.3.61 DBMS_PROTECT_MODE.................................................................................................................................410
A.3.62 DCNSIZE_OVER.................................................................................................................................................411
A.3.63 DDN_LFA............................................................................................................................................................412
A.3.64 DOWN_E1_AIS...................................................................................................................................................413
A.3.65 DROPRATIO_OVER...........................................................................................................................................414
A.3.66 E1_LOC................................................................................................................................................................415
A.3.67 E1_LOS................................................................................................................................................................417
A.3.68 ELAN_SMAC_FLAPPING.................................................................................................................................418
A.3.69 ENVHUM_SENSOR_FAIL.................................................................................................................................419
A.3.70 ENVTEMP_SENSOR_FAIL...............................................................................................................................420
A.3.71 ENVTEMP1_SENSOR_FAIL.............................................................................................................................421
A.3.72 ENVTEMP2_SENSOR_FAIL.............................................................................................................................423
A.3.73 ERPS_IN_PROTECTION....................................................................................................................................424
A.3.74 ETH_APS_LOST.................................................................................................................................................425
xi
A.3.75 ETH_APS_PATH_MISMATCH.........................................................................................................................426
A.3.76 ETH_APS_SWITCH_FAIL.................................................................................................................................427
A.3.77 ETH_APS_TYPE_MISMATCH..........................................................................................................................428
A.3.78 ETH_AUTO_LINK_DOWN...............................................................................................................................429
A.3.79 ETH_CFM_AIS....................................................................................................................................................430
A.3.80 ETH_CFM_LOC..................................................................................................................................................432
A.3.81 ETH_CFM_MISMERGE.....................................................................................................................................434
A.3.82 ETH_CFM_RDI...................................................................................................................................................437
A.3.83 ETH_CFM_UNEXPERI......................................................................................................................................439
A.3.84 ETH_EFM_DF.....................................................................................................................................................442
A.3.85 ETH_EFM_EVENT.............................................................................................................................................443
A.3.86 ETH_EFM_LOOPBACK.....................................................................................................................................445
A.3.87 ETH_EFM_REMFAULT.....................................................................................................................................446
A.3.88 ETH_LOS.............................................................................................................................................................447
A.3.89 ETH_NO_FLOW.................................................................................................................................................449
A.3.90 ETH_PWR_SUPPLY_FAIL................................................................................................................................450
A.3.91 ETHOAM_DISCOVER_FAIL............................................................................................................................451
A.3.92 ETHOAM_RMT_CRIT_FAULT.........................................................................................................................452
A.3.93 ETHOAM_RMT_LOOP......................................................................................................................................454
A.3.94 ETHOAM_RMT_SD...........................................................................................................................................455
A.3.95 ETHOAM_SELF_LOOP.....................................................................................................................................457
A.3.96 ETHOAM_VCG_SELF_LOOP...........................................................................................................................459
A.3.97 EX_ETHOAM_CC_LOS.....................................................................................................................................460
A.3.98 EX_ETHOAM_MPID_CNFLCT.........................................................................................................................462
A.3.99 EXT_SYNC_LOS................................................................................................................................................463
A.3.100 EXT_TIME_LOC...............................................................................................................................................464
A.3.101 FAN_AGING.....................................................................................................................................................465
A.3.102 FAN_FAIL.........................................................................................................................................................466
A.3.103 FCS_ERR...........................................................................................................................................................467
A.3.104 FDBSIZEALM_ELAN.......................................................................................................................................469
A.3.105 FLOW_OVER....................................................................................................................................................470
A.3.106 GSP_RSVP_NB_AUTH_ERR...........................................................................................................................471
A.3.107 GSP_RSVP_NB_DOWN...................................................................................................................................472
A.3.108 GSP_TNNL_DOWN..........................................................................................................................................473
A.3.109 HARD_BAD.......................................................................................................................................................475
A.3.110 HARD_NONSUPPORT.....................................................................................................................................477
A.3.111 HP_CROSSTR...................................................................................................................................................478
A.3.112 HP_LOM............................................................................................................................................................479
A.3.113 HP_RDI..............................................................................................................................................................480
A.3.114 HP_REI...............................................................................................................................................................481
A.3.115 HP_SLM.............................................................................................................................................................482
xii
A.3.116 HP_TIM..............................................................................................................................................................483
A.3.117 HP_UNEQ..........................................................................................................................................................484
A.3.118 HPAD_CROSSTR..............................................................................................................................................485
A.3.119 IF_CABLE_OPEN.............................................................................................................................................486
A.3.120 IF_INPWR_ABN...............................................................................................................................................488
A.3.121 IF_MODE_UNSUPPORTED............................................................................................................................489
A.3.122 IMA_GROUP_LE_DOWN................................................................................................................................490
A.3.123 IMA_GROUP_RE_DOWN...............................................................................................................................491
A.3.124 IMA_TXCLK_MISMATCH..............................................................................................................................492
A.3.125 IN_PWR_ABN...................................................................................................................................................493
A.3.126 IN_PWR_HIGH.................................................................................................................................................495
A.3.127 IN_PWR_LOW..................................................................................................................................................496
A.3.128 INTEMP_SENSOR_FAIL.................................................................................................................................498
A.3.129 IPFPM_INST_TLP_ERR...................................................................................................................................499
A.3.130 ISISADJACENCYCHANGE.............................................................................................................................500
A.3.131 J0_MM................................................................................................................................................................501
A.3.132 K1_K2_M...........................................................................................................................................................502
A.3.133 K2_M..................................................................................................................................................................504
A.3.134 L3V_TRAP_THRE_EXCEED...........................................................................................................................506
A.3.135 L3V_TRAP_VRF_DOWN.................................................................................................................................507
A.3.136 LAG_BWMM.....................................................................................................................................................508
A.3.137 LAG_DOWN......................................................................................................................................................509
A.3.138 LAG_MEMBER_DOWN..................................................................................................................................510
A.3.139 LAG_PORT_FAIL.............................................................................................................................................512
A.3.140 LAG_VC_PORT_FAIL.....................................................................................................................................514
A.3.141 LAN_LOC..........................................................................................................................................................515
A.3.142 LASER_CLOSED..............................................................................................................................................517
A.3.143 LASER_MOD_ERR...........................................................................................................................................517
A.3.144 LASER_MOD_ERR_EX...................................................................................................................................519
A.3.145 LASER_SHUT...................................................................................................................................................520
A.3.146 LCAS_FOPR......................................................................................................................................................521
A.3.147 LCAS_FOPT......................................................................................................................................................522
A.3.148 LCAS_PLCR......................................................................................................................................................524
A.3.149 LCAS_PLCT......................................................................................................................................................526
A.3.150 LCAS_TLCR......................................................................................................................................................527
A.3.151 LCAS_TLCT......................................................................................................................................................528
A.3.152 LCD....................................................................................................................................................................530
A.3.153 LCS_LIMITED...................................................................................................................................................531
A.3.154 LDP_PEER_DOWN...........................................................................................................................................534
A.3.155 LFA.....................................................................................................................................................................535
A.3.156 LICENSE_LOST................................................................................................................................................537
xiii
A.3.157 LINK_ERR.........................................................................................................................................................538
A.3.158 LMFA.................................................................................................................................................................539
A.3.159 LOOP_ALM.......................................................................................................................................................541
A.3.160 LP_CROSSTR....................................................................................................................................................544
A.3.161 LP_R_FIFO........................................................................................................................................................545
A.3.162 LP_RDI...............................................................................................................................................................546
A.3.163 LP_RDI_VC12...................................................................................................................................................547
A.3.164 LP_RDI_VC3.....................................................................................................................................................548
A.3.165 LP_REI...............................................................................................................................................................549
A.3.166 LP_REI_VC12....................................................................................................................................................550
A.3.167 LP_REI_VC3......................................................................................................................................................551
A.3.168 LP_RFI...............................................................................................................................................................552
A.3.169 LP_SLM.............................................................................................................................................................553
A.3.170 LP_SLM_VC12..................................................................................................................................................553
A.3.171 LP_SLM_VC3....................................................................................................................................................554
A.3.172 LP_T_FIFO.........................................................................................................................................................555
A.3.173 LP_TIM..............................................................................................................................................................556
A.3.174 LP_TIM_VC12...................................................................................................................................................557
A.3.175 LP_TIM_VC3.....................................................................................................................................................558
A.3.176 LP_UNEQ...........................................................................................................................................................560
A.3.177 LP_UNEQ_VC12...............................................................................................................................................561
A.3.178 LP_UNEQ_VC3.................................................................................................................................................562
A.3.179 LPS_UNI_BI_M.................................................................................................................................................563
A.3.180 LPT_CFG_CLOSEPORT...................................................................................................................................564
A.3.181 LPT_INEFFECT.................................................................................................................................................565
A.3.182 LPT_RFI.............................................................................................................................................................567
A.3.183 LSR_BCM_ALM...............................................................................................................................................568
A.3.184 LSR_NO_FITED................................................................................................................................................569
A.3.185 LSR_WILL_DIE................................................................................................................................................570
A.3.186 LTI......................................................................................................................................................................571
A.3.187 MAC_EXT_EXC...............................................................................................................................................573
A.3.188 MAC_FCS_EXC................................................................................................................................................574
A.3.189 MAC_FCS_SD...................................................................................................................................................575
A.3.190 MOD_COM_FAIL.............................................................................................................................................576
A.3.191 MOD_TYPE_MISMATCH...............................................................................................................................577
A.3.192 MP_DELAY.......................................................................................................................................................579
A.3.193 MP_DOWN........................................................................................................................................................580
A.3.194 MPLS_PW_AIS.................................................................................................................................................582
A.3.195 MPLS_PW_CSF.................................................................................................................................................583
A.3.196 MPLS_PW_BDI.................................................................................................................................................584
A.3.197 MPLS_PW_Excess.............................................................................................................................................584
xiv
A.3.198 MPLS_PW_LCK................................................................................................................................................585
A.3.199 MPLS_PW_LOCK.............................................................................................................................................586
A.3.200 MPLS_PW_LOCV.............................................................................................................................................587
A.3.201 MPLS_PW_MISMATCH..................................................................................................................................589
A.3.202 MPLS_PW_MISMERGE...................................................................................................................................590
A.3.203 MPLS_PW_OAMFAIL......................................................................................................................................591
A.3.204 MPLS_PW_RDI.................................................................................................................................................592
A.3.205 MPLS_PW_SD...................................................................................................................................................593
A.3.206 MPLS_PW_SF...................................................................................................................................................594
A.3.207 MPLS_PW_UNEXPMEG..................................................................................................................................595
A.3.208 MPLS_PW_UNEXPMEP..................................................................................................................................596
A.3.209 MPLS_PW_UNEXPPER...................................................................................................................................596
A.3.210 MPLS_PW_UNKNOWN...................................................................................................................................597
A.3.211 MPLS_TUNNEL_AIS.......................................................................................................................................598
A.3.212 MPLS_TUNNEL_BDI.......................................................................................................................................599
A.3.213 MPLS_TUNNEL_Excess...................................................................................................................................600
A.3.214 MPLS_TUNNEL_FDI.......................................................................................................................................600
A.3.215 MPLS_TUNNEL_LOCV...................................................................................................................................601
A.3.216 MPLS_TUNNEL_LOCK...................................................................................................................................603
A.3.217 MPLS_TUNNEL_MISMATCH........................................................................................................................604
A.3.218 MPLS_TUNNEL_MISMERGE.........................................................................................................................605
A.3.219 MPLS_TUNNEL_OAMFAIL............................................................................................................................606
A.3.220 MPLS_TUNNEL_RDI.......................................................................................................................................607
A.3.221 MPLS_TUNNEL_SD.........................................................................................................................................607
A.3.222 MPLS_TUNNEL_SF.........................................................................................................................................608
A.3.223 MPLS_TUNNEL_UNEXPMEG........................................................................................................................609
A.3.224 MPLS_TUNNEL_UNEXPMEP........................................................................................................................610
A.3.225 MPLS_TUNNEL_UNEXPPER.........................................................................................................................611
A.3.226 MPLS_TUNNEL_UNKNOWN.........................................................................................................................612
A.3.227 MS_AIS..............................................................................................................................................................613
A.3.228 MS_CROSSTR...................................................................................................................................................614
A.3.229 MS_RDI..............................................................................................................................................................616
A.3.230 MS_REI..............................................................................................................................................................617
A.3.231 MSAD_CROSSTR.............................................................................................................................................617
A.3.232 MULTI_RPL_OWNER......................................................................................................................................619
A.3.233 MW_AM_TEST.................................................................................................................................................620
A.3.234 MW_BER_EXC.................................................................................................................................................620
A.3.235 MW_BER_SD....................................................................................................................................................624
A.3.236 MW_CFG_MISMATCH....................................................................................................................................628
A.3.237 MW_CONT_WAVE..........................................................................................................................................629
A.3.238 MW_E1_LOST...................................................................................................................................................630
xv
A.3.239 MW_FEC_UNCOR............................................................................................................................................631
A.3.240 MW_LIM............................................................................................................................................................634
A.3.241 MW_LOF...........................................................................................................................................................636
A.3.242 MW_RDI............................................................................................................................................................641
A.3.243 NEIP_CONFUSION...........................................................................................................................................642
A.3.244 NESF_LOST.......................................................................................................................................................642
A.3.245 NESOFT_MM....................................................................................................................................................644
A.3.246 NO_BD_SOFT...................................................................................................................................................645
A.3.247 NP1_MANUAL_STOP......................................................................................................................................646
A.3.248 NP1_SW_FAIL..................................................................................................................................................647
A.3.249 NP1_SW_INDI...................................................................................................................................................648
A.3.250 NTP_SYNC_FAIL.............................................................................................................................................649
A.3.251 OCD....................................................................................................................................................................650
A.3.252 ODC_BATTERY_CURRENT_ABN................................................................................................................651
A.3.253 ODC_BATTERY_PWRDOWN........................................................................................................................653
A.3.254 ODC_DOOR_OPEN..........................................................................................................................................655
A.3.255 ODC_FAN_FAILED..........................................................................................................................................657
A.3.256 ODC_HUMI_ABN.............................................................................................................................................658
A.3.257 ODC_LOAD_PWRDOWN................................................................................................................................659
A.3.258 ODC_MDL_ABN...............................................................................................................................................662
A.3.259 ODC_POWER_FAIL.........................................................................................................................................664
A.3.260 ODC_SMOKE_OVER.......................................................................................................................................666
A.3.261 ODC_SURGE_PROTECTION_FAIL...............................................................................................................667
A.3.262 ODC_TEC_ALM...............................................................................................................................................669
A.3.263 ODC_TEMP_ABN.............................................................................................................................................670
A.3.264 ODC_WATER_ALM.........................................................................................................................................672
A.3.265 OSPFNBRSTATECHANGE.............................................................................................................................673
A.3.266 OUT_PWR_ABN...............................................................................................................................................675
A.3.267 OUT1TEMP_SENSOR_FAIL...........................................................................................................................676
A.3.268 OUT2TEMP_SENSOR_FAIL...........................................................................................................................678
A.3.269 PASSWORD_NEED_CHANGE.......................................................................................................................679
A.3.270 PATCH_BD_EXCLUDE...................................................................................................................................680
A.3.271 PATCH_BD_MATCH_FAIL............................................................................................................................680
A.3.272 PATCH_CHGSCC_NOTMATCH.....................................................................................................................681
A.3.273 PATCH_PKGERR.............................................................................................................................................682
A.3.274 PG_LINK_FAIL.................................................................................................................................................682
A.3.275 PG_PRT_DEGRADED......................................................................................................................................683
A.3.276 PLA_CFG_MISMATCH...................................................................................................................................684
A.3.277 PLA_DOWN......................................................................................................................................................686
A.3.278 PLA_MEMBER_DOWN...................................................................................................................................687
A.3.279 PORTMODE_MISMATCH...............................................................................................................................688
xvi
A.3.280 PORT_EXC_TRAFFIC......................................................................................................................................689
A.3.281 PORT_MODULE_OFFLINE.............................................................................................................................690
A.3.282 POWER_ABNORMAL.....................................................................................................................................691
A.3.283 POWER_ALM...................................................................................................................................................693
A.3.284 PPP_LCP_FAIL.................................................................................................................................................694
A.3.285 PPP_NCP_FAIL.................................................................................................................................................695
A.3.286 PTP_SOURCE_SWITCH..................................................................................................................................696
A.3.287 PTP_TIMESTAMP_ABN..................................................................................................................................697
A.3.288 PW_DOWN........................................................................................................................................................699
A.3.289 PW_DROPPKT_EXC........................................................................................................................................700
A.3.290 PW_NO_TRAFFIC............................................................................................................................................701
A.3.291 PWAPS_LOST...................................................................................................................................................702
A.3.292 PWAPS_PATH_MISMATCH...........................................................................................................................703
A.3.293 PWAPS_SWITCH_FAIL...................................................................................................................................704
A.3.294 PWAPS_TYPE_MISMATCH...........................................................................................................................705
A.3.295 PW_APS_DEGRADED.....................................................................................................................................706
A.3.296 PW_APS_OUTAGE...........................................................................................................................................707
A.3.297 R_LOC................................................................................................................................................................708
A.3.298 R_LOF................................................................................................................................................................709
A.3.299 R_LOS................................................................................................................................................................711
A.3.300 R_OOF................................................................................................................................................................712
A.3.301 RADIO_FADING_MARGIN_INSUFF.............................................................................................................714
A.3.302 RADIO_MUTE..................................................................................................................................................716
A.3.303 RADIO_RSL_BEYONDTH..............................................................................................................................717
A.3.304 RADIO_RSL_HIGH..........................................................................................................................................718
A.3.305 RADIO_RSL_LOW...........................................................................................................................................719
A.3.306 RADIO_TSL_HIGH...........................................................................................................................................720
A.3.307 RADIO_TSL_LOW...........................................................................................................................................721
A.3.308 RELAY_ALARM_CRITICAL..........................................................................................................................722
A.3.309 RELAY_ALARM_IGNORE.............................................................................................................................723
A.3.310 RELAY_ALARM_MAJOR...............................................................................................................................724
A.3.311 RELAY_ALARM_MINOR...............................................................................................................................724
A.3.312 RMFA.................................................................................................................................................................725
A.3.313 RPS_INDI...........................................................................................................................................................726
A.3.314 RS_CROSSTR....................................................................................................................................................728
A.3.315 RTC_FAIL..........................................................................................................................................................730
A.3.316 RT_TBL_LACK.................................................................................................................................................731
A.3.317 S1_SYN_CHANGE...........................................................................................................................................732
A.3.318 SCCDATA_BACKUP_FAIL(SYNC_FAIL)....................................................................................................733
A.3.319 SEC_RADIUS_FAIL.........................................................................................................................................734
A.3.320 SECU_ALM.......................................................................................................................................................736
xvii
A.3.321 SRV_SHUTDOWN_LD....................................................................................................................................737
A.3.322 SSL_CERT_NOENC.........................................................................................................................................737
A.3.323 SUBNET_RT_CONFLICT................................................................................................................................738
A.3.324 SWDL_ACTIVATED_TIMEOUT....................................................................................................................740
A.3.325 SWDL_AUTOMATCH_INH............................................................................................................................741
A.3.326 SWDL_CHGMNG_NOMATCH.......................................................................................................................742
A.3.327 SWDL_COMMIT_FAIL....................................................................................................................................743
A.3.328 SWDL_INPROCESS.........................................................................................................................................743
A.3.329 SWDL_NEPKGCHECK....................................................................................................................................744
A.3.330 SWDL_PKG_NOBDSOFT................................................................................................................................745
A.3.331 SWDL_PKGVER_MM......................................................................................................................................746
A.3.332 SWDL_ROLLBACK_FAIL...............................................................................................................................746
A.3.333 SYN_BAD..........................................................................................................................................................747
A.3.334 SYNC_C_LOS...................................................................................................................................................748
A.3.335 SYSLOG_COMM_FAIL...................................................................................................................................749
A.3.336 T_ALOS.............................................................................................................................................................750
A.3.337 T_LOC................................................................................................................................................................751
A.3.338 TEM_HA............................................................................................................................................................752
A.3.339 TEM_LA.............................................................................................................................................................753
A.3.340 TEMP_ALARM.................................................................................................................................................754
A.3.341 TEMP_OVER.....................................................................................................................................................755
A.3.342 TF........................................................................................................................................................................757
A.3.343 THUNDERALM................................................................................................................................................757
A.3.344 TIME_LOCK_FAIL...........................................................................................................................................758
A.3.345 TIME_NO_TRACE_MODE..............................................................................................................................759
A.3.346 TR_LOC.............................................................................................................................................................761
A.3.347 TU_AIS...............................................................................................................................................................762
A.3.348 TU_AIS_VC12...................................................................................................................................................764
A.3.349 TU_AIS_VC3.....................................................................................................................................................766
A.3.350 TU_LOP.............................................................................................................................................................768
A.3.351 TU_LOP_VC12..................................................................................................................................................768
A.3.352 TU_LOP_VC3....................................................................................................................................................770
A.3.353 TUNNEL_APS_DEGRADED...........................................................................................................................772
A.3.354 TUNNEL_APS_OUTAGE.................................................................................................................................773
A.3.355 UHCS..................................................................................................................................................................774
A.3.356 UP_E1_AIS........................................................................................................................................................775
A.3.357 USB_PROCESS_FAIL......................................................................................................................................776
A.3.358 V5_VCAIS.........................................................................................................................................................777
A.3.359 VC_AIS..............................................................................................................................................................778
A.3.360 VC_LOC.............................................................................................................................................................780
A.3.361 VC_RDI..............................................................................................................................................................782
xviii
A.3.362 VCAT_LOA.......................................................................................................................................................784
A.3.363 VCAT_LOM_VC12...........................................................................................................................................785
A.3.364 VCAT_LOM_VC3.............................................................................................................................................786
A.3.365 VCAT_SQM_VC12...........................................................................................................................................788
A.3.366 VCAT_SQM_VC3.............................................................................................................................................789
A.3.367 VERSION_NOTSUPPORT...............................................................................................................................791
A.3.368 VOLT_LOS........................................................................................................................................................793
A.3.369 VP_AIS...............................................................................................................................................................794
A.3.370 VP_LOC.............................................................................................................................................................796
A.3.371 VP_RDI..............................................................................................................................................................798
A.3.372 W_R_FAIL.........................................................................................................................................................800
A.3.373 WRG_BD_TYPE...............................................................................................................................................801
A.3.374 XPIC_LOS..........................................................................................................................................................801
B Performance Event Reference.................................................................................................804
B.1 Performance Events (by Event Type)........................................................................................................................805
B.1.1 SDH/PDH Performance Event List........................................................................................................................805
B.1.2 Radio Performance Events......................................................................................................................................809
B.1.3 MPLS Tunnel/PW Performance Events.................................................................................................................812
B.1.4 Other Performance Events......................................................................................................................................813
B.2 Performance Events (by Logical Board)....................................................................................................................814
B.2.1 CQ1.........................................................................................................................................................................816
B.2.2 CST/CSH/CSHU/CSHUA......................................................................................................................................819
B.2.3 EG4/EG4P...............................................................................................................................................................822
B.2.4 EM6T......................................................................................................................................................................822
B.2.5 EM6TA...................................................................................................................................................................822
B.2.6 EM6F......................................................................................................................................................................823
B.2.7 EM6FA...................................................................................................................................................................823
B.2.8 EFP8........................................................................................................................................................................824
B.2.9 EMS6......................................................................................................................................................................825
B.2.10 IF1.........................................................................................................................................................................827
B.2.11 IFU2/ISU2.............................................................................................................................................................830
B.2.12 IFX2/ISX2.............................................................................................................................................................834
B.2.13 ISV3......................................................................................................................................................................838
B.2.14 ML1/MD1.............................................................................................................................................................842
B.2.15 ODU......................................................................................................................................................................843
B.2.16 SL1D/SL1DA.......................................................................................................................................................844
B.2.17 SP3S/SP3D...........................................................................................................................................................846
B.3 Performance Events and Handling Procedures..........................................................................................................848
B.3.1 ATPC_P_ADJUST and ATPC_N_ADJUST.........................................................................................................848
B.3.2 AMDOWNCNT and AMUPCNT..........................................................................................................................848
B.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW.....................................................................................................849
xix
B.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR............................................................................................850
B.3.5 CURPOSITIVEPDV and CURNEGATIVEPDV..................................................................................................851
B.3.6 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and E1_LSES_SDH.............................................................851
B.3.7 E1_BBE, E1_ES, E1_SES, E1_CSES, and E1_UAS.............................................................................................853
B.3.8 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT............................................854
B.3.9 HPBBE, HPES, HPSES, HPCSES, and HPUAS...................................................................................................855
B.3.10 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS..........................................................................856
B.3.11 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...............................................................................................857
B.3.12 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG............................................................................................859
B.3.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS....................................................................................................859
B.3.14 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS............................................................................861
B.3.15 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV...................................................................................862
B.3.16 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY...............................862
B.3.17 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET.........................................................863
B.3.18 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and AVGPOSITIVEDELAY............................................864
B.3.19 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and MPLS_PW_UAS...................................................864
B.3.20 MSBBE, MSES, MSSES, MSCSES, and MSUAS..............................................................................................865
B.3.21 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS.......................................................................866
B.3.22 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR........................................................................................867
B.3.23 PG_IF_BBE, PG_IF_ES, PG_IF_SES, PG_IF_CSES, and PG_IF_UAS............................................................868
B.3.24 RPLMAX, RPLMIN, and RPLCUR....................................................................................................................870
B.3.25 RSBBE, RSES, RSSES, RSCSES, and RSUAS..................................................................................................870
B.3.26 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG..........................................................................................872
B.3.27 RSOOF and RSOFS..............................................................................................................................................872
B.3.28 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128, QAMWS256,
QAMWS512, QAM_L_WS512, QAMWS1024, and QAM_L_WS1024.......................................................................873
B.3.29 TLBMAX, TLBMIN, and TLBCUR....................................................................................................................874
B.3.30 RLHTT, RLLTT, TLHTT, TLLTT......................................................................................................................875
B.3.31 TPLMAX, TPLMIN, and TPLCUR.....................................................................................................................876
B.3.32 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG...........................................................................................876
B.3.33 TUPJCHIGH, TUPJCLOW, and TUPJCNEW....................................................................................................877
B.3.34 XPIC_XPD_VALUE............................................................................................................................................878
C RMON Event Reference..........................................................................................................879
C.1 List of RMON Alarm Entries....................................................................................................................................880
C.2 RMON Performance Entries List on the Packet-Plane..............................................................................................883
C.2.1 EM6F/EM6T/EM6FA/EM6TA/EG4/EG4P...........................................................................................................883
C.2.2 IFU2/IFX2...............................................................................................................................................................890
C.2.3 ISU2/ISX2/ISV3.....................................................................................................................................................896
C.2.4 ML1/MD1...............................................................................................................................................................903
C.2.5 CQ1.........................................................................................................................................................................909
C.2.6 CSH.........................................................................................................................................................................911
xx
C.2.7 CSHU/CSHUA.......................................................................................................................................................918
C.2.8 EFP8/EMS6............................................................................................................................................................935
C.3 RMON Performance Entries List on the EoS/EoPDH-Plane....................................................................................937
C.3.1 EFP8........................................................................................................................................................................937
C.3.2 EMS6......................................................................................................................................................................942
C.4 RMON Events and Handling Procedures..................................................................................................................947
C.4.1 ETHDROP..............................................................................................................................................................947
C.4.2 ETHEXCCOL.........................................................................................................................................................948
C.4.3 ETHLATECOL.......................................................................................................................................................949
C.4.4 RXBBAD................................................................................................................................................................950
C.4.5 TXDEFFRM...........................................................................................................................................................951
C.4.6 ETHUNDER...........................................................................................................................................................952
C.4.7 ETHOVER..............................................................................................................................................................952
C.4.8 ETHFRG.................................................................................................................................................................953
C.4.9 ETHJAB..................................................................................................................................................................954
C.4.10 ETHCOL...............................................................................................................................................................955
C.4.11 ETHFCS................................................................................................................................................................956
C.4.12 ATMPW_LOSPKTS............................................................................................................................................957
C.4.13 ATMPW_MISORDERPKTS...............................................................................................................................957
C.4.14 ATMPW_UNKNOWNCELLS............................................................................................................................958
C.4.15 ATM_CORRECTED_HCSERR..........................................................................................................................959
C.4.16 ATM_UNCORRECTED_HCSERR.....................................................................................................................959
C.4.17 CES_MISORDERPKTS.......................................................................................................................................960
C.4.18 CES_STRAYPKTS..............................................................................................................................................961
C.4.19 CES_MALPKTS...................................................................................................................................................961
C.4.20 CES_JTRUDR......................................................................................................................................................962
C.4.21 CES_JTROVR......................................................................................................................................................963
C.4.22 CES_LOSPKTS....................................................................................................................................................964
D Alarm Management.................................................................................................................965
D.1 NE Alarm Management.............................................................................................................................................966
D.2 Board Alarm Management........................................................................................................................................966
D.2.1 Setting the Alarm Severity......................................................................................................................................966
D.2.2 Alarm Suppression..................................................................................................................................................966
D.2.3 Alarm Auto-Report.................................................................................................................................................967
D.2.4 Alarm Reversion.....................................................................................................................................................967
D.2.5 Setting of the Bit Error Alarm Threshold...............................................................................................................967
D.2.6 AIS Insertion...........................................................................................................................................................968
D.2.7 UNEQ Insertion......................................................................................................................................................969
E Performance Event Management...........................................................................................970
E.1 NE Performance Event Management.........................................................................................................................971
E.2 Board Performance Event Management....................................................................................................................971
xxi
F Alarm Suppression Relationship...........................................................................................972
F.1 Alarm Suppression on TDM Plane............................................................................................................................973
F.2 Alarm Suppression on Data Plane..............................................................................................................................976
G Indicators of Boards.................................................................................................................983
H Glossary....................................................................................................................................1008
xxii
1 Safety Precautions
About This Chapter
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.
Maintenance Guide 1 Safety Precautions
1
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 Only trained and qualified personnel are permitted to install, operate, and maintain a device.
l Only certified professionals are permitted to remove the safety facilities, and to troubleshoot
and maintain the device.
l Only the personnel authenticated or authorized by Huawei are permitted to replace or
change the device or parts of the device (including software).
l The operating personnel must immediately report the faults or errors that may cause safety
problems to the person in charge.
Grounding Requirements
The grounding requirements are applicable to the device that needs to be grounded.
l When installing the device, always connect the grounding facilities first. When removing
the device, always disconnect the grounding facilities last.
l Ensure that the grounding conductor is intact.
l Do not operate the device in the absence of a suitably installed grounding conductor.
l The device must be connected to the PGND permanently. Before operating the device,
check the electrical connections of the device, and ensure that the device is properly
grounded.
Human Safety
l When there is a risk of a lightning strike, do not operate the fixed terminal or touch the
cables.
2
l When there is risk of a lightning strike, unplug the AC power connector. Do not use the
fixed terminal or touch the terminal or antenna connector.
NOTE
The preceding requirements apply to wireless fixed station terminals.
l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits to
telephone-network voltage (TNV) circuits.
l Do not look into optical ports without eye protection. Otherwise, human eyes may be hurt
by laser beams.
l 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.
l 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 Before any operation, install the device firmly on the ground or other rigid objects, such as
on a wall or in a rack.
l When the system is working, ensure that the ventilation hole is not blocked.
l When installing the front panel, use a tool to tighten the screws firmly, if required.
l After installing the device, clean up the packing materials.
1.2 Warning and Safety 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
LASER
RADIATION
DO NOT VIEW DIRECTLY
WITH OPTICAL
INSTRUMENTS
CLASS 1M 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.
3
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

FANLEAVESBEFORE
THEYSLOW 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.
4
High Leakage Current
CAUTION
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 Before installing or removing power cables, you must power off the device.
l Before connecting a power cable, you must ensure that the label on the power cable 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.
5
NOTICE
To avoid short-circuits when using a tool (such as a screwdriver), do not place the tool on the
ventilation plate of the subrack.
NOTICE
Prevent any screws from dropping into the subrack or chassis to avoid short-circuits.
Fuse
CAUTION
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
NOTICE
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.
l 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.
6
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 Incorrect operations of storage batteries cause hazards. During operation, prevent any short-
circuit, and prevent the electrolyte from overflowing or leakage.
l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte may
corrode metal parts and the circuit boards, and ultimately damage the circuit boards.
l A storage battery contains a great deal of energy. Misoperations may cause a short-circuit,
which leads to human injuries.
7
Basic Precautions
To ensure safety, note the following points before installing or maintaining the storage battery:
l Use special insulation tools.
l Wear an eye protector and take effective protection measures.
l Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowing
electrolyte.
l When handling the storage battery, ensure that its electrodes are upward. Leaning or
reversing the storage battery is prohibited.
l Before installing or maintaining the storage battery, ensure that the storage battery is
disconnected from the power supply that charges the storage battery.
Short-Circuit
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
NOTICE
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
NOTICE
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.
8
Battery Leakage
NOTICE
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 Sodium bicarbonate (NaHCO
3
)
l Sodium carbonate (Na
2
CO
3
)
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
NOTICE
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.
9
The fiber connectors and optical interfaces of the lasers must be cleaned with the following
special cleaning tools and materials:
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.
l Non-woven lens tissue
l Special compressed gas
l Cotton stick (medical cotton or long fiber cotton)
l Special cleaning roll, used with the recommended cleaning solvent
l Special magnifier for fiber connectors
For cleaning steps, see Task Collection "Cleaning Fiber Connectors and Adapters" in the 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 Use an attenuator if the optical power is excessively high. A high received optical power
damages the optical interface.
l Directly connect an attenuator to a slanting optical interface. Install the attenuator on the
IN port instead of the OUT port.
l 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

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.
NOTICE
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.
l 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.
11
CAUTION
When handling optical fibers, do not stand close to, or look into the optical fiber outlet directly
without eye protection.
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 All operations should be performed by authorized personnel who have completed the
required training courses.
l Wear a pair of eye-protective glasses when you are handling lasers or fibers.
l Ensure that the optical source is switched off before disconnecting optical fiber connectors.
l Do not look into the end of an exposed fiber or an open connector when you are not sure
whether the optical source is switched off.
l Use an optical power meter to measure the optical power and ensure that the optical source
is switched off.
l Before opening the front door of an optical transmission device, ensure that you are not
exposed to laser radiation.
l 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 Only trained personnel are permitted to cut and splice fibers.
l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the 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.
CAUTION
Strong radio frequency can harm the human body.
12
When installing or maintaining an aerial on the tower or mast that is installed with multiple
aerials, switch off the transmitter in advance.
1.7 Working at Heights
This topic describes safety precautions for working at heights.
CAUTION
When working at heights, be cautious to prevent objects from falling down.
The requirements for working at heights are as follows:
l The personnel who work at heights must be trained.
l Carry and handle the operating machines and tools with caution to prevent them from falling
down.
l Safety measures, such as wearing a helmet and a safety belt, must be taken.
l Wear cold-proof clothes when working at heights in cold areas.
l Check all lifting appliances thoroughly before starting the work, and ensure that they are
intact.
1.7.1 Hoisting Heavy Objects
This topic describes the safety precautions for hoisting heavy objects that you must follow when
installing, operating, and maintaining Huawei devices.
CAUTION
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.
l Only trained and qualified personnel can perform hoisting operations.
l Before hoisting heavy objects, check that the hoisting tools are complete and in good
condition.
l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object or
wall with good weight-bearing capacity.
l Issue orders with short and explicit words to ensure correct operations.
l Ensure that the angle between the two cables is less than or equal to 90 degrees during the
lifting, as shown in Figure 1-4.
13
Figure 1-4 Hoisting heavy objects

1.7.2 Using Ladders
This topic describes safety precautions for using ladders.
Checking Ladders
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.
l 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.
14
Figure 1-5 Slanting a ladder

Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
l Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
l Before operations, ensure that your body is stable to reduce risks.
l Do not climb higher than the fourth rung of the ladder (counted from up to down).
If you want to climb up a roof, ensure that the ladder top is at least one meter higher than the
roof, as shown in Figure 1-6.
Figure 1-6 Ladder top being one meter higher than the roof

15
1.8 Mechanical Safety
This topic describes safety precautions for drilling holes, handling sharp objects, operating fans,
and carrying heavy objects.
Drilling Holes
CAUTION
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 Before drilling a hole on the cabinet, remove the cables inside the cabinet.
l Wear an eye protector when drilling holes. This is to prevent eyes from being injured by
the splashing metal scraps.
l Wear protection gloves when drilling holes.
l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,
clean up the metallic scraps.
Sharp Objects
CAUTION
Wear protection gloves when carrying the device. This is to prevent hands from being injured
by the sharp edges of the device.
Fans
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.
l 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.
16
CAUTION
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.
l 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
NOTICE
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 Slide the board along the guide rails.
l Do not contact one board with another to avoid short-circuits or damage.
l When holding a board in hand, do not touch the board circuits, components, connectors,
or connection slots of the board to prevent damage caused by ESD of the human body to
the electrostatic-sensitive components.
Binding Signal Cables
NOTICE
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:
17
l When installing cables, ensure that the environment temperature is above 0C.
l 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.
l 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
CAUTION
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
CAUTION
Before installing or removing an IF cable, you must turn off the power switch of the IF board.
18
2 Notices for High-Risk Operations
About This Chapter
This 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
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.
Maintenance Guide 2 Notices for High-Risk Operations
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

Turning On the Toggle Lever Switch
1. Gently pull on the toggle lever switch out.
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.
21
2. 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
Procedure
Step 1 Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off the
ODU.
22
2
1
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
Procedure
Step 1 Follow instructions in 2.1 Operation Guide for the Toggle Lever Switch to power off the
ODU.
23
2
1
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.
24
3 2 1
3
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
25
3 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
Maintenance Item Recommen
ded
Maintenan
ce Cycle
Remarks
Checking the NE status Every day l If the NE icon is green, the NE operates
properly.
l If the NE icon is gray, the NE is
unreachable due to DCN faults.
l If the NE icon is in other colors, alarms
are reported or exceptions occur. You
need to troubleshoot in time.
Browsing current alarms Every day l Handle the alarms by referring to A.3
Alarms and Handling Procedures.
l For port alarms due to the interconnected
equipment, see 4.3.3 Browsing Current
Performance Events to reduce the
number of alarms and prevent interference
to emergent alarms.
Browsing historical alarms Every week By finding causes of and solutions to
historical alarms, you can take precautions to
avoid related faults.
Maintenance Guide 3 Routine Maintenance
26
ded
Maintenan
ce Cycle
Remarks
Browsing abnormal events Every week l Security events are generally records of
normal operations. Investigate the illegal
operations if there are any.
l Abnormal events about equipment have
been properly solved.
Browsing current
performance events
Every week l Gauge type performance events such as
the board temperature and laser power are
stable.
l Bit error type performance events meet
requirements on link availability.
Browsing historical
performance events
Every week
Browsing historical transmit
power and receive power
Every week l Historical received signal levels do not
exceed the fade margin for a long time.
l When automatic transmit power control
(ATPC) is disabled, historical transmitted
signal levels are allowed to be 3 dB larger
or smaller than the specified value.
Testing IF 1+1 protection
switching
Half a year 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.
Testing the IF N+1 protection
switching
Half a year Applies only to the equipment that is
configured with N+1 protection.

Field Maintenance Items for Indoor Equipment
ded
Maintenan
ce Cycle
Remarks
Checking the
telecommunications room
Every two
months
The site environment meets equipment
operation requirements.
Maintaining the environment
of outdoor cabinets
Half a year

27
Field Maintenance Items for Outdoor Equipment
Maintenance Item Recommended
Maintenance Cycle
Remarks
Checking the ODU
a
Half a year
NOTE
Perform a complete check after
a level-8 or higher-level
hurricane, an earthquake, or
other unexpected
circumstances.
The OptiX RTN 950 is
fixedly mounted and its
appearance is in good
condition, without the
coating being damaged or
corroded.
Checking the hybrid coupler The hybrid coupler is fixedly
mounted and its appearance
is in good condition, without
the coating being damaged or
corroded.
Checking the antenna The antenna is tightly placed
and does not deviate from the
designed angle.
Checking the IF cable and/or
flexible waveguide
The exterior of the cable is
intact, and the connectors are
properly waterproofed. The
cable is fixed properly with a
feeder fastener or cable ties,
and the cable bending degree
meets the requirement.
Checking the LOS condition A radio link is not blocked by
any visible object.

NOTE
a
: An area close to a pollution source refers to the area that covers a radius within any of the following
values:
l 3.7 km away from salty waters (such as an ocean and salty water)
l 3 km away from severe pollution sources (such as iron refinery works, and coal mines)
l 2 km away from intermediate pollution sources (such as chemical plants, rubber processing works, and
electroplating workshops)
l 1 km away from light pollution sources (such as food processing works, leather working plants, and
heating boilers).
28
4 Network Monitoring
About This Chapter
4.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.
4.2 Checking the Board Status
You can learn about the board status in a visual manner by checking the slot diagram.
4.3 Alarm and Performance Data Query
This section describes how to query alarms and non RMON-based performance data, such as
SDH performance data and microwave link performance data. You can query real-time and
historical performance data, which are monitored based on a 15minute or 24hour monitoring
period.
4.4 Microwave Link Performance Query
This section describes operations related to microwave link performance query.
4.5 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
4.6 Ethernet Port Traffic Monitoring
This section describes operations related to Ethernet traffic monitoring on Ethernet ports and
microwave ports.
4.7 Long-term Network Performance Monitoring
The U2000 centrally monitors long-term performance of various Huawei devices through the
Performance Management System (PMS).
4.8 Report Query
This section describes operations related to report query. You can obtain network information
from reports.
4.9 Alarm and Performance Management Setting
This section describes operations related to alarm and performance management.
Maintenance Guide 4 Network Monitoring
29
4.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.
Tools, Equipment, and Materials
U2000
Precautions
NOTE
By default, the color of the NE icon on the U2000 indicates the NE status.
Procedure
Step 1 Query NE running status.
1
2
View NE running
status.
3
Select the
desired NE.
4
30
NOTE
You can also determine NE running status by referring to information on the Legend tab.
NOTE
Complete the following steps to check NE running status from the WebLCT:
1. Query Communication status and Login status of the NE in NE List.
2. If Login status is Offline, log in to the NE.
3. Select the NE and click Log in.
4. Set User Name and Password.
NOTE
The default user name is lct.
The lct account owns system-level rights.
The default password of the lct account is password.
5. View NE status and alarm status.
----End
4.2 Checking the Board Status
You can learn about the board status in a visual manner by checking the slot diagram.
Prerequisites
31
U2000
Procedure
Step 1 Query board running status.
1
2
3
Right-click
the desired
NE.
4
Determine the board
running status by referring
to legend information.
NOTE
Complete the following step to query board running status from the WebLCT:
Click the Slot Layout tab in NE Explorer.
----End
4.3 Alarm and Performance Data Query
This section describes how to query alarms and non RMON-based performance data, such as
SDH performance data and microwave link performance data. You can query real-time and
historical performance data, which are monitored based on a 15minute or 24hour monitoring
period.
4.3.1 Browsing Current Alarms
You can find the faults that occur on the equipment by browsing current alarms.
Prerequisites
U2000
32
Procedure
Step 1 Open the current alarm window.
1
2
Step 2 Specify filter conditions.
33
3
Configure the severity, type, and
maintenance status parameters of the
alarms to be queried.
Set the occurring time and clearing time
of the alarms to be queried.
4
5
6
Click the Alarm Source tab and
specify filter conditions.
8
7
Select the desired
NEs.
Configure the filter
type. For example,
you can filter alarms
by NE.
9
10
11
Step 3 View alarm information.
34
Select an alarm and view its details
and possible causes in the following
panes.
12
Alarm details: contain information
about the board and optical port that
report the alarm as well as alarm
parameters.
Alarm handling: contains possible
causes for the alarm and reference
links to alarm handling suggestions
Step 4 Contact troubleshooting personnel in a timely manner for alarm handling.
For details about alarm handling, see A.3 Alarms and Handling Procedures.
35
NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
The Browse Current Alarms tab page is displayed by default.
----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 You can click (red) to browse the network-wide critical alarms.
l You can click (orange) to browse the network-wide major alarms.
l You can click (yellow) to browse the network-wide minor alarms.
l You can click (light-blue) to browse the network-wide warning alarms.
NOTE
By default, the number shown by each indicator indicates the number of current network-wide alarms, 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 Red: critical alarm
36
l Orange: major alarm
l Yellow: minor alarm
l Purple: warning
l Light blue: event
4.3.2 Browsing Historical Alarms
You can know the faults that occur on the equipment in a past period of time by browsing
historical alarms. A historical alarm refers to an alarm that is already cleared.
Prerequisites
You must be an NM user with NE monitor authority or higher.
U2000
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Open the historical alarm window.
1
2
37
3
Configure the severity, type, and maintenance
status parameters of the alarms to be queried.
Set the occurring time and clearing time
of the alarms to be queried.
4
38
5
6
Click the Alarm Source tab and
specify filter conditions.
8
7
Select the desired
NEs.
Configure the filter
type. For example,
you can filter alarms
by NE.
9
10
11
Step 3 View alarm information.
39
Select an alarm and view its details
and possible causes in the following
panes.
12
Alarm details: contain information about
the board and optical port that report the
alarm as well as alarm parameters.
Alarm handling: contains possible
causes for the alarm and reference
links to alarm handling suggestions
NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
Click the Browse Historical alarms tab.
----End
4.3.3 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.
l You must be an NM user with NE maintainer authority or higher.
U2000
40
NOTE
Procedure
Step 1 Open the performance data window.
1
2
Step 2 View current performance data.
Select performance event types and
specify the performance monitoring
period.
(Optional) Output the
performance data.
3
5
6
8
Select the desired
NEs.
Configure the query type.
For example, Measure is
selected here.
7
4
41
NOTE
Complete the following steps to query current performance data from the WebLCT:
Select the desired board in the NE Explorer and choose Performance > Current Performance from the
Function Tree.
----End
4.3.4 Browsing Historical Performance Events
You can know the faults that occur on the equipment in a past period of time by browsing
historical 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.
U2000
Procedure
Step 1 Open the performance data window.
1
2
3
Step 2 View historical performance data.
42
5
4
6
7
Select the desired
NEs.
Configure the
query type. For
example, Count is
selected here.
8
Select performance event types and
specify the performance monitoring
period.
NOTE
Complete the following steps to query historical performance data from the WebLCT:
Select the desired board in the NE Explorer and choose Performance > Historical Performance from the
Function Tree.
----End
4.3.5 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
NOTE
Procedure
Step 1 Open the Performance Threshold-Crossing Record window.
43
1
2
3
Step 2 Query performance threshold-crossing records.
5
4
6
Select the desired
NEs.
7
Select performance event types
and specify the performance
monitoring period.
NOTE
Complete the following steps to query performance threshold-crossing records from the WebLCT:
Select a desired board in the NE explorer and choose Performance > Threshold-Crossing Record from the
Function Tree.
----End
44
4.3.6 Browsing UAT Events
Learn about the severe abnormalities on the transmission line by browsing UAT events.
Prerequisites
Tools, Instruments, and Materials
U2000
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
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 Open the UAT window
1
2
3
Step 2 Query UAT events.
45
5
4
6
Select the
desired board.
7
Specify the time period, data source
and functional block type.
----End
4.4 Microwave Link Performance Query
This section describes operations related to microwave link performance query.
4.4.1 Querying the Historical Transmit Power and Receive Power
If the radio link requires troubleshooting, query the change trend for the historical transmit power
and receive power for reference.
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.
U2000
NOTE
Procedure
Step 1 Query historical receive power or transmit power information.
46
2
1
In the NE Explorer,
select the desired
ODU.
3
Set the time range, monitoring period, and
power parameters.
4
Click Draw.
The power curve is
displayed.
----End
4.4.2 Querying the SNR Values of a Radio Link
This section describes how to query the signal-to-noise ratio (SNR) change curve of a radio link,
assisting in handling radio link faults.
Prerequisites
l The IF boards and the ODUs to which the IF boards are connected have been added in the
NE Panel.
U2000
NOTE
Procedure
Step 1 Query how the SNR or Root-mean-square (RMS) error changes on microwave links.
47
2
1
In the NE Explorer,
select the desired IF
board.
3
Set the time range, monitoring period, and
performance type (SNR or MSE).
4
Click Draw.
The SNR or MSE curve is
displayed.
----End
4.4.3 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
U2000
NOTE
Procedure
Step 1 Right-click a microwave link in the main topology and choose Microwave Link Performance
Statistics.
48
2
1
Right-click the desired
microwave link.
49
NOTE
Uncheck Auto Refresh. Click Save as to save current performance of the microwave link into a TXT file.
Complete the following steps to query current performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
4.4.4 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
NOTE
Procedure
Step 1 Query historical performance of the microwave link.
2
1
microwave link.
50
3 4
Specify the query period and
monitoring period of the the
desired performance data.
5
(Optional) Specify the data type to be
displayed. By default, link transmit power and
receive power are displayed.
6
8
(Optional) Move the cursor
over the desired node to
check link information at a
specific time.
7
NOTE
Complete the following steps to query historical performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
4.5 Ethernet Performance Query
This section describes operations related to Ethernet performance query.
Context
NOTE
You can query real-time performance data and recent performance data.
Ethernet performance is monitored through RMON. Available performance monitoring periods include 30s, 30
minutes, custom period 1 (15 minutes by default), and custom period 2 (24 hours by default).
4.5.1 Browsing Current Ethernet Performance
After setting the RMON statistics group. you can browse real-time Ethernet performance
statistics.
51
Prerequisites
l 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 4-1 Packet plane
Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce
Ethernet
port
a
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.
Extended
performan
ce
MPLS
tunnel
performan
ce
MPLS
Tunnel
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 VPN-
PW
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
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the shortcut
menu.
52
Performa
nce
Object
Browsed
Object
Navigation Path
CES-PW
performan
ce
CES
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
ATM/IMA
(access
side)
performan
ce
Smart E1
port
Function Tree.
ATM-PW
performan
ce
ATM
PWE3
performan
ce
ATM
PWE3
service
choose Configuration > ATM Service Management from
the Function Tree.
2. Select one or more ATM PWE3 services, right-click the
menu.
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on
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.
53
Performa
nce
Object
Browsed
Object
Navigation Path
Port
priority
performan
ce
Egress
queues
For FE/GE ports:
Configuration > Interface Management > Ethernet
Interface from the Function Tree.
2. Click the Basic Attributes tab.
4. Select the desired egress queue in the Object drop-down list.
For Integrated IP radio ports:
Configuration > Interface Management > Microwave
Port DS
domain
performan
ce
Ports in a
DS
domain
Configuration > QoS Management > Diffserv Domain
Management > Diffserv Domain Management from the
Function Tree.
2. Select the desired DS domain.

Table 4-2 EoS/EoPDH plane
Performa
nce
Object
Obrowse
Object
Navigation Path
Basic
performan
ce
Ethernet
port
b
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.
Extended
performan
ce
54
Performa
nce
Object
Obrowse
Object
Navigation Path
VCG-other
performan
ce
VCTRUN
K port

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. Select the desired object or port from the drop-down list.
2. Select the performance items for which statistics need to be collected.
3. 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
4.5.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 The corresponding boards must be added in the NE Panel.
U2000
NOTE
Procedure
55
Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce
Ethernet
port
a
Function Tree.
NOTE
Extended
performan
ce
MPLS
tunnel
performan
ce
MPLS
Tunnel
L2 VPN-
PW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service
menu.
CES-PW
performan
ce
CES
performan
ce
CES
service
Function Tree.
ATM/IMA
(access
side)
performan
ce
Smart E1
port
Function Tree.
56
Performa
nce
Object
Browsed
Object
Navigation Path
ATM-PW
performan
ce
ATM
PWE3
performan
ce
ATM
PWE3
service
the Function Tree.
menu.
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on
NOTE
Port
priority
performan
ce
Egress
queues
For FE/GE ports:
Port DS
domain
performan
ce
Ports in a
DS
domain
Function Tree.
57

Performa
nce
Object
Obrowse
Object
Navigation Path
Basic
performan
ce
Ethernet
port
b
NOTE
b:
Extended
performan
ce
VCG-other
performan
ce
VCTRUN
K port

NOTE
Step 2 Click the Event tab and set the corresponding parameters.
Step 3 Click Apply. Close the displayed dialog box.
----End
4.5.3 Setting Parameters for Monitoring Historical Ethernet
Performance
After configuring a historical control group, you can specify how the historical Ethernet
performance data is monitored.
Prerequisites
U2000
NOTE
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
58
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
4.5.4 Browsing Historical Ethernet Performance Data
After configuring an history group, you can browse the historical performance statistics.
Prerequisites
l The objects and performance events to be monitored must be set.
U2000
NOTE
Procedure
Performa
nce
Object
Browsed
Object
Navigation Path
Basic
performan
ce
Ethernet
port
a
Function Tree.
NOTE
Extended
performan
ce
59
Performa
nce
Object
Browsed
Object
Navigation Path
MPLS
tunnel
performan
ce
MPLS
Tunnel
L2 VPN-
PW
performan
ce
ETH
PWE3
service
L2 VPN
performan
ce
UNI-UNI
E-Line
service
menu.
CES-PW
performan
ce
CES
performan
ce
CES
service
Function Tree.
ATM/IMA
(access
side)
performan
ce
Smart E1
port
Function Tree.
ATM-PW
performan
ce
ATM
PWE3
performan
ce
ATM
PWE3
service
the Function Tree.
menu.
60
Performa
nce
Object
Browsed
Object
Navigation Path
Port traffic
classificati
on
performan
ce
Ports that
perform
complex
traffic
classificati
on
NOTE
Port
priority
performan
ce
Egress
queues
For FE/GE ports:
Port DS
domain
performan
ce
Ports in a
DS
domain
Function Tree.

61
Performa
nce
Object
Obrowse
Object
Navigation Path
Basic
performan
ce
Ethernet
port
b
NOTE
b:
Extended
performan
ce
VCG-other
performan
ce
VCTRUN
K port

NOTE
Step 2 Click the History Group tab.
Step 3 Set the parameters of the historical group.
1. Select the desired object or port from the drop-down list.
2. Click and specify the required time span.
3. Select the performance items to browse.
4. Under History Table Type, set the time span for the performance items to be browsed.
Step 4 Click Query.
----End
4.6 Ethernet Port Traffic Monitoring
This section describes operations related to Ethernet traffic monitoring on Ethernet ports and
microwave ports.
4.6.1 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 the ports on the packet plane support this operation.
Prerequisites
62
The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring
function on a port, see 4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization
of Ethernet Ports.
U2000
NOTE
Background Information
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 Set Ethernet performance monitoring parameters.
1
2
3
Select the board where
the desired Ethernet
port resides.
4
Configure whether to flow
monitoring, physical bandwidth
monitoring, and bandwidth
utilization monitoring.
----End
4.6.2 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 the ports on the packet plane
support this operation.
63
Prerequisites
The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring
function on a port, see 4.6.1 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 4.5.1 Browsing Current Ethernet
Performance.
Procedure
Step 1 Query traffic, physical bandwidth, and bandwidth utilization.
1
2
3
Select the
desired board.
5
Specify the time period
and display mode.
4
Specify the data type. Available data
types include the flow data, physical
bandwidth data, and bandwidth usage
data.
----End
64
4.7 Long-term Network Performance Monitoring
The U2000 centrally monitors long-term performance of various Huawei devices through the
Performance Management System (PMS).
4.7.1 Creating a Performance Monitoring Template
This section describes how to create a performance monitoring template. Performance
monitoring templates specify counters used by performance monitoring instances and their
thresholds (if any). When counter values collected exceed the preset thresholds, the system
reports corresponding threshold crossing alerts (TCAs).
Prerequisites
You must be an NM user with NE operator authority or higher.
U2000
NOTE
The Web LCT does not support this operation.
Context
NOTE
You can create data monitoring templates and remote network monitoring (RMON) TCA monitoring
templates. To monitor Ethernet performance counters supporting TCAs, create RMON TCA monitoring
templates. To monitor other counters, create data monitoring templates.
Procedure
Step 1 Create a data monitoring template.
65
Select the monitoring
resource type.
1
2 3
4
5
Set the parameters of the
data monitoring template.
6
7
Click Add, and select the
performance monitoring
indicators.
9
8
Step 2 Create an RMON TCA monitoring template.
66
Select the monitoring
resource type.
1
2 3
4
5
Enter the template name and
set the template type to RMON
TAC.
6
7
Click Add, and select the
indicators.
8
9 Set the monitoring
threshold parameters.
10
----End
4.7.2 Creating a Performance Monitoring Instance
This section describes how to create a performance monitoring instance. A performance
monitoring instance can monitor the performance of multiple objects at the same time. You can
associate a created performance monitoring template and a created performance statistics
collection policy to a performance monitoring instance.
67
Prerequisites
U2000
NOTE
Procedure
Step 1 Open the Create Monitoring Instance dialog box.
2
3
1
Step 2 Select monitoring resources.
68
Select the desired
NE.
4
5
7
6
Select the desired
port.
8
Step 3 Select the monitoring template.
(Optional) If there is no desired
data monitoring template, create
one for the instances.
9
(Optional) Select the desired data
monitoring template if it is available. If
there is no desired template, go to step
10.
10
11
(Optional) Select the desired RMON
threshold monitoring template if it is
available. If there is no desired template,
go to step 12.
12
(Optional) If there is no desired RMON
threshold monitoring template, create one
for the instances.
13
NOTE
Complete step 9 and step 10 when creating a data monitoring instance.
Complete step 11 and step 12 when creating an RMON TCA monitoring instance.
Step 4 Specify the monitoring time.
69
14
NOTE
Skip this step for the OptiX RTN 950, which does not support the setting of monitoring time.
Step 5 Close the dialog box.
15
NOTE
If a creation success message is displayed, the creation is successful.
If the creation fails, determine the failure cause according to the displayed error information and recreate the
instance.
----End
70
4.7.3 Browsing the Real-Time Data of a Performance Monitoring
Instance
This section describes how to browse the real-time performance data of objects monitored by a
performance monitoring instance.
Prerequisites
l There is at least one performance monitoring instance.
U2000
NOTE
Procedure
Step 1 Open the real-time monitoring window.
2
1
instance.
Step 2 View real-time performance data.
71
3
(Optional) Set the timeline
granularity. The default value is 10s.
4
(Optional) Set the
performance display
mode. The default value is
line chart.
----End
4.7.4 Browsing the Historical Data of a Performance Monitoring
Instance
This section describes how to browse the performance data of objects monitored by a
performance monitoring instance in a specific time range.
Prerequisites
l There is at least one performance monitoring instance.
U2000
NOTE
Procedure
Step 1 Open the historical performance data window.
72
2
1
instance.
Step 2 View historical performance data.
----End
4.8 Report Query
This section describes operations related to report query. You can obtain network information
from reports.
4.8.1 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 Query the microwave link information report.
73
1
2
Select the desired
NEs.
3
4
6
(Optional) Output the link report.
5
7
----End
4.8.2 Querying the Network-wide License Report
By querying the network-wide license report, you can check the license information of each NE.
Prerequisites
U2000
NOTE
Procedure
Step 1 Query the license capacity report of NEs.
74
1
2
Select the desired
NEs.
3
4
(Optional) Output the microwave
capacity report.
5
6
Step 2 Query the air-interface license capacity report of the network.
75
1
2
3
4
(Optional) Output the air-interface
capacity report.
----End
4.8.3 Querying the Microwave Configuration Report
You can output the configuration report into an XLS file.
Prerequisites
U2000
NOTE
Procedure
Step 1 Export the microwave configuration report of an RTN NE.
76
1
2
Select the desired NEs. You
can also click the icon in the
red circle to quickly locate
desired NEs.
3
Select the types of
configuration data to be
exported.
4
Specify the directory for
saving the report.
5
----End
4.8.4 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
NOTE
Procedure
Step 1 Open the board information query window.
77
1
2
Set Physical
Inventory Type to
Board.
3
4
78
Select the
desired NEs.
7
5
6
Specify filter conditions. For
example, you can filter board
information by NE.
8
9
Step 3 View query results.
79
(Optional) Output the board
information report.
10
NOTE
Complete the following steps to query the board information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Information Report from the Function
Tree.
Version information of all boards is displayed in Board Information Report.
----End
4.8.5 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 Query the board manufacturing information report.
80
1
2
Select the desired
NEs.
3
4
(Optional) Output the board
manufacturing information report.
5
6
NOTE
Complete the following steps to query the board manufacturing information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Details Report from the Function Tree.
Manufacturing information of all boards is displayed in Board Details Report.
----End
4.8.6 Querying the ODU Information Report
You can query information about the ODUs on a network by querying the ODU information
report.
Prerequisites
U2000
Procedure
Step 1 Query ODU information.
81
(Optional) Output the ODU
information report.
1
2
3
4
----End
4.9 Alarm and Performance Management Setting
This section describes operations related to alarm and performance management.
Context
NOTE
The performance management in this section does not cover Ethernet performance
4.9.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
U2000
NOTE
82
Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance Monitoring
Time from the main menu.
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. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
l You can specify the start time of the performance monitoring function, only after selecting 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
4.9.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
Tools, Instruments and Materials
U2000
83
NOTE
Procedure
Step 1 In the NE Explorer, select the desired object.
Step 2 Choose Alarm > Alarm Severity and Auto Reporting from the Function Tree.
Step 3 Select any items in the column Event and set Severity and Auto Reporting Status for them.
Step 4 Click Apply to save the settings.
Step 5 Close the dialog box that is displayed.
NOTE
----End
4.9.3 Suppressing Alarms for Monitored Objects
This section describes how to suppress specific alarms for a specific monitored object.
Prerequisites
U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
84
Step 3 Set Monitored Object and click Query.
Step 4 Set Status in Alarm Suppression.
Step 5 Click Apply.
NOTE
----End
4.9.4 Suppressing Alarms for NEs
This section describes how to suppress certain alarms for NEs.
Prerequisites
U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
85
Step 3 Set Status in Alarm Suppression.
Step 4 Click Apply.
NOTE
----End
4.9.5 Reversing Alarms for Service Ports
This section describes how to reverse alarms for service ports.
Prerequisites
U2000
NOTE
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.
Step 3 Set Alarm Reversion to Enable (Manually Restore).
Step 4 Click Apply.
NOTE
Step 7 Choose Alarm > Alarm Reversion from the Function Tree.
Step 8 Set Reversion Status for the required port.
86
Step 9 Click Apply.
NOTE
----End
4.9.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
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > AIS Insertion from the Function Tree.
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.
Step 4 Click Apply.
NOTE
----End
4.9.7 Setting Trigger Conditions of UNEQ Insertion
This section describes how to set the trigger conditions of UNEQ insertion for service ports.
Prerequisites
87
U2000
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > UNEQ Insertion Switch from the Function Tree.
Step 3 Set the trigger conditions of UNEQ insertion. If you select Enabled under an alarm, the UNEQ
signal (all 0s) is inserted when this alarm occurs; otherwise, the UNEQ signal is not inserted
when this alarm occurs.
Step 4 Click Apply.
NOTE
----End
4.9.8 Setting Bit Error Thresholds for Service Ports
This section describes how to set bit error thresholds for service ports.
Prerequisites
U2000
NOTE
Procedure
Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.
Step 3 Set bit error thresholds.
88
Step 4 Click Apply.
NOTE
----End
4.9.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
NOTE
Procedure
Step 2 Choose Performance > Performance Monitor Status from the Function Tree.
Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-
Report.
89
Step 4 Click Apply.
NOTE
----End
4.9.10 Setting Performance Thresholds
This section describes how to set the thresholds of specific performance events for monitored
objects.
Prerequisites
U2000
NOTE
Procedure
Step 2 Choose Performance > Performance Threshold from the Function Tree.
Step 3 Set Threshold Value.
Step 4 Click Apply.
----End
4.9.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
90
U2000
NOTE
Procedure
Step 2 Choose Performance > Reset Board Performance Register from the Function Tree.
Step 3 Set Monitored Object and register types.
Step 4 Click Reset.
Step 5 In the Hint dialog box that is displayed, click Yes.
----End
91
5 Troubleshooting
About This Chapter
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.
Maintenance Guide 5 Troubleshooting
92
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 L3VPN Services
L3VPN service faults means that services are unavailable after the L3VPN function is
configured. This section describes how to troubleshoot L3VPN services.
5.15 Troubleshooting DCN Faults
A data communication network (DCN) fault causes an NE to be unreachable due to failed or
unstable communications between the NE and the NMS.
5.16 Troubleshooting Orderwire Faults
If orderwire calls cannot get through when services are normal, there is an orderwire fault.
5.17 Typical Cases
This section describes typical microwave link troubleshooting cases.
93
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.
94
General Troubleshooting Procedure
Figure 5-1 General troubleshooting procedure
Start
Record the fault phenomena
Analyze fault causes and locate
the fault
Is the fault
rectified?
Report to Huawei
Make a solution together
Attempt to rectify the fault
Is the service restored?
Observe the operation
Is the fault
rectified?
Fill in the troubleshooting
report
End
Other troubleshooting
procedures
No
Yes
Yes
Yes
No
No
No
Caused by external factors?
Yes
4
3
2
1
95

Table 5-1 General troubleshooting procedure
Comment
No.
Description
1 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 click-
to-collect function on the NMS to collect data.
2 Faults owing to external factors, including the power supply, cables,
environment, and terminal equipment (such as switch devices)
3 Determine the fault type according to preliminary analysis on alarms. Handle
different types of faults as follows:
l 5.2 Troubleshooting Service Interruptions
l 5.3 Troubleshooting the Radio Link
l 5.4 Troubleshooting Bit Errors in TDM Services
l 5.5 Troubleshooting Pointer Justifications
l 5.6 Troubleshooting the Interconnection with SDH Equipment
l 5.7 Troubleshooting the Interconnection with PDH Equipment
l 5.8 Troubleshooting Native Ethernet Service Faults
l 5.9 Troubleshooting Ethernet Service on the EoS/EoPDH Plane
l 5.10 Troubleshooting MPLS Tunnels
l 5.11 Troubleshooting CES Services
l 5.12 Troubleshooting ATM Services
l 5.13 Troubleshooting Ethernet Services Carried by PWs
l 5.15 Troubleshooting DCN Faults
l 5.16 Troubleshooting Orderwire Faults
l 5.14 Troubleshooting L3VPN Services
4 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.

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.
96
The configuration data changes, the loopback is performed, the cable is replaced, or the
board is replaced.
l The transmission NE or link is faulty.
l The interconnection is improper.
If the transmission equipment functions normally and the connection is normal, check
whether the interconnection between the transmission equipment is proper and whether the
switch equipment is faulty.
Fault Locating Methods
1. Check the operations before the service interruption to determine whether the service
interruption results from an incorrect operation.
2. Query alarms on the centralized NMS or the NMS that is used on the site, and then locate
the fault based on the alarm analysis.
If multiple NEs report alarms, analyze the alarms in the following order: equipment alarm,
line alarm, higher order path alarm, and lower order path alarm.
3. If the fault cannot be located through the alarm analysis method, locate the fault by
performing loopback section by section or replacing the corresponding parts.
NOTICE
If the fault cannot be rectified immediately, restore the services quickly by adjusting the service
route or performing a forced switching.
Troubleshooting Procedure
Handle the fault by following the emergency maintenance process.
97
Figure 5-2 Description of the general procedure
Start
Service interruoted by
external causes?
Yes
No
NE access successful and
alaarms cleared?
Query NE status and
alarms by using the NMS
Yes
Clear the alarm
No
Rectify the fault on site
Is there an incorrect
operation?
Cancel the operation
1
Yes
No
Is the service restored?
Contact Huawei engineers
No
Proceed with the next step
Is the service
restored?
No
End
Yes
Check the troubleshooting result
5
4
Yes
2
3
Contact related departments
to handle the problem

98
Table 5-2 Description of the main procedure
Comment
No.
Description
1 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 Faults owing to external factors, including the power supply, cables,
environment, and terminal equipment (such as switch devices)
3 The procedure is as follows:
1. Check the NE status.
2. If the NE is unreachable to the NMS, perform field troubleshooting
according to Figure 5-3. If alarms are reported on the NE, browse the
current alarms.
4 Generally, the following alarms can be cleared on the NMS:
l APS_MANUAL_STOP, APS_FAIL
l ETH_APS_LOST
l BD_NOT_INSTALLED, DBMS_ERROR, NESOFT_MM,
NESF_LOST
l ETH_APS_SWITCH_FAIL, ETH_APS_TYPE_MISMATCH
l HP_TIM, HP_UNEQ
l IMA_GROUP_LE_DOWN, IMA_GROUP_RE_DOWN
l LOOP_ALM
l J0_MM
l LPS_UNI_BI_M
l LP_SLM, LP_TIM, LP_UNEQ
l RADIO_MUTE
l MW_CFG_MISMATCH
l WRG_BD_TYPE
l ETH_CFM_UNEXPERI, ETH_EFM_LOOPBACK
99
Comment
No.
Description
5 After the fault is rectified, proceed as follows:
1. Check the alarms, and ensure that the system is running properly.
2. Assign personnel to monitor the operation of the system during the peak
service hour, ensuring that subsequent faults can be handled in time.
3. Fill in the field maintenance operation sheet, record the fault symptoms
and troubleshooting results, and then send them to Huawei. Table 2 shows
the field maintenance operation sheet.

100
Figure 5-3 Field troubleshooting sub-procedure
Equipment
alarm?
3
No
4
Yes
Clear the alarm
Yes
Clear the alarm
No
5
Yes
Clear the alarm
No
6
Yes
Clear the alarm
No
End
Proceed to the next
step
Is the service
restored?
Yes
No
Start
Obvious equipment
damage?
Yes
Repair or replace
the equipment
No Troubleshoot the
power input
Browse alarms
locally by using the
LCT
2
1
No
Yes
Troubleshoot the
inter-connection
faulty
Locate the fault by
performing loopback
operations section by
section
7
Yes
Troubleshoot the
packet service fault
8
Radio link
alarm?
No
Yes
Is the PWR indicator
on the PIU on?
High order
path alarm?
Low order
path alarm?
Faulty inter-
connection with
SDH/PDH equipment?
Packet service
fault?
No

101
Table 5-3 Description of the field troubleshooting sub-procedure
Comment
No.
Description
1 The troubleshooting procedure is as follows:
1. Check whether the circuit breaker for the input power is off. If the circuit
breaker is automatically turned off, find the cause (such as short 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.
1. Logging In to the Web LCT (Through NMS Interface).
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.
3 Pay special attention to the following alarms:
l HARD_BAD, BD_STATUS, FAN_FAIL
l NESF_LOST
l POWER_ALM, TEMP_ALARM
l RADIO_TSL_HIGH, RADIO_TSL_LOW
l IF_INPWR_ABN, IF_CABLE_OPEN
l VOLT_LOS
102
Comment
No.
Description
l PG_LINK_FAIL, PG_PRT_DEGRADED
l MW_LIM, MW_LOF
l MW_BER_EXC
l RADIO_RSL_HIGH, RADIO_RSL_LOW
l R_LOS, R_LOF, R_LOC
l MS_AIS
l AU_AIS, AU_LOP
l B1_EXC, B2_EXC
l HP_LOM, HP_UNEQ
l B3_EXC
l T_ALOS
l E1_LOC
l LP_UNEQ
l TU_AIS, TU_LOP
l BIP_EXC
7 See Troubleshooting the Interconnection with SDH Equipment or
Troubleshooting the Interconnection with PDH Equipment.
8 See Troubleshooting Native Ethernet Service Faults, Troubleshooting
Ethernet Service on the EoS/EoPDH Plane, Troubleshooting CES
Services, Troubleshooting ATM Services, Troubleshooting L3VPN
Services, and 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.
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:
103
l Equipment faults, including outdoor component faults, cable faults, and power supply faults
l Propagation faults, including fading, interference, and poor line of sight (LOS)
l Poor construction quality, including poor antenna/component installation, poor grounding,
and poor waterproofing
Figure 5-4 Radio link faults
Hardware
Faults
Causes of radio
link faults
Propagation
faults
Interference
Fading
Poor LOS
External
interference
Over-reach
interference
Rain
fading
Multipath
fading
Reflection
LOS not
achieved
Near-field
blocking
Poor construction
quality
Antenna
installation
Cables
Antennas
not aligned
Antennas
loosened or
offset
Poor
grounding
Poor
waterproofing
Equipment
faults
Power
faults
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 Fading Phenomena Fading Cause
Classifie
d by RSL
Down
fading
The RSL is lower than the RSL
after free space fading. The
difference can be tens of
decibels.
l Multi-path fading
l Duct-type fading
l Rain fading
Up
fading
The RSL is higher than the RSL
in the free space. The difference
can be 10-odd decibels.
l Interference
l Long delay caused by terrain
reflection
104
Fading Type Fading Phenomena Fading Cause
Classifie
d by
fading
duration
Fast
fading
The fading lasts from several
milliseconds to tens of seconds.
Generally, fast fading is caused
by multipath fading. It occurs
periodically. To be specific, fast
fading occurs in the period from
18:00 to 20:00 of a day or in a
certain season of a year.
l Multi-path fading
l Duct-type fading
l Long delay caused by terrain
reflection
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.

105
Figure 5-5 Procedure for troubleshooting the radio link
Start
RSL greater than the
receiver sensitivity?
Is there an
incorrect operation?
Undo the operation.
Yes
1
2
3
4
5
6
7
8
9
End
Hardware
alarms exist?
Rectify equipment faults.
Co-channel or adjacent-
channel interference
Long delay caused
by terrain reflection
The link is blocked.
The antennas are offset.
Passive components like
hybrid couplers or flexible
waveguides are faulty.
Rain fading
Multipath fading
Terrain reflection
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
Is the RSL value
always less than the
designed value?
Analyze the historical RSL
records and the current
RSL value
Are there IF or RF
alarms on the link?
Troubleshoot the fault as
a non-radio link fault.
Does the fault occur
regularly?
Troubleshoot the fault by
replacing the suspected
faulty parts.
Is the fault rectified?
Is it raining when the
fault occurs?

106
Table 5-5 Description of the procedure for troubleshooting the radio link
Mark Description
1 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
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_BEYONDTH
l AM_DOWNSHIFT
4 RSL is the major reference for locating and handling propagation faults. Follow
instructions in 4.4.3 Browsing Current Performance Events of the radio link
and 4.4.4 Browsing Historical Performance Data of a Radio Link to browse and
analyze the historical RSL records and the current RSL value.
107
Mark Description
5 l If the receive power fluctuates within a range less than 10 dB, mute the opposite
NE and check the RSL at the local NE.
After the opposite NE is muted, if the RSL value is greater than -90 dBm, there
may be co-channel interference that affects long-term availability and error-
second performance of the system.
1. Follow instructions in 8.1.2 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.
l 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.
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.
6 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.
108
Mark Description
7 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.
8 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.
9 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 During the commissioning, ensure that the antenna is aligned properly, to prevent possible
incipient faults.
109
l Periodically collect and analyze the data about the changes in the transmit power and receive
power so that you can detect and then rectify the incipient faults accordingly in time.
5.4 Troubleshooting Bit Errors in TDM 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
Table 5-6 Bit errors
Bit Error
Type
Description Related Alarm and Performance Event
IF bit errors Refer to the bit errors that the
IF board detects through the
self-defined overhead byte in
the microwave frame
l MW_BER_EXC, MW_BER_SD
l IF_BBE, IF_ES, IF_SES, IF_CSES,
IF_UAS
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
l B1_EXC, B1_SD
l RS_CROSSTR
l RSBBE, RSES, RSSES, RSCSES,
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.
MS bit errors Refer to the bit errors that the
line board detects through the
B2 byte in the MS overhead
l B2_EXC, B2_SD
l MS_CROSSTR
l MSBBE, MSES, MSSES, MSCSES,
MSUAS
HP bit errors Refer to the bit errors that the
line board detects through the
B2 byte in the MS overhead
l B3_EXC, B3_SD
l HP_CROSSTR
l HPBBE, HPES, HPSES, HPCSES,
HPUAS
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
l BIP_EXC, BIP_SD
l LP_CROSSTR
l LPBBE, LPES, LPSES, LPCSES,
LPUAS

110
Fault Causes
Table 5-7 Causes of bit errors
Fault Common Fault Cause
There are IF bit errors. l The radio link is faulty.
Check whether the MW_BER_EXC, MW_BER_SD,
MW_FEC_UNCOR, MW_LOF or RPS_INDI alarm 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.
There are not any RS
bit errors but there are
MS bit errors or HP bit
errors.
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 cross-connect 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.)

111
1. Analyze the equipment alarms and performance events that are related to service
configuration errors and bit errors.
2. When there are many types of alarms and performance events on a service path, first analyze
RS bit errors, then MS bit errors, HP bit errors, and finally LP bit errors.
3. When multiple paths have bit errors, first check whether the overlapping part of the service
paths is faulty.
4. If you fail to locate the fault by analyzing the alarms and performance events, perform
loopback operations section by section.
5. Replace the parts whose performance may deteriorate with new ones.
112
Figure 5-6 Procedure for troubleshooting bit errors
Start
Is there an
equipment alarm?
No
Yes
Clear the alarm
Is there an
RS bit error alarm or a
performance
event?
Yes
Troubleshoot RS bit errors
on the IF board
No
Is there an
MS/ HP alarm or
performance
event?
Yes Troubleshoot MS/HP bit
errors
No
Is there an LP
alarm?
Yes Troubleshoot LP bit
errors
Locate the fault by performing
loopback operations section
by section
No
Is the fault
rectified?
End
Yes
No
Is there a pointer
justification event?
Yes
Troubleshoot the pointer
justification
No
If the
alarming
board is
Troubleshoot RS bit errors
on the SDH optical interface
board
IF board
SDH optical
interface board
2
3
4
5
6
1

113
Table 5-8 Description of the procedure for troubleshooting bit errors
Comment
No.
Description
l TEMP_ALARM
l HARD_BAD
2 See 5.5 Troubleshooting Pointer Justifications.
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.
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.
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.
114
Comment
No.
Description
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 During the routine maintenance, check bit error performance events periodically and handle
them in time.
l To locate a fault, prefer the method of analyzing alarms and performance events to 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 AUPJCHIGH
l AUPJCLOW
l AUPJCNEW
NOTE
The AU pointer justification is made at an upstream NE but is detected and reported at a downstream NE.
When the service is configured to be at the VC-12 level, apply the reframing process to 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 TUPJCHIGH
l TUPJCLOW
l TUPJCNEW
115
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.
Fault Causes
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.
l The fiber connections are incorrect. As a result, a timing loop occurs.
l The quality of the clock source declines, the clock unit is faulty, or there are other clock-
related faults.
l The tributary board is faulty (only for the TU pointer justification).
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 Fault Locating Method
AU pointer justification 1. Analyze and clear clock alarms.
2. Rectify the incorrect data configuration and incorrect fiber
connections.
3. Change the clock configuration to locate the station whose
clock is 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.

116
Figure 5-7 Procedure for troubleshooting pointer justifications
Start
Is there a clock-related
alarm?
No
Yes
Clear the alarm
Incorrect fiber
connection?
Yes
Reconnect the fibers
No
An AU pointer
Yes
No
A TU pointer
Yes
Proceed with the
next step
End
Yes
No
Incorrect
configuration?
Modify the data
configuration
No
Check the clock
configuration
Yes
Check the fiber
connection
Locate the faulty board
Locate the NE whose clock
is out of synchronization
Locate the faulty board
Locate the NE whose clock
is out of synchronization
No
1
2
3
4
6
5
7

117
Table 5-9 Description of the procedure for troubleshooting pointer justifications
Comment
No.
Description
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.
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.
118
Comment
No.
Description
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.
7 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.
119
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 The overhead bytes at both ends are inconsistent.
l The indexes of the SDH interfaces do not meet the requirements.
NOTE
In the case of interconnection with ATM or Ethernet equipment, the common cause for an 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.
120
Figure 5-8 Procedure for troubleshooting the interconnection with SDH equipment
Start
Is the
interconnected equipment
the ATM/IP equipment?
No
Yes
Set the interconnection
service to be the VC-4 pass-
through service
Is there an overhead
setting related alarm?
Yes
Handle the alarm
No
Is the interface the
STM-1 electrical
interface?
Yes
No
Go to the next
step
Is the fault cleared?
End
Yes
No
Is the
numbering mode the
line numbering?
Modify the data configuration.
Use the line numbering
method to set the VC-12
No
Query the VC-12 numbering
method of the interconnected
equipment
Yes
1
Check the grounding
2
Test the indexes of interfaces
Do the interfaces meet
relevant standards?
Handle the faults of the local
equipment
Handle the faults of the
Yes
No
3

121
Table 5-10 Description of the procedure for troubleshooting the interconnection with SDH
equipment
Comment
No.
Description
l J0_MM
l HP_TIM
l LP_TIM
l HP_SLM
l LP_SLM
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.
3 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 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.
122
5.7 Troubleshooting the Interconnection with PDH
Equipment
An interconnection fault occurs when the NE fails in transmitting PDH services with other PDH
equipment.
Fault Causes
l There is an impedance mismatch between interfaces.
l The equipment is not grounded properly.
l The cable performance deteriorates.
l The indexes of the PDH interfaces do not meet the requirements.
Analyze the fault phenomena and alarms that are generated on the equipment. Check the possible
fault causes one after another.
123
Figure 5-9 Procedure for troubleshooting the interconnection with PDH equipment
Start
Is there an
impedance mismatch?
Yes
Replace the cable or the
tributary board
Check the cables.
Is in good conditions?
No
Yes
Proceed with the next step. Is the fault rectified?
End
Yes
No
Is the cable a
coaxial cable?
No
Check the impedance of
the interfaces.
Yes
Adjust the cables.
Test the indexes of
Interfaces.
Do the interfaces
meet standards?
Troubleshoot the faults
on the local equipment.
Troubleshoot the faults on
the interconnected
Equipment.
Yes
No
Check the grounding.
No
1
2
3
4

124
Table 5-11 Description of the procedure for troubleshooting the interconnection with PDH
equipment
Comment
No.
Description
1 Check the impedance of the E1 path. Ensure that the impedance of the E1
path is consistent with the cable type.
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.
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.
4 Check the following indexes:
l Input jitter tolerance
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.
125
5.8 Troubleshooting Native Ethernet Service Faults
An Ethernet service fault may be the Ethernet service interruption or Ethernet service
deterioration.
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-12 Common faults of Ethernet services
Symptom Alarm
Ethernet
services are
interrupted.
Hardware
alarms
Such as HARD_BAD, TEMP_ALARM,
WRG_BD_TYPE, BD_STATUS, COMMUN_FAIL,
and LASER_MOD_ERR.
Link alarms Such as ETH_LOS, ETH_LINK_DOWN,
ETH_EFM_LOOPBACK, LOOP_ALM,
PORTMODE_MISMATCH, and LAG_DOWN.
Service alarms Such as ETH_CFM_AIS, ETH_CFM_LCO, and
ETH_NO_FLOW.
Radio link
alarms
Such as MW_LOF, MW_LIM.
Ethernet
services suffer
degradation.
Hardware
alarms
Such as HARD_BAD, and TEMP_ALARM.
Link alarms Such as PORTMODE_MISMATCH, and
LAG_MEMBER_DOWN.
Service alarms Such as FLOW_OVER, MAC_EXT_EXC,
MAC_FCS_EXC, and DROPRATIO_OVER.
Radio link
alarms
Such as AM_DOWNSHIFT, MW_BER_EXC, and
MW_BER_SD.

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
126
The service configuration is incorrect.
l The equipment at the local end is faulty.
l The line board is faulty or has bit errors.
l A LAG or PLA group has faulty member links, resulting in decreased Ethernet bandwidth.
l When the AM function is enabled, the Ethernet service bandwidth decreases due to the
downward AM switch.
l The interconnected equipment is faulty.
l The network cable is faulty.
l External electromagnetic interference is severe.
1. Rectify the human-caused faults such as a loopback and a data configuration error.
2. Locate the fault cause according to the equipment alarms.
3. Locate the fault cause according to the RMON performance events and alarms.
127
Troubleshooting Ethernet Services Configured on a Per NE Basis
Figure 5-10 Procedure for troubleshooting Ethernet services configured on a per NE basis
Any abnormal
RMON performance
events?
Clear the alarm
6
No
Yes
An equipment
alarm or alarm on
the radio link?
An Ethernet alarm?
Yes
No
Yes
Troubleshoot the fault
according to the flow of
handling RMON
performance events
3
2
Troubleshoot equipment
faults by performing
loopbacks section by
section or replacing boards
Proceed
with the
next step
Is the fault
rectified?
End
Yes
No
A loop formed by
the E-LAN service
trails?
No
No
Yes
Release the loop
Start
Incorrect operation?
1
Cancel this operation
No
Yes
44
3
2
1
Query the port and service
traffic and analyze the fault
causes
Clear the alarm
5
No

128
Table 5-13 Description of the procedure for troubleshooting Ethernet services configured on a
per NE basis
Comment
No.
Description
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, FAN_FAIL, HARD_BAD, BD_STATUS,
TEMP_ALARM
l NESF_LOST
l IF_INPWR_ABN
Pay special attention to the following line alarms:
l MW_LIM
l MW_LOF
l MW_RDI
l ETH_LOS
l ETH_NO_FLOW
l LAG_DOWN, 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.
129
Comment
No.
Description
5 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.
6 For RMON performance events, see the C RMON Event Reference.

130
Figure 5-11 Procedure for troubleshooting an RMON performance event
Is it a MTU setting
problem?
Yes
Modify the MTU
value
No
Proceed with
the next step
Is the fault
rectified?
End
Yes
No
No
Is the test passed?
No
Yes
Use a meter to perform the test
Rectify the fault of the
Rectify the equipment fault by
loopback section by section or
replacing the board
5
Are broadcast packets
excessive?
No
Yes Handle the problem on
excessive broadcast
packets
4
Start
Rectify the fault of line bit
errors
No
Yes
Is there any FCS error?
Is there any collision
or fragment?
Yes
Check the working mode
of the port
2
3
View the statistics group
performance on an Ethernet port
1

Table 5-14 Description of the procedure for troubleshooting an RMON performance event
No. Description
1 4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization to
obtain the real-time performance statistics data of the Ethernet port.
131
No. Description
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.
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.)
4 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.
5 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.

132
Troubleshooting Ethernet Services Configured in an End-to-End Manner
Figure 5-12 Procedure for troubleshooting faults in Ethernet services configured in an end-to-
end manner
Success
Troubleshoot according to the
relevant handling suggestions.
Refer to the procedure for
troubleshooting Ethernet
services configured on a per
NE basis.
Proceed with the
next step.
End
Yes
No
Start
1
Cancel this operation.
No
Yes
Failure
2
Perform intelligent
diagnosis on Ethernet
services.

Table 5-15 Description of the procedure for troubleshooting Ethernet services configured in an
end-to-end manner
Comment
No.
Description
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.

133
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.
Symptom Alarm Board
Ethernet
services are
interrupted.
HARD_BAD, TEMP_ALARM,
WRG_BD_TYPE, or BD_STATUS
EMS6/EFP8
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

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
134
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 The equipment at the local end is faulty.
l The line board is faulty or has bit errors.
l The interconnected equipment is faulty.
l The network cable is faulty.
l The external electromagnetic interference is severe.
1. Rectify the human-caused faults such as a loopback and a data configuration error.
2. Locate the fault cause according to the equipment alarms.
3. Locate the fault cause according to the RMON performance events and alarms.
135
Figure 5-13 Procedure for troubleshooting Ethernet service faults
Any abnormal
RMON performance
events?
Clear the alarm
5
No
Yes
An equipment alarm
or alarm on the radio
link?
An Ethernet
alarm?
Yes
Query the port and service
traffic and analyze the fault
causes
No
Fault on the
opposite
equipment?
Yes
Troubleshoot the fault according
to the flow of handling RMON
performance events
Yes
Troubleshoot faults on the
opposite equipment
No
3
2
Troubleshoot equipment
faults by performing
loopbacks section by
section or replacing boards
Proceed
with the
next step
Is the fault
rectified?
En
d
Yes
No
A loop formed by the
E-LAN service trails?
No
No
Yes
Release the loop
Start
1
Cancel this operation
No
Yes
Clear the alarm
4
5
4
3
2
1

136
Table 5-17 Description of the procedure for troubleshooting Ethernet service faults
Comment
No.
Description
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.
l POWER_ALM
l FAN_FAIL
l HARD_BAD
l BD_STATUS
l NESF_LOST
l TEMP_ALARM
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l IF_INPWR_ABN
l 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
137
Comment
No.
Description
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
4 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.
5 For RMON performance events, see B Performance Event Reference.

138
Figure 5-14 Procedure for troubleshooting an RMON performance event
Start
Rectify the fault of line bit
errors
No
Yes
Is there any FCS error?
Is there any collision
or fragment?
Yes
Check the working mode
of the port
Is it a MTU setting
problem?
Yes
Modify the MTU value
No
2
Proceed with
the next step
Is the fault
rectified?
End
Yes
No
Is there any
PAUSE frame?
3
No
No
Yes
Handle the flow control
problem or increase the
bandwidth
View the statistics group
performance on an Ethernet port
Is the test passed?
No
Yes
Use a meter to perform the test
Rectify the fault of the
Rectify the equipment fault by
loopback section by section or
replacing the board
1
4
6
Are broadcast packets
excessive?
No
Yes Handle the problem on
excessive broadcast
packets
5

Table 5-18 Description of the procedure for troubleshooting an RMON performance event
Comment
No.
Description
1 View the statistics group performance on an Ethernet port to obtain the
real-time performance statistics data of the Ethernet port.
139
Comment
No.
Description
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.
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.)
l Whether the flow control method is the same.
l Whether the Ethernet service traffic exceeds the bandwidth of the
VCTRUNK.
5 Check for the cause for excessive broadcast packets (for example, you 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.
6 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.
140
Fault Phenomena
NOTE
In this section, an MPLS tunnel refers to a static label switched path (LSP).
Common faults of MPLS tunnels are as follows:
l MPLS tunnels fail to be created, and services are unavailable.
l MPLS tunnels are faulty, and services are interrupted.
l MPLS APS switching fails, services are interrupted, and packet loss or bit errors occur.
Table 5-19 Common faults of MPLS tunnels
Symptom Alarm Board
MPLS
tunnels are
faulty.
WRG_BD_TYPE, BUS_ERR,
BD_STATUS, MPLS_TUNNEL_OAM-
FAIL, 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_UNEXPMEP,
MPLS_TUNNEL_UNEXPPER
CSH
MW_CFG_MISMATCH
MW_LIM
MW_LOF
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 The local NE is faulty.
l The transmission link is faulty or has bit errors.
l Service bandwidth decreases due to an AM downshift.
l The opposite NE is faulty.
141
1. Check whether the data is modified, whether the line is looped back, and whether any boards
are replaced.
2. Handle the link alarms on the MPLS server trail.
3. Locate the faulty section by using the LSP Traceroute or MPLS-TP OAM function.
4. Locate the fault by replacing boards.
Figure 5-15 Procedure for troubleshooting MPLS tunnels
Clear the alarm.
No
Yes
Yes
Troubleshoot equipment faults by
performing loopbacks on sections
or replacing boards.
Contact Huawei
technical engineers.
Faults are rectified?
End
Yes
No
Clear the alarm using
LB/LT/LSP Ping/LSP Tracerout.
Start
Any incorrect
operation?
Cancel the operation.
No
Yes
Any equipment- or
link-related alarm?
No
Any alarm related to MPLS
tunnel ?
Yes
Handle the fault.
No
Any fault in
interconnection
equipment?
3
2
1

142
Table 5-20 Description of the procedure for troubleshooting MPLS tunnels
Comment
No.
Description
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
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
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR
143
Comment
No.
Description
3 Check whether the tunnel is faulty using LSP Ping, LSP Tracerout, or MPLS-
TP 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-21 Common faults of CES services
Symptom Alarm Board
CES services
are
interrupted.
BD_STATUS, CES_LOSPKT_EXC
CSH, CSHU, CSHUA, ML1,
MD1, CQ1
144
Symptom Alarm Board
AM_DOWNSHIFT
MW_CFG_MISMATCH
ISV3, ISU2, ISX2, IFU2,
IFX2
CES services
are
degraded.
CES_JTROVR_EXC,
CES_JTRUDR_EXC,
CES_MALPKT_EXC,
CES_MISORDERPKT_EXC,
CES_STRAYPKT_EXC
MD1, CQ1
AM_DOWNSHIFT
MW_CFG_MISMATCH
IFX2

Fault Causes
l The clock source is asynchronous.
l Jitters and delays on the network are too great.
1. Check whether the data is modified, whether the line is looped back, and whether any boards
are replaced.
2. Check whether the PW works properly by using the PW ping function. If the PW is faulty,
check whether the MPLS tunnel works properly by using the LSP ping function. If 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.
3. If the PW works properly, check whether the PE data configured at both ends is the same.
If the PE data is different, change the PE data to the same.
4. Check whether UNI-side data and CE-side data are consistent.
5. Analyze the RMON performance events of CES services.
6. Check whether there is impedance mismatch on channels and whether any electrical cables
are connected incorrectly.
7. Replace Smart E1 interface boards.
145
Figure 5-16 Procedure for troubleshooting CES services
Clear the alarm
No
Yes
Yes
Yes
Clear the alarm
or replacing boards
Contact Huawei
technical engineers
End
Yes
No
Clear the alarm
Start
Any incorrect
operation?
No
Yes
Any equipment- or
link-related alarm?
No
No
Any alarm related to
tunnels/PWs?
Any alarm on E1
ports?
Yes
Handle the fault
No
Any fault of
interconnection with
PDH equipment
7
5
3
2
1
Yes
Handle the performance event
No
Any RMON
performance event?
6
Yes
Clear the alarm
Any alarm related to
CES services?
4

146
Table 5-22 Description of the procedure for troubleshooting CES services
Commen
t No.
Description
l Whether a loopback is set for the E1 port
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.
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
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR
147
Commen
t No.
Description
l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l CES_JTROVR_EXC
l CES_JTRUDR_EXC
l CES_LOSPKT_EXC
l CES_MALPKT_EXC
l CES_MISORDERPKT_EXC
l CES_STRAYPKT_EXC
l T_ALOS
l UP_E1_AIS
l LFA
l LMFA
l ALM_E1RAI
l CES_MISORDERPKT
l CES_LOSPKT
l CES_MALPKT
l CES_JTRUDR
l CES_JTROVR
l CES_STRAYPKT
7 Troubleshoot the interconnection with the PDH equipment.

148
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-23 Common faults of ATM services
Symptom Alarm Board
ATM
services are
interrupted.
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
MD1
AM_DOWNSHIFT
MW_CFG_MISMATCH
IFX2
ATM
services are
degraded.
ALM_IMA_LIF, ALM_IMA_LODS,
ALM_IMA_RE_RX_UNUSABLE,
ALM_IMA_RE_TX_UNUSABLE, OCD
MD1
AM_DOWNSHIFT
MW_CFG_MISMATCH
IFX2

Fault Causes
149
1. Check whether the data is modified, whether the link is looped back, and whether any
boards are replaced.
2. Check whether the PW works properly by using the PW ping function. If the PW is faulty,
check whether the MPLS tunnel works properly by using the LSP ping function. If 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.
5. Analyze the RMON performance events of ATM services.
7. Replace Smart E1 processing boards.
150
Figure 5-17 Procedure for troubleshooting ATM services
Clear the alarm
No
Yes
Yes
Yes
Clear the alarm
or replacing boards
Contact Huawei
technical engineers
End
Yes
No
Clear the alarm
Start
Any incorrect
operation?
No
Yes
Any equipment- or
link-related alarm?
No
No
Any alarm related to ATM
services?
Any alarm at the E1
port?
Yes
Handle the fault
No
Any fault of
interconnection with
PDH equipment
6
4
3
2
1
Yes
Handle the performance event
No
Any RMON
performance event?
5

151
Table 5-24 Description of the procedure for troubleshooting ATM services
Comment
No.
Description
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 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
l MW_LIM
l MW_LOF
l MW_BER_EXC
l MW_BER_SD
l MW_RDI
l MW_FEC_UNCOR
152
Comment
No.
Description
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
l T_ALOS
l UP_E1_AIS
l LFA
l LMFA
l ATMPW_UNKNOWNCELLS
l ATM_UNCORRECTED_HCSERR
6 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.
153
Symptom Alarm Board
Ethernet
services are
interrupted.
BD_STATUS
EG4, EG4P, EM6TA,
EM6FA, EM6F or EM6T
COMMUN_FAIL, LAG_DOWN
ETH_LOS, ETH_EFM_LOOPBACK, or
LOOP_ALM
LASER_MOD_ERR EG4, EG4P, EM6FA, EM6F
Ethernet
services
deteriorate.
HARD_BAD or TEMP_ALARM EG4, EG4P, EM6TA,
EM6FA, EM6F or EM6T
PORTMODE_MISMATCH, FLOW_OVER
or LAG_MEMBER_DOWN
MAC_FCS_EXC
MAC_EXT_EXC
DROPRATIO_OVER
EG4, EG4P, EM6TA,
EM6FA, EM6F or EM6T
AM_DOWNSHIFT
MAC_FCS_EXC
MAC_EXT_EXC
DROPRATIO_OVER
ISV3, ISU2, ISX2, IFU2 or
IFX2

Fault Causes
1. Check whether the data is modified, whether the link is looped back, and whether any
boards are replaced.
2. Check whether the PW works properly by using the PW ping 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
154
whether the PW has the same configuration at both ends. If the configuration is the same,
replace the boardon the NNI side.
5. Analyze the RMON performance events of Ethernet services.
7. Replace Ethernet interface board.
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
Clear the alarm.
No
Yes
Yes
Contact Huawei
technical engineers.
End
Yes
No
Clear the alarm.
Start
Any incorrect
operation?
Cancel the operation.
No
Yes
Any equipment-
or link-related
alarm?
No
3
2
1
Yes
Handle the tunnel fault.
No
Any fault in the tunnel
that carries the PW?
Incorrect PW
configuration?
6
Yes
Re-configure the PW.
Yes
Handle the UNI-side fault.
No
Can the PW be
pinged after a PW
ping test is enabled?
4
No
5
Analyze PW traffic.
7
Any PW-related
alarm?
155

Table 5-26 Description of the procedure for troubleshooting PW-carried Ethernet services
configured on a per NE basis
No. Description
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 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
156
No. Description
l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
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
157
No. Description
4 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
5 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 Check PW configurations. If the PW configurations are incorrect, re-
configure the PW according to the network plan.
7 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.

158
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
Success
Troubleshoot according to the
relevant handling suggestions.
Refer to the procedure for
troubleshooting Ethernet
services configured on a per
NE basis.
Proceed with the
next step.
End
Yes
No
Start
1
Cancel this operation.
No
Yes
Failure
2
Perform intelligent
diagnosis on Ethernet
services.

Table 5-27 Description of the procedure for troubleshooting Ethernet services configured in an
end-to-end manner
Comment
No.
Description
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.
159
5.14 Troubleshooting L3VPN Services
L3VPN service faults means that services are unavailable after the L3VPN function is
configured. This section describes how to troubleshoot L3VPN services.
Fault Causes
l Data configurations are incorrect.
VPN instance configurations are incorrect.
BGP configurations are incorrect.
IGP configurations are incorrect.
Tunnel configurations are incorrect.
Tunnel policy configurations are incorrect.
l Equipment is faulty.
The local microwave equipment is faulty.
The peer equipment is faulty.
l Links are faulty, or bit errors occur.
Fault Locating Method
1. Collect L3VPN-related alarms and analyze the causes. L3VPN-related alarms include
BGPBACKTRANSITION, GSP_RSVP_NB_AUTH_ERR,
GSP_RSVP_NB_DOWN, GSP_TNNL_DOWN, ISISADJACENCYCHANGE,
L3V_TRAP_THRE_EXCEED, L3V_TRAP_VRF_DOWN, and RT_TBL_LACK.
2. Check whether any alarms indicating Ethernet link, microwave link, or equipment faults
are reported. The following table lists these alarms.
Alarm Type Alarm
Alarms indicating Ethernet link faults ETH_LOS, ETH_NO_FLOW,
ETH_AUTO_LINK_DOWN,
ETH_PWR_SUPPLY_FAIL
Alarms indicating microwave link faults MW_LIM, MW_LOF,
MW_BER_EXC, MW_BER_SD,
MW_RDI, MW_FEC_UNCOR
Alarms indicating equipment faults POWER_ALM, FAN_FAIL,
HARD_BAD, BD_STATUS,
BUS_ERR, NESF_LOST,
TEMP_ALARM, RADIO_RSL_HIGH,
RADIO_RSL_LOW,
RADIO_TSL_HIGH,
RADIO_TSL_LOW,
IF_INPWR_ABN, IF_CABLE_OPEN

160
Troubleshooting Processes
L3VPN service troubleshooting processes include the traffic-related fault troubleshooting
process and the route-related fault troubleshooting process.
Start
Traffic-
related fault
Yes No
Route-
related fault
Does the local VPN
instance routing
table contain VPN
routes?
l Traffic-related fault troubleshooting process
161
Figure 5-20 Traffic-related fault troubleshooting process
Bind the VPN
with a tunnel
policy.
1
Tracert the VPN IP
address at the local
end to locate the
fault.
Yes
No
Yes
Correct the
tunnel policy.
No
Correct the tunnel
configurations.
Contact Huawei
technical
support.
No
Yes
Traffic-
related fault
Is the fault
rectified?
No
Yes
Yes
Is the fault
rectified?
No
Yes
Is the fault
rectified?
No
End
2
3
4
5
6
7
Is the tunnel
policy correct?
Is the VPN instance
bound with a tunnel
policy?
Use LSP Ping
to check whether the tunnel
where a service fault has
occurred is working
properly.
l Route-related fault troubleshooting process
162
Figure 5-21 Route-related fault troubleshooting process
Yes
No
Correct the VPN instance
configurations, such as RT.
No
Yes
Are the BGP
configurations
correct?
Correct the BGP
configurations.
Yes No
Rectify the fault.
No
Are the IGP
configurations
correct?
No
Correct the IGP
configurations.
No Yes
Enable the interfaces
and configure IP
addresses for them.
Yes No
Are the
Ethernet/
microwave links
faulty?
Rectify the link
faults.
Yes
Is the
equipment
faulty?
No
Rectify the
equipment fault.
Yes
No
Contact Huawei
technical
support.
Route-
related fault
End
Is the fault
rectified?
Is the fault
rectified?
Is the fault
rectified?
Is the fault
rectified?
No
Yes
No
Yes
No
Yes
No
Yes
3
1
2
4
5
6
7
8
9
Does the BGP routing
table contain VPN routes?
Does the IGP routing table
contain a route to the
peer?
Are the VPN
instance
configurations
correct?
Does the VPN instance
routing table on the peer
contain VPN routes?
Are interfaces enabled
or configured with IP
addresses?
Summary
Learn about the principles and protocol configuration of the L3VPN feature before
troubleshooting L3VPN services.
5.15 Troubleshooting DCN Faults
A data communication network (DCN) fault causes an NE to be unreachable due to failed or
unstable communications between the NE and the NMS.
Context
If links or lines that bear DCN channels, including data communication channels (DCCs) and
inband DCN channels, are faulty, the DCN communication is interrupted. In this case, handle
the fault in the same manner as a service fault. In other cases, the DCN communication between
an NE and the NMS is interrupted or unstable, but the services between them are normal for the
moment. This fault also needs to be rectified in time, otherwise, you will fail to check the NE
information, obtain NE alarms, or change NE configurations when the services become faulty.
163
Fault Symptoms and Causes
Table 5-28 Fault symptoms and causes
Symptom Possible Cause
NEs connected through their
service ports like air
interfaces and Ethernet ports
are unreachable to their
NMS.
l Cause 1: Services are interrupted.
l Cause 2: DCN parameters are incorrectly set.
l Cause 3: System control boards are faulty.
NEs connected through their
NMS ports are unreachable
to their NMS.
l Cause 1: The network cable of the NMS is disconnected
or damaged.
l Cause 3: System control boards are faulty.
A few NEs are unreachable
or their connection to the
NMS is unstable.
l Cause 2: An NE ID or NE IP address conflict occurs
between NEs on the DCN subnet.
l Cause 3: The DCN subnet is too large.
l Cause 4: The system control unit of the NE is faulty.

164
Figure 5-22 Procedure for troubleshooting DCN faults
Start
Icon of the faulty
NE in gray
Fault rectified
End
Contact Huawei technical
service engineers
SCC boards are
being reset
The NMS cannot
reach the NE
Yes
NM
Information
loss?
No response to
commands from the
NMS
Too low DCN
channel bandwidth
Increase the DCN
channel bandwidth
Wait for the completion
of SCC resetting
5
Locate a
faulty NE
1
6
NO
NO
Yes
Yes
NO
Yes
NO
Yes
Yes
Yes
NO
Hardware
fault?
Settings
incorrectly
modified?
Large DCN
subnet?
2
3
4
Check settings
or undo
modifications
Check for hardware
alarms and check
cable connections
Divide the DCN
subnet

165
Table 5-29 Procedure description for troubleshooting DCN faults
Mark Operation Typical Symptom Measures
1 Locate the faulty
NE.
Locate the faulty NE
based on a DCN
networking diagram.
l If all NEs within an
area are unreachable to
their NMS, the
unreachable NE
closest to a normal NE
is probably the faulty
NE.
l If only one NE is
unreachable to its
NMS, the NE is the
faulty NE.
l If the faulty NE has a service fault, rectify the service
fault first.
l If an unreachable NE connects to its NMS through
an external DCN, verify that the external DCN
equipment or the cable used for DCN connection is
working correctly.
2 Handle
hardware faults.
l The faulty NE reports
hardware alarms like
HARD_BAD.
l Check whether the
NMS/COM port on the
faulty NE is connected
to a correct cable or
whether the network
cable of the faulty NE
is damaged.
l Handle hardware alarms based on the maintenance
and fault management procedure.
l Remove and then install, or replace the network
cable and optical fibers.
166
3 Modify
incorrect
configurations.
The following operations
are performed before a
faulty NE becomes
unreachable to its NMS:
l Modifying NE
attributes or NE
communication
settings
l Adding a new NE to
the network, or
replacing the faulty NE
or its system control
board
l Check for unplanned NE IDs and NE IP addresses
in the ECC routing table of the faulty NE's upstream
NE. If there is an unplanned NE ID or IP address in
the ECC routing table, the faulty NE is incorrectly
configured. To rectify the fault, log in to the faulty
NE using the unplanned NE ID and NE IP address
on the NMS and correct the settings.
l Change the DCC settings or inband DCN settings of
the faulty NE to interrupt the DCN channel between
the faulty NE and its upstream NE. Then, check for
the ID and IP address of the faulty NE in the ECC
routing table of the upstream NE. If the ID and IP
address of the faulty NE exist in the ECC routing
table of the upstream NE, another NE on the ECC
subnet has the same ID and IP address as the faulty
NE. In this case, correct the settings to ensure that
each NE on the ECC subnet has a unique ID and IP
address.
l If the inband DCN is enabled for the faulty NE and
its upstream NE, verify that the VLAN ID is
correctly set on the upstream NE.
l Verify that static routes are correctly set on the faulty
NE's upstream NE.
l Verify that OSPF parameters are correctly set on the
faulty NE's upstream NE. OSPF parameter settings
must be consistent for all NEs on the same ECC
subnet.
4 Analyze the
DCN subnet
size.
Check the number of NEs
in the IP routing table or
ECC routing table of the
faulty NE's upstream NE.
If there is a large number of NEs in the routing table,
the DCN subnet is too large in size and some NEs on
the DCN subnet may occasionally become unreachable
to their NMS. It is recommended that an DCN subnet
consist of no more than 120 NEs, if a 192 kbit/s
bandwidth is provided. If L2 DCN is used, an L2 DCN
subnet consists of not more than 30 NEs.
5 Troubleshoot
NMS
information
loss.
Some NEs may
occasionally become
unreachable to their NMS.
l Verify that a minimum of 192 kbit/s bandwidth is
allocated to the inband DCN. If the allocated
bandwidth is lower than 192 kbit/s, packets from the
NMS may be lost.
l Check whether the QoS priority allocated to the
inband DCN by a third-party network is high enough
if inband DCN packets are transmitted over the
third-party network. Lower QoS priority of inband
DCN packets may cause NEs unreachable to the
NMS due to congestive packet loss. The per-hop
behavior (PHB) priority of inband DCN packets
must not lower than expedited forwarding (EF).
167
6 Troubleshoot
no-response
problems.
l The NE fails to be
logged in to onsite.
l The NE does not
respond to commands.
l Search for the IP address of the faulty NE on the
NMS.
l If the IP address is not found, or if the IP address is
found but the NMS still cannot reach the faulty NE,
restart the OptiX RTN 950 after a power-off, in a
authorized maintenance window which service can
be interrupted.

5.16 Troubleshooting Orderwire Faults
If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Fault Causes
l The phone set is set incorrectly.
l The phone line is connected incorrectly.
l The orderwire is configured incorrectly.
l The orderwire unit is faulty.
l The system control unit is faulty.
l The line unit or radio link is faulty.
l Check whether the phone set is set correctly, whether the phone line is connected correctly,
and whether the orderwire is configured correctly.
l Replace the possibly faulty board to locate the fault.
168
Figure 5-23 Procedure for troubleshooting orderwire faults
Start
Is the phone
correctly set?
No
Modify the phone setting
Check the orderwire
configuration
Is the configuration
correct?
No
Yes
End
Yes
No
Is the phone line
correctly connected?
Yes
Check the phone setting
No
Modify the configuration
Replace the possibly faulty
board
Reconnect the phone line
Yes
3
2
1

169
Table 5-30 Description of the procedure for troubleshooting orderwire faults
Comment
No.
Description
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.
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.
5.17 Typical Cases
This section describes typical microwave link troubleshooting cases.
5.17.1 Transient Link Unavailability Due to Multi-path Fading
Fault Symptoms
A 20 km long cross-ocean 1+1 hot standby (HSB) radio link was interrupted intermittently, and
alarms such as B1_SD, HSB_INDI, MW_LOF, and R_LOF, were reported and lasted several
seconds to dozens of seconds.
170
Cause Analysis and Handling Procedure
1. Checked the ODU receive power that was recorded during the alarm period.
The difference between the maximum receive power and the minimum receive power was
more than 40 dB, and the minimum receive power was close to or less than the receiver
sensitivity. Therefore, it was inferred that the fault was caused by spatial fading.
2. Checked the network planning design.
The ODU operated at the 8 GHz band, which was less prone to rain fading, and therefore
multipath fading caused intermittent link interruptions. In addition, 1+1 HSB protection
does not well protect radio links against multipath fading.
3. Replaced 1+1 HSB protection with 1+1 space diversity (SD) protection.
Conclusions and Suggestions
l Routinely check whether the receive power reaches the designed value. If not, it is
recommended that you check the configuration, adjust antennas, or replace ODUs so the
receive power reaches the designed value.
l Minimize the impact of multipath fading by using one of the following methods, depending
on the actual conditions:
Use low capacity, low-order modulation schemes, and low bandwidths.
Increase the height difference between antennas at both ends providing that line-of-sight
(LOS) is guaranteed.
Add two antennas and configure an SD protection group.
171
5.17.2 Transoceanic Link Transient Unavailability Due to
Insufficient Height Difference between Diversity Antennas
Fault Symptoms
The received signal levels (RSLs) at both ends of a 1+1 SD cross-ocean radio link fluctuated
dramatically, leading to bit errors or even link interruptions.
1. Checked the alarms reported by NEs at both ends of the radio link.
The NEs did not report any hardware alarms but frequently reported radio link alarms and
service interruption alarms.
2. Checked the RSLs of the main and standby ODUs at each end.
The RSLs of the main and standby ODUs at each end fluctuated dramatically, with a
fluctuation range over 30 dB. Therefore, the fault was possibly caused by multipath fading.
3. Checked the network plans and the mounting height difference between the main and
standby antennas at each end.
The mounting height difference between the main and standby antennas at each end was
only 4 meters, so space diversity performance was poor.
NOTE
To protect long-distance cross-ocean radio links against multipath fading, take the following measures
during network planning:
l Ensure that the fading margin is greater than or equal to 30 dB.
l Increase the mounting height difference between the main and standby antennas at both ends of a 1
+1 SD radio link.
4. Adjusted the mounting heights of the main antennas to 24 meters and those of the standby
antennas to 10 meters.
The following figure shows the simulation result and illustrates satisfactory diversity
compensation.
NOTE
The value of K generally ranges from 0.67 to 1.33. In this case, the RSLs of the main and standby antennas
are not correlated with each other. When designing mounting heights for main and standby antennas, keep
appropriate antenna spacing for minimizing the impact of reflection on radio links. When reflection causes
high attenuation on the main path, the attenuation on the standby path is low.
172
When planning cross-ocean radio links, especially long-distance cross-ocean radio links, take
measures to minimize the impact of multipath fading. 1+1 SD protection is recommended for
these radio links. When mounting the main and standby antennas at one end, keep an appropriate
mounting height difference between them so attenuation has no impact on RSLs. In addition,
the main and standby antennas can be tilted slightly upwards providing that RSLs be not affected.
5.17.3 Link Unavailability Due to Inter-building Reflection
Fault Symptoms
On a 900-meter 1+0 microwave hop, IFX2 boards are used, working with 18 GHz HP ODUs,
at 28 MHz channel bandwidth and in 256QAM modulation, with XPIC disabled. One end of the
link continuously reports MW_LOF alarms and the other end reports MW_RDI alarms.
On this microwave hop, ODUs are mounted onto 0.3-meter diameter dual-polarized antennas
in separate-mount manner. Both ends of the radio hop are located on roofs. Antennas are installed
at the middle of poles about 5 meters high standing on the roofs.
1. The total hop spans only 900 meters. The receive power is ideal but the MSE is poor. The
faulty microwave link end is surrounded by many buildings, most of which have glass
walls. Therefore, it is suspected that some signals are reflected for many times between the
buildings before reaching the receive end or that some microwave signals are reflected
twice when traveling through the glass walls before reaching the receive end. See Figure
5-24.
Figure 5-24 Microwave link between buildings
Site A
Site B
Reflected signal
Main signal
2. To suppress signal reflection, do as follows:
173
l Change the pole position.
l Adjust the antenna elevation.
l Increase the antenna mount height.
l Use antennas with a larger diameter.
NOTE
Move poles near the building roof edges to decrease the inter-building reflection possibility or number of
reflection times. Generally, antennas can be adjusted upwards, downwards, leftwards, or rightwards.
During antenna adjustment, notice the MSE changes and ensure that the RSL is within its allowed range.
The larger the antenna diameter, the denser the beams. The smaller the beam angle at the receive end, the
powerful the capabilities to suppress reflection.
3. By means of the preceding methods, you can adjust the MSE values at both ends to be -30
dB to clear alarms.
The addressed problem is characterized by satisfactory receive power, poor MSE, and failure in
clearing alarms. To find out the cause, check whether the equipment hardware is faulty, whether
the equipment operates abnormally, and whether any exceptions occur on the path from an
antenna to an indoor unit (IDU). Then narrow down the cause on the space link, and determine
whether reflection and refraction are possible according to the topography.
5.17.4 Unidirectional Link Availability Due to Interference
Fault Symptoms
The1+0 link formed by NE A and NE B using IF1 board and 8G/HP ODU is available only in
one direction after the link is expanded from mode 5 (QPSK/28M/16E1) to mode 7 (128QAM/
28M/STM-1). The link is available only in one direction after the link is expanded from mode
5 (QPSK/28M/16E1) to mode 7 (128QAM/28M/STM-1).
1. The ODU supports 128QAM modulation scheme according to query results of NE data in
mode 7 and query of ODU product manual.
2. The receive power is unlikely to fade because the RSL is stable and the link is only 1.27
Km long.
3. The MSE values on the NE A are -35.35 dB and -34.57 dB in the mode 5 and the mode 7
respectively. The MSE values on the NE B are -26.77 dB and -20.56 dB in the mode 5 and
the mode 7 respectively. The MSE value on the NE B is greatly different from the required
modulation threshold from -24 dB to -35 dB in the mode 7. The modulation threshold of
the MSE value in the mode 7 is from -24 dB to -35 dB. When the link is normal, the MSE
value of NE B is also low. It is suspected that interference exists. Because the anti-
interference capability in QPSK modulation is more powerful than that in 128QAM
modulation, signal modulation is successful in QPSK modulation but fails in 128QAM
modulation.
4. Scan the frequency on the NE B to find out the interference source. Change the operating
frequency to eliminate interference.
174
For unidirectional link availability in case of modulation upshift, the possible causes are as
follows:
l The ODU cannot support the new IF mode of high modulation and of large capacity after
the link capacity is expanded.
l The link is interrupted because the receive power cannot meet the sensitivity requirement
in the new IF mode.
l The link is interrupted because the MSE value cannot reach the demodulation threshold
due to interference occurrence on the link.
Check the above items to prevent the link from being interrupted before the link capacity
expansion.
5.17.5 Bit Errors on Microwave Links
Fault Symptoms
Bit errors occurred in the services carried by a 2.5 km long radio link between NE A and NE B.
Both NEs used antennas with a diameter of 0.6 meters and 15 GHz ODUs. The IF1 boards on
both NEs worked in mode 5 (28 MHz/QPSK).
1. Checked the alarms and logs of the two NEs.
The NEs did not report any hardware alarm. NE A reported an MW_FEC_UNCOR alarm,
but NE B did not.
2. Checked the RSLs at the two NEs.
The RSL at NE A was 62 dBm and that at NE B was 70 dBm. These two values were
greater than the receiver sensitivity (85 dBm) in mode 5.
3. Checked for interference signals by muting the ODU at NE B.
The RSL at NE A was 80 dBm. Therefore, interference signals existed.
4. Used one of the following methods for eliminating interference signals:
l Using frequencies that are not affected by interference signals (tests showed that the
sub-bands supported by the ODU were all interfered)
l Using antennas with a diameter greater than 0.6 meters (the workload is heavy and
interference signals are also amplified)
l Changing a polarization direction (cross-polarization discrimination of 30 dB can be
achieved)
5. Changed the polarization direction of the radio link.
The fault was rectified.
If the RSL of an ODU is normal or apparently greater than the receiver sensitivity, frequent and
intermittent radio link interruptions or bit errors are generally caused by interference signals.
175
5.17.6 Poor Reliability Due to Network Planning Errors
Fault Symptoms
A radio link frequently but intermittently reported MW_RDI, R_LOC, and RPS_INDI alarms,
and HSB switchovers were triggered.
Table 5-31 Link information
Protection 1+1 HSB
IF board IF1B boards
IF mode IF mode 7 (28M/128QAM/STM-1)
ODU type SPA ODUs operating at the 8 GHz frequency
band
Receiver sensitivity 70.5 dBm
Transmit power 20 dBm
Receive power 39.5 dBm
Planned availability 99.994%
Predicted annual interruption time 1877 seconds

1. Queried historical receive power values of the radio link.
The receive power decreased to a value close to the receiver sensitivity when an alarm was
reported. Most alarms were reported during the night or in the early morning. When the
weather was favorable at noon, the receive power was normal. Therefore, intermittent radio
link interruptions were caused by multipath fading.
2. Checked annual interruption time predicted for the radio link.
The actual annual interruption time was longer than the predicted time of 1877 seconds.
Therefore, the fading margin was insufficient.
3. Checked the network planning methods.
The ITU-R-P.530-7/8 method was used. The area covered by the radio link was in the
Middle East, and therefore the ITU-R-P.530-9 method should be used.
4. Used the ITU-R-P.530-9 method to predict annual interruption time without changing other
conditions.
The obtained value was about 175833 seconds, which was longer than the value obtained
using the ITU-R-P.530-7/8 method.
176
Figure 5-25 Using the ITU-R-P.530-7/8 method
Figure 5-26 Using the ITU-R-P.530-9 method
5. Deleted 1+1 HSB protection settings and configured 1+1 SD protection. The link
availability met service requirements.
Network planning is crucial to radio link performance. For radio links that are frequently
interrupted due to fading, it is recommended that you first check their network planning
information.
177
6 Part Replacement
About This Chapter
Part replacement is a method frequently used to locate faults. The replacement operation varies
according to the specific part type.
Table 6-1 Part replacement description
Part Name Operation Tool
CQ1 6.4 Replacing the Channelized
STM-1 Processing Board
l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
SL1D, SL1DA 6.3 Replacing the SDH Optical
Interface Board
EG4, EG4P,
EM6T, EM6F,
EMS6,
EM6TA,
EM6FA, and
EFP8
6.7 Replacing the Ethernet
Interface Board
CF card 6.9 Replacing the CF Card
CST, CSH,
CSHU and
CSHUA
6.10 Replacing the System
Control, Switching and Timing
Board
AUX 6.11 Replacing the Auxiliary
Board
SP3D and SP3S 6.5 Replacing the PDH Interface
Board
l ESD wrist strap
l Screwdriver
Maintenance Guide 6 Part Replacement
178
Part Name Operation Tool
ISV3, IF1,
IFU2, ISX2,
ISU2, and IFX2
l U2000 6.8 Replacing the IF Board
PIU 6.13 Replacing the Power Board
ML1 and MD1 6.6 Replacing the Smart E1
Interface Board
FAN 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
SFP 6.14 Replacing the SFP l ESD wrist strap
l Tweezer fiber remover
l U2000

179
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.
180
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.
181

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.
182
NOTICE
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. 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.
183
2. Push the board gently along the slot guide rail until the board cannot slide further.
Figure 6-8 Inserting a board (1)

NOTICE
Insert the board slowly to prevent the components on the boards from colliding.
3. Press the two ejector levers inward with force.

4. Tighten screws on the panel.
184

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 You must know the impact of board replacement.
l You must know the specific position of the board to be replaced.
l You must know the service protection and protection channels of the board to be replaced.
l The spare SDH optical interface board must be available, and the version and type of 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 ESD wrist strap
l Screwdriver
l U2000
l 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.
185
1. Query the SNCP protection group.
2. Perform the forced switching, if the port on the board functions as the current working
channel, the current protection channel is not on the board, and the state of the 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. Query the linear MSP group.
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 7 After the board starts to work, check the STAT indicator on the board. The STAT indicator
should be on and green.
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 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 ESD wrist strap
l Screwdriver
186
l U2000
l Fiber remover
Procedure
Step 2 Optional: If the services on the board are configured with linear MSP, ensure that the services
Step 4 Check whether the version and SFP type of the spare board are the same as the version and SFP
Step 6 After the board starts to work, check the STAT indicator on the board. The STAT indicator
should be on and green.
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 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 ESD wrist strap
l Screwdriver
l U2000
187
Procedure
Step 3 Check and ensure that the version and type of the spare board are the same as the version and
Step 5 After the board starts to work, check the indicators on the board. The STAT indicator should be
on and green.
----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 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.
l ESD wrist strap
l Screwdriver
l U2000
Procedure
Step 1 Query the current alarms of the board to be replaced.
Step 3 Verify that the spare board has the same board version and board type as the board to be replaced.
Step 4 Insert the spare board.
Step 5 After the substitute board starts to work, check the indicators on the board. The STAT indicator
is on and green.
188
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.7 Replacing the Ethernet Interface Board
When the Ethernet interface board is replaced, the unprotected services on the board are
interrupted.
Prerequisites
l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
Procedure
Step 2 Optional: If the services are configured with MPLS APS, ensure that the services are already
switched to the protection tunnel.
1. Querying MPLS APS Status.
2. If the board functions as the current working board, perform the forced switching.
Step 3 Optional: If the services are configured with PW APS, ensure that the services are already
switched to the protection PW.
1. Querying PW APS Status.
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.
189
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.
on and green.
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 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.
l ESD wrist strap
l Screwdriver
l U2000
Procedure
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. Query the SNCP protection group.
2. If the port on the board functions as the current working channel, the current protection
channel is not on the board, 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. Query the IF 1+1 protection group.
190
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. Query the IF N+1 protection group.
Step 5 Optional: If the services are configured with MPLS APS, ensure that the services are already
switched to the protection tunnel.
1. Querying MPLS APS Status.
Step 6 Optional: If the services are configured with PW APS, ensure that the services are already
switched to the protection PW.
1. Querying PW APS Status.
Step 7 Optional: If the IF board is configured with the XPIC function, see 8.1.3 Muting/Unmuting
an ODU 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.
NOTICE
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 11 Ensure that the ODU-PWR switch on the front panel of the spare IF board is turned off.
on and green.
Step 14 Turn on the ODU-PWR switch on the front panel of the IF board.
191
NOTICE
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 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.
Step 18 If the IF board is configured with the XPIC function, see 8.1.3 Muting/Unmuting an ODU 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 You must be aware of the impact of CF card replacement.
l You must know the specific position of the CF card to be replaced.
l You must be a user with "NE maintainer" authority or higher.
l You must obtain a spare CF card that has the same capacity as the CF card to be replaced.
l ESD wrist strap
l U2000
l Fiber remover
Procedure
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.
192
1. See 8.9 Switching the System Control Unit and the Cross-Connect Unit, and ensure
that the current working board functions as the protection board.
2. If the board functions as the current working board, perform the manual switching.
Step 4 Remove the CF card according to the illustration in the following figure.
Step 5 Check the spare CF card.
Step 6 Install the spare CF card according to the illustration in the following figure.
Step 8 After the board starts to work, observe the indicators on the board. The STAT indicator should
be on and green.
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, Switching and Timing
Board
All the services are interrupted during the period of replacing the system control, switching, and
timing board, if the NE is configured with only one system control switch and timing board. If
193
a CSH/CST board is replaced, you can restore NE data by replacing the CF card. If a CSHU/
CSHUA board is replaced, you can back up and restore NE data from a USB flash drive. Perform
the operations specific to the type of the board to be replaced.
Prerequisites
l You must be aware of the impact of board replacement.
information to learn about the version of the board to be replaced.
l If a CSHU/CSHUA board is to be replaced, NE data has been obtained.
The backup NE data has been imported to a laptop where the Web LCT is installed, if
there is a backup of the NE database on the NMS.
The network plan document has been obtained if there is no backup of the NE database
on the NMS.
Impact on System
If no protection board is available, the replacement of the system control, switching, and timing
board results in service interruption.
l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
l A USB flash drive with the authorization file if a CSHU/CSHUA board is to be replaced
The file folders related to the NE (\db, \pkg, \patch, \sysdata, \script, and \license)
should not exist in the USB flash drive.
The RTN.CER file of the NE should be copied to the root directory of the USB flash
drive.
The RTN.CER file, which stores the account and password information at the system
administration level (the password is encrypted), is generated by the system
administrator of a network management center using dedicated tools.
Context
NOTE
After the NE database is restored successfully, a cold reset is automatically performed on the NE.
Procedure
Step 1 If a CSH/CST board is replaced, restore NE data by replacing the CF card.
1. Query the current alarms of the board.
194
2. Replace the system control, switching, and timing board.
If... Then...
One system
control,
switching, and
timing board is
configured
1. Notify the onsite maintenance personnel to remove the board.
2. Verify 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.
195
If... Then...
Two system
control,
switching, and
timing boards
are configured
1. Before replacing a working system control, switching, and timing
board, switch services from the working board to the protection
board. For details, see 8.9 Switching the System Control Unit
and the Cross-Connect Unit.
NOTICE
When the data of the working board is being synchronized to the protection
board or synchronization data is being delivered to the chip of the
protection board, removing the working board may interrupt services.
Before removing the working board, ensure that the board is in standby
status.
Wait until the protection switchover is completed, and then go to the next
step. A protection switchover is completed only after the data of the
working board has been synchronized to the protection board and
synchronization data has been delivered to the chip of the protection board.
2. After completing the protection switchover, 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 indicators on the board
are green.

3. Query the current alarms of the board. There should be no new alarms.
Step 2 If a CSHU/CSHUA board is replaced, back up and restore NE data from a USB flash drive.
2. Optional: If the NE is running, back up the NE data to the USB flash drive.
a. Insert the USB flash drive in the USB port on the OptiX RTN 950.
The indicator beside the USB port is blinking yellow during the data backup, and is
steady green after the data backup is complete.
b. Remove the USB flash drive after the data backup is complete.
3. Turn off the power supply for the IDU.
If the OptiX RTN 950 uses a two-input power supply, turn off both power inputs.
4. Replace the CSHU/CSHUA board.
a. Make labels for the cables and then 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.
196
1
2
1
1
2
Press
2
Press the front of the red latch. Properly move the red latch outwards. 2
1
b. Remove the CSHU/CSHUA board.
c. Verify that the spare board and the board to be replaced are of the same version and
use the same type of SFP modules.
d. Insert the spare CSHU/CSHUA board into the slot.
e. Recover the original cable connections according to the labels that are made
previously.
5. See the Commissioning Guide to power on the NE.
6. Restore NE configuration data.
If... Then...
The original NE is in the running state
and NE database is backed up by
following Step 2.2
Insert the USB flash drive into the USB port
of the CSHU/CSHUA board
The indicator beside the USB port is
blinking yellow during data restoration,
and is steady green after the data is restored.
It takes more than 10 minutes to restore NE
configuration data.
The original NE is not in the running
state and NE database is backed up to a
USB flash drive
1. Set the ID and IP address of the NE to
the predefined values by referring to
Changing the NE ID and Changing the
NE IP Address.
2. Restore NE configuration data by
referring to 7.4 Restoring the
Database by NMS.
The original NE is not in the running
state and NE database is not backed up
Configure NE data according to the
network plan.

197
----End
6.11 Replacing the Auxiliary Board
When the auxiliary board is replaced, the services on the auxiliary board are interrupted.
Prerequisites
l ESD wrist strap
l Screwdriver
l U2000
l Fiber remover
Procedure
Step 4 Insert the spare board.
on and green.
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.
198
Prerequisites
l ESD wrist strap
l U2000
Precautions
CAUTION
Do not touch the blades until the fan has stopped rotating.
Procedure
Step 2 Move the cables away from the front panel of the fan board assembly.
Step 3 Remove the fan board.
1
2
199
Step 5 Insert the standby fan board.
1
2
Step 6 After the board starts to work, observe the indicators on the board. The FAN indicator should
be on and green.
----End
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 ESD wrist strap
l Screwdriver
200
l U2000
Precautions
CAUTION
Do not remove or insert the power plug when the power is on. Turn off the power switch before
removing the power cable from the PIU.
Procedure
Step 2 Turn off the output power switch for the IDU 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.
Press the front of the red latch.
Properly move the red latch outwards. 2
1
1
2
1
2
1
2
Press
Step 4 Remove the power board gently and horizontally along the guide rail.
201
Step 5 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 Turn on the output power switch for the IDU.
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 You must know the impact of SFP replacement.
l You must know the specific position of the SFP to be replaced.
l You must know the service protection and protection channels of the SFP to be replaced.
l The spare SFP must be available, and the version and type of the spare SFP must be 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.
l ESD wrist strap
l Tweezer fiber remover
l U2000
Procedure
Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the services
1. Query the status of the SNCP group.
2. If the port on the local board functions as the working channel, the protection channel does
not involve the local board, and the protection channel is in the normal or SD state, perform
forced switching.
Step 3 Optional: If linear MSP is configured for services at the optical interface, ensure that the services
1. Query the status of the linear MSP group.
202
2. If the port on the local board functions as the working channel, the protection channel does
not involve the local board, and the protection channel is in the normal or SD state, 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
l Hold the extraction lever to remove the optical module.
l Press the release button before removing the STM-1 electrical module.
2
1
Press the release button.
Remove the STM-1 electical module.
1
2
Step 6 Insert the standby SFP module and reconnect cables based on the record.
Step 8 Optional: If the forced switching has been performed on the board, release the forced switching.
switching.
----End
6.15 Replacing the ODU
When the ODU is replaced, the unprotected services on the ODU are interrupted.
Prerequisites
l You must know the impact of ODU replacement.
203
l You must know the specific positions of the ODU to be replaced and the IF board connected
to the ODU.
l The spare ODU must be at hand, whose type must be the same as the type of the ODU to
be replaced.
l Ejector lever (torque spanner)
l U2000
l Silicon
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 Description
If... Then...
You need to remove the RTN 600 ODU
with a waveguide interface
Loosen the four latches of the ODU and
disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
You need to remove the RTN 600 ODU
with a coaxial interface
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 Description
If... Then...
204
Option Description
You need to install a new RTN 600 ODU
with a waveguide interface
See the RTN 600 ODU Quick Installation
Guide.
You need to install a new RTN 600 ODU
with a coaxial interface
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 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 You must know the impact of IF cable replacement.
l You must know the specific positions of the IF cable to be replaced and the IF board
connected to the IF jumper.
l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to
connect the IF cable to the IDU and both ends of the IF cable should be terminated 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.
l Multimeter
l Ejector lever
l Electro-technical knife
l File
l Installation parts and accessories of the connector
l IF cable
Procedure
Step 1 Query and record the current alarm of the IDU.
205
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... Then...
You need to make new connectors for the
IF cable
See the Installation Reference and make new
connectors for the IF cable.
You need to replace the IF cable with a new
one
Replace the IF cable with a new one.
Step 5 Connect the IF cable to the IF jumper and to the ODU.
Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.
Step 8 After the ODU starts to work, check the 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
6.17 Erasing Data in the Repair Parts
The storage media on the system control board stores NE configuration data. If necessary, erase
data on the board before repair.
6.17.1 Board Storage Media
The storage media on the system control board has the flash memory and CF card.
Overview
OptiX RTN 950 has two types of storage media: CF card and flash memory. Both the CF card
and flash memory may contain configuration data. As shown in Table 6-2, the types of storage
media supported by the system control boards for the OptiX RTN 950 are listed.
Table 6-2 Types of storage media on the system control boards
Board Storage Media
CST/CSH l Flash memory (integrated on the system
control board)
l CF card (pluggable)

206
Positions of the Storage Media
DIP switches on the system control board are used for some special maintenance-related
operations, including formatting the flash memory.
For the positions of the CF card and the DIP switches for formatting the flash memory, see "DIP
Switches and CF Card" of the system control board in the IDU Hardware Description.
6.17.2 Removing the CF Card
If necessary, remove the CF card from the repaired system control board to ensure data security.
l ESD wrist strap or ESD glove
l ESD bag for storing the removed CF card
NOTICE
Slowly and carefully remove the CF card, to prevent damages to the CF card or its card slot.
Procedure
Step 1 Wear an ESD wrist strap or ESD gloves during operations.
1. Put your hand through the ESD wrist strap, as shown inFigure 6-11.
2. Fasten the wrist strap to ensure good contact between the ESD wrist strap and your skin.
3. Connect the ground end of the ESD wrist strap to the ESD jack in the cabinet or chassis.
Step 2 Remove the CF card.
Step 3 Place the removed CF card to an ESD bag.
----End
207
6.17.3 Formatting the Flash Memory
If necessary, erase data in the flash memory by setting the DIP switches.
l ESD wrist strap or ESD glove
Procedure
Step 1 Wear an ESD wrist strap or ESD gloves during operations.
1. Put your hand through the ESD wrist strap, as shown inFigure 6-12.
2. Fasten the wrist strap to ensure good contact between the ESD wrist strap and your skin.
3. Connect the ground end of the ESD wrist strap to the ESD jack in the cabinet or chassis.
Step 2 Format the flash memory.
1. Remove the system control board from the chassis.
2. Set the BIOS DIP switches to binary values "1111".
When the DIP switches are set to "1111", the software will erase all data (except for board
manufacturing information), including data in the file system and the system parameter
area.
NOTE
For the positions of the DIP switches of system control boards, see "DIP Switches and CF Card" of
the system control board in the IDU Hardware Description.
3. Insert the system control board to the backup chassis, and power on the board. Observe the
RUN indicator. If the RUN indicator on the system control board blinks every 1s, the data
on the flash memory has been cleared.
208
NOTE
If the system control board cannot be powered on or the software fails to start, the preceding method
of clearing data from the flash memory by changing DIP switch settings is inapplicable. In this case,
contact Huawei technical support engineers.
----End
209
7 Database Backup and Restoration
About This Chapter
The OptiX RTN 950 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, cross-
connect, 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.
7.5 Recovering Databases from a USB Flash Drive
When NE data is lost or abnormal and DCN communication fails on an NE that houses a CSHU/
CSHUA board, you can recover NE databases from a USB flash drive.
Maintenance Guide 7 Database Backup and Restoration
210
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 An NE backs up DRDB data to the FDB within five minutes after NE configuration data
is modified.
l An NE backs up DRDB data to the FDB every 24 hours.
The following modes are available to back up FDB data:
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).
l On the NMS, FDB data can be backed up to an NMS server manually or at specified
intervals.
l For a CSHU/CSHUA board: If a USB flash drive is inserted in the USB port and the FDB
data in the flash memory is newer than that in the USB flash drive, the NE backs up the
FDB data from the flash memory to the USB flash drive.
l For a CSH/CST board: A CF card stores NE databases, system parameters (including NE-
IPs, NE-IDs, subnet masks, and LSR IDs), software packages, and NE logs.
211
NOTE
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.
Ensure that the software version of the system control, switching, and timing board is the same as that in
a CF card. 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.
NOTE
For a CSH/CST board, 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.
For a CSHU/CSHUA board, when you use the NMS to back up FDB data, system parameters such as NE-
IPs, NE-IDs, or subnet masks are backed up as well as LSR IDs.
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.
l When the NE is cold reset, the system control unit restores data from FDB0 and FDB1.
l When the data in both FDB0 and FDB1 is damaged, data can be restored from the CF
card.
l On the NMS, the FDB data in flash memory can be restored from an NMS server without
interruption of TDM services.
l For a CSHU/CSHUA board: If a USB flash drive is inserted in the USB port and the FDB
data in the USB flash drive is newer than that in the flash memory, the NE backs up the
FDB data from the USB flash drive to the flash drive.
l For a CSH/CST board: After you hold down the CRV button on the system control,
switching, and timing board for 8s, the data stored on the CF card will be synchronized to
the board. To synchronize the NE databases, system parameters, and NE logs from the
system control, switching, and timing board to the CF card, enable the regular backup
function. The default backup interval is 24 hours.
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, cross-
connect, 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 You must be an NM user with NE monitor authority or higher.
l You must log in to the NE.
U2000
212
NOTE
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/
Restoration from the Main Menu.
Step 2 In NE View, click Find.
Step 3 In the Find NE dialog box, set the search conditions and search for the NE that requires 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.
213
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 You must be an NM user with NE monitor authority or higher.
U2000
NOTE
Each NE has a default data backup policy.
214
l Database packages are backed up once at 2:00.
l The default backup policy is disabled by default.
l A maximum of five database packages can be backed up at a time.
l Data changes do not trigger any backup operations.
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy 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 to import the information of the NEs.
Step 5 Optional: Click to export the information of the NEs.
The information of the selected NEs is stored in the specified location.
Step 6 In NE Table, select one or more NEs.
Step 7 Click Next.
215
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
U2000
NOTE
Procedure
from the Main Menu.
216
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
from the Main Menu.
217
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 The data to be restored must be backed up.
U2000
218
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.
219
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 Set Activate Type to With Service Interruption and select Deliver To Board Activate.
NOTE
l If Activate Type is No Reboot, only database files are overwritten and the NE will not be warm reset. The
database does not take effect until the NE is reset.
l If Activate Type is With Service Interruption, database files will be overwritten, the NE will be warm
reset, and then the database will take effect.
l If Deliver To Board Activate is selected, the EFP8/EMS6 board will be instructed to perform a cold reset
during database activation.
l If Deliver To Board Activate is unselected, the EFP8/EMS6 board will not be cold reset.
Step 9 In the Recover dialog box, click Start.
Step 10 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 11 In NE View, right-click the NE and choose Active Database from the shortcut menu.
The Active Database dialog box is displayed.
Step 12 Click Start to start activating the database.
220
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
7.5 Recovering Databases from a USB Flash Drive
When NE data is lost or abnormal and DCN communication fails on an NE that houses a CSHU/
CSHUA board, you can recover NE databases from a USB flash drive.
Prerequisites
l The NE database has been backed up.
l You have logged in to the NE on the NMS.
U2000
USB flash drive
Procedure
Step 1 Copy the NE database backup file db_pck.gz from the NMS server to the \db directory in the
USB flash drive.
NOTE
Other directories related to the NE (\pkg, \patch, \sysdata, \script, and \license) must not exist.
Step 2 Copy the RTN.CER file of the NE to the root directory of the USB flash drive.
NOTE
The RTN.CER file, which stores the account and password information at the system administration level (the
password is encrypted), is generated by the system administrator of a network management center using
dedicated tools.
Step 3 Insert the USB flash drive in the USB port on the OptiX RTN 950.
NOTE
During the database recovering process, do not perform operations such as data configuration, NE resets, and
software loading.
Step 4 Check the data loading status based on the indicator on the USB flash drive.
221
Status of the USB
Indicator
Data Loading Status Operation
The indicator blinks yellow
and then turns steady green.
The loading of
commissioning data is
complete.
NOTE
l When the indicator is
blinking yellow, do not
remove the USB flash
drive. Otherwise, the data
loading may be interrupted.
l After the data loading is
complete, the NE will
automatically reset, which
takes 2 minutes to 3
minutes. After the reset is
complete, the USB
indicator and the system
indicator (SRV) on the NE
are both steady green,
indicating that the data
loading is successful.
Remove the USB flash drive.
The indicator is off. The USB flash drive is faulty
and fails to get online.
NOTE
Another possible cause is that
the USB flash drive is not
properly inserted.
l Copy the commissioning
data to another USB flash
drive.
l Repeat 1 to load the
commissioning data to
the NE.
The indicator blinks red. The type of the USB flash
drive is incorrect or an error
occurs when the NE attempts
to read/write the USB flash
drive.
NOTE
Preparing Documents and
Tools provides the USB flash
drive types that the OptiX RTN
950 supports.
l Copy the commissioning
data to another USB flash
drive.
the NE.
222
Status of the USB
Indicator
Data Loading Status Operation
The indicator is steady red. The loaded commissioning
data is abnormal.
Reload the data:
l Save the correct NE
software and
commissioning data
scripts in the correct
directories of the USB
flash drive.
the NE.
----End
223
8 Common Maintenance Operations
About This Chapter
This section introduces common maintenance operations.
8.1 Microwave Link Troubleshooting
This section describes common maintenance operations related to microwave link
troubleshooting.
8.2 Ethernet Service Troubleshooting
This section describes common maintenance operations related to Ethernet service
troubleshooting.
8.3 TDM/CES Service Troubleshooting
This section describes common maintenance operations related to TDM/CES service
troubleshooting.
8.4 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.5 Hardware Loopback
Hardware loopback refers to the loopback operation performed by changing the physical
connection.
8.6 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold
reset, warm reset.
8.7 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.8 Querying Power Consumption of Boards
This section describes how to query power consumption of the ODU and each board.
Maintenance Guide 8 Common Maintenance Operations
224
8.9 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.10 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.
225
8.1 Microwave Link Troubleshooting
This section describes common maintenance operations related to microwave link
troubleshooting.
8.1.1 Monitoring Radio Link Indicators
This section describes how to collect high-density samples about the RSL and MSE indicators
of radio links for monitoring. The longest monitoring duration is 48 hours.
Prerequisites
U2000
NOTE
Procedure
Step 1 Navigate to the interface for monitoring the RSL and MSE indicators of radio links.
2
1
Step 2 Configure parameters for monitoring the RSL and MSE indicators of radio links.
226
3
4
Set the monitored
object.
5
Set the monitoring
duration. The
maximum value is
48 hours.
6
Step 3 Query the monitoring result.
8 7 9
Set the query type.
The query result of the MSE
is displayed in green and that
of the RSL is displayed in red.
Set the time range of
the query.
----End
8.1.2 Scanning Interfering Signals
You can learn whether intra-frequency or inter-frequency interference exists by scanning
frequency spectra in microwave channels.
Prerequisites
l Mute the ODU at the opposite end, before scanning the reference signal.
227
U2000
Procedure
Step 1 Select the NE from Object tree in the NE Explorer.
NOTE
Step 2 Choose Diagnosis&Maintenance > ODU Frequency Scan.
NOTE
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.1.3 Muting/Unmuting an ODU
The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the
unmute state, the ODU transmits and receives microwave signals normally. When the ODU
transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive
microwave signals.
Prerequisites
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.
U2000
NOTE
228
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Step 2 Click the Advanced Attributes tab.
Step 3 Set Configure Transmission Status for the ODU.
NOTE
l In normal cases, Configure Transmission Status is set to unmute.
l If Configure Transmission Status is set to mute, the transmitter of the ODU does not work but can
normally receive microwave signals.
l If Configure Transmission Status is set to unmute, the ODU can normally transmit and receive
microwave signals.
Step 4 Click Apply.
----End
8.1.4 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
229
Precautions
Figure 8-1 PRBS test of the IF board
1
1
PRBS
transmitter
PRBS
ODU
1
ODU
NE at the local end NE at the opposite end
IF port outloop 1
transmitter
IF board IF board

NOTICE
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 Configure an outloop on the peer IF board by referring to instructions in 8.4.7 Setting Loopback
for the IF Board and .
Step 2 Start a PRBS test on the IF board.
230
3
Select the desired PRBS test type.
Two PRBS test types are available:
a. PRBS frames are transmitted through the
specified E1 timeslot.
b. PRBS frames are transmitted as Ethernet
frames.
2
1
Select the desired IF board.
4
Configure the
test time.
5
Select an E1 path.
This parameter is
mandatory only for
E1 PRBS tests.
6
7
Step 3 View test results.
231
View test results.
View the test
report.
8
9
10
Green indicates no
exception.
No bit error is found,
indicating that the link
works properly.
----End
8.2 Ethernet Service Troubleshooting
This section describes common maintenance operations related to Ethernet service
troubleshooting.
8.2.1 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
232
Procedure
Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.
NOTE
1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Ethernet Interface from the Function
Tree.
3. Click the Advanced Attributes tab.
4. Check the parameters such as Port Physical Parameters, Transmitting Rate, and
Receiving Rate.
Step 2 Optional: Querying the attributes of the port.
NOTE
1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Microwave Interface from the
Function Tree.
4. Check the parameters such as Transmitting Rate and Receiving Rate.
Step 3 Optional: Query the attributes of the external port on the EFP8 board.
NOTE
1. In NE Explorer, select the EFP8 board from the Object Tree.
2. Choose Configuration > Ethernet Interface Management > Ethernet Interface from
the Function Tree.
3. Select External Port.
5. Check the parameters such as Transmitting Rate and Receiving Rate.
NOTE
By performing this operation, you can query the attributes of the external ports on the EFP8 board (PORT1 to
PORT8) and the attributes of the bridging port on the EFP8 board (PORT9).
----End
8.2.2 Searching for Service Paths Based on VLANs
For E-Line services, this operation can display the transmission path of the VLAN service flow
on one access port. For E-LAN services, this operation can display the broadcast domain to
which the VLAN belongs.
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
233
Procedure
Step 1 Optional: Search for an E-Line service path.
Step 2 Optional: Search for an E-LAN service path.
----End
234
8.2.3 Searching for Service Paths Based on MAC Addresses
For E-LAN services, this operation allows the information of a MAC address learned by each
NE on a service path to be displayed, illustrating the entire service path through which packets
with the MAC address being the source address travel.
Prerequisites
Procedure
Step 1 Search for an E-LAN service path.
Step 2 Query the Learning of MAC Addresses.
235
----End
8.2.4 Checking the Layer 2 Protocols Used by Ethernet Services
This section describes how to check the Layer 2 protocols, including ERPS, MSTP, and STP,
used by E-LAN services based on service paths.
Prerequisites
End-to-end Ethernet services have been created and the related fibers/cables have been created.
Procedure
236
Step 2 Check the Layer 2 protocols used by the E-LAN services.
----End
8.2.5 Performing Intelligent Service Fault Diagnosis for Ethernet
Services
This section describes how to intelligently diagnose faults of Ethernet services based on service
paths.
Prerequisites
237
Procedure
Step 1 Search for services.
Step 2 Select a service to be diagnosed by specifying a service port.
Step 3 Diagnose the service and display the result.
238
----End
8.2.6 Performing E-LAN Service Loopback Detection
This section checks whether a loopback occurs on Ethernet services based on service paths.
Users can quickly rectify a data storm on a loop after finding out the loopback point.
Prerequisites
Procedure
239
Step 2 Perform E-LAN service loopback detection.
NOTE
If a service is looped back, can be seen from the icons .
----End
8.2.7 Monitoring Ethernet Service Performance and Traffic Volume
Based on Service Paths
This section describes how to monitor Ethernet service performance based on service paths.
240
Prerequisites
Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.
241
----End
8.2.8 Querying Ethernet Service QoS Configurations Based on
Service Paths
This section describes how to query Ethernet service QoS configurations based on service paths.
Prerequisites
End-to-End Ethernet services and associated fibers have been created.
Procedure
Step 1 Search out service paths.
242
Step 2 Select the service to be diagnosed by specifying service ports.
Step 3 Query QoS configurations.
243
----End
8.2.9 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. If the
system control, switching, and timing board is CSHU/CSHUA, this function is not supported.
Prerequisites
U2000
NOTE
244
Context
Figure 8-2 Schematic diagram of Ethernet port mirroring
Mirroring
port
NE under port mirroring
Monitoring
port
Ethernet equipment
Ethernet tester
Duplication
Ethernet equipment
Port
Forwarding

The port mirroring can be performed in two directions.
For the physical ports of:
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.
For the VCTRUNK of EFP8/EMS6:
l In the upstream direction, the ports mirror the data transmitted from the VCTRUNK to the
TDM side.
l In the downstream direction, the ports mirror the data transmitted from the TDM side to
the VCTRUNK.

Procedure
Step 1 Select operations according to the Ethernet board type.
In the case of... Then...
Ethernet boards exclude EFP8/EMS6 Perform Step 2 toStep 5.
EFP8/EMS6 boards Perform Step 6 toStep 9.

Step 2 In NE Explorer, select the NE.
Step 3 Choose Configuration > Port Mirroring from the Function Tree.
245
Step 4 Click New, and set Mirror Name, Select the Direction of Mirror Source Function Point,
Mirror Source Function Point, and Mirror Observation Point.
Step 5 Click OK.
Step 6 In NE Explorer, select the EFP8 or EMS6 board.
Step 7 Choose Configuration > Ethernet Interface Management > Port Mirroring from the
Function Tree.
Step 8 Click New, and set Mirrored Port, Mirrored Upstream Port, and Mirrored Downstream
Port.
Step 9 Click OK.
----End
8.2.10 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 The service traffic is encapsulated or mapped by using the GFP method.
U2000
NOTE
246
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-3 Ethernet test frames between Ethernet boards
Local
Ethernet
board
Remote
Ethernet
board
Test frame
Response frame

Precautions
NOTICE
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.
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
247
Related Information
If you choose the continue mode, the local port transmits test frames continuously until the test
is disabled.
8.2.11 Checking L3VPN Service Performance Using NQA
OptiX RTN 950 can function as the server of NQA UDP jitter. Performance of L3VPN services
between an OptiX RTN 950 and CX600 can be verified by enabling the NQA UDP jitter test on
the CX600.
Prerequisites
l L3VPN services have been correctly deployed.
U2000
NOTE
Context
NQA UDP jitter indicates the difference between the receiving interval and transmission interval
of two neighboring packets between a server and a client. Figure 8-4 shows the process for
testing the NQA UPD jitter:
1. The client sends test packets to the server at a certain interval.
2. After the server receives a test packet, it adds a time stamp and returns the packet to the
client.
3. After the client receives a returned test packet, it calculates the time difference between the
sending and receiving of the packet to get the jitter time.
248
Figure 8-4 NQA UDP jitter test process
Optix RTN 950
(Server)
CX 600
(client)
Adding time
stamp
Calculating
delay variation
t
n
t
n
'
t
1
t
1
'
t
n
t
1
Packet transmission interval on the client

t
n
' t
1
'
Packet receive interval on the server
UDP jitter test case packet
The packets received by the client can be used to calculate the maximum jitter time, minimum
jitter time, average jitter time, and delay between the client and the server, which can clearly
demonstrate the network performance.
NOTE
When NQA UDP jitter is used to calculate unidirectional delay, time on the client and the server must be
synchronous.
OptiX RTN 950 can only be used as the server of NQA UDP jitter.
Precautions
None
Sample Connection
The following steps are based on the test for services between the UNI (Vlanif 100) of RSG5
and the UNI (the VLAN sub-interface 1-EG4-1.1 on 1-EG4-1) of CSG1 in Figure 8-5.
249
Figure 8-5 Networking diagram
NodeB
S-GW/MME
Last Mile Access Aggregation MBB core
RNC
eNodeB
1
-
E
G
4
-
2
RSG5
RSG6
ASG4
ASG3
CSG1
CSG2
P11
P12

RR7
RR8
1-EG4-1
20.20.0.8/27
Procedure
Step 1 Choose Performance -> Performance Monitoring Management on the main menu of the
NMS to navigate to the performance monitoring and management interface.
Step 2 On the function tree of the interface, choose Test Path -> Network Path -> UDP Jitter Path
to navigate to the interface for configuring UDP jitter.
Step 3 On the lower right corner of the interface, click Create to navigate to the interface for creating
a monitoring instance.
Step 4 Set parameters for filtering NEs on the interface for setting the filtering criteria and click OK.
NOTE
When there are many NEs, set the filtering criteria to facilitate the selection of the server and client for a UDP
jitter test. When there are only a few NEs, click OK to skip the setting of filtering criteria.
Step 5 Select the server and client for the UDP jitter test from the resource list.
250
NOTE
By default, OptiX RTN 950 is used as the server of the test and a CX600 is the client.
Step 6 Click Next and Generate Test to generate a path.
Step 7 Click Next to configure the monitoring template. You can select a created template or create a
new template.
251
Figure 8-6 Selecting a monitoring template
Figure 8-7 Creating a monitoring template
Step 8 Click Next to set the default SLA parameters.
252
NOTE
Select a UDP jitter path, and configure parameters for the path. Set the parameters as follows:
l Set the destination address of the path to the IP address of the interface for the server to bind the VRF
instance.
l Set the VRF name to the name of the L3VPN instance on the sever.
l Retain the default value for the source address.
Step 9 Click Next to configure the monitoring time range.
253
NOTE
If the monitoring time range is not set, the UDP jitter test instance will keep on monitoring L3VPN services.
Step 10 (Optional) Click Create Scheduled Policy to set the timing policy for monitoring.
Step 11 Click Next to display the progress of the creation.
Step 12 Click Close to return to the performance monitoring and management interface. On the
performance monitoring list, the created UDP jitter monitoring instance is in the running status.
254
Step 13 Double-click the monitoring instance to view the monitoring status of L3VPN services in
graphical format.
----End
8.3 TDM/CES Service Troubleshooting
This section describes common maintenance operations related to TDM/CES service
troubleshooting.
8.3.1 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.
255
Operation object Operation Steps
SDH optical interface board 1. Choose Configuration > SDH
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.3.2 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.
256
Step 4 Click Apply to save the settings.
----End
8.3.3 Performing a PRBS Test for the Smart E1 Processing Board
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-8.
Figure 8-8 PRBS test in the tributary direction
PRBS
Transmitter
PRBS
Recevicer
Smart E1
processing unit
1
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-9.
257
Figure 8-9 PRBS test in the NNI direction
Cross-connect
Unit
PRBS
transmitter
PRBS
receiver
Smart E1
processing unit
ETH service
processing unit
IN
OUT
ETH port inloop ETH port outloop 1
2
3
2 3
1
ETH service
processing unit
ETH port inloop

Precautions
NOTICE
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 Configure a loopback as required by referring to Figure 8-8 and Figure 8-9.
Step 2 Start a PRBS test for the smart E1 processing board
258
2
1
3
4
5
6
Select the desired
smart E1 board in
the NE Explorer.
Specify the port type, frame
format, test period, and test
duration (1 to 255)
259
7
View test results, Green
indicates no exception.
8
9
The number of bit errors
and BER is 0, indicating
no exception.
----End
8.3.4 Performing a PRBS Test for the Tributary Board
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.
260
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-10.
Figure 8-10 PRBS test in the tributary direction
PRBS
Transmitter
PRBS
Recevicer
PDH unit DDF frame
1
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-11.
Figure 8-11 PRBS test in the cross-connect direction
Cross-connect
board
PRBS
transmitter
PRBS
receiver
PDH interface
board
IF board
IN
OUT
VC-4 inloop or
composite port inloop
IF port inloop IF port outloop 1
2
3
2 3
IF board
1
a) IF board working as the line board
Cross-connect board
PRBS
transmitter
PRBS
receiver
PDH interface board
NE at the local end
NE at the opposite end
IN
OUT
VC-4 inloop Port inloop Port outloop 1
2
3
2 3
SDH optical
interface board
1
b) Line board working as the SDH optical interface board

261
Precautions
NOTICE
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 Configure a loopback as required by referring to Figure 8-10 and Figure 8-11.
Step 2 Start a PRBS test for the tributary board.
2
1
Select an E1
interface board in the
NE Explorer.
3
Configure the port type, test
period, and test duration (1
to 255).
4
5
6
262
7
View test results. Green
indicates no exception.
8
9
The number of bit errors
and the BER are 0,
indicating no exception.
----End
8.3.5 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.
263
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.4 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.4.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
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-12 Optical/electrical interface inloop
SDH optical
interface board
Backplane
SDH

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.
264
Figure 8-13 Optical/electrical interface outloop
SDH optical
interface board
Backplane
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-14 VC-4 path outloop
SDH optical
interface board
Backplane
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.
Figure 8-15 VC-4 path inloop
SDH optical
board
Backplane
VC-4

265
Precautions
NOTICE
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.7 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... Choose...
Optical/electrical interface loopback Optical(Electrical) Interface Loopback
VC-4 path loopback VC4 Loopback
Step 4 Set the loopback status of the port or path based on the requirements.
Step 5 Click Apply.
Then, the Confirm dialog box is displayed.
Step 6 Click OK.
----End
8.4.2 Setting Loopback for the Channelized STM-1 Processing
Board
The channelized STM-1 processing board supports the optical/electrical interface inloop/
outloop.
Prerequisites
U2000
NOTE
266
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-16 Optical/electrical interface inloop
Channelized STM-1
Processing Board
backplane
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-17 Optical/electrical interface outloop
Channelized STM-1
Processing Board backplane
VC-12

Precautions
NOTICE
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.
267
Step 4 Set the loopback status of the port or path based on the requirements.
Step 5 Click Apply.
Step 6 Click OK.
----End
8.4.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.
Figure 8-18 Tributary inloop
PDH interface board
Backplane
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.
268
Figure 8-19 Tributary outloop
PDH
PDH interface board Backplane

Precautions
NOTICE
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.
Step 5 Click Apply.
Step 6 Click OK.
----End
8.4.4 Setting a Loopback for the Smart E1 Processing Board
A Smart E1 processing board supports inloops and outloops on E1 ports.
Prerequisites
269
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-20 E1 inloop
Smart E1
Processing Board Backplane
E1

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-21 E1 outloop
E1
Smart E1
Processing Boards
Backplane

Precautions
NOTICE
l A software loopback may be released automatically within a period (5 minutes, by default).
For details, see 8.7 Setting the Automatic Release Function.
270
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.
Smart E1
Processing Board Backplane
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.4.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).
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.
271
Figure 8-22 Ethernet port inloop
Ethernet service
processing board
Backplane
PHY MAC

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.
NOTICE
l A loopback operation results in service interruption.
NOTICE
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.
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.
PHY loopback
1. Choose Configuration > Interface Management > Ethernet
MAC loopback
1. Choose Configuration > Interface Management > Ethernet
272
Step 3 Set the loopback status of the port based on the requirements.
Step 4 Click Apply.
Step 5 Click OK.
----End
8.4.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.
Figure 8-23 Ethernet port inloop
Ethernet service
processing board
Backplane
PHY MAC

273
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.
EOPDH
Backplane 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.
EOS
Backplane EMS6

Precautions
NOTICE
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.7 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.
274
PHY loopback
1. Choose Configuration > Ethernet Interface Management >
Ethernet Interface from the Function Tree.
MAC loopback
1. Choose Configuration > Ethernet Interface Management >
Ethernet Interface from the Function Tree.
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.4.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
275
Context
The IF port inloop is a process wherein the IF signals are looped back at the modem unit towards
the backplane.
Figure 8-26 IF port inloop
IF board Backplane
IF signal

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-27 IF port outloop
IF board Backplane
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.
Figure 8-28 Composite port inloop
IF board Backplane
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.
276
Figure 8-29 Composite port outloop
IF board Backplane
Microwave
baseband
signal

Precautions
NOTICE
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.
NOTICE
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.
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
Select the corresponding function options from the Function Tree based on the loopback type.
277
IF port loopback
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.
set Optical (Electrical) Interface Loopback.
MAC loopback
1. Choose Configuration > Interface Management >
Microwave Interface from the Function Tree.
2. Select Advanced Attributes.
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
Step 6 Click OK to close the dialog box.
NOTE
Then, a dialog box is displayed.
NOTE
----End
8.4.8 Setting Software Loopback for the NE
This task sets the loopback for the object on an NE.
278
Prerequisites
U2000
NOTE
Precautions
NOTICE
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.
Step 4 Click Apply.
----End
279
8.4.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
NOTICE
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.
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.4.10 Locating a Fault by Performing Loopback Operations
Loopback is a common method of locating the fault.
280
Prerequisites
U2000
Service Trail
Figure 8-30 shows how to locate a fault by performing a loopback operation.
Figure 8-30 Service trail
IF
board
Cross-connect
board
SDH
tributary
board
ODU
NE2
IF
board
Cross-connect
board
SDH
tributary
board
ODU
NE3
Optical cable
IF
board
Cross-connect
board
ODU
NE4
PDH
tributary
board
IF
board
Cross-connect
board
ODU
NE1
PDH
tributary
board

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. 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.
281
2. If the fault is located in the service receiver, set outloop for the PDH tributary board to
check whether the interface board or switch unit is faulty.
3. If the radio link is faulty, replace the IF board and ODU to check whether the IF board or
ODU is faulty.
----End
8.5 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.
l PDH cable loopback indicates that the receive and transmit PDH cables are connected
through a short-circuiting cable or connector on the DDF.
l 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.
8.6 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold
reset, warm reset.
8.6.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
282
Precautions
NOTICE
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.
Step 3 Click OK.
----End
8.6.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.
Step 3 Click OK.
283
----End
8.7 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.8 Querying Power Consumption of Boards
This section describes how to query power consumption of the ODU and each board.
Prerequisites
U2000
NOTE
284
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 6 On the Board Power tab page, browse Nominal Power Consumption and Current Power
Consumption of the selected board.
----End
8.9 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.
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
Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair.
NOTE
285
Step 4 Perform the 1+1 protection switching on the board.
If... Then...
Active Board is set to Working Board Click Working/Protection Switching.
Active Board is set to Protection Board Click Restore Working/Protection.
Step 5 In the prompt that is displayed, click OK.
NOTE
----End
8.10 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.10.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 Disconnect both ends of the fiber. Ensure that there is no laser light on the fiber connectors.
l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.
Cartridge cleaner
Procedure
Step 1 Press down and hold the lever. Then, the shutter slides back and exposes a new cleaning area.
286
Figure 8-31 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-32 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.
287
Figure 8-33 Dragging the fiber tip slightly on the other cleaning area

Step 4 Release the lever to close the cleaning area.
----End
8.10.2 Cleaning Fiber Connectors by Using Lens Tissue
When there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.
Prerequisites
l Disconnect both ends of the fiber. ensure that there is no laser light on the fiber connectors.
l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.
l Clean solvent
l Non-woven lens tissue
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.
288
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-34 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.10.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 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.3.1 Setting the On/Off State of the Laser.
289
l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is
contaminated.
l Optical cleaning sticks
l Clean solvent
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
290
A 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.
Maintenance Guide A Alarm Reference
291
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 Description Alarm
Severity
A_LOC Loss of clock in the upstream bus Major
ACR_LOCK_FAIL 1588 ACR locking fails Major
ALM_E1RAI E1 link remote alarm indication Minor
ALM_GFP_dCSF Loss of GFP client signals Critical
ALM_GFP_dLFD Out of frame state of generic framing procedure
(GFP) frames
Major
ALM_IMA_LIF Frame delimitation is out-of-frame at the local end
of the IMA link.
Major
ALM_IMA_LODS Differential delay of the IMA link crosses the
threshold.
Major
ALM_IMA_RE_RX_
UNUSABLE
The IMA link on the opposite NE fails in the
receive direction.
Minor
ALM_IMA_RE_TX_
UNUSABLE
The IMA link on the opposite NE fails in the
transmit direction.
Minor
ALM_IMA_RFI Frame delimitation is out-of-frame at the remote
end of the IMA link.
Major
AM_DOWNSHIFT Downshift of AM modes Major
APS_FAIL Failure indication of MS protection switching Major
APS_INDI Indication of the APS protection switching Major
APS_MANUAL_ST
OP
MS protocol stopped manually Minor
ATMPW_UNKNOW
NCELL_EXC
The number of unknown ATM cells exceeds the
specified threshold in a time unit.
Major
AU_AIS AU alarm indication Major
AU_LOP Loss of AU pointers Major
B1_EXC Excessive regenerator section errors (B1) Minor
292
Severity
B1_SD Signal degradation due to excessive regenerator
section errors (B1)
Minor
B2_EXC Excessive multiplex section errors (B2) Major
B2_SD Signal degradation due to excessive multiplex
section errors (B2)
Minor
B3_EXC Excessive higher order path bit errors (B3) Major
B3_EXC_VC3 Excessive B3 bit errors in a VC-3 path Major
B3_SD Signal degradation due to excessive higher order
path bit errors (B3)
Minor
B3_SD_VC3 Signal degradation due to excessive VC-3 path
(B3) bit errors
Minor
BAT1TEMP_SENSO
R_FAIL
The temperature sensor of battery group 1 fails. Major
BAT2TEMP_SENSO
R_FAIL
The temperature sensor of battery group 2 fails. Major
BD_NOT_INSTALL
ED
The logical board is not added on the NMS. Minor
BD_STATUS The board is out-of-position. Major
BDTEMP_SENSOR_
FAIL
The board temperature sensor of the cabinet fails. Major
BGPBACKTRANSI-
TION
A BGP session is interrupted. Major
BIOS_STATUS The board is in BIOS state. Major
BIP_EXC Excessive BIP errors Minor
BIP_SD Signal degradation due to excessive BIP errors Minor
BOOTROM_BAD BOOTROM data check fails. Major
BUS_ERR Bus errors Critical
CES_ACR_LOCK_A
BN
The locking function of CES ACR service clock
is abnormal.
Minor
CES_APS_INDI Packet MSP protocol state indication Major
CES_APS_MANUA
L_STOP
The MSP protocol is disabled manually. Minor
CES_JTROVR_EXC The amount of jitter buffer overflow crosses the
specified threshold.
Major
293
Severity
CES_JTRUDR_EXC The amount of jitter buffer underflow crosses the
specified threshold.
Major
CES_K1_K2_M K1 and K2 mismatch Minor
CES_K2_M K2 mismatch Minor
CES_LOSPKT_EXC The number of lost packets crosses the specified
threshold in a time unit.
Major
CES_MALPKT_EX
C
The number of deformed packets crosses the
Major
CES_MISORDERP
KT_EXC
The number of lost disordered packets crosses the
Major
CES_RDI Remote defect indication Minor
CES_STRAYPKT_E
XC
The number of error packets crosses the specified
threshold in a time unit.
Major
CESPW_OPPOSITE
_ACFAULT
The AC circuit on the opposite NE is faulty. Major
CESPW_OPPOSITE
_RAI
Remote alarm indication Major
CFCARD_FAILED The operation on the CF card fails. Major
CFCARD_OFFLINE The CF card is offline. Major
CHCS Correctable cell errors Minor
CLK_LOCK_FAIL Clock locking fails Major
CLK_NO_TRACE_
MODE
The clock source is not in locked mode. Minor
COMMUN_FAIL Inter-board communication fails. Major
COM_EXTECC_FU
LL
Excessive TCP connections between
automatically extended ECC NEs
Major
CONFIG_NOSUPPO
RT
Configuration is not supported. Major
DBMS_DELETE The status of databases is delete. Major
DBMS_ERROR Errors in the processing of system databases Major
DBMS_PROTECT_
MODE
System databases in protection mode Critical
DCNSIZE_OVER Oversized DCN network Major
294
Severity
DDN_LFA The frame alignment signal of framed E1 services
is lost.
Major
DOWN_E1_AIS Alarm indication of 2 Mbit/s downstream signals Minor
DROPRATIO_OVE
R
The number of lost packets due to port congestion
crosses the threshold.
Minor
E1_LOC Loss of 2 Mbit/s clock in upstream signals Major
E1_LOS Loss of 2 Mbit/s line signals Minor
ELAN_SMAC_FLA
PPING
The source MAC address learned by an E-LAN
service flaps.
Major
ENVHUM_SENSOR
_FAIL
The ambient humidity sensor of the cabinet fails. Major
ENVTEMP_SENSO
R_FAIL
The ambient temperature sensor of the cabinet
fails.
Major
ENVTEMP1_SENSO
R_FAIL
The ambient temperature sensor 1 of the cabinet
fails.
Major
ENVTEMP2_SENSO
R_FAIL
The ambient temperature sensor 2 of the cabinet
fails.
Major
ERPS_IN_PROTEC-
TION
Indicates that a node on the EPRS ring is faulty. Minor
ETH_APS_LOST Loss of APS frames Minor
ETH_APS_PATH_M
ISMATCH
The working and protection paths of the APS
protection group differ between the two ends.
Major
ETH_APS_SWITCH
_FAIL
Protection switching failure Minor
ETH_APS_TYPE_M
ISMATCH
Protection scheme mismatch Major
ETH_AUTO_LINK_
DOWN
Automatic link down of Ethernet port Minor
ETH_CFM_AIS A local MEP_AIS occurs. Major
ETH_CFM_LOC Loss of connectivity Major
ETH_CFM_MISME
RGE
Misconnection Major
ETH_CFM_RDI The maintenance association end point (MEP)
fails to receive CCM packets.
Minor
295
Severity
ETH_CFM_UNEXP
ERI
Error frames Minor
ETH_EFM_DF Discovery failure Major
ETH_EFM_EVENT Performance events at the opposite end Major
ETH_EFM_LOOPB
ACK
A loopback occurs. Major
ETH_EFM_REMFA
ULT
Faults occur at the opposite end. Critical
ETH_LOS Loss of Ethernet port connection Critical
ETH_NO_FLOW No flow on the Ethernet port Major
ETH_PWR_SUPPL
Y_FAIL
Power output failure of an Ethernet port Critical
ETHOAM_DISCOV
ER_FAIL
Discovery failure is detected by point-to-point
Ethernet OAM.
Minor
ETHOAM_RMT_C
RIT_FAULT
Severe faults are detected by point-to-point
Ethernet OAM at the remote end.
Minor
ETHOAM_RMT_L
OOP
A remote loopback is detected by point-to-point
Ethernet OAM.
Minor
ETHOAM_RMT_SD Remote Ethernet performance degradation is
detected by point-to-point Ethernet OAM.
Minor
ETHOAM_SELF_L
OOP
An MAC port loopback is detected by point-to-
point Ethernet OAM.
Major
ETHOAM_VCG_SE
LF_LOOP
A VCTRUNK port loopback is detected by point-
to-point Ethernet OAM.
Major
EX_ETHOAM_CC_
LOS
Loss of periodical continuity check packets Critical
EX_ETHOAM_MPI
D_CNFLCT
Conflict of maintenance point IDs Major
EXT_SYNC_LOS Loss of external clock sources Critical
EXT_TIME_LOC Loss of external time sources Major
FAN_AGING Aged fans Minor
FAN_FAIL Failure of fan boards Major
FCS_ERR Frame check sequence (FCS) errors Critical
296
Severity
FDBSIZEALM_ELA
N
items listed in an E-LAN forwarding table are all
used
Minor
FLOW_OVER Excessive data traffic received by Ethernet ports Minor
GSP_RSVP_NB_AU
TH_ERR
An RSVP neighbor authentication error occurs. Major
GSP_RSVP_NB_DO
WN
An RSVP neighbor becomes unreachable. Major
GSP_TNNL_DOWN A tunnel is interrupted. Major
HARD_BAD Hardware faults Critical
HARD_NONSUPPO
RT
Board hardware does not support a certain
function.
Major
HP_CROSSTR Threshold-crossing performance event of the
higher order path
Minor
HP_LOM Loss of multiframes in the higher order path Major
HP_RDI Higher order path remote defect indication Minor
HP_REI Higher order path remote error indication Warning
HP_SLM Higher order path signal label mismatch Minor
HP_TIM High order path trace identifier mismatch Minor
HP_UNEQ Unequipped higher order path Minor
HPAD_CROSSTR Adaptation performance threshold-crossing of the
higher order path
Minor
IF_CABLE_OPEN IF cables are disconnected. Major
IF_INPWR_ABN The power supplied by an IF board to an ODU is
abnormal.
Major
IF_MODE_UNSUP-
PORTED
Preset IF working mode is not supported. Major
IMA_GROUP_LE_D
OWN
The IMA group at the local end fails. Major
IMA_GROUP_RE_D
OWN
The IMA group at the remote end fails. Major
IMA_TXCLK_MIS-
MATCH
The transmit clock modes at the two ends of the
IMA group are different.
Minor
IN_PWR_ABN Abnormal input optical power Major
297
Severity
IN_PWR_HIGH Over high input optical power Critical
IN_PWR_LOW Over low input optical power Critical
INTEMP_SENSOR_
FAIL
The air intake vent temperature sensor of the
cabinet fails.
Major
IPFPM_INST_TLP_
ERR
Binding an IP FPM instance to the TLP fails. Minor
ISISADJACENCY-
CHANGE
The status of an IS-IS neighbor changes. Major
J0_MM Trace identifier mismatch Minor
K1_K2_M K1 and K2 mismatch Minor
K2_M K2 mismatch Minor
L3V_TRAP_THRE_
EXCEED
The number of private network route prefixes
exceeds the threshold.
Major
L3V_TRAP_VRF_D
OWN
All ports on a private network are down. Major
LAG_BWMM Bandwidth inconsistency in the LAG group Major
LAG_DOWN The LAG is unavailable. Major
LAG_MEMBER_DO
WN
A member port of a link aggregation group (LAG)
is unavailable.
Minor
LAG_PORT_FAIL A member port of a LAG fails. Minor
LAG_VC_PORT_FA
IL
A VCG port of an LAG fails. Minor
LAN_LOC Ethernet communication failure Major
LASER_CLOSED The laser is shut down. Major
LASER_MOD_ERR The type of the pluggable optical module on the
board does not match the type of the optical
interface.
Major
LASER_MOD_ERR
_EX
The type of the pluggable optical module on the
board does not match the type of the optical
interface.
Major
LASER_SHUT The laser is shut down. Major
LCAS_FOPR LCAS protocol fails in the receive direction. Major
LCAS_FOPT LCAS protocol fails in the transmit direction. Major
298
Severity
LCAS_PLCR Loss of partial bandwidth in the LCAS receive
direction
Minor
LCAS_PLCT Loss of partial bandwidth in the LCAS transmit
direction
Minor
LCAS_TLCR Loss of total bandwidth in the LCAS receive
direction
Major
LCAS_TLCT Loss of total bandwidth in the LCAS transmit
direction
Major
LCD Loss of cell delimitation Major
LCS_LIMITED The capacity of the configured services exceeds
the range permitted by the license file.
Major
LDP_PEER_DOWN LDP peer interruption Major
LFA Out of frame state of E1 frames Major
LICENSE_LOST The NE fails to detect any license file. Major
LINK_ERR Faults occur in a data link. Critical
LMFA Out of frame state of E1 multiframes Major
LOOP_ALM A loopback occurs. Minor
LP_CROSSTR Performance threshold-crossing of the lower
order path
Minor
LP_R_FIFO FIFO overflow on the receive side of the lower
order path
Minor
LP_RDI Lower order path remote defect indication Minor
LP_RDI_VC12 VC-12 path remote defect indication Minor
LP_RDI_VC3 VC-3 path remote defect indication Minor
LP_REI Lower order path remote error indication Minor
LP_REI_VC12 VC-12 path remote error indication Minor
LP_REI_VC3 VC-3 path remote bit error indication Minor
LP_RFI Lower order path remote failure indication Minor
LP_SLM Lower order path signal label mismatch Minor
LP_SLM_VC12 VC-12 path signal label mismatch Minor
LP_SLM_VC3 VC-3 path signal label mismatch Minor
299
Severity
LP_T_FIFO FIFO overflow on the transmit side of the lower
order path
Minor
LP_TIM Lower order path trace identifier mismatch Minor
LP_TIM_VC12 VC-12 path trace identifier mismatch Minor
LP_TIM_VC3 VC-3 path tracking identification mismatch Minor
LP_UNEQ Unequipped lower order paths Minor
LP_UNEQ_VC12 Unequipped VC-12 paths Minor
LP_UNEQ_VC3 VC-3 path unequipped Minor
LPS_UNI_BI_M The switching mode is single-ended at one end
and dual-ended at the other end.
Minor
LPT_CFG_CLOSE-
PORT
The LPT closes the access port of the local NE. Major
LPT_INEFFECT LPT function failed Major
LPT_RFI Link state pass-through function fails at the
remote end.
Critical
LSR_BCM_ALM Laser bias current crossing the threshold Major
LSR_NO_FITED Laser not installed Critical
LSR_WILL_DIE Laser going to expire Critical
LTI Loss of clock synchronization source Major
MAC_EXT_EXC The number of bit errors at the MAC layer crosses
the threshold.
Major
MAC_FCS_EXC The software detects that the number of bit errors
at the MAC layer crosses the threshold.
Major
MAC_FCS_SD Signal degrade bit errors at the MAC layer cross
the threshold.
Major
MOD_COM_FAIL Module communication failure Critical
MOD_TYPE_MIS-
MATCH
Port module type mismatch Critical
MP_DELAY The group member delay Major
MP_DOWN MP group failure Major
MPLS_PW_AIS PW forward defect indication Major
MPLS_PW_BDI PW backward defect indication Minor
300
Severity
MPLS_PW_CSF MPLS PW Client Signal Fail
MPLS_PW_Excess Excessive trail termination source identifiers
(TTSIs) are received on the PW.
Warning
MPLS_PW_LCK The server layer (tunnel) of MPLS PW locked
indication
Major
MPLS_PW_LOCK Administration locking of PW layer Major
MPLS_PW_LOCV Loss of PW connectivity Major
MPLS_PW_MISMA
TCH
The trail termination source identifiers (TTSIs) on
the PW do not match with the specified one.
Major
MPLS_PW_MISME
RGE
The trail termination source identifiers (TTSIs)
are mismerged on the PW.
Major
MPLS_PW_OAMFA
IL
OAM protocol negotiation failure Minor
MPLS_PW_RDI PW backward defect indication Minor
MPLS_PW_SD Signal degradation on the PW Major
MPLS_PW_SF Signal failure on the PW Major
MPLS_PW_UNEXP
MEG
The MEP receives a packet with correct MEG
level but incorrect MEG ID.
Critical
MPLS_PW_UNEXP
MEP
The CCM information of a PW OAM packet is
incorrect.
Major
MPLS_PW_UNEXP
PER
The PW does not receive a CCM packet in the
expected period.
Major
MPLS_PW_UNKNO
WN
Unknown defects on the PW Major
MPLS_TUNNEL_AI
S
Tunnel forward defect indication Major
MPLS_TUNNEL_B
DI
Tunnel backward defect indication Minor
MPLS_TUNNEL_Ex
cess
Excessive trail termination source identifiers
(TTSIs) are received on the tunnel.
Warning
MPLS_TUNNEL_FD
I
Tunnel forward defect indication Minor
MPLS_TUNNEL_L
OCK
Administration locking of tunnel layer Major
301
Severity
MPLS_TUNNEL_L
OCV
Loss of tunnel connectivity Major
MPLS_TUNNEL_MI
SMATCH
The trail termination source identifiers (TTSIs) on
the tunnel do not match with the specified one.
Major
MPLS_TUNNEL_MI
SMERGE
The trail termination source identifiers (TTSIs)
are mismerged on the tunnel.
Major
MPLS_TUNNEL_O
AMFAIL
The OAM protocol negotiation between the two
ends of the tunnel fails.
Minor
MPLS_TUNNEL_R
DI
Tunnel backward defect indication Minor
MPLS_TUNNEL_SD Signal degradation on the tunnel Major
MPLS_TUNNEL_SF Signal failure on the tunnel Major
MPLS_TUNNEL_U
NEXPMEG
Unexpected MEG ID in the CCM packet Critical
MPLS_TUNNEL_U
NEXPMEP
Unexpected MEP ID in the CCM packet Major
MPLS_TUNNEL_U
NEXPPER
Unexpected period of the CCM packet Major
MPLS_TUNNEL_U
NKNOWN
Unknown defects on the tunnel Major
MS_AIS Multiplex section alarm indication Major
MS_CROSSTR Multiplex section performance threshold-
crossing
Minor
MS_RDI Multiplex section remote defect indication Minor
MS_REI Multiplex section remote error indication Warning
MSAD_CROSSTR Multiplex section adaptation performance
threshold-crossing
Minor
MULTI_RPL_OWN
ER
The ring network has multiple RPL_OWNER
nodes.
Minor
MW_AM_TEST The IF port is in the AM testing state. Minor
MW_BER_EXC Excessive errors on radio links Minor
MW_BER_SD Signal degradation due to excessive errors on
radio links
Minor
302
Severity
MW_CFG_MISMAT
CH
Configuration mismatch on radio links Critical
MW_CONT_WAVE Continuous wave Minor
MW_E1_LOST Loss of E1 signals Major
MW_FEC_UNCOR Microwave frames have the errors that cannot be
corrected by using the forward error correction
(FEC) technology.
Minor
MW_LIM Label mismatch on radio links Major
MW_LOF Loss of microwave frames Critical
MW_RDI Remote defect indication on radio links Minor
NEIP_CONFUSION IP address is conflict Major
NESF_LOST The NE software is lost. Critical
NESOFT_MM The software in the main area is different from that
in the standby area.
Major
NO_BD_SOFT The board software is lost. Critical
NP1_MANUAL_ST
OP
The N+1 protection protocol is stopped manually. Minor
NP1_SW_FAIL The N+1 protection switching fails. Major
NP1_SW_INDI N+1 protection switching indication Major
NTP_SYNC_FAIL Synchronization with the NTP time fails. Minor
OCD Out of cell delimitation Major
ODC_BATTERY_C
URRENT_ABN
Abnormal current of the storage battery Major
ODC_BATTERY_P
WRDOWN
The storage battery fails to supply power for the
equipment.
Major
ODC_DOOR_OPEN The door of an outdoor cabinet is open. Critical
ODC_FAN_FAILED Fan failure Major
ODC_HUMI_ABN The relative humidity in the cabinet environment
crosses the specified threshold.
Minor
ODC_LOAD_PWRD
OWN
The secondary load is powered off. Major
ODC_MDL_ABN The power module is abnormal. Major
303
Severity
ODC_POWER_FAI
L
Exceptions occur in the AC input power voltage. Major
ODC_SMOKE_OVE
R
Smoke occurs in an outdoor cabinet. Critical
ODC_SURGE_PRO
TECTION_FAIL
The surge protection function of the outdoor
cabinet fails.
Critical
ODC_TEC_ALM The TEC air conditioning module in the cabinet
fails.
Major
ODC_TEMP_ABN The ambient temperature of the cabinet or the
temperature of the storage battery is
inappropriate.
Minor
ODC_WATER_AL
M
Water in the outdoor cabinet Critical
OSPFNBRSTATE-
CHANGE
The OSPF neighbor state changes. Major
OUT_PWR_ABN Abnormal output optical power Critical
OUT1TEMP_SENS
OR_FAIL
The air outlet temperature sensor of the cabinet
fails.
Major
OUT2TEMP_SENS
OR_FAIL
The external recycling outlet temperature sensor
of the cabinet fails.
Major
PASSWORD_NEED
_CHANGE
Password of the user who logs in is unchanged. Major
PATCH_BD_EXCL
UDE
Patch isolation Major
PATCH_BD_MATC
H_FAIL
Patch matching failure Major
PATCH_CHGSCC_
NOTMATCH
Patch package mismatch due to system control
board replacement
Major
PATCH_PKGERR Abnormal patch package Minor
PG_LINK_FAIL Links of the 1+1 protection group fail. Critical
PG_PRT_DEGRAD
ED
The working link or protection link of the 1+1
protection group is faulty.
Major
PLA_CFG_MISMA
TCH
Inconsistent PLA configurations Critical
PLA_DOWN PLA group is faulty Major
304
Severity
PLA_MEMBER_DO
WN
Member link of a PLA group is faulty Major
PORTMODE_MIS-
MATCH
The working mode of the remote FE port does not
match that of the local FE port.
Minor
PORT_EXC_TRAFF
IC
The traffic is higher than the port bandwidth
threshold.
Warning
PORT_MODULE_O
FFLINE
Port not in position Major
POWER_ABNORM
AL
Power input alarm Major
POWER_ALM Power module alarm Major
PPP_LCP_FAIL LCP negotiation failure Major
PPP_NCP_FAIL NCP negotiation failure Major
PTP_SOURCE_SWI
TCH
PTP time source switching Minor
PTP_TIMESTAMP_
ABN
PTP time stamp abnormality Major
PW_DROPPKT_EX
C
The number of lost packets in a PW crosses the
threshold.
Warning
PW_NO_TRAFFIC The PW has no traffic. Critical
PWAPS_LOST Loss of APS frames Minor
PWAPS_PATH_MIS
MATCH
The working and protection paths of the APS
protection group differ between the two ends.
Major
PWAPS_SWITCH_F
AIL
Protection switching failure Minor
PWAPS_TYPE_MIS
MATCH
Protection scheme mismatch Major
PW_APS_DEGRAD
ED
The PW APS protection group is degraded. Major
PW_APS_OUTAGE The PW APS protection group is unavailable. Major
PW_DOWN A PW is disconnected. Critical
R_LOC Loss of clock on the receive line side Critical
R_LOF Loss of frame on the receive line side Critical
305
Severity
R_LOS Loss of signal or loss of microwave frame on the
receive line side
Critical
R_OOF The out-of-frame fault occurs on the receive line
side.
Critical
RADIO_FADING_M
ARGIN_INSUFF
Radio fading margin is insufficient. Minor
RADIO_MUTE The radio transmitter is muted. Warning
RADIO_RSL_BE-
YONDTH
Antennas are not aligned. Minor
RADIO_RSL_HIGH Over high radio receive signal level Critical
RADIO_RSL_LOW Over low radio receive signal level Critical
RADIO_TSL_HIGH Over high radio transmit signal level Critical
RADIO_TSL_LOW Over low radio transmit signal level Critical
RELAY_ALARM_C
RITICAL
There are critical alarm inputs. Critical
RELAY_ALARM_I
GNORE
There are warning inputs. Warning
RELAY_ALARM_M
AJOR
There are major alarm inputs. Major
RELAY_ALARM_M
INOR
There are minor alarm inputs. Minor
RMFA Loss of multiframe alignment at the remote end Minor
RPS_INDI Radio protection switching indication Major
RS_CROSSTR Regenerator section performance threshold-
crossing
Minor
RT_TBL_LACK Routing table resources are insufficient. Minor
RTC_FAIL The real-time clock (RTC) of the system control
board fails.
Major
S1_SYN_CHANGE Clock source switching in S1 mode Major
SCCDATA_BACKU
P_FAIL
Batch backup of SCC boards fails. Minor
SEC_RADIUS_FAIL RADIUS authentication fails. Major
SECU_ALM Security alarm Major
306
Severity
SRV_SHUTDOWN_
LD
Ethernet services are interrupted. Warning
SSL_CERT_NOENC Certificate file of SSL is not encrypted Major
SUBNET_RT_CON-
FLICT
Subnetwork route conflict Major
SWDL_ACTIVATE
D_TIMEOUT
The commit operation is not performed during
software package loading.
Critical
SWDL_AUTOMAT
CH_INH
The automatic match function is disabled. Minor
SWDL_CHGMNG_
NOMATCH
The board software version and the version of the
running software are inconsistent.
Critical
SWDL_COMMIT_F
AIL
The submit operation fails. Minor
SWDL_INPROCESS The package diffusion is being performed on the
NE.
Warning
SWDL_NEPKGCHE
CK
Certain files in the package stored in flash
memory are lost.
Critical
SWDL_PKG_NOBD
SOFT
The software package does not contain any board
software.
Minor
SWDL_PKGVER_M
M
Software package version consistency check fails. Minor
SWDL_ROLLBACK
_FAIL
The version rollback on an NE fails. Minor
SYN_BAD Synchronous source degradation Minor
SYNC_C_LOS Loss of synchronization clock sources Warning
SYSLOG_COMM_F
AIL
The communication between the NE and the
syslog server fails.
Major
T_ALOS Loss of analog signals at 2 Mbit/s interfaces Major
T_LOC Loss of clock on the transmit line side Major
TEM_HA Too high laser temperature Major
TEM_LA Too low laser temperature Major
TEMP_ALARM Excessive board temperature Minor
TEMP_OVER Excessive board temperature Major
TF Laser transmission fails. Critical
307
Severity
THUNDERALM Surge protection fails. Minor
TIME_LOCK_FAIL Time locking fails. Major
TIME_NO_TRACE_
MODE
The high precision time of the NE is in the non-
traced status.
Minor
TR_LOC Clock failure Major
TU_AIS TU alarm indication Major
TU_AIS_VC12 VC-12 path TU alarm indication Major
TU_AIS_VC3 TU of VC-3 level alarm indication Major
TU_LOP Loss of TU pointers Major
TU_LOP_VC12 Loss of TU pointers in VC-12 paths Major
TU_LOP_VC3 TU of VC-3 level loss of pointer Major
TUNNEL_APS_DE-
GRADED
The tunnel protection group degrades. Major
TUNNEL_APS_OUT
AGE
The tunnel protection group is unavailable Major
UHCS Uncorrectable cell errors Minor
UP_E1_AIS Alarm indication of 2 Mbit/s upstream signals Minor
USB_PROCESS_FAI
L
Data restoration from a USB flash drive fails Minor
V5_VCAIS Bits 5-7 in the V5 byte of a VC-12 path are set to
"1"s.
Major
VC_AIS Alarm indication signal of the VC connection Critical
VC_LOC Loss of VC continuity check Major
VC_RDI Remote defect indication of the VC connection Major
VCAT_LOA Excessive virtual concatenation delay Critical
VCAT_LOM_VC12 Loss of multiframe of VC-12 path virtual
concatenation
Major
VCAT_LOM_VC3 The virtually concatenated multiframes in a VC-3
path are lost.
Major
VCAT_SQM_VC12 SQ mismatch of VC-12 path virtual concatenation Major
VCAT_SQM_VC3 SQ mismatch of VC-3 path virtual concatenation Major
308
Severity
VERSION_NOTSUP
PORT
The current version does not support the
configured function or data.
Critical
VOLT_LOS Loss of voltage Major
VP_AIS Alarm indication signal of the VP connection Critical
VP_LOC Loss of VP continuity check Major
VP_RDI Remote defect indication of the VP connection Major
W_R_FAIL Failure in reading and writing chip registers Major
WRG_BD_TYPE Error board types Major
XPIC_LOS Loss of XPIC compensation signals Critical

A.2 Alarm List (Classified by Logical Boards)
This part lists the alarms that are reported by each board.
NOTE
The NE software consider a physical board as one or more logical boards when managing the physical board.
The NMS also considers a physical board as one or more logical boards when managing the physical board.
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
Logical Board
CST CST in the same slot
CSH CSH in the same slot
CSHU CSHU in the same slot
CSHUA CSHUA in the same slot
AUX AUX in the same slot
IF1 IF1 in the same slot
IFU2 IFU2 in the same slot
IFX2 IFX2 in the same slot
ISU2 ISU2 in the same slot
ISX2 ISX2 in the same slot
309
Physical
Board
Logical Board
ISV3 ISV3 in the same slot
SL1D SL1D in the same slot
SL1DA SL1DA in the same slot
EM6T EM6T in the same slot
EM6TA EM6TA in the same slot
EM6F EM6F in the same slot
EM6FA EM6FA in the same slot
EG4 EG4 in the same slot
EG4P EG4P in the same slot
EFP8 EFP8 in the same slot
EMS6 EMS6 in the same slot
SP3S SP3S in the same slot
SP3D SP3D in the same slot
ML1 ML1 in the same slot
MD1 MD1 in the same slot
CQ1 CQ1 in the same slot
PIU PIU in the same slot
FAN FAN in the same slot
ODU ODU in the slot whose number is 20 plus the slot number for the IF board
that is connected to the ODU

A.2.1 AUX
l BD_STATUS
l HARD_BAD
l RELAY_ALARM_CRITICAL
l RELAY_ALARM_IGNORE
l RELAY_ALARM_MAJOR
l RELAY_ALARM_MINOR
l WRG_BD_TYPE

310
A.2.2 CQ1
l ALM_E1RAI
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l BIP_EXC
l BIP_SD
l BUS_ERR
l CES_JTROVR_EXC
l CES_JTRUDR_EXC
l CES_LOSPKT_EXC
l CES_MALPKT_EXC
l CES_MISORDERPK
T_EXC
l CES_RDI
l CES_STRAYPKT_E
XC
l CESPW_OPPOSITE_
ACFAULT
l CESPW_OPPOSITE_
RAI
l HARD_BAD
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IN_PWR_ABN
l IN_PWR_HIGH
l IN_PWR_LOW
l J0_MM
l LASER_MOD_ERR
l LASER_SHUT
l LFA
l LMFA
l LOOP_ALM
l LP_RDI_VC12
l LP_REI_VC12
l LP_RFI
l LP_SLM_VC12
l LP_TIM_VC12
l LP_UNEQ_VC12
l LSR_BCM_ALM
l LSR_NO_FITED
l LSR_WILL_DIE
l MP_DELAY
l MP_DOWN
l MS_AIS
l MS_RDI
l MS_REI
l OUT_PWR_ABN
l POWER_ABNORM
AL
l PPP_LCP_FAIL
l PPP_NCP_FAIL
l R_LOC
l R_LOF
l R_LOS
l R_OOF
l TEM_HA
l TEM_LA
l TEMP_OVER
l TF
l TR_LOC
l TU_AIS_VC12
l TU_LOP_VC12
l UP_E1_AIS
l V5_VCAIS
l WRG_BD_TYPE

311
A.2.3 CSH
l ACR_LOCK_FAIL
l APS_FAIL
l APS_INDI
l APS_MANUAL_ST
OP
l BD_NOT_INSTALL
ED
l BD_STATUS
l BIOS_STATUS
l BOOTROM_BAD
l CES_APS_INDI
l CES_APS_MANUAL
_STOP
l CES_K1_K2_M
l CES_K2_M
l CFCARD_FAILED
l CFCARD_OFFLINE
l CLK_LOCK_FAIL
l CLK_NO_TRACE_
MODE
l COM_EXTECC_FUL
L
l COMMUN_FAIL
l DBMS_DELETE
l DBMS_ERROR
l DBMS_PROTECT_
MODE
l DCNSIZE_OVER
l ELAN_SMAC_FLAP
PING
l ETH_APS_LOST
l ETH_APS_PATH_M
ISMATCH
l ETH_APS_SWITCH
_FAIL
l ETH_APS_TYPE_MI
SMATCH
l ETH_NO_FLOW
l EXT_SYNC_LOS
l HARD_NONSUPPO
RT
l K1_K2_M
l K2_M
l LAG_BWMM
l LAN_LOC
l LCS_LIMITED
l LICENSE_LOST
l LPS_UNI_BI_M
l LPT_CFG_CLOSE-
PORT
l LTI
l MOD_COM_FAIL
l MPLS_PW_AIS
l MPLS_PW_BDI
l MPLS_PW_CSF
l MPLS_PW_Excess
l MPLS_PW_LCK
l MPLS_PW_LOCK
l MPLS_PW_LOCV
l MPLS_PW_MISMA
TCH
l MPLS_PW_MISMER
GE
l MPLS_PW_OAMFAI
L
l MPLS_PW_RDI
l MPLS_PW_SD
l MPLS_PW_SF
l MPLS_PW_UNEXP
MEG
l MPLS_PW_UNEXP
MEP
l MPLS_PW_UNEXPP
ER
l MPLS_PW_UNKNO
WN
l MPLS_TUNNEL_AI
S
l MPLS_TUNNEL_LO
CV
l MPLS_TUNNEL_MI
SMATCH
l MPLS_TUNNEL_MI
SMERGE
l MPLS_TUNNEL_OA
MFAIL
l MPLS_TUNNEL_RD
I
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_UN
EXPMEG
l MPLS_TUNNEL_UN
EXPMEP
l MPLS_TUNNEL_UN
EXPPER
l MPLS_TUNNEL_UN
KNOWN
l NEIP_CONFUSION
l NESF_LOST
l NESOFT_MM
l NP1_MANUAL_STO
P
l NP1_SW_FAIL
l NP1_SW_INDI
l NTP_SYNC_FAIL
l PASSWORD_NEED
_CHANGE
l PATCH_ACT_TIME-
OUT
l PATCH_DEACT_TI
MEOUT
l PATCH_PKGERR
l PG_LINK_FAIL
l PG_PRT_DEGRADE
D
l PLA_CFG_MISMAT
CH
l PWAPS_SWITCH_F
AIL
l PWAPS_TYPE_MIS-
MATCH
l PW_APS_DEGRAD
ED
l PW_APS_OUTAGE
l RPS_INDI
l RTC_FAIL
l S1_SYN_CHANGE
l SCCDATA_BACKU
P_FAIL
l SEC_RADIUS_FAIL
l SECU_ALM
l SRV_SHUTDOWN_
LD
l SSL_CERT_NOENC
l STORM_CUR_QUE
NUM_OVER
l SUBNET_RT_CON-
FLICT
l SWDL_ACTIVATED
_TIMEOUT
l SWDL_AUTOMATC
H_INH
l SWDL_CHGMNG_N
OMATCH
l SWDL_COMMIT_F
AIL
l SWDL_INPROCESS
l SWDL_NEPKGCHE
CK
l SWDL_PKG_NOBD-
SOFT
l SWDL_PKGVER_M
M
l SWDL_ROLLBACK
_FAIL
l SYN_BAD
l SYNC_C_LOS
312
l EXT_TIME_LOC
l FDBSIZEALM_ELA
N
l FLOW_OVER
l HARD_BAD
l MPLS_TUNNEL_BD
I
l MPLS_TUNNEL_Ex-
cess
l MPLS_TUNNEL_FD
I
l MPLS_TUNNEL_LO
CK
l PORT_EXC_TRAFFI
C
l POWER_ALM
l PTP_SOURCE_SWI
TCH
l PTP_TIMESTAMP_
ABN
l PW_DROPPKT_EXC
l PW_NO_TRAFFIC
l PWAPS_LOST
l PWAPS_PATH_MIS-
MATCH
l SYSLOG_COMM_F
AIL
l TEMP_ALARM
l TIME_LOCK_FAIL
l TIME_NO_TRACE_
MODE
l TUNNEL_APS_DE-
GRADED
l TUNNEL_APS_OUT
AGE
l WRG_BD_TYPE

313
A.2.4 CSHU/CSHUA
l ACR_LOCK_FAIL
l APS_FAIL
l APS_INDI
l APS_MANUAL_ST
OP
l BD_NOT_INSTALL
ED
l BD_STATUS
l BGPBACKTRANSI-
TION
l BIOS_STATUS
l BOOTROM_BAD
l CES_APS_INDI
l CES_APS_MANUAL
_STOP
l CES_K1_K2_M
l CES_K2_M
l CLK_LOCK_FAIL
l CLK_NO_TRACE_
MODE
l COM_EXTECC_FUL
L
l COMMUN_FAIL
l DBMS_DELETE
l DBMS_ERROR
l DBMS_PROTECT_
MODE
l DCNSIZE_OVER
l ELAN_SMAC_FLAP
PING
l ETH_APS_LOST
l ETH_APS_PATH_M
ISMATCH
l ETH_APS_SWITCH
_FAIL
l ETH_APS_TYPE_MI
SMATCH
l ETH_NO_FLOW
l EXT_SYNC_LOS
l EXT_TIME_LOC
l LICENSE_LOST
l LPS_UNI_BI_M
l LPT_CFG_CLOSE-
PORT
l LTI
l MAC_EXT_EXC
l MAC_FCS_EXC
l MPLS_PW_AIS
l MPLS_PW_BDI
l MPLS_PW_CSF
l MPLS_PW_Excess
l MPLS_PW_LCK
l MPLS_PW_LOCK
l MPLS_PW_LOCV
l MPLS_PW_MISMA
TCH
l MPLS_PW_MISMER
GE
l MPLS_PW_OAMFAI
L
l MPLS_PW_RDI
l MPLS_PW_SD
l MPLS_PW_SF
l MPLS_PW_UNEXP
MEG
l MPLS_PW_UNEXP
MEP
l MPLS_PW_UNEXPP
ER
l MPLS_PW_UNKNO
WN
l MPLS_TUNNEL_AI
S
l MPLS_TUNNEL_BD
I
l MPLS_TUNNEL_Ex-
cess
l MPLS_TUNNEL_FD
I
l MPLS_TUNNEL_LO
CK
l OSPFNBRSTATE-
CHANGE
l PASSWORD_NEED
_CHANGE
l PATCH_BD_EXCLU
DE
l PATCH_BD_MATC
H_FAIL
l PATCH_CHGSCC_N
OTMATCH
l PATCH_PKGERR
l PG_LINK_FAIL
l PG_PRT_DEGRADE
D
l PLA_CFG_MISMAT
CH
l PLA_DOWN
l PLA_MEMBER_DO
WN
l PORT_EXC_TRAFFI
C
l POWER_ALM
l PTP_SOURCE_SWI
TCH
l PTP_TIMESTAMP_
ABN
l PW_APS_DEGRAD
ED
l PW_APS_OUTAGE
l PW_DOWN
l PW_DROPPKT_EXC
l PW_NO_TRAFFIC
l PWAPS_LOST
l PWAPS_PATH_MIS-
MATCH
l PWAPS_SWITCH_F
AIL
l PWAPS_TYPE_MIS-
MATCH
l RPS_INDI
l RT_TBL_LACK
l TEMP_ALARM
l TIME_LOCK_FAIL
l TIME_NO_TRACE_
MODE
l TUNNEL_APS_DE-
GRADED
l TUNNEL_APS_OUT
AGE
l USB_PROCESS_FAI
L
l VERSION_NOTSUP-
PORT
l WRG_BD_TYPE
314
l FDBSIZEALM_ELA
N
l FLOW_OVER
l GSP_RSVP_NB_AU
TH_ERR
l GSP_RSVP_NB_DO
WN
l GSP_TNNL_DOWN
l HARD_BAD
l HARD_NONSUPPO
RT
l IPFPM_INST_TLP_E
RR
l ISISADJACENCY-
CHANGE
l K1_K2_M
l K2_M
l L3V_TRAP_THRE_
EXCEED
l L3V_TRAP_VRF_D
OWN
l LAG_BWMM
l LAN_LOC
l LCS_LIMITED
l LDP_PEER_DOWN
l MPLS_TUNNEL_LO
CV
l MPLS_TUNNEL_MI
SMATCH
l MPLS_TUNNEL_MI
SMERGE
l MPLS_TUNNEL_OA
MFAIL
l MPLS_TUNNEL_RD
I
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_UN
EXPMEG
l MPLS_TUNNEL_UN
EXPMEP
l MPLS_TUNNEL_UN
EXPPER
l MPLS_TUNNEL_UN
KNOWN
l NEIP_CONFUSION
l NESF_LOST
l NESOFT_MM
l NP1_MANUAL_STO
P
l NP1_SW_FAIL
l NP1_SW_INDI
l NTP_SYNC_FAIL
l RTC_FAIL
l S1_SYN_CHANGE
l SCCDATA_BACKU
P_FAIL
l SEC_RADIUS_FAIL
l SECU_ALM
l SRV_SHUTDOWN_
LD
l SSL_CERT_NOENC
l SWDL_ACTIVATED
_TIMEOUT
l SWDL_AUTOMATC
H_INH
l SWDL_CHGMNG_N
OMATCH
l SWDL_COMMIT_F
AIL
l SWDL_INPROCESS
l SWDL_NEPKGCHE
CK
l SWDL_PKG_NOBD-
SOFT
l SWDL_PKGVER_M
M
l SWDL_ROLLBACK
_FAIL
l SYN_BAD
l SYNC_C_LOS
l SYSLOG_COMM_F
AIL

315
A.2.5 CST
l APS_FAIL
l APS_INDI
l APS_MANUAL_ST
OP
l BD_NOT_INSTALL
ED
l BD_STATUS
l BIOS_STATUS
l BOOTROM_BAD
l CFCARD_FAILED
l CFCARD_OFFLINE
l CLK_LOCK_FAIL
l CLK_NO_TRACE_
MODE
l COM_EXTECC_FUL
L
l COMMUN_FAIL
l DBMS_DELETE
l DBMS_ERROR
l DBMS_PROTECT_
MODE
l DCNSIZE_OVER
l EXT_SYNC_LOS
l HARD_BAD
l K1_K2_M
l K2_M
l LAN_LOC
l LCS_LIMITED
l LICENSE_LOST
l LPS_UNI_BI_M
l LTI
l NEIP_CONFUSION
l NESF_LOST
l NESOFT_MM
l NP1_MANUAL_STO
P
l NP1_SW_FAIL
l NP1_SW_INDI
l NTP_SYNC_FAIL
l PASSWORD_NEED
_CHANGE
l PATCH_BD_EXCLU
DE
l PATCH_BD_MATC
H_FAIL
l PATCH_CHGSCC_N
OTMATCH
l PATCH_PKGERR
l PG_LINK_FAIL
l PG_PRT_DEGRADE
D
l PLA_CFG_MISMAT
CH
l POWER_ALM
l RPS_INDI
l RTC_FAIL
l S1_SYN_CHANGE
l SCCDATA_BACKU
P_FAIL
l SEC_RADIUS_FAIL
l SECU_ALM
l SSL_CERT_NOENC
l STORM_CUR_QUE
NUM_OVER
l SUBNET_RT_CON-
FLICT
l SWDL_ACTIVATED
_TIMEOUT
l SWDL_AUTOMATC
H_INH
l SWDL_CHGMNG_N
OMATCH
l SWDL_COMMIT_F
AIL
l SWDL_INPROCESS
l SWDL_NEPKGCHE
CK
l SWDL_PKG_NOBD-
SOFT
l SWDL_PKGVER_M
M
l SWDL_ROLLBACK
_FAIL
l SYN_BAD
l SYNC_C_LOS
l SYSLOG_COMM_F
AIL
l TEMP_ALARM
l WRG_BD_TYPE

316
A.2.6 EFP8
l ALM_GFP_dCSF
l ALM_GFP_dLFD
l BD_STATUS
l BIP_EXC
l BIP_SD
l COMMUN_FAIL
l DOWN_E1_AIS
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_LOS
l ETHOAM_DISCOV
ER_FAIL
l ETHOAM_RMT_CR
IT_FAULT
l ETHOAM_RMT_LO
OP
l ETHOAM_RMT_SD
l ETHOAM_SELF_LO
OP
l ETHOAM_VCG_SE
LF_LOOP
l EX_ETHOAM_CC_L
OS
l EX_ETHOAM_MPI
D_CNFLCT
l FCS_ERR
l FLOW_OVER
l HARD_BAD
l LAG_PORT_FAIL
l LAG_VC_PORT_FA
IL
l LCAS_FOPR
l LCAS_FOPT
l LCAS_PLCR
l LCAS_PLCT
l LCAS_TLCR
l LCAS_TLCT
l LFA
l LMFA
l LOOP_ALM
l LP_RDI_VC12
l LP_REI_VC12
l LP_SLM_VC12
l LP_TIM_VC12
l LP_UNEQ_VC12
l LPT_RFI
l NO_BD_SOFT
l RMFA
l TEMP_ALARM
l TU_AIS_VC12
l TU_LOP_VC12
l VCAT_LOA
l VCAT_LOM_VC12
l VCAT_SQM_VC12
l W_R_FAIL
l WRG_BD_TYPE

A.2.7 EG4
l BD_STATUS
l BUS_ERR
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IN_PWR_ABN
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LASER_MOD_ERR
l LASER_SHUT
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l LSR_NO_FITED
l LSR_WILL_DIE
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l OUT_PWR_ABN
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l TF
l WRG_BD_TYPE

317
A.2.8 EG4P
l BD_STATUS
l BUS_ERR
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETH_PWR_SUPPLY
_FAIL
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IN_PWR_ABN
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LASER_MOD_ERR
l LASER_SHUT
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l LSR_NO_FITED
l LSR_WILL_DIE
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l OUT_PWR_ABN
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l TF
l WRG_BD_TYPE

A.2.9 EM6T
l BD_STATUS
l BUS_ERR
l COMMUN_FAIL
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l WRG_BD_TYPE

318
A.2.10 EM6TA
l BD_STATUS
l BUS_ERR
l COMMUN_FAIL
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l WRG_BD_TYPE

A.2.11 EM6F
l BD_STATUS
l BUS_ERR
l COMMUN_FAIL
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IN_PWR_ABN
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LASER_MOD_ERR
l LASER_SHUT
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l LSR_NO_FITED
l LSR_WILL_DIE
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l OUT_PWR_ABN
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l TF
l WRG_BD_TYPE

319
A.2.12 EM6FA
l BD_STATUS
l BUS_ERR
l COMMUN_FAIL
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_AUTO_LINK_
DOWN
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETH_LOS
l ETH_NO_FLOW
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IN_PWR_ABN
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LASER_MOD_ERR
l LASER_SHUT
l LOOP_ALM
l LPT_CFG_CLOSE-
PORT
l LSR_NO_FITED
l LSR_WILL_DIE
l MAC_EXT_EXC
l MAC_FCS_EXC
l MAC_FCS_SD
l MULTI_RPL_OWNE
R
l OUT_PWR_ABN
l PORT_EXC_TRAFFI
C
l PORTMODE_MIS-
MATCH
l TEMP_ALARM
l TF
l WRG_BD_TYPE

A.2.13 EMS6
l ALM_GFP_dCSF
l ALM_GFP_dLFD
l B3_EXC_VC3
l B3_SD_VC3
l BD_STATUS
l BIP_EXC
l BIP_SD
l BUS_ERR
l COMMUN_FAIL
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_LOS
l ETHOAM_DISCOV
ER_FAIL
l ETHOAM_RMT_CR
IT_FAULT
l ETHOAM_RMT_LO
OP
l ETHOAM_RMT_SD
l ETHOAM_SELF_LO
OP
l EX_ETHOAM_CC_L
OS
l EX_ETHOAM_MPI
D_CNFLCT
l FCS_ERR
l FLOW_OVER
l HARD_BAD
l IN_PWR_ABN
l LAG_PORT_FAIL
l LAG_VC_PORT_FA
IL
l LCAS_FOPR
l LCAS_FOPT
l LCAS_PLCR
l LCAS_PLCT
l LCAS_TLCR
l LCAS_TLCT
l LINK_ERR
l LOOP_ALM
l LP_RDI_VC12
l LP_RDI_VC3
l LP_REI_VC12
l LP_REI_VC3
l LP_SLM_VC12
l LP_SLM_VC3
l LP_TIM_VC12
l LP_TIM_VC3
l LP_UNEQ_VC12
l LP_UNEQ_VC3
l LPT_INEFFECT
l LPT_RFI
l MOD_TYPE_MIS-
MATCH
l MULTI_RPL_OWNE
R
l NO_BD_SOFT
l OUT_PWR_ABN
l PORT_MODULE_O
FFLINE
l TEMP_ALARM
l TU_AIS_VC12
l TU_AIS_VC3
l TU_LOP_VC12
l TU_LOP_VC3
l VCAT_LOA
l VCAT_LOM_VC12
l VCAT_LOM_VC3
l VCAT_SQM_VC12
l VCAT_SQM_VC3
l WRG_BD_TYPE

320
A.2.14 FAN
l BD_STATUS
l FAN_AGING
l FAN_FAIL
l POWER_ALM
l WRG_BD_TYPE

A.2.15 IF1
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l HARD_BAD
l HP_CROSSTR
l HP_LOM
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IF_CABLE_OPEN
l IF_MODE_UNSUP-
PORTED
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l MS_AIS
l MS_CROSSTR
l MS_RDI
l MS_REI
l MSAD_CROSSTR
l MW_CONT_WAVE
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l R_LOC
l R_LOF
l R_LOS
l RS_CROSSTR
l T_LOC
l TEMP_ALARM
l VOLT_LOS
l WRG_BD_TYPE

321
A.2.16 IFU2
l AM_DOWNSHIFT
l BD_STATUS
l BIP_EXC
l BIP_SD
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IF_CABLE_OPEN
l LAG_BWMM
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l LP_RDI
l LP_REI
l LP_UNEQ
l MAC_EXT_EXC
l MAC_FCS_EXC
l MULTI_RPL_OWNE
R
l MW_BER_EXC
l MW_BER_SD
l MW_CFG_MISMAT
CH
l MW_CONT_WAVE
l MW_E1_LOST
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l PORT_EXC_TRAFFI
C
l R_LOC
l R_LOF
l TEMP_ALARM
l TU_AIS
l TU_LOP
l VOLT_LOS
l WRG_BD_TYPE

A.2.17 IFX2
l AM_DOWNSHIFT
l BD_STATUS
l BIP_EXC
l BIP_SD
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l IF_CABLE_OPEN
l LAG_BWMM
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l LP_RDI
l LP_REI
l LP_UNEQ
l MAC_EXT_EXC
l MAC_FCS_EXC
l MULTI_RPL_OWNE
R
l MW_BER_EXC
l MW_BER_SD
l MW_CFG_MISMAT
CH
l MW_CONT_WAVE
l MW_E1_LOST
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l PORT_EXC_TRAFFI
C
l R_LOC
l R_LOF
l TEMP_ALARM
l TU_AIS
l TU_LOP
l VOLT_LOS
l WRG_BD_TYPE
l XPIC_LOS

322
A.2.18 ISU2
l AM_DOWNSHIFT
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l BIP_EXC
l BIP_SD
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l HP_CROSSTR
l HP_LOM
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IF_CABLE_OPEN
l LAG_BWMM
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l LP_RDI
l LP_REI
l LP_UNEQ
l MAC_EXT_EXC
l MAC_FCS_EXC
l MS_AIS
l MS_CROSSTR
l MS_RDI
l MS_REI
l MSAD_CROSSTR
l MULTI_RPL_OWNE
R
l MW_AM_TEST
l MW_BER_EXC
l MW_BER_SD
l MW_CFG_MISMAT
CH
l MW_CONT_WAVE
l MW_E1_LOST
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l PORT_EXC_TRAFFI
C
l R_LOC
l R_LOF
l RS_CROSSTR
l T_LOC
l TEMP_ALARM
l TU_AIS
l TU_LOP
l VOLT_LOS
l WRG_BD_TYPE

323
A.2.19 ISV3
l AM_DOWNSHIFT
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l BIP_EXC
l BIP_SD
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l HP_CROSSTR
l HP_LOM
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IF_CABLE_OPEN
l LAG_BWMM
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l LP_RDI
l LP_REI
l LP_UNEQ
l MAC_EXT_EXC
l MAC_FCS_EXC
l MS_AIS
l MS_CROSSTR
l MS_RDI
l MS_REI
l MSAD_CROSSTR
l MULTI_RPL_OWNE
R
l MW_AM_TEST
l MW_BER_EXC
l MW_BER_SD
l MW_CFG_MISMAT
CH
l MW_CONT_WAVE
l MW_E1_LOST
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l PORT_EXC_TRAFFI
C
l R_LOC
l R_LOF
l RS_CROSSTR
l T_LOC
l TEMP_ALARM
l TU_AIS
l TU_LOP
l VOLT_LOS
l WRG_BD_TYPE
l XPIC_LOS

324
A.2.20 ISX2
l AM_DOWNSHIFT
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l BIP_EXC
l BIP_SD
l DROPRATIO_OVER
l ERPS_IN_PROTEC-
TION
l ETH_CFM_AIS
l ETH_CFM_LOC
l ETH_CFM_MISMER
GE
l ETH_CFM_RDI
l ETH_CFM_UNEXPE
RI
l ETH_EFM_DF
l ETH_EFM_EVENT
l ETH_EFM_LOOPBA
CK
l ETH_EFM_REMFA
ULT
l ETHOAM_SELF_LO
OP
l FLOW_OVER
l HARD_BAD
l HP_CROSSTR
l HP_LOM
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IF_CABLE_OPEN
l LAG_BWMM
l LAG_DOWN
l LAG_MEMBER_DO
WN
l LCS_LIMITED
l LICENSE_LOST
l LOOP_ALM
l LP_RDI
l LP_REI
l LP_UNEQ
l MAC_EXT_EXC
l MAC_FCS_EXC
l MS_AIS
l MS_CROSSTR
l MS_RDI
l MS_REI
l MSAD_CROSSTR
l MULTI_RPL_OWNE
R
l MW_AM_TEST
l MW_BER_EXC
l MW_BER_SD
l MW_CFG_MISMAT
CH
l MW_CONT_WAVE
l MW_E1_LOST
l MW_FEC_UNCOR
l MW_LIM
l MW_LOF
l MW_RDI
l PORT_EXC_TRAFFI
C
l R_LOC
l R_LOF
l RS_CROSSTR
l T_LOC
l TEMP_ALARM
l TU_AIS
l TU_LOP
l VOLT_LOS
l WRG_BD_TYPE
l XPIC_LOS

325
A.2.21 ML1/MD1
l ALM_E1RAI
l ALM_IMA_LIF
l ALM_IMA_LODS
l ALM_IMA_RE_RX_
UNUSABLE
l ALM_IMA_RE_TX_
UNUSABLE
l ALM_IMA_RFI
l ATMPW_UNKNOW
NCELL_EXC
l BD_STATUS
l BUS_ERR
l CES_ACR_LOCK_A
BN
l CES_JTROVR_EXC
l CES_JTRUDR_EXC
l CES_LOSPKT_EXC
l CES_MALPKT_EXC
l CES_MISORDERPK
T_EXC
l CES_RDI
l CES_STRAYPKT_E
XC
l CESPW_OPPOSITE_
ACFAULT
l CESPW_OPPOSITE_
RAI
l CHCS
l HARD_BAD
l IMA_GROUP_LE_D
OWN
l IMA_GROUP_RE_D
OWN
l IMA_TXCLK_MIS-
MATCH
l LCD
l LFA
l LMFA
l LOOP_ALM
l MP_DELAY
l MP_DOWN
l OCD
l POWER_ABNORM
AL
l PPP_LCP_FAIL
l PPP_NCP_FAIL
l T_ALOS
l TEMP_ALARM
l TR_LOC
l UHCS
l UP_E1_AIS
l VC_AIS
l VC_LOC
l VC_RDI
l VP_AIS
l VP_LOC
l VP_RDI
l WRG_BD_TYPE

A.2.22 ODU
l BD_STATUS
l CONFIG_NOSUPPO
RT
l HARD_BAD
l IF_INPWR_ABN
l LOOP_ALM
l POWER_ALM
l RADIO_FADING_M
ARGIN_INSUFF
l RADIO_MUTE
l RADIO_RSL_BE-
YONDTH
l RADIO_RSL_HIGH
l RADIO_RSL_LOW
l RADIO_TSL_HIGH
l RADIO_TSL_LOW
l TEMP_ALARM
l WRG_BD_TYPE

A.2.23 PIU
l BD_STATUS
l HARD_BAD
l POWER_ABNORMAL
l THUNDERALM
l WRG_BD_TYPE

326
A.2.24 PMU
l BAT1TEMP_SENSO
R_FAIL
l BAT2TEMP_SENSO
R_FAIL
l BD_STATUS
l ENVHUM_SENSOR
_FAIL
l ENVTEMP1_SENSO
R_FAIL
l ENVTEMP2_SENSO
R_FAIL
l HARD_BAD
l ODC_BATTERY_C
URRENT_ABN
l ODC_BATTERY_P
WRDOWN
l ODC_DOOR_OPEN
l ODC_HUMI_ABN
l ODC_LOAD_PWRD
OWN
l ODC_MDL_ABN
l ODC_POWER_FAIL
l ODC_SMOKE_OVE
R
l ODC_SURGE_PROT
ECTION_FAIL
l ODC_TEMP_ABN
l ODC_WATER_ALM
l WRG_BD_TYPE

A.2.25 SL1D/SL1DA
l AU_AIS
l AU_LOP
l B1_EXC
l B1_SD
l B2_EXC
l B2_SD
l B3_EXC
l B3_SD
l BD_STATUS
l HARD_BAD
l HP_CROSSTR
l HP_LOM
l HP_RDI
l HP_REI
l HP_SLM
l HP_TIM
l HP_UNEQ
l IN_PWR_HIGH
l IN_PWR_LOW
l J0_MM
l LASER_CLOSE
D
l LASER_MOD_
ERR_EX
l LOOP_ALM
l LSR_BCM_AL
M
l LSR_NO_FITE
D
l LSR_WILL_DIE
l MS_AIS
l MS_CROSSTR
l MS_RDI
l MS_REI
l MSAD_CROSS
TR
l OUT_PWR_AB
N
l R_LOC
l R_LOF
l R_LOS
l RS_CROSSTR
l T_LOC
l TF
l WRG_BD_TYP
E

A.2.26 SP3S/SP3D
l A_LOC
l BD_STATUS
l BIP_EXC
l BIP_SD
l DDN_LFA
l DOWN_E1_AIS
l E1_LOC
l E1_LOS
l HARD_BAD
l HPAD_CROSSTR
l LOOP_ALM
l LP_CROSSTR
l LP_R_FIFO
l LP_RDI
l LP_REI
l LP_RFI
l LP_SLM
l LP_T_FIFO
l LP_TIM
l LP_UNEQ
l T_ALOS
l TU_AIS
l TU_LOP
l UP_E1_AIS
l WRG_BD_TYPE

327
A.2.27 TCU
l BD_STATUS
l BDTEMP_SENSOR_
FAIL
l ENVTEMP_SENSOR
_FAIL
l HARD_BAD
l INTEMP_SENSOR_
FAIL
l ODC_DOOR_OPEN
l ODC_FAN_FAILED
l ODC_SMOKE_OVE
R
l ODC_SURGE_PROT
ECTION_FAIL
l ODC_TEC_ALM
l ODC_TEMP_ABN
l ODC_WATER_ALM
l OUT1TEMP_SENSO
R_FAIL
l OUT2TEMP_SENSO
R_FAIL
l WRG_BD_TYPE

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
Description
The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.
packet capturing/Call History Record/Security redline/inteface
Attribute
Alarm Severity Alarm Type
Major 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
328
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.
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 Cause 1: The frequency deviation of the clock source or the delay of the intermediate
network exceeds the upper threshold.
l Cause 2: The physical link where the traced clock source resides is faulty.
Procedure
Step 1 Handle the alarm according to the alarm parameters.
329
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 B.3.5 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.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
Minor Communication alarm
Parameters
None.
When this alarm occurs, the services on the local NE in the downstream direction are interrupted.
330
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.
Attribute
Critical Communication alarm
Parameters
Name Meaning
Parameter 1 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.
331
Possible Causes
l Cause 1: Timeslot binding is different at the source and sink VCTRUNKs.
l Cause 2: The radio link performance degrades.
l Cause 3: The alarmed board is faulty.
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
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
Major Communication alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the logical port, and the value is always 0x01.
332
Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l 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... Then...
The links are faulty Rectify the fault.
The links are normal Replace the alarmed board.
Step 2 Cause 2: When the LCAS is disabled, the source and the sink VCTRUNKs are configured with
different timeslots or different numbers of paths.
1. Correct the configuration data. For details, see Configuring VCTRUNKs on an Ethernet
Board.
----End
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
333
Name Meaning
Parameter 1, Parameter 2 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.
l After this alarm is cleared, the affected IMA link becomes available.
Possible Causes
l Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,
R_LOF, and MS_AIS.
l Cause 2: The IMA protocol negotiation fails between the two ends.
l Cause 3: The IMA link is faulty.
Procedure
Step 1 Cause 1: The path that carries the IMA link reports the SDH alarms, such as R_LOS,
R_LOF, and MS_AIS.
If... Then...
The path reports any SDH alarm Handle the relevant alarms first.
The path does not report any SDH alarm Go to Cause 2.
Step 2 Cause 2: The IMA protocol negotiation fails between the two ends.
1. Disable the IMA protocol at the two ends.
2. Check the IMA group configuration at the two ends and ensure that the configuration is
consistent.
3. Enable the IMA protocol at the two ends.
4. Then, check whether the alarm clears.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 3.
Step 3 Cause 3: The IMA link is faulty.
1. Replace the board. For details, see 6.6 Replacing the Smart E1 Interface Board.
----End
Related Information
Loss of frame alignment
334
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
Name Meaning
The IMA links are unavailable.
Possible Causes
l Cause 1: The maximum differential delay is configured incorrectly.
l 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.
335
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
Name Meaning
Possible Causes
R_LOF, and MS_AIS.
336
Procedure
R_LOF, and MS_AIS.
If... Then...
consistent.
If... Then...
----End
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
337
Name Meaning
Possible Causes
R_LOF, and MS_AIS.
Procedure
R_LOF, and MS_AIS.
If... Then...
consistent.
If... Then...
----End
Related Information
None.
338
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
Name Meaning
Possible Causes
R_LOF, and MS_AIS.
Procedure
R_LOF, and MS_AIS.
If... Then...
339
consistent.
If... Then...
----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.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.
340
Possible Causes
l Cause 1: The external factors (for example, the climate) cause the degradation of the
working channels.
l Cause 2: There are interferences around the working channels.
l Cause 3: The ODU at the transmit end has abnormal transmit power.
l Cause 4: The ODU at the receive end has abnormal receive power.
Procedure
Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the 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.
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
341
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 Cause 1: The parameters of the MSP protocol are set incorrectly.
l Cause 2: The parameters of the MSP protocol are lost.
Procedure
Step 1 Cause 1: The parameters of the MSP protocol are set incorrectly.
1. Check whether the parameters of the MSP protocol are set correctly.
If... Then...
The parameters are set incorrectly Set the parameters correctly.
The parameters are set correctly Go to the next step.
Step 2 Cause 2: The parameters of the MSP protocol are lost.
1. Check whether the MSP protocol is normal on the network.
2. Check whether the MSP protocol is normal on the network. For details, see Enabling/
Disabling the linear MSP protocol.
If... Then...
The alarm is cleared after the protocol is
restarted
End the alarm handling.
The alarm persists after the protocol is
restarted
Contact Huawei engineers to handle the
alarm.
----End
Related Information
None.
342
A.3.13 APS_INDI
Description
The APS_INDI is an alarm indicating that the MS protection switching occurs.
Attribute
Parameters
Name Meaning
Parameter 1
l 0x01: linear MS protection.
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.
2. Check whether the MSP protocol is in the manual switching state, forced switching state,
or locked switching state. If yes, release the switching and check whether the alarm is
cleared.
3. Check whether the MSP protocol is in the automatic switching state. Do as follows:
a. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the equipment
reports. After the alarms are cleared, wait until the MSP protocol is changed from the
343
automatic switching state to the normal state. Then, check whether the APS_INDI
alarm is cleared.
b. Check whether the service board configured with the MSP protocol is faulty. If yes,
replace the faulty board and then check whether the APS_INDI alarm is cleared.
c. Check whether the currently working system control and cross-connect board is faulty.
If the currently working system control and cross-connect board is faulty and 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.
----End
Related Information
This alarm is also reported upon a packet-based linear MSP switching. For querying the packet-
based Linear MSP group, refer toQuerying the Status of a Packet-based Linear MSP Group.
A.3.14 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.
Attribute
Minor Processing alarm
Parameters
Name Meaning
Parameter 1
When the APS_MANUAL_STOP alarm occurs, the MSP protocol may fail and therefore the
protection switching may fail.
344
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
This alarm is also reported upon a packet linear MSP switching. For enabling/disabling the
packet linear MSP protocol, refer toEnabling/Disabling the Linear MSP Protocol.
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.
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 Cause 1: PW control words mismatch.
l Cause 2: PW types mismatch.
l Cause 3: Fragments are received on the network side.
Procedure
Step 1 Check whether the configuration at the two ends of the PW is consistent. If not, modify the
configuration.
345
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.
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 Cause 1: The opposite NE inserts the AU_AIS alarm.
l Cause 2: The transmit unit of the opposite NE is faulty.
l Cause 3: The receive unit of the local NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE inserts the AU_AIS alarm.
If... Then...
The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.
No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.
Step 2 Cause 2: The transmit unit of the opposite NE is faulty.
1. Replace the line board at the opposite end
346
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm handling.
The alarm persists after replacement Go to the next step.
2. Replace the system control, cross-connect, and timing board at the opposite end.
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.
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 Cause 1: The transmit unit of the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite NE is faulty.
1. Replace the line board at the opposite end.
347
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm handling.
----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.
Attribute
Minor Service alarm
Parameters
None.
When the B1_EXC alarm occurs, the services on the port are interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
348
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 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over
low
Replace the SFP on the opposite NE.
The transmit power of the opposite NE is
normal, but the receive power of the local NE
is close to the value (for example, within 3
dB) of the receiver sensitivity.
The fiber is faulty. Go to the next step.
2. Exchange the core fibers of the optical cables in the receive and transmit directions of 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
fiber.
Ensure that the board is normal.
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 or
RPS_INDI alarm is reported. If yes, clear the alarm.
Step 3 Cause 3: The network clock quality degrades.
1. Check the network clock status of the alarmed NE.
If... Then...
The clock source of the local NE is
different from the clock source of the
opposite NE
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.
The clock of the local NE and the clock
of the opposite NE form a timing loop
This may cause errors and even service
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.
349
If... Then...
The fault is not rectified after the optical
interfaces are looped back
Replace the board where the alarmed
line unit is located on the local NE.
The fault is rectified after the optical
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... Then...
The fault is not rectified after the
multiplexing interface is looped back
Replace the alarmed IF board on the
local NE.
The fault is rectified after the multiplexing
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
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
Minor Service alarm
Parameters
None.
When the B1_SD alarm occurs, the service performance on the port degrades.
350
Possible Causes
board).
Procedure
board).
If... Then...
low
dB) of the receiver sensitivity
channel.
If... Then...
fiber
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is
generated. If yes, clear the alarm.
351
If... Then...
opposite NE
The clock may become asynchronous and
NE.
1. The SDH optical line board of the local NE is faulty. Loop back the optical interfaces of
the NE by using a fiber jumper to locate the fault.
If... Then...
If... Then...
local NE.
opposite NE.
----End
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).
352
Attribute
Major Service alarm
Parameters
None.
The services on the port are interrupted.
Possible Causes
board).
Procedure
board).
If... Then...
low
channel to locate the fault.
If... Then...
fiber
353
If... Then...
opposite NE
NE.
If... Then...
If... Then...
local NE.
opposite NE.
----End
Related Information
354
A.3.21 B2_SD
Description
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
Minor Service alarm
Parameters
None.
The service performance on the port degrades.
Possible Causes
board).
Procedure
board).
If... Then...
low
355
If... Then...
fiber
If... Then...
opposite NE
NE.
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
If... Then...
local NE.
opposite NE.
----End
356
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
Major Service alarm
Parameters
None.
When the B3_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
board).
Procedure
board).
If... Then...
low
357
If... Then...
If... Then...
fiber
If... Then...
opposite NE
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.
If... Then...
358
If... Then...
local NE.
opposite NE.
----End
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
Major Service alarm
Parameters
Name Meaning
Parameter 1 Has a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-3 path that reports the alarm. For example,
0x00 0x01 indicate that the alarm is reported in VC-3 path 1.
The services in the alarmed path have a large number of bit errors.
Possible Causes
l Cause 1: Higher-level bit error alarms occur in the system.
359
l Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical
port).
l Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical
port).
l Cause 4: A board is faulty.
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.
2. Check whether the alarm is cleared.
If... Then...
The alarm persists Go to Cause 2 or Cause 3.
Step 2 Cause 2: The line performance deteriorates (the alarm is reported by an Ethernet optical port).
1. Check whether the transmit power at the opposite site and the receive power at the local
site meet the specifications of the optical ports. For details, see Browsing Current
Performance Events.
If... Then...
The transmit power at the opposite site is
too low
Replace the optical module at the
opposite site.
normal, but the receive power at the local
site is close to the receiver sensitivity (for
example, a difference within 3 dB)
A fiber is faulty. Go to the next step.
2. Exchange the optical fibers in the receive and transmit directions of an optical path segment.
If... Then...
The number of bit errors changes Go to the next step.
The number of bit errors does not change Go to Cause 4.
3. If a fiber is faulty, check whether the fiber jumper from the equipment to the 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... Then...
Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet electrical port).
360
1. Check whether the cable grounding, cable connectors, and cables are damaged. If yes,
replace the faulty cables.
If... Then...
Step 4 Cause 4: A board is faulty.
1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.
If... Then...
Ethernet port is looped back
Replace the alarmed Ethernet processing
board at the local site.
The fault is rectified after the Ethernet
port is looped back
Replace the Ethernet processing board at
the opposite site.
----End
Related Information
None.
A.3.24 B3_SD
Description
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
Minor Service alarm
Parameters
None.
The service performance on the port degrades.
361
Possible Causes
board).
Procedure
board).
If... Then...
low
If... Then...
fiber
362
If... Then...
opposite NE
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.
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
If... Then...
local NE.
opposite NE.
----End
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).
363
Attribute
Minor Service alarm
Parameters
Name Meaning
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 Cause 1: Higher-level bit error alarms occur in the system.
port).
port).
Procedure
Step 1 Cause 1: Higher-level bit error alarms occur in the system.
1. Check whether the local or upstream site detects B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarms. If yes, clear the higher-level alarms.
If... Then...
The alarm persists Go to Cause 2 or Cause 3.
Performance Events.
364
If... Then...
too low
opposite site.
2. Exchange the optical fibers in the receive and transmit directions of an optical path segment.
If... Then...
The number of bit errors changes Go to the next step.
The number of bit errors does not change Go to Cause 4.
If... Then...
If... Then...
1. Perform an inloop at the Ethernet port that connects to the alarmed VC-3 path.
If... Then...
Ethernet port is looped back
Replace the alarmed Ethernet processing
board at the local site.
The fault is rectified after the Ethernet
port is looped back
Replace the Ethernet processing board at
the opposite site.
----End
Related Information
None.
365
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 Cause 1: The temperature sensor of battery group 1 is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 1 is faulty.
1. Replace the temperature sensor of battery group 1.
If... Then...
The alarm clears End the alarm handling.
Step 2 Cause 2: The control board of the cabinet is faulty.
1. Replace the cabinet.
If... Then...
Step 3 Cause 3: Cables are misconnected or damaged.
366
1. Replace damaged cables.
2. Connect cables correctly.
Step 4 Cause 4: The temperature sensor is not installed.
1. Install the temperature sensor.
----End
Related Information
None.
A.3.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 Cause 1: The temperature sensor of battery group 2 is faulty.
l Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 2 is faulty.
1. Replace the temperature sensor of battery group 2.
If... Then...
367
If... Then...
If... Then...
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
Minor Equipment alarm
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the slot.
368
When the BD_NOT_INSTALLED alarm occurs, the physical board in this slot cannot work.
Possible Causes
Cause 1: The logical board is not added in the corresponding logical slot.
Procedure
Step 1 Cause 1: The logical board is not added in the corresponding logical slot.
1. Configure the logical board.
----End
Related Information
None.
A.3.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 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect
slot.
l Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not
connected properly.
l Cause 3 of the alarm reported by a board of the IDU: The slot is faulty.
l Cause 4 of the alarm reported by a board of the IDU: A certain board is faulty.
If the alarm is reported by the ODU, the possible causes are as follows:
369
l Cause 1 of the alarm reported by the ODU: The other alarms are generated.
l Cause 2 of the alarm reported by the ODU: The ODU is faulty.
Procedure
Step 1 Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot.
1. Check whether the logical slot and physical slot of the alarmed board are consistent. For
details, see 4.2 Checking the Board Status.
If... Then...
The alarmed board is installed in an
incorrect slot
Install the board in a correct slot.
The alarmed board is installed 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... Then...
The alarm is cleared after the board is
removed and inserted
The fault is rectified. End the alarm
handling.
The alarm persists after the board is
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.
NOTE
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.
If... Then...
replaced
handling.
replaced
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.
370
If... Then...
The IF board reports any of the preceding alarms Clear the alarm immediately.
The IF board does not report any of the preceding
alarms
Replace the alarmed ODU.
Step 6 Cause 2 of the alarm reported by the ODU: The ODU is faulty.
1. Replace the alarmed ODU.
----End
Related Information
None.
A.3.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 Cause 1: The board temperature sensor is faulty.
l Cause 4: The board temperature sensor is not installed.
Procedure
Step 1 Cause 1: The board temperature sensor is faulty.
1. Replace the board temperature sensor.
371
If... Then...
If... Then...
Step 4 Cause 4: The board temperature sensor is not installed.
1. Install the board temperature sensor.
----End
Related Information
None.
A.3.31 BGPBACKTRANSITION
Description
The BGPBACKTRANSITION alarm indicates that a Border Gateway Protocol (BGP)
connection is interrupted because the status of the BGP peer changes.
Attribute
Parameters
372
Name Meaning
Parameters 1-4 Indicate the IPv4 address of the BGP peer.
Parameters 5-7 Indicate the error code contained in the BGP notification returned during
the last BGP connection interruption.
Parameters 8-11 Indicate the status of the BGP peer.
Parameters 12-15 Indicate the instance ID.
Parameters 16-19 Indicate the address family.
Parameters 20-23 Indicate the sub-address family.
Parameters 24-27 Indicate the address type of the BGP peer.
Parameters 28-48 Indicate the IPv6 address of the BGP peer.
Parameters 49-52 Indicate the cause of the BGP connection interruption.
Parameters 53-56 Indicate the local interface index.
Parameters 57-120 Indicate the local interface name.
The BGP connection is interrupted, routes become unreachable, and services are interrupted.
Possible Causes
l Cause 1. The BGP configurations change.
l Cause 2: There is no reachable IP route to the BGP peer.
Procedure
Step 1 Cause 1. The BGP configurations change.
1. Ensure that the BGP configurations are consistent at the local end and the BGP peer.
Step 2 Cause 2: There is no reachable IP route to the BGP peer.
1. Ping the public IP address of the BGP peer to check whether there is a reachable IP route
to the BGP peer. If there is no reachable IP route to the BGP peer, go to the next step.
2. Check whether the link to the BGP peer is faulty, for example, whether an ETH_LOS alarm
is reported. If the link is faulty, rectify the fault.
3. Ensure that the IGP configurations between the local end and the BGP peer are correct.
----End
373
Related Information
None
A.3.32 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating that the board is in BIOS state.
Attribute
Major Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the board that is in BIOS state.
The services on the alarmed board are interrupted.
Possible Causes
l Cause 1: The board software is lost.
l Cause 2: The board software becomes abnormal.
l Cause 3: The board is reset for three consecutive times.
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.
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.33 BIP_EXC
374
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
Minor Service alarm
Parameters
None.
When the BIP_EXC alarm occurs, the service on the alarmed path is interrupted.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio link
along which the E1 service signal travels. If yes, clear the alarm immediately.
The common line performance degradation alarms are as follows:
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,
RPS_INDI, MW_BER_EXC, and MW_BER_SD.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the service
signal. If yes, clear the alarm immediately.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the board where the E1 service unit is located. Then, check whether the alarm
is cleared.
375
If... Then...
The alarm persists Replace the system control and cross-connect board.
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
The alarm parameters have the meanings listed in Table A-3 when EMS6 board report the alarm.
Table A-3 Alarm Parameters of EMS6
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the path that reports the
alarm. For example, 0x00 0x01 indicate that
the alarm is reported in path 1.

A.3.34 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
preset BIP_SD alarm threshold (10
-6
by default) and lower than the preset BIP_EXC alarm
threshold (10
-3
by default).
Attribute
Minor Service alarm
Parameters
None.
376
When the BIP_SD alarm occurs, the service on the alarmed path degrades.
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio link
along which the E1 service signal travels. If yes, clear the alarm immediately.
The common line performance degradation alarms are as follows:
B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, B3_SD, MW_FEC_UNCOR,
RPS_INDI, MW_BER_EXC, and MW_BER_SD.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the service
signal.
If... Then...
An alarm occurs Clear the alarm immediately.
No alarm occurs Ensure that the board is normal.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the board where the E1 service unit is located. Then, check whether the alarm
is cleared.
If... Then...
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the Hybrid IF board. Then, check whether the alarm is cleared.
If... Then...
377
If... Then...
----End
Related Information
Table A-4 Alarm Parameters of EMS6
Name Meaning
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 path 1.

A.3.35 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
Name Meaning
378
Name Meaning
Parameter 2, Parameter 3 Indicates the type of the BOOTROM damage.
l 0x00, 0x01: damage of the basic BIOS
l 0x00, 0x02: damage of the extended BIOS
Parameter 4, Parameter 5 The values are always 0xff 0xff.
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 When the NE is already started, the BOOTROM_BAD alarm does not affect the system
and services.
l 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 Cause 1: The basic BIOS is damaged.
l Cause 2: The extended BIOS is damaged.
l Cause 3: The BOOTROM database is damaged.
l Cause 4: The system control switch and timing boardis faulty.
Procedure
Step 1 Replace the alarmed board.
----End
Related Information
None.
A.3.36 BUS_ERR
Description
The BUS_ERR alarm indicates bus errors. This alarm occurs when the bus becomes abnormal.
Attribute
Critical Equipment alarm
379
Parameters
Name Meaning
Parameter 1 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
Indicates the ID of the bus that has errors.
Parameter 3
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 Cause 1: The board is not properly inserted.
l Cause 2: A certain board is faulty.
380
Procedure
Step 1 Cause 1: The board is not properly inserted.
1. Remove and insert the board.
1. Perform a cold reset on the alarmed board. Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Replace the alarmed board.
----End
Related Information
Table A-5 Alarm parameters of EMS6
Name Meaning
Parameter 1 Indicates the bus error type.
0x10: The Serdes bus of the GE bridge is
faulty.

A.3.37 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
Minor Service alarm
Parameters
Name Meaning
Parameter 1 to Parameter 4
Indicate the index of PW that carries the services associated with
the ACR clock source.
381
Name Meaning
Parameter 5 Indicates clock mode.
l 0x01: tracing mode.
l 0x02: holdover mode.
l 0x03: free-run mode.
Parameter 6 Indicates whether the clock is locked.
l 0x00: unlocked.
l 0x01: locked.
Service quality is affected.
Possible Causes
l Cause 1: CES ACR services are unavailable or have alarms.
l Cause 2: The network is unstable.
l Cause 3: NEs on the service path are abnormal.
Procedure
Step 1 Cause 1: CES ACR services are unavailable or have alarms.
1. Query the CES services associated with the ACR clock source. For details, see Configuring
the Primary Clock for an ACR Clock Domain.
2. Check whether these services have alarms. For details, see 4.3.1 Browsing Current
Alarms.
Step 2 Cause 2: The network is unstable.
1. Check for jitters and delays on the network. Query service performance statistics. For
details, see 4.3.3 Browsing Current Performance Events.
2. Analyze service performance statistics. If the network is unstable, rectify the faults on the
network, or switch the affected services to a stable network.
Step 3 Cause 3: NEs on the service path are abnormal.
1. Query alarms reported by the NEs on the service path. For details, see 4.3.1 Browsing
Current Alarms.
2. Handle the alarms. For details, see A.3 Alarms and Handling Procedures.
----End
Related Information
None.
382
A.3.38 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
Name Meaning
Parameter 1 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.
l This alarm does not affect the services. If the protection channel fails at this time, the
services are interrupted.
Possible Causes
l Cause 1: An external command is issued to trigger switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
l 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.
l Cause 3: The attributes of the MSP protection group are incorrectly configured.
l 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. Check the switching status of the protection group.
383
If... Then...
The MSP is in the state of manual
switching, forced switching, or exercise
switching
Clear the switching status. Check whether
the alarm is cleared. If the alarm persists,
go to Step 2.
The MSP is not in any of the preceding
switching state
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,
R_LOF, MS_AIS, or B2_EXC alarm
The MSP protection group changes to the
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
switching state
Go to the next step.
2. Check the method for setting the revertive mode of the protection group.
If... Then...
Revertive Mode is set to Revertive 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.
384
If... Then...
Revertive Mode is set to Non-
Revertive
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.
Step 3 Cause 3: The attributes of the MSP protection group are incorrectly configured.
1. 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.
2. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The interface board is faulty.
1. Check whether the interface board that is configured with the packet linear MSP is
functioning properly.
2. If a hardware alarm such as HARD_BAD occurs on the interface board, clear the alarm
immediately.
3. Replace the interface board. For details, see 6 Part Replacement.
----End
Related Information
None.
A.3.39 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
385
Parameters
Name Meaning
Parameter 1 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. Determine the ID of the MSP protection group whose APS protocol is stopped according
to alarm parameters.
2. Restart the MSP protocol for the protection group.
----End
Related Information
None.
A.3.40 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.
386
The buffer area does not have sufficient space for the received frames. As a result, packets are
discarded.
Possible Causes
l Cause 1: The size of buffer area is set to a low value.
l 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. Query the size of buffer area. For details, see Querying CES Service Information.
2. Determine whether the size can be increased according to network planning. If yes, change
the size to a greater value. For details, see Managing CES Services.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are 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.41 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.
387
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
l Cause 3: The link is looped.
l Cause 4: The link is congested.
l Cause 5: The size of buffer area is set to a low value.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are 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. Query the size of buffer area. For details, see Querying CES Service Information.
2. Determine whether the size can be increased according to network planning. If yes, change
the size to a greater value. For details, see Managing CES Services.
----End
Related Information
None.
A.3.42 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).
388
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 Cause 1: MSP is incorrectly configured.
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.
2. Ensure that MSP is configured correctly. Then, check whether the alarm is cleared. If the
alarm persists, go to Step 2.
1. Check whether the interface boards on which MSP is configured are functioning properly
on the local and opposite NEs.
immediately.
3. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the System
Control, Switching and Timing Board.
----End
Related Information
None.
A.3.43 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
389
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).
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 Cause 1: Different protection modes are configured at both ends of a protection group.
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 Packet-based Linear MSP
Group.
1. Check whether the interface boards on which MSP is configured are functioning properly
on the local and opposite NEs.
immediately.
3. If the alarm persists, replace the interface board. For details, see 6.10 Replacing the System
Control, Switching and Timing Board.
----End
Related Information
None.
390
A.3.44 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.
Attribute
Parameters
None.
When this alarm occurs, all 1s are inserted and services are interrupted.
Possible Causes
Procedure
----End
Related Information
Packets are lost when the sequence numbers of received packets are greater than expected.
391
A.3.45 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
Parameters
None.
A deformed frame is discarded once it is detected. As a result, the packet loss rate increases and
Possible Causes
l Cause 1: The RTP head enabling status is different between the two ends of the PW.
l Cause 2: Bit errors occur on the link.
Procedure
Step 1 Cause 1: The RTP head enabling status is different between the two ends of the PW.
1. Set the RTP head enabling status to the same on the two ends of the PW. For details, see
Modifying CES Service Parameters.
Step 2 Cause 2: Bit errors occur on the link.
----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.
392
A.3.46 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.
Possible Causes
Procedure
1. See 5.3 Troubleshooting the Radio Link.
----End
Related Information
Packets are disordered when the sequence numbers of received packets are smaller than
expected.
393
A.3.47 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
Procedure
1. See 5.3 Troubleshooting the Radio Link.
----End
Related Information
None.
394
A.3.48 CES_STRAYPKT_EXC
Description
The CES_STRAYPKT_EXC is an alarm indicating that, in a time unit, the number of error
packets in CES services crosses the threshold. This alarm occurs when the board detects that the
number of error packets in CES services per second crosses the specified threshold.
Attribute
Parameters
None.
An error packet is discarded once it is detected. As a result, the packet loss rate increases and
Possible Causes
Cause 1: Links are misconnected.
Procedure
Step 1 Cause 1: Links are misconnected.
1. Check the link configuration and rectify the fault.
----End
Related Information
Incorrect packets are received when the tracing source field in the RTP head is different from
expected.
A.3.49 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.
395
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.3.50 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.
396
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.51 CFCARD_FAILED
Description
The CFCARD_FAILED is an alarm indicating that the operation on the CF card fails.
Attribute
Parameters
None.
When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF card
or be restored from the CF card. This alarm may cause rollback of the package loading upgrade.
Possible Causes
l Cause 1: The CF card fails to be initialized.
l Cause 2: The file system of the CF card does not match.
l Cause 3: The system control and communication board is faulty, and the file system of the
CF card fails to be created.
Procedure
Step 1 Cause 1: The CF card fails to be initialized.
397
Cause 2: The file system of the CF card does not match.
1. Replace the CF card and check whether the alarm is cleared.
If... Then...
Yes End the alarm handling.
No Go to Cause 3.
Step 2 Cause 3: The system control and communication board is faulty, and the file system of the CF
card fails to be created.
1. Check whether the HARD_BAD alarm occurs on the system control and communication
board.
2. If yes, perform a cold reset on the system control and communication board. Then, check
whether the alarm is cleared.
If... Then...
No Replace the system control and communication board.
----End
Related Information
None.
A.3.52 CFCARD_OFFLINE
Description
The CFCARD_OFFLINE is an alarm indicating that the CF card is offline.
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 Cause 1: The CF card is not inserted.
398
l Cause 2: The CF card is in poor contact with the system control and communication board.
l Cause 3: The CF card is faulty.
l Cause 4: The system control and communication board is faulty.
Procedure
Step 1 Cause 1: The CF card is not inserted.
1. Check whether the CF card is installed on the system control and communication board.
If... Then...
No Install the CF card.
Yes Go to Cause 2.
Step 2 Cause 2: The CF card is in poor contact with the system control and communication board.
1. Check whether the CF card is loosened. If yes, re-insert the CF card.
If... Then...
No Go to Cause 3.
Step 3 Cause 3: The CF card is faulty.
1. Replace the CF card.
If... Then...
No Go to Cause 4.
Step 4 Cause 4: The system control and communication board is faulty.
1. Check whether the HARD_BAD alarm occurs on the system control and communication
board.
2. If yes, perform a cold reset on the system control and communication board. Then, check
3. If the alarm persists, replace the system control and communication board.
----End
Related Information
None.
399
A.3.53 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 Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM
port.
l Cause 2: The ATM physical-layer processing chip of the board is faulty.
Procedure
Step 1 Cause 1: A few bit errors occur in the receive tunnel corresponding to the alarmed ATM port.
1. On the NMS, check whether the receive tunnel reports any alarms about excessive bit errors,
such as B1_SD, B2_SD, and B3_SD.
2. On the NMS, check whether the service is looped.
3. If yes, modify the service configuration to release the loop, and then check whether the
alarm is cleared.
Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the CHCS alarm and check whether the alarm
is cleared. For details, see 8.6.1 Cold Reset.
2. Optional: If the CHCS alarm persists after the cold reset, replace the alarmed board and
check whether the alarm is cleared. For details, see 6.6 Replacing the Smart E1 Interface
Board.
NOTE
Board replacement is not recommended because the alarm does not affect the services.
----End
400
Related Information
None.
A.3.54 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a clock locking failure.
Attribute
Parameters
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 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.
Possible Causes
l Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical
synchronization mode.
l Cause 2: The physical link where the clock source resides is faulty in physical
l Cause 3: Frequency deviation of the clock source has crossed the upper threshold in IEEE
1588v2 synchronization mode.
l Cause 4: The physical link where the clock source resides is faulty in IEEE 1588v2
401
Procedure
Step 1 Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical
1. Check whether high-level bit error alarms or performance events have been reported on
the NMS. If yes, handle them immediately.
2. 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.
3. 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. If there is an external clock source, check whether the NE reports the SYNC_C_LOS alarm.
If yes, clear the alarm immediately.
2. If the CLK_LOCK_FAIL alarm persists, 6.10 Replacing the System Control, Switching
and Timing Board.
Step 3 Cause 3: Frequency deviation of the clock source has crossed the upper threshold in IEEE 1588v2
1. Check whether high-level bit error alarms or performance events have been reported on
the NMS. If yes, handle them immediately.
2. 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
1. If the SYN_BAD alarm exists, clear the alarm immediately.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
A.3.55 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
402
Parameters
Name Meaning
Parameter 1
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 Cause 1: The system clock source priority table is not configured.
l Cause 2: All the clock sources in the clock source priority table fail.
Procedure
Step 1 Cause 1: The system clock source priority table is not configured.
1. Configure the system clock source priority table. For details, see Configuring the Clock
Sources.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Troubleshoot the synchronization sources that are listed in the clock source priority table.
If... Then...
The synchronization source is an
external clock
Handle the EXT_SYNC_LOS alarm.
The synchronization source is a line
clock
Handle the alarm that occurs on the line
board.
The synchronization source is an IF
clock
Handle the alarm that occurs on the IF board.
The synchronization source is a
tributary clock
Handle the alarm that occurs on the tributary
board.
Ethernet clock
Handle the alarm that occurs on the Ethernet
board.
----End
403
Related Information
None.
A.3.56 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
Name Meaning
Parameter 1
Indicates the ID of the port. The value is always 0x01.
Parameter 2, Parameter 3
Indicates the ID of the path on which the alarm is generated.
Parameter 2 is always 0x00. Parameter 3 has the following
meanings:
0x03: inter-board Ethernet communication
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 Cause 1: A certain board is reset.
l Cause 2: A board and the backplane are connected improperly.
l Cause 4: A slot is faulty.
404
l Cause 5: When the active and standby system control boards switch over, communication
between them are interrupted transiently.
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... Then...
handling.
replaced.
Clear the alarm according to the solution
for the alarm that is generated when a
board is faulty.
1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see 6
Part Replacement.
If... Then...
replaced
handling.
replaced
Clear the alarm according to the solution
for the alarm that is generated when a slot
is faulty.
Step 4 Cause 3: A slot is faulty.
1. Contact Huawei engineers to handle the faulty slot.
NOTE
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.
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.
Step 5 Cause 5: When the active and standby system control boards switch over, communication
between them are interrupted transiently.
1. It is normal that this alarm is reported during the switchover, so this alarm does not need
to be handled.
----End
Related Information
None.
405
A.3.57 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
Name Meaning
Parameters 1 to 5
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.3.58 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.
406
Attribute
Parameters
Name Meaning
Parameter 1 Indicates that the configuration data does not meet the requirements.
l 0x01: The frequency is set incorrectly.
l 0x02: The T/R spacing is set incorrectly.
l 0x03: The transmit power is set incorrectly.
l 0x04: The ATPC threshold is set incorrectly.
l 0x05: The bandwidth is set incorrectly.
l 0x06: The modulation mode is set incorrectly.
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 Cause 1: The type and configuration parameters of the ODU do not match the requirements.
l Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only
when Parameter 1 is 0x03.)
NOTE
Perform the handling procedure of Cause 2 if the following conditions are met: The AM function is enabled
on the radio link; the transmit power configured for the ODU is lower than the maximum rated power in
AM guaranteed capacity mode.
Procedure
Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.
1. Determine the parameter that does not meet the requirement according to the alarm
parameter. Then, handle the fault accordingly.
407
If... Then...
The alarm parameter takes a value from
0x01 to 0x03
Perform the operation described in Step
1.2.
The alarm parameter takes a value from
0x04 to 0x06
Perform the operation described in Step
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... Then...
The parameters meet the requirements of
network planning
Use the ODU of the proper model.
The parameters do not meet the
requirements of network planning
Modify the ODU interface parameters.
3. 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
network planning
Replace the IF board.
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
power needs to be changed
Perform a cold reset for the alarmed
ODU.
The conditions are met but the transmit
power does not need to be changed
Change the parameters of ODU interfaces
to recover the original value of transmit
power.
----End
Related Information
None.
408
A.3.59 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
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.60 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system
database.
Attribute
Parameters
None.
409
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
Cause: The database processing fails or the database is damaged.
Procedure
Step 1 Obtain NE backup data (backed up periodically by the U2000 or backed up manually) or NE
service configuration information.
Step 2 Contact Huawei technical support engineers for handling the alarm.
Step 3 In case of emergency, 6.10 Replacing the System Control, Switching and Timing Board and
restore the database or reconfigure service data.
----End
Related Information
None.
A.3.61 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protection
mode.
Attribute
Critical Processing alarm
Parameters
None.
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.
410
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, Switching and Timing Board.
----End
Related Information
None.
A.3.62 DCNSIZE_OVER
Description
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 If these parameters are 0xFF 0xFF, the NE works in L2DCN mode.
Otherwise, these parameters indicate the current size of the DCN
subnet.
l Some NEs become unreachable to the NMS because DCN packets cannot be forwarded
timely due to insufficient CPU resources.
l The DCN network is prone to route flapping and storms.
Possible Causes
Cause 1: The number of NEs on an L3 DCN subnet exceeds 400.
Cause 2: The number of NEs equipped with CSH/CST boards on an L2 DCN subnet exceeds
30.
411
Procedure
Step 1 Replan the DCN network based on actual networking conditions.
----End
A.3.63 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 Cause 1: The interconnected user equipment is faulty.
l Cause 2: The service frame format is configured incorrectly.
l Cause 3: The alarmed board has hardware faults.
Procedure
Step 1 Cause 1: The interconnected user equipment is faulty.
1. Troubleshoot the interconnected user equipment.
Step 2 Cause 2: The service frame format is configured incorrectly.
1. Set the E1 frame format of the local port to the same as that of the opposite port.
Step 3 Cause 3: The alarmed board has hardware faults.
1. Check whether the alarmed board also reports any hardware alarms, such as
HARD_BAD.
2. If yes, perform a cold reset on the alarmed board and check whether the DDN_LFA alarm
is cleared.
412
NOTICE
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.64 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.
Possible Causes
l Cause 1: The opposite NE transmits the E1_AIS alarm.
l Cause 2: An upstream alarm triggers this alarm.
l Cause 3: 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.
413
If... Then...
The opposite NE reports the UP_E1_AIS
or T_ALOS alarm
Clear the alarm immediately.
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: An upstream alarm triggers this alarm.
1. Clear the following upstream alarms immediately if there are any.
Upstream alarms that may cause a DOWN_E1_AIS alarm include R_LOS, R_LOF,
MS_AIS, AU_AIS, AU_LOP, MW_LOF, MW_LIM, R_LOF, MS_AIS, AU_AIS,
AU_LOP, MW_LOF, MW_LIM, and R_LOF.
Step 3 Cause 3: On the local NE, the receive unit of the tributary board or the system control and cross-
connect board is faulty.
1. Replace the board where the alarmed tributary unit is located. Then, check whether
the alarm is cleared.
If... Then...
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 in Table A-6.
Table A-6 Alarm Parameters of EFP8
Name Meaning
Parameter 1 0x01, indicates optical interface number.
Parameter 2, Parameter 3 Indicates the number of the path.

A.3.65 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.
414
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1
Indicates the direction in which traffic crosses the threshold.
l 0x00: The ratio of lost packets in the receive direction exceeds the threshold.
l 0x01: The ratio of lost packets in the transmit direction exceeds the threshold.
Service packet loss occurs.
Possible Causes
l Cause 1: Service configuration is incorrect.
l Cause 2: Actual traffic exceeds the configured port bandwidth or committed information
rate (CIR).
Procedure
Step 1 Cause 1: Service configuration is incorrect.
1. Check and reconfigure services according to the network plan.
Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.
1. 4.6.2 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.
2. If the port bandwidth is too low, follow instructions in Modifying the Port Policy to increase
port bandwidth or expand the network.
----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.66 E1_LOC
415
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.
Attribute
Parameters
None.
When the E1_LOC occurs, the service is not affected.
Possible Causes
l Cause 1: The opposite NE is faulty.
l Cause 2: The wiring sequence of the cable is incorrect.
l Cause 3: The receive unit of the tributary board on the local NE is faulty.
l Cause 4: The input E1 signal has an abnormal waveform.
Procedure
Step 1 Cause 1: The opposite NE is faulty.
1. Rectify the fault on the opposite NE.
Step 2 Cause 2: The wiring sequence of the cable is incorrect.
1. Redo the cable.
Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.
1. Replace the board where the line unit is located.
Step 4 Cause 4: The input E1 signal has an abnormal waveform.
1. Check whether any external interference causes the abnormal waveform of the E1 signal.
If... Then...
There is the external interference The fault is rectified. End the alarm handling.
There is no external interference Contact Huawei engineers.
----End
Related Information
None.
416
A.3.67 E1_LOS
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 Cause 1: The cable is not connected or the cable is faulty.
l Cause 3: The tributary board on the local NE is faulty.
Procedure
Step 1 Cause 1: The cable is not connected or the cable is faulty.
1. Check whether the cable is connected properly.
If... Then...
The cable is not connected properly Connect the cable properly.
The cable is prepared incorrectly Redo the cable.
Step 3 Cause 3: The tributary board on the local NE is faulty.
1. Replace the board where the tributary unit is located.
----End
Related Information
None.
417
A.3.68 ELAN_SMAC_FLAPPING
Description
The ELAN_SMAC_FLAPPING alarm indicates that the source MAC address learned by a
bridge-based or PW-carried E-LAN service flaps. This alarm is reported when two ports that
carry a bridge-based or PW-carried E-LAN service learn the same source MAC address.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameters 1 to 6
Indicate the source MAC address that flaps.
Indicate the VLAN ID.
Parameter 9
Indicate the type of the port that learns the source MAC address
before the flapping occurs.
l 0: UNI
l 1: NNI
Parameters 10 to 13
Indicate the ID of the UNI or NNI that learns the source MAC
address before the flapping occurs.
Parameter 14
Indicate the type of the port that learns the source MAC address
after the flapping occurs.
l 0: UNI
l 1: NNI
Parameters 15 to 18
Indicate the ID of the UNI or NNI that learns the source MAC
address after the flapping occurs.
A network storm may occur.
418
Possible Causes
Cause: A loop exists on a UNI or NNI that carries the E-LAN service.
Procedure
Step 1 Determine the E-LAN service according to the service ID on the NMS.
Step 2 Check the E-LAN service path by referring to instructions in Detecting an E-LAN Service Loop.
----End
Related Information
None
A.3.69 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 Cause 1: The ambient humidity sensor is faulty.
l Cause 4: The ambient humidity sensor is not installed.
Procedure
Step 1 Cause 1: The ambient humidity sensor is faulty.
1. Replace the ambient humidity sensor.
419
If... Then...
If... Then...
Step 4 Cause 4: The ambient humidity sensor is not installed.
1. Install the ambient humidity sensor.
----End
Related Information
None.
A.3.70 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.
420
Possible Causes
l Cause 1: The ambient temperature sensor is faulty.
l Cause 4: The ambient temperature sensor is not installed.
Procedure
Step 1 Cause 1: The ambient temperature sensor is faulty.
1. Replace the ambient temperature sensor.
If... Then...
If... Then...
Step 4 Cause 4: The ambient temperature sensor is not installed.
1. Install the ambient temperature sensor.
----End
Related Information
None.
A.3.71 ENVTEMP1_SENSOR_FAIL
Description
The ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1 of
the cabinet fails.
421
Attribute
Parameters
None.
Ambient temperature data 1 of the PMU cannot be collected.
Possible Causes
l Cause 1: Ambient temperature sensor 1 is faulty.
l Cause 4: Ambient temperature sensor 1 is not installed.
Procedure
Step 1 Cause 1: Ambient temperature sensor 1 is faulty.
1. Replace ambient temperature sensor 1.
If... Then...
If... Then...
Step 4 Cause 4: Ambient temperature sensor 1 is not installed.
1. Install ambient temperature sensor 1.
----End
422
Related Information
None.
A.3.72 ENVTEMP2_SENSOR_FAIL
Description
The ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2 of
the cabinet fails.
Attribute
Parameters
None.
Ambient temperature data 2 of the PMU cannot be collected.
Possible Causes
l Cause 1: Ambient temperature sensor 2 is faulty.
l Cause 4: Ambient temperature sensor 2 is not installed.
Procedure
Step 1 Cause 1: Ambient temperature sensor 2 is faulty.
1. Replace ambient temperature sensor 2.
If... Then...
423
If... Then...
Step 4 Cause 4: Ambient temperature sensor 2 is not installed.
1. Install ambient temperature sensor 2.
----End
Related Information
None.
A.3.73 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.
Attribute
Minor Equipment Alarm
Parameters
Name Meaning
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.
424
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. Locate the faulty node on the ERPS ring based on the alarm parameters.
2. Locate the ERPS blocked port on the faulty node.
3. Rectify the fault.
----End
Related Information
This alarm is not reported on an ERPS V2 network where virtual channels are disabled.
A.3.74 ETH_APS_LOST
Description
The ETH_APS_LOST is an alarm indicating that the APS frame is lost. This alarm is reported
when an ingress/egress node of a bidirectional tunnel does not receive any APS frames from the
protection channel.
Attribute
Parameters
None.
When this alarm occurs, the APS protection may fail.
Possible Causes
l Cause 1: The opposite NE is not configured with the APS protection.
l Cause 2: The APS protection group is deactivated.
l Cause 3: The settings of the APS protection group differ between the two ends.
l Cause 4: The service on the protection channel is interrupted.
425
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... Then...
The opposite NE is not configured with the APS protection Go to the next step.
The opposite NE is configured with the APS protection Go to Cause 2.
2. Create a matching APS protection group on the opposite NE, and activate the APS protocol.
Check whether the alarm clears.
3. If the alarm persists, proceed to cause 4.
Step 2 Cause 2: The APS protection group is deactivated.
1. Check whether the APS protocol is activated at both ends.
If... Then...
The APS protocol is deactivated at one end Activate the APS protocol at the end.
The APS protocol is activated at both ends Go to Cause 3.
2. Check whether the alarm clears. If the alarm persists, go to Cause 3.
Step 3 Cause 3: The settings of the APS protection group differ between the two ends.
1. On the NMS, check whether the settings of the APS protection group are the same at the
two ends. If the settings differ between the two ends, change them to the same. Then,
deactivate and activate the APS protection group at the two ends.
2. Check whether the alarm clears. If the alarm persists, go to Cause 4.
Step 4 Cause 4: The service on the protection channel is interrupted.
1. Check whether the protection channel reports an alarm related to signal loss or signal
degrade, such as ETH_LOS. If yes, clear the alarm immediately.
----End
Related Information
None.
A.3.75 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.
426
Attribute
Parameters
None.
When this alarm occurs, service protection fails.
Possible Causes
l Cause 1: The configured working and protection paths differ between the two ends.
l Cause 2: The physical link is connected incorrectly.
Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
1. Check whether the APS settings at the two ends are the same. For details, see Querying
MPLS APS Status.
2. 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.
3. If the alarm persists, go to Cause 2.
Step 2 Cause 2: The physical link is connected incorrectly.
1. Check whether the fiber or cable is correctly connected between the two ends. If not,
connect the fiber or cable properly.
----End
Related Information
None.
A.3.76 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.
427
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.Cause 2: APS
fails due to other reasons.
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.
Step 2 Cause 2: APS fails due to other reasons.
1. Reactivate APS protection at both ends.
----End
Related Information
None.
A.3.77 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
428
Parameters
Name Meaning
Parameter 1
Indicates the specific difference.
l 0x01: Indicates that the switching type is different.
l 0x02: Indicates that the switching direction is different.
l 0x03: Indicates that the revertive mode is different.
This alarm may cause the APS protection failure, and therefore the service protection fails.
Possible Causes
l Cause 1: The switching type is different.
l Cause 2: The switching direction is different.
l 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
Related Information
None.
A.3.78 ETH_AUTO_LINK_DOWN
Description
The ETH_AUTO_LINK_DOWN alarm indicates that an Ethernet port is automatically switched
to the link down state upon a fault detected by link-state pass through (LPT).
Attribute
429
Parameters
None.
The alarmed port cannot carry any services and a switchover may occur on external equipment
connected to the port.
Possible Causes
l Cause 1: The radio link connected to the alarmed port is faulty.
l Cause 2: The opposite service access port is faulty.
Procedure
Step 1 Cause 1: The radio link connected to the alarmed port is faulty.
1. Check for MW_LIM, MW_LOF, and MW_RDI alarms on the local and opposite
microwave ports, and clear them if any. Then, check whether the
ETH_AUTO_LINK_DOWN alarm is cleared.
Step 2 Cause 2: The opposite service access port is faulty.
1. Check for ETH_LOS alarm, and optical-module-related alarms on the opposite port, and
clear them if any.
----End
Related Information
None.
A.3.79 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
430
Name Meaning
Parameters 1 to 4 (port) 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.
l When this alarm occurs, the loopback (LB) and link trace (LT) detection functions are
disabled.
l In addition, the service between the relevant standard MEPs may be interrupted.
Possible Causes
Cause 1: The upstream NE detects a fault at the Ethernet server layer.
Procedure
Step 1 Check whether there is any defect in the Ethernet server layer between source and sink NE.
----End
Related Information
None.
431
A.3.80 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
Name Meaning
Parameter 1, Parameter 2, Parameter 3,
Parameter 4 (Port)
Indicates the ID of the alarmed port.
Parameter 5, Parameter 6 (VLAN ID) Indicates the VLAN ID of the MEP.
Parameter 7 (Direction) Indicates the direction of the local MEP.
l 0x00: The port is direction insensitive.
Parameter 8 (Level) Indicates the MD level of the local MEP.
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.
432
l When the ETH_CFM_LOC alarm occurs, the LB and LT detection functions of Ethernet
service OAM are unavailable.
l The service between the relevant standard MEPs may be interrupted.
Possible Causes
l Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
l Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
l Cause 3: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.
1. Check whether the physical links (such as network cables and fibers) between the standard
MEPs are connected properly.
If... Then...
The physical links are connected improperly Connect the physical links properly.
The physical links are connected properly Go to Cause 2.
Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
1. Check whether Ethernet service in the maintenance association (MA) to which the local
MEP belongs is configured correctly.
If... Then...
The service is configured incorrectly Modify the configuration of the service to 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.
433
Table A-7 Alarm Parameters
Name Meaning
Parameter 1 to Parameter 4 MD
Parameter 5 to Parameter 8 MA
Parameter 9, Parameter 10 MEP ID
Parameter 11 to Parameter 14 Indicates the ID of the alarmed port.
When these parameters indicate the
VCTRUNK ID, parameter values = (0x01 -
0x10) + 0x80.
Parameter 15, Parameter 16 Indicates the VLAN ID of the MEP.
Parameter 17 Indicates the direction of the local MEP.
Parameter 18 Indicates the MD level of the local MEP.
NOTE
Consumer indicates the user, provider indicates
the supplier, and operator indicates the carrier.
Parameter 19, Parameter 20 Indicates the ID of the remote MEP.
NOTE
If the alarmed port is a VCTRUNK, these
parameters are not supported.

A.3.81 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.
434
Attribute
Parameters
Name Meaning
Parameter 4 (Port)
NOTE
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 Cause 1: The names of the maintenance domain and the maintenance alliance that the
standard MEPs correspond to are inconsistent.
l Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are
different.
435
l Cause 3: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the 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.
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
Name Meaning
0x10) + 0x80.
436
Name Meaning
NOTE

A.3.82 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
Name Meaning
Parameter 4 (Port)
437
Name Meaning
NOTE
Parameter 9, Parameter 10 (RMEPID) Indicates the ID of the remote MEP.
l When the ETH_CFM_RDI alarm occurs, the loopback (LB) and link trace (LT) detection
functions of Ethernet service OAM are unavailable.
l The service between the relevant standard MEPs may be interrupted.
Possible 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. Determine the alarmed port according to the alarm parameter.
2. Check whether the remote MEP that is connected to the port reports the
ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.
----End
Related Information
438
Name Meaning
0x10) + 0x80.
NOTE
Parameter 19, Parameter 20 Indicates the ID of the remote MEP.
NOTE
If the alarmed port is a VCTRUNK, these
parameters are not supported.

A.3.83 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.
439
Attribute
Parameters
Name Meaning
Parameter 4 (Port)
NOTE
l When the ETH_CFM_UNEXPERI alarm occurs, the LB and LT detection functions of
Ethernet service OAM are unavailable.
l The service may become abnormal due to the loop.
Possible Causes
l Cause 1: No remote MEP is configured.
l Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.
440
l Cause 3: The service is looped back and the looped packet is received.
Procedure
Step 1 Cause 1: No remote MEP is configured.
1. Check whether the remote MEP is configured. If not, configure the remote MEP first.
Step 2 Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, 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. Check whether the IDs of the MEPs in the maintenance domain are in conflict.
If... Then...
The IDs are in conflict Change the conflicting IDs.
The IDs are not in conflict Go to Cause 3.
Step 3 Cause 3: The service is looped back and the looped packet is received.
1. Check whether any loop exists at each IP port of the service trail. If yes, release the loop
and clear the alarm.
----End
Related Information
The Table A-10 describes the meanings of the parameters in the ETH_CFM_LOC alarm
reported by the EoS/EoPDH plane.
Name Meaning
0x10) + 0x80.
441
Name Meaning
NOTE

A.3.84 ETH_EFM_DF
Description
The ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the point-
to-point OAM protocol negotiation fails at the Ethernet port.
Attribute
Parameters
442
Name Meaning
Parameter 1
Indicates the reason why the negotiation fails.
l 0x01: The local link is faulty.
l 0x02: The local end fails to receive any OAM packets in a specified period.
l 0x03: The OAM settings of the opposite end do not meet the requirements of
the local end.
l 0x04: The OAM settings of the local end do not meet the requirements of the
opposite end.
When the ETH_EFM_DF alarm occurs, the service at the alarmed port may be interrupted.
Possible Causes
l Cause 1: The physical port of the local end is faulty.
l Cause 2: The point to point OAM protocol is not enabled at the opposite end.
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the board where the Ethernet
port is located.
Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end.
1. Enable the point to point OAM protocol at the opposite end.
Step 3 Cause 3: The OAM configuration at both ends is inconsistent.
1. Reconfigure the point to point OAM protocol and ensure the consistency at both ends.
----End
Related Information
None.
A.3.85 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.
443
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the type of the link event.
l 0x01: errored symbol period.
l 0x02: errored frame.
l 0x03: errored frame period.
l 0x04: errored frame seconds summary.
When the ETH_EFM_EVENT alarm occurs, the service at the alarmed port may be interrupted.
Possible Causes
l Cause 1: The physical port at the local end is faulty.
l Cause 2: The equipment at the opposite end is faulty.
port).
port).
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.
Performance Events.
444
If... Then...
too low
opposite site.
If... Then...
The alarm persists Go to Cause 1 or 2.
If... Then...
The alarm persists Go to Cause 1 or 2.
----End
Related Information
None.
A.3.86 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
445
Name Meaning
Parameter 1
Indicates the state of the loopback.
l 0x01: The local end initiates a loopback.
l 0x02: The local end responds to a loop request from the opposite end.
When the ETH_EFM_LOOPBACK alarm occurs, the service at the alarmed port is looped back.
Possible Causes
l Cause 1: The local end initiates a loopback.
l Cause 2: The opposite end initiates a loopback.
Procedure
Step 1 Cause 1: The local end initiates a loopback.
1. According to the alarm parameter, it is determined that the local end initiates a loopback.
Determine the causes of the loopback initiated at the local end and release the loopback as
soon as possible.
Step 2 Cause 2: The opposite end initiates a loopback.
1. According to the alarm parameter, it is determined that the opposite end initiates a loopback.
Determine the causes of the loopback initiated at the opposite port and release the loopback
as soon as possible.
----End
Related Information
None.
A.3.87 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
446
Parameters
Name Meaning
Parameter 1
Indicates the fault type at the opposite end.
l 0x01: link fault.
l 0x02: dying gasp.
l 0x03: critical event.
When the ETH_EFM_REMFAULT alarm occurs, the service at the alarmed port may be
interrupted.
Possible Causes
l Cause 1: The opposite NE is reset.
Procedure
Step 1 Cause 1: The opposite NE is reset.
1. Check whether the opposite NE is reset frequently.
If... Then...
The opposite NE is reset frequently Rectify the fault on the opposite NE.
The opposite NE is not reset frequently Reset the opposite NE, and the alarm is
cleared.
----End
Related Information
None.
A.3.88 ETH_LOS
Description
The ETH_LOS is an alarm indicating the loss of Ethernet port connection.
447
Attribute
Parameters
None.
When the ETH_LOS alarm occurs, the service at the alarmed port is interrupted.
Possible Causes
l Cause 1: The negotiation fails because the transmit port and receive port work in different
modes.
l Cause 2: The cable or fiber is faulty.
l Cause 3: The local receive end is faulty.
l Cause 4: The remote transmit end 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
in different modes
Correctly set the working modes of the
transmit port and receive port.
The transmit port and receive port work
in the same mode
Go to Cause 2.
Step 2 Cause 2: The cable or fiber is faulty.
1. Check the network cable or fiber jumper connected to the alarmed port.
If... Then...
The network cable is loose or damaged Connect the network cable properly or
replace the damaged network cable.
The connector of the fiber jumper is dirty Clean the connector.
The connector or fiber is damaged Insert the connector properly or replace the
damaged fiber jumper.
The connection is normal Go to Cause 3.
Step 3 Cause 3: The local receive end is faulty.
1. Check whether any fault occurs on the alarmed port.
448
If... Then...
The equipment is faulty Replace the alarmed board on the local.
The equipment is normal Go to Cause 4.
Step 4 Cause 4: The remote transmit end is faulty.
1. Check whether any fault occurs on the equipment interconnected with the alarmed port.
2. Rectify the fault.
----End
Related Information
None.
A.3.89 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.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the MAC port number.
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.
449
When this alarm occurs, it indicates that the alarmed port has no flow.
Possible Causes
l Cause 1: The port is enabled and in link up state, but is configured with no service.
l Cause 2: The port is enabled and in link up state, but does not transmit any packet due to
the service fault at the local end.
l Cause 3: The port is enabled and in link up state, but does not receive any packet due to
the service fault at the remote end.
Procedure
Step 1 Determine the MAC port number, alarmed board, and cause according to the parameters.
Step 2 Cause 1: No services are configured.
1. Configure the Ethernet service.
Step 3 Cause 2: No services are available.
If... Then...
No services are available in the transmit
direction
Check whether the service is normal at the
local end.
No services are available in the receive
direction
Check whether the service is normal at the
remote end.
----End
Related Information
None.
A.3.90 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.
450
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.3.91 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
Name Meaning
Parameter 1
The values are always 0x00 0x01.
451
Name Meaning
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 Cause 1: The physical port of the local end is faulty.
l Cause 2: The P2P OAM protocol is not enabled at the opposite end.
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the alarmed board.
Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.
1. Enable the P2P OAM protocol at the opposite end. For details, see Enabling the 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.92 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
452
function enabled receives the OAM packets that contain critical fault information from the
opposite end.
Attribute
Parameters
Name Meaning
Parameter 1
Parameter 4 Indicates the type of the fault.
l 0x01: A link fault occurs at the port of the opposite end.
l 0x02: Irrecoverable problems such as the power failure occur at
the opposite end.
l 0x03-0xff: other faults.
When this alarm occurs, the services on the link may be interrupted.
Possible Causes
l Cause 1: A link fault occurs at the remote MEP.
l Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
l Cause 3: Other faults occur at the remote MEP.
Procedure
Step 1 Determine the fault type according to Parameter 4.
If... Then...
The value of Parameter 4 is 0x01 Go to Cause 1.
453
If... Then...
Parameter 4 is a value from 0x03 to 0xff. Go to Cause 3.
Step 2 Cause 1: A link fault occurs at the remote MEP.
1. Handle the ETH_LOS alarm at the remote port.
Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.
1. Handle the problems such as power failure at the remote MEP, and recover the power supply
to the remote MEP.
Step 4 Cause 3: Other faults occur at the remote MEP.
1. Contact Huawei technical support engineers.
----End
Related Information
None.
A.3.93 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
initiates a remote loopback or responds to the remote loopback initiated by the opposite
equipment.
Attribute
Parameters
Name Meaning
Parameter 1
454
Name Meaning
Parameter 4
l 0x01: The loopback is initiated.
l 0x02: The loopback is responded.
The services are looped back between the local equipment and the opposite equipment. The
services and other protocol packets are interrupted.
Possible Causes
l Cause 1: The local end issues a loopback command and the opposite end responds to the
command.
l Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
Procedure
Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarm
parameters.
If... Then...
Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to the
command.
1. Determine the causes of the loopback at the local end and release the loopback.
Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to the
command.
1. Determine the causes of the loopback at the opposite end and release the loopback.
----End
Related Information
None.
A.3.94 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.
455
Attribute
Parameters
Name Meaning
Parameter 1
Parameter 4 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 Cause 1: The link event notification function is enabled at the opposite end.
l Cause 2: The link performance thresholds of the opposite end are inappropriate.
l Cause 3: The link performance deteriorates.
Procedure
Step 1 Cause 1: The link event notification function is enabled at the opposite end.
1. Check whether the link event notification function is enabled at the opposite end.
If... Then...
If yes Disable the link event notification function at the opposite end.
If not Go to Cause 2.
Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate.
1. Check whether the link performance thresholds of the opposite end are appropriate.
456
If... Then...
If not Set the thresholds to appropriate values.
If yes Go to Cause 3.
Step 3 Cause 3: The link performance deteriorates.
1. Improve the link performance at the opposite end so that the opposite end does not 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.95 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
Major Environmental alarms
Parameters
Name Meaning
Parameter 1 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.
457
Possible Causes
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.
l Cause 2: Two ports of the board are connected through cables or two ports of the board are
connected to the same LAN.
Procedure
Step 1 Determine the loopback type according to Parameter 1, and then handle the loopback
accordingly.
If... Then...
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... Then...
The PHY/MAC loopback is manually
configured at the port
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.
The cable connected to the port is self-
looped
Connect the cable properly to release the
selfloop.
The port is connected to a LAN that has a
loopback
Release the loopback on the LAN, or break the
connection between the port and the LAN, to
release the selfloop.
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.
If... Then...
The two ports are connected through
cables
Disconnect the cables to release the
selfloop.
The two ports are connected to the same
network
Break the connection between a port and the
LAN to release the selfloop.
----End
Related Information
None.
458
A.3.96 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
Major Environment alarm
Parameters
Name Meaning
Parameter 1 Indicates the loopback type.
l 0x01: The port is self-looped.
l 0x02: The board is self-looped.
l 0x03-0xff: unknown types.
If the function of automatic shutdown in the case of a selfloop is enabled at the alarmed port,
the services at the alarmed port are interrupted. Otherwise, a network storm may occur.
Possible Causes
l Cause 1: A loopback occurs on the lines connected to one VCTRUNK.
l Cause 2: The lines connected to two VCTRUNKs on the same board are interconnected.
Procedure
Step 1 Check the alarm on the NMS and determine the type of loopback according to the alarm
parameters.
If... Then...
459
If... Then...
Step 2 Cause 1: The port is self-looped.
1. Release the loopback at the port.
2. Reconfigure the lines connected to the VCTRUNK port and ensure that the port is not self-
looped.
Step 3 Cause 2: The board is self-looped.
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.97 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
Name Meaning
Parameter 1 to Parameter 4 Indicates the ID of the remote MEP.
Parameter 5 to Parameter 8 Indicates the ID of the local MEP.
Parameter 9, Parameter 10 Indicates the ID of the alarmed port.
l PORT number, Parameter 9 is 0x00.
l VCTRUNK number, Parameter 9 is 0x80.
460
Name Meaning
Parameter 14 to Parameter 17 Indicates the ID of the remote MEP.
Parameter 18 - Parameter 21
Indicates the ID of the local MEP.
A unidirectional connectivity failure occurs in the Ethernet service between two MEPs.
Possible Causes
l Cause 1: The line between two MEPs is interrupted.
l Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
l Cause 3: The services between two MEPs are congested or interrupted.
Procedure
Step 1 Cause 1: The line between two MEPs is interrupted.
1. Check whether the physical links (such as network cables or optical fibers) that carry
services between the two MEPs are correctly connected.
If... Then...
If not Re-connect the cables to rectify the faults on physical links.
Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.
1. Check whether the Ethernet services in the MA to which the alarmed MEP belongs are
configured correctly.
If... Then...
If not Modify the configuration to ensure consistency at both ends.
Step 3 Cause 3: The services between two MEPs are congested or interrupted.
----End
Related Information
None.
461
A.3.98 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
Major Environment alarm
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicates the ID of the local MEP.
l PORT number, Parameter 9 is 0x00.
l VCTRUNK number, Parameter 9 is 0x80.
Parameter 10 to Parameter 13
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.
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.
462
1. Check the alarm on the NMS and determine the associated MP ID according to the alarm
parameters.
2. Query the information about the MEP. Delete the incorrect MEPs and create MEPs with
unique MP IDs.
----End
Related Information
None.
A.3.99 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of the external clock source.
Attribute
Parameters
Name Meaning
Parameter 1
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.
l 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.
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.
463
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... Then...
The equipment is faulty Rectify the fault.
The equipment is normal Go to the next step.
2. Check whether the cable that connects the external clock source is normal.
If... Then...
The cable is abnormal Replace the cable.
The cable is normal Replace the alarmed board.
----End
Related Information
None.
A.3.100 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm of the loss of the external time source.
Attribute
Parameters
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
464
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 Cause 1: The link at a port is faulty.
l Cause 2: The external time device is faulty.
Procedure
Step 1 Cause 1: The link at a port is faulty.
1. Check cable connections. If cables are incorrectly connected, connect the cables again.
Step 2 Cause 2: The external time device is faulty.
1. Check whether the external time device is faulty.
----End
Related Information
None.
A.3.101 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
Name Meaning
Parameter 1 Indicates the number of the alarmed fan.
465
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.102 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the fan.
When the FAN_FAIL alarm occurs, the heat dissipation of the system is affected.
After an alarm is reported, clear it immediately. Otherwise, services may be interrupted or
equipment may be damaged.
When a fan is faulty, perform the following operations:
466
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.
l 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 Cause 1: The board and the backplane are connected improperly.
l Cause 2: Fan failure occurs.
Procedure
Step 1 Cause 1: The board and the backplane are connected improperly.
1. Remove the fan board. Clean the dust on the fan and reinsert the fan board.
If... Then...
handling.
Go to Cause 2.
Step 2 Cause 2: Fan failure occurs.
1. Replace the alarmed fan board.
----End
Related Information
None.
A.3.103 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
Parameters
467
Name Meaning
Parameter 1
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 Cause 1: The encapsulation protocols or encapsulation parameters are inconsistent at both
ends of services.
l Cause 2: Service channels have errors.
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... Then...
The protocols are inconsistent Correct the configuration data.
The protocols are consistent Go to the next step.
2. Check whether the encapsulation parameters are consistent at both ends of services.
If... Then...
The parameters are inconsistent Correct the configuration data.
The parameters are consistent Go to the next step.
Step 2 Cause 2: Service channels have errors.
1. Check whether any error alarm or performance event occurs on the board that carries the
services.
If... Then...
Yes Handle the alarm or performance event.
No Go to the next step.
468
----End
Related Information
None.
A.3.104 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that items listed in an E-LAN forwarding table are
all used. This alarm is reported when the number of actual items in the MAC address table for
the E-LAN service is greater than Address Detection Upper Threshold. This alarm is cleared
automatically when the number of items in the MAC address table of the E-LAN service is lower
than Address Detection Upper Threshold.
Attribute
Minor Service alarm
Parameters
None.
When this alarm occurs, the E-LAN service stops learning new MAC addresses. As a result,
unknown unicast packets in the traffic flow may increase, and broadcast packets may increase
accordingly. In this case, the line rate may be affected.
Possible Causes
The possible causes of the FDBSIZEALM_E-LAN alarm are as follows:
l Cause 1: The value of Address Detection Upper Threshold is too small.
l Cause 2: The E-LAN service is attacked.
Procedure
l Cause 1: The value of Address Detection Upper Threshold is too low.
1. Check whether the value of Address Detection Upper Threshold is too small. For
details, see Configuring the MAC Address Learning Parameters.
2. If yes, set the parameter to a larger value based on actual situations. Check whether
the alarm is cleared. If the alarm persists, go to Cause 2.
469
l Cause 2: The E-LAN service is attacked.
1. Modify the settings so that the E-LAN service discards unknown packets. For details,
see Setting the Mode for Processing an Unknown Frame of the E-LAN Service.
----End
Related Information
None.
A.3.105 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating the received or transmitted traffic over the threshold
for some performance object
Attribute
Minor Service alarm
Parameters
Name Meaning
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 Cause 1: The traffic threshold is very low.
l Cause 2: The opposite end transmits excessive data flow.
l Cause 3: The network exists data storm.
470
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.
Step 3 Cause 3: the network exists data storm.
1. Check whether the network exists data storm. Release the loops if exist.
----End
Related Information
None.
A.3.106 GSP_RSVP_NB_AUTH_ERR
Description
The GSP_RSVP_NB_AUTH_ERR alarm indicates a Resource Reservation Protocol (RSVP)
neighbor authentication error.
Attribute
Parameters
Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.
No TE tunnel can be established between the local NE and the RSVP neighbor.
Possible Causes
The RSVP authentication parameters are set inconsistently on the local NE and the RSVP
neighbor.
471
Procedure
Step 1 Check the RSVP authentication parameters of the local NE and the RSVP neighbor. If the
parameters are set inconsistently, modify them to make them consistent.
----End
Related Information
None
A.3.107 GSP_RSVP_NB_DOWN
Description
The GSP_RSVP_NB_DOWN alarm indicates an interruption between the local NE and the
RSVP neighbor. This alarm is reported if the local NE does not receive any RSVP response
messages from the RSVP neighbor within three consecutive intervals.
Attribute
Parameters
Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.
The CR-LSP between the local NE and the RSVP neighbor is torn down.
Possible Causes
l Cause 1: RSVP is disabled on the RSVP neighbor.
l Cause 2: There is no reachable route to the RSVP neighbor.
l Cause 3: The link between the local NE and the RSVP neighbor is faulty.
l Cause 4: The RSVP neighbor is faulty.
472
Procedure
Step 1 Cause 1: RSVP is disabled on the RSVP neighbor.
1. Enable RSVP on the RSVP neighbor.
NOTE
RSVP is enabled on OptiX RTN 950 by default.
Step 2 Cause 2: There is no reachable route to the RSVP neighbor.
1. Check the IGP routing table and ensure that the table contains a route to the RSVP neighbor.
2. Ensure that the IGP configurations between the local NE and the RSVP neighbor are
correct.
3. Ensure that the interface parameters are set consistently on the local NE and the RSVP
neighbor, and that the interface status of both ends is Up.
Step 3 Cause 3: The link between the local NE and the RSVP neighbor is faulty.
1. Check whether the link between the local NE and the RSVP neighbor is faulty, for example,
whether an ETH_LOS or MW_LOF alarm is reported.
2. If the link is faulty, rectify the fault by following instructions in Troubleshooting
Microwave Links or Troubleshooting Native Ethernet Services.
Step 4 Cause 4: The RSVP neighbor device is faulty.
1. Check whether the RSVP neighbor device is faulty. If the device is faulty, rectify the fault.
----End
Related Information
None
A.3.108 GSP_TNNL_DOWN
Description
The GSP_TNNL_DOWN alarm indicates that an RSVP-TE tunnel is faulty.
Attribute
Parameters
473
Name Meaning
Parameter 1
Indicates the cause of the RSVP-TE tunnel fault. The values are as follows:
l 0x01: indicates a route calculation failure.
l 0x02: indicates a signaling response time-out.
l 0x03: indicates a bandwidth resource request error.
l 0x04: indicates that the resources (including interface and label
information) requested by RSVP are invalid.
l 0x05: indicates a label allocation failure.
l 0x06: indicates a cross-connection control failure.
l 0x07: indicates a tunnel cross-connection setup failure.
l 0x08: indicates an unavailable data link.
l 0x09: indicates a signaling negotiation failure.
l 0x0a: indicates an unknown cause.
l 0x0b: indicates a link fault.
l 0x0c: indicates an RSVP tunnel creation failure.
l 0x0d: indicates a restoration failure during an RSVP restart.
l 0x0e: indicates an RSVP summary refresh time-out.
l 0x0f: indicates an RSVP GR time-out.
l 0x10: indicates that a lower-priority RSVP tunnel goes Down because its
bandwidth resources are preempted by a higher-priority tunnel.
Parameters 2-5 Indicate the IP address of the faulty NE on the RSVP-TE tunnel.
The RSVP-TE tunnel cannot carry any services.
Possible Causes
l Cause 1:
The system control board on the peer NE has a hardware fault or software fault.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 2:
The link to the peer NE is faulty.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x08, 0x09, 0x0b, 0x0c, 0x0d, 0x0e, or
0x0f.
l Cause 3:
There is no reachable route to the destination NE, or no route complies with the explicit
LSP.
This may be the cause for 0x01, 0x02, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 4:
The RSVP-TE tunnel configurations are incorrect.
474
This may be the cause for 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x09, 0x0a, 0x0c, 0x0f, or
0x10.
l Cause 5:
The bandwidth of the NE is insufficient.
This may be the cause for 0x03, 0x04, or 0x10.
Procedure
Step 1 Cause 1: The system control board on the peer NE has a hardware or software fault.
1. Check whether the system control board on the peer NE has a hardware or software fault.
If the board has a fault, rectify it.
Step 2 Cause 2: The link to the peer NE is faulty.
1. Check whether the link to the peer NE is faulty. If the link is faulty and it is a microwave
link, rectify the fault by following instructions in Troubleshooting Microwave Links. If
the link is faulty and it is an Ethernet link, rectify the fault by following instructions in
Troubleshooting Native Ethernet Services.
Step 3 Cause 3: There is no reachable route to the destination NE, or no route complies with the explicit
LSP.
1. Ping the IP address of the destination NE and each NE along the explicit LSP. Ensure that
there is a reachable route to the destination NE or each NE along the explicit LSP.
2. Ensure that the IS-IS configurations on all the NEs between the local NE and destination
NE are correct.
Step 4 Cause 4: The RSVP-TE tunnel configurations are incorrect.
1. Ensure that the RSVP-TE tunnel configurations are correct. If IS-IS TE is enabled on an
interface, ensure that the RSVP authentication and RSVP-TE explicit path configurations
are correct.
Step 5 Cause 5: The bandwidth of the NE is insufficient.
1. Ensure that the bandwidth resources reserved for tunnels are configured correctly.
2. If a higher-priority tunnel preempts the bandwidth resources of a lower-priority tunnel,
check whether the tunnel priorities are configured properly. If the tunnel priorities are not
configured properly, configure them again.
3. If the reserved bandwidth resources are correctly configured and tunnel priorities are
configured properly but the link bandwidth cannot meet requirements, increase the network
bandwidth.
----End
Related Information
None
A.3.109 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware errors.
475
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 3 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 Cause 1: The board and the backplane are connected improperly.
l Cause 3: The slot is faulty.
Procedure
Step 1 Cause 1: The board and the backplane are connected improperly.
1. Remove and insert the alarmed board. For details, see 6.1 Removing a Board and 6.2
Inserting a Board. Then, check whether the alarm is cleared.
If... Then...
handling.
Check for the faults in boards.
1. Replace the alarmed board, and then check whether the alarm is cleared. For details, see 6
Part Replacement.
If... Then...
replaced
handling.
476
If... Then...
replaced
Check for the faults in slots.
Step 3 Cause 3: The slot is faulty.
1. Contact Huawei engineers to handle the faulty slot.
NOTE
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.110 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.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates functions that are not supported by a board.
l 0x01: ETH PWE3 control word
l 0x02: 2.5 Gbit/s bus rate
477
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.111 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.
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1
Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
478
Name Meaning
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 4.3.5 Browsing the Performance
Event Threshold-Crossing Records.
2. Handle the threshold-crossing performance event.
----End
Related Information
None.
A.3.112 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.
479
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 Cause 1: The service level is inconsistently configured at both ends.
l Cause 2: The transmit unit of the peer NE is faulty.
Procedure
Step 1 Cause 1: The service level is inconsistently configured at both ends.
1. Verify that cross-connection configurations (signal mapping) are consistent at both ends.
For example, if the VC-12 structure is configured at the local end and the VC-3 structure
is configured at the peer end, rectify the configurations.
Step 2 Cause 2: The transmit unit of the peer NE is faulty.
1. Replace the alarmed board on the local NE. Then, check whether the alarm is cleared.
If... Then...
The alarm persists Replace the system control, cross-connect, and timing board
on the peer NE.
----End
Related Information
None.
A.3.113 HP_RDI
480
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
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.114 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.
Attribute
Warning Service alarm
481
Parameters
None.
The service on the local site is not affected. The service received by the opposite station, however,
has errors.
Possible Causes
higher order path remote errors.
Procedure
1. Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.
----End
Related Information
None.
A.3.115 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.
None.
482
Possible Causes
l Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte configured
to be received at the local end.
l Cause 2: Configuration data is incorrect.
Procedure
Step 1 Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte configured to
be received at the local end.
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 Cross-
Connections of SNCP Services.
----End
Related Information
None.
A.3.116 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.
Possible Causes
l Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted
on the opposite NE.
483
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.
1. If the alarmed port is the SDH port that is interconnected with the ATM/Ethernet equipment,
configure the service as VC-4 pass-through service. For details, see Creating Cross-
Connections of SNCP Services or Creating the Cross-Connections of Point-to-Point
Services.
If... Then...
The alarm is cleared after the configuration
is changed
handling.
The alarm persists after the configuration
is changed
2. 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.117 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
Parameters
None.
484
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 Cause 1: The line port at the local NE is configured with services, but the corresponding
line port at the opposite NE is not configured with services.
l Cause 2: Byte C2 is set to 0 at the opposite NE.
Procedure
Step 1 Cause 1: The line port at the local NE is configured with services, but the corresponding 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.
Step 2 Cause 2: Byte C2 is set to 0 at the opposite NE.
1. Change the setting of byte C2. For details, see Configuring VC-4 POHs.
----End
Related Information
None.
A.3.118 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
Minor Service alarm
Parameters
485
Name Meaning
Parameter 1
l 0x01: 15 minutes
l 0x02: 24 hours
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 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
----End
Related Information
None.
A.3.119 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is open.
Attribute
Parameters
None.
486
When the IF_CABLE_OPEN alarm occurs, the service on the alarmed IF port is interrupted.
Possible Causes
l Cause 1: The IF cable is loose or faulty.
l Cause 2: The IF port on the IF board is damaged.
l Cause 3: The power module of the ODU is faulty.
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... Then...
The connector is loose 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 Go to the next step.
2. Check whether the surface of the IF fiber jumper and the IF cable is damaged.
If... Then...
The cable does not meet the requirement Replace the cable with a qualified one.
The cable meets the requirement Go to Cause 2 or Cause 3.

Step 2 Cause 2: The IF port on the IF board is damaged.
1. Replace the alarmed IF board.
Step 3 Cause 3: The power module of the ODU is faulty.
1. Replace the ODU connected to the alarmed IF port.
----End
Related Information
None.
487
A.3.120 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an ODU
is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1
l 0x01: Indicates that the input power of the ODU is too high.
l 0x02: Indicates that the input power of the ODU is too low.
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 Cause 1: The IF board is faulty.
l Cause 2: The IF cable is faulty.
l Cause 3: The ODU is faulty.
l Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
Procedure
Step 1 Cause 1: The IF board is faulty.
1. Replace the IF board connected to the alarmed ODU.
Step 2 Cause 2: The IF cable is faulty.
1. Check whether the connectors of the IF cable are loose or prepared incorrectly.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
488
If... Then...
Any of the connectors is loose Connect the connector tightly.
Any of the connectors is prepared
incorrectly
See the Installation Reference and make
new connectors for the IF cable.
All connectors are normal Go to the next step.

2. Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed,
and test the connectivity between the IF fiber jumper and the IF cable. For details, see
Testing the Connectivity of the IF Cable.
If... Then...
The IF cable is below standard Replace the IF cable.
The IF cable is up to standard The IF board or ODU may be faulty.

Step 3 Cause 3: The ODU is faulty.
1. Replace the alarmed ODU.
Step 4 Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
1. Connect the IF fiber jumper and the IF board correctly.
----End
Related Information
The logical slot ID of the ODU is obtained by adding 20 to the slot ID of the IF board connected
to the ODU.
A.3.121 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
489
Name Meaning
Parameter 1
Indicates the ID of the FPGA file that is loaded to the board.
l 0x01 indicates that FPGA file 250 is loaded.
l 0x02 indicates that FPGA file 002 is loaded.
When the IF_MODE_UNSUPPORTED alarm occurs, the service on the alarmed IF port 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. Contact Huawei engineers to upgrade the software and the FPGA file.
----End
Related Information
None.
A.3.122 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.
490
When this alarm occurs, all links of the alarmed IMA group are unavailable.
Possible Causes
l Cause 1: The IMA links on the local NE are faulty.
l Cause 2: The activated links of the IMA group on the local NE are less than the minimum
number.
Procedure
Step 1 Cause 1: The IMA links on the local NE are faulty.
1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.
2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,
configure the related services at other ports or replace the related board.
Step 2 Cause 2: The activated links of the IMA group on the local NE are less than the minimum number.
If... Then...
The ALM_IMA_LIF alarm occurs Clear the ALM_IMA_LIF alarm immediately.
Activate the links of the IMA group on the local NE.
No other alarm occurs Reconfigure the links of the IMA group on the 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.123 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
491
Parameters
None.
When this alarm occurs, the ports of the IMA group are congested and services have bit errors.
Possible Causes
l Cause 1: The IMA links on the remote NE are faulty.
l Cause 2: The activated links of the IMA group on the remote NE are less than the minimum
number.
Procedure
Step 1 Cause 1: The IMA links on the remote NE are faulty.
1. Check whether the T_ALOS alarm is reported at the E1 port. If yes, clear this alarm.
2. Check whether the IMA_GROUP_RE_DOWN alarm is cleared. If the alarm persists,
configure the related services at other ports or replace the related board.
Step 2 Cause 2: The activated links of the IMA group on the remote NE are less than the 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.124 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.
492
Attribute
Parameters
None.
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. Check the alarm information and determine the NE, board, and ATM trunk related to the
alarm.
2. Modify the Clock Mode parameter of the alarmed ATM trunk to the same value as that of
the opposite end. Then, check whether the alarm is cleared.
----End
Related Information
The Clock Mode parameter can be set to two modes.
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.
l 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.125 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.
Attribute
493
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 Cause 1: The transmit power of the opposite NE is over high or over low.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over high or over low.
1. Browse current performance events, and query the performance event of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not meet
the requirement
Replace the optical module.
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... Then...
The models are incorrect Replace the optical module.
The models are correct Go to Cause 3.
Step 3 Cause 3: The optical module at the receive end is faulty.
1. Use the optical power meter to test the receive optical power, and check whether the receive
optical power meets the requirement. If yes, contact Huawei engineers to replace the optical
module.
Step 4 Cause 4: The fiber performance degrades.
If... Then...
The connector of the fiber jumper is dirty Clean fiber connectors.
494
If... Then...
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 Meaning
Parameter 1 Indicates the port number.
Parameter 2, Parameter 3 The value of Parameter 2 is always 0x00, and
the value of Parameter 3 is always 0x01. The
two parameters indicate the path ID.
Parameter 4, Parameter 5 Reserved. The values are always 0xFF.

A.3.126 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 Cause 1: The transmit power of the opposite NE is over high.
495
Procedure
Step 1 Cause 1: The transmit power of the opposite site is over high.
If... Then...
the requirement
Contact Huawei engineers to replace the
optical module.
The transmit optical power meets the
requirement
Add a proper attenuator to reduce the
receive optical power.
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
optical power meets the requirement. If yes, contact Huawei engineers to replace the 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.127 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input optical power is over low.
Attribute
Parameters
None.
496
When the IN_PWR_LOW alarm occurs, the service at the alarmed optical interface has errors.
Possible Causes
l Cause 1: The transmit power of the opposite NE is over low.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over low.
If... Then...
the requirement
optical module.
The transmit optical power meets the
requirement
Go to Cause 2.
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
optical power meets the requirement.
If... Then...
The receive optical power meets the
requirement
optical module.
The receive optical power does not meet the
requirement
Go to Cause 4.
Step 4 Cause 4: The fiber performance degrades.
1. Clean fiber connectors and adapters.
497
If... Then...
The alarm is cleared after the connector is
cleaned
The fault is rectified. End the alarm handling.
The alarm persists after the connector is
cleaned
Replace the fiber.
----End
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity point.
SDH Interface Performance.
A.3.128 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 Cause 1: The air inlet temperature sensor is faulty.
l Cause 4: The air inlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air inlet temperature sensor is faulty.
1. Replace the air inlet temperature sensor.
498
If... Then...
If... Then...
Step 4 Cause 4: The air inlet temperature sensor is not installed.
1. Install the air inlet temperature sensor.
----End
Related Information
None.
A.3.129 IPFPM_INST_TLP_ERR
Description
The IPFPM_INST_TLP_ERR alarm indicates that binding an IP FPM instance to the Target
Logical Port (TLP) fails.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the instance ID.
499
The performance data collected for the IP FPM instance is inaccurate.
Possible Causes
Cause: ACL resources of the NE are insufficient.
Procedure
Step 1 Delete useless IP FPM instances or undesired complex traffic classification configurations to
release ACL resources.
Step 2 Re-bind the IP FPM instance to the TLP.
----End
A.3.130 ISISADJACENCYCHANGE
Description
The ISISADJACENCYCHANGE alarm indicates that the status of an IS-IS neighbor changes.
Attribute
Parameters
Name Meaning
Parameters 1-4
Indicate the IS-IS process ID.
Parameters 5-8
Indicate the type of the IS-IS neighbor.
Parameters 9-12
Indicate the IS-IS interface index.
Parameters 13-16
Indicate the interface index.
Parameters 17-39
Indicate the system ID.
Parameters 40-43
Indicate the status of the IS-IS neighbor.
500
Name Meaning
Parameters 44-47
Indicate the interface index.
Parameters 48-111
Indicate the interface name.
Parameters 112-115
Indicate the cause of the neighbor status change.
IS-IS may recalculate the route, resulting in route flapping.
The RSVP neighbor relationship and BGP peer relationship with IS-IS as the IGP route protocol
may be interrupted.
Possible Causes
l Cause 1: The IS-IS configurations are incorrect.
l Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
l Cause 3: The IS-IS neighbor fails.
Procedure
Step 1 Cause 1: The IS-IS configurations are incorrect.
1. Ensure that the IS-IS configurations are consistent on the local NE and the IS-IS neighbor.
Step 2 Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
1. Check whether the link between the local NE and the IS-IS neighbor is faulty, for example,
whether an ETH_LOS alarm is reported.
2. If the link is faulty, rectify the fault.
Step 3 Cause 3: The IS-IS neighbor is faulty.
1. Check whether the IS-IS neighbor is faulty. If the IS-IS neighbor is faulty, rectify the fault.
----End
Related Information
None
A.3.131 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.
501
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.3.132 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
502
Name Meaning
Parameter 1 Indicates the protection group type.
l 0x02: ring MS protection.
When the K1_K2_M alarm occurs, the MSP protocol may fail and therefore the protection
switching may fail.
Possible Causes
l Cause 1: The switching modes configured at both ends are single-ended switching and dual-
ended switching separately.
l Cause 2: The fiber connection is incorrect.
Procedure
Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dual-
ended switching separately.
1. Check whether the switching modes at both ends are the same.
If... Then...
The switching modes are different Configure the switching modes as the same.
The switching modes are the same Go to Cause 2.
Step 2 Cause 2: The fiber connection is incorrect.
1. Check whether the fiber connection is correct. For example, the fiber at the receive or
transmit port may be incorrectly connected, or disconnected.
If... Then...
The fiber connection is incorrect Connect the fiber properly.
The connection is correct Go to Cause 3.
1. Replace the opposite line board. Then, check whether the alarm is cleared.
If... Then...
503
If... Then...
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer to Creating a Packet-based Linear MSP Group
A.3.133 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
Name Meaning
Parameter 1 Indicates the protection group type.
l 0x02: ring MS protection.
When the K2_M alarm occurs, the MSP protocol may fail and therefore the protection switching
may fail.
Possible Causes
l Cause 1: Two NEs of the linear MSP group are configured with different protection modes
(1+1 or 1:N).
504
l Cause 2: The MSP protocol is stopped when the protection switching occurs.
l Cause 3: The fiber connection is incorrect.
Procedure
Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes (1
+1 or 1:N).
1. Query the status of the linear MSP, and check whether two NEs of the linear MSP group
are configured with different protection modes (1+1 or 1:N).
If... Then...
The protection modes are different Configure the protection modes as the same.
The protection modes are the same Go to Cause 2.
Step 2 Cause 2: The MSP protocol is stopped when the protection switching occurs.
1. Query the status of the linear MSP, and check whether the MSP protocol is stopped on the
opposite NE.
If... Then...
The protocol is stopped Restart the MSP protocol on the opposite NE. For details, 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... Then...
The connection is incorrect Connect the fiber properly
1. Replace the opposite line board. Then, check whether the alarm is cleared.
If... Then...
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer toCreating a Packet-based Linear MSP Group.
505
A.3.134 L3V_TRAP_THRE_EXCEED
Description
The L3V_TRAP_THRE_EXCEED alarm indicates that the number of VPN route prefixes
exceeds the maximum number allowed.
Attribute
Parameters
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-35 Indicates the current number of route prefixes.
Parameters 36-39 Indicates the maximum number of route prefixes.
When the number of VPN route prefixes exceeds the maximum number allowed, excess VPN
route prefixes cannot be added into the VPN instance routing table. As a result, the excess VPN
routes are lost and some services are unavailable.
Possible Causes
l Cause 1: Data configuration is incorrect.
l Cause 2: The maximum number of route prefixes in a VPN instance routing table is set to
a small value.
l Cause 3: The network structure is not appropriate.
Procedure
Step 1 Cause 1: Data configuration is incorrect.
1. Check the data configuration, especially BGP route configuration, to ensure that the NE
receives only required routes.
Step 2 Cause 2: The maximum number of route prefixes in a VPN instance routing table is set to a small
value.
1. Increase the maximum number of route prefixes in a VPN instance routing table.
506
Step 3 Cause 3: The network structure is not appropriate.
1. Optimize the network structure.
----End
Related Information
None
A.3.135 L3V_TRAP_VRF_DOWN
Description
The L3V_TRAP_VRF_DOWN alarm indicates that a VPN instance is in the Down state. This
alarm is reported when all the interfaces bound to a VPN instance go Down or the binding
relationships between a VPN instance and interfaces in the Up state are deleted.
Attribute
Parameters
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-33 Indicate the slot ID.
Parameter 34 Indicates the sub-slot ID.
Parameters 35-36 Indicate the interface ID.
Parameters 37-40 Indicate the interface running status. The values are as follows:
l 0x01: active
l 0x02: notInService
Parameters 41-44 Indicate the VPN instance running status.
l 0x01: up
l 0x02: down
The VPN service is interrupted.
Possible Causes
l Cause 1: The VPN instance is not bound with any interfaces.
l Cause 2: All the interfaces bound to the VPN instance go Down.
507
Procedure
Step 1 Cause 1: The VPN instance is not bound with any interfaces.
1. Bind interfaces to the VPN instance according to the plan. Ensure that the status of these
interfaces is Up.
Step 2 Cause 2: All the interfaces bound to the VPN instance go Down.
1. Ensure that the interfaces are enabled and configured with IP addresses. For details, see
Setting Ethernet Interface Parameters. If the interfaces are still in the Down state, go to the
next step.
2. Check whether the links to the interfaces are faulty. If they are faulty, rectify the faults by
following instructions in Troubleshooting Native Ethernet Services.
----End
Related Information
None
A.3.136 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. Query the license capacities of the ports of the LAG group by using the NMS.
2. If the license capacities of the ports differ from each other, reload a license file of an
appropriate capacity.
----End
508
Related Information
None.
A.3.137 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. Determine the alarmed port according to the alarm parameter.
2. Rectify the fault at each member port according to the description of
LAG_MEMBER_DOWN.
----End
Related Information
None.
509
A.3.138 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.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the slot ID of the alarmed board.
Parameter 3 Indicates the ID of the alarmed subboard. The value is always 0xff.
Parameter 6 Indicates the cause that makes the port unavailable.
l 0x01: The port link is faulty or disabled.
l 0x02: The port fails to receive the LACP packets.
l 0x03: The port works in half-duplex mode.
l 0x04: The port is self-looped.
The port in the LAG cannot share the service load, and the port does not transmit or receive any
services.
Possible Causes
l Cause 1: The port link is faulty or disabled.
l Cause 2: The port receives no LACP packets.
l Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.
l Cause 4: The port is self-looped.
510
Procedure
Step 1 Determine the alarmed port and the cause of the alarm according to the alarm parameters.
If... Then...
The value of Parameter 4 is 0x01 Perform the operations described in Step 2.
Step 2 Cause 1: The port link is faulty or disabled.
1. On the NMS, check whether the port in the LAG is enabled. For details, see Querying the
Protocol Information of the LAG.
If... Then...
The port is not enabled Enable the port in the LAG.
The port is enabled Go to the next step.
2. Check the link status of all ports and check whether the ETH_LOS alarm is reported.
If... Then...
The alarm is reported Clear the ETH_LOS alarm immediately and rectify 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.
2. On the NMS, change the working mode of the port into full-duplex and Auto-Negotiation.
Step 5 Cause 4: The port is self-looped.
1. Check whether the port is self-looped. For details, see 8.2.1 Querying the Attributes of
an Ethernet Port. If the port is self-looped, release the selfloop. For details, see 8.4.5
Setting a Loopback for the Packet-plane Ethernet Interface Board.
----End
Related Information
None.
511
A.3.139 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
Parameters
Name Meaning
Parameter 1
Indicates the number of the IP port.
Parameter 4 Indicates the cause of the protection failure.
l 0x01: The link of the port is faulty or fails.
l 0x02: The port is in half-duplex mode.
l 0x04: The port detects the selfloop.
l 0x05: Other unknown reasons.
Parameter 5 The value is always 0xff.
services.
Possible Causes
l Cause 1: The port is disabled or the link is faulty.
l Cause 2: The port is in the half-duplex mode.
l Cause 3: The port fails to receive the LCAP packets.
l Cause 4: The port detects a selfloop.
512
l Cause 5: other unknown reasons
Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause according to the alarm parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.
1. On the NMS, check whether the port in the LAG is enabled. For details, see Setting 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 half-
duplex mode, change the working mode of the port into full-duplex. For details, see Setting
the Basic Attributes of Ethernet Ports.
Step 4 Cause 3: The port fails to receive the LCAP packets.
1. On the NMS, check whether the LAG group is properly configured on the opposite end.
For details, see Querying the Protocol Information of the LAG.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
2. 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.
Step 5 Cause 4: The port detects a selfloop.
1. Release the selfloop of the port with reference to Enabling Self-Loop Detection.
Step 6 Cause 5: other unknown reasons
1. Contact Huawei engineers.
----End
513
Related Information
None.
A.3.140 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
Parameters
Name Meaning
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 0x04: The link of the port is configured into a loop.
l 0x05: other unknown reasons.
services.
514
Possible Causes
l Cause 1: The link of the port is faulty or fails.
l Cause 2: The port fails to receive the LCAP packets.
l Cause 3: The port detects a selfloop.
l Cause 4: other unknown reasons
Procedure
Step 1 Determine the port where the alarm occurs and the alarm cause according to the alarm parameter.
If... Then...
Step 2 Cause 1: The port is disabled or the link is faulty.
1. Check the link state of each VCG port. If any link is faulty, rectify the fault.
Step 3 Cause 2: The port fails to receive the LCAP packets.
1. On the NMS, check whether the LAG group is properly configured on the opposite end.
If... Then...
The LAG group is not properly configured Reconfigure the LAG group.
The LAG group is properly configured Go to the next step.
2. Check whether the local port and the remote port transmit the LACP packets. If the 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.141 LAN_LOC
Description
The LAN_LOC is an alarm indicating the Ethernet communication failure.
515
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the network port ID. For example, 0x01 indicates network
port 1 and 0x02 indicates network port 2.
Parameter 2, Parameter 3 Indicates the number of the path on which the alarm is reported.
Parameter 2 indicates the most significant bits and the value 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 Cause 1: The cable is not connected to the network port, or the cable is faulty.
l Cause 2: The network port is faulty.
l Cause 3: The system control, switching, and timing board is faulty.
Procedure
Step 1 View the alarm on the NMS. Determine the network port ID according to the alarm 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, Switching
and Timing Board.
Step 4 Cause 3: The system control, switching, and timing board is faulty.
516
1. Replace the system control, switching, and timing board. For details, see 6.10 Replacing
the System Control, Switching and Timing Board.
----End
Related Information
None.
A.3.142 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.
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.143 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.
517
Attribute
Parameters
None.
When the LASER_MOD_ERR alarm occurs, the performance of the optical interface degrades
and serious degradation even causes service interruption.
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface type.
l Cause 3: The optical module is faulty.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
1. Check whether the optical module installed at the optical interface matches the rate of the
optical interface. For details, see 4.8.5 Querying the Board Manufacturing Information
Report.
If... Then...
The optical module does not match the
rate of the optical interface
optical module with one that matches the
rate of the optical interface.
The optical module 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... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.
518
----End
Related Information
None.
A.3.144 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.
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 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface type.
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 4.8.5 Querying the Board Manufacturing Information
Report.
519
If... Then...
The optical module does not match the
rate of the optical interface
optical module with one that matches the
rate of the optical interface.
The optical module 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 Replace it with an SFP module of the correct type.
1. Replace the faulty optical module.
If... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.
----End
Related Information
None.
A.3.145 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.
520
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.3.146 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
Name Meaning
The Ethernet service is not normal.
521
Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
1. Check whether the LCAS enabling state and the LCAS parameters are the same at both
ends of the link.
If... Then...
The settings of the LCAS protocols are
not consistent
Properly enable the LCAS protocols at both
ends.
The settings of the LCAS protocols at
both ends are consistent
Go to Cause 2.
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
incorrect
Correct the configuration data.
correct
Go to Cause 2.
Step 2 Cause 2: The link is faulty.
1. Check whether the link where the service travels has errors or becomes faulty.
If... Then...
The link is faulty Rectify the fault.
The link is normal Go to the next step.
2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.
If... Then...
----End
Related Information
None.
A.3.147 LCAS_FOPT
522
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
Name Meaning
The Ethernet service is not normal.
Possible Causes
l Cause 1: Configuration data of the LCAS protocol is incorrect.
l Cause 2: The link is faulty.
Procedure
Step 1 Cause 1: Configuration data of the LCAS protocol is incorrect.
1. Check whether the LCAS enabling state and the LCAS parameters are the same at both
ends of the link.
If... Then...
The settings of the LCAS protocols are
not consistent
Properly enable the LCAS protocols at both
ends.
The settings of the LCAS protocol at both
ends are consistent
Go to Cause 2.
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.
523
If... Then...
incorrect
Correct the configuration data.
correct
Go to Cause 2.
Step 2 Cause 2: The link is faulty.
1. Check whether the link where the service travels has errors or becomes faulty.
If... Then...
The link is faulty Rectify the fault.
The link is normal Go to the next step.
2. Restart the LCAS protocols at both ends. Then, check whether the alarm clears.
If... Then...
----End
Related Information
None.
A.3.148 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
Minor Service alarm
Parameters
524
Name Meaning
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
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.
l Cause 2: Some paths in the transmit direction of the remote site are faulty.
l Cause 3: Some paths in the receive direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the 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
bound with different number of physical
paths or bound with different timeslots
Correct the configuration data. For details,
see Dynamically Increasing/Decreasing the
VCTRUNK Bandwidth.
Step 2 Cause 2: Some paths in the transmit direction of the remote site are faulty.
1. Check whether any path alarm exists in the transmit direction of the remote site.
If... Then...
Any of the preceding alarms occurs Clear the alarm immediately.
No alarm occurs Go to Cause 3.
Step 3 Cause 3: Some paths in the receive direction of the local site are faulty.
----End
Related Information
None.
525
A.3.149 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
Minor Service alarm
Parameters
Name Meaning
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 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the
remote site is different from that at the local site.
l Cause 2: Some paths in the receive direction of the remote site are faulty.
l Cause 3: Some paths in the transmit direction of the local site are faulty.
Procedure
Step 1 Cause 1: The number of paths or timeslots that are configured for the VCTRUNK at the 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.
526
If... Then...
bound with different number of physical
paths or different timeslots
Correct the configuration data. For details,
see Dynamically Increasing/Decreasing the
VCTRUNK Bandwidth.
bound with the same number of physical
paths or the same timeslots
Go to Cause 2.
Step 2 Cause 2: Some paths in the receive direction of the remote site are faulty.
1. Check whether any path alarm exists in the receive direction of the remote site.
If... Then...
No alarm occurs Go to the next step.
Step 3 Cause 3: Some paths in the transmit direction of the local site are faulty.
----End
Related Information
None.
A.3.150 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
Major Service alarm
Parameters
527
Name Meaning
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 Cause 1: No VCTRUNK is bound to the remote port.
l Cause 2: Paths in the transmit direction of the remote site are faulty.
l 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... Then...
VCTRUNKs has been added, 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 transmit direction of the remote site are faulty.
1. Check whether any path alarm exists in the transmit direction of the remote site.
If... Then...
No alarm occurs Go to Cause 3.
Step 3 Cause 3: Paths in the receive direction of the local site are faulty.
----End
Related Information
None.
A.3.151 LCAS_TLCT
528
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
Major Service alarm
Parameters
Name Meaning
There is no available bandwidth in the transmit direction, and the Ethernet services are
interrupted.
Possible Causes
l Cause 1: No VCTRUNK is bound to the remote port.
l Cause 2: Paths in the receive direction of the remote site are faulty.
l 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... Then...
VCTRUNKs has been added, Correct the configuration data. For details, see
Configuring VCTRUNKs on an Ethernet Board.
No VCTRUNK has been added, Go to Cause 2.
529
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... Then...
No alarm occurs Go to the next step.
Step 3 Cause 3: Paths in the transmit direction of the local site are faulty.
----End
Related Information
None.
A.3.152 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
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 Cause 1: The path connected to the ATM port receives signals in an incorrect manner. For
example, the MS_AIS, AU_AIS or AU_LOP alarm occurs.
l Cause 2: A great number of bit errors occur in the receive path. The receive path reports
alarms indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.
l Cause 3: The ATM processing chip of the board is faulty.
530
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. Check whether the MS_AIS, AU_AIS, or AU_LOP alarm occurs in the path connected
to the ATM port.
2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.
Step 2 Cause 2: A great number of bit errors occur in the receive path. The receive path reports alarms
indicating excessive bit errors, such as B1_EXC, B2_EXC, and B3_EXC.
1. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.
2. If yes, clear these alarms first, and then check whether the LCD alarm is cleared.
Step 3 Cause 3: The ATM processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the LCD alarm. For details, see 8.6.1 Cold
Reset.
2. If the LCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
Smart E1 Interface Board.
----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 For the external ATM port, the threshold of generating the LCD alarm is seven cells.
l For a VC-4 VCTRUNK port, the threshold of generating the LCD alarm is 360 cells.
l For a VC-12 VCTRUNK port, the threshold of generating the ALM_IMA_LINK_LCD
alarm in the bound E1 link is 104 cells. If only one E1 link is bound with the VCTRUNK,
the LCD alarm is reported when the ALM_IMA_LINK_LCD alarm occurs. If 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.153 LCS_LIMITED
Description
The LCS_LIMITED alarm indicates that the configuration capacity of an NE exceeds the
capacity authorized by the license file.
531
Attribute
Parameters
532
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.
l 0x12: No microwave 1+1 protection license is available.
l 0x13: No enhanced QoS license is available.
l 0x14: The capacity configured for the COMBO port exceeds the licensed
capacity.
l 0x15: No second-IF-port license is available.
l 0x16: No MPLS-TP OAM license is available.
l 0x17: No WRED license is available.
l 0x18: No AMAC license is available.
533
Name Meaning
l 0x1a: No HQoS license is available.
l 0x1b: No L2DCN license is available.
l 0x1c: No ITU-T Y.1731 license is available.
l 0x1d: No LLDP license is available.
l 0x20: No IS3 mode license is available.
l 0x1c: No IP FPM license is available.
When the LCS_LIMITED alarm occurs, the change of radio service capacity cannot take effect
on the NE.
Possible Causes
l Cause 1: The configured capacity exceeds the licensed capacity.
l Cause 2: The configured function is unlicensed.
Procedure
Step 1 Determine the alarm cause according to alarm data on the NMS.
Step 2 Query the capacity of the license on the NMS.
Step 3 Cause 1: The configured capacity exceeds the licensed capacity.
1. Check whether the capacity suggested in the alarm data is required.
2. If yes, purchase and load the license with the desired capacity.
3. If not, rectify the capacity configuration.
Step 4 Cause 2: The configured function is unlicensed.
1. Check whether the configured function is required.
2. If yes, purchase and load the desired license.
3. If not, do not enable the function.
----End
Related Information
For TDM services, radio service capacities of NEs are calculated based on the service cross-
connections on IF boards.
A.3.154 LDP_PEER_DOWN
Description
The LDP_PEER_DOWN alarm indicates that a Label Distribution Protocol (LDP) PW peer
becomes unreachable.
534
Attribute
Parameters
None
If graceful restart (GR) is disabled, the PW is interrupted, causing service interruption. If GR is
enabled, the PW is interrupted after the GR timer expires, causing service interruption.
Possible Causes
l Cause 1: LDP configurations are incorrect at the peer end.
l Cause 2: No IP route to the peer end is available.
l Cause 3: The Ethernet link is faulty.
Procedure
Step 1 Cause 1: LDP configurations are incorrect at the peer end.
1. Check whether LDP configurations are correct at the peer end. If the LDP configurations
are incorrect (for example, the authentication mode configured at the peer end differs from
that at the local end), rectify the configurations to ensure configuration consistency at both
ends.
Step 2 Cause 2: No IP route to the peer end is available.
1. Check whether the IP route to the peer end is available using IP ping.
2. Check whether route configurations at both ends are correct. If the configurations are
incorrect, rectify the configurations based on the network plan.
Step 3 Cause 3: The Ethernet link is faulty.
1. Check whether an ETH_LOS alarm is reported from the local end. If such an alarm is
reported, clear it.
----End
A.3.155 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.
535
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always 0x01.
Parameter 2, Parameter 3 Indicates the path ID.
l When this alarm occurs, the alarmed E1 link is unavailable, and the available links in the
IMA group are reduced.
l If the VCTRUNK link binds only one member, the service is interrupted when the LFA
alarm occurs.
l After this alarm clears, the E1 link in the IMA group will be recovered automatically.
Possible 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.
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.
1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware failure
alarm, and check whether the alarm clears.
536
NOTICE
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
A.3.156 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the type of the license file.
l 0x01: AM license
l 0x02: Hybrid license
l 0x03: TDM license
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.
537
Possible Causes
The license file is lost or is not loaded.
Procedure
Step 1 Contact Huawei engineers to reload the license file to the NE.
----End
Related Information
None.
A.3.157 LINK_ERR
Description
The LINK_ERR alarm indicates that a data link is faulty.
Attribute
Parameters
Name Meaning
Parameter 1 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 Cause 1: The optical fiber connected to the Ethernet optical port is faulty.
l Cause 2: The working modes of the ports at the local and opposite ends are different.
l Cause 3: The equipment at the local or opposite end is faulty.
538
Procedure
Step 1 Cause 1: The optical fiber connected to the Ethernet optical port is faulty.
1. Check whether the optical fiber connected to the Ethernet optical port is faulty.
If... Then...
The optical fiber is faulty Replace the fiber.
The optical fiber is not faulty Go to Cause 2.
Step 2 Cause 2: The working modes of the ports at the local and opposite ends are different.
1. Check whether the working modes of the ports at the local and opposite ends are different.
If... Then...
The working modes of the ports at the
local and opposite ends are different
Set the working modes of the ports to the
same.
The working modes of the ports at the
local and opposite ends are the same
Step 3 Cause 3: The equipment at the local or opposite end is faulty.
1. Use an optical fiber to perform a loopback at the the alarmed port. For details, see 8.5
Hardware Loopback.
If... Then...
The alarm is cleared Replace the Ethernet board at the opposite end.
The alarm persists Replace the Ethernet board at the local end.
----End
Related Information
None.
A.3.158 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
539
Name Meaning
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.
Possible Causes
The possible cause of the LMFA alarm is as follows:
l Cause 2: The frame format is incorrect.
Procedure
1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware failure
alarm, and check whether the alarm clears.
NOTICE
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.
Step 2 Cause 2: The frame format is incorrect.
1. Check the frame format of the opposite port. For details, see Setting Advanced Attributes
of Smart E1 Ports.
2. Set the frame format to CRC-4 Multiframe if it is incorrect.
----End
Related Information
Basic frame
Multiframe
540
A multiframe is composed of sixteen PCM frames, and can implement cyclic redundancy check
(CRC).
A.3.159 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loop occurs.
Attribute
Parameters
541
Name Meaning
Parameter 1
Indicates the type of loopback.
l 0x00: optical/electrical port inloop
l 0x01: optical/electrical port outloop
l 0x02: path inloop
l 0x03: path outloop
l 0x04: loopback on the user side
l 0x05: loopback on the multiplexing side
l 0x08: ATM layer inloop
l 0x09: ATM layer outloop
l 0x0A: PHY layer inloop
l 0x0B: PHY layer outloop
l 0x0C: MAC layer inloop
l 0x0D: MAC layer outloop
l 0x0E: VC-4 timeslot inloop
l 0x0F: VC-4 timeslot outloop
l 0x10: VC-3 timeslot inloop
l 0x11: VC-3 timeslot outloop
l 0x12: VC-12 timeslot inloop
l 0x13: VC-12 timeslot outloop
l 0x14: IF outloop
l 0x15: IF inloop
l 0x16: RF inloop
l 0xFF: any of the preceding loopback modes
When the LOOP_ALM alarm occurs, the looped port or path cannot carry services.
Possible Causes
Cause 1: A loop is performed on the local NE.
Procedure
Step 1 Cause 1: A loop is performed on the local NE.
1. Determine the type of loopback according to the alarm parameter.
2. Find out the cause of the loopback, and set the loopback status of the alarmed port to Non-
Loopback.
For details, see 8.4 Software Loopback.
----End
542
Related Information
This table provides parameters and their meanings for LOOP_ALM alarms reported by ports 1
to 7 on an EMS6 board.
Name Meaning
Parameter 1 Indicates the optical port ID. The parameter
takes a fixed value of 0x01.
Parameter 2, Parameter 3 Indicate the path ID (the value 1 indicates that
the optical port is looped back).
Parameter 4 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

This table provides parameters and their meanings for LOOP_ALM alarms reported by ports
VC-3 channels on an EMS6 board.
543
Name Meaning
Parameter 1 Indicates the optical port ID. The parameter
takes a fixed value of 0x01.
Parameter 2, Parameter 3 Indicates the VC-3 channel ID.

A.3.160 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
Minor Service alarm
Parameters
Name Meaning
Parameter 1
l 0x01: 15 minutes
l 0x02: 24 hours
544
Name Meaning
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. Check the threshold crossing records to find out the performance event that the lower order
path error crosses the preset threshold.
----End
Related Information
None.
A.3.161 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.
545
Attribute
Parameters
None.
When the LP_R_FIFO alarm occurs, the service has errors.
Possible Causes
l Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.
Procedure
Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.
1. Browse current performance events, and check whether the performance event of TU
pointer justification occurs on the local NE and the opposite NE.
If... Then...
The TU pointer justification occurs Handle the performance event. For details,
see B.3.33 TUPJCHIGH, TUPJCLOW,
and TUPJCNEW.
The TU pointer justification does not
occur
Go to Cause 2.
----End
Related Information
None.
A.3.162 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.
546
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
lower order path remote receive failure.
Procedure
lower order path remote receive failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None.
A.3.163 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
547
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
When this alarm occurs, the service on the local NE is not affected. The service received by 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.164 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
548
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.165 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
Minor Service alarm
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.
549
Possible Causes
lower order path remote errors.
Procedure
lower order path remote errors.
1. Handle the LP_BBE performance event on the opposite NE.
----End
Related Information
None.
A.3.166 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
Minor Service alarm
Parameters
Name Meaning
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.
550
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.167 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
Name Meaning
Bit errors exist in received services at the opposite site.
Possible Causes
The local site receives a message from the opposite site, and the message says that there are bit
errors at the remote end of a lower order (VC-3) path.
551
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.
1. Handle the alarm in the lower order (VC-3) path at the opposite site.
----End
Related Information
None.
A.3.168 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
lower order path remote failure.
Procedure
lower order path remote failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None.
552
A.3.169 LP_SLM
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
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.170 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.
553
Attribute
Parameters
Name Meaning
The service in this lower order path is unavailable.
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not
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.171 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.
554
Attribute
Parameters
Name Meaning
The services in the lower order (VC-3) path are unavailable.
Possible Causes
The signal label in byte C2 that is received at the local site does not match with the signal 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.172 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.
555
Attribute
Parameters
None.
Bit errors occur in the services.
Possible Causes
l Cause 1: The frequency offset of the input signal is very large.
Procedure
Step 1 Cause 1: The frequency offset of the input signal is very large.
1. Use an SDH analyzer to check whether the frequency offset of the input signal is within
50 ppm.
If... Then...
The frequency offset is very large Troubleshoot the remote site.
The frequency offset is within 50 ppm Go to Cause 2.
----End
Related Information
None.
A.3.173 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.
556
Attribute
Parameters
None.
None.
Possible Causes
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.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
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.174 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.
557
Attribute
Parameters
Name Meaning
None.
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
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.175 LP_TIM_VC3
558
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
Name Meaning
None.
Possible Causes
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.
l Cause 2: The data configuration at intermediate sites is incorrect.
Procedure
Step 1 Cause 1: Byte J1 to be received at the local site does not match with byte J1 to be transmitted 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.
559
A.3.176 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
Possible Causes
The data configuration is incorrect.
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.
l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path 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
configured with services
Configure services for the tributary path at
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
560
Related Information
None.
A.3.177 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
Name Meaning
If the alarm is generated due to incorrect service configurations, the services are interrupted.
Possible Causes
path at the remote site is not configured with services.
l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with services. For details,
561
If... Then...
The tributary path at the remote site is not configured with
services
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
----End
Related Information
None.
A.3.178 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
Name Meaning
The services in the path are unavailable. If the services are configured with protection, protection
switching is triggered.
Possible Causes
562
path at the opposite site is not.
l Cause 2: The cross-connection configuration at the intermediate sites is incorrect.
Procedure
the opposite site is not.
1. Check whether the tributary path at the opposite site is configured with services. For details,
If... Then...
The tributary path at the opposite site is not configured with
services
Configure services.
The tributary path at the opposite site is configured with
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
----End
Related Information
None.
A.3.179 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
563
Name Meaning
Parameter 1
0x01: linear MS protection.
The system performs protection switching in single-ended mode.
Possible Causes
Cause 1: The linear MSP is configured incorrectly.
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
l The switching modes (single-ended or dual-ended) at the local and remote sites are
different.
l The last three bits of the K2 byte are set to the indicated mode.
l The type of the protocol is set to a restructure protocol.
Procedure
Step 1 Cause 1: The linear MSP is configured incorrectly.
1. Change the MSP switching modes at both ends, and ensure that they are the same. For
details, see Querying the Status of the Linear MSP.
----End
Related Information
None.
A.3.180 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
564
Parameters
Name Meaning
Indicates the board ID.
Parameter 3
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.
2. If yes, clear these alarms. Then, check whether the LPT_CFG_CLOSEPORT alarm is
cleared.
----End
Related Information
None.
A.3.181 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.
565
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the IP port.
Parameter 2, Parameter 3 Indicate the port ID.
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... Then...
The LPT function is required 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.
566
A.3.182 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
Critical Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the ID of the IP port.
Parameter 2, Parameter 3 Indicate the ID of the optical interface. The values are always 0x00
0x01.
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 Cause 1: The remote port fails due to the alarms such as ETH_LOS and
LSR_NO_FITED, or the remote port is disabled.
l Cause 2: The LPT service network is faulty.
The communication link is interrupted.
There are the bit error threshold-crossing alarms BIP_EXC and B3_EXC.
There are the alarms such as TU_LOP, TU_AIS, VCAT_LOA,
VCAT_LOM_VC12, and LP_UNEQ_VC12.
567
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.
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... Then...
The opposite port is disabled Enable the opposite port.
The opposite port is enabled Go to the next step.
2. Check whether any link fault alarm occurs on the line board.
If... Then...
Any link fault alarm occurs Handle the link fault alarms. Focus on the R_LOS 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.183 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
568
Parameters
None.
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 Cause 1: The laser is aged.
l 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.184 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 Cause 1: The laser of the local site is not installed.
569
Procedure
Step 1 Cause 1: The SFP optical module of the local site is not installed.
1. Find out why the SFP optical module is not installed, and contact Huawei technical support
engineers for the installation. If SFP module is not needed, see Configuring an SFP Port to
delete this port.
1. 6.14 Replacing the SFP.
----End
Related Information
None.
A.3.185 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 Cause 1: The laser is aged.
l Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser is aged.
1. 6.14 Replacing the SFP.
Step 2 Cause 2: The detection circuit of the board is faulty.
570
1. Replacing the alarm Board.
----End
Related Information
None.
A.3.186 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
Name Meaning
Parameter 1
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 Cause 1: The clock configuration is incorrect.
l Cause 2: All the clock sources in the clock source priority table fail.
l Cause 3: A fiber cut or a cable cut occurs.
l Cause 4: The synchronization source is set to the manual reversion mode.
l Cause 5: No input is available from the external clock source.
l Cause 6: The board is faulty.
571
Procedure
Step 1 Cause 1: The clock configuration is incorrect.
1. Check whether the data in the clock source priority table meets the network planning
requirement. For details, see Querying the Clock Synchronization Status.
If... Then...
The configuration is incorrect Correct the configuration.
The configuration is correct Go to Cause 2.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Troubleshoot the synchronization sources based on the clock source priority table.
If... Then...
external clock
clock
board.
clock
Handle the alarm that occurs on the IF board.
tributary clock
board.
Ethernet clock
Handle the alarm that occurs on the Ethernet
board.
Step 3 Cause 3: A fiber cut or a cable cut occurs.
1. Connect the fiber or cable properly.
Step 4 Cause 4: The synchronization source is set to the manual reversion mode.
1. See Modifying the Recovery Parameter of the Clock Source, and set the clock source to
the automatic reversion mode.
Step 5 Cause 5: No input is available from the external clock source.
1. See Configuring Clock Sources for External Clock Output, and configure the clock source
that provides external clock signals.
Step 6 Cause 6: The board is faulty.
1. Replace the board.
----End
Related Information
None.
572
A.3.187 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crosses
the threshold.
Attribute
Parameters
Parameters
Name Meaning
Parameter 1
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 Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the upper
threshold.
l Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully
transmitted after successive collisions crosses the upper threshold.
l 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.
573
If... Then...
The ports at the transmit and receive
ends work in different modes or in half-
duplex mode
Set the working modes of the ports at the
transmit and receive ends to full-duplex or
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
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.
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.188 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
574
Name Meaning
Parameter 1
l 0x00: indicates that a performance threshold is crossed.
l 0x01: indicates bit-error-triggered switching.
When the MAC_FCS_EXC alarm occurs, the performance of services degrades.
Possible Causes
l Cause 1: The performance of the line signals degrades.
l Cause 2: The input optical power is abnormal.
l Cause 3: A fiber connector is dirty.
Procedure
Step 1 Cause 1: The performance of the line signals degrades.
1. On the NMS, check for a LOOP_ALM alarm. If there is any, clear it. For details, see 8.4
Software Loopback.
2. 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.
3. 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.
Step 2 Cause 2: The input optical power is abnormal.
1. Check whether the alarmed port reports an IN_PWR_ABN alarm as well.
2. If there is any, clear the IN_PWR_ABN alarm.
Step 3 Cause 3: A fiber connector is dirty.
1. Clean the fiber connector and the optical receive port. For details, see 8.10 Cleaning Fiber
Connectors and Adapters.
----End
Related Information
None.
A.3.189 MAC_FCS_SD
Description
The MAC_FCS_EXC alarm indicates that bit errors detected at the MAC layer exceed the
threshold. NE software periodically detects the number of bytes received by MAC chips and the
bytes that contain bit errors, and check the number of bit errors against the signal degrade (SD)
threshold. This alarm is reported if bit errors cross the threshold.
575
Attribute
Parameters
None
Service performance deteriorates.
Possible Causes
l Cause 1: Line signals degrade.
l Cause 2: Input optical power is abnormal.
l Cause 3: Fiber connectors are dirty.
Procedure
Step 1 Cause 1: Line signals degrade.
1. On the NMS, check whether a LOOP_ALM alarm is reported. If a LOOP_ALM alarm is
reported, clear it. For details, see 8.4 Software Loopback.
2. If the MAC_FCS_EXC alarm persists, check whether any source unexpectedly sends a
large amount of data, such as DOS attacks. If yes, eliminate the data source.
3. If the alarm persists, check whether the cable or fiber is faulty. If the cable or fiber is faulty,
replace the faulty cable or fiber.
Step 2 Cause 2: Input optical power is abnormal.
1. Check whether the local port also reports an IN_PWR_ABN alarm.
2. If an IN_PWR_ABN alarm is also reported, clear it.
Step 3 Cause 3: Fiber connectors are dirty.
1. Clean the fiber connectors and the receive port of the processing board. For details, see
8.10 Cleaning Fiber Connectors and Adapters.
----End
Related Information
None
A.3.190 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that Module communicates abnormally.
576
Attribute
Parameters
Name Meaning
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 Cause 1: The software processing of the related modules of the boardis faulty.
l Cause 2: The board hardware is faulty.
Procedure
Step 1 Cause 1: The software processing of the related modules of the board is faulty.
1. Perform a cold reset on the faulty board by using the NMS. For details, refer to 8.6.1 Cold
Reset.
2. remove the faulty board and insert it again.
Step 2 Cause 2: The board hardware is faulty.
1. Replace the faulty board. For details, refer to 6.10 Replacing the System Control,
Switching and Timing Board.
----End
Related Information
None.
A.3.191 MOD_TYPE_MISMATCH
577
Description
The MOD_TYPE_MISMATCH alarm indicates that a mismatched port module is detected.
Attribute
Critical Maloperation
Parameters
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by port 1.
The services at the alarmed port are interrupted.
Possible Causes
Cause 1: The preset type of the SFP module is different from the actual type of the SFP module.
Procedure
Step 1 Cause 1: The preset type of the SFP module is different from the actual type of the SFP module.
1. Find out the port that reports the alarm according to the alarm parameters.
2. Check whether the preset type of the SFP module is the same as the actual type of the SFP
module.
If... Then...
The preset type of the SFP module is the
same as the actual type of the SFP module
Replace the optical/electrical SFP
module. Ensure that the new SFP module is
of the correct type.
The preset type of the SFP module is
different from the actual type of the SFP
module
Reset the type of the SFP module.
----End
Related Information
None.
578
A.3.192 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
Name Meaning
Parameter 1 Indicates the ID of the board.
Parameter 2 Indicates the ID of the subborad.
Parameter 3, Parameter 4 Indicates the ID of the port.
Parameter 5 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 Cause 1: The signal quality of the MP group members deteriorates.
l Cause 2: The maximum differential delay is configured low.
Procedure
Step 1 Cause 1: The signal quality of the MP group members deteriorates.
1. Check whether the network is congested. If yes, expand the network and then check whether
the alarm is cleared.
579
2. If the alarm persists, replace the cable connecting to the port that reports the alarm. Then,
check whether the alarm is cleared.
Step 2 Cause 2: The maximum differential delay is configured low.
1. Check whether the maximum differential delay is configured properly on the NMS. For
details, see Creating MP Groups.
2. If the maximum differential delay is configured low, increase the value based on the actual
situation or disable the fragment function.
----End
Related Information
None.
A.3.193 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.
Attribute
Parameters
Name Meaning
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.
580
l When this alarm occurs, all services that the MP group carries are interrupted.
l 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 Cause 1: The number of the valid activated MP group members is less than that of the
minimum activated links.
l Cause 2: The configurations at both ends of the MP group are inconsistent.
l Cause 3: The NCP protocol on the member links of the MP group is running improperly.
l Cause 4: The physical link is interrupted.
l 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.
2. 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.
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.
Step 3 Cause 3: The NCP protocol on the member links of the MP group is running improperly.
1. On the NMS, check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm exists on
the member links of the MP group.
2. If yes, clear the PPP_LCP_FAIL or PPP_NCP_FAIL alarm immediately. Then, check
whether the MP_DOWN alarm is cleared.
Step 4 Cause 4: The physical link is interrupted.
1. On the NMS, check whether a signal alarm such as R_LOS or T_ALOS exists on the
member links of the MP group.
2. If yes, clear the R_LOS or T_ALOS alarm immediately.
Step 5 Cause 5: The MP group is not configured with an IP address or a subnet mask.
1. Configure an IP address and a subnet mask for the MP group. For details, see Creating MP
Groups.
----End
Related Information
None.
581
A.3.194 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.
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.
Step 2 Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.
1. Check whether a tunnel fault occurs on the S-PE. If an alarm such as
MPLS_TUNNEL_LOCV exists, clear the alarm immediately.
----End
Related Information
None.
582
A.3.195 MPLS_PW_CSF
Description
The MPLS_PW_CSF alarm indicates that client signals fail at the peer end of a PW. This alarm
is reported when one end of a PW receives Client Signal Fail (CSF) OAM packets from the peer
end.
Attribute
Parameters
None.
Services may be interrupted.
Possible Causes
Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
Procedure
Step 1 Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
1. Check whether the peer NE reports any link- or hardware-related alarm on the UNI side.
If yes, clear the alarm.
Possible alarms include:
l Link-related alarm: ETH_LOS
l Hardware-related alarm: BD_STATUS, HARD_BAD
l Alarm related to the IEEE 802.3ah protocol: ETH_EFM_DF,
ETH_EFM_LOOPBACK
----End
Related Information
None.
583
A.3.196 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... Then...
A board on the remote NE is reset or faulty Rectify the fault on the remote NE.
The physical link between the local NE and the
remote NE is faulty
Rectify the fault on the physical link.
The bandwidth allocated to the PW is fully
occupied.
Increase the bandwidth of the PW.
----End
Related Information
None.
A.3.197 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.
584
Attribute
Warning Communication alarm
Parameters
None.
Services may be interrupted if excessive redundant packets are received.
Possible Causes
l Cause 1: Multiple PWs are configured with the same label and PW ID.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple PWs are configured with the same label and PW ID.
1. Check whether multiple PWs are configured with the same label and PW ID.
2. If yes, delete the redundant PWs or change the PW ID and label of each PW to unique
values.
If... Then...
Step 2 Cause 2: Physical links are misconnected.
1. Check whether any fiber or cable is misconnected.
2. If yes, rectify the fault.
----End
Related Information
None.
A.3.198 MPLS_PW_LCK
Description
The MPLS_PW_LCK alarm indicates that a server layer tunnel is administratively locked. This
alarm is reported when the MEP receives a LCK message.
585
Attribute
Parameters
None.
The server-layer tunnel is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
1. Check whether tunnel locking is enabled on the nodes along the PW path. If yes, disable
the CLK after administrative locking (for diagnostic testing or other administrative
purpose) is no longer needed.
----End
Related Information
None.
A.3.199 MPLS_PW_LOCK
Description
The MPLS_PW_LOCK alarm indicates that the locked signal function (LCK) is enabled for the
PW layer.
Attribute
Parameters
None.
586
The PW is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for the PW layer.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the PW layer.
1. Check whether the LCK is enabled for the PW layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no longer
needed.
----End
Related Information
None.
A.3.200 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 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
l Cause 2: The OAM is different between the ends of the PW.
l Cause 3: The PW that carries services is faulty.
l Cause 4: The remote NE of the PW is faulty.
l Cause 5: The service interface is configured incorrectly.
587
l Cause 6: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
1. Check whether the remote NE of the PW stops transmitting CV/FFD packets.
If... Then...
The remote NE of the PW stops
transmitting CV/FFD packets
Enable the CV/FFD detection and then
check whether the alarm clears.
The remote NE of the PW keeps
transmitting CV/FFD packets
Go to Cause 2.
Step 2 Cause 2: The OAM is different between the ends of the PW.
1. Check whether the OAM is different between the ends of the PW. If no, Setting PW OAM
(Y.1711) Parameters according to the plan. If yes, go to cause 3.
Step 3 Cause 3: The PW that carries services is faulty.
1. Check whether the local NE and remote NE of the PW report any alarm related to boards.
If yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is cleared.
2. Check whether any link-related alarm is reported. If yes, clear the alarm. Then, check
whether the MPLS_PW_LOCV alarm is cleared.
If... Then...
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.
2. If the interconnected board of the remote NE reports other alarms, clear these alarms. Then,
check whether the MPLS_PW_LOCV alarm is cleared.
If... Then...
Step 5 Cause 5: The service interface is configured incorrectly.
1. Check whether the service interface is configured correctly according to service planning.
2. If not, reconfigure the service interface. Then, check whether the MPLS_PW_LOCV alarm
is cleared.
If... Then...
588
If... Then...
Step 6 Cause 6: Serious congestion occurs on the network.
1. Check whether the bandwidth allocated to the faulty tunnel is fully occupied.
2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large
amount of invalid data.
----End
Related Information
None.
A.3.201 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 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
Procedure
Step 1 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
1. Check whether the ingress node and egress node of the faulty PW are configured correctly
according to NE planning.
2. If the ingress node or egress node is configured incorrectly, correct the configuration and
then check whether the alarm clears.
589
----End
Related Information
None.
A.3.202 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 Cause 1: The PW is configured incorrectly.
Procedure
Step 1 Cause 1: The PW is configured incorrectly.
1. Check whether the PW are configured correctly according to NE planning.
2. If the PW is configured incorrectly, correct the configuration and then check whether the
alarm clears.
----End
590
Related Information
None.
A.3.203 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.
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.219
MPLS_TUNNEL_OAMFAIL occur on NEs at both ends of the PW. If yes, clear them
immediately.
591
2. Check whether service-related alarms such as A.3.200 MPLS_PW_LOCV occur on NEs
at both ends of the PW. If yes, clear them immediately.
----End
Related Information
None.
A.3.204 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.
592
A.3.205 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.
Attribute
Parameters
None.
Services degrade and moderate packet loss occurs.
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
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.
593
A.3.206 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.
Attribute
Parameters
None.
Services fail and severe packet loss occurs.
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
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.
594
A.3.207 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.
Attribute
Parameters
None.
When this alarm occurs, the MEP receives CCM packets of other PWs.
Possible Causes
l Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
l 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.
Step 2 Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
1. 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.
----End
Related Information
None.
595
A.3.208 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
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.209 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.
596
Attribute
Parameters
None.
PWs.
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.210 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.
597
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
Related Information
None.
A.3.211 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.
598
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, or a faulty
board. If yes, rectify the faults.
----End
Related Information
None.
A.3.212 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.
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.
599
A.3.213 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.
Services may be interrupted if excessive redundant packets are received.
Possible Causes
Procedure
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.214 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.
600
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.
If... Then...
The link-related alarms, such as MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR and MW_LOF, are
reported
Clear these alarms first.
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
Clear these alarms first.
----End
Related Information
None.
A.3.215 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.)
601
Attribute
Parameters
None.
When this alarm occurs, the services that the faulty tunnel carries are interrupted.
Possible Causes
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.
l Cause 2: Severe congestion occurs on the network.
l Cause 4: The physical link between the two ends is faulty.
Procedure
Step 1 Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection packet type
and detection packet period, differ at the two ends.
1. Check whether the MPLS OAM settings are the same at the two ends.
2. If the MPLS OAM settings are different at the two ends, change them to the same.
If... Then...
Step 2 Cause 2: Severe congestion occurs on the network.
1. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is fully
used. If the bandwidth of the faulty tunnel is exhausted, increase the bandwidth or eliminate
the sources that transmit a large amount of invalid data.
If... Then...
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.
602
If... Then...
The alarm persists Go to the next step.
2. Check whether the local NE and the remote NE report alarms related to optical modules or
boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first.
3. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.
If... Then...
Step 4 Cause 4: The physical link between the two ends is faulty.
1. Check whether any fiber or cable is damaged. If yes, replace the damaged fiber or cable.
----End
Related Information
None.
A.3.216 MPLS_TUNNEL_LOCK
Description
The MPLS_TUNNEL_LOCK alarm the locked signal function (LCK) is enabled for a tunnel.
Attribute
Parameters
None.
The tunnel is locked for diagnostic testing or other administrative purposes.
Possible Causes
Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
603
1. Check whether the LCK is enabled for the tunnel layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no longer
needed.
----End
Related Information
None.
A.3.217 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.
Attribute
Parameters
None.
When this alarm occurs, services are interrupted or packets from other tunnels are received.
Possible Causes
l Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ
at the two ends of the tunnel.
Procedure
Step 1 Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at 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.
604
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.218 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.
Attribute
Parameters
None.
When this alarm occurs, the packets from other tunnels are received.
Possible Causes
l Cause 1: Multiple tunnels are configured with the same label.
Procedure
Step 1 Cause 1: Multiple tunnels are configured with the same label.
1. Check whether multiple tunnels are configured with the same label.
2. If multiple tunnels are configured with the same label, delete the redundant labels or change
the label of each tunnel to a unique value.
1. Check whether any fiber or cable is misconnected between the two ends. If yes, connect
the fiber or cable properly.
----End
605
Related Information
On the NE, the label of each MPLS tunnel is unique.
A.3.219 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
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 Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end
and is disabled on the other end.
l Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection
mode is auto-sensing.
Procedure
Step 1 Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end 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. Check whether the sink node of the alarmed tunnel reports the HARD_BAD,
ETH_LOS, or R_LOS alarm.
2. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the
MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None.
606
A.3.220 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.
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.221 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.
607
Attribute
Parameters
None.
Services degrade and moderate packet loss occurs.
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. Check whether the FCS_ERR alarm is reported. If yes, clear the FCS_ERR alarm and then
check whether the MPLS_TUNNEL_SD alarm is cleared.
2. If the alarm persists, proceed to cause 2.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.
1. Check whether the bandwidth allocated to the tunnel is fully used. If the bandwidth of 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.222 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.
608
Attribute
Parameters
None.
When this alarm occurs, the quality of service degrades severely and a large number of packets
are lost.
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. On the NMS, check whether the FCS_ERR alarm is reported. If yes, clear the
FCS_ERR, and then check whether the MPLS_TUNNEL_SF is cleared.
2. If the MPLS_TUNNEL_SF persists, go to Cause 2.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.
1. On the NMS, check whether the bandwidth of the tunnel is fully used. If the bandwidth 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.223 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.
609
Attribute
Parameters
None.
When this alarm occurs, the sink NE receives CCM packets of other tunnels.
Possible Causes
l Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
l 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.
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.224 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
610
Parameters
None.
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.3.225 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.
tunnels.
611
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.226 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.
Attribute
Parameters
None.
When this alarm occurs, the OAM function is affected.
Possible Causes
l Cause 1: The OAM settings differ at the two ends.
l Cause 2: The NE receives packets from an unknown source.
Procedure
Step 1 Cause 1: The OAM settings differ at the two ends.
1. If the MPLS_TUNNEL_UNKNOWN alarm is reported transiently, check whether Tunnel
OAM configuration is changed on the local NE and the opposite NE.
2. If the local NE and the opposite NE have different Tunnel OAM configuration, the
MPLS_TUNNEL_UNKNOWN alarm is reported transiently and then the
612
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. Check whether there is any service configured between the NE and an unknown source, or
whether the NE is connected to an unknown source.
2. If yes, modify the incorrect configuration or reconnect the fibers.
----End
Related Information
None.
A.3.227 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.
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 Cause 1: The transmit unit of the opposite station is faulty.
l Cause 2: The receive unit of the local site is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite station is faulty.
1. Replace the line board at the opposite site based on the type of the alarmed board.
If... Then...
The line board reports the alarm Replace the line board at the opposite end.
613
If... Then...
The IF board reports the alarm Replace the IF board at the opposite end.
2. Replace the board and then check whether the alarm is cleared.
If... Then...
The alarm is cleared after replacement End the fault handling.
If... Then...
The alarm is cleared after the board replacement End the fault handling.
The alarm persists after the board replacement Go to Cause 2.
Step 2 Cause 2: The receive unit of the local site is faulty.
----End
Related Information
None.
A.3.228 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
Minor Service alarm
Parameters
614
Name Meaning
Parameter 1
l 0x01: 15 minutes
l 0x02: 24 hours
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.
Possible Causes
l Cause 1: Services are interrupted for a long time.
l Cause 2: The MS BER performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x16:
1. Check whether fibers are properly connected. If not, connect the fibers again according to
planning information.
2. Check whether cross-connections are configured for service ports. If not, configure cross-
connections again according to planning information.
Step 2 Cause 2: The MS BER performance indicator crosses the preset threshold.
1. Check the threshold crossing records of MS BER performance events to find out the
performance event that crosses the preset threshold. For details, see 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
2. Handle the performance event that crosses the threshold.
----End
615
Related Information
None.
A.3.229 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.
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.
616
A.3.230 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
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.
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.231 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.
617
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1
l 0x01: 15 minutes
l 0x02: 24 hours
l 0x2a: AUPJCHIGH
l 0x2b: AUPJCLOW
l 0x2c: AUPJCNEW
Bit errors may occur in the services.
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 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None.
618
A.3.232 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains several
RPL_OWNER nodes.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 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.
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 Meaning
Parameter 1 to Parameter 4 Indicates the port ID.
Parameter 5, Parameter 6 Indicate the ID of the ERPS instance.

619
A.3.233 MW_AM_TEST
Description
The MW_AM_TEST is an alarm indicating that the IF port is in the AM testing state.
Attribute
Minor Other alarms
Parameters
None.
The transmission capacity is reduced during the AM test, 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
Related Information
None.
A.3.234 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
Minor Service alarm
620
Parameters
None.
When the MW_BER_EXC alarm occurs, the service on the port is interrupted.
Possible Causes
l Cause 1: Signal attenuation on the radio link is very heavy.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power of the ODU is normal. If yes, determine
the abnormality and take proper measures. For details, see 4.4.1 Querying the Historical
Transmit Power and Receive Power
If... Then...
The RSL is lower than the receiver
sensitivity
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.
621
If... Then...
The RSL is higher than the specified RSL
of the network. The offset value is tens of
decibels. The duration is from tens of
Slow up fading occurs. Follow the steps:
1. Follow instructions in 8.1.2 Scanning
Interfering Signals to scan the frequency
spectrum around the radio link and check for
co-frequency interference and bias-
frequency 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
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
the specified RSL of the network and if
the duration is from several milliseconds
to tens of seconds.
Fast fading occurs. Contact the network planning
department to make the following changes:
l Adjust the position of the antenna to block the
reflected wave or make the reflection point
fall on the ground that has a small reflection
coefficient, 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.
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.4.7 Setting Loopback
for the IF Board. Check whether the fault at the opposite end is rectified after the loopback.
622
If... Then...
The fault at the opposite end is not rectified Replace the IF board.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not meet
the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite end.
The fault at the opposite end is rectified End the alarm handling.
Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 8.4.7 Setting Loopback
for the IF Board. Check whether the fault at the local end is rectified after the loopback.
If... Then...
the requirement.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the local end.
Step 4 Cause 4: An interference event occurs.
1. Follow instructions in 8.1.2 Scanning Interfering Signals to scan the frequency spectrum
around the radio link and check for co-frequency interference and bias-frequency
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.
----End
623
Related Information
None.
A.3.235 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
Minor Service alarm
Parameters
None.
The service performance on the port deteriorates. If the equipment is configured with 1+1 FD/
SD protection, switching on the channel side may be triggered.
Possible Causes
Procedure
Transmit Power and Receive Power
624
If... Then...
sensitivity
Follow the steps:
requirement.
range.
1. Follow instructions in 8.1.2 Scanning
Interfering Signals to scan the frequency
spectrum around the radio link and check for
co-frequency interference and bias-
frequency interference.
625
If... Then...
to tens of seconds.
fading.
Follow the steps:
If... Then...
the requirement.
626
If... Then...
Follow the steps:
If... Then...
the requirement.
If... Then...
1. Check whether any co-channel interference occurs.
a. Mute the ODU at the opposite end.
b. Check the RSL at the local end. For details, see Configuring 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.1.2 Scanning Interfering Signals to scan the frequency spectrum
around the radio link and check for co-frequency interference and bias-frequency
interference.
----End
Related Information
None.
627
A.3.236 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
Name Meaning
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.
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.
628
Possible Causes
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.
l Cause 2: The AM enabling is different on both ends of a radio link.
l Cause 3: The 1588 overhead enabling is different on both ends of a radio link.
l Cause 4: The modulation mode is different on both ends of a radio link.
l Cause 5: The service mode is different on both ends of a radio link.
l Cause 6: The IP header compression is different on both ends of a radio link.
l Cause 7: The air interface compression at L2 or L3 is different.
l Cause 8: The number of STM-1 signals is different on both ends of a radio link.
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.237 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.
Possible Causes
l Cause 1: The continuous wave function is enabled.
629
l Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the
IF port or composite port.
l 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. Release the loopback by referring to 8.4.7 Setting Loopback for the IF Board.
2. 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.238 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
Name Meaning
Parameter 1 Indicates the timeslots of E1 services.
630
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.239 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
631
Procedure
Transmit Power and Receive Power.
If... Then...
sensitivity
Follow the steps:
requirement.
range.
1. Check whether intra-frequency or inter-
frequency interference exists by scanning
frequency spectra in microwave channels.
For details, see 8.1.2 Scanning Interfering
Signals.
632
If... Then...
to tens of seconds.
fading.
Follow the steps:
If... Then...
the requirement.
633
If... Then...
Follow the steps:
If... Then...
the requirement.
If... Then...
1. Check for co-channel interference. For details, see 8.1.2 Scanning Interfering Signals.
----End
Related Information
None.
A.3.240 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.
634
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 Cause 1: The link ID of the local site does not match with the link ID of the opposite station.
l Cause 2: The services on other radio links are received due to the incorrect configuration
of the radio link receive frequency at the local or opposite station.
l Cause 3: The antenna receives the radio signals from the other stations, because the
direction of the antenna is set incorrectly.
l Cause 4: The polarization direction of the XPIC is incorrect.
Procedure
Step 1 Cause 1: The link ID of the local 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.
635
If... Then...
The polarization direction does not meet
the requirement of the planning
Delete the working XPIC group that is
configured incorrectly and create the
other working XPIC group again.
The polarization direction meets the
requirement of the planning

b. Check whether Link ID-V and Link ID-H meet the requirement of the planning.
If... Then...
The link ID does not meet the
requirement of the planning
Reset the ID of the radio link of the XPIC
IF board according to the planning. For
details, see Creating an XPIC Working
Group.
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.241 MW_LOF
Description
The MW_LOF is an alarm indicating that the radio frame is lost.
Attribute
Parameters
None.
636
The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: In the case of TDM radio services, the IF working modes at the local site and the
opposite station are different. In the case of services, the channel bandwidth and modulation
modes at the local site and the opposite station are different.
l Cause 3: The operating frequency of the ODU at the local site is inconsistent with the
operating frequency of the ODU at the opposite station.
l Cause 6: The receive power of the ODU is abnormal.
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.
637
1. Ensure that the type of the ODU at the local site is consistent with the type of the ODU at
the opposite station.
2. Reset the operating frequency of the ODU according to the network planning. For details,
see Setting ODU Transmit Frequency Attributes.
Set the transmit frequency of the local site to the same as the receive frequency of the
opposite station. Then, set the receive frequency of the local site to the same as the transmit
frequency of the opposite station.
1. Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
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
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.4.7 Setting
Loopback for the IF Board and . Check whether the fault at the opposite end is
rectified after the loopback.
If... Then...
b. Check whether the cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
d. 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.
1. Locate the fault by looping back the opposite station.
Follow the steps:
638
a. Perform an inloop on the IF port at the local end. For details, see 8.4.7 Setting
Loopback for the IF Board and . Check whether the fault at the local end is rectified
after the loopback.
If... Then...
b. Check whether the cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
d. Check whether the fault at the local end is rectified.
Step 6 Cause 6: The receive power of the ODU is abnormal.
1. At the local 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.
If... Then...
sensitivity
Follow the steps:
requirement.
range.
639
If... Then...
1. Check for co-channel interference. For
details, see 8.1.2 Scanning Interfering
Signals.
to tens of seconds.
fading.
Follow the steps:
1. Check for co-channel interference. For details, see 8.1.2 Scanning Interfering Signals.
----End
640
Related Information
None.
A.3.242 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.
641
A.3.243 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an IP address conflict.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the IP address.
The NEs associated with the IP address may be unreachable to the NMS.
Possible Causes
Cause 1: An IP address conflict occurs on the network.
Procedure
Step 1 Modify IP addresses for the affected NEs according to the network plan.
----End
Related Information
None.
A.3.244 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.
642
Attribute
Parameters
Name Meaning
Parameter 1
Indicate the ID of the routine inspection object.
Parameter 4
Indicates the specific alarm cause when a different bit is 1.
l 0x01: If the first bit is 1, it indicates that the file does not exist.
l 0x02: If the second bit is 1, it indicates that verification of the
file fails.
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 Cause 1: No new NE software is loaded after the existing NE software is erased.
l Cause 2: Loading the NE software is unsuccessful.
Procedure
Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.
Cause 2: Loading the NE software is unsuccessful.
1. Check whether the alarm is caused by the loading operation.
If... Then...
The alarm is caused by the loading
operation
Contact the Huawei technical support
engineers to reload the software.
The alarm is not caused by the loading
operation
643
1. For details, see 6.10 Replacing the System Control, Switching and Timing Board.
----End
Related Information
None.
A.3.245 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.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the location of the file.
l 0x01: the files in the flash memory
l 0x02: the software that is currently running
l 0x03: the software in the CF card
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,
Indicate the IDs of the inconsistent files in the currently running
software if the value of Parameter 1 is 0x02.
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.
644
l This alarm affects active/standby switching of system control boards if the active and
standby system control boards have different NE software versions.
l If no NE software exists in the flash memory, the system is unable to restart after power-
off or reset.
Possible Causes
l Cause 1: The software running on the active and standby SCC boards has different versions.
l Cause 2: The software stored in the ofs1 and ofs2 areas of the active SCC board has different
versions.
l 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.246 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is lost.
Attribute
Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the number of the lost file.
645
l If the board software is lost, the board fails to work normally.
l If the FPGA is lost, the FPGA does not have a backup copy.
Possible 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.247 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is disabled
manually.
Attribute
Parameters
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 N+1 protection may fail, or the protection switching may fail.
646
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.248 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01
The services cannot be switched. If the current paths are unavailable, the services are interrupted.
Possible Causes
l Cause 1: The parameters of the N+1 protection for the alarmed node are set incorrectly.
l Cause 2: The network-wide N+1 protection protocol runs abnormally.
647
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 incorrectly
Set the parameters of the N+1 protection
correctly.
The parameters of the N+1 protection are
set correctly
Go to Cause 2.
Step 2 Cause 2: The network-wide N+1 protection protocol runs abnormally.
1. Stop and restart the protocol manually. For details, see Starting/Stopping the N+1
Protection Protocol.
If... Then...
The alarm is cleared after the protocol is
restarted.
The alarm persists after the protocol is
restarted
Contact the Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
A.3.249 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.
Attribute
Parameters
648
Name Meaning
Parameter1, Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01
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.250 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.
Attribute
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 Cause 1: The NTP server is not configured or is configured incorrectly.
649
l Cause 2: The NTP server cannot communicate with the NE.
l Cause 3: The NTP server fails.
Procedure
Step 1 Cause 1: The NTP server is not configured or is configured incorrectly.
1. Configure the NTP server correctly.
2. Re-configure the NTP parameters for the NE.
Step 2 Cause 2: The NTP server cannot communicate with the NE.
1. Check whether the cable connecting the gateway NE to the NTP server is normal. If not,
rectify the connection fault.
2. Check whether the DCN communication between the NTP server and the NE is normal. If
not, configure the DCN communication correctly.
Step 3 Cause 3: The NTP server fails.
1. Troubleshoot the NTP server.
----End
Related Information
None.
A.3.251 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
Parameters
None.
When the OCD alarm occurs, all the services in the receive direction of the alarmed ATM port
lose cells.
650
Possible Causes
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.
l 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. Check whether the B1_EXC, B2_EXC, or B3_EXC alarm occurs in the receive path.
2. If yes, clear these alarms first, and then check whether the OCD alarm is cleared.
Step 2 Cause 2: The ATM processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the OCD alarm. For details, see 8.6.1 Cold
Reset.
2. If the OCD alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
----End
Related Information
None.
A.3.252 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
651
Name Meaning
Parameter 1
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 Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
l Cause 2: The positive and negative polarities of the storage battery are connected inversely.
l Cause 3: The power module frame is faulty.
l Cause 4: The power monitoring module is faulty.
l Cause 5: The power module is faulty.
Procedure
Step 1 Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
If... Then...
The circuit breaker of the storage battery is open Close the circuit breaker.
The fuse of the storage battery is broken Replace the fuse.
Step 2 Cause 2: The positive and negative polarities of the storage battery are connected inversely.
1. Connect the positive and negative polarities of the storage battery correctly.
Step 3 Cause 3: The power module frame is faulty.
1. Check whether the power module frame is damaged. If the power module frame is damaged,
replace the power module frame.
Step 4 Cause 4: The power monitoring module is faulty.
1. Replace the power monitoring module.
Step 5 Cause 5: The power module is faulty.
1. Check whether the ODC_MDL_ABN alarm is reported.
If... Then...
The ODC_MDL_ABN alarm is reported Rectify the fault by referring the solution
to the ODC_MDL_ABN alarm.
The ODC_MDL_ABN alarm is not
reported
Replace the power module.
----End
652
Related Information
None.
A.3.253 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
Name Meaning
Parameter 1
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 Cause 1 of power-off due to NMS control: The storage battery fails to provide power for
the equipment due to NMS control.
l Cause 1 of power-off due to local human interference: The BAT button on the front panel
of the PMU is set to OFF.
l Cause 1 of power-off due to low voltage: The AC input power is abnormal.
l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the storage battery due to high temperature is set to an inappropriate value.
653
l Cause 2 of power-off due to high temperature: The temperature of the storage battery is
very high.
l Cause 3 of power-off due to high temperature: The temperature sensor of the power module
is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The storage battery fails to provide power for 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... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
The threshold is appropriate Go to the next step.
2. Check whether the AC circuit breaker is closed.
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is incorrect. Connect the cable properly.
The AC power cable is deteriorated and damaged. Replace the cable.
Step 5 Cause 2 of power-off due to low voltage: The power module is faulty.
1. Rectify the fault of the power module by referring to the solution to the
ODC_MDL_ABN alarm.
Step 6 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
1. Rectify the fault of the power monitoring module.
Step 7 Cause 1 of power-off due to high temperature: The temperature that results in power-off of the
power module due to high temperature is set to an inappropriate value.
654
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 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.254 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.
Possible Causes
l Cause 1: The door access alarm is set incorrectly.
655
l Cause 2: The cabinet door is open.
l Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.
l Cause 4: The door sensor is faulty.
l Cause 5: The monitor device is faulty.
l Cause 6: No door sensor is installed.
Procedure
Step 1 Cause 1: The door access alarm is set incorrectly.
1. Check whether the door access alarm is set correctly according to the configuration and
If... Then...
The door access alarm is set correctly Go to Cause 2.
The door access alarm is set incorrectly Set the door access alarm correctly.
Step 2 Cause 2: The cabinet door is open.
1. Close the cabinet door.
Step 3 Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.
1. Check the cable between the door sensor and the monitor device.
If... Then...
The cable is connected incorrectly or is loose Connect the cable properly.
The cable is deteriorated or damaged Replace the cable.
Step 4 Cause 4: The door sensor is faulty.
1. Rectify the fault of the door sensor.
If... Then...
Step 5 Cause 5: The monitor device is faulty.
1. Rectify the fault of the monitor device.
Step 6 Cause 6: No door sensor is installed.
1. Install a door sensor.
----End
Related Information
None.
656
A.3.255 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED is an alarm indicating that the fan is faulty.
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the position of the fault.
l 0x01: The internal fan is faulty.
l 0x02: The external fan is faulty.
The cabinet cannot dissipate heat properly. As a result, the equipment may be damaged and the
services may be affected.
Possible Causes
l Cause 1: The fan cable is connected incorrectly.
l Cause 2: The fan is faulty.
l Cause 3: The fan is not installed.
Procedure
Step 1 Determine the faulty fan according to the alarm parameters displayed on the NMS.
Step 2 Cause 1: The fan cable is connected incorrectly.
1. Connect the cable properly to the fan according to the specified regulations or rules.
Step 3 Cause 2: The fan is faulty.
1. Replace the fan module.
Step 4 Cause 3: The fan is not installed.
1. Install the TEC module that contains a fan.
----End
657
Related Information
None.
A.3.256 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
Minor Environment alarm
Parameters
Name Meaning
Parameter 1
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 Cause 1: The threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the humidity sensor and the monitoring equipment is connected
incorrectly.
l Cause 3: The humidity sensor is faulty.
l Cause 4: The associated monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The threshold that results in an alarm is set incorrectly.
1. Check whether the humidity threshold is set correctly according to the configuration and
658
If... Then...
The humidity threshold is set correctly 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 deteriorated and damaged Handle the exceptions of 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 humidity sensor is faulty.
1. Rectify the fault of the sensor.
If... Then...
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.257 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is powered off.
Attribute
659
Parameters
Name Meaning
Parameter 1
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 Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
l Cause 1 of power-off due to low voltage: The AC input power is abnormal.
l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to low temperature: The cabinet temperature is very low.
l Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the load due to high temperature is set to an inappropriate value.
l Cause 2 of power-off due to high temperature: The cabinet temperature is very high.
l Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
1. Turn on the storage battery for the equipment.
Step 3 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
1. Query the threshold that results in an alarm when the AC power voltage is abnormal. Then,
determine whether the threshold is appropriate according to the configuration and planning
information.
If... Then...
660
If... Then...
The threshold is appropriate Go to the next step.
2. Check whether the AC circuit breaker is closed.
If... Then...
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is
incorrect.
Connect the cable properly.
The AC power cable is deteriorated and
damaged.
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... Then...
The heat exchanger does not work
properly
Rectify the fault of the heat exchange.
The heat exchanger works properly 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...
661
If... Then...
The threshold is appropriate 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. Check whether the ambient temperature is very high all the time.
2. Check whether the heat exchanger works properly.
If... Then...
The heat exchanger does not work
properly
Rectify the fault of the heat exchange.
The heat exchanger works properly 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.258 ODC_MDL_ABN
Description
The ODC_MDL_ABN is an alarm indicating that the power module is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the ID of the alarmed power module.
662
Name Meaning
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 Cause 1: The number of PSUs configured on the NMS is incorrect.
l Cause 2: The power module is not in position.
l Cause 3: The power module is faulty.
l Cause 4: The power monitoring unit is abnormal.
Procedure
Step 1 Cause 1: The power module is not configured on the NMS.
1. Set the logical slot of the power module on the NMS.
Step 2 Cause 2: The power module is not in position, or the power module is not inserted properly.
If... Then...
The power module is not in position Install the power module.
The power module is not inserted securely Install the power module properly.
Step 3 Cause 3: The power module is faulty.
1. Replace the power module.
Step 4 Cause 4: The power monitoring unit is abnormal.
1. Rectify the fault of the power monitoring unit.
----End
Related Information
None.
663
A.3.259 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
Name Meaning
Parameter 1
Indicates the type of the fault.
l 0x56: The AC input power is very high.
l 0x57: The AC input power is very low.
l 0x58: The DC output power is very high.
l 0x59: The DC output power is very low.
l 0x5b: No AC input power is available.
l 0x5c: The AC power voltage is abnormal.
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.
l If the DC output power voltage is abnormal, the services on the equipment are interrupted.
Possible Causes
l Cause 1: The AC input power voltage is abnormal.
l Cause 2: The DC output power voltage is abnormal.
Procedure
Step 1 Cause 1: The AC input power voltage is abnormal.
1. The threshold that results in an alarm due to the AC input power voltage is set incorrectly.
664
If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The AC circuit breaker is open.
If... Then...
3. The AC power cable is connected incorrectly.
If... Then...
The cable is connected correctly Go to the next step.
4. The AC power grid distributes the power abnormally.
If... Then...
The AC power grid distributes the power
abnormally
Rectify the fault of the power module
at the base station.
The AC power grid distributes the power
normally
5. The monitoring equipment is faulty.
If... Then...
The monitoring equipment is faulty Rectify the fault of the monitoring
equipment.
The monitoring equipment is not faulty Perform the operations required when the
Step 2 Cause 2: The DC output power voltage is abnormal.
1. The threshold that results in an alarm is set incorrectly.
If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The PSU module is faulty.
If... Then...
The PSU module is faulty Rectify the fault of the PSU module.
The PSU module is not faulty Go to the next step.
665
3. The power of the storage battery is insufficient.
If... Then...
The power of the storage battery is
insufficient
Recharge the storage battery.
The power of the storage battery is
sufficient
Rectify the fault of the monitoring
equipment.
----End
Related Information
None.
A.3.260 ODC_SMOKE_OVER
Description
The ODC_SMOKE_OVER is an alarm indicating that smoke occurs in an outdoor cabinet.
Attribute
Critical Environment alarm
Parameters
None.
The equipment may be burned.
Possible Causes
l Cause 1: The smoke alarm is set incorrectly.
l Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
l Cause 3: The cable between the smoke sensor and the monitoring equipment is connected
incorrectly.
l Cause 4: The smoke sensor is faulty.
Procedure
Step 1 Cause 1: The smoke alarm is set incorrectly.
1. Check whether the smoke alarm is set correctly according to the configuration and planning
information.
666
If... Then...
The smoke alarm is set correctly Perform the operations required when the
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... Then...
The cable is connected incorrectly or is
loose
The cable is deteriorated and damaged Replace the cable.
The cable is not deteriorated and damaged Perform the operations required when
Step 4 Cause 4: The smoke sensor is faulty.
If... Then...
due to cause 5.
Step 5 Cause 5: The associated monitoring equipment is faulty.
----End
Related Information
None.
A.3.261 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.
667
Attribute
Parameters
Name Meaning
Parameter 1
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 Cause 1: The alarm is set incorrectly.
l Cause 2: The cable between the lightning sensor and the monitoring equipment is connected
incorrectly.
l Cause 3: The lightning sensor is faulty.
l Cause 3: The lightning arrestor is faulty.
Procedure
Step 1 Cause 1: The alarm is set incorrectly.
1. Check whether the alarm is set correctly according to the configuration and planning
information.
If... Then...
The alarm is set correctly 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. Check the cable connection between the sensor and the monitoring equipment.
668
If... Then...
loose
The cable is deteriorated and damaged Replace the cable.
Step 3 Cause 3: The lightning sensor is faulty.
If... Then...
due to cause 4.
Step 4 Cause 3: The lightning arrestor is faulty.
1. Check whether the alarm output end of the lightning arrestor works properly.
If... Then...
The alarm output end of the lightning
arrestor works properly
Perform the operations required when the
The alarm output end of the lightning
arrestor does not work properly
Replace the lightning arrestor.
Step 5 Cause 5: The associated monitoring equipment is faulty.
----End
Related Information
None.
A.3.262 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
669
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 Cause 1: The TEC cable is connected incorrectly.
l Cause 2: The TEC module is faulty.
l Cause 3: The monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The TEC cable is connected incorrectly.
1. Connect the TEC cable correctly.
Step 2 Cause 2: The TEC module is faulty.
1. Replace the TEC module.
----End
Related Information
None.
A.3.263 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
670
Name Meaning
Parameter 1
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 Cause 1: The temperature threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the temperature sensor and the monitoring equipment is
connected incorrectly.
l Cause 3: The temperature sensor is faulty.
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
If... Then...
The temperature alarm is set correctly Perform the operations required when
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.
correctly.
671
If... Then...
loose
Step 3 Cause 3: The temperature sensor is faulty.
If... Then...
due to cause 4.
----End
Related Information
None.
A.3.264 ODC_WATER_ALM
Description
The ODC_WATER_ALM is an alarm indicating that certain water enters the cabinet.
Attribute
Critical Environment alarm
Parameters
None.
The moisture in the cabinet increases, and the equipment in the cabinet may be damaged.
Possible Causes
l Cause 1: The water alarm is set incorrectly.
672
l Cause 2: Certain water enters the cabinet.
l Cause 3: The cable between the water sensor and the monitoring equipment is connected
incorrectly.
l Cause 4: The water sensor is faulty.
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... Then...
The water alarm is set correctly Perform the operations required when the
The water alarm is set incorrectly Set the water alarm correctly.
Step 2 Cause 2: Certain water enters the cabinet.
1. Dry the cabinet and take waterproof measures for the cabinet.
Step 3 Cause 3: The cable between the sensor and the monitoring equipment is connected incorrectly.
correctly.
If... Then...
loose
Step 4 Cause 4: The sensor is faulty.
----End
Related Information
None.
A.3.265 OSPFNBRSTATECHANGE
Description
The OSPFNBRSTATECHANGE alarm indicates that the OSPF neighbor state changes.
673
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the router ID.
Parameter 5 to Parameter 8 Indicate the IP address of the OSPF neighbor.
Parameter 9 to Parameter 12 Indicate the index number of the interface on the OSPF
neighbor.
Parameter 13 to Parameter 16 Indicate the router ID of the OSPF neighbor.
Parameter 17 to Parameter 20 Indicate the OSPF neighbor state.
l 0x01: Down
l 0x02: Attempt
l 0x03: Init
l 0x04: 2-Way
l 0x05: ExStart
l 0x06: Exchange
l 0x07: Loading
l 0x08: Full
Parameter 21 to Parameter 24 Indicate the OSPF process ID.
Parameter 25 to Parameter 28 Indicate the OSPF area ID.
Parameter 29 to Parameter 32 Indicate the index number of the local interface.
Parameter 33 to Parameter 36 Indicate the IP address of the local interface.
Parameter 37 to Parameter 100 Indicate the name of the local interface.
Parameter 101 to Parameter 131 Indicate the name of the VPN instance.
Parameter 132 to Parameter 135 Indicate the alarm cause.
If the neighbor state transitions from Down to Full, no handling is required. If the neighbor state
transitions from Full to Down, services may be interrupted.
NOTE
State changes from Down to Full: Down > Init > 2-way > Exstart > Exchange > Loading >Full
674
Possible Causes
l Cause 1: OSPF configurations are changed at the peer end.
l Cause 2: The peer port is faulty.
l Cause 3: The physical link is faulty.
l Cause 4: The peer NE is faulty.
Procedure
Step 1 Cause 1: OSPF configurations are changed at the peer end.
1. Check whether OSPF configurations are correct at the peer end. If the OSPF configurations
are incorrect (such as incorrect interface IP address configurations, inconsistent
authentication mode configurations, and inconsistent OSPF area configurations), rectify
the configurations to ensure configuration consistency at both ends.
Step 2 Cause 2: The peer port is faulty.
1. Check whether the peer port is faulty, such as the port disabling state and abnormal optical
power. If the peer port is faulty, rectify the fault.
Step 3 Cause 3: The physical link is faulty.
1. Check whether any fiber or cable is broken, damaged, or pressed. If any of the preceding
problems exist, replace the faulty fiber or cable.
Step 4 Cause 4: The peer NE is faulty.
1. If the peer NE is faulty, rectify the fault.
----End
A.3.266 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the port ID.
675
Name Meaning
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 Cause 1: The output optical power is too high or low.
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
requirement
Replace the optical module.
The output optical power is too high Add a proper attenuator to reduce the input
optical power.
----End
Related Information
None.
A.3.267 OUT1TEMP_SENSOR_FAIL
Description
The OUT1TEMP_SENSOR_FAIL is an alarm indicating that the air outlet temperature sensor
of the cabinet fails.
Attribute
676
Parameters
None.
The air outlet temperature data of the TCU cannot be collected.
Possible Causes
l Cause 1: The air outlet temperature sensor is faulty.
l Cause 4: The air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air outlet temperature sensor is faulty.
1. Replace the air outlet temperature sensor.
If... Then...
If... Then...
Step 4 Cause 4: The air outlet temperature sensor is not installed.
1. Install the air outlet temperature sensor.
----End
Related Information
None.
677
A.3.268 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 Cause 1: The external cycling air outlet temperature sensor is faulty.
l Cause 4: The external cycling air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The external cycling air outlet temperature sensor is faulty.
1. Replace the external cycling air outlet temperature sensor.
If... Then...
If... Then...
678
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.269 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
Major Service alarm
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.
Procedure
Step 1 Modify the default user's password.
----End
Related Information
None.
679
A.3.270 PATCH_BD_EXCLUDE
Description
The PATCH_BD_EXCLUDE alarm indicates that an error occurs when a patch package is being
loaded to a board. The board is automatically isolated from patch package loading.
Attribute
Parameters
None
The board is isolated from patch package matching and patch package loading.
Possible Causes
Cause: An error occurs when a patch package is being loaded to the board.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
A.3.271 PATCH_BD_MATCH_FAIL
Description
The PATCH_BD_MATCH_FAIL alarm indicates that the patch package does not match the
board to which the patch package is loaded.
Attribute
Parameters
None
680
Patch package loading fails.
Possible Causes
Cause: The patch package does not match the board to which the patch package is loaded.
Procedure
Step 1 Reload a correct patch package to the board.
----End
Related Information
None
A.3.272 PATCH_CHGSCC_NOTMATCH
Description
The PATCH_BD_EXCLUDE alarm indicates a mismatch between the patch package and the
system control board after the system control board is replaced.
Attribute
Parameters
None
Patch package loading fails.
Possible Causes
Cause: The system control board is replaced.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
681
A.3.273 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that a patch package is incorrect or has been damaged
or deleted.
Attribute
Minor alarm 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 Cause 1: A patch package is incorrect.
l Cause 2: A patch package has been damaged.
l Cause 3: A patch package has been deleted.
Procedure
Step 1 Load a correct patch package.
----End
Related Information
None.
A.3.274 PG_LINK_FAIL
Description
The PG_LINK_FAIL is an alarm indicating that the links in a 1+1 protection group fail.
682
Attribute
Parameters
None.
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.275 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
Major Service alarm
Parameters
683
Name Meaning
Parameter 1 Indicates the board ID.
The services at the NE are not affected, but radio link protection fails.
Possible Causes
l Cause 1: Service alarms occur on the main board.
l Cause 2: Service alarms occur on the standby board.
Procedure
Step 1 Locate the faulty board according to the alarm parameter.
Step 2 Set the Alarm Report Mode to Protection group and board alarms. For details, see 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.276 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that physical link aggregation (PLA)
configurations are inconsistent at two ends of a radio link.
Attribute
Parameters
684
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the PLA group.
Parameter 3, Parameter 4 Indicate the error type.
l 0x00: The PLA group is not configured on the IF board of the
peer NE.
l 0x01: Layer 2 header compression is enabled for only one NE.
l 0x02: Layer 3 header compression is enabled for only one NE.
l 0x03: The number of member links in the PLA group is different
at both ends.
l 0x04: Local member ports and peer member ports do not belong
to the same PLA group.
The services carried by the radio link are unavailable.
Possible Causes
l Cause 1: The PLA group is configured on the local NE, but not configured on the peer NE.
l Cause 2: Frame header compression is enabled for only one NE.
l Cause 3: The number of member links in the PLA group is different at both ends.
l Cause 4: Local member ports and peer member ports do not belong to the same PLA group.
l Cause 5: The types of the PLA working groups at both ends do not match.
Procedure
Step 1 Cause 1: The PLA group is configured on the local NE, but not configured on the peer NE.
1. Configure the PLA group on the peer NE by referring to Creating a PLA/EPLA Group.
Step 2 Cause 2: Frame header compression is enabled for only one NE.
1. Determine the port that needs to be re-configured. For details, see Querying the Status of
a PLA/EPLA Group and the network plan.
2. Enable or disable frame header compression on the port to ensure configuration consistency
at both ends. For details, see Configuring Ethernet Frame Header Compression and Error
Frame Discarding over Air Interfaces.
Step 3 Cause 3: The number of member links in the PLA group is different at both ends.
1. Set the number of member links consistently at both ends by referring to Creating a PLA/
EPLA Group.
Step 4 Cause 4: Local member ports and peer member ports do not belong to the same PLA group.
1. Check whether PLA configurations of the interconnected IF boards comply with the
network plan. For details, see Creating a PLA/EPLA Group.
685
Option Description
If... Then...
The configurations do not comply with the
network plan
Re-configure the PLA group according to
the network plan.
The configurations comply with the
network plan
Verify the IF cable connections between
the IF boards and ODUs to make sure the
radio links are correct established.
Step 5 Cause 5: The types of the PLA working groups at both ends do not match.
1. Modify the PLA type to ensure that the types on both ends are the same. by referring to
Creating a PLA/EPLA Group.
----End
Related Information
None.
A.3.277 PLA_DOWN
Description
The PLA_DOWN alarm indicates that a PLA group is faulty. This alarm is reported when the
number of active member links in a PLA group is 0 or smaller than the preset minimum number
of active member links.
NOTE
The PLA in this section refers to EPLA only.
Attribute
Major Service alarm
Parameters
Name Meaning
The services carried by the PLA group are interrupted.
Possible Causes
The number of active member links in the PLA group is 0 or smaller than the preset minimum
number of active member links.
686
Procedure
Step 1 Check whether the specified minimum number of active links is consistent with the network
plan. If not, re-configure the minimum number of active links. For details, see querying PLA
group status.
Step 2 Clear the PLA_MEMBER_DOWN alarm.
----End
Related Information
None.
A.3.278 PLA_MEMBER_DOWN
Description
The PLA_MEMBER_DOWN alarm indicates that a member link of a PLA group is faulty.
NOTE
The PLA in this section refers to EPLA only.
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 3 Indicates the board ID of the inactive member.
If the PLA_DOWN alarm is also reported, services are interrupted. If the PLA_DOWN alarm
is not reported, only the services carried by the faulty member link are interrupted and available
bandwidth of the PLA group decreases.
Possible Causes
l Cause 1: A member link of the PLA group is faulty at the local end.
l Cause 2: The IF board configured with the PLA group or related ODU hardware is faulty
at the local end.
687
Procedure
Step 1 Cause 1: A member link of the PLA group is faulty at the local end.
1. Determine the associated IF board and radio links based on the ID of the PLA group. For
details, see querying PLA group status.
2. Check whether the MW_LOF, MW_LIM, MW_RDI, R_LOC, and R_LOF alarms are
reported the radio links. If yes, clear these alarms.
Step 2 Cause 2: The IF board configured with the PLA group or related ODU hardware is faulty at the
local end.
1. Determine the associated IF board and ODU based on the ID of the PLA group. For details,
see querying PLA group status.
2. Check whether the IF board and ODU report hardware-related alarms, such as
HARD_BAD, BD_STATUS, VOLT_LOS, WRG_BD_TYPE, and RADIO_MUTE. If
yes, clear these alarms.
----End
Related Information
None.
A.3.279 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
Both GE and FE ports support the PORTMODE_MISMATCH alarm.
Attribute
Minor Service alarm
Parameters
Name Meaning
Indicate the working mode of the FE port.
688
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 non-
auto-negotiation mode.
Procedure
Step 1 Cause 1: The local port works in auto-negotiation mode and the opposite port works in non-
auto-negotiation mode.
1. Disable the opposite port. For details, refer to Setting the Basic Attributes of Ethernet Ports.
2. 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.280 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its threshold.
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the traffic in the receive or transmit direction exceeds its threshold.
l 0x00: indicates the receive direction.
l 0x01: indicates the transmit direction.
689
Services are congested.
Possible Causes
l Cause 1: The configured bandwidth limit is too low.
l Cause 2: The port traffic is too high.
Procedure
Step 1 Cause 1: The configured bandwidth limit is too low.
1. Follow instructions in Configuring Traffic Shaping for Egress Queues to check the
configured bandwidth limit.
2. If the configured bandwidth limit is too low, follow instructions in Configuring Traffic
Shaping for Egress Queues to increase the bandwidth limit value or perform network
expansion.
Step 2 Cause 2: The configured port traffic is too high.
1. Follow instruction in 4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth
Utilization to query the bandwidth utilization over a port.
2. If the port bandwidth utilization is higher than its threshold, check whether a network storm
occurs. If a network storm occurs, eliminate the source that transmits a large amount of
invalid data.
----End
Related Information
None.
A.3.281 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that a port is offline.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm.
Parameter 2, Parameter 3 Have a fixed value of 0x00 0x01.
690
Name Meaning
Parameter 4, Parameter 5 Are reserved and have a fixed value of 0xff.
The services over the alarmed port are interrupted.
Possible Causes
The alarmed port is enabled but house no SFP module.
Procedure
Step 1 Cause: The alarmed port is enabled but house no SFP module.
1. Check whether the alarmed port needs to receive/transmit a service.
If... Then...
The alarmed port needs to receive/
transmit a service
The alarm port does not need to receive/
transmit a service
Follow instructions in Setting the Basic
Attributes of Ethernet Ports to disable the
alarmed port.
2. Check whether the alarmed port houses an SFP module.
If... Then...
The alarmed port houses no SFP
module
Follow instructions in Installing an SFP
Module to add an SFP module.
The alarmed port houses an SFP
module
3. Re-install the SFP module.
If... Then...
The alarm clears No further action is required.
The alarm persists Follow instructions in Replacing an SFP Module to replace the
SFP module.
----End
Related Information
None.
A.3.282 POWER_ABNORMAL
691
Description
The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1
Indicates the number of the voltage channel.
l 0x01: the first channel of 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.
Possible Causes
l Cause 1: The power cable is cut, damaged, or incorrectly connected.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The power cable is cut, damaged, or incorrectly connected.
1. Check whether the power cable is cut, damaged, or incorrectly connected. If the power
cable is cut or damaged, replace it with a proper power cable. If the power cable 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
692
Related Information
None.
A.3.283 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Parameters
Name Meaning
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.
Parameter 2 Indicates the alarm types.
l 0x01: under-voltage
l 0x02: over-voltage
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 Cause 1: The input power or the PIU is abnormal.
l Cause 2: The power module is abnormal.
693
If the alarm is reported on the ODU, the cause is as follows:
l Cause 1: The power module of the ODU is faulty.
Procedure
Step 1 (POWER_ALM reported by a board of the IDU) Cause 1: The input power or the PIU is
abnormal.
1. Check whether alarms are reported on the PIU, If yes, clear these alarms immediately.
Step 2 (POWER_ALM reported by a board of the IDU) Cause 2: The power module is abnormal.
1. Replace the alarmed board. For details, see 6 Part Replacement.
Step 3 (POWER_ALM reported on the ODU) Cause 1: The power module of the ODU is faulty.
1. Replace the ODU. For details, see 6.15 Replacing the ODU.
----End
Related Information
None.
A.3.284 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.
Attribute
Parameters
None.
When this alarm occurs, the LCP negotiation fails and services are interrupted.
Possible Causes
l Cause 1: Parameter configurations on the opposite port are inconsistent with those on the
local port.
l Cause 2: The network is congested or its quality is poor, which causes improper running
of the LCP protocol.
l Cause 3: The physical link is interrupted.
694
Procedure
Step 1 Cause 1: Parameter configurations on the opposite port are inconsistent with those on the local
port.
1. On the NMS, check whether parameter configurations on the peer port are consistent with
those on the local port.
2. If the parameter configurations are inconsistent, modify the parameters. Then, check
3. 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. On the NMS, check whether the bandwidth for the tunnel connected to the ports is
configured low. For details, see Querying MPLS Tunnel Information.
2. 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. Check whether the physical link is connected properly.
2. If not, restore the faulty physical link. Then, check whether the alarm is cleared.
----End
Related Information
None.
A.3.285 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.
695
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.286 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time sources.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the slot ID of the board before the switching.
Parameter 3 Indicates the ID of the subboard before the switching. 0xFF
indicates that there is no subboard.
Parameter 4, Parameter 5 Indicates the ID of the port before the switching.
Parameters 6 to 9 Indicates the ID 1 of the grandmaster clock before the switching.
Parameters 10 to 13 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.
696
Name Meaning
Parameters 19 to 22 Indicates the ID 1 of the grandmaster clock after the switching.
Parameters 23 to 26 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 Cause 1: The physical link between the local NE and the clock source is faulty.
l Cause 2: Information about the grandmaster clock such as the priority 1, quality level, and
priority 2 has changed.
l 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
Related Information
None.
A.3.287 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
697
Parameters
Name Meaning
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 Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
l Cause 2: The transmit NE is faulty.
l Cause 3: The receive NE is faulty.
Procedure
Step 1 Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
1. Reconfigure the P/E attribute. For details, see Setting the PTP NE Attributes.
Step 2 Cause 2: The transmit NE is faulty.
1. Check the transmit NE for troubleshooting, or replace the clock source.
Step 3 Cause 3: The receive NE is faulty.
----End
Related Information
None.
698
A.3.288 PW_DOWN
Description
The PW_DOWN alarm indicates that a PW is disconnected.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the index number of the faulty service.
Parameter 5 to Parameter 8 Indicate the running status at the local end.
Parameter 9 to Parameter 12 Indicate the running status at the peer end.
Services are interrupted.
Possible Causes
l Cause 1: Configurations are changed at the peer end.
l Cause 2: Severe network congestion occurs.
l Cause 3: The physical link is faulty.
l Cause 4: The peer NE is faulty.
Procedure
Step 1 Cause 1: Configurations are changed at the peer end.
1. Check whether PW configurations are consistent at both ends. If the configurations are
inconsistent, rectify the configurations.
Step 2 Cause 2: Severe network congestion occurs.
1. Check the bandwidth utilization of the tunnel. If the bandwidth is exhausted, allocate more
bandwidth resources to the tunnel or eliminate any source that unexpectedly transmits a
large amount of data.
Step 3 Cause 3: The physical link is faulty.
699
1. Check whether any fiber or cable is broken, damaged, or pressed. If any of the preceding
problems exist, replace the faulty fiber or cable.
Step 4 Cause 4: The peer NE is faulty.
1. If the peer NE is faulty, rectify the fault.
----End
A.3.289 PW_DROPPKT_EXC
Description
The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds its
threshold.
Attribute
Warning Processing alarm
Parameters
Parameters
Name Meaning
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.
Procedure
Step 1 Cause: A small number of packets are lost on the alarmed PW.
700
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.290 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
Name Meaning
Parameter 1 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 Cause 1: No service is configured.
l Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer
end.
l Cause 3: The peer services are abnormal and therefore no packet is transmitted to the local
end.
l Cause 4: The port that corresponds to the faulty PW works improperly.
701
Procedure
Step 1 Determine the alarmed board, 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
directions
Go to Step 2.
0x00 Go to Step 4.
0x01 Go to Step 3.
Step 2 Cause 1: No service is configured.
1. Check whether the port is configured with any services. If not, configure services correctly.
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. Replace the board that reports the alarm on the local NE. For details, see 6 Part
Replacement.
2. Check whether the alarm is cleared. If the alarm persists, replace the corresponding board
of the opposite NE.
----End
Related Information
None.
A.3.291 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.
Attribute
702
Parameters
None.
When this alarm occurs, the service protection fails.
Possible Causes
l Cause 1: The remote NE of the PW is not configured with any protection group.
l Cause 2: The service on the protection channel is interrupted.
Procedure
Step 1 Cause 1: The remote NE of the PW is not configured with any protection group.
1. Check whether the remote NE of the PW is configured with a protection group. If yes,
ensure that the configuration is the same at the two ends.
Step 2 Cause 2: The service on the protection channel is interrupted.
1. Check whether the protection channel is faulty. If yes, rectify the fault.
----End
Related Information
None.
A.3.292 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
Parameters
None.
703
Possible Causes
l Cause 2: Certain physical links are incorrectly connected.
Procedure
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
Step 2 Cause 2: Certain physical links are incorrectly connected.
1. Connect the fibers or cables properly.
----End
Related Information
None.
A.3.293 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.
Possible Causes
l Cause 2: Certain physical links are incorrectly connected.
704
Procedure
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
Step 2 Cause 2: Certain physical links are incorrectly connected.
1. Connect the fibers or cables properly.
----End
Related Information
None.
A.3.294 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 Cause 1: The configured protection modes (1+1 protection or 1:1 protection) differ at the
two ends of the PW.
l Cause 2: The configured switching modes (single-ended or dual-ended) differ at the two
ends of the PW.
l Cause 3: The configured revertive modes (revertive or non-revertive) differ at the two ends
of the PW.
705
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.295 PW_APS_DEGRADED
Description
The PW_APS_DEGRADED alarm indicates that a PW automatic protection switching (APS)
protection group is degraded. This alarm is reported when a PW in the protection group is faulty
and availability of the protection group declines. This alarm is cleared when both the working
and protection PWs are functional or faulty.
Attribute
Major Service alarm
Parameters
None
Availability of the protection group declines.
Possible Causes
Cause: A PW in the protection group is faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is reported,
handle the alarm.
----End
706
Related Information
None
A.3.296 PW_APS_OUTAGE
Description
The PW_APS_OUTAGE alarm indicates that a PW automatic protection switching (APS)
protection group is unavailable. This alarm is reported when both the working and protection
PWs in the protection group are faulty and the protection group is unavailable. This alarm is
cleared when a PW becomes available.
Attribute
Major Service alarm
Parameters
None
The protection group is unavailable and the services carried by the protection group are
interrupted.
Possible Causes
Cause: The working and protection PWs in the protection group are faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is reported,
handle the alarm.
----End
Related Information
None
707
A.3.297 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
Procedure
1. At the local end, perform an inloop on the port of the alarmed board. For details, see 8.4
Software Loopback.
If... Then...
The alarm persists after the loopback Replace the alarmed local board.
The alarm is cleared after the loopback Go to Cause 2.
1. Replace alarmed opposite board.
If... Then...
replaced
The fault is rectified. End the alarm handling.
replaced
Replace the system control, switch&timing
board at the opposite end.
----End
708
Related Information
None.
A.3.298 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.
may be triggered.
Possible Causes
l Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).
board).
Procedure
Step 1 Cause 1: Certain high-level alarms are generated (if the alarm is reported by an IF board).
1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR alarm is generated.
If... Then...
The alarm is generated Take priority to clear the
MW_FEC_UNCOR alarm.
The alarm is not generated Go to the next step.

2. Set the inloop on the alarmed IF port.
709
If... Then...
The alarm persists after the inloop is
performed
Go to Cause 4.
The alarm is cleared after the inloop is
performed
Go to Cause 3.

board).
1. If the alarm is reported by an optical interface board, exchange the transmit and receive
fiber jumpers at both ends.
If... Then...
The alarm persists after the exchange Go to Cause 3 or 4
The line port of the opposite station reports
the R_LOF alarm
Troubleshoot the optical fibers.

1. Replace the opposite board where the line unit is or the opposite IF board.
If... Then...
The alarm is cleared after the board
replacement
The fault is rectified, and the alarm
handling is complete.
The alarm persists after the board
replacement

2. Replace the system control and cross-connect board at the opposite end.
If... Then...
replacement
replacement
Go to Cause 4.

----End
Related Information
710
A.3.299 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.
may be triggered.
Possible Causes
l Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).
l Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).
Procedure
Step 1 Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).
1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR alarm is generated.
If... Then...
The alarm is generated Take priority to clear the
MW_FEC_UNCOR alarm.
The alarm is not generated Go to the next step.

2. Set the inloop on the alarmed IF port.
If... Then...
The alarm persists after the inloop is
performed
Go to Cause 4.
The alarm is cleared after the inloop is
performed
Go to Cause 3.
711

Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH line board).
1. If the alarm is reported by an optical interface board, exchange the transmit and receive
fiber jumpers at both ends.
If... Then...
The alarm persists after the exchange Go to Cause 3 or 4
The line port of the opposite station reports
the R_LOF alarm
Troubleshoot the optical fibers.

1. Replace the opposite board where the line unit is or the opposite IF board.
If... Then...
replacement
replacement
Proceed to the next step.

2. Replace the system control and cross-connect board at the opposite end.
If... Then...
replacement
replacement
Go to Cause 4.

----End
Related Information
A.3.300 R_OOF
Description
The R_OOF is an alarm indicating an out-of-frame event on the receive side of the line.
712
Attribute
Parameters
None.
l When this alarm occurs, services are interrupted, and the AIS signal is inserted on the
downstream NE.
l 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 Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 2: The receive board on the local NE is faulty.
l 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.
The transmit optical power of the opposite board is normal Go to the next step.
2. On the NMS, check whether the receive optical power of the local board is within the normal
range.
If... Then...
The receive optical power of the local board is too low Go to the next step.
The receive optical power of the local board is too high Go to Step 2.
3. 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.
4. 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.
713
5. If the alarm persists, check whether the fiber connector is contaminated. If yes, clean the
fiber and fiber connector. For details, see 8.10 Cleaning Fiber Connectors and
Adapters.
6. Check whether the optical cable is aged out, damaged, or pressed. If yes, replace the optical
cable.
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.5 Hardware Loopback.
NOTICE
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... Then...
The alarm persists The local board is faulty. Go to the next step.
The alarm is cleared Go to Step 3.
2. 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
Related Information
None.
A.3.301 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.
714
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 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
l Cause 2: The direction of the antenna is deflected.
l Cause 3: The transmission environment changes.
l Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.
Procedure
Step 1 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
1. Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.
If... Then...
The ODU at the transmit end reports the
RADIO_TSL_LOW alarm
Handle the RADIO_TSL_LOW alarm.
The ODU at the transmit end does not report the
RADIO_TSL_LOW alarm
Go to Cause 2.
Step 2 Cause 2: The direction of the antenna is deflected.
1. Check whether the direction of the antenna is deflected.
If... Then...
The direction of the antenna is deflected Adjust the direction of the antenna.
The direction of the antenna is not deflected Go to Cause 3.
Step 3 Cause 3: The transmission environment changes.
1. Check whether the transmission environment changes. For example, check whether any
building blocks the transmission and increases the link fading significantly.
If... Then...
The transmission environment changes Contact the network planning department for
re-planning the transmission trail.
715
If... Then...
The transmission environment does not
change
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.302 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
Attribute
Warning Equipment alarm
Parameters
None.
The transmitter does not transmit services.
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: The transmitter of the local site is muted manually.
l Cause 3: The IF board is faulty, causing abnormal IF output.
l Cause 4: The data output is abnormal because the ODU is faulty.
Procedure
Step 1 Cause 1: The other alarms are generated.
1. Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. If
yes, take priority to clear the alarm.
Step 2 Cause 2: The transmitter of the local site is muted manually.
716
1. Check whether the transmitter of the ODU is muted. For details, see Configuring a Single-
Hop 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.303 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.
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 Cause 1: Antennas are not aligned during the equipment commissioning.
l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.
717
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.304 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
Possible Causes
l Cause 1: The local ODU is faulty.
l Cause 2: There is a strong interference source nearby.
l Cause 3: The transmit power of the opposite ODU is very high.
Procedure
Step 1 Cause 1: The local ODU is faulty.
718
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.305 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.
Possible Causes
l Cause 1: Other alarms occur at the opposite station.
l Cause 2: The transmit power of the opposite station is very low.
l Cause 3: The local ODU is faulty.
719
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.
1. Replace the ODU at the local end.
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
Related Information
None.
A.3.306 RADIO_TSL_HIGH
720
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
1. Replace the ODU.
----End
Related Information
None.
A.3.307 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.
Attribute
721
Parameters
None.
Possible Causes
Cause 1: The local ODU is faulty.
Procedure
1. Replace the ODU.
----End
Related Information
None.
A.3.308 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.
Possible Causes
Cause 1: There is a critical alarm input.
722
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.309 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.
Then, the RELAY_ALARM_IGNORE alarm is cleared.
----End
Related Information
None.
723
A.3.310 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.
Then, the RELAY_ALARM_MAJOR alarm is cleared.
----End
Related Information
None.
A.3.311 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.
724
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.
Then, the RELAY_ALARM_MINOR alarm is cleared.
----End
Related Information
None.
A.3.312 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
725
Name Meaning
Parameter 2, Parameter 3 Indicate the path ID.
When this alarm occurs, the services at the local site are not affected. The alarm indicates 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.313 RPS_INDI
Description
The RPS_INDI is an alarm indicating that the radio protection switching is detected.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the ID of the protection group.
726
Name Meaning
Parameter 2
Indicates the type of protection switching.
0x01: HSB protection switching
l During the HSB protection switching, services are interrupted. After the HSB switching is
complete, the services are restored to normal.
l During the HSM protection switching, no bit errors occur and the services are not affected.
Possible 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
manual switching
Find the cause and release the 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
727
l RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH
l IF_INPWR_ABN or CONFIG_NOSUPPORT
l R_LOC, R_LOF, R_LOS, or MW_LOF
NOTE
l If the switching is non-revertive, the services are not automatically switched to the working 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 B1_SD or B2_SD
----End
Related Information
None.
A.3.314 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.
728
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1
l 0x01: 15 minutes
l 0x02: 24 hours
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 Cause 1: Services are interrupted for a long time.
l 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:
729
1. Check whether fibers are properly connected. If not, connect the fibers again according to
2. Check whether cross-connections are configured for service ports. If not, configure cross-
connections again according to planning information.
Step 2 Cause 2: The regenerator section bit error performance indicator crosses the preset threshold.
1. Find out the performance event that crosses the preset threshold. For details, see 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
----End
Related Information
None.
A.3.315 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 Cause 1: The RTC on the system control board is abnormal.
l Cause 2: The board temperature is too high.
Procedure
Step 1 Cause 1: The RTC on the system control board is abnormal.
1. Replace the system control, switching, and timing board.
Step 2 Cause 2: The board temperature is too high.
730
1. 4.3.1 Browsing Current Alarms, and if the board reports the TEMP_ALARM alarm,
clear this alarm first.
----End
Related Information
None.
A.3.316 RT_TBL_LACK
Description
The RT_TBL_LACK alarm indicates that routing table resources are insufficient.
Attribute
Parameters
Name Meaning
Parameters 1-4
Indicate the IP address.
Parameters 5-8
Indicate the mask of the IP address.
Routes fail to be added into the routing table, and the associated services are unavailable.
Possible Causes
The number of routes or next hops in the routing table exceeds the maximum number allowed.
Procedure
Step 1 Reduce service routes by re-planning services.
----End
731
Related Information
None
A.3.317 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte
mode.
Attribute
Parameters
Name Meaning
Parameter 1
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 Cause 1: The original clock source is lost.
l Cause 2: The fiber is cut off.
l Cause 3: The external BITS is interrupted.
l Cause 4: The S1_SYN_CHANGE alarm occurs at the upstream station.
Procedure
Step 1 Cause 1: The original clock source is lost.
1. Handle the SYNC_C_LOS alarm that is related to the original clock source.
732
Step 2 Cause 2: The fiber is cut off.
1. Replace the faulty fiber.
Step 3 Cause 3: The external BITS is interrupted.
1. Check whether the cable connect NE to BITS is normal. If not, replace the faulty cable.
Step 4 Cause 4: The S1_SYN_CHANGE alarm reported at the upstream station.
1. Handle the S1_SYN_CHANGE alarm reported at the upstream station.
----End
Related Information
None.
A.3.318 SCCDATA_BACKUP_FAIL(SYNC_FAIL)
Description
The SCCDATA_BACKUP_FAIL(SYNC_FAIL) is an alarm indicating that the batch backup
on SCC boards fails.
NOTE
SCCDATA_BACKUP_FAIL and SYNC_FAIL indicate the same alarm. SYNC_FAIL is used on NMS
of earlier versions and SCCDATA_BACKUP_FAIL is used on NMS of later versions.
Attribute
Parameters
Name Meaning
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.
733
Data synchronization between the main and standby SCC boards fails, and the switching between
the two boards is unavailable.
Possible Causes
l Cause 1: The main and standby SCC boards have different versions of software.
l Cause 2: Communication between the main and standby SCC boards fails.
l Cause 3: Databases on the main and standby SCC boards are damaged.
l Cause 4: The main and standby SCC boards have different data after an upgrade.
Procedure
Step 1 Cause 1: The main and standby SCC boards have different versions of software.
1. Query and record the software versions of the main and standby SCC boards according to
4.8.4 Querying the Board Information Report.
2. If the software versions are different, determine the correct version based on the version
mapping table and replace the SCC board with an incorrect version. For details, see 6.10
Replacing the System Control, Switching and Timing Board.
Step 2 Cause 2: Communication between the main and standby SCC boards fails.
1. Check whether the system reports the COMMUN_FAIL alarm.
2. If yes, clear the COMMUN_FAIL alarm. The system will start batch backup
automatically.
Step 3 Cause 3: Databases on the main and standby SCC boards are damaged.
1. Check whether the system reports the DBMS_ERROR alarm. For details, see 4.3.1
Browsing Current Alarms.
2. If yes, clear the DBMS_ERROR alarm. Then, check whether the SYNC_FAIL alarm is
cleared.
Step 4 Cause 4: The main and standby SCC boards have different data after an upgrade.
1. Re-install the standby SCC board.
----End
Related Information
None.
A.3.319 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.
734
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 16 Indicates the username.
A user cannot log in to an NE.
Possible Causes
l Cause 1: The active period of the account expires.
l Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access
policies.
l Cause 3: There are unauthenticated login attempts.
l Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
Procedure
Step 1 Cause 1: The active period of the account expires.
1. Use an active account.
Step 2 Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access
policies.
1. Enter the correct password.
2. Set correct access policies.
Step 3 Cause 3: There are unauthenticated login attempts.
1. Eliminate the source that initiates the unauthenticated login attempts.
Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
1. Set the shared key correctly.
----End
Related Information
None.
735
A.3.320 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the terminal type used in the login attempt.
Parameters 2 and 3
Indicate the errors that occur in the login attempt.
Parameters 4 and 5 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 900 seconds. During
the 900 seconds, the user cannot log in to the NE.
736
A.3.321 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
Parameters
None.
The loop of the alarmed Ethernet service is released, and the Ethernet service is restored.
Possible Causes
Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is deactivated.
Procedure
Step 1 Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is deactivated.
1. Check whether a service is looped back on the path of the alarmed Ethernet service.
2. Re-configure the preceding service based on the network plan.
----End
Related Information
None.
A.3.322 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.
Attribute
Major Equipment Alarm
737
Parameters
None.
Unencrypted certificate file is stored on device, private key of the file maybe be get illegally.
Possible Causes
Certificate file of SSL is not encrypted.
Procedure
Step 1 Download and verify the encrypted SSL certificate by NMS.
----End
Related Information
None.
A.3.323 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT is an alarm indicating a subnetwork route conflict. This alarm
occurs when the subnet route of an NMS port, that is, the IP subnet route of an NE, covers the
learned route of an OSPF subnet whose mask is longer than that of the IP subnet.
Attribute
Parameters
Name Meaning
Parameter 1 to Parameter 4 Indicate the IP address of the subnet whose route is covered by
the NE IP subnet route and whose mask is longer than that of the
NE IP subnet. When the routes of multiple subnets are covered
by the IP subnet route, this parameter is the IP address of the
subnet with the longest mask.
738
Name Meaning
Parameter 5 Indicates the mask length.
The NMS cannot manage the NEs through the NMS port of the NE that report the
SUBNET_RT_CONFLICT alarm.
Possible Causes
The subnet route of an NMS port (the IP subnet route of an NE) covers the learned route of an
OSPF subnet whose mask is longer than that of the IP subnet.
Procedure
Step 1 Collect the information about all NEs that report this alarm and check the DCN networking
based on the planned network topology.
Step 2 Obtain the information about the conflicting subnets and their masks based on the alarm
parameters.
Step 3 Determine the rectification plan based on the network topology and subnet information to ensure
that the subnet masks of non-gateway NEs are consistent with the mask of the gateway NE.
When subnet masks of multiple NEs need to be changed, change their subnet masks from the
farthest NE to the nearest one.
CAUTION
If the mask of a gateway NE needs to be changed, ensure that the DCN route after the change
is correct. If the DCN route is incorrect, NEs may be unreachable to the NMS.
Step 4 Change the subnet masks of NEs according to the plan.
----End
Related Information
The SUBNET_RT_CONFLICT alarm is generally caused by incorrect configurations of subnet
masks on NEs. For example, NE1 and NE2 are connected using air interfaces and the OSPF
protocol is enabled. The communication parameters and routing information of the two NEs are
listed in the following table.
If the NMS whose IP address is 129.9.0.254 is connected to the NMS port of NE1, the route of
packets transmitted from NE1 to the NMS is "129.9.0.0/255.255.255.0/129.9.0.2/OSPF/air
interface" according to the longest match principle. That is, the packets are transmitted from the
air interface of NE1 to the air interface of NE2 and finally to the NMS port of NE2. Therefore,
the NMS cannot manage NE1 properly.
739
NE Parameter
NE1 IP address 129.9.0.1
Subnet mask 255.255.0.0
Main IP routes
(destination IP address/
subnet mask/gateway/
protocol/interface)
l 129.9.0.0/255.255.0.0/129.9.0.1/direct/Ethernet
l 129.9.0.0/255.255.255.0/129.9.0.2/OSPF/IF
l 129.9.0.1/255.255.255.255/127.0.0.1/direct/loop
l 129.9.0.2/255.255.255.0/129.9.0.2/direct/IF
NE2 IP address 129.9.0.2
Subnet mask 255.255.255.0
Main IP routes
(destination IP address/
subnet mask/gateway/
protocol/interface)
l 129.9.0.0/255.255.255.0/129.9.0.1/direct/Ethernet
l 129.9.0.0/255.255.0.0/129.9.0.2/OSPF/air interface
l 129.9.0.2/255.255.255.255/127.0.0.1/direct/loop
l 129.9.0.1/255.255.255.0/129.9.0.2/direct/IF

A.3.324 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.
740
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... Then...
The radio link is faulty 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
Related Information
None.
A.3.325 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.
741
1. Contact the Huawei technical support engineers for troubleshooting.
----End
Related Information
None.
A.3.326 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 get online, if the system detects that the system control
board and any other boards 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 other boards.
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 other boards.
1. Re-load the software packages on the NE where the SWDL_CHGMNG_NOMATCH
alarm is reported.
----End
Related Information
None.
742
A.3.327 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
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. Check whether the loaded package is correct.
2. Perform the package diffusion again on the NE where the alarm is reported.
----End
Related Information
None.
A.3.328 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.
Attribute
Warning Processing alarm
743
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.
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.329 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 If this alarm occurs during package loading, package loading fails.
l If this alarm occurs in other conditions, automatic file matching fails.
Possible Causes
Cause 1: Certain files of the package are missing and cannot be recovered.
744
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.3.330 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.
745
A.3.331 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.
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.332 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.
746
Attribute
Parameters
None.
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.333 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.
747
Possible Causes
l Cause 1: The quality of the synchronization source declines.
Procedure
Step 1 Cause 1: The quality of the synchronization source declines.
1. Take different measures based on the traced synchronization source.
If... Then...
The traced synchronization source is an
external clock
Perform Steps Step 1.2 to Step 1.4.
The traced synchronization source is a
line clock
Replace the system control,
switching&timing board of the upstream
NE.
2. Check whether the configuration of the external clock is correct.
If... Then...
The configuration is incorrect Change the configuration data.
The configuration is correct Go to the next step.
3. Check whether the opposite equipment that provides the clock source is faulty.
If... Then...
The equipment functions normally Go to the next step.
4. Check whether the cable that is connected to the external clock source is in normal status.
If... Then...
The cable is not in normal status Replace the cable.
The cable is in normal status Go to Cause 2.
----End
Related Information
None.
A.3.334 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.
748
Attribute
Parameters
None.
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... Then...
external clock
clock
Handle the alarm that occurs on the IF
board.
clock
board.
tributary clock
board.
----End
Related Information
None.
A.3.335 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NE
and the syslog server fails.
749
Attribute
Parameters
None.
The syslog information of the NE cannot be sent to the syslog server.
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.336 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.
750
Possible Causes
l Cause 1: No 2Mbit/s services are received on the port.
l Cause 3: The IF cable 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.
The services are received Go to Cause 2.
Step 2 Cause 2: The equipment at the opposite end is faulty.
1. Check whether the equipment at the opposite end is faulty.
If... Then...
The equipment is normal Go to Cause 3.
Step 3 Cause 3: The IF cable is faulty.
1. Check whether the IF cable is faulty.
If... Then...
The IF cable is faulty Rectify the fault.
The IF cable is not faulty Go to Cause 4.
----End
Related Information
None.
A.3.337 T_LOC
Description
The T_LOC is an alarm indicating that the clock is lost on the transmit line side.
751
Attribute
Parameters
None.
The services in the alarmed AU-4 path are interrupted.
Possible Causes
l Cause 1: The cross-connect and timing board is faulty.
l Cause 2: The line board is faulty.
Procedure
Step 1 Cause 1: The cross-connect and timing board is faulty.
1. Replace the cross-connect and timing board at the local site.
If... Then...
replaced
handling.
replaced
Go to Cause 2.
Step 2 Cause 2: The line board is faulty.
----End
Related Information
None.
A.3.338 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is too high.
752
Attribute
Parameters
None.
When this alarm occurs, the laser is functioning improperly. As a result, services are interrupted.
Possible Causes
l Cause 1: The ambient temperature of the board is too high.
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.339 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is too low.
Attribute
Parameters
None.
753
When this alarm occurs, the laser is functioning improperly. As a result, services are interrupted.
Possible Causes
l Cause 1: The ambient temperature of the board is too low.
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.3.340 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the board temperature crosses the threshold.
Attribute
Minor Environmental alarm
Parameters
Name Meaning
Parameter 1
l 0x01: The temperature crosses the upper threshold.
l 0x02: The temperature crosses the lower threshold.
The board fails to work normally.
754
Possible Causes
l Cause 1: The board temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The board temperature crosses the threshold.
1. If the alarm is reported by the ODU, take appropriate measures (for example, installing a
sunshade) to control the temperature.
2. If the alarm is reported by the board on the IDU, check whether the temperature control
devices, such as air-conditioners, work normally.
If... Then...
The temperature control devices work
abnormally
Adjust the temperature control devices.
normally
3. Check whether the heat dissipation hole on the IDU is covered or blocked.
If... Then...
The heat dissipation hole is covered or
blocked
Clear or remove the covering materials or
obstacles.
The heat dissipation hole is not covered or
blocked
Go to Cause 2.
Step 2 Cause 2: The temperature detection circuit of the board is faulty.
1. If the ambient temperature is normal and no other heat dissipation problems exist, replace
the alarmed board.
----End
Related Information
None.
A.3.341 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature of the board crosses the
threshold.
755
Attribute
Parameters
Name Meaning
Parameter 1
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 Cause 1: The board temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The board temperature crosses the threshold.
1. Check whether temperature control devices, such as air-conditioners, work properly.
If... Then...
The temperature control devices
malfunction
Adjust the temperature control devices.
properly
2. Check whether the heat dissipation hole on the IDU is covered or blocked.
If... Then...
The heat dissipation hole is covered or
blocked
Clear or remove the covering materials or
obstacles.
The heat dissipation hole is not covered or
blocked
Step 2 Cause 2: The temperature detection circuit of the board is faulty.
756
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.342 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.
Possible Causes
l Cause 1: The laser module is damaged.
l Cause 2: The laser is aged out.
Procedure
Step 1 6.14 Replacing the SFP.
----End
Related Information
None.
A.3.343 THUNDERALM
Description
The THUNDERALM is an alarm indicating the surge protection failure. If the system detects
the surge protection circuit fails, the THUNDERALM occurs.
757
Attribute
Parameters
Name Meaning
Parameter 1
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 Cause 1: The fuse tube of the surge protection circuit is interrupted.
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.
1. Replace the board that reports the THUNDERALM alarm.
----End
Related Information
None.
A.3.344 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a time locking failure.
758
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.
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.345 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.
759
Attribute
Parameters
Name Meaning
Parameter 1 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.
Possible Causes
l Cause 1: The clock source priority table is not configured when an external clock interface
is used to trace the upstream NE clock.
l Cause 2: The link between the traced upstream time source and the NE is faulty.
l 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.
760
A.3.346 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
Name Meaning
Parameter 1 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 If the protection cross-connect board is faulty, the services are not affected.
l If the working cross-connect board is faulty, the services are switched, therefore causing
transient service interruption.
Possible Causes
l Cause 1: If one board reports this alarm, the board hardware is faulty.
l Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board 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.
761
2. 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.
3. If the alarm persists, replace the alarmed board. For details, see Replacing a Board.
Step 3 Cause 2: If multiple boards report this alarm, the clock cable of the cross-connect board is faulty.
1. If the working cross-connect board is faulty, perform 1+1 protection switching on the cross-
connect board. For details, see Performing 1+1 Protection Switching.
2. Perform a cold reset on the protection cross-connect board, and then check whether the
alarm is cleared.
3. If the alarm persists, remove and insert the protection cross-connect board, and then check
4. If the alarm persists, replace the protection cross-connect board.
----End
Related Information
None.
A.3.347 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 Cause 2: The line is faulty.
l Cause 3: The board at the opposite end is faulty.
l Cause 4: The board at the local end is faulty.
762
Procedure
1. See Creating the Cross-Connections of Point-to-Point Services to check whether the service
data is incorrect.
If... Then...
The service data is incorrect Change the configuration data.
The service data is correct Go to Cause 2.
Step 2 Cause 2: The line is faulty.
1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
The line alarm is reported Clear the line alarms that cause AIS insertion.
No line alarms are reported Go to the next step.
2. See 8.4 Software Loopback to locate whether the board at the local end or at the opposite
end is faulty.
If... Then...
The board at the opposite end is faulty Go to Cause 3.
The board at the local end is faulty Go to Cause 4.
Step 3 Cause 3: The board at the opposite end is faulty.
1. Replace the faulty board at the opposite end.
Step 4 Cause 4: The board at the local end is faulty.
1. Replace the board where the local line unit resides.
If... Then...
replaced
handling.
replaced
2. Replace the system control, cross-connect, and timing board at the local end.
If... Then...
replaced
handling.
replaced
763
----End
Related Information
None.
A.3.348 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
Parameters
Name Meaning
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 Cause 2: The line is faulty.
l Cause 3: The board at the opposite site is faulty.
l Cause 4: The board at the local site is faulty.
Procedure
764
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Cause 2.
Step 2 Cause 2: The line is faulty.
1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
The line alarm is reported Change the configuration data.
No line alarms are reported Go to Step 3.
Step 3 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.6
Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.
If... Then...
The board at the opposite site is faulty Go to Cause 3.
The board at the local site is faulty Go to Cause 4.
Step 4 Cause 3: The board at the opposite site is faulty.
1. Replace the faulty board at the opposite site.
Step 5 Cause 4: The board at the local site is faulty.
1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical
Interface Board.
If... Then...
The alarm clears after the board is
replaced
handling.
replaced
2. Replace the alarmed board at the local site.
----End
Related Information
None.
765
A.3.349 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
Name Meaning
The services in the alarmed TU-3 paths are interrupted. If the services are configured with
protection, protection switching is triggered.
Possible Causes
l Cause 1: SDH service configuration data is incorrect.
l Cause 2: The service path is faulty.
Procedure
Step 1 Cause 1: SDH service configuration data is incorrect.
1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to check
whether the SDH service configuration data is incorrect.
If... Then...
The SDH service configuration data is
incorrect
Rectify the SDH service configuration
data.
766
If... Then...
correct
Go to cause 2.
Step 2 Cause 2: The service path is faulty.
1. Check whether a line alarm that will cause AIS insertion is reported on the service path.
NOTE
For the line alarms that will cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
A line alarm that will cause AIS
insertion is reported
Rectify the SDH service configuration data.
No line alarm is reported Go to step 3.
Step 3 Follow instructions in 8.4.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... Then...
The board at the opposite end is faulty Go to cause 3.
The board at the local end is faulty Go to cause 4.
1. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the line
board at the local end.
If... Then...
2. Follow instructions in 6.10 Replacing the System Control, Switching and Timing
Board to replace the system control, switching, and timing board.
If... Then...
The alarm persists Follow instructions in Replacing an Alarmed Board to replace the
board that reports the alarm.
----End
Related Information
None.
767
A.3.350 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,
Possible Causes
l Cause 1: The system control, cross-connect, and timing board is faulty.
l Cause 2: The tributary board is faulty.
Procedure
Step 1 Cause 1: The system control, cross-connect, and timing board is faulty.
1. Replace the system control, cross-connect, and timing board at the local end.
If... Then...
replaced
handling.
replaced
Go to Cause 2.
Step 2 Cause 2: The tributary board is faulty.
1. Replace the board where the tributary unit resides.
----End
Related Information
None.
A.3.351 TU_LOP_VC12
768
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
Name Meaning
Services in the alarmed TU path are interrupted. If the services are configured with protection,
Possible Causes
l Cause 2: The board at the opposite site is faulty.
l Cause 3: The board at the local site is faulty.
Procedure
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Step 2.
Step 2 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.6
Setting Loopbacks for the EOS/EoPDH-Plane Ethernet Interface Board.
769
If... Then...
The board at the opposite site is faulty Go to Cause 2.
The board at the local site is faulty Go to Cause 3.
Step 3 Cause 2: The board at the opposite site is faulty.
1. In this case, replace the faulty board at the opposite site.
Step 4 Cause 3: The board at the local site is faulty.
1. Replace the line board at the local site. For details, see 6.3 Replacing the SDH Optical
Interface Board.
If... Then...
replaced
handling.
replaced
2. Replace the alarmed board at the local site.
----End
Related Information
None.
A.3.352 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.
Attribute
Parameters
770
Name Meaning
The services in the alarmed TU-3 path are interrupted. If the services are configured with
protection, protection switching is triggered.
Possible Causes
l Cause 1: SDH service configuration data is incorrect.
Procedure
Step 1 Cause 1: SDH service configuration data is incorrect.
1. Follow instructions in Creating the Cross-Connections of Point-to-Point Services to check
whether the SDH service configuration data is incorrect.
If... Then...
incorrect
Rectify the SDH service configuration
data.
correct
Go to step 2.
Step 2 Follow instructions in 8.4.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... Then...
The board at the opposite end is faulty Go to cause 2.
The board at the local end is faulty Go to cause 3.
1. Follow instructions in 6.3 Replacing the SDH Optical Interface Board to replace the line
board at the local end.
If... Then...
771
2. Follow instructions in 6.10 Replacing the System Control, Switching and Timing
Board to replace the system control, switching, and timing board.
If... Then...
3. Follow instructions in Replacing an Alarmed Board to replace the board that reports the
alarm.
----End
Related Information
None.
A.3.353 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED is an alarm indicating that a tunnel protection group
degrades.
Attribute
Major Service alarm
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.
Procedure
Step 1 Check the status of the tunnel protection group, locate the failed tunnel in the protection group.
Step 2 Querying MPLS tunnel information, locate the board and port used by the failed tunnel.
Step 3 If the port is a Ethernet port, refer to Setting the Basic Attributes of Ethernet Ports, check whether
the port is disabled.
Enable the port if it was disabled.
772
Step 4 Refer to 4.3.1 Browsing Current Alarms, check whether any relevant Ethernet services alarms
are generated in the port or board. If yes, take priority to clear them.
l Hardware alarms: Such as HARD_BAD, POWER_ALM, BD_STATUS,
COMMUN_FAIL, and LASER_MOD_ERR.
l Link alarms: Such as ETH_LOS, ETH_AUTO_LINK_DOWN,
ETH_EFM_LOOPBACK, LOOP_ALM, PORTMODE_MISMATCH, and
LAG_DOWN.
l Radio link alarms: Such as MW_LOF, MW_LIM.
Step 5 Refer to 4.3.1 Browsing Current Alarms, check whether any alarms are generated in the failed
tunnel. If yes, take priority to clear them.
l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
----End
Related Information
None.
A.3.354 TUNNEL_APS_OUTAGE
Description
The TUNNEL_APS_OUTAGE alarm indicates that a tunnel APS protection group is
unavailable. This alarm is reported when both the working and protection tunnels of the
protection group fail.
773
Attribute
Major Service alarm
Parameters
None.
The services carried by the protection group are interrupted.
Possible Causes
Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
Procedure
Step 1 Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
1. Determine the boards and port IDs associated with the faulty tunnels. For details, see
Querying MPLS APS Status.
2. Handle tunnel faults by referring to 5.10 Troubleshooting MPLS Tunnels.
----End
Related Information
None.
A.3.355 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.
774
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 Cause 1: A few bit errors occur in the receive path related to the ATM port which reports
the UHCS alarm.
l Cause 2: The ATM physical-layer processing chip of the board is faulty.
Procedure
Step 1 Cause 1: A few bit errors occur in the receive path connected to the ATM port which reports the
UHCS alarm.
1. On the NMS, check whether the related receive path reports any alarms indicating excessive
bit errors, such as B1_SD, B2_SD, and B3_SD.
2. On the NMS, check whether the service is looped.
3. If yes, modify the service configuration to release the loop, and then check whether the
alarm is cleared.
Step 2 Cause 2: The ATM physical-layer processing chip of the board is faulty.
1. Perform a cold reset on the board that reports the UHCS alarm and check whether the alarm
is cleared. For details, see 8.6.1 Cold Reset.
2. 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.356 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.
775
E1 signals are unavailable.
Possible Causes
l Cause 1: The opposite equipment transmits the AIS signal.
l Cause 2: The receive unit of the tributary board on the local equipment is faulty.
Procedure
Step 1 Cause 1: The opposite equipment transmits the AIS signal.
1. Check whether the opposite equipment transmits the AIS signal.
If... Then...
The opposite equipment transmits the
AIS signal
Rectify the fault on the opposite equipment.
The opposite equipment does not
transmit the AIS signal
Go to Cause 2.
Step 2 Cause 2: The receive unit of the tributary board on the local equipment is faulty.
----End
Related Information
None.
A.3.357 USB_PROCESS_FAIL
Description
The USB_PROCESS_FAIL is an alarm indicating that data recovery from or data backup to a
USB disk fails.
Attribute
Parameters
Name Meaning
Parameter 1
l 0x01 indicates data recovery.
l 0x02 indicates data backup.
776
Name Meaning
Parameter 2
Indicates the file type.
l 0x01: indicates the software package.
l 0x02: indicates the patch package.
l 0x03: indicates the system parameter area.
l 0x04: indicates the script.
l 0x05: indicates the database.
l 0x06: indicates the license file.
When this alarm occurs, the database fails to be backed up or recovered. The system status
remains unchanged.
Possible Causes
l Cause 1: Recovering data from a USB disk fails.
l Cause 2: Backing up data to a USB disk fails.
Procedure
Step 1 Cause 1: Recovering data from a USB disk fails.
1. Verify that the USB flash drive can be identified by the NE.
2. Check whether the data in the USB flash drive is correct. If the data is incorrect, upload
the USB flash drive with correct data.
3. Verify that the operations for recovering data from the USB flash drive are correct.
Step 2 Cause 2: Backing up data to a USB disk fails.
1. Verify that the USB flash drive has enough capacity for data backup.
2. Check whether the USB flash drive is properly inserted. If the USB flash drive is not
properly inserted, re-insert the USB flash drive.
3. Replace the USB flash drive and re-back up data.
----End
Related Information
None.
A.3.358 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.
777
Attribute
Parameters
None.
When this alarm occurs, services are interrupted in the TU path of the board.
Possible Causes
l Cause 1: Hardware fault alarms occur on boards of an upstream NE.
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
Related Information
None.
A.3.359 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
778
Parameters
Name Meaning
Parameter 1 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.
l 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.
Possible Causes
l Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the
downstream.
l Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is
abnormal in the receive direction and therefore inserts AIS cells to the downstream.
l Cause 3: The board on the local NE is faulty.
Procedure
Step 1 Cause 1: An upstream NE reports the VC_LOC, and the AIS cells are inserted to the downstream.
1. On the NMS, check whether the VC_LOC occurs and the ATM connections that report the
VC_LOC have the same ID.
2. If the VC_LOC occurs, clear the VC_LOC and then the AIS insertion stops.
Step 2 Cause 2: On the local NE, the ATM port connected to a faulty upstream SDH path is abnormal
in the receive direction and therefore inserts AIS cells to the downstream.
779
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS or TU_LOP occurs in the upstream SDH path.
2. If yes, clear these alarms and then the AIS insertion stops.
Step 3 Cause 3: The board on the local NE is faulty.
1. Perform a cold reset on the alarmed board.
2. If the alarm persists, replace the alarmed board.
----End
Related 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 If an NE is set with the segment end point attribute, it can retrieve the alarms that are
generated at the segment and end.
l If an NE is set with the segment point attribute, it can retrieve the alarms that are generated
at a segment.
l If an NE is set with the end point attribute, it can retrieve the alarms that are generated at
an end.
l 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.360 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
780
Parameters
Name Meaning
l 0x01: forward
l 0x02: backward
l 0x01: segment
l 0x02: end
l 0x03: segment and end
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.
l In other cases, the service is interrupted when the alarm occurs.
l When this alarm occurs, the system automatically inserts AIS cells to the downstream.
Possible Causes
l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
l Cause 2: No bandwidth is available on the local NE.
abnormal in the receive direction.
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. Check whether the CC function on the local NE is activated.
2. If yes, Deactivate the CC function on the local NE. Then, check whether the alarm is cleared.
Step 2 Cause 2: No bandwidth is available on the local NE.
781
1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.
2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of
invalid data.
in the receive direction.
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, AU_AIS, AU_LOP,
TU_AIS or TU_LOP, occurs in an upstream SDH path.
2. If yes, clear these alarms and check whether the VC_LOC is cleared.
----End
Related Information
None.
A.3.361 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.
Attribute
Parameters
Name Meaning
l 0x01: forward
l 0x02: backward
782
Name Meaning
l 0x01: segment
l 0x02: end
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 Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.
Procedure
Step 1 Cause 1: The VC_AIS occurs in the receive direction of the downstream VC connection.
1. Check whether the VC_AIS occurs in the receive direction of the downstream VC
connection.
2. If yes, clear the VC_AIS and then check whether the VC_RDI is cleared.
----End
Related Information
End and Segment
Segment End Point
783
at a segment.
an end.
A.3.362 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
Name Meaning
Parameter 2, Parameter 3 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.
784
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. Determine the ID of the alarmed VCTRUNK path based on the alarm parameters.
2. Check whether the transmission routes of the paths bound to a VCTRUNK are the same.
If not, adjust their routes to the same.
----End
Related Information
None.
A.3.363 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
Name Meaning
The alarmed path is unavailable. If the LCAS function is disabled, the services in the path are
interrupted.
Possible Causes
l Cause 1: Bit errors occur on the line.
l Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
785
l Cause 3: The delays between virtual concatenations are over long.
Procedure
Step 1 Cause 1: Bit errors occur on the line.
1. Check whether any bit error alarm such as BIP_EXC and BIP_SD occurs.
If... Then...
A bit error alarm occurs Handle the alarm immediately.
No bit error alarm occurs Go to Cause 2.
Step 2 Cause 2: The MFI field in the K4 byte sent from the opposite site is incorrect.
1. Replace the board at the opposite site. For details, see 6.7 Replacing the Ethernet
Interface Board.
2. Replace the board and then check whether the alarm clears.
If... Then...
Step 3 Cause 3: The delays between virtual concatenations are over long.
1. Check whether the VCAT_LOA alarm is reported in this path.
If... Then...
The VCAT_LOA alarm is reported Handle the VCAT_LOA alarm immediately.
The VCAT_LOA alarm is not reported Go to Cause 2.
2. Check whether the VCAT_LOM_VC12 alarm clears after handling the VCAT_LOA
alarm.
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.364 VCAT_LOM_VC3
786
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
Name Meaning
The path that reports the alarm is unavailable. If the LCAS function is disabled, services are
interrupted.
Possible Causes
l Cause 1: Bit errors occur in the line.
l Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.
l Cause 3: The delays between virtual concatenations are too long.
Procedure
Step 1 Cause 1: Bit errors occur in the line.
1. Check for the bit error alarms such as BIP_EXC or BIP_SD.
If... Then...
The bit error alarms exist Handle the alarms immediately.
The bit error alarms do not exist Go to Cause 2.
Step 2 Cause 2: The MFI field in byte K4 sent from the opposite site is incorrect.
1. Follow instructions in 6.7 Replacing the Ethernet Interface Board to replace the board
at the opposite site.
787
2. Replace the alarmed board and then check whether the alarm clears.
If... Then...
Step 3 Cause 3: The delays between virtual concatenations are too long.
1. Check whether a VCAT_LOA alarm is reported in this path.
If... Then...
A VCAT_LOA alarm is reported in this
path
Handle the VCAT_LOA alarm
immediately.
No VCAT_LOA alarm is reported in this
path
Go to Cause 2.
2. Check whether the VCAT_LOM_VC3 alarm clears after handling the VCAT_LOA alarm.
If... Then...
The VCAT_LOM_VC3 alarm clears End the alarm handling.
The VCAT_LOM_VC3 alarm persists Follow instructions in 6.7 Replacing the
Ethernet Interface Board to replace the
alarmed board at the local site.
----End
Related Information
None.
A.3.365 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.
Attribute
Parameters
788
Name Meaning
The alarmed path is unavailable. If the LCAS function is disabled, services are interrupted.
Possible Causes
l Cause 1: Bit errors occur on certain links or certain links are faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.
Procedure
Step 1 Cause 1: Bit errors occur on certain links or certain links are faulty.
1. Check whether bit errors or line alarms occur. Focus on the bit error alarm BIP_EXC or
BIP_SD.
If... Then...
Bit errors or line alarms occur Clear these alarms.
No bit errors or line alarms occur Go to the next step.
Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
1. Replace the corresponding board at the opposite site.
If... Then...
replaced
replaced
Contact Huawei technical support engineers
for handling the alarm.
----End
Related Information
None.
A.3.366 VCAT_SQM_VC3
789
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
Name Meaning
The path that reports the alarm is unavailable. If the LCAS function is disabled, services are
interrupted.
Possible Causes
l Cause 1: Bit errors occur on a link or a link is faulty.
l Cause 2: The SQ number sent from the opposite site is incorrect.
Procedure
Step 1 Cause 1: Bit errors occur on a link or a link is faulty.
1. Check for bit error alarms or line alarms, especially BIP_EXC and BIP_SD.
If... Then...
Bit error alarms or line alarms occur Clear these alarms.
No bit error alarms or line alarms occur Go to Cause 2.
Step 2 Cause 2: The SQ number sent from the opposite site is incorrect.
1. Replace the related board at the opposite site.
790
If... Then...
The VCAT_SQM_VC3 alarm clears after the
board is replaced
The VCAT_SQM_VC3 alarm persists after
the board is replaced
Contact Huawei technical support
engineers.
----End
Related Information
None.
A.3.367 VERSION_NOTSUPPORT
Description
The VERSION_NOTSUPPORT alarm indicates that the system control board of the current
version does not support the function or data configured for an NE.
Attribute
791
Parameters
Name Meaning
Parameter 1
Indicates the function not supported by the current version.
l 1: The number of VLANs exceeds 1024 and a bridge is configured on a
Hybrid port.
l 2: The MEP point of a specified VLAN is configured in a port-exclusive
service.
l 3: The DS domain that trusts EXP-based packet priority is configured on a
Layer 2 port.
l 4: port mirroring
l 5: TST/LCK/CSF
l 6: IGMP
l 7: The ID of an assigned label is out of range.
l 0x08: Enabling LM at the ingress port of ingress MEP and the egress port of
egress MEP at the same time is not allowed in the same service direction
l 0x09: PW LM in Huawei mode (with generic associated channel label value
being 14) is not supported.
l 0x0A: The number of VLANs exceeds 1024, and the 802.1ad bridge is
configured.
The configured function is not available or the configured data does not take effect.
Possible Causes
Cause: The current version does not support the function or data.
Procedure
Step 1 Determine the function or data not supported by the current version according to alarm
parameters.
Step 2 Determine whether to use the current system control board.
If... Then...
The current system control board is
retained
Rectify service configurations (for example,
modify and delete parameters) to ensure that all
configured data is supported by the system
control board.
792
If... Then...
The current system control board is not
retained
Replace the system control board with a system
control board that supports the configured data.
For details, see Replacing a System Control,
Switching, and Timing Board.
----End
Related Information
None
A.3.368 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.
Attribute
Parameters
Name Meaning
Parameter 1
The ODU that is connected to the IF board that reports this alarm fails to work.
Possible Causes
l Cause 1: The output power is abnormal.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The output power is abnormal.
1. Check the power switch of the ODU.
793
If... Then...
The power switch is turned off Turn on the power switch.
The power switch is turned on Go to the next step.

2. Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section for
a short circuit.
NOTICE
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... Then...
A short circuit exists Replace the short-circuited component,
and then replace the alarmed IF board.
No short circuits exist Replace the alarmed IF board.

Step 2 Cause 2: The input power is abnormal.
1. Replace the alarmed IF board.
----End
Related Information
None.
A.3.369 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
Parameters
794
Name Meaning
l 0x01: forward
l 0x02: backward
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 alarm. In this case, the connection, though
not interrupted, is not loaded with any user service.
l 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 Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the
downstream.
abnormal in the receive direction and inserts AIS cells to the downstream.
Procedure
Step 1 Cause 1: An upstream NE reports the VP_LOC, and the AIS cells are inserted to the downstream.
1. On the NMS, check whether the VP_LOC occurs and the ATM connections that report the
VP_LOC have the same ID.
2. If the VP_LOC occurs, clear the VP_LOC and then the AIS insertion stops.
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.
2. If yes, clear these alarms and then the AIS insertion stops.
795
----End
Related Information
End and Segment
Segment End Point
at a segment.
an end.
A.3.370 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
796
Name Meaning
l 0x01: forward
l 0x02: backward
l 0x01: segment
l 0x02: end
l 0x03: segment and end
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.
l In other cases, the service is interrupted when the alarm occurs.
l When this alarm occurs, the system automatically inserts AIS cells to the downstream.
l The VP_LOC is suppressed when the VP_AIS occurs.
Possible Causes
l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on the
upstream NE.
l Cause 2: No bandwidth is available on the local NE.
abnormal in the receive direction.
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. Deactivate the CC function on the local NE.
Step 2 Cause 2: No bandwidth is available on the local NE.
1. On the NMS, check whether the bandwidth allocated to the tunnel is fully used.
2. If yes, increase the bandwidth or eliminate the sources that transmit a large amount of
invalid data.
797
in the receive direction.
1. Check whether any alarm, such as the R_LOS, R_LOF, MS_AIS, TU_AIS, TU_LOP,
AU_AIS or AU_LOP, occurs in an upstream SDH path.
2. If yes, clear these alarms.
2. Check whether the alarm is cleared. If not, replace the alarmed board.
----End
Related Information
None.
A.3.371 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
Name Meaning
l 0x01: forward
l 0x02: backward
798
Name Meaning
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 Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.
Procedure
l Cause 1: The VP_AIS occurs in the receive direction of the downstream VP connection.
1. Check whether the VP_AIS occurs in the receive direction of the downstream VP
connection.
2. If yes, clear the VP_AIS and then check whether the VP_RDI is cleared.
1. Perform a cold reset on the alarmed board. For details, see 8.6.1 Cold Reset.
2. If the alarm persists, replace the alarmed board. For details, see 6.6 Replacing the
----End
Related Information
End and Segment
Segment End Point
799
at a segment.
an end.
A.3.372 W_R_FAIL
Description
The W_R_FAIL is an alarm indicating a failure of reading or writing chip register.
Attribute
Parameters
Name Meaning
Parameter 1 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.
----End
Related Information
None.
800
A.3.373 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 Cause 2: The board of an incorrect type is installed.
Procedure
1. See Configuring the Logical Board to check whether the board type complies with the
planning requirement.
If... Then...
The board type does not meet the planning
requirement
Change the configuration data.
The board type meets the planning requirement Go to Cause 2.
Step 2 Cause 2: The board of an incorrect type is installed.
1. Replace the board of an incorrect type.
----End
Related Information
None.
A.3.374 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
801
Attribute
Parameters
None.
Bit errors may occur in the service at the port, and the service may even be interrupted.
Possible Causes
l Cause 2: The radio link is faulty.
l Cause 3: The XPIC cable is faulty.
l Cause 4: The IF board or ODU is faulty.
Procedure
1. Check whether the XPIC function needs to be enabled. If 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... Then...
The cable is improperly connected Connect the XPIC cable properly.
The cable is properly connected Go to the next step.

2. Test the make and break of the XPIC cable by using the multimeter. If the XPIC cable 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.
802
If... Then...
replaced
replaced

2. Replace the ODU that is connected to the paired XPIC IF board.
If... Then...
The alarm is cleared after the ODU is
replaced
The alarm persists after the ODU is
replaced
Replace the alarmed XPIC IF board.

----End
Related Information
None.
803
B 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.
B.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.
B.2 Performance Events (by Logical Board)
This part lists all the performance events that are reported by each board.
B.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.
Maintenance Guide B Performance Event Reference
804
B.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.
B.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 B-1 Pointer Justification Performance Events
Event Name Description
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.
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.

Table B-2 Regenerator Section Error Performance Events
RSBBE Indicates the regenerator section background
block error.
RSES Indicates the regenerator section errored
second.
RSSES Indicates the regenerator section severely
errored second.
RSUAS Indicates the regenerator section unavailable
second.
805
RSCSES Indicates the regenerator section consecutive
severely errored second.
RSOFS Indicates the regenerator section out-of-
frame second.
RSOOF Indicates the count of regenerator section out-
of-frame events.

NOTE
In the case of PDH radio, regenerator section bit error performance events also exist and they are detected
according to the overheads used for detecting frame alignment and bit errors in the PDH microwave frames.
Table B-3 Multiplex Section Error Performance Events
MSBBE Indicates the multiplex section background
block error.
MSES Indicates the multiplex section errored
second.
MSSES Indicates the multiplex section severely
errored second.
MSCSES Indicates the multiplex section consecutive
MSUAS Indicates the multiplex section unavailable
second.
MSFEBBE Indicates the multiplex section far end
background block error.
MSFEES Indicates the multiplex section far end errored
second.
MSFESES Indicates the multiplex section far end
MSFECSES Indicates the multiplex section far end
consecutive severely errored second.
MSFEUAS Indicates the multiplex section far end
unavailable second.

806
Table B-4 Higher Order Path Error Performance Events
HPBBE Indicates the higher order path background
block error.
HPES Indicates the higher order path errored
second.
HPSES Indicates the higher order path severely
errored second.
HPCSES Indicates the higher order path consecutive
HPUAS Indicates the higher order path unavailable
second.
HPFEBBE Indicates the higher order path far end
HPFEES Indicates the higher order path far end errored
second.
HPFESES Indicates the higher order path far end
HPFECSES Indicates the higher order path far end
HPFEUAS Indicates the higher order path far end
unavailable second.

Table B-5 Lower Order Path Error Performance Events
LPBBE Indicates the lower order path background
block error.
LPES Indicates the lower order path errored second.
LPSES Indicates the lower order path severely
errored second.
LPCSES Indicates the lower order path consecutive
LPUAS Indicates the lower order path unavailable
second.
LPFEBBE Indicates the lower order path far end
807
LPFEES Indicates the lower order path far end errored
second.
LPFESES Indicates the lower order path far end
LPFECSES Indicates the lower order path far end
LPFEUAS Indicates the lower order far end unavailable
second.

Table B-6 E1 Line Side Code Violation Performance Events
E1_LCV_SDH Indicates the count of E1 line side code
violations.
E1_LLOSS_SDH Indicates the E1 line side loss-of-signal
second.
E1_LES_SDH Indicates the E1 line side code violation
errored second.
E1_LSES_SDH Indicates the E1 line side code violation

Table B-7 E1 Error Performance Events
E1_BBE Indicates the E1 background block error.
E1_ES Indicates the E1 errored second.
E1_SES Indicates the E1 severely errored second.
E1_CSES Indicates the E1 consecutive severely errored
second.
E1_UAS Indicates the E1 unavailable second.

808
Table B-8 PW carried ATM, CSE and L2VPN Services Performance Events
MPLS_PW_LS Indicates the packet loss seconds of PW
carried services.
MPLS_PW_SLS Indicates the severe packet loss seconds of
PW carried services.
MPLS_PW_CSLS Indicates the consecutive severe packet loss
seconds of PW carried services.
MPLS_PW_UAS Indicates the unavailable seconds of PW
carried services.

NOTE
Only the CSHU, CSHUA, SL92CSH board supports PW.
B.1.2 Radio Performance Events
The radio performance events are performance events of the radio link bit errors, ATPC, AM,
and power.
Table B-9 Radio power performance events
TSL_MAX Maximum value of radio transmit signal level
TSL_MIN Minimum value of radio transmit signal level
TSL_CUR Current value of radio transmit signal level
TSL_AVG Average value of radio transmit signal level
RSL_MAX Maximum value of radio receive signal level
RSL_MIN Minimum value of radio receive signal level
RSL_CUR Current value of radio receive signal level
RSL_AVG Average value of radio receive signal level
TLHTT The duration when the ODU at the local end
has a transit power higher than the upper
threshold
TLLTT The duration when the ODU at the local end
has a transit power higher than the lower
threshold
809
RLHTT The duration when the ODU at the local end
has a receive power lower than the upper
threshold
RLLTT The duration when the ODU at the local end
has a receive power lower than the lower
threshold

Table B-10 FEC performance events
FEC_BEF_COR_ER FEC bit error rate before correction
FEC_UNCOR_BLOCK_CNT FEC uncorrected block count
FEC_COR_BYTE_CNT The number of bytes that are corrected
through the FEC

Table B-11 Radio link error performance events
IF_BBE Radio link background block errors
IF_ES Radio link errored seconds
IF_SES Radio link severely errored seconds
IF_UAS Radio link unavailable second
IF_CSES Radio link consecutive severely errored
seconds
IF_BER Radio link bit error rate

Table B-12 ATPC performance events
ATPC_P_ADJUST Positive ATPC adjustment
ATPC_N_ADJUST Negative ATPC adjustment

810
Table B-13 AM performance events
QPSKWS Working time of the QPSK mode
QAMWS16 Working time of the 16QAM mode
QPSK_S_WS Working time of the QPSKSTRONG mode
QAM_S_WS16 Working time of the 16QAMSTRONG mode
QAM_L_WS512 Working time of the 512QAMLIGHT mode
QAM_L_WS1024 Working time of the 1024QAMLIGHT mode
AMDOWNCNT Count of the downshift of the AM scheme
AMUPCNT Count of the upshift of the AM scheme

Table B-14 XPIC performance events
XPIC_XPD_VALUE XPIC XPD value

Table B-15 IF 1+1 protection group error performance events
PG_IF_BBE IF 1+1 protection group background block
errors
PG_IF_ES IF 1+1 protection group errored seconds
PG_IF_SES IF 1+1 protection group severely errored
seconds
PG_IF_UAS IF 1+1 protection group unavailable second
PG_IF_CSES IF 1+1 protection group consecutive severely
errored seconds

811
Table B-16 IF port error performance events
IF_SNR_MAX Maximum signal to noise ratio
IF_SNR_MIN Minimum signal to noise ratio
IF_SNR_AVG Average signal to noise ratio

B.1.3 MPLS Tunnel/PW Performance Events
This section lists MPLS tunnel/PW performance events.
Table B-17 MPLS tunnel/PW performance events
MPLS_PW_LS PW packet loss seconds
MPLS_PW_SLS PW severe packet loss seconds
MPLS_PW_CSLS PW consecutive severe packet loss seconds
MPLS_PW_UAS PW unavailable seconds
MPLS_PW_LS_N PW packet loss seconds at the near end
MPLS_PW_SLS_N PW severe packet loss seconds at the near end
MPLS_PW_CSLS_N PW consecutive severe packet loss seconds at
the near end
MPLS_PW_UAS_N PW unavailable seconds at the near end
MPLS_TUNNEL_LS Tunnel packet loss seconds
MPLS_TUNNEL_SLS Tunnel severe packet loss seconds
MPLS_TUNNEL_CSLS Tunnel consecutive severe packet loss
seconds
MPLS_TUNNEL_UAS Tunnel unavailable seconds
MPLS_TUNNEL_LS_N Tunnel packet loss seconds at the near end
MPLS_TUNNEL_SLS_N Tunnel severe packet loss seconds at the near
end
MPLS_TUNNEL_CSLS_N Tunnel consecutive severe packet loss
seconds at the near end
MPLS_TUNNEL_UAS_N Tunnel unavailable seconds at the near end

812
NOTE
The CSHU, CSHUA, and SL92CSH support MPLS tunnel/PW performance events.
The supports PW performance events.
B.1.4 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 B-18 Optical power performance events
TPLMAX Maximum value of transmit optical power
TPLMIN Minimum value of transmit optical power
TPLCUR Current value of transmit optical power
RPLMAX Maximum value of receive optical power
RPLMIN Minimum value of receive optical power
RPLCUR Current value of receive optical power

Table B-19 Board temperature performance events
BDTEMPMAX Maximum value of board temperature
BDTEMPMIN Minimum value of board temperature
BDTEMPCUR Current value of board temperature

Table B-20 Laser temperature performance events
OSPITMPMAX Maximum temperature of a laser core
OSPITMPMIN Minimum temperature of a laser core
OSPITMPCUR Current temperature of a laser core

813
Table B-21 Transmitted bias current performance events
Performance Event Name Description
TLBMAX Maximum transmitted bias current of the
laser
TLBMIN Minimum transmitted bias current of the laser
TLBCUR Current transmitted bias current of the laser

Table B-22 Clock performance events
MAXFREQDEV Maximum frequency deviation
MINFREQDEV Minimum frequency deviation
AVGFREQDEV Average frequency deviation
CURPOSITIVEPDV Current positive PDV
MAXPOSITIVEDELAY Maximum positive delay
MINPOSITIVEDELAY Minimum positive delay
AVGPOSITIVEDELAY Average positive delay
MAXPHASEOFFSET Maximum phase offset
MINPHASEOFFSET Minimum phase offset
AVGPHASEOFFSET Average phase offset
MAXMEANPATHDELAY Maximum path delay
MINMEANPATHDELAY Minimum path delay
AVGMEANPATHDELAY Average path delay

B.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
814
Table B-23 Mappings between the physical boards and logical boards
Physical
Board
Logical Board
CST CST in the same slot
CSH CSH in the same slot
CSHU CSHU in the same slot
CSHUA CSHUA in the same slot
AUX AUX in the same slot
IF1 IF1 in the same slot
IFU2 IFU2 in the same slot
IFX2 IFX2 in the same slot
ISU2 ISU2 in the same slot
ISX2 ISX2 in the same slot
ISV3 ISV3 in the same slot
SL1D SL1D in the same slot
SL1DA SL1DA in the same slot
EM6T EM6T in the same slot
EM6TA EM6TA in the same slot
EM6F EM6F in the same slot
EM6FA EM6FA in the same slot
EG4 EG4 in the same slot
EG4P EG4P in the same slot
EFP8 EFP8 in the same slot
EMS6 EMS6 in the same slot
SP3S SP3S in the same slot
SP3D SP3D in the same slot
ML1 ML1 in the same slot
MD1 MD1 in the same slot
CQ1 CQ1 in the same slot
PIU PIU in the same slot
FAN FAN in the same slot
815
Physical
Board
Logical Board
ODU ODU in the slot whose number is 20 plus the slot number for the IF board
that is connected to the ODU

B.2.1 CQ1
The CQ1 board reports the board temperature performance events, SDH performance events
and Laser Performance Events.
Board temperature performance events

SDH Performance Events
Table B-25 Pointer Justification Performance Events
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.
TUPJCHIGH Indicates the count of positive TU pointer
justifications.
TUPJCLOW Indicates the count of negative TU pointer
justifications.

816
Table B-26 Regenerator Section Error Performance Events
RSBBE Indicates the regenerator section background
block error.
RSES Indicates the regenerator section errored
second.
RSSES Indicates the regenerator section severely
errored second.
RSUAS Indicates the regenerator section unavailable
second.
RSCSES Indicates the regenerator section consecutive

Table B-27 Multiplex section error performance events
MSBBE Multiplex section block of background error
MSES Multiplex section errored second
MSSES Multiplex section severely errored second
MSCSES Multiplex section consecutive severely
errored second
MSUAS Multiplex section unavailable second
MSFEBBE Multiplex section far end block of
background error
MSFEES Multiplex section far end errored second
MSFESES Multiplex section far end severely errored
second
MSFECSES Multiplex section far end consecutive
severely errored second
MSFEUAS Multiplex section far end unavailable second

Table B-28 Higher order path error performance events
HPBBE Higher order path background errored block
817
HPES Higher order path errored second
HPSES Higher order path severely errored second
HPCSES Higher order path consecutive severely
errored second
HPUAS Higher order path unavailable second
HPFEBBE Higher order path far end background errored
block
HPFEES Higher order path far end errored second
HPFESES Higher order path far end severely errored
second
HPFECSES Higher order path far end consecutive
HPFEUAS Higher order path far end unavailable second

Table B-29 Lower order path error performance events
LPBBE Lower order path block of background error
LPES Lower order path errored second
LPSES Lower order path severely errored second
LPCSES Lower order path continuous severe bit error
second
LPUAS Lower order path unavailable second
LPFEBBE Lower order path far end block of background
error
LPFEES Lower order path far end errored second
LPFESES Lower order path far end severely errored
second
LPFECSES Lower order path far end consecutive
LPFEUAS Lower order far end unavailable second

818
Laser Performance Events
Table B-30 Transmitted bias current performance events
Performance Event Name Description
TLBMAX Maximum transmitted bias current of the
laser
TLBMIN Minimum transmitted bias current of the laser
TLBCUR Current transmitted bias current of the laser



B.2.2 CST/CSH/CSHU/CSHUA
The CST/CSH/CSHU/CSHUA board reports five types of performance events: board
temperature performance events, IF 1+1 protection group error performance events, clock
performance events, PW performance events, and MPLS performance events.
819

Table B-34 IF 1+1 protection group error performance events
PG_IF_BBE IF 1+1 protection group background block
errors
PG_IF_ES IF 1+1 protection group errored seconds
PG_IF_SES IF 1+1 protection group severely errored
seconds
PG_IF_UAS IF 1+1 protection group unavailable second
PG_IF_CSES IF 1+1 protection group consecutive severely
errored seconds

Table B-35 Clock performance events (only CSH/CSHU/CSHUA supports)
MAXFREQDEV Maximum frequency deviation
MINFREQDEV Minimum frequency deviation
AVGFREQDEV Average frequency deviation
CURPOSITIVEPDV Current positive PDV
MAXPOSITIVEDELAY Maximum positive delay
MINPOSITIVEDELAY Minimum positive delay
AVGPOSITIVEDELAY Average positive delay
MAXPHASEOFFSET Maximum phase offset
MINPHASEOFFSET Minimum phase offset
AVGPHASEOFFSET Average phase offset
MAXMEANPATHDELAY Maximum path delay
MINMEANPATHDELAY Minimum path delay
820
AVGMEANPATHDELAY Average path delay

Table B-36 PW performance events (only CSH/CSHU/CSHUA supports)
MPLS_PW_LS PW packet loss seconds
MPLS_PW_LS_N PW packet loss seconds at the near end
MPLS_PW_SLS PW severe packet loss seconds
MPLS_PW_SLS_N PW severe packet loss seconds at the near end
MPLS_PW_CSLS PW consecutive severe packet loss seconds
MPLS_PW_CSLS_N PW consecutive severe packet loss seconds at
the near end
MPLS_PW_UAS PW unavailable seconds
MPLS_PW_UAS_N PW unavailable seconds at the near end

Table B-37 MPLS performance events (only CSHU/CSHUA supports)
MPLS_TUNNEL_LS Tunnel packet loss seconds
MPLS_TUNNEL_LS_N Tunnel severe packet loss seconds
MPLS_TUNNEL_SLS Tunnel consecutive severe packet loss
seconds
MPLS_TUNNEL_SLS_N Tunnel unavailable seconds
MPLS_TUNNEL_CSLS Tunnel packet loss seconds at the near end
MPLS_TUNNEL_CSLS_N Tunnel severe packet loss seconds at the near
end
MPLS_TUNNEL_UAS Tunnel consecutive severe packet loss
seconds at the near end
MPLS_TUNNEL_UAS_N Tunnel unavailable seconds at the near end

821
B.2.3 EG4/EG4P
The EG4/EG4P board reports optical power performance events and board temperature
performance events.


B.2.4 EM6T
The EM6T board reports only the board temperature performance events.

B.2.5 EM6TA
The EM6TA board reports only the board temperature performance events.
822

B.2.6 EM6F
The EM6F board reports optical power performance events and board temperature performance
events.


B.2.7 EM6FA
The EM6FA board reports optical power performance events and board temperature
performance events.
823


B.2.8 EFP8
The EFP8 board reports the temperature and PDH performance events.

824
second
error
second

B.2.9 EMS6
The EMS6 board reports the SDH performance events, board temperature performance events,
laser temperature performance events, and optical power performance events.
second
error
second

825
errored second
block
second



826

B.2.10 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 B-53 Pointer justification performance events
AUPJCHIGH Count of positive AU pointer justification
AUPJCLOW Count of negative AU pointer justification
AUPJCNEW Count of new AU pointer justifications

Table B-54 Regenerator section error performance events
RSBBE Regenerator section block of background
error
RSES Regenerator section errored second
RSSES Regenerator section severely errored second
RSUAS Regenerator section unavailable second
RSCSES Regenerator section consecutive severely
errored second
RSOFS Regenerator section out-of-frame second
RSOOF Regenerator section out of frame

827
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.
errored second
background error
second

HPBBE Higher order path background block error
errored second
HPFEBBE Higher order path far end background block
error
second
828

Radio Performance Events
FEC_COR_BYTE_CNT Frame count incorrect by FEC

IF_MSE_MAX Maximum MSE value
IF_MSE_MIN Minimum MSE value
IF_MSE_CUR Current MSE value
IF_MSE_AVG Average MSE value

Other Performance Events

829
B.2.11 IFU2/ISU2
The IFU2/ISU2 board reports three types of performance events: SDH performance events, PDH
performance events, radio performance events, and board temperature performance events.
SDH Performance Events (Only reported by ISU2)

error
errored second

errored second
830
background error
second

errored second
block
second

PDH Performance Events
831
second
error
second


seconds

832



833
B.2.12 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)

error
errored second

errored second
834
background error
second

errored second
block
second

835
second
error
second


seconds

836



837

B.2.13 ISV3
The ISV3 board reports four types of performance events: SDH performance events, PDH
performance events, microwave performance events, and board temperature performance
events.
error
errored second

errored second
background error
838
second

errored second
block
second

839
second
error
second


seconds

840
QPSK_S_WS Working time of the QPSK strong mode
QAM_S_WS16 Working time of the 16QAM strong mode
QAM_L_WS512 Working time of the 512QAM light mode
QAM_L_WS1024 Working time of the 1024QAM light mode


841


B.2.14 ML1/MD1
The ML1/MD1 board reports E1 performance events, PW performance events and board
temperature performance events.
Table B-91 E1 Performance Event List
E1_LCV_SDH Indicates the count of E1 line side code
violations.
E1_LLOSS_SDH Indicates the E1 line side loss-of-signal
second.
E1_LES_SDH Indicates the E1 line side code violation
errored second.
E1_LSES_SDH Indicates the E1 line side code violation

Table B-92 PW carried services performance events
MPLS_PW_LS Indicates the packet loss seconds of PW
carried services
MPLS_PW_SLS Indicates the severe packet loss seconds of
PW carried services
MPLS_PW_CSLS Indicates the consecutive severe packet loss
seconds of PW carried services
MPLS_PW_UAS Indicates the unavailable seconds of PW
carried services
842

Table B-93 Board Temperature Performance Events
BDTEMPMAX Indicates the maximum board
temperature.
BDTEMPMIN Indicates the minimum board
temperature.
BDTEMPCUR Indicates the current board temperature.

B.2.15 ODU
The ODU reports radio performance events and board temperature performance events.
Table B-94 Radio power performance events
TSL_MAX Maximum value of radio transmit signal level
TSL_MIN Minimum value of radio transmit signal level
TSL_CUR Current value of radio transmit signal level
TSL_AVG Average value of radio transmit signal level
RSL_MAX Maximum value of radio receive signal level
RSL_MIN Minimum value of radio receive signal level
RSL_CUR Current value of radio receive signal level
RSL_AVG Average value of radio receive signal level
TLHTT The duration when the ODU at the local end
has a transit power higher than the upper
threshold
TLLTT The duration when the ODU at the local end
has a transit power higher than the lower
threshold
RLHTT The duration when the ODU at the local end
has a receive power lower than the upper
threshold
RLLTT The duration when the ODU at the local end
has a receive power lower than the lower
threshold
843
ODU_SSV_TH The duration (seconds) when the ODU
receive power is lower than sensitivity

Table B-95 ATPC performance events
ATPC_P_ADJUST Positive ATPC adjustment
ATPC_N_ADJUST Negative ATPC adjustment

BDTEMPMAX Indicates the maximum board
temperature.
BDTEMPMIN Indicates the minimum board
temperature.
BDTEMPCUR Indicates the current board temperature.

B.2.16 SL1D/SL1DA
The SL1D/SL1DA board reports two types of performance events: SDH performance events,
and optical power performance events.

844
error
errored second

errored second
background error
second

845
errored second
block
second


B.2.17 SP3S/SP3D
The SP3S/SP3D board reports only the PDH performance events.
TUPJCHIGH Count of positive TU pointer justifications
846
TUPJCLOW Count of negative TU pointer justifications
TUPJCNEW Count of new TU pointer justifications

second
error
second

Table B-104 E1 Error Performance Events
E1_BBE Indicates the E1 background block error.
E1_ES Indicates the E1 errored second.
E1_SES Indicates the E1 severely errored second.
E1_CSES Indicates the E1 consecutive severely errored
second.
E1_UAS Indicates the E1 unavailable second.

847
B.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.
B.3.1 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 Description
Performance event cell ATPCPADJUST (ATPC_P_ADJUST) and
ATPCNADJUST (ATPC_N_ADJUST)
Unit 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.
B.3.2 AMDOWNCNT and AMUPCNT
Description
l AMDOWNCNT indicates the count of the AM downshifts on a board in the current
performance statistics period.
848
l AMUPCNT indicates the count of the AM upshifts on a board in the current performance
statistics period.
Attribute
Performance event cell ACMDCNT(AMDOWNCNT) and
ACMUCNT(AMUPCNT)
Unit times

Impact on System
l When the value of the performance event is larger, more AM scheme are made.
l When the factors that affect a communication link, such as sudden change of the weather,
do not exist, and when the AM scheme count is very large, the communication link 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.
B.3.3 AUPJCHIGH, AUPJCLOW, and AUPJCNEW
Description
l AUPJCHIGH indicates the count of positive AU pointer justifications.
l AUPJCLOW indicates the count of negative AU pointer justifications.
l AUPJCNEW indicates the count of new AU pointer justifications.
Attribute
Performance event cell PPJE (AUPJCHIGH)
NPJE (AUPJCLOW)
NDF (AUPJCNEW)
849
Unit Block

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 Default 15-Minute
Threshold
Default 24-Hour
Threshold
AUPJCHIGH 1500 30000
AUPJCLOW 1500 30000
AUPJCNEW 1500 30000

Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
B.3.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR
Description
l BDTEMPMAX indicates the maximum temperature of a board.
l BDTEMPMIN indicates the minimum temperature of a board.
l BDTEMPCUR indicates the current temperature of a board.
Attribute
Performance event cell XCS_TEMP
850
Unit 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.
B.3.5 CURPOSITIVEPDV and CURNEGATIVEPDV
Description
l CURPOSITIVEPDV indicates the current positive packet delay variation (PDV).
l CURNEGATIVEPDV indicates the current negative PDV.
Attribute
Performance event cell 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.
B.3.6 E1_LCV_SDH, E1_LLOSS_SDH, E1_LES_SDH, and
E1_LSES_SDH
Description
l The E1_LCV_SDH is a performance event indicating the E1 line side code violation count.
851
l The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-signal
seconds.
l The E1_LES_SDH is a performance event indicating the E1 line side code violation errored
second.
ES refers to a second in which one or more errored blocks are detected.
l The E1_LSES_SDH is a performance event indicating the E1 line side code violation
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
Performance event cell LCV_BPVCNT
Unit 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.
852
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
B.3.7 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 E1_ES indicates the E1 errored second.
Errored second (ES) refers to a second in which one or more errored blocks are detected.
l E1_SES indicates the E1 severely errored second.
Severely errored second (SES) refers to a second in which 30% or more than 30% 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
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
Performance event cell E1CRC_ERR_CNT
Unit 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).
853
Related Alarms
None.
Threshold
Default 24-Hour
Threshold
E1_BBE 1500 15000
E1_ES 50 100
E1_SES 20 50
E1_UAS 20 50
E1_CSES 4 (number of consecutive SESs)

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
B.3.8 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT and
FEC_UNCOR_BLOCK_CNT
Description
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.
l FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.
This event indicates the impact of the FEC.
l FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected
through the FEC.
This event indicates the number of blocks that cannot be corrected through the FEC.
854
Attribute
Performance event cell FECBEFCORER (FEC_BEF_COR_ER)
FECCORBYTECNT
(FEC_COR_BYTE_CNT)
FECUNCORBLOCKCNT
(FEC_UNCOR_BLOCK_CNT)
Unit None (FEC_BEF_COR_ER)
None (FEC_COR_BYTE_CNT)
Block (FEC_UNCOR_BLOCK_CNT)

Impact on System
If the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after 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.
B.3.9 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 HPES indicates the higher order path errored second.
l HPSES indicates the higher order path severely errored second.
SES refers to a second in which 30% or more than 30% errored blocks exist or at least 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
l HPCSES indicates the higher order path consecutive severely errored second.
CSES refers to a second in which the SES occurs continuously for less than 10 seconds.
l HPUAS indicates the higher order path unavailable second.
855
Attribute
Performance event cell B3CNT
Unit Block (HPBBE)
Second (HPES, HPSES, HPCSES, and
HPUAS)

Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10
-3
and 10
-6
Related Alarms
When the HPBBE, HPES, HPSES, HPCSES, or HPUAS performance event crosses the preset
threshold, the HP_CROSSTR alarm is reported.
Threshold
Default 24-Hour
Threshold
HPBBE 1500 15000
HPES 50 100
HPSES 20 50
HPUAS 20 50
HPCSES 4 (number of consecutive SESs)

Possible Causes
The system detects higher order path bit errors through the B3 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.
----End
B.3.10 HPFEBBE, HPFEES, HPFESES, HPFECSES, and HPFEUAS
Description
l HPFEBBE indicates the higher order path far end background block error.
856
Far end background block error (FEBBE) indicates that the BBE occurs at the opposite
end.
l HPFEES indicates the higher order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
l HPFESES indicates the higher order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
l HPFECSES indicates the higher order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite end.
l HPFEUAS indicates the higher order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Performance event cell PFEBE
Unit Block (HPFEBBE)
Second (HPFEES, HPFESES, HPFECSES,
and HPFEUAS)

Impact on System
-3
and 10
-6
Related Alarms
The HP_REI alarm is reported at the local end.
Possible Causes
The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End
B.3.11 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS
Description
l IF_BBE indicates the radio link background block error.
857
l IF_ES indicates the radio link errored second.
l IF_SES indicates the radio link severely errored second.
higher than 10
-2
l IF_CSES indicates the radio link consecutively severely errored second.
l IF_UAS indicates the radio link unavailable second.
l IF_BER indicates the radio link bit error rate.
Attribute
Performance event cell 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
-3
and 10
-6
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
----End
858
B.3.12 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG
Description
l IF_SNR_MAX indicates the maximum signal to noise ratio.
l IF_SNR_MIN indicates the minimum signal to noise ratio.
l IF_SNR_AVG indicates the average signal to noise ratio.
Attribute
Performance event cell IF_SNR(IF_SNR_MAX, IF_SNR_MIN)
IF_SNR_AVG_15M, 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.
B.3.13 LPBBE, LPES, LPSES, LPCSES, and LPUAS
Description
l LPBBE indicates the lower order path background block error.
l LPES indicates the lower order path errored second.
l LPSES indicates the lower order path severely errored second.
higher than 10
-2
l LPCSES indicates the lower order path consecutive severely errored second.
l LPUAS indicates the lower order path unavailable second.
859
Attribute
Performance event cell LPBIP2CNT
Unit Block (LPBBE)
Second (LPES, LPSES, LPCSES, and
LPUAS)

Impact on System
-3
and 10
-6
Related Alarms
When the LPBBE, LPES, LPSES, LPCSES, or LPUAS performance event crosses the preset
threshold, the LP_CROSSTR alarm is reported.
Threshold
Default 24-Hour
Threshold
LPBBE 1500 15000
LPES 50 100
LPSES 20 50
LPUAS 20 50
LPCSES 4 (number of consecutive SESs)

Possible Causes
The system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interface
board or Hybrid IF board).
Procedure
----End
860
B.3.14 LPFEBBE, LPFEES, LPFESES, LPFECSES, and LPFEUAS
Description
l LPFEBBE indicates the lower order path far end background block error.
FEBBE indicates that the BBE occurs at the opposite end.
l LPFEES indicates the lower order path far end errored second.
FEES indicates that the ES occurs at the opposite end.
l LPFESES indicates the lower order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
l LPFECSES indicates the lower order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite end.
l LPFEUAS indicates the lower order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Performance event cell LPFEBE
Unit Block (LPFEBBE)
Second (LPFEES, LPFESES, LPFECSES,
and LPFEUAS)

Impact on System
-3
and 10
-6
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
----End
861
B.3.15 MAXFREQDEV, MINFREQDEV, and AVGFREQDEV
Description
l MAXFREQDEV indicates the maximum frequency offset.
l MINFREQDEV indicates the minimum frequency offset.
l AVGFREQDEV indicates the average frequency offset.
Attribute
Performance event cell PTP_DA
Unit 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.
B.3.16 MAXMEANPATHDELAY, MINMEANPATHDELAY, and
AVGMEANPATHDELAY
Description
l MAXMEANPATHDELAY indicates the maximum path delay between the master and
slave clocks.
l MINMEANPATHDELAY indicates the minimum path delay between the master and slave
clocks.
l AVGMEANPATHDELAY indicates the average path delay between the master and slave
clocks.
Attribute
Performance event cell MAXMEANPATHDELAY
(MAXMEANPATHDELAY)
MINMEANPATHDELAY
(MINMEANPATHDELAY)
AVGMEANPATHDELAY
(AVGMEANPATHDELAY)
862
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.
B.3.17 MAXPHASEOFFSET, MINPHASEOFFSET, and
AVGPHASEOFFSET
Description
l MAXPHASEOFFSET indicates the maximum time deviation between the master and slave
clocks.
l MINPHASEOFFSET indicates the minimum time deviation between the master and slave
clocks.
l AVGPHASEOFFSET indicates the average time deviation between the master and slave
clocks.
Attribute
Performance event cell MAXPHASEOFFSET
(MAXPHASEOFFSET),
MINPHASEOFFSET
(MINPHASEOFFSET),
AVGPHASEOFFSET
(AVGPHASEOFFSET)
Unit ns

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.
863
Related Alarms
When the time deviation between the master and slave clocks is greater than 100 ns, the
TIME_LOCK_FAIL alarm is reported.
B.3.18 MAXPOSITIVEDELAY, MINPOSITIVEDELAY, and
AVGPOSITIVEDELAY
Description
l MAXPOSITIVEDELAY indicates the maximum positive delay between the master and
slave clocks.
l MINPOSITIVEDELAY indicates the minimum positive delay between the master and
slave clocks.
l AVGPOSITIVEDELAY indicates the average positive delay between the master and slave
clocks.
Attribute
Performance event cell PTP_PTD
Unit 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.
B.3.19 MPLS_PW_LS, MPLS_PW_SLS, MPLS_PW_CSLS, and
MPLS_PW_UAS
Description
l MPLS_PW_LS indicates the packet loss seconds of the PW service.
l MPLS_PW_SLS indicates the severe packet loss seconds of the PW service.
l MPLS_PW_CSLS indicates the consecutive severe packet loss seconds of the PW service.
l MPLS_PW_UAS indicates the unavailable seconds of the PW service.
864
Attribute
Performance event cell MPLS_PW_FL
Unit 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.
B.3.20 MSBBE, MSES, MSSES, MSCSES, and MSUAS
Description
l MSBBE indicates the multiplex section background block error.
l MSES indicates the multiplex section errored second.
l MSSES indicates the multiplex section severely errored second.
higher than 10
-2
l MSCSES indicates the multiplex section consecutive severely errored second.
l MSUAS indicates the multiplex section unavailable second.
Attribute
865
Unit Block (MSBBE)
Second (MSES, MSSES, MSCSES, and
MSUAS)

Impact on System
-3
and 10
-6
Related Alarms
When the MSBBE, MSES, MSSES, MSCSES, or MSUAS performance event crosses the preset
threshold, the MS_CROSSTR alarm is reported.
Threshold
Default 24-Hour
Threshold
MSBBE 1500 15000
MSES 50 100
MSES 20 50
MSUAS 20 50
MSCSES 4 (number of consecutive SESs)

Possible Causes
The system detects multiplex section bit errors through the B2 byte.
Procedure
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
B.3.21 MSFEBBE, MSFEES, MSFESES, MSFECSES, and MSFEUAS
Description
l MSFEBBE indicates the multiplex section far end background block error.
866
Far end background block error (FEBBE) indicates that the BBE occurs at the opposite
end.
l MSFEES indicates the multiplex section far end errored second.
Far end errored second (FEES) indicates that the ES occurs at the opposite end.
l MSFESES indicates the multiplex section far end severely errored second.
Far end severely errored second (FESES) indicates that the SES occurs at the opposite end.
l MSFECSES indicates the multiplex section far end consecutive severely errored second.
Far end consecutive severely errored second (FECSES) indicates that the CSES occurs 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
Performance event cell LFEBE
Unit Block (MSFEBBE)
Second (MSFEES, MSFESES, MSFECSES,
and MSFEUAS)

-3
and 10
-6
Related Alarms
The MS_REI alarm is reported at the local end.
Possible Causes
The system detects multiplex section far end bit errors through the M1 byte.
Procedure
----End
B.3.22 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR
Description
l OSPITMPMAX indicates the maximum temperature of a laser core.
l OSPITMPMIN indicates the minimum temperature of a laser core.
867
l OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Performance event cell TMP
Unit C

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.
B.3.23 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.
the unavailable and severely errored seconds.
l PG_IF_ES indicates the protection group errored second.
l PG_IF_SES indicates the protection group severely errored second.
-2
l PG_IF_CSES indicates the protection group consecutive severely errored second.
l PG_IF_UAS indicates the protection group unavailable second.
868
Attribute
Performance event cell IF_BIP8
Unit Block (PG_IF_BBE)
Second (PG_IF_ES, PG_IF_SES,
PG_IF_CSES, and PG_IF_UAS)

Impact on System
Excessive bit errors interrupt the service (the BER should be less than
-3
and 10
-6
Related Alarms
None.
Threshold
Default 24-Hour
Threshold
PG_IF_BBE 1500 15000
PG_IF_ES 50 100
PG_IF_SES 20 50
PG_IF_UAS 20 50
PG_IF_CSES 4 (number of consecutive SESs)

Possible Causes
The system detects the protection group bit errors.
Related Alarms
PG_LINK_FAIL, PG_PRT_DEGRADED
Procedure
Step 1 See PG_LINK_FAIL, PG_PRT_DEGRADED.
----End
869
B.3.24 RPLMAX, RPLMIN, and RPLCUR
Description
l RPLMAX indicates the maximum receive optical power at an optical interface.
l RPLMIN indicates the minimum receive optical power at an optical interface.
l RPLCUR indicates the current receive optical power at an optical interface.
Attribute
Performance event cell IPM
Unit 0.1dBm

Impact on System
In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,
and 5 dB lower than the overload power.
If the receive optical power is very low or very high, bit errors occur and even services are
interrupted.
Related Alarms
l If the transmit optical power is lower than the receiver sensitivity, the IN_PWR_LOW
alarm is reported.
l If the receive optical power is higher than the overload power, the IN_PWR_HIGH alarm
is reported.
B.3.25 RSBBE, RSES, RSSES, RSCSES, and RSUAS
Description
l RSBBE indicates the regenerator section background block error.
the unavailable and severely errored seconds.
l RSES indicates the regenerator section errored second.
l RSSES indicates the regenerator section severely errored second.
-2
l RSCSES indicates the regenerator section consecutive severely errored second.
870
l RSUAS indicates the regenerator section unavailable second.
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
Unit Block (RSBBE)
Second (RSES, RSSES, RSCSES, and
RSUAS)

Impact on System
-3
and 10
-6
Related Alarms
When the RSBBE, RSES, RSSES, RSCSES, or RSUAS performance event crosses the preset
threshold, the RS_CROSSTR alarm is reported.
Threshold
Default 24-Hour
Threshold
RSBBE 1500 15000
RSES 50 100
RSSES 20 50
RSUAS 20 50
RSCSES 4 (number of consecutive SESs)

Possible Causes
The system detects the regenerator section bit errors through the B1 byte.
871
Procedure
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
B.3.26 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG
Description
l RSL_MAX indicates the maximum radio received signal level.
l RSL_MIN indicates the minimum radio received signal level.
l RSL_CUR indicates the current radio received signal level.
l RSL_AVG indicates the average radio received signal level.
Attribute
Performance event cell RSL
Unit 0.1dBm

Impact on 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.
B.3.27 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.
872
Attribute
Performance event cell OOF
Unit Block (RSOOF)
Second (RSOFS)

Impact on System
The system discards OOF data blocks. Therefore, an RSOOF event is equivalent to a big error
(if one RSOOF exists in a second, the BER is not less than 1.25 x 10
-5
).
Related Alarms
If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. 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
B.3.28 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16,
QAMWS32, QAMWS64, QAMWS128, QAMWS256, QAMWS512,
QAM_L_WS512, QAMWS1024, and QAM_L_WS1024
Description
l QPSKWS indicates the working duration of the QPSK mode.
l QPSK_S_WS indicates the working duration of the QPSKWS Strong mode.
l QAMWS16 indicates the working duration of the 16QAM mode.
l QAM_S_WS16 indicates the working duration of the 16QAM Strong mode.
l QAM_L_WS512 indicates the working duration of the 512QAM Light mode.
873
l QAM_L_WS1024 indicates the working duration of the 1024QAM Light mode.
Attribute
Performance event cell QPSKWSSECOND (QPSK)
QPSK_S_WSSECOND (QPSK Strong)
QAMWS16SECOND (16QAM)
QAM_S_WS16SECOND (16QAM Strong)
QAM_L_WS512SECOND (512QAM
Light)
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.
B.3.29 TLBMAX, TLBMIN, and TLBCUR
Description
l TLBMAX indicates the maximum transmit bias current of the laser.
l TLBMIN indicates the minimum transmit bias current of the laser.
l TLBCUR indicates the current transmit bias current of the laser.
874
Attribute
Performance event cell LSBCM
Unit 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.
B.3.30 RLHTT, RLLTT, TLHTT, TLLTT
Description
l The RLHTT indicates the duration when the ODU at the local end has a receive power
lower than the upper threshold.
l The RLLTT indicates the duration when the ODU at the local end has a receive power
lower than the lower threshold.
l The TLHTT indicates the duration when the ODU at the local end has a transit power higher
than the upper threshold.
l The TLLTT indicates the duration when the ODU at the local end has a transit power higher
than the lower threshold.
Attribute
Performance event cell RLHTS(RLHTT), RLLTS(RLLTT), TLHTS
(TLHTT), and TLLTS(TLLTT)
Unit Second

Impact on System
None.
Related Alarms
None.
875
B.3.31 TPLMAX, TPLMIN, and TPLCUR
Description
l TPLMAX indicates the maximum transmit optical power at an optical interface.
l TPLMIN indicates the minimum transmit optical power at an optical interface.
l TPLCUR indicates the current transmit optical power at an optical interface.
Attribute
Performance event cell OPM
Unit 0.1dBm

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 If the transmit optical power at the opposite site is lower than the receiver sensitivity, the
IN_PWR_LOW alarm is reported.
l If the receive optical power at the opposite site is higher than the overload power, the
IN_PWR_HIGH alarm is reported.
B.3.32 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG
Description
l TSL_MAX indicates the maximum radio transmitted signal level.
l TSL_MIN indicates the minimum radio transmitted signal level.
l TSL_CUR indicates the current radio transmitted signal level.
l TSL_AVG indicates the average radio transmitted signal level.
Attribute
Performance event cell TSL
Unit 0.1dBm

876
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.
B.3.33 TUPJCHIGH, TUPJCLOW, and TUPJCNEW
Description
l TUPJCHIGH indicates the count of positive TU pointer justifications.
l TUPJCLOW indicates the count of negative TU pointer justifications.
l TUPJCNEW indicates the count of new TU pointer justifications.
Attribute
Performance event cell TUPPJE (TUPJCHIGH)
TUNPJE (TUPJCLOW)
TUNDF (TUPJCNEW)
Unit Block

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.
Threshold
Default 24-Hour
Threshold
TUPJCHIGH 1500 30000
TUPJCLOW 1500 30000
TUPJCNEW 1500 30000

877
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
B.3.34 XPIC_XPD_VALUE
Description
The XPIC_XPD_VALUE indicates the XPD value after the XPIC function is enabled.
Attribute
Performance event cell XPD
Unit dB

Impact on System
l When the XPIC function is disabled, the performance event does not affect the system.
l When the XPIC function is enabled, a greater XPD value indicates less interference between
H and V polarization directions and better signaling environment; a smaller XPD 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.
878
C 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.
C.1 List of RMON Alarm Entries
The RMON alarm entries refer to the table entries in the RMON alarm group.
C.2 RMON Performance Entries List on the Packet-Plane
This section lists RMON performance entries on the packet plane by logical board.
C.3 RMON Performance Entries List on the EoS/EoPDH-Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board type.
C.4 RMON Events and Handling Procedures
This chapter describes the RMON events that indicate Ethernet service abnormalities and how
to handle these events.
Maintenance Guide C RMON Event Reference
879
C.1 List of RMON Alarm Entries
The RMON alarm entries refer to the table entries in the RMON alarm group.
Table C-1 List of RMON alarm entries
Alarm
Name
Description Remarks Source
ETHDR
OP
The number of packet
loss events
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.
ISU2, ISX2, IFU2, IFX2,
ISV3
, EM6FA, EM6TA, EG4,
EG4P, EM6T, EM6F
ETHEX
CCOL
The number of frames
that fail to be transmitted
after continuous
collisions
Indicates the number of
frames that fail to be
transmitted due to
consecutive collisions.
, EM6T, EM6F, EM6FA,
EM6TA, EG4, EG4P
ETHLAT
ECOL
The number of collisions
that are detected after a
timeslot period elapses
collisions that are
detected after a timeslot
period elapses. The late
collisions indicate that
the diameter of a LAN is
too large.
TXDEFF
RM
The number of frames
whose transmission is
delayed
frames whose first
transmission is delayed
because transmission
media are busy,
excluding the number of
frames whose
transmission is delayed
due to collisions.
ETHUN
DER
The number of received
undersized packets
Undersized packets are
the packets shorter than
64 bytes (including FCS
bytes but not framing
bits).
880
Alarm
Name
ETHOV
ER
oversized packets
Oversized packets are
the packets larger than
MTU (including FCS
bits).
ETHFRG The number of received
fragmented packets
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 The number of received
errored oversized
packets
ETHJAB indicates the
number of received
packets that are larger
than MTU (including
FCS bytes but not
errors.
RXBBA
D
The number of bytes in
received bad packets
FCS bytes are included
but framing bits are
excluded.
ISU2, ISX2, IFU2, IFX2,
ISV3
, EM6FA, EM6TA, EG4,
EG4P, EM6T, EM6F
ETHFCS The number of frames
that have FCS check
errors
FCS error frames
exclude oversized
frames and undersized
frames.
PORT_R
X_BW_
UTILIZ
ATION
Indicates the bandwidth
utilization at a port in the
receive direction.
Bandwidth utilization
ratio = (Number of
received bytes x 8/
Monitoring period)/
Configured or actual
bandwidth
PORT_T
X_BW_
UTILIZ
ATION
utilization at a port in the
transmit direction.
Bandwidth utilization
ratio = (Number of
transmitted bytes x 8/
Monitoring period)/
Configured or actual
bandwidth

881
Table C-2 List of EMS6\EFP8 RMON alarm entries
Alarm
Name
ETHDR
OP
The number of packet
loss events
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.
EMS6, EFP8
RXBBA
D
The number of bytes in
FCS bytes are included
but framing bits are
excluded.
ETHUN
DER
undersized packets
Undersized packets are
the packets shorter than
64 bytes (including FCS
bits).
ETHOV
ER
oversized packets
Oversized packets are
the packets larger than
MTU (including FCS
bits).
ETHFRG The number of received
fragmented packets
ETHFRG indicates the
number of received
packets that are shorter
than 64 bytes (including
FCS bytes but not
errors.
ETHJAB The number of received
errored oversized
packets
ETHJAB indicates the
number of received
packets that are larger
than MTU (including
FCS bytes but not
errors.
that have FCS check
errors
FCS error frames
exclude oversized
frames and undersized
frames.
882
Alarm
Name
ETHALI The number of alignment
error frames
An alignment error
means that the frame
contains a fractional
number of bytes and fails
to pass the FCS check.

C.2 RMON Performance Entries List on the Packet-Plane
This section lists RMON performance entries on the packet plane by logical board.
C.2.1 EM6F/EM6T/EM6FA/EM6TA/EG4/EG4P
The RMON performance that the EM6F/EM6T/EM6FA/EM6TA/EG4/EG4P board supports
includes basic performance, extended performance, port traffic classification performance, port
priority performance, and Port DS domain performance.
Table C-3 Packet-plane RMON performance entry list (EM6F/EM6T/EM6FA/EM6TA/EG4/EG4P)
Category Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks
Basic
performanc
e
RXPKTS
Indicates the packets
received (packets).
Bad packets, broadcast packets, and
multicast packets are included.
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 bytes
received (bytes).
RXOCTETS indicates the total number
of bytes in received packets (including
bad packets), including framing bits but
not FCS bytes.
NOTE
If the packets received by an EM6T/EM6F
board are larger than MTU, byte count is
calculated based on the MTU.
If the packets received by an EG4/EG4P/
EM6FA/EM6TA board are larger than the
MTU, byte count is calculated based on actual
packet size.
RXMULCAST Indicates the multicast
packets received
(packets).
RXMULCAST indicates the total
number of received good packets with
multicast destination addresses,
excluding broadcast packets.
883
Performance Entry
Full Name of a
Performance Entry
Remarks
RXBRDCAST Indicates the broadcast
packets received
(packets).
ETHOVER Indicates the oversized
packets received
(packets).
Oversized packets are the packets larger
than MTU (including FCS bytes but not
framing bits).
NOTE
For EG4/EG4P boards, an oversized packet
is larger than 1518 bytes.
For other boards, an oversized packet is larger
than the MTU.
ETHJAB Indicates the oversized
error packets received
(packets).
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.
NOTE
For EG4/EG4P boards, an oversized error
packet is larger than 1518 bytes.
For other boards, an oversized error packet is
larger than the MTU.
ETHUNDER Indicates the undersized
packets received
(packets).
Undersized packets are the packets
shorter than 64 bytes (including FCS
bytes but not framing bits).
ETHFRG Indicates the fragments
received (packets).
ETHFRG indicates the number of
received packets that are shorter than 64
bytes (including FCS bytes but not
alignment errors. Increase of the count is
normal because noise collisions exist.
ETHCOL Indicates the collisions
(times).
-
PORT_RX_BW_UTI-
LIZATION
utilization on a port in the
receive direction.
Bandwidth utilization = (Number of
received bytes x 8/Monitoring period)/
Configured or actual bandwidth
PORT_TX_BW_UTI-
LIZATION
transmit direction.
transmitted bytes x 8/Monitoring
period)/Configured or actual bandwidth
Extended
performanc
e
TXPKTS Indicates the packets
transmitted (packets).
884
Performance Entry
Full Name of a
Performance Entry
Remarks
TXOCTETS Indicates the bytes
transmitted
Indicates the total number of bytes in
transmitted packets (including bad
packets), including framing bits but not
FCS bytes.
ETHFCS Indicates the FCS errored
frames (frames).
Indicates the number of received frames
that are an integral number of octets in
length but do not pass the FCS check.
NOTE
For EG4/EG4P boards, this count includes
undersized frames and oversized frames.
For other boards, this count does not include
undersized frames and oversized frames.
RXBGOOD Indicates the bytes in
received good packets
(bytes).
FCS bytes are included, but framing bits
are excluded.
TXBGOOD Indicates the bytes in
transmitted good packets
(bytes).
are excluded.
RXBBAD Indicates the bytes in
(bytes).
are excluded.
TXUNICAST Indicates the unicast
packets transmitted
(packets).
The unicast packets that are discarded or
fail to be transmitted are included.
RXUNICAST Indicates the unicast
packets received
(packets).
RXUNICAST indicates the number of
good unicast packets.
TXMULCAST Indicates the multicast
packets transmitted
(packets).
The multicast packets that are discarded
or fail to be transmitted are included.
TXBRDCAST Indicates the broadcast
packets transmitted
(packets).
The broadcast packets that are discarded
RXGOODFULLFRAME
SPEED
Indicates the rate of good
full-frame bytes received
(kbit/s).
Framing bits (20 bytes) and FCS bytes
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
transmitted (kbit/s).
are included.
885
Performance Entry
Full Name of a
Performance Entry
Remarks
RXFULLBGOOD Indicates the good full-
frame bytes received
(bytes).
are included.
TXFULLBGOOD Indicates the good full-
frame bytes transmitted
(bytes).
are included.
RXPAUSE Indicates the pause frames
received (frames).
RXPAUSE indicates the number of
MAC flow control frames with the
PAUSE opcode.
TXPAUSE Indicates the pause frames
transmitted (frames).
TXPAUSE indicates the number of
PAUSE opcode.
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.
ETHEXCCOL Indicates the frames
unsuccessfully
transmitted after
consecutive collisions
(frames).
-
TXDEFFRM Indicates the frames that
are deferred in
transmission (frames).
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.
RX_DROP_RATIO Packet loss rate in the
ingress direction
The discarded packets ratio in the ingress
direction, that is, number of actually drop
packets/ received packets.
TX_DROP_RATIO Packet loss rate in the
egress direction
packets/ transmitted packets.
ETH_RX_THROUGHP
UT_MAX
Indicates the maximum
throughput on a port in the
receive direction.
Maximum throughput = Number of
received bytes (including inter-frame
gaps and preambles)/Monitoring period
ETH_RX_THROUGHP
UT_MIN
Indicates the minimum
receive direction.
Minimum throughput = Number of
886
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_RX_THROUGHP
UT_AVG
Indicates the average
receive direction.
Average throughput = Number of
RXBPS Indicates the bit rate in the
receive direction of an
Ethernet port.
Bit rate in the receive direction = Number
of received bytes x 8/Monitoring period
TXBPS Indicates the bit rate in the
transmit direction of an
Ethernet port.
Bit rate in the transmit direction =
Number of transmitted bytes x 8/
Monitoring period
RXPPS Indicates the packet rate
(packets/second) in the
Ethernet port.
Packet rate in the receive direction =
Number of received packets/Monitoring
period
TXPPS Indicates the packet rate
Ethernet port.
Packet rate in the transmit direction =
Number of transmitted packets/
Monitoring period
Port traffic
classificati
on
performanc
e
QOS_PORTCAR_Mar-
kedRedPKTS
red packets after traffic
monitoring is enabled.
-
QOS_PORTCAR_Mar-
kedYellowPKTS
yellow packets after traffic
-
QOS_PORTCAR_Mar-
kedGreenPKTS
green packets after traffic
-
QOS_PORTSTRM_RCV
MATCHPKTS
packets received in the
matched flow.
-
QOS_PORTSTRM_SND
MATCHPKTS
packets transmitted in the
matched flow.
-
PORTSTRM_SHAPING
_DROPPKTS
packets discarded due to
network congestion when
the traffic shaping
function is enabled in the
egress direction.
-
887
Performance Entry
Full Name of a
Performance Entry
Remarks
PORTSTRM_SHAPING
_DROPRATIO
Indicates the ratio of
packet loss due to network
congestion when the
traffic shaping function is
enabled in the egress
direction.
Packet loss rate in the egress direction =
Number of discarded packets in the
egress direction/Number of packets
matching the traffic classification rule in
the egress direction
QOS_PORTCAR_Mar-
kedRedRATIO
Indicates the proportion of
packets marked in red
when the traffic policing
function is enabled.
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_PORTSTRM_RX_
PPS
Indicates the packet rate
(packets/s) in the receive
direction of a matched
flow.
period
QOS_PORTSTRM_TX_
PPS
(packets/s) in the transmit
flow.
Monitoring period
QOS_PORTSTRM_RCV
MATCHBYTES
a
bytes in the received
packets of a matched flow.
-
QOS_PORTSTRM_SND
MATCHBYTES
a
bytes in the transmitted
-
QOS_PORTSTRM_RX_
BPS
a
Indicates the bit rate in the
receive direction of a
matched flow.
QOS_PORTSTRM_TX_
BPS
a
transmit direction of a
matched flow.
Number of received bytes x 8/
Monitoring period
Port
priority
performanc
e
QOS_PORTQUEUE_DR
OPRATIO
packet loss due to
congestion in egress
queues with different
priorities.
Packet loss rate 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_DROPPKTS Indicates the number of
packets discarded in the
services with different
priorities.
-
888
Performance Entry
Full Name of a
Performance Entry
Remarks
QOS_PRI_DROPBYTES Indicates the number of
bytes discarded in the
priorities.
-
PORT_PRI_SNDPKTS Indicates the number of
packets transmitted in
egress queues with
different priorities.
-
PORT_PRI_SNDBYTES Indicates the number of
bytes in the packets
transmitted in egress
priorities.
-
PORT_PRI_TX_BPS Indicates the bit rates of
egress queues with
different priorities in the
transmit direction.
Bit rate = Number of transmitted bytes x
8/Monitoring period
PORT_PRI_TX_PPS Indicates the packet rate
(packets/second) of egress
priorities in the transmit
direction.
Packet rate = Number of transmitted
packets/Monitoring period
Port DS
domain
performanc
e
DS_CVLANPRI_PKTS Indicates the number of
packets with matched C-
VLAN priorities in the DS
domain
-
DS_CVLANPRI_BYTES Indicates the number of
bytes in the packets with
matched C-VLAN
priorities in the DS
domain.
-
DS_SVLANPRI_PKTS Indicates the number of
packets with matched S-
domain.
-
DS_SVLANPRI_BYTES Indicates the number of
matched S-VLAN
domain.
-
889
Performance Entry
Full Name of a
Performance Entry
Remarks
DS_DSCP_PKTS Indicates the number of
packets with matched IP
DSCP priorities in the DS
domain.
-
DS_DSCP_BYTES Indicates the number of
matched IP DSCP
domain.
-

NOTE
Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications or
port DS domains.
C.2.2 IFU2/IFX2
The RMON performance that the IFU2/IFX2 board supported include basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.
Table C-4 Packet-Plane RMON Performance Entry List (IFU2/IFX2)
Performance Entry
Full Name of a
Performance Entry
Remarks
Basic
performanc
e
RXPKTS
received (packets).
events (times).
received (bytes).
not FCS bytes.
NOTE
If the packets received by an IFU2/IFX2
board are larger than the MTU, byte count is
calculated based on MTU.
890
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
packets received
(packets).
PORT_RX_BW_UTI-
LIZATION
receive direction.
PORT_TX_BW_UTI-
LIZATION
transmit direction.
Extended
performanc
e
transmitted
FCS bytes.
frames (frames).
NOTE
For the IFU2/IFX2 board, this count does not
include undersized frames and oversized
frames.
(bytes).
are excluded.
(bytes).
are excluded.
(bytes).
are excluded.
packets transmitted
(packets).
891
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
packets transmitted
(packets).
packets transmitted
(packets).
RXGOODFULLFRAME
SPEED
(kbit/s).
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
are included.
(bytes).
are included.
(bytes).
are included.
ingress direction
packets/ received packets.
egress direction
packets/ transmitted packets.
ETH_RX_THROUGHP
UT_MAX
receive direction.
ETH_RX_THROUGHP
UT_MIN
receive direction.
ETH_RX_THROUGHP
UT_AVG
receive direction.
Ethernet port.
892
Performance Entry
Full Name of a
Performance Entry
Remarks
Ethernet port.
Monitoring period
Ethernet port.
period
Ethernet port.
Monitoring period
Port traffic
classificati
on
QOS_PORTCAR_Mar-
kedRedPKTS
-
QOS_PORTCAR_Mar-
kedYellowPKTS
-
QOS_PORTCAR_Mar-
kedGreenPKTS
-
QOS_PORTSTRM_RCV
MATCHPKTS
matched flow.
-
QOS_PORTSTRM_SND
MATCHPKTS
matched flow.
-
PORTSTRM_SHAPING
_DROPPKTS
the traffic shaping
egress direction.
-
PORTSTRM_SHAPING
_DROPRATIO
congestion when the
direction.
893
Performance Entry
Full Name of a
Performance Entry
Remarks
QOS_PORTCAR_Mar-
kedRedRATIO
QOS_PORTSTRM_RX_
PPS
flow.
period
QOS_PORTSTRM_TX_
PPS
flow.
Monitoring period
QOS_PORTSTRM_RCV
MATCHBYTES
-
QOS_PORTSTRM_SND
MATCHBYTES
-
QOS_PORTSTRM_RX_
BPS
matched flow.
QOS_PORTSTRM_TX_
BPS
matched flow.
Monitoring period
Port
priority
QOS_PORTQUEUE_DR
OPRATIO
packet loss due to
priorities.
queue
priorities.
-
priorities.
-
894
Performance Entry
Full Name of a
Performance Entry
Remarks
egress queues with
-
priorities.
-
egress queues with
transmit direction.
8/Monitoring period
direction.
Port DS
domain
domain
-
matched C-VLAN
domain.
-
domain.
-
matched S-VLAN
domain.
-
domain.
-
895
Performance Entry
Full Name of a
Performance Entry
Remarks
matched IP DSCP
domain.
-

NOTE
l Integrated IP radio ports support this parameter.
l Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications
or port DS domains.
C.2.3 ISU2/ISX2/ISV3
The RMON performance that the ISU2/ISX2/ISV3 board supported include basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.
Table C-5 Packet-Plane RMON Performance Entry List (ISU2/ISX2/ISV3)
Performance Entry
Full Name of a
Performance Entry
Remarks
Basic
performanc
e
RXPKTS Indicates the packets
received (packets).
events (times).
NOTE
For the ISV3 board, ETHDROP counts
packet loss events caused by congestion.
For the ISU2 and ISX2 boards, ETHDROP
counts packet loss events caused by
exceptions or congestion.
For other boards, ETHDROP counts packet
loss events caused by insufficient Ethernet
chip resources, but does not count packet loss
events caused by link congestion and other
reasons.
896
Performance Entry
Full Name of a
Performance Entry
Remarks
received (bytes).
not FCS bytes.
NOTE
If the packets received by an ISU2/ISX2/
ISV3 board are larger than the MTU, byte
count is calculated based on MTU.
packets received
(packets).
packets received
(packets).
PORT_RX_BW_UTI-
LIZATION
receive direction.
PORT_TX_BW_UTI-
LIZATION
transmit direction.
RXPKT64 Packets received (64 bytes
in length) (packets)
are excluded.
RXPKT65 Packets received (65-127
bytes in length) (packets)
are excluded.
are excluded.
are excluded.
RXPKT512 Packets received
(512-1023 bytes in length)
(packets)
are excluded.
(1024-1518 bytes in
length) (packets)
are excluded.
Extended
performanc
e
897
Performance Entry
Full Name of a
Performance Entry
Remarks
transmitted
FCS bytes.
frames (frames).
NOTE
For the ISU2/ISX2/ISV3 board, this count
does not include undersized frames and
oversized frames.
(bytes).
are excluded.
(bytes).
are excluded.
(bytes).
are excluded.
packets transmitted
(packets).
packets received
(packets).
packets transmitted
(packets).
packets transmitted
(packets).
RXGOODFULLFRAME
SPEED
(kbit/s).
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
are included.
(bytes).
are included.
898
Performance Entry
Full Name of a
Performance Entry
Remarks
(bytes).
are included.
ingress direction
packets/received packets.
egress direction
packets/transmitted packets.
RXPKT1519 Indicates the count of
received packets with a
length of over 1518 bytes
(errored packets included)
are excluded.
TXPKT64 Indicates the count of
transmitted 64-byte
packets (errored packets
included)
are excluded.
transmitted packets with a
length of 65 to 127 bytes
are excluded.
are excluded.
are excluded.
length of 512 to 1023
bytes (errored packets
included)
are excluded.
included)
are excluded.
899
Performance Entry
Full Name of a
Performance Entry
Remarks
are excluded.
ETH_RX_THROUGHP
UT_MAX
receive direction.
ETH_RX_THROUGHP
UT_MIN
receive direction.
ETH_RX_THROUGHP
UT_AVG
receive direction.
Ethernet port.
Ethernet port.
Monitoring period
Ethernet port.
period
Ethernet port.
Monitoring period
Port traffic
classificati
on
QOS_PORTCAR_Mar-
kedRedPKTS
-
QOS_PORTCAR_Mar-
kedYellowPKTS
-
QOS_PORTCAR_Mar-
kedGreenPKTS
-
QOS_PORTSTRM_RCV
MATCHPKTS
matched flow.
-
900
Performance Entry
Full Name of a
Performance Entry
Remarks
QOS_PORTSTRM_SND
MATCHPKTS
matched flow.
-
PORTSTRM_SHAPING
_DROPPKTS
the traffic shaping
egress direction.
-
PORTSTRM_SHAPING
_DROPRATIO
congestion when the
direction.
QOS_PORTCAR_Mar-
kedRedRATIO
QOS_PORTSTRM_RX_
PPS
flow.
period
QOS_PORTSTRM_TX_
PPS
flow.
Monitoring period
QOS_PORTSTRM_RCV
MATCHBYTES
-
QOS_PORTSTRM_SND
MATCHBYTES
-
QOS_PORTSTRM_RX_
BPS
matched flow.
QOS_PORTSTRM_TX_
BPS
matched flow.
Monitoring period
901
Performance Entry
Full Name of a
Performance Entry
Remarks
Port
priority
QOS_PORTQUEUE_DR
OPRATIO
packet loss due to
priorities.
queue
priorities.
-
priorities.
-
egress queues with
-
priorities.
-
egress queues with
transmit direction.
8/Monitoring period
direction.
Port DS
domain
domain
-
matched C-VLAN
domain.
-
902
Performance Entry
Full Name of a
Performance Entry
Remarks
domain.
-
matched S-VLAN
domain.
-
domain.
-
matched IP DSCP
domain.
-

NOTE
l Integrated IP radio ports support this parameter.
l Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications
or port DS domains.
C.2.4 ML1/MD1
The RMON performance that the ML1/MD1 board supported include ATM PWE3 performance,
ATM/IMA performance events on the access side, CES performance, PW performance, PPP
performance, and MLPPP performance.
Table C-6 Packet-Plane RMON Performance Entry List (ML1/MD1)
Performance Entry
Full Name of a
Performance Entry
Remarks
ATM
PWE3
performanc
e
ATMPW_SNDCELLS
Indicates the count of
transmitted cells. -
ATMPW_RCVCELLS Indicates the count of
received cells.
-
ATMPW_UNKNOWN-
CELLS
Indicates the count of
unknown cells.
-
903
Performance Entry
Full Name of a
Performance Entry
Remarks
ATM/IMA
performanc
e events on
the access
side
PORT_RX_BW_UTI-
LIZATION
receive direction.
PORT_TX_BW_UTI-
LIZATION
transmit direction.
ATM_CORRECTED_H
CSERR
correctable HCS error
cells received.
ATM_CORRECTED_HCSERR is used
to evaluate the service quality.
ATM_UNCORRECTED
_HCSERR
uncorrectable HCS error
cells received.
ATM_UNCORRECTED_HCSERR is
used to determine whether cell loss
occurs on a port.
ATM_RCVCELLS Indicates the total number
of received cells.
ATM_RCVCELLS is used to determine
whether ATM connections are normal.
ATM_RCVIDLECELLS Indicates the total number
of received idle cells.
ATM_RCVIDLECELLS is used to
determine whether cells are properly
processed at the ATM physical layer.
ATM_SNDCELLS Indicates the total number
of transmitted cells.
ATM_SNDCELLS is used to determine
whether a port transmits services
normally.
ATM_IF_INRATE_MA
X
rate of normal cells
received on the port.
-
ATM_IF_INRATE_MIN Indicates the minimum
received on the port.
-
ATM_IF_INRATE_AVG Indicates the average rate
of normal cells received
on the port.
-
ATM_IF_OUTRATE_M
AX
transmitted on the port.
-
ATM_IF_OUTRATE_M
IN
transmitted on the port.
-
ATM_IF_OUTRATE_A
VG
Indicates the average rate
of normal cells transmitted
on the port.
-
904
Performance Entry
Full Name of a
Performance Entry
Remarks
ATM_CELL_AVAILA-
BILITY
Indicates the percentage of
valid cells.
Percentage of valid cells = (Total number
of cells - Number of HEC-detected error
cells)/Total number of cells
PORT_RX_BW_UTI-
LIZATION
utilization rate (0.01%) of
the port in the receive
direction.
PORT_TX_BW_UTI-
LIZATION
utilization rate (0.01%) of
the port in the transmit
direction.
ATM_UNI1_INRATE_
MAX
rate of receiving correct
cells on the UNI1 side of
ATM connections.
ATM_UNI1_INRATE_MAX is based
on VPIs/VCIs.
ATM_UNI1_INRATE_
MIN
ATM connections.
ATM_UNI1_INRATE_MIN is based on
VPIs/VCIs.
ATM_UNI1_INRATE_A
VG
of receiving correct cells
on the UNI1 side of ATM
connections.
ATM_UNI1_INRATE_AVG is based
on VPIs/VCIs.
ATM_UNI1_OUTRATE
_MAX
rate of transmitting correct
ATM connections.
ATM_UNI1_OUTRATE_MAX is
based on VPIs/VCIs.
ATM_UNI1_OUTRATE
_MIN
ATM connections.
ATM_UNI1_OUTRATE_MIN is based
on VPIs/VCIs.
ATM_UNI1_OUTRATE
_AVG
of transmitting correct
ATM connections.
ATM_UNI1_OUTRATE_AVG is based
on VPIs/VCIs.
ATM_UNI2_INRATE_
MAX
ATM connections.
ATM_UNI2_INRATE_MAX is based
on VPIs/VCIs.
905
Performance Entry
Full Name of a
Performance Entry
Remarks
ATM_UNI2_INRATE_
MIN
ATM connections.
ATM_UNI2_INRATE_MIN is based on
VPIs/VCIs.
ATM_UNI2_INRATE_A
VG
connections.
ATM_UNI2_INRATE_AVG is based
on VPIs/VCIs.
ATM_UNI2_OUTRATE
_MAX
ATM connections.
ATM_UNI2_OUTRATE_MAX is
based on VPIs/VCIs.
ATM_UNI2_OUTRATE
_MIN
ATM connections.
ATM_UNI2_OUTRATE_MIN is based
on VPIs/VCIs.
ATM_UNI2_OUTRATE
_AVG
ATM connections.
ATM_UNI2_OUTRATE_AVG is based
on VPIs/VCIs.
ATM_UNI1_INCELLS Indicates the total number
connections.
ATM_UNI1_INCELLS is used to
determine whether ATM connections are
normal.
ATM_UNI1_OUT-
CELLS
Indicates the total number
ATM connections.
ATM_UNI1_OUTCELLS is used to
normal.
ATM_UNI2_INCELLS Indicates the total number
connections.
ATM_UNI2_INCELLS is used to
normal.
ATM_UNI2_OUT-
CELLS
Indicates the total number
ATM connections.
ATM_UNI2_OUTCELLS is used to
normal.
CES
performanc
e event
CES_MISORDERPKTS Indicates the number of
lost disordered packets.
-
CES_STRAYPKTS Indicates the number of
mis-connected packets.
-
906
Performance Entry
Full Name of a
Performance Entry
Remarks
CES_MALPKTS Indicates the number of
deformed frames.
-
CES_JTRUDR Indicates the number of
jitter buffer underflows.
-
CES_JTROVR Indicates the number of
jitter buffer overflows.
-
CES_LOSPKTS Indicates the number of
lost packets.
-
CES_RX_PKTS Indicates the number of
received packets.
-
PW
performanc
e of ATM/
CES
PW_RCVPKTS Indicates the number of
packets received from
PWs.
-
PW_RCVBYTES Indicates the number of
bytes received from PWs.
-
PW_SNDPKTS Indicates the number of
packets sent by PWs.
-
PW_SNDBYTES Indicates the number of
bytes sent by PWs.
-
MPLS_PW_FLR Indicates the packet loss
rate on the PW.
Packet loss rate = (Number of packets
transmitted by the source - Number of
packets received by the sink)/Number of
packets transmitted by the 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.)
MPLS_PW_FD Indicates the frame delay
on the PW.
Frame delay = Time when the source
sends a request packet - Time when the
source receives the response packet
MPLS_PW_FDV Indicates the frame delay
variation on the PW.
Frame delay variation is the difference
between two frame delay test results.
PPP PPP_TX_PKTS Indicates the number of
transmitted PPP packets.
-
907
Performance Entry
Full Name of a
Performance Entry
Remarks
PPP_TX_BYTES Indicates the number of
bytes of transmitted PPP
packets.
-
PPP_RX_PKTS Indicates the number of
received PPP packets.
-
PPP_RX_BYTES Indicates the number of
bytes of received PPP
packets.
-
PPP_RX_FCSPKTS Indicates the number of
PPP packets that received
FCS faults.
-
PPP_TX_LOSPKTS Indicates the number of
PPP packets dropped in
the transmitting process.
-
PPP_RX_LOSPKTS Indicates the number of
relieved abnormal PPP
packets.
-
PPP_RX_BW_UTILIZA-
TION
Indicates the PPP
bandwidth usage in the
receive direction.
PPP bandwidth usage = (Number of
PPP_TX_BW_UTILIZA-
TION
Indicates the PPP
transmit direction.
MLPPP MP_TX_PKTS Indicates the number of
transmitted MP packets.
-
MP_TX_BYTES Indicates the number of
bytes of transmitted MP
packets.
-
MP_RX_PKTS Indicates the number of
received MP packets.
-
MP_RX_BYTES Indicates the number of
bytes of received MP
packets.
-
MP_RX_ERRPKTS Indicates the number of
-
MP_TX_TOTALPKTS Indicates the total number
of transmitted MP
packets.
The transmitted MP packets include
service and protocol packets.
908
Performance Entry
Full Name of a
Performance Entry
Remarks
MP_RX_TOTALPKTS Indicates the total number
of received MP packets.
The received MP packets include service
and protocol packets.
MP_RX_BW_UTILIZA-
TION
Indicates the MP
receive direction.
MP bandwidth usage = (Number of
MP_TX_BW_UTILIZA-
TION
Indicates the MP
transmit direction.

C.2.5 CQ1
The RMON performance that the MP1 board supported include CES performance, PW
performance, PPP performance, and MLPPP performance.
Table C-7 Packet-Plane RMON Performance Entry List (CQ1)
Performance Entry
Full Name of a
Performance Entry
Remarks
CES
performanc
e event
CES_MISORDERPKTS
lost disordered packets. -
CES_STRAYPKTS Indicates the number of
mis-connected packets.
-
CES_MALPKTS Indicates the number of
deformed frames.
-
CES_JTRUDR Indicates the number of
jitter buffer underflows.
-
CES_JTROVR Indicates the number of
jitter buffer overflows.
-
CES_LOSPKTS Indicates the number of
lost packets.
-
CES_RX_PKTS Indicates the number of
received packets.
-
PW
performanc
e of CES
packets received from
PWs.
-
packets sent by PWs.
-
909
Performance Entry
Full Name of a
Performance Entry
Remarks
PW_SNDBYTES Indicates the number of
bytes sent by PWs.
-
bytes received from PWs.
-
PPP PPP_TX_PKTS Indicates the number of
transmitted PPP packets.
-
PPP_TX_BYTES Indicates the number of
bytes of transmitted PPP
packets.
-
PPP_RX_PKTS Indicates the number of
received PPP packets.
-
PPP_RX_BYTES Indicates the number of
bytes of received PPP
packets.
-
PPP_RX_FCSPKTS Indicates the number of
PPP packets that received
FCS faults.
-
PPP_TX_LOSPKTS Indicates the number of
PPP packets dropped in
the transmitting process.
-
PPP_RX_LOSPKTS Indicates the number of
relieved abnormal PPP
packets.
-
PPP_RX_BW_UTILIZA-
TION
Indicates the PPP
receive direction.
PPP_TX_BW_UTILIZA-
TION
Indicates the PPP
transmit direction.
MLPPP MP_TX_PKTS Indicates the number of
transmitted MP packets.
-
MP_TX_BYTES Indicates the number of
bytes of transmitted MP
packets.
-
MP_RX_PKTS Indicates the number of
-
910
Performance Entry
Full Name of a
Performance Entry
Remarks
MP_RX_BYTES Indicates the number of
bytes of received MP
packets.
-
MP_RX_ERRPKTS Indicates the number of
-
MP_TX_TOTALPKTS Indicates the total number
of transmitted MP
packets.
The transmitted MP packets include
service and protocol packets.
MP_RX_TOTALPKTS Indicates the total number
of received MP packets.
The received MP packets include service
and protocol packets.
MP_RX_BW_UTILIZA-
TION
Indicates the MP
receive direction.
MP_TX_BW_UTILIZA-
TION
Indicates the MP
transmit direction.

C.2.6 CSH
The RMON performance that the CSH board supported include L2VPN performance, Tunnel
performance, PW performance of L2VPN, ETH OAM 802.1ag performance, and MPLS-TP
OAM performance.
Table C-8 Packet-plane RMON performance entry list (CSH)
Performance Entry
Full Name of a
Performance Entry
Remarks
L2VPN
a
performanc
e
VLAN_RCVPKTS
packets received at the V-
UNI VLAN. -
VLAN_RCVBYTES Indicates the number of
received at the V-UNI
VLAN.
-
VUNI_RCVPKTS Indicates the number of
packets received on the V-
UNI.
Indicates the number of packets received
on a V-UNI of a service.
911
Performance Entry
Full Name of a
Performance Entry
Remarks
VUNI_RCVBYTES Indicates the number of
bytes received on the V-
UNI.
Indicates the number of bytes received on
a V-UNI of a service.
VLAN_RX_BPS Indicates the bit rate (bits/
second) in the receive
direction of a VLAN to
which a V-UNI belongs.
Bit rate = Number of received bytes x 8/
Monitoring period
VLAN_RX_PPS Indicates the packet rate
VLAN to which a V-UNI
belongs.
Packet rate = Number of received
Tunnel
performanc
e
TUNNEL_REVERSE_R
CVPKTS
reverse tunnel.
in the reverse tunnel of a bidirectional
transit tunnel.
TUNNEL_REVERSE_R
CVBYTES
bytes received in the
reverse tunnel.
Indicates the number of bytes received in
the reverse tunnel of a bidirectional
transit tunnel.
TUNNEL_RCVPKTS Indicates the number of
tunnel.
in a tunnel.
TUNNEL_RCVBYTES Indicates the number of
tunnel.
a tunnel.
TUNNEL_REVERSE_R
X_BPS
Indicates the bit rate (bits/
direction of a reverse
tunnel.
Monitoring period
TUNNEL_REVERSE_R
X_PPS
reverse tunnel.
TUNNEL_RX_BPS Indicates the bit rate (bits/
direction of a monitored
object.
Monitoring period
TUNNEL_RX_PPS Indicates the packet rate
monitored object.
912
Performance Entry
Full Name of a
Performance Entry
Remarks
PW
performanc
e of L2VPN
packets received on the
PW.
-
bytes received on the PW.
-
PW_DROPPKTS Indicates the number of
packets discarded on the
PW.
-
PW_RX_BPS Indicates the bit rate (bits/
object.
Monitoring period
PW_RX_PPS Indicates the packet rate
monitored object.
ETH OAM
802.1ag
performanc
e
ETH_CFM_FLR Indicates the E_Line
service packet loss rate.
transmitted by the source MEP - Number
of packets received by the sink MEP)/
Number of packets transmitted by the
source MEP
ETH_CFM_FL Indicates the number of
discarded E_Line service
packets.
OAM.)
ETH_CFM_FD Indicates the E_Line
service delay (s).
MEP sends a request packet - Time when
the source MEP receives the response
packet
ETH_CFM_FDV Indicates the E_Line
service delay variation
(s).
ETH_CFM_FLR_PRIn
NOTE
0 n 7
Indicates the packet loss
rate of the E-Line service
with a priority of n.
source MEP
913
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_CFM_FL_PRIn
NOTE
0 n 7
lost packets in the E-Line
service with a priority of n.
OAM.)
ETH_CFM_FD_PRIn
NOTE
0 n 7
Indicates the delay (s) of
the E-Line service with a
priority of n.
Bidirectional frame delay = Time when
the source sends a request packet - Time
when the source receives the response
packet
ETH_CFM_FDV_PRIn
NOTE
0 n 7
Indicates the delay
variation (s) of the E-
Line service with a
priority of n.
MPLS-TP
OAM
performanc
e
rate on the PW.
MPLS_PW_FLR_N Indicates the packet loss
rate on the PW at the near
end.
number on the PW.
OAM.)
MPLS_PW_FL_N Indicates the number of
lost packets on the PW at
the near end.
OAM.)
(s) on the PW.
variation (s) on the PW.
914
Performance Entry
Full Name of a
Performance Entry
Remarks
MPLS_TUNNEL_FLR Indicates the packet loss
rate in the tunnel.
MPLS_TUNNEL_FLR_
N
rate on the tunnel at the
near end.
MPLS_TUNNEL_FL Indicates the packet loss
number in the tunnel.
OAM.)
MPLS_TUNNEL_FL_N Indicates the number of
lost packets on the tunnel
at the near end.
OAM.)
MPLS_TUNNEL_FD Indicates the frame delay
(s) in the tunnel.
MPLS_TUNNEL_FDV Indicates the frame delay
variation (s) in the
tunnel.
PLA group RXPKTS Indicates the packets
received (packets).
events (times).
RXOCTETS
Indicates the bytes
received (bytes).
not FCS bytes.
packets received
(packets).
915
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
PORT_RX_BW_UTI-
LIZATION
receive direction.
PORT_TX_BW_UTI-
LIZATION
transmit direction.
are excluded.
are excluded.
are excluded.
are excluded.
(packets)
are excluded.
(1024-1518 bytes in
length) (packets)
are excluded.
transmitted
FCS bytes.
frames (frames).
(bytes).
are excluded.
(bytes).
are excluded.
916
Performance Entry
Full Name of a
Performance Entry
Remarks
(bytes).
are excluded.
packets transmitted
(packets).
packets received
(packets).
packets transmitted
(packets).
packets transmitted
(packets).
RXGOODFULLFRAME
SPEED
(kbit/s).
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
are included.
(bytes).
are included.
(bytes).
are included.
transmitted 64-byte
included)
are excluded.
are excluded.
are excluded.
917
Performance Entry
Full Name of a
Performance Entry
Remarks
are excluded.
included)
are excluded.
included)
are excluded.
are excluded.
are excluded.

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 The VUNIs mounted to the E-Line services that are transmitted on the OptiX RTN 950 by exclusively
occupying ports do not support VLAN-based RMON performance statistics.
l Only the SL92CSH board supports MPLS-TP OAM.
C.2.7 CSHU/CSHUA
The RMON performance that the CSHU/CSHUA board supported include L2VPN performance,
Tunnel performance, PW performance of L2VPN, ETH OAM 802.1ag performance, and MPLS-
TP OAM performance.
918
Table C-9 Packet-Plane RMON Performance Entry List (CSHU/CSHUA)
Performance Entry
Full Name of a
Performance Entry
Remarks
L2VPN
a
performanc
e
VLAN_RCVPKTS
packets received at the V-
UNI VLAN. -
VLAN_SNDPKTS Indicates the number of
packets transmitted at the
V-UNI VLAN.
-
VLAN_RCVBYTES Indicates the number of
received at the V-UNI
VLAN.
-
VLAN_SNDBYTES Indicates the number of
transmitted at the V-UNI
VLAN.
-
VUNI_RCVPKTS Indicates the number of
packets received on the V-
UNI.
on a V-UNI of a service.
VUNI_SNDPKTS Indicates the number of
packets transmitted on the
V-UNI.
Indicates the number of packets
transmitted on a V-UNI of a service.
VUNI_RCVBYTES Indicates the number of
bytes received on the V-
UNI.
Indicates the number of bytes received on
a V-UNI of a service.
VUNI_SNDBYTES Indicates the number of
bytes sent on the V-UNI.
Indicates the number of bytes in the
packets transmitted on a V-UNI of a
service.
VLAN_RX_BPS Indicates the bit rate (bits/
Monitoring period
VLAN_TX_BPS Indicates the bit rate (bits/
second) in the transmit
8/Monitoring period
VLAN_RX_PPS Indicates the packet rate
belongs.
919
Performance Entry
Full Name of a
Performance Entry
Remarks
VLAN_TX_PPS Indicates the packet rate
belongs.
Tunnel
performanc
e
TUNNEL_REVERSE_R
CVPKTS
reverse tunnel.
transit tunnel.
TUNNEL_REVERSE_S
NDPKTS
reverse tunnel.
transmitted in the reverse tunnel of a
bidirectional transit tunnel.
TUNNEL_REVERSE_R
CVBYTES
reverse tunnel.
the reverse tunnel of a bidirectional
transit tunnel.
TUNNEL_REVERSE_S
NDBYTES
bytes transmitted in the
reverse tunnel.
Indicates the number of bytes transmitted
transit tunnel.
TUNNEL_RCVPKTS Indicates the number of
tunnel.
in a tunnel.
TUNNEL_SNDPKTS Indicates the number of
tunnel.
transmitted in a tunnel.
TUNNEL_RCVBYTES Indicates the number of
tunnel.
a tunnel.
TUNNEL_SNDBYTES Indicates the number of
bytes transmitted in the
tunnel.
in a tunnel.
TUNNEL_REVERSE_R
X_BPS
tunnel.
Monitoring period
TUNNEL_REVERSE_T
X_BPS
tunnel.
Monitoring period
TUNNEL_REVERSE_R
X_PPS
Indicates the packet rate in
the receive direction of a
reverse tunnel.
920
Performance Entry
Full Name of a
Performance Entry
Remarks
TUNNEL_REVERSE_T
X_PPS
Indicates the packet rate in
the transmit direction of a
reverse tunnel.
TUNNEL_RX_BPS Indicates the bit rate (bits/
object.
Monitoring period
TUNNEL_TX_BPS Indicates the bit rate (bits/
direction of a tunnel.
8/Monitoring period
TUNNEL_RX_PPS Indicates the packet rate in
monitored object.
TUNNEL_TX_PPS Indicates the packet rate in
tunnel.
PW
performanc
e of L2VPN
packets received on the
PW.
-
packets transmitted on the
PW.
transmitted on a PW.
bytes received on the PW.
-
PW_SNDBYTES indicates the number of
bytes transmitted on a PW.
on a PW.
PW_DROPPKTS Indicates the number of
packets discarded on the
PW.
-
PW_RX_BPS Indicates the bit rate (bits/
object.
Monitoring period
PW_TX_BPS Indicates the bit rate (bits/
direction of a PW.
8/Monitoring period
PW_RX_PPS Indicates the packet rate in
monitored object.
921
Performance Entry
Full Name of a
Performance Entry
Remarks
PW_TX_PPS Indicates the packet rate in
PW.
ETH OAM
802.1ag
performanc
e
ETH_CFM_FLR Indicates the E_Line
service packet loss rate.
source MEP
ETH_CFM_FL Indicates the number of
discarded E_Line service
packets.
OAM.)
ETH_CFM_FD Indicates the E_Line
service delay (s).
MEP sends a request packet - Time when
the source MEP receives the response
packet
ETH_CFM_FDV Indicates the E_Line
(s).
ETH_CFM_FLR_PRIn
NOTE
0 n 7
rate of the E-Line service
with a priority of n.
source MEP
ETH_CFM_FL_PRIn
NOTE
0 n 7
lost packets in the E-Line
service with a priority of n.
OAM.)
ETH_CFM_FD_PRIn
NOTE
0 n 7
Indicates the delay (s) of
the E-Line service with a
priority of n.
packet
ETH_CFM_FDV_PRIn
NOTE
0 n 7
Indicates the delay
variation of the E-Line
service with a priority of n
(s).
922
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH OAM
performanc
e (E-LAN)
ETH_CFM_LAN_FLR_
TX
rate of an E-LAN service
at the far end.
source MEP
ETH_CFM_LAN_FL_T
X
lost E-LAN service
packets at the far end.
OAM.)
ETH_CFM_LAN_FLR_
RX
rate of an E-LAN service
at the near end.
transmitted by the sink MEP - Number of
packets received by the source MEP)/
sink MEP
ETH_CFM_LAN_FL_R
X
lost E-LAN service
packets at the near end.
packets transmitted by the sink - Number
of packets received by the source (Both
numbers are detected by the performance
monitoring scheme of OAM.)
ETH_CFM_LAN_FD Indicates the E-LAN
service delay (s).
packet
ETH_CFM_LAN_FDV Indicates the E-LAN
(s).
ETH_CFM_LAN_FPS_T
X
Indicates the number of E-
LAN service packets
transmitted per second at
the far end.
-
ETH_CFM_LAN_FBPS_
TX
bytes in the E-LAN
service packets
the far end.
-
ETH_CFM_LAN_FPS_R
X
Indicates the number of E-
LAN service packets
received per second at the
near end.
-
923
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_CFM_LAN_FBPS_
RX
bytes in the E-LAN
service packets received
per second at the near end.
-
ETH_CFM_FLR_TX_M
AX
packet loss rate of an E-
LAN service at the far end.
The maximum packet loss rate is the
largest value among the packet loss rates
calculated over a monitoring period.
source MEP
ETH_CFM_FLR_TX_MI
N
The minimum packet loss rate is the
smallest value among the packet loss
rates calculated over a monitoring period.
source MEP
ETH_CFM_FLR_TX_A
VG
The average packet loss rate is the
average value of the packet loss rates
source MEP
ETH_CFM_FLR_RX_M
AX
LAN service at the near
end.
The maximum packet loss rate is the
largest value among the packet loss rates
sink MEP
ETH_CFM_FLR_RX_M
IN
end.
The minimum packet loss rate is the
smallest value among the packet loss
rates calculated over a monitoring period.
sink MEP
924
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_CFM_FLR_RX_A
VG
end.
The average packet loss rate is the
average value of the packet loss rates
sink MEP
ETH_CFM_LAN_FPS_T
X_MAX
number of E-LAN service
packets transmitted per
second at the far end.
-
ETH_CFM_LAN_FPS_T
X_MIN
-
ETH_CFM_LAN_FPS_T
X_AVG
-
ETH_CFM_LAN_FBPS_
TX_MAX
number of bytes in the E-
LAN service packets
the far end.
-
ETH_CFM_LAN_FBPS_
TX_MIN
LAN service packets
the far end.
-
ETH_CFM_LAN_FBPS_
TX_AVG
LAN service packets
the far end.
-
ETH_CFM_LAN_FPS_R
X_MAX
packets received per
second at the near end.
-
925
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_CFM_LAN_FPS_R
X_MIN
-
ETH_CFM_LAN_FPS_R
X_AVG
-
ETH_CFM_LAN_FBPS_
RX_MAX
LAN service packets
near end.
-
ETH_CFM_LAN_FBPS_
RX_MIN
LAN service packets
near end.
-
ETH_CFM_LAN_FBPS_
RX_AVG
LAN service packets
near end.
-
ETH_CFM_LAN_FD_M
AX
Indicates the maximum E-
LAN service delay (s).
Indicates the maximum bidirectional
frame delay.
ETH_CFM_LAN_FD_M
IN
Indicates the minimum E-
Indicates the minimum bidirectional
frame delay.
ETH_CFM_LAN_FD_A
VG
Indicates the average E-
Indicates the average bidirectional frame
delay.
ETH_CFM_LAN_FDV_
MAX
Indicates the maximum E-
LAN service delay
variation (s).
The largest value among the frame delay
variations calculated over a monitoring
period (Frame delay variation is the
different between two frame delay test
results.)
ETH_CFM_LAN_FDV_
MIN
Indicates the minimum E-
LAN service delay
variation (s).
The smallest value among the frame
delay variations calculated over a
monitoring period (Frame delay
variation is the different between two
frame delay test results.)
926
Performance Entry
Full Name of a
Performance Entry
Remarks
ETH_CFM_LAN_FDV_
AVG
Indicates the average E-
LAN service delay
variation (s).
The average value among the frame delay
variations calculated over a monitoring
period (Frame delay variation is the
different between two frame delay test
results.)
MPLS-TP
OAM
performanc
e
rate on the PW.
MPLS_PW_FLR_N Indicates the packet loss
rate of the PW at the near
end.
number on the PW.
OAM.)
MPLS_PW_FL_N Indicates the number of
lost packets on the PW at
the near end.
OAM.)
(s) on the PW.
variation (s) on the PW.
MPLS_TUNNEL_FLR Indicates the packet loss
rate in the tunnel.
transmitted by the source tunnel -
tunnel)/Number of packets transmitted
by the source tunnel
MPLS_TUNNEL_FLR_
N
rate in the tunnel at the
near end.
transmitted by the source tunnel -
tunnel)/Number of packets transmitted
by the source tunnel
927
Performance Entry
Full Name of a
Performance Entry
Remarks
MPLS_TUNNEL_FL Indicates the packet loss
number in the tunnel.
OAM.)
MPLS_TUNNEL_FL_N Indicates the number of
lost packets in the tunnel at
the near end.
OAM.)
MPLS_TUNNEL_FD Indicates the frame delay
(s) in the tunnel.
tunnel sends a request packet - Time
when the source tunnel receives the
response packet
MPLS_TUNNEL_FDV Indicates the frame delay
variation (s) in the
tunnel.
PLA group RXPKTS Indicates the packets
received (packets).
events (times).
RXOCTETS
Indicates the bytes
received (bytes).
not FCS bytes.
packets received
(packets).
packets received
(packets).
PORT_RX_BW_UTI-
LIZATION
receive direction.
928
Performance Entry
Full Name of a
Performance Entry
Remarks
PORT_TX_BW_UTI-
LIZATION
transmit direction.
are excluded.
are excluded.
are excluded.
are excluded.
(packets)
are excluded.
(1024-1518 bytes in
length) (packets)
are excluded.
transmitted
FCS bytes.
frames (frames).
(bytes).
are excluded.
(bytes).
are excluded.
(bytes).
are excluded.
packets transmitted
(packets).
929
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
packets transmitted
(packets).
packets transmitted
(packets).
RXGOODFULLFRAME
SPEED
(kbit/s).
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
are included.
(bytes).
are included.
(bytes).
are included.
transmitted 64-byte
included)
are excluded.
are excluded.
are excluded.
are excluded.
930
Performance Entry
Full Name of a
Performance Entry
Remarks
included)
are excluded.
included)
are excluded.
are excluded.
are excluded.
NMS port RXPKTS Indicates the number of
received packets.
Corrupted packets, broadcast packets,
and multicast packets are included.
RXOCTETS
bytes in received packets
(including corrupted
packets).
are excluded.
RXMULCAST Indicates the number of
error-free multicast
packets received.
Broadcast packets are excluded.
RXBRDCAST Indicates the number of
error-free broadcast
packets received.
Multicast packets are excluded.
PORT_RX_BW_UTI-
LIZATION
receive direction.
Bandwidth utilization on a port in the
receive direction = (Number of received
bytes x 8/Monitoring period)/Configured
or actual bandwidth
PORT_TX_BW_UTI-
LIZATION
transmit direction.
Bandwidth utilization on a port in the
transmit direction = (Number of received
bytes x 8/Monitoring period)/Configured
or actual bandwidth
931
Performance Entry
Full Name of a
Performance Entry
Remarks
RXPKT64 Indicates the number of
length of 64 bytes
(including FCS bytes but
excluding framing bits).
Corrupted packets are included.
bytes (including FCS
bytes but excluding
framing bits).
(MTU) bytes (including
FCS bytes but excluding
framing bits).
TXPKTS Indicates the number of
transmitted packets.
Corrupted packets, broadcast packets,
and multicast packets are included.
TXOCTETS Indicates the number of
bytes in transmitted
packets (including
corrupted packets).
are excluded.
TXBGOOD Indicates the number of
bytes in error-free packets
transmitted.
are excluded.
932
Performance Entry
Full Name of a
Performance Entry
Remarks
RXBGOOD Indicates the number of
bytes in error-free packets
received.
are excluded.
TXUNICAST Indicates the number of
unicast packets
transmitted.
The packets that are dropped and fail to
be transmitted are included.
RXUNICAST Indicates the number of
error-free unicast packets
received.
Only error-free packets are included.
TXMULCAST Indicates the number of
multicast packets
transmitted.
TXBRDCAST Indicates the number of
broadcast packets
transmitted.
RXGOODFULLFRAME
SPEED
Indicates the rate of
receiving error-free full-
frame bits (kbit/s).
FCS bytes and framing bits are included.
TXGOODFULLFRAME
SPEED
transmitting error-free
full-frame bits (kbit/s).
RXFULLBGOOD Indicates the number of
error-free full-frame bytes
received.
TXFULLBGOOD Indicates the number of
error-free full-frame bytes
transmitted.
TXPKT64 Indicates the number of
length of 64 bytes
933
Performance Entry
Full Name of a
Performance Entry
Remarks
bytes but excluding
framing bits).
bytes but excluding
framing bits).
length of 1519 bytes to the
MTU (including FCS
bytes but excluding
framing bits).
length of 1519 bytes to the
MTU (including FCS
bytes but excluding
framing bits).
ETHUNDER Indicates the number of
received packets that are
undersized but error-free.
An undersized packet has less than 64
bytes (including FCS bytes but excluding
framing bits).
ETHOVER Indicates the number of
received packets that are
oversized but error-free.
An oversized packet has more than 1518
bytes (including FCS bytes but excluding
framing bits).
934
Performance Entry
Full Name of a
Performance Entry
Remarks
RX_DROP_RATIO Indicates the packet loss
rate in the receive
direction.
Packet loss rate in the receive direction =
Number of discarded packets/Total
number of received packets
TX_DROP_RATIO Indicates the packet loss
rate in the transmit
direction.
Packet loss rate in the transmit direction
= Number of discarded packets/Total
number of transmitted packets

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 The VUNIs mounted to the E-Line services that are transmitted on the OptiX RTN 950 by exclusively
occupying ports do not support VLAN-based RMON performance statistics.
C.2.8 EFP8/EMS6
The Packet-Plane RMON performance that the EFP8/EMS6 board supported include basic
performance and extended performance.
The EFP8 board's bridging port PORT10 is on the Packet-Plane.
The EMS6 board's bridging port PORT8 is on the Packet-Plane.
Table C-10 Packet-Plane RMON Performance Entry List (EFP8/EMS6)
Performance Entry
Full Name of a
Performance Entry
Remarks
Basic
performanc
e
RXPKTS
received (packets).
events (times).
received (bytes).
not FCS bytes.
NOTE
If the packets received by an EFP8/EMS6
board are larger than the MTU, byte count is
calculated based on MTU.
935
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
packets received
(packets).
packets received
(packets).
Oversized packets are the packets larger
than MTU (including FCS bytes but not
framing bits).
NOTE
For the EFP8/EMS6 board, an oversized
packet is larger than the MTU.
(packets).
alignment errors.
NOTE
For the EFP8/EMS6 board, an oversized error
packet is larger than the MTU.
Extended
performanc
e
frames (frames).
NOTE
For the EFP8/EMS6 board, this count dose
not include undersized frames and oversized
frames.
(bytes).
FCS bytes are included but framing bits
are excluded.
(bytes).
are excluded.
(bytes).
are excluded.
packets transmitted
(packets).
936
Performance Entry
Full Name of a
Performance Entry
Remarks
packets received
(packets).
packets transmitted
(packets).
packets transmitted
(packets).
RXGOODFULLFRAME
SPEED
(Kbit/s).
are included.
TXGOODFULLFRAME
SPEED
full-frame bytes
transmitted (Kbit/s).
are included.
(bytes).
are included.
(bytes).
are included.
RXPAUSE Indicates the pause frames
received (frames).
PAUSE opcode.
TXPAUSE Indicates the pause frames
transmitted (frames).
PAUSE opcode.

C.3 RMON Performance Entries List on the EoS/EoPDH-
Plane
This section lists RMON performance entries on the EoS/EoPDH plane by board type.
C.3.1 EFP8
The EFP8 board The RMON performance that the EFP8 Board supported include basic
performance, extended performance, and VCG performance.
The EFP8 board's Ethernet ports PORT1 to PORT8, bridging port PORT9, and internal ports
VCTRUNK1 to VCTRUNK16 are on the EoPDH plane.
937
Table C-11 EoPDH plane RMON Performance Entry List (EFP8)
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
Basic
performa
nce
received (bytes).
RXOCTETS indicates the total
number of bytes in received packets
(including bad packets), including
framing bits but not FCS bytes.
PORT1 to
PORT9
packets received
(packets).
RXBRDCAST indicates the total
number of received good packets
with broadcast destination
addresses, excluding multicast
packets.
RXMULCAST Indicates the broadcast
packets received
(packets).
with multicast destination
addresses, excluding broadcast
packets.
packets received
(packets).
Oversized packets are the packets
larger than MTU (including FCS
received (packets).
(packets).
framing bits) and contain FCS errors
or alignment errors.
that have FCS check
errors-
-
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.
PORT1 to
PORT8
ETHFRG Fragments received
(packets)
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.
938
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
RXPKT64 Packets received (64
bytes in length)
(packets)
FCS bytes are included but framing
bits are excluded.
PORT1 to
PORT9
(65-127 bytes in
length) (packets)
bits are excluded.
(128-255 bytes in
length) (packets)
bits are excluded.
(256-511 bytes in
length) (packets)
bits are excluded.
(512-1023 bytes in
length) (packets)
bits are excluded.
(1024-1518 bytes in
length) (packets)
bits are excluded.
Extended
performa
nce
RXCTLPKTS Control frames
received (frames)
- PORT1 to
PORT9
TXOCTETS Bytes transmitted
(bytes)
Indicates the total number of bytes
(including those in bad packets)
transmitted (including FCS bytes
but not framing bits).
TXPKTS Packets transmitted
(packets)
TXCTLPKTS Control frames
transmitted (frame)
-
TXPKT64 Packets transmitted
(64 bytes in length)
(packets)
bits are excluded.
(65-127 bytes in
length) (packets)
bits are excluded.
(128-255 bytes in
length) (packets)
bits are excluded.
939
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
(256-511 bytes in
length) (packets)
bits are excluded.
(512-1023 bytes in
length) (packets)
bits are excluded.
(1024-1518 bytes in
length) (packets)
bits are excluded.
ETHALI Alignment error
frames (frames)
An alignment error frame contains a
fractional number of bytes and fails
PKT64 Packets received and
transmitted (64 bytes in
length) (packets)
bits are excluded.
transmitted (65-127
bytes in length)
(packets)
bits are excluded.
transmitted (128-255
bytes in length)
(packets)
bits are excluded.
bytes in length)
(packets)
bits are excluded.
bytes in length)
(packets)
bits are excluded.
transmitted
(1024-1518 bytes in
length) (packets)
bits are excluded.
ETH_RX_THROUG
HPUT_MAX
Indicates the
maximum throughput
at a port in the receive
direction.
received bytes (including inter-
frame gaps and preambles)/
Monitoring period
940
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
ETH_RX_THROUG
HPUT_MIN
throughput at a port in
the receive direction.
Monitoring period
ETH_RX_THROUG
HPUT_AVG
throughput at a port in
the receive direction.
Monitoring period
RXGOODFULLFRA
MESPEED
good full-frame bits
received (Kbit/s).
Framing bits (20 bytes) and FCS
bytes are included.
TXGOODFULLFRA
MESPEED
bytes are included.
(bytes).
bytes are included.
frame bytes
transmitted (bytes).
bytes are included.
packets transmitted
(packets).
The multicast packets that are
discarded or fail to be transmitted
are included.
packets received
(packets).
RXUNICAST indicates the number
of good unicast packets.
packets transmitted
(packets).
The unicast packets that are
are included.
packets transmitted
(packets).
The broadcast packets that are
are included.
RXPAUSE Indicates the pause
frames received
(frames).
PAUSE opcode.
TXPAUSE Indicates the pause
frames transmitted
(frames).
PAUSE opcode.
VCG
performa
nce
VCG_TXGOODPAC
KETS
Good packets
transmitted (packets)
- VCTRU
NK1 to
941
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
VCG_TXPACKETS VCTRU
NK16
Packets transmitted
(packets)
VCG_TXOCTETS Bytes transmitted
(bytes)
Bad packets are included (FCS bytes
are included but framing bits are
excluded).
VCG_RXGOODPAC
KETS
Good packets received
(packets)
-
VCG_RXPACKETS Packets received
(packets)
VCG_RXOCTETS Bytes received (bytes) Bad packets are included (FCS bytes
excluded).
VCG_TXSPEED Speed of bytes
transmitted (bytes)
excluded).
VCG_RXSPEED Speed of bytes
received (bytes)
excluded).

C.3.2 EMS6
The RMON performance that the EMS6 Board supported include basic performance, extended
performance, and VCG performance.
The EMS6 board's Ethernet ports PORT1 to PORT6, bridging port PORT7, and internal ports
VCTRUNK1 to VCTRUNK8 are on the EoS plane.
Table C-12 EoS plane RMON Performance Entry List (EMS6)
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
Basic
performa
nce
received (bytes).
RXOCTETS indicates the total
number of bytes in received packets
(including bad packets), including
framing bits but not FCS bytes.
PORT1 to
PORT7
packets received
(packets).
RXBRDCAST indicates the total
with broadcast destination
addresses, excluding multicast
packets.
942
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
RXMULCAST Indicates the broadcast
packets received
(packets).
with multicast destination
addresses, excluding broadcast
packets.
packets received
(packets).
Oversized packets are the packets
larger than MTU (including FCS
received (packets).
(packets).
framing bits) and contain FCS errors
or alignment errors.
that have FCS check
errors-
-
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.
ETHFRG Fragments received
(packets)
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.
RXPKT64 Packets received (64
bytes in length)
(packets)
bits are excluded.
(65-127 bytes in
length) (packets)
bits are excluded.
(128-255 bytes in
length) (packets)
bits are excluded.
(256-511 bytes in
length) (packets)
bits are excluded.
943
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
(512-1023 bytes in
length) (packets)
bits are excluded.
(1024-1518 bytes in
length) (packets)
bits are excluded.
ETHALI The number of
alignment error frames
An alignment error frame contains a
fractional number of bytes and fails
PORT3 to
PORT6
Extended
performa
nce
RXCTLPKTS Control frames
received (frames)
- PORT1 to
PORT7
TXOCTETS Bytes transmitted
(bytes)
Indicates the total number of bytes
(including those in bad packets)
transmitted (including FCS bytes
but not framing bits).
TXPKTS Packets transmitted
(packets)
TXCTLPKTS Control frames
transmitted (frame)
-
(64 bytes in length)
(packets)
bits are excluded.
(65-127 bytes in
length) (packets)
bits are excluded.
(128-255 bytes in
length) (packets)
bits are excluded.
(256-511 bytes in
length) (packets)
bits are excluded.
(512-1023 bytes in
length) (packets)
bits are excluded.
(1024-1518 bytes in
length) (packets)
bits are excluded.
944
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
transmitted (64 bytes in
length) (packets)
bits are excluded.
transmitted (65-127
bytes in length)
(packets)
bits are excluded.
bytes in length)
(packets)
bits are excluded.
bytes in length)
(packets)
bits are excluded.
bytes in length)
(packets)
bits are excluded.
transmitted
(1024-1518 bytes in
length) (packets)
bits are excluded.
RXGOODFULLFRA
MESPEED
received (Kbit/s).
bytes are included.
TXGOODFULLFRA
MESPEED
bytes are included.
(bytes).
bytes are included.
frame bytes
transmitted (bytes).
bytes are included.
packets transmitted
(packets).
The multicast packets that are
are included.
945
Categor
y
Brief Name of a
Performance Entry
Full Name of a
Performance Entry
Remarks Source
Port
packets received
(packets).
RXUNICAST indicates the number
of good unicast packets.
packets transmitted
(packets).
The unicast packets that are
are included.
packets transmitted
(packets).
The broadcast packets that are
are included.
RXPAUSE Indicates the pause
frames received
(frames).
PAUSE opcode.
TXPAUSE Indicates the pause
frames transmitted
(frames).
PAUSE opcode.
VCG
performa
nce
VCG_TXGOODPAC
KETS
Good packets
transmitted (packets)
- VCTRU
NK1 to
VCTRU
NK8
VCG_TXPACKETS Packets transmitted
(packets)
VCG_TXOCTETS Bytes transmitted
(bytes)
excluded).
VCG_RXGOODPAC
KETS
Good packets received
(packets)
-
VCG_RXPACKETS Packets received
(packets)
VCG_RXOCTETS Bytes received (bytes) Bad packets are included (FCS bytes
excluded).
VCG_TXSPEED Speed of bytes
transmitted (bytes)
excluded).
VCG_RXSPEED Speed of bytes
received (bytes)
excluded).

946
C.4 RMON Events and Handling Procedures
This chapter describes the RMON events that indicate Ethernet service abnormalities and how
to handle these events.
C.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
For the ISV3 board, ETHDROP counts packet loss events caused by congestion.
For the ISU2 and ISX2 boards, ETHDROP counts packet loss events caused by exceptions or congestion.
For other boards, ETHDROP counts packet loss events caused by insufficient Ethernet chip resources, but
does not count packet loss events caused by link congestion and other reasons.
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 The lower threshold is not set to a non-zero value.
l The hardware at the local end is faulty.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower
threshold
Change the lower threshold to 0.
The number is higher than the upper
threshold
Manually decrease the traffic transmitted from
the opposite end. If the problem persists, go to
the next step.
Step 2 Replace the involved part.
----End
947
Reference
None.
C.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 half-
duplex mode.
Procedure
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends
work in inconsistent modes, or any port
works in half-duplex mode
Set the working modes of the ports on the
equipment at both ends to full-duplex or auto-
negotiation, so that these ports work in
consistent modes.
work in consistent modes and no ports work
in half-duplex mode
----End
Reference
None.
948
C.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
If... Then...
If... Then...
consistent modes.
in half-duplex mode
Step 3 Check whether the network diameter of the LAN is very large according to the networking
If... Then...
The network diameter is very large 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.
949
----End
Reference
None.
C.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. Errors occur when the opposite end transmits packets.
2. The transmission line is of the poor quality and bit errors exist.
3. The hardware at the local end is faulty.
Procedure
If... Then...
Step 2 Correct the errors that occur when the opposite end transmits packets.
Step 3 Handle the problem of poor quality of the transmission line.
Check whether the ETH_LOS alarm is reported at the local end because the external line is
damaged or over attenuated. If yes, see the related handling method to clear the alarm.
----End
Reference
None.
950
C.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
If... Then...
If... Then...
consistent modes.
in half-duplex mode
----End
Reference
None.
951
C.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. The length of a data frame that is received at a port is shorter than 64 bytes.
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
that is shorter than 64 bytes
Rectify the fault on the opposite equipment.
The opposite end does not transmit the
packet that is shorter than 64 bytes
----End
Reference
None.
C.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.
952
Possible Causes
1. The preset maximum frame length is less than the length of the frame that is received at a
port.
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... Then...
The opposite equipment transmits the
packet that is longer than the maximum
frame length set for the local equipment
Notify the opposite equipment that the length
of transmitted frames should be changed.
The opposite equipment does not transmit
the packet that is longer than the maximum
frame length set for the local equipment
----End
Reference
None.
C.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 The working modes of the ports on the equipment at both ends are not consistent.
l The ports on the equipment at both ends work in half-duplex mode, and the data traffic is
very heavy.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
953
If... Then...
The working modes are consistent Go to the next step.
The working modes are not consistent Change the working mode of the local port so 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 half-
duplex mode.
If... Then...
The working modes are not set to the half-
duplex mode
The working modes are set to the half-
duplex mode
Change the working modes of the ports on the
equipment at both ends to the full-duplex mode
or adaptive mode.
----End
C.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 The working modes of the ports on the equipment at both ends are not consistent.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... Then...
The working modes are consistent Go to the next step.
The working modes are not consistent Change the working mode of the local port so that
the ports on the equipment at both ends work in
consistent modes.
----End
954
C.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
If... Then...
If... Then...
consistent modes.
in half-duplex mode
----End
Reference
None.
955
C.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. The local port and opposite port work in inconsistent modes. For example, one port works
in full-duplex mode, and the opposite port works in half-duplex mode.
2. The transmission line is of the poor quality and bit errors exist.
Procedure
Step 1 Therefore, handle the alarm according to the specific performance event.
If... Then...
If... Then...
work in inconsistent modes
Change the working modes of the ports on the
equipment at both ends so that they can work
in consistent modes
work in consistent modes
----End
Reference
None.
956
C.4.12 ATMPW_LOSPKTS
Description
The ATMPW_LOSPKTS is a performance event indicating the number of lost ATM PW
packets.
None.
Possible Causes
1. Signals on the radio link deteriorate.
2. A strong interference source is present near the equipment.
3. A board at the transmit or receive end is faulty.
4. The operating temperature of the equipment is very high.
Procedure
Step 1 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Remove the interference source near the equipment and then check whether the performance
event is cleared.
Step 4 Replace the faulty board and then check whether the performance event is cleared.
Step 5 Rectify the fault in the fan so that the fan lowers the operating temperature of the equipment.
----End
Related Information
None.
C.4.13 ATMPW_MISORDERPKTS
Description
The ATMPW_MISORDERPKTS is a performance event indicating the number of disordered
ATM PW packets.
None.
Possible Causes
957
Procedure
event is cleared.
----End
Related Information
None.
C.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
event is cleared.
958
----End
Related Information
None.
C.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
Procedure
event is cleared.
----End
Related Information
None.
C.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.
959
Possible Causes
Procedure
Step 1 Refer to 5.3 Troubleshooting the Radio Link and handle the fault on the radio link.
event is cleared.
----End
Related Information
None.
C.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. Signals degrade on the link.
2. The link is looped.
3. The link is congested.
Related Alarms
CES_MISORDERPKT_EXC
Procedure
Step 1 See 5.3 Troubleshooting the Radio Link.
Step 2 Release the loop.
960
Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
----End
Related Information
None.
C.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.
C.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.
961
Possible Causes
1. The RTP head enabling status is different between the two ends of the PW.
2. 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.
C.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. Signals degrade on the link.
2. The PSN network clocks used for the transmission of CES services are not synchronized.
3. The link is looped.
4. The link is congested.
5. The size of buffer area is set to a low value.
Related 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.
962
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.
C.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. The jitter buffer area is too small.
2. The clocks are not synchronous.
3. Link quality deteriorates, causing more jitters.
4. There are too many hops of radio link on the network side, causing a large number of jitters.
Related 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 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.
963
C.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. The link transmission quality is poor.
2. The link is configured as a loop.
3. Link congestion occurs.
Related Alarms
CES_LOSPKT_EXC
Procedure
----End
Related Information
None.
964
D Alarm Management
The alarm management on the OptiX RTN 950 is classified into the NE alarm management and
board alarm management.
D.1 NE Alarm Management
The NE alarm management function set by user is applicable to all the boards on the NE.
D.2 Board Alarm Management
The board alarm management function is only applicable to the board on which users have
configured this function.
Maintenance Guide D Alarm Management
965
D.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 Settings of the alarm storage mode
l Setting of the alarm delay
l Setting of the alarm reversion mode
For details about these functions, see the manuals or online Help of the NMS.
D.2 Board Alarm Management
The board alarm management function is only applicable to the board on which users have
configured this function.
D.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.
l 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.
l 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.
l 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.
D.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.
966
D.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
alarm query is performed on the NMS. The maintenance personnel can change the setting on
the NMS.
D.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 (Disable)
In this mode, the alarms are monitored by default and alarm reversion cannot be enabled
for a port.
l Auto restore
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 restore
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 For OptiX RTN 950, only R_LOS, T_ALOS, MW_LOF, ETH_LOS, and LAN_LOC
alarms support alarm reversion.
l Alarm reversion is set based on ports. Configurations are required at both the NE level and
the port level.
l Alarm reversion does not change the actual status of alarms on the board, as well as the
indication status of the alarm indicators.
l 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.
D.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
967
of this threshold is supported by all the bit error threshold-crossing and degrading alarms on the
NE.
Table D-1 Setting of the bit error alarm threshold
Alarm Name Default Alarm Threshold Applicable Board
B1_EXC
10
-3
ISV3, ISX2, ISU2, SL1DA,
SL1D, IF1
B1_SD
10
-6
B2_EXC
10
-3
SL1D, IF1
B2_SD
10
-6
B3_EXC
10
-3
SL1D, IF1
B3_SD
10
-6
BIP_EXC
10
-3
ISV3, ISU2, ISX2, EFP8,
EMS6, SP3S, SP3D, IFU2,
IFX2
BIP_SD
10
-6
MW_BER_EXC
10
-3
IFX2
MW_BER_SD
10
-6

D.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 D-2 Setting of the AIS insertion
Trigger Condition Default Value Applicable Board
B1_EXC Enabled ISV3, ISX2, ISU2, IF1,
SL1D, SL1DA
B2_SD Disabled
B2_EXC Disabled
HP_LOM Enabled
HP_TIM Disabled
HP_SLM Disabled
HP_UNEQ Disabled
B3_EXC Enabled
B3_SD Disabled
968
B1_SD Disabled
LP_TIM Disabled SP3S and SP3D
LP_UNEQ Disabled
LP_SLM Disabled
BIP_EXC Disabled
MW_BER_EXC Enabled ISV3, ISU2, ISX2, IFX2 and
IFU2
MW_BER_SD Disabled

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 IFX2 and IFU2 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it forcibly inserts
the AIS.
D.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 D-3 Setting of the UNEQ insertion
T_ALOS Disabled SP3S and SP3D
Service path being not in use Disabled
969
E Performance Event Management
The performance event management is classified into the NE performance event management
and board performance event management.
E.1 NE Performance Event Management
The NE performance event management function set by user is applicable to all the boards on
the NE.
E.2 Board Performance Event Management
The performance event management function is only applicable to the board on which users
have configured this function.
Maintenance Guide E Performance Event Management
970
E.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 Setting NE performance event monitoring
l Setting the start/end time of performance events
l Enabling/Disabling the reporting of UAT events
For details about these functions, see the manuals or online Help of the NMS.
E.2 Board Performance Event Management
The performance event management function is only applicable to the board on which users
have configured this function.
Table E-1 Board performance event management function
Function Applicable Board
Setting 15-minute/24-
hour performance
monitoring
ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, CST, CSU,
CSHU, CSHUA, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1,
EFP8, IF1
Setting 15-minute/24-
hour performance event
auto-reporting
ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, CST, CSU,
CSHU, CSHUA, ODU, IFX2, IFU2, ISU2, ISX2, ML1, MD1,
EFP8, IF1
Setting performance
thresholds
ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2,
ISU2, ISX2, ML1, MD1, EFP8, IF1
Resetting the
performance register
ISV3, SL1DA, SL1D, SP3S, SP3D, ODU, IFX2, IFU2, ISU2,
ISX2, IF1
Generating performance
threshold-crossing
alarms
ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, ODU, IFX2,
IFU2, ISU2, ISX2, ML1, MD1, EFP8, IF1
Monitoring UAT events ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2,
ISU2, ISX2, EFP8, IF1
Monitoring CSES
performance events
ISV3, CQ1, SL1DA, EMS6, SL1D, SP3S, SP3D, IFX2, IFU2,
ISU2, ISX2, EFP8, IF1
Maintenance Guide E Performance Event Management
971
F 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 inter-
board alarms.
F.1 Alarm Suppression on TDM Plane
This section describes the alarm suppression relationship for SDH/PDH signals and IF signals
on the TDM plane.
F.2 Alarm Suppression on Data Plane
This section describes the alarm suppression relationship for Ethernet, MPLS tunnel, PW, ATM/
IMA, PPP/MLPPP, and EoS/EoPDH services.
Maintenance Guide F Alarm Suppression Relationship
972
F.1 Alarm Suppression on TDM Plane
This section describes the alarm suppression relationship for SDH/PDH signals and IF signals
on the TDM plane.
Intra-board Alarm Suppression on TDM Plane
Table F-1 Suppression relationship between intra-board alarms (IF1 board)
Root Alarm Suppressed Alarm
MW_LOF R_LOS, R_LOC, MW_FEC_UNCOR, R_LOF, MW_LIM,
MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS, MS_RDI,
MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ,
HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI
MW_LIM MW_RDI
R_LOC R_LOF, MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD,
MS_AIS, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
HP_UNEQ, HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI
R_LOF MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS,
MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
MS_AIS MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
B1_EXC B1_SD, MS_REI
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,
HP_RDI, HP_LOM, HP_REI
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM, HP_RDI,
HP_LOM, HP_REI
B3_EXC B3_SD
HP_UNEQ HP_TIM

Table F-2 Suppression relationship between intra-board alarms (IFU2/IFX2/ISU2/ISX2/ISV3
board, E1+Ethernet service mode)
MW_LOF R_LOC, R_LOF, MW_LIM, MW_RDI, MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR, MW_E1_LOST
973
R_LOC R_LOF, MW_LIM, MW_RDI, MW_BER_EXC, MW_BER_SD
R_LOF MW_LIM, MW_RDI, MW_BER_EXC, MW_BER_SD,
MW_E1_LOST
MW_BER_E
XC
MW_BER_SD
TU_AIS TU_LOP, LP_TIM, LP_UNEQ, LP_RDI, LP_REI, BIP_EXC,
BIP_SD
TU_LOP LP_TIM, LP_UNEQ, LP_RDI, LP_REI, BIP_EXC, BIP_SD,
LP_UNEQ LP_RDI, LP_RFI
LP_RDI LP_REI
BIP_EXC BIP_SD

Table F-3 Suppression relationship between intra-board alarms (ISU2/ISX2/ISV3 board,
STM-1+Ethernet service mode)
MW_LOF R_LOC, MW_FEC_UNCOR, R_LOF, MW_LIM, MW_RDI,
B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS, MS_RDI, MS_REI,
AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM,
HP_SLM, HP_RDI, HP_LOM, HP_REI, MW_E1_LOST
MW_LIM MW_RDI
R_LOC R_LOF, MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD,
MS_AIS, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
R_LOF MW_LIM, MW_RDI, B1_EXC, B1_SD, B2_EXC, B2_SD, MS_AIS,
HP_UNEQ, HP_TIM, HP_SLM, HP_RDI, HP_LOM, HP_REI,
MW_E1_LOST
MS_AIS MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD,
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM,
HP_RDI, HP_LOM, HP_REI
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_SLM, HP_RDI,
HP_LOM, HP_REI
974
B3_EXC B3_SD
HP_UNEQ HP_TIM

Table F-4 Suppression relationship between intra-board alarms (SL1D/SL1DA board)
LSR_NO_FIT
ED
R_LOS, R_LOC, R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS,
B2_EXC, B2_SD, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC,
B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM,
HP_LOM, IN_PWR_LOW, IN_PWR_HIGH, LASER_CLOSED,
LASER_MOD_ERR_EX, TF, OUT_PWR_ABN
R_LOS R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD,
HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM,
IN_PWR_LOW
R_LOC R_LOF, J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD,
HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM
R_LOF J0_MM, B1_EXC, B1_SD, MS_AIS, B2_EXC, B2_SD, MS_RDI,
MS_REI, AU_AIS, AU_LOP, B3_EXC, B3_SD, HP_UNEQ,
HP_TIM, HP_RDI, HP_REI, HP_SLM, HP_LOM
MS_AIS B2_EXC, B2_SD, MS_RDI, MS_REI, AU_AIS, AU_LOP, B3_EXC,
B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI, HP_SLM,
HP_LOM
MS_RDI MS_REI
AU_AIS AU_LOP, B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_RDI,
HP_REI, HP_SLM, HP_LOM
AU_LOP B3_EXC, B3_SD, HP_UNEQ, HP_TIM, HP_RDI, HP_REI,
HP_SLM, HP_LOM
HP_UNEQ HP_TIM, HP_RDI, HP_LOM
HP_RDI HP_REI
B3_EXC B3_SD

975
Table F-5 Suppression relationship between intra-board alarms (SP3S/SP3D board)
TU_AIS TU_LOP, LP_SLM, DOWN_E1_AIS, LP_R_FIFO, LP_UNEQ,
LP_TIM, LP_RFI, LP_RDI, LP_REI, BIP_EXC, BIP_SD
TU_LOP LP_SLM, DOWN_E1_AIS, LP_R_FIFO, LP_UNEQ, LP_TIM,
LP_RFI, LP_RDI, LP_REI, BIP_EXC, BIP_SD
LP_UNEQ LP_TIM, LP_RFI, LP_RDI, BIP_EXC, BIP_SD
LP_RDI LP_REI
BIP_EXC BIP_SD
T_ALOS E1_LOS, UP_E1_AIS, DDN_LFA
E1_LOS UP_E1_AIS
UP_E1_AIS DDN_LFA

Table F-6 Suppression relationship between intra-board alarms (CST/CSH/CSHU/CSHUA
board)
PG_LINK_F
AIL
PG_PRT_DEGRADED

Inter-board Alarm Suppression on TDM Plane
The inter-board alarm suppression means that, when services are configured between two boards
on the same NE, the service alarm generated by the source board suppresses the service alarm
generated by the sink board. The TDM plane supports alarm suppression between line/IF boards
and tributary boards.
Table F-7 Inter-board Alarm Suppression on TDM Plane
R_LOS, R_LOC, MS_AIS, AU_AIS,
AU_LOP, R_LOF
TU_AIS
MW_LOF, MW_LIM TU_AIS

F.2 Alarm Suppression on Data Plane
This section describes the alarm suppression relationship for Ethernet, MPLS tunnel, PW, ATM/
IMA, PPP/MLPPP, and EoS/EoPDH services.
976
Intra-board Alarm Suppression on Data Plane
Table F-8 Suppression relationship between intra-board alarms (Ethernet Port)
LSR_NO_FIT
ED
LASER_SHUT, ETH_LOS, TF, LSR_WILL_DIE, OUT_PWR_ABN
LASER_MO
D_ERR
LASER_SHUT, IN_PWR_ABN, OUT_PWR_ABN,
LSR_BCM_ALM, TEM_HA, TEM_LA, ETH_LOS, TF,
LSR_WILL_DIE
LASER_SHU
T
LSR_BCM_ALM, LSR_WILL_DIE, OUT_PWR_ABN
TF OUT_PWR_ABN, LSR_WILL_DIE
ETH_EFM_D
F
ETH_EFM_REMFAULT
ETH_EFM_R
EMFAULT
ETH_EFM_EVENT

Table F-9 Suppression relationship between intra-board alarms (MPLS Tunnel)
MPLS_TUNN
EL_MISMER
GE
MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_LOCV,
MPLS_TUNNEL_UNKNOWN, MPLS_TUNNEL_Excess,
MPLS_TUNNEL_SF, MPLS_TUNNEL_SD, MPLS_TUNNEL_UN-
EXPMEP, MPLS_TUNNEL_UNEXPPER
MPLS_TUNN
EL_MISMAT
CH
MPLS_TUNNEL_LOCV, MPLS_TUNNEL_UNKNOWN,
MPLS_TUNNEL_Excess, MPLS_TUNNEL_SF,
MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPMEP,
MPLS_TUNN
EL_FDI
MPLS_TUNN
EL_UNEXP
MEG
MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_LOCV,
MPLS_TUNNEL_SF, MPLS_TUNNEL_SD, MPLS_TUNNEL_UN-
EXPMEP, MPLS_TUNNEL_UNEXPPER
MPLS_TUNN
EL_UNEXP
MEP
MPLS_TUNNEL_SD, MPLS_TUNNEL_UNEXPPER
977
MPLS_TUNN
EL_AIS
MPLS_TUNN
EL_LOCV
MPLS_TUNNEL_SF
MPLS_TUNN
EL_SF
MPLS_TUNNEL_SD

Table F-10 Suppression relationship between intra-board alarms (PW)
MPLS_PW_
MISMERGE
MPLS_PW_MISMATCH, MPLS_PW_LOCV,
MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF,
MPLS_PW_SD, MPLS_PW_UNEXPMEP, MPLS_PW_UNEXPPER
MPLS_PW_
MISMATCH
MPLS_PW_LOCV, MPLS_PW_UNKNOWN, MPLS_PW_Excess,
MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPMEP,
MPLS_PW_UNEXPPER
MPLS_PW_U
NEXPMEG
MPLS_PW_MISMATCH, MPLS_PW_LOCV,
MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF,
MPLS_PW_SD, MPLS_PW_UNEXPMEP, MPLS_PW_UNEXPPER
MPLS_PW_U
NEXPMEP
MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPPER
MPLS_PW_A
IS
MPLS_PW_SF, MPLS_PW_SD, MPLS_PW_UNEXPMEP,
MPLS_PW_UNEXPPER
MPLS_PW_L
OCV
MPLS_PW_UNKNOWN, MPLS_PW_Excess, MPLS_PW_SF
MPLS_PW_S
F
MPLS_PW_SD
MPLS_PW_L
CK
MPLS_PW_LOCV, MPLS_PW_SF, MPLS_PW_SD

978
Table F-11 Suppression relationship between intra-board alarms (Tunnel APS)
ETH_APS_P
ATH_MISM
ATCH
ETH_APS_LOST
ETH_APS_L
OST
ETH_APS_TYPE_MISMATCH, ETH_APS_SWITCH_FAIL

Table F-12 Suppression relationship between intra-board alarms (PW APS)
PWAPS_SWI
TCH_FAIL
PWAPS_LOST, PWAPS_PATH_MISMATCH,
PWAPS_TYPE_MISMATCH
PWAPS_LOS
T
PWAPS_PATH_MISMATCH, PWAPS_TYPE_MISMATCH

Table F-13 Suppression relationship between intra-board alarms (ETH OAM)
ETH_CFM_
MISMERGE
ETH_CFM_U
NEXPERI
ETH_CFM_A
IS
ETH_CFM_LOC

Table F-14 Suppression relationship between intra-board alarms (CES services)
CES_LOSPK
T_EXC
CES_STRAYPKT_EXC, CES_JTROVR_EXC, CES_JTRUDR_EXC
CES_STRAY
PKT_EXC
CES_MISORDERPKT_EXC, CES_MALPKT_EXC

979
Table F-15 Suppression relationship between intra-board alarms (ATM/IMA services)
IMA_GROU
P_LE_DOW
N
VC_LOC, VP_LOC
ALM_IMA_L
IF
ALM_IMA_LODS
ALM_E1RAI ALM_IMA_RFI, ALM_IMA_RE_RX_UNUSABLE
T_ALOS UP_E1_AIS
UP_E1_AIS LFA, ALM_E1RAI
LFA LMFA, ALM_IMA_LIF, ALM_E1RAI
LMFA ALM_IMA_LIF

Table F-16 Suppression relationship between intra-board alarms (PPP)
PPP_LCP_F
AIL
PPP_NCP_FAIL

Table F-17 Suppression relationship between intra-board alarms (EoS/EoPDH)
TU_AIS_VC1
2
LP_TIM_VC12, LP_SLM_VC12, LP_UNEQ_VC12, LP_RDI_VC12
TU_LOP_VC
12
LP_TIM_VC12, LP_SLM_VC12, LP_UNEQ_VC12LP_RDI_VC12
LP_UNEQ_V
C12
LFA
BIP_EXC BIP_SD

Table F-18 Suppression relationship between intra-board alarms (Tunnel service - PW service)
MPLS_TUNN
EL_LOCV
MPLS_PW_LOCV
980
MPLS_TUNN
EL_BDI
MPLS_PW_BDI
MPLS_TUNN
EL_RDI
MPLS_PW_RDI
MPLS_TUNN
EL_OAMFAI
L
MPLS_PW_OAMFAIL
MPLS_TUNN
EL_LOCK
MPLS_PW_LOCV

Inter-board Alarm Suppression on Data Plane
The inter-board alarm suppression means that, when services are configured between two boards
on the same NE, the service alarm generated by the source board suppresses the service alarm
generated by the sink board. The data plane supports alarm suppression between interface/IF
boards and switching boards.
Table F-19 Suppression relationship between inter-board alarms (Ethernet Interface board-
Switching board)
LSR_NO_FIT
ED,
ETH_LOS,
LASER_MO
D_ERR
MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL,
MPLS_TUNNEL_FDI, MPLS_TUNNEL_BDI,
MPLS_TUNNEL_AIS, MPLS_TUNNEL_RDI, MPLS_TUNNEL_SF,
MPLS_TUNNEL_SD, MPLS_PW_UNKNOWN, MPLS_PW_Excess,
MPLS_TUNNEL_MISMERGE, MPLS_TUNNEL_MISMATCH,
MPLS_PW_UNEXPMEG, MPLS_TUNNEL_UNEXPMEP

Table F-20 Suppression relationship between inter-board alarms (IF board-Switching board)
R_LOC MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL

981
Table F-21 Suppression relationship between inter-board alarms (PPP interface board-
Switching board)
PPP_NCP_F
AIL,
MP_DOWN
MPLS_TUNNEL_LOCV, MPLS_TUNNEL_OAMFAIL,
MPLS_TUNNEL_BDI
982
G Indicators of Boards
Indicators of Boards
Table G-1 Status explanation for indicators on the CST
Indicator State Meaning
STAT On (green) The board is working properly.
On (red) The board hardware is faulty.
Off l The board is not working.
l The board is not created.
l There is no power supplied to the
board.
PROG Blinks on (green) and off at
100 ms intervals
Software is being loaded to the board
during the power-on or resetting process
of the board.
Blinks on (green) and off at
300 ms intervals
The board software is in BIOS boot state
of the board.
On (green) 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.
Maintenance Guide G Indicators of Boards
983
On (red) 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) The clock is working properly.
On (red) The clock source is lost or a clock
switchover occurs.
SRV On (green) The system is working properly.
On (red) A critical or major alarm occurs in the
system.
On (yellow) A minor or remote alarm occurs in the
system.
ACT On (green) In a 1+1 protected system, the board
works as the active one.
In an unprotected system, the board has
been activated.
Off In a 1+1 protected system, the board
works as the standby one.
In an unprotected system, the board is not
activated.

Table G-2 Status explanation for indicators on the CSH
984
board.
100 ms intervals
of the board.
300 ms intervals
of the board.
100 ms intervals
board.
the board.
switchover occurs.
system.
system.
985
been activated.
activated.

Table G-3 Status explanation for indicators on the CSHU
board.
100 ms intervals
of the board.
300 ms intervals
of the board.
100 ms intervals
board.
986
the board.
switchover occurs.
system.
system.
been activated.
activated.
USB Blinks (red) The USB flash drive is online but faulty,
or the NE does not support the USB flash
drive.
Blinks on (yellow) and off
at 300 ms intervals
Data on the USB flash drive is being
backed up or recovered.
On (red) Backing up or recovering data on the
USB flash drive fails.
On (green) l The USB flash drive is online.
l Backing up or recovering data on the
USB flash drive is complete.
987
Off The USB flash drive is offline, or the NE
cannot recognize the USB flash drive.

Table G-4 Status explanation for indicators on the CSHUA
board.
100 ms intervals
of the board.
300 ms intervals
of the board.
100 ms intervals
board.
the board.
988
switchover occurs.
system.
system.
been activated.
activated.
USB Blinks (red) The USB flash drive is online but faulty,
or the NE does not support the USB flash
drive.
Blinks on (yellow) and off
at 300 ms intervals
Data on the USB flash drive is being
backed up or recovered.
On (red) Backing up or recovering data on the
USB flash drive fails.
On (green) l The USB flash drive is online.
l Backing up or recovering data on the
USB flash drive is complete.
Off The USB flash drive is offline, or the NE
cannot recognize the USB flash drive.

Table G-5 Status explanation for indicators on the IF1
STAT On (green) The board is working
properly.
989
l There is no power
supplied to the board.
SRV On (green) The services are normal.
On (red) A critical or major alarm
occurs in the services.
On (yellow) A minor or remote alarm
LINK On (green) The radio link is normal.
On (red) The radio link is faulty.
ODU On (green) The ODU is working
properly.
On (red) 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.
Blinks on (yellow) and off at
300 ms intervals
The antennas are not aligned.
Off The ODU is offline.
RMT On (yellow) The remote equipment is
reporting defects.
Off The remote equipment is free
of defects.
ACT On (green) l In a 1+1 protected system,
the board works as the
active one.
l In an unprotected system,
the board has been
activated.
Off l In a 1+1 protected system,
standby one.
the board is not activated.
990

Table G-6 Status explanation for indicators on the IFU2
l There is no power supplied to the board.
services.
services.
ODU On (green) The ODU is working properly.
On (red) 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.
Blinks on (yellow)
and off at 300 ms
intervals
RMT On (yellow) The remote equipment is reporting defects.
Off The remote equipment is free of defects.
ACT On (green) l In a 1+1 protected system, the board
l In an unprotected system, the board has
been activated.
Off l In a 1+1 protected system, the board
l In an unprotected system, the board is not
activated.

991
Table G-7 Status explanation for indicators on the ISU2
properly.
l There is no power
properly.
l There is no power
alarms.
300 ms intervals
reporting defects.
of defects.
active one.
the board has been
activated.
992
standby one.

Table G-8 Status explanation for indicators on the IFX2
XPIC On (green) The XPIC input signal is
normal.
On (red) The XPIC input signal is lost.
Off The XPIC function is
disabled.
properly.
l There is no power
properly.
l There is no power
alarms.
993
300 ms intervals
reporting defects.
of defects.
active one.
the board has been
activated.
standby one.

Table G-9 Status explanation for indicators on the ISX2
XPIC On (green) The XPIC input signal is
normal.
On (red) The XPIC input signal is lost.
Off The XPIC function is
disabled.
properly.
l There is no power
994
properly.
l There is no power
alarms.
300 ms intervals
reporting defects.
of defects.
active one.
the board has been
activated.
standby one.

Table G-10 Status explanation for indicators on an ISV3 board
XPIC On (green) XPIC input signals are
normal.
On (red) XPIC input signals are lost.
995
Off XPIC is disabled.
properly.
Off The board is not working, not
created, or not powered on.
SRV On (green) Services are normal.
On (red) A critical or major alarm has
been reported.
On (yellow) A minor or remote alarm has
been reported.
properly.
On (red) The ODU has reported a
critical or major alarm, or
was not powered on.
On (yellow) The ODU has reported a
minor alarm.
300 ms intervals
Antennas are not well
aligned.
RMT On (yellow) The remote equipment has
reported a defect.
of defects.
ACT On (green) In a 1+1 protected system, the
board is working as the main
board.
In an unprotected system, the
board has been activated.
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.
996

Table G-11 Status explanation for indicators on the EM6T/EM6F
system.
On (yellow) A minor alarm occurs in the system.
Off There is no power supplied to the system.
100 ms intervals
Software is being loaded to the board during
board.
300 ms intervals
during the power-on or resetting process of
the board.
On (green) 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.
On (red) 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.
LINK1
a
On (green) The GE1 port is connected correctly and is
not receiving or transmitting data.
Blinking (green) The GE1 port is receiving or transmitting
data.
997
Off The GE1 port is not connected or is
LINK2
a
Blinking (green) The GE2 port is receiving or transmitting
data.
NOTE
a: The LINK1 and LINK2 indicators are available only on the EM6F and indicate the states of the
corresponding GE ports.

Table G-12 Status explanation for indicators on the EM6TA/EM6FA
system.
100 ms intervals
board.
300 ms intervals
the board.
being initialized.
998
ms intervals
On (red) The memory self-check fails or loading
upper layer software fails during the power-
on 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/A1
a
Blinking (yellow) The GE1 port is receiving or transmitting
data.
L/A2
a
Blinking (yellow) The GE2 port is receiving or transmitting
data.
NOTE
a: The L/A1 and L/A2 indicators are available only on the EM6FA and indicate the states of the
corresponding GE ports.

Table G-13 Status explanation for indicators on an EG4/EG4P board
Off The board is not working, not created, or not
powered on.
On (red) A critical or major alarm has been reported.
On (yellow) A minor alarm has been reported.
Off No service is configured.
999
L/A1
(optical/
electrical
port 1)
On (green) Port GE1 is connected correctly but is not
receiving or transmitting data.
ms intervals
Port GE1 has received extremely high
optical power (applicable only to an optical
port).
Blinks on (red) for 300 ms and
off for 700 ms at 1000 ms
intervals
Port GE1 has received extremely low optical
power (applicable only to an optical port).
Blinks (yellow) Port GE1 is receiving or transmitting data.
Off Port GE1 is not connected or is incorrectly
connected.
L/A2
(optical/
electrical
port 2)
ms intervals
Port GE2 has received extremely high
optical power (applicable only to an optical
port).
Blinks on (red) for 300 ms and
off for 700 ms at 1000 ms
intervals
Port GE2 has received extremely low optical
power (applicable only to an optical port).
connected.
L/A3
(electrical
port 3)
connected.
L/A4
(electrical
port 4)
connected.
P1 On (green) Power over Ethernet port 1 is enabled.
Off Power over Ethernet port 1 is disabled or is
working abnormally.
P2 On (green) Power over Ethernet port 2 is enabled.
1000
Off Power over Ethernet port 2 is disabled or is
working abnormally.
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 G-14 Status explanation for indicators on the EMS6
100 ms intervals
board.
300 ms intervals
the board.
On (green) 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.
ms intervals
board.
board.
SRV On (green) The system is working normally.
system.
1001
LINK1 On (green) The GE1 port is connected correctly.
ms intervals
The receive optical power at the GE1 optical
port is higher than the upper threshold.
Blinks 300 ms on (red) and 700
ms off
port is lower than the lower threshold.
ACT1 Blinking (yellow) The GE1 port is receiving or transmitting
data.
Off The GE1 port is not receiving or
transmitting data.
LINK2 On (green) The GE2 port is connected correctly.
ms intervals
port is higher than the upper threshold.
Blinks 300 ms on (red) and 700
ms off
port is lower than the lower threshold.
ACT2 Blinking (yellow) The GE2 port is receiving or transmitting
data.
Off The GE2 port is not receiving or
transmitting data.

Table G-15 Status explanation for indicators on the EFP8
1002
100 ms intervals
board.
300 ms intervals
the board.
being initialized.
ms intervals
board.
board.
system.

Table G-16 Status explanation for indicators on the SL1D/SL1DA
properly.
l There is no power
1003
Off The services are not
configured.
LOS1 On (red) The first port of the SL1D/
SL1DA is reporting the
R_LOS alarm.
Off The first port of the SL1D/
SL1DA is free of R_LOS
alarms.
LOS2 On (red) The second port of the
SL1D/SL1DA is reporting
the R_LOS alarm.
Off The second port of the
SL1D/SL1DA is free of
R_LOS alarms.

Table G-17 Status explanation for indicators on the SP3S/SP3D
properly.
l There is no power
configured.

1004
Table G-18 Status explanation for indicators on the ML1/MD1
properly.
l There is no power
configured.

Table G-19 Status explanation for indicators on a CQ1 board
properly.
Off The board is not working, not
created, or not powered on.
On (red) A critical or major alarm has
been reported.
On (yellow) A minor or remote alarm has
been reported.
Off No service is configured.
LOS1 On (red) The first port has reported an
R_LOS alarm.
Off The first port does not report
any R_LOS alarms.
1005
LOS2 On (red) The second port has reported
an R_LOS alarm.
Off The second port does not
report any R_LOS alarms.
LOS3 On (red) The third port has reported an
R_LOS alarm.
Off The third port does not report
any R_LOS alarms.
LOS4 On (red) The fourth port has reported
an R_LOS alarms.
Off The fourth port does not
report any R_LOS alarms.

Table G-20 Status explanation for indicators on the AUX
board.
system.
system.

Table G-21 Status explanation for indicators on the PIU
Indicator Status Description
PWR On (green) The power supply is connected.
Off There is no power supplied to the PIU or the power
supply is connected incorrectly.

1006
Table G-22 Status explanation for indicators on the FAN
FAN On (green) The fan is working properly.
On (red) The fan is faulty.
Off The fan is not powered on or is not installed.

NOTE
The CRIT, MAJ, or MIN indicator on the front panel of the FAN indicates the current alarm severity of the
subrack.
1007
H Glossary
Numerics
3G See 3rd Generation.
3GPP 3rd Generation Partnership Project
3rd Generation (3G) 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.
802.1Q in 802.1Q
(QinQ)
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 analog/digit
ABR See available bit rate.
ACAP See adjacent channel alternate polarization.
ACL See access control list.
ADC analog to digital converter
ADM add/drop multiplexer
AF See assured forwarding.
AIS alarm indication signal
ALS See automatic laser shutdown.
AM See adaptive modulation.
APS automatic protection switching
ARP See Address Resolution Protocol.
Maintenance Guide H Glossary
1008
ASBR See autonomous system boundary router.
ASIC See application-specific integrated circuit.
ATM asynchronous transfer mode
ATPC See automatic transmit power control.
AU See administrative unit.
Address Resolution
Protocol (ARP)
An Internet Protocol used to map IP addresses to MAC addresses. The ARP protocol
enables hosts and routers to determine link layer addresses through ARP requests and
responses. The address resolution is a process by which the host converts the target IP
address into a target MAC address before transmitting a frame. The basic function of
ARP is to use the target equipment's IP address to query its MAC address.
access control list
(ACL)
A list of entities, together with their access rights, which are authorized to access a
resource.
adaptive modulation
(AM)
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 high-
efficiency 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.
adjacent channel
alternate polarization
(ACAP)
A channel configuration method, which uses two adjacent channels (a horizontal
polarization wave and a vertical polarization wave) to transmit two signals.
administrative unit
(AU)
The information structure that enables adaptation between the higher order path layer
and the multiplex section layer. The administrative unit 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.
alarm suppression A method to suppress alarms for the alarm management purpose. Alarms that are
suppressed are no longer reported from NEs.
analog signal 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.
application-specific
integrated circuit
(ASIC)
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.
assured forwarding
(AF)
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.
1009
attenuator 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.
automatic laser
shutdown (ALS)
A technique (procedure) to automatically shutdown the output power of laser transmitters
and optical amplifiers to avoid exposure to hazardous levels.
automatic transmit
power control (ATPC)
A method of adjusting the transmit power based on fading of the transmit signal detected
at the receiver
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 See broadband integrated services digital network.
BDI See backward defect indication.
BE See best effort.
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIOS See basic input/output system.
BIP See bit interleaved parity.
BPDU See bridge protocol data unit.
BSC See base station controller.
BTS base transceiver station
Bidirectional
Forwarding Detection
(BFD)
A fast and independent hello protocol that delivers millisecond-level link failure
detection and provides carrier-class availability. After sessions are established between
neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system regards
that the bidirectional link fails and instructs the upper layer protocol to take actions to
recover the faulty link.
backbone network 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.
backward defect
indication (BDI)
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.
1010
bandwidth A range of transmission frequencies a transmission line or channel can carry in a network.
In fact, the bandwidth is the difference between the highest and lowest frequencies in
the transmission line or channel. The greater the bandwidth, the faster the data transfer
rate.
base station controller
(BSC)
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.
basic input/output
system (BIOS)
Firmware stored on the computer motherboard that 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.
baud rate 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.
best effort (BE) 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.
bit interleaved parity
(BIP)
A method of error monitoring. With even parity, the transmitting equipment generates
an X-bit code 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 forth. Even parity is generated by setting
the BIP-X bits so that an even number of 1s exist in each monitored partition of the
signal. A monitored partition comprises all bits in the same bit position within the X-bit
sequences in the covered portion of the signal. The covered portion includes the BIP-X.
bridge 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.
bridge protocol data
unit (BPDU)
Data messages exchanged across switches within an extended LAN that uses a spanning
tree protocol (STP) topology. BPDU packets contain information on ports, addresses,
priorities, and costs, and they ensure that the data reaches its intended destination. BPDU
messages are exchanged across bridges to detect loops in a network topology. These
loops are then removed by shutting down selected bridge interfaces and placing
redundant switch ports in a backup, or blocked, state.
broadband integrated
services digital network
(B-ISDN)
A standard defined by the ITU-T to handle high-bandwidth applications, such as voice.
It currently uses the ATM technology to transmit data over SONNET-based circuits at
155 to 622 Mbit/s or higher speed.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.
1011
broadcast domain 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 committed access rate
CBR See constant bit rate.
CBS See committed burst size.
CC See continuity check.
CCDP See co-channel dual polarization.
CDMA See Code Division Multiple Access.
CE See customer edge.
CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIST See Common and Internal Spanning Tree.
CLNP connectionless network protocol
CM connection management
CORBA See Common Object Request Broker Architecture.
CPU See central processing unit.
CRC See cyclic redundancy check.
CSES consecutive severely errored second
CSMA/CD See carrier sense multiple access with collision detection.
CTC common transmit clock
CW control word
Code Division Multiple
Access (CDMA)
A communication scheme that uses frequency expansion technology to form different
code sequences. When the CDMA scheme is used, subscribers with different addresses
can use different code sequences for multi-address connection.
Common Object
Request Broker
Architecture (CORBA)
A specification developed by the Object Management Group in 1992 in which pieces of
programs (objects) communicate with other objects in other programs, even if the two
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 therefore does not need to know the structure of the program from which the
object comes. CORBA is designed to work in object-oriented environments.
Common and Internal
Spanning Tree (CIST)
The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
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 A tie used to bind cables.
1012
carrier sense multiple
access with collision
detection (CSMA/CD)
Carrier sense multiple access with collision detection (CSMA/CD) is a computer
networking access method in which:
l A carrier sensing scheme is used.
l 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
(CPU)
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
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
channel A telecommunication path of a specific capacity and/or speed between two or more
locations in a network. The channel can be established through wire, radio (microwave),
fiber, or any 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 (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s
(1012 bit/s).
circuit emulation
service (CES)
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.
clock tracing The method of keeping the time on each node synchronized with a clock source in the
network.
co-channel dual
polarization (CCDP)
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.
committed burst size
(CBS)
A parameter used to define the capacity of token bucket C, that is, the maximum burst
IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of an
IP packet to be forwarded.
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) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
cross polarization
interference
cancellation (XPIC)
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.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly connecting
to the Service Provider (SP) network. A CE can be a router, switch, or host.
1013
cyclic redundancy
check (CRC)
A procedure used to check 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 performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the transmission
is considered to be error free. This procedure is known as a redundancy check because
each transmission includes not only data but extra (redundant) error-checking values.
D
DC direct current
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common
(with ground) (DC-C)
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.
DC-return isolate (with
ground) (DC-I)
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 is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel.
DCN See data communication network.
DDF digital distribution frame
DDN See digital data network.
DE discard eligible
DM See delay measurement.
DS boundary node 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.
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP See differentiated services code point.
DVMRP See Distance Vector Multicast Routing Protocol.
DiffServ See Differentiated Services.
Differentiated Services
(DiffServ)
An IETF standard that defines a mechanism for controlling and forwarding traffic in a
differentiated manner based on CoS settings to handle network congestion.
Distance Vector
Multicast Routing
Protocol (DVMRP)
An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
implements a typical dense mode IP multicast solution and uses IGMP to exchange
routing datagrams with its neighbors.
data communication
network (DCN)
A communication network used in a TMN or between TMNs to support the data
communication function.
1014
data communications
channel (DCC)
The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
delay measurement
(DM)
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.
differentiated services
code point (DSCP)
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.
digital data network
(DDN)
A data transmission network that is designed to transmit data on digital channels (such
as the fiber channel, digital microwave channel, or satellite channel).
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 See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
ECC See embedded control channel.
EMC See electromagnetic compatibility.
EMI See electromagnetic interference.
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logical device.
ERPS Ethernet ring protection switching
ESD electrostatic discharge
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
1015
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable and
easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000
Mbit/s, or 10,000 Mbit/s.
Ethernet aggregation
(E-Aggr)
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
connection).
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area
network (E-LAN)
A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
virtual connection).
Ethernet private LAN
service (EPLAN)
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line
(EPL)
networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual
private LAN service
(EVPLAN)
networks. This service is carried over shared bandwidth between multipoint-to-
multipoint connections.
Ethernet virtual
private line (EVPL)
networks. This service is carried over shared bandwidth between point-to-point
connections.
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
electromagnetic
compatibility (EMC)
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.
electromagnetic
interference (EMI)
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
limits the performance of electronics/electrical equipment.
embedded control
channel (ECC)
A logical channel that uses a data communications channel (DCC) as its physical layer
to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
engineering label A mark on a cable, a subrack, or a cabinet for identification.
erasable
programmable logical
device (EPLD)
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.
F
FD See frequency diversity.
FDDI See fiber distributed data interface.
1016
FDI See forward defect indication.
FEC See forward error correction.
FFD fast failure detection
FFD packet 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.
FIFO See first in first out.
FPGA See field programmable gate array.
FTP File Transfer Protocol
fiber distributed data
interface (FDDI)
A standard developed by the American National Standards Institute (ANSI) for high-
speed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
field programmable
gate array (FPGA)
A semi-customized circuit that is used in the Application Specific Integrated Circuit
(ASIC) field and developed based on programmable components. FPGA remedies many
of the deficiencies of customized circuits, and allows the use of many more gate arrays.
first in first out (FIFO) A stack management method in which data that is stored first in a queue is also read and
invoked first.
forward defect
indication (FDI)
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.
forward error
correction (FEC)
A bit error correction technology that adds correction information to the payload at the
transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
fragmentation 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.
frequency diversity
(FD)
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.
G
GCRA generic cell rate algorithm
GFC generic flow control
GFP See Generic Framing Procedure.
GNE See gateway network element.
GPS See Global Positioning System.
GTS See generic traffic shaping.
GUI graphical user interface
1017
Generic Framing
Procedure (GFP)
A framing and encapsulated method that can be applied to any data type. GFP is defined
by ITU-T G.7041.
Global Positioning
System (GPS)
A global navigation satellite system that provides reliable positioning, navigation, and
timing services to users worldwide.
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network
element (GNE)
An NE that serves as a gateway for other NEs to communicate with a network
management system.
generic traffic shaping
(GTS)
A traffic control measure that proactively adjusts the output speed of the traffic. This is
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
H
HDLC High-Level Data Link Control
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.
HSM hitless switch mode
High Speed Downlink
Packet Access
(HSDPA)
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.
hierarchical quality of
service (HQoS)
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.
hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports
the AM function.
I
I/O input/output
ICMP See Internet Control Message Protocol.
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
IGMP snooping 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.
IGP See Interior Gateway Protocol.
1018
IMA See inverse multiplexing over ATM.
IP Internet Protocol
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISO International Organization for Standardization
IST internal spanning tree
ITU See International Telecommunication Union.
IWF Interworking Function
Institute of Electrical
and Electronics
Engineers (IEEE)
A professional association of electrical and electronics engineers based in the United
States, but with membership from numerous other countries. The IEEE focuses on
electrical, electronics, and computer engineering, and produces many important
technology standards.
Interior Gateway
Protocol (IGP)
A routing protocol that is used within an autonomous system. The IGP runs in small-
sized 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
Intermediate System
(IS-IS)
A protocol used by network devices (routers) to determine the best way to forward
datagram or packets through a packet-based network.
International
Telecommunication
Union (ITU)
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).
Internet Control
Message Protocol
(ICMP)
A network layer protocol that provides message control and error reporting between a
host server and an Internet gateway.
Internet Group
Management Protocol
(IGMP)
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 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.
Internet Protocol
version 6 (IPv6)
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.
1019
indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,
multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
intermediate frequency
(IF)
The transitional frequency between the frequencies of a modulated signal and an RF
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 Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LB See loopback.
LCAS See link capacity adjustment scheme.
LM See loss measurement.
LOS See loss of signal.
LPT link-state pass through
LSDB link state database
LSP See label switched path.
LSP tunnel 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
LSR See label switching router.
LTE Long Term Evolution
Layer 2 switching 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.
Link Aggregation
Control Protocol
(LACP)
A dynamic link aggregation protocol that improves the transmission speed and
reliability. The two ends of the link send LACP packets to inform each other of their
parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
label switched path
(LSP)
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.
1020
label switching router
(LSR)
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.
laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. Semi-conductor lasers provide the light
used in a fiber system.
line rate 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 MSP linear multiplex section protection
link aggregation group
(LAG)
An aggregation that allows one or more links to be aggregated together to form a link
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.
local area network
(LAN)
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi technology and run at 1,000
Mbit/s (that is, 1 Gbit/s).
loopback (LB) 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.
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) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MADM multiple add/drop multiplexer
MBS maximum burst size
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDI medium dependent interface
MEP maintenance association end point
MIB See management information base.
1021
MIP maintenance intermediate point
MLPPP Multi-Link Point-to-Point Protocol
MP maintenance point
MPLS See Multiprotocol Label Switching.
MPLS L2VPN 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.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MPLS-TP See MultiProtocol Label Switching Transport Profile.
MS multiplex section
MSP See multiplex section protection.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTTR See mean time to repair.
MTU See maximum transmission unit.
Media Access Control
(MAC)
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.
MultiProtocol Label
Switching Transport
Profile (MPLS-TP)
A packet transport technology proposed by IETF that combines the packet experience
of MPLS with the operational experience of transport networks.
Multiple Spanning
Tree Protocol (MSTP)
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.
Multiple Spanning
Tree region (MST
region)
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.
1022
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.
maintenance domain
(MD)
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).
management
information base (MIB)
A type of database used for managing the devices in a communications network. It
comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
maximum transmission
unit (MTU)
The largest packet of data that can be transmitted on a network. MTU size varies,
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)
The average time between consecutive failures of a piece of equipment. It is a measure
of the reliability of the system.
mean time to repair
(MTTR)
The average time that a device will take to recover from a failure.
message digest
algorithm 5 (MD5)
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.
multicast 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.
multiple spanning tree
instance (MSTI)
A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
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)
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.
multiprotocol label
switching virtual
private network
(MPLS VPN)
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
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
1023
NE network element
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NNI network-to-network interface
NPE network provider edge
NSAP See network service access point.
NSF non-stop forwarding
network service access
point (NSAP)
A network address defined by ISO, at which the OSI Network Service is made available
to a Network service user by the Network service provider.
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.
node 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.
non-GNE See non-gateway network element.
non-gateway network
element (non-GNE)
A network element that communicates with the NM application layer through the
gateway NE application layer.
O
O&M operation and maintenance
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
ODF optical distribution frame
ODU See outdoor unit.
OSPF See Open Shortest Path First.
Open Shortest Path
First (OSPF)
A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
cost as its routing metric. A link state database is constructed of the network topology,
which is identical on all routers in the area.
operation,
administration and
maintenance (OAM)
A set of network management functions that cover fault detection, notification, location,
and repair.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequency
conversion and amplification for radio frequency (RF) signals.
P
1024
P2P See point-to-point service.
PBS See peak burst size.
PCB See printed circuit board.
PDH See plesiochronous digital hierarchy.
PDU protocol data unit
PE See provider edge.
PHB See per-hop behavior.
PIR peak information rate
PLA See physical link aggregation.
PLL See phase-locked loop.
PPP Point-to-Point Protocol
PRBS See pseudo random binary sequence.
PRI primary rate interface
PSN See packet switched network.
PSTN See public switched telephone network.
PTN packet transport network
PTP Precision Time Protocol
PTP clock See Precision Time Protocol clock.
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
Precision Time
Protocol clock (PTP
clock)
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.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
peak burst size (PBS) A parameter that defines the capacity of token bucket P, that is, the maximum burst IP
packet size when the information is transferred at the peak information rate.
per-hop behavior
(PHB)
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).
permanent virtual path
(PVP)
Virtual path that consists of PVCs.
1025
phase-locked loop
(PLL)
A circuit that consists essentially of a phase detector that compares the frequency of a
voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency 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.
physical link
aggregation (PLA)
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.
plesiochronous digital
hierarchy (PDH)
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
polarization 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.
printed circuit board
(PCB)
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.
provider edge (PE) 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.
pseudo random binary
sequence (PRBS)
A sequence that is random in the sense that the value of each element is independent of
the values of any of the other elements, similar to a real random sequence.
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.
pseudo wire emulation
edge-to-edge (PWE3)
An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
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)
A telecommunications network established to perform telephone services for the public
subscribers. Sometimes it is called POTS.
Q
QAM See quadrature amplitude modulation.
QPSK See quadrature phase shift keying.
1026
QinQ See 802.1Q in 802.1Q.
QoS See quality of service.
quadrature amplitude
modulation (QAM)
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.
quadrature phase shift
keying (QPSK)
A modulation method of data transmission through the conversion or modulation and
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 two-
bit 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 See Remote Authentication Dial In User Service.
RADIUS accounting An accounting mode in which the BRAS sends the accounting packets to the RADIUS
server. Then the RADIUS server performs accounting.
RDI remote defect indication
RED See random early detection.
REI remote error indication
RF See radio frequency.
RFC See Request For Comments.
RMEP remote maintenance association end point
RMON remote network monitoring
RNC See radio network controller.
RSL See received signal level.
RSSI See received signal strength indicator.
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RTN radio transmission node
RTSP Real-Time Streaming Protocol
Rapid Spanning Tree
Protocol (RSTP)
An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
1027
Remote Authentication
Dial In User Service
(RADIUS)
A security service that authenticates and authorizes dial-up users and is a centralized
access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments
(RFC)
A document in which a standard, a protocol, or other information pertaining to the
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)
A protocol that reserves resources on every node along a path. RSVP is designed for an
integrated services Internet.
RoHS restriction of the use of certain hazardous substances
radio frequency (RF) 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.
radio network
controller (RNC)
A device in a radio network subsystem that is in charge of controlling the usage and
integrity of radio resources.
random early detection
(RED)
A packet loss algorithm used in congestion avoidance. It discards the packet according
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.
received signal level
(RSL)
The signal level at a receiver input terminal.
received signal strength
indicator (RSSI)
The received wide band power, including thermal noise and noise generated in the
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
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
regeneration 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.
route The path that network traffic takes from its source to its destination. Routes can change
dynamically.
router 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.
rt-VBR See real-time variable bit rate.
1028
S
SAI service area identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SCSI Small Computer System Interface
SD See space diversity.
SDH See synchronous digital hierarchy.
SEC security screening
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SLA See service level agreement.
SNCP subnetwork connection protection
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
STM See synchronous transport module.
STM-1 See Synchronous Transport Module level 1.
STM-4 Synchronous Transport Module level 4
STM-N Synchronous Transport Module level N
STP Spanning Tree Protocol
Secure Sockets Layer
(SSL)
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.
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
Message (SSM)
A message that carries the quality levels of timing signals on a synchronous timing link.
SSM messages provide upstream clock information to nodes on an SDH network or
synchronization network.
Synchronous
Transport Module level
1 (STM-1)
Synchronous transfer mode at 155 Mbit/s.
1029
service level agreement
(SLA)
A service agreement between a customer and a service provider. SLA specifies the
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) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio
(SNR)
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.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.
single-polarized
antenna
An antenna intended to radiate or receive radio waves with only one specified
polarization.
space diversity (SD) 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.
subnet mask 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 device and is matched
with the IP address.
synchronous digital
hierarchy (SDH)
A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH 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 B-
ISDN.
synchronous transport
module (STM)
An information structure used to support section layer connections in the SDH. It consists
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 A North American standard for high-speed data transmission at 1.544Mbps. It provides
24 x 64 kbit/s channels.
TCI tag control information
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDD time division duplex
TDM See time division multiplexing.
TDMA See Time Division Multiple Access.
1030
TE See traffic engineering.
TEDB See traffic engineering database.
TIM trace identifier mismatch
TMN See telecommunications management network.
TOS test operation system
TTL See time to live.
TUG tributary unit group
Telnet 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
Access (TDMA)
An approach used for allocating a single channel among many users, by dividing the
channel into different timeslots during which each user has access to the medium.
Time Division-
Synchronous 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.
Transmission Control
Protocol (TCP)
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.
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.
tangent ring A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications
management network
(TMN)
A protocol model defined by ITU-T for managing open systems in a communications
network. TMN manages the planning, provisioning, installation, and OAM of
equipment, networks, and services.
time division
multiplexing (TDM)
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.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
trTCM See two rate three color marker.
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.
1031
traffic engineering
database (TEDB)
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.
tributary loopback 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.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
two rate three color
marker (trTCM)
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.
U
UART universal asynchronous receiver/transmitter
UAS unavailable second
UBR unspecified bit rate
UBR+ Unspecified Bit Rate Plus
UDP See User Datagram Protocol.
UI user interface
UNI See user-to-network interface.
UPC See usage parameter control.
User Datagram
Protocol (UDP)
A TCP/IP standard protocol that allows an application program on one device to send a
datagram to an application program on another. UDP uses IP to deliver datagrams. UDP
provides application programs with the unreliable connectionless packet delivery
service. That is, UDP messages may be lost, duplicated, delayed, or delivered out of
order. The destination device does not actively confirm whether the correct data packet
is received.
unicast The process of sending data from a source to a single recipient.
usage parameter
control (UPC)
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.
user-to-network
interface (UNI)
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-NNI virtual network-network interface
1032
V-UNI See virtual user-network interface.
VB virtual bridge
VBR See variable bit rate.
VC See virtual container.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VLAN virtual local area network
VPI See virtual path identifier.
VPLS virtual private LAN segment
VPN virtual private network
VSWR voltage standing wave ratio
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.
virtual channel
connection (VCC)
A VC logical trail that carries data between two end points in an ATM network. A point-
to-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit 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) .
virtual concatenation
group (VCG)
A group of co-located member trail termination functions that are connected to the same
virtual concatenation link.
virtual container (VC) An information structure used to support path layer connections in the SDH. A VC
consists of a payload and path overhead (POH), which are organized in a block frame
structure that repeats every 125 s or 500 s.
virtual path identifier
(VPI)
The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which
virtual path the cell belongs.
virtual user-network
interface (V-UNI)
A virtual user-network interface, works as an action point to perform service
classification and traffic control in HQoS.
W
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WEEE waste electrical and electronic equipment
WFQ See weighted fair queuing.
1033
WRED See weighted random early detection.
WRR weighted round robin
WTR See wait to restore.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wi-Fi See Wireless Fidelity.
Wideband Code
Division Multiple
Access (WCDMA)
A standard defined by the ITU-T for the third-generation wireless technology derived
from the Code Division Multiple Access (CDMA) technology.
Wireless Fidelity (Wi-
Fi)
A short-distant wireless transmission technology. It enables wireless access to the
Internet within a range of hundreds of feet wide.
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
weighted fair queuing
(WFQ)
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.
weighted random early
detection (WRED)
A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
winding pipe A tool for fiber routing, which acts as the corrugated pipe.
X
XPIC See cross polarization interference cancellation.
1034

OptiX RTN 950 Maintenance Guide (V100R006)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OptiX RTN 950 Maintenance Guide (V100R006)

Uploaded by

Copyright:

Available Formats

OptiX RTN 950 Radio Transmission System

DON'T TOUCH THE

Packet transmission interval on the client

You might also like