CiTRANS 660

High-capacity MPLS-TP Platform

Alarm and Performance

Reference
Version: A

Code: MN000001393

FiberHome Telecommunication Technologies Co., Ltd.

December 2012
Thank you for choosing our products.

We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.

All rights reserved

No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface

Related Documentation
Document Description

CiTRANS 660 High-capacity Introduces functions and features, protection mechanisms,

MPLS-TP Platform Product networking applications and technical specifications of the
Description product.

Describes the equipment’s structures, functions, signal

CiTRANS 660 High-capacity
flows, specifications, and technical parameters in terms of
MPLS-TP Platform Hardware
its hardware components (i.e. the cabinet, the subrack,
Description
cards, and cables).

Details the equipment’s appearance and structure, how to

CiTRANS 660 High-capacity
install the equipment, connect and lay out its wires and
MPLS-TP Platform Installation
cables, as well as the requirements on the installation
Guide
environment.
Introduces the rules and methods for the configuration of
CiTRANS 660 High-capacity
various functions and performance parameters in the
MPLS-TP Platform Configuration
subnet-level mode through the OTNM2000; gives some
Guide
typical configuration examples and operation procedures.

Details the routine maintenance items and operation

procedures, including the daily maintenance, the weekly
CiTRANS 660 High-capacity
maintenance, the monthly maintenance, and the quarterly
MPLS-TP Platform Routine
maintenance. Also includes the daily operation procedures
Maintenance
of the equipment, instructing users on the implementation
of the basic operations such as hardware replacement.

CiTRANS 660 High-capacity Gives a detailed introduction to notices of fault

MPLS-TP Platform management, fault isolating methods as well as
Troubleshooting Guide procedures and methods of fault management.

I
 Document Description

Describes classification and category of alarm and

CiTRANS 660 High-capacity
performance indicators and their suppressing
MPLS-TP Platform Alarm and
relationships, and lists definitions, causes and
Performance Reference
management of each alarm and performance.

Includes four manuals, i.e., product description, operation

guide, routine maintenance and installation guide, all of
e-Fim OTNM2000 Element
which are aimed at introducing common and fundamental
Management System Manual Set
contents of the OTNM2000 for a better understanding and
proficient use of the network management system.

II
Version
Version Description

Initial version.
A The version of the OTNM2000 is: V2.0R5, Build: 04.20.05.
32SP10.

Intended Readers

This manual is intended for the following readers:

u Commissioning engineers

u Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

u MPLS-TP technology

u Data communication technology

u TDM communication theory

u Ethernet technology

III
 Conventions

Terminology Conventions

Terminology Convention
FiberHome CiTRANS 660 High-capacity MPLS-TP
CiTRANS 660
Platform
FiberHome e-Fim OTNM2000 Element Management
OTNM2000
System

NMUJ1 EMU Management Card

XCUJ2 Cross-connect & Clock Card (320G)

XCUJ4 Cross-connect & Clock Card (160G)

XSJ2 10G LAN/WAN Optical Interface Card (2 channels)

XSJ3 10G LAN/WAN Optical Interface Card (4 channels)

XGJ1 XGE & GE Interface Board

GSJ2 GE Interface Card with Switch Function (MPLS)

GSJ3 GE Interface Card

ESJ1 Ethernet Interface Card with Switch Function
ESJ2 FE Interface Card with Switch Function
S1J1 STM-1 Optical Interface Card

S1J2 STM-1 Optical Interface Card (2 channels)

S1O1 cSTM-1 Emulated Interface Unit

S1J4 8×STM-1 Optical Interface Card

E1J1 E1 Interface Card

E1J2 E1 Processing Card

AIFJ1 Power and Auxiliary Terminal Board 1

AIFJ2 Power and Auxiliary Terminal Board 2

IEJ1 E1 Terminal Board (75Ω)

IEJ2 E1 Terminal Board (120Ω)

IFJ1 Ethernet Terminal Board

IV
Symbol Conventions

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.

Warning May cause severe bodily injuries.

➔ Jump Jumps to another step.

Cascading
→ Connects multi-level menu options.
menu
Bidirectional
↔ The service signal is bidirectional.
service
Unidirectional
→ The service signal is unidirectional.
service

V
Contents

Preface...................................................................................................................I

Related Documentation ...................................................................................I

Version ..........................................................................................................III

Intended Readers ..........................................................................................III

Conventions ................................................................................................. IV

1 Overview ........................................................................................................1

1.1 Operation Safety Precautions............................................................2

1.1.1 Safety and Warning Signs ...................................................2

1.1.2 ESD Protection Measures ...................................................4
1.1.3 Plugging and Unplugging Cards..........................................4
1.1.4 Operation Safety Rules of a Fiber and an Optical Interface ..6
1.1.5 Electrical Safety Precautions...............................................8
1.1.6 Operation Safety Rules of the OTNM2000...........................9

1.2 Alarm Definition ..............................................................................14

1.3 Alarm Level ....................................................................................14

1.4 Principles for Alarm Handling ..........................................................15

1.5 Alarm Classification ........................................................................17

1.6 Performance Classification .............................................................17

1.7 Alarm List .......................................................................................18

1.8 Performance List.............................................................................28

2 Basic Operations on the Alarm / Performance Event......................................34

2.1 Querying Alarm...............................................................................35

2.1.1 Querying Current Alarms ..................................................35

2.1.2 Querying Alarm History .....................................................36

2.2 Enabling the Performance Parameter Collection Function ...............38

2.3 Query Performance ........................................................................40

2.3.1 Querying Current Performance .........................................40

2.3.2 Querying Performance History ..........................................43
 2.4 Filtering the Card Alarm / Performance Event ..................................45

3 Alarm Handling .............................................................................................51

3.1 .MS_EXC. ......................................................................................60

3.2 .RS_SD. .........................................................................................62

3.3 1PPS_LOS.....................................................................................63

3.4 ALN_ERR.......................................................................................64

3.5 APS_MISMATCH ...........................................................................65

3.6 AU_AIS ..........................................................................................66

3.7 AU_LOP.........................................................................................67

3.8 AU_NPJE_ALARM .........................................................................69

3.9 AU_PPJE_ALARM .........................................................................70

3.10 BACKUP_FAULT............................................................................72

3.11 BAK_5V_FAIL ................................................................................73

3.12 BCS ...............................................................................................73

3.13 BKIP_ERR .....................................................................................74

3.14 BMC_LOS ......................................................................................75

3.15 BMC_SW .......................................................................................76

3.16 BRIDGE .........................................................................................77

3.17 CARD_ABSENT.............................................................................78

3.18 CARD_SWITCH .............................................................................79

3.19 CARD_TCT./CARD_TCT ................................................................80

3.20 CES_PK_LOS ................................................................................82

3.21 CFG_MISMATCH./CFG_MISMATCH..............................................83

3.22 COMFAIL .......................................................................................84

3.23 CONTEXT_FAIL .............................................................................85

3.24 CONTEXT_PACKET_LOS .............................................................86

3.25 CRC_PACKET_LIMIT.....................................................................88

3.26 CRC_ERR......................................................................................89

3.27 CUR_LOCK....................................................................................90

3.28 DCVOLDOWN................................................................................91

3.29 DCVOLOVER.................................................................................92
3.30 DZB_IN ..........................................................................................93

3.31 E1_AIS...........................................................................................94

3.32 E1_ES_LIMIT .................................................................................95

3.33 E1_LOF..........................................................................................97

3.34 E1_LOS .........................................................................................98

3.35 E1_RDI ..........................................................................................99

3.36 ETH_LCK .....................................................................................100

3.37 ETH_LOC.....................................................................................101

3.38 ETH_MMG ...................................................................................102

3.39 ETH_RDI......................................................................................103

3.40 ETH_UNL.....................................................................................105

3.41 ETH_UNM....................................................................................106

3.42 ETH_UNP ....................................................................................107

3.43 ETHLB_LOS ................................................................................108

3.44 fDISABLE ..................................................................................... 110

3.45 fRDONLY ..................................................................................... 111

3.46 FAIL./FAIL .................................................................................... 111

3.47 FANALAM .................................................................................... 113

3.48 FORCE_AIS ................................................................................. 113

3.49 FORCE_SWITCH......................................................................... 114

3.50 GFP_LOF..................................................................................... 115

3.51 HOLDOVER ................................................................................. 116

3.52 HP_AIS ........................................................................................ 117

3.53 HP_BBE_LIMIT ............................................................................ 118

3.54 HP_ES_LIMIT ..............................................................................120

3.55 HP_EXC.......................................................................................122

3.56 HP_NPJE_ALARM .......................................................................124

3.57 HP_PPJE_ALARM .......................................................................125

3.58 HP_RDI........................................................................................126

3.59 HP_SD./HP_SD ...........................................................................127

3.60 HP_SES_LIMIT ............................................................................129

3.61 HP_SLM.......................................................................................130

3.62 HP_SLU. ......................................................................................132

3.63 HP_TIM ........................................................................................133

3.64 HP_TIU. .......................................................................................134

3.65 HP_UNEQ/HP_UNEQ. .................................................................136

3.66 IOP_HIGH/IOPM_HIGH................................................................137

3.67 IOP_LOW/IOP_LOW. ...................................................................139

3.68 LASER_CCT ................................................................................141

3.69 LASER_OFF ................................................................................142

3.70 LASER_TCT ................................................................................143

3.71 LASER_TF ...................................................................................144

3.72 LINK_LOS ....................................................................................145

3.73 LOCK_MAIN.................................................................................147

3.74 LOF_2M .......................................................................................148

3.75 LOOP ...........................................................................................149

3.76 LOOP(T).......................................................................................150

3.77 LOOPL .........................................................................................151

3.78 LOOPL(T).....................................................................................152

3.79 LOOPL_L .....................................................................................153

3.80 LOOP_L .......................................................................................154

3.81 LP_AIS.........................................................................................155

3.82 LP_BBE_LIMIT.............................................................................156

3.83 LP_ES_LIMIT ...............................................................................158

3.84 LP_EXC .......................................................................................159

3.85 LP_LOP .......................................................................................161

3.86 LP_RDI ........................................................................................162

3.87 LP_SD..........................................................................................163

3.88 LP_SES_LIMIT.............................................................................165

3.89 LP_SLM .......................................................................................166

3.90 LP_TIM ........................................................................................167

3.91 LP_UNEQ ....................................................................................168

3.92 LSYN_LOC ..................................................................................169

3.93 LTI. ...............................................................................................170

3.94 M_Asynchronous Active / Standby Alarms ....................................172

3.95 M_SWITCH ..................................................................................175

3.96 MANUAL_SWITCH ......................................................................176

3.97 MCCABORT.................................................................................177

3.98 MCCCUTHROUGH ......................................................................178

3.99 MCCDISABLE ..............................................................................178

3.100 MON1/2/3/4 ..................................................................................179

3.101 MS_AIS........................................................................................180

3.102 MS_BBE_LIMIT............................................................................181

3.103 MS_ES_LIMIT ..............................................................................183

3.104 MS_EXC ......................................................................................185

3.105 MS_RDI .......................................................................................188

3.106 MS_SD.........................................................................................189

3.107 MS_SES_LIMIT............................................................................190

3.108 OOCR ..........................................................................................192

3.109 OTRX_ABSENT ...........................................................................194

3.110 PK_LOS .......................................................................................195

3.111 PORT_MIRROR ...........................................................................196

3.112 POWERALM ................................................................................197

3.113 PPI_LOS ......................................................................................197

3.114 PPS_ALM.....................................................................................199

3.115 PTP_ALM.....................................................................................200

3.116 PTP_CLK_ALM ............................................................................201

3.117 PTP_LOS .....................................................................................202

3.118 PTP_TEST ...................................................................................203

3.119 RCONTEXT_ACCESS_FAIL ........................................................204

3.120 RCONTEXT_PACKET_LOS .........................................................205

3.121 REF_CHANGE.............................................................................206

3.122 RLOS ...........................................................................................207

3.123 RPJE_LIMIT .................................................................................209

3.124 RS_BBE_LIMIT ............................................................................210

3.125 RS_ES_LIMIT .............................................................................. 211

3.126 RS_EXC./RS_EXC.......................................................................213

3.127 RX_LOC.......................................................................................215

3.128 RS_LOF .......................................................................................216

3.129 RS_OOF ......................................................................................217

3.130 RS_SD .........................................................................................218

3.131 RS_SES_LIMIT ............................................................................220

3.132 RS_SF .........................................................................................222

3.133 RS_TIM ........................................................................................223

3.134 RS_TIU./RS_TIU ..........................................................................224

3.135 RX_ERR ......................................................................................226

3.136 SCLK_LOS...................................................................................227

3.137 SCK_LOS/SCK_LOS....................................................................228

3.138 SPI_LOS ......................................................................................229

3.139 SPT_TF........................................................................................231

3.140 SW_FAIL ......................................................................................232

3.141 SWITHCH_LOOP.........................................................................233

3.142 SWR ............................................................................................234

3.143 SWTR ..........................................................................................235

3.144 TRAF_ONLOAD ...........................................................................236

3.145 TEMP_ABNORMAL .....................................................................237

3.146 TEMP_OVER ...............................................................................238

3.147 TEMP_TCT ..................................................................................239

3.148 TF ................................................................................................241

3.149 TOD_CRC_ERR...........................................................................243

3.150 TOD_LOS ....................................................................................244

3.151 TU_AIS ........................................................................................245

3.152 TU_LOM.......................................................................................247

3.153 TU_LOP .......................................................................................249

3.154 TX_ERR.......................................................................................250

3.155 VC_AIS ........................................................................................251

3.156 VC_CSF.......................................................................................253

3.157 VC_LCK .......................................................................................254

3.158 VC_LOC.......................................................................................255

3.159 VC_MMG .....................................................................................256

3.160 VC_RDI........................................................................................257

3.161 VC_SD .........................................................................................258

3.162 VC_SF .........................................................................................259

3.163 VC_UNM ......................................................................................261

3.164 VC_UNP ......................................................................................262

3.165 VCLB_LOS...................................................................................263

3.166 VP_AIS ........................................................................................264

3.167 VP_LCK .......................................................................................265

3.168 VP_LOC.......................................................................................266

3.169 VP_MMG......................................................................................267

3.170 VP_RDI ........................................................................................268

3.171 VP_SD .........................................................................................269

3.172 VP_SF..........................................................................................270

3.173 VP_SSF .......................................................................................271

3.174 VP_UNM ......................................................................................272

3.175 VP_UNP.......................................................................................273

3.176 VPLB_LOS...................................................................................274

3.177 VS_AIS ........................................................................................276

3.178 VS_LCK .......................................................................................277

3.179 VS_LOC.......................................................................................278

3.180 VS_MMG......................................................................................279

3.181 VS_RDI ........................................................................................280

3.182 VS_SD .........................................................................................281

3.183 VS_SF..........................................................................................282

3.184 VS_UNM ......................................................................................283

 3.185 VS_UNP.......................................................................................284

3.186 VSLB_LOS...................................................................................285

4 Performance Handling ................................................................................287

4.1 ALIGNMENT ................................................................................294

4.2 ANNOUNCE_RX ..........................................................................294

4.3 ANNOUNCE_RX_ERR.................................................................295

4.4 ANNOUNCE_TX ..........................................................................296

4.5 BAK_5V .......................................................................................296

4.6 BBE..............................................................................................297

4.7 BBE_HP.......................................................................................298

4.8 BBE_LP .......................................................................................300

4.9 BBE_MS ......................................................................................302

4.10 BBE_RS.......................................................................................304

4.11 BOARD_TEMP.............................................................................306

4.12 CONTEXT_EARLY_PKTS............................................................307

4.13 CONTEXT_LATE_PKTS...............................................................308

4.14 CONTEXT_LOSS_PKTS..............................................................308

4.15 CONTEXT_MALFORMED_PKTS.................................................309

4.16 CONTEXT_MISORDERDROP_PKTS ..........................................310

4.17 CONTEXT_OVERRUN_PKTS...................................................... 311

4.18 CONTEXT_REORDER_PKTS...................................................... 311

4.19 CONTEXT_RX_PKTS ..................................................................312

4.20 CONTEXT_TX_PKTS...................................................................313

4.21 CONTEXT_UNDERRUN_PKTS ...................................................313

4.22 CRC_ERR....................................................................................314

4.23 CSES_HP ....................................................................................315

4.24 CSES_LP .....................................................................................317

4.25 CSES_MS ....................................................................................319

4.26 CSES_RS ....................................................................................321

4.27 DELAY_REQ_RX .........................................................................323

4.28 DELAY_REQ_RX_ERR ................................................................324

4.29 DELAY_REQ_TX..........................................................................325

4.30 DELAY_RESP_RX .......................................................................325

4.31 DELAY_RSP_RX_ERR ................................................................326

4.32 DELAY_RESP_TX........................................................................327

4.33 E1_BBE .......................................................................................327

4.34 E1_ES..........................................................................................329

4.35 E1_HDB3_ERR............................................................................330

4.36 E1_SES .......................................................................................330

4.37 E1_UAS .......................................................................................332

4.38 ES ................................................................................................333

4.39 ES_HP .........................................................................................334

4.40 ES_LP..........................................................................................336

4.41 ES_MS.........................................................................................338

4.42 ES_RS .........................................................................................340

4.43 FAN_CTRM..................................................................................342

4.44 FAN_HTEMP................................................................................342

4.45 FE_CSES_HP ..............................................................................343

4.46 FE_CSES_LP...............................................................................346

4.47 FE_CSES_MS..............................................................................348

4.48 FE_ES_HP...................................................................................350

4.49 FE_ES_LP ...................................................................................352

4.50 FE_ES_MS ..................................................................................354

4.51 FE_SES_HP ................................................................................356

4.52 FE_SES_LP .................................................................................358

4.53 FE_SES_MS ................................................................................360

4.54 FOLLOW_UP_RX ........................................................................362

4.55 FOLLOW_UP_RX_ERR ...............................................................363

4.56 FOLLOW_UP_TX.........................................................................363

4.57 FRAGMENT .................................................................................364

4.58 IOP/IOP. .......................................................................................365

4.59 JABBER .......................................................................................366

4.60 LASER_BIAS ...............................................................................367

4.61 LASER_DIS .................................................................................368

4.62 LASER_TEMP..............................................................................369

4.63 LASER_LEN ................................................................................370

4.64 OFS_RS.......................................................................................370

4.65 OOP .............................................................................................372

4.66 POWER .......................................................................................374

4.67 PACKDELAY_NS .........................................................................374

4.68 PACKDELAY_S ............................................................................375

4.69 PACLDELAYVAR_NS...................................................................376

4.70 PACLDELAYVAR_S .....................................................................378

4.71 PACKLOSR_FAR .........................................................................379

4.72 PACKLOSR_NEAR ......................................................................381

4.73 PJEN_HP .....................................................................................384

4.74 PJEP_HP .....................................................................................385

4.75 REI_HP ........................................................................................387

4.76 REI_LP.........................................................................................389

4.77 REI_MS........................................................................................391

4.78 RPJEN_AU ..................................................................................393

4.79 RPJEP_AU...................................................................................394

4.80 RX_BCAST ..................................................................................396

4.81 RX_BDPK ....................................................................................397

4.82 RX_BYTES./RX_BYTES ..............................................................398

4.83 RX_CRC_ERR .............................................................................399

4.84 RX_DROP....................................................................................400

4.85 RX_FLOW....................................................................................401

4.86 RX_FILTER_DROP ......................................................................401

4.87 RX_GDPK ....................................................................................402

4.88 RX_GFP.......................................................................................402

4.89 RX_GFP_ERR .............................................................................403

4.90 RX_MCAST..................................................................................404

4.91 RX_OF_DROP .............................................................................405

4.92 RX_OTHER_ERR ........................................................................406

4.93 RX_PACKS ..................................................................................406

4.94 RX_PACKS_1024_TO_1518 ........................................................407

4.95 RX_PACKS_1519_TO_MAX ........................................................407

4.96 RX_PACKS_512_TO_1023 ..........................................................408

4.97 RX_PACKS128TO255 ..................................................................409

4.98 RX_PACKS256TO511 ..................................................................409

4.99 RX_PACKS64 ..............................................................................410

4.100 RX_PACKS65TO127....................................................................410

4.101 RX_PAUSE .................................................................................. 411

4.102 RX_PKTS.....................................................................................412

4.103 SES..............................................................................................412

4.104 SES_HP.......................................................................................414

4.105 SES_LP .......................................................................................415

4.106 SES_MS ......................................................................................417

4.107 SES_RS.......................................................................................419

4.108 SMART_FAN_L ............................................................................421

4.109 STAT_OSZ ...................................................................................422

4.110 STAT_USZ ...................................................................................422

4.111 SYNC_RX ....................................................................................423

4.112 SYNC_RX_ERR...........................................................................423

4.113 SYNC_TX.....................................................................................424

4.114 TEMP ...........................................................................................425

4.115 TPJEN_AU...................................................................................426

4.116 TPJEP_AU ...................................................................................427

4.117 TX_BCAST...................................................................................429

4.118 TX_BDPK.....................................................................................430

4.119 TX_BYTES./TX_BYTES ...............................................................431

4.120 TX_FLOW ....................................................................................432

 4.121 TX_GFP .......................................................................................432

4.122 TX_MCAST ..................................................................................433

4.123 TX_NONUCAST_PACKS .............................................................434

4.124 TX_PACKS...................................................................................434

4.125 TX_PACKS_1024_TO_1518.........................................................435

4.126 TX_PACKS_1519_TO_MAX.........................................................435

4.127 TX_PACKS_512_TO_1023...........................................................436

4.128 TX_PACKS128TO255 ..................................................................437

4.129 TX_PACKS256TO511...................................................................437

4.130 TX_PACKS64...............................................................................438

4.131 TX_PACKS65TO127 ....................................................................438

4.132 TX_PAUSE...................................................................................439

4.133 TX_UCAST ..................................................................................440

4.134 UAS .............................................................................................440

4.135 UAS_HP.......................................................................................441

4.136 UAS_LP .......................................................................................443

4.137 UAS_MS ......................................................................................445

4.138 UAS_RS.......................................................................................447

4.139 VC_RX_CV ..................................................................................449

4.140 VC_TX_CV...................................................................................450

4.141 VP_RX_CV ..................................................................................450

4.142 VP_TX_CV...................................................................................451

Appendix A Abbreviations ..........................................................................452

Figures

Figure 1-1 Positions of the ESD protection earth ground fastener, subrack earth
ground pole, and the corresponding signs .........................................3
Figure 1-2 Slide rails..........................................................................................5
Figure 1-3 The dedicated fiber puller..................................................................6
Figure 1-4 No access to Internet ........................................................................9
Figure 1-5 Do not modify protocol settings .......................................................10
Figure 1-6 Do not modify computer protocol property settings........................... 11
Figure 1-7 Do not modify computer name.........................................................12
Figure 1-8 Do not modify LAN settings .............................................................13
Figure 2-1 Procedures of querying the current alarm ........................................36
Figure 2-2 Procedures of querying the alarm history.........................................37
Figure 2-3 Performance parameter collection window ......................................39
Figure 2-4 Querying current performance.........................................................42
Figure 2-5 Procedures of querying the performance history ..............................45
Figure 2-6 The filtering setting GUI...................................................................47
Figure 2-7 Filtering by the line..........................................................................49
Figure 2-8 Filtering by the alarm / performance event .......................................50
Tables

Table 1-1 Safety and warning signs ..................................................................2

Table 1-2 Definitions of alarm levels ...............................................................15
Table 1-3 Alarm list ........................................................................................19
Table 1-4 Performance List.............................................................................28
Table 2-1 Access method for enabling performance gathering function ...........38
Table 2-2 Card performance parameters ........................................................42
Table 2-3 Performance codes of the card errors, packet loss and error
packets...........................................................................................43
Table 2-4 Introductions for configuration items in the filtering setting................47
Table 3-1 M_asynchronous active / standby alarms ......................................172
1 Overview

The following introduces the security precautions, definitions and classifications of

alarms and performance events.

Operation Safety Precautions

Alarm Definition

Alarm Level

Principles for Alarm Handling

Alarm Classification

Performance Classification

Alarm List

Performance List

Version: A 1
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

1.1 Operation Safety Precautions

The following introduces operation safety precautions in the process of equipment

operation. When implementing routine maintenance, you should be familiar with the
operation safety precautions of the equipment, so as to ensure both human body
and equipment safety during the operation.

1.1.1 Safety and Warning Signs

Safety and warning signs are attached to the key position of the CiTRANS 660
subrack. Maintenance staff should know the meanings of the security and warning
signs. Table 1-1 and Figure 1-1 list the meanings and positions of the signs.

Table 1-1 Safety and warning signs

Sign Meaning Location

The ESD protection sign. This sign
reminds the operators to wear an ESD
protection wrist strap, so as to avoid
damage to the equipment caused by
See Figure 1-1.
electrostatic discharge.

The subrack earth ground sign. This

sign marks the connection position of
the subrack earth ground cable.

The laser class sign. This sign marks

the optical source class of the optical
Located on the panels of
interface on a card. The operators
the cards with optical
must prevent the optical source from
interfaces.
entering the eyes directly to avoid
bodily harm.

Warning sign for periodical cleaning of

Located on the panel of
the anti-dust screen. This sign reminds
the subrack’s anti-dust
the operators to clean the anti-dust
screen.
screen periodically.

2 Version: A
 1 Overview

Table 1-1 Safety and warning signs (Continued)

Sign Meaning Location

The fan unit safety alarm sign on the
channel subrack. This sign reminds Located on the panel of
the maintenance staff not to touch the the fan unit.
running fan blades.

This sign reminds the maintenance

Located on the panel of
staff to shut down the PDP before
the AIFJ1 / AIFJ2 power
plugging and unplugging the AIFJ1 /
supply terminal board.
AIFJ2 power supply terminal board.

(1) ESD protection sign (2) ESD protection earth ground fastener

(3) Subrack earth ground sign (4) Earth ground pole

Figure 1-1 Positions of the ESD protection earth ground fastener, subrack earth ground pole,
and the corresponding signs

Version: A 3
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

1.1.2 ESD Protection Measures

Relevant knowledge

The electrostatic discharge can damage electrostatic-sensitive components on the

cards and subracks. Therefore, you must wear the ESD protection wrist strap
(delivered as the accessory with the equipment) before touching any equipment set,
card, or IC (Integrated Circuit) chip and use the ESD protection bags to store cards.

Note:

The ESD protection wrist strap is an accessory delivered with the

equipment.

Safety measure

To wear the ESD protection wrist strap, put its one end around your wrist, and
ensure that the metal fastener of ESD protection wrist strap is in good contact with
the skin and the other end of wrist strap is correctly connected to the ESD protection
earth ground fastener on the mounting ear at the right-hand side of the subrack.

1.1.3 Plugging and Unplugging Cards

u Wear an ESD protection glove or wrist strap (with its plug inserted in the ESD
protection earth ground fastener on the cabinet properly), and keep hands dry
and clean before plugging or unplugging a card.

u When holding a card, do not touch the components and wiring wiring trough on
the card.

u Confirm the following items before plugging cards.

4 Before plugging a card, make sure the slot matches the card and the
corresponding slot is available.

4 Before plugging a card, make sure that no cables or fibers are connected
with the card.

4 Before plugging a card, make sure the insertion direction of cards. Avoid
inserting the card upside down. Keep the side with card nameplate facing
downwards.
4 Version: A
 1 Overview

u Keep in mind the following considerations when inserting cards.

4 Do not insert the card with excessive force so as to avoid distorting pins on
the backplane.

4 When inserting a card, slide the card along the slide rails to avoid short
circuits caused by contact between the components on the card. See
Figure 1-2 for the position of the slide rails.

u Confirm whether the card carries service before unplugging the card. Removing
an in-service card can cause an interruption of services!

(1) Upper slide rail (2) Lower slide rail

Figure 1-2 Slide rails

Version: A 5
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

1.1.4 Operation Safety Rules of a Fiber and an Optical

Interface

Improper operations on the optical fibers and optical fiber connectors may cause
bodily harm to the operator. The following discusses the operation precautions of
connecting optical fibers and cleaning optical fiber connectors.

Using the dedicated fiber puller

Optical fibers are easily damaged if they are plugged or unplugged by hands without
using any tool.

Caution:

The operators should use the dedicated fiber puller to avoid damages to
optical fiber and fiber connector caused by rough handling.

The fiber puller, as the delivery accessory, is similar to tweezers in appearance and
attached with a spring cord, as shown in Figure 1-3.

The fiber puller is secured on the cabinet by a spring cord before delivery. When
plugging / unplugging the fiber, clamp the fiber connector using the fiber puller.

(1) Spring cord (2) Connected to the mounting (3) Dedicated fiber puller
hole on the vertical mounting
flange

Figure 1-3 The dedicated fiber puller

6 Version: A
 1 Overview

Protecting optical modules against high optical power

Do not insert the pigtail into the card’s optical interface when the pigtail’s output
optical power is unknown. To avoid damages to optical modules, just put the pigtail
in the card’s optical interface without connecting them or add an attenuator.

Optical fiber connection

u Before connecting the optical fiber, check whether the optical power meets the
power requirements of the optical interface module. If no, the optical fibers
cannot be connected.

u Before connecting optical fibers, check whether the optical fiber connector
matches the optical interface. If the optical fiber connector does not match the
optical interface, use a compatible connector.

Protecting eyes

Looking directly into its output interface or the end face of the pigtail fiber connected
with it will harm the eyes. Avoid direct light of the pigtail fiber into the eyes.

Avoiding excessive bends of the fiber

Excessive bends and pressures on pigtail fibers will influence the optical power. If
bends are necessary, the fiber bend radius should never be less than 38mm.

Protecting optical interfaces and optical connectors

u Cover the unused optical connectors on optical interfaces and pigtail fibers with
anti-dust caps, so as to protect the maintenance staff's eyes from being hurt
due to looking directly into the optical interfaces or connectors unintentionally
as well as to prevent optical interfaces and connector from being polluted by
dust.

u Cover the optical interfaces on the replaced cards with anti-dust caps in a
timely manner to keep the optical interfaces clean.

Cleaning optical interfaces and connectors

Use dedicated cleaning tools and materials to clean the optical interfaces and
optical fiber connectors.

Version: A 7
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

The following lists some common tools which the maintenance staff can choose
according to their needs.

u Dedicated cleaning solvent (the first choice is the isoamylol alcohol and the
second choice is the isopropyl alcohol).

u Non-woven lens tissue

u Dedicated compressed air

u Cotton swab (cotton for medical purposes or other long-staple cotton)

u Dedicated reel connector cleaner

1.1.5 Electrical Safety Precautions

The following discusses the electrical safety precautions for the maintenance staff,
so as to avoid electrical accidents such as short circuit and grounding failure.

Shorting

u When a shorting occurs, the excessive current surge may damage the
equipment and leave potential silent failures.

u During the operation, avoid metal fillings, water and other conductive materials
getting into the in-service equipment so as to prevent damage to electrical
apparatus and components caused by a short circuit.

u Avoid shorting caused by incorrect connection or small animals (such as rat)

entering the in-service equipment.

Grounding

u Confirm that the protection earth ground bar in the equipment room is grounded
properly.

u Confirm that the equipment is grounded properly.

Power supply

u The DC voltage range of the equipment is -40V to -57V.

u The DC power distribution system should have power failure protection

measures and usually be configured with a storage battery.

8 Version: A
 1 Overview

u Make sure the power is shut down before removing the power cable.

u The power cable should not be exposed. The exposed part should be wrapped
by insulating tape.

u If the operation condition permits, shut down the power first and then perform
other operations.

1.1.6 Operation Safety Rules of the OTNM2000

Operation safety rules of the network management system is described as follows:

u Use UPS power supply to avoid loss of network management data caused by
accidental power failure.

u To shut down the OTNM2000 computer, first exit the operation system normally
and then shut off the power supply.

u The OTNM2000 computer cannot be used for purposes other than network
management. Use of unidentified memory devices should be prohibited so as
to avoid computer viruses.

u Do not delete any files in the network management system randomly or copy
any irrelevant file into the network management computer.

u Do not visit Internet via the network management computer. Doing so may
increase data flow in the network card and hence affects normal network
management data transmission or results in other accidents.

Figure 1-4 No access to Internet

Version: A 9
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u Do not modify the network management computer’s protocol settings,

computer name or LAN settings. Doing so may result in abnormal operation of
network management system.

Figure 1-5 Do not modify protocol settings

10 Version: A
 1 Overview

Figure 1-6 Do not modify computer protocol property settings

Version: A 11
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Figure 1-7 Do not modify computer name

12 Version: A
 1 Overview

Figure 1-8 Do not modify LAN settings

The OTNM2000 safety precautions

u Do not disclose your login user name and password of the OTNM2000 in any
occasion or to anyone else.

u To prevent the lower level users from performing the higher level operations,
the OTNM2000 supports the authority and domain division function. The higher
level users can divide the network into different management domains and
authorizes the lower level users with the management rights on some of the
domains.

Version: A 13
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u Do not modify the completed settings and service configuration in the

OTNM2000 unless necessary, otherwise the operating services may be
interrupted.

u To modify the service configuration, please follow the rules below:

4 Before modifying the configuration, read the NE data from the equipment
and make sure the configuration data on the network management system
and that on the NE are consistent. Back up the network management data
for restoration in case of accidental faults.

4 After the modification, back up the latest network management data.

u Do not exit the OTNM2000 when it is working normally.

Note:

Exiting the network management system does not interrupt traffic in the
network, but precludes centralized control of the networked equipment.

1.2 Alarm Definition

The alarm is the notification and warning when a system parameter reaches the
threshold. Thus any alarms of the equipment should be dealt with promptly to
reduce equipment failures and risks, and to improve the network quality. Users
should handle the alarms following certain principles, so as to clear the alarm and
eliminate faults in the shortest time.

1.3 Alarm Level

The level of an alarm indicates the degree of severity, importance and urgency of an
alarm.

The CiTRANS 660 alarms can be classified into four levels by the OTNM2000. See
Table 1-2 for definitions of all levels as well as corresponding colors of the card
indicator LEDs in the OTNM2000 and the severity degree that each color indicates.

14 Version: A
 1 Overview

Note:

The CiTRANS 660's all alarms and the corresponding classifications are
listed in Alarm List.

Table 1-2 Definitions of alarm levels

Alarm Indicator LEDs Severity

Alarm Level Definition
Color (OTNM2000) Degree

Communication interruption between the CiTRANS

Communica-
660 and the OTNM2000 will lead to the fault alarm
tion No indicator LEDs
that the equipment stops working or is out of
interruption
management.

Fault alarms and event alarms that influence the

Critical alarm overall situation and cause the equipment Red
breakdown.
Fault alarms and event alarms on a card or a line in a
Major alarm Orange
certain region.

General fault alarms and event alarms that describe

whether a card or a line is working normally, e.g. card
Minor alarm Yellow
reset, public resource application failure / overtime
occupation.

Prompt alarm Prompt event alarms like switch alarms. Blue

Note:

Table 1-2 lists the color of the card indicator LEDs in the OTNM2000.
See CiTRANS 660 High-capacity MPLS-TP Platform Hardware
Description for the definition of alarm indicator LEDs on physical cards.

1.4 Principles for Alarm Handling

The following introduces the basic principles for handling alarms.

Version: A 15
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Principle of Restoring First and Repairing Second

u Description: Restoring first and repairing second means restoring the

services first by switching them to the protection path or the standby card and
then repairing faults.

u Application range: This principle is applicable for handling the alarms

influencing services.

Principle of External First and Equipment Second

u Description: External first and equipment second means that while handling
alarms, users should first exclude possible external faults (such as the broken
fiber, terminal equipment fault, power supply fault, or equipment room
environment problem), and then consider faults of this equipment.

u Application range: This principle is applicable for handling alarms caused by

external factors.

Principle of Higher Level First and Lower Level Second

u Description: Higher level first and lower level second means that in the
course of alarm analysis, users should analyze the higher level alarm, such as
the critical alarm and major alarm first, and then the lower level alarm, such as
the minor alarm and prompt alarm. When handling alarms, users should handle
the alarm influencing services first; if this alarm is caused by the higher level
alarm, handle the higher level alarm first.

u Application range: This principle is applicable for handling alarms when higher
level alarms and lower level alarms exist at the same time.

Principle of Majority First and Minority Second

u Description: Majority first and minority second means that users should
handle the majority of alarms of the same type existing in the network
management system first. The handling methods of alarms of the same type
are probably the same. After the majority of alarms of the same type are
eliminated, the alarms existing in the network management system will reduce
greatly. And this can help the supervision and maintenance staffs analyze and
ascertain the valid alarms.

16 Version: A
 1 Overview

u Application range: This principle is applicable for handling alarms when the
majority of alarms of the same type exists.

1.5 Alarm Classification

The alarm classification indicates the alarm source classification. The CiTRANS 660
alarms are classified into the following types:

u QoS alarm: refers to related alarms of the service status and the network
service quality, such as higher order path trace identifier mismatch alarm.

u Communication alarm: refers to related alarms of the NE communication and

the link connection, such as link set-up failure alarm.

u Equipment alarm: refers to related alarms of the equipment hardware, such as

laser transmission failure alarm.

u Environment alarm: refers to related alarms of the power supply system and the
equipment room environment , such as overlow DC voltage alarm.

Note:
The CiTRANS 660's all alarms and the corresponding classifications are
listed in Alarm List.

1.6 Performance Classification

During the normal operation of the optical transport network, the internal or external
factors (such as noise source, dispersion, optical fiber bending and ambient
temperature) may influence the transmission quality (such as bit errors, jitter, shift,
delay and packet loss), i.e. transmission impairment. The transmission impairment
is reflected as various performance events in the OTNM2000.

The CiTRANS 660 performance events mainly include the TDM performance
events, the Ethernet events and other performance events.

u TDM performance event: for monitoring and assessing the status where the
equipment performs a pointer adjustment because of bit errors and jitter.

Version: A 17
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u Ethernet performance: for monitoring and assessing the communication quality

of the Ethernet data service port.

u Other performance: for monitoring and assessing the hardware status and
ambient temperature, etc.

TDM performance events

The TDM performance events include: TDM regenerator section performance event,
multiplex section performance event, higher order path performance event, lower
order path performance event.

Ethernet performance events

The Ethernet performance events include:

u Ethernet performance event

u CES performance event

u L2VPN performance event

u Tunnel performance event

u PW performance event

u LSP performance event

Other performance events

Other performance events include:

u Laser performance event

u Card status performance event

u Temperature performance event

1.7 Alarm List

Table 1-3 lists all CiTRANS 660 alarm codes, levels and the classification.

18 Version: A
 1 Overview

Table 1-3 Alarm list

Alarm Code Name Alarm Level Alarm Classification

Multiplex section BER (bit error ratio)
.MS_EXC. Major alarm QoS alarm
threshold-crossing alarm

Regenerator section (RS) signal

.RS_SD. Minor alarm QoS alarm
deterioration alarm
1PPS_LOS Pulse per second loss alarm Critical alarm Equipment alarm

Alignment error threshold-crossing

ALN_ERR Minor alarm QoS alarm
alarm
APS_MISMATCH APS mismatch alarm Critical alarm Communication alarm
Administrative unit alarm indication
AU_AIS Minor alarm QoS alarm
signal

AU_LOP Administrative unit pointer loss alarm Critical alarm QoS alarm
Administrative unit negative pointer
AU_NPJE_ALARM Major alarm QoS alarm
adjustment threshold-crossing alarm

Administrative unit positive pointer

AU_PPJE_ALARM Major alarm QoS alarm
adjustment threshold-crossing alarm

BACKUP_FAULT Protection path fault alarm Prompt alarm QoS alarm

BAK_5V_FAIL Standby 5V power supply alarm Critical alarm Communication alarm

BCS Broadcast storm suppression Prompt alarm QoS alarm

BKIP_ERR Standby IP address invalid alarm Prompt alarm Communication alarm
Synchronization reference source
BMC_LOS Prompt alarm QoS alarm
loss
Time synchronization path
BMC_SW Prompt alarm QoS alarm
switchover
BRIDGE Bridge connection Minor alarm QoS alarm
Communication
CARD_ABSENT Card not-present alarm Communication alarm
interruption

CARD_SWITCH Active / standby card switching alarm Prompt alarm Communication alarm
CARD_TCT. Card over-temperature alarm Prompt alarm Environment alarm
CARD_TCT Card over-temperature alarm Prompt alarm Environment alarm
CES_PK_LOS Packet loss threshold-crossing alarm Major alarm QoS alarm
CFG_MISMATCH. Configuration mismatch Prompt alarm Equipment alarm

CFG_MISMATCH Configuration mismatch Prompt alarm QoS alarm

Communication
COMFAIL Card communication failure alarm Communication alarm
interruption

CONTEXT_FAIL Link creation failure alarm Critical alarm Communication alarm

Version: A 19
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

CONTEXT_
Local end link packet loss Critical alarm Communication alarm
PACKET_LOS

CONTEXT_
CEC threshold alarm Critical alarm Equipment alarm
PACKET_LIMIT

CRC_ERR CRC check error Minor alarm QoS alarm

CUR_LOCK Current status locking alarm Prompt alarm Communication alarm

DCVOLDOWN DC voltage over-low alarm Critical alarm Environment alarm

DCVOLOVER DC voltage over-high alarm Critical alarm Environment alarm

DZB_IN Terminal board not present Critical alarm QoS alarm
E1_AIS E1 alarm indication signal Minor alarm QoS alarm
E1_ES_LIMIT Errored second threshold-crossing Prompt alarm QoS alarm
E1_LOF E1 out-of-frame alarm Critical alarm Communication alarm
E1_LOS E1 input signal loss alarm Critical alarm Communication alarm
E1_RDI E1 remote defect indication alarm Minor alarm Communication alarm
ETH_LCK Ethernet locking alarm Prompt alarm Communication alarm
Ethernet connection verification
ETH_LOC Critical alarm Environment alarm
signal loss

Ethernet unexpected maintenance

ETH_MMG Minor alarm Communication alarm
entity group

ETH_RDI Ethernet remote failure indication Minor alarm Communication alarm

Ethernet unexpected maintenance
ETH_UNL Minor alarm QoS alarm
entity group level

Ethernet unexpected maintenance

ETH_UNM Minor alarm Communication alarm
entity group end point

ETH_UNP Ethernet time interval mismatch Minor alarm Communication alarm

Ethernet loopback signal timeout
ETHLB_LOS Prompt alarm Environment alarm
alarm
fDISABLE f interface DISABLE Prompt alarm QoS alarm

fRDONLY f interface read only Prompt alarm QoS alarm

FAIL. Card failure alarm Critical alarm Environment alarm
FAIL Card failure alarm Critical alarm Communication alarm
FANALAM Fan alarm Critical alarm Communication alarm
FORCE_AIS Forced transmission AIS Prompt alarm Communication alarm
FORCE_SWITCH Forced switch Prompt alarm QoS alarm
GFP_LOF GFP out-of-frame Minor alarm QoS alarm

20 Version: A
 1 Overview

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

HOLDOVER Clock entering holdover status Prompt alarm QoS alarm
HP_AIS Higher order path alarm indication Minor alarm QoS alarm
Higher order path background block
HP_BBE_LIMIT Prompt alarm QoS alarm
error threshold-crossing alarm

Higher order path errored second

HP_ES_LIMIT Warning alarm QoS alarm
threshold-crossing alarm

Higher order path bit error ratio

HP_EXC Major alarm QoS alarm
threshold-crossing alarm

Higher order path negative pointer

HP_NPJE_ALARM Major alarm QoS alarm
adjustment threshold-crossing alarm

Higher order path positive pointer

HP_PPJE_ALARM adjustment threshold-crossing Major alarm QoS alarm
alarm　
Higher order path remote defect
HP_RDI Minor alarm QoS alarm
indication alarm
Higher order path signal degradation
HP_SD. Minor alarm QoS alarm
alarm
Higher order path signal degradation
HP_SD Critical alarm QoS alarm
alarm
Higher order path severely errored
HP_SES_LIMIT Prompt alarm QoS alarm
second threshold-crossing alarm

Higher order path signal label

HP_SLM Critical alarm QoS alarm
mismatch alarm
Higher order path signal label
HP_SLU. Major alarm Communication alarm
unstable alarm
Higher order path trace identifier
HP_TIM Critical alarm QoS alarm
mismatch alarm
Higher order path trace identifier
HP_TIU. Major alarm QoS alarm
unstable alarm
HP_UNEQ Higher order path unequipped alarm Minor alarm QoS alarm
HP_UNEQ. Higher order path unequipped alarm Critical alarm Communication alarm
IOP_HIGH Input optical power over-high alarm Major alarm Equipment alarm

IOP_HIGH. Input optical power over-high alarm Minor alarm Communication alarm
IOP_LOW Input optical power over-low alarm Major alarm Equipment alarm

IOP_LOW. Input optical power over-low alarm Minor alarm Communication alarm
Laser bias current threshold-crossing
LASER_CCT Minor alarm Equipment alarm
alarm

Version: A 21
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

LASER_OFF Laser soft shutoff alarm Critical alarm Equipment alarm

Laser temperature threshold-

LASER_TCT Minor alarm Equipment alarm
crossing alarm

LASER_TF Laser transmission failure alarm Critical alarm Equipment alarm

LINK_LOS Connection signal loss alarm Critical alarm QoS alarm

LOCK_MAIN Lock-to-main Prompt alarm Communication alarm
LOF_2M E1 signal loss of frame Critical alarm Communication alarm

LOOP Equipment loopback alarm Prompt alarm QoS alarm

Tributary loopback or equipment
LOOP(T) Prompt alarm Communication alarm
loopback

LOOPL Line loopback Prompt alarm QoS alarm

LOOPL(T) Tributary line loopback Prompt alarm Communication alarm
LOOPL_L Aggregate line loopback alarm Prompt alarm Communication alarm
LOOP_L Aggregate equipment loopback Prompt alarm Communication alarm
LP_AIS Lower order path alarm indication Minor alarm QoS alarm
Lower order path background block
LP_BBE_LIMIT Prompt alarm Equipment alarm
error threshold-crossing alarm

Lower order path errored second

LP_ES_LIMIT Prompt alarm Equipment alarm
threshold-crossing alarm

Lower order path bit error ratio

LP_EXC Major alarm QoS alarm
threshold-crossing alarm

LP_LOP Lower order path pointer loss alarm Critical alarm QoS alarm
Lower order path remote defect
LP_RDI Minor alarm QoS alarm
indication alarm
Lower order path signal degradation
LP_SD Minor alarm QoS alarm
alarm
Lower order path severely errored
LP_SES_LIMIT Prompt alarm Equipment alarm
second threshold-crossing alarm

Lower order path signal label

LP_SLM Critical alarm QoS alarm
mismatch alarm
Lower order path trace identifier
LP_TIM Critical alarm QoS alarm
mismatch alarm
LP_UNEQ Lower order path unequipped alarm Minor alarm QoS alarm
LSYN_LOC Line synchronous clock loss Critical alarm QoS alarm

LTI Timing input loss Critical alarm QoS alarm

22 Version: A
 1 Overview

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

Asynchronous active / standby
M_BADDRDIF Critical alarm QoS alarm
management configuration

Asynchronous active / standby

M_BAREADIF Critical alarm QoS alarm
extension domain configuration

Asynchronous active / standby

M_BCFGRDIF Critical alarm QoS alarm
equipment configuration

Asynchronous active / standby cross-

M_BCROSDIF Critical alarm QoS alarm
connect configuration

Asynchronous active / standby

M_BCTRDIF Critical alarm QoS alarm
external terminal configuration

Asynchronous active / standby f

M_BFENBDIF Critical alarm QoS alarm
enable configuration

Asynchronous active / standby MCC

M_BMCCDIF Critical alarm QoS alarm
configuration

Asynchronous active / standby MCC

M_BMCCIRDIF Critical alarm QoS alarm
interruption configuration

Asynchronous active / standby MCC

M_BMCCSFDIF Critical alarm QoS alarm
shut-down configuration

Asynchronous active / standby MCF

M_BMCFRDIF Critical alarm QoS alarm
configuration

Asynchronous active / standby

M_BSTRURDIF Critical alarm QoS alarm
structure configuration

Asynchronous active / standby

M_SADDRDIF Prompt alarm QoS alarm
management configuration

Asynchronous active / standby

M_SAREADIF Prompt alarm QoS alarm
extension domain configuration

Asynchronous active / standby

M_SCFGRDIF Prompt alarm QoS alarm
equipment configuration

Asynchronous active / standby cross-

M_SCROSDIF Prompt alarm QoS alarm
connect configuration

Asynchronous active / standby

M_SCTRDIF Prompt alarm QoS alarm
external terminal configuration

Asynchronous active / standby f

M_SFENBDIF Prompt alarm QoS alarm
enable configuration

Asynchronous active / standby MCC

M_SMCCDIF Prompt alarm QoS alarm
configuration

Version: A 23
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

Asynchronous active / standby MCC
M_SMCCIRDIF Prompt alarm QoS alarm
interruption configuration

Asynchronous active / standby MCC

M_SMCCSFDIF Prompt alarm QoS alarm
shut-down configuration

Asynchronous active / standby MCF

M_SMCFRDIF Prompt alarm QoS alarm
configuration

Asynchronous active / standby

M_SSTRURDIF Prompt alarm QoS alarm
structure configuration

Active / standby management card

M_SWITCH Prompt alarm Equipment alarm
switching alarm

MANUAL_SWITCH Manual switch Prompt alarm QoS alarm

MCCABORT MCC interruption alarm Prompt alarm QoS alarm

MCCCUTHROUGH MCC pass-through alarm Prompt alarm Communication alarm

MCCDISABLE MCC shutdown alarm Prompt alarm Communication alarm

MON1 / 2 / 3 / 4 External monitoring event 1 / 2 / 3 / 4 Critical alarm QoS alarm

MS_AIS Multiplex section alarm indication Minor alarm QoS alarm
Multiplex section background block
MS_BBE_LIMIT Prompt alarm QoS alarm
error threshold-crossing alarm

Multiplex section errored second

MS_ES_LIMIT Prompt alarm QoS alarm
threshold-crossing alarm

MS_EXC Multiplex section excessive bit error Critical alarm QoS alarm
Multiplex section remote defect
MS_RDI Minor alarm Communication alarm
indication alarm
Multiplex section signal degradation
MS_SD Minor alarm Equipment alarm
alarm
Multiplex section severely errored
MS_SES_LIMIT Prompt alarm QoS alarm
second threshold-crossing alarm

Lock source frequency exceeding the

OOCR Critical alarm Equipment alarm
lock range

OTRX_ABSENT Optical module not-present alarm Critical alarm Equipment alarm

Packet loss rate threshold-crossing

PK_LOS Critical alarm QoS alarm
alarm
PORT_MIRROR Port mirroring Prompt alarm Communication alarm
POWERALM Power failure alarm Critical alarm QoS alarm
Signal loss alarm of the PDH
PPI_LOS Critical alarm QoS alarm
physical interface

24 Version: A
 1 Overview

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

PPS_ALM PPS abnormal Major alarm Equipment alarm

PTP_ALM Abnormal time synchronization Minor alarm QoS alarm

PTP_CLK_ALM Synchronous clock abnormal Major alarm QoS alarm
Accurate time synchronization loss
PTP_LOS Critical alarm Communication alarm
alarm
PTP_TEST Time synchronization test module Prompt alarm QoS alarm
RCONTEXT_
Remote link access failure alarm Minor alarm QoS alarm
ACCESS_FAIL

RCONTEXT_
Remote link packet loss alarm Minor alarm Communication alarm
PACKET_LOS

REF_CHANGE Clock reference source change Prompt alarm QoS alarm

RLOS Input optical signal loss Critical alarm Equipment alarm

Pointer adjustment threshold-

RPJE_LIMIT Prompt alarm QoS alarm
crossing alarm

Regenerator section background

RS_BBE_LIMIT Prompt alarm QoS alarm
block error threshold-crossing alarm

Regenerator section errored second

RS_ES_LIMIT Prompt alarm QoS alarm
threshold-crossing alarm

Regenerator section bit error ratio

RS_EXC. Major alarm QoS alarm
threshold-crossing alarm

Regenerator section bit error ratio

RS_EXC Critical alarm QoS alarm
threshold-crossing alarm

Regenerator section encoding loss

RS_LOC Critical alarm QoS alarm
alarm
Regenerator section frame loss
RS_LOF Critical alarm QoS alarm
alarm
Regenerator section out-of-frame
RS_OOF Critical alarm QoS alarm
alarm
Regenerator section signal
RS_SD Critical alarm QoS alarm
degradation alarm

Regeneration section severely

RS_SES_LIMIT errored second threshold-crossing Prompt alarm QoS alarm
alarm
Regenerator section signal loss
RS_SF Critical alarm Communication alarm
alarm
Regenerator section trace identifier
RS_TIM Critical alarm Equipment alarm
mismatch alarm

Version: A 25
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

Regenerator section trace identifier
RS_TIU. Major alarm QoS alarm
unstable alarm
Regenerator section trace identifier
RS_TIU Critical alarm QoS alarm
unstable alarm
Received error packet crossing
RX_ERR Minor alarm QoS alarm
threshold
SCLK_LOS System clock loss alarm Critical alarm Communication alarm
SCK_LOS System clock loss alarm Major alarm QoS alarm
SCK_LOS System clock loss alarm Critical alarm QoS alarm
TDM physical interface signal loss
SPI_LOS Critical alarm QoS alarm
alarm
TDM physical interface signal
SPT_TF Critical alarm QoS alarm
transmitting failure alarm

SW_FAIL Switching failure alarm Critical alarm QoS alarm

SWITHCH_LOOP Switch loop alarm Prompt alarm QoS alarm

SWR Switching received alarm Minor alarm QoS alarm

SWTR Wait to restore (WTR) alarm Minor alarm Equipment alarm

TRAF_ONLOAD Traffic loading alarm Prompt alarm Equipment alarm

TEMP_ABNORMAL Temperature abnormal alarm Critical alarm QoS alarm

TEMP_OVER Over-temperature alarm Critical alarm Communication alarm
Card temperature threshold-crossing
TEMP_TCT Critical alarm QoS alarm
alarm
TF Tx failure alarm Critical alarm QoS alarm
TOD_CEC_ERR ToD CRC error Major alarm Equipment alarm

TOD_LOS ToD loss Major alarm Equipment alarm

TU_AIS Tributary unit alarm indicator LEDs Minor alarm QoS alarm
TU_LOM Tributary unit multiframe loss Critical alarm QoS alarm
TU_LOP Tributary unit pointer loss Critical alarm QoS alarm
Tx error packet threshold-crossing
TX_ERR Minor alarm QoS alarm
alarm
MPLS-TP virtual channel alarm
VC_AIS Minor alarm Communication alarm
indication signal

MPLS-TP virtual channel client layer

VC_CSF Minor alarm Communication alarm
signal loss alarm

VC_LCK MPLS-TP virtual channel lock alarm Prompt alarm Communication alarm

26 Version: A
 1 Overview

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

MPLS-TP virtual channel connectivity
VC_LOC Critical alarm Communication alarm
verification signal loss alarm

MPLS-TP virtual channel unexpected

VC_MMG Minor alarm Communication alarm
maintenance entity group

MPLS-TP virtual channel far end fault

VC_RDI Minor alarm Communication alarm
indication
MPLS-TP virtual channel signal
VC_SD Major alarm Communication alarm
degradation alarm

MPLS-TP virtual channel signal

VC_SF Major alarm Communication alarm
failure alarm
MPLS-TP virtual channel unexpected
VC_UNM Minor alarm Communication alarm
maintenance entity group end point

MPLS-TP virtual channel time

VC_UNP Minor alarm Communication alarm
interval mismatch alarm
MPLS-TP virtual channel loopback
VCLB_LOS Prompt alarm QoS alarm
signal time-out alarm

MPLS-TP virtual path alarm

VP_AIS Minor alarm Communication alarm
indication signal

VP_LCK MPLS-TP virtual path lock alarm. Prompt alarm Communication alarm
MPLS-TP virtual path connectivity
VP_LOC Critical alarm QoS alarm
verification signal

MPLS-TP virtual path unexpected

VP_MMG Minor alarm Communication alarm
maintenance entity group

MPLS-TP virtual path far end fault

VP_RDI Minor alarm QoS alarm
indication alarm
MPLS-TP virtual path signal
VP_SD Major alarm Communication alarm
degradation alarm

MPLS-TP virtual path signal failure

VP_SF Major alarm Communication alarm
alarm
MPLS-TP virtual path service layer
VP_SSF Critical alarm Communication alarm
signal failure alarm

MPLS-TP virtual path unexpected

VP_UNM maintenance entity group end point Minor alarm Communication alarm
alarm
MPLS-TP virtual path time interval
VP_UNP Minor alarm QoS alarm
mismatch alarm
MPLS-TP virtual path loopback
VPLB_LOS Prompt alarm QoS alarm
signal time-out alarm

Version: A 27
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-3 Alarm list (Continued)

Alarm Code Name Alarm Level Alarm Classification

MPLS-TP virtual section alarm
VS_AIS Minor alarm Communication alarm
indication signal

VS_LCK MPLS-TP virtual section lock alarm Prompt alarm Communication alarm
MPLS-TP virtual section connectivity
VS_LOC Critical alarm QoS alarm
verification signal loss alarm

MPLS-TP virtual section unexpected

VS_MMG Minor alarm Communication alarm
maintenance entity group

MPLS-TP virtual section far end fault

VS_RDI Minor alarm QoS alarm
indication
MPLS-TP virtual section signal
VS_SD Major alarm Equipment alarm
degradation alarm

MPLS-TP virtual section signal failure

VS_SF Major alarm Equipment alarm
alarm
MPLS-TP virtual section unexpected
VS_UNM Minor alarm Communication alarm
maintenance entity group end point

MPLS-TP virtual section time interval

VS_UNP Minor alarm QoS alarm
mismatch alarm
MPLS-TP virtual section loopback
VSLB_LOS Prompt alarm QoS alarm
signal time-out alarm

1.8 Performance List

The CiTRANS 660's performance codes and relevant alarms are listed in Table 1-4.

Table 1-4 Performance List

Performance Code Performance Name Relevant Alarm

ALIGNMENT ALIGNMENT packet count -

ANNOUNCE_RX ANNOUNCE message received packet count

ANNOUNCE_RX_ERR ANNOUNCE message Rx error packet count -

ANNOUNCE_TX ANNOUNCE message Tx packet count

BAK_5V Backup 5V voltage BAK_5V_FAIL

BBE Background errored second -

BBE_HP Background block error of the higher order path HP_SD, HP_EXC

BBE_LP Background block error of the lower order path LP_SD, LP_EXC

BBE_MS Background block error of the multiplex section MS_SD, MS_EXC

28 Version: A
 1 Overview

Table 1-4 Performance List (Continued)

Performance Code Performance Name Relevant Alarm

BBE_RS Background block error of the regenerator section RS_SD, RS_EXC

BOARD_TEMP Card temperature TEMP_TCT

CONTEXT_EARLY_PKTS The number of early packets received by the link

-
CONTEXT_LATE_PKTS The number of late packets received by the link

CONTEXT_
CONTEXT_LOSS_PKTS The number of lost packets on the link
PACKET_LOS

CONTEXT_
The number of malformed packets on the link
MALFORMED_PKTS

CONTEXT_
The number of disorder packets discarded by the link
MISORDERDROP_PKTS

CONTEXT_OVERRUN_
The number of overflow packets on the link
PKTS
-
CONTEXT_REORDER_
The number of reordered Rx packets on the link
PKTS
CONTEXT_RX_PKTS The number of packets received by the link

CONTEXT_TX_PKTS The number of the packets transmitted by the link

CONTEXT_UNDERRUN_
The number of empty packets inserted in the link
PKTS
CRC_ERR CRC check error CRC_ERR

CSES_HP Continuous severely errored second of the higher order path HP_SD, HP_EXC

CSES_LP Continuous severely errored second of the lower order path LP_SD, LP_EXC

CSES_MS Continuous severely errored second of the multiplex section MS_SD, MS_EXC

CSES_RS Continuous severely errored second of the regenerator section RS_SD, RS_EXC

DELAY_REQ_RX The count of DELAY_REQ packets received

DELAY_REQ_RX_ERR The count of error DELAY_REQ packets received

DELAY_REQ_TX The count of DELAY_REQ packets transmitted

-
DELAY_RESP_RX The count of DELAY_RESP packets received

DELAY_RSP_RX_ERR The count of error DELAY_RESP packets received

DELAY_RESP_TX The count of DELAY_RESP packets transmitted

E1_BBE Background errored block

E1_ES Errored second (ES) E1_ES_LIMIT

E1_HDB3_ERR The count of HDB3 errors

E1_SES Severely errored second
-
E1_UAS Unavailable second

Version: A 29
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-4 Performance List (Continued)

Performance Code Performance Name Relevant Alarm

ES Errored second (ES)

ES_HP Errored second of the higher order path HP_SD, HP_EXC

ES_LP Errored second of the lower order path LP_SD, LP_EXC

ES_MS Errored second of the multiplex section MS_SD, MS_EXC

ES_RS Regenerator section errored seconds RS_SD, RS_EXC

FAN_CTRM Fan control mode -

FANALM, TEMP_
FAN_HTEMP Highest temperature in the fan area OVER, TEMP_
ABNORMAL
Remote continuous severely errored second of the higher order
FE_CSES_HP
path

Remote continuous severely errored second of the lower order

FE_CSES_LP
path

Remote continuous severely errored second of the multiplex

FE_CSES_MS
section
FE_ES_HP Remote errored second of the higher order path

FE_ES_LP Remote errored second of the lower order path

FE_ES_MS Remote errored second of the multiplex section -

FE_SES_HP Remote severely errored second of the higher order path

FE_SES_LP Remote severely errored second of the lower order path

FE_SES_MS Remote severely errored second of the multiplex section

FOLLOW_UP_RX The count of FOLLOW_UP packets received

FOLLOW_UP_RX_ERR The count of error FOLLOW_UP packets received

FOLLOW_UP_TX The count of FOLLOW_UP packets transmitted

FRAGMENT Fragment packets

IOP Input optical power

IOP_LOW, IOP_
IOP. Input optical power
HIGH
JABBER Jabbers packets statistics -
LASER_BIAS Laser bias current
LASER_DIS Laser transmission distance LASER_CCT
LASER_LEN Laser working wavelength

LASER_TEMP Laser working temperature

OFS_RS Out-of-frame seconds of the regenerator section

-
OOP Output optical power

30 Version: A
 1 Overview

Table 1-4 Performance List (Continued)

Performance Code Performance Name Relevant Alarm

DCVOLDOWN,
POWER Power supply voltage of the cabinet rack
DCVOLOVER
PACKDELAY_NS Delay nanosecond

PACKDELAY_S Delay second

PACLDELAYVAR_NS Delay variation nanosecond

-
PACLDELAYVAR_S Delay variation second

PACKLOSR_FAR Far end packet loss rate

PACKLOSR_NEAR Near end packet loss rate

The count of the negative pointer adjustment of the higher order

PJEN_HP
path
-
The count of the positive pointer adjustment of the higher order
PJEP_HP
path

REI_HP The far end bit error indication of the higher order path HP_RDI

REI_LP The far end bit error indication of the lower order path LP_RDI

REI_MS The far end bit error indication of the multiplex section. MS_RDI

RPJEN_AU The Rx negative pointer adjustment of the administrative unit AU_LOP

RPJEP_AU The Rx positive pointer adjustment of the administrative unit AU_LOP

RX_BCAST The number of broadcast packets received -

RX_BDPK The number of error packets received RX_ERR

RX_BYTES/RX_BYTES. The total number of received bytes -

RX_DROP The number of lost packets PK_LOS

RX_FILTER_DROP The number of received filtered lost packets

RX_FLOW Received traffic

RX_GDPK The number of received good packets

RX_GFP The number of received GFP packets

RX_GFP_ERR Received GFP error packets threshold-crossing

RX_MCAST The number of multicast packets received

-
RX_OF_DROP The number of received overflow lost packets

RX_OTHER_ERR The number of received other errored packets.

RX_PACKS The total number of received packets

RX_PACKS_1024_TO_
Received packets (1024 to 1518 bytes)
1518
RX_PACKS_1519_TO_
Received packets (1519 to MAX bytes)
MAX

Version: A 31
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 1-4 Performance List (Continued)

Performance Code Performance Name Relevant Alarm

RX_PACKS_512_TO_
Received packets (512 to 1023 bytes)
1023
RX_PACKS128TO255 Received packets (128 to 255 bytes)

RX_PACKS256TO511 Received packets (256 to 511 bytes)

RX_PACKS64 Received packets (64 bytes)

RX_PACKS65TO127 Received packets (65 to 127 bytes)

RX_PAUSE The number of received PAUSE frames

RX_PKTS The total number of received packets

SES Severely errored second -

SES_HP Severely errored second of the higher order path HP_SD, HP_EXC

SES_LP Severely errored second of the lower order path LP_SD, LP_EXC

SES_MS Severely errored second of the multiplex section MS_SD, MS_EXC

SES_RS Regenerator section severely errored second RS_SD, RS_EXC

SMART_FAN_L Intelligent fan speed FANALM

STAT_OSZ Over sized packet statistics
-
STAT_USZ Under sized packet statistics

SYNC_RX The count of SYNC packets received

SYNC_RX_ERR The count of error SYNC packets received -

SYNC_TX The count of SYNC packets transmitted

TEMP_OVER,
TEMP The EMU temperature
TEMP_ABNORMAL

TPKEN_AU The Rx negative pointer adjustment of the administrative unit

-
TPJEP_AU The Rx positive pointer adjustment of the administrative unit

TX_BCAST The number of broadcast packets transmitted

TX_BDPK The number of error packets transmitted

TX_BYTES/TX_BYTES. The total number of transmitted bytes

TX_FLOW The Tx traffic

TX_GFP The number of GFP packets transmitted
-
TX_MCAST The count of multicast packets transmitted

TX_NONUCAST_PACKS The number of transmitted non-unicast packets

TX_PACKS The total number of transmitted packets

TX_PACKS_1024_TO_
Transmitted packets (1024 to 1518 bytes)
1518

32 Version: A
 1 Overview

Table 1-4 Performance List (Continued)

Performance Code Performance Name Relevant Alarm

TX_PACKS_1519_TO_
Transmitted packets (1519 to MAX bytes)
MAX
TX_PACKS_512_TO_
Transmitted packets (512 to 1023 bytes)
1023
TX_PACKS128TO255 Transmitted packets (128 to 255 bytes)

TX_PACKS256TO511 Transmitted packets (256 to 511 bytes)

TX_PACKS64 Transmitted packets (64 bytes)

TX_PACKS65TO127 Transmitted packets (65 to 127 bytes)

TX_PAUSE The number of transmitted PAUSE frames

TX_UCAST The number of transmitted unicast packets

UAS_HP The unavailable seconds of the higher order path HP_EXC

UAS_LP The unavailable seconds of the lower order path LP_EXC

UAS_MS The unavailable seconds of the multiplex section MS_EXC

UAS_RS The unavailable seconds of the regenerator section RS_EXC

The count of the CV packets received by the MPLS-TP virtual

VC_RX_CV
channel
The count of the CV packets transmitted by the MPLS-TP virtual
VC_TX_CV
channel
-
The count of the CV packets received by the MPLS-TP virtual
VP_RX_CV
path

The count of the CV packets transmitted by the MPLS-TP virtual

VP_TX_CV
path

Version: A 33
2 Basic Operations on the Alarm /
Performance Event

The following introduces the basic operations on alarms / performance events,

including the query and filtering of alarms and performance events.

Querying Alarm

Enabling the Performance Parameter Collection Function

Query Performance

Filtering the Card Alarm / Performance Event

34 Version: A
 2 Basic Operations on the Alarm / Performance Event

2.1 Querying Alarm

The following introduces how to query alarms in the OTNM2000.

2.1.1 Querying Current Alarms

View current alarms regularly to isolate and eliminate faults in a timely manner.

Maintenance cycle

Daily

Tool / Instrument

The OTNM2000

Prerequisite

u The time synchronizes with the OTNM2000.

u The operator has the middle or above network management right.

Procedure

1. Double-click the icon on the server desktop, and enter the user name
and password, and access the OTNM2000 window.

2. Click Alarm→Current Alarm View in the menu bar to bring up the operational
tree pane, as shown in Figure 2-1.

3. Select the object to be queried in the operational tree pane, as shown in

Figure 2-1.

4. Click on the top of the object tree in the operational tree pane to view the
current alarm of the selected object, as shown in Figure 2-1.

Version: A 35
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Figure 2-1 Procedures of querying the current alarm

5. Record the check result in the routine maintenance worksheet.

Reference standard

No abnormal current alarms exist in the equipment.

Exception handling

If current alarms exist in the system, users can refer to CiTRANS 660 High-capacity
MPLS-TP Platform Alarm and Performance Reference for troubleshooting.

2.1.2 Querying Alarm History

The maintenance personnel can obtain the abnormal data in the past by querying
the alarm history to guide the current maintenance operation.

Maintenance cycle

Daily

Tool / Instrument

The OTNM2000

36 Version: A
 2 Basic Operations on the Alarm / Performance Event

Prerequisite

u The time synchronizes with the OTNM2000.

u The operator has the middle or above network management right.

Procedure

1. Double-click the icon on the server desktop, enter the user name and
password, and access the OTNM2000 window.

2. Click Alarm→Alarm History View in the menu bar to bring up the operational
tree pane, as shown in Figure 2-2.

3. Select the object to be queried in the operational tree pane, as shown in

Figure 2-2.

4. Click on the top of the object tree in the operational tree pane to view the
current alarm of the selected object, as shown in Figure 2-2.

Figure 2-2 Procedures of querying the alarm history

5. Record the check result in the routine maintenance worksheet.

Reference standard

No critical alarms or major alarms that occur frequently exist in the system.

Version: A 37
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Exception handling

If a critical alarm or a major alarm has been frequently occurring on the system for a
period of time, users should keep a record of its occurrence and analyze the system
for possible silent failures, so as to eliminate the potential problems in a timely
manner and reduce the risks that will affect the reliable operation of the equipment.

See CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance

Reference for the detailed processing of alarms.

2.2 Enabling the Performance Parameter

Collection Function

Enabling the performance parameter collection function is a prerequisite for

querying the historical performance data. This operation is usually implemented
during the equipment commissioning or capacity expansion.

Tool / Instrument

The OTNM2000

Prerequisite

The operator has the middle or above network management right.

Procedure

1. Double-click the icon of the OTNM2000 on the desktop, and enter the
username and password (both are 1 by default) in the dialog box that appears
to access the OTNM2000 window.

2. Select the access method in Table 2-1 to open the Performance Gathering
tab as shown in Figure 2-3.

Table 2-1 Access method for enabling performance gathering function

Operation Item Access Method

Open the Performance Click Performance→Performance Collection Settings to
Gathering tab open the PM Collection tab.

38 Version: A
 2 Basic Operations on the Alarm / Performance Event

Table 2-1 Access method for enabling performance gathering function (Continued)

Operation Item Access Method

Click Management Tool→Performance Management→
Performance Collection Settings in the Operation Tree to
open the PM Collection tab.

Figure 2-3 Performance parameter collection window

3. Select an NE or part in the Operation Tree pane and click Add in the PM
Collection tab. The PM Collection tab will display the corresponding
configuration items of the corresponding NE or part.

4. Double-click From Time and To Time of each NE or part in the Performance

Gathering tab to set the gathering time; and select 15-minute Performance
History Statistics Enable and 24 hour Performance.

Note:
The starting time should be later than the current time of the OTNM2000
and the NE.

5. Click Save after setting the time for the NE performance parameter collection
and click OK in the Command Manager alert box that appears subsequently to
save the configuration.

6. Record in the routine maintenance worksheet.

Version: A 39
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2.3 Query Performance

Query the current performance and the performance history via the OTNM2000 to
detect any silent failures in a timely manner and ensure the normal operation of the
equipment.

2.3.1 Querying Current Performance

By querying the reported performance, users can ascertain whether the equipment
is in normal operation and eliminate silent failures in a timely manner. Generally
users should query the performance of the NMUJ1 card and the service interface
card.

u Query the NMUJ1 card’s performance: Check whether the equipment’s

temperature and power voltage is normal.

u Query the service interface card's performance: Obtain the error count of the
system.

Maintenance cycle

Daily

Tool / Instrument

The OTNM2000

Prerequisite

u The NE time synchronizes with the OTNM2000.

u The OTNM2000 performance gathering function is enabled.

u The operator has the middle or above network management right.

40 Version: A
 2 Basic Operations on the Alarm / Performance Event

Note:

Users should enable the performance parameter collection before

querying the current performance of the network block, NE and the card.
See Enabling the Performance Parameter Collection Function for
detailed operations of enabling the performance parameter collection.

Procedure

1. Double-click the icon on the server desktop, enter the user name and
password, and access the OTNM2000 window.

2. Enter the current performance GUI.

4 Query the current performance of NE: Right-click the NE object in the

Logical Tree on the left side of the GUI and select Current Performance
in the shortcut menu to display the current performance.

4 Query the current performance of card: Click the corresponding card in the
subrack view and click Current Performance in the Task Pane on the
right side to display the current performance of the card, as shown in
Figure 2-4.

Version: A 41
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Figure 2-4 Querying current performance

3. Record the check result in the routine maintenance worksheet.

Reference standard

u Table 2-2 lists the normal range of performance parameters, such as

temperature, voltage and optical power.

u Table 2-3 lists the related performance codes and the corresponding names,
such as bit errors, packet loss and error packet.

Table 2-2 Card performance parameters

Performance
Card Type Performance Name Recommended Value
Code
TEMP The EMU temperature 10℃ to 50℃
Network
Power voltage for the
management POWER -41V to -56V
cabinet rack
signaling
Highest temperature in the
control card FAN_HTEMP 10℃ to 50℃
fan area
LASER_TEMP Laser working temperature 0℃ to 40℃
Optical
Refer to the optical
interface card Input and output optical
IOP, OOP module interface
power
specifications.

42 Version: A
 2 Basic Operations on the Alarm / Performance Event

Table 2-3 Performance codes of the card errors, packet loss and error packets

Performance Code Performance Name

E1_HDB3_ERR The count of HDB3 errors
BBE_HP Background block error of the higher order path

BBE_LP Background block error of the lower order path

BBE_MS Background block error of the multiplex section

BBE_RS Background block error of the regenerator section

CRC_ERR CRC check error

REI_HP Remote bit error indication of the higher order path

REI_LP Remote bit error indication of the lower order path

REI_MS Remote bit error indication of the multiplex section

JABBEER Jabbers packet statistics

FRAGMENT The number of fragment packets

STAT_OSZ Over sized packet statistics

STAT_USZ Under sized packet statistics

RX_DROP The number of received lost packets

Exception handling

Refer to CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance

Reference if the performance parameter is abnormal.

2.3.2 Querying Performance History

The maintenance personnel can obtain the network operation efficiency data by
querying and analyzing the performance history, so as to forecast the network future
performance and help the further network planning.

Maintenance cycle

Daily

Tool / Instrument

The OTNM2000

Version: A 43
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Prerequisite

u The NE time synchronizes with the OTNM2000.

u The operator has the middle or above network management right.

u The NE performance parameter collection has been enabled.

Note:

Users should enable the performance parameter collection before

querying the performance history of the network block, NE and the card.
See Enabling the Performance Parameter Collection Function for
detailed operations of enabling the performance parameter collection.

Procedure

1. Double-click the icon on the server desktop, enter the user name and
password, and access the OTNM2000 window.

2. Click Performance→History Performance View→History 15-minute

Performance / History 24-hour Performance, as shown in Figure 2-5.

3. Select the object to be queried in the Operational Tree pane, as shown in

Figure 2-5.

4. Click the icon at the top of the Operational Tree pane to view the selected
object's History 15-minute Performance / History 24-hour Performance, as
shown in Figure 2-5.

44 Version: A
 2 Basic Operations on the Alarm / Performance Event

Figure 2-5 Procedures of querying the performance history

5. Record the check result in the routine maintenance worksheet.

Reference standard

No abnormal performance events that frequently occur exist in the equipment.

Exception handling

If a performance parameter has become abnormal frequently on the system for a

period of time, users should keep a record of its occurrence and analyze the system
for possible silent failures, so as to eliminate the potential problems in a timely
manner and guarantee the normal operation of the system.

2.4 Filtering the Card Alarm / Performance Event

During the equipment commissioning and operation, some idle ports will generate
alarms and redundant performance events. Filtering these alarms and redundant
performance events can facilitate the maintenance on the equipment.

Note:

It is not recommended to filter the alarm and performance event of the in-
service ports.

Version: A 45
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Tool / Instrument

The OTNM2000

Prerequisite

u The OTNM2000 can manage, configure and monitor the entire network
normally; the OTNM2000 can ping each NE.

u The operator is knowledgeable of the busy / idle status of the ports and the
suppression relationship of alarms.

u The operator has the middle or above network management right.

Procedure

1. Double-click the on the desktop to access the OTNM2000 Login Info

dialog box. Then enter the user name and password (both are 1 by default) in it.
A successful login brings up the OTNM2000 window.

2. Click the NE that accommodates the desired card in the Logical Tree tab to
access the NE view.

3. Click the card in the subrack pane of the NE window, and then click
MASK_SETTING in the task panel on the right part of the main window to
access the filtering setting GUI, as shown in Figure 2-6.

46 Version: A
 2 Basic Operations on the Alarm / Performance Event

Figure 2-6 The filtering setting GUI

Table 2-4 lists descriptions for the configuration items in the filter setting GUI.

Table 2-4 Introductions for configuration items in the filtering setting

Item Description

Select a line first, and then select the alarm /

Mask by line
performance event to be filtered on this line.

Select an alarm / performance event first, and then

Mask by alarm /
select on which line this alarm / performance event
PM
should be filtered.
Filters all alarms / performance events on the selected
Line mask
line.
Mask mode
The OTNM2000 will no longer display any alarms on
Mask all alarm
this card after selecting this item.

The OTNM2000 will no longer display any performance

Mask all PM
events on this card after selecting this item.

The OTNM2000 will no longer display any alarms or

Mask all line performance events on this card after selecting this
item.
The OTNM2000 will cancel all alarm filtering after
Clear alarm mask
clicking this item.

Version: A 47
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Table 2-4 Introductions for configuration items in the filtering setting (Continued)

Item Description

The OTNM2000 will cancel the filtering of all

Clear performance mask
performance events after clicking this item.

The OTNM2000 will cancel all the line filtering after

Clear line mask
clicking this item.

The OTNM2000 will cancel all the filtering after clicking

Clear all mask
this item.
Save edited Saves the current configuration modification.

Cancels the current configuration modification, and

Cancel edited restore the configuration to the condition before the
modification.
Save to database Saves the current configuration to database.

Read from device Reads the current filtering configuration from the device.

Save to device Saves the current configuration to the equipment.

4. (Optional) Filtering alarms by the line:

1) Select Line-based filter in the drop-down list of the Filter Mode. Then
select the check box of a line under the Line Name item, e.g., for the 3
item; the codes, levels and types of the alarms and the codes of the
performance parameters that may occur on this line are listed in the right
part of the window, as shown in Figure 2-7.

48 Version: A
 2 Basic Operations on the Alarm / Performance Event

Figure 2-7 Filtering by the line

2) Select the codes of the alarm and the performance event that need to be
filtered under the Alarm code and Performance Abbreviation items
respectively, such as the MCCDISABLE item.

3) Click Save to the database and Save to the device in sequence to

complete the configuration.

5. (Optional) Filtering alarms by the alarm / performance:

1) Select Alarm- / PM-based Filter in the drop-down list of the Filter Mode.
Then select the check boxes of the alarm and the performance event that
need to be filtered under the Alarm code and Performance Abbreviation
items respectively, e.g.,MON1, as shown in Figure 2-8.

Version: A 49
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Figure 2-8 Filtering by the alarm / performance event

2) The right part of the window displays all line names that may generate the
selected alarm and performance event. Select the line under the Line
Name group box as needed.

3) Click Save to the database and Save to the device in sequence to

complete the configuration.

50 Version: A
3 Alarm Handling

The following introduces the information related to alarm handling, including

explanations, possible causes and processing procedures.

.MS_EXC.

.RS_SD.

1PPS_LOS

ALN_ERR

APS_MISMATCH

AU_AIS

AU_LOP

AU_NPJE_ALARM

AU_PPJE_ALARM

BACKUP_FAULT

BAK_5V_FAIL

BCS

BKIP_ERR

BMC_LOS

BMC_SW

BRIDGE

CARD_ABSENT

CARD_SWITCH

Version: A 51
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

CARD_TCT./CARD_TCT

CES_PK_LOS

CFG_MISMATCH./CFG_MISMATCH

COMFAIL

CONTEXT_FAIL

CONTEXT_PACKET_LOS

CRC_PACKET_LIMIT

CRC_ERR

CUR_LOCK

DCVOLDOWN

DCVOLOVER

DZB_IN

E1_AIS

E1_ES_LIMIT

E1_LOF

E1_LOS

E1_RDI

ETH_LCK

ETH_LOC

ETH_MMG

ETH_RDI

ETH_UNL

52 Version: A
 3 Alarm Handling

ETH_UNM

ETH_UNP

ETHLB_LOS

fDISABLE

fRDONLY

FAIL./FAIL

FANALAM

FORCE_AIS

FORCE_SWITCH

GFP_LOF

HOLDOVER

HP_AIS

HP_BBE_LIMIT

HP_ES_LIMIT

HP_EXC

HP_NPJE_ALARM

HP_PPJE_ALARM

HP_RDI

HP_SD./HP_SD

HP_SES_LIMIT

HP_SLM

HP_SLU.

HP_TIM

Version: A 53
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

HP_TIU.

HP_UNEQ/HP_UNEQ.

IOP_HIGH/IOPM_HIGH.

IOP_LOW/IOP_LOW.

LASER_CCT

LASER_OFF

LASER_TCT

LASER_TF

LINK_LOS

LOCK_MAIN

LOF_2M

LOOP

LOOP(T)

LOOPL

LOOPL(T)

LOOPL_L

LOOP_L

LP_AIS

LP_BBE_LIMIT

LP_ES_LIMIT

LP_EXC

LP_LOP

54 Version: A
 3 Alarm Handling

LP_RDI

LP_SD

LP_SES_LIMIT

LP_SLM

LP_TIM

LP_UNEQ

LSYN_LOC

LTI.

M_Asynchronous Active / Standby Alarms

M_SWITCH

MANUAL_SWITCH

MCCABORT

MCCCUTHROUGH

MCCDISABLE

MON1/2/3/4

MS_AIS

MS_BBE_LIMIT

MS_ES_LIMIT

MS_EXC

MS_RDI

MS_SD

MS_SES_LIMIT

OOCR

Version: A 55
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

OTRX_ABSENT

PK_LOS

PORT_MIRROR

POWERALM

PPI_LOS

PPS_ALM

PTP_ALM

PTP_CLK_ALM

PTP_LOS

PTP_TEST

RCONTEXT_ACCESS_FAIL

RCONTEXT_PACKET_LOS

REF_CHANGE

RLOS

RPJE_LIMIT

RS_BBE_LIMIT

RS_ES_LIMIT

RS_EXC./RS_EXC

RX_LOC

RS_LOF

RS_OOF

RS_SD

56 Version: A
 3 Alarm Handling

RS_SES_LIMIT

RS_SF

RS_TIM

RS_TIU./RS_TIU

RX_ERR

SCLK_LOS

SCK_LOS/SCK_LOS.

SPI_LOS

SPT_TF

SW_FAIL

SWITHCH_LOOP

SWR

SWTR

TRAF_ONLOAD

TEMP_ABNORMAL

TEMP_OVER

TEMP_TCT

TF

TOD_CRC_ERR

TOD_LOS

TU_AIS

TU_LOM

Version: A 57
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

TU_LOP

TX_ERR

VC_AIS

VC_CSF

VC_LCK

VC_LOC

VC_MMG

VC_RDI

VC_SD

VC_SF

VC_UNM

VC_UNP

VCLB_LOS

VP_AIS

VP_LCK

VP_LOC

VP_MMG

VP_RDI

VP_SD

VP_SF

VP_SSF

VP_UNM

58 Version: A
 3 Alarm Handling

VP_UNP

VPLB_LOS

VS_AIS

VS_LCK

VS_LOC

VS_MMG

VS_RDI

VS_SD

VS_SF

VS_UNM

VS_UNP

VSLB_LOS

Version: A 59
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.1 .MS_EXC.
Meaning

The bit error ratio threshold-crossing alarm of the multiplex section. The alarm
occurs when the bit error ratio detected by the B2 byte exceeds the threshold value.

Alarm level

Major alarm

Relevant card

S1J1, XSJ2, XSJ3

Influence on the system

The bit error of the alarmed multiplex section generating the .MS_EXC. alarm is
excessive and the service quality is degraded.

Possible cause

u The card temperature is over high and the TEMP_TCT alarm exists.

u Physical connection faults, such as broken pigtail fiber, too small bend radius of
the pigtail fiber, unclean optical interface, poor contact of the optical fiber
connector.

u The attenuation of the received signal is over-high.

u The attenuation value of the optical attenuator is over-high or over-low.

u The far end transmission equipment is faulty.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the .MS_EXC. alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the alarms like RS_EXC, HP_SD exist on the local end.

4 If yes, process alarms such as RS_EXC, HP_SD first. If the alarm persists,
➔ Step 3.

60 Version: A
 3 Alarm Handling

4 If not, ➔ Step 3.

3. Check whether the temperature of the alarmed card is over-high and whether
the TEMP_TCT alarm exists.

4 If yes, handle the TEMP_TCT alarm first and lower the ambient
temperature and the equipment working temperature. If the alarm persists,
➔ Step 4.

4 If not, ➔ Step 4.

4. Check whether the Rx optical power of the alarmed card is normal. If the Rx
optical power is normal, ➔ Step 5; if not, operate as below.

1) Secure the optical fiber connector to see whether the alarm is removed.

2) If the alarm persists, check whether the optical attenuator exists and
whether the attenuation value is within the normal range. If not, adjust the
attenuation value to see whether the alarm is removed.

3) If the alarm persists, clean the fiber connector and the receiving optical
interface at the local end to see whether the alarm is removed.

4) If the alarm persists, check whether the ring flange and the optical
attenuator at the local station is correctly connected. Connect the ring
flange and the optical attenuator correctly to see whether the alarm is
removed.

5. Check whether the Tx optical power is normal at the far end station. If the Tx
optical power is normal, clean the fiber connector at the remote station to see
whether the alarm is removed. If not, operate as below.

1) Replace the optical module or the card on the far end station to see
whether the alarm is removed.

2) If the alarm persists, check whether the ring flange and the optical
attenuator of the far end station are correctly connected, and whether the
attenuation value is over-high. Connect the ring flange and the optical
attenuator correctly to see whether the alarm is removed.

6. If the alarm persists, check whether the optical cable is faulty. If yes, handle the
fault to see whether the alarm is removed.

7. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

Version: A 61
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

8. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card.

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.2 .RS_SD.
Meaning

The regenerator section signal degradation alarm. This alarm occurs when the bit
error ratio of the tested equipment exceeds the threshold.

Alarm level

Minor alarm

Relevant card

S1J1, XSJ2, XSJ3

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
the local station will be degraded or the service will be interrupted.

Possible cause

u The input optical power is over-low or over-high.

u The card on the local end or the far end is faulty.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

Handling method

1. Check the .RS_SD. alarm on the OTNM2000 to identify the information such as
NE and card that generate the alarm.

2. Use the optical power meter to check whether the Rx optical power is normal.

4 If yes, ➔ Step 3.

62 Version: A
 3 Alarm Handling

4 If not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for handling

the alarm.

3. If the alarm persists, clean the optical interface.

4. If the alarm persists, check and eliminate the optical fiber fault.

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.3 1PPS_LOS
Meaning

1PPS_LOS is the pulse per second loss alarm.

Alarm level

Critical alarm

Relevant card

XCUJ2

Influence on the system

The time source is switched and the time synchronization is unstable.

Possible cause

u The connection of time source signal cables is faulty, which causes the
connection interruption.

u The time server is faulty.

u The TOD interface is damaged.

Handling procedure

1. Check whether the clock configuration on the local end and the adjacent
equipment is correct.

Version: A 63
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, ➔ Step 2.

4 If not, re-configure the clock configuration. If the alarm persists, ➔ Step 2.

2. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 3.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the alarm persists, ➔ Step 3.

3. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.4 ALN_ERR
Meaning

The alignment error threshold-crossing alarm. This alarm will be reported when the
number of ALIGNMENT error packets received by the Ethernet interface of the
system exceeds the alignment error threshold.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The line with the alignment error threshold-crossing alarm will be degraded.

Possible cause

u The alignment error threshold is set over-low.

64 Version: A
 3 Alarm Handling

u The interface line is interfered.

Handling method

1. Enter the OTNM2000.

2. Increase the alignment error threshold value of the alarmed card appropriately.

3. Check the physical connection status between the alarmed card and the
subrack.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.5 APS_MISMATCH
Meaning

The APS mismatch alarm. This alarm will be reported when the APS protection is
incorrectly configured or the APS transmission path is faulty.

Alarm level

Critical alarm

Relevant card

XCUJ2, XCUJ4

Influence on the system

The working path will be faulty and the protection will fail, which cause the service
interruption.

Possible cause

u The APS protection is incorrectly configured.

u The relevant line of the APS protection is faulty.

Version: A 65
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the APS_MISMATCH alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the protection configuration of the alarmed line is correct. See
CiTRANS 660 High-capacity MPLS-TP Platform Configuration Guide for
modifying it into the correct configuration and re-deliver it to the equipment.

3. Check whether the optical fibers, wires and cables connection between the
local end and the far end are correct. If the alarm persists, please contact
FiberHome after-sales maintenance engineer.

3.6 AU_AIS
Meaning

Alarm indication signal of the administrative unit. This alarm occurs when the S1J4
card receives the consecutive pointer values whose address values are all-ones.

Alarm level

Minor alarm

Relevant card

XGJ1, S1O1, S1J4, XSJ3

Influence on the system

u The services will be interrupted after the AU_AIS alarm is generated.

u The AU_AIS alarm will be inserted to the succeeding station after the it is
generated.

Possible cause

u The alarm exists in the previous station.

u The transmission at the far end is faulty.

u The receiving at the local end is faulty.

u The service configuration is faulty.

66 Version: A
 3 Alarm Handling

Handling method

1. Enter the OTNM2000 to check the AU_AIS alarm and confirm the NE that
generates the alarm.

2. Check whether the alarms like MS_EXC, MS_SD, RS_SD and RS_EXC exist
on the local end.

4 If yes, remove alarms first, such as MS_EXC, MS_SD, RS_SD, RS_EXC.

If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the service configuration on the local end and far end is correct.

4. Check whether the transmission at the far end is faulty.

4 If yes, eliminate the fault first. If the alarm persists, ➔ Step 5.

4 If not, ➔ Step 5.

5. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

6. If the alarm persists, replace the alarmed card with an identical spare one (see
CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance).

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.7 AU_LOP
Meaning

The administrative unit pointer loss alarm. This alarm occurs if the pointer value is
invalid for eight consecutive frames or eight consecutive new data flags (NDF) are
detected by the S1J2/S1J4 card.

Alarm level

Critical alarm

Relevant card

XGJ1, S1O1, S1J2, S1J4, XSJ3

Version: A 67
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

When the AU_LOP alarm is generated, the system transmits the HP_RDI
information back to the far end automatically.

Possible cause

u Errors exit in receiving of the local end.

u The transmission at the far end is faulty.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the AU_LOP alarm and confirm the NE that
generates the alarm.

2. Check whether the alarms like MS_EXC, MS_SD, RS_SD and RS_EXC exist
on the local end.

4 If yes, remove alarms first, such as MS_EXC, MS_SD, RS_SD, RS_EXC.

If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the transmission at the far end is faulty.

4 If yes, eliminate the fault first. If the alarm persists, ➔ Step 4.

4 If not, ➔ Step 4.

4. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

5. If the alarm persists, replace the alarmed card with an identical spare one (see
CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance for
operation procedures).

6. If the alarm still exists, please contact FiberHome after-sales maintenance

engineer.

68 Version: A
 3 Alarm Handling

3.8 AU_NPJE_ALARM
Meaning

The negative pointer adjustment threshold-crossing alarm of the administrative unit.

This alarm occurs if the total number of the AU negative pointer adjustment events
exceeds the preset AU_NPJE_ALARM threshold in 15 minutes.

Alarm level

Major alarm

Relevant card

S1O1, S1J4

Influence on the system

After the alarm is generated, the received line clock by this line will be asynchronous
with the system clock of this station and the code slip may occur in the line services,
which may cause the system performance degradation.

Possible cause

u The configuration of the synchronization reference source or the

synchronization reference source level is incorrect. As a result, two
synchronization reference sources or two NE clocks track each other, causing
the asynchronous clock.

u The local line card is faulty and the extracted clock is in poor quality, causing
the asynchronous clock.

u The clock and cross-connect card is faulty, causing that the provided
synchronization reference source is in poor quality or the tracked
synchronization reference source cannot be locked.

Handling method

1. Enter the OTNM2000 to check the AU_NPJE_ALARM alarm and confirm the
information such as the NE or line that generates the alarm.

Version: A 69
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check the clock reference source configuration to prevent the two clock
reference sources from existing in the entire network.

3. Check the clock tracking configuration to prevent clocks of two stations from
tracking each other.

4. Analyze the performance event of pointer adjustment and isolate the first
station (Station A) which is asynchronous with the clock reference source along
the tracking direction.

5. Replace the card that extracts the line clock in the station A. If the alarm
persists, ➔ Step 6.

6. Perform the switching between the active and standby clock and cross-connect
cards at Station A. Replace the clock and cross-connect card. If the alarm
persists, ➔ Step 7.

7. Please contact FiberHome after-sales maintenance engineer.

3.9 AU_PPJE_ALARM
Meaning

The positive pointer adjustment threshold-crossing alarm of the administrative unit.

The AU_PPJE_ALARM alarm will be generated if the total number of AU positive
pointer adjustment events exceeds the preset AU_NPJE_ALARM threshold in 15
minutes.

Alarm level

Major alarm

Relevant card

S1O1, S1J4

70 Version: A
 3 Alarm Handling

Influence on the system

The clock of the alarmed line is asynchronous with the system clock of the current
station, and the received line clock frequency is lower than the system clock
frequency. If the system clocks of two adjacent stations are asynchronous, the code
slip may occur in the line service, which causes the system performance
degradation.

Possible cause

u The incorrect configuration of the synchronization reference source or the

synchronization reference source level. As a result, two synchronization
reference sources or two NE clocks track each other, causing the
asynchronous clock.

u The local line card is faulty and the extracted clock is in poor quality, which
causes the asynchronous clock.

u The local clock and cross-connect card is faulty, causing that the provided
synchronization reference source is in poor quality or the tracked
synchronization reference source cannot be locked.

Handling method

1. Enter the OTNM2000 to check the AU_PPJE_ALARM alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check the clock reference source configuration to prevent that two clock
reference sources exist in the entire network.

3. Check the clock tracking configuration to prevent that clocks of two stations
track each other.

4. Analyze the performance event of the pointer adjustment and isolate the first
station (Station A) which is asynchronous with the clock reference source along
the tracking direction.

5. Replace the card that extracts the line clock in the station A. If the alarm
persists, ➔ Step 6.

6. Perform the switching between the active and standby clock and cross-connect
cards at Station A. Replace the clock and cross-connect card. If the alarm
persists, ➔ Step 7.

Version: A 71
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

7. Please contact FiberHome after-sales maintenance engineer.

3.10 BACKUP_FAULT
Meaning

The protection path fault alarm. If the CV frame is enabled, this alarm occurs when
the local end cannot detect the CV frame of the protection path.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

If the working path fails, the service cannot be switched to the protection path,
causing the service interruption.

Possible cause

u The BACKUP_FAULT alarm occurs as a subsequent alarm of alarms such as

LINK_LOS, RLOS, PPI_LOS, SPI_LOS, MS_SD, MS_AIS, RS_LOF, VP_LOC,
VS_LOC.

u The card is faulty.

Handling method

1. Enter the OTNM2000 to check the BACKUP_FAULT alarm and confirm the NE
and the line that generate the alarm.

2. Check whether alarms such as LINK_LOS, RLOS, PPI_LOS, SPI_LOS,

MS_SD, MS_AIS, RS_LOF, VP_LOC and VS_LOC exist in the NE.

4 If yes, remove the alarm according to the relevant alarm handling methods.
If the BACKUP_FAULT alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

72 Version: A
 3 Alarm Handling

3. If the alarm persists, replace the alarmed card with an identical spare one. Wait
a few minutes, if the alarm persists after the card is started up normally, ➔ Step
4.

4. Please contact FiberHome after-sales maintenance engineer.

3.11 BAK_5V_FAIL
Meaning

The standby 5V power alarm. The BAK_5V_FAIL alarm occurs when the NMUJ1
card detects that the voltage of the standby 5V power is lower than 3V.

Alarm level

Critical alarm

Relevant card

NMUJ1

Possible cause

The voltage of the external standby power supply is over-low.

Handling method

Check whether the voltage of the external standby power supply is over-low; if yes,
adjust the voltage to a higher value.

3.12 BCS
Meaning

The broadcast storm suppression alarm. The alarm occurs when the system
implements the rate control of the broadcast packets.

Alarm level

Prompt alarm

Version: A 73
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XGJ1, XSJ2, XSJ3

Possible cause

The port has set the broadcast storm suppression.

Handling method

1. Enter the OTNM2000 to check the BCS alarm and confirm the information such
as the NE or line that generates the alarm.

2. Confirm whether the function is necessary.

4 If yes, no handling is needed.

4 If not, disable the function in the card configuration of the alarmed card in
the OTNM2000 (see CiTRANS 660 High-capacity MPLS-TP Platform Card
Configuration Parameter Reference).

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.13 BKIP_ERR
Meaning

The standby IP address invalid alarm. Usually it is necessary to configure the active
and standby IP addresses for the intersecting node in the dual node ring. Normally,
the standby IP will not be used; if it is used and it turns out to be invalid, the
BKIP_ERR alarm will be generated.

Alarm level

Prompt alarm

Relevant card

NMUJ1

74 Version: A
 3 Alarm Handling

Influence on the system

The incorrect IP address may cause the equipment out of management or service
interruption.

Possible cause

The standby IP address is occupied or the standby IP address and the IP address
of the standby backbone node are not in the same network segment.

Handling method

Modify the IP address according to the network planning and re-deliver the
management configuration.

3.14 BMC_LOS
Meaning

Synchronization reference source loss alarm. This alarm occurs if the card fails to
detect the synchronization reference source signal.

Alarm level

Prompt alarm

Relevant card

GSJ2, XCUJ2, ESJ1, XSJ2

Influence on the system

This alarm indicates that the card fails to detect the valid reference clock transmitted
from the backplane, and the service of the card is unstable.

Possible cause

u The EMS configuration is incorrect.

u The time server does not transmit time source signals to the local end.

Version: A 75
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the BMC_LOS alarm and confirm the
information of the alarmed card.

2. Check and modify the faults of the time synchronization configuration of the
ESJ1 card in the OTNM2000 (see CiTRANS 660 High-capacity MPLS-TP
Platform Routine Maintenance for operation procedures).

3. If the alarm persists, check and ensure that the time service transmits time
source signals normally (see CiTRANS 660 High-capacity MPLS-TP Platform
Routine Maintenance for operation procedures).

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.15 BMC_SW
Meaning

Clock synchronization path switchover alarm. The alarm occurs when the time
synchronization path is switched.

Alarm level

Prompt alarm

Relevant card

GSJ2, XCUJ2, ESJ1, XSJ2

Influence on the system

This alarm indicates that the card fails to detect the valid reference clock transmitted
from the backplane, and the service of the card is unstable.

Possible cause

The time synchronization path is switched.

76 Version: A
 3 Alarm Handling

Handling method

No handling is needed. The alarm will disappear automatically after the switching is
completed.

3.16 BRIDGE
Meaning

The bridge connection alarm. The alarm occurs when the working path is faulty and
the service is bridged to the protection path.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the BRIDGE alarm is generated, the working path is faulty and the service is
bridged to the protection path.

Possible cause

u The BRIDGE alarm occurs as a subsequent alarm of alarms such as

LINK_LOS, RLOS, PPI_LOS, SPI_LOS, MS_SD, MS_AIS, RS_LOF, VP_LOC
and VS_LOC.

u The OTNM2000 delivers the forced switch or manual switch command to the
NE, triggering service switching to the protection path from the working path.

Handling method

1. Enter the OTNM2000 to check the BRIDGE alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether alarms such as LINK_LOS, RLOS, PPI_LOS, SPI_LOS,

MS_SD, MS_AIS, VP_LOC, VS_LOC and RS_LOF exist.

Version: A 77
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, remove the alarm according to the related alarm handling methods.
If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the active/standby switching command is delivered to the

alarmed XCUJ2/XCUJ4 card via the View Command Log command.

4 If not, deliver the restore to active / switching clearing command to the

alarmed XCUJ2/XCUJ4 card. If the alarm still exists, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.17 CARD_ABSENT
Meaning

The card not-present alarm. This alarm will be generated when a card is configured
in the OTNM2000 but the corresponding physical slot cannot detect the card signal.

Alarm level

Communication interruption

Relevant card

NMUJ1, XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, S1O1

Influence on the system

The communication between the alarmed card and the OTNM2000 is interrupted,
the other alarms and performance of this card cannot be reported and the
configuration cannot be delivered to this card via the OTNM2000.

Possible cause

u The card is resetting.

u The card is not in the slot.

u The card is not inserted in the slot reliably.

78 Version: A
 3 Alarm Handling

u The actual card configuration in the subrack is inconsistent with the

configuration in the OTNM2000.

u The alarmed card is faulty.

Handling method

1. Check the CARD_ABSENT alarm in the OTNM2000 and identify the alarmed
card and its slot.

2. Wait a few minutes to check whether the alarm disappears. If the alarm
disappears, the card is just reset; if not, ➔ Step 3.

3. Check whether the corresponding card is inserted in the corresponding slot;

4 If the card is present: Check whether the card is in good connection with
the slot. If not: Plug and unplug the alarmed card (see Plugging and
Unplugging Cards) and wait a few minutes. If the alarm still exists after the
card is started up normally, ➔ Step 4.

4 If the card is not present: Insert the identical spare card of the alarmed card.
Check whether the alarm disappears after the card is started up normally.
If the alarm persists, ➔ Step 4.

4. Check whether the card in the slot is consistent with the configuration in the
OTNM2000. If not, replace the card (see CiTRANS 660 High-capacity MPLS-
TP Platform Routine Maintenance for operation procedures). Wait a few
minutes after this operation; if the alarm persists after the card is started up,
proceed to ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

3.18 CARD_SWITCH
Meaning

The active / standby card switching alarm.

Alarm level

Prompt alarm

Version: A 79
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XCUJ2, XCUJ4

Possible cause

u The hardware or software of the active card is faulty.

u The switching command is delivered manually.

u The active card is unplugged manually.

u The active card is reset.

Handling method

No handling is needed. The alarm will disappear automatically after the switching is
completed.

3.19 CARD_TCT./CARD_TCT
Meaning

The card temperature over-high alarm. The alarm occurs when the card
temperature exceeds the temperature alarm threshold value set by the ONTM2000.

Alarm level

Prompt alarm

Relevant card

XCUJ2, XCUJ4, S1O1, S1J2, S1J4, XSJ2

Influence on the system

Faults, such as bit error and packet loss, occur when the card is in the temperature
threshold-crossing status.

80 Version: A
 3 Alarm Handling

Possible Cause

u The temperature in the equipment room is over-high.

u The temperature threshold value set in the OTNM2000 is not appropriate.

u Faults of the subrack fan

u Too much dust on the anti-dust screen of the subrack blocks the ventilation
hole.

u The alarmed card is faulty.

Handling method

1. Check the CARD_TCT./CARD_TCT alarm in the OTNM2000, and identify the

alarmed card and record the NE and slot to which it belongs.

2. Check whether the ambient temperature is within the normal range (-30℃ to
55℃).

4 If yes, ➔ Step 3.

4 If not, use the air conditioner to adjust the ambient temperature to a normal
range. If the alarm persists, ➔ Step 3.

3. Enter the card configuration GUI of the alarmed card in the OTNM2000 to
confirm whether the setting of the card over-temperature threshold value is
appropriate. The recommended value is 60℃ to 65℃.

4 If the setting is appropriate, ➔ Step 4.

4 If the setting is not appropriate, modify the threshold value setting. See
CiTRANS 660 High-capacity MPLS-TP Platform Card Configuration
Parameter Reference for card configuration.

4. Check whether the FANALM alarm (fan alarm) exists on the NE to which the
alarmed card belongs.

4 If yes, process this alarm. If the CARD_TCT alarm persists after removing
the FANALM alarm, ➔ Step 5.

4 If not, ➔ Step 5.

5. Check whether too much dust accumulates on the anti-dust screen of the
subrack to which the card belongs, or the subrack ventilation hole is blocked.

Version: A 81
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, clear the dust and unblock the ventilation hole. If the alarm persists,
➔ Step 6.

4 If the ventilation hole is normal, ➔ Step 6.

6. Replace the alarmed card with the identical spare card. If the alarm persists,
please contact FiberHome after-sales maintenance engineer.

3.20 CES_PK_LOS
Meaning

The packet loss threshold-crossing alarm. This alarm will be generated when the
frame loss exceeds the threshold set in the OTNM2000 continuously in a certain
period.

Alarm level

Major alarm

Relevant card

S1O1, S1J4, E1J1

Influence on the system

This alarm may cause service interruption.

Possible cause

u The line fault causes packet loss.

u The forwarding line card fault causes packet loss.

u The CES card fault causes packet loss.

u The CES clock recovery degradation causes packet loss.

Handling method

1. Check the link signal quality. Replace the optical fiber and the network cable,
and clean the optical module.

82 Version: A
 3 Alarm Handling

2. Check whether the temperature of the alarmed card is over-high and whether
the TEMP_TCT alarm exists. If yes, handle the TEMP_TCT alarm first and
lower the ambient temperature and equipment working temperature.

3. If the alarm still exists, check whether the DOS attack exists; if yes, clear the
illegal data source.

4. If the alarm still exists, check whether the loop occurs in the network; if yes,
modify the relevant configuration to eliminate the loop.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.21 CFG_MISMATCH./CFG_MISMATCH
Meaning

The configuration mismatch alarm. The alarm occurs when the card configuration
block of the OTNM2000 is incorrect.

Alarm level

Prompt alarm

Relevant card

GSJ2, GSJ3, XCUJ2, XSJ2, XSJ3, XGJ1, S1O1, XCUJ4, S1J4, ESJ1, ESJ2, ESJ2

Influence on the system

The incorrect configuration may cause a failure of the corresponding function of the
configuration block.

Possible cause

u The parameter configuration such as PTP_Config in the card configuration (the

ESJ1 card) is incorrect.

u The parameter configuration such as TDM_Config in the card configuration

(the S1J4 card) is incorrect .

u The parameter configuration such as Link_Config in the card configuration

(ESJ1, ESJ2) is incorrect.

Version: A 83
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the CFG_MISMATCH./CFG_MISMATCH alarm

and confirm the information such as the NE, card or line number that generates
the alarm.

2. Enter the configuration GUI of the alarmed card to check whether the
configuration information related to the alarmed line is correct.

4 If yes, ➔ Step 3.

4 If not, configure according to the actual condition. See CiTRANS 660 High-
capacity MPLS-TP Platform Card Configuration Parameter Reference for
service configuration and card parameter configuration. If the alarm
persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.22 COMFAIL
Meaning

Communication interruption alarm. The alarm occurs when the communication

between the card and the NMUJ1 card is interrupted.

Alarm level

Critical alarm

Relevant card

NMUJ1, XSJ2, XSJ3, XGJ1, GSJ2, GSJ3

Influence on the system

The alarm causes that the configuration of the EMS host is failed to be delivered to
the card, the card fails, services can not be configured and the protection switching
fails.

Possible cause

u The alarmed card is faulty.

84 Version: A
 3 Alarm Handling

u The card is reset.

Handling method

1. Check the alarmed card on the ONTM2000 to confirm that the alarm is reported
by a card or multiple cards.

4 If a card reports the alarm, ➔ Step 2.

4 If multiple cards report the alarm, ➔ Step 3.

2. Check whether the alarmed card is reset. If yes, wait a few minutes. If the alarm
persists, replace the alarmed card (referring to CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

3. If multiple cards report the alarm,

4 Check whether the alarmed NE and the other NEs connect via the switch
or the Hub. If yes, eliminate the VLAN loss of the network and check
whether the alarm is removed.

4 If the alarm persists, plug and unplug the alarmed card or replace the
alarmed card.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.23 CONTEXT_FAIL
Meaning

The link setting up failure alarm. The alarm occurs when the E1 link setting up fails
between the local and the far ends.

Alarm level

Critical alarm

Relevant card

E1J1, E1J2

Version: A 85
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

This alarm will cause the service interruption or protection switching function failure.

Possible cause

The alarmed card is faulty.

Handling procedure

Replace the alarmed card (see CiTRANS 660 High-capacity MPLS-TP Platform
Routine Maintenance).

3.24 CONTEXT_PACKET_LOS
Meaning

The local end link packet loss alarm. The alarm occurs when the link detects the
packet loss.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J2, E1J1, E1J2, S1J4

Influence on the system

The link that generates the CONTEXT_PACKET_LOS alarm has packet loss.

Possible cause

u The configuration data is incorrect.

u Line fault.

u The alarmed card is faulty.

86 Version: A
 3 Alarm Handling

Handling method

1. Enter the OTNM2000 to check the CONTEXT_PACKET_LOS alarm and

confirm the information such as the NE, card or line that generates the alarm.

2. Check whether the operation of the far end transmitting at the line-side is
normal.

4 If yes, ➔ Step 3.

4 If not, find the cause and eliminate the transmitting fault of the far end at
the line-side . If the alarm persists, ➔ Step 3.

3. Check whether the configurations of the local end and the far end are correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

4. Check whether the number of packets in the buffer is normal by the status
monitoring.

4 If yes, ➔ Step 5.

4 If not, modify the number of buffered packets in the card configuration. If

the alarm persists, ➔ Step 5.

5. Check whether the clock locking status of the local end is normal.

4 If yes, ➔ Step 6.

4 If not, find the cause and eliminate the clock locking fault first. If the alarm
persists, ➔ Step 6.

6. Unplug and re-insert the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 87
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.25 CRC_PACKET_LIMIT
Meaning

CRC threshold alarm. The alarm occurs when the emulation link detects the
threshold-crossing.

Alarm level

Critical alarm

Relevant card

S1O1

Influence on the system

This alarm will influence the service quality and cause the service unstable.

Possible cause

u The configuration data is incorrect.

u Line fault.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the CRC_PACKET_LIMIT alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the transmitting of the far end at the line-side is normal.

4 If yes, ➔ Step 3.

4 If not, find the cause and eliminate the transmitting fault of the far end at
the line-side . If the alarm persists, ➔ Step 3.

3. Check whether the configurations of the local end and the far end are correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

88 Version: A
 3 Alarm Handling

4. Check whether the number of packets in the buffer is normal by the status
monitoring.

4 If yes, ➔ Step 5.

4 If not, modify the number of buffered packets in the card configuration. If

the alarm persists, ➔ Step 5.

5. Check whether the locking status of the local end clock is normal.

4 If yes, ➔ Step 6.

4 If not, find the cause and eliminate the clock locking fault first. If the alarm
persists, ➔ Step 6.

6. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.26 CRC_ERR
Meaning

The CRC error alarm. This alarm occurs when the received CRC errors exceed the
CRC threshold set in the card configuration.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XSJ2, XSJ3, ESJ1, S1J2, S1J4, E1J1, E1J2

Influence on the system

The CRC_ERR alarm indicates the transmission of the service data fails.

Version: A 89
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The CRC threshold is incorrectly configured in the card configuration GUI.

u The optical fiber or cable is not securely connected.

u The clock and cross-connect card is reset.

Handling method

1. Access the card configuration GUI of the alarmed card and check the CRC
error threshold.

4 If the setting is inappropriately, modify and re-deliver the equipment

configuration and check whether the alarm is removed.

4 If the setting is appropriate, ➔ Step 2.

2. If the alarm persists, check whether the optical fiber or cable of the alarmed
card is securely connected, and eliminate the fiber connection fault.

3. If the alarm persists, check whether the clock and cross-connect card is reset in
the OTNM2000.

4 If the card is reset, wait 5 to 10 minutes to check whether the alarm is

removed.

4 If the card is not reset, ➔ Step 4.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.27 CUR_LOCK
Meaning

The current status locking alarm. The CUR_LOCK alarm occurs when the control
command of Lock_Status is delivered to the NMUJ1 card in the OTNM2000.

Alarm level

Prompt alarm

90 Version: A
 3 Alarm Handling

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the CUR_LOCK alarm is generated, the active / standby status of the NMUJ1
card is locked. The active / standby switching can be performed only when the
NMUJ1 card is unlocked.

Possible cause

The Lock_Status command is delivered to the card.

Handling method

1. Enter the OTNM2000 to check the CUR_LOCK alarm and confirm the
information such as the NE or line that generates the alarm.

2. Enter the control command GUI of the NMUJ1 card and execute the
Unlock_Status command to the NMUJ1 card.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.28 DCVOLDOWN
Meaning

The DC voltage is over-low. The DCVOLDOWN alarm occurs when the DC voltage
received by the NMUJ1 card is lower than the over-low threshold value set by the
OTNM2000.

Alarm level

Critical alarm

Relevant card

NMUJ1

Version: A 91
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The over-low voltage may cause the abnormal operation of the equipment.

Possible cause

u The over-low voltage threshold is set over-high.

u The DC voltage of the external power supply is over-low.

Handling method

1. Check whether the setting of the over-low voltage threshold is correct via the
OTNM2000. If not, modify the threshold value.

2. Check whether the voltage of the external power supply is over-low; if yes,
adjust the voltage to a higher value.

3.29 DCVOLOVER
Meaning

The DC voltage is over-high. When the NMUJ1 card detects that the received DC
voltage is higher than the over-high voltage threshold, the DCVOLOVER alarm
occurs.

Alarm level

Critical alarm

Relevant card

NMUJ1

Influence on the system

The over-high voltage may damage the equipment.

Possible cause

u The over-high voltage threshold is set over-low.

u The DC voltage of the external power supply is over-high.

92 Version: A
 3 Alarm Handling

Handling method

1. Check whether the setting of the over-high voltage threshold is correct via the
OTNM2000. If not, modify the threshold value.

2. Check whether the voltage of the external power supply is over-high; if yes,
adjust the voltage to a lower value.

3.30 DZB_IN
Meaning

Terminal board not present alarm. This alarm occurs when a card is configured in
the OTNM2000 but the corresponding physical slot cannot detect the card signal.

Alarm level

Communication interruption

Relevant card

E1J1

Influence on the system

The communication between the alarmed terminal board and the OTNM2000 is
interrupted, the other alarms and performance events of this card cannot be
reported and the configuration cannot be delivered to this card via the OTNM2000.

Possible cause

u The terminal board is not in the slot.

u The terminal board is resetting.

u The terminal board is not inserted in the backplane slot reliably.

u The actual terminal board configuration in the subrack is inconsistent with the
configuration in the OTNM2000.

u The terminal board fails.

Version: A 93
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Check the DZB_INT alarm on the OTNM2000 and identify the alarmed terminal
board and its slot.

2. Wait a few minutes to check whether the alarm disappears. If the alarm
disappears, the terminal board is just reset; if not, ➔ Step 3.

3. Check whether the corresponding terminal board is inserted in the

corresponding slot;

4 If the terminal board is present: Check whether the terminal board is in

good connection with the backplane slot. If not: Plug and unplug the
alarmed terminal board (see Plugging and Unplugging Cards) and wait a
few minutes. If the alarm persists after the card is started up normally, ➔
Step 4.

4 If the terminal board is not present: Insert the identical spare card of the
alarmed terminal board. Check whether the alarm disappears after the
terminal board is started up normally. If the alarm persists, ➔ Step 4.

4. Check whether the terminal board in the slot is consistent with the configuration
in the OTNM2000. If not, replace the terminal board (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).
Wait a few minutes after this operation; if the alarm persists after starting up the
terminal board, ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

3.31 E1_AIS
Meaning

E1 alarm indication signal. This alarm occurs when the card detects that the E1
signals are all-ones signals.

Alarm level

Minor alarm

Relevant card

S1O1, S1J1, S1J4, E1J1, E1J2

94 Version: A
 3 Alarm Handling

Influence on the system

This alarm may cause the service interruption.

Possible cause

u The corresponding E1 interface loops back.

u The meter and the user equipment connected to the corresponding port
transmit all-ones signals.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the E1_AIS alarm and confirm the information
such as the NE or line number that generates the alarm.

2. Check and clear the E1 interface loopback configuration.

3. If the alarm persists, check whether the meter and user equipment of the
corresponding port transmit the all-ones signals, and eliminate the transmitting
fault of the signal source.

4. If the alarm persists, reset or plug and unplug the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance) to see whether
the alarm is removed.

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to see whether the alarm is
removed.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.32 E1_ES_LIMIT
Meaning

The errored second threshold-crossing alarm. This alarm occurs if the detected
error number of the E1 interface in the unit time (1s) exceeds the threshold.

Version: A 95
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Prompt alarm

Relevant card

E1J2, E1J2

Influence on the system

u This alarm indicates the quality degradation of the transmission service.

u The system will insert the E1_AIS alarm to the cross-connect direction by
default after this alarm is generated.

Possible cause

u The signal source transmission is faulty.

u The interface line is faulty.

u The alarmed card is faulty.

Handling method

1. Clear the relevant performance (E1_HDB3_ERR and E1_ES) and check

whether the alarm is removed.

2. If the alarm persists, test whether the E1 signal transmitted by the far end is
normal with the error detector; if yes, eliminate the signal source transmission
fault.

3. If the alarm persists, check and ensure the E1 interface is well-connected.

4. If the alarm persists, reset or plug and unplug the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance) to see whether
the alarm is removed.

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to see whether the alarm is
removed.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

96 Version: A
 3 Alarm Handling

3.33 E1_LOF
Meaning

The E1 out-of-frame alarm. This alarm occurs if the card fails to isolate the E1 signal.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

This alarm may cause the service interruption.

Possible cause

u The line signal attenuation is over-high.

u The meter and the user equipment connected to the corresponding port
transmit all-ones signals.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the E1_LOF alarm and confirm the information
such as the NE or line number that generates the alarm.

2. Check and clear the loopback setting of the corresponding E1 interface.

3. Check whether the connected equipment and line is normal by the loopback
command to eliminate the line fault first.

4. If the alarm persists, check whether the configuration of E1 signal at the Tx side
is consistent with that at the Rx side, so as to eliminate the service
configuration fault.

5. If the alarm persists, reset or plug and unplug the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance) to see whether
the alarm is removed.

Version: A 97
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to see whether the alarm is
removed.

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.34 E1_LOS
Meaning

E1 input signal loss alarm. This alarm occurs when the card fails to detect the E1
signals input.

Alarm level

Critical alarm

Relevant card

S1J4, S1O1

Influence on the system

This alarm may cause the E1 service interruption.

Possible cause

u The E1 interface connection is in poor contact or the cable is faulty.

u The card service is inappropriately configured.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the E1_LOS alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the cable connected to the E1 interface is loose; if yes,

eliminate the poor contact.

3. Check and clear the loopback configuration of the corresponding E1 interface.

98 Version: A
 3 Alarm Handling

4. Check whether the connected equipment and line are normal by the loopback
command to eliminate the line fault first.

5. If the alarm persists, check whether the configuration of the E1 signal at the Tx
side is consistent with that of the Rx side, so as to eliminate the service
configuration fault.

6. If the alarm persists, reset or plug and unplug the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance) to see whether
the alarm is removed.

7. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to see whether the alarm is
removed.

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.35 E1_RDI
Meaning

E1 remote defect indication alarm. This alarm will be reported when the alarm exists
on the E1 far end and is transmitted to the local end by the overhead byte.

Alarm level

Minor alarm

Relevant card

S1O1, S1J1, S1J4, E1J1

Influence on the system

This alarm may cause the service interruption on the far end.

Possible cause

u The line at the single side is faulty.

u The alarmed card is faulty.

Version: A 99
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the E1_RDI alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the connected equipment and line are normal by the loopback
command to eliminate the line fault first.

3. If the alarm persists, reset or plug and unplug the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance) to see whether
the alarm is removed.

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to see whether the alarm is
removed.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.36 ETH_LCK
Meaning

The Ethernet locking alarm. The alarm occurs when the system receives the
ETH_LCK frame (Ethernet locking signal) from the adjacent MEP.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

The alarmed line service will be interrupted and the line will be occupied by the far
end for testing.

Possible cause

The system receives the ETH_LCK frame transmitted by the adjacent MEP.

100 Version: A
 3 Alarm Handling

Handling method

The ETH-LCK frame is the MEP announcement of its planned management or the
diagnostic action to its adjacent client layer MEP. No handling is needed for this
alarm.

3.37 ETH_LOC
Meaning

The Ethernet connection verification signal loss alarm. This alarm occurs when the
CCM frame from the far end is not received in 3.5 times the CCM transmission
period if the CCM frame is enabled at the local end.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

When the ETH_LOC alarm is generated, the OAM function cannot be performed
normally, and the services on the channel may be interrupted.

Possible cause

u This alarm occurs as a subsequent alarm of alarms such as ETH_MMG,

ETH_RDI, ETH_UNM, ETH_UNP, EHTLB_LOS.

u The far end CCM transmission is disabled.

u The network is terribly congested.

Handling method

1. Enter the OTNM2000 to check the ETH_LOC alarm and confirm the
information such as the NE, card or line that generates the alarm.

Version: A 101
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check whether the alarms such as ETH_MMG, ETH_RDI, ETH_UNM,

ETH_UNP and EHTLB_LOS exist in the alarmed card.

4 If the alarm exists, remove alarms, such as ETH_MMG, ETH_RDI,

ETH_UNM, ETH_UNP, EHTLB_LOS. See related contents in this manual
for troubleshooting. If the ETH_LOC alarm persists after the above
operation, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the CCM frame transmission at the far end of the alarmed line
is enabled.

4 If yes, ➔ Step 4.

4 If not, enable it. If the alarm persists, ➔ Step 4.

4. If the alarm persists, check the bandwidth occupation condition. If the

bandwidth is fully occupied, expand it or clear the illegal data source to see if
the alarm is removed.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.38 ETH_MMG
Meaning

The Ethernet unexpected maintenance entity group alarm. This alarm occurs when
the Ethernet OAM fails to receive the matched MEG value.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

When the ETH_MMG alarm occurs, the OAM function of the alarmed line cannot be
performed normally.

102 Version: A
 3 Alarm Handling

Possible cause

The setting of the MEG configuration of the local end and far end Ethernet OAMs
mismatches.

Handling method

1. Enter the OTNM2000 to check the ETH_MMG alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the MEG configuration of the far end is consistent with that of
the local end of the alarmed line. Check the MEG configuration in the
CFMOAM tab, see CiTRANS 660 High-capacity MPLS-TP Platform Card
Configuration Parameter Reference.

4 If yes, ➔ Step 3.

4 If not, modify the MEG-ICC or MEG-UMC information of the local end or far
end according to the actual situation to make the MEG information of the
two ends consistent. If the ETH_MMG alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.39 ETH_RDI
Meaning

The Ethernet remote failure indication alarm. This alarm occurs when the local end
receives the massages with the ETH-RDI information.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

The ETH-RDI information is transmitted by the faulty MEP. Receiving the ETH-RDI
information indicates the receiving of the opposite end equipment is faulty.

Version: A 103
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The service tag value transmitted by the local end does not match the far end
configuration.

u The Rx end of the opposite end equipment is faulty. The OAM message with
RDI information to the local end equipment is transmitted.

u The test instrument transmits the CV message with RDI indication to the local
end equipment.

Handling method

1. Enter the OTNM2000 to check the ETH_RDI alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the service tag value transmitted by the local end which
generates the alarmed line matches the service tag value received by the far
end.

4 If yes, ➔ Step 3.

4 If not, modify the tag value according to the actual service planning. After
this operation, if the ETH_RDI alarm persists, ➔ Step 3.

3. Check whether the alarm exists at the Rx end of the opposite end equipment.

4 If yes, eliminate the opposite end fault. After this operation, if the ETH_RDI
alarm still exists, ➔ Step 4.

4 If not, ➔ Step 4.

4. Check whether the message sent by the test instrument contains the RDI
information. If the RDI information is necessary, no handling is needed; if not,
modify the setting.

5. If the alarm still exists, please contact FiberHome after-sales maintenance

engineer.

104 Version: A
 3 Alarm Handling

3.40 ETH_UNL
Meaning

The Ethernet unexpected maintenance entity group level alarm. The alarm occurs
when the Ethernet OAM of the local end receives the MEP value that does not
match the EMS configuration.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

When the ETH_UNL alarm occurs, the OAM function of the alarmed line cannot be
performed normally.

Possible cause

The MEP configuration of the local Ethernet OAM is inconsistent with that of the far
end.

Handling method

1. Enter the OTNM2000 to check the ETH_UNL alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the MEP configuration of the far end is consistent with that of
the local end of the alarmed line. Check the MEP configuration in the CFMOAM
tab, and see CiTRANS 660 High-capacity MPLS-TP Platform Card
Configuration Parameter Reference for configuration description.

4 If yes, ➔ Step 3.

4 If not, modify the MEP-ID information of the far end to be consistent with
that of the local end. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

Version: A 105
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.41 ETH_UNM
Meaning

The Ethernet unexpected maintenance entity group end point alarm. The alarm
occurs when the Ethernet OAM of the local end receives the MEP value that does
not match the EMS configuration.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

When the ETH_UNM alarm occurs, the OAM function of the alarmed line cannot be
performed normally.

Possible cause

The MEP configuration of the local Ethernet OAM is inconsistent with that of the far
end.

Handling method

1. Enter the OTNM2000 to check the ETH_UNM alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the MEP configuration of the local end is consistent with that of
the far end. Check the MEP configuration in the CFMOAM tab, and see
CiTRANS 660 High-capacity MPLS-TP Platform Card Configuration Parameter
Reference for configuration description.

4 If yes, ➔ Step 3.

4 If not, modify the peer MEP-ID information and keep consistent with that of
the far end. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

106 Version: A
 3 Alarm Handling

3.42 ETH_UNP
Meaning

The Ethernet time interval mismatch alarm. The alarm occur when the time interval
of the local end Ethernet OAM receiving the far end CCM frame does not match the
expected value.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

When the ETH_UNP alarm occurs, the OAM function of the alarmed line cannot be
performed normally.

Possible cause

The transmission frequency of CCM frames of the local end is not consistent with
that of the far end.

Handling method

1. Enter the OTNM2000 to check the ETH_UNP alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the transmission period of the local CCM frame of the alarmed
line is consistent with that of the far end. Check the transmission period
configuration of the CCM frame in CFMOAM tab in the NE configuration GUI,
and see CiTRANS 660 High-capacity MPLS-TP Platform Configuration Guide
for configuration description.

4 If yes, ➔ Step 3.

Version: A 107
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, modify the transmission period configuration of the CCM frame to

make sure that the configuration of the local end is consistent with that of
the far end. The recommended value is 3.33ms. If the alarm persists, ➔
Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.43 ETHLB_LOS
Meaning

Ethernet loopback signal timeout alarm. The alarm occurs when the receiving of the
loopback frame at the local end is timed out.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ2, XSJ2, XSJ3

Influence on the system

The service may be interrupted in the alarmed line when the alarm is generated.

Possible cause

u The time interval of transmitting loopback frames at the local end is longer than
the time-out duration of the loopback frames.

u The setting of the time-out duration of loopback frames at the local end is
incorrect.

u The far end is not configured correspondingly, and does not respond to the
loopback frame.

u Physical connection failure, such as optical fiber break.

Handling method

1. Enter the OTNM2000 to check the ETHLB_LOS alarm and confirm the
information such as the NE or line that generates the alarm.

108 Version: A
 3 Alarm Handling

2. Check whether the setting of the cycle of transmitting CCM frames for the
alarmed line is correct and whether the Tx cycle is longer than the time-out
duration of the Ethernet loopback signal.

4 If the setting is appropriate, ➔ Step 3.

4 If not, modify the Tx period configuration of the CCM frame to make sure
that the configuration of the local end is consistent with that of the far end.
The recommended value is 3.33ms. If the alarm persists, ➔ Step 3.

3. Check whether the setting of the time-out duration for the local end Ethernet
loopback signal is appropriate. The recommended value is 100ms.

4 If the setting is appropriate, ➔ Step 4.

4 If the setting is not appropriate, modify the time-out duration for the local
end Ethernet loopback signals. If the alarm persists, ➔ Step 4.

4. Check whether the loopback frame response is enabled at the far end of the
alarmed line.

4 If yes, ➔ Step 5.

4 If not, enable the loopback frame response (equipment offered by other

manufactory), or set up the Ethernet fault management entry (equipment
offered by FiberHome) corresponding to the local Ethernet OAM entry. If
the alarm persists, ➔ Step 5.

Note:
The loopback frame response is enabled by default for the FiberHome
equipment. If the FiberHome equipment at the far end does not respond,
the reason may be that the Ethernet fault management entry
corresponding to the local end Ethernet OAM entry is not set up.

5. Check whether the physical connection of the alarmed line is normal without
physical faults such as fiber cut.

4 If yes, ➔ Step 6.

4 If not, eliminate the physical fault. If the ETHLB_LOS alarm persists after
executing the above operation, ➔ Step 6.

6. Please contact FiberHome after-sales maintenance engineer.

Version: A 109
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.44 fDISABLE
Meaning

The fDISABLE alarm indicates an execution of f disable command in the

OTNM2000.

Alarm level

Prompt alarm

Relevant card

NMUJ1

Influence on the system

When this alarm occurs, the normal communication between the LCT and the
equipment is affected. After the command is executed successfully, the LCT can
neither read nor configure the NE configuration data.

Possible cause

The f disable command is performed.

Handling method

1. Check the alarm through the OTNM2000 to identify the card that generates the
alarm.

2. Check whether the f disable command is normally required.

4 If yes, no handling is needed.

4 If not, execute the f disable command (right-click the card and select
Status Monitor in the shortcut menu).

110 Version: A
 3 Alarm Handling

3.45 fRDONLY
Meaning

The f interface read only indicates an execution of f read only command in the
OTNM2000.

Alarm level

Prompt alarm

Relevant card

NMUJ1

Influence on the system

The LCT can only read the NE configuration, but cannot configure the NE data.

Possible cause

The f read only command is performed.

Handling method

1. Check the alarm through the OTNM2000 to identify the card that generates the
alarm.

2. Check whether the f read only command is normally required.

4 If yes, no handling is needed.

4 If not, execute the f enable command (right-click the card and select
Status Monitor in the shortcut menu).

3.46 FAIL./FAIL
Meaning

The card failure alarm. The alarm occurs when the card hardware fault is detected.

Version: A 111
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Critical alarm

Relevant card

u FAIL. : XCUJ2, XCUJ4

u FAIL: S1O1, S1J4

Influence on the system

The alarmed card cannot operate normally and the current service of the card may
be interrupted.

Possible cause

u The CARD_ABSENT alarm exists.

u Poor contact between the card and the backplane.

u The alarmed card is faulty.

Handling method

1. Check the FAIL./FAIL alarm in the OTNM2000 and identify the alarmed NE /
card and its slot.

2. Check whether the CARD_ABSENT alarm exists on the alarmed card.

4 If yes, remove the CARD_ABSENT alarm and see CARD_ABSENT for

troubleshooting. If the FAIL./FAIL alarm persists after removing the
CARD_ABSENT alarm, ➔ Step 3.

4 If not, ➔ Step 3.

3. Unplug and insert the alarmed card and wait a few minutes. If the alarm
persists after restarting up the card, ➔ Step 4.

4. Replace the alarmed card with an identical spare one. Wait a few minutes, if the
alarm persists after the card is started up normally, ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

112 Version: A
 3 Alarm Handling

3.47 FANALAM
Meaning

The fan alarm. The alarm occurs when the fan fails.

Alarm level

Critical alarm

Relevant card

NMUJ1

Influence on the system

The fan fault may cause the high temperature in the equipment and alarms, such as
TEMP_OVER. The NE will be damaged due to the high temperature, which causes
the service interruption of the equipment.

Possible cause

u The fan is not secured.

u The fan fails.

Handling procedure

Plug and unplug the fan unit; replace the faulty fan unit (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

3.48 FORCE_AIS
Meaning

The forced transmission of the AIS alarm. The alarm occurs when the forced
transmission command is delivered via the OTNM2000. The alarm disappears when
the forced transmission command is removed.

Alarm level

Prompt alarm

Version: A 113
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

S1J1

Influence on the system

None.

Possible cause

The forced transmission AIS command is delivered in the OTNM2000.

Handling method

1. Enter the OTNM2000 to check the FORCE_AIS alarm and confirm the
information such as the NE or line that generates the alarm.

2. Enter the control command GUI of the alarmed card to check whether the
forced transmission AIS command is necessary. If not, remove the forced
command.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.49 FORCE_SWITCH
Meaning

The forced switch alarm. The alarm occurs when the forced switch command is
delivered in the OTNM2000. The alarm disappears when the forced switch
command is removed.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

114 Version: A
 3 Alarm Handling

Influence on the system

The FORCE_SWITCH alarm indicates the equipment executes the forced switch
command for the maintenance staff. The forced switch command is mainly used for
testing, and should be cleared after the test.

Possible cause

The forced transmission command is delivered in the OTNM2000.

Handling method

1. Enter the OTNM2000 to check the FORCE_SWITCH alarm and confirm the
information such as the NE or line that generates the alarm.

2. Enter the control command GUI of the alarmed card to check whether the
forced switch command is necessary. If not, remove the forced switch
command.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.50 GFP_LOF
Meaning

The GFP frame loss alarm. The system fails to detect valid GFP frames.

Alarm level

Minor alarm

Influence on the system

When the alarm occurs, the services may be interrupted in the Rx direction of the
local station.

Possible cause

u The service configuration is faulty.

u The alarmed card is faulty.

Version: A 115
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the GFP_LOF alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check the service configuration of the alarmed NE and the opposite service
and ensure that the service configuration is correct.

3. Replace the alarmed card (see CiTRANS 660 High-capacity MPLS-TP

Platform Routine Maintenance).

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.51 HOLDOVER
Meaning

Clock entering holdover status alarm. The alarm occurs when the clock enters the
holdover status.

Alarm level

Major alarm

Relevant card

S1J1

Influence on the system

This alarm will influence the service performance and cause the service unstable.

Possible cause

None.

Handling procedures

None.

116 Version: A
 3 Alarm Handling

3.52 HP_AIS
Meaning

Higher order path alarm indication alarm. The HP_AIS alarm occurs when the byte
C2 in five consecutive frames is detected all 111s.

Alarm level

Minor alarm

Relevant card

S1J1, S1J2, XSJ2

Influence on the system

When the alarm occurs, the service of the alarmed line in the Rx direction of the
local station is interruptted.

Possible cause

u The signal transmission of the previous station fails and the AIS signal is
transmitted to the local station.

u The service configuration is faulty.

u The opposite end equipment fails, for example, the signal between the clock
and cross-connect card and the optical card is interrupted, the optical card at
the opposite end fails.

u The card at the local end fails.

Handling method

1. Enter the OTNM2000 to check the HP_AIS alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the signal transmission failure exists in each previous station
according to the service flow of the higher order path.

3. Loopback the Tx and Rx of optical signals at the opposite end and check
whether the AU_AIS or HP_AIS alarm exists in the optical Rx direction after
loopback.

Version: A 117
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If no AU_AIS or HP_AIS alarm exists, ➔ Step 4.

4 If the AU_AIS or HP_AIS alarm exists, eliminate the fault on the opposite
end. If the alarm persists, ➔ Step 4.

4. Check whether the service configuration of the local station is correct.

5. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.53 HP_BBE_LIMIT
Meaning

The background block error threshold-crossing alarm of the higher order path. This
alarm occurs when the total number of B3 errored blocks in 15 minutes exceeds the
HP_BBE_LIMI threshold.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Influence on the system

The performance of the alarmed line in the Rx direction of the local station degrades
when the alarm occurs.

118 Version: A
 3 Alarm Handling

Possible cause

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The B1 error of the regenerator section and the B2 error of the multiplex section
cause the B3 error of the higher order path.

u The card on the local end or the far end is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_BBE_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Eliminate the external fault such as the abnormal temperature in the equipment
room, poor grounding or the interference source.

3. Check whether the RS_BBE_LIMIT and MS_BBE_LIMIT alarms related to the

B1 and B2 errors exist in the alarmed optical interface.

4 If yes, see MS_BBE_LIMIT and RS_BBE_LIMIT for troubleshooting If the

HP_BBE_LIMIT alarm persists after clearing the RS_BBE_LIMIT and
MS_BBE_LIMIT alarms, ➔ Step 4.

4 If not, ➔ Step 4.

4. Perform the loopback on the optical interface at the far end line side (users can
use the optical attenuator during the optical fiber loopback to ensure the Rx
optical power is within the normal range) and check whether the newly added
B3 error exists in the current performance on the opposite end.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 If yes: the previous station is faulty. Isolate the previous station and the
specified faulty point that generates the alarm according to the service
direction using loopback, and eliminate the fault by re-plugging and
unplugging or replacing the service card and the clock and cross-connect
card on the far end. If the alarm persists, ➔ Step 5.

5. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

Version: A 119
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. Please contact FiberHome after-sales maintenance engineer.

3.54 HP_ES_LIMIT
Meaning

The errored second threshold-crossing alarm of the higher order path. This alarm
will be generated when the total number of B3 errored seconds in 15 minutes
exceeds the HP_ES_LIMIT threshold.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station degrades.

Possible cause

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The B1 error of the regenerator section and the B2 error of the multiplex section
cause the B3 error of the higher order path.

120 Version: A
 3 Alarm Handling

u The card on the local end or the far end is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_ES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Eliminate the external fault such as the abnormal temperature in the equipment
room, poor grounding or the interference source.

3. Check whether the RS_ES_LIMIT and MS_ES_LIMIT alarms related to the B1

and B2 error exist in the alarmed optical interface.

4 If yes, see MS_ES_LIMIT and RS_ES_LIMIT for troubleshooting. If the

HP_ES_LIMIT alarm persists after removing the RS_ES_LIMIT and
MS_ES_LIMIT alarms, ➔ Step 4.

4 If not, ➔ Step 4.

4. Perform the loopback on the optical interface on the far end line side (users can
use the optical attenuator during the optical fiber loopback to ensure the Rx
optical power is within the normal range) and check whether the newly added
B3 error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 If yes: the previous station may be faulty. Isolate the previous station and
the specified faulty point that triggers the alarm according to the service
direction using loopback, and eliminate the fault by plugging and
unplugging or replacing the optical card and the clock and cross-connect
card. If the alarm persists, ➔ Step 5.

5. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. Please contact FiberHome after-sales maintenance engineer.

Version: A 121
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.55 HP_EXC
Meaning

The bit error ratio threshold-crossing alarm of the higher order path. The alarm
occurs when the higher order path bit error ratio exceeds the threshold value set in
the OTNM2000.

Alarm level

Major alarm

Relevant card

XGJ1, S1O1, S1J1, XSJ2, XSJ3, S1J4

Influence on the system

This alarm will influence the service quality and cause the service unstable.

Possible cause

u The alarms such as MS_EXC, MS_SD, RS_EXC, RS_SD exist.

u The card temperature is over high and the TEMP_TCT alarm exists.

u Physical connection faults, such as broken pigtail fiber, too small bend radius of
the pigtail fiber, unclean optical interface, poor connection of the optical fiber
connector.

u The attenuation of the received signal is over-high.

u The attenuation value of the attenuator is over-high or over-low.

u The far end transmission equipment is faulty.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_EXC alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the alarms like MS_EXC, MS_SD, RS_EXC, RS_SD exist on
the local end.

122 Version: A
 3 Alarm Handling

4 If yes, process alarms such as MS_EXC, MS_SD, RS_EXC, RS_SD first.

If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the temperature of the alarmed card is over-high and whether
the TEMP_TCT alarm exists.

4 If yes, handle the TEMP_TCT alarm first and lower the ambient
temperature and equipment working temperature. If the alarm persists, ➔
Step 4.

4 If not, ➔ Step 4.

4. Check whether the Rx optical power of the alarmed card is normal. If the Rx
optical power is normal, ➔ Step 5; if not, operate as below.

1) Secure the optical fiber connector to see whether the alarm is removed.

2) If the alarm persists, check whether the optical attenuator exists and
whether the attenuation value is appropriate. If not, adjust the attenuation
value to see whether the alarm is removed.

3) If the alarm persists, clean the pigtail fiber connector and the Rx optical
interface at the local end to see whether the alarm is removed.

4) If the alarm persists, check whether the ring flange and the optical
attenuator at the local station is correctly connected. Connect the ring
flange and the optical attenuator correctly to see whether the alarm is
removed.

5. Check whether the Tx optical power is normal at the opposite end station. If the
Tx optical power is normal, clean the pigtail fiber connector at the opposite end
station to see whether the alarm is removed. If not, operate as below.

1) Replace the optical module or the card on the opposite end station to see
whether the alarm is removed.

2) If the alarm persists, check whether the optical attenuator exists and
whether the attenuation value is appropriate. If not, adjust the attenuation
value to see whether the alarm is removed.

3) If the alarm persists, check whether the ring flange and the optical
attenuator at the local station is correctly connected. Connect the ring
flange and the optical attenuator correctly to see whether the alarm is
removed.

Version: A 123
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. If the alarm persists, check whether the optical cable is faulty. If yes, handle the
fault to see whether the alarm is removed.

7. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

8. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card.

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.56 HP_NPJE_ALARM
Meaning

Higher order path negative pointer adjustment threshold-crossing alarm

Alarm level

Major alarm

Relevant card

XGJ1, XSJ2, XSJ3

Influence on the system

The service may be interrupted in the alarmed channel when the alarm is generated.

Possible cause

u The optical fiber connector is contaminated or is in poor connection.

u The optical module is faulty.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_NPJE_ALARM alarm and confirm the
information such as the NE or line that generates the alarm.

124 Version: A
 3 Alarm Handling

2. Clear the NE's performance and observe for 15 minutes to check whether the
alarm appears.

Note:

Clear the NE performance: In the OTNM2000 window, right-click the NE

in the Logical Tree and select Clear NE Performance from the shortcut
menu, and select Yes in the Clear NE Performance window that
appears subsequently to clear the performance of the NE.

3. If the alarm persists, clear the optical fiber connector and make sure that the
optical fiber connector is firmly connected.

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

5. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

6. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.57 HP_PPJE_ALARM
Meaning

Higher order path positive pointer adjustment threshold-crossing alarm.

Alarm level

Major alarm

Relevant card

XGJ1, XSJ2, XSJ3

Influence on the system

This alarm will influence the service performance and cause the service unstable.

Version: A 125
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

The configuration of the HP_PPJE_ALARM threshold value is over-low.

Handling method

1. Enter the OTNM2000 to check the HP_PPJE_ALARM alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. In the Global_Config of the Card Configuration tab, check the setting of the
HP_PPJE_ALARM alarm threshold and modify it into a reasonable value.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.58 HP_RDI
Meaning

The remote defect indication alarm of the higher order path. This alarm occurs when
the far end transmits back a HP-RDI signal to the local end after receiving alarms
such as MS_AIS, AU_LOP, HP_UNEQ and HP_TIM.

Alarm level

Minor alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

The far end service receiving of the alarmed line will be interrupted when the
HP_RDI alarm occurs.

Possible cause

u The alarms such as MS_AIS, AU_LOP, HP_UNEQ and HP_TIM exist at the far
end.

u The receiving at the far end is faulty.

126 Version: A
 3 Alarm Handling

u The transmitting at the local end is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_RDI alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the alarm such as MS_AIS, AU_LOP, HP_UNEQ and HP_TIM
exists.

4 If yes, handle alarms first, such as MS_AIS, AU_LOP, HP_UNEQ, HP_TIM.

If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the receiving at the opposite end equipment is normal.

4 If the receiving at the opposite end equipment is normal, ➔ Step 4.

4 If the receiving of the opposite end equipment is faulty, find the cause and
eliminate the fault. If the alarm persists, ➔ Step 4.

4. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

5. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

6. Wait a few minutes. If the alarm persist after restarting the card, please contact
FiberHome after-sales maintenance engineer.

3.59 HP_SD./HP_SD
Meaning

The signal degradation alarm of the higher order path. This alarm occurs when the
bit error ratio of the tested equipment exceeds the threshold.

Alarm level

Critical alarm

Version: A 127
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

u HP_SD. : S1J1, XSJ2, XSJ3

u HP_SD: S1O1

Influence on the system

The service may be interrupted in the alarmed channel when the alarm occurs.

Possible cause

u The input optical power is over-low or over-high.

u The alarmed card is faulty.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

Handling method

1. Enter the OTNM2000 to check the HP_SD./HP_SD alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Use the optical power meter to check whether the optical power is normal.

4 If yes, ➔ Step 3.

4 If not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for

troubleshooting. If the alarm persists, ➔ Step 3.

3. If the alarm persists, check and eliminate the optical fiber fault.

4. If the alarm persists, replace the alarmed card (referring to CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

128 Version: A
 3 Alarm Handling

3.60 HP_SES_LIMIT
Meaning

The severely errored second threshold-crossing alarm of the higher order path. The
severely errored second refers to a one-second period that contains over 30%
errored blocks or at least one severely disturbed period. This alarm occurs if the
total number of the severely errored second of the higher order path exceeds the
HP_SES_LIMIT threshold set in the OTNM2000 within 15 minutes.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1J1, XSJ2, XSJ3, S1J4

Influence on the system

The service may be interrupted in the alarmed line when the alarm occurs.

Possible cause

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The B1 error of the regenerator section and the B2 error of the multiplex section
cause the B3 error of the higher order path.

u The card on the local end or the far end is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_SES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Eliminate the external fault such as the abnormal temperature in the equipment
room, poor grounding or the interference source.

Version: A 129
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Check whether the RS_BBE_LIMIT and MS_BBE_LIMIT alarms related to the

B1 and B2 errors exist in the alarmed optical interface.

4 If yes, see MS_SES_LIMIT and RS_SES_LIMIT for troubleshooting. If the

HP_BBE_LIMIT alarm persists after clearing the RS_BBE_LIMIT and
MS_BBE_LIMIT alarms, ➔ Step 4.

4 If not, ➔ Step 4.

4. Perform the loopback on the optical interface on the far end at the line side
(users can use the optical attenuator during the optical fiber loopback to ensure
the Rx optical power is within the normal range) and check whether the newly
added B3 error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 If yes: the previous station may be faulty. Isolate the previous station and
the specified faulty point that triggers the alarm according to the service
direction using loopback, and eliminate the fault by plugging and
unplugging or replacing the optical card and the clock and cross-connect
card. If the alarm persists, ➔ Step 5.

5. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. Please contact FiberHome after-sales maintenance engineer.

3.61 HP_SLM
Meaning

The signal label mismatch alarm of the higher order path. This alarm occurs when
the actually received C2 value by the card is not consistent with the expected
received C2 value.

130 Version: A
 3 Alarm Handling

Alarm level

Critical alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

The service may be interrupted in the alarmed channel when the alarm is generated.

Possible cause

u The OTNM2000 configuration is incorrect. As a result, the expected received

C2 value on the local end is inconsistent with the C2 value transmitted by the
far end.

u The service configuration data is incorrect.

Handling method

1. Enter the OTNM2000 to check the HP_SLM alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Isolate the source station of the received C2 byte toward the previous station
along the service.

3. Check whether the expected received C2 value on the local end is inconsistent
with the C2 value transmitted by the opposite end.

4 If yes, ➔ Step 3.

4 If not, re-set the C2 value to ensure the expected received C2 value on the
local end is consistent with the C2 value transmitted by the opposite end. If
the alarm persists, ➔ Step 3.

4. Check whether the configurations of the local end and the far end are correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

5. Please contact FiberHome after-sales maintenance engineer.

Version: A 131
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.62 HP_SLU.
Meaning

Higher order path signal label unstable alarm. This alarm occurs when the actually
received C2 value by the card is not consistent with the expected received C2 value.

Alarm level

Major alarm

Relevant card

S1J1

Influence on the system

The service may be interrupted in the alarmed channel when the HP_SLU. alarm
occurs.

Possible cause

u The OTNM2000 configuration is incorrect. As a result, the expected received

C2 value on the local end is inconsistent with the C2 value transmitted by the
far end.

u The cross-connect configuration is incorrect.

Handling method

1. Enter the OTNM2000 to check the HP_SLU. alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Isolate the source station of the received C2 byte toward the previous station
along the service.

3. Check whether the expected received C2 value on the local end is inconsistent
with the C2 value transmitted by the far end. Check the C2 value in the S1J1
card configuration GUI.

4 If yes, ➔ Step 3.

132 Version: A
 3 Alarm Handling

4 If not, re-set the C2 value to ensure the expected received C2 value on the
local end is consistent with the C2 value transmitted by the opposite end. If
the alarm persists, ➔ Step 3.

4. Check whether the cross-connect configurations of the local end and the far
end are correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

5. Please contact FiberHome after-sales maintenance engineer.

3.63 HP_TIM
Meaning

The trace identifier mismatch alarm of the higher order path. This alarm occurs
when the actually received J1 value by the card is not consistent with the expected
received J1 value.

Alarm level

Critical alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

The service may be interrupted in the alarmed channel when the HP_TIM alarm
occurs.

Possible cause

u The OTNM2000 configuration is incorrect. As a result, the expected received

J1 value on the local end is inconsistent with the J1 value transmitted by the
opposite end.

u The service configuration data is incorrect.

Version: A 133
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

1. Enter the OTNM2000 to check the HP_TIM alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Isolate the source station of the received J1 byte toward the previous station
along the service.

3. Check whether the expected received J1 value on the local end is inconsistent
with the J1 value transmitted by the far end. Check the J1 value in the S1J4
card configuration GUI.

4 If yes, ➔ Step 4.

4 If not, re-set the J1 value to make the expected received J1 value on the
local end consistent with the J1 value transmitted by the far end. If the
alarm persists, ➔ Step 4.

4. Check whether the configurations of the local end and the far end are correct.

4 If yes, ➔ Step 5.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

3.64 HP_TIU.
Meaning

Higher order path trace identifier unstable alarm. This alarm occurs when the
actually received J1 value by the card is not consistent with the expected received
J1 value.

Alarm level

Major alarm

Relevant card

S1J1

134 Version: A
 3 Alarm Handling

Influence on the system

The service may be interrupted in the alarmed channel when the HP_TIU. alarm
occurs.

Possible cause

u The OTNM2000 configuration is incorrect. As a result, the expected received

J1 value on the local end is inconsistent with the J1 value transmitted by the far
end.

u The service configuration data is incorrect.

Handling procedure

1. Enter the OTNM2000 to check the HP_TIU. alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Isolate the source station of the received J1 byte toward the previous station
along the service.

3. Check whether the expected received J1 value on the local end is inconsistent
with the J1 value transmitted by the far end. Check the J1 value in the S1J1
card configuration GUI.

4 If yes, ➔ Step 4.

4 If not, re-set the J1 value to make the expected received J1 value on the
local end consistent with the J1 value transmitted by the far end. If the
alarm persists, ➔ Step 3.

4. Check whether the configurations of the local end and the far end are correct.

4 If yes, ➔ Step 5.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

Version: A 135
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.65 HP_UNEQ/HP_UNEQ.
Meaning

The higher order path unequipped alarm. This alarm occurs when the local station
receives byte C2 of 00H exceeding 5 frames.

Alarm level

Critical alarm

Relevant card

u HP_UNEQ: S1J4

u HP_UNEQ.: S1J2

Influence on the system

The service may be interrupted in the alarmed channel when the HP_UNEQ alarm
is generated.

Possible cause

u The service corresponding to the local end is not configured at the opposite
end.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the HP_UNEQ alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the service is configured in the corresponding path of the local
end and the opposite end.

4 If not, configure the path service corresponding to the local end at the
opposite end according to the actual project. If the alarm persists, ➔ Step
3.

4 If yes, ➔ Step 3.

136 Version: A
 3 Alarm Handling

3. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

4. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

5. Wait a few minutes. If the alarm persists after re-starting the card, please
contact FiberHome after-sales maintenance engineer.

3.66 IOP_HIGH/IOPM_HIGH.
Meaning

The over-high input optical power alarm. The alarm occurs when the input optical
power is higher than the Input_OP_High_Threshold preset via the configuration
item of the OTNM2000.

Alarm level

u IOP_HIGH: major alarm

u IOP_HIGH: minor alarm

Relevant card

u IOP_HIGH: XGJ1, GSJ2, GSJ3, S1O1, ESJ2, S1J4

u IOP_HIGH.: S1J1, S1J2, XSJ2, XSJ3

Influence on the system

The service may be degraded or interrupted in the alarmed line when the alarm
occurs.

Possible cause

u The input optical power is too high without an appropriate attenuator.

u The output optical power of the card at the opposite end station is too high.

u The Input_OP_High_Threshold preset via the configuration item of the

OTNM2000 is too low.

Version: A 137
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the IOP_HIGH alarm and confirm the
information such as the NE or line that generates the alarm.

2. Calculate the normal range of the input optical power according to the
configuration of the line attenuation and attenuator. Check whether the Rx
range of the optical module's optical power complies with the above
requirements.

4 If not, select the proper optical module.

4 If yes, ➔ Step 3.

Note:

Check the optical module type configured in each line in the status GUI of
the card in the OTNM2000.

3. Check whether the input optical power of the alarmed card is within the normal
range using the optical power meter.

4 If the input optical power is over-high: add proper attenuators to adjust the
input optical power to a normal range. If the alarm persists, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Replace the optical module (see CiTRANS 660 High-capacity MPLS-TP

Platform Routine Maintenance Plugging and Unplugging Cards).

5. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. Please contact FiberHome after-sales maintenance engineer.

138 Version: A
 3 Alarm Handling

3.67 IOP_LOW/IOP_LOW.
Meaning

The input optical power over-low alarm. This alarm occurs when the input power of
the optical module is over-low.

Alarm level

Major alarm

Relevant card

u IOP_LOW: XGJ1, GSJ3, S1O1, ESJ2, S1J4

u IOP_LOW.: GSJ2, S1J1, S1J2, XSJ2, XSJ3, GSJ2

Possible cause

u The optical module is not present.

u The setting of the optical power threshold value is incorrect.

u The fiber connector is loose and the ring flange is connected incorrectly.

u The optical fiber head is unclean.

u The pigtail is over bent, damaged or aged.

u The receiving optical interface of the local card is equipped an over-high optical
attenuator.

u The optical signal is over attenuated during the transmission and receives
inadequate optical amplifying compensation.

u The over-high optical attenuator is added to the Tx port on the far end card or
the Tx optical module is faulty, causing that the Tx optical power of the opposite
end card is over-low.

u The alarmed card on the local end is faulty.

Handling method

1. Enter the OTNM2000 to check the IOP_LOW/IOP_LOW. alarm and confirm the
information such as the NE, card or line that generates the alarm.

Version: A 139
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check the optical module of the alarmed card and make sure it is present.

3. In the OTNM2000 GUI, check the thresholds of the related optical interfaces
and make sure they are set appropriately.

4. If the alarm persists, check the pigtail of the alarmed card. If the pigtail is over
bent, damaged or aged, adjust or replace it.

5. If the alarm persists, check whether the ring flange at the local station is
connected correctly. Use the ring flange correctly and secure the relevant
optical fiber connector to see whether the alarm is removed.

6. If the alarm persists, check whether the receiving optical interface of the local
card is equipped with the over-high optical attenuator; if yes, lower the
attenuation value or replace the optical attenuator.

7. Check whether the input optical power of the card at the local end is within the
allowed range using the optical power meter.

4 If yes, ➔ Step 8.

4 If not, check whether the optical fiber connector is contaminated; if yes,

clean the fiber connector and the card receiving optical interface at the
local station.

8. If the alarm persists, check whether the output optical power of the opposite
end card is within the normal range using the OTNM2000.

4 If yes, ➔ Step 9.

4 If not, clean the fiber connector and the card optical interface, and secure
the relevant optical fiber connector to see whether the alarm is removed.

9. If the alarm persists, check whether the Tx optical interface on the far end card
is equipped with the over-high optical attenuator; if yes, lower the attenuation
value or replace the optical attenuator.

10. If the alarm persists, replace the optical module or the card on the opposite
end to see whether the alarm is removed.

11. If the alarm persists, the local end card may be faulty. Replace the alarmed
card (see CiTRANS 660 High-capacity MPLS-TP Platform Routine
Maintenance for operation procedures).

12. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

140 Version: A
 3 Alarm Handling

3.68 LASER_CCT
Meaning

The laser bias current threshold-crossing alarm.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ3, ESJ2, XSJ2, XSJ3

Influence on the system

After this alarm occurs, the laser gain will be inadequate or the laser will be
damaged, and the service will be interrupted.

Possible cause

u The temperature of the card’s operation environment is over-high or over-low,

which influences the normal operation of the laser.

u The laser is aged.

u The card is faulty.

Handling method

1. Enter the OTNM2000 to check the LASER_CCT alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the ambient temperature of the equipment room is normal:

4 If not, adjust the ambient temperature of the equipment room using air
conditioners.

4 If yes, ➔ Step 3.

3. On condition that the service will not be influenced, plug and unplug the
alarmed card. (see Plugging and Unplugging Cards for operation procedures).

Version: A 141
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. If the alarm persists, replace the optical module on the alarmed card (referring
to CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance for
operation procedures).

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

3.69 LASER_OFF
Meaning

The laser soft shut-off alarm.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3, GSJ3, S1O1, ESJ2, S1J1, S1J2, S1J4

Influence on the system

The services will be interrupted after the laser is shut off.

Possible cause

u The Laser_NM_Close_Enable item in the card configuration GUI is set to

Allow and execute the Disable command to the laser of the optical module.

u The optical module is faulty.

Handling method

1. Enter the OTNM2000 to check the LASER_OFF alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Enter the control command GUI of the alarmed card to check whether the
Disable command is delivered to the laser.

4 If the laser is set to Disable, re-set it to Enable and re-deliver the control
command.

142 Version: A
 3 Alarm Handling

4 If the laser is set to Enable, ➔ Step 3.

3. Replace the optical module of the card to check whether the alarm is removed.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.70 LASER_TCT
Meaning

The laser temperature threshold-crossing alarm. This alarm occurs when the laser
operation temperature exceeds the threshold.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, GSJ3, ESJ2, XSJ2, XSJ3

Influence on the system

The laser operation temperature is over-high so that the laser is in high-risk status.
The faults such as bit error and service interruption may be caused if the laser
continuously operates in high temperature.

Possible cause

u The ambient temperature is over-high.

u The temperature threshold of the laser is set too low.

u The laser of the card is faulty.

Handling method

1. Enter the OTNM2000 to check the LASER_TCT alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the ambient temperature of the equipment room is normal:

Version: A 143
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, adjust the ambient temperature of the equipment room using air
cooling conditioner.

4 If yes, ➔ Step 3.

3. Check whether the threshold value of the laser set in the OTNM2000 is over-
low.

4 If yes, adjust the threshold value properly.

4 If not, ➔ Step 4.

4. On condition that the service will not be influenced, plug and unplug the
alarmed card and the alarmed optical module (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

5. If the alarm persists, replace the alarmed optical module and the alarmed card
(see CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance for
operation procedures).

3.71 LASER_TF
Meaning

The laser transmission failure alarm.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, GSJ3, S1J1, XSJ2, XSJ3

Influence on the system

The opposite end fails to receive optical signals.

Possible cause

The output optical power is smaller than the critical value of the output optical power.

144 Version: A
 3 Alarm Handling

Handling procedure

1. Enter the OTNM2000 to check the LASER_TF alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check the optical power of the input port on the alarmed card and ensure it is in
the normal range.

3. If the laser optical module supports the hot insertion, replace the laser module
(See CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance for
specific procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

3.72 LINK_LOS
Meaning

The connection signal loss alarm. This alarm indicates that the port cannot receive
the service signals. The detailed conditions are as follows:

u The connection between the local line port and the opposite end line port is
interrupted.

u The connection between the local system port and the clock and cross-connect
card is interrupted.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3, S1O1, ESJ1, ESJ2, S1J1, S1J2, S1J4, E1J1, E1J2

Influence on the system

After this alarm occurs, the data cannot be received to the port and the service will
be interrupted.

Version: A 145
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The optical module is not connected.

u The optical fiber is faulty.

u The opposite end transmission equipment is faulty.

u The local end receiving equipment is faulty.

u The clock and cross-connect card fails.

Handling method

1. Enter the OTNM2000 to check the LINK_LOS alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the optical module of the alarmed card is not connected with
the optical fiber or the fiber is loose; if yes, connect it with the optical fiber.

3. If the alarm persists, check whether the optical fiber is faulty. If yes, replace the
faulty optical fiber to see whether the alarm is removed.

4. If the alarm persists, check whether the Tx optical power of the opposite end is
normal:

4 If not, replace the opposite end card and check whether the alarm is
removed.

4 If yes, ➔ Step 5.

5. If the alarm persists, the local end card may be faulty. Replace the alarmed
card (see CiTRANS 660 High-capacity MPLS-TP Platform Routine
Maintenance for operation procedures).

6. If the alarm persists, the clock and cross-connect card of the local station may
be faulty and replace it.

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

146 Version: A
 3 Alarm Handling

3.73 LOCK_MAIN
Meaning

The lock-to-main alarm. This alarm occurs when the OTM2000 delivers the lock-
to-main command.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The LOCK_MAIN alarm indicates that the OTNM2000 delivered the Lock_to_Main
command. The Lock_to_Main command is mainly used for testing, and should be
cleared in a timely manner after the test.

Possible cause

The OTNM2000 has delivered the Lock_to_Main command.

Handling method

1. Enter the OTNM2000 to check the LOCK_MAIN alarm and confirm the
information such as the NE or line that generates the alarm.

2. Enter the control command GUI of the alarmed card and confirm whether the
command executed by the alarmed card is necessary.

4 If yes, no handling is needed.

4 If not, clear the command.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 147
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.74 LOF_2M
Meaning

E1 signal loss of frame alarm.

Alarm level

Critical alarm

Relevant card

E1J1

Influence on the system

When the alarm occurs, the service may be interrupted in the Rx direction of the
local station.

Possible cause

u The service configuration is faulty.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the LOF_2M alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check the service configuration of the alarmed NE and the opposite NE and
ensure that the service configuration is correct.

3. Plug and unplug or replace the alarmed card.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

148 Version: A
 3 Alarm Handling

3.75 LOOP
Meaning

The equipment loopback. This alarm occurs when the SET-DLB in the control
command is set to Enable and the OTNM2000 delivers the command.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, GSJ3, S1O1, S1J1, XSJ2, XSJ3, S1J2, S1J4, E1J1, E1J2

Influence on the system

The equipment loopback will cause that the service signal fails to be transmitted to
the far end.

Possible cause

The equipment loopback command is delivered for test or maintenance.

Handling method

1. Enter the OTNM2000 to check the LOOP alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the equipment loopback is set for the test or maintenance. After
the test or maintenance is completed, set the SET-DLB control command of the
corresponding interface to Disable, and deliver the control command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

Version: A 149
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.76 LOOP(T)
Meaning

The tributary loopback or equipment loopback alarm. This alarm occurs when the
Trib-SET-DLB in the control command is set to Enable.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J4

Influence on the system

The tributary equipment loopback will make the service signal fail to be transmitted
to the opposite end.

Possible cause

The tributary equipment loopback command is delivered for test or maintenance.

Handling method

1. Enter the OTNM2000 to check the LOOP(T) alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the tributary equipment loopback is set for test or maintenance.
After the test or maintenance is completed, set the Trib-SET-DLB control
command of the corresponding interface to Disable, and deliver the control
command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

150 Version: A
 3 Alarm Handling

3.77 LOOPL
Meaning

The line loopback alarm. This alarm occurs when the SET-LLB in the control
command is set to Enable and the OTNM2000 delivers the command.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, GSJ3, XSJ2, XSJ3, S1O1, S1J1, S1J2, S1J4, E1J1, E1J2

Influence on the system

The line loopback causes the service signal failed to be transmitted to the opposite
end.

Possible cause

The line loopback command is delivered for test or maintenance.

Handling procedure

1. Enter the OTNM2000 to check the LOOPL alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the line loopback is set for test or maintenance. After the test or
maintenance is completed, set the SET-LLB control command of the
corresponding interface to Disable, and deliver the control command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

Version: A 151
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.78 LOOPL(T)
Meaning

The tributary line loopback alarm. This alarm occurs when the Trib-SET-DLB in the
control command is set to Enable.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J4

Influence on the system

The tributary line loopback causes the service signal failed to be transmitted to the
opposite end.

Possible cause

The tributary line loopback command is delivered for test or maintenance.

Handling procedure

1. Enter the OTNM2000 to check the LOOPL(T) alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the tributary line loopback is set for test or maintenance. After
the test or maintenance is completed, set the Trib-SET-DLB control command
of the corresponding interface to Disable, and deliver the control command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

152 Version: A
 3 Alarm Handling

3.79 LOOPL_L
Meaning

The aggregate line loopback alarm. This alarm occurs when the AGG-SET-DLB in
the control command is set to Enable and the OTNM2000 delivers the command.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J4

Influence on the system

The aggregate line loopback causes the service signal failed to be transmitted to the
far end.

Possible cause

The aggregate line loopback command is delivered for test or maintenance.

Handling method

1. Enter the OTNM2000 to check the LOOPL_L alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the aggregate line loopback is set for test or maintenance. After
the test or maintenance is completed, set the AGG-SET-DLB control command
of the corresponding interface to Disable, and deliver the control command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

Version: A 153
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.80 LOOP_L
Meaning

The aggregate equipment loopback alarm. This alarm occurs when the SET-DLB in
the control command is set to Enable and the OTNM2000 delivers the command.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J4

Influence on the system

The aggregate equipment loopback causes the service signal failed to be

transmitted to the far end.

Possible cause

The line loopback command is delivered for test or maintenance.

Handling method

1. Enter the OTNM2000 to check the LOOP_L alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the line loopback is set for test or maintenance. After the test or
maintenance is completed, set the SET-DLB control command of the
corresponding interface to Disable, and deliver the control command.

3. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

154 Version: A
 3 Alarm Handling

3.81 LP_AIS
Meaning

Lower order path alarm indication alarm. The VC12 payload consecutively detects
the data 1 and the LP_AIS alarm is reported.

Alarm level

Prompt alarm

Relevant card

S1J2

Influence on the system

When the alarm occurs, the service of the alarmed line in the Rx direction of the
local station is interrupted.

Possible cause

u When the previous signal transmission fails, for example, alarms, such as LOS,
LOF, RS_EXC, MS_AIS, MS_EXC, AU_AIS, AU_LOP, are received, the Tx
equipment transmits the alarm indication AIS signals to the downlink direction.

u Services are not configured to the line or the cross-connect configuration of the
service in the OTNM2000 is incorrect.

u The opposite end equipment fails, for example, the signal between the clock
and cross-connect card and the optical card is interrupted, the optical card at
the opposite end fails.

u The card at the local end fails.

Handling method

1. Enter the OTNM2000 to check the LP_AIS alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the signal transmission failure exists in each previous station
according to the service flow of the lower order path.

Version: A 155
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, eliminate the signal transmission failure fault of the previous station
and see RS_EXC./RS_EXC, MS_AIS, MS_EXC, AU_AIS and AU_LOP for
troubleshooting. If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Loopback optical signals at the opposite end and check whether the TU_AIS or
LP_AIS alarm exists in the optical Rx direction after loopback.

4 If no TU_AIS or LP_AIS alarm exists, replace the local station card. If the
alarm persists, ➔ Step 7.

4 If the TU_AIS or LP_AIS alarm exists, the faulty point is at the opposite
end station. If the FiberHome equipment is in the opposite end station, ➔
Step 4; if the FiberHome equipment is not in the opposite end station, see
the equipment manual of the opposite end station for troubleshooting.

4. Check whether the cross-connect configuration of the opposite / local end

station is correct. If not, re-configure. If the cross-connect configuration is
correct and the alarm persists, ➔ Step 5.

5. Re-pug and re-unplug or replace the card in the opposite end station. If the
alarm persists, ➔ Step 6.

6. Switch the active and standby clock and cross-connect card in the opposite
end station or plug and unplug or replace the clock and cross-connect card in
the opposite end station. If the alarm persists, ➔ Step 7.

7. Please contact FiberHome after-sales maintenance engineer.

3.82 LP_BBE_LIMIT
Meaning

The background block error threshold-crossing alarm of the lower order path. The
alarm occurs when the lower order path background block error exceeds the
threshold value set in the OTNM2000.

Alarm level

Prompt alarm

156 Version: A
 3 Alarm Handling

Relevant card

S1O1, S1J4

Influence on the system

The lower order path background block error threshold-crossing will influence the
service quality of the alarmed lower order path.

Possible cause

u The input optical power is over-low or over-high.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_BBE_LIMIT alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Clear the NE performance: In the OTNM2000 window, right-click the NE in the

Logical Tree and select Clear NE Performance from the shortcut menu, and
select Yes in the Clear NE Performance window that appears subsequently to
clear the performance of the NE. Check whether the alarm is removed after 15
minutes. If the alarm persists, ➔ Step 3.

3. Measure the input optical power and check whether the Rx optical fiber of the
alarmed optical interface is within the normal range.

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling. If the alarm persists, ➔ Step 4.

4 If the input optical power is normal, check whether the end of optical fiber
of the optical module output interface is clean, and check whether the
optical fiber and the optical interface is loose. Clean the end of the optical
fiber of the optical fiber and re-connect the optical fiber. If the alarm
persists, ➔ Step 4.

4. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

5. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

Version: A 157
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. Please contact FiberHome after-sales maintenance engineer.

3.83 LP_ES_LIMIT
Meaning

The errored second threshold-crossing alarm of the lower order path.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

The alarm occurs when the service performance in the alarmed line may be
degraded.

Possible cause

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The input optical power is over-low or over-high.

u The card on the local end or the opposite end is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_ES_LIMIT alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Eliminate the external fault such as the abnormal temperature in the equipment
room, the poor grounding or the interference source.

3. Clear the NE performance and check whether the alarm is removed after 15
minutes. If the alarm persists, ➔ Step 4.

158 Version: A
 3 Alarm Handling

4. Check and eliminate the optical line fault. If the alarm persists, ➔ Step 5.

5. Perform the loopback on the optical interface on the far end line side (users can
use the optical attenuator during the optical fiber loopback to ensure the Rx
optical power is within the normal range) and check whether the newly added
B3 error exists in the current performance.

4 If not, ➔ Step 6.

4 If yes, faults exist in the opposite end. If the FiberHome equipment is in the
opposite end station, ➔ Step 6; if the FiberHome equipment is not in the
opposite end station, see the equipment manual of the opposite end
station for troubleshooting.

6. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

8. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

9. Please contact FiberHome after-sales maintenance engineer.

3.84 LP_EXC
Meaning

The bit error ratio threshold-crossing alarm of the lower order path. The alarm
occurs when the lower order path bit error ratio exceeds the threshold value set in
the OTNM2000.

Alarm level

Major alarm

Relevant card

S1O1, S1J1, S1J4

Version: A 159
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The data quality of the lower order path degrades.

Possible cause

u The higher level alarms such as MS_EXC, MS_SD, RS_EXC, RS_SD exist.

u The card temperature is over high and the TEMP_TCT alarm exists.

u The equipment of the opposite end is faulty.

u Physical connection fault, such as broken pigtail, too small bend radius of the
pigtail fiber, poor contact of the ring flange and unclean optical interface.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_EXC alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the higher level alarms like MS_EXC, MS_SD, RS_EXC,
RS_SD exist on the local end.

4 If yes, process the higher level alarms such as MS_EXC, MS_SD,

RS_EXC, RS_SD first. If the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the TEMP_TCT alarm exists in the alarmed card.

4 If yes, process the TEMP_TCT alarm first. If the alarm persists, ➔ Step 4.

4 If not, ➔ Step 4.

4. Check whether the transmission of the opposite end equipment is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the transmission fault on the opposite end first. If the alarm
persists after the above operation, ➔ Step 5.

5. Check whether the pigtail connection on the UNI side of the local alarmed card
is normal. Ensure that the situation such as broken pigtail, too small bend
radius of the pigtail fiber, poor contact of the ring flange and unclean optical
interface does not exist.

4 If yes, ➔ Step 6.

160 Version: A
 3 Alarm Handling

4 If not, eliminate the physical connection fault first. If the alarm persists after
the above operation, ➔ Step 6.

6. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

8. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.85 LP_LOP
Meaning

Lower order path pointer loss alarm. The LP_LOP alarm is reported when the lower
order path pointer detects the consecutive all 1 pattern.

Alarm level

Major alarm

Relevant card

S1J2

Influence on the system

When the alarm occurs, the lower order service of the alarmed line in the Rx
direction of the local station is interrupted.

Possible cause

The invalid pointer value is received in the tributary card.

Handling method

1. Enter the OTNM2000 to check the LP_LOP alarm and confirm the information
such as the NE or line that generates the alarm.

Version: A 161
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check whether higher level alarms than the LOP alarm exist; if yes, eliminate
the higher level alarm first. If the alarm persists, ➔ Step 3.

3. Check whether the cross-connect configuration at the opposite / local end

station is correct. If not, re-configure. If the alarm persists, ➔ Step 4.

4. Replace the tributary card at the opposite end. If the alarm persists, ➔ Step 5.

5. Replace the tributary card at the local end. If the alarm persists, ➔ Step 6.

6. Please contact FiberHome after-sales maintenance engineer.

3.86 LP_RDI
Meaning

The remote defect indication alarm of the lower order path. This alarm occurs when
the opposite end transmits back the RDI signal to the local end after receiving TU-
AIS, LP-TIM or LP-UNEQ alarms.

Alarm level

Minor alarm

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

The Rx service at the opposite end of the alarmed line is interrupted when the
LP_RDI alarm occurs.

Possible cause

u The alarms such as TU_AIS, LP_TIM and LP_UNEQ exist at the opposite end.

u The receiving equipment at the opposite end is faulty.

u The transmitting equipment at the local end is faulty.

162 Version: A
 3 Alarm Handling

Handling method

1. Enter the OTNM2000 to check the LP_RDI alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether alarms, such as TU_AIS, LP_TIM or LP_UNEQ exist in the

opposite end.

4 If yes, process the alarms, such as TU_AIS, LP_TIM or LP_UNEQ at the

opposite end. After this operation, if the MS_RDI alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the receiving of the opposite end equipment is normal.

4 If yes, ➔ Step 4.

4 If not, process the receiving faults at the opposite end first. If the alarm
persists, ➔ Step 4.

4. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

5. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.87 LP_SD
Meaning

The signal degradation alarm of the lower order path.

Alarm level

Minor alarm

Relevant card

S1O1, S1J1, S1J4

Version: A 163
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The service quality of the alarmed lower order path degrades when the alarm occurs.

Possible cause

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The B1 error of the regenerator section, the B2 error of the multiplex section
and the B3 error of the higher order path cause the error of lower order path.

u The input optical power is over-low or over-high.

u The card on the local end or the opposite end is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_SD alarm and confirm the information
such as the NE or line that generates the alarm.

2. Eliminate the external fault such as the abnormal temperature in the equipment
room, poor grounding or the interference source.

3. Check whether the B1, B2 and B3 errors exist in the alarmed optical interface.

4 If yes, see MS_BBE_LIMIT, RS_BBE_LIMIT and HP_BBE_LIMIT for

troubleshooting If the alarm persists after the above operation, ➔ Step 4.

4 If not, ➔ Step 4.

4. Perform the loopback on the optical interface of the opposite end at the line
side (users can use the optical attenuator during the optical fiber loopback to
ensure the Rx optical power is within the normal range) and check whether the
newly added lower order path error exists in the current performance.

4 If not, ➔ Step 5.

4 If yes: the previous station is faulty. Eliminate the fault of the previous
station. If the alarm persists, ➔ Step 5.

5. Plug and unplug or re-insert the alarmed card (see Plugging and Unplugging
Cards for operation procedures).

164 Version: A
 3 Alarm Handling

6. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

7. If the alarm persists, perform the switching between the active and standby
clock and cross-connect cards at the local station, or plug and unplug or
replace the clock and cross-connect card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance).

8. Please contact FiberHome after-sales maintenance engineer.

3.88 LP_SES_LIMIT
Meaning

The severely errored second threshold-crossing alarm of the lower order path.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

The service performance degrades when the alarm is generated.

Possible cause

u The input optical power is over-low or over-high.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_SES_LIMIT alarm and confirm the
information such as the NE, card or line that generates the alarm.

Version: A 165
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Clear the NE performance and check whether the alarm is removed after 15
minutes. If the alarm persists, ➔ Step 3.

3. Check and eliminate the optical line fault. If the alarm persists, ➔ Step 4.

4. Replace the alarmed card (see CiTRANS 660 High-capacity MPLS-TP

Platform Routine Maintenance). If the alarm persists, ➔ Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

3.89 LP_SLM
Meaning

The signal label mismatch alarm of the lower order path. This alarm occurs when
the bit5 to bit7 value in the actually received V5 byte by the local card is not
consistent with the expected value.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

The LP_SLM alarm occurs when the service may be interrupted in the alarmed
channel.

Possible cause

u The OTNM2000 configuration is incorrect. As a result, the bit5 to bit7 value in

the expected received V5 byte is inconsistent with the Tx value by the far end.

u The service configuration data is incorrect.

Handling method

1. Enter the OTNM2000 to check the LP_SLM alarm and confirm the information
such as the NE, card or line that generates the alarm.

166 Version: A
 3 Alarm Handling

2. Check whether the expected received bit5 to bit7 value in the V5 byte at the
local end is consistent with the Tx value by the opposite end.

4 If yes, ➔ Step 3.

4 If not, re-set the bit5 to bit7 value in the V5 byte to make the expected
received value on the local end consistent with the value transmitted by the
opposite end. If the alarm persists, ➔ Step 3.

3. Check whether the configurations of the local end and the opposite end are
correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.90 LP_TIM
Meaning

The trace identifier mismatch alarm of the lower order path. This alarm occurs when
the actually received J2 value by the local card is inconsistent with the expected
received J2 value.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

The service may be interrupted in the alarmed channel when the LP_TIM alarm
occurs.

Version: A 167
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The OTNM2000 configuration is incorrect, causing that the expected received

J2 value on the local end is inconsistent with the J2 value transmitted by the
opposite end.

u The service configuration data is incorrect.

Handling procedure

1. Enter the OTNM2000 to check the LP_TIM alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the expected received J2 value on the local end is inconsistent
with the J2 value transmitted by the opposite end. Check the expected J2 value
in the Emulation_Config tab of the S1J4 card configuration GUI.

4 If yes, ➔ Step 3.

4 If not, re-set the J2 value to make the expected received J2 value on the
local end consistent with the J2 value transmitted by the opposite end. If
the alarm persists, ➔ Step 3.

3. Check whether the configuration data of the local end and the opposite end is
correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.91 LP_UNEQ
Meaning

The lower order path unequipped alarm. This alarm occurs when the bit5 to bit7
value value in the V5 byte is detected to be 000.

Alarm level

Minor alarm

168 Version: A
 3 Alarm Handling

Relevant card

S1O1, S1J4, S1J1

Influence on the system

When the LP_UNEQ alarm occurs, the system inserts an AIS alarm into the next
level circuit.

Possible cause

u The service corresponding to the local end is not configured at the opposite
end.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the LP_UNEQ alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the service is configured in the corresponding path at the local
end and the opposite end.

4 If not, configure the service between the local end at the opposite end
according to the actual project situation. If the alarm persists, ➔ Step 3.

4 If yes, ➔ Step 3.

3. Plug and unplug or re-insert the alarmed card (see Plugging and Unplugging
Cards for operation procedures).

4. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

5. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.92 LSYN_LOC
Meaning

Line synchronous clock loss alarm.

Version: A 169
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Critical alarm

Relevant card

XGJ1, S1J1, XSJ2, XSJ3

Influence on the system

The occurrence of the alarm may cause the service performance degraded or
interrupted.

Possible cause

The LSYN_LOC alarm is reported when the local end fails to track the line
synchronous clock.

Handling method

1. Enter the OTNM2000 to check the LSYN_LOC alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check the optical path between the local end and the opposite end and ensure
it is normal.

3. Check whether the card at the opposite end can transmit the line synchronous
clock signals and ensure the transmission is normal.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.93 LTI.
Meaning

The timing input loss alarm. This alarm occurs if the card at the local end fails to
receive the line clock.

Alarm level

Critical alarm

170 Version: A
 3 Alarm Handling

Relevant card

XCUJ2, XCUJ4

Influence on the system

The line clock interruption indicates that no external synchronization reference

source input exists or the quality of input clock is poor. When the system
synchronization reference source is locked as the line clock, the system can not
work normally and the bit error or the packet loss occurs.

Possible cause

u The line card is not present, causing no synchronization reference source input.

u The network management configuration of the line clock input is incorrect.

Handling method

1. Enter the OTNM2000 to check the LTI. alarm and confirm the alarmed NE.

2. Check whether the line card is present in the line clock input slot of the clock
and cross-connect card in the OTNM2000.

4 If yes, check whether the line service exists in this line card. If the clock
input does not exist in this card, and re-configure the line clock in the
network management system. See CiTRANS 660 High-capacity MPLS-TP
Platform Card Configuration Parameter Reference for the configuration
method. If the LTI. alarm still exists after the reconfiguration, ➔ Step 3.

4 If not, reconfigure the line clock in the OTNM2000, and see CiTRANS 660
High-capacity MPLS-TP Platform Configuration Guide for configuration
methods. If the LTI. alarm still exists after reconfiguration, ➔ Step 3.

3. Check whether the parameter settings such as the input source QL value of the
clock and cross-connect card in Card Configuration→Clock_Config of the
alarmed NE is appropriate.

4 If yes, ➔ Step 4.

4 If not, reconfigure the network management line clock configuration, see

CiTRANS 660 High-capacity MPLS-TP Platform Card Configuration
Parameter Reference for the configuration method. If the LTI. alarm
persists after reconfiguration, ➔ Step 4.

Version: A 171
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. Check whether the clock signal input cable is connected correctly. Ensure the
cable connection is correct and check whether the alarm is removed.

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.94 M_Asynchronous Active / Standby Alarms

Table 3-1 M_asynchronous active / standby alarms

Alarmed
Alarm Name Alarm Level Alarm Meaning
Card
M_ Asynchronous active / standby
Critical alarm NMUJ1
BADDRDIF management configuration

M_ Asynchronous active / standby extension

Critical alarm NMUJ1
BAREADIF domain configuration

M_ Asynchronous active / standby equipment

Critical alarm NMUJ1
BCFGRDIF configuration

M_ Asynchronous active / standby

Critical alarm NMUJ1
BCROSDIF configuration data

Asynchronous active / standby external

M_BCTRDIF Critical alarm NMUJ1
terminal configuration

M_ Asynchronous active / standby f enable

Critical alarm NMUJ1
BFENBDIF configuration

Asynchronous active / standby MCC

M_BMCCDIF Critical alarm NMUJ1
configuration

M_ Asynchronous active / standby MCC

Critical alarm NMUJ1
BMCCIRDIF interruption configuration

M_ Asynchronous active / standby MCF shut-

Critical alarm NMUJ1
BMCCSFDIF down configuration

M_ Asynchronous active / standby MCF

Critical alarm NMUJ1
BMCFRDIF configuration

M_ Asynchronous active / standby structure

Critical alarm NMUJ1
BSTRURDIF configuration

M_ Asynchronous active / standby

Prompt alarm NMUJ1
SADDRDIF management configuration

172 Version: A
 3 Alarm Handling

Table 3-1 M_asynchronous active / standby alarms (Continued)

Alarmed
Alarm Name Alarm Level Alarm Meaning
Card
M_ Asynchronous active / standby extension
Prompt alarm NMUJ1
SAREADIF domain configuration

M_ Asynchronous active / standby equipment

Prompt alarm NMUJ1
SCFGRDIF configuration

M_ Asynchronous active / standby

Prompt alarm NMUJ1
SCROSDIF configuration data

Asynchronous active / standby external

M_SCTRDIF Prompt alarm NMUJ1
terminal configuration

M_ Asynchronous active / standby f enable

Prompt alarm NMUJ1
SFENBDIF configuration

Asynchronous active / standby MCC

M_SMCCDIF Prompt alarm NMUJ1
configuration

M_ Asynchronous active / standby MCC

Prompt alarm NMUJ1
SMCCIRDIF interruption configuration

M_ Asynchronous active / standby MCC shut-

Prompt alarm NMUJ1
SMCCSFDIF down configuration

M_ Asynchronous active / standby MCF

Prompt alarm NMUJ1
SMCFRDIF configuration

M_ Asynchronous active / standby structure

Prompt alarm NMUJ1
SSTRURDIF configuration

Meaning

If the double NMUJ1 cards are present but the configuration of the active card is
inconsistent with that of the standby card, the active card will synchronize the
service data with the standby card. The system reports the prompt alarm of the
asynchronous item when discovering the asynchronous configuration, and the
active card delivers the synchronization configuration command to the standby card.
If the prompt alarm does not disappear in five minutes, the alarm will become critical
alarm to remind users to handle.

Alarm level

See Table 3-1.

Version: A 173
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

See Table 3-1.

Influence on the system

The prompt alarms will not influence the system and no handling is needed. when
the critical alarm occurs, the synchronization of the active / standby card fails; when
the active / standby switching occurs, the system will be influenced.

Possible cause

The reasons of the active / standby card's synchronization failure generating the
critical alarm are as following:

u The communication channel between the active and standby cards is faulty.

u The software version of the active and standby cards is inconsistent.

u The hardware of the active and standby cards is damaged.

Handling method

1. When the asynchronous active / standby prompt alarm occurs, the system will
synchronize the configuration of the active and standby cards automatically.
The alarm will disappear automatically after the synchronization is completed.
No handling is needed.

2. If the prompt alarm does not disappear in five minutes, the synchronization
configuration of the active and standby cards fails. Users should access the
status GUI of the active / standby card to check whether the card software
version is consistent; if not, upgrade the EMS card software.

3. If the alarm persists, replace the standby EMS card.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

174 Version: A
 3 Alarm Handling

3.95 M_SWITCH
Meaning

The switching of the active and standby management cards. The alarm occurs after
the switching of the active and standby management cards.

Alarm level

Prompt alarm

Relevant card

NMUJ1

Influence on the system

The prompt alarm does not influence the system.

Possible cause

Below are reasons why the M_SWITCH alarm occurs.

u The communication channel between the active and standby cards is faulty.

u The software version of the active and standby cards is inconsistent.

u The hardware of the active and standby cards is damaged.

Handling method

1. When the switching prompt alarm of the active / standby management card
occurs, the system will synchronize the configuration of the active and standby
cards automatically. The alarm will disappear automatically after the
synchronization is completed. No handling is needed.

2. If the prompt alarm does not disappear in five minutes, the synchronization
configuration of the active and standby cards fails. Users should access the
status GUI of the active / standby card to check whether the card software
version is consistent; if not, upgrade the EMS card software.

3. If the alarm persists, replace the standby EMS card.

Version: A 175
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.96 MANUAL_SWITCH
Meaning

The manual switch alarm. The alarm occurs when the manual switch alarm is
delivered in the ONTM2000.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The MANUAL_SWITCH alarm indicates that the OTNM2000 delivered the manual
switch command, which is generally used in test. Clear the switch command in a
timely manner after the test.

Possible cause

The manual switch command is delivered in the OTNM2000.

Handling procedure

1. Enter the OTNM2000 to check the MANUAL_SWITCH alarm and confirm the
information such as the NE or line that generates the alarm.

2. Enter the control command GUI of the alarmed card to check whether the
manual switch command is necessary. If not, clear the switch command.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

176 Version: A
 3 Alarm Handling

3.97 MCCABORT
Meaning

The MCC interruption alarm. The MCCABROT alarm occurs if the test interruption
command is delivered by the transparent frame window, or the MCC communication
between the local end and the far end is abnormal.

Alarm level

Prompt alarm

Relevant card

NMUJ1

Influence on the system

The service communication will be interrupted when this alarm is generated.

Possible cause

u The MCC test interruption command is delivered by the transparent frame

window.

u The line between the local end station and the far end station is faulty.

u The line card and the optical module of the local / far end are faulty.

Handling procedure

1. Check the MCCABROT alarm in the OTNM2000 to identify the NE or card that
generates this alarm.

2. Check whether the MCC test interruption command is delivered by the

transparent frame window. If yes, clear the corresponding test command.

3. If the alarm still exists, check whether the line optical fiber of the local and far
end meet the following requirements; if not, clean the optical fiber connector or
replace the optical fiber.

4 The bend radius of the optical fiber should be no less than 38mm.

4 The fiber connector is well-connected with the optical interface.

Version: A 177
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The optical fiber connector is clean.

4 The line attenuation of the optical cable meet the design requirement.

4. If the alarm persists, the line cards or the optical modules of the local end and
the opposite end is faulty. Replace the line card or the optical module.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.98 MCCCUTHROUGH
Meaning

The MCC pass-through alarm.

Alarm level

Prompt alarm

Relevant card

NMUJ1

Influence on the system

The MCC pass-through will cause a data transmission failure.

Possible cause

The MCC Rx path of the application layer is disabled manually.

3.99 MCCDISABLE
Meaning

The MCC shutdown alarm.

Alarm level

Prompt alarm

178 Version: A
 3 Alarm Handling

Relevant card

NMUJ1

Influence on the system

The MCC shutdown will cause a data transmission failure.

Possible cause

The MCC Rx path of the application layer is disabled manually.

3.100 MON1/2/3/4
Meaning

MON1/2/3/4: The external monitoring event alarm. The MON port is the monitoring
port for external events (such as temperature and alarms) and usually interconnects
with the user equipment to be monitored.

Alarm level

Critical alarm

Relevant card

NMUJ1

Influence on the system

The external event detected by the MON port will not influence the service directly,
but will influence the normal operation of the equipment. This alarm should be
handled in a timely manner.

Possible cause

The MON interface detects the external monitoring event.

Version: A 179
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Check the alarm through the OTNM2000 and isolate the card and the
monitoring terminal which generate the alarm.

2. Check the external monitoring event status corresponding to the MON interface.
If a change occurs, perform the corresponding handling to eliminate the fault.

3.101 MS_AIS
Meaning

The multiplex section alarm indication alarm. The alarm occurs when the frames
received by the local end, which with the K2 byte and the b6 to b8 of the K2 byte are
111, are more than three frames.

Alarm level

Minor alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

After the MS_AIS alarm is generated, the local end will transmit back the RDI signal
to the opposite end and the opposite end will generate the MS_RDI alarm.

Possible cause

u The service signal transmitted by the opposite end is the MS-AIS signal, i.e. all-
ones signal.

u The transmission at the opposite end is faulty.

u The receiving at the local end is faulty.

Handling procedure

1. Enter the OTNM2000 to check the MS_AIS alarm and confirm the information
such as the NE, card or line that generates the alarm.

180 Version: A
 3 Alarm Handling

2. Check whether the service signal transmitted by the far end is all-ones signal.

4 If yes, no handling is needed.

4 If not, ➔ Step 3.

3. Check whether the transmission of the remote equipment is normal.

4 If yes, ➔ Step 4.

4 If the transmission is faulty: handle the transmission fault of the opposite

end equipment, plugging and unplugging or replacing the corresponding
card on the opposite end (see CiTRANS 660 High-capacity MPLS-TP
Platform Routine Maintenance for operation procedures), and check
whether the alarm is removed. If the alarm persists, ➔ Step 4.

4. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

5. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

6. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.102 MS_BBE_LIMIT
Meaning

The background block error threshold-crossing alarm of the multiplex section. This
alarm occurs when the total number of B2 errored blocks in 15 minutes exceeds the
HP_BBE_LIMI threshold.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Version: A 181
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The performance of the alarmed line in the Rx direction of this station degrades
when the alarm occurs.

Possible cause

u The B1 error of the regenerator section causes the B2 error of the multiplex
section.

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the opposite end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Enter the OTNM2000 to check the MS_BBE_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the B1 error exists in the alarmed optical interface.

4 If yes, see RS_BBE_LIMIT for troubleshooting. If the alarm persists after

the B1 error is eliminated, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the Rx optical fiber of the alarmed optical interface is within the
normal range.

182 Version: A
 3 Alarm Handling

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling.

4 If the optical fiber power is within the normal range, ➔ Step 4.

4. Perform the loopback on the optical interface on the opposite end line side
(users can use the optical attenuator during the optical fiber loopback to ensure
the Rx optical power is within the normal range) and check whether the newly
added B2 error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 Newly added error exists: the previous station may be faulty. Isolate the
previous station and the specified faulty point that generates the alarm
according to the service direction using loopback, and eliminate the fault
by plugging and unplugging or replacing the optical card and the clock and
cross-connect card.

5. Replace the card. If the alarm persists, ➔ Step 6.

6. Check whether the laser temperature and the equipment temperature is normal.
If the temperature is normal but the alarm persists, ➔ Step 7.

7. Check whether the equipment is well-grounded, whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the temperature is normal but the alarm persists, ➔ Step 8.

8. Please contact FiberHome after-sales maintenance engineer.

3.103 MS_ES_LIMIT
Meaning

The errored second threshold-crossing alarm of the multiplex section. This alarm
occurs when the total number of B2 errored seconds in 15 minutes exceeds the
MS_ES_LIMIT threshold set in the OTNM2000.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Version: A 183
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station degrades.

Possible cause

u The B1 error of the regenerator section causes the B2 error of the multiplex
section.

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the opposite end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Enter the OTNM2000 to check the MS_ES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the B1 error exists in the alarmed optical fiber.

4 If yes, see RS_BBE_LIMIT for troubleshooting. If the alarm persists after

the B1 error is eliminated, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the Rx optical fiber of the alarmed optical interface is within the
normal range.

184 Version: A
 3 Alarm Handling

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling.

4 If the optical fiber power is within the normal range, ➔ Step 4.

4. Perform the loopback on the optical interface on the opposite end at the line
side (users can use the optical attenuator during the optical fiber loopback to
ensure the Rx optical power is within the normal range) and check whether the
newly added B2 error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 Newly added error exists: the previous station may be faulty. Isolate the
previous station and the specified faulty point that generates the alarm
according to the service direction using loopback, and eliminate the fault
by plugging and unplugging or replacing the optical card and the clock and
cross-connect card.

5. Replace the card. If the alarm persists, ➔ Step 6.

6. Check whether the laser temperature and the equipment temperature are
normal. If the temperature is normal but the alarm persists, ➔ Step 7.

7. Check whether the equipment is well-grounded, and whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the temperature is normal but the alarm persists, ➔ Step 8.

8. Please contact FiberHome after-sales maintenance engineer.

3.104 MS_EXC
Meaning

The bit error ratio threshold-crossing alarm of the multiplex section. The alarm
occurs when the bit error ratio detected by B2 exceeds the threshold value.

Alarm level

Critical alarm

Relevant card

S1O1, S1J4

Version: A 185
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The bit error of the alarmed multiplex section is excessive and the service quality
degrades.

Possible cause

u The card temperature is over high and the TEMP_TCT alarm exists.

u Physical connection faults, such as broken pigtail fiber, too small bend radius of
the pigtail fiber, unclean optical interface, poor contact of the optical fiber
connector.

u The attenuation of the received signal is over-high.

u The attenuation value of the attenuator is over-high or over-low.

u The transmission at the opposite end is faulty.

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the MS_EXC alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the alarms like RS_EXC, HP_SD exist on the local end.

4 If yes, process alarms such as RS_EXC, HP_SD first. If the alarm still
exists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the temperature of the alarmed card is over-high and whether
the TEMP_TCT alarm exists.

4 If yes, handle the TEMP_TCT alarm first and lower the ambient
temperature and equipment working temperature. If the alarm persists, ➔
Step 4.

4 If not, ➔ Step 4.

4. Check whether the Rx optical power of the alarmed card is normal. If the Rx
optical power is normal, ➔ Step 5; if not, operate as below.

1) Secure the optical fiber connector to see whether the alarm is removed.

186 Version: A
 3 Alarm Handling

2) If the alarm persists, check whether the optical attenuator exists and
whether the attenuation value is appropriate. If not, adjust the attenuation
value to see whether the alarm is removed.

3) If the alarm persists, clean the fiber connector and the receiving optical
interface at the local end to see whether the alarm is removed.

4) If the alarm persists, check whether the ring flange and the optical
attenuator at the local station is correctly connected. Connect the ring
flange and the optical attenuator correctly to see whether the alarm is
removed.

5. Check whether the Tx optical power is normal at the opposite end station. If the
Tx optical power is normal, clean the fiber connector at the opposite end station
to see whether the alarm is removed. If not, operate as below.

1) Replace the optical module or the card on the opposite end station to see
whether the alarm is removed.

2) If the alarm persists, check whether the ring flange and the optical
attenuator of the far end station are correctly connected, and whether the
attenuation value is over-high. Connect the ring flange and the optical
attenuator correctly to see whether the alarm is removed.

6. If the alarm persists, check whether the optical cable is faulty. If yes, handle the
fault to see whether the alarm is removed.

7. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

8. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

Version: A 187
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.105 MS_RDI
Meaning

The remote defect indication alarm of the multiplex section. The alarm occurs when
the opposite end sends back the multiplex section remote defect indication (MS-RDI)
signal to the local end after detecting the MS-AIS signal.

Alarm level

Minor alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

A fault exists in the transmitting equipment of the local end or the receiving
equipment at the far end when the MS_RDI alarm occurs.

Possible cause

u The receiving equipment at the far end is faulty.

u The transmitting equipment of the local end is faulty.

Handling procedure

1. Enter the OTNM2000 to check the MS_RDI alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the receiving of the opposite end equipment is normal.

4 If the receiving of the opposite end equipment is normal, ➔ Step 3.

4 If the transmission is faulty: handle the transmission fault of the opposite

end equipment first, and then plug and unplug or replace the
corresponding card on the opposite end (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures), and
check whether the alarm is removed. If the alarm persists, ➔ Step 3.

3. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

188 Version: A
 3 Alarm Handling

4. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

5. Wait a few minutes. If the alarm still exists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.106 MS_SD
Meaning

The multiplex section signal degradation alarm. This alarm occurs when the bit error
ratio of the tested equipment exceeds the threshold.

Alarm level

Minor alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Influence on the system

If this alarm occurs, the performance of the alarmed line in the Rx direction of this
station degrades or the service will be interrupted.

Possible cause

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the far end is faulty.

u The synchronization performance of the system clock degrades.

Version: A 189
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Use the optical power meter to check whether the optical power is normal.

4 If yes, ➔ Step 2.

4 If not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for handling

the alarm.

2. If the alarm persists, check and eliminate the optical fiber fault.

3. If the alarm persists, clean the optical connector.

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.107 MS_SES_LIMIT
Meaning

The severely errored second threshold-crossing alarm of the multiplex section. The
severely errored second refers to a one-second period that contains over 30%
errored blocks or at least one severely disturbed period. This alarm occurs when the
total number of multiplex section severely errored seconds in 15 minutes exceeds
the MS_SES_LIMIT threshold.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J1, S1J4, XSJ2, XSJ3, XGJ1

190 Version: A
 3 Alarm Handling

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station degrades.

Possible cause

u The B1 error of the regenerator section causes the B2 error of the multiplex
section.

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the opposite end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Enter the OTNM2000 to check the MS_SES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the other error alarms exist in the alarmed optical fiber.

4 If yes, see RS_BBE_LIMIT and MS_AIS for troubleshooting. If the alarm

persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the Rx optical fiber of the alarmed optical interface is within the
normal range.

Version: A 191
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling.

4 If the optical fiber power is within the normal range, ➔ Step 4.

4. Perform the loopback on the optical interface on the opposite end at the line
side (users can use the optical attenuator during the optical fiber loopback to
ensure the Rx optical power is within the normal range) and check whether the
newly added B2 error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 5.

4 If yes: the previous station may be faulty. Eliminate the fault of the previous
station. If the alarm persists, ➔ Step 5.

5. Replace the card at the local end station. If the alarm persists, ➔ Step 6.

6. Check whether the laser temperature and the equipment temperature are
normal. If the temperature is normal but the alarm persists, ➔ Step 7.

7. Check whether the equipment is well-grounded, and whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the temperature is normal but the alarm persists, ➔ Step 8.

8. Please contact FiberHome after-sales maintenance engineer.

3.108 OOCR
Meaning

The alarm of the lock synchronization reference source frequency exceeding the
lock range. The alarm occurs when the detected lock synchronization reference
source frequency exceeds the lock range.

Alarm level

Critical alarm

Relevant card

XCUJ2, XCUJ4

192 Version: A
 3 Alarm Handling

Influence on the system

Lock synchronization reference source frequency exceeding the lock range may
cause the loss of the synchronization reference source, and the clock and cross-
connect card enters the holdover status from the locked mode. After the equipment
operates under this status for long term, the packet loss and bit errors will occur.
This will seriously influence the service normal operation.

Possible cause

u The lock synchronization reference source frequency exceeds the lock range.

u The clock module of the card is faulty.

Handling method

1. Enter the OTNM2000 to check the OOCR alarm and confirm the NE that
generates the alarm.

2. Check whether the alarms such as LTI exist on the local end.

4 If yes, handle the LTI alarm first and configure the relevant parameters of
the external synchronization reference source in the OTNM2000 correctly.
If the alarm persists, go to Step 3.

4 If not, ➔ Step 3.

3. Check whether the external synchronization reference source of the alarmed

clock and cross-connect card is normal.

4 If yes, ➔ Step 4.

4 If not, replace the external synchronization reference source or adjust the

frequency of the external synchronization reference source. If the alarm
persists, ➔ Step 4.

4. Replace the alarmed card with an identical spare one (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

5. If the OOCR alarm persists, please contact FiberHome after-sales

maintenance engineer.

Version: A 193
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.109 OTRX_ABSENT
Meaning

The optical module not present alarm. This alarm occurs when the card detects that
the optical module is not present.

Alarm level

Critical alarm

Relevant card

S1O1, S1J4

Influence on the system

The services carried by the alarmed interface will be interrupted.

Possible cause

u The optical module is not present or is not inserted into the right slot.

u The optical module is faulty.

u The alarmed card is faulty.

Handling method

1. Check the OTRX_ABSENT alarm in the OTNM2000 to identify the NE or card

that generates this alarm.

2. Check whether the optical module of the optical interface is present. If the
pluggable SFP and XFP optical modules are not present or not in the right slots,
re-install the optical module (see CiTRANS 660 High-capacity MPLS-TP
Platform Routine Maintenance for operation procedures).

3. If the alarm persists and the optical module is pluggable, replace the optical
module (see CiTRANS 660 High-capacity MPLS-TP Platform Routine
Maintenance for operation procedures).

4. If the alarm persists, the card is faulty. Replace the alarmed card (see
CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance for
operation procedures).

194 Version: A
 3 Alarm Handling

3.110 PK_LOS
Meaning

The packet loss threshold-crossing alarm. This alarm occurs when the frame loss
exceeds the threshold set in the OTNM2000 continuously in a certain period.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, XSJ2, XSJ3

Influence on the system

This alarm may cause service interruption.

Possible cause

The link signals are of poor quality or contain a significant amount of illegal data,
causing that the number of lost packet actually received exceeds the packet loss
threshold set in the card configuration GUI.

Handling method

1. Check the link signal quality. Replace the optical fiber and the network cable,
and clean the optical module.

2. Check whether the temperature of the alarmed card is over-high and whether
the CARD_TCT alarm exists. If yes, handle the CARD_TCT alarm first and
lower the ambient temperature and the equipment working temperature.

3. If the alarm persists, check whether the DOS attack exists; if yes, clear the
illegal data source.

4. If the alarm persists, check whether the loop occurs in the network; if yes,
modify the relevant configuration to eliminate the loop.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 195
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.111 PORT_MIRROR
Meaning

The port mirroring alarm.

Note:

The port mirroring function indicates that the equipment copies the data
frame transmitted or received by a interface to another port. The copied
port is called the mirroring source port and the copying port is the
destination port. Connect a protocol analyzer (such as Sniffer) or a
RMON monitor to the destination port to monitor and manage the network,
and to diagnose the network fault.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The services carried in the destination port will be interrupted.

Possible cause

The port mirroring is configured in the control command tab for test or maintenance.

Handling method

Check whether the port mirroring is configured in the control command tab for test or
maintenance. After the test or maintenance is completed, users should set the port
mirroring function to disable in the card control command.

196 Version: A
 3 Alarm Handling

3.112 POWERALM
Meaning

The power fault alarm. This alarm occurs when the internal module voltage
(including 5V, 3.3V, 1.8V, 1.2V and standby 5V power, etc.) in the card exceeds the
allowed range.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, S1J4, GSJ3, XSJ3, S1O1, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J1, S1J2,
E1J1, E1J2

Influence on the system

The abnormal voltage in the card may cause the abnormal operation of the chip, the
failure of the card function, and cause tremendous potential silent failures to the
normal operation of the system.

Possible cause

The alarmed card is faulty.

Handling method

1. Check the POWERALM alarm in the OTNM2000 and identify the alarmed NE /
card and its slot.

2. Replace the alarmed card with an identical spare one. Wait a few minutes, if the
alarm persists after starting the card normally, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.113 PPI_LOS
Meaning

The signal loss alarm of the PDH physical interface.

Version: A 197
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Critical alarm

Relevant card

E1J1, E1J2

Influence on the system

Possible cause

u The service of the equipment port is not accessed.

u The equipment loopback command is delivered to the card.

u The output port at the DFF side interface is unconnected or loosen.

u The input port of the local PDH interface is unconnected or loosen.

u The cable is faulty.

u The switch card is reset.

u The alarmed card is faulty.

Processing procedure

1. Check the PPI_LOS alarm in the OTNM2000 and identify the alarmed NE /
card and its slot.

2. Check whether the service signal is accessed to the equipment port and
ensure the service signal is accessed to the correct equipment port.

3. If the alarm persists, access the alarmed card status GUI in the OTNM2000 to
check whether the equipment loopback is configured.

4 If yes: access the control command GUI of the alarmed card to clear the
equipment loopback, and re-deliver the configuration to the equipment.

4 If the equipment loopback is not configured, ➔ Step 4.

4. If the alarm persists, check whether the output port of the DDF and the PDH
input port of the equipment is well-connected; if not, re-connect them.

5. If the alarm persists, the cable between the DDF and the equipment or between
the DDF and the switch may be faulty. Isolate the faulty cable by the DDF
loopback and replace the cable.

198 Version: A
 3 Alarm Handling

6. Replace the alarmed card with an identical spare one (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.114 PPS_ALM
Meaning

The PPS abnormal alarm. The alarm occurs when the PPS status is not available
detected by the TOD frame.

Alarm level

Critical alarm

Relevant card

XCUJ2

Influence on the system

The time source is switched and the time synchronization is unstable.

Possible cause

u The clock configuration is incorrect.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

Handling method

1. Check whether the clock configuration on the local end and the adjacent
equipment is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the alarm persists after the
above operation, ➔ Step 3.

Version: A 199
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 3.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the alarm persists after the above operation, ➔ Step 3.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.115 PTP_ALM
Meaning

The abnormal time synchronization alarm indicates an abnormality of PTP time

synchronization occurs.

Alarm level

Minor alarm

Relevant card

GSJ2, XCUJ2, ESJ1, XSJ2

Influence on the system

The time synchronization stability will be influenced.

Possible cause

u When the PPS+TOD port is in the output status, the node frequency is not
locked or locked to the incorrect reference source.

u The alarmed card is faulty.

Handling method

1. Check the alarm through the OTNM2000 to identify the card that generates the
alarm.

200 Version: A
 3 Alarm Handling

2. If the alarm persists, check the lock status of the alarmed node frequency,
ensuring the time and the frequency are locked to the same time reference
source.

3. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

3.116 PTP_CLK_ALM
Meaning

Synchronous clock abnormal alarm.

Alarm level

Major alarm

Relevant card

GSJ2, ESJ1, XSJ2

Influence on the system

The clock synchronization stability will be influenced.

Possible cause

u When the port of the line direction is in the SLAVE status, the node frequency is
not locked or locked to the incorrect reference source.

u The alarmed card is faulty.

Handling method

1. Check the alarm through the OTNM2000 to identify the card that generates the
alarm.

2. Check the external PTP synchronization reference source status.

3. If the alarm persists, check the lock status of the alarmed node frequency,
ensuring the time and the frequency are locked to the same time reference
source.

Version: A 201
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

3.117 PTP_LOS
Meaning

The accurate time synchronization loss alarm. The alarm occurs in the peer port
when the port is configured with the PTP clock and fails to receive the PTP clock
signal.

Alarm level

Critical alarm

Relevant card

XGJ1, XCUJ2, ESJ1, ESJ2, XSJ2, XSJ3

Influence on the system

This alarm indicates that the system precision time synchronization signal is lost.

Possible cause

u The link signal is interrupted.

u The PTP port has a wrong configuration, for example, the Master and Slave
setting of the local port mismatch with that of the interconnected port.

u One side of the PTP ports is not open.

u A hardware fault of the local end station or the opposite end station exists, such
as the line interface card or the alarmed card fault.

Handling procedure

1. Check the alarm through the OTNM2000 and identify the port that generates
this alarm.

2. Check whether the RLOS alarm appears in the line interface card. If yes, see
the alarm handling.

202 Version: A
 3 Alarm Handling

3. Check whether PTP functions of both the port and its interconnected port are
open. If not, modify the setting.

4. If the alarm persists, check whether the PTP operation mode of the port and its
interconnected port has a right setting. The right setting should be that the
Master matches with the Slave. If the setting is not correct, modify it.

5. If the alarm persists, replace the line interface card of the opposite end station
(see CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance) to
check whether the alarm disappears.

6. If the alarm persists, replace the line interface card of the local end station (see
CiTRANS 660 High-capacity MPLS-TP Platform Routine Maintenance) to
check whether the alarm disappears.

7. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance) to check whether the alarm
disappears.

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.118 PTP_TEST
Meaning

The time synchronization test mode alarm.

Alarm level

Prompt alarm

Relevant card

GSJ2, XCUJ2, ESJ1, XSJ2

Influence on the system

No

Possible cause

The system is progressing a time synchronization test.

Version: A 203
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling method

No handling is needed.

3.119 RCONTEXT_ACCESS_FAIL
Meaning

The remote link access failure alarm. This alarm will be reported when the opposite
end of the E1 link is faulty and the PPI_LOS and E1_AIS alarms occur.

Alarm level

Minor alarm

Relevant card

S1O1, S1J4, E1J1

Influence on the system

The service of the alarmed link will be interrupted.

Possible cause

u The E1 link configuration on the opposite end is incorrect.

u The line interface of the opposite end is abnormal and the service connected
with the opposite end equipment is abnormal.

Handling method

1. Enter the OTNM2000 to check the RCONTEXT_ACCESS_FAIL alarm and

confirm the NE that generates the alarm.

2. Check the configuration of the alarmed line's E1 link at the opposite end. If the
alarm persists after the verification, ➔ Step 3.

3. Check whether the physical fault exists in the line port of the opposite end
equipment, and whether any alarms exist in the E1 service connected to the
opposite end equipment. If the alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

204 Version: A
 3 Alarm Handling

3.120 RCONTEXT_PACKET_LOS
Meaning

The remote link packet loss alarm. The alarm occurs when the emulation link
detects the packet loss.

Alarm level

Minor alarm

Relevant card

S1O1, S1J4, E1J1, E1J2

Influence on the system

The link generating the RCONTEXT_PACKET_LOS alarm has the packet loss, and
the service is unstable. In general, the RCONTEXT_PACKET_LOS alarm and the
CONTEXT_PACKET_LOS alarm will occur simultaneously in the same link.

Possible cause

u The local end transmission equipment is faulty.

u The configuration data is incorrect.

u The recovered clock locking status is poor.

u The card buffering works abnormally.

u The alarmed card is faulty.

Handling method

1. Enter the OTNM2000 to check the RCONTEXT_PACKET_LOS alarm and

confirm the information such as the NE, card or line that generates the alarm.

2. Check whether the transmitting of the local end at the line side works normally.

4 If yes, ➔ Step 3.

4 If not, eliminate the transmission fault of the local end at the line side. If the
alarm persists, ➔ Step 3.

Version: A 205
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Check whether the configuration data of the local end and the opposite end are
correct.

4 If yes, ➔ Step 4.

4 If not, re-configure the cross-connect data according to the actual project

situation. If the alarm persists, ➔ Step 4.

4. Check whether the number of packets in the buffer is normal by the status
monitoring.

4 If yes, ➔ Step 5.

4 If not, modify the number of buffered packets in the card configuration. If

the alarm persists, ➔ Step 5.

5. Check whether the clock locking status of the local end and the far end is
normal.

4 If yes, ➔ Step 6.

4 If not, eliminate the clock locking fault. If the alarm persists, ➔ Step 6.

6. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

8. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.121 REF_CHANGE
Meaning

Clock reference source change alarm. This alarm occurs when the current lock
synchronization reference source switches.

Alarm level

Prompt alarm

206 Version: A
 3 Alarm Handling

Relevant card

XCUJ2, XCUJ4

Influence on the system

The current synchronization reference source will be switched, which does not
influence the services.

Possible cause

u Deliver the forced switch command in the OTNM2000.

u The current synchronization reference source is abnormal, causing the

synchronization reference source switch.

Handling procedure

1. Enter the OTNM2000 to check the REF_SWITCH alarm and confirm the NE
that generates the alarm.

2. Check whether the forced switch clock reference source command is delivered
to the alarmed clock and cross-connect card before the REF_SWITCH occurs
via the View Command Log in the OTNM2000.

4 If yes, deliver the CLR command in the Control Command in the alarmed
clock and cross-connect card. If the REF_SWITCH alarm persists, ➔ Step
3.

4 If not, ➔ Step 3.

3. Eliminate the original synchronization reference source fault. If the

REF_SWITCH alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.122 RLOS
Meaning

The input optical signal loss alarm indicates that the optical module detects no
optical input and the receiving signal is lost.

Version: A 207
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, GSJ3, ESJ2, XSJ2, XSJ3

Influence on the system

u This alarm will cause the service interruption and insert the AIS signal to the
succeeding station.

u After the alarm is generated, the system will transmit the MS_RDI back to the
previous station, which will generate the MS_RDI alarm.

Possible cause

u The optical fiber is broken or no optical fiber is connected.

u The laser is disabled.

u The line attenuation is excessive.

u The receiving equipment of the local end is faulty.

u The transmitting equipment of the opposite end is faulty.

Handling method

1. Enter the OTNM2000 to check the RLOS alarm and confirm the information
such as the NE or line that generates the alarm.

2. When the line attenuation is excessive or the optical fiber is broken, replace the
optical fiber to see whether the alarm is removed.

3. If the alarm persists, check whether the optical interface is normally connected.

4 If not, check the laser of the relevant port at the local end and make sure
the laser is set to Enable.

4 If yes, ➔ Step 4.

4. If the alarm persists, query the Tx optical power of the opposite end.

4 If not, replace the opposite end card and check whether the alarm is
removed.

208 Version: A
 3 Alarm Handling

4 If yes, ➔ Step 5.

5. If the alarm persists, check whether the alarmed card at the local end is faulty.

4 If yes, replace the alarmed card and check whether the alarm is removed.

4 If the local end alarmed card is normal, ➔ Step 6.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.123 RPJE_LIMIT
Meaning

Pointer adjustment threshold-crossing alarm.

Alarm level

Prompt alarm

Relevant card

S1J1

Influence on the system

The service may be interrupted in the alarmed channel when the alarm occurs.

Possible cause

u The optical fiber connector is contaminated or is in poor connection.

u The optical module is faulty.

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the RPJE_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Clear the NE's performance and observe for 15 minutes to check whether the
alarm appears.

Version: A 209
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Note:

Clear the NE performance: In the OTNM2000 window, right-click the NE

in the Logical Tree and select Clear NE Performance from the shortcut
menu, and select Yes in the Clear NE Performance window that
appears subsequently to clear the performance of the NE.

3. If the alarm persists, clear the optical fiber connector and make sure that the
optical fiber connector is firmly connected.

4. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

5. If the alarm persists, plug and unplug the alarmed card (see Plugging and
Unplugging Cards for operation procedures).

6. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance).

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.124 RS_BBE_LIMIT
Meaning

The background block error threshold-crossing alarm of the regenerator section.

The alarm occurs when the system detects that the background block error of the
regenerator section for the 10GE port exceeds the pre-set threshold value.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Influence on the system

This alarm will influence the service quality and cause the service unstable.

210 Version: A
 3 Alarm Handling

Possible cause

u The RS_BEE_LIMIT threshold is set over-low.

u The optical fiber is incorrectly connected.

u The laser of the card is faulty.

u The card is faulty.

Handling method

1. Enter the OTNM2000 to check the REF_SWITCH alarm and confirm the NE
that generates the alarm.

2. When the excessive line attenuation causes the Rx optical power in the critical
state, replace the optical fiber and check the BBE_RS current performance.

3. If the count of the BBE_RS performance still increases, replace the optical
module at two ends of the link and check the BBE_RS current performance.

4. If the count of the BBE_RS performance still increases, replace the card at two
ends of the link and check the BBE_RS current performance.

5. If the performance count still increases, please contact FiberHome after-sales

maintenance engineer.

3.125 RS_ES_LIMIT
Meaning

The errored second threshold-crossing alarm of the regenerator section. This alarm
occurs when the total number of B1 errored seconds in 15 minutes exceeds the
RS_ES_LIMIT threshold.

Alarm level

Prompt alarm

Relevant card

S1O1, S1J1, S1J4, XSJ2, XSJ3

Version: A 211
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station will be degraded.

Possible cause

u The input optical power is over-low or over-high

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of parameters such as the chromatic dispersion of the

optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the opposite end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling method

1. Enter the OTNM2000 to check the RS_ES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the Rx optical power of the alarmed optical interface is within
the normal range.

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling.

4 If optical fiber power is within the normal range, ➔ Step 3.

3. Perform the loopback on the optical interface on the far end line side (users can
use the optical attenuator during the optical fiber loopback to ensure th Rx
optical power is within the normal range) and check whether the newly added
error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 4.

212 Version: A
 3 Alarm Handling

4 If yes: the far end card may be faulty. Check whether the far end card
works normally. If the card on the far end works normally, check whether
the specifications are normal, such as optical fiber dispersion. If the alarm
persists even though the card and optical fiber on the opposite end are
normal, ➔ Step 4.

4. Check whether the laser working temperature and the equipment working
temperature are normal in the performance GUI of the OTNM2000.

4 If not, improve the ambient temperature. If the alarm persists, ➔ Step 5.

4 If yes, ➔ Step 5.

5. Replace the card. If the alarm persists, ➔ Step 6.

6. Check whether the equipment is well-grounded, whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the temperature is normal but the alarm persists, ➔ Step 7.

7. Please contact FiberHome after-sales maintenance engineer.

3.126 RS_EXC./RS_EXC
Meaning

The bit error ratio threshold-crossing alarm of the regenerator section. The alarm
occurs when the bit error ratio of the regenerator section exceeds the alarm
threshold set in the OTNM2000.

Alarm level

Critical alarm

Relevant card

u RS_EXC.: S1J1, XSJ2, XSJ3

u RS_EXC: S1O1, S1J4

Influence on the system

This alarm indicates the quality degradation of the transmission service.

Version: A 213
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The higher-level alarms such as RLOS and MS_EXC exist.

u The card temperature is over high and the TEMP_TCT alarm exists.

u The far end is faulty.

u Physical connection fault, such as broken pigtail, too small pigtail bend radius
of the pigtail fiber, poor contact of the ring flange and unclean optical interface.

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the RS_EXC alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the higher level alarms like RLOS and MS_EXC exist on the
local end.

4 If yes, remove the higher-level alarms such as RLOS and MS_EXC first. If
the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the TEMP_TCT alarm exists in the alarmed card.

4 If yes, process the TEMP_TCT alarm first. If the alarm persists, ➔ Step 4.

4 If not, ➔ Step 4.

4. Check whether the transmission at the far end is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the fault of the opposite end first. If the alarm persists, ➔
Step 5.

5. Check whether the pigtail connection of the local alarmed card is normal. Make
sure that the situation such as broken pigtail, too small pigtail bend radius, poor
contact of the ring flange and unclean optical interface does not exist.

4 If not, eliminate the physical connection fault first. If the alarm persists, ➔
Step 6.

4 If yes, ➔ Step 6.

6. Plug and unplug the alarmed card (see Plugging and Unplugging Cards for
operation procedures).

214 Version: A
 3 Alarm Handling

7. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

8. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.127 RX_LOC
Meaning

The receive signal loss alarm. The alarm is reported when the receive signals lose.

Alarm level

Critical alarm

Relevant card

XSJ2

Influence on the system

The service will be influenced when the signal loss is detected.

Possible cause

The line is incorrectly connected or configured.

Handling method

1. Enter the OTNM2000 to check the RX_LOC alarm and confirm the information
such as the NE or the line that generates the alarm.

2. Check whether the line is incorrectly connected; if yes, reconnect the optical
fiber or reconfigure the line to see whether the alarm is removed.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 215
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.128 RS_LOF
Meaning

The regenerator section frame loss alarm. The alarm occurs when the local end
receives the RS_OOF for 3m continuously.

Alarm level

Critical alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Influence on the system

After the RS_LOF alarm is generated, the service will be interrupted and the AIS
signal will be inserted to the succeeding station. The local end will transmit back the
RDI signal to the far end.

Possible cause

u The line card transmission at the far end is faulty.

u The Rx direction of the local end is faulty.

u The transmission cable is damaged so that the increased optical attenuation

causes the signal degradation.

u The optical receiver at the local end is faulty.

Handling method

1. Enter the OTNM2000 to check the RS_LOF alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the Tx direction of the line card at the opposite end fails. For
example: whether the optical transmitter works normally, and whether the
optical fiber is correctly connected.

4 If the transmission at the opposite end fails, eliminate the far end fault first.
If the alarm persists after the operation, ➔ Step 3.

216 Version: A
 3 Alarm Handling

4 If the transmission at the opposite end is normal, ➔ Step 3.

3. Check whether the lines and cables are faulty.

4 If yes, clear the fault of lines and cables. If the alarm persists after the
operation, ➔ Step 4.

4 If not, ➔ Step 4.

4. If the alarm persists, replace the optical module of the alarmed line with an
identical spare one. If the alarm persists, ➔ Step 5.

5. Check whether the clock and cross-connect card at the local and opposite ends
are faulty. Replace the alarmed clock and cross-connect card. If the alarm
persists, ➔ Step 6.

6. Please contact FiberHome after-sales maintenance engineer.

3.129 RS_OOF
Meaning

The regenerator section out-of-frame alarm. This alarm will be reported if the
equipment detects that the frame alignment bytes (A1 and A2) do not match.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

After the RS_OOF alarm is generated, the service will be interrupted and the AIS
signal will be inserted to the succeeding equipment. The local end will transmit back
the RDI signal to the far end.

Possible cause

u The transmission of the line card at the far end is faulty.

u The Rx direction of the local end is faulty.

Version: A 217
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u The transmission cable is damaged so that the increased optical attenuation

causes the signal degradation.

u The optical receiver at the local end is faulty.

Handling procedure

1. Enter the OTNM2000 to check the RS_OOF alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether the transmission of the line card at the far end fails. For
example: whether the optical transmitter works normally, and whether the
optical fiber is correctly connected.

4 If the transmission of the opposite end fails, eliminate the far end fault first.
If the alarm persists, ➔ Step 3.

4 If yes, ➔ Step 3.

3. Check whether the lines and cables are faulty.

4 If yes, clear the fault of lines and cables. If the alarm persists, ➔ Step 4.

4 If not, ➔ Step 4.

4. If the alarm persists, replace the optical module of the alarmed line with an
identical spare one. If the alarm persists, ➔ Step 5.

5. Check whether the clock and cross-connect card at the local and opposite ends
are faulty. Replace the alarmed clock and cross-connect card. If the alarm
persists after the above operation, ➔ Step 6.

6. Please contact FiberHome after-sales maintenance engineer.

3.130 RS_SD
Meaning

The regenerator section signal degradation alarm. This alarm occurs when the bit
error ratio of the tested equipment exceeds the threshold.

Alarm level

Critical alarm

218 Version: A
 3 Alarm Handling

Relevant card

S1O1, S1J4

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station degrades or the service will be interrupted.

Possible cause

u The input optical power is over-low or over-high.

u The card on the local end or the far end is faulty.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

Handling method

1. Check the RS_SD alarm in the OTNM2000 to identify the information such as
NE and card that generates the alarm.

2. Use the optical power meter to check whether the optical power is normal.

4 If yes, ➔ Step 3.

4 If not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for handling

the alarm.

3. If the alarm persists, clean the optical interface.

4. If the alarm persists, check and eliminate the optical fiber fault.

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 219
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.131 RS_SES_LIMIT
Meaning

The severely errored second threshold-crossing alarm of the regeneration section.

The severely errored second refers to a one-second period that contains over 30%
errored blocks or at least one severely disturbed period. This alarm occurs when the
total number of the regenerator section severely errored seconds in 15 minutes
exceeds the RS_SES_LIMIT threshold pre-set in the ONTM2000.

Alarm level

Prompt alarm

Relevant card

XGJ1, S1O1, S1J1, S1J4, XSJ2, XSJ3

Influence on the system

If this alarm is generated, the performance of the alarmed line in the Rx direction of
this station degrades.

Possible cause

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the the non-linear effect of the long-distance
transmission.

u The card on the local end or the far end is faulty.

u The synchronization performance of the system clock degardes.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

220 Version: A
 3 Alarm Handling

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Enter the OTNM2000 to check the RS_SES_LIMIT alarm and confirm the
information such as the NE or line that generates the alarm.

2. Check whether the Rx optical fiber of the alarmed optical interface is within the
normal range.

4 If it is beyond the normal range, see IOP_LOW/IOP_LOW. and IOP_HIGH/

IOPM_HIGH. for alarm handling.

4 If optical fiber power is within the normal range, ➔ Step 3.

3. Perform the loopback on the optical interface of the far end at the line side
(users can use the optical attenuator during the optical fiber loopback to ensure
the Rx optical power is within the normal range) and check whether the newly
added error exists in the current performance.

4 If not: the equipment on the local end is faulty, ➔ Step 4.

4 If yes, the card at the far end fails and check whether the card and the
optical fiber at the far end are normal.

u If yes, the alarm persists, ➔ Step 8.

u If not, replace the card or optical fiber (CiTRANS 660 High-capacity

MPLS-TP Platform Routine Maintenance). If the alarm persists, ➔
Step 6.

4. Check whether the laser working temperature and the equipment working
temperature are normal in the performance GUI of the OTNM2000.

4 If not: improve the ambient temperature or replace the optical module. If

the alarm persists, ➔ Step 5.

4 If yes, ➔ Step 5.

5. Replace the card. If the alarm persists, ➔ Step 6.

6. Check whether the equipment is well-grounded, whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the power supply is normal but the alarm persists, ➔ Step 7.

Version: A 221
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

7. Check the whether the specifications are normal, such as optical fiber
dispersion. If the alarm persists even though the card and optical fiber on the
far end are normal, ➔ Step 8.

8. In the application of the long-haul transmission, the high-speed line above

2.5Gbit/s should use the Tx optical module of the high chromatic dispersion
tolerance. If the alarm persists after using the Tx optical module of the high
chromatic dispersion tolerance, ➔ Step 9.

9. Please contact FiberHome after-sales maintenance engineer.

3.132 RS_SF
Meaning

Regenerator section signal failure alarm. This alarm occurs when the actually
received trace byte (J0) of the regenerator section does not match the expected
value.

Alarm level

Critical alarm

Relevant card

XSJ2

Influence on the system

The services carried by the alarmed port will be interrupted.

Possible cause

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
+55℃) or the humidity is higher than 90%.

222 Version: A
 3 Alarm Handling

u The terrible degradation of the parameters such as the chromatic dispersion of

the optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the far end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Check the RS_SF alarm in the OTNM2000 to identify the information such as
NE and card that generates the alarm.

2. Check and eliminate the faults of the optical fiber and the active connector. If
the alarm persists, ➔ Step 3.

3. Replace the faulty card at the far end equipment. If the alarm persists, ➔ Step
4.

4. Replace the faulty card at the local end equipment. If the alarm persists, ➔
Step 5.

5. Please contact FiberHome after-sales maintenance engineer.

3.133 RS_TIM
Meaning

The trace identifier mismatch alarm of the regenerator section. This alarm occurs
when the actually received trace byte (J0) of the regenerator section does not match
the expected value.

Alarm level

Critical alarm

Relevant card

XGJ1, S1O1, S1J1, S1J2, S1J4, XSJ2, XSJ3

Version: A 223
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

This alarm will not influence the service.

Possible cause

u The expected received J0 byte of the local end is inconsistent with the J0 byte
transmitted by the far end.

u The optical fiber is incorrectly connected.

Handling procedure

1. Enter the OTNM2000 to check the RS_TIM alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the expected received J0 byte of the local end card is
consistent with the J0 byte transmitted by the far end card. If not, check
whether the alarm is removed after the modification according to the actual
condition.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.134 RS_TIU./RS_TIU
Meaning

The trace identifier unstable alarm of the regenerator section. This alarm occurs
when the J0 data can not be received stably.

Alarm level

Critical alarm

u RS_TIU.: major alarm

u RS_TIU: critical alarm

Relevant card

u RS_TIU.: S1J1

u RS_TIU: S1O1, S1J4

224 Version: A
 3 Alarm Handling

Influence on the system

This alarm will degrade the performance of the alarmed line, and influence the
protection switch function of the ASON control platform.

Possible cause

u The B1 error exists in the line, causing the J0 receiving fault.

u The input optical power is over-low or over-high.

u The DC power voltage is unstable or exceeds the normal voltage range (-40V
to -57V).

u The temperature in the equipment room exceeds the normal range (-30℃ to
55℃) or the humidity is higher than 90%.

u The terrible degradation of parameters such as the chromatic dispersion of the

optical fiber line caused by the non-linear effect of the long-distance
transmission.

u The card on the local end or the far end is faulty.

u The synchronization performance of the system clock degrades.

u The pigtail fiber is contaminated, degraded, over-bent or pressed.

u The interference source exists in the equipment room or the equipment is not
well-grounded.

Handling procedure

1. Enter the OTNM2000 to check the RS_TIU alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the B1 error exists in the card performance. If yes, see the
processing method in RS_BBE_LIMIT to eliminate the B1 error; if not, ➔ Step
3.

3. Perform the loopback on the alarmed optical interface (users can use the
optical attenuator during the optical fiber loopback to ensure the received
optical power is within the normal range) and check whether the RS_TIU alarm
exists.

4 If the RS_TIU alarm persists, replace the faulty card at the local station. If
the RS_TIU alarm persists after replacing the card, ➔ Step 4.

Version: A 225
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If no RS_TIU alarm exists, check whether the opposite end station can
transmit the J0 byte normally. If the alarm persist after eliminating the fault
of the far end, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.135 RX_ERR
Meaning

The received error packet threshold-crossing alarm. This alarm will be reported
when the quality of received error packets exceeds the received error packet
threshold.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, XSJ2, XSJ3

Influence on the system

The error packet will be discarded once it is detected. The excessive packet loss will
influence the service.

Possible cause

u The line is incorrectly connected or configured.

u The received error packet threshold is set inappropriately.

Handling procedure

1. Enter the OTNM2000 to check the RX_ERR alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the line is incorrectly connected; if yes, reconnect the optical
fiber or reconfigure the line to see whether the alarm is removed.

3. If the alarm persists, enter the card configuration GUI of the alarmed card.
Adjust the Received-Bad-Packet-Threshold appropriately.

226 Version: A
 3 Alarm Handling

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.136 SCLK_LOS
Meaning

The system clock loss alarm. This alarm will be reported if the card fails to detect the
system clock.

Alarm level

Critical alarm

Relevant card

E1J1, E1J2

Influence on the system

This alarm indicates that the card fails to detect the valid reference clock transmitted
from the backplane, and the service of the card is unstable.

Possible cause

u The clock and cross-connect card fails.

u The clock extraction module of the card fails.

Handling procedure

1. Enter the OTNM2000 to check the SCLK_LOS alarm and confirm the
information of the alarmed card.

2. Check whether the status and the performance information of the clock and
cross-connect card is normal and ensure the clock and cross-connect card is
not faulty.

3. If the alarm persists, perform the active / standby switching of the clock and
cross-connect card.

Version: A 227
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. If the alarm persists, plug and unplug or reset the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance for operation
procedures ).

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

6. If the alarm persists, insert the alarmed card to another slot.

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.137 SCK_LOS/SCK_LOS.
Meaning

The system clock loss alarm. This alarm occurs if the card fails to detect the system
clock.

Alarm level

u SCK_LOS: major alarm

u SCK_LOS.: critical alarm

Relevant card

u SCK_LOS: XGJ1, S1O1, ESJ2, S1J4, XSJ2

u SCK_LOS.: GSJ2, GSJ3, ESJ1, S1J1, S1J2, XSJ3

Influence on the system

This alarm indicates that the card fails to detect the valid reference clock transmitted
from the backplane, and the service of the card is unstable.

Possible cause

u The clock and cross-connect card fails.

u The clock extraction module of the card fails.

228 Version: A
 3 Alarm Handling

Handling procedure

1. Enter the OTNM2000 to check the SCK_LOS/SCK_LOS. alarm and confirm

the information of the alarmed card.

2. Check whether the status and the performance information of the clock and
cross-connect card is normal and ensure the clock and cross-connect card is
not faulty.

3. If the alarm persists, perform the active / standby switching of the clock and
cross-connect card.

4. If the alarm persists, plug and unplug or reset the alarmed card (see CiTRANS
660 High-capacity MPLS-TP Platform Routine Maintenance for operation
procedures ).

5. If the alarm persists, replace the alarmed card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

6. If the alarm persists, insert the alarmed card to another slot.

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.138 SPI_LOS
Meaning

The signal loss alarm of the TDM physical interface. The alarm occurs when the
S1J4 card cannot detect the normal optical signal input.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

When the SPI_LOS alarm occurs, the service of the alarmed line is interrupted.

Version: A 229
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The transmission of the optical module at the far end equipment is faulty.

u The receiving of the optical module on the alarmed S1J4 card at the local end is
faulty.

u Physical connection fault, such as broken pigtail, too small pigtail bend radius
and the ring flange fault.

u The optical interface is unclean.

Handling procedure

1. Enter the OTNM2000 to check the SPI_LOS alarm and confirm the information
such as the NE and card that generates the alarm.

2. Measure the input optical power of the alarmed S1J4 card with the optical
power meter. If the optical power is lower than -10dBm, the system decides that
no light exists.

4 If no light exists or the optical power is lower than -10dBm: check whether
the optical transmission at the far end equipment is normal; if not, eliminate
the far end equipment fault. If the alarm persists, ➔ Step 3.

4 If the received light is normal: replace or clean the corresponding optical

module of the local alarmed S1J4 card. If the alarm persists, ➔ Step 7.

3. Check whether the faults such as broken pigtail fiber, too small pigtail bend
radius and poor contact of the ring flange exist in the alarmed line; if yes,
eliminate the fault.

4. If the alarm persists, clean the optical interface of the S1J4 card of the far end
equipment.

5. If the alarm persists, replace the optical module of the alarmed line with an
identical spare one.

6. If the alarm persists, replace the S1J4 card on the far end with the spare S1J4
card.

7. If the alarm persists, clean the optical interface of the S1J4 card of the local end
equipment.

230 Version: A
 3 Alarm Handling

8. If the alarm persists, replace the optical module of the local end S1J4 card with
an identical spare one. If the SPI_LOS alarm persists, replace the S1J4 card on
the local end with the spare S1J4 card.

9. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.139 SPT_TF
Meaning

The transmitting failure alarm of the TDM physical interface.

Alarm level

Critical alarm

Relevant card

S1O1, S1J4

Influence on the system

When the SPI_TF alarm is generated, the local end cannot transmit the optical
signal normally, and the service in the alarmed line will be interrupted.

Possible cause

u The laser of the faulty port is disabled.

u The optical module is faulty.

u The card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the SPI_TF alarm and confirm the information
such as the NE and card that generates the alarm.

2. Check the working status of the laser at the faulty port. If the laser is disabled,
enable it; if the laser is working normally, ➔ Step 3.

3. Replace the optical module at the faulty port; if the alarm persists, ➔ Step 4.

Version: A 231
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. Replace the faulty card.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.140 SW_FAIL
Meaning

The switching failure alarm. The alarm occurs when the switching fails because the
active and protection paths of the APS protection are faulty.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The protection switching fails and the service is interrupted.

Possible cause

u The BACKUP_FAULT alarm exists in the NE, which causes the switching
failure.

u The alarmed card is faulty.

Handling procedure

1. Check the SW_FAIL alarm in the OTNM2000 and identify the alarmed NE /
card and its slot.

2. Check whether the BACKUP_FAULT alarm exists in the alarmed card.

4 If yes, eliminate the BACKUP_FAULT alarm, see BACKUP_FAULT in this

manual. If the alarm persists after this operation, ➔ Step 3.

4 If not, ➔ Step 3.

3. Replace the alarmed card with an identical spare one, ans wait a few minutes.

232 Version: A
 3 Alarm Handling

4. If the alarm persists, restore the working path to eliminate the SW_FAIL alarm.

5. If the working path cannot be restored, please contact FiberHome after-sales

maintenance engineer.

3.141 SWITHCH_LOOP
Meaning

The switch loop alarm. This alarm will be reported when the Ethernet ports of the
ESJ1 / ESJ2 cards detect the loopback.

Alarm level

Prompt alarm

Relevant card

ESJ1, ESJ2

Influence on the system

When the SWITCH_LOOP alarm is generated, the port which is enabled with the
port protection will stop transmitting data packets to prevent the switch abnormality
caused by the protection switching.

Possible cause

The SWITCH_LOOP alarm is reported when the loop exits in the ESJ1 / ESJ2 card.

Handling procedure

1. Enter the OTNM2000 to check the SWITCH_LOOP alarm and confirm the
information such as the NE, card or line that generates the alarm.

2. Check whether the performance statistic for the transmitted and received
packet of the alarmed port on the card is normal. Ascertain whether the loop
exists in the port.

4 If yes, eliminate the loop; if the alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

Version: A 233
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Check the physical connection of the equipment of the port to eliminate the
physical loop. If the alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.142 SWR
Meaning

The Rx switching alarm. This alarm will be generated when the working path is
faulty and the service is switched to the protection path.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the SWR alarm occurs, the working path is faulty and the service will be
switched to the protection path.

Possible cause

u The SWR alarm occurs as a subsequent alarm of alarms such as LINK_LOS,

RLOS, PPI_LOS, SPI_LOS, MS_AIS, RS_LOF, VP_LOC, VS_LOC.

u The OTNM2000 delivers the forced switch or manual control switch command
to the NE, triggering service switching to the protection path from the working
path.

Handling procedure

Note:
This alarm usually occurs or disappears together with the BRIDGE alarm.

234 Version: A
 3 Alarm Handling

1. Enter the OTNM2000 to check the SWR alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether alarms, such as LINK_LOS, RLOS, PPI_LOS, SPI_LOS,

MS_AIS, RS_LOF, VP_LOC, VS_LOC, exist in the NE.

4 If yes, see this manual for the corresponding alarm handling. Remove the
above alarms to restore the working path. Wait a few minutes (the preset
wait-to-restore time for switch) after the above operation. If the SWR alarm
persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the forced switch / Force-Backup or manual switch /

Manual_Switch_to_Backup is delivered to the alarmed clock and cross-connect
card.

4 If the control command is delivered and not canceled, deliver a

Restore_to_Active / Clear_Switch command to the LSP/ring which has
executed the above operation. If the alarm persists, ➔ Step 4.

4 If the control command is not delivered or canceled, ➔ Step 4.

Caution:
The forced switch and manual switch is used to test. The command
should be removed after the test.

4. Please contact FiberHome after-sales maintenance engineer.

3.143 SWTR
Meaning

The wait-to-restore alarm. The service is switched to the protection path when the
working path is faulty. The alarm will be generated when the service is ready to
switch back to the working path from the protection path after the fault of the working
path is eliminated. The alarm will disappear automatically after the service is
switched to the working path.

Alarm level

Minor alarm

Version: A 235
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

This alarm will not influence the system.

Possible cause

The working path is restored from the faulty condition.

Handling procedure

No handling is needed.

3.144 TRAF_ONLOAD
Meaning

Service loading alarm.

Alarm level

Prompt alarm

Relevant card

E1J2

Influence on the system

This alarm will not influence the system.

Possible cause

None.

Handling procedure

No handling is needed.

236 Version: A
 3 Alarm Handling

3.145 TEMP_ABNORMAL
Meaning

The abnormal temperature alarm. This alarm will be reported when the equipment
operating temperature detected by the system is higher than the preset temperature
threshold.

Alarm level

Critical alarm

Relevant card

NMUJ1

Influence on the system

The over-high working temperature of the card may be hazard to the system. The
timely processing is needed when the bit error or service interruption may occur and
the card may be damaged if the equipment operates in this status for a long term.

Possible cause

u The temperature threshold is not set appropriately .

u The fan stops working or too much dust is on the anti-dust screen.

u The cooling facility in the equipment is faulty, causing the over-high ambient
temperature.

u The card is faulty.

Handling procedure

1. Query the upper limit setting of the temperature and the current card working
temperature, so as to determine whether the alarm is a false alarm.

2. If the alarm persists, check whether the fan unit is faulty and whether the
FANALAM alarm exists; if yes, eliminate the FANALAM alarm first and check
whether this alarm is removed.

Version: A 237
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. If the alarm still exists, check whether too much dust is in the anti-dust screen,
causing the air cooling problem. If yes, clean the anti-dust screen and check
whether this alarm is removed.

4. If the alarm persists, check whether the equipment working ambient

temperature is normal. If not, check whether the cooling facility is faulty. Make
sure the ambient temperature is normal and check whether this alarm is
removed.

5. If the alarm persists, check whether the temperature measuring chip in the card
is faulty; if yes, replace the faulty card.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.146 TEMP_OVER
Meaning

The card temperature threshold-crossing alarm. This alarm will be reported when
the equipment operating temperature detected by the system is higher than the
preset temperature threshold.

Alarm level

Critical alarm

Relevant card

NMUJ1

Influence on the system

The over-high working temperature of the card may be hazard to the system. The
timely processing is needed when the bit error or service interruption may occur and
the card may be damaged if the equipment operates in this status for a long term.

Possible cause

u The temperature threshold is not set appropriately.

u The fan stops working or too much dust is on the anti-dust screen.

238 Version: A
 3 Alarm Handling

u The cooling facility in the equipment is faulty, causing the over-high ambient
temperature.

u The card is faulty.

Handling procedure

1. Query the upper limit setting of the temperature and the current card working
temperature, so as to determine whether the alarm is a false alarm.

2. If the alarm persists, check whether the fan unit is faulty and whether the
FANALAM alarm exists; if yes, eliminate the FANALAM alarm first and check
whether this alarm is removed.

3. If the alarm persists, check whether too much dust is on the anti-dust screen,
causing the air cooling problem. If yes, clean the anti-dust screen and check
whether this alarm is removed.

4. If the alarm persists, check whether the equipment working ambient

temperature is normal. If not, check whether the cooling facility is faulty. Make
sure the ambient temperature is normal and check whether this alarm is
removed.

5. If the alarm persists, check whether the temperature measuring chip in the card
is faulty; if yes, replace the faulty card.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.147 TEMP_TCT
Meaning

The over temperature threshold-crossing alarm. This alarm will be reported when
the equipment operating temperature detected by the system is higher than the
preset temperature upper limit value.

Alarm level

Critical alarm

Version: A 239
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XGJ1, GSJ2, GSJ3, XSJ2, XSJ3

Influence on the system

The over-high working temperature of the card may be hazard to the system. The
timely processing is needed when the bit error or service interruption may occur and
the card may be damaged if the equipment operates in this status for a long term.

Possible cause

u The temperature threshold is not set appropriately.

u The fan stops working or too much dust is on the anti-dust screen.

u The cooling facility in the equipment is faulty, causing the over-high ambient
temperature.

u The card is faulty.

Handling procedure

1. Query the temperature upper limit setting and the current card working
temperature, so as to ascertain whether the alarm is a false alarm.

2. If the alarm persists, check whether the fan unit is faulty and whether the
FANALAM alarm exists; if yes, eliminate the FANALAM alarm first and check
whether this alarm is removed.

3. If the alarm still exists, check whether too much dust is in the anti-dust screen,
causing the air cooling problem. If yes, clean the anti-dust screen and check
whether this alarm is removed.

4. If the alarm persists, check whether the equipment working ambient

temperature is normal. If not, check whether the cooling facility is faulty. Ensure
the ambient temperature is normal and check whether this alarm is removed.

5. If the alarm persists, check whether the temperature measuring chip in the card
is faulty; if yes, replace the faulty card.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

240 Version: A
 3 Alarm Handling

3.148 TF
Meaning

The laser transmission failure alarm.

Alarm level

Critical alarm

Relevant card

S1J2

Influence on the system

When this alarm occurs, the services carried by the alarmed port will be interrupted.

Possible cause

u The Laser_Auto_Shutdown function is enabled, and the line shuts down the
laser when receiving the LOS alarm.

u The laser shutdown command is delivered in the OTNM2000.

u The hot-pluggable optical module is not well connected to the socket.

u The contact between the card and the backplane is poor.

u The clock and cross-connect card is faulty.

u The optical module is faulty.

u The local card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the TF alarm and confirm the information such
as the NE or line that generates the alarm.

4 If all optical interfaces of multiple cards in the same NE report the TF alarm,
➔ Step 2.

4 If not, ➔ Step 3.

Version: A 241
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check whether the clock and cross-connect card of the NE is working normally.
Users can ascertain by the switchover between the active and the standby
clock and cross-connect cards, plugging and unplugging or replacing the clock
and cross-connect card.

3. Check the alarm of the optical interface in the alarmed card.

4 If all the optical interfaces of the alarmed card report the TF alarm, ➔ Step
4.

4 If some of the optical interfaces of the alarmed card report the TF alarm, ➔
Step 7.

4. Check whether the card is well connected to the backplane; if not, secure the
card. If the alarm persists after plugging and unplugging the card, ➔ Step 5.

5. Replace the alarmed card. If the alarm persists, ➔ Step 6.

6. Perform the switchover between the active / standby clock and cross-connect
card to check whether the alarm disappears. If the alarm is removed, replace
the clock and cross-connect card in the standby status. If the alarm persists, ➔
Step 12.

7. Check whether the Laser_Auto_Shutdown is enabled.

4 If yes, check whether the LOS alarms exist in the line. If yes, eliminate the
alarm. If not, ➔ Step 8.

4 If not, ➔ Step 8.

8. Check whether the Laser_shutdow control command is executed in the

OTNM2000. Execute the Enable control command to enable the laser. If the TF
alarm still exists, ➔ Step 9.

9. Check whether the hot-pluggable optical module is well connected to the

socket; if not, plug and unplug the optical module (referring to CiTRANS 660
High-capacity MPLS-TP Platform Routine Maintenance). If the TF alarm still
exists, ➔ Step 10.

10. Replace the laser module. If the TF alarm still exists, ➔ Step 11.

11. Replace the alarmed card (see CiTRANS 660 High-capacity MPLS-TP
Platform Routine Maintenance). If the TF alarm still exists, ➔ Step 12.

12. Please contact FiberHome after-sales maintenance engineer.

242 Version: A
 3 Alarm Handling

3.149 TOD_CRC_ERR
Meaning

The ToD CRC error alarm.

Alarm level

Major alarm

Relevant card

XCUJ2

Influence on the system

The synchronization reference source switches or the time of day of the time
synchronization is incorrect.

Possible cause

u The connection of time source signal wires is faulty, which causes the
connection interruption.

u The time server is faulty.

u The TOD interface is damaged.

Handling procedure

1. Check whether the clock configuration on the local end and the adjacent
equipment is correct.

4 If yes, ➔ Step 2.

4 If not, re-configure the clock configuration. If the alarm persists after the
operation, ➔ Step 2.

2. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 3.

Version: A 243
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, use the the internal oscillator to provide the clock for other NEs when
the external synchronization reference source or the master clock
equipment is replaced. If the alarm persists after the operation, ➔ Step 3.

3. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.150 TOD_LOS
Meaning

The ToD loss alarm. The alarm occurs when the TOD frame signal is not detected.

Alarm level

Major alarm

Relevant card

XCUJ2

Influence on the system

The synchronization reference source switches or the time of day of the time
synchronization is incorrect.

Possible cause

u The connection of time source signal wires is faulty, which causes the
connection interruption.

u The time server is faulty.

u The TOD interface is damaged.

244 Version: A
 3 Alarm Handling

Handling procedure

1. Check whether the clock configuration on the local end and the adjacent
equipment is correct.

4 If yes, ➔ Step 2.

4 If not, re-configure the clock configuration. If the alarm persists, ➔ Step 3.

2. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the requirement.

4 If yes, ➔ Step 3.

4 If not, use the the internal oscillator to provide the clock for other NEs when
the external synchronization reference source or the master clock
equipment is replaced. If the alarm persists, ➔ Step 3.

3. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.151 TU_AIS
Meaning

Tributary unit alarm indication. This alarm occurs when the card detects that the TU
signal channel (including the TU pointer) is all-ones.

Alarm level

Minor alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

The service in the path with TU_AIS alarm will be interrupted.

Version: A 245
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The higher order alarms such as AU_AIS (The administrative unit alarm
indication) alarm and the HP_SLM (The higher order path signal identifier byte
mismatch) alarm exist in the system.

u The previous equipment is faulty, transmitting the all-ones signal to the local
end.

u The corresponding path of the opposite end is invalid.

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the TU_AIS alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether any higher-level alarm, such as AU_AIS and HP_SLM exists at
the local end.

4 If yes, remove the higher order alarm in the line. If the alarm persists, ➔
Step 3.

4 If not, ➔ Step 3.

3. Check whether the previous equipment is operating normally.

4 If not, eliminate the previous equipment fault. If the alarm persists, ➔ Step
4.

4 If yes, ➔ Step 4.

4. Check whether the opposite end equipment is operating normally and whether
the configuration of the tributary card and services is correct.

4 If yes, eliminate the opposite end fault. If the alarm persists, ➔ Step 5.

4 If not, ➔ Step 5.

5. Plug and unplug the clock and cross-connect cards (see Plugging and
Unplugging Cards).

6. Wait a few minutes. If the alarm persists after restarting the XCUJ2 card,
replace the alarmed card with an identical spare card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

246 Version: A
 3 Alarm Handling

7. Wait a few minutes. If the alarm still exists after restarting the clock and cross-
connect card, plug and unplug the alarmed S1J4 card.

8. Wait a few minutes. If the alarm persists after restarting the S1J4 card, replace
the alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

9. Wait a few minutes. If the alarm still exists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.152 TU_LOM
Meaning

The tributary unit loss of multiframe alarm. This alarm occurs when the backplane
side of the S1J1 card receives the invalid pointer for eight consecutive frames, or
eight consecutive new data flags (NDF) are detected.

Alarm level

Critical alarm

Relevant card

S1J1

Influence on the system

The service in the lower order path that generates the TU_LOM alarm will be
interrupted.

Possible cause

u The higher order alarms such as AU_AIS (The administrative unit alarm
indication) alarm and the HP_SLM (The higher order path signal identifier byte
mismatch) alarm exist in the system.

u The previous equipment is faulty.

u The corresponding tributary path at the far end is faulty.

u The clock and cross-connect card or the tributary card is faulty.

Version: A 247
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Enter the OTNM2000 to check the TU_LOM alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether any higher order alarms such as AU_AIS and HP_SLM exist at
the local end.

4 If yes, remove the higher order alarm in the line. If the alarm still exists, ➔
Step 3.

4 If not, ➔ Step 3.

3. Check whether the previous equipment is operating normally.

4 If not, eliminate the previous equipment fault. If the alarm persists after the
operation, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Check whether the corresponding tributary path at the far end is operating
normally.

4 If not, eliminate the equipment fault at the opposite end. If the alarm
persists after the operation, ➔ Step 5.

4 If yes, ➔ Step 5.

5. Plug and unplug the clock and cross-connect cards (see Plugging and
Unplugging Cards).

6. Wait a few minutes. If the alarm persists after restarting the XCUJ2 card,
replace the alarmed card with an identical spare card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the clock and cross-
connect card, plug and unplug the alarmed S1J1 card.

8. Wait a few minutes. If the alarm persists after restarting the S1J1 card, replace
the alarmed S1J1 card with an identical spare card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

248 Version: A
 3 Alarm Handling

3.153 TU_LOP
Meaning

The pointer loss alarm of the tributary unit. This alarm occurs when the backplane
side of the S1J4 card receives the invalid pointer for 8 consecutive frames, or 8
consecutive new data flags (NDF) are detected.

Alarm level

Critical alarm

Relevant card

S1O1, S1J1, S1J4

Influence on the system

The service in the lower order path that generates the TU_LOP alarm will be
interrupted.

Possible cause

u The higher order path alarms such as AU_AIS (The administrative unit alarm
indication) alarm and the HP_SLM (The higher order path signal identifier byte
mismatch) alarm exist in the system.

u The previous equipment is faulty.

u The corresponding tributary path at the opposite end equipment is faulty.

u The clock and cross-connect card or the tributary card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the TU_LOP alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether any higher-level alarms such as AU_AIS and HP_SLM exist at
the local end.

4 If yes, remove the higher-level alarm in the line. If the alarm persists after
the operation, ➔ Step 3.

Version: A 249
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, ➔ Step 3.

3. Check whether the previous equipment is operating normally.

4 If not, eliminate the previous equipment fault. If the alarm persists after the
operation, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Check whether the corresponding tributary path at the opposite end is

operating normally.

4 If not, eliminate the equipment fault at the opposite end. If the alarm still
exists, ➔ Step 5.

4 If yes, ➔ Step 5.

5. Plug and unplug the clock and cross-connect cards (see Plugging and
Unplugging Cards).

6. Wait a few minutes. If the alarm persists after restarting the XCUJ2 / XCUJ4
card, replace the alarmed card with an identical spare card (see CiTRANS 660
High-capacity MPLS-TP Platform Routine Maintenance for operation
procedures).

7. Wait a few minutes. If the alarm still exists after restarting the clock and cross-
connect card, plug and unplug the alarmed S1J4 card.

8. Wait a few minutes. If the alarm persists after restarting the S1J4 card, replace
the alarmed S1J4 card with an identical spare card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.154 TX_ERR
Meaning

The transmitted error packet threshold-crossing alarm. The TX_ERR alarm will be
reported when the number of the transmitted error packet exceeds the the threshold
value.

250 Version: A
 3 Alarm Handling

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The normal transmission of service signals is influenced.

Possible cause

u The interference source exists in the equipment room or the equipment is not
well-grounded.

u The optical fiber is incorrectly connected.

u The card at the local end fails.

Handling procedure

1. Enter the OTNM2000 to check the TX_ERR alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the equipment is well-grounded, and whether the powerful

interference source is near the equipment, and whether the power supply
works normally. If the ambient environment is normal but the alarm persists, ➔
Step 3.

3. Check whether the line is incorrectly connected; if yes, reconnect the optical
fiber or reconfigure the line. If the alarm persists, ➔ Step 4.

4. Replace the service optical module or the service card. If the alarm persists, ➔
Step 4.

5. Please contact FiberHome after-sales maintenance engineer.

3.155 VC_AIS
Meaning

MPLS-TP virtual channel alarm indication signal.

Version: A 251
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The service of the path with VC_AIS alarm will be interrupted.

Possible cause

u The AU_AIS (The administrative unit alarm indication) alarm and the HP_SLM
(The higher order path signal identifier byte mismatch) alarm exist.

u The previous equipment is faulty, transmitting the all-ones signal to the local
end.

u The corresponding path of the far end is invalid.

u The alarmed card is faulty.

Handling procedure

1. Enter the OTNM2000 to check the VC_AIS alarm and confirm the information
such as the NE, card or line that generates the alarm.

2. Check whether any higher-level alarms such as AU_AIS and HP_SLM exist at
the local end.

4 If yes, clear the higher-level alarm in the line. If the alarm persists after the
above operation, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the previous equipment is operating normally.

4 If not, eliminate the previous equipment fault. If the alarm persists, ➔ Step
4.

4 If yes, ➔ Step 4.

4. Check whether the far end equipment is operating normally and whether the
configuration of the tributary card and services is correct.

252 Version: A
 3 Alarm Handling

4 If yes, eliminate the remote end fault. If the alarm persists after the above
operation, ➔ Step 5.

4 If not, ➔ Step 5.

5. Plug and unplug the clock and cross-connect cards (see Plugging and
Unplugging Cards).

6. Wait a few minutes. If the alarm persists after restarting the XCUJ2 card,
replace the alarmed card with an identical spare card (see CiTRANS 660 High-
capacity MPLS-TP Platform Routine Maintenance for operation procedures).

7. Wait a few minutes. If the alarm persists after restarting the clock and cross-
connect card, plug and unplug the alarmed card (see Plugging and Unplugging
Cards for operation procedures).

8. Wait a few minutes. If the alarm persists after restarting the card, replace the
alarmed card with an identical spare card (see CiTRANS 660 High-capacity
MPLS-TP Platform Routine Maintenance for operation procedures).

9. Wait a few minutes. If the alarm persists after restarting the card, please
contact FiberHome after-sales maintenance engineer.

3.156 VC_CSF
Meaning

The client layer signal loss alarm of the MPLS-TP virtual channel. This alarm occurs
when the local end VC layer receives the CSF frame from the far end.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XSJ2, XSJ3

Influence on the system

The VC_CSF alarm may cause the service receiving failure of the client layer at the
local end. A switching may be triggered when users configure the relevant
protection.

Version: A 253
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u The faults like VC_LOC, VC_MMG and VC_UNM may cause the alarm when
the input signal of the far end client layer is detected to be failed.

u The CSF frame is input in the far end client layer, used for informing faults
actively.

Handling method

1. Enter the OTNM2000 to check the VC_CSF alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms which influence the service receiving such as
VC_LOC, VC_MMG and VC_UNM exist at the local end.

4 If yes, remove the VC_LOC, VC_MMG and VC_UNM alarms. If the

VC_CSF alarm persists after the fault is eliminated, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the UNI side of the far end is faulty.

4 If yes, eliminate the fault. If the VC_CSF alarm persists, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.157 VC_LCK
Meaning

The MPLS-TP virtual channel lock alarm. This alarm occurs when the local end VC
layer receives the LCK frame transmitted by the adjacent MEP.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

254 Version: A
 3 Alarm Handling

Influence on the system

The service in the alarmed line will be interrupted (usually for testing).

Possible cause

The LCK frame transmission at the far end is enabled.

Handling procedure

The LCK frame is the MEP announcement of its planned management or diagnostic
action to its adjacent client layer MEP. No handling is needed for the alarm.

3.158 VC_LOC
Meaning

The connectivity verification signal loss alarm of the MPLS-TP virtual channel. If the
CV frame of the local end VC layer is enabled, the VC_LOC alarm will be generated
when the CCM frame transmitted from the far end is not received in 3.5 times CCM
frame transmission period.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VC_LOC alarm is generated, the OAM function in the alarmed channel
cannot operate normally, and the service on the path of this layer may be interrupted.

Possible cause

u Physical fault, such as link fault or equipment fault.

u The CV frame transmission of the OAM in the VC layer connected to the far
end is disabled.

Version: A 255
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Check whether the CV frame transmission at the far end VC layer of the
alarmed line is enabled.

4 If yes, ➔ Step 2.

4 If not, enable it. If the alarm persists, ➔ Step 2.

2. Enter the OTNM2000 to check the information such as the NE, card or line that
generates the VC_LOC alarm.

3. Check and handle the card or line fault relevant to the alarm. If the alarm
persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.159 VC_MMG
Meaning

The unexpected maintenance entity alarm of the MPLS-TP virtual channel. The
alarm occurs when the CV frame received by the MEP does not match the MEG ID
network configuration.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The OAM of the VC layer cannot operate normally when the VC_MMG alarm occurs.

Possible cause

The MEG related configuration of VC OAM at the local end does not match that of
the far end.

256 Version: A
 3 Alarm Handling

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VC_MMG alarm.

2. Check whether the MEG configuration on the far end is consistent with that of
the local end. Check the MEP configuration of VC OAM in the corresponding
item of the alarmed line in the Demanded-OAM-Config tab of the XCUJ2/
XCUJ4 card's card configuration GUI.

4 If yes, ➔ Step 3.

4 If not, modify the MEG-ICC or MEG-UMC information. If the alarm persists,

➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.160 VC_RDI
Meaning

The far end fault indication of the MPLS-TP virtual channel. This alarm occurs when
the local end VC layer receives the set CCM messages of the RDI (Remote Defect
Indication).

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The VC_RDI information is transmitted by the faulty MEP. Receiving the VC_RDI
information indicates the remote equipment receiving is faulty, and the unidirectional
service is interrupted.

Possible cause

u A physical fault exists in the Rx end of the far end equipment, including the card
and line fault.

Version: A 257
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

u The setting of the Tx service at the local end does not match that of the
opposite end.

Handling procedure

1. Enter the OTNM2000 to check the VC_RDI alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms such as VC_AIS, VC_MMG and VC_UNM exist at
the receive end of the remote equipment.

4 If yes, eliminate the far end fault. After this operation, if the VC_RDI alarm
persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the service tag value transmitted by the local end which
generates the alarmed PW matches the service tag value received by the far
end.

4 If yes, ➔ Step 4.

4 If not, modify the tag value according to the actual service planning. After
this operation, if the VC_RDI alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.161 VC_SD
Meaning

The signal degradation alarm of the MPLS-TP virtual channel. This alarm occurs
when the packet loss rate of the VC layer signal is higher than VS_SD (0 to 65535)
and lower than VS_SF (0 to 65535).

Alarm level

Major alarm

Relevant card

XCUJ2, XCUJ4

258 Version: A
 3 Alarm Handling

Influence on the system

The current VC layer degrades, and packet loss rate is low.

Possible cause

u The OAM configuration of the VC layer on both sides of the line is not
consistent.

u The setting of the VS_SD (0 to 65535) and the VS_SF (0 to 65535) is not
appropriate.

u The other alarm occurs in the VC layer, such as VC_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VC_SD alarm.

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SD (20Second) (0 to 65535) is
correct.

3. If the alarm persists, check whether the OAM configuration of the VC layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by configuration inconsistency and protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.162 VC_SF
Meaning

The signal failure alarm of the MPLS-TP virtual channel. This alarm occurs when the
packet loss rate of the VC layer signal is higher than the VS_SF (20s) (0 to 65535).

Version: A 259
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Major alarm

Relevant card

XCUJ2, XCUJ4

Influence on the system

The performance of the VC layer is degraded, and the packet loss rate is high.

Possible cause

u The OAM configuration of the VC layer on both sides of the line is not
consistent.

u The setting of the VS_SF (0 to 65535) is not appropriately.

u The other alarm occurs in the VC layer, such as VC_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VC_SF alarm.

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SF (20Second) (0 to 65535) is
correct.

3. If the alarm persists, check whether the OAM configuration of the VC layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

260 Version: A
 3 Alarm Handling

3.163 VC_UNM
Meaning

The unexpected maintenance entity alarm of the MPLS-TP virtual channel. The
alarm will be generated when the MEP receives the unmatched MEP-ID.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VC_UNM alarm is generated, the OAM of the alarmed VC layer cannot
operate normally.

Possible cause

The MEP-ID configuration of the OAM of the VC layer at the local end does not
match that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VC_UNM alarm.

2. Check whether the MEP-ID configuration on the far end is consistent with that
of the local end. Check the MEP configuration of VC OAM in the corresponding
item of the alarmed line in the Demanded-OAM-Config tab of the XCUJ2/
XCUJ4 card's card configuration GUI.

4 If yes, ➔ Step 3.

4 If not, modify the MEP-ID information of the far end to be consistent with
that of the local end. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

Version: A 261
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.164 VC_UNP
Meaning

The time interval mismatch alarm of the MPLS-TP virtual channel. This alarm
occurs when the receiving frequency of the CV frame is different from the
expectation.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VC_UNP alarm occurs, the OAM of the alarmed VC layer cannot operate
normally.

Possible cause

The transmission period of the CV frame configured by the VC layer at the local end
is inconsistent with that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the VC_UNP alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the CV frame transmission period on the local end of the
alarmed line is consistent with that of the far end. Check the CV frame
transmission period in the corresponding item of the alarmed line in the
Demanded-OAM-Config tab in the XCUJ2/XCUJ4 card's card configuration
GUI.

4 If yes, ➔ Step 3.

262 Version: A
 3 Alarm Handling

4 If not, modify the transmission period configuration of the CV frame to

ensure the transmission period of the local end is consistent with that of
the far end. It is recommended to be set to 3.33ms. If the alarm persists, ➔
Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.165 VCLB_LOS
Meaning

The loopback signal time-out alarm of the MPLS-TP virtual channel.

Alarm level

Prompt alarm

Relevant card

GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The loopback test will fail and the line cannot work normally.

Possible cause

The loopback frame (LB) configuration in the OAM management of the VC layer is
enabled. The local end transmits the OAM LBM messages and expects that the far
end returns the OAM LBR messages. This alarm will be reported if the OAM LBR
messages are not returned in time.

Handling procedure

1. Enter the OTNM2000 to check whether the transmitting of the NE loopback

frame at the opposite end is enabled. The loopback frame configuration is in
the Demanded-OAM-Config tab of the clock and cross-connect card.

2. If the alarm persists, check whether the optical fiber and the physical link from
the local end to the far end is connected normally.

Version: A 263
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

4. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.166 VP_AIS
Meaning

The alarm indication signal of the MPLS-TP virtual path. This alarm occurs when the
local end VP layer receives the message containing the AIS alarm information.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

After the VP_AIS alarm is generated at the local end, the system will transmit back
the RDI message to the far end automatically, and the VP_AIS alarm will be
generated at the far end.

Possible cause

u Alarms such as the VP_SSF exist.

u The transmission at the far end is faulty.

Handling procedure

1. Enter the OTNM2000 to check the VP_AIS alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms which influence the receiving of the service such as
VP_SSF exist at the local end.

264 Version: A
 3 Alarm Handling

4 If yes, remove the VP_SSF alarm. If the VC_AIS alarm still exists after the
fault is eliminated, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the transmission of the line side at the far end is faulty.

4 If yes, eliminate the fault. If the VC_AIS alarm still exists after clearing the
transmission fault at the line side of the opposite end, ➔ Step 4.

4 If yes, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.167 VP_LCK
Meaning

The MPLS-TP virtual path lock alarm. This alarm occurs when the local end VP
layer receives the LCK frame transmitted by the far end.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The alarmed LSP service will be interrupted and occupied by the far end for purpose
(such as testing).

Possible cause

The LCK frame transmission at the far end VP layer is enabled.

Handling procedure

The LCK frame is the MEP announcement of its planned management or diagnostic
action to its adjacent client layer MEP. No handling is needed for the alarm.

Version: A 265
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.168 VP_LOC
Meaning

The connectivity verification signal loss alarm of the MPLS-TP virtual path. If the CV
frame of the local end VP layer is enabled, the VP_LOC alarm occurs when the
CCM frame transmitted from the far end is not received in 3.5 times CCM frame
transmission period.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VP_LOC alarm is generated, the OAM function in the alarmed channel
cannot operate normally, and the service on the path of this layer may be interrupted.

Possible cause

u Physical fault, such as the link fault or the equipment fault.

u The CV frame transmission of the OAM in the VP layer connected to the far end
is disabled.

Handling procedure

1. Check whether the CV frame transmission at the far end VP layer of the
alarmed line is enabled.

4 If yes, ➔ Step 2.

4 If not, enable it. If the alarm persists, ➔ Step 2.

2. Enter the OTNM2000 to see the NE, card and the line which generate the
VP_LOC alarm; handle and the alarmed card or the line fault.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

266 Version: A
 3 Alarm Handling

3.169 VP_MMG
Meaning

The unexpected maintenance entity alarm of the MPLS-TP virtual path. The alarm
occurs when the CV frame received by the MEP does not match the MEG ID
network configuration.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The OAM of the VP layer cannot operate normally when the VP_MMG alarm is
generated.

Possible cause

The MEG setting of the VP OAM at the local end does not match that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VP_MMG alarm.

2. Check whether the MEG configuration on the far end is consistent with that of
the local end. Check the MEP configuration of the VP OAM in the
corresponding item of the alarmed line in the Demanded-OAM-Config tab.

4 If yes, ➔ Step 3.

4 If not, modify the MEG-ICC or MEG-UMC information. If the alarm persists,

➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

Version: A 267
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.170 VP_RDI
Meaning

The far end fault indication of the MPLS-TP virtual path. This alarm occurs when the
local end VP layer receives the set CCM messages of the RDI field.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The VP_RDI information is transmitted by the faulty MEP. Receiving the VP_RDI
information indicates the remote equipment receiving is faulty, and the unidirectional
service is interrupted.

Possible cause

u A physical fault exists in the Rx end of the far end equipment, including the card
and line fault.

u The service configuration transmitted by the local end does not match the far
end configuration, including the tag value, MEG ID and MEP-ID.

Handling procedure

1. Enter the OTNM2000 to check the VP_RDI alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms such as VP_AIS, VP_MMG, VP_UNM exist at the
receive end of the remote equipment.

4 If yes, eliminate the far end fault. After this operation, if the VP_RDI alarm
still exists, ➔ Step 3.

4 If not, ➔ Step 3.

268 Version: A
 3 Alarm Handling

3. Check whether the service tag value transmitted by the local end which
generates the alarmed LSP matches the service tag value received by the far
end.

4 If yes, ➔ Step 4.

4 If not, modify the tag value according to the actual service planning. After
this operation, if the VP_RDI alarm persists, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.171 VP_SD
Meaning

The signal degradation alarm of the MPLS-TP virtual path. This alarm occurs when
the packet loss rate of the VC layer signal is higher than VS_SD (0 to 65535) and
lower than VS_SF (0 to 65535).

Alarm level

Major alarm

Relevant card

XCUJ2, XCUJ4

Influence on the system

The current VP layer degrades, and the packet loss rate is lower.

Possible cause

u The OAM configuration of the VP layer on both sides of the line is not
consistent.

u The setting of the VS_SD (0 to 65535) and the VS_SF (0 to 65535) is not
appropriate.

u The other alarm occurs, such as VP_LOC.

Version: A 269
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VP_SD alarm.

2. If the alarm persists, check whether the OAM configuration of the VP layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

3. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

4. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.172 VP_SF
Meaning

The signal failure alarm of the MPLS-TP virtual path. This alarm occurs when the
packet loss rate of the VP layer signal is higher than the VS_SF (20s) (0 to 65535).

Alarm level

Major alarm

Relevant card

XCUJ2, XCUJ4

Influence on the system

The current VP layer is degraded, and packet loss rate is high.

Possible cause

u The OAM configuration of the VP layer on both sides of the line is not
consistent.

270 Version: A
 3 Alarm Handling

u The VS path signal failure threshold (20s) is set inappropriately.

u The other alarm occurs, such as VP_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VP_SF alarm.

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SD (20Second) (0 to 65535)is
correct.

3. If the alarm persists, check whether the OAM configuration of the VP layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.173 VP_SSF
Meaning

The service layer signal failure alarm of the MPLS-TP virtual path. This alarm occurs
when the packet loss rate of the VP layer signal is higher than the VS_SF (20s) (0
to 65535).

Alarm level

Critical alarm

Relevant card

GSJ2, XCUJ2, XSJ2, XSJ3

Version: A 271
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The performance of the current VP layer is degraded, and the packet loss rate is
higher.

Possible cause

u The OAM configuration of the VP layer on both sides of the line is not
consistent.

u The VP path signal failure threshold (20s) is set inappropriately.

u The other alarm occurs, such as VP_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VP_SF alarm.

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SF (20Second) (0 to 65535) is
correct.

3. If the alarm persists, check whether the OAM configuration of the VP layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exist. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.174 VP_UNM
Meaning

The unexpected maintenance entity alarm of the MPLS-TP virtual path. The alarm
will be generated when the MEP receives the unmatched MEP-ID.

272 Version: A
 3 Alarm Handling

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VP_UNM alarm is generated, the OAM of the alarmed VP layer cannot
operate normally.

Possible cause

The MEG-ID configuration of the OAM of the VP layer at the local end does not
match that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VP_UNM alarm.

2. Check whether the MEP-ID configuration at the far end is consistent with that of
the local end. Check the MEP configuration of VP OAM in the corresponding
item of the alarmed line in the Demanded-OAM-Config tab.

4 If yes, ➔ Step 3.

4 If not, modify the MEP-ID information of the far end to be consistent with
that of the local end. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.175 VP_UNP
Meaning

The time interval mismatch alarm of the MPLS-TP virtual path. This alarm occurs
when the receiving frequency of the CV frame is different from the expectation.

Version: A 273
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

When the VP_UNP alarm is generated, the OAM of the alarmed VP layer cannot
operate normally.

Possible cause

The transmission period of the CV frame configured by the VP layer at the local end
is inconsistent with that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the VP_UNP alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the CV frame transmission period on the local end of the
alarmed line is consistent with that of the far end. Check the CV frame
transmission period in the corresponding item of the alarmed line in the
Demanded-OAM-Config tab in the card configuration.

4 If yes, ➔ Step 3.

4 If not, modify the transmission period of the CV frame to ensure that the
transmission period in the local end is consistent with that of the far end. It
is recommended to be set to 3.33ms. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.176 VPLB_LOS
Meaning

The loopback signal time-out alarm of the MPLS-TP virtual section.

274 Version: A
 3 Alarm Handling

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XCUJ2, XCUJ4, XSJ2, XSJ3

Influence on the system

The loopback test will fail and the line cannot work normally.

Possible cause

The loopback frame configuration (LB) in the OAM management of the VP layer is
enabled. The local end transmits the OAM LBM messages and expects that the far
end returns the OAM LBR messages. This alarm will be reported if the OAM LBR
messages are not returned in time.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VPLB_LOS alarm.

2. Enter the OTNM2000 to check whether the transmitting of the NE loopback

frame at the opposite end is enabled. The loopback frame configuration is in
the Demanded-OAM-Config tab of the clock and cross-connect card.

3. If the alarm persists, check whether the optical fiber line and the physical link
connection from the local end to the far end is normal.

4. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

Version: A 275
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.177 VS_AIS
Meaning

The alarm indication signal of the MPLS-TP virtual section. This alarm occurs when
the local end VS layer receives the message containing the AIS alarm information.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

After the VS_AIS alarm is generated at the local end, the system will transmit back
the RDI message to the far end automatically, and the VS_RDI alarm will be
generated at the far end.

Possible cause

u The alarms such as VS_SD (VP service signal degrade) exist at the local end.

u The opposite end transmission is faulty.

Handling procedure

1. Enter the OTNM2000 to check the VS_AIS alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms which influence the receiving of services such as
VS_SD exist at the local end.

4 If yes, clear the alarms. Refer to related contents in this manual for the
handling method. If the VC_AIS alarm persists after the fault is eliminated,
➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the opposite end transmission at the line side is faulty.

276 Version: A
 3 Alarm Handling

4 If yes, eliminate the fault. If the VC_AIS alarm persists after clearing the
opposite end transmission fault at the the line side, ➔ Step 4.

4 If the opposite end transmission is normal, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

3.178 VS_LCK
Meaning

The MPLS-TP virtual section lock alarm. This alarm occurs when the local end VS
layer receives the LCK frame information transmitted by the far end.

Alarm level

Prompt alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

The alarmed line service will be interrupted and occupied by the far end for purpose
(such as testing).

Possible cause

The LCK frame of the far end VS layer is enabled.

Handling procedure

The LCK frame is the MEP announcement of its planned management or diagnostic
action to its adjacent client layer MEP. No handling is needed for the alarm.

Version: A 277
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.179 VS_LOC
Meaning

The connectivity verification signal loss alarm of the MPLS-TP virtual section. If the
local end CV frame at the VS layer is enabled, the VS_LOC alarm will be generated
when the CCM frame transmitted from the far end is not received in 3.5 times CCM
frame transmission period.

Alarm level

Critical alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

When the VS_LOC alarm occurs, the OAM function in the alarmed channel cannot
operate normally, and the service on the path of this layer may be interrupted.

Possible cause

u Physical fault, such as link fault or equipment fault.

u The CV frame transmission of the OAM at the VS layer connected to the far
end is disabled.

Handling procedure

1. Check whether the CV frame transmission at the far end VS layer of the
alarmed line is enabled.

4 If yes, ➔ Step 2.

4 If not, enable it. If the alarm persists, ➔ Step 2.

2. Enter the OTNM2000 to check the information such as the NE, card or line that
generates theVS_LOC alarm. Handle the card or the line fault relevant to the
alarm.

3. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

278 Version: A
 3 Alarm Handling

3.180 VS_MMG
Meaning

The MPLS-TP virtual section unexpected maintenance entity group end point alarm.
The alarm occurs when the MEP receives the CV frame with mismatched MEG ID.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

The OAM of the VS layer cannot operate normally when the VS_MMG alarm occurs.

Possible cause

The MEG setting of the VS OAM at the local end does not match that of the far end.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VS_MMG alarm.

2. Check whether the MEG configuration of the far end is consistent with that of
the local end. Check the MEG configuration of the VS OAM in the Demanded-
OAM-Config tab.

4 If yes, ➔ Step 3.

4 If not, modify the MEG-ICC or MEG-UMC information. If the alarm persists,

➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

Version: A 279
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3.181 VS_RDI
Meaning

The far end fault indication alarm of the MPLS-TP virtual path. This alarm occurs
when the local end VS layer receives the set CCM messages of the RDI field.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

The VS_RDI information is transmitted by the faulty MEP. Receiving the VS_RDI
information indicates the receiving of the remote equipment is faulty, and the
unidirectional service is interrupted.

Possible cause

u A physical fault exists in the receive end of the opposite end equipment,
including the card and line fault.

u The service configuration transmitted by the local end does not match the far
end configuration, including MEG-ID and MEP-ID.

Handling procedure

1. Enter the OTNM2000 to check the VS_RDI alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the alarms such as VS_AIS, VS_MMG, VS_UNM exist at the
receive end of the opposite end equipment.

4 If yes, eliminate the opposite end fault. After this operation, if the VS_RDI
alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

280 Version: A
 3 Alarm Handling

3.182 VS_SD
Meaning

The signal degradation alarm of the MPLS-TP virtual section. This alarm occurs
when the packet loss rate of the VS layer signal is higher than VS_SD (0 to 65535)
and lower than VS_SF (0 to 65535).

Alarm level

Major alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

The VS layer performance degrades, and the packet loss rate is lower.

Possible cause

u The OAM configuration of the VS layer on both sides of the line is not
consistent.

u The setting of the VS_SF (0 to 65535) and the VS_SD(0 to 65535) is not
appropriate.

u The other alarm occurs in the VS layer, such as VS_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VS_SD alarm.

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SF (0 to 65535) and the VS_SD
(0 to 65535) is correct.

3. If the alarm persists, check whether the OAM configuration of the VS layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

Version: A 281
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.183 VS_SF
Meaning

The signal failure alarm of the MPLS-TP virtual section. This alarm occurs when the
packet loss rate of the VS layer signal is higher than the VS_SF (0 to 65535).

Alarm level

Major alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

The VS layer performance degrades, and the packet loss rate is higher.

Possible cause

u The OAM configuration of the VS layer on both sides of the line is not
consistent.

u The setting of the VS_SF (0 to 65535) is not appropriately.

u The other alarm occurs in the VS layer, such as VS_LOC.

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VS_SF alarm.

282 Version: A
 3 Alarm Handling

2. Enter the Pm-Threshold-Config tab of the card configuration GUI of the XSJ2
card; check and ensure the setting of the VS_SD (0 to 65535) is appropriate.

3. If the alarm persists, check whether the OAM configuration of the VS layer on
both sides of the line is consistent in the OTNM2000, and especially whether
the CV frame transmission rate matches.

4. If the alarm persists, check whether the physical link is well connected; if not,
reconnect the optical fiber or clean the optical module.

5. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

6. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

3.184 VS_UNM
Meaning

The MPLS-TP virtual section unexpected maintenance entity alarm. The alarm
occurs when the MEP receives the mismatched MEP-ID.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

When the VS_UNM alarm is generated, the OAM of the alarmed VS layer cannot
operate normally.

Possible cause

The MEG-ID configuration of the OAM of the VS layer local end does not match that
of the far end.

Version: A 283
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VS_UNM alarm.

2. Check whether the MEP-ID configuration on the far end is consistent with that
of the local end. Check the MEP configuration of the VS OAM in the
corresponding item of the alarmed line in the Demanded-OAM-Config tab in
the card configuration GUI.

4 If yes, ➔ Step 3.

4 If not, modify the MEP-ID information of the far end to be consistent with
that of the local end. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.185 VS_UNP
Meaning

The time interval mismatch alarm of the MPLS-TP virtual section. This alarm will be
generated when the receiving frequency of the CV frame is different from the
expectation.

Alarm level

Minor alarm

Relevant card

XGJ1, GSJ2, XSJ2, XSJ3

Influence on the system

When the VS_UNP alarm is generated, the OAM of the alarmed VS layer cannot
operate normally.

Possible cause

The transmission period of the CV frame configured by the VS layer at the local end
is inconsistent with that of the far end.

284 Version: A
 3 Alarm Handling

Handling procedure

1. Enter the OTNM2000 to check the VS_UNP alarm and confirm the information
such as the NE or line that generates the alarm.

2. Check whether the CV frame transmission period on the local end of the
alarmed line is consistent with that of the far end. Check the CV frame
transmission period in the corresponding item of the alarmed line in the
Demanded-OAM-Config tab in the card configuration GUI.

4 If yes, ➔ Step 3.

4 If not, modify the transmission period configuration of the CV frame to

ensure it is consistent with that of the far end. It is recommended to be set
to 3.33ms. If the alarm persists, ➔ Step 3.

3. Please contact FiberHome after-sales maintenance engineer.

3.186 VSLB_LOS
Meaning

The loopback signal time-out alarm of the MPLS-TP virtual section.

Alarm level

Prompt alarm

Relevant card

GSJ2, XSJ2, XSJ3

Influence on the system

The loopback test will fail and the line cannot work normally.

Possible cause

The loopback frame configuration (LB) in the OAM management of the VS layer is
enabled. The local end transmits the OAM LBM messages and expects that the far
end returns the OAM LBR messages. This alarm occurs if the OAM LBR messages
are not returned when the timer expires.

Version: A 285
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Enter the OTNM2000 to check the information such as the NE or line that
generates the VPLB_LOS alarm.

2. Enter the OTNM2000 to check whether the transmitting of the NE loopback

frame at the opposite end is enabled. The loopback frame configuration is in
the Demanded-OAM-Config tab of the clock and cross-connect card.

3. If the alarm persists, check whether the optical fiber and the physical link from
the local end to the far end is connected normally.

4. If the alarm persists, check whether the fault of other bearers exists. Eliminate
the fault caused by the configuration inconsistency and the protocol operation
abnormality.

5. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

286 Version: A
4 Performance Handling

The following introduces the information related to the handling of the performance
event, including explanations, possible causes and handling procedures.

ALIGNMENT

ANNOUNCE_RX

ANNOUNCE_RX_ERR

ANNOUNCE_TX

BAK_5V

BBE

BBE_HP

BBE_LP

BBE_MS

BBE_RS

BOARD_TEMP

CONTEXT_EARLY_PKTS

CONTEXT_LATE_PKTS

CONTEXT_LOSS_PKTS

CONTEXT_MALFORMED_PKTS

CONTEXT_MISORDERDROP_PKTS

CONTEXT_OVERRUN_PKTS

CONTEXT_REORDER_PKTS

Version: A 287
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

CONTEXT_RX_PKTS

CONTEXT_TX_PKTS

CONTEXT_UNDERRUN_PKTS

CRC_ERR

CSES_HP

CSES_LP

CSES_MS

CSES_RS

DELAY_REQ_RX

DELAY_REQ_RX_ERR

DELAY_REQ_TX

DELAY_RESP_RX

DELAY_RSP_RX_ERR

DELAY_RESP_TX

E1_BBE

E1_ES

E1_HDB3_ERR

E1_SES

E1_UAS

ES

ES_HP

ES_LP

288 Version: A
 4 Performance Handling

ES_MS

ES_RS

FAN_CTRM

FAN_HTEMP

FE_CSES_HP

FE_CSES_LP

FE_CSES_MS

FE_ES_HP

FE_ES_LP

FE_ES_MS

FE_SES_HP

FE_SES_LP

FE_SES_MS

FOLLOW_UP_RX

FOLLOW_UP_RX_ERR

FOLLOW_UP_TX

FRAGMENT

IOP/IOP.

JABBER

LASER_BIAS

LASER_DIS

LASER_TEMP

Version: A 289
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

LASER_LEN

OFS_RS

OOP

POWER

PACKDELAY_NS

PACKDELAY_S

PACLDELAYVAR_NS

PACLDELAYVAR_S

PACKLOSR_FAR

PACKLOSR_NEAR

PJEN_HP

PJEP_HP

REI_HP

REI_LP

REI_MS

RPJEN_AU

RPJEP_AU

RX_BCAST

RX_BDPK

RX_BYTES./RX_BYTES

RX_CRC_ERR

RX_DROP

290 Version: A
 4 Performance Handling

RX_FLOW

RX_FILTER_DROP

RX_GDPK

RX_GFP

RX_GFP_ERR

RX_MCAST

RX_OF_DROP

RX_OTHER_ERR

RX_PACKS

RX_PACKS_1024_TO_1518

RX_PACKS_1519_TO_MAX

RX_PACKS_512_TO_1023

RX_PACKS128TO255

RX_PACKS256TO511

RX_PACKS64

RX_PACKS65TO127

RX_PAUSE

RX_PKTS

SES

SES_HP

SES_LP

SES_MS

Version: A 291
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

SES_RS

SMART_FAN_L

STAT_OSZ

STAT_USZ

SYNC_RX

SYNC_RX_ERR

SYNC_TX

TEMP

TPJEN_AU

TPJEP_AU

TX_BCAST

TX_BDPK

TX_BYTES./TX_BYTES

TX_FLOW

TX_GFP

TX_MCAST

TX_NONUCAST_PACKS

TX_PACKS

TX_PACKS_1024_TO_1518

TX_PACKS_1519_TO_MAX

TX_PACKS_512_TO_1023

TX_PACKS128TO255

292 Version: A
 4 Performance Handling

TX_PACKS256TO511

TX_PACKS64

TX_PACKS65TO127

TX_PAUSE

TX_UCAST

UAS

UAS_HP

UAS_LP

UAS_MS

UAS_RS

VC_RX_CV

VC_TX_CV

VP_RX_CV

VP_TX_CV

Version: A 293
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.1 ALIGNMENT
Meaning

The statistics of the ALIGNMENT packets (frame alignment error). In Ethernet, any
packet whose length is not an integer multiple of 8 bytes is called the ALIGNMENT
packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, S1J2

Influence on the system

The ALIGNMENT packet is the abnormal Ethernet data packet. When the
ALIGNMENT packets appear successively, the transmitted data will fail.

Possible cause

Normal count for counting and reporting the number of ALIGNMENT packets.

Handling procedure

Check and update the card software program and eliminate the transmission
collision at the local and far ends.

4.2 ANNOUNCE_RX
Meaning

The count of ANNOUNCE packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

294 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the total number of the ANNOUNCE
packets received.

Handling procedure

Normal count. No handling is needed.

4.3 ANNOUNCE_RX_ERR
Meaning

The count of error ANNOUNCE packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

The service quality degrades when the ANNOUNCE_RX_ERR appears

continuously.

Possible cause

Normal count for the error ANNOUNCE packets received.

Handling procedure

1. Access the OTNM2000 to check the ANNOUNCE_RX_ERR performance and

confirm the information such as the NE or line that generates the performance
event.

2. Check and ensure the cable connection of the line side at the local end is
correct.

3. Check whether the ANNOUNCE parameter at the local end is consistent with
that at the far end.

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

Version: A 295
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.4 ANNOUNCE_TX
Meaning

The count of the ANNOUNCE packets transmitted.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the ANNOUNCE
packets transmitted.

Handling procedure

Normal count. No handling is needed.

4.5 BAK_5V
Meaning

The standby 5V power voltage is abnormal.

Relevant card

NMUJ1

Influence on the system

When the main power fails, if the standby 5V power voltage is abnormal, the power
supply will not work normally, which will influence the card operation.

Possible cause

The voltage of the external standby power supply is over-low.

296 Version: A
 4 Performance Handling

Handling procedure

Check whether the BAK_5V_FAIL alarm occurs simultaneously.

u If no BAK_5V_FAIL alarm exists, no handling is needed.

u If the BAK_5V_FAIL alarm exists, check whether the voltage of the external
standby power supply is over-low; if yes, adjust the voltage to a higher value.

4.6 BBE
Meaning

The count of background errored seconds.

Relevant card

E1J1

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exists near the equipment.

4 The heat dissipation of the equipment is poor, causing the working

temperature over-high.

u Equipment cause

Version: A 297
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The signal attenuation at the Rx side of the E1 card is over-high.

4 The Tx end or the Rx end of the E1 card is faulty.

4 The clock synchronization performance is degraded.

4 The fan fails.

4 The E1 card fails or its performance degrades.

Handling method

See E1_BBE for handling the performance event.

4.7 BBE_HP
Meaning

The background block error of the higher order path. Count the background block
error detected in the higher order path in the Rx side at the local end.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the BBE_HP is a non-zero value, the bit errors are detected in the
higher order path. The bigger the BBE_HP count is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The higher order path error is detected by monitoring the B3 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

298 Version: A
 4 Performance Handling

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the overbent pigtail, transmission cable
degradation and over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal and it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance degrades.

Handling procedure

1. Access the OTNM2000 to check the BBE_HP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as the equipment room

environment, the input voltage of the external power, the fiber and cable
connection and the fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

Version: A 299
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.8 BBE_LP
Meaning

The background block error of the lower order path. Count the background block
error detected in the lower order path in the Rx side at the local end.

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the BBE_LP is a non-zero value, bit errors are detected in the lower
order path and a fault exists between the far end transmitter and the local end
receiver. The bigger the BBE_LP count is, the more bit errors exist. A small quantity
of bit errors have little influence on the system while a large quantity of bit errors
influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the first two bits of the V5 byte.
The reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

300 Version: A
 4 Performance Handling

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation at the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the BBE_LP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

Version: A 301
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.9 BBE_MS
Meaning

The background block error of the multiplex section. Count the background block
error detected in the multiplex section in the Rx side at the local end.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the BBE_MS is a non-zero value, the bit errors are detected in the
multiplex section. The bigger the BBE_MS count is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The multiplex section error is detected by monitoring the B2 byte. The reasons of
this performance event may be:

u Environmental factors

302 Version: A
 4 Performance Handling

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation at the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the BBE_MS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

Version: A 303
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card on the local or far end by loopback if practical and
replace it with an identical spare one (see CiTRANS 660 High-capacity MPLS-
TP Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.10 BBE_RS
Meaning

The background block error of the regenerator section. Count the background block
error detected in the regenerator section in the Rx side at the local end.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the BBE_RS is a non-zero value, the bit errors are detected in the
regenerator section. The bigger the BBE_RS count is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The regenerator section error is detected by monitoring the B1 byte. The reasons of
this performance event may be:

u Environmental factors

304 Version: A
 4 Performance Handling

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation at the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the BBE_RS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

Version: A 305
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card on the local or far end by loopback if practical and
replace it with an identical spare one (see CiTRANS 660 High-capacity MPLS-
TP Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.11 BOARD_TEMP
Meaning

The card temperature. This performance reports the highest temperature of the
current card.

Relevant card

S1O1, XCUJ2, XCUJ4, S1J1, S1J2, S1J4

Influence on the system

The BOARD_TEMP performance indicates the highest temperature of the current

card. The normal card temperature will not influence the system. When the
temperature threshold-crossing occurs, the TEMP_TCT alarm is generated. User
should handle it in a timely manner, otherwise the bit error may occur or even the
card may be damaged.

Possible cause

The BMU of the card reports the monitored highest temperature of the current card
to the OTNM2000.

306 Version: A
 4 Performance Handling

Handling procedure

Check whether the TEMP_TCT alarm is generated simultaneously.

u If yes, no handling is needed and the operation ends.

u If not, see the previous contents in the manual for handling the TEMP_TCT
alarm.

4.12 CONTEXT_EARLY_PKTS
Meaning

The number of early packets received by the link.

Relevant card

E1J1, E1J2, S1J1, S1J2

Influence on the system

When the number of early packets received by the link increases continuously, the
service transmission quality is degraded.

Possible cause

Normal count for counting and reporting the number of the early packets received by
the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

Version: A 307
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.13 CONTEXT_LATE_PKTS
Meaning

The number of late packets received by the link.

Relevant card

E1J1, E1J2, S1J1, S1J2

Influence on the system

When the number of late packets received by the link increases continuously, the
service transmission quality is degraded.

Possible cause

Normal count for counting and reporting the number of the late packets received by
the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.14 CONTEXT_LOSS_PKTS
Meaning

The number of the lost packets received on the link.

Relevant card

S1O1, E1J1, E1J2, S1J1, S1J2, S1J4

308 Version: A
 4 Performance Handling

Influence on the system

When the number of the lost packets received by the link increases continuously,
the service transmission quality is degraded severely.

Possible cause

Normal count for counting and reporting the lost packets received by the link.

Handling procedure

1. Check and remove the physical link fault alarm at the network side.

2. If the performance count is still increasing, check and handle the OAM-related
alarm in the equipment.

3. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.15 CONTEXT_MALFORMED_PKTS
Meaning

The number of the malformed packets received on the link.

Relevant card

S1O1, S1J4

Influence on the system

When the number of malformed packets received by the link increases continuously,
the service transmission quality is degraded.

Possible cause

Normal count for counting and reporting the malformed Rx packets on the link.

Version: A 309
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.16 CONTEXT_MISORDERDROP_PKTS
Meaning

The number of the disordered packet loss on the link.

Relevant card

S1O1, S1J4

Influence on the system

When the number of disordered packet loss on the link increases continuously, the
service transmission quality is degraded.

Possible cause

Normal count for counting and reporting the disordered packet loss on the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

310 Version: A
 4 Performance Handling

4.17 CONTEXT_OVERRUN_PKTS
Meaning

The number of the overflow packets received on the link.

Relevant card

S1J4, S1O1

Influence on the system

When the number of overflow packets received by the link increases continuously,
the service transmission quality is degraded.

Possible cause

Normal count for counting and reporting the number of the overflow packets
received by the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.18 CONTEXT_REORDER_PKTS
Meaning

The number of the reordered packet received on the link.

Relevant card

S1O1, S1J4

Version: A 311
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

When the number of reordered packets received by the link increases continuously,
the service transmission quality degrades.

Possible cause

Normal count for counting and reporting the number of the reordered packets
received by the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.19 CONTEXT_RX_PKTS
Meaning

The number of the packets received by the link.

Relevant card

S1O1, E1J1, E1J2, S1J1, S1J2, S1J4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of the packets received by the
link.

Handling procedure

Normal count. No handling is needed.

312 Version: A
 4 Performance Handling

4.20 CONTEXT_TX_PKTS
Meaning

The number of the packets transmitted by the link.

Relevant card

S1O1, E1J1, E1J2, S1J1, S1J2, S1J4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the packets transmitted
by the link.

Handling procedure

Normal count. No handling is needed.

4.21 CONTEXT_UNDERRUN_PKTS
Meaning

The number of empty packets inserted in the link.

Relevant card

S1O1, E1J1, E1J2, S1J1, S1J2, S1J4

Influence on the system

When the number of empty packets inserted in the link increases continuously, the
service transmission quality degrades severely.

Version: A 313
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

Normal count for counting and reporting the number of empty packets inserted in
the link.

Handling procedure

1. Check the configuration data of the clock and cross-connect card and the
relevant line card to ensure the configuration is correct and the data is not
congested.

2. If the performance count is still increasing, please contact FiberHome after-

sales maintenance engineer.

4.22 CRC_ERR
Meaning

The number of the CRC check errors. The CRC (Cyclical Redundancy Check) can
perform strong error detection capability with simple algorithm.

Relevant card

XSJ2, XSJ3, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, E1J1, E1J2, S1J1, S1J2, S1J4

Influence on the system

When the CRC-ERR occurs continuously and exceeds the threshold, the service
quality is degraded.

Possible cause

Normal count for counting and reporting the number of CRC check error packets. If
the CRC_ERR count is increasing, the reasons may be:

u The working modes (auto negotiation mode and 100M/1000M full duplex link
mode) of the cards at both ends are inconsistent.

u The optical fiber of the Ethernet optical interface is contaminated or degraded.

u The network cable of the Ethernet electrical interface is degraded.

u The hardware (optical module or equipment) of the far end is faulty.

314 Version: A
 4 Performance Handling

Handling procedure

1. Check whether the CRC_ERR alarm is generated simultaneously.

4 No CRC_ERR alarm exists. No handling is needed.

4 The CRC_ERR alarm exists. ➔ Step 2.

2. Check whether the Global_Config tab is in the card configuration.

4 If yes, access the Global_Config tab to modify the CRC-Err-Limit. If the

alarm persists, ➔ Step 3.

4 If not, ➔ Step 3.

3. Check whether the working modes (auto negotiation mode and 100M/1000M
full duplex link mode) of the cards on both ends are consistent; if not, modify
the configuration.

4. Check whether the cable connection of the relevant cards is normal; if not,
eliminate the cable and connection fault.

4 Check whether the Rx optical power of the Ethernet optical interface is

normal. If the optical fiber exceeds the normal range, see IOP_LOW/
IOP_LOW. and IOP_HIGH/IOPM_HIGH. for handling alarms.

4 Replace the network cable of the Ethernet electrical interface.

5. Check whether the clock and cross-connect card is reset in the OTNM2000. If
yes, check the corresponding alarm and performance event after five to ten
minutes.

6. If the alarm persists, the optical module or the equipment at the far end fails.
Replace the optical module or the equipment.

7. If the alarm persists, please contact FiberHome after-sales maintenance

engineer.

4.23 CSES_HP
Meaning

CSES_HP : the continuous severely errored second of the higher order path.

Version: A 315
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the CSES_HP is a non-zero value, the bit errors exist in the higher
order path. The bigger the CSES_HP count is, the more bit errors exist. A small
quantity of bit errors have little influence on the system while a large quantity of bit
errors influence the service transmission quality.

Possible cause

The higher order path error is detected by monitoring the B3 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

316 Version: A
 4 Performance Handling

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the CSES_HP performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card on the local or far end by loopback if practical and
replace it with an identical spare one (see CiTRANS 660 High-capacity MPLS-
TP Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.24 CSES_LP
Meaning

The continuous severely errored second of the lower order path.

Version: A 317
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

S1O1, S1J4

Influence on the system

If the count of the CSES_LP performance is a non-zero value, the bit errors exist in
the lower order path. The bigger the CSES_LP count is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the first two bits of the V5 byte.
The reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

318 Version: A
 4 Performance Handling

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the CSES_LP performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.25 CSES_MS
Meaning

The continuous severely errored second of the multiplex section.

Version: A 319
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the CSES_MS performance is a non-zero value, the bit errors exist in
the multiplex section. The bigger the CSES_MS count is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The multiplex section error is detected by monitoring the B2 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

320 Version: A
 4 Performance Handling

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the CSES_MS performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card on the local or far end by loopback if practical and
replace it with an identical spare one (see CiTRANS 660 High-capacity MPLS-
TP Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.26 CSES_RS
Meaning

The continuous severely errored second of the regenerator section.

Version: A 321
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the CSES_RS performance is a non-zero value, the bit errors exist in
the regenerator section. The bigger the CSES_RS count is, the more bit errors exist.
A small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The regenerator section error is detected by monitoring the B1 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

322 Version: A
 4 Performance Handling

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the CSES_RS performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.27 DELAY_REQ_RX
Meaning

The count of the DELAY_REQ packets received.

Version: A 323
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of the total received packets.

Handling procedure

Normal count. No handling is needed.

4.28 DELAY_REQ_RX_ERR
Meaning

The count of error DELAY_REQ packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

The service quality degrades when the DELAY_REQ_RX_ERR appears

continuously.

Possible cause

Normal count. The count of the error DELAY_REQ packets received.

Handling procedure

1. Access the OTNM2000 to check the ANNOUNCE_RX_ERR performance and

confirm the information such as the NE or line that generates the performance
event.

324 Version: A
 4 Performance Handling

2. Check and ensure the cable connection of the line side at the local end is
correct.

3. Check whether the DELAY_REQ parameter of the local end is consistent with
that of the far end.

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

4.29 DELAY_REQ_TX
Meaning

The count of the DELAY_REQ packets transmitted.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of packets transmitted.

Handling procedure

Normal count. No handling is needed.

4.30 DELAY_RESP_RX
Meaning

The count of DELAY_RESP packets received.

Relevant card

XSJ2, GSJ2

Version: A 325
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the packets received.

Handling procedure

Normal count. No handling is needed.

4.31 DELAY_RSP_RX_ERR
Meaning

The count of error DELAY_RSP packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

The service quality degrades when the DELAY_RSP_RX_ERR appears

continuously.

Possible cause

Normal count. The count of error DELAY_RSP packets received.

Handling procedure

1. Access the OTNM2000 to check the DELAY_RSP_RX_ERR performance and

confirm the information such as the NE or line that generates the performance
event.

2. Check and ensure the cable connection at the local line side is correct.

3. Check whether the DELAY_RSP parameter of the local end is consistent with
that of the far end.

326 Version: A
 4 Performance Handling

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

4.32 DELAY_RESP_TX
Meaning

The count of DELAY_RESP packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of transmitted packets.

Handling procedure

Normal count. No handling is needed.

4.33 E1_BBE
Meaning

The count of the E1 background errored block.

Relevant card

E1J2

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the alarm caused by a large quantity of errors.

Version: A 327
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing over-high working

temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance is degraded.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Handling procedure

1. Check and eliminate external causes, such as poor grounding, over-high

working temperature, interference sources.

2. Test whether the E1 signal transmitted by the far end is normal with the error
detector; if not, eliminate the signal source transmission fault.

3. If the performance event still exists, check and ensure the E1 interface is well-
connected.

4. If the performance event persists, reset or plug and unplug the E1 card to see
whether the performance event is removed.

5. If the performance event persists, switch the synchronization reference source

of the clock synchronization to see whether the performance event is removed.

6. If the performance event persists, replace the E1 card (see CiTRANS 660
High-capacity MPLS-TP Platform Troubleshooting Guide) to see whether the
performance event is removed.

7. If the performance event persists, please contact FiberHome after-sales

maintenance engineer.

328 Version: A
 4 Performance Handling

4.34 E1_ES
Meaning

The count of E1 errored seconds.

Relevant card

E1J2

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing over-high working

temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance degrades.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Version: A 329
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

See E1_BBE for handling the performance event.

4.35 E1_HDB3_ERR
Meaning

The count of HDB3 errors.

Relevant card

E1J1, E1J2

Influence on the system

If the HDB3 errors occur continuously, the quality of the service transmission is
degraded.

Possible cause

Normal count for counting and reporting the number of the HDB3 errors.

Handling procedure

See E1_BBE for handling the performance event.

4.36 E1_SES
Meaning

The count of E1 severely errored second. The severely errored second refers to a
one-second period that contains over 30% errored blocks or at least one severely
disturbed period.

Relevant card

E1J2

330 Version: A
 4 Performance Handling

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing the over-high

working temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance is degraded.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Handling method

The E1 severely errored second is the burst error caused by the pulse interference.
Users should ensure the good grounding and see E1_BBE for handling methods of
the performance event.

Version: A 331
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.37 E1_UAS
Meaning

The count of E1 unavailable seconds. The E1_UAS performance event will be

reported when ten E1_SESs occur continuously.

Relevant card

E1J2

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

Possible cause

Normal count for counting and reporting the unavailable seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing the over-high

working temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance is degraded.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

332 Version: A
 4 Performance Handling

Handling procedure

See E1_BBE for handling the performance event.

4.38 ES
Meaning

The count of E1 errored seconds.

Relevant card

E1J1

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing the over-high

working temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance is degraded.

Version: A 333
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Handling procedure

See E1_BBE for handling the performance event.

4.39 ES_HP
Meaning

The errored second of the higher order path.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

If the count of the ES_HP performance is a non-zero value, the bit errors exist in the
higher order path. The bigger the ES_HP count is, the more bit errors exist. A small
quantity of bit errors have little influence on the system while a large quantity of bit
errors influence the service transmission quality.

Possible cause

The higher order path error is detected by monitoring the B3 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

334 Version: A
 4 Performance Handling

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the ES_HP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

Version: A 335
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.40 ES_LP
Meaning

The errored second of the lower order path.

Relevant card

S1O1, S1J1, S1J4

Influence on the system

If the count of the ES_LP performance is a non-zero value, the bit errors exist in the
lower order path. The bigger the ES_LP count is, the more bit errors exist. A small
quantity of bit errors have little influence on the system while a large quantity of bit
errors influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the first two bits of the V5 byte.
The reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

336 Version: A
 4 Performance Handling

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the ES_LP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

Version: A 337
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.41 ES_MS
Meaning

The errored second of the multiplex section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

If the count of the ES_MS performance is a non-zero value, the bit errors exist in the
multiplex section. The bigger the ES_MS count is, the more bit errors exist. A small
quantity of bit errors have little influence on the system while a large quantity of bit
errors influence the service transmission quality.

Possible cause

The multiplex section error is detected by monitoring the B2 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

338 Version: A
 4 Performance Handling

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the BBE_MS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

Version: A 339
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.42 ES_RS
Meaning

The errored second of the regenerator section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

If the count of the ES_RS performance is a non-zero value, the bit errors exist in the
regenerator section. The bigger the ES_RScount is, the more bit errors exist. A
small quantity of bit errors have little influence on the system while a large quantity
of bit errors influence the service transmission quality.

Possible cause

The regenerator section error is detected by monitoring the B1 byte. The reasons of
this performance event may be:

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

340 Version: A
 4 Performance Handling

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation in the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the ES_RS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

Version: A 341
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.43 FAN_CTRM
Meaning

The intelligent fan control mode can be set in the EMU_Special_Config tab of the
NMUJ1 card in the OTNM2000.

Relevant card

NMUJ1

Influence on the system

None.

Possible cause

The current control mode of the intelligent fan can be displayed in real time.

Handling procedure

Normal performance event. No handling is needed.

4.44 FAN_HTEMP
Meaning

The highest temperature in the fan area.

Relevant card

NMUJ1

342 Version: A
 4 Performance Handling

Influence on the system

If the highest temperature value in the fan area does not exceed the threshold, it has
little influence on the system; while if it does, it will bring the system into the high-risk
status. The bit errors and service interruption will occur if the equipment operates in
this condition for a long time. Users should handle these faults in a timely manner.

Possible cause

u The upper temperature threshold is set inappropriately.

u The fan stops working or too much dust is on the anti-dust screen.

u The cooling facility in the equipment is faulty, causing the over-high ambient
temperature.

Handling procedure

1. Check the temperature upper limit threshold and the current card working
temperature in the alarmed NMUJ1 card configuration GUI and the current
performance GUI, so as to ensure the temperature upper limit threshold is set
appropriately.

2. Check and eliminate the fan unit fault.

3. Check whether too much dust is in the anti-dust screen, causing the air cooling
problem. If yes, clean the anti-dust screen.

4. Check whether the equipment working ambient temperature is normal. If not,

check whether the cooling facility in the equipment room is faulty. Ensure the
ambient temperature is normal.

5. If the performance is still abnormal, please contact FiberHome after-sales

maintenance engineer.

4.45 FE_CSES_HP
Meaning

The remote continuous severely errored second of the higher order path.

Version: A 343
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, XGJ1 S1O1 S1J4

Influence on the system

If the count of the FE_CSES_HP is a non-zero value, the higher order path errors
are detected in the Rx side at the far end. The bigger the FE_CSES_HP count is,
the more bit errors exist. A small quantity of bit errors have little influence on the
system while a large quantity of bit errors influence the service transmission quality.

Possible cause

The higher order path error at the far end is detected by monitoring the G1 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation in the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

344 Version: A
 4 Performance Handling

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_CSES_HP performance and confirm

the NE or line at the local and far ends that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

Version: A 345
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.46 FE_CSES_LP
Meaning

The remote continuous severely errored second of the lower order path.

Relevant card

S1O1, S1J4

Influence on the system

If the count of the FE_CSES_LP is a non-zero value, the lower order path errors are
detected in the Rx side at the far end. The bigger the FE_CSES_LP count is, the
more bit errors exist. A small quantity of bit errors have little influence on the system
while a large quantity of bit errors influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the third bit of the V5 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

346 Version: A
 4 Performance Handling

4 The signal attenuation in the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_CSES_LP performance and confirm

the NE or line that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

Version: A 347
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.47 FE_CSES_MS
Meaning

The remote continuous severely errored second of the multiplex section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J4

Influence on the system

If the count of the FE_CSES_MS is a non-zero value, the multiplex section errors
are detected in the Rx side at the far end. The bigger the FE_CSES_LP count is,
the more bit errors exist. A small quantity of bit errors have little influence on the
system while a large quantity of bit errors influence the service transmission quality.

Possible cause

The remote error of the multiplex section is detected by monitoring the M1 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

348 Version: A
 4 Performance Handling

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation in the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_CSES_MS performance and confirm

the NE or line on the local and far ends that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

Version: A 349
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.48 FE_ES_HP
Meaning

The remote errored second of the higher order path.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J4

Influence on the system

If the count of the FE_ES_HP is a non-zero value, the higher order path errors are
detected in the Rx side at the far end. The bigger the FE_ES_HP count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a large quantity of bit errors influence the service transmission quality.

Possible cause

The higher order path error at the far end is detected by monitoring the G1 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

350 Version: A
 4 Performance Handling

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation in the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx side of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_ES_HP performance and confirm the
NE or line at the local and far ends that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

Version: A 351
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.49 FE_ES_LP
Meaning

The remote errored second of the lower order path.

Relevant card

S1O1, S1J4

Influence on the system

If the count of the FE_ES_LP is a non-zero value, the lower order path errors are
detected in the Rx side at the far end. The bigger the FE_ES_LP count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a large quantity of bit errors influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the third bit of the V5 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

352 Version: A
 4 Performance Handling

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation on the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx side of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_ES_LP performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors on the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

Version: A 353
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.50 FE_ES_MS
Meaning

The remote errored second of the multiplex section.

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the FE_ES_MS is a non-zero value, the multiplex section errors are
detected on the receiving side of the far end. The bigger the FE_ES_MS count is,
the more bit errors exist. A small quantity of bit errors have little influence on the
system while a large quantity of bit errors influence the service transmission quality.

Possible cause

The remote error of the multiplex section is detected by monitoring the M1 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

354 Version: A
 4 Performance Handling

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation in the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_ES_MS performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

Version: A 355
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.51 FE_SES_HP
Meaning

The remote severely errored second of the higher order path.

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the FE_SES_HP is a non-zero value, the higher order path errors are
detected in the Rx side at the far end. The bigger the FE_SES_HP count is, the
more bit errors exist. A small quantity of bit errors have little influence on the system
while a large quantity of bit errors influence the service transmission quality.

Possible cause

The higher order path error at the far end is detected by monitoring the G1 byte. The
reasons of this performance event may be:

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

356 Version: A
 4 Performance Handling

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors.

4 The signal attenuation on the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end of the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_SES_HP performance and confirm

the NE or line on the local and far ends that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

Version: A 357
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.52 FE_SES_LP
Meaning

The remote severely errored second of the lower order path.

Relevant card

S1O1, S1J4

Influence on the system

If the count of the FE_SES_LP is a non-zero value, the lower order path errors are
detected at the Rx side of the far end. The bigger the FE_SES_LP count is, the
more bit errors exist. A small quantity of bit errors have little influence on the system
while a large quantity of bit errors influence the service transmission quality.

Possible cause

The lower order path error is detected by monitoring the third bit of the V5 byte. The
reasons of this performance event may be:

u Environmental factors

358 Version: A
 4 Performance Handling

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation on the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The card in the Tx side at the local end is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_SES_LP performance and confirm the
NE or line that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

Version: A 359
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.53 FE_SES_MS
Meaning

The remote severely errored second of the multiplex section.

Relevant card

XSJ2, XSJ3, S1O1, S1J4, XGJ1

Influence on the system

If the count of the FE_SES_MS is a non-zero value, the multiplex section errors are
detected in the Rx side at the far end. The bigger the FE_SES_MS count is, the
more bit errors exist. A small quantity of bit errors have little influence on the system
while a large quantity of bit errors influence the service transmission quality.

Possible cause

The remote error of the multiplex section is detected by monitoring the M1 byte. The
reasons of this performance event may be:

360 Version: A
 4 Performance Handling

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector at the far end is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Equipment factors

4 The signal attenuation on the Rx end of the card at the far end is over-high.

4 The Tx end or Rx end of the card at the far end is faulty.

4 The optical power at the far end is abnormal that it is lower than the
sensitivity or higher than the overload point.

4 The optical power at the far end is normal, but the dispersion is over-high.

4 The clock synchronization performance at the far end is poor.

4 The card at the far end fails or its performance is degraded.

4 The Tx end at the local end card is faulty.

Handling procedure

1. Access the OTNM2000 to check the FE_SES_MS performance and confirm

the NE or line that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

Version: A 361
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment at the far end is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the time synchronization of the equipment at the far end is
normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card on the local or far end by loopback if practical and
replace it with an identical spare one (see CiTRANS 660 High-capacity MPLS-
TP Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.54 FOLLOW_UP_RX
Meaning

The count of FOLLOW_UP packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the FOLLOW_UP
packets received.

362 Version: A
 4 Performance Handling

Handling procedure

Normal count. No handling is needed.

4.55 FOLLOW_UP_RX_ERR
Meaning

The count of error FOLLOW_UP packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

The service quality degrades when the FOLLOW_UP_RX_ERR appears

continuously.

Possible cause

Normal count. The count of the error FOLLOW_UP packets received.

Handling procedure

1. Access the OTNM2000 to check the FOLLOW_UP_RX_ERR performance and

confirm the information such as the NE or line that generates the performance
event.

2. Check and ensure the cable connection at the local line side is correct.

3. Check whether the FOLLOW_UP parameter of the local end is consistent with
that of the far end.

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

4.56 FOLLOW_UP_TX
Meaning

The count of FOLLOW_UP packets transmitted.

Version: A 363
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the FOLLOW_UP
packets transmitted.

Handling method

Normal count. No handling is needed.

4.57 FRAGMENT
Meaning

The count of the fragment packets. In Ethernet, the length of the normal data packet
is from 64 to 1518 bytes. Any invalid data packet whose length is less than 64 bytes
is called the fragmentation packet, including the local or remote collision fragment
and the short packet containing the invalid FCS.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, E1J1, E1J2, S1J1, S1J2

Influence on the system

The fragment packet is the abnormal Ethernet data packet. The transmitted data will
fail if the fragment packets appear successively.

Possible cause

Normal count for counting and reporting the number of the fragment packets. The
following reasons may cause the count of the FRAGMENT increasing.

u The optical fiber of the Ethernet optical interface is contaminated or degraded.

364 Version: A
 4 Performance Handling

u The network cable of the Ethernet electrical interface is degraded.

u The optical module of the Ethernet optical interface is faulty.

u The equipment is faulty.

Handling procedure

1. Check the performance through the OTNM2000 and identify the port that
generates this performance.

2. Check whether the cable connection of the relevant cards is normal; if not,
eliminate the cable connection fault or optical power fault.

4 Check whether the Rx optical power of the Ethernet optical interface is

normal; if not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for
handling alarms.

4 Replace the network cable of the Ethernet electrical interface.

3. If this performance value is still not 0, the optical module or the equipment may
be faulty. Replace the faulty component.

4. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.58 IOP/IOP.
Meaning

The Rx optical power. The IOP/IOP. is the current value of the input optical power.

Relevant card

u IOP: S1O1, ESJ2, S1J4

u IOP.: XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, S1J1, S1J2

Influence on the system

This performance event will not influence the equipment and the system. The over-
high input optical power will damage the laser while the over-low input optical power
will cause that the laser fails to detect signals normally.

Version: A 365
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

This performance event is used for monitoring the current value of the optical power
received by the laser. This performance event will be continuously exist after the
laser works normally and is issued by the OTNM2000.

Handling procedure

1. Query the specifications of the corresponding optical interface to check the

normal range of the Rx power of the optical interface.

4 If the Rx optical power of the laser is within the normal range, no handling
is needed.

4 If the Rx optical power of the laser exceeds the threshold, check whether
the IOP_HIGH alarm and the IOP_LOW alarm exist simultaneously. If yes,
see methods in IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for
handling alarms.

2. If the Rx optical power is still abnormal, please contact FiberHome after-sales

maintenance engineer.

4.59 JABBER
Meaning

The count of the jabbers packets (timeout transmission). In Ethernet, the length of
the normal data packet is from 64 to1518 bytes. The data packet whose length
exceeds 1518 bytes containing the invalid FCS data is called the Jabbers packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, E1J1, E1J2, S1J1, S1J2

Influence on the system

The Jabbers packet is abnormal Ethernet data packet. When the Jabbers packets
appear successively, the transmitted data will fail.

366 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the number of the Jabbers packets. The
following reasons may cause the count of the Jabbers increasing.

u The optical fiber of the Ethernet optical interface is contaminated or degraded.

u The network cable of the Ethernet electrical interface is degraded.

u The optical module of the Ethernet optical interface is faulty.

u The equipment is faulty.

Handling procedure

1. Check the performance through the OTNM2000 and identify the port that
generates this performance.

2. Check whether the cable connection of the relevant cards is normal; if not,
eliminate the cable connection fault or the optical power fault.

4 Check whether the Rx optical power of the Ethernet optical interface is

normal; if not, see IOP_LOW/IOP_LOW. and IOP_HIGH/IOPM_HIGH. for
handling alarms.

4 Replace the network cable of the Ethernet electrical interface.

3. If this performance value is still not 0, the optical module or the equipment may
be faulty. Replace the faulty component.

4. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.60 LASER_BIAS
Meaning

The current value of the bias current sent by the laser.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, S1O1, ESJ2, S1J4

Version: A 367
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

This performance event will not influence the equipment and the system. If the laser
bias current exceeds the threshold, the laser is not available any more. The laser
failure may cause the service interruption.

Possible cause

This performance event is used for monitoring the current value of the laser bias
current. This performance event will be continuously exist after the laser works
normally and is issued by the OTNM2000.

Handling procedure

Check whether the LASER_CCT alarm is generated simultaneously in the

OTNM2000.

u If not, no handling is needed.

u If yes, see the previous descriptions in this manual for handling the
LASER_CCT alarm.

4.61 LASER_DIS
Meaning

Laser transmission distance.

Relevant card

GSJ2, GSJ3

Influence on the system

None.

Possible cause

Normal count. The transmission distance is reported.

368 Version: A
 4 Performance Handling

Handling procedure

Check whether the LASER_CCT alarm is generated simultaneously in the

OTNM2000.

u If not, no handling is needed.

u If yes, see the previous descriptions in this manual for handling the
LASER_CCT alarm.

4.62 LASER_TEMP
Meaning

The current value of the laser operating temperature.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, S1O1, ESJ2, S1J4

Influence on the system

This performance event will not influence the equipment and the system. The over-
high or over-low laser operating temperature will cause the abnormal operation of
the laser and service interruption.

Possible cause

This performance event (physical performance) is used for monitoring the laser
operating temperature. This performance event will be continuously exist after the
laser works normally and is issued by the OTNM2000.

Handling procedure

Check whether the LASER_TCT alarm is generated simultaneously in the

OTNM2000.

u If not, no handling is needed.

u If yes, see the previous descriptions in this manual for handling the
LASER_TCT alarm.

Version: A 369
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.63 LASER_LEN
Meaning

Laser transmission distance.

Relevant card

GSJ2, GSJ3

Influence on the system

None.

Possible cause

Normal count. The wavelength is reported.

Handling procedure

Check whether the LASER_CCT alarm is generated simultaneously in the

OTNM2000.

u If not, no handling is needed.

u If yes, see the previous descriptions in this manual for handling the
LASER_CCT alarm.

4.64 OFS_RS
Meaning

The out-of-frame second of the regenerator section. The out-of-frame second

means the second containing one or multiple out-of-frame events.

Relevant card

XSJ2, S1O1, S1J4

370 Version: A
 4 Performance Handling

Influence on the system

When the OFS_RS is generated, the frame alignment byte is lost, causing the
service interruption.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber loss.

4 The fiber connector is unclean or faulty.

u Equipment factors

4 The signal attenuation at the Rx end of the card is over-high.

4 The Tx end or Rx end of the card is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The clock synchronization performance is poor.

4 The card fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the OFS_RS performance and confirm the NE
or line that generates the performance event.

Version: A 371
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check whether the Rx optical power of the equipment is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 4.

4. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 5.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 5.

5. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

6. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.65 OOP
Meaning

The optical transmitting power. The OOP is the current value of the output optical
power.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, S1O1, ESJ2, S1J1, S1J2, S1J4

372 Version: A
 4 Performance Handling

Influence on the system

This performance event will not influence the equipment and the system, but the
over-high output optical power will damage the laser. While the over-low output
optical power will cause that the laser at the far end fails to detect signal normally.

Possible cause

This performance event is used for monitoring the current value of the optical power
transmitted by the laser. This performance event will be continuously exist after the
laser works normally and is issued by the OTNM2000.

Handling procedure

1. Check the specifications of the corresponding optical interface to check the

normal range of the optical Tx power.

2. If the Tx optical power of the laser is within the normal range, no handling is
needed; if it exceeds the threshold, perform the following operations until the Tx
optical power is normal.

4 In the OTNM2000 GUI, check the thresholds of the related optical

interfaces and ensure that they are set appropriately.

4 Check whether the optical fiber connector is contaminated. If yes, clean or

replace the optical fiber connector (see CiTRANS 660 High-capacity
MPLS-TP Platform Troubleshooting Guide for operations).

4 If the alarm persists, check the pigtail of the alarmed card. If the pigtail is
over bent, damaged or aged, adjust or replace it.

4 If the alarm persists, check whether the Rx optical interface of the local
card is equipped with the over-high or over-low optical attenuator; if yes,
adjust the attenuation value or replace the optical attenuator.

4 Replace with the identical optical module or replace the card.

3. If the Tx optical power of the laser is still abnormal, please contact FiberHome
after-sales maintenance engineer.

Version: A 373
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.66 POWER
Meaning

The power supply voltage of the cabinet rack.

Relevant card

NMUJ1

Influence on the system

The voltage range for the equipment normal operation is from -40V to -57V. If the
power supply voltage of the cabinet rack is over-low and the equipment power
supply is insufficient, some electronic devices can not be powered up; if the power
supply voltage of the cabinet rack is over-high, the equipment power supply function
and electronic components will be damaged.

Possible cause

The input voltage of the cabinet rack is abnormal.

Handling procedure

1. Adjust the power supply voltage of the cabinet rack to a normal range.

2. If the POWER performance value is still abnormal, please contact FiberHome

after-sales maintenance engineer.

4.67 PACKDELAY_NS
Meaning

The delay nanosecond. The PACKDELAY_NS monitors and reports the delay of the
LSP path service (unit: nanosecond).

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

374 Version: A
 4 Performance Handling

Influence on the system

The PACKDELAY_NS is the statistics of the delay of services on each layer. The
delay does not greatly influence the data service. However, for the services with
high real-time requirement such as voice and video, the larger the delay is, the
greater the service is damaged.

Possible cause

u The network bandwidth is inadequate and is blocked.

u The NEs through which the service path passes are excessive.

u The service is executing the protection switching.

Handling procedure

1. Access the OTNM2000 to check the NE or line that generates the

PACKDELAY_NS performance event.

2. Check the line where the LSP corresponding to the performance locates and
the bandwidth occupation condition of the network. If the bandwidth is
approximately fully occupied, expand the capacity of the equipment.

3. Check the NEs through which the service path passes; if the NEs are
excessive, select a new path for the service.

4. If the service is being switched, the delay value will decrease when the network
is stable.

5. If the delay time is still long, please contact FiberHome after-sales maintenance
engineer.

4.68 PACKDELAY_S
Meaning

The delay second. The PACKDELAY_S monitors and reports the delay jitter of the
LSP path service (unit: second).

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Version: A 375
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The PACKDELAY_NS measures the delay of services on each layer. The delay
does not greatly influence the data service. However, for the services with high real-
time requirement such as voice and video, the larger the delay is, the greater the
service is damaged.

Possible cause

u The network bandwidth is inadequate and is blocked.

u The NEs through which the service path passes are excessive.

u The service is executing the protection switching.

Handling procedure

1. Access the OTNM2000 to check the NE or line that generates the

PACKDELAY_S performance event.

2. Check the line where the LSP corresponding to the performance locates and
the bandwidth occupation condition of the network. If the bandwidth is
approximately fully occupied, expand the capacity of the equipment.

3. Check the NEs through which the service path passes; if the NEs are
excessive, select a new path for the service.

4. If the service is being switched, the delay value will decrease when the network
is stable.

5. If the delay time is still long, please contact FiberHome after-sales maintenance
engineer.

4.69 PACLDELAYVAR_NS
Meaning

The delay variation nanosecond. The PACLDELAYVAR_NS monitors and reports

the delay jitter of the LSP path service (unit: nanosecond).

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

376 Version: A
 4 Performance Handling

Influence on the system

The PACKDELAYVAR_NS measures the delay of services on each layer. The delay
variation does not greatly influence the data service. However, for the services with
high real-time requirement such as voice and video, the larger the delay variation is,
the greater the service is damaged.

Possible cause

u The protection switching occurs in the service path, causing the over delay
jitter.

u The network bandwidth is inadequate and is blocked.

u The NEs through which the service path passes are excessive.

Handling procedure

1. Access the OTNM2000 to check the NE or line that generates the

PACKDELAYVAR_NS performance event.

2. Wait a few minutes to check whether the delay variation is reduced.

4 If yes: the increasing of the previous PACKDELAYVAR_NS count may be

caused by the protection switch of the service path. Users do not have to
handle it after the network becomes stable.

4 If not, check the line where the LSP corresponding to the performance
locates and the bandwidth occupation condition of the network. If the
bandwidth is approximately fully occupied, expand the capacity of the
equipment.

3. If the delay variation increases continuously, check the NEs through which the
service path passes; if the NEs are excessive, select a new path for the
service.

4. If the delay variation increases continuously after the above operation, please
contact FiberHome after-sales maintenance engineer.

Version: A 377
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.70 PACLDELAYVAR_S
Meaning

The delay variation second. The PACLDELAYVAR_S monitors and reports the
delay jitter of the LSP path service (unit: second).

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

The PACKDELAYVAR_S measures the delay of services on each layer. The delay
variation does not greatly influence the data service. However, for the services with
high real-time requirement such as voice and video, the larger the delay variation is,
the greater the service is damaged.

Possible cause

u The protection switching occurs in the service path, causing the over delay
jitter.

u The network bandwidth is inadequate and is blocked.

u The NEs through which the service path passes are excessive.

Handling procedure

1. Access the OTNM2000 to check the NE or line that generates the

PACKDELAYVAR_S performance event.

2. Wait a few minutes to check whether the delay variation is reduced.

4 If yes: the increasing of the previous PACKDELAYVAR_S count may be

caused by the protection switch of the service path. Users do not have to
handle it after the network becomes stable.

4 If not, check the line where the LSP corresponding to the performance
locates and check the bandwidth occupation condition of the network. If
the bandwidth is approximately fully occupied, expand the capacity of the
equipment.

378 Version: A
 4 Performance Handling

3. If the delay variation increases continuously, check the NEs through which the
service path passes; if the NEs are excessive, select a new path for the
service.

4. If the delay variation increases continuously after the above operation, please
contact FiberHome after-sales maintenance engineer.

4.71 PACKLOSR_FAR
Meaning

The far end packet loss rate. The far end packet loss rate = (the number of the
packets transmitted by the far end to the local end - the number of the packets
received by the local end) / the number of the packets transmitted by the far end to
the local end.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

If the count of the PACKLOSER_FAR is a non-zero value, the bit errors exist in the
Rx side at the local end and a fault exists between the far end transmitter and the
local end receiver. A small quantity of bit errors have little influence on the system;
while the bigger the PACKLOSER_FAR count is, the greater the influence is on the
service transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room at the far end is beyond the
normal range from -30℃ to 55℃.

4 The humidity of the equipment room at the far end exceeds 90%.

4 The DC power voltage at the far end is of poor stability or is beyond the
normal voltage range from -40V to -57V.

4 The powerful interference sources exist near the equipment at the far end.

4 The equipment at the far end is not well grounded.

Version: A 379
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit at the far end is faulty.

4 The fiber connector is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Network factors

4 Errors exit in the network.

4 The network bandwidth is inadequate and is blocked.

u Equipment factors

4 The signal attenuation on the Rx end of the card is over-high.

4 The Tx end of the far end card or the Rx end of the local end card is faulty.

4 The clock synchronization performance of the card is poor.

4 The card at the local end and far end fails or its performance is degraded.

Handling procedure

1. Access the OTNM2000 to check the PACKLOSR_FAR performance and

confirm the NE or line that generates the performance event.

2. Check whether the environmental factors at the far end such as equipment
room environment, input voltage of the external power, fiber and cable
connection and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check the line corresponding to the performance and the bandwidth

occupation condition of the network. If the bandwidth is approximately fully
occupied, expand the capacity of the equipment.

4. Check whether the optical fiber connection and the Rx optical power of the
local end equipment is normal.

4 If yes, ➔ Step 5.

380 Version: A
 4 Performance Handling

4 If not, connect the optical fiber correctly and eliminate the optical power
fault. If the current performance value is still not 0 after this operation, ➔
Step 5.

5. Check whether the optical fiber connection and the Tx optical power of the local
end equipment is normal.

4 If yes, ➔ Step 6.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 6.

6. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

7. Check whether the clock synchronization of the equipment at the local and far
ends is normal.

4 If yes, ➔ Step 8.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 8.

8. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.72 PACKLOSR_NEAR
Meaning

The near end packet loss rate. The near end packet loss rate = (the number of the
packets transmitted by the local end to the far end - the number of the packets
received by the far end) / the number of the packets transmitted by the local end to
the far end.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Version: A 381
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If the count of the PACKLOSR_NEAR is a non-zero value, the bit errors exist in the
Rx side at the far end and a fault exists between the far end transmitter and the local
end receiver. A small quantity of bit errors have little influence on the system; while
the bigger the PACKLOSER_NEAR count is, the greater the influence is on the
service transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The powerful interference sources exist near the equipment.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The fiber connector is unclean or faulty.

4 The optical fiber faults, such as the over-bent pigtail, the transmission
cable degradation and the over-high optical fiber attenuation.

u Network factors

4 Errors exist in the network.

4 The network bandwidth is inadequate and is blocked.

u Equipment factors

4 The signal attenuation on the Rx end of the card at the far end is over-high.

4 The Tx end of local end card or the Rx end of the far end card is faulty.

4 The clock synchronization performance of the card is poor.

4 The card at the local end and far end fails or its performance is degraded.

382 Version: A
 4 Performance Handling

Handling procedure

1. Access the OTNM2000 to check the PACKLOSR_NEAR performance and

confirm the NE or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the current performance value

is still not 0 after this operation, ➔ Step 3.

3. Check the line corresponding to the performance and the bandwidth

occupation condition of the network. If the bandwidth is approximately fully
occupied, expand the capacity of the equipment.

4. Check whether the optical fiber connection and the Rx optical power of the
local end equipment is normal.

4 If yes, ➔ Step 5.

4 If not, connect the optical fiber correctly and eliminate the optical power
fault. If the current performance value is still not 0 after this operation, ➔
Step 5.

5. Check whether the optical fiber connection and the Tx optical power of the local
end equipment is normal.

4 If yes, ➔ Step 6.

4 If not, eliminate the optical power fault. If the current performance value is
still not 0 after this operation, ➔ Step 6.

6. Isolate the faulty card at the local or far end by loopback if practical and replace
it with an identical spare one (see CiTRANS 660 High-capacity MPLS-TP
Platform Troubleshooting Guide for replacement methods).

7. Check whether the clock synchronization of the equipment at the local and far
ends is normal.

4 If yes, ➔ Step 8.

4 If not, eliminate the clock fault. If the current performance value is still not 0
after this operation, ➔ Step 8.

Version: A 383
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

8. If the current performance value is still not 0, please contact FiberHome after-
sales maintenance engineer.

4.73 PJEN_HP
Meaning

The Rx negative pointer adjustment of the higher order path.

Relevant card

XSJ2, XSJ3, XGJ1

Influence on the system

The great pointer adjustment will cause the bit error of the service.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clock.

u The clock configuration is incorrect.

u The temperature of the NE or card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the PJEP_HP performance and confirm the
NE or line that generates the performance event.

384 Version: A
 4 Performance Handling

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

4 If not, replace the faulty fan and clean the anti-dust screen in a timely
manner. If the count of this performance event is still a non-zero value after
this operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after this operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one.

7. If the performance count is still a non-zero value after the operation, please
contact FiberHome after-sales maintenance engineer.

4.74 PJEP_HP
Meaning

The Rx positive pointer adjustment of the higher order path.

Version: A 385
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, XGJ1

Influence on the system

The great pointer adjustment will cause the bit error of the service.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clock.

u The clock configuration is incorrect.

u The temperature of the NE or card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the PJEP_HP performance and confirm the
NE or line that generates the performance event.

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

386 Version: A
 4 Performance Handling

4 If not, replace the faulty fan and clean the anti-dust screen in a timely
manner. If the count of this performance event is still a non-zero value after
this operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standards.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after this operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one.

7. If the performance count is still a non-zero value after the operation, please
contact FiberHome after-sales maintenance engineer.

4.75 REI_HP
Meaning

The far end bit error indication of the higher order path.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J2, S1J4

Version: A 387
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If the count of the REI_HP is a non-zero value, the higher order path errors are
detected in the Rx side at the far end. A small quantity of bit errors have little
influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the REI_HP performance and confirm the NE
or line that generates the performance event.

388 Version: A
 4 Performance Handling

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure the cable and the far end equipment is normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.76 REI_LP
Meaning

The far end bit error indication of the lower order path.

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the REI_LP is a non-zero value, the lower order path errors are
detected in the Rx side at the far end. A small quantity of bit errors have little
influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

Version: A 389
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment of far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the REI_LP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

390 Version: A
 4 Performance Handling

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.77 REI_MS
Meaning

The far end bit error indication of the multiplex section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J2, S1J4

Influence on the system

If the count of the REI_MS is a non-zero value, the multiplex section errors are
detected in the Rx side at the far end. A small quantity of bit errors have little
influence on the system while a larger quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

Version: A 391
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the REI_MS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, fiber and cable connection
and fan unit are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment is normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

392 Version: A
 4 Performance Handling

4.78 RPJEN_AU
Meaning

The Rx negative pointer adjustment of the administrative unit.

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

The great pointer adjustment will cause the bit error of the service.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clocks.

u The clock configuration is incorrect.

u The temperature of the NE or card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the RPJEN_AU performance and confirm the
NE or line that generates the performance event.

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

Version: A 393
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

4 If not, replace the faulty fan unit and clean the anti-dust screen in a timely
manner (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide). If the count of this performance event is still a
non-zero value after this operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the requirement.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after this operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

7. After the operation, If the performance count is still non-zero value, please
contact FiberHome after-sales maintenance engineer.

4.79 RPJEP_AU
Meaning

The Rx positive pointer adjustment of the administrative unit.

394 Version: A
 4 Performance Handling

Relevant card

S1O1, S1J1, S1J2, S1J4

Influence on the system

The great pointer adjustment will cause the bit error of the service.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clocks.

u The clock configuration is incorrect.

u The temperature of the NE or card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the RPJEP_AU performance and confirm the
NE or line that generates the performance event.

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

Version: A 395
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4 If not, replace the faulty fan unit and clean the anti-dust screen in a timely
manner (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide). If the count of this performance event is still a
non-zero value after this operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after this operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

7. After the operation, If the performance count is still non-zero value, please
contact FiberHome after-sales maintenance engineer.

4.80 RX_BCAST
Meaning

The number of the received broadcast packets. The data packet whose destination
MAC address is FF-FF-FF-FF-FF-FF is called the broadcast packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

396 Version: A
 4 Performance Handling

Influence on the system

All the nodes will process the broadcast packets so that excessive broadcast
packets may occupy all the node resource. Excessive broadcast packets are one of
the leading causes of the network performance degradation.

Possible cause

Normal count for counting and reporting the number of the received broadcast
packets.

Handling procedure

If the number of the broadcast packets is within the normal range, no handling is
needed; if the number is excessive, perform the following operations:

1. Check whether the loop exists; if yes, enable the STP protocol or modify the
physical link to eliminate the loop.

2. Enable the broadcast packet suppression function of the relevant port and set
the broadcast packet traffic appropriately in the Physical_Port_Config tab in
the NE configuration GUI.

3. Set VLAN for the relevant service port in the Logical_Port_Config tab of the
NE configuration GUI.

4. Analyze the broadcast packet source address with the packet capture tool and
check whether the equipment at this address is damaged or has viruses.

4.81 RX_BDPK
Meaning

The number of received error packets.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Version: A 397
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The larger the number of received error packets in a period (such as 15 minutes or
24 hours) is, the more severe the service quality degrades.

Possible cause

u The link signal is of poor quality or the misconnection occurs.

u The card at the Tx end or the Rx end is faulty.

Handling procedure

If the number of the Rx error packets is within the normal range, no handling is
needed; if the number is excessive, perform the following operations:

1. Check whether the line is incorrectly connected; if yes, reconnect the optical
fiber or reconfigure the line.

2. Check the quality of link signals. Replace the optical fiber and the network
cable, and clean the optical module.

3. Check whether the card at the Tx end or the Rx end is faulty; if yes, replace the
faulty card (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4.82 RX_BYTES./RX_BYTES
Meaning

The total number of the received bytes.

Relevant card

u RX_BYTES: XSJ3, XGJ1, XCUJ4

u RX_BYTES.: XSJ2, GSJ2, XCUJ2

Influence on the system

None.

398 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the total number of the received bytes.

Handling procedure

None.

4.83 RX_CRC_ERR
Meaning

The received Ethernet frame CRC is faulty.

Relevant card

S1O1

Influence on the system

If the count of the RX_CRC_ERR is a non-zero value, the local end receives the
CRC error packet. A great number of the CRC error packets may interrupt the
services.

Possible cause

u The cable is incorrectly connected.

u Incorrect configuration. The CRC parameter configuration at the local end and
far end is inconsistent.

Handling procedure

1. Access the OTNM2000 to check the RX_CRC_ERR performance and confirm

the information such as the NE or line that generates the performance event.

2. Check and ensure the cable connection at the local line side is correct.

3. Check whether the CRC parameter of the local end is consistent with that of the
far end.

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

Version: A 399
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.84 RX_DROP
Meaning

The number of the received packet loss.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, E1J1, E1J2, S1J1, S1J2

Influence on the system

The larger the number of received packet loss in a period (such as 15 minutes or 24
hours) is, the more severe the service quality degrades.

Possible cause

u The link signal is of poor quality or massive illegal data exists.

u The service traffic exceeds the distributed bandwidth.

u The card at the Tx end or the Rx end is faulty.

Handling procedure

If the number of the Rx packet loss is within the normal range, no handling is
needed; if the number is excessive, perform the following operations:

1. Check whether the link signal quality is poor; if yes, replace the optical fiber and
the network cable, and clean the optical module.

2. Check whether the DOS attack exists; if yes, clear the illegal data source.

3. Check whether the loop occurs; if yes, modify the configuration to eliminate the
loop.

4. Check the service configuration and whether it is necessary to re-distribute the

bandwidth.

5. Check whether the card at the Tx end or the Rx end is faulty; if yes, replace the
faulty card (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

400 Version: A
 4 Performance Handling

4.85 RX_FLOW
Meaning

The received flow.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the received flow.

Handling procedure

Normal count. No handling is needed.

4.86 RX_FILTER_DROP
Meaning

The number of filtered lost packets received.

Relevant card

ESJ1, ESJ2

Influence on the system

The count of the active loss packet has no influence on the system.

Possible cause

The unmatched data packet filtered by the layer 2 flow will be discarded.

Version: A 401
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

None.

4.87 RX_GDPK
Meaning

The received good packets.

Relevant card

ESJ1, ESJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of good packets received.

Handling procedure

Normal count. No handling is needed.

4.88 RX_GFP
Meaning

The statistics of GFP frames received.

Relevant card

S1J2

Influence on the system

None.

402 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the number of the GFP frames received.

Relevant alarm

None

Handling procedure

Normal count. No handling is needed.

4.89 RX_GFP_ERR
Meaning

The statistics of receiving GFP error frames.

Relevant card

S1J2

Influence on the system

None

Influence on the system

When the count of the RX_GFP_ERR is a non-zero value, the GFP error frame is
received at the local end and a great number of GFP error frames cause the
interruption of service channels.

Possible cause

u The optical fiber is incorrectly connected.

u Incorrect configuration. The GFP parameter configuration at the local end and
far end is inconsistent.

Version: A 403
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Access the OTNM2000 to check the RX_GFP_ERR performance and confirm

the information such as the NE or line that generates the performance event.

2. Check and ensure the optical fiber connection at the local line side is correct.

4 If yes, ➔ Step 3.

4 If not, reconnect the optical fiber. If the count of this performance event is
still a non-zero value after this operation, ➔ Step 3.

3. Check whether the GFP parameters at the local end is consistent with those at
the far end. Configure the GFP parameters in the logical port at the LP tab of
the S1O1 card configuration of the local NE in the OTNM2000.

4 If yes, ➔ Step 4.

4 If not, reconfigure the GFP parameters according to the actual project

planning and keep the GFP parameters at the local end consistent with
those of the far end. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 4.

4. Please contact FiberHome after-sales maintenance engineer.

4.90 RX_MCAST
Meaning

The number of the received multicast packets. The packet whose first byte of the
destination MAC address is an odd number is called the multicast packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

Influence on the system

Similar to the broadcast packet, all the member nodes belong to a same group
process the multicast packets, so that excessive multicast packets will cause the
network performance degradation. In general, the incidence of the multicast packet
is less than the broadcast packet.

404 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the number of the received multicast
packets.

Handling procedure

If the number of the multicast packets is within the normal range, no handling is
needed; if the number is overlarge, perform the following operations:

1. Enable the multicast packet suppression function of the relevant port and set
the multicast packet traffic appropriately in the Physical_Interface_Config tab
in the NE configuration GUI.

2. Set VLAN for the relevant service port in the Logical_Interface_Config tab of
the NE configuration GUI.

3. Analyze the multicast packet source address with the packet capture tool and
check whether the equipment at this address is damaged or is incorrectly
configured.

4.91 RX_OF_DROP
Meaning

The number of the overflow packet loss received.

Relevant card

ESJ1, ESJ2

Influence on the system

Excessive overflow packet loss will influence the service.

Possible cause

The buffer area capacity is limited. The buffer area will be full when the burst flow
occurs and the data overflow occurs.

Version: A 405
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

1. Access the OTNM2000 to check the RX_OF_DROP performance and confirm

the NE or line that generates the performance event.

2. Adjust the service bandwidth configuration and decrease the packet loss.

4.92 RX_OTHER_ERR
Meaning

The number of other errored packets received.

Relevant card

S1O1

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of the other errored packets
received.

Handling procedure

Normal count. No handling is needed.

4.93 RX_PACKS
Meaning

The total number of the received packets.

Relevant card

GSJ2, XCUJ2, XCUJ4, S1J2

406 Version: A
 4 Performance Handling

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets.

Handling procedure

Normal count. No handling is needed.

4.94 RX_PACKS_1024_TO_1518
Meaning

The total number of the received packets with 1024 to 1518 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
with 1024 to 1518 bytes.

Handling procedure

Normal count. No handling is needed.

4.95 RX_PACKS_1519_TO_MAX
Meaning

The total number of the received packets with 1519 to MAX bytes.

Version: A 407
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
with 1519 to MAX bytes.

Handling procedure

Normal count. No handling is needed.

4.96 RX_PACKS_512_TO_1023
Meaning

The total number of the received packets with 512 to 1023 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
with 512 to 1023 bytes.

Handling procedure

Normal count. No handling is needed.

408 Version: A
 4 Performance Handling

4.97 RX_PACKS128TO255
Meaning

The total number of the received packets with 128 to 255 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
with 128 to 255 bytes.

Handling procedure

Normal count. No handling is needed.

4.98 RX_PACKS256TO511
Meaning

The total number of the received packets with 256 to 511 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
with 256 to 511 bytes.

Version: A 409
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

Normal count. No handling is needed.

4.99 RX_PACKS64
Meaning

The total number of the received packets within 64 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets
within 64 bytes.

Handling procedure

Normal count. No handling is needed.

4.100 RX_PACKS65TO127
Meaning

The total number of the received packets with 65 to 127 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

410 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the total number of the received packets
with 65 to 127 bytes.

Handling procedure

Normal count. No handling is needed.

4.101 RX_PAUSE
Meaning

The number of the received PAUSE frames. The PAUSE frame is the MAC control
frame with the operation code 00-01, used to transmitting the flow control
information.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

Influence on the system

When the buffer occupation of the receiver exceeds the maximum value, users can
use the PAUSE frame to pause the transmission from the Tx equipment, so as to
prevent the packet loss caused by the buffer overflow of the receiver.

Possible cause

u The Tx packet rate exceeds the port bandwidth of the far end.

u The performance of the optical fiber (network cable) or the optical module is
degraded.

u The card is faulty.

Handling procedure

1. Lower the Tx packet rate at the local end.

2. Replace the optical fiber (network cable) or the optical module.

Version: A 411
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Replace the faulty card (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4. Please contact FiberHome after-sales maintenance engineer.

4.102 RX_PKTS
Meaning

The total number of the received packets.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, E1J1, E1J2, E1J2, S1J1, S1J4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the received packets.

Handling procedure

Normal count. No handling is needed.

4.103 SES
Meaning

The count of E1 severely errored seconds.

Relevant card

E1J1

412 Version: A
 4 Performance Handling

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
E1 signal transmission quality.

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the loss is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing over-high working

temperature.

u Equipment cause

4 The signal attenuation in the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance degrades.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Handling procedure

See the methods in E1_BBE for handling performance events .

Version: A 413
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.104 SES_HP
Meaning

The severely errored second of the higher order path. The monitoring period is one
month, and the sampling time is 1s. The second with the error rate more than 1×10 -3
is defined as the severely errored second.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

The high error rate may occur in short time on some system, which influence the
transmission quality terribly, so that the severely errored second is inducted here.

If the count of the SES_HP is a non-zero value, the higher order path severely
errors are detected in the Rx side at the far end. A small quantity of bit errors have
little influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

414 Version: A
 4 Performance Handling

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the SES_HP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.105 SES_LP
Meaning

The severely errored second of the lower order path. The monitoring period is one
month, and the sampling time is 1s. The second with the error rate more than 1×10 -3
is defined as the severely errored second.

Version: A 415
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

S1O1, S1J1, S1J4

Influence on the system

The high error rate may occur in short time on some system, which influence the
transmission quality terribly, so that the severely errored second is inducted here.

If the count of the SES_LP is a non-zero value, the lower order path severely errors
are detected in the Rx side at the far end. A small quantity of bit errors have little
influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

416 Version: A
 4 Performance Handling

u The fiber and the equipment of far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the SES_LP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.106 SES_MS
Meaning

The severely errored second of the multiplex section. The monitoring period is one
month, and the sampling time is 1s. The second with the error rate more than
1×10–3 is defined as the severely errored second.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Version: A 417
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

The high error rate may occur in short time on some system, which influence the
transmission quality terribly, so that the severely errored second is inducted here.

If the count of the SES_MS is a non-zero value, the multiplex section severely errors
are detected in the Rx side at the far end. A small quantity of bit errors have little
influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

418 Version: A
 4 Performance Handling

Handling procedure

1. Access the OTNM2000 to check the SES_MS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.107 SES_RS
Meaning

The severely errored second of the regenerator section. The monitoring period is
one month, and the sampling time is 1s. The second with the error rate more than
1×10–3 is defined as the severely errored second.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

The high error rate may occur in short time on some system, which influence the
transmission quality terribly, so that the severely errored second is inducted here.

Version: A 419
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

If the count of the SES_RS is a non-zero value, the regenerator section severely
errors are detected in the Rx side at the far end. A small quantity of bit errors have
little influence on the system while a large quantity of bit errors influence the service
transmission quality.

Possible cause

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the SES_RS performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

420 Version: A
 4 Performance Handling

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.108 SMART_FAN_L
Meaning

The intelligent fan rotating speed choice, including full speed, fast speed, slow
speed and stop.

Relevant card

NMUJ1

Influence on the system

None.

Possible cause

The system takes samples of the intelligent fan rotating speed.

Handling method

If the SMART_FAN_L is Stop, the fan is not operating. Plug and unplug the fan unit;
replace the faulty fan unit (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

Version: A 421
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.109 STAT_OSZ
Meaning

The count of the long packets. In the Ethernet, the length of the normal data packet
is between 64 and 1,518 bytes. The packet, whose length exceeds 1,518 bytes and
with valid FCS, is called the long packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, S1J1, ESJ1, ESJ2, E1J1, E1J2, S1J2

Influence on the system

Over sized packets are abnormal Ethernet packets. Excessive over sized packets
will affect the normal network operation or even cause network paralysis.

Possible cause

Normal count for counting and reporting the number of long packets.

Handling procedure

The generation of the long packet is related with the recent collisions and
interferences, such as bridge, driving fault of the interface card in the router or
software faults. Check whether the DOS attack exists and eliminate the source of
transmitting excessive illegal data.

4.110 STAT_USZ
Meaning

The count of the short packets. In the Ethernet, the length of the normal data packet
is between 64 and 1,518 bytes. The packet, whose length is less than 64 bytes and
with valid FCS, is called the short packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, S1J1, ESJ1, ESJ2, E1J1, E1J2, S1J2

422 Version: A
 4 Performance Handling

Influence on the system

The short packet is the abnormal Ethernet packet. Excessive short packets will
increase the network load, which may influence the normal operation of the network.

Possible cause

Normal count for counting and reporting the number of short packets .

Handling procedure

The generation of short packet is related with the local or remote collisions. Check
and eliminate the collisions.

4.111 SYNC_RX
Meaning

The count of SYNC packets received.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the packets received.

Handling procedure

Normal count. No handling is needed.

4.112 SYNC_RX_ERR
Meaning

The count of error SYNC packets received.

Version: A 423
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, GSJ2

Influence on the system

The service quality degrades when the SYNC_RX_ERR appears continuously.

Possible cause

Normal count for the error SYNC packets received.

Handling procedure

1. Access the OTNM2000 to check the SYNC_RX_ERR performance and confirm

the information such as the NE or line that generates the performance event.

2. Check and ensure the cable connection in the line side at the local end is
correct.

3. Check whether the SYNC parameter of the local end is consistent with that of
the far end.

4. If the performance event persists, contact after-sales maintenance engineers of

FiberHome.

4.113 SYNC_TX
Meaning

The count of SYNC packets transmitted.

Relevant card

XSJ2, GSJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of transmitted packets.

424 Version: A
 4 Performance Handling

Handling procedure

Normal count. No handling is needed.

4.114 TEMP
Meaning

The NMUJ1 card temperature.

Relevant card

NMUJ1

Influence on the system

If the card temperature does not exceed the threshold, it has no influence on the
system. If the card temperature is over-high, the system will be in a high-risk status.
Operations in this condition for a long time will cause faults such as bit errors and
service interruption, so that handling in a timely manner is required.

Possible cause

The system takes samples of the card temperature of the NMUJ1 card.

Handling procedure

1. Check whether the current working temperature of the card is threshold-

crossing.

2. Check and eliminate the fan unit fault.

3. Check whether too much dust is in the anti-dust screen, causing the air cooling
problem. If yes, clean the anti-dust screen.

4. Check whether the equipment working ambient temperature is normal. If not,

check whether the cooling facility in the equipment room is faulty. Ensure that
the ambient temperature is normal.

5. Check whether the temperature measuring chip in the card is faulty; if yes,
replace the faulty card (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

Version: A 425
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

6. Please contact FiberHome after-sales maintenance engineer.

4.115 TPJEN_AU
Meaning

AU transmitting negative pointer justification.

Relevant card

S1J1

Influence on the system

If the pointer adjustment is great, the bit error of the service will occur.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clock.

u The clock configuration is incorrect.

u The temperature of the NE or card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the TPJEP_AU performance and confirm the
NE or line that generates the performance event.

426 Version: A
 4 Performance Handling

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

4 If not, replace the faulty fan and clean the anti-dust screen in a timely
manner. If the count of this performance event is still a non-zero value after
this operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after this operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one.

7. After the operation, If the performance count is still a non-zero value, please
contact FiberHome after-sales maintenance engineer.

4.116 TPJEP_AU
Meaning

The Tx positive pointer adjustment of the administrative unit.

Version: A 427
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

S1J1

Influence on the system

If the pointer adjustment is great, the bit errors of the service will occur.

Possible cause

The pointer adjustment indicates the NEs with asynchronous clocks exist in the
network. The following reasons may cause the asynchronous clock.

u The clock configuration is incorrect.

u The temperature of the NE or the card is abnormal.

u The optical fiber is incorrectly connected.

u The quality of the external synchronization reference source is poor.

u The clock synchronization is abnormal after the line switch.

u The NE or the card is faulty.

4 The clock and cross-connect card is faulty, causing that the traced
synchronization reference source cannot be locked or the restored clock
signal is of poor quality.

4 The alarmed tributary card is faulty, causing that the restored clock signal
is of poor quality.

Handling procedure

1. Access the OTNM2000 to check the TPJEP_AU performance and confirm the
NE or line that generates the performance event.

2. Check whether the clock configuration on the local and adjacent NE is correct.

4 If yes, ➔ Step 3.

4 If not, re-configure the clock configuration. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the card temperature of the local and adjacent NE is correct.

4 If yes, ➔ Step 4.

428 Version: A
 4 Performance Handling

4 If not, replace the faulty fan and clean the anti-dust screen in a timely
manner. If the count of this performance event is still a non-zero value after
the above operation, ➔ Step 4.

4. Check whether the optical fiber connection of the local end and the adjacent
NE is correct.

4 If yes, ➔ Step 5.

4 If not, re-connect according to the planning of the actual east-west network

interface of the project. If the count of this performance event is still a non-
zero value after this operation, ➔ Step 5.

5. Check whether the accuracy of the external synchronization reference source

in the Internet complies with the standard.

4 If yes, ➔ Step 6.

4 If not, use the internal oscillator to provide the clock for other NEs when the
external synchronization reference source or the master clock equipment
is replaced. If the count of this performance event is still a non-zero value
after the above operation, ➔ Step 6.

6. Isolate the faulty card by analyzing the pointer justification time, the bit error
and the packet loss of other cards, and then replace the faulty card with an
identical spare one.

7. After the operation, If the performance count is still a non-zero value, please
contact FiberHome after-sales maintenance engineer.

4.117 TX_BCAST
Meaning

The number of the transmitted broadcast packets. The data packet whose
destination MAC address is FF-FF-FF-FF-FF-FF is called the broadcast packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, S1J2

Version: A 429
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

All the nodes will process the broadcast packets so that excessive broadcast
packets may occupy all the node resource. Excessive broadcast packets are one of
the leading causes of the network performance degradation.

Possible cause

Normal count for counting and reporting the number of the transmitted broadcast
packets.

Handling procedure

If the number of the broadcast packets is within the normal range, no handling is
needed; if the number is excessive, perform the following operations:

1. Check whether the loop exists; if yes, enable the STP protocol or modify the
physical link to eliminate the loop.

2. Enable the broadcast packet suppression function of the relevant port and set
the broadcast packet traffic appropriately in the Physical_Port_Config tab in
the NE configuration GUI.

3. Set VLAN for the relevant service port in the Logical_Port_Config tab of the
NE configuration GUI.

4. Analyze the broadcast packet source address with the packet capture tool and
check whether the equipment at this address is damaged or has viruses.

5. Please contact FiberHome after-sales maintenance engineer.

4.118 TX_BDPK
Meaning

The number of transmitted error packets.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

430 Version: A
 4 Performance Handling

Influence on the system

The larger the number of transmitted error packet in a period (such as 15 minutes or
24 hours) is, the more severe the service quality degrades.

Possible cause

The card at the Tx end or the optical module is faulty.

Handling procedure

If the number of the transmitted error packets is within the normal range, no
handling is needed; if the number is excessive, perform the following operations:

1. Replace or clean the optical module.

2. Check whether the card at the Tx end is faulty; if yes, replace the faulty card
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guid).

4.119 TX_BYTES./TX_BYTES
Meaning

The total number of the transmitted bytes.

Relevant card

u TX_BYTES.: XSJ2, GSJ2, XCUJ2

u TX_BYTES: XSJ3, XGJ1, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted bytes.

Handling procedure

Normal count. No handling is needed.

Version: A 431
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

4.120 TX_FLOW
Meaning

The transmitted flow.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the transmitted flow.

Handling procedure

Normal count. No handling is needed.

4.121 TX_GFP
Meaning

The statistics of transmitted GFP frames.

Relevant card

S1J2

Influence on the system

None

Possible cause

Normal count for counting and reporting the number of the transmitted GFP frames.

432 Version: A
 4 Performance Handling

Relevant alarm

None.

Handling procedure

Normal count. No handling is needed.

4.122 TX_MCAST
Meaning

The number of the transmitted multicast packets. The packet whose first byte of the
destination MAC address is an odd number is called the multicast packet.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, S1J2

Influence on the system

Similar to the broadcast packet, all the member nodes belong to a same group
process the multicast packets, so that excessive multicast packets will cause the
network performance degradation. In general, the incidence of the multicast packet
is less than the broadcast packet.

Possible cause

Normal count for counting and reporting the number of the transmitted multicast
packets.

Handling procedure

If the number of the multicast packets is within the normal range, no handling is
needed; if the number is excessive, perform the following operations:

1. Enable the multicast packet suppression function of the relevant LAN port and
set the broadcast packet traffic appropriately in the Physical_Port_Config tab
in the NE configuration GUI.

Version: A 433
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

2. Set VLAN for the relevant service port in the Logical_Port_Config tab of the
NE configuration GUI.

3. Analyze the multicast packet source address with the packet capture tool and
check whether the equipment at this address is damaged or is incorrectly
configured.

4.123 TX_NONUCAST_PACKS
Meaning

The number of non-unicast packets transmitted.

Relevant card

ESJ1, ESJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of non-unicast packets
transmitted.

Handling procedure

Normal count. No handling is needed.

4.124 TX_PACKS
Meaning

The total number of transmitted packets.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, S1O1, XCUJ2, XCUJ4, S1J2, S1J4

434 Version: A
 4 Performance Handling

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of transmitted packets.

Handling procedure

Normal count. No handling is needed.

4.125 TX_PACKS_1024_TO_1518
Meaning

The total number of the transmitted packets with 1024 to 1518 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
with 1024 to 1518 bytes.

Handling procedure

Normal count. No handling is needed.

4.126 TX_PACKS_1519_TO_MAX
Meaning

The total number of the transmitted packets with 1519 to MAX bytes.

Version: A 435
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of the transmitted packets with
1519 to MAX bytes.

Handling procedure

Normal count. No handling is needed.

4.127 TX_PACKS_512_TO_1023
Meaning

The total number of the transmitted packets with 512 to 1023 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
with 512 to 1023 bytes.

Handling procedure

Normal count. No handling is needed.

436 Version: A
 4 Performance Handling

4.128 TX_PACKS128TO255
Meaning

The total number of the transmitted packets with 128 to 255 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
with 128 to 255 bytes.

Handling procedure

Normal count. No handling is needed.

4.129 TX_PACKS256TO511
Meaning

The total number of the transmitted packets with 256 to 511 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
with 256 to 511 bytes.

Version: A 437
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

Normal count. No handling is needed.

4.130 TX_PACKS64
Meaning

The total number of the transmitted packets within 64 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
within 64 bytes.

Handling procedure

Normal count. No handling is needed.

4.131 TX_PACKS65TO127
Meaning

The total number of the transmitted packets with 65 to 127 bytes.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

438 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the total number of the transmitted packets
with 65 to 127 bytes.

Handling procedure

Normal count. No handling is needed.

4.132 TX_PAUSE
Meaning

The number of the transmitted PAUSE frames. The PAUSE frame is the MAC
control frame with the operation code 00-01 and is used to receive the flow control
information.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4, ESJ1, ESJ2, S1J2

Influence on the system

When the buffer occupation of the transmitter exceeds the maximum value, users
can use the PAUSE frame to pause the transmission from the receiver, so as to
prevent the packet loss caused by the buffer overflow of the transmitter.

Possible cause

u The Rx packet rate exceeds the port bandwidth at the far end.

u The performance of the optical fiber (network cable) or the optical module is
degraded.

u The alarmed card is faulty.

Handling procedure

1. Lower the Rx packet rate at the local end.

2. Replace the optical fiber (network cable) or the optical module.

Version: A 439
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

3. Replace the faulty card (see CiTRANS 660 High-capacity MPLS-TP Platform
Troubleshooting Guide).

4.133 TX_UCAST
Meaning

The number of the transmitted unicast packets.

Relevant card

ESJ1, ESJ2

Influence on the system

None.

Possible cause

Normal count for counting and reporting the number of transmitted unicast packets.

Handling procedure

Normal count. No handling is needed.

4.134 UAS
Meaning

Unavailable second.

Relevant card

E1J1

Influence on the system

A few errors exist in the E1 link. The system will not be influenced if no relevant
alarm is generated, yet users should find the causes and handle the performance
event in a timely manner to avoid the occurrence of alarms and the influence of the
transmission quality of the E1 signal.

440 Version: A
 4 Performance Handling

Possible cause

Normal count for counting and reporting the errored seconds of the E1 interface.
The causes of the performance abnormality may be:

u External cause

4 The E1 cable performance is degraded and the attenuation is high.

4 The E1 cable connector is unclean or connected incorrectly.

4 The equipment is not well-grounded.

4 The powerful interference sources exist near the equipment.

4 The heat dissipation of the equipment is poor, causing over-high working

temperature.

u Equipment cause

4 The signal attenuation on the Rx end of the E1 card is over-high.

4 The Tx end or Rx end of the E1 card is faulty.

4 The clock synchronization performance degrades.

4 The fan fails.

4 The E1 card fails or its performance is degraded.

Handling procedure

See methods in E1_BBE for handling the performance event.

4.135 UAS_HP
Meaning

The unavailable seconds of the higher order path.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Version: A 441
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If the count of the UAS_HP is a non-zero value, the higher order path errors are
detected in the Rx side at the local end. The bigger the UAS_HP count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a larger quantity of bit errors influence the service transmission quality.

Possible cause

During the monitoring on the B3 byte (error monitoring byte of the higher order path),
if the severe error of the higher order path is detected for ten consecutive seconds,
the UAS_HP count starts, which includes the previous ten seconds. The UAS_HP
count stops after the severe error of the higher order path disappears for ten
consecutive seconds continuously. These ten consecutive seconds is not included
in the UAS_HP count.

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

442 Version: A
 4 Performance Handling

u The fiber and the equipment at the far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the UAS_HP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Locate the faulty card by loopback and replace it with an identical spare one.

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.136 UAS_LP
Meaning

The unavailable seconds of the lower order path.

Relevant card

S1O1, S1J1, S1J4

Version: A 443
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Influence on the system

If the count of the UAS_LP is a non-zero value, the lower order path errors are
detected in the Rx side at the local end. The bigger the UAS_LP count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a large quantity of bit errors influence the service transmission quality.

Possible cause

During the monitoring on the 1 to 2 bit of the V5 byte (error monitoring byte), if the
severe error of the lower order path is detected for ten consecutive seconds, the
UAS_LP count starts, which includes the previous ten seconds. The UAS_LP count
stops after the severe error of the lower order path disappears for ten consecutive
seconds. These ten seconds is not included in the UAS_LP count.

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

444 Version: A
 4 Performance Handling

Handling procedure

1. Access the OTNM2000 to check the UAS_LP performance and confirm the NE
or line that generates the performance event.

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Locate the faulty card by loopback and replace it with an identical spare one. If
the count of this performance event is still a non-zero value, ➔ Step 5.

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.137 UAS_MS
Meaning

The unavailable seconds of the multiplex section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

If the count of the UAS_MS is a non-zero value, the multiplex section errors are
detected in the Rx side at the local end. The bigger the UAS_MS count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a larger quantity of bit errors influence the service transmission quality.

Version: A 445
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

During the monitoring on the B2 byte (error monitoring byte of the multiplex section),
if the severe error of the multiplex section is detected for ten consecutive seconds,
the UAS_MS count starts, which includes the previous ten seconds. The UAS_MS
count stops after the severe error of the multiplex section disappears for ten
consecutive seconds. These ten seconds is not included in the UAS_MS count.

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at the far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the UAS_MS performance and confirm the NE
or line that generates the performance event.

446 Version: A
 4 Performance Handling

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.138 UAS_RS
Meaning

The unavailable seconds of the regenerator section.

Relevant card

XSJ2, XSJ3, XGJ1, S1O1, S1J1, S1J4

Influence on the system

If the count of the UAS_RS is a non-zero value, the regenerator section errors are
detected in the Rx side at the local end. The bigger the UAS_RS count is, the more
bit errors exist. A small quantity of bit errors have little influence on the system while
a large quantity of bit errors influence the service transmission quality.

Version: A 447
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Possible cause

During the monitoring on the B1 byte (error monitoring byte of the regenerator
section), if the severe error of the regenerator section is detected for ten
consecutive seconds, the UAS_RS count starts, which includes the previous ten
seconds. The UAS_RS count stops after the severe error of regenerator section
disappears for ten consecutive seconds. These ten seconds is not included in the
UAS_RS count.

u Environmental factors

4 The temperature of the equipment room is beyond the normal range from
-30℃ to 55℃.

4 The humidity of the equipment room exceeds 90%.

4 The DC power voltage is of poor stability or is beyond the normal voltage

range from -40V to -57V.

4 The interference sources exist in the equipment room.

4 The equipment is not well grounded.

4 The anti-dust screen is blocked, and the air convection is poor.

4 The fan unit is faulty.

4 The optical power is abnormal that it is lower than the sensitivity or higher
than the overload point.

4 The optical power is normal, but the dispersion is over-high.

4 The optical fiber faults, such as the over-bent pigtail and the optical cable
degradation.

4 The fiber connector is unclean or faulty.

u The clock synchronization performance is poor.

u The alarmed card is faulty.

u The fiber and the equipment at far end is faulty.

Handling procedure

1. Access the OTNM2000 to check the UAS_RS performance and confirm the NE
or line that generates the performance event.

448 Version: A
 4 Performance Handling

2. Check whether the environmental factors such as equipment room

environment, input voltage of the external power, cable connection and fan unit
are normal.

4 If yes, ➔ Step 3.

4 If not, eliminate the environmental faults. If the count of this performance

event is still a non-zero value after this operation, ➔ Step 3.

3. Check whether the NE clock synchronization is normal.

4 If yes, ➔ Step 4.

4 If not, eliminate the clock fault. If the count of this performance event is still
a non-zero value after this operation, ➔ Step 4.

4. Isolate the faulty card by loopback and replace it with an identical spare one
(see CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide).

5. Ensure that the cable and the far end equipment are normal.

6. If the performance count still exists, please contact FiberHome after-sales

maintenance engineer.

4.139 VC_RX_CV
Meaning

The count of the CV packets received by the MPLS-TP virtual channel. Count and
report the total number of the CV frames received by the local VC layer.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

After the CV frame is enabled at the local and far ends, the CV frames of the VC
layer received by the local end are counted and reported.

Version: A 449
CiTRANS 660 High-capacity MPLS-TP Platform Alarm and Performance Reference

Handling procedure

Normal count. No handling is needed.

4.140 VC_TX_CV
Meaning

The count of the CV packets transmitted by the MPLS-TP virtual channel. Count
and report the total number of the CV frames transmitted by the local VC layer.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

After the CV frame is enabled at the local and far ends, the CV frames of the VC
layer transmitted by the local end are counted and reported.

Handling procedure

Normal count. No handling is needed.

4.141 VP_RX_CV
Meaning

The count of the CV packets received by the MPLS-TP virtual path. Count and
report the total number of the CV frames received by the local VP layer.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

450 Version: A
 4 Performance Handling

Influence on the system

None.

Possible cause

After the CV frame is enabled at the local and far ends, the CV frames of the VP
layer received by the local end are counted and reported.

Handling procedure

Normal count. No handling is needed.

4.142 VP_TX_CV
Meaning

The count of the CV packets transmitted by the MPLS-TP virtual path. Count and
report the total number of the CV frames transmitted by the local VP layer.

Relevant card

XSJ2, XSJ3, XGJ1, GSJ2, XCUJ2, XCUJ4

Influence on the system

None.

Possible cause

After the CV frame is enabled at the local and far ends, the CV frames of the VP
layer transmitted by the local end are counted and reported.

Handling procedure

Normal count. No handling is needed.

Version: A 451
 Appendix A Abbreviations

APS Automatic Protection Switching

ASON Automatically Switched Optical Network

BMU Board Management Unit

EMI Electromagnetic Interference

FC Fiber Channel
FE Fast Ethernet
FPGA Field-Programmable Gate Array

GE Gigabit Ethernet

IEEE Institute of Electrical and Electronics Engineers

IETF The Internet Engineering Task Force

IP Internet Protocol
ITU International Telegraph Union

ITU-T ITU Telecommunication Standardization Sector

MAC Media Access Control
MPLS Multi-Protocol Label Switching

MPLS-TP MPLS-Transport Profile

OAM Operation Administration and Maintenance

ODF Optical Distribution Frame

PDP Power Distribution Panel

PW Pseudo Wire
QinQ 802.1Q In 802.1Q or Double VLAN
QoS Quality of Service

SFP Small Form-Factor Pluggable

STM Synchronous Transport Module

TDM Time Division Multiplex and Multiplexer

TPS Tributary Protection Switching Unit

VLAN Virtual Local Area Network

VPLS Virtual Private LAN Service
VPWS Virtual Pseudo Wire Service
XFP 10 Gigabit Small Form Factor Pluggable

452 Version: A
 Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.

Name
Phone Number
Email Address
Company

To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.

Documentation Name
Code and Version

Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?

8. Which parts of the documentation are you unsatisfied with?Why?

9. What is your opinion on the Figures in the documentation?

□ Beautiful □ Unbeautiful (your advice)

□ Practical □ Unpractical (your advice)

10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:

Satisfied (please specify)

Unsatisfied (please specify)

12. Additional comments about our documentation or suggestions on how we can improve:

Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
[email protected]