Alarms and Performance Events Reference V100R006C01 02 PDF

OptiX OSN 8800/6800/3800
V100R006C01
Alarms and Performance Events

Reference
Issue
02
Date
2011-10-31
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2011-10-31)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
OptiX OSN 8800/6800/3800

Alarms and Performance Events Reference
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX OSN 8800
V100R006C01
OptiX OSN 6800
V100R006C01
OptiX OSN 3800
V100R006C01
iManager U2000
V100R005C00
iManager U2000 Web LCT
V100R005C00
Intended Audience
The intended audience of this document are:
l
System maintenance engineer
Network monitoring engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
Issue 02 (2011-10-31)
Indicates a hazard with a high level of risk, which if not

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

ii
OptiX OSN 8800/6800/3800

About This Document
Symbol
Description
CAUTION
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save

time.
NOTE
Provides additional information to emphasize or supplement

important points of the main text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 02 (2011-10-31) Based on Product Version

V100R006C01
Update
Description
2 Alarm List
l 2.2.63 NPO2 Board Alarm List is modified.

l 2.2.65 NQ2 Board Alarm List is modified.
l 2.2.66 NS2 Board Alarm List is modified.
l 2.2.62 ND2 Board Alarm List is modified.
Issue 02 (2011-10-31)

iii
OptiX OSN 8800/6800/3800

About This Document
Update
Description
4 Alarm
Processing
l 4.277 TIME_LOS is modified.

l 4.62 EXT_TIME_LOC is modified.
l 4.278 TIME_NO_TRACE_MODE is modified.
l 4.177 OPA_FAIL_INDI is modified.
l 4.93 LASER_HAZARD_WARNING is modified.
l 4.29 CFCARD_FAILED is modified.
l 3.37 POWER_FAIL is modified.
l 4.63 FAN_FAIL is modified.
5 Performance
Event List
l 5.2.44 NQ2 Board Performance Event List is modified.

l 5.2.47 NS2 Board Performance Event List is modified.
l 5.2.43 ND2 Board Performance Event List is modified.

V100R006C01
Update
Description
2 Alarm List
l 2.2.3 BMD4 Board Alarm List is added.

l 2.2.22 ELQX Board Alarm List is added.
l 2.2.74 PTQX Board Alarm List is added.
l 2.2.39 LOA Board Alarm List is added.
l 2.2.64 NPO2E Board Alarm List is added.
l 2.2.65 NQ2 Board Alarm List is modified.
l 2.2.62 ND2 Board Alarm List is modified.
l 2.2.66 NS2 Board Alarm List is modified.
l 2.2.101 TDX Board Alarm List is modified.
l 2.2.109 TQX Board Alarm List is modified.
l 2.2.68 OAU1 Board Alarm List is modified.
l 2.2.55 M40 Board Alarm List is modified.
l 2.2.10 D40 Board Alarm List is modified.
l 2.2.54 M40V Board Alarm List is modified.
l 2.2.23 ENQ2 Board Alarm List is modified.
l 2.2.81 SCC Board Alarm List is modified.
Issue 02 (2011-10-31)

iv
OptiX OSN 8800/6800/3800

About This Document
Update
Description
4 Alarm
Processing
l 4.4 ALS_ACTIVE is added.

l 4.115 MAINBD_SUBBD_MISMATCH is added.
l 4.225 RL_CRITICAL_HI is added.
l 4.226 RL_CRITICAL_LOW is added.
5 Performance
Event List
l 5.2.9 ELQX Board Performance Event List is added.

l 5.2.54 PTQX Board Performance Event List is added.
l 5.2.24 LOA Board Performance Event List is added.
l 5.2.46 NPO2E Board Performance Event List is added.
l 5.2.58 SCC Board Performance Event List is added.

V100R006C00
Update
Description
2 Alarm List

l 2.2.22 ELQX Board Alarm List is added.
l 2.2.74 PTQX Board Alarm List is added.
l 4.85 IPA_SHUT is added.
4 Alarm
Processing
l 4.177 OPA_FAIL_INDI is modified.

l 4.131 NO_BD_SOFT is modified.
5 Performance
Event List
Issue 02 (2011-10-31)
l 5.2.9 ELQX Board Performance Event List is added.

l 5.2.54 PTQX Board Performance Event List is added.

OptiX OSN 8800/6800/3800

About This Document

V100R006C00
Update
Description
2 Alarm List
l 2.2.97 SXH Board Alarm List is added.

l 2.2.102 THA Board Alarm List is added.
l 2.2.104 TOA Board Alarm List is added.
l 2.2.109 TQX Board Alarm List is modified.
l BMD4, BMD8, ELQX, PTQX are deleted.
4 Alarm
Processing
l 4.29 CFCARD_FAILED is added.
5 Performance
Event List
l 5.2.73 SXH Board Performance Event List is added.
l 4.60 EXT_MODULE_OFFLINE is added.
l 5.2.78 THA Board Performance Event List is added.

l 5.2.80 TOA Board Performance Event List is added.
l 5.2.85 TQX Board Performance Event List is modified.
l ELQX, PTQX are deleted.

V100R006C00
Update
Description
2 Alarm List
l 2.2.11 DAS1 Board Alarm List is added.

l 2.2.118 WSMD9 Board Alarm List is added.
l 2.2.119 XCH Board Alarm List is modified.
l 2.2.2 AUX Board Alarm List is modified.
l 4.51 ETH_MISCONNECT is added.
4 Alarm
Processing
l 4.248 SUBRACK_COMM_PS is added.
5 Performance
Event List
Issue 02 (2011-10-31)
l 5.2.2 DAS1 Board Performance Event List is added.

l 5.2.94 WSMD9 Board Performance Event List is added.

vi
OptiX OSN 8800/6800/3800

About This Document

V100R005C00
Update
Description
2 Alarm List
l 2.2.38 LEX4 Board Alarm List is modified.

l 2.2.37 LEM24 Board Alarm List is modified.
l 2.2.101 TDX Board Alarm List is modified.
l 2.2.61 MR8V Board Alarm List is modified.
l 2.2.19 EFI1 Board Alarm List is modified.
l 2.2.20 EFI2 Board Alarm List is modified.
5 Performance
Event List
l 5.2.12 HSC1 Board Performance Event List is modified.

l 5.2.43 ND2 Board Performance Event List is modified.
l 5.2.47 NS2 Board Performance Event List is modified.
l 5.2.77 TDX Board Performance Event List is modified.
l 5.2.85 TQX Board Performance Event List is modified.
l 5.2.28 LQMS Board Performance Event List is modified.
l 5.2.27 LQMD Board Performance Event List is modified.
l 5.2.29 LQM Board Performance Event List is modified.
l 5.2.83 TQM Board Performance Event List is modified.
l 5.2.82 TOM Board Performance Event List is modified.

V100R005C00
Some bugs in the manual of the previous version are fixed.

V100R005C00
Update
Description
4 Alarm
Processing
l 4.52 ETH_SERVICE_CONFIG_FAIL is added.

l 4.235 SPAN_LOSS_HIGH is added.
l 4.236 SPAN_LOSS_LOW is added.
l 4.257 SWDL_BD_EXCLUDE is added.
l ALC_LINE_WASTAGE is deleted.
Issue 02 (2011-10-31)

vii
OptiX OSN 8800/6800/3800

About This Document

V100R005C00
This issue is the first official release for OptiX OSN 8800/6800/3800 V100R005C00. In this
release, the manuals for OptiX OSN 8800 V100R002C02, OptiX OSN 6800 V100R004C04,
and OptiX OSN 3800 V100R004C04 are combined into one manual.
Update
Description
Whole manual
l This manual provides descriptions according to product series OptiX

OSN 8800, OptiX OSN 6800, and OptiX OSN 3800. Any difference
between the products is described in the manual.
l The equipment name is changed from OptiX OSN 8800 I to OptiX
OSN 8800 T32 or from OptiX OSN 8800 II to OptiX OSN 8800 T64.
2 Alarm List
l 2.2.23 ENQ2 Board Alarm List is added.

l 2.2.37 LEM24 Board Alarm List is added.
l 2.2.38 LEX4 Board Alarm List is added.
l 2.2.63 NPO2 Board Alarm List is added.
l 2.2.72 OPM8 Board Alarm List is added.
l 2.2.83 SFIU Board Alarm List is added.
l 2.2.84 ST2 Board Alarm List is added.
3 Common
Alarm
Processing
l 3.3 BOOTROM_BAD is modified.

l 3.4 BUS_ERR is modified.
l 3.7 COMMUN_FAIL is modified.
l 3.29 ODUk_PM_SSF is modified.
l 3.33 OTUk_LOF is modified.
l 3.34 OTUk_SSF is modified.
l 3.48 SWDL_NEPKGCHECK is modified.
l 3.50 TEMP_OVER is modified.
Issue 02 (2011-10-31)

viii
OptiX OSN 8800/6800/3800

About This Document
Update
Description
4 Alarm
Processing
l ALC_LINE_WASTAGE is added.
l 4.2 ALC_ADJUST_FAIL is added.
l 4.3 ALC_WAIT_ADJUST is added.
l 4.12 APE_ADJUST_FAIL is added.
l 4.13 APE_ADJUST_PEND is added.
l 4.65 FEATURE_WITHOUT_LICENSE is added.
l 4.73 FWD_PKT_LOSS is added.
l 4.95 LCS_DAYS_OF_GRACE is added.
l 4.96 LCS_EXPIRED is added.
l 4.97 LCS_FILE_NOT_EXIST is added.
l 4.126 MULTI_RPL_OWNER is added.
l 4.134 NTP_SYNC_FAIL is added.
l 4.184 OSC_BDI is added.
l 4.185 OSC_DEG is added.
l 4.231 SEC_RADIUS_FAIL is added.
l 4.282 VCAT_LOA is added.
l 4.289 WAVE_ADD_ABN is added.
l 4.290 WAVE_DROP_ABN is added.
5 Performance
Event List
l 5.2.10 ENQ2 Board Performance Event List is added.

l 5.2.22 LEM24 Board Performance Event List is added.
l 5.2.23 LEX4 Board Performance Event List is added.
l 5.2.45 NPO2 Board Performance Event List is added.
l 5.2.53 OPM8 Board Performance Event List is added.
l 5.2.70 ST2 Board Performance Event List is added.
Issue 02 (2011-10-31)

ix
OptiX OSN 8800/6800/3800

About This Document
Update
Description
6 Performance
Event
Processing
l 6.17 FEC_AFT_CORER_FLOAT is added.

l 6.20 FEC_BEF_CORER_FLOAT is added.
l 6.81 OSC_BBE is added.
l 6.82 OSC_BBER is added.
l 6.83 OSC_BIAES is added.
l 6.84 OSC_ES is added.
l 6.85 OSC_FEBBE is added.
l 6.86 OSC_FEBBER is added.
l 6.87 OSC_FEES is added.
l 6.88 OSC_FESES is added.
l 6.89 OSC_FESESR is added.
l 6.90 OSC_FEUAS is added.
l 6.91 OSC_IAES is added.
l 6.92 OSC_SES is added.
l 6.93 OSC_SESR is added.
l 6.94 OSC_UAS is added.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

Contents
Contents
About This Document.....................................................................................................................ii
1 Overview.........................................................................................................................................1
1.1 Alarm Level........................................................................................................................................................2
1.2 Alarm Category..................................................................................................................................................2
1.3 Performance Event Category..............................................................................................................................3
1.4 Alarm Signal Flow..............................................................................................................................................4
1.4.1 Overview...................................................................................................................................................4
1.4.2 Non-Convergent OTU Processing Standard SDH Signals........................................................................6
1.4.3 Non-Convergent OTU Processing Standard OTN Signals........................................................................9
1.4.4 Convergent OTU Processing Standard SDH Signals..............................................................................12
1.4.5 Convergent OTU Processing Standard OTN Signals..............................................................................15
1.4.6 Regenerating OTU...................................................................................................................................18
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect Function................................................20
1.4.8 OTU Processing GE Signals....................................................................................................................21
1.4.9 Optical-Layer Alarm Signal Processing on OTN....................................................................................25
1.5 Suppression Relationship of Alarms................................................................................................................29
1.5.1 Suppression of OTN Alarms...................................................................................................................29
1.5.2 Suppression of Alarms Related to SDH Services and Other Common Equipment Alarms....................31
1.6 Performance Event Suppression by Alarms.....................................................................................................32
2 Alarm List......................................................................................................................................34
2.1 Product Alarm List...........................................................................................................................................35
2.1.1 Alarm List A............................................................................................................................................35
2.1.2 Alarm List B............................................................................................................................................36
2.1.3 Alarm List C............................................................................................................................................37
2.1.4 Alarm List D............................................................................................................................................37
2.1.5 Alarm List E............................................................................................................................................38
2.1.6 Alarm List F.............................................................................................................................................39
2.1.7 Alarm List G............................................................................................................................................40
2.1.8 Alarm List H............................................................................................................................................40
2.1.9 Alarm List I.............................................................................................................................................41
2.1.10 Alarm List J...........................................................................................................................................41
2.1.11 Alarm List K..........................................................................................................................................42
Issue 02 (2011-10-31)

xi
OptiX OSN 8800/6800/3800

Contents
2.1.12 Alarm List L..........................................................................................................................................42

2.1.13 Alarm List M.........................................................................................................................................44
2.1.14 Alarm List N..........................................................................................................................................45
2.1.15 Alarm List O..........................................................................................................................................45
2.1.16 Alarm List P...........................................................................................................................................55
2.1.17 Alarm List R..........................................................................................................................................56
2.1.18 Alarm List S...........................................................................................................................................57
2.1.19 Alarm List T..........................................................................................................................................60
2.1.20 Alarm List V..........................................................................................................................................61
2.1.21 Alarm List W.........................................................................................................................................61
2.1.22 Alarm List X..........................................................................................................................................62
2.2 Board Alarm List..............................................................................................................................................62
2.2.1 ATE Board Alarm List............................................................................................................................62
2.2.2 AUX Board Alarm List...........................................................................................................................62
2.2.3 BMD4 Board Alarm List.........................................................................................................................63
2.2.4 BMD8 Board Alarm List.........................................................................................................................64
2.2.5 CMR1 Board Alarm List.........................................................................................................................64
2.2.8 CRPC Board Alarm List..........................................................................................................................64
2.2.9 D40V Board Alarm List..........................................................................................................................65
2.2.10 D40 Board Alarm List...........................................................................................................................65
2.2.11 DAS1 Board Alarm List........................................................................................................................65
2.2.12 DCU Board Alarm List..........................................................................................................................66
2.2.13 DCP Board Alarm List..........................................................................................................................66
2.2.14 DFIU Board Alarm List.........................................................................................................................67
2.2.15 DMR1 Board Alarm List.......................................................................................................................67
2.2.16 EAS2 Board Alarm List........................................................................................................................68
2.2.17 ECOM Board Alarm List......................................................................................................................69
2.2.18 EFI Board Alarm List............................................................................................................................69
2.2.19 EFI1 Board Alarm List..........................................................................................................................69
2.2.20 EFI2 Board Alarm List..........................................................................................................................70
2.2.21 EGSH Board Alarm List........................................................................................................................70
2.2.22 ELQX Board Alarm List.......................................................................................................................71
2.2.23 ENQ2 Board Alarm List........................................................................................................................73
2.2.24 FAN Board Alarm List..........................................................................................................................75
2.2.25 FIU Board Alarm List............................................................................................................................75
2.2.26 GFU Board Alarm List..........................................................................................................................76
2.2.27 HBA Board Alarm List..........................................................................................................................76
2.2.28 HSC1 Board Alarm List........................................................................................................................77
2.2.29 ITL Board Alarm List............................................................................................................................77
2.2.30 L4G Board Alarm List...........................................................................................................................78
Issue 02 (2011-10-31)

xii
OptiX OSN 8800/6800/3800

Contents
2.2.31 LDGD Board Alarm List.......................................................................................................................79

2.2.32 LDGS Board Alarm List........................................................................................................................81
2.2.33 LDM Board Alarm List.........................................................................................................................82
2.2.34 LDMD Board Alarm List......................................................................................................................84
2.2.35 LDMS Board Alarm List.......................................................................................................................85
2.2.36 LDX Board Alarm List..........................................................................................................................87
2.2.37 LEM24 Board Alarm List......................................................................................................................88
2.2.38 LEX4 Board Alarm List........................................................................................................................90
2.2.39 LOA Board Alarm List..........................................................................................................................91
2.2.40 LOG Board Alarm List..........................................................................................................................93
2.2.41 LOM Board Alarm List.........................................................................................................................95
2.2.42 LQG Board Alarm List..........................................................................................................................97
2.2.43 LQMD Board Alarm List......................................................................................................................98
2.2.44 LQMS Board Alarm List.....................................................................................................................101
2.2.45 LQM Board Alarm List.......................................................................................................................105
2.2.46 LSQ Board Alarm List........................................................................................................................106
2.2.47 LSXLR Board Alarm List...................................................................................................................108
2.2.48 LSXL Board Alarm List......................................................................................................................110
2.2.49 LSXR Board Alarm List......................................................................................................................113
2.2.50 LSX Board Alarm List........................................................................................................................114
2.2.51 LWX2 Board Alarm List.....................................................................................................................118
2.2.52 LWXD Board Alarm List....................................................................................................................118
2.2.53 LWXS Board Alarm List.....................................................................................................................119
2.2.54 M40V Board Alarm List......................................................................................................................120
2.2.55 M40 Board Alarm List........................................................................................................................121
2.2.56 MCA4 Board Alarm List.....................................................................................................................121
2.2.57 MCA8 Board Alarm List.....................................................................................................................122
2.2.58 MR2 Board Alarm List........................................................................................................................122
2.2.61 MR8V Board Alarm List.....................................................................................................................123
2.2.62 ND2 Board Alarm List........................................................................................................................123
2.2.63 NPO2 Board Alarm List......................................................................................................................127
2.2.64 NPO2E Board Alarm List....................................................................................................................132
2.2.65 NQ2 Board Alarm List........................................................................................................................133
2.2.66 NS2 Board Alarm List.........................................................................................................................141
2.2.67 NS3 Board Alarm List.........................................................................................................................149
2.2.68 OAU1 Board Alarm List.....................................................................................................................156
2.2.69 OBU1 Board Alarm List......................................................................................................................157
2.2.70 OBU2 Board Alarm List......................................................................................................................158
2.2.71 OLP Board Alarm List........................................................................................................................158
2.2.72 OPM8 Board Alarm List.....................................................................................................................159
Issue 02 (2011-10-31)

xiii
OptiX OSN 8800/6800/3800

Contents
2.2.73 PIU Board Alarm List..........................................................................................................................160

2.2.74 PTQX Board Alarm List......................................................................................................................160
2.2.75 RDU9 Board Alarm List......................................................................................................................162
2.2.76 RMU9 Board Alarm List.....................................................................................................................162
2.2.77 ROAM Board Alarm List....................................................................................................................163
2.2.78 SBM2 Board Alarm List......................................................................................................................163
2.2.79 SC1 Board Alarm List.........................................................................................................................163
2.2.80 SC2 Board Alarm List.........................................................................................................................164
2.2.81 SCC Board Alarm List........................................................................................................................164
2.2.82 SCS Board Alarm List.........................................................................................................................171
2.2.83 SFIU Board Alarm List.......................................................................................................................171
2.2.84 ST2 Board Alarm List.........................................................................................................................171
2.2.85 SF64 Board Alarm List........................................................................................................................172
2.2.86 SF64A Board Alarm List.....................................................................................................................172
2.2.87 SFD64 Board Alarm List.....................................................................................................................173
2.2.88 SL64 Board Alarm List.......................................................................................................................174
2.2.89 SLH41 Board Alarm List....................................................................................................................175
2.2.90 SLD64 Board Alarm List....................................................................................................................175
2.2.91 SLO16 Board Alarm List....................................................................................................................176
2.2.92 SLQ16 Board Alarm List....................................................................................................................177
2.2.93 SLQ64 Board Alarm List....................................................................................................................177
2.2.94 STG Board Alarm List........................................................................................................................178
2.2.95 STI Board Alarm List..........................................................................................................................178
2.2.96 SXM Board Alarm List.......................................................................................................................179
2.2.97 SXH Board Alarm List........................................................................................................................179
2.2.98 TBE Board Alarm List........................................................................................................................179
2.2.99 TDC Board Alarm List........................................................................................................................180
2.2.100 TDG Board Alarm List......................................................................................................................180
2.2.101 TDX Board Alarm List......................................................................................................................181
2.2.102 THA Board Alarm List......................................................................................................................184
2.2.103 TMX Board Alarm List.....................................................................................................................185
2.2.104 TOA Board Alarm List......................................................................................................................189
2.2.105 TOG Board Alarm List......................................................................................................................191
2.2.106 TOM Board Alarm List.....................................................................................................................191
2.2.107 TQM Board Alarm List.....................................................................................................................194
2.2.108 TQS Board Alarm List......................................................................................................................197
2.2.109 TQX Board Alarm List......................................................................................................................198
2.2.110 TSXL Board Alarm List....................................................................................................................202
2.2.111 VA1 Board Alarm List......................................................................................................................204
2.2.112 VA4 Board Alarm List......................................................................................................................205
2.2.113 WMU Board Alarm List....................................................................................................................205
2.2.114 WSD9 Board Alarm List...................................................................................................................205
Issue 02 (2011-10-31)

xiv
OptiX OSN 8800/6800/3800

Contents
2.2.115 WSM9 Board Alarm List..................................................................................................................206

2.2.116 WSMD2 Board Alarm List................................................................................................................207
2.2.119 XCH Board Alarm List......................................................................................................................208
2.2.120 XCM Board Alarm List.....................................................................................................................210
2.2.121 XCS Board Alarm List......................................................................................................................210
2.2.122 XCT Board Alarm List......................................................................................................................210
3 Common Alarm Processing.....................................................................................................211

3.1 B1_EXC..........................................................................................................................................................214
3.1.1 B1_EXC (OCS).....................................................................................................................................214
3.1.2 B1_EXC (OTN).....................................................................................................................................217
3.2 BEFFEC_EXC................................................................................................................................................220
3.3 BOOTROM_BAD..........................................................................................................................................224
3.3.1 BOOTROM_BAD (OCS).....................................................................................................................224
3.3.2 BOOTROM_BAD (OTN).....................................................................................................................226
3.4 BUS_ERR.......................................................................................................................................................227
3.4.1 BUS_ERR (OCS)..................................................................................................................................227
3.4.2 BUS_ERR (OTN)..................................................................................................................................230
3.5 CHAN_LOS...................................................................................................................................................232
3.6 CLIENT_PORT_PS.......................................................................................................................................235
3.7 COMMUN_FAIL...........................................................................................................................................237
3.7.1 COMMUN_FAIL (OCS)......................................................................................................................237
3.7.2 COMMUN_FAIL (OTN)......................................................................................................................239
3.8 ETH_8B10B_ERR.........................................................................................................................................244
3.9 EX_ETHOAM_CC_LOS...............................................................................................................................246
3.9.1 EX_ETHOAM_CC_LOS (OCS)..........................................................................................................246
3.9.2 EX_ETHOAM_CC_LOS (OTN)..........................................................................................................247
3.10 FC_LINK_ERR............................................................................................................................................249
3.11 FC_SYNC_LOS...........................................................................................................................................253
3.12 IN_PWR_HIGH...........................................................................................................................................254
3.12.1 IN_PWR_HIGH (OCS).......................................................................................................................254
3.12.2 IN_PWR_HIGH (OTN)......................................................................................................................256
3.13 IN_PWR_LOW............................................................................................................................................259
3.13.1 IN_PWR_LOW (OCS)........................................................................................................................259
3.13.2 IN_PWR_LOW (OTN).......................................................................................................................262
3.14 INTRA_OTU_PS.........................................................................................................................................266
3.15 LASER_MODULE_MISMATCH...............................................................................................................268
3.16 LINK_ERR...................................................................................................................................................269
3.16.1 LINK_ERR (OCS)..............................................................................................................................269
3.16.2 LINK_ERR (OTN)..............................................................................................................................270
3.17 LOOP_ALM.................................................................................................................................................273
Issue 02 (2011-10-31)

xv
OptiX OSN 8800/6800/3800

Contents
3.17.1 LOOP_ALM (OCS)............................................................................................................................274

3.17.2 LOOP_ALM (OTN)............................................................................................................................275
3.18 LPT_ACTIVE..............................................................................................................................................276
3.19 LSR_WILL_DIE..........................................................................................................................................279
3.20 MS_AIS........................................................................................................................................................280
3.20.1 MS_AIS (OCS)....................................................................................................................................280
3.20.2 MS_AIS (OTN)...................................................................................................................................282
3.21 MS_RDI........................................................................................................................................................284
3.21.1 MS_RDI (OCS)...................................................................................................................................284
3.21.2 MS_RDI (OTN)...................................................................................................................................286
3.22 MUT_LOS....................................................................................................................................................288
3.23 OA_LOW_GAIN.........................................................................................................................................291
3.24 ODU_SNCP_PS...........................................................................................................................................293
3.25 ODUk_PM_AIS...........................................................................................................................................295
3.26 ODUk_PM_BDI...........................................................................................................................................299
3.27 ODUk_PM_DEG..........................................................................................................................................301
3.28 ODUk_PM_EXC..........................................................................................................................................303
3.29 ODUk_PM_SSF...........................................................................................................................................306
3.30 OMS_FDI.....................................................................................................................................................309
3.31 OSC_LOS.....................................................................................................................................................311
3.32 OTS_LOS.....................................................................................................................................................312
3.33 OTUk_LOF..................................................................................................................................................313
3.34 OTUk_SSF...................................................................................................................................................316
3.35 OUT_PWR_HIGH.......................................................................................................................................318
3.36 PORT_MODULE_OFFLINE......................................................................................................................319
3.37 POWER_FAIL.............................................................................................................................................321
3.38 PUMP_COOL_EXC....................................................................................................................................323
3.39 R_LOF..........................................................................................................................................................325
3.39.1 R_LOF (OCS)......................................................................................................................................325
3.39.2 R_LOF (OTN).....................................................................................................................................328
3.40 R_LOS..........................................................................................................................................................332
3.40.1 R_LOS (OCS)......................................................................................................................................332
3.40.2 R_LOS (OTN).....................................................................................................................................336
3.41 R_OOF..........................................................................................................................................................340
3.41.1 R_OOF (OCS).....................................................................................................................................340
3.41.2 R_OOF (OTN).....................................................................................................................................343
3.42 R_SLIP.........................................................................................................................................................347
3.43 REM_SF.......................................................................................................................................................349
3.44 REMOTE_FAULT.......................................................................................................................................351
3.45 SECU_ALM.................................................................................................................................................353
3.46 SUBRACK_ID_CONFLICT........................................................................................................................354
3.47 SUM_INPWR_LOW....................................................................................................................................355
Issue 02 (2011-10-31)

xvi
OptiX OSN 8800/6800/3800

Contents
3.48 SWDL_NEPKGCHECK..............................................................................................................................357
3.49 TD.................................................................................................................................................................359
3.50 TEMP_OVER...............................................................................................................................................360
3.51 TF..................................................................................................................................................................363
3.52 TS_CFG_MISMATCH................................................................................................................................364
3.53 WRG_BD_TYPE.........................................................................................................................................366
4 Alarm Processing.......................................................................................................................368
4.1 AD_CHECK_FAIL........................................................................................................................................378
4.2 ALC_ADJUST_FAIL....................................................................................................................................379
4.3 ALC_WAIT_ADJUST...................................................................................................................................381
4.4 ALS_ACTIVE................................................................................................................................................382
4.5 ALM_ALS......................................................................................................................................................383
4.6 APS_MANUAL_STOP..................................................................................................................................383
4.7 ALM_GFP_dCSF...........................................................................................................................................384
4.8 ALM_GFP_dLFD..........................................................................................................................................385
4.9 ALM_HANGUP.............................................................................................................................................388
4.10 ALM_TC_OEI..............................................................................................................................................389
4.11 ALM_TC_REI..............................................................................................................................................390
4.12 APE_ADJUST_FAIL...................................................................................................................................392
4.13 APE_ADJUST_PEND.................................................................................................................................393
4.14 APS_FAIL....................................................................................................................................................394
4.15 APS_INDI....................................................................................................................................................395
4.16 AU_AIS........................................................................................................................................................396
4.17 AU_LOP.......................................................................................................................................................399
4.18 B1_SD..........................................................................................................................................................401
4.18.1 B1_SD (OCS)......................................................................................................................................401
4.18.2 B1_SD (OTN)......................................................................................................................................404
4.19 B2_EXC........................................................................................................................................................406
4.20 B2_SD..........................................................................................................................................................409
4.21 B3_EXC........................................................................................................................................................412
4.22 B3_EXC_VC3..............................................................................................................................................415
4.23 B3_EXC_VC4..............................................................................................................................................416
4.24 B3_SD..........................................................................................................................................................417
4.25 B3_SD_VC3.................................................................................................................................................420
4.26 B3_SD_VC4.................................................................................................................................................422
4.27 BD_NOT_INSTALLED..............................................................................................................................422
4.28 BD_STATUS................................................................................................................................................423
4.28.1 BD_STATUS (OCS)...........................................................................................................................423
4.28.2 BD_STATUS (OTN)...........................................................................................................................425
4.29 CFCARD_FAILED......................................................................................................................................426
4.30 BDID_ERROR.............................................................................................................................................427
4.31 C2_VCAIS....................................................................................................................................................428
Issue 02 (2011-10-31)

xvii
OptiX OSN 8800/6800/3800

Contents
4.32 CHAN_ADD................................................................................................................................................429
4.33 CHIP_ABN...................................................................................................................................................430
4.34 CLIENT_PROT_NOTSTART.....................................................................................................................430
4.35 CLIENT_PORT_STA_INDI........................................................................................................................431
4.36 CLK_NO_TRACE_MODE..........................................................................................................................433
4.37 CRC4_CROSSTR........................................................................................................................................434
4.38 DB_RESTORE_FAIL..................................................................................................................................435
4.39 DBPS_ABNORMAL...................................................................................................................................436
4.40 DBMS_ABNORMAL..................................................................................................................................438
4.41 DBMS_ERROR............................................................................................................................................439
4.42 DBMS_PROTECT_MODE.........................................................................................................................441
4.43 DCM_INSUFF.............................................................................................................................................442
4.44 DLAG_PROTECT_FAIL............................................................................................................................443
4.45 DSP_LOAD_FAIL.......................................................................................................................................445
4.46 ETH_CFM_LOC..........................................................................................................................................446
4.47 ETH_CFM_MISMERGE.............................................................................................................................447
4.48 ETH_CFM_MACSTATUS..........................................................................................................................449
4.49 ETH_CFM_RDI...........................................................................................................................................450
4.50 ETH_CFM_UNEXPERI..............................................................................................................................451
4.51 ETH_MISCONNECT..................................................................................................................................453
4.52 ETH_SERVICE_CONFIG_FAIL................................................................................................................454
4.53 ETHOAM_DISCOVER_FAIL....................................................................................................................455
4.54 ETHOAM_RMT_CRIT_FAULT................................................................................................................457
4.55 ETHOAM_RMT_LOOP..............................................................................................................................458
4.56 ETHOAM_RMT_SD...................................................................................................................................459
4.57 ETHOAM_SELF_LOOP.............................................................................................................................460
4.58 ETHOAM_VCG_SELF_LOOP...................................................................................................................462
4.59 EX_ETHOAM_MPID_CNFLCT................................................................................................................463
4.60 EXT_MODULE_OFFLINE.........................................................................................................................464
4.61 EXT_SYNC_LOS........................................................................................................................................465
4.62 EXT_TIME_LOC.........................................................................................................................................467
4.63 FAN_FAIL...................................................................................................................................................468
4.64 FAN_FAULT...............................................................................................................................................469
4.65 FEATURE_WITHOUT_LICENSE.............................................................................................................470
4.66 FC_8B10BERR_OVER...............................................................................................................................471
4.67 FCS_ERR.....................................................................................................................................................471
4.68 FEC_LOF.....................................................................................................................................................474
4.69 FEC_OOF.....................................................................................................................................................475
4.70 FLOW_OVER..............................................................................................................................................476
4.71 FPGA_ABN..................................................................................................................................................477
4.72 FSELECT_STG............................................................................................................................................478
4.73 FWD_PKT_LOSS........................................................................................................................................479
Issue 02 (2011-10-31)

xviii
OptiX OSN 8800/6800/3800

Contents
4.74 GAINDATA_MIS........................................................................................................................................480
4.75 HARD_BAD................................................................................................................................................481
4.76 HARD_ERR.................................................................................................................................................484
4.77 HP_LOM......................................................................................................................................................487
4.78 HP_RDI........................................................................................................................................................488
4.79 HP_REI.........................................................................................................................................................490
4.80 HP_SLM.......................................................................................................................................................491
4.81 HP_TIM........................................................................................................................................................493
4.82 HP_UNEQ....................................................................................................................................................494
4.83 HSC_UNAVAIL..........................................................................................................................................495
4.84 INTRA_OTU_STA_INDI............................................................................................................................496
4.85 IPA_SHUT...................................................................................................................................................498
4.86 J0_MM..........................................................................................................................................................499
4.87 K1_K2_M.....................................................................................................................................................500
4.88 K2_M............................................................................................................................................................501
4.89 L_SYNC.......................................................................................................................................................502
4.90 LAN_LOC....................................................................................................................................................503
4.91 LAG_PORT_FAIL.......................................................................................................................................504
4.92 LAG_VC_PORT_FAIL...............................................................................................................................505
4.93 LASER_HAZARD_WARNING..................................................................................................................507
4.94 LASER_SHUT.............................................................................................................................................508
4.95 LCS_DAYS_OF_GRACE...........................................................................................................................509
4.96 LCS_EXPIRED............................................................................................................................................510
4.97 LCS_FILE_NOT_EXIST.............................................................................................................................511
4.98 LCAS_FOPR................................................................................................................................................512
4.99 LCAS_FOPT................................................................................................................................................513
4.100 LCAS_PLCR..............................................................................................................................................513
4.101 LCAS_PLCT..............................................................................................................................................515
4.102 LCAS_TLCR..............................................................................................................................................516
4.103 LCAS_TLCT..............................................................................................................................................518
4.104 LOCAL_FAULT........................................................................................................................................519
4.105 LOCK_CUR_FAIL....................................................................................................................................520
4.106 LOCKPOW_MIS.......................................................................................................................................521
4.107 LP_RDI_VC3.............................................................................................................................................522
4.108 LP_SLM_VC3............................................................................................................................................523
4.109 LP_UNEQ_VC3.........................................................................................................................................524
4.110 LPT_RFI.....................................................................................................................................................525
4.111 LSR_COOL_ALM.....................................................................................................................................526
4.112 LSR_FORCE_OPEN..................................................................................................................................527
4.113 LSR_INVALID..........................................................................................................................................528
4.114 LTI..............................................................................................................................................................529
4.115 MAINBD_SUBBD_MISMATCH.............................................................................................................531
Issue 02 (2011-10-31)

xix
OptiX OSN 8800/6800/3800

Contents
4.116 MOD_COM_FAIL.....................................................................................................................................532
4.117 MODULE_ADJUST_FAIL.......................................................................................................................533
4.118 MODULE_COOLCUR_OVER.................................................................................................................534
4.119 MODULE_TEMP_OVER..........................................................................................................................535
4.120 MODULEFILE_UPDATE_FAIL..............................................................................................................536
4.121 MS_CROSSTR...........................................................................................................................................537
4.122 MS_REI......................................................................................................................................................538
4.123 MS_SNCP_PS............................................................................................................................................539
4.124 MS_SNCP_STA_INDI..............................................................................................................................540
4.125 MS_APS_INDI_EX...................................................................................................................................542
4.126 MULTI_RPL_OWNER..............................................................................................................................543
4.127 NEBD_XC_DIF.........................................................................................................................................544
4.128 NESF_LOST..............................................................................................................................................546
4.129 NESTATE_INSTALL................................................................................................................................546
4.130 NO_BD_PARA..........................................................................................................................................547
4.131 NO_BD_SOFT...........................................................................................................................................548
4.132 NO_ELABEL.............................................................................................................................................550
4.133 NODEID_MM............................................................................................................................................551
4.134 NTP_SYNC_FAIL.....................................................................................................................................552
4.135 NULL_SEND.............................................................................................................................................553
4.136 OCH_FDI...................................................................................................................................................554
4.137 OCH_FDI-O...............................................................................................................................................554
4.138 OCH_FDI-P................................................................................................................................................555
4.139 OCH_LOS-P...............................................................................................................................................556
4.140 OCH_OCI...................................................................................................................................................557
4.141 OCH_SSF...................................................................................................................................................558
4.142 OCH_SSF-O...............................................................................................................................................559
4.143 OCH_SSF-P................................................................................................................................................560
4.144 ODU_AIS...................................................................................................................................................561
4.145 ODU_LCK..................................................................................................................................................562
4.146 ODU_OCI...................................................................................................................................................563
4.147 ODU_SNCP_STA_INDI............................................................................................................................564
4.148 ODUk_LOFLOM.......................................................................................................................................566
4.149 ODUk_PM_LCK........................................................................................................................................567
4.150 ODUk_PM_OCI.........................................................................................................................................568
4.151 ODUk_PM_TIM........................................................................................................................................569
4.152 ODUk_TCMn_AIS....................................................................................................................................571
4.153 ODUk_TCMn_BDI....................................................................................................................................572
4.154 ODUk_TCMn_DEG...................................................................................................................................573
4.155 ODUk_TCMn_EXC...................................................................................................................................575
4.156 ODUk_TCMn_LCK...................................................................................................................................576
4.157 ODUk_TCMn_LTC...................................................................................................................................577
Issue 02 (2011-10-31)

xx
OptiX OSN 8800/6800/3800

Contents
4.158 ODUk_TCMn_OCI....................................................................................................................................578
4.159 ODUk_TCMn_SSF....................................................................................................................................579
4.160 ODUk_TCMn_TIM....................................................................................................................................580
4.161 ODUKSP_PS..............................................................................................................................................582
4.162 ODUKSP_STA_INDI................................................................................................................................583
4.163 OH_LOOP..................................................................................................................................................585
4.164 OLP_PS......................................................................................................................................................586
4.165 OLP_STA_INDI.........................................................................................................................................588
4.166 OMS_BDI...................................................................................................................................................589
4.167 OMS_BDI-O..............................................................................................................................................590
4.168 OMS_BDI-P...............................................................................................................................................591
4.169 OMS_FDI-O...............................................................................................................................................592
4.170 OMS_FDI-P................................................................................................................................................593
4.171 OMS_LOS-P..............................................................................................................................................594
4.172 OMS_SSF...................................................................................................................................................595
4.173 OMS_SSF-O...............................................................................................................................................596
4.174 OMS_SSF-P...............................................................................................................................................597
4.175 OOL............................................................................................................................................................598
4.176 OOS_LOST................................................................................................................................................599
4.177 OPA_FAIL_INDI.......................................................................................................................................600
4.178 OPU1_MSIM..............................................................................................................................................601
4.179 OPU1_VCAT_SQM...................................................................................................................................602
4.180 OPU1_VCAT_VcPLM..............................................................................................................................603
4.181 OPU2_MSIM..............................................................................................................................................604
4.182 OPU3_MSIM..............................................................................................................................................604
4.183 OPUk_PLM................................................................................................................................................605
4.184 OSC_BDI....................................................................................................................................................606
4.185 OSC_DEG..................................................................................................................................................607
4.186 OSC_RDI....................................................................................................................................................608
4.187 OTS_BDI....................................................................................................................................................609
4.188 OTS_BDI-O................................................................................................................................................610
4.189 OTS_BDI-P................................................................................................................................................611
4.190 OTS_LOS-O...............................................................................................................................................612
4.191 OTS_LOS-P................................................................................................................................................613
4.192 OTS_TIM...................................................................................................................................................614
4.193 OTU_AIS....................................................................................................................................................615
4.194 OTU_LOF..................................................................................................................................................616
4.195 OTU_LOM.................................................................................................................................................617
4.196 OTUk_AIS..................................................................................................................................................618
4.197 OTUk_BDI.................................................................................................................................................619
4.198 OTUk_DEG................................................................................................................................................620
4.199 OTUk_EXC................................................................................................................................................621
Issue 02 (2011-10-31)

xxi
OptiX OSN 8800/6800/3800

Contents
4.200 OTUk_LOM...............................................................................................................................................622
4.201 OTUk_TIM.................................................................................................................................................623
4.202 OUT_PWR_LOW......................................................................................................................................625
4.203 OWSP_PS...................................................................................................................................................626
4.204 OWSP_STA_INDI.....................................................................................................................................627
4.205 PATCH_ACT_TIMEOUT.........................................................................................................................629
4.206 PATCH_DEACT_TIMEOUT....................................................................................................................630
4.207 PATCH_PKGERR.....................................................................................................................................631
4.208 PM_BDI......................................................................................................................................................632
4.209 PM_BEI......................................................................................................................................................633
4.210 PM_BIP8_OVER.......................................................................................................................................634
4.211 PM_BIP8_SD.............................................................................................................................................635
4.212 PM_TIM.....................................................................................................................................................637
4.213 PORTSWITCH_FAIL................................................................................................................................638
4.214 POWER_ABNORMAL.............................................................................................................................638
4.215 POWER_DIFF_OVER...............................................................................................................................640
4.216 PRBS_LSS..................................................................................................................................................641
4.217 PUM_BCM_ALM......................................................................................................................................642
4.218 PUM_TEM_ALM......................................................................................................................................643
4.219 R_LOC........................................................................................................................................................644
4.219.1 R_LOC (OCS)...................................................................................................................................644
4.219.2 R_LOC (OTN)...................................................................................................................................645
4.220 RELAY_ALARM_CRITICAL .................................................................................................................646
4.221 RELAY_ALARM_IGNORE ....................................................................................................................647
4.222 RELAY_ALARM_MAJOR ......................................................................................................................649
4.223 RELAY_ALARM_MINOR ......................................................................................................................650
4.224 REM_SD....................................................................................................................................................651
4.225 RL_CRITICAL_HI....................................................................................................................................652
4.226 RL_CRITICAL_LOW................................................................................................................................653
4.227 RS_CROSSTR............................................................................................................................................654
4.228 RTC_FAIL..................................................................................................................................................655
4.229 S1_SYN_CHANGE...................................................................................................................................656
4.230 SCC_LOC...................................................................................................................................................657
4.231 SEC_RADIUS_FAIL.................................................................................................................................658
4.232 SERVICE_TYPE_EXCEED_LICENSE...................................................................................................659
4.233 SERVICE_CAPACITY_EXCEED_LICENSE.........................................................................................660
4.234 SHELF_AREA_POWER_OVER..............................................................................................................661
4.235 SPAN_LOSS_HIGH..................................................................................................................................662
4.236 SPAN_LOSS_LOW...................................................................................................................................663
4.237 SLAVE_WORKING..................................................................................................................................664
4.238 SM_BDI......................................................................................................................................................666
4.239 SM_BEI......................................................................................................................................................667
Issue 02 (2011-10-31)

xxii
OptiX OSN 8800/6800/3800

Contents
4.240 SM_BIP8_OVER.......................................................................................................................................668
4.241 SM_BIP8_SD.............................................................................................................................................669
4.242 SM_IAE......................................................................................................................................................670
4.243 SM_TIM.....................................................................................................................................................671
4.244 SNCP_FAIL...............................................................................................................................................672
4.245 SO_SK_MISMATCH................................................................................................................................673
4.246 SPEED_OVER...........................................................................................................................................675
4.247 STORM_CUR_QUENUM_OVER............................................................................................................676
4.248 SUBRACK_COMM_PS............................................................................................................................676
4.249 SUBRACK_ID_MISMATCH....................................................................................................................677
4.250 SUBRACK_LOOP.....................................................................................................................................678
4.251 SUBRACK_TYPE_MISMATCH..............................................................................................................679
4.252 SUM_INPWR_HI......................................................................................................................................680
4.253 SW_SNCP_PS............................................................................................................................................682
4.254 SW_SNCP_STA_INDI..............................................................................................................................683
4.255 SWDL_ACTIVATED_TIMEOUT............................................................................................................684
4.256 SWDL_AUTOMATCH_INH....................................................................................................................685
4.257 SWDL_BD_EXCLUDE.............................................................................................................................686
4.258 SWDL_CHGMNG_NOMATCH...............................................................................................................687
4.259 SWDL_COMMIT_FAIL............................................................................................................................688
4.260 SWDL_INPROCESS.................................................................................................................................689
4.261 SWDL_PKG_NOBDSOFT........................................................................................................................690
4.262 SWDL_PKGVER_MM..............................................................................................................................691
4.263 SWDL_ROLLBACK_FAIL......................................................................................................................691
4.264 SYN_BAD..................................................................................................................................................692
4.265 SYNC_C_LOS...........................................................................................................................................694
4.266 SYNC_DISABLE.......................................................................................................................................695
4.267 SYNC_F_M_SWITCH..............................................................................................................................696
4.268 SYNC_LOCKOFF.....................................................................................................................................698
4.269 SYNC_FAIL...............................................................................................................................................699
4.270 SYSPARA_CFDB_NOSAME...................................................................................................................700
4.271 T_LOSEX...................................................................................................................................................701
4.272 T_SLIP........................................................................................................................................................702
4.273 TEM_HA....................................................................................................................................................702
4.274 TEM_LA....................................................................................................................................................703
4.275 TEST_STATUS..........................................................................................................................................704
4.276 THUNDERALM........................................................................................................................................705
4.277 TIME_LOS.................................................................................................................................................706
4.278 TIME_NO_TRACE_MODE......................................................................................................................707
4.279 TR_LOC.....................................................................................................................................................709
4.280 TU_AIS_VC3.............................................................................................................................................710
4.281 TU_LOP_VC3............................................................................................................................................711
Issue 02 (2011-10-31)

xxiii
OptiX OSN 8800/6800/3800

Contents
4.282 VCAT_LOA...............................................................................................................................................712
4.282.1 VCAT_LOA (OCS)...........................................................................................................................713
4.282.2 VCAT_LOA (OTN)..........................................................................................................................714
4.283 VCAT_LOM_VC3.....................................................................................................................................714
4.284 VCAT_LOM_VC4.....................................................................................................................................715
4.285 VLAN_SNCP_PS.......................................................................................................................................717
4.286 VOA_ADJUST_FAIL................................................................................................................................718
4.287 VOADATA_MIS.......................................................................................................................................719
4.288 W_R_FAIL.................................................................................................................................................720
4.289 WAVE_ADD_ABN...................................................................................................................................721
4.290 WAVE_DROP_ABN.................................................................................................................................722
4.291 WAVEDATA_MIS....................................................................................................................................723
4.292 WAVELEN_OVER....................................................................................................................................724
4.293 XC_UNSWITCH........................................................................................................................................725
5 Performance Event List.............................................................................................................727

5.1 Product Performance Event List.....................................................................................................................728
5.1.1 Performance Event of Check and Error Correction...............................................................................728
5.1.2 Performance Event of Pointer Justification...........................................................................................729
5.1.3 Performance Event of Equipment Function..........................................................................................729
5.1.4 Performance Event of Multiplex Section Bit Error...............................................................................733
5.1.5 Performance Event of Regenerator Section Bit Error...........................................................................733
5.1.6 Performance Event of Higher Order Path Bit Error..............................................................................734
5.1.7 Performance Event of Lower Order Path Bit Error...............................................................................734
5.1.8 Performance Event of OTN...................................................................................................................735
5.1.9 Performance Event List of RMON Function.........................................................................................745
5.1.10 TCM Performance Event ....................................................................................................................751
5.1.11 Performance Event of FC....................................................................................................................751
5.2 Board Performance Event List.......................................................................................................................752
5.2.1 CRPC Board Performance Event List...................................................................................................752
5.2.2 DAS1 Board Performance Event List...................................................................................................752
5.2.3 D40V Board Performance Event List....................................................................................................753
5.2.4 D40 Board Performance Event List.......................................................................................................753
5.2.5 DCP Board Performance Event List......................................................................................................754
5.2.6 EGSH Board Performance Event List...................................................................................................754
5.2.7 EAS2 Board Performance Event List....................................................................................................755
5.2.8 ECOM Board Performance Event List..................................................................................................756
5.2.9 ELQX Board Performance Event List...................................................................................................756
5.2.10 ENQ2 Board Performance Event List.................................................................................................758
5.2.11 FIU Board Performance Event List.....................................................................................................760
5.2.12 HSC1 Board Performance Event List..................................................................................................760
5.2.13 HBA Board Performance Event List...................................................................................................760
5.2.14 ITL Board Performance Event List.....................................................................................................760
Issue 02 (2011-10-31)

xxiv
OptiX OSN 8800/6800/3800

Contents
5.2.15 L4G Board Performance Event List....................................................................................................761

5.2.16 LDGD Board Performance Event List................................................................................................762
5.2.17 LDGS Board Performance Event List.................................................................................................764
5.2.18 LDM Board Performance Event List...................................................................................................766
5.2.19 LDMD Board Performance Event List................................................................................................767
5.2.20 LDMS Board Performance Event List................................................................................................769
5.2.21 LDX Board Performance Event List...................................................................................................771
5.2.22 LEM24 Board Performance Event List...............................................................................................772
5.2.23 LEX4 Board Performance Event List..................................................................................................773
5.2.24 LOA Board Performance Event List...................................................................................................774
5.2.25 LOG Board Performance Event List...................................................................................................776
5.2.26 LOM Board Performance Event List...................................................................................................778
5.2.27 LQMD Board Performance Event List................................................................................................780
5.2.28 LQMS Board Performance Event List................................................................................................783
5.2.29 LQM Board Performance Event List...................................................................................................785
5.2.30 LSQ Board Performance Event List....................................................................................................787
5.2.31 LSXLR Board Performance Event List...............................................................................................788
5.2.32 LSXL Board Performance Event List.................................................................................................789
5.2.33 LSXR Board Performance Event List.................................................................................................790
5.2.34 LSX Board Performance Event List....................................................................................................791
5.2.35 LWX2 Board Performance Event List................................................................................................793
5.2.36 LWXD Board Performance Event List...............................................................................................793
5.2.37 LWXS Board Performance Event List................................................................................................793
5.2.38 M40V Board Performance Event List.................................................................................................794
5.2.39 M40 Board Performance Event List....................................................................................................794
5.2.40 MCA4 Board Performance Event List................................................................................................794
5.2.41 MCA8 Board Performance Event List................................................................................................795
5.2.42 MR8V Board Performance Event List................................................................................................795
5.2.43 ND2 Board Performance Event List....................................................................................................795
5.2.44 NQ2 Board Performance Event List....................................................................................................802
5.2.45 NPO2 Board Performance Event List.................................................................................................808
5.2.46 NPO2E Board Performance Event List...............................................................................................810
5.2.47 NS2 Board Performance Event List....................................................................................................811
5.2.48 NS3 Board Performance Event List....................................................................................................817
5.2.49 OAU1 Board Performance Event List.................................................................................................822
5.2.50 OBU1 Board Performance Event List.................................................................................................822
5.2.51 OBU2 Board Performance Event List.................................................................................................822
5.2.52 OLP Board Performance Event List....................................................................................................823
5.2.53 OPM8 Board Performance Event List.................................................................................................823
5.2.54 PTQX Board Performance Event List.................................................................................................823
5.2.55 RDU9 Board Performance Event List.................................................................................................825
5.2.56 RMU9 Board Performance Event List................................................................................................825
Issue 02 (2011-10-31)

xxv
OptiX OSN 8800/6800/3800

Contents
5.2.57 ROAM Board Performance Event List...............................................................................................825

5.2.58 SCC Board Performance Event List....................................................................................................826
5.2.59 SC1 Board Performance Event List.....................................................................................................826
5.2.60 SC2 Board Performance Event List.....................................................................................................826
5.2.61 SFD64 Board Performance Event List................................................................................................826
5.2.62 SF64 Board Performance Event List...................................................................................................827
5.2.63 SF64A Board Performance Event List................................................................................................828
5.2.64 SL64 Board Performance Event List...................................................................................................829
5.2.65 SLD64 Board Performance Event List................................................................................................830
5.2.66 SLH41 Board Performance Event List................................................................................................830
5.2.67 SLO16 Board Performance Event List................................................................................................831
5.2.68 SLQ16 Board Performance Event List................................................................................................831
5.2.69 SLQ64 Board Performance Event List................................................................................................832
5.2.70 ST2 Board Performance Event List.....................................................................................................833
5.2.71 STG Board Performance Event List....................................................................................................833
5.2.72 SXM Board Performance Event List...................................................................................................833
5.2.73 SXH Board Performance Event List...................................................................................................833
5.2.74 TBE Board Performance Event List....................................................................................................834
5.2.75 TDC Board Performance Event List...................................................................................................835
5.2.76 TDG Board Performance Event List...................................................................................................835
5.2.77 TDX Board Performance Event List...................................................................................................836
5.2.78 THA Board Performance Event List...................................................................................................842
5.2.79 TMX Board Performance Event List...................................................................................................844
5.2.80 TOA Board Performance Event List...................................................................................................845
5.2.81 TOG Board Performance Event List...................................................................................................847
5.2.82 TOM Board Performance Event List...................................................................................................848
5.2.83 TQM Board Performance Event List...................................................................................................851
5.2.84 TQS Board Performance Event List....................................................................................................854
5.2.85 TQX Board Performance Event List...................................................................................................855
5.2.86 TSXL Board Performance Event List.................................................................................................861
5.2.87 VA1 Board Performance Event List....................................................................................................864
5.2.88 VA4 Board Performance Event List....................................................................................................864
5.2.89 WMU Board Performance Event List.................................................................................................864
5.2.90 WSD9 Board Performance Event List.................................................................................................864
5.2.91 WSM9 Board Performance Event List................................................................................................865
5.2.92 WSMD2 Board Performance Event List.............................................................................................865
5.2.95 XCH Board Performance Event List...................................................................................................865
5.2.96 XCM Board Performance Event List..................................................................................................866
5.2.97 XCT Board Performance Event List...................................................................................................866
6 Performance Event Processing................................................................................................867

Issue 02 (2011-10-31)

xxvi
OptiX OSN 8800/6800/3800

Contents
6.1 AUPJCHIGH..................................................................................................................................................872
6.2 AUPJCLOW...................................................................................................................................................873
6.3 AUPJCNEW...................................................................................................................................................874
6.4 BCV................................................................................................................................................................875
6.5 CCV................................................................................................................................................................875
6.6 CRC4ES..........................................................................................................................................................876
6.7 CRC4FEES.....................................................................................................................................................877
6.8 CRC4FESES...................................................................................................................................................878
6.9 CRC4FEUAS..................................................................................................................................................879
6.10 CRC4SES.....................................................................................................................................................879
6.11 CRC4UAS....................................................................................................................................................880
6.12 EDTMP.........................................................................................................................................................881
6.13 EDTPL..........................................................................................................................................................882
6.14 ENVTMP......................................................................................................................................................883
6.15 FEC_AFT_COR_ER....................................................................................................................................883
6.16 FEC_AFT_COR_ERAVR............................................................................................................................884
6.17 FEC_AFT_CORER_FLOAT.......................................................................................................................885
6.18 FEC_BEF_COR_ER....................................................................................................................................886
6.19 FEC_BEF_COR_ERAVR............................................................................................................................887
6.20 FEC_BEF_CORER_FLOAT.......................................................................................................................888
6.21 FEC_COR_0BIT_CNT................................................................................................................................888
6.22 FEC_COR_1BIT_CNT................................................................................................................................889
6.23 FEC_COR_BYTE_CNT..............................................................................................................................890
6.24 FEC_UNCOR_BLOCK_CNT.....................................................................................................................890
6.25 HPBBE.........................................................................................................................................................891
6.26 HPCSES........................................................................................................................................................892
6.27 HPES............................................................................................................................................................893
6.28 HPFEBBE.....................................................................................................................................................894
6.29 HPFECSES...................................................................................................................................................895
6.30 HPFEES........................................................................................................................................................896
6.31 HPFESES......................................................................................................................................................897
6.32 HPFEUAS....................................................................................................................................................898
6.33 HPSES..........................................................................................................................................................899
6.34 HPUAS.........................................................................................................................................................900
6.35 ICCLC..........................................................................................................................................................901
6.36 ICTMP..........................................................................................................................................................902
6.37 LSBIAS........................................................................................................................................................903
6.38 LSBISA........................................................................................................................................................904
6.39 LSCLC..........................................................................................................................................................905
6.40 LSIOP...........................................................................................................................................................906
6.41 LSOOP..........................................................................................................................................................907
6.42 LSTMP.........................................................................................................................................................908
Issue 02 (2011-10-31)

xxvii
OptiX OSN 8800/6800/3800

Contents
6.43 MSBBE.........................................................................................................................................................909
6.44 MSCSES.......................................................................................................................................................910
6.45 MSES............................................................................................................................................................911
6.46 MSFEBBE....................................................................................................................................................912
6.47 MSFECSES..................................................................................................................................................912
6.48 MSFEES.......................................................................................................................................................913
6.49 MSFESES.....................................................................................................................................................914
6.50 MSFEUAS....................................................................................................................................................915
6.51 MSSES..........................................................................................................................................................916
6.52 MSUAS........................................................................................................................................................917
6.53 ODU2PMBIP8..............................................................................................................................................918
6.54 ODUk_PM_BBE..........................................................................................................................................919
6.55 ODUk_PM_BBER.......................................................................................................................................919
6.56 ODUk_PM_ES.............................................................................................................................................920
6.57 ODUk_PM_FEBBE.....................................................................................................................................921
6.58 ODUk_PM_FEBBER...................................................................................................................................922
6.59 ODUk_PM_FEES........................................................................................................................................923
6.60 ODUk_PM_FESES......................................................................................................................................923
6.61 ODUk_PM_FESESR....................................................................................................................................924
6.62 ODUk_PM_FEUAS.....................................................................................................................................925
6.63 ODUk_PM_SES...........................................................................................................................................926
6.64 ODUk_PM_SESR........................................................................................................................................926
6.65 ODUk_PM_UAS..........................................................................................................................................927
6.66 ODUk_TCMn_BBE.....................................................................................................................................928
6.67 ODUk_TCMn_BBER..................................................................................................................................929
6.68 ODUk_TCMn_BIAES.................................................................................................................................930
6.69 ODUk_TCMn_ES........................................................................................................................................930
6.70 ODUk_TCMn_FEBBE................................................................................................................................931
6.71 ODUk_TCMn_FEBBER..............................................................................................................................932
6.72 ODUk_TCMn_FEES....................................................................................................................................933
6.73 ODUk_TCMn_FESES.................................................................................................................................933
6.74 ODUk_TCMn_FESESR...............................................................................................................................934
6.75 ODUk_TCMn_FEUAS................................................................................................................................935
6.76 ODUk_TCMn_IAES....................................................................................................................................935
6.77 ODUk_TCMn_SES......................................................................................................................................936
6.78 ODUk_TCMn_SESR...................................................................................................................................937
6.79 ODUk_TCMn_UAS.....................................................................................................................................937
6.80 OOPRL.........................................................................................................................................................938
6.81 OSC_BBE.....................................................................................................................................................939
6.82 OSC_BBER..................................................................................................................................................940
6.83 OSC_BIAES.................................................................................................................................................940
6.84 OSC_ES........................................................................................................................................................941
Issue 02 (2011-10-31)

xxviii
OptiX OSN 8800/6800/3800

Contents
6.85 OSC_FEBBE................................................................................................................................................941
6.86 OSC_FEBBER.............................................................................................................................................942
6.87 OSC_FEES...................................................................................................................................................943
6.88 OSC_FESES.................................................................................................................................................943
6.89 OSC_FESESR..............................................................................................................................................944
6.90 OSC_FEUAS................................................................................................................................................945
6.91 OSC_IAES....................................................................................................................................................945
6.92 OSC_SES......................................................................................................................................................946
6.93 OSC_SESR...................................................................................................................................................947
6.94 OSC_UAS....................................................................................................................................................947
6.95 OSPICCV.....................................................................................................................................................948
6.96 OSPITMP.....................................................................................................................................................949
6.97 OTU2SMBIP8..............................................................................................................................................950
6.98 OTUk_BBE..................................................................................................................................................950
6.99 OTUk_BBER................................................................................................................................................951
6.100 OTUk_ES...................................................................................................................................................952
6.101 OTUk_FEBBE............................................................................................................................................953
6.102 OTUk_FEBBER.........................................................................................................................................954
6.103 OTUk_FEES...............................................................................................................................................954
6.104 OTUk_FESES............................................................................................................................................955
6.105 OTUk_FESESR..........................................................................................................................................956
6.106 OTUk_FEUAS...........................................................................................................................................957
6.107 OTUk_SES.................................................................................................................................................957
6.108 OTUk_SESR..............................................................................................................................................958
6.109 OTUk_UAS................................................................................................................................................959
6.110 PCLSOP......................................................................................................................................................960
6.111 PCLSSN......................................................................................................................................................961
6.112 PCLSWL....................................................................................................................................................961
6.113 PCLSWLO..................................................................................................................................................962
6.114 RPL.............................................................................................................................................................963
6.115 RSBBE........................................................................................................................................................964
6.116 RSCSES......................................................................................................................................................964
6.117 RSES...........................................................................................................................................................965
6.118 RSOFS........................................................................................................................................................966
6.119 RSOOF.......................................................................................................................................................967
6.120 RSSES........................................................................................................................................................968
6.121 RSUAS.......................................................................................................................................................969
6.122 SUMIOP.....................................................................................................................................................970
6.123 SUMOOP....................................................................................................................................................971
6.124 TLB.............................................................................................................................................................972
6.125 TPL.............................................................................................................................................................973
6.126 VC3BBE.....................................................................................................................................................974
Issue 02 (2011-10-31)

xxix
OptiX OSN 8800/6800/3800

Contents
6.127 VC3CSES...................................................................................................................................................975
6.128 VC3ES........................................................................................................................................................977
6.129 VC3FEBBE................................................................................................................................................979
6.130 VC3FECSES..............................................................................................................................................980
6.131 VC3FEES...................................................................................................................................................981
6.132 VC3FESES.................................................................................................................................................982
6.133 VC3FEUAS................................................................................................................................................983
6.134 VC3SES......................................................................................................................................................985
6.135 VC3UAS.....................................................................................................................................................986
6.136 WCV...........................................................................................................................................................987
6.137 XCSTMP....................................................................................................................................................988
7 Event List.....................................................................................................................................990
8 Event Processing........................................................................................................................993
8.1 EAPE abnormal event notification.................................................................................................................994
8.2 EAPE adjustment result event notification.....................................................................................................995
8.3 OWSP abnormal event...................................................................................................................................998
8.4 ODUk SPRing abnormal event.....................................................................................................................1001
8.5 RMON performance value is above the upper limit.....................................................................................1003
8.6 RMON module performance value is lower than the lower threshold.........................................................1005
8.7 1+1 Equipment Level Protection Switching Event Report..........................................................................1007
A Glossary....................................................................................................................................1009
Issue 02 (2011-10-31)

xxx
OptiX OSN 8800/6800/3800

1 Overview
Overview
About This Chapter

This topic describes the meaning and indicator status of the alarms of four levels, and the
meaning, range and severity of the alarms in different categories. Describes different types of
performance event, the alarm signal flow of the OTU unit and the suppression relationship of
alarms.
1.1 Alarm Level
This section respectively describes the meaning, influence and indicator status of the alarms of
four levels.
1.2 Alarm Category
This section describes the meaning and range of alarms in different categories.
1.3 Performance Event Category
Performance events can be classified into ten categories according to the function monitored by
a performance event. Among these performance events, Performance Event of Higher Order
Path Bit Error, Lower Order Path Bit Error and Pointer Justification are supported only by the
OptiX OSN 8800.
1.4 Alarm Signal Flow
This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.5 Suppression Relationship of Alarms
This section describes the rules of alarm suppression and provides the suppression relationship
figure of common alarms. The efficiency for handling the alarms can be enhanced due to the
alarm suppression.
1.6 Performance Event Suppression by Alarms
An optical interface can report several alarms and performance events. Some performance events
are not important for the maintenance engineer.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
1.1 Alarm Level

This section respectively describes the meaning, influence and indicator status of the alarms of
four levels.
The alarm level is used to identify the severity, importance and urgency of the alarms. The alarms
can be classified into the following four levels in the sequence of decreasing severity: critical
alarm, major alarm, minor alarm and warning alarm.
l
Critical alarm: The alarm needs to be handled immediately, otherwise the system would
be down.
Major alarm: The alarm needs to be handled in time, otherwise some important functions
would not be performed.
Minor alarm: The alarm is used to inform the maintenance personnel for locating the alarm
causes and removing the incipient fault.
Warning alarm: The alarm need not be handled. The maintenance personnel only needs to
know the running status of the equipment.
For the meaning and corresponding indicator status on the board of the alarms of the four levels,
refer to the Table 1-1.
Table 1-1 Alarm level
Alarm Level
Definition
Indicator Status
Critical alarm
Global fault alarms and event alarms that

would cause system down.
The SRV is on (red).
Major alarm
Faulty alarms and event alarms of partial

boards or lines.
The SRV is on (red).
Minor alarm
General fault alarms and event alarms that are

used to describe whether the board or line
works properly.
The SRV is on (yellow).
Warning
alarm
Fault alarms and event alarms for warning.
The alarm indicator is off.
1.2 Alarm Category

This section describes the meaning and range of alarms in different categories.
The alarms can be classified into the following six categories. For details, see Table 1-2.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Table 1-2 Alarm category

Alarm
Category
Definition
Example
Communication
alarm
Alarms related to the NE

communication, ECC
communication, and
communication with optical
signals
The alarm is generated when the

NE communication is interrupted
or the optical signal is lost.
Process alarm
Alarms related to the software

processing and anomalies

database is in error or the NE is in
the installing state.
Equipment alarm
Alarms related to the hardware of

the equipment

laser is faulty or the optical port is
looped back.
Service alarm
Alarms related to the service status

and network service quality

signals at the line layer are
degraded.
Environment
alarm
Alarms related to the power supply

system and environment of the
equipment room

temperature of the power module is
excessively high.
Security alarm
Alarms related to the network

management and the NE security

NE user is not logged in.
1.3 Performance Event Category

Performance events can be classified into ten categories according to the function monitored by
a performance event. Among these performance events, Performance Event of Higher Order
Path Bit Error, Lower Order Path Bit Error and Pointer Justification are supported only by the
OptiX OSN 8800.
The performance event is an important parameter that reflects the working performance of the
equipment. The knowledge of the generation principle, related boards and alarms of the
performance event is helpful to find incipient faults in routine maintenance and analyze the fault.
The categories of the performance events are shown in the Table 1-3.
Performance events and alarms are related. When the number of the performance events exceeds
the preset threshold, the related alarm is triggered. Hence, when a performance event is
generated, check whether the related alarm is generated and handle the performance event by
referring to the handling procedure of the related alarm.
The OptiX OSN 8800/OptiX OSN 6800/OptiX OSN 3800 provides the remote monitoring
function by which the network can monitor the transmission of data in different network
segments. Remote monitoring (RMON) provides flexible detection modes and control
mechanism to cater for the needs of different kinds of network. The RMON defines a serial of
statistic formats and functions to realize the data exchange among the control stations and
detection stations in compliance with the RMON standard. The RMON also provides error
diagnosis, planning and information receiving of the performance events of the entire network.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Table 1-3 Performance event category

Performance event category
Definition
Performance event related to the

bit errors of the regenerator
section
The performance event generated when bit errors occur at

the regenerator section in the SDH frames of the signals
on the WDM side or the client side of the board.

bit errors of the multiplex
section
The performance event generated when bit errors occur in

the multiplex section in the SDH frames of the signals on
the WDM side or the client side of the board.
Performance Event of Higher

Order Path Bit Error
The performance event generated when bit errors occur on

higher order path.
Performance Event of Lower

Order Path Bit Error
The performance event generated when bit errors occur on

lower order path.
Performance Event of Pointer

Justification
The performance event generated when the board

performs pointer justification

check and error correction
The performance event generated when the board

performs service check or bit error correction.

equipment function
The performance event generated when the optical power,

the working current of the laser or other factors about the
running environment exceed the threshold.
OTN performance event
The performance event generated when bit errors occur in

the PM, TCM or SM segment of the OTN service.
RMON performance event
The performance event related to the mode in which the

board transmits or receives the data packets, the number
and quality of packets in different lengths transmitted or
received.
FC performance event
The performance event generated when parameter changes

in FC.
1.4 Alarm Signal Flow

This section describes the alarm signal flow of the OTU. It describes the generation, detection,
and transmission of alarms when the OTU accesses different types of signals.
1.4.1 Overview
This section describes the seven types of scenarios of the alarm signal flow, SF, SD, and basic
concepts in the alarm signal flow diagram.
Classification
For a WDM product, the detection and transmission of alarms vary according to the type of the
signals that are accessed into the OTU. The OTU is classified into the following types:
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Non-convergent OTU
It refers to an OTU that converts one channel of client service signals.
Convergent OTU
It refers to an OTU that converges and converts multiple channels of client service signals.
Regenerating OTU
It refers to an OTU that regenerates the corresponding service signals at an intermediate
station.
According to the type of the OTU and the type of the signals accessed by the OTU, the following
seven situations are defined in this section:
l
Non-convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard SDH signals.
Non-convergent OTU processing standard OTN signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard OTN signals.
Convergent OTU processing standard SDH signals

This section describes the alarm signal flow when the convergent OTU processes standard
SDH signals.
Convergent OTU processing standard OTN signals

This section describes the alarm signal flow when the convergent OTU processes standard
OTN signals.
Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
OTU with the cross-connect function

This section describes the alarm signal flow of the OTU with the cross-connect function.
OTU processing GE signals

This section describes the alarm signal flow when the OTU processes GE signals.
SF and SD
SF is a signal failure event, and SD is a signal degrade event. The SF and SD events are trigger
conditions of a protection switching. Whether the SD event is used as a trigger condition,
however, it can be set by the user.
The SF and SD events are marked in the alarm signal flow diagrams in this section. These events
are generated when the equipment configured with network protection detects a certain alarm.
If the equipment is not configured with the network protection, the SF and SD events are not
detected or reported.
Concepts
The following concepts are used in the diagrams in this section:
l
WDM side: It is the WDM side of the OTU.
Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Middle part: It is the middle part between the WDM side and the client side. It is a virtual
concept, and therefore is not displayed on the U2000. This concept is introduced to describe
the alarm detection mechanism.
N#1: It indicates channel 1 at optical port N on the OTU. For example, the client-side optical
ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical port of the
LQMD unit is numbered 1. Then, 3#1 indicates channel 1 at client-side optical port 3.
1#N: It indicates channel N at WDM-side optical port 1 on the OTU. For example, 1#3
indicates channel 3 at WDM-side optical port 1.
1.4.2 Non-Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the non-convergent OTU processes standard
SDH signals.
Figure 1-1 and Figure 1-2 show the alarm signal flows when the non-convergent OTU processes
NOTE
The ALS function of the OTU shown in the figures in this section is not enabled.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A
Client-side
Station B
WDM-side
WDM-side
Client device
Client-side
Client-device
SF
R_LOS
R_LOS
R_LOF
R_LOF
R_LOF
R_LOF
MS_AIS
MS_AIS
MS_AIS
B1_SD/
B1_EXC
B1_SD/
B1_EXC
R_LOF
SF
R_LOF
MS_AIS
SD
BI errors
B1errors
SD
PM BIP8 errors
ODUk_PM_DEG/
ODUk_PM_EXC
PM remote BER
performance events
SM BIP8 Errors
Errors
SD
OTUk_DEG/
OTUk_EXC
Errors
OTUk remote BER

performance events
OTUk_AIS
SF
OTUk_AIS
R_LOF
ODUk_PM_BDI
&OTUk_BDI
OTUk_LOM
SD
OTUk_AIS
R_OOF
ODUk_PM_BDI
&OTUk_BDI
SF: SF event detecting
xxx
SD: SD event detecting
Alarm processing
Detects and reports the xxx alarm or performance event
This section describes the alarm signal flow by analyzing how the OTU processes the R_LOS
alarm and PM BIP8 errors. The alarm signal flows of other alarms are similar.
l
R_LOS
The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The client side of
the OTU at station B detects the REM_SF alarm. The alarm is then sent to the downstream
client device of station B, and the OTU reports the R_LOF alarm to the client device.
l
Issue 02 (2011-10-31)
PM BIP8 errors
OptiX OSN 8800/6800/3800

1 Overview
The OTU at station B detects PM BIP 8 errors on the WDM side. When the PM BIP 8
errors exceed the threshold, the ODUk_PM_DEG or ODUk_PM_EXC alarm is generated.
The number of errors determines which alarm is generated. In addition, the performance
events indicting ODUk PM remote bit errors are sent to the WDM side of upstream station
A. The bit errors are then sent to the client device (The bit errors cannot be sent to the
downstream station except that the PM BIP 8 errors are from the data inside). The alarms
related to bit errors are detected in the client device.
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
Station B
Station A
Client-side
WDM-side
WDM-side
MFAS frame discontinuous
Client-side
Client device
Client-device
OTUk_LOM
ODUk_PM_BDI
&OTUk_BDI
PM TTI byte mismatch
SF
ODUk_PM_TIM
R_LOF
ODUk_PM_BDI
SF
SM TTI byte mismatch
OTUk_TIM
R_LOF
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
Excessive bit errors before FEC
OTUk_LOF
OTUk_BDI
BEFFEC_EXC
SF
OTUk_LOF
R_LOF
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
SF
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
R_LOF
ODUk_PM_BDI
R_LOS
SF
R_LOS
R_LOF
ODUk_PM_BDI
&OTUk_BDI
xxx
Alarm processing
Detects and reports the xxx alarm
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
This section describes the alarm signal flow by analyzing how the OTU processes the
OTUk_LOF alarm. The alarm signal flows of other alarms are similar.
The WDM side of the OTU at station B detects the OTUk_LOF alarm. Then, the OTU sends
the ODUk_PM_BDI and OTUk_BDI alarms to the WDM side of upstream station A. In addition,
the alarm is then sent to the client side of station B. After the alarm is processed on the client
side, the R_LOF alarm is detected in the client device.
1.4.3 Non-Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the non-convergent OTU unit processes
Figure 1-3 and Figure 1-4 show the alarm signal flows when the non-convergent OTU processes
NOTE
The non-intrusive monitoring of the board shown in the figures in this section is enabled.
Issue 02 (2011-10-31)

OptiX OSN 8800/6800/3800

1 Overview
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
Station A
Client-side
R_LOS
Station B
WDM-side
WDM-side
Client-side
SF
ODUk_PM_AIS
R_LOS
Client device
Client-device
ODUk_PM_AIS
OTUk_BDI
SD
ODUk_PM_DEG/
ODUk_PM_EXC
PM BIP8 errors ODUk_PM_DEG/

ODUk_PM_EXC
PM BIP8 errors
SM BIP8 errors OTUk_DEG/

OTUk_EXC
OTUk remote BER
performance events
SM BIP8 errors
SD
OTUk_DEG/
OTUk_EXC
OTUk remote BER

performance events
PM BIP8 errors
OTUk_LOF
SD
ODUk_PM_DEG/
ODUk_PM_EXC
PM BIP8 errors
OTUk_LOF
SF
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_LOM
SF
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_AIS
SF
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_BDI
OTUk_LOM
OTUk_BDI
OTUk_AIS
OTUk_BDI
OTUk_LOF/
OTUk_LOM/
OTUk_AIS
SF
OTUk_LOF/
OTUk_LOM/
OTUk_AIS
ODUk_PM_AIS
OTUk_BDI
xxx
Alarm processing
This section describes the alarm signal flow by analyzing how the OTU unit processes the
R_LOS and OTUk_LOF alarms. The alarm signal flow of other alarms is similar.
l
R_LOS
The client side of the OTU at station A receives R_LOS signals. The R_LOS signals are
processed on the WDM side of the OTU and then are sent to station B. The WDM side of
the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated.
The event triggers a protection switching. The alarm is then sent to the downstream client
equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client
equipment.
OTUk_LOF
The OTUk_LOF alarm is detected on the WDM side of the OTU board at station B, and
station B sends the OTUk_BDI alarm to the WDM side of the OTU at the upstream station
A. At the same time, the alarm is then sent to the downstream station of station B, where
Issue 02 (2011-10-31)

10
OptiX OSN 8800/6800/3800

1 Overview
it is processed on the client side of the OTU. In this case, the ODUk_PM_AIS alarm is
detected in the client equipment. An SF event is generated on the WDM side of the OTU
at station B, and a service channel protection switching is triggered.
The client side of the OTU at station A receives OTUk_LOF signals. The OTU sends the
OTUk_BDI alarm to the upstream client equipment of station A. In addition, the LOF alarm
is processed on the WDM side of the OTU and then is sent to station B. The WDM side of
the OTU at station B detects the ODUk_PM_AIS alarm, and then an SF event is generated.
The event triggers a protection switching. The alarm is then sent to the downstream client
equipment of station B, and the OTU reports the ODUk_PM_AIS alarm to the client
equipment.
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
Station A
Client-side
Station B
WDM-side
WDM-side
Client-side
Client device
Client-device
The SF event is generated when the

SF TIM follow-up response is Enabled.
The SF event is generated when the
OTUk_TIM
SF TIM follow-up response is Enabled.
OTUk_TIM
OTUk_BDI
OTUk_BDI
OTUk_BDI
OTUk_BDI
OTUk_BDI
OTUk_BDI
Transparent transmission of all PM signals

ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
SF
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
R_LOS
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
SF
R_LOS
ODUk_PM_AIS
OTUk_BDI

xxx
Alarm processing
OTUk_TIM
After the OTU at station A receives the OTUk_TIM alarm on the client side, it sends the
OTUk_BDI alarm to the upstream station, but it does not send the OTUk_TIM alarm to
the downstream station. If the TIM is enabled in the subsequent action, an SF event is
generated and the WDM side of the OTU at station B reports the ODUk_PM_AIS alarm.
The ODUk_PM_AIS alarm is sent to the downstream and the client device reports this
alarm.
After the OTU at station B receives the OTUk_TIM alarm on the WDM side, this alarm is
not sent to the downstream if the TIM is not enabled in the subsequent action. If the TIM
Issue 02 (2011-10-31)

11
OptiX OSN 8800/6800/3800

1 Overview
is enabled in the subsequent action, an SF event is generated. After the client side of station
B processes the event, the client device reports the ODUk_PM_AIS alarm.
l
OTUk_BDI
The OTU detects the OTUk_BDI alarm from the upstream station. This alarm is not sent
to the downstream station.
ODUk_PM_TIM/ODUk_PM_BDI
The OTU transparently transmits all PM alarms.
ODUk_PM_AIS/ODUk_PM_LCK/ODUk_PM_OCI
The client side of the OTU at station A receives ODUk_PM_AIS, ODUk_PM_LCK, or
ODUk_PM_OCI signals. The signals are not processed and reported at the local station.
After the signals are sent to station B, the WDM side of the OTU at station B detects the
ODUk_PM_AIS, ODUk_PM_LCK, or ODUk_PM_OCI alarm. Then, an SF event is
generated. The event triggers a protection switching. The alarm is then sent to the
downstream client equipment of station B, and the OTU reports the ODUk_PM_AIS,
ODUk_PM_LCK, or ODUk_PM_OCI alarm to the client equipment.
R_LOS
The WDM side of the OTU at station B detects the R_LOS alarm. The OTU sends the
OTUk_BDI alarm to the WDM side of upstream station A. In addition, the alarm is then
sent to the client side of station B. After the alarm is processed on the client side, the
ODUk_PM_AIS alarm is detected in the client equipment.
An SF event is generated on the WDM side of the OTU at station B, and a protection
switching is triggered.
1.4.4 Convergent OTU Processing Standard SDH Signals

This section describes the alarm signal flow when the convergent OTU processes standard SDH
signals.
Figure 1-5 and Figure 1-6 show the alarm signal flows when the convergent OTU processes
NOTE
l In Figure 1-5, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side optical
ports of the LQMD are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD is
numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates channel N at
WDM-side optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port
1.
l Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and
therefore is not displayed on the U2000. This concept is introduced to describe the alarm detection
mechanism. In the middle part of the convergent OTU, the optical port numbers and channel numbers
of signals are reallocated.
NOTE
Issue 02 (2011-10-31)

12
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
R_LOS
Middle
Client device
Station B
Station A
Client-side
WDM-side
WDM-side
Client-side
Middle
Client-device
N#1 R_LOS
N#1 REM_SF
N#1 R_LOF
R_LOS
N#1 R_LOS
N#1 REM_SF
N#1 R_LOF
R_LOS
N#1 R_LOS
N#1 REM_SF
N#1 R_LOF
R_LOS
N#1 R_LOS
N#1 REM_SF
N#1 R_LOF
N#1 R_LOS
N#1 REM_SF
N#1 R_LOF
N#1 R_LOF
N#1 REM_SF
N#1 R_LOF
N#1 REM_SF
N#1 R_LOF
R_LOS
R_LOF
R_LOC
Errors
SF
N#1 R_LOC
SD
1#N BIT Errors
N#1 Errors
A
B
C
D
Errors
N#1 A
1#N A
N#1 B
1#N B
N#1 C
1#N C
N#1 D
1#N D
A, B, C, D are the others of the SDH alarms

SF:SF event detecting
xxx
SD:SD event detecting
Alarm processing
Detects and reports the xxx alarm.
This section describes the alarm signal flow through an example in which four client-side
services are accessed on the convergent OTU.
l
Four channels of R_LOS signals are accessed on the client side.

The OTU at station A accesses four channels of R_LOS signals on the client side. After
being processed in the middle part of the OTU at station A, the alarm signals are then sent
to station B. The REM_SF alarm is generated on the client side of station B. The R_LOF
alarm is detected in the client equipment.
One channel of R_LOS signals are accessed on the client side.

The OTU at station A accesses one channel of R_LOS signals on the client side, for
example, channel 1 at optical port 3. After being processed in the middle part and on the
WDM side of the OTU at station A and the WDM side of station B, the alarm signals are
then sent to the downstream station. The REM_SF alarm of channel 1 at optical port 3 is
generated on the client side of station B. The R_LOF alarm is detected in the client
equipment.
Non-R_LOS signals are accessed on the client side.

The signal flow of the R_LOF or the LOC is similar to that of the R_LOS.
When any other alarms are accessed, the same alarm is reported at each detection point in
the system.
Issue 02 (2011-10-31)

13
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
Station A
Client-side
Station B
Middle
WDM-side
WDM-side
Middle
Client device
Client-side
Client-device
R_LOF
R_LOS
R_LOF
SF
R_LOS
R_LOF
ODUk_PM_BDI&
OTUk_BDI
R_LOF
R_LOF
SF
OTUk_LOF/
OTUk_AIS OTUk_LOF/
OTUk_AIS
R_LOF
R_LOF
ODUk_PM_BDI&
OTUk_BDI
R_LOF
R_LOF
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
SF
R_LOF
ODUk_PM_AIS/
ODUk_PM_LCK/
ODUk_PM_OCI
R_LOF
ODUk_PM_BDI
R_LOF
Errors
SD
Errors
PM BIP8 errors ODUk_PM_DEG/

ODUk_PM_EXC
Errors
OTUk remote BER
performance events
Errors
Errors
SD
SM BIP8 errors
Errors
OTUk_DEG/
OTUk_EXC
Errors
PM remote BER
performance events
xxx
Errors
Alarm processing
l
Issue 02 (2011-10-31)
There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, or

ODUk_PM_LCK on the WDM side.
14
OptiX OSN 8800/6800/3800

1 Overview
The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU
sends the ODUk_PM_BDI and OTUk_BDI alarm to the WDM side of upstream station A.
In addition, the alarm is then sent to the client side of station B. After the alarm is processed
on the client side, the R_LOF alarm is detected in the client equipment.
l
There are bit error alarms on the WDM side.

The OTU at station B accesses and processes bit error alarm signals on the WDM side, and
then sends remote bit error performance events to the WDM side of upstream station A.
The bit error alarm is then sent to the client side of the downstream station B, and the bit
error alarm is detected in the client equipment.
An SD event is generated on the WDM side of the OTU at station B. In this case, users can
determine whether the SD event triggers a service channel protection switching through
proper configuration.
1.4.5 Convergent OTU Processing Standard OTN Signals

This section describes the alarm signal flow when the convergent OTU processes standard OTN
signals.
Figure 1-7 and Figure 1-8 show the alarm signal flows when the convergent OTU processes
NOTE
In Figure 1-7, N#1 indicates channel 1 at optical port N of the OTU. For example, the client-side optical
ports of the LQMD unit are numbered 3, 4, 5, and 6, and the WDM-side optical port of the LQMD unit is
numbered 1. Hence, 3#1 indicates channel 1 at client-side optical port 3. 1#N indicates channel N at WDMside optical port 1 on the OTU. For example, 1#3 indicates channel 3 at WDM-side optical port 1.
Middle part is the middle part between the WDM side and the client side. It is a virtual concept, and therefore
is not displayed on the U2000. This concept is introduced to describe the alarm detection mechanism. In
the middle part of the convergent OTU, the optical port number and channel number of signals are reallocated.
NOTE
Issue 02 (2011-10-31)

15
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
Station B
Station A
Client-side
Middle
WDM-side
WDM-side
Middle
R_LOS
SF
Inserts OTUk_BDI back N#1 R_LOS
N#1 ODUk_PM_AIS
R_LOS
SF
N#1 ODUk_PM_AIS
R_LOS
SF
N#1 ODUk_PM_AIS
R_LOS
SF
N#1 ODUk_PM_AIS
R_LOS
SF
N#1 ODUk_PM_AIS
Client-device
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
SF
OTUk_LOM
N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 OTUk_LOM

OTUk_LOF
N#1 ODUk_PM_AIS
OTUk_TIM
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
B
C
BIT errors
N#1 ODUk_PM_AIS
SF
N#1 ODUk_PM_AIS
N#1 ODUk_PM_AIS
SF
Inserts OTUk_BDI back N#1 OTUk_TIM

ODUk_PM_AIS
N#1 ODUk_PM_AIS
SF
Inserts OTUk_BDI back N#1 OTUk_LOF
N#1 ODUk_PM_AIS
N#1 A
1#N A
1#N A
N#1 B
1#N B
1#N B
N#1 C
1#N C
1#N C
SD
N#1 BIT errors

xxx
Client device
Client-side
1#N BIT errors

1#N BIT errors
Alarm processing
A, B, C are the others of the OTN alarms
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
l
Four channels of R_LOS signals are accessed on the client side.

The OTU at station A accesses four channels of R_LOS signals on the client side. After
being processed in the middle part and on the WDM side of the OTU at station A, the alarm
signals are then sent to station B. The ODUk_PM_AIS alarm of the corresponding channel
is generated in the middle part of station B. The ODUk_PM_AIS alarm is detected in the
client device.
An SF event is generated in each channel of the OTU at station B, and a protection switching
is triggered.
One channel of R_LOS, OTUk_LOM or OTUk_LOF signals is accessed on the client side.
The OTU at station A accesses one channel of R_LOS, OTUk_LOM or OTUk_LOF signals
on the client side, for example, channel 1 at optical port 3. After being processed in the
middle part and on the WDM side of the OTU at station A and the WDM side of station
B, the alarm signals are then sent to the downstream station. The ODUk_PM_AIS alarm
Issue 02 (2011-10-31)

16
OptiX OSN 8800/6800/3800

1 Overview
of channel 3 at optical port 1 is generated in the middle part of station B. The

ODUk_PM_AIS alarm is detected in the client device.
An SF event is generated in each channel of the OTU at station B, and a protection switching
is triggered.
l
The alarm signals except for the signals of the R_LOS, OTUk_LOM, and OTUk_LOF
alarms are accessed on the client side.
When any of other alarm signals is accessed, the corresponding alarm is reported at each
detection point in the system.
Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
Station A
Client-side
Middle
Client device
Station B
WDM-side
WDM-side
Middle
Client-side
Client-device
ODUk_PM_AIS
ODUk_PM_AIS
SF
R_LOS
R_LOS
ODUk_PM_AIS
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS
ODUk_PM_AIS
OTUk_LOF/
SF
OTUk_LOM/
OTUk_LOF/
OTUk_AIS
ODUk_PM_AIS
OTUk_LOM/
OTUk_AIS
ODUk_PM_AIS
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS
ODUk_PM_AIS
SF
ODUk_PM_AIS/
ODUk_PM_LCK/ ODUk_PM_AIS/
ODUk_PM_OCI
ODUk_PM_AIS
ODUk_PM_LCK/
ODUk_PM_OCI
ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
Errors
SD
PM BIP8 errors
Errors
ODUk_PM_DEG/
ODUk_PM_EXC
Errors
PM remote BER
performance events
Errors
Errors
SM BIP8 errors
SD
Errors
OTUk_DEG/
OTUk_EXC
Errors
OTUk remote BER

performance events
xxx
Issue 02 (2011-10-31)
Errors
Alarm processing

17
OptiX OSN 8800/6800/3800

1 Overview
NOTE
The value of k on the WDM-side is different from that of the client device.
l
There is R_LOS, OTUk_LOF, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI or

ODUk_PM_LCK on the WDM side.
The WDM side of the OTU at station B accesses and processes the alarm signals. The OTU
sends the ODUk_PM_BDI or OTUk_BDI alarm to the WDM side of upstream station A.
In addition, the alarm is then sent to the client side of station B. After the alarm is processed
on the client side, the ODUk_PM_AIS alarm is detected in the client device.
There are bit error alarms on the WDM side.

The WDM side of the OTU at station B accesses and processes the bit error alarm signals.
The OTU sends the remote bit error performance events to the WDM side of upstream
station A. The alarm is then sent to the client side of the downstream station B. The errordependent alarm is detected in the client device.
An SD event is generated on the WDM side of the OTU at station B, and a protection
1.4.6 Regenerating OTU

This section describes the alarm signal flow of the regenerating OTU.
Figure 1-9 shows the alarm signal flow of the regenerating OTU.
NOTE
The ALS function of the OTU shown in the figure in this section is not enabled.
The non-intrusive monitoring of the board shown in the figure in this section is enabled.
Issue 02 (2011-10-31)

18
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-9 Alarm signal flow of the regenerating OTU

Station A
Station B(REG)
WDM-side
WDM-side1
MFASframe discontinuous
Station C
WDM-side2
WDM-side
ODUk_PM_AIS
OTUk_LOM
OTUk_BDI

ODUk_PM_TIM
ODUk_PM_TIM
OTUk_TIM
TIM follow-up response is Enabled.

ODUk_PM_AIS
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
ODUk_PM_BDI
OTUk_BDI
OTUk_LOF
OTUk_LOF
ODUk_PM_AIS
OTUk_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
PM BIP8 errors
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_DEG/
ODUk_PM_EXC
SM BIP8 errors
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_DEG/
ODUk_PM_EXC
OTUk_DEG/
OTUk_EXC
Excessive bit errors before FEC

BEFFEC_EXC
R_LOS
R_LOS
ODUk_PM_AIS
OTUk_BDI
Detects and reports the xxx
xxx
alarm
Alarm processing
In the case of the regenerating OTU, all alarms in the SM section are terminated at the local
station and are not sent to the downstream station (except that the OTUk_LOF alarm is inserted
with an ODUk_PM_AIS alarm to the downstream station). Other alarms are then sent to the
downstream station, and are reported on the WDM side of the OTU (except that the R_LOS
alarm is inserted with an ODUk_PM_AIS alarm to the downstream station).
Issue 02 (2011-10-31)

19
OptiX OSN 8800/6800/3800

1 Overview
1.4.7 Alarm Signal Processing of the OTU with the Cross-Connect

Function
The OTU with the cross-connect function supports the service transmission in the straightthrough mode or the cross-connect mode. The processing of alarm signals in one mode is
different from that in the other mode.
Straight-Through Mode
Figure 1-10 shows the unidirectional signal flow in the straight-through mode.
NOTE
The optical port number and channel number shown in Figure 1-10 are the numbers that are displayed on
the U2000.
Figure 1-10 OTU with the cross-connect function in the straight-through mode
A
3#1(RX1)
4#1(RX2)
5#1(RX3)
6#1(RX4)
B
1#3
1#4 1(OUT)
1#5
1#3
1(IN) 1#4
1#5
1#6
1#6
3#1(TX1)
4#1(TX2)
5#1(TX3)
6#1(TX4)
As shown in Figure 1-10, the four channels of optical signals accessed from RX1-RX4 on unit
A at the upstream station are sent to channels 3-6 that correspond to the OUT port in the straightthrough mode. One channel of optical signals that are input from the IN port on unit B at the
downstream station is demultiplexed into four channels of optical signals, which are then directly
sent to TX1-TX4.
Hence, in the straight-through mode, the REM_SF and REM_SD alarms at the downstream
station indicate that the signals at the corresponding port on the client side at the upstream station
fail or bit errors at this port exceed the threshold. For example, when the services in channel 1
at optical port 3 on unit A at the upstream station fail, channel 1 at optical port 3 on unit B at the
downstream station reports the REM_SF alarm.
Cross-Connect Mode
The cross-connect mode is classified into intra-unit cross-connection and inter-unit crossconnection.
l
Intra-unit cross-connection
In Figure 1-11, the cross-connection from RX3 (channel 1 at optical port 5) on unit A to
OUT (channel 3 at optical port 1) on unit A is defined as the intra-unit cross-connection.
Inter-unit cross-connection
In Figure 1-11, the cross-connection from RX1 (channel 1 at optical port 3) on unit C to
OUT (channel 6 at optical port 1) on unit A is defined as the inter-unit cross-connection.
The inter-unit cross-connection is realized by using the backplane.
Figure 1-11 shows the unidirectional signal flow in the cross-connect mode.
Issue 02 (2011-10-31)

20
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-11 OTU with the cross-connect function in the cross-connect mode
A
3#1(RX1)
B
1#3
1#4 1(OUT)
1#5
4#1(RX2)
5#1(RX3)
6#1(RX4)
1#3
1(IN) 1#4
1#5
1#6
3#1(RX1)
1#6
3#1(TX1)
4#1(TX2)
5#1(TX3)
6#1(TX4)
1#3
1#4
1#5
4#1(RX2)
5#1(RX3)
6#1(RX4)
1#6
C
In Figure 1-11, the following cross-connections are created:

l
Intra-unit cross-connection from RX3 (channel 1 at optical port 5) on unit A to OUT

(channel 3 at optical port 1) on unit A
Inter-unit cross-connection from RX1 (channel 1 at optical port 3) on unit C to OUT

(channel 6 at optical port 1) on unit A
The signals that are received from RX3 (channel 1 at optical port 5) on unit A at the upstream
station are sent to IN (channel 3 at optical port 1) on unit B at the downstream station. The signals
received from RX1 (channel 1 at optical port 3) on unit C at the upstream station are sent to IN
(channel 6 at optical port 1) on unit B at the downstream station.
The meaning of optical channels regarding the REM_SF and REM_SD alarms in the crossconnect mode is different from that in the straight-through mode. For example, when the services
in channel 1 at optical port 4 on unit A at the upstream station fail, unit B at the downstream
station reports the REM_SF alarm in channel 1 at optical port 3; when the services in channel
1 at optical port 3 on unit C at the upstream station fail, unit B at the downstream station reports
the REM_SF alarm in channel 1 at optical port 6.
Hence, when a unit reports the REM_SF or REM_SD alarm, query the cross-connections of the
unit at the upstream station to locate the alarm signal source. Then, check whether the client
signal status such as the optical power, fibers and optical modules in the channel at the
corresponding optical port is normal. If not, take the corresponding maintenance measures.
CAUTION
In any mode, proper configuration must be made on the U2000.
1.4.8 OTU Processing GE Signals

This section describes the alarm signal flow when the OTU board processes Ethernet service
signals.
Issue 02 (2011-10-31)

21
OptiX OSN 8800/6800/3800

1 Overview
The GE services are encapsulated into OTN signals or SDH signals after they are accessed on
the client side of the OTU on an Ethernet network. The alarm signal processing when the GE
services are encapsulated into OTN signals differs slightly from the alarm signal processing
when the GE services are encapsulated into SDH signals.
Figure 1-12 and Figure 1-13 show the signal flow when the GE services are encapsulated into
OTN signals and the signal flow when the GE services are encapsulated into SDH signals
respectively.
NOTE
Issue 02 (2011-10-31)

22
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals
Station A
Client-side
Client device
Station B
WDMside
Middle
WDMside
Middle
Client-side
Client-device
Scenario 1: The client sides are in the non-negotiation mode.

R_LOS
R_LOS
LINK_ERR
REM_SF
LINK_ERR
LINK_ERR
REM_SF
None
Scenario 2: The client sides are in the auto-negotiation mode.

R_LOS
REM_SF
LINK_ERR
R_LOS
LPT=Enable
LINK_ERR
None
LINK_ERR
Errors
LPT=Disable
LINK_ERR
LINK_ERR
LINK_ERR
None
Errors
Errors
PM BIP8 errors
SD
ODUk_PM_DEG/
ODUk_PM_EXC
Errors
PM remote BER
performance events
SM BIP8 errors
SD
OTUk_DEG/
OTUk_EXC
OTUk remote BER

performance events
R_LOS
Errors
SF
R_LOS
LINK_ERR
OTUk_BDI&
ODUk_PM_BDI
SF
OTUk_AIS/
OTUk_LOF/ OTUk_AIS/
OTUk_LOM OTUk_LOF
/
OTUk_LOM
OTUk_BDI&
ODUk_PM_BDI
LINK_ERR
ODUk_PM_AIS/
SF
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_BDI
LINK_ERR

xxx
Alarm processing
This section describes the alarm signal flow when the OTU processes the R_LOS and
LINK_ERR alarms. The signal flow for processing other alarms is similar.
l
Issue 02 (2011-10-31)
R_LOS

23
OptiX OSN 8800/6800/3800

1 Overview
The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The R_LOS alarm signal is received on the client side of the OTU at station A. The
alarm signal is sent to station B after it is processed on the WDM side of the OTU. In this
case, the REM_SF alarm is generated on the client side of the OTU at station B, and the
client equipment at station B reports the LINK_ERR alarm.
The client sides of the OTUs at station A and station B work in the auto-negotiation mode.
The R_LOS alarm signal is received on the client side of the OTU at station A. The alarm
signal is sent to station B after it is processed on the WDM side of the OTU. In this case,
the REM_SF and LINK_ERR alarms are generated on the client side of the OTU at station
B, and the client equipment at station B reports the LINK_ERR alarm.
l
LINK_ERR
The client sides of the OTUs at station A and station B work in the non-auto-negotiation
mode. The client signals at station A contain LINK_ERR alarms, and the client signals are
transmitted transparently from station A to the WDM side of the OTU at station B.
The client sides of the OTUs at station A and station B work in the auto-negotiation mode.
In the case of the Ethernet board that supports the LPT function, when the LPT enabling
status is set to Disable, the LINK_ERR alarm is not generated on the client side of the OTU
at station B; when the LPT enabling status is set to Enable, the LINK_ERR alarm is
generated on the client side of the OTU at station B.
Figure 1-13 Alarm signal flow 2: when the OTU processes GE signals
Client-side
Client device
Station B
Station A
WDM-side
WDM-side
Client-side
Client-device
REM_SF
LINK_ERR
Scenario 1: The client sides are in the non-negotiation mode.

R_LOS
R_LOS
LINK_ERR
LINK_ERR
None
None
Scenario 2: The client sides are in the auto-negotiation mode.

R_LOS
REM_SF
LINK_ERR
R_LOS
LPT=Enable
LINK_ERR
LINK_ERR
None
LPT=Disable
R_LOS
LINK_ERR
LINK_ERR
LINK_ERR
None
SF
R_LOS
None
LINK_ERR
MS_BDI
xxx
Issue 02 (2011-10-31)
Alarm processing

24
OptiX OSN 8800/6800/3800

1 Overview
This section describes the alarm signal flow when the R_LOS alarm is received on the WDM
side of the OTU at station B. The signal flow for processing other alarms is similar to Figure
1-12.
After the R_LOS alarm is received on the WDM side of the OTU at station B, the SF event is
generated. In addition, station B sends the MS_BDI alarm to the WDM side of the OTU at station
A, and the client equipment at station B reports the LINK_ERR alarm.
1.4.9 Optical-Layer Alarm Signal Processing on OTN

This section describes how an OTU board processes optical-layer alarm signals and how the
alarm signals flow.
Certain alarms are specific to the OCh, OMS, or OTS optical layer. This section mainly describes
the association relations between the optical-layer alarms generated by each NE.
The following part describes the alarm association relations in three network scenarios, as shown
in Figure 1-14, Figure 1-15, and Figure 1-16.
Figure 1-14 Scenario I
OTU
OTU
OTU
OM
OA
OA
OTU
OD
OA
OTU
OTU
FIU
SC1
OTU
OA
Client-side equipment
OTU
FIU
Line-side ODF
SC1
Line-side ODF
OTU
OD
OM
OTU
OTU
OTU
Station A
Station B
In this scenario, there are two stations. Station A and station B are OTM stations.
In this scenario, the OTS, OMS, and OCh trails are between adjacent nodes.
In case of the following faults, the association relations of alarms are as follows:
l
The fiber from station A to station B is cut.

The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm.
At station A, the optical amplifier unit in direction A-to-B is faulty.

The FIU board at station B reports the OTS_LOS-P alarm and the FIU board at station A
reports the OTS_BDI-P alarm.
l
Issue 02 (2011-10-31)
At station A, the optical amplifier in direction A-to-B loses input light.

25
OptiX OSN 8800/6800/3800

1 Overview
The FIU board at station A inserts the OTS_PMI signal and the FIU board at station B does
not report the OTS_LOS-P alarm.
l
At station A, the fiber in direction SC1-to-FIU is cut.

The FIU board at station B reports the OTS_LOS-O alarm and the FIU board at station A
reports the OTS_BDI-O alarm.
The configuration of TTI to be received at station B is inconsistent with TTI transmitted

by station A.
The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A
The optical multiplexer (OM) unit at station A is faulty.

The optical demultiplexer (OD) unit at station B reports the OMS_LOS-P alarm and the
OM unit at station A reports the OMS_BDI-P alarm.
The OTU board at station A is faulty.

The OTU board at station B reports the OCh_LOS-P alarm.
Figure 1-15 Scenario II

OTU
OTU
OTU
OTU
OD
OA
FI
U
FIU
SC2
FIU
OA
Line-side ODF
SC1
West line-side
ODF
OTU
OA
OD
OA
East line-side ODF
OM
Line-side ODF
OTU
OTU
OTU
FIU
OA
SC1
OTU
OA
OM
OTU
OTU
OTU
Station A
Station B
Station C
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an OLA station.
In this scenario, station OLA only amplifies signals and terminates the OTS layer. The OMS
and OCh trails are between station A and station C.
l

The FIU board at station B reports the OTS_LOS alarm and the OD unit at station C reports
the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the
OTS_BDI alarm and OMS_BDI alarm respectively.

The FIU board at station B reports the OTS_LOS-P alarm. The OD unit at station C reports
the OMS_FDI-P or OMS_SSF-P alarm. The FIU board and OM unit at station A report the
OTS_BDI-P alarm and OMS_BDI-P alarm respectively.

Issue 02 (2011-10-31)

26
OptiX OSN 8800/6800/3800

1 Overview

The FIU board at station B reports the OTS_LOS-O alarm. The OD unit at station C reports
the OMS_FDI-O or OMS_SSF-O alarm. The FIU board and OM unit at station A report
the OTS_BDI-O alarm and OMS_BDI-O alarm respectively.

by station A.
The FIU board at station B reports the OTS_TIM alarm. The OD unit at station C reports
the OMS_FDI or OMS_SSF alarm. The FIU board and OM unit at station A report the
OTS_BDI alarm and OMS_BDI alarm respectively.
The OM unit at station A is faulty.

The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station A
reports the OMS_BDI-P alarm.

The OTU board at station B reports the OCh_LOS-P alarm.
Figure 1-16 Scenario III

West clientside
OOO
T T T
U U U
OTU
East clientside
O O OO
T T T T
U U U U
O
T
U
OTU
OTU
OD
OA
OA
OM
O
T
U
WSD9
OA
O O OO O
T T T T T
U U UU U
OTU
OTU
FIU
SC1
OTU
OA
OD
West clientside
Station A
FIU
SC2
RMU9
OA
OTU
OA
OD
OD
RMU9
Line-side ODF
OTU
WSD9
OA
FI
U
OA
OM
East line-side ODF
SC1
OTU
FI
U
West line-side ODF
OTU
Line-side ODF
OM
OM
OTU
OO
T T
UU
OTU
East clientside
Station B
Station C
In this scenario, there are three stations. Station A and station C are OTM stations, and station
B is an ROADM station.
In this scenario, station ROADM adds and drops certain wavelengths. That is, certain
wavelengths are between stations A and B, or stations B and C, and the other wavelengths are
between stations A and C. Hence, certain OCh trails are between stations A and B, or B and C,
and the other OCh trails are between stations A and C.
l

The FIU board at station B reports the OTS_LOS alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
wavelengths between stations A and C).
Issue 02 (2011-10-31)

27
OptiX OSN 8800/6800/3800

1 Overview
The FIU board at station B reports the OTS_LOS-P alarm and the FIU board at station A
reports the OTS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm (for
l


The FIU board at station B reports the OTS_LOS-O alarm and the FIU board at station A
reports the OTS_BDI-O alarm. Station C reports the OCh_FDI-O or OCh_SSF-O alarm
(for wavelengths between stations A and C).

by station A.
The FIU board at station B reports the OTS_TIM alarm and the FIU board at station A
reports the OTS_BDI alarm. Station C reports the OCh_FDI or OCh_SSF alarm (for
The OM unit at station A is faulty.

The OD unit at station B reports the OMS_LOS-P alarm and the OM unit at station A
reports the OMS_BDI-P alarm. Station C reports the OCh_FDI-P or OCh_SSF-P alarm
(for wavelengths between stations A and C).

The OTU board at station B reports the OCh_LOS-P alarm (for wavelengths between
stations A and B). The OTU board at station C reports the OCh_LOS-P alarm (for
The fiber from station B to station C is cut.

The FIU board at station C reports the OTS_LOS alarm and the FIU board at station B
At station B, the optical amplifier unit in direction B-to-C is faulty.

The FIU board at station C reports the OTS_LOS-P alarm and the FIU board at station B
reports the OTS_BDI-P alarm.
At station B, the optical amplifier in direction B-to-C loses input light.

The FIU board at station B inserts the OTS_PMI signal and the FIU board at station C does
At station B, the fiber in direction SC1-to-FIU is cut.

The FIU board at station C reports the OTS_LOS-O alarm and the FIU board at station B
reports the OTS_BDI-O alarm.
The configuration of TTI to be received at station C is inconsistent with TTI transmitted

by station B.
The FIU board at station C reports the OTS_TIM alarm and the FIU board at station B
The OM unit at station B is faulty.

The OD unit at station C reports the OMS_LOS-P alarm and the OM unit at station B reports
the OMS_BDI-P alarm.
The OTU board at station B is faulty.

The OTU board at station C reports the OCh_LOS-P alarm (for wavelengths from station
B to station C).
Issue 02 (2011-10-31)

28
OptiX OSN 8800/6800/3800

1 Overview
1.5 Suppression Relationship of Alarms

This section describes the rules of alarm suppression and provides the suppression relationship
figure of common alarms. The efficiency for handling the alarms can be enhanced due to the
alarm suppression.
When the equipment is faulty, several alarms may be generated by the same optical port.
However, some alarms are not important for the maintenance engineer. For example, when the
signal is lost, the optical port generates the R_LOS alarm accompanied with the alarm indicating
that the B1 bit errors cross the threshold. However, the alarm indicating that the B1 bit errors
cross the threshold is not important for the maintenance engineer. In this case, the equipment
suppresses the alarm indicating that the B1 bit errors cross the threshold through the R_LOS
alarm. Only the R_LOS alarm is reported by the optical port.
The rules of alarm suppression are as follows:
l
The client-side alarms and the WDM-side alarms are relatively independent. There is no
alarm suppression relationship between the client-side alarms and the WDM-side alarms.
There is no alarm suppression relationship between the detection alarms related to the board
hardware and the service alarms.
NOTE
Some alarms for the optical module are exceptions. For example, the R_LOS alarm suppresses the
IN_PWR_LOW alarm.
There is no alarm suppression relationship for the alarms that cannot be generated at the
same time.
1.5.1 Suppression of OTN Alarms

There is no alarm suppression for the alarms of different TCM layers.
The suppression of OTN alarms is shown in the Figure 1-17.
The alarm above the arrow suppresses the alarm below the arrow. For example, the OTUk_LOM
alarm suppresses the OTUk_TIM alarm.
Issue 02 (2011-10-31)

29
OptiX OSN 8800/6800/3800

1 Overview
Figure 1-17 Suppression of OTN alarms

OCH_LOS
OTUk_LOF
OTUk_LOM
OTUk_SSF
OTUk_TIM
OTUk_BDI
ODUk_LOFLOM
ODUk_TCMn_LTC/
ODUk_TCMn_LCK/
ODUk_TCMn_OCI
Note:
The TIM alarm suppresses the
BDI alarm and DEG alarm of
the same layer just when the
TIM follow-up response is
Enabled.
OTUk_DEG
ODUk_TCMn_SSF
ODUk_TCMn_TIM
ODUk_TCMn_BDI
ODUk_TCMn_DEG
ODUk_PM_OCI/
ODUk_PM_LCK
ODUk_PM_SSF
ODUk_PM_TIM
ODUk_PM_BDI
ODUk_PM_DEG
OPUk_PLM
OPUk_MISM
Issue 02 (2011-10-31)

30
OptiX OSN 8800/6800/3800

1 Overview
1.5.2 Suppression of Alarms Related to SDH Services and Other

Common Equipment Alarms
The suppression of SDH service alarms and other common alarms related to equipment alarms
is shown in Figure 1-18.
The alarm above the arrow suppresses the alarm below the arrow. For example, when an optical
port on the client side loses signals, the optical port only reports the R_LOS alarm. The R_LOC
and R_LOF alarms are not reported.
Figure 1-18 Suppression of alarms related to SDH services and other common equipment alarms
PORT_MODULE_OF
FLINE
LSR_COOL_ALM
TEM_HA/TEM_LA
IN_PWR_HIGH/
OUT_PWR_HIGH
TF
LSR_WILL_DIE
OUT_PWR_LOW
TD
R_LOS
IN_PWR_LOW
R_LOC
R_LOF
BEFFEC_EXC
J0_MM
MS_REI
B1_EXC
MS_AIS
MS_RDI
B1_SD
Issue 02 (2011-10-31)
B2_EXC
B2_SD

31
OptiX OSN 8800/6800/3800

1 Overview
1.6 Performance Event Suppression by Alarms

An optical interface can report several alarms and performance events. Some performance events
are not important for the maintenance engineer.
When the equipment is faulty, several alarms and performance events may be generated by the
same optical interface. However, some alarms and performance events are not important for the
maintenance engineer. For example, when the signal is lost, the optical interface generates the
R_LOS alarm accompanied with the B1 bit error performance event. However, the B1 bit error
performance event is not important for the maintenance engineer. In this case, the equipment
suppresses the B1 bit error performance event through the R_LOS alarm. Only the R_LOS alarm
is reported by the optical interface.
For OptiX OSN 8800, Table 1-4 lists the performance events suppressed by the R_LOS alarm.
For OptiX OSN 6800/3800, Table 1-5 lists the performance events suppressed by the R_LOS
alarm.
Table 1-4 Performance events suppressed by the R_LOS alarm (OptiX OSN 8800)
MSBBE
RSBBE
LSIOPCUR
MSES
RSES
LSIOPMAX
MSFEES
RSCSES
LSIOPMIN
MSFESES
RSOFS
SUMIOPCUR
MSFEBBE
FEC_AFT_COR_ER
SUMIOPMAX
MSFEUAS
FEC_BEF_COR_ER
SUMIOPMIN
Table 1-5 Performance events suppressed by the R_LOS alarm (OptiX OSN 6800/3800)
MSBBE
MSFEUAS
LSIOPCUR
MSES
RSBBE
LSIOPMAX
MSCSES
RSES
LSIOPMIN
MSFEES
RSCSES
SUMIOPCUR
MSFESES
RSOFS
SUMIOPMAX
MSFEBBE
FEC_AFT_COR_ER
SUMIOPMIN
MSFECSES
FEC_BEF_COR_ER
Table 1-6 lists the performance events suppressed by the NO_BD_PARA alarm.
Issue 02 (2011-10-31)

32
OptiX OSN 8800/6800/3800

1 Overview
Table 1-6 Performance events suppressed by the NO_BD_PARA alarm
Issue 02 (2011-10-31)
LSBIASCUR
LSTMPMAX
LSIOPMIN
LSBIASMAX
LSTMPMIN
SUMIOPCUR
LSBIASMIN
LSOOPCUR
SUMIOPMAX
LSCLCCUR
LSOOPMAX
SUMIOPMIN
LSCLCMAX
LSOOPMIN
SUMOOPCUR
LSCLCMIN
LSIOPCUR
SUMOOPMAX
LSTMPCUR
LSIOPMAX
SUMOOPMIN

33
OptiX OSN 8800/6800/3800

2 Alarm List
Alarm List
About This Chapter

This topic describes the alphabetical lists of alarms and lists alarms of every board.
2.1 Product Alarm List
This section lists the alarms supported by the product in alphabetical order.
2.2 Board Alarm List
Lists the alarms of every board.
Issue 02 (2011-10-31)

34
OptiX OSN 8800/6800/3800

2 Alarm List
2.1 Product Alarm List

This section lists the alarms supported by the product in alphabetical order.
2.1.1 Alarm List A

This section used a table to list the alarms starting with A.
Issue 02 (2011-10-31)
Name
Description
Level
AD_CHECK_FAIL
AD (analog to digital
converter) self check
failure
Major
ALM_ALS
Automatic laser shutdown

(ALS) alarm
Minor
ALM_GFP_dCSF
The loss of GFP client

signal
Critical
ALM_GFP_dLFD
The loss of GFP frame

delineation
Major
ALC_ADJUST_FAIL
ALC link adjustment

failure
Major
ALC_WAIT_ADJUST
ALC link anomaly and

wait for adjustment
Major
ALS_ACTIVE
ALS occurred
Minor
ALM_HANGUP
The orderwire phone is in

the off-hook state for a
long time
Minor
APE_ADJUST_FAIL
APE adjustment failure
Major
APE_ADJUST_PEND
APE adjustment is
pending for operation.
Major
APS_MANUAL_STOP
The MSP protocol is

manually stopped
Minor
APS_FAIL
APS protection switching

failure
Major
APS_INDI
An alarm indicating the

APS state
Major
AU_AIS
AU alarm indication
signal
Major
AU_LOP
AU loss of pointer
Major

35
OptiX OSN 8800/6800/3800

2 Alarm List
2.1.2 Alarm List B

This section used a table to list the alarms starting with B.
Issue 02 (2011-10-31)
Name
Description
Level
B1_EXC
Regenerator section (B1)

excessive errors
Minor
B1_SD
Regenerator section (B1)

signal degraded
Minor
B2_EXC
Multiplex section (B2)

excessive errors
Major
B2_SD
Multiplex section (B2)

signal degraded
Minor
B3_EXC
The number of higher

order path B3 bit errors in
the signals received on the
line exceeds the threshold
Major
B3_EXC_VC3
The number of B3 bit

errors in the lower order
path VC-3 exceeds the
threshold.
Major
B3_EXC_VC4

errors in the VC-4 path
exceeds the threshold.
Major
B3_SD
The higher order path B3

signals received on the line
are degraded.
Minor
B3_SD_VC3
The number of VC-3 B3

bit errors exceeds the
threshold.
Minor
B3_SD_VC4

errors in the VC-4 path
Minor
BD_NOT_INSTALLED
Logic board not installed

alarm
Minor
BD_STATUS
Board out of position
Major
BDID_ERROR
An alarm of slot
verification error
Major
BEFFEC_EXC
Signal degraded before

FEC
Minor
BOOTROM_BAD
BOOTROM data check

failed
Major

36
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
BUS_ERR
Bus error
Critical
2.1.3 Alarm List C

This section used a table to list the alarms starting with C.
Name
Description
Level
C2_VCAIS
A C2 byte alarm indication
Minor
CFCARD_FAILED
CF Card Failed
Major
CHAN_ADD
Channel of single wave

signal add
Major
CHAN_LOS
Channel of single wave

signal loss
Critical
CHIP_ABN
Temperature chip failure
Minor
CLIENT_PROT_NOTSTART
Client-side 1+1 protection

group not started
Minor
CLIENT_PORT_PS
Client-side 1+1 protection

switching
Major
CLIENT_PORT_STA_INDI
The state of the client-side

1+1 optical channel
protection group
Minor
CLK_NO_TRACE_MODE
The clock enters into a

non-tracing running mode.
Minor
CLK_LOCK_FAIL
Clock lockout failure

alarm
Major
COMMUN_FAIL
Internal communication
failure on the board
Major
CPC_NODE_ID_ERR
Node ID Error
Critical
CRC4_CROSSTR
CRC4 multi-frame error

code count exceeds the
threshold
Minor
2.1.4 Alarm List D

This section used a table to list the alarms starting with D.
Issue 02 (2011-10-31)

37
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
DB_RESTORE_FAIL
Database restore fail alarm
Major
DBMS_ABNORMAL
Database state is abnormal
Major
DBMS_ERROR
Database error alarm
Major
DBMS_PROTECT_MODE
Database in protect mode
Critical
DBPS_ABNORMAL
DBPS abnormal alarm
Major
DCM_INSUFF
Insufficient dispersion
compensation margin
Warning
DLAG_PROTECT_FAIL
DLAG protect failed

alarm
Major
DSP_LOAD_FAIL
DSP software loading

failure
Major
2.1.5 Alarm List E

This section used a table to list the alarms starting with E.
Issue 02 (2011-10-31)
Name
Description
Level
ETH_8B10B_ERR
Ethernet line signal encoding/

decoding error
Minor
ETH_CFM_LOC
Service connectivity loss
Critical
ETH_CFM_MISMERGE
Misconnection
Critical
ETH_CFM_MACSTATUS
Remote MAC defect

indication
Major
ETH_CFM_RDI
A remote CFM_OAM alarm

indication
Minor
ETH_CFM_UNEXPERI
Errored frame
Minor
ETH_MISCONNECT
Network interface
misconnection alarm
Major
ETH_SERVICE_CONFIG_
FAIL
Ethernet service
configuration failure
Major
ETHOAM_DISCOVER_F
AIL
The point-to-point Ethernet

OAM discovery failure alarm
Minor
ETHOAM_RMT_CRIT_F
AULT
A critical fault occurs to the

remote end of point-to-point
Ethernet OAM
Minor

38
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
ETHOAM_RMT_LOOP
The remote loopback of

point-to-point Ethernet OAM
alarm
Minor
ETHOAM_RMT_SD
The remote SD of point-topoint Ethernet OAM alarm
Minor
ETHOAM_SELF_LOOP
Loopback of the MAC port

that receives the OAM
protocol packets in a point-topoint manner
Major
ETHOAM_VCG_SELF_L
OOP
Loopback of the VCTRUNK

port that receives the OAM
protocol packets in a point-topoint manner
Major
EX_ETHOAM_CC_LOS
Loss of the periodic

continuity check message
Critical
EX_ETHOAM_MPID_CN
FLCT
The maintenance point ID

conflict
Major
EXT_MODULE_OFFLINE
The extended wavelength

module offline
Major
EXT_SYNC_LOS
The loss of external clock

source
Critical
EXT_TIME_LOC
The loss of the external timing

source
Major
2.1.6 Alarm List F

This section used a table to list the alarms starting with F.
Issue 02 (2011-10-31)
Name
Description
Level
FAN_FAIL
Fan failed
Major
FAN_FAULT
Fan fault
Minor
FC_8B10BERR_OVER
8B10B bit error rate

crossing alarm
Minor
FC_LINK_ERR
FC service link failure

alarm
Critical
FC_SYNC_LOS
FC service synchronous
word loss alarm
Critical

39
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
FCS_ERR
The frame check sequence

(FCS) is incorrect
Critical
FEATURE_WITHOUT_LICENSE
Service without license
Major
FLOW_OVER
The inflow at the Ethernet

port exceeds the threshold
Minor
FEC_LOF
Received FEC is loss of

frame
Critical
FEC_OOF
Received FEC is out of

frame
Critical
FPGA_ABN
FPGA status is abnormal
Major
FSELECT_STG
The clock board is forcibly

selected
Major
FWD_PKT_LOSS
Packets droped alarms
Minor
2.1.7 Alarm List G

This section used a table to list the alarms starting with G.
Name
Description
Level
GAINDATA_MIS
Mismatch of gain attribute
Major
2.1.8 Alarm List H

This section used a table to list the alarms starting with H.
Issue 02 (2011-10-31)
Name
Description
Level
HARD_BAD
Hardware failed
Critical
HARD_ERR
Minor hardware error
Minor
HP_LOM
Loss of multiframe in the

higher order path
Major
HP_RDI
A remote defect in the

higher order path
Minor
HP_REI
A remote error indication

in the higher order path
Warning

40
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
HP_SLM
A signal label mismatch

alarm in the higher order
path
Minor
HP_TIM
A trace identifier
mismatch alarm in the
higher order path
Minor
HP_UNEQ
An alarm indicating that

no signals are loaded in the
higher order path
Minor
HSC_UNAVAIL
Working/protection
switching failed
Minor
2.1.9 Alarm List I

This section used a table to list the alarms starting with I.
Name
Description
Level
IN_PWR_HIGH
Input optical power is too

high
Critical
IN_PWR_LOW
Input optical power is

excessively low
Critical
INTRA_OTU_PS
Intra-OTU 1+1 protection

switching
Major
INTRA_OTU_STA_INDI
The state of the Intra-OTU

1+1 optical channel
protection group
Minor
IPA_SHUT
Laser shutdown by IPA
Minor
2.1.10 Alarm List J

This section used a table to list the alarms starting with J.
Issue 02 (2011-10-31)
Name
Description
Level
J0_MM
J0 byte or trace indicator

mismatch
Minor

41
OptiX OSN 8800/6800/3800

2 Alarm List
2.1.11 Alarm List K

This section used a table to list the alarms starting with K.
Name
Description
Level
K1_K2_M
The K1 and K2 bytes

mismatch alarm
Minor
K2_M
The K2 bytes mismatch

alarm
Minor
2.1.12 Alarm List L

This section used a table to list the alarms starting with L.
Issue 02 (2011-10-31)
Name
Description
Level
L_SYNC
Loss of synchronization
alarm
Critical
LAG_PORT_FAIL
Aggregation group VCG

port failure alarm
Minor
LAG_VC_PORT_FAIL
Aggregation group VCG

port failure alarm
Minor
LAN_LOC
Ethernet communication
failure
Major
LASER_HAZARD_WARN
ING
Warning indication of the

laser hazard level.
Critical
LASER_MODULE_MISMATCH
Optical module mismatch

alarm
Major
LASER_SHUT
The laser of the board is

shut down
Major
LCAS_FOPR
The failure of the LCAS

protocol in the receive
direction
Major
LCAS_FOPT
The failure of the LCAS

protocol in the transmit
direction
Major
LCAS_PLCR
Partial loss of capacity in

the LCAS receive
direction
Minor
LCAS_PLCT
Partial loss of capacity in

the LCAS transmit
direction
Minor

42
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
LCAS_TLCR
The total loss of capacity

in the LCAS receive
direction
Major
LCAS_TLCT
Total loss of capacity in

the LCAS transmit
direction
Major
LCS_DAYS_OF_GRACE
License in keepalive
period
Major
LCS_EXPIRED
License expired
Critical
LCS_FILE_NOT_EXIST
No license file
Critical
LINK_ERR
Incorrect data link
Critical
LOCAL_FAULT
Local fault
Minor
LOCKPOW_MIS
Mismatch of lock-power
attribute
Major
LOCK_CUR_FAIL
Pump drive current

unlocked alarm
Critical
LOOP_ALM
Indication of loop
operating
Minor
LP_RDI_VC3
Aremote defect indication

in the VC-3 lower order
path
Minor
LP_SLM_VC3
A signal label mismatch

alarm in the VC-3 lower
order path
Minor
LP_UNEQ_VC3
No payload is equipped in Minor

the VC-3 lower order path
LPT_ACTIVE
LPT switching is active
Major
LPT_RFI
A remote failure
indication alarm of link
state pass through
Critical
LSR_COOL_ALM
Cooling current of the

laser over threshold
Major
LSR_FORCE_OPEN
Laser forced open
Minor
LSR_INVALID
Invalid optical module

alarm
Critical
LSR_WILL_DIE
Laser will be out of work
Critical

43
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
LTI
The loss of
synchronization source
Major
2.1.13 Alarm List M

This section used a table to list the alarms starting with M.
Issue 02 (2011-10-31)
Name
Description
Level
MAINBD_SUBBD_MISMATCH
Mainboard and subboard

mismatch
Major
MOD_COM_FAIL
Module communicates
abnormally
Major
MODULE_ADJUST_FAIL
Adjustment of optical
module failed
Major
MODULE_COOLCUR_OVE
R
Module cooling current

exceeds the threshold
Major
MODULE_TEMP_OVER
Module temperature
Major
MODULEFILE_UPDATE_F
AIL
Updating the microprogram

and laser parameter table
failed
Major
MS_AIS
Multiplex section alarm

indication
Major
MS_APS_INDI_EX
An extended indication
alarm of the MSP switching
state
Major
MS_CROSSTR
Multiplex section
performance over threshold
Minor
MS_RDI
Multiplex section remote

defect indication
Minor
MS_REI
Multiplex section remote

error indication
Warning
MS_SNCP_PS
MS SNCP protection switch
Major
MS_SNCP_STA_INDI
The state of the MS SNCP

protection group
Minor
MULTI_RPL_OWNER
More than one

RPL_OWNER alarm
Minor
MUT_LOS
Loss of multiplexed signals
Critical

44
OptiX OSN 8800/6800/3800

2 Alarm List
2.1.14 Alarm List N

This section used a table to list the alarms starting with N.
Name
Description
Level
NEBD_XC_DIF
Crossing data of NE and

board different
Critical
NESF_LOST
Lack a set of host software
Critical
NESTATE_INSTALL
NE is in install state, not

configured
Critical
NO_BD_PARA
No board parameter
Critical
NO_BD_SOFT
No board software
Critical
NO_ELABEL
E-label unloaded
Warning
NODEID_MM
The NODEID_MM is an
alarm indicating the MSP
node ID mismatch
Major
NTP_SYNC_FAIL
NTP synchronization
failure
Minor
NULL_SEND
The NULL signals

(overhead is expressed in
all "0"s) are sent out
Warning
2.1.15 Alarm List O

This section used a table to list the alarms starting with O.
Issue 02 (2011-10-31)
Name
Description
Level
OA_LOW_GAIN
Optical multiplexed signal

gain low
Critical
OCH_FDI
Forward defect indication

at OCh layer
Warning
OCH_FDI-O

at OCh layer (overhead)
Warning
OCH_FDI-P

at OCh layer (payload)
Warning
OCH_LOS-P
Loss of signal (payload) at

OCh layer
Critical

45
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
OCH_OCI
Open connection
indication at OCh layer
Minor
OCH_SSF
Server signal fail at OCh

layer
Warning
OCH_SSF-O
Server signal fail

(overhead) at OCh layer
Warning
OCH_SSF-P
Server signal fail

(payload) at OCh layer
Warning
ODU_AIS
ODU (optical channel data

unit) alarm indication
signal
Warning
ODU_LCK
ODU locked
Major
ODU_OCI
ODU open connection

indication
Major
ODU_SNCP_PS
ODU SNCP protection

switching
Major
ODU_SNCP_STA_INDI
The state of the ODU

SNCP protection group
Minor
ODUFLEX_PLM
OPUFLEX Payload Label

Mismatch
Minor
ODUFLEX_LOFLOM
The FAS and MFAS are

abnormal
Critical
ODUFLEX_PM_AIS
ODUFlex PM Alarm
Indication Signal
Major
ODUFLEX_PM_BDI
ODU0 PM Backward
Defect Indication
Minor
ODUFLEX_PM_DEG
ODUFlex PM Signal
Degrade Alarm
Minor
ODUFLEX_PM_EXC
ODUFlex PM Section
Excessive BIP8 Errors
defect
Minor
ODUFLEX_PM_LCK
ODUFlex PM Lockout
Defect
Minor
ODUFLEX_PM_OCI
ODUFlex PM Open
Connection Indication
Minor
ODUFLEX_PM_SSF
ODUFlex PM Server
Signal Fail
Critical

46
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
ODUFLEX_PM_TIM
ODUFlex PM Trace
Identifier Mismatch
Minor
ODU0_LOFLOM

abnormal
Critical
ODU0_PM_AIS
ODU0 PM alarm
indication signal
Warning
ODU0_PM_BDI
ODU0 PM backward
defect indication
Warning
ODU0_PM_DEG
ODU0 PM signal
degraded
Minor
ODU0_PM_LCK
ODU0 PM signal locked
Minor
ODU0_PM_OCI
ODU0 PM open
connection indication
Minor
ODU0_PM_SSF
ODU0 PM Server signal

fail
Warning
ODU0_PM_TIM
ODU0 PM section TTI

mismatch
Minor
ODU0_PM_EXC
ODU0 PM section BIP8

excessive error defect
Major
ODU0_TCMn_AIS
ODU0 TCMn alarm

indication signal
Warning
ODU0_TCMn_BDI
ODU0 TCMn backward

defect indication
Warning
ODU0_TCMn_DEG
ODU0 TCMn signal

degraded
Minor
ODU0_TCMn_LCK
ODU0 TCMn signal

locked
Minor
ODU0_TCMn_LTC
Loss of ODU0 TCMn

serial connection
Minor
ODU0_TCMn_OCI
ODU0 TCMn open

Minor
ODU0_TCMn_SSF
ODU0 TCMn Server

signal fail
Warning
ODU0_TCMn_TIM
ODU0 TCMn TTI

mismatch
Minor
ODU0_TCMn_EXC
ODU0 TCMn section

BIP8 excessive error
defect
Major

47
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
ODU0_LOFLOM

abnormal
Critical
ODU1_PM_AIS
ODU1 PM alarm
indication signal
Warning
ODU1_PM_BDI
ODU1 PM backward
defect indication
Warning
ODU1_PM_DEG
ODU1 PM signal
degraded
Minor
ODU1_PM_LCK
Minor
ODU1_PM_OCI
ODU1 PM open
Minor
ODU1_PM_SSF
ODU1 PM Server signal

fail
Warning
ODU1_PM_TIM
ODU1 PM section TTI

mismatch
Minor
ODU1_PM_EXC

Major
ODU1_TCMn_AIS
ODU1 TCMn alarm

indication signal
Warning
ODU1_TCMn_BDI
ODU1 TCMn backward

defect indication
Warning
ODU1_TCMn_DEG
ODU1 TCMn signal

degraded
Minor
ODU1_TCMn_LCK
ODU1 TCMn signal

locked
Minor
ODU1_TCMn_LTC
Loss of ODU1 TCMn

serial connection
Minor
ODU1_TCMn_OCI
ODU1 TCMn open

Minor
ODU1_TCMn_SSF
ODU1 TCMn Server

signal fail
Warning
ODU1_TCMn_TIM
ODU1 TCMn TTI

mismatch
Minor
ODU1_TCMn_EXC
ODU1 TCMn section

defect
Major
ODU2_LOFLOM

abnormal
Critical

48
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
ODU2_PM_AIS
ODU2 PM alarm
indication signal
Warning
ODU2_PM_BDI
ODU2 PM backward
defect indication
Warning
ODU2_PM_DEG
ODU2 PM signal
degraded
Minor
ODU2_PM_LCK
Minor
ODU2_PM_OCI
ODU2 PM open
Minor
ODU2_PM_SSF
ODU2 PM server signal

fail
Warning
ODU2_PM_TIM
ODU2 PM section TTI

mismatch
Minor
ODU2_PM_EXC

Major
ODU2_TCMn_AIS
ODU2 TCMn alarm

indication signal
Warning
ODU2_TCMn_BDI
ODU2 TCMn backward

defect indication
Warning
ODU2_TCMn_DEG
ODU2 TCMn signal

degraded
Minor
ODU2_TCMn_LCK
ODU2 TCMn signal

locked
Minor
ODU2_TCMn_LTC
Loss of ODU2 TCMn

serial connection
Minor
ODU2_TCMn_OCI
ODU2 TCMn open

Minor
ODU2_TCMn_SSF
ODU2 TCMn server

signal fail
Warning
ODU2_TCMn_TIM
ODU2 TCMn TTI

mismatch
Minor
ODU2_TCMn_EXC
ODU2 TCMn section

defect
Major
ODU3_PM_AIS
ODU3 PM alarm
indication signal
Warning
ODU3_PM_BDI
ODU3 PM backward
defect indication
Warning

49
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
ODU3_PM_DEG
ODU3 PM signal
degraded
Minor
ODU3_PM_LCK
Minor
ODU3_PM_OCI
ODU3 PM open
Minor
ODU3_PM_SSF
ODU3 PM server signal

fail
Warning
ODU3_PM_TIM
ODU3 PM section TTI

mismatch
Minor
ODU3_PM_EXC

Major
ODU3_TCMn_AIS
ODU3 TCMn alarm

indication signal
Warning
ODU3_TCMn_BDI
ODU3 TCMn backward

defect indication
Warning
ODU3_TCMn_DEG
ODU3 TCMn signal

degraded
Minor
ODU3_TCMn_LCK
ODU3 TCMn signal

locked
Minor
ODU3_TCMn_LTC
Loss of ODU3 TCMn

serial connection
Minor
ODU3_TCMn_OCI
ODU3 TCMn open

Minor
ODU3_TCMn_SSF
ODU3 TCMn server

signal fail
Warning
ODU3_TCMn_TIM
ODU3 TCMn TTI

mismatch
Minor
ODU3_TCMn_EXC
ODU3 TCMn section

defect
Major
ODU5G_LOFLOM

abnormal
Critical
ODU5G_PM_AIS
ODU5G PM alarm
indication signal
Warning
ODU5G_PM_BDI
ODU5G PM backward
defect indication
Warning
ODU5G_PM_DEG
ODU5G PM signal
degraded
Minor

50
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
ODU5G_PM_EXC
ODU5G PM section BIP8

Major
ODU5G_PM_LCK
ODU5G PM signal locked
Minor
ODU5G_PM_OCI
ODU5G PM open
Minor
ODU5G_PM_SSF
ODU5G PM server signal

fail
Warning
ODU5G_PM_TIM
ODU5G PM section TTI

mismatch
Minor
ODU5G_TCMn_AIS
ODU5G TCMn alarm

indication signal
Warning
ODU5G_TCMn_BDI
ODU5G TCMn backward

defect indication
Warning
ODU5G_TCMn_DEG
ODU5G TCMn signal

degraded
Minor
ODU5G_TCMn_EXC
ODU5G TCMn section

defect
Major
ODU5G_TCMn_LCK
ODU5G TCMn signal

locked
Minor
ODU5G_TCMn_LTC
Loss of ODU5G TCMn

serial connection
Minor
ODU5G_TCMn_OCI
ODU5G TCMn open

Minor
ODU5G_TCMn_SSF
ODU5G TCMn server

signal fail
Warning
ODU5G_TCMn_TIM
ODU5G TCMn TTI

mismatch
Minor
ODUKSP_PS
ODUk SP protection
switch
Major
ODUKSP_STA_INDI
The state of the ODUk

SPRing protection group
Minor
OH_LOOP
Overhead bus loopback
Minor
OLP_PS
Optical line protection

switching
Major
OLP_STA_INDI
The state of the optical line

protection group
Minor

51
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
OMS_BDI
Backward defect
indication at OMS layer
Warning
OMS_BDI-O
Backward defect
indication (overhead) at
OMS layer
Warning
OMS_BDI-P
Backward defect
indication (payload) at
OMS layer
Warning
OMS_FDI

at OMS layer
Warning
OMS_FDI-O

(overhead) at OMS layer
Warning
OMS_FDI-P

(payload) at OMS layer
Warning
OMS_LOS-P

OMS layer
Critical
OMS_SSF
Server signal fail at OMS

layer
Warning
OMS_SSF-O
Server signal fail

(overhead) at OMS layer
Warning
OMS_SSF-P
Server signal fail

(payload) at OMS layer
Warning
OOL
The phase-locked loop is

out of lock
Major
OOS_LOST
Loss of OOS
Minor
OPA_FAIL_INDI
Automatic adjustment of
power during optical
cross-connection failed
Major
OPU0_PLM
OPU0 payload mismatch
Minor
OPU1_PLM
Minor
OPU1_MSIM
OPU1 multiplex structure

indicator mismatch
Minor
OPU1_VCAT_SQM
OPU1 sequence indicator

mismatch
Major
OPU1_VCAT_VcPLM
OPU1 virtual
concatenation payload
mismatch
Minor

52
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
OPU2_MSIM

indicator mismatch
Minor
OPU2_PLM
Minor
OPU3_MSIM

indicator mismatch
Minor
OPU3_PLM
Minor
OPU5G_PLM
OPU5G payload
mismatch
Minor
OSC_BDI
OSC Backward defect

indication
Minor
OSC_DEG
OSC signal degrade
Minor
OSC_LOS
Loss of OSC signal
Critical
OSC_RDI
Remote defect indication
Minor
OTU_AIS
OTU alarm indication

signal
Warning
OTU_LOF
Loss of frame
Critical
OTU_LOM
Loss of Multi-frame
Major
OTU1_AIS
OTU1 alarm indication

signal
Warning
OTU1_BDI
OTU1 backward defect

indication
Warning
OTU1_DEG
OTU1 signal degraded
Minor
OTU1_EXC
OTU1 BIP8 excessive

error defect
Major
OTU1_LOF
The FAS is abnormal
Critical
OTU1_LOM
The MFAS is abnormal
Major
OTU1_SSF
OTU1 server signal fail
Warning
OTU1_TIM
OTU1 TTI mismatch
Minor
OTU2_AIS

signal
Warning
OTU2_BDI

indication
Warning
OTU2_DEG
Minor
OTU2_LOF
The FAS is abnormal
Critical

53
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
OTU2_LOM
Major
OTU2_SSF
Warning
OTU2_TIM
OTU2 TTI mismatch
Minor
OTU2_EXC
OTU2 BIP8 excessive

error defect
Major
OTU3_AIS

signal
Warning
OTU3_BDI

indication
Warning
OTU3_DEG
Minor
OTU3_LOF
The FAS is abnormal
Critical
OTU3_LOM
Major
OTU3_SSF
Warning
OTU3_TIM
OTU3 TTI mismatch
Minor
OTU3_EXC
OTU3 BIP8 excessive

error defect
Major
OTU5G_AIS
OTU5G alarm indication

signal
Warning
OTU5G_BDI
OTU5G backward defect

indication
Warning
OTU5G_DEG
OTU5G signal degraded
Minor
OTU5G_EXC
OTU5G BIP8 excessive

error defect
Major
OTU5G_LOF
The FAS is abnormal
Critical
OTU5G_LOM
Major
OTU5G_SSF
OTU5G server signal fail
Warning
OTU5G_TIM
OTU5G TTI mismatch
Minor
OTS_BDI
Backward defect
indication at OTS layer
Warning
OTS_BDI-O
Backward defect
indication (overhead) at
OTS layer
Warning
OTS_BDI-P
Backward defect
indication (payload) at
OTS layer
Warning

54
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
OTS_LOS
Loss of signal at OTS layer
Critical
OTS_LOS-O
Loss of signal (overhead)

at OTS layer
Major
OTS_LOS-P

OTS layer
Critical
OTS_TIM
Trail trace identifier

mismatch at OTS layer
Minor
OUT_PWR_HIGH
Output optical power is

too high
Major
OUT_PWR_LOW
Output optical power is

excessively low
Major
OWSP_PS
Optical wave share

protection switching
Major
OWSP_STA_INDI
the state of the optical

wave share protection
group
Minor
2.1.16 Alarm List P

This section used a table to list the alarms starting with P.
Issue 02 (2011-10-31)
Name
Description
Level
PATCH_ACT_TIMEOUT
Activated patch overtime
Minor
PATCH_DEACT_TIMEOUT
Deactivated patch
overtime
Minor
PATCH_PKGERR
Patch package file error
Minor
PM_BDI
ODU PM section
backward defect
indication
Major
PM_BEI
ODU PM section
backward error indication
Major
PM_BIP8_OVER
ODU layer, PM section

BIP exceed the upper
threshold
Major
PM_BIP8_SD
Optical channel data unit

layer, path monitoring
section bit interleaved
parity signal degraded
Major

55
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
PM_TIM
ODU layer PM section

TTI mismatch
Major
PORT_MODULE_OFFLINE
Port module offline
Major
PORTSWITCH_FAIL
Optical switch switching

failure
Major
POWER_ABNORMAL
Power supply failure
Major
POWER_DIFF_OVER
Power difference between

optical monitoring active
and standby crossed the
threshold
Major
POWER_FAIL
Power failure
Major
PRBS_LSS
PRBS signal lost alarm
Minor
PTP_SOURCE_SWITCH
PTP time source switching

alarm
Minor
PTP_TIMESTAMP_ABN
PTP time stamp anomaly
Major
PUM_TEM_ALM
Working temperature of
the pump laser over
threshold
Major
PUM_BCM_ALM
Working current of pump

Major
PUMP_COOL_EXC
Cooling current of pump

Critical
2.1.17 Alarm List R

This section used a table to list the alarms starting with R.
Issue 02 (2011-10-31)
Name
Description
Level
R_LOC
Loss of clock on receiving line
Critical
R_LOF
Loss of frame on receiving line
Critical
R_LOS
Loss of signal on receiving line
Critical
R_OOF
Out of frame on receiving line
Critical
R_SLIP
Receiving side frame slipping
Major
RELAY_ALARM_CRITICAL
Critical relay alarm
Critical
RELAY_ALARM_IGNORE
Relay alarm warning
Warning

56
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
RELAY_ALARM_MAJOR
Major relay alarm
Major
RELAY_ALARM_Minor
Remote signal degraded
Minor
REM_SD
Remote signal degraded
Minor
REM_SF
Remote client-side service

unloaded
Minor
REMOTE_FAULT
Remote fault
Minor
RL_CRITICAL_HI
Critical high return loss alarm
Critical
RL_CRITICAL_LOW
Critical low return loss alarm
Critical
RS_CROSSTR
Regenerator section performance

over threshold
Minor
RTC_FAIL
RTC time fail alarm
Major
2.1.18 Alarm List S

This section used a table to list the alarms starting with S.
Issue 02 (2011-10-31)
Name
Description
Level
S1_SYN_CHANGE
Synchronous source
changed in S1 mode
Major
SCC_LOC
SCC loss of clock
Critical
SEC_RADIUS_FAIL
Excessive failures in radius

authentication
Major
SECU_ALM
Security alarm
Major
SERVICE_CAPACITY_E
XCEED_LICENSE
The service capacity

exceeds the license limit
Major
SERVICE_TYPE_EXCEE
D_LICENSE
The service type exceeds

the license limit
Major
SHELF_AREA_POWER_
OVER
Total optical power

consumption of the subrack
Critical
SLAVE_WORKING
The protection board is

working
Warning
SM_BDI
OTU SM section backward

defect indication
Major

57
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
SM_BEI
OTU layer, SM section

Major
SM_BIP8_OVER
OTU layer, SM section bit

interleaved parity exceeds
threshold
Major
SM_BIP8_SD
OTU layer, SM section bit

interleaved parity
deterioration
Major
SM_IAE
OTU layer, SM section

incoming alignment error
Major
SM_TIM
OTU layer, SM Trail Trace

Identifier (TTI) is
mismatched
Major
SNCP_FAIL
The SNCP switching

failure
Critical
SPAN_LOSS_HIGH
Span loss is excessively

high
Major
SPAN_LOSS_LOW
Span loss is excessively

low
Major
SO_SK_MISMATCH
The number of timeslots

bundled at the LCAS
source is not consistent
with the number of
timeslots bundled at the
LCAS sink
Critical
SPEED_OVER
Data rate exceeding the set

limits
Major
STORM_CUR_QUENUM_
OVER
Alarm storm
Minor
SUBRACK_TYPE_MISMATCH
The configured subrack

does not match the physical
subrack
Major
SUBRACK_COMM_PS
Inter-subrack
communication protection
switching alarm
Major
SUBRACK_ID_CONFLICT
Conflict of subrack ID
Critical
SUBRACK_ID_MISMATCH
Mismatch of subrack ID
Major
SUBRACK_LOOP
Loop of subrack
Critical

58
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
Name
Description
Level
SUM_INPWR_HI
Sum input optical power is

too high
Major
SUM_INPWR_LOW
Sum input optical power is

excessively low
Major
SW_SNCP_PS
SW SNCP protection
switching
Major
SW_SNCP_STA_INDI
The state of the SubWavelength SNCP

protection group.
Minor
SWDL_ACTIVATED_TIM
EOUT
Activation time out
Critical
SWDL_AUTOMATCH_IN
H
Automatic match inhibited
Minor
SWDL_BD_EXCLUDE
Board excluded from

software download during
software package loading
Major
SWDL_CHGMNG_NOMATCH
SCC board changed
Critical
SWDL_COMMIT_FAIL
Commit failure
Minor
SWDL_INPROCESS
NE is loading package
Warning
SWDL_NEPKGCHECK
Loss of file
Critical
SWDL_PKG_NOBDSOFT
Board software cancelled

during the loading of
package
Minor
SWDL_PKGVER_MM
Package version
conformance check failed
Minor
SWDL_ROLLBACK_FAIL
NE rollback failed
Minor
SYN_BAD
A synchronization source
degrade alarm
Minor
SYNC_FAIL
Batch backup failed
Minor
SYSPARA_CFDB_NOSAME
Difference between the

SCC data and the CF card
data
Minor
SYNC_C_LOS
The loss of synchronization

source level
Warning
SYNC_DISABLE
Automatic synchronization
of the system control board
is disabled
Minor

59
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
SYNC_F_M_SWITCH
The forced or manual

switching state of a clock
source
Warning
SYNC_LOCKOFF
The clock source in the

priority list is locked
Warning
SYSPARA_CFDB_NOSAME
Difference between the

SCC data and the CF card
data
Minor
SYSLOG_COMM_FAIL
The communication
between an NE and the
syslog server fails
Major
2.1.19 Alarm List T

This section used a table to list the alarms starting with T.
Issue 02 (2011-10-31)
Name
Description
Level
T_LOSEX
A board has detected the

loss of signal in the service
bus of the backplane
Major
T_SLIP
Transmitted side frame

slipping
Major
TD
Transmitter degrade
Critical
TEM_HA
Laser temperature is too

high
Major
TEM_LA
Laser temperature is
excessively low
Major
TEMP_OVER
Working temperature over

threshold
Major
TEST_STATUS
The board is in the test

status
Warning
TF
Transmission Failure
Critical
THUNDERALM
Thunder protection circuit

failure
Minor
TIME_LOCK_FAIL
Time lock failure alarm
Major
TIME_LOS
The loss of the timing

source level
Major

60
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
TIME_NO_TRACE_MOD
E
The time enters the nontrace mode
Minor
TR_LOC
The clock of the crossconnect board is faulty
Major
TS_CFG_MISMATCH
The timeslot configuration

mismatch alarm
Major
TU_AIS_VC3
A TU alarm indication
signal in the VC-3 lower
order path
Major
TU_LOP_VC3
An alarm indicating the

loss of pointer in the VC-3
lower order path
Major
2.1.20 Alarm List V

This section used a table to list the alarms starting with V.
Name
Description
Level
VCAT_LOA
Delay of multiframes
Major
VCAT_LOM_VC3
The loss of the virtual

concatenation multiframe
in the VC-3 path
Major
VCAT_LOM_VC4
The loss of the virtual

concatenation multiframe
in the VC-4 path
Major
VLAN_SNCP_PS
VLAN SNCP switching
Major
VOADATA_MIS
Mismatch of attenuation
attribute
Major
VOA_ADJUST_FAIL
VOA adjustment failed
Major
2.1.21 Alarm List W

This section used a table to list the alarms starting with W.
Issue 02 (2011-10-31)
Name
Description
Level
W_R_FAIL
Writing or reading chip

register failed
Major

61
OptiX OSN 8800/6800/3800

2 Alarm List
Name
Description
Level
WAVE_ADD_ABN
APE detect wavelengths

added
Warning
WAVE_DROP_ABN
APE detect wavelengths

dropped
Warning
WAVEDATA_MIS
Mismatch of wave or band

attribute
Major
WAVELEN_OVER
Wavelength over
threshold
Major
WRG_BD_TYPE
Real board is mismatched

with configured board
Major
2.1.22 Alarm List X

This section used a table to list the alarms starting with X.
Name
Description
Level
XC_UNSWITCH
The cross-connect matrix

of the board is not
switched
Major
2.2 Board Alarm List

Lists the alarms of every board.
2.2.1 ATE Board Alarm List

BD_STATUS
WRG_BD_TYPE
2.2.2 AUX Board Alarm List

TN11AUX
BD_STATUS
HARD_BAD
NO_BD_SOFT
COMMUN_FAIL
HARD_ERR
NO_ELABEL
ETH_MISCONNECT
LAN_LOC
WRG_BD_TYPE
TN22AUX
Issue 02 (2011-10-31)

62
OptiX OSN 8800/6800/3800

2 Alarm List
BD_STATUS
HARD_ERR
RELAY_ALARM_MAJOR
COMMUN_FAIL
RELAY_ALARM_MINOR
HARD_BAD
RELAY_ALARM_IGNORE
WRG_BD_TYPE
BD_STATUS
NO_BD_SOFT
RELAY_ALARM_MAJOR
COMMUN_FAIL
NO_ELABEL
RELAY_ALARM_MINOR
HARD_BAD
WRG_BD_TYPE
HARD_ERR
RELAY_ALARM_IGNORE
TN21AUX
TN51AUX
BD_STATUS
HARD_BAD
COMMUN_FAIL
HARD_ERR
WRG_BD_TYPE
TN16AUX
BD_STATUS
HARD_ERR
SWDL_PKGVER_MM
BOOTROM_BAD
NO_BD_SOFT
TEMP_OVER
COMMUN_FAIL
NO_ELABEL
WRG_BD_TYPE
HARD_BAD
POWER_FAIL
2.2.3 BMD4 Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
OMS_FDI_O
OMS_SSF_P
OMS_BDI
OMS_FDI_P
OPA_FAIL_INDI
OMS_BDI_O
OMS_LOS_P
WAVEDATA_MIS
OMS_BDI_P
OMS_SSF
WRG_BD_TYPE
OMS_FDI
OMS_SSF_O

63
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.4 BMD8 Board Alarm List

BD_STATUS
OMS_FDI_O
OMS_SSF_P
OMS_BDI
OMS_FDI_P
OPA_FAIL_INDI
OMS_BDI_O
OMS_LOS_P
WAVEDATA_MIS
OMS_BDI_P
OMS_SSF
WRG_BD_TYPE
OMS_FDI
OMS_SSF_O
2.2.5 CMR1 Board Alarm List

BD_STATUS
WAVEDATA_MIS
WRG_BD_TYPE
WAVEDATA_MIS
WRG_BD_TYPE
WAVEDATA_MIS
WRG_BD_TYPE
OPA_FAIL_INDI

BD_STATUS
OPA_FAIL_INDI

BD_STATUS
OPA_FAIL_INDI
2.2.8 CRPC Board Alarm List
Issue 02 (2011-10-31)
AD_CHECK_FAIL
LOCK_CUR_FAIL
POWER_FAIL
BD_STATUS
LSR_WILL_DIE
PUMP_COOL_EXC
COMMUN_FAIL
NO_BD_PARA
PUM_BCM_ALM
FAN_FAIL
NO_BD_SOFT
RL_CRITICAL_HI
FPGA_ABN
OPA_FAIL_INDI
RL_CRITICAL_LOW
LASER_HAZARD_WARNING
OUT_PWR_HIGH
WRG_BD_TYPE

64
OptiX OSN 8800/6800/3800

LOCKPOW_MIS
2 Alarm List
OUT_PWR_LOW
W_R_FAIL
BD_STATUS
NO_BD_SOFT
OMS_SSF
COMMUN_FAIL
NO_ELABEL
OMS_SSF_O
HARD_BAD
OMS_BDI
OMS_SSF_P
HARD_ERR
OMS_BDI_O
OPA_FAIL_INDI
MODULEFILE_UPDATE_F
AIL
OMS_BDI_P
SUM_INPWR_HI
MODULE_TEMP_OVER
OMS_FDI
SUM_INPWR_LOW
MOD_COM_FAIL
OMS_FDI_O
TEMP_OVER
MUT_LOS
OMS_FDI_P
WAVEDATA_MIS
NO_BD_PARA
OMS_LOS_P
WRG_BD_TYPE
BD_STATUS
NO_ELABEL
OMS_SSF_O
COMMUN_FAIL
OMS_BDI
OMS_SSF_P
HARD_BAD
OMS_BDI_O
OPA_FAIL_INDI
HARD_ERR
OMS_BDI_P
SUM_INPWR_HI
MODULE_COOLCUR_OV
ER
OMS_FDI
SUM_INPWR_LOW
MODULE_TEMP_OVER
OMS_FDI_O
TEMP_OVER
MUT_LOS
OMS_FDI_P
WAVEDATA_MIS
NO_BD_PARA
OMS_LOS_P
WRG_BD_TYPE
NO_BD_SOFT
OMS_SSF
2.2.9 D40V Board Alarm List
2.2.10 D40 Board Alarm List
2.2.11 DAS1 Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
OA_LOW_GAIN
PUMP_COOL_EXC
BEFFEC_EXC
OPA_FAIL_INDI
PUM_BCM_ALM

65
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
OSC_BDI
PUM_TEM_ALM
GAINDATA_MIS
OSC_DEG
R_LOF
HARD_BAD
OSC_LOS
SCC_LOC
HARD_ERR
OTS_BDI
SPAN_LOSS_HIGH
IN_PWR_HIGH
OTS_BDI_O
SPAN_LOSS_LOW
IN_PWR_LOW
OTS_BDI_P
SUM_INPWR_HI
OTS_LOS
SUM_INPWR_LOW
OTS_LOS_O
TD
LOOP_ALM
OTS_LOS_P
TEMP_OVER
LSR_WILL_DIE
OTS_TIM
TF
MUT_LOS
OOS_LOST
VOADATA_MIS
NO_BD_PARA
OUT_PWR_HIGH
VOA_ADJUST_FAIL
NO_BD_SOFT
OUT_PWR_LOW
WAVEDATA_MIS
PORT_MODULE_OFFLINE
WRG_BD_TYPE
NO_ELABEL
2.2.12 DCU Board Alarm List

BD_STATUS
OPA_FAIL_INDI
WRG_BD_TYPE
BD_STATUS
NO_BD_SOFT
OCh_SSF_P
CLIENT_PORT_PS
NO_ELABEL
OPA_FAIL_INDI
OCh_FDI
OWSP_PS
COMMUN_FAIL
OCh_FDI_O
OWSP_STA_INDI
HARD_BAD
OCh_FDI_P
POWER_DIFF_OVER
HARD_ERR
OCh_LOS_P
R_LOS
INTRA_OTU_PS
OCh_OCI
TEMP_OVER
2.2.13 DCP Board Alarm List

TN11DCP
Issue 02 (2011-10-31)

66
OptiX OSN 8800/6800/3800

2 Alarm List
INTRA_OTU_STA_INDI
OCh_SSF
NO_BD_PARA
OCh_SSF_O
WRG_BD_TYPE
TN12DCP
BD_STATUS
NO_BD_SOFT
OPA_FAIL_INDI
CLIENT_PORT_PS
OCh_FDI
OWSP_PS
OCh_FDI_O
OWSP_STA_INDI
COMMUN_FAIL
OCh_FDI_P
POWER_DIFF_OVER
HARD_BAD
OCh_LOS_P
R_LOS
HARD_ERR
OCh_OCI
TEMP_OVER
INTRA_OTU_PS
OCh_SSF
WRG_BD_TYPE
INTRA_OTU_STA_INDI
OCh_SSF_O
NO_BD_PARA
OCh_SSF_P
2.2.14 DFIU Board Alarm List

BD_STATUS
OTS_BDI-O
OTS_TIM
MUT_LOS
OTS_BDI-P
WAVEDATA_MIS
OOS_LOST
OTS_LOS
WRG_BD_TYPE
OPA_FAIL_INDI
OTS_LOS-O
OTS_BDI
OTS_LOS-P
2.2.15 DMR1 Board Alarm List

BD_STATUS
WAVEDATA_MIS
WRG_BD_TYPE
OPA_FAIL_INDI
Issue 02 (2011-10-31)

67
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.16 EAS2 Board Alarm List
Issue 02 (2011-10-31)
ALM_GFP_dCSF
EX_ETHOAM_MPID_C
NFLCT
LSR_INVALID
ALM_GFP_dLFD
FCS_ERR
LSR_NO_FITED
AU_AIS
FLOW_OVER
LSR_WILL_DIE
AU_LOP
HARD_BAD
MULTI_RPL_OWNER
B3_EXC_VC3
HARD_ERR
NO_BD_SOFT
B3_EXC_VC4
HP_RDI
NO_ELABEL
B3_SD_VC3
HP_SLM
OUT_PWR_HIGH
B3_SD_VC4
HP_TIM
OUT_PWR_LOW
BDID_ERROR
HP_UNEQ
PORT_MODULE_OFFLINE
BD_STATUS
IN_PWR_HIGH
R_LOS
BOOTROM_BAD
IN_PWR_LOW
SLAVE_WORKING
CHIP_ABN
LAG_PORT_FAIL
SO_SK_MISMATCH
COMMUN_FAIL
LAG_VC_PORT_FAIL
TD
DLAG_PROTECT_FAIL
LASER_MODULE_MIS
MATCH
TEMP_OVER
ETHOAM_DISCOVER_FAIL
LCAS_FOPR
TEM_HA
ETHOAM_RMT_CRIT_FAULT
LCAS_FOPT
TEM_LA
ETHOAM_RMT_LOOP
LCAS_PLCR
TEST_STATUS
ETHOAM_RMT_SD
LCAS_PLCT
TF
ETHOAM_SELF_LOOP
LCAS_TLCR
TR_LOC
ETHOAM_VCG_SELF_LOOP
LCAS_TLCT
TU_AIS_VC3
ETH_CFM_LOC
LINK_ERR
TU_LOP_VC3
ETH_CFM_MACSTATUS
LOOP_ALM
T_LOSEX
ETH_CFM_MISMERGE
LPT_RFI
VCAT_LOA
ETH_CFM_RDI
LP_RDI_VC3
VCAT_LOM_VC3
ETH_CFM_UNEXPERI
LP_SLM_VC3
VCAT_LOM_VC4
EX_ETHOAM_CC_LOS
LP_UNEQ_VC3
WRG_BD_TYPE

68
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.17 ECOM Board Alarm List

BD_STATUS
LSR_FORCE_OPEN
TEM_HA
HARD_BAD
LSR_WILL_DIE
TEM_LA
HARD_ERR
OUT_PWR_HIGH
TEMP_OVER
IN_PWR_HIGH
OUT_PWR_LOW
TF
IN_PWR_LOW
PORT_MODULE_OFFLINE
WAVEDATA_MIS
R_LOS
WRG_BD_TYPE
LOOP_ALM
TD
2.2.18 EFI Board Alarm List

TN11EFI
BD_STATUS
RELAY_ALARM_MINOR
ETH_MISCONNECT
RELAY_ALARM_IGNORE
WRG_BD_TYPE
LAN_LOC
RELAY_ALARM_MAJOR
TN61EFI
BD_STATUS
RELAY_ALARM_MINOR
ETH_MISCONNECT
RELAY_ALARM_IGNORE
WRG_BD_TYPE
LAN_LOC
RELAY_ALARM_MAJOR
2.2.19 EFI1 Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
RELAY_ALARM_MINOR
HARD_BAD
RELAY_ALARM_IGNORE
WRG_BD_TYPE
LAN_LOC
RELAY_ALARM_MAJOR

69
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.20 EFI2 Board Alarm List

BD_STATUS
HARD_BAD
ETH_MISCONNECT
WRG_BD_TYPE
LAN_LOC
2.2.21 EGSH Board Alarm List
Issue 02 (2011-10-31)
ALM_GFP_dCSF
EX_ETHOAM_CC_LOS
LSR_WILL_DIE
ALM_GFP_dLFD
EX_ETHOAM_MPID_CNFL
CT
MULTI_RPL_OWNER
AU_AIS
FCS_ERR
NO_BD_SOFT
AU_LOP
HARD_BAD
NO_ELABEL
B3_EXC_VC3
HARD_ERR
OUT_PWR_HIGH
B3_EXC_VC4
HP_RDI
OUT_PWR_LOW
B3_SD_VC3
HP_SLM
PORT_MODULE_OFFLINE
B3_SD_VC4
HP_UNEQ
R_LOS
BDID_ERROR
IN_PWR_HIGH
SLAVE_WORKING
BD_STATUS
IN_PWR_LOW
SO_SK_MISMATCH
BOOTROM_BAD
LAG_PORT_FAIL
TD
CHIP_ABN
TEMP_OVER
COMMUN_FAIL
LCAS_FOPR
TEM_HA
DLAG_PROTECT_FAIL
LCAS_FOPT
TEM_LA
ETHOAM_DISCOVER_FA
IL
LCAS_PLCR
TEST_STATUS
ETHOAM_RMT_CRIT_FA
ULT
LCAS_PLCT
TF
ETHOAM_RMT_LOOP
LCAS_TLCR
TR_LOC
ETHOAM_RMT_SD
LCAS_TLCT
TU_AIS_VC3
ETHOAM_SELF_LOOP
LINK_ERR
TU_LOP_VC3
ETHOAM_VCG_SELF_LO
OP
LOOP_ALM
T_LOSEX
ETH_CFM_LOC
LPT_RFI
VCAT_LOA

70
OptiX OSN 8800/6800/3800

2 Alarm List
ETH_CFM_MACSTATUS
LP_RDI_VC3
VCAT_LOM_VC3
ETH_CFM_MISMERGE
LP_SLM_VC3
VCAT_LOM_VC4
ETH_CFM_RDI
LP_UNEQ_VC3
WRG_BD_TYPE
ETH_CFM_UNEXPERI
LSR_INVALID
2.2.22 ELQX Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_TCM3_TIM
ODU2_TCM3_SSF
B1_SD
ODU1_TCM4_AIS
ODU2_TCM3_TIM
BD_STATUS
ODU1_TCM4_BDI
ODU2_TCM4_AIS
BEFFEC_EXC
ODU1_TCM4_DEG
ODU2_TCM4_BDI
BUS_ERR
ODU1_TCM4_LCK
ODU2_TCM4_DEG
CLIENT_PORT_PS
ODU1_TCM4_LTC
ODU2_TCM4_LCK
ODU1_TCM4_OCI
ODU2_TCM4_LTC
ODU1_TCM4_SSF
ODU2_TCM4_OCI
COMMUN_FAIL
ODU1_TCM4_TIM
ODU2_TCM4_SSF
HARD_BAD
ODU1_TCM5_AIS
ODU2_TCM4_TIM
HARD_ERR
ODU1_TCM5_BDI
ODU2_TCM5_AIS
IN_PWR_HIGH
ODU1_TCM5_DEG
ODU2_TCM5_BDI
IN_PWR_LOW
ODU1_TCM5_LCK
ODU2_TCM5_DEG
J0_MM
ODU1_TCM5_LTC
ODU2_TCM5_LCK
ODU1_TCM5_OCI
ODU2_TCM5_LTC
LOCAL_FAULT
ODU1_TCM5_SSF
ODU2_TCM5_OCI
LOOP_ALM
ODU1_TCM5_TIM
ODU2_TCM5_SSF
LPT_ACTIVE
ODU1_TCM6_AIS
ODU2_TCM5_TIM
LSR_FORCE_OPEN
ODU1_TCM6_BDI
ODU2_TCM6_AIS
LSR_INVALID
ODU1_TCM6_DEG
ODU2_TCM6_BDI
LSR_WILL_DIE
ODU1_TCM6_LCK
ODU2_TCM6_DEG
NO_BD_SOFT
ODU1_TCM6_LTC
ODU2_TCM6_LCK
NO_ELABEL
ODU1_TCM6_OCI
ODU2_TCM6_LTC

71
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
NULL_SEND
ODU1_TCM6_SSF
ODU2_TCM6_OCI
ODU1_LOFLOM
ODU1_TCM6_TIM
ODU2_TCM6_SSF
ODU1_PM_AIS
ODU2_LOFLOM
ODU2_TCM6_TIM
ODU1_PM_BDI
ODU2_PM_AIS
ODU_SNCP_PS
ODU1_PM_DEG
ODU2_PM_BDI
ODU_SNCP_STA_INDI
ODU1_PM_LCK
ODU2_PM_DEG
OPA_FAIL_INDI
ODU1_PM_OCI
ODU2_PM_LCK
OPU2_MSIM
ODU1_PM_SSF
ODU2_PM_OCI
OPU2_PLM
ODU1_PM_TIM
ODU2_PM_SSF
OTU2_AIS
ODU1_TCM1_AIS
ODU2_PM_TIM
OTU2_BDI
ODU1_TCM1_BDI
ODU2_TCM1_AIS
OTU2_DEG
ODU1_TCM1_DEG
ODU2_TCM1_BDI
OTU2_LOF
ODU1_TCM1_LCK
ODU2_TCM1_DEG
OTU2_LOM
ODU1_TCM1_LTC
ODU2_TCM1_LCK
OTU2_SSF
ODU1_TCM1_OCI
ODU2_TCM1_LTC
OTU2_TIM
ODU1_TCM1_SSF
ODU2_TCM1_OCI
OUT_PWR_HIGH
ODU1_TCM1_TIM
ODU2_TCM1_SSF
OUT_PWR_LOW
ODU1_TCM2_AIS
ODU2_TCM1_TIM
PORT_MODULE_OFFLINE
ODU1_TCM2_BDI
ODU2_TCM2_AIS
PRBS_LSS
ODU1_TCM2_DEG
ODU2_TCM2_BDI
REMOTE_FAULT
ODU1_TCM2_LCK
ODU2_TCM2_DEG
REM_SD
ODU1_TCM2_LTC
ODU2_TCM2_LCK
REM_SF
ODU1_TCM2_OCI
ODU2_TCM2_LTC
R_LOC
ODU1_TCM2_SSF
ODU2_TCM2_OCI
R_LOF
ODU1_TCM2_TIM
ODU2_TCM2_SSF
R_LOS
ODU1_TCM3_AIS
ODU2_TCM2_TIM
TD
ODU1_TCM3_BDI
ODU2_TCM3_AIS
TEMP_OVER
ODU1_TCM3_DEG
ODU2_TCM3_BDI
TEM_HA
ODU1_TCM3_LCK
ODU2_TCM3_DEG
TEM_LA
ODU1_TCM3_LTC
ODU2_TCM3_LCK
TF

72
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM3_OCI
ODU2_TCM3_LTC
WAVEDATA_MIS
ODU1_TCM3_SSF
ODU2_TCM3_OCI
WRG_BD_TYPE
BD_STATUS
HARD_BAD
TEMP_OVER
BUS_ERR
HARD_ERR
WRG_BD_TYPE
COMMUN_FAIL
NO_ELABEL
2.2.23 ENQ2 Board Alarm List

TN54ENQ2(STND)
TN54ENQ2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM3_TIM
ODU2_TCM3_BDI
BEFFEC_EXC
ODU1_TCM4_AIS
ODU2_TCM3_DEG
BUS_ERR
ODU1_TCM4_BDI
ODU2_TCM3_LCK
COMMUN_FAIL
ODU1_TCM4_DEG
ODU2_TCM3_LTC
HARD_BAD
ODU1_TCM4_LCK
ODU2_TCM3_OCI
HARD_ERR
ODU1_TCM4_LTC
ODU2_TCM3_SSF
LOOP_ALM
ODU1_TCM4_OCI
ODU2_TCM3_TIM
NO_BD_SOFT
ODU1_TCM4_SSF
ODU2_TCM4_AIS
NO_ELABEL
ODU1_TCM4_TIM
ODU2_TCM4_BDI
NULL_SEND
ODU1_TCM5_AIS
ODU2_TCM4_DEG
ODU0_LOFLOM
ODU1_TCM5_BDI
ODU2_TCM4_LCK
ODU0_PM_AIS
ODU1_TCM5_DEG
ODU2_TCM4_LTC
ODU0_PM_BDI
ODU1_TCM5_LCK
ODU2_TCM4_OCI
ODU0_PM_DEG
ODU1_TCM5_LTC
ODU2_TCM4_SSF
ODU0_PM_LCK
ODU1_TCM5_OCI
ODU2_TCM4_TIM
ODU0_PM_OCI
ODU1_TCM5_SSF
ODU2_TCM5_AIS
ODU0_PM_SSF
ODU1_TCM5_TIM
ODU2_TCM5_BDI
ODU0_PM_TIM
ODU1_TCM6_AIS
ODU2_TCM5_DEG
ODU1_LOFLOM
ODU1_TCM6_BDI
ODU2_TCM5_LCK
ODU1_PM_AIS
ODU1_TCM6_DEG
ODU2_TCM5_LTC

73
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU1_PM_BDI
ODU1_TCM6_LCK
ODU2_TCM5_OCI
ODU1_PM_DEG
ODU1_TCM6_LTC
ODU2_TCM5_SSF
ODU1_PM_LCK
ODU1_TCM6_OCI
ODU2_TCM5_TIM
ODU1_PM_OCI
ODU1_TCM6_SSF
ODU2_TCM6_AIS
ODU1_PM_SSF
ODU1_TCM6_TIM
ODU2_TCM6_BDI
ODU1_PM_TIM
ODU2_PM_AIS
ODU2_TCM6_DEG
ODU1_TCM1_AIS
ODU2_PM_BDI
ODU2_TCM6_LCK
ODU1_TCM1_BDI
ODU2_PM_DEG
ODU2_TCM6_LTC
ODU1_TCM1_DEG
ODU2_PM_LCK
ODU2_TCM6_OCI
ODU1_TCM1_LCK
ODU2_PM_OCI
ODU2_TCM6_SSF
ODU1_TCM1_LTC
ODU2_PM_SSF
ODU2_TCM6_TIM
ODU1_TCM1_OCI
ODU2_PM_TIM
ODUKSP_PS
ODU1_TCM1_SSF
ODU2_TCM1_AIS
ODUKSP_STA_INDI
ODU1_TCM1_TIM
ODU2_TCM1_BDI
ODU_SNCP_PS
ODU1_TCM2_AIS
ODU2_TCM1_DEG
ODU_SNCP_STA_INDI
ODU1_TCM2_BDI
ODU2_TCM1_LCK
OPU1_MSIM
ODU1_TCM2_DEG
ODU2_TCM1_LTC
OPU1_PLM
ODU1_TCM2_LCK
ODU2_TCM1_OCI
OPU2_MSIM
ODU1_TCM2_LTC
ODU2_TCM1_SSF
OPU2_PLM
ODU1_TCM2_OCI
ODU2_TCM1_TIM
OTU2_AIS
ODU1_TCM2_SSF
ODU2_TCM2_AIS
OTU2_BDI
ODU1_TCM2_TIM
ODU2_TCM2_BDI
OTU2_DEG
ODU1_TCM3_AIS
ODU2_TCM2_DEG
OTU2_LOF
ODU1_TCM3_BDI
ODU2_TCM2_LCK
OTU2_LOM
ODU1_TCM3_DEG
ODU2_TCM2_LTC
OTU2_SSF
ODU1_TCM3_LCK
ODU2_TCM2_OCI
OTU2_TIM
ODU1_TCM3_LTC
ODU2_TCM2_SSF
PRBS_LSS
ODU1_TCM3_OCI
ODU2_TCM2_TIM
TEMP_OVER
ODU1_TCM3_SSF
ODU2_TCM3_AIS
WRG_BD_TYPE

74
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.24 FAN Board Alarm List

TN11FAN/TN21FAN/TN51FAN
BD_STATUS
FAN_FAULT
WRG_BD_TYPE
BD_STATUS
FAN_FAULT
WRG_BD_TYPE
FAN_FAIL
HARD_ERR
FAN_FAIL
TN16FAN
2.2.25 FIU Board Alarm List

TN13FIU
BD_STATUS
OTS_BDI-O
OTS_TIM
MUT_LOS
OTS_BDI-P
WAVEDATA_MIS
OOS_LOST
OTS_LOS
WRG_BD_TYPE
OPA_FAIL_INDI
OTS_LOS-O
OTS_BDI
OTS_LOS-P
TN12FIU
BD_STATUS
OTS_BDI
SUM_INPWR_HI
COMMUN_FAIL
OTS_BDI-O
SUM_INPWR_LOW
HARD_BAD
OTS_BDI-P
TEMP_OVER
HARD_ERR
OTS_LOS
WAVEDATA_MIS
MUT_LOS
OTS_LOS-O
WRG_BD_TYPE
OOS_LOST
OTS_LOS-P
OPA_FAIL_INDI
OTS_TIM
TN11FIU
Issue 02 (2011-10-31)
BD_STATUS
OOS_LOST
OTS_TIM
COMMUN_FAIL
OPA_FAIL_INDI
SUM_INPWR_HI

75
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_BAD
OTS_BDI
SUM_INPWR_LOW
HARD_ERR
OTS_BDI-O
TEMP_OVER
MUT_LOS
OTS_BDI-P
WAVEDATA_MIS
NO_BD_PARA
OTS_LOS
WRG_BD_TYPE
NO_BD_SOFT
OTS_LOS-O
NO_ELABEL
OTS_LOS-P
TN21FIU
BD_STATUS
OTS_BDI-O
OTS_TIM
MUT_LOS
OTS_BDI-P
WAVEDATA_MIS
OOS_LOST
OTS_LOS
WRG_BD_TYPE
OPA_FAIL_INDI
OTS_LOS-O
OTS_BDI
OTS_LOS-P
2.2.26 GFU Board Alarm List

BD_STATUS
OPA_FAIL_INDI
WRG_BD_TYPE
COMMUN_FAIL
2.2.27 HBA Board Alarm List

BD_STATUS
Issue 02 (2011-10-31)
MODULEFILE_UPDATE_FAI
L
SUM_INPWR_HI
COMMUN_FAIL
MUT_LOS
SUM_INPWR_LOW
GAINDATA_MIS
OA_LOW_GAIN
TEMP_OVER
HARD_BAD
OPA_FAIL_INDI
WAVEDATA_MIS
HARD_ERR
SPAN_LOSS_HIGH
WRG_BD_TYPE
LASER_HAZARD_W
ARNING
SPAN_LOSS_LOW

76
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.28 HSC1 Board Alarm List

ALM_HANGUP
LSR_COOL_ALM
R_LOF
BD_STATUS
LSR_WILL_DIE
R_SLIP
COMMUN_FAIL
NO_BD_PARA
SCC_LOC
CRC4_CROSSTR
NO_BD_SOFT
TD
HARD_BAD
NO_ELABEL
TEMP_OVER
HARD_ERR
OSC_LOS
TF
IN_PWR_HIGH
OSC_RDI
T_SLIP
IN_PWR_LOW
OUT_PWR_HIGH
WRG_BD_TYPE
LOOP_ALM
OUT_PWR_LOW
2.2.29 ITL Board Alarm List

TN11ITL
BD_STATUS
OMS_FDI-O
OMS_SSF-P
OMS_BDI
OMS_FDI-P
OPA_FAIL_INDI
OMS_BDI-O
OMS_LOS-P
WAVEDATA_MIS
OMS_BDI-P
OMS_SSF
WRG_BD_TYPE
OMS_FDI
OMS_SSF-O
TN12ITL
Issue 02 (2011-10-31)
BD_STATUS
OMS_BDI-P
OMS_SSF-O
COMMUN_FAIL
OMS_FDI
OMS_SSF-P
HARD_BAD
OMS_FDI-O
OPA_FAIL_INDI
HARD_ERR
OMS_FDI-P
TEMP_OVER
OMS_BDI
OMS_LOS-P
WAVEDATA_MIS
OMS_BDI-O
OMS_SSF
WRG_BD_TYPE

77
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.30 L4G Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU5G_PM_OCI
ODU5G_TCM5_LCK
B1_SD
ODU5G_PM_SSF
ODU5G_TCM5_LTC
BD_STATUS
ODU5G_PM_TIM
ODU5G_TCM5_OCI
BEFFEC_EXC
ODU5G_TCM1_AIS
ODU5G_TCM5_SSF
BUS_ERR
ODU5G_TCM1_BDI
ODU5G_TCM5_TIM
CLIENT_PORT_PS
ODU5G_TCM1_DEG
ODU5G_TCM6_AIS
ODU5G_TCM1_EXC
ODU5G_TCM6_BDI
ODU5G_TCM1_LCK
ODU5G_TCM6_DEG
COMMUN_FAIL
ODU5G_TCM1_LTC
ODU5G_TCM6_EXC
HARD_BAD
ODU5G_TCM1_OCI
ODU5G_TCM6_LCK
HARD_ERR
ODU5G_TCM1_SSF
ODU5G_TCM6_LTC
IN_PWR_HIGH
ODU5G_TCM1_TIM
ODU5G_TCM6_OCI
IN_PWR_LOW
ODU5G_TCM2_AIS
ODU5G_TCM6_SSF
J0_MM
ODU5G_TCM2_BDI
ODU5G_TCM6_TIM
LAG_PORT_FAIL
ODU5G_TCM2_DEG
OPA_FAIL_INDI
LAG_VC_PORT_FAIL
ODU5G_TCM2_EXC
OPU5G_PLM
ODU5G_TCM2_LCK
OTU5G_AIS
LINK_ERR
ODU5G_TCM2_LTC
OTU5G_BDI
LOOP_ALM
ODU5G_TCM2_OCI
OTU5G_DEG
LPT_ACTIVE
ODU5G_TCM2_SSF
OTU5G_EXC
LSR_FORCE_OPEN
ODU5G_TCM2_TIM
OTU5G_LOF
LSR_INVALID
ODU5G_TCM3_AIS
OTU5G_LOM
LSR_WILL_DIE
ODU5G_TCM3_BDI
OTU5G_SSF
MS_AIS
ODU5G_TCM3_DEG
OTU5G_TIM
MS_RDI
ODU5G_TCM3_EXC
OUT_PWR_HIGH
MS_SNCP_PS
ODU5G_TCM3_LCK
OUT_PWR_LOW
MS_SNCP_STA_INDI
ODU5G_TCM3_LTC
PORT_MODULE_OFFLINE
NO_BD_SOFT
ODU5G_TCM3_OCI
REM_SD
NO_ELABEL
ODU5G_TCM3_SSF
REM_SF

78
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI
ODU5G_TCM3_TIM
R_LOC
OCh_FDI_O
ODU5G_TCM4_AIS
R_LOF
OCh_FDI_P
ODU5G_TCM4_BDI
R_LOS
OCh_LOS_P
ODU5G_TCM4_DEG
SW_SNCP_PS
OCh_OCI
ODU5G_TCM4_EXC
SW_SNCP_STA_INDI
OCh_SSF
ODU5G_TCM4_LCK
TD
OCh_SSF_O
ODU5G_TCM4_LTC
TEMP_OVER
OCh_SSF_P
ODU5G_TCM4_OCI
TEM_HA
ODU5G_LOFLOM
ODU5G_TCM4_SSF
TEM_LA
ODU5G_PM_AIS
ODU5G_TCM4_TIM
TF
ODU5G_PM_BDI
ODU5G_TCM5_AIS
VLAN_SNCP_PS
ODU5G_PM_DEG
ODU5G_TCM5_BDI
WAVEDATA_MIS
ODU5G_PM_EXC
ODU5G_TCM5_DEG
WRG_BD_TYPE
ODU5G_PM_LCK
ODU5G_TCM5_EXC
2.2.31 LDGD Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_DEG
ODU1_TCM5_DEG
B1_SD
ODU1_PM_EXC
ODU1_TCM5_EXC
B2_EXC
ODU1_PM_LCK
ODU1_TCM5_LCK
B2_SD
ODU1_PM_OCI
ODU1_TCM5_LTC
BD_STATUS
ODU1_PM_SSF
ODU1_TCM5_OCI
BEFFEC_EXC
ODU1_PM_TIM
ODU1_TCM5_SSF
BUS_ERR
ODU1_TCM1_AIS
ODU1_TCM5_TIM
CLIENT_PORT_PS
ODU1_TCM1_BDI
ODU1_TCM6_AIS
ODU1_TCM1_DEG
ODU1_TCM6_BDI
ODU1_TCM1_EXC
ODU1_TCM6_DEG
COMMUN_FAIL
ODU1_TCM1_LCK
ODU1_TCM6_EXC
HARD_BAD
ODU1_TCM1_LTC
ODU1_TCM6_LCK
HARD_ERR
ODU1_TCM1_OCI
ODU1_TCM6_LTC
INTRA_OTU_PS
ODU1_TCM1_SSF
ODU1_TCM6_OCI

79
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
INTRA_OTU_STA_INDI
ODU1_TCM1_TIM
ODU1_TCM6_SSF
IN_PWR_HIGH
ODU1_TCM2_AIS
ODU1_TCM6_TIM
IN_PWR_LOW
ODU1_TCM2_BDI
OPA_FAIL_INDI
J0_MM
ODU1_TCM2_DEG
OPU1_PLM
ODU1_TCM2_EXC
OTU1_AIS
LINK_ERR
ODU1_TCM2_LCK
OTU1_BDI
LOOP_ALM
ODU1_TCM2_LTC
OTU1_DEG
LPT_ACTIVE
ODU1_TCM2_OCI
OTU1_EXC
LSR_COOL_ALM
ODU1_TCM2_SSF
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM2_TIM
OTU1_LOM
LSR_INVALID
ODU1_TCM3_AIS
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_BDI
OTU1_TIM
MS_AIS
ODU1_TCM3_DEG
OUT_PWR_HIGH
MS_CROSSTR
ODU1_TCM3_EXC
OUT_PWR_LOW
MS_RDI
ODU1_TCM3_LCK
PORT_MODULE_OFFLINE
MS_SNCP_PS
ODU1_TCM3_LTC
REM_SD
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
REM_SF
NO_BD_SOFT
ODU1_TCM3_SSF
RS_CROSSTR
NO_ELABEL
ODU1_TCM3_TIM
R_LOC
OCh_FDI
ODU1_TCM4_AIS
R_LOF
OCh_FDI_O
ODU1_TCM4_BDI
R_LOS
OCh_FDI_P
ODU1_TCM4_DEG
SW_SNCP_PS
OCh_LOS_P
ODU1_TCM4_EXC
SW_SNCP_STA_INDI
OCh_OCI
ODU1_TCM4_LCK
TD
OCh_SSF
ODU1_TCM4_LTC
TEMP_OVER
OCh_SSF_O
ODU1_TCM4_OCI
TEM_HA
OCh_SSF_P
ODU1_TCM4_SSF
TEM_LA
ODU1_LOFLOM
ODU1_TCM4_TIM
TF
ODU1_PM_AIS
ODU1_TCM5_AIS
WAVEDATA_MIS
ODU1_PM_BDI
ODU1_TCM5_BDI
WRG_BD_TYPE

80
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.32 LDGS Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_LCK
ODU1_TCM5_LCK
B1_SD
ODU1_PM_OCI
ODU1_TCM5_LTC
B2_EXC
ODU1_PM_SSF
ODU1_TCM5_OCI
B2_SD
ODU1_PM_TIM
ODU1_TCM5_SSF
BD_STATUS
ODU1_TCM1_AIS
ODU1_TCM5_TIM
BEFFEC_EXC
ODU1_TCM1_BDI
ODU1_TCM6_AIS
BUS_ERR
ODU1_TCM1_DEG
ODU1_TCM6_BDI
CLIENT_PORT_PS
ODU1_TCM1_EXC
ODU1_TCM6_DEG
ODU1_TCM1_LCK
ODU1_TCM6_EXC
ODU1_TCM1_LTC
ODU1_TCM6_LCK
COMMUN_FAIL
ODU1_TCM1_OCI
ODU1_TCM6_LTC
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_OCI
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_SSF
IN_PWR_HIGH
ODU1_TCM2_AIS
ODU1_TCM6_TIM
IN_PWR_LOW
ODU1_TCM2_BDI
OPA_FAIL_INDI
J0_MM
ODU1_TCM2_DEG
OPU1_PLM
ODU1_TCM2_EXC
OTU1_AIS
LINK_ERR
ODU1_TCM2_LCK
OTU1_BDI
LOOP_ALM
ODU1_TCM2_LTC
OTU1_DEG
LPT_ACTIVE
ODU1_TCM2_OCI
OTU1_EXC
LSR_COOL_ALM
ODU1_TCM2_SSF
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM2_TIM
OTU1_LOM
LSR_INVALID
ODU1_TCM3_AIS
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_BDI
OTU1_TIM
MS_AIS
ODU1_TCM3_DEG
OUT_PWR_HIGH
MS_CROSSTR
ODU1_TCM3_EXC
OUT_PWR_LOW
MS_RDI
ODU1_TCM3_LCK
PORT_MODULE_OFFLINE

81
OptiX OSN 8800/6800/3800

2 Alarm List
MS_SNCP_PS
ODU1_TCM3_LTC
REM_SD
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
REM_SF
NO_BD_SOFT
ODU1_TCM3_SSF
RS_CROSSTR
NO_ELABEL
ODU1_TCM3_TIM
R_LOC
OCh_FDI
ODU1_TCM4_AIS
R_LOF
OCh_FDI_O
ODU1_TCM4_BDI
R_LOS
OCh_FDI_P
ODU1_TCM4_DEG
SW_SNCP_PS
OCh_LOS_P
ODU1_TCM4_EXC
SW_SNCP_STA_INDI
OCh_OCI
ODU1_TCM4_LCK
TD
OCh_SSF
ODU1_TCM4_LTC
TEMP_OVER
OCh_SSF_O
ODU1_TCM4_OCI
TEM_HA
OCh_SSF_P
ODU1_TCM4_SSF
TEM_LA
ODU1_LOFLOM
ODU1_TCM4_TIM
TF
ODU1_PM_AIS
ODU1_TCM5_AIS
WAVEDATA_MIS
ODU1_PM_BDI
ODU1_TCM5_BDI
WRG_BD_TYPE
ODU1_PM_DEG
ODU1_TCM5_DEG
ODU1_PM_EXC
ODU1_TCM5_EXC
2.2.33 LDM Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_SSF
ODU1_TCM5_LTC
B1_SD
ODU1_PM_TIM
ODU1_TCM5_OCI
BD_STATUS
ODU1_TCM1_AIS
ODU1_TCM5_SSF
BEFFEC_EXC
ODU1_TCM1_BDI
ODU1_TCM5_TIM
CLIENT_PORT_PS
ODU1_TCM1_DEG
ODU1_TCM6_AIS
ODU1_TCM1_EXC
ODU1_TCM6_BDI
ODU1_TCM1_LCK
ODU1_TCM6_DEG
COMMUN_FAIL
ODU1_TCM1_LTC
ODU1_TCM6_EXC
ETH_8B10B_ERR
ODU1_TCM1_OCI
ODU1_TCM6_LCK
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_LTC
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_OCI

82
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
INTRA_OTU_PS
ODU1_TCM2_AIS
ODU1_TCM6_SSF
INTRA_OTU_STA_INDI
ODU1_TCM2_BDI
ODU1_TCM6_TIM
IN_PWR_HIGH
ODU1_TCM2_DEG
OPA_FAIL_INDI
IN_PWR_LOW
ODU1_TCM2_EXC
OPU1_PLM
J0_MM
ODU1_TCM2_LCK
OTU1_AIS
ODU1_TCM2_LTC
OTU1_BDI
LINK_ERR
ODU1_TCM2_OCI
OTU1_DEG
LOOP_ALM
ODU1_TCM2_SSF
OTU1_EXC
LPT_ACTIVE
ODU1_TCM2_TIM
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_LOM
LSR_INVALID
ODU1_TCM3_BDI
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_DEG
OTU1_TIM
L_SYNC
ODU1_TCM3_EXC
OUT_PWR_HIGH
MS_AIS
ODU1_TCM3_LCK
OUT_PWR_LOW
NO_BD_SOFT
ODU1_TCM3_LTC
PORT_MODULE_OFFLINE
NO_ELABEL
ODU1_TCM3_OCI
PRBS_LSS
NULL_SEND
ODU1_TCM3_SSF
REM_SD
OCh_FDI
ODU1_TCM3_TIM
REM_SF
OCh_FDI_O
ODU1_TCM4_AIS
RS_CROSSTR
OCh_FDI_P
ODU1_TCM4_BDI
R_LOC
OCh_LOS_P
ODU1_TCM4_DEG
R_LOF
OCh_OCI
ODU1_TCM4_EXC
R_LOS
OCh_SSF
ODU1_TCM4_LCK
SPEED_OVER
OCh_SSF_O
ODU1_TCM4_LTC
TD
OCh_SSF_P
ODU1_TCM4_OCI
TEMP_OVER
ODU1_LOFLOM
ODU1_TCM4_SSF
TEM_HA
ODU1_PM_AIS
ODU1_TCM4_TIM
TEM_LA
ODU1_PM_BDI
ODU1_TCM5_AIS
TF
ODU1_PM_DEG
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU1_PM_EXC
ODU1_TCM5_DEG
WAVEDATA_MIS

83
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_LCK
ODU1_TCM5_EXC
ODU1_PM_OCI
ODU1_TCM5_LCK
WRG_BD_TYPE
2.2.34 LDMD Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_OCI
ODU1_TCM5_LCK
B1_SD
ODU1_PM_SSF
ODU1_TCM5_LTC
BD_STATUS
ODU1_PM_TIM
ODU1_TCM5_OCI
BEFFEC_EXC
ODU1_TCM1_AIS
ODU1_TCM5_SSF
CLIENT_PORT_PS
ODU1_TCM1_BDI
ODU1_TCM5_TIM
ODU1_TCM1_DEG
ODU1_TCM6_AIS
ODU1_TCM1_EXC
ODU1_TCM6_BDI
COMMUN_FAIL
ODU1_TCM1_LCK
ODU1_TCM6_DEG
ETH_8B10B_ERR
ODU1_TCM1_LTC
ODU1_TCM6_EXC
HARD_BAD
ODU1_TCM1_OCI
ODU1_TCM6_LCK
HARD_ERR
ODU1_TCM1_SSF
ODU1_TCM6_LTC
INTRA_OTU_PS
ODU1_TCM1_TIM
ODU1_TCM6_OCI
INTRA_OTU_STA_INDI
ODU1_TCM2_AIS
ODU1_TCM6_SSF
IN_PWR_HIGH
ODU1_TCM2_BDI
ODU1_TCM6_TIM
IN_PWR_LOW
ODU1_TCM2_DEG
OPU1_PLM
J0_MM
ODU1_TCM2_EXC
OTU1_AIS
ODU1_TCM2_LCK
OTU1_BDI
LINK_ERR
ODU1_TCM2_LTC
OTU1_DEG
LOOP_ALM
ODU1_TCM2_OCI
OTU1_EXC
LPT_ACTIVE
ODU1_TCM2_SSF
OTU1_LOF
LSR_COOL_ALM
ODU1_TCM2_TIM
OTU1_LOM
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_SSF
LSR_INVALID
ODU1_TCM3_BDI
OTU1_TIM
LSR_WILL_DIE
ODU1_TCM3_DEG
OUT_PWR_HIGH
L_SYNC
ODU1_TCM3_EXC
OUT_PWR_LOW

84
OptiX OSN 8800/6800/3800

2 Alarm List
MS_AIS
ODU1_TCM3_LCK
PORT_MODULE_OFFLINE
NO_BD_SOFT
ODU1_TCM3_LTC
PRBS_LSS
NO_ELABEL
ODU1_TCM3_OCI
REM_SD
NULL_SEND
ODU1_TCM3_SSF
REM_SF
OCh_FDI
ODU1_TCM3_TIM
RS_CROSSTR
OCh_FDI_O
ODU1_TCM4_AIS
R_LOC
OCh_FDI_P
ODU1_TCM4_BDI
R_LOF
OCh_LOS_P
ODU1_TCM4_DEG
R_LOS
OCh_OCI
ODU1_TCM4_EXC
SPEED_OVER
OCh_SSF
ODU1_TCM4_LCK
TD
OCh_SSF_O
ODU1_TCM4_LTC
TEMP_OVER
OCh_SSF_P
ODU1_TCM4_OCI
TEM_HA
ODU1_LOFLOM
ODU1_TCM4_SSF
TEM_LA
ODU1_PM_AIS
ODU1_TCM4_TIM
TF
ODU1_PM_BDI
ODU1_TCM5_AIS
TS_CFG_MISMATCH
ODU1_PM_DEG
ODU1_TCM5_BDI
WAVEDATA_MIS
ODU1_PM_EXC
ODU1_TCM5_DEG
WRG_BD_TYPE
ODU1_PM_LCK
ODU1_TCM5_EXC
2.2.35 LDMS Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_SSF
ODU1_TCM5_LCK
B1_SD
ODU1_PM_TIM
ODU1_TCM5_LTC
BD_STATUS
ODU1_TCM1_AIS
ODU1_TCM5_OCI
BEFFEC_EXC
ODU1_TCM1_BDI
ODU1_TCM5_SSF
CLIENT_PORT_PS
ODU1_TCM1_DEG
ODU1_TCM5_TIM
ODU1_TCM1_EXC
ODU1_TCM6_AIS
ODU1_TCM1_LCK
ODU1_TCM6_BDI
COMMUN_FAIL
ODU1_TCM1_LTC
ODU1_TCM6_DEG
ETH_8B10B_ERR
ODU1_TCM1_OCI
ODU1_TCM6_EXC

85
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_LCK
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_LTC
IN_PWR_HIGH
ODU1_TCM2_AIS
ODU1_TCM6_OCI
IN_PWR_LOW
ODU1_TCM2_BDI
ODU1_TCM6_SSF
J0_MM
ODU1_TCM2_DEG
ODU1_TCM6_TIM
ODU1_TCM2_EXC
OPU1_PLM
LINK_ERR
ODU1_TCM2_LCK
OTU1_AIS
LOOP_ALM
ODU1_TCM2_LTC
OTU1_BDI
LPT_ACTIVE
ODU1_TCM2_OCI
OTU1_DEG
LSR_COOL_ALM
ODU1_TCM2_SSF
OTU1_EXC
LSR_FORCE_OPEN
ODU1_TCM2_TIM
OTU1_LOF
LSR_INVALID
ODU1_TCM3_AIS
OTU1_LOM
LSR_WILL_DIE
ODU1_TCM3_BDI
OTU1_SSF
L_SYNC
ODU1_TCM3_DEG
OTU1_TIM
MS_AIS
ODU1_TCM3_EXC
OUT_PWR_HIGH
NO_BD_SOFT
ODU1_TCM3_LCK
OUT_PWR_LOW
NO_ELABEL
ODU1_TCM3_LTC
PORT_MODULE_OFFLINE
NULL_SEND
ODU1_TCM3_OCI
PRBS_LSS
OCh_FDI
ODU1_TCM3_SSF
REM_SD
OCh_FDI_O
ODU1_TCM3_TIM
REM_SF
OCh_FDI_P
ODU1_TCM4_AIS
RS_CROSSTR
OCh_LOS_P
ODU1_TCM4_BDI
R_LOC
OCh_OCI
ODU1_TCM4_DEG
R_LOF
OCh_SSF
ODU1_TCM4_EXC
R_LOS
OCh_SSF_O
ODU1_TCM4_LCK
SPEED_OVER
OCh_SSF_P
ODU1_TCM4_LTC
TD
ODU1_LOFLOM
ODU1_TCM4_OCI
TEMP_OVER
ODU1_PM_AIS
ODU1_TCM4_SSF
TEM_HA
ODU1_PM_BDI
ODU1_TCM4_TIM
TEM_LA
ODU1_PM_DEG
ODU1_TCM5_AIS
TF

86
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_EXC
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU1_PM_LCK
ODU1_TCM5_DEG
WAVEDATA_MIS
ODU1_PM_OCI
ODU1_TCM5_EXC
WRG_BD_TYPE
B1_EXC
ODU2_PM_TIM
ODU2_TCM5_OCI
B1_SD
ODU2_TCM1_AIS
ODU2_TCM5_SSF
BD_STATUS
ODU2_TCM1_BDI
ODU2_TCM5_TIM
BEFFEC_EXC
ODU2_TCM1_DEG
ODU2_TCM6_AIS
CLIENT_PORT_PS
ODU2_TCM1_LCK
ODU2_TCM6_BDI
ODU2_TCM1_LTC
ODU2_TCM6_DEG
ODU2_TCM1_OCI
ODU2_TCM6_LCK
COMMUN_FAIL
ODU2_TCM1_SSF
ODU2_TCM6_LTC
HARD_BAD
ODU2_TCM1_TIM
ODU2_TCM6_OCI
HARD_ERR
ODU2_TCM2_AIS
ODU2_TCM6_SSF
IN_PWR_HIGH
ODU2_TCM2_BDI
ODU2_TCM6_TIM
IN_PWR_LOW
ODU2_TCM2_DEG
OPA_FAIL_INDI
J0_MM
ODU2_TCM2_LCK
OPU2_PLM
ODU2_TCM2_LTC
OTU2_AIS
LOCAL_FAULT
ODU2_TCM2_OCI
OTU2_BDI
LOOP_ALM
ODU2_TCM2_SSF
OTU2_DEG
LPT_ACTIVE
ODU2_TCM2_TIM
OTU2_LOF
LSR_COOL_ALM
ODU2_TCM3_AIS
OTU2_LOM
LSR_FORCE_OPEN
ODU2_TCM3_BDI
OTU2_SSF
LSR_INVALID
ODU2_TCM3_DEG
OTU2_TIM
LSR_WILL_DIE
ODU2_TCM3_LCK
OUT_PWR_HIGH
NO_BD_SOFT
ODU2_TCM3_LTC
OUT_PWR_LOW
NO_ELABEL
ODU2_TCM3_OCI
PORT_MODULE_OFFLINE
NULL_SEND
ODU2_TCM3_SSF
PRBS_LSS
2.2.36 LDX Board Alarm List
Issue 02 (2011-10-31)

87
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI
ODU2_TCM3_TIM
REMOTE_FAULT
OCh_FDI_O
ODU2_TCM4_AIS
REM_SD
OCh_FDI_P
ODU2_TCM4_BDI
REM_SF
OCh_LOS_P
ODU2_TCM4_DEG
RS_CROSSTR
OCh_OCI
ODU2_TCM4_LCK
R_LOC
OCh_SSF
ODU2_TCM4_LTC
R_LOF
OCh_SSF_O
ODU2_TCM4_OCI
R_LOS
OCh_SSF_P
ODU2_TCM4_SSF
TD
ODU2_PM_AIS
ODU2_TCM4_TIM
TEMP_OVER
ODU2_PM_BDI
ODU2_TCM5_AIS
TEM_HA
ODU2_PM_DEG
ODU2_TCM5_BDI
TEM_LA
ODU2_PM_LCK
ODU2_TCM5_DEG
TF
ODU2_PM_OCI
ODU2_TCM5_LCK
WAVEDATA_MIS
ODU2_PM_SSF
ODU2_TCM5_LTC
WRG_BD_TYPE
B1_EXC
NO_BD_SOFT
ODU2_TCM5_AIS
B1_SD
NO_ELABEL
ODU2_TCM5_BDI
BD_STATUS
NULL_SEND
ODU2_TCM5_DEG
BEFFEC_EXC
ODU2_PM_AIS
ODU2_TCM5_LCK
BUS_ERR
ODU2_PM_BDI
ODU2_TCM5_LTC
CLIENT_PORT_PS
ODU2_PM_DEG
ODU2_TCM5_OCI
ODU2_PM_LCK
ODU2_TCM5_SSF
ODU2_PM_OCI
ODU2_TCM5_TIM
COMMUN_FAIL
ODU2_PM_SSF
ODU2_TCM6_AIS
DBPS_ABNORMAL
ODU2_PM_TIM
ODU2_TCM6_BDI
ODU2_TCM1_AIS
ODU2_TCM6_DEG
ETHOAM_RMT_CRIT_FAU
LT
ODU2_TCM1_BDI
ODU2_TCM6_LCK
ETHOAM_RMT_LOOP
ODU2_TCM1_DEG
ODU2_TCM6_LTC
2.2.37 LEM24 Board Alarm List
Issue 02 (2011-10-31)

88
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ETHOAM_RMT_SD
ODU2_TCM1_LCK
ODU2_TCM6_OCI
ETHOAM_SELF_LOOP
ODU2_TCM1_LTC
ODU2_TCM6_SSF
ETHOAM_VCG_SELF_LOO
P
ODU2_TCM1_OCI
ODU2_TCM6_TIM
ETH_CFM_LOC
ODU2_TCM1_SSF
OPA_FAIL_INDI
ETH_CFM_MACSTATUS
ODU2_TCM1_TIM
OPU2_PLM
ETH_CFM_MISMERGE
ODU2_TCM2_AIS
OTU2_AIS
ETH_CFM_RDI
ODU2_TCM2_BDI
OTU2_BDI
ETH_CFM_UNEXPERI
ODU2_TCM2_DEG
OTU2_DEG
ETH_SERVICE_CONFIG_F
AIL
ODU2_TCM2_LCK
OTU2_LOF
EX_ETHOAM_CC_LOS
ODU2_TCM2_LTC
OTU2_LOM
EX_ETHOAM_MPID_CNFL
CT
ODU2_TCM2_OCI
OTU2_SSF
FLOW_OVER
ODU2_TCM2_SSF
OTU2_TIM
FWD_PKT_LOSS
ODU2_TCM2_TIM
OUT_PWR_HIGH
HARD_BAD
ODU2_TCM3_AIS
OUT_PWR_LOW
HARD_ERR
ODU2_TCM3_BDI
PORT_MODULE_OFFLINE
IN_PWR_HIGH
ODU2_TCM3_DEG
PRBS_LSS
IN_PWR_LOW
ODU2_TCM3_LCK
REM_SD
J0_MM
ODU2_TCM3_LTC
REM_SF
LAG_PORT_FAIL
ODU2_TCM3_OCI
RS_CROSSTR
LAG_VC_PORT_FAIL
ODU2_TCM3_SSF
R_LOF
ODU2_TCM3_TIM
R_LOS
LINK_ERR
ODU2_TCM4_AIS
TD
LOOP_ALM
ODU2_TCM4_BDI
TEMP_OVER
LPT_ACTIVE
ODU2_TCM4_DEG
TEM_HA
LSR_COOL_ALM
ODU2_TCM4_LCK
TEM_LA
LSR_FORCE_OPEN
ODU2_TCM4_LTC
TF
LSR_INVALID
ODU2_TCM4_OCI
VLAN_SNCP_PS
LSR_WILL_DIE
ODU2_TCM4_SSF
WRG_BD_TYPE

89
OptiX OSN 8800/6800/3800

MULTI_RPL_OWNER
2 Alarm List
ODU2_TCM4_TIM
WAVEDATA_MIS
B1_EXC
NO_BD_SOFT
ODU2_TCM5_AIS
B1_SD
NO_ELABEL
ODU2_TCM5_BDI
BD_STATUS
NULL_SEND
ODU2_TCM5_DEG
BEFFEC_EXC
ODU2_PM_AIS
ODU2_TCM5_LCK
BUS_ERR
ODU2_PM_BDI
ODU2_TCM5_LTC
CLIENT_PORT_PS
ODU2_PM_DEG
ODU2_TCM5_OCI
ODU2_PM_LCK
ODU2_TCM5_SSF
ODU2_PM_OCI
ODU2_TCM5_TIM
COMMUN_FAIL
ODU2_PM_SSF
ODU2_TCM6_AIS
DBPS_ABNORMAL
ODU2_PM_TIM
ODU2_TCM6_BDI
ODU2_TCM1_AIS
ODU2_TCM6_DEG
ETHOAM_RMT_CRIT_FAU
LT
ODU2_TCM1_BDI
ODU2_TCM6_LCK
ETHOAM_RMT_LOOP
ODU2_TCM1_DEG
ODU2_TCM6_LTC
ETHOAM_RMT_SD
ODU2_TCM1_LCK
ODU2_TCM6_OCI
ETHOAM_SELF_LOOP
ODU2_TCM1_LTC
ODU2_TCM6_SSF
ETHOAM_VCG_SELF_LOO
P
ODU2_TCM1_OCI
ODU2_TCM6_TIM
ETH_CFM_LOC
ODU2_TCM1_SSF
OPA_FAIL_INDI
ETH_CFM_MACSTATUS
ODU2_TCM1_TIM
OPU2_PLM
ETH_CFM_MISMERGE
ODU2_TCM2_AIS
OTU2_AIS
ETH_CFM_RDI
ODU2_TCM2_BDI
OTU2_BDI
ETH_CFM_UNEXPERI
ODU2_TCM2_DEG
OTU2_DEG
ETH_SERVICE_CONFIG_F
AIL
ODU2_TCM2_LCK
OTU2_LOF
EX_ETHOAM_CC_LOS
ODU2_TCM2_LTC
OTU2_LOM
EX_ETHOAM_MPID_CNFL
CT
ODU2_TCM2_OCI
OTU2_SSF
FLOW_OVER
ODU2_TCM2_SSF
OTU2_TIM
2.2.38 LEX4 Board Alarm List
Issue 02 (2011-10-31)

90
OptiX OSN 8800/6800/3800

2 Alarm List
FWD_PKT_LOSS
ODU2_TCM2_TIM
OUT_PWR_HIGH
HARD_BAD
ODU2_TCM3_AIS
OUT_PWR_LOW
HARD_ERR
ODU2_TCM3_BDI
PORT_MODULE_OFFLINE
IN_PWR_HIGH
ODU2_TCM3_DEG
PRBS_LSS
IN_PWR_LOW
ODU2_TCM3_LCK
REM_SD
J0_MM
ODU2_TCM3_LTC
REM_SF
LAG_PORT_FAIL
ODU2_TCM3_OCI
RS_CROSSTR
LAG_VC_PORT_FAIL
ODU2_TCM3_SSF
R_LOF
ODU2_TCM3_TIM
R_LOS
LINK_ERR
ODU2_TCM4_AIS
TD
LOOP_ALM
ODU2_TCM4_BDI
TEMP_OVER
LPT_ACTIVE
ODU2_TCM4_DEG
TEM_HA
LSR_COOL_ALM
ODU2_TCM4_LCK
TEM_LA
LSR_FORCE_OPEN
ODU2_TCM4_LTC
TF
LSR_INVALID
ODU2_TCM4_OCI
VLAN_SNCP_PS
LSR_WILL_DIE
ODU2_TCM4_SSF
WRG_BD_TYPE
MULTI_RPL_OWNER
ODU2_TCM4_TIM
WAVEDATA_MIS
2.2.39 LOA Board Alarm List
Issue 02 (2011-10-31)
ALS_ACTIVE
ODU0_PM_TIM
ODUFLEX_PM_TIM
B1_EXC
ODU1_LOFLOM
OPA_FAIL_INDI
B1_SD
ODU1_PM_AIS
OPU0_PLM
BD_STATUS
ODU1_PM_BDI
OPU1_MSIM
BEFFEC_EXC
ODU1_PM_DEG
OPU1_PLM
CLIENT_PORT_PS
ODU1_PM_LCK
OPU2_MSIM
CLIENT_PORT_STA_I
NDI
ODU1_PM_OCI
OPU2_PLM
ODU1_PM_SSF
OTU1_AIS
COMMUN_FAIL
ODU1_PM_TIM
OTU1_BDI

91
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
HARD_BAD
ODU1_TCMn_AIS
OTU1_DEG
HARD_ERR
ODU1_TCMn_BDI
OTU1_LOF
IN_PWR_HIGH
ODU1_TCMn_DEG
OTU1_LOM
IN_PWR_LOW
ODU1_TCMn_LCK
OTU1_SSF
J0_MM
ODU1_TCMn_LTC
OTU1_TIM
LASER_MODULE_MIS
MATCH
ODU1_TCMn_OCI
OTU2_AIS
LINK_ERR
ODU1_TCMn_SSF
OTU2_BDI
LOOP_ALM
ODU1_TCMn_TIM
OTU2_DEG
LPT_ACTIVE
ODU2_PM_AIS
OTU2_LOF
LSR_COOL_ALM
ODU2_PM_BDI
OTU2_LOM
LSR_INVALID
ODU2_PM_DEG
OTU2_SSF
LSR_WILL_DIE
ODU2_PM_LCK
OTU2_TIM
L_SYNC
ODU2_PM_OCI
OUT_PWR_HIGH
NO_BD_SOFT
ODU2_PM_SSF
OUT_PWR_LOW
NO_ELABEL
ODU2_PM_TIM
PORT_MODULE_OFFLINE
NULL_SEND
ODU2_TCMn_AIS
PRBS_LSS
OCh_FDI
ODU2_TCMn_BDI
REM_SD
OCh_FDI_O
ODU2_TCMn_DEG
REM_SF
OCh_FDI_P
ODU2_TCMn_LCK
RS_CROSSTR
OCh_LOS_P
ODU2_TCMn_LTC
R_LOC
OCh_OCI
ODU2_TCMn_OCI
R_LOF
OCh_SSF
ODU2_TCMn_SSF
R_LOS
OCh_SSF_O
ODU2_TCMn_TIM
TD
OCh_SSF_P
ODUFLEX_LOFLOM
TEMP_OVER
ODU0_LOFLOM
ODUFLEX_PLM
TEM_HA
ODU0_PM_AIS
ODUFLEX_PM_AIS
TEM_LA
ODU0_PM_BDI
ODUFLEX_PM_BDI
TF
ODU0_PM_DEG
ODUFLEX_PM_DEG
TS_CFG_MISMATCH
ODU0_PM_LCK
ODUFLEX_PM_LCK
WAVEDATA_MIS
ODU0_PM_OCI
ODUFLEX_PM_OCI
WRG_BD_TYPE

92
OptiX OSN 8800/6800/3800

ODU0_PM_SSF
2 Alarm List
ODUFLEX_PM_SSF
2.2.40 LOG Board Alarm List

TN12LOG
Issue 02 (2011-10-31)
BD_STATUS
ODU2_PM_SSF
ODU2_TCM5_LTC
BEFFEC_EXC
ODU2_PM_TIM
ODU2_TCM5_OCI
BUS_ERR
ODU2_TCM1_AIS
ODU2_TCM5_SSF
CLIENT_PORT_PS
ODU2_TCM1_BDI
ODU2_TCM5_TIM
ODU2_TCM1_DEG
ODU2_TCM6_AIS
ODU2_TCM1_LCK
ODU2_TCM6_BDI
COMMUN_FAIL
ODU2_TCM1_LTC
ODU2_TCM6_DEG
HARD_BAD
ODU2_TCM1_OCI
ODU2_TCM6_LCK
HARD_ERR
ODU2_TCM1_SSF
ODU2_TCM6_LTC
IN_PWR_HIGH
ODU2_TCM1_TIM
ODU2_TCM6_OCI
IN_PWR_LOW
ODU2_TCM2_AIS
ODU2_TCM6_SSF
ODU2_TCM2_BDI
ODU2_TCM6_TIM
LINK_ERR
ODU2_TCM2_DEG
OPA_FAIL_INDI
LOOP_ALM
ODU2_TCM2_LCK
OPU2_PLM
LPT_ACTIVE
ODU2_TCM2_LTC
OTU2_AIS
LSR_COOL_ALM
ODU2_TCM2_OCI
OTU2_BDI
LSR_FORCE_OPEN
ODU2_TCM2_SSF
OTU2_DEG
LSR_INVALID
ODU2_TCM2_TIM
OTU2_LOF
LSR_WILL_DIE
ODU2_TCM3_AIS
OTU2_LOM
L_SYNC
ODU2_TCM3_BDI
OTU2_SSF
MS_SNCP_PS
ODU2_TCM3_DEG
OTU2_TIM
MS_SNCP_STA_INDI
ODU2_TCM3_LCK
OUT_PWR_HIGH
NO_BD_SOFT
ODU2_TCM3_LTC
OUT_PWR_LOW
NO_ELABEL
ODU2_TCM3_OCI
PORT_MODULE_OFFLINE
NULL_SEND
ODU2_TCM3_SSF
PRBS_LSS

93
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI
ODU2_TCM3_TIM
REM_SD
OCh_FDI_O
ODU2_TCM4_AIS
REM_SF
OCh_FDI_P
ODU2_TCM4_BDI
R_LOS
OCh_LOS_P
ODU2_TCM4_DEG
SW_SNCP_PS
OCh_OCI
ODU2_TCM4_LCK
SW_SNCP_STA_INDI
OCh_SSF
ODU2_TCM4_LTC
TD
OCh_SSF_O
ODU2_TCM4_OCI
TEMP_OVER
OCh_SSF_P
ODU2_TCM4_SSF
TEM_HA
ODU2_PM_AIS
ODU2_TCM4_TIM
TEM_LA
ODU2_PM_BDI
ODU2_TCM5_AIS
TF
ODU2_PM_DEG
ODU2_TCM5_BDI
WAVEDATA_MIS
ODU2_PM_LCK
ODU2_TCM5_DEG
WRG_BD_TYPE
ODU2_PM_OCI
ODU2_TCM5_LCK
TN11LOG
Issue 02 (2011-10-31)
BD_STATUS
ODU2_PM_OCI
ODU2_TCM5_LCK
BEFFEC_EXC
ODU2_PM_SSF
ODU2_TCM5_LTC
BUS_ERR
ODU2_PM_TIM
ODU2_TCM5_OCI
CLIENT_PORT_PS
ODU2_TCM1_AIS
ODU2_TCM5_SSF
ODU2_TCM1_BDI
ODU2_TCM5_TIM
ODU2_TCM1_DEG
ODU2_TCM6_AIS
COMMUN_FAIL
ODU2_TCM1_LCK
ODU2_TCM6_BDI
HARD_BAD
ODU2_TCM1_LTC
ODU2_TCM6_DEG
HARD_ERR
ODU2_TCM1_OCI
ODU2_TCM6_LCK
IN_PWR_HIGH
ODU2_TCM1_SSF
ODU2_TCM6_LTC
IN_PWR_LOW
ODU2_TCM1_TIM
ODU2_TCM6_OCI
ODU2_TCM2_AIS
ODU2_TCM6_SSF
LINK_ERR
ODU2_TCM2_BDI
ODU2_TCM6_TIM
LOOP_ALM
ODU2_TCM2_DEG
OPA_FAIL_INDI
LPT_ACTIVE
ODU2_TCM2_LCK
OPU2_PLM

94
OptiX OSN 8800/6800/3800

2 Alarm List
LSR_COOL_ALM
ODU2_TCM2_LTC
OTU2_AIS
LSR_FORCE_OPEN
ODU2_TCM2_OCI
OTU2_BDI
LSR_INVALID
ODU2_TCM2_SSF
OTU2_DEG
LSR_WILL_DIE
ODU2_TCM2_TIM
OTU2_LOF
L_SYNC
ODU2_TCM3_AIS
OTU2_LOM
MS_SNCP_PS
ODU2_TCM3_BDI
OTU2_SSF
MS_SNCP_STA_INDI
ODU2_TCM3_DEG
OTU2_TIM
NO_BD_SOFT
ODU2_TCM3_LCK
OUT_PWR_HIGH
NO_ELABEL
ODU2_TCM3_LTC
OUT_PWR_LOW
NULL_SEND
ODU2_TCM3_OCI
PORT_MODULE_OFFLINE
OCh_FDI
ODU2_TCM3_SSF
PRBS_LSS
OCh_FDI_O
ODU2_TCM3_TIM
REM_SD
OCh_FDI_P
ODU2_TCM4_AIS
REM_SF
OCh_LOS_P
ODU2_TCM4_BDI
R_LOS
OCh_OCI
ODU2_TCM4_DEG
SW_SNCP_PS
OCh_SSF
ODU2_TCM4_LCK
SW_SNCP_STA_INDI
OCh_SSF_O
ODU2_TCM4_LTC
TD
OCh_SSF_P
ODU2_TCM4_OCI
TEMP_OVER
ODU2_LOFLOM
ODU2_TCM4_SSF
TEM_HA
ODU2_PM_AIS
ODU2_TCM4_TIM
TEM_LA
ODU2_PM_BDI
ODU2_TCM5_AIS
TF
ODU2_PM_DEG
ODU2_TCM5_BDI
WAVEDATA_MIS
ODU2_PM_LCK
ODU2_TCM5_DEG
WRG_BD_TYPE
BD_STATUS
ODU2_PM_SSF
ODU2_TCM5_LTC
BEFFEC_EXC
ODU2_PM_TIM
ODU2_TCM5_OCI
CLIENT_PORT_PS
ODU2_TCM1_AIS
ODU2_TCM5_SSF
ODU2_TCM1_BDI
ODU2_TCM5_TIM
2.2.41 LOM Board Alarm List
Issue 02 (2011-10-31)

95
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU2_TCM1_DEG
ODU2_TCM6_AIS
COMMUN_FAIL
ODU2_TCM1_LCK
ODU2_TCM6_BDI
FC_8B10BERR_OVER
ODU2_TCM1_LTC
ODU2_TCM6_DEG
FC_LINK_ERR
ODU2_TCM1_OCI
ODU2_TCM6_LCK
FC_SYNC_LOS
ODU2_TCM1_SSF
ODU2_TCM6_LTC
HARD_BAD
ODU2_TCM1_TIM
ODU2_TCM6_OCI
HARD_ERR
ODU2_TCM2_AIS
ODU2_TCM6_SSF
IN_PWR_HIGH
ODU2_TCM2_BDI
ODU2_TCM6_TIM
IN_PWR_LOW
ODU2_TCM2_DEG
OPA_FAIL_INDI
ODU2_TCM2_LCK
OPU2_MSIM
LINK_ERR
ODU2_TCM2_LTC
OPU2_PLM
LOOP_ALM
ODU2_TCM2_OCI
OTU2_AIS
LPT_ACTIVE
ODU2_TCM2_SSF
OTU2_BDI
LSR_COOL_ALM
ODU2_TCM2_TIM
OTU2_DEG
LSR_FORCE_OPEN
ODU2_TCM3_AIS
OTU2_LOF
LSR_INVALID
ODU2_TCM3_BDI
OTU2_LOM
LSR_WILL_DIE
ODU2_TCM3_DEG
OTU2_SSF
L_SYNC
ODU2_TCM3_LCK
OTU2_TIM
NO_BD_SOFT
ODU2_TCM3_LTC
OUT_PWR_HIGH
NO_ELABEL
ODU2_TCM3_OCI
OUT_PWR_LOW
NULL_SEND
ODU2_TCM3_SSF
PORT_MODULE_OFFLINE
OCh_FDI
ODU2_TCM3_TIM
PRBS_LSS
OCh_FDI_O
ODU2_TCM4_AIS
R_LOC
OCh_FDI_P
ODU2_TCM4_BDI
R_LOS
OCh_LOS_P
ODU2_TCM4_DEG
REM_SD
OCh_OCI
ODU2_TCM4_LCK
REM_SF
OCh_SSF
ODU2_TCM4_LTC
TD
OCh_SSF_O
ODU2_TCM4_OCI
TEMP_OVER
OCh_SSF_P
ODU2_TCM4_SSF
TEM_HA
ODU2_PM_AIS
ODU2_TCM4_TIM
TEM_LA

96
OptiX OSN 8800/6800/3800

2 Alarm List
ODU2_PM_BDI
ODU2_TCM5_AIS
TF
ODU2_PM_DEG
ODU2_TCM5_BDI
TS_CFG_MISMATCH
ODU2_PM_LCK
ODU2_TCM5_DEG
WAVEDATA_MIS
ODU2_PM_OCI
ODU2_TCM5_LCK
WRG_BD_TYPE
B1_EXC
ODU5G_PM_OCI
ODU5G_TCM5_LTC
B1_SD
ODU5G_PM_SSF
ODU5G_TCM5_OCI
BD_STATUS
ODU5G_PM_TIM
ODU5G_TCM5_SSF
BEFFEC_EXC
ODU5G_TCM1_AIS
ODU5G_TCM5_TIM
BUS_ERR
ODU5G_TCM1_BDI
ODU5G_TCM6_AIS
CLIENT_PORT_PS
ODU5G_TCM1_DEG
ODU5G_TCM6_BDI
ODU5G_TCM1_EXC
ODU5G_TCM6_DEG
ODU5G_TCM1_LCK
ODU5G_TCM6_EXC
COMMUN_FAIL
ODU5G_TCM1_LTC
ODU5G_TCM6_LCK
HARD_BAD
ODU5G_TCM1_OCI
ODU5G_TCM6_LTC
HARD_ERR
ODU5G_TCM1_SSF
ODU5G_TCM6_OCI
IN_PWR_HIGH
ODU5G_TCM1_TIM
ODU5G_TCM6_SSF
IN_PWR_LOW
ODU5G_TCM2_AIS
ODU5G_TCM6_TIM
J0_MM
ODU5G_TCM2_BDI
OPA_FAIL_INDI
ODU5G_TCM2_DEG
OPU5G_PLM
LINK_ERR
ODU5G_TCM2_EXC
OTU5G_AIS
LOOP_ALM
ODU5G_TCM2_LCK
OTU5G_BDI
LPT_ACTIVE
ODU5G_TCM2_LTC
OTU5G_DEG
LSR_COOL_ALM
ODU5G_TCM2_OCI
OTU5G_EXC
LSR_FORCE_OPEN
ODU5G_TCM2_SSF
OTU5G_LOF
LSR_INVALID
ODU5G_TCM2_TIM
OTU5G_LOM
LSR_WILL_DIE
ODU5G_TCM3_AIS
OTU5G_SSF
L_SYNC
ODU5G_TCM3_BDI
OTU5G_TIM
2.2.42 LQG Board Alarm List
Issue 02 (2011-10-31)

97
OptiX OSN 8800/6800/3800

2 Alarm List
MS_AIS
ODU5G_TCM3_DEG
OUT_PWR_HIGH
MS_RDI
ODU5G_TCM3_EXC
OUT_PWR_LOW
MS_SNCP_PS
ODU5G_TCM3_LCK
PORT_MODULE_OFFLINE
MS_SNCP_STA_INDI
ODU5G_TCM3_LTC
PRBS_LSS
NO_BD_SOFT
ODU5G_TCM3_OCI
REM_SD
NO_ELABEL
ODU5G_TCM3_SSF
REM_SF
NULL_SEND
ODU5G_TCM3_TIM
RS_CROSSTR
OCh_FDI
ODU5G_TCM4_AIS
R_LOC
OCh_FDI_O
ODU5G_TCM4_BDI
R_LOF
OCh_FDI_P
ODU5G_TCM4_DEG
R_LOS
OCh_LOS_P
ODU5G_TCM4_EXC
SW_SNCP_PS
OCh_OCI
ODU5G_TCM4_LCK
SW_SNCP_STA_INDI
OCh_SSF
ODU5G_TCM4_LTC
TD
OCh_SSF_O
ODU5G_TCM4_OCI
TEMP_OVER
OCh_SSF_P
ODU5G_TCM4_SSF
TEM_HA
ODU5G_LOFLOM
ODU5G_TCM4_TIM
TEM_LA
ODU5G_PM_AIS
ODU5G_TCM5_AIS
TF
ODU5G_PM_BDI
ODU5G_TCM5_BDI
WAVEDATA_MIS
ODU5G_PM_DEG
ODU5G_TCM5_DEG
WRG_BD_TYPE
ODU5G_PM_EXC
ODU5G_TCM5_EXC
ODU5G_PM_LCK
ODU5G_TCM5_LCK
2.2.43 LQMD Board Alarm List

TN12LQMD
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_LCK
ODU1_TCM5_LTC
B1_SD
ODU1_PM_OCI
ODU1_TCM5_OCI
BD_STATUS
ODU1_PM_SSF
ODU1_TCM5_SSF
BEFFEC_EXC
ODU1_PM_TIM
ODU1_TCM5_TIM
BUS_ERR
ODU1_TCM1_AIS
ODU1_TCM6_AIS
CLIENT_PORT_PS
ODU1_TCM1_BDI
ODU1_TCM6_BDI

98
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU1_TCM1_DEG
ODU1_TCM6_DEG
ODU1_TCM1_EXC
ODU1_TCM6_EXC
COMMUN_FAIL
ODU1_TCM1_LCK
ODU1_TCM6_LCK
ETH_8B10B_ERR
ODU1_TCM1_LTC
ODU1_TCM6_LTC
HARD_BAD
ODU1_TCM1_OCI
ODU1_TCM6_OCI
HARD_ERR
ODU1_TCM1_SSF
ODU1_TCM6_SSF
INTRA_OTU_PS
ODU1_TCM1_TIM
ODU1_TCM6_TIM
INTRA_OTU_STA_INDI
ODU1_TCM2_AIS
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_TCM2_BDI
OPU1_PLM
IN_PWR_LOW
ODU1_TCM2_DEG
OTU1_AIS
J0_MM
ODU1_TCM2_EXC
OTU1_BDI
ODU1_TCM2_LCK
OTU1_DEG
LINK_ERR
ODU1_TCM2_LTC
OTU1_EXC
LOOP_ALM
ODU1_TCM2_OCI
OTU1_LOF
LPT_ACTIVE
ODU1_TCM2_SSF
OTU1_LOM
LSR_COOL_ALM
ODU1_TCM2_TIM
OTU1_SSF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_TIM
LSR_INVALID
ODU1_TCM3_BDI
OUT_PWR_HIGH
LSR_WILL_DIE
ODU1_TCM3_DEG
OUT_PWR_LOW
L_SYNC
ODU1_TCM3_EXC
PORT_MODULE_OFFLINE
MS_AIS
ODU1_TCM3_LCK
PRBS_LSS
MS_SNCP_PS
ODU1_TCM3_LTC
REM_SD
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
REM_SF
NO_BD_SOFT
ODU1_TCM3_SSF
RS_CROSSTR
NO_ELABEL
ODU1_TCM3_TIM
R_LOC
NULL_SEND
ODU1_TCM4_AIS
R_LOF
OCh_FDI
ODU1_TCM4_BDI
R_LOS
OCh_FDI_O
ODU1_TCM4_DEG
SPEED_OVER
OCh_FDI_P
ODU1_TCM4_EXC
SW_SNCP_PS
OCh_LOS_P
ODU1_TCM4_LCK
SW_SNCP_STA_INDI

99
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_OCI
ODU1_TCM4_LTC
TD
OCh_SSF
ODU1_TCM4_OCI
TEMP_OVER
OCh_SSF_O
ODU1_TCM4_SSF
TEM_HA
OCh_SSF_P
ODU1_TCM4_TIM
TEM_LA
ODU1_LOFLOM
ODU1_TCM5_AIS
TF
ODU1_PM_AIS
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU1_PM_BDI
ODU1_TCM5_DEG
WAVEDATA_MIS
ODU1_PM_DEG
ODU1_TCM5_EXC
WRG_BD_TYPE
ODU1_PM_EXC
ODU1_TCM5_LCK
TN11LQMD
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_LCK
ODU1_TCM5_LTC
B1_SD
ODU1_PM_OCI
ODU1_TCM5_OCI
BD_STATUS
ODU1_PM_SSF
ODU1_TCM5_SSF
BEFFEC_EXC
ODU1_PM_TIM
ODU1_TCM5_TIM
BUS_ERR
ODU1_TCM1_AIS
ODU1_TCM6_AIS
CLIENT_PORT_PS
ODU1_TCM1_BDI
ODU1_TCM6_BDI
ODU1_TCM1_DEG
ODU1_TCM6_DEG
ODU1_TCM1_EXC
ODU1_TCM6_EXC
COMMUN_FAIL
ODU1_TCM1_LCK
ODU1_TCM6_LCK
ETH_8B10B_ERR
ODU1_TCM1_LTC
ODU1_TCM6_LTC
HARD_BAD
ODU1_TCM1_OCI
ODU1_TCM6_OCI
HARD_ERR
ODU1_TCM1_SSF
ODU1_TCM6_SSF
INTRA_OTU_PS
ODU1_TCM1_TIM
ODU1_TCM6_TIM
INTRA_OTU_STA_INDI
ODU1_TCM2_AIS
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_TCM2_BDI
OPU1_PLM
IN_PWR_LOW
ODU1_TCM2_DEG
OTU1_AIS
J0_MM
ODU1_TCM2_EXC
OTU1_BDI
ODU1_TCM2_LCK
OTU1_DEG
LINK_ERR
ODU1_TCM2_LTC
OTU1_EXC

100
OptiX OSN 8800/6800/3800

2 Alarm List
LOOP_ALM
ODU1_TCM2_OCI
OTU1_LOF
LPT_ACTIVE
ODU1_TCM2_SSF
OTU1_LOM
LSR_COOL_ALM
ODU1_TCM2_TIM
OTU1_SSF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_TIM
LSR_INVALID
ODU1_TCM3_BDI
OUT_PWR_HIGH
LSR_WILL_DIE
ODU1_TCM3_DEG
OUT_PWR_LOW
L_SYNC
ODU1_TCM3_EXC
PORT_MODULE_OFFLINE
MS_AIS
ODU1_TCM3_LCK
PRBS_LSS
MS_SNCP_PS
ODU1_TCM3_LTC
REM_SD
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
REM_SF
NO_BD_SOFT
ODU1_TCM3_SSF
RS_CROSSTR
NO_ELABEL
ODU1_TCM3_TIM
R_LOC
NULL_SEND
ODU1_TCM4_AIS
R_LOF
OCh_FDI
ODU1_TCM4_BDI
R_LOS
OCh_FDI_O
ODU1_TCM4_DEG
SW_SNCP_PS
OCh_FDI_P
ODU1_TCM4_EXC
SW_SNCP_STA_INDI
OCh_LOS_P
ODU1_TCM4_LCK
TD
OCh_OCI
ODU1_TCM4_LTC
TEMP_OVER
OCh_SSF
ODU1_TCM4_OCI
TEM_HA
OCh_SSF_O
ODU1_TCM4_SSF
TEM_LA
OCh_SSF_P
ODU1_TCM4_TIM
TF
ODU1_LOFLOM
ODU1_TCM5_AIS
TS_CFG_MISMATCH
ODU1_PM_AIS
ODU1_TCM5_BDI
WAVEDATA_MIS
ODU1_PM_BDI
ODU1_TCM5_DEG
WRG_BD_TYPE
ODU1_PM_DEG
ODU1_TCM5_EXC
ODU1_PM_EXC
ODU1_TCM5_LCK
2.2.44 LQMS Board Alarm List

TN12LQMS
B1_EXC
Issue 02 (2011-10-31)
ODU1_PM_SSF
ODU1_TCM5_SSF
101
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
B1_SD
ODU1_PM_TIM
ODU1_TCM5_TIM
BD_STATUS
ODU1_TCM1_AIS
ODU1_TCM6_AIS
BEFFEC_EXC
ODU1_TCM1_BDI
ODU1_TCM6_BDI
BUS_ERR
ODU1_TCM1_DEG
ODU1_TCM6_DEG
CLIENT_PORT_PS
ODU1_TCM1_EXC
ODU1_TCM6_EXC
ODU1_TCM1_LCK
ODU1_TCM6_LCK
ODU1_TCM1_LTC
ODU1_TCM6_LTC
COMMUN_FAIL
ODU1_TCM1_OCI
ODU1_TCM6_OCI
ETH_8B10B_ERR
ODU1_TCM1_SSF
ODU1_TCM6_SSF
HARD_BAD
ODU1_TCM1_TIM
ODU1_TCM6_TIM
HARD_ERR
ODU1_TCM2_AIS
ODU_SNCP_PS
IN_PWR_HIGH
ODU1_TCM2_BDI
ODU_SNCP_STA_INDI
IN_PWR_LOW
ODU1_TCM2_DEG
OPA_FAIL_INDI
J0_MM
ODU1_TCM2_EXC
OPU1_PLM
ODU1_TCM2_LCK
OTU1_AIS
LINK_ERR
ODU1_TCM2_LTC
OTU1_BDI
LOOP_ALM
ODU1_TCM2_OCI
OTU1_DEG
LPT_ACTIVE
ODU1_TCM2_SSF
OTU1_EXC
LSR_COOL_ALM
ODU1_TCM2_TIM
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_LOM
LSR_INVALID
ODU1_TCM3_BDI
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_DEG
OTU1_TIM
L_SYNC
ODU1_TCM3_EXC
OUT_PWR_HIGH
MS_AIS
ODU1_TCM3_LCK
OUT_PWR_LOW
MS_SNCP_PS
ODU1_TCM3_LTC
PORT_MODULE_OFFLINE
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
PRBS_LSS
NO_BD_SOFT
ODU1_TCM3_SSF
REM_SD
NO_ELABEL
ODU1_TCM3_TIM
REM_SF
NULL_SEND
ODU1_TCM4_AIS
RS_CROSSTR
OCh_FDI
ODU1_TCM4_BDI
R_LOC

102
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI_O
ODU1_TCM4_DEG
R_LOF
OCh_FDI_P
ODU1_TCM4_EXC
R_LOS
OCh_LOS_P
ODU1_TCM4_LCK
SPEED_OVER
OCh_OCI
ODU1_TCM4_LTC
SW_SNCP_PS
OCh_SSF
ODU1_TCM4_OCI
SW_SNCP_STA_INDI
OCh_SSF_O
ODU1_TCM4_SSF
TD
OCh_SSF_P
ODU1_TCM4_TIM
TEMP_OVER
ODU1_LOFLOM
ODU1_TCM5_AIS
TEM_HA
ODU1_PM_AIS
ODU1_TCM5_BDI
TEM_LA
ODU1_PM_BDI
ODU1_TCM5_DEG
TF
ODU1_PM_DEG
ODU1_TCM5_EXC
TS_CFG_MISMATCH
ODU1_PM_EXC
ODU1_TCM5_LCK
WAVEDATA_MIS
ODU1_PM_LCK
ODU1_TCM5_LTC
WRG_BD_TYPE
ODU1_PM_OCI
ODU1_TCM5_OCI
TN11LQMS
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_OCI
ODU1_TCM5_LTC
B1_SD
ODU1_PM_SSF
ODU1_TCM5_OCI
BD_STATUS
ODU1_PM_TIM
ODU1_TCM5_SSF
BEFFEC_EXC
ODU1_TCM1_AIS
ODU1_TCM5_TIM
BUS_ERR
ODU1_TCM1_BDI
ODU1_TCM6_AIS
CLIENT_PORT_PS
ODU1_TCM1_DEG
ODU1_TCM6_BDI
ODU1_TCM1_EXC
ODU1_TCM6_DEG
ODU1_TCM1_LCK
ODU1_TCM6_EXC
COMMUN_FAIL
ODU1_TCM1_LTC
ODU1_TCM6_LCK
ETH_8B10B_ERR
ODU1_TCM1_OCI
ODU1_TCM6_LTC
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_OCI
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_SSF
IN_PWR_HIGH
ODU1_TCM2_AIS
ODU1_TCM6_TIM
IN_PWR_LOW
ODU1_TCM2_BDI
OPA_FAIL_INDI

103
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
J0_MM
ODU1_TCM2_DEG
OPU1_PLM
ODU1_TCM2_EXC
OTU1_AIS
LINK_ERR
ODU1_TCM2_LCK
OTU1_BDI
LOOP_ALM
ODU1_TCM2_LTC
OTU1_DEG
LPT_ACTIVE
ODU1_TCM2_OCI
OTU1_EXC
LSR_COOL_ALM
ODU1_TCM2_SSF
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM2_TIM
OTU1_LOM
LSR_INVALID
ODU1_TCM3_AIS
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_BDI
OTU1_TIM
L_SYNC
ODU1_TCM3_DEG
OUT_PWR_HIGH
MS_AIS
ODU1_TCM3_EXC
OUT_PWR_LOW
MS_SNCP_PS
ODU1_TCM3_LCK
PORT_MODULE_OFFLINE
MS_SNCP_STA_INDI
ODU1_TCM3_LTC
PRBS_LSS
NO_BD_SOFT
ODU1_TCM3_OCI
REM_SD
NO_ELABEL
ODU1_TCM3_SSF
REM_SF
NULL_SEND
ODU1_TCM3_TIM
RS_CROSSTR
OCh_FDI
ODU1_TCM4_AIS
R_LOC
OCh_FDI_O
ODU1_TCM4_BDI
R_LOF
OCh_FDI_P
ODU1_TCM4_DEG
R_LOS
OCh_LOS_P
ODU1_TCM4_EXC
SW_SNCP_PS
OCh_OCI
ODU1_TCM4_LCK
SW_SNCP_STA_INDI
OCh_SSF
ODU1_TCM4_LTC
TD
OCh_SSF_O
ODU1_TCM4_OCI
TEMP_OVER
OCh_SSF_P
ODU1_TCM4_SSF
TEM_HA
ODU1_LOFLOM
ODU1_TCM4_TIM
TEM_LA
ODU1_PM_AIS
ODU1_TCM5_AIS
TF
ODU1_PM_BDI
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU1_PM_DEG
ODU1_TCM5_DEG
WAVEDATA_MIS
ODU1_PM_EXC
ODU1_TCM5_EXC
WRG_BD_TYPE
ODU1_PM_LCK
ODU1_TCM5_LCK

104
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.45 LQM Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_OCI
ODU1_TCM5_OCI
B1_SD
ODU1_PM_SSF
ODU1_TCM5_SSF
BD_STATUS
ODU1_PM_TIM
ODU1_TCM5_TIM
BEFFEC_EXC
ODU1_TCM1_AIS
ODU1_TCM6_AIS
BUS_ERR
ODU1_TCM1_BDI
ODU1_TCM6_BDI
CLIENT_PORT_PS
ODU1_TCM1_DEG
ODU1_TCM6_DEG
ODU1_TCM1_EXC
ODU1_TCM6_EXC
ODU1_TCM1_LCK
ODU1_TCM6_LCK
COMMUN_FAIL
ODU1_TCM1_LTC
ODU1_TCM6_LTC
ETH_8B10B_ERR
ODU1_TCM1_OCI
ODU1_TCM6_OCI
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_SSF
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_TIM
INTRA_OTU_PS
ODU1_TCM2_AIS
OPA_FAIL_INDI
INTRA_OTU_STA_INDI
ODU1_TCM2_BDI
OPU1_PLM
IN_PWR_HIGH
ODU1_TCM2_DEG
OTU1_AIS
IN_PWR_LOW
ODU1_TCM2_EXC
OTU1_BDI
J0_MM
ODU1_TCM2_LCK
OTU1_DEG
ODU1_TCM2_LTC
OTU1_EXC
LINK_ERR
ODU1_TCM2_OCI
OTU1_LOF
LOOP_ALM
ODU1_TCM2_SSF
OTU1_LOM
LPT_ACTIVE
ODU1_TCM2_TIM
OTU1_SSF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_TIM
LSR_INVALID
ODU1_TCM3_BDI
OUT_PWR_HIGH
LSR_WILL_DIE
ODU1_TCM3_DEG
OUT_PWR_LOW
L_SYNC
ODU1_TCM3_EXC
PORT_MODULE_OFFLINE
MS_AIS
ODU1_TCM3_LCK
PRBS_LSS
MS_SNCP_PS
ODU1_TCM3_LTC
REM_SD

105
OptiX OSN 8800/6800/3800

2 Alarm List
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
REM_SF
NO_BD_SOFT
ODU1_TCM3_SSF
RS_CROSSTR
NO_ELABEL
ODU1_TCM3_TIM
R_LOC
NULL_SEND
ODU1_TCM4_AIS
R_LOF
OCh_FDI
ODU1_TCM4_BDI
R_LOS
OCh_FDI_O
ODU1_TCM4_DEG
SPEED_OVER
OCh_FDI_P
ODU1_TCM4_EXC
SW_SNCP_PS
OCh_LOS_P
ODU1_TCM4_LCK
SW_SNCP_STA_INDI
OCh_OCI
ODU1_TCM4_LTC
TD
OCh_SSF
ODU1_TCM4_OCI
TEMP_OVER
OCh_SSF_O
ODU1_TCM4_SSF
TEM_HA
OCh_SSF_P
ODU1_TCM4_TIM
TEM_LA
ODU1_LOFLOM
ODU1_TCM5_AIS
TF
ODU1_PM_AIS
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU1_PM_BDI
ODU1_TCM5_DEG
WAVEDATA_MIS
ODU1_PM_DEG
ODU1_TCM5_EXC
WRG_BD_TYPE
ODU1_PM_EXC
ODU1_TCM5_LCK
ODU1_PM_LCK
ODU1_TCM5_LTC
2.2.46 LSQ Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU3_TCM1_EXC
ODU3_TCM5_OCI
B1_SD
ODU3_TCM1_LCK
ODU3_TCM5_SSF
BD_STATUS
ODU3_TCM1_LTC
ODU3_TCM5_TIM
BEFFEC_EXC
ODU3_TCM1_OCI
ODU3_TCM6_AIS
CLIENT_PORT_PS
ODU3_TCM1_SSF
ODU3_TCM6_BDI
ODU3_TCM1_TIM
ODU3_TCM6_DEG
ODU3_TCM2_AIS
ODU3_TCM6_EXC
COMMUN_FAIL
ODU3_TCM2_BDI
ODU3_TCM6_LCK
DCM_INSUFF
ODU3_TCM2_DEG
ODU3_TCM6_LTC

106
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
HARD_BAD
ODU3_TCM2_EXC
ODU3_TCM6_OCI
HARD_ERR
ODU3_TCM2_LCK
ODU3_TCM6_SSF
IN_PWR_HIGH
ODU3_TCM2_LTC
ODU3_TCM6_TIM
IN_PWR_LOW
ODU3_TCM2_OCI
OPA_FAIL_INDI
J0_MM
ODU3_TCM2_SSF
OPU3_MSIM
LOOP_ALM
ODU3_TCM2_TIM
OPU3_PLM
LSR_FORCE_OPEN
ODU3_TCM3_AIS
OTU3_AIS
LSR_WILL_DIE
ODU3_TCM3_BDI
OTU3_BDI
NO_BD_SOFT
ODU3_TCM3_DEG
OTU3_DEG
NO_ELABEL
ODU3_TCM3_EXC
OTU3_EXC
NULL_SEND
ODU3_TCM3_LCK
OTU3_LOF
OCh_FDI
ODU3_TCM3_LTC
OTU3_LOM
OCh_FDI_O
ODU3_TCM3_OCI
OTU3_SSF
OCh_FDI_P
ODU3_TCM3_SSF
OTU3_TIM
OCh_LOS_P
ODU3_TCM3_TIM
OUT_PWR_HIGH
OCh_OCI
ODU3_TCM4_AIS
OUT_PWR_LOW
OCh_SSF
ODU3_TCM4_BDI
PORT_MODULE_OFFLINE
OCh_SSF_O
ODU3_TCM4_DEG
PRBS_LSS
OCh_SSF_P
ODU3_TCM4_EXC
R_LOC
ODU3_PM_AIS
ODU3_TCM4_LCK
R_LOF
ODU3_PM_BDI
ODU3_TCM4_LTC
R_LOS
ODU3_PM_DEG
ODU3_TCM4_OCI
REM_SD
ODU3_PM_EXC
ODU3_TCM4_SSF
REM_SF
ODU3_PM_LCK
ODU3_TCM4_TIM
TD
ODU3_PM_OCI
ODU3_TCM5_AIS
TEMP_OVER
ODU3_PM_SSF
ODU3_TCM5_BDI
TF
ODU3_PM_TIM
ODU3_TCM5_DEG
WAVEDATA_MIS
ODU3_TCM1_AIS
ODU3_TCM5_EXC
WRG_BD_TYPE
ODU3_TCM1_BDI
ODU3_TCM5_LCK
ODU3_TCM1_DEG
ODU3_TCM5_LTC

107
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.47 LSXLR Board Alarm List

TN11LSXLR
Issue 02 (2011-10-31)
BD_STATUS
ODU3_TCM1_OCI
ODU3_TCM5_OCI
BEFFEC_EXC
ODU3_TCM1_SSF
ODU3_TCM5_SSF
COMMUN_FAIL
ODU3_TCM1_TIM
ODU3_TCM5_TIM
DCM_INSUFF
ODU3_TCM2_AIS
ODU3_TCM6_AIS
HARD_BAD
ODU3_TCM2_BDI
ODU3_TCM6_BDI
HARD_ERR
ODU3_TCM2_DEG
ODU3_TCM6_DEG
IN_PWR_HIGH
ODU3_TCM2_LCK
ODU3_TCM6_LCK
IN_PWR_LOW
ODU3_TCM2_LTC
ODU3_TCM6_LTC
LSR_FORCE_OPEN
ODU3_TCM2_OCI
ODU3_TCM6_OCI
LSR_WILL_DIE
ODU3_TCM2_SSF
ODU3_TCM6_SSF
NO_BD_SOFT
ODU3_TCM2_TIM
ODU3_TCM6_TIM
NO_ELABEL
ODU3_TCM3_AIS
OPA_FAIL_INDI
OCh_FDI
ODU3_TCM3_BDI
OTU3_AIS
OCh_FDI_O
ODU3_TCM3_DEG
OTU3_BDI
OCh_FDI_P
ODU3_TCM3_LCK
OTU3_DEG
OCh_LOS_P
ODU3_TCM3_LTC
OTU3_LOF
OCh_OCI
ODU3_TCM3_OCI
OTU3_LOM
OCh_SSF
ODU3_TCM3_SSF
OTU3_SSF
OCh_SSF_O
ODU3_TCM3_TIM
OTU3_TIM
OCh_SSF_P
ODU3_TCM4_AIS
OUT_PWR_HIGH
ODU3_PM_AIS
ODU3_TCM4_BDI
OUT_PWR_LOW
ODU3_PM_BDI
ODU3_TCM4_DEG
PORT_MODULE_OFFLINE
ODU3_PM_DEG
ODU3_TCM4_LCK
R_LOS
ODU3_PM_LCK
ODU3_TCM4_LTC
TD
ODU3_PM_OCI
ODU3_TCM4_OCI
TEMP_OVER
ODU3_PM_SSF
ODU3_TCM4_SSF
TEM_HA
ODU3_PM_TIM
ODU3_TCM4_TIM
TEM_LA
ODU3_TCM1_AIS
ODU3_TCM5_AIS
TF
ODU3_TCM1_BDI
ODU3_TCM5_BDI
WAVEDATA_MIS

108
OptiX OSN 8800/6800/3800

2 Alarm List
ODU3_TCM1_DEG
ODU3_TCM5_DEG
ODU3_TCM1_LCK
ODU3_TCM5_LCK
ODU3_TCM1_LTC
ODU3_TCM5_LTC
WRG_BD_TYPE
TN12LSXLR
Issue 02 (2011-10-31)
BD_STATUS
ODU3_TCM1_LTC
ODU3_TCM5_LTC
BEFFEC_EXC
ODU3_TCM1_OCI
ODU3_TCM5_OCI
BUS_ERR
ODU3_TCM1_SSF
ODU3_TCM5_SSF
COMMUN_FAIL
ODU3_TCM1_TIM
ODU3_TCM5_TIM
DCM_INSUFF
ODU3_TCM2_AIS
ODU3_TCM6_AIS
HARD_BAD
ODU3_TCM2_BDI
ODU3_TCM6_BDI
HARD_ERR
ODU3_TCM2_DEG
ODU3_TCM6_DEG
IN_PWR_HIGH
ODU3_TCM2_LCK
ODU3_TCM6_LCK
IN_PWR_LOW
ODU3_TCM2_LTC
ODU3_TCM6_LTC
LSR_FORCE_OPEN
ODU3_TCM2_OCI
ODU3_TCM6_OCI
LSR_WILL_DIE
ODU3_TCM2_SSF
ODU3_TCM6_SSF
NO_BD_SOFT
ODU3_TCM2_TIM
ODU3_TCM6_TIM
NO_ELABEL
ODU3_TCM3_AIS
OPA_FAIL_INDI
OCh_FDI
ODU3_TCM3_BDI
OPU3_MSIM
OCh_FDI_O
ODU3_TCM3_DEG
OPU3_PLM
OCh_FDI_P
ODU3_TCM3_LCK
OTU3_AIS
OCh_LOS_P
ODU3_TCM3_LTC
OTU3_BDI
OCh_OCI
ODU3_TCM3_OCI
OTU3_DEG
OCh_SSF
ODU3_TCM3_SSF
OTU3_LOF
OCh_SSF_O
ODU3_TCM3_TIM
OTU3_LOM
OCh_SSF_P
ODU3_TCM4_AIS
OTU3_SSF
ODU3_PM_AIS
ODU3_TCM4_BDI
OTU3_TIM
ODU3_PM_BDI
ODU3_TCM4_DEG
OUT_PWR_HIGH
ODU3_PM_DEG
ODU3_TCM4_LCK
OUT_PWR_LOW
ODU3_PM_LCK
ODU3_TCM4_LTC
PORT_MODULE_OFFLINE

109
OptiX OSN 8800/6800/3800

2 Alarm List
ODU3_PM_OCI
ODU3_TCM4_OCI
R_LOS
ODU3_PM_SSF
ODU3_TCM4_SSF
TD
ODU3_PM_TIM
ODU3_TCM4_TIM
TEMP_OVER
ODU3_TCM1_AIS
ODU3_TCM5_AIS
TF
ODU3_TCM1_BDI
ODU3_TCM5_BDI
WAVEDATA_MIS
ODU3_TCM1_DEG
ODU3_TCM5_DEG
WRG_BD_TYPE
ODU3_TCM1_LCK
ODU3_TCM5_LCK
2.2.48 LSXL Board Alarm List

TN11LSXL
Issue 02 (2011-10-31)
B1_EXC
ODU3_TCM1_DEG
ODU3_TCM5_SSF
B1_SD
ODU3_TCM1_LCK
ODU3_TCM5_TIM
BD_STATUS
ODU3_TCM1_LTC
ODU3_TCM6_AIS
BEFFEC_EXC
ODU3_TCM1_OCI
ODU3_TCM6_BDI
CLIENT_PORT_PS
ODU3_TCM1_SSF
ODU3_TCM6_DEG
ODU3_TCM1_TIM
ODU3_TCM6_LCK
ODU3_TCM2_AIS
ODU3_TCM6_LTC
COMMUN_FAIL
ODU3_TCM2_BDI
ODU3_TCM6_OCI
DCM_INSUFF
ODU3_TCM2_DEG
ODU3_TCM6_SSF
HARD_BAD
ODU3_TCM2_LCK
ODU3_TCM6_TIM
HARD_ERR
ODU3_TCM2_LTC
OPA_FAIL_INDI
IN_PWR_HIGH
ODU3_TCM2_OCI
OPU3_PLM
IN_PWR_LOW
ODU3_TCM2_SSF
OTU3_AIS
J0_MM
ODU3_TCM2_TIM
OTU3_BDI
LOOP_ALM
ODU3_TCM3_AIS
OTU3_DEG
LSR_FORCE_OPEN
ODU3_TCM3_BDI
OTU3_LOF
LSR_WILL_DIE
ODU3_TCM3_DEG
OTU3_LOM
NO_BD_SOFT
ODU3_TCM3_LCK
OTU3_SSF
NO_ELABEL
ODU3_TCM3_LTC
OTU3_TIM
OCh_FDI
ODU3_TCM3_OCI
OUT_PWR_HIGH

110
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI_O
ODU3_TCM3_SSF
OUT_PWR_LOW
OCh_FDI_P
ODU3_TCM3_TIM
PORT_MODULE_OFFLINE
OCh_LOS_P
ODU3_TCM4_AIS
REM_SD
OCh_OCI
ODU3_TCM4_BDI
REM_SF
OCh_SSF
ODU3_TCM4_DEG
RS_CROSSTR
OCh_SSF_O
ODU3_TCM4_LCK
R_LOC
OCh_SSF_P
ODU3_TCM4_LTC
R_LOF
ODU3_PM_AIS
ODU3_TCM4_OCI
R_LOS
ODU3_PM_BDI
ODU3_TCM4_SSF
TD
ODU3_PM_DEG
ODU3_TCM4_TIM
TEMP_OVER
ODU3_PM_LCK
ODU3_TCM5_AIS
TEM_HA
ODU3_PM_OCI
ODU3_TCM5_BDI
TEM_LA
ODU3_PM_SSF
ODU3_TCM5_DEG
TF
ODU3_PM_TIM
ODU3_TCM5_LCK
WAVEDATA_MIS
ODU3_TCM1_AIS
ODU3_TCM5_LTC
WRG_BD_TYPE
ODU3_TCM1_BDI
ODU3_TCM5_OCI
TN12LSXL
Issue 02 (2011-10-31)
B1_EXC
ODU3_TCM1_AIS
ODU3_TCM5_LTC
B1_SD
ODU3_TCM1_BDI
ODU3_TCM5_OCI
BD_STATUS
ODU3_TCM1_DEG
ODU3_TCM5_SSF
BEFFEC_EXC
ODU3_TCM1_LCK
ODU3_TCM5_TIM
BUS_ERR
ODU3_TCM1_LTC
ODU3_TCM6_AIS
CLIENT_PORT_PS
ODU3_TCM1_OCI
ODU3_TCM6_BDI
ODU3_TCM1_SSF
ODU3_TCM6_DEG
ODU3_TCM1_TIM
ODU3_TCM6_LCK
COMMUN_FAIL
ODU3_TCM2_AIS
ODU3_TCM6_LTC
DCM_INSUFF
ODU3_TCM2_BDI
ODU3_TCM6_OCI
HARD_BAD
ODU3_TCM2_DEG
ODU3_TCM6_SSF

111
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_ERR
ODU3_TCM2_LCK
ODU3_TCM6_TIM
IN_PWR_HIGH
ODU3_TCM2_LTC
OPA_FAIL_INDI
IN_PWR_LOW
ODU3_TCM2_OCI
OPU3_MSIM
J0_MM
ODU3_TCM2_SSF
OPU3_PLM
LOOP_ALM
ODU3_TCM2_TIM
OTU3_AIS
LSR_FORCE_OPEN
ODU3_TCM3_AIS
OTU3_BDI
LSR_WILL_DIE
ODU3_TCM3_BDI
OTU3_DEG
NO_BD_SOFT
ODU3_TCM3_DEG
OTU3_LOF
NO_ELABEL
ODU3_TCM3_LCK
OTU3_LOM
NULL_SEND
ODU3_TCM3_LTC
OTU3_SSF
OCh_FDI
ODU3_TCM3_OCI
OTU3_TIM
OCh_FDI_O
ODU3_TCM3_SSF
OUT_PWR_HIGH
OCh_FDI_P
ODU3_TCM3_TIM
OUT_PWR_LOW
OCh_LOS_P
ODU3_TCM4_AIS
PORT_MODULE_OFFLINE
OCh_OCI
ODU3_TCM4_BDI
PRBS_LSS
OCh_SSF
ODU3_TCM4_DEG
REM_SD
OCh_SSF_O
ODU3_TCM4_LCK
REM_SF
OCh_SSF_P
ODU3_TCM4_LTC
R_LOF
ODU3_PM_AIS
ODU3_TCM4_OCI
R_LOS
ODU3_PM_BDI
ODU3_TCM4_SSF
R_OOF
ODU3_PM_DEG
ODU3_TCM4_TIM
TD
ODU3_PM_LCK
ODU3_TCM5_AIS
TEMP_OVER
ODU3_PM_OCI
ODU3_TCM5_BDI
TF
ODU3_PM_SSF
ODU3_TCM5_DEG
WAVEDATA_MIS
ODU3_PM_TIM
ODU3_TCM5_LCK
WRG_BD_TYPE
NOTE
In the alarms, n indicates the level of TCM and its value ranges from 1 to 6. The TCMn is from TCM1 to
TCM6.
Issue 02 (2011-10-31)

112
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.49 LSXR Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
ODU2_TCM1_OCI
ODU2_TCM5_LTC
BEFFEC_EXC
ODU2_TCM1_SSF
ODU2_TCM5_OCI
COMMUN_FAIL
ODU2_TCM1_TIM
ODU2_TCM5_SSF
HARD_BAD
ODU2_TCM2_AIS
ODU2_TCM5_TIM
HARD_ERR
ODU2_TCM2_BDI
ODU2_TCM6_AIS
IN_PWR_HIGH
ODU2_TCM2_DEG
ODU2_TCM6_BDI
IN_PWR_LOW
ODU2_TCM2_LCK
ODU2_TCM6_DEG
LSR_FORCE_OPEN
ODU2_TCM2_LTC
ODU2_TCM6_LCK
LSR_WILL_DIE
ODU2_TCM2_OCI
ODU2_TCM6_LTC
NO_BD_SOFT
ODU2_TCM2_SSF
ODU2_TCM6_OCI
NO_ELABEL
ODU2_TCM2_TIM
ODU2_TCM6_SSF
OCh_FDI
ODU2_TCM3_AIS
ODU2_TCM6_TIM
OCh_FDI_O
ODU2_TCM3_BDI
OPA_FAIL_INDI
OCh_FDI_P
ODU2_TCM3_DEG
OTU2_AIS
OCh_LOS_P
ODU2_TCM3_LCK
OTU2_BDI
OCh_OCI
ODU2_TCM3_LTC
OTU2_DEG
OCh_SSF
ODU2_TCM3_OCI
OTU2_LOF
OCh_SSF_O
ODU2_TCM3_SSF
OTU2_LOM
OCh_SSF_P
ODU2_TCM3_TIM
OTU2_SSF
ODU2_PM_AIS
ODU2_TCM4_AIS
OTU2_TIM
ODU2_PM_BDI
ODU2_TCM4_BDI
OUT_PWR_HIGH
ODU2_PM_DEG
ODU2_TCM4_DEG
OUT_PWR_LOW
ODU2_PM_LCK
ODU2_TCM4_LCK
PORT_MODULE_OFFLINE
ODU2_PM_OCI
ODU2_TCM4_LTC
R_LOS
ODU2_PM_SSF
ODU2_TCM4_OCI
TD
ODU2_PM_TIM
ODU2_TCM4_SSF
TEMP_OVER
ODU2_TCM1_AIS
ODU2_TCM4_TIM
TEM_HA
ODU2_TCM1_BDI
ODU2_TCM5_AIS
TEM_LA
ODU2_TCM1_DEG
ODU2_TCM5_BDI
TF
ODU2_TCM1_LCK
ODU2_TCM5_DEG
WAVEDATA_MIS

113
OptiX OSN 8800/6800/3800

ODU2_TCM1_LTC
2 Alarm List
ODU2_TCM5_LCK
WRG_BD_TYPE
2.2.50 LSX Board Alarm List

TN11LSX
Issue 02 (2011-10-31)
B1_EXC
ODU2_PM_TIM
ODU2_TCM5_OCI
B1_SD
ODU2_TCM1_AIS
ODU2_TCM5_SSF
BD_STATUS
ODU2_TCM1_BDI
ODU2_TCM5_TIM
BEFFEC_EXC
ODU2_TCM1_DEG
ODU2_TCM6_AIS
CLIENT_PORT_PS
ODU2_TCM1_LCK
ODU2_TCM6_BDI
ODU2_TCM1_LTC
ODU2_TCM6_DEG
ODU2_TCM1_OCI
ODU2_TCM6_LCK
COMMUN_FAIL
ODU2_TCM1_SSF
ODU2_TCM6_LTC
HARD_BAD
ODU2_TCM1_TIM
ODU2_TCM6_OCI
HARD_ERR
ODU2_TCM2_AIS
ODU2_TCM6_SSF
IN_PWR_HIGH
ODU2_TCM2_BDI
ODU2_TCM6_TIM
IN_PWR_LOW
ODU2_TCM2_DEG
OPA_FAIL_INDI
J0_MM
ODU2_TCM2_LCK
OPU2_PLM
ODU2_TCM2_LTC
OTU2_AIS
LOCAL_FAULT
ODU2_TCM2_OCI
OTU2_BDI
LOOP_ALM
ODU2_TCM2_SSF
OTU2_DEG
LPT_ACTIVE
ODU2_TCM2_TIM
OTU2_LOF
LSR_COOL_ALM
ODU2_TCM3_AIS
OTU2_LOM
LSR_FORCE_OPEN
ODU2_TCM3_BDI
OTU2_SSF
LSR_INVALID
ODU2_TCM3_DEG
OTU2_TIM
LSR_WILL_DIE
ODU2_TCM3_LCK
OUT_PWR_HIGH
NO_BD_SOFT
ODU2_TCM3_LTC
OUT_PWR_LOW
NO_ELABEL
ODU2_TCM3_OCI
PORT_MODULE_OFFLINE
NULL_SEND
ODU2_TCM3_SSF
PRBS_LSS
OCh_FDI
ODU2_TCM3_TIM
REMOTE_FAULT

114
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI_O
ODU2_TCM4_AIS
REM_SD
OCh_FDI_P
ODU2_TCM4_BDI
REM_SF
OCh_LOS_P
ODU2_TCM4_DEG
RS_CROSSTR
OCh_OCI
ODU2_TCM4_LCK
R_LOC
OCh_SSF
ODU2_TCM4_LTC
R_LOF
OCh_SSF_O
ODU2_TCM4_OCI
R_LOS
OCh_SSF_P
ODU2_TCM4_SSF
TD
ODU2_PM_AIS
ODU2_TCM4_TIM
TEMP_OVER
ODU2_PM_BDI
ODU2_TCM5_AIS
TEM_HA
ODU2_PM_DEG
ODU2_TCM5_BDI
TEM_LA
ODU2_PM_LCK
ODU2_TCM5_DEG
TF
ODU2_PM_OCI
ODU2_TCM5_LCK
WAVEDATA_MIS
ODU2_PM_SSF
ODU2_TCM5_LTC
WRG_BD_TYPE
B1_EXC
ODU2_PM_TIM
ODU2_TCM5_SSF
B1_SD
ODU2_TCM1_AIS
ODU2_TCM5_TIM
BD_STATUS
ODU2_TCM1_BDI
ODU2_TCM6_AIS
BEFFEC_EXC
ODU2_TCM1_DEG
ODU2_TCM6_BDI
CLIENT_PORT_PS
ODU2_TCM1_LCK
ODU2_TCM6_DEG
ODU2_TCM1_LTC
ODU2_TCM6_LCK
ODU2_TCM1_OCI
ODU2_TCM6_LTC
COMMUN_FAIL
ODU2_TCM1_SSF
ODU2_TCM6_OCI
HARD_BAD
ODU2_TCM1_TIM
ODU2_TCM6_SSF
HARD_ERR
ODU2_TCM2_AIS
ODU2_TCM6_TIM
IN_PWR_HIGH
ODU2_TCM2_BDI
OPA_FAIL_INDI
IN_PWR_LOW
ODU2_TCM2_DEG
OPU2_PLM
J0_MM
ODU2_TCM2_LCK
OTU2_AIS
ODU2_TCM2_LTC
OTU2_BDI
LOCAL_FAULT
ODU2_TCM2_OCI
OTU2_DEG
TN12LSX
Issue 02 (2011-10-31)

115
OptiX OSN 8800/6800/3800

2 Alarm List
LOOP_ALM
ODU2_TCM2_SSF
OTU2_LOF
LPT_ACTIVE
ODU2_TCM2_TIM
OTU2_LOM
LSR_COOL_ALM
ODU2_TCM3_AIS
OTU2_SSF
LSR_FORCE_OPEN
ODU2_TCM3_BDI
OTU2_TIM
LSR_INVALID
ODU2_TCM3_DEG
OUT_PWR_HIGH
LSR_WILL_DIE
ODU2_TCM3_LCK
OUT_PWR_LOW
L_SYNC
ODU2_TCM3_LTC
PORT_MODULE_OFFLINE
NO_BD_SOFT
ODU2_TCM3_OCI
PRBS_LSS
NO_ELABEL
ODU2_TCM3_SSF
REMOTE_FAULT
NULL_SEND
ODU2_TCM3_TIM
REM_SD
OCh_FDI
ODU2_TCM4_AIS
REM_SF
OCh_FDI_O
ODU2_TCM4_BDI
RS_CROSSTR
OCh_FDI_P
ODU2_TCM4_DEG
R_LOC
OCh_LOS_P
ODU2_TCM4_LCK
R_LOF
OCh_OCI
ODU2_TCM4_LTC
R_LOS
OCh_SSF
ODU2_TCM4_OCI
TD
OCh_SSF_O
ODU2_TCM4_SSF
TEMP_OVER
OCh_SSF_P
ODU2_TCM4_TIM
TEM_HA
ODU2_PM_AIS
ODU2_TCM5_AIS
TEM_LA
ODU2_PM_BDI
ODU2_TCM5_BDI
TF
ODU2_PM_DEG
ODU2_TCM5_DEG
WAVEDATA_MIS
ODU2_PM_LCK
ODU2_TCM5_LCK
WRG_BD_TYPE
ODU2_PM_OCI
ODU2_TCM5_LTC
ODU2_PM_SSF
ODU2_TCM5_OCI
TN13LSX
Issue 02 (2011-10-31)
B1_EXC
ODU2_PM_TIM
ODU2_TCM5_SSF
B1_SD
ODU2_TCM1_AIS
ODU2_TCM5_TIM
BD_STATUS
ODU2_TCM1_BDI
ODU2_TCM6_AIS
BEFFEC_EXC
ODU2_TCM1_DEG
ODU2_TCM6_BDI

116
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
CLIENT_PORT_PS
ODU2_TCM1_LCK
ODU2_TCM6_DEG
ODU2_TCM1_LTC
ODU2_TCM6_LCK
ODU2_TCM1_OCI
ODU2_TCM6_LTC
COMMUN_FAIL
ODU2_TCM1_SSF
ODU2_TCM6_OCI
HARD_BAD
ODU2_TCM1_TIM
ODU2_TCM6_SSF
HARD_ERR
ODU2_TCM2_AIS
ODU2_TCM6_TIM
IN_PWR_HIGH
ODU2_TCM2_BDI
OPA_FAIL_INDI
IN_PWR_LOW
ODU2_TCM2_DEG
OPU2_PLM
J0_MM
ODU2_TCM2_LCK
OTU2_AIS
ODU2_TCM2_LTC
OTU2_BDI
LOCAL_FAULT
ODU2_TCM2_OCI
OTU2_DEG
LOOP_ALM
ODU2_TCM2_SSF
OTU2_LOF
LPT_ACTIVE
ODU2_TCM2_TIM
OTU2_LOM
LSR_COOL_ALM
ODU2_TCM3_AIS
OTU2_SSF
LSR_FORCE_OPEN
ODU2_TCM3_BDI
OTU2_TIM
LSR_INVALID
ODU2_TCM3_DEG
OUT_PWR_HIGH
LSR_WILL_DIE
ODU2_TCM3_LCK
OUT_PWR_LOW
L_SYNC
ODU2_TCM3_LTC
PORT_MODULE_OFFLINE
NO_BD_SOFT
ODU2_TCM3_OCI
PRBS_LSS
NO_ELABEL
ODU2_TCM3_SSF
REMOTE_FAULT
NULL_SEND
ODU2_TCM3_TIM
REM_SD
OCh_FDI
ODU2_TCM4_AIS
REM_SF
OCh_FDI_O
ODU2_TCM4_BDI
RS_CROSSTR
OCh_FDI_P
ODU2_TCM4_DEG
R_LOC
OCh_LOS_P
ODU2_TCM4_LCK
R_LOF
OCh_OCI
ODU2_TCM4_LTC
R_LOS
OCh_SSF
ODU2_TCM4_OCI
TD
OCh_SSF_O
ODU2_TCM4_SSF
TEMP_OVER
OCh_SSF_P
ODU2_TCM4_TIM
TEM_HA
ODU2_PM_AIS
ODU2_TCM5_AIS
TEM_LA

117
OptiX OSN 8800/6800/3800

2 Alarm List
ODU2_PM_BDI
ODU2_TCM5_BDI
TF
ODU2_PM_DEG
ODU2_TCM5_DEG
WAVEDATA_MIS
ODU2_PM_LCK
ODU2_TCM5_LCK
WRG_BD_TYPE
ODU2_PM_OCI
ODU2_TCM5_LTC
ODU2_PM_SSF
ODU2_TCM5_OCI
2.2.51 LWX2 Board Alarm List

B1_EXC
LSR_FORCE_OPEN
OUT_PWR_HIGH
B1_SD
LSR_INVALID
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
PORT_MODULE_OFFLINE
CLIENT_PORT_PS
MODULEFILE_UPDATE_
FAIL
RS_CROSSTR
NO_BD_SOFT
R_LOC
NO_ELABEL
R_LOF
COMMUN_FAIL
OCh_FDI
R_LOS
HARD_BAD
OCh_FDI_O
SPEED_OVER
HARD_ERR
OCh_FDI_P
TD
IN_PWR_HIGH
OCh_LOS_P
TEMP_OVER
IN_PWR_LOW
OCh_OCI
TEM_HA
J0_MM
OCh_SSF
TEM_LA
OCh_SSF_O
TF
LOOP_ALM
OCh_SSF_P
WAVEDATA_MIS
LSR_COOL_ALM
OPA_FAIL_INDI
WRG_BD_TYPE
B1_EXC
LSR_COOL_ALM
OUT_PWR_HIGH
B1_SD
LSR_FORCE_OPEN
OUT_PWR_LOW
2.2.52 LWXD Board Alarm List
Issue 02 (2011-10-31)

118
OptiX OSN 8800/6800/3800

2 Alarm List
BD_STATUS
LSR_INVALID
PORT_MODULE_OFFLINE
CLIENT_PORT_PS
LSR_WILL_DIE
RS_CROSSTR
MODULEFILE_UPDATE_
FAIL
R_LOC
NO_BD_SOFT
R_LOF
COMMUN_FAIL
NO_ELABEL
R_LOS
HARD_BAD
OCh_FDI
SPEED_OVER
HARD_ERR
OCh_FDI_O
TD
INTRA_OTU_PS
OCh_FDI_P
TEMP_OVER
INTRA_OTU_STA_INDI
OCh_LOS_P
TEM_HA
IN_PWR_HIGH
OCh_OCI
TEM_LA
IN_PWR_LOW
OCh_SSF
TF
J0_MM
OCh_SSF_O
WAVEDATA_MIS
OCh_SSF_P
WRG_BD_TYPE
LOOP_ALM
OPA_FAIL_INDI
2.2.53 LWXS Board Alarm List

TN11LWXS
Issue 02 (2011-10-31)
B1_EXC
LSR_FORCE_OPEN
OUT_PWR_HIGH
B1_SD
LSR_INVALID
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
PORT_MODULE_OFFLINE
CLIENT_PORT_PS
MODULEFILE_UPDATE_
FAIL
RS_CROSSTR
NO_BD_SOFT
R_LOC
NO_ELABEL
R_LOF
COMMUN_FAIL
OCh_FDI
R_LOS
HARD_BAD
OCh_FDI_O
SPEED_OVER
HARD_ERR
OCh_FDI_P
TD

119
OptiX OSN 8800/6800/3800

2 Alarm List
IN_PWR_HIGH
OCh_LOS_P
TEMP_OVER
IN_PWR_LOW
OCh_OCI
TEM_HA
J0_MM
OCh_SSF
TEM_LA
OCh_SSF_O
TF
LOOP_ALM
OCh_SSF_P
WAVEDATA_MIS
LSR_COOL_ALM
OPA_FAIL_INDI
WRG_BD_TYPE
B1_EXC
LSR_FORCE_OPEN
OUT_PWR_LOW
B1_SD
LSR_WILL_DIE
PORT_MODULE_OFFLINE
BD_STATUS
MODULEFILE_UPDATE_
FAIL
RS_CROSSTR
CLIENT_PORT_PS
NO_BD_SOFT
R_LOC
NO_ELABEL
R_LOF
OCh_FDI
R_LOS
COMMUN_FAIL
OCh_FDI_O
SPEED_OVER
HARD_BAD
OCh_FDI_P
TD
HARD_ERR
OCh_LOS_P
TEMP_OVER
IN_PWR_HIGH
OCh_OCI
TEM_HA
IN_PWR_LOW
OCh_SSF
TEM_LA
J0_MM
OCh_SSF_O
TF
OCh_SSF_P
WAVEDATA_MIS
LOOP_ALM
OPA_FAIL_INDI
WRG_BD_TYPE
LSR_COOL_ALM
OUT_PWR_HIGH
TN12LWXS
2.2.54 M40V Board Alarm List

TN12M40V
BD_STATUS
Issue 02 (2011-10-31)
MODULE_TEMP_OVER
OPA_FAIL_INDI
120
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
MOD_COM_FAIL
TEMP_OVER
HARD_BAD
NO_BD_PARA
WAVEDATA_MIS
HARD_ERR
NO_BD_SOFT
WRG_BD_TYPE
MODULEFILE_UPDAT
E_FAIL
NO_ELABEL
TN11M40V
BD_STATUS
MODULE_TEMP_OVER
OPA_FAIL_INDI
COMMUN_FAIL
MODULEFILE_UPDATE_F
AIL
TEMP_OVER
HARD_BAD
NO_BD_PARA
WAVEDATA_MIS
HARD_ERR
NO_BD_SOFT
WRG_BD_TYPE
MOD_COM_FAIL
NO_ELABEL
2.2.55 M40 Board Alarm List

BD_STATUS
MODULE_TEMP_OVER
TEMP_OVER
COMMUN_FAIL
NO_BD_PARA
WAVEDATA_MIS
HARD_BAD
NO_BD_SOFT
WRG_BD_TYPE
HARD_ERR
NO_ELABEL
MODULE_COOLCUR_OV
ER
OPA_FAIL_INDI
2.2.56 MCA4 Board Alarm List
Issue 02 (2011-10-31)
APE_ADJUST_FAIL
HARD_ERR
TEMP_OVER
APE_ADJUST_PEND
L
WAVEDATA_MIS
BD_STATUS
MOD_COM_FAIL
WRG_BD_TYPE
CHAN_ADD
NO_BD_PARA
WAVE_ADD_ABN
CHAN_LOS
NO_BD_SOFT
WAVE_DROP_ABN
COMMUN_FAIL
NO_ELABEL

121
OptiX OSN 8800/6800/3800

HARD_BAD
2 Alarm List
PORTSWITCH_FAIL
2.2.57 MCA8 Board Alarm List

APE_ADJUST_FAIL
HARD_ERR
TEMP_OVER
APE_ADJUST_PEND
L
WAVE_ADD_ABN
BD_STATUS
MOD_COM_FAIL
WAVE_DROP_ABN
CHAN_ADD
NO_BD_PARA
WAVEDATA_MIS
CHAN_LOS
NO_BD_SOFT
WRG_BD_TYPE
COMMUN_FAIL
NO_ELABEL
HARD_BAD
PORTSWITCH_FAIL
2.2.58 MR2 Board Alarm List

BD_STATUS
OMS_FDI-O
OPA_FAIL_INDI
OMS_BDI
OMS_FDI-P
WAVEDATA_MIS
OMS_BDI-O
OMS_SSF
WRG_BD_TYPE
OMS_BDI-P
OMS_SSF-O
OMS_FDI
OMS_SSF-P
Issue 02 (2011-10-31)
BD_STATUS
OMS_FDI-O
OPA_FAIL_INDI
OMS_BDI
OMS_FDI-P
WAVEDATA_MIS
OMS_BDI-O
OMS_SSF
WRG_BD_TYPE
OMS_BDI-P
OMS_SSF-O
OMS_FDI
OMS_SSF-P

122
OptiX OSN 8800/6800/3800

2 Alarm List

BD_STATUS
OMS_FDI-O
OPA_FAIL_INDI
OMS_BDI
OMS_FDI-P
WAVEDATA_MIS
OMS_BDI-O
OMS_SSF
WRG_BD_TYPE
OMS_BDI-P
OMS_SSF-O
OMS_FDI
OMS_SSF-P
2.2.61 MR8V Board Alarm List

BD_STATUS
OMS_BDI_P
OMS_SSF_P
COMMUN_FAIL
OMS_FDI
OPA_FAIL_INDI
HARD_BAD
OMS_FDI_O
TEMP_OVER
HARD_ERR
OMS_FDI_P
VOADATA_MIS
OMS_BDI
OMS_SSF
WAVEDATA_MIS
OMS_BDI_O
OMS_SSF_O
WRG_BD_TYPE
BD_STATUS
ODU0_TCMn_OCI
ODUFLEX_PM_AIS
BEFFEC_EXC
ODU0_TCMn_SSF
ODUFLEX_PM_BDI
BUS_ERR
ODU0_TCMn_TIM
ODUFLEX_PM_DEG
COMMUN_FAIL
ODU1_LOFLOM
ODUFLEX_PM_LCK
HARD_BAD
ODU1_PM_AIS
ODUFLEX_PM_OCI
HARD_ERR
ODU1_PM_BDI
ODUFLEX_PM_SSF
IN_PWR_HIGH
ODU1_PM_DEG
ODUFLEX_PM_TIM
IN_PWR_LOW
ODU1_PM_LCK
ODUKSP_PS
LASER_MODULE_MIS
MATCH
ODU1_PM_OCI
ODUKSP_STA_INDI
LOOP_ALM
ODU1_PM_SSF
ODU_SNCP_PS
LSR_WILL_DIE
ODU1_PM_TIM
ODU_SNCP_STA_INDI
2.2.62 ND2 Board Alarm List

TN53ND2
Issue 02 (2011-10-31)

123
OptiX OSN 8800/6800/3800

2 Alarm List
NO_BD_SOFT
ODU1_TCMn_AIS
OPA_FAIL_INDI
NO_ELABEL
ODU1_TCMn_BDI
OPU1_MSIM
NULL_SEND
ODU1_TCMn_DEG
OPU1_PLM
OCh_FDI
ODU1_TCMn_LCK
OPU2_MSIM
OCh_FDI_O
ODU1_TCMn_LTC
OPU2_PLM
OCh_FDI_P
ODU1_TCMn_OCI
OTU2_AIS
OCh_LOS_P
ODU1_TCMn_SSF
OTU2_BDI
OCh_OCI
ODU1_TCMn_TIM
OTU2_DEG
OCh_SSF
ODU2_PM_AIS
OTU2_LOF
OCh_SSF_O
ODU2_PM_BDI
OTU2_LOM
OCh_SSF_P
ODU2_PM_DEG
OTU2_SSF
ODU0_LOFLOM
ODU2_PM_LCK
OTU2_TIM
ODU0_PM_AIS
ODU2_PM_OCI
OUT_PWR_HIGH
ODU0_PM_BDI
ODU2_PM_SSF
OUT_PWR_LOW
ODU0_PM_DEG
ODU2_PM_TIM
PORT_MODULE_OFFLINE
ODU0_PM_LCK
ODU2_TCMn_AIS
PRBS_LSS
ODU0_PM_OCI
ODU2_TCMn_BDI
R_LOS
ODU0_PM_SSF
ODU2_TCMn_DEG
TD
ODU0_PM_TIM
ODU2_TCMn_LCK
TEMP_OVER
ODU0_TCMn_AIS
ODU2_TCMn_LTC
TEM_HA
ODU0_TCMn_BDI
ODU2_TCMn_OCI
TEM_LA
ODU0_TCMn_DEG
ODU2_TCMn_SSF
TF
ODU0_TCMn_LCK
ODU2_TCMn_TIM
WAVEDATA_MIS
ODU0_TCMn_LTC
ODUFLEX_LOFLOM
WRG_BD_TYPE
TN53ND2(COMP)
Issue 02 (2011-10-31)
BD_STATUS
ODU1_LOFLOM
ODU2_TCMn_TIM
BEFFEC_EXC
ODU1_PM_AIS
ODUKSP_PS
BUS_ERR
ODU1_PM_BDI
ODUKSP_STA_INDI
COMMUN_FAIL
ODU1_PM_DEG
ODU_SNCP_PS

124
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_BAD
ODU1_PM_LCK
ODU_SNCP_STA_INDI
HARD_ERR
ODU1_PM_OCI
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_PM_SSF
OPU1_MSIM
IN_PWR_LOW
ODU1_PM_TIM
OPU1_PLM
ODU1_TCMn_AIS
OPU2_MSIM
LOOP_ALM
ODU1_TCMn_BDI
OPU2_PLM
LSR_WILL_DIE
ODU1_TCMn_DEG
OTU2_AIS
NO_BD_SOFT
ODU1_TCMn_LCK
OTU2_BDI
NO_ELABEL
ODU1_TCMn_LTC
OTU2_DEG
NULL_SEND
ODU1_TCMn_OCI
OTU2_LOF
OCh_FDI
ODU1_TCMn_SSF
OTU2_LOM
OCh_FDI_O
ODU1_TCMn_TIM
OTU2_SSF
OCh_FDI_P
ODU2_PM_AIS
OTU2_TIM
OCh_LOS_P
ODU2_PM_BDI
OUT_PWR_HIGH
OCh_OCI
ODU2_PM_DEG
OUT_PWR_LOW
OCh_SSF
ODU2_PM_LCK
PORT_MODULE_OFFLINE
OCh_SSF_O
ODU2_PM_OCI
PRBS_LSS
OCh_SSF_P
ODU2_PM_SSF
R_LOS
ODU0_LOFLOM
ODU2_PM_TIM
TD
ODU0_PM_AIS
ODU2_TCMn_AIS
TEMP_OVER
ODU0_PM_BDI
ODU2_TCMn_BDI
TEM_HA
ODU0_PM_DEG
ODU2_TCMn_DEG
TEM_LA
ODU0_PM_LCK
ODU2_TCMn_LCK
TF
ODU0_PM_OCI
ODU2_TCMn_LTC
WAVEDATA_MIS
ODU0_PM_SSF
ODU2_TCMn_OCI
WRG_BD_TYPE
ODU0_PM_TIM
ODU2_TCMn_SSF
TN52ND2
BD_STATUS
Issue 02 (2011-10-31)
ODU1_TCM3_LCK

ODU2_TCM3_LTC
125
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
BEFFEC_EXC
ODU1_TCM3_LTC
ODU2_TCM3_OCI
BUS_ERR
ODU1_TCM3_OCI
ODU2_TCM3_SSF
COMMUN_FAIL
ODU1_TCM3_SSF
ODU2_TCM3_TIM
HARD_BAD
ODU1_TCM3_TIM
ODU2_TCM4_AIS
HARD_ERR
ODU1_TCM4_AIS
ODU2_TCM4_BDI
IN_PWR_HIGH
ODU1_TCM4_BDI
ODU2_TCM4_DEG
IN_PWR_LOW
ODU1_TCM4_DEG
ODU2_TCM4_LCK
LOOP_ALM
ODU1_TCM4_LCK
ODU2_TCM4_LTC
LSR_FORCE_OPEN
ODU1_TCM4_LTC
ODU2_TCM4_OCI
LSR_WILL_DIE
ODU1_TCM4_OCI
ODU2_TCM4_SSF
NO_BD_SOFT
ODU1_TCM4_SSF
ODU2_TCM4_TIM
NO_ELABEL
ODU1_TCM4_TIM
ODU2_TCM5_AIS
NULL_SEND
ODU1_TCM5_AIS
ODU2_TCM5_BDI
OCh_FDI
ODU1_TCM5_BDI
ODU2_TCM5_DEG
OCh_FDI_O
ODU1_TCM5_DEG
ODU2_TCM5_LCK
OCh_FDI_P
ODU1_TCM5_LCK
ODU2_TCM5_LTC
OCh_LOS_P
ODU1_TCM5_LTC
ODU2_TCM5_OCI
OCh_OCI
ODU1_TCM5_OCI
ODU2_TCM5_SSF
OCh_SSF
ODU1_TCM5_SSF
ODU2_TCM5_TIM
OCh_SSF_O
ODU1_TCM5_TIM
ODU2_TCM6_AIS
OCh_SSF_P
ODU1_TCM6_AIS
ODU2_TCM6_BDI
ODU0_LOFLOM
ODU1_TCM6_BDI
ODU2_TCM6_DEG
ODU0_PM_AIS
ODU1_TCM6_DEG
ODU2_TCM6_LCK
ODU0_PM_BDI
ODU1_TCM6_LCK
ODU2_TCM6_LTC
ODU0_PM_DEG
ODU1_TCM6_LTC
ODU2_TCM6_OCI
ODU0_PM_LCK
ODU1_TCM6_OCI
ODU2_TCM6_SSF
ODU0_PM_OCI
ODU1_TCM6_SSF
ODU2_TCM6_TIM
ODU0_PM_SSF
ODU1_TCM6_TIM
ODUKSP_PS
ODU0_PM_TIM
ODU2_LOFLOM
ODUKSP_STA_INDI
ODU1_LOFLOM
ODU2_PM_AIS
ODU_SNCP_PS
ODU1_PM_AIS
ODU2_PM_BDI
ODU_SNCP_STA_INDI

126
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_BDI
ODU2_PM_DEG
OPA_FAIL_INDI
ODU1_PM_DEG
ODU2_PM_LCK
OPU1_MSIM
ODU1_PM_LCK
ODU2_PM_OCI
OPU1_PLM
ODU1_PM_OCI
ODU2_PM_SSF
OPU2_MSIM
ODU1_PM_SSF
ODU2_PM_TIM
OPU2_PLM
ODU1_PM_TIM
ODU2_TCM1_AIS
OTU2_AIS
ODU1_TCM1_AIS
ODU2_TCM1_BDI
OTU2_BDI
ODU1_TCM1_BDI
ODU2_TCM1_DEG
OTU2_DEG
ODU1_TCM1_DEG
ODU2_TCM1_LCK
OTU2_LOF
ODU1_TCM1_LCK
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_LTC
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_OCI
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_SSF
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_TIM
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM2_AIS
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM2_BDI
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM2_DEG
ODU2_TCM2_LCK
R_LOS
ODU1_TCM2_LCK
ODU2_TCM2_LTC
TD
ODU1_TCM2_LTC
ODU2_TCM2_OCI
TEMP_OVER
ODU1_TCM2_OCI
ODU2_TCM2_SSF
TEM_HA
ODU1_TCM2_SSF
ODU2_TCM2_TIM
TEM_LA
ODU1_TCM2_TIM
ODU2_TCM3_AIS
TF
ODU1_TCM3_AIS
ODU2_TCM3_BDI
WAVEDATA_MIS
ODU1_TCM3_BDI
ODU2_TCM3_DEG
WRG_BD_TYPE
ODU1_TCM3_DEG
ODU2_TCM3_LCK
NOTE
TCM6.
2.2.63 NPO2 Board Alarm List

TN55NPO2(STND)
Issue 02 (2011-10-31)

127
OptiX OSN 8800/6800/3800

2 Alarm List
BD_STATUS
ODU1_PM_BDI
ODUKSP_PS
BEFFEC_EXC
ODU1_PM_DEG
ODUKSP_STA_INDI
BUS_ERR
ODU1_PM_LCK
ODU_SNCP_PS
COMMUN_FAIL
ODU1_PM_OCI
ODU_SNCP_STA_INDI
EXT_MODULE_OFFLINE
ODU1_PM_SSF
OPA_FAIL_INDI
HARD_BAD
ODU1_PM_TIM
OPU1_MSIM
HARD_ERR
ODU1_TCMn_AIS
OPU1_PLM
IN_PWR_HIGH
ODU1_TCMn_BDI
OPU2_MSIM
IN_PWR_LOW
ODU1_TCMn_DEG
OPU2_PLM
IPA_SHUT
ODU1_TCMn_LCK
OTU2_AIS
LOOP_ALM
ODU1_TCMn_LTC
OTU2_BDI
LSR_FORCE_OPEN
ODU1_TCMn_OCI
OTU2_DEG
LSR_WILL_DIE
ODU1_TCMn_SSF
OTU2_LOF
ODU1_TCMn_TIM
OTU2_LOM
MUT_LOS
ODU2_PM_AIS
OTU2_SSF
NO_BD_PARA
ODU2_PM_BDI
OTU2_TIM
NO_BD_SOFT
ODU2_PM_DEG
OUT_PWR_HIGH
NO_ELABEL
ODU2_PM_LCK
OUT_PWR_LOW
NULL_SEND
ODU2_PM_OCI
PRBS_LSS
ODU0_LOFLOM
ODU2_PM_SSF
R_LOS
ODU0_PM_AIS
ODU2_PM_TIM
TD
ODU0_PM_BDI
ODU2_TCMn_AIS
TEMP_OVER
ODU0_PM_DEG
ODU2_TCMn_BDI
TEM_HA
ODU0_PM_LCK
ODU2_TCMn_DEG
TEM_LA
ODU0_PM_OCI
ODU2_TCMn_LCK
TF
ODU0_PM_SSF
ODU2_TCMn_LTC
WAVEDATA_MIS
ODU0_PM_TIM
ODU2_TCMn_OCI
WRG_BD_TYPE
ODU1_LOFLOM
ODU2_TCMn_SSF
ODU1_PM_AIS
ODU2_TCMn_TIM
TN55NPO2
Issue 02 (2011-10-31)

128
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
BD_STATUS
ODU1_LOFLOM
OMS_BDI
BEFFEC_EXC
ODU1_PM_AIS
OMS_BDI_O
BUS_ERR
ODU1_PM_BDI
OMS_BDI_P
COMMUN_FAIL
ODU1_PM_DEG
OMS_FDI
EXT_MODULE_OFFLINE
ODU1_PM_LCK
OMS_FDI_O
HARD_BAD
ODU1_PM_OCI
OMS_FDI_P
HARD_ERR
ODU1_PM_SSF
OMS_LOS_P
IN_PWR_HIGH
ODU1_PM_TIM
OMS_SSF
IN_PWR_LOW
ODU1_TCMn_AIS
OMS_SSF_O
IPA_SHUT
ODU1_TCMn_BDI
OMS_SSF_P
LOOP_ALM
ODU1_TCMn_DEG
OPA_FAIL_INDI
LSR_FORCE_OPEN
ODU1_TCMn_LCK
OPU1_MSIM
LSR_WILL_DIE
ODU1_TCMn_LTC
OPU1_PLM
ODU1_TCMn_OCI
OPU2_MSIM
MUT_LOS
ODU1_TCMn_SSF
OPU2_PLM
NO_BD_PARA
ODU1_TCMn_TIM
OTU2_AIS
NO_BD_SOFT
ODU2_PM_AIS
OTU2_BDI
NO_ELABEL
ODU2_PM_BDI
OTU2_DEG
NULL_SEND
ODU2_PM_DEG
OTU2_LOF
OCh_FDI
ODU2_PM_LCK
OTU2_LOM
OCh_FDI_O
ODU2_PM_OCI
OTU2_SSF
OCh_FDI_P
ODU2_PM_SSF
OTU2_TIM
OCh_LOS_P
ODU2_PM_TIM
OUT_PWR_HIGH
OCh_OCI
ODU2_TCMn_AIS
OUT_PWR_LOW
OCh_SSF
ODU2_TCMn_BDI
PRBS_LSS
OCh_SSF_O
ODU2_TCMn_DEG
R_LOS
OCh_SSF_P
ODU2_TCMn_LCK
TD
ODU0_LOFLOM
ODU2_TCMn_LTC
TEMP_OVER
ODU0_PM_AIS
ODU2_TCMn_OCI
TEM_HA
ODU0_PM_BDI
ODU2_TCMn_SSF
TEM_LA

129
OptiX OSN 8800/6800/3800

2 Alarm List
ODU0_PM_DEG
ODU2_TCMn_TIM
TF
ODU0_PM_LCK
ODUKSP_PS
WAVEDATA_MIS
ODU0_PM_OCI
ODUKSP_STA_INDI
WRG_BD_TYPE
ODU0_PM_SSF
ODU_SNCP_PS
ODU0_PM_TIM
ODU_SNCP_STA_INDI
TN54NPO2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM3_LCK
ODU2_TCM4_BDI
BEFFEC_EXC
ODU1_TCM3_LTC
ODU2_TCM4_DEG
BUS_ERR
ODU1_TCM3_OCI
ODU2_TCM4_LCK
COMMUN_FAIL
ODU1_TCM3_SSF
ODU2_TCM4_LTC
HARD_BAD
ODU1_TCM3_TIM
ODU2_TCM4_OCI
HARD_ERR
ODU1_TCM4_AIS
ODU2_TCM4_SSF
IN_PWR_HIGH
ODU1_TCM4_BDI
ODU2_TCM4_TIM
IN_PWR_LOW
ODU1_TCM4_DEG
ODU2_TCM5_AIS
ODU1_TCM4_LCK
ODU2_TCM5_BDI
LOOP_ALM
ODU1_TCM4_LTC
ODU2_TCM5_DEG
LSR_FORCE_OPEN
ODU1_TCM4_OCI
ODU2_TCM5_LCK
LSR_WILL_DIE
ODU1_TCM4_SSF
ODU2_TCM5_LTC
ODU1_TCM4_TIM
ODU2_TCM5_OCI
MUT_LOS
ODU1_TCM5_AIS
ODU2_TCM5_SSF
NO_BD_PARA
ODU1_TCM5_BDI
ODU2_TCM5_TIM
NO_BD_SOFT
ODU1_TCM5_DEG
ODU2_TCM6_AIS
NO_ELABEL
ODU1_TCM5_LCK
ODU2_TCM6_BDI
NULL_SEND
ODU1_TCM5_LTC
ODU2_TCM6_DEG
OCh_FDI
ODU1_TCM5_OCI
ODU2_TCM6_LCK
OCh_FDI_O
ODU1_TCM5_SSF
ODU2_TCM6_LTC
OCh_FDI_P
ODU1_TCM5_TIM
ODU2_TCM6_OCI
OCh_LOS_P
ODU1_TCM6_AIS
ODU2_TCM6_SSF

130
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
OCh_OCI
ODU1_TCM6_BDI
ODU2_TCM6_TIM
OCh_SSF
ODU1_TCM6_DEG
ODUKSP_PS
OCh_SSF_O
ODU1_TCM6_LCK
ODUKSP_STA_INDI
OCh_SSF_P
ODU1_TCM6_LTC
ODU_SNCP_PS
ODU0_LOFLOM
ODU1_TCM6_OCI
ODU_SNCP_STA_INDI
ODU0_PM_AIS
ODU1_TCM6_SSF
OMS_BDI
ODU0_PM_BDI
ODU1_TCM6_TIM
OMS_BDI_O
ODU0_PM_DEG
ODU2_PM_AIS
OMS_BDI_P
ODU0_PM_LCK
ODU2_PM_BDI
OMS_FDI
ODU0_PM_OCI
ODU2_PM_DEG
OMS_FDI_O
ODU0_PM_SSF
ODU2_PM_LCK
OMS_FDI_P
ODU0_PM_TIM
ODU2_PM_OCI
OMS_LOS_P
ODU1_LOFLOM
ODU2_PM_SSF
OMS_SSF
ODU1_PM_AIS
ODU2_PM_TIM
OMS_SSF_O
ODU1_PM_BDI
ODU2_TCM1_AIS
OMS_SSF_P
ODU1_PM_DEG
ODU2_TCM1_BDI
OPA_FAIL_INDI
ODU1_PM_LCK
ODU2_TCM1_DEG
OPU1_MSIM
ODU1_PM_OCI
ODU2_TCM1_LCK
OPU1_PLM
ODU1_PM_SSF
ODU2_TCM1_LTC
OPU2_MSIM
ODU1_PM_TIM
ODU2_TCM1_OCI
OPU2_PLM
ODU1_TCM1_AIS
ODU2_TCM1_SSF
OTU2_AIS
ODU1_TCM1_BDI
ODU2_TCM1_TIM
OTU2_BDI
ODU1_TCM1_DEG
ODU2_TCM2_AIS
OTU2_DEG
ODU1_TCM1_LCK
ODU2_TCM2_BDI
OTU2_LOF
ODU1_TCM1_LTC
ODU2_TCM2_DEG
OTU2_LOM
ODU1_TCM1_OCI
ODU2_TCM2_LCK
OTU2_SSF
ODU1_TCM1_SSF
ODU2_TCM2_LTC
OTU2_TIM
ODU1_TCM1_TIM
ODU2_TCM2_OCI
OUT_PWR_HIGH
ODU1_TCM2_AIS
ODU2_TCM2_SSF
OUT_PWR_LOW
ODU1_TCM2_BDI
ODU2_TCM2_TIM
PORT_MODULE_OFFLINE

131
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM2_DEG
ODU2_TCM3_AIS
PRBS_LSS
ODU1_TCM2_LCK
ODU2_TCM3_BDI
R_LOS
ODU1_TCM2_LTC
ODU2_TCM3_DEG
TD
ODU1_TCM2_OCI
ODU2_TCM3_LCK
TEMP_OVER
ODU1_TCM2_SSF
ODU2_TCM3_LTC
TEM_HA
ODU1_TCM2_TIM
ODU2_TCM3_OCI
TEM_LA
ODU1_TCM3_AIS
ODU2_TCM3_SSF
TF
ODU1_TCM3_BDI
ODU2_TCM3_TIM
WAVEDATA_MIS
ODU1_TCM3_DEG
ODU2_TCM4_AIS
WRG_BD_TYPE
2.2.64 NPO2E Board Alarm List

TN55NPO2E
Issue 02 (2011-10-31)
BD_STATUS
ODU1_PM_BDI
ODUKSP_PS
BEFFEC_EXC
ODU1_PM_DEG
ODUKSP_STA_INDI
BUS_ERR
ODU1_PM_LCK
ODU_SNCP_PS
COMMUN_FAIL
ODU1_PM_OCI
ODU_SNCP_STA_INDI
EXT_MODULE_OFFLINE
ODU1_PM_SSF
OPA_FAIL_INDI
HARD_BAD
ODU1_PM_TIM
OPU1_MSIM
HARD_ERR
ODU1_TCMn_AIS
OPU1_PLM
IN_PWR_HIGH
ODU1_TCMn_BDI
OPU2_MSIM
IN_PWR_LOW
ODU1_TCMn_DEG
OPU2_PLM
IPA_SHUT
ODU1_TCMn_LCK
OTU2_AIS
LOOP_ALM
ODU1_TCMn_LTC
OTU2_BDI
LSR_FORCE_OPEN
ODU1_TCMn_OCI
OTU2_DEG
LSR_WILL_DIE
ODU1_TCMn_SSF
OTU2_LOF
ODU1_TCMn_TIM
OTU2_LOM
MUT_LOS
ODU2_PM_AIS
OTU2_SSF
NO_BD_PARA
ODU2_PM_BDI
OTU2_TIM
NO_BD_SOFT
ODU2_PM_DEG
OUT_PWR_HIGH
NO_ELABEL
ODU2_PM_LCK
OUT_PWR_LOW

132
OptiX OSN 8800/6800/3800

2 Alarm List
NULL_SEND
ODU2_PM_OCI
PRBS_LSS
ODU0_LOFLOM
ODU2_PM_SSF
R_LOS
ODU0_PM_AIS
ODU2_PM_TIM
TD
ODU0_PM_BDI
ODU2_TCMn_AIS
TEMP_OVER
ODU0_PM_DEG
ODU2_TCMn_BDI
TEM_HA
ODU0_PM_LCK
ODU2_TCMn_DEG
TEM_LA
ODU0_PM_OCI
ODU2_TCMn_LCK
TF
ODU0_PM_SSF
ODU2_TCMn_LTC
WAVEDATA_MIS
ODU0_PM_TIM
ODU2_TCMn_OCI
WRG_BD_TYPE
ODU1_LOFLOM
ODU2_TCMn_SSF
ODU1_PM_AIS
ODU2_TCMn_TIM
2.2.65 NQ2 Board Alarm List

TN53NQ2
Issue 02 (2011-10-31)
BD_STATUS
ODU0_TCMn_OCI
ODUFLEX_PM_AIS
BEFFEC_EXC
ODU0_TCMn_SSF
ODUFLEX_PM_BDI
BUS_ERR
ODU0_TCMn_TIM
ODUFLEX_PM_DEG
COMMUN_FAIL
ODU1_LOFLOM
ODUFLEX_PM_LCK
HARD_BAD
ODU1_PM_AIS
ODUFLEX_PM_OCI
HARD_ERR
ODU1_PM_BDI
ODUFLEX_PM_SSF
IN_PWR_HIGH
ODU1_PM_DEG
ODUFLEX_PM_TIM
IN_PWR_LOW
ODU1_PM_LCK
ODUKSP_PS
LASER_MODULE_MIS
MATCH
ODU1_PM_OCI
ODUKSP_STA_INDI
LOOP_ALM
ODU1_PM_SSF
ODU_SNCP_PS
LSR_WILL_DIE
ODU1_PM_TIM
ODU_SNCP_STA_INDI
NO_BD_SOFT
ODU1_TCMn_AIS
OPA_FAIL_INDI
NO_ELABEL
ODU1_TCMn_BDI
OPU1_MSIM
NULL_SEND
ODU1_TCMn_DEG
OPU1_PLM
OCh_FDI
ODU1_TCMn_LCK
OPU2_MSIM
OCh_FDI_O
ODU1_TCMn_LTC
OPU2_PLM

133
OptiX OSN 8800/6800/3800

2 Alarm List
OCh_FDI_P
ODU1_TCMn_OCI
OTU2_AIS
OCh_LOS_P
ODU1_TCMn_SSF
OTU2_BDI
OCh_OCI
ODU1_TCMn_TIM
OTU2_DEG
OCh_SSF
ODU2_PM_AIS
OTU2_LOF
OCh_SSF_O
ODU2_PM_BDI
OTU2_LOM
OCh_SSF_P
ODU2_PM_DEG
OTU2_SSF
ODU0_LOFLOM
ODU2_PM_LCK
OTU2_TIM
ODU0_PM_AIS
ODU2_PM_OCI
OUT_PWR_HIGH
ODU0_PM_BDI
ODU2_PM_SSF
OUT_PWR_LOW
ODU0_PM_DEG
ODU2_PM_TIM
PORT_MODULE_OFFLINE
ODU0_PM_LCK
ODU2_TCMn_AIS
PRBS_LSS
ODU0_PM_OCI
ODU2_TCMn_BDI
R_LOS
ODU0_PM_SSF
ODU2_TCMn_DEG
TD
ODU0_PM_TIM
ODU2_TCMn_LCK
TEMP_OVER
ODU0_TCMn_AIS
ODU2_TCMn_LTC
TEM_HA
ODU0_TCMn_BDI
ODU2_TCMn_OCI
TEM_LA
ODU0_TCMn_DEG
ODU2_TCMn_SSF
TF
ODU0_TCMn_LCK
ODU2_TCMn_TIM
WAVEDATA_MIS
ODU0_TCMn_LTC
ODUFLEX_LOFLOM
WRG_BD_TYPE
TN53NQ2(COMP)
Issue 02 (2011-10-31)
BD_STATUS
ODU1_LOFLOM
ODU2_TCMn_TIM
BEFFEC_EXC
ODU1_PM_AIS
ODUKSP_PS
BUS_ERR
ODU1_PM_BDI
ODUKSP_STA_INDI
COMMUN_FAIL
ODU1_PM_DEG
ODU_SNCP_PS
HARD_BAD
ODU1_PM_LCK
ODU_SNCP_STA_INDI
HARD_ERR
ODU1_PM_OCI
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_PM_SSF
OPU1_MSIM
IN_PWR_LOW
ODU1_PM_TIM
OPU1_PLM
ODU1_TCMn_AIS
OPU2_MSIM

134
OptiX OSN 8800/6800/3800

2 Alarm List
LOOP_ALM
ODU1_TCMn_BDI
OPU2_PLM
LSR_WILL_DIE
ODU1_TCMn_DEG
OTU2_AIS
NO_BD_SOFT
ODU1_TCMn_LCK
OTU2_BDI
NO_ELABEL
ODU1_TCMn_LTC
OTU2_DEG
NULL_SEND
ODU1_TCMn_OCI
OTU2_LOF
OCh_FDI
ODU1_TCMn_SSF
OTU2_LOM
OCh_FDI_O
ODU1_TCMn_TIM
OTU2_SSF
OCh_FDI_P
ODU2_PM_AIS
OTU2_TIM
OCh_LOS_P
ODU2_PM_BDI
OUT_PWR_HIGH
OCh_OCI
ODU2_PM_DEG
OUT_PWR_LOW
OCh_SSF
ODU2_PM_LCK
PORT_MODULE_OFFLINE
OCh_SSF_O
ODU2_PM_OCI
PRBS_LSS
OCh_SSF_P
ODU2_PM_SSF
R_LOS
ODU0_LOFLOM
ODU2_PM_TIM
TD
ODU0_PM_AIS
ODU2_TCMn_AIS
TEMP_OVER
ODU0_PM_BDI
ODU2_TCMn_BDI
TEM_HA
ODU0_PM_DEG
ODU2_TCMn_DEG
TEM_LA
ODU0_PM_LCK
ODU2_TCMn_LCK
TF
ODU0_PM_OCI
ODU2_TCMn_LTC
WAVEDATA_MIS
ODU0_PM_SSF
ODU2_TCMn_OCI
WRG_BD_TYPE
ODU0_PM_TIM
ODU2_TCMn_SSF
TN54NQ2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM3_DEG
ODU2_TCM3_LTC
BEFFEC_EXC
ODU1_TCM3_LCK
ODU2_TCM3_OCI
BUS_ERR
ODU1_TCM3_LTC
ODU2_TCM3_SSF
COMMUN_FAIL
ODU1_TCM3_OCI
ODU2_TCM3_TIM
HARD_BAD
ODU1_TCM3_SSF
ODU2_TCM4_AIS
HARD_ERR
ODU1_TCM3_TIM
ODU2_TCM4_BDI
IN_PWR_HIGH
ODU1_TCM4_AIS
ODU2_TCM4_DEG

135
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
IN_PWR_LOW
ODU1_TCM4_BDI
ODU2_TCM4_LCK
ODU1_TCM4_DEG
ODU2_TCM4_LTC
LOOP_ALM
ODU1_TCM4_LCK
ODU2_TCM4_OCI
LSR_FORCE_OPEN
ODU1_TCM4_LTC
ODU2_TCM4_SSF
LSR_WILL_DIE
ODU1_TCM4_OCI
ODU2_TCM4_TIM
NO_BD_SOFT
ODU1_TCM4_SSF
ODU2_TCM5_AIS
NO_ELABEL
ODU1_TCM4_TIM
ODU2_TCM5_BDI
NULL_SEND
ODU1_TCM5_AIS
ODU2_TCM5_DEG
OCh_FDI
ODU1_TCM5_BDI
ODU2_TCM5_LCK
OCh_FDI_O
ODU1_TCM5_DEG
ODU2_TCM5_LTC
OCh_FDI_P
ODU1_TCM5_LCK
ODU2_TCM5_OCI
OCh_LOS_P
ODU1_TCM5_LTC
ODU2_TCM5_SSF
OCh_OCI
ODU1_TCM5_OCI
ODU2_TCM5_TIM
OCh_SSF
ODU1_TCM5_SSF
ODU2_TCM6_AIS
OCh_SSF_O
ODU1_TCM5_TIM
ODU2_TCM6_BDI
OCh_SSF_P
ODU1_TCM6_AIS
ODU2_TCM6_DEG
ODU0_LOFLOM
ODU1_TCM6_BDI
ODU2_TCM6_LCK
ODU0_PM_AIS
ODU1_TCM6_DEG
ODU2_TCM6_LTC
ODU0_PM_BDI
ODU1_TCM6_LCK
ODU2_TCM6_OCI
ODU0_PM_DEG
ODU1_TCM6_LTC
ODU2_TCM6_SSF
ODU0_PM_LCK
ODU1_TCM6_OCI
ODU2_TCM6_TIM
ODU0_PM_OCI
ODU1_TCM6_SSF
ODUKSP_PS
ODU0_PM_SSF
ODU1_TCM6_TIM
ODUKSP_STA_INDI
ODU0_PM_TIM
ODU2_PM_AIS
ODU_SNCP_PS
ODU1_LOFLOM
ODU2_PM_BDI
ODU_SNCP_STA_INDI
ODU1_PM_AIS
ODU2_PM_DEG
OPA_FAIL_INDI
ODU1_PM_BDI
ODU2_PM_LCK
OPU1_MSIM
ODU1_PM_DEG
ODU2_PM_OCI
OPU1_PLM
ODU1_PM_LCK
ODU2_PM_SSF
OPU2_MSIM
ODU1_PM_OCI
ODU2_PM_TIM
OPU2_PLM

136
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_SSF
ODU2_TCM1_AIS
OTU2_AIS
ODU1_PM_TIM
ODU2_TCM1_BDI
OTU2_BDI
ODU1_TCM1_AIS
ODU2_TCM1_DEG
OTU2_DEG
ODU1_TCM1_BDI
ODU2_TCM1_LCK
OTU2_LOF
ODU1_TCM1_DEG
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_LCK
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_LTC
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_OCI
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_SSF
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM1_TIM
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM2_AIS
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM2_BDI
ODU2_TCM2_LCK
R_LOS
ODU1_TCM2_DEG
ODU2_TCM2_LTC
TD
ODU1_TCM2_LCK
ODU2_TCM2_OCI
TEMP_OVER
ODU1_TCM2_LTC
ODU2_TCM2_SSF
TEM_HA
ODU1_TCM2_OCI
ODU2_TCM2_TIM
TEM_LA
ODU1_TCM2_SSF
ODU2_TCM3_AIS
TF
ODU1_TCM2_TIM
ODU2_TCM3_BDI
WAVEDATA_MIS
ODU1_TCM3_AIS
ODU2_TCM3_DEG
WRG_BD_TYPE
ODU1_TCM3_BDI
ODU2_TCM3_LCK
TN52NQ2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM3_DEG
ODU2_TCM3_LTC
BEFFEC_EXC
ODU1_TCM3_LCK
ODU2_TCM3_OCI
BUS_ERR
ODU1_TCM3_LTC
ODU2_TCM3_SSF
COMMUN_FAIL
ODU1_TCM3_OCI
ODU2_TCM3_TIM
HARD_BAD
ODU1_TCM3_SSF
ODU2_TCM4_AIS
HARD_ERR
ODU1_TCM3_TIM
ODU2_TCM4_BDI
IN_PWR_HIGH
ODU1_TCM4_AIS
ODU2_TCM4_DEG
IN_PWR_LOW
ODU1_TCM4_BDI
ODU2_TCM4_LCK

137
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU1_TCM4_DEG
ODU2_TCM4_LTC
LOOP_ALM
ODU1_TCM4_LCK
ODU2_TCM4_OCI
LSR_FORCE_OPEN
ODU1_TCM4_LTC
ODU2_TCM4_SSF
LSR_WILL_DIE
ODU1_TCM4_OCI
ODU2_TCM4_TIM
NO_BD_SOFT
ODU1_TCM4_SSF
ODU2_TCM5_AIS
NO_ELABEL
ODU1_TCM4_TIM
ODU2_TCM5_BDI
NULL_SEND
ODU1_TCM5_AIS
ODU2_TCM5_DEG
OCh_FDI
ODU1_TCM5_BDI
ODU2_TCM5_LCK
OCh_FDI_O
ODU1_TCM5_DEG
ODU2_TCM5_LTC
OCh_FDI_P
ODU1_TCM5_LCK
ODU2_TCM5_OCI
OCh_LOS_P
ODU1_TCM5_LTC
ODU2_TCM5_SSF
OCh_OCI
ODU1_TCM5_OCI
ODU2_TCM5_TIM
OCh_SSF
ODU1_TCM5_SSF
ODU2_TCM6_AIS
OCh_SSF_O
ODU1_TCM5_TIM
ODU2_TCM6_BDI
OCh_SSF_P
ODU1_TCM6_AIS
ODU2_TCM6_DEG
ODU0_LOFLOM
ODU1_TCM6_BDI
ODU2_TCM6_LCK
ODU0_PM_AIS
ODU1_TCM6_DEG
ODU2_TCM6_LTC
ODU0_PM_BDI
ODU1_TCM6_LCK
ODU2_TCM6_OCI
ODU0_PM_DEG
ODU1_TCM6_LTC
ODU2_TCM6_SSF
ODU0_PM_LCK
ODU1_TCM6_OCI
ODU2_TCM6_TIM
ODU0_PM_OCI
ODU1_TCM6_SSF
ODUKSP_PS
ODU0_PM_SSF
ODU1_TCM6_TIM
ODUKSP_STA_INDI
ODU0_PM_TIM
ODU2_PM_AIS
ODU_SNCP_PS
ODU1_LOFLOM
ODU2_PM_BDI
ODU_SNCP_STA_INDI
ODU1_PM_AIS
ODU2_PM_DEG
OPA_FAIL_INDI
ODU1_PM_BDI
ODU2_PM_LCK
OPU1_MSIM
ODU1_PM_DEG
ODU2_PM_OCI
OPU1_PLM
ODU1_PM_LCK
ODU2_PM_SSF
OPU2_MSIM
ODU1_PM_OCI
ODU2_PM_TIM
OPU2_PLM
ODU1_PM_SSF
ODU2_TCM1_AIS
OTU2_AIS

138
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_TIM
ODU2_TCM1_BDI
OTU2_BDI
ODU1_TCM1_AIS
ODU2_TCM1_DEG
OTU2_DEG
ODU1_TCM1_BDI
ODU2_TCM1_LCK
OTU2_LOF
ODU1_TCM1_DEG
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_LCK
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_LTC
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_OCI
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_SSF
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM1_TIM
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM2_AIS
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM2_BDI
ODU2_TCM2_LCK
R_LOS
ODU1_TCM2_DEG
ODU2_TCM2_LTC
TD
ODU1_TCM2_LCK
ODU2_TCM2_OCI
TEMP_OVER
ODU1_TCM2_LTC
ODU2_TCM2_SSF
TEM_HA
ODU1_TCM2_OCI
ODU2_TCM2_TIM
TEM_LA
ODU1_TCM2_SSF
ODU2_TCM3_AIS
TF
ODU1_TCM2_TIM
ODU2_TCM3_BDI
WAVEDATA_MIS
ODU1_TCM3_AIS
ODU2_TCM3_DEG
WRG_BD_TYPE
ODU1_TCM3_BDI
ODU2_TCM3_LCK
TN51NQ2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM3_SSF
ODU2_TCM3_OCI
BEFFEC_EXC
ODU1_TCM3_TIM
ODU2_TCM3_SSF
BUS_ERR
ODU1_TCM4_AIS
ODU2_TCM3_TIM
COMMUN_FAIL
ODU1_TCM4_BDI
ODU2_TCM4_AIS
HARD_BAD
ODU1_TCM4_DEG
ODU2_TCM4_BDI
HARD_ERR
ODU1_TCM4_LCK
ODU2_TCM4_DEG
IN_PWR_HIGH
ODU1_TCM4_LTC
ODU2_TCM4_LCK
IN_PWR_LOW
ODU1_TCM4_OCI
ODU2_TCM4_LTC

139
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU1_TCM4_SSF
ODU2_TCM4_OCI
LOOP_ALM
ODU1_TCM4_TIM
ODU2_TCM4_SSF
LSR_COOL_ALM
ODU1_TCM5_AIS
ODU2_TCM4_TIM
LSR_FORCE_OPEN
ODU1_TCM5_BDI
ODU2_TCM5_AIS
LSR_WILL_DIE
ODU1_TCM5_DEG
ODU2_TCM5_BDI
NO_BD_SOFT
ODU1_TCM5_LCK
ODU2_TCM5_DEG
NO_ELABEL
ODU1_TCM5_LTC
ODU2_TCM5_LCK
NULL_SEND
ODU1_TCM5_OCI
ODU2_TCM5_LTC
OCh_FDI
ODU1_TCM5_SSF
ODU2_TCM5_OCI
OCh_FDI_O
ODU1_TCM5_TIM
ODU2_TCM5_SSF
OCh_FDI_P
ODU1_TCM6_AIS
ODU2_TCM5_TIM
OCh_LOS_P
ODU1_TCM6_BDI
ODU2_TCM6_AIS
OCh_OCI
ODU1_TCM6_DEG
ODU2_TCM6_BDI
OCh_SSF
ODU1_TCM6_LCK
ODU2_TCM6_DEG
OCh_SSF_O
ODU1_TCM6_LTC
ODU2_TCM6_LCK
OCh_SSF_P
ODU1_TCM6_OCI
ODU2_TCM6_LTC
ODU1_LOFLOM
ODU1_TCM6_SSF
ODU2_TCM6_OCI
ODU1_PM_AIS
ODU1_TCM6_TIM
ODU2_TCM6_SSF
ODU1_PM_BDI
ODU2_PM_AIS
ODU2_TCM6_TIM
ODU1_PM_DEG
ODU2_PM_BDI
ODUKSP_PS
ODU1_PM_LCK
ODU2_PM_DEG
ODUKSP_STA_INDI
ODU1_PM_OCI
ODU2_PM_LCK
ODU_SNCP_PS
ODU1_PM_SSF
ODU2_PM_OCI
ODU_SNCP_STA_INDI
ODU1_PM_TIM
ODU2_PM_SSF
OPA_FAIL_INDI
ODU1_TCM1_AIS
ODU2_PM_TIM
OPU2_MSIM
ODU1_TCM1_BDI
ODU2_TCM1_AIS
OPU2_PLM
ODU1_TCM1_DEG
ODU2_TCM1_BDI
OTU2_AIS
ODU1_TCM1_LCK
ODU2_TCM1_DEG
OTU2_BDI
ODU1_TCM1_LTC
ODU2_TCM1_LCK
OTU2_DEG
ODU1_TCM1_OCI
ODU2_TCM1_LTC
OTU2_LOF

140
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM1_SSF
ODU2_TCM1_OCI
OTU2_LOM
ODU1_TCM1_TIM
ODU2_TCM1_SSF
OTU2_SSF
ODU1_TCM2_AIS
ODU2_TCM1_TIM
OTU2_TIM
ODU1_TCM2_BDI
ODU2_TCM2_AIS
OUT_PWR_HIGH
ODU1_TCM2_DEG
ODU2_TCM2_BDI
OUT_PWR_LOW
ODU1_TCM2_LCK
ODU2_TCM2_DEG
PORT_MODULE_OFFLINE
ODU1_TCM2_LTC
ODU2_TCM2_LCK
PRBS_LSS
ODU1_TCM2_OCI
ODU2_TCM2_LTC
R_LOS
ODU1_TCM2_SSF
ODU2_TCM2_OCI
TD
ODU1_TCM2_TIM
ODU2_TCM2_SSF
TEMP_OVER
ODU1_TCM3_AIS
ODU2_TCM2_TIM
TEM_HA
ODU1_TCM3_BDI
ODU2_TCM3_AIS
TEM_LA
ODU1_TCM3_DEG
ODU2_TCM3_BDI
TF
ODU1_TCM3_LCK
ODU2_TCM3_DEG
WAVEDATA_MIS
ODU1_TCM3_LTC
ODU2_TCM3_LCK
WRG_BD_TYPE
ODU1_TCM3_OCI
ODU2_TCM3_LTC
2.2.66 NS2 Board Alarm List

TN53NS2
Issue 02 (2011-10-31)
BD_STATUS
ODU0_TCMn_OCI
ODUFLEX_PM_AIS
BEFFEC_EXC
ODU0_TCMn_SSF
ODUFLEX_PM_BDI
BUS_ERR
ODU0_TCMn_TIM
ODUFLEX_PM_DEG
COMMUN_FAIL
ODU1_LOFLOM
ODUFLEX_PM_LCK
HARD_BAD
ODU1_PM_AIS
ODUFLEX_PM_OCI
HARD_ERR
ODU1_PM_BDI
ODUFLEX_PM_SSF
IN_PWR_HIGH
ODU1_PM_DEG
ODUFLEX_PM_TIM
IN_PWR_LOW
ODU1_PM_LCK
ODUKSP_PS
LASER_MODULE_MIS
MATCH
ODU1_PM_OCI
ODUKSP_STA_INDI
LOOP_ALM
ODU1_PM_SSF
ODU_SNCP_PS

141
OptiX OSN 8800/6800/3800

2 Alarm List
LSR_WILL_DIE
ODU1_PM_TIM
ODU_SNCP_STA_INDI
NO_BD_SOFT
ODU1_TCMn_AIS
OPA_FAIL_INDI
NO_ELABEL
ODU1_TCMn_BDI
OPU1_MSIM
NULL_SEND
ODU1_TCMn_DEG
OPU1_PLM
OCh_FDI
ODU1_TCMn_LCK
OPU2_MSIM
OCh_FDI_O
ODU1_TCMn_LTC
OPU2_PLM
OCh_FDI_P
ODU1_TCMn_OCI
OTU2_AIS
OCh_LOS_P
ODU1_TCMn_SSF
OTU2_BDI
OCh_OCI
ODU1_TCMn_TIM
OTU2_DEG
OCh_SSF
ODU2_PM_AIS
OTU2_LOF
OCh_SSF_O
ODU2_PM_BDI
OTU2_LOM
OCh_SSF_P
ODU2_PM_DEG
OTU2_SSF
ODU0_LOFLOM
ODU2_PM_LCK
OTU2_TIM
ODU0_PM_AIS
ODU2_PM_OCI
OUT_PWR_HIGH
ODU0_PM_BDI
ODU2_PM_SSF
OUT_PWR_LOW
ODU0_PM_DEG
ODU2_PM_TIM
PORT_MODULE_OFFLINE
ODU0_PM_LCK
ODU2_TCMn_AIS
PRBS_LSS
ODU0_PM_OCI
ODU2_TCMn_BDI
R_LOS
ODU0_PM_SSF
ODU2_TCMn_DEG
TD
ODU0_PM_TIM
ODU2_TCMn_LCK
TEMP_OVER
ODU0_TCMn_AIS
ODU2_TCMn_LTC
TEM_HA
ODU0_TCMn_BDI
ODU2_TCMn_OCI
TEM_LA
ODU0_TCMn_DEG
ODU2_TCMn_SSF
TF
ODU0_TCMn_LCK
ODU2_TCMn_TIM
WAVEDATA_MIS
ODU0_TCMn_LTC
ODUFLEX_LOFLOM
WRG_BD_TYPE
TN53NS2(COMP)
Issue 02 (2011-10-31)
BD_STATUS
ODU1_LOFLOM
ODU2_TCMn_TIM
BEFFEC_EXC
ODU1_PM_AIS
ODUKSP_PS
BUS_ERR
ODU1_PM_BDI
ODUKSP_STA_INDI

142
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
ODU1_PM_DEG
ODU_SNCP_PS
HARD_BAD
ODU1_PM_LCK
ODU_SNCP_STA_INDI
HARD_ERR
ODU1_PM_OCI
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_PM_SSF
OPU1_MSIM
IN_PWR_LOW
ODU1_PM_TIM
OPU1_PLM
ODU1_TCMn_AIS
OPU2_MSIM
LOOP_ALM
ODU1_TCMn_BDI
OPU2_PLM
LSR_WILL_DIE
ODU1_TCMn_DEG
OTU2_AIS
NO_BD_SOFT
ODU1_TCMn_LCK
OTU2_BDI
NO_ELABEL
ODU1_TCMn_LTC
OTU2_DEG
NULL_SEND
ODU1_TCMn_OCI
OTU2_LOF
OCh_FDI
ODU1_TCMn_SSF
OTU2_LOM
OCh_FDI_O
ODU1_TCMn_TIM
OTU2_SSF
OCh_FDI_P
ODU2_PM_AIS
OTU2_TIM
OCh_LOS_P
ODU2_PM_BDI
OUT_PWR_HIGH
OCh_OCI
ODU2_PM_DEG
OUT_PWR_LOW
OCh_SSF
ODU2_PM_LCK
PORT_MODULE_OFFLINE
OCh_SSF_O
ODU2_PM_OCI
PRBS_LSS
OCh_SSF_P
ODU2_PM_SSF
R_LOS
ODU0_LOFLOM
ODU2_PM_TIM
TD
ODU0_PM_AIS
ODU2_TCMn_AIS
TEMP_OVER
ODU0_PM_BDI
ODU2_TCMn_BDI
TEM_HA
ODU0_PM_DEG
ODU2_TCMn_DEG
TEM_LA
ODU0_PM_LCK
ODU2_TCMn_LCK
TF
ODU0_PM_OCI
ODU2_TCMn_LTC
WAVEDATA_MIS
ODU0_PM_SSF
ODU2_TCMn_OCI
WRG_BD_TYPE
ODU0_PM_TIM
ODU2_TCMn_SSF
TN52NS2
Issue 02 (2011-10-31)

143
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
BD_STATUS
ODU1_TCM3_LCK
ODU2_TCM3_OCI
BEFFEC_EXC
ODU1_TCM3_LTC
ODU2_TCM3_SSF
BUS_ERR
ODU1_TCM3_OCI
ODU2_TCM3_TIM
COMMUN_FAIL
ODU1_TCM3_SSF
ODU2_TCM4_AIS
HARD_BAD
ODU1_TCM3_TIM
ODU2_TCM4_BDI
HARD_ERR
ODU1_TCM4_AIS
ODU2_TCM4_DEG
IN_PWR_HIGH
ODU1_TCM4_BDI
ODU2_TCM4_LCK
IN_PWR_LOW
ODU1_TCM4_DEG
ODU2_TCM4_LTC
LOOP_ALM
ODU1_TCM4_LCK
ODU2_TCM4_OCI
LSR_FORCE_OPEN
ODU1_TCM4_LTC
ODU2_TCM4_SSF
LSR_WILL_DIE
ODU1_TCM4_OCI
ODU2_TCM4_TIM
NO_BD_SOFT
ODU1_TCM4_SSF
ODU2_TCM5_AIS
NO_ELABEL
ODU1_TCM4_TIM
ODU2_TCM5_BDI
NULL_SEND
ODU1_TCM5_AIS
ODU2_TCM5_DEG
OCh_FDI
ODU1_TCM5_BDI
ODU2_TCM5_LCK
OCh_FDI_O
ODU1_TCM5_DEG
ODU2_TCM5_LTC
OCh_FDI_P
ODU1_TCM5_LCK
ODU2_TCM5_OCI
OCh_LOS_P
ODU1_TCM5_LTC
ODU2_TCM5_SSF
OCh_OCI
ODU1_TCM5_OCI
ODU2_TCM5_TIM
OCh_SSF
ODU1_TCM5_SSF
ODU2_TCM6_AIS
OCh_SSF_O
ODU1_TCM5_TIM
ODU2_TCM6_BDI
OCh_SSF_P
ODU1_TCM6_AIS
ODU2_TCM6_DEG
ODU0_LOFLOM
ODU1_TCM6_BDI
ODU2_TCM6_LCK
ODU0_PM_AIS
ODU1_TCM6_DEG
ODU2_TCM6_LTC
ODU0_PM_BDI
ODU1_TCM6_LCK
ODU2_TCM6_OCI
ODU0_PM_DEG
ODU1_TCM6_LTC
ODU2_TCM6_SSF
ODU0_PM_LCK
ODU1_TCM6_OCI
ODU2_TCM6_TIM
ODU0_PM_OCI
ODU1_TCM6_SSF
ODUKSP_PS
ODU0_PM_SSF
ODU1_TCM6_TIM
ODUKSP_STA_INDI
ODU0_PM_TIM
ODU2_PM_AIS
ODU_SNCP_PS
ODU1_LOFLOM
ODU2_PM_BDI
ODU_SNCP_STA_INDI

144
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_AIS
ODU2_PM_DEG
OPA_FAIL_INDI
ODU1_PM_BDI
ODU2_PM_LCK
OPU1_MSIM
ODU1_PM_DEG
ODU2_PM_OCI
OPU1_PLM
ODU1_PM_LCK
ODU2_PM_SSF
OPU2_MSIM
ODU1_PM_OCI
ODU2_PM_TIM
OPU2_PLM
ODU1_PM_SSF
ODU2_TCM1_AIS
OTU2_AIS
ODU1_PM_TIM
ODU2_TCM1_BDI
OTU2_BDI
ODU1_TCM1_AIS
ODU2_TCM1_DEG
OTU2_DEG
ODU1_TCM1_BDI
ODU2_TCM1_LCK
OTU2_LOF
ODU1_TCM1_DEG
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_LCK
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_LTC
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_OCI
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_SSF
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM1_TIM
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM2_AIS
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM2_BDI
ODU2_TCM2_LCK
R_LOS
ODU1_TCM2_DEG
ODU2_TCM2_LTC
TD
ODU1_TCM2_LCK
ODU2_TCM2_OCI
TEMP_OVER
ODU1_TCM2_LTC
ODU2_TCM2_SSF
TEM_HA
ODU1_TCM2_OCI
ODU2_TCM2_TIM
TEM_LA
ODU1_TCM2_SSF
ODU2_TCM3_AIS
TF
ODU1_TCM2_TIM
ODU2_TCM3_BDI
WAVEDATA_MIS
ODU1_TCM3_AIS
ODU2_TCM3_DEG
WRG_BD_TYPE
ODU1_TCM3_BDI
ODU2_TCM3_LCK
ODU1_TCM3_DEG
ODU2_TCM3_LTC
TN12NS2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM4_AIS
ODU2_TCM3_TIM
BEFFEC_EXC
ODU1_TCM4_BDI
ODU2_TCM4_AIS

145
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
BUS_ERR
ODU1_TCM4_DEG
ODU2_TCM4_BDI
COMMUN_FAIL
ODU1_TCM4_LCK
ODU2_TCM4_DEG
HARD_BAD
ODU1_TCM4_LTC
ODU2_TCM4_LCK
HARD_ERR
ODU1_TCM4_OCI
ODU2_TCM4_LTC
IN_PWR_HIGH
ODU1_TCM4_SSF
ODU2_TCM4_OCI
IN_PWR_LOW
ODU1_TCM4_TIM
ODU2_TCM4_SSF
LOOP_ALM
ODU1_TCM5_AIS
ODU2_TCM4_TIM
LSR_FORCE_OPEN
ODU1_TCM5_BDI
ODU2_TCM5_AIS
LSR_WILL_DIE
ODU1_TCM5_DEG
ODU2_TCM5_BDI
NO_BD_SOFT
ODU1_TCM5_LCK
ODU2_TCM5_DEG
NO_ELABEL
ODU1_TCM5_LTC
ODU2_TCM5_LCK
NULL_SEND
ODU1_TCM5_OCI
ODU2_TCM5_LTC
OCh_FDI
ODU1_TCM5_SSF
ODU2_TCM5_OCI
OCh_FDI_O
ODU1_TCM5_TIM
ODU2_TCM5_SSF
OCh_FDI_P
ODU1_TCM6_AIS
ODU2_TCM5_TIM
OCh_LOS_P
ODU1_TCM6_BDI
ODU2_TCM6_AIS
OCh_OCI
ODU1_TCM6_DEG
ODU2_TCM6_BDI
OCh_SSF
ODU1_TCM6_LCK
ODU2_TCM6_DEG
OCh_SSF_O
ODU1_TCM6_LTC
ODU2_TCM6_LCK
OCh_SSF_P
ODU1_TCM6_OCI
ODU2_TCM6_LTC
ODU1_LOFLOM
ODU1_TCM6_SSF
ODU2_TCM6_OCI
ODU1_PM_AIS
ODU1_TCM6_TIM
ODU2_TCM6_SSF
ODU1_PM_BDI
ODU2_PM_AIS
ODU2_TCM6_TIM
ODU1_PM_DEG
ODU2_PM_BDI
ODUKSP_PS
ODU1_PM_LCK
ODU2_PM_DEG
ODUKSP_STA_INDI
ODU1_PM_OCI
ODU2_PM_LCK
ODU_SNCP_PS
ODU1_PM_SSF
ODU2_PM_OCI
ODU_SNCP_STA_INDI
ODU1_PM_TIM
ODU2_PM_SSF
OPA_FAIL_INDI
ODU1_TCM1_AIS
ODU2_PM_TIM
OPU1_PLM
ODU1_TCM1_BDI
ODU2_TCM1_AIS
OPU2_MSIM
ODU1_TCM1_DEG
ODU2_TCM1_BDI
OPU2_PLM

146
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM1_LCK
ODU2_TCM1_DEG
OTU2_AIS
ODU1_TCM1_LTC
ODU2_TCM1_LCK
OTU2_BDI
ODU1_TCM1_OCI
ODU2_TCM1_LTC
OTU2_DEG
ODU1_TCM1_SSF
ODU2_TCM1_OCI
OTU2_LOF
ODU1_TCM1_TIM
ODU2_TCM1_SSF
OTU2_LOM
ODU1_TCM2_AIS
ODU2_TCM1_TIM
OTU2_SSF
ODU1_TCM2_BDI
ODU2_TCM2_AIS
OTU2_TIM
ODU1_TCM2_DEG
ODU2_TCM2_BDI
OUT_PWR_HIGH
ODU1_TCM2_LCK
ODU2_TCM2_DEG
OUT_PWR_LOW
ODU1_TCM2_LTC
ODU2_TCM2_LCK
PORT_MODULE_OFFLINE
ODU1_TCM2_OCI
ODU2_TCM2_LTC
PRBS_LSS
ODU1_TCM2_SSF
ODU2_TCM2_OCI
R_LOS
ODU1_TCM2_TIM
ODU2_TCM2_SSF
TD
ODU1_TCM3_AIS
ODU2_TCM2_TIM
TEMP_OVER
ODU1_TCM3_BDI
ODU2_TCM3_AIS
TEM_HA
ODU1_TCM3_DEG
ODU2_TCM3_BDI
TEM_LA
ODU1_TCM3_LCK
ODU2_TCM3_DEG
TF
ODU1_TCM3_LTC
ODU2_TCM3_LCK
WAVEDATA_MIS
ODU1_TCM3_OCI
ODU2_TCM3_LTC
WRG_BD_TYPE
ODU1_TCM3_SSF
ODU2_TCM3_OCI
ODU1_TCM3_TIM
ODU2_TCM3_SSF
TN11NS2
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM4_AIS
ODU2_TCM3_SSF
BEFFEC_EXC
ODU1_TCM4_BDI
ODU2_TCM3_TIM
BUS_ERR
ODU1_TCM4_DEG
ODU2_TCM4_AIS
COMMUN_FAIL
ODU1_TCM4_LCK
ODU2_TCM4_BDI
HARD_BAD
ODU1_TCM4_LTC
ODU2_TCM4_DEG
HARD_ERR
ODU1_TCM4_OCI
ODU2_TCM4_LCK
IN_PWR_HIGH
ODU1_TCM4_SSF
ODU2_TCM4_LTC

147
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
IN_PWR_LOW
ODU1_TCM4_TIM
ODU2_TCM4_OCI
LOOP_ALM
ODU1_TCM5_AIS
ODU2_TCM4_SSF
LSR_FORCE_OPEN
ODU1_TCM5_BDI
ODU2_TCM4_TIM
LSR_WILL_DIE
ODU1_TCM5_DEG
ODU2_TCM5_AIS
NO_BD_SOFT
ODU1_TCM5_LCK
ODU2_TCM5_BDI
NO_ELABEL
ODU1_TCM5_LTC
ODU2_TCM5_DEG
NULL_SEND
ODU1_TCM5_OCI
ODU2_TCM5_LCK
OCh_FDI
ODU1_TCM5_SSF
ODU2_TCM5_LTC
OCh_FDI_O
ODU1_TCM5_TIM
ODU2_TCM5_OCI
OCh_FDI_P
ODU1_TCM6_AIS
ODU2_TCM5_SSF
OCh_LOS_P
ODU1_TCM6_BDI
ODU2_TCM5_TIM
OCh_OCI
ODU1_TCM6_DEG
ODU2_TCM6_AIS
OCh_SSF
ODU1_TCM6_LCK
ODU2_TCM6_BDI
OCh_SSF_O
ODU1_TCM6_LTC
ODU2_TCM6_DEG
OCh_SSF_P
ODU1_TCM6_OCI
ODU2_TCM6_LCK
ODU1_LOFLOM
ODU1_TCM6_SSF
ODU2_TCM6_LTC
ODU1_PM_AIS
ODU1_TCM6_TIM
ODU2_TCM6_OCI
ODU1_PM_BDI
ODU2_LOFLOM
ODU2_TCM6_SSF
ODU1_PM_DEG
ODU2_PM_AIS
ODU2_TCM6_TIM
ODU1_PM_LCK
ODU2_PM_BDI
ODUKSP_PS
ODU1_PM_OCI
ODU2_PM_DEG
ODUKSP_STA_INDI
ODU1_PM_SSF
ODU2_PM_LCK
ODU_SNCP_PS
ODU1_PM_TIM
ODU2_PM_OCI
ODU_SNCP_STA_INDI
ODU1_TCM1_AIS
ODU2_PM_SSF
OPA_FAIL_INDI
ODU1_TCM1_BDI
ODU2_PM_TIM
OPU1_PLM
ODU1_TCM1_DEG
ODU2_TCM1_AIS
OPU2_MSIM
ODU1_TCM1_LCK
ODU2_TCM1_BDI
OPU2_PLM
ODU1_TCM1_LTC
ODU2_TCM1_DEG
OTU2_AIS
ODU1_TCM1_OCI
ODU2_TCM1_LCK
OTU2_BDI
ODU1_TCM1_SSF
ODU2_TCM1_LTC
OTU2_DEG
ODU1_TCM1_TIM
ODU2_TCM1_OCI
OTU2_LOF

148
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM2_AIS
ODU2_TCM1_SSF
OTU2_LOM
ODU1_TCM2_BDI
ODU2_TCM1_TIM
OTU2_SSF
ODU1_TCM2_DEG
ODU2_TCM2_AIS
OTU2_TIM
ODU1_TCM2_LCK
ODU2_TCM2_BDI
OUT_PWR_HIGH
ODU1_TCM2_LTC
ODU2_TCM2_DEG
OUT_PWR_LOW
ODU1_TCM2_OCI
ODU2_TCM2_LCK
PORT_MODULE_OFFLINE
ODU1_TCM2_SSF
ODU2_TCM2_LTC
PRBS_LSS
ODU1_TCM2_TIM
ODU2_TCM2_OCI
R_LOS
ODU1_TCM3_AIS
ODU2_TCM2_SSF
TD
ODU1_TCM3_BDI
ODU2_TCM2_TIM
TEMP_OVER
ODU1_TCM3_DEG
ODU2_TCM3_AIS
TEM_HA
ODU1_TCM3_LCK
ODU2_TCM3_BDI
TEM_LA
ODU1_TCM3_LTC
ODU2_TCM3_DEG
TF
ODU1_TCM3_OCI
ODU2_TCM3_LCK
WAVEDATA_MIS
ODU1_TCM3_SSF
ODU2_TCM3_LTC
WRG_BD_TYPE
ODU1_TCM3_TIM
ODU2_TCM3_OCI
2.2.67 NS3 Board Alarm List

TN54NS3
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM5_OCI
ODU3_TCM1_AIS
BEFFEC_EXC
ODU1_TCM5_SSF
ODU3_TCM1_BDI
BUS_ERR
ODU1_TCM5_TIM
ODU3_TCM1_DEG
COMMUN_FAIL
ODU1_TCM6_AIS
ODU3_TCM1_EXC
DCM_INSUFF
ODU1_TCM6_BDI
ODU3_TCM1_LCK
HARD_BAD
ODU1_TCM6_DEG
ODU3_TCM1_LTC
HARD_ERR
ODU1_TCM6_EXC
ODU3_TCM1_OCI
IN_PWR_HIGH
ODU1_TCM6_LCK
ODU3_TCM1_SSF
IN_PWR_LOW
ODU1_TCM6_LTC
ODU3_TCM1_TIM
LOOP_ALM
ODU1_TCM6_OCI
ODU3_TCM2_AIS
LSR_FORCE_OPEN
ODU1_TCM6_SSF
ODU3_TCM2_BDI

149
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
LSR_WILL_DIE
ODU1_TCM6_TIM
ODU3_TCM2_DEG
NO_BD_SOFT
ODU2_LOFLOM
ODU3_TCM2_EXC
NO_ELABEL
ODU2_PM_AIS
ODU3_TCM2_LCK
NULL_SEND
ODU2_PM_BDI
ODU3_TCM2_LTC
OCh_FDI
ODU2_PM_DEG
ODU3_TCM2_OCI
OCh_FDI_O
ODU2_PM_EXC
ODU3_TCM2_SSF
OCh_FDI_P
ODU2_PM_LCK
ODU3_TCM2_TIM
OCh_LOS_P
ODU2_PM_OCI
ODU3_TCM3_AIS
OCh_OCI
ODU2_PM_SSF
ODU3_TCM3_BDI
OCh_SSF
ODU2_PM_TIM
ODU3_TCM3_DEG
OCh_SSF_O
ODU2_TCM1_AIS
ODU3_TCM3_EXC
OCh_SSF_P
ODU2_TCM1_BDI
ODU3_TCM3_LCK
ODU0_LOFLOM
ODU2_TCM1_DEG
ODU3_TCM3_LTC
ODU0_PM_AIS
ODU2_TCM1_EXC
ODU3_TCM3_OCI
ODU0_PM_BDI
ODU2_TCM1_LCK
ODU3_TCM3_SSF
ODU0_PM_DEG
ODU2_TCM1_LTC
ODU3_TCM3_TIM
ODU0_PM_EXC
ODU2_TCM1_OCI
ODU3_TCM4_AIS
ODU0_PM_LCK
ODU2_TCM1_SSF
ODU3_TCM4_BDI
ODU0_PM_OCI
ODU2_TCM1_TIM
ODU3_TCM4_DEG
ODU0_PM_SSF
ODU2_TCM2_AIS
ODU3_TCM4_EXC
ODU0_PM_TIM
ODU2_TCM2_BDI
ODU3_TCM4_LCK
ODU1_LOFLOM
ODU2_TCM2_DEG
ODU3_TCM4_LTC
ODU1_PM_AIS
ODU2_TCM2_EXC
ODU3_TCM4_OCI
ODU1_PM_BDI
ODU2_TCM2_LCK
ODU3_TCM4_SSF
ODU1_PM_DEG
ODU2_TCM2_LTC
ODU3_TCM4_TIM
ODU1_PM_EXC
ODU2_TCM2_OCI
ODU3_TCM5_AIS
ODU1_PM_LCK
ODU2_TCM2_SSF
ODU3_TCM5_BDI
ODU1_PM_OCI
ODU2_TCM2_TIM
ODU3_TCM5_DEG
ODU1_PM_SSF
ODU2_TCM3_AIS
ODU3_TCM5_EXC
ODU1_PM_TIM
ODU2_TCM3_BDI
ODU3_TCM5_LCK
ODU1_TCM1_AIS
ODU2_TCM3_DEG
ODU3_TCM5_LTC

150
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
ODU1_TCM1_BDI
ODU2_TCM3_EXC
ODU3_TCM5_OCI
ODU1_TCM1_DEG
ODU2_TCM3_LCK
ODU3_TCM5_SSF
ODU1_TCM1_EXC
ODU2_TCM3_LTC
ODU3_TCM5_TIM
ODU1_TCM1_LCK
ODU2_TCM3_OCI
ODU3_TCM6_AIS
ODU1_TCM1_LTC
ODU2_TCM3_SSF
ODU3_TCM6_BDI
ODU1_TCM1_OCI
ODU2_TCM3_TIM
ODU3_TCM6_DEG
ODU1_TCM1_SSF
ODU2_TCM4_AIS
ODU3_TCM6_EXC
ODU1_TCM1_TIM
ODU2_TCM4_BDI
ODU3_TCM6_LCK
ODU1_TCM2_AIS
ODU2_TCM4_DEG
ODU3_TCM6_LTC
ODU1_TCM2_BDI
ODU2_TCM4_EXC
ODU3_TCM6_OCI
ODU1_TCM2_DEG
ODU2_TCM4_LCK
ODU3_TCM6_SSF
ODU1_TCM2_EXC
ODU2_TCM4_LTC
ODU3_TCM6_TIM
ODU1_TCM2_LCK
ODU2_TCM4_OCI
ODUKSP_PS
ODU1_TCM2_LTC
ODU2_TCM4_SSF
ODUKSP_STA_INDI
ODU1_TCM2_OCI
ODU2_TCM4_TIM
ODU_SNCP_PS
ODU1_TCM2_SSF
ODU2_TCM5_AIS
ODU_SNCP_STA_INDI
ODU1_TCM2_TIM
ODU2_TCM5_BDI
OPA_FAIL_INDI
ODU1_TCM3_AIS
ODU2_TCM5_DEG
OPU1_MSIM
ODU1_TCM3_BDI
ODU2_TCM5_EXC
OPU1_PLM
ODU1_TCM3_DEG
ODU2_TCM5_LCK
OPU3_MSIM
ODU1_TCM3_EXC
ODU2_TCM5_LTC
OPU3_PLM
ODU1_TCM3_LCK
ODU2_TCM5_OCI
OTU3_AIS
ODU1_TCM3_LTC
ODU2_TCM5_SSF
OTU3_BDI
ODU1_TCM3_OCI
ODU2_TCM5_TIM
OTU3_DEG
ODU1_TCM3_SSF
ODU2_TCM6_AIS
OTU3_EXC
ODU1_TCM3_TIM
ODU2_TCM6_BDI
OTU3_LOF
ODU1_TCM4_AIS
ODU2_TCM6_DEG
OTU3_LOM
ODU1_TCM4_BDI
ODU2_TCM6_EXC
OTU3_SSF
ODU1_TCM4_DEG
ODU2_TCM6_LCK
OTU3_TIM
ODU1_TCM4_EXC
ODU2_TCM6_LTC
OUT_PWR_HIGH
ODU1_TCM4_LCK
ODU2_TCM6_OCI
OUT_PWR_LOW

151
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM4_LTC
ODU2_TCM6_SSF
PORT_MODULE_OFFLINE
ODU1_TCM4_OCI
ODU2_TCM6_TIM
PRBS_LSS
ODU1_TCM4_SSF
ODU3_PM_AIS
R_LOS
ODU1_TCM4_TIM
ODU3_PM_BDI
TD
ODU1_TCM5_AIS
ODU3_PM_DEG
TEMP_OVER
ODU1_TCM5_BDI
ODU3_PM_EXC
TEM_HA
ODU1_TCM5_DEG
ODU3_PM_LCK
TEM_LA
ODU1_TCM5_EXC
ODU3_PM_OCI
TF
ODU1_TCM5_LCK
ODU3_PM_SSF
WRG_BD_TYPE
ODU1_TCM5_LTC
ODU3_PM_TIM
TN52NS3
Issue 02 (2011-10-31)
BD_STATUS
ODU1_TCM5_SSF
ODU3_TCM1_LCK
BEFFEC_EXC
ODU1_TCM5_TIM
ODU3_TCM1_LTC
BUS_ERR
ODU1_TCM6_AIS
ODU3_TCM1_OCI
COMMUN_FAIL
ODU1_TCM6_BDI
ODU3_TCM1_SSF
DCM_INSUFF
ODU1_TCM6_DEG
ODU3_TCM1_TIM
HARD_BAD
ODU1_TCM6_LCK
ODU3_TCM2_AIS
HARD_ERR
ODU1_TCM6_LTC
ODU3_TCM2_BDI
IN_PWR_HIGH
ODU1_TCM6_OCI
ODU3_TCM2_DEG
IN_PWR_LOW
ODU1_TCM6_SSF
ODU3_TCM2_LCK
LOOP_ALM
ODU1_TCM6_TIM
ODU3_TCM2_LTC
LSR_FORCE_OPEN
ODU2_LOFLOM
ODU3_TCM2_OCI
LSR_WILL_DIE
ODU2_PM_AIS
ODU3_TCM2_SSF
NO_BD_SOFT
ODU2_PM_BDI
ODU3_TCM2_TIM
NO_ELABEL
ODU2_PM_DEG
ODU3_TCM3_AIS
NULL_SEND
ODU2_PM_LCK
ODU3_TCM3_BDI
OCh_FDI
ODU2_PM_OCI
ODU3_TCM3_DEG
OCh_FDI_O
ODU2_PM_SSF
ODU3_TCM3_LCK
OCh_FDI_P
ODU2_PM_TIM
ODU3_TCM3_LTC

152
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
OCh_LOS_P
ODU2_TCM1_AIS
ODU3_TCM3_OCI
OCh_OCI
ODU2_TCM1_BDI
ODU3_TCM3_SSF
OCh_SSF
ODU2_TCM1_DEG
ODU3_TCM3_TIM
OCh_SSF_O
ODU2_TCM1_LCK
ODU3_TCM4_AIS
OCh_SSF_P
ODU2_TCM1_LTC
ODU3_TCM4_BDI
ODU0_LOFLOM
ODU2_TCM1_OCI
ODU3_TCM4_DEG
ODU0_PM_AIS
ODU2_TCM1_SSF
ODU3_TCM4_LCK
ODU0_PM_BDI
ODU2_TCM1_TIM
ODU3_TCM4_LTC
ODU0_PM_DEG
ODU2_TCM2_AIS
ODU3_TCM4_OCI
ODU0_PM_LCK
ODU2_TCM2_BDI
ODU3_TCM4_SSF
ODU0_PM_OCI
ODU2_TCM2_DEG
ODU3_TCM4_TIM
ODU0_PM_SSF
ODU2_TCM2_LCK
ODU3_TCM5_AIS
ODU0_PM_TIM
ODU2_TCM2_LTC
ODU3_TCM5_BDI
ODU1_LOFLOM
ODU2_TCM2_OCI
ODU3_TCM5_DEG
ODU1_PM_AIS
ODU2_TCM2_SSF
ODU3_TCM5_LCK
ODU1_PM_BDI
ODU2_TCM2_TIM
ODU3_TCM5_LTC
ODU1_PM_DEG
ODU2_TCM3_AIS
ODU3_TCM5_OCI
ODU1_PM_LCK
ODU2_TCM3_BDI
ODU3_TCM5_SSF
ODU1_PM_OCI
ODU2_TCM3_DEG
ODU3_TCM5_TIM
ODU1_PM_SSF
ODU2_TCM3_LCK
ODU3_TCM6_AIS
ODU1_PM_TIM
ODU2_TCM3_LTC
ODU3_TCM6_BDI
ODU1_TCM1_AIS
ODU2_TCM3_OCI
ODU3_TCM6_DEG
ODU1_TCM1_BDI
ODU2_TCM3_SSF
ODU3_TCM6_LCK
ODU1_TCM1_DEG
ODU2_TCM3_TIM
ODU3_TCM6_LTC
ODU1_TCM1_LCK
ODU2_TCM4_AIS
ODU3_TCM6_OCI
ODU1_TCM1_LTC
ODU2_TCM4_BDI
ODU3_TCM6_SSF
ODU1_TCM1_OCI
ODU2_TCM4_DEG
ODU3_TCM6_TIM
ODU1_TCM1_SSF
ODU2_TCM4_LCK
ODUKSP_PS
ODU1_TCM1_TIM
ODU2_TCM4_LTC
ODUKSP_STA_INDI
ODU1_TCM2_AIS
ODU2_TCM4_OCI
ODU_SNCP_PS
ODU1_TCM2_BDI
ODU2_TCM4_SSF
ODU_SNCP_STA_INDI

153
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM2_DEG
ODU2_TCM4_TIM
OPA_FAIL_INDI
ODU1_TCM2_LCK
ODU2_TCM5_AIS
OPU1_MSIM
ODU1_TCM2_LTC
ODU2_TCM5_BDI
OPU1_PLM
ODU1_TCM2_OCI
ODU2_TCM5_DEG
OPU2_MSIM
ODU1_TCM2_SSF
ODU2_TCM5_LCK
OPU2_PLM
ODU1_TCM2_TIM
ODU2_TCM5_LTC
OPU3_MSIM
ODU1_TCM3_AIS
ODU2_TCM5_OCI
OPU3_PLM
ODU1_TCM3_BDI
ODU2_TCM5_SSF
OTU3_AIS
ODU1_TCM3_DEG
ODU2_TCM5_TIM
OTU3_BDI
ODU1_TCM3_LCK
ODU2_TCM6_AIS
OTU3_DEG
ODU1_TCM3_LTC
ODU2_TCM6_BDI
OTU3_EXC
ODU1_TCM3_OCI
ODU2_TCM6_DEG
OTU3_LOF
ODU1_TCM3_SSF
ODU2_TCM6_LCK
OTU3_LOM
ODU1_TCM3_TIM
ODU2_TCM6_LTC
OTU3_SSF
ODU1_TCM4_AIS
ODU2_TCM6_OCI
OTU3_TIM
ODU1_TCM4_BDI
ODU2_TCM6_SSF
OUT_PWR_HIGH
ODU1_TCM4_DEG
ODU2_TCM6_TIM
OUT_PWR_LOW
ODU1_TCM4_LCK
ODU3_PM_AIS
PORT_MODULE_OFFLINE
ODU1_TCM4_LTC
ODU3_PM_BDI
PRBS_LSS
ODU1_TCM4_OCI
ODU3_PM_DEG
R_LOS
ODU1_TCM4_SSF
ODU3_PM_EXC
TD
ODU1_TCM4_TIM
ODU3_PM_LCK
TEMP_OVER
ODU1_TCM5_AIS
ODU3_PM_OCI
TEM_HA
ODU1_TCM5_BDI
ODU3_PM_SSF
TEM_LA
ODU1_TCM5_DEG
ODU3_PM_TIM
TF
ODU1_TCM5_LCK
ODU3_TCM1_AIS
WAVEDATA_MIS
ODU1_TCM5_LTC
ODU3_TCM1_BDI
WRG_BD_TYPE
ODU1_TCM5_OCI
ODU3_TCM1_DEG
TN11NS3
Issue 02 (2011-10-31)

154
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
BD_STATUS
ODU3_PM_TIM
ODU3_TCM5_LCK
BEFFEC_EXC
ODU3_TCM1_AIS
ODU3_TCM5_LTC
BUS_ERR
ODU3_TCM1_BDI
ODU3_TCM5_OCI
COMMUN_FAIL
ODU3_TCM1_DEG
ODU3_TCM5_SSF
DCM_INSUFF
ODU3_TCM1_LCK
ODU3_TCM5_TIM
HARD_BAD
ODU3_TCM1_LTC
ODU3_TCM6_AIS
HARD_ERR
ODU3_TCM1_OCI
ODU3_TCM6_BDI
IN_PWR_HIGH
ODU3_TCM1_SSF
ODU3_TCM6_DEG
IN_PWR_LOW
ODU3_TCM1_TIM
ODU3_TCM6_LCK
LOOP_ALM
ODU3_TCM2_AIS
ODU3_TCM6_LTC
LSR_FORCE_OPEN
ODU3_TCM2_BDI
ODU3_TCM6_OCI
LSR_WILL_DIE
ODU3_TCM2_DEG
ODU3_TCM6_SSF
NO_BD_SOFT
ODU3_TCM2_LCK
ODU3_TCM6_TIM
NO_ELABEL
ODU3_TCM2_LTC
ODU_SNCP_PS
OCh_FDI
ODU3_TCM2_OCI
ODU_SNCP_STA_INDI
OCh_FDI_O
ODU3_TCM2_SSF
OPA_FAIL_INDI
OCh_FDI_P
ODU3_TCM2_TIM
OPU2_PLM
OCh_LOS_P
ODU3_TCM3_AIS
OPU3_MSIM
OCh_OCI
ODU3_TCM3_BDI
OPU3_PLM
OCh_SSF
ODU3_TCM3_DEG
OTU3_AIS
OCh_SSF_O
ODU3_TCM3_LCK
OTU3_BDI
OCh_SSF_P
ODU3_TCM3_LTC
OTU3_DEG
ODU2_LOFLOM
ODU3_TCM3_OCI
OTU3_LOF
ODU2_PM_AIS
ODU3_TCM3_SSF
OTU3_LOM
ODU2_PM_BDI
ODU3_TCM3_TIM
OTU3_SSF
ODU2_PM_DEG
ODU3_TCM4_AIS
OTU3_TIM
ODU2_PM_LCK
ODU3_TCM4_BDI
OUT_PWR_HIGH
ODU2_PM_OCI
ODU3_TCM4_DEG
OUT_PWR_LOW
ODU2_PM_SSF
ODU3_TCM4_LCK
PORT_MODULE_OFFLINE
ODU2_PM_TIM
ODU3_TCM4_LTC
R_LOS
ODU3_PM_AIS
ODU3_TCM4_OCI
TD

155
OptiX OSN 8800/6800/3800

2 Alarm List
ODU3_PM_BDI
ODU3_TCM4_SSF
TEMP_OVER
ODU3_PM_DEG
ODU3_TCM4_TIM
TF
ODU3_PM_LCK
ODU3_TCM5_AIS
WAVEDATA_MIS
ODU3_PM_OCI
ODU3_TCM5_BDI
WRG_BD_TYPE
ODU3_PM_SSF
ODU3_TCM5_DEG
NOTE
TCM6.
2.2.68 OAU1 Board Alarm List

TN13OAU1
BD_STATUS
NO_BD_SOFT
SPAN_LOSS_LOW
COMMUN_FAIL
NO_ELABEL
SUM_INPWR_HI
GAINDATA_MIS
OA_LOW_GAIN
SUM_INPWR_LOW
HARD_BAD
OPA_FAIL_INDI
TEMP_OVER
HARD_ERR
PUMP_COOL_EXC
VOA_ADJUST_FAIL
LASER_HAZARD_WA
RNING
PUM_BCM_ALM
WRG_BD_TYPE
MUT_LOS
PUM_TEM_ALM
NO_BD_PARA
SPAN_LOSS_HIGH
TN12OAU1
Issue 02 (2011-10-31)
BD_STATUS
NO_BD_SOFT
SPAN_LOSS_LOW
COMMUN_FAIL
NO_ELABEL
SUM_INPWR_HI
GAINDATA_MIS
OA_LOW_GAIN
SUM_INPWR_LOW
HARD_BAD
OPA_FAIL_INDI
TEMP_OVER
HARD_ERR
PUMP_COOL_EXC
VOA_ADJUST_FAIL
PUM_BCM_ALM
WRG_BD_TYPE
MUT_LOS
PUM_TEM_ALM
NO_BD_PARA
SPAN_LOSS_HIGH

156
OptiX OSN 8800/6800/3800

2 Alarm List
TN11OAU1
BD_STATUS
NO_BD_PARA
SPAN_LOSS_HIGH
COMMUN_FAIL
NO_BD_SOFT
SPAN_LOSS_LOW
DSP_LOAD_FAIL
NO_ELABEL
SUM_INPWR_HI
GAINDATA_MIS
OA_LOW_GAIN
SUM_INPWR_LOW
HARD_BAD
OPA_FAIL_INDI
TEMP_OVER
HARD_ERR
PUMP_COOL_EXC
VOA_ADJUST_FAIL
PUM_BCM_ALM
WRG_BD_TYPE
MUT_LOS
PUM_TEM_ALM
2.2.69 OBU1 Board Alarm List

TN12OBU1
BD_STATUS
NO_BD_PARA
PUM_TEM_ALM
COMMUN_FAIL
NO_BD_SOFT
SPAN_LOSS_HIGH
GAINDATA_MIS
NO_ELABEL
SPAN_LOSS_LOW
HARD_BAD
OA_LOW_GAIN
SUM_INPWR_HI
HARD_ERR
OPA_FAIL_INDI
SUM_INPWR_LOW
PUMP_COOL_EXC
TEMP_OVER
MUT_LOS
PUM_BCM_ALM
WRG_BD_TYPE
BD_STATUS
NO_BD_PARA
SPAN_LOSS_HIGH
COMMUN_FAIL
NO_BD_SOFT
SPAN_LOSS_LOW
DSP_LOAD_FAIL
NO_ELABEL
SUM_INPWR_HI
GAINDATA_MIS
OA_LOW_GAIN
SUM_INPWR_LOW
HARD_BAD
OPA_FAIL_INDI
TEMP_OVER
HARD_ERR
PUMP_COOL_EXC
WRG_BD_TYPE
PUM_BCM_ALM
TN11OBU1
Issue 02 (2011-10-31)

157
OptiX OSN 8800/6800/3800

MUT_LOS
2 Alarm List
PUM_TEM_ALM
2.2.70 OBU2 Board Alarm List

TN12OBU2
BD_STATUS
NO_BD_PARA
PUM_TEM_ALM
COMMUN_FAIL
NO_BD_SOFT
SPAN_LOSS_HIGH
GAINDATA_MIS
NO_ELABEL
SPAN_LOSS_LOW
HARD_BAD
OA_LOW_GAIN
SUM_INPWR_HI
HARD_ERR
OPA_FAIL_INDI
SUM_INPWR_LOW
PUMP_COOL_EXC
TEMP_OVER
MUT_LOS
PUM_BCM_ALM
WRG_BD_TYPE
BD_STATUS
NO_BD_PARA
SPAN_LOSS_HIGH
COMMUN_FAIL
NO_BD_SOFT
SPAN_LOSS_LOW
DSP_LOAD_FAIL
NO_ELABEL
SUM_INPWR_HI
GAINDATA_MIS
OA_LOW_GAIN
SUM_INPWR_LOW
HARD_BAD
OPA_FAIL_INDI
TEMP_OVER
HARD_ERR
PUMP_COOL_EXC
WRG_BD_TYPE
PUM_BCM_ALM
MUT_LOS
PUM_TEM_ALM
TN11OBU2
2.2.71 OLP Board Alarm List

TN11OLP
Issue 02 (2011-10-31)
BD_STATUS
NO_BD_PARA
OCh_SSF_O
CLIENT_PORT_PS
NO_BD_SOFT
OCh_SSF_P
NO_ELABEL

OLP_PS
158
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
OCh_FDI
OLP_STA_INDI
HARD_BAD
OCh_FDI_O
OPA_FAIL_INDI
HARD_ERR
OCh_FDI_P
POWER_DIFF_OVER
INTRA_OTU_PS
OCh_LOS_P
R_LOS
INTRA_OTU_STA_INDI
OCh_OCI
TEMP_OVER
MUT_LOS
OCh_SSF
WRG_BD_TYPE
BD_STATUS
NO_BD_PARA
OLP_PS
CLIENT_PORT_PS
OCh_FDI
OLP_STA_INDI
OCh_FDI_O
OPA_FAIL_INDI
COMMUN_FAIL
OCh_FDI_P
POWER_DIFF_OVER
HARD_BAD
OCh_LOS_P
R_LOS
HARD_ERR
OCh_OCI
TEMP_OVER
INTRA_OTU_PS
OCh_SSF
WRG_BD_TYPE
INTRA_OTU_STA_INDI
OCh_SSF_O
MUT_LOS
OCh_SSF_P
TN12OLP
2.2.72 OPM8 Board Alarm List
Issue 02 (2011-10-31)
APE_ADJUST_FAIL
HARD_BAD
NO_ELABEL
APE_ADJUST_PEND
HARD_ERR
PORTSWITCH_FAIL
BD_STATUS
L
TEMP_OVER
CHAN_ADD
MOD_COM_FAIL
WRG_BD_TYPE
CHAN_LOS
NO_BD_PARA
WAVE_ADD_ABN
COMMUN_FAIL
NO_BD_SOFT
WAVE_DROP_ABN

159
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.73 PIU Board Alarm List

BD_STATUS
THUNDERALM
WRG_BD_TYPE
POWER_FAIL
2.2.74 PTQX Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_TCM3_LTC
ODU2_TCM4_DEG
B1_SD
ODU1_TCM3_OCI
ODU2_TCM4_LCK
BD_STATUS
ODU1_TCM3_SSF
ODU2_TCM4_LTC
BEFFEC_EXC
ODU1_TCM3_TIM
ODU2_TCM4_OCI
BUS_ERR
ODU1_TCM4_AIS
ODU2_TCM4_SSF
CLIENT_PORT_PS
ODU1_TCM4_BDI
ODU2_TCM4_TIM
ODU1_TCM4_DEG
ODU2_TCM5_AIS
ODU1_TCM4_LCK
ODU2_TCM5_BDI
COMMUN_FAIL
ODU1_TCM4_LTC
ODU2_TCM5_DEG
HARD_BAD
ODU1_TCM4_OCI
ODU2_TCM5_LCK
HARD_ERR
ODU1_TCM4_SSF
ODU2_TCM5_LTC
IN_PWR_HIGH
ODU1_TCM4_TIM
ODU2_TCM5_OCI
IN_PWR_LOW
ODU1_TCM5_AIS
ODU2_TCM5_SSF
J0_MM
ODU1_TCM5_BDI
ODU2_TCM5_TIM
ODU1_TCM5_DEG
ODU2_TCM6_AIS
LOCAL_FAULT
ODU1_TCM5_LCK
ODU2_TCM6_BDI
LOOP_ALM
ODU1_TCM5_LTC
ODU2_TCM6_DEG
LPT_ACTIVE
ODU1_TCM5_OCI
ODU2_TCM6_LCK
LSR_FORCE_OPEN
ODU1_TCM5_SSF
ODU2_TCM6_LTC
LSR_INVALID
ODU1_TCM5_TIM
ODU2_TCM6_OCI
LSR_WILL_DIE
ODU1_TCM6_AIS
ODU2_TCM6_SSF
MUT_LOS
ODU1_TCM6_BDI
ODU2_TCM6_TIM
NO_BD_PARA
ODU1_TCM6_DEG
ODU_SNCP_PS
NO_BD_SOFT
ODU1_TCM6_LCK
ODU_SNCP_STA_INDI

160
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
NO_ELABEL
ODU1_TCM6_LTC
OMS_BDI
NULL_SEND
ODU1_TCM6_OCI
OMS_BDI_O
OCh_FDI
ODU1_TCM6_SSF
OMS_BDI_P
OCh_FDI_O
ODU1_TCM6_TIM
OMS_FDI
OCh_FDI_P
ODU2_LOFLOM
OMS_FDI_O
OCh_LOS_P
ODU2_PM_AIS
OMS_FDI_P
OCh_OCI
ODU2_PM_BDI
OMS_LOS_P
OCh_SSF
ODU2_PM_DEG
OMS_SSF
OCh_SSF_O
ODU2_PM_LCK
OMS_SSF_O
OCh_SSF_P
ODU2_PM_OCI
OMS_SSF_P
ODU1_LOFLOM
ODU2_PM_SSF
OPA_FAIL_INDI
ODU1_PM_AIS
ODU2_PM_TIM
OPU2_MSIM
ODU1_PM_BDI
ODU2_TCM1_AIS
OPU2_PLM
ODU1_PM_DEG
ODU2_TCM1_BDI
OTU2_AIS
ODU1_PM_LCK
ODU2_TCM1_DEG
OTU2_BDI
ODU1_PM_OCI
ODU2_TCM1_LCK
OTU2_DEG
ODU1_PM_SSF
ODU2_TCM1_LTC
OTU2_LOF
ODU1_PM_TIM
ODU2_TCM1_OCI
OTU2_LOM
ODU1_TCM1_AIS
ODU2_TCM1_SSF
OTU2_SSF
ODU1_TCM1_BDI
ODU2_TCM1_TIM
OTU2_TIM
ODU1_TCM1_DEG
ODU2_TCM2_AIS
OUT_PWR_HIGH
ODU1_TCM1_LCK
ODU2_TCM2_BDI
OUT_PWR_LOW
ODU1_TCM1_LTC
ODU2_TCM2_DEG
PORT_MODULE_OFFLINE
ODU1_TCM1_OCI
ODU2_TCM2_LCK
PRBS_LSS
ODU1_TCM1_SSF
ODU2_TCM2_LTC
REMOTE_FAULT
ODU1_TCM1_TIM
ODU2_TCM2_OCI
REM_SD
ODU1_TCM2_AIS
ODU2_TCM2_SSF
REM_SF
ODU1_TCM2_BDI
ODU2_TCM2_TIM
R_LOC
ODU1_TCM2_DEG
ODU2_TCM3_AIS
R_LOF
ODU1_TCM2_LCK
ODU2_TCM3_BDI
R_LOS

161
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM2_LTC
ODU2_TCM3_DEG
TD
ODU1_TCM2_OCI
ODU2_TCM3_LCK
TEMP_OVER
ODU1_TCM2_SSF
ODU2_TCM3_LTC
TEM_HA
ODU1_TCM2_TIM
ODU2_TCM3_OCI
TEM_LA
ODU1_TCM3_AIS
ODU2_TCM3_SSF
TF
ODU1_TCM3_BDI
ODU2_TCM3_TIM
WAVEDATA_MIS
ODU1_TCM3_DEG
ODU2_TCM4_AIS
WRG_BD_TYPE
ODU1_TCM3_LCK
ODU2_TCM4_BDI
BD_STATUS
OMS_BDI
OMS_SSF_O
COMMUN_FAIL
OMS_BDI_O
OMS_SSF_P
HARD_BAD
OMS_BDI_P
OPA_FAIL_INDI
HARD_ERR
OMS_FDI
SUM_INPWR_HI
MODULEFILE_UPDATE_F
AIL
OMS_FDI_O
SUM_INPWR_LOW
MODULE_ADJUST_FAIL
OMS_FDI_P
TEMP_OVER
MOD_COM_FAIL
OMS_LOS_P
WAVEDATA_MIS
MUT_LOS
OMS_SSF
WRG_BD_TYPE
2.2.75 RDU9 Board Alarm List
2.2.76 RMU9 Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
OMS_BDI
OMS_SSF_P
COMMUN_FAIL
OMS_BDI_O
OPA_FAIL_INDI
HARD_BAD
OMS_BDI_P
SUM_INPWR_HI
HARD_ERR
OMS_FDI
SUM_INPWR_LOW
MODULE_TEMP_OVE
R
OMS_FDI_O
TEMP_OVER
MUT_LOS
OMS_FDI_P
VOADATA_MIS
NO_BD_PARA
OMS_LOS_P
WAVEDATA_MIS

162
OptiX OSN 8800/6800/3800

2 Alarm List
NO_BD_SOFT
OMS_SSF
NO_ELABEL
OMS_SSF_O
WRG_BD_TYPE
2.2.77 ROAM Board Alarm List

BD_STATUS
NO_ELABEL
OMS_SSF_O
COMMUN_FAIL
OMS_BDI
OMS_SSF_P
HARD_BAD
OMS_BDI_O
OPA_FAIL_INDI
HARD_ERR
OMS_BDI_P
SUM_INPWR_HI
MODULEFILE_UPDATE_F
AIL
OMS_FDI
SUM_INPWR_LOW
MODULE_ADJUST_FAIL
OMS_FDI_O
TEMP_OVER
MOD_COM_FAIL
OMS_FDI_P
WAVEDATA_MIS
MUT_LOS
OMS_LOS_P
WRG_BD_TYPE
NO_BD_SOFT
OMS_SSF
2.2.78 SBM2 Board Alarm List

BD_STATUS
WAVEDATA_MIS
WRG_BD_TYPE
OPA_FAIL_INDI
2.2.79 SC1 Board Alarm List
Issue 02 (2011-10-31)
ALM_HANGUP
LOOP_ALM
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
R_LOF
COMMUN_FAIL
NO_BD_PARA
R_SLIP
CRC4_CROSSTR
NO_BD_SOFT
SCC_LOC
HARD_BAD
NO_ELABEL
TEMP_OVER
HARD_ERR
OSC_LOS
TF
IN_PWR_HIGH
OSC_RDI
T_SLIP
IN_PWR_LOW
OUT_PWR_HIGH
WRG_BD_TYPE

163
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.80 SC2 Board Alarm List

ALM_HANGUP
LOOP_ALM
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
R_LOF
COMMUN_FAIL
NO_BD_PARA
R_SLIP
CRC4_CROSSTR
NO_BD_SOFT
SCC_LOC
HARD_BAD
NO_ELABEL
TEMP_OVER
HARD_ERR
OSC_LOS
TF
IN_PWR_HIGH
OSC_RDI
T_SLIP
IN_PWR_LOW
OUT_PWR_HIGH
WRG_BD_TYPE
2.2.81 SCC Board Alarm List

TN51SCC
LCS_EXPIRED
SUBRACK_ID_CONFLICT
ALC_WAIT_ADJUST
LCS_FILE_NOT_EXIST
SUBRACK_ID_MISMATCH
APS_FAIL
MS_APS_INDI_EX
SUBRACK_LOOP
APS_INDI
NEBD_XC_DIF
SUBRACK_TYPE_MI
SMATCH
APS_MANUAL_STOP
NESF_LOST
SWDL_ACTIVATED_
TIMEOUT
BD_NOT_INSTALLED
NESTATE_INSTALL
SWDL_AUTOMATCH
_INH
BD_STATUS
NODEID_MM
SWDL_BD_EXCLUDE
BOOTROM_BAD
NTP_SYNC_FAIL
SWDL_CHGMNG_NO
MATCH
COMMUN_FAIL
PATCH_ACT_TIMEOUT
SWDL_COMMIT_FAI
L
CPC_NODE_ID_ERR
PATCH_DEACT_TIMEOUT
SWDL_INPROCESS
DBMS_ABNORMAL
PATCH_PKGERR
SWDL_NEPKGCHEC
K
DBMS_ERROR
POWER_FAIL
SWDL_PKGVER_MM
DBMS_PROTECT_MOD
E
RTC_FAIL
SWDL_PKG_NOBDSOFT
ALC_ADJUST_FAIL
Issue 02 (2011-10-31)

164
OptiX OSN 8800/6800/3800

2 Alarm List
DB_RESTORE_FAIL
SECU_ALM
SWDL_ROLLBACK_F
AIL
FEATURE_WITHOUT_
LICENSE
SEC_RADIUS_FAIL
SYNC_DISABLE
HARD_BAD
SERVICE_CAPACITY_EXCEE
D_LICENSE
SYNC_FAIL
HARD_ERR
SERVICE_TYPE_EXCEED_LICENSE
SYSLOG_COMM_FAI
L
HSC_UNAVAIL
SHELF_AREA_POWER_OVER
SYSPARA_CFDB_NOSAME
K1_K2_M
SNCP_FAIL
TEMP_OVER
K2_M
STORM_CUR_QUENUM_OVE
R
WRG_BD_TYPE
LCS_DAYS_OF_GRAC
E
SUBRACK_COMM_PS
XC_UNSWITCH
TN11SCC
LCS_FILE_NOT_EXIST
SWDL_ACTIVATED_TI
MEOUT
NESF_LOST
SWDL_AUTOMATCH_I
NH
BD_NOT_INSTALLED
NESTATE_INSTALL
SWDL_BD_EXCLUDE
BD_STATUS
NTP_SYNC_FAIL
SWDL_CHGMNG_NOMATCH
BOOTROM_BAD
PATCH_ACT_TIMEOUT
SWDL_COMMIT_FAIL
COMMUN_FAIL
PATCH_DEACT_TIMEOUT
SWDL_INPROCESS
DBMS_ABNORMAL
PATCH_PKGERR
SWDL_NEPKGCHECK
DBMS_ERROR
POWER_FAIL
SWDL_PKGVER_MM
DBMS_PROTECT_MODE
RTC_FAIL
SWDL_PKG_NOBDSOFT
DB_RESTORE_FAIL
SECU_ALM
SWDL_ROLLBACK_FAI
L
SEC_RADIUS_FAIL
SYNC_DISABLE
HARD_BAD
STORM_CUR_QUENUM_
OVER
SYNC_FAIL
ALC_ADJUST_FAIL
ALC_WAIT_ADJUST
Issue 02 (2011-10-31)

165
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_ERR
SUBRACK_ID_CONFLICT
SYSLOG_COMM_FAIL
HSC_UNAVAIL
SUBRACK_ID_MISMATCH
SYSPARA_CFDB_NOSAME
LCS_DAYS_OF_GRACE
SUBRACK_LOOP
TEMP_OVER
LCS_EXPIRED
WRG_BD_TYPE
TN21SCC
LCS_EXPIRED
SWDL_ACTIVATED_TI
MEOUT
LCS_FILE_NOT_EXIST
SWDL_AUTOMATCH_I
NH
BD_NOT_INSTALLED
NESF_LOST
SWDL_BD_EXCLUDE
BD_STATUS
NESTATE_INSTALL
SWDL_CHGMNG_NOMATCH
BOOTROM_BAD
NTP_SYNC_FAIL
SWDL_COMMIT_FAIL
COMMUN_FAIL
PATCH_ACT_TIMEOUT
SWDL_INPROCESS
CPC_NODE_ID_ERR
PATCH_DEACT_TIMEOUT
SWDL_NEPKGCHECK
DBMS_ABNORMAL
PATCH_PKGERR
SWDL_PKGVER_MM
DBMS_ERROR
POWER_FAIL
SWDL_PKG_NOBDSOFT
DBMS_PROTECT_MODE
RTC_FAIL
SWDL_ROLLBACK_FAI
L
DB_RESTORE_FAIL
SECU_ALM
SYNC_DISABLE
SEC_RADIUS_FAIL
SYNC_FAIL
HARD_BAD
STORM_CUR_QUENUM_
OVER
SYSLOG_COMM_FAIL
HARD_ERR
SUBRACK_ID_MISMATCH
SYSPARA_CFDB_NOSAME
HSC_UNAVAIL
SUBRACK_LOOP
TEMP_OVER
LCS_DAYS_OF_GRACE
WRG_BD_TYPE
ALC_ADJUST_FAIL
ALC_WAIT_ADJUST
TN22SCC
Issue 02 (2011-10-31)

166
OptiX OSN 8800/6800/3800

2 Alarm List
ALC_ADJUST_FAIL
LCS_DAYS_OF_GRACE
SWDL_AUTOMATCH_I
NH
ALC_WAIT_ADJUST
LCS_EXPIRED
SWDL_BD_EXCLUDE
LCS_FILE_NOT_EXIST
SWDL_CHGMNG_NOMATCH
BD_STATUS
NESF_LOST
SWDL_COMMIT_FAIL
BOOTROM_BAD
NESTATE_INSTALL
SWDL_INPROCESS
COMMUN_FAIL
NTP_SYNC_FAIL
SWDL_NEPKGCHECK
CPC_NODE_ID_ERR
PATCH_ACT_TIMEOUT
SWDL_PKGVER_MM
DBMS_ABNORMAL
PATCH_DEACT_TIMEOUT
SWDL_PKG_NOBDSOFT
DBMS_ERROR
PATCH_PKGERR
SWDL_ROLLBACK_FAI
L
DBMS_PROTECT_MODE
POWER_FAIL
SYNC_DISABLE
DB_RESTORE_FAIL
RTC_FAIL
SYNC_FAIL
SECU_ALM
SYSLOG_COMM_FAIL
HARD_BAD
SEC_RADIUS_FAIL
SYSPARA_CFDB_NOSAME
HARD_ERR
STORM_CUR_QUENUM_
OVER
TEMP_OVER
HSC_UNAVAIL
SWDL_ACTIVATED_TIM
EOUT
WRG_BD_TYPE
BD_NOT_INSTALLED
TN52SCC
Issue 02 (2011-10-31)
ALC_ADJUST_FAIL
LCS_EXPIRED
SUBRACK_ID_MISMATCH
ALC_WAIT_ADJUST
LCS_FILE_NOT_EXIST
SUBRACK_LOOP
APS_FAIL
MS_APS_INDI_EX
SUBRACK_TYPE_MI
SMATCH
APS_INDI
NEBD_XC_DIF
SWDL_ACTIVATED_
TIMEOUT
APS_MANUAL_STOP
NESF_LOST
SWDL_AUTOMATCH
_INH
BD_NOT_INSTALLED
NESTATE_INSTALL
SWDL_BD_EXCLUDE

167
OptiX OSN 8800/6800/3800

2 Alarm List
BD_STATUS
NODEID_MM
SWDL_CHGMNG_NO
MATCH
BOOTROM_BAD
NTP_SYNC_FAIL
SWDL_COMMIT_FAI
L
CFCARD_FAILED
PATCH_ACT_TIMEOUT
SWDL_INPROCESS
COMMUN_FAIL
PATCH_DEACT_TIMEOUT
SWDL_NEPKGCHEC
K
CPC_NODE_ID_ERR
PATCH_PKGERR
SWDL_PKGVER_MM
DBMS_ABNORMAL
POWER_FAIL
SWDL_PKG_NOBDSOFT
DBMS_ERROR
RTC_FAIL
SWDL_ROLLBACK_F
AIL
DBMS_PROTECT_MOD
E
SECU_ALM
SYNC_DISABLE
DB_RESTORE_FAIL
SEC_RADIUS_FAIL
SYNC_FAIL
FEATURE_WITHOUT_
LICENSE
D_LICENSE
SYSLOG_COMM_FAI
L
HARD_BAD
SYSPARA_CFDB_NOSAME
HARD_ERR
TEMP_OVER
HSC_UNAVAIL
SNCP_FAIL
WRG_BD_TYPE
K1_K2_M
R
XC_UNSWITCH
K2_M
SUBRACK_COMM_PS
LCS_DAYS_OF_GRAC
E
SUBRACK_ID_CONFLICT
TNK2SCC
Issue 02 (2011-10-31)
ALC_ADJUST_FAIL
LCS_EXPIRED
SUBRACK_ID_MISMATCH
ALC_WAIT_ADJUST
LCS_FILE_NOT_EXIST
SUBRACK_LOOP
APS_FAIL
MS_APS_INDI_EX
SUBRACK_TYPE_MI
SMATCH
APS_INDI
NEBD_XC_DIF
SWDL_ACTIVATED_
TIMEOUT

168
OptiX OSN 8800/6800/3800

2 Alarm List
APS_MANUAL_STOP
NESF_LOST
SWDL_AUTOMATCH
_INH
BD_NOT_INSTALLED
NESTATE_INSTALL
SWDL_BD_EXCLUDE
BD_STATUS
NODEID_MM
SWDL_CHGMNG_NO
MATCH
BOOTROM_BAD
NTP_SYNC_FAIL
SWDL_COMMIT_FAI
L
CFCARD_FAILED
PATCH_ACT_TIMEOUT
SWDL_INPROCESS
COMMUN_FAIL
PATCH_DEACT_TIMEOUT
SWDL_NEPKGCHEC
K
CPC_NODE_ID_ERR
PATCH_PKGERR
SWDL_PKGVER_MM
DBMS_ABNORMAL
POWER_FAIL
SWDL_PKG_NOBDSOFT
DBMS_ERROR
RTC_FAIL
SWDL_ROLLBACK_F
AIL
DBMS_PROTECT_MOD
E
SECU_ALM
SYNC_DISABLE
DB_RESTORE_FAIL
SEC_RADIUS_FAIL
SYNC_FAIL
FEATURE_WITHOUT_
LICENSE
D_LICENSE
SYSLOG_COMM_FAI
L
HARD_BAD
SYSPARA_CFDB_NOSAME
HARD_ERR
TEMP_OVER
HSC_UNAVAIL
SNCP_FAIL
WRG_BD_TYPE
K1_K2_M
R
XC_UNSWITCH
K2_M
SUBRACK_COMM_PS
LCS_DAYS_OF_GRAC
E
SUBRACK_ID_CONFLICT
TN16SCC
Issue 02 (2011-10-31)
ALC_ADJUST_FAIL
LCS_FILE_NOT_EXIST
SUBRACK_ID_MISMATCH
ALC_WAIT_ADJUST
LTI
SUBRACK_LOOP
APS_MANUAL_STOP
MS_APS_INDI_EX

169
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
APS_FAIL
NEBD_XC_DIF
SWDL_ACTIVATED_TIME
OUT
APS_INDI
NESF_LOST
SWDL_AUTOMATCH_INH
BD_NOT_INSTALLED
NESTATE_INSTALL
SWDL_BD_EXCLUDE
BD_STATUS
NODEID_MM
SWDL_CHGMNG_NOMATCH
BOOTROM_BAD
NO_BD_SOFT
SWDL_COMMIT_FAIL
CFCARD_FAILED
NO_ELABEL
SWDL_INPROCESS
CLK_LOCK_FAIL
NTP_SYNC_FAIL
SWDL_NEPKGCHECK
CLK_NO_TRACE_MO
DE
OOL
SWDL_PKGVER_MM
COMMUN_FAIL
PATCH_ACT_TIMEOUT
SWDL_PKG_NOBDSOFT
CPC_NODE_ID_ERR
PATCH_DEACT_TIMEOUT
SWDL_ROLLBACK_FAIL
DBMS_ABNORMAL
PATCH_PKGERR
SYNC_C_LOS
DBMS_ERROR
POWER_FAIL
SYNC_DISABLE
DBMS_PROTECT_MO
DE
PTP_SOURCE_SWITCH
SYNC_FAIL
DB_RESTORE_FAIL
PTP_TIMESTAMP_ABN
SYNC_F_M_SWITCH
EXT_SYNC_LOS
RTC_FAIL
SYNC_LOCKOFF
EXT_TIME_LOC
S1_SYN_CHANGE
SYN_BAD
FEATURE_WITHOUT_
LICENSE
SECU_ALM
SYSLOG_COMM_FAIL
HARD_BAD
SEC_RADIUS_FAIL
SYSPARA_CFDB_NOSAME
HARD_ERR
SERVICE_CAPACITY_EX
CEED_LICENSE
TEMP_OVER
HSC_UNAVAIL
SERVICE_TYPE_EXCEED
_LICENSE
TIME_LOCK_FAIL
K1_K2_M
SHELF_AREA_POWER_O
VER
TIME_LOS
K2_M
STORM_CUR_QUENUM_
OVER
TIME_NO_TRACE_MODE
LCS_DAYS_OF_GRAC
E
SUBRACK_COMM_PS
WRG_BD_TYPE
LCS_EXPIRED
SUBRACK_ID_CONFLICT

170
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.82 SCS Board Alarm List

BD_STATUS
OMS_FDI_O
OMS_SSF_P
OMS_BDI
OMS_FDI_P
OPA_FAIL_INDI
OMS_BDI_O
OMS_LOS_P
WRG_BD_TYPE
OMS_BDI_P
OMS_SSF
OMS_FDI
OMS_SSF_O
2.2.83 SFIU Board Alarm List

BD_STATUS
OTS_BDI_O
OTS_TIM
MUT_LOS
OTS_BDI_P
WAVEDATA_MIS
OOS_LOST
OTS_LOS
WRG_BD_TYPE
OPA_FAIL_INDI
OTS_LOS_O
OTS_BDI
OTS_LOS_P
2.2.84 ST2 Board Alarm List
Issue 02 (2011-10-31)
ALM_HANGUP
LOOP_ALM
PORT_MODULE_OFFLINE
BD_STATUS
LSR_WILL_DIE
R_LOF
BEFFEC_EXC
NO_BD_SOFT
SCC_LOC
COMMUN_FAIL
NO_ELABEL
TD
HARD_BAD
OSC_BDI
TEMP_OVER
HARD_ERR
OSC_DEG
TF
IN_PWR_HIGH
OSC_LOS
WRG_BD_TYPE
IN_PWR_LOW
OUT_PWR_HIGH
OUT_PWR_LOW

171
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.85 SF64 Board Alarm List

ALM_ALS
HP_TIM
PM_BIP8_OVER
AU_AIS
HP_UNEQ
PM_BIP8_SD
AU_LOP
IN_PWR_HIGH
PM_TIM
B1_EXC
IN_PWR_LOW
PORT_MODULE_OFFLINE
B1_SD
J0_MM
POWER_ABNORMAL
B2_EXC
R_LOC
B2_SD
LASER_SHUT
R_LOF
B3_EXC
LOOP_ALM
R_LOS
B3_SD
LSR_COOL_ALM
SLAVE_WORKING
BD_STATUS
LSR_WILL_DIE
SM_BDI
BEFFEC_EXC
MS_AIS
SM_BEI
BUS_ERR
MS_RDI
SM_BIP8_OVER
C2_VCAIS
MS_REI
SM_BIP8_SD
COMMUN_FAIL
NO_BD_SOFT
SM_IAE
FEC_LOF
ODU_AIS
SM_TIM
FEC_OOF
ODU_LCK
TEMP_OVER
FSELECT_STG
ODU_OCI
TEM_HA
HARD_BAD
OH_LOOP
TEM_LA
HARD_ERR
OTU_AIS
TEST_STATUS
HP_LOM
OTU_LOF
TF
HP_RDI
OTU_LOM
TR_LOC
HP_REI
PM_BDI
WAVEDATA_MIS
HP_SLM
PM_BEI
WRG_BD_TYPE
2.2.86 SF64A Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_TIM
PM_BIP8_OVER
AU_AIS
HP_UNEQ
PM_BIP8_SD
AU_LOP
IN_PWR_HIGH
PM_TIM

172
OptiX OSN 8800/6800/3800

2 Alarm List
B1_EXC
IN_PWR_LOW
PORT_MODULE_OFFLINE
B1_SD
J0_MM
POWER_ABNORMAL
B2_EXC
R_LOC
B2_SD
LASER_SHUT
R_LOF
B3_EXC
LOOP_ALM
R_LOS
B3_SD
LSR_COOL_ALM
SLAVE_WORKING
BD_STATUS
LSR_WILL_DIE
SM_BDI
BEFFEC_EXC
MS_AIS
SM_BEI
BUS_ERR
MS_RDI
SM_BIP8_OVER
C2_VCAIS
MS_REI
SM_BIP8_SD
COMMUN_FAIL
NO_BD_SOFT
SM_IAE
FEC_LOF
ODU_AIS
SM_TIM
FEC_OOF
ODU_LCK
TEMP_OVER
FSELECT_STG
ODU_OCI
TEM_HA
HARD_BAD
OH_LOOP
TEM_LA
HARD_ERR
OTU_AIS
TEST_STATUS
HP_LOM
OTU_LOF
TF
HP_RDI
OTU_LOM
TR_LOC
HP_REI
PM_BDI
WRG_BD_TYPE
HP_SLM
PM_BEI
2.2.87 SFD64 Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_TIM
PM_BIP8_OVER
AU_AIS
HP_UNEQ
PM_BIP8_SD
AU_LOP
IN_PWR_HIGH
PM_TIM
B1_EXC
IN_PWR_LOW
PORT_MODULE_OFFLINE
B1_SD
J0_MM
POWER_ABNORMAL
B2_EXC
R_LOC

173
OptiX OSN 8800/6800/3800

2 Alarm List
B2_SD
LASER_SHUT
R_LOF
B3_EXC
LOOP_ALM
R_LOS
B3_SD
LSR_COOL_ALM
SLAVE_WORKING
BD_STATUS
LSR_WILL_DIE
SM_BDI
BEFFEC_EXC
MS_AIS
SM_BEI
BUS_ERR
MS_RDI
SM_BIP8_OVER
C2_VCAIS
MS_REI
SM_BIP8_SD
COMMUN_FAIL
NO_BD_SOFT
SM_IAE
FEC_LOF
ODU_AIS
SM_TIM
FEC_OOF
ODU_LCK
TEMP_OVER
FSELECT_STG
ODU_OCI
TEM_HA
HARD_BAD
OH_LOOP
TEM_LA
HARD_ERR
OTU_AIS
TEST_STATUS
HP_LOM
OTU_LOF
TF
HP_RDI
OTU_LOM
TR_LOC
HP_REI
PM_BDI
WAVEDATA_MIS
HP_SLM
PM_BEI
WRG_BD_TYPE
2.2.88 SL64 Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT
AU_LOP
HP_REI
OH_LOOP
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER

174
OptiX OSN 8800/6800/3800

2 Alarm List
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.89 SLH41 Board Alarm List

ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT
AU_LOP
HP_REI
OH_LOOP
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.90 SLD64 Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT

175
OptiX OSN 8800/6800/3800

2 Alarm List
AU_LOP
HP_REI
OH_LOOP
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.91 SLO16 Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT
AU_LOP
HP_REI
OH_LOOP
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA

176
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.92 SLQ16 Board Alarm List

ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT
AU_LOP
HP_REI
OH_LOOP
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.93 SLQ64 Board Alarm List
Issue 02 (2011-10-31)
ALM_ALS
HP_LOM
MS_REI
AU_AIS
HP_RDI
NO_BD_SOFT
AU_LOP
HP_REI
OH_LOOP

177
OptiX OSN 8800/6800/3800

2 Alarm List
B1_EXC
HP_SLM
PORT_MODULE_OFFLINE
B1_SD
HP_TIM
POWER_ABNORMAL
B2_EXC
HP_UNEQ
R_LOC
B2_SD
IN_PWR_HIGH
R_LOF
B3_EXC
IN_PWR_LOW
R_LOS
B3_SD
J0_MM
SLAVE_WORKING
BD_STATUS
TEMP_OVER
BUS_ERR
LASER_SHUT
TEM_HA
C2_VCAIS
LOOP_ALM
TEM_LA
COMMUN_FAIL
LSR_COOL_ALM
TEST_STATUS
FSELECT_STG
LSR_WILL_DIE
TF
HARD_BAD
MS_AIS
TR_LOC
HARD_ERR
MS_RDI
WRG_BD_TYPE
2.2.94 STG Board Alarm List

BD_STATUS
LTI
CLK_NO_TRACE_MOD
E
NO_BD_SOFT
COMMUN_FAIL
NO_ELABEL
TEMP_OVER
EXT_SYNC_LOS
OOL
TIME_LOS
EXT_TIME_LOC
S1_SYN_CHANGE
TIME_NO_TRACE_MODE
HARD_BAD
SYNC_C_LOS
WRG_BD_TYPE
HARD_ERR
SYNC_F_M_SWITCH
SYNC_LOCKOFF
SYN_BAD
2.2.95 STI Board Alarm List

BD_STATUS
Issue 02 (2011-10-31)
WRG_BD_TYPE

178
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.96 SXM Board Alarm List

BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
2.2.97 SXH Board Alarm List
2.2.98 TBE Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ETH_CFM_RDI
MULTI_RPL_OWNER
B1_SD
ETH_CFM_UNEXPERI
NO_BD_SOFT
BD_STATUS
EX_ETHOAM_CC_LOS
NO_ELABEL
BUS_ERR
EX_ETHOAM_MPID_CNFL
CT
OPA_FAIL_INDI
CLIENT_PORT_PS
FLOW_OVER
OUT_PWR_HIGH
HARD_BAD
OUT_PWR_LOW
HARD_ERR
PORT_MODULE_OFFLINE
COMMUN_FAIL
IN_PWR_HIGH
RS_CROSSTR
DBPS_ABNORMAL
IN_PWR_LOW
R_LOF
DLAG_PROTECT_FAIL
J0_MM
R_LOS
ETHOAM_DISCOVER_FA
IL
LAG_PORT_FAIL
TD
ETHOAM_RMT_CRIT_FA
ULT
LAG_VC_PORT_FAIL
TEMP_OVER
ETHOAM_RMT_LOOP
TEM_HA
ETHOAM_RMT_SD
LINK_ERR
TEM_LA
ETHOAM_SELF_LOOP
LOOP_ALM
TF

179
OptiX OSN 8800/6800/3800

2 Alarm List
ETHOAM_VCG_SELF_LO
OP
LPT_ACTIVE
VLAN_SNCP_PS
ETH_CFM_LOC
LSR_FORCE_OPEN
WAVEDATA_MIS
ETH_CFM_MACSTATUS
LSR_INVALID
WRG_BD_TYPE
ETH_CFM_MISMERGE
LSR_WILL_DIE
2.2.99 TDC Board Alarm List

BD_STATUS
HARD_ERR
NO_ELABEL
COMMUN_FAIL
IN_PWR_HIGH
R_LOS
DCM_INSUFF
IN_PWR_LOW
TEMP_OVER
HARD_BAD
NO_BD_SOFT
WRG_BD_TYPE
2.2.100 TDG Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
LSR_WILL_DIE
OUT_PWR_HIGH
BUS_ERR
MS_SNCP_PS
OUT_PWR_LOW
CLIENT_PORT_PS
MS_SNCP_STA_INDI
PORT_MODULE_OFFLINE
NO_BD_SOFT
REM_SD
NO_ELABEL
REM_SF
COMMUN_FAIL
ODU1_LOFLOM
R_LOS
HARD_BAD
ODU1_PM_AIS
SW_SNCP_PS
HARD_ERR
ODU1_PM_BDI
SW_SNCP_STA_INDI
IN_PWR_HIGH
ODU1_PM_DEG
TD
IN_PWR_LOW
ODU1_PM_EXC
TEMP_OVER
ODU1_PM_LCK
TEM_HA
LINK_ERR
ODU1_PM_OCI
TEM_LA
LOOP_ALM
ODU1_PM_SSF
TF
LPT_ACTIVE
ODU1_PM_TIM
WAVEDATA_MIS
LSR_FORCE_OPEN
OPA_FAIL_INDI
WRG_BD_TYPE

180
OptiX OSN 8800/6800/3800

2 Alarm List
LSR_INVALID
OPU1_PLM
2.2.101 TDX Board Alarm List

TN53TDX
Issue 02 (2011-10-31)
ALS_ACTIVE
ODU2_PM_BDI
ODU_SNCP_STA_INDI
B1_EXC
ODU2_PM_DEG
OPU2_PLM
B1_SD
ODU2_PM_EXC
OTU2_AIS
BD_STATUS
ODU2_PM_LCK
OTU2_BDI
BEFFEC_EXC
ODU2_PM_OCI
OTU2_DEG
BUS_ERR
ODU2_PM_SSF
OTU2_LOF
CLIENT_PORT_PS
ODU2_PM_TIM
OTU2_LOM
CLIENT_PORT_STA_I
NDI
ODU2_TCMn_AIS
OTU2_SSF
ODU2_TCMn_BDI
OTU2_TIM
COMMUN_FAIL
ODU2_TCMn_DEG
OUT_PWR_HIGH
HARD_BAD
ODU2_TCMn_EXC
OUT_PWR_LOW
HARD_ERR
ODU2_TCMn_LCK
PORT_MODULE_OFFLINE
IN_PWR_HIGH
ODU2_TCMn_LTC
PRBS_LSS
IN_PWR_LOW
ODU2_TCMn_OCI
REMOTE_FAULT
J0_MM
ODU2_TCMn_SSF
REM_SD
LASER_MODULE_MIS
MATCH
ODU2_TCMn_TIM
REM_SF
LOCAL_FAULT
ODUFLEX_LOFLOM
RS_CROSSTR
LOOP_ALM
ODUFLEX_PLM
R_LOC
LPT_ACTIVE
ODUFLEX_PM_AIS
R_LOF
LSR_INVALID
ODUFLEX_PM_BDI
R_LOS
LSR_WILL_DIE
ODUFLEX_PM_DEG
TD
L_SYNC
ODUFLEX_PM_EXC
TEMP_OVER
NO_BD_SOFT
ODUFLEX_PM_LCK
TEM_HA
NO_ELABEL
ODUFLEX_PM_OCI
TEM_LA

181
OptiX OSN 8800/6800/3800

2 Alarm List
NULL_SEND
ODUFLEX_PM_SSF
TF
ODU2_LOFLOM
ODUFLEX_PM_TIM
WAVEDATA_MIS
ODU2_PM_AIS
ODU_SNCP_PS
WRG_BD_TYPE
ALS_ACTIVE
NO_ELABEL
OTU2_DEG
B1_EXC
NULL_SEND
OTU2_LOF
B1_SD
ODU2_LOFLOM
OTU2_LOM
BD_STATUS
ODU2_PM_AIS
OTU2_SSF
BEFFEC_EXC
ODU2_PM_BDI
OTU2_TIM
BUS_ERR
ODU2_PM_DEG
OUT_PWR_HIGH
CLIENT_PORT_PS
ODU2_PM_LCK
OUT_PWR_LOW
CLIENT_PORT_STA_I
NDI
ODU2_PM_OCI
PORT_MODULE_OFFLINE
ODU2_PM_SSF
PRBS_LSS
COMMUN_FAIL
ODU2_PM_TIM
REM_SD
HARD_BAD
ODU2_TCMn_AIS
REM_SF
HARD_ERR
ODU2_TCMn_BDI
REMOTE_FAULT
IN_PWR_HIGH
ODU2_TCMn_DEG
R_LOC
IN_PWR_LOW
ODU2_TCMn_LCK
R_LOF
J0_MM
ODU2_TCMn_LTC
R_LOS
LASER_MODULE_MIS
MATCH
ODU2_TCMn_OCI
TD
LOCAL_FAULT
ODU2_TCMn_SSF
TEMP_OVER
LOOP_ALM
ODU2_TCMn_TIM
TEM_HA
LPT_ACTIVE
ODU_SNCP_PS
TEM_LA
LSR_FORCE_OPEN
ODU_SNCP_STA_INDI
TF
LSR_INVALID
OPU2_PLM
WAVEDATA_MIS
LSR_WILL_DIE
OTU2_AIS
WRG_BD_TYPE
NO_BD_SOFT
OTU2_BDI
TN52TDX
Issue 02 (2011-10-31)

182
OptiX OSN 8800/6800/3800

2 Alarm List
TN11TDX
B1_EXC
LSR_FORCE_OPEN
OUT_PWR_HIGH
B1_SD
LSR_INVALID
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
PORT_MODULE_OFFLINE
BUS_ERR
MS_AIS
PRBS_LSS
CLIENT_PORT_PS
NO_BD_SOFT
REMOTE_FAULT
NO_ELABEL
REM_SD
ODU1_LOFLOM
REM_SF
COMMUN_FAIL
ODU1_PM_AIS
R_LOC
FLOW_OVER
ODU1_PM_BDI
R_LOF
HARD_BAD
ODU1_PM_DEG
R_LOS
HARD_ERR
ODU1_PM_EXC
TD
IN_PWR_HIGH
ODU1_PM_LCK
TEMP_OVER
IN_PWR_LOW
ODU1_PM_OCI
TEM_HA
J0_MM
ODU1_PM_SSF
TEM_LA
ODU1_PM_TIM
TF
LOCAL_FAULT
OPA_FAIL_INDI
VCAT_LOA
LOOP_ALM
OPU1_PLM
WAVEDATA_MIS
LPT_ACTIVE
OPU1_VCAT_SQM
WRG_BD_TYPE
LSR_COOL_ALM
OPU1_VCAT_VcPLM
TN12TDX
Issue 02 (2011-10-31)
B1_EXC
LSR_FORCE_OPEN
OUT_PWR_HIGH
B1_SD
LSR_INVALID
OUT_PWR_LOW
BD_STATUS
LSR_WILL_DIE
PORT_MODULE_OFFLINE
BUS_ERR
NO_BD_SOFT
PRBS_LSS
CLIENT_PORT_PS
NO_ELABEL
REMOTE_FAULT
ODU2_LOFLOM
REM_SD
ODU2_PM_AIS
REM_SF

183
OptiX OSN 8800/6800/3800

2 Alarm List
COMMUN_FAIL
ODU2_PM_BDI
R_LOC
HARD_BAD
ODU2_PM_DEG
R_LOF
HARD_ERR
ODU2_PM_EXC
R_LOS
IN_PWR_HIGH
ODU2_PM_LCK
TD
IN_PWR_LOW
ODU2_PM_OCI
TEMP_OVER
J0_MM
ODU2_PM_SSF
TEM_HA
ODU2_PM_TIM
TEM_LA
LOCAL_FAULT
ODU_SNCP_PS
TF
LOOP_ALM
ODU_SNCP_STA_INDI
WAVEDATA_MIS
LPT_ACTIVE
OPA_FAIL_INDI
WRG_BD_TYPE
LSR_COOL_ALM
OPU2_PLM
2.2.102 THA Board Alarm List
Issue 02 (2011-10-31)
ALS_ACTIVE
ODU0_PM_OCI
ODU_SNCP_PS
B1_EXC
ODU0_PM_SSF
ODU_SNCP_STA_INDI
B1_SD
ODU0_PM_TIM
OPU0_PLM
BD_STATUS
ODU1_LOFLOM
OPU1_MSIM
BEFFEC_EXC
ODU1_PM_AIS
OPU1_PLM
BUS_ERR
ODU1_PM_BDI
OTU1_AIS
CLIENT_PORT_PS
ODU1_PM_DEG
OTU1_BDI
CLIENT_PORT_STA_I
NDI
ODU1_PM_EXC
OTU1_DEG
ODU1_PM_LCK
OTU1_EXC
COMMUN_FAIL
ODU1_PM_OCI
OTU1_LOF
HARD_BAD
ODU1_PM_SSF
OTU1_LOM
HARD_ERR
ODU1_PM_TIM
OTU1_SSF
IN_PWR_HIGH
ODU1_TCMn_AIS
OTU1_TIM
IN_PWR_LOW
ODU1_TCMn_BDI
OUT_PWR_HIGH
J0_MM
ODU1_TCMn_DEG
OUT_PWR_LOW

184
OptiX OSN 8800/6800/3800

2 Alarm List
LASER_MODULE_MIS
MATCH
ODU1_TCMn_EXC
PORT_MODULE_OFFLINE
LINK_ERR
ODU1_TCMn_LCK
PRBS_LSS
LOOP_ALM
ODU1_TCMn_LTC
REM_SD
LPT_ACTIVE
ODU1_TCMn_OCI
REM_SF
LSR_INVALID
ODU1_TCMn_SSF
RS_CROSSTR
LSR_WILL_DIE
ODU1_TCMn_TIM
R_LOC
L_SYNC
ODUFLEX_LOFLOM
R_LOF
NO_BD_SOFT
ODUFLEX_PLM
R_LOS
NO_ELABEL
ODUFLEX_PM_AIS
TD
NULL_SEND
ODUFLEX_PM_BDI
TEMP_OVER
ODU0_LOFLOM
ODUFLEX_PM_DEG
TEM_HA
ODU0_PM_AIS
ODUFLEX_PM_EXC
TEM_LA
ODU0_PM_BDI
ODUFLEX_PM_LCK
TF
ODU0_PM_DEG
ODUFLEX_PM_OCI
TS_CFG_MISMATCH
ODU0_PM_EXC
ODUFLEX_PM_SSF
WAVEDATA_MIS
ODU0_PM_LCK
ODUFLEX_PM_TIM
WRG_BD_TYPE
NOTE
TCM6.
2.2.103 TMX Board Alarm List

TN11TMX
Issue 02 (2011-10-31)
B1_EXC
ODU1_TCM3_SSF
ODU2_TCM4_BDI
B1_SD
ODU1_TCM3_TIM
ODU2_TCM4_DEG
BD_STATUS
ODU1_TCM4_AIS
ODU2_TCM4_LCK
BEFFEC_EXC
ODU1_TCM4_BDI
ODU2_TCM4_LTC
CLIENT_PORT_PS
ODU1_TCM4_DEG
ODU2_TCM4_OCI
ODU1_TCM4_LCK
ODU2_TCM4_SSF
ODU1_TCM4_LTC
ODU2_TCM4_TIM
COMMUN_FAIL
ODU1_TCM4_OCI
ODU2_TCM5_AIS

185
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
HARD_BAD
ODU1_TCM4_SSF
ODU2_TCM5_BDI
HARD_ERR
ODU1_TCM4_TIM
ODU2_TCM5_DEG
IN_PWR_HIGH
ODU1_TCM5_AIS
ODU2_TCM5_LCK
IN_PWR_LOW
ODU1_TCM5_BDI
ODU2_TCM5_LTC
J0_MM
ODU1_TCM5_DEG
ODU2_TCM5_OCI
ODU1_TCM5_LCK
ODU2_TCM5_SSF
LOOP_ALM
ODU1_TCM5_LTC
ODU2_TCM5_TIM
LSR_FORCE_OPEN
ODU1_TCM5_OCI
ODU2_TCM6_AIS
LSR_INVALID
ODU1_TCM5_SSF
ODU2_TCM6_BDI
LSR_WILL_DIE
ODU1_TCM5_TIM
ODU2_TCM6_DEG
NO_BD_SOFT
ODU1_TCM6_AIS
ODU2_TCM6_LCK
NO_ELABEL
ODU1_TCM6_BDI
ODU2_TCM6_LTC
NULL_SEND
ODU1_TCM6_DEG
ODU2_TCM6_OCI
OCh_FDI
ODU1_TCM6_LCK
ODU2_TCM6_SSF
OCh_FDI_O
ODU1_TCM6_LTC
ODU2_TCM6_TIM
OCh_FDI_P
ODU1_TCM6_OCI
OPA_FAIL_INDI
OCh_LOS_P
ODU1_TCM6_SSF
OPU1_PLM
OCh_OCI
ODU1_TCM6_TIM
OPU2_MSIM
OCh_SSF
ODU2_LOFLOM
OPU2_PLM
OCh_SSF_O
ODU2_PM_AIS
OTU1_AIS
OCh_SSF_P
ODU2_PM_BDI
OTU1_BDI
ODU1_LOFLOM
ODU2_PM_DEG
OTU1_DEG
ODU1_PM_AIS
ODU2_PM_LCK
OTU1_LOF
ODU1_PM_BDI
ODU2_PM_OCI
OTU1_LOM
ODU1_PM_DEG
ODU2_PM_SSF
OTU1_SSF
ODU1_PM_LCK
ODU2_PM_TIM
OTU1_TIM
ODU1_PM_OCI
ODU2_TCM1_AIS
OTU2_AIS
ODU1_PM_SSF
ODU2_TCM1_BDI
OTU2_BDI
ODU1_PM_TIM
ODU2_TCM1_DEG
OTU2_DEG
ODU1_TCM1_AIS
ODU2_TCM1_LCK
OTU2_LOF

186
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM1_BDI
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_DEG
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_LCK
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_LTC
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_OCI
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM1_SSF
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM1_TIM
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM2_AIS
ODU2_TCM2_LCK
REM_SD
ODU1_TCM2_BDI
ODU2_TCM2_LTC
REM_SF
ODU1_TCM2_DEG
ODU2_TCM2_OCI
RS_CROSSTR
ODU1_TCM2_LCK
ODU2_TCM2_SSF
R_LOC
ODU1_TCM2_LTC
ODU2_TCM2_TIM
R_LOF
ODU1_TCM2_OCI
ODU2_TCM3_AIS
R_LOS
ODU1_TCM2_SSF
ODU2_TCM3_BDI
TD
ODU1_TCM2_TIM
ODU2_TCM3_DEG
TEMP_OVER
ODU1_TCM3_AIS
ODU2_TCM3_LCK
TEM_HA
ODU1_TCM3_BDI
ODU2_TCM3_LTC
TEM_LA
ODU1_TCM3_DEG
ODU2_TCM3_OCI
TF
ODU1_TCM3_LCK
ODU2_TCM3_SSF
WAVEDATA_MIS
ODU1_TCM3_LTC
ODU2_TCM3_TIM
WRG_BD_TYPE
ODU1_TCM3_OCI
ODU2_TCM4_AIS
TN12TMX
Issue 02 (2011-10-31)
B1_EXC
ODU1_TCM3_SSF
ODU2_TCM4_DEG
B1_SD
ODU1_TCM3_TIM
ODU2_TCM4_LCK
BD_STATUS
ODU1_TCM4_AIS
ODU2_TCM4_LTC
BEFFEC_EXC
ODU1_TCM4_BDI
ODU2_TCM4_OCI
CLIENT_PORT_PS
ODU1_TCM4_DEG
ODU2_TCM4_SSF
ODU1_TCM4_LCK
ODU2_TCM4_TIM
ODU1_TCM4_LTC
ODU2_TCM5_AIS

187
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
COMMUN_FAIL
ODU1_TCM4_OCI
ODU2_TCM5_BDI
HARD_BAD
ODU1_TCM4_SSF
ODU2_TCM5_DEG
HARD_ERR
ODU1_TCM4_TIM
ODU2_TCM5_LCK
IN_PWR_HIGH
ODU1_TCM5_AIS
ODU2_TCM5_LTC
IN_PWR_LOW
ODU1_TCM5_BDI
ODU2_TCM5_OCI
J0_MM
ODU1_TCM5_DEG
ODU2_TCM5_SSF
ODU1_TCM5_LCK
ODU2_TCM5_TIM
LOOP_ALM
ODU1_TCM5_LTC
ODU2_TCM6_AIS
LSR_FORCE_OPEN
ODU1_TCM5_OCI
ODU2_TCM6_BDI
LSR_INVALID
ODU1_TCM5_SSF
ODU2_TCM6_DEG
LSR_WILL_DIE
ODU1_TCM5_TIM
ODU2_TCM6_LCK
NO_BD_SOFT
ODU1_TCM6_AIS
ODU2_TCM6_LTC
NO_ELABEL
ODU1_TCM6_BDI
ODU2_TCM6_OCI
NULL_SEND
ODU1_TCM6_DEG
ODU2_TCM6_SSF
OCh_FDI
ODU1_TCM6_LCK
ODU2_TCM6_TIM
OCh_FDI_O
ODU1_TCM6_LTC
OPA_FAIL_INDI
OCh_FDI_P
ODU1_TCM6_OCI
OPU1_PLM
OCh_LOS_P
ODU1_TCM6_SSF
OPU2_MSIM
OCh_OCI
ODU1_TCM6_TIM
OPU2_PLM
OCh_SSF
ODU2_PM_AIS
OTU1_AIS
OCh_SSF_O
ODU2_PM_BDI
OTU1_BDI
OCh_SSF_P
ODU2_PM_DEG
OTU1_DEG
ODU1_LOFLOM
ODU2_PM_LCK
OTU1_LOF
ODU1_PM_AIS
ODU2_PM_OCI
OTU1_LOM
ODU1_PM_BDI
ODU2_PM_SSF
OTU1_SSF
ODU1_PM_DEG
ODU2_PM_TIM
OTU1_TIM
ODU1_PM_LCK
ODU2_TCM1_AIS
OTU2_AIS
ODU1_PM_OCI
ODU2_TCM1_BDI
OTU2_BDI
ODU1_PM_SSF
ODU2_TCM1_DEG
OTU2_DEG
ODU1_PM_TIM
ODU2_TCM1_LCK
OTU2_LOF

188
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM1_AIS
ODU2_TCM1_LTC
OTU2_LOM
ODU1_TCM1_BDI
ODU2_TCM1_OCI
OTU2_SSF
ODU1_TCM1_DEG
ODU2_TCM1_SSF
OTU2_TIM
ODU1_TCM1_LCK
ODU2_TCM1_TIM
OUT_PWR_HIGH
ODU1_TCM1_LTC
ODU2_TCM2_AIS
OUT_PWR_LOW
ODU1_TCM1_OCI
ODU2_TCM2_BDI
PORT_MODULE_OFFLINE
ODU1_TCM1_SSF
ODU2_TCM2_DEG
PRBS_LSS
ODU1_TCM1_TIM
ODU2_TCM2_LCK
REM_SD
ODU1_TCM2_AIS
ODU2_TCM2_LTC
REM_SF
ODU1_TCM2_BDI
ODU2_TCM2_OCI
RS_CROSSTR
ODU1_TCM2_DEG
ODU2_TCM2_SSF
R_LOC
ODU1_TCM2_LCK
ODU2_TCM2_TIM
R_LOF
ODU1_TCM2_LTC
ODU2_TCM3_AIS
R_LOS
ODU1_TCM2_OCI
ODU2_TCM3_BDI
TD
ODU1_TCM2_SSF
ODU2_TCM3_DEG
TEMP_OVER
ODU1_TCM2_TIM
ODU2_TCM3_LCK
TEM_HA
ODU1_TCM3_AIS
ODU2_TCM3_LTC
TEM_LA
ODU1_TCM3_BDI
ODU2_TCM3_OCI
TF
ODU1_TCM3_DEG
ODU2_TCM3_SSF
WAVEDATA_MIS
ODU1_TCM3_LCK
ODU2_TCM3_TIM
WRG_BD_TYPE
ODU1_TCM3_LTC
ODU2_TCM4_AIS
ODU1_TCM3_OCI
ODU2_TCM4_BDI
2.2.104 TOA Board Alarm List
Issue 02 (2011-10-31)
ALS_ACTIVE
ODU0_PM_OCI
ODU_SNCP_PS
B1_EXC
ODU0_PM_SSF
ODU_SNCP_STA_INDI
B1_SD
ODU0_PM_TIM
OPU0_PLM
BD_STATUS
ODU1_LOFLOM
OPU1_MSIM
BEFFEC_EXC
ODU1_PM_AIS
OPU1_PLM

189
OptiX OSN 8800/6800/3800

2 Alarm List
BUS_ERR
ODU1_PM_BDI
OTU1_AIS
CLIENT_PORT_PS
ODU1_PM_DEG
OTU1_BDI
CLIENT_PORT_STA_I
NDI
ODU1_PM_EXC
OTU1_DEG
ODU1_PM_LCK
OTU1_EXC
COMMUN_FAIL
ODU1_PM_OCI
OTU1_LOF
HARD_BAD
ODU1_PM_SSF
OTU1_LOM
HARD_ERR
ODU1_PM_TIM
OTU1_SSF
IN_PWR_HIGH
ODU1_TCMn_AIS
OTU1_TIM
IN_PWR_LOW
ODU1_TCMn_BDI
OUT_PWR_HIGH
J0_MM
ODU1_TCMn_DEG
OUT_PWR_LOW
LASER_MODULE_MIS
MATCH
ODU1_TCMn_EXC
PORT_MODULE_OFFLINE
LINK_ERR
ODU1_TCMn_LCK
PRBS_LSS
LOOP_ALM
ODU1_TCMn_LTC
REM_SD
LPT_ACTIVE
ODU1_TCMn_OCI
REM_SF
LSR_INVALID
ODU1_TCMn_SSF
RS_CROSSTR
LSR_WILL_DIE
ODU1_TCMn_TIM
R_LOC
L_SYNC
ODUFLEX_LOFLOM
R_LOF
NO_BD_SOFT
ODUFLEX_PLM
R_LOS
NO_ELABEL
ODUFLEX_PM_AIS
TD
NULL_SEND
ODUFLEX_PM_BDI
TEMP_OVER
ODU0_LOFLOM
ODUFLEX_PM_DEG
TEM_HA
ODU0_PM_AIS
ODUFLEX_PM_EXC
TEM_LA
ODU0_PM_BDI
ODUFLEX_PM_LCK
TF
ODU0_PM_DEG
ODUFLEX_PM_OCI
TS_CFG_MISMATCH
ODU0_PM_EXC
ODUFLEX_PM_SSF
WAVEDATA_MIS
ODU0_PM_LCK
ODUFLEX_PM_TIM
WRG_BD_TYPE
NOTE
TCM6.
Issue 02 (2011-10-31)

190
OptiX OSN 8800/6800/3800

2 Alarm List
2.2.105 TOG Board Alarm List

BD_STATUS
NO_BD_SOFT
ODU1_PM_TIM
BUS_ERR
NO_ELABEL
OPU0_PLM
CLIENT_PORT_PS
ODU0_LOFLOM
OPU1_PLM
ODU0_PM_AIS
OUT_PWR_HIGH
ODU0_PM_BDI
OUT_PWR_LOW
COMMUN_FAIL
ODU0_PM_DEG
PORT_MODULE_OFFLINE
ETH_8B10B_ERR
ODU0_PM_LCK
REM_SD
HARD_BAD
ODU0_PM_OCI
REM_SF
HARD_ERR
ODU0_PM_SSF
R_LOS
IN_PWR_HIGH
ODU0_PM_TIM
TD
IN_PWR_LOW
ODU1_LOFLOM
TEMP_OVER
ODU1_PM_AIS
TEM_HA
LOOP_ALM
ODU1_PM_BDI
TEM_LA
LSR_FORCE_OPEN
ODU1_PM_DEG
TF
LSR_INVALID
ODU1_PM_LCK
WAVEDATA_MIS
LSR_WILL_DIE
ODU1_PM_OCI
WRG_BD_TYPE
L_SYNC
ODU1_PM_SSF
2.2.106 TOM Board Alarm List

TN52TOM
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_BDI
ODU1_TCM5_LTC
B1_SD
ODU1_PM_DEG
ODU1_TCM5_OCI
BD_STATUS
ODU1_PM_EXC
ODU1_TCM5_SSF
BEFFEC_EXC
ODU1_PM_LCK
ODU1_TCM5_TIM
BUS_ERR
ODU1_PM_OCI
ODU1_TCM6_AIS
CLIENT_PORT_PS
ODU1_PM_SSF
ODU1_TCM6_BDI
ODU1_PM_TIM
ODU1_TCM6_DEG
ODU1_TCM1_AIS
ODU1_TCM6_EXC

191
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
COMMUN_FAIL
ODU1_TCM1_BDI
ODU1_TCM6_LCK
ETH_8B10B_ERR
ODU1_TCM1_DEG
ODU1_TCM6_LTC
HARD_BAD
ODU1_TCM1_EXC
ODU1_TCM6_OCI
HARD_ERR
ODU1_TCM1_LCK
ODU1_TCM6_SSF
INTRA_OTU_PS
ODU1_TCM1_LTC
ODU1_TCM6_TIM
INTRA_OTU_STA_INDI
ODU1_TCM1_OCI
ODU_SNCP_PS
IN_PWR_HIGH
ODU1_TCM1_SSF
ODU_SNCP_STA_INDI
IN_PWR_LOW
ODU1_TCM1_TIM
OPA_FAIL_INDI
J0_MM
ODU1_TCM2_AIS
OPU0_PLM
ODU1_TCM2_BDI
OPU1_MSIM
LINK_ERR
ODU1_TCM2_DEG
OPU1_PLM
LOOP_ALM
ODU1_TCM2_EXC
OTU1_AIS
LPT_ACTIVE
ODU1_TCM2_LCK
OTU1_BDI
LSR_FORCE_OPEN
ODU1_TCM2_LTC
OTU1_DEG
LSR_INVALID
ODU1_TCM2_OCI
OTU1_EXC
LSR_WILL_DIE
ODU1_TCM2_SSF
OTU1_LOF
L_SYNC
ODU1_TCM2_TIM
OTU1_LOM
MS_SNCP_PS
ODU1_TCM3_AIS
OTU1_SSF
MS_SNCP_STA_INDI
ODU1_TCM3_BDI
OTU1_TIM
NO_BD_SOFT
ODU1_TCM3_DEG
OUT_PWR_HIGH
NO_ELABEL
ODU1_TCM3_EXC
OUT_PWR_LOW
NULL_SEND
ODU1_TCM3_LCK
PORT_MODULE_OFFLINE
OCh_FDI
ODU1_TCM3_LTC
PRBS_LSS
OCh_FDI_O
ODU1_TCM3_OCI
REM_SD
OCh_FDI_P
ODU1_TCM3_SSF
REM_SF
OCh_LOS_P
ODU1_TCM3_TIM
RS_CROSSTR
OCh_OCI
ODU1_TCM4_AIS
R_LOC
OCh_SSF
ODU1_TCM4_BDI
R_LOF
OCh_SSF_O
ODU1_TCM4_DEG
R_LOS
OCh_SSF_P
ODU1_TCM4_EXC
SW_SNCP_PS

192
OptiX OSN 8800/6800/3800

2 Alarm List
ODU0_LOFLOM
ODU1_TCM4_LCK
SW_SNCP_STA_INDI
ODU0_PM_AIS
ODU1_TCM4_LTC
TD
ODU0_PM_BDI
ODU1_TCM4_OCI
TEMP_OVER
ODU0_PM_DEG
ODU1_TCM4_SSF
TEM_HA
ODU0_PM_LCK
ODU1_TCM4_TIM
TEM_LA
ODU0_PM_OCI
ODU1_TCM5_AIS
TF
ODU0_PM_SSF
ODU1_TCM5_BDI
TS_CFG_MISMATCH
ODU0_PM_TIM
ODU1_TCM5_DEG
WAVEDATA_MIS
ODU1_LOFLOM
ODU1_TCM5_EXC
WRG_BD_TYPE
ODU1_PM_AIS
ODU1_TCM5_LCK
TN11TOM
Issue 02 (2011-10-31)
B1_EXC
ODU1_PM_OCI
ODU1_TCM5_OCI
B1_SD
ODU1_PM_SSF
ODU1_TCM5_SSF
BD_STATUS
ODU1_PM_TIM
ODU1_TCM5_TIM
BEFFEC_EXC
ODU1_TCM1_AIS
ODU1_TCM6_AIS
BUS_ERR
ODU1_TCM1_BDI
ODU1_TCM6_BDI
CLIENT_PORT_PS
ODU1_TCM1_DEG
ODU1_TCM6_DEG
ODU1_TCM1_EXC
ODU1_TCM6_EXC
ODU1_TCM1_LCK
ODU1_TCM6_LCK
COMMUN_FAIL
ODU1_TCM1_LTC
ODU1_TCM6_LTC
ETH_8B10B_ERR
ODU1_TCM1_OCI
ODU1_TCM6_OCI
HARD_BAD
ODU1_TCM1_SSF
ODU1_TCM6_SSF
HARD_ERR
ODU1_TCM1_TIM
ODU1_TCM6_TIM
INTRA_OTU_PS
ODU1_TCM2_AIS
ODU_SNCP_PS
INTRA_OTU_STA_INDI
ODU1_TCM2_BDI
ODU_SNCP_STA_INDI
IN_PWR_HIGH
ODU1_TCM2_DEG
OPA_FAIL_INDI
IN_PWR_LOW
ODU1_TCM2_EXC
OPU1_PLM
J0_MM
ODU1_TCM2_LCK
OTU1_AIS
ODU1_TCM2_LTC
OTU1_BDI

193
OptiX OSN 8800/6800/3800

2 Alarm List
LINK_ERR
ODU1_TCM2_OCI
OTU1_DEG
LOOP_ALM
ODU1_TCM2_SSF
OTU1_EXC
LPT_ACTIVE
ODU1_TCM2_TIM
OTU1_LOF
LSR_FORCE_OPEN
ODU1_TCM3_AIS
OTU1_LOM
LSR_INVALID
ODU1_TCM3_BDI
OTU1_SSF
LSR_WILL_DIE
ODU1_TCM3_DEG
OTU1_TIM
L_SYNC
ODU1_TCM3_EXC
OUT_PWR_HIGH
MS_AIS
ODU1_TCM3_LCK
OUT_PWR_LOW
MS_SNCP_PS
ODU1_TCM3_LTC
PORT_MODULE_OFFLINE
MS_SNCP_STA_INDI
ODU1_TCM3_OCI
PRBS_LSS
NO_BD_SOFT
ODU1_TCM3_SSF
REM_SD
NO_ELABEL
ODU1_TCM3_TIM
REM_SF
NULL_SEND
ODU1_TCM4_AIS
RS_CROSSTR
OCh_FDI
ODU1_TCM4_BDI
R_LOC
OCh_FDI_O
ODU1_TCM4_DEG
R_LOF
OCh_FDI_P
ODU1_TCM4_EXC
R_LOS
OCh_LOS_P
ODU1_TCM4_LCK
SPEED_OVER
OCh_OCI
ODU1_TCM4_LTC
SW_SNCP_PS
OCh_SSF
ODU1_TCM4_OCI
SW_SNCP_STA_INDI
OCh_SSF_O
ODU1_TCM4_SSF
TD
OCh_SSF_P
ODU1_TCM4_TIM
TEMP_OVER
ODU1_LOFLOM
ODU1_TCM5_AIS
TEM_HA
ODU1_PM_AIS
ODU1_TCM5_BDI
TEM_LA
ODU1_PM_BDI
ODU1_TCM5_DEG
TF
ODU1_PM_DEG
ODU1_TCM5_EXC
TS_CFG_MISMATCH
ODU1_PM_EXC
ODU1_TCM5_LCK
WAVEDATA_MIS
ODU1_PM_LCK
ODU1_TCM5_LTC
WRG_BD_TYPE
2.2.107 TQM Board Alarm List

TN11TQM
Issue 02 (2011-10-31)

194
OptiX OSN 8800/6800/3800

2 Alarm List
B1_EXC
LSR_INVALID
OUT_PWR_HIGH
B1_SD
LSR_WILL_DIE
OUT_PWR_LOW
BD_STATUS
L_SYNC
PORT_MODULE_OFFLINE
BUS_ERR
MS_AIS
REM_SD
CLIENT_PORT_PS
MS_SNCP_PS
REM_SF
MS_SNCP_STA_INDI
RS_CROSSTR
NO_BD_SOFT
R_LOC
COMMUN_FAIL
NO_ELABEL
R_LOF
ETH_8B10B_ERR
ODU1_LOFLOM
R_LOS
HARD_BAD
ODU1_PM_AIS
SW_SNCP_PS
HARD_ERR
ODU1_PM_BDI
SW_SNCP_STA_INDI
IN_PWR_HIGH
ODU1_PM_DEG
TD
IN_PWR_LOW
ODU1_PM_EXC
TEMP_OVER
J0_MM
ODU1_PM_LCK
TEM_HA
ODU1_PM_OCI
TEM_LA
LINK_ERR
ODU1_PM_SSF
TF
LOOP_ALM
ODU1_PM_TIM
TS_CFG_MISMATCH
LPT_ACTIVE
OPA_FAIL_INDI
WAVEDATA_MIS
LSR_FORCE_OPEN
OPU1_PLM
WRG_BD_TYPE
B1_EXC
ODU1_TCM1_LTC
ODU1_TCM6_DEG
B1_SD
ODU1_TCM1_OCI
ODU1_TCM6_EXC
BD_STATUS
ODU1_TCM1_SSF
ODU1_TCM6_LCK
BEFFEC_EXC
ODU1_TCM1_TIM
ODU1_TCM6_LTC
BUS_ERR
ODU1_TCM2_AIS
ODU1_TCM6_OCI
CLIENT_PORT_PS
ODU1_TCM2_BDI
ODU1_TCM6_SSF
ODU1_TCM2_DEG
ODU1_TCM6_TIM
ODU1_TCM2_EXC
ODU_SNCP_PS
TN12TQM
Issue 02 (2011-10-31)

195
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
2 Alarm List
COMMUN_FAIL
ODU1_TCM2_LCK
ODU_SNCP_STA_INDI
ETH_8B10B_ERR
ODU1_TCM2_LTC
OPA_FAIL_INDI
HARD_BAD
ODU1_TCM2_OCI
OPU1_PLM
HARD_ERR
ODU1_TCM2_SSF
OTU1_AIS
IN_PWR_HIGH
ODU1_TCM2_TIM
OTU1_BDI
IN_PWR_LOW
ODU1_TCM3_AIS
OTU1_DEG
J0_MM
ODU1_TCM3_BDI
OTU1_EXC
ODU1_TCM3_DEG
OTU1_LOF
LINK_ERR
ODU1_TCM3_EXC
OTU1_LOM
LOOP_ALM
ODU1_TCM3_LCK
OTU1_SSF
LPT_ACTIVE
ODU1_TCM3_LTC
OTU1_TIM
LSR_FORCE_OPEN
ODU1_TCM3_OCI
OUT_PWR_HIGH
LSR_INVALID
ODU1_TCM3_SSF
OUT_PWR_LOW
LSR_WILL_DIE
ODU1_TCM3_TIM
PORT_MODULE_OFFLINE
L_SYNC
ODU1_TCM4_AIS
PRBS_LSS
MS_AIS
ODU1_TCM4_BDI
REM_SD
MS_SNCP_PS
ODU1_TCM4_DEG
REM_SF
MS_SNCP_STA_INDI
ODU1_TCM4_EXC
RS_CROSSTR
NO_BD_SOFT
ODU1_TCM4_LCK
R_LOC
NO_ELABEL
ODU1_TCM4_LTC
R_LOF
ODU1_LOFLOM
ODU1_TCM4_OCI
R_LOS
ODU1_PM_AIS
ODU1_TCM4_SSF
SPEED_OVER
ODU1_PM_BDI
ODU1_TCM4_TIM
SW_SNCP_PS
ODU1_PM_DEG
ODU1_TCM5_AIS
SW_SNCP_STA_INDI
ODU1_PM_EXC
ODU1_TCM5_BDI
TD
ODU1_PM_LCK
ODU1_TCM5_DEG
TEMP_OVER
ODU1_PM_OCI
ODU1_TCM5_EXC
TEM_HA
ODU1_PM_SSF
ODU1_TCM5_LCK
TEM_LA
ODU1_PM_TIM
ODU1_TCM5_LTC
TF
ODU1_TCM1_AIS
ODU1_TCM5_OCI
TS_CFG_MISMATCH

196
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_TCM1_BDI
ODU1_TCM5_SSF
WAVEDATA_MIS
ODU1_TCM1_DEG
ODU1_TCM5_TIM
WRG_BD_TYPE
ODU1_TCM1_EXC
ODU1_TCM6_AIS
ODU1_TCM1_LCK
ODU1_TCM6_BDI
2.2.108 TQS Board Alarm List
Issue 02 (2011-10-31)
B1_EXC
ODU1_TCM1_TIM
ODU1_TCM6_BDI
B1_SD
ODU1_TCM2_AIS
ODU1_TCM6_DEG
BD_STATUS
ODU1_TCM2_BDI
ODU1_TCM6_EXC
BEFFEC_EXC
ODU1_TCM2_DEG
ODU1_TCM6_LCK
BUS_ERR
ODU1_TCM2_EXC
ODU1_TCM6_LTC
CLIENT_PORT_PS
ODU1_TCM2_LCK
ODU1_TCM6_OCI
ODU1_TCM2_LTC
ODU1_TCM6_SSF
ODU1_TCM2_OCI
ODU1_TCM6_TIM
COMMUN_FAIL
ODU1_TCM2_SSF
ODU_SNCP_PS
HARD_BAD
ODU1_TCM2_TIM
ODU_SNCP_STA_INDI
HARD_ERR
ODU1_TCM3_AIS
OPA_FAIL_INDI
IN_PWR_HIGH
ODU1_TCM3_BDI
OPU1_PLM
IN_PWR_LOW
ODU1_TCM3_DEG
OTU1_AIS
J0_MM
ODU1_TCM3_EXC
OTU1_BDI
ODU1_TCM3_LCK
OTU1_DEG
LOOP_ALM
ODU1_TCM3_LTC
OTU1_EXC
LSR_FORCE_OPEN
ODU1_TCM3_OCI
OTU1_LOF
LSR_INVALID
ODU1_TCM3_SSF
OTU1_LOM
LSR_WILL_DIE
ODU1_TCM3_TIM
OTU1_SSF
NO_BD_SOFT
ODU1_TCM4_AIS
OTU1_TIM
NO_ELABEL
ODU1_TCM4_BDI
OUT_PWR_HIGH
ODU1_LOFLOM
ODU1_TCM4_DEG
OUT_PWR_LOW
ODU1_PM_AIS
ODU1_TCM4_EXC
PORT_MODULE_OFFLINE

197
OptiX OSN 8800/6800/3800

2 Alarm List
ODU1_PM_BDI
ODU1_TCM4_LCK
REM_SD
ODU1_PM_DEG
ODU1_TCM4_LTC
REM_SF
ODU1_PM_EXC
ODU1_TCM4_OCI
RS_CROSSTR
ODU1_PM_LCK
ODU1_TCM4_SSF
R_LOC
ODU1_PM_OCI
ODU1_TCM4_TIM
R_LOF
ODU1_PM_SSF
ODU1_TCM5_AIS
R_LOS
ODU1_PM_TIM
ODU1_TCM5_BDI
TD
ODU1_TCM1_AIS
ODU1_TCM5_DEG
TEMP_OVER
ODU1_TCM1_BDI
ODU1_TCM5_EXC
TEM_HA
ODU1_TCM1_DEG
ODU1_TCM5_LCK
TEM_LA
ODU1_TCM1_EXC
ODU1_TCM5_LTC
TF
ODU1_TCM1_LCK
ODU1_TCM5_OCI
WAVEDATA_MIS
ODU1_TCM1_LTC
ODU1_TCM5_SSF
WRG_BD_TYPE
ODU1_TCM1_OCI
ODU1_TCM5_TIM
ODU1_TCM1_SSF
ODU1_TCM6_AIS
2.2.109 TQX Board Alarm List

TN55TQX
Issue 02 (2011-10-31)
ALS_ACTIVE
ODU2_PM_BDI
OPU2_PLM
B1_EXC
ODU2_PM_DEG
OTU2_AIS
B1_SD
ODU2_PM_EXC
OTU2_BDI
BD_STATUS
ODU2_PM_LCK
OTU2_DEG
BEFFEC_EXC
ODU2_PM_OCI
OTU2_EXC
BUS_ERR
ODU2_PM_SSF
OTU2_LOF
CLIENT_PORT_PS
ODU2_PM_TIM
OTU2_LOM
CLIENT_PORT_STA_I
NDI
ODU2_TCMn_AIS
OTU2_SSF
ODU2_TCMn_BDI
OTU2_TIM
COMMUN_FAIL
ODU2_TCMn_DEG
OUT_PWR_HIGH
HARD_BAD
ODU2_TCMn_EXC
OUT_PWR_LOW

198
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_ERR
ODU2_TCMn_LCK
PORT_MODULE_OFFLINE
IN_PWR_HIGH
ODU2_TCMn_LTC
PRBS_LSS
IN_PWR_LOW
ODU2_TCMn_OCI
REMOTE_FAULT
J0_MM
ODU2_TCMn_SSF
REM_SD
LASER_MODULE_MIS
MATCH
ODU2_TCMn_TIM
REM_SF
LOCAL_FAULT
ODUFLEX_LOFLOM
RS_CROSSTR
LOOP_ALM
ODUFLEX_PLM
R_LOC
LPT_ACTIVE
ODUFLEX_PM_AIS
R_LOF
LSR_COOL_ALM
ODUFLEX_PM_BDI
R_LOS
LSR_INVALID
ODUFLEX_PM_DEG
TD
LSR_WILL_DIE
ODUFLEX_PM_EXC
TEMP_OVER
L_SYNC
ODUFLEX_PM_LCK
TEM_HA
NO_BD_SOFT
ODUFLEX_PM_OCI
TEM_LA
NO_ELABEL
ODUFLEX_PM_SSF
TF
NULL_SEND
ODUFLEX_PM_TIM
WAVEDATA_MIS
ODU2_LOFLOM
ODU_SNCP_PS
WRG_BD_TYPE
ODU2_PM_AIS
ODU_SNCP_STA_INDI
TN53TQX
Issue 02 (2011-10-31)
B1_EXC
NULL_SEND
OTU2_DEG
B1_SD
ODU2_LOFLOM
OTU2_EXC
BD_STATUS
ODU2_PM_AIS
OTU2_LOF
BEFFEC_EXC
ODU2_PM_BDI
OTU2_LOM
BUS_ERR
ODU2_PM_DEG
OTU2_SSF
CLIENT_PORT_PS
ODU2_PM_EXC
OTU2_TIM
CLIENT_PORT_STA_I
NDI
ODU2_PM_LCK
OUT_PWR_HIGH
ODU2_PM_OCI
OUT_PWR_LOW
COMMUN_FAIL
ODU2_PM_SSF
PORT_MODULE_OFFLINE
HARD_BAD
ODU2_PM_TIM
PRBS_LSS

199
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_ERR
ODU2_TCMn_AIS
REMOTE_FAULT
IN_PWR_HIGH
ODU2_TCMn_BDI
REM_SD
IN_PWR_LOW
ODU2_TCMn_DEG
REM_SF
J0_MM
ODU2_TCMn_EXC
RS_CROSSTR
LASER_MODULE_MIS
MATCH
ODU2_TCMn_LCK
R_LOC
LOCAL_FAULT
ODU2_TCMn_LTC
R_LOF
LOOP_ALM
ODU2_TCMn_OCI
R_LOS
LPT_ACTIVE
ODU2_TCMn_SSF
TD
LSR_COOL_ALM
ODU2_TCMn_TIM
TEMP_OVER
LSR_INVALID
ODU_SNCP_PS
TEM_HA
LSR_WILL_DIE
ODU_SNCP_STA_INDI
TEM_LA
L_SYNC
OPU2_PLM
TF
NO_BD_SOFT
OTU2_AIS
WAVEDATA_MIS
NO_ELABEL
OTU2_BDI
WRG_BD_TYPE
TN52TQX
Issue 02 (2011-10-31)
B1_EXC
ODU2_TCM1_OCI
ODU2_TCM6_BDI
B1_SD
ODU2_TCM1_SSF
ODU2_TCM6_DEG
BD_STATUS
ODU2_TCM1_TIM
ODU2_TCM6_LCK
BEFFEC_EXC
ODU2_TCM2_AIS
ODU2_TCM6_LTC
BUS_ERR
ODU2_TCM2_BDI
ODU2_TCM6_OCI
CLIENT_PORT_PS
ODU2_TCM2_DEG
ODU2_TCM6_SSF
ODU2_TCM2_LCK
ODU2_TCM6_TIM
ODU2_TCM2_LTC
ODU_SNCP_PS
COMMUN_FAIL
ODU2_TCM2_OCI
ODU_SNCP_STA_INDI
HARD_BAD
ODU2_TCM2_SSF
OPU2_PLM
HARD_ERR
ODU2_TCM2_TIM
OTU2_AIS
IN_PWR_HIGH
ODU2_TCM3_AIS
OTU2_BDI
IN_PWR_LOW
ODU2_TCM3_BDI
OTU2_DEG
J0_MM
ODU2_TCM3_DEG
OTU2_LOF

200
OptiX OSN 8800/6800/3800

2 Alarm List
ODU2_TCM3_LCK
OTU2_LOM
LOCAL_FAULT
ODU2_TCM3_LTC
OTU2_SSF
LOOP_ALM
ODU2_TCM3_OCI
OTU2_TIM
LPT_ACTIVE
ODU2_TCM3_SSF
OUT_PWR_HIGH
LSR_FORCE_OPEN
ODU2_TCM3_TIM
OUT_PWR_LOW
LSR_INVALID
ODU2_TCM4_AIS
PORT_MODULE_OFFLINE
LSR_WILL_DIE
ODU2_TCM4_BDI
PRBS_LSS
NO_BD_SOFT
ODU2_TCM4_DEG
REMOTE_FAULT
NO_ELABEL
ODU2_TCM4_LCK
REM_SD
NULL_SEND
ODU2_TCM4_LTC
REM_SF
ODU2_PM_AIS
ODU2_TCM4_OCI
R_LOC
ODU2_PM_BDI
ODU2_TCM4_SSF
R_LOF
ODU2_PM_DEG
ODU2_TCM4_TIM
R_LOS
ODU2_PM_LCK
ODU2_TCM5_AIS
TD
ODU2_PM_OCI
ODU2_TCM5_BDI
TEMP_OVER
ODU2_PM_SSF
ODU2_TCM5_DEG
TEM_HA
ODU2_PM_TIM
ODU2_TCM5_LCK
TEM_LA
ODU2_TCM1_AIS
ODU2_TCM5_LTC
TF
ODU2_TCM1_BDI
ODU2_TCM5_OCI
WAVEDATA_MIS
ODU2_TCM1_DEG
ODU2_TCM5_SSF
WRG_BD_TYPE
ODU2_TCM1_LCK
ODU2_TCM5_TIM
ODU2_TCM1_LTC
ODU2_TCM6_AIS
TN11TQX
Issue 02 (2011-10-31)
B1_EXC
LSR_FORCE_OPEN
OUT_PWR_LOW
B1_SD
LSR_INVALID
PORT_MODULE_OFFLINE
BD_STATUS
LSR_WILL_DIE
PRBS_LSS
BUS_ERR
NO_BD_SOFT
REMOTE_FAULT
CLIENT_PORT_PS
NO_ELABEL
REM_SD

201
OptiX OSN 8800/6800/3800

2 Alarm List
ODU2_LOFLOM
REM_SF
ODU2_PM_AIS
R_LOC
COMMUN_FAIL
ODU2_PM_BDI
R_LOF
HARD_BAD
ODU2_PM_DEG
R_LOS
HARD_ERR
ODU2_PM_LCK
TD
IN_PWR_HIGH
ODU2_PM_OCI
TEMP_OVER
IN_PWR_LOW
ODU2_PM_SSF
TEM_HA
J0_MM
ODU2_PM_TIM
TEM_LA
ODU_SNCP_PS
TF
LOCAL_FAULT
ODU_SNCP_STA_INDI
WAVEDATA_MIS
LOOP_ALM
OPA_FAIL_INDI
WRG_BD_TYPE
LPT_ACTIVE
OPU2_PLM
LSR_COOL_ALM
OUT_PWR_HIGH
2.2.110 TSXL Board Alarm List

TN11TSXL
Issue 02 (2011-10-31)
B1_EXC
MS_AIS
OUT_PWR_HIGH
B1_SD
NO_BD_SOFT
OUT_PWR_LOW
BD_STATUS
NO_ELABEL
PORT_MODULE_OFFLINE
BUS_ERR
ODU2_LOFLOM
PRBS_LSS
CLIENT_PORT_PS
ODU2_PM_AIS
REM_SD
ODU2_PM_BDI
REM_SF
ODU2_PM_DEG
RS_CROSSTR
COMMUN_FAIL
ODU2_PM_EXC
R_LOC
HARD_BAD
ODU2_PM_LCK
R_LOF
HARD_ERR
ODU2_PM_OCI
R_LOS
IN_PWR_HIGH
ODU2_PM_SSF
TD
IN_PWR_LOW
ODU2_PM_TIM
TEMP_OVER

202
OptiX OSN 8800/6800/3800

2 Alarm List
J0_MM
ODU_SNCP_PS
TEM_HA
LOOP_ALM
ODU_SNCP_STA_INDI
TEM_LA
LSR_COOL_ALM
OPA_FAIL_INDI
TF
LSR_FORCE_OPEN
OPU2_MSIM
VCAT_LOA
LSR_WILL_DIE
OPU2_PLM
WRG_BD_TYPE
B1_EXC
ODU3_TCM2_AIS
ODU3_TCM6_BDI
B1_SD
ODU3_TCM2_BDI
ODU3_TCM6_DEG
BD_STATUS
ODU3_TCM2_DEG
ODU3_TCM6_LCK
BEFFEC_EXC
ODU3_TCM2_LCK
ODU3_TCM6_LTC
BUS_ERR
ODU3_TCM2_LTC
ODU3_TCM6_OCI
CLIENT_PORT_PS
ODU3_TCM2_OCI
ODU3_TCM6_SSF
ODU3_TCM2_SSF
ODU3_TCM6_TIM
ODU3_TCM2_TIM
ODU3_TCM6_EXC
COMMUN_FAIL
ODU3_TCM2_EXC
ODU_SNCP_PS
HARD_BAD
ODU3_TCM3_AIS
ODU_SNCP_STA_INDI
HARD_ERR
ODU3_TCM3_BDI
OPU3_MSIM
IN_PWR_HIGH
ODU3_TCM3_DEG
OPU3_PLM
IN_PWR_LOW
ODU3_TCM3_LCK
OTU3_AIS
J0_MM
ODU3_TCM3_LTC
OTU3_BDI
LOOP_ALM
ODU3_TCM3_OCI
OTU3_DEG
LSR_FORCE_OPEN
ODU3_TCM3_SSF
OTU3_LOF
LSR_WILL_DIE
ODU3_TCM3_TIM
OTU3_LOM
NO_BD_SOFT
ODU3_TCM3_EXC
OTU3_SSF
NO_ELABEL
ODU3_TCM4_AIS
OTU3_TIM
NULL_SEND
ODU3_TCM4_BDI
OTU3_EXC
ODU3_PM_AIS
ODU3_TCM4_DEG
OUT_PWR_HIGH
ODU3_PM_BDI
ODU3_TCM4_LCK
OUT_PWR_LOW
TN53TSXL
Issue 02 (2011-10-31)

203
OptiX OSN 8800/6800/3800

2 Alarm List
ODU3_PM_DEG
ODU3_TCM4_LTC
PORT_MODULE_OFFLINE
ODU3_PM_LCK
ODU3_TCM4_OCI
PRBS_LSS
ODU3_PM_OCI
ODU3_TCM4_SSF
REM_SD
ODU3_PM_SSF
ODU3_TCM4_TIM
REM_SF
ODU3_PM_TIM
ODU3_TCM4_EXC
R_LOC
ODU3_PM_EXC
ODU3_TCM5_AIS
R_LOF
ODU3_TCM1_AIS
ODU3_TCM5_BDI
R_LOS
ODU3_TCM1_BDI
ODU3_TCM5_DEG
TD
ODU3_TCM1_DEG
ODU3_TCM5_LCK
TEMP_OVER
ODU3_TCM1_LCK
ODU3_TCM5_LTC
TEM_HA
ODU3_TCM1_LTC
ODU3_TCM5_OCI
TEM_LA
ODU3_TCM1_OCI
ODU3_TCM5_SSF
TF
ODU3_TCM1_SSF
ODU3_TCM5_TIM
WRG_BD_TYPE
ODU3_TCM1_TIM
ODU3_TCM5_EXC
ODU3_TCM1_EXC
ODU3_TCM6_AIS
2.2.111 VA1 Board Alarm List

TN11VA1
BD_STATUS
NO_BD_PARA
SUM_INPWR_HI
COMMUN_FAIL
NO_BD_SOFT
SUM_INPWR_LOW
HARD_BAD
NO_ELABEL
TEMP_OVER
HARD_ERR
OPA_FAIL_INDI
VOADATA_MIS
MODULE_TEMP_OVE
R
SPAN_LOSS_HIGH
WAVEDATA_MIS
MUT_LOS
SPAN_LOSS_LOW
WRG_BD_TYPE
BD_STATUS
OPA_FAIL_INDI
VOADATA_MIS
COMMUN_FAIL
SPAN_LOSS_HIGH
WAVEDATA_MIS
HARD_BAD
SPAN_LOSS_LOW
WRG_BD_TYPE
TN12VA1
Issue 02 (2011-10-31)

204
OptiX OSN 8800/6800/3800

HARD_ERR
2 Alarm List
TEMP_OVER
2.2.112 VA4 Board Alarm List

TN11VA4
BD_STATUS
NO_BD_PARA
SPAN_LOSS_LOW
COMMUN_FAIL
NO_BD_SOFT
TEMP_OVER
HARD_BAD
NO_ELABEL
VOADATA_MIS
HARD_ERR
OPA_FAIL_INDI
WAVEDATA_MIS
MODULE_TEMP_OVE
R
SPAN_LOSS_HIGH
WRG_BD_TYPE
BD_STATUS
OPA_FAIL_INDI
VOADATA_MIS
COMMUN_FAIL
SPAN_LOSS_HIGH
WAVEDATA_MIS
HARD_BAD
SPAN_LOSS_LOW
WRG_BD_TYPE
HARD_ERR
TEMP_OVER
TN12VA4
2.2.113 WMU Board Alarm List

BD_STATUS
MODULE_ADJUST_FAIL
PORTSWITCH_FAIL
COMMUN_FAIL
NO_BD_PARA
TEMP_OVER
HARD_BAD
NO_BD_SOFT
WAVELEN_OVER
HARD_ERR
NO_ELABEL
WRG_BD_TYPE
2.2.114 WSD9 Board Alarm List

TN11WSD9
Issue 02 (2011-10-31)
BD_STATUS
NO_BD_PARA
OMS_LOS_P
COMMUN_FAIL
NO_BD_SOFT
OMS_SSF
HARD_BAD
NO_ELABEL
OMS_SSF_O

205
OptiX OSN 8800/6800/3800

2 Alarm List
HARD_ERR
OMS_BDI
OMS_SSF_P
IN_PWR_HIGH
OMS_BDI_O
OPA_FAIL_INDI
IN_PWR_LOW
OMS_BDI_P
TEMP_OVER
MODULE_ADJUST_FAI
L
OMS_FDI
VOADATA_MIS
MOD_COM_FAIL
OMS_FDI_O
WAVEDATA_MIS
MUT_LOS
OMS_FDI_P
WRG_BD_TYPE
TN12WSD9/TN13WSD9
BD_STATUS
OMS_BDI_O
OPA_FAIL_INDI
COMMUN_FAIL
OMS_BDI_P
SUM_INPWR_HI
HARD_BAD
OMS_FDI
SUM_INPWR_LOW
HARD_ERR
OMS_FDI_O
TEMP_OVER
MODULEFILE_UPDATE_F
AIL
OMS_FDI_P
VOADATA_MIS
MODULE_ADJUST_FAIL
OMS_LOS_P
WAVEDATA_MIS
MOD_COM_FAIL
OMS_SSF
WRG_BD_TYPE
MUT_LOS
OMS_SSF_O
OMS_BDI
OMS_SSF_P
2.2.115 WSM9 Board Alarm List

TN11WSM9
BD_STATUS
MOD_COM_FAIL
TEMP_OVER
COMMUN_FAIL
NO_BD_PARA
VOADATA_MIS
HARD_BAD
NO_BD_SOFT
WAVEDATA_MIS
HARD_ERR
NO_ELABEL
WRG_BD_TYPE
MODULE_ADJUST_FAI
L
OPA_FAIL_INDI
TN12WSM9/TN13WSM9
Issue 02 (2011-10-31)

206
OptiX OSN 8800/6800/3800

2 Alarm List
BD_STATUS
L
TEMP_OVER
COMMUN_FAIL
MODULE_ADJUST_FAIL
VOADATA_MIS
HARD_BAD
MOD_COM_FAIL
WAVEDATA_MIS
HARD_ERR
OPA_FAIL_INDI
WRG_BD_TYPE
2.2.116 WSMD2 Board Alarm List

BD_STATUS
OMS_BDI_O
OPA_FAIL_INDI
COMMUN_FAIL
OMS_BDI_P
SUM_INPWR_HI
HARD_BAD
OMS_FDI
SUM_INPWR_LOW
HARD_ERR
OMS_FDI_O
TEMP_OVER
MODULEFILE_UPDATE_F
AIL
OMS_FDI_P
VOADATA_MIS
MODULE_ADJUST_FAIL
OMS_LOS_P
WAVEDATA_MIS
MOD_COM_FAIL
OMS_SSF
WRG_BD_TYPE
MUT_LOS
OMS_SSF_O
OMS_BDI
OMS_SSF_P

TN11WSMD4
Issue 02 (2011-10-31)
BD_STATUS
OMS_BDI_O
OPA_FAIL_INDI
COMMUN_FAIL
OMS_BDI_P
SUM_INPWR_HI
HARD_BAD
OMS_FDI
SUM_INPWR_LOW
HARD_ERR
OMS_FDI_O
TEMP_OVER
MODULEFILE_UPDATE_F
AIL
OMS_FDI_P
VOADATA_MIS
MODULE_ADJUST_FAIL
OMS_LOS_P
WAVEDATA_MIS
MOD_COM_FAIL
OMS_SSF
WRG_BD_TYPE
MUT_LOS
OMS_SSF_O
OMS_BDI
OMS_SSF_P

207
OptiX OSN 8800/6800/3800

2 Alarm List
TN12WSMD4
BD_STATUS
OMS_BDI
OMS_SSF_O
COMMUN_FAIL
OMS_BDI_O
OMS_SSF_P
HARD_BAD
OMS_BDI_P
OPA_FAIL_INDI
HARD_ERR
OMS_FDI
SUM_INPWR_HI
MODULEFILE_UPDATE_F
AIL
OMS_FDI_O
SUM_INPWR_LOW
MODULE_ADJUST_FAIL
OMS_FDI_P
TEMP_OVER
MOD_COM_FAIL
OMS_LOS_P
VOADATA_MIS
MUT_LOS
OMS_SSF
WRG_BD_TYPE

BD_STATUS
NO_ELABEL
OMS_SSF_P
COMMUN_FAIL
OMS_BDI
OPA_FAIL_INDI
HARD_BAD
OMS_BDI_O
SUM_INPWR_HI
HARD_ERR
OMS_BDI_P
SUM_INPWR_LOW
MODULEFILE_UPDATE_F
AIL
OMS_FDI
TEMP_OVER
MODULE_ADJUST_FAIL
OMS_FDI_O
VOADATA_MIS
MOD_COM_FAIL
OMS_FDI_P
WAVEDATA_MIS
MUT_LOS
OMS_LOS_P
WRG_BD_TYPE
NO_BD_SOFT
OMS_SSF
NO_BD_PARA
OMS_SSF_O
2.2.119 XCH Board Alarm List

TN52XCH
BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
TN16XCH
Issue 02 (2011-10-31)

208
OptiX OSN 8800/6800/3800

2 Alarm List
ALC_ADJUST_FAI
L
LCS_FILE_NOT_EXIST
SUBRACK_LOOP
ALC_WAIT_ADJUS
T
LTI
MS_APS_INDI_EX
SWDL_ACTIVATED_TI
MEOUT
NEBD_XC_DIF
SWDL_AUTOMATCH_I
NH
APS_FAIL
APS_INDI
Issue 02 (2011-10-31)
APS_MANUAL_ST
OP
NESF_LOST
SWDL_CHGMNG_NOMATCH
BD_NOT_INSTALL
ED
NESTATE_INSTALL
SWDL_BD_EXCLUDE
BD_STATUS
NODEID_MM
SWDL_COMMIT_FAIL
BOOTROM_BAD
NO_BD_SOFT
SWDL_INPROCESS
BUS_ERR
NO_ELABEL
SWDL_NEPKGCHECK
CFCARD_FAILED
NTP_SYNC_FAIL
SWDL_PKGVER_MM
CLK_NO_TRACE_
MODE
OOL
SWDL_PKG_NOBDSOFT
COMMUN_FAIL
PATCH_ACT_TIMEOUT
SWDL_ROLLBACK_FA
IL
CPC_NODE_ID_ER
R
PATCH_DEACT_TIMEOUT
SYNC_C_LOS
DBMS_ABNORMA
L
PATCH_PKGERR
SYNC_DISABLE
DBMS_ERROR
POWER_FAIL
SYNC_FAIL
DBMS_PROTECT_
MODE
RTC_FAIL
SYNC_F_M_SWITCH
DB_RESTORE_FAI
L
S1_SYN_CHANGE
SYNC_LOCKOFF
EXT_SYNC_LOS
SECU_ALM
SYN_BAD
EXT_TIME_LOC
SEC_RADIUS_FAIL
SYSLOG_COMM_FAIL
FEATURE_WITHO
UT_LICENSE
SERVICE_CAPACITY_EXCEED_
LICENSE
SYSPARA_CFDB_NOSAME
HARD_BAD
TEMP_OVER
HARD_ERR
TIME_LOS

209
OptiX OSN 8800/6800/3800

2 Alarm List
HSC_UNAVAIL
SNCP_FAIL
TIME_NO_TRACE_MO
DE
K1_K2_M
STORM_CUR_QUENUM_OVER
WRG_BD_TYPE
K2_M
SUBRACK_COMM_PS
XC_UNSWITCH
LCS_DAYS_OF_GR
ACE
SUBRACK_ID_CONFLICT
LCS_EXPIRED
SUBRACK_ID_MISMATCH
2.2.120 XCM Board Alarm List

TN52XCM
BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
2.2.121 XCS Board Alarm List

TN11XCS
BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
BD_STATUS
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE
HARD_BAD
NO_ELABEL
TN12XCS
2.2.122 XCT Board Alarm List
Issue 02 (2011-10-31)
BD_STATUS
HARD_BAD
NO_ELABEL
BUS_ERR
HARD_ERR
TEMP_OVER
COMMUN_FAIL
NO_BD_SOFT
WRG_BD_TYPE

210
OptiX OSN 8800/6800/3800

3 Common Alarm Processing
Common Alarm Processing
About This Chapter

This topic describes common information relevant to alarm handling, including alarm
descriptions, alarm parameters, impacts of alarms on the system, alarm causes, and alarm
handling procedures.
NOTE
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable opticallayer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on the
Optical Layer" in the Supporting Tasks.
NOTE
In the case of an alarm, see its handling procedure to clear it; if the alarm persists, contact Huawei engineers
for troubleshooting.
The alarm handling involves board reset, either cold or warm. Cold reset and warm reset have
different impacts on services.
l
Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software,
neither the FPGA file nor hardware data is updated and so a warm reset does not interrupt
services. A cold reset of the SCC might result in re-setting of the key hardware, such as
FPGA reloading; the upper-layer software need be restarted.
Reset of other boards: A warm reset on other boards does not affect running services while
a cold reset on other boards does. If such a board is reset incorrectly, the communication
between the board and the SCC is affected and even the services are interrupted.
Certain alarms listed in this topic are handled in different ways, because the board types are
different. This topic describes how to handle alarms in the OCS and OTN systems separately
according to the system where the board is located.
3.1 B1_EXC
Refer to the alarm page according to the type of the board that reports the alarm.
3.2 BEFFEC_EXC
3.3 BOOTROM_BAD
See the alarm page according to the type of the board that reports the alarm.
3.4 BUS_ERR
Issue 02 (2011-10-31)

211
OptiX OSN 8800/6800/3800

3.5 CHAN_LOS
3.6 CLIENT_PORT_PS
3.7 COMMUN_FAIL
3.8 ETH_8B10B_ERR
3.9 EX_ETHOAM_CC_LOS
3.10 FC_LINK_ERR
3.11 FC_SYNC_LOS
3.12 IN_PWR_HIGH
3.13 IN_PWR_LOW
3.14 INTRA_OTU_PS
3.15 LASER_MODULE_MISMATCH
3.16 LINK_ERR
3.17 LOOP_ALM
3.18 LPT_ACTIVE
3.19 LSR_WILL_DIE
3.20 MS_AIS
3.21 MS_RDI
3.22 MUT_LOS
3.23 OA_LOW_GAIN
3.24 ODU_SNCP_PS
3.25 ODUk_PM_AIS
3.26 ODUk_PM_BDI
3.27 ODUk_PM_DEG
3.28 ODUk_PM_EXC
3.29 ODUk_PM_SSF
3.30 OMS_FDI
3.31 OSC_LOS
Issue 02 (2011-10-31)

212
OptiX OSN 8800/6800/3800

3.32 OTS_LOS
3.33 OTUk_LOF
3.34 OTUk_SSF
3.35 OUT_PWR_HIGH
3.36 PORT_MODULE_OFFLINE
3.37 POWER_FAIL
3.38 PUMP_COOL_EXC
3.39 R_LOF
3.40 R_LOS
3.41 R_OOF
3.42 R_SLIP
3.43 REM_SF
3.44 REMOTE_FAULT
3.45 SECU_ALM
3.46 SUBRACK_ID_CONFLICT
3.47 SUM_INPWR_LOW
3.48 SWDL_NEPKGCHECK
3.49 TD
3.50 TEMP_OVER
3.51 TF
3.52 TS_CFG_MISMATCH
3.53 WRG_BD_TYPE
Issue 02 (2011-10-31)

213
OptiX OSN 8800/6800/3800

3.1 B1_EXC
Table 3-1 Alarm page link
Board Type
Alarm page link
SF64, SF64A, SFD64, SL64, SLD64,

SLQ16, SLQ64, SLH41, SLO16, or EGSH
3.1.1 B1_EXC (OCS)
Boards other than the SF64, SF64A, SFD64,

SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
3.1.2 B1_EXC (OTN)
3.1.1 B1_EXC (OCS)

Description
The B1_EXC (OCS) alarm indicates that the number of regenerator section B1 bit errors in the
signals received on the line exceeds the threshold. When a line board detects the B1 bytes and
determines that the bit error ratio (BER) of the regenerator section signals exceeds the threshold
for the B1_EXC alarm, the alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None
Impact on the System

l
When the B1_EXC occurs, the quality of the transmitted services is degraded.
When the B1_EXC occurs, by default, the system inserts the AU_AIS alarm in the crossconnection direction.
Possible Causes
The possible causes of the B1_EXC alarm are as follows:
l
Cause 1: The line performance degrades.
Cause 2: The external environment is abnormal.
Issue 02 (2011-10-31)

214
OptiX OSN 8800/6800/3800

Cause 3: The receive board of the local end is faulty.
Cause 4: The transmit board of the opposite end is faulty.
Query current alarms on the U2000. According to parameter 1, determine the ID of the
interface that reports the alarm. For details, see Querying the Current Alarms in the
Supporting Task.
Procedure
1.
Check whether the transmit power at the opposite station and the receive power at the
local station meet the specifications of the interfaces. For details on optical power
specification of the board, see"Technical Specifications" of the Product
Description. For details, see Querying Optical Power of the Board in the Supporting
Task.
NOTE
Refer to Querying Optical Module Information in the Supporting Task, and you can obtain the
manufacturer information about the board optical module.
2.
If...
Then...
The transmit optical power of the opposite station is

normal, but the receive optical power of the local
station is almost equal to the specification (for
example, within 3 dB) of the receiver sensitivity,
Proceed to the next step.
The transmit optical power of the local board is

abnormal,
See cause 4.
Check whether the optical connector is normal.

If...
Then...
The connector is loose
Tighten the optical connector. Check whether the alarm

is cleared. If the alarm persists, proceed to the next step.
The interface is normal Proceed to the next step.

3.
Issue 02 (2011-10-31)
Check whether the connector is dirty. For details, see Inspecting and Cleaning the
Fiber-Optic Connectors in the Supporting Task.

215
OptiX OSN 8800/6800/3800

If...
Then...
The connector is dirty
Clean the optical connector. For details, see

l Cleaning Optical Fiber Connectors Using Cartridge
Cleaners
l Cleaning Optical Fiber Connectors Using Lens
Tissue
l Cleaning Optical Adapters Using Optical Cleaning
Sticks
in Supporting Task. Then, check whether the alarm is
cleared. If the alarm persists, proceed to the next step.
The connector is normal Proceed to the next step.

4.
5.
If...
Then ...
The value of optical attenuation is

improper,
Adjust the attenuation to the proper

value. For details, see Adjusting,
Replacing, Adding and Removing
Attenuator in the Supporting Task. Then,
check whether the alarm is cleared. If the
alarm persists, proceed to the next step.

proper,
Check whether the fiber is faulty. Especially, check whether the bending radius of a
fiber jumper is within the normal range, and check whether the fiber from the
equipment to the ODF and the fiber outside the equipment room are pressed. If the
bending radius of the fiber jumper is less than 6 cm, spool the fiber jumper again. If
the fiber is faulty, replace it. Then, check whether the alarm is cleared. If the alarm
persists, see cause 2.

1.
Check the ambient temperature of the equipment room. If the temperature is higher
than 45C or is lower than 0C, use a cooler/heater to decrease/increase the ambient
temperature.
2.
Check whether the alarm is cleared. If the alarm persists, see cause 3.

1.
Issue 02 (2011-10-31)
Check whether the attenuation value of the optical attenuator is proper according to
the specified receive optical power. For details on optical power specifications of the
board, see "Technical Specifications" of the Product Description.
Perform an inloop on the receive and transmit ports of the board. Refer to Supporting
Task.

216
OptiX OSN 8800/6800/3800

CAUTION
The loopback may cause service interruptions.
If...
Then...
Any bit error alarm is reported, The local board is faulty. Proceed to the next
step.
No bit error alarm is reported,
See cause 4.
2.
If the board supports the pluggable optical module, replace the pluggable optical
module. Otherwise, replace the local faulty board. For details, see Parts
Replacement.
3.

1.
module. Otherwise, replace the faulty board at the opposite end. For details, see Parts
Replacement.
----End
Related Information
None.
3.1.2 B1_EXC (OTN)

Description
The B1_EXC (OTN) alarm indicates the regenerator section (B1) excessive errors. The alarm
is generated when the received SDH signals degrade and the B1 bit errors in the multiplex section
exceed the threshold.
Reported from the WDM side or client side: WDM side client side.
l
The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received
on the WDM side exceed the B1 bit error threshold.
The alarm is generated on the client side when the B1 bit errors in the SDH signals received
on the client side exceed the B1 bit error threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None
Issue 02 (2011-10-31)

217
OptiX OSN 8800/6800/3800


The B1 bit errors in the service signals received by the board exceed the threshold of the B1 bit
errors set for the board. The alarm affects the QoS of the service signals.
Fault Symptom
None.
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic, handle
the fault according to "Handling Procedure" provided in this topic.
Possible Causes
l
Cause 1 of this alarm generated on the client side: The input signals on the client side contain
B1 bit errors.
Cause 2 of this alarm generated on the client side: The board that reports this alarm is faulty.
Cause 1 of this alarm generated on the WDM side: The receive side of the local station
(Station B) is faulty.
Cause 2 of this alarm generated on the WDM side: The attenuation of the received signals
is excessively high; the fiber or connector is not clean.
Cause 3 of this alarm generated on the WDM side: The transmit side of the opposite station
(Station A) is faulty.
Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
Procedure
Detects and reports

the B1_EXC alarm
Detects and reports

the B1_EXC alarm
OTU1
O
A
D
M
F
I
U
F
I
U
O
A
D
M
WDM side Client side
Client side WDM side

Station A
OTU2
Out-loop
Station B
Cause 1 of this alarm generated on the client side: The input signals on the client side contain
B1 bit errors.
1.
If this alarm is reported from the client side of the board, apply a hardware loopback
between the transmit and receive optical ports on the client side of OTU1. If the alarm
on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case, see the
alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
Configuring a loopback on the board interrupts the services on the board.
Issue 02 (2011-10-31)

218
OptiX OSN 8800/6800/3800

2.
l
If the alarm is cleared, it indicates that the input signals on the client side of the board
contain B1 bit errors. In this case, rectify the fault on the client equipment.
Cause 2 of this alarm generated on the client side: The board that reports the alarm is faulty.
1.
Check whether the board that reports this alarm supports pluggable optical modules.
If ...
Then ...
The board supports pluggable optical Replace the specific pluggable optical
module. For details, refer to "Replacing
modules,
Pluggable Optical Modules" of the Parts
Replacement.
The board does not support
pluggable optical modules,
Replace the faulty board. For details, refer

to "Replacing a Board" of the Supporting
Tasks.
Cause 1 of this alarm generated on the WDM side: The receive side of the local station
(Station B) is faulty.
1.
Configure outloop at the transmit and receive optical ports on the WDM side of OTU2.
If there is no bit error alarm on the OTU1, it indicates that the board at the local station
(Station B) is faulty. Replace the faulty board.
If ...
Then ...
modules,
Replacement.

Tasks.
CAUTION
2.
l
If OTU1 has bit error alarms, see the alarm handling procedure for cause 2 of this
alarm generated on the WDM side.
Cause 2 of this alarm generated on the WDM side: The attenuation of the received signals
is excessively high; the fiber or connector is not clean.
1.
If there are bit errors, check the transmit optical power at the corresponding optical
ports on the opposite OTU1 on the U2000. For the optical power specification of the
specific board, refer to "Technical Specifications" of the Product Description.For
details, refer to "Querying Optical Power on the U2000" of the Supporting Tasks.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards"
of the Hardware Description to obtain the manufacturing information of the optical module
on the board.
Issue 02 (2011-10-31)

219
OptiX OSN 8800/6800/3800

2.
If the transmit optical power of the corresponding optical port on OTU1 is within the
normal range, check the attenuation of the transmission link between transmitting
module of OTU1 at the opposite station and the receiving module of OTU2 at the local
station. If the preset attenuation values are excessively large, correct them so that they
are within the normal range. For details, see "Adjusting, Replacing, Adding, and
Removing Attenuator" in the Supporting Tasks.
3.
If the alarm persists, check the fiber connectors at stations A and B separately. If the
fiber connectors are dirty, clean or replace them. For details, refer to "Inspecting and
Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
4.
If the alarm persists, check the fiber jumper. If the fiber jumper endures a large bending
radius or it is damaged or aging, adjust or replace the fiber jumper. For details, see
"Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are
normal, check the optical cables between stations to rectify the fault.
5.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling
procedure for cause 3 of this alarm generated on the WDM side.
Cause 3 of this alarm generated on the WDM side: The transmit side of the opposite station
(Station A) is faulty.
1.
If the transmit optical power of the corresponding optical port on OTU1 at the opposite
station is abnormal, it indicates that OTU1 is faulty. In this case, replace the board.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.2 BEFFEC_EXC
Description
This alarm indicates that signals are degraded before FEC. Signals sent from WDM sides of the
opposite-end OTU have the FEC function. As a result, before performing signal FEC in the
receive direction of WDM side of the local-end OTU, the local-end OTU counts the bit error
rate. This alarm occurs when the counted bit error rate crosses the threshold.
Reported from the WDM or client side: WDM side.
Issue 02 (2011-10-31)

220
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The error tolerance of the system decreases, which affects the quality of signals if the decrease
is sufficient.
Fault Symptom
Table 3-2 lists the fault symptom for the BEFFEC_EXC alarm.
Table 3-2 Fault symptom for the BEFFEC_EXC alarm
Fault Symptom
Cause
The NE that reports this alarm reports a

temperature alarm or fan fault alarm, such as
TEMP_OVER or FAN_FAIL, within a
certain time.
Cause 3 of this alarm in the case of multiple

wavelengths: The external environment is
improper.
NOTE
Possible Causes
The possible causes of the BEFFEC_EXC alarm are as follows:
l
Cause 1 of this alarm in the case of a single wavelength: The input optical power of the
OTU board is extremely high or low.
Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of
the interconnected OTUs are different.
Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board
and the multiplexer/demultiplexer board is faulty.
Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed.
Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm
is faulty.
Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station
is faulty.
Issue 02 (2011-10-31)

221
OptiX OSN 8800/6800/3800

Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables
between stations or the multiplexing portions inside a station are faulty.
Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals
during line transmission is excessively high.
Cause 3 of this alarm in the case of multiple wavelengths: The external environment is
improper.
Procedure
Step 1 Check the alarm information on the U2000 and record the IDs of the port and channel where the
alarm is generated.
Step 2 Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU
board is extremely high or low.
1.
Check whether the received optical power on the U2000 is within the normal range. For
the optical power specification of the specific board, refer to "Technical Specifications" of
the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks or "Bar Code for Boards" of
the Hardware Description to obtain the manufacturing information of the optical module on the
board.
2.
If the input optical power is abnormal, see the methods for handling the IN_PWR_HIGH
and IN_PWR_LOW alarms.
3.
If the input optical power is normal but the alarm persists, see the alarm handling procedure
for cause 2 of this alarm in the case of a single wavelength.
Step 3 Cause 2 of this alarm in the case of a single wavelength: The settings of the FEC mode of the
interconnected OTUs are different.
1.
On the U2000, check the settings of FEC mode of the two interconnected OTUs. If the
settings are different, change the settings to FEC or AFEC to ensure consistency. For details,
see "Setting the FEC Mode" in the Supporting Tasks.
2.
Check whether the alarm is cleared. If the alarm persists, see the alarm handling procedure
Step 4 Cause 3 of this alarm in the case of a single wavelength: The fiber between the OTU board and
the multiplexer/demultiplexer board is faulty.
1.
Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them.
For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting
Tasks.
2.
"Replacing Fiber Jumpers" in the Supporting Tasks.
3.
Step 5 Cause 4 of this alarm in the case of a single wavelength: An inappropriate DCM is installed.
1.
Check whether the DCM used on the existing network is appropriate. If not, replace the
DCM.
2.
Issue 02 (2011-10-31)

222
OptiX OSN 8800/6800/3800

Step 6 Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm is
faulty.
1.
2.
Replace the board that reports this alarm.

If ...
Then ...
The board supports pluggable optical

modules,
Replace the specific pluggable optical

Replacement.
The board does not support pluggable

optical modules,
Replace the faulty board. For details, refer to

"Replacing a Board" of the Supporting
Tasks.
Step 7 Cause 6 of this alarm in the case of a single wavelength: The board at the opposite station is
faulty.
1.
2.
Replace the OTU board at the opposite station.

If ...
Then ...
The board supports pluggable optical

modules,
Replace the specific pluggable optical

Replacement.
The board does not support pluggable

optical modules,
Replace the faulty board. For details, refer to

Tasks.
Step 8 Cause 1 of this alarm in the case of multiple wavelengths: Fibers in the optical cables between
stations or the multiplexing portions inside a station are faulty.
1.
Check the related fiber connectors. If the fiber connectors are dirty, clean or replace them.
For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of the Supporting
Tasks.
2.
"Replacing Fiber Jumpers" in the Supporting Tasks. If the fibers inside a station are normal,
check the optical cables between stations to rectify the fault.
3.
for cause 2 of this alarm in the case of multiple wavelengths.
Step 9 Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals during
line transmission is excessively high.
1.
Issue 02 (2011-10-31)
Check the attenuation of the multiplexing portions inside a station and the line attenuation
between stations section by section. If the preset attenuation values are excessively large,
correct them so that they are within the normal range. For details, refer to "Adjusting,
Replacing, Adding and Removing Attenuator" of the Supporting Tasks.
223
OptiX OSN 8800/6800/3800

2.
for cause 3 of this alarm in the case of multiple wavelengths.
Step 10 Cause 3 of this alarm in the case of multiple wavelengths: The external environment is improper.
1.
Check the ambient temperature inside the telecommunications room, the cleanliness of the
air filter, and the heat dissipation conditions of each fan. For details, see the procedure for
handling the TEMP_OVER alarm.
2.
Check whether the alarm is cleared. If the alarm persists, check whether external
electromagnetic interference exists. For example, whether there is external electronic
equipment, whether the power supply is instable, and whether the lightning electromagnetic
interference exists, or whether a high-voltage output cable generates electromagnetic
interference. If yes, take corresponding measures to withstand the electromagnetic
interference.
3.
----End
Related Information
Related Cases:
l
MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets Close
to the Threshold
MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm
BEFFEC_EXC Is Detected on the Newly-added LWFS Board
MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board
help/wdm/com/mc/tt_wdm_mc_0237.xml#tt_wdm_mc_0237
None.
3.3 BOOTROM_BAD
Board Type
Alarm Page Link

3.3.1 BOOTROM_BAD (OCS)

SLO16, or EGSH
3.3.2 BOOTROM_BAD (OTN)
3.3.1 BOOTROM_BAD (OCS)

Issue 02 (2011-10-31)

224
OptiX OSN 8800/6800/3800

Description
The BOOTROM_BAD (OCS) is an alarm indicating the BOOTROM data check failure. During
the running of board software, the system periodically checks whether the BOOTROM data is
damaged. This alarm is generated when the BOOTROM data is detected damaged.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name
Meaning
Parameter 1
Indicates the type of the BIOS damage.

l 0x01: basic BIOS damaged
l 0x02: extended BIOS damaged

l
If the board has been started, the BOOTROM_BAD alarm does not affect the system or
the services.
If you perform cold reset on the board when there is the BOOTROM_BAD alarm, the board
fails to load BIOS and cannot be started.
Possible Causes
The possible causes of the BOOTROM_BAD alarm are as follows:
l
The basic BIOS is damaged.
The extended BIOS is damaged.
The BOOTROM data area is damaged.
Procedure
Step 1 View the BOOTROM_BAD alarm on the U2000 and determine the relevant board.
Step 2 Replace the board. If the board has been started, do not replace the board. Replacing the board
can interrupt services, whereas the BOOTROM_BAD alarm does not affect the system or the
services.
----End
Issue 02 (2011-10-31)

225
OptiX OSN 8800/6800/3800

Related Information
None
3.3.2 BOOTROM_BAD (OTN)

Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm
occurs when the basic or extended BIOS software of the board is damaged.
Reported from the WDM side or client side: NA
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameters 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software.
0x02 indicates the extended BIOS software.

When powered on again or reset after a power supply failure, the SCC board cannot be normally
started.
Fault Symptom
None
NOTE
Possible Causes
l
Cause 1: The basic BIOS software of the board is damaged.
Cause 2: The extended BIOS software of the board is damaged.
Cause 3: The SCC board is faulty.
Issue 02 (2011-10-31)

226
OptiX OSN 8800/6800/3800

Procedure
l
Determine upon the alarm parameter (0x01 indicates the basic BIOS while 0x02 the
extended BIOS) whether the basic or extended BIOS software of the board is damaged.
Cause 1: The basic BIOS software of the board is damaged.
1.
Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the
Parts Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
Cause 2: The extended BIOS software of the board is damaged.

1.
Reload the extended BIOS of the SCC board. For details, see the Version Upgrade
Guide.
2.
procedure for cause 3.
NOTE
The BIOS detection interval is 24 hours. Therefore, the BOOTROM_BAD alarm is displayed
24 hours later if the alarm persists after you reload the extended BISO.
Cause 3: The SCC board is faulty.

1.
Replace the faulty SCC board. For details, refer to "Replacing the SCC Board" of the
Parts Replacement.
2.
----End
Related Information
None
3.4 BUS_ERR
Board Type
Alarm Page Link

3.4.1 BUS_ERR (OCS)

SLO16, or EGSH
3.4.2 BUS_ERR (OTN)
3.4.1 BUS_ERR (OCS)
Issue 02 (2011-10-31)

227
OptiX OSN 8800/6800/3800

Description
The BUS_ERR (OCS) is an alarm indicating the bus error. This alarm is generated when the
board detects a backplane bus error.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of slot that houses the cross-connect board.
Parameters 2 and 3
Indicates the statuses of buses.

l
When the BUS_ERR alarm is reported, the services that pass through the relevant bus are
interrupted or have bit errors.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l
Cause 1: The internal bus of the cross-connect board is faulty.
Cause 2: The software version does not match the specified version.
Cause 3: The backplane or the relevant board is faulty.
Query current alarms on the U2000. For details, see Querying the Current Alarms in the
Supporting Task.
Cause 1: The internal bus of the cross-connect board is faulty.
Procedure
1.
Issue 02 (2011-10-31)
Replace the cross-connect board. For details, see the Parts Replacement.

228
OptiX OSN 8800/6800/3800

CAUTION
If no cross-connect board that works normally can be used for protection, do not
perform the operations, because all the services may be interrupted.
l
Cause 2: The software version does not match the specified version.
1.
Check whether the version of the cross-connect board matches the version of relevant
service board. For details, see Querying the Version of the Board in the Supporting
Task.
2.
If the versions of the cross-connect board and relevant service board do not match,
contact Huawei engineers to upgrade the relevant boards.
Cause 3: The backplane or the relevant board is faulty.

1.
Perform cold reset on the service board that maps the cross-connect board by using
the U2000, or reseat the service board that maps the cross-connect board. For the
operations that are performed on the U2000, see Performing a Cold Reset of a Board
in the Supporting Task. For the operations of reseating the board, see the Installation
Guide. Then, check whether the alarm is cleared.
2.
If the alarm persists, replace the service board. For details, see the Parts
Replacement.
CAUTION
If the services that travel through the service board are not protected, do not perform
the cold reset or replace the board because services may be interrupted.
3.
Perform cold reset on the cross-connect board by using the U2000, or reseat the crossconnect board. Then, check whether the alarm is cleared.
4.
If the alarm persists, replace the cross-connect board. For details, see the Parts
Replacement. Then, check whether the alarm is cleared.
CAUTION
If no cross-connect board that works normally can be used for protection, do not
perform the operations, because all the services may be interrupted.
5.
If the alarm persists, contact Huawei engineers to check whether the fault is caused
by bent pins of the backplane. If the backplane is faulty, replace the backplane of the
subrack.
----End
Related Information
None
Issue 02 (2011-10-31)

229
OptiX OSN 8800/6800/3800

3.4.2 BUS_ERR (OTN)

Description
The BUS_ERR is an alarm indicating the bus error. This alarm is generated when the board
detects a backplane bus error.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment
Parameters
table.
Parameter
Description
Parameters 1 and 2
Indicates the ID of the bus in which the alarm is generated.

l
In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, this alarm triggers the
bus switching. For example, if the bus from cross-connect board 9 contains a BUS_ERR
alarm while the bus from cross-connect board 10 does not, services are switched to the bus
from cross-connect board 10.
Services are unavailable or bit errors are generated. For example, ODU1 and GE services
of the OptiX OSN 6800 are affected and ODU1 and ODU0 services of the OptiX OSN
8800 are affected.
Fault Symptom
None
NOTE
Possible Causes
l
Cause 1: The OTU board is inserted inappropriately or faulty.
Cause 2: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, the crossconnect board is inserted inappropriately or faulty.
Issue 02 (2011-10-31)

230
OptiX OSN 8800/6800/3800

Cause 3: When ASON services are configured, the type of the service that is actually
received does not match the service type configured on the board.
Cause 4: The pins are faulty or the bus is faulty on the backplane.
Cause 1: The OTU board is inserted inappropriately or faulty.
Procedure
1.
Reseat the OTU board. For the operation of reseating the board, see the Installation
Guide. In the case of the OptiX OSN 6800 equipment, see "Removing Boards" and
"Inserting Boards". In the case of the OptiX OSN 3800 equipment, see "Removing
Boards" and "Inserting Boards".In the case of the OptiX OSN 8800 equipment, see
"Removing Boards" and "Inserting Boards". .
2.
Check whether the alarm is cleared. If the alarm persists, replace the board. For details,
see the Parts Replacement.
Cause 2: In the case of the OptiX OSN 6800 or OptiX OSN 8800 equipment, the crossconnect board is inserted inappropriately or faulty.
1.
Reseat the cross-connect board. For operations, see Removing Boards in the
Installation Guide and Inserting Boards in the Installation Guide.
2.
Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
board. For details, see the Parts Replacement.
Cause 3: When ASON services are configured, the type of the service that is actually
received does not match the service type configured on the board.
1.
Check whether board that reports this alarm supports pluggable optical modules.
If...
Then...
modules,
Replacement.
2.
l

Tasks.
Check whether this alarm is cleared. If the alarm persists, see the alarm handling
Cause 4: The pins are faulty or the bus is faulty on the backplane.
1.
Perform a cold reset on the faulty board through the U2000.
2.
If the alarm persists, replace the backplane of the subrack. For the detailed operations,
contact Huawei engineers.
----End
Related Information
None
Issue 02 (2011-10-31)

231
OptiX OSN 8800/6800/3800

3.5 CHAN_LOS
Description
The CHAN_LOS alarm indicates the single wavelength signal loss. The alarm is generated when
the MCA (optical spectrum analyzer) board detects that the original channel is lost after it scans
the optical spectrum.
Reported from the WDM side or client side: NA.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

l
The services of the related wavelength are unavailable.
The MCA cannot monitor the optical spectrum performance of the wavelength related to
the alarm.
Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1: The wavelength that needs to be monitored is not received. For example, in the
following figure, 1 wavelength needs to be monitored as configured, but actually 1
wavelength is not accessed. The possible cause is that the fiber to the client or WDM side
of the OTU1 is connected.
MCA
1
OTU1
2
OTU2
Client side
WDM side
M
U
X
/
D
M
U
X
Station A
Issue 02 (2011-10-31)
OA
OA
F
I
U
F
I
U
M
U
X
/
D
M
U
X
OA
OA
1
OTU3
2
OTU4
WDM side
Client side
Station B

232
OptiX OSN 8800/6800/3800

Cause 2: The laser of the board at the opposite station is shut down. For example, the laser
of OTU1 in the preceding figure is shut down.
Cause 3: The optical power difference between the monitored wavelengths is excessively
large. (For example, the optical power difference between 1 and 2 is excessively large.)
Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is
excessively high.
Cause 5: The OTU board located before the MCA is faulty. For example, OTU1 in the
preceding figure is faulty.
Cause 6: The MCA that reports the alarm is faulty.
Cause 1: The wavelength that needs to be monitored is not received.
Procedure
1.
Check whether the wavelength where the alarm is generated is required in the actual
network. If not, modify the wavelength monitoring configuration of the MCA so that
the monitoring of the wavelength is disabled.
2.
If the wavelength needs to be accessed in the actual network, check the fiber
connection in the upstream stations along the signal flow so that the fiber connection
is established properly.
3.
Cause 2: The laser of the board at the opposite station is shut down.
1.
Check whether the laser of the OTU that transmits the wavelength is shut down. If the
laser is shut down, opening the Laser.
2.
Cause 3: The optical power difference between the monitored wavelengths is excessively
large.
1.
Query whether the system is configured with the APE function. If yes, enable the APE
function to re-adjust the optical power of each wavelength. For detailed operations,
see "Automatic Power Equilibrium (APE)" in the Feature Description.
2.
If the system is not configured with the APE function, manually enable the adjustment
of a single wavelength and adjust the optical power of the wavelength with excessively
large difference, ensuring that the optical power is flat.
3.
Cause 4: The attenuation of the multiplexer or OA unit interconnected with the MCA is
excessively high.
1.
Issue 02 (2011-10-31)
Query the output optical power of the upstream OTU board connected to the
multiplexer unit. Check whether the output optical power of the upstream OTU board
is within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description.

233
OptiX OSN 8800/6800/3800

NOTE
on the board.
2.
Query the alarms reported by the MCA input optical power of the optical interface,
and then calculate the output optical power of the upstream multiplexer or OA unit to
determine whether it is within the normal range. For the optical power specification
of the specific board, refer to "Technical Specifications" of the Product
Description.If the optical power is extremely low or there is no light, check the
attenuation that is set for the input optical power on the multiplexer or OA unit. If the
attenuation is very high, decrease the attenuation for the multiplexer or OA unit.
NOTE
Output optical power of the multiplexer or OA unit (dBm) = Input optical power at the IN port
on the MCA (dBm) - 10lg("MON"/"OUT") (dBm). "MON"/"OUT" represents the split ratio
of the MON port on the multiplexer or OA unit. For details, see "MON Interface Optical Split
Ratio" in the Hardware Description.
3.
l
Cause 5: The OTU in the upstream direction of the MCA is faulty.

1.
Replace the OTU that transmits the wavelength to the MCA.

If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
Cause 6: The MCA that reports the alarm is faulty.

1.
Use an optical spectrum analyzer to analyze the optical spectrum data of the
corresponding optical interface on the MCA. If the data is normal, perform a cold reset
on the MCA.
2.
If the alarm persists, replace the MCA that reports the alarm. For details, refer to
"Replacing a Board" of the Supporting Tasks.
3.
----End
Related Information
None.
Issue 02 (2011-10-31)

234
OptiX OSN 8800/6800/3800

3.6 CLIENT_PORT_PS
Description
The CLIENT_PORT_PS alarm indicates the client-side 1+1 protection switching. This alarm
occurs when the client-side 1+1 protection group actuates switching in which the current channel
switches to the protection channel from the working channel.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the client-side 1+1 protection group actuates switching, services are transiently
interrupted. When this alarm is reported, the working channel of the client-side 1+1 protection
group might have faulty services that needs to be restored.
Fault Symptom
Table 3-5 lists the fault symptoms for the CLIENT_PORT_PS alarm.
Table 3-5 Fault symptoms for the CLIENT_PORT_PS alarm
Fault Symptom
Cause
A protection switching is performed, but

there is no alarm that can trigger a protection
switching.
Cause 1: A user issues an external switching

command such as forced switching or manual
switching.
A protection switching is performed, and the

board on the working channel reports alarms
that can trigger a protection switching. For
details about the alarm information, see
Table 3-6.
Cause 2: The services of the working channel

of the client-side 1+1 protection group are
faulty. The current channel automatically
switches to the working channel and the
alarm is reported.
NOTE
Issue 02 (2011-10-31)

235
OptiX OSN 8800/6800/3800

Possible Causes
l
Cause 1: A user issues an external switching command such as forced switching or manual
switching. Such a command makes the current channel of the client-side 1+1 protection
group switch to the protection channel from the working channel. Hence, the alarm is
reported.
Cause 2: The services of the working channel of the client-side 1+1 protection group are
faulty. The current channel automatically switches to the working channel and the alarm
is reported.
switching.
Procedure
1.
On the U2000, query the switching state of the protection group. If the switching state
is forced switching or manual switching, check whether the external switching
operation is necessary.
2.
If the external switching operation is necessary, ignore the alarm.
3.
If the external switching operation is unnecessary, issue an external command to

switch the current channel to the working channel, thus clearing the alarm.
Cause 2: The services of the working channel of the client-side 1+1 protection group are
is reported.
1.
Query whether the related boards for configuring the protection group have alarms
relevant to the services. If yes, handle the alarms by referring to the alarm handling
procedure. For details about the alarm information, see Table 3-6.
2.
If the alarm persists, check whether the attribute of the protection group is
Revertive. If yes, the current channel automatically switches to the working channel
and the alarm clears. If the attribute is Non-Revertive, set it to Revertive and the
alarm clears.
3.
----End
Related Information
Table 3-6 lists the alarms that can trigger a protection switching.
Table 3-6 Related Alarms
Issue 02 (2011-10-31)
R_LOF
OTUk_TIM
IN_PWR_HIGH
R_LOS
ODUk_PM_AIS
IN_PWR_LOW
R_LOC
ODUk_PM_OCI
ODUk_PM_DEG
HARD_BAD
ODUk_PM_LCK
ODUk_PM_EXC
OTUk_LOF
ODUk_PM_TIM
OTUk_DEG
OTUk_LOM
REM_SF
OTUk_EXC

236
OptiX OSN 8800/6800/3800

OTUk_AIS
B1_EXC
REM_SD
For details, see "Client 1+1 Protection" in the Feature Description.
3.7 COMMUN_FAIL
Board Type
Alarm page link

3.7.1 COMMUN_FAIL (OCS)

SLO16, or EGSH
3.7.2 COMMUN_FAIL (OTN)
3.7.1 COMMUN_FAIL (OCS)

Description
The COMMUN_FAIL (OCS) is an alarm indicating an inter-board communication failure. This
alarm is reported when the communication between the SCC and other boards is interrupted.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

237
OptiX OSN 8800/6800/3800

Parameter
Description
Parameters 1 and 2 Indicates the ID of the channel in which the alarm is generated. For
example,
0x00 0x01 indicates RS485 path 1.
0x00 0x02 indicates RS485 path 2.
0x00 0x03 indicates intra-board communication.
0x00 0x04 indicates the Ethernet emergency channel between subracks.

When the alarm is generated, the SCC cannot send commands or services to the board, or the
board cannot work. In this case, the service cannot be configured or the protection switching
becomes invalid. Thus, the new service becomes abnormal.
Possible Causes
The possible causes of the COMMUN_FAIL alarm are as follows:
l
Cause 1 of a single board reporting this alarm: The board is in the cold reset or warm reset
state.
Cause 2 of a single board reporting this alarm: The board is faulty.
Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
NOTE
If the communication ports between the AUX board and other boards are faulty, the service board
reports the COMMUN_FAIL alarm while the standby SCC board does not report the alarm.
Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board
is faulty.
NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service board report
the COMMUN_FAIL alarm at the same time.
If the cross-connect board is faulty, the communication in the 485 path is faulty. The cross-connect
board and the service board report the COMMUN_FAIL alarm.
Procedure
l
Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter. For details, see Querying the Current Alarms in the
Supporting Task.
Cause 1 of a single board reporting this alarm: The board status is cold reset or warm reset.
l
Issue 02 (2011-10-31)
1.
Check the board alarm indicator to see whether the status of the board that reports the
alarm is cold reset or warm reset. Wait for 5 minutes if the status is cold reset or warm
reset, and then check whether the alarm is cleared. For the description of the alarm
indicators on the board, see Board Indicators in the Hardware Description.
2.
If the alarm persists, see Cause 2 of a single board reporting this alarm.

238
OptiX OSN 8800/6800/3800

1.
l
Replace the board that reports the alarm. For details, see the Parts Replacement.
Cause 1 of multiple boards reporting this alarm: The service board AUX is faulty.
1.
Check whether the AUX board reports the alarm that indicates a board or chip fault
such as the BD_STATUS alarm. Reseat the board. For the operations of reseating a
board, see the Installation Guide. Then, check whether the COMMUN_FAIL alarm
is cleared.
2.
If the alarm persists, replace the board. For details, see the Parts Replacement. Then,
check whether the COMMUN_FAIL alarm is cleared.
3.
If the alarm persists, see Cause 2 of multiple boards reporting alarm.
Cause 2 of multiple boards reporting this alarm: The SCC board or the cross-connect board
is faulty.
1.
Check whether the active SCC board or the active cross-connect board reports the
alarm such as the BD_STATUS or HARD_BAD alarm that indicates a board fault.
Reseat the board. For the operations of reseating a board, see the Installation Guide.
Then, check whether the COMMUN_FAIL alarm is cleared.
2.
If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
3.7.2 COMMUN_FAIL (OTN)

Description
The COMMUN_FAIL is an alarm indicating an inter-board communication failure. This alarm
occurs when the communication between the SCC and other boards is interrupted.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1
Indicates the optical port number and the value is always 0x01.
Issue 02 (2011-10-31)

239
OptiX OSN 8800/6800/3800

Parameter
Description
Parameters 2 and 3 Indicates the ID of the channel in which the alarm is generated. For
example,
0x00 0x01 denotes RS485 path 1;
0x00 0x03 denotes intra-board communication;
0x00 0x04 denotes the Ethernet emergency channel between subracks.
0x00 0x05 denotes the spi communication failure between the SCC board
and AUX board.

After the alarm is generated, configuration data fails to be applied to other boards or other boards
cannot function normally. The service configuration or protection switching may fail or the
package loading may roll back abnormally. Thus, new services become abnormal.
Fault Symptom
Table 3-8 lists the fault symptom for the COMMUN_FAIL alarm.
Table 3-8 Fault symptom for the COMMUN_FAIL alarm
Fault Symptom
A single board reports the
COMMUN_FAIL alarm.
The alarm parameter is 0x01
0x00 0x03.
Cause
l The board also reports the
BD_STATUS alarm
(only when the board is in
cold reset state).
Cause 1 of a single board

reporting this alarm: The
board is in cold reset or warm
reset state.
l The PROG indicator on

the board blinks first at
the frequency of 300 ms
on and 300 ms off (green)
and then at the frequency
of 100 ms on and 100 ms
off (green).
No other symptoms occur.
Issue 02 (2011-10-31)


board is faulty.
240
OptiX OSN 8800/6800/3800

Fault Symptom
A single board reports the
COMMUN_FAIL alarm.
Cause
No other symptoms occur.

board is faulty.
The network cables for

cascading subracks are selfmade network cables rather
than standard straightthrough cables with all eight
cores being used.

network cables for cascading
subracks do not meet the
requirements.
l The standby SCC board

does not report the
COMMUN_FAIL alarm.
Cause 1 of multiple boards

reporting this alarm: For
OptiX OSN 6800 and OptiX
OSN 3800: The AUX board
is faulty. For OptiX OSN
8800: The EFI1 or EFI2
board is faulty.

0x00 0x01 or 0x01 0x00
0x02.
The SCC board of a slave
subrack reports the
COMMUN_FAIL alarm.
0x00 0x04.
Multiple boards report the
COMMUN_FAIL alarm.
0x00 0x03.
l For OptiX OSN 6800 and

OptiX OSN 3800: The
AUX board reports the
BD_STATUS alarm.
l For OptiX OSN 8800:
The EFI1 or EFI2 board
reports the BD_STATUS
alarm.
l The boards that report the
COMMUN_FAIL alarm
are housed in slave
subracks.
l The SUBRACK_LOOP
alarm is generated on the
NE, or the
SUBRACK_ID_CONFLICT or
SUBRACK_ID_MISMATCH alarm is
generated in the housing
subracks of the boards
that report the
COMMUN_FAIL alarm.
Issue 02 (2011-10-31)


settings of the DIP switches
of the subracks are incorrect
or the subracks are cascaded
inappropriately.
241
OptiX OSN 8800/6800/3800

Fault Symptom
Cause
l The active and standby
SCC boards report the
COMMUN_FAIL alarm
at the same time.

SCC or cross-connect board
is faulty.
l The active SCC board

also reports alarms such
as HARD_BAD and
BD_STATUS, indicating
abnormal equipment
status.
Multiple boards report the
COMMUN_FAIL alarm.
0x00 0x01 or 0x01 0x00
0x02.
l The cross-connect board

reports the
COMMUN_FAIL alarm.
l The cross-connect board
also reports alarms such
as BD_STATUS,
indicating abnormal
equipment status.

SCC or cross-connect board
is faulty.
NOTE
Possible Causes
The possible causes of a single board reporting the COMMUN_FAIL alarm are as follows:
l
Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset
state.
Cause 2 of a single board reporting this alarm: The network cables for cascading subracks
do not meet the requirements.
The possible causes of multiple boards reporting the COMMUN_FAIL alarm are as follows:
l
Cause 1 of multiple boards reporting this alarm: For OptiX OSN 6800 and OptiX OSN
3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
NOTE
When the ports on the AUX board for communicating with other boards are faulty, the services boards
report the COMMUN_FAIL alarm but the standby SCC board does not report this alarm.
Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the
subracks are incorrect or the subracks are cascaded inappropriately.
Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
Issue 02 (2011-10-31)

242
OptiX OSN 8800/6800/3800

NOTE
If the active SCC board is faulty, the active SCC board, standby SCC board, and service boards report
the COMMUN_FAIL alarm at the same time.
If the cross-connect board is faulty, the communication on channel 485 fails. In this case, the crossconnect board and service boards report the COMMUN_FAIL alarm at the same time.
Procedure
l
Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter. For details, refer to "Querying the Current Alarms and
Performance Events of a NE on the U2000" of the Supporting Tasks.
Cause 1 of a single board reporting this alarm: The board is in cold reset or warm reset
state.
1.
View the alarm indicators of the board to check whether the board that reports this
alarm is in warm reset or cold reset state. If yes, wait for five minutes and then check
whether the alarm is cleared. For the description of the alarm indicators on the board,
see the Hardware Description.
2.
If the alarm persists, see cause 2 of a single board reporting this alarm.
Cause 2 of a single board reporting this alarm: The network cables for cascading subracks
do not meet the requirements.
1.
Replace the network cables for cascading subracks with standard straight-through
network cables with all eight cores being used. Then check whether the alarm is
cleared.
2.
If the alarm persists, see cause 3 of a single board reporting this alarm.

1.
Replace the board that reports the alarm. For details, refer to "Replacing a Board" of
the Supporting Tasks.
2.
Cause 1 of multiple boards reporting this alarm: For OptiX OSN 6800 and OptiX OSN
3800: The AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty..
For OptiX OSN 6800 and OptiX OSN 3800: The AUX board is faulty.
1.
Check whether the AUX board also reports alarms such as BD_STATUS, indicating
abnormal board status. Reseat the board. For the operation of reseating the board, see
the Installation Guide. In the case of the OptiX OSN 6800 equipment, see "Removing
Boards" and "Inserting Boards". In the case of the OptiX OSN 3800 equipment, see
"Removing Boards" and "Inserting Boards".
2.
Check whether the alarm is cleared. If the alarm persists, replace the AUX board. For
details, refer to "Replacing the AUX Board" of the Parts Replacement.
3.
Check whether the alarm is cleared. If the alarm persists, see cause 2 of multiple boards
reporting this alarm.
For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
Issue 02 (2011-10-31)
1.
Check whether the EFI1 or EFI2 board also reports alarms such as BD_STATUS,
indicating abnormal board status. Reseat the board. For the operation of reseating the
board, see "Removing Boards" and "Inserting Boards" in the Installation Guide.
2.
Check whether the alarm is cleared. If the alarm persists, replace the EFI1 or EFI2
board. For details, refer to "Replacing the EFI Board" of the Parts Replacement.
243
OptiX OSN 8800/6800/3800

3.
l
Cause 2 of multiple boards reporting this alarm: The settings of the DIP switches of the
subracks are incorrect or the subracks are cascaded inappropriately.
1.
Check whether the SUBRACK_LOOP, SUBRACK_ID_CONFLICT, and

SUBRACK_ID_MISMATCH alarms are generated. If yes, process these alarms in
advance.
2.
Cause 3 of multiple boards reporting this alarm: The SCC or cross-connect board is faulty.
1.
Check whether the active SCC or active cross-connect board also reports the
BD_STATUS and HARD_BAD alarms. Reseat the board. For the operation of
reseating the board, see the Installation Guide. In the case of the OptiX OSN 6800
equipment, see "Removing Boards" and "Inserting Boards". In the case of the OptiX
OSN 3800 equipment, see "Removing Boards" and "Inserting Boards".In the case of
the OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting Boards".
2.
Check whether the alarm is cleared. If the alarm persists, replace the relevant board.
See For details, refer to "Replacing a Board" of the Supporting Tasks.
3.
----End
Related Information
None
3.8 ETH_8B10B_ERR
Description
This alarm indicates an Ethernet line signal encoding/decoding error. The alarm occurs when
signals are converted from 8bit mode to 10bit mode.
Reported from the WDM side or client side: Client side
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The coding and encoding error of the signals on the Ethernet line may lead to the bit errors. If
this alarm is consecutively generated for a long time, the service may be interrupted.
Issue 02 (2011-10-31)

244
OptiX OSN 8800/6800/3800

Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1: The fiber between the access equipment and the optical interface on the client side
of the board is faulty.
Cause 2: The access equipment is faulty.
Cause 3: The board hardware is faulty.
Cause 1: The fiber between the access equipment and the optical interface on the client side
of the board is faulty.
Procedure
1.
Check whether the attenuation of the fiber between the input equipment and the
interface on the client side of the board is overlarge, and whether the fiber is aged or
loose. If that is the case, clean the fiber connector or replace the fiber.
2.
Cause 2: The access equipment is faulty.

1.
Apply a hardware loopback between the transmit and receive optical interfaces on the
client side of the board. If the alarm persists, it indicates that the board is faulty. In
this case, replace the board.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
If the alarm is cleared, it indicates that the access equipment on the client side is faulty.
In this case, rectify the fault on the access equipment.
Cause 3: The board hardware is faulty.

1.
Replace the faulty board.

If ...
Then ...
modules,
Replacement.
Issue 02 (2011-10-31)

245
OptiX OSN 8800/6800/3800

2.
If ...
Then ...


Tasks.
If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.9 EX_ETHOAM_CC_LOS
Board Type
Alarm page link

3.9.1 EX_ETHOAM_CC_LOS (OCS)

SLO16, or EGSH
3.9.2 EX_ETHOAM_CC_LOS (OTN)
3.9.1 EX_ETHOAM_CC_LOS (OCS)

Description
The EX_ETHOAM_CC_LOS (OCS) alarm indicates the loss of the periodic continuity check
(CC) message. When the sink maintenance point receives the CC message from the source
maintenance point, the timer is started to periodically check the link between the source and sink
maintenance points. If the sink maintenance point does not receive the CC message from the
source maintenance point in one period (3.5 times the time the CC message is transmitted from
the source maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
Issue 02 (2011-10-31)

246
OptiX OSN 8800/6800/3800


table.
Name
Meaning
Parameters 1 and 2 Indicates the VLAN ID, consisting of two bytes.

Parameter 3
Indicates the level of the maintenance domain, consisting of one byte.
Parameters 4 to 7
Indicates the ID of the local maintenance point, consisting of four bytes.
Parameters 8 to 12 Indicates the ID of the remote maintenance point, consisting of five bytes.

When the EX_ETHOAM_CC_LOS alarm is generated, it indicates that a unidirectional
connectivity failure is detected on the link between the source and sink maintenance points.
Possible Causes
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
l
A software or hardware failure occurs to the services from the source maintenance point
to the sink maintenance point.
Service congestion or service interruption occurs between the source maintenance point
and the sink maintenance point.
Procedure
Step 1 View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the relevant
maintenance point according to the alarm parameters.
Step 2 Query the information about the maintenance point.
Step 3 Perform loopback (LB) and link trace (LT) test for the source and sink maintenance points, thus
to locate the fault in the services between the source maintenance point and the sink maintenance
point.
Step 4 Check the faulty services, including software, hardware, and traffic. After the services restore,
the alarm automatically clears. You may also perform LB to confirm that the alarm clears.
----End
Related Information
None
3.9.2 EX_ETHOAM_CC_LOS (OTN)

Description
This alarm indicates a loss of the periodic continuity check message. When the sink maintenance
point receives the continuity check (CC) message from the source maintenance point, the timer
Issue 02 (2011-10-31)

247
OptiX OSN 8800/6800/3800

is started to periodically check the link between the source and sink maintenance points. If the
sink maintenance point does not receive the CC message from the source maintenance point in
one period (3.5 times of the time during which the CC message is transmitted from the source
maintenance point to the sink maintenance point), this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 2 bytes, indicates the number of the Ethernet port where this alarm is
generated.
Parameters 3 and 4 2 bytes, indicates the VLAN ID.
Parameter 5
Indicates the level of the maintenance domain.
Parameters 6 to 9
4 bytes, indicates the ID of the locate maintenance point.
Parameters 10 to 14 5 bytes, indicates the ID of the remote maintenance point.

When the EX_ETHOAM_CC_LOS alarm is generated, it indicates that a unidirectional
connectivity failure is detected on the link between the source and the sink maintenance points.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:
Issue 02 (2011-10-31)

248
OptiX OSN 8800/6800/3800

Cause 1: A software or hardware failure occurs in the services from the source maintenance
point to the sink maintenance point.
Cause 2: Service congestion or service interruption occurs between the source maintenance
point and the sink maintenance point.
Cause 1 and Cause 2: A software or hardware failure, service congestion or service

interruption occurs between the source maintenance point and the sink maintenance point.
Procedure
1.
View the EX_ETHOAM_CC_LOS alarm on the U2000 and confirm the ID of the
relevant maintenance point according to the alarm parameters.
2.
Query the information about the maintenance point.
3.
Perform loopback (LB) for the source and sink maintenance points, to locate the fault
in the services between the source maintenance point and the sink maintenance point.
4.
Perform checks for the problem services, including software check, hardware check,
and traffic check. After the services restore, the alarm is automatically cleared. You
may perform LB to confirm that the alarm is cleared.
5.
----End
Related Information
None.
3.10 FC_LINK_ERR
Description
The FC_LINK_ERR alarm indicates an FC service link failure. This alarm occurs when the FC
link is faulty.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
table.
Issue 02 (2011-10-31)

249
OptiX OSN 8800/6800/3800

Parameter Description
Parameter 1 Indicates the status of the transmission link on the WDM side. It is used to identify
the link status on a transmission network.
l 0x00: means WAN_UP, indicating that the transmission link is normal.
l 0x01: means WAN_DOWN, indicating that the transmission link is faulty.
Parameter 2 Indicates the FCBB network status.
When Parameter 1 is 0x01, it is a fixed value of 0xff;
When Parameter 1 is 0x00, it indicates the FCBB link status, include,
0x01: Indicates that the protocol parameter ISL mode is incorrect, and the flow
control management mode at the transmit end mismatches that at receive end.
0x02: Indicates that LEM state machine is not successfully closed. The LEM
state machine can distinguish between Client and WAN.
0x03: Indicates that the GFPT_Link Init state is not completed.
0x04: Indicates that the ping/ping_Ack result and the configured Buffer water
line do not match.

The services may be interrupted.
Fault Symptom
Table 3-10 lists the fault symptom for the FC_LINK_ERR alarm.
Table 3-10 Fault symptom for the FC_LINK_ERR alarm
Fault Symptom
Cause
The WDM side of the opposite board may

report an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm.
Cause 1: The WDM side of the opposite OTU

reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The
value of parameter 1 is 0x01.)
NOTE
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
250
OptiX OSN 8800/6800/3800

Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.)
Cause 3: The type or the time sequence of the services on the board is configured
improperly.
Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
Check the information of this alarm on the U2000. Record the parameters of this alarm.
Cause 1: The WDM side of the opposite OTU reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. (The value of parameter 1 is 0x01.)
Procedure
1.
On the U2000, check whether an R_LOS, R_LOF, OTUk_LOF, OTUk_LOM, or

OTUk_AIS alarm is generated on the WDM side of the connected board. If yes, handle
the alarm properly.
2.
Cause 2: The ISL mode of the client equipment is incorrect or a mismatch of the flow
control management mode occurs. (The value of parameter 2 is 0x01.).
1.
Check the alarm parameters to see whether the ISL mode is incorrect, or the flow
control management mode mismatches. If yes, check the configuration of the client
equipment in the network.
2.
Reconfigure the ISL mode and the traffic control management mode.
3.
Cause 3: The type or the time sequence of the services on the board is configured
improperly.
1.
Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If not, change the service type
of the corresponding port on the board or replace the board with another board that
matches the service type. For details, refer to "Replacing a Board" of the Supporting
Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
Issue 02 (2011-10-31)
2.
Check whether the rate that is configured for the services ports on the board where
the alarm is generated matches the rate of the actually received services. If they do
not match, you need to change the type of the accessed services or the type of the
services configured on the board according to the networking planning, thus to ensure
that the rates of these services are consistent.
3.
Cause 4: The type of the client-side optical module on the board mismatches the type of
the actual service, or the actual fiber mismatches the fiber type that the optical module
supports.
251
OptiX OSN 8800/6800/3800

1.
Check whether the service type that the client-side optical module on the board is the
same with the actual service type. If not, replace the board or replace the optical module
if it is pluggable to ensure the optical module type matches the actual service type.
If ...
Then ...
modules,
Replacement.

Tasks.
2.
If the alarm persists, check whether the fiber type supported by the client-side optical
module is the same with the type of the connected fiber. If not, replace the board or
the fiber.
3.
Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).

1.
If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
If ...
Then ...
modules,
Replacement.

Tasks.
2.
If the alarm persists, the OTU board at the opposite station may be faulty. In this case,
replace the faulty board.
3.
Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).

1.
If the alarm persists, the client equipment may be faulty. In this case, rectify the fault
on the client equipment.
2.
If the alarm persists, the client equipment at the opposite station may be faulty. In this
case, rectify the fault on the client equipment at the opposite station.
3.
----End
Related Information
None.
Issue 02 (2011-10-31)

252
OptiX OSN 8800/6800/3800

3.11 FC_SYNC_LOS
Description
This alarm indicates a loss of the FC service synchronous word. This alarm is generated when
the FC service state fails to obtain the signal alignment word.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Fault Symptom
Table 3-11 lists the fault symptom for the FC_SYNC_LOS alarm.
Table 3-11 Fault symptom for the FC_SYNC_LOS alarm
Fault Symptom
Cause
The board reports an OUT_PWR_HIGH or

OUT_PWR_LOW alarm.
Cause 2: The transmit optical power is

abnormal.
NOTE
Possible Causes
The possible causes of the FC_SYNC_LOS alarm are as follows:
l
Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
Cause 2: The transmit optical power is abnormal.
Issue 02 (2011-10-31)

253
OptiX OSN 8800/6800/3800

Procedure
l
Cause 1: The rate of the services receivable mismatches the rate of the services that are
actually received.
1.
Check whether the rate that is configured on the U2000 of the services at the ports on
the local board matches the rate of the accessed services. If they are not matched, you
need to change the type of the accessed services or the type of the services on the
board according to the networking planning, to ensure that the rates of these services
are the same. The service type for an optical interface on the board can be set or queried
on the U2000. For details, refer to "Querying and Setting the Service Type on the
Client Side of a Board" of the Supporting Tasks.
2.
Cause 2: The transmit optical power is abnormal.

1.
On the U2000, check whether the output optical power at the transmit end of the board
is within the normal range. For the optical power specification of the specific board,
refer to "Technical Specifications" of the Product Description. If the output optical
power is abnormal, see the handling procedures for the OUT_PWR_HIGH and
OUT_PWR_LOW alarms to rectify the fault.
2.
----End
Related Information
None.
3.12 IN_PWR_HIGH
Board Type
Alarm page link

3.12.1 IN_PWR_HIGH (OCS)

SLO16, or EGSH
3.12.2 IN_PWR_HIGH (OTN)
3.12.1 IN_PWR_HIGH (OCS)

Description
The IN_PWR_HIGH (OCS) is an alarm of too high input optical power. This alarm is generated
when a board detects that the actual input power is higher than the upper threshold of the input
power reference value.
Issue 02 (2011-10-31)

254
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

After the IN_PWR_HIGH alarm is generated, the services at the optical interface may contain
bit errors. Too high input power also causes damages to the laser.
Possible Causes
The possible causes of the IN_PWR_HIGH alarm are as follows:
l
Cause of the threshold setting: The reference value or threshold of optical power is
improper.
Cause of the external line: The attenuation value of the optical attenuator is improper.
Cause of the board: The board at the opposite station is faulty. As a result, the transmitting
power of the opposite station is too high.
Cause of the optical module: The type of the optical module is not correct.
Supporting Task.
Cause of the threshold setting: The reference value or threshold of optical power is not
correct.
Procedure
1.
Check the type of the optical module on the board. You can obtain the manufacturer
information about the optical module on the board through Querying Optical Module
Information in the Supporting Task.
2.
Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power of the Board in the Supporting Task. If the configured
threshold is improper, re-set the input upper threshold according to the overload
optical power of the board. For details on the optical power specifications of the board,
see "Technical Specifications" of the Product Description. Then, check whether the
alarm is cleared.
3.
If the alarm persists, see other causes.
Cause of the external line: The configured attenuation value of the optical attenuator is
improper.
1.
Issue 02 (2011-10-31)
On the U2000, check whether the receive optical power of the local end is within the
normal range. For details, see Querying Optical Power of the Board in the Supporting
Task. For details on optical power specification of the board, see "Technical
Specifications" of the Product Description. For details, see Querying Optical Power
of the Board in the Supporting Task.
255
OptiX OSN 8800/6800/3800

NOTE
2.
Check whether the attenuation value of the optical attenuator is correct if the receive
optical power is excessively high. If the attenuation value is not correct, change the
value according to the receive optical power specified for the board. For details, see
Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
Then, check whether the alarm is cleared.
3.
Cause of the board: The transmit power of the opposite station is excessively high because
the opposite board is faulty.
1.
Check whether the OUT_PWR_HIGH alarm exists at the opposite station.
2.
If the alarm exists, it indicates that the optical power transmitted by the opposite station
is not standard. Replace the optical module on the board or the board at the opposite
station. For details, see Replacing the Pluggable Optical Module in the Parts
3.
If the alarm persists, replace the opposite board. For details, see Parts Replacement.
4.
Cause of the optical module: The type of the optical module is not proper.
1.
Check whether the type of the optical module on the board is proper according to the
transmission distance. For details on the mapping relationship between the optical
module type and the transmission distance, see "Technical Specifications" of the
Product Description. For details on the operation, see Querying Optical Module
2.
If the type is not proper, replace the optical module or board with a proper optical
module or board. For details, see Replacing the Pluggable Optical Module in the Parts
Replacement. Otherwise, replace with the proper board. If the board supports
pluggable optical modules, replace the board with a proper board. For details, see
Parts Replacement.
3.
----End
Related Information
None.
3.12.2 IN_PWR_HIGH (OTN)

Description
This alarm indicates that the input optical power is excessively high. This alarm is generated
when the input optical power is higher than the upper threshold of the input optical power.
Reported from the WDM side or client side: WDM side, client side.
Issue 02 (2011-10-31)

256
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

When the input optical power is excessively high, bit errors and LOF alarms may be generated
in the received signals, and the optical module on the board can be damaged. As a result, the
services are affected.
Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1 for this alarm generated on the client side: The input optical power is excessively
high, and the attenuation configured is insufficient.
Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
Cause 1 for this alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
Cause 2 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
Cause 1 for this alarm generated on the client side: The input optical power is excessively
high, and the attenuation configured is insufficient.
Procedure
1.
Issue 02 (2011-10-31)
If the alarm is generated on the client side, query the input optical power of the board
that reports the alarm on the U2000 to check whether the input optical power is within
the normal range. For the optical power specification of the specific board, refer to
"Technical Specifications" of the Product Description. If the input power is abnormal
as shown on the U2000, use a power meter to measure the input optical power of the
board that reports the alarm to check whether the input optical power is within the
normal range. If the input optical power is abnormal, increase the attenuation to a
proper extent so that the input optical power is within the normal range.
257
OptiX OSN 8800/6800/3800

NOTE
on the board.
2.
l
procedure for cause 2 of this alarm generated on the client side.
Cause 2 for this alarm generated on the client side: The board that reports the alarm is faulty.
1.
If the input optical power of the board that reports the alarm is normal, the board may
be faulty. In this case, replace the board.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
Cause 1 for this alarm generated on the WDM side: The output optical power of the board
in the upstream station is excessively high.
1.
If the alarm is generated on the WDM side, query the input optical power of the board
that reports the alarm on the U2000 to check whether the input optical power is within
"Technical Specifications" of the Product Description.. If the input optical power is
abnormal, query the input and output optical power of the board in the upstream
direction of the OTU in a reverse sequence of the signal flow on the U2000. If the
input and output optical power of the upstream board exceeds the normal range, adjust
the input optical power of the board to a proper value.
2.
If the input optical power of the upstream boards is within the normal range, whereas
the output optical power is abnormal, the upstream board may be faulty. Replace the
board.
If ...
Then ...
modules,
Replacement.
3.
l
Issue 02 (2011-10-31)

Tasks.
Cause 2 for this alarm generated on the WDM side: The board that reports the alarm is
faulty.
258
OptiX OSN 8800/6800/3800

1.
If the input optical power of the board that reports the alarm is normal, the board may
be faulty. In this case, replace the board.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
If the alarm is generated in multiple wavelengths, the alarm handling method is similar to
the handling method for this alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
3.13 IN_PWR_LOW
Board Type
Alarm page link

3.13.1 IN_PWR_LOW (OCS)

SLO16, or EGSH
3.13.2 IN_PWR_LOW (OTN)
3.13.1 IN_PWR_LOW (OCS)

Description
The IN_PWR_LOW (OCS) alarm indicates excessively low input optical power. This alarm is
generated when a board detects that the actual input power is lower than the lower threshold of
the input power reference value.
Issue 02 (2011-10-31)

259
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

After the IN_PWR_LOW alarm is generated, the services at the optical interface may contain
bit errors.
Possible Causes
The possible causes of the IN_PWR_LOW alarm are as follows:
l
Cause of the threshold setting: The reference value or threshold of the optical power is not
correct.
Cause of the external line: The receive optical power is excessively low because the
performance of the fiber is degraded.
Cause of the board: The transmit power of the opposite station is excessively low because
Cause of the optical module: The type of the optical module is not correct.
Query current alarms on the U2000. Determine the number of the optical interface that
reports the alarm according to parameter 1. For details, see Querying the Current Alarms
in the Supporting Task.
Cause of the threshold setting: The reference value or threshold of optical power is not
correct.
Procedure
1.
Check the type of the optical module on the board. You can obtain the manufacturer
information about the optical module on the board through Querying Optical Module
2.
Check whether the threshold of the optical power is set properly. For the operations,
see Querying Optical Power of the Board in the Supporting Task. If the configured
threshold is not correct, re-set the input lower threshold according to the optical power
receiver sensitivity of the board. For details on the optical power specifications of the
board, see the "Technical Specifications" of the Product Description. Then, check
whether the alarm is cleared.
3.
Cause of the external line: The receive optical power is excessively low because the
performance of the fiber is degraded.
1.
Issue 02 (2011-10-31)
On the U2000, check whether the receive optical power of the local station is within
the normal range. For details, see Querying Optical Power of the Board in the
Supporting Task. For details on optical power specification of the board, see
"Technical Specifications" of the Product Description.
260
OptiX OSN 8800/6800/3800

NOTE
Refer to Querying Optical Module Information in the Supporting Task, you can obtain the
2.
Check whether the attenuation value of the optical attenuator is correct if the receive
optical power is excessively low. If the attenuation value is not correct, change the
value according to the receive optical power specified for the board. Then, check
3.
If the alarm persists, see Inspecting and Cleaning the Fiber-Optic Connectors in the
Supporting Task to check whether the connectors are dirty. Clean the optical
connectors if they are dirty. For the operations, see the Supporting Task.
Cleaning Optical Fiber Connectors Using Cartridge Cleaners
Cleaning Optical Fiber Connectors Using Lens Tissue
Cleaning Optical Adapters Using Optical Cleaning Sticks
4.
If the alarm persists, check whether the fiber is damaged or oppressed. If yes, replace
the fiber. Then, check whether the alarm is cleared.
5.
If the alarm persists, add a proper optical amplifier to increase the receive optical
power at the local station according to the receive optical power specified for the board.
6.
Cause of the board: The transmit power of the opposite station is excessively low because
1.
Check whether the OUT_PWR_LOW alarm exists at the opposite station.
2.
If the alarm exists, it indicates that the optical power transmitted by the opposite station
is not standard. Replace the optical module on the board or the board at the opposite
station. For details, see Replacing the Pluggable Optical Module in the Parts
3.
4.
Cause of the optical module: The type of the optical module is not proper.
1.
Check whether the type of the optical module on the board is proper according to the
transmission distance. For details on the mapping relationship between the optical
module type and the transmission distance, see "Technical Specifications" of the
Product Description. For details on the operation, see Querying Optical Module
2.
88. If the type is improper, replace the optical module or board with a proper optical
module or board. If the board supports pluggable optical modules, replace the
pluggable optical module. For details, see Replacing the Pluggable Optical Module
in the Parts Replacement. Otherwise, replace the board with a proper board. For
details, see Parts Replacement.
3.
----End
Related Information
None.
Issue 02 (2011-10-31)

261
OptiX OSN 8800/6800/3800

3.13.2 IN_PWR_LOW (OTN)

Description
This alarm indicates that the input optical power is excessively low. The alarm is generated when
the input optical power is smaller than the lower threshold of the input optical power.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

If the input optical power is excessively low, bit errors may be generated in the received signals,
which affect the normal receiving of the services.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the IN_PWR_LOW alarm are as follows:
l
Cause 1 for this alarm generated on the client side: The fiber connector is dirty, and the
fiber jumper is over-bent, damaged or aged.
Cause 2 for this alarm generated on the client side: The attenuation of the attenuator attached
to the optical port on the board that reports this alarm is excessively high.
faulty.
Cause 1 for this alarm generated on the WDM side: The fiber connector is dirty, and the
Cause 2 for this alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical port on the board that reports this alarm is excessively high.
Cause 3 for this alarm generated on the WDM side: The attenuation attached to the transmit
optical port on the board at the opposite station is excessively high, or the transmit optical
module is faulty.
Issue 02 (2011-10-31)

262
OptiX OSN 8800/6800/3800

Cause 4 for this alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.
faulty.
Cause 1 for this alarm generated on the client side: The fiber connector is dirty, and the
Procedure
1.
Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the normal range. For details,
refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting
Tasks. For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the
manufacturing information of the optical module on the board.
2.
If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, refer to "Inspecting
and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
3.
If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged
or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to
4.
Cause 2 for this alarm generated on the client side: The attenuation of the attenuator attached
to the optical port on the board that reports the alarm is excessively high.
1.
If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical port is excessively high. If the attenuation is excessively high, decrease
the attenuation value of the attenuator to a proper value or replace it with a suitable
attenuator. For details, refer to "Adjusting, Replacing, Adding and Removing
Attenuator" of the Supporting Tasks.
2.
1.
If the alarm persists, replace the board that reports the alarm.
If ...
Then ...
modules,
Replacement.
Issue 02 (2011-10-31)

Tasks.

263
OptiX OSN 8800/6800/3800

2.
l
Cause 1 for this alarm generated on the WDM side: The fiber connector is dirty, and the
1.
Use an optical power meter to measure the input optical power of the local board to
determine whether the input optical power is within the normal range. For details,
refer to "Testing Optical Power by Using an Optical Power Meter" of the Supporting
Tasks. For the optical power specification of the specific board, refer to "Technical
NOTE
See "Querying Optical Module Information" of the Supporting Tasks to obtain the
manufacturing information of the optical module on the board.
2.
If the detected power is excessively low, check the fiber connection. If the fiber
connector is dirty, clean or replace the fiber connector. For details, refer to "Inspecting
and Cleaning the Fiber-Optic Connectors" of the Supporting Tasks.
3.
If the alarm persists, check the fiber jumper. If the fiber jumper is over-bent, damaged
or aged, adjust the fiber jumper or replace the fiber jumper. For details, refer to
4.
Cause 2 for this alarm generated on the WDM side: The attenuation of the attenuator
attached to the optical port on the board that reports the alarm is excessively high.
1.
If the alarm persists, check whether the attenuation of the attenuator attached to the
receive optical port is excessively high. If the attenuation is excessively high, decrease
the attenuation value of the attenuator to a proper value or replace it with a suitable
attenuator. For details, refer to "Adjusting, Replacing, Adding and Removing
2.
Cause 3 for this alarm generated on the WDM side: The attenuation attached to the transmit
optical port on the board at the opposite station is excessively high, or the transmit optical
module is faulty.
1.
Check the board at the opposite station. If the laser on the board is closed, open it on
the U2000. For details, refer to "Opening/Closing Lasers" in the Supporting Tasks.
2.
Check whether the alarm is cleared. If the alarm persists, check whether the optical
attenuator with excessively high attenuation is attached to the transmit optical port on
the board at the opposite station. If yes, decrease the attenuation to a proper value or
replace the optical attenuator so that the output optical power of the opposite board is
normal. For details, refer to "Adjusting, Replacing, Adding and Removing Attenuator"
of the Supporting Tasks.
3.
Check whether the alarm is cleared. If the alarm persists, check the output optical
power performance values and alarms of the board. If the reported alarms or
performance values are different from the specification values, see the corresponding
handling procedure for the alarms or performance events to rectify the fault.
4.
Cause 4 for this alarm generated on the WDM side: The attenuation in the transmission of
the optical signals is excessively high and the compensation is insufficient.
1.
Issue 02 (2011-10-31)
Query the input and output optical power of the boards in the upstream direction of
the OTU at the local station in the reversed sequence of signal flow on the U2000.
264
OptiX OSN 8800/6800/3800

Locate the board with the very low optical power, and then adjust the input optical
power of the board to a proper value. For details, refer to "Adjusting, Replacing,
Adding and Removing Attenuator" of the Supporting Tasks.
2.
Check the input and output optical power of the upstream stations one by one in the
reversed sequence of signal flow on the U2000 and locate the faulty section where the
optical power is excessively low.
3.
If the output optical power of the upstream station is normal, check the cables, fiber
jumpers, fiber connectors, and attenuators; if the attenuation of the cables is higher
than the attenuation in the engineering design, adjust the attenuator, rectify or change
the cables; if the fiber jumper, fiber connector or the attenuator is dirty, clean or replace
the fiber jumper, fiber connector or attenuator. For details, see the Supporting Tasks.
4.
If the output optical power of the upstream station is abnormal, troubleshoot the faults
at the upstream station so that the output optical power is normal.
5.
faulty.
1.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
If the alarm is generated in multiple wavelengths, the alarm handling method is similar to
the handling method for the alarm generated on the WDM side.
----End
Related Information
The optical attenuator is marked with attenuation values expressed in dB.
Related Cases:
l
MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm
MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some
Wavelengths Report the IN_PWR_LOW Alarm
MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW
Alarm Reported by the OTU Board
MC-A217 An IN_PWR_LOW Alarm Is Reported After an Optical-Layer ASON Service

Is Configured on the ASON OptiX OSN 6800 NE
Issue 02 (2011-10-31)

265
OptiX OSN 8800/6800/3800

None.
3.14 INTRA_OTU_PS
Description
The INTRA_OTU_PS alarm indicates the intra-board 1+1 protection switching. This alarm
occurs when the intra-board 1+1 protection group actuates switching in which the current
channel switches to the protection channel from the working channel.
Reported from the WDM side or client side: WDM side
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the intra-board 1+1 protection group actuates switching, services are transiently
interrupted. When this alarm is reported, the working channel of the intra-board 1+1 protection
group might have faulty services that needs to be restored.
Fault Symptom
Table 3-14 lists the fault symptoms for the INTRA_OTU_PS alarm.
Table 3-14 Fault symptoms for the INTRA_OTU_PS alarm
Fault Symptom
Cause

switching.

switching.

Table 3-15.

of the intra-board 1+1 protection group are
alarm is reported.
NOTE
Issue 02 (2011-10-31)

266
OptiX OSN 8800/6800/3800

Possible Causes
l
switching. Such a command makes the current channel of the intra-board 1+1 protection
group switch to the protection channel from the working channel. Hence, the alarm is
reported.
Cause 2: The services of the working channel of the intra-board 1+1 protection group are
is reported.
switching.
Procedure
1.
2.
3.

Cause 2: The services of the working channel of the intra-board 1+1 protection group are
is reported.
1.
relevant to the services. If yes, handle the alarms by referring to the alarm handling
procedure. For details about the alarm information, see Table 3-15.
2.
alarm clears.
3.
----End
Related Information
Issue 02 (2011-10-31)
R_LOF
OTUk_AIS
IN_PWR_HIGH
R_LOS
ODUk_PM_AIS
IN_PWR_LOW
POWER_DIFF_OVER
ODUk_PM_OCI
ODUk_PM_DEG
R_LOC
ODUk_PM_LCK
ODUk_PM_EXC
OTUk_LOF
ODUk_LOFLOM
OTUk_DEG
OTUk_LOM
B1_EXC
OTUk_EXC

267
OptiX OSN 8800/6800/3800

For details, see "Intra-Board 1+1 Protection" in the Feature Description.
3.15 LASER_MODULE_MISMATCH
Description
This alarm indicates a mismatch of the optical module type and the fiber type. This alarm is
generated when the type of the optical module mismatches the type of the board.
Reported from the WDM side or client side: WDM side, client side
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The LASER_MODULE_MISMATCH alarm results in that services cannot be normally
received or transmitted. It can even cause service interruption.
Fault Symptom
None.
NOTE
Possible Causes
The possible cause of the LASER_MODULE_MISMATCH alarm is as follows:
l
Cause 1: The optical port type supported by the physical board does not match the type of
the optical module inserted into the optical port.
Cause 1: The optical port type supported by the physical board does not match the type of
the optical module inserted into the optical port.
Procedure
Issue 02 (2011-10-31)
1.
Check whether the optical module inserted into the optical port matches the type of
the optical port. For details, see "Quick Reference Table of the Units" in the Hardware
Description.
2.
If not, replace the optical module with another one of the right type. For details, see
"Replacing the Pluggable Optical Module" in the Parts Replacement.
268
OptiX OSN 8800/6800/3800

3.
Check whether this alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
None.
3.16 LINK_ERR
Board Type
Alarm page link

3.16.1 LINK_ERR (OCS)

SLO16, or EGSH
3.16.2 LINK_ERR (OTN)
3.16.1 LINK_ERR (OCS)

Description
The LINK_ERR (OCS) alarm indicates incorrect data link. This alarm is generated when the
Ethernet connection is incorrect and the port negotiation fails.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the LINK_ERR alarm is generated during the data transmission, the network port
negotiation fails. The data cannot be received and the services are interrupted.
Possible Causes
The possible causes of the LINK_ERR alarm are as follows:
Issue 02 (2011-10-31)

269
OptiX OSN 8800/6800/3800

The working modes of optical interfaces at the transmit and receive ends are inconsistent.
Hence, the negotiation fails.
The link is faulty.
The electrical cable, fiber connection, or opposite equipment is faulty.
Procedure
Step 1 View the LINK_ERR alarm on the U2000 to confirm the relevant board. Confirm the specific
port ID of the board.
Step 2 Check whether the working mode of the local port is consistent with that of the port at the
opposite station. If not, change it and then check whether the LINK_ERR alarm is cleared.
Step 3 If the alarm persists, check whether the electrical cable or fiber connection is faulty. If yes, fix
the electrical cable or fiber connection, and then check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the opposite equipment is faulty. If yes, replace the board
at the opposite station, and then check whether the alarm is cleared.
Step 5 If the alarm persists, replace the board that generates the alarm. After you make sure that the
working modes of the ports at the local and opposite stations are consistent, the LINK_ERR
alarm is automatically cleared.
----End
Related Information
None
3.16.2 LINK_ERR (OTN)

Description
This alarm indicates a link error. This alarm is generated when the link status of the Ethernet
data port is down.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the link status of the Ethernet ports is down, a valid link cannot be created between the
two data ports and the data services are interrupted.
Issue 02 (2011-10-31)

270
OptiX OSN 8800/6800/3800

Fault Symptom
Table 3-17 lists the fault symptom for the LINK_ERR alarm.
Table 3-17 Fault symptom for the LINK_ERR alarm
Fault Symptom
Cause
An IN_PWR_HIGH or IN_PWR_LOW
alarm may be generated on both of the two
interconnected boards.
Cause 3: The input optical power of the two

interconnected Ethernet ports is excessively
high or low.
NOTE
Possible Causes
l
Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports
are inconsistent. For example, one port is in the auto-negotiation mode but the other is nonnegotiation.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
Cause 4: The fiber or cable that connects the two Ethernet ports fails.
Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules can be connected to
are inconsistent.
Cause 6: The data equipment on the client side is faulty.
Cause 7: The board that reports this alarm is faulty.
Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
Procedure
1.
Check whether the service type of the OTU at the local station matches the type of
the services transmitted from the client data equipment. If not, change the service type
of the corresponding port on the board or replace the board with another board that
matches the service type. For details, refer to "Replacing a Board" of the Supporting
Tasks.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
2.
Issue 02 (2011-10-31)
271
OptiX OSN 8800/6800/3800

Cause 2: The settings of the auto-negotiation mode of the two connected Ethernet ports are
inconsistent.
1.
Check whether the auto-negotiation mode of the optical port on the board that reports
the alarm is consistent with that of the client data equipment. If they are inconsistent,
modify the setting to ensure the consistency.
2.
Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
1.
Check whether the input optical power of the two interconnected Ethernet ports is
within the normal range. For the optical power specification of the specific board,
NOTE
on the board.
2.
If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
3.
Cause 4: The fiber or cable that connects the two Ethernet ports fails.
1.
Check whether the fiber or cable that connects the two Ethernet ports are properly
connected. If they are not properly connected, reconnect or replace the fiber or cable.
2.
Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Hence, the types of fibers that the two optical modules can be connected to
are inconsistent.
1.
Check whether the types of fibers that the two optical modules can be connected to
are consistent. If they are inconsistent, replace the fiber or either board to make the
type of the two optical modules match the fiber type.
If ...
Then ...
modules,
Replacement.
l
Issue 02 (2011-10-31)

Tasks.
2.
If the alarm persists, check whether the optical module types of the two interconnected
boards match the type of the fiber that connects the two boards. If not, replace the
board whose optical module type does not match the fiber board.
3.
Cause 6: The data equipment on the client side is faulty.

272
OptiX OSN 8800/6800/3800

1.
Apply a hardware loopback between the transmit and receive optical ports on the client
side of the board. If the alarm persists, it indicates that the OTU at the local station is
faulty. For details, see the alarm handling procedure for cause 7.
2.
If the alarm is cleared, it indicates that the data equipment on the client side is faulty.
In this case, rectify the fault on the data equipment.
3.
Cause 7: The board that reports the alarm is faulty.

1.
2.
If ...
Then ...
modules,
Replacement.
3.

Tasks.
----End
Related Information
Related Cases:
l
MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. The
LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
MC-A102 The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS
Alarm
MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G Boards
and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
None.
3.17 LOOP_ALM
Issue 02 (2011-10-31)
Board Type
Alarm page link

3.17.1 LOOP_ALM (OCS)

273
OptiX OSN 8800/6800/3800

Board Type
Alarm page link

SLO16, or EGSH
3.17.2 LOOP_ALM (OTN)
3.17.1 LOOP_ALM (OCS)

Description
The LOOP_ALM (OCS) alarm indicates a loopback. Loopback is classified into optical interface
loopback and VC-4 channel loopback. This alarm is generated when service loopback is set.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the status of loopback.

The values are as follows:
l 0x00: Non-Loopback.
l 0x01: Inloop.
l 0x02: Outloop.

When the LOOP_ALM alarm is generated, it indicates that the system loopback is performed.
In this case, if services are running on the optical interface or channel, the services are interrupted.
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
The board loopback is manually configured.
Issue 02 (2011-10-31)

274
OptiX OSN 8800/6800/3800

Procedure
Step 1 After you manually cancel the loopback configuration, the LOOP_ALM alarm is automatically
cleared.
----End
Related Information
None.
3.17.2 LOOP_ALM (OTN)

Description
This alarm indicates that a loop is generated. The alarm is generated when the optical port of
the board is in the loopback status.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 Indicates the optical port where this alarm is generated. For example, 0x00
0x01 indicates optical port 1.
Parameter 3
Indicates the loopback type.

l 0x00: Inloop
l 0x01: Outloop

Services are interrupted.
Fault Symptom
None.
Issue 02 (2011-10-31)

275
OptiX OSN 8800/6800/3800

NOTE
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
l
Cause 1: The loopback command is issued during testing or maintenance.
Cause 1: The loopback command is issued during testing or maintenance.
Procedure
1.
Check whether the loopback is set on the optical port during testing or maintenance.
After the test or maintenance is complete, release the loopback configured for the
specific optical port. For details, refer to "Performing Inloop and Outloop" of the
Supporting Tasks.
2.
----End
Related Information
None.
3.18 LPT_ACTIVE
Description
This alarm indicates that the LPT switching is active. The data equipment itself has protection
scheme. Hence, the protection provided by the WDM equipment is not needed. However, the
WDM equipment is needed for informing the data equipment about the faults in the transmission
layer. In this way, the switching would be triggered for the data equipment. The alarm is
generated when switching is triggered.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.
Issue 02 (2011-10-31)

276
OptiX OSN 8800/6800/3800


When the alarm is generated, services will be interrupted if no protection route exists. If there
is alternative route, the services would automatically search the protection route for automatic
restoration. And a prompt would be generated to remind user to remove the fault.
Fault Symptom
Table 3-19 lists the fault symptoms for the LPT_ACTIVE alarm.
Table 3-19 Fault symptoms for the LPT_ACTIVE alarm
Fault Symptom
Cause
The R_LOS, LINK_ERR or L_SYNC alarm

may be generated on the client side of the
board.
Cause 1: The input signals on the client side

are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
An REM_SF alarm may be generated on the

client side of the board.
Cause 2: An REM_SF alarm is generated on

the client side of the local board because
equipment at the opposite station
malfunctions.
The OTUk_AIS, OTUk_LOF,

ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI, or ODUk_TCMn_LCK
may be generated on the WDM side of the
board.
Cause 3: When the WDM equipment

accesses data services and the OTN frames
are transmitted on the WDM side, this alarm
may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK,
ODUk_TCMn_AIS, ODUk_TCMn_OCI, or
ODUk_TCMn_LCK alarm on the WDM
side.
An R_LOF alarm may be generated on the

WDM side.
Cause 4: When the WDM equipment

accesses data services and the SDH frames
are transmitted on the WDM side, this alarm
may be triggered by the R_LOS or R_LOF
alarm on the WDM side.
An R_LOS alarm may be generated on the

WDM side.
Cause 3 or cause 4
NOTE
Possible Causes
l
Cause 1: The input signals on the client side are missing or the local board detects a
Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
Issue 02 (2011-10-31)

277
OptiX OSN 8800/6800/3800

Cause 3: When the WDM equipment accesses data services and the OTN frames are
transmitted on the WDM side, this alarm may be triggered by the R_LOS, OTUk_AIS,
OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS,
ODUk_TCMn_OCI, or ODUk_TCMn_LCK alarm on the WDM side.
Cause 4: When the WDM equipment accesses data services and the SDH frames are
transmitted on the WDM side, this alarm may be triggered by the R_LOS or R_LOF alarm
on the WDM side.
Cause 5: Regarding to separation of the tributary board from the line board, if the crossconnection configuration does not exist, the alarm is generated.
Check whether the service type accessed by the WDM equipment and the frame format
transmitted on the WDM side is consistent with that of the service configuration model by
using the U2000. If they are not consistent, configure them to ensure the consistency.
Cause 1: The input signals on the client side are missing or the local board detects a
Procedure
Issue 02 (2011-10-31)
1.
Check whether the R_LOS, LINK_ERR or L_SYNC alarms are generated on the
client side. If that is the case, clear the R_LOS, LINK_ERR or L_SYNCalarm.
2.
Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
1.
Check whether an REM_SF alarm is generated on the client side. If that is the case,
clear the REM_SF alarm.
2.
Cause 3: When the WDM equipment accesses the data services and the OTN frames are
transmitted on the WDM side, the alarm may be triggered by the R_LOS, OTUk_AIS,
ODUk_TCMn_OCI or ODUk_TCMn_LCK alarm on the WDM side.
1.
If the frames on the WDM side are transmitted in the OTN format, check whether
there are R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI or
ODUk_TCMn_LCK alarms. If yes, clear the alarms.
2.
Cause 4: When the WDM equipment accesses the data services and the SDH frames are
transmitted on the WDM side, the alarm may be triggered by the R_LOS or R_LOF alarm
on the WDM side.
1.
If the frames on the WDM side are transmitted in the SDH format, check the R_LOS
or R_LOF alarm information on the U2000 and clear the alarm.
2.
Cause 5: Regarding to separation of the tributary board from the line board, if the crossconnection configuration does not exist, the alarm is generated.
278
OptiX OSN 8800/6800/3800

1.
Check the trails of the cross-connect services according to the board that reports the
alarm. Regarding to separation of the tributary board from the line board, check
whether the cross-connection is configured on the U2000. If not, configure the crossconnection.
2.
----End
Related Information
As a link-based protection scheme, link pass through (LPT) provides the required network-level
protection for point-to-point private line services by means of point-to-point link pass
through.For details, see "LPT(OTN)" in the Feature Description.
3.19 LSR_WILL_DIE
Description
This alarm indicates that the laser will be out of work.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The laser is aging, and therefore the quality of the output optical signals and the received signals
is decreased (for example, the optical power is lower or is unstable). The impact depends on the
aging level of the laser.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the LSR_WILL_DIE alarm are as follows:
Cause 1: The laser is aging. The service life of the laser would be terminated.
Issue 02 (2011-10-31)

279
OptiX OSN 8800/6800/3800

Cause 2: The detection circuit of the board is faulty.
Procedure
l
Cause 1: The laser is aging. The service life of the laser would be terminated.
1.
If ...
Then ...
modules,
Replacement.
2.
l
Replace the board. For details, refer to

Tasks.

1.
Replace the faulty board. For details, refer to "Replacing a Board" of the Supporting
Tasks.
2.
----End
Related Information
None.
3.20 MS_AIS
Board Type
Alarm page link

3.20.1 MS_AIS (OCS)

SLO16, or EGSH
3.20.2 MS_AIS (OTN)
3.20.1 MS_AIS (OCS)

Issue 02 (2011-10-31)

280
OptiX OSN 8800/6800/3800

Description
The MS_AIS (OCS) is an indication alarm in the multiplex section. When the last three bits of
the K2 byte are 111 in five frames consecutively received on the receive side of the local optical
interface, the MS_AIS alarm is reported. This alarm shows that the signals in the multiplex
section corresponding to the optical interface that reports the alarm are useless.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

l
When the MS_AIS alarm is generated, the services are interrupted.
After the MS_AIS alarm is generated, the board automatically returns the MS_RDI alarm
to the opposite station. Consequently, the opposite station reports the MS_RDI alarm.
Possible Causes
The possible causes of the MS_AIS alarm are as follows:
l
Cause 1: The receive board at the local station is faulty.
Cause 2: The working and protection cross-connect boards at the opposite station are not
in position or are faulty.
Cause 3: The transmit board at the opposite station is faulty.
Query current alarms on the U2000. Determine the ID of the interface that reports the alarm
according to alarm parameter 1. For details, see Querying the Current Alarms in the
Supporting Task.
Procedure
1.
Perform a cold reset on the receive board at the local station. For the operations that
are performed on the U2000, see Performing a Cold Reset of a Board in the Supporting
Task. For the operations of reseating a board, see the Installation Guide. Then, check
CAUTION
If the services that pass the board are not configured with protection, the services are
interrupted after you perform a cold reset on the board.
Issue 02 (2011-10-31)

281
OptiX OSN 8800/6800/3800

2.
If the alarm persists, replace the board that reports the alarm. For details, see Parts
3.
If the alarm persists, see cause 2.
Cause 2: The working and protection cross-connect boards at the opposite station are not
in position or are faulty.
1.
Check the board alarm indicator to see whether the status of the cross-connect board
status is cold reset or warm reset. Wait for 5 minutes, and then check whether the
alarm is cleared. For the description of the alarm indicators on the board, see Board
Indicators in the Hardware Description.
2.
If the alarm persists, check whether the working and protection cross-connect boards
at the opposite station are loose. If yes, tighten the working and protection crossconnect boards. For details, see the Installation Guide. Then, check whether the alarm
is cleared.
3.
If the alarm persists, replace the cross-connect board. For details, see Parts
4.
Cause 3: The transmit board at the opposite station is faulty.

1.
----End
Related Information
None.
3.20.2 MS_AIS (OTN)

Description
This alarm is a multiplex section alarm indication. The alarm is generated when the input signals
from the client side contain the MS_AIS signal or the receive side of the local station is faulty.
Reported from the WDM or client side: client side.
l
client side: In this case, the type of the service received on the client side is SDH.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The services are faulty.
Issue 02 (2011-10-31)

282
OptiX OSN 8800/6800/3800

Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1 : The input signals from the client side contain the MS_AIS signal, as shown in
the following figure.
Detects and
reports the
MS_AIS alarm
The client signals

contain the
MS_AIS signal
OTU1
Client
side
WDM
side
O
A
D
M
F
I
U
F
I
U
Station A
O
A
D
M
OTU2
WDM
side
Client
side
Station B
Cause 2 : The board that reports the alarm is faulty.
Cause 1 : The input signals from the client side contain the MS_AIS signal
Procedure
1.
side of OTU1. If the alarm on OTU1 persists, it indicates that OTU1 is faulty. In this
case, see the alarm handling procedure for cause 2.
2.
If the alarm is cleared, it indicates that the input signals on the client side contain bit
errors. In this case, rectify the fault on the client equipment.

1.
If the alarm persists, the board that reports the alarm is faulty. Replace the board.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Issue 02 (2011-10-31)

283
OptiX OSN 8800/6800/3800

Related Information
None.
3.21 MS_RDI
Board Type
Alarm page link

3.21.1 MS_RDI (OCS)

SLO16, or EGSH
3.21.2 MS_RDI (OTN)
3.21.1 MS_RDI (OCS)

Description
The MS_RDI (OCS) is a remote defect indication in the multiplex section. When the last three
bits of the K2 byte are 110 in five frames consecutively received on the receive side of the local
optical station, the MS_RDI alarm is reported. When receiving the R_LOS and MS_AIS alarms,
the opposite station returns the alarm to the local station.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the MS_RDI alarm is generated, the local station is not affected. This alarm just shows
that the services at the opposite station are interrupted.
Possible Causes
The possible causes of the MS_RDI alarm are as follows:
l
Issue 02 (2011-10-31)
Cause 1: The opposite station receives the R_LOS and MS_AIS alarms.
284
OptiX OSN 8800/6800/3800

Cause 2: The transmit board at the local station is faulty.
Cause 3: The receive board at the opposite station is faulty.
Supporting Task.
Cause 1: The opposite station receives the R_LOS and MS_AIS alarms.
Procedure
1.
On the U2000, check whether the service interruptions or bit error alarms, such as
R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD exist at the opposite station. If
yes, clear these alarms first.
2.
Then, check whether the MS_RDI alarm is cleared. If the alarm persists, see cause 2.
Cause 2: The transmit board at the local station is faulty.

1.
Perform a cold reset on the transmit board at the local station. For the operations on
the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For the
operations of reseating a board, see the Installation Guide. Then, check whether the
alarm is cleared.
CAUTION
2.
If the alarm persists, replace the transmit board at the local station. For details, see
Parts Replacement. Then, check whether the alarm is cleared.
3.
Cause 3: The receive board at the opposite station is faulty.

1.
Perform a cold reset on the receive board at the opposite station. For the operations
on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For
the operations of reseating a board, see the Installation Guide. Then, check whether
the alarm is cleared.
CAUTION
2.
If the alarm persists, replace the receive board at the opposite station. For details, see
Parts Replacement.
----End
Related Information
None.
Issue 02 (2011-10-31)

285
OptiX OSN 8800/6800/3800

3.21.2 MS_RDI (OTN)

Description
This alarm is a multiplex section remote defect indication. The alarm is generated at the local
station if the opposite station back transmits the information through overhead when the WDMside receive part of the opposite station is faulty (for example, the R_LOS, R_LOF or MS_AIS
alarm is generated).
Reported from the WDM or client side: WDM side, client side
l
WDM side: In this case, the type of the service received on the WDM side is SDH.
Client side: In this case, the type of the service accessed on the client side is SDH.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

l
If the alarm is reported from the WDM side, the services may be interrupted.
If the alarm is reported from the client side, the client-side services are faulty.
Fault Symptom
Table 3-22 lists the fault symptom for the MS_RDI alarm.
Table 3-22 Fault symptom for the MS_RDI alarm
Fault Symptom
Cause
The board at the opposite station reports an

R_LOS, R_LOF, or MS_AIS alarm.
Cause 1 for this alarm generated on the WDM

side: The receiver on the WDM side at the
opposite station detects a signal failure.
NOTE
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1 for this alarm generated on the client side: For the OTU board whose client side
supports the SDH services, the input signals from the client side contain the MS_RDI signal.
As shown in the following figure, the input signals from the client side of the OTU board
286
OptiX OSN 8800/6800/3800

at the local station A contain the MS_RDI signals. The OTU of the station A reports the
MS_RDI alarm on the client side after it detects the MS_RDI signals.
Detects and reports the
MS_RDI alarm
The client signals contain

the MS_RDI signal
Client
side
O
T
U
WDM
side
WDM
side
Station A
O
T
U
Client
side
Station B
Cause 1 for this alarm generated on the WDM side: The receiver on the WDM side at the
opposite station detects a signal failure. (For example, an R_LOS, R_LOF, or the MS_AIS
alarm is generated.) As shown in the following figure, the WDM side of the OTU board in
station B (the opposite station) sends the MS_RDI signals back to station A (the local
station) after it detects and reports the R_LOS, R_LOF or the MS_AIS alarm. The WDM
side of the OTU board in station A reports the MS_RDI alarm after it detects the MS_RDI
signals.
Detects and reports the R_LOS,
R_LOF, MS_AIS alarm
Client
side
O
T
U
WDM
side
Station A
MS_RDI alarm
WDM
side
O
T
U
Client
side
Station B
Sends the MS_RDI
signal back
faulty.
Cause 1 for this alarm generated on the client side: In the case of the OTU board of which
the client side supports the SDH service, the input signals from the client side contain the
MS_RDI signal.
Procedure
1.
Issue 02 (2011-10-31)
When the MS_RDI alarm is reported from the client side, rectify the fault on the client
equipment connected to the OTU board. For details, see the related manual of the
client equipment.

287
OptiX OSN 8800/6800/3800

Cause 1 for the alarm generate on the WDM side: The receiver on the WDM side at the
opposite station detects a signal failure (for example, an R_LOS, R_LOF or the MS_AIS
alarm is generated).
1.
Query the alarm of the board at the opposition station by using the U2000. If and
R_LOS, R_LOF or MS_AIS alarm exists, see the handling procedure of the R_LOS,
R_LOF, or MS_AIS alarm for troubleshooting.
2.
faulty.
1.
If the alarm persists, the board at the local station is faulty. Consider whether to replace
the faulty board according to the actual situation (for example, whether replacing the
board affects the services).
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
None.
3.22 MUT_LOS
Description
This alarm indicates a loss of multiplexed signals. This alarm is generated when the input
multiplexed signals of the board are lost.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

288
OptiX OSN 8800/6800/3800


The services through the optical port where this alarm is generated are interrupted.
Fault Symptom
Table 3-23 lists the fault symptom for the MUT_LOS alarm.
Table 3-23 Fault symptom for the MUT_LOS alarm
Fault Symptom
Cause
The optical ports on the board that reports this

alarm are disconnected.
Cause 1: Certain optical ports on the board

that reports this alarm are disconnected or the
fibers connected to the optical ports are
damaged.
NOTE
Possible Causes
l
Cause 1: Fibers connected to certain optical ports at the receive end of the board that reports
the alarm are not connected, incorrectly connected, or damaged.
Cause 2: The attenuation of signals during line transmission is excessively high.
On the U2000, check whether the boards on the multiplexing link in the upstream direction
report this alarm along the reverse direction of the signal flow.
Cause 1: Fibers connected to certain optical ports at the receive end of the board that reports
the alarm are not connected, incorrectly connected, or damaged.
Procedure
1.
Check whether there are fibers connected to certain optical ports at the receive end of
the board that reports the alarm are not connected or incorrectly connected. If yes,
connect the input optical fibers to the specific optical port.
2.
Check whether the fibers or fiber connectors on the board that reports this alarm are
dirty. If yes, see Checking Fiber Jumpers by Using an Optical Power Meter or
Replacing Fiber Jumpers to rectify the fault.
3.
Cause 2: The attenuation of signals during line transmission is excessively high.

1.
Issue 02 (2011-10-31)
Use an optical power meter to measure the actual receive optical power of the board
that reports the alarm. Check whether the receive optical power is within the normal
range. For the optical power specification of the specific board, refer to "Technical
289
OptiX OSN 8800/6800/3800

NOTE
on the board.
2.
If the receive optical power is excessively low, check whether an optical attenuator
with excessively high attenuation is attached to the receive optical port on the board.
If yes, decrease the attenuation of the optical attenuator to a proper value or replace
the optical attenuator with a proper one.
3.
If the alarm persists, check whether the attenuation of the built-in VOA in the upstream
board is excessively high. If yes, adjust the attenuation of the VOA to a proper value.
4.
Check whether the alarm is cleared. If the alarm persists, the optical cables between
stations may be faulty. In this case, rectify the fault on the optical cables.
5.

1.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
Related Cases:
l
MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
MC-A151 OWSP Protection Switching Fails Due to Incorrect Connection of Fiber Jumpers
On The DCP Boards, DCP Boards Report The MUT_LOS Alarms And TDG Board Reports
The OPU1_PLM Alarm
MC-A182 Receive Optical Power Is Excessively Low Because of The End Face Problem
of the Fiber Jumper, The OAU Board Reports The MUT_LOS And R_LOS Alarms
MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
None.
Issue 02 (2011-10-31)

290
OptiX OSN 8800/6800/3800

3.23 OA_LOW_GAIN
Description
This alarm indicates that the gain of an optical amplifier is low. The alarm is generated when
the actual gain of the optical amplifier board is 3 dB lower than the standard gain.
Attribute
Alarm Severity
Alarm Type
Critical
Service alarm
Parameters
None

The alarm caused by different factors has different impacts on the system:
l
If the alarm is generated because the input optical power is excessively high, the redundancy
of the system decreases, which affects the subsequent capacity expansion.
If the alarm is caused by other factors (for example, excessive insertion loss between the
TDC and RDC optical ports on an OAU board), the input optical power of the downstream
signals and the redundancy of the system decrease. The services may have bit errors or
even be interrupted.
Fault Symptom
Table 3-24 lists the fault symptom for the OA_LOW_GAIN alarm.
Table 3-24 Fault symptom for the OA_LOW_GAIN alarm
Fault Symptom
Cause
The OAU board that reports this alarm also

reports a power high alarm, such as
SUM_INPWR_HI.
Cause 1: The input optical power of the OAU

board is excessively high.
NOTE
Issue 02 (2011-10-31)

291
OptiX OSN 8800/6800/3800

Possible Causes
The possible causes of the OA_LOW_GAIN alarm are as follows:
l
Cause 1: The input optical power of the board is excessively high.
Cause 2: This alarm may be generated because the insertion loss between the TDC and
RDC optical ports is excessively high. (This cause is applicable only to the OAU board.)
Cause 1: The input optical power of the board is excessively high.
Procedure
1.
On the U2000, check whether the receive optical power of the board is within the
normal range. For the optical power specification of the specific board, refer to
2.
If the input optical power is not within the normal range, adjust the optical attenuator
attached to the input optical port so that the input optical power meets the specification
requirement. For details, refer to "Adjusting, Replacing, Adding and Removing
3.
If no optical attenuator is attached to the input optical port, add an optical attenuator
to ensure that the input optical power meet the specification requirement. For details,
refer to "Adjusting, Replacing, Adding and Removing Attenuator" of the Supporting
Tasks.
4.
Cause 2: The insertion loss between the TDC and RDC optical ports is excessively high.
(This cause is applicable only to the OAU board.)
1.
On the U2000, check the optical power at the TDC and RDC optical ports on the OAU,
and then calculate the insertion loss between the TDC and RDC optical ports. For
details, refer to "Querying the Insertion Loss Between the TDC and RDC optical ports
on the OAU board" in the Supporting Tasks.
NOTE
Insertion loss = Optical power at the TDC optical port - Optical power at the RDC optical port.
On the U2000, the difference between the optical power at optical port 3 and the optical power
at optical port 5 represents the insertion loss.
2.
If the insertion loss is excessive, clean the fiber jumper and fiber connector between
the TDC and RDC optical ports. For details, refer to "Inspecting and Cleaning the
Fiber-Optic Connectors" in the Supporting Tasks. For the insertion loss specification,
see the Product Description. For the optical power specification of the specific board,
3.
Check whether the alarm is cleared. If the alarm persists, replace the DCM module
between the TDC and RDC optical ports. For details, see "Replacing the DCM" in the
Supporting Tasks.
4.

1.
Issue 02 (2011-10-31)
Replace the faulty board.

292
OptiX OSN 8800/6800/3800

If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
None.
3.24 ODU_SNCP_PS
Description
The ODU_SNCP_PS alarm indicates the ODU SNCP protection switching. This alarm occurs
when the ODU SNCP protection group actuates switching in which the current channel switches
to the protection channel from the working channel.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the ODU SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the ODU SNCP protection group might
have faulty services that needs to be restored.
Fault Symptom
Table 3-25 lists the fault symptoms for the ODU_SNCP_PS alarm.
Issue 02 (2011-10-31)

293
OptiX OSN 8800/6800/3800

Table 3-25 Fault symptoms for the ODU_SNCP_PS alarm

Fault Symptom
Cause

switching.

switching.

Table 3-26.

of the ODU SNCP protection group are
alarm is reported.
NOTE
Possible Causes
l
switching. Such a command makes the current channel of the ODU SNCP protection group
switch to the protection channel from the working channel. Hence, the alarm is reported.
Cause 2: The services of the working channel of the ODU SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
switching.
Procedure
Issue 02 (2011-10-31)
1.
2.
3.

Cause 2: The services of the working channel of the ODU SNCP protection group are faulty.
reported.
1.
relevant to the services. If that is the case, handle the alarms by referring to the
corresponding handling procedure of the alarms. For details about the alarm
information, see Table 3-26.
2.
alarm clears.
294
OptiX OSN 8800/6800/3800

3.
----End
Related Information
R_LOF
OTUk_AIS
ODUk_PM_TIM
R_LOS
OTUk_TIM
ODUk_TCMn_AIS
R_LOC
OTUk_EXC
ODUk_TCMn_LCK
HARD_BAD
ODUk_PM_AIS
ODUk_TCMn_OCI
OTUk_LOF
ODUk_PM_LCK
ODUk_TCMn_LTC
OTUk_LOM
ODUk_PM_OCI
ODUk_TCMn_EXC
ODUk_TCMn_TIM
ODUk_PM_DEG
ODUk_TCMn_DEG
OTUk_DEG
ODUk_PM_EXC
For details, see "ODUk SNCP Protection" in the Feature Description.
3.25 ODUk_PM_AIS
Description
This alarm is an ODUk PM alarm indication signal. An AIS signal from the downstream station
indicates that a signal failure is detected at the upstream station.
k indicates the level of rate.
l
For OptiX OSN 8800, its value is FLEX, 0, 1, 2, 3.
For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G.
For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

295
OptiX OSN 8800/6800/3800


The services through the optical port are interrupted.
Fault Symptom
Table 3-27 lists the fault symptoms for the ODUk_PM_AIS alarm.
Table 3-27 Fault symptoms for the ODUk_PM_AIS alarm
Fault Symptom
Cause
The client side of the corresponding OTU

board at the opposite station reports an
ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm.

side: The client side of the corresponding
OTU board at the opposite station reports an
ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm and then
inserts an AIS signal to the local station.
The WDM side of the OTU board at the local

station reports an R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm.

side: The WDM side of the OTU board at the
local station reports an R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm, and
therefore the board at the local station also
reports an ODUk_PM_AIS alarm.
NOTE
Possible Causes
The possible causes of the ODUk_PM_AIS alarm are as follows:
l
Cause 1 for this alarm generated on the client side: Signals input from the client side contain
ODUk_PM_AIS signal.
See the following figure.
The input signals on the client side of the OTU at station A contain ODUk_PM_AIS signals.
The OTU at station A reports an ODUk_PM_AIS alarm on the client side after detecting
the ODUk_PM_AIS signals.
Issue 02 (2011-10-31)

296
OptiX OSN 8800/6800/3800

Detects and reports

the ODUk_PM_AIS alarm
The client
signals contain
the ODUk_PM_AIS
signal
Client
side
O
T
U
WDM
side
Station A
WDM
side
O
T
U
Client
side
Station B
Cause 1 for this alarm generated on the WDM side: The client side of the corresponding
board at the opposite station reports an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm, and then inserts an AIS signal to the local station.
The client side of the OTU at station A automatically inserts an ODUk_PM_AIS signal
into the WDM-side signals after detecting an ODUk_PM_AIS, R_LOS, OTUk_LOF,
OTUk_LOM, or OTUk_TIM alarm. The WDM side of the OTU at station B reports an
ODUk_PM_AIS alarm after detecting an ODUk_PM_AIS signal.
ODUk_PM_AIS, R_LOS,
OTUk_LOF, OTUk_LOM,
OTUk_TIM alarm
Client
side
O
T
U
Insert the
ODUk_PM_AIS
signal
WDM
side
Station A
Detects and reports

the ODUk_PM_AIS alarm
WDM
side
O
T
U
Client
side
Station B
Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at
the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and
therefore the OTU board at the local station also reports an ODUk_PM_AIS alarm.
ODUk_PM_AIS signal.
Procedure
Issue 02 (2011-10-31)

297
OptiX OSN 8800/6800/3800

1.
between the transmit and receive optical ports on the client side of OTU1. If the alarm
on OTU1 persists, it indicates that the OTU1 hardware is faulty. In this case, see the
CAUTION
2.
l
If the alarm is cleared, it indicates that the input signals on the client side of the board
contain bit errors. In this case, rectify the fault on the client equipment.
1.
If ...
Then ...
modules,
Replacement.
l

Tasks.
The client side of the corresponding OTU board at the opposite station reports an
ODUk_PM_AIS, R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm and then
inserts an AIS signal to the local station
1.
On the U2000, check whether an ODUk_PM_AIS, R_LOS, OTUk_LOF,

OTUk_LOM or OTUk_TIM alarm exists on the client side of the OTU board at the
opposite end. If the alarm exists, check the equipment at the opposite station.
2.
Cause 2 for this alarm generated on the WDM side: The WDM side of the OTU board at
the local station reports an R_LOS, OTUk_LOF, OTUk_LOM, or OTUk_TIM alarm, and
therefore the OTU board at the local station also reports an ODUk_PM_AIS alarm.
1.
On the U2000, check whether an R_LOS, OTUk_LOF, OTUk_LOM, or

OTUk_TIM alarm exists on the WDM side of the OTU at the local station. If yes,
rectify the fault at the local station to clear the alarm.
2.
----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)

298
OptiX OSN 8800/6800/3800

3.26 ODUk_PM_BDI
Description
This alarm is an ODUk PM backward defect indication. This alarm is generated when the PM
section at the opposite station detects a signal failure and inserts a BDI alarm to the local station.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

The services through the optical port are interrutped.
Fault Symptom
Table 3-28 lists the fault symptom for the ODUk_PM_BDI alarm.
Table 3-28 Fault symptom for the ODUk_PM_BDI alarm
Issue 02 (2011-10-31)
Fault Symptom
Cause

R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI,
ODUk_PM_TIM, or ODUk_PM_SSF alarm.

side: The WDM side of the corresponding
board at the opposite station reports an
R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_TIM, or ODUk_PM_SSF alarm
and inserts an ODUk_PM_BDI back to the
local station (station A).

299
OptiX OSN 8800/6800/3800

NOTE
Possible Causes
l
an ODUk_PM_BDI signal.
faulty.
Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding
board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and
inserts an ODUk_PM_BDI back to the local station (station A).
Detects and reports R_LOS,
OTUk_LOF, OTUk_LOM,
ODUk_PM_TIM, ODUk_PM_SSF
alarms
Client
side
O
T
U
WDM
side
Station A
ODUk_PM_BDI alarm
WDM
side
O
T
U
Client
side
Station B
Sends the
ODUk_PM_BDI signal
back
Procedure
l
On the U2000, check whether there is an alarm with higher severity on the board. If yes,
handle the alarm properly.
an ODUk_PM_BDI signal.
1.
between the transmit and receive optical ports on the client side of OTU board. If this
alarm persists, it indicates that the board is faulty. In this case, see the alarm handling
CAUTION
A loopback on the board interrupts the existing services.
2.
l
Issue 02 (2011-10-31)
If this alarm is cleared, it indicates that the input signals on the client side of the board
contain bit errors. In this case, rectify the fault on the client equipment.
faulty.
300
OptiX OSN 8800/6800/3800

1.
If ...
Then ...
modules,
Replacement.

Tasks.
Cause 1 for this alarm generated on the WDM side: The WDM side of the corresponding
board at the opposite station reports an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm, and
inserts an ODUk_PM_BDI back to the local station.
1.
If this alarm is reported from the WDM side, check whether the corresponding OTU
board at the opposite station receives an R_LOS, OTUk_LOF, OTUk_LOM,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, or ODUk_PM_SSF alarm
by using the U2000. If yes, handle the corresponding alarm at the opposite station.
2.
----End
Related Information
ITU-T G.709
3.27 ODUk_PM_DEG
Description
This alarm indicates that the ODUk PM signal is degraded. When the BIP8 detection is in burst
mode, this alarm is generated if the signal degradation or bit error count exceeds the threshold.
In addition, when the BIP8 detection in poisson mode, this alarm is generated if the signal
degradation exceeds the threshold.
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-10-31)

301
OptiX OSN 8800/6800/3800

Parameters
None

If this alarm is generated, bit errors are generated in the services through the optical port, which
makes the service signals unavailable.
Fault Symptom
Table 3-29 lists the fault symptom for the ODUk_PM_DEG alarm.
Table 3-29 Fault symptom for the ODUk_PM_DEG alarm
Fault Symptom
Cause
The OTU board at the local station may report

an IN_PWR_LOW or a BEFFEC_EXC
alarm.
Cause 1: The attenuation of received signals

is excessively large. As a result, the input
optical power of the board is abnormal.
NOTE
Possible Causes
The possible causes of the ODUk_PM_DEG alarm are as follows:
l
Cause 1: The input optical power of the OTU board is abnormal.
Cause 2: The fiber on the transmission line is abnormal.
Cause 3: The board that reports the alarm is faulty or the corresponding board at the opposite
station is faulty.
Cause 1: The input optical power of the OTU board is abnormal.
Procedure
Issue 02 (2011-10-31)
1.
On the U2000, view the alarms of the entire network to confirm the slot ID, interface
ID, and channel ID of the board that generates this alarm.
2.
Along the service signal flow, check whether the input optical power of the point that
first generates this alarm is within the normal range. For the optical power specification
of the specific board, refer to "Technical Specifications" of the Product Description.
3.
If the optical power is not within the normal range, adjust the input optical power of
the board to a proper value. For details, refer to "Adjusting, Replacing, Adding and
Removing Attenuator" of the Supporting Tasks.
4.
Check whether the alarm is cleared. If the alarm persists, troubleshoot this alarm
station by station along the service signal flow.
5.
302
OptiX OSN 8800/6800/3800

Cause 2: The fiber on the transmission line is abnormal.

1.
Check the related fiber connectors. If the fiber connectors are dirty, clean or replace
them. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of
2.
3.
Cause 3: The board that reports the alarm is faulty or the corresponding board at the opposite
station is faulty.
1.
If the alarm persists, replace the board that reports the alarm.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
ITU-T G.709
3.28 ODUk_PM_EXC
Description
This alarm indicates that the BIP8 error count on the ODUk PM section exceeds the threshold.
This alarm is generated when the BIP8 detection is in poisson mode and bit error count exceeds
the threshold.
l
Issue 02 (2011-10-31)

303
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The alarm has impacts on the QoS of the service signals.
Fault Symptom
Table 3-30 lists the fault symptoms for the ODUk_PM_EXC alarm.
Table 3-30 Fault symptoms for the ODUk_PM_EXC alarm
Fault Symptom
Cause
The OTU board at the local station may report

an IN_PWR_LOW alarm.
Cause 1: The attenuation of the received

signals is rather large, and the fiber
transmission line is abnormal.
NOTE
Possible Causes
l
Cause 1: The attenuation of the received signals is rather large, and the fiber transmission
line is abnormal.
Cause 2: The transmitter of OTU board at the opposite station is faulty.
Cause 3: The receiver of the OTU board at local station is faulty.
Cause 1: The attenuation of the received signals is rather large, and the fiber transmission
line is abnormal.
Procedure
1.
On the U2000, check whether the receive optical power is within the normal range.
For the optical power specification of the specific board, refer to "Technical
Specifications" of the Product Description.For details, refer to "Querying Optical
Power on the U2000" of the Supporting Tasks.
NOTE
on the OTU board.
Issue 02 (2011-10-31)

304
OptiX OSN 8800/6800/3800

2.
If the receive optical power of the OTU board at the local station is excessively low,
clear the alarm according to the handling procedure of the IN_PWR_LOW alarm.
3.
If the alarm persists, check whether the launched optical power at the corresponding
optical port on the upstream board is within the normal range on the U2000. For the
optical power specification of the specific board, refer to "Technical Specifications"
of the Product Description. If the launched optical power of the OTU board at the
upstream station is excessively low, clear the alarm according to the handling
procedure of the OUT_PWR_LOW alarm.
4.
Cause 2: The transmitter of the OTU board at the opposite station is faulty.
1.
Apply a hardware loopback between the transmit and receive optical ports on the
WDM side of the OTU board at the upstream station. If the alarm persists, it indicates
that the transmitter on the OTU board of the opposite station is faulty. In this case,
replace the OTU board.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
If the alarm persists, see the alarm handling procedure for cause 3.
Cause 3: The receiver of the OTU board at local station is faulty.

1.
If the alarm persists, replace the faulty board at the local station.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)

305
OptiX OSN 8800/6800/3800

3.29 ODUk_PM_SSF
Description
The ODUk_PM_SSF is an alarm indicating signal failure at the ODUk PM layer.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Fault Symptom
Table 3-31 lists the fault symptom for the ODUk_PM_SSF alarm.
Table 3-31 Fault symptom for the ODUk_PM_SSF alarm
Fault Symptom
Cause
A station may report the R_LOS, OTUk_SSF

alarm at the same time.
Cause 1: The line in the regeneration span is

abnormal when there are electrical
regeneration boards.
Cause 4: In the case of a station configured
with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm
when the line is abnormal.
Issue 02 (2011-10-31)
A station may report the ODUk_TCMn_SSF,

ODUk_TCMn_LCK, ODUk_TCMn_OCI,
ODUk_TCMn_AIS, ODUk_TCMn_LTC, or
ODUk_TCMn_TIM alarm at the same time.
Cause 2: The station reports an alarm of the

ODUk_TCMn type and the ODUk_PM_SSF
A station may report the OTUk_TIM alarm at

the same time.
Cause 3: The station reports the OTUk_TIM

alarm and the ODUk_PM_SSF alarm at the
same time.

306
OptiX OSN 8800/6800/3800

NOTE
Possible Causes
l
Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration
boards. As shown in the following figure, when the line in the span from the OTU1 board
at station A to the OTU2 board at station B or in the span from the OTU3 board at station
B to the OTU4 board at station C is abnormal, the OTU4 board at station C reports the
ODUk_PM_SSF alarm.
O
T
U
1
Client WDM
side
side
M
U
X/
D
M
U
X
Station A
OA
OA
F
I
U
F
I
U
OA
OA
M
U
X/
D
M
U
X
O
T
U
2
O
T
U
3
M
U
X/
D
M
U
X
Station B
OA
OA
F
I
U
F
I
U
OA
OA
M
U
O
X/
T
D
U
M
4
U
X WDM Client
side
side
Station C
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
Cause 2: When Sink Enable Status is Enabled and Source Mode is Operation Mode for
the TCM overheads of the station, the station reports the ODUk_TCMn_SSF,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_AIS, ODUk_TCMn_LTC, or
ODUk_TCMn_TIM alarm and the ODUk_PM_SSF alarm at the same time. The
ODUk_TCMn_LTC alarm is reported only when Enable LTC Response is set to
Enabled. The ODUk_TCMn_TIM alarm is reported only when Enable TIM Response is
set to Enabled.
Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the
same time. The OTUk_TIM alarm is reported only when Enable TIM Response is set to
Enabled.
Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration
boards.
Procedure
Issue 02 (2011-10-31)
1.
According to the service flow, find the first station where the SSF alarm is reported
and then the OTU board that reports the alarm at the station, for example, the OTU4
board at station C in the figure.
2.
If the OTU4 board is a tributary-line board, check whether the OTU2 board at station
B reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.

307
OptiX OSN 8800/6800/3800

If ...
Then ...
The OTU2 board reports the

preceding alarms,
Handle these alarms in advance. That is,

clear these alarms according to the
corresponding methods.
The OTU2 board does not report the See cause 2.

preceding alarms,
3.
If the OTU4 board consists of a tributary board and a line board, check whether the
line board at station C reports the R_LOS, OTUk_SSF, and OTUk_LOF alarms.
If ...
Then ...
The line board at station C reports

the preceding alarms,
Handle these alarms in advance. That is,

The line board at station C does not See the next step.
report the preceding alarms,
4.
Check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and
OTUk_LOF alarms.
If ...
Then ...
The OTU2 board at station B reports Handle these alarms in advance. That is,
The OTU2 board at station B does
not report the preceding alarms,
l
Issue 02 (2011-10-31)
See cause 2.
Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF
1.
and then the OTU board that reports the alarm at the station.
2.
Check whether the ODUk_TCMn_SSF, ODUk_TCMn_LCK, ODUk_TCMn_OCI,

ODUk_TCMn_AIS, ODUk_TCMn_LTC, or the ODUk_TCMn_TIM alarm is
reported at the station. If yes, handle the alarm in advance. That is, clear the alarm
according to the corresponding method.
3.
Cause 3: The station reports the OTUk_TIM alarm and the ODUk_PM_SSF alarm at the
same time.
1.
Check whether the OTUk_TIM alarm is reported at the station. If yes, handle the alarm
in advance. That is, clear the alarm according to the corresponding method.
2.
Cause 4: In the case of a station configured with tributary boards and line boards, the line
boards report the ODUk_PM_SSF alarm when the line is abnormal.
308
OptiX OSN 8800/6800/3800

1.
Check whether the R_LOS, OTUk_SSF, and OTUk_LOF alarms are reported on the
WDM side of the line board at the station. If yes, handle the alarms in advance. That
is, clear the alarms according to the corresponding methods.
If ...
Then ...
The line board at the station reports Handle these alarms in advance. That is,
The line board at the station does not Contact Huawei engineers.
report the preceding alarms,
----End
Related Information
None
3.30 OMS_FDI
Description
This alarm is a forward defect indication at OMS layer. When the OMS_FDI-P and OMS_FDIO alarms coexist, this alarm is generated. At the same time, the OMS_FDI-P and OMS_FDI-O
alarms are suppressed. When the board at the OTS layer detects a loss of signal alarm but cannot
forward the alarm to the downstream station, it inserts the OMS_FDI signal. When the
downstream station receives the OMS_FDI signal, it reports the OMS_FDI alarm.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

The existing services may be interrupted.
Fault Symptom
Table 3-32 lists the fault symptom for the OMS_FDI alarm.
Issue 02 (2011-10-31)

309
OptiX OSN 8800/6800/3800

Table 3-32 Fault symptom for the OMS_FDI alarm

Fault Symptom
Cause

OTS_LOS or OTS_TIM alarm.
Cause 2: At the upstream station, a fiber cut

occurs or the optical power is excessively
low. Thus, the loss of signal alarm is detected
at the downstream station, and an OMS_FDI
alarm is then inserted to the downstream
station.
NOTE
Possible Causes
The possible causes of the OMS_FDI alarm are as follows:
l
Cause 1: The logical fiber connections are inconsistent with the physical fiber connections.
Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Thus, the loss of signal alarm is detected at the downstream station, and the OMS_FDI is
then inserted to the downstream station.
Cause 1: The logical fiber connections are inconsistent with the physical fiber connections.
Procedure
1.
Check whether the logical fiber connection configured for the optical interface where
the alarm is generated is consistent with its physical fiber connection. If not, modify
the configuration of the logical fiber connection so that the logical fiber connection is
consistent with the physical fiber connection. For details, see "Checking Logical
Fibers" in the Supporting Tasks.
2.
Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Thus, the loss of signal alarm is detected at the downstream station, and then the OMS_FDI
is inserted to the downstream station.
1.
Check whether an OTS_LOS or OTS_TIM alarm is generated at the opposite station

and all upstream stations. If yes, troubleshoot the OTS_LOS or OTS_TIM alarm
according to the alarm handling procedure.
2.
----End
Related Information
None.
Issue 02 (2011-10-31)

310
OptiX OSN 8800/6800/3800

3.31 OSC_LOS
Description
The OSC_LOS alarm indicates the loss of input optical power on receiving line. This alarm is
generated when the input optical power of the OSC board exceeds the LOS threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

There is a fiber break in the receive direction and this can cause loss of the monitoring signals.
Possible Causes
l
Cause 1: A certain optical port on the board that reports the alarm is not connected to a
fiber.
Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.
Cause 4: The transmit part of the opposite station is faulty.
Cause 5: The receive part of the local station is faulty.
Query the alarm on the U2000 and record the IDs of the optical port and channel where the
alarm is generated.
Cause 1: A certain optical port on the board that reports the alarm is not connected to a
fiber.
Procedure
1.
l
1.
Issue 02 (2011-10-31)
Check whether the fiber jumper is connected to the optical port of the board at the
local station. If not, connect the fiber jumper.
Use the U2000 to check whether the laser of the specific board at the opposite station
is on. If not, open the laser of the board.
Cause 3: The attenuation of the transmission line is excessively high, or a fiber break occurs
on the transmission line.
311
OptiX OSN 8800/6800/3800

1.
On the U2000 check whether the receive optical power at the optical port where the
alarm is generated is within the normal range. For the optical power specification of
the specific board, refer to "Technical Specifications" of the Product Description.
2.
If the receive optical power is not within the normal range, clear the alarm according
to the handling procedure for the IN_PWR_LOW or IN_PWR_HIGH.
3.
If the receive optical power is normal, check the fiber connector. If the fiber connector
is dirty or damaged, clean or replace the fiber connector.
Cause 4: The transmit part of the opposite station is faulty.

1.
If the alarm persists, replace the faulty board. For details, refer to "Replacing a Board"
Cause 5: The receive part of the local station is faulty.

1.
----End
Related Information
None.
3.32 OTS_LOS
Description
The OTS_LOS alarm indicates a loss of signal at the OTS layer. When the OTS_LOS-P and
OTS_LOS-O alarms coexist, this alarm is generated. At the same time, the OTS_LOS-P and
OTS_LOS-O alarms are suppressed.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Possible Causes
Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
Issue 02 (2011-10-31)

312
OptiX OSN 8800/6800/3800

Procedure
l
Check the alarm information on the U2000 and record the IDs of the optical interface and
channel where the alarm is generated.
Cause 1: The OTS_LOS-P and OTS_LOS-O alarms exist at the opposite station.
1.
Check whether the logical fiber connections of the FIU are consistent with the physical
fiber connections. If not, modify the configuration of the logical fiber connections so
that logical fiber connections are consistent with the physical fiber connections.
2.
Check and make sure that the fiber connection between the "IN" interface on the local
FIU and the opposite station is correct and reliable.
3.
If the alarm persists, check whether the attenuation of the "IN" interface on the FIU
is excessively high. If yes, adjust the attenuation to a proper value.
4.
If the alarm persists, check and make sure that fibers connected to the optical interfaces
on the FIU are correct and reliable.
----End
Related Information
None.
3.33 OTUk_LOF
Description
The OTUk_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal. This
alarm occurs when the frame alignment processing is out of frame (OOF) in three consecutive
milliseconds.
l
For OptiX OSN 8800, its value is 1, 2, 3.
For OptiX OSN 6800, its value is 1, 2, 3 or 5G.
For OptiX OSN 3800, its value is 1, 2 or 5G.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Services on the board are interrupted.
Issue 02 (2011-10-31)

313
OptiX OSN 8800/6800/3800

Fault Symptom
Table 3-33 lists the fault symptom for the TEMP_OVER alarm.
Table 3-33 Fault symptom for the OTUk_LOF alarm
Fault Symptom
Cause
Two boards at two ends of a single

wavelength report the OTUk_LOF alarm in
the deployment.
Cause 1: The settings of the service type or

FEC type are incorrect.
A single board at one end reports the

OTUk_LOF alarm in the deployment. In
addition, the alarm indicating abnormal
optical power is reported.
Cause 3: The receive optical power or the

OSNR of the local board is abnormal.
Multiple boards on the same link report the

OTUk_LOF alarm in the deployment.
Cause 6: The dispersion compensation value

is excessively great or small.
A single board at one end reports the

OTUk_LOF alarm in the deployment.
Cause 2: The board that reports the alarm is

faulty.
A board reports the OTUk_LOF alarm during

normal operation after deployment.
Cause 2: The board that reports the alarm is

faulty.
NOTE
Possible Causes
l
Cause 1: The settings of the service type or FEC type are incorrect.
Cause 3: The receive optical power or the OSNR of the local board is abnormal.
Cause 4: The signals transmitted by the corresponding board at the opposite end do not
have a frame structure.
Cause 5: The fiber of the transmission line is abnormal.
Cause 6: The dispersion compensation value is excessively great or small.
Cause 1: The settings of the service type or FEC type are incorrect.
Procedure
Issue 02 (2011-10-31)
1.
Query the FEC type on the U2000 to check whether the set FEC type is the same as
the FEC type supported by the board. For the specific service types and FEC types,
see the Hardware Description. If the FEC type is different from the FEC type
supported by the board, reset the FEC type to the same as the FEC type supported by
the board. For details about the operation, see Setting the FEC Type in the Supporting
Tasks.
2.
314
OptiX OSN 8800/6800/3800


1.
See Performing Hardware Loopback to perform the relevant operation on the optical
port where the alarm is reported. Then check whether the alarm is cleared.
2.
If the alarm persists, replace the board.

If ...
Then ...
modules,
Replacement.
3.
l

Tasks.
If the alarm disappears, see cause 3.
Cause 3: The receive optical power or the OSNR of the local board is abnormal.
1.
Check whether the input optical power of the position where the alarm is first
generated is within the normal range. For the optical power specifications of specific
boards, see the Product Description. If the optical power is abnormal, see the handling
methods of the IN_PWR_HIGH and IN_PWR_LOW alarms to clear the alarms.
2.
Cause 4: The signals transmitted by the corresponding board at the opposite end do not
have a frame structure.
1.
Test the signal sent from the WDM side on the board at the opposite station by using
a meter. Check whether the signal is the white light without signal frame or does not
have the OTN frame format. If the light does not comply with the requirement, replace
the faulty board.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
Cause 5: The fiber of the transmission line is abnormal.

1.
If the alarm persists, check whether the fiber meets the following requirements:
The bending radius is not less than 40 mm.
The optical port connector is well inserted.
The fiber connector is clean.
The cable is intact.
Issue 02 (2011-10-31)

315
OptiX OSN 8800/6800/3800

If the preceding requirements are not met, clean the fiber connector or replace the
fiber. For details, refer to "Inspecting and Cleaning the Fiber-Optic Connectors" of
2.
l
Cause 6: The dispersion compensation value is excessively great or small.

1.
If the alarm persists, replace the DCM module. For details about the operations, see
Replacing a DCM in the Supporting Tasks.
2.
----End
Related Information
ITU-T G.709
3.34 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Fault Symptom
Table 3-34 lists the fault symptom for the OTUk_SSF alarm.
Issue 02 (2011-10-31)

316
OptiX OSN 8800/6800/3800

Table 3-34 Fault symptom for the OTUk_SSF alarm

Fault Symptom
Cause
A station may report the R_LOS,

ODUk_PM_SSF alarm at the same time.
Cause 1: The station reports the R_LOS alarm

and the OTUk_SSF alarm at the same time.
A station may report the OTUk_AIS,

OTUk_LOF, or OTUk_LOM alarm at the
same time.
Cause 2: The station reports the OTUk_AIS,

OTUk_LOF, or OTUk_LOM alarm and the
NOTE
Possible Causes
l
Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time.
As shown in the following figure, the client side (the client side accesses the OTU service)
in the receive direction of the OTU1 board at station A or the WDM side in the receive
direction of the OTU2 board at station B reports the R_LOS alarm.
O
T
U
1
Client WDM
side
side
M
U
X/
D
M
U
X
OA
OA
F
I
U
F
I
U
Station A
OA
OA
M
U
O
X/
T
D
U
M
2
U
Client
WDM
X
side side
Station B
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time.
Procedure
Issue 02 (2011-10-31)
1.
board at station A or the OTU2 board at station B in the figure.
2.
Check whether the R_LOS alarm is reported in the receive direction of the OTU board
at the station.

317
OptiX OSN 8800/6800/3800

If ...
Then ...
The OTU board reports the

preceding alarm,
Handle the alarm in advance. That is, clear

the alarm according to the corresponding
method.
The OTU board does not report the See cause 2.

preceding alarm,
l
Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
1.
board at station A or the OTU2 board at station B in the figure.
2.
Check whether the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm is reported in the

receive direction of the OTU board at the station.
If ...
Then ...
The OTU board reports the

preceding alarm,
Handle the alarm in advance. That is, clear

the alarm according to the corresponding
method.
The OTU board does not report the Contact Huawei engineers.
preceding alarm,
----End
Related Information
None
3.35 OUT_PWR_HIGH
Description
This alarm indicates that the output optical power is very high. This alarm is generated when
the laser output optical power exceeds the upper threshold.
Reported from the WDM or client side: WDM side, client side.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

318
OptiX OSN 8800/6800/3800


l
When the output optical power is excessively high, the input optical power at the receive
end will be very high if no proper optical attenuator is used at the receive end. As a result,
the module at the receive end may be damaged.
If the board works abnormally, the existing services are affected.
Fault Symptom
None.
NOTE
Possible Causes
Cause 1: The optical module of laser is faulty or the board is faulty.
Procedure
l
Check the alarm information on the U2000 and record the IDs of the optical port and channel
where the alarm is generated.
Cause 1: The optical module of laser is faulty or the board is faulty.

1.
If ...
Then ...
modules,
Replacement.
The board does not supports
2.

Tasks.
----End
Related Information
None.
3.36 PORT_MODULE_OFFLINE
Description
This alarm indicates that the optical module on an optical port is offline. This alarm is generated
when the board detects that an optical module is offline.
Issue 02 (2011-10-31)

319
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Absence of the optical module leads to an interruption of services through by the corresponding
optical port.
Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1: The optical module does not exist or is not correctly inserted in the optical port.
Cause 2: The optical module or the board is faulty.
Cause 1: The optical module does not exist or is not correctly inserted in the slot.
Procedure
1.
Issue 02 (2011-10-31)
Check whether the optical port where this alarm is generated has an optical module.
If ...
Then ...
The optical port has no optical

module.
Insert an optical module into the optical

port properly.
The optical port has an optical

module.
See the alarm handling procedure for

cause 2.
Cause 2: The optical module or the board is faulty.

1.
2.
If the alarm persists, the board that reports the alarm may be faulty.If the board uses
pluggable optical modules, replace the specific pluggable optical module. For details,
refer to "Replacing Pluggable Optical Modules" of the Parts Replacement.
3.
If the optical module is not pluggable, replace the faulty board. For details, refer to
320
OptiX OSN 8800/6800/3800

4.
----End
Related Information
None.
3.37 POWER_FAIL
Description
This alarm indicates a power failure. This alarm is generated if the power supply of a board
becomes abnormal. For example, there is overvoltage or undervoltage of the power supply, or
the battery on the SCC has no charge.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the state of the power supply in which the alarm is generated. For
example:
0x3d indicates the undervoltage of the -48 V power supply.
0x3f indicates the undervoltage of the -60 V power supply.
0x3e indicates the overvoltage of the -48 V power supply.
0x40 indicates the overvoltage of the -60 V power supply.
0x05 indicates that the voltage of the battery is excessively low or the battery
fails.
0x53 indicates the undervoltage of the -48 V fan power supply.
0x54 indicates the overvoltage of the -48 V fan power supply.
Issue 02 (2011-10-31)

321
OptiX OSN 8800/6800/3800


l
If this alarm is reported by the SCC board, the system time is lost when the system is
powered off.
If this alarm is reported by other boards,

If the active power supply fails but the standby power supply is normal, there is no
impact on the existing services, because a switching to the standby power supply is
performed.
If both active and standby power supply fail, the existing services are interrupted.
Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1: If this alarm is reported by the SCC board, it indicates that the battery of the SCC
board is abnormal (the value of parameter 1 of this alarm is 0x05).
Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the
subrack is abnormal because the power supply module is faulty (the value of parameter 1
of this alarm is 0x3d or 0x3f).
Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power
supply module of the board fails or is aging (the value of parameter 1 of this alarm may be
any one but 0x05).
Cause 1: If this alarm is reported by the SCC board, it indicates that the battery of the SCC
board is abnormal (the value of alarm parameter 1 is 0x05).
Procedure
Issue 02 (2011-10-31)
1.
check whether the jumper cap is correctly placed over the battery jumper. If yes, check
the jumper setting of the battery on the SCC board. If the setting disables the battery
from proving power, change the setting to ensure that the battery to provide power to
the SCC board. For details about the jumper setting of the battery on the SCC board,
see the Hardware Description.
2.
If the alarm persists, use a multimeter to measure the battery voltage. If the voltage is
lower than 3 V, the battery is out of work. The board must be replaced. Replace the
faulty board. For details, see the Parts Replacement.
Cause 2: If this alarm is reported by the PIU board, it indicates that the input voltage of the
subrack is abnormal because the power supply module is faulty (the value of parameter 1
of this alarm is 0x3d or 0x3f).
1.
Check whether the switch on the DC power distribution box of the cabinet is ON. If
not, turn it to ON.
2.
If the alarm persists, it indicates that the switch on the DC power distribution box is
faulty. In this case, replace the switch. For details, see "Replacing the Power Switch
on the DC Power Distribution Box" in the Parts Replacement.
322
OptiX OSN 8800/6800/3800

Cause 3: If this alarm is reported by the PIU or CRPC board, it indicates that the power
supply module of the board fails or is aging (the value of parameter 1 of this alarm may be
any one but 0x05).
1.
Replace the faulty board. For details, see "Replacing the PIU Board" or "Replacing
the Raman Amplifier Board" in the Parts Replacement.
----End
Related Information
Related Cases:
l
MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER

Alarms
MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution
MC-A112 The SCC Housed In the Slave Subrack Reports the POWER_FAIL Alarm
Because the Jumper on the Board Is Set Improperly
MC-A204 Power Modules on Multiple Boards Report the POWER_FAIL Alarms Due to
Excessively High Temperature
3.38 PUMP_COOL_EXC
Description
This alarm indicates that the cooling current of the pump laser exceeds the threshold. This alarm
is generated when the laser cooling current exceeds the upper threshold.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates that the cooling current exceeds the threshold. The value is always
0x01.
Issue 02 (2011-10-31)

323
OptiX OSN 8800/6800/3800


When this alarm is reported, the laser ages sharply and the performance of output signals
degrades.
Fault Symptom
Table 3-35 lists the fault symptom for the PUMP_COOL_EXC alarm.
Table 3-35 Fault symptom for the PUMP_COOL_EXC alarm
Fault Symptom
Cause
The NE that reports this alarm reports a

temperature alarm or fan fault alarm, such as
TEMP_OVER or FAN_FAIL, within a
certain time.
Cause 1: The ambient temperature of the

board is excessively high or low.
NOTE
Possible Causes
The possible causes of the PUMP_COOL_EXC alarm are as follows:
l
Cause 1: The ambient temperature is excessively high or low.
Cause 2: The pump laser temperature is excessively high or low.
Cause 1: The ambient temperature is excessively high or low.
Procedure
1.
Check the ambient temperature inside the telecommunications room, the cleanliness
of the air filter, and heat dissipation through fans. For details, see TEMP_OVER to
rectify the fault.
2.
procedure for causes 2 and 3.
Causes 2: The pump laser temperature is excessively high or low/Cause 3: The board that
reports this alarm is faulty.
1.
2.
----End
Related Information
None.
Issue 02 (2011-10-31)

324
OptiX OSN 8800/6800/3800

3.39 R_LOF
Board Type
Alarm page link

3.39.1 R_LOF (OCS)

SLO16, or EGSH
3.39.2 R_LOF (OTN)
3.39.1 R_LOF (OCS)

Description
The R_LOF (OCS) alarm indicates loss of frame on the receive side of the line. When the R_OOF
alarm are received in consecutive 3 ms by the optical interface on the receive side of the local
optical station, the R_LOF alarm is reported.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
When the R_LOF alarm is generated, the services are interrupted, and the AIS signal is
inserted in the downstream station.
When the R_LOF occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station reports the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOF alarm are as follows:
l
Cause 1: Two boards at different rates are connected to each other.
Cause 2: The receive optical power is excessively low.
Issue 02 (2011-10-31)

325
OptiX OSN 8800/6800/3800

Cause 3: The receive optical power is excessively high.
Cause 4: The transmit optical power of the opposite station is abnormal.
Cause 6: The transmitted signals do not have the frame structure because of the fault of the
opposite board.
Supporting Task.
Cause 1: Two boards at different rates are connected to each other.
Procedure
1.
The improper fiber connection may cause that two boards at different rates are
connected to each other. This affects the service configuration. Correct the fiber
connection and then check whether the alarm is cleared.
2.
If the alarm persists, check whether the types of the two boards are the same. If the
board that supports the FEC function is connected to the board that does not support
the FEC function, two boards at different rates may be connected to each other. Enable
or disable the FEC function of the two boards according to the actual condition. For
details, see Enabling the FEC Function in the Supporting Task. For details on the
boards that support the FEC function, see the "Function and Feature" of each board
in the Hardware Description. Then, check whether the alarm is cleared.
3.
Cause 2 and cause 3: The receive optical power is excessively low.

1.
On the U2000, check whether the receive optical power of the local station is within
the normal range. For details on optical power specification of the board,
see"Technical Specifications" of the Product Description. For details of the
operations, see Querying Optical Power of the Board in the Supporting Task.
NOTE
manufacturer information about the optical module.
2.
If...
Then...
The receive optical power of the local board is

excessively low

excessively high
Go to step 3.
Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task
to check whether the connectors are dirty. If the fiber connector is dirty, clean
immediately. For the operations, see Supporting Task.
3.
Issue 02 (2011-10-31)
If the alarm persists, check whether the attenuation of the optical attenuator is correct.
If the attenuation is not correct, change the value. The attenuation of the optical
326
OptiX OSN 8800/6800/3800

attenuator depends on the receive optical power of the board. For details, see
Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
If...
Then...
The optical attenuation is excessively

low
Decrease the optical attenuation and


high
Increase the optical attenuation and

alarm persists, see cause 4.
4.
Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check
5.

1.
On the U2000, check whether the transmit optical power of the opposite board is within
the normal range. For details on optical power specification of the board, see
"Technical Specifications" of the Product Description. For details of the operations,
see Querying Optical Power of the Board in the Supporting Task.
NOTE
2.
If the transmit optical power of the opposite board is abnormal, see the
OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check
whether the R_LOF alarm is cleared.
3.

1.
Perform a selfloop (hardware inloop) on the receive and transmit interfaces of the
board. For details, see Performing Hardware Loopback in the Supporting Task.
CAUTION
CAUTION
The overload of optical power should be avoided when the hardware inloop is
performed. According to the optical power specifications of the board, add an optical
attenuator on the receive optical interface. For the operations of adding an attenuator,
see Adjusting, Replacing, Adding and Removing Attenuator in the Supporting Task.
Issue 02 (2011-10-31)

327
OptiX OSN 8800/6800/3800

If...
Then...
The alarm is reported
The local board is faulty. Proceed to the next step.
No alarm is reported
See cause 6.
2.
Replace the optical module or board at the local station. For details, see Replacing the
Pluggable Optical Module in the Parts Replacement. Otherwise, replace the faulty
board. For details, see Parts Replacement. Then, check whether the alarm is cleared.
3.
Cause 6: The transmitted signals at the opposite station do not have the frame structure.
1.
Replace the optical module or board at the opposite station. For details, see Replacing
the Pluggable Optical Module in the Parts Replacement. Otherwise, replace the board.
For details, see Parts Replacement.
----End
Related Information
None.
3.39.2 R_LOF (OTN)

Description
This alarm indicates loss of frame in the received signals. This alarm is generated when the frame
alignment processing is out of frame (OOF) in consecutive 3 ms.
Reported from the WDM side or client side:
l
WDM side - Check for this alarm when there are SDH frames in the services accessed on
the WDM side.
Client side - Check for this alarm when the SDH services are accessed on the client side.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
The board fails to locate the data frame of the received SDH signals, and therefore the
client services fail.
After this alarm is detected, a protection switching is performed if the board supports
protection switching.
Issue 02 (2011-10-31)

328
OptiX OSN 8800/6800/3800

Fault Symptom
Table 3-37 lists the fault symptom for the R_LOF alarm.
Table 3-37 Fault symptom for the R_LOF alarm
Fault Symptom
Cause
The upstream board may report an R_LOS or

R_LOF alarm.

side
NOTE
Possible Causes
l
Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF signal.
faulty.
Cause 1 for this alarm generated on the WDM side: The receive optical power or the OSNR
of the local board is abnormal.
Cause 2 for this alarm generated on the WDM side: The signals transmitted by the upstream
OTU have no SDH frame structure.
faulty.
Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
Cause 5 for this alarm generated on the WDM side: The dispersion is under- or overcompensated.
Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF alarm signal.
Procedure
1.
between the transmit and receive optical ports on the client side of the board. If this
alarm on the board persists, it indicates that the board is faulty. In this case, see the
CAUTION
Issue 02 (2011-10-31)

329
OptiX OSN 8800/6800/3800

2.
l
If this alarm is cleared, it indicates that the input signals on the client side contain an
R_LOF signal. In this case, rectify the fault on the client equipment.
faulty.
1.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
Cause 1 for this alarm generated on the WDM side/Cause 2 for this alarm generated on the
WDM side: The receive optical power or the OSNR of the local board is abnormal; the
signals transmitted by the upstream OTU have no SDH frame structure.
1.
If the WDM side reports this alarm, on the U2000 check whether the client side of the
board at the opposite station reports an R_LOF alarm. If yes, rectify the fault according
to the procedure for handling the R_LOF alarm generated on the client side.
2.
If the alarm persists, on the U2000 check whether the receive optical power at the
WDM-side optical port of the alarm-reporting board is within normal range. For the
optical power specification of the specific board, refer to "Technical Specifications"
of the Product Description.
NOTE
on the board.
3.
If the optical power is abnormal, rectify the fault according the procedure for handling
the IN_PWR_LOW or IN_PWR_HIGH alarm.
4.
If the receive optical power is normal, use an SDH meter to receive signals from the
WDM side of the board in opposite station. Check whether the received signal is of
white spectrum (no signal frame) or has no SDH frame. If the received signal fails to
comply with the requirement, replace the faulty board.
If ...
Then ...
modules,
Replacement.
Issue 02 (2011-10-31)

Tasks.

330
OptiX OSN 8800/6800/3800

5.
l
faulty.
1.
If the alarm persists, the board may be faulty. Replace the faulty board at the local
station.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.
Cause 4 for this alarm generated on the WDM side: The input signals from the upstream
station contain an R_LOS or R_LOF signal.
1.
If the alarm persists, clear the alarm of the equipment at the upstream station.
2.
Cause 5 for this alarm generated on the WDM side: The dispersion is under- or overcompensated.
1.
If the alarm persists, replace the DCM module. For details, see "Replacing a DCM"
in the Supporting Tasks.
2.
----End
Related Information
Related Cases:
l
MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
MC-A21 An Interconnection Failure between the WDM and SDH Equipment
MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
MC-A31 Wrong Calculation for Dispersion in One DWDM Project
MC-A104 No Optical Power Is Output on the WDM Side Due to Incorrect

Configuration,the Board Reports the R_LOF, R_LOC, TP_LOC Alarms
MC-A115 Determine Whether the Type and Connections Of the Dispersion Compensation
Module (DCM) Are Proper When the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD
Alarms Are Reported on the WDM Side of LWF Board
MC-A128 EPL Service Was Interrupted Due To a Service Mode Mismatch of L4G Boards
and Nodes Report R_LOF, ODU5G_PS_AIS, OTU5G_LOF, LINK_ERR Alarm
Issue 02 (2011-10-31)

331
OptiX OSN 8800/6800/3800

None.
3.40 R_LOS
Board Type
Alarm page link

3.40.1 R_LOS (OCS)

SLO16, or EGSH
3.40.2 R_LOS (OTN)
3.40.1 R_LOS (OCS)

Description
The R_LOS (OCS) alarm indicates the loss of signal on the receive side of the line.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
When the R_LOS alarm is generated, the services are interrupted, and the AIS signal is
inserted at the downstream station.
When the R_LOS occurs, the system automatically returns the MS_RDI alarm to the
upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_LOS alarm are as follows:
l
Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface
board).
Identification method: Use instruments to test the fiber.
Issue 02 (2011-10-31)

332
OptiX OSN 8800/6800/3800

Cause 2 of the fiber: The optical interface of the local board is not connected to the fiber
jumper or is connected to an incorrect fiber jumper (if the alarm is reported by an SDH
optical interface board).
Identification method: Check the connection of the fiber jumper.
Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power
is excessively low (if the alarm is reported by an SDH optical interface board).
Identification method: Query the optical power of the two stations.
Cause 1 of the laser: The local optical interface is not used.

Identification method: Check whether the optical interface is in use (if the alarm is reported
by an SDH optical interface board).
Cause 2 of the laser: The opposite laser is inactive, and as a result, no signal is input.
Identification method: Check whether the laser is in use (if the alarm is reported by an SDH
optical interface board).
Cause 1 of the board: The receive board at the local station is faulty. As a result, the line
receiving fails.
Identification method: Perform a loopback.
Cause 2 of the board: The transmit board at the opposite station is faulty. As a result, the
line transmitting fails.
Identification method: Locate the fault with the exclusive method.
Procedure
l
Query current alarms on the U2000. Determine the ID of the optical interface that reports
the alarm according to alarm parameter 1. For details, see Querying the Current Alarms in
the Supporting Task.
Cause 1 of the fiber: There is a fiber cut (if the alarm is reported by an SDH optical interface
board).
1.
Use the optical time-domain reflectometer (OTDR) to test the fiber, and check whether
there is a fiber cut and determine the location of the fiber cut according to the
attenuation curve of the line shown on the OTDR.
NOTE
The OTDR has a dead zone when it is very close to the fiber.
If...
Then...
A fiber cut occurs on the line
Replace the fiber and check whether the alarm is

cleared. If the alarm persists, see other causes.
No fiber cut occurs on the line See other causes.

l
Cause 2 of the fiber: The optical interface of the local board is loose, is not connected to
the fiber jumper, or is connected to an incorrect fiber jumper (if the alarm is reported by
an SDH optical interface board).
1.
Issue 02 (2011-10-31)
Check the fiber jumper connected to the optical interface of the local board.

333
OptiX OSN 8800/6800/3800

2.
If...
Then...
The connection between the fiber

jumper and the interface is loose
Tighten the fiber jumper and check

whether the alarm is cleared. If the
The connection between the fiber

jumper and the interface is secure
Check whether the tail fiber is connected to the optical interface of the local board
properly.
If...
Then...
The fiber jumper is connected

improperly
According to the networking

environment, connect the fiber jumper
between optical boards in the subrack
properly and check whether the alarm is
cleared. If the alarm persists, see other
causes.
The fiber jumper is connected

properly
See other causes.
Cause 3 of the fiber: The line attenuation is excessively high. As a result, the optical power
is excessively low (if the alarm is reported by an SDH optical interface board).
1.
Measure the transmit optical power of the opposite board and the receive optical power
of the local board. For details, see Querying Optical Power of the Board in the
Supporting Task.
If...
Then...
The transmit optical power of the opposite station is See cause 2 of the board.
abnormal
The receive optical power of the local station is
abnormal
2.
The difference between the transmit optical power of the opposite station and the
receive optical power of the local station is the actual optical power attenuation of the
line. Compare the result with the line attenuation in the engineering design. If the
actual attenuation is excessively high, perform the following steps to find the fault
and rectify it.
(1) Check whether there are too many optical connectors on the fiber line and
whether they are connected to the optical modules securely. If the connectors are
loose, insert the connectors into the optical modules securely.
(2) Check whether there are aerial optical fiber cable on the fiber line that may be
damaged because of bad weather. If yes, provide a protection for the aerial optical
fiber cable.
Issue 02 (2011-10-31)

334
OptiX OSN 8800/6800/3800

(3) Check whether the type of the fiber and the attenuation factor on the fiber line
meet the requirements specified in the engineering design document. If not,
replace the fiber.
(4) Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting
Task to check whether the optical connector in the fiber line is dirty. If the fiber
connector is dirty, clean it immediately. For the operations, see the Supporting
Task.
3.
l
Check whether the alarm is cleared. If the alarm persists, see other causes.
Cause 1 of the laser: The local optical interface is not used (if the alarm is reported by an
SDH optical interface board).
1.
Check whether an unused fiber is connected to the optical interface of the board. If
yes, perform the self-loop on the receive and transmit optical interfaces by using the
unused fiber.
2.
Cause 2 of the laser: The laser at the opposite station is inactive. As a result, no signal is
input (if the alarm is reported by an SDH optical interface board).
1.
Check whether the laser of the corresponding opposite board is shut down. If yes,
switch on the laser on the optical interface. For details, see Opening/Closing Lasers
2.
Causes 1 of the board: The receive board at the local station is fault. As a result, the line
receiving fails.
1.
CAUTION
CAUTION
Issue 02 (2011-10-31)
If...
Then...
See other causes.

335
OptiX OSN 8800/6800/3800

2.
Replace the optical module or board at the local station. If the board supports pluggable
optical module, replace the specific pluggable optical module. Otherwise, replace the
faulty board. For details, see Parts Replacement.
Cause 2 of the board: The transmit board (including the cross-connect and timing board)
at the opposite station is faulty. As a result, the line transmitting fails.
1.
If the opposite board supports the pluggable optical module, replace the pluggable
optical module. Otherwise, replace the opposite faulty board. For details, see Parts
Replacement.
2.
----End
Related Information
None.
3.40.2 R_LOS (OTN)

Description
This alarm indicates a loss of signal. This alarm is generated when the receive side receives no
signal.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None.

Services through optical port where this alarm is generated are interrupted.
Possible Causes
l
Cause 1 for this alarm generated on the client side: The fiber jumper is not connected at
the optical port of the board.
Cause 2 for this alarm generated on the client side: The line attenuation is excessively high
or there is a fiber cut.
faulty.
Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the
optical port on the board of the local station, the fiber jumper connected to the optical port
is loose, or the fiber jumper is connected incorrectly.
Issue 02 (2011-10-31)

336
OptiX OSN 8800/6800/3800

Cause 2 for this alarm generated on the WDM side: The line attenuation is excessively high
Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
Cause 4 for this alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
this alarm is generated.
Cause 1 for this alarm generated on the client side: No fiber jumper is connected to the
Procedure
1.
Check the fiber jumper connection on the board that reports this alarm at the local
station.
If ...
Then ...
No fiber jumper is connected to the

optical port,
Connect the fiber jumper that is

connected to the upstream board to the
optical port.
A fiber jumper is connected to the

optical port,
Check whether the fiber jumper is

connected tightly to the optical port. If
not, secure the fiber jumper to the optical
port.
2.
Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
3.
Cause 2 for this alarm generated on the client side: The line attenuation is excessively high
1.
Use a test instrument to test the fiber connection to determine whether a fiber break
occurs. If yes, replace the fiber.
2.
Check whether this alarm is cleared. If the alarm persists, on the U2000 check whether
the receive optical power of the optical port is within the normal range. For the optical
power specifications of the board, see the Product Description.
If ...
Then ...
The receive optical power exceeds See IN_PWR_LOW or IN_PWR_HIGH to

the normal range,
rectify the fault.
The receive optical power is
normal,
Issue 02 (2011-10-31)
Check the relevant fiber connectors. If the

fiber connectors are dirty, clean or replace the
fiber connectors.

337
OptiX OSN 8800/6800/3800

3.
l
faulty.
1.
side of the board that reports this alarm. If this alarm persists, it indicates that the board
is faulty. In this case, replace the board. For details, refer to "Replacing a Board" of
the Supporting Tasks. If this alarm is cleared, it indicates that the output power of the
client equipment is abnormal. In this case, check for and rectify the fault on the client
equipment.
2.
Cause 1 for this alarm generated on the WDM side: No fiber jumper is connected to the
1.
Check the fiber jumper connection on the board that reports this alarm at the local
station.
If ...
Then ...
No fiber jumper is connected to the

optical port,
Connect the optical port properly.
A fiber jumper is connected to the

optical port,
Check whether the fiber jumper is

connected tightly to the optical port. If
not, secure the fiber jumper to the optical
port.
2.
Check whether this alarm is cleared. If the alarm persists, check whether the fiber
jumper is connected properly. Reconnect fiber jumpers between boards according to
the actual networking environment.
3.
Cause 2 for this alarm generated on the WDM side: The line attenuation is excessively high
1.
On the U2000, check whether the receive optical power at the optical port is within
If ...
Then ...
The receive optical power exceeds See IN_PWR_LOW or IN_PWR_HIGH to

the normal range,
rectify the fault.
The receive optical power is
normal,
Issue 02 (2011-10-31)
Check the relevant fiber connectors. If there

is any dirt or damage, clean or replace the fiber
connectors. For how to troubleshoot the
specific fault, refer to "Troubleshooting
Optical Power Anomalies" of the
Troubleshooting.

338
OptiX OSN 8800/6800/3800

2.
l
Cause 3 for this alarm generated on the WDM side: The laser of the board at the opposite
station is shut down.
1.
On the U2000, check whether the laser on the board at the opposite station is on. If
not, open the laser.
2.
Cause 4 for this alarm generated on the WDM side: The transmit module of the opposite
station or receive module of the local station is faulty.
1.
If the alarm persists, check whether the board at the opposite station or the board at
the local station supports pluggable optical modules.
If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
Related Cases:
l
MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides. The
LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
MC-A14 The LWF Board Reports R_LOS
MC-A15 The Downstream Optical Amplifier Board Does Not Report R_LOS
MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
MC-A125 Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of
a fiber break
MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm Even
If the Attenuation Is Decreased
MC-A141 Normal Boards Are Mistakenly Considered Faulty due to Optical Module
Characteristics
MC-A145 The Client Equipment Interconnected with the TOM Board Reports the R_LOS
Alarm Due to a Problem with the Optical Module on the TOM Board
Issue 02 (2011-10-31)

339
OptiX OSN 8800/6800/3800

MC-A153 It Is Recommended to Enable the Auto-Negotiation Working Mode at a GE Port

When the LPT Function Is Enabled, Or The Services Are Interrupted And The System
Reports The R_LOS Alarms
MC-A154 The N2SLQ16 Board Interconnected with the TQS Board Reports an R_LOS
Alarm Because The TQS Board Emits White Lights When the Input Optical Power Is
Normal
MC-A156 An SDH Board on the SDH Equipment Reports an R_LOF Alarm When the
SDH Board Is Interconnected with a Tributary Board on the OptiX OSN 6800
MC-A159 Services Are Interrupted After the Protection Hold-Off Time Is Set to 10s During
Configuration of Client-Side 1+1 Protection on the OptiX OSN 6800, The System Reports
The R_LOS Alarm
MC-A164 Why the WDM-Side Service Rate Reaches 11.1 Gbit/s When the LSX Board
Receives 10GE-LAN Services in Bit Transparent Transmission Mode on the Client Side
MC-A182 Receive Optical Power Is Excessively Low Because of The End Face Problem
of the Fiber Jumper, The OAU Board Reports The MUT_LOS And R_LOS Alarms
MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
3.41 R_OOF
Board Type
Alarm page link

3.41.1 R_OOF (OCS)

SLO16, or EGSH
3.41.2 R_OOF (OTN)
3.41.1 R_OOF (OCS)

Description
The R_OOF (OCS) alarm indicates that the out-of-frame event occurs on the receive side of the
line. When the correct A1, A2 bytes are not contained in five consecutive frames received on
the receive side of the local optical station, the R_OOF alarm is reported.
Issue 02 (2011-10-31)

340
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
When the R_OOF alarm is generated, the services are interrupted, and the AIS signal is
inserted at the downstream station.
When the R_OOF alarm is generated, the system automatically returns the MS_RDI alarm
to the upstream station. Consequently, the upstream station generates the MS_RDI alarm.
Possible Causes
The possible causes of the R_OOF alarm are as follows:
l
Cause 1: The receive optical power is excessively low.
Cause 2: The receive optical power is excessively high.
Cause 4: The receive board at the local station is faulty (including the fault of the crossconnect board).
Cause 5: The transmit board at the opposite station is faulty (including the fault of the crossconnect board).
Supporting Task.
Cause 1: The receive optical power is excessively low. Cause 2: The receive optical power
is excessively high.
Procedure
1.
On the U2000, check whether the optical power of the local station is within the normal
range. For details on optical power specification of the board, see "Technical
Specifications" of the Product Description. For details, see Querying Optical Power
of the Board in the Supporting Task.
NOTE
manufacturer information about the optical module on the board.
Issue 02 (2011-10-31)
If...
Then...

excessively low

341
OptiX OSN 8800/6800/3800

2.
If...
Then...

excessively high
Proceed to step 3.
Refer to Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task
to check whether the connectors are dirty. If the fiber connector is dirty, clean it
immediately. For the operations, see Supporting Task.
3.
If the alarm persists, check whether the attenuation of the optical attenuator is correct.
If the attenuation is not correct, change the value. The value of the optical attenuator
depends on the receive optical power of the board. For details, see Adjusting,
Replacing, Adding and Removing Attenuator in the Supporting Task.
If...
Then...

low
Decrease the optical attenuation. Then,


high
Increase the optical attenuation. Then,

alarm persists, see cause 3.
4.
Check whether the fiber is damaged or oppressed. If yes, replace the fiber. Then, check
5.

1.
On the U2000, check whether the transmit optical power of the opposite board is within
the normal range. For details on optical power specification of the board, see
"Technical Specifications" of the Product Description. For details, see Querying
Optical Power of the Board in the Supporting Task.
NOTE
manufacturer information about the optical module on the board.
2.
If the transmit optical power of the opposite board is abnormal, see the
OUT_PWR_HIGH or OUT_PWR_LOW alarm to rectify the fault. Then, check
whether the R_OOF alarm is cleared.
3.
Cause 4: The receive board at the local station is faulty (including the fault of the crossconnect board).
1.
Issue 02 (2011-10-31)

342
OptiX OSN 8800/6800/3800

CAUTION
CAUTION
If...
Then...
See cause 5.
2.
Replace the optical module or board at the local station. If the board supports the
pluggable optical module, replace the pluggable optical module. For details, see
Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace
the faulty board. For details, see Parts Replacement. Then, check whether the alarm
is cleared.
3.
If the alarm persists, replace the local cross-connect board. For details, see Parts
4.
Cause 5: The transmit board at the opposite station is faulty (including the fault of the crossconnect board).
1.
Replace the optical module or board at the opposite station. If the board supports the
pluggable optical module, replace the pluggable optical module. For details, see
Replacing the Pluggable Optical Module in the Parts Replacement. Otherwise, replace
the faulty board. For details, see Parts Replacement. Then, check whether the alarm
is cleared.
2.
If the alarm persists, replace the cross-connect board at the opposite station. For details,
see Parts Replacement.
----End
Related Information
None.
3.41.2 R_OOF (OTN)

Description
This alarm indicates out of frame in the receive signals. This alarm is generated when the heads
of consecutive five frames fail to be detected.
Issue 02 (2011-10-31)

343
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Services through the optical interface where this alarm is generated are interrupted.
Fault Symptom
Table 3-40 lists the fault symptoms for the R_OOF alarm.
Table 3-40 Fault alarms for the R_OOF alarm
Fault Symptom
Cause
The board that reports this alarm also report

an IN_PWR_LOW alarm.

side
The board that reports this alarm also reports

bit error alarms, such as B1_EXC alarm.

side
NOTE
Possible Causes
l
Cause 1 for this alarm generated on the client side: The input signals on the client side are
abnormal and thus an R_OOF alarm is generated.
faulty.
Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the
received signals are excessively high.
Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
faulty.
Issue 02 (2011-10-31)

344
OptiX OSN 8800/6800/3800

Procedure
l
Cause 1 for this alarm generated on the client side: The input signals on the client side are
abnormal and thus an R_OOF alarm is generated.
1.
between the transmit and receive optical interfaces on the client side of the board. If
this alarm on the board persists, it indicates that the board is faulty. In this case, see
the alarm handling procedure for cause 2 of this alarm generated on the client side.
CAUTION
2.
l
If the alarm is cleared, it indicates that the input signals on the client side contain
R_OOF signals. In this case, rectify the fault on the client equipment.
faulty.
1.
If the alarm persists, replace the faulty board.

If ...
Then ...
modules,
Replacement.

Tasks.
Cause 1 for this alarm generated on the WDM side: The attenuation or optical power of the
received signals excessively high.
1.
If the client side reports this alarm, check whether the receive optical power of the
interface is within the normal range on the U2000. For the optical power specification
of the specific board, refer to "Technical Specifications" of the Product Description.
NOTE
on the board.
Issue 02 (2011-10-31)
2.
If the receive optical power is not within the normal range, see IN_PWR_LOW or
IN_PWR_HIGH to rectify the fault.
3.
If the receive optical power is within the normal range, see the alarm handling
Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
345
OptiX OSN 8800/6800/3800

1.
Check whether there are bit error alarms. If there are bit error alarms, clear the alarms
first according to the proper handling procedure.
2.
If there is no bit error alarm and the receive optical power is normal, check the fiber
connector. If the fiber connector is dirty or damaged, clean or replace the fiber
connector.
3.
Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
1.
On the U2000, check whether the transmit optical power at the corresponding optical
interface on the opposite OTU is within the normal range. For the optical power
specification of the specific board, refer to "Technical Specifications" of the Product
Description. For details, refer to "Querying Optical Power on the U2000" of the
Supporting Tasks.
2.
If the transmit optical power exceeds the normal range, it indicates that the opposite
board is faulty. In this case, replace the faulty board.
If ...
Then ...
modules,
Replacement.
3.
l

Tasks.
If the transmit optical power is within the normal range, see the alarm handling
faulty.
1.

If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
Related Cases:
Issue 02 (2011-10-31)

346
OptiX OSN 8800/6800/3800

MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
MC-A115 Determine Whether the Type and Connections Of the Dispersion Compensation
Module (DCM) Are Proper When the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD
Alarms Are Reported on the WDM Side of LWF Board
MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
3.42 R_SLIP
Description
This alarm indicates frame slipping on the receive side. The alarm is generated when the phase
deviation occurs in the received service frames of the OSC or OTC board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

This alarm has impact on services carried by the OSC. For example, the optical supervisory
signals or clock signals are degraded. As a result, the NE is disconnected from the U2000 system.
Fault Symptom
Table 3-41 lists the fault symptom for the R_SLIP alarm.
Table 3-41 Fault symptom for the R_SLIP alarm
Fault Symptom
Cause
The board that reports this alarm also report

an IN_PWR_HIGH or IN_PWR_LOW
alarm.
Cause 2: The optical line attenuation is

excessively high or the receive optical power
is excessively high.
NOTE
Issue 02 (2011-10-31)

347
OptiX OSN 8800/6800/3800

Possible Causes
l
Cause 1: The clock configuration is wrong or the clock signals are not synchronous.
Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC
board are connected reversely.
Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.
Procedure
1.
Check whether the clock configuration is correct. If not, reconfigure it to ensure that
the clocks of the total network are synchronous. For details on how to configure the
clock information, see "Physical Clock" in the Feature Description.
2.
Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
1.
On the U2000, check whether the receive optical power at the optical interface is
within the normal range. For the optical power specification of the specific board,
If ...
Then ...
The receive optical power is excessively Check the fiber jumper or the fiber
low,
connector. If the fiber jumper or fiber
connector is dirty, clean the fiber
connector or replace the fiber jumper.
The receive optical power is excessively adjust the optical attenuator to ensure
high,
that the receive optical power is within
the normal range.
2.
l
Cause 3: The fibers at the eastward and westward optical interfaces on the OSC or OTC
board are connected reversely. For example, the fibers for connecting to the TM1 optical
interface in the west and the TM2 optical interface in the east are connected reversely. See
the following figure.
1.
Issue 02 (2011-10-31)
If the alarm persists, check the engineering fiber connection diagram to see whether
the fibers at the eastward and the westward optical interfaces on the OSC or OTC
board are connected reversely. If the fiber connection is incorrect, correct it according
to the diagram.

348
OptiX OSN 8800/6800/3800

OA
F
I
U
RM1 TM2
SC2
TM1 RM2
F
I
U
OA
2.
l

1.
If the alarm persists, perform a cold reset on the faulty board on the U2000.
2.

If ...
Then ...
modules,
Replacement.
3.

Tasks.
----End
Related Information
Related Cases:
l
MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the
OSC Board
None.
3.43 REM_SF
Description
This alarm indicates that remote client-side services are not loaded. This alarm is generated when
the client side of the board at the opposite end fails to receive signals (for example, when there
is an R_LOS alarm).
Reported from the WDM or client side: client side.
Issue 02 (2011-10-31)

349
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Services borne by client sides of the board are interrupted.
Fault Symptom
Table 3-42 lists the fault symptom for the REM_SF alarm.
Table 3-42 Fault symptom for the REM_SF alarm
Fault Symptom
Cause
The OTU board at the opposite station reports

an R_LOS, R_LOF, R_LOC, MS_AIS, or a
LINK_ERR alarm.
Cause 1: An R_LOS, R_LOF, R_LOC,

MS_AIS, or a LINK_ERR alarm is generated
on the client side of the OTU at the opposite
station.
NOTE
Possible Causes
l
Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on

the client side of the OTU board at the opposite station.
Cause 2: The client side of the OTU board at the opposite end is faulty.
Cause 1: An R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR alarm is generated on

the client side of the OTU board at the opposite station.
Procedure
1.
Cause 2: The client side of the OTU board at the opposite end is faulty.
1.
Issue 02 (2011-10-31)
On the U2000, check whether an R_LOS, R_LOF, R_LOC, MS_AIS, or a LINK_ERR

alarm is generated on the client side of the OTU board at the opposite station. If yes,
see R_LOS, R_LOF, R_LOC, MS_AIS, LINK_ERR to clear the alarm.
Replace the OTU board at the opposite station.
350
OptiX OSN 8800/6800/3800

If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
None.
3.44 REMOTE_FAULT
Description
This alarm indicates a fault at the remote end.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the board receives the REMOTE_FAULT alarm, the services may be interrupted.
Fault Symptom
Table 3-43 lists the fault symptom for the REMOTE_FAULT alarm.
Table 3-43 Fault symptom for the REMOTE_FAULT alarm
Issue 02 (2011-10-31)
Fault Symptom
Cause
A LOCAL_FAULT alarm is reported from

the client side of the board at the opposite end.
Cause 1: The opposite station receives a

LOCAL_FAULT alarm.

351
OptiX OSN 8800/6800/3800

NOTE
Possible Causes
l
Cause 1: The opposite station receives a LOCAL_FAULT alarm.

The client side of OTU board at station A detects a LOCAL_FAULT alarm, and the client
side of the OTU board at station B reports a REMOTE_FAULT alarm.
Client
side
O
T
U
WDM
side
Station A
LOCAL_FAULT alarm
O
T
U
WDM
side
Client
side
Station B
REMOTE_FAULT alarm
Cause 2: The board at the opposite station is faulty.
Cause 1: The opposite station receives a LOCAL_FAULT alarm.
Procedure
1.
Clear the LOCAL_FAULT alarm at the opposite station.
2.
Cause 2: The board at the opposite station is faulty.

1.
Replace the faulty board at the opposite station. For details, refer to "Replacing a
Board" of the Supporting Tasks.
2.
----End
Related Information
None.
Issue 02 (2011-10-31)

352
OptiX OSN 8800/6800/3800

3.45 SECU_ALM
Description
The SECU_ALM is a security alarm. This alarm is generated when login fails after four
consecutive login failures performed by the same user.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
None.

The alarm automatically ends with no impact on the system.
Fault Symptom
None.
NOTE
Possible Causes
l
Cause 1: This alarm can be caused by illegal login. For example, the password is incorrect
or the user does not exist.
Cause 1: This alarm can be caused by illegal login. For example, the password is incorrect
or the user does not exist.
Procedure
1.
Check whether invalid users exist in the user list in the login window. If yes, delete
the invalid users from the user list.
2.
----End
Related Information
None.
Issue 02 (2011-10-31)

353
OptiX OSN 8800/6800/3800

3.46 SUBRACK_ID_CONFLICT
Description
This alarm indicates a conflict of subrack IDs. In the case of the master-slave subrack mode,
this alarm is reported when the master subrack detects that the DIP switch settings of the slave
subracks are repeated.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
Parameter
Description
Parameter 1
Indicates the conflict subrack ID.

The inter-subrack communication is abnormal. As a result, the master subrack cannot manage
the slave subrack.
Fault Symptom
Table 3-44 lists the fault symptom for the SUBRACK_ID_CONFLICT alarm.
Table 3-44 Fault symptom for the SUBRACK_ID_CONFLICT alarm
Fault Symptom
Cause
The board may report the BD_STATUS,

COMMUN_FAIL, and WRG_BD_TYPE
alarms at the same time.
l Cause 1: In the case of the master-slave

subrack mode, multiple master subracks
exist in the system.
l Cause 2: In the case of the master-slave
subrack mode, the DIP switch settings of
two slave subracks are repeated.
NOTE
Issue 02 (2011-10-31)

354
OptiX OSN 8800/6800/3800

Possible Causes
The possible causes of the SUBRACK_ID_CONFLICT alarm are as follows:
l
Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
Procedure
1.
There should be only one master subrack in the system. Check which master subrack
is redundant according to the actual networking and then remove it.
2.
Perform a warm reset on the SCC board in the master subrack.
3.
Perform a warm reset on all boards on the NE.
4.
Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
1.
Disconnect one slave subrack from the master subrack, and re-set the ID of this slave
subrack by changing the DIP switch setting on the SCC board. In this case, the IDs of
the two slave subracks are different.
2.
Perform a warm reset on the SCC board in the master subrack on the NE. For details,
see "Performing a Warm Reset on the Board" in the Supporting Tasks.
3.
After the subrack ID is changed, perform a warm reset on all the boards in the subrack.
For details, see "Performing a Warm Reset on the Board" in the Supporting Tasks.
4.
----End
Related Information
For details, see "Master-Slave Subrack" in the Feature Description.
3.47 SUM_INPWR_LOW
Description
Sum input optical power is excessively low. The alarm is generated when the input optical power
of the multiplexed signals is lower than the threshold.
This alarm is reported from neither the WDM side nor the client side.
Issue 02 (2011-10-31)

355
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None.

The output optical signals of a single channel of the board may be lost; the services in use may
have bit errors or even are interrupted.
Fault Symptom
Table 3-45 lists the fault symptom for the SUM_INPWR_LOW alarm.
Table 3-45 Fault symptom for the SUM_INPWR_LOW alarm
Fault Symptom
Cause
The upstream board reports an

OUT_PWR_LOW alarm.
Cause 1: The output optical power of the

upstream station decreases, and thus the input
optical power of the local station is
excessively low.
NOTE
Possible Causes
l
Cause 1: The output optical power of the upstream station decreases, and thus the input
optical power of the local station is excessively low.
Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
Cause 1: The output optical power of the upstream station decreases and thus the input
optical power of the local station is excessively low.
Procedure
1.
Issue 02 (2011-10-31)
On the U2000, check the output optical power of the boards at the upstream station
along the reverse direction of the signal flow. If the output optical power of a certain
356
OptiX OSN 8800/6800/3800

board is excessively low, adjust the output optical power of the board to a value within
the normal range.
2.
If the alarm persists, replace the board whose output optical power is excessively low.
For details, refer to "Replacing a Board" of the Supporting Tasks.
3.
Cause 2: The line attenuation is excessively high, or related fiber jumpers or fiber
connectors are dirty.
1.
If the output optical power of all the boards at the upstream stations is normal, check
whether an optical attenuator with excessively high attenuation is attached to the
receive optical interface on the board that reports this alarm. If yes, decrease the
attenuation of the optical attenuator to a proper value or replace the optical attenuator
with a proper one.
2.
If the alarm persists, check whether the attenuation of the built-in VOA in the upstream
boards is excessively high. If yes, adjust the attenuation of the VOA to a proper value.
3.
If the alarm persists, check whether related fibers or fiber connectors are dirty. If yes,
replace the fiber jumpers or check and clean the fiber connectors.
4.
If the alarm persists, the optical cables between stations may be faulty. In this case,
rectify the fault on the optical cables.
5.

1.

If ...
Then ...
modules,
Replacement.
2.

Tasks.
----End
Related Information
None.
3.48 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that the file is lost. The alarm occurs when
the SCC checks the software package and finds that a file in a partition of the SCC software
Issue 02 (2011-10-31)

357
OptiX OSN 8800/6800/3800

package is lost and the file cannot be restored from the related file in another partition. Next
time when the SCC checks the software package and finds the file, the alarm is cleared.
NOTE
The SCC checks the software package every time when it starts up and when the periodical check is performed.
The periodical check is performed every hour by default.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

Because a file in the SCC software package is lost, there may be an impact on the normal
operation of certain functions of the NE.
Fault Symptom
Table 3-46 lists the fault symptom for the SWDL_NEPKGCHECK alarm.
Table 3-46 Fault symptom for the SWDL_NEPKGCHECK alarm
Fault Symptom
Cause
The SWDL_NEPKGCHECK alarm persists.
Cause 1: The same file in two partitions in the

SCC software package of the SCC board is
lost and cannot be restored.
The SWDL_NEPKGCHECK alarm

disappears after being reported for a certain
period and is reported again.
Cause 2: A file in a partition of the SCC

software package is lost and the file cannot be
restored from the associated file in another
partition.
NOTE
Possible Causes
l
Cause 1: The same file in two partitions in the SCC software package is lost and cannot be
restored.
Cause 2: A file in a partition of the SCC software package is lost and the file cannot be
restored from the associated file in another partition.
Issue 02 (2011-10-31)

358
OptiX OSN 8800/6800/3800

Procedure
l
Causes 1 and 2: The same file in two partitions in the SCC software package is lost and
cannot be restored. A file in a partition of the SCC software package is lost and the file
cannot be restored from the associated file in another partition.
1.
Select the software package of the same version to perform a package loading on the
NMS.
2.
After successful package loading, the alarm is removed automatically. If the alarm
persists, contact Huawei engineers.
----End
Related Information
None
3.49 TD
Description
This alarm indicates that the transmitter is degraded. The TD alarm threshold of the laser is set
to a value 1.2 times of the initial value of the bias current. The TD alarm is generated when the
bias current of the laser exceeds the threshold and is smaller than the initial value by 1.5 times.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None.

Possibly the board laser cannot work normally, or the output light of the laser is of low quality
or with bit errors and further cause service break.
Fault Symptom
None.
NOTE
Issue 02 (2011-10-31)

359
OptiX OSN 8800/6800/3800

Possible Causes
Cause 1: The laser is aging.
Procedure
l
Cause 1: The laser is aging.

1.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.

1.
Tasks.
2.
----End
Related Information
In a cooling optical module that adopts the automatic level control (ALC) function, the laser is
aged after long-term operation and thus the laser emitting efficiency decreases. To ensure
constant output optical power, the laser bias current, an index that reflects the laser aging degree,
needs to be increased.
3.50 TEMP_OVER
Description
The TEMP_OVER is an alarm indicating that the working temperature crosses the threshold.
This alarm occurs, when the system detects that the board working temperature is higher than
the upper threshold or lower than the lower threshold.
Issue 02 (2011-10-31)

360
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates the upper
threshold is exceeded and 0x02 indicates the lower threshold is exceeded.

The excessively high or low temperature puts the system in a highly dangerous state. If the
system runs in this state for a long time, bit errors may be generated and services may be
interrupted. Hence, the TEMP_OVER alarm must be handled in time.
Fault Symptom
Table 3-47 lists the fault symptom for the TEMP_OVER alarm.
Table 3-47 Fault symptom for the TEMP_OVER alarm
Issue 02 (2011-10-31)
Fault Symptom
Cause
On the NMS, the adjusting mode of the fan

board is set to Adjustable Speed Mode and
the rotating speed is set to Low Speed or
Medium Speed.
Cause 1: The set rotating speed of the fan

board is excessively low.
The fan board reports the FAN_FAIL or

FAN_FAULT alarm.
Cause 2: The fan board is faulty.
The adjusting mode of the fan board is set to

Auto Speed Mode and the rotating speed is
set to High Speed. In addition, no other
alarms are generated.
Cause 3: The air filter is excessively dusty.
The fan board reports the BD_STATUS

alarm.
Cause 5: The fan is not in position.

361
OptiX OSN 8800/6800/3800

NOTE
Possible Causes
The possible causes of the TEMP_OVER alarm are as follows:
l
Cause 1: The set rotating speed of the fan board is excessively low.
Cause 3: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
Query the alarm parameter on the U2000. If the parameter is 0x01, handle the alarm
according to causes 1 to 6. If the parameter is 0x02, handle the alarm according to causes
3 and 5.
Cause 1: The set rotating speed of the fan board is excessively low.
Procedure
1.
Check the adjusting mode and rotating speed of the fan board on the NMS. If the
adjusting mode is Adjustable Speed Mode and the rotating speed is Low Speed or
Medium Speed, change the rotating speed to High Speed or the adjusting mode to
Auto Speed Mode.
2.

1.
If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is

generated on the fan board. If yes, handle the alarm in advance.
2.
Cause 3: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
1.
Check whether the ambient temperature of the equipment room is higher than 45C
or lower than 0C. If the temperature is higher than 45C or lower than 0C, use a
cooler or heater to decrease or increase the ambient temperature.
NOTE
The TEMP_OVER alarm is cleared when the board temperature is 5C lower than the upper
threshold or 5C higher than the lower threshold so that intermittent TEMP_OVER alarms can
be prevented.
2.
l
l
Issue 02 (2011-10-31)
Check whether the alarm is cleared. If the alarm persists, see Cause 5.

1.
Check whether the NE reports the BD_STATUS alarm or check whether the fan is in
position on the U2000. If the fan is not in position, place it firmly.
2.

362
OptiX OSN 8800/6800/3800

1.
l
Replace the board that reports the alarm. For details, see the Parts Replacement.

1.
If the alarm persists, check whether the air filter is excessively dusty, causing the
problem of heat dissipation. You can feel the wind and the temperature of the wind at
the air exhaust vent.
2.
If the problem is caused by dusty the air filter, remove the air filter and clean it. For
details, see Cleaning the Air Filter in the Supporting Tasks.
3.
----End
Related Information
None
3.51 TF
Description
This alarm indicates a transmission failure. This alarm is generated when the transmit optical
power of the laser exceeds the threshold of the output optical power of the laser.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The laser transmission becomes faulty, and a service interruption occurs.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the TF alarm are as follows:
Cause 1: The laser module is damaged, or the laser is aging.
Issue 02 (2011-10-31)

363
OptiX OSN 8800/6800/3800

Procedure
l
Cause 1: The laser module is damaged, or the laser is aging.

1.
If ...
Then ...
modules,
Replacement.
2.
l

Tasks.

1.
2.
If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty
board. For details, refer to "Replacing a Board" of the Supporting Tasks.
3.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after longterm operation and therefore the laser emitting efficiency decreases. To ensure constant output
optical power, the laser bias current needs to be increased. Hence, the bias current is an index
that reflects the aging degree of the laser.
Related Cases:
l
MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
MC-A12 Certain Boards Report the TF Alarm Transiently
3.52 TS_CFG_MISMATCH
Description
This alarm indicates a timeslot mistach. This alarm is generated when the configured timeslot
of one board at the local station is inconsistent with the timeslot transmitted from the opposite
station.
Issue 02 (2011-10-31)

364
OptiX OSN 8800/6800/3800

Attribute
Alarm Severity
Alarm Type
Major
Processing
Parameters
None

If a timeslot mismatch occurs, the service cannot be received properly.
Fault Symptom
None.
NOTE
Possible Causes
Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with the
received timeslot.
Procedure
l
Cause 1: The configured timeslot of the board that reports this alarm is inconsistent with
the received timeslot.
1.
Check whether the value of Timeslot Configuration Mode of the board that reports
this alarm is the same as the value of Timeslot Configuration Mode of the
corresponding board at the opposite station. If not, set them to Automatic. For details
on how to configure the service timeslots, see "Configuring Service Timeslots" in the
Configuration Guide.
2.
If the mode is consistent, check whether the timeslot configuration at the transmit end
of the opposite board is consistent with the timeslot configuration at the receive end
of the local board. If not, modify the timeslot configuration of the opposite board or
the local board according to the actual service.
3.
----End
Related Information
None.
Issue 02 (2011-10-31)

365
OptiX OSN 8800/6800/3800

3.53 WRG_BD_TYPE
Description
This alarm indicates that the type of the board is incorrect. This alarm is generated when the
logical board and the physical board are inconsistent.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The type of the logical board is different from the type of the physical board. The board cannot
work normally.
Fault Symptom
NOTE
None.
Possible Causes
The possible causes of the WRG_BD_TYPE alarm are as follows:
l
Cause 1: The type of the logical board configured on the U2000 is different from the type
of the physical board installed in the slot.
Cause 1: The type of the logical board configured on the U2000 is different from the type
of the physical board installed in the slot.
Procedure
1.
On the U2000, check whether the type of the logical board is the same as the type of
the physical board installed in the corresponding slot. If not, determine whether the
type of logical board or the type of the physical board is inappropriate according to
the engineering configuration requirements.
If the type of the logical board is inappropriate, reconfigure the logical board on
the U2000.
Issue 02 (2011-10-31)

366
OptiX OSN 8800/6800/3800

If the type of the physical board is appropriate, remove the existing board and then
insert another board of the correct type.
2.
l

1.
Tasks.
CAUTION
Exercise caution when replacing the SCC board. For details on how to replace the
SCC board and the precautions, see the Parts Replacement.
2.
----End
Related Information
None.
Issue 02 (2011-10-31)

367
OptiX OSN 8800/6800/3800

4 Alarm Processing
Alarm Processing
About This Chapter

This topic describes information relevant to alarm handling, including alarm descriptions, alarm
parameters, impacts of alarms on the system, alarm causes, and alarm handling procedures.
NOTE
By default, optical-layer alarms (OTS, OMS, and OCH alarms) are not reported. You can enable opticallayer alarm reporting as required using the NMS. For details, see "Enabling/Disabling Supervision on the
Optical Layer" in the Supporting Tasks.
NOTE
If the fault of an alarm cannot be located, contact Huawei engineers for troubleshooting.
The alarm handling involves board reset, either of cold or warm. Warm reset and cold reset have
different impacts on services.
l
Reset of the SCC board: A warm reset of the SCC is a restart of the upper-layer software,
which neither updates the FPGA or hardware data nor interrupts services. A cold reset of
the SCC may result in reconfiguration of the key hardware, such as FPGA reloading; the
upper-layer software need be restarted.
Reset of other boards: a reset of software on other boards does not affect running services
while a reset of hardware on other boards does. A mis-reset of such a board affects the
communication between this board and the SCC and even interrupts services.
The handling measures of certain alarms in this topic vary according to the boards that report
these alarms, and therefore the handling measures of these alarms are described according to the
systems (OCS and OTN systems) that the boards belong to.
4.1 AD_CHECK_FAIL
4.2 ALC_ADJUST_FAIL
4.3 ALC_WAIT_ADJUST
4.4 ALS_ACTIVE
4.5 ALM_ALS
4.6 APS_MANUAL_STOP
Issue 02 (2011-10-31)

368
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.7 ALM_GFP_dCSF
4.8 ALM_GFP_dLFD
4.9 ALM_HANGUP
4.10 ALM_TC_OEI
4.11 ALM_TC_REI
4.12 APE_ADJUST_FAIL
4.13 APE_ADJUST_PEND
4.14 APS_FAIL
4.15 APS_INDI
4.16 AU_AIS
4.17 AU_LOP
4.18 B1_SD
4.19 B2_EXC
4.20 B2_SD
4.21 B3_EXC
4.22 B3_EXC_VC3
4.23 B3_EXC_VC4
4.24 B3_SD
4.25 B3_SD_VC3
4.26 B3_SD_VC4
4.27 BD_NOT_INSTALLED
4.28 BD_STATUS
4.29 CFCARD_FAILED
4.30 BDID_ERROR
4.31 C2_VCAIS
4.32 CHAN_ADD
4.33 CHIP_ABN
4.34 CLIENT_PROT_NOTSTART
4.35 CLIENT_PORT_STA_INDI
4.36 CLK_NO_TRACE_MODE
4.37 CRC4_CROSSTR
4.38 DB_RESTORE_FAIL
Issue 02 (2011-10-31)

369
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.39 DBPS_ABNORMAL
4.40 DBMS_ABNORMAL
4.41 DBMS_ERROR
4.42 DBMS_PROTECT_MODE
4.43 DCM_INSUFF
4.44 DLAG_PROTECT_FAIL
4.45 DSP_LOAD_FAIL
4.46 ETH_CFM_LOC
4.47 ETH_CFM_MISMERGE
4.48 ETH_CFM_MACSTATUS
4.49 ETH_CFM_RDI
4.50 ETH_CFM_UNEXPERI
4.51 ETH_MISCONNECT
4.52 ETH_SERVICE_CONFIG_FAIL
4.53 ETHOAM_DISCOVER_FAIL
4.54 ETHOAM_RMT_CRIT_FAULT
4.55 ETHOAM_RMT_LOOP
4.56 ETHOAM_RMT_SD
4.57 ETHOAM_SELF_LOOP
4.58 ETHOAM_VCG_SELF_LOOP
4.59 EX_ETHOAM_MPID_CNFLCT
4.60 EXT_MODULE_OFFLINE
4.61 EXT_SYNC_LOS
4.62 EXT_TIME_LOC
4.63 FAN_FAIL
4.64 FAN_FAULT
4.65 FEATURE_WITHOUT_LICENSE
4.66 FC_8B10BERR_OVER
4.67 FCS_ERR
4.68 FEC_LOF
4.69 FEC_OOF
4.70 FLOW_OVER
4.71 FPGA_ABN
Issue 02 (2011-10-31)

370
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.72 FSELECT_STG
4.73 FWD_PKT_LOSS
4.74 GAINDATA_MIS
4.75 HARD_BAD
4.76 HARD_ERR
4.77 HP_LOM
4.78 HP_RDI
4.79 HP_REI
4.80 HP_SLM
4.81 HP_TIM
4.82 HP_UNEQ
4.83 HSC_UNAVAIL
4.84 INTRA_OTU_STA_INDI
4.85 IPA_SHUT
4.86 J0_MM
4.87 K1_K2_M
4.88 K2_M
4.89 L_SYNC
4.90 LAN_LOC
4.91 LAG_PORT_FAIL
4.92 LAG_VC_PORT_FAIL
4.93 LASER_HAZARD_WARNING
4.94 LASER_SHUT
4.95 LCS_DAYS_OF_GRACE
4.96 LCS_EXPIRED
4.97 LCS_FILE_NOT_EXIST
4.98 LCAS_FOPR
4.99 LCAS_FOPT
4.100 LCAS_PLCR
4.101 LCAS_PLCT
4.102 LCAS_TLCR
4.103 LCAS_TLCT
4.104 LOCAL_FAULT
Issue 02 (2011-10-31)

371
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.105 LOCK_CUR_FAIL
4.106 LOCKPOW_MIS
4.107 LP_RDI_VC3
4.108 LP_SLM_VC3
4.109 LP_UNEQ_VC3
4.110 LPT_RFI
4.111 LSR_COOL_ALM
4.112 LSR_FORCE_OPEN
4.113 LSR_INVALID
4.114 LTI
4.115 MAINBD_SUBBD_MISMATCH
4.116 MOD_COM_FAIL
4.117 MODULE_ADJUST_FAIL
4.118 MODULE_COOLCUR_OVER
4.119 MODULE_TEMP_OVER
4.120 MODULEFILE_UPDATE_FAIL
4.121 MS_CROSSTR
4.122 MS_REI
4.123 MS_SNCP_PS
4.124 MS_SNCP_STA_INDI
4.125 MS_APS_INDI_EX
4.126 MULTI_RPL_OWNER
4.127 NEBD_XC_DIF
4.128 NESF_LOST
4.129 NESTATE_INSTALL
4.130 NO_BD_PARA
4.131 NO_BD_SOFT
4.132 NO_ELABEL
4.133 NODEID_MM
4.134 NTP_SYNC_FAIL
4.135 NULL_SEND
4.136 OCH_FDI
4.137 OCH_FDI-O
Issue 02 (2011-10-31)

372
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.138 OCH_FDI-P
4.139 OCH_LOS-P
4.140 OCH_OCI
4.141 OCH_SSF
4.142 OCH_SSF-O
4.143 OCH_SSF-P
4.144 ODU_AIS
4.145 ODU_LCK
4.146 ODU_OCI
4.147 ODU_SNCP_STA_INDI
4.148 ODUk_LOFLOM
4.149 ODUk_PM_LCK
4.150 ODUk_PM_OCI
4.151 ODUk_PM_TIM
4.152 ODUk_TCMn_AIS
4.153 ODUk_TCMn_BDI
4.154 ODUk_TCMn_DEG
4.155 ODUk_TCMn_EXC
4.156 ODUk_TCMn_LCK
4.157 ODUk_TCMn_LTC
4.158 ODUk_TCMn_OCI
4.159 ODUk_TCMn_SSF
4.160 ODUk_TCMn_TIM
4.161 ODUKSP_PS
4.162 ODUKSP_STA_INDI
4.163 OH_LOOP
4.164 OLP_PS
4.165 OLP_STA_INDI
4.166 OMS_BDI
4.167 OMS_BDI-O
4.168 OMS_BDI-P
4.169 OMS_FDI-O
4.170 OMS_FDI-P
Issue 02 (2011-10-31)

373
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.171 OMS_LOS-P
4.172 OMS_SSF
4.173 OMS_SSF-O
4.174 OMS_SSF-P
4.175 OOL
4.176 OOS_LOST
4.177 OPA_FAIL_INDI
4.178 OPU1_MSIM
4.179 OPU1_VCAT_SQM
4.180 OPU1_VCAT_VcPLM
4.181 OPU2_MSIM
4.182 OPU3_MSIM
4.183 OPUk_PLM
4.184 OSC_BDI
4.185 OSC_DEG
4.186 OSC_RDI
4.187 OTS_BDI
4.188 OTS_BDI-O
4.189 OTS_BDI-P
4.190 OTS_LOS-O
4.191 OTS_LOS-P
4.192 OTS_TIM
4.193 OTU_AIS
4.194 OTU_LOF
4.195 OTU_LOM
4.196 OTUk_AIS
4.197 OTUk_BDI
4.198 OTUk_DEG
4.199 OTUk_EXC
4.200 OTUk_LOM
4.201 OTUk_TIM
4.202 OUT_PWR_LOW
4.203 OWSP_PS
Issue 02 (2011-10-31)

374
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.204 OWSP_STA_INDI
4.205 PATCH_ACT_TIMEOUT
4.206 PATCH_DEACT_TIMEOUT
4.207 PATCH_PKGERR
4.208 PM_BDI
4.209 PM_BEI
4.210 PM_BIP8_OVER
4.211 PM_BIP8_SD
4.212 PM_TIM
4.213 PORTSWITCH_FAIL
4.214 POWER_ABNORMAL
4.215 POWER_DIFF_OVER
4.216 PRBS_LSS
4.217 PUM_BCM_ALM
4.218 PUM_TEM_ALM
4.219 R_LOC
4.220 RELAY_ALARM_CRITICAL
4.221 RELAY_ALARM_IGNORE
4.222 RELAY_ALARM_MAJOR
4.223 RELAY_ALARM_MINOR
4.224 REM_SD
4.225 RL_CRITICAL_HI
4.226 RL_CRITICAL_LOW
4.227 RS_CROSSTR
4.228 RTC_FAIL
4.229 S1_SYN_CHANGE
4.230 SCC_LOC
4.231 SEC_RADIUS_FAIL
4.232 SERVICE_TYPE_EXCEED_LICENSE
4.233 SERVICE_CAPACITY_EXCEED_LICENSE
4.234 SHELF_AREA_POWER_OVER
4.235 SPAN_LOSS_HIGH
Issue 02 (2011-10-31)

375
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.236 SPAN_LOSS_LOW
4.237 SLAVE_WORKING
4.238 SM_BDI
4.239 SM_BEI
4.240 SM_BIP8_OVER
4.241 SM_BIP8_SD
4.242 SM_IAE
4.243 SM_TIM
4.244 SNCP_FAIL
4.245 SO_SK_MISMATCH
4.246 SPEED_OVER
4.247 STORM_CUR_QUENUM_OVER
4.248 SUBRACK_COMM_PS
4.249 SUBRACK_ID_MISMATCH
4.250 SUBRACK_LOOP
4.251 SUBRACK_TYPE_MISMATCH
4.252 SUM_INPWR_HI
4.253 SW_SNCP_PS
4.254 SW_SNCP_STA_INDI
4.255 SWDL_ACTIVATED_TIMEOUT
4.256 SWDL_AUTOMATCH_INH
4.257 SWDL_BD_EXCLUDE
4.258 SWDL_CHGMNG_NOMATCH
4.259 SWDL_COMMIT_FAIL
4.260 SWDL_INPROCESS
4.261 SWDL_PKG_NOBDSOFT
4.262 SWDL_PKGVER_MM
4.263 SWDL_ROLLBACK_FAIL
4.264 SYN_BAD
4.265 SYNC_C_LOS
4.266 SYNC_DISABLE
4.267 SYNC_F_M_SWITCH
4.268 SYNC_LOCKOFF
Issue 02 (2011-10-31)

376
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.269 SYNC_FAIL
4.270 SYSPARA_CFDB_NOSAME
4.271 T_LOSEX
4.272 T_SLIP
4.273 TEM_HA
4.274 TEM_LA
4.275 TEST_STATUS
4.276 THUNDERALM
4.277 TIME_LOS
4.278 TIME_NO_TRACE_MODE
4.279 TR_LOC
4.280 TU_AIS_VC3
4.281 TU_LOP_VC3
4.282 VCAT_LOA
4.283 VCAT_LOM_VC3
4.284 VCAT_LOM_VC4
4.285 VLAN_SNCP_PS
4.286 VOA_ADJUST_FAIL
4.287 VOADATA_MIS
4.288 W_R_FAIL
4.289 WAVE_ADD_ABN
4.290 WAVE_DROP_ABN
4.291 WAVEDATA_MIS
4.292 WAVELEN_OVER
4.293 XC_UNSWITCH
Issue 02 (2011-10-31)

377
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.1 AD_CHECK_FAIL
Description
The AD_CHECK_FAIL alarm is an alarm indicating AD (analog to digital converter) self check
failure. This alarm is reported when the AD chip on the board is faulty.
Reported from the WDM side or client side: NA.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.

l
This alarm may affect services.
Parameters relevant to the AD chip on the board, such as board input/output optical power,
back facet current and cooling current, fail to be queried on the U2000. As a result,
maintenance engineers can neither obtain the current operation performance data of the
network nor find in time any dormant problems of the network operation. The alarm may
interrupt the service in the system or even make the system down. Hence, this alarm should
be handled immediately.
Possible Causes
The board hardware is faulty.
Procedure
Step 1 Perform a cold reset on the faulty board through the U2000.
Step 2 If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty board.
For details, see the Parts Replacement.
----End
Issue 02 (2011-10-31)

378
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.2 ALC_ADJUST_FAIL
Description
ALC link adjustment failure. This alarm is generated when the ALC link adjustment fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ALC link number.
Parameter 2
Indicates the adjustment failure cause.

l 0x01: The board does not respond.
l 0x02: There is an equipment alarm.
l 0x03: Adjustment frames are received but the link is absent
from the link.
l 0x04: The link operation times out.
l 0x05: The node operation times out.
l 0x06: The node status is incorrect.
l 0x07: The node does not allow adjustment.
l 0x08: The link configuration is in disorder.
Issue 02 (2011-10-31)

379
OptiX OSN 8800/6800/3800

Name
4 Alarm Processing
Meaning
Parameter 3 and Parameter 4 l When Parameter 2 is 0x01, it indicates the no-response slot.
l When Parameter 2 is 0x02, it indicates the slot of the board
and optical interface.
l When Parameter 2 is 0x03, Parameter 3 indicates the link
number.
l When Parameter 2 is 0x04, it indicates the timeout period.
l When Parameter 2 is 0x05, it indicates the timeout period.
l When Parameter 2 is 0x06, Parameter 3 indicates the node
state.
Parameter 5 and Parameter 6 l When Parameter 2 is 0x01, it indicates the port number.
l When Parameter 2 is 0x02, it indicates the port number.
Parameter 7 and Parameter 8 When Parameter 2 is 0x01, it indicates the command.

The line attenuation is excessive and cannot be compensated by adjusting the intra-NE
attenuation or gain. In this case, the service signals may be instable and the BER may increase.
Possible Causes
l
The board does not respond to a query.
Alarms such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, and R_LOS occur on the

equipment.
The node receives adjustment frames but no link is on the node.
The link adjustment operation times out.
The node adjustment operation times out.
The node is in an incorrect node. That is, though receiving adjustment frames, the node is
not in the pre-adjustment state.
The node does not permit adjustment and there are more than two retries of adjustment.
The link configuration is in disorder.
Procedure
Step 1 Check whether the ALC configuration is normal. The configuration rules are as follows:
l The sink node cannot be configured as a reference node.
l Reference equipment must be configured for the source node.
l The detection board should not be empty for a non-reference node.
l When the detection board is OBU1, the adjustment equipment should not be empty.
l When configuring the source node, make sure that the same optical interface is not configured
for the detection equipment and reference equipment.
Step 2 Check whether the adjustment on the adjustment node is within the range.
Issue 02 (2011-10-31)

380
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 3 Check whether other alarms, such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, or R_LOS,
exist on the current equipment on the U2000. If an alarm occurs on the equipment, first rectify
the alarm.
Step 4 If the adjustment times out, re-start adjustment.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.3 ALC_WAIT_ADJUST
Description
ALC link anomaly and wait for adjustment. This alarm is generated when the ALC link in manual
mode is faulty and needs to be adjusted, this alarm is reported at the source node.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Parameter 2
Indicates the node ID of the faulty node.
Parameter 3, Parameter 4, Parameter 5, Parameter 6 Indicates the NE ID of the faulty node.

The line attenuation is excessive and may affect signal quality.
Possible Causes
l
Issue 02 (2011-10-31)
Currently, the ALC is in the manual mode. When the ALC link has anomaly and needs to
be adjusted, this alarm is reported.
381
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Manually start ALC adjustment.
Step 2 Change the current ALC to automatic adjustment mode.
----End
Related Information
4.4 ALS_ACTIVE
Description
ALS (automatic laser shutdown function) occurred alarm. When the laser is disabled based on
the ALS protocol, an ALS_ACTIVE alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the alarm is generated, the related boards laser is shut down automatically.
Possible Causes
l
The input signals on the client side is missing at the local station.
The WDM-side of the related boards is faulty.
Procedure
Step 1 On the U2000, query whether the client-side of the related boards has the R_LOS alarm. If that
is the case, handle the alarms according to the corresponding handling procedure.
Step 2 On the U2000, query whether the WDM-side of the related boards have the R_LOS, OTUk_AIS,
ODUk_TCMn_OCI or ODUk_TCMn_LCK alarms. If that is the case, handle the alarms
according to the corresponding handling procedure.
----End
Issue 02 (2011-10-31)

382
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
The OTU board and tributary board of the system provide the automatic laser shutdown (ALS)
function. For details, see "ALS" in the Feature Description.
4.5 ALM_ALS
Description
The ALM_ALS alarm in an alarm related to the automatic laser shutdown (ALS) function. When
a board enables the ALS function and the R_LOS alarm is generated at the optical interface, the
laser is shut down automatically. In this case, the board reports the ALM_ALS alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

When the ALM_ALS alarm is generated, the system is not affected. This alarm just indicates
that the ALS function of the laser is enabled.
Possible Causes
The ALS function is enabled on the U2000 or the Navigator.
Procedure
Step 1 When the ALS function is disabled, the alarm is cleared automatically.
----End
Related Information
None
4.6 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually stopped.
Issue 02 (2011-10-31)

383
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Processing alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the MSP group type.

l 0x01: linear MSP group
l 0x02: ring MSP group
Parameter 2, Parameter 3
Indicates the MSP group ID.

The MSP switching protocol of the corresponding MSP group fails to function. Accordingly,
the MSP fails.
Possible Causes
The MSP protocol of the corresponding MSP group is manually stopped.
Procedure
Step 1 View on the U2000 and confirm the MSP subnet where the protocol is stopped.
Step 2 Restart the MSP protocol of the protection group, and the alarm is cleared.
----End
Related Information
None
4.7 ALM_GFP_dCSF
Issue 02 (2011-10-31)

384
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The ALM_GFP_dCSF is an alarm indicating the loss of the GFP client signal. When the source
end cannot receive the client signal, it sends the management frame to the sink end. When the
sink end receives the management frame, this alarm is reported.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

During data transmission, the source end cannot receive the client signal. The services lose
packets or are interrupted.
Possible Causes
l
The interface module at the source end is faulty. For example, the optical module is absent
or does not match, or the optical/electrical signal is lost.
The physical link at the source end fails, and it cannot normally receive the physical signal.
Procedure
Step 1 View the ALM_GFP_dCSF alarm on the U2000, and then determine the number of the
VCTRUNK where this alarm is generated.
Step 2 Check whether the physical link at the source end of the VCTRUNK where the uplink service
is configured is normal. For example, check whether the physical link is invalid because the
fiber is damaged. If the fiber is damaged, replace the fiber and then check whether the alarm is
cleared.
Step 3 If the alarm persists, check whether the interface module at the source end is normal. If not,
replace the optical module.
Step 4 If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None
4.8 ALM_GFP_dLFD
Issue 02 (2011-10-31)

385
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The ALM_GFP_dLFD is an alarm indicating the loss of generic framing procedure (GFP) frame
delineation. If the alarm is reported when the delimitation state machine of the GFP leaves the
SYNC state of the delimitation processing; the alarm is cleared when the state is SYNC again.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

During the data transmission, failure in the GFP framing causes service interruption.
Possible Causes
l
Cause 1: There are a large number of bit errors on the link.

Identification method: Query the alarms on the U2000.
Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the
number of timeslots bound with the VCTRUUNK at the opposite station are not the same
or the number of timeslots bound with the path is not the same as the number of timeslots
configured in the cross-connection.
Identification method: Query the service configuration on the U2000.
Cause 3: The board is faulty.

Identification method: Use the exclusive method or determine based on experience.
Procedure
l
View the ALM_GFP_dLFD alarm on the U2000, and then determine the number of the
VCTRUNK where this alarm is generated. For details, see Querying the Current Alarms
Cause 1: There are a large number of bit errors on the link.

1.
Check whether any bit error alarm exists on the link.

If...
Then...
Any bit error alarm exists Handle the bit error alarms first. The bit error alarms
are as follows:
l B3_EXC
l B3_SD
Check whether the ALM_GFP_dLFD alarm is
cleared. If the alarm persists, see other causes.
Issue 02 (2011-10-31)

386
OptiX OSN 8800/6800/3800

4 Alarm Processing
If...
Then...
No bit error alarm exists
See other causes.
Cause 2: The number of timeslots bound with the VCTRUNK at the local station and the
number of timeslots bound with the VCTRUUNK at the opposite station are not the same
or the number of timeslots bound with the path is not the same as the number of timeslots
configured in the cross-connection.
1.
Check whether the number of upstream or downstream timeslots bound with the
VCTRUNK at the local station is consistent with the number of downstream or
upstream timeslots configured at the opposite station.
If ...
Then ...
The counts of timeslots are different Increase or decrease the number of bound
paths to ensure consistency of timeslots at
both stations. For details, see the
Configuration Guide. Then, check whether
the alarm is cleared. If the alarm persists,
proceed to the next step.
The counts of timeslots are the same Proceed to the next step.
2.
Select the corresponding NE from the Main Topology. Check whether the number of
timeslots bound with the path is the same as the number of timeslots configured in the
cross-connection.
If...
Then...
The counts are different Reconfigure the bound timeslots or the crossconnection. Then, check whether the alarm is cleared. If
the alarm persists, see other causes.
The counts are the same See other causes.
l

1.
Check whether the board reports the HARD_BAD alarm.

If...
Then...
The HARD_BAD alarm exists
The board is faulty. Proceed to the next

step.
The HARD_BAD alarm does not exist After eliminating other causes, proceed
to the next step if the fault persists.
2.
Replace the board. For details, see the Parts Replacement.
----End
Related Information
Cell Delimitation State Machine
Issue 02 (2011-10-31)

387
OptiX OSN 8800/6800/3800

4 Alarm Processing
The cell delimitation state machine has three states: HUNT, PRESYNC, and SYNC. In the
HUNT state, the state machine searches the position of delimiting cells in the BYTE BY BYTE
manner. After finding a correct HCS, the state machine changes to the PRESYNC state. In the
PRESYNC state, the state machines locks the position of delimiting cells. After consecutively
receiving DELTA correct HCS cells, the state machine changes to the SYNC state. In this case,
the cell boundary is found. In the PRESYNC state, after receiving an incorrect HCS cell, the
state machine returns to the HUNT state. In the SYNC state, after consecutively receiving
ALPHA incorrect HCS cells, the state machine changes to the HUNT state. Otherwise, it keeps
in the SYNC state, as shown in the following figure.
4.9 ALM_HANGUP
Description
The ALM_HANGUP is an alarm indicating that the orderwire phone is in the off-hook state for
a long time. This alarm is generated when the orderwire phone is in the off-hook state for a long
time.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

388
OptiX OSN 8800/6800/3800

4 Alarm Processing

l
The ALM_HANGUP alarm does not affect the services or communication of the NE.
The ALM_HANGUP alarm indicates that the orderwire phone of the NE is in the off-hook
state for a long time. When the alarm is generated, hang up.
Possible Causes
l
The orderwire phone is in the off-hook state for a long time.
The hardware is faulty.
Procedure
Step 1 Check whether the orderwire phone is hung up. If not, hang up the phone. Then, check whether
the ALM_HANGUP alarm is cleared.
Step 2 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the faulty
----End
Related Information
None
4.10 ALM_TC_OEI
Description
The ALM_TC_OEI alarm is an output error indication in the tandem connection. When the
accumulated number of output errors received at the sink of the tandem connection within one
second is greater than 0, the ALM_TC_OEI alarm is reported.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

When the ALM_TC_OEI alarm is generated, the services at the local station are not affected.
This alarm just indicates that some bit errors occur in the signals output from the sink of the
tandem connection.
Issue 02 (2011-10-31)

389
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
Some bit errors occur in the signals output from the sink of the tandem connection.
Procedure
Step 1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC,
B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to
clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted
firmly. Then check whether the ALM_TC_OEI alarm at the local station is cleared.
Step 2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a
cold reset on the relevant line board, and then check whether the alarm is cleared.
CAUTION
If the services that travel through the board are not configured with protection, the services are
interrupted after the cold reset of the board.
Step 3 If the alarm persists, replace the relevant line board at the source, and then check whether the
alarm is cleared.
Step 4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold
reset on the board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
Step 5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check
Step 6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded.
In this case, ask the relevant carrier for solution.
----End
Related Information
None
4.11 ALM_TC_REI
Description
The ALM_TC_REI alarm is a remote error indication in the tandem connection. When the
accumulated number of remote bit errors in the tandem connection received at the sink within
one second is greater than 0, the ALM_TC_REI alarm is reported.
Issue 02 (2011-10-31)

390
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

When the ALM_TC_REI alarm is generated, the services at the local station are not affected.
This alarm just indicates that bit errors occur in the monitored tandem connection section.
Consequently, the transmission service quality is degraded.
Possible Causes
Bit errors occur in the monitored tandem connection section.
Procedure
Step 1 Check whether any higher-level bit error alarm, such as the B1_EXC, B2_EXC, B3_EXC,
B1_SD, B2_SD, or B3_SD alarm, is detected at the source and the sink. If yes, take priority to
clear it. Moreover, clean the fiber connector, and make sure that the fiber connector is inserted
firmly. Then, check whether the TC_REI alarm at the local station is cleared.
Step 2 If the alarm persists, check whether the transmit board at the source is faulty. If yes, perform a
cold reset on the relevant board, and then check whether the alarm is cleared.
CAUTION
Step 3 If the alarm persists, replace the relevant line board at the source, and then check whether the
alarm is cleared.
Step 4 If the alarm persists, check whether the receive board at the sink is faulty. If yes, perform a cold
reset on the line board that reports the alarm, and then check whether the alarm is cleared.
CAUTION
Step 5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check
Issue 02 (2011-10-31)

391
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded.
In this case, ask the relevant carrier for solution.
----End
Related Information
None
4.12 APE_ADJUST_FAIL
Description
APE adjustment failure. This alarm is generated when the APE adjustment fails.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the index of APE.

OSNR of receive signal degrades.
Possible Causes
l
The communication fails.
The board is offline.
An error is responded from a board.
The equilibrium cannot be reached after adjustment.
The board type error.
The VMUX attenuation adjusting fails.
The adjustment is stopped by the user.
Issue 02 (2011-10-31)

392
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check the cause of OSNR degrade and handle the alarm accordingly.
----End
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.13 APE_ADJUST_PEND
Description
APE adjustment is pending for operation.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

SNR of receive signal degrade.
Possible Causes
APE detect the powers of channels are unequal, then APE adjustment is pending for operation.
Procedure
Step 1 Manually start APE adjustment.
----End
Issue 02 (2011-10-31)

393
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
4.14 APS_FAIL
Description
The APS_FAIL is an alarm indicating the APS protection switching failure. This alarm is
generated when the MSP switching fails.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of the MSP group in which protection switching occurs.
Parameter 2 Indicates the MSP group ID.

When the APS_FAIL alarm is generated, the MSP switching fails. For a linear MSP or a twofiber ring MSP, if a fiber cut or another fault occurs at this time, the services are interrupted.
Possible Causes
The possible causes of the APS_FAIL alarm are as follows:
l
The MSP configuration parameters are incorrect.
The MSP configuration is lost.
The board that reports the alarm is faulty.
Issue 02 (2011-10-31)

394
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Make sure that the networkwide MSP configuration is correct. For a ring MSP, check the fiber
connections in the east and west directions. For a linear MSP, check the working and protection
fiber connections, or check the MSP switching modes at the two ends. After modifying the
incorrect configuration, check whether the alarm is cleared.
Step 2 Make sure that the networkwide APS protocol works properly. Stop the protocol, and then restart
it to check whether the alarm is cleared.
Step 3 If the alarm persists, the board that reports the alarm may be faulty. Replace the board. For
details, refer to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
4.15 APS_INDI
Description
The APS_INDI is an alarm indicating the APS state. This alarm is generated when the MSP is
in the switching state.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of the MSP group in which protection switching

occurs.
Parameter 2, Parameter 3 Indicates the MSP group ID.
Issue 02 (2011-10-31)

395
OptiX OSN 8800/6800/3800

4 Alarm Processing

l
The APS_INDI alarm indicates the occurrence of a fiber cut or a terminal node failure,
which triggers the MSP switching.
For a two-fiber ring MSP or a linear MSP, if a fiber cut or another fault occurs after the
occurrence of this alarm, the services are interrupted.
Possible Causes
The possible causes of the APS_INDI alarm are as follows:
l
An external command, including manual switching, forced switching, and exercise

switching, is issued.
After the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm is generated, the MSP
group changes to the switching state.
The service board is faulty.
The cross-connect board is faulty.
Procedure
Step 1 View the APS_INDI alarm on the U2000, and then confirm the type and ID of the protection
group in which this alarm is generated.
Step 2 Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked
switching. If yes, clear the switching and then observe whether the alarm is cleared.
Step 3 To check whether the MSP is in the automatic switching state, do as follows:
1.
Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm reported by the
equipment. When these alarms are cleared, wait for the MSP switching to be automatically
restored to the normal state, and then check whether the APS_INDI alarm is cleared.
2.
Make sure that the service board of the MSP is not faulty. Replace the relevant service
board and then check whether the alarm is cleared.
3.
Make sure that the cross-connect board of the MSP is not faulty. Replace the relevant crossconnect board and then check whether the alarm is cleared.
----End
Related Information
For the 1+1 single-ended non-revertive linear MSP, the APS_INDI alarm is generated when the
protection switching occurs. When the optical path recovers to normal, the service is not
automatically switched back to the working path, and the APS_INDI alarm persists. In this case,
manually switch the service from the protection path to the working path. After successful
manual switching, the APS_INDI alarm is cleared.
4.16 AU_AIS
Description
The AU_AIS is an administrative unit (AU) alarm indication. When the pointer value received
on the receive side of the local optical port is all "1"s, the AU_AIS alarm is reported.
Issue 02 (2011-10-31)

396
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

l
When the AU_AIS alarm is reported, the VC-4 level services are interrupted if the network
is not protected.
In this case, the AU-AIS alarm is reported at the downstream station.
Possible Causes
The possible causes of the AU_AIS alarm are as follows:
l
Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm
Identification method: Query the alarms and the loopback on the U2000.
Board cause 1: The receive board (including the cross-connect and timing board) at the
local end is faulty.
Identification method: Use the exclusive method.
Board cause 2: The transmit board (including the cross-connect and timing board) at the
opposite end is faulty.
Procedure
l
Query current alarms on the U2000. Determine the number of the interface that reports the
alarm according to Parameter 1. For details, see Querying the Current Alarms in the
Supporting Task.
Cause of inserting alarm by the upstream station: The upstream station inserts the AIS alarm
1.
Check whether any higher-level alarm exists at the upstream station.

If...
Then...
The alarms listed in Table 4-1 exist
Handle these alarms first. If the AU_AIS

The alarms listed in Table 4-1 do not Proceed to the next step.
exist
2.
Issue 02 (2011-10-31)
Perform a loopback at the upstream station to locate the station that reports the
AU_AIS alarm originally. Perform an inloop at the receive and transmit ports at the
opposite board. See the Supporting Task.
397
OptiX OSN 8800/6800/3800

4 Alarm Processing
CAUTION
The loopback may cause the service interruption.
3.
Check whether the AU_AIS alarm exists at the opposite station after the loopback is
performed.
If ...
Then ...
The alarm exists
The AU_AIS alarm of the local station is transmitted

from the opposite station. Proceed to the next step.
The alarm does not exist See board cause 1.

4.
Perform the loopback again to locate the station where the AU_AIS alarm is reported
originally at the opposite upstream station. Check whether any higher-level alarm
exists on board at the service source end corresponding to the station.
If ...
Then ...
The alarms listed in Table 4-1 exist
Handle these alarms first. If the AU_AIS

alarm is not cleared, see board cause 1.
The alarms listed in Table 4-1 do not See board cause 2.

exist
l
Board cause 1: The receive board (including the cross-connect and timing board) of the
local end is faulty.
1.
Replace the receive board of the local station. For details, see Parts Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, replace the local crossconnect and timing board. For details, see Parts Replacement.
3.
Board cause 2: The transmit board (including the cross-connect and timing board) of the
opposite end is faulty.
1.
Replace the corresponding transmit board of the station where the AU_AIS alarm is
originally reported. For details, see Parts Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
and timing board. For details, see Parts Replacement.
3.
----End
Related Information
Table 4-1 Alarms that may cause the AU_AIS alarm
Issue 02 (2011-10-31)
R_LOS
R_LOF
R_OOF
MS_AIS
B1_EXC
B1_SD

398
OptiX OSN 8800/6800/3800

4 Alarm Processing
B2_EXC
B2_SD
AU_LOP
B3_EXC
B3_SD
HP_TIM
HP_LOM
HP_SLM
HP_UNEQ
4.17 AU_LOP
Description
The AU_LOP is an alarm indicating loss of the AU pointer. When the NDF or invalid pointer
values are received in eight consecutively frames on the receive side of the local optical port,
the AU_LOP alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

l
When the AU_LOP alarm is reported, the VC-4 level services are interrupted if the network
is not protected.
When the AU_LOP alarm is reported, the system returns the G1 byte to the opposite end,
indicating the HP_RDI alarm. Consequently, the opposite station reports the HP_RDI
alarm.
Possible Causes
The possible causes of the AU_LOP alarm are as follows:
l
Cause 1: Excessive receive bit errors are available at the local station.
Identification method: Query the alarms of bit errors on the U2000.
Cause 2: The level of the service transmitted by the opposite station is inconsistent with
that of the service to be received at the local station.
Identification method: Query the service configuration on the U2000.
Cause 3: The board (including the cross-connect and timing board) of the local end is faulty.
Cause 4: The board (including the cross-connect and timing board) of the opposite end is
faulty.
Issue 02 (2011-10-31)

399
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
Supporting Task.
Cause 1: Excessive bit errors are available at the local station.

1.
Check whether any bit error alarms exist at the local end. Clear these alarms first.
B1_EXC
B1_SD
B2_EXC
B2_SD
2.
l
Check whether the AU_LOP alarm is cleared. If the alarm persists, see other causes.
Cause 2: The level of the service transmitted by the opposite station is inconsistent with
the level of the service to be received at the local station.
1.
Check whether the level of the service transmitted by the opposite station is consistent
with the level of the service to be received by the local station.
If...
Then...
The service levels are different Reconfigure the service levels at the two ends.
Then, check whether the alarm is cleared. If the
alarm persists, see other causes.
The service levels are the same See other causes.
l
Cause 3: The board (including the cross-connect and timing board) of the local end is faulty.
1.
Replace the receive board of the local station. For details, see Parts Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, perform cold reset on the
cross-connect board at the local station by using the U2000, or reseat the cross-connect
board at the local station. For the operations that are performed on the U2000, see
Performing a Cold Reset of a Board in the Supporting Task. For the operations of
reseating a board, see the Installation Guide.
CAUTION
If no protection cross-connect board works normally, do not perform the operations,
because all the services may be interrupted.
3.
l
Issue 02 (2011-10-31)
Check whether the alarm is cleared. If the alarm persists, replace the local crossconnect and timing board. For details, see Parts Replacement.
Cause 4: The transmit board (including the cross-connect and timing board) of the opposite
end is faulty.
1.
Replace the faulty transmit board at the opposite station. For details, see Parts
Replacement.
2.
Check whether the alarm is cleared. If the alarm persists, perform cold reset on the
cross-connect board at the opposite end, or reseat the cross-connect board at the
opposite end. For the operations that are performed by the U2000, see Performing a
400
OptiX OSN 8800/6800/3800

4 Alarm Processing
Cold Reset of a Board in the Supporting Task. For the operations of reseating a board,
see the Installation Guide.
CAUTION
If no protection cross-connect board is available, the cold reset on the cross-connect
and clock board may interrupt the entire service.
3.
Check whether the alarm is cleared. If the alarm persists, replace the opposite crossconnect and timing board. For details, see Parts Replacement.
----End
Related Information
The concatenation levels of the services involve AU3, VC4, VC4-4c, VC4-8c, VC4-16c, and
VC4-64c.
NOTE
If the AU_LOP alarm is reported when the equipment runs on the existing network, you need to contact
the technical support engineers of Huawei and report the alarm even though you have cleared it by adopting
the preceding methods.
4.18 B1_SD
Board Type
Alarm Page Link

4.18.1 B1_SD (OCS)

SLO16, or EGSH
4.18.2 B1_SD (OTN)
4.18.1 B1_SD (OCS)

Description
The B1_SD (OCS) is an alarm indicating that regenerator section B1 signals received on the
line are degraded. When a line board detects that the bit errors of the regenerator section signals
exceed the B1_SD alarm threshold but are lower than the B1_EXC alarm threshold, the B1_SD
alarm is reported.
Issue 02 (2011-10-31)

401
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the B1_SD alarm is reported, the quality of the transmitted services is degraded.
Possible Causes
The possible causes of the B1_SD alarm are as follows:
l
Supporting Task.
Procedure
1.
Task.
NOTE
2.
Issue 02 (2011-10-31)
If...
Then...


abnormal,
See cause 4.

402
OptiX OSN 8800/6800/3800

4 Alarm Processing
If...
Then...


3.
If...
Then...

Cleaners
Tissue
Sticks

4.
5.
Issue 02 (2011-10-31)
If...
Then ...

improper,


proper,

403
OptiX OSN 8800/6800/3800

4 Alarm Processing
1.
temperature.
2.

1.
Task.
CAUTION
If...
Then...
step.
See cause 4.
2.
Replacement.
3.

1.
Replacement.
----End
Related Information
None.
4.18.2 B1_SD (OTN)

Description
The B1_SD(OTN) alarm is an alarm indicating that the regenerator section signals are degraded.
The alarm occurs when the received signals in SDH frame degrade and the B1 bit errors in the
multiplex section exceed the signal degrade (SD) threshold.
l
The alarm is generated on the WDM side when the B1 bit errors in the SDH signals received
on the WDM side exceed the signal degrade threshold.
The alarm is generated on the client side when the B1 bit errors in the SDH signals received
on the client side exceed the signal degrade threshold.
Issue 02 (2011-10-31)

404
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The B1 bit errors in the service signals received by the board exceed the degrade threshold of
signals set on the board. The generation of the alarm has an impact on the QoS of the service
signals.
Possible Causes
l
The attenuation of the received signals is overlarge; the fiber or connector is dirty.
The transmit part of the opposite station is faulty.
The receive part of the local station is faulty.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using
the U2000. For optical power specifications of specific boards, see the Product Description. If
the receive optical power of the board at the local station is excessively low, clear the alarm
according to the handling procedure of the IN_PWR_LOW alarm.
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For the optical power
specifications of specific boards, see the Product Description. If the transmit optical power of
the board at the upstream station is excessively low, clear the alarm according to the handling
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station by using
the U2000 and loop back the transmit optical port and receive optical port on the WDM side of
the OTU board at the upstream station. If bit errors exist, clear the bit error fault of the upstream
station.
Step 4 If the alarm persists and the faulty board supports the pluggable optical module, replace the
pluggable optical module. For details, see the Parts Replacement.
Step 5 If the alarm persists, replace the faulty board at the local station. For details, see the Parts
Replacement.
Step 6 If the alarm bursts, it may be caused by the transmission line influenced by various noise sources.
Search the jam source that may cause the burst bit errors and remove the interference.
----End
Related Information
None
Issue 02 (2011-10-31)

405
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.19 B2_EXC
Description
The B2_EXC is an alarm indicating that the number of multiplex section B2 bit errors in the
signals received on the line exceed the specified value. When a line board detects that the bit
errors of the multiplex section signals exceed the threshold for the B2_EXC alarm by detecting
the B2 byte, the B2_EXC alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

l
When the B2_EXC alarm is generated, the quality of the transmitted services is degraded.
When the B2_EXC alarm is reported, the system returns the M1 byte to the opposite end,
indicating the MS_REI alarm. Consequently, the opposite station reports the MS_REI
alarm.
Possible Causes
l
Supporting Task.
Procedure
1.
Issue 02 (2011-10-31)
Task.
406
OptiX OSN 8800/6800/3800

4 Alarm Processing
NOTE
2.
If...
Then...


abnormal,
See cause 4.

If...
Then...


3.
If...
Then...

Cleaners
Tissue
Sticks

4.
Issue 02 (2011-10-31)

407
OptiX OSN 8800/6800/3800

5.
4 Alarm Processing
If...
Then ...

improper,


proper,

1.
temperature.
2.

1.
Task.
CAUTION
If...
Then...
step.
See cause 4.
2.
Replacement.
3.

1.
Replacement.
----End
Issue 02 (2011-10-31)

408
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None.
4.20 B2_SD
Description
The B2_SD is an alarm indicating that multiplex section B2 signals received on the line are
degraded. When a line board detects that the bit errors of the multiplex section signals exceed
the B2_SD alarm threshold but are lower than the B2_EXC alarm threshold, the B2_SD alarm
is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

l
When the B2_SD alarm is reported, the quality of the transmitted services is degraded.
When the B2_SD alarm is reported, the system may return the M1 byte to the opposite end,
indicating the MS_REI alarm. Consequently, the remote station may report the MS_REI
alarm.
Possible Causes
l
Supporting Task.
Procedure
1.
Issue 02 (2011-10-31)
409
OptiX OSN 8800/6800/3800

4 Alarm Processing
Task.
NOTE
2.
If...
Then...


abnormal,
See cause 4.

If...
Then...


3.
If...
Then...

Cleaners
Tissue
Sticks

4.
Issue 02 (2011-10-31)

410
OptiX OSN 8800/6800/3800

5.
4 Alarm Processing
If...
Then ...

improper,


proper,

1.
temperature.
2.
Cause 3: The setting of the bit error threshold is improper.

1.
Query the bit error threshold of the board that reports the alarm. According to the
situation, increase the B2 error threshold. For operations, see the Supporting Task.
2.

1.
Task.
CAUTION
If...
Then...
step.
Issue 02 (2011-10-31)
See cause 4.
2.
Replacement.
3.
411
OptiX OSN 8800/6800/3800

4 Alarm Processing

1.
Replacement.
----End
Related Information
None.
4.21 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of higher order path B3 bit errors in the
signals received on the line exceeds the threshold. When a line board detects that the bit errors
of the higher order path signals exceed the specified threshold by detecting the B3 byte, the
B3_EXC alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

l
When the B3_EXC alarm is reported, bit errors occur in the path-level services.
When the B3_EXC alarm is reported, the system returns the G1 byte to the opposite end,
indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm.
If the AU_AIS alarm is inserted when the B3_EXC alarm is reported, the system returns
the G1 byte to the opposite end, indicating the HP_RDI alarm. Consequently, the remote
station generates the HP_RDI alarm.
Possible Causes
l
Issue 02 (2011-10-31)

412
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
alarm. For details, see Querying the Current Alarms in the Supporting Task.

1.
Task.
NOTE
2.
If...
Then...


abnormal,
See cause 4.

If...
Then...


3.
If...
Then...

Cleaners
Tissue
Sticks
Issue 02 (2011-10-31)

413
OptiX OSN 8800/6800/3800

4.
5.
4 Alarm Processing
If...
Then ...

improper,


proper,

1.
temperature.
2.

1.
Task.
CAUTION
If...
Then...
step.
l
Issue 02 (2011-10-31)
See cause 4.
2.
Replacement.
3.

414
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
Replacement.
----End
Related Information
None.
4.22 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of B3 bit errors in the lower order
path VC-3 exceeds the threshold. If a board has detected that the number of B3 bit errors exceeds
the specified threshold value, the B3_EXC_VC3 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the B3_EXC_VC3 alarm is generated, a great number of bit errors occur in the VC-3
service.
Possible Causes
The possible causes of the B3_EXC_VC3 alarm are as follows:
l
A higher-level bit error alarm is generated in the system.
The received signals are heavily attenuated.
The fiber connector is dirty.
The fiber connector is loose.
The transmit unit at the opposite station is faulty.
The receive unit at the local station is faulty.
Issue 02 (2011-10-31)

415
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD, is detected at the local station or at the upstream station. If yes, take priority
to clear it, and then check whether the B3_EXC_VC3 alarm is cleared.
Step 2 If the alarm persists, check whether the receive optical power of the board that reports the alarm
is within the normal range.
l
If yes, go to Step 3.
If not, take the following steps:
1.
Insert the fiber connector firmly, and then check whether the alarm is cleared.
2.
Check whether the attenuation value specified in the fiber attenuator is proper. If not, adjust
it to a proper value, and then check whether the alarm is cleared.
3.
Clean the fiber connector at the local station and the receive optical interface on the line
board, and then check whether the alarm is cleared.
4.
Check whether the flange is correctly connected to the optical attenuator at the local station,
and whether the attenuation value specified in the optical attenuator is proper. After making
sure that the flange and optical attenuator are used properly, check whether the alarm is
cleared.
5.
Check whether the transmit optical power at the opposite station is within the normal range.
6.
If the transmit optical power is beyond the specified range, replace the optical module, and
then check whether the alarm is cleared. If not, replace the line board at the opposite end,
and then check whether the alarm is cleared.
7.
If the transmit optical power is within the normal range, clean the fiber connector at the
remote station, and then check whether the alarm is cleared.
8.
Check whether the flange is correctly connected to the optical attenuator at the opposite
station, and whether the attenuation value specified in the optical attenuator is proper. After
making sure that the flange and optical attenuator are used properly, check whether the
alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the B3_EXC_VC3 alarm.
----End
Related Information
None
4.23 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that the number of B3 bit errors in the VC-4 path
exceeds the threshold. If a board has detected that the number of B3 bit errors in the VC-4 path
exceeds the specified threshold value, the B3_EXC_VC4 alarm is reported.
Issue 02 (2011-10-31)

416
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the B3_EXC_VC4 alarm occurs, bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_EXC_VC4 alarm may be the same as those of the B3_EXC alarm.
Procedure
Step 1 See the procedure for handling the B3_EXC alarm.
----End
4.24 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path B3 signals received on the line are
degraded. When a line board detects that the bit errors of the higher order path signals exceed
the specified B3_SD alarm threshold but are lower than the specified B3_EXC alarm threshold
by detecting the B3 byte, the B3_SD alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

l
When the B3_SD alarm is reported, bit errors occur in the path-level services.
When the B3_SD alarm is reported, the system returns the G1 byte to the opposite end,
indicating the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm.
If the AU_AIS alarm is inserted when the B3_SD alarm is reported, the system returns the
Issue 02 (2011-10-31)

417
OptiX OSN 8800/6800/3800

4 Alarm Processing
G1 byte to the opposite station, indicating the HP_RDI alarm. Consequently, the opposite
station generates the HP_RDI alarm.
Possible Causes
l
Supporting Task.
Procedure
1.
Task.
NOTE
2.
If...
Then...


abnormal,
See cause 4.

If...
Then...


3.
Issue 02 (2011-10-31)

418
OptiX OSN 8800/6800/3800

4 Alarm Processing
If...
Then...

Cleaners
Tissue
Sticks

4.
5.
If...
Then ...

improper,


proper,

1.
temperature.
2.

1.
Issue 02 (2011-10-31)
Task.

419
OptiX OSN 8800/6800/3800

4 Alarm Processing
CAUTION
If...
Then...
step.
See cause 4.
2.
Replacement.
3.

1.
Replacement.
----End
Related Information
None.
4.25 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of VC-3 B3 bit errors exceeds the
threshold. If a board has detected that the number of VC-3 B3 bit errors exceeds the specified
B3_SD alarm threshold value, the B3_SD_VC3 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the B3_SD_VC3 alarm is generated, the service transmission quality in the VC-3 service
channel is degraded.
Issue 02 (2011-10-31)

420
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The possible causes of the B3_SD_VC3 alarm are as follows:
l
Higher-level bit alarms occur in the system.
The fiber connector is loose.
The receive unit at the opposite station is faulty.
The transmit unit at the local station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,
B3_EXC, or B3_SD alarm, is detected at the local station or at the upstream station. If yes, take
priority to clear it, and then check whether the B3_SD_VC3 alarm is cleared.
Step 2 If the alarm persists, check whether the receive optical power of the board that report the alarm
is within the normal range.
l
If yes, go to Step 3.
If not, take the following steps:
1.
Insert the fiber connector firmly, and then check whether the alarm is cleared.
2.
Check whether the attenuation value specified in the fiber attenuator is proper. If not, adjust
it to a proper value, and then check whether the alarm is cleared.
3.
Clean the fiber connector at the local station and the receive optical interface on the line
board, and then check whether the alarm is cleared.
4.
Check whether the flange is correctly connected to the optical attenuator at the local station,
and whether the attenuation value specified in the optical attenuator is proper. After making
sure that the flange and optical attenuator are used properly, check whether the alarm is
cleared.
5.
Check whether the transmit optical power at the opposite station is within the normal range.
6.
If the transmit optical power is beyond the specified range, replace the optical module, and
then check whether the alarm is cleared. If not, replace the line board at the opposite end,
7.
If the transmit optical power is within the normal range, clean the fiber connector at the
opposite station, and then check whether the alarm is cleared.
8.
Check whether the flange is correctly connected to the optical attenuator at the opposite
station, and whether the attenuation value specified in the optical attenuator is proper. After
making sure that the flange and optical attenuator are used properly, check whether the
alarm is cleared.
Step 3 If the alarm persists, replace the board that generates the B3_SD_VC3 alarm.
----End
Related Information
None
Issue 02 (2011-10-31)

421
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.26 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of B3 bit errors in the VC-4 path exceeds
the threshold. If a board has detected that the number of B3 bit errors in the VC-4 path exceeds
the specified threshold value, the B3_SD_VC4 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the B3_SD_VC4 alarm is generated, bit errors occur in the path-level services.
Possible Causes
The possible causes of the B3_SD_VC4 alarm may be the same as those of the B3_SD alarm.
Procedure
Step 1 See the procedure for handling the B3_SD alarm.
----End
4.27 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED alarm is an alarm indicating that the logical board is not created
in the corresponding slot. This alarm occurs when a physical board is installed but no logical
board is created on the U2000.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Issue 02 (2011-10-31)

422
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
table.
Name
Meaning
Parameter 1
Indicates the ID of the slot where the alarm is generated.

When the BD_NOT_INSTALLED alarm occurs, the corresponding slot cannot be configured
with services. This alarm, however, does not affect the operation of the system.
Possible Causes
The logic board is not created.
Procedure
Step 1 On the U2000, add a logic board that corresponds to the slot that reports the alarm.
----End
Related Information
None
4.28 BD_STATUS
Board Type
Alarm Page Link

4.28.1 BD_STATUS (OCS)

SLO16, or EGSH
4.28.2 BD_STATUS (OTN)
4.28.1 BD_STATUS (OCS)

Issue 02 (2011-10-31)

423
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The BD_STATUS (OCS) is an alarm indicating that the physical board is offline. This alarm is
reported when the logical board is created on the U2000 but the physical board is not inserted
in the subrack.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Because the physical board is not inserted in the equipment, the data that is configured on the
NE cannot be delivered to this board. Hence, configuration of services fails.
Possible Causes
The possible causes of the BD_STATUS alarm are as follows:
l
Cause 1: The board is in the cold reset or warm reset state.
Cause 2: The board is not inserted in the corresponding slot or the board does not contact
the mother board firmly.
Cause 3: The pins of the mother board are bent or the board is faulty.
Query current alarms on the U2000. Then find the boards that report the alarm. For details,
see Querying the Current Alarms in the Supporting Task.
Cause 1: The board status is cold reset or warm reset.
Procedure
Issue 02 (2011-10-31)
1.
Check the board alarm indicator to see whether the status of the board that reports the
alarm is cold reset or warm reset. Wait for five minutes if the board is in the cold reset
or warm reset state, and then check whether the alarm is cleared. For the description
of the alarm indicators on the board, see Board Indicators in the Hardware
Description.
2.
Cause 2: The board is not inserted in the corresponding slot or the contact part of the board
with the mother board is loose.
1.
Check whether the board is inserted in the corresponding slot. If not, insert the
corresponding physical board. For details, see the Installation Guide.
2.
Check whether the board is connected to the backplane properly and whether the board
is connected properly. If the board is loose, reseat the board. For operations, see the
Installation Guide. Then, check whether the alarm is cleared.
3.

424
OptiX OSN 8800/6800/3800

4 Alarm Processing
Cause 3: The pins of the mother board are bent or the board is faulty.
1.
Remove the board that reports the alarm. For details, see the Installation Guide. Check
whether any pins of the mother board are bent. If any bins are bent, contact Huawei
engineers for fixing the pins. After the pins are fixed, insert the board. For details, see
the Installation Guide. Then, check whether the alarm is cleared.
2.
If the alarm persists, replace the board that reports the alarm. For details, see the Parts
3.
----End
Related Information
None.
4.28.2 BD_STATUS (OTN)

Description
The BD_STATUS is an alarm indicating that the board is out of position. This alarm is reported
when the logical board is created on the U2000 but the physical board is not inserted in the slot.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The board is not in position. Hence, the functions related to the board are unavailable.
Possible Causes
l
The AUX board is faulty.
The logic board is configured but the physical board has not been inserted in the proper
slot.
The connection between the plug of the board and the socket of the backplane is loose.
The board is faulty.
The backplane is faulty.
Issue 02 (2011-10-31)

425
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 If the alarm is reported on the AUX board and all service boards but services are normal and the
SCC board operates normally, it indicates that the AUX board is faulty. Perform a warm reset
or cold reset on the faulty board through the U2000. If the alarm persists, replace the AUX board.
Step 2 Check whether the corresponding board is inserted in the physical slot.
l
If no corresponding board is inserted, insert the board.
If the corresponding board is inserted, check whether the insertion is firm. If not, reset the
board.
Step 3 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
Step 4 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei
engineers.
----End
Related Information
None
4.29 CFCARD_FAILED
Description
CF Card Failed.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the CFCARD_FAILED alarm occurs, the system is not affected. The alarm indicates that
the operations related to the CF card fail.
Possible Causes
The CF card is faulty and needs to be replaced.
Issue 02 (2011-10-31)

426
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Replace the CF card and then check whether the CFCARD_FAILED alarm is cleared. If the
alarm persists, replace the SCC board. For details, see the Parts Replacement.
----End
Related Information
None
4.30 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating slot verification error. This alarm is generated when
the board parity check fails or when the board is not properly secured in its slot.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

l
When the BDID_ERROR alarm is generated, the board may fail to get online and as a result
the services are interrupted.
In this case, you cannot configure and monitor the services for the board.
Possible Causes
The possible causes of the BDID_ERROR alarm are as follows:
l
The board is not properly secured in the slot.
The board hardware fails.
Pins on the backplane are bent.
Procedure
Step 1 View the BDID_ERROR alarm on the U2000 to determine the relevant board.
Step 2 Remove the board to check whether there are any bent pins on the backplane. If any pins are
bent, fix them and then insert the board. Check whether the alarm is cleared.
Issue 02 (2011-10-31)

427
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 3 If the alarm persists, replace the board.

----End
Related Information
None
4.31 C2_VCAIS
Description
The C2_VCAIS is a C2 byte alarm indication. If a board has detected that the value of the
received C2 byte is all "1"s, the C2_VCAIS alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The services are interrupted.
Possible Causes
The value of the C2 byte to be transmitted is incorrectly configured at the remote end.
Procedure
Step 1 View the C2_VCAIS alarm on the U2000. Determine the VC path that reports the alarm.
Step 2 Check whether the value of the C2 byte to be transmitted is correctly configured at the remote
end. If not, modify it, and then check whether the C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board at the remote end. For details, see the Parts
Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

428
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.32 CHAN_ADD
Description
The CHAN_ADD is an alarm indicating that wavelengths are added to a single-wavelength
signal. The alarm occurs when the MCA (optical spectrum analyzing) board detects that new
wavelengths are added after it scans the optical spectrum.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The MCA cannot monitor the optical spectrum performance of the wavelength related to the
alarm.
Possible Causes
l
The configuration for wavelength monitoring is incorrect. The accessed wavelength is not
set as the monitored wavelength.
The MCA board is faulty.
Procedure
Step 1 Check whether the configuration for wavelength monitoring of the MCA board is incorrect by
using the U2000. If the configuration is incorrect, modify the configuration to ensure that the
monitored wavelength and the number of the monitored wavelengths are consistent with the
accessed wavelength and the number of accessed wavelengths.
Step 2 If the alarm persists, test the optical spectrum data of the input optical signals by using the optical
spectrum analyzer. If the data is normal, the optical spectrum analyzing module may be faulty.
Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

429
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.33 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating temperature chip failure. This alarm is generated when
the temperature chip fails.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

When the CHIP_ABN alarm is generated, the board temperature cannot be correctly detected.
Possible Causes
The temperature chip on the board fails.
Procedure
Step 1 Check whether the equipment has another cross-connect board that is functioning properly. If
yes, perform cold reset on the board that reports the CHIP_ABN alarm. After successful cold
reset, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.34 CLIENT_PROT_NOTSTART
Description
The CLIENT_PROT_NOTSTART is an alarm indicating that the client-side 1+1 protection
group is not started. This alarm occurs when the client-side 1+1 protection group is disabled
because the configurations on the both sides of the active and standby channels of the protection
group do not meet the requirements of enabling the protection group.
Issue 02 (2011-10-31)

430
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The client-side 1+1 protection group does not perform the switching in case of a service fault.
In this case, the protection fails.
Possible Causes
l
The active or standby channel is configured with an incorrect electrical-layer crossconnection.
The active or standby channel is not configured with complete electrical-layer services
between WDM-side ports and client-side ports.
The active or standby channel is configured with an EVPL link that converges at a clientside optical interface.
Procedure
Step 1 Query on the U2000 whether the active or standby channel is configured with an incorrect
electrical-layer cross-connection such as a cross-connection with an IP port as the source and
another IP port as the sink. If yes, delete the incorrect electrical-layer cross-connection.
Step 2 If the alarm persists, check the OTU that can be configured with electrical-layer crossconnections. If the active or standby channel of this OTU is not configured with complete
electrical-layer services between WDM-side ports and client-side ports, configure the complete
electrical-layer services.
Step 3 If the alarm persists, check whether the active or standby channel is configured with an EVPL
link that converges in the downlink. If yes, change this EVPL link to an EPL link or an EVPL
link that broadcasts in the downstream.
----End
Related Information
4.35 CLIENT_PORT_STA_INDI
Description
The CLIENT_PORT_STA_INDI alarm indicates the state of the client side 1+1 optical channel
protection group. This alarm is reported when the working or protection channel of the protection
group is faulty or the user runs an external switching command.
Issue 02 (2011-10-31)

431
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1
Indicate the switch request status. For example:

l 0x0F: Lockout
l 0x0E: Forced Switch
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x07: Manual Switch
l 0x05: WTR

l
When switching of the client 1+1 protection group occurs, services are transiently
interrupted.
When this alarm is reported, the working channel or the protection channel of the client 1
+1 protection group might have faulty services that need to be restored.
Possible Causes
l
Cause 1: A user issues an external switching command such as forced switching, manual
switching or locked switching.
Cause 2: The services of the working channel or the protection channel of the client 1+1
protection group are faulty.
Cause 3: The switching is in WTR state. After WTR Times (s), the alarm clears.
Procedure
1.
Issue 02 (2011-10-31)
is forced switching, manual switching or locked switching, check whether the external
switching operation is necessary.
432
OptiX OSN 8800/6800/3800

4 Alarm Processing
2.
3.
If the external switching operation is unnecessary, issue a command to clear the

external switching.
Cause 2: The services of the working channel or protection channel of the client 1+1
protection group are faulty.
1.
Query whether the boards that are configured with the working channel or protection
channel of the protection group have the alarms, such as R_LOF, R_LOS, R_LOC,
HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS, OTUk_TIM,
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_TIM,
REM_SF, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC or REM_SD. If
yes, handle the alarms by referring to the corresponding alarm handling procedures.
2.
Revertive or not. If the attribute is Revertive, the working channel of the current
service automatically switches to the working channel and then the alarm clears. If
the attribute is Non-Revertive, set it to Revertive and the alarm clears.
1.
There is no need to handle this alarm. After WTR Times (s), the alarm clears.
----End
Related Information
4.36 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE is an alarm indicating that the clock enters the non-tracing
mode. This alarm is generated when the current clock does not trace any line clock source,
tributary clock source, or external clock source.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

When the CLK_NO_TRACE_MODE alarm is generated, the clock is in the non-tracing mode.
In this case, the system clock is of a low quality. When the low quality clock results in the outof-synchronization status among NEs, the bit error rate of services increases.
Issue 02 (2011-10-31)

433
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows:
l
Cause 1: A priority table is not manually set for the system, and NEs use their own default
priority tables.
Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
Cause 1: A priority table is not manually set for the system, and NEs use their own default
priority tables.
Procedure
1.
Query the current priority table of the system. If there is only the internal clock source
in the priority table, set the clock source priority table to include other available clock
sources. After the setting, the alarm is automatically cleared. For details, see
Configuring the System Clock Source Priority Table in the Feature Description.
Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
1.
In the current priority table, if the internal clock source is not the only available source,
find out why other clock sources cannot be traced. Common causes are as follows:
The existence status of the clock source is lost. In this case, the system generates
the SYNC_C_LOS alarm. After the SYNC_C_LOS alarm is cleared, the system
clock traces any clock source other than the internal clock source, and then check
whether the CLK_NO_TRACE_MODE alarm is cleared.
The synchronous source is degraded. In this case, the system generates the
SYN_BAD alarm. After the SYN_BAD alarm is cleared, the system clock traces
any clock source other than the internal clock source, and then check whether the
CLK_NO_TRACE_MODE alarm is cleared.
The local station enables the SSM protocol, while the upstream station does not
enable the SSM protocol. In this case, enable the SSM protocol at the upstream
station. When the system clock traces any clock source other than the internal clock
source, the CLK_NO_TRACE_MODE alarm is automatically cleared. For details,
see Configuring the Clock Source Protection in the Feature Description.
----End
Related Information
For details, see "Physical Clocks" in the Feature Description.
4.37 CRC4_CROSSTR
Description
The CRC4_CROSSTR is an alarm indicating that the count of CRC4 multi-frame errors crosses
the threshold. The alarm occurs when the number of the bit errors in the CRC4 multiframe
Issue 02 (2011-10-31)

434
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The alarm has an influence on the services (supervisory channel such as the orderwire signal).
Possible Causes
l
The configuration of the system clock is incorrect.
The attenuation of the transmission line is overlarge.
The receive optical power is overloaded.
Procedure
Step 1 Check the clock configuration of the system on the U2000 to ensure that the configuration is
correct. For details, see the Configuration Guide.
Step 2 Check whether the input optical power of the interface of the board at the local station is within
the normal range by using the U2000. For optical power specifications of the specific boards,
see the Product Description. If the optical power is abnormal, take the processing methods of
alarms such as IN_PWR_HIGH or IN_PWR_LOW for troubleshooting.
Step 3 If the services are not influenced, check whether the fiber jumper between the FIU board and
the SC2/SC1/ST2 board is extruded. If the fiber jumper is extruded, clean up the routed fiber
jumper. If the fiber jumper is transformed due to the extrusion, replace the fiber jumper.
----End
Related Information
None
4.38 DB_RESTORE_FAIL
Description
The DB_RESTORE_FAIL is an alarm indicating a database restore failure. This alarm occurs
when the database recovery fails.
Issue 02 (2011-10-31)

435
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Process Alarm
Parameters
table.
Parameter
Description
Parameters 1
0x01, indicating that the OCP database fails to recover

The configured data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l
The database configuration file is lost.
Data in the database is damaged.
Procedure
Step 1 Back up the database regularly at a fixed time to solve this problem. Check and test the database
in the backup area to ensure that the data in database is complete.
----End
Related Information
None
4.39 DBPS_ABNORMAL
Description
The alarm indicates that the DBPS protection group is abnormal. When the DBPS protection
group detects anomalies, the DBPS_ABNORMAL alarm is reported.
Issue 02 (2011-10-31)

436
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.
Parameter 3
The anomaly of the DBPS protection group is classified into the following
three types:
l 0x1 indicates that timeout occurs during the communication between
the active equipment and standby equipment;
l 0x2 indicates that the protection configuration of the active and
standby equipment is incorrect;
l 0x3 indicates that the snooping protocol is abnormal.

The following exceptions may result in service disruption.
l
If the protocol communication between the active equipment and the standby equipment
in the DBPS protection group cannot be established, there may be two pieces of active
equipment or standby equipment.
If the DBPS protection status of the active equipment and standby equipment is
inconsistent, the service protection cannot function properly.
If the snooping protocol used (VRRP or ARP) detects anomalies, the snooping function
cannot be realized, and therefore the protection status of the active equipment and the
protection status of the standby equipment are incorrect.
Possible Causes
l
The protocol communication between the active equipment and the standby equipment is
interrupted. In this case, communication between the protocol interfaces cannot be
established, or the protection configuration on the active equipment and the protection
configuration on the standby equipment are inconsistent.
The VLAN configuration of the active equipment and the VLAN configuration of the
standby equipment are inconsistent, or the active equipment and standby equipment use
different snooping protocols.
In the case of the VRRP protocol, the configuration of the DBPS protection group may be
inconsistent with the configuration of the VRRP group of the interconnected routers or the
Issue 02 (2011-10-31)

437
OptiX OSN 8800/6800/3800

4 Alarm Processing
VRRP groups of the routers interconnected to the active and standby DBPS may be
different.
Procedure
Step 1 Query alarms on the U2000 to determine the ID of the protection group where the alarms are
generated.
Step 2 Check whether the protocol interface of the DBPS protection group is configured properly and
the IDs of the protection groups on the active and standby equipment are consistent. If there are
errors in the configuration, modify the configuration of the protection group.
Step 3 Check whether the VLAN configuration and the snooping protocol on DBPS protection group
are consistent. If not, modify the protection configuration.
Step 4 If the VRRP protocol is used, check whether the configuration of the DBPS protection group is
consistent with the configuration of the VRRP protection in the two interconnected routers. Note
that the DBPS protection group must correspond to the VRRP group. In addition, the VRRP
groups of the routers interconnected to the active and standby DBPS equipment must be
consistent. Otherwise, eliminate the incorrect VRRP configuration of the router, and then reconfigure the DBPS protection group.
----End
Related Information
For details, see "DBPS Protection" in the Feature Description.
4.40 DBMS_ABNORMAL
Description
The alarm indicates that the database state is abnormal. When an exception occurs during the
running of the database, a DBMS_ABNORMAL alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 02 (2011-10-31)

438
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
Parameter
Description
Parameter 1
Indicates the alarm cause.

0x01 indicates that nvram device is bad.
0x02 indicates that there is no enough flash space.
0x03 indicates that submitting transactions times out.
0x04 indicates that the database is deleted without restarting the system.

Service configurations may be lost.
Possible Causes
l
Cause 1: The nvram device is damaged, the flash memory is insufficient, or submitting
transactions times out.
Cause 2: The database is deleted.
Cause 1: The nvram device is damaged, the flash memory is insufficient, or submitting
transactions times out.
Procedure
1.
Check whether configurations are changed after the alarm is reported.
2.
If configurations are changed, manually back up services and reset the board. If no
configurations are changed, reset the board directly.
3.
If the alarm persists, replace the board.
Cause 2: The database is deleted.

1.
Reset the NE.
2.
----End
Related Information
None
4.41 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating a database error. The alarm occurs when the database
is in error
Issue 02 (2011-10-31)

439
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Parameter 1 Indicates the alarm type. The value is the error code that causes the
DBMS_ERROR alarm.
Parameter 2 Indicates the memory areas in the database:
0x00 indicates FDB0.
0x01 indicates FDB1.
0x02 indicates DRDB.
Parameter 3 Indicates the ID of the database that has errors. Currently, the value can only be
0-255 (0x00-0xFF).
0x00 indicates that the entire storage area mistakes in error.
0x01-0xff indicates that the database is in error.

The configured data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l
Operation to database fails.
Data in the database is damaged.
Procedure
Step 1 Solve the problem by periodically backing up the database. Check and test the database in the
backup area to ensure that the data in database is complete.
----End
Issue 02 (2011-10-31)

440
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.42 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the database is in the protection
mode. The alarm occurs when the NE database is in the protection mode.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

In the protection mode, the NE database cannot be backed up.
Possible Causes
l
The reset times of the SCC in five minutes cross the threshold value of the protection mode.
The SCC issues a command to test the protection mode.
Procedure
Step 1 Check whether the NE database in the protection mode is caused by human factors. If that is the
case,
l
Perform warm or cold reset on the SCC through the U2000. Release the protection mode.
For details, see the Supporting Tasks.
Wait for 15 minutes. Release the protection mode after the automatic reset.
----End
Related Information
None
Issue 02 (2011-10-31)

441
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.43 DCM_INSUFF
Description
The DCM_INSUFF is an alarm indicating the insufficient dispersion compensation margin. The
alarm is generated when the dispersion compensation value gets close to the limit of the
dispersion compensation margin
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Parameter 1 The value is always 0xff.
Parameter 2 Indicates the positive or negative dispersion compensation margin. The value
0x00 indicates the positive dispersion compensation margin, and the value 0x01
indicates the negative dispersion compensation margin.

The alarm does not affect the existing services. The alarm indicates that the system cannot meet
the higher dispersion compensation requirements.
Possible Causes
The configuration of the DCM module is not correct or the DCM module is faulty.
Procedure
Step 1 Check whether there is the OTUk_LOF alarm on the U2000. If there is the OTUk_LOF alarm,
clear the alarm according to the proper procedure.
Step 2 If there are no other alarms, query the dispersion compensation value of the board on the
U2000.
Issue 02 (2011-10-31)

442
OptiX OSN 8800/6800/3800

4 Alarm Processing
If the dispersion compensation value is large and close to the upper limit of the dispersion
compensation margin, replace the DCM module with a DCM module with lower dispersion
compensation capabilities.
If the dispersion compensation value is small and close to the lower limit of the dispersion
compensation margin, replace the DCM module with a DCM module with higher dispersion
compensation capabilities.
----End
Related Information
None
4.44 DLAG_PROTECT_FAIL
Description
The DLAG_PROTECT_FAIL is an alarm indicating that the DLAG protection fails. If
negotiation fails or any anomaly occurs during the DLAG protection, the
DLAG_PROTECT_FAIL alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
table.
Name
Meaning
Parameters 1 and 2 Indicates the ID of the aggregation group.
Issue 02 (2011-10-31)

443
OptiX OSN 8800/6800/3800

4 Alarm Processing
Name
Meaning
Parameter 3
Indicates the cause of the DLAG protection failure.

l 0x01: Both the active and the standby links fail.
l 0x02: The active and standby ports fail to receive the LACP packets.
l 0x03: The opposite equipment does not enter the LACP
synchronization status.
l 0x04: The active or standby port detects the self-loop. Alternatively,
the active or standby port may form a loop with other ports on the
board.
l 0x05: The communication between the active and standby boards
times out.
l 0x06: The communication between the board and the cross-connect
board times out.
l 0x07: The active port selected by LACP is inconsistent with the one
selected by cross-connect board.

When all the DLAG ports fail, or when the board fails to normally communicate with other
boards, the DLAG_PROTECT_FAIL alarm is reported. In the case of the
DLAG_PROTECT_FAIL alarm, services cannot be received or transmitted in the LAG, or the
user cannot check whether services are in the normal state.
Possible Causes
The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:
l
Both the active and standby links fail.
The active and standby ports fail to receive the LACP packets.
The opposite equipment does not enter the LACP synchronization status.
The active or standby port detects the self-loop. Alternatively, the active or standby port
may form a loop with other ports on the board.
The communication between the active and standby boards times out.
The communication between the board and the cross-connect board or SCC board times
out.
The active port selected by LACP is inconsistent with the one selected by cross-connect
board.
Procedure
Step 1 View the DLAG_PROTECT_FAIL alarm on the U2000, and determine the board where the
DLAG_PROTECT_FAIL alarm is generated. Determine the ID of the LAG where the
DLAG_PROTECT_FAIL alarm is generated according to Parameters 1 and 2, and determine
the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 3.
Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
Issue 02 (2011-10-31)

444
OptiX OSN 8800/6800/3800

4 Alarm Processing
1.
On the U2000, check whether the port in the LAG is enabled. If not, enable the port and
then check whether the DLAG_PROTECT_FAIL alarm is cleared.
2.
If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports. Rectify
the fault of the port link, and then check whether the DLAG_PROTECT_FAIL alarm is
cleared.
Step 3 If the value of Parameter 3 is 0x02, it indicates that the port fails to receive the LACP packets.
1.
On the U2000, check whether the LAG is configured at the opposite end, and check whether
the port connected to the faulty port is added to the LAG at the opposite end. Make sure
that the LAG is correctly configured, and then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
2.
If the DLAG_PROTECT_FAIL alarm persists, check whether the local port transmits
packets. If both ends can normally transmit and receive packets, check whether the
DLAG_PROTECT_FAIL alarm is cleared.
Step 4 If the value of Parameter 3 is 0x03, it indicates that the opposite equipment fails to enter the
LACP protocol synchronization status. Check the connection of the port, and LAG configuration
at the opposite equipment, and then check whether the DLAG_PROTECT_FAIL alarm is
cleared.
Step 5 If the value of Parameter 3 is 0x04, it indicates the port is in the self-loop state. Release the loop
and then check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 6 If the value of Parameter 3 is 0x05, it indicates that the communication between the active and
standby boards times out. Make sure the active and standby boards are in position, and the
communication between them is normal. Then check whether the DLAG_PROTECT_FAIL
alarm is cleared.
Step 7 If the value of Parameter 3 is 0x06, it indicates that the communication between the board and
the cross-connect board and SCC board times out. Make sure that the software of the crossconnect board and the SCC is normal. If the board normally communicates with the crossconnect board or SCC board, check whether the DLAG_PROTECT_FAIL alarm is cleared.
Step 8 If the value of Parameter 3 is 0x07, it indicates that the active port selected by LACP is
inconsistent with the one selected by cross-connect board. Make sure that the active port selected
by LACP is consistent with the one selected by cross-connect board, and then check whether
the DLAG_PROTECT_FAIL alarm is cleared.
----End
Related Information
None
4.45 DSP_LOAD_FAIL
Description
The DSP_LOAD_FAIL is an alarm indicating DSP software loading failure. The alarm occurs
when loading the DSP program fails.
Issue 02 (2011-10-31)

445
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
None

Loading the DSP program to the board fails. As a result, the board cannot work normally, which
has an influence on the services of users.
Possible Causes
Procedure
Step 1 Perform warm reset on the faulty board through the U2000. For details, see the Supporting
Tasks.
----End
Related Information
None
4.46 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating service connectivity loss. This alarm is generated
when the continuity check message (CCM) packets transmitted by the maintenance end point
(MEP) of the opposite end are not received within 3.5 times of the continuity check (CC) period.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
Issue 02 (2011-10-31)

446
OptiX OSN 8800/6800/3800

4 Alarm Processing

table.
Parameter
Description
Parameters 1 to 4
Indicates the Ethernet port.
Parameters 5 and 6
Indicates the VLAN ID.
Parameter 7
Indicates the direction of the maintenance point.
Parameter 8
Parameters 9 and 10 Indicates the ID of the remote maintenance point. The remote
maintenance point ID is the ID of the CC source maintenance point.

Possible Causes
Cause 1: There is a failure in the service connectivity.
Procedure
l
Cause 1: There is a failure in the service connectivity.

1.
Check whether the related alarms, such as LINK_ERR, are reported. If the related
alarms are reported, clear the alarms first.
2.
If the ETH_CFM_LOC alarm persists, check whether the attributes and crossconnection status of the service are correctly configured on the U2000. If any error is
found, modify the configuration.
----End
Related Information
None
4.47 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating a misconnection. This alarm indicates that
there are misconnections between different maintenance domains (MDs).
Issue 02 (2011-10-31)

447
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Environment alarm
Parameters
table.
Parameter
Description
Parameters 1 to 4
Indicates the Ethernet port.
Parameters 5 and 6
Parameter 7
Parameter 8
Indicates the level of the MD.

The CFM_OAM fails to test the service connectivity. The alarm does not affect services.
Possible Causes
l
Cause 1: The level of the MD to which the maintenance end point (MEP) belongs is
incorrectly configured.
Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
Cause 3: Certain physical links are incorrectly connected.
Cause 1: The level of the MD to which the MEP belongs is incorrectly configured.
Procedure
1.
Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
1.
l
Issue 02 (2011-10-31)
Check whether the level of the maintenance point on the service is correctly
configured. If the level is incorrectly configured, change the level so that the level is
correct.
If the alarm persists, check whether the MD/MA names configured at the source and
sink ends are consistent. If not, modify them to the same, and then check whether the
alarm is cleared.
Cause 3: Certain physical links are incorrectly connected.

448
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
If the alarm persists, check whether physical links are misconnected. If yes, reconnect
the fiber or line, and then check whether the alarm is cleared.
----End
Related Information
None
4.48 ETH_CFM_MACSTATUS
Description
The ETH_CFM_MACSTATUS is a remote MAC defect indication. This alarm indicates that a
continuity check packet carrying a port tlv or an interface tlv is received from a given remote
MEP.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
Parameter
Description
Parameters 1 to 4
Indicates the Ethernet port ID.
Parameters 5 and 6
Parameter 7
Parameter 8
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).

The MAC status of remote mep's port is linkdown or discard.
Issue 02 (2011-10-31)

449
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
Cause 1: The port status of remote mep occur defection.
Procedure
l
Cause 1: The port status of remote mep occur defection.

1.
Check whether the port of remote mep is linkdown or discarding. Rectify the fault.
----End
Related Information
None
4.49 ETH_CFM_RDI
Description
The ETH_CFM_RDI is a remote CFM_OAM alarm indication. This alarm is generated at the
local end when the CFM_OAM fault is generated at the remote end. This alarm indicates that
at least one continuity check message (CCM) packet with the RDI indication is received.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Parameter
Description
Parameters 1 to 4
Parameters 5 and 6
Parameter 7
Parameter 8
Issue 02 (2011-10-31)

450
OptiX OSN 8800/6800/3800

Parameter
4 Alarm Processing
Description
maintenance point ID is the ID of the source maintenance point of the
continuity check (CC).

When the ETH_CFM_RDI alarm is generated, the services on the transmit side of the local
equipment may be interrupted.
Possible Causes
Cause 1: The opposite equipment detects a fault.
Procedure
l
Cause 1: The opposite equipment detects a fault.

1.
Check whether ETH alarms exist on the opposite equipment, and then rectify the fault
according to the alarms.
----End
Related Information
None
4.50 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating error frames. This alarm indicates that there
are error continuity check message (CCM) packets in the same maintenance association (MA).
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Issue 02 (2011-10-31)

451
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameters 1 to 4
Parameters 5 and 6
Parameter 7
Parameter 8

The CFM_OAM fails to test the service connectivity. The alarm does not affect services.
Possible Causes
l
Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong
are inconsistent.
Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong
are the same or illegal MEP ID is used.
Cause 3: There are service loops in the MDs to which the MEPs of the service belong.
Cause 1: The periods of the MDs to which the MEPs of the stations of the service belong
are inconsistent.
Procedure
1.
Cause 2: The MEP IDs in the MDs to which the MEPs of the stations of the service belong
are the same or illegal MEP IDs are used.
1.
Check whether the CCM periods that are configured on the equipment at the stations
of the service are consistent. If the CCM periods are inconsistent, change the
configuration so that the CCM periods are consistent.
If the alarm persists, check whether the same MEP IDs are used in the MD to which
the MEPs of the stations of the service belong. If the same MEP IDs are used, delete
the repeated MEP ID and create another MEP ID so that no MEP ID conflict exists
in the MD.
Cause 3: There are service loops in the MDs to which the MEPs of the service belong.
1.
If the alarm persists, check whether there are service loops in the MDs to which the
MEPs of the service belong. If there are service loops, release the service loops.
----End
Related Information
None
Issue 02 (2011-10-31)

452
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.51 ETH_MISCONNECT
Description
ETH_MISCONNECT is an alarm indicating an incorrect connection between network
interfaces. This alarm indicates that the LAN cable for connecting subracks is incorrectly
connected.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1
Indicates the network interface number.

None
Possible Causes
l
Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is connected
to a subrack.
Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is connected
to a subrack.
Procedure
1.
Check whether the ETH3 interface is connected to a subrack. If the ETH3 interface
is connected to a subrack, modify the network condition and disconnect the ETH3
interface from the subrack.
----End
Related Information
None.
Issue 02 (2011-10-31)

453
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.52 ETH_SERVICE_CONFIG_FAIL
Description
Ethernet service configuration failure alarm.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 Indicates the service ID. A link conflicting with DBPS is invisible to users
and the value of this parameter for such a link is 0xff 0xff (invalid).
Parameters 3 and 4 Indicates the in port CVLAN ID. 0xff 0xff: No in port CVLAN is
available.
Parameters 5 and 6 Indicates the in port SVLAN ID. 0xff 0xff: No in port SVLAN is
available.
Parameter 7
Indicates the protection type. 0x00: LAG. 0x0a: DBPS. 0xff: No

protection is available.
Parameter 8
Indicates the protection group ID. 0xff: No protection group is available.

The Ethernet service for which the alarm is reported fails to be created and other services are
not affected.
Possible Causes
Cause 1: The Ethernet service fails to be configured due to resource conflict.
Issue 02 (2011-10-31)

454
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
Cause 1: The Ethernet service fails to be configured due to resource conflict.

1.
On the U2000, view the alarm parameters. If the value of parameter 7 is 0xff, determine
the service ID based on parameters 1 and 2 and delete the service mapping. Then create
the service again by using another VLAN or port.
2.
If the value of parameter 7 is 0x00 (LAG), determine the service ID based on alarm
parameters 1 and 2 and delete the service mapping the service ID, or determine the
protection group ID based on alarm parameter 8 and delete the LAG protection group
mapping the protection group ID. Then create the service again by using another port
or VLAN.
3.
If the value of parameter 7 is 0x01 (DBPS), determine the protection group ID based
on alarm parameter 8 and delete the southbound port of the DBPS protection group
or delete the DBPS protection group. Then, create the southbound port of the DBPS
protection group by using another port.
----End
Related Information
None.
4.53 ETHOAM_DISCOVER_FAIL
Description
The ETHOAM_DISCOVER_FAIL is an alarm indicating the point-to-point Ethernet OAM
discovery failure. When the OAM protocol is enabled at the port of a board and the negotiation
with the opposite equipment fails, this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

455
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter 1 Indicates the reason why the negotiation fails.
l 0x01: A link fault occurs at the local end.
l 0x02: The local end fails to transmit the OAM message.
l 0x03: The local end fails to receive the OAM message.
l 0x04: The OAM configurations of the opposite end do not meet the
requirements of the local end.
l 0x05: The OAM configurations of the local end do not meet the requirements
of the opposite end.

The ETHOAM_DISCOVER_FAIL alarm is generated when the system runs the IEEE 802.3ah
OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services.
Possible Causes
l
A link fault occurs at the local end.
The local end fails to transmit the OAM message.
The local end fails to receive the OAM message in a specified time.
The OAM configurations of the opposite end do not meet the requirements of the local end.
The OAM configurations of the local end do not meet the requirements of the opposite end.
Procedure
Step 1 View the ETHOAM_DISCOVER_FAIL alarm on the U2000 and determine the possible causes
of the alarm according to Parameter 1.
Step 2 When Parameter 1 is 0x01, it indicates that a link fault occurs at the local end. Query the boardlevel alarms on the U2000. Then remove the fault according to the specific link alarms such as
LINK_ERR and L_SYNC.
Step 3 When Parameter 1 is 0x02, it indicates that the local end fails to transmit the OAM message.
View the printed information about the serial port. The DSSP, drive, and microcode components
are involved in the problem. The fault location needs the assistance of engineers on related
project teams.
Step 4 When Parameter 1 is 0x03, it indicates that the local end fails to receive the 3ahOAM message
from the opposite end in a user-defined time.
1.
Check whether the MAC addresses of the interconnected ports are the same. If yes, set
different MAC addresses for the interconnected ports. Then check whether the alarm is
cleared.
2.
Check whether the 3ahOAM protocol is enabled at the opposite end. If not, enable the
protocol at the opposite end. Then check whether the alarm is cleared.
3.
If the alarm persists, the local end fails to receive the OAM message. Replace the board.
For details, see the Parts Replacement.
Step 5 When Parameter 1 is 0x04, it indicates that the OAM configurations of the opposite end,
including link event reporting capability and unidirectional operation capability, do not meet the
Issue 02 (2011-10-31)

456
OptiX OSN 8800/6800/3800

4 Alarm Processing
requirements of the local end. Query and modify the configurations of the opposite port on the
U2000. When the configurations meet the requirements of the local end, the alarm is
automatically cleared.
Step 6 When Parameter 1 is 0x05, it indicates that the OAM configurations of the local end do not meet
the requirements of the opposite end. Query and modify the configurations of the local port on
the U2000. When the configurations meet the requirements of the opposite end, the alarm is
----End
Related Information
None
4.54 ETHOAM_RMT_CRIT_FAULT
Description
The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs on the
remote end of point-to-point Ethernet OAM. When the port with the OAM protocol enabled
receives the OAM message that contains critical fault information from the opposite end, this
alarm is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the type of the fault.

l 0x01: A link fault occurs at the opposite port.
l 0x02: Irrecoverable problems such as a power failure occur at the opposite
end.
l 0x03-0xFF: Other unknown faults occur.

The ETHOAM_RMT_CRIT_FAULT alarm is generated when the system runs the IEEE
802.3ah OAM protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to
Issue 02 (2011-10-31)

457
OptiX OSN 8800/6800/3800

4 Alarm Processing
services. This alarm indicates that the signal loss alarm is generated at the receive end of the
opposite port.
Possible Causes
The port with the OAM protocol enabled receives the OAM message that contains critical fault
information from the opposite end, such as a link fault or power failure.
Procedure
Step 1 If a link fault occurs at the opposite port, query board-level alarms on the U2000. Remove the
fault according to the specific link alarms such as L_SYNC and LINK_ERR. Check whether
Step 2 If irrecoverable problems such as a power failure occur at the opposite end, remove the fault.
The alarm is automatically cleared.
Step 3 If other unknown faults occur, contact Huawei engineers.
----End
Related Information
None
4.55 ETHOAM_RMT_LOOP
Description
The ETHOAM_RMT_LOOP is an alarm indicating the remote loopback of the point-to-point
Ethernet OAM. This alarm only occurs at the port with the point-to-point OAM protocol enabled.
If the port is able to respond to loopback, it enters the loopback response state and reports the
loopback response alarm after it receives the remote loopback enabling command sent by the
opposite OAM port. The loopback initiation end reports the loopback initiation alarm. If the port
receives the loopback disabling command, it exits the loopback response state and ends the
loopback response alarm. The loopback initiation end also ends the loopback initiation alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

458
OptiX OSN 8800/6800/3800

4 Alarm Processing
Name
Meaning
Parameter 1
l 0x01: The loopback is initiated.

l 0x02: The loopback is responded.

The ETHOAM_RMT_LOOP alarm is generated when the system runs the IEEE 802.3ah OAM
protocol. When this alarm is generated, it indicates that the services are looped back from the
loopback initiation end to the loopback response end. The services and other packets are all
interrupted.
Possible Causes
l
A command is issued to enable the loopback at the local port, and the opposite end is the
loopback response end.
A command is issued to enable the loopback at the opposite port, and the local end is the
loopback response end.
Procedure
Step 1 Disable the loopback. The ETHOAM_RMT_LOOP alarm is automatically cleared.
----End
Related Information
None
4.56 ETHOAM_RMT_SD
Description
The ETHOAM_RMT_SD is an alarm indicating the remote SD of the point-to-point Ethernet
OAM. When the port with the OAM protocol enabled receives the link event message from the
opposite end which indicates that the remote Ethernet performance is degraded, this alarm
occurs.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
Issue 02 (2011-10-31)

459
OptiX OSN 8800/6800/3800

4 Alarm Processing
table.
Name
Meaning
Parameter 1
Indicates the type of the received link event:

l 0x01: error frame event
l 0x02: error frame period event
l 0x03: error frame second event

The ETHOAM_RMT_SD alarm is generated when the system runs the IEEE 802.3ah OAM
protocol. IEEE 802.3ah OAM is a link management protocol and is irrelevant to services. When
this alarm is generated, it indicates that the alarm indicating that the error frame crosses the
threshold occurs at the receive end of the local port. The service performance degrades.
Possible Causes
The port with the OAM protocol enabled receives the link event message from the opposite end.
Procedure
Step 1 Improve the link performance at the opposite end until the opposite end does not send link event
message to the local end, and therefore the ETHOAM_RMT_SD alarm at the local end is
Step 2 Modify the value of the link performance monitoring threshold at the opposite end. Then the
ETHOAM_RMT_SD alarm at the local end is automatically cleared.
Step 3 Disable the link event reporting at the opposite end. Then the ETHOAM_RMT_SD alarm at the
local end is automatically cleared.
----End
Related Information
None
4.57 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating loopback of the MAC port that receives the
OAM protocol packets in a point-to-point manner. If the MAC port of a board receives the OAM
protocol packets sent by itself or the board after detection of the loop is enabled, the
ETHOAM_SELF_LOOP alarm is reported.
Issue 02 (2011-10-31)

460
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1

l 0x01: self-loop of the port
l 0x02: self-loop of the board
l 0x03-0xff: other reasons

In the case of the ETHOAM_SELF_LOOP alarm, the port is in the self-loop state. The U2000
provides a function of automatically shutting down the port in the case of the
ETHOAM_SELF_LOOP alarm. If the user enables this function in advance, services of this
port are interrupted. Otherwise, a broadcast storm may occur.
Possible Causes
l
Self-loop is performed for the port with a fiber.
Loopback is set among ports of the board.
The PHY/MAC loopback of the port is manually set.
Procedure
Step 1 Check whether the transmit and receive ends of the port are connected with a fiber. If yes, connect
the fiber correctly, and then check whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 2 If the ETHOAM_SELF_LOOP alarm persists, check whether the transmit and receive ends of
the port are connected to those of other ports with fibers. If yes, connect the fibers correctly, and
then check whether the ETHOAM_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_SELF_LOOP alarm persists, check whether any PHY/MAC-layer loopback
is set for the port. If yes, release the loopback, or wait for five minutes when the U2000
automatically releases the loopback. Then check whether the ETHOAM_SELF_LOOP alarm is
cleared.
----End
Issue 02 (2011-10-31)

461
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.58 ETHOAM_VCG_SELF_LOOP
Description
The ETHOAM_VCG_SELF_LOOP is an alarm indicating the loopback of the VCTRUNK port
that receives the OAM protocol packets in a point-to-point manner. If the VCTRUNK port of a
board receives the OAM protocol packets sent by itself or the board after detection of the loop
is enabled, the ETHOAM_VCG_SELF_LOOP alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
Name
Meaning
Parameters 1 and 2
Indicate the VCG port number.
Parameter 3

l 0x01: The link of the VCG port is configured with a self-loop.
l 0x02: The link between VCG ports is configured with a loop.
l 0x03-0xff: There are other reasons.

In the case of the ETHOAM_VCG_SELF_LOOP alarm, the link of the VCG port is configured
with a self-loop. The U2000 provides a function of automatically shutting down the port in the
case of the ETHOAM_VCG_SELF_LOOP alarm. If the user enables this function in advance,
services of this port are interrupted. If the user does not enable this function, a broadcast storm
may occur.
Possible Causes
l
The links of the VCG port is configured with a self-loop.
The links between VCG ports of the board is configured with a loop.
Issue 02 (2011-10-31)

462
OptiX OSN 8800/6800/3800

4 Alarm Processing
The port is configured with a loopback at the PHY/MAC layer manually.
Procedure
Step 1 Check the ETHOAM_VCG_SELF_LOOP alarm on the U2000, and determine the VCG port
number according to Parameters 1 and 2.
Step 2 Check the link configuration of the VCG port to see whether the transmit and receive directions
of the port are connected. Make sure the link configuration is correct, and then check if the
ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 3 If the ETHOAM_VCG_SELF_LOOP alarm persists, check the link configuration of the VCG
port to see whether this VCG port is connected to another VCG port on the board in the transmit
and receive directions. Make sure that the link configuration is correct. Then, the
ETHOAM_VCG_SELF_LOOP alarm is cleared.
Step 4 If the alarm persists, check whether the port is configured with a loopback at the PHY/MAC
layer. If the loopback exists, release it manually.
----End
Related Information
None
4.59 EX_ETHOAM_MPID_CNFLCT
Description
The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the maintenance point (MP) ID
conflict. When an MP receives the message sent by another MP with the same MP ID in a
maintenance domain, this alarm occurs.
Attribute
Alarm Severity
Alarm Type
Major
Environment alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 Indicates the number of the Ethernet port where the alarm is generated.
Issue 02 (2011-10-31)

463
OptiX OSN 8800/6800/3800

Parameter
4 Alarm Processing
Description
Parameters 3 and 4 Indicates the VLAN ID.

Parameter 5
Parameters 6 to 9
Indicates the ID of the MP where the alarm occurs. The highest byte
indicates the network ID. The second highest byte indicates the node ID
of the network. The lower two bytes indicate the identifier of the MP on
the network node.
The MP should be unique networkwide. Each node supports a maximum
of 1024 MPs (each data board supports a maximum of 128 MPs).

The MP should be unique networkwide. The MP conflict can affect the protocol and cause the
LB and LT tests to become abnormal. The services may be incorrectly received.
Possible Causes
Multiple MPs with the same MPID are created in a maintenance domain.
Procedure
Step 1 View the EX_ETHOAM_MPID_CNFLCT alarm on the U2000 and confirm the ID of the
relevant MP according to the alarm parameters.
Step 2 Query the information about the MP. Delete all the MPs that repeat the MPID, the alarm is
----End
Related Information
None
4.60 EXT_MODULE_OFFLINE
Description
Extended wavelengh module offline. This alarm is generated when a user has configured services
on the channel corresponding to an extended module, but the physical extended module is offline.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 02 (2011-10-31)

464
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

All services on the channel corresponding to the extended module are unavailable.
Possible Causes
A user has configured services on the channel corresponding to the extended module, but the
physical extended module is offline.
Procedure
Step 1 Check whether services on the channel corresponding to the extended module are necessary.
Step 2 If the services are necessary, check whether an extended module is properly installed. If the
extended module is properly installed, replace it with a new one.
Step 3 If services are not necessary, delete the services.
----End
Related Information
None
4.61 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm is
generated when the system detects the loss of the external clock source traced by the equipment.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
Name
Meaning
Parameter 1
Indicates the number of the subrack where the clock board is located.
Parameter 2
The value is always 0xf0.
Issue 02 (2011-10-31)

465
OptiX OSN 8800/6800/3800

Name
Meaning
Parameter 3
Indicates the reserved byte, whose value is always 0x00.
Parameter 4
Indicates which external clock source is lost.
4 Alarm Processing
l 0x01: The first external clock source is lost.

l 0x02: The second external clock source is lost.

When the EXT_SYNC_LOS alarm is generated, the external clock source of the system is lost
and cannot be traced by the equipment. This is because the clock quality may be lowered, the
service quality may be affected, and pointer justifications and even bit errors may be generated.
Possible Causes
The possible causes of the EXT_SYNC_LOS alarm are as follows:
l
Cause 1: The physical interface for the external clock source loses signals.
Cause 2: The input and output modes of the external clock source are inconsistent.
Cause 3: The clock input cable is incorrectly connected.
Cause 4: The clock board is faulty.
Query alarms on the U2000. Determine the number of the subrack where the clock loss
occurs and which clock is lost according to the alarm parameters.
Cause 1: The physical interface for the external clock source loses signals.
Procedure
1.
1.
If the alarm persists, check whether the input and output modes of the external clock
source are consistent. After the input and output of the external clock source are set
to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared. For
details, see Configuring Physical Clock in the Feature Description.
Cause 3: The clock input cable is incorrectly connected.

1.
Check whether the output signals of the external clock equipment are normal. If not,
replace the faulty external clock equipment, and then check whether the alarm is
cleared.
If the alarm persists, check whether the clock input cable is correctly connected. If
not, ensure the correct connection of the clock input cable, and then check whether
the alarm is cleared. For details, see the Installation Guide.

1.
If the alarm persists, perform cold reset on the timing board, and then check whether
the alarm is cleared. For details, see Performing a Cold Reset of a Board in the
Supporting Tasks.
2.
If the alarm persists, replace the clock board. For details, see the Parts Replacement.
----End
Issue 02 (2011-10-31)

466
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
4.62 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating the loss of the external timing source. This alarm
is generated when the board does not detect the external timing signal after the external timing
port is enabled.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the number of the subrack where the clock board is located.
Parameter 2
The value is always 0xf0.
Parameter 3
Indicates the reserved byte, whose value is always 0x00.
Parameter 4
Indicates which external timing source is lost.

l 0x02: The first external timing source is lost.
l 0x04: The second external timing source is lost.

The time of the local NE cannot be synchronous with the time of the external timing equipment
to which the enabled external timing port is connected.
Possible Causes
The possible causes of the EXT_TIME_LOC alarm are as follows:
Issue 02 (2011-10-31)

467
OptiX OSN 8800/6800/3800

4 Alarm Processing
Cause 1: The physical interface for the external timing source loses signals.
Cause 2: The timing input cable is incorrectly connected.
Query alarms on the U2000. Determine the number of the subrack where the external timing
loss occurs and which external timing source is lost according to the alarm parameters.
Cause 1: The physical interface for the external timing source loses signals.
Procedure
1.
Cause 2: The timing input cable is incorrectly connected.

1.
Check whether the output signals of the external timing equipment are normal. If not,
replace the faulty external timing equipment, and then check whether the alarm is
cleared.
If the alarm persists, check whether the timing input cable is correctly connected. If
not, ensure the correct connection of the timing input cable, and then check whether
the alarm is cleared. For details, see "Installing and Routing Clock Cables" in the
Quick Installation Guide.

1.
If the alarm persists, perform cold reset for the clock board, and then check whether
the alarm is cleared. For details, see "Performing a Cold Reset of a Board" in the
Supporting Tasks.
2.
If the alarm persists, replace the clock board. For details, see "Replacing the Clock
Board" in the Parts Replacement.
----End
Related Information
For details, see "IEEE 1588v2" in the Feature Description.
4.63 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating a fan failure. This alarm is generated when one or more
fans fail.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

468
OptiX OSN 8800/6800/3800

4 Alarm Processing

The failure of one or more fans leads to the increase on the board temperature and even the
damage to the board.
Possible Causes
l
The fans stop running.
The speed of the fans is excessively low.
The fans fail.
Procedure
Step 1 Check whether the FAN Speed Level is set to Stop or Low Speed through the U2000. If that
is the case, set FAN Speed Level to High Speed.
Step 2 If the alarm persists, replace the faulty fan tray assembly. For details, see the Parts
Replacement.
----End
Related Information
None
4.64 FAN_FAULT
Description
The FAN_FAULT is an alarm indicating a fan fault. This alarm is generated when one fan fails.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The failure of one fan may lead to the increase on the board temperature and even the damage
to the board.
Possible Causes
l
One fan fails.
The logical inspection fails.
Issue 02 (2011-10-31)

469
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Replace the fan tray assembly. For details, see the Parts Replacement.
----End
Related Information
None
4.65 FEATURE_WITHOUT_LICENSE
Description
Service without license. A license-controlled feature is used but a license for the feature is not
installed.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
None

A user cannot create, enable, or modify the license-controlled service or feature, but can query,
delete, or deactivate the service or feature. The available services are not affected and are still
available, but the alarm is reported.
Possible Causes
A license-controlled feature is used but a license for the feature is not installed. The possible
causes why the feature is not authorized are as follows:
l
A license for this feature is not purchased.
The license file does not match ESN or V/R version, and the system has been operating for
60 consecutive days.
The trial period of the license-controlled feature has expired, and the keepalive period of
60 days has also elapsed since the expiry.
Procedure
Step 1 Load a correct license file onto the system so that the license-controlled feature is authorized,
or delete the service of unauthorized feature.
----End
Issue 02 (2011-10-31)

470
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.66 FC_8B10BERR_OVER
Description
The FC_8B10BERR_OVER is an alarm indicating that the 8B10B bit errors in the FC services
cross the threshold. When the 8B10B bit errors in the FC services cross the threshold, this alarm
is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The quality of services is affected.
Possible Causes
There are bit errors on the link, which causes the 8B10B bit errors on the ports of the FC link
layer after decoding cross the threshold.
Procedure
Step 1 Check whether there is dust on the optical fiber connector or the fiber is aged. If that is the case,
clean the optical fiber connector or replace the fiber. For details, see the Supporting Tasks.
Step 2 Step 2 Check whether the input optical power of the board is within the normal range. For optical
power specifications, see the corresponding Product Description. If the optical power is
abnormal, see the handing procedures for the IN_PWR_HIGH and IN_PWR_LOW alarms, to
clear the alarm.
----End
Related Information
None
4.67 FCS_ERR
Issue 02 (2011-10-31)

471
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The FCS_ERR is an alarm indicating that the frame check sequence (FCS) is incorrect. At the
local station, perform an FCS check for the received frames encapsulated in the GFP format. If
any error occurs in the check, the alarm is reported.
NOTE
The alarm is generated only when the received service of the local station is the GFP service.
This is because the IDLE frame lacks the FCS field, if the IDLE frame is encapsulated in the GFP format,
the FCS check errors may occur.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

l
If the FCS_ERR alarm is generated due to inconsistent encapsulation protocols, the services
are interrupted.
If the FCS_ERR alarm is generated due to bit errors in the system, packets are lost or
services are interrupted.
Possible Causes
The possible causes of the FCS_ERR alarm are as follows:
l
Cause 1: Mapping protocols of the local station and opposite station are inconsistent. For
example, the local station uses the GFP encapsulation protocol whereas the opposite station
uses the LAPS encapsulation protocol. Or the parameter settings of the protocol are
inconsistent. For example, both stations use the GFP encapsulation but Extension Header
Option of the local station is set to Yes whereas Extension Header Option of the opposite
station is set to No.
Cause 2: There are bit errors on the link.
Cause 3: The optical connector of the Ethernet board at the optical interface is loose or
dirty.
Query current alarms on the U2000. Determine the VCTRUNK number that reports the
alarm. For details, see Querying the Current Alarms in the Supporting Task.
Cause 1: The encapsulation protocols adopted by the local station and the opposite station
are inconsistent or the settings of the protocol parameters are inconsistent.
Procedure
1.
Issue 02 (2011-10-31)
Check whether the encapsulation protocols of corresponding VCTRUNK ports of the

local station and the opposite station are consistent and whether the parameter settings
472
OptiX OSN 8800/6800/3800

4 Alarm Processing
of the protocols are consistent. For example, check whether the parameters such as
Scramble and Set Inverse Value for CRC about the protocols are set as the same.
For details, see the Configuration Guide. Then, check whether the alarm is cleared.
2.
l
If the alarm persists, see Cause 2.
Cause 2: There are bit errors on the link.

1.
Check the network-wide alarms on the U2000. For operations, see the Routine
Maintenance. Check whether there are bit error alarms such as B3_EXC and
B3_SD on the link. If these alarms occur, clear these alarms according to
corresponding procedures. Then, check whether the alarm is cleared.
2.
Cause 3: The optical connector of the Ethernet board at the optical interface is loose or
dirty.
1.
Check whether the connector of the fiber is normal. If the connector is loose, tighten
the connector.
2.
See Inspecting and Cleaning the Fiber-Optic Connectors in the Supporting Task to
check whether the connector is dirty. If the connector is dirty, ensure that it is cleaned
immediately. For operations, see the Supporting Task.
3.
If the attenuation value of the optical attenuator is improper, increase or decrease it to

a proper value. The value of the optical attenuator is set according to the receive optical
power of the board. For optical power specifications of boards, see "Technical
Specifications" of the Product Description. For operations of adjusting the optical
attenuator, see Adjusting, Replacing, Adding and Removing Attenuator in the
Supporting Task. For operations of querying the optical power, see Querying Optical
Power of the Board in the Supporting Task.
NOTE
From Querying Optical Module Information in the Supporting Task or Hardware

Description, you can obtain the manufacturer information of the optical module on the board.
4.
l

1.
After the preceding causes are excluded, if the alarm persists, the board where the
alarm is reported is faulty. In the case of the Ethernet board with an interface board,
replace the interface board first. In the case of the board without an interface board,
replace the faulty board. For details, see Parts Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

473
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.68 FEC_LOF
Description
The FEC_LOF is an alarm indicating that lost of the FEC frame. The alarm occurs when the
FEC frame is lost.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the FEC_LOF alarm is generated, the FEC function is disabled. Consequently, the services
are interrupted.
Possible Causes
l
The cable is faulty, or the optical power is improper.
The service rate is incorrect.
The clocks on the NEs are out of synchronization.
Certain problems are found in the services from the opposite end.
Procedure
Step 1 View the FEC_LOF alarm on the U2000 to determine the relevant board.
Step 2 View the receive optical power of the board on the U2000. If the receive optical power is
excessively low, clean the fiber header and connector. If the receive optical power is excessively
high, provide more optical attenuators. After making sure that the receive optical power is proper,
check whether the FEC_LOF alarm is cleared.
Step 3 If the alarm persists, check whether the upstream service is the FEC service at the same rate. If
not, configure the FEC service at a correct rate, and then check whether the FEC_LOF alarm is
cleared.
Step 4 If the alarm persists, check whether the upstream service is supported by the board. If not,
configure a correct service, and then check whether the FEC_LOF alarm is cleared.
Step 5 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_LOF alarm is cleared.
Issue 02 (2011-10-31)

474
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 6 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports
the alarm at the local station.
Step 7 If the alarm persists, the board at the opposite station may be faulty. In this case, replace the
board.
----End
Related Information
None
4.69 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the FEC_OOF alarm is generated, the FEC function is disabled. Consequently, the
Possible Causes
l
The fiber is faulty, or the optical power is improper.
Excessive bit errors occur during transmission.
The clocks on the NEs are out of synchronization.
The transmit unit at the opposite end is faulty.
Procedure
Step 1 View the FEC_OOF alarm on the U2000 to determine the relevant board.
Step 2 View the received optical power of the board on the U2000. If the received optical power is
excessively low, clean the fiber header and the connector. If the received optical power is
excessively high, provide more optical attenuators. After making sure that the received optical
power is proper, check whether the FEC_OOF alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power at the opposite end. If the transmit optical
power is excessively low, replace the board at the opposite end.
Issue 02 (2011-10-31)

475
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 If the alarm persists, check whether the clocks on the local NE and the opposite NE are
synchronous with those on the network. If not, set the clock tracing function, and then check
whether the FEC_OOF alarm is cleared.
Step 5 If the alarm persists, check whether the fiber is normal. If yes, replace the board that generates
the alarm.
Step 6 If the alarm persists, replace the cross-connect and timing board at the local station.
Step 7 If the alarm persists, replace the line board at the opposite end.
Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite end.
----End
Related Information
None
4.70 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating that the input flow at the Ethernet port exceeds the
threshold. When the received traffic at the Ethernet port exceeds the expected traffic, this alarm
is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Parameter
Description
Parameters 1 and 2 Indicates the extra traffic (Mbit/s) of the actual traffic that exceeds the
expected traffic.

l
Issue 02 (2011-10-31)
During data transmission, when the configured bandwidth is lower than the actual traffic
at the port and there is the FLOW_OVER alarm, service packets are lost.
476
OptiX OSN 8800/6800/3800

4 Alarm Processing
During data transmission, when the configured bandwidth is higher than or equal to the
actual traffic at the port and there is the FLOW_OVER alarm, the system and the services
are not affected.
Possible Causes
The traffic received by the port is greater than the preset traffic at the port.
Procedure
Step 1 View the information about the alarm on the U2000 and identify the board and number of the
port where the alarm is reported.
l
If the expected traffic at the port can be increased, increase the expected traffic to a value
greater than the actual traffic at the port.
If the expected traffic at the port cannot be increased, service packet loss can be avoided
only by reducing the traffic transmitted by the opposite station.
----End
Related Information
None
4.71 FPGA_ABN
Description
The FPGA_ABN is an alarm indicating that the FPGA status is abnormal. The alarm occurs
when the standby FPGA is currently used by the board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The active FPGA file of the board is abnormal and the standby FPGA file is enabled. If the
standby FGPA file is abnormal, the board cannot work, which has an influence on the services
of users. This problem needs to be handled in time.
Possible Causes
l
Issue 02 (2011-10-31)
The active FPGA file does not exist when the board starts.
477
OptiX OSN 8800/6800/3800

4 Alarm Processing
Loading of the active FPGA file fails when the board starts.
Procedure
Step 1 Reload the FPGA file to the board.
----End
Related Information
None
4.72 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is forcibly selected.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the slot of the clock board that is selected forcibly.

l 0x01 indicates the slot with a smaller number.
l 0x02 indicates the slot with a bigger number.

If the forcibly selected clock board is normal, transient interruption occurs when the services
are switched. Otherwise, the services are interrupted.
Possible Causes
The command of forcibly selecting the clock board is issued.
Issue 02 (2011-10-31)

478
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 After the command of forcibly selecting the clock board is cancelled, the FSELECT_STG alarm
is automatically cleared.
----End
Related Information
None
4.73 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates why the packets are lost.

The services lose packets or are interrupted.
Possible Causes
l
The packets received by the port do not match the service configuration.
The packets received by the port do not match the port configuration.
Packets are lost because of data congestion, such as the loss of the CAR shaping packet.
The packets in a queue are lost, such as the loss of the COS packet.
The MAC address of the received packets is listed on the black list.
Issue 02 (2011-10-31)

479
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the service configuration and the attribute configuration of the port match the
received packets. If a mismatch occurs, re-configure the service and/or the attributes of the port.
Step 2 If the alarm persists, check whether the packets transmitted at the opposite station are proper. If
not, transmit proper packets again.
Step 3 If the alarm persists, check whether the QoS is configured properly. If not, re-configure the QoS.
Step 4 If the alarm persists, check whether the black list is configured properly. If not, re-configure the
black list.
----End
Related Information
None
4.74 GAINDATA_MIS
Description
The GAINDATA_MIS is an alarm indicating mismatch of gain attribute. When the nominal
gain value issued by the NE software falls beyond the tuning range of the nominal gain, the
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The service quality may be affected.
Possible Causes
Cause 1: As for the nominal gain, replacing the optical amplifier unit (OAU) or the optical
module causes that the nominal gain value issued by the NE software falls beyond the new tuning
range of the nominal gain.
Procedure
l
Issue 02 (2011-10-31)
Cause 1: The nominal gain value issued by the NE software falls beyond the new tuning
range of the nominal gain.
480
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
Query the threshold of the current actual nominal gain on the U2000. Reconfigure a
valid nominal gain value for the optical interface channel of the unit based on the
queried threshold.
----End
Related Information
None
4.75 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware failure. When the system detects hardware
failure, this alarm is reported.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

481
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameter 1
Indicates the fault type of the alarm. For example:

0x01 indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the
board is not in good contact with the backplane, that is, the
board is not secured).
0x03 indicates that 38M system clock 1 is abnormal.
0x05 indicates that the 2M clock source is abnormal.
0x06 indicates the digital phase-locked loop is abnormal.
0x07 indicates that the 38M service clock is lost.
0x08 indicates that the bus is abnormal.
0x09 indicates that the standby board in TPS protection is
abnormal.
0x0a indicates the active crystal oscillator of the clock stops.
0x0b indicates the frequency deviation of the crystal oscillator
is excessively large.
0x0c indicates that the standby crystal oscillator of the clock
stops.
0x0d indicates that the CPU/DSP/coprocessor fails.
0x0e indicates that the memory component the fails.
0x0f indicates that the component of the programmable logic
device fails
0x10 indicates that the SDH component fails.
0x11 indicates that the data communication component fails.
0x12 indicates that the clock component fails.
0x13 indicates that the interface component fails.
0x14 indicates that the power component fails.
0x15 indicates that other faults occur.
0x16 indicates that the simulated phase-locked loop (PLL) is
abnormal.
0x17 indicates that the 32M clock is invalid.
0x1a indicates that the loop of the cross-connect chip fails.
Issue 02 (2011-10-31)

482
OptiX OSN 8800/6800/3800

Parameter
4 Alarm Processing
Description
0x1b indicates that the 8k online signal is pulled down.
0x1c indicates that the chip of the probe laser fails.
0x1d indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x22 indicates the 2M system frame header 1.
0x24 indicates that the self-check fails.
0x25 indicates the self-check of the PHY chip fails.
0x26 indicates that detecting the port status of the PHY chip
fails.
0x27 indicates that the 25M clock is lost.
0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it

indicates that bus A is abnormal; When Parameter 1 is 0x08
and Parameter 2 is 0x02, it indicates that bus B is abnormal.
Parameter 3 is 0xff.
When Parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13,
0x14, 0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have
different values, which indicate different component, module,
or chip faults.
When Parameter 1 is 0x15, Parameter 2 and Parameter 3
indicate other equipment faults.
When Parameter 1 is of another value, Parameter 2 and
Parameter 3 are always 0xff.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l
Cause 1: The NE power is abnormal.
Cause 2: The board is not connected to the backplane properly or the board is faulty.
Issue 02 (2011-10-31)

483
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
Cause 1: The NE power is abnormal.

1.
Check whether the NE power works normally. If not, feed the NE with power supply.
For details, see the Installation Guide.
Cause 2: The board is not connected to the backplane properly or the board is faulty.
1.
Reseat the board. For operations, see the Installation Guide. In the case of the OptiX
OSN 6800 and OptiX OSN 8800 equipment, see "Removing Boards" and "Inserting
Boards". In the case of the OptiX OSN 3800 equipment, see "Removing Boards" and
"Inserting Boards".. Then, check whether the alarm is cleared.
2.
If the alarm persists, replace the board. For details, see the Parts Replacement.
----End
Related Information
None
4.76 HARD_ERR
Description
The HARD_ERR is an alarm indicating a hardware error. The alarm occurs when the board
hardware has a minor fault.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

484
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameter 1
Indicates the fault type of the alarm. For example:

0x01 indicates that the power supply module is abnormal.
0x02 indicates that the board is not properly installed (the
board is not in good contact with the backplane, that is, the
board is not secured).
0x05 indicates that the 2M clock source is abnormal.
0x06 indicates the digital phase-locked loop is abnormal.
0x07 indicates that the 38M service clock is lost.
0x08 indicates that the bus is abnormal.
0x09 indicates that the standby board in TPS protection is
abnormal.
0x0a indicates the active crystal oscillator of the clock stops.
0x0b indicates the frequency deviation of the crystal oscillator
is excessively large.
0x0c indicates that the standby crystal oscillator of the clock
stops.
0x0d indicates that the CPU/DSP/coprocessor fails.
0x0e indicates that the memory component the fails.
0x0f indicates that the component of the programmable logic
device fails
0x10 indicates that the SDH component fails.
0x11 indicates that the data communication component fails.
0x12 indicates that the clock component fails.
0x13 indicates that the interface component fails.
0x14 indicates that the power component fails.
0x15 indicates that other faults occur.
0x16 indicates that the simulated phase-locked loop (PLL) is
abnormal.
0x1a indicates that the loop of the cross-connect chip fails.
Issue 02 (2011-10-31)

485
OptiX OSN 8800/6800/3800

Parameter
4 Alarm Processing
Description
0x1b indicates that the 8k online signal is pulled down.
0x1c indicates that the chip of the probe laser fails.
0x1d indicates that the chip of the loading laser fails.
0x1e indicates that the clock of the DSP driver chip is lost.
0x1f indicates that the output clock of the DSP is lost.
0x20 indicates that the RTM module is offline.
0x21 indicates that a chip fault.
0x24 indicates that the self-check fails.
0x25 indicates the self-check of the PHY chip fails.
0x26 indicates that detecting the port status of the PHY chip
fails.
0x27 indicates that the 25M clock is lost.
0x28 indicates that the APD fails.
Parameters 2 and Parameters 3 When Parameter 1 is 0x08 and Parameter 2 is 0x01, it

indicates that bus A is abnormal; When Parameter 1 is 0x08
and Parameter 2 is 0x02, it indicates that bus B is abnormal.
Parameter 3 is 0xff.
When Parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13,
0x14, 0x16, 0x19, or 0x21, Parameter 2 and Parameter 3 have
different values, which indicate different component, module,
or chip faults.
When Parameter 1 is 0x15, Parameter 2 and Parameter 3
indicate other equipment faults.
When Parameter 1 is of another value, Parameter 2 and
Parameter 3 are always 0xff.

The services are not affected. For specific influence, see Parameter 1.
Possible Causes
Issue 02 (2011-10-31)

486
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Perform warm reset or cold reset on the faulty board through the U2000. For details, see the
Troubleshooting.
----End
Related Information
None
4.77 HP_LOM
Description
The HP_LOM is an alarm indicating higher order path loss of multiframe.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the HP_LOM alarm occurs, it indicates that the values of the H4 bytes in the payload are
inconsistent with the expected values in several consecutive basic frames in the multiframe
sequence. The multiframe indication of the VC-12 services is lost. As a result, the VC-12 services
are unavailable.
When the HP_LOM alarm occurs, the board will insert VTAIS (TU_AIS for tributary services)
into the corresponding path.
Possible Causes
The possible causes of the HP_LOM alarm are as follows:
l
The services are incorrectly configured.
The H4 byte is lost or the H4 byte value is invalid.
Procedure
Step 1 Check whether the services at the opposite station and the local station are correctly configured.
If not, modify the incorrect configuration and issue it again.
Issue 02 (2011-10-31)

487
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 2 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Options
Description
If this alarm is cleared
The fault is removed. End the alarm handling.
If this alarm persists
Step 3 Check whether the cross-connect unit and the line board are faulty. You can employ the optical
path self-loop method to check whether any hardware of the opposite station is faulty. If the
fault is located on the opposite station. Replace the line board first and then the SCC board of
the opposite station.
Step 4 View alarms on the U2000 to check whether the HP_LOM alarm is cleared.
Options
Description
Step 5 Ensure the local station is faulty. Replace the faulty board.
----End
Related Information
None.
4.78 HP_RDI
Description
The HP_RDI is an alarm indicating that the local station receives the remote defect indication
in the higher order path sent from the opposite station
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

488
OptiX OSN 8800/6800/3800

4 Alarm Processing

When the HP_RDI alarm occurs, it indicates that the services received by the opposite station
have the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm. As a result, the HP_RDI alarm is
sent to the local station.
Possible Causes
The possible causes of the HP_RDI alarm are as follows:
l
The opposite line receives the AU_AIS/AU_LOP/HP_TIM/HP_SLM alarms.
The receive part at the opposite station is faulty.
The transmit part at the local station is faulty.
Procedure
Step 1 View the alarms of the NE on the U2000 and check whether there are higher order alarms.
Options
Description
If the AU_AIS, AU_LOP, HP_TIM, and

HP_SLM alarms occur
Refer to the corresponding section in this

document to clear the alarm.
If the AU_AIS, AU_LOP, HP_TIM, and

HP_SLM alarms do not occur
Step 2 View alarms on the U2000 to check whether the HP_RDI alarm is cleared.
Options
Description
Step 3 Perform the loopback for the stations at two ends of the line. Locate the faulty board.
Options
Description
The board at the opposite station reports the

HP_RDI alarm
The transmit end of the board at the opposite

station is faulty. Replace the faulty board.
The board at the local station reports the

HP_RDI alarm
The receive end of the board at the local

----End
Related Information
AU_AIS, AU_LOP, HP_TIM, HP_SLM
Issue 02 (2011-10-31)

489
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.79 HP_REI
Description
The HP_REI is an alarm indicating that the local station receives the remote bit error in the
higher order path sent from the opposite station.
Attribute
Alarm Severity
Alarm Type
Warning
Service quality alarm
Parameters
None

When the HP_REI alarm occurs, it indicates that the services received by the opposite station
have the higher order B3 errored blocks. As a result, the HP_REI alarm is sent to the local station.
Possible Causes
The possible cause of the HP_REI alarm is as follows:
The B3 bit errors are received at the opposite station.
Procedure
Step 1 View the alarms on the opposite NE, and check whether there are B1 or B2 bit errors.
Options
Description
There are B1 or B2 bit errors
Refer to the corresponding section in this

document to clear the alarm.
There are B1 or B2 bit errors
Step 2 Check whether the equipment is securely grounded and whether there is intense interference
source around the equipment. If few B3 bit errors occur at the remote end, the fault usually lies
in the equipment instead of the optical path.
Step 3 Perform the loopback for the stations at two ends of the line. Check whether the cross-connect
and timing unit and the tributary board on both the opposite equipment and local equipment
operate normally. Following the service direction, check upstream stations one by one. Locate
the faulty board.
Issue 02 (2011-10-31)

490
OptiX OSN 8800/6800/3800

4 Alarm Processing
Options
Description
The board at the opposite station reports B3

bit errors
The receive end at the opposite station is

faulty. Replace the boards in an order of line
board, tributary board, and SCC board.
The board at the local station reports B3 bit

errors
The transmit end of the board at the local

CAUTION
Replacing the tributary board will interrupt services. This operation is of risk.
----End
Related Information
B1_EXC, B1_SD, B2_EXC, B2_SD
4.80 HP_SLM
Description
The HP_SLM is an alarm indicating the mismatch of the higher order path signal label (C2)
received by the line board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_SLM alarm occurs, it indicates that the higher order overhead C2 byte received
by the local station is inconsistent with the C2 byte expected. As a result, the services in the
payload are unavailable.
When the HP_SLM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_SLM alarm are as follows:
Issue 02 (2011-10-31)

491
OptiX OSN 8800/6800/3800

4 Alarm Processing
The signal label C2 byte expected to be received by the local station is inconsistent with
that transmitted by the opposite station.
Procedure
Step 1 Check whether the C2 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If the configuration
is different, modify them to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option
Description
Step 4 View alarms on the U2000 to check whether the HP_SLM alarm is cleared.
Option
Description
Step 5 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Option
Description

HP_SLM alarm

board and SCC board.
The board at the local station reports

HP_SLM bit errors

CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
Issue 02 (2011-10-31)

492
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.81 HP_TIM
Description
The HP_TIM is an alarm indicating the mismatch of the higher order path trace identifier (J1)
received by the line board.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_TIM alarm occurs, it indicates that the higher order overhead J1 byte received by
the local station is inconsistent with the J1 byte expected. As a result, the services in the payload
are unavailable.
When the HP_TIM alarm occurs, the board returns the HP_RDI alarm to the opposite station.
Possible Causes
The possible causes of the HP_TIM alarm are as follows:
l
The path trace identifier J1 byte expected to be received by the local station is inconsistent
with that transmitted by the opposite station.
Procedure
Step 1 Check whether the J1 byte transmitted by the corresponding higher order path at the opposite
station is consistent with that expected to be received by the local station. If not, modify them
to be consistent and issue the configuration again.
Step 2 View alarms on the U2000 to check whether the HP_TIM alarm is cleared.
Options
Description
Issue 02 (2011-10-31)

493
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 Perform the loopback for the stations at two ends of the line. Check the opposite equipment and
local equipment to locate the faulty board.
Option
Description

HP_TIM alarm

board and SCC board.
The board at the local station reports HP_TIM

bit errors

CAUTION
Replacing the board will interrupt services. This operation is of risk.
----End
Related Information
None.
4.82 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the higher order path received by the line board is
unloaded.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the HP_UNEQ alarm occurs, it indicates that the signal payload transmitted by the line
board at the opposite station is unloaded.
Possible Causes
The possible cause of the HP_UNEQ alarm is as follows:
Issue 02 (2011-10-31)

494
OptiX OSN 8800/6800/3800

4 Alarm Processing
The C2 byte in five consecutive frames is all "0"s.
Procedure
Step 1 Check the C2 byte configuration of the opposite NE to see whether the C2 byte has sent UNEQ.
If the configuration is incorrect, modify and re-issue the configuration.
Step 2 Check whether the line board of the opposite NE is configured with services in the transmitting
direction. If not, re-configure the services of the NE.
Step 3 View alarms on the U2000 to check whether the HP_UNEQ alarm is cleared.
Options
Description
Step 4 The board at the local station is faulty. Replace the faulty board.
----End
Related Information
None.
4.83 HSC_UNAVAIL
Description
The HSC_UNAVAIL is an alarm indicating that the working/protection switching fails. This
alarm occurs when the configured active and standby boards fail to perform switching
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the working/protection status of the invalid board.
Issue 02 (2011-10-31)

495
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameter 2
Indicates the slot ID of the invalid board.

The active-standby switching and backup functions are not available.
Possible Causes
l
The active and standby board versions mismatch.
The hardware of the standby board is faulty.
Communication between the active and standby boards is abnormal.
Procedure
Step 1 Replace the standby board. For details, see the Parts Replacement.
----End
Related Information
None
4.84 INTRA_OTU_STA_INDI
Description
The INTRA_OTU_STA_INDI alarm indicates the state of the Intra-OTU 1+1 optical channel
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Issue 02 (2011-10-31)

496
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameters 1

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l
When the intra-board 1+1 protection group actuates switching, services are transiently
interrupted.
When the alarm is reported, the working channel or the protection channel of the board
might have faulty services that need to be restored.
Possible Causes
l
Cause 1: A user issues a command to perform the external switching such as forced
switching, manual switching or locked switching.
Cause 2: The services of the working channel or the protection channel of the intra-board
1+1 protection group are faulty.
Cause 1: A user issues a command to perform the external switching.
Procedure
Issue 02 (2011-10-31)
1.
2.
3.

external switching.
Cause 2: The services of the working channel or the protection channel of the intra-board
1+1 protection group are faulty.
1.
Query whether the relevant boards for configuring the protection group have the
alarms, such as R_LOF, R_LOS, POWER_DIFF_OVER, R_LOC, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC, IN_PWR_HIGH,
IN_PWR_LOW, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG,
OTUk_EXC. If yes, handle the alarms by referring to the corresponding alarm
handling procedure to restore the services of the working channel or the protection
channel.
2.
Revertive or not. If yes, the protection channel automatically switches to the working
channel and the alarm clears. If the attribute is Non-Revertive, set it to Revertive.
497
OptiX OSN 8800/6800/3800

4 Alarm Processing
Then the protection channel automatically switches to the working channel and the
alarm clears.
l
1.
This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
4.85 IPA_SHUT
Description
Laser shutdown by IPA. When the IPA function detects a LOS alarm for an input port of a board,
it automatically shuts down the laser for the corresponding output port of the board.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The laser on the corresponding output port of the board is shut down and therefore cannot launch
optical power to the downstream board.
Possible Causes
l
The line fiber is damaged. As a result, the board reports a MUT_LOS alarm.
The line loss is excessive. As a result, the input optical power is lower than the LOS
threshold of the board.
The board is faulty. As a result, it reports a MUT_LOS alarm.
Procedure
Step 1 On the U2000, check whether a MUT_LOS alarm is reported on the boards in an IPA pair. If
the alarm is reported, clear the alarm by referring to MUT_LOS. After the fault on the line is
rectified, the laser on the board that reports the IPA_SHUT alarm is enabled again and the
IPA_SHUT alarm is automatically cleared.
----End
Issue 02 (2011-10-31)

498
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
The system provides the intelligent power adjustment (IPA) function for PID boards. For details,
see "Introduction to PID IPA" in the Feature Description.
4.86 J0_MM
Description
The J0_MM is an alarm indicating trace indicator mismatch. The alarm occurs when the received
J0 byte is not consistent with the J0 byte to be received.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services are not affected.
Possible Causes
l
The J0 byte mismatches.
The service connection is incorrect.
Procedure
Step 1 Check whether the J0 byte to be transmitted by the board at the opposite station is set the same
as the J0 byte to be received by the board at the local station. If they are inconsistent, set the two
as the same.
Step 2 If the alarm persists, bit errors may exist in the line. Refer to the handling procedure of the B1_SD
or B2_SD alarm for troubleshooting.
Step 3 If the alarm persists, consider whether to replace the board according to the actual situation
because only the J0_MM alarm does not affect the services. For details, see the Parts
Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

499
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.87 K1_K2_M
Description
The K1_K2_M is an alarm indicating K1 and K2 byte mismatch. This alarm occurs when the
path numbers indicated in the transmitted K1 byte and the received K2 byte are inconsistent and
the inconsistency lasts for a time period (160 ms by default).
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K1_K2_M alarm are as follows:
l
The fiber connection is incorrect.
The protection group types configured at the two ends of the protection group are
inconsistent.
Procedure
Step 1 View this alarm on the U2000, and determine the ID of the MS where the alarm is reported
according to alarm parameters.
Step 2 Check whether the fiber connection that this MS travels through is normal, and whether the
logical configuration of the fiber is consistent with the physical configuration. After confirming
that the fiber connection is correct, check whether the alarm is cleared
Step 3 If the alarm persists, check whether the protection group types configured at the two ends of the
protection group are consistent. If not, re-configure the protection type and check whether the
alarm is cleared.
Step 4 If the alarm persists, check the boards configured with the MS at the local and opposite ends are
faulty. If yes, replace the faulty board. For details, see the Parts Replacement.
Issue 02 (2011-10-31)

500
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 5 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are
faulty. If yes, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.88 K2_M
Description
The K2_M is an alarm indicating K2 byte mismatch. This alarm occurs when the protection
group type configured at the opposite end indicated by the fifth bit (counted from the highest bit
to the lowest bit) of the K2 byte is inconsistent with that of the local end, and the inconsistency
lasts for a time period (2s by default).
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The MS protection fails. As a result, services are interrupted if a fiber cut or another fault occurs.
Possible Causes
The possible causes of the K2_M alarm are as follows:
l
The MS configuration is incorrect.
Procedure
Step 1 Check whether the MS configuration on the local NE is consistent with that on the opposite NE.
If not, re-configure the MS and check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the boards configured with MSs at the local and opposite
ends are faulty. If yes, replace the faulty board and check whether the alarm is cleared
Issue 02 (2011-10-31)

501
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 3 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are
faulty. If yes, replace the faulty board and check whether the alarm is cleared
----End
Related Information
None
4.89 L_SYNC
Description
Loss of synchronization alarm. This alarm is generated when loss of synchronization occurs in
the physical coding sublayer (PCS) of a receiving port.
Attribute
Alarm Severity
Alarm Type
Critical
Service quality alarm
Parameters
None

When loss of synchronization occurs in the physical coding sublayer (PCS) of a receiving port,
the port stops receiving data. therefore, the loss of synchronization alarm affects the quality of
service (QoS). In this case, the service is interrupted.
Possible Causes
l
Configuration of working mode, signal type or rate of the equipment at the local station
and the opposite station are not consistent.
Link failure.
The equipment in the opposite station is faulty.
The receive optical power of the local board is abnormal.
The board at the local station is faulty.
Procedure
Step 1 Check whether the configuration of working mode, signal type or rate of the equipment at the
local station and the opposite station are consistent. If they are not consistent, modify the setting
to ensure the consistency.
Issue 02 (2011-10-31)

502
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 2 If the alarm persists, check whether the fiber or cable that is used to connect between the
equipment at the local station and the opposite station are well connected. If they are not well
connected, reconnect or replace the fiber or cable.
Step 3 If the alarm persists, check whether the data equipment in the opposite station is faulty. If that
is the case, remove the fault of the data equipment in the opposite station.
Step 4 If the alarm remains, use the U2000 to check whether the receive optical power of the WDMside interface of the alarm-reporting board is in normal range. For optical power specifications
of boards, see the Product Description. If the optical power is abnormal, take the alarm as the
IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Step 5 If the alarm persists, the board at the local station might be faulty. Replace the faulty board. For
details, see the Parts Replacement.
----End
Related Information
None
4.90 LAN_LOC
Description
Ethernet communication failure. In the case of NE cascading, this alarm is generated when the
Ethernet communication between NEs fails.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the network port is faulty or there is a cut in the network cable, the communication at this
network port fails. In this case, the communication between the NE and the U2000 stops.
Possible Causes
l
The network port is required and is enabled on the U2000. However, the network cable is
not connected to the network port or is inappropriately connected.
The network port is not required but is enabled on the U2000.
The network cable is faulty.
Issue 02 (2011-10-31)

503
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Query the alarm informations on the U2000. Check whether the corresponding network port is
required according to the alarm parameters,
If ...
Then ...
The corresponding network port is not

required.
Disable the port on the U2000. For details, see

"Disable the Unused Auxiliary Interfaces" in
the Commissioning Guide.
The corresponding network port is

required.
Check and ensure that the network cable is

properly connected to the network port.
Step 2 If the alarm persists, the network cable may be faulty. In this case, replace the network cable
and re-connect it.
Step 3 If the alarm persists, the auxiliary interface board (such as the AUX, EFI, EFI1, and EFI2 board)
may be faulty. In this case, replace the faulty board. For detailed operations, see Parts
Replacement.
----End
Related Information
None
4.91 LAG_PORT_FAIL
Description
The LAG_PORT_FAIL is an alarm indicating that the port in the aggregation group is invalid.
When the GE port is not available, the aggregation fails. Therefore, this alarm occurs.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
table.
Issue 02 (2011-10-31)

504
OptiX OSN 8800/6800/3800

Name
4 Alarm Processing
Meaning
Parameters 1 and 2 Indicates the number of the port where the alarm is generated, consisting
of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02
indicates port 2, 0x03 indicates port 3, and so on.
Parameter 3
Indicates the cause of the invalid port in the aggregate group. For example,
0x01 indicates that the port is in the link down or disabled state. 0x02
indicates that the port is in the half-duplex mode. 0x03 indicates that port
fails to receive LACP messages. 0x04 indicates that the port is selflooped.

The port in the aggregation group fails to share the service load. In this case, the port cannot
receive or transmit services.
Possible Causes
l
The port is in the link down or disabled state.
The port is in the half-duplex mode.
The port has not received LACP messages.
The port is self-looped.
Procedure
Step 1 Check the link and enabling status of all ports on the U2000. Remove link faults, and then set
the port to Enable on the U2000.
Step 2 On the U2000, check whether the operation mode of the port is set to Half-Duplex. If yes, reset it to Full-Duplex.
Step 3 Check whether the corresponding link aggregation group is configured at the opposite station.
If yes, check whether the MAC address of the opposite aggregation group that provides links to
the local aggregation group is invalid. If yes, re-configure it.
Step 4 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
4.92 LAG_VC_PORT_FAIL
Description
The LAG_VC_PORT_FAIL is an alarm indicating that the VCG port in the aggregation group
fails. When the VCTRUNK port is not available, the aggregation fails. Therefore, this alarm
occurs.
Issue 02 (2011-10-31)

505
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
table.
Name
Meaning
Parameters 1 and 2 Indicates the number of the port where the alarm is generated, consisting
of two bytes. For example, 0x00 0x01 indicates port 1, 0x00 0x02
indicates port 2, 0x03 indicates port 3, etc.
Parameter 3
Indicates the cause of the invalid port in the aggregate group. For example,
0x01 indicates that the port is in the link down or disabled state. 0x02
indicates that the port is in the half-duplex mode. 0x03 indicates that port
fails to receive LACP messages. 0x04 indicates that the port is selflooped.

The port in the aggregation group fails to share the service load. In this case, the port cannot
receive or transmit services.
Possible Causes
l
The port is in the link down or disabled state.
The port has not received LACP messages.
The port is self-looped.
Procedure
Step 1 Check whether the VCG port in the aggregation group fails. If yes, remove VCG port faults.
Step 2 Check whether the corresponding link aggregation group is configured at the opposite station.
If yes, check whether the MAC address of the opposite aggregation group that provides links to
the local aggregation group is invalid. If yes, re-configure it.
Step 3 Check whether the port is configured as self-looped. If yes, cancel the configuration.
----End
Related Information
None
Issue 02 (2011-10-31)

506
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.93 LASER_HAZARD_WARNING
Description
The laser hazard warning alarm. When a high-power laser is used in the optical transmission
system, the system may cause personal injury. In this case, if the IPA function is not configured,
this alarm is reported prompting the user to configure the IPA function.
Attribute
Alarm Severity
Alarm Type
Critical
Environment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the work band. 0x01 indicates the C-Band and 0x02 indicates the LBand.

This alarm does not affect services; however, it might cause personal injury.
Possible Causes
l
The laser power is high and the IPA protection is not configured.
The laser power is high; although the IPA function has been configured, it is disabled.
Procedure
Step 1 Check the IPA configuration on the NE. For details, see "Creating IPA" in the Feature
Description. Check the IPA configuration for a Raman system, see "Creating IPA for a Raman
System" in the Feature Description.
Step 2 If the NE is not configured with the IPA function, follow the network plan to create the IPA
protection. For details, see "Creating IPA" in the Feature Description. To create IPA protection
for a Raman system, see "Creating IPA for a Raman System" in the Feature Description.
Step 3 If the NE is configured with the IPA function, enable the IPA function. For details, see "Enabling
IPA" in the Feature Description. To enable the IPA function for a Raman system, see " Enabling
the IPA in a Raman System" in the Feature Description.
Issue 02 (2011-10-31)

507
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 After the IPA function is configured and enabled, the alarm is cleared automatically. If the alarm
persists, contact Huawei for help.
----End
Related Information
The system provides the intelligent power adjustment (IPA) function. For details, see "Intelligent
Power Adjustment (IPA)" in the Feature Description.
The power of the pump light from Raman amplifiers is very high. For details, see "Intelligent
Power Adjustment (IPA) of Raman System" in the Feature Description.
4.94 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Alarm Severity
Alarm Type
Major
Security alarm
Parameters
None

When the LASER_SHUT alarm is generated, the services are interrupted.
Possible Causes
The user uses the U2000 or Navigator to perform the operation to shut down the laser.
Procedure
Step 1 If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is automatically
cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

508
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.95 LCS_DAYS_OF_GRACE
Description
License in keepalive period. The LCS_DAYS_OF_GRACE is an alarm indicating the license
has expired and is within the keepalive period of 60 days.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Name
Meaning
Parameters 1 and 2 l 0x00 0x00 indicate file level alarm.

l Other values indicate control-item ID.
Parameters 3 and 4 Indicate days.
Parameter 5
l 0x00 indicates that the license or control-item expire naturally.

l 0x01 indicates that the license has been revoked.
l 0x02 indicates ESN mismatching.
l 0x03 indicates V/R mismatching.
l 0x04 indicates ESN and V/R mismatching.
When Parameter 1 and Parameter 2 are of other values, the value of
Parameter 5 is 0x00.

When the license has expired but is still within the keepalive period of 60 days, the system
functions are not affected, but this alarm is reported every day, reminding the user of updating
the license.
Possible Causes
l
Issue 02 (2011-10-31)
The license file fails. The system is in the trial state and within the keepalive period of 60
days.
509
OptiX OSN 8800/6800/3800

4 Alarm Processing
The license file does not match ESN or V/R version. The system is in trial state and within
the keepalive period of 60 days.
The license-controlled items exceed the expiry date but is within the keepalive period of
60 days.
Procedure
Step 1 Load a license file to the system.
----End
Related Information
None
4.96 LCS_EXPIRED
Description
License expired. The LCS_EXPIRED is an alarm indicating the license has expired and the
keepalive period of 60 days has also elapsed.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
table.
Name
Meaning
Parameters 1 and 2
Indicate days.
Parameter 3
l 0x01 indicate license having been revoked.

l 0x02 indicate ESN mismatching.
l 0x03 indicate V/R mismatching.
l 0x04 indicate ESN and V/R mismatching.

When the license has expired and the keepalive period of 60 days has also elapsed, only the
default functions of the system are available.
Issue 02 (2011-10-31)

510
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The license of the system has expired and the keepalive period of 60 days has also elapsed.
The system license file does not match the ESN or V/R version, and the keepalive period
of 60 days has elapsed.
Procedure
----End
Related Information
None
4.97 LCS_FILE_NOT_EXIST
Description
No license file. The LCS_FILE_NOT_EXIST is an alarm indicating the system is under license
control but a license file is not loaded onto the system.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

If a license file is not installed, only the default functions of the system are available.
Possible Causes
When starting up, the system does not find a license file, which is essential for the system to
run.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

511
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.98 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction.
When the sink end of the LCAS module detects anomalies, the LCAS negotiation is unavailable
or incorrect and this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
None

When the LCAS_FOPR alarm is generated, it indicates that the protocol state machine in the
receive direction is in confusion. The negotiation may be abnormal.
Possible Causes
The possible causes of the LCAS_FOPR alarm are as follows:
l
The downstream VCG receives repeated sequence numbers due to incorrect configurations
or link bit errors.
The LCAS function of the opposite VCG is disabled.
The downstream VCG simultaneously receives the FIXED and other LCAS control bytes
due to incorrect configurations or link bit errors.
The cross-connection is incorrectly bound.
Procedure
Step 1 View the LCAS_FOPR alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS protocol is enabled at the opposite end. If not, enable the LCAS
protocol at the opposite end. Check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the configurations are correct. Especially, check whether
the cross-connection is bound correctly. If not, modify the incorrect configurations. Check
Step 4 If the alarm persists, disable and then enable the LCAS function at both ends. Check whether
----End
Issue 02 (2011-10-31)

512
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.99 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the failure of the LCAS protocol in the transmit
direction. When the source end of the LCAS module detects anomalies, the LCAS negotiation
is unavailable or incorrect and this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Major
Processing alarm
Parameters
None

When the LCAS_FOPT alarm is generated, it indicates that the protocol state machine in the
transmit direction is in confusion. The negotiation may be abnormal.
Possible Causes
There is the persistent and unexpected MST due to incorrect configurations or link bit errors.
For example, the member that transmits IDLE always receives MST=OK.
Procedure
Step 1 View the LCAS_FOPT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the service cross-connection of the VCTRUNK is bound correctly. If not, modify
the incorrect configurations. Check whether the alarm is cleared.
----End
Related Information
None
4.100 LCAS_PLCR
Issue 02 (2011-10-31)

513
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The LCAS_PLCR is an alarm indicating partial unavailability of the bandwidth in the LCAS
receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive
direction, the number of paths that carry load is less than the number of paths configured and is
not zero.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the LCAS_PLCR alarm is generated, it indicates that the available bandwidth in the
receive direction is reduced. The services are not interrupted.
Possible Causes
The possible causes of the LCAS_PLCR alarm are as follows:
l
Bidirectional services are not configured.
The number of members in the upstream of the opposite end is less than that in the
downstream of the local end.
The path communication fails because the cross-connection is incorrect or the physical link
is improperly connected.
Procedure
Step 1 Check whether there are other alarms such as AIS, LOP, UNEQ, and LOM. If yes, clear these
alarms first. Then, check whether the alarm is cleared.
Step 2 Ensure that the physical link is available. Check whether bidirectional services are configured.
If not, configure bidirectional services.
Step 3 If the alarm persists, check on the U2000 whether the number of downstream timeslots bound
with the VCTRUNK at the local end is consistent with that of upstream timeslots bound with
the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number
of the timeslots at both ends consistent. Check whether the alarm is cleared.
Step 4 Check whether the cross-connection is bound from the transmit direction to the opposite end. If
not, re-bind the cross-connection. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the
members are still not restored. Then, check the WTR time. Wait for a period, and then check
Issue 02 (2011-10-31)

514
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Then, check
Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Then,
check whether the alarm is cleared.
Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
CAUTION
interrupted after cold reset of the board.
----End
Related Information
None
4.101 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating partial loss of unavailability of the bandwidth in the
LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit
direction, the number of paths that carry load is less than the number of paths configured and is
not zero.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

When the LCAS_PLCT alarm is generated, it indicates that the available bandwidth in the
transmit direction is reduced. The services will lose packets when the actual service traffic is
larger than the available bandwidth in the transmit direction.
Possible Causes
The possible causes of the LCAS_PLCT alarm are as follows:
Issue 02 (2011-10-31)

515
OptiX OSN 8800/6800/3800

4 Alarm Processing
The number of members in the downstream of the opposite end is less than that in the
upstream of the local end.
The path communication fails because the cross-connection is incorrect or the physical link
is improperly connected.
Procedure
Step 1 View the LCAS_PLCT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS_PLCR alarm is present at the opposite station. If yes, clear the
LCAS_PLCR alarm first. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, check whether bidirectional services are configured. If not, configure
bidirectional services. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check on the U2000 whether the number of upstream timeslots bound with
the VCTRUNK at the local end is consistent with that of downstream timeslots bound with the
VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of
the timeslots at both ends consistent. Check whether the alarm is cleared.
Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the opposite
end. Re-bind the cross-connection. The alarm is automatically cleared.
Step 6 If the alarm persists, the wait-to-restore (WTR) time may be excessively long and thus the
members are still not restored. Check the WTR time. Wait for a period, and then check whether
Step 9 If the alarm persists, perform cold reset on the board.
CAUTION
----End
Related Information
None
4.102 LCAS_TLCR
Issue 02 (2011-10-31)

516
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The LCAS_TLCR is an alarm indicating the total loss of bandwidth in the LCAS receive
direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the
number of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the LCAS_TLCR alarm is generated, it indicates that the available bandwidth in the
receive direction is reduced to zero. The services in the receive direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCR alarm are as follows:
l
The upstream of the opposite end is not bound with members.
The path communication fails because the cross-connection is incorrect or other alarms are
present.
Procedure
Step 1 View the LCAS_TLCR alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear
these alarms first. Then, check whether the alarm is cleared.
Step 3 Check whether bidirectional services are configured. If not, configure bidirectional services.
Step 4 If the alarm persists, check whether the upstream of the opposite end is bound with timeslots. If
not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the local
end. Re-bind the cross-connection. The alarm is automatically cleared.
Step 8 If the alarm persists, perform cold reset on the board, or remove and insert the board.
Issue 02 (2011-10-31)

517
OptiX OSN 8800/6800/3800

4 Alarm Processing
CAUTION
----End
Related Information
None
4.103 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating total loss of bandwidth in the LCAS transmit direction.
When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number
of paths that carry load is zero, whereas the number of paths configured is not zero.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the LCAS_TLCT alarm is generated, it indicates that the available bandwidth in the
transmit direction is reduced to zero. The services in the transmit direction are interrupted.
Possible Causes
The possible causes of the LCAS_TLCT alarm are as follows:
l
The downstream of the opposite end is not bound with members.
The path communication fails because the cross-connection is correct or other alarms are
present.
Procedure
Step 1 View the LCAS_TLCT alarm on the U2000 and determine the relevant VCTRUNK.
Step 2 Check whether the LCAS_TLCR alarm is present at the opposite station. If yes, clear the
LCAS_TLCR alarm first. Then, check whether the alarm is cleared.
Issue 02 (2011-10-31)

518
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 3 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear
these alarms first. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the downstream of the opposite end is bound with timeslots.
If not, bind the timeslots in the corresponding direction. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check whether the cross-connection is correctly bound from the transmit
direction to the opposite end. If not, re-bind the cross-connection. Then, check whether the alarm
is cleared.
Step 8 If the alarm persists, perform cold reset on the board.
CAUTION
----End
Related Information
None
4.104 LOCAL_FAULT
Description
Local fault alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The 10GE services in the flow control mode are configured on the client side of the board
(TN11LSX). If the board receives the LOCAL_FAULT alarm, the received services may be
interrupted.
Issue 02 (2011-10-31)

519
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The input fiber on the client side is transiently cut.
The board receives various bit errors.
The input optical power on the client side is abnormal.
Procedure
Step 1 Check whether the attenuation of the fiber between the input equipment and the interface on the
client side of the board is overlarge, and whether the fiber is aged or loose. If that is the case,
clean the fiber connector or replace the fiber. For details, see the Supporting Tasks.
Step 2 Check whether the output optical power of the input equipment is within the normal range. If
the optical power is abnormal, remove the fault of the input equipment.
----End
Related Information
None
4.105 LOCK_CUR_FAIL
Description
The LOCK_CUR_FAIL is an alarm indicating that the pump drive currently unlocked. The
alarm occurs when the working current is abnormal.
Reporting side: NA
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the number of pump laser.
Issue 02 (2011-10-31)

520
OptiX OSN 8800/6800/3800

4 Alarm Processing

The locking of the output optical power of the board fails, which influences the services on the
entire optical line.
Possible Causes
Procedure
Tasks.
----End
Related Information
None
4.106 LOCKPOW_MIS
Description
The LOCKPOW_MIS is an alarm indicating mismatch of locked pump optical power. When
the locked pump optical power falls beyond the range of the locked pump optical power, the
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Possible Causes
Cause 1: As for the locked pump optical power of the Raman board, a value that falls beyond
the range of the locked pump optical power is set.
Issue 02 (2011-10-31)

521
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
Cause 1: A value that falls beyond the range of the locked pump optical power is set.
1.
Query the locked pump optical power of the corresponding optical interface channel
and reconfigure a valid value on the U2000.
----End
Related Information
None
4.107 LP_RDI_VC3
Description
The LP_RDI_VC3 is a remote defect indication in the VC-3 lower order path. If a board has
detected that bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI_VC3 alarm is
reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the LP_RDI_VC3 alarm is generated, the services at the local station are not affected.
This alarm just indicates that the services at the opposite end are interrupted.
Possible Causes
The LP_RDI_VC3 alarm is an accompanying alarm. When the relevant path of a tributary board
at the opposite station reports the TU_AIS_VC3 or TU_LOP_VC3 alarm, it returns the
LP_RDI_VC3 alarm to the local station, indicating that the TU_AIS_VC3 or TU_LOP_VC3
alarm is received at the opposite station.
Procedure
Step 1 After you clear the TU_AIS_VC3 or TU_LOP_VC3 alarm reported from the relevant path of a
tributary board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared.
----End
Issue 02 (2011-10-31)

522
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.108 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a signal label mismatch in the VC-3 lower order path.
If a board has detected that the signal label mismatch event occurs in the C2 byte, the
LP_SLM_VC3 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The system is not affected.
Possible Causes
The possible causes of the LP_SLM_VC3 alarm are as follows:
l
The type of the received signals does not match that of the signals to be received. That is,
the signal label byte C2 in the lower order path is inconsistent with the received C2 byte.
The service type is incorrectly configured.
Procedure
Step 1 View the LP_SLM_VC3 alarm on the U2000, and then determine the path number.
Step 2 Check whether the signal label byte in the lower order path of the tributary board at the opposite
station is consistent with that in the lower order path of the line board at the local station. If not,
modify it, and then check whether the LP_SLM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the service configuration of the path is correct. After
modifying the incorrect configuration, check whether the LP_SLM_VC3 alarm is cleared.
Step 4 If the alarm persists, replace the line board at the local station.
Step 5 If the alarm persists, replace the tributary board at the opposite station.
----End
Issue 02 (2011-10-31)

523
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.109 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that no payload is equipped in the VC-3 lower order
path. If a board has detected that the signal label in the C2 byte is 0, the LP_UNEQ_VC3 alarm
is reported.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The LP_UNEQ_VC3 alarm indicates that no path services are loaded. If the service
configuration is incorrect, and if the services on the PDH side are not accessed, the services may
be interrupted.
Possible Causes
The possible causes of the LP_UNEQ_VC3 alarm are as follows:
l
The service type is incorrectly configured.
The services on the PDH side are not accessed.
Procedure
Step 1 View the LP_UNEQ_VC3 alarm on the U2000, and then determine the path number.
Step 2 Check whether the service type configuration is correct. After modifying the incorrect
configuration and making sure that the services are correctly accessed on the PDH side, check
whether the LP_UNEQ_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the property configuration of the relevant tributary board is
correct. After you modify the incorrect configuration, the LP_UNEQ_VC3 alarm is
----End
Issue 02 (2011-10-31)

524
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.110 LPT_RFI
Description
The LPT_RFI is a remote failure indication alarm of link pass through (LPT). This alarm occurs
when the link pass through detects the failure of the remote port or the LPT service network.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

During the data transmission, when the LPT detects the failure of the remote port or the service
network, the link is unavailable and the services are interrupted. Moreover, the link backup is
triggered.
Possible Causes
The possible causes of the LPT_RFI alarm are as follows:
l
The remote port fails. For example, there is the LINK_ERR alarm, or the remote port is
disabled.
The LPT service network is faulty, including the following cases:

There is a fiber cut.
There are bit error threshold-crossing alarms such as B3_EXC.
There are alarms such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and
LP_UNEQ_VC3.
Procedure
Step 1 View the LPT_RFI alarm on the U2000 to determine the number of the port on the board that
reports the alarm according to Parameter 1.
Step 2 Based on the confirmed port number, check whether the opposite port is enabled. If yes, check
whether the LPT_RFI alarm is cleared.
Step 3 If the alarm persists, check whether there is the LINK_ERR alarm. If yes, after the LINK_ERR
alarm is cleared, check whether the LPT_RFI alarm is cleared.
Issue 02 (2011-10-31)

525
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 If the LPT_RFI alarm still persists, check whether the service network fails.
l If a fiber cut occurs, replace the fiber.
l If the bit error threshold-crossing alarms such as BIP_EXC and B3_EXC are detected, first
clear these alarms and then check whether the LPT_RFI alarm is cleared.
l Check whether there are alarms such as VCAT_LOA, VCATA_LOM_VC3,
VCAT_LOM_VC4, and LP_UNEQ_VC3. If yes, first clear these alarms and then check
whether the LPT_RFI alarm is cleared.
----End
Related Information
None
4.111 LSR_COOL_ALM
Description
The LSR_COOL_ALM is an alarm indicating that the cooling current of the laser crosses the
threshold. The alarm is generated when the cooling current of the laser on the WDM side exceeds
the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the cooling current of the laser exceeds the threshold, the optical module of the board
works abnormally. As a result, services cannot be transmitted or received normally.
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows:
l
The ambient temperature is excessively high.
The laser is faulty.
Issue 02 (2011-10-31)

526
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is excessively high. If yes, decrease it to a proper value
for the equipment to work well, and then check whether the LSR_COOL_ALM alarm is cleared.
Step 2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm. For
----End
Related Information
None
4.112 LSR_FORCE_OPEN
Description
The LSR_FORCE_OPEN is an alarm indicating that the laser is forced to be open.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The inconsistent operations may occur.
Possible Causes
The optical interface is set to Disabled but the status of the laser is On.
NOTE
For L4G board, if the laser is On when the port on the client side is set to be disabled, the alarm is generated.
Procedure
Step 1 Query whether the laser reporting the alarm needs to be used. If that is the case, set the status of
the laser to On on the U2000. If not, shut down the laser on the U2000.
----End
Related Information
None
Issue 02 (2011-10-31)

527
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.113 LSR_INVALID
Description
The LSR_INVALID is an alarm indicating an invalid optical module. It is generated when the
optical module cannot pass an authentication.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Parameter 1 Indicates the reason why the optical is invalid. 0x01 indicates that the optical
module has no license. 0x02 indicates that the license verification of the optical
module is incorrect.

The optical interface of the board cannot receive and transmit services. Services are interrupted.
Possible Causes
l
The optical module has no license.
A fault occurs during verifying the license of the optical module.
Procedure
Step 1 Replace the optical module with another one with a correct license, and then re-verify the license.
After successful verification, the alarm is cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

528
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.114 LTI
Description
The LTI is an alarm indicating the loss of synchronization source. This alarm is generated when
there are clock sources other than internal clock sources listed in the priority table but the board
operates in the holdover or free-run mode.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates which synchronization sources are lost.

l 0x01: All synchronization sources for the system clock are lost.
l 0x02: All synchronization sources for the first 2M phase-locked source are
lost.
l 0x03: All synchronization sources for the second 2M phase-locked source
are lost.

When the LTI alarm is generated, the NE clock is in an abnormal state. If the NE clock remains
in this abnormal state for a long time, the bit error rate and the pointer justifications may increase
due to the decreased clock quality.
Possible Causes
The possible causes of the LTI alarm are as follows:
l
Cause 1: There is a fiber cut or a cable cut.
Cause 2: There is no input from the external clock source.
Cause 3: The synchronization source is set as non-revertive or is locked.
Issue 02 (2011-10-31)

529
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
On the U2000, view the clock sources traced by the NE that reports the LTI alarm. The
clock sources include external clock sources, line clock sources, and tributary clock sources.
Cause 1: There is a fiber cut or a cable cut. Cause 4: The board is faulty.
1.
On the U2000, check whether the R_LOS, R_LOC, or R_LOF alarm occurs on the
relevant line board or tributary board. If yes, take priority to clear the alarm, and then
check whether the LTI alarm is cleared.
2.
If the alarm persists, perform cold reset on the relevant line board or tributary board.
After successful cold reset, check whether the LTI alarm is cleared. For details, see
Performing Cold Reset on a Board in the Supporting Tasks.
3.
If the alarm persists, replace the relevant line board or tributary board, and then check
whether the LTI alarm is cleared. For details, see Parts Replacement.
4.
If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
5.
Cause 2: There is no input from the external clock source. Cause 4: The board is faulty.
1.
Make sure that the external clock equipment properly transmits signals. Replace the
external clock equipment with a normal one, and then check whether the LTI alarm
is cleared.
2.
3.
If the alarm persists, check whether the clock input cable is correctly connected. After
ensuring the correct connection of the clock input cable, check whether the alarm is
cleared.
4.
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.
5.
Cause 3: The synchronization source is set as non-revertive or locked.

1.
On the U2000, check whether the synchronization source is set as non-revertive. If

yes, set the source as revertive. Then, check whether the alarm is cleared.
2.
On the U2000, check whether the synchronization source is set as locked. If yes, set
the source as unlocked. Then, check whether the alarm is cleared.
----End
Related Information
Issue 02 (2011-10-31)

530
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.115 MAINBD_SUBBD_MISMATCH
Description
This alarm is generated when the board where services are processed mismatches the board
where services are output in a PID group.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The board where services are output does not support the board where services are processed,
and therefore the board where services are processed is unavailable.
Possible Causes
The board where services are output does not support the board where services are processed.
However, the board where services are processed is housed in the corresponding slot.
Procedure
Step 1 Determine whether the board where the services are processed is required.
Step 2 If the board where the services are processed is required, replace the board where services are
output with a board that supports the board where services are processed.
Step 3 If the board where services are processed is not required, remove it from the corresponding slot.
----End
Related Information
For OptiX OSN 6800, see "PID" in the Feature Description.
For OptiX OSN 8800, see "PID" in the Feature Description.
Issue 02 (2011-10-31)

531
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.116 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that the module communication is abnormal. The
alarm is generated when the communication of the CPU and other internal modules of the board
is abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Because the communication between the CPU and the optical module is abnormal, the optical
module cannot be managed by the U2000 and the information about the optical module cannot
be queried.
Possible Causes
l
The board is in poor contact with the connector of the optical module.
The software processing of the related modules of the board is faulty.
Procedure
Step 1 Check the connection between the board and optical module, and re-connect the board and
optical module.
Step 2 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert
it again. For details, see the Supporting Tasks.
Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board. For
----End
Related Information
None
Issue 02 (2011-10-31)

532
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.117 MODULE_ADJUST_FAIL
Description
The MODULE_ADJUST_FAIL is an alarm indicating that adjustment of the optical module
fails.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Parameter 1 Indicates the type of the component in which the alarm is generated. For example,
0x01 indicates that the VOA adjustment fails. 0x02 indicates that the optical
switch adjustment fails.

The adjustment of the VOA or optical switch of the optical module fails, which leads to the
failure of issuing a command.
Possible Causes
l
The temperature of the optical module is excessively high.
The optical module of the board is faulty.
Procedure
Step 1 Check whether the board temperature exceeds the threshold, and whether the TEM_HA and
TEMP_OVER alarm exist. If that is the case, handle the alarms according to the corresponding
Step 2 Deliver the configuration again. If the alarm persists, the adjusted range of the optical module
exceeds the threshold. Perform warm reset on the board. For details, see the Supporting Tasks.
Step 3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts
Replacement.
----End
Issue 02 (2011-10-31)

533
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.118 MODULE_COOLCUR_OVER
Description
The MODULE_COOLCUR_OVER is an alarm indicating that the module cooling current
exceeds the threshold. The alarm occurs when the cooling current of the module is higher than
the upper threshold or lower than the lower threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter 1 Indicates the threshold crossing type. For example, 0x01 indicates that the upper
threshold is exceeded and 0x02 indicates that the lower threshold is exceeded.

The working performance and the reliability of the module are affected. Generally the QoS is
not affected. However, the QoS is affected if the alarm exists for a long time. The alarm should
be handled in time.
Possible Causes
l
The temperature of the optical module is excessively high.
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific
boards, see the Product Description. If the ambient temperature is excessively high, handle the
alarm according to the handling procedure of the TEMP_OVER alarm.
Issue 02 (2011-10-31)

534
OptiX OSN 8800/6800/3800

4 Alarm Processing
----End
Related Information
None
4.119 MODULE_TEMP_OVER
Description
The MODULE_TEMP_OVER is an alarm indicating that the module temperature exceeds the
threshold. The alarm is generated when the temperature of the module is higher than the upper
threshold or lower than the lower threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter 1 Indicates the threshold crossing type. 0x01 indicates that the upper threshold is
exceeded and 0x02 indicates that the lower threshold is exceeded.

Because the temperature of the optical module exceeds the threshold, the working performance
and reliability of the optical module are affected. As a result, services are affected. The alarm
should be handled in time.
Possible Causes
l
The ambient temperature of the board is excessively high or excessively low.
Issue 02 (2011-10-31)

535
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check the ambient temperature of the board. For ambient temperature specifications of specific
boards, see the Product Description. If the ambient temperature is excessively high or
excessively low, handle the alarm according to the handling procedure of the TEMP_OVER
alarm.
Step 2 If the alarm persists, the board at the local station may be faulty. Perform a cold reset on the
faulty board through the U2000
----End
Related Information
None
4.120 MODULEFILE_UPDATE_FAIL
Description
The MODULEFILE_UPDATE_FAIL is an alarm indicating that updating the microprogram
and laser parameter table fails. The alarm occurs when the in-service upgrade of the
microprogram of the optical module and the parameter table on the U2000 fails.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
table.
Parameter 1 Indicates the type of the software that generates the alarm. 0x01 indicates the
microprogram and 0x02 denotes the parameter table.

l
The upgrade of the microprogram of the optical module fails. The new microprogram of
the optical module is unavailable and the old one is still used.
The upgrade of the parameter table of the laser fails.
Issue 02 (2011-10-31)

536
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The upgrade of the microprogram of the optical module and the parameter table of the laser fails.
Procedure
Step 1 Check whether the upgraded microprogram of the optical module and the parameter table of the
laser are correct.
Step 2 Upgrade the microprogram of the optical module and the parameter table of the laser again.
Step 3 If the alarm persists, replace the faulty optical module or board. For details, see the Parts
Replacement.
----End
Related Information
None
4.121 MS_CROSSTR
Description
Multiplex section performance exceeds the threshold. The alarm is generated when the
performance module reports the threshold crossing of the performance events in the multiplex
section.
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l
The laser of the board in the opposite station is degraded.
The input optical power of the board at the local station is too high or too low.
The clock in the opposite station is degraded.
The fiber is degraded.
Issue 02 (2011-10-31)

537
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the fiber is aging or has excessive attenuation. If that is the case, remove the fault
of the fiber.
Step 2 Query whether the board has the B1_EXC, B2_EXC, B1_SD or B2_SD alarms by using the
U2000. If that is the case, clear the alarms.
Step 3 Check whether the input optical power of the board at the local station is within the normal range
by using the U2000. For the optical power specifications of the specific board, see the Product
Description.
l
If the optical power displayed on the U2000 is normal, the board might be faulty. Replace
the faulty board. For details, see the Parts Replacement.
If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
be within the normal range.
Step 4 If the alarm persists, remove the fault of the board in the opposite station.
----End
Related Information
None
4.122 MS_REI
Description
The MS_REI is an alarm that indicates that bit errors occur at the remote end of the multiplex
section (MS). When the receive side of the local optical station receives the M1 byte, which
indicates that the number of block bit errors detected by BIP-Nx24 (B2) at the opposite station,
the MS_REI alarm is reported.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

When the MS_REI alarm is generated, the number of B2 bit errors received at the opposite
station is beyond the specified range. The services at the local station are not affected, but the
service quality at the opposite station is degraded.
Issue 02 (2011-10-31)

538
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The number of B2 bit errors received at the opposite station is beyond the specified range.
Procedure
Step 1 After you clear the B2_EXC or B2_SD alarm that occurs at the opposite station, the MS_REI
alarm is automatically cleared.
----End
Related Information
None
4.123 MS_SNCP_PS
Description
The MS_SNCP_PS is an alarm indicating the MS SNCP protection switching. This alarm occurs
when the MS SNCP protection group actuates switching in which the current channel switches
Reporting side: NA
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the MS SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the MS SNCP protection group might have
faulty services that need to be restored.
Possible Causes
l
switching. Such a command makes the current channel of the MS SNCP protection group
Cause 2: The services of the working channel of the MS SNCP protection group are faulty.
reported.
Issue 02 (2011-10-31)

539
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 On the U2000, query the switching state of the protection group. If the switching state is forced
switching or manual switching, check whether the external switching operation is necessary,
1.
2.
If the external switching operation is unnecessary, issue an external command to switch

the current channel to the working channel, thus clearing the alarm.
Step 2 If the alarm is generated due to the automatic switching of the protection group,
1.
Query whether the related boards for configuring the protection group have alarms relevant
to the services, such as B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK,
ODUk_PM_OCI, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
REM_SF, and REM_SD. If yes, handle the alarms by referring to the corresponding alarm
2.
If the alarm persists, check whether the attribute of the protection group is Revertive. If
yes, the current channel automatically switches to the working channel and the alarm clears.
If the attribute is Non-Revertive, set it to Revertive and the alarm clears.
----End
Related Information
For details, see "MS SNCP Protection" in the Feature Description.
4.124 MS_SNCP_STA_INDI
Description
The MS_SNCP_STA_INDI is an alarm indicating the MS SNCP protection switching. This
alarm is reported when the working or protection channel of the protection group is faulty or the
user runs an external switching command.
Reporting side: NA
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Issue 02 (2011-10-31)

540
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameters 1

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l
When switching is performed in the MS SNCP group, the services may be transiently
interrupted.
When the alarm is reported, the working or protection channel of the MS SNCP group may
have faulty services that need to be restored.
Possible Causes
l
The user issues an external switching command such as forced switching, manual
switching, or locked switching.
The services of the working or protection channel of the MS SNCP group are faulty.
The switching is set to WTR State. After the WTR time, the alarm is cleared.
Procedure
switching, manual switching or locked switching, check whether the external switching is
necessary,
1.
If the external switching is necessary, ignore the alarm.
2.
If the external switching is unnecessary, issue a switching clearing command to clear the
external switching.
Step 2 If the alarm is generated due to the fault of the working or protection channel of the protection
group, do as follows:
1.
Query whether the related boards for configuring the protection group have alarms such as
B1_EXC, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_LOFLOM, ODUk_PM_AIS, ODUk_PM_LCK, ODUk_PM_OCI,
OTUk_DEG, OTUk_EXC, ODUk_PM_DEG, ODUk_PM_EXC, REM_SF, and
REM_SD. If that is the case, handle the alarms according to the corresponding handling
procedure of the alarms to restore the services of the working or protection channel.
2.
that is the case, the services in the working channel automatically switch to the working
channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the
alarm is cleared.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the WTR
state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Issue 02 (2011-10-31)

541
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
For details, see "MS SNCP Protection" in the Feature Description.
4.125 MS_APS_INDI_EX
Description
The MS_APS_INDI_EX is an extended indication alarm of the MSP switching state. The alarm
occurs when the multiplex section switching causes the switching of services.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the type of the MSP group in which protection switching

occurs:
Parameter 2, Parameter 3 Indicates the MSP group ID.

l Linear MSP: The parameter value ranges from 0x01 to 0xFF
(1-255).
l Ring MSP: The parameter value ranges from 0x01 to 0x90
(1-144).
Parameter 4
Indicates the slot ID of the board where the protection switching

occurs.
Parameter 5
Indicates the number of the optical interface where the protection

switching occurs.
Issue 02 (2011-10-31)

542
OptiX OSN 8800/6800/3800

4 Alarm Processing

If a fiber cut or another fault occurs after the MS_APS_INDI_EX alarm is generated, the services
are interrupted.
Possible Causes
The possible causes of the MS_APS_INDI_EX alarm are as follows:
l
An external switching command is issued.
There is a fiber cut.
Procedure
Step 1 View the MS_APS_INDI_EX alarm on the U2000. According to the alarm parameters,
determine the slot ID and optical interface number related to the board where the protection
switching occurs.
Step 2 Check whether the MSP is in the state of manual switching, forced switching, or locked
switching. If yes, clear the switching, and then the alarm is automatically cleared.
Step 3 If the MSP is in the automatic switching state, do as follows:
1.
Make sure that the fibers connected to the service board configured with the MSP are not
cut. Fix the broken fibers and then check whether the alarm is cleared.
2.
Make sure that the service board configured with the MSP is not faulty. Replace the relevant
service board and then check whether the alarm is cleared.
3.
Make sure that the cross-connect board configured with the MSP is not faulty. Replace the
relevant cross-connect board and then check whether the alarm is cleared.
----End
Related Information
After the services are switched in the 1+1 single-ended non-revertive linear multiplex section,
the services are not automatically switched back to the working channel if the optical channel
is recovered, and the MS_APS_INDI_EX alarm persists. In this case, the services need to be
manually switched from the protection channel to the working channel. The MS_APS_INDI_EX
alarm can be cleared only after successful switching.
4.126 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that there is more than one RPL OWNER
node on the ring.
Issue 02 (2011-10-31)

543
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

There is no connection between all the nodes on the ring. If certain services are configured, the
services may be interrupted.
Possible Causes
The ERPS protocol requires that the configuration of every node on a ring should be managed
and one RPL OWNER should exist on each ring. Therefore, the alarm is generated when more
than one RPL OWNER node is configured in a ring.
Procedure
Step 1 Check whether the node ID in all the received NR and RB packets is consistent with the ID of
the local node. If yes, proceed with the next step.
Step 2 Start the timer whose time is three times of the transmitting period (15s) of the packets. The
aging of the timer indicates the end of the alarm.
----End
Related Information
None
4.127 NEBD_XC_DIF
Description
The NEBD_XC_DIF is an alarm indicating that the cross-connect matrix data of the NE and
board is different. For the board supporting service cross-connection, the alarm occurs when the
cross-connection data stored on the SCC is not consistent with that stored on the board.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Issue 02 (2011-10-31)

544
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
table.
Parameter
Description
Parameter 1 and Parameters 2 Indicates the slot ID.

Parameters 3
Indicates the cross-connect type. For example:

0x3 indicates inconsistent space division cross-connections.

Services are interrupted during service grooming or perform warm reset on the board.
Possible Causes
l
Cause 1: The cross-connection data of the board is incorrect.
Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
Query the alarm on the U2000. Record the slot ID of the board that reports the alarm.
Cause 1: The cross-connection data of the board is incorrect.
Procedure
1.
l
Re-configure the cross-connection data on the U2000. For details, refer to the
Configuration Guide.
Cause 2: The cross-connection data stored on the board is different from that on the SCC
board.
1.
If the alarm persists, perform a warm reset on the board related to service crossconnections on the U2000.
2.
If the alarm persists, perform warm reset on the SCC on the U2000. For details, refer
to "Replacing a Board" of the Supporting Tasks.
----End
Related Information
None
Issue 02 (2011-10-31)

545
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.128 NESF_LOST
Description
The NESF_LOST is an alarm indicating absence of NE software. The alarm occurs when the
NE software on the SCC board does not exist.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

If the two sets of NE software do not exist, and thus the board cannot work normally and the
U2000 cannot monitor the NE after the reset or power-off restart of the SCC.
Possible Causes
The NE software is not reloaded after the NE software of the SCC board is erased.
Procedure
Step 1 Reload the NE software of the SCC according to the Version Upgrade Guide.
----End
Related Information
None
4.129 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in installation state and is not
configured. The alarm occurs when the NE is in the initial installation state.
Issue 02 (2011-10-31)

546
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

l
The U2000 cannot query all configuration information about the NE.
If the alarm is generated by the NE that is in the normal running state, the data of the
U2000 is initialized. You need to deliver the correct configuration in time.
Possible Causes
l
The NE is in the initial installation state.
The normal configuration is not delivered to the NE after the NE is initialized.
Procedure
Step 1 Deliver the configuration information to the board by using the U2000.
----End
Related Information
None
4.130 NO_BD_PARA
Description
The NO_BD_PARR is an alarm indicating absence of the board parameter table. The alarm
occurs when the board does not have the parameter table.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

547
OptiX OSN 8800/6800/3800

4 Alarm Processing

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l
The correct parameter table is not loaded before delivery.
The incorrect parameter table file is loaded on site, which overlaps the original file.
The parameter table file is abnormally lost in the running process.
Procedure
Tasks.
----End
Related Information
None
4.131 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating absence of board software. The alarm occurs when
the board does not have the necessary files, such as loading software and logic software.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the fault type. For example, 0x01 indicates that the file is lost
and 0x02 indicates that the file verification fails.
Issue 02 (2011-10-31)

548
OptiX OSN 8800/6800/3800

Parameter
4 Alarm Processing
Description
Parameters 2 and 3 Indicates the ID of the lost file. For example,

l 0x00 0x01 indicates that the software of the working board is lost.
l 0x00 0x02 indicates that the software of the protection board is lost.
l 0x00 0x03 indicates that the active FPGA file is lost.
l 0x00 0x04 indicates that the standby FPGA file is lost.
l 0x00 0x05 indicates that the active ini file is lost.
l 0x00 0x06 indicates that the standby ini file is lost.
l 0x00 0x07 indicates that the active large logic file is lost.
l 0x00 0x08 indicates that the standby large logic file is lost.
l 0x00 0x0b indicates that the oa.cfg file is lost.
l 0x00 0x0d indicates that the oxudsp.par file is lost.

The alarm affects the system as follows:
l
If the board that reports the alarm is not reset, the services and functions of the board are
not affected.
If the board that reports the alarm is reset, the board may fail to start.
Possible Causes
l
Parts of the software are not loaded to the board.
The software on the board is abnormally lost in the running process.
The internal detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software through the U2000.
Tasks.
----End
Related Information
None
Issue 02 (2011-10-31)

549
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.132 NO_ELABEL
Description
The NO_ELABEL is an alarm indicating that the electronic label is unloaded. The alarm is
generated when the electronic label of board is lost or not loaded.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the carrier type of the electronic label. For Example, 0x01
indicates the mother board, 0x02 indicates the sub-board and 0x03
indicates the optical module.
Parameters 2 and 3 Indicates the carrier ID.

None
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 1 Replace the board. For details, see the Parts Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

550
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.133 NODEID_MM
Description
The NODEID_MM is an alarm indicating a mismatch of the MSP node ID. This alarm is
generated when the configured ID of an MSP node on the MS ring mismatches the actual node
ID.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
table.
Name
Meaning
Parameter 1 and Parameter 2 Indicates the ID of the MSP group in which the NODEID_MM
alarm is generated.

When the NODEID_MM alarm is generated, the MSP switching fails. If the squelching is
enabled, the squelching function fails.
Possible Causes
The east and west node IDs configured for each node on the MSP ring do not match.
Procedure
Step 1 View the NODEID_MM alarm on the U2000, and then determine the relevant MSP group ID.
Step 2 Check whether the configuration of the MSP data meets the following requirements. If not, reconfigure the MSP according to the following requirements:
l The node IDs configured for any two NEs are not repeated.
l If node A is in the west of its adjacent node B, the local node ID of node A must be the same
as the west node ID of node B, and the local node ID of node B must be the same as the east
node ID of node A.
Step 3 Restart the MSP protocol, and the alarm is cleared automatically.
----End
Issue 02 (2011-10-31)

551
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.134 NTP_SYNC_FAIL
Description
NTP synchronization failure. This alarm indicates that the NE is in the unsync state. The alarm
is cleared when the NTP turns into the sync state.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The NTP synchronization failure leads to unsynchronous NE time. As a result, the time of NE
performance events, alarms, and operation records is incorrect.
Possible Causes
l
The NTP server is not configured correctly.
The NE fails to connect to the NTP server or the connection is interrupted.
The NTP server stops unexpectedly.
Procedure
Step 1 Check whether the NTP server is configured correctly.
Step 2 Check whether the DCN is normal.
Step 3 Check whether the NTP server works properly.
----End
Related Information
None
Issue 02 (2011-10-31)

552
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.135 NULL_SEND
Description
The NULL_SEND is an alarm indicating that the NULL signals (the payload is all "0"s) are sent
out. When the NULL mapping status of the board is enabled, the NULL_SEND alarm is
generated, prompting the users that the NULL signals are being sent out.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
None

When this alarm is generated, it indicates that the board that reports the alarm is sending out the
NULL signals and the opposite station receives the NULL signals. Hence, services are
interrupted.
Possible Causes
The NULL Mapping Status parameter of the board is set to Enabled.
Procedure
Step 1 Check the NULL mapping status of the board that reports the alarm. If the NULL mapping status
is enabled, change the value from Enabled to Disabled.
NOTE
If the NULL mapping status needs to be enabled in the actual situation, suppress the alarm and then disable
the NULL mapping status. After that, configure the NULL_SEND alarm to be monitored.
----End
Related Information
None
Issue 02 (2011-10-31)

553
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.136 OCH_FDI
Description
The OCH_FDI is an alarm indicating a forward defect at the OCh layer. When the OCH_FDIP and OCH_FDI-O alarms coexist, this alarm is generated. At the same time, the OCH_FDI-P
and OCH_FDI-O alarms are suppressed.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services
may be interrupted.
Possible Causes
The OCH_FDI-P and OCH_FDI-O alarms coexist.
Procedure
Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection. If not,
modify the logical fiber connection to make it consistent with the actual fiber connection.
Step 2 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-O, or
OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the OTS_LOS,
OTS_TIM, OTS_LOS-O, or OMS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.137 OCH_FDI-O
Description
The OCH_FDI-O is an alarm indicating a forward defect (overhead) at the OCh layer. The
OCH_FDI-O signal is inserted to the downstream station when the board at the OTS layer detects
Issue 02 (2011-10-31)

554
OptiX OSN 8800/6800/3800

4 Alarm Processing
the OTS_LOS-O signal and the alarm is generated when the downstream station receives the
signal.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, there may
be an impact on the system monitoring and management.
Possible Causes
l
The logical fiber connection is not consistent with the actual fiber connection.
The OCh layer receives the FDI-O overhead signal from the OCH layer, when the OMS
layer loses overhead signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-O alarm by following proper handling
procedures.
----End
Related Information
None
4.138 OCH_FDI-P
Description
The OCH_FDI-P is an alarm indicating a forward defect indication (payload) at the OCh layer.
The OCH_FDI-P signal is inserted to the downstream station when the board at the OMS layer
detects payload LOS signals and the alarm is generated when the downstream station receives
the signals.
Issue 02 (2011-10-31)

555
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise the services
are interrupted.
Possible Causes
l
The OCh layer receives the FDI-O overhead signal from the OCh layer, when the OMS
layer loses payload signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 If the alarm persists, check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm
by following proper handling procedures.
----End
Related Information
None
4.139 OCH_LOS-P
Description
The OCH_LOS-P is an alarm indicating loss of signal (payload) at the OCh layer. When the
OTU detects LOS alarms and there is no OTS_LOS-P, OMS_LOS-P, or OMS_SSF-P alarm at
the upper OMS and OTS layers, the OCH_LOS-P alarm is reported.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Issue 02 (2011-10-31)

556
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

If the logical fiber connection is incorrect, there is no impact on services. Otherwise, the services
are interrupted.
Possible Causes
l
The board detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.
Procedure
Step 2 Confirm that the fiber connection between the OTU board that reports this alarm and the
DEMUX board is correct.
Step 3 If the alarm persists, check whether the output optical power at the OUT interface of the OTU
board at the opposite or upstream station is normal. If not, clear the alarm according to the
procedure to handle the IN_PWR_HIGH or IN_PWR_LOW alarm to make the output optical
power normal.
Step 4 If the alarm persists, check whether the fiber at the OUT interface of the OTU board at the
opposite or upstream station is disconnected from the MUX board. If yes, correctly connect the
fiber between the two boards.
Step 5 If the alarm persists, check whether the dispersion of the fiber is compliant with the requirement.
For specifications of the dispersion, see the Product Description. If not, connect a suitable
dispersion compensation module according to the Troubleshooting.
Step 6 Check whether there is the R_LOS alarm.
l
If yes, clear the alarm according to the handling procedure of R_LOS.
If not, replace the faulty board according to the Parts Replacement.
----End
Related Information
None
4.140 OCH_OCI
Description
The OCH_OCI is an alarm indicating an open connection at the OCh layer. No optical crossconnections are configured on the upstream service link, or no logical fiber connection is
configured from the OTU board to the MUX board. In this case, the OCI signal is inserted to
Issue 02 (2011-10-31)

557
OptiX OSN 8800/6800/3800

4 Alarm Processing
the downstream service link. After receiving the OCI signal, the optical termination node in the
downstream reports the OCH_OCI alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

are interrupted.
Possible Causes
l
No optical cross-connection for services to the local station is configured at the upstream
station.
Procedure
Step 2 Check whether the services of the optical cross-connections at the upstream station are
configured. If not, re-configure the optical cross-connections to ensure the normal transmission
of the services.
----End
Related Information
None
4.141 OCH_SSF
Description
The OCH_SSF is an alarm indicating that the server signal fails at the OCh layer. When the
OCH_SSF-P and OCH_SSF-O alarms coexist, this alarm is generated. At the same time, the
OCH_SSF-P and OCH_SSF-O alarms are suppressed.
Issue 02 (2011-10-31)

558
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

are interrupted.
Possible Causes
l
The OTS-LOS alarm at the upper OTS layer or the OMS-LOS alarm at the OMS layer is
generated.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOSP alarm on the FIU connected to the local board, If yes, clear the OTS_LOS, OTS_TIM,
OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOSO, or OMS_LOS-P alarm at the opposite station and all upstream stations. If yes, clear the
OTS_LOS, OTS_TIM, OTS_LOS-P, OTS_LOS-O, or OMS_LOS-P alarm by following the
proper handling procedures.
----End
Related Information
None
4.142 OCH_SSF-O
Description
The OCH_SSF-O is an alarm indicating that server signal (overhead) fails at the OCh layer.
When the OMS layer detects the lost of the overhead signals, this alarm is generated.
Issue 02 (2011-10-31)

559
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
l
The OCh layer receives the SSF-O overhead signal from the OMS layer, when the OTS
layer loses overhead signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated.
Procedure
Step 2 Check whether there is the OTS_LOS-O alarm on the FIU connected to the local board. If yes,
clear the OTS_LOS-O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether there is the OTS_LOS-O alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-O alarm by following proper handling
procedure.
----End
Related Information
None
4.143 OCH_SSF-P
Description
The OCH_SSF-P is an alarm indicating that the server signal (payload) fails at the OCh layer.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Issue 02 (2011-10-31)

560
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

Possible Causes
The OCh layer receives the SSF-P overhead signal from the OMS layer, when the OMS layer
loses payload signals because of a fiber cut, low optical power, or dispersion. This alarm is
generated.
Procedure
Step 2 Check whether there is the OTS_LOS-P or OMS_LOS-P alarm on the FIU connected to the
local board. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm by following proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm
----End
Related Information
None
4.144 ODU_AIS
Description
The ODU_AIS is an ODU alarm indication.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

561
OptiX OSN 8800/6800/3800

4 Alarm Processing

When the ODU_AIS alarm is generated, the entire ODU path is unavailable.
Possible Causes
The possible causes of the ODU_AIS alarm are as follows:
l
Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF,
and OTU_AIS.
The upstream services are faulty.
This board is faulty.
Procedure
Step 1 Check on the U2000 whether the alarms of higher levels such as R_LOS, FEC_LOF, OTU_LOF.
and OTU_AIS exist at the local station. If yes, clear these alarms and then check whether the
ODU_AIS alarm is cleared.
Step 2 If the ODU_AIS alarm persists, locate the fault in the upstream direction. Determine the station
(FR station) that is the first to receive the ODU_AIS alarm. Then follow Step 1 to troubleshoot
the FR station.
Step 3 If the ODU_AIS alarm still persists, troubleshoot the upstream station (PR station) of the FR
station. Check whether any alarms of higher levels exist in the receive part of the PR station. If
yes, clear the alarms.
Step 4 If the ODU_AIS alarm still persists, perform a loopback for the service output optical interfaces
of the upstream stations from the FR station. Determine the station (FL station) where the
ODU_AIS or alarms of higher levels occur for the first time after the loopback. Troubleshoot
the FL station as follows:
1.
Check the configuration at the FL station. If any fault exists, correct the connection and
configuration.
2.
If the ODU_AIS alarm persists, replace the line boards at the FL station.
3.
If the ODU_AIS alarm still persists, replace the cross-connect and timing board at the FL
station.
----End
Related Information
None
4.145 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the ODU path are locked.
Issue 02 (2011-10-31)

562
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the ODU_LCK alarm is generated, the entire ODU path is locked and thus cannot be
configured with services of customers.
Possible Causes
The possible causes of the ODU_LCK alarm are as follows:
l
The ODU path test is performed.
Procedure
Step 1 Check whether the ODU path test is performed. If yes, wait until the ODU path test is complete.
Cancel the lockout. Then, check whether the ODU_LCK alarm is cleared.
Step 2 If no ODU path test is performed, cancel the lockout and then check whether the ODU_LCK
alarm is cleared.
Step 3 If the alarm persists, the board hardware may be faulty. In this case, replace the board that reports
the alarm.
----End
Related Information
None
4.146 ODU_OCI
Description
The ODU_OCI is an ODU open connection indication.
Issue 02 (2011-10-31)

563
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the ODU_OCI alarm is generated, no connection source exists for the entire ODU path.
At this time, the service is unavailable.
Possible Causes
The possible causes of the ODU_OCI alarm are as follows:
l
Alarms of higher levels exist at the local station, such as R_LOS, FEC_LOF, OTU_LOF,
and OTU_AIS.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS, FEC_LOF,
OTU_LOF, and OTU_AIS exist at the local station. If yes, clear these alarms and then check
whether the ODU_OCI alarm is cleared.
Step 2 If the alarm persists, the upstream services may be faulty. Check the upstream equipment. If it
is the OptiX OSN equipment, replace the line boards. If it is another type of equipment, add a
cross-connection to the downstream ODU path that receives the ODU_OCI alarm according to
the corresponding alarm troubleshooting measures.
Step 3 If the alarm still persists, the board at the local station may be faulty. In this case, replace the
board at the local station.
----End
Related Information
None
4.147 ODU_SNCP_STA_INDI
Description
The ODU_SNCP_STA_INDI alarm indicates the state of the ODU SNCP protection group. This
alarm is reported when the working or protection channel of the protection group is faulty or the
user runs an external switching command.
Issue 02 (2011-10-31)

564
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l
When switching is performed to the ODU SNCP group, the services would be transiently
interrupted.
When the alarm is reported, the working or protection channel of the ODU SNCP group
might have faulty services that need to be restored.
Possible Causes
l
Cause 2: The services of the working channel or the protection channel of the ODU SNCP
group are faulty.
Cause 1: A user issues an external switching command.
Procedure
Issue 02 (2011-10-31)
1.
2.

565
OptiX OSN 8800/6800/3800

3.
l
4 Alarm Processing

external switching.
Cause 2: The services of the working channel or the protection channel of the ODU SNCP
group are faulty.
1.
Query whether the related boards for configuring the protection group have the alarms,
for example, R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, OTUk_TIM, ODUk_LOFLOM, ODUk_PM_AIS,
ODUk_PM_LCK, ODUk_PM_OCI, ODUk_PM_TIM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn_LTC,
ODUk_TCMn_TIM, OTUk_DEG, OTUk_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, ODUk_TCMn_DEG, ODUk_TCMn_EXC. If these boards
have these alarms, handle the alarms by referring to the corresponding handling
procedure of the alarms to restore the services of the working channel or the protection
channel.
2.
Revertive. If the attribute is Revertive, the working channel would automatically
switch to the working channel. The alarm would clear. If the attribute is NonRevertive, set it to Revertive and the alarm would clear.
1.
This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
4.148 ODUk_LOFLOM
Description
The ODUk_LOFLOM is an alarm indicating that the frame alignment signal (FAS) and
multiframe alignment signal (MFAS) are abnormal. The alarm occurs when the information
about the upstream frame header and the downstream frame header does not match
l
For OptiX OSN 8800, its value is FLEX, 0, 1 or 2.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

566
OptiX OSN 8800/6800/3800

4 Alarm Processing

The services on the board are interrupted.
Possible Causes
l
The signals transmitted by the corresponding board at the opposite end do not have a frame
structure.
The input optical power is abnormal.
The FEC type is incorrectly configured.
Bit errors in the received signals of the OTU board at the local station are excessive.
The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If that is the case, locate
the position where the alarm is first generated according to the service route. If no alarm exists
at the opposite end, the local end is the place where the alarm is first generated.
Step 2 Check whether the input optical power of the place where the alarm is first generated is within
the normal range by using the U2000. For optical power specifications of specific boards, see
the Product Description. If the optical power is abnormal, handle the alarm according to the
handling procedure of the IN_PWR_HIGH or IN_PWR_LOW alarm.
Step 3 Query the FEC type of the board set on the U2000 to check whether it is consistent with the FEC
type of the board. For specific error correction types, see the Hardware Description. If they are
not consistent, modify the setting on the U2000 to ensure the consistency.
Step 4 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local station by using the U2000. If the BIP8 bit errors are excessive, handle the alarm according
to the handling procedure of the OTUk_DEG or OTUk_EXC alarm.
Step 5 If the alarm persists, check whether the fiber meets the following requirements:
l The bending radius is not less than 40 mm.
l The optical interface connector is well inserted.
l The fiber connector is clean.
l The cable is intact.
If the preceding requirements are not met, clean the fiber connector or replace the fiber. For
details, see the Supporting Tasks.
----End
Related Information
ITU-T G.709
4.149 ODUk_PM_LCK
Description
The ODUk_PM_LCK is an alarm indicating that the ODUk PM signal is locked. The
maintenance signal LCK byte required by the carrier is used to lock the access point signal of
Issue 02 (2011-10-31)

567
OptiX OSN 8800/6800/3800

4 Alarm Processing
users during testing. It can be generated when the service layer adapts the source and sink. The
alarm is generated when the STAT byte value is "101" during locking.
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services borne by the optical port would be interrupted.
Possible Causes
The services at the optical port are interrupted.
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
Step 2 Query the board information and set LCK Insertion to Disabled if it is Enabled, and the local
station does not insert an LCK signal to the downstream.
----End
Related Information
ITU-T G.709
4.150 ODUk_PM_OCI
Description
The ODUk_PM_OCI is an alarm indicating an ODUk PM open connection. The alarm is
generated when the output interface is not connected to the input interface and the STAT byte
value is "110".
l
Issue 02 (2011-10-31)

568
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services at the optical port are interrupted.
Possible Causes
l
The corresponding board at the upstream station has the ODUk_PM_OCI alarm.
There is loopback on the corresponding board at the opposite station.
The corresponding board at the opposite station has no or incorrect cross-connection

configuration.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board by using the U2000. If there
is, handle the alarm with higher severity.
Step 2 If the alarm persists, query whether the upstream stations generate the alarm. If that is the case,
locate the station where the alarm is triggered according to the service route.
Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If that is the case, release the loopback.
Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is
configured with incorrect cross-connection or has no cross-connection configuration. If that is
the case, correctly configure the cross-connection.
----End
Related Information
ITU-T G.709
4.151 ODUk_PM_TIM
Description
The ODUk_PM_TIM is an alarm indicating mismatch of the ODUk PM trace identifier. The
alarm occurs during control process when the trace identifier at the opposite end mismatches
Issue 02 (2011-10-31)

569
OptiX OSN 8800/6800/3800

4 Alarm Processing
that at the local end when the TIM detection is enabled. The system compares the access point
identifiers (API) in the input signals and the expected API.
For the set TIM detection mode, the network architecture can be classified into the following
three types.
l
For the point-to-point topology, only the source access point identifiers (SAPI) is compared
for the sink of trail termination.
For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPI) is compared for the sink of trail termination.

l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the signal quality of the services at the optical port is degraded. Hence,
the service signals may be unavailable.
Possible Causes
l
The networking architecture and the TIM detection mode to be configured are not
consistent.
The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be
received at the local end.
The cross-connection configuration is incorrect.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end on the U2000 interface according to networking architecture. If the topology is a
point-to-point topology or point-to-multipoint topology, only the SAPI is compared for the sink
of trail termination. If the topology is multipoint-to-multipoint topology, only the DAPI is
compared for the sink of trail termination.
Issue 02 (2011-10-31)

570
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be
received at the local end through the U2000. If they are not consistent, query the received TTI
on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to the same
as these of the received TTI.
Step 3 If the alarm persists, check whether the fiber connection between the local port and the upstream
port is correct. If the fiber connection is incorrect, correctly connect the fiber.
Step 4 Check whether the cross-connection configuration is correct. If not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.152 ODUk_TCMn_AIS
Description
The ODUk_TCMn_AIS is an ODUk TCMn alarm signal indication. An AIS signal travels
downstream, which indicates that a signal failure is detected in the upstream.
l
For OptiX OSN 8800, its value is 0, 1, 2, 3.
For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

The services at the optical interface are unavailable.
Possible Causes
l
Signals input from the client side contain the ODUk_TCMn_AIS signal.
The corresponding board at the opposite end transmits the ODUk_TCMn_AIS signals.
Issue 02 (2011-10-31)

571
OptiX OSN 8800/6800/3800

4 Alarm Processing
The loopback or cross-connection is set at the upstream station, and the FEC type is
incorrectly configured.
Procedure
Step 2 Query whether the alarm is reported from the client side. If that is the case, check the equipment
on the client side.
Step 3 Query whether the ODUk_PM_AIS, R_LOS, or R_LOF alarm exists on the client side of the
OTU board at the opposite end by using the U2000. If the alarm exists, check the equipment at
the opposite end.
Step 4 Query whether the loopback is set on the upstream station by using the U2000. If that is the case,
release the loopback of the upstream station.
Step 5 Check whether the configuration of the cross-connection and FEC type at the upstream station
is correct. If the configuration is incorrect, modify the configuration.
----End
Related Information
ITU-T G.709
4.153 ODUk_TCMn_BDI
Description
The ODUk_TCMn_BDI is an ODUk TCMn backward defect indication. The alarm occurs when
five consecutive BDI bytes in the TCMn overhead field are "1".
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

572
OptiX OSN 8800/6800/3800

4 Alarm Processing

Bit errors occur at the downstream station.
Possible Causes
l
Signals input from the client side contain the ODUk_TCMn_BDI signal.
The corresponding OTU board at the downstream station receives the LOF, LOM,
ODUk_TCMn_AIS, ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or
ODUk_TCMn_SSF alarm.
Procedure
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l
If the alarm is reported from the client side, check the equipment on the client side.
If the alarm is reported from the WDM side, check whether the corresponding OTU board
at the downstream station receives the LOF, LOM, ODUk_TCMn_AIS,
ODUk_TCMn_LCK, ODUk_TCMn_LTC, ODUk_TCMn_OCI, or ODUk_TCMn_SSF
alarm by using the U2000. If yes, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
4.154 ODUk_TCMn_DEG
Description
The ODUk_TCMn_DEG is an alarm indicating that the ODUk TCMn signal is degraded. This
alarm occurs when the signal is degraded or bit errors cross the threshold if the error detection
is in the burst mode. This alarm occurs when the signal is degraded or bit errors cross the
threshold if the error detection is in the Poisson mode.
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-10-31)

573
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

If the alarm is generated, the services at the optical interface generate bit errors, which make the
service signals unavailable.
Possible Causes
l
The optical interface that reports the alarm is faulty.
The optical interface at the opposite end is faulty.
Procedure
Step 1 Use the U2000 to browse alarms of the entire network to determine the slot ID, interface ID,
and channel ID of the board that generates this alarm.
Step 2 Locate the point that first generates the ODUk_TCMn_DEG alarm according to the service
route.
Step 3 Step 3 Check whether the input optical power of the place where the alarm is first generated is
within the normal range by using the U2000. If not, handle it according to the handling
procedures of the IN_PWR_HIGH and IN_PWR_LOW alarms. For optical power specifications
of specific boards, see the Product Description.
Step 5 If the alarm persists, the optical interface on the board at the local end may be faulty. Replace
Step 6 If the alarm persists, the optical interface on the OTU board at the opposite end may be faulty.
Replace the faulty OTU board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)

574
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.155 ODUk_TCMn_EXC
Description
The ODUk_TCMn_EXC is an alarm indicating that the ODUk TCMn section BIP8 errors cross
the threshold. This alarm occurs when the bit errors cross the threshold if the error detection is
in the Poisson mode.
l
For OptiX OSN 8800, its value is 0, 1, 2, 3
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The alarm has an influence on the QoS of the service signals.
Possible Causes
l
The attenuation of the received signals is excessively large, and the fiber of the transmission
line is abnormal.
Procedure
Step 1 Check whether the received optical power of the interface is within the normal range by using
Step 2 If the alarm persists, check whether the transmit optical power of the corresponding interface
on the upstream board is within the normal range by using the U2000. For optical power
specifications of specific boards, see the Product Description. If the transmit optical power of
the board at the upstream station is excessively low, clear the alarm according to the handling
Issue 02 (2011-10-31)

575
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station by using
the U2000. Loop back the transmit optical interface and receive optical interface on the WDM
side of the OTU board at the upstream station. If the bit errors exist, clear the bit error fault of
the upstream station.
Replacement.
----End
Related Information
ITU-T G.709
4.156 ODUk_TCMn_LCK
Description
The ODUk_TCMn_LCK is an alarm indicating that the ODUk TCMn signal is locked. The
maintenance signal LCK byte required by the carrier is used to lock the access point signal of
users during testing. It can be generated when the service layer adapts the source and sink. The
alarm is generated when the STAT byte value is "101" during locking.
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possible Causes
The signals are locked for the test of current line signals.
Issue 02 (2011-10-31)

576
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Use the U2000 to query and locate the slot ID, interface ID, and channel ID of the board that
generates this alarm.
Step 2 Set the LCK type to Disabled if it is Enabled.
----End
Related Information
ITU-T G.709
4.157 ODUk_TCMn_LTC
Description
The ODUk_TCMn_LTC is an alarm indicating loss of ODUk TCMn serial connection. The
TCM provides the connection monitoring function of the ODUk to cater for different application
scenarios. For example, the TCM from optical NNI to optical NNI monitors the connection of
the ODUk through the carrier network. The alarm occurs when the serial connection is lost and
the STAT byte is "000".
l
For OptiX OSN 8800, its value is 0, 1, 2, 3
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The TCM is not available.
Possible Causes
The TCM at the opposite end is not set as enabled, and thus there is no TCM source.
Issue 02 (2011-10-31)

577
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 On the U2000, find the position that generates this alarm first according to the network topology.
Step 2 Query whether the source configuration of this position and its opposite position is correct. If
not, modify the configuration
----End
Related Information
ITU-T G.709
4.158 ODUk_TCMn_OCI
Description
The ODUk_TCMn_OCI is an ODUk TCMn open connection indication. The alarm occurs when
the output interface is not connected to the input interface and the STAT byte is "110".
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possible Causes
l
The corresponding board at the upstream station has the ODUk_TCMn_OCI alarm.
There is loopback on the corresponding board at the opposite station.
The corresponding board at the opposite station has no or incorrect cross-connection

configuration.
Issue 02 (2011-10-31)

578
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 2 If the alarm persists, check whether the upstream station has this alarm. If yes, locate the station
that triggers this alarm according to the service route.
Step 3 Check whether the corresponding board of the station that triggers this alarm has any loopback.
If yes, release the loopback.
Step 4 If the alarm persists, check the corresponding board of the station that triggers this alarm is
configured with incorrect or no cross-connection. If yes, configure the correct cross-connection.
----End
Related Information
ITU-T G.709
4.159 ODUk_TCMn_SSF
Description
The ODUk_TCMn_SSF is an alarm indicating that the ODUk TCMn server signal fails.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
l
Issue 02 (2011-10-31)
The ODUk_TCMn_AIS or ODUk_LOFLOM alarm is generated on the line.

579
OptiX OSN 8800/6800/3800

4 Alarm Processing
The OTUk_TIM alarm is generated on the line and the OTUk_TIM follow-up response is
set to be enabled.
The OTUk_SSF alarm is generated.
Procedure
Step 1 Check along the service signal flow to locate the station that first generates the SSF alarm.
1.
Check whether the ODUk_PM_AIS or ODUk_LOFLOM alarm occurs at the station. If

yes, clear the alarm according to the corresponding handling procedure.
2.
Check whether the OTUk_TIM alarm occurs at the station. If yes, clear the alarm according
to the alarm handling procedure.
Step 2 If the alarm persists, check whether the OTUk_SSF alarm occurs on the line or not. If yes, clear
the alarm according to the alarm handling procedure.
----End
Related Information
None
4.160 ODUk_TCMn_TIM
Description
The ODUk_TCMn_TIM is an alarm indicating ODUk TCMn trace identifier mismatch. This
alarm occurs during control process when the trail trace identifier at the opposite end mismatches
that at the local end when the TIM detection is enabled. The system compares the access point
identifiers (API) in the input signals and the expected API.
three types:
l
termination.

l
Issue 02 (2011-10-31)

580
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the quality of the signals at the optical interface is degraded. Hence,
Possible Causes
l
consistent.
The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be
received at the local end.
Procedure
Step 1 Query the TIM detection mode of the local end on the U2000. Select the suitable topology for
the local end on the U2000 interface according to the networking architecture. If the topology
is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink
of trail termination.
Step 2 Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with
that to be received at the local end through the U2000. If they are not consistent, query the
received TTI on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local
end to the same as these of the received TTI.
cross-connection.
----End
Related Information
ITU-T G.709
Issue 02 (2011-10-31)

581
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.161 ODUKSP_PS
Description
The ODUKSP_PS is an alarm indicating the ODUk SP protection switching. This alarm occurs
when the ODUk SP protection group actuates switching in which the current channel switches
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the ODUk SP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the ODUk SP protection group might have
Possible Causes
l
switching. Such a command makes the current channel of the ODUk SP protection group
Cause 2: The services of the working channel of the ODUk SP protection group are faulty.
reported.
Procedure
1.
2.

1.
Issue 02 (2011-10-31)
to the services, such as R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI, ODUk_TCMn_LCK,
ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG and ODUk_TCMn_EXC. If yes,
handle the alarms by referring to the corresponding alarm handling procedures.
582
OptiX OSN 8800/6800/3800

2.
4 Alarm Processing
----End
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services. This
protection uses two different ODUk channels to achieve the protection of multiple distributed
services between all stations. For details, see "ODUk SPRing Protection" in the Feature
Description.
4.162 ODUKSP_STA_INDI
Description
The ODUKSP_STA_INDI is an alarm indicating the state of the ODUk SPRing protection
group. This alarm is reported when the working or protection channel of the protection group is
faulty or the user runs an external switching command.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Issue 02 (2011-10-31)

583
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameters 1
Indicate the west switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR
Parameters 1
Indicate the east switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR

l
When the ODUk SP protection switching is performed, the services are transiently
interrupted.
When the alarm is reported, the working or protection channel in the ODUk SP protection
group may contain faulty services. In this case, you need to remove the fault to restore the
services.
Issue 02 (2011-10-31)

584
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The user issues an external switching command such as forced switching, manual
The services of the working or protection channel of the ODUk SP protection group are
faulty.
The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
switching, manual switching, or locked switching, check whether the external switching is
necessary.
1.
2.
external switching.
1.
Check whether service related alarms such as R_LOS, R_LOC, HARD_BAD,

OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_LOFLOM, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, ODUk_TCMn_AIS, OTUk_EXC, ODUk_TCMn_DEG or
ODUk_TCMn_EXC occur on the corresponding boards in the protection group. If yes,
clear the alarm according to the corresponding alarm handling procedures to restore the
services of the working channel or protection channel.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the
WTR state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Related Information
The ODUk SPRing protection mainly applies to the ring network with distributed services. This
protection uses two different ODUk channels to achieve the protection of multiple distributed
services between all stations. For details, see "ODUk SPRing Protection" in the Feature
Description.
4.163 OH_LOOP
Description
The OH_LOOP is an alarm of overhead bus loopback. This alarm occurs when the overhead
bus of a line board is looped back.
Attribute
Alarm Severity
Alarm Type
Minor
Security alarm
Issue 02 (2011-10-31)

585
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
table.
Name
Meaning
Parameter 1
l 0x01: indicates a loopback on the line board.

l 0x02: indicates a loopback on the opposite board.
l 0x03: indicates a loopback on the SCC board.

When the OH_LOOP alarm occurs, the overhead signal is looped back. The services are not
affected but the ECC communication is interrupted.
Possible Causes
The overhead bus of the line board is looped back.
Procedure
Step 1 After the loopback is released, the OH_LOOP alarm is automatically cleared.
----End
Related Information
None
4.164 OLP_PS
Description
The OLP_PS is an alarm indicating the optical line protection switching. This alarm occurs when
the optical line protection group actuates switching in which the current channel switches to the
protection channel from the working channel.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

586
OptiX OSN 8800/6800/3800

4 Alarm Processing

When the optical line protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the optical line protection group might have
Possible Causes
l
switching. Such a command makes the current channel of the optical line protection group
Cause 2: The services of the working channel of the optical line protection group are faulty.
reported.
Cause 3: The difference between the optical power on the working channel and that on the
protection channel exceeds the threshold.
Procedure
1.
2.

1.
Query whether the input optical power of the working channel is within the normal range
on the U2000. For optical power specifications of specific boards, see the Product
Description. If the optical power is not within the normal range, handle the alarm according
to the handling procedure of the IN_PWR_LOW alarm to make the input optical power of
the working or protection channel be within the normal range.
2.
Step 3 If the alarm persists, check whether the POWER_DIFF_OVER alarm exist. If that is the case,
handle the alarms according to the corresponding handling procedures.
----End
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual
fed and selective receiving function of OLP boards. For details, see "Optical Line Protection"
in the Feature Description.
Issue 02 (2011-10-31)

587
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.165 OLP_STA_INDI
Description
The OLP_STA_INDI is an alarm indicating the optical line protection switching. This alarm is
reported when the working or protection channel of the protection group is faulty or the user
runs an external switching command.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l
When protection switching is performed on the optical line, the services are transiently
interrupted.
When the alarm is reported, the working or protection channel of the optical line protection
group may have faulty services that need to be restored.
Possible Causes
l
The user issues an external switching command such as forced switching, manual switching
or locked switching.
The services of the working channel or protection channel of the optical line protection
group are faulty.
Issue 02 (2011-10-31)

588
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
necessary.
1.
2.
external switching.
Step 2 If the alarm is generated due to the fault of the working channel or protection channel of the
protection group, do as follows:
1.
Query whether the input optical power of the working or protection channel is within the
normal range on the U2000. For optical power specifications of specific boards, see the
Product Description. If the optical power is not within the normal range, handle the alarm
according to the handling procedure of the IN_PWR_LOW alarm to make the input optical
power of the working or protection channel be within the normal range.
2.
that is the case, the services in the working channel automatically switch to the working
channel. The alarm is cleared. If the attribute is Non-Revertive, set it to Revertive and the
alarm is cleared.
----End
Related Information
Optical line protection (OLP) protects line fibers between adjacent stations by using the dual
fed and selective receiving function of OLP boards. For details, see "Optical Line Protection"
in the Feature Description.
4.166 OMS_BDI
Description
The OMS_BDI is the backward defect indication at the OMS layer. When the OMS_BDI-P and
OMS_BDI-O alarms coexist, this alarm is generated. At the same time, the OMS_BDI-P and
OMS_BDI-O alarms are suppressed.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

589
OptiX OSN 8800/6800/3800

4 Alarm Processing

The incorrect logical fiber connection does not affect services. Otherwise, the services of the
system are interrupted.
Possible Causes
The OMS_BDI-P and OMS_BDI-O alarms coexist.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_LOS-O, OTS_TIM, or OMS_LOS-P alarm at the
opposite station and all downstream stations. If yes, clear the OTS_LOS, OTS_LOS-O,
OTS_TIM, or OMS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.167 OMS_BDI-O
Description
The OMS_BDI-O is a backward defect indication (overhead) at the OMS layer. The OMS_BDIO signal is inserted back to the upstream station when the downstream station receives no
overhead signals from the upstream station and the OTS_LOS_O alarm is generated from the
downstream station.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
l
Issue 02 (2011-10-31)
The downstream station inserts the BDI-O overhead signal back to the OMS layer of the
local station, when the downstream station detects no overhead signals because of a fiber
590
OptiX OSN 8800/6800/3800

4 Alarm Processing
cut, low optical power, or dispersion. This alarm is generated when the local station receives
the BDI-O overhead signal.
l
The local station sends no overhead signals.
Procedure
Step 2 Check whether there is the OTS_LOS-O alarm at the opposite station and all downstream
stations. If yes, clear the OTS_LOS-O alarm by following proper handling procedures.
----End
Related Information
None
4.168 OMS_BDI-P
Description
The OMS_BDI-P is a backward defect indication (payload) at the OMS layer. The OMS_BDIP signal is inserted back to the upstream station when the downstream station receives no payload
signals from the upstream station.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

are interrupted.
Possible Causes
The downstream station inserts the BDI-P overhead signal back to the OMS layer of the local
station, when the downstream station detects no payload signals because of a fiber cut, low
optical power, or dispersion. This alarm is generated when the local station receives the BDI-P
overhead signal.
Issue 02 (2011-10-31)

591
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 2 Check whether there is the OTS_LOS-P or OMS_LOS-P alarm at the opposite station and all
downstream stations. If yes, clear the OTS_LOS-P or OMS_LOS-P alarm by following proper
----End
Related Information
None
4.169 OMS_FDI-O
Description
The OMS_FDI-O is a forward defect indication (overhead) at the OMS layer. The OMS_FDIO signal is inserted to the downstream station when the board at the OTS layer detects no
overhead signals and cannot send overhead signals to the downstream station.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
l
The FDI-O overhead signal is inserted to the OMS layer of the downstream station, when
the local station detects no overhead signals because of a fiber cut, low optical power, or
dispersion. This alarm is generated when the downstream station receives the FDI-O
overhead signal.
Procedure
Issue 02 (2011-10-31)

592
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 2 Check whether there is the OTS_LOS-O alarm at all upstream stations. If yes, clear the
OTS_LOS-O alarm by following proper handling procedures.
----End
Related Information
None
4.170 OMS_FDI-P
Description
The OMS_FDI-P is a forward defect indication (payload) at the OMS layer. The OMS_FDI-P
signal is inserted to the downstream station when the board at the OTS layer detects no payload
signals and cannot send payload signals to the downstream station.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
The FDI-P signal is inserted to the OMS layer of the downstream station, when the local station
detects no payload signals because of a fiber cut, low optical power, or dispersion. This alarm
is generated when the downstream station receives the FDI-P signal.
Procedure
Step 2 Check whether there is the OTS_LOS-P alarms at the opposite station and all upstream stations.
If yes, clear the OTS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
Issue 02 (2011-10-31)

593
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.171 OMS_LOS-P
Description
The OMS_LOS-P is an alarm indicating loss of signal (payload) at the OMS layer. If there is
no OTS_LOS-P alarm at the OTS layer, the OMS_LOS-P alarm is reported when the OTU board
detects the LOS alarm.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

are interrupted.
Possible Causes
The OMS layer detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.
Procedure
Step 1 Step 1 Check whether the logical fiber connection is consistent with the actual fiber connection.
If not, modify the logical fiber connection to make it consistent with the actual fiber connection.
Step 2 Confirm that the actual fiber connection between the board that reports this alarm and the FIU
board is correct.
Step 3 Check whether there is the OTS_LOS alarm on the FIU. If yes, clear the alarm according to the
procedure to handle OTS_LOS.
Step 4 Check whether there is MUT_LOS alarm.
l
If yes, clear the alarm according to the procedure to handle MUT_LOS.
If not, replace the faulty board according to the Parts Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

594
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.172 OMS_SSF
Description
The OMS_SSF is an alarm indicating that the server signal fails at the OMS layer. When the
OMS_SSF-P and OMS_SSF-O alarms coexist, this alarm is generated. At the same time, the
OMS_SSF-P and OMS_SSF-O alarms are suppressed.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

are interrupted.
Possible Causes
The OMS_SSF-P and OMS_SSF-O alarms coexist.
Procedure
Step 2 Check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, or OTS_LOS-O alarm on the
FIU connected to the local board. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOS-P, or
OTS_LOS-O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether there is the OTS_LOS, OTS_TIM, OTS_LOS-P, or
OTS_LOS-O alarm at all upstream stations. If yes, clear the OTS_LOS, OTS_TIM, OTS_LOSP, or OTS_LOS-O alarms by following proper handling procedures.
----End
Related Information
None
Issue 02 (2011-10-31)

595
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.173 OMS_SSF-O
Description
The OMS_SSF-O is an alarm indicating that the server signal (overhead) fails at the OMS layer.
When the OTS layer detects the failure of the overhead signals, or receives the OMS_FDI-O
signal from the upstream station, this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Possible Causes
l
Because of a fiber cut, low optical power, dispersion, or failure in overhead signals at the
upstream OTS layer, the OTS layer of the board loses the overhead signals and the overhead
signals received by the OMS layer from the OTS layer are invalid. Hence, this alarm is
reported.
Procedure
Step 2 Check whether there is the OTS_LOS-O or OOS_LOST alarm on the FIU connected to the local
board. If yes, clear the OTS_LOS-O, or OOS_LOST alarm by following proper handling
procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-O, or OOS_LOST alarm at the
opposite station and all upstream stations. If yes, clear the OTS_LOS-O, or OOS_LOST alarm
----End
Related Information
None
Issue 02 (2011-10-31)

596
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.174 OMS_SSF-P
Description
The OMS_SSF-P is an alarm indicating that the server signal fails (payload) at the OMS layer.
When the OTS layer detects the failure of the payload signals or receives the OMS_FDI-P signal
from the upstream station, this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

are interrupted.
Possible Causes
When the service-layer payload signals received by the OMS layer are invalid and the OTS layer
can not detect any signals because of a fiber cut, low optical power, or dispersion, this alarm is
generated.
Procedure
Step 2 Check whether there is OTS_LOS-P alarm on the FIU connected to the local board. If yes, clear
the OTS_LOS-P alarm by following proper handling procedures.
Step 3 If the alarm persists, check whether there is the OTS_LOS-P alarm at the opposite station and
all upstream stations. If yes, clear the OTS_LOS-P alarms by following proper handling
procedures.
----End
Related Information
None
Issue 02 (2011-10-31)

597
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.175 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm occurs
when the phase-locked loop on the clock board becomes faulty.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the failed phase-locked loop.

l 0x01: first 2M phase-locked loop
l 0x02: second 2M phase-locked loop
l 0x03: 155M system phase-locked loop

When the OOL alarm is generated, the phase-locked loop cannot lock on the input signals, and
as a result the output clock signals are affected. This alarm may lower the quality of services or
interrupt the services.
Possible Causes
Cause 1: The board hardware of the phase-locked loop is damaged.
Procedure
l
Cause 1: The board hardware of the phase-locked loop is damaged.

1.
Perform cold reset on the board. Then, check whether the alarm is cleared. For details,
see Performing Cold Reset of a Board in the Supporting Tasks.
2.
----End
Issue 02 (2011-10-31)

598
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
4.176 OOS_LOST
Description
The OOS_LOST is an alarm indicating loss of OTM overhead signal (OOS). When the local
station receives no overhead signals in ten consecutive seconds and there is no OTS_LOS-O
alarm, this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

be an impact on the optical-layer overhead.
Possible Causes
l
The local station receives no overhead signals in ten consecutive seconds because the
opposite station sends no overhead signals.
Procedure
Step 2 Check whether the opposite station supports the OLS function.
l
If not, this alarm does not need to be handled.
If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None
Issue 02 (2011-10-31)

599
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.177 OPA_FAIL_INDI
Description
The OPA_FAIL_INDI alarm is an alarm indicating that the automatic power adjustment (OPA)
of the optical cross-connection fails. The alarm occurs if the calculated attenuation exceeds the
settable range of the board when the optical power is automatically adjusted.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
Parameter
Description
Parameter 1
Indicates the ID of the wavelength of the optical cross-connection.

l
When the alarm is reported, the attenuation of the board is not adjusted. For new services,
the services may be unavailable. For existing services, the QoS cannot be improved.
This alarm indicates an operation failure instead of a fault being detected. In other words,
this alarm persists even after you manually adjust the attenuation and services are restored.
Possible Causes
l
Cause 1: The optical power budget is insufficient.
Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or
VA4 board is used.
Cause 3: When there are adjustment points of multiplexed wavelengths and each single
wavelength in OPA scenarios, the attenuation of the VOAs at the multiplexed wavelength
adjustment points is not adjusted to the minimum value. For example, in the OPA
application scenario, the built-in VOAs on multiplexer or demultiplexer boards or optical
add/drop multiplexer (OADM) boards adjust single wavelengths, and the VA1 or VA4
boards on the line side or the built-in VOAs adjust multiplexed wavelengths.
Cause 1: The optical power budget is insufficient.
Procedure
1.
Issue 02 (2011-10-31)
Use OA boards with larger optical power, and modify the rated input and output optical
power of the OA boards. For details, see "Setting the Rated Optical Power of the OA
Board" in the Commissioning Guide.
Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or
VA4 board is used.
600
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
Change the optical cross-connection mode from automatic to manual and change the
mode to automatic again. The OPA will be triggered after the mode is changed from
manual to automatic. Therefore, check whether services are configured on the trail
where the OPA applies before you change the mode.
Cause 3: When there are adjustment points of multiplexed wavelengths and each single
wavelength in the automatic optical power adjustment scenario, the attenuation of the
VOAs at the multiplexed wavelength adjustment points is not adjusted to the minimum
value.
1.
On the U2000, adjust the attenuation of the VOAs on the VA1 or VA4 board or an
OA board to the minimum value, change the mode of all optical cross-connections on
the trail from automatic to manual, and then change the mode to automatic again. The
OPA will be triggered after the mode is changed from manual to automatic. Therefore,
check whether services are configured on the trail where the OPA applies before you
change the mode.
----End
Related Information
The optical power adjustment (OPA) technology is available in the commissioning phase. For
details, see "Optical Power Adjust (OPA)" in the Feature Description.
4.178 OPU1_MSIM
Description
The OPU1_MSIM is an alarm indicating the OPU1 multiplex structure identifier mismatch.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The services may be unavailable.
Possible Causes
The board does not support the multiplex structure for service transmission of the board on the
source NE.
Issue 02 (2011-10-31)

601
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the multiplex structure of the local board mismatches with that of the
corresponding board on the source NE. For the multiplex structure of the board, see the
Hardware Description.
Step 2 If the multiplex structures of the two boards do not match, replace one of them with a matched
----End
Related Information
ITU-T G.709
4.179 OPU1_VCAT_SQM
Description
The OPU1_VCAT_SQM is an alarm indicating the OPU1 sequence indicator mismatch. The
alarm is generated when the received OPU1 sequence indicator (SQ) value is not consistent with
the expected value. For example, the SQ values of channels 1-4 on the system side are 0-3
respectively. When the services from channel 1 are connected to channel 2 on the system side
of the opposite TDX, the received SQ value is 0 and the SQ value to be received is 1. The values
mismatch, and then the alarm is generated.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When an OPU1_VCAT_SQM is detected, the value of received SQ is not consistent with the
value of SQ to be received. Then, the services are interrupted.
Possible Causes
Procedure
Step 1 Check whether the cross-connection sequence of the virtual cascading OPU1 at the local end
mismatches that at the opposite end. If not, re-configure the virtual cascading OPU1s at the local
end.
----End
Issue 02 (2011-10-31)

602
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
Each channel on the WDM side has an SQ value. The SQ values of optical interfaces are in an
ascending order. Compare the SQ value of the frame in each WDM-side optical interface with
that of its previous frame. If mismatch is found, the SQ mismatch alarm of the optical interface
is reported. If the SQ values of two optical interfaces are the same, the board also reports the SQ
mismatch alarm.
4.180 OPU1_VCAT_VcPLM
Description
The OPU1_VCAT_VcPLM is an alarm indicating mismatch of the OPU1 virtual concatenation
payload. The alarm is generated when the type of the OPU1 virtual concatenation payload
received mismatches the expected type. Each service type corresponds to a VcPt value. For
10GE LAN, the value is 5. For STM-64, the value is 3. When two TDXs interconnected with
each other, the alarm is generated if the service types at the two ends mismatch.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possible Causes
l
Service type configuration is incorrect.
Cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the VcPt value to be received at the local end is consistent with the received VcPt
value. If not, check whether the service type at the opposite end is consistent with that at the
local end. Re-configure the cross-connect service of the interconnected TDX board.
Step 2 If the alarm persists, check whether the VcPt value of the services transmitted from the opposite
end is consistent with the VcPt value to be received at the local end. If not, re-configure the
cross-connect service at the opposite end.
----End
Issue 02 (2011-10-31)

603
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
ITU-T G.709
4.181 OPU2_MSIM
Description
The OPU2_MSIM is an alarm indicating that mismatch of the OPU2 multiplex structure
indicator.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possibly the services are not available.
Possible Causes
source NE.
Procedure
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
----End
Related Information
ITU-T G.709
4.182 OPU3_MSIM
Description
The OPU3_MSIM is an alarm indicating mismatch of the OPU3 multiplex structure.
Issue 02 (2011-10-31)

604
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possible Causes
source NE.
Procedure
corresponding board of the source NE. For the multiplex structure of the board, see the Hardware
Description.
----End
Related Information
ITU-T G.709
4.183 OPUk_PLM
Description
The OPUk_PLM is an alarm indicating OPUk payload mismatch. The type of received payload
mismatches the expected payload type defined in the adaptation function.
l
Issue 02 (2011-10-31)

605
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

Possible Causes
The type of the payload in the data on the WDM side of the interconnected board mismatches.
Procedure
Step 1 Use the U2000 to query whether the PT byte value to be received at the OPU of the local board
is consistent with that of the received PT bytes. If they are not consistent, modify the PT of the
local NE to be consistent.
Step 2 Check whether the WDM-side fiber connection is correct according to the engineering fiber
connection diagram. If the fiber connection is incorrect, correctly connect the fiber according to
the engineering fiber connection diagram.
Step 3 Check whether the service type on the client side of the local board is the same as that of the
peer board. If the service types on the local board and peer board are not the same, set the service
types again based on the network plan to ensure that they are the same.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
----End
Related Information
ITU-T G.709
4.184 OSC_BDI
Description
Backward defect indication. This alarm occurs when detects a signal failure and the BDI byte
value is 1.
Issue 02 (2011-10-31)

606
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The OSC signals borne by the optical interface would be unavailable.
Possible Causes
BDI is declared if the BDI bit in the overhead field (byte 3, bit 5) is "1" for 5 consecutive frames.
Procedure
Step 2 If the alarm persists, check whether the corresponding board at the downstream station receives
the R_LOS orR_LOF alarm by using the U2000. If yes, handle the corresponding alarm at the
downstream station.
----End
Related Information
None
4.185 OSC_DEG
Description
Signal degraded alarm. This alarm occurs when bit errors are of burst distribution and the signal
degradation or bit error count crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

607
OptiX OSN 8800/6800/3800

4 Alarm Processing

If the alarm is generated, the OSC signals borne by the optical interface would generate bit errors,
which makes the OSC signals unavailable.
Possible Causes
l
The optical interface at the local end is faulty.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For the optical
power specification of the specific board, refer to "Technical Specifications" of the Product
Description. If the optical power is not within the normal range, see the handing procedure of
the IN_PWR_HIGH and IN_PWR_LOW alarms for troubleshooting.
Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, refer to
----End
Related Information
None
4.186 OSC_RDI
Description
The OSC_RDI is an alarm indicating a remote defect. The alarm occurs when the opposite station
returns the RDI alarm to the local station after receiving an R_LOF alarm.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-10-31)

608
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

The communication between the two stations is abnormal.
Possible Causes
l
The opposite station returns the RDI alarm to the local station after receiving the R_LOF
signals.
The optical fiber is damaged.
Procedure
Step 1 Query whether the opposite station has the R_LOF alarm. If that is the case, take it as the R_LOF
alarm for troubleshooting.
Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If that is the
case, repair the fiber.
----End
Related Information
None
4.187 OTS_BDI
Description
The OTS_BDI is an alarm indicating a backward defect at the OTS layer. When the OTS_BDIP and OTS_BDI-O alarms coexist, this alarm is generated. At the same time, the OTS_BDI-P
and OTS_BDI-O alarms are suppressed.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

609
OptiX OSN 8800/6800/3800

4 Alarm Processing

are interrupted.
Possible Causes
l
The upstream station reports the OTS_LOS alarm, and the downstream station inserts it
back to the local station.
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber
connection. If not, modify the logical fiber connection to make it consistent with the actual fiber
connection.
Step 2 Check whether there is the OTS_TIM or OTS_LOS alarm at the opposite station. If yes, clear
the OTS_TIM or OTS_LOS alarm by following proper handling procedures.
Step 3 If the alarm persists, check and make sure that fibers connected to the receive interfaces on the
local FIU are correct and there is no fiber disconnection.
----End
Related Information
None
4.188 OTS_BDI-O
Description
The OTS_BDI-O is an alarm indicating a backward defect (overhead) at the OTS layer. After
receiving the OTS_BDI-O signal inserted by the upstream station to the downstream, the local
station reports the OTS_BDI-O alarm.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

Issue 02 (2011-10-31)

610
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The opposite station inserts the BDI-O signal back to the local station, when detecting no
overhead signals because of a fiber cut, low optical power, or dispersion. This alarm is generated
when the local station receives the BDI-O overhead signal.
Procedure
Step 2 If the alarm persists, check and make sure that the fiber connection of the "RM" interface on the
local FIU is correct and there is no fiber disconnection.
Step 3 Check whether the opposite FIU reports the OTS_LOS-O alarm. If yes, handle the alarm by
following proper handling procedures.
----End
Related Information
None
4.189 OTS_BDI-P
Description
The OTS_BDI-P is an alarm indicating a backward defect (payload) at the OTS layer. After
receiving the OTS_BDI-P signal inserted back to the local station by the downstream station,
the local station reports this alarm.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

are interrupted.
Possible Causes
Issue 02 (2011-10-31)

611
OptiX OSN 8800/6800/3800

4 Alarm Processing
The opposite station inserts the BDI-P signal back to the local station, when detecting no payload
signal because of a fiber cut, low optical power, or dispersion. This alarm is generated when the
local station receives the BDI-P signal.
Procedure
connection.
Step 2 If the alarm persists, check and make sure that fibers connected to the receive interfaces of the
local PIU are correct and there is no fiber disconnection.
Step 3 Check whether there is the OTS_LOS-P alarm at the opposite station of the FIU. If yes, clear
the OTS_LOS-P alarm by following proper handling procedures.
----End
Related Information
None
4.190 OTS_LOS-O
Description
The OTS_LOS-O is an alarm indicating loss of signals (overhead) at the OTS layer. When the
OSC board connected to the "TM" interface of the FIU detects the LOS signals, this alarm is
generated.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

Possible Causes
This alarm is generated when the OTS layer of the receive end detects no overhead signal because
of a fiber cut, low optical power, or dispersion.
Issue 02 (2011-10-31)

612
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
connection.
Step 2 If the alarm persists, check and make sure that the fiber connection between the "TM" interface
of the local FIU and the OSC board is correct and there is no fiber disconnection.
Step 3 If the alarm persists, check and make sure that the fiber connection between the "TM" interface
of the local FIU and the OSC board is correct and there is no fiber disconnection.
Step 4 If the alarm persists, check whether the laser of the OSC at the opposite station is "On". If not,
open the laser of the OSC.
----End
Related Information
None
4.191 OTS_LOS-P
Description
The OTS_LOS-P is an alarm indicating loss of signal (payload) at the OTS layer. This alarm is
generated when the amplifier or other boards connected to the transmit interface of the FIU
detects the LOS signals.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

are interrupted.
Possible Causes
This alarm is generated when the OTS layer of the receive end detects no payload signal because
of a fiber cut, low optical power, or dispersion.
Issue 02 (2011-10-31)

613
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
connection.
Step 2 If the alarm persists, check and make sure that fibers connected to the interfaces of the local
station are correct and there is no fiber disconnection.
----End
Related Information
None
4.192 OTS_TIM
Description
The OTS_TIM is an alarm indicating mismatch of the trail trace identifier at the OTS layer.
When the API of the received TTI at the OTS layer is not consistent with the API to be received,
this alarm is generated.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the configuration of the TTI is incorrect, there has no influence to the services. If the fiber
connection is incorrect, the services may be interrupted.
Possible Causes
l
The TTI transmitted at the upstream station is not consistent with the TTI to be received at
the local station.
The fiber actual connection is incorrect.
Procedure
Step 1 Check whether the TTI transmitted at the transmit end (upstream station) is consistent with the
TTI to be received at the local end. If not, configure the TTI at the upstream station again.
Step 2 Check whether the fiber connection between the OSC and the "RM" or "TM" interface of the
FIU is compliant with the network regulation. If not, connect the fibers again.
----End
Issue 02 (2011-10-31)

614
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
For details of the API and TTI, see ITU-T G.709.
4.193 OTU_AIS
Description
The OTU_AIS an OTU alarm indication.
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None

When the OTU-AIS alarm is generated, no connection source exists for the entire ODU path.
At this time, the service is unavailable.
Possible Causes
The possible causes of the OTU_AIS alarm are as follows:
l
Alarms of higher levels such as R_LOS and FEC_LOF exist at the local station.
Procedure
Step 1 On the U2000, check whether the alarms of higher levels such as R_LOS and FEC_LOF exist
at the local station. If yes, clear these alarms and then check whether the OTU_AIS alarm is
cleared.
Step 2 If the OTU_AIS alarm persists, locate the fault in the upstream direction. Determine the station
(marked as an FR station) which is the first to receive the OTU_AIS alarm. Then follow Step 1
to troubleshoot the FR station.
Step 3 If the OTU_AIS alarm still persists, troubleshoot the upstream station (marked as a PR station)
of the FR station. Check whether any alarms of higher levels exist in the receive part of the PR
station. If yes, clear the alarms.
Step 4 If the OTU_AIS alarm persists, use fibers to perform loopbacks for the service output parts of
the upstream stations from the FR station. Determine the station (marked as an FL station) where
the OTU_AIS alarm is generated for the first time after the fiber loopbacks. Perform the
following steps to troubleshoot the FL station. Skip this step if the services cannot be interrupted.
Issue 02 (2011-10-31)

615
OptiX OSN 8800/6800/3800

4 Alarm Processing
In this case, directly replace the boards in the receive part of the FR station and the boards in
the service output part of the PR station.
1.
Check the configuration at the FL station. If any fault exists, correct the connection and
configuration.
2.
If the OTU_AIS alarm persists, replace the line boards at the FL station.
3.
If the OTU_AIS alarm still persists, replace the cross-connect and timing board at the FL
station.
----End
Related Information
None
4.194 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame alignment signal (FAS) is abnormal.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

When the OTU_LOF alarm is generated, the FEC function is disabled. At the same time, the
Possible Causes
The possible causes of the OTU_LOF alarm are as follows:
l
The fiber or the optical power is faulty.
The services that are transmitted from the opposite station are faulty.
Procedure
Step 1 View the OTU_LOF alarm on the U2000 to determine the relevant board.
excessively low, clean the fiber header and the connector. If the receive optical power is
Issue 02 (2011-10-31)

616
OptiX OSN 8800/6800/3800

4 Alarm Processing
excessively high, provide more optical attenuators. After making sure that the receive optical
power is proper, check whether the OTU_LOF alarm is cleared.
Step 3 If the OTU_LOF alarm persists, check the transmit optical power at the opposite station. If the
transmit optical power is excessively low, replace the board at the opposite station.
Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous
with those on the network. If not, set the clock tracing function, and then check whether the
OTU_LOF alarm is cleared.
Step 5 If the alarm still persists, check whether the fiber works well. If yes, replace the board that
generates the alarm.
Step 6 If the alarm persists, replace the cross-connect and timing board at the local station.
Step 7 If the alarm persists, replace the line board at the opposite station.
Step 8 If the alarm persists, replace the cross-connect and timing board at the opposite station.
----End
Related Information
None
4.195 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is
abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the OTU_LOM alarm is generated, the multiframe is lost and the services are interrupted.
Possible Causes
The possible causes of the OTU_LOM alarm are as follows:
l
The expected consecutive frames are not received.
Too many bit errors exist during the transmission.
Issue 02 (2011-10-31)

617
OptiX OSN 8800/6800/3800

4 Alarm Processing
The receive direction of this board is faulty.
Procedure
Step 1 View the OTU_LOM alarm on the U2000 to determine the relevant board.
excessively low, clean the fiber header and the connector. If the receive optical power is
excessively high, provide more optical attenuators. After making sure that the receive optical
power is proper, check whether the OTU_LOM alarm is cleared.
Step 3 If the alarm persists, check the transmit optical power at the opposite station. If the transmit
optical power is excessively low, replace the board at the opposite station.
Step 4 If the alarm persists, check whether the clocks on the local NE and opposite NE are synchronous
with those on the network. If not, set the clock tracing function, and then check whether the
OTU_LOM alarm is cleared.
Step 5 If the alarm persists, check whether the fiber works well. If yes, replace the board that generates
the alarm.
Step 6 If the OTU_LOM alarm still persists, replace the source board of the OUT path (excluding the
stations that transparently transmit the ODU path).
----End
Related Information
None
4.196 OTUk_AIS
Description
The OTUk_AIS is an OTUk alarm indication. An AIS signal travels downstream, which
indicates that a signal failure is detected in the upstream.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

618
OptiX OSN 8800/6800/3800

4 Alarm Processing

The services at the optical port are unavailable.
Possible Causes
l
Signals input from the client side contain the ODUk_PM_AIS or OTUk_AIS signals.
The upstream station has loopback or cross-connection or the FEC type configuration is
incorrect.
Procedure
Step 2 If the alarm is reported from the client side, check the equipment on the client side.
Step 3 Use the U2000 to query whether the upstream station has any loopback. If yes, release the
loopback.
Step 4 Check whether the configuration of the cross-connection and FEC type is correct at the upstream
station. If not so, correct the configuration.
----End
Related Information
ITU-T G.709
4.197 OTUk_BDI
Description
The OTUk_BDI indicates an OTUk backward defect. This alarm occurs when the SM section
detects a signal failure and the value of the BDI byte is 1.
l
Attribute
Alarm Severity
Alarm Type
Warning
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

619
OptiX OSN 8800/6800/3800

4 Alarm Processing

The services at the optical port are unavailable.
Possible Causes
l
Signals input from the client side contain the OTUk_BDI alarm.
The corresponding OTU board at the downstream station receives the LOF, LOM,
OTUk_AIS, or OTUk_TIM, OTUk_SSF alarm.
Procedure
Step 2 Query whether the alarm is reported from the client side or the WDM side.
l
If the alarm is reported from the client side, check the equipment on the client side.
If the alarm is reported from the WDM side, check whether the corresponding OTU board
at the downstream station receives the LOF, LOM, OTUk_AIS, OTUk_TIM, or
OTUk_SSF alarm by using the U2000. If yes, handle the corresponding alarm at the
downstream station.
----End
Related Information
ITU-T G.709
4.198 OTUk_DEG
Description
The OTUk_DEG is an alarm indicating that the OTUk signal is degraded. When the BIP8
detection is in burst mode, this alarm is generated if the signal degradation or bit error count
exceeds the threshold. In addition, when the BIP8 detection in poisson mode, this alarm is
generated if the signal degradation exceeds the threshold.
l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Issue 02 (2011-10-31)

620
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

If the alarm is generated, the services at the optical port have bit errors, which make the service
signals invalid or even unusable.
Possible Causes
l
The optical port at the local end is faulty.
Procedure
Step 1 Check whether the input optical power of the board is within the normal range. For optical power
specifications of specific boards, see the Product Description. If the optical power is not within
the normal range, see the handing procedure of the IN_PWR_HIGH and IN_PWR_LOW alarms
for troubleshooting.
Step 3 If the alarm persists, the board may be faulty. Replace the faulty board. For details, see the
Supporting Tasks.
----End
Related Information
ITU-T G.709
4.199 OTUk_EXC
Description
The OTUk_EXC is an alarm indicating that the OTUk bit errors cross the threshold. This alarm
is generated when the BIP8 detection is in poisson mode and bit error count exceeds the
threshold.
l
For OptiX OSN 8800, its value is 1, 2, 3
Issue 02 (2011-10-31)

621
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

Possible Causes
l
The attenuation of the received signals is rather large, and the fiber of the transmission line
is abnormal.
Procedure
Step 1 Check whether the receive optical power of the interface is within the normal range by using
Replacement.
----End
Related Information
ITU-T G.709
4.200 OTUk_LOM
Description
The OTUk_LOM is an alarm indicating that the multiframe alignment signal (MFAS) is
abnormal. This alarm occurs when the multiframe locating is out of multiframe (OOM) in three
consecutive milliseconds.
l
Issue 02 (2011-10-31)

622
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

Possible Causes
l
The FEC type is incorrectly configured.
The bit errors in the received signals of the OTU board at the local station are excessive.
Procedure
Step 1 Query the FEC type of the board set on the U2000 to check whether it is consistent with the FEC
type of the board. For specific error correction types, see the Hardware Description. If they are
not consistent, modify the setting on the U2000 to ensure the consistency.
Step 2 Query the performance value of the BIP8 bit errors in the received signals of the board at the
local station through the U2000. If the BIP8 bit errors are excessive, see the handling procedure
of the OTUk_EXC or OTUk_DEG for troubleshooting.
----End
Related Information
ITU-T G.709
4.201 OTUk_TIM
Description
The OTUk_TIM is an alarm indicating OTUk trail trace identifier (TTI) mismatch. This alarm
occurs during the control process when the TTI at the opposite end mismatches that at the local
end when the TIM detection is enabled. The system compares the access point identifiers (API)
in the input signals and the expected API.
three types:
Issue 02 (2011-10-31)

623
OptiX OSN 8800/6800/3800

4 Alarm Processing
termination.

l
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

If the alarm is generated, the signal quality of the services at the optical port is degraded. Hence,
Possible Causes
l
consistent.
The TTI sent at the opposite end is not consistent with the TTI to be received at the local
end.
Procedure
Step 1 Query the TIM detection mode of the local end on the NMU2000. Select the suitable topology
for the local end on the U2000 interface according to networking architecture. If the topology
is point-to-point or point-to-multipoint, only the SAPI is compared for the sink of trail
termination. If the topology is multipoint-to-multipoint, only the DAPI is compared for the sink
of trail termination.
Step 2 If the alarm persists, query whether the TTI sent at the opposite end is consistent with that to be
received at the local end through the U2000. If they are not consistent, query the received TTI
on the U2000. Set the SAPI and the DAPI of the TTI to be received at the local end to be the
same as these of the received TTI.
Issue 02 (2011-10-31)

624
OptiX OSN 8800/6800/3800

4 Alarm Processing
cross-connection.
----End
Related Information
ITU-T G.709
4.202 OUT_PWR_LOW
Description
The OUT_PWR_LOW is an alarm indicating that the output optical power is excessively low.
The output optical power of the laser is excessively low.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The output optical power of the laser is excessively low, which influences the normal
transmission of services.
Possible Causes
l
The input optical power is excessively low.
The laser is aged.
Procedure
Step 1 Check whether the input optical power of the interface of the board at the local station is within
the normal range by using the U2000. For optical power specifications of specific boards, see
the Product Description.
l
Issue 02 (2011-10-31)
If it is not within the normal range, add a suitable attenuation to adjust the input optical
power in the normal range.
625
OptiX OSN 8800/6800/3800

4 Alarm Processing
If it is within the normal range, replace the faulty optical module. For details, see the Parts
Replacement.
----End
Related Information
None
4.203 OWSP_PS
Description
The OWSP_PS is an alarm indicating the OWSP protection switching. This alarm occurs when
the OWSP protection group actuates switching in which the current channel switches to the
protection channel from the working channel.
Attribute
Alarm Severity
Alarm Type
Major
Communication Alarm
Parameters
None

When the OWSP protection group actuates switching, services are transiently interrupted. When
this alarm is reported, the working channel of the OWSP protection group might have faulty
services that need to be restored.
Possible Causes
l
switching. Such a command makes the current channel of the OWSP protection group
Cause 2: The services of the working channel of the OWSP protection group are faulty.
reported.
Procedure
1.
Issue 02 (2011-10-31)

626
OptiX OSN 8800/6800/3800

2.
4 Alarm Processing

1.
to the services, such as R_LOC, R_LOS. If yes, handle the alarms by referring to the
corresponding alarm handling procedures.
2.
----End
Related Information
The optical wavelength shared protection applies to ring networks with distributed services. It
occupies two wavelengths to provide protection for one channel of distributed services among
all stations. For details, see "Optical Wavelength Shared Protection (DCP board)" in the Feature
Description.
4.204 OWSP_STA_INDI
Description
The OWSP_STA_INDI is an alarm indicating the state of the optical wave share protection
group. This alarm is reported when the working or protection channel of the protection group is
faulty or the user runs an external switching command.
Attribute
Alarm Severity
Alarm Type
Minor
Communication Alarm
Parameters
table.
Issue 02 (2011-10-31)

627
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameter
Description
Parameters 1
Indicate the west switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR
Parameters 2
Indicate the east switching request. For example:

l 0x16: LP
l 0X15: SF_P
l 0x13: SF_R
l 0x12: SF_RP
l 0x11: SF_RW
l 0x10: SF_W
l 0x0E: FS_R
l 0x0D: SD_P
l 0x0B: SD_R
l 0x0A: SD_W
l 0x08: MS_R
l 0x06: WTR_R
l 0x03: EXER_R
l 0x00: NR

l
When the OWSP group performs switching, services are transiently interrupted.
When this alarm is reported, the working or protection channel of the OWSP protection
group may have faulty services that need to be restored.
Issue 02 (2011-10-31)

628
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The user issues an external switching command such as the forced switching, manual
The services of the working or protection channel of the OWSP protection group are faulty.
Procedure
necessary,
1.
2.
external switching.
1.
Query whether the related boards for configuring the protection group have alarms, such
as R_LOC, R_LOS. If yes, handle the alarms according to the corresponding alarm handling
procedures.
----End
Related Information
The optical wavelength shared protection applies to ring networks with distributed services. It
occupies two wavelengths to provide protection for one channel of distributed services among
all stations. For details, see "Optical Wavelength Shared Protection (DCP board)" in the Feature
Description.
4.205 PATCH_ACT_TIMEOUT
Description
The PATCH_ACT_TIMEOUT is an alarm indicating that the activated state of the patch
package is excessively long. The alarm is generated when the activated state of the patch package
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

629
OptiX OSN 8800/6800/3800

4 Alarm Processing

The activation of the patch is not in the stable state. If the board is reset in this case, the patch
does not take effect after the system restarts, and the patch is automatically restored to the
deactivated state. The functions of the patch are not available or the bug corrected by the patch
appears again.
Possible Causes
The activated state of the patch package is excessively long.
Procedure
Step 1 If the patch file is confirmed to be correct, run the patch file through the U2000 after the end of
the observation.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the
U2000.
----End
Related Information
None
4.206 PATCH_DEACT_TIMEOUT
Description
The PATCH_DEACT_TIMEOUT is an alarm indicating that the deactivated state of the patch
package is excessively long. The alarm is generated when the deactivated state of the patch
package exceeds the threshold.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The deactivated state indicates that the patch is loaded but the patch is not running. If the board
is reset in this case, the patch is automatically restored to the idle state after the system restarts.
The functions of the patch are not available or the bug corrected by the patch appears again.
Issue 02 (2011-10-31)

630
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The deactivated state of the patch package exceeds the threshold.
Procedure
Step 1 If the patch file is confirmed to be correct, activate the patch file through the U2000.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one by using the
U2000.
----End
Related Information
None
4.207 PATCH_PKGERR
Description
The PATCH_PKGERR is an alarm indicating a patch package file error.
Attribute
Alarm Severity
Alarm Type
Minor
Process
Parameters
None

Package loading management of certain boards may be unavailable if this alarm is generated.
Possible Causes
The patch package of certain boards is lost
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package file.
----End
Related Information
None
Issue 02 (2011-10-31)

631
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.208 PM_BDI
Description
The PM_BDI is an alarm indicating PM back defect in the PM overhead at the optical
demultiplexer unit (ODU) layer. This alarm indicates that ODUs are provided at the remote end
or severe alarms occur at an upper layer.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The PM_BDI alarm is generated at the ODU termination station mapping the services in the
transmit direction. The services in the receive direction are not affected.
Possible Causes
The possible causes of the PM_BDI alarm are as follows:
l
Certain alarms occur at the remote ODU termination station.
The transmit unit at the local end is faulty.
The receive unit at the remote end is faulty.
Procedure
Step 1 Check whether any other higher-level ODU alarm is generated at the remote ODU termination
station. If yes, take priority to clear it, and then check whether the PM_BDI alarm is cleared.
Step 2 If the alarm at the remote end persists, perform an inloop at the local optical interface. If the
PM_BDI alarm is generated, check and modify the configuration.
CAUTION
The loopback causes service interruption.
Step 3 If the alarm persists, replace the board at the local station.
Issue 02 (2011-10-31)

632
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 If the alarm at the remote end persists and the inloop is normally performed at the local optical
station, replace the board at the remote end.
----End
Related Information
None
4.209 PM_BEI
Description
The PM_BEI is an alarm indicating a PM back error in the PM overhead at the optical
demultiplexer unit (ODU) layer. This alarm indicates that PM-BIP check bit errors occur at the
remote end.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

performance
When the PM_BEI alarm is generated, PM-BIP bit errors occur at the ODU termination station,
but the FEC function and are not affected at the local station.
Possible Causes
The possible causes of the PM_BEI alarm are as follows:
l
Certain bit errors occur at the remote ODU termination station.
Procedure
Step 1 Check whether any bit error occurs at the ODU termination station. After clearing the bit error,
check whether the PM_BEI alarm is cleared.
PM_BEI alarm is generated, check and modify the configuration.
Issue 02 (2011-10-31)

633
OptiX OSN 8800/6800/3800

4 Alarm Processing
CAUTION
----End
Related Information
None
4.210 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the ODU PM section
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the PM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_OVER alarm are as follows:
l
The connector is incorrectly connected.
Issue 02 (2011-10-31)

634
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether any higher-level alarm, such as R_LOS or R_LOF, is detected on the U2000. If
yes, take priority to clear it, and then check whether the PM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the board that reports the alarm is within the normal
range. If yes, go to Step 9.
Step 3 Clean the fiber connector at the local station and the receive optical interface on the line board,
Step 4 Check whether the flange is correctly connected to the optical attenuator at the local station, and
whether the attenuation value specified in the optical attenuator is proper. After making sure
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 5 Check whether the transmit optical power at the opposite station is within the normal range. If
not, replace the line board.
Step 6 If the transmit optical power is within the normal range, clean the fiber connector at the opposite
station, and then check whether the alarm is cleared.
Step 7 Check whether the flange is correctly connected to the optical attenuator at the opposite station,
and whether the attenuation value specified in the optical attenuator is proper. After making sure
Step 8 Check whether the fiber cable is faulty. If yes, rectify the fault, and then check whether the alarm
is cleared.
Step 9 Replace the line board that reports the alarm at the local station, and then check whether the
alarm is cleared.
Step 10 Replace the cross-connect and timing board at the local station, and then check whether the alarm
is cleared.
Step 11 Replace the line board at the opposite station, and then check whether the alarm is cleared.
Step 12 Replace the cross-connect and timing board at the opposite station, and then check whether the
alarm is cleared.
----End
Related Information
None
4.211 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the PM BIP error signal is degraded in the ODU
PM section.
Issue 02 (2011-10-31)

635
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the PM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the PM_BIP8_SD alarm are as follows:
l
Procedure
yes, take priority to clear it, and then check whether the PM_BIP8_SD alarm is cleared.
is cleared.
Issue 02 (2011-10-31)

636
OptiX OSN 8800/6800/3800

4 Alarm Processing
alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.212 PM_TIM
Description
The PM_TIM is an alarm indicating that the monitoring trail trace identifier (TTI) mismatches
in the ODU PM overhead.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the PM_TIM alarm is generated, the FEC function and services are not affected.
Possible Causes
The possible cause of the PM_TIM alarm is as follows:
The PM_TTI byte to be received at the local station is incorrectly set.
Procedure
Step 1 Check whether the SM-TTI byte to be received at the board is consistent with the received SMTTI byte. If not, modify it and make sure it is consistent with the received SM-TTI byte.
----End
Issue 02 (2011-10-31)

637
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.213 PORTSWITCH_FAIL
Description
The PORTSWITCH_FAIL is an alarm indicating an optical switch switching failure. This alarm
occurs when the board detects that the optical switch inside the board fails to switch.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the MCA board reports this alarm, the spectrum analysis data at optical ports cannot be
queried.
Possible Causes
Procedure
Step 1 Perform cold reset on the faulty board by using the U2000 or remove the faulty board and insert
it again. For details, see the Supporting Tasks.
Step 2 After the board is reset, perform the spectrum analysis on the MCA again by sing the U2000.
----End
Related Information
None
4.214 POWER_ABNORMAL
Issue 02 (2011-10-31)

638
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm occurs
when the power supply of a board becomes abnormal.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 and Parameter 2 Each bit indicates whether the alarm is generated in the
corresponding voltage. Bit 1 indicates that the alarm is
generated, and bit 0 indicates that no alarm is generated.

When the POWER_ABNORMAL alarm is generated, the power supply functions abnormally,
and the board may not be able to function normally.
Possible Causes
l
Cause 1: The input power of the PIU is abnormal.
Cause 2: The jumper cap of the SCC is not configured.
Cause 3: The power module on the board is faulty.
Query current alarms on the U2000. Then, determine the board that reports the alarm. For
details, see Querying the Current Alarms in the Supporting Task.
Cause 1: The input power of the PIU is abnormal.
Procedure
1.
Check the board alarm indicator to see whether the power input is normal. For the
description of the alarm indicators on the board, see the Hardware Description.
2.
If not, feed the NE power again or replace the DC PDU. For operations of accessing
the power supply, see the Installation Guide.
Cause 2: The jumper cap of the SCC is not configured.

NOTE
The POWER_ABNORMAL alarm is reported when the jumper used to set the used input voltage of
the SCC is configured incorrectly.
Issue 02 (2011-10-31)

639
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
Contact the local representative office of Huawei, and then check whether the jumper
of the SCC is correct. If not, adjust the jumper. For details on the jumper setting of
each SCC, see the Hardware Description.
Cause 3: The power module on the board is faulty.

1.
Check whether the alarm is cleared after you perform cold reset on the board. For the
operations that are performed by using the U2000, see Performing a Cold Reset of a
Board in the Supporting Task. For operations of reseating a board, see the Installation
Guide.
CAUTION
interrupted after you perform cold reset on the board.
2.
If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement.
----End
Related Information
None
4.215 POWER_DIFF_OVER
Description
The POWER_DIFF_OVER is an alarm indicating that the power difference between the active
and standby optical supervisory channels (OSCs) crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The switching of the active and standby channels is affected. As a result, the quality of the
received services is affected.
Issue 02 (2011-10-31)

640
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
During transport, the optical power of signals is excessively attenuated or the board at the
local end is added with an over-large optical attenuator. Hence, the optical power difference
between the active and standby OSCs at the receive end is excessively large.
The optical power difference of signals in the active and standby channels when the board
at the opposite end transmits signals is excessively large.
The detection circuit of the board at the local end is faulty.
Procedure
Step 1 Replace with a suitable optical attenuator. Adjust the optical power in the active and standby
channels of the board at the local station to ensure that the power difference is within 5 dB.
Step 2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the
faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.216 PRBS_LSS
Description
The PRBS_LSS is an alarm indicating loss of the pseudo-random binary sequence (PRBS)
signal. The alarm is generated when the board, on which the PRBS bit error test is performed,
does not receive the PRBS signals from the local board.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

The PRBS test services on the board are interrupted.
Possible Causes
l
Cause 1: The link is abnormal. Hence, the board, on which the PRBS bit error test is
performed, does not receive the PRBS signals from the local board.
Cause 2: The board is faulty, or the line is degraded.
Issue 02 (2011-10-31)

641
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Perform a self-loop by connecting the transmit end to the receive end of the PRBS signals on
the local board.
l
If the alarm is cleared, it indicates that the board is normal. See Step 2 to check the link.
If the alarm persists, it indicates that the board is faulty. Replace the board. For details, see
the Parts Replacement.
Step 2 Check the link and make sure that the link under the PRBS test is a loop. If the alarm persists,
perform a loopback on each point of the link. Find out the abnormal point on the link, and repair
or replace the link.
----End
Related Information
None
4.217 PUM_BCM_ALM
Description
The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser crosses the
threshold. This alarm occurs when the pump laser bias current of the optical amplifier unit crosses
the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Parameter
Description
Parameter 1
Indicates the threshold crossing type. The value is always 0x01.

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken, however, the output optical power of the board is affected in a period of time. This
affects the services
Possible Causes
l
Excessively high or excessively low ambient temperature affects the laser.
Issue 02 (2011-10-31)

642
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is normal. If not, adjust the ambient temperature of the
equipment to a proper degree.
Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect the services.
----End
Related Information
None
4.218 PUM_TEM_ALM
Description
The PUM_TEM_ALM is an alarm indicating that the working temperature of the pump laser
exceeds the threshold. This alarm occurs when the operating temperature of the pump laser on
the optical amplifier unit crosses the threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken, however, the output optical power of the board is affected in a period of time. This
affects the services.
Possible Causes
l
The ambient temperature is excessively high or excessively low.
The cooling system of the pump laser is damaged.
The pump laser has excessive current.
Issue 02 (2011-10-31)

643
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the ambient temperature is normal. If not, improve it.
Step 2 If the alarm persists, perform a warm reset on the faulty board through the U2000.
Step 3 If the alarm persists, you can reseat the faulty board if it does not affect services.
----End
Related Information
None
4.219 R_LOC
Board Type
Alarm Page Link

4.219.1 R_LOC (OCS)

SLO16, or EGSH
4.219.2 R_LOC (OTN)
4.219.1 R_LOC (OCS)

Description
The R_LOC (OCS) is an alarm indicating loss of the clock. This alarm is reported if the line
board fails to extract clock signal from the line signal.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

644
OptiX OSN 8800/6800/3800

4 Alarm Processing

When the R_LOC alarm is generated, the line board fails to extract the clock from the received
optical signals. Consequently, the services are interrupted.
Possible Causes
The possible causes of the R_LOC alarm are as follows:
l
The clock extraction module on the line board is faulty.
The cross-connect and timing board at the opposite station is faulty or is out of position.
Procedure
Step 1 Perform cold reset on the line board that generates the alarm at the local station. Then check
whether the R_LOC alarm is cleared.
Step 2 If the alarm persists, the clock extraction module on the line board may be faulty. In this case,
replace the line board, and then check whether the R_LOC alarm is cleared.
Step 3 If the alarm persists, check whether the cross-connect and timing board at the opposite station
is faulty. If yes, replace the cross-connect and timing board, and then check whether the R_LOC
alarm is cleared.
----End
Related Information
None
4.219.2 R_LOC (OTN)

Description
The R_LOC is an alarm indicating loss of the clock on the receive line. This alarm occurs when
the clock signal fails to be extracted from the received signals.
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

Services at this port are interrupted.
Issue 02 (2011-10-31)

645
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The link is abnormal and the board cannot normally extract clock signals.
The setting of the board clock tracing is incorrect.
Procedure
Step 1 Perform a self-loop on the board. Then, check whether the physical link is normal. If there is
any abnormity, such as OTUk_LOF, remove the fault.
Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire
network planning. Adjust the board clock setting if it is incorrect.
----End
Related Information
None
4.220 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is a critical alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input
interface of the EFI1 board changes.
interface of the EFI board changes.
interface of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
Issue 02 (2011-10-31)

646
OptiX OSN 8800/6800/3800

4 Alarm Processing
The status of the alarm input of the EFI1 board changes.
The alarm input interface of the EFI1 board reports the alarm by default. The alarm is
reported in the default state.

l
The status of the alarm input of the EFI board changes.
The alarm input interface of the EFI board reports the alarm by default. The alarm is reported
in the default state.

l
The status of the alarm input of the AUX board changes.
The alarm input interface of the AUX board reports the alarm by default. The alarm is
Procedure
Step 1 For the OptiX OSN 8800, Check whether the status of the external equipment (for example,
access control system) connected to the alarm input interface of the EFI1 board changes. If that
is the case, remove the fault of the external equipment.
access control system) connected to the alarm input interface of the EFI board changes. If that
access control system) connected to the alarm input interface of the AUX board changes. If that
Step 4 If no external equipment is connected to the alarm input interface, set the input interface to
Unused and the alarm is cleared.
----End
Related Information
None
4.221 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is a warning alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Issue 02 (2011-10-31)

647
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

interface of the EFI1/EFI2 board changes
Possible Causes
l
Procedure
Step 1 Check whether the status of the external equipment (for example, access control system)
connected to the alarm input interface of the EFI1 board changes. If that is the case, remove the
fault of the external equipment.
connected to the alarm input interface of the EFI board changes. If that is the case, remove the
connected to the alarm input interface of the AUX board changes. If that is the case, remove the
----End
Related Information
None
Issue 02 (2011-10-31)

648
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.222 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is a major alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

interface of the EFI1 board changes.
Possible Causes
l
Procedure
Issue 02 (2011-10-31)

649
OptiX OSN 8800/6800/3800

4 Alarm Processing
----End
Related Information
None
4.223 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is a minor alarm of the alarm input.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

interface of the EFI1board changes.
Possible Causes
l
Issue 02 (2011-10-31)

650
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
----End
Related Information
None
4.224 REM_SD
Description
The REM_SD is an alarm indicating that the remote signal is degraded. When the received
signals on the client side of the board at the opposite station is degraded, the alarm signal is
inserted. The alarm is generated when the client side of the board at the local station detects the
signals.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

The QoS of the service signals is affected. In a serious situation, the services are interrupted.
Issue 02 (2011-10-31)

651
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The client side of the OTU at the opposite end has the B1_EXC alarm.
The demultiplexed client signals on the WDM side of the OTU at the local end have the
B1_EXC alarm.
Procedure
Step 1 Check whether the OTU at the opposite end has the B1_EXC alarm. If yes, see the procedure
of handling B1_EXC to handle the alarm.
Step 2 If the alarm persists, check whether demultiplexed client signals on the WDM side of the OTU
at the local end have the B1_EXC alarm. If yes, see the procedure of handling B1_EXC to handle
the alarm.
----End
Related Information
None
4.225 RL_CRITICAL_HI
Description
Critical high return loss alarm. This alarm is generated when the return loss is higher than the
upper threshold of the return loss alarm.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

This alarm is generated in case of a fiber connection error. When this alarm is generated, services
may be interrupted.
Possible Causes
l
The fiber near the Raman board is broken.
The fiber near the Raman board is over-bent or pressed.
The connector of the fiber near the Raman board is unclean.
The connector of the fiber near the Raman board is installed incorrectly.
Issue 02 (2011-10-31)

652
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether
the fiber near the Raman board is properly connected. If not, reconnect it.
Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If
yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by
means of splicing.
Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean.
If not, clean it again and then connect the fiber properly.
----End
Related Information
None
4.226 RL_CRITICAL_LOW
Description
Critical low return loss alarm. This alarm is generated when the return loss is lower than the
lower threshold of the return loss alarm.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

This alarm is generated in case of a fiber connection error. When this alarm is generated, services
may be interrupted.
Possible Causes
l
The fiber near the Raman board is broken.
The fiber near the Raman board is over-bent or pressed.
The connector of the fiber near the Raman board is unclean.
The connector of the fiber near the Raman board is installed incorrectly.
Issue 02 (2011-10-31)

653
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Then check whether
the fiber near the Raman board is properly connected. If not, reconnect it.
Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If
yes, spool the fiber again. If the fiber is broken because of the press, replace it or repair it by
means of splicing.
Step 3 If the alarm still persists, check whether the end face of the fiber near the Raman board is clean.
If not, clean it again and then connect the fiber properly.
----End
Related Information
None
4.227 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that the regenerator section performance events cross
the threshold. The alarm occurs when the performance module reports the threshold crossing of
the performance events in the regenerator section
Attribute
Alarm Severity
Alarm Type
Minor
Service alarm
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l
The laser of the board at the opposite station is degraded.
The input optical power of the board at the local station is excessively high or excessively
low.
The clock at the opposite station is degraded.
The fiber is degraded.
Issue 02 (2011-10-31)

654
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the fiber is aged or has excessive attenuation. If that is the case, remove the fault
of the fiber.
Step 2 Query whether the board has the B1_EXC, B2_EXC, B1_SD, or B2_SD alarm by using the
U2000. If that is the case, clear the alarm.
Step 3 Check whether the input optical power of the board at the local station is within the normal range
by using the U2000. For optical power specifications of specific boards, see the Product
Description.
l
If the optical power displayed on the U2000 is normal, the board may be faulty. Replace
If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
a value within the normal range.
Step 4 If the alarm persists, remove the fault of the board at the opposite station.
----End
Related Information
None
4.228 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the timing of the real time clock (RTC) fails.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the alarm is reported, the system employs the soft timing. Hence, the timestamp precision
of the system decreases.
Possible Causes
l
The clip of the RTC clock is damaged.
The temperature of the board is excessively high.
Issue 02 (2011-10-31)

655
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the board temperature is normal. If it is abnormal, replace the fan.
Step 2 If the alarm persists, replace the faulty SCC. For details, see the Parts Replacement.
----End
Related Information
RTC is also called NE timing.
4.229 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the ID of the priority table. Valid values are as follows:

l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source

The switching performs on the working clock source of the board, which influence the user
services.
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1: The fiber connection is faulty.

656
OptiX OSN 8800/6800/3800

4 Alarm Processing
Cause 2: The upstream station generates the alarm.
Cause 1: The fiber connection is faulty.
Procedure
1.
Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
see the Supporting Tasks.
2.
If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
Cause 2: The upstream station generates the alarm.

1.
If the alarm persists, check whether the S1_SYN_CHANGE alarm is generated at the
upstream station. If yes, repeat steps to clear the S1_SYN_CHANGE alarm at the
upstream station. The S1_SYN_CHANGE alarm at the local station is then
----End
Related Information
4.230 SCC_LOC
Description
The SCC_LOC is an alarm indicating that the SCC losses the clock. The alarm occurs when the
OSC board detects that the clock source sent by the SCC board is lost.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The NE is out of control and the OSC is interrupted.
Possible Causes
l
The SCC board is faulty.
The alarm is generated during the cold reset of the SCC board. The alarm is automatically
cleared after the cold reset is complete.
Issue 02 (2011-10-31)

657
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Query the reset record of the SCC board.
l
If the time when the alarm is cleared is consistent with the time that the SCC is reset, the
alarm may be caused by resetting the SCC. There is no need to handle the alarm.
If the time when the alarm is cleared is not consistent with the time that the SCC is reset,
the board may be faulty. Replace the faulty board. For details, see the Parts Replacement.
Step 2 If the alarm persists, the SCC board may be faulty. Replace the faulty SCC board. For details,
see the Parts Replacement.
----End
Related Information
None
4.231 SEC_RADIUS_FAIL
Description
Excessive failures in radius authentication. The SEC_RADIUS_FAIL is an alarm indicating that
a large number of authentification failures occur on the NE within a short period.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

User login fails.
Possible Causes
A large number of RADIUS authentication failures occur on the NE within a short period.
Procedure
Step 1 Check whether the user account expired.
Step 2 Check whether the user password is changed or the user access policy is changed by the
administrator.
Step 3 Check whether an unauthorized user attempts to log in to the network device.
Issue 02 (2011-10-31)

658
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 4 Check whether the shared key between the GNAS and the radius server is correct.
----End
Related Information
None
4.232 SERVICE_TYPE_EXCEED_LICENSE
Description
The SERVICE_TYPE_EXCEED_LICENSE is an alarm indicating that the service type exceeds
the license limit. The alarm indicates that the type of configured services exceeds the license
limit.
Attribute
Alarm Severity
Alarm Type
Major
Service
Parameters
table.
Parameter 1 Indicates the ID of the subrack, where the service type exceeds the license limit.

When the SERVICE_TYPE_EXCEED_LICENSE alarm is generated, neither the existing
services nor the operation of the system is affected. The subrack where the alarm is generated,
however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service type configured in the subrack exceeds the license limit.
Procedure
Step 1 According the alarm parameter, check whether the type of configured services in the subrack
exceeds the license limit by using the U2000.
Issue 02 (2011-10-31)

659
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 2 If yes, assign a proper license.

Step 3 If no proper license is available, purchase the license with a higher version from Huawei.
----End
Related Information
None
4.233 SERVICE_CAPACITY_EXCEED_LICENSE
Description
The SERVICE_CAPACITY_EXCEED_LICENSE is an alarm indicating that the service
capacity exceeds the license limit. This alarm indicates that the service capacity configured in
the subrack exceeds the license limit.
Attribute
Alarm Severity
Alarm Type
Major
Service
Parameters
table.
Parameter 1 Indicates the ID of the subrack, where the service capacity exceeds the license
limit.

When the SERVICE_CAPACITY_EXCEED_LICENSE alarm is generated, neither the existing
services nor the operation of the system is affected. The subrack where the alarm is generated,
however, cannot be configured with services corresponding to the alarm.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.
Issue 02 (2011-10-31)

660
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 According to the alarm parameters, query the license capacity for the subrack where the alarm
is generated. Then, select a proper license capacity to meet the service requirements of the
subrack.
Step 2 If no license with a proper capacity can be used, purchase the license with a proper capacity
from Huawei.
----End
Related Information
None
4.234 SHELF_AREA_POWER_OVER
Description
The SHELF_AREA_POWER_OVER is an alarm indicating that the total optical power
consumption of the subrack exceeds the threshold. This alarm is generated when the total power
consumption of the boards in each partition of the subrack is higher than or equal to the power
consumption threshold for each partition.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates the subrack ID.
Parameter 2
Indicates the number of the partition.

The total power consumption of the boards in each partition of the subrack exceeds the threshold.
This puts the system in a very dangerous state. If the system runs in this state for a long time,
the power supply unit of the subrack may work abnormally and a power failure may occur in
the subrack.
Issue 02 (2011-10-31)

661
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The total power consumption of the boards in each partition of the subrack is higher than or
equal to the power consumption threshold for each partition.
Procedure
Step 1 Remove the board from the subrack. Wait until the alarm is cleared.
----End
Related Information
None
4.235 SPAN_LOSS_HIGH
Description
Line insertion loss is excessively high. The alarm is generated when the actual line insertion loss
is higher than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

If the line insertion loss is excessively high, service signals may be instable and BER may
increase. Then, the alarm indicating excessively low path optical power may occur and the
performance may be abnormal.
Possible Causes
l
Issue 02 (2011-10-31)
The line fiber is aged.

662
OptiX OSN 8800/6800/3800

4 Alarm Processing
The line insertion loss is increased.
The alarm threshold is incorrect.
The insertion loss of a board on the line is abnormal.
The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fiber connections are abnormal and whether the fibers are aging. If the
line fiber connections are abnormal or the fibers are aging, reconnect the fibers or replace the
aging fibers.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation
to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low,
set the alarm threshold according to the planning of the live network.
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see
Step 5 If none of preceding problems occur, re-sample the reference value.
----End
Related Information
4.236 SPAN_LOSS_LOW
Description
Line insertion loss is excessive low. The alarm is generated when the actual line insertion loss
is lower than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Issue 02 (2011-10-31)

663
OptiX OSN 8800/6800/3800

4 Alarm Processing
Name
Meaning
Parameter 1

When the line insertion loss is excessively low, an alarm indicating that the optical power of the
channel is excessively high may be generated and the performance may be abnormal.
Possible Causes
l
Aging fibers on the line are replaced with new fibers, or the line insertion loss is decreased.
The sampled reference value of the line attenuation is inappropriate.
Procedure
Step 1 Check whether the line fibers are aging. If the line fibers are new fibers, enable the ALC function
and then sample the reference value again.
Step 2 Check whether any VOA is not configured on the line. If yes, manually adjust the attenuation
to the normal value.
Step 3 Check whether the alarm threshold is excessively low. If the alarm threshold is excessively low,
set the alarm threshold according to the planning of the live network.
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, see
Step 5 If none of preceding problems occur, re-sample the reference value.
----End
Related Information
4.237 SLAVE_WORKING
Description
The SLAVE_WORKING is an alarm indicating the working state of the protection board. If the
protection cross-connect board is selected for the service bus of the service board, and if the
slave clock is selected as the system clock, the SLAVE_WORKING alarm is reported.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Issue 02 (2011-10-31)

664
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

When the SLAVE_WORKING alarm is generated, the system is not affected. This alarm just
indicates that the protection cross-connect board is selected for the service bus of the service
board, and the slave clock is selected as the system clock.
Possible Causes
The possible causes of the SLAVE_WORKING alarm are as follows:
l
Cause 1: The active cross-connect and timing board is not in position.
Cause 2: The active cross-connect and timing board is faulty.
Cause 3: The service board is faulty.
Query current alarms on the U2000. Determine the board that reports the alarm. For details,
see Querying the Current Alarms in the Supporting Task.
Cause 1: The active cross-connect and timing board is not in position.
Procedure
1.
Check whether the active cross-connect and timing board is loose. If yes, tighten the
active cross-connect and timing board. For details, see the Installation Guide. Then,
2.
Cause 2: The active cross-connect and timing board is faulty.

1.
Replace the active cross-connect and timing board. For details, see Parts
2.

1.
Perform cold reset on the service board that reports the alarm by using the U2000, or
reseat the service board that reports the alarm. For the operations that are performed
on the U2000, see Performing a Cold Reset of a Board in the Supporting Task. For
operations of reseating a board, see the Installation Guide. Then, check whether the
alarm is cleared.
2.
If the alarm persists, replace the board that reports the alarm. For details, see Parts
Replacement.
----End
Related Information
The working cross-connect board refers to the cross-connect board inserted in the slot of a smaller
ID.
The protection cross-connect board refers to the cross-connect board inserted in the slot of a
larger ID.
Issue 02 (2011-10-31)

665
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.238 SM_BDI
Description
The SM_BDI is an SM back defect indication at the optical transponder unit (OTU) layer. This
alarm indicates that OTUs are provided at the remote end or severe alarms occur at an upper
layer.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The SM_BDI alarm just indicates that certain alarms occur at the OTU termination station
mapping the services in the transmit direction. The services in the receive direction are not
affected.
Possible Causes
The possible causes of the SM_BDI alarm are as follows:
l
Certain alarms occur at the remote OTU termination station.
Procedure
Step 1 Check whether any other higher-level OTU alarm is generated at the remote OTU termination
station. If yes, take priority to clear it, and then check whether the SM_BDI alarm is cleared.
SM_BDI occurs, check and modify the configuration.
CAUTION
Issue 02 (2011-10-31)

666
OptiX OSN 8800/6800/3800

4 Alarm Processing
----End
Related Information
None
4.239 SM_BEI
Description
The SM_BEI is an SM back error indication at the optical transponder unit (OTU) layer. This
alarm indicates that SM-BIP errors occur at the remote end.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the SM_BEI alarm is generated, SM_BIP errors occur at the remote OTU termination
station, but the FEC function and performance are not affected at the local station.
Possible Causes
The possible causes of the SM_BEI alarm are as follows:
l
Certain bit errors occur at the remote OTU termination station.
Procedure
Step 1 Query the performance of the board at the remote OTU termination station, and clear the bit
errors at the remote end.
----End
Related Information
None
Issue 02 (2011-10-31)

667
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.240 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the OTU SM section
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the SM_BIP8_OVER alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_OVER alarm are as follows:
l
Procedure
yes, take priority to clear it, and then check whether the SM_BIP8_OVER alarm is cleared.
Issue 02 (2011-10-31)

668
OptiX OSN 8800/6800/3800

4 Alarm Processing
Step 8 Check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the
alarm is cleared.
alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.241 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the SM BIP error signal is degraded in the OTU
SM section.
Attribute
Alarm Severity
Alarm Type
Major
Service alarm
Parameters
None

When the SM_BIP8_SD alarm is generated, the service transmission quality is affected.
Possible Causes
The possible causes of the SM_BIP8_SD alarm are as follows:
Issue 02 (2011-10-31)

669
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
yes, take priority to clear it, and then check whether the SM_BIP8_SD alarm is cleared.
is cleared.
alarm is cleared.
is cleared.
alarm is cleared.
----End
Related Information
None
4.242 SM_IAE
Issue 02 (2011-10-31)

670
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The SM_IAE is alarm indicating an SM incoming alignment error (IAE) in the OTU SM section.
When the ODU frame is synchronously mapped into the OTU frame, the IAE flag is set to true
if the frame alignment errors occur. When the IAE errors are detected at the sink, the sub-frame
alignment bit errors occur in the received services.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the SM_IAE alarm is generated, the service availability is affected.
Possible Causes
The possible causes of the SM_IAE alarm are as follows:
l
The clock jitter event occurs in the transmit unit at the remote end (namely, the source of
the OTU/ODU adaptation function).
The frame offset on the board termination side of the remote end (namely, the source of
the OTU/ODU adaptation function) is inaccurate.
The board FEC processing chip at the remote end (namely, the source of the OTU/ODU
adaptation function) is faulty.
Procedure
Step 1 Adjust the frame offset on the board system side of the remote end (namely, the source of the
OTU/ODU adaptation function).
Step 2 If the alarm persists, replace the board at the remote end (namely, the source of the OTU/ODU
adaptation function).
----End
Related Information
None
4.243 SM_TIM
Issue 02 (2011-10-31)

671
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The SM_TIM is an alarm indicating the section monitoring TTI mismatch in the OTU SM
overhead.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the SM_TIM alarm is generated, the FEC function and the services are not affected.
Possible Causes
The possible causes of the SM_TIM alarm are as follows:
l
The expected SM_TIM byte at the local end is incorrectly set.
The value of the SM_TTI byte transmitted at the remote end is incorrectly configured.
The fiber is incorrectly connected.
Procedure
Step 1 According to the service network, determine the expected setting of the SM_TTI byte in the
relevant position.
Step 2 Check whether the SM-TTI byte to be received at the board is consistent with the received SMTTI byte. If not, modify the incorrect SM-TTI byte to be received.
Step 3 If the received SM-TTI byte is incorrect, check whether the fiber connection at the next local
station is correct. If not, modify the connection.
Step 4 Check whether the setting of the transmitted SM-TTI byte in the upstream services is correct.
If not, modify the transmitted SM-TTI byte in the upstream services.
----End
Related Information
None
4.244 SNCP_FAIL
Issue 02 (2011-10-31)

672
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
table.
Name
Meaning
Parameter 1 and Parameter 2
Indicates the protection group ID.

When the SNCP switching fails, the services configured with SNCP are not protected, and the
services in this SNCP group are interrupted.
Possible Causes
During the SNCP switching, the service grooming fails.
Procedure
Step 1 Reset the SCC board to re-configure all the services.
----End
Related Information
None
4.245 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots bundled at the
LCAS source is not consistent with the number of timeslots bundled at the LCAS sink. When
the number of upstream (or downstream) timeslots is not consistent with the number of
downstream (or upstream) timeslots for a VCTRUNK, the SO_SK_MISMATCH alarm is
reported.
Issue 02 (2011-10-31)

673
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Communication alarm
Parameters
None

In the case of the SO_SK_MISMATCH alarm, services are not affected.
CAUTION
If the timeslots at the sink are added to other VCTRUNKs after the SO_SK_MISMATCH alarm
is reported, services in the VCTRUNK are interrupted. Do not proceed with other operations
before making sure that source and sink have the same number of timeslots.
Possible Causes
The possible cause of the SO_SK_MISMATCH is as follows:
The LCAS source and LCAS sink have different number of configured timeslots.
NOTE
If timeslots except the last timeslot are deleted at the sink instead of at the source, the SO_SK_MISMATCH
alarm is generated.
If the last timeslot is deleted at the sink instead of at the source, the SO_SK_MISMATCH alarm is not
generated.
Procedure
Step 1 View the SO_SK_MISMATCH alarm on the U2000, and then determine the number of the
VCTRUNK where the SO_SK_MISMATCH alarm is generated.
Step 2 On the U2000, check whether the number of upstream (or downstream) timeslots is consistent
with the number of downstream (or upstream) timeslots bundled in the VCTRUNK. If not, make
them consistent by adding or deleting some timeslots, and then check whether the
SO_SK_MISMATCH alarm is cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

674
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.246 SPEED_OVER
Description
The SPEED_OVER is an alarm indicating that the data rate exceeds the set limit. The
SPEED_OVER is an alarm indicating the mismatch between the rate of the monitored optical
interface and the preset one. This alarm is generated when a board detects that the received rate
mismatches the preset one.
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
None

When the SPEED_OVER alarm is generated, the received service rate mismatches the preset
one. The board cannot carry the service and the service is interrupted.
Possible Causes
l
The set rate of the optical interface is incorrect.
Procedure
Step 1 Query the set rate and actual rate on the U2000, and determine whether the set rate is incorrect.
Step 2 If the set rate is incorrect, set a correct one on the U2000.
Step 3 If the alarm persists, check whether the input optical power is normal. If the input optical power
is excessively high or excessively low, adjust it.
Step 4 If the alarm persists, check whether the board chip is faulty, that is, whether there is a
HARD_BAD or a HARD_ERR alarm at the local station. If yes, replace the relevant board. For
details, see the Parts Replacement
----End
Related Information
None
Issue 02 (2011-10-31)

675
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.247 STORM_CUR_QUENUM_OVER
Description
Alarm storm. Certain alarms on the SCC board may be lost when the alarm queue is full. This
alarm indicates that the alarm module is in the alarm storm state.
Attribute
Alarm Severity
Alarm Type
Minor
Service
Parameters
None

Certain alarms may be overwritten when there are excessive alarms. In this case, the alarm status
of the NE is inappropriate.
Possible Causes
The alarm queue fails to contain all the alarms when there are excessive alarms.
Procedure
Step 1 Handle the existing alarms (except the STORM_CUR_QUENUM_OVER alarm). The
STORM_CUR_QUENUM_OVER alarm clears when the number of the current alarms is equal
to or below the STORM_CUR_QUENUM_OVER alarm threshold.
----End
Related Information
None
4.248 SUBRACK_COMM_PS
Description
SUBRACK_COMM_PS is an alarm indicating ETH2 interface status. This alarm indicates that
the ETH2 interface on the master subrack is in working state when the master subrack is under
inter-subrack communication protection.
Issue 02 (2011-10-31)

676
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

An NE detects that the link between subracks is broken, but communication between subracks
is protected.
Possible Causes
l
Cause 1: The ETH2 interface on the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
Cause 1: The ETH2 interface on the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
Procedure
1.
If the ETH2 interface on the master subrack is in working state when the master
subrack is under inter-subrack communication protection, the original working
channel where the ETH1 interface is located is malfunctioning. Check for any
LAN_LOC alarm on the NE. If the alarm is reported, restore the subrack connection
according to the alarm processing method. After the connection is restored, intersubrack communication protection automatically switches the current working
channel to the original working channel. In this manner, the ETH2 interface stops
working and then the SUBRACK_COMM_PS alarm is cleared.
----End
Related Information
4.249 SUBRACK_ID_MISMATCH
Description
The SUBRACK_ID_MISMATCH is an alarm indicating mismatch of the subrack ID.
Issue 02 (2011-10-31)

677
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1
Indicates mismatch of the logical subrack ID.

The DIP switch of the subrack ID mismatches with the subrack ID saved by the software, which
leads to the abnormal communication between the boards.
Possible Causes
The DIP switch of the subrack ID is changed. The subrack ID detected by the NE software and
board software is mismatched with the actual subrack ID.
Procedure
Step 1 Modify the DIP switch of the AUX to the subrack ID displayed in the statistics diode of the SCC
or power off the subrack
Step 2 Modify the DIP switch to "0", and thus the alarm is cleared.
----End
Related Information
4.250 SUBRACK_LOOP
Description
The SUBRACK_LOOP is an alarm indicating the loop of the subrack. The alarm occurs when
the cascaded subracks form a closed loop.
Issue 02 (2011-10-31)

678
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None

The network storm occurs to the intra-subrack communication, which leads to unavailability of
the intra-subrack communication.
Possible Causes
l
In the master/slave subrack mode, the internal network interfaces are connected in a closed
loop.
The AUX board is faulty, which leads to the abnormal communication.
Procedure
Step 1 Check the cable connection between the subracks to ensure that the subracks are connected in
a chain manner.
Step 2 Check whether the alarm is cleared. If the alarm persists, perform a warm reset or cold reset on
the faulty board through the U2000.
Step 3 If the alarm persists, replace the AUX board.
----End
Related Information
4.251 SUBRACK_TYPE_MISMATCH
Description
The alarm indicating that the subrack configured does not match the type of the physical subrack.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 02 (2011-10-31)

679
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
table.
Name
Meaning
Parameter 1
The ID of the subrack.

The alarm does not affect the existing services and the operation of the system. The subrack that
generates this alarm, however, cannot be configured with services.
Possible Causes
l
Cause 1: The subrack configured for the SCC does not match the type of the physical
subrack.
Cause 1: The subrack configured for the SCC does not match the type of the physical
subrack.
Procedure
1.
Determine whether the logical subrack or the physical subrack is incorrect according
to the actual network.
2.
If the logical subrack is incorrect, delete the incorrect subrack from the U2000 and
then configure a correct logical subrack that is consistent with the physical subrack.
3.
If the physical subrack is incorrect, replace the subrack with a correct one and then
configure a correct subrack ID. For details on the operations, see Feature
Description.
4.
----End
Related Information
4.252 SUM_INPWR_HI
Description
The SUM_INPWR_HI is an alarm indicating that the input optical power is excessively high.
The alarm occurs when the input optical power of the multiplexed signals exceeds the threshold.
Issue 02 (2011-10-31)

680
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The optical modules of the boards at the local station and downstream station may be damaged.
The services have bit errors, or are even interrupted.
Possible Causes
l
The output optical power of the board at the upstream station is normal and the power of
the received optical signals accessed by the board at the local station is excessively high.
The proper attenuation is not added.
The output optical power of the board at the upstream station or opposite station is
excessively high.
Procedure
Step 1 Check whether the input optical power of the input interface of the board at the local station is
within the normal range by using an optical power meter. For optical power specifications of
specific boards, see the Product Description. If the power is not within the normal range, add
proper attenuation by placing a fixed attenuator or a VOA.
Step 2 If the alarm persists, check whether the output optical power of the board at the upstream stations
is within the normal range by using the U2000. For optical power specifications of specific
boards, see the Product Description. If the input optical power of the board at the local station
is excessively high, handle the alarm according to the handling procedure of the IN_PWR_HIGH
alarm. If the output optical power of the boards at the upstream stations is excessively high,
respectively check whether the corresponding input and output optical power of each upstream
station are within the normal range.
l
If the input and output optical power of the board at the upstream station are not within the
normal range, adjust the input optical power to a value within the normal range. For optical
power specifications of specific boards, see the Product Description.
If the input optical power of the board at the upstream station is within the normal range
but the output optical power is not, the board at the upstream station may be faulty. Replace
----End
Related Information
None
Issue 02 (2011-10-31)

681
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.253 SW_SNCP_PS
Description
The SW_SNCP_PS is an alarm indicating the SW SNCP protection switching. This alarm occurs
when the SW SNCP protection group actuates switching in which the current channel switches
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the SW SNCP protection group actuates switching, services are transiently interrupted.
When this alarm is reported, the working channel of the SW SNCP protection group might have
Possible Causes
l
switching. Such a command makes the current channel of the SW SNCP protection group
Cause 2: The services of the working channel of the SW SNCP protection group are faulty.
reported.
Procedure
1.
2.

1.
Issue 02 (2011-10-31)
to the services, such as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF,
OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
REM_SF, ODUk_LOFLOM, B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC,
OTUk_DEG, OTUk_EXC, or REM_SD. If yes, handle the alarms by referring to the
corresponding alarm handling procedures.
682
OptiX OSN 8800/6800/3800

2.
4 Alarm Processing
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.254 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the state of the Sub-Wavelength SNCP
Attribute
Alarm Severity
Alarm Type
Minor
Communication alarm
Parameters
table.
Parameter
Description
Parameters 1

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l
Issue 02 (2011-10-31)
When switching is performed in the SW SNCP group, the services are transiently
interrupted.
683
OptiX OSN 8800/6800/3800

4 Alarm Processing
When the alarm is reported, the working or protection channel of the SW SNCP group may
have faulty services that need to be restored.
Possible Causes
l
The user issues an external switching command such as forced switching, manual switching
The services of the working or protection channel of the SW SNCP group are faulty.
Procedure
necessary.
1.
2.
external switching.
1.
Query whether the related boards for configuring the protection group have the alarm such
as R_LOF, R_LOS, R_LOC, HARD_BAD, OTUk_LOF, OTUk_LOM, OTUk_AIS,
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, REM_SF, ODUk_LOFLOM,
B1_EXC, ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC, or REM_SD.
If that is the case, handle the alarms according to the corresponding handling procedure of
the alarm to restore the services of the working or protection channel.
2.
that is the case, the services are automatically switched to the working channel. The alarm
is cleared. If the attribute is Non-Revertive, set it to Revertive and the alarm is cleared.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in the WTR
state. This alarm requires no handling. After the WTR time, the alarm is cleared.
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.
4.255 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the activation times out.
During loading of the software package, the alarm occurs when the operation is not committed
120 seconds after activation operation.
Issue 02 (2011-10-31)

684
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Critical
Process alarm
Parameters
None

The services are not affected.
Possible Causes
The operation is not committed 120 seconds after activation operation during loading of the
software package.
Procedure
Step 1 Commit the activation operation again. If the alarm persists, check whether the software version
is correct. If the software version is incorrect, roll back the NE to the version before package
loading, and select the required software package on the NMS to load the package again.
----End
Related Information
None
4.256 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic matching function
is disabled.
NOTE
After the automatic matching function is enabled, when a board is added to an NE, the system automatically
checks whether the board software matches the NE software. If not, the SCC board upgrades the board software
of the new board.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Issue 02 (2011-10-31)

685
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

The SCC board cannot automatically update the software of the board that is newly inserted. If
the software of the new board mismatches the NE software, certain functions of the NE may
operate abnormally.
Possible Causes
The automatic matching switch is turned off.
Procedure
Step 1 If the alarm persists, contact Huawei engineers.
----End
Related Information
None
4.257 SWDL_BD_EXCLUDE
Description
The SWDL_BD_EXCLUDE is an alarm indicating that a board is excluded from software
download during software package downloading. This alarm occurs when some board failed
because of a failure to communicate with the SCC board or insufficient flash space.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters
None

After package loading, the software of the board excluded from software download mismatches
with the NE software. This may result in damage to services. Hence, handle this alarm in time.
Possible Causes
l
Issue 02 (2011-10-31)
Cause 1: The board is offline.

686
OptiX OSN 8800/6800/3800

4 Alarm Processing
Cause 2: The communication between the board and the SCC board is abnormal.
Cause 3: The flash memory space on the board is insufficient.
Cause 4: The board is repeatedle reset after activation because of a board software fault.
Procedure
Step 1 On the DC window of the U2000, view the information about the boards that are isolated during
package loading.
Step 2 Check whether the isolated boards are offline. If the isolated boards are offline, get them online.
Step 3 Check whether any COMMUN_FAIL alarm is reported on the isolated boards. If the alarm is
reported, handle the problem by referring to the alarm processing mehod.
Step 4 Check whether the flash memory space on the boards is sufficient. If the space is insufficient,
clean up the boards to get sufficient space.
Step 5 Check whether the downloaded software matches with the isolated board version. If the software
mismathches with the board verison, download the correct software again.
Step 6 If the preceding items are checeked and the results are normal, select the isolated boards on the
DC window, download software agagin, and then activate the software.
Step 7 After handling all isolated boards, the SWDL_BD_EXCLUDE alarm is cleared when the board
isolation is released.
----End
Related Information
None
4.258 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm indicating that the SCC board is changed. The
system re-checks whether the board software of each board matches the NE software after the
NE starts up upon a power failure, the SCC unit is replaced, or cold reset is performed on the
SCC unit. The alarm occurs when the board software of a board mismatches the NE software.
It indicates that the board software mismatches the NE software.
Attribute
Alarm Severity
Alarm Type
Critical
Equipment alarm
Parameters
None
Issue 02 (2011-10-31)

687
OptiX OSN 8800/6800/3800

4 Alarm Processing

l
When the alarm occurs, the automatic matching function for package loading is disabled.
The software version of the unit is inconsistent with that of the SCC board. Certain functions
of the NE may operate abnormally.
Possible Causes
l
After the NE is powered off, a board is inserted and the software version of the board is
inconsistent with that of the SCC board.
The SCC board is replaced, and the software package of the new SCC is inconsistent with
the software version of the board.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.259 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating a commitment failure. During loading of
the software package, the alarm occurs when the commitment operation fails.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The package loading fails and the upgrade of the software version fails.
Possible Causes
During the package loading, the dual-partition board fails in copying the new software from one
partition to the other.
Issue 02 (2011-10-31)

688
OptiX OSN 8800/6800/3800

4 Alarm Processing
NOTE
The dual-partition board has two file systems. The two partitions are of mutual backups. In normal states, every
file is saved in both partitions.
Procedure
Step 1 On the U2000, use a correct software package to perform the package loading on the board.
----End
Related Information
None
4.260 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the package loading is performed on the
NE. This alarm occurs when the NE is performing the package loading. After the NE finishes
the commitment operation, the alarm is cleared.
Attribute
Alarm Severity
Alarm Type
Warning
Process alarm
Parameters
None

The working/protection backup function of the SCC board is disabled.
Possible Causes
The NE is performing the package loading operation.
Procedure
Step 1 The software package loading is still in process. Wait until the package loading is complete.
Then, the alarm is cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

689
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.261 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that no matching board software is
available. After an NE is loaded with a customized software package, when a board is inserted,
the software for the board is not found in the customized software package. In this case, the
board cannot be matched automatically and therefore the alarm occurs.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual
requirement.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The software version of the unit is inconsistent with that of the SCC board. Certain functions of
the NE may operate abnormally.
Possible Causes
The user uses the customized software package, in which no software for the normal board is
found.
Procedure
Step 1 On the U2000, choose correct software version to perform a normal package loading again.
----End
Related Information
None
Issue 02 (2011-10-31)

690
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.262 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the package version consistency check
fails. The alarm indicates that the software version information (similar to the file list category)
of the software package is not consistent with the actual software version information.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The software versions on the NE are inconsistent. Certain functions of the NE may operate
abnormally.
Possible Causes
The file of the software package is faulty, and the software version information of the software
package is not consistent with the actual software version information.
Procedure
Step 1 On the U2000, use a correct software package to perform package loading on the board.
----End
Related Information
None
4.263 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the NE rollback fails. If certain
board rollbacks fail when the NE performs the rollback, the alarm occurs.
Issue 02 (2011-10-31)

691
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The NE rollback fails. The board software cannot be recovered to the version before the package
loading. In this case, the board software version and the NE software version may mismatch.
Certain functions of the NE may operate abnormally.
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.
Procedure
Step 1 On the U2000, use the correct software package to perform package loading on the board.
----End
Related Information
None
4.264 SYN_BAD
Description
SYN_BAD is an alarm indicating that the frequency deviation of the synchronization source
exceeds the permitted range. This alarm is generated when the frequency deviation of the
synchronization source exceeds the permitted range so that quality of the physical-layer
synchronization source deteriorates.
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
Issue 02 (2011-10-31)

692
OptiX OSN 8800/6800/3800

4 Alarm Processing

table.
Name
Meaning
Parameter 1 Indicates the number of the subrack where the clock board is located.
Parameter 2 Indicates the number of the slot in the subrack where the clock source of the
service board is located. If the external clock source is used, the value is always
0xf0.
Parameter 3 Indicates the reserved byte, whose value is always 0x00.
Parameter 4 In the case of the clock source of the service board, it indicates the number of
the port in the subrack where the clock source is located.
In the case of the external clock source, it indicates the number of the external
clock.
l 0x01 indicates the first external clock.
l 0x02 indicates the second external clock.

When the SYN_BAD alarm is generated, tracing the relevant clock source may cause service
bit errors.
Possible Causes
The possible causes of the SYN_BAD alarm are as follows:
l
Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
Cause 3: The clock board that reports the alarm is faulty.
Check whether any higher-level alarm (such as B1_EXC, B1_SD, B2_EXC, B2_SD or
MS_CROSSTR) or performance event is detected on the U2000. If yes, take priority to
handle the higher-level alarm or performance event, and then check whether the SYN_BAD
alarm is cleared.
Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
Procedure
1.
1.
Issue 02 (2011-10-31)
If an external clock source is traced, check whether the clock signals are normal. If
not, replace the external clock source. For details, see Configuring Physical Clock in
the Feature Description.
693
OptiX OSN 8800/6800/3800

4 Alarm Processing
l
Cause 3: The clock board that reports the alarm is faulty.

1.
1. If the alarm persists, perform cold reset on the clock board, and then check whether
the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
2.
----End
Related Information
4.265 SYNC_C_LOS
Description
SYNC_C_LOS is an alarm indicating a synchronization source priority loss. This alarm is
generated when the clock source on a service board is lost in the priority table.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. The parameter
of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal
format and is described as follows:
l
When the parameter contains six numbers, it indicates that the time source of the service
board is in subrack 0. The first and second numbers indicate the ID of the slot where the
time source of the service board is located in the subrack. The third to sixth numbers indicate
the number of port where the time source of the service board is located in the subrack. For
example, if the parameter value is 120001, the time source of the service board is located
at port 1 of the board in slot 18 in subrack 0.
When the parameter contains seven numbers, the first number indicates the ID of the
subrack where the time source of the service board is located. The second and third numbers
indicate the ID of the slot where the time source of the service board is located in the subrack.
The fourth to seventh numbers indicate the number of port where the time source of the
service board is located in the subrack. For example, if the parameter value is 1120001, the
time source of the service board is located at port 1 of the board in slot 18 in subrack 1.
Issue 02 (2011-10-31)

694
OptiX OSN 8800/6800/3800

4 Alarm Processing

If this alarm is generated, it indicates that the external clock is lost. The equipment cannot trace
this lost external clock. In this case, if only the internal clock source can be used, bit error occurs
in the services later.
Possible Causes
The possible causes of the SYNC_C_LOS alarm are as follows:
l
Cause 1: Input signals are lost at the optical or electrical port that is connected to the clock
source.
Cause 2: There is a fiber cut (when a line clock source is traced).
Cause 4: The timing board is faulty.
Cause 1: Input signals are lost at the optical or electrical port that is connected to the clock
source. Cause 2: There is a fiber cut (when a line clock source is traced).
Procedure
1.
On the U2000, check whether the R_LOS alarm is generated on the relevant service
board. If yes, take priority to clear the R_LOS alarm, and then check whether the
SYNC_C_LOS alarm is cleared.

1.
If the alarm persists, perform cold reset on the relevant service board, and then check
whether the alarm is cleared. For details, see Performing Cold Reset of a Board in the
Supporting Tasks.
2.
Replacement.

1.
2.
If the alarm persists, replace the clock board.
----End
Related Information
4.266 SYNC_DISABLE
Description
The SYNC_DISABLE is an alarm indicating that the automatic synchronization of the system
control board is disabled. When the automatic synchronization of the system control board is
disabled, backup in batches is not supported and this alarm is generated.
Issue 02 (2011-10-31)

695
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The data of the active and standby system control boards may be inconsistent.
Possible Causes
The automatic synchronization state of the system control board is changed from enabled to
disabled.
Procedure
Step 1 Change the automatic synchronization state of the system control board to disabled, and then
the alarm is cleared automatically.
----End
Related Information
None
4.267 SYNC_F_M_SWITCH
Description
The SYNC_F_M_SWITCH is an alarm indicating the forced or manual switching state of a
clock source.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
Issue 02 (2011-10-31)

696
OptiX OSN 8800/6800/3800

4 Alarm Processing
table.
Name
Meaning
Parameter 1 Indicates the number of the subrack where the switched clock source is located.
Parameter 2 Indicates the number of the slot in the subrack where the switched clock source
is located. If the external clock source is used, the value is always 0xf0.
the port in the subrack where the switched clock source is located.
clock.
Parameter 5 Indicates the ID of the priority table. Valid values are as follows:
l 0x01: priority table of the system clock
l 0x02: priority table of the first channel 2M phase-locked source
l 0x03: priority table of the second channel 2M phase-locked source

When the SYNC_F_M_SWITCH alarm is generated, the NE clock works in the forced or manual
switching state. This alarm does not affect services.
Possible Causes
Cause 1: A manual or forced switching command is issued for the clock source.
Procedure
l
View the SYNC_F_M_SWITCH alarm on the U2000, and then determine the relevant
clock source according to the alarm parameters.
Cause 1: A manual or forced switching command is issued for the clock source.
1.
Clear the manual or forced switching for the relevant clock source, and the alarm is
automatically cleared. For details, see Configuring Physical Clock in the Feature
Description.
----End
Related Information
Issue 02 (2011-10-31)

697
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.268 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is locked.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the number of the subrack where the locked clock source is located.
Parameter 2 Indicates the number of the slot in the subrack where the locked clock source is
located. If the external clock source is used, the value is always 0xf0.
the port in the subrack where the locked clock source is located.
clock.

When the SYNC_LOCKOFF alarm is generated, the relevant clock source is locked and cannot
be traced by the NE. This alarm itself does not affect services.
Possible Causes
Cause 1: The NE software issues a command to lock the clock source.
Issue 02 (2011-10-31)

698
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
l
View the SYNC_LOCKOFF alarm on the U2000, and then determine the locked clock
source according to the alarm parameters.
Cause 1: The NE software issues a command to lock the clock source.

1.
After the lockout of the clock source is released on the U2000, the SYNC_LOCKOFF
alarm is automatically cleared. For details, see Configuring Physical Clock in the
Feature Description.
----End
Related Information
4.269 SYNC_FAIL
Description
The SYNC_FAIL is an alarm indicating that the batch backup fails.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
Parameter
Description
Parameter 1 Indicates the alarm cause.

0x31 indicates that backing up the database fails.
0x32 indicates that verifying the active and standby SCC file versions fails.
0x33 indicates that the active and standby SCCs fails to communicate.

The patch backup fails, and the working/protection switching is unavailable.
Possible Causes
l
The database backup fails.
Software versions of the working board and the protection board are not consistent.
Protection board communication is not stable or available.
Issue 02 (2011-10-31)

699
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Wait until the next working/protection backup succeeds and check whether the alarm is cleared.
Step 2 If the alarm persists, check whether the software versions of the working board and the protection
board are consistent. If not, upgrade the software for consistency.
----End
Related Information
None
4.270 SYSPARA_CFDB_NOSAME
Description
The SYSPARA_CFDB_NOSAME is an alarm indicating the difference between the SCC data
and the CF card data. Back up the data from the SCC to the CF card: In the first startup, the SCC
performs the consistency check between the SCC data and the CF card data. If not consistent,
the SCC does not perform the timing backup before reporting this alarm. If consistent, the SCC
starts the timing backup.
Attribute
Alarm Severity
Alarm Type
Minor
Process alarm
Parameters
None

The data in the system parameter area are not consistent with that saved in the CF card. The data
cannot be recovered from the CF card.
Possible Causes
The SCC data and the CF card data are not consistent upon the first startup.
Procedure
Step 1 Wait for the next backup period so that the NE database automatically backs up data to the CF
card and the alarm is cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

700
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.271 T_LOSEX
Description
The T_LOSEX is an alarm indicating that a board has detected the loss of signals in the service
bus of the backplane. If the board has detected that the service bus of the backplane is in the
LOS state, the T_LOSEX alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the T_LOSEX alarm is generated, the services of a board are interrupted. Consequently,
the board fails to work normally.
Possible Causes
The possible causes of the T_LOSEX alarm are as follows:
l
The service board is improperly inserted.
The cross-connect board is improperly inserted.
The clock source of the working and protection cross-connect boards fails to work or is of
poor quality.
Procedure
Step 1 View the T_LOSEX alarm on the U2000 to determine the relevant board.
Step 2 Make sure that the board is firmly inserted and properly installed, and then check whether the
T_LOSEX alarm is cleared. If the alarm persists, go to the next step.
Step 3 Make sure that the cross-connect board is firmly inserted and properly installed, and then check
whether the T_LOSEX alarm is cleared. If the alarm persists, go to the next step.
Step 4 Replace the cross-connect board that reports the alarm, and then check whether the T_LOSEX
alarm is cleared. If the alarm persists, go to the next step.
Step 5 Replace the board that reports the T_LOSEX alarm.
----End
Issue 02 (2011-10-31)

701
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.272 T_SLIP
Description
The T_SLIP is an alarm indicating that slip frames occur on the transmitted side. The alarm
occurs when the phase deviation occurs on the transmitted service frames of the board.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Bit errors occur in the client services, which can cause a service break when it gets severe.
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform cold reset on the faulty board through the U2000 or remove the faulty board. For details,
----End
Related Information
None
4.273 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is excessively high. This alarm
occurs when the laser temperature is higher than the upper laser temperature threshold.
Issue 02 (2011-10-31)

702
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

When the temperature of the tube core of the optical module is excessively high, the working
wavelengths of the optical module and the client services are affected.
Possible Causes
l
The working temperature of the board is excessively high.
The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature and ventilation of the equipment room. If the board
ambient temperature is excessively high, cool the equipment room with cooling devices, such
as an air conditioner.
Step 2 Replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.274 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is excessively low. This alarm
occurs when the laser temperature is lower than the lower threshold of the laser temperature.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Issue 02 (2011-10-31)

703
OptiX OSN 8800/6800/3800

4 Alarm Processing
Parameters
None

This has impact on the working wavelengths of the optical module and affects the client services.
Possible Causes
l
Working temperature of the board is excessively low.
The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it.
----End
Related Information
None
4.275 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that the board is in the test state.
Attribute
Alarm Severity
Alarm Type
Warning
Processing alarm
Parameters
None

The test commands, which can be issued only when the board is in the test status, may have an
impact on the system.
Possible Causes
A command is issued for the board to enter the test state.
Issue 02 (2011-10-31)

704
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 View the TEST_STATUS alarm on the U2000 to determine the relevant board.
Step 2 When a command is issued to end the test state, the TEST_STATUS alarm is automatically
cleared. However, this does not eliminate the system impact that arose during the test state of
the board. To ensure that the commands issued during the test state no longer affect the system,
perform cold reset on the board.
----End
Related Information
None
4.276 THUNDERALM
Description
The THUNDERALM is an alarm indicating a lighting protection circuit failure.
The alarm is generated when the PIU board detects a lightning protection circuit failure of the
PIU board.
Attribute
Alarm Severity
Alarm Type
Minor
Environment alarm
Parameters
table.
Parameter
Description
Parameter 1
Indicates the number of the unit that reports the alarm. For example,
0x01 indicates the PIU1 unit.
0x02 indicates the PIU2 unit.

The lightning protection performance of the system is degraded. If the equipment is attacked by
a strong current (for example, a strong lightning stroke), the board in the subrack may be
unavailable. As a result, the services are interrupted.
Issue 02 (2011-10-31)

705
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
l
The equipment is attacked by a strong lighting stroke (the common mode current is larger
than 5000 A and the differential mode current is larger than 3000 A). As a result, the
lightning protection component on the PIU board is unavailable and the circuit is broke due
to the automatic protection of the fuse. Hence, the PIU detects the failure and reports this
alarm.
Procedure
Step 1 Replace the faulty PIU board. For details, see the Parts Replacement.
----End
Related Information
In the stormy weather, intensive electromagnetic fields form in the air. To protect the equipment
against the lightning stroke, the equipment must be grounded during installation.
4.277 TIME_LOS
Description
The TIME_LOS is an alarm indicating the loss of the time source level. This alarm is generated
when the time source state does not exist after the precision time function is enabled.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. The parameter
of the alarm is displayed in the brackets in the Details area. The parameter is in the hexadecimal
format and is described as follows:
l
When the parameter contains six numbers, it indicates that the time source of the service
board is in subrack 0. The first and second numbers indicate the ID of the slot where the
time source of the service board is located in the subrack. The third to sixth numbers indicate
the number of port where the time source of the service board is located in the subrack. For
example, if the parameter value is 120001, the time source of the service board is located
at port 1 of the board in slot 18 in subrack 0.
When the parameter contains seven numbers, the first number indicates the ID of the
subrack where the time source of the service board is located. The second and third numbers
indicate the ID of the slot where the time source of the service board is located in the subrack.
The fourth to seventh numbers indicate the number of port where the time source of the
Issue 02 (2011-10-31)

706
OptiX OSN 8800/6800/3800

4 Alarm Processing
service board is located in the subrack. For example, if the parameter value is 1120001, the
time source of the service board is located at port 1 of the board in slot 18 in subrack 1.

When the alarm is reported, the time between the upstream and downstream NEs cannot be
synchronous, which may affect the quality of the service.
Possible Causes
The possible causes of the TIME_LOS alarm are as follows:
l
Cause 1: There are fiber failures or misconnections.
Procedure
1.
l
Check the fiber connections. Check whether there are optical interface alarms, such
as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first.

1.
If the alarm persists, perform cold reset on the relevant service board, and then check
whether the alarm is cleared. For details, see "Performing a Cold Reset of a Board"
in the Supporting Tasks.
2.
Replacement.

1.
Supporting Tasks.
2.
If the alarm persists, replace the clock board.For details, see "Replacing the Clock
----End
Related Information
4.278 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the time enters the non-trace mode.
The precision time of the board is in the non-trace mode. This alarm is generated when the board
traces the internal source after the precision time function is enabled.
Issue 02 (2011-10-31)

707
OptiX OSN 8800/6800/3800

4 Alarm Processing
Attribute
Alarm Severity
Alarm Type
Minor
Equipment alarm
Parameters
None

When the alarm is reported, the time between the upstream and downstream NEs cannot be
synchronous, which may affect the quality of the service.
Possible Causes
The possible causes of the TIME_NO_TRACE_MODE alarm are as follows:
l
Cause 1: The priority table is not configured.
Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
Cause 1: The priority table is not configured.
Procedure
1.

1.
Check the fiber connections. Check whether there are optical interface alarms, such
as R_LOS and R_LOF. If there are optical interface alarms, clear the alarms first.
Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
1.
Query the current priority table of the system. If there is only the internal clock source
in the priority table, set the clock source priority table to include other available clock
sources. After the setting, the alarm is automatically cleared. For details, see
"Configuring a IEEE 1588v2 Clock" in the Feature Description.
If the alarm persists, check whether the attributes of the packets at the upstream NE
are configured correctly on the U2000. If any error is found, modify the configuration.
For details, see "Configuring a IEEE 1588v2 Clock" in the Feature Description.

1.
Supporting Tasks.
2.
If the alarm persists, replace the clock board. For details, see "Replacing the Clock
----End
Related Information
Issue 02 (2011-10-31)

708
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.279 TR_LOC
Description
The TR_LOC is an alarm indicating that the clock of the cross-connect board is faulty. If a board
has detected loss of the clock signal of the cross-connect board, loss of the frame header, or
damage to the cross-connect board, the TR_LOC alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the detailed fault information.

l Bit 0 indicates that the clock of the cross-connect board in the slot with a
smaller number is lost.
l Bit 1 indicates that the frame header of the cross-connect board in the slot
with a smaller number is lost.
l Bit 2 indicates that the bus indicating the status of the cross-connect board in
the slot with a smaller number is faulty.
l Bit 4 indicates that the clock of the cross-connect board in the slot with a
bigger number is lost.
l Bit 5 indicates that the frame header of the cross-connect board in the slot
with a bigger number is lost.
l Bit 6 indicates that the bus indicating the status of the cross-connect board in
the slot with a bigger number is faulty.

When the TR_LOC occurs, the board fails to work normally. If the protection cross-connect
board is faulty, the services are not affected. If the working cross-connect board is faulty, the
services are switched. Consequently, transient service interruption occurs.
Issue 02 (2011-10-31)

709
OptiX OSN 8800/6800/3800

4 Alarm Processing
Possible Causes
The possible causes of the TR_LOC alarm are as follows:
l
The clock line of the cross-connect board is faulty.
The hardware of the local board is faulty.
Procedure
Step 1 View the TR_LOC alarm at the local station, and check whether the alarm is generated on the
service boards.
l
If the TR_LOC alarm is generated on most service boards, the cross-connect board is faulty.
In this case, replace the faulty cross-connect board.
If only the local board reports the alarm, replace the board.
----End
Related Information
None
4.280 TU_AIS_VC3
Description
The TU_AIS_VC3 is a TU alarm indication in the VC-3 lower order path. TU alarm indication
is the AIS at the level of the VC-3 lower order path. If a board has detected that the TU path is
all "1"s, the TU_AIS_VC3 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

When the TU_AIS_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_AIS_VC3 alarm are as follows:
l
Issue 02 (2011-10-31)
Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in
the system.
710
OptiX OSN 8800/6800/3800

4 Alarm Processing
The cross-connect and timing board is faulty.
The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is
detected on the U2000. If yes, take priority to clear it, and then check whether the TU_AIS_VC3
Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_AIS_VC3
CAUTION
Step 3 Replace the board that reports the alarm, and then check whether the TU_AIS_VC3 alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check
whether the TU_AIS_VC3 alarm is cleared.
Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether
the TU_AIS_VC3 alarm is cleared.
----End
Related Information
None
4.281 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating the loss of pointer in the VC-3 lower order path. If a
board has detected that the TU-PTR value is an invalid pointer or NDF reversion in eight
consecutive frames, the TU_LOP_VC3 alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None
Issue 02 (2011-10-31)

711
OptiX OSN 8800/6800/3800

4 Alarm Processing

When the TU_LOP_VC3 alarm is generated, the VC-3 path services are interrupted.
Possible Causes
The possible causes of the TU_LOP_VC3 alarm are as follows:
l
Certain higher-level alarms, such as the R_LOS, R_LOF, HP_SLM, or AU_AIS, occur in
the system.
The cross-connect and timing board is faulty.
The relevant path at the opposite station is faulty.
Procedure
Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is
detected on the U2000. If yes, take priority to clear it, and then check whether the TU_LOP_VC3
Step 2 Perform cold reset on the board that reports the alarm. Then check whether the TU_LOP_VC3
CAUTION
Step 3 Replace the board that reports the alarm, and then check whether the TU_LOP_VC3 alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check
whether the TU_LOP_VC3 alarm is cleared.
Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether
the TU_LOP_VC3 alarm is cleared.
----End
Related Information
None
4.282 VCAT_LOA
Issue 02 (2011-10-31)

712
OptiX OSN 8800/6800/3800

4 Alarm Processing

Board Type
Alarm Page Link

4.282.1 VCAT_LOA (OCS)

SLO16, or EGSH
4.282.2 VCAT_LOA (OTN)
4.282.1 VCAT_LOA (OCS)

Description
The VCAT_LOA (OCS) is an alarm indicating that the delay of the virtual concatenation is
excessively long. This alarm occurs when the delay time of the timeslots bound to a VCTRUNK
exceeds the time allowed by the virtual concatenation delay. The time allowed by the virtual
concatenation delay varies according to different board types.
Attribute
Alarm Severity
Alarm Type
Critical
Processing alarm
Parameters
None

During the service data transmission, when the alignment time of the virtual concatenation delay
is excessively long, the timeslots cannot form a data frame. Accordingly, it causes the packet
loss.
Possible Causes
The possible cause of the VCAT_LOA alarm is as follows:
The configured VCTRUNK timeslots pass physical links of different distances.
Procedure
Step 1 View the VCAT_LOA alarm on the U2000 to determine the relevant board.
Step 2 Configure the timeslots of the VCTRUNK again, so that they pass the same fiber. If they need
to pass different fibers, make sure that the distance difference of the fibers is the shortest.
----End
Issue 02 (2011-10-31)

713
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.282.2 VCAT_LOA (OTN)

Description
The VCAT_LOA is an alarm indicating that the delay of multiframes exceeds the threshold. The
alarm is generated when the MFAS value in OTN signals received on the WDM side is not
consistent.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

The board is unable to converge the WDM-side services into the client-side 40 Gbit/s services,
which causes that the client-side services are abnormal.
Possible Causes
l
The fiber connection on the WDM side is incorrect.
The board at the upstream or local station is faulty.
Procedure
Step 1 Check whether the fiber connection on the WDM side is correct. If not, re-connect the fibers.
Step 2 Check whether there are abnormal alarms in the WDM-side services. If yes, clear the alarms
according to the proper procedures.
Step 3 If the alarm persists, perform a WDM-side inloop on the upstream board and then on the local
board, to determine which board is faulty.
Step 4 Based on the results, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
ITU-T G.709
4.283 VCAT_LOM_VC3
Issue 02 (2011-10-31)

714
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The VCAT_LOM_VC3 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-3 path. This alarm is generated when the system detects that the multiframe indicator
(MFI) field in the H4 byte of the VC-3 timeslot is illegal.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

l
During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC3 alarm are as follows:
l
The virtual concatenation delay is excessively long.
The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC3 alarm on the U2000 to determine the relevant board.
Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm
to clear it. After that, check whether the VCAT_LOM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC3 alarm at the
local end is faulty. Replace the board that reports the alarm at the local station, and then check
whether the VCAT_LOM_VC3 alarm is cleared.
Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is
incorrect. Replace the corresponding board at the opposite station, and then check whether the
VCAT_LOM_VC3 alarm is cleared.
----End
Related Information
None
4.284 VCAT_LOM_VC4
Issue 02 (2011-10-31)

715
OptiX OSN 8800/6800/3800

4 Alarm Processing
Description
The VCAT_LOM_VC4 is an alarm indicating the loss of the virtual concatenation multiframe
in the VC-4 path. This alarm is generated when the system detects that the multiframe indicator
(MFI) field in the H4 byte of the VC-4 timeslot is illegal.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
None

l
During the data transmission, if the LCAS is disabled, the services are interrupted.
Possible Causes
The possible causes of the VCAT_LOM_VC4 alarm are as follows:
l
The virtual concatenation delay is excessively long.
The MFI field in the K4 byte transmitted from the opposite end is incorrect.
Procedure
Step 1 View the VCAT_LOM_VC4 alarm on the U2000 to determine the relevant board.
Step 2 On the U2000, check whether there is the VCAT_LOA alarm. If yes, it indicates that the virtual
concatenation delay is excessively long. See the procedure for handling the VCAT_LOA alarm
to clear it. After that, check whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 If the alarm persists, check whether the board that reports the VCAT_LOM_VC4 alarm at the
local end is faulty. Replace the board that reports the alarm at the local station, and then check
whether the VCAT_LOM_VC4 alarm is cleared.
Step 4 If the alarm persists, it indicates that the MFI domain transmitted from the SDH opposite end is
incorrect. Replace the corresponding board at the opposite station, and then check whether the
VCAT_LOM_VC4 alarm is cleared.
----End
Related Information
None
Issue 02 (2011-10-31)

716
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.285 VLAN_SNCP_PS
Description
VLAN SNCP protection switching alarm. This alarm is reported when the working or protection
channel of the protection group is faulty or the user runs an external switching command.
Attribute
Alarm Severity
Alarm Type
Major
Communication alarm
Parameters
Parameter
Description
Parameters 1 and 2 Indicates the ID of the protection group in which the alarm is generated.

l
When switching is performed to the VLAN SNCP group, the services would be transiently
interrupted.
When the alarm is reported, the working channel or the protection channel of the VLAN
SNCP group might have faulty services that need to be restored.
Possible Causes
l
A user issues an external switching command such as forced switching, manual switching
The services of the working channel or the protection channel of the VLAN SNCP group
are faulty.
The switching is in WTR State. After WTR Times (s), the alarm clears.
Procedure
switching, manual switching or locked switching, check whether the external switching
operation is necessary,
1.
2.
If the external switching operation is unnecessary, issue a clear switching command to clear
the external switching.
Step 2 If the alarm is generated due to the fault of the working channel or the protection channel of the
protection group,
Issue 02 (2011-10-31)

717
OptiX OSN 8800/6800/3800

4 Alarm Processing
1.
Query whether the related boards for configuring the protection group have the alarms, for
example, R_LOF, R_LOS, R_OOF, OTUk_LOF, OTUk_LOM, OTUk_AIS. If yes, clear
the alarm so that the services in the working channel or the protection channel return normal.
2.
that is the case, the working channel would automatically switch to the working channel.
The alarm would disappear. If the attribute is Non-Revertive, set it to Revertive and the
alarm would disappear.
Step 3 On the U2000, query the switching state of the protection group, if the switching is in WTR
State. This alarm requires no handling. After WTR Times (s), the alarm clears.
----End
Related Information
VLAN SNCP protection utilizes the dual fed and selective receiving function of the L2 module
to protect the upstream convergence services. The service granularity of protection switching is
services at client-side ports, which are identified as VLAN. For details, see "VLAN SNCP
Protection" in the Feature Description.
4.286 VOA_ADJUST_FAIL
Description
The VOA_ADJUST_FAIL is an alarm indicating that the VOA adjustment fails.
Attribute
Alarm Severity
Alarm Type
Major
Process alarm
Parameters

The gain adjustment of the OAU1 fails, which results in failure of command issuing.
Possible Causes
l
The external DCM of the OAU1 has excessive attenuation between the input and output
interfaces.
The OAU1 laser is off.
Issue 02 (2011-10-31)

718
OptiX OSN 8800/6800/3800

4 Alarm Processing
The gain set for OAU1 exceeds the maximum permitted actual gain. As a result, the VOA
adjustment fails.
Procedure
Step 1 Check whether the external DCM of the OAU1 has excessive attenuation between the input and
output interfaces. If yes, adjust it to keep the input and output in a normal range.
Step 2 If the alarm persists, check whether the laser of the OAU1 is on. If not, turn it on.
Step 3 Query the permitted actual gain range of OAU1 on the U2000 and set the gain again to ensure
that the gain is within the permitted range.
----End
Related Information
None
4.287 VOADATA_MIS
Description
The VOADATA_MIS is an alarm indicating mismatch of the attenuation attribute. When the
set attenuation value falls beyond the adjustable attenuation range of the board, the alarm is
reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

Possible Causes
Cause 1: As for the attenuation, replacing the board or the optical module causes that the stored
attenuation value issued by the NE software falls beyond the new adjustable attenuation range
of the board.
Procedure
l
Issue 02 (2011-10-31)
Cause 1: The stored attenuation value issued by the NE software falls beyond the new
adjustable attenuation range of the board.
719
OptiX OSN 8800/6800/3800

1.
4 Alarm Processing
Query the adjustable range of the current actual attenuation. Re-set a valid attenuation
value for the optical interface channel of the board based on the queried adjustable
range.
----End
Related Information
None
4.288 W_R_FAIL
Description
Writing or reading chip register failure. The alarm is generated when the read value and the
written value of the register are not consistent.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
Parameter 1 Indicates the IDs of the board register. For example, 0x01-0x09 indicates the IDs
of the faulty chips that are of different types.

The board cannot work normally. In this case, the services may not be received or transmitted
properly. In addition, the board may fail to query the current performance value.
Possible Causes
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000. For details, see the Troubleshooting.
----End
Related Information
None
Issue 02 (2011-10-31)

720
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.289 WAVE_ADD_ABN
Description
APE detect wavelengths added.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

APE detect wavelengths added.
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the
spectrum analysis module of the detect board. The wavelengths are then compared with the
scanned wavelengths obtained during the defining. If a new wavelength is detected, a wavelength
add alarm is reported.
Procedure
Step 1 The network management system prompts the user to re-define the APE standard optical power
curve.
----End
Related Information
Issue 02 (2011-10-31)

721
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.290 WAVE_DROP_ABN
Description
APE detect wavelengths dropped.
Attribute
Alarm Severity
Alarm Type
Warning
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1

APE detect wavelengths dropped.
Possible Causes
The actually accessed wavelengths on each optical interface can be obtained through the
spectrum analysis module of the detect board. The wavelengths are then compared with the
scanned wavelengths obtained during the defining. If there is a wavelength that is not accessed,
a wavelength drop alarm is reported.
Procedure
Step 1 The network management system prompts the user to re-define the APE standard optical power
curve.
----End
Related Information
Issue 02 (2011-10-31)

722
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.291 WAVEDATA_MIS
Description
The WAVEDATA_MIS is an alarm indicating mismatch of the wavelength or band attribute.
When the configured logic wavelength or band differs with the actual wavelength or band, the
alarm is reported.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The service may be interrupted.
Possible Causes
l
Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
Procedure
1.
Query the actual wavelength of the unit and the logic wavelength stored on the
U2000. If these two wavelengths differ, reconfigure the operating wavelength of the
corresponding optical port to make it the same as the fixed wavelength of the optical
module on the board.

1.
If the alarm persists, replace the board or optical module with another one whose
wavelength is the same as that stored in the NE software. For details, see the Parts
Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

723
OptiX OSN 8800/6800/3800

4 Alarm Processing
4.292 WAVELEN_OVER
Description
The WAVELEN_OVER is an alarm indicating that the wavelength crosses the threshold. When
the wavelength drift of the OTU board exceeds the threshold, this alarm occurs.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
None

The services carried by the wavelength is degraded or interrupted, and the services carried by
the adjacent wavelengths may be affected.
Possible Causes
l
The wavelength drift of the corresponding channel of the OTU board exceeds the upper or
lower threshold.
The wavelength locking is mis-adjusted because the logical fiber connection is inconsistent
with the physical fiber connection.
The wavelength locking module on the WMU board or a module on the OTU board is
malfunctioning.
Procedure
Step 1 Check whether the wavelength of the optical interface connecting to the wavelength monitoring
board on the OTU board is within the normal range. If not, the OTU board enables the wavelength
locking function to adjust the monitored wavelength. When the monitored wavelength restores
to a value within the normal range, this alarm is cleared.
Step 2 If the alarm persists, check whether the logical fiber connections are consistent with the physical
fiber connections. If not, modify the logical fiber connections so that the logical fiber connections
are consistent with the physical fiber connections. For details, see "Checking Logical Fibers" in
Step 3 If the alarm persists, cold reset of the OTU board is required. For details, see the Supporting
Tasks.
Step 4 If the alarm persists, contact Huawei engineers.
----End
Issue 02 (2011-10-31)

724
OptiX OSN 8800/6800/3800

4 Alarm Processing
Related Information
None
4.293 XC_UNSWITCH
Description
The XC_UNSWITCH is an alarm indicating that the cross-connect matrix of the board is not
switched.
Attribute
Alarm Severity
Alarm Type
Major
Equipment alarm
Parameters
table.
Name
Meaning
Parameter 1 Indicates the subrack ID of the board whose cross-connect matrix is not switched.
Parameter 2 Indicates the slot ID of the board whose cross-connect matrix is not switched.

The services related to the board that reports the alarm are interrupted.
Possible Causes
The possible causes of the XC_UNSWITCH alarm are as follows:
l
The cross-connect board or the line board fails to respond to the cross-connect matrix
switching command issued by the NE software, and as a result is not updated with the crossconnect matrix configured by the NE software.
The board is in the BIOS state, and as a result cannot be updated with the cross-connect
matrix configured by the NE software.
Issue 02 (2011-10-31)

725
OptiX OSN 8800/6800/3800

4 Alarm Processing
Procedure
Step 1 Check whether the board that reports the alarm has communication alarms. If yes, clear the
communication alarms, and then check whether the XC_UNSWITCH alarm is cleared.
Step 2 If the alarm persists, perform warm reset on the board, and check whether the XC_UNSWITCH
alarm is still generated.
Step 3 If the alarm persists, contact Huawei engineers to re-load the board software.
Step 4 If the alarm persists, replace the board that reports the alarm. For details, see the Parts
Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

726
OptiX OSN 8800/6800/3800

5 Performance Event List
Performance Event List
About This Chapter

This topic lists the names, description and relevant boards of the performance event in
alphabetical order and lists the performance event of every board.
5.1 Product Performance Event List
Lists the different types of performance event.
5.2 Board Performance Event List
This section list the performance event of every board.
Issue 02 (2011-10-31)

727
OptiX OSN 8800/6800/3800

5.1 Product Performance Event List

Lists the different types of performance event.
5.1.1 Performance Event of Check and Error Correction

Lists of the performance event of check and error correction.
Table 5-1 Performance Event List of Check and Error Correction
Issue 02 (2011-10-31)
Name
Description
CRC4ES
CRC4 Errored Second
CRC4FEES
CRC4 Far End Errored Second
CRC4FESES
CRC4 Far End Severely Errored Second
CRC4FEUAS
CRC4 Far End Unavailable Second
CRC4SES
CRC4 Severely Errored Second
CRC4UAS
CRC4 Unavailable Second
FEC_AFT_COR_ERAVR
After FEC Correct Average Errored Rate in

monitor period
FEC_BEF_COR_ERAVR
Before FEC Correct Average Errored Rate in

monitor period
FEC_AFT_COR_ER
After FEC Correct Errored Rate
FEC_BEF_COR_ER
Before FEC Correct Errored Rate
FEC_COR_0BIT_CNT
Forward Error Correction - Corrected 0 Bit

Count
FEC_COR_1BIT_CNT
Forward Error Correction - Corrected 1 Bit

Count
FEC_COR_BYTE_CNT
Forward Error Correction - Corrected Byte

Count
FEC_UNCOR_BLOCK_CNT
Forward Error Correction - Uncorrected Block

Count
FEC_BEF_CORER_FLOAT
Before FEC Correct Errored Rate (FLOAT)
FEC_AFT_CORER_FLOAT
After FEC Correct Errored Rate (FLOAT)
OSC_BBE
OSC Path Background Block Error
OSC_BBER
OSC Path Background Block Error Ratio
OSC_BIAES
OSC Path Backward Incoming Alignment

Errored Second
728
OptiX OSN 8800/6800/3800

Name
Description
OSC_ES
OSC Path Errored Second
OSC_FEBBE
OSC Path Far End Background Block Error
OSC_FEBBER
OSC Path Far End Background Block Error

Ratio
OSC_FEES
OSC Path Far End Errored Second
OSC_FESES
OSC Path Far End Severely Errored Second
OSC_FESESR
OSC Path Unavailable Seconds
OSC_FEUAS
OSC Path Far End Unavailable Seconds
OSC_IAES
OSC Path Incoming Alignment Errored Second
OSC_SES
OSC Path Severely Errored Second
OSC_SESR
OSC_UAS
5.1.2 Performance Event of Pointer Justification

This topic lists the performance events for pointer justifications.
Table 5-2 Pointer justification performance event list
Name
Description
AUPJCHIGH
Count of positive AU pointer justifications
AUPJCLOW
Count of negative AU pointer justifications
AUPJCNEW
Count of new AU pointer justifications
5.1.3 Performance Event of Equipment Function

Lists the performance event of equipment function.
Table 5-3 Performance Event List of Equipment Function
Issue 02 (2011-10-31)
Name
Description
BCVCUR
Average Pump Laser Backfacet Current

Value
BCVMAX
Maximum Pump Laser Backfacet Current

Value
729
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
BCVMIN
Minimum Pump Laser Backfacet Current

Value
CCVCUR
Average Pump Laser Cooling Current Value
CCVMAX
Maximum Pump Laser Cooling Current

Value
CCVMIN
Minimum Pump Laser Cooling Current

Value
EDTMPCUR
Current Laser Temperature Value
EDTMPMAX
Maximum Laser Temperature Value
EDTMPMIN
Minimum Laser Temperature Value
EDTPLCUR
Current Laser Output Optical Power Value
EDTPLMAX
Maximum Laser Output Optical Power Value
EDTPLMIN
Minimum Laser Output Optical Power Value
ENVTMPCUR
Current Environmental Temperature Value
ENVTMPMAX
Maximum Environmental Temperature

Value
ENVTMPMIN
Minimum Environmental Temperature

Value
ICCLCCUR
Current Module Cooling Current Value
ICCLCMAX
Maximum Module Cooling Current Value
ICCLCMIN
Minimum Module Cooling Current Value
ICTMPCUR
Current Module Temperature Value
ICTMPMAX
Maximum Module Temperature Value
ICTMPMIN
Minimum Module Temperature Value
LSBIASCUR
Current Laser Bias Current Value
LSBIASMAX
Maximum Laser Bias Current Value
LSBIASMIN
Minimum Laser Bias Current Value
LSCLCCUR
Current Laser Cooling Current Value
LSCLCMAX
Maximum Laser Cooling Current Value
LSCLCMIN
Minimum Laser Cooling Current Value
LSIOPCUR
Current Input Optical Power Value
LSIOPMAX
Maximum Input Optical Power Value

730
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
LSIOPMIN
Minimum Input Optical Power Value
LSOOPCUR
Current Output Optical Power Value
LSOOPMAX
Maximum Output Optical Power Value
LSOOPMIN
Minimum Output Optical Power Value
LSTMPCUR
Current Laser Temperature Value
LSTMPMAX
Maximum Laser Temperature Value
LSTMPMIN
Minimum Laser Temperature Value
OOPRLCUR
Current value of the optical output power

return loss
OOPRLMAX
Maximum value of the optical output power

return loss within a time period
OOPRLMIN
Minimum value of the optical output power

return loss within a time period
OSPICCVCUR
Average value of laser cooling current
OSPICCVMAX
Maximum value of laser cooling current
OSPICCVMIN
Minimum value of laser cooling current
OSPITMPCUR
Current value of laser working temperature
OSPITMPMAX
Maximum value of laser working

temperature
OSPITMPMIN
Minimum value of laser working temperature
RPLCUR
Current value of input optical power
RPLMAX
Maximum value of input optical power
RPLMIN
Minimum value of input optical power
PCLSOPCUR
Current Per-Channel Laser Output Power

Value
PCLSOPMAX
Maximum Per-Channel Laser Output Power

Value
PCLSOPMIN
Minimum Per-Channel Laser Output Power

Value
PCLSSNCUR
Current Per-Channel OSNR Value
PCLSSNMAX
Maximum Per-Channel OSNR Value
PCLSSNMIN
Minimum Per-Channel OSNR Value

731
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
PCLSWLCUR
Current Per-Channel Central Wavelength

Value
PCLSWLMAX
Maximum Per-Channel Central Wavelength

Value
PCLSWLMIN
Minimum Per-Channel Central Wavelength

Value
PCLSWLOCUR
Current Per-Channel Central Wavelength
PCLSWLOMAX
Maximum Per-Channel Central Wavelength
PCLSWLOMIN
Minimum Per-Channel Central Wavelength
SUMIOPCUR
Current Total Input Optical Power Value
SUMIOPMAX
Maximum Total Input Optical Power Value
SUMIOPMIN
Minimum Total Input Optical Power Value
SUMOOPCUR
Current Output Optical Power Value
SUMOOPMAX
Maximum Total Output Optical Power Value
SUMOOPMIN
Minimum Total Output Optical Power Value
TLBCUR
Current value of laser bias current
TLBMAX
Maximum value of laser bias current
TLBMIN
Minimum value of laser bias current
TPLCUR
Current value of output optical power
TPLMAX
Maximum value of output optical power
TPLMIN
Minimum value of output optical power
WCVCUR
Current value of pump laser working current
WCVMAX
Maximum value of pump laser working

current
WCVMIN
Minimum value of pump laser working

current
AVGFREQDEV
Average frequency deviation
MAXFREQDEV
Maximum frequency deviation
MINFREQDEV
Minimum frequency deviation
AVGMEANPATHDELAY
Average path delay
MAXMEANPATHDELAY
Maximum path delay
MINMEANPATHDELAY
Minimum path delay

732
OptiX OSN 8800/6800/3800

Name
Description
AVGPHASEOFFSET
Average phase offset
MAXPHASEOFFSET
Maximum phase offset
MINPHASEOFFSET
Minimum phase offset
XCSTMPCUR
Current Environmental Temperature Value
XCSTMPMAX
Maximum Environmental Temperature

Value
XCSTMPMIN
Minimum Environmental Temperature

Value
5.1.4 Performance Event of Multiplex Section Bit Error

Lists performance event of multiplex section bit error.
Table 5-4 Performance Event list of Multiplex Section Bit Error
Name
Description
MSBBE
MS Background Block Error
MSES
MS Errored Second
MSFEBBE
MS Far End Background Block Error
MSFEES
MS Far End Errored Second
MSFESES
MS Far End Severely Errored Second
MSFEUAS
MS Far End Unavailable Second
MSSES
MS Severely Errored Second
MSUAS
MS Unavailable Second
5.1.5 Performance Event of Regenerator Section Bit Error

Lists the performance event of Regenerator Section Bit Error.
Table 5-5 Performance Event List of Regenerator Section Bit Error
Issue 02 (2011-10-31)
Name
Description
RSBBE
RS Background Block Error
RSCSES
RS Consecutive Severely Errored Second

733
OptiX OSN 8800/6800/3800

Name
Description
RSES
RS Errored Second
RSOFS
RS Out-of-Frame Second
RSOOF
Regenerator section of OOF preferance seconds
RSSES
RS Severely Errored Second
RSUAS
RS Unavailable Second
5.1.6 Performance Event of Higher Order Path Bit Error

This topic lists the performance events for the bit errors in the higher order paths.
Table 5-6 Higher order path performance event list
Name
Description
HPBBE
Higher order path block of background error
HPES
Higher order path errored second
HPSES
Higher order path severely errored second
HPUAS
Higher order path far end unavailable second
HPFEBBE
Higher order path far end block of background

error
HPFEES
Higher order path far end errored second
HPFESES
Higher order path far end severely errored

second
HPFEUAS
Higher order path far end consecutive severely

errored second
5.1.7 Performance Event of Lower Order Path Bit Error

This topic lists the performance events for the bit errors in the lower order paths.
Table 5-7 Lower order path performance event list
Issue 02 (2011-10-31)
Name
Description
VC3BBE
VC3 block of background error
VC3ES
VC3 errored second
VC3SES
VC3 severely errored second

734
OptiX OSN 8800/6800/3800

Name
Description
VC3UAS
VC3 unavailable second
VC3CSES
VC3 consecutive severely errored second
VC3FEBBE
VC3 far end block of background error
VC3FEES
VC3 far end errored second
VC3FESES
VC3 far end severely errored second
VC3FECSES
VC3 far end consecutive severely errored

second
VC3FEUAS
VC3 far end unavailable second
5.1.8 Performance Event of OTN

List the three sections performance Event of OTN. It include: Path Monitoring (PM) section,
Tandem Connection Monitoring (TCM) section and Section Monitoring (SM).
Performance Event of PM Section

Table 5-8 Performance Event of PM Section
Issue 02 (2011-10-31)
Name
Description
ODU0_PM_BBE
ODU0 PM Section Background Block Error
ODU0_PM_BBER
ODU0 PM Section Ratio of Background

Block Error
ODU0_PM_ES
ODU0 PM Section Errored Second
ODU0_PM_FEBBE
ODU0 PM Section Far End Background

Block Error
ODU0_PM_FEBBER
ODU0 PM Section Ratio of Far End

Background Block Error
ODU0_PM_FEES
ODU0 PM Section Far End Errored Second
ODU0_PM_FESES
ODU0 PM Section Far End Severely Errored

Second
ODU0_PM_FESESR
ODU0 PM Section Ratio of Far End Severely

Errored Second
ODU0_PM_FEUAS
ODU0 PM Section Far End Unavailable

Second
ODU0_PM_SES
ODU0 PM Section Severely Errored Second

735
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
ODU0_PM_SESR
ODU0 PM Section Ratio of Severely Errored

Second
ODU0_PM_UAS
ODU0 PM Section Unavailable Second
ODU1_PM_BBE
ODU1_PM_BBER

Block Error
ODU1_PM_ES
ODU1_PM_FEBBE

Block Error
ODU1_PM_FEBBER

ODU1_PM_FEES
ODU1_PM_FESES

Second
ODU1_PM_FESESR

Errored Second
ODU1_PM_FEUAS

Second
ODU1_PM_SES
ODU1_PM_SESR

Second
ODU1_PM_UAS
ODU2_PM_BBE
ODU2_PM_BBER

Block Error
ODU2_PM_ES
ODU2_PM_FEBBE

Block Error
ODU2_PM_FEBBER

ODU2_PM_FEES
ODU2_PM_FESES

Second
ODU2_PM_FESESR

Errored Second

736
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
ODU2_PM_FEUAS

Second
ODU2_PM_SES
ODU2_PM_SESR

Second
ODU2_PM_UAS
ODU3_PM_BBE
ODU3_PM_BBER

Block Error
ODU3_PM_ES
ODU3_PM_FEBBE

Block Error
ODU3_PM_FEBBER

ODU3_PM_FEES
ODU3_PM_FESES

Second
ODU3_PM_FESESR

Errored Second
ODU3_PM_FEUAS

Second
ODU3_PM_SES
ODU3_PM_SESR

Second
ODU3_PM_UAS
ODU5G_PM_BBE
ODU5G PM Section Background Block

Error
ODU5G_PM_BBER
ODU5G PM Section Ratio of Background

Block Error
ODU5G_PM_ES
ODU5G PM Section Errored Second
ODU5G_PM_FEBBE
ODU5G PM Section Far End Background

Block Error
ODU5G_PM_FEBBER
ODU5G PM Section Ratio of Far End

ODU5G_PM_FEES
ODU5G PM Section Far End Errored Second

737
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
ODU5G_PM_FESES
ODU5G PM Section Far End Severely

Errored Second
ODU5G_PM_FESESR
ODU5G PM Section Ratio of Far End

Severely Errored Second
ODU5G_PM_FEUAS
ODU5G PM Section Far End Unavailable

Second
ODU5G_PM_SES
ODU5G PM Section Severely Errored

Second
ODU5G_PM_SESR
ODU5G PM Section Ratio of Severely

Errored Second
ODU5G_PM_UAS
ODU5G PM Section Unavailable Second
ODUFLEX_PM_BBE
ODUFLEX PM Section Background Block

Error
ODUFLEX_PM_BBER
ODUFLEX PM Section Ratio of Background

Block Error
ODUFLEX_PM_ES
ODUFLEX PM Section Errored Second
ODUFLEX_PM_FEBBE
ODUFLEX PM Section Far End Background

Block Error
ODUFLEX_PM_FEBBER
ODUFLEX PM Section Ratio of Far End

ODUFLEX_PM_FEES
ODUFLEX PM Section Far End Errored

Second
ODUFLEX_PM_FESES
ODUFLEX PM Section Far End Severely

Errored Second
ODUFLEX_PM_FESESR
ODUFLEX PM Section Ratio of Far End

ODUFLEX_PM_FEUAS
ODUFLEX PM Section Far End Unavailable

Second
ODUFLEX_PM_SES
ODUFLEX PM Section Severely Errored

Second
ODUFLEX_PM_SESR
ODUFLEX PM Section Ratio of Severely

Errored Second
ODUFLEX_PM_UAS
ODUFLEX PM Section Unavailable Second

738
OptiX OSN 8800/6800/3800

Performance Event of TCM Section

Table 5-9 Performance Event of TCM Section
Issue 02 (2011-10-31)
Name
Description
ODU0_TCMn_BBE
ODU0 TCMn Section Background Block

Error
ODU0_TCMn_BBER
ODU0 TCMn Section Ratio of Background

Block Error
ODU0_TCMn_BIAES
ODU0 TCMn Section Background

Introduced Alignment Errored Second
ODU0_TCMn_ES
ODU0 TCMn Section Errored Second
ODU0_TCMn_FEBBE
ODU0 TCMn Section Far End Background

Block Error
ODU0_TCMn_FEBBER
ODU0 TCMn Section Ratio of Far End

ODU0_TCMn_FEES
ODU0 TCMn Section Far End Errored

Second
ODU0_TCMn_FESES
ODU0 TCMn Section Far End Severely

Errored Second
ODU0_TCMn_FESESR

ODU0_TCMn_FEUAS
ODU0 TCMn Section Far End Unavailable

Second
ODU0_TCMn_IAES
ODU0 TCMn Section Introduced Alignment

Errored Second
ODU0_TCMn_SES
ODU0 TCMn Section Severely Errored

Second
ODU0_TCMn_SESR
ODU0 TCMn Section Ratio of Severely

Errored Second
ODU0_TCMn_UAS
ODU0 TCMn Section Unavailable Second
ODU1_TCMn_BBE

Error
ODU1_TCMn_BBER

Block Error
ODU1_TCMn_BIAES

ODU1_TCMn_ES

739
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
ODU1_TCMn_FEBBE

Block Error
ODU1_TCMn_FEBBER

ODU1_TCMn_FEES

Second
ODU1_TCMn_FESES

Errored Second
ODU1_TCMn_FESESR

ODU1_TCMn_FEUAS

Second
ODU1_TCMn_IAES

Errored Second
ODU1_TCMn_SES

Second
ODU1_TCMn_SESR

Errored Second
ODU1_TCMn_UAS
ODU2_TCMn_BBE

Error
ODU2_TCMn_BBER

Block Error
ODU2_TCMn_BIAES

ODU2_TCMn_ES
ODU2_TCMn_FEBBE

Block Error
ODU2_TCMn_FEBBER

ODU2_TCMn_FEES

Second
ODU2_TCMn_FESES

Errored Second
ODU2_TCMn_FESESR


740
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
ODU2_TCMn_FEUAS

Second
ODU2_TCMn_IAES

Errored Second
ODU2_TCMn_SES

Second
ODU2_TCMn_SESR

Errored Second
ODU2_TCMn_UAS
ODU2PMBIP8
Number of bit errors in the optical channel

data unit
ODU3_TCMn_BBE

Error
ODU3_TCMn_BBER

Block Error
ODU3_TCMn_BIAES

ODU3_TCMn_ES
ODU3_TCMn_FEBBE

Block Error
ODU3_TCMn_FEBBER

ODU3_TCMn_FEES

Second
ODU3_TCMn_FESES

Errored Second
ODU3_TCMn_FESESR

ODU3_TCMn_FEUAS

Second
ODU3_TCMn_IAES

Errored Second
ODU3_TCMn_SES

Second
ODU3_TCMn_SESR

Errored Second
ODU3_TCMn_UAS

741
OptiX OSN 8800/6800/3800

Name
Description
ODU5G_TCMn_BBE
ODU5G TCMn Section Background Block

Error
ODU5G_TCMn_BBER
ODU5G TCMn Section Ratio of Background

Block Error
ODU5G_TCMn_BIAES
ODU5G TCMn Section Background

ODU5G_TCMn_ES
ODU5G TCMn Section Errored Second
ODU5G_TCMn_FEBBE
ODU5G TCMn Section Far End Background

Block Error
ODU5G_TCMn_FEBBER
ODU5G TCMn Section Ratio of Far End

ODU5G_TCMn_FEES
ODU5G TCMn Section Far End Errored

Second
ODU5G_TCMn_FESES
ODU5G TCMn Section Far End Severely

Errored Second
ODU5G_TCMn_FESESR
ODU5G TCMn Section Ratio of Far End

ODU5G_TCMn_FEUAS
ODU5G TCMn Section Far End Unavailable

Second
ODU5G_TCMn_IAES
ODU5G TCMn Section Introduced

Alignment Errored Second
ODU5G_TCMn_SES
ODU5G TCMn Section Severely Errored

Second
ODU5G_TCMn_SESR
ODU5G TCMn Section Ratio of Severely

Errored Second
ODU5G_TCMn_UAS
ODU5G TCMn Section Unavailable Second
Performance Event of SM Section

Table 5-10 Performance Event of SM Section
Issue 02 (2011-10-31)
Name
Description
OTU1_BBE
OTU1 SM Section Background Block Error
OTU1_BBER
OTU1 SM Section Ratio of Background

Block Error
OTU1_BIAES
OTU1 SM Section Background Introduced


742
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
OTU1_ES
OTU1 SM Section Errored Second
OTU1_FEBBE
OTU1 SM Section Far End Background

Block Error
OTU1_FEBBER
OTU1 SM Section Ratio of Far End

OTU1_FEES
OTU1 SM Section Far End Errored Second
OTU1_FESES
OTU1 SM Section Far End Severely Errored

Second
OTU1_FESESR
OTU1 SM Section Ratio of Far End Severely

Errored Second
OTU1_FEUAS
OTU1 SM Section Far End Unavailable

Second
OTU1_IAES
OTU1 SM Section Introduced Alignment

Errored Second
OTU1_SES
OTU1 SM Section Severely Errored Second
OTU1_SESR
OTU1 SM Section Ratio of Severely Errored

Second
OTU1_UAS
OTU1 SM Section Unavailable Second
OTU2_BBE
OTU2_BBER

Block Error
OTU2_BIAES

OTU2_ES
OTU2_FEBBE

Block Error
OTU2_FEBBER

OTU2_FEES
OTU2_FESES

Second
OTU2_FESESR

Errored Second
OTU2_FEUAS

Second

743
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
OTU2_IAES

Errored Second
OTU2_SES
OTU2_SESR

Second
OTU2_UAS
OTU2SMBIP8
Number of bit errors in the optical channel

transport unit
OTU3_BBE
OTU3_BBER

Block Error
OTU3_BIAES

OTU3_ES
OTU3_FEBBE

Block Error
OTU3_FEBBER

OTU3_FEES
OTU3_FESES

Second
OTU3_FESESR

Errored Second
OTU3_FEUAS

Second
OTU3_IAES

Errored Second
OTU3_SES
OTU3_SESR

Second
OTU3_UAS
OTU5G_BBE
OTU5G SM Section Background Block

Error
OTU5G_BBER
OTU5G SM Section Ratio of Background

Block Error

744
OptiX OSN 8800/6800/3800

Name
Description
OTU5G_BIAES
OTU5G SM Section Background Introduced

OTU5G_ES
OTU5G SM Section Errored Second
OTU5G_FEBBE
OTU5G SM Section Far End Background

Block Error
OTU5G_FEBBER
OTU5G SM Section Ratio of Far End

OTU5G_FEES
OTU5G SM Section Far End Errored Second
OTU5G_FESES
OTU5G SM Section Far End Severely

Errored Second
OTU5G_FESESR
OTU5G SM Section Ratio of Far End

OTU5G_FEUAS
OTU5G SM Section Far End Unavailable

Second
OTU5G_IAES
OTU5G SM Section Introduced Alignment

Errored Second
OTU5G_SES
OTU5G SM Section Severely Errored

Second
OTU5G_SESR
OTU5G SM Section Ratio of Severely

Errored Second
OTU5G_UAS
OTU5G SM Section Unavailable Second
5.1.9 Performance Event List of RMON Function

Lists the performance event of RMON function.
Table 5-11 RMON Performance Event List
Issue 02 (2011-10-31)
Name
Description
ETHDROP (Drop Events)
The total number of events in which packets

were dropped by the probe due to lack of
resources. Note that this number is not
necessarily the number of packets dropped; it
is just the number of times this condition has
been detected.
RXOCTETS (Octets Received)
The total number of octets of data (including

those in bad packets) received on the network
(excluding framing bits but including FCS
octets).

745
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
RXPKTS (Packets Received)
The total number of packets (including bad

packets, broadcast packets, and multicast
packets) received.
RXBRDCAST (Broadcast Packets

Received)
The total number of good packets received

that were directed to the broadcast address.
Note that this does not include multicast
packets.
RXMULCAST (Multicast Packets Received)

that were directed to a multicast address. Note
that this number does not include packets
directed to the broadcast address.
ETHCRCALI (FCS and Alignment Errors)
The total number of packets received that had

a length (excluding framing bits, but
including FCS octets) of between 64 and
1518 octets, inclusive, but had either a bad
Frame Check Sequence (FCS) with an
integral number of octets (FCS Error) or a bad
FCS with a non-integral number of octets
(Alignment Error).
ETHUNDER (Undersize Packets Received)
The total number of packets received that

were less than 64 octets long (excluding
framing bits, but including FCS octets) and
were otherwise well formed.
ETHOVER (Oversize Packets Received)

were longer than 1518 octets (excluding
ETHFRG (Fragments)

were less than 64 octets in length (excluding
framing bits but including FCS octets) and
had either a bad Frame Check Sequence
(FCS) with an integral number of octets (FCS
Error) or a bad FCS with a non-integral
number of octets (Alignment Error).
ETHJAB (Jabbers)

framing bits, but including FCS octets), and
had either a bad Frame Check Sequence
(FCS) with an integral number of octets (FCS
Error) or a bad FCS with a non-integral
number of octets (Alignment Error).
RXPKT64 (Packets Received, 64 Octets in

Length)

packets) received that were 64 octets in length
octets).

746
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
RXPKT65 (Packets Received, 65~127 Octets

in Length)

packets) received that were between 65 and
127 octets in length inclusive (excluding
framing bits but including FCS octets).
RXPKT128 (Packets Received, 128~255

Octets in Length)


Octets in Length)


Octets in Length)


Octets in Length)

RXPKT1519 (Packets Received, 1519~MTU

Octets in Length)

MTU octets in length inclusive (excluding
PKT64 (Packets Received and Transmitted,

64 Octets in Length)

packets) received and transmitted that were
64 octets in length (excluding framing bits but
including FCS octets).

65~127 Octets in Length)

between 65 and 127 octets in length inclusive
octets).


between 128 and 255 octets in length
inclusive (excluding framing bits but



747
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description


PKT1024 (Packets Received and

Transmitted, 1024~1518 Octets in Length)

TXFULLBGOOD (Good Full Frame Octets

Transmitted)
The total number of transmitted octets of

good packets (including framing bits and FCS
octets).
RXFULLBGOOD (Good Full Frame Octets

Received)
The total number of received octets of good

packets (including framing bits and FCS
octets).
TXGOODFULLFRAMESPEED (Good Full

Frame Speed Transmitted)
The rate of transmitted octets of good packets

(including framing bits and FCS octets).
RXGOODFULLFRAMESPEED (Good Full

Frame Speed Received)
The rate of received octets of good packets

(including framing bits and FCS octets).
VCG_TXGOODPACKETS (Good Packets

Transmitted)
The total number of transmitted octets of

good packets.
VCG_RXGOODPACKETS (Good Packets

Received)
The total number of received octets of good

packets.
VCG_TXSPEED (Full Frame Speed

Transmitted)
The rate of octets of data (including those in

bad packets) transmitted on the network
octets).
VCG_RXSPEED (Full Frame Speed

Received)
The rate of octets of data (including those in

bad packets) received on the network
octets).
TXPKT64 (Packets Transmitted, 64 Octets in

Length)

packets) transmitted that were 64 octets in
length (excluding framing bits but including
FCS octets).
TXPKT65 (Packets Transmitted, 65~127

Octets in Length)

packets) transmitted that were between 65
and 127 octets in length inclusive (excluding

748
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description

Octets in Length)


Octets in Length)


Octets in Length)

TXPKT1024 (Packets Transmitted,


TXPKT1519 (Packets Transmitted,

1519~MTU Octets in Length)

and MTU octets in length inclusive
octets).
RXUNICAST (Unicast Packets Received)

that were directed to a unicast address.
TXUNICAST (Unicast Packets Transmitted)
The total number of packets that higher-level

protocols requested be transmitted, and
which were not addressed to a multicast or
broadcast address at this sub-layer, including
those that were discarded or not sent.
TXMULCAST (Multicast Packets

Transmitted)

which were addressed to a multicast address
at this sub-layer, including those that were
discarded or not sent. For a MAC layer
protocol, this includes both Group and
Functional addresses.
TXBRDCAST (Broadcast Packets

Transmitted)

which were addressed to a broadcast address
at this sub-layer, including those that were
discarded or not sent.
RXPAUSE (Pause Frames Received)
A count of MAC Control frames received on

this interface with an opcode indicating the
PAUSE operation.

749
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
Name
Description
TXPAUSE (Pause Frames Transmitted)
A count of MAC Control frames transmitted

on this interface with an opcode indicating the
PAUSE operation.
RXBGOOD (Good Octets Received)
The total number of octets of good packets

received on the network (excluding framing
bits but including FCS octets).
TXBGOOD (Good Octets Transmitted)
The total number of octets of good packets

transmitted on the network (excluding
RXBBAD (Bad Octets Received)
The total number of octets of bad packets

received on the network (excluding framing
bits but including FCS octets).
TXBBAD (Bad Octets Transmitted)
The total number of octets of bad packets

transmitted on the network (excluding
ETHALI (Alignment Errors)
A count of frames received on a particular

interface that are not an integral number of
octets in length and do not pass the FCS
check.
ETHFCS (FCS Errors)
A count of frames received on a particular

interface that are an integral number of octets
in length but do not pass the FCS check. This
count does not include frames received with
frame-too-long or frame-too-short error.
RXCTLPKTS (Control Frames Received)
A count of MAC Control frames received on

this interface with an opcode indicating the
special operation.
TXCTLPKTS (Control Frames Transmitted)
A count of MAC Control frames transmitted

on this interface with an opcode indicating the
special operation.
TXETHDROP (Drop Events at Transmission

Direction)
The total number of events in which packets

were dropped by the probe due to lack of
resources at transmission direction. Note that
this number is not necessarily the number of
packets dropped; it is just the number of times
this condition has been detected.
TXETHOVER (Oversize Packets

Transmitted)
The total number of packets transmitted that

TXPKTS (Packets Transmitted)

packets, broadcast packets, and multicast
packets) Transmitted.

750
OptiX OSN 8800/6800/3800

Name
Description
TXOCTETS (Octets Transmitted)
The total number of octets of data (including

those in bad packets) Transmitted on the
network (excluding framing bits but
5.1.10 TCM Performance Event

TCM performance events are used to monitor the transmission performance in the tandem
connection.
Table 5-12 TCM performance event list
Name
Description
TCBBE
Tandem Connection Background Block Error
TCFEBBE
Tandem Connection Far End Background Block

Error
TCOBBE
Tandem Connection Outgoing Background

Block Error
5.1.11 Performance Event of FC

Lists of the performance event of FC service.
Name
The total number of frames with wrong CRC that the FC channel
received in client side.
The total number of times that the link reseted in both client and WAN
side.
The total number of frames, with the type of Class1, that the FC channel
The total number of frames, with the type of Classf, that the FC channel
Issue 02 (2011-10-31)

751
OptiX OSN 8800/6800/3800

Name
The total number of frames that the FC channel received in client side.
transmitted in client side.
The total number of frames, with the type of Classf, that the FC channel
The total number of frames that the FC channel transmitted in client side.
The total number of bytes that the FC channel received in client side.
The total number of bytes that the FC channel transmitted in client side.
The count of OS that the FC channel can't support.
5.2 Board Performance Event List

This section list the performance event of every board.
5.2.1 CRPC Board Performance Event List

BCVCUR
EDTPLMAX
LSIOPCUR
BCVMAX
EDTPLMIN
WCVCUR
BCVMIN
ENVTMPCUR
WCVMAX
CCVCUR
ENVTMPMAX
WCVMIN
CCVMAX
ENVTMPMIN
OOPRLMAX
CCVMIN
LSIOPMAX
OOPRLMIN
EDTPLCUR
LSIOPMIN
OOPRLCUR
5.2.2 DAS1 Board Performance Event List
Issue 02 (2011-10-31)
BCVCUR
LSBIASMIN
OSC_FEUAS
BCVMAX
LSIOPCUR
OSC_IAES

752
OptiX OSN 8800/6800/3800

BCVMIN
LSIOPMAX
OSC_SES
CCVCUR
LSIOPMIN
OSC_SESR
CCVMAX
LSOOPCUR
OSC_UAS
CCVMIN
LSOOPMAX
SUMIOPCUR
EDTMPCUR
LSOOPMIN
SUMIOPMAX
EDTMPMAX
LSTMPCUR
SUMIOPMIN
EDTMPMIN
LSTMPMAX
SUMOOPCUR
FEC_AFT_COR_ER
LSTMPMIN
SUMOOPMAX
FEC_AFT_COR_ERAVR
OSC_BBE
SUMOOPMIN
FEC_BEF_COR_ER
OSC_BBER
WCVCUR
FEC_BEF_COR_ERAVR
OSC_BIAES
WCVMAX
FEC_COR_0BIT_CNT
OSC_ES
WCVMIN
FEC_COR_1BIT_CNT
OSC_FEBBE
XCSTMPCUR
FEC_COR_BYTE_CNT
OSC_FEBBER
XCSTMPMAX
FEC_UNCOR_BLOCK_CN
T
OSC_FEES
XCSTMPMIN
LSBIASCUR
OSC_FESES
LSBIASMAX
OSC_FESESR
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.
5.2.3 D40V Board Performance Event List

ICTMPCUR
SUMIOPCUR
XCSTMPCUR
ICTMPMAX
SUMIOPMAX
XCSTMPMAX
ICTMPMIN
SUMIOPMIN
XCSTMPMIN
5.2.4 D40 Board Performance Event List

TN12D40
Issue 02 (2011-10-31)
ICCLCCUR
ICTMPMIN
SUMOOPMAX
ICCLCMAX
SUMIOPCUR
SUMOOPMIN

753
OptiX OSN 8800/6800/3800

ICCLCMIN
SUMIOPMAX
XCSTMPCUR
ICTMPCUR
SUMIOPMIN
XCSTMPMAX
ICTMPMAX
SUMOOPCUR
XCSTMPMIN
TN11D40
ICCLCCUR
ICTMPMAX
SUMIOPMIN
ICCLCMAX
ICTMPMIN
XCSTMPCUR
ICCLCMIN
SUMIOPCUR
XCSTMPMAX
ICTMPCUR
SUMIOPMAX
XCSTMPMIN
5.2.5 DCP Board Performance Event List

LSIOPCUR
LSIOPMIN
XCSTMPMAX
LSIOPMAX
XCSTMPCUR
XCSTMPMIN
5.2.6 EGSH Board Performance Event List

HPBBE
LSBIASMIN
VC3ES
HPES
LSIOPCUR
VC3FEBBE
HPCSES
LSIOPMAX
VC3FECSES
HPFEBBE
LSIOPMIN
VC3FEES
HPFEES
LSOOPCUR
VC3FESES
HPFECSES
LSOOPMAX
VC3FEUAS
HPFESES
LSOOPMIN
VC3SES
HPFEUAS
LSTMPCUR
VC3UAS
HPSES
LSTMPMAX
XCSTMPCUR
HPUAS
LSTMPMIN
XCSTMPMAX
LSBIASCUR
VC3BBE
XCSTMPMIN
LSBIASMAX
VC3CSES
RMON Performance Event List

Issue 02 (2011-10-31)

754
OptiX OSN 8800/6800/3800

Broadcast Packets
Transmitted
Multicast Packets Received
Packets Received(64 Octets in

Length)
Broadcast Packets
Received
Multicast Packets Transmitted
Packets Received(65~127
Octets in Length)
Control Frames
Received
Octets Received
Packets Transmitted
Control Frames
Transmitted
Octets Transmitted
Packets Transmitted
(1024~1518 Octets in Length)
Drop Events
Oversize Packets Received
Packets Transmitted(128~255
Octets in Length)
FCS Errors
Packets Received
Octets in Length)
Fragments
Packets Received and Transmitted

Packets Transmitted
Full Frame Speed

Received

Packets Transmitted(64 Octets

in Length)
Full Frame Speed

Transmitted

Octets in Length)
Good Full Frame

Octets Received

Pause Frames Transmitted
Good Full Frame

Octets Transmitted

(64 Octets in Length)
Pause Frames Received
Good Full Frame

Speed Received

Undersize Packets Received
Good Full Frame

Speed Transmitted
Packets Received(1024~1518 Octets

in Length)
Unicast Packets Transmitted
Good Packets
Received
Packets Received(128~255 Octets in

Length)
Unicast Packets Received
Good Packets
Transmitted
Packets Received(256~511 Octets in

Length)
Jabbers

in Length)
5.2.7 EAS2 Board Performance Event List
Issue 02 (2011-10-31)
HPBBE
HPUAS
LSOOPMIN
HPCSES
LSBISACUR
LSTMPCUR
HPES
LSBISAMAX
LSTMPMAX

755
OptiX OSN 8800/6800/3800

HPFEBBE
LSBISAMIN
LSTMPMIN
HPFECSES
LSIOPCUR
XCSTMPCUR
HPFEES
LSIOPMAX
XCSTMPMAX
HPFESES
LSIOPMIN
XCSTMPMIN
HPFEUAS
LSOOPCUR
HPSES
LSOOPMAX
5.2.8 ECOM Board Performance Event List

LSBIASCUR
LSIOPMIN
LSTMPMAX
LSBIASMAX
LSOOPCUR
LSTMPMIN
LSBIASMIN
LSOOPMAX
XCSTMPCUR
LSIOPCUR
LSOOPMIN
XCSTMPMAX
LSIOPMAX
LSTMPCUR
XCSTMPMIN
Broadcast Packets Received
Undersize Packets
Received
Fragments
Jabbers
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Good Octets Received
Good Octets Transmitted
Bad Octets Received
FCS Errors
Oversize Packets Transmitted
5.2.9 ELQX Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_UAS
ODU2_TCMn_FEES
FEC_AFT_COR_ER
ODU1_TCMn_BBE
ODU2_TCMn_FESES
FEC_AFT_COR_ERAVR
ODU1_TCMn_BBER
ODU2_TCMn_FESESR
FEC_BEF_CORER_FLOAT
ODU1_TCMn_BIAES
ODU2_TCMn_FEUAS

756
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_BEF_COR_ER
ODU1_TCMn_ES
ODU2_TCMn_IAES
FEC_BEF_COR_ERAVR
ODU1_TCMn_FEBBE
ODU2_TCMn_SES
FEC_COR_0BIT_CNT
ODU1_TCMn_FEBBER
ODU2_TCMn_SESR
FEC_COR_1BIT_CNT
ODU1_TCMn_FEES
ODU2_TCMn_UAS
FEC_COR_BYTE_CNT
ODU1_TCMn_FESES
OTU2_BBE
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FESESR
OTU2_BBER
LSBIASCUR
ODU1_TCMn_FEUAS
OTU2_BIAES
LSBIASMAX
ODU1_TCMn_IAES
OTU2_ES
LSBIASMIN
ODU1_TCMn_SES
OTU2_FEBBE
LSIOPCUR
ODU1_TCMn_SESR
OTU2_FEBBER
LSIOPMAX
ODU1_TCMn_UAS
OTU2_FEES
LSIOPMIN
ODU2_PM_BBE
OTU2_FESES
LSOOPCUR
ODU2_PM_BBER
OTU2_FESESR
LSOOPMAX
ODU2_PM_ES
OTU2_FEUAS
LSOOPMIN
ODU2_PM_FEBBE
OTU2_IAES
LSTMPCUR
ODU2_PM_FEBBER
OTU2_SES
LSTMPMAX
ODU2_PM_FEES
OTU2_SESR
LSTMPMIN
ODU2_PM_FESES
OTU2_UAS
ODU1_PM_BBE
ODU2_PM_FESESR
RSBBE
ODU1_PM_BBER
ODU2_PM_FEUAS
RSCSES
ODU1_PM_ES
ODU2_PM_SES
RSES
ODU1_PM_FEBBE
ODU2_PM_SESR
RSOFS
ODU1_PM_FEBBER
ODU2_PM_UAS
RSSES
ODU1_PM_FEES
ODU2_TCMn_BBE
RSUAS
ODU1_PM_FESES
ODU2_TCMn_BBER
XCSTMPCUR
ODU1_PM_FESESR
ODU2_TCMn_BIAES
XCSTMPMAX
ODU1_PM_FEUAS
ODU2_TCMn_ES
XCSTMPMIN
ODU1_PM_SES
ODU2_TCMn_FEBBE
ODU1_PM_SESR
ODU2_TCMn_FEBBER

757
OptiX OSN 8800/6800/3800

NOTE
TCM6.
NOTE

Octets Received
Packets Received (128~255

Octets in Length)
Packets Received

Octets in Length)
Broadcast Packets
Received

Octets in Length)
Multicast Packets
Received

Octets in Length)
Broadcast Packets Transmitted
Undersize Packets
Received
Packets Transmitted (64

Octets in Length)
Oversize Packets
Received
Packets Transmitted (65~127

Octets in Length)
Fragments

Octets in Length)
Alignment Errors
Jabbers

Octets in Length)
FCS Errors
Packets Received (64

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Received
(65~127 Octets in
Length)
Packets Transmitted
Octets Transmitted
5.2.10 ENQ2 Board Performance Event List

TN54ENQ2(STND)
XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
FEC_AFT_CORER_FLOAT
ODU1_PM_SES
ODU2_TCMn_BIAES
FEC_AFT_COR_ER
ODU1_PM_SESR
ODU2_TCMn_ES
FEC_AFT_COR_ERAVR
ODU1_PM_UAS
ODU2_TCMn_FEBBE
TN54ENQ2
Issue 02 (2011-10-31)

758
OptiX OSN 8800/6800/3800

FEC_BEF_CORER_FLOAT
ODU1_TCMn_BBE
ODU2_TCMn_FEBBER
FEC_BEF_COR_ER
ODU1_TCMn_BBER
ODU2_TCMn_FEES
FEC_BEF_COR_ERAVR
ODU1_TCMn_BIAES
ODU2_TCMn_FESES
FEC_COR_0BIT_CNT
ODU1_TCMn_ES
ODU2_TCMn_FESESR
FEC_COR_1BIT_CNT
ODU1_TCMn_FEBBE
ODU2_TCMn_FEUAS
FEC_COR_BYTE_CNT
ODU1_TCMn_FEBBER
ODU2_TCMn_IAES
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEES
ODU2_TCMn_SES
ODU0_PM_BBE
ODU1_TCMn_FESES
ODU2_TCMn_SESR
ODU0_PM_BBER
ODU1_TCMn_FESESR
ODU2_TCMn_UAS
ODU0_PM_ES
ODU1_TCMn_FEUAS
OTU2_BBE
ODU0_PM_FEBBE
ODU1_TCMn_IAES
OTU2_BBER
ODU0_PM_FEBBER
ODU1_TCMn_SES
OTU2_BIAES
ODU0_PM_FEES
ODU1_TCMn_SESR
OTU2_ES
ODU0_PM_FESES
ODU1_TCMn_UAS
OTU2_FEBBE
ODU0_PM_FESESR
ODU2_PM_BBE
OTU2_FEBBER
ODU0_PM_FEUAS
ODU2_PM_BBER
OTU2_FEES
ODU0_PM_SES
ODU2_PM_ES
OTU2_FESES
ODU0_PM_SESR
ODU2_PM_FEBBE
OTU2_FESESR
ODU0_PM_UAS
ODU2_PM_FEBBER
OTU2_FEUAS
ODU1_PM_BBE
ODU2_PM_FEES
OTU2_IAES
ODU1_PM_BBER
ODU2_PM_FESES
OTU2_SES
ODU1_PM_ES
ODU2_PM_FESESR
OTU2_SESR
ODU1_PM_FEBBE
ODU2_PM_FEUAS
OTU2_UAS
ODU1_PM_FEBBER
ODU2_PM_SES
XCSTMPCUR
ODU1_PM_FEES
ODU2_PM_SESR
XCSTMPMAX
ODU1_PM_FESES
ODU2_PM_UAS
XCSTMPMIN
ODU1_PM_FESESR
ODU2_TCMn_BBE
ODU1_PM_FEUAS
ODU2_TCMn_BBER
NOTE
Issue 02 (2011-10-31)

759
OptiX OSN 8800/6800/3800

5.2.11 FIU Board Performance Event List

SUMIOPCUR
SUMIOPMIN
XCSTMPMAX
SUMIOPMAX
XCSTMPCUR
XCSTMPMIN
5.2.12 HSC1 Board Performance Event List

CRC4BBE
LSBIASCUR
LSIOPMIN
CRC4ES
LSBIASMAX
LSOOPCUR
CRC4FEBBE
LSBIASMIN
LSOOPMAX
CRC4FEES
LSCLCCUR
LSOOPMIN
CRC4FESES
LSCLCMAX
XCSTMPCUR
CRC4FEUAS
LSCLCMIN
XCSTMPMAX
CRC4SES
LSIOPCUR
XCSTMPMIN
CRC4UAS
LSIOPMAX
5.2.13 HBA Board Performance Event List

BCVCUR
EDTMPMAX
SUMOOPMIN
BCVMAX
EDTMPMIN
WCVCUR
BCVMIN
SUMIOPCUR
WCVMAX
CCVCUR
SUMIOPMAX
WCVMIN
CCVMAX
SUMIOPMIN
XCSTMPCUR
CCVMIN
SUMOOPCUR
XCSTMPMAX
EDTMPCUR
SUMOOPMAX
XCSTMPMIN
5.2.14 ITL Board Performance Event List

XCSTMPCUR
Issue 02 (2011-10-31)
XCSTMPMAX

XCSTMPMIN
760
OptiX OSN 8800/6800/3800

5.2.15 L4G Board Performance Event List

FEC_AFT_COR_ER
ODU5G_PM_BBER
ODU5G_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU5G_PM_ES
OTU5G_BBE
FEC_BEF_COR_ER
ODU5G_PM_FEBBE
OTU5G_BBER
FEC_BEF_COR_ERAVR
ODU5G_PM_FEBBER
OTU5G_BIAES
FEC_COR_0BIT_CNT
ODU5G_PM_FEES
OTU5G_ES
FEC_COR_1BIT_CNT
ODU5G_PM_FESES
OTU5G_FEBBE
FEC_COR_BYTE_CNT
ODU5G_PM_FESESR
OTU5G_FEBBER
FEC_UNCOR_BLOCK_CN
T
ODU5G_PM_FEUAS
OTU5G_FEES
LSBIASCUR
ODU5G_PM_SES
OTU5G_FESES
LSBIASMAX
ODU5G_PM_SESR
OTU5G_FESESR
LSBIASMIN
ODU5G_PM_UAS
OTU5G_FEUAS
LSCLCCUR
ODU5G_TCMn_BBE
OTU5G_IAES
LSCLCMAX
ODU5G_TCMn_BBER
OTU5G_SES
LSCLCMIN
ODU5G_TCMn_BIAES
OTU5G_SESR
LSIOPCUR
ODU5G_TCMn_ES
OTU5G_UAS
LSIOPMAX
ODU5G_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU5G_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU5G_TCMn_FEES
RSES
LSOOPMAX
ODU5G_TCMn_FESES
RSOFS
LSOOPMIN
ODU5G_TCMn_FESESR
RSSES
LSTMPCUR
ODU5G_TCMn_FEUAS
RSUAS
LSTMPMAX
ODU5G_TCMn_IAES
XCSTMPCUR
LSTMPMIN
ODU5G_TCMn_SES
XCSTMPMAX
ODU5G_PM_BBE
ODU5G_TCMn_SESR
XCSTMPMIN
NOTE
TCM6.
NOTE

Issue 02 (2011-10-31)

761
OptiX OSN 8800/6800/3800

Octets Received
Packets Received
Undersize Packets
Received
Fragments
Jabbers
Packets Received and

Transmitted (64 Octets in
Length)

Transmitted (65~127 Octets
in Length)

Transmitted (128~255
Octets in Length)

in Length)

Octets in Length)

Octets in Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Alignment Errors
FCS Errors
Control Frames Received
Control Frames
Transmitted
Packets Transmitted
Octets Transmitted
5.2.16 LDGD Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
MSFEES
ODU1_TCMn_SES
FEC_AFT_COR_ERAVR
MSFESES
ODU1_TCMn_SESR
FEC_BEF_COR_ER
MSFEUAS
ODU1_TCMn_UAS
FEC_BEF_COR_ERAVR
MSSES
OTU1_BBE
FEC_COR_0BIT_CNT
MSUAS
OTU1_BBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_BIAES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_ES
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_ES
OTU1_FEBBE
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEBBER
LSBIASMAX
ODU1_PM_FEBBER
OTU1_FEES
LSBIASMIN
ODU1_PM_FEES
OTU1_FESES
LSCLCCUR
ODU1_PM_FESES
OTU1_FESESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_FEUAS

762
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU1_PM_FEUAS
OTU1_IAES
LSIOPCUR
ODU1_PM_SES
OTU1_SES
LSIOPMAX
ODU1_PM_SESR
OTU1_SESR
LSIOPMIN
ODU1_PM_UAS
OTU1_UAS
LSOOPCUR
ODU1_TCMn_BBE
RSBBE
LSOOPMAX
ODU1_TCMn_BBER
RSCSES
LSOOPMIN
ODU1_TCMn_BIAES
RSES
LSTMPCUR
ODU1_TCMn_ES
RSOFS
LSTMPMAX
ODU1_TCMn_FEBBE
RSSES
LSTMPMIN
ODU1_TCMn_FEBBER
RSUAS
MSBBE
ODU1_TCMn_FEES
XCSTMPCUR
MSCSES
ODU1_TCMn_FESES
XCSTMPMAX
MSES
ODU1_TCMn_FESESR
XCSTMPMIN
MSFEBBE
ODU1_TCMn_FEUAS
MSFECSES
ODU1_TCMn_IAES
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Drop Events
Fragments
Jabbers
Packets Received (64 Octets

in Length)

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
(1024~1518 Octets in
Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted

763
OptiX OSN 8800/6800/3800

Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
Bad Octets Transmitted
FCS Errors
5.2.17 LDGS Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
MSFEES
ODU1_TCMn_SES
FEC_AFT_COR_ERAVR
MSFESES
ODU1_TCMn_SESR
FEC_BEF_COR_ER
MSFEUAS
ODU1_TCMn_UAS
FEC_BEF_COR_ERAVR
MSSES
OTU1_BBE
FEC_COR_0BIT_CNT
MSUAS
OTU1_BBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
OTU1_BIAES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
OTU1_ES
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_ES
OTU1_FEBBE
LSBIASCUR
ODU1_PM_FEBBE
OTU1_FEBBER
LSBIASMAX
ODU1_PM_FEBBER
OTU1_FEES
LSBIASMIN
ODU1_PM_FEES
OTU1_FESES
LSCLCCUR
ODU1_PM_FESES
OTU1_FESESR
LSCLCMAX
ODU1_PM_FESESR
OTU1_FEUAS
LSCLCMIN
ODU1_PM_FEUAS
OTU1_IAES
LSIOPCUR
ODU1_PM_SES
OTU1_SES
LSIOPMAX
ODU1_PM_SESR
OTU1_SESR
LSIOPMIN
ODU1_PM_UAS
OTU1_UAS
LSOOPCUR
ODU1_TCMn_BBE
RSBBE
LSOOPMAX
ODU1_TCMn_BBER
RSCSES
LSOOPMIN
ODU1_TCMn_BIAES
RSES

764
OptiX OSN 8800/6800/3800

LSTMPCUR
ODU1_TCMn_ES
RSOFS
LSTMPMAX
ODU1_TCMn_FEBBE
RSSES
LSTMPMIN
ODU1_TCMn_FEBBER
RSUAS
MSBBE
ODU1_TCMn_FEES
XCSTMPCUR
MSCSES
ODU1_TCMn_FESES
XCSTMPMAX
MSES
ODU1_TCMn_FESESR
XCSTMPMIN
MSFEBBE
ODU1_TCMn_FEUAS
MSFECSES
ODU1_TCMn_IAES
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Drop Events
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
FCS Errors

765
OptiX OSN 8800/6800/3800

5.2.18 LDM Board Performance Event List

FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
OTU1_FEES
LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR
LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR
NOTE
TCM6.
NOTE

Issue 02 (2011-10-31)

766
OptiX OSN 8800/6800/3800

Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Packets Transmitted(64
Octets in Length)
Packets Transmitted
Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors
Octets in Length)
Drop Events at
Transmission Direction
Octets in Length)
Oversize Packets
Transmitted
5.2.19 LDMD Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
OTU1_FEES

767
OptiX OSN 8800/6800/3800

LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR
LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Packets Transmitted

768
OptiX OSN 8800/6800/3800

Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors
Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
5.2.20 LDMS Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
OTU1_FEES
LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR
LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE

769
OptiX OSN 8800/6800/3800

LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Packets Transmitted
Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors

770
OptiX OSN 8800/6800/3800

Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
5.2.21 LDX Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU2_PM_BBE
ODU2_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU2_PM_BBER
OTU2_BBE
FEC_AFT_CORER_FLOAT
ODU2_PM_ES
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBE
OTU2_BIAES
FEC_BEF_COR_ERAVR
ODU2_PM_FEBBER
OTU2_ES
FEC_BEF_CORER_FLOAT
ODU2_PM_FEES
OTU2_FEBBE
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBER
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEES
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FESES
FEC_UNCOR_BLOCK_CNT
ODU2_PM_SES
OTU2_FESESR
LSBIASCUR
ODU2_PM_SESR
OTU2_FEUAS
LSBIASMAX
ODU2_PM_UAS
OTU2_IAES
LSBIASMIN
ODU2_TCMn_BBE
OTU2_SES
LSCLCCUR
ODU2_TCMn_BBER
OTU2_SESR
LSCLCMAX
ODU2_TCMn_BIAES
OTU2_UAS
LSCLCMIN
ODU2_TCMn_ES
RSBBE
LSIOPCUR
ODU2_TCMn_FEBBE
RSCSES
LSIOPMAX
ODU2_TCMn_FEBBER
RSES
LSIOPMIN
ODU2_TCMn_FEES
RSOFS
LSOOPCUR
ODU2_TCMn_FESES
RSSES
LSOOPMAX
ODU2_TCMn_FESESR
RSUAS
LSOOPMIN
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU2_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU2_TCMn_SESR

771
OptiX OSN 8800/6800/3800

NOTE

Octets in Length)
Alignment Errors
Broadcast Packets
Transmitted
Packets Received
Octets in Length)
Broadcast Packets
Received
Octets in Length)
Octets in Length)
FCS Errors
Octets in Length)
Packets Transmitted(64 Octets in

Length)
Fragments
Octets in Length)
Octets in Length)
Jabbers
Octets in Length)
Multicast Packets
Received

Length)
Multicast Packets
Transmitted

in Length)
Octets Received
Packets Transmitted
Octets Transmitted
Octets in Length)
5.2.22 LEM24 Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU2_PM_BBER
ODU2_TCMn_UAS
FEC_AFT_COR_ER
ODU2_PM_ES
OTU2_BBE
FEC_BEF_CORER_FLOAT
ODU2_PM_FEBBE
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBER
OTU2_BIAES
FEC_COR_0BIT_CNT
ODU2_PM_FEES
OTU2_ES
FEC_COR_1BIT_CNT
ODU2_PM_FESES
OTU2_FEBBE
FEC_COR_BYTE_CNT
ODU2_PM_FESESR
OTU2_FEBBER
FEC_UNCOR_BLOCK_CN
T
ODU2_PM_FEUAS
OTU2_FEES
LSBIASCUR
ODU2_PM_SES
OTU2_FESES
LSBIASMAX
ODU2_PM_SESR
OTU2_FESESR

772
OptiX OSN 8800/6800/3800

LSBIASMIN
ODU2_PM_UAS
OTU2_FEUAS
LSCLCCUR
ODU2_TCMn_BBE
OTU2_IAES
LSCLCMAX
ODU2_TCMn_BBER
OTU2_SES
LSCLCMIN
ODU2_TCMn_BIAES
OTU2_SESR
LSIOPCUR
ODU2_TCMn_ES
OTU2_UAS
LSIOPMAX
ODU2_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU2_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU2_TCMn_FEES
RSES
LSOOPMAX
ODU2_TCMn_FESES
RSSES
LSOOPMIN
ODU2_TCMn_FESESR
RSUAS
LSTMPCUR
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU2_TCMn_SES
XCSTMPMIN
ODU2_PM_BBE
ODU2_TCMn_SESR
NOTE
TCM6.
NOTE
5.2.23 LEX4 Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU2_PM_BBER
ODU2_TCMn_UAS
FEC_AFT_COR_ER
ODU2_PM_ES
OTU2_BBE
FEC_BEF_CORER_FLOAT
ODU2_PM_FEBBE
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBER
OTU2_BIAES
FEC_COR_0BIT_CNT
ODU2_PM_FEES
OTU2_ES
FEC_COR_1BIT_CNT
ODU2_PM_FESES
OTU2_FEBBE
FEC_COR_BYTE_CNT
ODU2_PM_FESESR
OTU2_FEBBER
FEC_UNCOR_BLOCK_CN
T
ODU2_PM_FEUAS
OTU2_FEES
LSBIASCUR
ODU2_PM_SES
OTU2_FESES
LSBIASMAX
ODU2_PM_SESR
OTU2_FESESR

773
OptiX OSN 8800/6800/3800

LSBIASMIN
ODU2_PM_UAS
OTU2_FEUAS
LSCLCCUR
ODU2_TCMn_BBE
OTU2_IAES
LSCLCMAX
ODU2_TCMn_BBER
OTU2_SES
LSCLCMIN
ODU2_TCMn_BIAES
OTU2_SESR
LSIOPCUR
ODU2_TCMn_ES
OTU2_UAS
LSIOPMAX
ODU2_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU2_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU2_TCMn_FEES
RSES
LSOOPMAX
ODU2_TCMn_FESES
RSSES
LSOOPMIN
ODU2_TCMn_FESESR
RSUAS
LSTMPCUR
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU2_TCMn_SES
XCSTMPMIN
ODU2_PM_BBE
ODU2_TCMn_SESR
NOTE
TCM6.
NOTE
5.2.24 LOA Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU1_PM_SES
ODUFLEX_PM_FEBBE
FEC_AFT_COR_ER
ODU1_PM_SESR
ODUFLEX_PM_FEBBER
FEC_AFT_COR_ERAV
R
ODU1_PM_UAS
ODUFLEX_PM_FEES
FEC_BEF_CORER_FLO
AT
ODU1_TCMn_BBE
ODUFLEX_PM_FESES
FEC_BEF_COR_ER
ODU1_TCMn_BBER
ODUFLEX_PM_FESESR
FEC_BEF_COR_ERAV
R
ODU1_TCMn_BIAES
ODUFLEX_PM_FEUAS
FEC_COR_0BIT_CNT
ODU1_TCMn_ES
ODUFLEX_PM_SES
FEC_COR_1BIT_CNT
ODU1_TCMn_FEBBE
ODUFLEX_PM_SESR

774
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_COR_BYTE_CNT
ODU1_TCMn_FEBBER
ODUFLEX_PM_UAS
FEC_UNCOR_BLOCK_
CNT
ODU1_TCMn_FEES
OTU1_BBE
LSBIASCUR
ODU1_TCMn_FESES
OTU1_BBER
LSBIASMAX
ODU1_TCMn_FESESR
OTU1_BIAES
LSBIASMIN
ODU1_TCMn_FEUAS
OTU1_ES
LSCLCCUR
ODU1_TCMn_IAES
OTU1_FEBBE
LSCLCMAX
ODU1_TCMn_SES
OTU1_FEBBER
LSCLCMIN
ODU1_TCMn_SESR
OTU1_FEES
LSIOPCUR
ODU1_TCMn_UAS
OTU1_FESES
LSIOPMAX
ODU2_PM_BBE
OTU1_FESESR
LSIOPMIN
ODU2_PM_BBER
OTU1_FEUAS
LSOOPCUR
ODU2_PM_ES
OTU1_IAES
LSOOPMAX
ODU2_PM_FEBBE
OTU1_SES
LSOOPMIN
ODU2_PM_FEBBER
OTU1_SESR
LSTMPCUR
ODU2_PM_FEES
OTU1_UAS
LSTMPMAX
ODU2_PM_FESES
OTU2_BBE
LSTMPMIN
ODU2_PM_FESESR
OTU2_BBER
ODU0_PM_BBE
ODU2_PM_FEUAS
OTU2_BIAES
ODU0_PM_BBER
ODU2_PM_SES
OTU2_ES
ODU0_PM_ES
ODU2_PM_SESR
OTU2_FEBBE
ODU0_PM_FEBBE
ODU2_PM_UAS
OTU2_FEBBER
ODU0_PM_FEBBER
ODU2_TCMn_BBE
OTU2_FEES
ODU0_PM_FEES
ODU2_TCMn_BBER
OTU2_FESES
ODU0_PM_FESES
ODU2_TCMn_BIAES
OTU2_FESESR
ODU0_PM_FESESR
ODU2_TCMn_ES
OTU2_FEUAS
ODU0_PM_FEUAS
ODU2_TCMn_FEBBE
OTU2_IAES
ODU0_PM_SES
ODU2_TCMn_FEBBER
OTU2_SES
ODU0_PM_SESR
ODU2_TCMn_FEES
OTU2_SESR
ODU0_PM_UAS
ODU2_TCMn_FESES
OTU2_UAS
ODU1_PM_BBE
ODU2_TCMn_FESESR
RSBBE

775
OptiX OSN 8800/6800/3800

ODU1_PM_BBER
ODU2_TCMn_FEUAS
RSCSES
ODU1_PM_ES
ODU2_TCMn_IAES
RSES
ODU1_PM_FEBBE
ODU2_TCMn_SES
RSOFS
ODU1_PM_FEBBER
ODU2_TCMn_SESR
RSSES
ODU1_PM_FEES
ODU2_TCMn_UAS
RSUAS
ODU1_PM_FESES
ODUFLEX_PM_BBE
XCSTMPCUR
ODU1_PM_FESESR
ODUFLEX_PM_BBER
XCSTMPMAX
ODU1_PM_FEUAS
ODUFLEX_PM_ES
XCSTMPMIN
NOTE
TCM6.
NOTE
5.2.25 LOG Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
LSTMPMAX
ODU2_TCMn_IAES
FEC_AFT_COR_ERAVR
LSTMPMIN
ODU2_TCMn_SES
FEC_AFT_CORER_FLOAT
ODU2_PM_BBER
ODU2_TCMn_SESR
FEC_BEF_COR_ER
ODU2_PM_ES
ODU2_TCMn_UAS
FEC_BEF_COR_ERAVR
ODU2_PM_FEBBE
ODU3_PM_BBE
FEC_BEF_CORER_FLOAT
ODU2_PM_FEBBER
OTU2_BBE
FEC_COR_0BIT_CNT
ODU2_PM_FEES
OTU2_BBER
FEC_COR_1BIT_CNT
ODU2_PM_FESES
OTU2_BIAES
FEC_COR_BYTE_CNT
ODU2_PM_FESESR
OTU2_ES
FEC_UNCOR_BLOCK_CNT
ODU2_PM_FEUAS
OTU2_FEBBE
LSBIASCUR
ODU2_PM_SES
OTU2_FEBBER
LSBIASMAX
ODU2_PM_SESR
OTU2_FEES
LSBIASMIN
ODU2_PM_UAS
OTU2_FESES
LSCLCCUR
ODU2_TCMn_BBE
OTU2_FESESR
LSCLCMAX
ODU2_TCMn_BBER
OTU2_FEUAS
LSCLCMIN
ODU2_TCMn_BIAES
OTU2_IAES

776
OptiX OSN 8800/6800/3800

LSIOPCUR
ODU2_TCMn_ES
OTU2_SES
LSIOPMAX
ODU2_TCMn_FEBBE
OTU2_SESR
LSIOPMIN
ODU2_TCMn_FEBBER
OTU2_UAS
LSOOPCUR
ODU2_TCMn_FEES
XCSTMPCUR
LSOOPMAX
ODU2_TCMn_FESES
XCSTMPMAX
LSOOPMIN
ODU2_TCMn_FESESR
XCSTMPMIN
LSTMPCUR
ODU2_TCMn_FEUAS
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Drop Events
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
(512~1023 Octets in
Length)

Octets in Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
FCS Errors

777
OptiX OSN 8800/6800/3800

NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
5.2.26 LOM Board Performance Event List

FEC_AFT_COR_ER
LSTMPMAX
ODU2_TCMn_FEUAS
FEC_AFT_COR_ERAVR
LSTMPMIN
ODU2_TCMn_IAES
FEC_BEF_CORER_FLOAT
ODU2_PM_BBE
ODU2_TCMn_SES
FEC_BEF_COR_ER
ODU2_PM_BBER
ODU2_TCMn_SESR
FEC_BEF_COR_ERAVR
ODU2_PM_ES
ODU2_TCMn_UAS
FEC_AFT_CORER_FLOAT
ODU2_PM_FEBBE
OTU2_BBE
FEC_COR_0BIT_CNT
ODU2_PM_FEBBER
OTU2_BBER
FEC_COR_1BIT_CNT
ODU2_PM_FEES
OTU2_BIAES
FEC_COR_BYTE_CNT
ODU2_PM_FESES
OTU2_ES
FEC_UNCOR_BLOCK_CNT
ODU2_PM_FESESR
OTU2_FEBBE
LSBISACUR
ODU2_PM_FEUAS
OTU2_FEBBER
LSBISAMAX
ODU2_PM_SES
OTU2_FEES
LSBISAMIN
ODU2_PM_SESR
OTU2_FESES
LSCLCCUR
ODU2_PM_UAS
OTU2_FESESR
LSCLCMAX
ODU2_TCMn_BBE
OTU2_FEUAS
LSCLCMIN
ODU2_TCMn_BBER
OTU2_IAES
LSIOPCUR
ODU2_TCMn_BIAES
OTU2_SES
LSIOPMAX
ODU2_TCMn_ES
OTU2_SESR
LSIOPMIN
ODU2_TCMn_FEBBE
OTU2_UAS
LSOOPCUR
ODU2_TCMn_FEBBER
XCSTMPCUR
LSOOPMAX
ODU2_TCMn_FEES
XCSTMPMAX
LSOOPMIN
ODU2_TCMn_FESES
XCSTMPMIN
LSTMPCUR
ODU2_TCMn_FESESR
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)

778
OptiX OSN 8800/6800/3800


Drop Events
Multicast Packets
Received
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
(512~1023 Octets in
Length)

Octets in Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
(256~511 Octets in
Length)
Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Bad Octets Received
FCS Errors
Drop Events at
FC Performance Event List

CLIENT_CRC_ERR
Issue 02 (2011-10-31)
FC_Client_RxOLSPrim_
Cnt
LINKTST_CNT
FC_Client_CreditZero_Cnt
FC_Client_Truncated
FrmCnt_sum
FC_Wsys_Crc_Err_Cnt
FC_Client_Invld_10BCode_
Cnt
FC_Client_Tx_NOS_Cnt
FC_Wsys_LinkDown_Cnt
CLIENT_RXBYTECNT_S
UM
FC_Client_Tx_Utilization
FC_Wsys_OverLongFrm_Su
m
CLIENT_RXFRMCNT_C1
CLIENT_TXBYTECNT_
SUM
FC_Wsys_Rx_PausePrim_Cn
t

779
OptiX OSN 8800/6800/3800

CLIENT_RXFRMCNT_C2
CLIENT_TXFRMCNT_C
1
FC_Wsys_Rx_PingAckPrim_
Cnt
CLIENT_RXFRMCNT_C3
CLIENT_TXFRMCNT_C
2
FC_Wsys_Rx_PingPrim_Cnt
CLIENT_RXFRMCNT_C4
CLIENT_TXFRMCNT_C
3
FC_Wsys_Rx_ResumePrim_
Cnt
CLIENT_RXFRMCNT_CF
CLIENT_TXFRMCNT_C
4
FC_Wsys_Truncated
FrmCnt_sum
CLIENT_RXFRMCNT_SU
M
CLIENT_TXFRMCNT_C
F
FC_Wsys_Tx_PausePrim_Cn
t
FC_Client_Rx_NOS_Cnt
CLIENT_TXFRMCNT_S
UM
FC_Wsys_Tx_PingAckPrim_
Cnt
FC_Client_Rx_Utilization
CLIENT_UNSUPOS_CN
T
FC_Wsys_Tx_PingPrim_Cnt
FC_Client_OverLongFrm_S
um
FC_Client_TxLRPrim_Cn
t
FC_Wsys_Tx_ResumePrim_
Cnt
FC_Client_RxLRPrim_Cnt
FC_Client_TxLRRPrim_
Cnt
FC_Wsys_unsupos_cnt
FC_Client_RxLRRPrim_Cnt
FC_Client_TxOLSPrim_
Cnt
5.2.27 LQMD Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_FEUAS
OTU1_FEES
LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR
LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS

780
OptiX OSN 8800/6800/3800

LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR
SEFS_S
RSOFS
NOTE
TCM6.
NOTE

TN11LQMD
Issue 02 (2011-10-31)
Drop Events
FCS and Alignment Errors
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
Packets Received
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

Octets in Length)
Packets Transmitted

781
OptiX OSN 8800/6800/3800

Packets Transmitted
Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
Drop Events at Transmission

Direction
Oversize Packets
Transmitted
TN12LQMD
Issue 02 (2011-10-31)
Broadcast Packets
Transmitted
Drop Events
Packets Received
Length)
Packets Received
(1519~MTU Octets in
Length)
Octets in Length)
Packets Transmitted
Packets Transmitted
Fragments
Packets Transmitted
Bad Octets Received
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Length)
Alignment Errors
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted

782
OptiX OSN 8800/6800/3800

Octets in Length)
Octets in Length)
Multicast Packets
Transmitted
5.2.28 LQMS Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_FEUAS
OTU1_FEES
LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR
LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR

783
OptiX OSN 8800/6800/3800

SEFS_S
RSOFS
NOTE
TCM6.
NOTE

TN11LQMS
Drop Events
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
Packets Received
Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Multicast Packets Broadcast
Bad Octets Received
Drop Events at Transmission

Direction
Oversize Packets
Transmitted
TN12LQMS

Issue 02 (2011-10-31)
Packets Received
Length)

Multicast Packets
Transmitted
784
OptiX OSN 8800/6800/3800

Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Packets Transmitted
Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors
Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
5.2.29 LQM Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBER
ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_ES
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
OTU1_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
OTU1_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
OTU1_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
OTU1_FEBBER
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_FEUAS
OTU1_FEES
LSBIASCUR
ODU1_PM_SES
OTU1_FESES
LSBIASMAX
ODU1_PM_SESR
OTU1_FESESR

785
OptiX OSN 8800/6800/3800

LSBIASMIN
ODU1_PM_UAS
OTU1_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
OTU1_IAES
LSCLCMAX
ODU1_TCMn_BBER
OTU1_SES
LSCLCMIN
ODU1_TCMn_BIAES
OTU1_SESR
LSIOPCUR
ODU1_TCMn_ES
OTU1_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU1_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU1_TCMn_FEES
RSES
LSOOPMAX
ODU1_TCMn_FESES
RSSES
LSOOPMIN
ODU1_TCMn_FESESR
RSUAS
LSTMPCUR
ODU1_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU1_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU1_TCMn_SES
XCSTMPMIN
ODU1_PM_BBE
ODU1_TCMn_SESR
SEFS_S
RSOFS
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Packets Transmitted
Fragments
Packets Transmitted

786
OptiX OSN 8800/6800/3800

Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors
Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
5.2.30 LSQ Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU3_PM_BBE
ODU3_TCMn_UAS
FEC_AFT_COR_ER
ODU3_PM_BBER
OTU3_BBE
FEC_AFT_COR_ERAVR
ODU3_PM_ES
OTU3_BBER
FEC_BEF_CORER_FLOAT
ODU3_PM_FEBBE
OTU3_BIAES
FEC_BEF_COR_ER
ODU3_PM_FEBBER
OTU3_ES
FEC_BEF_COR_ERAVR
ODU3_PM_FEES
OTU3_FEBBE
FEC_COR_0BIT_CNT
ODU3_PM_FESES
OTU3_FEBBER
FEC_COR_1BIT_CNT
ODU3_PM_FESESR
OTU3_FEES
FEC_COR_BYTE_CNT
ODU3_PM_FEUAS
OTU3_FESES
FEC_UNCOR_BLOCK_CN
T
ODU3_PM_SES
OTU3_FESESR
LSBIASCUR
ODU3_PM_SESR
OTU3_FEUAS
LSBIASMAX
ODU3_PM_UAS
OTU3_IAES
LSBIASMIN
ODU3_TCMn_BBE
OTU3_SES
LSCLCCUR
ODU3_TCMn_BBER
OTU3_SESR
LSCLCMAX
ODU3_TCMn_BIAES
OTU3_UAS
LSCLCMIN
ODU3_TCMn_ES
RSBBE
LSIOPCUR
ODU3_TCMn_FEBBE
RSCSES

787
OptiX OSN 8800/6800/3800

LSIOPMAX
ODU3_TCMn_FEBBER
RSES
LSIOPMIN
ODU3_TCMn_FEES
RSOFS
LSOOPCUR
ODU3_TCMn_FESES
RSSES
LSOOPMAX
ODU3_TCMn_FESESR
RSUAS
LSOOPMIN
ODU3_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU3_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU3_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU3_TCMn_SESR
NOTE
TCM6.
5.2.31 LSXLR Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
LSTMPMAX
ODU3_TCMn_FEUAS
FEC_AFT_COR_ERAVR
LSTMPMIN
ODU3_TCMn_IAES
FEC_AFT_CORER_FLOA
T
ODU3_PM_BBE
ODU3_TCMn_SES
FEC_BEF_COR_ER
ODU3_PM_BBER
ODU3_TCMn_SESR
FEC_BEF_COR_ERAVR
ODU3_PM_ES
ODU3_TCMn_UAS
FEC_BEF_CORER_FLOA
T
ODU3_PM_FEBBE
OTU3_BBE
FEC_COR_0BIT_CNT
ODU3_PM_FEBBER
OTU3_BBER
FEC_COR_1BIT_CNT
ODU3_PM_FEES
OTU3_BIAES
FEC_COR_BYTE_CNT
ODU3_PM_FESES
OTU3_ES
FEC_UNCOR_BLOCK_C
NT
ODU3_PM_FESESR
OTU3_FEBBE
LSBIASCUR
ODU3_PM_FEUAS
OTU3_FEBBER
LSBIASMAX
ODU3_PM_SES
OTU3_FEES
LSBIASMIN
ODU3_PM_SESR
OTU3_FESES
LSCLCCUR
ODU3_PM_UAS
OTU3_FESESR
LSCLCMAX
ODU3_TCMn_BBE
OTU3_FEUAS
LSCLCMIN
ODU3_TCMn_BBER
OTU3_IAES

788
OptiX OSN 8800/6800/3800

LSIOPCUR
ODU3_TCMn_BIAES
OTU3_SES
LSIOPMAX
ODU3_TCMn_ES
OTU3_SESR
LSIOPMIN
ODU3_TCMn_FEBBE
OTU3_UAS
LSOOPCUR
ODU3_TCMn_FEBBER
XCSTMPCUR
LSOOPMAX
ODU3_TCMn_FEES
XCSTMPMAX
LSOOPMIN
ODU3_TCMn_FESES
XCSTMPMIN
LSTMPCUR
ODU3_TCMn_FESESR
NOTE
TCM6.
5.2.32 LSXL Board Performance Event List

TN11LSXL/TN12LSXL
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU3_PM_BBE
ODU3_TCMn_UAS
FEC_AFT_COR_ER
ODU3_PM_BBER
OTU3_BBE
FEC_AFT_COR_ERAVR
ODU3_PM_ES
OTU3_BBER
FEC_BEF_CORER_FLOAT
ODU3_PM_FEBBE
OTU3_BIAES
FEC_BEF_COR_ER
ODU3_PM_FEBBER
OTU3_ES
FEC_BEF_COR_ERAVR
ODU3_PM_FEES
OTU3_FEBBE
FEC_COR_0BIT_CNT
ODU3_PM_FESES
OTU3_FEBBER
FEC_COR_1BIT_CNT
ODU3_PM_FESESR
OTU3_FEES
FEC_COR_BYTE_CNT
ODU3_PM_FEUAS
OTU3_FESES
FEC_UNCOR_BLOCK_CN
T
ODU3_PM_SES
OTU3_FESESR
LSBIASCUR
ODU3_PM_SESR
OTU3_FEUAS
LSBIASMAX
ODU3_PM_UAS
OTU3_IAES
LSBIASMIN
ODU3_TCMn_BBE
OTU3_SES
LSCLCCUR
ODU3_TCMn_BBER
OTU3_SESR
LSCLCMAX
ODU3_TCMn_BIAES
OTU3_UAS
LSCLCMIN
ODU3_TCMn_ES
RSBBE
LSIOPCUR
ODU3_TCMn_FEBBE
RSCSES

789
OptiX OSN 8800/6800/3800

LSIOPMAX
ODU3_TCMn_FEBBER
RSES
LSIOPMIN
ODU3_TCMn_FEES
RSOFS
LSOOPCUR
ODU3_TCMn_FESES
RSSES
LSOOPMAX
ODU3_TCMn_FESESR
RSUAS
LSOOPMIN
ODU3_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU3_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU3_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU3_TCMn_SESR
NOTE
TCM6.
5.2.33 LSXR Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU2_PM_BBE
ODU2_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU2_PM_BBER
OTU2_BBE
FEC_AFT_CORER_FLOA
T
ODU2_PM_ES
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBE
OTU2_BIAES
FEC_BEF_COR_ERAVR
ODU2_PM_FEBBER
OTU2_ES
FEC_BEF_CORER_FLOA
T
ODU2_PM_FEES
OTU2_FEBBE
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBER
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEES
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FESES
FEC_UNCOR_BLOCK_C
NT
ODU2_PM_SES
OTU2_FESESR
LSBIASCUR
ODU2_PM_SESR
OTU2_FEUAS
LSBIASMAX
ODU2_PM_UAS
OTU2_IAES
LSBIASMIN
ODU2_TCMn_BBE
OTU2_SES
LSCLCCUR
ODU2_TCMn_BBER
OTU2_SESR
LSCLCMAX
ODU2_TCMn_BIAES
OTU2_UAS
LSCLCMIN
ODU2_TCMn_ES
RSBBE

790
OptiX OSN 8800/6800/3800

LSIOPCUR
ODU2_TCMn_FEBBE
RSCSES
LSIOPMAX
ODU2_TCMn_FEBBER
RSES
LSIOPMIN
ODU2_TCMn_FEES
RSOFS
LSOOPCUR
ODU2_TCMn_FESES
RSSES
LSOOPMAX
ODU2_TCMn_FESESR
RSUAS
LSOOPMIN
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU2_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU2_TCMn_SESR
NOTE
TCM6.
NOTE
5.2.34 LSX Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU2_PM_BBE
ODU2_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU2_PM_BBER
OTU2_BBE
FEC_AFT_CORER_FLOA
T
ODU2_PM_ES
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBE
OTU2_BIAES
FEC_BEF_COR_ERAVR
ODU2_PM_FEBBER
OTU2_ES
FEC_BEF_CORER_FLOA
T
ODU2_PM_FEES
OTU2_FEBBE
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBER
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEES
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FESES
FEC_UNCOR_BLOCK_C
NT
ODU2_PM_SES
OTU2_FESESR
LSBIASCUR
ODU2_PM_SESR
OTU2_FEUAS
LSBIASMAX
ODU2_PM_UAS
OTU2_IAES
LSBIASMIN
ODU2_TCMn_BBE
OTU2_SES

791
OptiX OSN 8800/6800/3800

LSCLCCUR
ODU2_TCMn_BBER
OTU2_SESR
LSCLCMAX
ODU2_TCMn_BIAES
OTU2_UAS
LSCLCMIN
ODU2_TCMn_ES
RSBBE
LSIOPCUR
ODU2_TCMn_FEBBE
RSCSES
LSIOPMAX
ODU2_TCMn_FEBBER
RSES
LSIOPMIN
ODU2_TCMn_FEES
RSOFS
LSOOPCUR
ODU2_TCMn_FESES
RSSES
LSOOPMAX
ODU2_TCMn_FESESR
RSUAS
LSOOPMIN
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU2_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU2_TCMn_SESR
NOTE
TCM6.
NOTE
Issue 02 (2011-10-31)
Octets Received
Packets Received
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
Length)

Octets in Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted

792
OptiX OSN 8800/6800/3800

Alignment Errors
FCS Errors
Packets Transmitted
Octets Transmitted
5.2.35 LWX2 Board Performance Event List

LSBIASCUR
LSIOPMIN
RSCSES
LSBIASMAX
LSOOPCUR
RSES
LSBIASMIN
LSOOPMAX
RSOFS
LSCLCCUR
LSOOPMIN
RSSES
LSCLCMAX
LSTMPCUR
RSUAS
LSCLCMIN
LSTMPMAX
XCSTMPCUR
LSIOPCUR
LSTMPMIN
XCSTMPMAX
LSIOPMAX
RSBBE
XCSTMPMIN
5.2.36 LWXD Board Performance Event List

LSBIASCUR
LSIOPMIN
RSCSES
LSBIASMAX
LSOOPCUR
RSES
LSBIASMIN
LSOOPMAX
RSOFS
LSCLCCUR
LSOOPMIN
RSSES
LSCLCMAX
LSTMPCUR
RSUAS
LSCLCMIN
LSTMPMAX
XCSTMPCUR
LSIOPCUR
LSTMPMIN
XCSTMPMAX
LSIOPMAX
RSBBE
XCSTMPMIN
5.2.37 LWXS Board Performance Event List
Issue 02 (2011-10-31)
LSBIASCUR
LSIOPMIN
RSCSES
LSBIASMAX
LSOOPCUR
RSES
LSBIASMIN
LSOOPMAX
RSOFS
LSCLCCUR
LSOOPMIN
RSSES

793
OptiX OSN 8800/6800/3800

LSCLCMAX
LSTMPCUR
RSUAS
LSCLCMIN
LSTMPMAX
XCSTMPCUR
LSIOPCUR
LSTMPMIN
XCSTMPMAX
LSIOPMAX
RSBBE
XCSTMPMIN
5.2.38 M40V Board Performance Event List

ICTMPCUR
SUMOOPCUR
XCSTMPCUR
ICTMPMAX
SUMOOPMAX
XCSTMPMAX
ICTMPMIN
SUMOOPMIN
XCSTMPMIN
5.2.39 M40 Board Performance Event List

TN12M40
ICCLCCUR
ICTMPMIN
SUMOOPMAX
ICCLCMAX
SUMIOPCUR
SUMOOPMIN
ICCLCMIN
SUMIOPMAX
XCSTMPCUR
ICTMPCUR
SUMIOPMIN
XCSTMPMAX
ICTMPMAX
SUMOOPCUR
XCSTMPMIN
TN11M40
ICCLCCUR
ICTMPMAX
SUMOOPMIN
ICCLCMAX
ICTMPMIN
XCSTMPCUR
ICCLCMIN
SUMOOPCUR
XCSTMPMAX
ICTMPCUR
SUMOOPMAX
XCSTMPMIN
5.2.40 MCA4 Board Performance Event List
Issue 02 (2011-10-31)
PCLSOPCUR
PCLSSNMIN
PCLSWLOMAX
PCLSOPMAX
PCLSWLCUR
PCLSWLOMIN
PCLSOPMIN
PCLSWLMAX
XCSTMPCUR

794
OptiX OSN 8800/6800/3800

PCLSSNCUR
PCLSWLMIN
XCSTMPMAX
PCLSSNMAX
PCLSWLOCUR
XCSTMPMIN
5.2.41 MCA8 Board Performance Event List

PCLSOPCUR
PCLSSNMIN
PCLSWLOMAX
PCLSOPMAX
PCLSWLCUR
PCLSWLOMIN
PCLSOPMIN
PCLSWLMAX
XCSTMPCUR
PCLSSNCUR
PCLSWLMIN
XCSTMPMAX
PCLSSNMAX
PCLSWLOCUR
XCSTMPMIN
5.2.42 MR8V Board Performance Event List

XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
5.2.43 ND2 Board Performance Event List

TN53ND2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_TCMn_FESES
ODU2_PM_UAS
FEC_AFT_COR_ER
ODU0_TCMn_FESESR
ODU2_TCMn_BBE
FEC_AFT_COR_ERAV
R
ODU0_TCMn_FEUAS
ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT
ODU0_TCMn_IAES
ODU2_TCMn_BIAES
FEC_BEF_COR_ER
ODU0_TCMn_SES
ODU2_TCMn_ES
FEC_BEF_COR_ERAV
R
ODU0_TCMn_SESR
ODU2_TCMn_FEBBE
FEC_COR_0BIT_CNT
ODU0_TCMn_UAS
ODU2_TCMn_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
ODU2_TCMn_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
ODU2_TCMn_FESES
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_ES
ODU2_TCMn_FESESR

795
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
LSBIASCUR
ODU1_PM_FEBBE
ODU2_TCMn_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
ODU2_TCMn_IAES
LSBIASMIN
ODU1_PM_FEES
ODU2_TCMn_SES
LSCLCCUR
ODU1_PM_FESES
ODU2_TCMn_SESR
LSCLCMAX
ODU1_PM_FESESR
ODU2_TCMn_UAS
LSCLCMIN
ODU1_PM_FEUAS
ODUFLEX_PM_BBE
LSIOPCUR
ODU1_PM_SES
ODUFLEX_PM_BBER
LSIOPMAX
ODU1_PM_SESR
ODUFLEX_PM_ES
LSIOPMIN
ODU1_PM_UAS
ODUFLEX_PM_FEBBE
LSOOPCUR
ODU1_TCMn_BBE
ODUFLEX_PM_FEBBER
LSOOPMAX
ODU1_TCMn_BBER
ODUFLEX_PM_FEES
LSOOPMIN
ODU1_TCMn_BIAES
ODUFLEX_PM_FESES
LSTMPCUR
ODU1_TCMn_ES
ODUFLEX_PM_FESESR
LSTMPMAX
ODU1_TCMn_FEBBE
ODUFLEX_PM_FEUAS
LSTMPMIN
ODU1_TCMn_FEBBER
ODUFLEX_PM_SES
ODU0_PM_BBE
ODU1_TCMn_FEES
ODUFLEX_PM_SESR
ODU0_PM_BBER
ODU1_TCMn_FESES
ODUFLEX_PM_UAS
ODU0_PM_ES
ODU1_TCMn_FESESR
OTU2_BBE
ODU0_PM_FEBBE
ODU1_TCMn_FEUAS
OTU2_BBER
ODU0_PM_FEBBER
ODU1_TCMn_IAES
OTU2_BIAES
ODU0_PM_FEES
ODU1_TCMn_SES
OTU2_ES
ODU0_PM_FESES
ODU1_TCMn_SESR
OTU2_FEBBE
ODU0_PM_FESESR
ODU1_TCMn_UAS
OTU2_FEBBER
ODU0_PM_FEUAS
ODU2_PM_BBE
OTU2_FEES
ODU0_PM_SES
ODU2_PM_BBER
OTU2_FESES
ODU0_PM_SESR
ODU2_PM_ES
OTU2_FESESR
ODU0_PM_UAS
ODU2_PM_FEBBE
OTU2_FEUAS
ODU0_TCMn_BBE
ODU2_PM_FEBBER
OTU2_IAES
ODU0_TCMn_BBER
ODU2_PM_FEES
OTU2_SES
ODU0_TCMn_BIAES
ODU2_PM_FESES
OTU2_SESR
ODU0_TCMn_ES
ODU2_PM_FESESR
OTU2_UAS

796
OptiX OSN 8800/6800/3800

ODU0_TCMn_FEBBE
ODU2_PM_FEUAS
XCSTMPCUR
ODU0_TCMn_FEBBER
ODU2_PM_SES
XCSTMPMAX
ODU0_TCMn_FEES
ODU2_PM_SESR
XCSTMPMIN
TN53ND2 (COMP)
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU0_PM_UAS
ODU2_PM_SES
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAVR
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLOAT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES
LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE
LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER
LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES

797
OptiX OSN 8800/6800/3800

ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS
ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR
ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN52ND2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_PM_UAS
ODU2_PM_SES
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAV
R
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAV
R
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES

798
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE
LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER
LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES
ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS
ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR
ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN12ND2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_SES
ODU2_TCMn_BIAES
FEC_AFT_COR_ER
ODU1_PM_SESR
ODU2_TCMn_ES
FEC_AFT_COR_ERAVR
ODU1_PM_UAS
ODU2_TCMn_FEBBE
FEC_BEF_CORER_FLOAT
ODU1_TCMn_BBE
ODU2_TCMn_FEBBER
FEC_BEF_COR_ER
ODU1_TCMn_BBER
ODU2_TCMn_FEES
FEC_BEF_COR_ERAVR
ODU1_TCMn_BIAES
ODU2_TCMn_FESES
FEC_COR_0BIT_CNT
ODU1_TCMn_ES
ODU2_TCMn_FESESR

799
OptiX OSN 8800/6800/3800

FEC_COR_1BIT_CNT
ODU1_TCMn_FEBBE
ODU2_TCMn_FEUAS
FEC_COR_BYTE_CNT
ODU1_TCMn_FEBBER
ODU2_TCMn_IAES
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEES
ODU2_TCMn_SES
LSBIASCUR
ODU1_TCMn_FESES
ODU2_TCMn_SESR
LSBIASMAX
ODU1_TCMn_FESESR
ODU2_TCMn_UAS
LSBIASMIN
ODU1_TCMn_FEUAS
OTU2_BBE
LSIOPCUR
ODU1_TCMn_IAES
OTU2_BBER
LSIOPMAX
ODU1_TCMn_SES
OTU2_BIAES
LSIOPMIN
ODU1_TCMn_SESR
OTU2_ES
LSOOPCUR
ODU1_TCMn_UAS
OTU2_FEBBE
LSOOPMAX
ODU2_PM_BBE
OTU2_FEBBER
LSOOPMIN
ODU2_PM_BBER
OTU2_FEES
LSTMPCUR
ODU2_PM_ES
OTU2_FESES
LSTMPMAX
ODU2_PM_FEBBE
OTU2_FESESR
LSTMPMIN
ODU2_PM_FEBBER
OTU2_FEUAS
ODU1_PM_BBE
ODU2_PM_FEES
OTU2_IAES
ODU1_PM_BBER
ODU2_PM_FESES
OTU2_SES
ODU1_PM_ES
ODU2_PM_FESESR
OTU2_SESR
ODU1_PM_FEBBE
ODU2_PM_FEUAS
OTU2_UAS
ODU1_PM_FEBBER
ODU2_PM_SES
XCSTMPCUR
ODU1_PM_FEES
ODU2_PM_SESR
XCSTMPMAX
ODU1_PM_FESES
ODU2_PM_UAS
XCSTMPMIN
ODU1_PM_FESESR
ODU2_TCMn_BBE
ODU1_PM_FEUAS
ODU2_TCMn_BBER
TN11ND2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_FESESR
ODU2_TCMn_BBER
FEC_AFT_COR_ER
ODU1_PM_FEUAS
ODU2_TCMn_BIAES
FEC_AFT_COR_ERAVR
ODU1_PM_SES
ODU2_TCMn_ES
FEC_BEF_CORER_FLOAT
ODU1_PM_SESR
ODU2_TCMn_FEBBE

800
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_BEF_COR_ER
ODU1_PM_UAS
ODU2_TCMn_FEBBER
FEC_BEF_COR_ERAVR
ODU1_TCMn_BBE
ODU2_TCMn_FEES
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU2_TCMn_FESES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU2_TCMn_FESESR
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU2_TCMn_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU2_TCMn_IAES
LSBIASCUR
ODU1_TCMn_FEBBER
ODU2_TCMn_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU2_TCMn_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU2_TCMn_UAS
LSCLCCUR
ODU1_TCMn_FESESR
OTU2_BBE
LSCLCMAX
ODU1_TCMn_FEUAS
OTU2_BBER
LSCLCMIN
ODU1_TCMn_IAES
OTU2_BIAES
LSIOPCUR
ODU1_TCMn_SES
OTU2_ES
LSIOPMAX
ODU1_TCMn_SESR
OTU2_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
OTU2_FEBBER
LSOOPCUR
ODU2_PM_BBE
OTU2_FEES
LSOOPMAX
ODU2_PM_BBER
OTU2_FESES
LSOOPMIN
ODU2_PM_ES
OTU2_FESESR
LSTMPCUR
ODU2_PM_FEBBE
OTU2_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
OTU2_IAES
LSTMPMIN
ODU2_PM_FEES
OTU2_SES
ODU1_PM_BBE
ODU2_PM_FESES
OTU2_SESR
ODU1_PM_BBER
ODU2_PM_FESESR
OTU2_UAS
ODU1_PM_ES
ODU2_PM_FEUAS
XCSTMPCUR
ODU1_PM_FEBBE
ODU2_PM_SES
XCSTMPMAX
ODU1_PM_FEBBER
ODU2_PM_SESR
XCSTMPMIN
ODU1_PM_FEES
ODU2_PM_UAS
ODU1_PM_FESES
ODU2_TCMn_BBE

801
OptiX OSN 8800/6800/3800

NOTE
TCM6.
NOTE
5.2.44 NQ2 Board Performance Event List

TN54NQ2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_BBER
ODU2_PM_SESR
FEC_AFT_COR_ER
ODU1_PM_ES
ODU2_PM_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_FEBBE
ODU2_TCMn_BBE
FEC_BEF_CORER_FLOAT
ODU1_PM_FEBBER
ODU2_TCMn_BBER
FEC_BEF_COR_ER
ODU1_PM_FEES
ODU2_TCMn_BIAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESES
ODU2_TCMn_ES
FEC_COR_0BIT_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBE
FEC_COR_1BIT_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEBBER
FEC_COR_BYTE_CNT
ODU1_PM_SES
ODU2_TCMn_FEES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_SESR
ODU2_TCMn_FESES
LSBIASCUR
ODU1_PM_UAS
ODU2_TCMn_FESESR
LSBIASMAX
ODU1_TCMn_BBE
ODU2_TCMn_FEUAS
LSBIASMIN
ODU1_TCMn_BBER
ODU2_TCMn_IAES
LSIOPCUR
ODU1_TCMn_BIAES
ODU2_TCMn_SES
LSIOPMAX
ODU1_TCMn_ES
ODU2_TCMn_SESR
LSIOPMIN
ODU1_TCMn_FEBBE
ODU2_TCMn_UAS
LSOOPCUR
ODU1_TCMn_FEBBER
OTU2_BBE
LSOOPMAX
ODU1_TCMn_FEES
OTU2_BBER
LSOOPMIN
ODU1_TCMn_FESES
OTU2_BIAES
LSTMPCUR
ODU1_TCMn_FESESR
OTU2_ES
LSTMPMAX
ODU1_TCMn_FEUAS
OTU2_FEBBE
LSTMPMIN
ODU1_TCMn_IAES
OTU2_FEBBER
ODU0_PM_BBE
ODU1_TCMn_SES
OTU2_FEES
ODU0_PM_BBER
ODU1_TCMn_SESR
OTU2_FESES
ODU0_PM_ES
ODU1_TCMn_UAS
OTU2_FESESR

802
OptiX OSN 8800/6800/3800

ODU0_PM_FEBBE
ODU2_PM_BBE
OTU2_FEUAS
ODU0_PM_FEBBER
ODU2_PM_BBER
OTU2_IAES
ODU0_PM_FEES
ODU2_PM_ES
OTU2_SES
ODU0_PM_FESES
ODU2_PM_FEBBE
OTU2_SESR
ODU0_PM_FESESR
ODU2_PM_FEBBER
OTU2_UAS
ODU0_PM_FEUAS
ODU2_PM_FEES
XCSTMPCUR
ODU0_PM_SES
ODU2_PM_FESES
XCSTMPMAX
ODU0_PM_SESR
ODU2_PM_FESESR
XCSTMPMIN
ODU0_PM_UAS
ODU2_PM_FEUAS
ODU1_PM_BBE
ODU2_PM_SES
TN53NQ2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_TCMn_FESES
ODU2_PM_UAS
FEC_AFT_COR_ER
ODU0_TCMn_FESESR
ODU2_TCMn_BBE
FEC_AFT_COR_ERAV
R
ODU0_TCMn_FEUAS
ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT
ODU0_TCMn_IAES
ODU2_TCMn_BIAES
FEC_BEF_COR_ER
ODU0_TCMn_SES
ODU2_TCMn_ES
FEC_BEF_COR_ERAV
R
ODU0_TCMn_SESR
ODU2_TCMn_FEBBE
FEC_COR_0BIT_CNT
ODU0_TCMn_UAS
ODU2_TCMn_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
ODU2_TCMn_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
ODU2_TCMn_FESES
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_ES
ODU2_TCMn_FESESR
LSBIASCUR
ODU1_PM_FEBBE
ODU2_TCMn_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
ODU2_TCMn_IAES
LSBIASMIN
ODU1_PM_FEES
ODU2_TCMn_SES
LSCLCCUR
ODU1_PM_FESES
ODU2_TCMn_SESR
LSCLCMAX
ODU1_PM_FESESR
ODU2_TCMn_UAS
LSCLCMIN
ODU1_PM_FEUAS
ODUFLEX_PM_BBE

803
OptiX OSN 8800/6800/3800

LSIOPCUR
ODU1_PM_SES
ODUFLEX_PM_BBER
LSIOPMAX
ODU1_PM_SESR
ODUFLEX_PM_ES
LSIOPMIN
ODU1_PM_UAS
ODUFLEX_PM_FEBBE
LSOOPCUR
ODU1_TCMn_BBE
ODUFLEX_PM_FEBBER
LSOOPMAX
ODU1_TCMn_BBER
ODUFLEX_PM_FEES
LSOOPMIN
ODU1_TCMn_BIAES
ODUFLEX_PM_FESES
LSTMPCUR
ODU1_TCMn_ES
ODUFLEX_PM_FESESR
LSTMPMAX
ODU1_TCMn_FEBBE
ODUFLEX_PM_FEUAS
LSTMPMIN
ODU1_TCMn_FEBBER
ODUFLEX_PM_SES
ODU0_PM_BBE
ODU1_TCMn_FEES
ODUFLEX_PM_SESR
ODU0_PM_BBER
ODU1_TCMn_FESES
ODUFLEX_PM_UAS
ODU0_PM_ES
ODU1_TCMn_FESESR
OTU2_BBE
ODU0_PM_FEBBE
ODU1_TCMn_FEUAS
OTU2_BBER
ODU0_PM_FEBBER
ODU1_TCMn_IAES
OTU2_BIAES
ODU0_PM_FEES
ODU1_TCMn_SES
OTU2_ES
ODU0_PM_FESES
ODU1_TCMn_SESR
OTU2_FEBBE
ODU0_PM_FESESR
ODU1_TCMn_UAS
OTU2_FEBBER
ODU0_PM_FEUAS
ODU2_PM_BBE
OTU2_FEES
ODU0_PM_SES
ODU2_PM_BBER
OTU2_FESES
ODU0_PM_SESR
ODU2_PM_ES
OTU2_FESESR
ODU0_PM_UAS
ODU2_PM_FEBBE
OTU2_FEUAS
ODU0_TCMn_BBE
ODU2_PM_FEBBER
OTU2_IAES
ODU0_TCMn_BBER
ODU2_PM_FEES
OTU2_SES
ODU0_TCMn_BIAES
ODU2_PM_FESES
OTU2_SESR
ODU0_TCMn_ES
ODU2_PM_FESESR
OTU2_UAS
ODU0_TCMn_FEBBE
ODU2_PM_FEUAS
XCSTMPCUR
ODU0_TCMn_FEBBER
ODU2_PM_SES
XCSTMPMAX
ODU0_TCMn_FEES
ODU2_PM_SESR
XCSTMPMIN
TN53NQ2 (COMP)
Issue 02 (2011-10-31)

804
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU0_PM_UAS
ODU2_PM_SES
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAVR
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLOAT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES
LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE
LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER
LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES
ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS

805
OptiX OSN 8800/6800/3800

ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR
ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN52NQ2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU0_PM_UAS
ODU2_PM_SES
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAVR
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLOAT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES
LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE
LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER

806
OptiX OSN 8800/6800/3800

LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES
ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS
ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR
ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN51NQ2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_FESESR
ODU2_TCMn_BBER
FEC_AFT_COR_ER
ODU1_PM_FEUAS
ODU2_TCMn_BIAES
FEC_AFT_COR_ERAVR
ODU1_PM_SES
ODU2_TCMn_ES
FEC_BEF_CORER_FLOAT
ODU1_PM_SESR
ODU2_TCMn_FEBBE
FEC_BEF_COR_ER
ODU1_PM_UAS
ODU2_TCMn_FEBBER
FEC_BEF_COR_ERAVR
ODU1_TCMn_BBE
ODU2_TCMn_FEES
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU2_TCMn_FESES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU2_TCMn_FESESR
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU2_TCMn_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU2_TCMn_IAES
LSBIASCUR
ODU1_TCMn_FEBBER
ODU2_TCMn_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU2_TCMn_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU2_TCMn_UAS
LSCLCCUR
ODU1_TCMn_FESESR
OTU2_BBE
LSCLCMAX
ODU1_TCMn_FEUAS
OTU2_BBER

807
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU1_TCMn_IAES
OTU2_BIAES
LSIOPCUR
ODU1_TCMn_SES
OTU2_ES
LSIOPMAX
ODU1_TCMn_SESR
OTU2_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
OTU2_FEBBER
LSOOPCUR
ODU2_PM_BBE
OTU2_FEES
LSOOPMAX
ODU2_PM_BBER
OTU2_FESES
LSOOPMIN
ODU2_PM_ES
OTU2_FESESR
LSTMPCUR
ODU2_PM_FEBBE
OTU2_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
OTU2_IAES
LSTMPMIN
ODU2_PM_FEES
OTU2_SES
ODU1_PM_BBE
ODU2_PM_FESES
OTU2_SESR
ODU1_PM_BBER
ODU2_PM_FESESR
OTU2_UAS
ODU1_PM_ES
ODU2_PM_FEUAS
XCSTMPCUR
ODU1_PM_FEBBE
ODU2_PM_SES
XCSTMPMAX
ODU1_PM_FEBBER
ODU2_PM_SESR
XCSTMPMIN
ODU1_PM_FEES
ODU2_PM_UAS
ODU1_PM_FESES
ODU2_TCMn_BBE
NOTE
TCM6.
NOTE
5.2.45 NPO2 Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_BBER
ODU2_PM_SESR
FEC_AFT_COR_ER
ODU1_PM_ES
ODU2_PM_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_FEBBE
ODU2_TCMn_BBE
FEC_BEF_CORER_FLOAT
ODU1_PM_FEBBER
ODU2_TCMn_BBER
FEC_BEF_COR_ER
ODU1_PM_FEES
ODU2_TCMn_BIAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESES
ODU2_TCMn_ES
FEC_COR_0BIT_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBE

808
OptiX OSN 8800/6800/3800

FEC_COR_1BIT_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEBBER
FEC_COR_BYTE_CNT
ODU1_PM_SES
ODU2_TCMn_FEES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_SESR
ODU2_TCMn_FESES
LSBIASCUR
ODU1_PM_UAS
ODU2_TCMn_FESESR
LSBIASMAX
ODU1_TCMn_BBE
ODU2_TCMn_FEUAS
LSBIASMIN
ODU1_TCMn_BBER
ODU2_TCMn_IAES
LSIOPCUR
ODU1_TCMn_BIAES
ODU2_TCMn_SES
LSIOPMAX
ODU1_TCMn_ES
ODU2_TCMn_SESR
LSIOPMIN
ODU1_TCMn_FEBBE
ODU2_TCMn_UAS
LSOOPCUR
ODU1_TCMn_FEBBER
OTU2_BBE
LSOOPMAX
ODU1_TCMn_FEES
OTU2_BBER
LSOOPMIN
ODU1_TCMn_FESES
OTU2_BIAES
LSTMPCUR
ODU1_TCMn_FESESR
OTU2_ES
LSTMPMAX
ODU1_TCMn_FEUAS
OTU2_FEBBE
LSTMPMIN
ODU1_TCMn_IAES
OTU2_FEBBER
ODU0_PM_BBE
ODU1_TCMn_SES
OTU2_FEES
ODU0_PM_BBER
ODU1_TCMn_SESR
OTU2_FESES
ODU0_PM_ES
ODU1_TCMn_UAS
OTU2_FESESR
ODU0_PM_FEBBE
ODU2_PM_BBE
OTU2_FEUAS
ODU0_PM_FEBBER
ODU2_PM_BBER
OTU2_IAES
ODU0_PM_FEES
ODU2_PM_ES
OTU2_SES
ODU0_PM_FESES
ODU2_PM_FEBBE
OTU2_SESR
ODU0_PM_FESESR
ODU2_PM_FEBBER
OTU2_UAS
ODU0_PM_FEUAS
ODU2_PM_FEES
XCSTMPCUR
ODU0_PM_SES
ODU2_PM_FESES
XCSTMPMAX
ODU0_PM_SESR
ODU2_PM_FESESR
XCSTMPMIN
ODU0_PM_UAS
ODU2_PM_FEUAS
ODU1_PM_BBE
ODU2_PM_SES
NOTE
Issue 02 (2011-10-31)

809
OptiX OSN 8800/6800/3800

5.2.46 NPO2E Board Performance Event List

TN55NPO2E
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_BBER
ODU2_PM_SESR
FEC_AFT_COR_ER
ODU1_PM_ES
ODU2_PM_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_FEBBE
ODU2_TCMn_BBE
FEC_BEF_CORER_FLOAT
ODU1_PM_FEBBER
ODU2_TCMn_BBER
FEC_BEF_COR_ER
ODU1_PM_FEES
ODU2_TCMn_BIAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESES
ODU2_TCMn_ES
FEC_COR_0BIT_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBE
FEC_COR_1BIT_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEBBER
FEC_COR_BYTE_CNT
ODU1_PM_SES
ODU2_TCMn_FEES
FEC_UNCOR_BLOCK_CNT
ODU1_PM_SESR
ODU2_TCMn_FESES
LSBIASCUR
ODU1_PM_UAS
ODU2_TCMn_FESESR
LSBIASMAX
ODU1_TCMn_BBE
ODU2_TCMn_FEUAS
LSBIASMIN
ODU1_TCMn_BBER
ODU2_TCMn_IAES
LSIOPCUR
ODU1_TCMn_BIAES
ODU2_TCMn_SES
LSIOPMAX
ODU1_TCMn_ES
ODU2_TCMn_SESR
LSIOPMIN
ODU1_TCMn_FEBBE
ODU2_TCMn_UAS
LSOOPCUR
ODU1_TCMn_FEBBER
OTU2_BBE
LSOOPMAX
ODU1_TCMn_FEES
OTU2_BBER
LSOOPMIN
ODU1_TCMn_FESES
OTU2_BIAES
LSTMPCUR
ODU1_TCMn_FESESR
OTU2_ES
LSTMPMAX
ODU1_TCMn_FEUAS
OTU2_FEBBE
LSTMPMIN
ODU1_TCMn_IAES
OTU2_FEBBER
ODU0_PM_BBE
ODU1_TCMn_SES
OTU2_FEES
ODU0_PM_BBER
ODU1_TCMn_SESR
OTU2_FESES
ODU0_PM_ES
ODU1_TCMn_UAS
OTU2_FESESR
ODU0_PM_FEBBE
ODU2_PM_BBE
OTU2_FEUAS
ODU0_PM_FEBBER
ODU2_PM_BBER
OTU2_IAES
ODU0_PM_FEES
ODU2_PM_ES
OTU2_SES
ODU0_PM_FESES
ODU2_PM_FEBBE
OTU2_SESR

810
OptiX OSN 8800/6800/3800

ODU0_PM_FESESR
ODU2_PM_FEBBER
OTU2_UAS
ODU0_PM_FEUAS
ODU2_PM_FEES
XCSTMPCUR
ODU0_PM_SES
ODU2_PM_FESES
XCSTMPMAX
ODU0_PM_SESR
ODU2_PM_FESESR
XCSTMPMIN
ODU0_PM_UAS
ODU2_PM_FEUAS
ODU1_PM_BBE
ODU2_PM_SES
NOTE
5.2.47 NS2 Board Performance Event List

TN53NS2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_TCMn_FESES
ODU2_PM_UAS
FEC_AFT_COR_ER
ODU0_TCMn_FESESR
ODU2_TCMn_BBE
FEC_AFT_COR_ERAV
R
ODU0_TCMn_FEUAS
ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT
ODU0_TCMn_IAES
ODU2_TCMn_BIAES
FEC_BEF_COR_ER
ODU0_TCMn_SES
ODU2_TCMn_ES
FEC_BEF_COR_ERAV
R
ODU0_TCMn_SESR
ODU2_TCMn_FEBBE
FEC_COR_0BIT_CNT
ODU0_TCMn_UAS
ODU2_TCMn_FEBBER
FEC_COR_1BIT_CNT
ODU1_PM_BBE
ODU2_TCMn_FEES
FEC_COR_BYTE_CNT
ODU1_PM_BBER
ODU2_TCMn_FESES
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_ES
ODU2_TCMn_FESESR
LSBIASCUR
ODU1_PM_FEBBE
ODU2_TCMn_FEUAS
LSBIASMAX
ODU1_PM_FEBBER
ODU2_TCMn_IAES
LSBIASMIN
ODU1_PM_FEES
ODU2_TCMn_SES
LSCLCCUR
ODU1_PM_FESES
ODU2_TCMn_SESR
LSCLCMAX
ODU1_PM_FESESR
ODU2_TCMn_UAS
LSCLCMIN
ODU1_PM_FEUAS
ODUFLEX_PM_BBE
LSIOPCUR
ODU1_PM_SES
ODUFLEX_PM_BBER

811
OptiX OSN 8800/6800/3800

LSIOPMAX
ODU1_PM_SESR
ODUFLEX_PM_ES
LSIOPMIN
ODU1_PM_UAS
ODUFLEX_PM_FEBBE
LSOOPCUR
ODU1_TCMn_BBE
ODUFLEX_PM_FEBBER
LSOOPMAX
ODU1_TCMn_BBER
ODUFLEX_PM_FEES
LSOOPMIN
ODU1_TCMn_BIAES
ODUFLEX_PM_FESES
LSTMPCUR
ODU1_TCMn_ES
ODUFLEX_PM_FESESR
LSTMPMAX
ODU1_TCMn_FEBBE
ODUFLEX_PM_FEUAS
LSTMPMIN
ODU1_TCMn_FEBBER
ODUFLEX_PM_SES
ODU0_PM_BBE
ODU1_TCMn_FEES
ODUFLEX_PM_SESR
ODU0_PM_BBER
ODU1_TCMn_FESES
ODUFLEX_PM_UAS
ODU0_PM_ES
ODU1_TCMn_FESESR
OTU2_BBE
ODU0_PM_FEBBE
ODU1_TCMn_FEUAS
OTU2_BBER
ODU0_PM_FEBBER
ODU1_TCMn_IAES
OTU2_BIAES
ODU0_PM_FEES
ODU1_TCMn_SES
OTU2_ES
ODU0_PM_FESES
ODU1_TCMn_SESR
OTU2_FEBBE
ODU0_PM_FESESR
ODU1_TCMn_UAS
OTU2_FEBBER
ODU0_PM_FEUAS
ODU2_PM_BBE
OTU2_FEES
ODU0_PM_SES
ODU2_PM_BBER
OTU2_FESES
ODU0_PM_SESR
ODU2_PM_ES
OTU2_FESESR
ODU0_PM_UAS
ODU2_PM_FEBBE
OTU2_FEUAS
ODU0_TCMn_BBE
ODU2_PM_FEBBER
OTU2_IAES
ODU0_TCMn_BBER
ODU2_PM_FEES
OTU2_SES
ODU0_TCMn_BIAES
ODU2_PM_FESES
OTU2_SESR
ODU0_TCMn_ES
ODU2_PM_FESESR
OTU2_UAS
ODU0_TCMn_FEBBE
ODU2_PM_FEUAS
XCSTMPCUR
ODU0_TCMn_FEBBER
ODU2_PM_SES
XCSTMPMAX
ODU0_TCMn_FEES
ODU2_PM_SESR
XCSTMPMIN
TN53NS2 (COMP)
FEC_AFT_CORER_FLOAT
Issue 02 (2011-10-31)
ODU0_PM_UAS

ODU2_PM_SES
812
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAVR
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLOAT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAVR
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES
LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE
LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER
LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES
ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS
ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR

813
OptiX OSN 8800/6800/3800

ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN52NS2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_PM_UAS
ODU2_PM_SES
FEC_AFT_COR_ER
ODU1_PM_BBE
ODU2_PM_SESR
FEC_AFT_COR_ERAV
R
ODU1_PM_BBER
ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT
ODU1_PM_ES
ODU2_TCMn_BBE
FEC_BEF_COR_ER
ODU1_PM_FEBBE
ODU2_TCMn_BBER
FEC_BEF_COR_ERAV
R
ODU1_PM_FEBBER
ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_FEES
ODU2_TCMn_ES
FEC_COR_1BIT_CNT
ODU1_PM_FESES
ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT
ODU1_PM_FESESR
ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_FEUAS
ODU2_TCMn_FEES
LSBIASCUR
ODU1_PM_SES
ODU2_TCMn_FESES
LSBIASMAX
ODU1_PM_SESR
ODU2_TCMn_FESESR
LSBIASMIN
ODU1_PM_UAS
ODU2_TCMn_FEUAS
LSCLCCUR
ODU1_TCMn_BBE
ODU2_TCMn_IAES
LSCLCMAX
ODU1_TCMn_BBER
ODU2_TCMn_SES
LSCLCMIN
ODU1_TCMn_BIAES
ODU2_TCMn_SESR
LSIOPCUR
ODU1_TCMn_ES
ODU2_TCMn_UAS
LSIOPMAX
ODU1_TCMn_FEBBE
OTU2_BBE
LSIOPMIN
ODU1_TCMn_FEBBER
OTU2_BBER
LSOOPCUR
ODU1_TCMn_FEES
OTU2_BIAES
LSOOPMAX
ODU1_TCMn_FESES
OTU2_ES
LSOOPMIN
ODU1_TCMn_FESESR
OTU2_FEBBE

814
OptiX OSN 8800/6800/3800

LSTMPCUR
ODU1_TCMn_FEUAS
OTU2_FEBBER
LSTMPMAX
ODU1_TCMn_IAES
OTU2_FEES
LSTMPMIN
ODU1_TCMn_SES
OTU2_FESES
ODU0_PM_BBE
ODU1_TCMn_SESR
OTU2_FESESR
ODU0_PM_BBER
ODU1_TCMn_UAS
OTU2_FEUAS
ODU0_PM_ES
ODU2_PM_BBE
OTU2_IAES
ODU0_PM_FEBBE
ODU2_PM_BBER
OTU2_SES
ODU0_PM_FEBBER
ODU2_PM_ES
OTU2_SESR
ODU0_PM_FEES
ODU2_PM_FEBBE
OTU2_UAS
ODU0_PM_FESES
ODU2_PM_FEBBER
XCSTMPCUR
ODU0_PM_FESESR
ODU2_PM_FEES
XCSTMPMAX
ODU0_PM_FEUAS
ODU2_PM_FESES
XCSTMPMIN
ODU0_PM_SES
ODU2_PM_FESESR
ODU0_PM_SESR
ODU2_PM_FEUAS
TN12NS2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_FESESR
ODU2_TCMn_BBER
FEC_AFT_COR_ER
ODU1_PM_FEUAS
ODU2_TCMn_BIAES
FEC_AFT_COR_ERAVR
ODU1_PM_SES
ODU2_TCMn_ES
FEC_BEF_CORER_FLOAT
ODU1_PM_SESR
ODU2_TCMn_FEBBE
FEC_BEF_COR_ER
ODU1_PM_UAS
ODU2_TCMn_FEBBER
FEC_BEF_COR_ERAVR
ODU1_TCMn_BBE
ODU2_TCMn_FEES
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU2_TCMn_FESES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU2_TCMn_FESESR
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU2_TCMn_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU2_TCMn_IAES
LSBIASCUR
ODU1_TCMn_FEBBER
ODU2_TCMn_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU2_TCMn_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU2_TCMn_UAS
LSCLCCUR
ODU1_TCMn_FESESR
OTU2_BBE

815
OptiX OSN 8800/6800/3800

LSCLCMAX
ODU1_TCMn_FEUAS
OTU2_BBER
LSCLCMIN
ODU1_TCMn_IAES
OTU2_BIAES
LSIOPCUR
ODU1_TCMn_SES
OTU2_ES
LSIOPMAX
ODU1_TCMn_SESR
OTU2_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
OTU2_FEBBER
LSOOPCUR
ODU2_PM_BBE
OTU2_FEES
LSOOPMAX
ODU2_PM_BBER
OTU2_FESES
LSOOPMIN
ODU2_PM_ES
OTU2_FESESR
LSTMPCUR
ODU2_PM_FEBBE
OTU2_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
OTU2_IAES
LSTMPMIN
ODU2_PM_FEES
OTU2_SES
ODU1_PM_BBE
ODU2_PM_FESES
OTU2_SESR
ODU1_PM_BBER
ODU2_PM_FESESR
OTU2_UAS
ODU1_PM_ES
ODU2_PM_FEUAS
XCSTMPCUR
ODU1_PM_FEBBE
ODU2_PM_SES
XCSTMPMAX
ODU1_PM_FEBBER
ODU2_PM_SESR
XCSTMPMIN
ODU1_PM_FEES
ODU2_PM_UAS
ODU1_PM_FESES
ODU2_TCMn_BBE
TN11NS2
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_FESESR
ODU2_TCMn_BBER
FEC_AFT_COR_ER
ODU1_PM_FEUAS
ODU2_TCMn_BIAES
FEC_AFT_COR_ERAVR
ODU1_PM_SES
ODU2_TCMn_ES
FEC_BEF_CORER_FLOAT
ODU1_PM_SESR
ODU2_TCMn_FEBBE
FEC_BEF_COR_ER
ODU1_PM_UAS
ODU2_TCMn_FEBBER
FEC_BEF_COR_ERAVR
ODU1_TCMn_BBE
ODU2_TCMn_FEES
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU2_TCMn_FESES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU2_TCMn_FESESR
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU2_TCMn_FEUAS
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU2_TCMn_IAES

816
OptiX OSN 8800/6800/3800

LSBIASCUR
ODU1_TCMn_FEBBER
ODU2_TCMn_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU2_TCMn_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU2_TCMn_UAS
LSCLCCUR
ODU1_TCMn_FESESR
OTU2_BBE
LSCLCMAX
ODU1_TCMn_FEUAS
OTU2_BBER
LSCLCMIN
ODU1_TCMn_IAES
OTU2_BIAES
LSIOPCUR
ODU1_TCMn_SES
OTU2_ES
LSIOPMAX
ODU1_TCMn_SESR
OTU2_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
OTU2_FEBBER
LSOOPCUR
ODU2_PM_BBE
OTU2_FEES
LSOOPMAX
ODU2_PM_BBER
OTU2_FESES
LSOOPMIN
ODU2_PM_ES
OTU2_FESESR
LSTMPCUR
ODU2_PM_FEBBE
OTU2_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
OTU2_IAES
LSTMPMIN
ODU2_PM_FEES
OTU2_SES
ODU1_PM_BBE
ODU2_PM_FESES
OTU2_SESR
ODU1_PM_BBER
ODU2_PM_FESESR
OTU2_UAS
ODU1_PM_ES
ODU2_PM_FEUAS
XCSTMPCUR
ODU1_PM_FEBBE
ODU2_PM_SES
XCSTMPMAX
ODU1_PM_FEBBER
ODU2_PM_SESR
XCSTMPMIN
ODU1_PM_FEES
ODU2_PM_UAS
ODU1_PM_FESES
ODU2_TCMn_BBE
NOTE
TCM6.
NOTE
5.2.48 NS3 Board Performance Event List

TN54NS3
FEC_AFT_CORER_FLOAT
Issue 02 (2011-10-31)
ODU1_PM_FESESR

ODU2_TCMn_UAS
817
OptiX OSN 8800/6800/3800

Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_FEUAS
ODU3_PM_BBE
FEC_AFT_COR_ERAVR
ODU1_PM_SES
ODU3_PM_BBER
FEC_BEF_CORER_FLOAT
ODU1_PM_SESR
ODU3_PM_ES
FEC_BEF_COR_ER
ODU1_PM_UAS
ODU3_PM_FEBBE
FEC_BEF_COR_ERAVR
ODU1_TCMn_BBE
ODU3_PM_FEBBER
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU3_PM_FEES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU3_PM_FESES
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU3_PM_FESESR
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU3_PM_FEUAS
LSBIASCUR
ODU1_TCMn_FEBBER
ODU3_PM_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU3_PM_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU3_PM_UAS
LSCLCCUR
ODU1_TCMn_FESESR
ODU3_TCMn_BBE
LSCLCMAX
ODU1_TCMn_FEUAS
ODU3_TCMn_BBER
LSCLCMIN
ODU1_TCMn_IAES
ODU3_TCMn_BIAES
LSIOPCUR
ODU1_TCMn_SES
ODU3_TCMn_ES
LSIOPMAX
ODU1_TCMn_SESR
ODU3_TCMn_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
ODU3_TCMn_FEBBER
LSOOPCUR
ODU2_PM_BBE
ODU3_TCMn_FEES
LSOOPMAX
ODU2_PM_BBER
ODU3_TCMn_FESES
LSOOPMIN
ODU2_PM_ES
ODU3_TCMn_FESESR
LSTMPCUR
ODU2_PM_FEBBE
ODU3_TCMn_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
ODU3_TCMn_IAES
LSTMPMIN
ODU2_PM_FEES
ODU3_TCMn_SES
ODU0_PM_BBE
ODU2_PM_FESES
ODU3_TCMn_SESR
ODU0_PM_BBER
ODU2_PM_FESESR
ODU3_TCMn_UAS
ODU0_PM_ES
ODU2_PM_FEUAS
OTU3_BBE
ODU0_PM_FEBBE
ODU2_PM_SES
OTU3_BBER
ODU0_PM_FEBBER
ODU2_PM_SESR
OTU3_BIAES
ODU0_PM_FEES
ODU2_PM_UAS
OTU3_ES

818
OptiX OSN 8800/6800/3800

ODU0_PM_FESES
ODU2_TCMn_BBE
OTU3_FEBBE
ODU0_PM_FESESR
ODU2_TCMn_BBER
OTU3_FEBBER
ODU0_PM_FEUAS
ODU2_TCMn_BIAES
OTU3_FEES
ODU0_PM_SES
ODU2_TCMn_ES
OTU3_FESES
ODU0_PM_SESR
ODU2_TCMn_FEBBE
OTU3_FESESR
ODU0_PM_UAS
ODU2_TCMn_FEBBER
OTU3_FEUAS
ODU1_PM_BBE
ODU2_TCMn_FEES
OTU3_IAES
ODU1_PM_BBER
ODU2_TCMn_FESES
OTU3_SES
ODU1_PM_ES
ODU2_TCMn_FESESR
OTU3_SESR
ODU1_PM_FEBBE
ODU2_TCMn_FEUAS
OTU3_UAS
ODU1_PM_FEBBER
ODU2_TCMn_IAES
XCSTMPCUR
ODU1_PM_FEES
ODU2_TCMn_SES
XCSTMPMAX
ODU1_PM_FESES
ODU2_TCMn_SESR
XCSTMPMIN
FEC_AFT_COR_ER
ODU1_PM_FESESR
ODU2_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_PM_FEUAS
ODU3_PM_BBE
FEC_AFT_CORER_FLOAT
ODU1_PM_SES
ODU3_PM_BBER
FEC_BEF_COR_ER
ODU1_PM_SESR
ODU3_PM_ES
FEC_BEF_COR_ERAVR
ODU1_PM_UAS
ODU3_PM_FEBBE
FEC_BEF_CORER_FLOAT
ODU1_TCMn_BBE
ODU3_PM_FEBBER
FEC_COR_0BIT_CNT
ODU1_TCMn_BBER
ODU3_PM_FEES
FEC_COR_1BIT_CNT
ODU1_TCMn_BIAES
ODU3_PM_FESES
FEC_COR_BYTE_CNT
ODU1_TCMn_ES
ODU3_PM_FESESR
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FEBBE
ODU3_PM_FEUAS
LSBIASCUR
ODU1_TCMn_FEBBER
ODU3_PM_SES
LSBIASMAX
ODU1_TCMn_FEES
ODU3_PM_SESR
LSBIASMIN
ODU1_TCMn_FESES
ODU3_PM_UAS
LSCLCCUR
ODU1_TCMn_FESESR
ODU3_TCMn_BBE
LSCLCMAX
ODU1_TCMn_FEUAS
ODU3_TCMn_BBER
TN52NS3
Issue 02 (2011-10-31)

819
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU1_TCMn_IAES
ODU3_TCMn_BIAES
LSIOPCUR
ODU1_TCMn_SES
ODU3_TCMn_ES
LSIOPMAX
ODU1_TCMn_SESR
ODU3_TCMn_FEBBE
LSIOPMIN
ODU1_TCMn_UAS
ODU3_TCMn_FEBBER
LSOOPCUR
ODU2_PM_BBE
ODU3_TCMn_FEES
LSOOPMAX
ODU2_PM_BBER
ODU3_TCMn_FESES
LSOOPMIN
ODU2_PM_ES
ODU3_TCMn_FESESR
LSTMPCUR
ODU2_PM_FEBBE
ODU3_TCMn_FEUAS
LSTMPMAX
ODU2_PM_FEBBER
ODU3_TCMn_IAES
LSTMPMIN
ODU2_PM_FEES
ODU3_TCMn_SES
ODU0_PM_BBE
ODU2_PM_FESES
ODU3_TCMn_SESR
ODU0_PM_BBER
ODU2_PM_FESESR
ODU3_TCMn_UAS
ODU0_PM_ES
ODU2_PM_FEUAS
OTU3_BBE
ODU0_PM_FEBBE
ODU2_PM_SES
OTU3_BBER
ODU0_PM_FEBBER
ODU2_PM_SESR
OTU3_BIAES
ODU0_PM_FEES
ODU2_PM_UAS
OTU3_ES
ODU0_PM_FESES
ODU2_TCMn_BBE
OTU3_FEBBE
ODU0_PM_FESESR
ODU2_TCMn_BBER
OTU3_FEBBER
ODU0_PM_FEUAS
ODU2_TCMn_BIAES
OTU3_FEES
ODU0_PM_SES
ODU2_TCMn_ES
OTU3_FESES
ODU0_PM_SESR
ODU2_TCMn_FEBBE
OTU3_FESESR
ODU0_PM_UAS
ODU2_TCMn_FEBBER
OTU3_FEUAS
ODU1_PM_BBE
ODU2_TCMn_FEES
OTU3_IAES
ODU1_PM_BBER
ODU2_TCMn_FESES
OTU3_SES
ODU1_PM_ES
ODU2_TCMn_FESESR
OTU3_SESR
ODU1_PM_FEBBE
ODU2_TCMn_FEUAS
OTU3_UAS
ODU1_PM_FEBBER
ODU2_TCMn_IAES
XCSTMPCUR
ODU1_PM_FEES
ODU2_TCMn_SES
XCSTMPMAX
ODU1_PM_FESES
ODU2_TCMn_SESR
XCSTMPMIN
TN11NS3
Issue 02 (2011-10-31)

820
OptiX OSN 8800/6800/3800

ODU2_PM_ES
ODU3_TCMn_FEBBE
R
FEC_AFT_COR_ERAVR
ODU2_PM_FEBBE
ODU3_TCMn_FEES
FEC_AFT_CORER_FLOAT
ODU2_PM_FEBBER
ODU3_TCMn_FESES
FEC_BEF_COR_ER
ODU2_PM_FEES
ODU3_TCMn_FESES
R
FEC_BEF_COR_ERAVR
ODU2_PM_FESES
ODU3_TCMn_FEUAS
FEC_BEF_CORER_FLOAT
ODU2_PM_FESESR
ODU3_TCMn_IAES
FEC_COR_0BIT_CNT
ODU2_PM_FEUAS
ODU3_TCMn_SES
FEC_COR_1BIT_CNT
ODU2_PM_SES
ODU3_TCMn_SESR
FEC_COR_BYTE_CNT
ODU2_PM_SESR
ODU3_TCMn_UAS
FEC_UNCOR_BLOCK_CNT
ODU2_PM_UAS
OTU3_BBE
LSBIASCUR
ODU3_PM_BBE
OTU3_BBER
LSBIASMAX
ODU3_PM_BBER
OTU3_BIAES
LSBIASMIN
ODU3_PM_ES
OTU3_ES
LSCLCCUR
ODU3_PM_FEBBE
OTU3_FEBBE
LSCLCMAX
ODU3_PM_FEBBER
OTU3_FEBBER
LSCLCMIN
ODU3_PM_FEES
OTU3_FEES
LSIOPCUR
ODU3_PM_FESES
OTU3_FESES
LSIOPMAX
ODU3_PM_FESESR
OTU3_FESESR
LSIOPMIN
ODU3_PM_FEUAS
OTU3_FEUAS
LSOOPCUR
ODU3_PM_SES
OTU3_IAES
LSOOPMAX
ODU3_PM_SESR
OTU3_SES
LSOOPMIN
ODU3_PM_UAS
OTU3_SESR
LSTMPCUR
ODU3_TCMn_BBE
OTU3_UAS
LSTMPMAX
ODU3_TCMn_BBER
XCSTMPCUR
LSTMPMIN
ODU3_TCMn_BIAES
XCSTMPMAX
ODU2_PM_BBE
ODU3_TCMn_ES
XCSTMPMIN
ODU2_PM_BBER
ODU3_TCMn_FEBBE
FEC_AFT_COR_ER
NOTE
TCM6.
Issue 02 (2011-10-31)

821
OptiX OSN 8800/6800/3800

5.2.49 OAU1 Board Performance Event List

BCVCUR
EDTMPMAX
SUMOOPMIN
BCVMAX
EDTMPMIN
WCVCUR
BCVMIN
SUMIOPCUR
WCVMAX
CCVCUR
SUMIOPMAX
WCVMIN
CCVMAX
SUMIOPMIN
XCSTMPCUR
CCVMIN
SUMOOPCUR
XCSTMPMAX
EDTMPCUR
SUMOOPMAX
XCSTMPMIN
5.2.50 OBU1 Board Performance Event List

BCVCUR
EDTMPMAX
SUMOOPMIN
BCVMAX
EDTMPMIN
WCVCUR
BCVMIN
SUMIOPCUR
WCVMAX
CCVCUR
SUMIOPMAX
WCVMIN
CCVMAX
SUMIOPMIN
XCSTMPCUR
CCVMIN
SUMOOPCUR
XCSTMPMAX
EDTMPCUR
SUMOOPMAX
XCSTMPMIN
5.2.51 OBU2 Board Performance Event List
Issue 02 (2011-10-31)
BCVCUR
EDTMPMAX
SUMOOPMIN
BCVMAX
EDTMPMIN
WCVCUR
BCVMIN
SUMIOPCUR
WCVMAX
CCVCUR
SUMIOPMAX
WCVMIN
CCVMAX
SUMIOPMIN
XCSTMPCUR
CCVMIN
SUMOOPCUR
XCSTMPMAX
EDTMPCUR
SUMOOPMAX
XCSTMPMIN

822
OptiX OSN 8800/6800/3800

5.2.52 OLP Board Performance Event List

LSIOPCUR
SUMIOPCUR
XCSTMPCUR
LSIOPMAX
SUMIOPMAX
XCSTMPMAX
LSIOPMIN
SUMIOPMIN
XCSTMPMIN
5.2.53 OPM8 Board Performance Event List

PCLSOPCUR
PCLSWLCUR
XCSTMPCUR
PCLSOPMAX
PCLSWLMAX
XCSTMPMAX
PCLSOPMIN
PCLSWLMIN
XCSTMPMIN
5.2.54 PTQX Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU1_PM_UAS
ODU2_TCMn_FEES
FEC_AFT_COR_ER
ODU1_TCMn_BBE
ODU2_TCMn_FESES
FEC_AFT_COR_ERAVR
ODU1_TCMn_BBER
ODU2_TCMn_FESESR
FEC_BEF_CORER_FLOAT
ODU1_TCMn_BIAES
ODU2_TCMn_FEUAS
FEC_BEF_COR_ER
ODU1_TCMn_ES
ODU2_TCMn_IAES
FEC_BEF_COR_ERAVR
ODU1_TCMn_FEBBE
ODU2_TCMn_SES
FEC_COR_0BIT_CNT
ODU1_TCMn_FEBBER
ODU2_TCMn_SESR
FEC_COR_1BIT_CNT
ODU1_TCMn_FEES
ODU2_TCMn_UAS
FEC_COR_BYTE_CNT
ODU1_TCMn_FESES
OTU2_BBE
FEC_UNCOR_BLOCK_CN
T
ODU1_TCMn_FESESR
OTU2_BBER
LSBIASCUR
ODU1_TCMn_FEUAS
OTU2_BIAES
LSBIASMAX
ODU1_TCMn_IAES
OTU2_ES
LSBIASMIN
ODU1_TCMn_SES
OTU2_FEBBE
LSIOPCUR
ODU1_TCMn_SESR
OTU2_FEBBER
LSIOPMAX
ODU1_TCMn_UAS
OTU2_FEES
LSIOPMIN
ODU2_PM_BBE
OTU2_FESES
LSOOPCUR
ODU2_PM_BBER
OTU2_FESESR

823
OptiX OSN 8800/6800/3800

LSOOPMAX
ODU2_PM_ES
OTU2_FEUAS
LSOOPMIN
ODU2_PM_FEBBE
OTU2_IAES
LSTMPCUR
ODU2_PM_FEBBER
OTU2_SES
LSTMPMAX
ODU2_PM_FEES
OTU2_SESR
LSTMPMIN
ODU2_PM_FESES
OTU2_UAS
ODU1_PM_BBE
ODU2_PM_FESESR
RSBBE
ODU1_PM_BBER
ODU2_PM_FEUAS
RSCSES
ODU1_PM_ES
ODU2_PM_SES
RSES
ODU1_PM_FEBBE
ODU2_PM_SESR
RSOFS
ODU1_PM_FEBBER
ODU2_PM_UAS
RSSES
ODU1_PM_FEES
ODU2_TCMn_BBE
RSUAS
ODU1_PM_FESES
ODU2_TCMn_BBER
XCSTMPCUR
ODU1_PM_FESESR
ODU2_TCMn_BIAES
XCSTMPMAX
ODU1_PM_FEUAS
ODU2_TCMn_ES
XCSTMPMIN
ODU1_PM_SES
ODU2_TCMn_FEBBE
ODU1_PM_SESR
ODU2_TCMn_FEBBER
NOTE
TCM6.
NOTE

Octets Received
Issue 02 (2011-10-31)

Octets in Length)
Packets Received

Octets in Length)
Broadcast Packets
Received

Octets in Length)
Multicast Packets
Received

Octets in Length)
Undersize Packets
Received

Octets in Length)

824
OptiX OSN 8800/6800/3800

Oversize Packets
Received

Octets in Length)
Fragments

Octets in Length)
Alignment Errors
Jabbers

Octets in Length)
FCS Errors

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Received
(65~127 Octets in
Length)
Packets Transmitted
Octets Transmitted
5.2.55 RDU9 Board Performance Event List

SUMIOPCUR
SUMIOPMIN
XCSTMPMAX
SUMIOPMAX
XCSTMPCUR
XCSTMPMIN
5.2.56 RMU9 Board Performance Event List

ICTMPCUR
SUMIOPMAX
SUMOOPMIN
ICTMPMAX
SUMIOPMIN
XCSTMPCUR
ICTMPMIN
SUMOOPCUR
XCSTMPMAX
SUMIOPCUR
SUMOOPMAX
XCSTMPMIN
5.2.57 ROAM Board Performance Event List
Issue 02 (2011-10-31)
ICTMPCUR
LSOOPMIN
SUMOOPMAX
ICTMPMAX
SUMIOPCUR
SUMOOPMIN
ICTMPMIN
SUMIOPMAX
XCSTMPCUR
LSOOPCUR
SUMIOPMIN
XCSTMPMAX
LSOOPMAX
SUMOOPCUR
XCSTMPMIN

825
OptiX OSN 8800/6800/3800

5.2.58 SCC Board Performance Event List

TN16SCC
AVGFREQDEV
MAXMEANPATHDELAY
MINPHASEOFFSET
AVGMEANPATHDELA
Y
MAXPHASEOFFSET
XCSTMPCUR
AVGPHASEOFFSET
MINFREQDEV
XCSTMPMAX
MAXFREQDEV
MINMEANPATHDELAY
XCSTMPMIN
5.2.59 SC1 Board Performance Event List

CRC4BBE
CRC4UAS
LSOOPCUR
CRC4FEBBE
LSBIASCUR
LSOOPMAX
CRC4ES
LSBIASMAX
LSOOPMIN
CRC4FEES
LSBIASMIN
XCSTMPCUR
CRC4FESES
LSIOPCUR
XCSTMPMAX
CRC4FEUAS
LSIOPMAX
XCSTMPMIN
CRC4SES
LSIOPMIN
5.2.60 SC2 Board Performance Event List

CRC4BBE
CRC4UAS
LSOOPCUR
CRC4FEBBE
LSBIASCUR
LSOOPMAX
CRC4ES
LSBIASMAX
LSOOPMIN
CRC4FEES
LSBIASMIN
XCSTMPCUR
CRC4FESES
LSIOPCUR
XCSTMPMAX
CRC4FEUAS
LSIOPMAX
XCSTMPMIN
CRC4SES
LSIOPMIN
5.2.61 SFD64 Board Performance Event List

AUPJCHIGH
Issue 02 (2011-10-31)
HPFEUAS

OTU2SMBIP8
826
OptiX OSN 8800/6800/3800

AUPJCLOW
HPSES
RPLCUR
AUPJCNEW
HPUAS
RPLMAX
FEC_AFT_COR_ER
MSBBE
RPLMIN
FEC_AFT_COR_ERAVR
MSES
RSBBE
FEC_AFT_CORER_FLOAT
MSCSES
RSCSES
FEC_BEF_COR_ER
MSFEBBE
RSES
FEC_BEF_COR_ERAVR
MSFEES
RSOFS
FEC_BEF_CORER_FLOAT
MSFECSES
RSOOF
FEC_COR_0BIT_CNT
MSFESES
RSSES
FEC_COR_1BIT_CNT
MSFEUAS
RSUAS
FEC_COR_BYTE_CNT
MSSES
TLBCUR
FEC_UNCOR_BLOCK_CN
T
MSUAS
TLBMAX
HPBBE
ODU2PMBIP8
TLBMIN
HPES
OSPICCVCUR
TPLCUR
HPCSES
OSPICCVMAX
TPLMAX
HPFEBBE
OSPICCVMIN
TPLMIN
HPFEES
OSPITMPCUR
XCSTMPCUR
HPFECSES
OSPITMPMAX
XCSTMPMAX
HPFESES
OSPITMPMIN
XCSTMPMIN
NOTE
5.2.62 SF64 Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
HPSES
RPLMAX
AUPJCLOW
HPUAS
RPLMIN
AUPJCNEW
MSBBE
RSBBE
FEC_AFT_COR_ER
MSES
RSES
FEC_AFT_COR_ERAVR
MSCSES
RSOFS
FEC_AFT_CORER_FLOAT
MSFEBBE
RSOOF
FEC_BEF_COR_ER
MSFEES
RSSES

827
OptiX OSN 8800/6800/3800

FEC_BEF_COR_ERAVR
MSFESES
RSCSES
FEC_BEF_CORER_FLOAT
MSFECSES
RSUAS
FEC_COR_0BIT_CNT
MSFEUAS
TCBBE
FEC_COR_1BIT_CNT
MSSES
TCFEBBE
FEC_COR_BYTE_CNT
MSUAS
TCOBBE
FEC_UNCOR_BLOCK_CN
T
ODU2PMBIP8
TLBCUR
HPBBE
OSPICCVCUR
TLBMAX
HPES
OSPICCVMAX
TLBMIN
HPCSES
OSPICCVMIN
TPLCUR
HPFEBBE
OSPITMPCUR
TPLMAX
HPFEES
OSPITMPMAX
TPLMIN
HPFESES
OSPITMPMIN
XCSTMPCUR
HPFECSES
OTU2SMBIP8
XCSTMPMAX
HPFEUAS
RPLCUR
XCSTMPMIN
NOTE
5.2.63 SF64A Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
MSBBE
RSBBE
AUPJCLOW
MSES
RSES
AUPJCNEW
MSCSES
RSCSES
FEC_AFT_COR_ER
MSFEBBE
RSOFS
FEC_AFT_COR_ERAVR
MSFEES
RSOOF
FEC_BEF_COR_ER
MSFECSES
RSSES
FEC_BEF_COR_ERAVR
MSFESES
RSUAS
FEC_COR_0BIT_CNT
MSFEUAS
TCBBE
FEC_COR_1BIT_CNT
MSSES
TCFEBBE
FEC_COR_BYTE_CNT
MSUAS
TCOBBE
FEC_UNCOR_BLOCK_CN
T
ODU2PMBIP8
TLBCUR

828
OptiX OSN 8800/6800/3800

HPBBE
OSPICCVCUR
TLBMAX
HPES
OSPICCVMAX
TLBMIN
HPFEBBE
OSPICCVMIN
TPLCUR
HPFEES
OSPITMPCUR
TPLMAX
HPFESES
OSPITMPMAX
TPLMIN
HPFECSES
OSPITMPMIN
XCSTMPCUR
HPFEUAS
OTU2SMBIP8
XCSTMPMAX
HPCSES
RPLCUR
XCSTMPMIN
HPSES
RPLMAX
HPUAS
RPLMIN
NOTE
5.2.64 SL64 Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS
HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR
HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN

829
OptiX OSN 8800/6800/3800

5.2.65 SLD64 Board Performance Event List

AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS
HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR
HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN
5.2.66 SLH41 Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS
HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR

830
OptiX OSN 8800/6800/3800

HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN
5.2.67 SLO16 Board Performance Event List

AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS
HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR
HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN
5.2.68 SLQ16 Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS

831
OptiX OSN 8800/6800/3800

HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR
HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN
5.2.69 SLQ64 Board Performance Event List
Issue 02 (2011-10-31)
AUPJCHIGH
MSFEBBE
RSBBE
AUPJCLOW
MSFEES
RSCSES
AUPJCNEW
MSFECSES
RSES
HPBBE
MSFESES
RSOFS
HPES
MSFEUAS
RSOOF
HPCSES
MSSES
RSSES
HPFEBBE
MSUAS
RSUAS
HPFEES
OSPICCVCUR
TLBCUR
HPFECSES
OSPICCVMAX
TLBMAX
HPFESES
OSPICCVMIN
TLBMIN
HPFEUAS
OSPITMPCUR
TPLCUR
HPSES
OSPITMPMAX
TPLMAX
HPUAS
OSPITMPMIN
TPLMIN
MSBBE
RPLCUR
XCSTMPCUR
MSCSES
RPLMAX
XCSTMPMAX
MSES
RPLMIN
XCSTMPMIN

832
OptiX OSN 8800/6800/3800

5.2.70 ST2 Board Performance Event List

FEC_AFT_COR_ER
LSIOPMIN
OSC_FEES
FEC_AFT_COR_ERAVR
LSOOPCUR
OSC_FESES
FEC_BEF_COR_ER
LSOOPMAX
OSC_FESESR
FEC_BEF_COR_ERAVR
LSOOPMIN
OSC_FEUAS
FEC_COR_0BIT_CNT
LSTMPCUR
OSC_IAES
FEC_COR_1BIT_CNT
LSTMPMAX
OSC_SES
FEC_COR_BYTE_CNT
LSTMPMIN
OSC_SESR
FEC_UNCOR_BLOCK_CN
T
OSC_BBE
OSC_UAS
LSBIASCUR
OSC_BBER
XCSTMPCUR
LSBIASMAX
OSC_BIAES
XCSTMPMAX
LSBIASMIN
OSC_ES
XCSTMPMIN
LSIOPCUR
OSC_FEBBE
LSIOPMAX
OSC_FEBBER
NOTE
5.2.71 STG Board Performance Event List

XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
5.2.72 SXM Board Performance Event List

XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
5.2.73 SXH Board Performance Event List

XCSTMPCUR
Issue 02 (2011-10-31)
XCSTMPMAX

XCSTMPMIN
833
OptiX OSN 8800/6800/3800

5.2.74 TBE Board Performance Event List

LSBIASCUR
LSOOPMAX
RSES
LSBIASMAX
LSOOPMIN
RSOFS
LSBIASMIN
LSTMPCUR
RSSES
LSIOPCUR
LSTMPMAX
RSUAS
LSIOPMAX
LSTMPMIN
XCSTMPCUR
LSIOPMIN
RSBBE
XCSTMPMAX
LSOOPCUR
RSCSES
XCSTMPMIN
Drop Events
Octets Received
Packets Received
Undersize Packets
Received
Fragments
Jabbers
Packets Received (64 Octets in

Length)

Octets in Length)
Packets Received
(128~255 Octets in
Length)

Octets in Length)

Octets in Length)
Packets Received
Length)
Packets Transmitted (64 Octets

in Length)

Octets in Length)
Packets Transmitted
(128~255 Octets in
Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Length)

Transmitted (64 Octets in
Length)

in Length)

Octets in Length)

in Length)

Octets in Length)

Octets in Length)
Multicast Packets
Transmitted
Issue 02 (2011-10-31)

834
OptiX OSN 8800/6800/3800

FCS Errors
Control Frames
Transmitted
Packets Transmitted
Octets Transmitted
5.2.75 TDC Board Performance Event List

LSIOPCUR
LSOOPCUR
XCSTMPCUR
LSIOPMAX
LSOOPMAX
XCSTMPMAX
LSIOPMIN
LSOOPMIN
XCSTMPMIN
5.2.76 TDG Board Performance Event List

LSBIASCUR
LSTMPCUR
ODU1_PM_FESES
LSBIASMAX
LSTMPMAX
ODU1_PM_FESESR
LSBIASMIN
LSTMPMIN
ODU1_PM_FEUAS
LSIOPCUR
ODU1_PM_BBE
ODU1_PM_SES
LSIOPMAX
ODU1_PM_BBER
ODU1_PM_SESR
LSIOPMIN
ODU1_PM_ES
ODU1_PM_UAS
LSOOPCUR
ODU1_PM_FEBBE
XCSTMPCUR
LSOOPMAX
ODU1_PM_FEBBER
XCSTMPMAX
LSOOPMIN
ODU1_PM_FEES
XCSTMPMIN
Issue 02 (2011-10-31)
Drop Events
Fragments
Jabbers

in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
Packets Received
Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

835
OptiX OSN 8800/6800/3800

Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
(1519~MTU Octets in
Length)
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
FCS Errors
5.2.77 TDX Board Performance Event List

TN53TDX
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU2_PM_FEBBER
ODUFLEX_PM_FESESR
FEC_AFT_COR_ER
ODU2_PM_FEES
ODUFLEX_PM_FEUAS
FEC_AFT_COR_ERAV
R
ODU2_PM_FESES
ODUFLEX_PM_SES
FEC_BEF_CORER_FLO
AT
ODU2_PM_FESESR
ODUFLEX_PM_SESR
FEC_BEF_COR_ER
ODU2_PM_FEUAS
ODUFLEX_PM_UAS
FEC_BEF_COR_ERAV
R
ODU2_PM_SES
OTU2_BBE
FEC_COR_0BIT_CNT
ODU2_PM_SESR
OTU2_BBER
FEC_COR_1BIT_CNT
ODU2_PM_UAS
OTU2_BIAES
FEC_COR_BYTE_CNT
ODU2_TCMn_BBE
OTU2_ES
FEC_UNCOR_BLOCK_
CNT
ODU2_TCMn_BBER
OTU2_FEBBE
LSBIASCUR
ODU2_TCMn_BIAES
OTU2_FEBBER
LSBIASMAX
ODU2_TCMn_ES
OTU2_FEES
LSBIASMIN
ODU2_TCMn_FEBBE
OTU2_FESES
LSCLCCUR
ODU2_TCMn_FEBBER
OTU2_FESESR
LSCLCMAX
ODU2_TCMn_FEES
OTU2_FEUAS

836
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU2_TCMn_FESES
OTU2_IAES
LSIOPCUR
ODU2_TCMn_FESESR
OTU2_SES
LSIOPMAX
ODU2_TCMn_FEUAS
OTU2_SESR
LSIOPMIN
ODU2_TCMn_IAES
OTU2_UAS
LSOOPCUR
ODU2_TCMn_SES
RSBBE
LSOOPMAX
ODU2_TCMn_SESR
RSCSES
LSOOPMIN
ODU2_TCMn_UAS
RSES
LSTMPCUR
ODUFLEX_PM_BBE
RSSES
LSTMPMAX
ODUFLEX_PM_BBER
RSUAS
LSTMPMIN
ODUFLEX_PM_ES
XCSTMPCUR
ODU2_PM_BBE
ODUFLEX_PM_FEBBE
XCSTMPMAX
ODU2_PM_BBER
ODUFLEX_PM_FEBBER
XCSTMPMIN
ODU2_PM_ES
ODUFLEX_PM_FEES
ODU2_PM_FEBBE
ODUFLEX_PM_FESES
TN52TDX
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU2_PM_ES
OTU2_BBE
FEC_AFT_COR_ERAV
R
ODU2_PM_FEBBE
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBER
OTU2_BIAES
FEC_BEF_COR_ERAV
R
ODU2_PM_FEES
OTU2_ES
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBE
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEBBER
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FEES
FEC_UNCOR_BLOCK_
CNT
ODU2_PM_SES
OTU2_FESES
FEC_BEF_CORER_FL
OAT
ODU2_PM_SESR
OTU2_FESESR
FEC_AFT_CORER_FL
OAT
ODU2_PM_UAS
OTU2_FEUAS
LSBIASCUR
ODU2_TCMn_BBE
OTU2_IAES
LSBIASMAX
ODU2_TCMn_BBER
OTU2_SES

837
OptiX OSN 8800/6800/3800

LSBIASMIN
ODU2_TCMn_BIAES
OTU2_SESR
LSIOPCUR
ODU2_TCMn_ES
OTU2_UAS
LSIOPMAX
ODU2_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU2_TCMn_FEBBER
RSES
LSOOPCUR
ODU2_TCMn_FEES
RSCSES
LSOOPMAX
ODU2_TCMn_FESES
RSSES
LSOOPMIN
ODU2_TCMn_FESESR
RSUAS
LSTMPCUR
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU2_TCMn_SES
XCSTMPMIN
ODU2_PM_BBE
ODU2_TCMn_SESR
SEFS_S
ODU2_PM_BBER
ODU2_TCMn_UAS
RSOFS
TN11TDX
LSBIASCUR
LSTMPCUR
ODU1_PM_SES
LSBIASMAX
LSTMPMAX
ODU1_PM_SESR
LSBIASMIN
LSTMPMIN
ODU1_PM_UAS
LSCLCCUR
ODU1_PM_BBE
RSBBE
LSCLCMAX
ODU1_PM_BBER
RSCSES
LSCLCMIN
ODU1_PM_ES
RSES
LSIOPCUR
ODU1_PM_FEBBE
RSOFS
LSIOPMAX
ODU1_PM_FEBBER
RSSES
LSIOPMIN
ODU1_PM_FEES
RSUAS
LSOOPCUR
ODU1_PM_FESES
XCSTMPCUR
LSOOPMAX
ODU1_PM_FESESR
XCSTMPMAX
LSOOPMIN
ODU1_PM_FEUAS
XCSTMPMIN
LSBIASCUR
LSTMPCUR
ODU2_PM_SES
LSBIASMAX
LSTMPMAX
ODU2_PM_SESR
TN12TDX
Issue 02 (2011-10-31)

838
OptiX OSN 8800/6800/3800

LSBIASMIN
LSTMPMIN
ODU2_PM_UAS
LSCLCCUR
ODU2_PM_BBE
RSBBE
LSCLCMAX
ODU2_PM_BBER
RSCSES
LSCLCMIN
ODU2_PM_ES
RSES
LSIOPCUR
ODU2_PM_FEBBE
RSSES
LSIOPMAX
ODU2_PM_FEBBER
RSUAS
LSIOPMIN
ODU2_PM_FEES
XCSTMPCUR
LSOOPCUR
ODU2_PM_FESES
XCSTMPMAX
LSOOPMAX
ODU2_PM_FESESR
XCSTMPMIN
LSOOPMIN
ODU2_PM_FEUAS
SEFS_S
RSOFS
NOTE

TN53TDX
Octets Transmitted
Packets Transmitted
(128~255 Octets in
Length)
Bad Octets Received
Oversize Packets
Received
Packets Transmitted
(1519~MTU Octets in
Length)
Oversize Packets
Transmitted
Packets Transmitted
(256~511 Octets in
Length)
Packets Received
Packets Transmitted
(512~1023 Octets in
Length)
Packets Received
Length)

Octets in Length)
Packets Received
(128~255 Octets in
Length)
Packets Transmitted
Control Frames Transmitted
Packets Received
(1519~MTU Octets in
Length)
Alignment Errors
Issue 02 (2011-10-31)

839
OptiX OSN 8800/6800/3800

FCS Errors
Packets Received
(256~511 Octets in
Length)
Fragments
Packets Received
(512~1023 Octets in
Length)
Undersize Packets
Received
Jabbers

Octets in Length)

Octets in Length)
Unicast Packets
Transmitted
Packets Transmitted
Octets Received
Packets Transmitted
Length)
TN52TDX
Issue 02 (2011-10-31)
Octets in Length)
Alignment Errors
Octets Transmitted
Bad Octets
Received
Packets Transmitted
(1519~MTUOctets in Length)
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Packets Received
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Control Frames
Received
Octets in Length)
Octets in Length)
Control Frames
Transmitted
Packets Received(1519~MTU
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Jabbers

Length)
Multicast Packets
Received

in Length)

840
OptiX OSN 8800/6800/3800

Multicast Packets
Transmitted
Packets Transmitted
Octets Received
Octets in Length)
TN11TDX
Fragments
Jabbers

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

Octets in Length)
Packets Transmitted
Packets Transmitted
Packets Transmitted
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Unicast Packets
Transmitted
Multicast Packets
Transmitted
Broadcast Packets
Transmitted
Bad Octets Received
FCS Errors
Control Frames Transmitted
Oversize Packets
Transmitted
TN12TDX
Issue 02 (2011-10-31)
Octets Received
Packets Received

FCS Errors
841
OptiX OSN 8800/6800/3800

5.2.78 THA Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_PM_SESR
ODUFLEX_PM_FEBBER
FEC_AFT_COR_ER
ODU0_PM_UAS
ODUFLEX_PM_FEES
FEC_AFT_COR_ERAV
R
ODU1_PM_BBE
ODUFLEX_PM_FESES
FEC_BEF_CORER_FLO
AT
ODU1_PM_BBER
ODUFLEX_PM_FESESR
FEC_BEF_COR_ER
ODU1_PM_ES
ODUFLEX_PM_FEUAS
FEC_BEF_COR_ERAV
R
ODU1_PM_FEBBE
ODUFLEX_PM_SES
FEC_COR_0BIT_CNT
ODU1_PM_FEBBER
ODUFLEX_PM_SESR
FEC_COR_1BIT_CNT
ODU1_PM_FEES
ODUFLEX_PM_UAS
FEC_COR_BYTE_CNT
ODU1_PM_FESES
OTU1_BBE
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_FESESR
OTU1_BBER
LSBIASCUR
ODU1_PM_FEUAS
OTU1_BIAES
LSBIASMAX
ODU1_PM_SES
OTU1_ES
LSBIASMIN
ODU1_PM_SESR
OTU1_FEBBE
LSIOPCUR
ODU1_PM_UAS
OTU1_FEBBER
LSIOPMAX
ODU1_TCMn_BBE
OTU1_FEES
LSIOPMIN
ODU1_TCMn_BBER
OTU1_FESES
LSOOPCUR
ODU1_TCMn_BIAES
OTU1_FESESR
LSOOPMAX
ODU1_TCMn_ES
OTU1_FEUAS
LSOOPMIN
ODU1_TCMn_FEBBE
OTU1_IAES
LSTMPCUR
ODU1_TCMn_FEBBER
OTU1_SES
LSTMPMAX
ODU1_TCMn_FEES
OTU1_SESR
LSTMPMIN
ODU1_TCMn_FESES
OTU1_UAS
ODU0_PM_BBE
ODU1_TCMn_FESESR
RSBBE
ODU0_PM_BBER
ODU1_TCMn_FEUAS
RSCSES
ODU0_PM_ES
ODU1_TCMn_IAES
RSES
ODU0_PM_FEBBE
ODU1_TCMn_SES
RSSES
ODU0_PM_FEBBER
ODU1_TCMn_SESR
RSUAS

842
OptiX OSN 8800/6800/3800

ODU0_PM_FEES
ODU1_TCMn_UAS
XCSTMPCUR
ODU0_PM_FESES
ODUFLEX_PM_BBE
XCSTMPMAX
ODU0_PM_FESESR
ODUFLEX_PM_BBER
XCSTMPMIN
ODU0_PM_FEUAS
ODUFLEX_PM_ES
ODU0_PM_SES
ODUFLEX_PM_FEBBE
NOTE
TCM6.

Bad Octets
Received
Issue 02 (2011-10-31)
Packets Transmitted
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Drop Events
Octets in Length)
Octets in Length)
Drop Events at
Transmission
Direction
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Good Octets
Received

Length)
Good Octets
Transmitted

in Length)
Jabbers
Octets in Length)
Multicast Packets
Received
Octets in Length)

843
OptiX OSN 8800/6800/3800

5.2.79 TMX Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_TCMn_BBER
ODU2_TCMn_UAS
FEC_AFT_COR_ERAVR
ODU1_TCMn_BIAES
OTU1_BBE
FEC_AFT_CORER_FLOAT
ODU1_TCMn_ES
OTU1_BBER
FEC_BEF_COR_ER
ODU1_TCMn_FEBBE
OTU1_BIAES
FEC_BEF_COR_ERAVR
ODU1_TCMn_FEBBER
OTU1_ES
FEC_BEF_CORER_FLOAT
ODU1_TCMn_FEES
OTU1_FEBBE
FEC_COR_0BIT_CNT
ODU1_TCMn_FESES
OTU1_FEBBER
FEC_COR_1BIT_CNT
ODU1_TCMn_FESESR
OTU1_FEES
FEC_COR_BYTE_CNT
ODU1_TCMn_FEUAS
OTU1_FESES
FEC_UNCOR_BLOCK_CNT
ODU1_TCMn_IAES
OTU1_FESESR
LSBIASCUR
ODU1_TCMn_SES
OTU1_FEUAS
LSBIASMAX
ODU1_TCMn_SESR
OTU1_IAES
LSBIASMIN
ODU1_TCMn_UAS
OTU1_SES
LSCLCCUR
ODU2_PM_BBE
OTU1_SESR
LSCLCMAX
ODU2_PM_BBER
OTU1_UAS
LSCLCMIN
ODU2_PM_ES
OTU2_BBE
LSIOPCUR
ODU2_PM_FEBBE
OTU2_BBER
LSIOPMAX
ODU2_PM_FEBBER
OTU2_BIAES
LSIOPMIN
ODU2_PM_FEES
OTU2_ES
LSOOPCUR
ODU2_PM_FESES
OTU2_FEBBE
LSOOPMAX
ODU2_PM_FESESR
OTU2_FEBBER
LSOOPMIN
ODU2_PM_FEUAS
OTU2_FEES
LSTMPCUR
ODU2_PM_SES
OTU2_FESES
LSTMPMAX
ODU2_PM_SESR
OTU2_FESESR
LSTMPMIN
ODU2_PM_UAS
OTU2_FEUAS
ODU1_PM_BBE
ODU2_TCMn_BBE
OTU2_IAES
ODU1_PM_BBER
ODU2_TCMn_BBER
OTU2_SES
ODU1_PM_ES
ODU2_TCMn_BIAES
OTU2_SESR
ODU1_PM_FEBBE
ODU2_TCMn_ES
OTU2_UAS
ODU1_PM_FEBBER
ODU2_TCMn_FEBBE
RSBBE

844
OptiX OSN 8800/6800/3800

ODU1_PM_FEES
ODU2_TCMn_FEBBER
RSCSES
ODU1_PM_FESES
ODU2_TCMn_FEES
RSES
ODU1_PM_FESESR
ODU2_TCMn_FESES
RSOFS
ODU1_PM_FEUAS
ODU2_TCMn_FESESR
RSSES
ODU1_PM_SES
ODU2_TCMn_FEUAS
RSUAS
ODU1_PM_SESR
ODU2_TCMn_IAES
XCSTMPCUR
ODU1_PM_UAS
ODU2_TCMn_SES
XCSTMPMAX
ODU1_TCMn_BBE
ODU2_TCMn_SESR
XCSTMPMIN
NOTE
TCM6.
NOTE
5.2.80 TOA Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU0_PM_SESR
ODUFLEX_PM_FEBBER
FEC_AFT_COR_ER
ODU0_PM_UAS
ODUFLEX_PM_FEES
FEC_AFT_COR_ERAV
R
ODU1_PM_BBE
ODUFLEX_PM_FESES
FEC_BEF_CORER_FLO
AT
ODU1_PM_BBER
ODUFLEX_PM_FESESR
FEC_BEF_COR_ER
ODU1_PM_ES
ODUFLEX_PM_FEUAS
FEC_BEF_COR_ERAV
R
ODU1_PM_FEBBE
ODUFLEX_PM_SES
FEC_COR_0BIT_CNT
ODU1_PM_FEBBER
ODUFLEX_PM_SESR
FEC_COR_1BIT_CNT
ODU1_PM_FEES
ODUFLEX_PM_UAS
FEC_COR_BYTE_CNT
ODU1_PM_FESES
OTU1_BBE
FEC_UNCOR_BLOCK_
CNT
ODU1_PM_FESESR
OTU1_BBER
LSBIASCUR
ODU1_PM_FEUAS
OTU1_BIAES
LSBIASMAX
ODU1_PM_SES
OTU1_ES
LSBIASMIN
ODU1_PM_SESR
OTU1_FEBBE

845
OptiX OSN 8800/6800/3800

LSIOPCUR
ODU1_PM_UAS
OTU1_FEBBER
LSIOPMAX
ODU1_TCMn_BBE
OTU1_FEES
LSIOPMIN
ODU1_TCMn_BBER
OTU1_FESES
LSOOPCUR
ODU1_TCMn_BIAES
OTU1_FESESR
LSOOPMAX
ODU1_TCMn_ES
OTU1_FEUAS
LSOOPMIN
ODU1_TCMn_FEBBE
OTU1_IAES
LSTMPCUR
ODU1_TCMn_FEBBER
OTU1_SES
LSTMPMAX
ODU1_TCMn_FEES
OTU1_SESR
LSTMPMIN
ODU1_TCMn_FESES
OTU1_UAS
ODU0_PM_BBE
ODU1_TCMn_FESESR
RSBBE
ODU0_PM_BBER
ODU1_TCMn_FEUAS
RSCSES
ODU0_PM_ES
ODU1_TCMn_IAES
RSES
ODU0_PM_FEBBE
ODU1_TCMn_SES
RSSES
ODU0_PM_FEBBER
ODU1_TCMn_SESR
RSUAS
ODU0_PM_FEES
ODU1_TCMn_UAS
XCSTMPCUR
ODU0_PM_FESES
ODUFLEX_PM_BBE
XCSTMPMAX
ODU0_PM_FESESR
ODUFLEX_PM_BBER
XCSTMPMIN
ODU0_PM_FEUAS
ODUFLEX_PM_ES
ODU0_PM_SES
ODUFLEX_PM_FEBBE
NOTE
TCM6.

Bad Octets
Received
Issue 02 (2011-10-31)
Packets Transmitted
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)

846
OptiX OSN 8800/6800/3800

Drop Events
Octets in Length)
Octets in Length)
Drop Events at
Transmission
Direction
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Good Octets
Received

Length)
Good Octets
Transmitted

in Length)
Jabbers
Octets in Length)
Multicast Packets
Received
Octets in Length)
5.2.81 TOG Board Performance Event List

LSBIASCUR
ODU0_PM_BBER
ODU1_PM_ES
LSBIASMAX
ODU0_PM_ES
ODU1_PM_FEBBE
LSBIASMIN
ODU0_PM_FEBBE
ODU1_PM_FEBBER
LSIOPCUR
ODU0_PM_FEBBER
ODU1_PM_FEES
LSIOPMAX
ODU0_PM_FEES
ODU1_PM_FESES
LSIOPMIN
ODU0_PM_FESES
ODU1_PM_FESESR
LSOOPCUR
ODU0_PM_FESESR
ODU1_PM_FEUAS
LSOOPMAX
ODU0_PM_FEUAS
ODU1_PM_SES
LSOOPMIN
ODU0_PM_SES
ODU1_PM_SESR
LSTMPCUR
ODU0_PM_SESR
ODU1_PM_UAS
LSTMPMAX
ODU0_PM_UAS
XCSTMPCUR
LSTMPMIN
ODU1_PM_BBE
XCSTMPMAX
ODU0_PM_BBE
ODU1_PM_BBER
XCSTMPMIN

Issue 02 (2011-10-31)

847
OptiX OSN 8800/6800/3800

Bad Octets Received

Octets in Length)

Length)
FCS Errors
Octets in Length)

in Length)
Fragments
Octets in Length)
Octets in Length)
Jabbers
Octets in Length)
Broadcast Packets
Received
Drop Events
5.2.82 TOM Board Performance Event List

TN52TOM
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU0_PM_FESES
ODU1_TCMn_IAES
FEC_AFT_COR_ERAVR
ODU0_PM_FESESR
ODU1_TCMn_SES
FEC_AFT_CORER_FLOAT
ODU0_PM_FEUAS
ODU1_TCMn_SESR
FEC_BEF_COR_ER
ODU0_PM_SES
ODU1_TCMn_UAS
FEC_BEF_COR_ERAVR
ODU0_PM_SESR
OTU1_IAES
FEC_BEF_CORER_FLOAT
ODU0_PM_UAS
OTU1_BIAES
FEC_COR_0BIT_CNT
ODU1_PM_BBE
OTU1_BBE
FEC_COR_1BIT_CNT
ODU1_PM_BBER
OTU1_ES
FEC_COR_BYTE_CNT
ODU1_PM_ES
OTU1_SES
FEC_UNCOR_BLOCK_CN
T
ODU1_PM_FEBBE
OTU1_UAS
LSBIASCUR
ODU1_PM_FEBBER
OTU1_SESR
LSBIASMAX
ODU1_PM_FEES
OTU1_BBER
LSBIASMIN
ODU1_PM_FESES
OTU1_FEBBE
LSIOPCUR
ODU1_PM_FESESR
OTU1_FEES
LSIOPMAX
ODU1_PM_FEUAS
OTU1_FESES
LSIOPMIN
ODU1_PM_SES
OTU1_FEUAS

848
OptiX OSN 8800/6800/3800

LSOOPCUR
ODU1_PM_SESR
OTU1_FESESR
LSOOPMAX
ODU1_PM_UAS
OTU1_FEBBER
LSOOPMIN
ODU1_TCMn_BBE
RSBBE
LSTMPCUR
ODU1_TCMn_BBER
RSES
LSTMPMAX
ODU1_TCMn_BIAES
RSOFS
LSTMPMIN
ODU1_TCMn_ES
RSCSES
ODU0_PM_BBE
ODU1_TCMn_FEBBE
RSSES
ODU0_PM_BBER
ODU1_TCMn_FEBBER
RSUAS
ODU0_PM_ES
ODU1_TCMn_FEES
XCSTMPCUR
ODU0_PM_FEBBE
ODU1_TCMn_FESES
XCSTMPMAX
ODU0_PM_FEBBER
ODU1_TCMn_FESESR
XCSTMPMIN
ODU0_PM_FEES
ODU1_TCMn_FEUAS
TN11TOM
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_FEBBER
OTU1_BBE
FEC_BEF_COR_ER
ODU1_PM_FEES
OTU1_BBER
FEC_COR_0BIT_CNT
ODU1_PM_FESES
OTU1_BIAES
FEC_COR_1BIT_CNT
ODU1_PM_FESESR
OTU1_ES
FEC_COR_BYTE_CNT
ODU1_PM_FEUAS
OTU1_FEBBE
FEC_UNCOR_BLOCK_CNT
ODU1_PM_SES
OTU1_FEBBER
LSBIASCUR
ODU1_PM_SESR
OTU1_FEES
LSBIASMAX
ODU1_PM_UAS
OTU1_FESES
LSBIASMIN
ODU1_TCMn_BBE
OTU1_FESESR
LSIOPCUR
ODU1_TCMn_BBER
OTU1_FEUAS
LSIOPMAX
ODU1_TCMn_BIAES
OTU1_IAES
LSIOPMIN
ODU1_TCMn_ES
OTU1_SES
LSOOPCUR
ODU1_TCMn_FEBBE
OTU1_SESR
LSOOPMAX
ODU1_TCMn_FEBBER
OTU1_UAS
LSOOPMIN
ODU1_TCMn_FEES
RSBBE
LSTMPCUR
ODU1_TCMn_FESES
RSCSES

849
OptiX OSN 8800/6800/3800

LSTMPMAX
ODU1_TCMn_FESESR
RSES
LSTMPMIN
ODU1_TCMn_FEUAS
RSSES
ODU1_PM_BBE
ODU1_TCMn_IAES
RSUAS
ODU1_PM_BBER
ODU1_TCMn_SES
XCSTMPCUR
ODU1_PM_ES
ODU1_TCMn_SESR
XCSTMPMAX
ODU1_PM_FEBBE
ODU1_TCMn_UAS
XCSTMPMIN
SEFS_S
RSOFS
NOTE
TCM6.

TN52TOM
Issue 02 (2011-10-31)
Packets Transmitted
Bad Octets Received
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Drop Events
Octets in Length)
Octets in Length)
Drop Events at
Transmission
Direction
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Good Octets
Transmitted

Length)
Octets in Length)
Jabbers
Packets Transmitted

850
OptiX OSN 8800/6800/3800

Multicast Packets
Received
Octets in Length)
TN11TOM
Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Octets in Length)
Pause Frames
Transmitted
Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received

in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
FCS Errors
Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
Drop Events
5.2.83 TQM Board Performance Event List

TN11TQM
Issue 02 (2011-10-31)
LSBIASCUR
LSTMPMIN
ODU1_PM_SESR
LSBIASMAX
ODU1_PM_BBE
ODU1_PM_UAS

851
OptiX OSN 8800/6800/3800

LSBIASMIN
ODU1_PM_BBER
RSBBE
LSIOPCUR
ODU1_PM_ES
RSCSES
LSIOPMAX
ODU1_PM_FEBBE
RSES
LSIOPMIN
ODU1_PM_FEBBER
RSSES
LSOOPCUR
ODU1_PM_FEES
RSUAS
LSOOPMAX
ODU1_PM_FESES
XCSTMPCUR
LSOOPMIN
ODU1_PM_FESESR
XCSTMPMAX
LSTMPCUR
ODU1_PM_FEUAS
XCSTMPMIN
LSTMPMAX
ODU1_PM_SES
TN12TQM
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_FEBBE
OTU1_BBE
FEC_AFT_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BBER
FEC_BEF_COR_ER
ODU1_PM_FEES
OTU1_BIAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESES
OTU1_ES
FEC_COR_0BIT_CNT
ODU1_PM_FESESR
OTU1_FEBBE
FEC_COR_1BIT_CNT
ODU1_PM_FEUAS
OTU1_FEBBER
FEC_COR_BYTE_CNT
ODU1_PM_SES
OTU1_FEES
FEC_UNCOR_BLOCK_C
NT
ODU1_PM_SESR
OTU1_FESES
LSBIASCUR
ODU1_PM_UAS
OTU1_FESESR
LSBIASMAX
ODU1_TCMn_BBE
OTU1_FEUAS
LSBIASMIN
ODU1_TCMn_BBER
OTU1_IAES
LSIOPCUR
ODU1_TCMn_BIAES
OTU1_SES
LSIOPMAX
ODU1_TCMn_ES
OTU1_SESR
LSIOPMIN
ODU1_TCMn_FEBBE
OTU1_UAS
LSOOPCUR
ODU1_TCMn_FEBBER
RSBBE
LSOOPMAX
ODU1_TCMn_FEES
RSCSES
LSOOPMIN
ODU1_TCMn_FESES
RSES
LSTMPCUR
ODU1_TCMn_FESESR
RSSES
LSTMPMAX
ODU1_TCMn_FEUAS
RSUAS

852
OptiX OSN 8800/6800/3800

LSTMPMIN
ODU1_TCMn_IAES
XCSTMPCUR
ODU1_PM_BBE
ODU1_TCMn_SES
XCSTMPMAX
ODU1_PM_BBER
ODU1_TCMn_SESR
XCSTMPMIN
ODU1_PM_ES
ODU1_TCMn_UAS
SEFS_S
RSOFS
NOTE

TN11TQM
Drop Events
Multicast Packets
Received
FCS Errors
Fragments
Jabbers

Octets in Length)

Octets in Length)

Octets in Length)
Packets Received
(256~511 Octets in
Length)
Packets Received

Octets in Length)
Packets Received
(1519~MTU Octets in
Length)

Octets in Length)

Octets in Length)
Packets Transmitted
(128~255 Octets in
Length)
Packets Transmitted

Octets in Length)
Packets Transmitted
Length)
Packets Transmitted
(1519~MTU Octets in
Length)
Unicast Packets
Transmitted
Multicast Packets
Transmitted
Bad Octets Received
Drop Events at
Oversize Packets
Transmitted
Issue 02 (2011-10-31)

853
OptiX OSN 8800/6800/3800

TN12TQM
Packets Received
Length)
Multicast Packets
Transmitted
Packets Received
(1519~MTU Octets in
Length)
Broadcast Packets
Transmitted
Octets in Length)
Packets Transmitted
Fragments
Packets Transmitted
Jabbers
Packets Transmitted

Length)
Packets Transmitted
Bad Octets Received
Octets in Length)
Packets Transmitted
Length)
Octets in Length)
Packets Transmitted
(1519~MTUOctets in
Length)
Alignment Errors
Octets in Length)
Drop Events at
Octets in Length)
Oversize Packets
Transmitted
5.2.84 TQS Board Performance Event List
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU1_PM_FEBBE
OTU1_BBE
FEC_AFT_COR_ERAVR
ODU1_PM_FEBBER
OTU1_BBER
FEC_BEF_COR_ER
ODU1_PM_FEES
OTU1_BIAES
FEC_BEF_COR_ERAVR
ODU1_PM_FESES
OTU1_ES
FEC_COR_0BIT_CNT
ODU1_PM_FESESR
OTU1_FEBBE
FEC_COR_1BIT_CNT
ODU1_PM_FEUAS
OTU1_FEBBER
FEC_COR_BYTE_CNT
ODU1_PM_SES
OTU1_FEES

854
OptiX OSN 8800/6800/3800

FEC_UNCOR_BLOCK_C
NT
ODU1_PM_SESR
OTU1_FESES
LSBIASCUR
ODU1_PM_UAS
OTU1_FESESR
LSBIASMAX
ODU1_TCMn_BBE
OTU1_FEUAS
LSBIASMIN
ODU1_TCMn_BBER
OTU1_IAES
LSIOPCUR
ODU1_TCMn_BIAES
OTU1_SES
LSIOPMAX
ODU1_TCMn_ES
OTU1_SESR
LSIOPMIN
ODU1_TCMn_FEBBE
OTU1_UAS
LSOOPCUR
ODU1_TCMn_FEBBER
RSBBE
LSOOPMAX
ODU1_TCMn_FEES
RSCSES
LSOOPMIN
ODU1_TCMn_FESES
RSES
LSTMPCUR
ODU1_TCMn_FESESR
RSOFS
LSTMPMAX
ODU1_TCMn_FEUAS
RSSES
LSTMPMIN
ODU1_TCMn_IAES
RSUAS
ODU1_PM_BBE
ODU1_TCMn_SES
XCSTMPCUR
ODU1_PM_BBER
ODU1_TCMn_SESR
XCSTMPMAX
ODU1_PM_ES
ODU1_TCMn_UAS
XCSTMPMIN
NOTE
TCM6.
NOTE
5.2.85 TQX Board Performance Event List

TN55TQX
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU2_PM_FEBBER
ODUFLEX_PM_FESESR
FEC_AFT_COR_ER
ODU2_PM_FEES
ODUFLEX_PM_FEUAS
FEC_AFT_COR_ERAV
R
ODU2_PM_FESES
ODUFLEX_PM_SES
FEC_BEF_CORER_FLO
AT
ODU2_PM_FESESR
ODUFLEX_PM_SESR
FEC_BEF_COR_ER
ODU2_PM_FEUAS
ODUFLEX_PM_UAS

855
OptiX OSN 8800/6800/3800

FEC_BEF_COR_ERAV
R
ODU2_PM_SES
OTU2_BBE
FEC_COR_0BIT_CNT
ODU2_PM_SESR
OTU2_BBER
FEC_COR_1BIT_CNT
ODU2_PM_UAS
OTU2_BIAES
FEC_COR_BYTE_CNT
ODU2_TCMn_BBE
OTU2_ES
FEC_UNCOR_BLOCK_
CNT
ODU2_TCMn_BBER
OTU2_FEBBE
LSBIASCUR
ODU2_TCMn_BIAES
OTU2_FEBBER
LSBIASMAX
ODU2_TCMn_ES
OTU2_FEES
LSBIASMIN
ODU2_TCMn_FEBBE
OTU2_FESES
LSCLCCUR
ODU2_TCMn_FEBBER
OTU2_FESESR
LSCLCMAX
ODU2_TCMn_FEES
OTU2_FEUAS
LSCLCMIN
ODU2_TCMn_FESES
OTU2_IAES
LSIOPCUR
ODU2_TCMn_FESESR
OTU2_SES
LSIOPMAX
ODU2_TCMn_FEUAS
OTU2_SESR
LSIOPMIN
ODU2_TCMn_IAES
OTU2_UAS
LSOOPCUR
ODU2_TCMn_SES
RSBBE
LSOOPMAX
ODU2_TCMn_SESR
RSCSES
LSOOPMIN
ODU2_TCMn_UAS
RSES
LSTMPCUR
ODUFLEX_PM_BBE
RSOFS
LSTMPMAX
ODUFLEX_PM_BBER
RSSES
LSTMPMIN
ODUFLEX_PM_ES
RSUAS
ODU2_PM_BBE
ODUFLEX_PM_FEBBE
XCSTMPCUR
ODU2_PM_BBER
ODUFLEX_PM_FEBBER
XCSTMPMAX
ODU2_PM_ES
ODUFLEX_PM_FEES
XCSTMPMIN
ODU2_PM_FEBBE
ODUFLEX_PM_FESES
TN53TQX
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLO
AT
ODU2_PM_BBE
ODU2_TCMn_UAS
FEC_AFT_COR_ER
ODU2_PM_BBER
OTU2_BBE

856
OptiX OSN 8800/6800/3800

FEC_AFT_COR_ERAV
R
ODU2_PM_ES
OTU2_BBER
FEC_BEF_CORER_FLO
AT
ODU2_PM_FEBBE
OTU2_BIAES
FEC_BEF_COR_ER
ODU2_PM_FEBBER
OTU2_ES
FEC_BEF_COR_ERAV
R
ODU2_PM_FEES
OTU2_FEBBE
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBER
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEES
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FESES
FEC_UNCOR_BLOCK_
CNT
ODU2_PM_SES
OTU2_FESESR
LSBIASCUR
ODU2_PM_SESR
OTU2_FEUAS
LSBIASMAX
ODU2_PM_UAS
OTU2_IAES
LSBIASMIN
ODU2_TCMn_BBE
OTU2_SES
LSCLCCUR
ODU2_TCMn_BBER
OTU2_SESR
LSCLCMAX
ODU2_TCMn_BIAES
OTU2_UAS
LSCLCMIN
ODU2_TCMn_ES
RSBBE
LSIOPCUR
ODU2_TCMn_FEBBE
RSCSES
LSIOPMAX
ODU2_TCMn_FEBBER
RSES
LSIOPMIN
ODU2_TCMn_FEES
RSOFS
LSOOPCUR
ODU2_TCMn_FESES
RSSES
LSOOPMAX
ODU2_TCMn_FESESR
RSUAS
LSOOPMIN
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPCUR
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMAX
ODU2_TCMn_SES
XCSTMPMIN
LSTMPMIN
ODU2_TCMn_SESR
TN52TQX
Issue 02 (2011-10-31)
FEC_AFT_COR_ER
ODU2_PM_ES
OTU2_BBE
FEC_AFT_COR_ERAV
R
ODU2_PM_FEBBE
OTU2_BBER
FEC_BEF_COR_ER
ODU2_PM_FEBBER
OTU2_BIAES

857
OptiX OSN 8800/6800/3800

FEC_BEF_COR_ERAV
R
ODU2_PM_FEES
OTU2_ES
FEC_COR_0BIT_CNT
ODU2_PM_FESES
OTU2_FEBBE
FEC_COR_1BIT_CNT
ODU2_PM_FESESR
OTU2_FEBBER
FEC_COR_BYTE_CNT
ODU2_PM_FEUAS
OTU2_FEES
FEC_UNCOR_BLOCK_
CNT
ODU2_PM_SES
OTU2_FESES
FEC_BEF_CORER_FL
OAT
ODU2_PM_SESR
OTU2_FESESR
FEC_AFT_CORER_FL
OAT
ODU2_PM_UAS
OTU2_FEUAS
LSBIASCUR
ODU2_TCMn_BBE
OTU2_IAES
LSBIASMAX
ODU2_TCMn_BBER
OTU2_SES
LSBIASMIN
ODU2_TCMn_BIAES
OTU2_SESR
LSIOPCUR
ODU2_TCMn_ES
OTU2_UAS
LSIOPMAX
ODU2_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU2_TCMn_FEBBER
RSES
LSOOPCUR
ODU2_TCMn_FEES
RSCSES
LSOOPMAX
ODU2_TCMn_FESES
RSSES
LSOOPMIN
ODU2_TCMn_FESESR
RSUAS
LSTMPCUR
ODU2_TCMn_FEUAS
XCSTMPCUR
LSTMPMAX
ODU2_TCMn_IAES
XCSTMPMAX
LSTMPMIN
ODU2_TCMn_SES
XCSTMPMIN
ODU2_PM_BBE
ODU2_TCMn_SESR
SEFS_S
ODU2_PM_BBER
ODU2_TCMn_UAS
RSOFS
TN11TQX
Issue 02 (2011-10-31)
LSBIASCUR
LSTMPCUR
ODU2_PM_SES
LSBIASMAX
LSTMPMAX
ODU2_PM_SESR
LSBIASMIN
LSTMPMIN
ODU2_PM_UAS
LSCLCCUR
ODU2_PM_BBE
RSBBE
LSCLCMAX
ODU2_PM_BBER
RSCSES

858
OptiX OSN 8800/6800/3800

LSCLCMIN
ODU2_PM_ES
RSES
LSIOPCUR
ODU2_PM_FEBBE
RSSES
LSIOPMAX
ODU2_PM_FEBBER
RSUAS
LSIOPMIN
ODU2_PM_FEES
XCSTMPCUR
LSOOPCUR
ODU2_PM_FESES
XCSTMPMAX
LSOOPMAX
ODU2_PM_FESESR
XCSTMPMIN
LSOOPMIN
ODU2_PM_FEUAS
SEFS_S
RSOFS
NOTE

TN55TQX
Issue 02 (2011-10-31)
Octets in Length)
Alignment Errors
Octets Transmitted
Bad Octets
Received
Packets Transmitted
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Packets Received
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Control Frames
Received
Octets in Length)
Octets in Length)
Control Frames
Transmitted
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Jabbers

Length)
Multicast Packets
Received

in Length)

859
OptiX OSN 8800/6800/3800

Multicast Packets
Transmitted
Packets Transmitted
Octets Received
Octets in Length)
TN53TQX
Octets in Length)
Alignment Errors
Octets Transmitted
Bad Octets
Received
Packets Transmitted
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Packets Received
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Control Frames
Received
Octets in Length)
Octets in Length)
Control Frames
Transmitted
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Jabbers

Length)
Multicast Packets
Received

in Length)
Multicast Packets
Transmitted
Packets Transmitted
Octets Received
Octets in Length)
TN52TQX
Alignment Errors
Issue 02 (2011-10-31)
Octets Transmitted

Octets in Length)
860
OptiX OSN 8800/6800/3800

Bad Octets
Received
Packets Transmitted
Bad Octets
Transmitted
Octets in Length)
Broadcast Packets
Transmitted
Packets Received
Octets in Length)
Broadcast Packets
Received
Octets in Length)

Length)
Control Frames
Received
Octets in Length)
Octets in Length)
Control Frames
Transmitted
Octets in Length)
FCS Errors
Octets in Length)
Fragments
Octets in Length)
Jabbers

Length)
Multicast Packets
Received

in Length)
Multicast Packets
Transmitted
Packets Transmitted
Octets Received
Octets in Length)
TN11TQX
Octets Received
Undersize Packets
Received
Packets Received
FCS Errors
5.2.86 TSXL Board Performance Event List

TN11TSXL
Issue 02 (2011-10-31)
LSBIASCUR
LSTMPCUR
ODU2_PM_SES
LSBIASMAX
LSTMPMAX
ODU2_PM_SESR
LSBIASMIN
LSTMPMIN
ODU2_PM_UAS

861
OptiX OSN 8800/6800/3800

LSCLCCUR
ODU2_PM_BBE
RSBBE
LSCLCMAX
ODU2_PM_BBER
RSCSES
LSCLCMIN
ODU2_PM_ES
RSES
LSIOPCUR
ODU2_PM_FEBBE
RSOFS
LSIOPMAX
ODU2_PM_FEBBER
RSSES
LSIOPMIN
ODU2_PM_FEES
RSUAS
LSOOPCUR
ODU2_PM_FESES
XCSTMPCUR
LSOOPMAX
ODU2_PM_FESESR
XCSTMPMAX
LSOOPMIN
ODU2_PM_FEUAS
XCSTMPMIN
TN53TSXL
Issue 02 (2011-10-31)
FEC_AFT_CORER_FLOAT
ODU3_PM_ES
OTU3_BBE
FEC_AFT_COR_ER
ODU3_PM_FEBBE
OTU3_BBER
FEC_AFT_COR_ERAVR
ODU3_PM_FEBBER
OTU3_BIAES
FEC_BEF_CORER_FLOAT
ODU3_PM_FEES
OTU3_ES
FEC_BEF_COR_ER
ODU3_PM_FESES
OTU3_FEBBE
FEC_BEF_COR_ERAVR
ODU3_PM_FESESR
OTU3_FEBBER
FEC_COR_0BIT_CNT
ODU3_PM_FEUAS
OTU3_FEES
FEC_COR_1BIT_CNT
ODU3_PM_SES
OTU3_FESES
FEC_COR_BYTE_CNT
ODU3_PM_SESR
OTU3_FESESR
FEC_UNCOR_BLOCK_CN
T
ODU3_PM_UAS
OTU3_FEUAS
LSBIASCUR
ODU3_TCMn_BBE
OTU3_IAES
LSBIASMAX
ODU3_TCMn_BBER
OTU3_SES
LSBIASMIN
ODU3_TCMn_BIAES
OTU3_SESR
LSIOPCUR
ODU3_TCMn_ES
OTU3_UAS
LSIOPMAX
ODU3_TCMn_FEBBE
RSBBE
LSIOPMIN
ODU3_TCMn_FEBBER
RSCSES
LSOOPCUR
ODU3_TCMn_FEES
RSES
LSOOPMAX
ODU3_TCMn_FESES
RSOFS
LSOOPMIN
ODU3_TCMn_FESESR
RSSES

862
OptiX OSN 8800/6800/3800

LSTMPCUR
ODU3_TCMn_FEUAS
RSUAS
LSTMPMAX
ODU3_TCMn_IAES
XCSTMPCUR
LSTMPMIN
ODU3_TCMn_SES
XCSTMPMAX
ODU3_PM_BBE
ODU3_TCMn_SESR
XCSTMPMIN
ODU3_PM_BBER
ODU3_TCMn_UAS
NOTE
TCM6.
Issue 02 (2011-10-31)
FCS Errors
Unicast Packets
Received
Good Octets
Transmitted

Octets in Length)
Packets Transmitted
Broadcast Packets
Received
Packets Transmitted
Packets Received (64 Octets in

Length)
Fragments
Packets Transmitted
Packets Received (65~127 Octets

in Length)
Multicast Packets
Received
Packets Transmitted
(512~1023 Octets in
Length)

Octets in Length)
Undersize Packets
Received
Packets Transmitted
Length)
Packets Received (256~511 Octets

in Length)
Oversize Packets
Received
Packets Transmitted
(1519~MTU Octets in
Length)

Octets in Length)
Jabbers

Octets in Length)
Packets Received (1519~MTU

Octets in Length)

863
OptiX OSN 8800/6800/3800

5.2.87 VA1 Board Performance Event List

TN11VA1
ICTMPCUR
SUMIOPCUR
XCSTMPCUR
ICTMPMAX
SUMIOPMAX
XCSTMPMAX
ICTMPMIN
SUMIOPMIN
XCSTMPMIN
XCSTMPMAX
XCSTMPMIN
TN12VA1
XCSTMPCUR
5.2.88 VA4 Board Performance Event List

TN11VA4
ICTMPCUR
ICTMPMIN
XCSTMPMAX
ICTMPMAX
XCSTMPCUR
XCSTMPMIN
XCSTMPMAX
XCSTMPMIN
TN12VA4
XCSTMPCUR
5.2.89 WMU Board Performance Event List

PCLSWLCUR
PCLSOPCUR
XCSTMPMAX
PCLSWLOCUR
XCSTMPCUR
XCSTMPMIN
5.2.90 WSD9 Board Performance Event List
Issue 02 (2011-10-31)
ICTMPCUR
SUMIOPCUR
XCSTMPCUR
ICTMPMAX
SUMIOPMAX
XCSTMPMAX
ICTMPMIN
SUMIOPMIN
XCSTMPMIN

864
OptiX OSN 8800/6800/3800

5.2.91 WSM9 Board Performance Event List

ICTMPCUR
SUMOOPCUR
XCSTMPCUR
ICTMPMAX
SUMOOPMAX
XCSTMPMAX
ICTMPMIN
SUMOOPMIN
XCSTMPMIN
5.2.92 WSMD2 Board Performance Event List

ICTMPCUR
SUMIOPMAX
SUMOOPMIN
ICTMPMAX
SUMIOPMIN
XCSTMPCUR
ICTMPMIN
SUMOOPCUR
XCSTMPMAX
SUMIOPCUR
SUMOOPMAX
XCSTMPMIN

ICTMPCUR
SUMIOPMAX
SUMOOPMIN
ICTMPMAX
SUMIOPMIN
XCSTMPCUR
ICTMPMIN
SUMOOPCUR
XCSTMPMAX
SUMIOPCUR
SUMOOPMAX
XCSTMPMIN

ICTMPCUR
SUMIOPMAX
SUMOOPMIN
ICTMPMAX
SUMIOPMIN
XCSTMPCUR
ICTMPMIN
SUMOOPCUR
XCSTMPMAX
SUMIOPCUR
SUMOOPMAX
XCSTMPMIN
5.2.95 XCH Board Performance Event List

TN16XCH
Issue 02 (2011-10-31)
XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
MAXFREQDEV
MINFREQDEV
AVGFREQDEV

865
OptiX OSN 8800/6800/3800

MAXPHASEOFFSET
MINPHASEOFFSET
AVGPHASEOFFSET
MAXMEANPATHDELAY
MINMEANPATHDELAY
AVGMEANPATHDELAY
XCSTMPMAX
XCSTMPMIN
TN52XCH
XCSTMPCUR
5.2.96 XCM Board Performance Event List

TN52XCM
XCSTMPCUR
XCSTMPMAX
XCSTMPMIN
5.2.97 XCT Board Performance Event List

XCSTMPCUR
Issue 02 (2011-10-31)
XCSTMPMAX

XCSTMPMIN
866
OptiX OSN 8800/6800/3800

6 Performance Event Processing
Performance Event Processing
About This Chapter

The performance event is an important parameter to evaluate the working performance of
equipment. Being acquainted with the generation principle, related boards and related alarms
helps you discover hidden trouble in routine maintenance and locate faults in troubleshooting.
If a performance event exceeds the threshold, the related alarms are generated. Therefore, upon
any performance event, check any related alarms and handle the event accordingly.
The meaning of the n and k in this topic as follows:
l
k indicates the level of rate and its value is 1, 2, 3 and 5G.
6.1 AUPJCHIGH
6.2 AUPJCLOW
6.3 AUPJCNEW
6.4 BCV
6.5 CCV
6.6 CRC4ES
6.7 CRC4FEES
6.8 CRC4FESES
6.9 CRC4FEUAS
6.10 CRC4SES
6.11 CRC4UAS
6.12 EDTMP
6.13 EDTPL
6.14 ENVTMP
6.15 FEC_AFT_COR_ER
Issue 02 (2011-10-31)

867
OptiX OSN 8800/6800/3800

6.16 FEC_AFT_COR_ERAVR
6.17 FEC_AFT_CORER_FLOAT
6.18 FEC_BEF_COR_ER
6.19 FEC_BEF_COR_ERAVR
6.20 FEC_BEF_CORER_FLOAT
6.21 FEC_COR_0BIT_CNT
6.23 FEC_COR_BYTE_CNT
6.24 FEC_UNCOR_BLOCK_CNT
6.25 HPBBE
6.26 HPCSES
6.27 HPES
6.28 HPFEBBE
6.29 HPFECSES
6.30 HPFEES
6.31 HPFESES
6.32 HPFEUAS
6.33 HPSES
6.34 HPUAS
6.35 ICCLC
6.36 ICTMP
6.37 LSBIAS
6.38 LSBISA
6.39 LSCLC
6.40 LSIOP
6.41 LSOOP
6.42 LSTMP
6.43 MSBBE
6.44 MSCSES
6.45 MSES
6.46 MSFEBBE
6.47 MSFECSES
6.48 MSFEES
Issue 02 (2011-10-31)

868
OptiX OSN 8800/6800/3800

6.49 MSFESES
6.50 MSFEUAS
6.51 MSSES
6.52 MSUAS
6.53 ODU2PMBIP8
6.54 ODUk_PM_BBE
6.55 ODUk_PM_BBER
6.56 ODUk_PM_ES
6.57 ODUk_PM_FEBBE
6.58 ODUk_PM_FEBBER
6.59 ODUk_PM_FEES
6.60 ODUk_PM_FESES
6.61 ODUk_PM_FESESR
6.62 ODUk_PM_FEUAS
6.63 ODUk_PM_SES
6.64 ODUk_PM_SESR
6.65 ODUk_PM_UAS
6.66 ODUk_TCMn_BBE
6.67 ODUk_TCMn_BBER
6.68 ODUk_TCMn_BIAES
6.69 ODUk_TCMn_ES
6.70 ODUk_TCMn_FEBBE
6.71 ODUk_TCMn_FEBBER
6.72 ODUk_TCMn_FEES
6.73 ODUk_TCMn_FESES
6.74 ODUk_TCMn_FESESR
6.75 ODUk_TCMn_FEUAS
6.76 ODUk_TCMn_IAES
6.77 ODUk_TCMn_SES
6.78 ODUk_TCMn_SESR
6.79 ODUk_TCMn_UAS
6.80 OOPRL
6.81 OSC_BBE
Issue 02 (2011-10-31)

869
OptiX OSN 8800/6800/3800

6.82 OSC_BBER
6.83 OSC_BIAES
6.84 OSC_ES
6.85 OSC_FEBBE
6.86 OSC_FEBBER
6.87 OSC_FEES
6.88 OSC_FESES
6.89 OSC_FESESR
6.90 OSC_FEUAS
6.91 OSC_IAES
6.92 OSC_SES
6.93 OSC_SESR
6.94 OSC_UAS
6.95 OSPICCV
6.96 OSPITMP
6.97 OTU2SMBIP8
6.98 OTUk_BBE
6.99 OTUk_BBER
6.100 OTUk_ES
6.101 OTUk_FEBBE
6.102 OTUk_FEBBER
6.103 OTUk_FEES
6.104 OTUk_FESES
6.105 OTUk_FESESR
6.106 OTUk_FEUAS
6.107 OTUk_SES
6.108 OTUk_SESR
6.109 OTUk_UAS
6.110 PCLSOP
6.111 PCLSSN
6.112 PCLSWL
6.113 PCLSWLO
6.114 RPL
Issue 02 (2011-10-31)

870
OptiX OSN 8800/6800/3800

6.115 RSBBE
6.116 RSCSES
6.117 RSES
6.118 RSOFS
6.119 RSOOF
6.120 RSSES
6.121 RSUAS
6.122 SUMIOP
6.123 SUMOOP
6.124 TLB
6.125 TPL
6.126 VC3BBE
6.127 VC3CSES
6.128 VC3ES
6.129 VC3FEBBE
6.130 VC3FECSES
6.131 VC3FEES
6.132 VC3FESES
6.133 VC3FEUAS
6.134 VC3SES
6.135 VC3UAS
6.136 WCV
6.137 XCSTMP
Issue 02 (2011-10-31)

871
OptiX OSN 8800/6800/3800

6.1 AUPJCHIGH
Description
Administrative unit pointer justification count high
It indicates the positive justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
the cause and solve the problem timely to avoid any alarm to ensure the signal transmission
quality.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs on the SDH network are
not synchronous. The possible causes of the event are as follows:
l
The performance of the external clock is degraded.
The clocks in two NEs trace each other because the optical fibers are connected incorrectly.
The equipment performance is degraded due to high temperature.
The clocks are configured incorrectly. If the SSM protocol is enabled but the clock IDs are
not set, the loss of the primary clock source causes the network-wide pointer justification
event.
The clock quality is degraded because the SSM clock protection is disabled.
The performance of the line board is degraded.
The performance of the clock board is degraded.
Related Alarms
None
Procedure
Step 1 Check whether clock alarms, such as the SYN_BAD, LTI, S1_SYN_CHANGE and
EXT_SYNC_LOS, are generated in the whole network. If yes, take priority to clear them.
Step 2 For the network-wide pointer justification, check whether the clock configurations are consistent
with those specified in the plan, including clock ID, SSM protocol, and clock tracing level.
Step 3 For the non-network-wide pointer justification, check whether the optical fibers are connected
correctly, and whether the ambient temperature of the equipment is within the normal range. If
the AU pointer justification event occurs continuously, contact the technical support engineers
of Huawei.
----End
Issue 02 (2011-10-31)

872
OptiX OSN 8800/6800/3800

Related Information
None
6.2 AUPJCLOW
Description
Administrative unit pointer justification count low
It indicates the negative justification count of the AU pointer when the rate of VC frame is
adjusted.
Impact on System
A small number of pointer justification counts bring no impact on the services. A large number
of pointer justification counts, however, cause bit errors in the services. In this case, determine
quality.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
not synchronous. The possible causes are as follows:
l
event.
Related Alarms
None
Procedure
Issue 02 (2011-10-31)

873
OptiX OSN 8800/6800/3800

of Huawei.
----End
Related Information
None
6.3 AUPJCNEW
Description
New count of administrative unit pointer
Impact on System
A little pointer justification does not affect the services. A large pointer justification can cause
bit errors in the services and in this case, you need to find out the causes and take proper measures
to ensure the transmission quality and prevent alarms.

The root cause of generating new data flag (pointer) for the AU pointer justification event is that
the clocks of NEs in the SDH network are not synchronous. As a result, the new AU data flag
(pointer) event is generated. The possible causes are as follows:
l
event.
Related Alarms
None
Procedure
Issue 02 (2011-10-31)

874
OptiX OSN 8800/6800/3800

of Huawei.
----End
Related Information
None
6.4 BCV
Description
Pump Laser Back Facet Current
It includes:
l
BCVMAX: stands for the maximum value during a period of time.
BCVMIN: stands for the minimum value during a period of time.
BCVCUR: stands for the current value.
Impact on System
None

Back facet current is current O/E converted from part of light reflected from the resonant cavity
of a laser. The back facet current reflects the laser output optical power value. If the BCVCUR
is 0, the laser is faulty. In this case, replace the board where this faulty laser resides in.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.5 CCV
Description
Pump Laser Cooling Current
Issue 02 (2011-10-31)

875
OptiX OSN 8800/6800/3800

It includes:
l
CCVMAX: stands for the maximum value during a period of time.
CCVMIN: stands for the minimum value during a period of time.
CCVCUR: stands for the current value.
Impact on System
None

Use an A/D converter to sample the voltage corresponding to the cooling current of each laser,
and convert the voltage into cooling current. This value shows the working status of the cooling
circuit in a certain laser.
Related Alarms
Alarm Name
Correlation
PUMP_COOL_EXC
It is generated when the cooling current of the

laser exceeds the normal range.
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.6 CRC4ES
Description
CRC4 errored seconds
Impact on System
There are bit errors in the services. If the CRC4 errored seconds are generated continuously,
determine the cause and solve the problem in a timely manner to avoid any alarm, thus to ensure
the signal transmission quality.

CRC error is detected by checking the received parity bit. An errored second contains more than
one error block.
Issue 02 (2011-10-31)

876
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
CRC4_CROSSTR
CRC4 multi-frame error code exceeds the

threshold. The alarm is generated when the
number of the bit errors in the CRC4 multiframe exceeds the threshold.
Procedure
Step 1 Refer to the method of handling the CRC4_CROSSTR.
----End
Related Information
None
6.7 CRC4FEES
Description
CRC4 far end errored second
Impact on System
There are bit errors in the services. If the far-end errored seconds are generated continuously,
the signal transmission quality. If the number of bit errors exceeds the threshold, the
CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. An errored second contains more than
one error block. And the far end errored second refers to the errored second detected at the
opposite end.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
CRC4_CROSSTR
CRC4 multi-frame error code counter

exceeds the threshold. The alarm is generated
when the number of the bit errors in the CRC4
multiframe exceeds the threshold.

877
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.8 CRC4FESES
Description
CRC4 far end severely errored second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem in a timely manner
to avoid any alarm, and thus to ensure the signal transmission quality. If the number of bit errors
exceeds the threshold, the CRC4_CROSSTR alarm is generated.

CRC error is detected by checking the received parity bit. During a severely errored second,
there is at least one defect. And the far end severely errored second refers to the severely errored
second detected at the opposite end.
Related Alarms
Alarm Name
Correlation
CRC4_CROSSTR
CRC4 multi-frame error code count exceeds

the threshold. The alarm is generated when
the number of the bit errors in the CRC4
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

878
OptiX OSN 8800/6800/3800

6.9 CRC4FEUAS
Description
CRC4 far end unavailable second
Impact on System
because the bit errors have affected the signal transmission quality. If the number of bit errors

CRC error is detected by checking the received parity bit. If the severely errored seconds last
for more than 10 seconds, the unavailable second starts from the beginning of the 11th second,
and the former 10 severely errored seconds are counted as unavailable. If the severely errored
second disappears for more than 10 seconds, the available time starts from the beginning of the
11th second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name
Correlation
CRC4_CROSSTR

Procedure
----End
Related Information
None
6.10 CRC4SES
Description
CRC4 severely errored second
Issue 02 (2011-10-31)

879
OptiX OSN 8800/6800/3800

Impact on System

CRC error is detected by checking the received parity bit. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
Alarm Name
Correlation
CRC4_CROSSTR

Procedure
----End
Related Information
None
6.11 CRC4UAS
Description
CRC4 unavailable second
Impact on System

CRC error is detected by checking the received parity bit. If the severely errored seconds last
for more than 10 seconds, the unavailable second starts from the beginning of the 11th second,
and the former 10 severely errored seconds are counted as unavailable. If the severely errored
second disappears for more than 10 seconds, the available time starts from the beginning of the
11th second, and the former 10 seconds are counted as available.
Issue 02 (2011-10-31)

880
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
CRC4_CROSSTR

Procedure
----End
Related Information
None
6.12 EDTMP
Description
Laser temperature value
It includes:
l
EDTMPMAX: stands for the maximum value during a period of time.
EDTMPMIN: stands for the minimum value during a period of time.
EDTMPCUR: stands for the current value.
Impact on System
None

This performance event is detected by hardware detecting circuit and then the result is calculated
by the software for conversion. If the performance is not in the normal range, the EDFA module
might be faulty.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
PUM_TEM_ALM
Working temperature of the pump laser exceeds the threshold. This

alarm is generated when the pump laser operating temperature of the
optical amplifier unit exceeds the threshold.

881
OptiX OSN 8800/6800/3800

Procedure
Step 1 Refer to the method of handling the PUM_TEM_ALM.
----End
Related Information
None
6.13 EDTPL
Description
Pump output optical power
It includes:
l
EDTPLMAX: stands for the maximum value during a period of time.
EDTPLMIN: stands for the minimum value during a period of time.
EDTPLCUR: stands for the current value.
Impact on System
Bit errors may be generated in the services and the services may be interrupted.

This performance event is detected by hardware detecting circuit and then the result is calculated
by the software for conversion. If the performance is not in the normal range, the EDFA module
might be faulty.
Related Alarms
Alarm Name
Correlation
OUT_PWR_HIGH
It is generated when the optical power output by the pump laser is

higher than the upper threshold.
OUT_PWR_LOW
It is generated when the optical power output by the pump laser is

lower than the lower threshold.
Procedure
Step 1 Refer to the method of handling the OUT_PWR_HIGH or OUT_PWR_LOW.
----End
Related Information
None
Issue 02 (2011-10-31)

882
OptiX OSN 8800/6800/3800

6.14 ENVTMP
Description
Board environmental temperature
It includes:
l
ENVTMPMAX: stands for the maximum value during a period of time.
ENVTMPMIN: stands for the minimum value during a period of time.
ENVTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by hardware detecting to show the ambient temperature of
the board.
Related Alarms
Alarm Name
Correlation
TEMP_OVER
It is generated when the board working

temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None
6.15 FEC_AFT_COR_ER
Description
After FEC correct errored rate
Issue 02 (2011-10-31)

883
OptiX OSN 8800/6800/3800

Impact on System
After the error correction, in normal cases, the value should be 0. If the value is not 0, it indicates
that the bit errors in the services bring impact on the transmission quality. In this case, determine
the cause timely.

This performance event shows that there are still errors at the receiver after FEC. This
performance event is caused by low OSNR at the receive end. In normal cases, it should be 0.
In this case, there must be FEC_BEF_COR_ER accompanied and you should check the alarm
timely.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Signal degraded before FEC alarm. Signals sent from WDM sides of
the opposite-end OTUs have the FEC function. As a result, before
performing signal FEC in the receive direction of WDM side of the
local-end OTU, the local-end OTU counts the bit error rate. This alarm
is generated when the counted bit error rate exceeds the threshold.
Procedure
Step 1 Refer to the procedure for handling the BEFFEC_EXC.
----End
Related Information
None
6.16 FEC_AFT_COR_ERAVR
Description
After FEC Correct Average Errored Rate in monitor period.
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that
the bit errors in the services bring impact on the transmission quality. In this case, determine the
cause timely.

This performance event shows there are still errors at the receiver after FEC. This performance
event is caused by low OSNR at the receive end. Normally, it should be zero.
Issue 02 (2011-10-31)

884
OptiX OSN 8800/6800/3800

In this case, there must be FEC_BEF_COR_ERAVR accompanied. You can adjust the optical
power to increase the OSNR.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Procedure
----End
Related Information
None
6.17 FEC_AFT_CORER_FLOAT
Description
After FEC Correct Errored Rate (floating point values)
Impact on System
After the error correction, the value should be 0 normally. If the value is not 0, it indicates that
the bit errors in the services bring impact on the transmission quality. In this case, determine the
cause in a timely manner.

This performance event shows there are still errors at the receiver after FEC. This performance
event is caused by low OSNR at the receiving end. Normally, it should be zero.
In this case, there must be FEC_BEF_CORER_FLOAT accompanied. You can adjust the optical
power to increase the OSNR.
Issue 02 (2011-10-31)

885
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Procedure
----End
Related Information
None
6.18 FEC_BEF_COR_ER
Description
BER before FEC
Impact on System
There are bit errors in the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates normally. If the BER is high, determine the causes and solve
the problem timely to avoid any alarm to ensure the signal transmission quality.

The cause for the BER before the FEC is that the receiver detects bit errors, which are caused
by dispersion, unstable performance of the optical port, and/or excessively high attenuation.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
BEFFEC_EXC

886
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.19 FEC_BEF_COR_ERAVR
Description
Before FEC Correct Average Errored Rate in monitor period.
Impact on System
(BER) is low, the system operates normally. If the BER is high, determine the cause and solve
the problem timely to avoid any alarm to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR
at the receive end. Normally, it should be zero.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Procedure
Step 1 Refer to the method of handling the BEFFEC_EXC.
----End
Related Information
None
Issue 02 (2011-10-31)

887
OptiX OSN 8800/6800/3800

6.20 FEC_BEF_CORER_FLOAT
Description
Before FEC Correct Errored Rate (floating point values)
Impact on System
(BER) is low, the system operates normally. If the BER is high, determine the cause and solve
the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission quality.

This performance event shows errors are detected at the receiver, which is caused by low OSNR
at the receiving end.
Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Signal degraded before FEC alarm. Signals sent from WDM side of
the local-end OTU, the local-end OTU counts the bit error rate. This
alarm is generated when the counted bit error rate exceeds the
threshold.
BEFFEC_SD
Signal degraded alarm before FEC alarm. Signals sent from WDM
side of the local-end OTU, the local-end OTU counts the bit error rate.
This alarm is generated when the counted bit error rate exceeds the
threshold.
Procedure
----End
Related Information
None
Description
Forward error correction - corrected 0 bit count
Issue 02 (2011-10-31)

888
OptiX OSN 8800/6800/3800

Impact on System
None

This performance event shows the number of 0bit corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
Description
Forward error correction - corrected 1 bit count
Impact on System
None

This performance event shows the number of 1bit corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
Issue 02 (2011-10-31)

889
OptiX OSN 8800/6800/3800

6.23 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None

This performance event shows the number of byte corrected by FEC function of the board, and
indicates the FEC capability to signals of low OSNR. Normally, it should be 0.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.24 FEC_UNCOR_BLOCK_CNT
Description
Forward error correction - uncorrected block count
Impact on System
There are bit errors in the services and the signal transmission quality is affected.

This performance event shows the number of received error frames that cannot be corrected by
FEC, and indicates that signals of low OSNR are beyond the correction capability of FEC.
Normally, the performance value should be 0.
Issue 02 (2011-10-31)

890
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
BEFFEC_EXC
Signal degraded before FEC alarm. Signals sent from WDM side of
the local-end OTU, the local-end OTU counts the bit error rate. This
alarm is generated when the counted bit error rate exceeds the
threshold.
Procedure
----End
Related Information
None
6.25 HPBBE
Description
Higher order path background block error
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
system is not affected. You need to, however, find out the causes and take proper measures in
time to avoid any alarm, which affects the quality of the signals transmitted in the higher order
path.

The HPBBEs are detected by means of detecting the B3 byte. The possible causes of the event
are as follows:
l
There is interference from the external environment.
A fault occurs in the switch that interworks with the SDH equipment.
The signal cable is faulty.
The line board is faulty.
The cross-connection unit is faulty.
The clock unit is faulty.
Issue 02 (2011-10-31)

891
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
B3_SD
When the count of B3 bit errors in the alarm path exceeds the threshold of
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC
the B3_EXC, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The background block error means that one or more bit errors occur in the data block during
transmission.
6.26 HPCSES
Description
Higher order path consecutive severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The severely
errored second (SES) refers to the second in which more than 30% errored blocks occur or at
least one serious disturbance period (SDP) occurs. Generally, the consecutive severely errored
second (CSES) is accompanied by the B3_EXC alarm. Consequently, the services are
interrupted. The possible causes of the event are as follows:
l
Issue 02 (2011-10-31)

892
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
B3_SD
When the count of B3 bit errors in the alarm path exceeds the
threshold of the B3_SD but lower than the threshold of the
B3_EXC, the alarm is reported.
B3_EXC
threshold of the B3_EXC, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
None
6.27 HPES
Description
Higher order path errored second
Impact on System
A small number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

Bit errors in the higher order path are detected by means of detecting the B3 byte. The possible
causes of the event are as follows:
l
Issue 02 (2011-10-31)

893
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
B3_SD
B3_EXC
threshold, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarm.
----End
Related Information
The errored second (ES) refers to the second in which one or more errored blocks are detected.
6.28 HPFEBBE
Description
Higher order path far end background block error
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is
generated, the system is not affected. You need to, however, find out the causes and take proper
measures in time to avoid any alarm, which affects the quality of the signals transmitted in the
higher order path.

The HPFEBBE refers to the higher order path block error that is detected at the opposite station.
The possible causes of the event are as follows:
l
Issue 02 (2011-10-31)

894
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
HP_REI
If the board has detected that the value is 1-8 for bits 1-4 of the G1 byte
in the higher order path, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the HP_REI alarm.
----End
Related Information
The background block error means that one or more bit errors occur in the data block during
transmission.
6.29 HPFECSES
Description
Higher order path far end consecutive severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.

The consecutive severely errored bits at the far end of the higher order path are detected by
means of detecting the G1 byte. The possible causes of the event are as follows:
l
Issue 02 (2011-10-31)

895
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
HP_REI
If the board has detected that the value is 1-8 for bits 1-4 of the G1
byte in the higher order path, the alarm is reported.
Procedure
----End
Related Information
The severely errored second (SES) refers to the second in which more than 30% errored blocks
occur or at least one serious disturbance period (SDP) occurs.
Consecutive Severely Errored Second
The consecutive severely errored second (CSES) refers to the severely errored second (SES)
event that occurs consecutively.
Remote Bit Error
The remote bit error refers to the bit error that is detected at the opposite station.
6.30 HPFEES
Description
Higher order path far end errored second
Impact on System
A small number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.

l
Issue 02 (2011-10-31)

896
OptiX OSN 8800/6800/3800

The cross-connection clock unit is faulty.
Related Alarms
Alarm Name
Correlation
HP_REI
Procedure
----End
Related Information
Remote Errored Second
The remote errored second refers to the errored second that is detected at the peer end.
6.31 HPFESES
Description
Higher order path far end severely errored second
Impact on System
A great number of bit errors occur at the far end of the higher order path. If no related alarm is
higher order path.

l
The cross-connect unit is faulty.
Issue 02 (2011-10-31)

897
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
HP_REI
Procedure
----End
Related Information
The severely errored second (SES) refers to the second in which more than 30% errored blocks
occur or at least one serious disturbance period (SDP) occurs.
6.32 HPFEUAS
Description
Higher order path far end unavailable second
Impact on System
If bit errors occur in the services on a remote NE, detect the causes and troubleshoot the problem
in a timely manner. Otherwise, alarms will be generated and the signal transmission quality will
be affected.

HPFEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
The fiber performance degrades and the attenuation is excessively high at the opposite
station.
The fiber connector is dirty or incorrect at the opposite station.
The equipment is improperly grounded at the opposite station.
There is a strong interference source around the equipment at the opposite station.
The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:
Issue 02 (2011-10-31)

898
OptiX OSN 8800/6800/3800

The signal attenuation at the receive side of the line board at the opposite station is
excessively high, the transmitting circuit of the opposite station is faulty, or the receiving
circuit of the local station is faulty.
The synchronization performance of the clock is poor at the opposite station.
The cross-connect unit and the service board do not work with each other properly at the
opposite station.
The fan of the opposite equipment is faulty.
The board fails or the board performance degrades at the opposite station.
Related Alarms
Alarm Name
Correlation
HP_REI
Higher order path remote error indication
HP_RDI
Remote defect indication in higher order paths
Procedure
Step 1 If any alarm is generated, use the method of the related alarm to clear it.
----End
Related Information
None.
6.33 HPSES
Description
Higher order path severely errored second
Impact on System
A great number of bit errors occur in the higher order path. If no related alarm is generated, the
path.

l
Issue 02 (2011-10-31)

899
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
B3_SD
B3_EXC
Procedure
Step 1 Refer to the method of handling the B3_SD and B3_EXC alarms.
----End
Related Information
The severely errored second (SES) refers to the second in more than 30% errored blocks occur
or at least one serious disturbance period (SDP) occurs.
6.34 HPUAS
Description
Higher order path unavailable second
Impact on System
l
A great number of bit errors occur in the higher order path. If no related alarm is generated,
the system is not affected. You need to, however, find out the causes and take proper
measures in time to avoid any alarm, which affects the quality of the signals transmitted in
the higher order path.
If the performance event is generated, check whether the AU_AIS, B3_EXC and
HP_UNEQ alarms are generated. If yes, the services may be interrupted.

Bit errors in the higher order path are detected by means of detecting the B3 byte. When signals
are consecutively received for 10 seconds, and if the bit error ratio per second is more than
10-3, the period from the first second is called the period of UAS (unavailable second). When
signals are consecutively received for 10 seconds, and if the bit error ratio per second is less than
Issue 02 (2011-10-31)

900
OptiX OSN 8800/6800/3800

10-3, the period from the first second is called the period of available second. The errored second
(ES) refers to the second in which one or more errored blocks occur. The possible causes of the
event are as follows:
l
Related Alarms
Alarm Name
Correlation
B3_SD
the B3_SD but lower than the threshold of the B3_EXC, the alarm is
reported.
B3_EXC
When the count of B3 bit errors in the alarm path exceeds the threshold,
the alarm is reported.
AU_AIS
When the alarm is generated, the HPUAS value is increased.
HP_TIM
HP_UNEQ
Procedure
Step 1 Refer to the method of handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and
HP_UNEQalarms.
----End
Related Information
None
6.35 ICCLC
Description
Module cooling current
It includes:
l
ICCLCMAX: stands for the maximum value during a period of time.
ICCLCMIN: stands for the minimum value during a period of time.
ICCLCCUR: stands for the current value.
Issue 02 (2011-10-31)

901
OptiX OSN 8800/6800/3800

Impact on System
None

This performance event is generated by software checking with the cooling current detecting
circuit on the board, to show the working status of module cooling current.
Related Alarms
None
Alarm Name
Correlation
MODULE_COOLCUR_OVER
It is generated when the cooling or warming

current of module exceeds the alarm
threshold.
Procedure
Step 1 If the MODULE_COOLCUR_OVER alarm is generated, see the handling procedure of the
alarm.
Step 2 None
----End
Related Information
None
6.36 ICTMP
Description
Module temperature
It includes:
l
ICTMPMAX: stands for the maximum value during a period of time.
ICTMPMIN: stands for the minimum value during a period of time.
ICTMPCUR: stands for the current value.
Impact on System
None
Issue 02 (2011-10-31)

902
OptiX OSN 8800/6800/3800


This performance event is generated by checking the current working temperature of module to
show the working temperature of a module.
Related Alarms
Alarm Name
Correlation
MODULE_TEMP_OVER
It is generated when the working temperature

of a module exceeds the threshold.
Procedure
Step 1 If the MODULE_TEMP_OVER alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.37 LSBIAS
Description
Laser bias current
It includes:
l
LSBIASMAX: stands for the maximum value during a period of time.
LSBIASMIN: stands for the minimum value during a period of time.
LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
TD
It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.
903
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
LSR_WILL_DIE
It is generated when the working current of a

laser exceeds the threshold or a multiple of
the threshold.
Procedure
Step 1 If the TD alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.38 LSBISA
Description
Laser bias current
It includes:
l
LSBIASMAX: stands for the maximum value during a period of time.
LSBIASMIN: stands for the minimum value during a period of time.
LSBIASCUR: stands for the current value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
TD
It is generated when the working current of a laser exceeds

the threshold or a multiple of the threshold.
LSR_WILL_DIE
It is generated when the working current of a laser exceeds

the threshold or a multiple of the threshold.

904
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.39 LSCLC
Description
Laser cooling current
It includes:
l
LSCLCMAX: stands for the maximum value during a period of time.
LSCLCMIN: stands for the minimum value during a period of time.
LSCLCCUR: stands for the current value.
Impact on System
When the cooling current of a laser exceeds the threshold, the optical module of the board works
abnormally. As a result, services cannot be transmitted or received normally.

External cooling equipment should be provided to keep the temperature stable for a laser to
work. The laser cooling current shows the working status of cooling equipment or circuit.
Related Alarms
Alarm Name
Correlation
LSR_COOL_ALM
It is generated when the laser cooling current

exceeds the pre-set threshold.
Procedure
Step 1 If the LSR_COOL_ALM alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
Issue 02 (2011-10-31)

905
OptiX OSN 8800/6800/3800

6.40 LSIOP
Description
Input optical power
It includes:
l
LSIOPMAX: stands for the maximum value during a period of time.
LSIOPMIN: stands for the minimum value during a period of time.
LSIOPCUR: stands for the current value.
Impact on System
When the input optical power is excessively high or low, bit errors and the LOF alarm may be
generated in the received signals, which brings impact on the services.

The hardware checks the optical module and then the software converts the check result into
LSIOP to show the input optical power performance of a board.
Related Alarms
Alarm Name
Correlation
IN_PWR_HIGH
It is generated when the optical power input by board is higher than

the upper threshold.
IN_PWR_LOW
It is generated when the optical power input by board is lower than

the lower threshold.
Procedure
Step 1 If no alarm is generated when the current performance value is at least 2 dB higher than the
history performance value and the change in optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH alarm.
Step 2 If no alarm is generated when the current performance value is at least 2 dB lower than the
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
Step 3 If an alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
Issue 02 (2011-10-31)

906
OptiX OSN 8800/6800/3800

6.41 LSOOP
Description
Output optical power
It includes:
l
LSOOPMAX: stands for the maximum value during a period of time.
LSOOPMIN: stands for the minimum value during a period of time.
LSOOPCUR: stands for the current value.
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal transmission
of services.

The hardware checks the optical module and then the software converts the check result into
LSOOP value to show the output optical power performance of the laser on a board.
Related Alarms
Alarm Name
Correlation
OUT_PWR_HIGH
It is generated when the optical power output by a board is higher than

the upper threshold.
OUT_PWR_LOW
It is generated when the optical power output by a board is lower than

the lower threshold.
TF
It is generated when the optical power output by a board is 1 dB lower

than the lower threshold.
Procedure
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
history performance value and the change of optical power is not caused by normal operations
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
Step 3 If an alarm is generated, see the Related Alarms.
----End
Issue 02 (2011-10-31)

907
OptiX OSN 8800/6800/3800

Related Information
None
6.42 LSTMP
Description
Laser temperature
It includes:
l
LSTMPMAX: stands for the maximum value during a period of time.
LSTMPMIN: stands for the minimum value during a period of time.
LSTMPCUR: stands for the current value.
Impact on System
None

Normally, the laser temperature is a stable value obtained by software through calculating the
result output by the temperature detecting circuit in the laser.
Related Alarms
Alarm Name
Correlation
TEM_HA
Laser temperature is excessively high. This alarm is generated when

the laser temperature is higher than the upper threshold of the laser
temperature.
TEM_LA
Laser temperature is excessively low. This alarm is generated when

the laser temperature is lower than the upper threshold of the laser
temperature.
Procedure
Step 1 If the TEM_HA or TEM_LA alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
Issue 02 (2011-10-31)

908
OptiX OSN 8800/6800/3800

6.43 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, determine the cause and
solve the problem timely to avoid any alarm to ensure the signal transmission quality.

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name
Correlation
B2_EXC
Multiplex section (B2) excessive errors alarm. The alarm is generated

when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD
Multiplex section (B2) signal degraded alarm. The alarm is generated

when the B2 bit errors in the multiplex section exceed the signal
degrade (SD) threshold.
MS_AIS
Multiplex section alarm indication. The alarm is generated when the

opposite station transmits the MS_AIS signals or the receive part of
the local station is faulty.
MS_CROSSTR
Multiplex section performance exceeds the threshold. The alarm is

generated when the performance module reports the threshold
crossing of the performance events in the multiplex section.
R_LOF
Loss of frame on receiving line. This alarm is generated when the

frame alignment processing is out of frame (OOF) in consecutive 3
ms.
Procedure
Step 1 Refer to the method of handling the B2_EXC.
----End
Related Information
None
Issue 02 (2011-10-31)

909
OptiX OSN 8800/6800/3800

6.44 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Determine the cause and solve the problem
timely because the bit errors severely affect the signal transmission quality. In addition, the
B2_EXC and B2_SD alarms may be generated.

The multiplex section errors are detected by checking the B2 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. The consecutive
severely errored second means the severely errored second appears consecutively, and it is
accompanied by the B2_EXC alarm. It might result in service interruption.
Related Alarms
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

MS_CROSSTR

R_LOF

ms.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

910
OptiX OSN 8800/6800/3800

6.45 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, determine
quality.

The multiplex section errors are detected by checking the B2 byte. The MS errored second means
there are more than one error block transmitted in this second.
Related Alarms
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

MS_CROSSTR

R_LOF

ms.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

911
OptiX OSN 8800/6800/3800

6.46 MSFEBBE
Description
MS far end background block error
Impact on System
If bit errors are generated in the services on a far-end NE but no related alarm is reported on the
opposite NE, there is no impact on the system. You, however, need to determine the cause and

The multiplex section errors are detected by checking the B2 byte. The background block error
means there are one or more data blocks containing error bit during transmission. And the far
end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
MS_RDI
Multiplex section remote defect indication alarm. The alarm is

generated at the local station if the opposite station back transmits the
information through overhead when the WDM-side receive part of
the opposite station is faulty.
Procedure
Step 1 Refer to the method of handling the MS_RDI.
----End
Related Information
None
6.47 MSFECSES
Description
MS far end consecutive severely errored second
Impact on System
Issue 02 (2011-10-31)

912
OptiX OSN 8800/6800/3800


severely errored second means the severely errored second appears consecutively, and it is
accompanied by the B2_EXE alarm. It might result in service interruption. The far end
consecutive severely errored second refers to the consecutive severely errored second detected
at the opposite end.
Related Alarms
Alarm Name
Correlation
MS_RDI

Procedure
----End
Related Information
None
6.48 MSFEES
Description
MS far end errored second
Impact on System

The multiplex section errors are detected by checking the B2 byte. An errored second contains
more than one error block. And the far end errored second refers to the errored second detected
Issue 02 (2011-10-31)

913
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
MS_RDI

Procedure
----End
Related Information
None
6.49 MSFESES
Description
MS far end severely errored second
Impact on System

second, there is at least one defect or 30% of data blocks are error blocks. And the far end severely
errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
MS_RDI


914
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.50 MSFEUAS
Description
MS far end unavailable second
Impact on System
solve the problem in a timely manner to avoid any alarm, thus to ensure the signal transmission
quality.

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds
last for more than 10 seconds, the unavailable second starts from the beginning of the 11th
second, and the former 10 severely errored seconds are counted as unavailable. If the severely
errored second disappears for more than 10 seconds, the available time starts from the beginning
of the 11th second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name
Correlation
MS_RDI

Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

915
OptiX OSN 8800/6800/3800

6.51 MSSES
Description
MS severely errored second
Impact on System

second, there is at least one defect or 30% of data blocks are error blocks.
Related Alarms
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

MS_CROSSTR

R_LOF

ms.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

916
OptiX OSN 8800/6800/3800

6.52 MSUAS
Description
MS unavailable second
Impact on System
There are bit errors in the services. Determine the cause and solve the problem timely to ensure

The multiplex section errors are detected by checking the B2 byte. If the severely errored seconds
last for more than 10 seconds, the unavailable second starts from the beginning of the eleventh
second, and the former 10 severely errored seconds are counted as unavailable. If the severely
errored second disappears for more than 10 seconds, the available time starts from the beginning
of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
B2_EXC

B2_SD

MS_AIS

MS_CROSSTR

R_LOS
Loss of signal on receiving line. This alarm is generated when the

receive side receives no signals.
MS_RDI

MS_REI
Multiplex section remote error indication. The alarm is generated

when the remote end detects the bit error block.

917
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.53 ODU2PMBIP8
Description
ODU PM section BIP8
Impact on System
quality.

This performance event shows the number of errors that a board with an OTN interface detects
in path monitoring through the BIP8 check. Normally, the performance value should be zero.
Related Alarms
Alarm Name
Correlation
PM_BIP8_OVER
Bit interleaved parity (BIP) in the PM section of the ODU layer

exceeds the upper threshold. The alarm is generated when the number
of BIP8 bit errors of the PM section on the optical channel data unit
layer exceeds the upper threshold.
PM_BIP8_SD
BIP in the PM section of the ODU layer degrades. The alarm is

generated when the number of BIP8 bit errors of the PM section on
the optical channel data unit layer exceeds the degrade threshold.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

918
OptiX OSN 8800/6800/3800

6.54 ODUk_PM_BBE
Description
ODU PM section background block error
Impact on System
There are bit errors in the services. If the number of block errors increases, determine the cause
and solve the problem timely to avoid any alarm to ensure the signal transmission quality.

ODU PM section errors are detected by checking the received parity bits. The background block
error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
Bit interleaved parity (BIP) in the PM section of the ODU layer

exceeds the upper threshold. The alarm is generated when the number
of BIP8 bit errors of the PM section on the optical channel data unit
layer exceeds the upper threshold.
ODUk_PM_DEG
Bit interleaved parity signal in the PM section of the ODU layer

degrades. The alarm is generated when the number of BIP8 bit errors
of the PM section of the ODU layer exceeds the degrade threshold.
Procedure
Step 1 Refer to the method of handling the ODUk_PM_EXC or ODUk_PM_DEG.
----End
Related Information
None
6.55 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Issue 02 (2011-10-31)

919
OptiX OSN 8800/6800/3800

Impact on System
When the value is not 0, it indicates that there are bit errors in the services. When the value is
large, determine the cause and solve the problem timely to avoid any alarm to ensure the signal
transmission quality.

ODU PM section background block errors are detected by checking the received parity bits. The
background block error refers to a data block where at least one bit error is generated during the
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODU layer PM section BIP exceeds the upper threshold. The alarm
is generated when the number of BIP8 bit errors of the PM section on
the optical channel data unit layer exceeds the upper threshold.
ODUk_PM_DEG

of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.56 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System
Issue 02 (2011-10-31)

920
OptiX OSN 8800/6800/3800


ODU PM section errors are detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.57 ODUk_PM_FEBBE
Description
ODU PM section far end background block error
Impact on System

ODU PM section errors are detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
ODUk_PM_BDI
ODU PM section backward defect indication.

921
OptiX OSN 8800/6800/3800

Procedure
Step 1 Refer to the method of handling the ODUk_PM_BDI.
----End
Related Information
None
6.58 ODUk_PM_FEBBER
Description
ODU PM section ratio of far end background block error
Impact on System

ODU PM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the ODU PM section refers to the ratio of the
number of background block errors of the ODU PM section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second]. And the ratio of far end background block error refers to the ratio
of background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

922
OptiX OSN 8800/6800/3800

6.59 ODUk_PM_FEES
Description
ODU PM section far end errored second
Impact on System

ODU PM section error is detected by checking the received parity bit. An errored second contains
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
6.60 ODUk_PM_FESES
Description
ODU PM section far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. If the number of block errors increases,
determine the cause and solve the problem timely to avoid any alarm to ensure the signal
Issue 02 (2011-10-31)

923
OptiX OSN 8800/6800/3800


Errors are detected by checking the received parity bit. During a severely errored second, there
is at least one defect or 30% of data blocks are error blocks. The consecutive severely errored
second means the severely errored second appears consecutively. It might result in the
interruption of the service that shares a fiber link with the supervisory channel. And the far end
severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
6.61 ODUk_PM_FESESR
Description
ODU PM section ratio of far end severely errored second
Impact on System

Bit errors are detected by checking the received parity bits. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. Severely errored second (SES)
ratio refers to the ratio of SES count in a certain period of time to the total available time. Far
end severely errored second ratio refers to the ratio of errored seconds that are detected at the
opposite end.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
ODUk_PM_BDI

924
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.62 ODUk_PM_FEUAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services on a far-end NE. The services may be affected.

If the severely errored seconds last for more than 10 seconds, the unavailable second starts from
the beginning of the eleventh second, and the former 10 severely errored seconds are counted
as unavailable. If the severely errored second disappears for more than 10 seconds, the available
time starts from the beginning of the eleventh second, and the former 10 seconds are counted as
available. And the far end unavailable second refers to the unavailable second detected at the
opposite end.
Related Alarms
Alarm Name
Correlation
ODUk_PM_BDI
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

925
OptiX OSN 8800/6800/3800

6.63 ODUk_PM_SES
Description
ODU PM section severely errored second
Impact on System
There are bit errors in services. Determine the cause and solve the problem timely because the
bit errors have affected the signal transmission quality.

ODU PM Section error is detected by checking the received parity bit. During a severely errored
severely errored second means the severely errored second appears consecutively, it might result
in the interruption of the service that shares a fiber link with the supervisory channel.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
is generated when the number of BIP8 bit errors of the PM section of
ODUk_PM_DEG
Optical channel data unit layer, path monitoring section bit

interleaved parity signal degraded. The alarm is generated when the
number of BIP8 bit errors of the PM section of the optical channel
data unit layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.64 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Issue 02 (2011-10-31)

926
OptiX OSN 8800/6800/3800

Impact on System
There are bit errors in the services. Determine the cause and solve the problem timely because
the bit errors have affected the signal transmission quality.

ratio refers to the ratio of SES count in a certain period of time to the total available time.
Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.65 ODUk_PM_UAS
Description
ODU PM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

available.
Issue 02 (2011-10-31)

927
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
ODUk_PM_EXC
ODUk_PM_DEG

number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.66 ODUk_TCMn_BBE
Description
ODUk TCMn section background block error
Impact on System
and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal

ODUk TCMn section errors are detected by checking the received parity bits. The background
block error means there are one or more data blocks containing error bits during transmission.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
ODUk_TCMn_DEG
ODU TCMn burst-mode signal degradation.
ODUk_TCMn_EXC
ODU TCMn Poisson-mode excessive bit errors.

928
OptiX OSN 8800/6800/3800

Procedure
Step 1 On the U2000, check whether there are a great amount of BIP8 bit errors of the TCM section in
the input signals on the client side. If yes, rectify the fault on the client-side equipment.
Step 2 If the performance keeps deteriorating, see the handling procedure for the
ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.67 ODUk_TCMn_BBER
Description
ODUk TCMn section ratio of background block error
Impact on System
large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus to
ensure the signal transmission quality.

ODUk TCMn section background block errors are detected by checking the received parity bits.
The background block error refers to a data block where at least one bit error is generated during
the transmission. Background block error ratio of the ODUk TCMn section refers to the ratio of
the number of background block errors of the ODUk TCMn section to the number of all blocks
minus the number of blocks during the unavailable time and SES period. BBER = cBBE/[(PUAS-cSES) x blocks per second].
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_DEG
ODUk_TCMn_EXC
Procedure
Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Issue 02 (2011-10-31)

929
OptiX OSN 8800/6800/3800

Related Information
None
6.68 ODUk_TCMn_BIAES
Description
ODU TCMn section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Determine the cause and solve the problem in a timely
manner to ensure the signal transmission quality.

ODU TCMn section backward introducing alignment errored seconds are detected by checking
the backward input frame alignment bits. Backward incoming alignment errored second refers
to the second where more than one backward input frame alignment errors are generated.
Related Alarms
None
Procedure
Step 1 On the U2000, check whether the input optical power of the optical interface is within the normal
range. For the optical power specifications of the board, see the Product Description. If the input
optical power is abnormal, see the methods for handling the IN_PWR_HIGH and
IN_PWR_LOW alarms.
Step 2 If the performance event persists, see the description on bit error fault handling in the
Troubleshooting.
----End
Related Information
None
6.69 ODUk_TCMn_ES
Description
ODUk TCMn section errored second
Issue 02 (2011-10-31)

930
OptiX OSN 8800/6800/3800

Impact on System

ODUk TCMn section error is detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_DEG
ODUk_TCMn_EXC
Procedure
Step 2 If the performance event persists, see the handling procedure for the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.70 ODUk_TCMn_FEBBE
Description
ODUk TCMn section far end background block error
Impact on System
quality.

Far end background block of the ODUk TCMn section is detected by checking the received
backward error bits. The background block error means there are one or more data blocks
containing error bit during transmission. And the far end background block error refers to the
Issue 02 (2011-10-31)

931
OptiX OSN 8800/6800/3800

background block error detected at the opposite end. The backward error bit means the inserted
indication to the local end after the background block error is detected at the opposite end.
Related Alarms
None
Procedure
IN_PWR_LOW alarms.
Troubleshooting.
----End
Related Information
None
6.71 ODUk_TCMn_FEBBER
Description
ODUk TCMn section ratio of far end background block error
Impact on System

Background block errors are detected by checking the received parity bits. The background block
error refers to a data block where at least one bit error is generated during the transmission. Far
end background block error ratio of the ODUk TCMn section refers to the ratio of the number
of far end background block errors of the ODUk TCMn section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second].
Related Alarms
None
Procedure
Issue 02 (2011-10-31)

932
OptiX OSN 8800/6800/3800

IN_PWR_LOW alarms.
Troubleshooting.
----End
6.72 ODUk_TCMn_FEES
Description
ODUk TCMn section far end errored second
Impact on System

ODUk backward error indication of the TCMn section is determined by the BEI that is inserted
at the far end. Far end errored second refers to the second where the checked signals contain at
least one block error at the far end.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None
6.73 ODUk_TCMn_FESES
Description
ODUk TCMn section far end severely errored second
Impact on System
Issue 02 (2011-10-31)

933
OptiX OSN 8800/6800/3800


ODUk far end severely errored second of the TCMn section is determined by the BEI that is
inserted at the far end. During a far end severely errored second, there is at least one defect or
30% of data blocks are error blocks. The fiber line may be faulty.
Related Alarms
None
Procedure
IN_PWR_LOW alarms.
Troubleshooting.
----End
Related Information
None
6.74 ODUk_TCMn_FESESR
Description
ODUk TCMn section ratio of far end severely errored second
Impact on System
There are bit errors in the services on a far-end NE. Determine the cause and solve the problem
in a timely manner, thus to ensure the signal transmission quality.

During a far end severely errored second, there is at least one defect or 30% of data blocks are
error blocks. FESESR refers to the ratio of the FESES count in a certain period to the total
available time.
Related Alarms
None
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_SESR.
----End
Issue 02 (2011-10-31)

934
OptiX OSN 8800/6800/3800

Related Information
None
6.75 ODUk_TCMn_FEUAS
Description
ODUk TCMn section unavailable second
Impact on System
The far-end services are not available.

Unavailable seconds are generated when the number of bit errors at the far end is large.
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_BDI
ODU TCMn backward defect indication.
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_BDI.
----End
Related Information
None
6.76 ODUk_TCMn_IAES
Description
ODUk TCMn section introducing alignment errored second
Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

There is the OTUk_OOF or OTUk_LOF alarm at the upstream station.
Issue 02 (2011-10-31)

935
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
OTUk_LOF
OTUk frame loss. The upstream station detects the LOF alarm and
then inserts IAE. The local station reports ODU1_TCMn_IAES.
Procedure
Step 1 Refer to the method of handling the OTUk_LOF.
----End
Related Information
None
6.77 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System
because the bit errors have affected the signal transmission quality.

It is obtained by calculating the BIP-8 of ODUk TCMn section. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. The fiber line may be faulty.
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_DEG
ODUk_TCMn_EXC
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Issue 02 (2011-10-31)

936
OptiX OSN 8800/6800/3800

Related Information
None
6.78 ODUk_TCMn_SESR
Description
ODUk TCMn section ratio of severely errored second
Impact on System

It is obtained by calculating the BIP-8 of ODU1 TCMn section. During a severely errored second,
there is at least one defect or 30% of data blocks are error blocks. The consecutive severely
errored second means the severely errored second appears consecutively. SESR refers to the
ratio of the SES count in a specified period to the total available time.
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_DEG
ODUk_TCMn_EXC
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC.
----End
Related Information
None
6.79 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System
Issue 02 (2011-10-31)

937
OptiX OSN 8800/6800/3800


the beginning of the 11th second, and the former 10 severely errored seconds are counted as
unavailable. If the severely errored second disappears for more than 10 seconds, the available
time starts from the beginning of the 11th second, and the former 10 seconds are counted as
available.
Related Alarms
Alarm Name
Correlation
ODUk_TCMn_DEG
ODUk_TCMn_EXC
Procedure
Step 1 Refer to the method of handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC
----End
Related Information
None
6.80 OOPRL
Description
Optical Output Power Return Loss
It includes:
l
OOPRLMAX: maximum value of the optical output power return loss within a time period
OOPRLMIN: minimum value of the optical output power return loss within a time period
OOPRLCUR: current value of the optical output power return loss
Impact on System
Services may be interrupted.

The fiber near the Raman board is broken, over-bent, or pressed, or the fiber connector is unclean
or installed incorrectly.
Issue 02 (2011-10-31)

938
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
RL_CRITICAL_HI
This alarm is generated when the return loss is higher than the upper
threshold of the return loss alarm.
RL_CRITICAL_LO
W
This alarm is generated when the return loss is lower than the lower
threshold of the return loss alarm.
Procedure
Step 1 Refer to the method of handling the RL_CRITICAL_HI or RL_CRITICAL_LOW.
----End
Related Information
None
6.81 OSC_BBE
Description
OSC Path Section Background Block Error.
Impact on System
There are bit errors in the OSC signals. If the number of block errors increases, determine the
cause and solve the problem in a timely manner to avoid any alarm, thus to ensure the signal

The background block error means there are one or more data blocks containing error bits during
transmission.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
Issue 02 (2011-10-31)

939
OptiX OSN 8800/6800/3800

6.82 OSC_BBER
Description
OSC Path Section Ratio of Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the OSC signals. When the value
is large, determine the cause and solve the problem in a timely manner to avoid any alarm, thus
to ensure the signal transmission quality.

The background block error means there are one or more data blocks containing error bits during
transmission. Background block error ratio refers to the ratio of the number of background block
errors to the number of all blocks minus the number of blocks during the unavailable time and
SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second].
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.83 OSC_BIAES
Description
OSC Path Backward Incoming Alignment Errored Second.
Impact on System
There are errors in frame alignment. Determine the cause and solve the problem in a timely
manner to ensure the signal transmission quality.

Backward incoming alignment errored second refers to the second where more than one
backward input frame alignment errors are generated.
Issue 02 (2011-10-31)

940
OptiX OSN 8800/6800/3800

Related Alarms
None
Procedure
Troubleshooting.
----End
Related Information
None
6.84 OSC_ES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are bit errors in the OSC signals. If the number of bit errors increases, determine the cause

An errored second contains more than one error block.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.85 OSC_FEBBE
Description
OSC Path Far End Background Block Error.
Issue 02 (2011-10-31)

941
OptiX OSN 8800/6800/3800

Impact on System
If bit errors are generated in the signals on a far-end NE but no related alarm is reported on the
quality.

OSC Path error is detected by checking the received parity bit. The background block error
means there are one or more data blocks containing error bit during transmission. And the far
end background block error refers to the background block error detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.86 OSC_FEBBER
Description
Osc Path Section Ratio of Far End Background Block Error.
Impact on System
When the value is not 0, it indicates that there are bit errors in the signalss. When the value is

The background block error refers to a data block where at least one bit error is generated during
the transmission. Background block error ratio refers to the ratio of the number of background
block errors to the number of all blocks minus the number of blocks during the unavailable time
and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks per second]. And the ratio of far end
background block error refers to the ratio of background block error detected at the opposite
end.
Related Alarms
None
Issue 02 (2011-10-31)

942
OptiX OSN 8800/6800/3800

Procedure
Step 1 None
----End
Related Information
None
6.87 OSC_FEES
Description
OSC Path Section Far End Background Block Error.
Impact on System
There are bit errors in the signals on a far-end NE. If the number of block errors increases,

OSC path section error is detected by checking the received parity bit. An errored second contains
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.88 OSC_FESES
Description
OSC Path Section Far End Severely Errored Second.
Issue 02 (2011-10-31)

943
OptiX OSN 8800/6800/3800

Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.

Bit errors are detected by checking the received parity bit. During a severely errored second,
errored second means the severely errored second appears consecutively. And the far end
severely errored second refers to the severely errored second detected at the opposite end.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.89 OSC_FESESR
Description
OSC Path Section Ratio of Far End Severely Errored Second.
Impact on System
There are bit errors in the signals on a far-end NE. Determine the cause and solve the problem

far end.
Related Alarms
None
Issue 02 (2011-10-31)

944
OptiX OSN 8800/6800/3800

Procedure
Step 1 None
----End
Related Information
None
6.90 OSC_FEUAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.

opposite end.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.91 OSC_IAES
Description
OSC Path Section Errored Second.
Issue 02 (2011-10-31)

945
OptiX OSN 8800/6800/3800

Impact on System
There are framing errors in the upstream signals and bit errors are generated in the system.

None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.92 OSC_SES
Description
OSC Path Section Severely Errored Second.
Impact on System
There are severely errored second in the OSC signals. Determine the cause and solve the problem

Error is detected by checking the received parity bit. During a severely errored second, there is
at least one defect or 30% of data blocks are error blocks.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
Issue 02 (2011-10-31)

946
OptiX OSN 8800/6800/3800

6.93 OSC_SESR
Description
OSC Path Section Ratio of Severely Errored Second.
Impact on System
There are severely errored second in the signals. Determine the cause and solve the problem in
a timely manner because the bit errors have affected the signal transmission quality.

errored second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel. Severely errored
second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available
time.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.94 OSC_UAS
Description
OSC Path Section Unavailable Second.
Impact on System
There are bit errors in the signals and the bit errors have affected the signal transmission quality.

Issue 02 (2011-10-31)

947
OptiX OSN 8800/6800/3800

available.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.95 OSPICCV
Description
The OSPICCV indicates the value of the cooling current of the laser.
It includes:
l
OSPICCVMAX: stands for the maximum value during a period of time.
OSPICCVMIN: stands for the minimum value during a period of time.
OSPICCVCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the cooling current of
the laser is excessively high or low, however, the laser may work abnormally. If the cooling
current is within the normal range, you do not need to take any action.

l
The performance event records the current value of the cooling current.
The cooling current is applied to control the temperature of the optical module. In the case
of excessively low temperature, the cooling current is increased to make the temperature
higher. In the case of excessively high temperature, the cooling current is decreased to make
the temperature lower.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
LSR_COOL_ALM
When the cooling current of the laser is beyond the specified

range, this alarm is generated.

948
OptiX OSN 8800/6800/3800

Procedure
Step 1 Refer to the method of handling the LSR_COOL_ALM alarm.
----End
Related Information
None
6.96 OSPITMP
Performance Event Meaning
The OSPITMP indicates the value of the temperature in the tube core of the laser.
It includes:
l
OSPITMPMAX: stands for the maximum value during a period of time.
OSPITMPMIN: stands for the minimum value during a period of time.
OSPITMPCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the temperature in the
tube core of the laser is excessively high or low; however, the laser may work abnormally. As
a result, the services may be interrupted. If the temperature is within the normal range, you do
not need to take any action.

The performance event is adopted to monitor the current temperature in the tube core of the
laser, and to know the current temperature of the laser.
Related Alarms
Alarm Name
Correlation
TEM_HA
When the temperature of the laser is higher than the upper

TEM_LA
When the temperature of the laser is less than the lower

Procedure
Step 1 Refer to the method of handling the TEM_HA and TEM_LA alarms.
----End
Issue 02 (2011-10-31)

949
OptiX OSN 8800/6800/3800

Related Information
None
6.97 OTU2SMBIP8
Description
OTU SM section BIP8
Impact on System
quality.

This performance event shows the number of errors that a board with an OTN interface detects
in section monitoring through the BIP8 check. In normal cases, it should be 0.
Related Alarms
Alarm Name
Correlation
SM_BIP8_OVER
OTU SM section bit interleaved parity exceeds threshold. The alarm

is generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the threshold.
SM_BIP8_SD
OTU SM section bit interleaved parity deterioration. The alarm is

generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the degraded threshold.
Procedure
Step 1 If any alarm is generated, use the method of the relevant alarm to clear it.
----End
Related Information
None
6.98 OTUk_BBE
Description
OTU background block error
Issue 02 (2011-10-31)

950
OptiX OSN 8800/6800/3800

Impact on System

OTU errors are detected by checking the received parity bits. The background block error means
there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name
Correlation
OTUk_EXC

OTUk_DEG

generated when the number of BIP8 bit errors of the SM section in
Procedure
Step 1 Refer to the method of handling the OTUk_EXC or OTUk_DEG.
----End
Related Information
None
6.99 OTUk_BBER
Description
OTU ratio of background block error
Impact on System

OTU section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU section refers to the ratio of the number
of background block errors of the OTU section to the number of all blocks minus the number
Issue 02 (2011-10-31)

951
OptiX OSN 8800/6800/3800

of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks
per second].
Related Alarms
Alarm Name
Correlation
OTUk_EXC

is generated when the number of BIP8 bit errors of the SM section in
OTUk_DEG

Procedure
----End
Related Information
None
6.100 OTUk_ES
Description
OTU errored second
Impact on System

OTU error is detected by checking the received parity bit. An errored second contains more than
one error block.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
OTUk_EXC

952
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
OTUk_DEG

Procedure
----End
Related Information
None
6.101 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System

OTU SM section error is detected by checking the received parity bit. The background block
error means there are one or more data blocks containing error bit during transmission. And the
far end background block error refers to the background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
OTU SM section backward defect indication.
Procedure
Step 1 Refer to the method of handling the OTUk_BDI.
----End
Related Information
None
Issue 02 (2011-10-31)

953
OptiX OSN 8800/6800/3800

6.102 OTUk_FEBBER
Description
OTU SM section ratio of far end background block error
Impact on System

OTU SM section background block errors are detected by checking the received parity bits. The
transmission. Background block error ratio of the OTU SM section refers to the ratio of the
number of background block errors of the OTU SM section to the number of all blocks minus
the number of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAScSES) x blocks per second]. And the ratio of far end background block error refers to the ratio
of background block error detected at the opposite end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
6.103 OTUk_FEES
Description
OTU SM section far end errored second
Issue 02 (2011-10-31)

954
OptiX OSN 8800/6800/3800

Impact on System

OTU SM section error is detected by checking the received parity bit. An errored second contains
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
6.104 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System
timely because the bit errors have affected the signal transmission quality.

OTU SM Section error is detected by checking the received parity bit. During a severely errored
severely errored second means the severely errored second appears consecutively, it might result
in the interruption of the service that shares a fiber link with the supervisory channel. And the
far end severely errored second refers to the severely errored second detected at the opposite
end.
Issue 02 (2011-10-31)

955
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
6.105 OTUk_FESESR
Description
OTU SM section ratio of far end severely errored second
Impact on System

far end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Issue 02 (2011-10-31)

956
OptiX OSN 8800/6800/3800

Related Information
None
6.106 OTUk_FEUAS
Description
OTU SM section unavailable second
Impact on System
There are bit errors in the services and the services may be affected.

opposite end.
Related Alarms
Alarm Name
Correlation
OTUk_BDI
Procedure
----End
Related Information
None
6.107 OTUk_SES
Description
OTU severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem
Issue 02 (2011-10-31)

957
OptiX OSN 8800/6800/3800


Error is detected by checking the received parity bit. During a severely errored second, there is
at least one defect or 30% of data blocks are error blocks. The consecutive severely errored
second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel.
Related Alarms
Alarm Name
Correlation
OTUk_EXC

OTUk_DEG

Procedure
----End
Related Information
None
6.108 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Determine the cause and solve the problem

errored second means the severely errored second appears consecutively, it might result in the
interruption of the service that shares a fiber link with the supervisory channel. Severely errored
second (SES) ratio refers to the ratio of SES count in a certain period of time to the total available
time.
Issue 02 (2011-10-31)

958
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
OTUk_EXC

OTUk_DEG

Procedure
----End
Related Information
None
6.109 OTUk_UAS
Description
OTU unavailable second
Impact on System

available.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
OTUk_EXC

959
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
OTUk_DEG

Procedure
----End
Related Information
None
6.110 PCLSOP
Description
Per-channel laser output power, indicating the optical power of a channel of signal monitored
by the spectrum analyzer unit.
It includes:
l
PCLSOPMAX: stands for the maximum value during a period of time.
PCLSOPMIN: stands for the minimum value during a period of time.
PCLSOPCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signal to check
its optical power.
Related Alarms
None
Procedure
Step 1 None
----End
Issue 02 (2011-10-31)

960
OptiX OSN 8800/6800/3800

Related Information
None
6.111 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signal monitored by the spectrum analyzer
unit.
It includes:
l
PCLSSNMAX: stands for the maximum value during a period of time.
PCLSSNMIN: stands for the minimum value during a period of time.
PCLSSNCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the OSNR
of a channel of signal.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.112 PCLSWL
Description
Per-channel central wavelength, indicating the central wavelength of a channel among optical
signals monitored by the spectrum analyzer unit.
It includes:
l
PCLSWLMAX: stands for the maximum value during a period of time.
PCLSWLMIN: stands for the minimum value during a period of time.
Issue 02 (2011-10-31)

961
OptiX OSN 8800/6800/3800

PCLSWLCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signal to check
its central wavelength.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.113 PCLSWLO
Description
Per-channel central wavelength deviation indicates the deviation between the ITU-T standard
wavelength and the wavelength of a channel among optical signals monitored by the spectrum
analyzer unit.
It includes:
l
PCLSWLOMAX: stands for the maximum value during a period of time.
PCLSWLOMIN: stands for the minimum value during a period of time.
PCLSWLOCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the central
wavelength deviation of a channel of signal.
Related Alarms
None
Issue 02 (2011-10-31)

962
OptiX OSN 8800/6800/3800

Procedure
Step 1 None
----End
Related Information
None
6.114 RPL
Description
The RPL indicates the value of the input optical power.
It includes:
l
RPLMAX: stands for the maximum value during a period of time.
RPLMIN: stands for the minimum value during a period of time.
RPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the input optical power
is excessively high, the laser may be damaged. If the input optical power is excessively low, the
laser may fail to detect the signals. You can know the normal range of the input optical power
by querying the specifications for related optical interfaces.

The performance event is adopted to monitor the value of the input optical power of the laser,
and to know the value of the input optical power.
Related Alarms
Alarm Name
Correlation
IN_PWR_LOW
The alarm is generated when the input optical power is lower

than the lower threshold of the input optical power.
IN_PWR_HIGH
The alarm is generated when the input optical power is higher

than the upper threshold of the input optical power.
Procedure
----End
Issue 02 (2011-10-31)

963
OptiX OSN 8800/6800/3800

Related Information
None
6.115 RSBBE
Description
RS background block error
Impact on System

The regenerator section errors are detected by checking the B1 byte. The background block error
means there are one or more data blocks containing error bits during transmission.
Related Alarms
Alarm Name
Correlation
B1_EXC
Regenerator section (B1) excessive errors.

The alarm is generated when the received
signals in SDH frame degrade and the B1 bit
errors in the multiplex section exceed the
threshold.
Procedure
----End
Related Information
None
6.116 RSCSES
Description
RS consecutive severely errored second
Issue 02 (2011-10-31)

964
OptiX OSN 8800/6800/3800

Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored
second, there is at least one defect or 30% of data blocks are error blocks. Consecutive severely
errored seconds (CSES) mean the severely errored seconds appear consecutively, and the CSES
is generally accompanied by the B1_EXC alarm. It might result in service interruption.
Related Alarms
Alarm Name
Correlation
B1_EXC

threshold.
Procedure
----End
Related Information
None
6.117 RSES
Description
Regenerator section (RS) errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. The RS errored second
means that there are more than one error block transmitted in this second.
Issue 02 (2011-10-31)

965
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
B1_EXC

threshold.
Procedure
----End
Related Information
None
6.118 RSOFS
Description
RS out-of-frame second
Impact on System
This alarm indicates that the frame headers cannot be identified in five or more consecutive
frames in the received signals of the line board. The board enters the out-of-frame state. As a
result, the services are unavailable. If the out-of-frame state lasts for 3 ms, the board enters the
loss-of-frame state and the R_LOF alarm is generated.

Out-of-frame (OOF) refers to the loss of framing bytes and the OOF second contains at least
one OOF.
OOF turns to be loss of frame (LOF) if it lasts more than 3 ms.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
R_OOF
Out of frame on receiving line. This alarm is

generated when the headers of consecutive
five frames fail to be detected.

966
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
R_LOF
Loss of frame on receiving line. This alarm is

generated when the frame alignment
processing is in the OOF state in consecutive
3 ms.
Procedure
Step 1 Check whether the fibers are damaged and whether the connectors are properly installed. Clean
the fiber connectors.
Step 2 Check whether the input optical power of the input interface of the board is within the normal
range by using an optical power meter. For the optical power specifications of a certain board,
see the Product Description. If the power is not within the normal range, add proper attenuation
by adding a fix attenuator or a variable optical attenuator (VOA).
----End
Related Information
None
6.119 RSOOF
Description
The RSOOF indicates the count of out-of-frame events in the regenerator section.
Impact on System
When the performance event occurs, the frame alignment bytes are lost. As a result, the services
are interrupted.

The out-of-frame event means that the frame alignment bytes are lost. The RSOOF means that
one or more out-of-frame events occur during transmission. The possible causes of the event are
as follows:
l
The performance of the optical fiber is degraded.
Issue 02 (2011-10-31)

967
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
R_OOF
If more than five consecutive frames cannot be correctly

aligned with the SDH frame header, the alarm is reported.
R_LOF
When the R_OOF alarm lasts for 3 ms, the alarm is reported.
Procedure
Step 1 Refer to the method of handling the R_OOF and R_LOF.
----End
Related Information
None
6.120 RSSES
Description
RS severely errored second
Impact on System

The regenerator section errors are detected by checking the B1 byte. During a severely errored
second, there is at least one defect or 30% of blocks are error blocks.
Related Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
B1_EXC

threshold.

968
OptiX OSN 8800/6800/3800

Procedure
----End
Related Information
None
6.121 RSUAS
Description
RS unavailable second
Impact on System

The regenerator section errors are detected by checking the B1 byte. If the severely errored
seconds last for more than 10 seconds, the unavailable second starts from the beginning of the
eleventh second, and the former 10 severely errored seconds are counted as unavailable. If the
severely errored second disappears for more than 10 seconds, the available time starts from the
beginning of the eleventh second, and the former 10 seconds are counted as available.
Related Alarms
Alarm Name
Correlation
B1_EXC

threshold.
Procedure
----End
Related Information
None
Issue 02 (2011-10-31)

969
OptiX OSN 8800/6800/3800

6.122 SUMIOP
Description
Total input optical power
It includes:
l
SUMIOPMAX: stands for the maximum value during a period of time.
SUMIOPMIN: stands for the minimum value during a period of time.
SUMIOPCUR: stands for the current value.
Impact on System
If the total input optical power is excessively high, the optical modules of the local board and
the downstream board may be damaged. As a result, bit errors are generated in the services or
even the services are interrupted. If the total input optical power is excessively low, the singlewavelength optical signals that are output by the board may be lost. As a result, bit errors are
generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate
the result with software for conversion.
SUMIOP is the total input optical power of demultiplexer and the optical amplifier board.
Related Alarms
Alarm Name
Correlation
IN_PWR_HIGH
It is generated when the input optical power is higher than the upper
threshold. Inaccurate optical power detection or faulty optical module
can cause the input optical power higher than the upper threshold.
IN_PWR_LOW
It is generated when the optical power input by board is lower than

the lower threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power lower than the lower
threshold.
SUM_INPWR_HI
It is generated when the detected total input optical power is higher

than the upper threshold.
SUM_INPWR_LO
W
It is generated when the detected total input optical power is lower

than the lower threshold.
Procedure
Issue 02 (2011-10-31)

970
OptiX OSN 8800/6800/3800

(such as expansion or upgrade), see the procedure for handling the IN_PWR_HIGH or
SUM_INPWR_HI alarm.
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW or
SUM_INPWR_LOW alarm.
----End
Related Information
The board types that are supported by the input power alarm are different from the board types
that are supported by the total input power alarm.
6.123 SUMOOP
Description
Total output optical power
It includes:
l
SUMOOPMAX: stands for the maximum value during a period of time.
SUMOOPMIN: stands for the minimum value during a period of time.
SUMOOPCUR: stands for the current value.
Impact on System
The total output power brings impact on the services. If the total output power is excessively
high, the input optical power of the downstream board may be excessively high. As a result, bit
errors are generated in the services or even the services are interrupted. In addition, the receiver
module of the OTU at the downstream station may be damaged. If the total output power is
excessively low, the input optical power of the downstream board may be excessively low. As
a result, bit errors are generated in the services or even the services are interrupted.

To obtain this performance event, perform a check using the check circuit, and then calculate
the result with software for conversion.
SUMOOP is the total optical power output by the multiplexer and the optical amplifier board.
In a multiplexer unit, the input signals pass the multiplexer and then output the total optical
power through the "OUT" port, while on an amplifier board, the input signals pass the amplifier
and then output the total optical power through the "OUT" port.
Issue 02 (2011-10-31)

971
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
OUT_PWR_HIGH
It is generated when the optical power output by board is higher than

the upper threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power higher than the upper
threshold.
OUT_PWR_LOW
It is generated when the optical power output by board is lower than

the lower threshold. Inaccurate optical power detection or faulty
optical module can cause the input optical power lower than the lower
threshold.
Procedure
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_HIGH alarm.
(such as expansion or upgrade), see the procedure for handling the OUT_PWR_LOW alarm.
----End
Related Information
The board types that are supported by the output power alarm are different from the board types
that are supported by the total output power alarm.
6.124 TLB
Description
The TLB indicates the value of the bias current of the laser.
It includes:
l
TLBMAX: stands for the maximum value during a period of time.
TLBMIN: stands for the minimum value during a period of time.
TLBCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the bias current of the
laser is beyond the normal range, however, the laser fails to work or is going to the end of its
life. As a result, the services are interrupted. If the bias current is within the normal range, you
do not need to take any action.
Issue 02 (2011-10-31)

972
OptiX OSN 8800/6800/3800


The performance event is adopted to monitor the bias of the laser, and to know the value of the
bias current of the laser.
Related Alarms
Alarm Name
Correlation
TF
When the bias current of the laser is beyond the normal

range, the alarm is reported, showing transmission failure of
the laser.
LSR_WILL_DIE
When the bias current of the laser is less than the TF value,
the alarm is reported, indicating that the life of the laser is
going to the end.
Procedure
----End
Related Information
None
6.125 TPL
Description
The TPL indicates the value of the output optical power.
It includes:
l
TPLMAX: stands for the maximum value during a period of time.
TPLMIN: stands for the minimum value during a period of time.
TPLCUR: stands for the current value.
Impact on System
The performance event does not affect the equipment and the system. If the output optical power
of the laser is beyond the normal range, however, the laser fails to work or is going to the end
of its life. As a result, the services are interrupted. If the output optical power is within the normal
range, you do not need to take any action.

The performance event is adopted to monitor the value of the output optical power of the laser,
and to know the current value of the output optical power.
Issue 02 (2011-10-31)

973
OptiX OSN 8800/6800/3800

Related Alarms
Alarm Name
Correlation
TF
When the output optical power is beyond the normal range

and this causes transmission failure of the laser, the alarm is
reported.
LSR_WILL_DIE
When the output optical power is greatly beyond the normal

range, the alarm is reported, indicating that the life of the
laser is going to the end.
Procedure
----End
Related Information
None
6.126 VC3BBE
The VC3BBE is a performance event indicating the VC-3 background block error.

If bit errors occur in the services, determine the cause and solve the problem in a timely manner
to avoid any alarm, and thus to ensure the signal transmission quality. If bit errors exceed the
B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
VC3BBE indicates bit errors detected in a verification and excluding the higher order path
unavailable time and higher order path severely errored second.
External causes:
l
The fiber performance is degraded, and the attenuation of the fiber is excessively high.
The fiber connector is dirty or incorrect.
The equipment is improperly grounded.
There is a strong interference source around the equipment.
Equipment problems:
Issue 02 (2011-10-31)

974
OptiX OSN 8800/6800/3800

The signal attenuation at the receive side of the service board is excessively high, the
transmitting circuit of the opposite end is faulty, or the receiving circuit of the local end is
faulty.
The synchronization performance of the clock is poor.
The cross-connect unit and the service board do not work with each other properly.
The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3 bit errors exceeds the threshold
B3_SD_VC3
Signals degraded (B3)
Procedure
Step 1 Eliminate external causes. For example, the grounding is improper or the operating temperature
is high. The receive optical power of the service board is excessively low or high. In this case,
ground the equipment properly or provide a proper operating environment for the equipment.
For more information about solving the optical power problem, see the 6.114 RPL performance.
Then, check whether bit errors occur on the service boards.
Step 2 If all the service boards of an NE have bit errors, the clock unit might be faulty. In this case,
replace the clock unit.
Step 3 If only a service board reports that bit errors exist, it indicates that the local service board might
be faulty or that the opposite NE or fibers are faulty. Locate the faulty board by using the loopback
method. Then, replace the faulty board.
----End
Reference
None.
6.127 VC3CSES
The VC3CSES is a performance event indicating the VC-3 continuous severely errored second.

B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms
will be generated.
Issue 02 (2011-10-31)

975
OptiX OSN 8800/6800/3800

Possible Causes
When a consecutive VC3CSES sequence is detected, the VC3CSES performance event occurs.
When unavailable time comes or VC3CSES is absent in one second, the VC3CSES sequence
ends.
External causes:
l
Equipment problems:
l
faulty.
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3 bit errors exceed the threshold.
B3_SD_VC3
Signals degraded (B3).
R_LOS
The signal on the receive line side is lost.
R_LOF
The out-of-frame fault occurs on the receiver line side.
MS_AIS
Multiplex section alarm indication.
AU_AIS
AU alarm indication.
AU_LOP
AU pointer loss.
LP_UNEQ_VC3
VC-3 path unequipped.
Procedure
Step 1 Refer to the 6.128 VC3ES.
----End
Reference
None.
Issue 02 (2011-10-31)

976
OptiX OSN 8800/6800/3800

6.128 VC3ES
The VC3ES is a performance event indicating VC-3 errored second.

B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD alarms
will be generated.
Possible Causes
The VC3ES performance event occurs when one or multiple bit error blocks are detected in one
second or, when the R_LOS, R_LOF, and MS_AIS alarms are detected on the optical interface,
or when the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected over the path.
External causes:
l
Equipment problems:
l
faulty.
Relevant Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
The signal on the receiver line side is lost.
R_LOF
The out-of-frame fault occurs on the receive line side.
MS_AIS

977
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
AU_AIS
AU_LOP
AU pointer loss.
LP_UNEQ_VC3
Procedure
Step 1 If the R_LOS/R_LOF alarm is generated, a fiber cut, high attenuation, received overload or
faulty board might exist.
1.
If the receive optical power is overloaded, add an attenuator.
2.
Check whether the optical fiber cables are intact and whether the connectors are clean and
properly connected. Replace the fibers or clean the fiber connectors, if necessary.
3.
If the board is faulty, replace the board.
Step 2 If the MS_AIS alarm is generated:

1.
Check whether the service board at the opposite station is configured with insertion of the
MS_AIS alarm. If yes, cancel the configuration.
2.
Check whether the transmit unit of the service board at the opposite station is faulty. Check
whether the service board reports the MS_AIS alarm by performing self-loop on the fibers.
3.
Check the service board of the local station. Reset or replace the board. Then, check whether
the MS_AIS alarm is cleared.
Step 3 If the AU_AIS alarm is generated:

1.
For the AU_AIS alarm caused by MS_AIS, R_LOS, and R_LOF, analyze the MS_AIS,
R_LOS, and R_LOF alarms to locate the fault.
2.
whether the service board reports the AU_AIS alarm by performing self-loop on the fibers.
If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS
alarm is cleared.
3.
If the service unit of the local station is faulty, replace the SCC board at the local station.
Step 4 If the AU_LOP alarm is generated:

1.
Check whether the service configuration is correct at the local and opposite stations. If not,
reconfigure the service.
2.
Check whether the opposite clock board works normally and whether the cross-connect
unit detects the clock. If the clock board works abnormally, modify the clock configuration
and issue it again.
3.
whether the service board reports the AS_AIS alarm by performing self-loop on the fibers.
If the service board is faulty, reset or replace the board. Then, check whether the AU_AIS
alarm is cleared.
4.
If the service unit of the local station is faulty, replace the SCC board at the local station.
Step 5 If the LP_UNEQ_VC3 alarm is generated:

Issue 02 (2011-10-31)

978
OptiX OSN 8800/6800/3800

1.
Check whether the C2 byte is correctly configured. If not, modify the configuration and
issue it again. If yes, the board is judged as faulty. In this case, replace the faulty board.
Step 6 Refer to the 6.126 VC3BBE.

----End
Reference
None.
6.129 VC3FEBBE
The VC3FEBBE is a performance event indicating the VC-3 far end background block error.

If bit errors occur in the services on a remote NE, determine the cause and solve the problem in
a timely manner to avoid any alarm, and thus to ensure the signal transmission quality.
Possible Causes
VC3FEBBE indicates the returned bit errors excluding the bit errors occurring in the VC3 far
end unavailable time and VC3 far end severely errored seconds.
External causes:
l
station.
Equipment problems:
l
The signal attenuation at the receive side of the service board at the opposite station is
opposite station.
The fan of the opposite equipment becomes faulty.
Issue 02 (2011-10-31)

979
OptiX OSN 8800/6800/3800

Relevant Alarms
Alarm Name
Correlation
LP_RDI_VC3
VC-3 path remote defect indication
Procedure
Step 1 Refer to the 6.126 VC3BBE to handle the NE at the opposite end.
----End
Reference
None.
6.130 VC3FECSES
The VC3FECSES is a performance event indicating the VC-3 far end consecutive severely
errored second.

Possible Causes
When a consecutive VC3FECSES sequence is detected, the VC3FECSES performance event
occurs. When unavailable time comes or VC3FECSES is absent in one second, the VC3FECSES
sequence ends.
External causes:
l
The fiber performance degrades and the attenuation is excessive at the opposite station.
Equipment problems:
l
Issue 02 (2011-10-31)

980
OptiX OSN 8800/6800/3800

opposite station.
Relevant Alarms
Alarm Name
Correlation
LP_RDI_VC3
Procedure
Step 1 Refer to the 6.131 VC3FEES.
----End
Reference
None.
6.131 VC3FEES
The VC3FEES is a performance event indicating the VC-3 far end errored second.

Possible Causes
The VC3FEES performance event occurs when one or multiple bit errors are returned by the G1
byte in one second or when the LP_RDI_VC3 alarm is detected on the path.
External causes:
l
station.
Equipment problems:
Issue 02 (2011-10-31)

981
OptiX OSN 8800/6800/3800

opposite station.
Relevant Alarms
Alarm Name
Correlation
LP_RDI_VC3
Procedure
Step 1 If the LP_RDI_VC3 alarm is generated:
1.
Check whether the service board of the opposite station receives an alarm such as
TU_AIS_VC3, TU_LOP_VC3 and LP_UNEQ_VC3. If yes, first clear the alarm.
2.
If the service board of the opposite station does not receive an alarm such as TU_AIS_VC3,
TU_LOP_VC3 and LP_UNEQ_VC3, or if the local station still reports the LP_RDI_VC3
alarm after the opposite station ends this kind of alarm, check whether the opposite station
or the local station is faulty by looping back the fibers.
3.
If the receive unit of the opposite station is faulty, replace the relevant board.
4.
If the transmit part of the local station is faulty, replace the SCC board.
Step 2 Refer to the 6.129 VC3FEBBE.

----End
Reference
None.
6.132 VC3FESES
The VC3FESES is a performance event indicating the VC-3 far end severely errored second.

Issue 02 (2011-10-31)

982
OptiX OSN 8800/6800/3800

Possible Causes
The VC3FESES performance event occurs when not less than 30% bit errors are contained in
the message returned in one second or at least one severely disturbed period (SDP) occurs. SDP
occurs when the BER of all the continuous blocks in a period of at least four continuous blocks
or 1 ms (select the longer period) is lower than 10-2, or when the LP_RDI_VC3 alarm is
generated.
External causes:
l
station.
Equipment problems:
l
opposite station.
Relevant Alarms
Alarm Name
Correlation
LP_RDI_VC3
Procedure
----End
Reference
None.
6.133 VC3FEUAS
Issue 02 (2011-10-31)

983
OptiX OSN 8800/6800/3800


The VC3FEUAS is a performance event indicating the VC-3 far end unavailable second.

Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
station.
Equipment problems:
l
opposite station.
Relevant Alarms
Alarm Name
Correlation
LP_RDI_VC3
Procedure
----End
Reference
None
Issue 02 (2011-10-31)

984
OptiX OSN 8800/6800/3800

6.134 VC3SES
The VC3SES is a performance event indicating the VC-3 far end severely errored second.

B3 bit error threshold and degrade threshold, the B3_EXC and B3_SD alarms will be generated.
Possible Causes
The VC3SES performance event occurs when not less than 30% bit errors are detected in one
second or at least one severely disturbed period (SDP) occurs. The SDP indicates that the BER
of all the consecutive blocks is not lower than 10-2 or the R_LOS, R_LOF and MS_AIS alarms
are generated in a period of at least four consecutive blocks or i ms (the longer one is selected),
or the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected on the path.
External causes:
l
Equipment problems:
l
faulty.
Relevant Alarms
Issue 02 (2011-10-31)
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF

985
OptiX OSN 8800/6800/3800

Alarm Name
Correlation
MS_AIS
AU_AIS
AU_LOP
AU pointer loss.
LP_UNEQ_VC3
Procedure
----End
Reference
None.
6.135 VC3UAS
The VC3UAS is a performance event indicating the VC-3 unavailable second.

B3 bit error threshold and degrade threshold, the B3_EXC_VC3 and B3_SD_VC3 alarms will
be generated.
Possible Causes
VC3UAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
l
Equipment problems:
Issue 02 (2011-10-31)

986
OptiX OSN 8800/6800/3800

faulty.
Relevant Alarms
Alarm Name
Correlation
B3_EXC_VC3
B3_SD_VC3
R_LOS
R_LOF
MS_AIS
AU_AIS
AU_LOP
AU pointer loss.
LP_UNEQ_VC3
Procedure
----End
Reference
None
6.136 WCV
Description
Pump laser working current, also called pump laser driver current or pump laser bias current.
It includes:
l
WCVMAX: stands for the maximum value during a period of time (in 1 mA).
WCVMIN: stands for the minimum value during a period of time (in 1 mA).
WCVCUR: stands for the current value (in 1 mA).
Issue 02 (2011-10-31)

987
OptiX OSN 8800/6800/3800

Impact on System
When the pump laser works normally, there is no impact on the services. If an alarm is generated,
determine the cause.

WCV indicates the pump laser driver current of an optical amplifier board. The optical amplifier
board amplifies the input signal using the pump laser driven by pump laser working current.
Related Alarms
Alarm Name
Correlation
PUM_BCM_ALM
The board reports this alarm when the detected pump laser driver
current is higher than the threshold due to laser exceptions caused by
laser aging, or over-high/low ambient temperature.
LSR_WILL_DIE
The board reports this alarm when the pump laser driver current is
higher than the termination threshold due to laser aging.
TD
Transmitter degrade alarm. The alarm is generated when the bias

current of the laser exceeds the degrade threshold.
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the handling procedure of the alarm.
Step 2 If the LSR_WILL_DIE alarm is generated, see the handling procedure of the alarm.
Step 3 If the TD alarm is generated, see the handling procedure of the alarm.
----End
Related Information
None
6.137 XCSTMP
Description
Board environmental temperature
It includes:
l
XCSTMPMAX: stands for the maximum value during a period of time.
XCSTMPMIN: stands for the minimum value during a period of time.
XCSTMPCUR: stands for the current value.
Issue 02 (2011-10-31)

988
OptiX OSN 8800/6800/3800

Impact on System
Excessively high or low board temperature might cause faults such as degradation of the board
working performance and bit errors.

This performance event is generated by hardware detecting to show the ambient temperature of
the board.
When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures
are improper, the XCSTEMP event occurs.
Related Alarms
Alarm Name
Correlation
TEMP_OVER
It is generated when the ambient temperature exceeds the threshold.
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the proper handling procedures.
----End
Related Information
None
Issue 02 (2011-10-31)

989
OptiX OSN 8800/6800/3800

7 Event List
Event List
This section list the common events.

Table 7-1 Events regarding APE and EAPE
Name
Level
Description
APE adjust finished
Warning
APE adjustment starts upon an APE

adjustment start command. When the
adjustment is complete, an APE adjust
finished is reported.
APE adjust failed
Critical
When APE adjustment is terminated upon an

APE adjustment stop command issued by the
user or due to other causes, an APE adjust
failed event is reported.
EAPE adjustment result

notification event
Major
When EAPE adjustment is complete, an EAPE

adjustment result notification event is reported
to indicate whether the adjustment is
successful.
EAPE abnormal notification

event
Major
When EAPE adjustment becomes abnormal,

an EAPE abnormal notification event is
reported.
Name
Level
Description
IPA abnormal event
Major
When IPA adjustment is terminated due to a

fault of the laser, an IPA abnormal event is
reported.
Table 7-2 Events regarding IPA
Issue 02 (2011-10-31)

990
OptiX OSN 8800/6800/3800

7 Event List
Table 7-3 Events regarding ROADM

Name
Level
Description
ROADM wave conflict event
Critical
If a passthrough wavelength conflicts with an

add wavelength of the OTU after a wavelength
resource consistency check is started, an
ROADM wavelength conflict event is
reported.
ROADM wave check event
Critical
When the system starts a wavelength resource

consistency check, an ROADM wave check
event is reported.
ROADM wave reconfig event
Critical
When actions such as setting wavelength

blocking and deleting intra-board optical
cross-connections are performed, an ROADM
wave reconfig event is reported.
ROADM power adjust event
Critical
When the optical power equalization

adjustment at an ROADM node is started, an
ROADM power adjust event is reported.
ROADM wave state change

event
Critical
After a wavelength resource consistency

check at an ROADM node is started, the logic
wavelength group of the node is in an idle or
abnormal state. That is, if the node passes the
check, the group returns the idle state; if the
node fails the check, the group enters into the
abnormal state. If the status of the logic
wavelength group changes, an ROADM wave
state change event is reported.
Table 7-4 Events regarding protection
Issue 02 (2011-10-31)
Name
Level
Description
OWSP abnormal event
Major
This event is reported when the optical

wavelength shared protection switching
occurs.
ODUk SPRing abnormal event
Major
This event is reported when an ODUk SPRing

protection switching occurs.
1+1 equipment-level
protection switching event
Critical
This event is reported when a protection

switching occurs on a cross-connect board or
on the system control and communication
(SCC) board.

991
OptiX OSN 8800/6800/3800

7 Event List
Table 7-5 Other events
Issue 02 (2011-10-31)
Name
Level
Description
RMON performance value is

above the upper limit
Minor
This event is automatically reported when the

performance value in the sampling period is
higher than the upper threshold.
RMON module performance

value is lower than the lower
threshold
Minor
In the sampling period, an event indicating

upper threshold crossing occurs. In a new
sampling period, when the sampling value is
less than or is equal to the lower threshold
value, this event is reported.

992
OptiX OSN 8800/6800/3800

8 Event Processing
Event Processing
About This Chapter

This chapter describes information relevant to event handling, including event descriptions,
event attribute, event parameters, impacts of events on the system, event causes, and event
NOTE
In the case of an event, refer to its handling procedure to clear it; if this event persists, contact a customer
service technician of Huawei for troubleshooting.
When you view an event on the network management system, select the event. In the Detail
Description in the Event Details field display the related parameters of the event.
8.1 EAPE abnormal event notification
8.2 EAPE adjustment result event notification
8.3 OWSP abnormal event
8.4 ODUk SPRing abnormal event
8.5 RMON performance value is above the upper limit
8.6 RMON module performance value is lower than the lower threshold
8.7 1+1 Equipment Level Protection Switching Event Report
Issue 02 (2011-10-31)

993
OptiX OSN 8800/6800/3800

8 Event Processing
8.1 EAPE abnormal event notification

Description
An event indicating that the EAPE meets the conditions for adjustment. This event indicates that
the current status of the system allows for EAPE adjustment.
Attribute
Event Severity
Event Type
Major
Equipment
Parameter
Parameter
Description
Parameter 1
Indicates the configuration index number for the

EAPE pair, such as 1.
Parameter 2
Indicates the current pre-correction BER of the

sink OTU.
Parameter 3
Indicates the current input optical power of the

sink OTU (in the unit of 0.1 dBm).
Parameter 4
Indicates the BIP8 bit error status in the SM

section for the sink OTU. When this event is
reported, only the Normal status is present,
indicating that the current bit error is zero.
Impact on System
When this event occurs, the EAPE pair of the system meets the conditions for adjustment. In
this case, starting the adjustment does not affect the services.
Possible Causes
Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the conditions
for adjustment. That is, the input optical power does not cross the threshold, the BIP8 bit error
in the SM section is zero, or the pre-correction BER degrades.
Procedure
l
Issue 02 (2011-10-31)
Cause 1: The system is configured with an EAPE pair and the EAPE pair meets the
conditions for adjustment.
994
OptiX OSN 8800/6800/3800

1.
8 Event Processing
On the U2000, start the EAPE automatic adjustment. For details, refer to the Feature
Description.
----End
Related Information
None
8.2 EAPE adjustment result event notification

Description
An event indicating the end of the EAPE adjustment. When the EAPE adjustment is complete,
the adjustment result event is reported, indicating whether the adjustment is successful or not.
Attribute
Event Severity
Event Type
Major
Equipment
Parameter
Issue 02 (2011-10-31)
Parameter
Description
Parameter 1
Indicates the configuration index number for the

EAPE pair, such as 1.

995
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Description
Parameter 2
Indicates the cause for the end of the adjustment.

The values of the parameter are as follows:
succeed
manual adjust
no balance after adjusting
communication failed
board uninstalled
board type error
board offline
vmux carry error
board response error
system error
adjust ne not found
choice ne not found
condition not meet
choice board not found
no reason
Parameter 3
Indicates the ID of the NE where the adjustment

is successful or fails.
Parameter 4
Indicates the slot number of the board where the

adjustment is successful or fails.
Parameter 5
Indicates the number of the optical interface where

the adjustment is successful or fails.
Parameter 6
Indicates the number of the channel where the

adjustment is successful or fails.
Impact on System
If an adjustment success is reported, the system BER is lowered and the signal transmission
quality is improved.
If an adjustment failure is reported, the signal transmission quality needs to be improved.
Possible Causes
l
Cause 1: The adjustment is successful.
Cause 2: The user manually issues a command to stop the adjustment.
Cause 3: After the adjustment is performed for six times, the pre-correction BER of the
sink OTU does not reach the expected value.
Cause 4: The inter-NE communication fails.
Issue 02 (2011-10-31)

996
OptiX OSN 8800/6800/3800

8 Event Processing
Cause 5: The logical board is not installed.
Cause 6: The board type is incorrect.
Cause 7: The board is not in position.
Cause 8: The attenuation of the board with attenuator is adjusted to the extreme.
Cause 9: The board incorrectly responds to the command.
Cause 10: The system has an error, for example, operation to database fails.
Cause 11: The address of the NE where the adjustment is to be performed cannot be found.
Cause 12: The address of the NE where signals are selectively received cannot be found.
Cause 13: The EAPE pair does not meet the conditions for starting the adjustment. The
start-up conditions are as follows:
The input optical power does not cross the threshold.
The BIP8 value in the SM section is zero.
The pre-correction BER degrades.
Cause 14: The board that selectively receives signals is in an incorrect state.
Cause 15: Other causes.
Cause 1: The adjustment is successful.
Procedure
1.
l
Cause 2: The user manually issues a command to stop the adjustment.

1.
1.
Check whether the pre-correction BER of the sink OTU is lowered.
2.
If yes, proceed with the adjustment.
3.
If the BER is not lowered, the EAPE function does not meet the requirements of the
system. In this case, refer to section "Rectifying Bit Errors" in the Troubleshooting to
handle the BER.
Cause 4: The inter-NE communication fails.
Issue 02 (2011-10-31)
Find the board according to the NE ID and slot number indicated by event parameters
and then install the board or replace the board with one of the correct type.
Cause 8: The attenuation of the board with attenuator is adjusted to the extreme.
1.
On the U2000, check whether NEs involved in the EAPE pair normally communicate
with each other.
Causes 57: The logical board is not installed, or the board type is incorrect, the board is
not in position.
1.
Ignore the event.
Cause 3: After the adjustment is performed for six times, the pre-correction BER of the
sink OTU does not reach the expected value.
1.
l
Ignore the event.
Check whether the attenuation of the board is adjusted to the extreme according to the
NE ID, slot number, optical interface number, and channel number indicated by the
event parameters. If yes, the system cannot continue the EAPE adjustment. In this
case, check whether the optical power of signals is normal. For specifications, refer
to the Product Description.
Cause 9: The board incorrectly responds to the command.

997
OptiX OSN 8800/6800/3800

1.
Reconfigure the EAPE and start another EAPE adjustment. For details, refer to the
Feature Description.
Cause 11 or Cause 12: The address of the NE where the adjustment is to be performed
cannot be found, or the address of the NE where signals are selectively received cannot be
found.
1.
Check the network connection between the NEs, and ensure the connection between
the NEs is correct.
2.
On the U2000, check for the configuration information about the EAPE pair. If there
is no configuration information about the EAPE pair, reconfigure the EAPE pair.
Cause 13: The EAPE pair does not meet the conditions for starting the adjustment.
1.
Find the board according to the NE ID and slot number indicated by event parameters
and query alarms related to the board. Handle the alarms by seeing the Handling
Procedure parts for respective alarms.
Cause 10 or Cause 15: The system has an error, or other causes.

1.
8 Event Processing
Check the parameters such as the input optical power and performance of the sink
board meet the conditions for adjustment. If not, the system cannot perform the EAPE
adjustment.
Cause 14: The board that selectively receives signals is in an incorrect state.
1.
Check whether the board that selectively receiving signals is normal. Query alarms
related to this board and handle the alarms by seeing the Handling Procedure parts for
respective alarms.
----End
Related Information
None
8.3 OWSP abnormal event

Description
An event indicating the optical wavelength shared protection. When the optical wavelength
shared protection switching occurs, this event is reported.
Attribute
Event Severity
Event Type
Major
Communication
Parameter
Description
Parameter 1
Indicates the ID of the protection group where the

Parameter
Issue 02 (2011-10-31)

998
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Description
Parameter 2
Indicates the status of the westbound working channel.

SF, SD, normal, unknown, unmonitored
Parameter 3
Indicates the status of the westbound protection channel.

Parameter 4
Indicates the status of the eastbound working channel. The

values of the parameter are as follows:
Parameter 5
Indicates the status of the eastbound protection channel.

Parameter 6
Indicates the switching request of the westbound channel.

no request
response request
exercise switching - ring
WTR - ring switching
manual switching - ring
SD ring switching - working SD protection OK
SD ring switching - working SD protection SD
protection SD
forced switching - ring
SF ring switching - working SF protection OK
SF ring switching - working SF protection SD
SF ring switching - working SD protection SF
SF ring switching - working SF protection SF
protection SF
locked
Parameter 7
Issue 02 (2011-10-31)
Indicates the switching request of the eastbound channel.

The values of the parameter are the same as those of
Parameter 6.

999
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Description
Parameter 8
Indicates current page status. The values of the parameter

are as follows:
stopped
starting
idle
east switching
west switching
full pass-through
APS pass-through
Indicates the indication of westbound remote and local
ends. The values of the parameter are as follows:
Parameter 9
remote-end, near-end
Parameter 10
Indicates the indication of eastbound remote and local

ends. The values of the parameter are as follows:
remote-end, near-end
Impact on System
When the switching occurs in the wavelength shared protection group, the services in the system
are transiently interrupted. When this event is reported, it indicates that the service in the current
working channel of the protection group may be abnormal. In this case, find and rectify the fault.
Possible Causes
l
Cause 1: The current working channel is abnormal.
Cause 2: An external switching command is issued.
Cause 1: The current working channel is abnormal.
Procedure
1.
Find out the cause and rectify the fault according to the alarm information reported in
the current working channel. For details on the operation, see Alarm Processing parts
for respective alarms.
Cause 2: An external switching command is issued.

1.
Ignore the event.
----End
Related Information
None
Issue 02 (2011-10-31)

1000
OptiX OSN 8800/6800/3800

8 Event Processing
8.4 ODUk SPRing abnormal event

Description
An event indicating the ODUk protection. When the switching occurs in the ODUk SPRing
protection group, the working channel is switched to the protection channel, or the protection
channel is switched to the working channel. In this case, this event, indicating that the switching
occurs in the protection group, is reported.
Attribute
Event Severity
Event Type
Major
Communication
Parameter
Parameter
Description
Parameter 1
Indicates the ID of the protection group where this event

occurs.
Parameter 2
Indicates the current status of the westbound working

channel. The values of the parameter are as follows:
Parameter 3
Indicates the current status of the westbound protection

channel. The values of the parameter are the same as those
of Parameter 2.
Parameter 4
Indicates the current status of the eastbound working

of Parameter 2.
Parameter 5
Indicates the current status of the eastbound protection

of Parameter 2.
Parameter 6
Indicates the current page of the protection group. The

values of the parameter are as follows:
stopped
starting
idle
east switching
west switching
full pass-through
APS pass-through
Issue 02 (2011-10-31)

1001
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Description
Parameter 7
Indicates the switching request of the westbound channel

of the protection group. The values of the parameter are
as follows:
no req
exercise sw
WTR - ring sw
manual sw
SD sw - work SD pro OK
SD sw - work SD pro SD
pro SD
forced sw
SF sw - work SF pro OK
SF sw - work SF pro SD
SF sw - work SD pro SF
SF sw - work SF pro SF
pro SF
locked
Parameter 8
Indicates the switching request of eastbound channel of

the protection group. The values of the parameter are the
same as those of Parameter 7.
Parameter 9
Indicates the westbound remote and local indication, and

indicates whether the local station is the initiating end of
the switching. The values of the parameter are as follows:
remote local station as the responding end
near local station as the initiating end
Parameter 10
Indicates the eastbound remote and local indication, and

indicates whether the local station is the initiating end of
the switching. The values of the parameter are as those of
Parameter 9.
Impact on System
When the switching occurs in the ODUk SPRing protection group, the service is transiently
interrupted.
After this event is reported, if the ODUk SPRing protection group is currently in the switching
page, it indicates that the service in the westbound working channel or eastbound working
channel in the ODUk SPRing protection group is abnormal. In this case, find and rectify the
fault.
Issue 02 (2011-10-31)

1002
OptiX OSN 8800/6800/3800

8 Event Processing
Possible Causes
l
Cause 1: The user issues an external switching command, such as forced switching or
manual switching. Hence, in the ODUk SPRing protection group, the working channel in
a direction is switched to the protection channel in another direction, or the protection
channel in a direction is switched to the working channel in another direction. In this case,
this event is reported.
Cause 2: When the service in the working channel of the ODUk SPRing protection group
is abnormal, the service is automatically switched to the protection channel. When the
service in the protection channel is abnormal, the service is automatically switched to the
working channel. Hence, this event is reported.
Cause 3: If the service in the working channel of the ODUk SPRing is restored, after the
WTR time elapses, the service in the protection channel is automatically switched to the
working channel. Hence, this event is reported.
Cause 1 or Cause 3: The user issues an external switching command, or after the WTR time
elapses, the service in the protection channel is automatically switched to the working
channel.
Procedure
1.
l
Ignore the event.
Cause 2: The service is automatically switched to the protection channel

1.
On the U2000, query the related switching alarms. For details, see Handling Procedure
parts for respective alarms.
----End
Related Information
None
8.5 RMON performance value is above the upper limit

Description
An event indicating that the performance value of the RMON module exceeds the upper
threshold. When the performance value in the sampling period is higher than the upper threshold,
this event is automatically reported. For example, when the performance value of collisions
exceeds the upper threshold, the event is reported.
Attribute
Issue 02 (2011-10-31)
Event Severity
Event Type
Minor
Communication

1003
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Parameter
Description
Parameter 1
Indicates the slot ID, port number and channel number,

such as 1-LOG-2(ETHER):1.
Parameter 2
Indicates the performance event of threshold crossing.

Drop Events
Fragments
Jabbers
Collisions
Bad Octets Received
Alignment Errors
FCS Errors
Late Collisions
Excessive Collisions
Deferred Transmissions
Carrier Sense Errors
Drop Events at Transmission Direction
Parameter 3
Indicates the performance value.
Parameter 4
Indicates the higher threshold value.
Impact on System
The quality of the Ethernet service is degraded, or even the services in the system are interrupted.
Possible Causes
l
Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits
the data packets.
Cause 2: The working modes of the ports at the local and opposite ends mismatch.
Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
Cause 4: The optical fiber is damaged or the fiber connector is untidy.
Issue 02 (2011-10-31)

1004
OptiX OSN 8800/6800/3800

8 Event Processing
Procedure
l
Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits
the data packets.
1.
Cause 2: The working modes of the ports at the local and opposite ends mismatch.
1.
Check whether the received optical power of the interface is within the normal range
by using the U2000. For the optical power specifications of a specific board, see the
Product Description. If the optical power is not within the normal range, takes
handling measures according to the handling method of the IN_PWR_HIGH or
IN_PWR_LOW alarm.
Cause 4: The optical fiber is damaged or the fiber connector is untidy.

1.
On the U2000, query whether the working modes of the ports at the two ends of the
equipment match. If the working modes mismatch, adjust the working modes of the
ports according to the actual situation.
Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
1.
Use the smartbits equipment to check whether bit errors occur in the data transmitted
at the client side. If bit errors occur, find and rectify the fault of the client-side
equipment.
Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,

1.
If this event persists, replace the faulty board. For details on operations, see the Parts
Replacement.
----End
Related Information
None
8.6 RMON module performance value is lower than the

lower threshold
Description
An event indicating that the RMON module performance value is lower than the lower threshold.
In the sampling period, an event indicating upper threshold crossing occurs. In a new sampling
period, when the sampling value is less than or is equal to the lower threshold value, and the
reporting mode is that this event is reported when the performance value is lower than the lower
threshold value, or that this event is reported when the performance value is higher than the
upper threshold value or lower than the lower threshold value, this event is reported.
Attribute
Issue 02 (2011-10-31)
Event Severity
Event Type
Minor
Communication

1005
OptiX OSN 8800/6800/3800

8 Event Processing
Parameter
Parameter
Description
Parameter 1
Indicates the slot ID, port number and channel number,

such as 1-LOG-2(ETHER):1.
Parameter 2
Indicates the performance event of threshold crossing.

Drop Events
Fragments
Jabbers
Collisions
Bad Octets Received
Alignment Errors
FCS Errors
Late Collisions
Excessive Collisions
Deferred Transmissions
Carrier Sense Errors
Drop Events at Transmission Direction
Parameter 3
Indicates the performance value.
Parameter 4
Indicates the lower threshold value.
Impact on System
When this event is reported, it indicates that the related Ethernet performance values are
recovered. The quality of the Ethernet service in the system is improved.
Possible Causes
The fault of the system is rectified, and the performance value is recovered.
Procedure
l
Ignore the event.
----End
Related Information
None
Issue 02 (2011-10-31)

1006
OptiX OSN 8800/6800/3800

8 Event Processing
8.7 1+1 Equipment Level Protection Switching Event Report

Description
1+1 Equipment Level Protection Switching Event Report, when the board protection switching
occurs, this event is reported.
Attribute
Event Severity
Event Type
Critical
Equipment
Parameter
Parameter
Description
Parameter 1
Indicates the ID of the protection group where this

event occurs, The values of the parameter are as
follows:
The value is 1, indicates the SCC board protection
switching occurs.
The value is 1, indicates the cross-connect board
The value is 2, indicates the SCC board protection
switching occurs.
Parameter 2
Indicates the slot ID of the current working board,

such as "9".
Parameter 3
Indicates the slot ID of the current protection board,

such as "10".
Impact on System
When the cross-connect board protection switching occurs in the protection group, the service
may be transiently interrupted.
Possible Causes
l
Cause 1: The user issues an external switching command, such as forced switching or
clearing. In this case, the working unit of the protection group is switched to the protection
unit, or the protection unit is switched to the working unit, this event is reported.
Cause 2: When one unit in the protection group is abnormal, the protection group is switched
to another unit. In this case, this event is reported.
Issue 02 (2011-10-31)

1007
OptiX OSN 8800/6800/3800

8 Event Processing
Procedure
l
Cause 1: The user issues an external switching command.

1.
Ignore the event.
Cause 2: When one unit in the protection group is abnormal, the protection group is switched
to another unit. In this case, this event is reported.
1.
If this event persists, replace the faulty board. For details on operations, see Parts
Replacement.
----End
Related Information
None
Issue 02 (2011-10-31)

1008
OptiX OSN 8800/6800/3800

A Glossary
Glossary
A
AC
See alternating current
access control list
A list of entities, together with their access rights, which are authorized to have access
to a resource.
ACK
See acknowledgement
acknowledgement
A response sent by a receiver to indicate successful reception of information.

Acknowledgements may be implemented at any level including the physical level (using
voltage on one or more wires to coordinate transfer), at the link level (to indicate
successful transmission across a single hardware link), or at higher levels.
ACL
See access control list
add/drop multiplexer
Network elements that provide access to all or some subset of the constituent signals
contained within an STM-N signal. The constituent signals are added to (inserted), and/
or dropped from (extracted) the STM-N signal as it passed through the ADM.
Add/drop wavelength
Add/drop wavelength refers to the wavelength that carries the add/drop services in the
OADM equipment.
Address Resolution
Protocol
Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to

MAC addresses. It allows hosts and routers to determine the link layer addresses through
ARP requests and ARP responses. The address resolution is a process in which the host
converts the target IP address into a target MAC address before transmitting a frame.
The basic function of the ARP is to query the MAC address of the target equipment
through its IP address.
ADM
See add/drop multiplexer
administrative unit
The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrator
A user who has authority to access all the Management Domains of the EMLCore
product. He has access to the whole network and to all the management functionalities.
ADSL
See asymmetric digital subscriber line
AGC
See automatic gain control
Issue 02 (2011-10-31)

1009
OptiX OSN 8800/6800/3800

A Glossary
AID
access identifier
AIS
See alarm indication signal
alarm
A message reported when a fault is detected by a device or by the network management

system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm cable
The cable for generation of visual or audio alarms.
alarm cascading
The shunt-wound output of the alarm signals of several subracks or cabinets.
alarm cause
A single disturbance or fault may lead to the detection of multiple defects. A fault cause
is the result of a correlation process which is intended to identify the defect that is
representative of the disturbance or fault that is causing the problem.
alarm indication
On the cabinet of an NE, there are four indicators in different colors indicating the current
status of the NE. When the green indicator is on, it indicates that the NE is powered on.
When the red indicator is on, it indicates that a critical alarm is generated. When the
orange indicator is on, it indicates that a major alarm is generated. When the yellow
indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on
the front panel of a board indicates the current status of the board.
alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure
has been detected and alarmed. It is associated with multiple transport layers.
alarm mask
On the host, an alarm management method through which users can set conditions for
the system to discard (not to save, display, or query for) the alarm information meeting
the conditions.
alarm severity
The significance of a change in system performance or events. According to ITU-T

recommendations, an alarm can have one of the following severities: Critical, Major,
Minor, Warning.
alarm suppression
A function used not to monitor alarms for a specific object, which may be the
networkwide equipment, a specific NE, a specific board and even a specific function
module of a specific board.
alarm type
Classification of alarms with different attributes. There are six alarm types as following:
Communication: alarm indication related with information transfer. Processing: alarm
indication related with software or information processing Equipment: alarm indication
related with equipment fault Service: alarm indication related with QoS of the equipment
Environment: alarm related with the environment where the equipment resides, usually
generated by a sensor Security: alarm indication related with security
ALC
See automatic level control
ALC link
A piece of end-to-end configuration information, which exists in the equipment (single

station) as an ALC link node. Through the ALC function of each node, it fulfils optical
power control on the line that contains the link.
ALC node
The ALC functional unit. It corresponds to the NE in a network. The power detect unit,
variable optical attenuator unit, and supervisory channel unit at the ALC node work
together to achieve the ALC function.
ALS
See automatic laser shutdown
alternating current
Electric current that reverses its direction of flow (polarity) periodically according to a
frequency measured in hertz, or cycles per second.
Issue 02 (2011-10-31)

1010
OptiX OSN 8800/6800/3800

A Glossary
American National
Standard Institute
An organization that defines U.S standards for the information processing industry.
American National Standard Institute (ANSI) participates in defining network protocol
standards.
American Standard
Code for Information
Interchange
American Standard Code for Information Interchange - the standard system for
representing letters and symbols. Each letter or symbol is assigned a unique number
between 0 and 127.
ANSI
See American National Standard Institute
antistatic floor
A floor that can quickly release the static electricity of the object contacting it to prevent
accumulated static electricity
APD
See avalanche photodiode
APE
automatic power equilibrium
APID
access point identifier
application-specific
integrated circuit
A special type of chip that starts out as a nonspecific collection of logic gates. Late in
the manufacturing process, a layer is added to connect the gates for a specific function.
By changing the pattern of connections, the manufacturer can make the chip suitable for
many needs.
APS
See automatic protection switching
ARP
See Address Resolution Protocol
arrayed waveguide
grating
A device, built with silicon planar lightwave circuits (PLC), that allows multiple
wavelengths to be combined and separated in a dense wavelength-division multiplexing
(DWDM) system.
ASCII
See American Standard Code for Information Interchange
ASE
amplified spontaneous emission
ASIC
See application-specific integrated circuit
ASON
See automatically switched optical network
asymmetric digital
subscriber line
A technology for transmitting digital information at a high bandwidth on existing phone

lines to homes and businesses. Unlike regular dialup phone service, ADSL provides
continuously-available, "always on" connection. ADSL is asymmetric in that it uses most
of the channel to transmit downstream to the user and only a small part to receive
information from the user. ADSL simultaneously accommodates analog (voice)
information on the same line. ADSL is generally offered at downstream data rates from
512 Kbps to about 6 Mbps.
Asynchronous
Transfer Mode
A protocol for the transmission of a variety of digital signals using uniform 53 byte cells.
A transfer mode in which the information is organized into cells; it is asynchronous in
the sense that the recurrence of cells depends on the required or instantaneous bit rate.
Statistical and deterministic values may also be used to qualify the transfer mode.
ATAG
autonomously generated correlation tag
ATM
See Asynchronous Transfer Mode
AU
See administrative unit
auto-negotiation
An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to
automatically exchange information over a link about speed and duplex abilities.
Issue 02 (2011-10-31)

1011
OptiX OSN 8800/6800/3800

A Glossary
automatic gain control A process or means by which gain is automatically adjusted in a specified manner as a
function of a specified parameter, such as received signal level.
automatic laser
shutdown
A technique (procedure) to automatically shutdown the output power of laser transmitters

and optical amplifiers to avoid exposure to hazardous levels.
automatic level control A well-known application in communication systems with a given input signal
conditioned to produce an output signal as possible, while supporting a wide gain range
and controlled gain-reduction and gain recovery characteristics.
automatic protection
switching
Capability of a transmission system to detect a failure on a working facility and to switch

to a standby facility to recover the traffic.
automatically switched A network which is based on technology enabling the automatic delivery of transport
optical network
services. Specifically, an ASON can deliver not only leased-line connections but also
other transport services such as soft-permanent and switched optical connections.
avalanche photodiode
A semiconductor photodetector with integral detection and amplification stages.

Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
AWG
See arrayed waveguide grating
B
background block
error ratio
The ratio of background block errors (BBE) to total blocks in available time during a
fixed measurement interval. The count of total blocks excludes all blocks during SESs.
backup
A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth
A range of transmission frequencies that a transmission line or channel can carry in a

network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BAS
See broadband access server
basic input/output
system
A firmware stored in the computer mainboard. It contains basic input/output control

programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
bayonet-neillconcelman
A connector used for connecting two coaxial cables.
BBE
background block error
BBER
See background block error ratio
BC
See boundary clock
BDI
Backward Defect Indication
BEI
BER
See bit error rate
BIAE
backward incoming alignment error
Issue 02 (2011-10-31)

1012
OptiX OSN 8800/6800/3800

A Glossary
bill of material
Listing of all the subassemblies, parts and raw materials that go into the parent assembly.
It shows the quantity of each raw material required to make the assembly. There are a
variety of display formats for BOMS, including single level, indented, modular/
planning, transient, matrix and costed BOMs [APICs, CMSG].
BIOS
See basic input/output system
BIP
See bit-interleaved parity
BIP-8
See bit interleaved parity order 8
bit error
An incompatibility between a bit in a transmitted digital signal and the corresponding

bit in the received digital signal.
bit error rate
Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
bit interleaved parity

order 8
A frame is divided into several blocks with 8 bits (one byte)in a parity unit. Then arrange
the blocks in matrix. Compute the number of "1" over each column. Then fill a 1 in the
corresponding bit for the result if the number is odd, otherwise fill a 0.
bit-interleaved parity
A method of error monitoring. With even parity an X-bit code is generated by the
transmitting equipment over a specified portion of the signal in such a manner that the
first bit of the code provides even parity over the first bit of all X-bit sequences in the
covered portion of the signal, the second bit provides even parity over the second bit of
all X-bit sequences within the specified portion, etc. Even parity is generated by setting
the BIP-X bits so that there is an even number of 1s in each monitored partition of the
signal. A monitored partition comprises all bits which are in the same bit position within
the X-bit sequences in the covered portion of the signal. The covered portion includes
the BIP-X.
BITS
See building integrated timing supply
BMC
best master clock
BNC
See bayonet-neill-concelman
BOM
See bill of material
boundary clock
A clock with a clock port for each of two or more distinct PTP communication paths.
BPDU
See bridge protocol data unit
BPS
board-level protection switching
bridge protocol data

unit
The data messages that are exchanged across the switches within an extended LAN that
uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
bridging
The action of transmitting identical traffic on the working and protection channels
simultaneously.
broadband access
server
A server providing features as user access, connection management, address allocation

and authentication, authorization and accounting. It also works as a router featuring
effective route management, high forwarding performance and abundant services.
broadcast
A means of delivering information to all members in a network. The broadcast range is

determined by the broadcast address.
Issue 02 (2011-10-31)

1013
OptiX OSN 8800/6800/3800

A Glossary
broadcast service
The unidirectional services from one service source to multiple service sinks.
building integrated
timing supply
In the situation of multiple synchronous nodes or communication devices, one can use
a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
BWS
Backbone WDM System
C
cable tie
The tape used to bind the cables.
capex
See capital expenditure
capital expenditure
Capital expenditures (CAPEX or capex) are expenditures creating future benefits. A

capital expenditure is incurred when a business spends money either to buy fixed assets
or to add to the value of an existing fixed asset with a useful life that extends beyond the
taxable year. Capex are used by a company to acquire or upgrade physical assets such
as equipment, property, or industrial buildings.
CAR
See committed access rate
CBS
See committed burst size
CC
See connectivity check
CCI
connection control interface
CCM
See continuity check message
CD
chromatic dispersion
CDMA
See Code Division Multiple Access
CE
See customer edge
CENELEC
See European Committee for Electrotechnical Standardization
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
centralized alarm
system
The system that gathers all the information about alarms into a certain terminal console.
CF
See compact flash
CGMP
Cisco Group Management Protocol
channel
A telecommunication path of a specific capacity and/or at a specific speed between two

or more locations in a network. The channel can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s),
and Tb/s (1012 bit/s).
channel spacing
The center-to-center difference in frequency or wavelength between adjacent channels

in a WDM device.
CIR
See committed information rate
Issue 02 (2011-10-31)

1014
OptiX OSN 8800/6800/3800

A Glossary
CIST
Common and Internal Spanning Tree
CLEI
common language equipment identification
CLNP
connectionless network protocol
CLNS
connectionless network service
clock synchronization
Also called frequency synchronization, clock synchronization means that the signal
frequency traces the reference frequency, but the start point need not be consistent.
clock synchronization A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588
compliant with
V2 standard specifies the precision time protocol (PTP) in a measurement and control
precision time protocol system. The PTP protocol ensures clock synchronization precise to sub-microseconds.
clock tracing
The method to keep the time on each node being synchronized with a clock source in a
network.
CM
See configuration management
CMEP
connection monitoring end point
CMI
coded mark inversion
coarse wavelength
division multiplexing
A signal transmission technology that multiplexes widely-spaced optical channels into

the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM
does not support optical amplifiers and is applied in short-distance chain networking.
Code Division Multiple A communication scheme that forms different code sequences by using the frequency
Access
expansion technology. In this case, subscribers of different addresses can use different
code sequences for multi-address connection.
committed access rate
A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
committed burst size
committed burst size. A parameter used to define the capacity of token bucket C, that is,
the maximum burst IP packet size when the information is transferred at the committed
information rate. This parameter must be larger than 0. It is recommended that this
parameter should be not less than the maximum length of the IP packet that might be
forwarded.
committed information The rate at which a frame relay network agrees to transfer information in normal
rate
conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common Object
Request Broker
Architecture
A specification developed by the Object Management Group in 1992 in which pieces of

programs (objects) communicate with other objects in other programs, even if the two
programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and thus does not need to know the structure of the program from which the object
comes. CORBA is designed to work in object-oriented environments. See also IIOP,
object (definition 2), Object Management Group, object-oriented.
compact flash
Compact flash (CF) was originally developed as a type of data storage device used in
portable electronic devices. For storage, CompactFlash typically uses flash memory in
a standardized enclosure.
concatenation
A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.
Issue 02 (2011-10-31)

1015
OptiX OSN 8800/6800/3800

A Glossary
Configuration Data
A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other Nes in an entire network. Thus, configuration data is the key factor
for normal running of an entire network.
configuration
management
1. A network management function defined by the International Standards Organization

(ISO). It involves installing, reinitializing & modifying hardware & software.
2. Configuration Management (CM) is a system for collecting the configuration
information of all nodes in the network.
configure
To set the basic parameters of an operation object.
congestion
An extra intra-network or inter-network traffic resulting in decreasing network service

efficiency.
connecting plate
A metallic plate which is used to combine two cabinets.
connection point
A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
connectivity check
Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by
each MEP transmitting a Continuity Check Message (CCM) periodically.
continuity check
message
CCM is used to detect the link status.
convergence
1. A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals.
2. It refers to the speed and capability for a group of networking devices to run a specific
routing protocol. It functions to keep the network topology consistent.
convergence service
A service that provides enhancements to an underlying service in order to provide for

the specific requirements of the convergence service user.
CORBA
See Common Object Request Broker Architecture
corrugated pipe
Used to protect optical fibers.
CPLD
Complex Programmable Logical Device
CPU
See central processing unit
CRC
See cyclic redundancy check
CSA
Canadian Standards Association
CSES
consecutive severely errored second
CSMA
carrier sense multiple access
CST
Common Spanning Tree
current alarm
An alarm not handled or not acknowledged after being handled.
current performance
data
Performance data stored currently in a register. An NE provides two types of registers,

namely, 15-minute register and 24-hour register, to store performance parameters of a
performance monitoring entity. The two types of registers stores performance data only
in the specified monitoring period.
Issue 02 (2011-10-31)

1016
OptiX OSN 8800/6800/3800

A Glossary
customer edge
A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.
CWDM
See coarse wavelength division multiplexing
cyclic redundancy
check
A procedure used in checking for errors in data transmission. CRC error checking uses
a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
D
DAPI
destination access point identifiers
Data backup
A method that is used to copy key data to the standby storage area, to prevent data loss
in the case of the damage or failure in the original storage area.
data communication
network
A communication network used in a TMN or between TMNs to support the Data

Communication Function (DCF).
data communications
channel
The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
transmit information on operation, management, maintenance and provision (OAM&P)
between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
DBPS
distribute board protect system
DCC
See data communications channel
DCF
See dispersion compensation fiber
DCM
See dispersion compensation module
DCM frame
A frame which is used to hold the DCM (Dispersion Compensation Module).
DCN
See data communication network
DDF
See digital distribution frame
DDN
See digital data network
demultiplexer
A device that separates signals that have been combined by a multiplexer for transmission
over a communications channel as a single signal.
dense wavelength
division multiplexing
Technology that utilizes the characteristics of broad bandwidth and low attenuation of
single mode optical fiber, employs multiple wavelengths with specific frequency spacing
as carriers, and allows multiple channels to transmit simultaneously in the same fiber.
device set
A collection of multiple managed devices. By dividing managed devices into different

device sets, users can manage the devices by using the U2000 in an easier way. If an
operation authority over one device set is assigned to a user (user group), the authority
over all the devices in the device set is assigned to the user (user group), thus making it
unnecessary to set the operation authority over all the devices in a device set separately.
It is recommended to configure device set by geographical region, network level, device
type, or another criterion.
DHCP
See Dynamic Host Configuration Protocol
Issue 02 (2011-10-31)

1017
OptiX OSN 8800/6800/3800

A Glossary
diamond-shaped nut
A type of nut that is used to fasten the wiring frame to the cabinet.
digital data network
A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
digital distribution
frame
A type of equipment used between the transmission equipment and the exchange with
transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital subscriber line

access multiplexer
A network device, usually situated in the main office of a telephone company that
receives signals from multiple customer Digital Subscriber Line (DSL) connections and
puts the signals on a high-speed backbone line using multiplexing techniques.
dispersion
compensation fiber
A kind of fiber which uses negative dispersion to compensate for the positive dispersion
of transmitting fiber to maintain the original shape of the signal pulse.
dispersion
compensation module
A module, which contains dispersion compensation fibers to compensate for the

dispersion of transmitting fiber.
Distance Vector
Multicast Routing
Protocol
An Internet gateway protocol mainly based on the RIP. The protocol implements a typical
dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
datagrams with its neighbors.
distributed link
aggregation group
The distributed link aggregation group (DLAG) is a board-level port protection

technology used to detect unidirectional fiber cuts and to negotiate with the opposite end.
In the case of a link down failure on a port or a hardware failure on a board, the services
can automatically be switched to the slave board, thus realizing 1+1 protection for the
inter-board ports.
DLAG
See distributed link aggregation group
DMUX; DEMUX
See demultiplexer
DNI
Dual Node Interconnection
domain
A logical subscriber group based on which the subscriber rights are controlled.
DQPSK
differential quadrature phase shift keying
DRDB
dynamic random database
DRZ
differential phase return to zero
DSCP
Differentiated Services Code Point
DSCR
dispersion slope compensation rate
DSLAM
See digital subscriber line access multiplexer
DSP
Digital Signal Processing
DTE
Data Terminal Equipment
DTMF
See dual tone multiple frequency
DTR
data terminal ready
dual tone multiple

frequency
In telephone systems, multifrequency signaling in which standard set combinations of

two specific voice band frequencies, one from a group of four low frequencies and the
other from a group of four higher frequencies, are used.
dual-ended switching
A protection operation method which takes switching action at both ends of the protected
entity (e.g. "connection", "path"), even in the case of a unidirectional failure.
Issue 02 (2011-10-31)

1018
OptiX OSN 8800/6800/3800

DVB
Digital Video Broadcasting
DVMRP
See Distance Vector Multicast Routing Protocol
DWDM
See dense wavelength division multiplexing
A Glossary
Dynamic Host
Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol.
Configuration Protocol A DHCP server provides configuration parameters specific to the DHCP client host
requesting, generally, information required by the host to participate on the Internet
network. DHCP also provides a mechanism for allocation of IP addresses to hosts.
E
E2E
End to End
EAPE
enhanced automatic power pre-equilibrium
EBS
See excess burst size
ECC
See embedded control channel
EDFA
See erbium doped fiber amplifier
eDQPSK
enhanced differential quadrature phase shift keying
EFM
See Ethernet in the first mile
ejector lever
A lever for removing circuit boards from an electronic chassis.
electric supervisory
channel
A technology realizes the communication among all the nodes and transmits the
monitoring data in the optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electromagnetic
compatibility
Electromagnetic compatibility is the condition which prevails when telecommunications

equipment is performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to unintentional
electromagnetic interference to or from other equipment in the same environment.
electromagnetic
interference
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or

limits the effective performance of electronics/electrical equipment.
electrostatic discharge
The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
element management
system
An element management system (EMS) manages one or more of a specific type of

network elements (NEs). An EMS allows the user to manage all the features of each NE
individually, but not the communication between NEs - this is done by the network
management system (NMS).
embedded control
channel
A logical channel that uses a data communications channel (DCC) as its physical layer,
to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
EMC
See electromagnetic compatibility
EMI
See electromagnetic interference
EMS
See element management system
enterprise system
connection
A path protocol which connects the host with various control units in a storage system.
It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
EPL
See Ethernet private line
Issue 02 (2011-10-31)

1019
OptiX OSN 8800/6800/3800

A Glossary
EPLAN
See Ethernet private LAN service
erbium doped fiber

amplifier
An optical device that amplifies the optical signals. The device uses a short length of
optical fiber doped with the rare-earth element Erbium and the energy level jump of
Erbium ions activated by pump sources. When the amplifier passes the external light
source pump, it amplifies the optical signals in a specific wavelength range.
ESC
See electric supervisory channel
ESCON
See enterprise system connection
ESD
See electrostatic discharge
ESD jack
Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
eSFP
enhanced small form-factor pluggable
Ethernet
A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision

Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..
Ethernet in the first

mile
Last mile access from the broadband device to the user community. The EFM takes the
advantages of the SHDSL.b is technology and the Ethernet technology. The EFM
provides both the traditional voice service and internet access service of high speed. In
addition, it meets the users' requirements on high definition television system (HDTV)
and Video On Demand (VOD).
Ethernet private LAN

service
An Ethernet service type, which carries Ethernet characteristic information over a

dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or
MPLS server layer networks.
Ethernet private line
A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual
private LAN service
An Ethernet service type, which carries Ethernet characteristic information over a shared
bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
Ethernet virtual
private line
An Ethernet service type, which carries Ethernet characteristic information over shared
bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
ETS
European Telecommunication Standards
ETSI
European Telecommunications Standards Institute
ETSI 300mm cabinet
A cabinet which is 600mm in width and 300mm in depth, compliant with the standards
of the ETSI.
European Committee
for Electrotechnical
Standardization
The European Committee for Electrotechnical Standardization was established in 1976

in Brussels. It is the result of the incorporation of two former organizations. It aims to
reduce internal frontiers and trade barriers for electrotechnical products, systems and
services.
EVOA
electrical variable optical attenuator
EVPL
See Ethernet virtual private line
EVPLAN
See Ethernet virtual private LAN service
Issue 02 (2011-10-31)

1020
OptiX OSN 8800/6800/3800

A Glossary
excess burst size
A parameter related to traffic. In the single rate three color marker (srTCM) mode, the
traffic control is achieved by the token buckets C and E. Excess burst size is a parameter
used to define the capacity of token bucket E, that is, the maximum burst IP packet size
when the information is transferred at the committed information rate. This parameter
must be larger than 0. It is recommended that this parameter should be not less than the
maximum length of the IP packet that might be forwarded.
Extended ID
The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The extended ID and ID form the physical ID of the NE.
External cable
The cables and optical fibers which are used for connecting electrical interfaces and
optical interfaces of one cabinet to interfaces of other cabinets or peripherals.
eye pattern
An oscilloscope display of synchronized pseudo-random digital data (signal amplitude

versus time), showing the superposition of accumulated output waveforms.
F
F1 byte
The user path byte, which is reserved for the user, but is typically special for network
providers. The F1 byte is mainly used to provide the temporary data or voice path for
special maintenance objectives. It belongs to the regenerator section overhead byte.
fast Ethernet
Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
fault
A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources and intentional settings.
FBG
fiber Bragg grating
FC
See fiber channel
FDB
flash database
FDDI
See fiber distributed data interface
FE
See fast Ethernet
FEC
See forward error correction
fiber channel
A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
fiber distributed data

interface
A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber management tray A device used to coil up extra optical fibers.
Issue 02 (2011-10-31)

1021
OptiX OSN 8800/6800/3800

A Glossary
fiber patch cord
A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
fiber spool
A device used in coiling up an extra length of optical fibers.
Fiber trough
The trough that is used for routing fibers.
fiber/cable
Fiber & Cable is the general name of optical fiber and cable. It refers to the physical
entities that connect the transmission equipment, carry transmission objects (user
information and network management information) and perform transmission function
in the transmission network. The optical fiber transmits optical signal, while the cable
transmits electrical signal. The fiber/cable between NEs represents the optical fiber
connection or cable connection between NEs. The fiber/cable between SDH NEs
represents the connection relation between NEs. At this time, the fiber/cable is of optical
fiber type.
field programmable
gate array
A type of semi-customized circuit used in the Application Specific Integrated Circuit

(ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arrays.
FIFO
See First in First out
File Transfer Protocol
A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
First in First out
A stack management mechanism. The first saved data is first read and invoked.
Flow
An aggregation of packets that have the same characteristics. On the network

management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation. At present,
two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID
and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist
in the same port.
FMT
See fiber management tray
FOADM
fixed optical add/drop multiplexer
FOAs
fixed optical attenuator
Forced switch
For normal traffic signals, switches normal traffic signal to the protection section, unless
an equal or higher priority switch command is in effect or SF condition exists on the
protection section, by issuing a forced switch request for that traffic signal.
forward error
correction
A bit error correction technology that adds the correction information to the payload at
the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
four-wave mixing
Four-Wave Mixing (FWM), also called four-photon mixing, occurs when the interaction
of two or three optical waves at different wavelengths generates new optical waves,
called mixing products or sidebands, at other wavelengths.
FPGA
See field programmable gate array
Issue 02 (2011-10-31)

1022
OptiX OSN 8800/6800/3800

frame
A Glossary
A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties.
frame alignment signal A distinctive signal inserted in every frame or once in every n frames, always occupying
the same relative position within the frame, and used to establish and maintain frame
alignment.
FTP
See File Transfer Protocol
full-duplex
A full-duplex, or sometimes double-duplex system, allows communication in both

directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line
telephone networks are full-duplex, since they allow both callers to speak and be heard
at the same time. A good analogy for a full-duplex system would be a two-lane road with
one lane for each direction.
G
gain
The ratio between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
gain flattening filter
Gain Flattening Filter (GFFs), also known as gain equalizing filters, are used to flatten
or smooth out unequal signal intensities over a specified wavelength range. This unequal
signal intensity usually occurs after an amplification stage (for example, EDFA and/or
Raman). Typically, GFFs are used in conjunction with gain amplifiers to ensure that the
amplified channels all have the same gain. A static spectral device that flattens the output
spectrum of an erbium-doped fiber amplifier.
Gateway IP
When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
gateway network
element
A network element that is used for communication between the NE application layer and
the NM application layer
Gb
See gigabit
GCC
general communication channel
GCP
See GMPLS control plan
GE
See gigabit Ethernet
GE ADM
The technology can optimize GE service transport over WDM for Metro network. It
owns the capability of GE service convergence and grooming and benefits to use the
network resource more effectively.
generic framing
procedure
A framing and encapsulated method which can be applied to any data type. It has been
standardized by ITU-T SG15.
GFF
See gain flattening filter
GFP
See generic framing procedure
Issue 02 (2011-10-31)

1023
OptiX OSN 8800/6800/3800

A Glossary
gigabit
In data communications, a gigabit is one billion bits, or 1,000,000,000 (that is, 10^9)
bits. It's commonly used for measuring the amount of data that is transferred in a second
between two telecommunication points.
gigabit Ethernet
GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.
It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support
coaxial cables or other cables. It also supports the channels in the bandwidth mode. If
Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge
(switch) or a router as the center, it gives full play to the performance and the bandwidth.
In the network structure, Gigabit Ethernet uses full duplex links that are private, causing
the length of the links to be sufficient for backbone applications in a building and campus.
Global Positioning
System
A global navigation satellite system. It provides reliable positioning, navigation, and

timing services to worldwide users.
GMPLS
generalized multiprotocol label switching
GMPLS control plan
The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei.
The OptiX GCP applies to the OptiX OSN product series. By using this software, the
traditional network can evolve into the ASON network. The OptiX OSN product series
support the ASON features.
GNE
See gateway network element
GPS
See Global Positioning System
graphical user interface A visual computer environment that represents programs, files, and options with
graphical images, such as icons, menus, and dialog boxes, on the screen.
grounding
The connection of sections of an electrical circuit to a common conductor, called the

ground, which serves as the reference for the other voltages in the circuit.
GSSP
General Snooping and Selection Protocol
GUI
See graphical user interface
H
Hardware loopback
A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HCS
See hierarchical cell structure
HDB
high density bipolar code
HDLC
See high level data link control
hierarchical cell
structure
This is a term typically used to describe the priority of cells within a mixed environment.
That is when Macro, Micro, and Pico cells may be viewed as candidates for cell
reselection the priority described by the HCS will be used in the associated calculations.
high level data link

control
The HDLC protocol is a general purpose protocol which operates at the data link layer
of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by
adding a trailer and a header.
History alarm
The confirmed alarms that have been saved in the memory and other external memories.
History Performance
Data
The performance data that is stored in the history register or that is automatically reported
and stored in the NMS.
Issue 02 (2011-10-31)

1024
OptiX OSN 8800/6800/3800

A Glossary
I
IAE
incoming alignment error
IC
See integrated circuit
ICC
ITU carrier code
ICMP
See Internet Control Message Protocol
ID
See identity
identity
The collective aspect of the set of characteristics by which a thing is definitively

recognizable or known.
Idle resource optical

NE
When the U2000 is started successfully, an NE icon called "Idle ONE" will be displayed
on the topological view. In this NE, the subracks and boards that are not divided to other
optical NEs (such as OTM, OADM and other NEs) are retained. In this NE, idle DWDM
subracks and boards are reserved, which can be distributed to other ONEs. Double-click
the NE icon to view all the currently idle DWDM subracks or boards in the network.
IE
See Internet Explorer
IEC
See International Electrotechnical Commission
IEEE
See Institute of Electrical and Electronics Engineers
IETF
See Internet Engineering Task Force
IGMP
See Internet Group Management Protocol
Input jitter tolerance
The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30
second measurement intervals.
Institute of Electrical
and Electronics
Engineers
A society of engineering and electronics professionals based in the United States but
boasting membership from numerous other countries. The IEEE focuses on electrical,
electronics, computer engineering, and science-related matters.
integrated circuit
A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
integrated services
digital network
A network defined in CCITT, providing comprehensive transmission service for the

voice, video, and data. The ISDN enables the voice, video, and data transmission on a
small number of data channels simultaneously, thus implementing a comprehensive
transmission service.
intelligent power
adjustment
A technology that the system reduces the optical power of all the amplifiers in an adjacent
regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. The loss of optical signals may due to the fiber is broken, the
performance of equipments trend to be inferior or the connector is not plugged well.
Thus, the maintenance engineers are not hurt by the laser being sent out from the slice
of broken fiber.
Internal cable
The cables and optical fibers which are used for interconnecting electrical interfaces and
optical interfaces within the cabinet.
internal spanning tree
A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.
Issue 02 (2011-10-31)

1025
OptiX OSN 8800/6800/3800

A Glossary
International
Electrotechnical
Commission
The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards.
International
Organization for
Standardization
An international association that works to establish global standards for communications

and information exchange. Primary among its accomplishments is the widely accepted
ISO/OSI reference model, which defines standards for the interaction of computers
connected by communications networks.
International
Telecommunication
Union
A United Nations agency, one of the most important and influential recommendation
bodies, responsible for recommending standards for telecommunication (ITU-T) and
radio networks (ITU-R).
International
Telecommunication
UnionTelecommunication
Standardization Sector
An international body that develops worldwide standards for telecommunications

technologies. These standards are grouped together in series which are prefixed with a
letter indicating the general subject and a number specifying the particular standard. For
example, X.25 comes from the "X" series which deals with data networks and open
system communications and number "25" deals with packet switched networks.
Internet Control
Message Protocol
A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
other information relevant to IP packet processing. For example, it can let the IP software
on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Engineering
Task Force
A worldwide organization of individuals interested in networking and the Internet.

Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with
studying technical problems facing the Internet and proposing solutions to the Internet
Architecture Board (IAB). The work of the IETF is carried out by various working groups
that concentrate on specific topics, such as routing and security. The IETF is the publisher
of the specifications that led to the TCP/IP protocol standard.
Internet Explorer
Microsoft's Web browsing software. Introduced in October 1995, the latest versions of
Internet Explorer include many features that allow you to customize your experience on
the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.
Internet Group
Management Protocol
The protocol for managing the membership of Internet Protocol multicast groups among
the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish
and maintain multicast group memberships.
Internet Protocol
The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part. The
entire protocol suite is often referred to as TCP/IP because TCP and IP are the two
fundamental protocols. IP is standardized in RFC 791.
IP
See Internet Protocol
IP address
A 32-bit (4-byte) binary number that uniquely identifies a host (computer) connected to
the Internet for communication with other hosts in the Internet by transferring packets.
An IP address is expressed in dotted decimal notation, consisting of the decimal values
of its 4 bytes, separated with periods; for example, 127.0.0.1. The first three bytes of the
IP address identify the network to which the host is connected, and the last byte identify
the host itself.
IP over DCC
The IP Over DCC follows TCP/IP telecommunications standards and controls the remote
NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead
DCC byte (the default is D1-D3) for communication.
IPA
See intelligent power adjustment
Issue 02 (2011-10-31)

1026
OptiX OSN 8800/6800/3800

A Glossary
IPG
inter-packet gap
ISDN
See integrated services digital network
ISO
See International Organization for Standardization
IST
See internal spanning tree
ITU
See International Telecommunication Union
ITU-T
See International Telecommunication Union-Telecommunication Standardization

Sector
J
Jitter
Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
Jitter transfer
The physical relationship between jitter applied at the input port and the jitter appearing
at the output port.
L
label switched path
A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label

switching mechanisms. A label-switched path can be chosen dynamically, based on
normal routing mechanisms, or through configuration.
LACP
See Link Aggregation Control Protocol
LAG
See link aggregation group
LAN
See local area network
LAPD
link access procedure on the D channel
LAPS
link access protocol-SDH
Laser
A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
layer
A concept used to allow the transport network functionality to be described hierarchically

as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.
LB
See loopback
LCAS
See link capacity adjustment scheme
LCD
See liquid crystal display
LCN
local communication network
LCT
local craft terminal
LED
See light emitting diode
LHP
long hop
Issue 02 (2011-10-31)

1027
OptiX OSN 8800/6800/3800

A Glossary
light emitting diode
A display and lighting technology used in almost every electrical and electronic product
on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice and laser-class printers.
Link Aggregation
Control Protocol
A method of bundling a group of physical interfaces together as a logical interface to

increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity
adjustment scheme
LCAS in the virtual concatenation source and sink adaptation functions provides a
control mechanism to hitlessly increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the Network and Element Management Systems.
Link Control Protocol
In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes,
configures, and tests data-link Internet connections.
link state
advertisement
The link in LSA is any type of connection between OSPF routers, while the state is the
condition of the link.
linktrace message
The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP
is called Linktrace Message(LTM). LTM includes the Time to Live (TTL) and the MAC
address of the destination MEP2.
linktrace reply
For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called Linktrace Reply (LTR). LTR also includes the TTL that equals the result of the
TTL of LTM minus 1.
liquid crystal display
A type of display that uses a liquid compound having a polar molecular structure,
sandwiched between two transparent electrodes.
LLC
See logical link control
LMP
link management protocol
LOC
loss of clock
local area network
A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Locked switching
When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
logical link control
According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
logical port
A logical port is a logical number assigned to every application.
Issue 02 (2011-10-31)

1028
OptiX OSN 8800/6800/3800

A Glossary
loopback
A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LOP
See loss of pointer
LOS
See Loss Of Signal
loss of pointer
Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the

PHY overhead indicating that the receiving equipment has lost the pointer to the start of
cell in the payload. This is used to monitor the performance of the PHY layer.
Loss Of Signal
Loss of signal (LOS) indicates that there are no transitions occurring in the received
signal.
Lower subrack
The subrack close to the bottom of the cabinet when a cabinet contains several subracks.
LP
See logical port
LPT
link-state pass through
LSA
See link state advertisement
LSP
See label switched path
LT
linktrace
LTM
See linktrace message
LTR
See linktrace reply
M
MA
Maintenance Associations
MAC
See media access control
MADM
multiple add/drop multiplexer
main distribution
frame
A device at a central office, on which all local loops are terminated.
main path interface at

the transmitter
A reference point on the optical fiber just after the OM/OA output optical connector.
main topology
A interface that displays the connection relation of NEs on the NMS (screen display).
The default client interface of the NMS, a basic component of the human-machine
interactive interface. The topology clearly shows the structure of the network, the alarms
of different NEs, subnets in the network, the communication status as well as the basic
network operation status. All topology management functions are accessed here.
maintenance domain
The network or the part of the network for which connectivity is managed by CFM. The
devices in an MD are managed by a single ISP.
maintenance point
Maintenance Point (MP) is one of either a MEP or a MIP.
MAN
See metropolitan area network
managed object
The management view of a resource within the telecommunication environment that may
be managed via the agent. Examples of SDH managed objects are: equipment, receive
port, transmit port, power supply, plug-in card, virtual container, multiplex section, and
regenerator section.
Issue 02 (2011-10-31)

1029
OptiX OSN 8800/6800/3800

A Glossary
Management
information
The information that is used for network management in a transport network.
management
information base
A type of database used for managing the devices in a communications network. It

comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
manual switch
Switches normal traffic signal to the protection section, unless a failure condition exists
on other sections (including the protection section) or an equal or higher priority switch
command is in effect, by issuing a manual switch request for that normal traffic signal.
Mapping
A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
marking-off template
A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MD
See maintenance domain
MDB
Memory Database
MDF
See main distribution frame
MDP
message dispatch process
MDS
message distribution service software
ME
maintenance entities
mean launched power
The average power of a pseudo-random data sequence coupled into the fiber by the
transmitter.
Mean Time Between

Failures
The average time between consecutive failures of a piece of equipment. It is a measure

of the reliability of the system.
media access control
A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
MEP
maintenance end point
metropolitan area
network
A metropolitan area network (MAN) is a network that interconnects users with computer
resources in a geographic area or region larger than that covered by even a large local
area network (LAN) but smaller than the area covered by a wide area network (WAN).
The term is applied to the interconnection of networks in a city into a single larger
network (which may then also offer efficient connection to a wide area network). It is
also used to mean the interconnection of several local area networks by bridging them
with backbone lines. The latter usage is also sometimes referred to as a campus network.
MFAS
See multiframe alignment signal
MIB
See management information base
MIP
maintenance intermediate point
MLD
See multicast listener discovery
Issue 02 (2011-10-31)

1030
OptiX OSN 8800/6800/3800

A Glossary
MLM laser
See multi-longitudinal mode laser
MO
See managed object
mother board
A printed board assembly that is used for interconnecting arrays of plug-in electronic
modules.
mounting ear
A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
MP
See maintenance point
MPI
main path interface
MPI-R
main path interface at the receiver
MPI-S
See main path interface at the transmitter
MPLS
See Multiprotocol Label Switching
MS
Multiplex Section
MSA
Multiplex Section Adaptation
MSI
multi-frame structure identifier
MSOH
See multiplex section overhead
MSP
See multiplex section protection
MSPP
multi-service provisioning platform
MST
See multiplex section termination
MSTI
See multiple spanning tree instance
MSTP
See Multiple Spanning Tree Protocol
MTA
Mail Transfer Agent
MTBF
See Mean Time Between Failures
MTU
Maximum Transmission Unit
multi-longitudinal
mode laser
An injection laser diode which has a number of longitudinal modes.
multicast listener
discovery
The MLD is used by the IPv6 router to discover the multicast listeners on their directly
connected network segments, and set up and maintain member relationships. On IPv6
networks, after MLD is configured on the receiver hosts and the multicast router to which
the hosts are directly connected, the hosts can dynamically join related groups and the
multicast router can manage members on the local network.
multiframe alignment
signal
A distinctive signal inserted in every multiframe or once in every n multiframes, always

occupying the same relative position within the multiframe, and used to establish and
maintain multiframe alignment.
multiple spanning tree Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP
instance
within an MST Region, to provide a simply and fully connected active topology for
frames classified as belonging to a VLAN that is mapped to the MSTI by the MST
Configuration. A VLAN cannot be assigned to multiple MSTIs.
Issue 02 (2011-10-31)

1031
OptiX OSN 8800/6800/3800

A Glossary
Multiple Spanning
Tree Protocol
Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an
algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed
as a tree network. In this case, the proliferation and endless cycling of packets is avoided
in the loop network. The protocol that introduces the mapping between VLANs and
multiple spanning trees. This solves the problem that data cannot be normally forwarded
in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
multiplex section
overhead
The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH
definition.
multiplex section
protection
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section
termination
The function performed to generate the MSOH in the process of forming an SDH frame
signal and terminates the MSOH in the reverse direction.
multiplexer
Equipment which combines a number of tributary channels onto a fewer number of

aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
Multiplexing
A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
Multiprotocol Label
Switching
A technology that uses short tags of fixed length to encapsulate packets in different link
layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
MUX
See multiplexer
MVOA
mechanical variable optical attenuator
N
NA
No Acknowledgment
NCP
See Network Control Protocol
NE
See network element
NE database
There are three types of database on NE SCC board as following:

(1) DRDB: a dynamic database in a dynamic RAM, powered by battery;
(2) SDB: a static database in a power-down RAM;
(3) FDB0, FDB0: permanently saved databases in a Flash ROM.
In efficient operation, the NE configuration data is saved in DRDB and SDB at the same
time. Backing up an NE database means backing up the NE configuration data from SDB
to FDB0 and FDB1. When an NE is restarted after power-down, the NE database is
restored in the following procedures: As the SDB data is lost due to power-down, the
main control restores the data first from DRDB. If the data in DRDB is also lost due to
the exhaustion of the battery, the data is restored from FDB0 or FDB1.
Issue 02 (2011-10-31)

1032
OptiX OSN 8800/6800/3800

A Glossary
NE Explorer
The main operation interface, of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, the user can query, manage and
maintain the NE, boards, and ports on a per-NE basis.
NE ID
An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NE Panel
A graphical user interface, of the network management system, which displays subracks,
boards, and ports on an NE. In the NE Panel, the user can complete most of the
configuration, management and maintenance functions for an NE.
NE-side data
The NE configuration data that is stored on the SCC board of the equipment. The NEside data can be uploaded to the network management system(NMS) and thus is stored
on the NMS side.
NEBS
Network Equipment Building System
NEF
See network element function
Network Control
Protocol
This is the program that switches the virtual circuit connections into place, implements
path control, and operates the Synchronous Data Link Control (SDLC) link.
network element
A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control and communication(SCC) board which
manages and monitors the entire network element. The NE software runs on the SCC
board.
network element
function
A function block which represents the telecommunication functions and communicates

with the TMN OSF function block for the purpose of being monitored and/or controlled.
network management
The process of controlling a network so as to maximize its efficiency and productivity.

ISO's model divides network management into five categories: fault management,
accounting management, configuration management, security management and
performance management.
Network Management A system in charge of the operation, administration, and maintenance of a network.
System
network node interface The interface at a network node which is used to interconnect with another network node.
network segment
A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
network service access A network address defined by ISO, through which entities on the network layer can
point
access OSI network services.
Network Time Protocol The Network Time Protocol (NTP) defines the time synchronization mechanism. It
synchronizes the time between the distributed time server and the client.
NM
See network management
NMS
See Network Management System
NNI
See network node interface
NOC
network operation center
Noise figure
An index that represents the degrade extent of optical signals after the signals passing a
system.
NSAP
See network service access point
NTP
See Network Time Protocol
Issue 02 (2011-10-31)

1033
OptiX OSN 8800/6800/3800

A Glossary
O
OA
See optical amplifier
OADM
See optical add/drop multiplexer
OADM frame
A frame which is used to hold the OADM boards.
OAM
See operation, administration and maintenance
OC
See optical coupler
OCI
open connection indication
OCP
See optical channel protection
OD
optical demultiplexing
ODB
optical duobinary
ODF
See optical distribution frame
ODUk
optical channel data unit-k
OEQ
optical equalizer
OFC
open fiber control
OLA
See optical line amplifier
OLP
See optical line protection
OM
optical multiplexing
OMS
optical multiplexing section
ONE
See optical network element
Online Help
The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
OOF
See out of frame
OPA
optical power adjust
open shortest path first A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed of the network topology which is identical on all routers
in the area.
Open Systems
Interconnection
A framework of ISO standards for communication between different systems made by

different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation,
administration and
maintenance
A group of network support functions that monitor and sustain segment operation,
activities that are concerned with, but not limited to, failure detection, notification,
location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
OpEx; OPEX
operation expenditure
OPS
optical physical section
Issue 02 (2011-10-31)

1034
OptiX OSN 8800/6800/3800

A Glossary
optic fiber connector
A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).+
optical add/drop
multiplexer
A device that can be used to add the optical signals of various wavelengths to one channel
and drop the optical signals of various wavelengths from one channel.
optical amplifier
Devices or subsystems in which optical signals can be amplified by means of the

stimulated emission taking place in a suitable active medium.
optical attenuator
A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
optical channel
A signal transmitted at one wavelength in a fiber-optic system.
optical channel
protection
In an optical transmission link that contains multiple wavelengths, when a certain

wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
optical coupler
A coupler for coupling light in an optical system. Multiple discrete layers of alternating
optical materials have respective first and second indexes of refraction. The thickness of
each layer is a fraction of the light wavelength.
optical distribution
frame
A frame which is used to transfer and spool fibers.
optical line amplifier
A piece of equipment that functions as an OLA to directly amplify the input optical
signals and to compensate for the line loss. Currently, the key component of the OLA is
the EDFA amplifier.
optical line protection
A protection mechanism that adopts dual fed and selective receiving principle and singleended switching mode. In this protection, two pairs of fibers are used. One pair of fibers
forms the working route. The working route transmits line signals when the line is
normal. The other pair of fibers forms the protection route. The protection route carries
line signals when the line is broken or the signal attenuation is extremely large.
optical network
element
A transport entity that implements the NE functions (terminal multiplexing, add/drop

multiplexing, cross-connection and regeneration) in a DWDM layer network. The types
of ONEs include OTM, OADM, OLA, REG and OXC. The locating of an ONE is
equivalent to that of a common NE. In a view, an ONE is displayed with an icon, like a
common NE and its alarm status can be displayed with colors. Logically, an ONE consists
of different subracks. Like a common NE, an ONE cannot be expanded or entered like
a sub-network. Similar to a common NE, an ONE provides a list of the subracks that
form the NE to display the board layout.
optical signal-to-noise
ratio
The most important index of measuring the performance of a DWDM system. The ratio
of signal power and noise power in a transmission link. That is, OSNR = signal power/
noise power.
optical spectrum
analyzer
A device that allows the details of a region of an optical spectrum to be resolved.

Commonly used to diagnose DWDM systems.
optical supervisory
channel
A technology that realizes communication among nodes in optical transmission network

and transmits the monitoring data in a certain channel (the wavelength of the working
channel for it is 1510 nm and that of the corresponding protection one is 1625 nm).
Optical switch
A passive component possessing two or more ports which selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.
Issue 02 (2011-10-31)

1035
OptiX OSN 8800/6800/3800

A Glossary
optical time domain

reflectometer
A device that sends a very short pulse of light down a fiber optic communication system
and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
optical transmission
section
Optical transmission section allows the network operator to perform monitoring and
maintenance tasks between NEs.
optical transponder
unit
A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength.
optical transport
network
A network that uses the optical signal to transmit data
optical wavelength
shared protection
In the optical wavelength shared protection (OWSP), the service protection between
different stations can be achieved by using the same wavelength, realizing wavelength
sharing. This saves the wavelength resources and lowers the cost. The optical wavelength
shared protection is mainly applied to the ring network which is configured with
distributed services. It is achieved by using the OWSP board. In a ring network where
services are distributed at adjacent stations, each station requires one OWSP board. Then,
two wavelengths are enough for configuring the shared protection to protect one service
among stations.
OPU
optical channel payload unit
OPUk
optical channel payload unit-k
orderwire
A channel that provides voice communication between operation engineers or

maintenance engineers of different stations.
original equipment
manufacturer
An original equipment manufacturer, or OEM is typically a company that uses a

component made by a second company in its own product, or sells the product of the
second company under its own brand.
OSA
See optical spectrum analyzer
OSC
See optical supervisory channel
OSI
See Open Systems Interconnection
OSN
optical switch node
OSNR
See optical signal-to-noise ratio
OSPF
See open shortest path first
OTDR
See optical time domain reflectometer
OTM
optical terminal multiplexer
OTN
See optical transport network
OTS
See optical transmission section
OTU
See optical transponder unit
OTUk
optical channel transport unit-k
out of frame
An NE transmits an OOF downstream when it receives framing errors in a specified

number of consecutive frame bit positions.
Output optical power
The ranger of optical energy level of output signals.
overhead cabling
Cables or fibers connect the cabinet with other equipment from the top of the cabinet.
OWSP
See optical wavelength shared protection
Issue 02 (2011-10-31)

1036
OptiX OSN 8800/6800/3800

A Glossary
P
PA
pre-amplifier
packet over SDH/

SONET
A MAN and WAN technology that provides point-to-point data connections. The POS
interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet switched
network
A telecommunication network which works in packet switching mode.
Packing case
A case which is used for packing the board or subrack.
Paired slots
Two slots of which the overheads can be passed through by using the bus on the
backplane.
pass-through
The action of transmitting the same information that is being received for any given
direction of transmission.
PBS
See peak burst size
PCB
See printed circuit board
PCC
protection communication channel
PCC
See policy and charging control
PCS
See physical coding sublayer
PDH
See plesiochronous digital hierarchy
PDL
See polarization dependent loss
PDU
Protocol Data Unit
PE
Provider Edge
peak burst size
A parameter used to define the capacity of token bucket P, that is, the maximum burst
IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that this parameter should be not
less than the maximum length of the IP packet that might be forwarded.
peak information rate
Peak Information Rate. A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
Performance register
Performance register is the memory space for performance event counts, including 15min current performance register, 24-hour current performance register, 15-min history
performance register, 24-hour history performance register, UAT register and CSES
register. The object of performance event monitoring is the board functional module, so
every board functional module has a performance register. A performance register is
used to count the performance events taking place within a period of operation time, so
as to evaluate the quality of operation from the angle of statistics.
PGND
protection ground
phase-locked loop
A circuit that consists essentially of a phase detector which compares the frequency of
a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
PHY
See physical sublayer & physical layer
Issue 02 (2011-10-31)

1037
OptiX OSN 8800/6800/3800

A Glossary
physical coding
sublayer
The PCS further helps to define physical layer specifications for 10 gigabit Ethernet after
having been broken down into their Physical Media Dependent Sublayer or PMD. Each
sublayer places the 10GBASE standards into either LAN or WAN specifications.
physical sublayer &

physical layer
1. physical sublayer: One of two sublayers of the FDDI physical layer. 2. physical layer:
In ATM, the physical layer provides the transmission of cells over a physical medium
that connects two ATM devices. The PHY is comprised of two sublayers: PMD and TC
PID
photonics integrated device
PIM-DM
protocol independent multicast-dense mode
PIM-SM
See protocol independent multicast sparse mode
PIN
See Positive Intrinsic Negative
PIR
See peak information rate
plesiochronous digital
hierarchy
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
PLL
See phase-locked loop
PMD
polarization mode dispersion
PMI
payload missing indication
POH
path overhead
point to multipoint
A communications network that provides a path from one location to multiple locations
(from one to many).
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates
data packets on the network layer. It is located in layer 2 of the IP protocol stack.
Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating
over Ethernet
PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard
PPP features such as authentication, encryption, and compression.
Pointer
An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which it is supported.
polarization dependent The maximum, peak-to-peak insertion loss (or gain) variation caused by a component
loss
when stimulated by all possible polarization states. It is specified in dB units.
policy and charging
control
Short for Policy and Charging Control, the PCC is defined in 3GPP R7. The PCC
provides the QoS control and service-based charging functions in the wireless bearer
network.
POS
See packet over SDH/SONET
Positive Intrinsic
Negative
Photodiode. A semiconductor detector with an intrinsic (i) region separating the p- and
n-doped regions. It has fast linear response and is used in fiber-optic receivers.
Power box
A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power distribution box A power box through which the power enters the cabinet and is re-distributed to various
components, at the mean time, the Power Distribution Box protects the electric devices
from current overload.
PPP
See Point-to-Point Protocol
PPPoE
See Point-to-Point Protocol over Ethernet
Issue 02 (2011-10-31)

1038
OptiX OSN 8800/6800/3800

A Glossary
PRBS
See pseudo random binary sequence
PRC
primary reference clock
PRI
See primary rate interface
primary rate interface
An interface consisting of 23 channel Bs and a 64 kbit/s channel D that uses the T1 line,
or consisting of 30 channel Bs and a channel D that uses the E1 line.
printed circuit board
A board used to mechanically support and electrically connect electronic components

using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
protection ground
cable
A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow; while the other half is green.
Protection path
A specific path that is part of a protection group and is labeled protection.
Protection policy
In case the service route provides multiple service protections, different protection
policies can be selected as required. Protection policy refers to the protection mode given
the priority in use for the trail: protection, no protection, and extra traffic. Of the above,
the protection preference is divided into trail protection and subnet connection
protection.
Protection service
A specific service that is part of a protection group and is labeled protection.
protocol independent
multicast sparse mode
It is applicable to large-scale multicast networks with scattered members.
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence
values of any of the other elements, similar to real random sequences.
PSI
payload structure identifier
PSN
See packet switched network
PSTN
See public switched telephone network
PT
payload type
PTMP
See point to multipoint
PTN
packet transport network
PTP
Point-To-Point
public switched
telephone network
A telecommunications network established to perform telephone services for the public

subscribers. Sometimes called POTS.
Q
QA
Q adaptation
QoS
See quality of service
quality of service
A commonly-used performance indicator of a telecommunication system or channel.

Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
Issue 02 (2011-10-31)

1039
OptiX OSN 8800/6800/3800

A Glossary
R
radio network
controller
An equipment in the RNS which is in charge of controlling the use and the integrity of
the radio resources.
RAI
remote alarm indication
RAM
See random access memory
random access memory Semiconductor-based memory that can be read and written by the central processing unit
(CPU) or other hardware devices. The storage locations can be accessed in any order.
Note that the various types of ROM memory are capable of random access but cannot
be written to. The term RAM, however, is generally understood to refer to volatile
memory that can be written to as well as read.
Rapid Spanning Tree
Protocol
An evolution of the Spanning Tree Protocol, providing for faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Receiver Sensitivity
Receiver sensitivity is defined as the minimum acceptable value of average received

power at point R to achieve a 10-12 (The FEC is open).
reconfiguration optical The WDM equipment supports the ROADM. It flexibly and dynamically adjusts add/
add/drop multiplexer drop wavelengths of sites on the network by adjusting the pass-through or block status
of any wavelength without affecting the service transmission in the main optical channel.
This implements wavelength allocation among sites on the network. After the ROADM
is used, the existing services are not affected during upgrade. The wavelength can be
modified quickly and efficiently during network maintenance, which reduces
maintenance cost. In addition, the ROADM supports the equalization for optical power,
which equalizes the optical power at the channel level.
Reed Solomon Code
A type of forward error correcting codes invented in 1960 by Irving Reed and Gustave
Solomon, which has become commonplace in modern digital communications.
reference clock
A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
Reflectance
The ratio of the reflected optical power to the incident optical power.
REG
A piece of equipment or device that regenerates electrical signals.
Regeneration
The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
REI
Remote Error Indication
Resource Reservation
Protocol
The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is
used to reserve resources on every node along a path. RSVP operates on the transport
layer; however, RSVP does not transport application data. RSVP is a network control
protocol like Internet Control Message Protocol (ICMP).
RF
Radio Frequency
RFC
Requirement for Comments
RFI
remote failure indication
ring network
A type of network topology in which each node connects to exactly two other nodes,
forming a circular pathway for signals.
RIP
See Routing Information Protocol
Issue 02 (2011-10-31)

1040
OptiX OSN 8800/6800/3800

A Glossary
RMON
remote network monitoring
RNC
See radio network controller
ROADM
See reconfiguration optical add/drop multiplexer
route
A route is the path that network traffic takes from its source to its destination. In a TCP/
IP network, each IP packet is routed independently. Routes can change dynamically.
Routing Information
Protocol
A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
based on the smallest hop count between source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its neighboring routers and is
known to waste bandwidth.
RS Code
See Reed Solomon Code
RS232
In the asynchronous transfer mode and there is no hand-shaking signal. It can

communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RSTP
See Rapid Spanning Tree Protocol
RSVP
See Resource Reservation Protocol
RZ
return to zero code
S
S1 byte
In an SDH network, each network element traces step by step to the same clock reference
source through a specific clock synchronization path, thus realizing the synchronization
of the whole network. If a clock reference source traced by the NE is missing, this NE
will trace another clock reference source of a lower level. To implement protection
switching of clocks in the whole network, the NE must learn about clock quality
information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to
transmit network synchronization status information. It uses the lower four bits of the
multiplex section overhead S1 byte to indicate 16 types of synchronization quality
grades. Auto protection switching of clocks in a synchronous network can be
implemented using S1 byte and a proper switching protocol.
Safe control switch
The IPA safe switch is set in consideration of the long-span networking requirement,
which cannot allow too low output optical power. If the safe control switch is turned off,
IPA restarting optical power is the specified output power of the OAU. Otherwise, the
IPA restarting optical power is restricted to less than 10 dBm.
SAN
See storage area network
SAP
service access point
SAPI
source access point identifiers
SBS
stimulated Brillouin scattering
SC
See square connector
SD
See signal degrade
SD trigger flag
SD stands for signal degrade. The SD trigger flag determines whether to perform a
switching when SD occurs. The SD trigger flag can be set by using the network
management system.
SDH
See synchronous digital hierarchy
Issue 02 (2011-10-31)

1041
OptiX OSN 8800/6800/3800

A Glossary
SDI
See Serial Digital Interface
SDP
serious disturbance period
Search domain
Search field refers to the range of IP addresses being searched. In the TCP/IP, the IP
addresses include: Category A address (1.0.0.0---126.255.255.255). For example,
10.*.*.*, whose search field is 10.255.255.255, all 10.*.*.* to be searched. Category B
address (128.0.0.0---191. 255. 255. 255). For example, 129.9.*.*, whose search field is
129.9.255.255, all 129.9.*.* to be searched. Category C address (192.0.0.0---223. 255.
255. 255). For example, 192.224.9.*, whose search field is 192.224.9.255, all
192.224.9.* to be searched. Category D address (224.0.0.0---230.255.255.255), which
is reserved. Category E address (240.0.0.0---247.255.255.255), which is reserved. Netid 127.*.*.*, in which .*.*.* can be any number. This net-ID is a local address.
Secure File Transfer

Protocol
A network protocol designed to provide secure file transfer over SSH.
Self-healing
Self-healing is the establishment of a replacement connection by network without the

NMC function. When a connection failure occurs, the replacement connection is found
by the network elements and rerouted depending on network resources available at that
time.
Serial Digital Interface An interface for transmitting digital signals.

Serial Line Interface
Protocol
Serial Line Interface Protocol, defines the framing mode over the serial line to implement
transmission of messages over the serial line and provide the remote host interconnection
function with a known IP address.
service level agreement A service contract between a customer and a service provider that specifies the
forwarding service a customer should receive. A customer may be a user organization
(source domain) or another differentiated services domain (upstream domain). A SLA
may include traffic conditioning rules which constitute a traffic conditioning agreement
as a whole or partially.
Service protection
A measure that ensures that the services can be received at the receive end.
SES
See severely errored second
SETS
See synchronous equipment timing source
settings
Parameters of a system or operation that can be selected by the user.
severely errored second A one-second period which has a bit error ratio >= 10-3 or at least one defect. Time
interval of one second during which a given digital signal is received with an error ratio
greater than 10-3 (Rec. ITU R F. 592 needs correction) .
SF
See signal fail
SFP
See small form-factor pluggable
SFTP
See Secure File Transfer Protocol
shock-proof reinforce
A process by which the cabinet is fastened to the wiring frame or the top of the equipment
room so that the cabinet stands stably.
shortcut menu
A menu that is displayed when right-clicking an object's name or icon. This is also
referred to a context menu.
side door
The side door of a cabinet is used to protect the equipment inside the cabinet against
unexpected touch and environment impact.
Issue 02 (2011-10-31)

1042
OptiX OSN 8800/6800/3800

A Glossary
side mode suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
ratio
source spectrum to the second largest peak.
side trough
The trough on the side of the cable rack, which is used to place nuts so as to fix the
cabinet.
signal cable
Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
signal degrade
A signal indicating the associated data has degraded in the sense that a degraded defect
(e.g., dDEG) condition is active.
signal fail
A signal that indicates the associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal to noise ratio
The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
Simple Network
Management Protocol
A network management protocol of TCP/IP. It enables remote users to view and modify
the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
single-ended switching A protection operation method which takes switching action only at the affected end of
the protected entity (e.g. "trail", "subnetwork connection"), in the case of a unidirectional
failure.
single-mode fiber
A type of fiber optic cable through which only one type of light signal with a fixed wave
length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber is used to transmit data in long distance.
SLA
See service level agreement
SLIP
See Serial Line Interface Protocol
SLM
single longitudinal mode
SM
section monitoring
small form-factor
pluggable
A specification for a new generation of optical modular transceivers.
SMF
See single-mode fiber
SMSR
See side mode suppression ratio
SNCP
See subnetwork connection protection
SNCTP
See subnetwork connection tunnel protection
SNMP
See Simple Network Management Protocol
SNR
See signal to noise ratio
soft permanent
connections
An ASON connection which features flexible and dynamic adjustment of routes. SPC
includes different classes of services (CoS).
SONET
See synchronous optical network
Issue 02 (2011-10-31)

1043
OptiX OSN 8800/6800/3800

span
A Glossary
The physical reach between two pieces of WDM equipment. The number of spans
determines the signal transmission distance supported by a piece of equipment and varies
according to transmission system type.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant
network to block some undesirable redundant paths through certain algorithms and prune
a loop network into a loop-free tree network.
SPC
See soft permanent connections
SPM
self phase modulation
SQL
See structured query language
square connector
Cables may use two styles of connectors: "square" and "D-style".
SRLG
Shared Risk Link Group
SRS
stimulated Raman scattering
SSM
See Synchronization Status Message
SSMB
synchronization status message byte
SSU
synchronization supply unit
STM
Synchronous Transfer Mode
STM-1
See synchronous transport mode 1
STM-4
Synchronous Transport Module of order 4
storage area network
An architecture to attach remote computer storage devices such as disk array controllers,
tape libraries and CD arrays to servers in such a way that to the operating system the
devices appear as locally attached devices.
STP
See Spanning Tree Protocol
structured query
language
A database query and programming language widely used for accessing, querying,
updating, and managing data in relational database systems.
sub-network
Sub-network is the logical entity in the transmission network and comprises a group of
network management objects. The network that consists of a group of interconnected or
correlated NEs, according to different functions. For example, protection subnet, clock
subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a
sub-network is used to contain the equipments which are located in adjacent regions and
closely related with one another, and it is indicated with a sub-network icon on a
topological view. The U2000 supports multilevels of sub-networks. A sub-network
planning can better the organization of a network view. On the one hand, the view space
can be saved, on the other hand, it helps the network management personnel focus on
the equipments under their management.
sub-network number
A number used to differentiate network sections in a sub-network conference. A subnetwork ID consists of the first several digits (one or two) of a user phone number. An
oderwire phone number consists of the sub-network ID and the user number.
subnet mask
The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router and is matched with the IP address.
subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection
protection
subnetwork connection if the working subnetwork connection fails, or if its performance
falls below a required level.
Issue 02 (2011-10-31)

1044
OptiX OSN 8800/6800/3800

A Glossary
subnetwork connection SNCTP provides a VC-4 level channel protection. When the working channel is faulty,
tunnel protection
the services of the entire VC-4 path can be switched over to the protection channel.
support
A part used to support and fix a cabinet on the antistatic floor, it is made of welded steel
plates and is used to block the cabinets up, thus facilitating floor paving and cabling.
Before the whole set of equipment is grounded, insulation plates must be installed under
the supports, and insulating coverings must be added to the expansion bolts to satisfy
the insulation requirements.
Suppression state
An attribute set to determine whether an NE monitors the alarm. Under suppression

status, NE will not monitor the corresponding alarm conditions and the alarm will not
occur even when the alarm conditions are met.
Switching priority
There may be the case that several protected boards need to be switched; thus the tributary
board switching priority should be set. If the switching priority of each board is set the
same, the tributary board that fails later cannot be switched. The board with higher
priority can preempt the switching of that with lower priority.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message
Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
synchronize NE time
To send the system time of the server of the network management system to NEs so as
to synchronize all NEs with the server.
synchronous digital
hierarchy
A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.
synchronous
equipment timing
source
The SETS function provides timing reference to the relevant component parts of
multiplexing equipment and represents the SDH network clement clock.
synchronous optical
network
A high-speed network that provides a standard interface for communications carriers to

connect networks based on fiberoptic cable. SONET is designed to handle multiple data
types (voice, video, and so on). It transmits at a base rate of 51.84 Mbps, but multiples
of this base rate go as high as 2.488 Gbps (gigabits per second).
synchronous transport Synchronous Transfer Mode at 155 Mbit/s.

mode 1
T
TCM
Tandem Connection Monitoring
TCP
See Transmission Control Protocol
TDM
See time division multiplexing
TE
See traffic engineering
Issue 02 (2011-10-31)

1045
OptiX OSN 8800/6800/3800

A Glossary
Telecommunication
A protocol model defined by ITU-T for managing open systems in a communications
Management Network network. An architecture for management, including planning, provisioning, installation,
maintenance, operation and administration of telecommunications equipment, networks
and services.
terminal multiplexer
A device used at a network terminal to multiplex multiple channels of low rate signals
into one channel of high rate signals, or to demultiplex one channel of high rate signals
into multiple channels of low rate signals.
TFTP
See Trivial File Transfer Protocol
TIM
trace identifier mismatch
time division
multiplexing
A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
(TSn, n=0, 1, 2, 3 and so on), and the sampling value codes of multiple signals engross
time slots in a certain order, forming multiple multiplexing digital signals to be
transmitted over one channel.
Time Slot
Continuously repeating interval of time or a time period in which two devices are able
to interconnect.
Time Synchronization
Also called the moment synchronization, time synchronization means that the
synchronization of the absolute time, which requires that the starting time of the signals
keeps consistent with the UTC time.
time to live
A technique used in best-effort delivery systems to prevent packets that loop endlessly.
The TTL is set by the sender to the maximum time the packet is allowed to be in the
network. Each router in the network decrements the TTL field when the packet arrives,
and discards any packet if the TTL counter reaches zero.
TL1
See Transaction Language 1
TLV
Type/Length/Value
TM
See terminal multiplexer
TMN
See Telecommunication Management Network
TP
traffic Policing
traffic engineering
A technology that is used to dynamically monitor the traffic of the network and the load
of the network elements, to adjust in real time the parameters such as traffic management
parameters, route parameters and resource restriction parameters, and to optimize the
utilization of network resources. The purpose is to prevent the congestion caused by
unbalanced loads.
Transaction Language Transaction Language One is a widely used telecommunications management protocol.
1
TL1 is a vendor-independent and technology-independent man-machine language. TL1
facilities can be provided as part of an OSS for interacting with either underlying
management systems or NEs. One popular application is for a management system (or
NE) to package its trap/notification data in TL1 format and forward it to an OSS
component. ...(from authors.phptr.com/morris/glossary.html) Transaction Language 1
(TL1) is a widely used, "legacy", management protocol in telecommunications. It is a
cross-vendor, cross-technology man-machine language, and is widely used to manage
optical (SONET) and broadband access infrastructure in North America. It is defined in
GR-831 by Bellcore (now Telcordia). (from en.wikipedia.org/wiki/TL1)
Issue 02 (2011-10-31)

1046
OptiX OSN 8800/6800/3800

A Glossary
Transmission Control
Protocol
The protocol within TCP/IP that governs the breakup of data messages into packets to
be sent via IP (Internet Protocol), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
tray
A component that can be installed in the cabinet for holding chassis or other devices.
tributary unit group
One or more Tributary Units, occupying fixed, defined positions in a higher order VCn payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that
mixed capacity payloads made up of different size Tributary Units can be constructed
to increase flexibility of the transport network
Trivial File Transfer

Protocol
A small and simple alternative to FTP for transferring files. TFTP is intended for
applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication. TFTP is
small enough to be contained in ROM to be used for bootstrapping diskless machines.
trTCM
Two Rate Three Color Marker
TTI
trail trace identifier
TTL
See time to live
TU
tributary unit
TUG
See tributary unit group
U
UAS
unavailable second
UAT
See unavailable time event
UDP
See User Datagram Protocol
unavailable time event A UAT event is reported when the monitored object generates 10 consecutive severely
errored seconds (SES) and the SESs begin to be included in the unavailable time. The
event will end when the bit error ratio per second is better than within 10 consecutive
seconds.
UNI
See user network interface
universal time
coordinated
The world-wide scientific standard of timekeeping. It is based upon carefully maintained

atomic clocks and is kept accurate to within microseconds worldwide.
Unprotected
Pertaining to the transmission of the services that are not protected, the services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
upload
An operation to report some or all configuration data of an NE to the NMS(Network

Management system). The configuration data then covers the configuration data stored
at the NMS side.
Upper subrack
The subrack close to the top of the cabinet when a cabinet contains several subracks.
User
A client user of the NMS. The user name and password uniquely identifies the operation
rights of a user in the NMS.
Issue 02 (2011-10-31)

1047
OptiX OSN 8800/6800/3800

User Datagram
Protocol
A Glossary
A TCP/IP standard protocol that allows an application program on one device to send a
datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
user network interface The interface between user equipment and private or public network equipment (for
example, ATM switches).
UTC
See universal time coordinated
V
VB
virtual bridge
VC
See virtual container
VCG
See virtual concatenation group
VCI
See virtual channel identifier
virtual channel
identifier
A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to
identify the next destination of a cell as it passes through a series of ATM switches on
its way to its destination.
virtual concatenation
group
A group of co-located member trail termination functions that are connected to the same
virtual concatenation link
virtual container
The information structure used to support path layer connections in the SDH. It consists
of information payload and path Overhead (POH) information fields organized in a block
frame structure which repeats every 125 s or 500 s.
virtual local area

network
A logical grouping of two or more nodes which are not necessarily on the same physical
network segment but which share the same IP network number. This is often associated
with switched Ethernet.
virtual path identifier
The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which
VP (Virtual Path) the cell belongs.
virtual private network A system configuration, where the subscriber is able to build a private network via
connections to different network switches that may include private network capabilities.
VLAN
See virtual local area network
VOA
Variable Optical Attenuator
voice over IP
An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
VoIP
See voice over IP
VPI
See virtual path identifier
VPN
See virtual private network
VRRP
Virtual Router Redundancy Protocol
Issue 02 (2011-10-31)

1048
OptiX OSN 8800/6800/3800

A Glossary
W
WAN
See wide area network
wavelength division
multiplexing
A technology that utilizes the characteristics of broad bandwidth and low attenuation of
single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple
channels to transmit simultaneously in a single fiber.
Wavelength protection The wavelength protection group is important to describe the wavelength protection
group
structure. Its function is similar to that of the protection subnet in the SDH NE. The
wavelength path protection can only work with the correct configuration of the
wavelength protection group.
WDM
See wavelength division multiplexing
WEEE
waste electrical and electronic equipment
wide area network
A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
Working path
The channels allocated to transport the normal traffic.
Working service
A specific service that is part of a protection group and is labeled working.
WRR
weighted round Robin
WSS
wavelength selective switching
WTR
Wait To Restore
WXCP
wavelength cross-connection protection
WXCP service
The WXCP service is also called the GE ADM protection service. The WXCP is a type
of channel protection based on ring network. It adopts the dual fed and selective receiving
principle and uses the cross-connection function to achieve service switching between
working and protection channels.
X
XFP
10Gbit/s Small Form-Factor Pluggable
XPM
cross-phase modulation
Issue 02 (2011-10-31)

1049

Alarms and Performance Events Reference V100R006C01 02 PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Alarms and Performance Events Reference V100R006C01 02 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

OptiX OSN 8800/6800/3800