OSN 8800 6800 3800 V100R007C00 Alarms and Performance Events Reference 06

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

Reference
Issue 06
Date 2015-07-20
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 06 (2015-07-20) Huawei Proprietary and Confidential i

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 V100R007C00
iManager U2000 V100R006C02
iManager U2000 Web LCT V100R006C02
Intended Audience
The intended audience of this document are:
l System maintenance engineer

l Network monitoring engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Issue 06 (2015-07-20) Huawei Proprietary and Confidential ii

OptiX OSN 8800/6800/3800
Symbol Description
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation, which if not

CAUTION 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 06 (2015-07-20) Based on Product Version

V100R007C00
This issue is the sixth official release for OptiX OSN 8800/6800/3800 V100R007C00. Compared
with the 05 issue, some bugs in the manual of the previous version are fixed.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential iii

OptiX OSN 8800/6800/3800

V100R007C00
This issue is the fifth official release for OptiX OSN 8800/6800/3800 V100R007C00. Compared
with the 04 issue, the manual of this issue provides the following updates.
Update Description
2 Alarm List 2.2.92 SCC Board Alarm List is modified, TN21SCC board is deleted.

V100R007C00
This issue is the fourth official release for OptiX OSN 8800/6800/3800 V100R007C00.
Compared with the 03 issue, updating of SPC300 is added.
Update Description
4 Clearing l 3.7.2 COMMUN_FAIL (OTN) is modified.

Alarms

V100R007C00
This issue is the third official release for OptiX OSN 8800/6800/3800 V100R007C00. Compared
with the 02 issue, updating of SPC200 is added.
Update Description
2 Alarm List l 2.2.92 SCC Board Alarm List is modified.

l 2.2.110 TD20 Board Alarm List is modified.
l Add "Service Affecting" in the section 2.1 Product Alarm List.
4 Clearing l 4.326 SUBRACK_TYPE_MISMATCH is modified.

Alarms l 4.52 DERIVED_PWR_ERROR is modified.
l ELPS_B_CFG_MISMATCH is deleted.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential iv

OptiX OSN 8800/6800/3800

V100R007C00
This issue is the second official release for OptiX OSN 8800/6800/3800 V100R007C00. Only
the issue number is updated.

V100R007C00
This issue is the first official release for OptiX OSN 8800/6800/3800 V100R007C00. Compared
with the OptiX OSN 8800/6800/3800 V100R006C03, the manual of this issue provides the
following updates.
Update Description
2 Alarm List l 2.2.27 EX2 Board Alarm List is added.

l 2.2.26 EG16 Board Alarm List is added.
l 2.2.69 NO2 Board Alarm List is added.
l 2.2.75 NS4 Board Alarm List is added.
l 2.2.82 PND2 Board Alarm List is added.
l 2.2.85 RAU2 Board Alarm List is added.
l 2.2.110 TD20 Board Alarm List is added.
l 2.2.116 TM20 Board Alarm List is added.
l 2.2.121 TOX Board Alarm List is added.
l 2.2.126 USXH Board Alarm List is added.
l 2.2.127 UXCH Board Alarm List is added.
l 2.2.128 UXCM Board Alarm List is added.
l 2.2.129 UXCT Board Alarm List is added.
l 2.2.23 EGSH Board Alarm List is modified.
l 2.2.41 LEM24 Board Alarm List is modified.
l 2.2.42 LEX4 Board Alarm List is modified.
l 2.2.80 OPM8 Board Alarm List is modified.
l 2.2.84 RAU1 Board Alarm List is modified.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential v

OptiX OSN 8800/6800/3800
Update Description
4 Clearing l 4.17 ASE_NOT_CALIBRATE is added.

Alarms l 4.43 COM_EXTECC_FULL is added.
l 4.52 DERIVED_PWR_ERROR is added.
l 4.55 EFI_TYPE_MISMATCH is added.
l 4.146 LSR_NO_FITED is added.
l 4.125 LASER_MOD_ERR is added.
l 4.111 IN_PWR_ABN is added.
l 4.143 LSR_BCM_ALM is added.
l ELPS_B_CFG_MISMATCH is added.
l 4.72 ETH_LOS is added.
l 4.71 ETH_LINK_DOWN is added.
l 4.148 MAC_FCS_EXC is added.
l 4.120 LAG_MEMBER_DOWN is added.
l 4.119 LAG_DOWN is added.
l 4.61 ETH_CFM_AIS is added.
l 4.67 ETH_EFM_DF is added.
l 4.70 ETH_EFM_REMFAULT is added.
l 4.68 ETH_EFM_EVENT is added.
l 4.69 ETH_EFM_LOOPBACK is added.
l 4.150 MCLAG_CFG_MISMATCH is added.
l 4.151 MCSP_PATH_LOCV is added.
l 4.168 MPLS_TUNNEL_LOCV is added.
l 4.173 MPLS_TUNNEL_UNEXPMEG is added.
l 4.174 MPLS_TUNNEL_UNEXPMEP is added.
l 4.175 MPLS_TUNNEL_UNEXPPER is added.
l 4.170 MPLS_TUNNEL_RDI is added.
l 4.167 MPLS_TUNNEL_AIS is added.
l 4.171 MPLS_TUNNEL_SD is added.
l 4.172 MPLS_TUNNEL_SF is added.
l 4.159 MPLS_PW_LOCV is added.
l 4.164 MPLS_PW_UNEXPMEG is added.
l 4.165 MPLS_PW_UNEXPMEP is added.
l 4.166 MPLS_PW_UNEXPPER is added.
l 4.161 MPLS_PW_RDI is added.
l 4.158 MPLS_PW_AIS is added.
l 4.162 MPLS_PW_SD is added.
l 4.163 MPLS_PW_SF is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential vi

OptiX OSN 8800/6800/3800
Update Description
l 4.169 MPLS_TUNNEL_OAMFAIL is added.

l 4.160 MPLS_PW_OAMFAIL is added.
l 4.241 OPUk_CSF is added.
l 4.283 PW_NO_TRAFFIC is added.
l 4.287 PWAPS_TYPE_MISMATCH is added.
l 4.285 PWAPS_PATH_MISMATCH is added.
l 4.286 PWAPS_SWITCH_FAIL is added.
l 4.284 PWAPS_LOST is added.
l 4.60 ETH_APS_TYPE_MISMATCH is added.
l 4.58 ETH_APS_PATH_MISMATCH is added.
l 4.59 ETH_APS_SWITCH_FAIL is added.
l 4.57 ETH_APS_LOST is added.
l 4.359 TUNNEL_APS_DEGRADED is added.
l 4.318 SRV_SHUTDOWN_LD is added.
l 4.274 PORT_EXC_TRAFFIC is added.
l 4.33 BWUTILIZATION_OVER is added.
l 4.88 FDBSIZEALM_ELAN is added.
l 4.320 SSM_LOS is added.
l 4.321 SSM_QL_FAILED is added.
l 4.112 INSERTION_LOSS_HIGH is modified.
5 Performance l 5.2.13 EX2 Board Performance Event List is added.

Event List l 5.2.12 EG16 Board Performance Event List is added.
l 5.2.49 NO2 Board Performance Event List is added.
l 5.2.55 NS4 Board Performance Event List is added.
l 5.2.61 PND2 Board Performance Event List is added.
l 5.2.64 RAU2 Board Performance Event List is added.
l 5.2.85 TD20 Board Performance Event List is added.
l 5.2.91 TM20 Board Performance Event List is added.
l 5.2.96 TOX Board Performance Event List is added.
l 5.2.101 USXH Board Performance Event List is added.
l 5.2.102 UXCH Board Performance Event List is added.
l 5.2.103 UXCM Board Performance Event List is added.
l 5.2.104 UXCT Board Performance Event List is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential vii

OptiX OSN 8800/6800/3800
Update Description
6 Handling l 6.5 BDTEMP is added.

Performance l 6.53 MPLS_PW_LS is added.
Event
l 6.54 MPLS_PW_SLS is added.
l 6.55 MPLS_PW_CSLS is added.
l 6.56 MPLS_PW_UAS is added.
l 6.19 ETH_CFM_LS is added.
l 6.20 ETH_CFM_SLS is added.
l 6.21 ETH_CFM_CSLS is added.
l 6.22 ETH_CFM_UAS is added.

V100R006C03
Update Description
2 Alarm List l 2.2.53 LSXL Board Alarm List is modified.
3 Clearing l 3.37 POWER_FAIL is modified.

Common
Alarms
4 Clearing l 4.5 ALS_TRIGGERED is modified.

Alarms
5 Performance l 5.2.36 LSXL Board Performance Event List is modified.

Event List
Issue 06 (2015-07-20) Huawei Proprietary and Confidential viii

OptiX OSN 8800/6800/3800

V100R006C03
Update Description
2 Alarm List l 2.2.10 CRPC Board Alarm List is modified.

l 2.2.29 FIU Board Alarm List is modified.
l 2.2.43 LOA Board Alarm List is modified.
l 2.2.92 SCC Board Alarm List is modified.
l 2.2.115 THA Board Alarm List is modified.
l 2.2.118 TOA Board Alarm List is modified.
l 2.2.119 TOG Board Alarm List is modified.
l 2.2.138 XCH Board Alarm List is modified.
4 Clearing l 4.5 ALS_TRIGGERED is added.

Alarms l 4.103 HARD_NONSUPPORT is added.
l 4.261 OUT_PWR_ABN is added.
l 4.296 RM_RLOS is added.
l 4.319 SSL_CERT_NOENC is added.
l VOA_ADJUST_FAIL is modified.
l LSR_FORCE_OPEN is deleted.
5 Performance l 5.2.14 FIU Board Performance Event List is modified.

Event List l 5.2.50 NQ2 Board Performance Event List is modified.
l 5.2.99 TQX Board Performance Event List is modified.
l 5.2.90 THA Board Performance Event List is modified.
l 5.2.54 NS3 Board Performance Event List is modified.
6 Handling l 6.32 FEC_TMP is added.

Performance l 6.94 ODUk_TCMn_TMP is added.
Event
l 6.79 ODUk_PM_TMP is added.
l 6.127 OTUk_TMP is added.
l 6.134 RMIOP is added.
l 6.136 RS_TMP is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential ix

OptiX OSN 8800/6800/3800

V100R006C03
Update Description
2 Alarm List l 2.2.56 LTX Board Alarm List is modified.

l 2.2.50 LSC Board Alarm List is modified.
l 2.2.74 NS3 Board Alarm List is modified.
l 2.2.53 LSXL Board Alarm List is modified.
l 2.2.135 WSMD2 Board Alarm List is modified.
l 2.2.134 WSM9 Board Alarm List is modified.
l 2.2.133 WSD9 Board Alarm List is modified.
l 2.2.125 TSXL Board Alarm List is modified.
l 2.2.84 RAU1 Board Alarm List is modified.
l Enabled more boards to support the ALS_ACTIVE and
BD_LEDTEST alarms.
4 Clearing l 4.47 DBMS_DELETE is added.

Alarms l 4.265 PASSWORD_NEED_CHANGE is added.
l 4.192 OA_HIGH_GAIN is added.
l 4.181 MUT_TLOS is added.
l 3.23 OA_LOW_GAIN is modified.
l 3.33 OTUk_LOF is modified.
l 3.38 PUMP_COOL_EXC is modified.
l 4.4 ALS_ACTIVE is modified.
l 4.138 LOCKPOW_MIS is modified.
l RX_WAVELEN_MISMATCH is deleted.

Event List l 5.2.39 LTX Board Performance Event List is modified.
l 5.2.33 LSC Board Performance Event List is modified.
l 5.2.36 LSXL Board Performance Event List is modified.
6 Handling l 6.146 TDC is added.

Performance
Event
Issue 06 (2015-07-20) Huawei Proprietary and Confidential x

OptiX OSN 8800/6800/3800

V100R006C03
Update Description
2 Alarm List l 2.2.56 LTX Board Alarm List is added.

l 2.2.50 LSC Board Alarm List is added.
l 2.2.84 RAU1 Board Alarm List is added.
l 2.2.114 TEM28 Board Alarm List is added.
l 2.2.53 LSXL Board Alarm List is modified.
l 2.2.29 FIU Board Alarm List is modified.
4 Clearing l 4.21 BD_LEDTEST is added.

Alarms l 4.74 ETH_NO_FLOW is added.
l 4.100 GFP_UPM is added.
l 4.150 MCLAG_CFG_MISMATCH is added.
l 4.151 MCSP_PATH_LOCV is added.
l 4.299 RX_POWER_ABNORMAL is added.
l RX_WAVELEN_MISMATCH is added.
l 4.360 VCTRUNK_NO_FLOW is added.
l 4.51 DCNSIZE_OVER is added.
l 4.94 FIBERTYPE_MIS is added.
l 4.155 MODULE_RATE_MISMATCH is added.
l 4.45 DB_RESTORE_FAIL is modified.
l DBMS_ABNORMAL is deleted.
5 Performance l 5.2.39 LTX Board Performance Event List is added.

Event List l 5.2.33 LSC Board Performance Event List is added.
l 5.2.63 RAU1 Board Performance Event List is added.
l 5.2.89 TEM28 Board Performance Event List is added.
l 5.2.100 TSXL Board Performance Event List is modified.
l 5.2.36 LSXL Board Performance Event List is modified.

V100R006C01
Some bugs in the manual of the previous version are fixed.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xi

OptiX OSN 8800/6800/3800

V100R006C01
Update Description
2 Alarm List l 2.2.41 LEM24 Board Alarm List is modified.

l 2.2.42 LEX4 Board Alarm List is modified.
l 2.2.60 M40V Board Alarm List is modified.
l 2.2.76 OAU1 Board Alarm List is modified.

Event List l 5.2.88 TDX Board Performance Event List is modified.
l 5.2.60 OPM8 Board Performance Event List is modified.

V100R006C01
Update Description
2 Alarm List l 2.2.115 THA Board Alarm List is modified.

l 2.2.118 TOA Board Alarm List is modified.
l 2.2.43 LOA Board Alarm List is modified.
4 Clearing l 4.103 HARD_NONSUPPORT is added

Alarms
5 Performance l 5.2.50 NQ2 Board Performance Event List is modified.

Event List l 5.2.99 TQX Board Performance Event List is modified.
l 5.2.90 THA Board Performance Event List is modified.
6 Handling l 6.32 FEC_TMP is added.

Performance l 6.79 ODUk_PM_TMP is added.
Event
l 6.94 ODUk_TCMn_TMP is added.
l 6.127 OTUk_TMP is added.
l 6.136 RS_TMP is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xii

OptiX OSN 8800/6800/3800

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

l 2.2.72 NQ2 Board Alarm List is modified.
l 2.2.68 ND2 Board Alarm List is modified.
4 Clearing l 4.353 TIME_LOS is modified.

Alarms l 4.85 EXT_TIME_LOC is modified.
l 4.355 TIME_NO_TRACE_MODE is modified.
l 4.234 OPA_FAIL_INDI is modified.
l 4.124 LASER_HAZARD_WARNING is modified.
l 4.34 CFCARD_FAILED is modified.
l 3.37 POWER_FAIL is modified.
l 4.86 FAN_FAIL is modified.
l DBMS_ABNORMAL is added.
5 Performance l 5.2.50 NQ2 Board Performance Event List is modified.

Event List l 5.2.53 NS2 Board Performance Event List is modified.
l 5.2.48 ND2 Board Performance Event List is modified.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xiii

OptiX OSN 8800/6800/3800

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

l 2.2.5 BMD8 Board Alarm List is added.
l 2.2.24 ELQX Board Alarm List is added.
l 2.2.83 PTQX Board Alarm List is added.
l 2.2.43 LOA Board Alarm List is added.
l 2.2.71 NPO2E Board Alarm List is added.
l 2.2.72 NQ2 Board Alarm List is modified.
l 2.2.68 ND2 Board Alarm List is modified.
l 2.2.113 TDX Board Alarm List is modified.
l 2.2.124 TQX Board Alarm List is modified.
l 2.2.76 OAU1 Board Alarm List is modified.
l 2.2.61 M40 Board Alarm List is modified.
l 2.2.12 D40 Board Alarm List is modified.
l 2.2.60 M40V Board Alarm List is modified.
l 2.2.70 NPO2 Board Alarm List is modified.
l 2.2.25 ENQ2 Board Alarm List is modified.
l 2.2.92 SCC Board Alarm List is modified.
4 Clearing l 4.4 ALS_ACTIVE is added.

Alarms l 4.149 MAINBD_SUBBD_MISMATCH is added.
l 4.294 RL_CRITICAL_HI is added.
l 4.295 RL_CRITICAL_LOW is added.
5 Performance l 5.2.10 ELQX Board Performance Event List is added.

Event List l 5.2.62 PTQX Board Performance Event List is added.
l 5.2.27 LOA Board Performance Event List is added.
l 5.2.52 NPO2E Board Performance Event List is added.
l 5.2.68 SCC Board Performance Event List is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xiv

OptiX OSN 8800/6800/3800

V100R006C00
Update Description
2 Alarm List l 2.2.4 BMD4 Board Alarm List is added.

l 2.2.5 BMD8 Board Alarm List is added.
l 2.2.24 ELQX Board Alarm List is added.
l 2.2.83 PTQX Board Alarm List is added.
4 Clearing l 4.114 IPA_SHUT is added.

Alarms l 4.234 OPA_FAIL_INDI is modified.
l 4.187 NO_BD_SOFT is modified.
5 Performance l 5.2.10 ELQX Board Performance Event List is added.

Event List l 5.2.62 PTQX Board Performance Event List is added.

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

l 2.2.115 THA Board Alarm List is added.
l 2.2.118 TOA Board Alarm List is added.
l 2.2.124 TQX Board Alarm List is modified.
l BMD4, BMD8, ELQX, PTQX are deleted.
4 Clearing l 4.34 CFCARD_FAILED is added.

Alarms l 4.83 EXT_MODULE_OFFLINE is added.
5 Performance l 5.2.83 SXH Board Performance Event List is added.

Event List l 5.2.90 THA Board Performance Event List is added.
l 5.2.93 TOA Board Performance Event List is added.
l ELQX, PTQX are deleted.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xv

OptiX OSN 8800/6800/3800

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

l 2.2.137 WSMD9 Board Alarm List is added.
l 2.2.138 XCH Board Alarm List is modified.
l 2.2.3 AUX Board Alarm List is modified.
4 Clearing l 4.73 ETH_MISCONNECT is added.

Alarms l 4.323 SUBRACK_COMM_PS is added.
5 Performance l 5.2.3 DAS1 Board Performance Event List is added.

Event List l 5.2.112 WSMD9 Board Performance Event List is added.

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

l 2.2.41 LEM24 Board Alarm List is modified.
l 2.2.113 TDX Board Alarm List is modified.
l 2.2.67 MR8V Board Alarm List is modified.
l 2.2.21 EFI1 Board Alarm List is modified.
l 2.2.22 EFI2 Board Alarm List is modified.
5 Performance l 5.2.15 HSC1 Board Performance Event List is modified.

Event List l 5.2.48 ND2 Board Performance Event List is modified.
l 5.2.88 TDX Board Performance Event List is modified.
l 5.2.31 LQMS Board Performance Event List is modified.
l 5.2.30 LQMD Board Performance Event List is modified.
l 5.2.32 LQM Board Performance Event List is modified.
l 5.2.97 TQM Board Performance Event List is modified.
l 5.2.95 TOM Board Performance Event List is modified.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xvi

OptiX OSN 8800/6800/3800

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

V100R005C00
Update Description
4 Clearing l 4.75 ETH_SERVICE_CONFIG_FAIL is added.

Alarms l 4.306 SPAN_LOSS_HIGH is added.
l 4.307 SPAN_LOSS_LOW is added.
l 4.332 SWDL_BD_EXCLUDE is added.
l ALC_LINE_WASTAGE is deleted.

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.25 ENQ2 Board Alarm List is added.

l 2.2.41 LEM24 Board Alarm List is added.
l 2.2.42 LEX4 Board Alarm List is added.
l 2.2.70 NPO2 Board Alarm List is added.
l 2.2.80 OPM8 Board Alarm List is added.
l 2.2.94 SFIU Board Alarm List is added.
l 2.2.95 ST2 Board Alarm List is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xvii

OptiX OSN 8800/6800/3800
Update Description
3 Clearing l 3.3 BOOTROM_BAD is modified.

Common l 3.4 BUS_ERR is modified.
Alarms
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.
4 Clearing l ALC_LINE_WASTAGE is added.

Alarms 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.89 FEATURE_WITHOUT_LICENSE is added.
l 4.98 FWD_PKT_LOSS is added.
l 4.127 LCS_DAYS_OF_GRACE is added.
l 4.128 LCS_EXPIRED is added.
l 4.129 LCS_FILE_NOT_EXIST is added.
l 4.182 MULTI_RPL_OWNER is added.
l 4.190 NTP_SYNC_FAIL is added.
l 4.243 OSC_BDI is added.
l 4.244 OSC_DEG is added.
l 4.302 SEC_RADIUS_FAIL is added.
l 4.361 VCAT_LOA is added.
l 4.367 WAVE_ADD_ABN is added.
l 4.368 WAVE_DROP_ABN is added.
5 Performance l 5.2.11 ENQ2 Board Performance Event List is added.

Event List l 5.2.25 LEM24 Board Performance Event List is added.
l 5.2.26 LEX4 Board Performance Event List is added.
l 5.2.51 NPO2 Board Performance Event List is added.
l 5.2.60 OPM8 Board Performance Event List is added.
l 5.2.80 ST2 Board Performance Event List is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xviii

OptiX OSN 8800/6800/3800
Update Description
6 Handling l 6.25 FEC_AFT_CORER_FLOAT is added.

Performance l 6.28 FEC_BEF_CORER_FLOAT is added.
Event
l 6.97 OSC_BBE is added.
l 6.98 OSC_BBER is added.
l 6.99 OSC_BIAES is added.
l 6.100 OSC_ES is added.
l 6.101 OSC_FEBBE is added.
l 6.102 OSC_FEBBER is added.
l 6.103 OSC_FEES is added.
l 6.104 OSC_FESES is added.
l 6.105 OSC_FESESR is added.
l 6.106 OSC_FEUAS is added.
l 6.107 OSC_IAES is added.
l 6.108 OSC_SES is added.
l 6.109 OSC_SESR is added.
l 6.110 OSC_UAS is added.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xix

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference Contents
Contents
About This Document.....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 Alarm Severity................................................................................................................................................................3
1.2 Alarm Category..............................................................................................................................................................3
1.3 Alarm Management........................................................................................................................................................4
1.4 Performance Event Category..........................................................................................................................................6
1.5 Alarm Signal Flow(OTN)...............................................................................................................................................7
1.5.1 Overview.....................................................................................................................................................................7
1.5.2 Non-Convergent OTU Processing Standard SDH Signals..........................................................................................8
1.5.3 Non-Convergent OTU Processing Standard OTN Signals........................................................................................12
1.5.4 Convergent OTU Processing Standard SDH Signals................................................................................................15
1.5.5 Convergent OTU Processing Standard OTN Signals................................................................................................18
1.5.6 Regenerating OTU.....................................................................................................................................................22
1.5.7 Alarm Signal Processing of the OTU with the Cross-Connect Function..................................................................24
1.5.8 OTU Processing GE Signals......................................................................................................................................26
1.5.9 Optical-Layer Alarm Signal Processing on OTN......................................................................................................29
1.6 Alarm Signal Flow (OCS)............................................................................................................................................33
1.6.1 Overview...................................................................................................................................................................33
1.6.1.1 Directions and Levels of Signal Flows...................................................................................................................34
1.6.1.2 Two Common Alarms............................................................................................................................................34
1.6.2 Generation and Detection of Alarms and Performance Events in the SDH Higher Order Signal Flow...................35
1.6.2.1 Downstream Signal Flow.......................................................................................................................................36
1.6.2.2 Upstream Signal Flow............................................................................................................................................39
1.7 Suppression Relation of Alarms (OTN).......................................................................................................................40
1.7.1 Suppression of OTN Optical-Layer Alarms..............................................................................................................40
1.7.2 Suppression of OTN Electrical-Layer Alarms..........................................................................................................41
1.7.3 Suppression Between Alarms Related to SDH Services and Other Common Equipment Alarms...........................43
1.8 Suppression Relation of Alarms (OCS)........................................................................................................................44
1.9 Performance Event Suppression by Alarms.................................................................................................................45
2 Alarm List......................................................................................................................................47
2.1 Product Alarm List.......................................................................................................................................................48
2.1.1 Alarm List A..............................................................................................................................................................48
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xx

OptiX OSN 8800/6800/3800
2.1.2 Alarm List B..............................................................................................................................................................49

2.1.3 Alarm List C..............................................................................................................................................................50
2.1.4 Alarm List D..............................................................................................................................................................51
2.1.5 Alarm List E..............................................................................................................................................................52
2.1.6 Alarm List F...............................................................................................................................................................54
2.1.7 Alarm List G..............................................................................................................................................................55
2.1.8 Alarm List H..............................................................................................................................................................55
2.1.9 Alarm List I...............................................................................................................................................................56
2.1.10 Alarm List J.............................................................................................................................................................56
2.1.11 Alarm List K............................................................................................................................................................56
2.1.12 Alarm List L............................................................................................................................................................57
2.1.13 Alarm List M...........................................................................................................................................................59
2.1.14 Alarm List N............................................................................................................................................................61
2.1.15 Alarm List O............................................................................................................................................................62
2.1.16 Alarm List P.............................................................................................................................................................73
2.1.17 Alarm List R............................................................................................................................................................75
2.1.18 Alarm List S.............................................................................................................................................................76
2.1.19 Alarm List T............................................................................................................................................................79
2.1.20 Alarm List V............................................................................................................................................................80
2.1.21 Alarm List W...........................................................................................................................................................80
2.1.22 Alarm List X............................................................................................................................................................81
2.2 Board Alarm List..........................................................................................................................................................81
2.2.1 APIU Board Alarm List.............................................................................................................................................81
2.2.2 ATE Board Alarm List..............................................................................................................................................81
2.2.3 AUX Board Alarm List.............................................................................................................................................82
2.2.4 BMD4 Board Alarm List...........................................................................................................................................83
2.2.5 BMD8 Board Alarm List...........................................................................................................................................83
2.2.6 BPA Board Alarm List..............................................................................................................................................84
2.2.7 CMR1 Board Alarm List...........................................................................................................................................84
2.2.10 CRPC Board Alarm List..........................................................................................................................................84
2.2.11 D40V Board Alarm List..........................................................................................................................................85
2.2.12 D40 Board Alarm List.............................................................................................................................................85
2.2.13 DAS1 Board Alarm List..........................................................................................................................................86
2.2.14 DCU Board Alarm List............................................................................................................................................86
2.2.15 DCP Board Alarm List............................................................................................................................................86
2.2.16 DFIU Board Alarm List...........................................................................................................................................87
2.2.17 DMR1 Board Alarm List.........................................................................................................................................88
2.2.18 EAS2 Board Alarm List..........................................................................................................................................88
2.2.19 ECOM Board Alarm List........................................................................................................................................89
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxi

OptiX OSN 8800/6800/3800
2.2.20 EFI Board Alarm List..............................................................................................................................................89

2.2.21 EFI1 Board Alarm List............................................................................................................................................90
2.2.22 EFI2 Board Alarm List............................................................................................................................................90
2.2.23 EGSH Board Alarm List..........................................................................................................................................90
2.2.24 ELQX Board Alarm List.........................................................................................................................................91
2.2.25 ENQ2 Board Alarm List..........................................................................................................................................93
2.2.26 EG16 Board Alarm List...........................................................................................................................................95
2.2.27 EX2 Board Alarm List.............................................................................................................................................96
2.2.28 FAN Board Alarm List............................................................................................................................................97
2.2.29 FIU Board Alarm List..............................................................................................................................................98
2.2.30 GFU Board Alarm List............................................................................................................................................99
2.2.31 HBA Board Alarm List............................................................................................................................................99
2.2.32 HSC1 Board Alarm List........................................................................................................................................100
2.2.33 ITL Board Alarm List............................................................................................................................................100
2.2.34 L4G Board Alarm List...........................................................................................................................................101
2.2.35 LDGD Board Alarm List.......................................................................................................................................102
2.2.36 LDGS Board Alarm List........................................................................................................................................104
2.2.37 LDM Board Alarm List.........................................................................................................................................105
2.2.38 LDMD Board Alarm List......................................................................................................................................107
2.2.39 LDMS Board Alarm List.......................................................................................................................................108
2.2.40 LDX Board Alarm List..........................................................................................................................................110
2.2.41 LEM24 Board Alarm List......................................................................................................................................111
2.2.42 LEX4 Board Alarm List........................................................................................................................................113
2.2.43 LOA Board Alarm List..........................................................................................................................................114
2.2.44 LOG Board Alarm List..........................................................................................................................................115
2.2.45 LOM Board Alarm List.........................................................................................................................................118
2.2.46 LQG Board Alarm List..........................................................................................................................................120
2.2.47 LQMD Board Alarm List......................................................................................................................................121
2.2.48 LQMS Board Alarm List.......................................................................................................................................125
2.2.49 LQM Board Alarm List.........................................................................................................................................128
2.2.50 LSC Board Alarm List...........................................................................................................................................129
2.2.51 LSQ Board Alarm List..........................................................................................................................................130
2.2.52 LSXLR Board Alarm List.....................................................................................................................................131
2.2.53 LSXL Board Alarm List........................................................................................................................................134
2.2.54 LSXR Board Alarm List........................................................................................................................................136
2.2.55 LSX Board Alarm List..........................................................................................................................................137
2.2.56 LTX Board Alarm List..........................................................................................................................................142
2.2.57 LWX2 Board Alarm List.......................................................................................................................................143
2.2.58 LWXD Board Alarm List......................................................................................................................................144
2.2.59 LWXS Board Alarm List.......................................................................................................................................144
2.2.60 M40V Board Alarm List........................................................................................................................................146
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxii

OptiX OSN 8800/6800/3800
2.2.61 M40 Board Alarm List..........................................................................................................................................147

2.2.62 MCA4 Board Alarm List.......................................................................................................................................147
2.2.63 MCA8 Board Alarm List.......................................................................................................................................147
2.2.64 MR2 Board Alarm List..........................................................................................................................................148
2.2.67 MR8V Board Alarm List.......................................................................................................................................148
2.2.68 ND2 Board Alarm List..........................................................................................................................................149
2.2.69 NO2 Board Alarm List..........................................................................................................................................158
2.2.70 NPO2 Board Alarm List........................................................................................................................................160
2.2.71 NPO2E Board Alarm List......................................................................................................................................165
2.2.72 NQ2 Board Alarm List..........................................................................................................................................166
2.2.73 NS2 Board Alarm List...........................................................................................................................................174
2.2.76 OAU1 Board Alarm List.......................................................................................................................................191
2.2.77 OBU1 Board Alarm List........................................................................................................................................192
2.2.78 OBU2 Board Alarm List........................................................................................................................................193
2.2.79 OLP Board Alarm List..........................................................................................................................................194
2.2.80 OPM8 Board Alarm List.......................................................................................................................................195
2.2.81 PIU Board Alarm List............................................................................................................................................195
2.2.82 PND2 Board Alarm List........................................................................................................................................195
2.2.83 PTQX Board Alarm List........................................................................................................................................197
2.2.84 RAU1 Board Alarm List........................................................................................................................................199
2.2.85 RAU2 Board Alarm List........................................................................................................................................199
2.2.86 RDU9 Board Alarm List........................................................................................................................................200
2.2.87 RMU9 Board Alarm List.......................................................................................................................................200
2.2.88 ROAM Board Alarm List......................................................................................................................................201
2.2.89 SBM2 Board Alarm List........................................................................................................................................201
2.2.90 SC1 Board Alarm List...........................................................................................................................................201
2.2.91 SC2 Board Alarm List...........................................................................................................................................202
2.2.92 SCC Board Alarm List..........................................................................................................................................202
2.2.93 SCS Board Alarm List...........................................................................................................................................208
2.2.94 SFIU Board Alarm List.........................................................................................................................................209
2.2.95 ST2 Board Alarm List...........................................................................................................................................209
2.2.96 SF64 Board Alarm List..........................................................................................................................................209
2.2.97 SF64A Board Alarm List.......................................................................................................................................210
2.2.98 SFD64 Board Alarm List.......................................................................................................................................211
2.2.99 SL64 Board Alarm List.........................................................................................................................................212
2.2.100 SLH41 Board Alarm List....................................................................................................................................213
2.2.101 SLD64 Board Alarm List....................................................................................................................................213
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxiii

OptiX OSN 8800/6800/3800
2.2.102 SLO16 Board Alarm List....................................................................................................................................214

2.2.103 SLQ16 Board Alarm List....................................................................................................................................215
2.2.104 SLQ64 Board Alarm List....................................................................................................................................215
2.2.105 STG Board Alarm List........................................................................................................................................216
2.2.106 STI Board Alarm List..........................................................................................................................................216
2.2.107 SXM Board Alarm List.......................................................................................................................................216
2.2.108 SXH Board Alarm List........................................................................................................................................217
2.2.109 TBE Board Alarm List........................................................................................................................................217
2.2.110 TD20 Board Alarm List.......................................................................................................................................218
2.2.111 TDC Board Alarm List........................................................................................................................................218
2.2.112 TDG Board Alarm List........................................................................................................................................218
2.2.113 TDX Board Alarm List........................................................................................................................................219
2.2.114 TEM28 Board Alarm List....................................................................................................................................222
2.2.115 THA Board Alarm List........................................................................................................................................224
2.2.116 TM20 Board Alarm List......................................................................................................................................225
2.2.117 TMX Board Alarm List.......................................................................................................................................225
2.2.118 TOA Board Alarm List........................................................................................................................................229
2.2.119 TOG Board Alarm List........................................................................................................................................231
2.2.120 TOM Board Alarm List.......................................................................................................................................232
2.2.121 TOX Board Alarm List........................................................................................................................................235
2.2.122 TQM Board Alarm List.......................................................................................................................................236
2.2.123 TQS Board Alarm List........................................................................................................................................238
2.2.124 TQX Board Alarm List........................................................................................................................................240
2.2.125 TSXL Board Alarm List......................................................................................................................................244
2.2.126 USXH Board Alarm List.....................................................................................................................................246
2.2.127 UXCH Board Alarm List.....................................................................................................................................247
2.2.128 UXCM Board Alarm List....................................................................................................................................247
2.2.129 UXCT Board Alarm List.....................................................................................................................................248
2.2.130 VA1 Board Alarm List........................................................................................................................................249
2.2.131 VA4 Board Alarm List........................................................................................................................................249
2.2.132 WMU Board Alarm List......................................................................................................................................250
2.2.133 WSD9 Board Alarm List.....................................................................................................................................250
2.2.134 WSM9 Board Alarm List....................................................................................................................................251
2.2.135 WSMD2 Board Alarm List..................................................................................................................................251
2.2.138 XCH Board Alarm List........................................................................................................................................253
2.2.139 XCM Board Alarm List.......................................................................................................................................255
2.2.140 XCS Board Alarm List........................................................................................................................................255
2.2.141 XCT Board Alarm List........................................................................................................................................255
3 Clearing Common Alarms.......................................................................................................256
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxiv

OptiX OSN 8800/6800/3800
3.1 B1_EXC......................................................................................................................................................................259
3.1.1 B1_EXC (OCS).......................................................................................................................................................259
3.1.2 B1_EXC (OTN).......................................................................................................................................................262
3.2 BEFFEC_EXC............................................................................................................................................................266
3.3 BOOTROM_BAD......................................................................................................................................................269
3.3.1 BOOTROM_BAD (OCS).......................................................................................................................................270
3.3.2 BOOTROM_BAD (OTN).......................................................................................................................................271
3.4 BUS_ERR...................................................................................................................................................................272
3.4.1 BUS_ERR (OCS)....................................................................................................................................................273
3.4.2 BUS_ERR (OTN)....................................................................................................................................................276
3.5 CHAN_LOS...............................................................................................................................................................278
3.6 CLIENT_PORT_PS...................................................................................................................................................281
3.7 COMMUN_FAIL.......................................................................................................................................................283
3.7.1 COMMUN_FAIL (OCS)........................................................................................................................................284
3.7.2 COMMUN_FAIL (OTN)........................................................................................................................................285
3.8 ETH_8B10B_ERR.....................................................................................................................................................291
3.9 EX_ETHOAM_CC_LOS...........................................................................................................................................292
3.9.1 EX_ETHOAM_CC_LOS (OCS)............................................................................................................................293
3.9.2 EX_ETHOAM_CC_LOS (OTN)............................................................................................................................294
3.10 FC_LINK_ERR........................................................................................................................................................296
3.11 FC_SYNC_LOS.......................................................................................................................................................299
3.12 IN_PWR_HIGH.......................................................................................................................................................301
3.12.1 IN_PWR_HIGH (OCS).........................................................................................................................................301
3.12.2 IN_PWR_HIGH (OTN)........................................................................................................................................303
3.13 IN_PWR_LOW........................................................................................................................................................305
3.13.1 IN_PWR_LOW (OCS)..........................................................................................................................................306
3.13.2 IN_PWR_LOW (OTN).........................................................................................................................................307
3.14 INTRA_OTU_PS.....................................................................................................................................................311
3.15 LASER_MODULE_MISMATCH...........................................................................................................................313
3.16 LINK_ERR...............................................................................................................................................................314
3.16.1 LINK_ERR (OCS)................................................................................................................................................314
3.16.2 LINK_ERR (OTN)................................................................................................................................................316
3.17 LOOP_ALM.............................................................................................................................................................319
3.17.1 LOOP_ALM (OCS)..............................................................................................................................................319
3.17.2 LOOP_ALM (OTN)..............................................................................................................................................322
3.18 LPT_ACTIVE..........................................................................................................................................................323
3.19 LSR_WILL_DIE......................................................................................................................................................326
3.20 MS_AIS....................................................................................................................................................................327
3.20.1 MS_AIS (OCS)......................................................................................................................................................327
3.20.2 MS_AIS (OTN).....................................................................................................................................................329
3.21 MS_RDI....................................................................................................................................................................331
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxv

OptiX OSN 8800/6800/3800
3.21.1 MS_RDI (OCS).....................................................................................................................................................331

3.21.2 MS_RDI (OTN).....................................................................................................................................................332
3.22 MUT_LOS................................................................................................................................................................335
3.23 OA_LOW_GAIN.....................................................................................................................................................337
3.24 ODU_SNCP_PS.......................................................................................................................................................340
3.25 ODUk_PM_AIS.......................................................................................................................................................342
3.26 ODUk_PM_BDI.......................................................................................................................................................346
3.27 ODUk_PM_DEG......................................................................................................................................................348
3.28 ODUk_PM_EXC......................................................................................................................................................350
3.29 ODUk_PM_SSF.......................................................................................................................................................353
3.30 OMS_FDI.................................................................................................................................................................355
3.31 OSC_LOS.................................................................................................................................................................357
3.32 OTS_LOS.................................................................................................................................................................358
3.33 OTUk_LOF..............................................................................................................................................................359
3.34 OTUk_SSF...............................................................................................................................................................363
3.35 OUT_PWR_HIGH...................................................................................................................................................365
3.36 PORT_MODULE_OFFLINE..................................................................................................................................366
3.37 POWER_FAIL.........................................................................................................................................................368
3.38 PUMP_COOL_EXC................................................................................................................................................371
3.39 R_LOF......................................................................................................................................................................372
3.39.1 R_LOF (OCS)........................................................................................................................................................373
3.39.2 R_LOF (OTN).......................................................................................................................................................375
3.40 R_LOS......................................................................................................................................................................379
3.40.1 R_LOS (OCS)........................................................................................................................................................380
3.40.2 R_LOS (OTN).......................................................................................................................................................383
3.41 R_OOF......................................................................................................................................................................388
3.42 R_SLIP.....................................................................................................................................................................391
3.43 REM_SF...................................................................................................................................................................394
3.44 REMOTE_FAULT...................................................................................................................................................395
3.45 SECU_ALM.............................................................................................................................................................397
3.46 SUBRACK_ID_CONFLICT....................................................................................................................................398
3.47 SUM_INPWR_LOW................................................................................................................................................399
3.48 SWDL_NEPKGCHECK..........................................................................................................................................401
3.49 TD.............................................................................................................................................................................403
3.50 TEMP_OVER...........................................................................................................................................................404
3.51 TF..............................................................................................................................................................................407
3.52 TS_CFG_MISMATCH............................................................................................................................................408
3.53 WRG_BD_TYPE.....................................................................................................................................................409
4 Clearing Alarms.........................................................................................................................412
4.1 AD_CHECK_FAIL....................................................................................................................................................425
4.2 ALC_ADJUST_FAIL................................................................................................................................................426
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxvi

OptiX OSN 8800/6800/3800
4.3 ALC_WAIT_ADJUST...............................................................................................................................................428
4.4 ALS_ACTIVE............................................................................................................................................................429
4.5 ALS_TRIGGERED....................................................................................................................................................430
4.6 ALM_ALS..................................................................................................................................................................431
4.7 ALM_GFP_dCSF.......................................................................................................................................................432
4.8 ALM_GFP_dLFD......................................................................................................................................................433
4.9 ALM_HANGUP.........................................................................................................................................................435
4.10 TC_OEI....................................................................................................................................................................436
4.11 TC_REI.....................................................................................................................................................................438
4.12 APE_ADJUST_FAIL...............................................................................................................................................440
4.13 APE_ADJUST_PEND.............................................................................................................................................441
4.14 APS_FAIL................................................................................................................................................................442
4.15 APS_INDI................................................................................................................................................................443
4.16 APS_MANUAL_STOP............................................................................................................................................446
4.17 ASE_NOT_CALIBRATE........................................................................................................................................448
4.18 AU_AIS....................................................................................................................................................................448
4.19 AU_LOP...................................................................................................................................................................451
4.20 B1_SD......................................................................................................................................................................453
4.20.1 B1_SD (OCS)........................................................................................................................................................453
4.20.2 B1_SD (OTN)........................................................................................................................................................455
4.21 BD_LEDTEST.........................................................................................................................................................456
4.22 B2_EXC....................................................................................................................................................................457
4.23 B2_SD......................................................................................................................................................................459
4.24 B3_EXC....................................................................................................................................................................461
4.25 B3_EXC_VC3..........................................................................................................................................................463
4.26 B3_EXC_VC4..........................................................................................................................................................465
4.27 B3_SD......................................................................................................................................................................467
4.28 B3_SD_VC3.............................................................................................................................................................470
4.29 B3_SD_VC4.............................................................................................................................................................472
4.30 BD_NOT_INSTALLED..........................................................................................................................................474
4.31 BD_STATUS............................................................................................................................................................475
4.31.1 BD_STATUS (OCS).............................................................................................................................................475
4.31.2 BD_STATUS (OTN).............................................................................................................................................477
4.32 BIOS_STATUS........................................................................................................................................................478
4.33 BWUTILIZATION_OVER......................................................................................................................................479
4.34 CFCARD_FAILED..................................................................................................................................................481
4.35 BDID_ERROR.........................................................................................................................................................481
4.36 C2_VCAIS................................................................................................................................................................482
4.37 CHAN_ADD............................................................................................................................................................484
4.38 CHIP_ABN...............................................................................................................................................................485
4.39 CLIENT_PROT_NOTSTART.................................................................................................................................486
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxvii

OptiX OSN 8800/6800/3800
4.40 CLIENT_PORT_STA_INDI....................................................................................................................................487
4.41 CLK_LOCK_FAIL..................................................................................................................................................488
4.42 CLK_NO_TRACE_MODE......................................................................................................................................490
4.43 COM_EXTECC_FULL............................................................................................................................................492
4.44 CRC4_CROSSTR....................................................................................................................................................492
4.45 DB_RESTORE_FAIL..............................................................................................................................................493
4.46 DBPS_ABNORMAL...............................................................................................................................................495
4.47 DBMS_DELETE......................................................................................................................................................496
4.48 DBMS_ERROR........................................................................................................................................................497
4.49 DBMS_PROTECT_MODE.....................................................................................................................................499
4.50 DCM_INSUFF.........................................................................................................................................................500
4.51 DCNSIZE_OVER....................................................................................................................................................501
4.52 DERIVED_PWR_ERROR.......................................................................................................................................502
4.53 DLAG_PROTECT_FAIL........................................................................................................................................503
4.54 DSP_LOAD_FAIL...................................................................................................................................................505
4.55 EFI_TYPE_MISMATCH.........................................................................................................................................506
4.56 ERPS_IN_PROTECTION........................................................................................................................................507
4.57 ETH_APS_LOST.....................................................................................................................................................508
4.58 ETH_APS_PATH_MISMATCH.............................................................................................................................510
4.59 ETH_APS_SWITCH_FAIL.....................................................................................................................................511
4.60 ETH_APS_TYPE_MISMATCH..............................................................................................................................513
4.61 ETH_CFM_AIS........................................................................................................................................................515
4.62 ETH_CFM_LOC......................................................................................................................................................516
4.63 ETH_CFM_MISMERGE.........................................................................................................................................518
4.64 ETH_CFM_MACSTATUS......................................................................................................................................519
4.65 ETH_CFM_RDI.......................................................................................................................................................520
4.66 ETH_CFM_UNEXPERI..........................................................................................................................................522
4.67 ETH_EFM_DF.........................................................................................................................................................523
4.68 ETH_EFM_EVENT.................................................................................................................................................525
4.69 ETH_EFM_LOOPBACK.........................................................................................................................................526
4.70 ETH_EFM_REMFAULT.........................................................................................................................................527
4.71 ETH_LINK_DOWN................................................................................................................................................529
4.72 ETH_LOS.................................................................................................................................................................530
4.73 ETH_MISCONNECT..............................................................................................................................................533
4.74 ETH_NO_FLOW.....................................................................................................................................................534
4.75 ETH_SERVICE_CONFIG_FAIL............................................................................................................................536
4.76 ETHOAM_DISCOVER_FAIL................................................................................................................................537
4.77 ETHOAM_RMT_CRIT_FAULT............................................................................................................................539
4.78 ETHOAM_RMT_LOOP..........................................................................................................................................540
4.79 ETHOAM_RMT_SD...............................................................................................................................................541
4.80 ETHOAM_SELF_LOOP.........................................................................................................................................542
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxviii

OptiX OSN 8800/6800/3800
4.81 ETHOAM_VCG_SELF_LOOP...............................................................................................................................544
4.82 EX_ETHOAM_MPID_CNFLCT............................................................................................................................545
4.83 EXT_MODULE_OFFLINE.....................................................................................................................................546
4.84 EXT_SYNC_LOS....................................................................................................................................................547
4.85 EXT_TIME_LOC.....................................................................................................................................................549
4.86 FAN_FAIL...............................................................................................................................................................551
4.87 FAN_FAULT...........................................................................................................................................................551
4.88 FDBSIZEALM_ELAN............................................................................................................................................552
4.89 FEATURE_WITHOUT_LICENSE.........................................................................................................................553
4.90 FC_8B10BERR_OVER...........................................................................................................................................554
4.91 FCS_ERR.................................................................................................................................................................555
4.92 FEC_LOF.................................................................................................................................................................557
4.93 FEC_OOF.................................................................................................................................................................558
4.94 FIBERTYPE_MIS....................................................................................................................................................559
4.95 FLOW_OVER..........................................................................................................................................................560
4.96 FPGA_ABN..............................................................................................................................................................561
4.97 FSELECT_STG........................................................................................................................................................562
4.98 FWD_PKT_LOSS....................................................................................................................................................563
4.99 GAINDATA_MIS....................................................................................................................................................564
4.100 GFP_UPM..............................................................................................................................................................565
4.101 HARD_BAD..........................................................................................................................................................566
4.102 HARD_ERR...........................................................................................................................................................570
4.103 HARD_NONSUPPORT.........................................................................................................................................573
4.104 HP_LOM................................................................................................................................................................574
4.105 HP_RDI..................................................................................................................................................................575
4.106 HP_REI...................................................................................................................................................................576
4.107 HP_SLM.................................................................................................................................................................577
4.108 HP_TIM..................................................................................................................................................................579
4.109 HP_UNEQ..............................................................................................................................................................581
4.110 HSC_UNAVAIL....................................................................................................................................................583
4.111 IN_PWR_ABN.......................................................................................................................................................584
4.112 INSERTION_LOSS_HIGH...................................................................................................................................586
4.113 INTRA_OTU_STA_INDI......................................................................................................................................587
4.114 IPA_SHUT.............................................................................................................................................................589
4.115 J0_MM....................................................................................................................................................................590
4.116 K1_K2_M...............................................................................................................................................................591
4.117 K2_M......................................................................................................................................................................592
4.118 L_SYNC.................................................................................................................................................................593
4.119 LAG_DOWN..........................................................................................................................................................594
4.120 LAG_MEMBER_DOWN......................................................................................................................................595
4.121 LAG_PORT_FAIL.................................................................................................................................................598
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxix

OptiX OSN 8800/6800/3800
4.122 LAG_VC_PORT_FAIL.........................................................................................................................................599
4.123 LAN_LOC..............................................................................................................................................................600
4.124 LASER_HAZARD_WARNING............................................................................................................................602
4.125 LASER_MOD_ERR..............................................................................................................................................603
4.126 LASER_SHUT.......................................................................................................................................................604
4.127 LCS_DAYS_OF_GRACE.....................................................................................................................................605
4.128 LCS_EXPIRED......................................................................................................................................................607
4.129 LCS_FILE_NOT_EXIST.......................................................................................................................................608
4.130 LCAS_FOPR..........................................................................................................................................................608
4.131 LCAS_FOPT..........................................................................................................................................................610
4.132 LCAS_PLCR..........................................................................................................................................................611
4.133 LCAS_PLCT..........................................................................................................................................................612
4.134 LCAS_TLCR..........................................................................................................................................................614
4.135 LCAS_TLCT..........................................................................................................................................................615
4.136 LOCAL_FAULT....................................................................................................................................................616
4.137 LOCK_CUR_FAIL................................................................................................................................................617
4.138 LOCKPOW_MIS...................................................................................................................................................618
4.139 LP_RDI_VC3.........................................................................................................................................................619
4.140 LP_SLM_VC3........................................................................................................................................................620
4.141 LP_UNEQ_VC3.....................................................................................................................................................621
4.142 LPT_RFI.................................................................................................................................................................622
4.143 LSR_BCM_ALM...................................................................................................................................................623
4.144 LSR_COOL_ALM.................................................................................................................................................624
4.145 LSR_INVALID......................................................................................................................................................625
4.146 LSR_NO_FITED....................................................................................................................................................626
4.147 LTI..........................................................................................................................................................................627
4.148 MAC_FCS_EXC....................................................................................................................................................629
4.149 MAINBD_SUBBD_MISMATCH.........................................................................................................................631
4.150 MCLAG_CFG_MISMATCH................................................................................................................................632
4.151 MCSP_PATH_LOCV............................................................................................................................................633
4.152 MOD_COM_FAIL.................................................................................................................................................634
4.153 MODULE_ADJUST_FAIL...................................................................................................................................635
4.154 MODULE_COOLCUR_OVER.............................................................................................................................636
4.155 MODULE_RATE_MISMATCH...........................................................................................................................637
4.156 MODULE_TEMP_OVER......................................................................................................................................638
4.157 MODULEFILE_UPDATE_FAIL..........................................................................................................................639
4.158 MPLS_PW_AIS.....................................................................................................................................................640
4.159 MPLS_PW_LOCV.................................................................................................................................................641
4.160 MPLS_PW_OAMFAIL..........................................................................................................................................643
4.161 MPLS_PW_RDI.....................................................................................................................................................645
4.162 MPLS_PW_SD.......................................................................................................................................................646
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxx

OptiX OSN 8800/6800/3800
4.163 MPLS_PW_SF.......................................................................................................................................................648
4.164 MPLS_PW_UNEXPMEG......................................................................................................................................649
4.165 MPLS_PW_UNEXPMEP......................................................................................................................................652
4.166 MPLS_PW_UNEXPPER.......................................................................................................................................653
4.167 MPLS_TUNNEL_AIS...........................................................................................................................................654
4.168 MPLS_TUNNEL_LOCV.......................................................................................................................................656
4.169 MPLS_TUNNEL_OAMFAIL................................................................................................................................658
4.170 MPLS_TUNNEL_RDI...........................................................................................................................................660
4.171 MPLS_TUNNEL_SD.............................................................................................................................................661
4.172 MPLS_TUNNEL_SF.............................................................................................................................................662
4.173 MPLS_TUNNEL_UNEXPMEG............................................................................................................................663
4.174 MPLS_TUNNEL_UNEXPMEP............................................................................................................................666
4.175 MPLS_TUNNEL_UNEXPPER.............................................................................................................................668
4.176 MS_APS_INDI_EX...............................................................................................................................................669
4.177 MS_CROSSTR.......................................................................................................................................................670
4.178 MS_REI..................................................................................................................................................................672
4.179 MS_SNCP_PS........................................................................................................................................................672
4.180 MS_SNCP_STA_INDI..........................................................................................................................................674
4.181 MUT_TLOS...........................................................................................................................................................675
4.182 MULTI_RPL_OWNER..........................................................................................................................................677
4.183 NEBD_XC_DIF.....................................................................................................................................................678
4.184 NESF_LOST..........................................................................................................................................................679
4.185 NESTATE_INSTALL............................................................................................................................................680
4.186 NO_BD_PARA......................................................................................................................................................681
4.187 NO_BD_SOFT.......................................................................................................................................................682
4.188 NO_ELABEL.........................................................................................................................................................683
4.189 NODEID_MM........................................................................................................................................................684
4.190 NTP_SYNC_FAIL.................................................................................................................................................685
4.191 NULL_SEND.........................................................................................................................................................686
4.192 OA_HIGH_GAIN..................................................................................................................................................687
4.193 OCH_FDI...............................................................................................................................................................688
4.194 OCH_FDI_O..........................................................................................................................................................689
4.195 OCH_FDI_P...........................................................................................................................................................690
4.196 OCH_LOS_P..........................................................................................................................................................691
4.197 OCH_OCI...............................................................................................................................................................692
4.198 OCH_SSF...............................................................................................................................................................693
4.199 OCH_SSF_O..........................................................................................................................................................694
4.200 OCH_SSF_P...........................................................................................................................................................695
4.201 ODU_AIS...............................................................................................................................................................696
4.202 ODU_LCK..............................................................................................................................................................697
4.203 ODU_OCI...............................................................................................................................................................698
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxi

OptiX OSN 8800/6800/3800
4.204 ODU_SNCP_STA_INDI........................................................................................................................................699
4.205 ODUk_LOFLOM...................................................................................................................................................701
4.206 ODUk_PM_LCK....................................................................................................................................................702
4.207 ODUk_PM_OCI.....................................................................................................................................................703
4.208 ODUk_PM_TIM....................................................................................................................................................704
4.209 ODUk_TCMn_AIS................................................................................................................................................706
4.210 ODUk_TCMn_BDI................................................................................................................................................707
4.211 ODUk_TCMn_DEG...............................................................................................................................................708
4.212 ODUk_TCMn_EXC...............................................................................................................................................709
4.213 ODUk_TCMn_LCK...............................................................................................................................................711
4.214 ODUk_TCMn_LTC...............................................................................................................................................712
4.215 ODUk_TCMn_OCI................................................................................................................................................713
4.216 ODUk_TCMn_SSF................................................................................................................................................714
4.217 ODUk_TCMn_TIM................................................................................................................................................715
4.218 ODUKSP_PS..........................................................................................................................................................716
4.219 ODUKSP_STA_INDI............................................................................................................................................718
4.220 OH_LOOP..............................................................................................................................................................720
4.221 OLP_PS..................................................................................................................................................................721
4.222 OLP_STA_INDI.....................................................................................................................................................723
4.223 OMS_BDI...............................................................................................................................................................725
4.224 OMS_BDI_O..........................................................................................................................................................725
4.225 OMS_BDI_P..........................................................................................................................................................726
4.226 OMS_FDI_O..........................................................................................................................................................727
4.227 OMS_FDI_P...........................................................................................................................................................728
4.228 OMS_LOS_P..........................................................................................................................................................729
4.229 OMS_SSF...............................................................................................................................................................730
4.230 OMS_SSF_O..........................................................................................................................................................731
4.231 OMS_SSF_P...........................................................................................................................................................732
4.232 OOL........................................................................................................................................................................733
4.233 OOS_LOST............................................................................................................................................................734
4.234 OPA_FAIL_INDI...................................................................................................................................................735
4.235 OPU1_MSIM..........................................................................................................................................................736
4.236 OPU1_VCAT_SQM...............................................................................................................................................737
4.237 OPU1_VCAT_VcPLM..........................................................................................................................................738
4.238 OPU2_MSIM..........................................................................................................................................................739
4.239 OPU3_MSIM..........................................................................................................................................................740
4.240 OPU4_MSIM..........................................................................................................................................................741
4.241 OPUk_CSF.............................................................................................................................................................742
4.242 OPUk_PLM............................................................................................................................................................743
4.243 OSC_BDI................................................................................................................................................................744
4.244 OSC_DEG..............................................................................................................................................................744
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxii

OptiX OSN 8800/6800/3800
4.245 OSC_RDI................................................................................................................................................................745
4.246 OTS_BDI................................................................................................................................................................746
4.247 OTS_BDI_O...........................................................................................................................................................747
4.248 OTS_BDI_P............................................................................................................................................................748
4.249 OTS_LOS_O..........................................................................................................................................................749
4.250 OTS_LOS_P...........................................................................................................................................................750
4.251 OTS_TIM...............................................................................................................................................................751
4.252 OTU_AIS................................................................................................................................................................752
4.253 OTU_LOF..............................................................................................................................................................753
4.254 OTU_LOM.............................................................................................................................................................754
4.255 OTUk_AIS..............................................................................................................................................................755
4.256 OTUk_BDI.............................................................................................................................................................756
4.257 OTUk_DEG............................................................................................................................................................757
4.258 OTUk_EXC............................................................................................................................................................758
4.259 OTUk_LOM...........................................................................................................................................................759
4.260 OTUk_TIM.............................................................................................................................................................760
4.261 OUT_PWR_ABN...................................................................................................................................................762
4.262 OUT_PWR_LOW..................................................................................................................................................763
4.263 OWSP_PS...............................................................................................................................................................764
4.264 OWSP_STA_INDI.................................................................................................................................................765
4.265 PASSWORD_NEED_CHANGE...........................................................................................................................767
4.266 PATCH_ACT_TIMEOUT.....................................................................................................................................768
4.267 PATCH_DEACT_TIMEOUT................................................................................................................................769
4.268 PATCH_PKGERR.................................................................................................................................................770
4.269 PM_BDI..................................................................................................................................................................770
4.270 PM_BEI..................................................................................................................................................................772
4.271 PM_BIP8_OVER...................................................................................................................................................773
4.272 PM_BIP8_SD.........................................................................................................................................................774
4.273 PM_TIM.................................................................................................................................................................776
4.274 PORT_EXC_TRAFFIC..........................................................................................................................................776
4.275 PORTSWITCH_FAIL............................................................................................................................................778
4.276 POWER_ABNORMAL.........................................................................................................................................778
4.277 POWER_DIFF_OVER...........................................................................................................................................780
4.278 PRBS_LSS..............................................................................................................................................................781
4.279 PTP_SOURCE_SWITCH......................................................................................................................................782
4.280 PTP_TIMESTAMP_ABN......................................................................................................................................784
4.281 PUM_BCM_ALM..................................................................................................................................................786
4.282 PUM_TEM_ALM..................................................................................................................................................787
4.283 PW_NO_TRAFFIC................................................................................................................................................788
4.284 PWAPS_LOST.......................................................................................................................................................790
4.285 PWAPS_PATH_MISMATCH...............................................................................................................................791
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxiii

OptiX OSN 8800/6800/3800
4.286 PWAPS_SWITCH_FAIL.......................................................................................................................................793
4.287 PWAPS_TYPE_MISMATCH...............................................................................................................................795
4.288 R_LOC....................................................................................................................................................................796
4.288.1 R_LOC (OCS).....................................................................................................................................................796
4.288.2 R_LOC (OTN).....................................................................................................................................................797
4.289 RELAY_ALARM_CRITICAL..............................................................................................................................798
4.290 RELAY_ALARM_IGNORE.................................................................................................................................800
4.291 RELAY_ALARM_MAJOR ..................................................................................................................................801
4.292 RELAY_ALARM_MINOR ..................................................................................................................................802
4.293 REM_SD................................................................................................................................................................804
4.294 RL_CRITICAL_HI................................................................................................................................................805
4.295 RL_CRITICAL_LOW............................................................................................................................................806
4.296 RM_RLOS..............................................................................................................................................................807
4.297 RS_CROSSTR........................................................................................................................................................807
4.298 RTC_FAIL..............................................................................................................................................................809
4.299 RX_POWER_ABNORMAL..................................................................................................................................810
4.300 S1_SYN_CHANGE...............................................................................................................................................811
4.301 SCC_LOC...............................................................................................................................................................812
4.302 SEC_RADIUS_FAIL.............................................................................................................................................813
4.303 SERVICE_TYPE_EXCEED_LICENSE...............................................................................................................814
4.304 SERVICE_CAPACITY_EXCEED_LICENSE.....................................................................................................815
4.305 SHELF_AREA_POWER_OVER..........................................................................................................................816
4.306 SPAN_LOSS_HIGH..............................................................................................................................................817
4.307 SPAN_LOSS_LOW...............................................................................................................................................819
4.308 SLAVE_WORKING..............................................................................................................................................820
4.309 SM_BDI..................................................................................................................................................................821
4.310 SM_BEI..................................................................................................................................................................822
4.311 SM_BIP8_OVER...................................................................................................................................................823
4.312 SM_BIP8_SD.........................................................................................................................................................825
4.313 SM_IAE..................................................................................................................................................................826
4.314 SM_TIM.................................................................................................................................................................827
4.315 SNCP_FAIL...........................................................................................................................................................828
4.316 SO_SK_MISMATCH............................................................................................................................................829
4.317 SPEED_OVER.......................................................................................................................................................830
4.318 SRV_SHUTDOWN_LD........................................................................................................................................831
4.319 SSL_CERT_NOENC.............................................................................................................................................832
4.320 SSM_LOS...............................................................................................................................................................833
4.321 SSM_QL_FAILED.................................................................................................................................................834
4.322 STORM_CUR_QUENUM_OVER........................................................................................................................835
4.323 SUBRACK_COMM_PS........................................................................................................................................836
4.324 SUBRACK_ID_MISMATCH................................................................................................................................837
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxiv

OptiX OSN 8800/6800/3800
4.325 SUBRACK_LOOP.................................................................................................................................................838
4.326 SUBRACK_TYPE_MISMATCH..........................................................................................................................839
4.327 SUM_INPWR_HI..................................................................................................................................................840
4.328 SW_SNCP_PS........................................................................................................................................................841
4.329 SW_SNCP_STA_INDI..........................................................................................................................................843
4.330 SWDL_ACTIVATED_TIMEOUT........................................................................................................................844
4.331 SWDL_AUTOMATCH_INH................................................................................................................................845
4.332 SWDL_BD_EXCLUDE.........................................................................................................................................846
4.333 SWDL_CHGMNG_NOMATCH...........................................................................................................................847
4.334 SWDL_COMMIT_FAIL........................................................................................................................................848
4.335 SWDL_INPROCESS.............................................................................................................................................849
4.336 SWDL_PKG_NOBDSOFT....................................................................................................................................850
4.337 SWDL_PKGVER_MM..........................................................................................................................................851
4.338 SWDL_ROLLBACK_FAIL..................................................................................................................................852
4.339 SYN_BAD..............................................................................................................................................................853
4.340 SYNC_C_LOS.......................................................................................................................................................855
4.341 SYNC_DISABLE...................................................................................................................................................856
4.342 SYNC_F_M_SWITCH..........................................................................................................................................857
4.343 SYNC_LOCKOFF.................................................................................................................................................859
4.344 SYNC_FAIL...........................................................................................................................................................860
4.345 SYSLOG_COMM_FAIL.......................................................................................................................................861
4.346 SYSPARA_CFDB_NOSAME...............................................................................................................................862
4.347 T_LOSEX...............................................................................................................................................................863
4.348 T_SLIP....................................................................................................................................................................864
4.349 TEM_HA................................................................................................................................................................865
4.350 TEM_LA................................................................................................................................................................866
4.351 TEST_STATUS......................................................................................................................................................867
4.352 THUNDERALM....................................................................................................................................................867
4.353 TIME_LOS.............................................................................................................................................................869
4.354 TIME_LOCK_FAIL...............................................................................................................................................870
4.355 TIME_NO_TRACE_MODE..................................................................................................................................872
4.356 TR_LOC.................................................................................................................................................................873
4.357 TU_AIS_VC3.........................................................................................................................................................875
4.358 TU_LOP_VC3........................................................................................................................................................876
4.359 TUNNEL_APS_DEGRADED...............................................................................................................................877
4.360 VCTRUNK_NO_FLOW........................................................................................................................................878
4.361 VCAT_LOA...........................................................................................................................................................879
4.361.1 VCAT_LOA (OCS).............................................................................................................................................880
4.361.2 VCAT_LOA (OTN)............................................................................................................................................881
4.362 VCAT_LOM_VC3.................................................................................................................................................882
4.363 VCAT_LOM_VC4.................................................................................................................................................883
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxv

OptiX OSN 8800/6800/3800
4.364 VLAN_SNCP_PS...................................................................................................................................................884
4.365 VOADATA_MIS...................................................................................................................................................885
4.366 W_R_FAIL.............................................................................................................................................................886
4.367 WAVE_ADD_ABN...............................................................................................................................................887
4.368 WAVE_DROP_ABN.............................................................................................................................................888
4.369 WAVEDATA_MIS................................................................................................................................................889
4.370 WAVELEN_OVER................................................................................................................................................890
4.371 XC_UNSWITCH....................................................................................................................................................891
5 Performance Event List.............................................................................................................893

5.1 Product Performance Event List.................................................................................................................................894
5.1.1 Performance Event of Check and Error Correction.................................................................................................894
5.1.2 Performance Event of Pointer Justification.............................................................................................................895
5.1.3 Performance Event of Equipment Function............................................................................................................896
5.1.4 Performance Event of Multiplex Section Bit Error.................................................................................................900
5.1.5 Performance Event of Regenerator Section Bit Error.............................................................................................901
5.1.6 Performance Event of Higher Order Path Bit Error................................................................................................901
5.1.7 Performance Event of Lower Order Path Bit Error.................................................................................................902
5.1.8 Performance Event of OTN.....................................................................................................................................903
5.1.9 Performance Event List of RMON Function...........................................................................................................916
5.1.10 TCM Performance Event ......................................................................................................................................926
5.1.11 Performance Event of FC......................................................................................................................................926
5.2 Board Performance Event List...................................................................................................................................928
5.2.1 BPA Board Performance Event List........................................................................................................................928
5.2.2 CRPC Board Performance Event List.....................................................................................................................928
5.2.3 DAS1 Board Performance Event List.....................................................................................................................929
5.2.4 D40V Board Performance Event List......................................................................................................................930
5.2.5 D40 Board Performance Event List.........................................................................................................................930
5.2.6 DCP Board Performance Event List........................................................................................................................930
5.2.7 EAS2 Board Performance Event List......................................................................................................................930
5.2.8 EGSH Board Performance Event List.....................................................................................................................931
5.2.9 ECOM Board Performance Event List....................................................................................................................932
5.2.10 ELQX Board Performance Event List...................................................................................................................933
5.2.11 ENQ2 Board Performance Event List...................................................................................................................935
5.2.12 EG16 Board Performance Event List....................................................................................................................936
5.2.13 EX2 Board Performance Event List......................................................................................................................938
5.2.14 FIU Board Performance Event List.......................................................................................................................941
5.2.15 HSC1 Board Performance Event List....................................................................................................................941
5.2.16 HBA Board Performance Event List.....................................................................................................................941
5.2.17 ITL Board Performance Event List.......................................................................................................................942
5.2.18 L4G Board Performance Event List......................................................................................................................942
5.2.19 LDGD Board Performance Event List..................................................................................................................943
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxvi

OptiX OSN 8800/6800/3800
5.2.20 LDGS Board Performance Event List...................................................................................................................945

5.2.21 LDM Board Performance Event List.....................................................................................................................947
5.2.22 LDMD Board Performance Event List..................................................................................................................949
5.2.23 LDMS Board Performance Event List..................................................................................................................951
5.2.24 LDX Board Performance Event List.....................................................................................................................952
5.2.25 LEM24 Board Performance Event List.................................................................................................................954
5.2.26 LEX4 Board Performance Event List....................................................................................................................956
5.2.27 LOA Board Performance Event List.....................................................................................................................958
5.2.28 LOG Board Performance Event List.....................................................................................................................960
5.2.29 LOM Board Performance Event List.....................................................................................................................961
5.2.30 LQMD Board Performance Event List..................................................................................................................964
5.2.31 LQMS Board Performance Event List..................................................................................................................966
5.2.32 LQM Board Performance Event List.....................................................................................................................969
5.2.33 LSC Board Performance Event List......................................................................................................................971
5.2.34 LSQ Board Performance Event List......................................................................................................................973
5.2.35 LSXLR Board Performance Event List.................................................................................................................974
5.2.36 LSXL Board Performance Event List...................................................................................................................975
5.2.37 LSXR Board Performance Event List...................................................................................................................977
5.2.38 LSX Board Performance Event List......................................................................................................................978
5.2.39 LTX Board Performance Event List......................................................................................................................981
5.2.40 LWX2 Board Performance Event List..................................................................................................................983
5.2.41 LWXD Board Performance Event List.................................................................................................................983
5.2.42 LWXS Board Performance Event List..................................................................................................................983
5.2.43 M40V Board Performance Event List...................................................................................................................984
5.2.44 M40 Board Performance Event List......................................................................................................................984
5.2.45 MCA4 Board Performance Event List..................................................................................................................984
5.2.46 MCA8 Board Performance Event List..................................................................................................................985
5.2.47 MR8V Board Performance Event List..................................................................................................................985
5.2.48 ND2 Board Performance Event List......................................................................................................................985
5.2.49 NO2 Board Performance Event List......................................................................................................................992
5.2.50 NQ2 Board Performance Event List......................................................................................................................994
5.2.51 NPO2 Board Performance Event List.................................................................................................................1001
5.2.52 NPO2E Board Performance Event List...............................................................................................................1003
5.2.53 NS2 Board Performance Event List....................................................................................................................1004
5.2.56 OAU1 Board Performance Event List.................................................................................................................1020
5.2.57 OBU1 Board Performance Event List.................................................................................................................1021
5.2.58 OBU2 Board Performance Event List.................................................................................................................1021
5.2.59 OLP Board Performance Event List....................................................................................................................1021
5.2.60 OPM8 Board Performance Event List.................................................................................................................1021
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxvii

OptiX OSN 8800/6800/3800
5.2.61 PND2 Board Performance Event List.................................................................................................................1022

5.2.62 PTQX Board Performance Event List.................................................................................................................1025
5.2.63 RAU1 Board Performance Event List.................................................................................................................1027
5.2.64 RAU2 Board Performance Event List.................................................................................................................1027
5.2.65 RDU9 Board Performance Event List.................................................................................................................1027
5.2.66 RMU9 Board Performance Event List................................................................................................................1028
5.2.67 ROAM Board Performance Event List...............................................................................................................1028
5.2.68 SCC Board Performance Event List....................................................................................................................1028
5.2.69 SC1 Board Performance Event List.....................................................................................................................1028
5.2.70 SC2 Board Performance Event List.....................................................................................................................1029
5.2.71 SFD64 Board Performance Event List................................................................................................................1029
5.2.72 SF64 Board Performance Event List...................................................................................................................1030
5.2.73 SF64A Board Performance Event List................................................................................................................1031
5.2.74 SL64 Board Performance Event List...................................................................................................................1032
5.2.75 SLD64 Board Performance Event List................................................................................................................1032
5.2.76 SLH41 Board Performance Event List................................................................................................................1033
5.2.77 SLO16 Board Performance Event List................................................................................................................1033
5.2.78 SLQ16 Board Performance Event List................................................................................................................1034
5.2.79 SLQ64 Board Performance Event List................................................................................................................1035
5.2.80 ST2 Board Performance Event List.....................................................................................................................1035
5.2.81 STG Board Performance Event List....................................................................................................................1036
5.2.82 SXM Board Performance Event List...................................................................................................................1036
5.2.83 SXH Board Performance Event List...................................................................................................................1036
5.2.84 TBE Board Performance Event List....................................................................................................................1036
5.2.85 TD20 Board Performance Event List..................................................................................................................1038
5.2.86 TDC Board Performance Event List...................................................................................................................1038
5.2.87 TDG Board Performance Event List...................................................................................................................1038
5.2.88 TDX Board Performance Event List...................................................................................................................1039
5.2.89 TEM28 Board Performance Event List...............................................................................................................1045
5.2.90 THA Board Performance Event List...................................................................................................................1047
5.2.91 TM20 Board Performance Event List.................................................................................................................1049
5.2.92 TMX Board Performance Event List...................................................................................................................1049
5.2.93 TOA Board Performance Event List...................................................................................................................1051
5.2.94 TOG Board Performance Event List...................................................................................................................1053
5.2.95 TOM Board Performance Event List...................................................................................................................1054
5.2.96 TOX Board Performance Event List...................................................................................................................1058
5.2.97 TQM Board Performance Event List...................................................................................................................1060
5.2.98 TQS Board Performance Event List....................................................................................................................1063
5.2.99 TQX Board Performance Event List...................................................................................................................1064
5.2.100 TSXL Board Performance Event List...............................................................................................................1070
5.2.101 USXH Board Performance Event List...............................................................................................................1073
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxviii

OptiX OSN 8800/6800/3800
5.2.102 UXCH Board Performance Event List..............................................................................................................1073

5.2.103 UXCM Board Performance Event List.............................................................................................................1073
5.2.104 UXCT Board Performance Event List...............................................................................................................1073
5.2.105 VA1 Board Performance Event List..................................................................................................................1073
5.2.106 VA4 Board Performance Event List..................................................................................................................1074
5.2.107 WMU Board Performance Event List...............................................................................................................1074
5.2.108 WSD9 Board Performance Event List...............................................................................................................1074
5.2.109 WSM9 Board Performance Event List..............................................................................................................1074
5.2.110 WSMD2 Board Performance Event List...........................................................................................................1074
5.2.113 XCH Board Performance Event List.................................................................................................................1075
5.2.114 XCM Board Performance Event List................................................................................................................1076
5.2.115 XCT Board Performance Event List.................................................................................................................1076
6 Handling Performance Event................................................................................................1077

6.1 AUPJCHIGH............................................................................................................................................................1083
6.2 AUPJCLOW.............................................................................................................................................................1084
6.3 AUPJCNEW.............................................................................................................................................................1085
6.4 BCV..........................................................................................................................................................................1086
6.5 BDTEMP..................................................................................................................................................................1086
6.6 CCV..........................................................................................................................................................................1087
6.7 CRC4ES....................................................................................................................................................................1088
6.8 CRC4FEES...............................................................................................................................................................1089
6.9 CRC4FESES.............................................................................................................................................................1090
6.10 CRC4FEUAS..........................................................................................................................................................1090
6.11 CRC4SES...............................................................................................................................................................1091
6.12 CRC4UAS..............................................................................................................................................................1092
6.13 DGD........................................................................................................................................................................1093
6.14 EDRPL....................................................................................................................................................................1094
6.15 EDTMP...................................................................................................................................................................1095
6.16 EDTPL....................................................................................................................................................................1095
6.17 EDWCS..................................................................................................................................................................1096
6.18 ENVTMP................................................................................................................................................................1097
6.19 ETH_CFM_LS.......................................................................................................................................................1098
6.20 ETH_CFM_SLS.....................................................................................................................................................1098
6.21 ETH_CFM_CSLS..................................................................................................................................................1099
6.22 ETH_CFM_UAS....................................................................................................................................................1100
6.23 FEC_AFT_COR_ER..............................................................................................................................................1100
6.24 FEC_AFT_COR_ERAVR......................................................................................................................................1101
6.25 FEC_AFT_CORER_FLOAT.................................................................................................................................1102
6.26 FEC_BEF_COR_ER..............................................................................................................................................1103
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xxxix

OptiX OSN 8800/6800/3800
6.27 FEC_BEF_COR_ERAVR......................................................................................................................................1104
6.28 FEC_BEF_CORER_FLOAT.................................................................................................................................1105
6.29 FEC_COR_0BIT_CNT..........................................................................................................................................1105
6.30 FEC_COR_1BIT_CNT..........................................................................................................................................1106
6.31 FEC_COR_BYTE_CNT........................................................................................................................................1107
6.32 FEC_TMP...............................................................................................................................................................1107
6.33 FEC_UNCOR_BLOCK_CNT...............................................................................................................................1108
6.34 FREQDEV..............................................................................................................................................................1109
6.35 HPBBE...................................................................................................................................................................1109
6.36 HPCSES..................................................................................................................................................................1110
6.37 HPES......................................................................................................................................................................1111
6.38 HPFEBBE...............................................................................................................................................................1112
6.39 HPFECSES.............................................................................................................................................................1113
6.40 HPFEES..................................................................................................................................................................1114
6.41 HPFESES................................................................................................................................................................1115
6.42 HPFEUAS..............................................................................................................................................................1116
6.43 HPSES....................................................................................................................................................................1117
6.44 HPUAS...................................................................................................................................................................1118
6.45 ICCLC....................................................................................................................................................................1120
6.46 ICTMP....................................................................................................................................................................1120
6.47 LSBIAS..................................................................................................................................................................1121
6.48 LSCLC....................................................................................................................................................................1122
6.49 LSIOP.....................................................................................................................................................................1123
6.50 LSOOP....................................................................................................................................................................1124
6.51 LSTMP...................................................................................................................................................................1126
6.52 MEANPATHDELAY............................................................................................................................................1127
6.53 MPLS_PW_LS.......................................................................................................................................................1127
6.54 MPLS_PW_SLS.....................................................................................................................................................1128
6.55 MPLS_PW_CSLS..................................................................................................................................................1129
6.56 MPLS_PW_UAS....................................................................................................................................................1129
6.57 MSBBE...................................................................................................................................................................1130
6.58 MSCSES.................................................................................................................................................................1131
6.59 MSES......................................................................................................................................................................1132
6.60 MSFEBBE..............................................................................................................................................................1133
6.61 MSFECSES............................................................................................................................................................1134
6.62 MSFEES.................................................................................................................................................................1135
6.63 MSFESES...............................................................................................................................................................1136
6.64 MSFEUAS..............................................................................................................................................................1136
6.65 MSSES....................................................................................................................................................................1137
6.66 MSUAS..................................................................................................................................................................1138
6.67 ODU2PMBIP8........................................................................................................................................................1139
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xl

OptiX OSN 8800/6800/3800
6.68 ODUk_PM_BBE....................................................................................................................................................1140
6.69 ODUk_PM_BBER.................................................................................................................................................1141
6.70 ODUk_PM_ES.......................................................................................................................................................1142
6.71 ODUk_PM_FEBBE...............................................................................................................................................1143
6.72 ODUk_PM_FEBBER.............................................................................................................................................1144
6.73 ODUk_PM_FEES..................................................................................................................................................1145
6.74 ODUk_PM_FESES................................................................................................................................................1145
6.75 ODUk_PM_FESESR..............................................................................................................................................1146
6.76 ODUk_PM_FEUAS...............................................................................................................................................1147
6.77 ODUk_PM_SES.....................................................................................................................................................1148
6.78 ODUk_PM_SESR..................................................................................................................................................1149
6.79 ODUk_PM_TMP....................................................................................................................................................1149
6.80 ODUk_PM_UAS....................................................................................................................................................1150
6.81 ODUk_TCMn_BBE...............................................................................................................................................1151
6.82 ODUk_TCMn_BBER............................................................................................................................................1152
6.83 ODUk_TCMn_BIAES...........................................................................................................................................1153
6.84 ODUk_TCMn_ES..................................................................................................................................................1153
6.85 ODUk_TCMn_FEBBE..........................................................................................................................................1154
6.86 ODUk_TCMn_FEBBER........................................................................................................................................1155
6.87 ODUk_TCMn_FEES..............................................................................................................................................1156
6.88 ODUk_TCMn_FESES...........................................................................................................................................1156
6.89 ODUk_TCMn_FESESR.........................................................................................................................................1157
6.90 ODUk_TCMn_FEUAS..........................................................................................................................................1158
6.91 ODUk_TCMn_IAES..............................................................................................................................................1158
6.92 ODUk_TCMn_SES................................................................................................................................................1159
6.93 ODUk_TCMn_SESR.............................................................................................................................................1160
6.94 ODUk_TCMn_TMP...............................................................................................................................................1160
6.95 ODUk_TCMn_UAS...............................................................................................................................................1161
6.96 OOPRL...................................................................................................................................................................1162
6.97 OSC_BBE...............................................................................................................................................................1163
6.98 OSC_BBER............................................................................................................................................................1163
6.99 OSC_BIAES...........................................................................................................................................................1164
6.100 OSC_ES................................................................................................................................................................1165
6.101 OSC_FEBBE........................................................................................................................................................1165
6.102 OSC_FEBBER.....................................................................................................................................................1166
6.103 OSC_FEES...........................................................................................................................................................1167
6.104 OSC_FESES.........................................................................................................................................................1167
6.105 OSC_FESESR......................................................................................................................................................1168
6.106 OSC_FEUAS........................................................................................................................................................1169
6.107 OSC_IAES............................................................................................................................................................1169
6.108 OSC_SES..............................................................................................................................................................1170
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xli

OptiX OSN 8800/6800/3800
6.109 OSC_SESR...........................................................................................................................................................1171
6.110 OSC_UAS............................................................................................................................................................1171
6.111 OSPICCV.............................................................................................................................................................1172
6.112 OSPITMP.............................................................................................................................................................1173
6.113 OTU2SMBIP8......................................................................................................................................................1174
6.114 OTUk_BBE..........................................................................................................................................................1175
6.115 OTUk_BBER........................................................................................................................................................1176
6.116 OTUk_BIAES......................................................................................................................................................1177
6.117 OTUk_ES.............................................................................................................................................................1177
6.118 OTUk_FEBBE......................................................................................................................................................1178
6.119 OTUk_FEBBER...................................................................................................................................................1179
6.120 OTUk_FEES.........................................................................................................................................................1180
6.121 OTUk_FESES......................................................................................................................................................1181
6.122 OTUk_FESESR....................................................................................................................................................1181
6.123 OTUk_FEUAS.....................................................................................................................................................1182
6.124 OTUk_IAES.........................................................................................................................................................1183
6.125 OTUk_SES...........................................................................................................................................................1183
6.126 OTUk_SESR........................................................................................................................................................1184
6.127 OTUk_TMP..........................................................................................................................................................1185
6.128 OTUk_UAS..........................................................................................................................................................1186
6.129 PCLSOP................................................................................................................................................................1187
6.130 PCLSSN................................................................................................................................................................1187
6.131 PCLSWL..............................................................................................................................................................1188
6.132 PCLSWLO............................................................................................................................................................1189
6.133 PHASEOFFSET...................................................................................................................................................1190
6.134 RMIOP..................................................................................................................................................................1190
6.135 RPL.......................................................................................................................................................................1191
6.136 RS_TMP...............................................................................................................................................................1192
6.137 RSBBE..................................................................................................................................................................1193
6.138 RSCSES................................................................................................................................................................1194
6.139 RSES.....................................................................................................................................................................1194
6.140 RSOFS..................................................................................................................................................................1195
6.141 RSOOF.................................................................................................................................................................1196
6.142 RSSES..................................................................................................................................................................1197
6.143 RSUAS.................................................................................................................................................................1198
6.144 SUMIOP...............................................................................................................................................................1199
6.145 SUMOOP..............................................................................................................................................................1200
6.146 TDC......................................................................................................................................................................1201
6.147 TLB.......................................................................................................................................................................1202
6.148 TPL.......................................................................................................................................................................1203
6.149 VC3BBE...............................................................................................................................................................1204
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xlii

OptiX OSN 8800/6800/3800
6.150 VC3CSES.............................................................................................................................................................1205
6.151 VC3ES..................................................................................................................................................................1207
6.152 VC3FEBBE..........................................................................................................................................................1209
6.153 VC3FECSES........................................................................................................................................................1210
6.154 VC3FEES.............................................................................................................................................................1211
6.155 VC3FESES...........................................................................................................................................................1212
6.156 VC3FEUAS..........................................................................................................................................................1214
6.157 VC3SES................................................................................................................................................................1215
6.158 VC3UAS...............................................................................................................................................................1216
6.159 WCV.....................................................................................................................................................................1217
7 Event List...................................................................................................................................1219
8 Event Processing......................................................................................................................1222
8.1 OWSP abnormal event.............................................................................................................................................1223
8.2 ODUk SPRing abnormal event.................................................................................................................................1225
8.3 RMON performance value is above the upper limit.................................................................................................1228
8.4 RMON module performance value is lower than the lower threshold.....................................................................1230
8.5 1+1 Equipment Level Protection Switching Event Report......................................................................................1232
A Glossary....................................................................................................................................1234
Issue 06 (2015-07-20) Huawei Proprietary and Confidential xliii

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 1 Overview
1 Overview
About This Chapter
This topic describes the meaning, impact, and indicator status of the alarms of four severities,
alarm categories, and examples for the alarm categories. In addition, it describes different types
of performance events, the alarm signal flow of OTU boards, the suppression relationship
between alarms, and performance events suppressed by alarms.
1.1 Alarm Severity
This topic describes the meaning, impact, and indicator status of the alarms of four severities.
1.2 Alarm Category
This topic describes the alarm categories and examples for the alarm categories.
1.3 Alarm Management
This section describes the alarm reporting process.
1.4 Performance Event Category
Performance events can be classified into seven 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.5 Alarm Signal Flow(OTN)
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.6 Alarm Signal Flow (OCS)
This topic describes the generation principles and detection mechanism of certain signal flows
in the SDH services.
1.7 Suppression Relation of Alarms (OTN)
This topic describes the rules of alarm suppression and provides a figure to show the suppression
relationship between common alarms. A better understanding of the alarm suppression
relationship helps improve the efficiency for handling alarms.
1.8 Suppression Relation of Alarms (OCS)
The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This section describes the suppression relationships among SDH alarms.
Issue 06 (2015-07-20) Huawei Proprietary and Confidential 1

OptiX OSN 8800/6800/3800
1.9 Performance Event Suppression by Alarms

An optical port can report several alarms and performance events. Some performance events are
not important for maintenance engineers.

OptiX OSN 8800/6800/3800
1.1 Alarm Severity

This topic describes the meaning, impact, and indicator status of the alarms of four severities.
The alarm severity is used to identify the importance and urgency of alarms. Alarms can be
classified into critical, major, minor, and warning alarms in descending order of severities.
l Critical alarm: The alarm needs to be handled immediately; otherwise, the system may
break down.
l Major alarm: The alarm needs to be handled in time; otherwise, some important functions
will be affected.
l Minor alarm: The alarm is used to prompt the maintenance personnel to isolate the alarm
causes in time and remove hidden trouble.
l Warning alarm: The alarm does not need to be handled. It prompts the maintenance
personnel with the running status of the equipment.
Table 1-1 describes the meaning and indicator status of the alarms of the four severities.
Table 1-1 Alarm level
Alarm Definition Indicator Status

Severity
Critical alarm A global fault alarm that would cause the The SRV is on (red).
system down.
Major alarm A fault alarm reported on partial boards or The SRV is on (red).
lines.
Minor alarm General fault alarms and event alarms that are The SRV is on (yellow).
used to describe whether the board or line
works properly. A common alarm that
describes whether a board or line works
properly, for example, an alarm indicating
that a board underwent a reset, applying for
common resources failed, or allocating
common resources timed out.
Warning A fault alarm for warning. The alarm indicator is off.

alarm
1.2 Alarm Category

This topic describes the alarm categories and examples for the alarm categories.
Alarms can be classified into six categories. For details, see Table 1-2.

OptiX OSN 8800/6800/3800
Table 1-2 Alarm category

Alarm Definition Example
Category
Communication Alarms related to the NE The alarm is generated when the

alarm communication, ECC NE communication is interrupted
communication, and optical signal or optical signals are lost.
communication
Process alarm Alarms related to the software The alarm is generated when the
processing and anomalies database is in error or the NE is in
the installing state.
Equipment alarm Alarms related to the hardware of The alarm is generated when the
the equipment laser is faulty or an optical port is
looped back.
Service alarm Alarms related to the service status The alarm is generated when the
and network service quality signals at the line layer are
degraded.
Environment Alarms related to the power supply The alarm is generated when the
alarm system and environment of the temperature of the power module is
equipment room excessively high.
Security alarm Alarms related to the network The alarm is generated when the
management and the NE security NE user is not logged in.
1.3 Alarm Management

This section describes the alarm reporting process.
Alarms are reported in the following cases:
l A board detects alarms and reports them to the NE software.
l The NE software reports alarms to the NMS server.
l A user queries alarms on the NMS server using an NMS client.
In the entire process, alarms are saved on the NMS after the following processing steps:
l Alarm suppression
l Automatic alarm reporting
l Alarm masking
In addition, alarm filtering and alarm reversion affect alarm reporting.
Alarm Suppression
Lower-level alarms usually derive from a root alarm that is directly triggered by an exception
or fault. These lower-level alarms make fault locating and handling difficult. Alarm correlation
can be configured to suppress non-root alarms. Then, fewer alarms are reported to the NMS,
and faults can be identified and rectified quickly.

OptiX OSN 8800/6800/3800
Automatic Alarm Reporting

After automatic alarm reporting is enabled on an NE, an alarm on the NE is reported to the NMS
immediately after this alarm is generated. Then, an alarm panel is displayed on the NMS. A user
can view the alarm information in the alarm panel. A user can disable this function for certain
alarms. This reduces the impact of a large number of alarms on the NMS performance.
Alarm Masking
The alarm masking function can be enabled for all alarms on an NE or a board on an NE. When
an alarm is masked, the corresponding NE or board does not monitor this alarm.
Alarm Filtering
Alarm filtering is implemented on the NMS, and does not affect alarms on NEs. The NMS
accepts or discards reported alarms based on the alarm filtering configuration. If alarm filtering
is enabled for an alarm on an NE, the NMS discards the alarm and does not save it into the alarm
database. If alarm filtering is disabled for an alarm on an NE, the NMS accepts the alarm and
saves it into the alarm database.
Alarm Reversion
For ports that are not configured with services, the alarm reversion function can be used to
prevent alarms from being generated. This prevents interference from alarms.
When the alarm reversion function is enabled on a port, the alarm status of this port is opposite
to the actual status. That is, no alarm is reported when an alarm is generated and an alarm is
reported when no alarm is generated.
There are three alarm reversion modes: non-reversion, automatic reversion, and manual
reversion.
l Non-reversion
This mode indicates the normal alarm monitoring state and is the default mode. In this
mode, the alarm reversion function cannot be enabled on a port.
l Automatic reversion
In this mode, the alarm reversion function can be enabled only on a port that reports alarms.
After the alarm reversion function is enabled, the port does not report any alarms. When
the current alarms are cleared, the port automatically exits the reversion mode and the alarm
status reported by the port is restored to the actual alarm status.
l Manual reversion
In this mode, the alarm reversion function can be enabled on a port regardless of whether
any alarms are reported at this port.
When the alarm reversion function is enabled on a port, the alarm status reported by the
port is opposite to the actual alarm status.
When the alarm reversion function is disabled on a port, the alarm status reported by
the port is the same as the actual alarm status.
Take the following precautions when configuring the alarm reversion function:

OptiX OSN 8800/6800/3800
l After alarm reversion is enabled on a port on a board, the alarm status of the board, including
the status of the alarm indicators on the board, remains unchanged and indicates the running
status of the board.
l The alarm reversion function is implemented by the NE software. The alarm data on the
NE is the same as the alarm data on the NMS. The alarm data indicates the alarm status
after alarm reversion is implemented.
1.4 Performance Event Category

Performance events can be classified into seven 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.
A performance event is an important parameter that reflects the working performance of the
equipment. An understanding of the generation principle and the related boards and alarms of
performance events is helpful to find incipient faults in routine maintenance and analyze the
fault. Table 1-3 describes the categories of performance events..
Performance events and alarms are related. When the value of a performance event exceeds the
preset threshold, the related alarm is triggered. Therefore, 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
(RMON) function by which the network can monitor the transmission of data in different
network segments. The RMON provides flexible detection modes and control mechanisms to
cater for the needs of different types of networks. The RMON defines a series of statistic formats
and functions to realize 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 on the entire network.
Table 1-3 Performance Event Category
Performance event category Definition
Performance event related to the Performance event generated when the board performs
check and error correction service check or bit error correction
Performance event related to the Performance event generated when the optical power, the
equipment function working current of the laser or other factors about the
running environment exceed the threshold
Performance event related to the Performance event generated when bit errors occur on the
bit errors on the multiplex multiplexing section in the SDH frames of the signals on
section the WDM side or the client side of a board
Performance event related to the Performance event generated when bit errors occur on the
bit errors on the regenerator regenerator section in the SDH frames of the signals on the
section WDM side or the client side of a board

OptiX OSN 8800/6800/3800
Performance event category Definition
Performance Event of Higher The performance event generated when bit errors occur on
Order Path Bit Error higher order path.
Performance Event of Lower The performance event generated when bit errors occur on
Order Path Bit Error lower order path.
Performance Event of Pointer The performance event generated when the board
Justification performs pointer justification.
OTN performance event Performance event generated when bit errors occur in the
PM, TCM or SM segment of the OTN service
RMON performance event Performance event related to the mode in which the board
transmits or receives data packets, the number and quality
of packets in different lengths transmitted or received
FC performance event Performance event related to FC channels
1.5 Alarm Signal Flow(OTN)

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.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:
l Non-convergent OTU
It refers to an OTU that converts one channel of client service signals.
l Convergent OTU
It refers to an OTU that converges and converts multiple channels of client service signals.
l 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.

OptiX OSN 8800/6800/3800
l Non-convergent OTU processing standard OTN signals

This section describes the alarm signal flow when the non-convergent OTU processes
standard OTN signals.
l Convergent OTU processing standard SDH signals
This section describes the alarm signal flow when the convergent OTU processes standard
SDH signals.
l Convergent OTU processing standard OTN signals
This section describes the alarm signal flow when the convergent OTU processes standard
OTN signals.
l Regenerating OTU
This section describes the alarm signal flow of the regenerating OTU.
l OTU with the cross-connect function
This section describes the alarm signal flow of the OTU with the cross-connect function.
l 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.

l Client side: it is the client side of the OTU. On the client side, the services from a client
device are accessed.
l 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.
l 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.
l 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.5.2 Non-Convergent OTU Processing Standard SDH Signals

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

OptiX OSN 8800/6800/3800
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.
Figure 1-1 Alarm signal flow 1: when the non-convergent OTU processes standard SDH signals
Station A Station B Client device
Client-side WDM-side WDM-side Client-side Client-device
R_LOS
R_LOS REM_SF R_LOF
R_LOF
R_LOF REM_SF R_LOF
MS_AIS
MS_AIS REM_SF MS_AIS
BI errors
B1_EXC REM_SD B1errors
BI errors
B1_SD B1errors
SD
PM BIP8 errors ODUk_PM_DEG/
Errors
ODUk_PM_EXC
PM remote BER
performance events
SD
SM BIP8 Errors OTUk_DEG/
Errors
OTUk_EXC
OTUk remote BER

performance events
SF
OTUk_AIS
OTUk_AIS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF
OTUk_LOM
OTUk_LOM R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF: SF event detecting SD: SD event detecting Alarm processing

xxx Detects and reports the xxx alarm or performance event

OptiX OSN 8800/6800/3800
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 detects the R_LOS alarm. 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 PM BIP8 errors
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.

OptiX OSN 8800/6800/3800
Figure 1-2 Alarm signal flow 2: when the non-convergent OTU processes standard SDH signals
SF
MFAS frame discontinuous
OTUk_LOM
ODUk_PM_BDI
&OTUk_BDI The SF event is generated when the
SF TIM follow-up response is Enabled.
PM TTI byte mismatch
ODUk_PM_TIM R_LOF
ODUk_PM_BDI
The SF event is generated when the
SM TTI byte mismatch
OTUk_TIM R_LOF
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
Excessive bit errors before FEC

BEFFEC_EXC
SF
OTUk_LOF
OTUk_LOF R_LOF
ODUk_PM_BDI
&OTUk_BDI
ODUk_PM_AIS/
SF
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/
ODUk_PM_OCI/ R_LOF
ODUk_PM_LCK
ODUk_PM_BDI
SF
R_LOS
R_LOS R_LOF
ODUk_PM_BDI
&OTUk_BDI
SF: SF event detecting Alarm processing
xxx Detects and reports the xxx alarm
For TIM alarm: The SF event is generated when the TIM follow-up response is Enabled.
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,

OptiX OSN 8800/6800/3800
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.5.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.
Figure 1-3 Alarm signal flow 1: when the non-convergent OTU processes standard OTN signals
R_LOS SF
R_LOS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SD
PM BIP8 errors ODUk_PM_DEG/
ODUk_PM_DEG/ PM BIP8 errors
ODUk_PM_EXC ODUk_PM_EXC
SM BIP8 errors OTUk_DEG/

OTUk_EXC
OTUk remote BER SD
performance events SM BIP8 errors
OTUk_DEG/
OTUk_EXC
OTUk remote BER
performance events
SD
PM BIP8 errors
ODUk_PM_DEG/
PM BIP8 errors
ODUk_PM_EXC
SF
OTUk_LOF
OTUk_LOF ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_LOM
OTUk_LOM ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI
SF
OTUk_AIS
OTUk_AIS ODUk_PM_AIS ODUk_PM_AIS
OTUk_BDI OTUk_LOF/
OTUk_LOM/ SF
OTUk_AIS OTUk_LOF/
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS
OTUk_BDI


OptiX OSN 8800/6800/3800
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.
l 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
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.

OptiX OSN 8800/6800/3800
Figure 1-4 Alarm signal flow 2: when the non-convergent OTU processes standard OTN signals
The SF event is generated when the

OTUk_TIM The SF event is generated when the
OTUk_TIM
OTUk_BDI
OTUk_BDI
OTUk_BDI OTUk_BDI
OTUk_BDI OTUk_BDI
Transparent transmission of all PM signals
ODUk_PM_AIS/
SF
ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_AIS/ ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_LCK/ ODUk_PM_LCK/ ODUk_PM_LCK/
ODUk_PM_OCI ODUk_PM_OCI ODUk_PM_OCI
R_LOS SF
R_LOS ODUk_PM_AIS
OTUk_BDI

xxx Detects and reports the xxx alarm
l 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
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.
l ODUk_PM_TIM/ODUk_PM_BDI
The OTU transparently transmits all PM alarms.
l 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.

OptiX OSN 8800/6800/3800
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.
l 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.5.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

OptiX OSN 8800/6800/3800
Figure 1-5 Alarm signal flow 1: when the convergent OTU processes standard SDH signals
Client-side Middle WDM-side WDM-side Middle Client-side Client-device
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 SF 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_LOF
N#1 R_LOF N#1 REM_SF N#1 R_LOF
R_LOC
N#1 R_LOC N#1 REM_SF N#1 R_LOF
SD
Errors
N#1 Errors 1#N BIT Errors Errors
A
N#1 A 1#N A A
B
N#1 B 1#N B B
C
N#1 C 1#N C C
D N#1 D 1#N D D
A, B, C, D are the others of the SDH alarms
SF:SF event detecting SD:SD event detecting Alarm processing
xxx 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.
l 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.
l 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.

OptiX OSN 8800/6800/3800
When any other alarms are accessed, the same alarm is reported at each detection point in
the system.
Figure 1-6 Alarm signal flow 2: when the convergent OTU processes standard SDH signals
R_LOF
SF R_LOF
R_LOS
R_LOS
R_LOF
ODUk_PM_BDI&
OTUk_BDI R_LOF
R_LOF
SF
OTUk_LOF/ R_LOF
OTUk_AIS OTUk_LOF/
OTUk_AIS
R_LOF
ODUk_PM_BDI&
R_LOF
OTUk_BDI
R_LOF
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ R_LOF
ODUk_PM_OCI ODUk_PM_LCK/
ODUk_PM_OCI R_LOF
ODUk_PM_BDI R_LOF
Errors
SD
PM BIP8 errors ODUk_PM_DEG/ Errors
ODUk_PM_EXC
Errors
OTUk remote BER

Errors
performance events
Errors
SD
Errors
OTUk_EXC
Errors
PM remote BER
performance events Errors


OptiX OSN 8800/6800/3800
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 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.5.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 WDM-
side 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 re-
allocated.
NOTE

OptiX OSN 8800/6800/3800
Figure 1-7 Alarm signal flow 1: when the convergent OTU processes standard OTN signals
R_LOS SF
N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS
R_LOS SF
N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
Inserts OTUk_BDI back N#1 R_LOS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
R_LOS SF
Inserts OTUk_BDI back N#1 R_LOS
OTUk_LOM SF
Inserts OTUk_BDI back N#1 OTUk_LOM N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
OTUk_LOF SF
Inserts OTUk_BDI back N#1 OTUk_LOF N#1 ODUk_PM_AIS N#1 ODUk_PM_AIS
OTUk_TIM
SF
Inserts OTUk_BDI back N#1 OTUk_TIM
ODUk_PM_AIS
N#1 ODUk_PM_AIS SF
A 1#N A
N#1 A 1#N A
B 1#N B 1#N B
N#1 B
C 1#N C 1#N C
N#1 C
SD
BIT errors
N#1 BIT errors 1#N BIT errors 1#N BIT errors
xxx Detects and reports the xxx alarm 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.
l 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

OptiX OSN 8800/6800/3800
B, the alarm signals are then sent to the downstream station. The ODUk_PM_AIS alarm
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.

OptiX OSN 8800/6800/3800
Figure 1-8 Alarm signal flow 2: when the convergent OTU processes standard OTN signals
ODUk_PM_AIS
R_LOS SF ODUk_PM_AIS
R_LOS
ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
OTUk_LOF/ SF
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS OTUk_LOF/
OTUk_LOM/
OTUk_AIS ODUk_PM_AIS
ODUk_PM_BDI
ODUk_PM_AIS
&OTUk_BDI
ODUk_PM_AIS
ODUk_PM_AIS/ SF
ODUk_PM_LCK/ ODUk_PM_AIS/ ODUk_PM_AIS
ODUk_PM_OCI
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
Errors
SD
SM BIP8 errors Errors
OTUk_DEG/
OTUk_EXC
Errors
OTUk remote BER


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.

OptiX OSN 8800/6800/3800
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.
l 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 error-
dependent 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.5.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.

OptiX OSN 8800/6800/3800
Figure 1-9 Alarm signal flow of the regenerating OTU
Station A Station B(REG) Station C
WDM-side WDM-side1 WDM-side2 WDM-side
MFASframe discontinuous
OTUk_LOM ODUk_PM_AIS
OTUk_BDI
PM TTI byte mismatch PM TTI byte mismatch

ODUk_PM_TIM ODUk_PM_TIM
SM TTI byte mismatch TIM follow-up response is Enabled.

OTUk_TIM ODUk_PM_AIS
OTUk_BDI
ODUk_PM_BDI
ODUk_PM_BDI ODUk_PM_BDI
OTUk_BDI
OTUk_BDI
OTUk_LOF
OTUk_LOF ODUk_PM_AIS
OTUk_BDI
ODUk_PM_AIS/
ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_AIS/ ODUk_PM_AIS/
ODUk_PM_OCI/ ODUk_PM_OCI/
ODUk_PM_LCK ODUk_PM_LCK
PM BIP8 errors ODUk_PM_DEG/ ODUk_PM_DEG/

ODUk_PM_EXC ODUk_PM_EXC

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
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

OptiX OSN 8800/6800/3800
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).
1.5.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 straight-
through 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 B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
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 straight-
through 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 cross-
connection.
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.
l Inter-unit cross-connection

OptiX OSN 8800/6800/3800
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.
Figure 1-11 OTU with the cross-connect function in the cross-connect mode
A B
3#1(RX1) 3#1(TX1)
1#3 1#3
4#1(RX2) 4#1(TX2)
1#4 1(OUT) 1(IN) 1#4
5#1(RX3) 5#1(TX3)
1#5 1#5
6#1(RX4) 6#1(TX4)
1#6 1#6
3#1(RX1)
1#3
4#1(RX2)
1#4
5#1(RX3)
1#5
6#1(RX4)
1#6
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
l 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 cross-
connect 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.
NOTICE
In any mode, proper configuration must be made on the U2000.

OptiX OSN 8800/6800/3800
1.5.8 OTU Processing GE Signals

This section describes the alarm signal flow when the OTU board processes Ethernet service
signals.
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

OptiX OSN 8800/6800/3800
Figure 1-12 Alarm signal flow 1: when the OTU processes GE signals

WDM- WDM-
Client-side Middle Middle Client-side Client-device
side side
Scenario 1: The client sides are in the non-negotiation mode.

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

R_LOS REM_SF
R_LOS LINK_ERR
LINK_ERR
LPT=Enable LINK_ERR LINK_ERR

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

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

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 R_LOS

OptiX OSN 8800/6800/3800
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
Scenario 1: The client sides are in the non-negotiation mode.

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

R_LOS REM_SF
R_LOS LINK_ERR
LINK_ERR
LPT=Enable LINK_ERR LINK_ERR

LINK_ERR
LINK_ERR None None
LPT=Disable
SF
R_LOS
R_LOS None LINK_ERR
SM_BDI
SF: SF event detecting Alarm processing

Detects and reports the xxx
xxx
alarm
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.

OptiX OSN 8800/6800/3800
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 SM_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.5.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 OD
OTU
Client-side equipment
Line-side ODF
Line-side ODF
OTU OTU
SC1 FIU FIU SC1
OTU OTU
OTU
OD OA OA 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.
l 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 At station A, the optical amplifier in direction A-to-B loses input light.
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.

OptiX OSN 8800/6800/3800
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.
l 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
l 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.
l 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
OM OA OA OD
East line-side ODF

OA OTU
Line-side ODF
Line-side ODF
West line-side
OTU OTU
ODF
FI
SC1 FIU SC1
U FIU SC2 FIU
OTU OTU
OTU
OD OA OA OM
OA 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.
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.

OptiX OSN 8800/6800/3800
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.
l 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 C reports the OCh_LOS_P alarm.
Figure 1-16 Scenario III

West client- East client-
side side
OTU OOO O O OO O
T T T T T T T T OTU
U U U U U U U U
OTU
OM OA OD OM OA OD
OTU
West line-side ODF
East line-side ODF
Line-side ODF
OTU
Line-side ODF
OTU OA WSD9 RMU9 OA

FI FI
FIU FIU SC1
SC1
U U SC2
OTU RMU9 WSD9 OA OTU

OA
OTU
OD OA OA OM
OM OD
OTU
OTU O O O OO O OO
T T T T T T T T OTU
U U U UU U UU
West client- East client-

side side
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.
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).

OptiX OSN 8800/6800/3800
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 wavelengths between stations A and C).
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
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
l 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
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
l 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
l 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.
l 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
l 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.
l 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
l 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.
l The OTU board at station B is faulty.

OptiX OSN 8800/6800/3800
The OTU board at station C reports the OCh_LOS_P alarm (for wavelengths from station
B to station C).
1.6 Alarm Signal Flow (OCS)

This topic describes the generation principles and detection mechanism of certain signal flows
in the SDH services.
1.6.1 Overview
There are sufficient overhead bytes in SDH frames, including regenerator section overheads,
multiplex section overheads, and path overheads. These overhead bytes carry alarm and
performance information. According to the information, the SDH system can monitor alarms
and bit errors in real time. With an understanding of the alarm generation and detection
principles, you can quickly identify faults.
Figure 1-17 shows the SDH alarm signal flow.
Figure 1-17 SDH alarm signal flow
SPI RST MST MSA HPT HPA LPT

LOS
"1"
(A1,A2) LOF
J0_MM AIS
(J0)
RS_BIP Err.
(B1)
MS_AIS "1"
(K2) AIS
MS_BIP Err.
(B2)
MS_REI
(M1)
MS_RDI
(K2)
AU_AIS "1"
(H1,H2,H3)
AU_LOP
(H1,H2)
HP_SLM, HP_UNEQ "1"
(C2)
HP_TIM
(J1) AIS
HP_BIP Err.
(B3)
HP_REI
(G1)
HP_RDI
(G1)
TU_AIS "1"
(V1,V2,V3)
TU_LOP
(V1,V2)
HP_LOM
(H4)
LP_UNEQ "1"
(V5)
LP_TIM
(J2)
LP_BIP Err. AIS
(V5)
LP_REI
(V5)
LP_RDI
(V5)
"1"
LP_SLM AIS
(V5)
Indicates that the corresponding alarm or signal is generated

Indicates that the corresponding alarm is detected

OptiX OSN 8800/6800/3800
1.6.1.1 Directions and Levels of Signal Flows

This topic describes basic concepts, including the uplink signal flow, downlink signal flow,
higher order path, and lower order path, involved in signal analysis.
Term Description Figure
Downlink The signal flow is as follows:

SDH SDH
signal SDH port cross-connect unit port port
flow lower order SDH port or Cross-connect
unit
Ethernet port.
PDH port
Downlink
signal flow
Uplink The signal flow is as follows:

SDH SDH
signal lower order SDH port or Ethernet port port
flow port cross-connect unit Cross-connect
unit Uplink
higher order SDH port. signal flow
PDH port
Higher The signal between the SDH port Higer order part
order and the cross-connect unit is the
signal higher order signal flow.
flow SDH SDH
port Cross-connect port
unit
PDH port
Lower The signal between the cross-

order connect unit and the SDH port or SDH SDH
signal Ethernet port is the lower order port Cross-connect port
unit
flow signal flow.
PDH port
Lower order part
1.6.1.2 Two Common Alarms

This section describes two common alarms: alarm indication signal (AIS) and remote defect
indication (RDI).

OptiX OSN 8800/6800/3800
Alarm Description
AIS When an AIS alarm is reported, the system inserts all 1s into the
lower-level circuits to indicate that the signal is unavailable. The
MS_AIS, and AU_AIS alarms are common AIS alarms.
RDI When detecting the loss of signal (LOS), AIS, or trace identifier
mismatch (TIM) alarm, the opposite NE sends the RDI alarm to
the local NE.
The MS_RDI, and HP_RDI alarms are common RDI alarms.
NOTE
The generation of an alarm on an NE does not necessarily indicate that the NE is faulty. The alarm may
be generated due to a fault on the opposite NE or due to other causes.
For example, the R_LOS alarm is generated due to a fiber cut, or the HP_LOM alarm is generated on the
local NE due to the failure in the cross-connect unit on the opposite NE.
1.6.2 Generation and Detection of Alarms and Performance Events

in the SDH Higher Order Signal Flow
The principle for locating faults is "line first, then tributary; high level first, then low
level". Therefore, this section focuses only on the alarms and performance events generated
between the SDH interface and the cross-connect unit during maintenance.
Generally, the alarms and performance events that are generated in the higher order paths cause
lower order alarms and performance events. Figure 1-18 shows the signal flow between the
SDH interface and the cross-connect unit.
Figure 1-18 Alarm signals generated between the SDH interface and the cross-connect unit
Frame synchronizer MS overhead Pointer processor and HP
and RS overhead processor overhead processor
processor
(RST) (MST) (MSA, HPT)
LOS "1" AIS "1" AIS

STM-N AU-AIS
optical MS-AIS H1,H2
A1, LOF AU-LOP
interface K2 H1,H2
A2 HP-TIM
B2-Err. J1 "1"
B2 HP-UNEQ
C2 Cross-connect
BI Err. MS-REI HP-SLM unit
B1 M1 C2
H4 HP-LOM
MS-RDI
k2 B3 Err.
B3
HP-REI
G1
HP-RDI
G1
Downlink signal flow Alarm report or return
Signal transfer point Alarm termination point

(Insert all "1"s signal) (Report to SCC unit)
Based on the positions of the various overhead bytes in the STM-1 frame, the overhead bytes
are classified into the following four modules:

OptiX OSN 8800/6800/3800
l Regenerator section overheads

l Multiplex section overheads
l Higher order path overheads
In normal cases, a fault in the first two modules affects all the higher order paths. A fault in the
higher order overhead bytes, however, affects higher order paths.
The following sections describe the signal flow and the processing of overhead bytes.
1.6.2.1 Downstream Signal Flow

In the higher order downstream signal flow, overhead bytes are extracted and terminated.
Frame Synchronizer and Regenerator Section Overhead Processor

In the regenerator section (RS), the overhead bytes that are related to alarms and performance
events are as follows:
l Framing bytes (A1, A2)

l Regenerator section trace byte (J0)
l RS bit interleaved parity (BIP-8) code byte (B1)
The alarm signal flow is as follows:
l In the receive direction

When the STM-N optical signal from a line enters the optical receiving module of a line
board, the signal is first converted into an electrical signal through the optical/electrical
conversion (O/E conversion) module. It is then sent to a frame synchronizer and an
unscrambler for processing. During this process, the O/E conversion module continuously
checks the signal. An R_LOS alarm is reported if the following faults are detected:
No signal is input.
The optical power is low or high.
The code type of the input signal does not match the original one.
The R_LOS alarm persists on the SDH equipment, until the optical receiving module of
the local station detects the correct code pattern and at the same time no new R_LOS alarm
is detected.
When an R_LOS alarm occurs, the system inserts an all "1"s signal into the lower level
circuits.
l Detecting the A1, A2 and J0 bytes
After receiving an STM-N signal from the O/E conversion module, the frame synchronizer
captures the frame alignment signal through the A1 and the A2 bytes in the signal.
Meanwhile, the frame synchronizer extracts the line reference synchronization clock source
from the signal and sends it to the clock board for locking the clock.
Normally, the A1 value is always "F6H", and the A2 value is always "28H". If incorrect
A1 or A2 values are detected in five consecutive frames, an R_OOF alarm occurs. If the
R_OOF alarm lasts for more than 3 ms, an R_LOF alarm occurs, and an all "1"s signal is
inserted. If the framing state lasts for more than 1 ms after the R_LOF alarm occurs, the
equipment returns to normal.

OptiX OSN 8800/6800/3800
The J0 byte is used to verify if the two ends of the regenerator section are permanently
connected to each other. For an NE, the J0 byte received and the J0 byte to be received
must match. Otherwise, the equipment reports a trace identifier mismatch alarm (J0_MM).
An unscrambler is used to unscramble all the bytes except A1, A2, J0, and the two bytes
that follow the J0 bytes in the STM-N signals.
l Detecting the B1 byte
The regenerator section overhead (RSOH) processor extracts and processes other RSOH
bytes in the STM-N signal. Among all the bytes, the B1 byte is the most important.
If the B1 byte recovered from an STM-N signal is not consistent with the BIP-8 computing
result of the preceding STM-N frame, B1 bit errors are reported.
If the number of B1 bit errors exceeds the threshold 10-6 (which is the default value), a
B1_SD alarm occurs.
If the number of B1 bit errors exceeds the threshold 10-3 (which is the default value), a
B1_EXC alarm occurs.
When there are ten consecutive severely errored seconds (SES, indicating a second in which
errored blocks reach a percentage of 30%) in the regenerator section, the regenerator section
unavailable time event (RSUAT) occurs.
The F1, D1-D3, and E1 bytes, which are irrelevant to alarms and performance events, are sent
to the SCC module and the overhead module.
Multiplex Section Overhead Processor

In the multiplex section (MS), the overhead bytes that are related to the alarms and the
performance events are as follows:
l Automatic protection switching bytes (K1, K2)
l MS bit interleaved parity code byte (B2)
l MS remote error indication (M1)
The signal flow is as follows:
l Detecting the K1 and the K2 bytes

The K2 byte (bits 6-8) is used to indicate a failure at the remote end of the MS.
If the code of the bits 6-8 of the K2 byte is "111", an MS_AIS alarm is generated and
an all "1"s signal is inserted.
If the code of the bits 6-8 of the K2 byte is "110", an MS_RDI alarm is generated.
The bytes K1 and K2 (bits 1-5) are used to transmit the automatic protection switching
(APS) protocol. The bytes K1 and K2 (bits 1-5) can work with the system control and
communication board and the cross-connect board to realize MSP.
l Detecting the B2 byte and the M1 byte
If the B2 byte recovered from the STM-N signal is not consistent with the BIP-24 computing
result of the preceding STM-N frame (all bits expect for the RSOH), B2 bit errors occur.
The M1 byte is used to check if an MS_REI alarm is reported. The M1 byte carries the
error count of the interleaved bit blocks that the B2 byte has detected.
If B2 bit errors exceed the threshold 10-6 (default), a B2_SD alarm is generated.
If B2 bit errors exceed the threshold 10-3 (default), a B2_EXC alarm is generated.

OptiX OSN 8800/6800/3800
In the multiplex section protection mode, the B2_EXC and the B2_SD (if enabled) alarms
can trigger the MSP switching.
If the B2 byte detects MSSES for 10 consecutive seconds, the multiplex section unavailable
time (MSUAT) event occurs.
Pointer Processor and Higher Order Path Overhead Processor

The bytes that are related to pointer justifications are H1, H2 and H3. The bytes that are related
to alarms and bit errors are as follows:
l Higher order path trace byte (J1)

l Signal label byte (C2)
l Higher order path bit interleaved parity code (path BIP-8) byte (B3)
l Path status byte (G1)
l Multiframe indicator byte (H4)
The alarm signal flow is as follows:
l Detecting the H1 and H2 bytes

The pointer processor interprets and justifies the pointer on the basis of the H1 and H2 bytes
in each AU-4. It achieves frequency and phase alignment. The pointer processor also locates
each VC-4 and transmits them to the corresponding higher order path overhead processor.
NOTE
H3 bytes tolerate phase jitter and wander in the network.

If the H1 and the H2 bytes of the AU pointer are detected to be all "1"s, an AU_AIS alarm
is reported and an all "1"s signal is inserted. If the pointer values of H1 and H2 are illegal
(beyond the normal range, which is from 0 to 782) and illegal pointers are received in eight
consecutive frames, an AU_LOP alarm is reported and an all "1"s signal is inserted.
If the AU pointer justification is positive, the number of PJCHIGHs of the multiplex section
adaptation (MSA) increases by one. If the AU pointer justification is negative, the number
of PJCLOWs of the MSA increases by one.
l Detecting the J1, C2, B3, G1 and H4 bytes
The higher order path overhead processor processes higher order path overhead (HPOH)
bytes in the received NxVC-4s. The mode for processing each byte is described as follows:
If the J1 byte value detected is not the same as the preset value, an HP_TIM alarm is reported
and an all "1"s signal is inserted.
If the C2 byte is detected as 00, an HP_UNEQ alarm is reported and an all "1"s signal is
inserted.
NOTE
In the case of the Huawei OSN series equipment, you can use the NMS to set whether the all "1"s
signal is inserted when the HP_TIM, HP_UNEQ alarm occurs. By default, the all "1"s signal is not
inserted.
Currently, the tributary unit group (TUG) is adopted as the payload structure in China. The
preset C2 value that corresponds to the TUG structure is "02".
If the B3 byte restored from the HPOH is not consistent with the BIP-8 computing result
of the VC-4 signal of the preceding frame, B3 bit errors are reported.

OptiX OSN 8800/6800/3800
In the STM-N lower order SDH interface board, the TU-12 signal extracted from VC-4s
requires the H4 byte to indicate the frame number of the current multiframe in which the
current TU-12 is placed. If the H4 byte detected is illegal, an HP_LOM alarm is reported.
If bit 5 of the G1 byte is "1", an HP_RDI alarm is reported. The value of bits 1-4 of the G1
byte determines if an HP_REI alarm is reported. If the value of bits 1-4 of the G1 byte is
1-8, an HP_REI alarm is reported.
When B3 detects SES for 10 consecutive seconds, an HPUAT EVENT performance event
occurs.
Other overhead bytes such as the F3, K3 and N1 are reserved for future use.
Finally, the NxSTM-1 payloads are transmitted to the cross-connect unit for the cross connection
of the higher order path and the lower order path.
1.6.2.2 Upstream Signal Flow

The overhead bytes are extracted and then terminated in the downstream signal flow of the higher
order path. Generating overhead bytes and returning alarm signals to the opposite NE are
completed in the upstream signal flow of the higher order path.
Pointer Processor and Higher Order Path Overhead Processor

N x STM-1 payload signals from the cross-connect unit are first sent to higher order path
overhead processor.
The higher order path overhead processor generates N x higher order path overhead bytes, which
are sent to the pointer processor with the N x STM-1 payloads. The setting of higher order path
overhead bytes such as the J1, C2, B3, G1, F2, F3 and N1 can be completed along the upstream
direction.
If an AU_AIS, an AU_LOP, a HP_UNEQ or a HP_LOM (Optional HP_TIM) alarm is detected

in the downstream signal flow, bit b5 of the G1 byte is set to "1", and an HP_RDI alarm is
reported to the remote end. If B3 bit errors are detected in the downstream signal, bits 1-4 of the
G1 byte are set to a corresponding bit error value (ranging 1-8) based on the detected error value,
and an HP_REI alarm is reported to the remote end.
The H4 byte is not processed in the upstream direction.
The pointer processor generates N x AU-4 pointers, and adapts the VC-4 into an AU-4 (H1 and
H2 bytes). The N x AU-4s are then multiplexed into an STM-N signal by using the multiplexing
processor and are sent to the MSOH processor.
Multiplex Section Overhead Processor

The multiplex section overhead processor sets the MSOH bytes such as the K1, K2, D4-D12,
S1, M1, E2 and B2 for the received STM-N signal.
If an R_LOS, an R_LOF or an MS_AIS alarm is detected in the downstream signal flow, bits
6-8 of the K2 byte are set to "110", and an MS_RDI alarm is reported to the remote end.
If B2 bit errors are detected in the downstream signal flow, an MS_REI alarm is reported to the
remote end through the M1 byte.

OptiX OSN 8800/6800/3800
Frame Synchronizer and Regenerator Section Overhead Processor

The RSOH processor sets the overhead bytes, such as the A1, A2, J0, E1, F1, D1-D3 and B1,
in the regenerator section and sends a complete STM-N electrical signal to the frame
synchronizer and scrambler.
After being scrambled by the frame synchronizer and scrambler, the STM-N electrical signal is
converted into an STM-N optical signal by the E/O module and then sent out of the optical
interface.
1.7 Suppression Relation of Alarms (OTN)

This topic describes the rules of alarm suppression and provides a figure to show the suppression
relationship between common alarms. A better understanding of the alarm suppression
relationship helps improve the efficiency for handling alarms.
When the equipment is faulty, several alarms may be generated by the same optical port.
However, some alarms are not important for maintenance engineers. 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 maintenance engineers. In this case, the equipment
suppresses the alarm indicating that the B1 bit errors cross the threshold using the R_LOS alarm.
Only the R_LOS alarm is reported by the optical port.
The rules of alarm suppression are as follows:

l Client-side alarms and WDM-side alarms are relatively independent, and there is no
suppression relationship between the alarms.
l There is no alarm suppression relationship between service alarms and detection alarms
related to board hardware.
NOTE
Some optical module alarms have suppression relationships. For example, the R_LOS alarm
suppresses the IN_PWR_LOW alarm.
l There is no suppression relationship between the alarms that cannot be generated at the
same time.
1.7.1 Suppression of OTN Optical-Layer Alarms

Figure 1-19 shows the suppression of OTN optical-layer alarms.
The alarm above an arrow suppresses the alarm below the arrow. For example, the OTS_LOS
alarm suppresses the OTS_LOS_P and OTS_LOS_O alarms.
NOTE
The R_LOS alarm on a single wavelength and alarms at the electrical layer are not suppressed by alarms
at the server layer.

OptiX OSN 8800/6800/3800
Figure 1-19 Suppression of OTN optical-layer alarms

OTS_PMI OTS_LOS
OTS_LOS_P OTS_LOS-O
OTS_TIM
OTS_BDI
OTS_BDI_O OTS_BDI_P
OTS_TSF_P OMS_SSF OTS_TSF_O
OMS_SSF_P OMS_SSF_O
OMS_FDI
OMS_FDI_P OMS_FDI_O
OMS_PMI OMS_BDI
OMS_LOS_P OMS_BDI_O OMS_BDI_P
OMS_TSF_P OCh_SSF OMS_TSF-O
OCh_SSF_P OCh_SSF_O
OCh_FDI
OCh_FDI_P OCh_FDI_O
OCh_LOS_P OCh_OCI
OCh_TSF_P OCh_TSF_O
R_LOS in OTU OTUk_SSF

boards
XXX Alarms Suppression
XXX Signals Trigger Conditions
1.7.2 Suppression of OTN Electrical-Layer Alarms

Figure 1-20 shows the suppression of OTN electrical-layer alarms.
The alarm above an arrow suppresses the alarm below the arrow. For example, the OTUk_LOM
alarm suppresses the OTUk_TIM alarm.

OptiX OSN 8800/6800/3800
Figure 1-20 Suppression of OTN electrical-layer alarms
OCH_LOS
OTUk_LOF
OTUk_LOM Note:
The TIM alarm suppresses the
OTUk_SSF
BDI alarm and DEG alarm of
the same layer just when the
TIM follow-up response is
OTUk_TIM Enabled.
OTUk_BDI ODUk_LOFLOM OTUk_DEG
ODUk_TCMn_LTC/
ODUk_TCMn_LCK/ ODUk_TCMn_SSF
ODUk_TCMn_OCI
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

OptiX OSN 8800/6800/3800
1.7.3 Suppression Between Alarms Related to SDH Services and

Other Common Equipment Alarms
Figure 1-21 shows the suppression between SDH service alarms and other common alarms
related to equipment alarms.
The alarm above an 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-21 Suppression between 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
B2_EXC
B1_EXC
MS_AIS MS_RDI
B1_SD
B2_SD

OptiX OSN 8800/6800/3800
1.8 Suppression Relation of Alarms (OCS)

The equipment supports the alarm suppression function so that you can quickly locate the root
fault. This section describes the suppression relationships among SDH alarms.
Alarms are correlative. An alarm may trigger another alarm, especially, a higher-level alarm
may trigger a lower-level alarm.
For example, an R_LOS alarm occurs on an optical interface unit due to optical route faults. The
R_LOS alarm then inserts an AIS signal to the downstream circuit. As a result, all overhead
bytes change to all-1s, and alarms such as MS_AIS and AU_AIS are triggered. You do not need
to handle the downstream alarms that are triggered by the R_LOS alarm.
In addition, if all these alarms are reported simultaneously, the NMS and SCC board are heavily
loaded, and maintenance tasks are difficult.
To prevent the preceding situations, the equipments uses the alarm suppression function to
suppress some unnecessary alarms.
Figure 1-22 shows the suppression relationships of some major alarms.
Figure 1-22 Suppression of major alarms
R_LOS
R_LOF
MS_AIS
B1_EXC
B2_EXC AU_AIS
AU_LOP
B3_EXC HP_UNEQ HP_TIM HP_SLM
The higher-level alarms above the arrow mask the lower-level alarms below the arrow. This
mechanism allows maintenance engineers to focus only on higher-level alarms.
NOTE
There are suppression relationships between different-level alarms, but not between different-level
performance data because there is no causality between performance events. B2 bit errors will not be
triggered when B1 bit errors occur. The B2 bit error data is derived from calculating the contents in the
managed area.

OptiX OSN 8800/6800/3800
1.9 Performance Event Suppression by Alarms

An optical port can report several alarms and performance events. Some performance events are
not important for maintenance engineers.
When the equipment is faulty, several alarms and performance events may be generated by the
same optical port. However, some alarms and performance events are not important for
maintenance engineers. For example, when the signal is lost, the optical port 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 using the R_LOS alarm and reports only the
R_LOS alarm.
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.

OptiX OSN 8800/6800/3800
Table 1-6 Performance events suppressed by the NO_BD_PARA alarm
LSBIASCUR LSTMPMAX LSIOPMIN
LSBIASMAX LSTMPMIN SUMIOPCUR
LSBIASMIN LSOOPCUR SUMIOPMAX
LSCLCCUR LSOOPMAX SUMIOPMIN
LSCLCMAX LSOOPMIN SUMOOPCUR
LSCLCMIN LSIOPCUR SUMOOPMAX
LSTMPCUR LSIOPMAX SUMOOPMIN

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 2 Alarm List
2 Alarm List
About This Chapter
This topic describes all alarms supported by the product and the related information, and lists
the alarms of each board.
2.1 Product Alarm List

This topic lists the alarms supported by the product.
2.2 Board Alarm List

This topic lists the alarms of every board.

OptiX OSN 8800/6800/3800
2.1 Product Alarm List

This topic lists the alarms supported by the product.
2.1.1 Alarm List A

This section used a table to list the alarms starting with A.
Name Description Level Service

Affecting
AD_CHECK_FAIL AD (analog to digital Major No

converter) self check failure
ALC_ADJUST_FAIL ALC link adjustment Major No

failure
ALC_WAIT_ADJUST ALC link anomaly and wait Major No

for adjustment
ALS_ACTIVE ALS occurred Minor No
ALS_TRIGGERED The laser on a board is Critical Yes

disabled by ALS
ALM_ALS Automatic laser shutdown Minor No
ALM_GFP_dCSF GFP client signal fail Critical Yes
ALM_GFP_dLFD The loss of generic framing Major Yes

procedure (GFP) frame
delineation
ALM_HANGUP The orderwire phone is in Minor No

the off-hook state for a long
time
APE_ADJUST_FAIL APE adjustment failure Major Yes
APE_ADJUST_PEND APE adjustment is pending Major Yes

for operation.
APS_MANUAL_STOP The MSP protocol is Minor No

manually stopped
APS_FAIL APS protection switching Major No

failure
APS_INDI An alarm indicating the Major No

APS state
ASE_NOT_CALIBRATE ASE of raman optical Minor Yes

module not demarcated

OptiX OSN 8800/6800/3800

Affecting
AU_AIS AU alarm indication signal Major Yes
AU_LOP AU loss of pointer Major Yes
2.1.2 Alarm List B

This section used a table to list the alarms starting with B.

Affecting
B1_EXC Regenerator section (B1) Minor Yes

excessive errors
B1_SD Regenerator section (B1) Minor Yes

signal degraded
B2_EXC Multiplex section (B2) Major Yes

excessive errors
B2_SD Multiplex section (B2) Minor Yes

signal degraded
B3_EXC The number of higher order Major Yes

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

in the lower order path
VC-3 exceeds the
threshold.
B3_EXC_VC4 The number of B3 bit errors Major Yes

in the VC-4 path exceeds
the threshold.
B3_SD The higher order path B3 Minor Yes

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

errors exceeds the
threshold.
B3_SD_VC4 The number of B3 bit errors Minor Yes

in the VC-4 path exceeds
the threshold.

OptiX OSN 8800/6800/3800

Affecting
BD_LEDTEST Board LED Flash Test Warning No
BD_NOT_INSTALLED Logic board not installed Minor No

alarm
BD_STATUS Board out of position Major Yes
BDID_ERROR An alarm of slot Major No

verification error
BEFFEC_EXC Signal degraded before Minor Yes

FEC
BIOS_STATUS The BIOS status Major Yes
BOOTROM_BAD BOOTROM data check Major No

failed
BUS_ERR Bus error Critical Yes
BWUTILIZATION_OVE Bandwidth utilization over Warning Yes

the threshold
2.1.3 Alarm List C

This section used a table to list the alarms starting with C.

Affecting
C2_VCAIS A C2 byte alarm indication Minor Yes
CFCARD_FAILED CF Card Failed Major No
CHAN_ADD Channel of single wave Major No

signal add
CHAN_LOS Channel of single wave Critical No

signal loss
CHIP_ABN Temperature chip failure Minor No
CLIENT_PROT_NOT- Client-side 1+1 protection Minor No

START group not started
CLIENT_PORT_PS Client-side 1+1 protection Major No

switching
CLIENT_PORT_STA_INDI The state of the client-side Minor No

1+1 optical channel
protection group

OptiX OSN 8800/6800/3800

Affecting
CLK_NO_TRACE_MODE The clock enters into a non- Minor No

tracing running mode.
CLK_LOCK_FAIL Clock lockout failure alarm Major No
COM_EXTECC_FULL Number of TCP Major No

connections between NEs
running the automatically
extended ECC protocol
exceeding the system limit
COMMUN_FAIL Internal communication Major No

failure on the board
CPC_NODE_ID_ERR Node ID Error Critical No
CRC4_CROSSTR CRC4 multi-frame error Minor Yes

code count exceeds the
threshold
2.1.4 Alarm List D

This section used a table to list the alarms starting with D.

Affecting
DB_RESTORE_FAIL Database restore fail alarm Major No
DBMS_DELETE The NE database is deleted Critical No
DCNSIZE_OVER The number of NEs in a Major No

DCN subnet exceeds the
setting threshold
DBMS_ERROR Database error alarm Major No
DBMS_PROTECT_MODE Database in protect mode Critical No
DBPS_ABNORMAL DBPS abnormal alarm Major Yes
DCM_INSUFF Insufficient dispersion Warning Yes

compensation margin
DERIVED_PWR_ERROR Optical power exception Critical Yes

alarm
DLAG_PROTECT_FAIL DLAG protect failed alarm Major Yes

OptiX OSN 8800/6800/3800

Affecting
DSP_LOAD_FAIL DSP software loading Major Yes

failure
2.1.5 Alarm List E

This section used a table to list the alarms starting with E.

Affecting
EFI_TYPE_MISMATCH Mismatch between the EFI Critical No

board type and subrack type
ERPS_IN_PROTECTION EPRS switching is triggered Minor Yes
ETH_APS_LOST APS frame loss Minor No
ETH_APS_PATH_MIS- Mismatch of APS working/ Major No

MATCH protection paths
ETH_APS_SWITCH_FAI APS protection switching Major No

L failure
ETH_APS_TYPE_MIS- Mismatch of APS Major No

MATCH protection type
ETH_8B10B_ERR Ethernet line signal Minor Yes

encoding/decoding error
ETH_CFM_AIS ETH MEP alarm indication Major Yes

signal
ETH_CFM_LOC Service connectivity loss Critical Yes
ETH_CFM_MISMERGE Misconnection Critical Yes
ETH_CFM_MACSTA- Remote MAC defect Major Yes

TUS indication
ETH_CFM_RDI A remote CFM_OAM Minor Yes

alarm indication
ETH_CFM_UNEXPERI Errored frame Minor Yes
ETH_EFM_DF Discovery failure alarm Major Yes
ETH_EFM_EVENT Remote link event alarm Major Yes
ETH_EFM_LOOPBACK Ethernet loopback alarm Major Yes
ETH_EFM_REMFAULT Remote failure indication Critical Yes

OptiX OSN 8800/6800/3800

Affecting
ETH_LINK_DOWN Failure of network interface Critical Yes

connection
ETH_LOS Loss of Ethernet interface Critical Yes

connection
ETH_MISCONNECT Network interface Major No

misconnection alarm
ETH_NO_FLOW No traffic at Ethernet port Major No
ETH_SERVICE_CONFI Ethernet service Major No

G_FAIL configuration failure
ETHOAM_DISCOVER_ The point-to-point Ethernet Minor No

FAIL OAM discovery failure
alarm
ETHOAM_RMT_CRIT_ A critical fault occurs to the Minor Yes

FAULT remote end of point-to-point
Ethernet OAM
ETHOAM_RMT_LOOP The remote loopback of Minor Yes

point-to-point Ethernet
OAM alarm
ETHOAM_RMT_SD The remote SD of point-to- Minor Yes

point Ethernet OAM alarm
ETHOAM_SELF_LOOP Loopback of the MAC port Major Yes

that receives the OAM
protocol packets in a point-
to-point manner
ETHOAM_VCG_SELF_ Loopback of the Major Yes

LOOP VCTRUNK port that
receives the OAM protocol
packets in a point-to-point
manner
EX_ETHOAM_CC_LOS Loss of the periodic Critical Yes

continuity check message
EX_ETHOAM_MPID_C The maintenance point ID Major No

NFLCT conflict
EXT_MODULE_OFF- The extended wavelength Major Yes

LINE module offline
EXT_SYNC_LOS The loss of external clock Critical No

source

OptiX OSN 8800/6800/3800

Affecting
EXT_TIME_LOC The loss of the external Major No

timing source
2.1.6 Alarm List F

This section used a table to list the alarms starting with F.

Affecting
FAN_FAIL Fan failed Major No
FAN_FAULT Fan fault Minor No
FC_8B10BERR_OVER 8B10B bit error rate Minor Yes

crossing alarm
FC_LINK_ERR FC service link failure Critical Yes

alarm
FC_SYNC_LOS FC service synchronous Critical Yes

word loss alarm
FCS_ERR The frame check sequence Critical Yes

(FCS) is incorrect
FDBSIZEALM_ELAN MAC address forwarding Minor Yes

table of E-LAN used up
FEATURE_WITHOUT_LI- Service without license Major No

CENSE
FIBERTYPE_MIS Fiber type mismatch Major Yes
FLOW_OVER The inflow at the Ethernet Minor Yes

port exceeds the threshold
FEC_LOF Received FEC is loss of Critical Yes

frame
FEC_OOF Received FEC is out of Critical Yes

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

selected
FWD_PKT_LOSS Packets droped alarms Minor Yes

OptiX OSN 8800/6800/3800
2.1.7 Alarm List G

This section used a table to list the alarms starting with G.

Affecting
GAINDATA_MIS Mismatch of gain attribute Major Yes
GFP_UPM User payload mismatch Major Yes
2.1.8 Alarm List H

This section used a table to list the alarms starting with H.

Affecting
HARD_BAD Hardware failed Critical Yes
HARD_ERR Minor hardware error Minor No
HARD_NONSUPPORT Hardware does not Critical Yes

support the configuration
delivered by the SCC
board
HP_LOM Loss of multiframe in the Major Yes

higher order path
HP_RDI A remote defect in the Minor Yes

higher order path
HP_REI A remote error indication Warning Yes

in the higher order path
HP_SLM A signal label mismatch Minor Yes

alarm in the higher order
path
HP_TIM A trace identifier Minor Yes

mismatch alarm in the
higher order path
HP_UNEQ An alarm indicating that Minor Yes

no signals are loaded in the
higher order path
HSC_UNAVAIL Working/protection Minor No

switching failed

OptiX OSN 8800/6800/3800
2.1.9 Alarm List I

This section used a table to list the alarms starting with I.

Affecting
IN_PWR_ABN Input power abnormal Major Yes
IN_PWR_HIGH Input optical power is too Critical Yes

high
IN_PWR_LOW Input optical power is Critical No

excessively low
INSERTION_LOSS_HIGH Excessive insertion loss Major Yes

between the TDC and RDC
optical ports
INTRA_OTU_PS Intra-board 1+1 protection Major No

switching
INTRA_OTU_STA_INDI The state of the intra-board Minor No

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

This section used a table to list the alarms starting with J.

Affecting
J0_MM J0 byte or trace indicator Minor No

mismatch
2.1.11 Alarm List K

This section used a table to list the alarms starting with K.

Affecting
K1_K2_M The K1 and K2 bytes Minor No

mismatch alarm

OptiX OSN 8800/6800/3800

Affecting
K2_M The K2 bytes mismatch Minor No

alarm
2.1.12 Alarm List L

This section used a table to list the alarms starting with L.

Affecting
L_SYNC Loss of synchronization Critical Yes

alarm
LAG_DOWN LAG unavailable Major Yes
LAG_MEMBER_DOWN LAG member unavailable Minor Yes
LAG_PORT_FAIL Aggregation group VCG Minor Yes

port failure alarm
LAG_VC_PORT_FAIL Aggregation group VCG Minor Yes

port failure alarm
LAN_LOC Ethernet communication Major No

failure
LASER_HAZARD_WARN- Warning indication of the Critical No

ING laser hazard level.
LASER_MOD_ERR Wrong type of optical Major Yes

module inserted
LASER_MODULE_MIS- Optical module mismatch Major Yes

MATCH alarm
LASER_SHUT The laser of the board is Major Yes

shut down
LCAS_FOPR The failure of the LCAS Major Yes

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

protocol in the transmit
direction
LCAS_PLCR Partial loss of capacity in Minor Yes

the LCAS receive direction

OptiX OSN 8800/6800/3800

Affecting
LCAS_PLCT Partial loss of capacity in Minor Yes

the LCAS transmit
direction
LCAS_TLCR The total loss of capacity in Major Yes

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

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

attribute
LOCK_CUR_FAIL Pump drive current Critical Yes

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

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

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

the VC-3 lower order path
LPT_ACTIVE LPT switching is active Major No
LPT_RFI A remote failure indication Critical Yes

alarm of link state pass
through
LSR_BCM_ALM Laser bias current crossing Major No

the threshold
LSR_COOL_ALM Cooling current of the laser Major No

over threshold
LSR_NO_FITED Laser not installed Critical No

OptiX OSN 8800/6800/3800

Affecting
LSR_INVALID Invalid optical module Critical Yes

alarm
LSR_WILL_DIE Laser will be out of work Critical Yes
LTI The loss of synchronization Major No

source
2.1.13 Alarm List M

This section used a table to list the alarms starting with M.

Affecting
MAC_FCS_EXC Bit error threshold- Major Yes

crossing detected at MAC
layer
MAINBD_SUBBD_MIS- Mainboard and subboard Major No

MATCH mismatch
MCLAG_CFG_MIS- Configuration of MC-LAG Major Yes

MATCH Mismatch
MCSP_PATH_LOCV Loss of connection of the Major No

protocol channel for multi-
chassis synchronization
protocol
MOD_COM_FAIL Module communicates Critical Yes

abnormally
MODULE_ADJUST_FAIL Adjustment of optical Critical Yes

module failed
MODULE_COOLCUR_OV Module cooling current Major No

ER exceeds the threshold
MODULE_TEMP_OVER Module temperature Major No

MODULE_RATE_MIS- The signal rate Major Yes

MATCH mismatched with the
optical module.
MODULEFILE_UPDATE_ Updating the Major No

FAIL microprogram and laser
parameter table failed

OptiX OSN 8800/6800/3800

Affecting
MPLS_PW_AIS PW forward defect Major Yes
MPLS_PW_LOCV Loss of PW connectivity Critical Yes
MPLS_PW_OAMFAIL OAM protocol negotiation Minor Yes

failure
MPLS_PW_RDI PW backward defect Minor Yes
MPLS_PW_SD PW SD Major Yes
MPLS_PW_SF PW SF Major Yes
MPLS_PW_UNEXPMEG Unexpected MEG ID in Critical Yes

CCM packets of PW OAM
MPLS_PW_UNEXPMEP Unexpected MEP ID in Major Yes

CCM packets of PW OAM
MPLS_PW_UNEXPPER No expected CCM packets Major Yes

to PW
MPLS_TUNNEL_AIS Tunnel forward defect Major Yes
MPLS_TUNNEL_LOCV Loss of tunnel connectivity Critical Yes
MPLS_TUNNEL_OAM- OAM protocol negotiation Minor Yes

FAIL failure
MPLS_TUNNEL_RDI Tunnel backward defect Minor Yes
MPLS_TUNNEL_SD Tunnel SD Major Yes
MPLS_TUNNEL_SF Tunnel SF Major Yes
MPLS_TUNNEL_UNEXP- Unexpected MEP ID in Critical Yes

MEG CCM packets of tunnel
OAM
MPLS_TUNNEL_UNEXP- Unexpected MEP ID in Major Yes

MEP CCM packets of PW OAM
MPLS_TUNNEL_UNEXP- No expected CCM packets Major Yes

PER to the tunnel
MS_AIS Multiplex section alarm Major Yes

indication
MS_APS_INDI_EX An extended indication Major Yes

alarm of the MSP
switching state

OptiX OSN 8800/6800/3800

Affecting
MS_CROSSTR Multiplex section Minor Yes

performance over
threshold
MS_RDI Multiplex section remote Minor No

defect indication
MS_REI Multiplex section remote Warning Yes

error indication
MS_SNCP_PS MS SNCP protection Major Yes

switch
MS_SNCP_STA_INDI The state of the MS SNCP Minor No

protection group
MULTI_RPL_OWNER More than one Minor Yes

RPL_OWNER alarm
MUT_LOS Loss of multiplexed Critical Yes

signals
MUT_TLOS Loss of output multiplexed Critical Yes

signals
2.1.14 Alarm List N

This section used a table to list the alarms starting with N.

Affecting
NEBD_XC_DIF Crossing data of NE and Critical No

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

configured
NO_BD_PARA No board parameter Critical Yes
NO_BD_SOFT No board software Critical Yes
NO_ELABEL E-label unloaded Warning No
NODEID_MM The NODEID_MM is an Major No

alarm indicating the MSP
node ID mismatch

OptiX OSN 8800/6800/3800

Affecting
NTP_SYNC_FAIL NTP synchronization Minor No

failure
NULL_SEND The NULL signals Warning Yes

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

This section used a table to list the alarms starting with O.

Affecting
OA_LOW_GAIN Optical multiplexed signal Critical No

gain low
OA_HIGH_GAIN Gain of an optical amplifier Critical Yes

is high
OCH_FDI Forward defect indication Warning Yes

at OCh layer
OCH_FDI_O Forward defect indication Warning No

at OCh layer (overhead)
OCH_FDI_P Forward defect indication Warning Yes

at OCh layer (payload)
OCH_LOS_P Loss of signal (payload) at Critical Yes

OCh layer
OCH_OCI Open connection indication Minor Yes

at OCh layer
OCH_SSF Server signal fail at OCh Warning Yes

layer
OCH_SSF_O Server signal fail Warning No

(overhead) at OCh layer
OCH_SSF_P Server signal fail (payload) Warning Yes

at OCh layer
ODU_AIS ODU (optical channel data Warning Yes

unit) alarm indication
signal
ODU_LCK ODU locked Major Yes

OptiX OSN 8800/6800/3800

Affecting
ODU_OCI ODU open connection Major Yes

indication
ODU_SNCP_PS ODU SNCP protection Major No

switching
ODU_SNCP_STA_INDI The state of the ODU SNCP Minor No

protection group
ODUFLEX_LOFLOM The FAS and MFAS are Critical Yes

abnormal
ODUFLEX_PM_AIS ODUFlex PM Alarm Major Yes

Indication Signal
ODUFLEX_PM_BDI ODU0 PM Backward Minor No

Defect Indication
ODUFLEX_PM_DEG ODUFlex PM Signal Minor Yes

Degrade Alarm
ODUFLEX_PM_EXC ODUFlex PM Section Minor Yes

Excessive BIP8 Errors
defect
ODUFLEX_PM_LCK ODUFlex PM Lockout Minor Yes

Defect
ODUFLEX_PM_OCI ODUFlex PM Open Minor Yes

Connection Indication
ODUFLEX_PM_SSF ODUFlex PM Server Warning Yes

Signal Fail
ODUFLEX_PM_TIM ODUFlex PM Trace Minor Yes

Identifier Mismatch
ODU0_LOFLOM The FAS and MFAS are Critical Yes

abnormal
ODU0_PM_AIS ODU0 PM alarm indication Warning Yes

signal
ODU0_PM_BDI ODU0 PM backward defect Warning No

indication
ODU0_PM_DEG ODU0 PM signal degraded Minor Yes
ODU0_PM_LCK ODU0 PM signal locked Minor Yes
ODU0_PM_OCI ODU0 PM open connection Minor Yes

indication

OptiX OSN 8800/6800/3800

Affecting
ODU0_PM_SSF ODU0 PM Server signal Warning Yes

fail
ODU0_PM_TIM ODU0 PM section TTI Minor Yes

mismatch
ODU0_PM_EXC ODU0 PM section BIP8 Major Yes

excessive error defect
ODU0_TCMn_AIS ODU0 TCMn alarm Warning Yes

indication signal
ODU0_TCMn_BDI ODU0 TCMn backward Warning No

defect indication
ODU0_TCMn_DEG ODU0 TCMn signal Minor Yes

degraded
ODU0_TCMn_LCK ODU0 TCMn signal locked Minor Yes
ODU0_TCMn_LTC Loss of ODU0 TCMn serial Minor Yes

connection
ODU0_TCMn_OCI ODU0 TCMn open Minor Yes

connection indication
ODU0_TCMn_SSF ODU0 TCMn Server signal Warning Yes

fail
ODU0_TCMn_TIM ODU0 TCMn TTI Minor Yes

mismatch
ODU0_TCMn_EXC ODU0 TCMn section BIP8 Major Yes


abnormal

signal

indication

indication
ODU1_PM_SSF ODU1 PM Server signal Warning Yes

fail

OptiX OSN 8800/6800/3800

Affecting

mismatch


indication signal
ODU1_TCMn_BDI ODU1 TCMn backward Warning Yes

defect indication

degraded

connection

ODU1_TCMn_SSF ODU1 TCMn Server signal Warning Yes

fail

mismatch


abnormal

signal

indication

indication
ODU2_PM_SSF ODU2 PM server signal fail Warning Yes

mismatch

OptiX OSN 8800/6800/3800

Affecting


indication signal

defect indication

degraded

connection

ODU2_TCMn_SSF ODU2 TCMn server signal Warning Yes

fail

mismatch


signal

indication

indication

mismatch


indication signal

OptiX OSN 8800/6800/3800

Affecting

defect indication

degraded

connection


fail

mismatch


signal

indication

indication

mismatch

indication signal

defect indication

degraded

connection

OptiX OSN 8800/6800/3800

Affecting


fail

mismatch
ODU5G_LOFLOM The FAS and MFAS are Critical Yes

abnormal
ODU5G_PM_AIS ODU5G PM alarm Warning Yes

indication signal
ODU5G_PM_BDI ODU5G PM backward Warning No

defect indication
ODU5G_PM_DEG ODU5G PM signal Minor Yes

degraded
ODU5G_PM_EXC ODU5G PM section BIP8 Major Yes

ODU5G_PM_LCK ODU5G PM signal locked Minor Yes
ODU5G_PM_OCI ODU5G PM open Minor Yes

ODU5G_PM_SSF ODU5G PM server signal Warning Yes

fail
ODU5G_PM_TIM ODU5G PM section TTI Minor Yes

mismatch
ODU5G_TCMn_AIS ODU5G TCMn alarm Warning Yes

indication signal
ODU5G_TCMn_BDI ODU5G TCMn backward Warning Yes

defect indication
ODU5G_TCMn_DEG ODU5G TCMn signal Minor Yes

degraded
ODU5G_TCMn_EXC ODU5G TCMn section Major Yes

BIP8 excessive error defect
ODU5G_TCMn_LCK ODU5G TCMn signal Minor Yes

locked
ODU5G_TCMn_LTC Loss of ODU5G TCMn Minor Yes

serial connection

OptiX OSN 8800/6800/3800

Affecting
ODU5G_TCMn_OCI ODU5G TCMn open Minor Yes

ODU5G_TCMn_SSF ODU5G TCMn server Warning Yes

signal fail
ODU5G_TCMn_TIM ODU5G TCMn TTI Minor Yes

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

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

switching
OLP_STA_INDI The state of the optical line Minor No

protection group
OMS_BDI Backward defect indication Warning No

at OMS layer
OMS_BDI_O Backward defect indication Warning No

(overhead) at OMS layer
OMS_BDI_P Backward defect indication Warning No

(payload) at OMS layer
OMS_FDI Forward defect indication Warning Yes

at OMS layer
OMS_FDI_O Forward defect indication Warning No

OMS_FDI_P Forward defect indication Warning Yes

(payload) at OMS layer
OMS_LOS_P Loss of signal (payload) at Critical Yes

OMS layer
OMS_SSF Server signal fail at OMS Warning Yes

layer
OMS_SSF_O Server signal fail Warning No

OMS_SSF_P Server signal fail (payload) Warning Yes

at OMS layer
OOL The phase-locked loop is Major No

out of lock

OptiX OSN 8800/6800/3800

Affecting
OOS_LOST Loss of OOS Minor No
OPA_FAIL_INDI Automatic adjustment of Major Yes

power during optical cross-
connection failed
OPU0_CSF Client-side signals fail Minor Yes
OPU0_PLM OPU0 payload mismatch Minor Yes
OPU1_MSIM OPU1 multiplex structure Minor Yes

indicator mismatch
OPU1_VCAT_SQM OPU1 sequence indicator Major Yes

mismatch
OPU1_VCAT_VcPLM OPU1 virtual Minor Yes

concatenation payload
mismatch

indicator mismatch

indicator mismatch

indicator mismatch
OPU5G_PLM OPU5G payload mismatch Minor Yes
OPUFLEX_CSF Client-side signals fail Minor Yes
OPUFLEX_PLM OPUFLEX Payload Label Minor Yes

Mismatch
OSC_BDI OSC Backward defect Minor Yes

indication
OSC_DEG OSC signal degrade Minor Yes
OSC_LOS Loss of OSC signal Critical No

OptiX OSN 8800/6800/3800

Affecting
OSC_RDI Remote defect indication Minor No
OTU_AIS OTU alarm indication Warning Yes

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

signal
OTU1_BDI OTU1 backward defect Warning Yes

indication
OTU1_DEG OTU1 signal degraded Minor Yes
OTU1_EXC OTU1 BIP8 excessive error Major Yes

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

signal

indication

defect

signal

indication

OptiX OSN 8800/6800/3800

Affecting

defect

signal

indication
OTU5G_AIS OTU5G alarm indication Warning Yes

signal
OTU5G_BDI OTU5G backward defect Warning Yes

indication
OTU5G_DEG OTU5G signal degraded Minor Yes
OTU5G_EXC OTU5G BIP8 excessive Major Yes

error defect
OTU5G_LOF The FAS is abnormal Critical Yes
OTU5G_LOM The MFAS is abnormal Major Yes
OTU5G_SSF OTU5G server signal fail Warning Yes
OTU5G_TIM OTU5G TTI mismatch Minor Yes
OTS_BDI Backward defect indication Warning No

at OTS layer
OTS_BDI_O Backward defect indication Warning No

(overhead) at OTS layer
OTS_BDI_P Backward defect indication Warning No

(payload) at OTS layer

OptiX OSN 8800/6800/3800

Affecting
OTS_LOS Loss of signal at OTS layer Critical Yes
OTS_LOS_O Loss of signal (overhead) at Major No

OTS layer
OTS_LOS_P Loss of signal (payload) at Critical Yes

OTS layer
OTS_TIM Trail trace identifier Minor Yes

mismatch at OTS layer
OUT_PWR_HIGH Output optical power is too Major No

high
OUT_PWR_ABN Output power abnormal Critical Yes
OUT_PWR_LOW Output optical power is Major No

excessively low
OWSP_PS Optical wave share Major Yes

protection switching
OWSP_STA_INDI the state of the optical wave Minor No

share protection group
2.1.16 Alarm List P

This section used a table to list the alarms starting with P.

Affecting
PASSWORD_NEED_CHAN Default password must be Major No

GE changed
PATCH_ACT_TIMEOUT Activated patch overtime Minor No
PATCH_DEACT_TIME- Deactivated patch overtime Minor No

OUT
PATCH_PKGERR Patch package file error Minor No
PM_BDI ODU PM section backward Warning No

defect indication
PM_BEI ODU PM section backward Warning Yes

error indication
PM_BIP8_OVER ODU layer, PM section BIP Major Yes

exceed the upper threshold

OptiX OSN 8800/6800/3800

Affecting
PM_BIP8_SD Optical channel data unit Major Yes

layer, path monitoring
section bit interleaved
parity signal degraded
PM_TIM ODU layer PM section TTI Major Yes

mismatch
PORT_EXC_TRAFFIC Traffic at Ethernet ports Warning Yes

over the threshold
PORT_MODULE_OFFLINE Port module offline Major Yes
PORTSWITCH_FAIL Optical switch switching Major No

failure
POWER_ABNORMAL Power supply failure Major No
POWER_DIFF_OVER Power difference between Major Yes

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

alarm
PTP_TIMESTAMP_ABN PTP time stamp anomaly Major No
PUM_TEM_ALM Working temperature of the Major No

pump laser over threshold
PUM_BCM_ALM Working current of pump Major No

laser over threshold
PUMP_COOL_EXC Cooling current of pump Critical No

laser over threshold
PW_NO_TRAFFIC PW without traffic alarm Critical Yes
PWAPS_LOST PW APS frame lost Minor No
PWAPS_PATH_MIS- Mismatch of PW APS Major No

MATCH working/protection paths
PWAPS_SWITCH_FAIL PW APS protection Major No

switching failure
PWAPS_TYPE_MIS- Mismatch of PW APS Major No

MATCH protection type

OptiX OSN 8800/6800/3800
2.1.17 Alarm List R

This section used a table to list the alarms starting with R.

Affecting
R_LOC Loss of clock on receiving Critical Yes

line
R_LOF Loss of frame on receiving Critical Yes

line
R_LOS Loss of signal on receiving Critical Yes

line
R_OOF Out of frame on receiving Critical Yes

line
R_SLIP Receiving side frame Major Yes

slipping
RELAY_ALARM_CRITI- Critical relay alarm Critical No

CAL
RELAY_ALARM_IGNORE Relay alarm warning Warning No
RELAY_ALARM_MAJOR Major relay alarm Major No
RELAY_ALARM_Minor Remote signal degraded Minor No
REM_SD Remote signal degraded Minor Yes
REM_SF Remote signal failure alarm Minor Yes

indication
REMOTE_FAULT Remote fault Minor Yes
RL_CRITICAL_HI Critical high return loss Critical Yes

alarm
RL_CRITICAL_LOW Critical low return loss Critical Yes

alarm
RM_RLOS Loss of input reverse pump Major Yes

optical signals
RS_CROSSTR Regenerator section Minor Yes

performance over threshold
RTC_FAIL RTC time fail alarm Major No
RX_POWER_ABNORMAL Abnormal received optical Critical Yes

power

OptiX OSN 8800/6800/3800
2.1.18 Alarm List S

This section used a table to list the alarms starting with S.

Affecting
S1_SYN_CHANGE Synchronous source Major No

changed in S1 mode
SCC_LOC SCC loss of clock Critical No
SEC_RADIUS_FAIL Excessive failures in radius Major No

authentication
SECU_ALM Security alarm Major No
SERVICE_CAPACITY_EX The service capacity Major No

CEED_LICENSE exceeds the license limit
SERVICE_TYPE_EXCEED The service type exceeds Major No

_LICENSE the license limit
SHELF_AREA_POWER_O Total optical power Critical No

VER consumption of the subrack
SLAVE_WORKING The protection board is Warning No

working
SM_BDI OTU SM section backward Warning No

defect indication
SM_BEI OTU layer, SM section Warning Yes

backward error indication
SM_BIP8_OVER OTU layer, SM section bit Major Yes

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

interleaved parity
deterioration
SM_IAE OTU layer, SM section Warning Yes

incoming alignment error
SM_TIM OTU layer, SM Trail Trace Major Yes

Identifier (TTI) is
mismatched
SNCP_FAIL The SNCP switching failure Critical Yes
SPAN_LOSS_HIGH Span loss is excessively Major No

high

OptiX OSN 8800/6800/3800

Affecting
SPAN_LOSS_LOW Span loss is excessively low Major No
SO_SK_MISMATCH The number of timeslots Critical Yes

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

limits
SRV_SHUTDOWN_LD Ethernet service shutdown Warning Yes
SSL_CERT_NOENC The certificate file of SSL is Major No

not encrypted
SSM_LOS Loss of SSM quality Minor No

information
SSM_QL_FAILED Received SSM quality Minor No

worse than the threshold
STORM_CUR_QUENUM_ Alarm storm Minor No

OVER
SUBRACK_TYPE_MIS- The configured subrack Major No

MATCH does not match the physical
subrack
SUBRACK_COMM_PS Inter-subrack Major No

communication protection
switching alarm
SUBRACK_ID_CONFLICT Conflict of subrack ID Critical Yes
SUBRACK_ID_MIS- Mismatch of subrack ID Major No

MATCH
SUBRACK_LOOP Loop of subrack Critical No
SUM_INPWR_HI Sum input optical power is Major No

too high
SUM_INPWR_LOW Sum input optical power is Major No

excessively low
SW_SNCP_PS SW SNCP protection Major No

switching
SW_SNCP_STA_INDI The state of the Sub- Minor No

Wavelength SNCP
protection group.

OptiX OSN 8800/6800/3800

Affecting
SWDL_ACTIVATED_TIM Activation time out Critical No

EOUT
SWDL_AUTOMATCH_IN Automatic match inhibited Minor No

H
SWDL_BD_EXCLUDE Board excluded from Major No

software download during
software package loading
SWDL_CHGMNG_NO- Software mismatching Critical No

MATCH alarm after system control
board replacement
SWDL_COMMIT_FAIL Commit failure Minor No
SWDL_INPROCESS NE is loading package Warning No
SWDL_NEPKGCHECK Loss of file Critical No
SWDL_PKG_NOBDSOFT Board software cancelled Minor No

during the loading of
package
SWDL_PKGVER_MM Package version Minor No

conformance check failed
SWDL_ROLLBACK_FAIL NE rollback failed Minor No
SYN_BAD A synchronization source Minor No

degrade alarm
SYNC_FAIL Batch backup failed Minor No
SYSPARA_CFDB_NO- Difference between the Minor No

SAME SCC data and the CF card
data
SYNC_C_LOS The loss of synchronization Warning No

source level
SYNC_DISABLE Automatic synchronization Minor No

of the system control board
is disabled
SYNC_F_M_SWITCH The forced or manual Warning No

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

priority list is locked

OptiX OSN 8800/6800/3800

Affecting
SYSPARA_CFDB_NO- Difference between the Minor No

SAME SCC data and the CF card
data
SYSLOG_COMM_FAIL The communication Major No

between an NE and the
syslog server fails
2.1.19 Alarm List T

This section used a table to list the alarms starting with T.

Affecting
T_LOSEX A board has detected the Major Yes

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

slipping
TD Transmitter degrade Critical Yes
TEM_HA Laser temperature is too Major Yes

high
TEM_LA Laser temperature is Major Yes

excessively low
TEMP_OVER Working temperature over Major No

threshold
TEST_STATUS The board is in the test Warning No

status
TF Transmission Failure Critical Yes
THUNDERALM Thunder protection circuit Minor No

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

source level
TIME_NO_TRACE_MODE The time enters the non- Minor No

trace mode

OptiX OSN 8800/6800/3800

Affecting
TR_LOC The clock of the cross- Major Yes

connect board is faulty
TS_CFG_MISMATCH The timeslot configuration Major Yes

mismatch alarm
TU_AIS_VC3 A TU alarm indication Major Yes

signal in the VC-3 lower
order path
TU_LOP_VC3 An alarm indicating the loss Major Yes

of pointer in the VC-3 lower
order path
TUNNEL_APS_DEGRA- Downgrade of APS tunnel Major No

DED protection group
2.1.20 Alarm List V

This section used a table to list the alarms starting with V.

Affecting
VCAT_LOA Delay of multiframes Major Yes

VCAT_LOM_VC3 The loss of the virtual Major Yes

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

concatenation multiframe
in the VC-4 path
VCTRUNK_NO_FLOW No traffic at VCTRUNK Major Yes

port
VLAN_SNCP_PS VLAN SNCP switching Major Yes
VOADATA_MIS Mismatch of attenuation Major Yes

attribute
2.1.21 Alarm List W

This section used a table to list the alarms starting with W.

OptiX OSN 8800/6800/3800

Affecting
W_R_FAIL Writing or reading chip Major No

register failed
WAVE_ADD_ABN APE detect wavelengths Warning No

added
WAVE_DROP_ABN APE detect wavelengths Warning No

dropped
WAVEDATA_MIS Mismatch of wave or band Major Yes

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

with configured board
2.1.22 Alarm List X

This section used a table to list the alarms starting with X.

Affecting
XC_UNSWITCH The cross-connect matrix Major Yes

of the board is not switched
2.2 Board Alarm List

This topic lists the alarms of every board.
2.2.1 APIU Board Alarm List

TN21APIU
BD_STATUS POWER_FAIL WRG_BD_TYPE
2.2.2 ATE Board Alarm List

BD_STATUS WRG_BD_TYPE

OptiX OSN 8800/6800/3800
2.2.3 AUX Board Alarm List

TN11AUX
BD_LEDTEST HARD_BAD NO_ELABEL
BD_STATUS HARD_ERR WRG_BD_TYPE
COMMUN_FAIL LAN_LOC
ETH_MISCONNECT NO_BD_SOFT
TN22AUX
BD_LEDTEST HARD_ERR RELAY_ALARM_MINOR
BD_STATUS RELAY_ALARM_CRITI- WRG_BD_TYPE

CAL
COMMUN_FAIL RELAY_ALARM_IG-
NORE
HARD_BAD RELAY_ALARM_MAJOR
TN21AUX
BD_LEDTEST HARD_ERR RELAY_ALARM_IG-

NORE
BD_STATUS NO_BD_SOFT RELAY_ALARM_MAJOR
COMMUN_FAIL NO_ELABEL RELAY_ALARM_MINOR
HARD_BAD RELAY_ALARM_CRITI- WRG_BD_TYPE

CAL
TN51AUX
BD_LEDTEST COMMUN_FAIL HARD_ERR
BD_STATUS HARD_BAD WRG_BD_TYPE
TN16AUX
BD_LEDTEST HARD_BAD SWDL_PKGVER_MM
BD_STATUS HARD_ERR TEMP_OVER

OptiX OSN 8800/6800/3800
BOOTROM_BAD NO_BD_SOFT WRG_BD_TYPE
COMMUN_FAIL NO_ELABEL
EFI_TYPE_MIS- POWER_FAIL
MATCH
TN15AUX
SUBRACK_ID_MIS-
BD_LEDTEST HARD_ERR MATCH
BD_STATUS LAN_LOC SWDL_PKGVER_MM
BOOTROM_BAD NO_BD_SOFT TEMP_OVER
COMMUN_FAIL NO_ELABEL WRG_BD_TYPE
HARD_BAD POWER_FAIL
2.2.4 BMD4 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 BMD8 Board Alarm List

OMS_FDI OMS_SSF_O

OptiX OSN 8800/6800/3800
2.2.6 BPA Board Alarm List

BDID_ERROR IN_PWR_LOW PATCH_NOT_CONFIRM
BD_STATUS LOCK_CUR_FAIL POWER_ABNORMAL
BIOS_STATUS NO_BD_PARA PUMP_COOL_EXC
COMMUN_FAIL NO_BD_SOFT PUM_BCM_ALM
HARD_BAD OUT_PWR_ABN SWDL_PKG_NOBDSOFT
IN_PWR_FAIL PATCHFILE_NOTEXIST TEMP_OVER
IN_PWR_HIGH PATCH_ERR WRG_BD_TYPE
2.2.7 CMR1 Board Alarm List

BD_STATUS WAVEDATA_MIS WRG_BD_TYPE
OPA_FAIL_INDI

OPA_FAIL_INDI

OPA_FAIL_INDI
2.2.10 CRPC Board Alarm List

AD_CHECK_FAIL LOCK_CUR_FAIL POWER_FAIL
ALS_TRIGGERED LSR_WILL_DIE PUMP_COOL_EXC
BD_STATUS MUT_LOS PUM_BCM_ALM
COMMUN_FAIL NO_BD_PARA RL_CRITICAL_HI

OptiX OSN 8800/6800/3800
FAN_FAIL NO_BD_SOFT RL_CRITICAL_LOW
FPGA_ABN OPA_FAIL_INDI WRG_BD_TYPE
LASER_HAZARD_WARN- OUT_PWR_HIGH W_R_FAIL

ING
LOCKPOW_MIS OUT_PWR_LOW
2.2.11 D40V Board Alarm List

BD_LEDTEST NO_BD_SOFT OMS_SSF_O
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 OMS_FDI TEMP_OVER

AIL
MODULE_TEMP_OVER OMS_FDI_O WAVEDATA_MIS
MOD_COM_FAIL OMS_FDI_P WRG_BD_TYPE
MUT_LOS OMS_LOS_P
NO_BD_PARA OMS_SSF
2.2.12 D40 Board Alarm List

BD_LEDTEST NO_BD_SOFT OMS_SSF
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 OMS_FDI SUM_INPWR_LOW

ER
MODULE_TEMP_OVER OMS_FDI_O TEMP_OVER
MUT_LOS OMS_FDI_P WAVEDATA_MIS
NO_BD_PARA OMS_LOS_P WRG_BD_TYPE

OptiX OSN 8800/6800/3800
2.2.13 DAS1 Board Alarm List

BD_LEDTEST NO_ELABEL PUMP_COOL_EXC
BD_STATUS OA_LOW_GAIN PUM_BCM_ALM
BEFFEC_EXC OPA_FAIL_INDI PUM_TEM_ALM
COMMUN_FAIL OSC_BDI R_LOF
GAINDATA_MIS OSC_DEG SCC_LOC
HARD_BAD OSC_LOS SPAN_LOSS_HIGH
HARD_ERR OTS_BDI SPAN_LOSS_LOW
IN_PWR_HIGH OTS_BDI_O SUM_INPWR_HI
IN_PWR_LOW OTS_BDI_P SUM_INPWR_LOW
INSERTION_LOSS_HIGH OTS_LOS TD
LASER_HAZARD_WARN- OTS_LOS_O TEMP_OVER

ING
LASER_MODULE_MIS- OTS_LOS_P TF
MATCH
LOOP_ALM OTS_TIM VOADATA_MIS
LSR_WILL_DIE OOS_LOST WAVEDATA_MIS
MUT_LOS OUT_PWR_HIGH WRG_BD_TYPE
NO_BD_PARA OUT_PWR_LOW
PORT_MODULE_OFF-
NO_BD_SOFT LINE
2.2.14 DCU Board Alarm List

BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
2.2.15 DCP Board Alarm List

TN11DCP
BD_LEDTEST NO_BD_PARA OCh_SSF_O

OptiX OSN 8800/6800/3800
BD_STATUS NO_BD_SOFT OCh_SSF_P
CLIENT_PORT_PS NO_ELABEL OPA_FAIL_INDI
CLIENT_PORT_STA_IN- OCh_FDI OWSP_PS

DI
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
INTRA_OTU_STA_INDI OCh_SSF WRG_BD_TYPE
TN12DCP
BD_LEDTEST NO_BD_PARA OCh_SSF_P
BD_STATUS NO_BD_SOFT OPA_FAIL_INDI
CLIENT_PORT_PS OCh_FDI OWSP_PS
CLIENT_PORT_STA_IN- OCh_FDI_O OWSP_STA_INDI

DI
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
2.2.16 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

OptiX OSN 8800/6800/3800
2.2.17 DMR1 Board Alarm List

OPA_FAIL_INDI
2.2.18 EAS2 Board Alarm List

EX_ETHOAM_MPID_C
ALM_GFP_dCSF 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
PORT_MODULE_OFF-
BDID_ERROR HP_UNEQ LINE
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
LASER_MODULE_MIS
DLAG_PROTECT_FAIL 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

OptiX OSN 8800/6800/3800
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
2.2.19 ECOM Board Alarm List

BD_LEDTEST LOOP_ALM TEM_HA
BD_STATUS LSR_WILL_DIE TEM_LA
HARD_BAD OUT_PWR_HIGH TEMP_OVER
HARD_ERR OUT_PWR_LOW TF
IN_PWR_HIGH PORT_MODULE_OFF- WAVEDATA_MIS

LINE
IN_PWR_LOW R_LOS WRG_BD_TYPE
LASER_MODULE_MISMATCH TD
2.2.20 EFI Board Alarm List

TN11EFI
RELAY_ALARM_CRITI-
BD_STATUS CAL RELAY_ALARM_MINOR
ETH_MISCONNECT RELAY_ALARM_IGNORE WRG_BD_TYPE
LAN_LOC RELAY_ALARM_MAJOR
TN15EFI
RELAY_ALARM_CRITI-
RELAY_ALARM_MA- RELAY_ALARM_IGNORE WRG_BD_TYPE

JOR
TN16EFI

OptiX OSN 8800/6800/3800
RELAY_ALARM_CRITI-
ETH_MISCONNECT RELAY_ALARM_IGNORE WRG_BD_TYPE
2.2.21 EFI1 Board Alarm List

BD_STATUS RELAY_ALARM_CRITI- RELAY_ALARM_MINOR
CAL
HARD_BAD RELAY_ALARM_IG- WRG_BD_TYPE

NORE
2.2.22 EFI2 Board Alarm List

BD_STATUS HARD_BAD LAN_LOC
ETH_MISCONNECT WRG_BD_TYPE
2.2.23 EGSH Board Alarm List

ALM_GFP_dCSF EX_ETHOAM_CC_LOS LSR_WILL_DIE
ALM_GFP_dLFD EX_ETHOAM_MPID_CNFL MULTI_RPL_OWNER

CT
AU_AIS FCS_ERR NO_BD_SOFT
AU_LOP FLOW_OVER NO_ELABEL
B3_EXC_VC3 HARD_BAD OUT_PWR_HIGH
B3_EXC_VC4 HARD_ERR OUT_PWR_LOW
B3_SD_VC3 HP_RDI PORT_MODULE_OFF-

LINE
B3_SD_VC4 HP_SLM R_LOS
BDID_ERROR HP_UNEQ SLAVE_WORKING
BD_STATUS IN_PWR_HIGH SO_SK_MISMATCH

OptiX OSN 8800/6800/3800
BOOTROM_BAD IN_PWR_LOW TD
CHIP_ABN LAG_PORT_FAIL TEMP_OVER
COMMUN_FAIL LASER_MODULE_MIS- TEM_HA

MATCH
DLAG_PROTECT_FAIL LCAS_FOPR TEM_LA
ETHOAM_DISCOVER_FA LCAS_FOPT TEST_STATUS

IL
ETHOAM_RMT_CRIT_FA LCAS_PLCR TF
ULT
ETHOAM_RMT_LOOP LCAS_PLCT TR_LOC
ETHOAM_RMT_SD LCAS_TLCR TU_AIS_VC3
ETHOAM_SELF_LOOP LCAS_TLCT TU_LOP_VC3
ETHOAM_VCG_SELF_LO LINK_ERR T_LOSEX

OP
ETH_CFM_LOC LOOP_ALM VCAT_LOA
ETH_CFM_MACSTATUS LPT_RFI VCAT_LOM_VC3
ETH_CFM_MISMERGE LP_RDI_VC3 VCAT_LOM_VC4
ETH_CFM_RDI LP_SLM_VC3 VCTRUNK_NO_FLOW
ETH_CFM_UNEXPERI LP_UNEQ_VC3 WRG_BD_TYPE
ETH_NO_FLOW LSR_INVALID
2.2.24 ELQX Board Alarm List

BD_LEDTEST ODU1_TCM3_TIM ODU2_TCM3_SSF
B1_EXC ODU1_TCM4_AIS ODU2_TCM3_TIM
B1_SD ODU1_TCM4_BDI ODU2_TCM4_AIS
BD_STATUS ODU1_TCM4_DEG ODU2_TCM4_BDI
BEFFEC_EXC ODU1_TCM4_LCK ODU2_TCM4_DEG
BUS_ERR ODU1_TCM4_LTC ODU2_TCM4_LCK
CLIENT_PORT_PS ODU1_TCM4_OCI ODU2_TCM4_LTC
CLIENT_PORT_STA_INDI ODU1_TCM4_SSF ODU2_TCM4_OCI
CLIENT_PROT_NOTSTART ODU1_TCM4_TIM ODU2_TCM4_SSF

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU1_TCM5_AIS ODU2_TCM4_TIM
HARD_BAD ODU1_TCM5_BDI ODU2_TCM5_AIS
HARD_ERR ODU1_TCM5_DEG ODU2_TCM5_BDI
IN_PWR_HIGH ODU1_TCM5_LCK ODU2_TCM5_DEG
IN_PWR_LOW ODU1_TCM5_LTC ODU2_TCM5_LCK
J0_MM ODU1_TCM5_OCI ODU2_TCM5_LTC
LASER_MODULE_MIS- ODU1_TCM5_SSF ODU2_TCM5_OCI

MATCH
LOCAL_FAULT ODU1_TCM5_TIM ODU2_TCM5_SSF
LOOP_ALM ODU1_TCM6_AIS ODU2_TCM5_TIM
LPT_ACTIVE 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
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

OptiX OSN 8800/6800/3800
ODU1_TCM1_TIM ODU2_TCM1_SSF OUT_PWR_LOW
ODU1_TCM2_AIS ODU2_TCM1_TIM PORT_MODULE_OFF-

LINE
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
ODU1_TCM3_OCI ODU2_TCM3_LTC WAVEDATA_MIS
ODU1_TCM3_SSF ODU2_TCM3_OCI WRG_BD_TYPE
2.2.25 ENQ2 Board Alarm List

TN54ENQ2(STND)
BD_LEDTEST COMMUN_FAIL NO_ELABEL
BD_STATUS HARD_BAD TEMP_OVER
BUS_ERR HARD_ERR WRG_BD_TYPE
TN54ENQ2
BD_LEDTEST ODU1_TCM3_TIM ODU2_TCM3_DEG
BD_STATUS ODU1_TCM4_AIS ODU2_TCM3_LCK
BEFFEC_EXC ODU1_TCM4_BDI ODU2_TCM3_LTC
BUS_ERR ODU1_TCM4_DEG ODU2_TCM3_OCI

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU1_TCM4_LCK ODU2_TCM3_SSF
HARD_BAD ODU1_TCM4_LTC ODU2_TCM3_TIM
HARD_ERR ODU1_TCM4_OCI ODU2_TCM4_AIS
LOOP_ALM ODU1_TCM4_SSF ODU2_TCM4_BDI
NO_BD_SOFT ODU1_TCM4_TIM ODU2_TCM4_DEG
NO_ELABEL ODU1_TCM5_AIS ODU2_TCM4_LCK
NULL_SEND ODU1_TCM5_BDI ODU2_TCM4_LTC
ODU0_LOFLOM ODU1_TCM5_DEG ODU2_TCM4_OCI
ODU0_PM_AIS ODU1_TCM5_LCK ODU2_TCM4_SSF
ODU0_PM_BDI ODU1_TCM5_LTC ODU2_TCM4_TIM
ODU0_PM_DEG ODU1_TCM5_OCI ODU2_TCM5_AIS
ODU0_PM_LCK ODU1_TCM5_SSF ODU2_TCM5_BDI
ODU0_PM_OCI ODU1_TCM5_TIM ODU2_TCM5_DEG
ODU0_PM_SSF ODU1_TCM6_AIS ODU2_TCM5_LCK
ODU0_PM_TIM ODU1_TCM6_BDI ODU2_TCM5_LTC
ODU1_LOFLOM ODU1_TCM6_DEG ODU2_TCM5_OCI
ODU1_PM_AIS ODU1_TCM6_LCK ODU2_TCM5_SSF
ODU1_PM_BDI ODU1_TCM6_LTC ODU2_TCM5_TIM
ODU1_PM_DEG ODU1_TCM6_OCI ODU2_TCM6_AIS
ODU1_PM_LCK ODU1_TCM6_SSF ODU2_TCM6_BDI
ODU1_PM_OCI ODU1_TCM6_TIM ODU2_TCM6_DEG
ODU1_PM_SSF ODU2_PM_AIS ODU2_TCM6_LCK
ODU1_PM_TIM ODU2_PM_BDI ODU2_TCM6_LTC
ODU1_TCM1_AIS ODU2_PM_DEG ODU2_TCM6_OCI
ODU1_TCM1_BDI ODU2_PM_LCK ODU2_TCM6_SSF
ODU1_TCM1_DEG ODU2_PM_OCI ODU2_TCM6_TIM
ODU1_TCM1_LCK ODU2_PM_SSF ODUKSP_PS
ODU1_TCM1_LTC ODU2_PM_TIM ODUKSP_STA_INDI
ODU1_TCM1_OCI ODU2_TCM1_AIS ODU_SNCP_PS
ODU1_TCM1_SSF ODU2_TCM1_BDI ODU_SNCP_STA_INDI

OptiX OSN 8800/6800/3800
ODU1_TCM1_TIM ODU2_TCM1_DEG OPU1_MSIM
ODU1_TCM2_AIS ODU2_TCM1_LCK OPU1_PLM
ODU1_TCM2_BDI ODU2_TCM1_LTC OPU2_MSIM
ODU1_TCM2_DEG ODU2_TCM1_OCI OPU2_PLM
ODU1_TCM2_LCK ODU2_TCM1_SSF OTU2_AIS
ODU1_TCM2_LTC ODU2_TCM1_TIM OTU2_BDI
ODU1_TCM2_OCI ODU2_TCM2_AIS OTU2_DEG
ODU1_TCM2_SSF ODU2_TCM2_BDI OTU2_LOF
ODU1_TCM2_TIM ODU2_TCM2_DEG OTU2_LOM
ODU1_TCM3_AIS ODU2_TCM2_LCK OTU2_SSF
ODU1_TCM3_BDI ODU2_TCM2_LTC OTU2_TIM
ODU1_TCM3_DEG ODU2_TCM2_OCI PRBS_LSS
ODU1_TCM3_LCK ODU2_TCM2_SSF TEMP_OVER
ODU1_TCM3_LTC ODU2_TCM2_TIM WRG_BD_TYPE
ODU1_TCM3_OCI ODU2_TCM3_AIS
ODU1_TCM3_SSF ODU2_TCM3_BDI
2.2.26 EG16 Board Alarm List

BD_LEDTEST HARD_ERR MPLS_TUNNEL_AIS
MPLS_TUNNEL_OAM-
BD_STATUS IN_PWR_ABN FAIL
BWUTILIZATION_OVE
R IN_PWR_HIGH MPLS_TUNNEL_RDI
MPLS_TUNNEL_UNEXP-
COMMUN_FAIL IN_PWR_LOW MEG
MPLS_TUNNEL_UNEXP-
ETHOAM_SELF_LOOP LAG_DOWN MEP
MPLS_TUNNEL_UNEXP-
ETH_APS_LOST LAG_MEMBER_DOWN PER
ETH_APS_PATH_MIS-
MATCH LASER_MOD_ERR MPLS_TUNNEL_LOCV

OptiX OSN 8800/6800/3800
ETH_APS_SWITCH_FA
IL LASER_SHUT MPLS_TUNNEL_SD
ETH_APS_TYPE_MIS-
MATCH LOOP_ALM MPLS_TUNNEL_SF
ETH_CFM_AIS LSR_BCM_ALM NO_ELABEL
ETH_CFM_LOC LSR_NO_FITED OUT_PWR_ABN
ETH_CFM_MISMERGE LSR_WILL_DIE PORT_EXC_TRAFFIC
ETH_CFM_RDI MAC_FCS_EXC PWAPS_LOST
PWAPS_PATH_MIS-
ETH_CFM_UNEXPERI MCLAG_CFG_MISMATCH MATCH
ETH_EFM_DF MCSP_PATH_LOCV PWAPS_SWITCH_FAIL
PWAPS_TYPE_MIS-
ETH_EFM_EVENT MPLS_PW_AIS MATCH
ETH_EFM_LOOPBACK MPLS_PW_LOCV PW_NO_TRAFFIC
ETH_EFM_REMFAULT MPLS_PW_OAMFAIL SRV_SHUTDOWN_LD
ETH_LINK_DOWN MPLS_PW_RDI TEMP_OVER
ETH_LOS MPLS_PW_SD TEM_HA
ETH_NO_FLOW MPLS_PW_SF TEM_LA
TUNNEL_APS_DEGRA-
FDBSIZEALM_ELAN MPLS_PW_UNEXPMEG DED
FLOW_OVER MPLS_PW_UNEXPMEP WRG_BD_TYPE
HARD_BAD MPLS_PW_UNEXPPER
2.2.27 EX2 Board Alarm List

BD_LEDTEST HARD_ERR MPLS_TUNNEL_AIS
MPLS_TUNNEL_OAM-
BD_STATUS IN_PWR_ABN FAIL
BWUTILIZATION_OVE
R IN_PWR_HIGH MPLS_TUNNEL_RDI
MPLS_TUNNEL_UNEXP-
COMMUN_FAIL IN_PWR_LOW MEG
MPLS_TUNNEL_UNEXP-
ETHOAM_SELF_LOOP LAG_DOWN MEP

OptiX OSN 8800/6800/3800
MPLS_TUNNEL_UNEXP-
ETH_APS_LOST LAG_MEMBER_DOWN PER
ETH_APS_PATH_MIS-
MATCH LASER_MOD_ERR MPLS_TUNNEL_LOCV
ETH_APS_SWITCH_FA
IL LASER_SHUT MPLS_TUNNEL_SD
ETH_APS_TYPE_MIS-
MATCH LOOP_ALM MPLS_TUNNEL_SF
ETH_CFM_AIS LSR_BCM_ALM NO_ELABEL
ETH_CFM_LOC LSR_NO_FITED OUT_PWR_ABN
ETH_CFM_MISMERGE LSR_WILL_DIE PORT_EXC_TRAFFIC
ETH_CFM_RDI MAC_FCS_EXC PWAPS_LOST
PWAPS_PATH_MIS-
ETH_CFM_UNEXPERI MCLAG_CFG_MISMATCH MATCH
ETH_EFM_DF MCSP_PATH_LOCV PWAPS_SWITCH_FAIL
PWAPS_TYPE_MIS-
ETH_EFM_EVENT MPLS_PW_AIS MATCH
ETH_EFM_LOOPBACK MPLS_PW_LOCV PW_NO_TRAFFIC
ETH_EFM_REMFAULT MPLS_PW_OAMFAIL SRV_SHUTDOWN_LD
ETH_LINK_DOWN MPLS_PW_RDI TEMP_OVER
ETH_LOS MPLS_PW_SD TEM_HA
ETH_NO_FLOW MPLS_PW_SF TEM_LA
TUNNEL_APS_DEGRA-
FDBSIZEALM_ELAN MPLS_PW_UNEXPMEG DED
FLOW_OVER MPLS_PW_UNEXPMEP WRG_BD_TYPE
HARD_BAD MPLS_PW_UNEXPPER
2.2.28 FAN Board Alarm List

TN11FAN/TN21FAN/TN51FAN
BD_STATUS FAN_FAULT WRG_BD_TYPE
FAN_FAIL
TN16FAN/TN15FAN

OptiX OSN 8800/6800/3800
BD_STATUS FAN_FAULT WRG_BD_TYPE
FAN_FAIL HARD_ERR
2.2.29 FIU Board Alarm List

TN14FIU
BD_LEDTEST OOS_LOST OTS_LOS_O
BD_STATUS OPA_FAIL_INDI OTS_LOS_P
COMMUN_FAIL OTS_BDI OTS_TIM
HARD_BAD OTS_BDI_O RM_RLOS
HARD_ERR OTS_BDI_P TEMP_OVER
MUT_LOS OTS_LOS WRG_BD_TYPE
TN13FIU
OTS_BDI OTS_LOS-P
TN12FIU
BD_LEDTEST OPA_FAIL_INDI OTS_TIM
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
TN11FIU

OptiX OSN 8800/6800/3800
BD_LEDTEST NO_ELABEL OTS_LOS-P
BD_STATUS OOS_LOST OTS_TIM
COMMUN_FAIL OPA_FAIL_INDI SUM_INPWR_HI
HARD_BAD OTS_BDI SUM_INPWR_LOW
HARD_ERR OTS_BDI-O TEMP_OVER
NO_BD_PARA OTS_LOS WRG_BD_TYPE
NO_BD_SOFT OTS_LOS-O
TN21FIU
OTS_BDI OTS_LOS-P
2.2.30 GFU Board Alarm List

BD_STATUS OPA_FAIL_INDI WRG_BD_TYPE
COMMUN_FAIL
2.2.31 HBA Board Alarm List

BD_LEDTEST LASER_HAZARD_WARN- SPAN_LOSS_LOW
ING
BD_STATUS 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

OptiX OSN 8800/6800/3800
2.2.32 HSC1 Board Alarm List

TN11HSC1
ALM_HANGUP LOOP_ALM OUT_PWR_LOW
BD_LEDTEST 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
2.2.33 ITL Board Alarm List

TN11ITL
OMS_FDI OMS_SSF_O
TN12ITL
BD_LEDTEST OMS_BDI_P OMS_SSF_P
BD_STATUS OMS_FDI OPA_FAIL_INDI
COMMUN_FAIL OMS_FDI_O TEMP_OVER
HARD_BAD OMS_FDI_P WAVEDATA_MIS
HARD_ERR OMS_LOS_P WRG_BD_TYPE
OMS_BDI OMS_SSF
OMS_BDI_O OMS_SSF_O

OptiX OSN 8800/6800/3800
2.2.34 L4G Board Alarm List

B1_EXC ODU5G_PM_SSF ODU5G_TCM5_LTC
B1_SD ODU5G_PM_TIM ODU5G_TCM5_OCI
BD_STATUS ODU5G_TCM1_AIS ODU5G_TCM5_SSF
BEFFEC_EXC ODU5G_TCM1_BDI ODU5G_TCM5_TIM
BUS_ERR ODU5G_TCM1_DEG ODU5G_TCM6_AIS
CLIENT_PORT_PS ODU5G_TCM1_EXC ODU5G_TCM6_BDI
CLIENT_PORT_STA_INDI ODU5G_TCM1_LCK ODU5G_TCM6_DEG
CLIENT_PROT_NOTSTART ODU5G_TCM1_LTC ODU5G_TCM6_EXC
COMMUN_FAIL ODU5G_TCM1_OCI ODU5G_TCM6_LCK
HARD_BAD ODU5G_TCM1_SSF ODU5G_TCM6_LTC
HARD_ERR ODU5G_TCM1_TIM ODU5G_TCM6_OCI
IN_PWR_HIGH ODU5G_TCM2_AIS ODU5G_TCM6_SSF
IN_PWR_LOW ODU5G_TCM2_BDI ODU5G_TCM6_TIM
J0_MM ODU5G_TCM2_DEG OPA_FAIL_INDI
LAG_PORT_FAIL ODU5G_TCM2_EXC OPU5G_PLM
LAG_VC_PORT_FAIL ODU5G_TCM2_LCK OTU5G_AIS
LASER_MODULE_MIS- ODU5G_TCM2_LTC OTU5G_BDI

MATCH
LINK_ERR ODU5G_TCM2_OCI OTU5G_DEG
LOOP_ALM ODU5G_TCM2_SSF OTU5G_EXC
LPT_ACTIVE 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_OFF-

LINE
NO_BD_SOFT ODU5G_TCM3_OCI REM_SD
NO_ELABEL ODU5G_TCM3_SSF REM_SF

OptiX OSN 8800/6800/3800
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
ODU5G_PM_OCI ODU5G_TCM5_LCK
2.2.35 LDGD Board Alarm List

ALS_ACTIVE ODU1_PM_DEG ODU1_TCM5_EXC
B1_EXC ODU1_PM_EXC ODU1_TCM5_LCK
B1_SD ODU1_PM_LCK ODU1_TCM5_LTC
B2_EXC ODU1_PM_OCI ODU1_TCM5_OCI
B2_SD ODU1_PM_SSF ODU1_TCM5_SSF
BD_LEDTEST 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
CLIENT_PORT_STA_INDI ODU1_TCM1_LCK ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_LTC ODU1_TCM6_LTC

OptiX OSN 8800/6800/3800
COMMUN_FAIL 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
LASER_MODULE_MIS- ODU1_TCM2_LTC OTU1_EXC

MATCH
LINK_ERR ODU1_TCM2_OCI OTU1_LOF
LOOP_ALM ODU1_TCM2_SSF OTU1_LOM
LPT_ACTIVE ODU1_TCM2_TIM OTU1_SSF
LSR_COOL_ALM ODU1_TCM3_AIS OTU1_TIM
LSR_INVALID ODU1_TCM3_BDI OUT_PWR_HIGH
LSR_WILL_DIE ODU1_TCM3_DEG OUT_PWR_LOW
MS_AIS ODU1_TCM3_EXC PORT_MODULE_OFF-

LINE
MS_CROSSTR ODU1_TCM3_LCK REM_SD
MS_RDI ODU1_TCM3_LTC REM_SF
MS_SNCP_PS ODU1_TCM3_OCI RS_CROSSTR
MS_SNCP_STA_INDI ODU1_TCM3_SSF R_LOC
NO_BD_SOFT ODU1_TCM3_TIM R_LOF
NO_ELABEL ODU1_TCM4_AIS R_LOS
OCh_FDI ODU1_TCM4_BDI SW_SNCP_PS
OCh_FDI_O ODU1_TCM4_DEG SW_SNCP_STA_INDI
OCh_FDI_P ODU1_TCM4_EXC TD
OCh_LOS_P ODU1_TCM4_LCK TEMP_OVER
OCh_OCI ODU1_TCM4_LTC TEM_HA
OCh_SSF ODU1_TCM4_OCI TEM_LA
OCh_SSF_O ODU1_TCM4_SSF TF

OptiX OSN 8800/6800/3800
OCh_SSF_P ODU1_TCM4_TIM WAVEDATA_MIS
ODU1_LOFLOM ODU1_TCM5_AIS WRG_BD_TYPE
ODU1_PM_AIS ODU1_TCM5_BDI
ODU1_PM_BDI ODU1_TCM5_DEG
2.2.36 LDGS Board Alarm List

ALS_ACTIVE ODU1_PM_EXC ODU1_TCM5_EXC
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_LEDTEST ODU1_TCM1_AIS ODU1_TCM5_TIM
BD_STATUS ODU1_TCM1_BDI ODU1_TCM6_AIS
BEFFEC_EXC ODU1_TCM1_DEG ODU1_TCM6_BDI
BUS_ERR ODU1_TCM1_EXC ODU1_TCM6_DEG
CLIENT_PORT_PS ODU1_TCM1_LCK ODU1_TCM6_EXC
CLIENT_PORT_STA_INDI ODU1_TCM1_LTC ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_OCI ODU1_TCM6_LTC
COMMUN_FAIL ODU1_TCM1_SSF ODU1_TCM6_OCI
HARD_BAD ODU1_TCM1_TIM ODU1_TCM6_SSF
HARD_ERR ODU1_TCM2_AIS ODU1_TCM6_TIM
IN_PWR_HIGH ODU1_TCM2_BDI OPA_FAIL_INDI
IN_PWR_LOW ODU1_TCM2_DEG OPU1_PLM
J0_MM ODU1_TCM2_EXC OTU1_AIS
LASER_MODULE_MIS- ODU1_TCM2_LCK OTU1_BDI

MATCH
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

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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
2.2.37 LDM Board Alarm List

ALS_ACTIVE ODU1_PM_TIM ODU1_TCM5_OCI
B1_EXC ODU1_TCM1_AIS ODU1_TCM5_SSF
B1_SD ODU1_TCM1_BDI ODU1_TCM5_TIM
BD_LEDTEST ODU1_TCM1_DEG ODU1_TCM6_AIS
BD_STATUS ODU1_TCM1_EXC ODU1_TCM6_BDI

OptiX OSN 8800/6800/3800
CLIENT_PORT_PS ODU1_TCM1_LTC ODU1_TCM6_EXC
CLIENT_PORT_STA_INDI ODU1_TCM1_OCI ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_SSF ODU1_TCM6_LTC
COMMUN_FAIL ODU1_TCM1_TIM ODU1_TCM6_OCI
HARD_BAD ODU1_TCM2_AIS ODU1_TCM6_SSF
HARD_ERR ODU1_TCM2_BDI ODU1_TCM6_TIM
INTRA_OTU_PS ODU1_TCM2_DEG OPA_FAIL_INDI
INTRA_OTU_STA_INDI ODU1_TCM2_EXC OPU1_PLM
IN_PWR_HIGH ODU1_TCM2_LCK OTU1_AIS
IN_PWR_LOW ODU1_TCM2_LTC OTU1_BDI
J0_MM ODU1_TCM2_OCI OTU1_DEG
LASER_MODULE_MIS- ODU1_TCM2_SSF OTU1_EXC

MATCH
LINK_ERR ODU1_TCM2_TIM OTU1_LOF
LOOP_ALM ODU1_TCM3_AIS OTU1_LOM
LPT_ACTIVE ODU1_TCM3_BDI OTU1_SSF
LSR_INVALID ODU1_TCM3_DEG OTU1_TIM
LSR_WILL_DIE ODU1_TCM3_EXC OUT_PWR_HIGH
L_SYNC ODU1_TCM3_LCK OUT_PWR_LOW
NO_BD_SOFT ODU1_TCM3_LTC PORT_MODULE_OFF-

LINE
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

OptiX OSN 8800/6800/3800
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
ODU1_PM_LCK ODU1_TCM5_EXC WRG_BD_TYPE
ODU1_PM_OCI ODU1_TCM5_LCK
ODU1_PM_SSF ODU1_TCM5_LTC
2.2.38 LDMD Board Alarm List

ALS_ACTIVE ODU1_PM_OCI ODU1_TCM5_LCK
B1_EXC ODU1_PM_SSF ODU1_TCM5_LTC
B1_SD ODU1_PM_TIM ODU1_TCM5_OCI
BD_LEDTEST ODU1_TCM1_AIS ODU1_TCM5_SSF
BD_STATUS ODU1_TCM1_BDI ODU1_TCM5_TIM
BEFFEC_EXC ODU1_TCM1_DEG ODU1_TCM6_AIS
CLIENT_PORT_PS ODU1_TCM1_EXC ODU1_TCM6_BDI
CLIENT_PORT_STA_INDI ODU1_TCM1_LCK ODU1_TCM6_DEG
CLIENT_PROT_NOTSTART ODU1_TCM1_LTC ODU1_TCM6_EXC
COMMUN_FAIL ODU1_TCM1_OCI ODU1_TCM6_LCK
HARD_BAD ODU1_TCM1_SSF ODU1_TCM6_LTC
HARD_ERR ODU1_TCM1_TIM ODU1_TCM6_OCI
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 OPU1_PLM
IN_PWR_LOW ODU1_TCM2_EXC OTU1_AIS
J0_MM ODU1_TCM2_LCK OTU1_BDI
LASER_MODULE_MIS- ODU1_TCM2_LTC OTU1_DEG

MATCH
LINK_ERR ODU1_TCM2_OCI OTU1_EXC

OptiX OSN 8800/6800/3800
LOOP_ALM ODU1_TCM2_SSF OTU1_LOF
LPT_ACTIVE ODU1_TCM2_TIM OTU1_LOM
LSR_COOL_ALM 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
MS_AIS ODU1_TCM3_LCK PORT_MODULE_OFF-

LINE
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.39 LDMS Board Alarm List

ALS_ACTIVE ODU1_PM_TIM ODU1_TCM5_OCI
B1_EXC ODU1_TCM1_AIS ODU1_TCM5_SSF
B1_SD ODU1_TCM1_BDI ODU1_TCM5_TIM

OptiX OSN 8800/6800/3800
BD_LEDTEST ODU1_TCM1_DEG ODU1_TCM6_AIS
BD_STATUS ODU1_TCM1_EXC ODU1_TCM6_BDI
CLIENT_PORT_PS ODU1_TCM1_LTC ODU1_TCM6_EXC
CLIENT_PORT_STA_INDI ODU1_TCM1_OCI ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_SSF ODU1_TCM6_LTC
IN_PWR_LOW ODU1_TCM2_EXC OTU1_AIS
J0_MM ODU1_TCM2_LCK OTU1_BDI
LASER_MODULE_MIS- ODU1_TCM2_LTC OTU1_DEG

MATCH
LINK_ERR ODU1_TCM2_OCI OTU1_EXC
LPT_ACTIVE ODU1_TCM2_TIM OTU1_LOM
LSR_COOL_ALM 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
MS_AIS ODU1_TCM3_LCK PORT_MODULE_OFF-

LINE
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

OptiX OSN 8800/6800/3800
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_EXC ODU1_TCM5_DEG WRG_BD_TYPE
ODU1_PM_LCK ODU1_TCM5_EXC
ODU1_PM_OCI ODU1_TCM5_LCK
ODU1_PM_SSF ODU1_TCM5_LTC
2.2.40 LDX Board Alarm List

ALS_ACTIVE ODU2_PM_TIM ODU2_TCM5_SSF
BD_LEDTEST ODU2_TCM1_DEG ODU2_TCM6_BDI
BD_STATUS ODU2_TCM1_LCK ODU2_TCM6_DEG
BEFFEC_EXC ODU2_TCM1_LTC ODU2_TCM6_LCK
HARD_BAD ODU2_TCM2_BDI OPA_FAIL_INDI
HARD_ERR ODU2_TCM2_DEG OPU2_PLM
LASER_MODULE_MIS- ODU2_TCM2_SSF OTU2_LOF

MATCH

OptiX OSN 8800/6800/3800
LOCAL_FAULT ODU2_TCM2_TIM OTU2_LOM
LOOP_ALM ODU2_TCM3_AIS OTU2_SSF
LPT_ACTIVE ODU2_TCM3_BDI OTU2_TIM
LSR_COOL_ALM ODU2_TCM3_DEG OUT_PWR_HIGH
LSR_INVALID ODU2_TCM3_LCK OUT_PWR_LOW
LSR_WILL_DIE ODU2_TCM3_LTC PORT_MODULE_OFF-

LINE
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
2.2.41 LEM24 Board Alarm List

ALS_ACTIVE HARD_ERR ODU2_TCMn_OCI
B1_EXC IN_PWR_HIGH ODU2_TCMn_SSF
B1_SD IN_PWR_LOW ODU2_TCMn_TIM
BD_LEDTEST J0_MM OPA_FAIL_INDI

OptiX OSN 8800/6800/3800
BD_STATUS LAG_PORT_FAIL OPU2_PLM
BEFFEC_EXC LAG_VC_PORT_FAIL OTU2_AIS
LASER_MODULE_MIS-
BUS_ERR MATCH OTU2_BDI
CLIENT_PORT_PS LINK_ERR OTU2_DEG
CLIENT_PORT_STA_I
NDI LOOP_ALM OTU2_LOF
CLIENT_PROT_NOT-
START LPT_ACTIVE OTU2_LOM
COMMUN_FAIL LPT_RFI OTU2_SSF
DBPS_ABNORMAL LSR_COOL_ALM OTU2_TIM
ERPS_IN_PROTEC-
TION LSR_INVALID OUT_PWR_HIGH
ETHOAM_DISCOVER_
FAIL LSR_WILL_DIE OUT_PWR_LOW
ETHOAM_RMT_CRIT_
FAULT MULTI_RPL_OWNER PORT_MODULE_OFFLINE
ETHOAM_RMT_LOOP NO_BD_SOFT PRBS_LSS
ETHOAM_RMT_SD NO_ELABEL REM_SD
ETHOAM_SELF_LOOP NULL_SEND REM_SF
ETHOAM_VCG_SELF_
LOOP ODU2_PM_AIS RS_CROSSTR
ETH_CFM_LOC ODU2_PM_BDI R_LOF
ETH_CFM_MACSTA-
TUS ODU2_PM_DEG R_LOS
ETH_CFM_MISMERGE ODU2_PM_LCK TD
ETH_CFM_RDI ODU2_PM_OCI TEMP_OVER
ETH_CFM_UNEXPERI ODU2_PM_SSF TEM_HA
ETH_SERVICE_CONFI
G_FAIL ODU2_PM_TIM TEM_LA
EX_ETHOAM_CC_LOS ODU2_TCMn_AIS TF
EX_ETHOAM_MPID_C
NFLCT ODU2_TCMn_BDI VLAN_SNCP_PS
FLOW_OVER ODU2_TCMn_DEG WAVEDATA_MIS

OptiX OSN 8800/6800/3800
FWD_PKT_LOSS ODU2_TCMn_LCK WRG_BD_TYPE
HARD_BAD ODU2_TCMn_LTC
2.2.42 LEX4 Board Alarm List

ALS_ACTIVE IN_PWR_HIGH ODU2_TCMn_SSF
B1_EXC IN_PWR_LOW ODU2_TCMn_TIM
B1_SD J0_MM OPA_FAIL_INDI
BD_LEDTEST LAG_PORT_FAIL OPU2_PLM
BD_STATUS LAG_VC_PORT_FAIL OTU2_AIS
LASER_MODULE_MIS-
BEFFEC_EXC MATCH OTU2_BDI
BUS_ERR LINK_ERR OTU2_DEG
CLIENT_PORT_PS LOOP_ALM OTU2_LOF
CLIENT_PORT_STA_I
NDI LPT_ACTIVE OTU2_LOM
CLIENT_PROT_NOT-
START LPT_RFI OTU2_SSF
COMMUN_FAIL LSR_COOL_ALM OTU2_TIM
DBPS_ABNORMAL LSR_INVALID OUT_PWR_HIGH
ETHOAM_DISCOVER_
ETHOAM_RMT_CRIT_
ETHOAM_VCG_SELF_
ETH_CFM_MACSTA-

OptiX OSN 8800/6800/3800
ETH_SERVICE_CONFI
EX_ETHOAM_MPID_C
HARD_ERR ODU2_TCMn_OCI
2.2.43 LOA Board Alarm List

ALS_ACTIVE ODU0_PM_TIM OPU0_PLM
B1_EXC ODU1_LOFLOM OPU1_CSF
B1_SD ODU1_PM_AIS OPU1_MSIM
BD_LEDTEST ODU1_PM_BDI OPU1_PLM
BD_STATUS ODU1_PM_DEG OPU2_CSF
BEFFEC_EXC ODU1_PM_LCK OPU2_MSIM
CLIENT_PORT_PS ODU1_PM_OCI OPU2_PLM
CLIENT_PORT_STA_I
NDI ODU1_PM_SSF OPUFLEX_CSF
CLIENT_PROT_NOT-
START ODU1_PM_TIM OPUFLEX_PLM
COMMUN_FAIL ODU1_TCMn_AIS OTU1_AIS
HARD_BAD ODU1_TCMn_BDI OTU1_BDI
HARD_ERR ODU1_TCMn_DEG OTU1_DEG
HARD_NONSUPPORT ODU1_TCMn_LCK OTU1_LOF
IN_PWR_HIGH ODU1_TCMn_LTC OTU1_LOM
IN_PWR_LOW ODU1_TCMn_OCI OTU1_SSF
J0_MM ODU1_TCMn_SSF OTU1_TIM

OptiX OSN 8800/6800/3800
LASER_MODULE_MIS
MATCH ODU1_TCMn_TIM OTU2_AIS
LINK_ERR ODU2_PM_AIS OTU2_BDI
LOOP_ALM ODU2_PM_BDI OTU2_DEG
LPT_ACTIVE ODU2_PM_DEG OTU2_LOF
LSR_COOL_ALM ODU2_PM_LCK OTU2_LOM
LSR_INVALID ODU2_PM_OCI OTU2_SSF
LSR_WILL_DIE ODU2_PM_SSF OTU2_TIM
L_SYNC ODU2_PM_TIM OUT_PWR_HIGH
NO_BD_SOFT ODU2_TCMn_AIS OUT_PWR_LOW
NO_ELABEL ODU2_TCMn_BDI PORT_MODULE_OFFLINE
NULL_SEND ODU2_TCMn_DEG PRBS_LSS
OCh_FDI ODU2_TCMn_LCK REM_SD
OCh_FDI_O ODU2_TCMn_LTC REM_SF
OCh_FDI_P ODU2_TCMn_OCI RS_CROSSTR
OCh_LOS_P ODU2_TCMn_SSF R_LOC
OCh_OCI ODU2_TCMn_TIM R_LOF
OCh_SSF ODUFLEX_LOFLOM R_LOS
OCh_SSF_O ODUFLEX_PM_AIS TD
OCh_SSF_P ODUFLEX_PM_BDI TEMP_OVER
ODU0_LOFLOM ODUFLEX_PM_DEG TEM_HA
ODU0_PM_AIS ODUFLEX_PM_LCK TEM_LA
ODU0_PM_BDI ODUFLEX_PM_OCI TF
ODU0_PM_DEG ODUFLEX_PM_SSF TS_CFG_MISMATCH
ODU0_PM_LCK ODUFLEX_PM_TIM WAVEDATA_MIS
ODU0_PM_OCI OPA_FAIL_INDI WRG_BD_TYPE
ODU0_PM_SSF OPU0_CSF
2.2.44 LOG Board Alarm List

TN12LOG

OptiX OSN 8800/6800/3800
ALS_ACTIVE ODU2_PM_OCI ODU2_TCM5_LCK
BD_LEDTEST ODU2_PM_SSF ODU2_TCM5_LTC
BD_STATUS ODU2_PM_TIM ODU2_TCM5_OCI
BEFFEC_EXC ODU2_TCM1_AIS ODU2_TCM5_SSF
BUS_ERR ODU2_TCM1_BDI ODU2_TCM5_TIM
CLIENT_PORT_PS ODU2_TCM1_DEG ODU2_TCM6_AIS
CLIENT_PORT_STA_INDI ODU2_TCM1_LCK ODU2_TCM6_BDI
CLIENT_PROT_NOTSTART ODU2_TCM1_LTC ODU2_TCM6_DEG
IN_PWR_HIGH ODU2_TCM2_AIS ODU2_TCM6_SSF
IN_PWR_LOW ODU2_TCM2_BDI ODU2_TCM6_TIM
LASER_MODULE_MIS- ODU2_TCM2_DEG OPA_FAIL_INDI

MATCH
LINK_ERR ODU2_TCM2_LCK OPU2_PLM
LOOP_ALM ODU2_TCM2_LTC OTU2_AIS
LPT_ACTIVE ODU2_TCM2_OCI OTU2_BDI
LSR_COOL_ALM 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_OFF-

LINE
NULL_SEND ODU2_TCM3_SSF PRBS_LSS
OCh_FDI ODU2_TCM3_TIM REM_SD
OCh_FDI_O ODU2_TCM4_AIS REM_SF
OCh_FDI_P ODU2_TCM4_BDI R_LOS

OptiX OSN 8800/6800/3800
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_LCK ODU2_TCM5_DEG WRG_BD_TYPE
TN11LOG
ALS_ACTIVE ODU2_PM_OCI ODU2_TCM5_LTC
BD_LEDTEST ODU2_PM_SSF ODU2_TCM5_OCI
BD_STATUS ODU2_PM_TIM ODU2_TCM5_SSF
BEFFEC_EXC ODU2_TCM1_AIS ODU2_TCM5_TIM
BUS_ERR ODU2_TCM1_BDI ODU2_TCM6_AIS
CLIENT_PORT_PS ODU2_TCM1_DEG ODU2_TCM6_BDI
CLIENT_PROT_NOTSTART ODU2_TCM1_LTC ODU2_TCM6_LCK
COMMUN_FAIL ODU2_TCM1_OCI ODU2_TCM6_LTC
HARD_BAD ODU2_TCM1_SSF ODU2_TCM6_OCI
HARD_ERR ODU2_TCM1_TIM ODU2_TCM6_SSF
IN_PWR_HIGH ODU2_TCM2_AIS ODU2_TCM6_TIM
IN_PWR_LOW ODU2_TCM2_BDI OPA_FAIL_INDI
LASER_MODULE_MIS- ODU2_TCM2_DEG OPU2_PLM

MATCH
LINK_ERR ODU2_TCM2_LCK OTU2_AIS
LOOP_ALM ODU2_TCM2_LTC OTU2_BDI
LPT_ACTIVE ODU2_TCM2_OCI OTU2_DEG
LSR_COOL_ALM ODU2_TCM2_SSF OTU2_LOF

OptiX OSN 8800/6800/3800
LSR_INVALID ODU2_TCM2_TIM OTU2_LOM
LSR_WILL_DIE ODU2_TCM3_AIS OTU2_SSF
L_SYNC ODU2_TCM3_BDI OTU2_TIM
MS_SNCP_PS ODU2_TCM3_DEG OUT_PWR_HIGH
MS_SNCP_STA_INDI ODU2_TCM3_LCK OUT_PWR_LOW
NO_BD_SOFT ODU2_TCM3_LTC PORT_MODULE_OFF-

LINE
NO_ELABEL ODU2_TCM3_OCI PRBS_LSS
NULL_SEND ODU2_TCM3_SSF REM_SD
OCh_FDI ODU2_TCM3_TIM REM_SF
OCh_FDI_O ODU2_TCM4_AIS R_LOS
OCh_FDI_P ODU2_TCM4_BDI SW_SNCP_PS
OCh_LOS_P ODU2_TCM4_DEG SW_SNCP_STA_INDI
OCh_OCI ODU2_TCM4_LCK TD
OCh_SSF ODU2_TCM4_LTC TEMP_OVER
OCh_SSF_O ODU2_TCM4_OCI TEM_HA
OCh_SSF_P ODU2_TCM4_SSF TEM_LA
ODU2_LOFLOM ODU2_TCM4_TIM TF
ODU2_PM_AIS ODU2_TCM5_AIS WAVEDATA_MIS
ODU2_PM_BDI ODU2_TCM5_BDI WRG_BD_TYPE
ODU2_PM_DEG ODU2_TCM5_DEG
ODU2_PM_LCK ODU2_TCM5_LCK
2.2.45 LOM Board Alarm List

ALS_ACTIVE ODU2_PM_SSF ODU2_TCM5_OCI
BD_LEDTEST ODU2_PM_TIM ODU2_TCM5_SSF
BD_STATUS ODU2_TCM1_AIS ODU2_TCM5_TIM
BEFFEC_EXC ODU2_TCM1_BDI ODU2_TCM6_AIS
CLIENT_PORT_PS ODU2_TCM1_DEG ODU2_TCM6_BDI

OptiX OSN 8800/6800/3800
CLIENT_PROT_NOTSTART ODU2_TCM1_LTC ODU2_TCM6_LCK
COMMUN_FAIL ODU2_TCM1_OCI ODU2_TCM6_LTC
FC_8B10BERR_OVER ODU2_TCM1_SSF ODU2_TCM6_OCI
FC_LINK_ERR ODU2_TCM1_TIM ODU2_TCM6_SSF
FC_SYNC_LOS ODU2_TCM2_AIS ODU2_TCM6_TIM
HARD_ERR ODU2_TCM2_DEG OPU2_MSIM
IN_PWR_HIGH ODU2_TCM2_LCK OPU2_PLM
IN_PWR_LOW ODU2_TCM2_LTC OTU2_AIS
LASER_MODULE_MIS- ODU2_TCM2_OCI OTU2_BDI

MATCH
LINK_ERR ODU2_TCM2_SSF OTU2_DEG
LOOP_ALM ODU2_TCM2_TIM OTU2_LOF
LPT_ACTIVE ODU2_TCM3_AIS OTU2_LOM
LSR_COOL_ALM ODU2_TCM3_BDI OTU2_SSF
LSR_INVALID ODU2_TCM3_DEG OTU2_TIM
LSR_WILL_DIE ODU2_TCM3_LCK OUT_PWR_HIGH
L_SYNC ODU2_TCM3_LTC OUT_PWR_LOW
NO_BD_SOFT ODU2_TCM3_OCI PORT_MODULE_OFF-

LINE
NO_ELABEL ODU2_TCM3_SSF PRBS_LSS
NULL_SEND ODU2_TCM3_TIM R_LOC
OCh_FDI ODU2_TCM4_AIS R_LOS
OCh_FDI_O ODU2_TCM4_BDI REM_SD
OCh_FDI_P ODU2_TCM4_DEG REM_SF
OCh_LOS_P ODU2_TCM4_LCK TD
OCh_OCI ODU2_TCM4_LTC TEMP_OVER
OCh_SSF ODU2_TCM4_OCI TEM_HA
OCh_SSF_O ODU2_TCM4_SSF TEM_LA
OCh_SSF_P ODU2_TCM4_TIM TF
ODU2_PM_AIS ODU2_TCM5_AIS TS_CFG_MISMATCH

OptiX OSN 8800/6800/3800
ODU2_PM_BDI ODU2_TCM5_BDI WAVEDATA_MIS
ODU2_PM_DEG ODU2_TCM5_DEG WRG_BD_TYPE
2.2.46 LQG Board Alarm List

ALS_ACTIVE ODU5G_PM_LCK ODU5G_TCM5_LCK
B1_EXC ODU5G_PM_OCI ODU5G_TCM5_LTC
B1_SD ODU5G_PM_SSF ODU5G_TCM5_OCI
BD_LEDTEST ODU5G_PM_TIM ODU5G_TCM5_SSF
BD_STATUS ODU5G_TCM1_AIS ODU5G_TCM5_TIM
BEFFEC_EXC ODU5G_TCM1_BDI ODU5G_TCM6_AIS
BUS_ERR ODU5G_TCM1_DEG ODU5G_TCM6_BDI
CLIENT_PORT_PS ODU5G_TCM1_EXC ODU5G_TCM6_DEG
CLIENT_PORT_STA_INDI ODU5G_TCM1_LCK ODU5G_TCM6_EXC
CLIENT_PROT_NOTSTART ODU5G_TCM1_LTC ODU5G_TCM6_LCK
COMMUN_FAIL ODU5G_TCM1_OCI ODU5G_TCM6_LTC
HARD_BAD ODU5G_TCM1_SSF ODU5G_TCM6_OCI
HARD_ERR ODU5G_TCM1_TIM ODU5G_TCM6_SSF
IN_PWR_HIGH ODU5G_TCM2_AIS ODU5G_TCM6_TIM
IN_PWR_LOW ODU5G_TCM2_BDI OPA_FAIL_INDI
J0_MM ODU5G_TCM2_DEG OPU5G_PLM
LASER_MODULE_MIS- ODU5G_TCM2_EXC OTU5G_AIS

MATCH
LINK_ERR ODU5G_TCM2_LCK OTU5G_BDI
LOOP_ALM ODU5G_TCM2_LTC OTU5G_DEG
LPT_ACTIVE ODU5G_TCM2_OCI OTU5G_EXC
LSR_COOL_ALM ODU5G_TCM2_SSF OTU5G_LOF
LSR_INVALID ODU5G_TCM2_TIM OTU5G_LOM
LSR_WILL_DIE ODU5G_TCM3_AIS OTU5G_SSF

OptiX OSN 8800/6800/3800
L_SYNC ODU5G_TCM3_BDI OTU5G_TIM
MS_AIS ODU5G_TCM3_DEG OUT_PWR_HIGH
MS_RDI ODU5G_TCM3_EXC OUT_PWR_LOW
MS_SNCP_PS ODU5G_TCM3_LCK PORT_MODULE_OFF-

LINE
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
2.2.47 LQMD Board Alarm List

TN12LQMD
ALS_ACTIVE ODU1_PM_LCK ODU1_TCM5_LTC

OptiX OSN 8800/6800/3800

MATCH
L_SYNC ODU1_TCM3_EXC PORT_MODULE_OFF-

LINE
MS_AIS ODU1_TCM3_LCK PRBS_LSS
NULL_SEND ODU1_TCM4_AIS R_LOF
OCh_FDI ODU1_TCM4_BDI R_LOS
OCh_FDI_O ODU1_TCM4_DEG SPEED_OVER

OptiX OSN 8800/6800/3800
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
TN11LQMD
ALS_ACTIVE ODU1_PM_LCK ODU1_TCM5_LTC

OptiX OSN 8800/6800/3800

MATCH
L_SYNC ODU1_TCM3_EXC PORT_MODULE_OFF-

LINE
MS_AIS ODU1_TCM3_LCK PRBS_LSS
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

OptiX OSN 8800/6800/3800
2.2.48 LQMS Board Alarm List

TN12LQMS
ALS_ACTIVE ODU1_PM_SSF ODU1_TCM5_SSF
B1_EXC ODU1_PM_TIM ODU1_TCM5_TIM
B1_SD ODU1_TCM1_AIS ODU1_TCM6_AIS
BD_LEDTEST ODU1_TCM1_BDI ODU1_TCM6_BDI
BD_STATUS ODU1_TCM1_DEG ODU1_TCM6_DEG
BEFFEC_EXC ODU1_TCM1_EXC ODU1_TCM6_EXC
BUS_ERR ODU1_TCM1_LCK ODU1_TCM6_LCK
CLIENT_PORT_PS ODU1_TCM1_LTC ODU1_TCM6_LTC
CLIENT_PORT_STA_INDI ODU1_TCM1_OCI ODU1_TCM6_OCI
CLIENT_PROT_NOTSTART ODU1_TCM1_SSF ODU1_TCM6_SSF
COMMUN_FAIL ODU1_TCM1_TIM ODU1_TCM6_TIM
HARD_BAD ODU1_TCM2_AIS ODU_SNCP_PS
HARD_ERR 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
LASER_MODULE_MIS- ODU1_TCM2_LTC OTU1_BDI

MATCH
LINK_ERR ODU1_TCM2_OCI OTU1_DEG
LOOP_ALM ODU1_TCM2_SSF OTU1_EXC
LPT_ACTIVE ODU1_TCM2_TIM OTU1_LOF
LSR_COOL_ALM 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_OFF-

LINE
MS_SNCP_STA_INDI ODU1_TCM3_OCI PRBS_LSS

OptiX OSN 8800/6800/3800
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
ODU1_PM_OCI ODU1_TCM5_OCI
TN11LQMS
ALS_ACTIVE ODU1_PM_OCI ODU1_TCM5_LTC
B1_EXC ODU1_PM_SSF ODU1_TCM5_OCI
B1_SD ODU1_PM_TIM ODU1_TCM5_SSF
BUS_ERR ODU1_TCM1_EXC ODU1_TCM6_DEG
CLIENT_PORT_PS ODU1_TCM1_LCK ODU1_TCM6_EXC
CLIENT_PORT_STA_INDI ODU1_TCM1_LTC ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_OCI ODU1_TCM6_LTC

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU1_TCM1_SSF ODU1_TCM6_OCI
HARD_BAD ODU1_TCM1_TIM ODU1_TCM6_SSF
HARD_ERR ODU1_TCM2_AIS ODU1_TCM6_TIM
IN_PWR_HIGH ODU1_TCM2_BDI OPA_FAIL_INDI
IN_PWR_LOW ODU1_TCM2_DEG OPU1_PLM
J0_MM ODU1_TCM2_EXC OTU1_AIS
LASER_MODULE_MIS- ODU1_TCM2_LCK OTU1_BDI

MATCH
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_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_OFF-

LINE
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

OptiX OSN 8800/6800/3800
ODU1_PM_AIS ODU1_TCM5_AIS TF
ODU1_PM_BDI ODU1_TCM5_BDI TS_CFG_MISMATCH
ODU1_PM_EXC ODU1_TCM5_EXC WRG_BD_TYPE
2.2.49 LQM Board Alarm List

ALS_ACTIVE NO_BD_SOFT OTU1_DEG
B1_EXC NO_ELABEL OTU1_EXC
B1_SD NULL_SEND OTU1_LOF
BD_LEDTEST OCh_FDI OTU1_LOM
BD_STATUS OCh_FDI_O OTU1_SSF
BEFFEC_EXC OCh_FDI_P OTU1_TIM
BUS_ERR OCh_LOS_P OUT_PWR_HIGH
CLIENT_PORT_PS OCh_OCI OUT_PWR_LOW
CLIENT_PORT_STA_INDI OCh_SSF PORT_MODULE_OFF-

LINE
CLIENT_PROT_NOTSTART OCh_SSF_O PRBS_LSS
COMMUN_FAIL OCh_SSF_P REM_SD
HARD_BAD ODU1_LOFLOM REM_SF
HARD_ERR ODU1_PM_AIS RS_CROSSTR
INTRA_OTU_PS ODU1_PM_LCK R_LOC
INTRA_OTU_STA_INDI ODU1_PM_OCI R_LOF
IN_PWR_HIGH ODU1_PM_SSF R_LOS
IN_PWR_LOW ODU1_PM_TIM SPEED_OVER
J0_MM ODU1_TCMn_AIS SW_SNCP_PS
LASER_MODULE_MIS- ODU1_TCMn_BDI SW_SNCP_STA_INDI

MATCH
LINK_ERR ODU1_TCMn_DEG TD
LOOP_ALM ODU1_TCMn_EXC TEMP_OVER

OptiX OSN 8800/6800/3800
LPT_ACTIVE ODU1_TCMn_LCK TEM_HA
LSR_INVALID ODU1_TCMn_LTC TEM_LA
LSR_WILL_DIE ODU1_TCMn_OCI TF
L_SYNC ODU1_TCMn_SSF TS_CFG_MISMATCH
ODU1_PM_BDI ODU1_TCMn_TIM WAVEDATA_MIS
ODU1_PM_DEG OPA_FAIL_INDI WRG_BD_TYPE
ODU1_PM_EXC OPU1_PLM
MS_SNCP_PS OTU1_AIS
MS_SNCP_STA_INDI OTU1_BDI
2.2.50 LSC Board Alarm List

TN12LSC
ALS_ACTIVE OCh_FDI_P OPA_FAIL_INDI
BD_LEDTEST OCh_LOS_P OPU4_PLM
BD_STATUS OCh_OCI OTU4_BDI
BEFFEC_EXC OCh_SSF OTU4_DEG
CLIENT_PORT_PS OCh_SSF_O OTU4_LOF
CLIENT_PORT_STA_I
NDI OCh_SSF_P OTU4_LOM
CLIENT_PROT_NOT-
START ODU4_PM_AIS OTU4_SSF
COMMUN_FAIL ODU4_PM_BDI OTU4_TIM
HARD_BAD ODU4_PM_DEG OUT_PWR_HIGH
HARD_ERR ODU4_PM_LCK OUT_PWR_LOW
IN_PWR_HIGH ODU4_PM_OCI PORT_MODULE_OFFLINE
IN_PWR_LOW ODU4_PM_SSF PRBS_LSS
LASER_MODULE_MIS
MATCH ODU4_PM_TIM REMOTE_FAULT
LOCAL_FAULT ODU4_TCMn_AIS RX_POWER_ABNORMAL
LOOP_ALM ODU4_TCMn_BDI R_LOS
LSR_WILL_DIE ODU4_TCMn_DEG REM_SF

OptiX OSN 8800/6800/3800
NO_BD_SOFT ODU4_TCMn_LCK TD
NO_ELABEL ODU4_TCMn_LTC TEMP_OVER
NULL_SEND ODU4_TCMn_OCI TF
OCh_FDI ODU4_TCMn_SSF WRG_BD_TYPE
OCh_FDI_O ODU4_TCMn_TIM
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.
2.2.51 LSQ Board Alarm List

ALS_ACTIVE ODU3_TCM1_DEG ODU3_TCM5_LTC
B1_EXC ODU3_TCM1_EXC ODU3_TCM5_OCI
B1_SD ODU3_TCM1_LCK ODU3_TCM5_SSF
BD_LEDTEST ODU3_TCM1_LTC ODU3_TCM5_TIM
BD_STATUS ODU3_TCM1_OCI ODU3_TCM6_AIS
BEFFEC_EXC ODU3_TCM1_SSF ODU3_TCM6_BDI
CLIENT_PORT_PS ODU3_TCM1_TIM ODU3_TCM6_DEG
CLIENT_PORT_STA_INDI ODU3_TCM2_AIS ODU3_TCM6_EXC
CLIENT_PROT_NOT- ODU3_TCM2_BDI ODU3_TCM6_LCK

START
COMMUN_FAIL ODU3_TCM2_DEG ODU3_TCM6_LTC
DCM_INSUFF ODU3_TCM2_EXC ODU3_TCM6_OCI
HARD_BAD ODU3_TCM2_LCK ODU3_TCM6_SSF
HARD_ERR ODU3_TCM2_LTC ODU3_TCM6_TIM
IN_PWR_HIGH ODU3_TCM2_OCI OPA_FAIL_INDI
IN_PWR_LOW ODU3_TCM2_SSF OPU3_MSIM
J0_MM ODU3_TCM2_TIM OPU3_PLM
LOOP_ALM ODU3_TCM3_AIS OTU3_AIS
LSR_WILL_DIE ODU3_TCM3_BDI OTU3_BDI
NO_BD_SOFT ODU3_TCM3_DEG OTU3_DEG

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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
2.2.52 LSXLR Board Alarm List

TN11LSXLR
BD_LEDTEST ODU3_TCM1_OCI ODU3_TCM5_OCI
BD_STATUS ODU3_TCM1_SSF ODU3_TCM5_SSF
BEFFEC_EXC ODU3_TCM1_TIM ODU3_TCM5_TIM
COMMUN_FAIL ODU3_TCM2_AIS ODU3_TCM6_AIS
DCM_INSUFF ODU3_TCM2_BDI ODU3_TCM6_BDI
HARD_BAD ODU3_TCM2_DEG ODU3_TCM6_DEG

OptiX OSN 8800/6800/3800
HARD_ERR ODU3_TCM2_LCK ODU3_TCM6_LCK
IN_PWR_HIGH ODU3_TCM2_LTC ODU3_TCM6_LTC
IN_PWR_LOW 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
ODU3_TCM1_DEG ODU3_TCM5_DEG WRG_BD_TYPE
ODU3_TCM1_LCK ODU3_TCM5_LCK
ODU3_TCM1_LTC ODU3_TCM5_LTC
TN12LSXLR
BD_LEDTEST ODU3_TCM1_LTC ODU3_TCM5_LTC
BD_STATUS ODU3_TCM1_OCI ODU3_TCM5_OCI

OptiX OSN 8800/6800/3800
BEFFEC_EXC ODU3_TCM1_SSF ODU3_TCM5_SSF
BUS_ERR ODU3_TCM1_TIM ODU3_TCM5_TIM
COMMUN_FAIL ODU3_TCM2_AIS ODU3_TCM6_AIS
DCM_INSUFF ODU3_TCM2_BDI ODU3_TCM6_BDI
HARD_BAD ODU3_TCM2_DEG ODU3_TCM6_DEG
HARD_ERR ODU3_TCM2_LCK ODU3_TCM6_LCK
IN_PWR_HIGH ODU3_TCM2_LTC ODU3_TCM6_LTC
IN_PWR_LOW 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
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

OptiX OSN 8800/6800/3800
2.2.53 LSXL Board Alarm List

TN11LSXL
B1_EXC OCh_OCI OTU3_DEG
B1_SD OCh_SSF OTU3_LOF
BD_LEDTEST OCh_SSF_O OTU3_LOM
BD_STATUS OCh_SSF_P OTU3_SSF
BEFFEC_EXC ODU3_PM_AIS OTU3_TIM
CLIENT_PORT_PS ODU3_PM_BDI OUT_PWR_HIGH
CLIENT_PORT_STA_INDI ODU3_PM_DEG OUT_PWR_LOW
CLIENT_PROT_NOT- ODU3_PM_LCK PORT_MODULE_OFF-

START LINE
COMMUN_FAIL ODU3_PM_OCI REM_SD
DCM_INSUFF ODU3_PM_SSF REM_SF
HARD_BAD ODU3_PM_TIM RS_CROSSTR
HARD_ERR ODU3_TCMn_AIS R_LOC
IN_PWR_HIGH ODU3_TCMn_BDI R_LOF
IN_PWR_LOW ODU3_TCMn_DEG R_LOS
J0_MM ODU3_TCMn_LCK TD
LOOP_ALM ODU3_TCMn_LTC TEMP_OVER
LSR_WILL_DIE ODU3_TCMn_OCI TEM_HA
NO_BD_SOFT ODU3_TCMn_SSF TEM_LA
NO_ELABEL ODU3_TCMn_TIM TF
OCh_FDI OPA_FAIL_INDI WAVEDATA_MIS
OCh_FDI_O OPU3_PLM WRG_BD_TYPE
OCh_FDI_P OTU3_AIS
OCh_LOS_P OTU3_BDI
TN12LSXL
ALS_ACTIVE OCh_FDI_O OPU3_MSIM
B1_EXC OCh_FDI_P OPU3_PLM

OptiX OSN 8800/6800/3800
B1_SD OCh_LOS_P OTU3_AIS
BD_LEDTEST OCh_OCI OTU3_BDI
BD_STATUS OCh_SSF OTU3_DEG
BEFFEC_EXC OCh_SSF_O OTU3_LOF
BUS_ERR OCh_SSF_P OTU3_LOM
CLIENT_PORT_PS ODU3_PM_AIS OTU3_SSF
CLIENT_PORT_STA_INDI ODU3_PM_BDI OTU3_TIM
CLIENT_PROT_NOT- ODU3_PM_DEG OUT_PWR_HIGH

START
COMMUN_FAIL ODU3_PM_LCK OUT_PWR_LOW
DCM_INSUFF ODU3_PM_OCI PORT_MODULE_OFF-

LINE
HARD_BAD ODU3_PM_SSF PRBS_LSS
HARD_ERR ODU3_PM_TIM REM_SD
IN_PWR_HIGH ODU3_TCMn_AIS REM_SF
IN_PWR_LOW ODU3_TCMn_BDI R_LOF
J0_MM ODU3_TCMn_DEG R_LOS
LOOP_ALM ODU3_TCMn_LCK R_OOF
LSR_WILL_DIE ODU3_TCMn_LTC TD
NO_BD_SOFT ODU3_TCMn_OCI TEMP_OVER
NO_ELABEL ODU3_TCMn_SSF TF
NULL_SEND ODU3_TCMn_TIM WAVEDATA_MIS
OCh_FDI OPA_FAIL_INDI WRG_BD_TYPE
TN15LSXL
ALS_ACTIVE OCh_FDI_P OPU3_PLM
B1_EXC OCh_LOS_P OTU3_AIS
B1_SD OCh_OCI OTU3_BDI
BD_LEDTEST OCh_SSF OTU3_DEG
BD_STATUS OCh_SSF_O OTU3_LOF
BEFFEC_EXC OCh_SSF_P OTU3_LOM

OptiX OSN 8800/6800/3800
CLIENT_PORT_PS ODU3_PM_AIS OTU3_SSF
CLIENT_PORT_STA_I
NDI ODU3_PM_BDI OTU3_TIM
CLIENT_PROT_NOT-
START ODU3_PM_DEG OUT_PWR_HIGH
COMMUN_FAIL ODU3_PM_LCK OUT_PWR_LOW
HARD_BAD ODU3_PM_OCI PORT_MODULE_OFFLINE
HARD_ERR ODU3_PM_SSF PRBS_LSS
IN_PWR_HIGH ODU3_PM_TIM RS_CROSSTR
IN_PWR_LOW ODU3_TCMn_AIS R_LOC
J0_MM ODU3_TCMn_BDI R_LOF
LOOP_ALM ODU3_TCMn_DEG R_LOS
LSR_WILL_DIE ODU3_TCMn_LCK REM_SD
NO_BD_SOFT ODU3_TCMn_LTC REM_SF
NO_ELABEL ODU3_TCMn_OCI TD
NULL_SEND ODU3_TCMn_SSF TEMP_OVER
OCh_FDI ODU3_TCMn_TIM TF
OCh_FDI_O OPA_FAIL_INDI WRG_BD_TYPE
NOTE
TCM6.
2.2.54 LSXR Board Alarm List

BD_LEDTEST ODU2_TCM1_OCI ODU2_TCM5_LTC
BD_STATUS ODU2_TCM1_SSF ODU2_TCM5_OCI
BEFFEC_EXC ODU2_TCM1_TIM ODU2_TCM5_SSF
HARD_BAD ODU2_TCM2_BDI ODU2_TCM6_AIS
HARD_ERR ODU2_TCM2_DEG ODU2_TCM6_BDI
IN_PWR_HIGH ODU2_TCM2_LCK ODU2_TCM6_DEG
IN_PWR_LOW ODU2_TCM2_LTC ODU2_TCM6_LCK

OptiX OSN 8800/6800/3800
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
ODU2_TCM1_LTC ODU2_TCM5_LCK WRG_BD_TYPE
2.2.55 LSX Board Alarm List

TN11LSX
ALS_ACTIVE ODU2_PM_TIM ODU2_TCM5_SSF
BD_LEDTEST ODU2_TCM1_DEG ODU2_TCM6_BDI

OptiX OSN 8800/6800/3800
BD_STATUS ODU2_TCM1_LCK ODU2_TCM6_DEG
BEFFEC_EXC ODU2_TCM1_LTC ODU2_TCM6_LCK

MATCH
LOCAL_FAULT ODU2_TCM2_TIM OTU2_LOM
LSR_COOL_ALM ODU2_TCM3_DEG OUT_PWR_HIGH
LSR_INVALID ODU2_TCM3_LCK OUT_PWR_LOW
LSR_WILL_DIE ODU2_TCM3_LTC PORT_MODULE_OFF-

LINE

OptiX OSN 8800/6800/3800
ODU2_PM_SSF ODU2_TCM5_OCI
TN12LSX
B1_EXC ODU2_PM_TIM ODU2_TCM5_SSF
B1_SD ODU2_TCM1_AIS ODU2_TCM5_TIM
BD_LEDTEST ODU2_TCM1_BDI ODU2_TCM6_AIS
CLIENT_PORT_PS ODU2_TCM1_LTC ODU2_TCM6_LCK
CLIENT_PORT_STA_INDI ODU2_TCM1_OCI ODU2_TCM6_LTC
CLIENT_PROT_NOTSTART ODU2_TCM1_SSF ODU2_TCM6_OCI
COMMUN_FAIL ODU2_TCM1_TIM ODU2_TCM6_SSF
HARD_BAD ODU2_TCM2_AIS ODU2_TCM6_TIM
HARD_ERR ODU2_TCM2_BDI OPA_FAIL_INDI
IN_PWR_LOW ODU2_TCM2_LCK OTU2_AIS
J0_MM ODU2_TCM2_LTC OTU2_BDI
LASER_MODULE_MIS- ODU2_TCM2_OCI OTU2_DEG

MATCH
LOCAL_FAULT ODU2_TCM2_SSF OTU2_LOF
LOOP_ALM ODU2_TCM2_TIM OTU2_LOM
LPT_ACTIVE ODU2_TCM3_AIS OTU2_SSF
LSR_COOL_ALM ODU2_TCM3_BDI OTU2_TIM
LSR_INVALID ODU2_TCM3_DEG OUT_PWR_HIGH

OptiX OSN 8800/6800/3800
LSR_WILL_DIE ODU2_TCM3_LCK OUT_PWR_LOW
L_SYNC ODU2_TCM3_LTC PORT_MODULE_OFF-

LINE
TN13LSX
B1_EXC ODU2_PM_TIM ODU2_TCM5_SSF
B1_SD ODU2_TCM1_AIS ODU2_TCM5_TIM
BD_LEDTEST ODU2_TCM1_BDI ODU2_TCM6_AIS
CLIENT_PORT_PS ODU2_TCM1_LTC ODU2_TCM6_LCK
CLIENT_PORT_STA_INDI ODU2_TCM1_OCI ODU2_TCM6_LTC
CLIENT_PROT_NOTSTART ODU2_TCM1_SSF ODU2_TCM6_OCI

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU2_TCM1_TIM ODU2_TCM6_SSF
HARD_BAD ODU2_TCM2_AIS ODU2_TCM6_TIM
IN_PWR_LOW ODU2_TCM2_LCK OTU2_AIS
J0_MM ODU2_TCM2_LTC OTU2_BDI
LASER_MODULE_MIS- ODU2_TCM2_OCI OTU2_DEG

MATCH
LOCAL_FAULT ODU2_TCM2_SSF OTU2_LOF
LOOP_ALM ODU2_TCM2_TIM OTU2_LOM
LPT_ACTIVE ODU2_TCM3_AIS OTU2_SSF
LSR_COOL_ALM ODU2_TCM3_BDI OTU2_TIM
LSR_WILL_DIE ODU2_TCM3_LCK OUT_PWR_LOW
L_SYNC ODU2_TCM3_LTC PORT_MODULE_OFF-

LINE

OptiX OSN 8800/6800/3800
NOTE
TCM6.
2.2.56 LTX Board Alarm List

TN11LTX
ALS_ACTIVE OCh_LOS_P ODU4_TCMn_TIM
B1_EXC OCh_OCI OPA_FAIL_INDI
B1_SD OCh_SSF OPU2_PLM
BD_LEDTEST OCh_SSF_O OPU4_PLM
BD_STATUS OCh_SSF_P OTU4_AIS
BEFFEC_EXC ODU2_LOFLOM OTU4_BDI
CLIENT_PORT_PS ODU2_PM_AIS OTU4_DEG
CLIENT_PORT_STA_I
NDI ODU2_PM_BDI OTU4_LOF
CLIENT_PROT_NOT-
START ODU2_PM_DEG OTU4_LOM
COMMUN_FAIL ODU2_PM_LCK OTU4_SSF
HARD_BAD ODU2_PM_OCI OTU4_TIM
HARD_ERR ODU2_PM_SSF OUT_PWR_HIGH
IN_PWR_HIGH ODU2_PM_TIM OUT_PWR_LOW
IN_PWR_LOW ODU4_PM_AIS PORT_MODULE_OFFLINE
J0_MM ODU4_PM_BDI PRBS_LSS
LASER_MODULE_MIS
MATCH ODU4_PM_DEG REMOTE_FAULT
LOCAL_FAULT ODU4_PM_LCK REM_SD
LOOP_ALM ODU4_PM_OCI REM_SF
LPT_ACTIVE ODU4_PM_SSF RS_CROSSTR
LSR_COOL_ALM ODU4_PM_TIM R_LOC
LSR_WILL_DIE ODU4_TCMn_AIS R_LOF

OptiX OSN 8800/6800/3800
NO_BD_SOFT ODU4_TCMn_BDI R_LOS
NO_ELABEL ODU4_TCMn_DEG TD
NULL_SEND ODU4_TCMn_LCK TEMP_OVER
OCh_FDI ODU4_TCMn_LTC TF
OCh_FDI_O ODU4_TCMn_OCI WRG_BD_TYPE
OCh_FDI_P ODU4_TCMn_SSF
NOTE
TCM6.
2.2.57 LWX2 Board Alarm List

ALS_ACTIVE LSR_COOL_ALM OUT_PWR_LOW
PORT_MODULE_OFF-
B1_EXC LSR_INVALID LINE
B1_SD LSR_WILL_DIE RS_CROSSTR
BD_LEDTEST MODULEFILE_UPDATE_ R_LOC

FAIL
BD_STATUS NO_BD_SOFT R_LOF
CLIENT_PORT_PS NO_ELABEL R_LOS
CLIENT_PORT_STA_INDI OCh_FDI SPEED_OVER
CLIENT_PROT_NOT- OCh_FDI_O TD
START
COMMUN_FAIL OCh_FDI_P TEMP_OVER
HARD_BAD OCh_LOS_P TEM_HA
HARD_ERR OCh_OCI TEM_LA
IN_PWR_HIGH OCh_SSF TF
IN_PWR_LOW OCh_SSF_O WAVEDATA_MIS
J0_MM OCh_SSF_P WRG_BD_TYPE
LASER_MODULE_MIS- OPA_FAIL_INDI
MATCH
LOOP_ALM OUT_PWR_HIGH

OptiX OSN 8800/6800/3800
2.2.58 LWXD Board Alarm List

ALS_ACTIVE MATCH
B1_EXC LOOP_ALM OUT_PWR_HIGH
B1_SD LSR_COOL_ALM OUT_PWR_LOW
BD_LEDTEST LSR_INVALID PORT_MODULE_OFF-

LINE
BD_STATUS LSR_WILL_DIE RS_CROSSTR
CLIENT_PORT_PS MODULEFILE_UPDATE_ R_LOC

FAIL
CLIENT_PORT_STA_INDI NO_BD_SOFT R_LOF
CLIENT_PROT_NOT- NO_ELABEL R_LOS

START
COMMUN_FAIL OCh_FDI SPEED_OVER
HARD_BAD OCh_FDI_O TD
HARD_ERR OCh_FDI_P TEMP_OVER
INTRA_OTU_PS OCh_LOS_P TEM_HA
INTRA_OTU_STA_INDI OCh_OCI TEM_LA
2.2.59 LWXS Board Alarm List

TN11LWXS
ALS_ACTIVE LSR_COOL_ALM OUT_PWR_LOW
PORT_MODULE_OFF-
B1_EXC LSR_INVALID LINE
B1_SD LSR_WILL_DIE RS_CROSSTR
BD_LEDTEST MODULEFILE_UPDATE_ R_LOC

FAIL
BD_STATUS NO_BD_SOFT R_LOF
CLIENT_PORT_PS NO_ELABEL R_LOS

OptiX OSN 8800/6800/3800
CLIENT_PORT_STA_INDI OCh_FDI SPEED_OVER
CLIENT_PROT_NOT- OCh_FDI_O TD
START
COMMUN_FAIL OCh_FDI_P TEMP_OVER
HARD_BAD OCh_LOS_P TEM_HA
HARD_ERR OCh_OCI TEM_LA
MATCH
LOOP_ALM OUT_PWR_HIGH
TN12LWXS
ALS_ACTIVE LOOP_ALM OUT_PWR_HIGH
B1_EXC LSR_COOL_ALM OUT_PWR_LOW
B1_SD LSR_WILL_DIE PORT_MODULE_OFF-

LINE
BD_LEDTEST MODULEFILE_UPDATE_ RS_CROSSTR

FAIL
BD_STATUS NO_BD_SOFT R_LOC
CLIENT_PORT_PS NO_ELABEL R_LOF
CLIENT_PORT_STA_INDI OCh_FDI R_LOS
CLIENT_PROT_NOT- OCh_FDI_O SPEED_OVER

START
COMMUN_FAIL OCh_FDI_P TD
HARD_BAD OCh_LOS_P TEMP_OVER
HARD_ERR OCh_OCI TEM_HA
IN_PWR_HIGH OCh_SSF TEM_LA
IN_PWR_LOW OCh_SSF_O TF
J0_MM OCh_SSF_P WAVEDATA_MIS

OptiX OSN 8800/6800/3800
LASER_MODULE_MIS- OPA_FAIL_INDI WRG_BD_TYPE

MATCH
2.2.60 M40V Board Alarm List

TN13M40V
BD_LEDTEST MODULE_TEMP_OVER TEMP_OVER
BD_STATUS MOD_COM_FAIL VOADATA_MIS
COMMUN_FAIL NO_BD_PARA WAVEDATA_MIS
HARD_BAD NO_BD_SOFT WRG_BD_TYPE
HARD_ERR NO_ELABEL
MODULEFILE_UPDAT
E_FAIL OPA_FAIL_INDI
TN12M40V
BD_STATUS MOD_COM_FAIL VOADATA_MIS
HARD_ERR NO_ELABEL
MODULEFILE_UPDAT
E_FAIL OPA_FAIL_INDI
TN11M40V
BD_STATUS MODULEFILE_UPDATE_F VOADATA_MIS

AIL
HARD_ERR NO_ELABEL
MOD_COM_FAIL OPA_FAIL_INDI

OptiX OSN 8800/6800/3800
2.2.61 M40 Board Alarm List

BD_LEDTEST MODULE_COOLCUR_OV OPA_FAIL_INDI
ER
BD_STATUS MODULE_TEMP_OVER TEMP_OVER
HARD_ERR NO_ELABEL
2.2.62 MCA4 Board Alarm List

APE_ADJUST_FAIL HARD_BAD PORTSWITCH_FAIL
APE_ADJUST_PEND HARD_ERR TEMP_OVER
BD_LEDTEST MODULEFILE_UPDATE_FAI WAVEDATA_MIS

L
BD_STATUS MOD_COM_FAIL WRG_BD_TYPE
CHAN_ADD NO_BD_PARA WAVE_ADD_ABN
CHAN_LOS NO_BD_SOFT WAVE_DROP_ABN
2.2.63 MCA8 Board Alarm List

APE_ADJUST_FAIL HARD_BAD PORTSWITCH_FAIL
APE_ADJUST_PEND HARD_ERR TEMP_OVER
BD_LEDTEST MODULEFILE_UPDATE_FAI WAVE_ADD_ABN

L
BD_STATUS MOD_COM_FAIL WAVE_DROP_ABN
CHAN_ADD NO_BD_PARA WAVEDATA_MIS
CHAN_LOS NO_BD_SOFT WRG_BD_TYPE

OptiX OSN 8800/6800/3800
2.2.64 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

OMS_BDI_P OMS_SSF_O
OMS_FDI OMS_SSF_P

OMS_BDI_P OMS_SSF_O
OMS_FDI OMS_SSF_P
2.2.67 MR8V Board Alarm List

BD_LEDTEST OMS_BDI_P OPA_FAIL_INDI
BD_STATUS OMS_FDI TEMP_OVER
COMMUN_FAIL OMS_FDI_O VOADATA_MIS
HARD_BAD OMS_FDI_P WAVEDATA_MIS
HARD_ERR OMS_SSF WRG_BD_TYPE

OptiX OSN 8800/6800/3800
OMS_BDI OMS_SSF_O
OMS_BDI_O OMS_SSF_P
2.2.68 ND2 Board Alarm List

TN53ND2
BD_LEDTEST ODU0_TCMn_LTC ODUFLEX_PM_AIS
BD_STATUS ODU0_TCMn_OCI ODUFLEX_PM_BDI
BEFFEC_EXC ODU0_TCMn_SSF ODUFLEX_PM_DEG
BUS_ERR ODU0_TCMn_TIM ODUFLEX_PM_LCK
COMMUN_FAIL ODU1_LOFLOM ODUFLEX_PM_OCI
HARD_BAD ODU1_PM_AIS ODUFLEX_PM_SSF
HARD_ERR ODU1_PM_BDI ODUFLEX_PM_TIM
IN_PWR_HIGH ODU1_PM_DEG ODUKSP_PS
IN_PWR_LOW ODU1_PM_LCK ODUKSP_STA_INDI
LASER_MODULE_MIS
MATCH ODU1_PM_OCI ODU_SNCP_PS
LOOP_ALM ODU1_PM_SSF ODU_SNCP_STA_INDI
LSR_COOL_ALM ODU1_PM_TIM OPA_FAIL_INDI
LSR_WILL_DIE ODU1_TCMn_AIS OPU1_MSIM
NO_BD_SOFT ODU1_TCMn_BDI OPU1_PLM
NO_ELABEL ODU1_TCMn_DEG OPU2_MSIM
NULL_SEND ODU1_TCMn_LCK OPU2_PLM
OCh_FDI ODU1_TCMn_LTC OTU2_AIS
OCh_FDI_O ODU1_TCMn_OCI OTU2_BDI
OCh_FDI_P ODU1_TCMn_SSF OTU2_DEG
OCh_LOS_P ODU1_TCMn_TIM OTU2_LOF
OCh_OCI ODU2_PM_AIS OTU2_LOM
OCh_SSF ODU2_PM_BDI OTU2_SSF
OCh_SSF_O ODU2_PM_DEG OTU2_TIM
OCh_SSF_P ODU2_PM_LCK OUT_PWR_HIGH

OptiX OSN 8800/6800/3800
ODU0_LOFLOM ODU2_PM_OCI OUT_PWR_LOW
ODU0_PM_AIS ODU2_PM_SSF PORT_MODULE_OFFLINE
ODU0_PM_BDI ODU2_PM_TIM PRBS_LSS
ODU0_PM_DEG ODU2_TCMn_AIS R_LOS
ODU0_PM_LCK ODU2_TCMn_BDI TD
ODU0_PM_OCI ODU2_TCMn_DEG TEMP_OVER
ODU0_PM_SSF ODU2_TCMn_LCK TEM_HA
ODU0_PM_TIM ODU2_TCMn_LTC TEM_LA
ODU0_TCMn_AIS ODU2_TCMn_OCI TF
ODU0_TCMn_BDI ODU2_TCMn_SSF WAVEDATA_MIS
ODU0_TCMn_DEG ODU2_TCMn_TIM WRG_BD_TYPE
ODU0_TCMn_LCK ODUFLEX_LOFLOM
TN53ND2
LASER_MODULE_MIS

OptiX OSN 8800/6800/3800
TN53ND2(COMP)
BD_LEDTEST ODU0_PM_TIM ODU2_TCMn_TIM
BD_STATUS ODU1_LOFLOM ODUKSP_PS
BEFFEC_EXC ODU1_PM_AIS ODUKSP_STA_INDI
BUS_ERR ODU1_PM_BDI ODU_SNCP_PS
COMMUN_FAIL ODU1_PM_DEG ODU_SNCP_STA_INDI
HARD_BAD ODU1_PM_LCK OPA_FAIL_INDI
HARD_ERR ODU1_PM_OCI OPU1_MSIM

OptiX OSN 8800/6800/3800
IN_PWR_HIGH ODU1_PM_SSF OPU1_PLM
IN_PWR_LOW ODU1_PM_TIM OPU2_MSIM
LASER_MODULE_MIS-
MATCH ODU1_TCMn_AIS OPU2_PLM
LOOP_ALM ODU1_TCMn_BDI OTU2_AIS
LSR_COOL_ALM ODU1_TCMn_DEG OTU2_BDI
LSR_WILL_DIE ODU1_TCMn_LCK OTU2_DEG
NO_BD_SOFT ODU1_TCMn_LTC OTU2_LOF
NO_ELABEL ODU1_TCMn_OCI OTU2_LOM
NULL_SEND ODU1_TCMn_SSF OTU2_SSF
OCh_FDI ODU1_TCMn_TIM OTU2_TIM
OCh_FDI_O ODU2_PM_AIS OUT_PWR_HIGH
OCh_FDI_P ODU2_PM_BDI OUT_PWR_LOW
PORT_MODULE_OFF-
OCh_LOS_P ODU2_PM_DEG LINE
OCh_OCI ODU2_PM_LCK PRBS_LSS
OCh_SSF ODU2_PM_OCI R_LOS
OCh_SSF_O ODU2_PM_SSF TD
OCh_SSF_P ODU2_PM_TIM TEMP_OVER
ODU0_LOFLOM ODU2_TCMn_AIS TEM_HA
ODU0_PM_AIS ODU2_TCMn_BDI TEM_LA
ODU0_PM_BDI ODU2_TCMn_DEG TF
ODU0_PM_DEG ODU2_TCMn_LCK WAVEDATA_MIS
ODU0_PM_LCK ODU2_TCMn_LTC WRG_BD_TYPE
ODU0_PM_OCI ODU2_TCMn_OCI
ODU0_PM_SSF ODU2_TCMn_SSF
TN52ND2
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM3_LTC
BD_STATUS ODU1_TCM3_LTC ODU2_TCM3_OCI
BEFFEC_EXC ODU1_TCM3_OCI ODU2_TCM3_SSF

OptiX OSN 8800/6800/3800
BUS_ERR ODU1_TCM3_SSF ODU2_TCM3_TIM
COMMUN_FAIL ODU1_TCM3_TIM ODU2_TCM4_AIS
HARD_BAD ODU1_TCM4_AIS ODU2_TCM4_BDI
HARD_ERR ODU1_TCM4_BDI ODU2_TCM4_DEG
IN_PWR_HIGH ODU1_TCM4_DEG ODU2_TCM4_LCK
IN_PWR_LOW ODU1_TCM4_LCK ODU2_TCM4_LTC
LOOP_ALM 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
ODU1_PM_BDI ODU2_PM_DEG OPA_FAIL_INDI

OptiX OSN 8800/6800/3800
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
TN12ND2
BD_LEDTEST ODU1_TCM3_TIM ODU2_TCM3_SSF
BD_STATUS ODU1_TCM4_AIS ODU2_TCM3_TIM
BEFFEC_EXC ODU1_TCM4_BDI ODU2_TCM4_AIS
BUS_ERR ODU1_TCM4_DEG ODU2_TCM4_BDI

OptiX OSN 8800/6800/3800
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
LASER_MODULE_MIS- ODU1_TCM5_AIS ODU2_TCM4_TIM

MATCH
LOOP_ALM 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

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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
TN11ND2
BUS_ERR ODU1_TCM4_LCK ODU2_TCM4_DEG
COMMUN_FAIL ODU1_TCM4_LTC ODU2_TCM4_LCK
HARD_BAD ODU1_TCM4_OCI ODU2_TCM4_LTC
HARD_ERR ODU1_TCM4_SSF ODU2_TCM4_OCI

OptiX OSN 8800/6800/3800
IN_PWR_HIGH ODU1_TCM4_TIM ODU2_TCM4_SSF
IN_PWR_LOW ODU1_TCM5_AIS ODU2_TCM4_TIM

OptiX OSN 8800/6800/3800
ODU1_TCM2_LTC ODU2_TCM2_LCK PORT_MODULE_OFFLINE
ODU1_TCM3_TIM ODU2_TCM3_SSF
NOTE
TCM6.
2.2.69 NO2 Board Alarm List

TN55NO2
BD_LEDTEST ODU0_PM_SSF ODU2_TCMn_LTC
BD_STATUS ODU0_PM_TIM ODU2_TCMn_OCI
BEFFEC_EXC ODU1_LOFLOM ODU2_TCMn_SSF
BUS_ERR ODU1_PM_AIS ODU2_TCMn_TIM
COMMUN_FAIL ODU1_PM_BDI ODU_SNCP_PS
HARD_BAD ODU1_PM_DEG ODU_SNCP_STA_INDI
HARD_ERR ODU1_PM_LCK OPU1_MSIM

OptiX OSN 8800/6800/3800
IN_PWR_HIGH ODU1_PM_OCI OPU1_PLM
IN_PWR_LOW ODU1_PM_SSF OPU2_MSIM
LASER_MODULE_MIS
MATCH ODU1_PM_TIM OPU2_PLM
LOOP_ALM ODU1_TCMn_AIS OTU2_AIS
LSR_WILL_DIE ODU1_TCMn_BDI OTU2_BDI
NO_BD_SOFT ODU1_TCMn_DEG OTU2_DEG
NO_ELABEL ODU1_TCMn_LCK OTU2_LOF
NULL_SEND ODU1_TCMn_LTC OTU2_LOM
OCh_FDI ODU1_TCMn_OCI OTU2_SSF
OCh_FDI_O ODU1_TCMn_SSF OTU2_TIM
OCh_FDI_P ODU1_TCMn_TIM OUT_PWR_HIGH
OCh_LOS_P ODU2_PM_AIS OUT_PWR_LOW
OCh_OCI ODU2_PM_BDI PORT_MODULE_OFFLINE
OCh_SSF ODU2_PM_DEG PRBS_LSS
OCh_SSF_O ODU2_PM_LCK R_LOS
OCh_SSF_P ODU2_PM_OCI TD
ODU0_LOFLOM ODU2_PM_SSF TEMP_OVER
ODU0_PM_AIS ODU2_PM_TIM TF
ODU0_PM_BDI ODU2_TCMn_AIS WAVEDATA_MIS
ODU0_PM_DEG ODU2_TCMn_BDI WRG_BD_TYPE
ODU0_PM_LCK ODU2_TCMn_DEG
ODU0_PM_OCI ODU2_TCMn_LCK
TN55NO2(REG)
BD_LEDTEST OCh_SSF_O OPU2_PLM
BD_STATUS OCh_SSF_P OTU2_AIS
BEFFEC_EXC ODU2_PM_AIS OTU2_BDI
COMMUN_FAIL ODU2_PM_BDI OTU2_DEG
HARD_BAD ODU2_PM_DEG OTU2_LOF

OptiX OSN 8800/6800/3800
HARD_ERR ODU2_PM_LCK OTU2_LOM
IN_PWR_HIGH ODU2_PM_OCI OTU2_SSF
IN_PWR_LOW ODU2_PM_SSF OTU2_TIM
LASER_MODULE_MIS
MATCH ODU2_PM_TIM OUT_PWR_HIGH
LSR_WILL_DIE ODU2_TCMn_AIS OUT_PWR_LOW
NO_BD_SOFT ODU2_TCMn_BDI PORT_MODULE_OFFLINE
NO_ELABEL ODU2_TCMn_DEG R_LOS
OCh_FDI ODU2_TCMn_LCK TD
OCh_FDI_O ODU2_TCMn_LTC TEMP_OVER
OCh_FDI_P ODU2_TCMn_OCI TF
OCh_LOS_P ODU2_TCMn_SSF WAVEDATA_MIS
OCh_OCI ODU2_TCMn_TIM WRG_BD_TYPE
OCh_SSF OPU2_MSIM
NOTE
TCM6.
2.2.70 NPO2 Board Alarm List

TN55NPO2(STND)
BD_LEDTEST ODU1_PM_BDI ODUKSP_PS
BD_STATUS ODU1_PM_DEG ODUKSP_STA_INDI
BEFFEC_EXC ODU1_PM_LCK ODU_SNCP_PS
BUS_ERR ODU1_PM_OCI ODU_SNCP_STA_INDI
COMMUN_FAIL ODU1_PM_SSF OPA_FAIL_INDI
EXT_MODULE_OFFLINE ODU1_PM_TIM OPU1_MSIM
HARD_BAD ODU1_TCMn_AIS OPU1_PLM
HARD_ERR ODU1_TCMn_BDI OPU2_MSIM
IN_PWR_HIGH ODU1_TCMn_DEG OPU2_PLM
IN_PWR_LOW ODU1_TCMn_LCK OTU2_AIS
IPA_SHUT ODU1_TCMn_LTC OTU2_BDI

OptiX OSN 8800/6800/3800
LOOP_ALM ODU1_TCMn_OCI OTU2_DEG
LSR_WILL_DIE ODU1_TCMn_SSF OTU2_LOF
MAINBD_SUBBD_MIS-
MATCH 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
BD_LEDTEST ODU1_LOFLOM OMS_BDI
BD_STATUS ODU1_PM_AIS OMS_BDI_O
BEFFEC_EXC ODU1_PM_BDI OMS_BDI_P
BUS_ERR ODU1_PM_DEG OMS_FDI
COMMUN_FAIL ODU1_PM_LCK OMS_FDI_O
EXT_MODULE_OFF-
LINE ODU1_PM_OCI OMS_FDI_P
HARD_BAD ODU1_PM_SSF OMS_LOS_P
HARD_ERR ODU1_PM_TIM OMS_SSF
IN_PWR_HIGH ODU1_TCMn_AIS OMS_SSF_O

OptiX OSN 8800/6800/3800
IN_PWR_LOW ODU1_TCMn_BDI OMS_SSF_P
IPA_SHUT ODU1_TCMn_DEG OPA_FAIL_INDI
LOOP_ALM ODU1_TCMn_LCK OPU1_MSIM
LSR_WILL_DIE ODU1_TCMn_LTC OPU1_PLM
MAINBD_SUBBD_MIS-
MATCH 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
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
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM4_BDI

OptiX OSN 8800/6800/3800
BD_STATUS ODU1_TCM3_LTC ODU2_TCM4_DEG
BEFFEC_EXC ODU1_TCM3_OCI ODU2_TCM4_LCK
BUS_ERR ODU1_TCM3_SSF ODU2_TCM4_LTC
IN_PWR_HIGH ODU1_TCM4_DEG ODU2_TCM5_AIS
IN_PWR_LOW ODU1_TCM4_LCK ODU2_TCM5_BDI
LASER_MODULE_MIS- ODU1_TCM4_LTC ODU2_TCM5_DEG

MATCH
LOOP_ALM ODU1_TCM4_OCI ODU2_TCM5_LCK
LSR_WILL_DIE ODU1_TCM4_SSF ODU2_TCM5_LTC
MAINBD_SUBBD_MIS- ODU1_TCM4_TIM ODU2_TCM5_OCI

MATCH
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
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

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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

OptiX OSN 8800/6800/3800
ODU1_TCM3_DEG ODU2_TCM4_AIS WRG_BD_TYPE
2.2.71 NPO2E Board Alarm List

TN55NPO2E
BD_LEDTEST ODU1_PM_BDI ODUKSP_PS
BD_STATUS ODU1_PM_DEG ODUKSP_STA_INDI
BEFFEC_EXC ODU1_PM_LCK ODU_SNCP_PS
BUS_ERR ODU1_PM_OCI ODU_SNCP_STA_INDI
COMMUN_FAIL ODU1_PM_SSF OPA_FAIL_INDI
EXT_MODULE_OFFLINE ODU1_PM_TIM OPU1_MSIM
HARD_BAD ODU1_TCMn_AIS OPU1_PLM
HARD_ERR ODU1_TCMn_BDI OPU2_MSIM
IN_PWR_HIGH ODU1_TCMn_DEG OPU2_PLM
IN_PWR_LOW ODU1_TCMn_LCK OTU2_AIS
IPA_SHUT ODU1_TCMn_LTC OTU2_BDI
LOOP_ALM ODU1_TCMn_OCI OTU2_DEG
LSR_WILL_DIE ODU1_TCMn_SSF OTU2_LOF
MAINBD_SUBBD_MIS-
MATCH 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

OptiX OSN 8800/6800/3800
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.72 NQ2 Board Alarm List

TN53NQ2
LASER_MODULE_MIS
LSR_WILL_DIE ODU1_PM_TIM OPA_FAIL_INDI
LSR_COOL_ALM ODU1_TCMn_AIS OPU1_MSIM

OptiX OSN 8800/6800/3800
TN53NQ2(COMP)
BD_STATUS ODU0_PM_TIM ODU2_TCMn_SSF
BEFFEC_EXC ODU1_LOFLOM ODU2_TCMn_TIM
BUS_ERR ODU1_PM_AIS ODUKSP_PS
COMMUN_FAIL ODU1_PM_BDI ODUKSP_STA_INDI
HARD_BAD ODU1_PM_DEG ODU_SNCP_PS
HARD_ERR ODU1_PM_LCK ODU_SNCP_STA_INDI
IN_PWR_HIGH ODU1_PM_OCI OPA_FAIL_INDI
LASER_MODULE_MIS-
LOOP_ALM ODU1_TCMn_AIS OPU2_MSIM
LSR_COOL_ALM ODU1_TCMn_BDI OPU2_PLM
LSR_WILL_DIE ODU1_TCMn_DEG OTU2_AIS
NO_BD_SOFT ODU1_TCMn_LCK OTU2_BDI

OptiX OSN 8800/6800/3800
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
PORT_MODULE_OFF-
OCh_SSF ODU2_PM_LCK LINE
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
TN54NQ2
BD_LEDTEST ODU1_TCM3_DEG ODU2_TCM3_LTC
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
LASER_MODULE_MIS- ODU1_TCM4_LCK ODU2_TCM4_OCI

MATCH

OptiX OSN 8800/6800/3800
LOOP_ALM 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
ODU1_PM_TIM ODU2_TCM1_BDI OTU2_BDI
ODU1_TCM1_AIS ODU2_TCM1_DEG OTU2_DEG

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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
TN52NQ2
BD_LEDTEST ODU1_TCM3_DEG ODU2_TCM3_LTC
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
LASER_MODULE_MIS- ODU1_TCM4_LCK ODU2_TCM4_OCI

MATCH

OptiX OSN 8800/6800/3800

OptiX OSN 8800/6800/3800
ODU1_TCM1_TIM ODU2_TCM2_BDI PORT_MODULE_OFF-

LINE
TN51NQ2
BD_LEDTEST ODU1_TCM3_SSF ODU2_TCM3_OCI
BD_STATUS ODU1_TCM3_TIM ODU2_TCM3_SSF
BEFFEC_EXC ODU1_TCM4_AIS ODU2_TCM3_TIM
BUS_ERR ODU1_TCM4_BDI ODU2_TCM4_AIS
COMMUN_FAIL ODU1_TCM4_DEG ODU2_TCM4_BDI
HARD_BAD ODU1_TCM4_LCK ODU2_TCM4_DEG
HARD_ERR ODU1_TCM4_LTC ODU2_TCM4_LCK
IN_PWR_HIGH ODU1_TCM4_OCI ODU2_TCM4_LTC
IN_PWR_LOW ODU1_TCM4_SSF ODU2_TCM4_OCI
LASER_MODULE_MIS- ODU1_TCM4_TIM ODU2_TCM4_SSF

MATCH

OptiX OSN 8800/6800/3800
LOOP_ALM ODU1_TCM5_AIS ODU2_TCM4_TIM
LSR_COOL_ALM ODU1_TCM5_BDI ODU2_TCM5_AIS
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
ODU1_TCM1_SSF ODU2_TCM1_OCI OTU2_LOM
ODU1_TCM1_TIM ODU2_TCM1_SSF OTU2_SSF

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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.73 NS2 Board Alarm List

TN53NS2
LASER_MODULE_MIS

OptiX OSN 8800/6800/3800
ODU0_TCMn_LTC ODUFLEX_PM_AIS
TN53NS2(COMP)
BD_STATUS ODU0_PM_TIM ODU2_TCMn_SSF
BEFFEC_EXC ODU1_LOFLOM ODU2_TCMn_TIM
BUS_ERR ODU1_PM_AIS ODUKSP_PS

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU1_PM_BDI ODUKSP_STA_INDI
HARD_BAD ODU1_PM_DEG ODU_SNCP_PS
HARD_ERR ODU1_PM_LCK ODU_SNCP_STA_INDI
IN_PWR_HIGH ODU1_PM_OCI OPA_FAIL_INDI
LASER_MODULE_MIS-
LOOP_ALM ODU1_TCMn_AIS OPU2_MSIM
LSR_COOL_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
PORT_MODULE_OFF-
OCh_SSF ODU2_PM_LCK LINE
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
TN52NS2

OptiX OSN 8800/6800/3800
BD_LEDTEST ODU1_TCM3_LCK ODU2_TCM3_OCI
BD_STATUS ODU1_TCM3_LTC ODU2_TCM3_SSF
BEFFEC_EXC ODU1_TCM3_OCI ODU2_TCM3_TIM
BUS_ERR ODU1_TCM3_SSF ODU2_TCM4_AIS
COMMUN_FAIL ODU1_TCM3_TIM ODU2_TCM4_BDI
HARD_BAD ODU1_TCM4_AIS ODU2_TCM4_DEG
HARD_ERR ODU1_TCM4_BDI ODU2_TCM4_LCK
IN_PWR_HIGH ODU1_TCM4_DEG ODU2_TCM4_LTC
IN_PWR_LOW ODU1_TCM4_LCK ODU2_TCM4_OCI

OptiX OSN 8800/6800/3800
ODU1_TCM1_TIM ODU2_TCM2_BDI PORT_MODULE_OFFLINE
ODU1_TCM3_DEG ODU2_TCM3_LTC
TN12NS2

OptiX OSN 8800/6800/3800
BUS_ERR ODU1_TCM4_LCK ODU2_TCM4_DEG
COMMUN_FAIL ODU1_TCM4_LTC ODU2_TCM4_LCK
HARD_BAD ODU1_TCM4_OCI ODU2_TCM4_LTC
HARD_ERR ODU1_TCM4_SSF ODU2_TCM4_OCI
IN_PWR_HIGH ODU1_TCM4_TIM ODU2_TCM4_SSF
IN_PWR_LOW ODU1_TCM5_AIS ODU2_TCM4_TIM

OptiX OSN 8800/6800/3800
ODU1_TCM2_LTC ODU2_TCM2_LCK PORT_MODULE_OFFLINE
ODU1_TCM3_TIM ODU2_TCM3_SSF
TN11NS2
BD_LEDTEST ODU1_TCM4_AIS ODU2_TCM3_SSF
BD_STATUS ODU1_TCM4_BDI ODU2_TCM3_TIM
BEFFEC_EXC ODU1_TCM4_DEG ODU2_TCM4_AIS
BUS_ERR ODU1_TCM4_LCK ODU2_TCM4_BDI
COMMUN_FAIL ODU1_TCM4_LTC ODU2_TCM4_DEG

OptiX OSN 8800/6800/3800
HARD_BAD ODU1_TCM4_OCI ODU2_TCM4_LCK
HARD_ERR ODU1_TCM4_SSF ODU2_TCM4_LTC
IN_PWR_HIGH ODU1_TCM4_TIM ODU2_TCM4_OCI
IN_PWR_LOW ODU1_TCM5_AIS ODU2_TCM4_SSF
LOOP_ALM 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

OptiX OSN 8800/6800/3800
ODU1_TCM1_OCI ODU2_TCM1_LCK OTU2_BDI
ODU1_TCM1_SSF ODU2_TCM1_LTC OTU2_DEG
ODU1_TCM1_TIM ODU2_TCM1_OCI OTU2_LOF
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

TN55NS3
BD_LEDTEST ODU1_PM_LCK ODU3_PM_TIM
BD_STATUS ODU1_PM_OCI ODU3_TCMn_AIS
BEFFEC_EXC ODU1_PM_SSF ODU3_TCMn_BDI
BUS_ERR ODU1_PM_TIM ODU3_TCMn_DEG
COMMUN_FAIL ODU1_TCMn_AIS ODU3_TCMn_LCK
HARD_BAD ODU1_TCMn_BDI ODU3_TCMn_LTC
HARD_ERR ODU1_TCMn_DEG ODU3_TCMn_OCI
IN_PWR_HIGH ODU1_TCMn_LCK ODU3_TCMn_SSF

OptiX OSN 8800/6800/3800
IN_PWR_LOW ODU1_TCMn_LTC ODU3_TCMn_TIM
LOOP_ALM ODU1_TCMn_OCI ODUKSP_PS
LSR_WILL_DIE ODU1_TCMn_SSF ODUKSP_STA_INDI
NO_BD_SOFT ODU1_TCMn_TIM ODU_SNCP_PS
NO_ELABEL ODU2_LOFLOM ODU_SNCP_STA_INDI
NULL_SEND ODU2_PM_AIS OPA_FAIL_INDI
OCh_FDI ODU2_PM_BDI OPU1_MSIM
OCh_FDI_O ODU2_PM_DEG OPU1_PLM
OCh_FDI_P ODU2_PM_LCK OPU3_MSIM
OCh_LOS_P ODU2_PM_OCI OPU3_PLM
OCh_OCI ODU2_PM_SSF OTU3_AIS
OCh_SSF ODU2_PM_TIM OTU3_BDI
OCh_SSF_O ODU2_TCMn_AIS OTU3_DEG
OCh_SSF_P ODU2_TCMn_BDI OTU3_LOF
ODU0_LOFLOM ODU2_TCMn_DEG OTU3_LOM
ODU0_PM_AIS ODU2_TCMn_LCK OTU3_SSF
ODU0_PM_BDI ODU2_TCMn_LTC OTU3_TIM
ODU0_PM_DEG ODU2_TCMn_OCI OUT_PWR_HIGH
ODU0_PM_LCK ODU2_TCMn_SSF OUT_PWR_LOW
ODU0_PM_OCI ODU2_TCMn_TIM PORT_MODULE_OFFLINE
ODU0_PM_SSF ODU3_PM_AIS PRBS_LSS
ODU0_PM_TIM ODU3_PM_BDI R_LOS
ODU1_LOFLOM ODU3_PM_DEG TD
ODU1_PM_AIS ODU3_PM_LCK TEMP_OVER
ODU1_PM_BDI ODU3_PM_OCI TF
ODU1_PM_DEG ODU3_PM_SSF WRG_BD_TYPE
TN54NS3/TN54NS3(STND)
BD_LEDTEST ODU1_PM_LCK ODU3_TCMn_AIS
BD_STATUS ODU1_PM_OCI ODU3_TCMn_BDI

OptiX OSN 8800/6800/3800
BEFFEC_EXC ODU1_PM_SSF ODU3_TCMn_DEG
BUS_ERR ODU1_PM_TIM ODU3_TCMn_EXC
COMMUN_FAIL ODU1_TCMn_AIS ODU3_TCMn_LCK
DCM_INSUFF ODU1_TCMn_BDI ODU3_TCMn_LTC
HARD_BAD ODU1_TCMn_DEG ODU3_TCMn_OCI
HARD_ERR ODU1_TCMn_EXC ODU3_TCMn_SSF
IN_PWR_HIGH ODU1_TCMn_LCK ODU3_TCMn_TIM
IN_PWR_LOW ODU1_TCMn_LTC ODUKSP_PS
LASER_MODULE_MIS
MATCH ODU1_TCMn_OCI ODUKSP_STA_INDI
LOOP_ALM ODU1_TCMn_SSF ODU_SNCP_PS
LSR_WILL_DIE ODU1_TCMn_TIM ODU_SNCP_STA_INDI
MODULE_RATE_MIS-
MATCH ODU2_LOFLOM OPA_FAIL_INDI
NO_BD_SOFT ODU2_PM_AIS OPU1_MSIM
NO_ELABEL ODU2_PM_BDI OPU1_PLM
NULL_SEND ODU2_PM_DEG OPU3_MSIM
OCh_FDI ODU2_PM_EXC OPU3_PLM
OCh_FDI_O ODU2_PM_LCK OTU3_AIS
OCh_FDI_P ODU2_PM_OCI OTU3_BDI
OCh_LOS_P ODU2_PM_SSF OTU3_DEG
OCh_OCI ODU2_PM_TIM OTU3_EXC
OCh_SSF ODU2_TCMn_AIS OTU3_LOF
OCh_SSF_O ODU2_TCMn_BDI OTU3_LOM
OCh_SSF_P ODU2_TCMn_DEG OTU3_SSF
ODU0_LOFLOM ODU2_TCMn_EXC OTU3_TIM
ODU0_PM_AIS ODU2_TCMn_LCK OUT_PWR_HIGH
ODU0_PM_BDI ODU2_TCMn_LTC OUT_PWR_LOW
ODU0_PM_DEG ODU2_TCMn_OCI PORT_MODULE_OFFLINE
ODU0_PM_EXC ODU2_TCMn_SSF PRBS_LSS
ODU0_PM_LCK ODU2_TCMn_TIM R_LOS

OptiX OSN 8800/6800/3800
ODU0_PM_OCI ODU3_PM_AIS TD
ODU0_PM_SSF ODU3_PM_BDI TEMP_OVER
ODU0_PM_TIM ODU3_PM_DEG TEM_HA
ODU1_LOFLOM ODU3_PM_EXC TEM_LA
ODU1_PM_AIS ODU3_PM_LCK TF
ODU1_PM_BDI ODU3_PM_OCI WAVEDATA_MIS
ODU1_PM_DEG ODU3_PM_SSF WRG_BD_TYPE
ODU1_PM_EXC ODU3_PM_TIM
TN52NS3
BD_LEDTEST ODU1_TCM5_SSF ODU3_TCM1_LCK
BD_STATUS ODU1_TCM5_TIM ODU3_TCM1_LTC
BEFFEC_EXC ODU1_TCM6_AIS ODU3_TCM1_OCI
BUS_ERR ODU1_TCM6_BDI ODU3_TCM1_SSF
COMMUN_FAIL ODU1_TCM6_DEG ODU3_TCM1_TIM
DCM_INSUFF ODU1_TCM6_LCK ODU3_TCM2_AIS
HARD_BAD ODU1_TCM6_LTC ODU3_TCM2_BDI
HARD_ERR ODU1_TCM6_OCI ODU3_TCM2_DEG
IN_PWR_HIGH ODU1_TCM6_SSF ODU3_TCM2_LCK
IN_PWR_LOW ODU1_TCM6_TIM ODU3_TCM2_LTC
LOOP_ALM 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
OCh_LOS_P ODU2_TCM1_AIS ODU3_TCM3_OCI
OCh_OCI ODU2_TCM1_BDI ODU3_TCM3_SSF

OptiX OSN 8800/6800/3800
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
ODU1_TCM2_DEG ODU2_TCM4_TIM OPA_FAIL_INDI

OptiX OSN 8800/6800/3800
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
BD_LEDTEST ODU3_PM_TIM ODU3_TCM5_LCK

OptiX OSN 8800/6800/3800
BD_STATUS ODU3_TCM1_AIS ODU3_TCM5_LTC
BEFFEC_EXC ODU3_TCM1_BDI ODU3_TCM5_OCI
BUS_ERR ODU3_TCM1_DEG ODU3_TCM5_SSF
COMMUN_FAIL ODU3_TCM1_LCK ODU3_TCM5_TIM
DCM_INSUFF ODU3_TCM1_LTC ODU3_TCM6_AIS
HARD_BAD ODU3_TCM1_OCI ODU3_TCM6_BDI
HARD_ERR ODU3_TCM1_SSF ODU3_TCM6_DEG
IN_PWR_HIGH ODU3_TCM1_TIM ODU3_TCM6_LCK
IN_PWR_LOW ODU3_TCM2_AIS ODU3_TCM6_LTC
LOOP_ALM 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

OptiX OSN 8800/6800/3800
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.

TN54NS4
BD_LEDTEST ODU1_PM_SSF ODU4_PM_DEG
BD_STATUS ODU1_PM_TIM ODU4_PM_LCK
BEFFEC_EXC ODU1_TCMn_AIS ODU4_PM_OCI
BUS_ERR ODU1_TCMn_BDI ODU4_PM_SSF
COMMUN_FAIL ODU1_TCMn_DEG ODU4_PM_TIM
HARD_BAD ODU1_TCMn_LCK ODU4_TCMn_AIS
HARD_ERR ODU1_TCMn_LTC ODU4_TCMn_BDI
IN_PWR_HIGH ODU1_TCMn_OCI ODU4_TCMn_DEG
IN_PWR_LOW ODU1_TCMn_SSF ODU4_TCMn_LCK
LOOP_ALM ODU1_TCMn_TIM ODU4_TCMn_LTC
LSR_WILL_DIE ODU2_LOFLOM ODU4_TCMn_OCI
NO_BD_SOFT ODU2_PM_AIS ODU4_TCMn_SSF
NO_ELABEL ODU2_PM_BDI ODU4_TCMn_TIM
NULL_SEND ODU2_PM_DEG ODUFLEX_LOFLOM
OCh_FDI ODU2_PM_LCK ODUFLEX_PM_AIS
OCh_FDI_O ODU2_PM_OCI ODUFLEX_PM_BDI
OCh_FDI_P ODU2_PM_SSF ODUFLEX_PM_DEG
OCh_LOS_P ODU2_PM_TIM ODUFLEX_PM_LCK
OCh_OCI ODU2_TCMn_AIS ODUFLEX_PM_OCI

OptiX OSN 8800/6800/3800
OCh_SSF ODU2_TCMn_BDI ODUFLEX_PM_SSF
OCh_SSF_O ODU2_TCMn_DEG ODUFLEX_PM_TIM
OCh_SSF_P ODU2_TCMn_LCK ODUKSP_PS
ODU0_LOFLOM ODU2_TCMn_LTC ODUKSP_STA_INDI
ODU0_PM_AIS ODU2_TCMn_OCI ODU_SNCP_PS
ODU0_PM_BDI ODU2_TCMn_SSF ODU_SNCP_STA_INDI
ODU0_PM_DEG ODU2_TCMn_TIM OPA_FAIL_INDI
ODU0_PM_LCK ODU3_LOFLOM OPU4_PLM
ODU0_PM_OCI ODU3_PM_AIS OTU4_AIS
ODU0_PM_SSF ODU3_PM_BDI OTU4_BDI
ODU0_PM_TIM ODU3_PM_DEG OTU4_DEG
ODU0_TCMn_AIS ODU3_PM_LCK OTU4_LOF
ODU0_TCMn_BDI ODU3_PM_OCI OTU4_LOM
ODU0_TCMn_DEG ODU3_PM_SSF OTU4_SSF
ODU0_TCMn_LCK ODU3_PM_TIM OTU4_TIM
ODU0_TCMn_LTC ODU3_TCMn_AIS OUT_PWR_HIGH
ODU0_TCMn_OCI ODU3_TCMn_BDI OUT_PWR_LOW
ODU0_TCMn_SSF ODU3_TCMn_DEG PORT_MODULE_OFFLINE
ODU0_TCMn_TIM ODU3_TCMn_LCK PRBS_LSS
ODU1_LOFLOM ODU3_TCMn_LTC R_LOS
ODU1_PM_AIS ODU3_TCMn_OCI TD
ODU1_PM_BDI ODU3_TCMn_SSF TEMP_OVER
ODU1_PM_DEG ODU3_TCMn_TIM TF
ODU1_PM_LCK ODU4_PM_AIS WRG_BD_TYPE
ODU1_PM_OCI ODU4_PM_BDI
TN54NS4(REG)
BD_LEDTEST OCh_SSF OPA_FAIL_INDI
BD_STATUS OCh_SSF_O OPU4_PLM
BEFFEC_EXC OCh_SSF_P OTU4_AIS

OptiX OSN 8800/6800/3800
COMMUN_FAIL ODU4_PM_AIS OTU4_BDI
HARD_BAD ODU4_PM_BDI OTU4_DEG
HARD_ERR ODU4_PM_DEG OTU4_LOF
IN_PWR_HIGH ODU4_PM_LCK OTU4_LOM
IN_PWR_LOW ODU4_PM_OCI OTU4_SSF
LOOP_ALM ODU4_PM_SSF OTU4_TIM
LSR_WILL_DIE ODU4_PM_TIM OUT_PWR_HIGH
NO_BD_SOFT ODU4_TCMn_AIS OUT_PWR_LOW
NO_ELABEL ODU4_TCMn_BDI PORT_MODULE_OFFLINE
NULL_SEND ODU4_TCMn_DEG PRBS_LSS
OCh_FDI ODU4_TCMn_LCK R_LOS
OCh_FDI_O ODU4_TCMn_LTC TD
OCh_FDI_P ODU4_TCMn_OCI TEMP_OVER
OCh_LOS_P ODU4_TCMn_SSF TF
OCh_OCI ODU4_TCMn_TIM WRG_BD_TYPE
NOTE
TCM6.
2.2.76 OAU1 Board Alarm List

TN13OAU1
BD_LEDTEST MUT_LOS PUM_TEM_ALM
BD_STATUS NO_BD_PARA SPAN_LOSS_HIGH
COMMUN_FAIL NO_BD_SOFT SPAN_LOSS_LOW
GAINDATA_MIS NO_ELABEL SUM_INPWR_HI
HARD_BAD OA_LOW_GAIN SUM_INPWR_LOW
HARD_ERR OPA_FAIL_INDI TEMP_OVER
INSERTION_LOSS_HIG
H PUMP_COOL_EXC WRG_BD_TYPE
LASER_HAZARD_WA
RNING PUM_BCM_ALM

OptiX OSN 8800/6800/3800
TN12OAU1
INSERTION_LOSS_HIGH PUMP_COOL_EXC WRG_BD_TYPE
LASER_HAZARD_WARN- PUM_BCM_ALM
ING
TN11OAU1
BD_LEDTEST LASER_HAZARD_WAR PUM_BCM_ALM

NING
BD_STATUS MUT_LOS PUM_TEM_ALM
COMMUN_FAIL NO_BD_PARA SPAN_LOSS_HIGH
DSP_LOAD_FAIL NO_BD_SOFT SPAN_LOSS_LOW
INSERTION_LOSS_HIGH PUMP_COOL_EXC WRG_BD_TYPE
2.2.77 OBU1 Board Alarm List

TN12OBU1
BD_LEDTEST NO_BD_PARA SPAN_LOSS_HIGH
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 WRG_BD_TYPE

OptiX OSN 8800/6800/3800
ING
MUT_LOS PUM_TEM_ALM
TN11OBU1
DSP_LOAD_FAIL NO_ELABEL SUM_INPWR_HI
ING
2.2.78 OBU2 Board Alarm List

TN12OBU2
BD_LEDTEST NO_BD_PARA SPAN_LOSS_HIGH
BD_STATUS NO_BD_SOFT SPAN_LOSS_LOW
COMMUN_FAIL NO_ELABEL SUM_INPWR_HI
ING
MUT_LOS PUM_TEM_ALM
TN11OBU2

OptiX OSN 8800/6800/3800
DSP_LOAD_FAIL NO_ELABEL SUM_INPWR_HI
ING
2.2.79 OLP Board Alarm List

TN11OLP
BD_LEDTEST NO_BD_PARA OCh_SSF_P
BD_STATUS NO_BD_SOFT OLP_PS
CLIENT_PORT_PS NO_ELABEL OLP_STA_INDI
CLIENT_PORT_STA_IN- OCh_FDI OPA_FAIL_INDI

DI
COMMUN_FAIL OCh_FDI_O POWER_DIFF_OVER
HARD_BAD OCh_FDI_P R_LOS
HARD_ERR OCh_LOS_P TEMP_OVER
INTRA_OTU_PS OCh_OCI WRG_BD_TYPE
INTRA_OTU_STA_INDI OCh_SSF
MUT_LOS OCh_SSF_O
TN12OLP
BD_LEDTEST MUT_LOS OCh_SSF_P
BD_STATUS NO_BD_PARA OLP_PS
CLIENT_PORT_PS OCh_FDI OLP_STA_INDI
CLIENT_PORT_STA_IN- OCh_FDI_O OPA_FAIL_INDI

DI
COMMUN_FAIL OCh_FDI_P POWER_DIFF_OVER
HARD_BAD OCh_LOS_P R_LOS

OptiX OSN 8800/6800/3800
HARD_ERR OCh_OCI TEMP_OVER
INTRA_OTU_PS OCh_SSF WRG_BD_TYPE
INTRA_OTU_STA_INDI OCh_SSF_O
2.2.80 OPM8 Board Alarm List

APE_ADJUST_FAIL COMMUN_FAIL NO_ELABEL
APE_ADJUST_PEND HARD_BAD PORTSWITCH_FAIL
BD_LEDTEST HARD_ERR TEMP_OVER
BD_STATUS MODULEFILE_UPDATE_FAI WRG_BD_TYPE

L
CHAN_ADD MOD_COM_FAIL WAVE_ADD_ABN
CHAN_LOS NO_BD_SOFT WAVE_DROP_ABN
2.2.81 PIU Board Alarm List

BD_STATUS THUNDERALM WRG_BD_TYPE
POWER_FAIL
2.2.82 PND2 Board Alarm List

BD_LEDTEST LSR_COOL_ALM ODU2_TCMn_DEG
BD_STATUS LSR_WILL_DIE ODU2_TCMn_LCK
BEFFEC_EXC MCLAG_CFG_MISMATCH ODU2_TCMn_LTC
BWUTILIZATION_OVE
R MCSP_PATH_LOCV ODU2_TCMn_OCI
COMMUN_FAIL MPLS_PW_AIS ODU2_TCMn_SSF
ETHOAM_SELF_LOOP MPLS_PW_LOCV ODU2_TCMn_TIM
ETH_APS_LOST MPLS_PW_OAMFAIL OPU2_PLM
ETH_APS_PATH_MIS-
MATCH MPLS_PW_RDI OTU2_BDI

OptiX OSN 8800/6800/3800
ETH_APS_SWITCH_FA
IL MPLS_PW_SD OTU2_DEG
ETH_APS_TYPE_MIS-
MATCH MPLS_PW_SF OTU2_LOF
ETH_CFM_AIS MPLS_PW_UNEXPMEG OTU2_LOM
ETH_CFM_LOC MPLS_PW_UNEXPMEP OTU2_SSF
ETH_CFM_MISMERGE MPLS_PW_UNEXPPER OTU2_TIM
ETH_CFM_RDI MPLS_TUNNEL_AIS OUT_PWR_HIGH
MPLS_TUNNEL_OAM-
ETH_CFM_UNEXPERI FAIL OUT_PWR_LOW
ETH_EFM_DF MPLS_TUNNEL_RDI PORT_EXC_TRAFFIC
MPLS_TUNNEL_UNEXP-
ETH_EFM_EVENT MEG PORT_MODULE_OFFLINE
MPLS_TUNNEL_UNEXP-
ETH_EFM_LOOPBACK MEP PRBS_LSS
MPLS_TUNNEL_UNEXP-
ETH_EFM_REMFAULT PER PWAPS_LOST
PWAPS_PATH_MIS-
ETH_LINK_DOWN MPLS_Tunnel_LOCV MATCH
ETH_NO_FLOW MPLS_Tunnel_SD PWAPS_SWITCH_FAIL
PWAPS_TYPE_MIS-
FDBSIZEALM_ELAN MPLS_Tunnel_SF MATCH
FLOW_OVER NO_ELABEL PW_NO_TRAFFIC
HARD_BAD NULL_SEND R_LOS
HARD_ERR ODU2_PM_BDI SRV_SHUTDOWN_LD
IN_PWR_HIGH ODU2_PM_DEG TD
IN_PWR_LOW ODU2_PM_LCK TEMP_OVER
LAG_DOWN ODU2_PM_OCI TF
TUNNEL_APS_DEGRA-
LAG_MEMBER_DOWN ODU2_PM_SSF DED
LASER_MODULE_MIS
MATCH ODU2_PM_TIM WAVEDATA_MIS
LOOP_ALM ODU2_TCMn_BDI WRG_BD_TYPE

OptiX OSN 8800/6800/3800
NOTE
TCM6.
2.2.83 PTQX Board Alarm List

B1_EXC ODU1_TCM3_LTC ODU2_TCM4_DEG
B1_SD ODU1_TCM3_OCI ODU2_TCM4_LCK
BD_LEDTEST ODU1_TCM3_SSF ODU2_TCM4_LTC
BD_STATUS ODU1_TCM3_TIM ODU2_TCM4_OCI
BEFFEC_EXC ODU1_TCM4_AIS ODU2_TCM4_SSF
BUS_ERR ODU1_TCM4_BDI ODU2_TCM4_TIM
CLIENT_PORT_PS ODU1_TCM4_DEG ODU2_TCM5_AIS
CLIENT_PORT_STA_INDI ODU1_TCM4_LCK ODU2_TCM5_BDI
CLIENT_PROT_NOTSTART ODU1_TCM4_LTC ODU2_TCM5_DEG
IN_PWR_HIGH ODU1_TCM5_AIS ODU2_TCM5_SSF
IN_PWR_LOW ODU1_TCM5_BDI ODU2_TCM5_TIM
J0_MM ODU1_TCM5_DEG ODU2_TCM6_AIS
LASER_MODULE_MIS- ODU1_TCM5_LCK ODU2_TCM6_BDI

MATCH
LOCAL_FAULT ODU1_TCM5_LTC ODU2_TCM6_DEG
LOOP_ALM ODU1_TCM5_OCI ODU2_TCM6_LCK
LPT_ACTIVE 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
NO_ELABEL ODU1_TCM6_LTC OMS_BDI
NULL_SEND ODU1_TCM6_OCI OMS_BDI_O

OptiX OSN 8800/6800/3800
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_OFF-

LINE
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
ODU1_TCM2_LTC ODU2_TCM3_DEG TD
ODU1_TCM2_OCI ODU2_TCM3_LCK TEMP_OVER

OptiX OSN 8800/6800/3800
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 MAINBD_SUBBD_MIS-

MATCH
2.2.84 RAU1 Board Alarm List

ASE_NOT_CALI-
BRATE MOD_COM_FAIL RL_CRITICAL_HI
BD_LEDTEST MUT_LOS RL_CRITICAL_LOW
FIBERTYPE_MIS NO_ELABEL SUM_INPWR_HI
HARD_BAD OA_HIGH_GAIN TEMP_OVER
HARD_ERR OPA_FAIL_INDI INSERTION_LOSS_HIGH
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WRG_BD_TYPE
LOCKPOW_MIS PUM_BCM_ALM
LSR_WILL_DIE PUM_TEM_ALM
2.2.85 RAU2 Board Alarm List

ASE_NOT_CALI-
BRATE LSR_WILL_DIE PUM_TEM_ALM
BD_LEDTEST MOD_COM_FAIL RL_CRITICAL_HI
BD_STATUS MUT_LOS RL_CRITICAL_LOW
COMMUN_FAIL NO_BD_PARA SPAN_LOSS_HIGH
FIBERTYPE_MIS NO_BD_SOFT SPAN_LOSS_LOW

OptiX OSN 8800/6800/3800
HARD_BAD OA_HIGH_GAIN SUM_INPWR_LOW
HARD_ERR OA_LOW_GAIN TEMP_OVER
INSERTION_LOSS_HIG
H OPA_FAIL_INDI VOADATA_MIS
LASER_HAZARD_WA
RNING PUMP_COOL_EXC WRG_BD_TYPE
LOCKPOW_MIS PUM_BCM_ALM
2.2.86 RDU9 Board Alarm List

TN11RDU9
BD_LEDTEST OMS_BDI OMS_SSF_P
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 OMS_FDI_P WAVEDATA_MIS

AIL
MODULE_ADJUST_FAIL OMS_LOS_P WRG_BD_TYPE
MOD_COM_FAIL OMS_SSF
MUT_LOS OMS_SSF_O
2.2.87 RMU9 Board Alarm List

BD_LEDTEST NO_ELABEL OMS_SSF_O
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 OMS_FDI_O TEMP_OVER

R

OptiX OSN 8800/6800/3800
MUT_LOS OMS_FDI_P VOADATA_MIS
NO_BD_PARA OMS_LOS_P WAVEDATA_MIS
NO_BD_SOFT OMS_SSF WRG_BD_TYPE
2.2.88 ROAM Board Alarm List

BD_LEDTEST NO_BD_SOFT OMS_SSF
BD_STATUS NO_ELABEL OMS_SSF_O
MODULEFILE_UPDATE_F OMS_FDI SUM_INPWR_LOW

AIL
MODULE_ADJUST_FAIL OMS_FDI_O TEMP_OVER
MOD_COM_FAIL OMS_FDI_P WAVEDATA_MIS
MUT_LOS OMS_LOS_P WRG_BD_TYPE
2.2.89 SBM2 Board Alarm List

OPA_FAIL_INDI
2.2.90 SC1 Board Alarm List

ALM_HANGUP LOOP_ALM R_LOF
BD_LEDTEST LSR_WILL_DIE R_SLIP
BD_STATUS NO_BD_PARA SCC_LOC
COMMUN_FAIL NO_BD_SOFT TEMP_OVER
CRC4_CROSSTR NO_ELABEL TF
HARD_BAD OSC_LOS T_SLIP
HARD_ERR OSC_RDI WRG_BD_TYPE

OptiX OSN 8800/6800/3800
IN_PWR_HIGH OUT_PWR_HIGH
IN_PWR_LOW OUT_PWR_LOW
2.2.91 SC2 Board Alarm List

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

TN52SCC
STORM_CUR_QUEN
ALC_ADJUST_FAIL K1_K2_M UM_OVER
ALC_WAIT_ADJUST SUBRACK_COMM_P
K2_M S
APS_FAIL SUBRACK_ID_CON-
LCS_DAYS_OF_GRACE FLICT
APS_INDI SUBRACK_ID_MIS-
LCS_EXPIRED MATCH
APS_MANUAL_STOP LCS_FILE_NOT_EXIST SUBRACK_LOOP
BD_LEDTEST MS_APS_INDI_EX SUBRACK_TYPE_MI

SMATCH
BD_NOT_INSTALLED NEBD_XC_DIF SWDL_ACTIVATED_

TIMEOUT
BD_STATUS NESF_LOST SWDL_AUTOMATCH

_INH

OptiX OSN 8800/6800/3800
BOOTROM_BAD NESTATE_INSTALL SWDL_BD_EXCLUDE
CFCARD_FAILED NO_ELABEL SWDL_CHGMNG_NO

MATCH
COM_EXTECC_FULL NODEID_MM SWDL_COMMIT_FAI

L
COMMUN_FAIL NTP_SYNC_FAIL SWDL_INPROCESS
CPC_NODE_ID_ERR PASSWORD_NEED_CHANGE SWDL_NEPKGCHEC

K
DBMS_DELETE PATCH_PKGERR SWDL_PKGVER_MM
DBMS_ERROR POWER_FAIL SWDL_PKG_NOBD-

SOFT
DBMS_PROTECT_MOD RTC_FAIL SWDL_ROLLBACK_F

E AIL
DB_RESTORE_FAIL SECU_ALM SYNC_DISABLE
DCNSIZE_OVER SEC_RADIUS_FAIL SYNC_FAIL
EFI_TYPE_MISMATCH SERVICE_CAPACITY_EXCEE SYSLOG_COMM_FAI

D_LICENSE L
FEATURE_WITHOUT_ SERVICE_TYPE_EXCEED_LI- SYSPARA_CFDB_NO-

LICENSE CENSE SAME
HARD_BAD SHELF_AREA_POWER_OVER TEMP_OVER
HARD_ERR SNCP_FAIL WRG_BD_TYPE
HSC_UNAVAIL SSL_CERT_NOENC XC_UNSWITCH
TN51SCC
LCS_DAYS_OF_GRACE SUBRACK_ID_CON-
ALC_ADJUST_FAIL FLICT
ALC_WAIT_ADJUST LCS_EXPIRED SUBRACK_ID_MIS-

MATCH
APS_FAIL LCS_FILE_NOT_EXIST SUBRACK_LOOP
APS_INDI MS_APS_INDI_EX SUBRACK_TYPE_MI

SMATCH
APS_MANUAL_STOP NEBD_XC_DIF SWDL_ACTIVATED_

TIMEOUT
BD_LEDTEST NESF_LOST SWDL_AUTOMATCH

_INH

OptiX OSN 8800/6800/3800
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
COM_EXTECC_FULL PASSWORD_NEED_CHANGE SWDL_INPROCESS
COMMUN_FAIL PATCH_PKGERR SWDL_NEPKGCHEC

K
CPC_NODE_ID_ERR POWER_FAIL SWDL_PKGVER_MM
DBMS_DELETE RTC_FAIL SWDL_PKG_NOBD-

SOFT
DBMS_ERROR SECU_ALM SWDL_ROLLBACK_F

AIL
DBMS_PROTECT_MOD SEC_RADIUS_FAIL SYNC_DISABLE

E
DB_RESTORE_FAIL SERVICE_CAPACITY_EXCEE SYNC_FAIL

D_LICENSE
DCNSIZE_OVER SERVICE_TYPE_EXCEED_LI- SYSLOG_COMM_FAI

CENSE L
FEATURE_WITHOUT_ SHELF_AREA_POWER_OVER SYSPARA_CFDB_NO-

LICENSE SAME
HARD_BAD SNCP_FAIL TEMP_OVER
HARD_ERR SSL_CERT_NOENC WRG_BD_TYPE
HSC_UNAVAIL STORM_CUR_QUENUM_OVE XC_UNSWITCH

R
K1_K2_M SUBRACK_COMM_PS
TN11SCC
SUBRACK_TYPE_MIS-
ALC_ADJUST_FAIL LCS_DAYS_OF_GRACE MATCH
ALC_WAIT_ADJUST SWDL_ACTIVATED_TI
LCS_EXPIRED MEOUT
BD_LEDTEST SWDL_AUTOMATCH_I
LCS_FILE_NOT_EXIST NH
BD_NOT_INSTALLED NESF_LOST SWDL_BD_EXCLUDE

OptiX OSN 8800/6800/3800
BD_STATUS NESTATE_INSTALL SWDL_CHGMNG_NO-

MATCH
BOOTROM_BAD NTP_SYNC_FAIL SWDL_COMMIT_FAIL
COM_EXTECC_FULL PASSWORD_NEED_CHA SWDL_INPROCESS

NGE
COMMUN_FAIL PATCH_PKGERR SWDL_NEPKGCHECK
DBMS_DELETE POWER_FAIL SWDL_PKGVER_MM
DBMS_ERROR RTC_FAIL SWDL_PKG_NOBD-

SOFT
DBMS_PROTECT_MODE SECU_ALM SWDL_ROLLBACK_FAI

L
DB_RESTORE_FAIL SEC_RADIUS_FAIL SYNC_DISABLE
DCNSIZE_OVER SSL_CERT_NOENC SYNC_FAIL
FEATURE_WITHOUT_LI- STORM_CUR_QUENUM_ SYSLOG_COMM_FAIL

CENSE OVER
HARD_BAD SUBRACK_ID_CONFLICT SYSPARA_CFDB_NO-

SAME
HARD_ERR SUBRACK_ID_MIS- TEMP_OVER

MATCH
HSC_UNAVAIL SUBRACK_LOOP WRG_BD_TYPE
TN22SCC/TN23SCC
SWDL_ACTIVATED_TI
ALC_ADJUST_FAIL HARD_ERR MEOUT
ALC_WAIT_ADJUST SWDL_AUTOMATCH_I
HSC_UNAVAIL NH
BD_LEDTEST LCS_DAYS_OF_GRACE SWDL_BD_EXCLUDE
BD_NOT_INSTALLED SWDL_CHGMNG_NO-
LCS_EXPIRED MATCH
BD_STATUS LCS_FILE_NOT_EXIST SWDL_COMMIT_FAIL
BOOTROM_BAD NESF_LOST SWDL_INPROCESS
COM_EXTECC_FULL NESTATE_INSTALL SWDL_NEPKGCHECK
COMMUN_FAIL NTP_SYNC_FAIL SWDL_PKGVER_MM

OptiX OSN 8800/6800/3800
CPC_NODE_ID_ERR PASSWORD_NEED_CHA SWDL_PKG_NOBD-

NGE SOFT
DBMS_DELETE PATCH_PKGERR SWDL_ROLLBACK_FAI

L
DBMS_ERROR POWER_FAIL SYNC_DISABLE
DBMS_PROTECT_MODE RTC_FAIL SYNC_FAIL
DB_RESTORE_FAIL SECU_ALM SYSLOG_COMM_FAIL
DCNSIZE_OVER SEC_RADIUS_FAIL SYSPARA_CFDB_NO-

SAME
FEATURE_WITHOUT_LI- SSL_CERT_NOENC TEMP_OVER

CENSE
HARD_BAD STORM_CUR_QUENUM_ WRG_BD_TYPE

OVER
TNK2SCC
SUBRACK_ID_CON-
ALC_ADJUST_FAIL K2_M FLICT
ALC_WAIT_ADJUST SUBRACK_ID_MIS-
LCS_DAYS_OF_GRACE MATCH
APS_FAIL LCS_EXPIRED SUBRACK_LOOP
APS_INDI SUBRACK_TYPE_MI
LCS_FILE_NOT_EXIST SMATCH
APS_MANUAL_STOP MS_APS_INDI_EX SWDL_ACTIVATED_

TIMEOUT
BD_LEDTEST NEBD_XC_DIF SWDL_AUTOMATCH

_INH
BD_NOT_INSTALLED NESF_LOST SWDL_BD_EXCLUDE
BD_STATUS NESTATE_INSTALL SWDL_CHGMNG_NO

MATCH
BOOTROM_BAD NO_ELABEL SWDL_COMMIT_FAI

L
CFCARD_FAILED NODEID_MM SWDL_INPROCESS
COM_EXTECC_FULL NTP_SYNC_FAIL SWDL_NEPKGCHEC

K
COMMUN_FAIL PATCH_PKGERR SWDL_PKGVER_MM

OptiX OSN 8800/6800/3800
CPC_NODE_ID_ERR POWER_FAIL SWDL_PKG_NOBD-

SOFT
DBMS_DELETE RTC_FAIL SWDL_ROLLBACK_F

AIL
DBMS_ERROR SECU_ALM SYNC_DISABLE
DBMS_PROTECT_MOD SEC_RADIUS_FAIL SYNC_FAIL

E
DB_RESTORE_FAIL SERVICE_CAPACITY_EXCEE SYSLOG_COMM_FAI

D_LICENSE L
DCNSIZE_OVER SERVICE_TYPE_EXCEED_LI- SYSPARA_CFDB_NO-

CENSE SAME
FEATURE_WITHOUT_ SHELF_AREA_POWER_OVER TEMP_OVER

LICENSE
HARD_BAD SNCP_FAIL WRG_BD_TYPE
HARD_ERR SSL_CERT_NOENC XC_UNSWITCH
HSC_UNAVAIL STORM_CUR_QUENUM_OVE
R
K1_K2_M SUBRACK_COMM_PS
TN16SCC
ALC_ADJUST_FAIL LCS_DAYS_OF_GRACE SUBRACK_COMM_PS
ALC_WAIT_ADJUST LCS_EXPIRED SUBRACK_ID_CONFLICT
SUBRACK_ID_MIS-
APS_MANUAL_STOP LCS_FILE_NOT_EXIST MATCH
APS_FAIL LTI SUBRACK_LOOP
SUBRACK_TYPE_MIS-
APS_INDI MS_APS_INDI_EX MATCH
SWDL_ACTIVATED_TIME
BD_LEDTEST NEBD_XC_DIF OUT
BD_NOT_INSTALLED NESF_LOST SWDL_AUTOMATCH_INH
BD_STATUS NESTATE_INSTALL SWDL_BD_EXCLUDE
SWDL_CHGMNG_NO-
BOOTROM_BAD NODEID_MM MATCH
CFCARD_FAILED NO_BD_SOFT SWDL_COMMIT_FAIL

OptiX OSN 8800/6800/3800
CLK_LOCK_FAIL NO_ELABEL SWDL_INPROCESS
CLK_NO_TRACE_MO
DE NTP_SYNC_FAIL SWDL_NEPKGCHECK
COM_EXTECC_FULL OOL SWDL_PKGVER_MM
PASSWORD_NEED_CHAN
COMMUN_FAIL GE SWDL_PKG_NOBDSOFT
CPC_NODE_ID_ERR PATCH_PKGERR SWDL_ROLLBACK_FAIL
DBMS_DELETE POWER_FAIL SYNC_C_LOS
DBMS_ERROR PTP_SOURCE_SWITCH SYNC_DISABLE
DBMS_PROTECT_MO
DE PTP_TIMESTAMP_ABN SYNC_FAIL
DB_RESTORE_FAIL RTC_FAIL SYNC_F_M_SWITCH
DCNSIZE_OVER S1_SYN_CHANGE SYNC_LOCKOFF
EXT_SYNC_LOS SECU_ALM SYN_BAD
EXT_TIME_LOC SEC_RADIUS_FAIL SYSLOG_COMM_FAIL
FEATURE_WITHOUT_ SERVICE_CAPACITY_EX SYSPARA_CFDB_NO-

LICENSE CEED_LICENSE SAME
SERVICE_TYPE_EXCEED
HARD_BAD _LICENSE TEMP_OVER
SHELF_AREA_POWER_O
HARD_ERR VER TIME_LOCK_FAIL
HSC_UNAVAIL SSM_LOS TIME_LOS
K1_K2_M SSM_QL_FAILED TIME_NO_TRACE_MODE
STORM_CUR_QUENUM_
K2_M OVER WRG_BD_TYPE
2.2.93 SCS Board Alarm List

OMS_BDI_O OMS_LOS_P WRG_BD_TYPE
OMS_BDI_P OMS_SSF
OMS_FDI OMS_SSF_O

OptiX OSN 8800/6800/3800
2.2.94 SFIU Board Alarm List

BD_STATUS OTS_BDI_O OTS_TIM
MUT_LOS OTS_BDI_P WAVEDATA_MIS
OPA_FAIL_INDI OTS_LOS_O
OTS_BDI OTS_LOS_P
2.2.95 ST2 Board Alarm List

LASER_MODULE_MIS- OUT_PWR_LOW
ALM_HANGUP MATCH
BD_LEDTEST PORT_MODULE_OFF-
LOOP_ALM LINE
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
2.2.96 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_OFF-

LINE
B1_SD J0_MM POWER_ABNORMAL
B2_EXC LASER_MODULE_MIS- R_LOC

MATCH
B2_SD LASER_SHUT R_LOF

OptiX OSN 8800/6800/3800
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.97 SF64A Board Alarm List


LINE

MATCH

OptiX OSN 8800/6800/3800
HP_LOM OTU_LOF TF
HP_REI PM_BDI WRG_BD_TYPE
HP_SLM PM_BEI
2.2.98 SFD64 Board Alarm List


LINE

MATCH

OptiX OSN 8800/6800/3800
HP_LOM OTU_LOF TF
HP_REI PM_BDI WAVEDATA_MIS
HP_SLM PM_BEI WRG_BD_TYPE
2.2.99 SL64 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_OFF-

LINE
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 LASER_MODULE_MIS- TEMP_OVER

MATCH
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

OptiX OSN 8800/6800/3800
2.2.100 SLH41 Board Alarm List


LINE

MATCH
2.2.101 SLD64 Board Alarm List


LINE

OptiX OSN 8800/6800/3800

MATCH
2.2.102 SLO16 Board Alarm List


LINE

MATCH

OptiX OSN 8800/6800/3800
2.2.103 SLQ16 Board Alarm List


LINE

MATCH
2.2.104 SLQ64 Board Alarm List


LINE

OptiX OSN 8800/6800/3800

MATCH
2.2.105 STG Board Alarm List

TN11STG/TN52STG/TNK2STG
BD_LEDTEST LTI SYNC_F_M_SWITCH
BD_STATUS NO_BD_SOFT SYNC_LOCKOFF
CLK_NO_TRACE_MOD NO_ELABEL SYN_BAD

E
COMMUN_FAIL OOL TEMP_OVER
EXT_SYNC_LOS S1_SYN_CHANGE TIME_LOS
EXT_TIME_LOC SSM_LOS TIME_NO_TRACE_MODE
HARD_BAD SSM_QL_FAILED WRG_BD_TYPE
HARD_ERR SYNC_C_LOS
2.2.106 STI Board Alarm List

BD_STATUS WRG_BD_TYPE
2.2.107 SXM Board Alarm List

BD_LEDTEST HARD_BAD TEMP_OVER

OptiX OSN 8800/6800/3800
BUS_ERR NO_BD_SOFT
2.2.108 SXH Board Alarm List

BUS_ERR NO_BD_SOFT
2.2.109 TBE Board Alarm List

B1_EXC ETH_CFM_RDI NO_BD_SOFT
B1_SD ETH_CFM_UNEXPERI NO_ELABEL
BD_STATUS EX_ETHOAM_CC_LOS OPA_FAIL_INDI
BUS_ERR EX_ETHOAM_MPID_CNFL OUT_PWR_HIGH

CT
CLIENT_PORT_PS FLOW_OVER OUT_PWR_LOW
CLIENT_PORT_STA_INDI HARD_BAD PORT_MODULE_OFF-

LINE
CLIENT_PROT_NOT- HARD_ERR RS_CROSSTR

START
COMMUN_FAIL IN_PWR_HIGH R_LOF
DBPS_ABNORMAL IN_PWR_LOW R_LOS
DLAG_PROTECT_FAIL J0_MM TD
ETHOAM_DISCOVER_FA LAG_PORT_FAIL TEMP_OVER

IL
ETHOAM_RMT_CRIT_FA LAG_VC_PORT_FAIL TEM_HA

ULT
ETHOAM_RMT_LOOP LASER_MODULE_MIS- TEM_LA

MATCH
ETHOAM_RMT_SD LINK_ERR TF
ETHOAM_SELF_LOOP LOOP_ALM VLAN_SNCP_PS

OptiX OSN 8800/6800/3800
ETHOAM_VCG_SELF_LO LPT_ACTIVE WAVEDATA_MIS

OP
ETH_CFM_LOC LSR_INVALID WRG_BD_TYPE
ETH_CFM_MACSTATUS LSR_WILL_DIE
ETH_CFM_MISMERGE MULTI_RPL_OWNER
2.2.110 TD20 Board Alarm List

BD_LEDTEST MUT_LOS PUMP_COOL_EXC
BD_STATUS NO_BD_PARA PUM_BCM_ALM
COMMUN_FAIL NO_BD_SOFT PUM_TEM_ALM
DERIVED_PWR_ER-
ROR NO_ELABEL SUM_INPWR_HI
HARD_ERR POWER_FAIL WRG_BD_TYPE
2.2.111 TDC Board Alarm List

BD_LEDTEST HARD_ERR R_LOS
BD_STATUS IN_PWR_HIGH TEMP_OVER
COMMUN_FAIL IN_PWR_LOW WRG_BD_TYPE
DCM_INSUFF NO_BD_SOFT
HARD_BAD NO_ELABEL
2.2.112 TDG Board Alarm List

ALS_ACTIVE LSR_INVALID OPU1_PLM
BD_LEDTEST LSR_WILL_DIE OUT_PWR_HIGH
BD_STATUS MS_SNCP_PS OUT_PWR_LOW
BUS_ERR MS_SNCP_STA_INDI PORT_MODULE_OFF-

LINE

OptiX OSN 8800/6800/3800
CLIENT_PORT_PS NO_BD_SOFT REM_SD
CLIENT_PORT_STA_INDI NO_ELABEL REM_SF
CLIENT_PROT_NOTSTART ODU1_LOFLOM R_LOS
COMMUN_FAIL ODU1_PM_AIS SW_SNCP_PS
HARD_BAD ODU1_PM_BDI SW_SNCP_STA_INDI
HARD_ERR ODU1_PM_DEG TD
IN_PWR_HIGH ODU1_PM_EXC TEMP_OVER
IN_PWR_LOW ODU1_PM_LCK TEM_HA
LASER_MODULE_MIS- ODU1_PM_OCI TEM_LA

MATCH
LINK_ERR ODU1_PM_SSF TF
LOOP_ALM ODU1_PM_TIM WAVEDATA_MIS
LPT_ACTIVE OPA_FAIL_INDI WRG_BD_TYPE
2.2.113 TDX Board Alarm List

TN53TDX
ALS_ACTIVE ODU2_PM_BDI OPU2_PLM
B1_EXC ODU2_PM_DEG OPUFLEX_CSF
B1_SD ODU2_PM_EXC OPUFLEX_PLM
BD_LEDTEST ODU2_PM_LCK OTU2_AIS
BD_STATUS ODU2_PM_OCI OTU2_BDI
BEFFEC_EXC ODU2_PM_SSF OTU2_DEG
BUS_ERR ODU2_PM_TIM OTU2_LOF
CLIENT_PORT_PS ODU2_TCMn_AIS OTU2_LOM
CLIENT_PORT_STA_I
NDI ODU2_TCMn_BDI OTU2_SSF
CLIENT_PROT_NOT-
START ODU2_TCMn_DEG OTU2_TIM
COMMUN_FAIL ODU2_TCMn_EXC OUT_PWR_HIGH
HARD_BAD ODU2_TCMn_LCK OUT_PWR_LOW
HARD_ERR ODU2_TCMn_LTC PORT_MODULE_OFFLINE

OptiX OSN 8800/6800/3800
IN_PWR_HIGH ODU2_TCMn_OCI PRBS_LSS
IN_PWR_LOW ODU2_TCMn_SSF REMOTE_FAULT
J0_MM ODU2_TCMn_TIM REM_SD
LASER_MODULE_MIS
MATCH ODUFLEX_LOFLOM REM_SF
LOCAL_FAULT ODUFLEX_PM_AIS RS_CROSSTR
LOOP_ALM ODUFLEX_PM_BDI R_LOC
LPT_ACTIVE ODUFLEX_PM_DEG R_LOF
LSR_INVALID ODUFLEX_PM_EXC R_LOS
LSR_WILL_DIE ODUFLEX_PM_LCK TD
L_SYNC ODUFLEX_PM_OCI TEMP_OVER
NO_BD_SOFT ODUFLEX_PM_SSF TEM_HA
NO_ELABEL ODUFLEX_PM_TIM TEM_LA
NULL_SEND ODU_SNCP_PS TF
ODU2_LOFLOM ODU_SNCP_STA_INDI WAVEDATA_MIS
ODU2_PM_AIS OPU2_CSF WRG_BD_TYPE
TN52TDX
ALS_ACTIVE NO_ELABEL OTU2_DEG
B1_EXC NULL_SEND OTU2_LOF
B1_SD ODU2_LOFLOM OTU2_LOM
BD_LEDTEST ODU2_PM_AIS OTU2_SSF
BD_STATUS ODU2_PM_BDI OTU2_TIM
BEFFEC_EXC ODU2_PM_DEG OUT_PWR_HIGH
BUS_ERR ODU2_PM_LCK OUT_PWR_LOW
CLIENT_PORT_PS ODU2_PM_OCI PORT_MODULE_OFFLINE
CLIENT_PORT_STA_I
NDI ODU2_PM_SSF PRBS_LSS
CLIENT_PROT_NOT-
START ODU2_PM_TIM REM_SD
COMMUN_FAIL ODU2_TCMn_AIS REM_SF

OptiX OSN 8800/6800/3800
HARD_BAD ODU2_TCMn_BDI REMOTE_FAULT
HARD_ERR ODU2_TCMn_DEG R_LOC
IN_PWR_HIGH ODU2_TCMn_LCK R_LOF
IN_PWR_LOW ODU2_TCMn_LTC R_LOS
J0_MM ODU2_TCMn_OCI TD
LASER_MODULE_MIS
MATCH ODU2_TCMn_SSF TEMP_OVER
LOCAL_FAULT ODU2_TCMn_TIM TEM_HA
LOOP_ALM ODU_SNCP_PS TEM_LA
LPT_ACTIVE ODU_SNCP_STA_INDI TF
LSR_INVALID OPU2_PLM WAVEDATA_MIS
LSR_WILL_DIE OTU2_AIS WRG_BD_TYPE
NO_BD_SOFT OTU2_BDI
TN11TDX
ALS_ACTIVE LPT_ACTIVE OPU1_VCAT_VcPLM
B1_EXC LSR_COOL_ALM OUT_PWR_HIGH
B1_SD LSR_INVALID OUT_PWR_LOW
BD_LEDTEST LSR_WILL_DIE PORT_MODULE_OFF-

LINE
BD_STATUS MS_AIS PRBS_LSS
BUS_ERR NO_BD_SOFT REMOTE_FAULT
CLIENT_PORT_PS NO_ELABEL REM_SD
CLIENT_PORT_STA_INDI ODU1_LOFLOM REM_SF
CLIENT_PROT_NOTSTART ODU1_PM_AIS R_LOC
COMMUN_FAIL ODU1_PM_BDI R_LOF
FLOW_OVER ODU1_PM_DEG R_LOS
HARD_BAD ODU1_PM_EXC TD
HARD_ERR ODU1_PM_LCK TEMP_OVER
IN_PWR_HIGH ODU1_PM_OCI TEM_HA
IN_PWR_LOW ODU1_PM_SSF TEM_LA

OptiX OSN 8800/6800/3800
J0_MM ODU1_PM_TIM TF
LASER_MODULE_MIS- OPA_FAIL_INDI VCAT_LOA

MATCH
LOCAL_FAULT OPU1_PLM WAVEDATA_MIS
LOOP_ALM OPU1_VCAT_SQM WRG_BD_TYPE
TN12TDX
ALS_ACTIVE LPT_ACTIVE OPU2_PLM
B1_EXC LSR_COOL_ALM OUT_PWR_HIGH
B1_SD LSR_INVALID OUT_PWR_LOW
BD_LEDTEST LSR_WILL_DIE PORT_MODULE_OFF-

LINE
BD_STATUS NO_BD_SOFT PRBS_LSS
BUS_ERR NO_ELABEL REMOTE_FAULT
CLIENT_PORT_PS ODU2_LOFLOM REM_SD
CLIENT_PORT_STA_INDI ODU2_PM_AIS REM_SF
CLIENT_PROT_NOTSTART ODU2_PM_BDI R_LOC
COMMUN_FAIL ODU2_PM_DEG R_LOF
HARD_BAD ODU2_PM_EXC 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
LASER_MODULE_MIS- ODU_SNCP_PS TF
MATCH
LOCAL_FAULT ODU_SNCP_STA_INDI WAVEDATA_MIS
LOOP_ALM OPA_FAIL_INDI WRG_BD_TYPE
2.2.114 TEM28 Board Alarm List

ALS_ACTIVE IN_PWR_HIGH ODU2_TCMn_SSF

OptiX OSN 8800/6800/3800
B1_EXC IN_PWR_LOW ODU2_TCMn_TIM
B1_SD J0_MM OPA_FAIL_INDI
BD_LEDTEST LAG_PORT_FAIL OPU2_PLM
BD_STATUS LAG_VC_PORT_FAIL OTU2_AIS
LASER_MODULE_MIS-
BEFFEC_EXC MATCH OTU2_BDI
BUS_ERR LINK_ERR OTU2_DEG
CLIENT_PORT_PS LOOP_ALM OTU2_LOF
CLIENT_PORT_STA_I
NDI LPT_ACTIVE OTU2_LOM
CLIENT_PROT_NOT-
START LPT_RFI OTU2_SSF
COMMUN_FAIL LSR_COOL_ALM OTU2_TIM
DBPS_ABNORMAL LSR_INVALID OUT_PWR_HIGH
ETHOAM_DISCOVER_
ETHOAM_RMT_CRIT_
ETHOAM_VCG_SELF_
ETH_CFM_MACSTA-
ETH_SERVICE_CONFI
EX_ETHOAM_MPID_C

OptiX OSN 8800/6800/3800
HARD_ERR ODU2_TCMn_OCI
2.2.115 THA Board Alarm List

ALS_ACTIVE ODU0_PM_OCI OPU0_PLM
B1_EXC ODU0_PM_SSF OPU1_CSF
B1_SD ODU0_PM_TIM OPU1_MSIM
BD_LEDTEST ODU1_LOFLOM OPU1_PLM
BD_STATUS ODU1_PM_AIS OPUFLEX_CSF
BEFFEC_EXC ODU1_PM_BDI OPUFLEX_PLM
BUS_ERR ODU1_PM_DEG OTU1_AIS
CLIENT_PORT_PS ODU1_PM_EXC OTU1_BDI
CLIENT_PORT_STA_I
NDI ODU1_PM_LCK OTU1_DEG
CLIENT_PROT_NOT-
START ODU1_PM_OCI OTU1_EXC
COMMUN_FAIL ODU1_PM_SSF OTU1_LOF
HARD_BAD ODU1_PM_TIM OTU1_LOM
HARD_ERR ODU1_TCMn_AIS OTU1_SSF
HARD_NONSUPPORT ODU1_TCMn_BDI OTU1_TIM
IN_PWR_HIGH ODU1_TCMn_DEG OUT_PWR_HIGH
IN_PWR_LOW ODU1_TCMn_EXC OUT_PWR_LOW
J0_MM ODU1_TCMn_LCK PORT_MODULE_OFFLINE
LASER_MODULE_MIS
MATCH ODU1_TCMn_LTC PRBS_LSS
LINK_ERR ODU1_TCMn_OCI REM_SD
LOOP_ALM ODU1_TCMn_SSF REM_SF
LPT_ACTIVE ODU1_TCMn_TIM RS_CROSSTR
LSR_INVALID ODUFLEX_LOFLOM R_LOC

OptiX OSN 8800/6800/3800
LSR_WILL_DIE ODUFLEX_PM_AIS R_LOF
L_SYNC ODUFLEX_PM_BDI R_LOS
NO_BD_SOFT ODUFLEX_PM_DEG TD
NO_ELABEL ODUFLEX_PM_EXC TEMP_OVER
NULL_SEND ODUFLEX_PM_LCK TEM_HA
ODU0_LOFLOM ODUFLEX_PM_OCI TEM_LA
ODU0_PM_AIS ODUFLEX_PM_SSF TF
ODU0_PM_BDI ODUFLEX_PM_TIM TS_CFG_MISMATCH
ODU0_PM_DEG ODU_SNCP_PS WAVEDATA_MIS
ODU0_PM_EXC ODU_SNCP_STA_INDI WRG_BD_TYPE
ODU0_PM_LCK OPU0_CSF
NOTE
TCM6.
2.2.116 TM20 Board Alarm List

BD_LEDTEST MODULE_ADJUST_FAIL NO_ELABEL
BD_STATUS MODULE_TEMP_OVER OPA_FAIL_INDI
COMMUN_FAIL MOD_COM_FAIL POWER_FAIL
HARD_BAD MUT_TLOS TEMP_OVER
HARD_ERR NO_BD_PARA WRG_BD_TYPE
MODULEFILE_UPDAT
E_FAIL NO_BD_SOFT
2.2.117 TMX Board Alarm List

TN11TMX
ALS_ACTIVE ODU1_TCM3_OCI ODU2_TCM4_AIS
B1_EXC ODU1_TCM3_SSF ODU2_TCM4_BDI
B1_SD ODU1_TCM3_TIM ODU2_TCM4_DEG
BD_LEDTEST ODU1_TCM4_AIS ODU2_TCM4_LCK

OptiX OSN 8800/6800/3800
BD_STATUS ODU1_TCM4_BDI ODU2_TCM4_LTC
BEFFEC_EXC ODU1_TCM4_DEG ODU2_TCM4_OCI
CLIENT_PORT_PS ODU1_TCM4_LCK ODU2_TCM4_SSF
CLIENT_PORT_STA_INDI ODU1_TCM4_LTC ODU2_TCM4_TIM
CLIENT_PROT_NOTSTART ODU1_TCM4_OCI ODU2_TCM5_AIS
COMMUN_FAIL ODU1_TCM4_SSF ODU2_TCM5_BDI
HARD_BAD ODU1_TCM4_TIM ODU2_TCM5_DEG
HARD_ERR ODU1_TCM5_AIS ODU2_TCM5_LCK
IN_PWR_HIGH ODU1_TCM5_BDI ODU2_TCM5_LTC
IN_PWR_LOW ODU1_TCM5_DEG ODU2_TCM5_OCI
J0_MM ODU1_TCM5_LCK ODU2_TCM5_SSF
LASER_MODULE_MIS- ODU1_TCM5_LTC ODU2_TCM5_TIM

MATCH
LOOP_ALM 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

OptiX OSN 8800/6800/3800
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
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_OFF-

LINE
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
TN12TMX
ALS_ACTIVE ODU1_TCM3_LTC ODU2_TCM4_AIS
B1_EXC ODU1_TCM3_OCI ODU2_TCM4_BDI

OptiX OSN 8800/6800/3800
BD_LEDTEST ODU1_TCM3_SSF ODU2_TCM4_DEG
B1_SD ODU1_TCM3_TIM ODU2_TCM4_LCK
CLIENT_PORT_PS ODU1_TCM4_DEG ODU2_TCM4_SSF
CLIENT_PORT_STA_INDI ODU1_TCM4_LCK ODU2_TCM4_TIM
CLIENT_PROT_NOTSTART ODU1_TCM4_LTC ODU2_TCM5_AIS
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
LASER_MODULE_MIS- ODU1_TCM5_LCK ODU2_TCM5_TIM

MATCH
LOOP_ALM ODU1_TCM5_LTC ODU2_TCM6_AIS
LSR_COOL_ALM 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

OptiX OSN 8800/6800/3800
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
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_OFF-

LINE
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
2.2.118 TOA Board Alarm List

TN54TOA

OptiX OSN 8800/6800/3800
ALS_ACTIVE ODU0_PM_SSF OPU1_CSF
B1_EXC ODU0_PM_TIM OPU1_MSIM
B1_SD ODU1_LOFLOM OPU1_PLM
BD_LEDTEST ODU1_PM_AIS OPUFLEX_CSF
BD_STATUS ODU1_PM_BDI OPUFLEX_PLM
BEFFEC_EXC ODU1_PM_DEG OTU1_AIS
BUS_ERR ODU1_PM_EXC OTU1_BDI
CLIENT_PORT_PS ODU1_PM_LCK OTU1_DEG
CLIENT_PORT_STA_I
NDI ODU1_PM_OCI OTU1_EXC
CLIENT_PROT_NOT-
START ODU1_PM_SSF OTU1_LOF
COMMUN_FAIL ODU1_PM_TIM OTU1_LOM
HARD_BAD ODU1_TCMn_AIS OTU1_SSF
HARD_ERR ODU1_TCMn_BDI OTU1_TIM
HARD_NONSUPPORT ODU1_TCMn_DEG OUT_PWR_HIGH
IN_PWR_HIGH ODU1_TCMn_EXC OUT_PWR_LOW
IN_PWR_LOW ODU1_TCMn_LCK PORT_MODULE_OFFLINE
J0_MM ODU1_TCMn_LTC PRBS_LSS
LASER_MODULE_MIS
MATCH ODU1_TCMn_OCI REM_SD
LINK_ERR ODU1_TCMn_SSF REM_SF
LPT_ACTIVE ODU1_TCMn_TIM RS_CROSSTR
LSR_INVALID ODUFLEX_LOFLOM R_LOC
LSR_WILL_DIE ODUFLEX_PM_AIS R_LOF
L_SYNC ODUFLEX_PM_BDI R_LOS
NO_BD_SOFT ODUFLEX_PM_DEG TD
NO_ELABEL ODUFLEX_PM_EXC TEMP_OVER
NULL_SEND ODUFLEX_PM_LCK TEM_HA
ODU0_LOFLOM ODUFLEX_PM_OCI TEM_LA
ODU0_PM_AIS ODUFLEX_PM_SSF TF
ODU0_PM_BDI ODUFLEX_PM_TIM TS_CFG_MISMATCH

OptiX OSN 8800/6800/3800
ODU0_PM_DEG ODU_SNCP_PS WAVEDATA_MIS
ODU0_PM_EXC ODU_SNCP_STA_INDI WRG_BD_TYPE
ODU0_PM_LCK OPU0_CSF
ODU0_PM_OCI OPU0_PLM
NOTE
TCM6.
2.2.119 TOG Board Alarm List

TN52TOG
ALS_ACTIVE NO_BD_SOFT ODU1_PM_TIM
BD_LEDTEST NO_ELABEL OPU0_PLM
BD_STATUS ODU0_LOFLOM OPU1_PLM
BUS_ERR ODU0_PM_AIS OUT_PWR_HIGH
CLIENT_PORT_PS ODU0_PM_BDI OUT_PWR_LOW
CLIENT_PORT_STA_INDI ODU0_PM_DEG PORT_MODULE_OFF-

LINE
CLIENT_PROT_NOTSTART ODU0_PM_LCK REM_SD
COMMUN_FAIL ODU0_PM_OCI REM_SF
HARD_BAD ODU0_PM_SSF R_LOS
HARD_ERR ODU0_PM_TIM TD
IN_PWR_HIGH ODU1_LOFLOM TEMP_OVER
IN_PWR_LOW ODU1_PM_AIS TEM_HA
LASER_MODULE_MIS- ODU1_PM_BDI TEM_LA

MATCH
LOOP_ALM 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

OptiX OSN 8800/6800/3800
2.2.120 TOM Board Alarm List

TN52TOM
ALS_ACTIVE ODU1_PM_BDI ODU1_TCM5_LTC
B1_EXC ODU1_PM_DEG ODU1_TCM5_OCI
B1_SD ODU1_PM_EXC ODU1_TCM5_SSF
BD_LEDTEST ODU1_PM_LCK ODU1_TCM5_TIM
BD_STATUS ODU1_PM_OCI ODU1_TCM6_AIS
BEFFEC_EXC ODU1_PM_SSF ODU1_TCM6_BDI
BUS_ERR ODU1_PM_TIM ODU1_TCM6_DEG
CLIENT_PORT_PS ODU1_TCM1_AIS ODU1_TCM6_EXC
CLIENT_PORT_STA_INDI ODU1_TCM1_BDI ODU1_TCM6_LCK
CLIENT_PROT_NOTSTART ODU1_TCM1_DEG ODU1_TCM6_LTC
COMMUN_FAIL ODU1_TCM1_EXC ODU1_TCM6_OCI
HARD_BAD ODU1_TCM1_LCK ODU1_TCM6_SSF
HARD_ERR ODU1_TCM1_LTC ODU1_TCM6_TIM
INTRA_OTU_PS ODU1_TCM1_OCI ODU_SNCP_PS
INTRA_OTU_STA_INDI ODU1_TCM1_SSF ODU_SNCP_STA_INDI
IN_PWR_HIGH ODU1_TCM1_TIM OPA_FAIL_INDI
IN_PWR_LOW ODU1_TCM2_AIS OPU0_PLM
J0_MM ODU1_TCM2_BDI OPU1_MSIM
LASER_MODULE_MIS- ODU1_TCM2_DEG OPU1_PLM

MATCH
LINK_ERR ODU1_TCM2_EXC OTU1_AIS
LOOP_ALM ODU1_TCM2_LCK OTU1_BDI
LPT_ACTIVE 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

OptiX OSN 8800/6800/3800
NO_ELABEL ODU1_TCM3_EXC OUT_PWR_LOW
NULL_SEND ODU1_TCM3_LCK PORT_MODULE_OFF-

LINE
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
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
ALS_ACTIVE ODU1_PM_SSF ODU1_TCM5_TIM
B1_EXC ODU1_PM_TIM ODU1_TCM6_AIS
B1_SD ODU1_TCM1_AIS ODU1_TCM6_BDI
BD_LEDTEST ODU1_TCM1_BDI ODU1_TCM6_DEG
BD_STATUS ODU1_TCM1_DEG ODU1_TCM6_EXC
BEFFEC_EXC ODU1_TCM1_EXC ODU1_TCM6_LCK
BUS_ERR ODU1_TCM1_LCK ODU1_TCM6_LTC

OptiX OSN 8800/6800/3800
CLIENT_PORT_PS ODU1_TCM1_LTC ODU1_TCM6_OCI
CLIENT_PORT_STA_INDI ODU1_TCM1_OCI ODU1_TCM6_SSF
CLIENT_PROT_NOTSTART ODU1_TCM1_SSF ODU1_TCM6_TIM
COMMUN_FAIL ODU1_TCM1_TIM ODU_SNCP_PS
HARD_BAD ODU1_TCM2_AIS ODU_SNCP_STA_INDI
INTRA_OTU_PS ODU1_TCM2_DEG OPU1_PLM
INTRA_OTU_STA_INDI ODU1_TCM2_EXC OTU1_AIS
IN_PWR_HIGH ODU1_TCM2_LCK OTU1_BDI
IN_PWR_LOW ODU1_TCM2_LTC OTU1_DEG
J0_MM ODU1_TCM2_OCI OTU1_EXC

MATCH
LINK_ERR ODU1_TCM2_TIM OTU1_LOM
LSR_WILL_DIE ODU1_TCM3_EXC OUT_PWR_LOW
L_SYNC ODU1_TCM3_LCK PORT_MODULE_OFF-

LINE
MS_AIS ODU1_TCM3_LTC PRBS_LSS
MS_SNCP_PS ODU1_TCM3_OCI REM_SD
MS_SNCP_STA_INDI ODU1_TCM3_SSF REM_SF
NO_BD_SOFT ODU1_TCM3_TIM RS_CROSSTR
NO_ELABEL ODU1_TCM4_AIS R_LOC
NULL_SEND ODU1_TCM4_BDI R_LOF
OCh_FDI ODU1_TCM4_DEG R_LOS
OCh_FDI_O ODU1_TCM4_EXC SPEED_OVER
OCh_FDI_P ODU1_TCM4_LCK SW_SNCP_PS
OCh_LOS_P ODU1_TCM4_LTC SW_SNCP_STA_INDI
OCh_OCI ODU1_TCM4_OCI TD

OptiX OSN 8800/6800/3800
OCh_SSF ODU1_TCM4_SSF TEMP_OVER
OCh_SSF_O ODU1_TCM4_TIM TEM_HA
OCh_SSF_P ODU1_TCM5_AIS TEM_LA
ODU1_LOFLOM ODU1_TCM5_BDI TF
ODU1_PM_AIS ODU1_TCM5_DEG TS_CFG_MISMATCH
ODU1_PM_BDI ODU1_TCM5_EXC WAVEDATA_MIS
ODU1_PM_DEG ODU1_TCM5_LCK WRG_BD_TYPE
ODU1_PM_EXC ODU1_TCM5_LTC
ODU1_PM_LCK ODU1_TCM5_OCI
ODU1_PM_OCI ODU1_TCM5_SSF
2.2.121 TOX Board Alarm List

ALS_ACTIVE NO_BD_SOFT OTU2_AIS
B1_EXC NO_ELABEL OTU2_BDI
B1_SD NULL_SEND OTU2_DEG
BD_LEDTEST ODU2_LOFLOM OTU2_LOF
BD_STATUS ODU2_PM_AIS OTU2_LOM
BEFFEC_EXC ODU2_PM_BDI OTU2_SSF
BUS_ERR ODU2_PM_DEG OTU2_TIM
CLIENT_PORT_PS ODU2_PM_LCK OUT_PWR_HIGH
CLIENT_PORT_STA_I
NDI ODU2_PM_OCI OUT_PWR_LOW
CLIENT_PROT_NOT-
START ODU2_PM_SSF PORT_MODULE_OFFLINE
COMMUN_FAIL ODU2_PM_TIM PRBS_LSS
HARD_BAD ODU2_TCMn_AIS REMOTE_FAULT
HARD_ERR ODU2_TCMn_BDI RS_CROSSTR
IN_PWR_HIGH ODU2_TCMn_DEG R_LOC
IN_PWR_LOW ODU2_TCMn_LCK R_LOF
J0_MM ODU2_TCMn_LTC R_LOS

OptiX OSN 8800/6800/3800
LASER_MODULE_MIS
MATCH ODU2_TCMn_OCI REM_SD
LOCAL_FAULT ODU2_TCMn_SSF REM_SF
LOOP_ALM ODU2_TCMn_TIM TD
LPT_ACTIVE ODU_SNCP_PS TEMP_OVER
LSR_INVALID ODU_SNCP_STA_INDI TF
LSR_WILL_DIE OPU2_CSF WAVEDATA_MIS
L_SYNC OPU2_PLM WRG_BD_TYPE
NOTE
TCM6.
2.2.122 TQM Board Alarm List

TN11TQM
ALS_ACTIVE LSR_INVALID OUT_PWR_HIGH
B1_EXC LSR_WILL_DIE OUT_PWR_LOW
B1_SD L_SYNC PORT_MODULE_OFF-

LINE
BD_LEDTEST MS_AIS REM_SD
BD_STATUS MS_SNCP_PS REM_SF
BUS_ERR MS_SNCP_STA_INDI RS_CROSSTR
CLIENT_PORT_PS NO_BD_SOFT R_LOC
CLIENT_PORT_STA_INDI NO_ELABEL R_LOF
CLIENT_PROT_NOTSTART ODU1_LOFLOM R_LOS
COMMUN_FAIL ODU1_PM_AIS SW_SNCP_PS
HARD_BAD ODU1_PM_BDI SW_SNCP_STA_INDI
HARD_ERR ODU1_PM_DEG TD
IN_PWR_HIGH ODU1_PM_EXC TEMP_OVER
IN_PWR_LOW ODU1_PM_LCK TEM_HA
J0_MM ODU1_PM_OCI TEM_LA

OptiX OSN 8800/6800/3800
LASER_MODULE_MIS- ODU1_PM_SSF TF
MATCH
LINK_ERR ODU1_PM_TIM TS_CFG_MISMATCH
LOOP_ALM OPA_FAIL_INDI WAVEDATA_MIS
LPT_ACTIVE OPU1_PLM WRG_BD_TYPE
TN12TQM
ALS_ACTIVE ODU1_TCM1_LTC ODU1_TCM6_DEG
B1_EXC ODU1_TCM1_OCI ODU1_TCM6_EXC
B1_SD ODU1_TCM1_SSF ODU1_TCM6_LCK
BD_LEDTEST ODU1_TCM1_TIM ODU1_TCM6_LTC
BD_STATUS ODU1_TCM2_AIS ODU1_TCM6_OCI
BEFFEC_EXC ODU1_TCM2_BDI ODU1_TCM6_SSF
BUS_ERR ODU1_TCM2_DEG ODU1_TCM6_TIM
CLIENT_PORT_PS ODU1_TCM2_EXC ODU_SNCP_PS
CLIENT_PORT_STA_INDI ODU1_TCM2_LCK ODU_SNCP_STA_INDI
CLIENT_PROT_NOTSTART ODU1_TCM2_LTC OPA_FAIL_INDI
COMMUN_FAIL ODU1_TCM2_OCI OPU1_PLM
HARD_BAD ODU1_TCM2_SSF OTU1_AIS
HARD_ERR ODU1_TCM2_TIM OTU1_BDI
IN_PWR_HIGH ODU1_TCM3_AIS OTU1_DEG
IN_PWR_LOW ODU1_TCM3_BDI OTU1_EXC
J0_MM ODU1_TCM3_DEG OTU1_LOF
LASER_MODULE_MIS- ODU1_TCM3_EXC OTU1_LOM

MATCH
LINK_ERR ODU1_TCM3_LCK OTU1_SSF
LOOP_ALM ODU1_TCM3_LTC OTU1_TIM
LPT_ACTIVE ODU1_TCM3_OCI OUT_PWR_HIGH
LSR_INVALID ODU1_TCM3_SSF OUT_PWR_LOW
LSR_WILL_DIE ODU1_TCM3_TIM PORT_MODULE_OFF-

LINE

OptiX OSN 8800/6800/3800
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
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.123 TQS Board Alarm List

ALS_ACTIVE ODU1_TCM1_SSF ODU1_TCM6_AIS
B1_EXC ODU1_TCM1_TIM ODU1_TCM6_BDI
B1_SD ODU1_TCM2_AIS ODU1_TCM6_DEG
BD_LEDTEST ODU1_TCM2_BDI ODU1_TCM6_EXC
BD_STATUS ODU1_TCM2_DEG ODU1_TCM6_LCK
BEFFEC_EXC ODU1_TCM2_EXC ODU1_TCM6_LTC
BUS_ERR ODU1_TCM2_LCK ODU1_TCM6_OCI

OptiX OSN 8800/6800/3800
CLIENT_PORT_PS ODU1_TCM2_LTC ODU1_TCM6_SSF
CLIENT_PORT_STA_INDI ODU1_TCM2_OCI ODU1_TCM6_TIM
CLIENT_PROT_NOTSTART ODU1_TCM2_SSF ODU_SNCP_PS
COMMUN_FAIL ODU1_TCM2_TIM ODU_SNCP_STA_INDI
HARD_BAD ODU1_TCM3_AIS OPA_FAIL_INDI
HARD_ERR ODU1_TCM3_BDI OPU1_PLM

MATCH
LOOP_ALM 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_OFF-

LINE
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

OptiX OSN 8800/6800/3800
ODU1_TCM1_LTC ODU1_TCM5_SSF WRG_BD_TYPE
ODU1_TCM1_OCI ODU1_TCM5_TIM
2.2.124 TQX Board Alarm List

TN55TQX
ALS_ACTIVE ODU2_PM_AIS OPUFLEX_PLM
B1_EXC ODU2_PM_BDI OTU2_AIS
B1_SD ODU2_PM_DEG OTU2_BDI
BD_STATUS ODU2_PM_LCK OTU2_DEG
BD_LEDTEST ODU2_PM_OCI OTU2_LOF
BEFFEC_EXC ODU2_PM_SSF OTU2_LOM
BUS_ERR ODU2_PM_TIM OTU2_SSF
CLIENT_PORT_PS ODU2_TCMn_AIS OTU2_TIM
CLIENT_PORT_STA_I
NDI ODU2_TCMn_BDI OUT_PWR_HIGH
CLIENT_PROT_NOT-
START ODU2_TCMn_DEG OUT_PWR_LOW
COMMUN_FAIL ODU2_TCMn_LCK PORT_MODULE_OFFLINE
HARD_BAD ODU2_TCMn_LTC PRBS_LSS
HARD_ERR ODU2_TCMn_OCI REMOTE_FAULT
IN_PWR_HIGH ODU2_TCMn_SSF REM_SD
IN_PWR_LOW ODU2_TCMn_TIM REM_SF
J0_MM ODUFLEX_LOFLOM RS_CROSSTR
LASER_MODULE_MIS
MATCH ODUFLEX_PM_AIS R_LOC
LOCAL_FAULT ODUFLEX_PM_BDI R_LOF
LOOP_ALM ODUFLEX_PM_DEG R_LOS
LPT_ACTIVE ODUFLEX_PM_LCK TD
LSR_COOL_ALM ODUFLEX_PM_OCI TEMP_OVER
LSR_INVALID ODUFLEX_PM_SSF TEM_HA
LSR_WILL_DIE ODUFLEX_PM_TIM TEM_LA

OptiX OSN 8800/6800/3800
L_SYNC ODU_SNCP_PS TF
NO_BD_SOFT ODU_SNCP_STA_INDI WAVEDATA_MIS
NO_ELABEL OPU2_CSF WRG_BD_TYPE
NULL_SEND OPU2_PLM
ODU2_LOFLOM OPUFLEX_CSF
TN53TQX
ALS_ACTIVE NULL_SEND OTU2_DEG
B1_EXC ODU2_LOFLOM OTU2_EXC
B1_SD ODU2_PM_AIS OTU2_LOF
BD_LEDTEST ODU2_PM_BDI OTU2_LOM
BD_STATUS ODU2_PM_DEG OTU2_SSF
BEFFEC_EXC ODU2_PM_EXC OTU2_TIM
BUS_ERR ODU2_PM_LCK OUT_PWR_HIGH
CLIENT_PORT_PS ODU2_PM_OCI OUT_PWR_LOW
CLIENT_PORT_STA_I
NDI ODU2_PM_SSF PORT_MODULE_OFFLINE
CLIENT_PROT_NOT-
START ODU2_PM_TIM PRBS_LSS
COMMUN_FAIL ODU2_TCMn_AIS REMOTE_FAULT
HARD_BAD ODU2_TCMn_BDI REM_SD
HARD_ERR ODU2_TCMn_DEG REM_SF
IN_PWR_HIGH ODU2_TCMn_EXC RS_CROSSTR
IN_PWR_LOW ODU2_TCMn_LCK R_LOC
J0_MM ODU2_TCMn_LTC R_LOF
LASER_MODULE_MIS
MATCH ODU2_TCMn_OCI R_LOS
LOCAL_FAULT ODU2_TCMn_SSF TD
LOOP_ALM ODU2_TCMn_TIM TEMP_OVER
LPT_ACTIVE ODU_SNCP_PS TEM_HA
LSR_COOL_ALM ODU_SNCP_STA_INDI TEM_LA

OptiX OSN 8800/6800/3800
LSR_INVALID OPU2_PLM TF
LSR_WILL_DIE OPU2_CSF WAVEDATA_MIS
L_SYNC OPUFLEX_CSF WRG_BD_TYPE
NO_BD_SOFT OTU2_AIS
NO_ELABEL OTU2_BDI
TN52TQX
ALS_ACTIVE ODU2_TCM1_LTC ODU2_TCM6_AIS
B1_EXC ODU2_TCM1_OCI ODU2_TCM6_BDI
B1_SD ODU2_TCM1_SSF ODU2_TCM6_DEG
BD_LEDTEST ODU2_TCM1_TIM ODU2_TCM6_LCK
BUS_ERR ODU2_TCM2_DEG ODU2_TCM6_SSF
CLIENT_PORT_PS ODU2_TCM2_LCK ODU2_TCM6_TIM
CLIENT_PORT_STA_INDI ODU2_TCM2_LTC ODU_SNCP_PS
CLIENT_PROT_NOTSTART ODU2_TCM2_OCI ODU_SNCP_STA_INDI
COMMUN_FAIL ODU2_TCM2_SSF OPU2_PLM
HARD_BAD ODU2_TCM2_TIM OTU2_AIS
HARD_ERR ODU2_TCM3_AIS OTU2_BDI
IN_PWR_HIGH ODU2_TCM3_BDI OTU2_DEG
IN_PWR_LOW ODU2_TCM3_DEG OTU2_LOF
J0_MM ODU2_TCM3_LCK OTU2_LOM
LASER_MODULE_MIS- ODU2_TCM3_LTC OTU2_SSF

MATCH
LOCAL_FAULT ODU2_TCM3_OCI OTU2_TIM
LOOP_ALM ODU2_TCM3_SSF OUT_PWR_HIGH
LPT_ACTIVE ODU2_TCM3_TIM OUT_PWR_LOW
LSR_INVALID ODU2_TCM4_AIS PORT_MODULE_OFF-

LINE
LSR_WILL_DIE ODU2_TCM4_BDI PRBS_LSS

OptiX OSN 8800/6800/3800
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
TN11TQX
ALS_ACTIVE LPT_ACTIVE OUT_PWR_HIGH
B1_EXC LSR_COOL_ALM OUT_PWR_LOW
B1_SD LSR_INVALID PORT_MODULE_OFF-

LINE
BD_LEDTEST LSR_WILL_DIE PRBS_LSS
BD_STATUS NO_BD_SOFT REMOTE_FAULT
BUS_ERR NO_ELABEL REM_SD
CLIENT_PORT_PS ODU2_LOFLOM REM_SF
CLIENT_PORT_STA_INDI ODU2_PM_AIS R_LOC
CLIENT_PROT_NOTSTART ODU2_PM_BDI R_LOF
COMMUN_FAIL ODU2_PM_DEG R_LOS
HARD_BAD ODU2_PM_LCK TD
HARD_ERR ODU2_PM_OCI TEMP_OVER
IN_PWR_HIGH ODU2_PM_SSF TEM_HA

OptiX OSN 8800/6800/3800
IN_PWR_LOW ODU2_PM_TIM TEM_LA
J0_MM ODU_SNCP_PS TF
LASER_MODULE_MIS- ODU_SNCP_STA_INDI WAVEDATA_MIS

MATCH
LOCAL_FAULT OPA_FAIL_INDI WRG_BD_TYPE
LOOP_ALM OPU2_PLM
2.2.125 TSXL Board Alarm List

TN11TSXL
ALS_ACTIVE MS_AIS OUT_PWR_HIGH
B1_EXC NO_BD_SOFT OUT_PWR_LOW
B1_SD NO_ELABEL PORT_MODULE_OFF-

LINE
BD_LEDTEST ODU2_LOFLOM PRBS_LSS
BD_STATUS ODU2_PM_AIS REM_SD
CLIENT_PORT_PS ODU2_PM_BDI REM_SF
CLIENT_PORT_STA_INDI ODU2_PM_DEG RS_CROSSTR
CLIENT_PROT_NOT- ODU2_PM_EXC R_LOC

START
COMMUN_FAIL ODU2_PM_LCK R_LOF
HARD_BAD ODU2_PM_OCI R_LOS
HARD_ERR ODU2_PM_SSF TD
IN_PWR_HIGH ODU2_PM_TIM TEMP_OVER
IN_PWR_LOW ODU_SNCP_PS TEM_HA
J0_MM ODU_SNCP_STA_INDI TEM_LA
LOOP_ALM OPA_FAIL_INDI TF
LSR_COOL_ALM OPU2_MSIM VCAT_LOA
LSR_WILL_DIE OPU2_PLM WRG_BD_TYPE
TN53TSXL

OptiX OSN 8800/6800/3800
ALS_ACTIVE ODU3_TCM1_EXC ODU3_TCM6_AIS
B1_EXC ODU3_TCM2_AIS ODU3_TCM6_BDI
B1_SD ODU3_TCM2_BDI ODU3_TCM6_DEG
BD_LEDTEST ODU3_TCM2_DEG ODU3_TCM6_LCK
BD_STATUS ODU3_TCM2_LCK ODU3_TCM6_LTC
BEFFEC_EXC ODU3_TCM2_LTC ODU3_TCM6_OCI
BUS_ERR ODU3_TCM2_OCI ODU3_TCM6_SSF
CLIENT_PORT_PS ODU3_TCM2_SSF ODU3_TCM6_TIM
CLIENT_PORT_STA_INDI ODU3_TCM2_TIM ODU3_TCM6_EXC
CLIENT_PROT_NOT- ODU3_TCM2_EXC ODU_SNCP_PS

START
COMMUN_FAIL ODU3_TCM3_AIS ODU_SNCP_STA_INDI
HARD_BAD ODU3_TCM3_BDI OPU3_MSIM
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
ODU3_PM_DEG ODU3_TCM4_LTC PORT_MODULE_OFF-

LINE
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

OptiX OSN 8800/6800/3800
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
TN54TSXL
ALS_ACTIVE LOOP_ALM OPU3_PLM
BD_LEDTEST LSR_WILL_DIE PORT_MODULE_OFFLINE
BD_STATUS NO_BD_SOFT REMOTE_FAULT
BUS_ERR NO_ELABEL REM_SF
CLIENT_PORT_PS ODU3_LOFLOM RX_POWER_ABNORMAL
CLIENT_PORT_STA_I
NDI ODU3_PM_AIS R_LOS
CLIENT_PROT_NOT-
START ODU3_PM_BDI TD
COMMUN_FAIL ODU3_PM_DEG TEMP_OVER
HARD_BAD ODU3_PM_LCK TF
HARD_ERR ODU3_PM_OCI WRG_BD_TYPE
LASER_MODULE_MIS
MATCH ODU3_PM_SSF
LOCAL_FAULT ODU3_PM_TIM
2.2.126 USXH Board Alarm List

BUS_ERR NO_BD_SOFT

OptiX OSN 8800/6800/3800
2.2.127 UXCH Board Alarm List

BUS_ERR NO_BD_SOFT
2.2.128 UXCM Board Alarm List

TN52UXCM
BUS_ERR NO_BD_SOFT
TN16UXCM
STORM_CUR_QUENUM_
ALC_ADJUST_FAIL LCS_DAYS_OF_GRACE OVER
ALC_WAIT_ADJUST LCS_EXPIRED SUBRACK_COMM_PS
APS_FAIL LCS_FILE_NOT_EXIST SUBRACK_ID_CONFLICT
APS_INDI LTI SUBRACK_LOOP
SUBRACK_TYPE_MIS-
APS_MANU_STOP MS_APS_INDI_EX MATCH
SWDL_ACTIVATED_TIME
BD_LEDTEST NEBD_XC_DIF OUT
BD_NOT_INSTALLED NESF_LOST SWDL_AUTOMATCH_INH
BD_STATUS NESTATE_INSTALL SWDL_BD_EXCLUDE
SWDL_CHGMNG_NO-
BOOTROM_BAD NODEID_MM MATCH
BUS_ERR NO_BD_SOFT SWDL_COMMIT_FAIL

OptiX OSN 8800/6800/3800
CFCARD_FAILED NO_ELABEL SWDL_INPROCESS
CLK_LOCK_FAIL NTP_SYNC_FAIL SWDL_NEPKGCHECK
CLK_NO_TRACE_MO
DE OOL SWDL_PKGVER_MM
PASSWORD_NEED_CHAN
COMMUN_FAIL GE SWDL_PKG_NOBDSOFT
COM_EXTECC_FULL PATCH_PKGERR SWDL_ROLLBACK_FAIL
CPC_NODE_ID_ERR POWER_FAIL SYNC_C_LOS
DBMS_DELETE PTP_SOURCE_SWITCH SYNC_DISABLE
DBMS_ERROR PTP_TIMESTAMP_ABN SYNC_FAIL
DBMS_PROTECT_MO
DE RTC_FAIL SYNC_F_M_SWITCH
DB_RESTORE_FAIL S1_SYN_CHANGE SYNC_LOCKOFF
DCNSIZE_OVER SECU_ALM SYN_BAD
EXT_SYNC_LOS SEC_RADIUS_FAIL SYSLOG_COMM_FAIL
SERVICE_CAPACITY_EX SYSPARA_CFDB_NO-
EXT_TIME_LOC CEED_LICENSE SAME
FEATURE_WITHOUT_ SERVICE_TYPE_EXCEED
LICENSE _LICENSE TEMP_OVER
SHELF_AREA_POWER_O
HARD_BAD VER TIME_LOCK_FAIL
HARD_ERR SSL_CERT_NOENC TIME_LOS
HSC_UNAVAIL SSM_LOS TIME_NO_TRACE_MODE
K1_K2_M SSM_QL_FAILED WRG_BD_TYPE
K2_M SNCP_FAIL XC_UNSWITCH
2.2.129 UXCT Board Alarm List

BUS_ERR NO_BD_SOFT

OptiX OSN 8800/6800/3800
2.2.130 VA1 Board Alarm List

TN11VA1
BD_LEDTEST NO_BD_PARA SUM_INPWR_LOW
BD_STATUS NO_BD_SOFT TEMP_OVER
COMMUN_FAIL NO_ELABEL VOADATA_MIS
HARD_BAD OPA_FAIL_INDI WAVEDATA_MIS
HARD_ERR SPAN_LOSS_HIGH WRG_BD_TYPE
MODULE_TEMP_OVE SPAN_LOSS_LOW
R
MUT_LOS SUM_INPWR_HI
2.2.131 VA4 Board Alarm List

TN11VA4
BD_LEDTEST NO_BD_PARA TEMP_OVER
BD_STATUS NO_BD_SOFT VOADATA_MIS
COMMUN_FAIL NO_ELABEL WAVEDATA_MIS
HARD_BAD OPA_FAIL_INDI WRG_BD_TYPE
HARD_ERR SPAN_LOSS_HIGH
MODULE_TEMP_OVE SPAN_LOSS_LOW
R
TN12VA4
BD_LEDTEST MUT_LOS VOADATA_MIS
BD_STATUS OPA_FAIL_INDI WAVEDATA_MIS
COMMUN_FAIL SPAN_LOSS_HIGH WRG_BD_TYPE
HARD_BAD SPAN_LOSS_LOW
HARD_ERR TEMP_OVER

OptiX OSN 8800/6800/3800
2.2.132 WMU Board Alarm List

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

TN11WSD9
BD_LEDTEST NO_BD_PARA OMS_SSF
BD_STATUS NO_BD_SOFT OMS_SSF_O
COMMUN_FAIL NO_ELABEL OMS_SSF_P
HARD_BAD OMS_BDI OPA_FAIL_INDI
HARD_ERR OMS_BDI_O TEMP_OVER
IN_PWR_HIGH OMS_BDI_P VOADATA_MIS
IN_PWR_LOW OMS_FDI WAVEDATA_MIS
MODULE_ADJUST_FAI OMS_FDI_O WRG_BD_TYPE

L
MOD_COM_FAIL OMS_FDI_P
MUT_LOS OMS_LOS_P
TN12WSD9/TN13WSD9
BD_LEDTEST MUT_LOS OMS_SSF_O
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
MODULEFILE_UPDATE_F OMS_FDI_O TEMP_OVER

AIL
MODULE_ADJUST_FAIL OMS_FDI_P VOADATA_MIS

OptiX OSN 8800/6800/3800
MODULE_TEMP_OVER OMS_LOS_P WAVEDATA_MIS
MOD_COM_FAIL OMS_SSF WRG_BD_TYPE
2.2.134 WSM9 Board Alarm List

TN11WSM9
BD_LEDTEST MODULE_ADJUST_FAIL OPA_FAIL_INDI
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
TN12WSM9/TN13WSM9
MODULEFILE_UPDATE_FAI OPA_FAIL_INDI
BD_LEDTEST L
BD_STATUS MODULE_ADJUST_FAIL TEMP_OVER
COMMUN_FAIL MOD_COM_FAIL VOADATA_MIS
HARD_BAD MODULE_TEMP_OVER WAVEDATA_MIS
HARD_ERR MUT_TLOS WRG_BD_TYPE
2.2.135 WSMD2 Board Alarm List

BD_LEDTEST MUT_TLOS OMS_SSF_P
BD_STATUS OMS_BDI OPA_FAIL_INDI
COMMUN_FAIL OMS_BDI_O SUM_INPWR_HI
HARD_BAD OMS_BDI_P SUM_INPWR_LOW
HARD_ERR OMS_FDI TEMP_OVER
MODULEFILE_UPDATE_F OMS_FDI_O VOADATA_MIS

AIL
MODULE_ADJUST_FAIL OMS_FDI_P WAVEDATA_MIS
MODULE_TEMP_OVER OMS_LOS_P WRG_BD_TYPE

OptiX OSN 8800/6800/3800
MUT_LOS OMS_SSF_O

TN11WSMD4
BD_LEDTEST MUT_TLOS OMS_SSF_P
BD_STATUS OMS_BDI OPA_FAIL_INDI
COMMUN_FAIL OMS_BDI_O SUM_INPWR_HI
HARD_BAD OMS_BDI_P SUM_INPWR_LOW
HARD_ERR OMS_FDI TEMP_OVER
MODULEFILE_UPDATE_F OMS_FDI_O VOADATA_MIS

AIL
MODULE_ADJUST_FAIL OMS_FDI_P WAVEDATA_MIS
MODULE_TEMP_OVER OMS_LOS_P WRG_BD_TYPE
MUT_LOS OMS_SSF_O
TN12WSMD4
BD_LEDTEST MUT_LOS OMS_SSF
BD_STATUS MUT_TLOS OMS_SSF_O
MODULEFILE_UPDATE_F OMS_FDI SUM_INPWR_LOW

AIL
MODULE_ADJUST_FAIL OMS_FDI_O TEMP_OVER
MODULE_TEMP_OVER OMS_FDI_P VOADATA_MIS
MOD_COM_FAIL OMS_LOS_P WRG_BD_TYPE

OptiX OSN 8800/6800/3800

TN11WSMD9
BD_LEDTEST NO_BD_SOFT OMS_SSF_O
BD_STATUS NO_BD_PARA OMS_SSF_P
COMMUN_FAIL NO_ELABEL OPA_FAIL_INDI
HARD_BAD OMS_BDI SUM_INPWR_HI
HARD_ERR OMS_BDI_O SUM_INPWR_LOW
MODULEFILE_UPDATE_F OMS_BDI_P TEMP_OVER

AIL
MODULE_ADJUST_FAIL OMS_FDI VOADATA_MIS
MODULE_TEMP_OVER OMS_FDI_O WAVEDATA_MIS
MOD_COM_FAIL OMS_FDI_P WRG_BD_TYPE
MUT_LOS OMS_LOS_P
MUT_TLOS OMS_SSF
2.2.138 XCH Board Alarm List

TN52XCH
BUS_ERR NO_BD_SOFT
TN16XCH
ALC_ADJUST_FAI SUBRACK_COMM_PS
L LCS_EXPIRED
ALC_WAIT_ADJUS SUBRACK_ID_CON-
T LCS_FILE_NOT_EXIST FLICT
APS_FAIL SUBRACK_ID_MIS-
LTI MATCH
APS_INDI MS_APS_INDI_EX SUBRACK_LOOP

OptiX OSN 8800/6800/3800
APS_MANUAL_ST SUBRACK_TYPE_MIS-
OP NEBD_XC_DIF MATCH
BD_LEDTEST NESF_LOST SWDL_ACTIVATED_TI

MEOUT
BD_NOT_INSTALL NESTATE_INSTALL SWDL_AUTOMATCH_I

ED NH
BD_STATUS NODEID_MM SWDL_CHGMNG_NO-

MATCH
BOOTROM_BAD NO_BD_SOFT SWDL_BD_EXCLUDE
BUS_ERR NO_ELABEL SWDL_COMMIT_FAIL
CFCARD_FAILED NTP_SYNC_FAIL SWDL_INPROCESS
CLK_NO_TRACE_ OOL SWDL_NEPKGCHECK

MODE
COMMUN_FAIL PASSWORD_NEED_CHANGE SWDL_PKGVER_MM
CPC_NODE_ID_ER PATCH_ACT_TIMEOUT SWDL_PKG_NOBD-

R SOFT
DBMS_DELETE PATCH_DEACT_TIMEOUT SWDL_ROLLBACK_FA

IL
DBMS_ERROR PATCH_PKGERR SYNC_C_LOS
DBMS_PROTECT_ POWER_FAIL SYNC_DISABLE

MODE
DB_RESTORE_FAI RTC_FAIL SYNC_FAIL

L
DCNSIZE_OVER S1_SYN_CHANGE SYNC_F_M_SWITCH
EXT_SYNC_LOS SECU_ALM SYNC_LOCKOFF
EXT_TIME_LOC SEC_RADIUS_FAIL SYN_BAD
FEATURE_WITHO SERVICE_CAPACITY_EXCEED_ SYSLOG_COMM_FAIL

UT_LICENSE LICENSE
HARD_BAD SERVICE_TYPE_EXCEED_LI- SYSPARA_CFDB_NO-

CENSE SAME
HARD_ERR SHELF_AREA_POWER_OVER TEMP_OVER
HSC_UNAVAIL SNCP_FAIL TIME_LOS
K1_K2_M SSM_LOS TIME_NO_TRACE_MO

DE
K2_M SSM_QL_FAILED WRG_BD_TYPE

OptiX OSN 8800/6800/3800
LCS_DAYS_OF_GR STORM_CUR_QUENUM_OVER XC_UNSWITCH

ACE
2.2.139 XCM Board Alarm List

TN52XCM
BUS_ERR NO_BD_SOFT
2.2.140 XCS Board Alarm List

TN11XCS
BD_STATUS HARD_BAD NO_ELABEL
BUS_ERR HARD_ERR TEMP_OVER
TN12XCS
BD_LEDTEST HARD_BAD NO_ELABEL
BD_STATUS HARD_ERR TEMP_OVER
2.2.141 XCT Board Alarm List

BUS_ERR NO_BD_SOFT

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 3 Clearing Common Alarms
3 Clearing Common Alarms
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 optical-
layer 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.
l 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.

OptiX OSN 8800/6800/3800
3.4 BUS_ERR
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

OptiX OSN 8800/6800/3800
3.31 OSC_LOS
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

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, 3.1.1 B1_EXC (OCS)

SLQ16, SLQ64, SLH41, SLO16, or EGSH
Boards other than the SF64, SF64A, SFD64, 3.1.2 B1_EXC (OTN)
SL64, SLD64, SLQ16, SLQ64, SLH41,
SLO16, or EGSH
3.1.1 B1_EXC (OCS)
Description
The B1_EXC is an alarm indicating that the number of B1 bit errors exceeds the specified
threshold. This alarm is reported when the line board detects that the number of regenerator
section bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the B1
byte.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the port on the board.
Parameter 2, Parameter 3 Indicate the path ID.

OptiX OSN 8800/6800/3800
Impact on the System

l When this alarm occurs, the quality of transmitted services has badly deteriorated.
Possible Causes
l Cause 1: The bit error threshold is not proper.
l Cause 2: The ambient environment is abnormal.
l Cause 3: Line performance deteriorates.
l Cause 4: The equipment is not grounded properly
l Cause 5: The local receive board is faulty.
l Cause 6: The peer transmit board is faulty.
l Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
Procedure
Step 1 Cause 1: The bit error threshold is not proper.
1. Check the bit error threshold. If it is low, raise the threshold as required.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The ambient environment is abnormal.

1. Check the ambient temperature, air filter, and heat dissipation. For details, see the methods
of handling the TEMP_OVER alarm.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, check for external
electromagnetic interference sources, such as external electronic equipment, unstable
power supply, lightning, and high-voltage wires. If any of the electromagnetic interference
sources exist, take anti-interference measures.
Step 3 Cause 3: Line performance deteriorates.

1. On the NMS, check whether the transmit optical power of the peer board is within the
specified range.
If... Then...
The transmit optical power of the peer board is out of range Go to Step 6.
The transmit optical power of the peer NE is within the specified Go to the next step.
range
2. On the NMS, check whether the transmit optical power of the local board is within the
specified range.
If... Then...
The transmit optical power of the local board is out of range Go to Step 5.

OptiX OSN 8800/6800/3800
If... Then...
The transmit optical power of the local board is within the Go to the next step.
specified range
3. On the NMS, check whether the receive optical power of the local board is within the
specified range.
If... Then...
The receive optical power of the local Check the fiber ends, fiber connector, and
board is out of range optical cable in turn.
The receive optical power of the local Go to Step 5.

board is within the specified range
4. Check whether the fiber connector is properly connected.
If... Then...
The fiber connector is loose Properly connect the fiber connector. Check
whether the B1_EXC alarm is cleared. If the
alarm persists, go to the next step.
The fiber connector is properly Go to the next step.

connected
5. Check whether the fiber connector is contaminated.
If... Then...
The fiber connector is contaminated Clean the fiber connector.
Check whether the B1_EXC alarm is cleared. If

the alarm persists, go to the next step.
The fiber connector is clean Go to the next step.
6. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm, and
check the optical cable for damage, sheath stripping, aging, fusion, and cut. If the radius is
less than 6 cm, re-roll the pigtail. If any damage, sheath stripping, aging, fusion, or cut is
found on the optical cable, replace it and check whether the B1_EXC alarm is cleared.
7. If the alarm persists, check whether the optical cable matches the optical interface board
in model type. Mismatch in model type may result in low fiber sensitivity, large dispersion,
and signal distortion, which will cause bit errors.
If... Then...
The optical cable does not match the Replace the fiber or line board as required
optical interface board in model type and check whether the B1_EXC alarm is
cleared.

OptiX OSN 8800/6800/3800
If... Then...
The optical cable matches the optical Go to the next step.

interface board in model type
8. If the B1_EXC alarm persists, go to Step 4.
Step 4 Cause 4: The equipment is not grounded properly

1. Ensure that the equipment is properly grounded. For example, ensure that the PGND cable
is properly connected and the cabinet and ground bar are properly connected.
Step 5 Cause 5: The local receive board is faulty.

1. Replace the local optical module or board. If a pluggable optical module is installed on the
board, replace the optical module. If no pluggable optical module is installed on the board,
replace the board.
Step 6 Cause 6: The peer transmit board is faulty.

1. Replace the peer optical module or board. If a pluggable optical module is installed on the
board, replace the optical module. If no pluggable optical module is installed on the board,
replace the board.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, replace the peer cross-
connect and clock board by referring to Step 7.
Step 7 Cause 7: The clock configuration is incorrect, or the clock unit performance deteriorates
1. Check the local and peer clock sources for timing loop or asynchronization. If pointer
adjustment events or alarms, such as the AUPJCHIGH event or the SYN_BAD alarm, are
reported along with the B1_EXC alarm, clear the pointer adjustment events or alarms first.
2. Check whether the B1_EXC alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None.
3.1.2 B1_EXC (OTN)
Description
Excessive errors on the regenerator section (B1). This alarm is generated when the received SDH
signals degrade and the B1 bit errors on the regenerator section exceed the threshold.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
None

The B1 bit errors in the service signals received by a board exceed the B1 bit error threshold 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 not covered in this topic, handle the fault according
to "Handling Procedure" provided in this topic.
Possible Causes
l Cause 1 (reported from the client side): The input signals on the client side contain B1 bit
errors.
l Cause 2 (reported from the client side): The board that reports this alarm is faulty.
l Cause 1 (reported from the WDM side): The receive side of the local station (Station B) is
faulty.
l Cause 2 (reported from the WDM side): The attenuation of the received signals is
excessively high; the fiber or connector is not clean.
l Cause 3 (reported from the WDM side): The transmit side of the opposite station (Station
A) is faulty.
Procedure
l Check the alarm information on the U2000 and record the IDs of the port and channel where
the alarm is generated.
Detects and reports Detects and reports
the B1_EXC alarm the B1_EXC alarm
O O
A F F A
OTU(A) I OTU(B)
D I D
Out-loop M U U M Out-loop
Client side WDM side WDM side Client side
Station A Station B
l Cause 1 (reported from the client side): The input signals on the client side contain B1 bit
errors.

OptiX OSN 8800/6800/3800
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 OTU(A). If the
alarm on OTU(A) persists, the OTU(A) hardware is faulty. See the alarm handling
procedure for cause 2 (reported from the client side).
NOTICE
Configuring a loopback on the board interrupts the services on the board.
2. If the alarm is cleared, the input signals on the client side of the board contain B1 bit
errors. Rectify the fault on the client equipment.
l Cause 2 (reported from 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
modules, module.
The board does not support pluggable Replace the board.

optical modules,
l Cause 1 (reported from the WDM side): The receive side of the local station (Station B) is
faulty.
1. Configure an outloop at the transmit and receive optical ports on the WDM side of
OTU(B). If there is no bit error alarm on the OTU(A), the board at the local station
(Station B) is faulty. Replace the faulty board.
If ... Then ...
modules, module.

optical modules,
NOTICE
2. If OTU(A) has bit error alarms, see the alarm handling procedure for cause 2 (reported
from the WDM side).
l Cause 2 (reported from 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 OTU(A) on the U2000. For the optical power specifications of

OptiX OSN 8800/6800/3800
the specific board, see "Technical Specifications" in the Product Description. For
details, see "Querying Optical Power on the U2000" in the Supporting Tasks.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for Boards"
in the Hardware Description to obtain the manufacturing information of the optical module on
the board.
2. If the transmit optical power of the corresponding optical port on OTU(A) is within
the permitted range, check the attenuation of the transmission link between the
transmitting module of OTU(A) at the opposite station and the receiving module of
OTU(B) at the local station. If the preset attenuation values are excessively large,
correct them so that they are within the permitted range.
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, see "Inspecting and
Cleaning the Fiber-Optic Connectors" in 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
"Replace the Fiber Jumper" in the Parts Replacement. 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 (reported from the WDM side).
l Cause 3 (reported from the WDM side): The transmit side of the opposite station (Station
A) is faulty.
1. Add a pigtail to connect a 5 dB fixed attenuator and the OTU(A) board on the opposite
station and perform a WDM-side hardware loopback. If the alarm on the OTU(A)
board persists, the OTU(A) board is faulty. In this case, replace the board.
If ... Then ...
modules, module.

optical modules,
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A88 The OTU Board Reports the B1_EXC Alarm, And There Are the Difference in
BER Reported by the OTU Board and Test Instrument
l MC-A105 Line Reflection Leads to Inaccurate BER Detection of the SSC6LWX Board,
the Board Reports the B1_EXC Alarm

OptiX OSN 8800/6800/3800
3.2 BEFFEC_EXC
Description
Signal degraded before FEC. Signals sent from the WDM side of the opposite-end OTU have
the FEC function. As a result, before performing signal FEC in the receive direction on the 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 crosses the threshold.
Attribute
Minor Service alarm
Parameters
None

The error tolerance of the system decreases, which may even affect the quality of signals.
Fault Symptom
Table 3-2 lists the fault symptom of 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 Cause 3 of this alarm in the case of multiple
temperature alarm or fan fault alarm, such as wavelengths: The external environment is
TEMP_OVER or FAN_FAIL, within a improper.
certain time.
NOTE
to "Procedure" provided in this topic.
Possible Causes
The possible causes of this alarm in the case of a single wavelength are as follows:
l Cause 1: The input optical power of the OTU board is excessively high or low.
l Cause 2: The settings of the FEC mode of the interconnected OTU boards are different.

OptiX OSN 8800/6800/3800
l Cause 3: The fiber between the OTU board and the multiplexer/demultiplexer board is
faulty.
l Cause 4: An inappropriate DCM is installed.
l Cause 5: The board that reports this alarm or the board at the opposite station is faulty.
The possible causes of this alarm in the case of multiple wavelengths are as follows:
l Cause 1: Fibers in the optical cables between stations or the multiplexing portions inside a
station are faulty.
l Cause 2: The attenuation of the signals during line transmission is excessively high.
l Cause 3: The external environment is improper.
Procedure
Step 1 On the U2000, check the alarm information and record the IDs of the port and channel where
Step 2 Cause 1 of this alarm in the case of a single wavelength: The input optical power of the OTU
board is excessively high or low.
1. Check whether the receive optical power on the U2000 is within the permitted range. For
the optical power specifications of the specific board, see "Technical Specifications" in the
Product Description.
NOTE
See "Querying Optical Module Information" in the Supporting Tasks or "Bar Code for Boards" in
the Hardware Description to obtain the manufacturer 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 OTU boards are different.
1. On the U2000, check the settings of FEC mode of the two interconnected OTU boards. 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, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the Supporting
Tasks.
"Replacing Fiber Jumpers" in the Parts Replacement.

OptiX OSN 8800/6800/3800
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.
Step 6 Cause 5 of this alarm in the case of a single wavelength: The board that reports this alarm or the
board at the opposite station is faulty.
1. If the alarm is reported simultaneously on the IN port of both the OTU(A) and OTU(B)
boards, as shown in the following figure, add a pigtail to connect a 5 dB fixed attenuator
and the OTU(B) board and perform a WDM-side loopback. If the alarm persists, the OTU
(B) board is faulty. If the alarm is cleared, the OTU(B) board is normal but the OTU(A)
board may be faulty.
OUT IN
OTU OTU
2 1
(A) (B)
IN OUT
Station A Station B
2. Release the loopback on the OTU(B) board. Add a pigtail to connect a 5 dB fixed attenuator
and the OTU(A) board on the opposite station and perform a WDM-side hardware
loopback. If the alarm on the OTU(A) board persists, the OTU(A) board is faulty.
3. Replace the faulty board. Check whether the alarm is cleared.
If ... Then ...
modules, module.

optical modules,
Step 7 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, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the Supporting
Tasks.
"Replacing Fiber Jumpers" in the Parts Replacement. If the fibers inside a station are
normal, check the optical cables between stations to rectify the fault.
for cause 2 of this alarm in the case of multiple wavelengths.
Step 8 Cause 2 of this alarm in the case of multiple wavelengths: The attenuation of the signals during
line transmission is excessively high.

OptiX OSN 8800/6800/3800
1. 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 permitted range.
for cause 3 of this alarm in the case of multiple wavelengths.
Step 9 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 unstable, 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. Check whether the alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
Related Cases:
l MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets Close
to the Threshold
l MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm
BEFFEC_EXC Is Detected on the Newly-added LWFS Board
l MC-A80 Intermittent BEFFEC_EXC Alarm at IN/OUT optical interfaces on LWF board
l MC-A237 Dispersion Topology Affects System Performance
l MC-A238 High PMD Affects 40G Services
l MC-A239 Inappropriate Line Optical Power Adjustment Causes Deteriorated 40G
Performance
3.3 BOOTROM_BAD
SF64, SF64A, SFD64, SL64, SLD64, 3.3.1 BOOTROM_BAD (OCS)

Boards other than the SF64, SF64A, SFD64, 3.3.2 BOOTROM_BAD (OTN)
SLO16, or EGSH

OptiX OSN 8800/6800/3800
3.3.1 BOOTROM_BAD (OCS)
Description
The BOOTROM_BAD is an alarm indicating a failure to check the BOOTROM data. This alarm
is reported when the basic or extended BIOS software is damaged on a board.
Attribute
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the BIOS software type.
l 0x01: basic BIOS software

l 0x02: extended BIOS software
0xFF indicates no meaning.

l This alarm does not affect the system or services when the board is operating.
l When this alarm occurs, cold reset or restart will lead to a failure to load the BIOS software.
As a result, the board cannot be started.
Possible Causes
l The extended BIOS software is damaged.
l The basic BIOS software is damaged.
l The board is faulty.
Procedure
Step 1 On the NMS, view the BOOTROM_BAD alarm and determine the type of the damaged BIOS
software based on alarm parameters.

OptiX OSN 8800/6800/3800
If... Then...
The basic BIOS software is damaged Go to Step 2.
The extended BIOS software is Reload the extended BIOS software and check
damaged whether the BOOTROM_BAD alarm is cleared.
Step 2 If the alarm persists, replace the board.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None.
3.3.2 BOOTROM_BAD (OTN)
Description
BOOTROM data check failed. This alarm is generated when the basic or extended BIOS
software of the board is damaged.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the BIOS type. For example, 0x01 indicates the basic BIOS software,
and 0x02 indicates the extended BIOS software.

When powered on again or reset after a power supply failure, the system control board cannot
be normally started.

OptiX OSN 8800/6800/3800
Fault Symptom
None
NOTE
Possible Causes
l Cause 1: The basic BIOS software of the system control board is damaged.
l Cause 2: The extended BIOS software of the system control board is damaged.
l Cause 3: The system control board is faulty.
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 system control board
is damaged.
l Cause 1: The basic BIOS software of the system control board is damaged.
1. Replace the faulty system control board. For details, see "Replacing the SCC Board"
in the Parts Replacement.
assistance.
l Cause 2: The extended BIOS software of the system control board is damaged.
1. Reload the extended BIOS of the system control board.
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 is not cleared after you reload the extended BIOS.
l Cause 3: The system control board is faulty.
1. Replace the faulty system control board. For details, see "Replacing the SCC Board"
in the Parts Replacement.
assistance.
----End
Related Information
None
3.4 BUS_ERR

OptiX OSN 8800/6800/3800
SF64, SF64A, SFD64, SL64, SLD64, 3.4.1 BUS_ERR (OCS)

Boards other than the SF64, SF64A, SFD64, 3.4.2 BUS_ERR (OTN)
SLO16, or EGSH
3.4.1 BUS_ERR (OCS)
Description
The BUS_ERR is an alarm indicating an error in the cross-connect board bus. This alarm is
reported when the cross-connect board detects an exception on the bus from the service board
to the cross-connect board.
Attribute
Critical Equipment alarm
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the bus type.

l 0x00: bus interconnecting the service and cross-connect boards
l 0x01: bus that aggregates the lower-order services on the lower-
order daughter board to the higher-order bus
l 0x02: bus that transmits services to the lower-order bus on the
lower-order daughter board
l 0x03: bus (ingress bus to the chip) that restore higher order
services to the lower-order bus on the lower-order daughter
board
l 0x04: bus (inter-chip bus) that restore higher order services to
the lower-order bus on the lower-order daughter board
l 0x05: bus that interconnects lower-order buses on the lower-
order daughter board
Parameter 2, Parameter 3 Indicate the global logical number of a bus.

l When parameter 1 is 0x00, parameters 2 and 3 indicate the
global logical number of a higher-order bus.
l When parameter 1 is a value other than 0x00, parameters 2 and
3 indicate the logical number of a bus on the lower-order
daughter board.

l When the alarm occurs, the services that traverse over the faulty bus are interrupted or have
bit errors.
l When both the active and standby cross-connect boards have the BUS_ERR alarm but no
severer alarm, such as HARD_BAD, no active/standby switching occurs. When only the
active cross-connect board has the HARD_BAD alarm, services are switched from the
active board to the standby board.
Possible Causes
l Cause 1: The service board does not match the cross-connect board in software version.
l Cause 2: The service board is faulty.
l Cause 3: The cross-connect board is faulty.
l Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
Procedure
Step 1 Cause 1: The service board does not match the cross-connect board in software version.
1. Check whether the service board matches the cross-connect board in software version. For
details, see the software version mapping table in the Supporting Tasks.

OptiX OSN 8800/6800/3800
If... Then...
Both boards match in software version Go to Step 2.
Both boards do not match in software Upgrade either board to the version matching
version that of the other board.
Check whether the BUS_ERR alarm is

cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The service board is faulty.

1. Check whether the cross-connect and service boards are properly installed. If either board
is installed improperly, install it properly and check whether the BUS_ERR alarm is
cleared.
2. If the alarm persists, reset the service board. For details, see the Supporting Tasks. Then,
check whether the BUS_ERR alarm is cleared.
NOTE
You can initially warm reset the service board. If the BUS_ERR alarm persists after the warm reset,
cold reset the board.
3. If the alarm persists, replace the service board. For details, see Parts Replacement. Then,
NOTICE
Cold reset or replace the board only when the services traverse the board are protected.
Otherwise, cold resetting or replacing the board may interrupt services.
4. If the alarm persists, go to Step 3.
Step 3 Cause 3: The cross-connect board is faulty.

1. Reset the alarm-reporting cross-connect board. For details, see the Supporting Tasks. Then,
NOTE
You can initially warm reset the cross-connect board. If the BUS_ERR alarm persists after the warm
reset, cold reset the board.
2. If the alarm persists, replace the alarm-reporting cross-connect board. For details, see the
Parts Replacement. Then, check whether the BUS_ERR alarm is cleared.
NOTICE
Replace the cross-connect board only when at least one standby cross-connect board is
working properly. Otherwise, replacing the board may interrupt services.

OptiX OSN 8800/6800/3800
3. If the alarm persists, follow the preceding operations and reset or replace the other cross-
connect board that has not reported this alarm. Then, check whether the BUS_ERR alarm
is cleared.
Step 4 Cause 4: The backplane bus from the service board to the cross-connect board is faulty.
1. Contact Huawei technical support engineers to check whether the backplane has bent pins.
Replace the backplane if it is damaged.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
----End
Related Information
None.
3.4.2 BUS_ERR (OTN)
Description
Backplane bus error. This alarm is generated when the board detects a backplane bus error.
Attribute
Parameters
Parameter Description
Parameter 1 Indicates the bus type if the cross-connect board reports the alarm.
l 0x00 indicates higher order buses.

l 0x01 to 0x05 indicate lower order buses.
If a service board report the alarm, there is no parameter 1.

OptiX OSN 8800/6800/3800
Parameters 2 and 3 Indicate the logical number of a bus if a cross-connect board reports the
alarm.
If a service board reports the alarm,
l For OptiX OSN 6800, the parameters indicate the number of the faulty
bus.
l For OptiX OSN 8800, the parameters indicate the slot ID of the
working/protection cross-connect board. When parameter 3 is 0x09,
the parameters indicate that the services on the cross-connect board in
slot 9 are abnormal. 0x0a indicates that the services on the cross-
connect board in slot 10 are abnormal.

l 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.
l Services are unavailable or bit errors are generated. For example, ODU1 and GE services
of the OptiX OSN 6800 are affected, ODU1 and ODU0 services of the OptiX OSN 8800
are affected.
Fault Symptom
None
NOTE
Possible Causes
l Cause 1: The OTU broad, tributary or line board is not properly inserted or is faulty.
l Cause 2: The cross-connect board is not properly inserted or is faulty.
l Cause 3: When ASON services are configured, the type of services that are actually received
does not match the service type configured on the board.
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
Procedure
l Cause 1: The OTU board, tributary or line board is not properly inserted or is faulty.
1. Remove and re-insert the board where the alarm is generated.
2. Along the signal flow, remove and re-insert the OTU board, tributary or line board
where the cross-connect service traverses.
3. Check whether the alarm is cleared. If the alarm persists, replace the board.
l Cause 2: The cross-connect board is not properly inserted or is faulty.
1. Remove and re-insert the cross-connect board.

OptiX OSN 8800/6800/3800
2. Check whether the alarm is cleared. If the alarm persists, replace the cross-connect
board.
l Cause 3: When ASON services are configured, the type of services that are actually received
does not match the service type configured on the board.
If... Then...
modules, module.

optical modules,
l Cause 4: The pins are faulty or the bus is faulty on the backplane.
1. On the U2000, perform a cold reset on the faulty board.
2. If the alarm persists, replace the backplane of the subrack. For the detailed operations,
contact Huawei for assistance.
----End
Related Information
Related Cases:
l MC-A144 The TDX Board Reports the BUS_ERR Alarm When Cross-Connections Are
Configured on the Board Because the Service Type of the Board Is Not Set
l MC-A161 The NS2 and TDG Boards Report the BUS_ERR Alarms at the Same Time After
ODUk SNCP Protection Is Configured Because The SCC Board Is Faulty
l MC-A209 Many Boards at A Site Report the BUS_ERR Alarms
l MC-A246 The TN52TQX Board in a Subrack Using the TN1K1AFB Backplane Reports
the BUS_ERR Alarm
3.5 CHAN_LOS
Description
Single-wavelength signal loss or performance (the center wavelength, power, or OSNR) degrade
alarm. The alarm is generated when the multi-channel spectrum analyzer (MCA) board detects
that the original wavelength is lost or the optical spectrum performance degrade amount exceeds
the threshold after it scans the optical spectrum.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

l The services of the related wavelength are unavailable.
l 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 or the shift of the
monitored wavelength exceeds 0.15 nm. For example, in the following figure, 1 needs to
be monitored as configured, but actually 1 is not received. The possible cause is that the
fiber on the WDM side of the OTU1 is not connected.
MCA
?1 M M ?1
OTU1 U OA OA U OTU3
X/ F F X/
?2 D I I D ?2
M U U M
OTU2 OTU4
U OA OA U
X X
Client WDM Client
WDM side
side side side
Station A Station B
l Cause 2: The laser on the board at the opposite station is turned off. For example, the laser
on OTU1 in the preceding figure is turned off.
l 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.
l Cause 4: The attenuation of the multiplexer or OA board interconnected with the MCA is
excessively high.
l Cause 5: The OTU board located before the MCA is faulty. For example, OTU1 in the
preceding figure is faulty.
l Cause 6: The MCA that reports the alarm is faulty.

OptiX OSN 8800/6800/3800
Procedure
l On the U2000, check the alarm information and record the IDs of the port and channel
where the alarm is generated.
l Cause 1: The wavelength that needs to be monitored is not received or the shift of the
monitored wavelength exceeds 0.15 nm.
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 received in the actual network, check the fiber connection
at the upstream stations along the signal flow so that the fiber connection is established
properly.
3. Check the historical and current performance statistics of the MCA board. Verify that
the shift of the monitored wavelength is within 0.15 nm. If the wavelength shift
exceeds the threshold, optimize the performance of related OTU boards or replace
them.
l Cause 2: The laser on the board at the opposite station is turned off.
1. Check whether the laser on the OTU that transmits the wavelength is turned off. If the
laser is turned off, turn on the laser.
l Cause 3: The optical power difference between the monitored wavelengths is excessively
large.
1. Query whether the APE function is configured. If it is, 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 APE function is not configured for the system, manually enable the adjustment
of a single wavelength and adjust the optical power of the wavelengths with
excessively large difference, ensuring that the optical power is flat.
l Cause 4: The attenuation of the multiplexer or OA board interconnected with the MCA is
excessively high.
1. Query the output optical power of the upstream OTU board connected to the
multiplexer board. Check whether the output optical power of the upstream OTU
board is within the permitted range. For the optical power specifications of the specific
board, see "Technical Specifications" in the Product Description.
NOTE
in the Hardware Description to obtain the manufacturer information of the optical module on
the board.
2. Use an optical meter to query the input optical power of the optical port that reports
the alarm, and calculate the output optical power of the upstream multiplexer or OA
board to determine whether the output optical power is within the permitted range.
For the optical power specifications of the specific board, see "Technical

OptiX OSN 8800/6800/3800
Specifications" in 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 board. If the attenuation is very high, decrease the attenuation for
the multiplexer or OA board.
NOTE
Output optical power of the multiplexer or OA board (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 board. For details, see "MON Port Optical
Split Ratio" in the Hardware Description.
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, module.

optical modules,
l 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 port 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. Replace the board.
assistance.
----End
Related Information
None.
3.6 CLIENT_PORT_PS
Description
Client-side 1+1 protection switching. This alarm is generated when a client 1+1 protection group
undergoes protection switching and the active channel is switched from the working channel to
the protection channel.

OptiX OSN 8800/6800/3800
Attribute
Major Communication alarm
Parameters
None

When a client 1+1 protection group undergoes protection switching, services are transiently
interrupted. When this alarm is generated, the working channel of the client 1+1 protection group
might have services that need 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
Protection switching is performed, but there Cause 1: A user delivers an external

is no alarm that can trigger protection switching command such as forced switching
switching. or manual switching.
Protection switching is performed, and the Cause 2: The services on the working channel
board on the working channel reports alarms of the client 1+1 protection group are faulty.
that can trigger protection switching. The active channel automatically switches to
the working channel and the alarm is
reported.
NOTE
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching or manual
switching. Such a command makes the active channel of a client 1+1 protection group
switch from the working channel to the protection channel, triggering the
CLIENT_PORT_PS alarm.
l Cause 2: The services on the working channel of a client 1+1 protection group are faulty
and the active channel automatically switches to the working channel, triggering the
CLIENT_PORT_PS alarm.

OptiX OSN 8800/6800/3800
Procedure
switching.
1. On the U2000, query the switching status 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, deliver an external command to
switch the active channel to the working channel, clearing the alarm.
l Cause 2: The services of the working channel of the client 1+1 protection group are faulty.
The active channel automatically switches to the working channel and the alarm is reported.
1. Query whether the related boards for configuring the protection group have alarms
related to the services, 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
they do, handle the alarms by referring to the alarm handling procedure.
2. If the alarm persists, check whether the attribute of the protection group is
Revertive. If yes, after WTR Time the current channel automatically switches to the
working channel and the alarm clears. If the attribute is Non-Revertive, set it to
Revertive, and after WTR Time the alarm clears.
3. Check whether the alarm clears. If the alarm persists, contact Huawei for assistance.
----End
Related Information
For details, see "Client 1+1 Protection" in the Feature Description.
3.7 COMMUN_FAIL
Board Type Alarm page link
SF64, SF64A, SFD64, SL64, SLD64, 3.7.1 COMMUN_FAIL (OCS)

Boards other than the SF64, SF64A, SFD64, 3.7.2 COMMUN_FAIL (OTN)
SLO16, or EGSH

OptiX OSN 8800/6800/3800
3.7.1 COMMUN_FAIL (OCS)
Description
The COMMUN_FAIL is an alarm indicating that inter-board communication is interrupted. This
alarm is reported when the communication is interrupted between the SCC board and a non-
SCC board.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the path in which the alarm is generated.
l 0x00 0x01: path 1 of the RS485
l 0x00 0x02: path 2 of the RS485
l 0x00 0x03: inter-board Ethernet communication
l 0x00 0x04: inter-subrack Ethernet emergency path

When this alarm occurs, the NE configurations cannot be applied to a board or the board cannot
work. This may disable service configuration and protection switching and affect new services.
Possible Causes
A single board may report the COMMUN_FAIL alarm due to the following causes:
l Cause 1: The service board is being reset.

Multiple boards may report the COMMUN_FAIL alarm due to the following causes:
l Cause 1: The AUX or SEI board is faulty.

l Cause 2: The SCC or cross-connect board is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Cause 1: The service board is being reset.
1. View the service board indicator to determine whether the board is being reset. For details,
see the Hardware Description. Alternatively, query historical resets of the board. For
details, see the Supporting Tasks.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the COMMUN_FAIL alarm is cleared.
The board is not being reset Go to Step 2.

1. Replace the alarm-reporting service board. For details, see the Parts Replacement. Then,
check whether the COMMUN_FAIL alarm is cleared.
2. If the alarm persists, contact Huawei technical support engineers to handle the alarm.
Step 3 Cause 1: The AUX or SEI board is faulty.

1. Remove and insert the AUX and SEI boards and check whether the COMMUN_FAIL
alarm is cleared.
2. If the alarm persists, replace the AUX or SEI board. For details about how to replace the
AUX board, see the Parts Replacement. Then, check whether the COMMUN_FAIL alarm
is cleared.
Step 4 Cause 2: The SCC or cross-connect board is faulty.

1. Remove and insert the active SCC or active cross-connect board and check whether the
COMMUN_FAIL alarm is cleared.
2. If the alarm persists, replace the active SCC or active cross-connect board. For details about
how to replace the active SCC board, see the Parts Replacement. For details about how to
replace the active cross-connect board, see the Parts Replacement. Then, check whether
the COMMUN_FAIL alarm is cleared.
----End
Related Information
None.
3.7.2 COMMUN_FAIL (OTN)
Description
Inter-board communication failure. This alarm is generated when the communication between
the system control board and other boards is interrupted.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Parameter 1 Indicates the optical port number and the value is fixed at 0x01.
Parameters 2 and 3 Indicates the ID of the channel where the alarm is generated. For example,
l 0x00 0x01 indicates RS485 path 1.
l 0x00 0x03 indicates inter-board communication.
l 0x00 0x04 indicates the Ethernet emergency channel between
subracks.
l 0x00 0x05 indicates the SPI communication failure between the
system control board and AUX board.

After the alarm is generated, configuration data fails to be applied to other boards or other boards
cannot function properly. The service configuration or protection switching may fail or the
package loading may roll back abnormally. As a result, new services become abnormal.
Fault Symptom
Table 3-7 lists the fault symptom for the COMMUN_FAIL alarm.

OptiX OSN 8800/6800/3800
Table 3-7 Fault symptom for the COMMUN_FAIL alarm
Fault Symptom Cause
A single board l The board also reports Cause 1 (reported on a single board):
reports the the BD_STATUS The board is in the cold reset or warm
COMMUN_FAIL alarm (only when the reset state.
alarm. board is in the cold reset
The alarm parameter state).
is 0x01 0x00 0x03. 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. Cause 3 (reported on a single board):

The board is faulty.
A single board No other symptoms occur. Cause 3 (reported on a single board):

reports the The board is faulty.
COMMUN_FAIL
alarm.
The alarm parameter
is 0x01 0x00 0x01 or
0x01 0x00 0x02.
The system control The network cables for Cause 2 (reported on a single board):
board of a slave cascading subracks are The network cables for cascading
subrack reports the self-made network cables subracks do not meet the requirements.
COMMUN_FAIL rather than standard
alarm. straight-through cables
The alarm parameter with all eight cores being
is 0x01 0x00 0x04. used.
Multiple boards l The standby system Cause 1 (reported on multiple boards):

report the control board does not For OptiX OSN 6800 and OptiX OSN
COMMUN_FAIL report the 3800: The AUX board is faulty. For
alarm. COMMUN_FAIL OptiX OSN 8800: The EFI1 or EFI2
The alarm parameter alarm. board is faulty.
is 0x01 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.

OptiX OSN 8800/6800/3800
Fault Symptom Cause
l The boards that report Cause 2 (reported on multiple boards):

the COMMUN_FAIL The settings of the DIP switches of the
alarm are housed in subracks are incorrect or the subracks
slave subracks. are cascaded inappropriately.
l The
SUBRACK_LOOP
alarm is generated on
the NE, or the
SUBRACK_ID_CON-
FLICT or
SUBRACK_ID_MIS-
MATCH alarm is
generated in the
housing subracks of the
boards that report the
COMMUN_FAIL
alarm.
l The active and standby Cause 3 (reported on multiple boards):

system control boards The system control board or cross-
report the connect board is faulty.
COMMUN_FAIL
alarm at the same time.
l The active system
control board also
reports alarms such as
HARD_BAD and
BD_STATUS,
indicating abnormal
equipment status.
Multiple boards l The cross-connect Cause 3 (reported on multiple boards):

report the board reports the The system control board or cross-
COMMUN_FAIL COMMUN_FAIL connect board is faulty.
alarm. alarm.
The alarm parameter l The cross-connect
is 0x01 0x00 0x01 or board also reports
0x01 0x00 0x02. alarms such as
BD_STATUS,
indicating abnormal
equipment status.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
The possible causes of the COMMUN_FAIL alarm reported on a single board are as follows:
l Cause 1 (reported on a single board): The board is in the cold reset or warm reset state.
l Cause 2 (reported on a single board): The network cables for cascading subracks do not
meet the requirements.
l Cause 3 (reported on a single board): The board is faulty.
The possible causes of the COMMUN_FAIL alarm reported on multiple boards are as follows:
l Cause 1 (reported on multiple boards): 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 system control board does not report this alarm.
l Cause 2 (reported on multiple boards): The settings of the DIP switches of the subracks are
incorrect or the subracks are cascaded inappropriately.
l Cause 3 (reported on multiple boards): The system control board or cross-connect board is
faulty.
NOTE
If the active system control board is faulty, the active system control board, standby system control
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 cross-
connect board and service boards report the COMMUN_FAIL alarm at the same time.
Procedure
l On the U2000, query the alarm to determine the boards that report the alarm and
corresponding alarm parameters.
l Cause 1 (reported on a single board): The board is in the cold reset or warm reset state.
1. View the alarm indicators on the board to check whether the board that reports this
alarm is in the warm reset or cold reset state. If it is, wait for 5 minutes and 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 (reported on a single board).
l Cause 2 (reported on a single board): 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. Check whether the alarm is cleared.
2. If the alarm persists, see cause 3 (reported on a single board).
l Cause 3 (reported on a single board): The board is faulty.
1. Replace the board that reports the alarm. Replace the board.
assistance.
l Cause 1 (reported on multiple boards): For OptiX OSN 6800 and OptiX OSN 3800: The
AUX board is faulty. For OptiX OSN 8800: The EFI1 or EFI2 board is faulty..

OptiX OSN 8800/6800/3800
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. Remove and re-insert the board. For details, see "Removing
Boards" and "Inserting Boards" in the Quick Installation Guide of the applicable
equipment.
2. Check whether the alarm is cleared. If the alarm persists, replace the AUX board. For
details, see "Replacing the AUX Board" in the Parts Replacement.
3. Check whether the alarm is cleared. If the alarm persists, see cause 2 (reported on
multiple boards).
For OptiX OSN 8800: The EFI1 or EFI2 board is faulty.
1. Check whether the EFI1 or EFI2 board also reports alarms such as BD_STATUS,
indicating abnormal board status. Remove and re-insert the board. For details, see
"Removing Boards" and "Inserting Boards" in the Quick Installation Guide of the
applicable equipment.
2. Check whether the alarm is cleared. If the alarm persists, replace the EFI1 or EFI2
board. For details, see "Replacing the EFI Board" in the Parts Replacement.
multiple boards).
l Cause 2 (reported on multiple boards): 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, clear these alarms in
advance.
multiple boards).
l Cause 3 (reported on multiple boards): The system control board or cross-connect board is
faulty.
1. Check whether the active system control board or active cross-connect board also
reports the BD_STATUS and HARD_BAD alarms. Remove and re-insert the board.
2. Check whether the alarm is cleared. If the alarm persists, Replace the board.
assistance.
l If you deliver configuration to the board when the alarm is present on the board, the board
configuration will differ from the NE configuration after the alarm is cleared. When this
occurs, perform a warm reset on the board to ensure synchronization between the board
configuration and NE configuration.
----End
Related Information
Related Cases:
l MC-A191 How to Clear the COMMUN_FAIL Alarm on the OptiX OSN 6800
l MC-A197 High Ambient Temperature Causes the SCC Board on the OptiX OSN 8800
Repeatedly Reports Transient COMMUN_FAIL Alarms

OptiX OSN 8800/6800/3800
l MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report

Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
l MC-A223 When a Self-Made Network Cable Is Used, the OptiX OSN 6800 Reports the
COMMUN_FAIL Alarm
l MC-A224 The Network Cable at the COM Port on the EFI Board of the OptiX OSN 6800
Subrack Is Incorrectly Connected. Consequently, All the Boards on the OptiX OSN 6800
Subrack Report the COMMUN_FAIL Alarms
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.
Attribute
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.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1: The fiber between the access equipment and the optical port on the client side of
the board is faulty.
l Cause 2: The access equipment is faulty.
l Cause 3: The board hardware is faulty.
Procedure
l Cause 1: The fiber between the access equipment and the optical port on the client side of
the board is faulty.

OptiX OSN 8800/6800/3800
1. Check whether the attenuation of the fiber between the input equipment and the port
on the client side of the board is overlarge, and whether the fiber is aged or loose. If
it is, clean the fiber connector or replace the fiber jumper.
2. Check whether this alarm is cleared. If the alarm persists, see the alarm handling
l Cause 2: The access equipment is faulty.
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 board is faulty. In this case,
replace the board.
If ... Then ...
modules, module.
The board does not support pluggable Replace the faulty board. Replace the
optical modules, board.
2. 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.
l Cause 3: The board hardware is faulty.
1. Replace the faulty board.
If ... Then ...
modules, module.
2. If the alarm persists, contact Huawei for assistance.
----End
Related Information
None.
3.9 EX_ETHOAM_CC_LOS
SF64, SF64A, SFD64, SL64, SLD64, 3.9.1 EX_ETHOAM_CC_LOS (OCS)


OptiX OSN 8800/6800/3800
Boards other than the SF64, SF64A, SFD64, 3.9.2 EX_ETHOAM_CC_LOS (OTN)
SLO16, or EGSH
3.9.1 EX_ETHOAM_CC_LOS (OCS)
Description
The EX_ETHOAM_CC_LOS is an alarm indicating that a periodical continuity check message
(CCM) is lost. This alarm is reported when a sink maintenance point has not received a CCM
from the source maintenance point within 3.5 times of the specified continuity check (CC)
period. This period has started since the sink maintenance point enabled the timer to periodically
check the source-sink link after receiving the first CCM.
Attribute
Critical Communication alarm
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the VLAN ID for the local maintenance point.
Parameter 3 Indicates the level of the local maintenance point.
Parameters 4 to 7 Indicate the ID of the remote maintenance point.
Parameters 8 to 11 Indicate the ID of the local maintenance point.

When this alarm occurs, a unidirectional continuity fault occurs on the source-sink link.
Possible Causes
l Software or hardware faults occur between the source and sink maintenance points.

OptiX OSN 8800/6800/3800
l Services are blocked or interrupted between the source and sink maintenance points.
Procedure
Step 1 View this alarm on the NMS and determine the ID of the maintenance point that generates the
alarm.
Step 2 Query the information about the maintenance point.
Step 3 Perform the loopback (LB) or linktrace (LT) test on the source and sink maintenance points to
locate source-sink faults.
Step 4 Check the involved software, hardware, and traffic and restore the faulty services. Then, you
can perform a loopback test to check whether the EX_ETHOAM_CC_LOS alarm is cleared.
----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
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
Parameters

OptiX OSN 8800/6800/3800
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 1 bytes, 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:
l Cause 1: A software or hardware failure occurs in the services from the source maintenance
point to the sink maintenance point.
l Cause 2: Service congestion or service interruption occurs between the source maintenance
point and the sink maintenance point.
Procedure
l 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.
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.

OptiX OSN 8800/6800/3800
assistance.
----End
Related Information
None.
3.10 FC_LINK_ERR
Description
The FC_LINK_ERR alarm indicates an FC service link failure. This alarm is generated when
the FC link is faulty.
Attribute
Parameters
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.

OptiX OSN 8800/6800/3800
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, including,
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-9 lists the fault symptom for the FC_LINK_ERR alarm.
Table 3-9 Fault symptom for the FC_LINK_ERR alarm
Fault Symptom Cause
The WDM side of the opposite board may Cause 1: The WDM side of the opposite OTU
report an R_LOS, R_LOF, OTUk_LOF, reports an R_LOS, R_LOF, OTUk_LOF,
OTUk_LOM, or OTUk_AIS alarm. OTUk_LOM, or OTUk_AIS alarm. (The
value of parameter 1 is 0x01.)
NOTE
Possible Causes
l 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.)
l 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.)
l Cause 3: The type or the time sequence of the services on the board is configured
improperly.

OptiX OSN 8800/6800/3800
l 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.
l Cause 5: The board is faulty (the value of parameter 2 is 0x03 or 0x04).
l Cause 6: The client equipment is faulty (the value of parameter 2 is 0x02).
Procedure
l Check the information of this alarm on the U2000. Record the parameters of this alarm.
l 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.)
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.
l 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.
l 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. Replace the board.
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. 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.
l 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.
1. Check whether the service type that the client-side optical module on the board is the
same as 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.

OptiX OSN 8800/6800/3800
If ... Then ...
modules, module.

optical modules,
2. If the alarm persists, check whether the fiber type supported by the client-side optical
module is the same as the type of the connected fiber. If not, replace the board or the
fiber.
l 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, module.

optical modules,
2. If the alarm persists, the OTU board at the opposite station may be faulty. In this case,
replace the faulty board.
l 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.
assistance.
----End
Related Information
None.
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.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

Fault Symptom
Table 3-10 lists the fault symptom for the FC_SYNC_LOS alarm.
Table 3-10 Fault symptom for the FC_SYNC_LOS alarm
Fault Symptom Cause
The board reports an OUT_PWR_HIGH or Cause 2: The transmit optical power is

OUT_PWR_LOW alarm. abnormal.
NOTE
Possible Causes
The possible causes of the FC_SYNC_LOS alarm are as follows:
l Cause 1: The rate of the services to be received mismatches the rate of the services that are
actually received.
l Cause 2: The transmit optical power is abnormal.
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 port on the board can be set or queried
on the U2000. For details, see "Querying and Setting the Service Type on the Client
Side of a Board" in the Supporting Tasks.

OptiX OSN 8800/6800/3800
l 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 permitted range. For the optical power specifications of the specific board,
see "Technical Specifications" in 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.
assistance.
----End
Related Information
None.
3.12 IN_PWR_HIGH
SF64, SF64A, SFD64, SL64, SLD64, 3.12.1 IN_PWR_HIGH (OCS)

Boards other than the SF64, SF64A, SFD64, 3.12.2 IN_PWR_HIGH (OTN)
SLO16, or EGSH
3.12.1 IN_PWR_HIGH (OCS)

Description
The IN_PWR_HIGH is an alarm indicating a high receive optical power. This alarm is reported
when a board detects that the actual receive optical power exceeds the specified upper threshold.
Attribute
Parameters
None.

OptiX OSN 8800/6800/3800

When this alarm occurs, bit errors occur in the services on the optical port. In addition, high
receive optical power will damage the laser.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The transmit optical power is high at the peer end.
l Cause 3: The alarm-reporting board is faulty.
Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board.
2. Check whether the optical power threshold is set properly. If the optical power threshold
is improperly set, reset Input Power Reference Lower Threshold and Input Power
Reference Upper Threshold based on board receiver sensitivity or optical-power overload
indicators.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The transmit optical power is high at the peer end.
1. On the NMS, check whether the transmit optical power of the peer board connected to the
local alarm-reporting board is above the specified upper threshold, or whether the peer
board reports the OUT_PWR_HIGH alarm.
If... Then...
The transmit optical power is above the specified upper Go to the next step.
threshold
The transmit optical power is proper Go to Step 3.
2. Replace the optical module if it is pluggable on the peer board. Replace the board if the
optical module is unpluggable.
3. Check whether the IN_PWR_HIGH alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 3: The alarm-reporting board is faulty.

1. If the receive optical power of the alarm-reporting board is proper, this board may be faulty.
In this case, replace the board.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
3.12.2 IN_PWR_HIGH (OTN)

Description
Input optical power being too high. This alarm is generated when the input optical power is
higher than the upper threshold of the input optical power.
Attribute
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 (reported from the client side): The input optical power is excessively high, and
the attenuation configured is insufficient.
l Cause 1 (reported from the WDM side): The output optical power of the board in the
upstream station is excessively high.
l Cause 2 (reported from the WDM side): The board that reports this alarm is faulty.
Procedure
l Cause 1 (reported from the client side): The input optical power is excessively high, and
the attenuation configured is insufficient.
1. 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 permitted range. For the optical power specifications of the specific board, see

OptiX OSN 8800/6800/3800
"Technical Specifications" in 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
permitted range. If the input optical power is abnormal, increase the attenuation so
that the input optical power is within the permitted range.
NOTE
the board.
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, module.

optical modules,
assistance.
l Cause 1 (reported from 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" in 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 along the reverse signal flow on the U2000. If the input and
output optical power of the upstream board exceeds the permitted 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 permitted range, whereas
the output optical power is abnormal, the upstream board may be faulty. Replace the
board.
If ... Then ...
modules, module.

optical modules,

OptiX OSN 8800/6800/3800
l Cause 2 (reported from the WDM 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, module.

optical modules,
assistance.
l 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.
Related Cases:
l MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
l MC-A97 The Optical Amplifier Reports the IN_PWR_HIGH Alarm Because of Optical
Power Reflection
l MC-A194 A Malfunctioning VA1 Board Causes Abnormal Optical Power, The NS2
Boards Reports IN_PWR_HIGH Alarms For Three Times
3.13 IN_PWR_LOW
SF64, SF64A, SFD64, SL64, SLD64, 3.13.1 IN_PWR_LOW (OCS)

Boards other than the SF64, SF64A, SFD64, 3.13.2 IN_PWR_LOW (OTN)
SLO16, or EGSH

OptiX OSN 8800/6800/3800
3.13.1 IN_PWR_LOW (OCS)
Description
The IN_PWR_LOW is an alarm indicating a low receive optical power. This alarm is reported
when a board detects that the actual receive optical power exceeds the specified lower threshold.
Attribute
Parameters
None.

When this alarm occurs, plenty of bit errors occur in the received signals, which affects service
receiving.
Possible Causes
l Cause 1: The optical power threshold is not set properly.
l Cause 2: The fiber connector is loose or contaminated.
l Cause 3: The transmit optical power is low at the peer end.
l Cause 4: The alarm-reporting board is faulty.
Procedure
Step 1 Cause 1: The optical power threshold is not set properly.
1. Query the optical-module details for the alarm-reporting board.
2. Check whether the optical power threshold is set properly. If the optical power threshold
is improperly set, reset Input Power Reference Lower Threshold and Input Power
Reference Upper Threshold based on board receiver sensitivity or optical-power overload
indicators.
3. Check whether the IN_PWR_LOW alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The fiber connector is loose or contaminated.

1. Verify that the fiber connector is properly connected. Then, check whether the
IN_PWR_LOW alarm is cleared.
2. If the alarm persists, check whether the fiber connector is contaminated.
Step 3 Cause 3: The transmit optical power is low at the peer end.

OptiX OSN 8800/6800/3800
1. Replace the optical module if it is pluggable on the peer board. Replace the board if the
optical module is unpluggable.
Step 4 Cause 4: The alarm-reporting board is faulty.

1. If the receive optical power of the alarm-reporting board is proper, this board may be faulty.
In this case, replace the board.
----End
Related Information
None.
3.13.2 IN_PWR_LOW (OTN)
Description
Input optical power being too low. The alarm is generated when the input optical power is smaller
than the lower threshold of the input optical power.
Attribute
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:

OptiX OSN 8800/6800/3800
l Cause 1 (reported from the client side): The fiber connector is dirty, and the fiber jumper
is over-bent, damaged or aged.
l Cause 2 (reported from the client side): The attenuation of the attenuator attached to the
optical port on the board that reports this alarm is excessively high.
l Cause 1 (reported from the WDM side): The fiber connector is dirty, and the fiber jumper
l Cause 2 (reported from the WDM side): The attenuation of the attenuator attached to the
optical port on the board that reports this alarm is excessively high.
l Cause 3 (reported from 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.
l Cause 4 (reported from the WDM side): The attenuation in the transmission of the optical
signals is excessively high and the compensation is insufficient.
l Cause 5 (reported from the WDM side): The board that reports this alarm is faulty.
Procedure
the alarm is generated. On the U2000, check whether the input optical power of the board
where the alarm is reported is within the permitted range.
l Cause 1 (reported from the client side): The fiber connector is dirty, and the fiber jumper
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 permitted range. For the optical
power specifications of the specific board, see "Technical Specifications" in the
NOTE
See "Querying Optical Module Information" in the Supporting Tasks to obtain the manufacturer
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, see "Inspecting
and Cleaning the Fiber-Optic Connectors" in 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 Replacing Fiber Jumpers.
l Cause 2 (reported from 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 the attenuator with
a suitable attenuator. For details, see "Adjusting, Replacing, Adding and Removing
Attenuator" in the Supporting Tasks.

OptiX OSN 8800/6800/3800
1. If the alarm persists, replace the board that reports the alarm.
If ... Then ...
modules, module.

optical modules,
assistance.
l Cause 1 (reported from the WDM side): The fiber connector is dirty, and the fiber jumper
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 permitted range. For the optical
power specifications of the specific board, see "Technical Specifications" in the
NOTE
See "Querying Optical Module Information" in the Supporting Tasks to obtain the manufacturer
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, see "Inspecting
and Cleaning the Fiber-Optic Connectors" in 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 replacing fiber jumpers.
l Cause 2 (reported from the WDM side): The attenuation of the attenuator attached to the
optical port on the board that reports the alarm is excessively high.
1. 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 the attenuator with a suitable attenuator.
For details, see "Adjusting, Replacing, Adding and Removing Attenuator" in the
Supporting Tasks.
l Cause 3 (reported from 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 turned off, turn on
it on the U2000.
2. Check whether the alarm is cleared. If the alarm persists, check whether an optical
attenuator with excessively high attenuation is attached to the transmit optical port on
the board at the opposite station. If it is, decrease the attenuation to a proper value or
replace the optical attenuator so that the output optical power of the opposite board is

OptiX OSN 8800/6800/3800
normal. For details, see "Adjusting, Replacing, Adding and Removing Attenuator" in
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.
l Cause 4 (reported from the WDM side): The attenuation in the transmission of the optical
signals is excessively high and the compensation is insufficient.
1. Query the input and output optical power of the boards in the upstream direction of
the OTU at the local station along the reverse signal flow on the U2000. Locate the
board with the excessively low optical power and adjust the input optical power of
the board to a proper value. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.
2. Check the input and output optical power of the upstream stations one by one along
the reverse 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, or 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.
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.
If ... Then ...
modules, module.

optical modules,
2. If the alarm persists, contact Huawei for assistance.

l 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:

OptiX OSN 8800/6800/3800
l MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm

l MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
l MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some
Wavelengths Report the IN_PWR_LOW Alarm
l MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
l MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW
Alarm Reported by the OTU Board
l MC-A217 An IN_PWR_LOW Alarm Is Reported After an Optical-Layer ASON Service
Is Configured on the ASON OptiX OSN 6800 NE
3.14 INTRA_OTU_PS
Description
Intra-board 1+1 protection switching. This alarm is generated when an intra-board 1+1
protection group undergoes protection switching in which the active channel switches from the
working channel to the protection channel.
Attribute
Parameters
None

When an intra-board 1+1 protection group undergoes protection 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-13 lists the fault symptoms for the INTRA_OTU_PS alarm.
Table 3-13 Fault symptoms for the INTRA_OTU_PS alarm
Fault Symptom Cause


OptiX OSN 8800/6800/3800
Fault Symptom Cause
Protection switching is performed, and the Cause 2: The services of the working channel
board on the working channel reports alarms of the intra-board 1+1 protection group are
that can trigger protection switching. faulty. The active channel automatically
switches to the protection channel and the
alarm is reported.
NOTE
Possible Causes
switching. Such a command makes the active channel of the intra-board 1+1 protection
group switch from the working channel to the protection channel. Therefore, the alarm is
reported.
l Cause 2: The services on the working channel of the intra-board 1+1 protection group are
faulty. The active channel automatically switches to the protection channel and the alarm
is reported.
Procedure
switching.
state is forced switching or manual switching, check whether the external switching
switch the active channel to the working channel to clear the alarm.
l Cause 2: The services on the working channel of the intra-board 1+1 protection group are
faulty. The active channel automatically switches to the protection channel and the alarm
is reported.
1. Query whether alarms related to the services are reported on the boards in the
protection group, 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, B1_EXC, IN_PWR_HIGH, IN_PWR_LOW,
ODUk_PM_DEG, ODUk_PM_EXC, OTUk_DEG, OTUk_EXC. If there are such
alarms, handle the alarms by referring to the alarm handling procedure.
Revertive. If it is, the active channel automatically switches to the working channel
and the alarm clears after WTR Times. If the attribute is Non-Revertive, set it to
Revertive, The alarm clears after WTR Times.

OptiX OSN 8800/6800/3800
assistance.
----End
Related Information
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 inserted into an optical port mismatches the type
of optical port.
Attribute
Parameters
None

Services cannot be properly received or transmitted and even will be interrupted.
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.
Procedure
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.

OptiX OSN 8800/6800/3800
1. Check whether the optical module inserted into the optical port matches the type of
the optical port.
2. If they mismatch, replace the optical module with another one of the right type.
3. Check whether this alarm is cleared. If the alarm persists, contact Huawei for
assistance.
----End
Related Information
None.
3.16 LINK_ERR
SF64, SF64A, SFD64, SL64, SLD64, 3.16.1 LINK_ERR (OCS)

Boards other than the SF64, SF64A, SFD64, 3.16.2 LINK_ERR (OTN)
SLO16, or EGSH
3.16.1 LINK_ERR (OCS)

Description
The LINK_ERR is an alarm indicating data link errors. This alarm is reported when connections
are incorrect and port negotiation fails on an Ethernet.
Attribute
Parameters
None.

When the alarm occurs during data transmission, the network port negotiation fails. The services
cannot be received and thus the services are interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The transmit and receive ports work in different modes.
l Cause 2: Ethernet boards at both ends have different optical modules, or the types of the
two optical modules do not match those of the fibers connected to them.
l Cause 3: The fibers or cables connected to the Ethernet ports fail.
l Cause 4: The board is faulty.
Procedure
Step 1 View the alarm on the NMS, and determine the board that reports the alarm and the ID of the
port that reports the alarm according to alarm parameters.
Step 2 Cause 1: The transmit and receive ports work in different modes.
1. Check whether the transmit and receive ports work in the same mode. If they work in
different modes, for example, a port works in autonegotiation mode while the other port
works in non-autonegotiation mode, configure the working mode to keep its consistency
between both ports. in the Configuration Guide
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: Ethernet boards at both ends have different optical modules, or the types of the two
optical modules do not match those of the fibers connected to them.
1. Check whether the Ethernet boards at both ends have the same optical module. If they have
different optical modules, such as single- and multi-mode optical modules, replace the
optical module on either board to keep its consistency. If the optical module on the board
is pluggable, replace the optical module. For details, see the Parts Replacement.
2. Then, check whether the LINK_ERR alarm is cleared. If the alarm persists, check whether
the types of the two optical modules match those of the fibers connected to them. If the
type of an optical module does not match that of its fiber, for example, a single-mode fiber
is connected to a multi-mode optical module, replace the optical module or fiber to keep
the type consistency between them.
Step 4 Cause 3: The fibers or cables connected to the Ethernet ports fail.
1. Check whether the fibers or cables are properly connected to the Ethernet ports. If the fibers
or cables are improperly connected or even fail, re-connect or replace them.
Step 5 Cause 4: The board is faulty.

1. Use a network cable to loop back signals on the Ethernet port that reports the alarm. Then,
check whether the LINK_ERR alarm is cleared.
If... Then...
The alarm is cleared Replace the peer board. For details, see Parts Replacement.
The alarm persists Replace the local board. For details, see Parts Replacement.

OptiX OSN 8800/6800/3800
2. Check whether the LINK_ERR alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End
Related Information
None.
3.16.2 LINK_ERR (OTN)
Description
Incorrect data link. This alarm is generated when the link status of Ethernet data ports is down.
Attribute
Parameters
None

When the link status of Ethernet ports is down, a valid link cannot be created between the two
data ports and the data services are interrupted.
Fault Symptom
Table 3-15 lists the fault symptom for the LINK_ERR alarm.
Table 3-15 Fault symptom for the LINK_ERR alarm
Fault Symptom Cause
An IN_PWR_HIGH or IN_PWR_LOW Cause 3: The input optical power of the two

alarm may be generated on both interconnected Ethernet ports is excessively
interconnected boards. high or low.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
l Cause 2: The settings of the auto-negotiation mode of the two interconnected Ethernet ports
are inconsistent. For example, one port is in auto-negotiation mode but the other is in non-
negotiation mode.
l Cause 3: The input optical power of the two interconnected Ethernet ports is excessively
high or low.
l Cause 4: The fiber or cable that connects the two Ethernet ports fails.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Therefore, the types of fibers that the two optical modules can be connected
to are inconsistent.
l Cause 6: The data equipment on the client side is faulty.
l Cause 7: The board that reports this alarm is faulty.
Procedure
the alarm is reported.
l Cause 1: The service type of the client equipment mismatches the service type of the
interconnected OTU.
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 they mismatch, change the
service type of the corresponding port on the board or replace the board with another
board that matches the service type.
NOTE
Before changing the service type of the port, make sure that the optical cross-connections
configured on the board are in deactivation state.
l 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.
l 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 permitted range. For the optical power specifications of the specific board,
see "Technical Specifications" in the Product Description.

OptiX OSN 8800/6800/3800
NOTE
the board.
2. If the input optical power is abnormal, see the handling procedures for the
IN_PWR_HIGH or IN_PWR_LOW alarm.
l 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 is properly
connected. If it is not properly connected, reconnect or replace the fiber or cable.
l Cause 5: The optical module types of the two interconnected Ethernet boards are
inconsistent. Therefore, the types of fibers that the two optical modules can be connected
to are inconsistent.
1. Check whether the types of the optical modules on two interconnected boards are
consistent. If they are inconsistent, replace the boards or optical modules to ensure the
optical module type consistency.
If ... Then ...
modules, module.

optical modules,
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 they are inconsistent,
replace the board whose optical module type does not match the fiber board.
l Cause 6: The data equipment on the client side is faulty.
side of the board. If the alarm persists, the OTU at the local station is faulty. For details,
see the alarm handling procedure for cause 7.
2. If the alarm is cleared, the data equipment on the client side is faulty. In this case,
rectify the fault on the data equipment.
l Cause 7: The board that reports the alarm is faulty.
1. Perform a cold reset on the faulty board on the U2000.

OptiX OSN 8800/6800/3800
If ... Then ...
modules, module.

optical modules,
assistance.
----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.
l MC-A102 The LBE, LDG and LQG Boards Report the LINK_ERR or LINK_STATUS
Alarm
l 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
l MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
3.17 LOOP_ALM
SF64, SF64A, SFD64, SL64, SLD64, 3.17.1 LOOP_ALM (OCS)

Boards other than the SF64, SF64A, SFD64, 3.17.2 LOOP_ALM (OTN)
SLO16, or EGSH
3.17.1 LOOP_ALM (OCS)
Description
The LOOP_ALM is an alarm indicating the service loopback.

OptiX OSN 8800/6800/3800
Attribute
Minor Equipment alarm
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of a path. Parameter 2 indicates the optical-port

loopback alarm when being set to 0x01.

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 3 Indicates the loopback type.
l 0x00: optical- or electrical- port inloop

l 0x01: optical- or electrical- port outloop
l 0x02: channel inloop
l 0x03: channel outloop
l 0x04:loopback on the client
l 0x05: loopback on the optical multiplexer
l 0x06: SPI inloop
l 0x07: SPI outloop
l 0x08: ATM layer inloop
l 0x09: ATM layer outloop
l 0x0A: PHY layer inloop
l 0x0B: PHY layer outloop
l 0x0C: MAC layer inloop
l 0x0D: MAC layer outloop
l 0x0E: VC-4 timeslot inloop
l 0x0F: VC-4 timeslot outloop
l 0x10: VC-3 timeslot inloop
l 0x11: VC-3 timeslot outloop
l 0x12: VC-12 timeslot inloop
l 0x13: VC-12 timeslot outloop
l 0x14: intermediate frequency (IF) outloop
l 0x15: IF inloop
l 0x16: radio frequency (RF) inloop
l 0xFF: any of the preceding loopback types

When this alarm occurs, services are interrupted.
Possible Causes
Cause 1: A loopback command is issued for the test or maintenance purpose.
Procedure
Step 1 View the alarm on the NMS and determine the port that reports the alarm.
Step 2 Cause 1: A loopback command is issued for the test or maintenance purpose.

OptiX OSN 8800/6800/3800
1. Check whether the loopback is configured for the test or maintenance purpose. If the test
or maintenance is complete, eliminate the loopback on the port by referring to Supporting
Tasks.
----End
Related Information
None.
3.17.2 LOOP_ALM (OTN)
Description
This alarm is generated when the optical port of a board is in the loopback state.
Attribute
Parameters
l 0x00: inloop
l 0x01: outloop

Services are interrupted.
Fault Symptom
None.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
The possible cause of the LOOP_ALM alarm is as follows:
l Cause 1: The loopback command is delivered during testing or maintenance.
Procedure
l Cause 1: The loopback command is delivered during testing or maintenance.
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, see "Performing Inloop and Outloop" in the
Supporting Tasks.
assistance.
----End
Related Information
None.
3.18 LPT_ACTIVE
Description
This alarm indicates that LPT switching occurred. The data equipment itself has protection
schemes. 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
Parameters
None.

When this alarm is generated, services will be interrupted if no alternative route is available. If
an alternative route is available, the services will be automatically switched to the available
route, and a message will be generated, prompting the user to remove the fault.

OptiX OSN 8800/6800/3800
Fault Symptom
Table 3-17 lists the fault symptoms for the LPT_ACTIVE alarm.
Table 3-17 Fault symptoms for the LPT_ACTIVE alarm
Fault Symptom Cause
The R_LOS, LINK_ERR or L_SYNC alarm Cause 1: The input signals on the client side
may be generated on the client side of the are missing or the local board detects a
board. LINK_ERR or L_SYNC alarm.
An REM_SF alarm may be generated on the Cause 2: An REM_SF alarm is generated on

client side of the board. the client side of the local board because
equipment at the opposite station
malfunctions.
The OTUk_AIS, OTUk_LOF, Cause 3: When the WDM equipment receives

ODUk_PM_AIS, ODUk_PM_OCI, data services and the OTN frames are
ODUk_PM_LCK, ODUk_TCMn_AIS, transmitted on the WDM side, this alarm may
ODUk_TCMn_OCI, or ODUk_TCMn_LCK be triggered by the R_LOS, OTUk_AIS,
alarm may be generated on the WDM side of OTUk_LOF, ODUk_PM_AIS,
the board. 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 Cause 4: When the WDM equipment receives
WDM side. 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 Cause 3 or cause 4

WDM side.
NOTE
Possible Causes
l Cause 1: The input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
l Cause 2: An REM_SF alarm is generated on the client side of the local board because
equipment at the opposite station malfunctions.
l Cause 3: When the WDM equipment receives 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.

OptiX OSN 8800/6800/3800
l Cause 4: When the WDM equipment receives 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.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
Procedure
l Check whether the service type received by the WDM equipment and the frame format
transmitted on the WDM side is consistent with that of the service configuration model
using the U2000. If they are not consistent, configure them to ensure the consistency.
l Cause 1: The input signals on the client side are missing or the local board detects a
LINK_ERR or L_SYNC alarm.
1. Check whether the R_LOS, LINK_ERR or L_SYNC alarm is generated on the client
side. If it is, clear the R_LOS, LINK_ERR or L_SYNC alarm.
l 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 it is, clear the
REM_SF alarm.
l 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,
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.
1. If the frames on the WDM side are transmitted in the OTN format, check whether 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 is generated. If it is, clear the alarm.
l 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.
l Cause 5: Regarding to separation of the tributary board from the line board, if the cross-
connection configuration does not exist, the alarm is generated.
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

OptiX OSN 8800/6800/3800
whether the cross-connection is configured on the U2000. If not, configure the cross-
connection.
assistance.
----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 life will end.
Attribute
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 will be terminated.
Cause 2: The detection circuit of the board is faulty.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: The laser is aging. The service life of the laser will be terminated.
If ... Then ...
modules, module.

optical modules,
l Cause 2: The detection circuit of the board is faulty.
1. Replace the board.
assistance.
----End
Related Information
None.
3.20 MS_AIS
SF64, SF64A, SFD64, SL64, SLD64, 3.20.1 MS_AIS (OCS)

Boards other than the SF64, SF64A, SFD64, 3.20.2 MS_AIS (OTN)
SLO16, or EGSH
3.20.1 MS_AIS (OCS)
Description
The MS_AIS is an alarm indicating that multiplex section signals are unavailable on the optical
port that reports this alarm. This alarm is reported when the receive optical port of the local NE
has received five consecutive frames in which the last three bits of the K2 byte are 111.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

l When this alarm occurs, services are interrupted.
l When this alarm occurs, the system automatically returns the RDI message to the peer NE.
Then, the peer NE reports the MS_RDI alarm.
l When this alarm occurs, the AU_AIS alarm occurs on the downstream NE.
Possible Causes
l Cause 1: The local receive board is faulty.
l Cause 2: The active and standby cross-connect boards on the upstream NE are not detected.
l Cause 3: The transmit or cross-connect board on the upstream NE is faulty.
Procedure
Step 1 Cause 1: The local receive board is faulty.
1. Cold reset the local receive board on the NMS or directly remove and insert the board. For
details about how to cold reset a board, see the Supporting Tasks. Then, check whether the
alarm is cleared.
NOTICE
If services on the board are not protected, cold resetting the board interrupts services.
2. If the alarm persists, replace the local receive board. For details, see Parts Replacement.
Then, check whether the alarm is cleared.
Step 2 Cause 2: The active and standby cross-connect boards on the upstream NE are not detected.
1. Check whether the active and standby cross-connect boards are loose on the upstream NE.
If yes, insert the boards firmly. Then, check whether the alarm is cleared.
2. If the alarm persists, cold reset the cross-connect boards on the NMS. For details, see the
Supporting Tasks. Then, check whether the alarm is cleared.

OptiX OSN 8800/6800/3800
NOTICE
If there is no standby cross-connect board, cold resetting the active cross-connect board
may interrupt services.
Step 3 Cause 3: The transmit or cross-connect board on the upstream NE is faulty.

1. Replace the transmit board on the upstream NE. For details, see Parts Replacement. Then,
check whether the alarm is cleared.
2. If the alarm persists, replace the cross-connect board on the upstream NE. For details, see
the Parts Replacement. Then, check whether the alarm is cleared.
----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.
Attribute
Parameters
None

The services are faulty.
Fault Symptom
None.
NOTE

OptiX OSN 8800/6800/3800
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 O O

contain the A F F A
OTU(A) OTU(B)
MS_AIS signal D I I D
M U U M
Client WDM WDM Client
side side side side
Station A Station B
l Cause 2 : The board that reports the alarm is faulty.
Procedure
l Cause 1 : The input signals from the client side contain the MS_AIS signal
side of OTU(A). If the alarm on OTU(A) persists, it indicates that OTU(A) 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, module.
assistance.
----End
Related Information
Related Cases:
l MC-A57 How to Clear OTU Alarms Because of Unused Ports

OptiX OSN 8800/6800/3800
3.21 MS_RDI
SF64, SF64A, SFD64, SL64, SLD64, 3.21.1 MS_RDI (OCS)

Boards other than the SF64, SF64A, SFD64, 3.21.2 MS_RDI (OTN)
SLO16, or EGSH
3.21.1 MS_RDI (OCS)
Description
The MS_RDI is an alarm indicating that data reception fails at the peer end of a multiplex section
(MS). This alarm is reported when the board detects that the last three bits of the K2 byte are
110. The peer NE reports this alarm to the local NE when the MS_AIS alarm occurs.
Attribute
Parameters
None.

When this alarm occurs, services on the local NE are not affected. Services received by the peer
NE, however, are interrupted.
Possible Causes
l The local NE receives an alarm such as R_LOS and MS_AIS.
l The local transmit board is faulty.
l The peer receive board is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Check whether an alarm, such as R_LOS, R_LOF, MS_AIS, B2_EXC, and B2_SD, occurs on
the peer board. If yes, clear the alarm. Then, check whether the MS_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the local board is faulty. If yes, cold reset the local board.
Step 3 If the alarm persists, replace the local board. Then, check whether the alarm is cleared.
Step 4 If the alarm persists, check whether the peer board is faulty. If yes, cold reset the peer board.
Step 5 If the alarm persists, replace the peer board. Then, check whether the alarm is cleared.
----End
Related Information
None.
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 WDM-
side receive part of the opposite station is faulty (for example, the R_LOS, R_LOF or MS_AIS
alarm is generated).
Attribute
Parameters
None

l If the alarm is reported from the WDM side, the services may be interrupted.
l If the alarm is reported from the client side, the client-side services are abnormal.
Fault Symptom
Table 3-20 lists the fault symptom for the MS_RDI alarm.

OptiX OSN 8800/6800/3800
Table 3-20 Fault symptom for the MS_RDI alarm
Fault Symptom Cause
The board at the opposite station reports an Cause 1 (reported from the WDM side): The
R_LOS, R_LOF, or MS_AIS alarm. receiver on the WDM side at the opposite
station detects a signal failure.
NOTE
Possible Causes
l Cause 1 (reported from 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 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 O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
l Cause 1 (reported from 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 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 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.

OptiX OSN 8800/6800/3800
Detects and reports the R_LOS,

R_LOF, MS_AIS alarm
Client O WDM O
WDM Client
side T side T
side side
U U
Station A Station B
Detects and reports the Sends the MS_RDI
MS_RDI alarm signal back
Procedure
l Cause 1 (reported from 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.
1. 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.
l Cause 1 (reported from 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 MS_AIS alarm is
generated).
1. Query the alarm of the board at the opposition station by using the U2000. If an
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.
procedure for cause 2 of this alarm generated on the WDM side.
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, module.

OptiX OSN 8800/6800/3800
assistance.
----End
Related Information
None.
3.22 MUT_LOS
Description
Loss of multiplexed signals. This alarm is generated when the input multiplexed signals of the
board are lost.
Attribute
Parameters
None

The services carried by the optical port where this alarm is generated are interrupted.
Fault Symptom
Table 3-21 lists the fault symptom for the MUT_LOS alarm.
Table 3-21 Fault symptom for the MUT_LOS alarm
Fault Symptom Cause
There is no input optical power on the optical Cause 1: The fiber connected to an optical
port where the MUT_LOS alarm is reported. port at the receive end of the board that reports
the alarm is not connected, incorrectly
connected, or damaged.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The fiber connected to an optical port at the receive end of the board that reports
the alarm is not connected, incorrectly connected, or damaged.
Procedure
l 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.
l Cause 1: The fiber connected to an optical port at the receive end of the board that reports
the alarm is not connected, incorrectly connected, or damaged.
1. Check whether the fiber connected to an optical port at the receive end of the board
that reports the alarm is not connected or incorrectly connected. If it is not connected
or incorrectly connected, ensure that it is properly connected.
2. Check the fibers or fiber connectors on the board that reports this alarm are dirty. If
they are dirty, see Checking Fiber Jumpers by Using an Optical Power Meter or
Replace the Fiber Jumper to rectify the fault.
1. 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 permitted
range. For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.
NOTE
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 it is, 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 it is, 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.

OptiX OSN 8800/6800/3800
If ... Then ...
modules, module.

optical modules,
assistance.
----End
Related Information
Related Cases:
l MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
l MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
l MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
l 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
l 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 Alarm
l 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
l MC-A245 Physical Optical Cable Is Interrupted But Logical Fibers Connected to the FIU
Board Do Not Change to Red on the NMS
3.23 OA_LOW_GAIN
Description
Gain of an optical amplifier (OA) board being low. This alarm is generated when the actual gain
of an OA board is 3 dB lower than the nominal gain. For the Raman optical module of the RAU
board, the alarm is generated when the actual gain is 2 dB lower than the nominal gain.
Attribute
Critical Service alarm
Parameters
None

OptiX OSN 8800/6800/3800

The impacts of this alarm vary according to the alarm causes:
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.
l 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-22 lists the fault symptom for the OA_LOW_GAIN alarm.
Table 3-22 Fault symptom for the OA_LOW_GAIN alarm
Fault Symptom Cause
The OAU board that reports this alarm also Cause 1: The input optical power of the OAU
reports a power high alarm, such as board is excessively high.
SUM_INPWR_HI.
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
For optical amplifier boards and the EDFA optical module of the RAU board, the alarm caused
by different factors has different impacts on the system:
l Cause 1: The input optical power of the board is excessively high.

l 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.)
For the Raman optical module of the RAU board, the alarm caused by different factors has
different impacts on the system:
l Cause 1: The quality of the fiber 30 km near the board deteriorates or the end face of the
fiber is burnt.
l Cause 2: The insertion loss of the near-end fiber connector is too large.
l Cause 3: The span is too short.
l Cause 4: The configured fiber type is inconsistent with the actual fiber type.
l Cause 5: The current configured gain is out of the gain range of the new fibers after the
fiber type is changed.

OptiX OSN 8800/6800/3800
l Cause 6: A fault occurs on the board. For example, the pump laser is aging or faulty, or the
gain locking unit is faulty.
Procedure
l Cause 1: The input optical power of the board is excessively high.
1. On the U2000, check whether the receive optical power of the board is within the
permitted range. For the optical power specifications of the specific board, see
"Technical Specifications" in the Product Description.
2. If the input optical power is not within the permitted range, adjust the optical attenuator
attached to the input optical port so that the input optical power meets the specification
requirement. For details, see "Adjusting, Replacing, Adding and Removing
Attenuator" in the Supporting Tasks.
3. If no optical attenuator is attached to the input optical port, add an optical attenuator
to ensure that the input optical power meets the specification requirement. For details,
see "Adjusting, Replacing, Adding and Removing Attenuator" in the Supporting
Tasks.
l 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".
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". For the insertion loss specification, see the Product
Description. For the optical power specifications of the specific board, see "Technical
3. Check whether the alarm is cleared. If the alarm persists, replace the DCM module
between the TDC and RDC optical ports.
1. Replace the faulty board.
If ... Then ...
modules, module.

OptiX OSN 8800/6800/3800
If ... Then ...

optical modules,
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei for help.
l Cause 1: The quality of the fiber 30 km near the board deteriorates or the end face of the
fiber is burnt.
1. Check the end face of the fiber using a fiberscope and check the fiber quality using
an OTDR. When checking the fiber quality using an OTDR, you are advised to connect
a temporary fiber longer than 5000 m between the ODF and the OTDR.If the end face
of the fiber is burnt, replace or re-splice the fiber. If the fiber quality deteriorates,
contact Huawei to rectify the fiber link or decrease the gain of the Raman optical
module.
l Cause 2: The insertion loss of the near-end fiber connector is too large.
1. Check the fiber connection using an appropriate meter.
l Cause 3: The span is too short.
1. Check whether the span is greater than 70 km.
l Cause 4: The configured fiber type is inconsistent with the actual fiber type.
1. Check whether the specified fiber type matches the fiber in use. If they mismatch, set
the fiber type again so that they match each other.
l Cause 5: The current configured gain is out of the gain range of the new fibers after the
fiber type is changed.
1. Check whether the current nominal gain is higher than the maximum nominal gain of
the new fiber. If it is, reset the nominal gain to ensure that it is within the permitted
range.
l Cause 6: A fault occurs on the board. For example, the pump laser is aging or faulty, or the
gain locking unit is faulty.
----End
Related Information
None.
3.24 ODU_SNCP_PS
Description
ODUk SNCP protection switching. This alarm is generated on the board of working channel
when an ODU SNCP protection group actuates switching in which the current channel switches
to the protection channel from the working channel.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

When an ODUk SNCP protection group undergoes switching, services are transiently
interrupted. When this alarm is reported, the working channel of the ODUk SNCP protection
group might have faulty services that need to be restored.
Fault Symptom
Table 3-23 lists the fault symptoms for the ODU_SNCP_PS alarm.
Table 3-23 Fault symptoms for the ODU_SNCP_PS alarm
Fault Symptom Cause

Protection switching is performed, and the Cause 2: The services on the working channel
board on the working channel reports alarms of the ODUk SNCP protection group are
that can trigger protection switching. faulty and therefore services are
automatically switched to the protection
channel.
NOTE
Possible Causes
switching. Such a command switches the services of the ODUk SNCP protection group
from the working channel to the protection channel.
l Cause 2: The services on the working channel of the ODUk SNCP protection group are
faulty and therefore services are automatically switched to the protection channel.

OptiX OSN 8800/6800/3800
Procedure
switching.
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
switch the current channel to the working channel.
l Cause 2: The services on the working channel of the ODUk SNCP protection group are
faulty and therefore services are automatically switched to the protection channel.
1. Query whether the related boards for configuring the protection group have service-
related 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 they do, handle
the alarms by referring to the corresponding handling procedure of the alarms.
Revertive. If it is, after WTR Time the active channel automatically switches to the
working channel and the alarm clears. If the attribute is Non-Revertive, set it to
Revertive, and after WTR Time the alarm clears.
assistance.
----End
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
Related Cases:
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
3.25 ODUk_PM_AIS
Description
ODUk PM alarm indication signal. An AIS signal is transmitted to the downstream station,
indicating 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, or 4.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3, 4, or 5G.

OptiX OSN 8800/6800/3800
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2, or 5G.
Attribute
Warning Communication alarm
Parameters
None

The services carried at the optical port are interrupted.
Fault Symptom
Table 3-24 lists the fault symptoms for the ODUk_PM_AIS alarm.
Table 3-24 Fault symptoms for the ODUk_PM_AIS alarm
Fault Symptom Cause
The client side of the corresponding OTU Cause 1 (reported from the WDM side): The
board at the opposite station reports an client side of the corresponding OTU board
ODUk_PM_AIS, R_LOS, OTUk_LOF, at the opposite station reports an
OTUk_LOM, or OTUk_TIM alarm. 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 Cause 2 (reported from the WDM side): The
station reports an R_LOS, OTUk_LOF, WDM side of the OTU board at the local
OTUk_LOM, or OTUk_TIM alarm. 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 (reported from the client side): Signals input from the client side contain an
ODUk_PM_AIS signal.
See the following figure.

OptiX OSN 8800/6800/3800
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.
Detects and reports

the ODUk_PM_AIS alarm
The client
signals contain
the ODUk_PM_AIS
signal O O
Client T WDM WDM T Client
side U side side U side
Station A Station B
l Cause 1 (reported from 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.
Detects and reports the
ODUk_PM_AIS, R_LOS, Insert the Detects and reports
OTUk_LOF, OTUk_LOM, ODUk_PM_AIS the ODUk_PM_AIS alarm
OTUk_TIM alarm signal
Client O WDM WDM O Client

side T side side T side
U U
Station A Station B
l Cause 2 (reported from 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.
Procedure

OptiX OSN 8800/6800/3800
ODUk_PM_AIS signal.
between the transmit and receive optical ports on the client side of OTU1. If the alarm
on OTU1 persists, the OTU1 hardware is faulty. See the alarm handling procedure for
cause 2 of this alarm generated on the client side.
NOTICE
2. If the alarm is cleared, the input signals on the client side of the board contain
ODUk_PM_AIS signals. Rectify the fault on the client equipment.
If ... Then ...
modules, module.

optical modules,
l Cause 1 (reported from the WDM 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
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.
l Cause 2 (reported from 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.
assistance.
----End
Related Information
ITU-T G.709
Related Cases:

OptiX OSN 8800/6800/3800
Alarms
3.26 ODUk_PM_BDI
Description
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.

Attribute
Parameters
None

Fault Symptom
Table 3-25 lists the fault symptom for the ODUk_PM_BDI alarm.
Table 3-25 Fault symptom for the ODUk_PM_BDI alarm
Fault Symptom Cause
The board at the opposite station reports an Cause 1 (reported from the WDM side): The
R_LOS, OTUk_LOF, OTUk_LOM, WDM side of the corresponding board at the
ODUk_PM_LCK, ODUk_PM_OCI, opposite station reports an R_LOS,
ODUk_PM_TIM, or ODUk_PM_SSF alarm. 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).

OptiX OSN 8800/6800/3800
NOTE
Possible Causes
ODUk_PM_BDI signal.
l Cause 1 (reported from 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_LCK, ODUk_PM_OCI,
ODUk_PM_TIM, ODUk_PM_SSF
alarms
O O
T T
side side side side
U U
Station A Station B
Detects and reports the Sends the
ODUk_PM_BDI alarm ODUk_PM_BDI signal
back
Procedure
l On the U2000, check whether there is an alarm with higher severity on the board. If there
is, handle the alarm properly.
ODUk_PM_BDI signal.
between the transmit and receive optical ports on the client side of OTU board. If this
alarm persists, the board is faulty. In this case, see the alarm handling procedure for
cause 2 of this alarm generated on the client side.
NOTICE
A loopback on the board interrupts the existing services.
2. If this alarm is cleared, the input signals on the client side of the board contain bit
errors. Rectify the fault on the client equipment.

OptiX OSN 8800/6800/3800
If ... Then ...
modules, module.

optical modules,
l Cause 1 (reported from 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.
assistance.
----End
Related Information
ITU-T G.709
3.27 ODUk_PM_DEG
Description
ODUk PM signal degraded. This alarm is generated if signal degradation occurs or the bit error
count exceeds the threshold when the BIP8 detection is in burst mode and generated if signal
degradation occurs when the BIP8 detection in poisson mode.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

If this alarm is generated, bit errors are generated in the services carried at the optical port, which
makes the service signals invalid or even unavailable.
Fault Symptom
Table 3-26 lists the fault symptom for the ODUk_PM_DEG alarm.
Table 3-26 Fault symptom for the ODUk_PM_DEG alarm
Fault Symptom Cause
The OTU board at the local station may report Cause 1: The attenuation of received signals
an IN_PWR_LOW or BEFFEC_EXC alarm. 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.

l Cause 2: The fiber on the transmission line is abnormal.
l Cause 3: The board that reports the alarm is faulty or the board in the upstream station is
faulty.
Procedure
l Cause 1: The input optical power of the OTU board is abnormal.
1. On the U2000, view the alarms of the entire network to confirm the slot ID, port 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 permitted range. For the optical power
specifications of the specific board, see "Technical Specifications" in the Product
Description.
3. If the optical power is within the permitted range, query historical performance data
of the optical power on the U2000 to check whether there is an exception. For details,
see "Checking Historical WDM Performance Events" in the Supporting Tasks. If there
is an exception, see the alarm handling procedure for cause 2.
4. If the optical power is not within the permitted range, adjust the input optical power
of the board to a proper value. For details, see "Adjusting, Replacing, Adding and
Removing Attenuator" in the Supporting Tasks.

OptiX OSN 8800/6800/3800
5. Check whether the alarm is cleared. If the alarm persists, troubleshoot this alarm
station by station along the service signal flow.
l 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, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
radius or it is damaged or aging, adjust or replace the fiber jumper.
l Cause 3: The board that reports the alarm is faulty or the board in the upstream station is
faulty.
1. If the alarm persists, replace the board that reports the alarm or the faulty board in the
upstream station.
If ... Then ...
modules, module.

optical modules,
assistance.
----End
Related Information
ITU-T G.709
3.28 ODUk_PM_EXC
Description
ODUk PM BIP8 error count exceeding 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 FLEX, 0, 1, 2, 3.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.

OptiX OSN 8800/6800/3800
Attribute

Parameters
None

The alarm has impacts on the QoS of the service signals.
Fault Symptom
Table 3-27 lists the fault symptoms for the ODUk_PM_EXC alarm.
Table 3-27 Fault symptoms for the ODUk_PM_EXC alarm
Fault Symptom Cause
The OTU board at the local station may report Cause 1: The attenuation of the received
an IN_PWR_LOW alarm. 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.
l Cause 2: The transmitter of the OTU board at the opposite station is faulty.
l Cause 3: The receiver of the OTU board at local station is faulty.
Procedure
l Cause 1: The attenuation of the received signals is rather large, and the fiber transmission
line is abnormal.
1. On the U2000, check whether the receive optical power is within the permitted range.
For the optical power specifications of the specific board, see "Technical
Specifications" in the Product Description.For details, see "Querying Optical Power
on the U2000" in the Supporting Tasks.

OptiX OSN 8800/6800/3800
NOTE
the OTU board.
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 permitted range on the U2000. For
the optical power specifications of the specific board, see "Technical Specifications"
in 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.
l 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, the
transmitter on the OTU board of the opposite station is faulty. Replace the OTU board.
If ... Then ...
modules, module.
2. If the alarm persists, see the alarm handling procedure for cause 3.
l 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, module.

optical modules,
----End
Related Information
ITU-T G.709

OptiX OSN 8800/6800/3800
3.29 ODUk_PM_SSF
Description
Failure of ODUk PM server-layer signals.

Attribute
Parameters
None

Fault Symptom
Table 3-28 lists the fault symptom for the ODUk_PM_SSF alarm.
Table 3-28 Fault symptom for the ODUk_PM_SSF alarm
Fault Symptom Cause
A station may report the R_LOS or Cause 1: The line in the regeneration span is
OTUk_SSF alarm at the same time. 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.
A station may report the ODUk_TCMn_SSF, Cause 2: The station reports an alarm of the
ODUk_TCMn_LCK, ODUk_TCMn_OCI, ODUk_TCMn type and the ODUk_PM_SSF
ODUk_TCMn_AIS, ODUk_TCMn_LTC, or alarm at the same time.
ODUk_TCMn_TIM alarm at the same time.

OptiX OSN 8800/6800/3800
Fault Symptom Cause
A station may report the OTUk_TIM alarm at Cause 3: The station reports the OTUk_TIM
the same time. or ODUk_PM_AIS alarm.
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.
M M M M
O U OA OA U U U
O O OA OA O
T X/ F F X/ X/ F F X/
T T T
U D I I D D I I D
U U U
1 M U U M M U U M
OA OA 2 3 4
Client WDM U U U OA OA U
side side X X X X WDM Client
side side
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
l 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.
l Cause 3: The station reports the OTUk_TIM or ODUk_PM_SSF alarm. The OTUk_TIM
alarm is reported only when Enable TIM Response is set to Enabled.
l 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.
Procedure
l Cause 1: The line in the regeneration span is abnormal when there are electrical regeneration
boards.
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.

OptiX OSN 8800/6800/3800
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. Handle these alarms with
precedence, otherwise see the next step.
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.
Handle these alarms with precedence, otherwise see the next step.
4. Check whether the OTU2 board at station B reports the R_LOS, OTUk_SSF, and
OTUk_LOF alarms. Handle these alarms with precedence, otherwise see the next step.
l Cause 2: The station reports an alarm of the ODUk_TCMn type and the ODUk_PM_SSF
alarm at the same time.
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 such an alarm is reported, handle the alarm first. That is,
clear the alarm according to the corresponding method.
3. Check whether the alarm is cleared. If the alarm persists, see cause 3.
l Cause 3: The station reports the OTUk_TIM or ODUk_PM_AIS alarm. The OTUk_TIM
alarm is reported only when Enable TIM Response is set to Enabled
1. Check whether the OTUk_TIM or ODUk_PM_AIS is reported at the station. If such
an alarm is generated, handle the alarm first. That is, clear the alarm according to the
corresponding method.
l 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.
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 with precedence.
That is, clear the alarms according to the corresponding methods. If the alarm still
exists, contact Huawei engineers.
----End
Related Information
Related Cases:
l MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of ODUk
SPRing Protection
l MC-A200 Fiber Faults Result in Service Interruption, The TDX Board Reports
ODU1_PM_SSF Alarms
l MC-A229 Switching Fails Due to Incorrect SNCP Protection Mode on the WDM
Equipment
3.30 OMS_FDI
Description
Forward defect indication at OMS layer. This alarm is generated to suppress the OMS_FDI_P
and OMS_FDI_O alarms when the two alarms coexist. When the board at the OTS layer detects

OptiX OSN 8800/6800/3800
a signal loss 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

Parameters
None

The existing services may be interrupted.
Fault Symptom
Table 3-29 lists the fault symptom for the OMS_FDI alarm.
Table 3-29 Fault symptom for the OMS_FDI alarm
Fault Symptom Cause
The board at the opposite station reports an Cause 2: At the upstream station, a fiber cut
OTS_LOS or OTS_TIM alarm. occurs or the optical power is excessively
low. Therefore, the signal loss 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.
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Therefore, the loss of signal alarm is detected at the downstream station, and the OMS_FDI
is then inserted to the downstream station.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: The logical fiber connections are inconsistent with the physical fiber connections.
1. Check whether the logical fiber connection configured for the optical port where the
alarm is generated is consistent with its physical fiber connection. If it is 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".
l Cause 2: At the upstream station, a fiber cut occurs or the optical power is excessively low.
Therefore, the signal loss 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 it is, troubleshoot the OTS_LOS or OTS_TIM alarm
according to the alarm handling procedure.
assistance.
----End
Related Information
None.
3.31 OSC_LOS
Description
Loss of input optical power on the OSC. This alarm is generated when the input optical power
of the OSC board exceeds the LOS threshold.
Attribute
Parameters
None

There is a fiber cut in the receive direction and this can cause loss of the monitoring signals.

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: An optical port on the board that reports the alarm is not connected to a fiber.
l Cause 2: The laser of the board at the opposite station is shut down.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber cut occurs
on the transmission line.
l Cause 4: The transmit part of the opposite station is faulty.
l Cause 5: The receive part of the local station is faulty.
Procedure
l Query the alarm on the U2000 and record the IDs of the optical port and channel where the
alarm is generated.
l Cause 1: An optical port on the board that reports the alarm is not connected to a fiber.
1. Check whether the fiber jumper is connected to the optical port of the board at the
local station. If it is not, connect the fiber jumper.
l Cause 2: The laser of the board at the opposite station is shut down.
1. On the U2000, check whether the laser of the specific board at the opposite station is
turned on. If it is not, open the laser of the board.
l Cause 3: The attenuation of the transmission line is excessively high, or a fiber cut occurs
on the transmission line.
1. On the U2000 check whether the receive optical power at the optical port where the
alarm is generated is within the permitted range. For the optical power specifications
of the specific board, see "Technical Specifications" in the Product Description.
2. If the receive optical power is not within the permitted 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.
l Cause 4: The transmit part of the opposite station is faulty.
1. If the alarm persists, replace the faulty board. Replace the board.
l Cause 5: The receive part of the local station is faulty.
1. If the alarm persists, replace the faulty board. Replace the board.
----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.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

Services may be interrupted.
Possible Causes
Cause 1: The OTS_LOS_P and OTS_LOS_O alarms exist at the opposite station.
Procedure
l Check the alarm information on the U2000 and record the IDs of the optical port and channel
l 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" port on the local FIU
and the opposite station is correct and reliable.
3. If the alarm persists, check whether the attenuation of the "IN" port 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 ports 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.

OptiX OSN 8800/6800/3800
l For OptiX OSN 8800, its value is 1, 2, 3, or 4.

l For OptiX OSN 6800, its value is 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is 1, 2, or 5G.
Attribute
Parameters
None

Services on the board are interrupted.
Fault Symptom
Table 3-30 lists the fault symptom for the OTUk_LOF alarm.
Table 3-30 Fault symptom for the OTUk_LOF alarm
Fault Symptom Cause
Two boards at two ends of a single Cause 1: The settings of the service type or
wavelength report the OTUk_LOF alarm in FEC type are incorrect.
the deployment.
A single board at one end reports the Cause 3: The receive optical power or the
OTUk_LOF alarm in the deployment. In OSNR of the local board is abnormal.
addition, the alarm indicating abnormal
optical power is reported.
Multiple boards on the same link report the Cause 6: The dispersion compensation value
OTUk_LOF alarm in the deployment. is excessively great or small.
A single board at one end reports the Cause 2: The board that reports the alarm is
OTUk_LOF alarm in the deployment. faulty.
A board reports the OTUk_LOF alarm during Cause 2: The board that reports the alarm is
normal operation after deployment. faulty.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The settings of the service type or FEC type are incorrect.
l Cause 3: The receive optical power or the OSNR of the local board is abnormal.
l Cause 4: The signals transmitted by the corresponding board at the opposite end do not
have a frame structure.
l Cause 5: The fiber of the transmission line is abnormal.
l Cause 6: The dispersion compensation value is excessively great or small.
l Cause 7: For the coherent board, the actually received wavelength is inconsistent with the
configured received wavelength on the board.
Procedure
l Cause 1: The settings of the service type or FEC type are incorrect.
1. Query the service type or FEC type on the U2000 to check whether the set service
type or FEC type is the same as the service type or FEC type supported by the board.
If the service type or FEC type is different from the service type or FEC type supported
by the board, reset the service type or FEC type to the same as the service type or FEC
type supported by the board.
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, module.

optical modules,
3. If the alarm disappears, see cause 3.

l 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 the
specific board, see "Technical Specifications" in 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.
l 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

OptiX OSN 8800/6800/3800
have the OTN frame format. If the light does not comply with the requirement, replace
the faulty board.
2. If no meter is available, perform a hardware loopback on the WDM-side optical port
of the opposite board. If the alarm on the board at the opposite end persists, the opposite
board is faulty and needs to be replaced.
If ... Then ...
modules, module.

optical modules,
l 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.
If the preceding requirements are not met, clean the fiber connector or replace the
fiber. For details, see "Inspecting and Cleaning the Fiber-Optic Connectors" in the
Supporting Tasks.
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.
l Cause 7: For the coherent board, the actually received wavelength is inconsistent with the
configured received wavelength on the board.
1. Verify consistency between the actually received wavelength and configured received
wavelength on the board.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
l MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with
the SSE1TMR
l MC-A56 LWF Board Reports OTU_LOF Alarm

OptiX OSN 8800/6800/3800
l MC-A63 MSBBE Bit Errors and OTU_LOF Alarm Occur in a DWDM 10G Network Due
to the Incorrect PMD
l MC-A72 The OTU_LOF Alarm Reported in the LWC1 Due to Wrong Regenerator Board
l MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
l MC-A115 Determine Whether the Type and Connections of the DCM Are Proper When
the OTU_LOF, R_OOF, R_LOF, and BEFFEC_SD Alarms Are Reported Discontinuously
on the WDM Side of LWF Board
l MC-A147 Services Are Unavailable Due to Inappropriate FEC Configuration on the 40G
Regeneration Boards, The System Reports An OTU_LOF Alarm
l MC-A188 The LDGF2 Board on the OptiX OSN 1800 Reports an OTU1_LOF Alarm
l MC-A206 Service Provisioning Fails on an LHP Network, The OTU2_LOF Alarm Is
Reported
l MC-A208 40G Service Provisioning Fails On a Network, The OTU_LOF And
DCM_INSUFF Alarms Are Reported
l MC-A211 OTUk_LOF Alarm Is Reported Due to Mismatched Mapping Modes of the LSX
Boards in the Case of 10GE LAN Services
l MC-A215 Incorrect Configuration of an Added Wavelength During Expansion Results in
Service Interruption of Another Normal Wavelength on an OTU Board, The Corresponding
OTU Board Reports OTU2_LOF Alarm
Alarms
l MC-A236 The OTU Board Transiently Reports the OTU_LOF Alarm Multiple Times due
to Excessively Large System PMD
l MC-A248 Network Services Are Interrupted After the Equipment Restarts Because the
Wavelengths Conflict After the Wavelength Configurations Are Modified
3.34 OTUk_SSF
Description
The OTUk_SSF is an alarm that the signal fails at the OTUk server layer.

Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Fault Symptom
Table 3-31 lists the fault symptom for the OTUk_SSF alarm.
Table 3-31 Fault symptom for the OTUk_SSF alarm
Fault Symptom Cause
A station may report the R_LOS, OTUk_SSF Cause 1: The station reports the R_LOS alarm
alarm at the same time. and the OTUk_SSF alarm at the same time.
A station may report the OTUk_AIS, Cause 2: The station reports the OTUk_AIS,
OTUk_LOF, or OTUk_LOM alarm at the OTUk_LOF, or OTUk_LOM alarm and the
same time. OTUk_SSF alarm at the same time.
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.
M M
O U OA U
OA O
T X/ F F X/
U D I T
I D
1 M U U
U M
U OA OA 2
Client WDM U
X WDM Client
side side X
side side
Station A Station B
NOTE
The OTU boards in the figure can be either tributary-line boards or tributary boards and line boards.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
OTUk_SSF alarm at the same time.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: The station reports the R_LOS alarm and the OTUk_SSF alarm at the same time.
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. Handle the alarm in advance, otherwise to the next step.
l Cause 2: The station reports the OTUk_AIS, OTUk_LOF, or OTUk_LOM alarm and the
OTUk_SSF alarm at the same time.
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 the alarm still exists, contact
Huawei engineers.
----End
Related Information
Related Cases:
SPRing Protection
3.35 OUT_PWR_HIGH
Description
Output optical power being too high. This alarm is generated when the laser output optical power
exceeds the upper threshold.
Attribute
Parameters
None

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.

OptiX OSN 8800/6800/3800
l If the board works abnormally, the existing services are affected.
Fault Symptom
None.
NOTE
Possible Causes
Cause 1: The optical module of the 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
l Cause 1: The optical module of the laser is faulty or the board is faulty.
If ... Then ...
modules, module.
The board does not supports pluggable Replace the board.

optical modules,
----End
Related Information
None.
3.36 PORT_MODULE_OFFLINE
Description
Optical module on an optical port being offline. This alarm is generated when the board detects
that an optical module is offline.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Absence of the optical module leads to an interruption of services carried at the corresponding
optical port.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1: The optical module does not exist or is not correctly inserted.
l Cause 2: The optical module or the board is faulty.
Procedure
l Cause 1: The optical module does not exist or is not correctly inserted.
1. Check whether the optical port where this alarm is generated has an optical module.
If ... Then ...
The optical port has no optical Insert an optical module into the optical
module. port properly.
The optical port has an optical See the alarm handling procedure for
module. cause 2.
l Cause 2: The optical module or the board is faulty.

2. If the alarm persists, the optical module or the board that reports the alarm may be
faulty. If the board uses pluggable optical modules, replace the specific pluggable
optical module. For details, see "Replacing Pluggable Optical Modules" in the Parts
Replacement.
3. If the optical module is not pluggable, replace the faulty board. Replace the board.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
3.37 POWER_FAIL
Description
Power supply failure. This alarm is generated when the power supply of a board becomes
abnormal. For example, there is overvoltage or undervoltage of the power supply, or the battery
on the system control board has no charge.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the state of the power supply in which the alarm is generated. For
example:
0x01 indicates the overvoltage of the 5 V power supply.
0x02 indicates the undervoltage of the 5 V power supply.
0x03 indicates the overvoltage of the -5 V power supply.
0x04 indicates the undervoltage of the -5 V power supply.
0x05 indicates that the voltage of the battery is excessively low or the battery
fails.
0x06 indicates that the 4.8 V power supply is abnormal.
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.
0x53 indicates the undervoltage of the -48 V fan power supply.
0x54 indicates the overvoltage of the -48 V fan power supply.
0x6E indicates no input for the -48 V power supply.
0x6D indicates no output of the 3.3 V power supply.

l When this alarm is reported by the system control board, the system time and the NE
configuration data of the latest 30 minutes will be lost when the power supply fails.
l When 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 the switching to the standby power supply is
performed.
If both active and standby power supplies fail, the existing services are interrupted.
Fault Symptom
None.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: If this alarm is reported by the system control board, the battery of the system
control and communication board is abnormal (the value of parameter 1 of this alarm is
0x05).
l Cause 2: If this alarm is reported by the PIU board, 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).
l Cause 3: If this alarm is reported by the PIU or CRPC board, the power supply module of
the board fails or is aging (the value of parameter 1 of this alarm may be any value except
0x05).
Procedure
l Cause 1: If this alarm is reported by the system control board, the battery of the system
control and communication board is abnormal (the value of alarm parameter 1 is 0x05).
1. On the NMS, back up the NE configuration data to the flash database on the system
control board.
2. Check whether the jumper cap is correctly placed over the battery jumper. If it is,
check the jumper setting of the battery on the system control board. If the setting
disables the battery from providing power, change the setting to ensure that the battery
provides power to the system control board.
3. 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.
l Cause 2: If this alarm is reported by the PIU board, 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
it is not, turn it to ON.
2. Use a multimeter to check whether the voltage of the external input power supply is
within the permitted range (the permitted range for the voltage of the working power
supply for OptiX optical transmission equipment is -72 V to -40 V). If the voltage is
not within the permitted range, check whether the power supply of the equipment
room is normal.
3. If the voltage of the external input power supply is within the permitted range but the
alarm persists, the power switch on the DC power distribution box may be faulty. In
this case, replace the switch. For details, see "Replacing the Power Switch on the DC
Power Distribution Box".
4. If the alarm persists, the PIU board is faulty. Replacing the PIU Board.
l Cause 3: If this alarm is reported by the PIU or CRPC board, the power supply module of
the board fails or is aging (the value of parameter 1 of this alarm may be any value except
0x05).
1. Replace the faulty board. For details, see "Replacing the PIU Board" or "Replacing
the Raman Amplifier Board".
----End

OptiX OSN 8800/6800/3800
Related Information
Related Cases:
l MC-A2 The E1V40 Board Reports the POWER_FAIL and MODULE_TEMP_OVER
Alarms
l MC-A82 Analysis of the POWER_FAIL Alarm on the OptiX OSN 6800 and Solution
l MC-A112 The SCC Housed In the Slave Subrack Reports the POWER_FAIL Alarm
Because the Jumper on the Board Is Set Improperly
l MC-A204 Power Modules on Multiple Boards Report the POWER_FAIL Alarms Due to
Excessively High Temperature
3.38 PUMP_COOL_EXC
Description
Cooling current of the pump laser exceeding the threshold. This alarm is generated when the
laser cooling current is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
Parameter 1 Indicates the threshold crossing type:
0x01 indicates that the upper threshold is exceeded;
0x02 indicates that the lower threshold is exceeded.

When this alarm is reported, the laser ages sharply and the performance of output signals
deteriorates.
Fault Symptom
Table 3-32 lists the fault symptom for the PUMP_COOL_EXC alarm.

OptiX OSN 8800/6800/3800
Table 3-32 Fault symptom for the PUMP_COOL_EXC alarm
Fault Symptom Cause
The NE that reports this alarm reports a Cause 1: The ambient temperature of the
temperature alarm or fan fault alarm, such as board is excessively high or low.
TEMP_OVER or FAN_FAIL, within a
certain time.
NOTE
Possible Causes
The possible causes of the PUMP_COOL_EXC alarm are as follows:
l Cause 1: The ambient temperature of the board is excessively high or low.

l Cause 2: The pump laser temperature is excessively high or low.
Procedure
l Cause 1: The ambient temperature of the board is excessively high or low.
1. Check the ambient temperature of the equipment room, the cleanliness of the air filter,
and heat dissipation of fans. For details, see TEMP_OVER to rectify the fault.
procedure for causes 2 and 3.
l Causes 2: The pump laser temperature is excessively high or low/Cause 3: The board that
reports this alarm is faulty.
1. If the alarm persists, replace the faulty board. Refer to Replace the board.
assistance.
----End
Related Information
None
3.39 R_LOF

OptiX OSN 8800/6800/3800
SF64, SF64A, SFD64, SL64, SLD64, 3.39.1 R_LOF (OCS)

Boards other than the SF64, SF64A, SFD64, 3.39.2 R_LOF (OTN)
SLO16, or EGSH
3.39.1 R_LOF (OCS)
Description
The R_LOF is an alarm indicating that frames are lost on the receive side of the line. This alarm
is reported when the local optical port receives five consecutive frames that do not contain correct
A1 and A2 bytes.
Attribute
Parameters
None.

l When this alarm occurs, services are interrupted, and the local NE inserts an AIS signal to
the downstream NE.
l When this alarm occurs, the system automatically returns an MS_RDI signal to the
upstream NE. Then, the upstream NE reports the MS_RDI alarm.
Possible Causes
l Cause 1: Two boards at different rates are interconnected.
l Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 3: The local receive board is faulty so that the frame structure is lost.
l Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is
lost.

OptiX OSN 8800/6800/3800
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting port according to alarm
parameters.
Step 2 Cause 1: Two boards at different rates are interconnected.

1. An improper fiber connection may cause an interconnection of two boards at different rates,
which triggers the R_LOF alarm. Check whether the optical fiber is properly connected. If
not, correct the optical fiber connection. For details, see the Commissioning Guide. Then,
2. If the alarm persists, check whether the types of the two interconnected boards are the same.
For example, when a board that supports the FEC function is interconnected with a board
that does not support the FEC function, the R_LOF alarm will be reported if the rates of
the two boards are inconsistent.
3. Select two boards with the same rate. Then, check whether the alarm is cleared. If the alarm
persists, go to Step 3.
Step 3 Cause 2: The transmit cable is faulty, and the fiber connector is loose or contaminated.
1. Check whether the output optical power of the peer board is within the normal range. For
details about the optical power indicators for boards, see Product Description. For details
about how to check the output optical power of a board, see the Supporting Tasks.
NOTE
For detailed manufacturing information about an optical module, see the Supporting Tasks or Bar
Code in the Hardware Description.
If... Then...
The output optical power of the peer board is out of range Go to Step 5.
The output optical power of the peer board is within the normal Go to the next step.
range
2. On the NMS, check whether the input optical power of the local board is within the normal
range.
If... Then...
The input optical power of the local board is below the lower Go to the next step.
threshold
The input optical power of the local board is above the upper Go to Step 4.
threshold
3. Check whether the bending radius of the pigtail is within the normal range. If the bending
radius is smaller than 6 cm, re-roll the pigtail. Then, check whether the alarm is cleared.
4. If the alarm persists, properly connect the pigtail to the optical port on the board. Then,

OptiX OSN 8800/6800/3800
5. If the alarm persists, check whether the fiber connector is contaminated. For details, see
the Supporting Tasks. If the fiber connector is contaminated, clean the fiber connector. For
details, see Supporting Tasks.
6. Check whether the optical cable is aged, damaged, or pressed. If yes, replace the optical
cable. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Perform a hardware loopback on the port that reports the alarm on the local NE. For details,
see the Supporting Tasks.
NOTICE
A loopback interrupts services. Ensure that the optical power is within the normal range
when performing a hardware loopback. You can add an optical attenuator for the receive
optical interface according to the optical power specifications for the board.
If... Then...
The R_LOF alarm persists The local board is faulty. Go to the next step.
The R_LOF alarm is cleared Go to Step 5.
2. Replace the optical module if it is pluggable on the board. For details, see the Parts
Replacement. Replace the board if the optical module is unpluggable. For details, see Parts
Replacement.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 5.
Step 5 Cause 4: The peer transmit or cross-connect board is faulty so that the frame structure is lost.
1. Replace the optical module if it is pluggable on the board. For details, see the Parts
Replacement. Replace the board if the optical module is unpluggable. For details, see Parts
Replacement. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see the Parts
Replacement.
----End
Related Information
None.
3.39.2 R_LOF (OTN)

Description
Loss of frames on the receiving line. This alarm is generated when the frame alignment
processing is out of frame (OOF) in 3 consecutive milliseconds.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

l The board fails to locate the data frame of the received SDH signals, and therefore the client
services fail.
l After this alarm is detected, protection switching is performed if the board supports
protection switching.
Fault Symptom
Table 3-34 lists the fault symptom for the R_LOF alarm.
Table 3-34 Fault symptom for the R_LOF alarm
Fault Symptom Cause
The upstream board may report an R_LOS or Cause 4 (reported from the WDM side)
R_LOF alarm.
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.
l Cause 2 for this alarm generated on the client side: The board that reports this alarm is
faulty.
l Cause 1 for this alarm generated on the WDM side: The receive optical power or the OSNR
of the local board is abnormal.
l Cause 2 for this alarm generated on the WDM side: The signals transmitted by the upstream
OTU have no SDH frame structure.
l Cause 3 for this alarm generated on the WDM side: The board that reports this alarm is
faulty.
l 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.

OptiX OSN 8800/6800/3800
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
Procedure
l Cause 1 for this alarm generated on the client side: The input signals from the client side
contain an R_LOF alarm signal.
between the transmit and receive optical ports on the client side of the board. If this
alarm on the board persists, the board is faulty. In this case, see the alarm handling
procedure for cause 2 of this alarm generated on the client side.
NOTICE
2. If this alarm is cleared, the input signals on the client side contain an R_LOF signal.
In this case, rectify the fault on the client equipment.
faulty.
1. Check whether board that reports this alarm supports pluggable optical modules.
If ... Then ...
modules, module.

optical modules,
assistance.
l 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 permitted range. For
the optical power specifications of the specific board, see "Technical Specifications"
in the Product Description.

OptiX OSN 8800/6800/3800
NOTE
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 at the 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, module.

optical modules,
faulty.
1. If the alarm persists, the board may be faulty. Replace the faulty board at the local
station.
If ... Then ...
modules, module.

optical modules,
l 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.
l Cause 5 for this alarm generated on the WDM side: The dispersion is under- or over-
compensated.
1. If the alarm persists, replace the DCM module.
assistance.
----End

OptiX OSN 8800/6800/3800
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
l MC-A21 An Interconnection Failure between the WDM and SDH Equipment
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A31 Wrong Calculation for Dispersion in One DWDM Project
l 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
l 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
l MC-A133 In a WDM System with 1:N Optical Channel Protection, the R_LOF Alarm Is
Reported in the Receive Direction on the Client Side When the Laser on the LWC1 Board
in the Protection Channel Is Open
l 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
l 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
l 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
Alarms
3.40 R_LOS
SF64, SF64A, SFD64, SL64, SLD64, 3.40.1 R_LOS (OCS)

Boards other than the SF64, SF64A, SFD64, 3.40.2 R_LOS (OTN)
SLO16, or EGSH

OptiX OSN 8800/6800/3800
3.40.1 R_LOS (OCS)
Description
The R_LOS is an alarm indicating that signals are lost on the receive side.
Attribute
Parameters
None.

When this alarm occurs, either of the following will interrupt services on the receive side of the
line:
l The system automatically inserts an AIS signal to the downstream NE.

l The system automatically sends an MS_RDI signal to the upstream NE so that the upstream
NE reports the MS_RDI alarm.
If a data board reports an R_LOS alarm, the Ethernet port enters the link-down state.
If an E-Line service is configured between the Ethernet port and the corresponding VCTRUNK
port, the VCTRUNK port may insert a management frame containing the client signal fail (CSF)
signal to the downstream NE.
Possible Causes
l Cause 1: The local optical port is unused.
l Cause 2: The peer laser is disabled so that no optical signal is input.
l Cause 3: The fiber is cut or the line performance deteriorates.
l Cause 4: The local receive board is faulty so that signals fail to be received.
l Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to be
transmitted.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the alarm-reporting port.
Step 2 Cause 1: The local optical port is unused.

1. Check whether the port that reports the alarm is unused or whether the port is connected to
a fiber that is not in use. If the fiber is not in use, perform a selfloop for the transmit and
receive optical interfaces using a fiber.

OptiX OSN 8800/6800/3800
If... Then...
The optical port is unused or the No action is required. To clear the R_LOS
specified fiber is not connected to the alarm, mask the alarm or use a fiber to
optical port connect the receive and transmit interfaces
of the optical port.
NOTE
Masking the R_LOS alarm may trigger other
alarms.
NOTICE
Ensure that the receive optical power is within the
specified range when performing a hardware
loopback on the optical port.
The optical port is in use and the Go to Step 3.

specified fiber is connected to the optical
port
Step 3 Cause 2: The peer laser is disabled so that no optical signal is input.
1. Check whether the laser at the peer port is disabled.
If... Then...
The laser is disabled Enable the laser. For details, see the Supporting Tasks. Then,
check whether the alarm is cleared. If the alarm persists, go to
Step 4.
The laser is enabled Go to Step 4.
Step 4 Cause 3: The fiber is cut or the line performance deteriorates.

1. Check whether the output optical power of the peer board is within the specified range,
which is provided in Product Description. For details about how to check the output optical
power of a board, see the Supporting Tasks.
NOTE
For detailed manufacturing information about an optical module, see the Supporting Tasks or Bar
Code in the Hardware Description.
If... Then...
The output optical power of the peer board is out of range Go to Step 6.
The output optical power of the peer board is within the Go to the next step.
specified range
2. Use a fiber to connect the receive and transmit ports of the local receive board. For details,

OptiX OSN 8800/6800/3800
NOTICE
A loopback interrupts services. Ensure that the input optical power is within the specified
range when performing a hardware loopback. You can add an optical attenuator at the
receive optical interface of the optical port based on the optical power specifications for
the board.
If... Then...
The R_LOS alarm persists Go to Step 5.
The R_LOS alarm is cleared Repeat steps Step 4.3 to Step 4.6 to check the pigtails
and fiber connectors on the local and peer NEs.
3. Check whether the radius of the roll into which the pigtail is coiled is less than 6 cm. If the
radius is less than 6 cm, re-roll the pigtail. Then, check whether the alarm is cleared.
4. If the alarm persists, check whether the pigtail is correctly connected to the optical port.
If... Then...
The pigtail is connected incorrectly Correctly connect the pigtail between the optical
boards in the subrack based on site situations.
Then, check whether the alarm is cleared. If the
The pigtail is connected correctly Go to the next step.
5. Ensure that the pigtail is securely connected to the optical port. Then, check whether the
alarm is cleared.
6. If the alarm persists, check whether the fiber connector is contaminated. For details, see
the Supporting Tasks. If the fiber connector is contaminated, clean the fiber connector. For
details, see the Supporting Tasks.
Check whether the alarm is cleared. If the alarm persists, go to the next step.
7. Use an optical time-domain reflectometer (OTDR) to check whether a fiber cut occurs on
the transmission line and to further locate the position of the fiber cut. For details about
how to use an OTDR, see the OTDR operation guide.
If... Then...
A fiber cut occurs on the transmission line Replace the optical fiber. Check whether
the alarm is cleared. If the alarm persists,
go to Step 5.
No fiber cut occurs on the transmission line Go to Step 5.
Step 5 Cause 4: The local receive board is faulty so that signals fail to be received.

OptiX OSN 8800/6800/3800
1. Replace the optical module if it is pluggable on the alarm-reporting board. For details, see
the Parts Replacement. Replace the alarm-reporting board if the optical module is
unpluggable. For details, see Parts Replacement.
Step 6 Cause 5: The peer transmit board or cross-connect board is faulty so that signals fail to be
transmitted.
1. Replace the optical module if it is pluggable on the alarm-reporting board. For details, see
the Parts Replacement. Replace the alarm-reporting board if the optical module is
unpluggable. For details, see Parts Replacement. Then, check whether the alarm is cleared.
2. If the alarm persists, replace the peer cross-connect board. For details, see the Parts
Replacement.
----End
Related Information
None.
3.40.2 R_LOS (OTN)
Description
Loss of signals at the receive end. This alarm is generated when the receive end receives no
signal.
Attribute
Parameters
None

Services carried at the optical port where this alarm is generated are interrupted.
Possible Causes
l Cause 1 (reported from the client 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.
l Cause 2 (reported from the client side): The line attenuation is excessively high or a fiber
cut occurs.

OptiX OSN 8800/6800/3800
l Cause 4 (reported from the client side): If the board reporting this alarm is a 40G or 100G
board, at least one wavelength has been missing from the receive end of the board.
l Cause 1 (reported from 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.
l Cause 2 (reported from the WDM side): The line attenuation is excessively high or a fiber
cut occurs.
l Cause 3 (reported from the WDM side): The laser of the board at the opposite station is
shut down.
l Cause 4 (reported from the WDM side): The transmit module of the opposite station or
receive module of the local station is faulty.
Procedure
where this alarm is generated.
l Cause 1 (reported from the client 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.
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 Connect the fiber jumper that is

optical port, connected to the upstream board to the
optical port.
A fiber jumper is connected to the Check whether the fiber jumper is

optical port, 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.
l Cause 2 (reported from the client side): The line attenuation is excessively high or there is
a fiber cut.
1. Use a test instrument to test the fiber connection to determine whether a fiber cut
occurs. If a fiber cut occurs, 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 permitted range. For the
optical power specifications of the specific board, see "Technical Specifications" in
the Product Description.

OptiX OSN 8800/6800/3800
If ... Then ...
The receive optical power exceeds See IN_PWR_LOW or IN_PWR_HIGH

the permitted range, to rectify the fault.
The receive optical power is Check the relevant fiber connectors. If the
normal, fiber connectors are dirty, clean or replace the
fiber connectors.
side of the board that reports this alarm. If this alarm persists, the board is faulty. In
this case, replace the board. Replace the board. If this alarm is cleared, the output
power of the client equipment is abnormal. In this case, check for and rectify the fault
on the client equipment.
l Cause 4 (reported from the client side): If the board reporting this alarm is a 40G or 100G
board, at least one wavelength has been missing from the receive end of the board.
1. On the U2000, check whether the receive optical power at the optical port is within
If ... Then ...

The receive optical power is replace the CFP module on the 40G or 100G
normal, board.
assistance.
l Cause 1 (reported from 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.
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 Connect the optical port properly.

optical port,

OptiX OSN 8800/6800/3800
If ... Then ...
A fiber jumper is connected to the Check whether the fiber jumper is

optical port, 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.
l Cause 2 (reported from the WDM side): The line attenuation is excessively high or there
is a fiber cut.
If ... Then ...

The receive optical power is Check the relevant fiber connectors. If there
normal, is any dirt or damage, clean or replace the
fiber connectors.
l Cause 3 (reported from 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.
l Cause 4 (reported from 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, module.

optical modules,

OptiX OSN 8800/6800/3800
assistance.
----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.
l MC-A14 The LWF Board Reports R_LOS
l MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS Alarm
on the Board
l MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
l MC-A125 Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of
a fiber break
l MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm Even
If the Attenuation Is Decreased
l MC-A141 Normal Boards Are Mistakenly Considered Faulty due to Optical Module
Characteristics
l 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
l 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
l 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
l 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
l 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
l 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
l 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
l MC-A243 The TN52TOM Board Reports the R_LOS Alarm When Light Is Received
l MC-A252 Switching of ODUk SNCP Protection Fails

OptiX OSN 8800/6800/3800
l MC-A282 R_LOS Is Reported by a Line Board on a Regular Basis Because of Incorrect

Wavelength Monitoring Configuration on the Electrical Regeneration NE (NG WDM
Equipment)
3.41 R_OOF
Description
Out of frames on the receiving line. This alarm is generated when the heads of five consecutive
frames fail to be detected.
Attribute
Parameters
None

Services carried at the optical port where this alarm is generated are interrupted.
Fault Symptom
Table 3-36 lists the fault symptoms for the R_OOF alarm.
Table 3-36 Fault alarms for the R_OOF alarm
Fault Symptom Cause
The board that reports this alarm also report Cause 1 (reported from the WDM side)
an IN_PWR_LOW alarm.
The board that reports this alarm also reports Cause 2 (reported from the WDM side)
bit error alarms, such as B1_EXC alarm.
NOTE
Possible Causes
l Cause 1 for this alarm generated on the client side: The input signals on the client side are
abnormal and therefore an R_OOF alarm is generated.

OptiX OSN 8800/6800/3800
faulty.
l Cause 1 for this alarm generated on the WDM side: The attenuation of the received signals
is excessively high.
l Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
l Cause 3 for this alarm generated on the WDM side: The transmit side of the opposite station
is faulty.
faulty.
Procedure
l Cause 1 for this alarm generated on the client side: The input signals on the client side are
abnormal and therefore an R_OOF alarm is generated.
between the transmit and receive optical ports on the client side of the board. If this
alarm on the board persists, the board is faulty. In this case, see the alarm handling
NOTICE
Performing a loopback on the board interrupts the services on the board.
2. If the alarm is cleared, 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, module.

optical modules,
l Cause 1 for this alarm generated on the WDM side: The attenuation of the received signals
is excessively high.
1. If the client side reports this alarm, check whether the receive optical power of the
port is within the permitted range on the U2000. For the optical power specifications
of the specific board, see "Technical Specifications" in the Product Description.

OptiX OSN 8800/6800/3800
NOTE
the board.
2. If the receive optical power is not within the permitted range, see the procedure for
handling the IN_PWR_LOW alarm to rectify the fault.
3. If the receive optical power is within the permitted range, see the alarm handling
l Cause 2 for this alarm generated on the WDM side: A large number of bit errors are
generated during the transmission.
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.
l 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
port on the opposite OTU is within the permitted range. For the optical power
specifications of the specific board, see "Technical Specifications" in the Product
Description. For details, see "Querying Optical Power on the U2000" in the
Supporting Tasks.
2. If the transmit optical power exceeds the permitted range, the opposite board is faulty.
Replace the faulty board.
If ... Then ...
modules, module.

optical modules,
3. If the transmit optical power is within the permitted range, see the alarm handling
faulty.
If ... Then ...
modules, module.

OptiX OSN 8800/6800/3800
If ... Then ...

optical modules,
assistance.
----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
l MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
3.42 R_SLIP
Description
Frame slipping on the receive side. The alarm is generated when the phase deviation occurs in
the received service frames of the OSC board.
Attribute
Parameters
None

This alarm affects the services carried by the OSC board. 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-37 lists the fault symptom for the R_SLIP alarm.

OptiX OSN 8800/6800/3800
Table 3-37 Fault symptom for the R_SLIP alarm
Fault Symptom Cause
The board that reports this alarm also report Cause 2: The optical line attenuation is
an IN_PWR_HIGH or IN_PWR_LOW excessively high or the receive optical power
alarm. is excessively high.
NOTE
Possible Causes
l Cause 1: The clock configuration is wrong or the clock signals are not synchronous.
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
l Cause 3: The fibers at the eastward and westward optical ports on the OSC board are
connected reversely.
Procedure
l Cause 1: The clock configuration is incorrect or the clock signals are not synchronous.
1. Check whether the clock configuration is correct. If it is 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 (OCS) and Physical Clock (Packet).
l Cause 2: The optical line attenuation is excessively high or the receive optical power is
excessively high.
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 permitted range.

OptiX OSN 8800/6800/3800
l Cause 3: The fibers at the eastward and westward optical ports on the OSC board are
connected reversely. For example, the fibers for connecting to the TM1 optical port in the
west and the TM2 optical port in the east are connected reversely. See the following figure.
1. If the alarm persists, check the engineering fiber connection diagram to see whether
the fibers at the eastward and the westward optical ports on the OSC board are
connected reversely. If the fiber connection is incorrect, correct it according to the
diagram.
OA
F RM1 TM2 F
I SC2 I
U TM1 RM2 U
OA
1. If the alarm persists, perform a cold reset on the faulty board on the U2000.
If ... Then ...
modules, module.

optical modules,
assistance.
----End
Related Information
Related Cases:
l MC-A7 The R_SLIP Alarm Is Generated Because of Improper Fiber Connections on the
OSC Board

OptiX OSN 8800/6800/3800
3.43 REM_SF
Description
Remote signal failure alarm indication. This alarm is generated when the client side of the board
at the opposite station fails to receive signals (for example, when there is an R_LOS or R_LOF
alarm).
Attribute
Parameters
None

Services carried on the client side of the board are interrupted.
Fault Symptom
Table 3-38 lists the fault symptom for the REM_SF alarm.
Table 3-38 Fault symptom for the REM_SF alarm
Fault Symptom Cause
The OTU board at the opposite station reports Cause 1: An R_LOS, R_LOF, R_LOC,
an R_LOS, R_LOF, R_LOC, LINK_ERR, LINK_ERR, L_SYNC, or a
L_SYNC, or a LOCAL_FAULT alarm. LOCAL_FAULT 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 , LINK_ERR, L_SYNC, or a LOCAL_FAULT
alarm is generated on the client side of the OTU board at the opposite station.
l Cause 2: The client side of the OTU board at the opposite station is faulty.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: An R_LOS, R_LOF, R_LOC , LINK_ERR, L_SYNC, or a LOCAL_FAULT
alarm is generated on the client side of the OTU board at the opposite station.
1. On the U2000, check whether an R_LOS, R_LOF, R_LOC, LINK_ERR, L_SYNC
or LOCAL_FAULT alarm is generated on the client side of the OTU board at the
opposite station. If it is, clear the alarm.
l Cause 2: The client side of the OTU board at the opposite station is faulty.
1. Replace the OTU board at the opposite station.
If ... Then ...
modules, module.

optical modules,
assistance.
----End
Related Information
None.
3.44 REMOTE_FAULT
Description
Fault at the remote end.
Attribute
Parameters
None

If a board receives the REMOTE_FAULT alarm, the services on the board may be interrupted.

OptiX OSN 8800/6800/3800
Fault Symptom
Table 3-39 lists the fault symptom for the REMOTE_FAULT alarm.
Table 3-39 Fault symptom for the REMOTE_FAULT alarm
Fault Symptom Cause
A LOCAL_FAULT alarm is reported from Cause 1: The opposite station receives a

the client side of the board at the opposite end. LOCAL_FAULT alarm.
NOTE
Possible Causes
l Cause 1: The LOCAL_FAULT alarm is reported at the opposite station when 10GE LAN
(BIT transparent transmission) services are received.
The client side of the 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.
Detects and reports the Detects and reports a fault

LOCAL_FAULT alarm at the local end alarm
O O
router side
T
side side
T
side
router
U U
Station A Station B
Detects and reports a fault Detects and reports the
at the remote end alarm REMOTE_FAULT alarm
l Cause 2: The data equipment on the client side is malfunctioning.
Procedure
l Cause 1: The LOCAL_FAULT alarm is reported at the opposite station when 10GE LAN
(BIT transparent transmission) services are received.
1. Check whether the LOCAL_FAULT alarm is reported at the opposite station. If it is,
clear the LOCAL_FAULT alarm at the opposite station.
l Cause 2: The data equipment on the client side is malfunctioning.
1. Rectify the fault on the data equipment.

OptiX OSN 8800/6800/3800
assistance.
----End
Related Information
None.
3.45 SECU_ALM
Description
Invalid access. This alarm is generated when a user fails to log in again after four consecutive
login failures.
Attribute
Major Security alarm
Parameters
None.

The alarm automatically clears and has no impact on the system.
Fault Symptom
None.
NOTE
Possible Causes
l Cause 1: Authorized login. For example, the password is incorrect.
Procedure
l Cause 1: Authorized login. For example, the password is incorrect.
1. Verify that the user name and password are correct. If they are incorrect, use the correct
ones to log in again.

OptiX OSN 8800/6800/3800
2. If the alarm persists after invalid users are cleared, reset the board or remove or reinsert
the board. If the alarm persists, replace the board.
----End
Related Information
None.
3.46 SUBRACK_ID_CONFLICT
Description
Conflict of subrack IDs. In the case of the master-slave subrack mode, this alarm is generated
when the master subrack detects that the DIP switch settings of the slave subracks are repeated.
Attribute
Parameters
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-40 lists the fault symptom for the SUBRACK_ID_CONFLICT alarm.
Table 3-40 Fault symptom for the SUBRACK_ID_CONFLICT alarm
Fault Symptom Cause
The board may report the BD_STATUS, l Cause 1: In the case of the master-slave
COMMUN_FAIL, and WRG_BD_TYPE subrack mode, multiple master subracks
alarms at the same time. 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.

OptiX OSN 8800/6800/3800
NOTE
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.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
subracks are repeated.
Procedure
l Perform all the following steps regardless of whether the SUBRACK_ID_CONFLICT
alarm is cleared during the operations.
l Cause 1: In the case of the master-slave subrack mode, multiple master subracks exist in
the system.
1. There should be only one master subrack in the system. Identify the redundant master
subracks according to the actual networking and then remove them.
2. Perform a warm reset on the system control board in the master subrack.
3. Perform a warm reset on all boards on the NE.
l Cause 2: In the case of the master-slave subrack mode, the DIP switch settings of two slave
subracks are repeated.
1. Disconnect one slave subrack from the master subrack and reset the ID of this slave
subrack by changing the DIP switch setting on the system control board. In this case,
the IDs of the two slave subracks are different.
2. Perform a warm reset on the system control board in the master subrack on the NE.
3. After the subrack ID is changed, perform a warm reset on all the boards in the subrack.
assistance.
----End
Related Information
For OptiX OSN 8800 and OptiX OSN 6800, see "Master-Slave Subrack" in the Feature
Description.
3.47 SUM_INPWR_LOW
Description
Input optical power of multiplexed wavelengths being excessively low. This alarm is generated
when the input optical power of multiplexed signals is lower than the threshold.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

The output optical signals of a single channel of the board may be lost. As a result, the services
in use may have bit errors or even are interrupted.
Fault Symptom
Table 3-41 lists the fault symptom for the SUM_INPWR_LOW alarm.
Table 3-41 Fault symptom for the SUM_INPWR_LOW alarm
Fault Symptom Cause
The upstream board reports an Cause 1: The output optical power of the
OUT_PWR_LOW alarm. upstream station decreases. Therefore, 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. Therefore, the input
optical power of the local station is excessively low.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers, fiber connectors,
or optical attenuators are dirty.
Procedure
l Cause 1: The output optical power of the upstream station decreases. Therefore, the input
optical power of the local station is excessively low.
1. 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

OptiX OSN 8800/6800/3800
board is excessively low, adjust the output optical power of the board to a value within
2. If the alarm persists, replace the board whose output optical power is excessively low.
Replace the board.
l Cause 2: The line attenuation is excessively high, or related fiber jumpers, fiber connectors,
or optical attenuators 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 port on the board that reports this alarm. If it is, 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 it is, adjust the attenuation of the VOA to a proper value.
3. If the alarm persists, check whether related fibers, fiber connectors, or optical
attenuators are dirty. If they are, 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.
If ... Then ...
modules, module.

optical modules,
assistance.
----End
Related Information
None.
3.48 SWDL_NEPKGCHECK
Description
Loss of files. This alarm is generated when the NE software checks the software package and
finds that a file in a partition of the system control board software package is lost and the file

OptiX OSN 8800/6800/3800
cannot be restored from the related file in another partition. This alarm clears when the NE
software checks the software package and finds the file during next preventive maintenance.
NOTE
The system control board checks the software package each time when the system control board starts up and
when the periodical check is performed. The periodical check is performed every hour by default.
Attribute
Critical Process alarm
Parameters
None

Because a file in the NE software package is lost, some functions of the NE may be affected.
Fault Symptom
Table 3-42 lists the fault symptom for the SWDL_NEPKGCHECK alarm.
Table 3-42 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
software package of the system control board
is lost and cannot be restored.
The SWDL_NEPKGCHECK alarm Cause 2: A file in a partition in the software

disappears after being reported for a certain package of the system control board is lost
period and is reported again. 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 software package of the system control board
is lost and cannot be restored.
l Cause 2: A file in a partition in the software package of the system control board is lost and
the file cannot be restored from the associated file in another partition.

OptiX OSN 8800/6800/3800
Procedure
l Causes 1 and 2: The same file in two partitions in the software package of the system control
board is lost and cannot be restored. A file in a partition in the software package of the
system control board is lost and the file cannot be restored from the associated file in another
partition.
1. On the U2000, select the software package of the same version to perform package
loading.
2. After the package is successfully loaded, the alarm clears. If the alarm persists, contact
Huawei for assistance.
----End
Related Information
None
3.49 TD
Description
Transmitter being 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
Parameters
None.

The board laser may not work properly, the output light of the laser is of low quality, bit errors
are generated, or even services are interrupted.
Fault Symptom
None.
NOTE

OptiX OSN 8800/6800/3800
Possible Causes
Cause 1: The laser is aging.
Procedure
l Cause 1: The laser is aging.
1. Check whether board that reports this alarm supports pluggable optical modules.
If ... Then ...
modules, module.

optical modules,
1. Replace the faulty board. Refer to Replace the board.
assistance.
----End
Related Information
In a cooled optical module that adopts the automatic level control (ALC) function, the laser is
aged after long-term operation and 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
Working temperature crossing the threshold. This alarm is generated when the system detects
that the board working temperature is higher than the upper threshold or lower than the lower
threshold.
Attribute

OptiX OSN 8800/6800/3800
Parameters
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 period of time, bit errors may be generated and services may
be interrupted. Therefore, the TEMP_OVER alarm must be handled in a timely manner.
Fault Symptom
Table 3-43 lists the fault symptom for the TEMP_OVER alarm.
Table 3-43 Fault symptom for the TEMP_OVER alarm
Fault Symptom Cause
On the NMS, the adjusting mode of the fan Cause 1: The set rotating speed of the fan
board is set to Adjustable Speed Mode and board is excessively low.
the rotating speed is set to Low Speed or
Medium Speed.
The fan board reports the FAN_FAIL or Cause 2: The fan board is faulty.
FAN_FAULT alarm.
The adjusting mode of the fan board is set to Cause 3: The air filter is excessively dusty.
Auto Speed Mode and the rotating speed is
set to High Speed. In addition, no other
alarms are generated.
The fan board reports the BD_STATUS Cause 5: The fan is not in position.
alarm.
NOTE
Possible Causes
The possible causes of the TEMP_OVER alarm are as follows:

OptiX OSN 8800/6800/3800
l Cause 1: The set rotating speed of the fan board is excessively low.
l Cause 2: The fan board is faulty.
l Cause 3: The air filter is excessively dusty.
l Cause 4: The ambient temperature is excessively high or excessively low due to a cooler
or heater equipment fault.
l Cause 5: The fan is not in position.
Procedure
l 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.
l Cause 1: The set rotating speed of the fan board is excessively low.
1. Check the adjusting mode and rotating speed of the fan board on the U2000. 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.
l Cause 2: The fan board is faulty.
1. If the alarm persists, check whether the FAN_FAIL or FAN_FAULT alarm is
generated on the fan board. If it is, handle the alarm immediately.
l Cause 3: The air filter is excessively dusty.
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 and clean the air filter.
3. Check whether the alarm is cleared. If the alarm persists, see Cause 4.
l Cause 4: 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.
l Cause 5: The fan is not in position.
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.

OptiX OSN 8800/6800/3800
1. Replace the board that reports the alarm. Refer to Replace the board.
----End
Related Information
Related Cases:
l MC-A134 How to Resolve The Problem of The OptiX BWS 1600G Subrack Reports The
TEMP_OVER Alarm
l MC-A146 The TN11LOM Board Intermittently Reports the TEMP_OVER Alarm
l MC-A225 Services on Boards Are Interrupted And The Boards Report The HARD_BAD
Alarm Due to Dusty Air Filters
3.51 TF
Description
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
Parameters
None

If a laser transmission failure occurs, services are interrupted.
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.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: The laser module is damaged, or the laser is aging.
If ... Then ...
modules, module.

optical modules,
1. If the alarm persists, the board that reports the alarm may be faulty. Replace the faulty
board. Refer to Replace the board.
assistance.
----End
Related Information
In a cooled optical module that adopts automatic level control (ALC), the laser ages after a long-
term operation and therefore the laser emitting efficiency decreases. To ensure constant output
optical power, the laser bias current needs to be increased. Therefore, the bias current is an index
that reflects the aging degree of the laser.
Related Cases:
l MC-A12 Certain Boards Report the TF Alarm Transiently
3.52 TS_CFG_MISMATCH
Description
Timeslot mismatch. 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.
Attribute
Major Processing

OptiX OSN 8800/6800/3800
Parameters
None

If timeslot mismatch occurs, services 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 it is 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 it is not, modify the timeslot configuration of the opposite board
or the local board according to the actual service.
assistance.
----End
Related Information
None.
3.53 WRG_BD_TYPE
Description
Incorrect board type. This alarm is generated when the logical board and the physical board are
inconsistent.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

If the type of the logical board is different from the type of the physical board, the board cannot
work properly, affecting services.
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.
Procedure
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.
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 it is 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.
If the type of the physical board is inappropriate, remove the existing board and
insert a board of the correct type.

OptiX OSN 8800/6800/3800
assistance.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 4 Clearing Alarms
4 Clearing Alarms
About This Chapter
This topic describes information related to alarm handling, including alarm descriptions, alarm
parameters, impact 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 optical-
layer 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 resets (either cold or warm). Warm and cold resets have
different impact on services.
l Reset of the system control board: A warm reset of the system control is a restart of the
upper-layer software, which neither updates the FPGA or hardware data nor interrupts
services. A cold reset of the system control may result in reconfiguration of the key
hardware, such as FPGA reloading, and the upper-layer software need to be restarted.
l Reset of other boards: A warm reset on other boards does not affect running services while
a cold reset on other boards does. A mis-reset of such a board affects the communication
between this board and the system control 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 ALS_TRIGGERED
4.6 ALM_ALS

OptiX OSN 8800/6800/3800
4.7 ALM_GFP_dCSF
4.8 ALM_GFP_dLFD
4.9 ALM_HANGUP
4.10 TC_OEI
4.11 TC_REI
4.12 APE_ADJUST_FAIL
4.13 APE_ADJUST_PEND
4.14 APS_FAIL
4.15 APS_INDI
4.16 APS_MANUAL_STOP
4.17 ASE_NOT_CALIBRATE
4.18 AU_AIS
4.19 AU_LOP
4.20 B1_SD
4.21 BD_LEDTEST
4.22 B2_EXC
4.23 B2_SD
4.24 B3_EXC
4.25 B3_EXC_VC3
4.26 B3_EXC_VC4
4.27 B3_SD
4.28 B3_SD_VC3
4.29 B3_SD_VC4
4.30 BD_NOT_INSTALLED
4.31 BD_STATUS
4.32 BIOS_STATUS
4.33 BWUTILIZATION_OVER
4.34 CFCARD_FAILED
4.35 BDID_ERROR
4.36 C2_VCAIS
4.37 CHAN_ADD

OptiX OSN 8800/6800/3800
4.38 CHIP_ABN
4.39 CLIENT_PROT_NOTSTART
4.40 CLIENT_PORT_STA_INDI
4.41 CLK_LOCK_FAIL
4.42 CLK_NO_TRACE_MODE
4.43 COM_EXTECC_FULL
4.44 CRC4_CROSSTR
4.45 DB_RESTORE_FAIL
4.46 DBPS_ABNORMAL
4.47 DBMS_DELETE
4.48 DBMS_ERROR
4.49 DBMS_PROTECT_MODE
4.50 DCM_INSUFF
4.51 DCNSIZE_OVER
4.52 DERIVED_PWR_ERROR
4.53 DLAG_PROTECT_FAIL
4.54 DSP_LOAD_FAIL
4.55 EFI_TYPE_MISMATCH
4.56 ERPS_IN_PROTECTION
4.57 ETH_APS_LOST
4.58 ETH_APS_PATH_MISMATCH
4.59 ETH_APS_SWITCH_FAIL
4.60 ETH_APS_TYPE_MISMATCH
4.61 ETH_CFM_AIS
4.62 ETH_CFM_LOC
4.63 ETH_CFM_MISMERGE
4.64 ETH_CFM_MACSTATUS
4.65 ETH_CFM_RDI
4.66 ETH_CFM_UNEXPERI
4.67 ETH_EFM_DF
4.68 ETH_EFM_EVENT
4.69 ETH_EFM_LOOPBACK

OptiX OSN 8800/6800/3800
4.70 ETH_EFM_REMFAULT
4.71 ETH_LINK_DOWN
4.72 ETH_LOS
4.73 ETH_MISCONNECT
4.74 ETH_NO_FLOW
4.75 ETH_SERVICE_CONFIG_FAIL
4.76 ETHOAM_DISCOVER_FAIL
4.77 ETHOAM_RMT_CRIT_FAULT
4.78 ETHOAM_RMT_LOOP
4.79 ETHOAM_RMT_SD
4.80 ETHOAM_SELF_LOOP
4.81 ETHOAM_VCG_SELF_LOOP
4.82 EX_ETHOAM_MPID_CNFLCT
4.83 EXT_MODULE_OFFLINE
4.84 EXT_SYNC_LOS
4.85 EXT_TIME_LOC
4.86 FAN_FAIL
4.87 FAN_FAULT
4.88 FDBSIZEALM_ELAN
4.89 FEATURE_WITHOUT_LICENSE
4.90 FC_8B10BERR_OVER
4.91 FCS_ERR
4.92 FEC_LOF
4.93 FEC_OOF
4.94 FIBERTYPE_MIS
4.95 FLOW_OVER
4.96 FPGA_ABN
4.97 FSELECT_STG
4.98 FWD_PKT_LOSS
4.99 GAINDATA_MIS
4.100 GFP_UPM
4.101 HARD_BAD

OptiX OSN 8800/6800/3800
4.102 HARD_ERR
4.103 HARD_NONSUPPORT
4.104 HP_LOM
4.105 HP_RDI
4.106 HP_REI
4.107 HP_SLM
4.108 HP_TIM
4.109 HP_UNEQ
4.110 HSC_UNAVAIL
4.111 IN_PWR_ABN
4.112 INSERTION_LOSS_HIGH
4.113 INTRA_OTU_STA_INDI
4.114 IPA_SHUT
4.115 J0_MM
4.116 K1_K2_M
4.117 K2_M
4.118 L_SYNC
4.119 LAG_DOWN
4.120 LAG_MEMBER_DOWN
4.121 LAG_PORT_FAIL
4.122 LAG_VC_PORT_FAIL
4.123 LAN_LOC
4.124 LASER_HAZARD_WARNING
4.125 LASER_MOD_ERR
4.126 LASER_SHUT
4.127 LCS_DAYS_OF_GRACE
4.128 LCS_EXPIRED
4.129 LCS_FILE_NOT_EXIST
4.130 LCAS_FOPR
4.131 LCAS_FOPT
4.132 LCAS_PLCR
4.133 LCAS_PLCT

OptiX OSN 8800/6800/3800
4.134 LCAS_TLCR
4.135 LCAS_TLCT
4.136 LOCAL_FAULT
4.137 LOCK_CUR_FAIL
4.138 LOCKPOW_MIS
4.139 LP_RDI_VC3
4.140 LP_SLM_VC3
4.141 LP_UNEQ_VC3
4.142 LPT_RFI
4.143 LSR_BCM_ALM
4.144 LSR_COOL_ALM
4.145 LSR_INVALID
4.146 LSR_NO_FITED
4.147 LTI
4.148 MAC_FCS_EXC
4.149 MAINBD_SUBBD_MISMATCH
4.150 MCLAG_CFG_MISMATCH
4.151 MCSP_PATH_LOCV
4.152 MOD_COM_FAIL
4.153 MODULE_ADJUST_FAIL
4.154 MODULE_COOLCUR_OVER
4.155 MODULE_RATE_MISMATCH
4.156 MODULE_TEMP_OVER
4.157 MODULEFILE_UPDATE_FAIL
4.158 MPLS_PW_AIS
4.159 MPLS_PW_LOCV
4.160 MPLS_PW_OAMFAIL
4.161 MPLS_PW_RDI
4.162 MPLS_PW_SD
4.163 MPLS_PW_SF
4.164 MPLS_PW_UNEXPMEG
4.165 MPLS_PW_UNEXPMEP

OptiX OSN 8800/6800/3800
4.166 MPLS_PW_UNEXPPER
4.167 MPLS_TUNNEL_AIS
4.168 MPLS_TUNNEL_LOCV
4.169 MPLS_TUNNEL_OAMFAIL
4.170 MPLS_TUNNEL_RDI
4.171 MPLS_TUNNEL_SD
4.172 MPLS_TUNNEL_SF
4.173 MPLS_TUNNEL_UNEXPMEG
4.174 MPLS_TUNNEL_UNEXPMEP
4.175 MPLS_TUNNEL_UNEXPPER
4.176 MS_APS_INDI_EX
4.177 MS_CROSSTR
4.178 MS_REI
4.179 MS_SNCP_PS
4.180 MS_SNCP_STA_INDI
4.181 MUT_TLOS
4.182 MULTI_RPL_OWNER
4.183 NEBD_XC_DIF
4.184 NESF_LOST
4.185 NESTATE_INSTALL
4.186 NO_BD_PARA
4.187 NO_BD_SOFT
4.188 NO_ELABEL
4.189 NODEID_MM
4.190 NTP_SYNC_FAIL
4.191 NULL_SEND
4.192 OA_HIGH_GAIN
4.193 OCH_FDI
4.194 OCH_FDI_O
4.195 OCH_FDI_P
4.196 OCH_LOS_P
4.197 OCH_OCI

OptiX OSN 8800/6800/3800
4.198 OCH_SSF
4.199 OCH_SSF_O
4.200 OCH_SSF_P
4.201 ODU_AIS
4.202 ODU_LCK
4.203 ODU_OCI
4.204 ODU_SNCP_STA_INDI
4.205 ODUk_LOFLOM
4.206 ODUk_PM_LCK
4.207 ODUk_PM_OCI
4.208 ODUk_PM_TIM
4.209 ODUk_TCMn_AIS
4.210 ODUk_TCMn_BDI
4.211 ODUk_TCMn_DEG
4.212 ODUk_TCMn_EXC
4.213 ODUk_TCMn_LCK
4.214 ODUk_TCMn_LTC
4.215 ODUk_TCMn_OCI
4.216 ODUk_TCMn_SSF
4.217 ODUk_TCMn_TIM
4.218 ODUKSP_PS
4.219 ODUKSP_STA_INDI
4.220 OH_LOOP
4.221 OLP_PS
4.222 OLP_STA_INDI
4.223 OMS_BDI
4.224 OMS_BDI_O
4.225 OMS_BDI_P
4.226 OMS_FDI_O
4.227 OMS_FDI_P
4.228 OMS_LOS_P
4.229 OMS_SSF

OptiX OSN 8800/6800/3800
4.230 OMS_SSF_O
4.231 OMS_SSF_P
4.232 OOL
4.233 OOS_LOST
4.234 OPA_FAIL_INDI
4.235 OPU1_MSIM
4.236 OPU1_VCAT_SQM
4.237 OPU1_VCAT_VcPLM
4.238 OPU2_MSIM
4.239 OPU3_MSIM
4.240 OPU4_MSIM
4.241 OPUk_CSF
4.242 OPUk_PLM
4.243 OSC_BDI
4.244 OSC_DEG
4.245 OSC_RDI
4.246 OTS_BDI
4.247 OTS_BDI_O
4.248 OTS_BDI_P
4.249 OTS_LOS_O
4.250 OTS_LOS_P
4.251 OTS_TIM
4.252 OTU_AIS
4.253 OTU_LOF
4.254 OTU_LOM
4.255 OTUk_AIS
4.256 OTUk_BDI
4.257 OTUk_DEG
4.258 OTUk_EXC
4.259 OTUk_LOM
4.260 OTUk_TIM
4.261 OUT_PWR_ABN

OptiX OSN 8800/6800/3800
4.262 OUT_PWR_LOW
4.263 OWSP_PS
4.264 OWSP_STA_INDI
4.265 PASSWORD_NEED_CHANGE
4.266 PATCH_ACT_TIMEOUT
4.267 PATCH_DEACT_TIMEOUT
4.268 PATCH_PKGERR
4.269 PM_BDI
4.270 PM_BEI
4.271 PM_BIP8_OVER
4.272 PM_BIP8_SD
4.273 PM_TIM
4.274 PORT_EXC_TRAFFIC
4.275 PORTSWITCH_FAIL
4.276 POWER_ABNORMAL
4.277 POWER_DIFF_OVER
4.278 PRBS_LSS
4.279 PTP_SOURCE_SWITCH
4.280 PTP_TIMESTAMP_ABN
4.281 PUM_BCM_ALM
4.282 PUM_TEM_ALM
4.283 PW_NO_TRAFFIC
4.284 PWAPS_LOST
4.285 PWAPS_PATH_MISMATCH
4.286 PWAPS_SWITCH_FAIL
4.287 PWAPS_TYPE_MISMATCH
4.288 R_LOC
4.289 RELAY_ALARM_CRITICAL
4.290 RELAY_ALARM_IGNORE
4.291 RELAY_ALARM_MAJOR
4.292 RELAY_ALARM_MINOR

OptiX OSN 8800/6800/3800
4.293 REM_SD
4.294 RL_CRITICAL_HI
4.295 RL_CRITICAL_LOW
4.296 RM_RLOS
4.297 RS_CROSSTR
4.298 RTC_FAIL
4.299 RX_POWER_ABNORMAL
4.300 S1_SYN_CHANGE
4.301 SCC_LOC
4.302 SEC_RADIUS_FAIL
4.303 SERVICE_TYPE_EXCEED_LICENSE
4.304 SERVICE_CAPACITY_EXCEED_LICENSE
4.305 SHELF_AREA_POWER_OVER
4.306 SPAN_LOSS_HIGH
4.307 SPAN_LOSS_LOW
4.308 SLAVE_WORKING
4.309 SM_BDI
4.310 SM_BEI
4.311 SM_BIP8_OVER
4.312 SM_BIP8_SD
4.313 SM_IAE
4.314 SM_TIM
4.315 SNCP_FAIL
4.316 SO_SK_MISMATCH
4.317 SPEED_OVER
4.318 SRV_SHUTDOWN_LD
4.319 SSL_CERT_NOENC
4.320 SSM_LOS
4.321 SSM_QL_FAILED
4.322 STORM_CUR_QUENUM_OVER
4.323 SUBRACK_COMM_PS
4.324 SUBRACK_ID_MISMATCH

OptiX OSN 8800/6800/3800
4.325 SUBRACK_LOOP
4.326 SUBRACK_TYPE_MISMATCH
4.327 SUM_INPWR_HI
4.328 SW_SNCP_PS
4.329 SW_SNCP_STA_INDI
4.330 SWDL_ACTIVATED_TIMEOUT
4.331 SWDL_AUTOMATCH_INH
4.332 SWDL_BD_EXCLUDE
4.333 SWDL_CHGMNG_NOMATCH
4.334 SWDL_COMMIT_FAIL
4.335 SWDL_INPROCESS
4.336 SWDL_PKG_NOBDSOFT
4.337 SWDL_PKGVER_MM
4.338 SWDL_ROLLBACK_FAIL
4.339 SYN_BAD
4.340 SYNC_C_LOS
4.341 SYNC_DISABLE
4.342 SYNC_F_M_SWITCH
4.343 SYNC_LOCKOFF
4.344 SYNC_FAIL
4.345 SYSLOG_COMM_FAIL
4.346 SYSPARA_CFDB_NOSAME
4.347 T_LOSEX
4.348 T_SLIP
4.349 TEM_HA
4.350 TEM_LA
4.351 TEST_STATUS
4.352 THUNDERALM
4.353 TIME_LOS
4.354 TIME_LOCK_FAIL
4.355 TIME_NO_TRACE_MODE
4.356 TR_LOC

OptiX OSN 8800/6800/3800
4.357 TU_AIS_VC3
4.358 TU_LOP_VC3
4.359 TUNNEL_APS_DEGRADED
4.360 VCTRUNK_NO_FLOW
4.361 VCAT_LOA
4.362 VCAT_LOM_VC3
4.363 VCAT_LOM_VC4
4.364 VLAN_SNCP_PS
4.365 VOADATA_MIS
4.366 W_R_FAIL
4.367 WAVE_ADD_ABN
4.368 WAVE_DROP_ABN
4.369 WAVEDATA_MIS
4.370 WAVELEN_OVER
4.371 XC_UNSWITCH

OptiX OSN 8800/6800/3800
4.1 AD_CHECK_FAIL
Description
Self-check failure of the analog to digital (AD) chip. This alarm is reported when the AD chip
on the board is faulty.
Attribute
Parameters
Parameter 1 Indicates the serial number of an AD chip. For example, 0x01 indicates chip 1.

l This alarm may affect services.
l 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 on the U2000.
Step 2 If the alarm persists, the board that reports the alarm may be faulty. Replace the board.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.2 ALC_ADJUST_FAIL
Description
ALC link adjustment failure. This alarm is generated when the ALC link adjustment fails.
Attribute
Parameters
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
node.
l 0x04: The link operation times out.
l 0x05: The node operation times out.
l 0x06: The node status is incorrect. That is, though receiving
adjustment frames, the node is not in the pre-adjustment state
l 0x07: The node does not permit another adjustment because more than
two adjustments have been performed.
l 0x08: The link configuration is in disorder.

OptiX OSN 8800/6800/3800
Name Meaning
Parameters 3 and 4 l Indicate the slot of the no-response board when parameter 2 is 0x01.
l Indicate the slot ID of the board and the optical port reporting the alarm
when parameter 2 is 0x02.
l When parameter 2 is 0x03, parameter 3 indicates the link number and
parameter 4 is invalid.
l Indicate the timeout period when parameter 2 is 0x04.
l Indicate the timeout period when parameter 2 is 0x05.
l When parameter 2 is 0x06, parameter 3 indicates the node status and
parameter 4 is invalid.
Parameters 5 and 6 l Indicate the number of the port that has no response when parameter
2 is 0x01.
l Indicate the number of the port that generates the alarm when
parameter 2 is 0x02.
Parameters 7 and 8 Indicates the command when parameter 2 is 0x01.

The line attenuation is excessively large 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.
l Alarms such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, and R_LOS occur on the
equipment.
l The node receives adjustment frames but no link is on the node.
l The link adjustment operation times out.
l The node adjustment operation times out.
l The node is in an incorrect state. That is, though receiving adjustment frames, the node is
not in the pre-adjustment state.
l The node does not permit another adjustment because more than two adjustments have
been performed.
l 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 cannot be empty.

OptiX OSN 8800/6800/3800
l When configuring the source node, make sure that the same optical port is not configured
for the detection equipment and reference equipment.
Step 2 Check whether the adjustment on the adjustment node is within the range.
Step 3 Check whether other alarms, such as WRG_BD_TYPE, BD_STATUS, MUT_LOS, or R_LOS,
are generated on the current equipment on the U2000. If an alarm is generated on the equipment,
first rectify the alarm.
Step 4 If the adjustment times out, perform an adjustment again.
----End
Related Information
For details, see "Automatic Level Control (ALC)" in the Feature Description.
4.3 ALC_WAIT_ADJUST
Description
Waiting for adjustment due to an ALC link exception. This alarm is generated at the source node
when the ALC link in manual mode is faulty and needs to be adjusted.
Attribute
Parameters
Name Meaning
Parameter 2 Indicates the ID of a faulty node.
Parameters 3, 4, 5, and 6 Indicate the NE IDs of the faulty nodes.

The line attenuation is excessively large and may affect signal quality.

OptiX OSN 8800/6800/3800
Possible Causes
l Currently, the ALC is in the manual mode. When the ALC link is faulty and needs to be
adjusted, this alarm is reported.
Procedure
Step 1 Manually start an ALC adjustment.
Step 2 If the ALC_ADJUST_PEND alarm persists and simultaneously the ALC_ADJUST_FAIL alarm
is reported, clear the alarms by referring to the procedure for clearing the ALC_ADJUST_FAIL
alarm.
----End
Related Information
4.4 ALS_ACTIVE
Description
Automatic laser shutdown (ALS) occurred alarm. This alarm is generated when the laser is turned
off using the ALS function.
Attribute
Minor Service alarm
Parameters
None

When the alarm is generated, the lasers on the related boards are turned off automatically.
Possible Causes
l The input signals on the client side are missing at the local station or opposite station.
l The WDM side of the related boards is faulty or reports a (Lower Order ODUk, LO ODUk)
ODUk_PM_BDI alarm.
Procedure
Step 1 Check the configuration of the ALS function, and determine the triggering condition of the ALS
function. For details, see "ALS" in the Feature Description.

OptiX OSN 8800/6800/3800
Step 2 On the U2000, query whether the R_LOS alarm is generated on the client side of the related
boards. If it is, handle the alarm according to the corresponding handling procedure.
Step 3 On the U2000, query whether the R_LOS, OTUk_AIS, OTUk_LOF, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, ODUk_TCMn_AIS, ODUk_TCMn_OCI,
ODUk_TCMn_LCK, or (Lower Order ODUk, LO ODUk) ODUk_PM_BDI alarm is generated
on the WDM side of the related boards. If it is, handle the alarm according to the corresponding
handling procedure.
----End
Related Information
The OTU board and tributary board of the system provide the ALS function. For details, see
"ALS" in the Feature Description.
4.5 ALS_TRIGGERED
Description
This alarm is generated when the laser on a Raman board is turned off by the automatic laser
shutdown (ALS) function.
Attribute
Parameters
None

The services that traverse this board may be interrupted.
Possible Causes
The laser on the CRPC board is shut down by ALS function.
Procedure
Step 1 Check the communication between the CRPC board and system control board.
Step 2 Restart the intelligent power adjustment (IPA) function. The laser on the OA board on the
upstream NE emits probe light to turn on the laser on the CRPC board and restore the services.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.6 ALM_ALS
Description
The ALM_ALS is an alarm indicating automatic laser shutdown. This alarm is generated when
the laser is automatically shut down due to the R_LOS alarm generated for the optical port.
Attribute
Parameters
None.

This alarm indicates that the automatic laser shutdown function is enabled, which does not affect
the system.
Possible Causes
A user has enabled the automatic laser shutdown function.
Procedure
Step 1 If the user disables the automatic laser shutdown function, this alarm will not be reported.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.7 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that GFP client signals are lost. When the source
receives no GFP client signal, it sends a management frame to the sink. This alarm is generated
when the sink receives the management frame.
Attribute
Parameters
None.

When this alarm occurs during data transmission, services will lose packets or be interrupted.
Possible Causes
l The source interface module is incorrect. For example, the optical module does not exist
or match, or the optical or electrical signal is lost.
l The source physical link fails and cannot receive physical signals.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port that reports the alarm.
Step 2 Check whether the physical link where the source VCTRUNK port resides is functioning
properly. If the physical link fails due to optical-fiber damage, replace the optical fiber and check
whether the ALM_GFP_dCSF alarm is cleared.
Step 3 If the alarm persists, check whether the source interface module runs properly. If the source
interface module runs improperly, replace it.
Step 4 If the alarm persists, replace the board that reports the alarm.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.8 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the generic framing procedure (GFP) frame
is out of frame. This alarm is generated when the GFP state machine escapes from the SYNC
state, and is cleared when the state machine enters the SYNC state again.
Attribute
Parameters
None.

During data transmission, if the board fails to align the GFP frame, the services are interrupted.
Possible Causes
l Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends
are inconsistent.
l Cause 2: The performance of the service transmission line degrades.
l Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The settings of timeslots and other parameters of the VCTRUNKs at both ends are
inconsistent.
1. Check whether the number of uplink (downlink) timeslots bound with the local VCTRUNK
is consistent with the number of downlink (uplink) timeslots bound with the peer
VCTRUNK.
If... Then...
The number of timeslots is Modify Number of Bound Paths at either end

inconsistent to ensure that the number of timeslots is
consistent. Then, check whether the
ALM_GFP_dLFD alarm is cleared. If the
The number of timeslots is consistent Go to the next step.

OptiX OSN 8800/6800/3800
2. Double-click a desired NE. In the NE Explorer, choose Configuration > SDH Service
Configuration from the navigation tree.
3. Check whether the number of timeslots bound with the VCTRUNK matches cross-
connection settings.
If... Then...
The number of timeslots bound with Reconfigure the cross-connections or the

the VCTRUNK does not match cross- timeslots to be bound to the VCTRUNK. Then,
connection settings check whether the ALM_GFP_dLFD alarm is
cleared. If the alarm persists, go to the next
step.
The number of timeslots bound with Go to the next step.

the VCTRUNK matches cross-
connection settings
4. Check whether the service level is consistent between the SDH cross-connections at both
ends. If the service level is inconsistent, for example, the service level of the SDH cross-
connections at the local end is VC4 but that at the peer end is VC4-16C, reconfigure the
service level of SDH cross-connections to keep its consistency between both ends.
5. Check whether the ALM_GFP_dLFD alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The performance of the service transmission line degrades.
1. Check the transmission link for bit error and optical power alarms and errored block
performance events, which are generated due to loose or contaminated fiber connectors,
faulty optical fiber cables, or poor contact between optical components.
If... Then...
Alarms, such as B3_EXC, B3_SD, Clear the alarms or events. Then, check
IN_PWR_HIGH, and IN_PWR_LOW, whether the ALM_GFP_dLFD alarm is
or events, such as RSBBE, MSBBE, and cleared. If the alarm persists, go to Step 3.
HPBBE exist
None of the preceding alarms or Go to Step 3.

performance events exists
Step 3 Cause 3: A certain board is faulty.

1. Replace the board that reports the alarm.
2. Then, check whether the alarm is cleared. If the ALM_GFP_dLFD alarm persists, contact
Huawei technical support engineers to handle this alarm.
----End
Related Information
Cell Delimitation State Machine
The cell delimitation state machine is available in three states: HUNT, PRESYNC, and SYNC.
In the HUNT state, the state machine hunts the position of delimitating cells in the BYTE BY

OptiX OSN 8800/6800/3800
BYTE manner. After finding a correct HCS, the state machine changes to the PRESYNC state.
In the PRESYNC state, the state machine locks the position of delimitating 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
Orderwire phone being 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
Parameters
None

l The ALM_HANGUP alarm does not affect the services or communication of the NE.

OptiX OSN 8800/6800/3800
l 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 the orderwire phone.
Possible Causes
l The orderwire phone is in the off-hook state for a long time.
l 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 alarm persists, perform a cold reset on the optical supervisory channel board (For example,
SC2 board) on the U2000.
Step 3 If the ALM_HANGUP alarm persists, the board hardware may be faulty. Replace the board.
----End
Related Information
None
4.10 TC_OEI
Description
The TC_OEI is an outgoing error indication in the tandem connection. When the accumulated
number of tandem connection output errors received at the sink within one second is greater
than 0, the TC_OEI alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the actual optical port number of the board.

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 2, Parameter 3 Indicates the AU-4 path number.
For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter

3 = 0x01. In this case, the TC_OEI alarm is reported from path 1
of optical port 1 on the board.

When the TC_OEI alarm occurs, the services at the local station are not affected. This alarm
just shows that some bit errors occur in the signals output from the TCM sink.
Possible Causes
The possible cause of the TC_OEI alarm is as follows:
Some bit errors occur in the signals output from the TCM sink.
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 the fiber connector is inserted firmly.
Then check whether the 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.
NOTICE
If the services 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.
NOTICE
Step 5 If the alarm persists, replace the line board that generates the alarm at the sink, and then check
whether the alarm is cleared.

OptiX OSN 8800/6800/3800
Step 6 If the alarm persists, possibly the performance of other inevitable carrier networks is degraded.
In this case, ask the relevant carrier for the solution.
----End
Related Information
None.
4.11 TC_REI
Description
The TC_REI is a remote error indication in the tandem connection. When the accumulated
number of tandem connection remote bit errors received at the sink within one second is greater
than 0, the TC_REI alarm is reported.
Attribute
Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the AU-4 path number.
For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter

3 = 0x01. In this case, the TC_REI alarm is reported from path 1
of optical port 1 on the board.

When the TC_REI alarm occurs, the services at the local station are not affected. This alarm just
shows that bit errors occur in the monitored tandem connection section. Consequently, the
transmission service quality is degraded.

OptiX OSN 8800/6800/3800
Possible Causes
The possible cause of the TC_REI alarm is as follows:
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 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.
NOTICE
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.
NOTICE
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 the solution.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.12 APE_ADJUST_FAIL
Description
Automatic power equilibrium (APE) adjustment failure. This alarm is generated when the APE
adjustment fails.
Attribute
Major Process alarm
Parameters
Name Meaning
Parameter 1 Indicates the index to APE.

The OSNR of receive signals degrades.
Possible Causes
l The communication fails.
l The board is offline.
l The equilibrium cannot be reached after adjustment.
l The board type error.
l The number of adjustment times exceeds the upper limit.
l The adjustment is stopped by the user.
Procedure
Step 1 Isolate the alarm cause and handle the alarm accordingly.
----End

OptiX OSN 8800/6800/3800
Related Information
For details, see "Automatic Power Equilibrium (APE)" in the Feature Description.
4.13 APE_ADJUST_PEND
Description
This alarm is generated when APE adjustment is pending.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the index of APE.

The OSNR of receive signals degrades.
Possible Causes
The APE detects that the optical power of some channels is unequal and is going to start an
adjustment.
Procedure
Step 1 Manually start an APE adjustment.
Step 2 If the APE_ADJUST_PEND alarm persists and simultaneously the APE_ADJUST_FAIL alarm
is reported, clear the alarms by referring to the procedure for clearing the APE_ADJUST_FAIL
alarm.
----End
Related Information

OptiX OSN 8800/6800/3800
4.14 APS_FAIL
Description
The APS_FAIL is an alarm indicating a multiplex section protection (MSP) switching failure.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group where the switching occurs.
l 0x01: linear MSP group

l 0x02: ring MSP group
Parameter 2, Parameter 3 Indicates the ID of the MSP group.

When this alarm occurs, services cannot be switched. In addition, if the existing path cannot be
used, services are interrupted.
Possible Causes
l MSP parameters are incorrectly configured.
l The MSP configuration is lost.
Procedure
Step 1 Verify that network-wide MSP configuration is correct. For ring MSP, check the optical-fiber
connection. For linear MSP, check working and protection optical-fiber connections or MSP
switching mode. After MSP configuration is corrected, check whether the APS_FAIL alarm is
cleared.

OptiX OSN 8800/6800/3800
Step 2 If the alarm persists, verify that network-wide MSP-related protocols are properly running. If
the protocols are improperly running, restart them. Then, check whether the APS_FAIL alarm
is cleared.
Step 3 If the alarm persists, replace the board that reports this alarm.
----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
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group where the switching occurs.

Parameter 2, Parameter 3 Indicates the ID of the MSP group.

l The APS_INDI alarm indicates the occurrence of a fiber cut or a terminal node failure,
which triggers the MSP switching.

OptiX OSN 8800/6800/3800
l 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
l Cause 1: An external command is issued to initiate a switching (such as manual switching,
forced switching, exercise switching, and lockout of switching).
l Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD
alarm) that triggers an automatic MSP switching.
l Cause 4: The SCC board is faulty.
Procedure
Step 1 View this alarm on the NMS and determine the MSP group type and ID based on alarm
parameters.
Step 2 Cause 1: An external command is issued to initiate a switching (such as manual switching, forced
switching, exercise switching, and lockout of switching).
1. Query the MSP switching state.
If... Then...
The MSP group is in the state of manual Clear the switching state and verify that the
switching, forced switching, exercise alarm is cleared. If the alarm persists, go to
switching, or locked switching Step 3.
The MSP group is in none of the Go to Step 3.

preceding switching states
Step 3 Cause 2: There is an alarm (such as the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm)
that triggers an automatic MSP switching.
1. Check whether the MSP group is in the automatic switching state.
If... Then...
The local NE reports the R_LOS, The MSP group enters the automatic
R_LOF, MS_AIS, or B2_EXC alarm switching state and reports the APS_INDI
alarm. In this case, clear the R_LOS, R_LOF,
MS_AIS, or B2_EXC alarm and check
whether the APS_INDI alarm is cleared.
If the APS_INDI alarm persists, go to the

next step.

OptiX OSN 8800/6800/3800
If... Then...
The local NE reports the B2_SD alarm After you enable the SD switching condition,
the SD-related alarm can trigger the MSP
NOTE
switching. You can use either of the
Both SF and SD switching conditions can following methods to clear the APS_INDI
trigger automatic MSP switching. The
B2_SD alarm cannot trigger MSP switching
alarm:
by default but can be specified as the SD
l Disable SD switching.
switching condition to trigger MSP
switching. l Clear the B2_SD alarm first.
Check whether the APS_INDI alarm is

cleared. If the alarm persists, go to the next
step.
The MSP group is in none of the Go to the next step.

preceding switching states
2. Query the revertive mode of the MSP group.
If... Then...
Revertive Mode is set to Revertive After the working path recovers, the services
are switched automatically from the
protection path to the working path only when
the preset wait to restore (WTR) time expires.
The APS_INDI alarm is cleared after the
switching is successful.
When the MS is automatically restored from

the switching state to the normal state, check
whether the APS_INDI alarm is cleared. If the
alarm persists, go to Step 4.
Revertive Mode is set to Non-Revertive After the working path recovers, the services
are not switched automatically from the
protection path to the working path and the
APS_INDI alarm persists.
To clear the alarm, manually switch the

services from the protection path to the
working path.
3. In the NE Explorer, select the NE, and choose Configuration > Linear MS or
Configuration > Ring MS from the navigation tree. In the Slot Mapping Settings area,
right-click the working unit or the protection unit of a protection group and choose the
desired switching mode from the shortcut menu.
4. After the manual switching is successful, check whether the APS_INDI alarm is cleared.
If the alarm persists, go to Step 4.

1. Check whether the service board where the multiplex section is configured is faulty.

OptiX OSN 8800/6800/3800
If... Then...
A service board reports alarms indicating Replace the service board.

hardware faults, such as the HARD_BAD
Check whether the alarm is cleared. If the
alarm
A service board reports no alarm indicating Go to Step 5.

hardware faults
Step 5 Cause 4: The SCC board is faulty.

1. Check whether the SCC board that reports alarms is faulty.
If... Then...
An SCC board reports alarms indicating Warm reset the SCC board.
hardware or software faults, such as the
HARD_BAD and HARD_BAD alarms
An SCC board reports no alarm indicating Contact Huawei technical support

hardware or software faults engineers to handle the alarm.
2. Replace the faulty SCC board. Check whether the alarm is cleared. If the alarm persists,
contact Huawei technical support engineers to handle the alarm.
----End
Related Information
Revertive Mode
The Revertive Mode field can be set to Revertive or Non-Revertive. Generally, it is

recommended that you set Revertive Mode to Revertive.
l If you set Revertive Mode to Revertive, the services are switched automatically from the
protection path to the working path after the working path recovers.
l If you set Revertive Mode to Non-Revertive, the services are not switched automatically
from the protection path to the working path after the working path recovers, and the
services are still transmitted over the protection path.
4.16 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped manually.

OptiX OSN 8800/6800/3800
Attribute
Minor Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the type of the MSP group.

Parameter 2 Indicates the ID of the MSP group.

When this alarm occurs, the MSP switching protocol does not work, which causes the MSP
failure.
Possible Causes
The MSP protocol is manually stopped.
Procedure
Step 1 Locate the MSP subnet where the MSP protocol is stopped on the NMS.
Step 2 Start the MSP protocol.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.17 ASE_NOT_CALIBRATE
Description
This alarm is generated when the amplified spontaneous emission (ASE) on the Raman optical
module is not demarcated.
Attribute

Parameters
None

This alarm affects the ALC adjustment and therefore may interrupt services.
Possible Causes
After the demarcation for the RAU board is complete, the ASE of the Raman optical module on
the RAU board is not demarcated if the RAU board is replaced or the type of the logical fibers
used by the RAU board is changed.
Procedure
Step 1 on the U2000, demarcate the RAU board. If the mark is successful, the alarm cleared
automatically.
----End
Related Information
None
4.18 AU_AIS
Description
The AU_AIS is an alarm indication of the administrative unit (AU). This alarm is generated
when the optical port on the local NE receives the AU pointer of all 1s.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

l Without the network protection, the services in the VC-4 path that reports the alarm are
interrupted.
l The AU_AIS alarm is reported on the downstream NEs.
Possible Causes
l Cause 1: The local NE has the higher level alarms.
l Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
l Cause 3: The transmit boards on the upstream NE are faulty.
l Cause 4: The receive boards on the local NE are faulty.
Procedure
Step 1 Cause 1: The local NE has the higher level alarms.
1. On the NMS, check the local NE for higher level alarms.
If... Then...
The higher level alarms, such as the Clear these alarms and then check whether
R_LOS, R_LOF, B1_EXC, and B2_EXC the AU_AIS alarm is cleared. If the alarm
alarms, are reported persists, go to Step 2.
No higher level alarm is reported Go to Step 2.
Step 2 Cause 2: The upstream NE inserts the AIS alarm to the downstream NE.
1. Check upstream NEs for severer alarms.
If... Then...
Any of the alarms listed in Table 4-1 Clear the alarm and check whether the
occurs AU_AIS alarm is cleared. If the alarm
persists, go to the next step.
None of the alarms listed in Table 4-1 Go to the next step.

occurs
2. Perform loopback to locate the upstream NE that initially generates the AU_AIS alarm.

OptiX OSN 8800/6800/3800
NOTICE
A loopback will interrupt services.
3. Check whether the AU_AIS alarm occurs on the peer NE after the loopback is performed.
If... Then...
The AU_AIS alarm occurs on the peer The peer NE has transmitted the AU_AIS
NE alarm to the local NE. In this case, go to the
next step.
No AU_AIS alarm occurs on the peer Go to Step 4.

NE
4. Perform loopback to locate the upstream NE that generates the AU_AIS alarm. Check the
service source board of the NE for severer alarms.
If... Then...
Any of the alarms listed in Table 4-1 Clear the alarm and check whether the
occurs AU_AIS alarm is cleared. If the alarm
None of the alarms listed in Table 4-1 Go to Step 3.

occurs
Step 3 Cause 3: The transmit boards on the upstream NE are faulty.

1. Replace the transmit board that initially reports the AU_AIS alarm on the peer NE.
2. Check whether the AU_AIS alarm is cleared.
3. Check whether the AU_AIS alarm is cleared. If the alarm persists, contact Huawei technical
Step 4 Cause 4: The receive boards on the local NE are faulty.

1. Replace the receive board that reports the alarm on the local NE.
2. Check whether the AU_AIS alarm is cleared. If the alarm persists, contact Huawei technical
----End
Related Information
Table 4-1 Alarms that may cause the AU_AIS alarm
R_LOS R_LOF MS_AIS
B1_EXC B1_SD (OCS) B2_EXC
B2_SD AU_LOP B3_EXC

OptiX OSN 8800/6800/3800
B3_SD HP_TIM HP_SLM
HP_UNEQ
4.19 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm is generated when
the optical port of the local NE receives eight consecutive frames that contain NDFs or invalid
AU pointers.
Attribute
Parameters
None.

l When this alarm occurs, the services on the VC-4 path are interrupted without network
protection.
l When this alarm occurs, the system automatically returns the HP_RDI alarm to the peer
NE by using the G1 byte, and the peer NE reports the HP_RDI alarm.
l When this alarm occurs, the AU_AIS alarm occurs on the downstream NEs.
Possible Causes
l Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
l Cause 2: The services transmitted by the peer NE and received by local NE are inconsistent
in the service level.
l Cause 3: Boards on the local NE are faulty.
l Cause 4: Boards on the peer NE are faulty.
Procedure
Step 1 Cause 1: The number of bit errors received by the local NE exceeds the upper threshold.
1. Check whether local NE reports the following bit error alarms:
l B1_EXC
l B1_SD
l B2_EXC

OptiX OSN 8800/6800/3800
l B2_SD
2. If the local NE reports any of the preceding alarms, clear it and check whether the AU_LOP
alarm is cleared. If the local NE reports no bit error alarm, or the AU_LOP alarm persists
after bit error alarms are cleared, go to Step 2.
Step 2 Cause 2: The services transmitted by the peer NE and received by local NE are inconsistent in
the service level.
1. Check whether the services transmitted by the peer NE and received by local NE are
consistent in the service level.
If... Then...
Services transmitted by the peer NE and Reconfigure the service level on the local
received by local NE are inconsistent in and peer NEs and check whether the
the service level AU_LOP alarm is cleared. If the alarm
Services transmitted by the peer NE and Go to Step 3.

received by local NE are consistent in the
service level
Step 3 Cause 3: Boards on the local NE are faulty.

1. Cold reset the local receive board on the NMS or directly remove and insert this board.
NOTICE
If services traverse the board are not protected, cold resetting the board will interrupt
services.
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the local receive
board.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: Boards on the peer NE are faulty.

1. Cold reset the peer transmit board on the NMS or directly remove and insert this board.
NOTICE
If services traverse the board are not protected, a board cold reset will interrupt services.
2. Check whether the AU_LOP alarm is cleared. If the alarm persists, replace the peer transmit
board.
3. Check whether the AU_LOP alarm is cleared. If the alarm persists, contact Huawei
technical support engineers to handle the alarm.
----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.20 B1_SD
SF64, SF64A, SFD64, SL64, SLD64, 4.20.1 B1_SD (OCS)

Boards other than the SF64, SF64A, SFD64, 4.20.2 B1_SD (OTN)
SLO16, or EGSH
4.20.1 B1_SD (OCS)
Description
The B1_SD is an alarm indicating regenerator section signal deterioration. This alarm is reported
when the local board receives deteriorated SDH frames and the bit error rate of the regenerator
section exceeds the signal deterioration threshold (10-6).
Attribute
Minor Service alarm
Parameters
Name Meaning

OptiX OSN 8800/6800/3800

When this alarm occurs, the quality of transmitted services has deteriorated.
Possible Causes
l The bit error threshold is not proper.
l The ambient environment is abnormal.
l The fiber connector is loose or not properly connected.
l The fiber connector is contaminated.
l Received signals have attenuated during transmission.
l The peer transmit unit is faulty.
l The local receive unit is faulty.
Procedure
Step 1 Check the bit error threshold. If it is low, raise the threshold as required and check whether the
alarm is cleared.
Step 2 Check whether the alarm-reporting board runs in an equipment room with a temperature higher
than 45C or lower than 0C for a long period of time. If the temperature is higher than 45C or
lower than 0C, adjust it into the normal range and check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the alarm-reporting board has a proper receive optical power.
If... Then...
The receive optical power is proper Go to Step 4.
The receive optical power is not proper Perform the following steps:
1. Check whether the fiber connector at the local receive port is loose. If the fiber connector
is loose, properly connect it and check whether the alarm is cleared.
2. Check whether pigtail at the local receive port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the receive optical port and check whether
the alarm is cleared.
Step 4 If the alarm persists, check whether the transmit optical power of the peer board is proper.
If... Then...
The transmit optical power is proper Perform the following steps:
The transmit optical power is not proper Go to Step 7.
1. Check whether the fiber connector at the peer transmit port is loose. If the fiber connector

OptiX OSN 8800/6800/3800
2. Check whether pigtail at the peer transmit port is contaminated. If the pigtail is
contaminated, clean the pigtail connector and the transmit optical port and check whether
Step 5 If the alarm persists, check whether the transmission line is faulty. If the transmission line is
faulty, replace it and check whether the alarm is cleared.
Step 6 If the alarm persists, check whether the local receive board malfunctions. If the board has a
pluggable optical module and malfunctions, replace the optical module. If the board has no
pluggable optical module and malfunctions, replace the board.
Step 7 If the alarm persists, check whether the peer transmit board malfunctions. If the board has a
Step 8 If the alarm persists, contact Huawei technical support engineers to handle the alarm.
----End
Related Information
None.
4.20.2 B1_SD (OTN)
Description
Regenerator section (B1) signal degraded. This alarm is generated when the received signals in
SDH frame degrade and the B1 bit errors on the regenerator section exceed the signal degrade
(SD) threshold.
Attribute
Minor Service alarm
Parameters
None

The B1 bit errors in the service signals received by the board exceed the signal degrade threshold
set on the board. The generation of the alarm affects the QoS of the service signals.
Possible Causes
l The attenuation of the received signals is overlarge; the fiber or connector is dirty.
l The transmit part of the opposite station is faulty.
l The receive part of the local station is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 On the U2000, check whether the receive optical power of the port is within the permitted range.
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 port on the
upstream board is within the permitted range on the U2000. If the transmit optical power of the
board at the upstream station is excessively low, clear the alarm according to the handling
procedure of the OUT_PWR_LOW alarm.
Step 3 If the alarm persists, check on the U2000 whether the bit error alarm exists at the upstream station
by using the 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 pluggable optical modules, Replace the specific
pluggable optical module.
Step 5 If the alarm persists, Replace the board.
Step 6 If the alarm bursts, it may be caused by the transmission line influenced by various noise sources.
Search for the jam source that may cause the burst bit errors and remove the interference.
----End
Related Information
None
4.21 BD_LEDTEST
Description
Board LED blinking test alarm. This alarm is generated when an LED blinking test is performed
on a board.
Attribute
Warning Equipment alarm
Parameters
None

None

OptiX OSN 8800/6800/3800
Possible Causes
l A board receives a command for performing an LED blinking test.
Procedure
Step 1 Check whether an LED blinking test is being performed on the board. If an LED blinking test
is being performed, wait until the test is complete. The alarm will be terminated after the test is
complete.
----End
Related Information
None
4.22 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
Major Service alarm
Parameters
Name Meaning

l When the B2_EXC alarm is generated, the quality of the transmitted services is degraded.

OptiX OSN 8800/6800/3800
l 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
The possible causes of the B2_EXC alarm are as follows:

Procedure
alarm is cleared.
If... Then...
If... Then...

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.23 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
Minor Service alarm
Parameters

OptiX OSN 8800/6800/3800
Name Meaning

l When the B2_SD alarm is reported, the quality of the transmitted services is degraded.
l 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
The possible causes of the B2_SD alarm are as follows:

Procedure
alarm is cleared.
If... Then...

OptiX OSN 8800/6800/3800
If... Then...
----End
Related Information
None.
4.24 B3_EXC
Description
The B3_EXC is an alarm indicating that the number of the higher order path (HP) B3 bit errors
exceeds the specified threshold. This alarm is generated when a board detects that the number
of the HP bit errors exceeds the specified threshold (default threshold: 10-3) by monitoring the
B3 byte.
Attribute
Major Service alarm

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the ID of the AU-4 path.

When this alarm occurs, path level services have bit errors.
Possible Causes
The possible causes of the B3_EXC alarm are as follows:

Procedure
alarm is cleared.
If... Then...

OptiX OSN 8800/6800/3800
If... Then...
----End
Related Information
None.
4.25 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that the number of lower order path (LP) VC-3 B3
bit errors exceeds the specified threshold. This alarm is generated when a board detects that the
number of the VC-3 bit errors exceeds the B3_EXC alarm threshold by monitoring the B3 byte.
Attribute
Major Service alarm

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 2, Parameter 3 Indicates the ID of the VC-3 path.

When the B3_EXC_VC3 alarm occurs, the VC-3 service has plenty of bit errors.
Possible Causes
l Severer bit error alarms have occurred in the system.
Procedure
Step 1 Check the local and upstream NEs for the B1_EXC, B1_SD, B2_EXC, B2_SD, B3_EXC, or
B3_SD alarm. If any of these alarms exists, clear it and check whether the B3_EXC_VC3 alarm
is cleared.
alarm is cleared.
If... Then...
The receive optical power is proper Go to 4.

OptiX OSN 8800/6800/3800
If... Then...
The transmit optical power is not proper Go to 7.
----End
Related Information
None.
4.26 B3_EXC_VC4
Description
The B3_EXC_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors exceeds the
specified threshold. This alarm is generated when a board detects that the number of the VC-4
bit errors exceeds the specified threshold by monitoring the B3 byte.

OptiX OSN 8800/6800/3800
Attribute
Major Service alarm
Parameters
Name Meaning

Possible Causes
Procedure
is cleared.
alarm is cleared.

OptiX OSN 8800/6800/3800
If... Then...
If... Then...
----End
4.27 B3_SD
Description
The B3_SD is an alarm indicating higher order path (HP) B3 signal deterioration. This alarm is
generated when a board detects that the number of HP signal bit errors exceeds the B3_SD alarm
threshold (default threshold: 10-6) but remains below the B3_EXC alarm threshold (default
threshold: 10-3) by monitoring the B3 byte.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
Name Meaning

Possible Causes
The possible causes of the B3_SD alarm are as follows:

Procedure
alarm is cleared.

OptiX OSN 8800/6800/3800
If... Then...
If... Then...
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.28 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the number of the VC-3 B3 bit errors exceeds the
specified threshold. This alarm is generated when a board detects that the number of the VC-3
bit errors exceeds the B3_SD alarm threshold by monitoring the B3 byte.
Attribute
Minor Service alarm
Parameters
Name Meaning

When this alarm occurs, the service transmission quality of the VC-3 path has deteriorated.
Possible Causes

OptiX OSN 8800/6800/3800
Procedure
is cleared.
alarm is cleared.
If... Then...
If... Then...

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.29 B3_SD_VC4
Description
The B3_SD_VC4 is an alarm indicating that the number of the VC-4 B3 bit errors has exceeded
the specified threshold. This alarm is generated when a board detects that the number of the
VC-4 bit errors exceeds the specified threshold by monitoring the B3 byte.
Attribute
Minor Service alarm
Parameters
Name Meaning

Possible Causes

OptiX OSN 8800/6800/3800

Procedure
is cleared.
alarm is cleared.
If... Then...
If... Then...

OptiX OSN 8800/6800/3800
----End
4.30 BD_NOT_INSTALLED
Description
Logical board not added in the corresponding slot. This alarm is generated when a physical board
is installed but no logical board is created on the U2000.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the board where the alarm is generated.

When the BD_NOT_INSTALLED alarm occurs, no services can be configured in the
corresponding slot. This alarm, however, does not affect the operation of the system.
Possible Causes
The logical board is not created.
Procedure
Step 1 On the U2000, add a logical board that corresponds to the board that reports the alarm.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.31 BD_STATUS
SF64, SF64A, SFD64, SL64, SLD64, 4.31.1 BD_STATUS (OCS)

Boards other than the SF64, SF64A, SFD64, 4.31.2 BD_STATUS (OTN)
SLO16, or EGSH
4.31.1 BD_STATUS (OCS)
Description
The BD_STATUS is an alarm indicating an offline physical board. This alarm is reported when
a user has configured a board on the NMS but has not installed the board.
Attribute
Parameters
None.

When this alarm occurs, NE configuration data cannot be applied to the board. As a result, service
configuration fails.
Possible Causes
l Cause 1: The board is being reset.
l Cause 2: The board is not installed or has poor contact with the backplane.
l Cause 3: The board is faulty or the backplane has bent pins.
Procedure
Step 1 Cause 1: The board is being reset.

OptiX OSN 8800/6800/3800
1. View the board indicator to determine whether the board is being reset. For details, see the
Hardware Description. Alternatively, query historical resets of the board. For details, see
in Supporting Tasks.
If... Then...
The board is being reset Wait until the reset is complete (about 5 minutes) and
check whether the BD_STATUS alarm is cleared.
The board is not being reset Go to Step 2.
2. Check whether the BD_STATUS alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The board is not installed or has poor contact with the backplane.
1. On the NMS, double-click the alarm-reporting NE in the Main Topology. Then, record the
logical-board type for the alarm-reporting slot on the NE Panel.
2. Check whether the physical board is installed.
If... Then...
The physical board is not installed Properly install the physical board that matches the
logical board.
Check whether the BD_STATUS alarm is cleared.

The physical board is installed Go to the next step.
3. Check the contact between the board and backplane.
If... Then...
If the contact is poor Remove and properly re-insert the board. Then, check whether
the BD_STATUS alarm is cleared. If the alarm persists, go to
Step 3.
If the contact is fine Go to Step 3.
Step 3 Cause 3: The board is faulty or the backplane has bent pins.
1. Replace the alarm-reporting board. For details, see Parts Replacement. Then, check
whether the BD_STATUS alarm is cleared.
2. If the alarm persists, check whether the backplane has bent pins.
If... Then...
The backplane has bent pins Contact Huawei technical support engineers to repair
the bent pins. Then, properly re-insert the board.

OptiX OSN 8800/6800/3800
If... Then...
The backplane has no bent pin Contact Huawei technical support engineers to handle
the alarm.
----End
Related Information
None.
4.31.2 BD_STATUS (OTN)
Description
Physical board being offline. This alarm is generated when the logical board is created on the
U2000 but the physical board is not inserted in the slot.
Attribute
Parameters
None

The board is offline. Therefore, the functions related to the board are unavailable.
Possible Causes
l The AUX board is faulty.
l The logical board is configured but the physical board has not been inserted in the
corresponding slot.
l The connection between the plug of the board and the socket of the backplane is loose.
l The backplane is faulty.
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 physical board is inserted in the physical slot.

OptiX OSN 8800/6800/3800
l If no corresponding board is inserted, insert the board.

l 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 "Replace the board.".
Step 4 If the alarm persists, replace the backplane. For the detailed operations, contact Huawei for
assistance.
----End
Related Information
Related Cases:
l MC-A32 When OptiX BWS 1600G SCC Board Is Replaced with the SCE, TC2 Board
Reports BD_STATUS Alarm
l MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
l MC-A195 Incorrect DIP Settings Cause the BD_STATUS Alarm on the CRPC Board
l MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report
Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
l MC-A231 The Board Cannot Identify the Subrack, So A New OTU Board on an OptiX
OSN 8800 NE Fails to Go Online
4.32 BIOS_STATUS
Description
The BIOS_STATUS is an alarm indicating the BIOS status. By default, if loading of the board
software fails for three consecutive times within five minutes, the board enters the BIOS status
and the BIOS_STATUS alarm is reported.
Attribute
Major Environment alarm
Parameters
None

When an anomaly occurs on the board software or hardware, the BIOS_STATUS alarm is
generated and related services are interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
The possible causes of the BIOS_STATUS alarm are as follows:
l The software is lost.

l Incorrect software is loaded.
l Writing or reading the software becomes abnormal.
l The board hardware is faulty.
Procedure
Step 1 View the BIOS_STATUS alarm on the U2000, and then determine the board where the
BIOS_STATUS alarm is generated.
Step 2 Perform warm reset on the board and then check whether the BIOS_STATUS alarm is cleared.
Step 3 If the BIOS_STATUS alarm persists, perform cold reset on the board. Then check whether the
BIOS_STATUS alarm is cleared.
Step 4 If the BIOS_STATUS alarm persists, contact Huawei technical support engineers and ask them
to replace the board software. After the board software is replaced, check whether the
BIOS_STATUS alarm is cleared.
Step 5 If the alarm persists, replace the board and check whether the BIOS_STATUS alarm is cleared.
----End
Related Information
None
4.33 BWUTILIZATION_OVER
Description
The BWUTILIZATION_OVER is an alarm indicating that bandwidth usage exceeds the
threshold. If traffic received or transmitted by monitored objects such as traffic classification
exceeds the traffic threshold and the bandwidth usage exceeds the acceptable value, the
BWUTILIZATION_OVER alarm is reported.
Attribute
Warning Service alarm
Parameters

OptiX OSN 8800/6800/3800

Name Meaning
Parameter 1 Indicates the direction where the bandwidth utilization rate exceeds the threshold.
l 0x00: indicates that the traffic in the receive direction exceeds the traffic
threshold.
l 0x01: indicates that the traffic in the transmit direction exceeds the traffic
threshold.

When this alarm occurs, the network is congested.
Possible Causes
The possible causes of the BWUTILIZATION_OVER alarm are as follows:
l Cause 1: The traffic received or transmitted by a monitored object exceeds the traffic
threshold.
l Cause 2: The configured bandwidth usage threshold for a monitored object is low.
Procedure
Step 1 Cause 1: The traffic received or transmitted by a monitored object exceeds the traffic threshold.
1. On the NMS, view alarm information and determine the object (traffic classification) that
generates the alarm.
2. Check whether the network traffic exceeds the traffic threshold. If the configured traffic
threshold is low, check whether the threshold can be raised. You can raise the threshold to
make it greater than the actual traffic to clear the alarm. If the threshold cannot be raised,
go to the next step.
3. Check whether network storm or invalid data source exists on the network. Eliminate the
source that transmits a large amount of data and check whether the alarm is cleared.
4. If the alarm persists, enable CAR or configure QoS to reduce the data traffic transmitted
from the peer end.
Step 2 Cause 2: The configured bandwidth usage threshold for a monitored object is low.
1. On the NMS, view alarm information and determine the object (traffic classification) that
generates the alarm.
2. Check whether the bandwidth usage threshold for the object is low. If the configured
threshold is low, expand network capacity to clear the alarm.
----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.34 CFCARD_FAILED
Description
CF card failed.
Attribute
Parameters
None

The CFCARD_FAILED alarm has no impact on the system. The alarm only indicates that the
operations related to the CF card fail.
Possible Causes
The CF card is faulty and needs to be replaced.
Procedure
Step 1 Replace the CF card and check whether the CFCARD_FAILED alarm is cleared. If the alarm
persists, replace the system control board.
----End
Related Information
None
4.35 BDID_ERROR
Description
The BDID_ERROR is an alarm indicating an error in board position check. This alarm is
generated when a board parity check fails or the board is not properly installed.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

l When this alarm occurs, a board may fail to go online, which will interrupt services.
l When this alarm occurs, you cannot configure or monitor board services.
Possible Causes
l The board is not properly installed.
l The board has hardware faults.
l The backplane has bent pins.
Procedure
Step 1 View this alarm on the NMS and determine the board that reports the alarm.
Step 2 Remove the board to check the backplane for bent pins. If the backplane has bent pins, repair
them and insert the board. Then, check whether the BDID_ERROR alarm is cleared.
----End
Related Information
None.
4.36 C2_VCAIS
Description
The C2_VCAIS is an alarm pertaining to C2 bytes. This alarm is generated when a board detects
that all the received C2 bytes are 1.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
Name Meaning

Possible Causes
The remote end has transmitted C2 bytes that are incorrectly configured.
Procedure
Step 1 View the alarm information on the NMS and determine the VC path that has reported this alarm.
Step 2 Check whether the remote end has correctly configured the to-be-transmitted C2 bytes. If the
remote end has incorrectly configured the C2 bytes, reconfigure them and check whether the
C2_VCAIS alarm is cleared.
Step 3 If the alarm persists, replace the transmit board of the remote end.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.37 CHAN_ADD
Description
Wavelengths being added to a single- wavelength signal. This alarm is generated when the multi-
channel spectrum analyzer (MCA) board detects that new wavelengths are added after it scans
the optical spectrum.
Attribute
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 received wavelengths are
not set as the monitored wavelengths.
l The MCA board is faulty.
Procedure
Step 1 On the U2000, check whether the configuration for wavelength monitoring of the MCA board
is incorrect. 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 using the optical
spectrum analyzer. If the data is normal, the optical spectrum analyzing module of the MCA
board may be faulty. Replace the faulty board.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.38 CHIP_ABN
Description
The CHIP_ABN is an alarm indicating an invalid temperature chip. This alarm is generated
when a temperature chip becomes invalid.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the invalid temperature chip. The value 0x01 indicates
that the temperature chip becomes invalid.

When this alarm occurs, the board temperature cannot be correctly detected.
Possible Causes
The temperature chip becomes invalid.
Procedure
Step 1 Check whether there is another cross-connect board that is working properly. If there is such a
board, cold reset the board that has reported the CHIP_ABN alarm. After the cold reset is
successful, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the alarm-reporting board.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.39 CLIENT_PROT_NOTSTART
Description
Client 1+1 protection group not started. This alarm is generated when a client 1+1 protection
group is not started because the configurations on the both sides of the working and protection
channels of the protection group do not meet the requirements of enabling the protection group.
Attribute
Parameters
None

The client 1+1 protection group does not perform switching in case of a service fault and
therefore the protection fails.
Possible Causes
l An incorrect electrical-layer cross-connections is configured on the working or protection
channel.
l Complete electrical-layer services between WDM-side ports and client-side ports are not
configured on the working or protection channel.
l An EVPL link that converges at a client-side optical port is configured for the working or
protection channel.
Procedure
Step 1 On the U2000, query an incorrect electrical-layer cross-connection is configured on the working
or protection channel, such as a cross-connection with an IP port as the source and another IP
port as the sink. If it is, delete the incorrect electrical-layer cross-connection.
Step 2 If the alarm persists, check the OTU board on which electrical-layer cross-connections can be
configured. If incomplete electrical-layer cross-connections are configured between WDM-side
ports and client-side ports, configure the complete electrical-layer cross-connections.
Step 3 If the alarm persists, check whether an EVPL link that converges in the downlink is configured
for the working or protection channel. If it is, change this EVPL link to an EPL link or an EVPL
link that broadcasts in the downstream.
----End

OptiX OSN 8800/6800/3800
Related Information
4.40 CLIENT_PORT_STA_INDI
Description
Status indication of a client 1+1 protection group. This alarm is generated when the working or
protection channel of a protection group is faulty or a user delivers an external switching
command.
Attribute
Parameters
Parameter 1 Indicates the switching request status. For example:

l 0x0F: Lockout switching
l 0x0E: Forced switching
l 0x0C: SF switching
l 0x09: SD switching
l 0x07: Manual switching
l 0x05: WTR

l When a client 1+1 protection group undergoes switching, services are transiently
interrupted.
l When this alarm is reported, the working channel or the protection channel of a client 1+1
protection group might have services that need to be restored.
Possible Causes
l Cause 1: A user delivers an external switching command such as forced switching, manual
switching, or locked switching.

OptiX OSN 8800/6800/3800
l Cause 2: The services on the working channel or the protection channel of a client 1+1
protection group are faulty.
l Cause 3: The switching is in WTR state. After WTR Times (s) elapses, the alarm clears.
Procedure
state is forced switching, manual switching, or locked switching, check whether the
external switching operation is necessary.
3. If the external switching operation is unnecessary, deliver a command to clear the
external switching.
l Cause 2: The services on the working channel or protection channel of the client 1+1
protection group are faulty.
1. Query whether the related boards on 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
they do, handle the alarms by referring to the corresponding alarm handling
procedures.
Revertive. If the attribute is Revertive, after WTR Times the active channel of the
service automatically switches to the working channel and then the alarm clears. If
the attribute is Non-Revertive, set it to Revertive, and after WTR Times the alarm
clears.
l Cause 3: The switching is in WTR state. After WTR Times elapses, the alarm clears.
1. There is no need to handle this alarm. After WTR Times elapses, the alarm clears.
----End
Related Information
4.41 CLK_LOCK_FAIL
Description
Clock lockout failure alarm. When the frequency of an NE is synchronized from the upstream,
the frequency lock status is locking. When the frequency of an NE is not locked, this alarm is
reported to remind the user of the unlock status of the NE clock.

OptiX OSN 8800/6800/3800
Attribute
Parameters
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 switched clock source
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 switched 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.
Parameter 5 0x02 indicates that the difference between phase discrimination values is larger
than 300 within 40s.

When this alarm is generated, the NE clock is unlocked. As a result, the time of the slave NE
cannot trace the time of the master NE, and services are prone to bit errors. Hence, handle this
alarm in time once it is reported.
Possible Causes
The possible causes of the CLK_LOCK_FAIL alarm are as follows:
l Case 1: In the case of physical synchronization, the clock source has excessive frequency
deviation.
l Case 2: The physical link with the clock source is faulty.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: In the case of physical synchronization, the clock source has excessive frequency
deviation.
1. Check for BER-related alarms or performance events at a higher level on the NMS.
If there are such alarms or performance events, handle them and then check whether
the CLK_LOCK_FAIL alarm is cleared.
2. If an external clock source is traced, check whether the clock signals are normal. If
not, update the traced clock source.
3. Check whether clock configuration is correct. For example, check whether the input
mode matches the output mode. Correct clock configuration and then check whether
the CLK_LOCK_FAIL alarm is cleared.
4. If the alarm persists, the clock board may be faulty. In this case, replace the faulty
clock board.
l Cause 2: The physical link with the clock source is faulty.
1. On the NMS determine the number of the port where the alarm is reported.
2. Check whether a network cable or fiber is disconnected from this port. If yes, reconnect
the network cable or fiber, and then check whether the alarm is cleared.
3. If the alarm persists, check whether the network cable or fiber is faulty. If yes, replace
the network cable or fiber and then check whether the alarm is cleared.
4. If the alarm persists, query the transmit optical power of the opposite NE on the NMS.
If the transmit optical power is normal, replace the optical power at the opposite NE.
5. If the alarm persists, check whether the local receive board is faulty. If yes, replace
the board that reports the alarm on the local NE.
----End
Related Information
None
4.42 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

OptiX OSN 8800/6800/3800
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 out-
of-synchronization status among NEs, the clock synchronization performance of the system is
degraded. (For the OCS system, the bit error rate of services increases.)
Possible Causes
The possible causes of the CLK_NO_TRACE_MODE alarm are as follows:
l Cause 1: If SDH boards are configured on NEs, a priority table is not manually set for the
system, and NEs use their own default priority tables.
l Cause 2: A priority table is set, but only the internal clock source in the priority table can
be traced.
Procedure
l Cause 1: If SDH boards are configured on NEs, a priority table is not manually set for the
system, and NEs use their own default priority tables.
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.
l 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.

OptiX OSN 8800/6800/3800
4.43 COM_EXTECC_FULL
Description
Number of TCP connections between NEs running the automatically extended ECC protocol
exceeding the system limit.
Attribute
Parameters
None

The DCN network will be unstable.
Possible Causes
The number of TCP connections between NEs running the automatically extended ECC protocol
exceeds the system limit.
Procedure
Step 1 Disable the automatically extended ECC protocol and enable the manually extended ECC
----End
Related Information
None
4.44 CRC4_CROSSTR
Description
CRC4 multi-frame bit error count exceeding the threshold. The alarm is generated when the
number of the bit errors in the CRC4 multiframe exceeds the threshold.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
None

The alarm has an impact on the services (supervisory channel such as the orderwire signal).
Possible Causes
l The configuration of the system clock is incorrect.
l The attenuation of the transmission line is overlarge.
l The receive optical power is overloaded.
Procedure
Step 1 On the U2000, check the clock configuration of the system to ensure that the configuration is
correct.
Step 2 Check whether the input optical power of the board at the local station is within the permitted
range on the U2000. 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 affected, 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.45 DB_RESTORE_FAIL
Description
Database restoration failure. This alarm is generated when the database fails to be restored.

OptiX OSN 8800/6800/3800
Attribute
Major Process Alarm
Parameters
Parameters 1 and 2 Indicate that the slot ID of the board whose OCP database fails to be
restored.
Parameter 3 Indicate the alarm cause:
0x01: The database fails to be restored.
0x02: Operating the memory database fails.
0x03: Memory data and memory database data are different.
0x04: The memory database cannot construct memory data.

The configuration data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l The database configuration file is lost.
l Data in the database is damaged.
Procedure
Step 1 Back up the database regularly to resolve this problem. Check and test the database in the backup
area to ensure that the data in database is complete.
Step 2 If the alarm persists, replace the faulty board.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.46 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.
Attribute
Parameters
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.
l If the DBPS protection status of the active equipment and standby equipment is
inconsistent, the service protection cannot function properly.
l 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.

OptiX OSN 8800/6800/3800
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.
l 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.
l 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
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 re-
configure the DBPS protection group.
----End
Related Information
For details, see "DBPS Protection" in the Feature Description.
4.47 DBMS_DELETE
Description
NE database being deleted. This alarm is generated when the NE enters the database deletion
state after a user deletes the NE database from the flash memory of the system control board.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The NE database will not be automatically backed up to the flash memory of the system control
board until the NE is reset within 48 hours after the NE database is deleted from the flash memory
of the system control board. If the NE is not reset 48 hours later after the NE database is deleted
from the flash memory of the system control board, the NE database are automatically backed
up to the flash memory of the system control board.
Possible Causes
l The possible cause is that a user runs a command to delete the NE database.
Procedure
Step 1 Check whether the NE database is deleted incorrectly. If it is deleted incorrectly, back up the
NE database to the flash memory of the system control board, otherwise, reset the NE.
Step 2 Check whether this alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.48 DBMS_ERROR
Description
Database error. The alarm is generated when the database is in error.
Attribute
Major Process alarm

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x00: The board is working properly.

l 0x01: A database check is performed.
l 0x02: A periodical database backup is performed.
l 0x04: The system is running abnormally.
l 0x08: The database data is inconsistent on the active and standby system
control boards.
l 0x10: Database incremental data fails to be backed up.
l 0x20: Database incremental data fails to be backed up to the NVRAM.
l 0x40: Database incremental data fails to be backed up to the flash memory.
Parameter 2 Indicates the errored data storage area.
l 0x00: OSF1
l 0x01: OSF2
l 0x02: DRDB, indicating the reserved memory database
l 0x03: MDB, indicating the memory database
l 0x04: TDRDB, indicating the temporary memory database
l 0x05: database on the CF card
l 0x06: shared storage area
l 0x0C: NVRAM storage area
Parameter 3 Indicates the ID of the errored database. Currently, the value ranging from 0 to
255 (that is, from 0x00 to 0xff) is supported.
l 0x00: The entire storage area is faulty.

l 0x01 to 0xff: The database with a certain ID is faulty.

The configuration data cannot be saved successfully. As a result, the data is lost.
Possible Causes
l Cause 1: The database operation fails.
l Cause 2: Data in the database is damaged.

OptiX OSN 8800/6800/3800
l Cause 4: The data in the database on the active system control board is inconsistent with
the data in the database on the standby system control board.
Procedure
Step 1 Periodically back up the database to resolve 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.49 DBMS_PROTECT_MODE
Description
Database in the protection mode. This alarm is generated when the NE database is in the
protection mode.
Attribute
Parameters
None

In the protection mode, the NE database cannot be backed up.
Possible Causes
l The number of reset times for the NE in 5 minutes crosses the threshold of the protection
mode.
l The NE delivers 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 it is caused
by human factors,
l On the U2000, perform a warm or cold reset on the system control board to release the
protection mode.

OptiX OSN 8800/6800/3800
l Wait for 2 hours. Release the protection mode after the automatic reset.
----End
Related Information
None
4.50 DCM_INSUFF
Description
Insufficient dispersion compensation margin. This alarm is generated when the dispersion
compensation value is close to the limit of the dispersion compensation margin.
Attribute
Parameters
Parameter 1 The value is fixed at 0xff.
Parameter 2 Indicates the positive or negative dispersion compensation margin. Value 0x00
indicates the positive dispersion compensation margin and 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 DCM module is not properly configured or is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 On the U2000, Check whether an OTUk_LOF alarm is reported. If the OTUk_LOF alarm is
reported, 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.
l 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 that has lower
dispersion compensation capabilities.
l 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 that has higher
dispersion compensation capabilities.
----End
Related Information
Related Cases:
l MC-A240 Isolated Bit Errors Are Found in the Long-Term Bit Error Testing of a 40G
System
4.51 DCNSIZE_OVER
Description
Number of NEs on a DCN subnet exceeding the setting threshold.
Attribute
Parameters
Parameter 1 Indicates the number of NEs on the current DCN subnet.

System resources may be insufficient and therefore services may be affected.

OptiX OSN 8800/6800/3800
Possible Causes
The DCN subnet contains too many NEs.
Procedure
Step 1 Plan the DCN subnet again based on the actual networking.
----End
Related Information
None
4.52 DERIVED_PWR_ERROR
Description
Optical power exception alarm. This alarm is generated when any of the SUM_INPWR_LOW,
SUM_INPWR_HI, and OA_LOW_GAIN alarms is reported.
Attribute
Critical Communication
Parameters
None

The single optical signal output by the board might be lost. The services have bit errors or even
are interrupted.
Possible Causes
l The input optical power is excessively high.
l The input optical power is excessively low.
l The pump laser may be aged.
l The board that reports this alarm is faulty.
Procedure
Step 1 Check whether the input optical power of the input port of the board at the local station is within
the permitted range by using an optical power meter. If the power is not within the permitted
range, add proper attenuation by placing a fixed attenuator or a VOA.

OptiX OSN 8800/6800/3800
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.53 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
Major Processing alarm
Parameters
Name Meaning
Parameters 1 and 2 Indicates the ID of the aggregation group.

OptiX OSN 8800/6800/3800
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.

l The active and standby ports fail to receive the LACP packets.
l The opposite equipment does not enter the LACP synchronization status.
l 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 The communication between the active and standby boards times out.
l The communication between the board and the cross-connect board or SCC board times
out.
l 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.

OptiX OSN 8800/6800/3800
Step 2 If the value of Parameter 3 is 0x01, it indicates that the link becomes faulty or fails.
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 cross-
connect board and the SCC is normal. If the board normally communicates with the cross-
connect 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.54 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.

OptiX OSN 8800/6800/3800
Attribute
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.
Step 2 If the alarm persists, replace the faulty board. For details, see the Parts Replacement.
----End
Related Information
None
4.55 EFI_TYPE_MISMATCH
Description
Mismatch between the EFI board type and subrack type. This alarm is generated when the EFI
board type mismatches the type of the subrack where the EFI board is inserted.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

If the system control board of the subrack is reset after this alarm is reported, data in the NE
database will be lost.
Possible Causes
The EFI board type mismatches the subrack type.
Procedure
Step 1 Check the subrack type of the current NE and replace the EFI board with an EFI board that
matches the subrack type.
----End
Related Information
None
4.56 ERPS_IN_PROTECTION
Description
This alarm is generated when EPRS (Ethernet Ring Protection Switching) switching is triggered.
Indicates that a node on the EPRS ring is faulty.
Attribute
Parameters
Parameters 1 to 2 Indicates the EPRS ring ID.
Parameters 3 Indicates the direction of the fault relative to the ERPS RPL-OWNER node
on the ERPS ring.
l 0x00 indicates in west;

l 0x01 indicates in east.

OptiX OSN 8800/6800/3800
Parameter 4 to 9 Indicating the MAC address of the faulty node.

If one or more nodes on the ring lose connection when services have been configured, services
may be interrupted.
Possible Causes
EPRS switching is triggered by a fault on the ERPS ring (for example, bidirectional fiber cuts).
Procedure
Step 1 Locate the faulty node on the ERPS ring based on the alarm parameter para.
Step 2 Locate the ERPS blocked port on the faulty node and handle the fault.
----End
Related Information
None
4.57 ETH_APS_LOST
Description
The ETH_APS_LOST alarm indicates that the automatic protection switching (APS) frames are
lost. This alarm is generated when no APS frame is received from the protection channel.
Attribute
Parameters
None.

Service protection fails.
The following figure shows the major suppression relationship between the alarm and other
alarms related to the ETH APS protection group.

OptiX OSN 8800/6800/3800
The alarm above an arrow suppresses the alarm below the arrow. For example, the
ETH_APS_PATH_MISMATCH alarm suppresses the ETH_APS_LOST alarm.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
ETH_APS_TYPE_ ETH_APS_
MISMATCH SWITCH_FAIL
Possible Causes
The possible causes of the ETH_APS_LOST alarm are as follows:
l Cause 1: The opposite NE is not configured with APS protection.

l Cause 2: The APS protection group is deactivated.
l Cause 3: The physical link is connected incorrectly or is faulty.
Procedure
Step 1 Cause 1: The opposite NE is not configured with APS protection.
1. On the NMS, check whether the opposite NE is configured with APS protection.
If... Then...
The opposite NE is not configured with APS protection Go to the next step.
The opposite NE is configured with APS protection Go to Step 2.
2. Create a matching APS protection group on the opposite NE, and activate the APS protocol.
Step 2 Cause 2: The APS protection group is deactivated.

1. Check whether the APS protocol is enabled on the opposite NE.
If... Then...
The APS protocol is disabled Disable the APS protocol on the local NE and then
enable the protocol at both ends.
The APS protocol is enabled Go to Step 3.
Step 3 Cause 3: The physical link is connected incorrectly or is faulty.

1. Check whether the protection channel reports an alarm related to signal loss or signal
degrade, such as ETH_LOS. If an alarm related to signal loss or signal degrade is reported,
clear the alarm first.

OptiX OSN 8800/6800/3800
2. Check whether the fiber or cable is connected correctly. If the port on the working channel
is physically connected to the port on the protection channel, one end cannot receive APS
packets from the other end. If the fiber or cable is incorrectly connected, rectify the fiber
or cable connection. Check whether the alarm is cleared.
3. If the alarm persists, check whether the fiber or cable of the protection channel is damaged
or pressed. If the fiber or cable is damaged or pressed, replace the faulty fiber or cable.
engineers for handling the alarm.
----End
Related Information
None.
4.58 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH alarm indicates that the working and protection paths of
the APS protection group differ between the two ends. This alarm is generated when the working
and protection paths at one end are different from the working and protection paths at the other
end.
Attribute
Parameters
None.


OptiX OSN 8800/6800/3800
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
Possible Causes
The possible causes of the ETH_APS_PATH_MISMATCH alarm are as follows:
l Cause 1: The configured working and protection paths at the two ends differ.
l Cause 2: The physical link is connected incorrectly.
Procedure
Step 1 Cause 1: The configured working and protection paths at the two ends differ.
1. On the NMS, check whether the APS settings at both ends are the same. For example, tunnel
1 is set as the working channel and tunnel 2 is set as the protection channel at one end,
whereas tunnel 1 is set as the protection channel and tunnel 2 is set as the working channel
at the other end. For the same tunnel, one end is the working channel, the other end is the
protection channel, and the working and protection channels are different.
2. If the APS settings are different, change them to the same. Then, deactivate and activate
the APS protection groups at both ends. Check whether the alarm is cleared.
Step 2 Cause 2: The physical link is connected incorrectly.
1. Check whether the fiber or cable is incorrectly connected. For example, check whether the
port on the working channel at one end is physically connected to the port on the protection
channel at the other end due to a manual change of the required port. If the fiber or cable
is incorrectly connected, rectify the fiber or cable connection.
----End
Related Information
None.
4.59 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL alarm indicates a protection switching failure. This alarm is
generated when the request signals in the transmitted automatic protection switching (APS)

OptiX OSN 8800/6800/3800
frame are different from the bridge signals in the received APS frame and this symptom lasts
for 50 ms.
Attribute
Parameters
None.

ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
Possible Causes
The possible causes of the ETH_APS_SWITCH_FAIL alarm are as follows:
l Cause 1: The settings of the APS protection group at two ends differ.
l Cause 2: The physical link deteriorates or is connected incorrectly.
Procedure
Step 1 Cause 1: The settings of the APS protection group at two ends differ.
1. On the NMS, check whether the APS settings at both ends are the same. For example, if
the APS protection group is enabled at one end but disabled at the other end, the other end
does not process a received switching request.
2. If the settings are different at the two ends, change them to the same. Then, deactivate and
activate the APS protection groups at both ends.

OptiX OSN 8800/6800/3800
Step 2 Cause 2: The physical link deteriorates or is connected incorrectly.

1. Check whether the protection channel reports an alarm related to signal loss or signal
degrade, such as ETH_LOS. If an alarm related to signal loss or signal degrade is reported,
clear the alarm first.
is physically connected to the port on the protection channel, one end cannot receive a
switching request from the other end. If the fiber or cable is incorrectly connected, rectify
the fiber or cable connection.
----End
Related Information
None.
4.60 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH alarm indicates protection scheme mismatch. This alarm
is generated when the information in the received automatic protection switching (APS) frame
is different from the APS protection scheme specified at the local end.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the specific difference.
l 0x01: Indicates that the switching type is different.

l 0x02: Indicates that the switching direction is different.
l 0x03: Indicates that the revertive mode is different.

OptiX OSN 8800/6800/3800

This alarm may cause the APS protection failure, and therefore the service protection fails.
ETH_APS_PATH_
MISMATCH
ETH_APS_
LOST
Possible Causes
The possible causes of the ETH_APS_TYPE_MISMATCH alarm are as follows:
l Cause 1: The switching types are different.

l Cause 2: The switching directions are different.
l Cause 3: The revertive modes are different.
Procedure
Step 1 On the NMS, check whether the APS settings at both ends are the same. For example, check
whether one end is configured with 1+1 protection, but the other end is configured with 1:1
protection.
Step 2 If they are different, change them to the same. Then, deactivate and activate the APS protection
groups at both ends.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.61 ETH_CFM_AIS
Description
ETH MEP alarm indication signal. This alarm is generated when received an AIS OAM packet,
indicates that the ETH at service level is faulty.
Attribute
Parameters
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 Indicates the level of the maintenance domain.

Possible Causes
The upstream NE detects that a fault occurs at the ETH server layer.
Procedure
Step 1 Check whether there is any defect in the ETH server layer between local NE and upstream NE.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.62 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating service connectivity loss. This alarm is reported
when the system does not receive CCM packets from the remote MEP in the 3.5 times of the
continuity check (CC) period.
Attribute
Parameters
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
l Cause 1: The corresponding MEP at the opposite end is not configured correctly.
l Cause 2: The configuration of the Ethernet services that correspond to the MAs of the MEPs
at both ends is incorrect.
l Cause 3: The service transmission line between the MEPs at both ends is interrupted.
l Cause 4: The network is congested seriously.

OptiX OSN 8800/6800/3800
Procedure
l Cause 1: The corresponding MEP at the opposite end is not configured correctly.
1. Check whether the MEP of opposite end is configured correctly.
2. Modify the configuration of the MEP to ensure consistency at both ends.
l Cause 2: The configuration of the Ethernet services that correspond to the MAs of the MEPs
at both ends is incorrect.
1. Check whether the configuration of the Ethernet services is correct
If... Then...
The configuration is incorrect Modify the configuration of the Ethernet services

to ensure consistency at both ends.
The configuration is correct Go to Cause 3.
l Cause 3: The service transmission line between the MEPs at both ends is interrupted.
1. Check whether the physical links (such as cables or fibers) between the MEPs at both
ends are correct.
If... Then...
The connection is incorrect Connect the cable properly. Check whether the alarm
is cleared. If the alarm persists, go to the next step.
The connection is correct Go to the next step.
2. Check whether the cable connector is connected properly.
If... Then...
The cable connector is loose Connect the cable connector properly.

The cable connector is connected Go to the next step.

properly
3. Check whether the cable is pressed, damaged, peeled off, aged, or cut. If the cable is
faulty, replace the cable. Check whether the alarm is cleared. If the alarm persists, go
to case 4.
l Cause 4: The network is congested seriously.
1. Check the bandwidth utilization of the MEPs at both ends. For example, check whether
the FLOW_OVER alarm is reported.

OptiX OSN 8800/6800/3800
If... Then...
The bandwidth is exhausted Increase the bandwidth or eliminate the root

causes of illegal data transmission. Check
whether the alarm is cleared. If the alarm
persists, contact Huawei technical support
The bandwidth is not exhausted Contact Huawei technical support engineers to

handle the alarm.
----End
Related Information
None
4.63 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).
Attribute
Parameters
Parameter 8 Indicates the level of the MD.

OptiX OSN 8800/6800/3800

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.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
l Cause 3: Certain physical links are incorrectly connected.
Procedure
l Cause 1: The level of the MD to which the MEP belongs is incorrectly configured.
1. 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.
l Cause 2: The MDs and MAs respectively configured at the source and sink ends of the
same service are inconsistent.
1. 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.
l Cause 3: Certain physical links are incorrectly connected.
1. 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.64 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

OptiX OSN 8800/6800/3800
Parameters
Parameters 1 to 4 Indicates the Ethernet port ID.
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.
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.65 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.

OptiX OSN 8800/6800/3800
Attribute
Minor Environment alarm
Parameters
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

OptiX OSN 8800/6800/3800
4.66 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating error frames. This alarm is reported when
the system receives invalid CCM packets.
Attribute
Parameters

The CFM_OAM fails to test the service connectivity. The alarm does not affect services.
Possible Causes
l Cause 1: The cycles of the continuity check (CC) of the MEPs at both ends are different
from each other.
l Cause 2: The IDs of the MEPs at both ends conflict with each other.
l Cause 3: Loopback occurs in the service, and loopback packets are received.
Procedure
l Cause 1:The cycles of the continuity check (CC) of the MEPs at both ends are different
from each other.

OptiX OSN 8800/6800/3800
1. Check whether the CCM periods that are configured on the MEPs at both ends are
consistent. If the CCM periods are inconsistent, change the configuration so that the
CCM periods are consistent.
l Cause 2: The IDs of the MEPs at both ends conflict with each other.
1. If the alarm persists, check whether the same MEP IDs are used in the MD to which
the MEPs of the stations 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.
l Cause 3: Loopback occurs in the service, and loopback packets are received.
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
4.67 ETH_EFM_DF
Description
The ETH_EFM_DF alarm indicates discovery failure. This alarm is generated when the
negotiation of the P2P OAM protocol fails at a port.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the cause of the failure.
l 0x01: The connection at the local end fails.

l 0x02: No OAM packet is received at the local end within a specified period.
l 0x03: The OAM settings of the opposite end do not meet the requirements of
the local end.
l 0x04: The OAM settings of the local end do not meet the requirements of the
opposite end.
l 0x05 - 0xFF: Reserved.

Possible Causes
The possible causes of the ETH_EFM_DF alarm are as follows:
l Cause 1: Hardware equipment on the local end, such as the optical module, boards, or
physical link, is faulty.
l Cause 2: No OAM packet is received at the local end within a specified period.
l Cause 3: The OAM settings of one end do not meet the requirements of the other end.
Procedure
l Cause 1: Hardware equipment on the local end, such as the optical module, boards, or
physical link, is faulty.
1. On the NMS, check whether there are hardware-related alarms at the local end, such
as HARD_BAD and LSR_NO_FITED. If such alarms exist, clear these alarms.
Check whether the ETH_EFM_DF alarm is cleared.
2. If the alarm persists, check whether the optical fiber or Ethernet cable between the
local NE and the opposite NE is faulty. If the optical fiber or Ethernet cable is faulty,
replace the faulty optical fiber or Ethernet cable. Check whether the alarm is cleared.
3. If the alarm persists, go to Cause 2.
l Causes 2 and 3: No OAM packet is received at the local end within a specified period, and
the OAM settings of one end do not meet the requirements of the other end.
1. On the NMS, check whether the port working modes at the two ends are different (for
example, the port working mode at one end is auto-negotiation, while the port working
mode at the other end is 1000M full-duplex). If the port working modes are different,
reset the port working modes. Then, check whether the alarm is cleared.
2. If the alarm persists, check whether the OAM protocol is enabled on the opposite NE.
If not, enable the OAM protocol. Check whether the alarm is cleared.
3. If the alarm persists, check whether the OAM work modes are passive on both sides
of the NEs. For two interconnected systems, the OAM mode of at least one system
must be the active mode. If the OAM work modes are passive on both sides of the

OptiX OSN 8800/6800/3800
NEs, make the setting of the OAM work mode active at one end or two ends according
to the actual situations. Then, check whether the alarm is cleared.
4. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is
fully used. If the bandwidth is fully used, or eliminate the source that transmits a large
amount of invalid data.
----End
Related Information
None.
4.68 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT alarm indicates that an event occurs on the opposite NE. This alarm
is generated when the P2P OAM protocol is enabled and the local end receives an event
indication from the opposite end.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of a link event.
l 0x01: Indicates the errored symbol period.

l 0x02: Indicates the errored frames.
l 0x03: Indicates the errored frame period.
l 0x04: Indicates the errored frame seconds.

Services degradation or even service interruption occurs.
Possible Causes
The possible causes of the ETH_EFM_EVENT alarm are as follows:

OptiX OSN 8800/6800/3800
l Cause 1: Boards at the two ends work improperly.

l Cause 2: The physical link between the two ends is faulty.
Procedure
l Cause 1: Boards at the two ends work abnormally.
1. On the NMS, check whether the opposite NE or the local NE reports any alarms that
are related to the hardware of the optical modules or boards, such as HARD_BAD
and LSR_NO_FITED. If yes, clear these alarms. Then, check whether the
ETH_EFM_EVENT alarm is cleared.
1. Check whether the optical fiber or Ethernet cable between the local NE and the
opposite NE is faulty. If yes, replace the faulty optical fiber or Ethernet cable.
----End
Related Information
None.
4.69 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK alarm indicates a loopback. This alarm is generated when the
P2P OAM protocol is enabled and the local end initiates a loopback or performs a loopback at
the request from the opposite end. If the ports at both ends can respond to a loopback,
l The local OAM port receives the "remote loopback control enable command" issued by
the opposite OAM port, responds to the command, and reports the corresponding alarm,
and the opposite port reports the alarm indicating the initiation of a loopback.
l The local OAM port receives the "remote loopback control disable command" issued by
the opposite OAM port, responds to the command, and clears the corresponding alarm, and
the opposite port clears the alarm indicating the initiation of a loopback.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the loopback status.
l 0x01: initiating a loopback

l 0x02: performing a loopback at the request from the opposite end

Services are looped back.
Possible Causes
The possible causes of the ETH_EFM_LOOPBACK alarm are as follows:
l Cause 1: The local port initiates a loopback and the opposite port performs a loopback at
the request from the local end.
l Cause 2: The opposite port initiates a loopback and the local port performs a loopback at
the request from the opposite end.
Procedure
l Cause 1: The local port initiates a loopback and the opposite port performs a loopback at
the request from the local end.
1. On the NMS, query the alarm information and locate the port that reports the alarm.
2. Set Remote Side Loopback Response of the port to Disabled.
l Cause 2: The opposite port initiates a loopback and the local port performs a loopback at
the request from the opposite end.
1. On the NMS, query the alarm information of the opposite NE and locate the port that
reports the alarm.
2. Set Remote Side Loopback Response of the port to Disabled.
----End
Related Information
None.
4.70 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT alarm indicates that the opposite NE is faulty. This alarm is
generated when the P2P OAM protocol is enabled and the local end receives a fault indication
from the opposite end.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the type of the fault.
l 0x01: A link fault occurs on the opposite port.

l 0x02: An irrecoverable problem such as power failure occurs no the opposite
end.
l 0x03: A critical event occurs on the opposite port.

The opposite end is faulty and services at the port may be unavailable.
Possible Causes
The possible causes of the ETH_EFM_REMFAULT alarm are as follows:
l Cause 1: The opposite port is faulty.

l Cause 2: A board on the opposite NE works improperly.
Procedure
l Cause 1: The opposite port is faulty.
1. On the NMS, check whether the opposite port reports the ETH_LOS or
ETH_LINK_DOWN alarm. If yes, clear these alarms first. Check whether the
ETH_EFM_REMFAULT alarm is cleared.
l Cause 2: A board on the opposite NE works improperly.
1. On the NMS, check whether the opposite NE reports alarms that are related to the
hardware of the optical modules or boards, such as HARD_BAD and
LSR_NO_FITED. If yes, clear these alarms first. Then, check whether the
ETH_EFM_REMFAULT alarm is cleared.

OptiX OSN 8800/6800/3800

1. Check whether the optical fiber or Ethernet cable between the two ends is faulty. If
yes, replace the faulty optical fiber or Ethernet cable.
----End
Related Information
None.
4.71 ETH_LINK_DOWN
Description
Failure of network interface connection.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the Ethernet port number. For example:
0x02 indicates the RM2 or TM2 port.
0x03 indicates the ETH1 port.
0x04 indicates the ETH2 port.

When the ETH_LINK_DOWN alarm is generated during data transmission, the network port
negotiation fails. The data cannot be received and the services are interrupted.
Possible Causes
l The working modes of the transmit and receive ports are inconsistent and the negotiation
fails.
l The link is faulty.

OptiX OSN 8800/6800/3800
l The cable or fiber is incorrectly connected or the opposite equipment is faulty.
Procedure
Step 1 View the alarm on the NMS to determine the board that reports the alarm. Then, determine the
number of the port on the board that reports the alarm.
Step 2 Check whether the working mode of the local port is consistent with that of the opposite port.
If not, modify the modes to the same, and then check whether the alarm is cleared.
Step 3 If the alarm persists, check whether the cable or fiber connection is faulty. If yes, recover the
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 faulty
board at the opposite station, and then check whether the alarm is cleared.
Step 5 If the alarm persists, replace the board that reports the alarm, and then ensure that the working
modes of the ports at the local station and opposite station are consistent. Then the alarm is
cleared.
----End
Related Information
None
4.72 ETH_LOS
Description
The ETH_LOS is an alarm indicating the loss of network connection. This alarm is generated
when the Ethernet port fails to receive any Ethernet signal.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. The value
ranges are different for different boards.
In the case of packet processing boards and packet interface

boards, no parameters are available.
Parameter 2 and Parameter 3 Parameter 2 is always 0x00, and Parameter 3 is always 0x01.
These parameters are meaningless.

The network port fails to receive data and the services are interrupted.
l In the case of an electrical port, the bidirectional services are interrupted.

l In the case of an optical port, the services of certain working modes are interrupted.
If the working mode is set to auto-negotiation, the bidirectional services are interrupted.
If the working mode is set to full duplex, the services in the receive direction are
interrupted.
Common Fault Symptom

NOTE
If this section does not describe the common fault symptom or the actual fault symptom is not contained
in the description of the common fault symptom, handle the ETH_LOS alarm by following the steps
provided in Handling Procedure.
None.
Possible Causes
The possible causes of the ETH_LOS alarm are as follows:
l Cause 1: The port is enabled, but no signal is accessed from the client side.
l Cause 2: The working mode of the local port does not match the working mode of the
opposite port.
l Cause 3: The port is enabled, but the network cable or fiber is connected incorrectly or
faulty.
l Cause 4: The opposite board is faulty.
l Cause 5: The local board is faulty.
Procedure
Step 1 On the NMS, check the alarms. Determine the port that reports the alarm according to the alarm
parameters.
Step 2 Cause 1: The port is enabled, but no signal is accessed from the client side.

OptiX OSN 8800/6800/3800
1. If the services on the Ethernet port are deleted but the Ethernet port is still Enabled, the
ETH_LOS alarm may be reported. Check whether the port accesses signals from the client
side and whether the port is enabled.
2. If the services at the port are deleted, configure services properly. If the port is no longer
required, disable the port.
Step 3 Cause 2: The working mode of the local port does not match the working mode of the opposite
port.
1. Query the working modes of the interconnected ports. Determine whether the ports support
the auto-negotiation mode, and then select a proper working mode.
2. Ensure that the working modes of the interconnected ports are consistent. Then, check
whether the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: The port is enabled, but the network cable or fiber is connected incorrectly or faulty.
1. Check whether the port where the alarm is reported is connected correctly to the network
cable or fiber. If the port is connected incorrectly to the network cable or fiber, connect the
port to the network cable or fiber correctly according to the requirements of the actual
network. Then, check whether the alarm is cleared.
2. Check whether the network cable or fiber jumper at the port is loose. If yes, install the
network cable or fiber jumper correctly. Check whether the alarm is cleared.
3. In the case of an optical port, check whether the fiber connector is dirty. If the fiber
connector is dirty, clean it immediately. Check whether the alarm is cleared.
4. If the alarm persists, exchange the cables or fibers to locate the fault. If the cable or fiber
is faulty, the Ethernet services may be interrupted. Replace the cable or fiber which may
be faulty with a good one. Check whether the alarm is cleared.
Step 5 Cause 4: The opposite board is faulty.
If... Then...
The processing board is an optical port board Go to Step 5.1.
The processing board is an electrical interface board Go to Step 5.3.
1. In the case of an optical port board, check whether the transmit optical power of the opposite
board is within the permitted range on the NMS. For the optical power specifications of
the specific board, see "Technical Specifications" in the Product Description.
If... Then...
The transmit optical power on the Replace the relevant board. Replace the
opposite NE is abnormal board. Check whether the alarm is cleared.

OptiX OSN 8800/6800/3800
If... Then...
The transmit optical power on the Go to the next step.

opposite NE is normal
2. In the case of an electrical interface board, check whether the transmit optical power of the
local board is within the permitted range on the NMS.
If... Then...
The transmit optical power on the local NE is abnormal Go to Step 6.
The transmit optical power on the local NE is normal Go to Step 5.4.
3. In the case of an electrical interface board, check whether the board reports the alarms
indicating the fault of the board or chip, such as HARD_BAD.
If... Then...
One of the preceding alarms is reported Replace the board.
None of the preceding alarms is reported Exchange the boards to locate the fault.
4. If the Ethernet board works with an interface board, replace the interface board first. If the
Ethernet board does not work with any interface board, replace the processing board.
Replace the board. Check whether the alarm is cleared. If the alarm persists, go to Step 6.
Step 6 Cause 5: The local board is faulty.

1. If the Ethernet board works with an interface board, replace the interface board first. If the
Ethernet board does not work with an interface board, replace the processing board.
----End
Related Information
If the negotiated mode of the Ethernet ports is half duplex, signals are transmitted in one direction
at the same time. As a result, the data transmission performance degrades greatly. When the
service traffic is low, packet loss occurs at the interconnected ports. When the service traffic is
high, services are interrupted.
4.73 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.

OptiX OSN 8800/6800/3800
Attribute
Parameters
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.
Procedure
l Cause 1: When subracks are cascaded on a ring network, the ETH3 interface is connected
to a subrack.
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.
4.74 ETH_NO_FLOW
Description
Ethernet port traffic alarm. This alarm is generated when there is no traffic at an Ethernet port.

OptiX OSN 8800/6800/3800
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the direction in which the traffic at an Ethernet port is interrupted. For
example, 0x00 indicates the receive direction and 0x01 receives the transmit
direction.

None
Possible Causes
l The Ethernet port is enabled and linked up, but it is not configured with any services.
l The Ethernet port is enabled and linked up, but the local services are abnormal or no packets
are transmitted from the local port.
l The port is enabled and linked up, but the opposite end is abnormal or no packets are
transmitted to the local end.
Procedure
Step 1 Check whether services are configured at the port where the alarm is generated.
Step 2 Query alarm parameters on the U2000 and determine the traffic interruption direction. If traffic
is interrupted in the transmit direction, check whether services at the local NE are normal. If the
services at the local NE are abnormal, handle the alarm by referring to the procedure for handling
other alarms.
Step 3 Check traffic is interrupted in the receive direction, check whether an exception occurs at the
peer NE and handle the alarm accordingly.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.75 ETH_SERVICE_CONFIG_FAIL
Description
Ethernet service configuration failure alarm.
Attribute
Parameters
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.

OptiX OSN 8800/6800/3800
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.76 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
Parameters

OptiX OSN 8800/6800/3800
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.
l The local end fails to transmit the OAM message.
l The local end fails to receive the OAM message in a specified time.
l The OAM configurations of the opposite end do not meet the requirements of the local end.
l 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 board-
level 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.

OptiX OSN 8800/6800/3800
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
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.77 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
Parameters
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.

OptiX OSN 8800/6800/3800

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
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 for assistance.
----End
Related Information
None
4.78 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
Parameters

OptiX OSN 8800/6800/3800

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.
l 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.79 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

OptiX OSN 8800/6800/3800
Parameters
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.80 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

OptiX OSN 8800/6800/3800
protocol packets sent by itself or the board after detection of the loop is enabled, the
ETHOAM_SELF_LOOP alarm is reported.
Attribute
Parameters
Name Meaning
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.
l Loopback is set among ports of the board.
l 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

OptiX OSN 8800/6800/3800
automatically releases the loopback. Then check whether the ETHOAM_SELF_LOOP alarm is
cleared.
----End
Related Information
None
4.81 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
Parameters
Name Meaning
Parameters 1 and 2 Indicate the VCG port number.
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.

OptiX OSN 8800/6800/3800
Possible Causes
l The links of the VCG port is configured with a self-loop.
l The links between VCG ports of the board is configured with a loop.
l 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.82 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
Parameters

OptiX OSN 8800/6800/3800
Parameters 1 and 2 Indicates the number of the Ethernet port where the alarm is generated.
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.83 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.

OptiX OSN 8800/6800/3800
Attribute
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.84 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

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 2 l When ports are cascaded, this parameter indicates the ID of the slot where
the board is located.
l When ports are not cascaded, the value is always 0xf0.
Parameter 4 l When ports are cascaded:

0x01: The external clock source of the first cascaded port is lost.
0x03: The external clock source of the second cascaded port is lost.
l When ports are not cascaded:
0x02: The first external clock source is lost.
0x04: 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 port for the external clock source loses signals.
l Cause 2: The input and output modes of the external clock source are inconsistent.
l Cause 3: The clock input cable is incorrectly connected.
l Cause 4: The clock board is faulty.
Procedure
l 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.
l Cause 1: The physical port for the external clock source loses signals.
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.
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.

OptiX OSN 8800/6800/3800
l Cause 3: The clock input cable is incorrectly connected.

1. 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 Quick Installation Guide of the applicable
equipment.
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
Related Information
4.85 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm indicating the loss of the external time source. This alarm is
generated when the board does not detect the external timing signal after the external timing
port is enabled.
Attribute
Parameters
Name Meaning
Parameter 2 l When ports are cascaded, this parameter indicates the ID of the slot where
the board is located.
l When ports are not cascaded, the value is always 0xf0.

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 4 Indicates which external time source is lost.
l 0x02: The first external time source is lost.

l 0x04: The second external time 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:
l Cause 1: The physical port for the external time source loses signals.
l Cause 2: The timing input cable is incorrectly connected.
Procedure
l Query alarms on the U2000. Determine the number of the subrack where the external timing
loss occurs and which external time source is lost according to the alarm parameters.
l Cause 1: The physical port for the external time source loses signals.
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.
l Cause 2: The timing input cable is incorrectly connected.
1. 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 of the applicable equipment.
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.

OptiX OSN 8800/6800/3800
4.86 FAN_FAIL
Description
Fan failure. This alarm is generated when two or more fans fail.
Attribute
Parameters
None

The failure of two or more fans leads to the increase of the board temperature and even the
damage to the board.
Possible Causes
l The fans stop running.
l The speed of the fans is excessively low.
l The fans fail.
Procedure
Step 1 On the U2000, check whether the FAN Speed Level is set to Stop or Low Speed. If it is, set
FAN Speed Level to High Speed. For details, see "Setting the Speed Level of Fans".
Step 2 If the alarm persists, replace the faulty fan tray assembly.
----End
Related Information
None
4.87 FAN_FAULT
Description
Fan fault. This alarm is generated when a fan fails.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The failure of one fan may lead to the increase of the board temperature and even the damage
to the board.
Possible Causes
l One fan fails.
l The logical inspection fails.
Procedure
Step 1 Replace the fan tray assembly.
----End
Related Information
None
4.88 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that items listed in an E-LAN forwarding table are
all used. This alarm is generated when the number of actual items in the MAC address table for
the E-LAN service is greater than Address Detection Upper Threshold. This alarm is cleared
automatically when the number of items in the MAC address table of the E-LAN service is lower
than Address Detection Upper Threshold.
Attribute
Minor Service alarm
Parameters
None.

OptiX OSN 8800/6800/3800

When this alarm occurs, the E-LAN service stops learning new MAC addresses. As a result,
unknown unicast packets in the traffic flow may increase, and broadcast packets may increase
accordingly. In this case, the line rate may be affected.
Possible Causes
The possible causes of the FDBSIZEALM_E-LAN alarm are as follows:
l Cause 1: The value of Address Detection Upper Threshold is too small.

l Cause 2: The E-LAN service is attacked.
Procedure
l Cause 1: The value of Address Detection Upper Threshold is too low.
1. On the NMS, check whether the value of Address Detection Upper Threshold is too
small.
2. If yes, set the parameter to a larger value based on actual situations. Check whether
the alarm is cleared. If the alarm persists, go to Cause 2.
l Cause 2: The E-LAN service is attacked.
1. On the NMS, modify the settings so that the E-LAN service discards unknown packets.
----End
Related Information
None.
4.89 FEATURE_WITHOUT_LICENSE
Description
Service without license. This alarm is generated when a license-controlled feature is used but a
license for the feature is not installed.
Attribute
Major Process alarm
Parameters
None

OptiX OSN 8800/6800/3800

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.

l The license file does not match ESN or V/R version, and the system has been operating for
60 consecutive days.
l The trial period of the license-controlled feature has expired, and the keepalive period of
60 days has also elapsed since the expiration.
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
Related Information
None
4.90 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
Parameters
None

The quality of services is affected.

OptiX OSN 8800/6800/3800
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 it is, clean the
optical fiber connector or replace the fiber.
Step 2 Step 2 Check whether the input optical power of the board is within the permitted range. 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.91 FCS_ERR
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
Parameters
None

l If the FCS_ERR alarm is generated due to inconsistent encapsulation protocols, the services
are interrupted.
l If the FCS_ERR alarm is generated due to bit errors in the system, packets are lost or
services are interrupted.

OptiX OSN 8800/6800/3800
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.
l Cause 2: There are bit errors on the link.
l Cause 3: The optical connector of the Ethernet board at the optical port is loose or dirty.
Procedure
l Query current alarms on the U2000. Determine the VCTRUNK number that reports the
alarm.
l 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.
1. Check whether the encapsulation protocols of corresponding VCTRUNK ports of the
local station and the opposite station are consistent and whether the parameter settings
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. If the alarm persists, see Cause 2.
l 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.
l Cause 3: The optical connector of the Ethernet board at the optical port is loose or dirty.
1. Check whether the connector of the fiber is normal. If the connector is loose, tighten
the connector.
2. 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 Product
Description. For operations of adjusting the optical attenuator, see Part
Replacement. For operations of querying the optical power, see Supporting Task.
NOTE
From Supporting Task or Hardware Description, you can obtain the manufacturer information
of the optical module on the board.
4. Check whether the alarm is cleared. If the alarm persists, see Cause 4.

OptiX OSN 8800/6800/3800

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
4.92 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
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.
l The service rate is incorrect.
l The clocks on the NEs are out of synchronization.
l 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

OptiX OSN 8800/6800/3800
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.
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.93 FEC_OOF
Description
The FEC_OOF is an alarm indicating that the FEC is out-of-frame.
Attribute
Parameters
None

When the FEC_OOF alarm is generated, the FEC function is disabled. Consequently, the
services are interrupted.
Possible Causes
l The fiber is faulty, or the optical power is improper.
l Excessive bit errors occur during transmission.

OptiX OSN 8800/6800/3800
l The clocks on the NEs are out of synchronization.

l 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.
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.94 FIBERTYPE_MIS
Description
Mismatch between hardware parameters and fiber types.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

The gain control may be inaccurate.
Possible Causes
The possible causes are as follows:
l The hardware version is earlier than the required version.

l The fiber type is not supported.
Procedure
Step 1 Commission the system by locking optical power.
Step 2 If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.95 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
Parameters
Parameters 1 and 2 Parameter 1 is always 0x00, and Parameter 2 is always 0x01.

OptiX OSN 8800/6800/3800
Parameters 3 and 4 Indicates the extra traffic (Mbit/s) of the actual traffic that exceeds the
expected traffic.

l 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.
l 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. For details, see "Setting the RMON Performance
Monitoring Parameters for an Ethernet Port" in the Supporting Tasks.
l 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.96 FPGA_ABN
Description
FPGA status being abnormal. This alarm is generated when the standby FPGA is currently used
by the board.
Attribute

OptiX OSN 8800/6800/3800
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 will affect services. This problem
needs to be handled in time.
Possible Causes
l The active FPGA file does not exist when the board starts.
l 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.97 FSELECT_STG
Description
The FSELECT_STG is an alarm indicating that the clock board is selected forcibly.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 Indicates the slot of the forcibly selected clock board.
l 0x01: slot with the smaller ID

l 0x02: slot with the larger ID

If the forcibly selected clock board runs properly, services will be interrupted transiently during
the switchover. If the board is faulty, services will be interrupted.
Possible Causes
A command is issued to forcibly select the clock board.
Procedure
Step 1 Cancel the command for forcibly selecting the clock board.
----End
Related Information
None.
4.98 FWD_PKT_LOSS
Description
The FWD_PKT_LOSS is an alarm indicating loss of packets at a certain port
Attribute
Parameters

OptiX OSN 8800/6800/3800
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.
l The packets received by the port do not match the port configuration.
l Packets are lost because of data congestion, such as the loss of the CAR shaping packet.
l The packets in a queue are lost, such as the loss of the COS packet.
l The MAC address of the received packets is listed on the black list.
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.99 GAINDATA_MIS
Description
Mismatch of gain attributes. This alarm is generated when the preset nominal gain value falls
beyond the gain adjustment range supported by a board.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The service quality may be affected.
Possible Causes
Cause 1: As for the nominal gain, replacing an optical amplifier (OA) board or the optical module
causes that the nominal gain value issued by the NE software falls beyond the new gain
adjustment range.
Procedure
l Cause 1: The nominal gain value issued by the NE software falls beyond the new gain
adjustment range.
1. On the U2000, query the threshold of the current actual nominal gain. Reconfigure a
valid nominal gain value for the corresponding optical port and channel of the board
based on the queried threshold.
----End
Related Information
None
4.100 GFP_UPM
Description
Client-side signal type mismatch alarm. This alarm is generated if the UPI in the received TYPE
domain is different from the planned UPI when the GFP encapsulation mode is used.
Attribute

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 1 Indicates the number of the logical port. The parameter value is
always 0x01.
Parameter 2, Parameter 3 Indicates the VCTRUNK number.

After a board receives a packet indicating UPI mismatch, the board chip marks the packet as an
incorrect packet and discards it in the traffic control module. As a result, services are interrupted.
Possible Causes
The UPI in the received TYPE domain is different from the planned UPI when the GFP
encapsulation mode is used.
Procedure
Step 1 Check whether the peer board uses the GFP encapsulation mode.
Step 2 Check whether the GFP encapsulation formats (GFP-T or GFP-F) used by the local and peer
NEs are the same. If they are not the same, modify them as required to ensure that they are the
same.
----End
Related Information
None
4.101 HARD_BAD
Description
Hardware failure. This alarm is generated when the system detects a hardware failure.
Attribute

OptiX OSN 8800/6800/3800
Parameters

OptiX OSN 8800/6800/3800
Parameter 1 Indicates the fault type of the alarm. For example:
0x01: The power supply module is abnormal.
0x02: The board is not properly installed (the board is not in good contact
with the backplane, that is, the board is not secured).
0x03: 38M system clock 1 is abnormal.
0x05: The 2M clock source is abnormal.
0x06: The digital phase-locked loop (PLL) is abnormal.
0x07: The 38M service clock is lost.
0x08: The bus is abnormal.
0x09: The standby board under TPS protection is abnormal.
0x0a: The active crystal oscillator of the clock stops.
0x0b: The frequency deviation of the crystal oscillator is excessively

large.
0x0c: The standby crystal oscillator of the clock stops.
0x0d: The CPU/DSP/coprocessor fails.
0x0e: The memory component the fails.
0x0f: The component of the programmable logic device fails.
0x10: The SDH component fails.
0x11: The data communication component fails.
0x12: The clock component fails.
0x13: The interface component fails.
0x14: The power component fails.
0x15: Other faults occur.
0x16: The simulated PLL is abnormal.
0x17: The 32M clock is invalid.
0x1a: The loop of the cross-connect chip fails.
0x1b: The 8k online signal is pulled down.
0x1c: The chip of the probe laser fails.

OptiX OSN 8800/6800/3800
0x1d: The chip of the loading laser fails.
0x1e: The clock of the DSP driver chip is lost.
0x1f: The output clock of the DSP is lost.
0x20: The RTM module is offline.
0x21: A chip fails.
0x22: 2M system frame header 1 fails.
0x24: The self-check fails.
0x25: The self-check of the PHY chip fails.
0x26: Detecting the port status of the PHY chip fails.
0x27: The 25M clock is lost.
0x28: The APD fails.
Parameters 2 and 3 When parameter 1 is 0x08, bus A is abnormal if parameter 2 is 0x01 and
bus B is abnormal if parameter 2 is 0x02. Parameter 3 is 0xff.
When parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16,
0x19, or 0x21, parameters 2 and 3 have different values, which indicate
different component, module, or chip faults.
When parameter 1 is 0x15, a fault on other components of the local board,

a fault on other boards, or a fault on other components of other boards.
When parameter 1 is of another value, parameters 2 and 3 are fixed at

0xff.

The alarm affects the normal operating of the board and affects services.
Possible Causes
l Cause 1: The NE power supplies are abnormal.
l Cause 2: The board is not connected to the backplane properly or the board is faulty.
Procedure
l Cause 1: The NE power supplies are abnormal.
1. Check whether the NE power supplies are normal. If they are abnormal, apply new
power supplies to the NE.
l Cause 2: The board is not connected to the backplane properly or the board is faulty.

OptiX OSN 8800/6800/3800
1. Remove and re-insert the system control board. Check whether the alarm is cleared.
2. If the alarm persists, replace the board. For details, see "Replace the board.".
----End
Related Information
Related Cases:
l MC-A143 The Service Alarm Indicator on an OTU Board Is Still Red After the
HARD_ERR and HARD_BAD Alarms Are Suppressed
4.102 HARD_ERR
Description
Hardware error. This alarm is generated when the board hardware has a minor fault.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Parameter 1 Indicates the fault type of the alarm. For example:
0x01: The power supply module is abnormal.
0x02: The board is not properly installed (the board is not in good contact
with the backplane, that is, the board is not secured).
0x05: The 2M clock source is abnormal.
0x06: The digital phase-locked loop (PLL) is abnormal.
0x07: The 38M service clock is lost.
0x08: The bus is abnormal.
0x09: The standby board under TPS protection is abnormal.
0x0a: The active crystal oscillator of the clock stops.
0x0b: The frequency deviation of the crystal oscillator is excessively

large.
0x0c: The standby crystal oscillator of the clock stops.
0x0d: The CPU/DSP/coprocessor fails.
0x0e: The memory component the fails.
0x0f: The component of the programmable logic device fails.
0x10: The SDH component fails.
0x11: The data communication component fails.
0x12: The clock component fails.
0x13: The interface component fails.
0x14: The power component fails.
0x15: Other faults occur.
0x16: The simulated PLL is abnormal.
0x1a: The loop of the cross-connect chip fails.
0x1b: The 8k online signal is pulled down.
0x1c: The chip of the probe laser fails.

OptiX OSN 8800/6800/3800
0x1d: The chip of the loading laser fails.
0x1e: The clock of the DSP driver chip is lost.
0x1f: The output clock of the DSP is lost.
0x20: The RTM module is offline.
0x21: A chip fails.
0x24: The self-check fails.
0x25: The self-check of the PHY chip fails.
0x26: Detecting the port status of the PHY chip fails.
Parameters 2 and 3 When parameter 1 is 0x08, bus A is abnormal if parameter 2 is 0x01 and
bus B is abnormal if parameter 2 is 0x02. Parameter 3 is 0xff.
When parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16,
0x19, or 0x21, parameters 2 and 3 have different values, which indicate
different component, module, or chip faults.
When parameter 1 is 0x15, a fault on other components of the local board,

a fault on other boards, or a fault on other components of other boards.
When parameter 1 is of another value, parameters 2 and 3 are fixed at

0xff.

The services are not affected. For specific influence, see Parameter.
Possible Causes
Procedure
Step 1 On the U2000, perform a warm reset or cold reset on the faulty board.
Step 2 If the alarm persists, replace the faulty board. For details, see "Replace the board.".
----End
Related Information
Related Cases:

OptiX OSN 8800/6800/3800
l MC-A143 The Service Alarm Indicator on an OTU Board Is Still Red After the
HARD_ERR and HARD_BAD Alarms Are Suppressed
4.103 HARD_NONSUPPORT
Description
This alarm indicates that the hardware does not support the configuration.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates that some functions configured on the board are not supported by the
board hardware.
l 0x01: ETH PWE3 control words.

l 0x02: 2.5 Gbit/s bus rate is configured.
l 0x03: PW OAM control words (GAL disable).
l 0x04: The transmit optical power is adjustable, or the configured transmit
optical power is beyond the permitted adjustment range.

When this alarm is reported, the configuration cannot take effect. Specifically, when this alarm
is reported during service configuration, the service fails to be applied to the hardware and
therefore cannot be deployed. If this alarm is reported when IEEE 1588 is enabled, the IEEE
1588 function will fail to be enabled.
Possible Causes
The hardware does not support the configuration.

OptiX OSN 8800/6800/3800
Procedure
Step 1 If the alarm parameter is 0x04, set the transmit optical power to the default value or within the
permitted adjustment range on the U2000.
Step 2 Replace the board and use the board supporting functions.
Step 3 Check whether the alarm is cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
None
4.104 HP_LOM
Description
The HP_LOM is an alarm indicating that a higher order path (HP) multiframe is lost.
Attribute
Parameters
Name Meaning

When this alarm occurs, the path-level services are interrupted.
Possible Causes
l Cause 1: The level is inconsistent between source and sink services.
l Cause 2: The cross-connect and clock board is faulty. As a result, the H4 byte is lost or
incorrect.

OptiX OSN 8800/6800/3800
Procedure
Step 1 View this alarm on the NMS and determine the IDs of the port and path that report the alarm.
Step 2 Check whether the level is consistent between the peer to-be-transmitted service and the local
to-be-received service. If the service level is inconsistent, change the service level at either end
to keep its consistency. Then, check whether the HP_LOM alarm is cleared.
Step 3 If the alarm persists, replace the cross-connect and clock board.
----End
Related Information
None.
4.105 HP_RDI
Description
The HP_RDI is an alarm indicating the remote receive failure in the higher order path (HP).
Attribute
Parameters
Name Meaning

When this alarm occurs, the local end is not affected. This alarm indicates only that the remote
path-level service is interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
This is an accompanying alarm. When reporting the AU_AIS, AU_LOP, HP_TIM, or HP_SLM
alarm, the relevant path of the peer line board sends the HP_RDI alarm to the local end.
Procedure
Step 1 Clear the AU_AIS, AU_LOP, HP_TIM, or HP_SLM alarm reported by the relevant path of the
peer line board.
----End
Related Information
None.
4.106 HP_REI
Description
The HP_REI is an alarm indicating remote bit errors in the higher order path (HP).
Attribute
Parameters
Name Meaning

When this alarm occurs, the local NE is not affected. This alarm indicates only that the higher
order services generate error bits when traversing NEs and deteriorates.

OptiX OSN 8800/6800/3800
Possible Causes
This is an accompanying alarm. When a service-traversed NE reports the B3_EXC or B3_SD
alarm after detecting B3 bit errors, it sends the HP_REI alarm to the local NE.
Procedure
Step 1 Clear the B3_EXC or B3_SD alarm reported by a service-traversed NE.
----End
Related Information
None.
4.107 HP_SLM
Description
The HP_SLM is an alarm indicating signal label mismatch in the higher order path (HP). This
alarm is generated when the line board detects the inconsistency between the received and to-
be-received C2 bytes.
Attribute
Parameters
Name Meaning

If the AU-AIS alarm is inserted when the HP_SLM alarm occurs, the path services are
interrupted. In addition, the HP_RDI alarm is transmitted to the peer NE.

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: On the local NE, the received C2 byte (signal label overhead in the HP), which
is not 0x00, is inconsistent with the to-be-received C2 byte.
l Cause 2: The service type is incorrectly configured.
l Cause 3: The board on the terminating NE works improperly.
Procedure
Step 1 Determine the board that initially transmits lower order services by checking the upstream NEs
that have transmitted the services. The board that initially transmits the services is the source of
the C2 byte, while the other NEs transmit the C2 byte transparently. Then, determine the remote
NE that terminates the higher order overhead and transmits the C2 byte to the local NE, and
specify the remote NE as the terminating NE.
Step 2 Check whether the configured service type and to-be-transmitted C2 byte match on the
terminating NE. If they do not match, reconfigure the C2 byte. Then, check whether the HP_SLM
alarm is cleared.
Step 3 If the alarm persists, check whether the configured service type and to-be-received C2 byte match
on the local NE. If they do not match, reconfigure the C2 byte. Then, check whether the HP_SLM
alarm is cleared.
Step 4 If the alarm persists, check whether the configured service type is consistent between the
terminating and local NEs. If the configured service type is inconsistent, modify the service on
the required NE to keep the service consistency. Then, check whether the HP_SLM alarm is
cleared.
Step 5 If the alarm persists, cold reset the receive board of the terminating NE on the NMS or directly
remove and reinsert the board. Then, check whether the HP_SLM alarm is cleared.
Step 6 If the alarm persists, replace the receive board on the terminating NE.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission and termination
Transparent transmission indicates that a service board receives a higher order overhead byte
from an upstream NE and directly transmits it to a downstream NE without processing them.
The higher order overhead byte remains unchanged when it is transmitted from the cross-connect
board to the service board and then to the downstream NE. In most cases, higher order services,
such as the VC-4 service, transparently transmit higher order overhead bytes.
Termination indicates that the higher order overhead byte from the cross-connect board to the
service board is modified and transmitted through the optical port. The source of lower order
services, such as the VC-3 and VC-12 services, terminates higher order overhead bytes.

OptiX OSN 8800/6800/3800
Figure 4-1 shows overhead transparent-transmission and termination.
Figure 4-1 Overhead transparent-transmission and termination

Line board Line board
Higher order Higher order Higher order
path overhead path overhead path overhead
Overhead detection Overhead detection

A Overhead pass-through B Overhead termination
4.108 HP_TIM
Description
The HP_TIM is an alarm indicating the trace identifier mismatch (TIM) in the higher order path
(HP).
Attribute
Parameters
Name Meaning

If the AU-AIS alarm is inserted when the HP_TIM alarm occurs, the path services are interrupted.
In addition, the HP_RDI alarm is transmitted to the peer NE.

OptiX OSN 8800/6800/3800
Possible Causes
l The service cross-connection is incorrectly configured.
l The J1 byte is incorrectly configured.
Procedure
Step 1 Check whether the service cross-connection is correctly configured. If the service cross-
connection is incorrectly configured, correct it. Then, check whether the HP_TIM alarm is
cleared.
Step 2 If the alarm persists, determine the board that initially transmits lower order services by checking
the upstream NEs that have transmitted the services. The board that initially transmits the
services is the source of the J1 byte, while the other NEs transmit the J1 byte transparently. Then,
determine the remote NE that terminates the higher order overhead and transmits the J1 byte to
the local NE, and specify the remote NE as the terminating NE.
Step 3 Check whether the J1 byte to be transmitted by the line board on the terminating NE consists
with the J1 byte to be received by the line board on the local NE. If both J1 bytes are different,
reconfigure the J1 byte on the required NE to keep its consistency.
----End
Related Information
J1 byte (path trace byte)
The J1 byte is used to repetitively transmit an HP access point identifier (APID), which helps
the receive end check whether the channel is correctly connected to the specified transmit end.
Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing them.
The higher order overhead byte remains unchanged when it is transmitted from the cross-connect



OptiX OSN 8800/6800/3800
4.109 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path (HP) carries no overhead. The
received C2 byte is 0x00.
Attribute
Parameters
Name Meaning

If the AU-AIS alarm is inserted when the HP_UNEQ alarm occurs, the path services are
interrupted. In addition, the HP_RDI alarm is transmitted to the peer NE.
Possible Causes
l Services are not configured at the upstream NEs.
l The received C2 byte is 0x00.
Procedure
Step 1 Check whether services are configured on the required path on the peer NE.
If... Then...
Services are not configured Correctly configure services and check whether the HP_UNEQ
alarm is cleared. If the alarm persists, go to Step 2.

OptiX OSN 8800/6800/3800
If... Then...
Services are configured Go to Step 2.
Step 2 Check the service path passing through the upstream NE for the HP_UNEQ alarm.
If... Then...
The alarm exists The upstream NE transparently transmits services with no

overhead to the local NE. In this case, clear the HP_UNEQ alarm
on the path passing through the upstream NE. Then, check whether
the HP_UNEQ alarm is cleared on the local NE. If the alarm
The alarm does not exist Go to Step 3.
Step 3 Determine the board that initially transmits lower order services by checking the upstream NEs
that have transmitted the services. The board that initially transmits the services is the source of
the C2 byte, while the other NEs transmit the C2 byte transparently. Then, determine the remote
NE that terminates the higher order overhead and transmits the C2 byte to the local NE, and
specify the remote NE as the terminating NE.
Step 4 Check whether the C2 byte to be transmitted by the terminating NE is 0x00. If the C2 byte is
0x00, modify it based on the actual service type. Then, check whether the HP_UNEQ alarm is
cleared.
----End
Related Information
C2 byte (signal label byte)
The C2 byte indicates the structures of the higher order virtual containers (VC-3, VC-4, and
VC-4-Xc) and the payload property.
Transparent transmission indicates that a service board receives higher order overhead bytes
from an upstream NE and directly transmits them to a downstream NE without processing. The
higher order overhead byte remains unchanged when it is transmitted from the cross-connect

OptiX OSN 8800/6800/3800


4.110 HSC_UNAVAIL
Description
Working/protection switching failure. This alarm is generated when the configured active and
standby boards fail to perform switching.
Attribute
Parameters
Parameter 1 Indicates the working/protection status of the invalid board.
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.
l The hardware of the standby board is faulty.

OptiX OSN 8800/6800/3800
l Communication between the active and standby boards is abnormal.
Procedure
Step 1 Replace the standby board.
----End
Related Information
None
4.111 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the actual ID of the port on the board.
In the case of packet processing boards and packet interface boards,

no parameters are available.
Parameter 2, Parameter 3 Indicates the path number.

The IN_PWR_ABN alarm affects the transmission performance of the service, and may result
in the service interruption.

OptiX OSN 8800/6800/3800
Common Fault Symptom

NOTE
If the possible causes do not correspond to any symptoms, or the symptoms are not listed in this topic,
handle the alarm according to the handling procedures.
None.
Possible Causes
The possible causes of the IN_PWR_ABN alarm are as follows:
l Cause 1: The threshold of the optical power is not set properly.

l Cause 2: The fiber connector is loose or dirty.
l Cause 3: The model of the selected optical module is incorrect.
l Cause 4: The board at the local end is faulty.
l Cause 5: The board at the opposite end is faulty.
Procedure
Step 1 Cause 1: The threshold of the optical power is not set properly.
1. Query the type of the optical module that reports the alarm.
2. Check whether the optical power threshold is set properly. If the threshold is set improperly,
change Input Power Reference Lower Threshold and Input Power Reference Upper
Threshold according to the receiver sensitivity or overload threshold of the board.
Step 2 Cause 2: The fiber connector is loose or dirty.

1. Check whether the output optical power of the board that is connected to the board that
reports the alarm is within the permitted range.
If... Then...
The output optical power is abnormal Go to Step 4.
The output optical power is normal Go to the next step.
2. Query whether the output optical power of the board that reports the alarm on the local end
is within the permitted range.
If... Then...
The output optical power is abnormal Go to Step 3.
The output optical power is normal Go to the next step.
3. Query whether the input optical power of the board that reports the alarm on the local end
is within the permitted range.

OptiX OSN 8800/6800/3800
If... Then...
The input optical power is abnormal Repeat the following step to check the fiber
jumpers and fiber connectors at both ends in
order.
The input optical power is normal Go to Step 3.
4. Check whether the bend radius of the fiber jumper is within the permitted range. If the bend
radius is less than 6 cm, roll the fiber jumper again. Check whether the alarm is cleared.
5. If the alarm persists, check whether the fiber connector is loose. Ensure that the fiber
connector is firmly connected. Then, check whether the alarm is cleared.
6. If the alarm persists, check whether the fiber connector is dirty.
Step 3 Cause 3: The model of the selected optical module is incorrect.

1. See IN_PWR_LOW to handle faults related to incorrect optical modules. Check whether
the alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 4: The board at the local end is faulty.

1. If the board supports the pluggable optical module, replace the pluggable optical module.
Otherwise, replace the faulty board.
Step 5 Cause 5: The board at the opposite end is faulty.

1. Handle the fault in the transmit unit at the opposite end. For details, see Step 4. Check
whether the alarm is cleared. If the alarm persists, contact Huawei technical support
----End
Related Information
None.
4.112 INSERTION_LOSS_HIGH
Description
This alarm is generated when the insertion loss between the TDC and RDC is excessively large
or does not match the gain.
Attribute
Major Process alarm

OptiX OSN 8800/6800/3800
Parameters
Name Meaning

The gain adjustment of the optical amplifier board fails, which results in a command issuing
failure.
Possible Causes
The insertion loss between the input and output ports of the DCM connected to the optical
amplifier board is excessively large or does not match the gain.
Procedure
Step 1 Check whether the insertion loss between the input and output ports of the DCM connected to
the optical amplifier board is excessively large. If it is excessively large, the fiber connector
connected to the input or output port may be dirty or the pigtail may be bent. Clean the fiber
connector or replace the pigtail.
Step 2 On the U2000, query the actual permitted gain range of optical amplifier board and set the gain
again to ensure that the gain is within the permitted range.
----End
Related Information
None
4.113 INTRA_OTU_STA_INDI
Description
Status indication of an intra-board 1+1 protection group. This alarm is generated when the
working or protection channel of the protection group is faulty or the user delivers an external
switching command.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Parameter 1 Indicate the switch request status. For example:

l 0x0F: Lockout switching
l 0x0E: Forced switching
l 0x06: Exercise switching
l 0x05: WTR

l When the intra-board 1+1 protection group undergoes switching, services are transiently
interrupted.
l 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 delivers a command to perform the external switching such as forced
switching, manual switching, or locked switching.
l Cause 2: The services of the working channel or the protection channel of the intra-board
1+1 protection group are faulty.
l Cause 3: The switching is in WTR state. After the time specified by WTR Times elapses,
the alarm clears.
Procedure
l Cause 1: A user delivers a command to perform external switching.
state is forced switching, manual switching, or locked switching, check whether the
external switching operation is necessary.

OptiX OSN 8800/6800/3800

external switching.
l 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 associated 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 there are such alarms, handle the alarms by referring to the
corresponding alarm handling procedure to restore the services of the working channel
or the protection channel.
Revertive. If it is, after WTR Times the protection channel automatically switches
to the working channel and the alarm clears. If the attribute is Non-Revertive, set it
to Revertive. The active channel automatically switches to the working channel and
after WTR Times the alarm clears.
l Cause 3: The switching is in the WTR state. After the time specified by WTR Times
elapses, the alarm clears.
1. This alarm requires no handling. After the time specified by WTR Times elapses, the
alarm clears.
----End
Related Information
For details, see "Intra-Board 1+1 Protection" in the Feature Description.
4.114 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
Parameters
None

OptiX OSN 8800/6800/3800

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.
l The line loss is excessive. As a result, the input optical power is lower than the LOS
threshold of the board.
l 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
Related Information
OptiX OSN 8800 provides the intelligent power adjustment (IPA) function for PID boards. For
details, see "Introduction to PID IPA" in the Feature Description.
4.115 J0_MM
Description
J0 byte or trace indicator mismatch. This alarm is generated when the received J0 byte is not
consistent with the J0 byte to be received.
Attribute
Parameters
None

The services are not affected.

OptiX OSN 8800/6800/3800
Possible Causes
l The J0 byte mismatches.
l 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 them
to the same.
Step 2 If the alarm persists, bit errors may exist on the line. See the handling procedure of the B1_SD
alarm for troubleshooting.
Step 3 If the alarm persists, consider whether to replace the board as required because only the J0_MM
alarm does not affect the services.
----End
Related Information
None
4.116 K1_K2_M
Description
The K1_K2_M is an alarm indicating a mismatch between the K1 and K2 bytes. This alarm is
generated when the K1 and K2 bytes indicates different channel numbers for a given period
(default: 160 ms).
Attribute
Parameters
None.

When this alarm occurs, the multiplex section protection (MSP) is unavailable. If the fiber cut
or another fault occurs, services may be interrupted.
Possible Causes
l The optical fiber is connected incorrectly.
l The MSP group type is inconsistent between both ends.

OptiX OSN 8800/6800/3800

l The cross-connect board is faulty.
Procedure
Step 1 Verify that the optical fiber of the multiplex section (MS) is properly connected and the logic
configuration of the fiber matches its physical configuration. Then, check whether the K1_K2_M
alarm is cleared.
Step 2 If the alarm persists, check whether the MSP group type is consistent between both ends. If the
MSP group type is inconsistent, reconfigure the MSP group to keep its consistency between both
ends. Then, check whether the K1_K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If either
board is faulty, replace it and check whether the K1_K2_M alarm is cleared.
Step 4 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If either
board is faulty, replace it.
----End
Related Information
None.
4.117 K2_M
Description
The K2_M is an alarm indicating a K2 byte mismatch. This alarm is generated when the fifth
bit of the received K2 byte indicates a specified period (default: 2s) of inconsistency between
the peer and local multiplex section protection (MSP) modes.
Attribute
Parameters
None.

When this alarm occurs, the MSP is unavailable. If the fiber cut or another fault occurs, services
may be interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
l The multiplex section (MS) configuration is incorrect.
Procedure
Step 1 Check whether the MS configuration is consistent between the local and peer NEs. If the MS
configuration is inconsistent, reconfigure the MS to keep its consistency between both NEs.
Then, check whether the K2_M alarm is cleared.
Step 2 If the alarm persists, check whether the local and peer MS-configured boards are faulty. If either
board is faulty, replace it and check whether the K2_M alarm is cleared.
Step 3 If the alarm persists, check whether the local and peer cross-connect boards are faulty. If either
board is faulty, replace it and check whether the K2_M alarm is cleared.
----End
Related Information
None.
4.118 L_SYNC
Description
Loss of synchronization. This alarm is generated when loss of synchronization occurs in the
physical coding sublayer (PCS) of a receiving port.
Attribute
Critical Service quality alarm
Parameters
None

When loss of synchronization occurs in the PCS of a receiving port, the port stops receiving
data. Therefore, this alarm affects the quality of services (QoS). In this case, services are
interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
l The peer end and the local end have different settings in the working mode of the Ethernet
port and in the types of services received on the client side.
l Link failure.
l The equipment at the opposite station is faulty.
l The receive optical power of the board at the local station is abnormal.
l The board at the local station is faulty.
Procedure
Step 1 Check whether the working mode (autonegotiation/full-duplex/half-duplex) of the Ethernet port
at the peer end is consistent with that of the local end. If they are inconsistent, modify the setting
to ensure the consistency.
Step 2 Check whether the service types configured for the local end are consistent with the actual service
types. If they are inconsistent, modify the setting to ensure the consistency.
Step 3 If the alarm persists, check whether the fiber or cable that is used to connect the equipment at
the local station and that at the opposite station are well connected. If they are not well connected,
reconnect or replace the fiber or cable.
Step 4 If the alarm persists, check whether the data equipment at the opposite station is faulty. If it is,
remove the fault of the data equipment at the opposite station.
Step 5 If the alarm remains, use the U2000 to check whether the receive optical power of the optical
ports on the alarm-reporting board is within the permitted range. If the optical power is abnormal,
take the alarm as the IN_PWR_HIGH or IN_PWR_LOW alarm for troubleshooting.
Step 6 If the alarm persists, the board at the local station may be faulty. Replace the board.
----End
Related Information
None
4.119 LAG_DOWN
Description
The LAG_DOWN alarm indicates that a link aggregation group (LAG) is unavailable. This
alarm is generated when the number of activated members in a LAG is 0.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None.

Possible Causes
The possible causes of the LAG_DOWN alarm are as follows:
l Cause 1: The opposite NE is not configured with any LAGs.

l Cause 2: All member ports in the LAG are unavailable.
Procedure
Step 1 Cause 1: The opposite NE is not configured with any LAGs.
1. Check whether the opposite NE is configured with a LAG.
2. If not, configure a LAG on the opposite NE. Check whether the alarm is cleared. If the
Step 2 Cause 2: All member ports in the LAG are unavailable.

1. Check whether the ETH_LOS, ETH_LINK_DOWN, or LAG_MEMBER_DOWN alarm
is reported. If yes, clear the ETH_LOS, ETH_LINK_DOWN, or
LAG_MEMBER_DOWN alarm.
2. Check whether the LAG_DOWN alarm is cleared. If the alarm persists, contact Huawei
technical support engineers for handling the alarm.
----End
Related Information
None.
4.120 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN alarm indicates that a member port in the link aggregation group
(LAG) is unavailable. This alarm is generated when a member port cannot be activated and
cannot work as the backup port.
Attribute

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the board ID.
Parameter 3 Indicates the sub-board ID (0xFF: no sub-board).
Parameter 4, Parameter 5 Indicates the port ID.
Parameter 6 Indicates the cause that makes the port unavailable.
l 0x01: The port is disabled or link down occurs on the port.

l 0x02: The port receives no LACP packet.
l 0x03: The port works in half-duplex mode.
l 0x04: The port is looped back.

The impact on the system varies depending on the load-sharing mode used.
l In load-sharing mode, packet loss may occur continuously due to bandwidth insufficiency.
l In load non-sharing mode, link switching is triggered and packet loss occurs temporarily.
Possible Causes
The possible causes of the ETH_LINK_DOWN alarm are as follows:
l Cause 1: The port is unavailable or is disabled.

l Cause 2: The port receives no LACP packet.
l Cause 3: The port works in half-duplex mode.
l Cause 4: The port is looped back.
Procedure
Step 1 On the U2000, query parameters of the reported alarm.
l If the alarm cause is 0x01, go to Step 2.
Step 2 Cause 1: The port is unavailable or is disabled.

OptiX OSN 8800/6800/3800
1. Check whether the alarmed port reports the ETH_LOS or ETH_LINK_DOWN alarm. If
yes, clear the ETH_LOS or ETH_LINK_DOWN alarm before first. Check whether the
LAG_MEMBER_DOWN alarm is cleared.
2. If the alarm persists, check whether the alarmed port is enabled. If it is not enabled, enable
it and then check whether the alarm is cleared. If the alarm persists, go to Step 3.
Step 3 Cause 2: The port receives no LACP packet.

1. Check whether LAG parameters (such as the LAG aggregation type and LAG load-sharing
mode) at both ends are set the same. If not, set them the same. Check whether the alarm is
cleared.
2. If the alarm persists, check whether LAG member ports at both ends match each other. For
example, check whether a member port is deleted by misoperation. If yes, add ports to the
LAG group, and then check whether the alarm is cleared.
3. If the alarm persists, check whether the fiber connection is correct. Verify that the fiber
connection is correct, and then check whether the LAG_MEMBER_DOWN alarm is
cleared.
4. If the alarm persists, check the traffic state and QoS settings on the alarmed port. For
example, check whether the alarmed port reports the FLOW_OVER alarm or is configured
with rate limiting, which may cause packet loss. Verify that no FLOW_OVER alarm is
reported and no rate limiting is configured, and then check whether the
LAG_MEMBER_DOWN alarm is cleared. If the alarm persists, go to Step 4.
Step 4 Cause 3: The port works in half-duplex mode.

1. Check the working modes of LAG ports at both ends. Verify that the LAG ports work in
auto-negotiation mode or full-duplex mode, and then check whether the alarm is cleared.
Step 5 Cause 4: The port is looped back.

1. Check whether a software loopback (such as a PHY/MAC layer loopback) or hardware
loopback (such as loopback using network cables or optical fibers) is enabled at the alarmed
port. If yes, release the loopback. Check whether the alarm is cleared.
2. If the alarm persists, check whether there is switching equipment (such as a switch,
concentrator, or hub) between both ends of the LAG. If there is switching equipment, check
whether a loopback is enabled on the switching equipment or a loopback occurs due to
broadcast on the switching equipment. Release the loopback and then check whether the
alarm is cleared.
3. If the alarm persists, check whether port MAC addresses or NE MAC addresses at both
ends of the LAG are the same. If they are the same, a loopback occurs. Release the loopback
and then check whether the alarm is cleared.
4. If the alarm persists, contact Huawei technical support engineers for handling the alarm.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.121 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
Minor Process alarm
Parameters
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, 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 self-
looped.

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.
l The port is in the half-duplex mode.
l The port has not received LACP messages.
l The port is self-looped.

OptiX OSN 8800/6800/3800
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, re-
set 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.122 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.
Attribute
Minor Process alarm
Parameters
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.

OptiX OSN 8800/6800/3800
Name Meaning
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 self-
looped.

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.
l The port has not received LACP messages.
l 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
4.123 LAN_LOC
Description
Ethernet communication failure. In the case of NE cascading, this alarm is generated when the
Ethernet communication between NEs fails.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

The communication at this network port fails and some NEs may be unreachable, but the services
on the NEs are not affected.
Possible Causes
l The network port is required and is enabled on the U2000. However, the network cable is
not connected or incorrectly connected to the network port.
l The network port is not required but is enabled on the U2000.
l The network cable is faulty.
Procedure
Step 1 Query the alarm information on the U2000. Check whether the corresponding network port is
required according to the alarm parameters,
If ... Then ...
The corresponding network port is not Disable the port on the U2000.
required.
Disable the port
The corresponding network port is required. Verify that the network cable is properly
connected to the network port and the
network ports at the both ends of the
network cable are in working state.
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.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.124 LASER_HAZARD_WARNING
Description
Hazard related to laser levels. When a high-power laser is used in the optical transmission system,
the system may cause personal injuries. In this case, if the IPA function is disabled or not
configured, this alarm is reported prompting the user to configure the IPA function.
Attribute
Critical Environment alarm
Parameters
Name Meaning
Parameter 1 Indicates the working band. 0x01 indicates the C-band and 0x02 indicates the L-
band.

This alarm does not affect services; however, it might cause personal injuries.
Possible Causes
l The laser power is high and the IPA function is not configured.
l The laser power is high and the IPA function is disabled although it has been configured.
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 IPA function is not configured for the NE, follow the network plan to create 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.

OptiX OSN 8800/6800/3800
Step 3 If the IPA function is configured for the NE but is disabled, 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.
Step 4 After the IPA function is configured and enabled, the alarm is cleared automatically. If the alarm
persists, contact Huawei for assistance.
----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.
Related Cases:
l MC-A175 How to Clear the LASER_HAZARD_WARNING Alarms Reported on Certain
OBU and OAU Boards After an Upgrade of Software
4.125 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating mismatch of optical modules. When the type
of the optical module inserted does not match the type supported by the board, this alarm occurs.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the number of the optical port of the board.


OptiX OSN 8800/6800/3800
Name Meaning
Parameter 2, Parameter 3 Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These
parameters are meaningless.
In the case of E1 optical port processing boards, these parameters

indicate the path number.

When the installed optical module is incorrect, the performance of the optical port is degraded.
In severe cases, the services are interrupted.
Possible Causes
The possible causes of the LASER_MOD_ERR alarm are as follows:
l The rate of the optical module inserted does not match the rate of the optical port of the
board.
l The type of the inserted optical module and the type of the port on the actual board
mismatch.
Procedure
Step 1 View the LASER_MOD_ERR alarm on the NMS and confirm the relevant board.
Step 2 Replace the optical module. The alarm is automatically cleared.
----End
Related Information
None.
4.126 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser of the board is shut down.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

When the LASER_SHUT alarm is generated, the services are interrupted.
Possible Causes
The user uses the U2000 to perform the operation to shut down the laser.
l Cause 1: For OCS system boards, the user uses the U2000 or Navigator to perform the
operation to shut down the laser.
l Cause 2: For a non-coherent 40G board in a WDM system, the laser is shut down because
the board temperature exceeds the permitted range.
Procedure
l Cause 1: For OCS system boards, the user uses the U2000 to perform the operation to shut
down the laser.
1. If the user cancels the setting of laser shutdown, the LASER_SHUT alarm is
l Cause 2: For a non-coherent 40G board in a WDM system, the laser is shut down because
the board temperature exceeds the permitted range.
1. Decease the board temperature to the normal level, and check whether the alarm is
cleared.
2. If the alarm persists, turn on the laser or perform a cold reset on the board.
----End
Related Information
None
4.127 LCS_DAYS_OF_GRACE
Description
License in keepalive period. This alarm indicates that the license has expired but is within the
keepalive period of 60 days.
Attribute
Major Process alarm
Parameters

OptiX OSN 8800/6800/3800

Name Meaning
Parameters 1 and 2 l 0x00 0x00 indicate the file level alarm.

l Other values indicate the control item ID.
Parameters 3 and 4 Indicate the number of days.
Parameter 5 l Indicates that the license or control-item expire naturally when the
parameter value is 0x00.
l Indicates that the license has been revoked when the parameter value
is 0x01.
l Indicates ESN mismatching when the parameter value is 0x02.
l Indicates V/R mismatching when the parameter value is 0x03.
l Indicates ESN and V/R mismatching when the parameter value is
0x04.
When parameters 1 and 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 The license file fails. The system is in the trial state and within the keepalive period of 60
days.
l 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.
l The license-controlled items exceed the expiration date but is within the keepalive period
of 60 days.
Procedure
Step 1 Load a license file to the system.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.128 LCS_EXPIRED
Description
License expired. This alarm indicates that the license has expired and the keepalive period of
60 days has also elapsed.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicate the number of days.
Parameter 3 l Indicates that the license has been revoked when the parameter value
is 0x01.
l Indicates ESN mismatching when the parameter value is 0x02.
l Indicates V/R mismatching when the parameter value is 0x03.
l Indicates ESN and V/R mismatching when the parameter value is
0x00.

When the license has expired and the keepalive period of 60 days has also elapsed, only the
default functions of the system are available.
Possible Causes
l The license of the system has expired and the keepalive period of 60 days has also elapsed.
l The system license file does not match the ESN or V/R version, and the keepalive period
of 60 days has elapsed.
Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.129 LCS_FILE_NOT_EXIST
Description
No license file. This alarm indicates that the system is under license control but no license file
is loaded to the system.
Attribute
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
4.130 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating the link capacity adjustment scheme (LCAS) protocol
fails in the receive direction. This alarm is generated when the system detects an exception on
the LCAS sink, which may result in an LCAS negotiation failure or error.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

When this alarm occurs, the protocol state machine in the receive direction is confused, which
may result in improper negotiation.
Possible Causes
l The downstream VCTRUNK port receives duplicate sequence numbers due to incorrect
configuration or link bit errors.
l The LCAS function is not enabled on the peer VCTRUNK port.
l The downstream VCTRUNK port concurrently receives the FIXED and other LCAS
control words due to incorrect configuration or link bit errors.
l The cross-connection is incorrectly bound.
Procedure
Step 1 View the alarm on the NMS and determine the ID of the VCTRUNK port.
Step 2 Check whether the LCAS protocol is enabled at the peer end. If the protocol is not enabled at
the peer end, enable it and check whether the LCAS_FOPR alarm is cleared.
Step 3 If the alarm persists, check whether configurations, especially timeslot cross-connection binding,
are correct. If there are incorrect configurations, correct them and check whether the
LCAS_FOPR alarm is cleared.
Step 4 If the alarm persists, disable the LCAS protocol at both ends and concurrently enable it. Then,
check whether the LCAS_FOPR alarm is cleared.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.131 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating the LCAS protocol fails in the transmit direction. This
alarm is generated when the system detects an exception on the LCAS source, which may result
in an LCAS negotiation failure or error.
Attribute
Parameters
None.

When this alarm occurs, the protocol state machine in the transmit direction is confused, which
may result in improper negotiation.
Possible Causes
An unexpected multiplex section termination (MST) occurs and lasts long due to incorrect
configurations and invalid links.
Procedure
Step 2 Verify that the service cross-connection is bound correctly on the VCTRUNK port. Then, check
whether the LCAS_FOPT alarm is cleared.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.132 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating loss of partial bandwidth in the LCAS receive direction.
This alarm is generated when only some of the configured channels carry load in the receive
direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the available bandwidth in the receive direction decreases, but services
still keep running.
Possible Causes
l Bidirectional services are not configured.
l The downstream channels bound at the local end outnumber the upstream channels bound
at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.
Procedure
Step 1 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_PLCR alarm is cleared.
Step 2 If the alarm persists, verify the connectivity of the physical link and check whether bidirectional
services are configured. If bidirectional services are not configured, correctly configure them
and check whether the LCAS_PLCR alarm is cleared.
Step 3 If the alarm persists, check whether the number of downstream timeslots configured for the local
VCTRUNK port is consistent with that of upstream timeslots configured for the peer VCTRUNK
port on the NMS. If the number of timeslots is inconsistent, add or delete timeslots as required
to make the number of timeslots consistent. Then, check whether the LCAS_PLCR alarm is
cleared.

OptiX OSN 8800/6800/3800
Step 4 Check whether the cross-connections are bound from the transmit end to the receive end. If the
cross-connections are not bound, bind them and check whether the LCAS_PLCR alarm is
cleared.
Step 5 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR expires.
Then, check whether the LCAS_PLCR alarm is cleared.
Step 6 If the alarm persists, disable and enable the LCAS protocol on the VCTRUNK port. Then, check
whether the LCAS_PLCR alarm is cleared.
Step 7 If the alarm persists, delete and re-bind all physical channels of the VCTRUNK port and check
whether the LCAS_PLCR alarm is cleared.
Step 8 If the alarm persists, cold reset the board and check whether the LCAS_PLCR alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_PLCR alarm is cleared.
----End
Related Information
None.
4.133 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating loss of partial bandwidth in the LCAS transmit
direction. This alarm is generated when only some of the configured channels carry load in the
transmit direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Minor Service alarm
Parameters
None.

When this alarm occurs, the available bandwidth in the transmit direction decreases. This results
in packet loss when the actual outgoing traffic exceeds the available bandwidth.

OptiX OSN 8800/6800/3800
Possible Causes
l The upstream channels bound at the local end outnumber the downstream channels bound
at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or
improperly connected physical links.
Procedure
Step 2 Check the peer end for the LCAS_PLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_PLCT alarm is cleared.
Step 3 If the alarm persists, check whether bidirectional services are configured on the port. If
bidirectional services are not configured, correctly configure them and check whether the
LCAS_PLCT alarm is cleared.
Step 4 If the alarm persists, check whether the number of upstream timeslots configured for the local
VCTRUNK port is consistent with that of downstream timeslots configured for the peer
VCTRUNK port on the NMS. If the number of timeslots is inconsistent, add or delete timeslots
as required to make the number of timeslots consistent. Then, check whether the LCAS_PLCT
alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit end
to the receive end.
Step 6 If the alarm persists, check the wait-to-restore (WTR) duration and wait until the WTR expires.
Then, check whether the LCAS_PLCT alarm is cleared.
Step 7 If the alarm persists, disable and enable the LCAS function on the VCTRUNK port. Then, check
whether the LCAS_PLCT alarm is cleared.
whether the LCAS_PLCT alarm is cleared.
Step 9 If the alarm persists, cold reset the board and check whether the LCAS_PLCT alarm is cleared.
Step 10 If the alarm persists, replace the board and check whether the LCAS_PLCT alarm is cleared.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.134 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating loss of all bandwidth in the LCAS receive direction.
This alarm is generated when none of the configured channels carries load in the receive direction
after the LCAS function is enabled on the VCTRUNK port.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, no bandwidth is available in the receive direction. That is, services are
interrupted in this direction.
Possible Causes
l The upstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or other
alarms.
Procedure
Step 2 Check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM. If any of them
exists, clear it first and check whether the LCAS_TLCR alarm is cleared.
Step 3 If the alarm persists, verify the connectivity of the physical link and check whether bidirectional
services are configured. If bidirectional services are not configured, correctly configure them
and check whether the LCAS_TLCR alarm is cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the upstream direction at the peer
end. If timeslots are not bound in the upstream direction, correctly bind them and check whether
the LCAS_TLCR alarm is cleared.
Step 5 If the alarm persists, verify that the cross-connections are correctly bound from the transmit end
to the receive end. Then, check whether the LCAS_TLCR alarm is cleared.

OptiX OSN 8800/6800/3800
whether the LCAS_TLCR alarm is cleared.
whether the LCAS_TLCR alarm is cleared.
Step 8 If the alarm persists, cold reset the board.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCR alarm is cleared.
----End
Related Information
None.
4.135 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating loss of all bandwidth in the LCAS transmit direction.
This alarm is generated when none of the configured channels carries load in the transmit
direction after the LCAS function is enabled on the VCTRUNK port.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, there is no available bandwidth in the transmit direction. That is, services
are interrupted in this direction.
Possible Causes
l The downstream channels are not bound at the peer end.
l The channel transmission fails. For example, there are incorrect cross-connections or other
alarms.

OptiX OSN 8800/6800/3800
Procedure
Step 2 Check the peer end for the LCAS_TLCR alarm. If the alarm exists at the peer end, clear it and
check whether the LCAS_TLCT alarm is cleared.
Step 3 If the alarm persists, check the system for other alarms, such as the AIS, LOP, UNEQ, and LOM.
If any of them exists, clear it first and check whether the LCAS_TLCT alarm is cleared.
Step 4 If the alarm persists, check whether timeslots are bound in the downstream direction at the peer
end. If timeslots are not bound in the downstream direction, correctly bind them and check
whether the LCAS_TLCT alarm is cleared.
Step 5 Verify that the cross-connections are correctly bound from the transmit end to the receive end.
Then, check whether the LCAS_TLCT alarm is cleared.
Step 8 If the alarm persists, cold reset the board and check whether the LCAS_TLCT alarm is cleared.
Step 9 If the alarm persists, replace the board and check whether the LCAS_TLCT alarm is cleared.
----End
Related Information
None.
4.136 LOCAL_FAULT
Description
Local fault alarm.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

If the board receives the LOCAL_FAULT alarm, the received services may be interrupted.
Possible Causes
l The input fiber on the client side is transiently cut.
l The board receives various bit errors.
l 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 optical port on
the client side of the board is overlarge, and whether the fiber is aged or loose. If it is, clean the
fiber connector or replace the fiber.
Step 2 Check whether the output optical power of the input equipment is within the permitted range.
If the optical power is abnormal, rectify the fault of the input equipment.
----End
Related Information
None
4.137 LOCK_CUR_FAIL
Description
Failure to lock the working current. The alarm occurs when the working current is abnormal.
Attribute
Parameters
Parameter 1 Indicates the number of the pump laser.

OptiX OSN 8800/6800/3800

The output optical power of the board will fail to be locked, which influences the services on
the entire optical line.
Possible Causes
Procedure
Step 1 Perform a warm reset on the faulty board on the U2000.
----End
Related Information
None
4.138 LOCKPOW_MIS
Description
Mismatch of locked pump optical power. This alarm is generated when the configured locked
pump optical power and the actual locked pump optical power of the board are inconsistent.
Attribute
Parameters
None

Possible Causes
The configured locked pump optical power and the actual locked pump optical power of the
board are inconsistent

OptiX OSN 8800/6800/3800
Procedure
Step 1 Reconfigure the locked pump optical power of the board on the U2000.
----End
Related Information
None
4.139 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating a remote receive failure on the VC-3 path. This alarm
is generated when a board detects bit 5 of the G1 byte is 1 for the VC-3 path.
Attribute
Parameters
None.

This alarm does not affect the local services, but indicates that services fail to be received by
the remote end.
Possible Causes
The peer end receives alarms, such as TU_AIS_VC3 and TU_LOP_VC3.
Procedure
Step 1 On the NMS, check for severer alarms, such as such as TU_AIS_VC3 and TU_LOP_VC3. Clear
these alarms first.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.140 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating a mismatch between C2 bytes identifying VC-3
signals.
Attribute
Parameters
None.

When this alarm occurs, the system is not affected.
Possible Causes
l The type is inconsistent between the received and to-be-received signals. That is, the
received and to-be-received C2 bytes are different.
l The service type is set incorrectly.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Check whether the C2 byte is consistent between the VC-3 paths at the local and peer ends. If
the C2 byte is inconsistent, modify the C2 byte on the VC-3 path at either end to keep its
consistency. Then, check whether the LP_SLM_VC3 alarm is cleared.
Step 3 If the alarm persists, check whether the VC-3 services are correctly configured. If the services
are incorrectly configured, correctly configure them and check whether the LP_SLM_VC3 alarm
is cleared.
Step 4 If the alarm persists, replace the local board that reports the alarm.
Step 5 If the alarm still persists, replace the peer board as required.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.141 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 path carries no service. This alarm is
generated when a board detects that the C2 byte is 0.
Attribute
Parameters
None.

When this alarm occurs, the VC-3 path carries no service. If the alarm is caused by the incorrect
service configurations or no accessed service, services will be interrupted.
Possible Causes
l The service type is set incorrectly.
l No service is accessed.
Procedure
Step 1 View the alarm on the NMS and determine the number of the path that reports the alarm.
Step 2 Verify that the service type is correctly set and services are correctly accessed. Then, check
whether the LP_UNEQ_VC3 alarm is cleared.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.142 LPT_RFI
Description
The LPT_RFI is an alarm indicating that the link-state pass through (LPT) detects a remote port
failure. This alarm is generated when the LPT detects that a remote port or its LPT service
network fails.
Attribute
Parameters
None.

When this alarm occurs during data transmission, the active link is unavailable and services are
interrupted, which enables the standby link.
Possible Causes
l The remote port fails. For example, the port reports the LINK_ERR alarm or is not enabled.
l The LPT service network is faulty when:
Fiber cut occurs.
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 alarm on the NMS, and determine the board that reports the alarm and the ID of the
port that reports the alarm according to alarm parameters.
Step 2 Check whether the remote port is enabled. If the port is not enabled, enable it and check whether
the LPT_RFI alarm is cleared.
Step 3 If the alarm persists, check the remote end for the LINK_ERR alarm. If the alarm exists, clear
it and check whether the LPT_RFI alarm is cleared.
Step 4 If the alarm persists, check whether the remote LPT service network is faulty.
l If fiber cut occurs, replace the fiber.
l If there are bit error threshold-crossing alarms, such as B3_EXC, clear them and check
whether the LPT_RFI alarm is cleared.

OptiX OSN 8800/6800/3800
l If there are alarms, such as VCAT_LOA, VCAT_LOM_VC3, VCAT_LOM_VC4, and

LP_UNEQ_VC3, clear them and check whether the LPT_RFI alarm is cleared.
----End
Related Information
None.
4.143 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating that the bias current of the laser crosses the
threshold. If the bias current of the laser crosses the threshold, the LSR_BCM_ALM alarm is
reported.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the port number.
In the case of packet processing boards and packet interface boards (except ATM
boards in the packet domain), no parameters are available.
For ATM boards in the packet domain, meanings of parameter values are as
follows:
l 0x01: The bias current exceeds the maximum value.
l 0x02: The bias current exceeds the minimum value.

OptiX OSN 8800/6800/3800

In the case of the LSR_BCM_ALM alarm, the laser works abnormally. A too high working
current may damage the laser, and a too low working current may not achieve the required gain.
In both cases, services are interrupted.
Possible Causes
The possible causes of the LSR_BCM_ALM alarm are as follows:
l The laser is aged.

l The laser is faulty.
Procedure
Step 1 View the LSR_BCM_ALM alarm on the NMS, and confirm the board where the
LSR_BCM_ALM alarm is reported.
Step 2 If the board supports a pluggable optical module, replace the pluggable optical module.
Otherwise, replace the faulty board, and then check whether the alarm is cleared.
----End
Related Information
None.
4.144 LSR_COOL_ALM
Description
Cooling current of the laser crossing the threshold. This alarm is generated when the cooling
current of the laser on the WDM side exceeds the threshold.
Attribute
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 properly.

OptiX OSN 8800/6800/3800
Possible Causes
The possible causes of the LSR_COOL_ALM alarm are as follows:
l The ambient temperature is excessively high.
Procedure
Step 1 Check whether the ambient temperature is excessively high. If it is, decrease the ambient
temperature to a proper value for the equipment to work well, and 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.
----End
Related Information
None
4.145 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
Parameters
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 port of the board cannot receive and transmit services. Services are interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
l The optical module has no license.
l 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
4.146 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the laser is not installed. This alarm is generated
when the optical port is enabled but not installed with the optical module.
Attribute
Parameters
Name Meaning
Parameter 1 The meanings of the parameter values are as follows:
l 0x01: indicates that the laser is not in position.

l 0x02: indicates that the EEPROM is empty.

When the optical port is not installed with the optical module, the data cannot be transmitted.

OptiX OSN 8800/6800/3800
Possible Causes
The possible causes of the LSR_NO_FITED alarm are as follows:
l The enabled optical port is not installed with the optical module.
l The optical module is faulty.
Procedure
Step 1 View the LSR_NO_FITED alarm on the U2000 to confirm the relevant board.
Step 2 After you replace the board, the LSR_NO_FITED alarm is automatically cleared.
----End
Related Information
None
4.147 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
Parameters
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.

OptiX OSN 8800/6800/3800

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.

l Cause 2: There is no input from the external clock source.
l Cause 3: The synchronization source is set as non-revertive or is locked.
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.
l 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.
l 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.
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.
the alarm is cleared. For details, see Performing Cold Reset on a Board in the
Supporting Tasks.

OptiX OSN 8800/6800/3800
l 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
4.148 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that a bit error threshold-crossing event is detected at the
MAC layer. The software periodically detects the number of bytes received by the MAC chip
and the number of bytes that have bit errors. This alarm is generated when the number of bit
errors crosses the threshold.
Attribute
Parameters
None.

Services degrade or even are interrupted.
Possible Causes
The possible causes of the MAC_FCS_EXC alarm are as follows:
l Cause 1: Line signals deteriorate.

l Cause 2: The transmit optical power at the opposite end is abnormal, which may be caused
by a faulty fiber connector.
l Cause 3: The receive optical power at the local end is abnormal, which may be caused by
a fiber connector.
Procedure
l Cause 1: Line signals deteriorate.

OptiX OSN 8800/6800/3800
1. On the NMS, check whether the DOS attack exists. If yes, eliminate the source that
transmits a large amount of invalid data, and then check whether the MAC_FCS_EXC
alarm is cleared.
2. If the alarm persists, check whether the cable or fiber is faulty. If yes, replace the faulty
cable or fiber, and check whether the MAC_FCS_EXC alarm is cleared.
l Cause 2: The transmit optical power at the opposite end is abnormal, which may be caused
by a faulty fiber connector.
1. On the NMS, check whether the transmit optical power at the opposite end is within
NOTE
the board.
If ... Then ...

The transmit optical power of is beyond the permitted Go to the next step.
range
The transmit optical power of is within the permitted range Go to Cause 3.
2. Check the jumper connectors and fiber connectors.
a. Check whether the fiber connector is properly connected. Ensure that the fiber
connector is installed securely. Check whether the alarm is cleared.
b. If the alarm persists, check whether the fiber connector is clean. If the fiber
connector is dirty, clean it. For details, see the Supporting Tasks. Check whether
3. If the alarm persists, check whether the attenuation value of the optical attenuator is
proper.
If ... Then ...
The attenuation value of the optical Adjust the value properly. Check
attenuator is improper whether the alarm is cleared. If the
The attenuation value of the optical Go to the next step.

attenuator is proper
4. Check whether the flange is correctly connected. Ensure that the flange is correctly
connected, and then check whether the alarm is cleared.
5. If the alarm persists, replace the optical module located at the transmit port of the
opposite NE. Then, check whether the alarm is cleared.
6. If the alarm persists, check whether the service processing board and cross-connect
board of the opposite NE report hardware-related alarms, such as HARD_BAD and
TEMP_OVER. If yes, replace the board that reports a hardware-related alarm. Then,
check whether the alarm is cleared. If the alarm persists, go to Cause 3.

OptiX OSN 8800/6800/3800
l Cause 3: The receive optical power at the local end is abnormal, which may be caused by
a fiber connector.
1. On the NMS, check whether the receive optical power at the local end is within the
permitted range. For details, see step 1 in Cause 2.
2. If the receive optical power is beyond the permitted range, see steps 2 to 6 in Cause
2 for troubleshooting at the local end.
----End
Related Information
None.
4.149 MAINBD_SUBBD_MISMATCH
Description
In one PID group, the service processing board must match the service outputting board;
otherwise, the MAINBD_SUBBD_MISMATCH alarm is generated.
Attribute
Parameters
None

In a PID group, if the service outputting board does not support the service processing board,
the wavelength services on the service outputting board will not be affected, but the service
processing board will be unavailable.
For example, in a PID group where the NPO2 board and ENQ2 board are used together, if the
NPO2 board does not support the ENQ2 board installed in the corresponding slot, the wavelength
services on the NPO2 board will not be affected, but the wavelength services on the ENQ2 board
will be unavailable.
Possible Causes
The service outputting board does not support the service processing board. However, the service
processing board is housed in the corresponding slot.
Procedure
Step 1 Determine whether the service processing board is required.

OptiX OSN 8800/6800/3800
Step 2 If the service processing board is required, replace the service outputting board with a board that
supports the service processing board.
Step 3 If the service processing board 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.
4.150 MCLAG_CFG_MISMATCH
Description
MC-LAG configuration mismatch alarm. This alarm is generated when the system detects that
the configurations at both ends of an MC-LAG are inconsistent.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the type of mismatched configurations. For example,

valid values can be as follows:
l 0x01: LAG ID mismatch

l 0x02: LAG type mismatch
l 0x04: MCLAG load sharing mode mismatch
l 0x08: MCLAG restoration mode mismatch

Negotiation of MC-LAG configuration fails and the services may be interrupted.
Possible Causes
The MC-LAG configurations at two ends are different.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Query the alarm on the U2000. Then, determine the boards that report the alarm and
corresponding alarm parameter.
Step 2 If the alarm parameter is 0x01, check whether the LAG IDs at both ends are consistent.
Step 3 If the alarm parameter is 0x02, check whether the MC-LAG types at both ends are consistent.
Step 4 If the alarm parameter is 0x04, check whether the MC-LAG load types at both ends are
consistent.
Step 5 If the alarm parameter is 0x08, check whether the LAG recover modes at both ends are consistent.
----End
Related Information
None
4.151 MCSP_PATH_LOCV
Description
Loss of connection of the protocol channel for multi-chassis synchronization protocol. This
alarm is generated when there is no expected Hello packet observed in any period of three
consecutive intervals.
Attribute
Parameters
Name Meaning
Parameter 1, Parameter 2 Indicates the protocol channel ID.

Services may be unavailable because protection switching may be triggered.

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The peer NE is malfunctioning.
l Cause 2: The physical link with the peer NE is interrupted.
l Cause 3: There is no path configuration on the peer NE.
Procedure
Step 1 Check whether the physical connection between the local NE and peer NE is valid. If yes, check
whether the physical fiber is damaged and replace the damaged fiber accordingly. If not, check
whether the physical connection is the same as the planned connection in the planning drawing.
Step 2 Check whether the protocol channel status of the peer NE is normal. If the protocol channel
status is abnormal, rectify the fault.
----End
Related Information
None
4.152 MOD_COM_FAIL
Description
Module communication exception. The alarm is generated when the communication between
the CPU and other internal modules of the board is abnormal.
Attribute
Parameters
None

Because the communication between the CPU and an 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.
l The software processing of the optical module on the board is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Check the connection between the board and optical module and re-connect the board and optical
module if they are not properly connected.
Step 2 Perform a cold reset on the faulty board on the U2000 or remove the faulty board and insert it
again.
Step 3 If the alarm persists, the board at the local station may be faulty. Replace the faulty board.
----End
Related Information
None
4.153 MODULE_ADJUST_FAIL
Description
Optical module adjustment failure.
Attribute
Parameters
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 on 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.

OptiX OSN 8800/6800/3800
l The optical module of the board is faulty.
Procedure
Step 1 Check whether the board temperature exceeds the threshold, and whether the TEM_HA or
TEMP_OVER alarm is generated. If it is, handle the alarm 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 a warm reset on the board.
Step 3 If the alarm persists, replace the faulty optical module or board.
----End
Related Information
None
4.154 MODULE_COOLCUR_OVER
Description
Module cooling current exceeding the threshold. The alarm is generated when the cooling current
of the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
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 reliability of the module are affected. In general, the QoS is not
affected; however, it will be affected if the alarm exists for a long time. Therefore, the alarm
needs to be handled in a timely manner.

OptiX OSN 8800/6800/3800
Possible Causes
l The temperature of the optical module is excessively high.
Procedure
Step 1 Check the ambient temperature of the board. If the ambient temperature is excessively high,
handle the alarm according to the handling procedure of the TEMP_OVER alarm.
----End
Related Information
None
4.155 MODULE_RATE_MISMATCH
Description
Signal rate mismatching an optical module. This alarm is generated when the optical module
does not support a mode, such as the speedup mode, specified by the user.
Attribute
Parameters
None

When this alarm occurs, services are unavailable or may be interrupted.
Possible Causes
l The module does not support the rate specified for the board.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Check whether the module supports the rate specified for the board. If it is not, change the rate
to the one that is supported by the module.
----End
Related Information
None
4.156 MODULE_TEMP_OVER
Description
Module temperature exceeding the threshold. This alarm is generated when the temperature of
the module is higher than the upper threshold or lower than the lower threshold.
Attribute
Parameters
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. Therefore,
this alarm must be handled in a timely manner.
Possible Causes
l The ambient temperature of the board is excessively high or excessively low.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Check the ambient temperature of the board. 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 on the U2000
----End
Related Information
None
4.157 MODULEFILE_UPDATE_FAIL
Description
Failure to update the microprogram and laser parameter table. This alarm is generated when the
in-service upgrade of the microprogram of the optical module and the parameter table on the
U2000 fails.
Attribute
Major Process alarm
Parameters
None

l The upgrade of the microprogram of the optical module fails. As a result, the new
microprogram of the optical module is unavailable and the old one is still used.
l The upgrade of the parameter table of the laser fails.
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.

OptiX OSN 8800/6800/3800
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.
----End
Related Information
None
4.158 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating defects of a PW. The MIP sends an AIS packet to
the downstream NE when it detects a fault on the tunnel that carries the PW. The sink MEP NE
reports this alarm upon receiving the AIS packet.
Attribute
Parameters
None.

When this alarm occurs, services may be interrupted.
Possible Causes
The possible cause of the MPLS_PW_AIS alarm is as follows:
Cause: The MIP NE detects a fault on a tunnel carrying the PW.

OptiX OSN 8800/6800/3800
Figure 4-4 MPLS_PW_AIS alarm detection

5. The MEP cannot receive
2. Configure MS- the OAM packet and
PW. reports the
3. Enable AIS MPLS_PW_LOCV alarm.
packet inserting. 6. The MEP reports the
1. The MEP
4. The MIP inserts MPLS_PW_AIS alarm
sends an OAM
the AIS packet after upon receiving the AIS
packet.
detecting a fault. packet.
OAM packet AIS packet
MEP MIP MEP
Procedure
Step 1 Cause: The MIP NE detects a fault on a tunnel carrying the PW.
1. Check whether MPLS Tunnel OAM is configured correctly on source and sink MEP NEs
and the MIP NE. If MPLS Tunnel OAM is configured incorrectly, modify the
configurations. Then, check whether the alarm is cleared.
2. If the alarm persists, check whether tunnel-related alarms are reported on MEP NEs. For
example, MPLS_TUNNEL_AIS. If any of these alarms exist, clear them immediately.
Then, check whether the MPLS_PW_AIS alarm is cleared.
----End
Related Information
None.
4.159 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV is an alarm indicating the loss of PW connectivity. This alarm is
generated when an Ethernet port fails to receive OAM detection packets for three consecutive
periods.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None.

When this alarm occurs, services are switched to the protection PW if PW APS is configured or
services are interrupted if PW APS is not configured.
Possible Causes
The possible causes of the MPLS_PW_LOCV alarm are as follows:
l Cause 1: PW labels are configured incorrectly.

l Cause 2: The network is severely congested.
l Cause 3: Board failure occurs.
l Cause 4: The PW physical link is connected incorrectly or is faulty.
Procedure
Step 1 Cause 1: PW labels are configured incorrectly.
1. Check the PW labels configured for all the NEs (including the source NE, transit NEs, and
sink NE), and ensure that ingress and egress labels on neighboring NEs are the same.
2. If the PW labels are configured incorrectly, change them to the same for neighboring NEs.
Check whether the alarm is cleared.
Step 2 Cause 2: The network is severely congested.

1. Based on the actual situation, increase the value of Detection Packet Period appropriately.
2. If the alarm persists, check whether the bandwidth allocated to the faulty PW is fully used.
If yes, or eliminate the source that transmits a large amount of invalid data. Then, check
Step 3 Cause 3: Board failure occurs.

1. On the NMS, check whether the COMMUN_FAIL alarm is reported on the opposite NE.
If yes, you can infer that the opposite NE is being reset. After the COMMUN_FAIL alarm
is cleared, check whether the MPLS_PW_LOCV alarm is cleared.
2. If the MPLS_PW_LOCV alarm persists, check whether the local NE and the opposite NE
report alarms that are related to the hardware of the optical modules or boards, such as
HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first. Then, check whether
the MPLS_PW_LOCV alarm is cleared.
Step 4 Cause 4: The PW physical link is connected incorrectly or is faulty.

1. Check whether the fiber or cable is connected incorrectly. For example, a fiber or cable is
incorrectly connected to a port on the next-hop NE due to manual operations. If the fiber

OptiX OSN 8800/6800/3800
or cable is incorrectly connected, rectify the fiber or cable connection. Check whether the
alarm is cleared.
2. If the alarm persists, check whether the fiber or cable is damaged or pressed. If the fiber or
cable is damaged or pressed, replace the faulty fiber or cable. Check whether the alarm is
cleared.
----End
Related Information
None.
4.160 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating that the OAM protocol negotiation fails. This
alarm is generated when the OAM protocol negotiation fails on NEs at both ends of a PW.
Attribute
Parameters
None.

When this alarm occurs, services carried by the faulty PW may be interrupted..
Possible Causes
In the auto-negotiation mode, the possible causes of the MPLS_PW_OAMFAIL alarm are as
follows:
Cause 1: The OAM function is only enabled on the NE at one end of the PW.

OptiX OSN 8800/6800/3800
Figure 4-5 MPLS_PW_OAMFAIL alarm detection (1)
MPLS PW OAM is MPLS PW OAM is

enabled on the local disabled on the remote
NE. NE.
The local NE reports the

MPLS_PW_OAMFAIL alarm. Service flow
NOTE
The alarm is reported only by the NE on which the OAM function is enabled. As shown in Figure 4-5,
only the local NE reports the MPLS_PW_OAMFAIL alarm.
Cause 2: The PW has been interrupted when enabling the OAM function.
Figure 4-6 MPLS_PW_OAMFAIL alarm detection (2)
Local: Remote:
MPLS PW OAM is enabled. MPLS PW OAM is enabled.
OAM Detection Mechanism is set OAM Detection Mechanism is set
to auto-sensing. to auto-sensing.
Forward PW
Reverse PW
The remote NE reports the

MPLS_PW_OAMFAIL alarm.
Service flow
NOTE
As shown in Figure 4-6, when the PW is interrupted in the forward direction or reverse direction, the peer
or local NE reports the MPLS_PW_OAMFAIL alarm.
Procedure
Step 1 Cause 1: The OAM function is only enabled on the NE at one end of the PW.

OptiX OSN 8800/6800/3800
1. On the NMS, query this alarm and check whether the OAM function is enabled on NEs at
both ends of the PW. If the OAM function is enabled only on one NE, set OAM Status to
Enabled for the other NE.
Step 2 Cause 2: The PW has been interrupted when enabling the OAM function.
1. On the NMS, check whether tunnel-related alarms are reported on the two ends of the PW.
For example, MPLS_TUNNEL_OAMFAIL. If any of these alarms exist, clear them
before you proceed.
----End
Related Information
None.
4.161 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating defects of a remote PW. The remote MEP sends an
RDI packet to the local MEP when it detects a PW fault. The local MEP reports this alarm after
receiving the RDI packet.
Attribute
Parameters
None.

When this alarm occurs, the services on the transmit side are affected.
Possible Causes
The possible cause of the MPLS_PW_RDI alarm is as follows:
A PW fault is detected on the remote MEP NE.

OptiX OSN 8800/6800/3800
Figure 4-7 MPLS_PW_RDI alarm detection
1. The remote MEP

sends an OAM packet.
OAM packet PSN
RDI packet
MEP MEP
3. The remote MEP reports the 2. The local MEP cannot
MPLS_PW_RDI alarm upon receive the OAM packet due
receiving the RDI packet. to a PW fault. It returns an
RDI packet to the local MEP.
Procedure
Step 1 A PW fault is detected on the remote MEP NE.
1. Check whether the faulty NE reports port-, optical module- or board-related alarms. For
example, ETH_LOS, ETH_LINK_DOWN, LSR_NO_FITED, and HARD_BAD. If
any preceding alarms are reported, clear them.
2. Check whether service-related alarms are reported by the faulty NE. For example,
MPLS_PW_LOCV. If any of these alarms exist, clear them immediately. Then, check
whether the MPLS_PW_RDI alarm is cleared.
3. If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical
fiber or cable.
----End
Related Information
None.
4.162 MPLS_PW_SD
Description
The MPLS_PW_SD alarm indicates that signals on a PW degrade. This alarm is generated when
the loss ratio of continuity check (CC) packets is higher than the SD threshold but is lower than
the SF threshold.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

The quality of service degrades and a small number of packets are lost.
Possible Causes
The possible causes of the MPLS_PW_SD alarm are as follows:
l Cause 1: An excessive number of bit errors occur.

l Cause 2: The bandwidth of the PW is fully occupied.
Procedure
Step 1 Cause 1: An excessive number of bit errors occur.
1. Query the performance statistics of Ethernet ports to check whether bit errors or FCS errored
frames are generated.
2. Check whether the physical link is connected correctly. If any optical cables are broken,
replace the faulty optical fibers. If any optical ports are dirty or damaged, clean the optical
ports. If the bend radius of the fiber patch cord is less than 6 cm, reroute the fiber patch
cord. Clear bit errors on the transmission line first. Then, check whether the alarm is cleared.
Step 2 Cause 2: The bandwidth of the PW is fully occupied.

1. Check the bandwidth utilization of the PW. If the PW bandwidth is fully occupied, or
eliminate the source that transmits a large amount of invalid data. Check whether the alarm
is cleared.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.163 MPLS_PW_SF
Description
The MPLS_PW_SF is an alarm indicating that signals on a PW degrades severely. This alarm
is generated when the loss ratio of CC packets crosses the SF threshold.
Attribute
Parameters
None.

The quality of service degrades severely and a large number of packets are lost.
Possible Causes
The possible causes of the MPLS_PW_SF alarm are as follows:

l Cause 2: The bandwidth of the PW is fully occupied.
Procedure
1. Query the performance statistics of Ethernet ports to check whether bit errors or FCS errored
frames are generated.
2. Check whether the physical link is connected correctly. If any optical cables are broken,
replace the faulty optical fibers. If any optical ports are dirty or damaged, clean the optical
ports. If the bend radius of the fiber patch cord is less than 6 cm, reroute the fiber patch
cord. Clear bit errors on the transmission line first. Then, check whether the alarm is cleared.
Step 2 Cause 2: The bandwidth of the PW is fully occupied.

1. Check the bandwidth utilization of the PW. If the PW bandwidth is fully occupied, or
eliminate the source that transmits a large amount of invalid data. Check whether the alarm
is cleared.
----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.164 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG alarm indicates that an MEG is unexpected on the PW. This
alarm is reported when the MEP receives CCM frames with the correct MEG level, correct MEG
ID, but unexpected MEG ID.
Attribute
Parameters
None.

When this alarm is generated, packets on other PWs are received over this PW.
Possible Causes
The possible causes of the MPLS_PW_UNEXPMEG alarm are as follows:
l Cause 1: The PW is configured incorrectly. Different PWs use the same labels.
As shown in Figure 4-8, NE1 is the source NE, and NE2 is the sink NE. The PW incoming
label for NE2 is 1, indicating that it is supposed to receive packets from PW1 only.
On the live network, NE1 configures a PW outgoing label whose value is 1 to both PW1
and PW2. Therefore, after receiving CCM packets from PW2, NE2 detects different MEG
IDs and reports the MPLS_PW_UNEXPMEG alarm.

OptiX OSN 8800/6800/3800
Figure 4-8 MPLS_PW_UNEXPMEG alarm detection (1)
PW1PW outlabel = 1
PW inlabel = 1
PW2PW outlabel = 1
PW1
NE1 NE2
PW2
NE2 reports the

MPLS_PW_UNEXPMEG alarm.
Service flow
l Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
As shown in Figure 4-9, on the link from NE1 to NE2, the MEG ID is 1.
In practice, the MEG ID for NE1 is 1 and MEG ID for NE2 is 2. Then, NE2 receives CCM
packets containing different MEG ID and reports the MPLS_PW_UNEXPMEG alarm.
MEG ID = 1 MEG ID = 2
NE1 NE2
NE2 reports the

Service flow
l Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label are
connected to the same sink NE.
As shown in Figure 4-10, a fiber between NE1 and NE2 is correctly connected. On the
link from NE1 to NE2, the PW outgoing label is 1, and the MEG ID is 1. On the link from
NE3 to NE4, the PW outgoing label is 1, and the MEG ID is 2.

OptiX OSN 8800/6800/3800
In practice, if a fiber is incorrectly connected from NE3 to NE2, the outgoing label of NE1
is the same as that on NE3, and the incoming label on NE2 is the same as that on NE4. As
a result, NE2 reports the MPLS_PW_UNEXPMEG alarm.
PW outlabel = 1 PW inlabel = 1
NE1 NE2
NE2 reports the

NE3 NE4
PW outlabel = 1 PW outlabel = 1
Service flow
Procedure
Step 1 Cause 1: The PW is configured incorrectly. Different PWs use the same labels.
1. As shown in Figure 4-8, check whether the PW label is configured correctly. If multiple
PWs use the same labels, reconfigure the PW label.
Step 2 Cause 2: MEG IDs configured on NEs at both ends of the PW are different.
1. As shown in Figure 4-9, check whether the PW configurations on NEs at both ends of the
PW are consistent. PW IDs on NEs at both ends of a PW must be set to the same value.
Step 3 Cause 3: The physical link is connected incorrectly. Multiple PWs with the same label are
1. As shown in Figure 4-10, check whether the fiber or cable is correctly connected between
ports at both ends. If the fiber or cable is connected incorrectly, connect it correctly.

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.165 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP alarm indicates that an MEP is unexpected on a PW. This alarm
is reported when the MEP receives CCM frames with the correct MEG level, correct MEG ID,
but unexpected MEP ID.
Attribute
Parameters
None.

When this alarm is generated, the services may be interrupted or packets on other PWs are
received over this PW.
Possible Causes
The possible cause of the MPLS_PW_UNEXPMEP alarm is as follows:
l Cause 1: MEP IDs are inconsistent on NEs at both ends of a PW.

As shown in Figure 4-11, NE2 is the sink end for NE1 and the MEP ID is 1 for both NEs
in the network plan.
However, the MEP ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore,
NE2 reports the MPLS_PW_UNEXPMEP alarm upon receiving the CCM packet that
contains incorrect MEP ID from NE1.

OptiX OSN 8800/6800/3800
Figure 4-11 MPLS_PW_UNEXPMEP alarm detection

MEP ID = 1 MEP ID = 2
PW
NE1 PSN NE2
NE2 reports the MPLS_PW_UNEXPMEP alarm.
Service flow
l Cause 2: The physical link has an incorrect connection.
Procedure
Step 1 Cause 1: MEP IDs are inconsistent on NEs at both ends of a PW.
1. As shown in Figure 4-11, check whether PW configurations are consistent on the source
and sink NEs. MEP IDs must be set to the same value for NEs at both ends of a PW service.
2. On the NMS, check whether tunnel-related alarms are reported by NEs at both ends of the
PW. For example, MPLS_TUNNEL_OAMFAIL. If any of these alarms are reported,
clear them before you proceed.
3. Check whether service-related alarms are reported by NEs at both ends of the PW. For
example, MPLS_TUNNEL_LOCV. If any of these alarms are reported, clear them before
you proceed.
Step 2 Cause 2: The physical link has an incorrect connection.

1. Ensure that the related fiber or cable is correctly connected.
2. If the fiber or cable connection is incorrect, rectify the connection.
----End
Related Information
None.
4.166 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER alarm indicates that the PW period is unexpected. This alarm is
reported when the MEP receives packets with the correct MEG level, MEG ID, and MEP ID,
but the period carried in the packets is different from the period for the MEP to transmit packets.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

When this alarm occurs, services may be interrupted.
Possible Causes
The possible cause of the MPLS_PW_UNEXPPER alarm is as follows:
l Cause 1: The PW source or sink node is configured with an incorrect period.

Procedure
Step 1 Cause 1: The PW source or sink node is configured with an incorrect period.
1. Ensure that the correct periods are configured at the PW source and sink nodes, according
to the NE planning table.
2. If period configurations are incorrect, rectify them.

----End
Related Information
None.
4.167 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating defects of a tunnel. The MIP NE sends an AIS
packet to the downstream NE when it detects a fault on the upstream port. The MEP NE reports
the MPLS_TUNNEL_AIS alarm upon receiving the AIS packet.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

Possible Causes
The possible cause of the MPLS_TUNNEL_AIS alarm is as follows:
The MIP node detects a fault on the Tunnel physical layer.
Figure 4-12 MPLS_TUNNEL_AIS alarm detection

3. The local MEP fails to receive the OAM
detection packet and reports the
Precondition: The AIS MPLS_TUNNEL_LOCV alarm.
insertion function is enabled. 4. Upon receiving the AIS packet, the local
2. The MIP detects a fault MEP reports the MPLS_TUNNEL_AIS
1. The remote MEP sends an and inserts an AIS packet alarm and suppresses the
OAM detection packet. to the downstream. MPLS_TUNNEL_LOCV alarm.
Tunnel Tunnel
MEP MIP MEP
OAM detection packet

AIS packet
Procedure
Step 1 The MIP node detects a fault on the Tunnel physical layer.
any of these alarms are reported, clear them immediately. Then, check whether the
MPLS_TUNNEL_RDI alarm is cleared.
fiber or cable.

OptiX OSN 8800/6800/3800
engineers for a solution.
----End
Related Information
None.
4.168 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV alarm indicates the loss of tunnel connectivity. This alarm is
generated when an Ethernet port fails to receive expected OAM detection packets for three
consecutive periods.
Attribute
Parameters
None.

When this alarm occurs, services are switched to the protection tunnel if Tunnel APS is
configured or services are interrupted if Tunnel APS is not configured.
Possible Causes
The possible causes of the MPLS_TUNNEL_LOCV alarm are as follows:
l Cause 1: Tunnel labels are configured incorrectly.

l Cause 2: The network is severely congested.
l Cause 3: Board failure occurs.
l Cause 5: ARP entries fail to be learned.
NOTE
This problem may occur on either ingress or transit node.
Procedure
Step 1 Cause 1: Tunnel labels are configured incorrectly.

OptiX OSN 8800/6800/3800
1. Check the tunnel labels configured for all the nodes (including the ingress node, transit
nodes, and egress node) on the label switched path (LSP) in sequence, and ensure that
ingress and egress labels on neighboring nodes are the same.
2. If the tunnel labels are configured incorrectly, change them to the same settings for
neighboring nodes. Then, check whether the alarm is cleared.
Step 2 Cause 2: The network is severely congested.

1. Based on the actual situation, increase the value of Detection Packet Period appropriately.
Check whether the alarm is cleared.
2. If the alarm persists, check whether the bandwidth allocated to the faulty tunnel is fully
used. If yes, or eliminate the source that transmits a large amount of invalid data. Check
Step 3 Cause 3: Board failure occurs.

1. On the NMS, check whether the COMMUN_FAIL alarm is reported on the opposite NE.
If yes, you can infer that the opposite NE is being reset. After the COMMUN_FAIL alarm
is cleared, check whether the MPLS_TUNNEL_LOCV alarm is cleared.
2. On the NMS, check whether the local NE and the opposite NE report alarms that are related
to the hardware of the optical modules or boards, such as HARD_BAD and
LSR_NO_FITED. If yes, clear these alarms first. Then, check whether the
MPLS_TUNNEL_LOCV alarm is cleared.

1. Check whether the fiber or cable is connected incorrectly. For example, a fiber or cable is
incorrectly connected to a port on the next-hop NE due to manual operations. If the fiber
or cable is incorrectly connected, rectify the fiber or cable connection. Then, check whether
2. If the alarm persists, check whether the fiber or cable is damaged or pressed. If the fiber or
cable is damaged or pressed, replace the faulty fiber or cable. Then, check whether the
alarm is cleared.
Step 5 Cause 5: ARP entries fail to be learned.

1. Check the ARP entries on the explicit nodes (including the ingress node, transit nodes, and
egress node) in sequence according to the NE planning table, and ensure that the mapping
between IP addresses and MAC addresses is correct on neighboring nodes.
2. If the mapping between IP addresses and MAC addresses on the next-hop NE is not
displayed, ARP entries fail to be learned. Rectify the fault on the MPLS tunnel immediately.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.169 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL is an alarm indicating a failure to negotiate the OAM
protocol. This alarm is generated by a Tunnel OAM enabled NE when the OAM protocol
negotiation fails on NEs at both ends of a tunnel.
Attribute
Parameters
None.

When this alarm occurs, services carried by the faulty tunnel may be interrupted.
Possible Causes
In the auto-negotiation mode, the possible causes of the MPLS_TUNNEL_OAMFAIL alarm
are as follows:
Cause 1: The OAM function is enabled only on the NE at one end of the tunnel. The OAM
enabled end reports the MPLS_TUNNEL_OAMFAIL alarm.
Figure 4-13 MPLS_TUNNEL_OAMFAIL alarm detection (1)
Local end: Remote end:

MPLS Tunnel OAM is enabled. MPLS Tunnel OAM is disabled.
Forward
tunnel
PSN
Backward
tunnel
MPLS_TUNNEL_OAMFAIL is reported.
Service flow

OptiX OSN 8800/6800/3800
NOTE
Only the NE where the OAM function is enabled will report the MPLS_TUNNEL_OAMFAIL alarm. As
shown in Figure 4-13, only the local NE reports the MPLS_TUNNEL_OAMFAIL alarm.
Cause 2: The tunnel has been interrupted when the OAM function is enabled.
Figure 4-14 MPLS_TUNNEL_OAMFAIL alarm detection (2)
A section of the forward tunnel is

interrupted.
Local end Remote end

Forward
tunnel
PSN
Backward
tunnel
MPLS_TUNNEL_OAMFAIL is reported
Service flow
NOTE
As shown in Figure 4-14, the MPLS_TUNNEL_OAMFAIL alarm is reported by the remote NE when the
forward tunnel is interrupted and by the local NE when the reverse tunnel is interrupted.
Procedure
Step 1 Cause 1: The OAM function is enabled only on the NE at one end of the tunnel. The OAM
enabled end reports the MPLS_TUNNEL_OAMFAIL alarm.
1. Query this alarm On the NMS and check whether the OAM function is enabled on NEs at
both ends of the tunnel. If the OAM function is enabled only on one NE, set OAM
Status to Enabled for the other NE.
Step 2 Cause 2: The tunnel has been interrupted when the OAM function is enabled.
1. On the NMS, check whether there are port-, optical module- and board-related alarms on
NEs which the tunnel traverses. For example, ETH_LOS, ETH_LINK_DOWN,
LSR_NO_FITED, and HARD_BAD. If any of these alarms exist, clear them before you
proceed.
2. Check whether there are service-related alarms on NEs which the tunnel traverses. For
example, MPLS_TUNNEL_LOCV. If any of these alarms exist, clear them before you
proceed.
3. Check whether physical links of this tunnel are faulty. For example, the optical fiber or
cable is damaged or pressed. If yes, replace the faulty optical fiber or cable.

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.170 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating remote defects of a tunnel. The remote MEP
NE sends an RDI packet to the local MEP NE when it detects defects of a tunnel. The local MEP
NE reports this alarm upon receiving the RDI packet.
Attribute
Parameters
None.

When this alarm occurs, the services on the transmit side are affected.
Possible Causes
The possible cause of the MPLS_TUNNEL_RDI alarm is as follows:
The remote MEP NE detects that the tunnel is faulty.
Figure 4-15 MPLS_TUNNEL_RDI alarm detection

1. The remote MEP sends
an OAM detection packet.
PSN
Forward tunnel
Backward Tunnel
3. Upon receiving the RDI packet, 2. Due to a tunnel fault, the local MEP fails to receive
the remote MEP reports the the OAM detection packet. As a result, the local MEP
MPLS_TUNNEL_RDI alarm. reports the MPLS_TUNNEL_LOCV alarm and returns
an RDI packet.
OAM detection packet

RDI packet

OptiX OSN 8800/6800/3800
Procedure
Step 1 The remote MEP NE detects that the tunnel is faulty.
any of these alarms are reported, clear them immediately. Then, check whether the
MPLS_TUNNEL_RDI alarm is cleared.
2. Check whether the faulty NE reports service-related alarms, such as
MPLS_TUNNEL_LOCV. If any of these alarms are reported, clear them immediately.
Then, check whether the MPLS_TUNNEL_RDI alarm is cleared.
fiber or cable.
engineers for a solution.
----End
Related Information
None.
4.171 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD alarm indicates that signals on a tunnel degrade. This alarm is
generated when the packet loss ratio of continuity (CC) is higher than the SD threshold but is
lower than the SF threshold.
Attribute
Parameters
None.

The quality of service degrades and a small number of packets are lost.
Possible Causes
The possible causes of the MPLS_TUNNEL_SD alarm are as follows:

OptiX OSN 8800/6800/3800

l Cause 2: The bandwidth of the tunnel is fully used.
l Cause 3: Another service carrier layer is faulty.
Procedure
1. On the NMS, check whether the MAC_FCS_EXC alarm is reported. If yes, clear the
MAC_FCS_EXC alarm first and check whether the alarm is cleared.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.

1. On the NMS, check whether the allocated bandwidth is fully used. If yes, eliminate the
source that transmits a large amount of invalid data. Check whether the alarm is cleared.
Step 3 Cause 3: Another service carrier layer is faulty.

1. On the NMS, check whether another service carrier layer, such as the Ethernet layer, is
faulty. If yes, rectify the fault regarding the running of the MPLS OAM protocol or
regarding setting consistency.
----End
Related Information
None.
4.172 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF alarm indicates that signals on a tunnel degrade severely. During the
continuity check (CC), this alarm is reported if the packet loss ratio crosses the SF threshold but
CC packets are received in three consecutive periods.
Attribute
Parameters
None.

OptiX OSN 8800/6800/3800

The quality of service degrades severely and a large number of packets are lost.
Possible Causes
The possible cause of the MPLS_TUNNEL_SF alarm is as follows:

l Cause 2: The bandwidth of the tunnel is fully used.
l Cause 3: Another service carrier layer is faulty.
Procedure
1. On the NMS, check whether the MAC_FCS_EXC alarm is reported. If yes, clear the
MAC_FCS_EXC alarm first and check whether the alarm is cleared.
Step 2 Cause 2: The bandwidth of the tunnel is fully used.

1. On the NMS, check whether the allocated bandwidth is fully used. If yes, eliminate the
source that transmits a large amount of invalid data. Check whether the alarm is cleared.
Step 3 Cause 3: Another service carrier layer is faulty.

1. On the NMS, check whether another service carrier layer, such as the Ethernet layer, is
faulty. If yes, rectify the fault regarding the running of the MPLS OAM protocol or
regarding setting consistency.
----End
Related Information
None.
4.173 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG alarm indicates that an MEG is unexpected on a tunnel.
This alarm indicates that the MEP receives packets with the correct MEG level but incorrect
MEG ID.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

When this alarm is generated, packets on other tunnels are received over this tunnel.
Possible Causes
The possible causes of the MPLS_TUNNEL_UNEXPMEG alarm are as follows:
l Cause 1: There are multiple tunnels with the same MEG ID between the source and sink
NEs.
An example is provided as follows: As shown in Figure 4-16, there are two links in the
network plan that are connected to NE2: tunnel 1 between NE1 and NE2, and tunnel 2
between NE3 and NE2. The MEG ID of tunnel 1 is 1 and tunnel 2 is 2.
However, in actual configuration, outgoing MEG IDs of both tunnel 1 and tunnel 2 are set
to 1. NE2 receives an OAM packet (containing CCM information) that contains incorrect
MEG ID from NE3. As a result, NE2 reports the MPLS_TUNNEL_UNEXPMEG alarm.
Figure 4-16 MPLS_TUNNEL_UNEXPMEG alarm detection (1)

Tunnel
NE1 NE2
el
PSN T unn
NE2 reports the

NE3 MPLS_TUNNEL_UNEXPMEG alarm.
MEG ID = 1 Service flow
l Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.

An example is provided as follows: As shown in Figure 4-17, NE2 is the source end for
NE1 and the MEG ID on both NEs is 1 in the network plan.

OptiX OSN 8800/6800/3800
However, the MEG ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore,
NE2 reports the MPLS_PW_UNEXPMEP alarm upon receiving the OAM packet
(containing CCM information) with an incorrect MEG ID from NE1.

Tunnel outlabel = 1 Tunnel inlabel = 1
Tunnel
NE1 PSN NE2
NE2 reports the MPLS_TUNNEL_UNEXPMEG

alarm.
Service flow
l Cause 3: Physical links are connected improperly. Multiple tunnels with the same MEG
ID are connected to the same sink NE.
As shown in Figure 4-18, a fiber between NE1 and NE2 is connected correctly. The tunnel
between NE1 and NE2 has an outgoing label (label 1) and the MEG ID is 1. The tunnel
between NE3 and NE4 has an outgoing label (label 1) and the MEG ID is 2.
In practice, if NE2 is mistakenly connected to NE3, the outgoing label of a tunnel on NE1
is the same as that of the tunnel from NE3 to NE4, and the incoming label of a tunnel on
NE2 is the same as the outgoing label of a tunnel from NE3 to NE4. As a result, NE2 reports
the MPLS_TUNNEL_UNEXPMEG alarm.

Tunnel
NE1 NE2
el
Tunn
PSN NE2 reports the

MPLS_TUNNEL_UNEXPMEG alarm.
Tunnel
NE3 NE4

Service flow

OptiX OSN 8800/6800/3800
Procedure
Step 1 Cause 1: There are multiple tunnels with the same MEG ID between the source and sink NEs.
1. As shown in Figure 4-16, check whether there are multiple tunnels with the same outgoing
label on the source and sink NEs. If yes, reconfigure labels for tunnels.
Step 2 Cause 2: MEG IDs are inconsistent on NEs at both ends of a tunnel.
1. As shown in Figure 4-17, check whether tunnel configurations are consistent on the source
and sink NEs. MEG IDs must be set to the same value on NEs at both ends of a tunnel
service.
Step 3 Cause 3: Physical links are connected improperly. Multiple tunnels with the same MEG ID are
1. As shown in Figure 4-18, check whether the fiber or cable correctly connects ports on both
source and sink NEs. If the fiber or cable connection is incorrect, connect it correctly.
----End
Related Information
None.
4.174 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP alarm indicates that an MEP is unexpected on a tunnel.
This alarm is reported when the MEP receives CCM frames with the correct MEG level, correct
MEG ID, but unexpected MEP ID.
Attribute
Parameters
None.

When this alarm is generated, the services may be interrupted or packets on other tunnels are
received over this tunnel.

OptiX OSN 8800/6800/3800
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPMEP alarm is as follows:
l Cause 1: MEP IDs are inconsistent on NEs at both ends of the tunnel.
As shown in Figure 4-19, NE2 is the source end for NE1 and the MEP ID on both NEs is
1.
However, the MEP ID of NE1 is set to 1 while that of NE2 is set to 2 in fact. Therefore,
NE2 reports the MPLS_TUNNEL_UNEXPMEP alarm upon receiving the OAM packet
(containing CCM information) with an unexpected MEP ID from NE1.
Figure 4-19 MPLS_TUNNEL_UNEXPMEP alarm detection
MEP ID = 1 MEP ID = 2
Tunnel
NE1 PSN NE2
NE2 reports the MPLS_TUNNEL_UNEXPMEP

alarm.
Service flow
Procedure
Step 1 Cause 1: MEP IDs are inconsistent on NEs at both ends of the tunnel.
1. As shown in Figure 4-19, check whether MEP IDs are consistent on the source and sink
NEs of the tunnel.
NOTE
The MEP IDs must be consistent on the source and sink NEs of a tunnel.
2. If MEP IDs are inconsistent, change them to the same.

----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.175 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER alarm indicates that the tunnel period is unexpected. This
alarm is reported when the MEP receives packets with the correct MEG level, MEG ID, and
MEP ID, but the period carried in the packets is different from the period for the MEP to transmit
packets.
Attribute
Parameters
None.

When this alarm is generated, the services may be interrupted or packets on other tunnels are
received over this tunnel.
Possible Causes
The possible cause of the MPLS_TUNNEL_UNEXPPER alarm is as follows:
l Cause 1: The tunnel configurations are incorrect and the periods configured at the source
and sink NEs are different.
Procedure
Step 1 Cause 1: The tunnel configurations are incorrect and the periods configured at the source and
sink NEs are different.
1. On the NMS, check the tunnel configurations and check whether the tunnel configurations
at the source and sink NEs are consistent.
2. If they are inconsistent, modify the tunnel configurations.

----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.176 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
Parameters
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 port where the protection
switching occurs.

OptiX OSN 8800/6800/3800

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.

l 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 port 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.177 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.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
None

The line has bit errors, which decreases the QoS.
Possible Causes
l The performance of the laser on the board at the opposite station deteriorates.
l The input optical power of the board at the local station is excessively high or excessively
low.
l The performance of the clock at the opposite station deteriorates.
l The fiber performance deteriorates.
Procedure
Step 1 Check whether the fiber is aging or has excessive attenuation. If it is, 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 it is, clear the alarms.
range by using the U2000. For the optical power specifications of the specific board, see the
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.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
be within the permitted range.
Step 4 If the alarm persists, remove the fault of the board in the opposite station.
----End
Related Information
A performance monitoring period can be 15 minutes or 24 hours. A performance threshold
crossing alarm check whether the requirement of alarm clearance is met only after a new
monitoring period starts. If the alarm persists after you perform the provided procedure, query
whether the service has been restored to normal by checking the accumulated performance
values. Or wait after a new monitoring period starts and then check whether the alarm is cleared.

OptiX OSN 8800/6800/3800
4.178 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
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.
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.179 MS_SNCP_PS
Description
The MS_SNCP_PS is an alarm indicating the MS SNCP protection switching. This alarm is
generated when the MS SNCP protection group actuates switching in which the current channel
switches to the protection channel from the working channel.

OptiX OSN 8800/6800/3800
Attribute
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 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 MS SNCP protection group
switch to the protection channel from the working channel. Hence, the alarm is reported.
l Cause 2: The services of the working channel of the MS SNCP protection group are faulty.
The current channel automatically switches to the working channel and the alarm is
reported.
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,
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, after WTR Times the current channel automatically switches to the working channel
and the alarm clears. If the attribute is Non-Revertive, set it to Revertive, and after WTR
Times the alarm clears.
----End

OptiX OSN 8800/6800/3800
Related Information
For OptiX OSN 6800 and OptiX OSN 3800, see "MS SNCP Protection" in the Feature
Description.
4.180 MS_SNCP_STA_INDI
Description
The MS_SNCP_STA_INDI is an alarm indicating the MS SNCP protection switching. This
alarm is generated when the working or protection channel of the protection group is faulty or
the user runs an external switching command.
Reporting side: NA
Attribute
Parameters
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 is performed in the MS SNCP group, the services may be transiently
interrupted.
l When the alarm is reported, the working or protection channel of the MS SNCP group may
have faulty services that need to be restored.

OptiX OSN 8800/6800/3800
Possible Causes
l The user issues an external switching command such as forced switching, manual
l The services of the working or protection channel of the MS SNCP group are faulty.
l 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 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 are reported on the related boards for
configuring the protection group. If they are, handle the alarms according to the
corresponding handling procedure of the alarms to restore the services of the working or
protection channel.
2. If the alarm persists, check whether the attribute of the protection group is Revertive. If it
is, after WTR Times 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 after WTR Times 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 WTR Times, the alarm is cleared.
----End
Related Information
For OptiX OSN 6800 and OptiX OSN 3800, see "MS SNCP Protection" in the Feature
Description.
4.181 MUT_TLOS
Description
Loss of output multiplexed signals. This alarm is generated when the output multiplexed signals
of the board are lost.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Parameter 1 Indicates the optical port where the alarm is generated. For example,
0x01 indicates optical port 1.
Parameters 2 and 3 Consists of two bytes, and indicates the channel where the alarm is
generated. For example, 0x00 0x01 indicates channel 1 of the optical port
indicated by Parameter 1.

All services traversing the board are interrupted.
Possible Causes
l The optical power of the output port is excessively low. Maybe the input optical power of
the add wavelength is excessively low.
l The attenuation of signals in line transmission is overlarge.
Procedure
Step 1 Verify that the fiber connections are correct according to the engineering fiber connection
diagram so that the input optical signals in different wavelengths are transmitted to
corresponding input optical ports of the board. If the fiber connections are incorrect, correct
them according to the diagram.
Step 2 If the alarm persists, measure the actual receive optical power of the board at the local station
by using an optical power meter. Check whether the receive optical power or transmit optical
power is within the permitted range.
Step 3 If the receive optical power or transmit optical power of the board at the local station is
excessively low, check whether the MUT_LOS alarm is generated at the local station.
l If yes, see the handling procedure of the MUT_LOS alarm for troubleshooting.
l If no, make sure that the input power of the added wavelength is normal.

OptiX OSN 8800/6800/3800
----End
Related Information
None
4.182 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that there is more than one RPL OWNER
node on the ring.
Attribute
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

OptiX OSN 8800/6800/3800
4.183 NEBD_XC_DIF
Description
Cross-connect matrix data of the NE and board being different. This alarm is generated when
the cross-connection data stored on the system control board is not consistent with that stored
on a board supporting service cross-connections. It is also generated when multiple subracks are
configured in master-slave mode and SDH boards are present in the slave subracks.
Attribute

Parameters
Parameters 1 Indicates the ID of the subrack where the board is located.
Parameters 2 Indicates the slot ID of the board.
Parameter 3 Indicates the cross-connect type.
l 0x01 indicates an inconsistency of high-order cross-connect matrix data.

l 0x02 indicates an inconsistency of low-order cross-connect matrix data.
l 0x03 indicates presence of SDH boards in the slave subracks when subracks
are configured in master-slave mode.

When the value of alarm parameter 3 is not 0x03, services are interrupted during service
grooming or a warm reset on the board; when the value of alarm parameter 3 is 0x03, the system
functions may be abnormal, for example, service grooming may fail or protection switching may
time out.
Possible Causes
l Cause 1: The cross-connection data of the board is incorrect.

OptiX OSN 8800/6800/3800
l Cause 2: The cross-connection data stored on the board is different from that on the system
control board.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the slave subracks.
Procedure
l Query the alarm on the U2000. Record the slot ID of the board that reports the alarm.
l Cause 1: The cross-connection data of the board is incorrect.
1. Re-configure the cross-connection data on the U2000.
l Cause 2: The cross-connection data stored on the board is different from that on the system
control board.
1. If the alarm persists, perform a warm reset on the board related to service cross-
connections on the U2000.
2. If the alarm persists, perform a warm reset on the system control board on the
U2000.
l Cause 3: Multiple subracks are configured in master-slave mode and SDH boards are
present in the slave subracks.
1. Modify the board configurations in the slave subracks to ensure that no SDH board is
present when multiple subracks are configured in master-slave mode.
----End
Related Information
Related Cases:
l MC-A119 The NEBD_XC_DIF Alarm Occurs Because of Cross-Connections and Outloop
Configured on the Client Side of the LQG
4.184 NESF_LOST
Description
Absence of NE software. The alarm is generated when the NE software information is not found
on the system control board.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

If neither of the two sets of NE software exists, the board cannot work properly and the
U2000 cannot monitor the NE after the reset or power-off restart of the system control board.
Possible Causes
The NE software is not reloaded after the NE software of the system control board is erased.
Procedure
Step 1 Reload the NE software of the system control board.
----End
Related Information
None
4.185 NESTATE_INSTALL
Description
NE being in installing state and no data configured. This alarm is generated when the NE is in
the initial installation state.
Attribute
Parameters
None

l The U2000 cannot query all configuration information about the NE.
l If the alarm is generated on the NE that is in the normal running state, the data of the
U2000 is initialized and correct configuration needs to be delivered in a timely manner.
Possible Causes
l The NE is in the initial installation state.
l The normal configuration is not delivered to the NE after the NE is initialized.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Deliver the configuration information to the board by using the U2000.
----End
Related Information
None
4.186 NO_BD_PARA
Description
Absence of the board parameter table file. This alarm is generated when the board does not have
the parameter table file.
Attribute
Parameters
None

The parameter table file of the board is lost, which may influence the services of users.
Possible Causes
l The correct parameter table file is not loaded before delivery.
l The incorrect parameter table file is loaded on site, which overlaps the original file.
l The parameter table file is abnormally lost in the running process.
Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.187 NO_BD_SOFT
Description
Absence of board software. This alarm is generated when the board does not have necessary
software, such as the loading software and logic software.
Attribute
Parameters
Parameter 1 Indicates the fault type. For example, 0x01 indicates that the file is lost
and 0x02 indicates that the file verification fails.
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 to 0x00 0x1f indicates that the parameter table 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.
l If the board that reports the alarm is reset, the board may fail to start.

OptiX OSN 8800/6800/3800
Possible Causes
l Parts of the software are not loaded to the board.
l The software on the board is abnormally lost in the running process.
l The internal detection of the board is abnormal.
Procedure
Step 1 Reload the corresponding software on the U2000.
----End
Related Information
None
4.188 NO_ELABEL
Description
Electronic label unloaded. This alarm is generated when the electronic label of a board is lost
or not loaded.
Attribute
Parameters
Parameter 1 Indicates the carrier type of the electronic label. This parameter has a fixed
value of 0x01.
Parameters 2 and 3 l 0x00 0xfe: indicates that the electronic label of the backplane is lost.
l 0x00 0x01: indicates that the electronic label of the board where the
alarm is generated is lost.

OptiX OSN 8800/6800/3800

None
Possible Causes
The electronic label is unloaded or lost.
Procedure
Step 1 Check the value of alarm parameters 2 and 3.
1. If the electronic label of the board where the alarm is generated is lost, replace the board.
NOTE
During board replacement, check whether there are bent pins on the backplane. If there are bent pins
on the backplane, handle the bent pins in a timely manner.
2. If the electronic label of the backplane is lost, check whether there are bent pins on the
backplane. If there are bent pins on the backplane, handle the bent pins in a timely manner.
If the problem persists after handling, replace the subrack.
Step 2 If the alarm persists after the preceding operations, contact Huawei engineers to handle the
problem.
----End
Related Information
None
4.189 NODEID_MM
Description
Mismatch of MSP node IDs. This alarm is generated when the configured ID of an MSP node
on the MS ring mismatches the actual node ID.
Attribute

Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameters 1 and 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 to determine the MSP group ID.
Step 2 Check whether the configuration of the MSP data meets the following requirements. If it is not,
re-configure 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. The alarm clears automatically.
----End
Related Information
None
4.190 NTP_SYNC_FAIL
Description
NTP synchronization failure. This alarm indicates that the NE is in the unsynchronous state. The
alarm is cleared when the NTP turns into the synchronous state.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

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.
l The NE fails to connect to the NTP server or the connection is interrupted.
l 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
4.191 NULL_SEND
Description
NULL signals (with payload being "0"s) being sent out. When the NULL mapping status of the
board is enabled, the NULL_SEND alarm is generated, indicating that the NULL signals are
being sent out.
Attribute
Parameters
None

When this alarm is generated, the board that reports the alarm is sending out NULL signals and
the opposite station will receive the NULL signals, interrupting services.

OptiX OSN 8800/6800/3800
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
4.192 OA_HIGH_GAIN
Description
Gain of an optical amplifier (OA) board being high. This alarm is generated when the actual
gain of an optical amplifier board is 2 dB higher than the nominal gain.
Attribute
Parameters
None

The receive optical power of the downstream receiver is overloaded, resulting in bit errors in
services.
Possible Causes
The possible causes of the OA_HIGH_GAIN alarm are as follows:
l Cause 1: The specified fiber type mismatches the fiber in use.

l Cause 2: After the nominal gain is set, the current nominal gain is lower than the minimum
nominal gain supported by the new fiber.
l Cause 3: The upstream FIU board is incorrectly configured.

OptiX OSN 8800/6800/3800
l Cause 4: A fault occurs on the board, for example, the gain locking unit on the board is
faulty.
Procedure
Step 1 Check whether the specified fiber type matches the fiber in use. If they mismatch, set the fiber
type again so that they match each other.
Step 2 Check whether the current nominal gain is lower than the minimum nominal gain of the new
fiber. If it is, reset the nominal gain to ensure that it is within the permitted range.
Step 3 Check whether the upstream board is the TN14FIU board and whether it is properly connected.
----End
Related Information
None.
4.193 OCH_FDI
Description
Forward defect at the OCh layer. This alarm is generated to suppress the OCH_FDI_P and
OCH_FDI_O alarms when the two alarms coexist.
Attribute
Parameters
None

If this alarm is due to incorrect logical fiber connections, this alarm has no impact on services.
If this alarm is due to other causes, services are 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 it is
not, modify the logical fiber connection to make it consistent with the actual fiber connection.

OptiX OSN 8800/6800/3800
Step 2 If the alarm persists, check whether the OTS_LOS, OTS_TIM, OTS_LOS_O, or OMS_LOS_P
alarm is generated 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.194 OCH_FDI_O
Description
Forward defect (overhead) at the OCh layer. This alarm is generated when the downstream
station receives the OCH_FDI_O signal inserted by the OTS layer after the OTS layer detects
the OTS_LOS_O signal.
Attribute
Parameters
None

If this alarm is due to other causes, 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.
l The OCh layer receives the FDI_O overhead signal inserted by the OMS layer at the
upstream station when the OMS layer loses overhead signals because of a fiber cut, low
optical power, or dispersion.
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 it is, clear the OTS_LOS_O alarm by following proper handling
procedures.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.195 OCH_FDI_P
Description
Forward defect indication (payload) at the OCh layer. This alarm is generated when the
downstream station receives the OCH_FDI_P signal inserted by the OMS layer after the OMS
layer detects a payload LOS signal.
Attribute

Parameters
None

Possible Causes
l The OCh layer receives the FDI_O overhead signal inserted by the OMS layer at the
upstream station when the OMS layer loses overhead signals because of a fiber cut, low
optical power, or dispersion.
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 it is, clear the OTS_LOS_P or OMS_LOS_P alarm
by following proper handling procedures.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.196 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
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 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 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 port 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 port 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.
If not, connect a suitable dispersion compensation module.
Step 6 Check whether there is the R_LOS alarm.

OptiX OSN 8800/6800/3800
l If yes, clear the alarm according to the handling procedure of R_LOS.

l If not, replace the faulty board.
----End
Related Information
None
4.197 OCH_OCI
Description
Open connection indication at the OCh layer. This alarm is generated when the optical
termination node in the downstream receives the OCI signal inserted to the downstream if no
optical cross-connections are configured on the upstream service link or no logical fiber
connection is configured from the OTU board to the multiplexer board.
Attribute

Parameters
None

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 optical cross-connections at the upstream station are configured. If they are
not, configure the optical cross-connections to ensure the normal transmission of the services.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.198 OCH_SSF
Description
Server signal failure at the OCh layer. This alarm is generated to suppress OCH_SSF_P and
OCH_SSF_O alarms when the two alarms coexist.
Attribute

Parameters
None

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_LOS_P alarm is generated on the FIU board connected to the local board, If it is, 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 the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O, or
OMS_LOS_P alarm is reported at the opposite station and all upstream stations. If it is, clear
the OTS_LOS, OTS_TIM, OTS_LOS_P, OTS_LOS_O, or OMS_LOS_P alarm by following
the proper handling procedures.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.199 OCH_SSF_O
Description
Server signal (overhead) failure at the OCh layer. This alarm is generated when the OMS layer
detects the loss of overhead signals.
Attribute
Parameters
None

management.
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.
Procedure
Step 2 Check whether the OTS_LOS_O alarm is generated on the FIU board connected to the local
board. If it is, clear the OTS_LOS_O alarm by following proper handling procedure.
Step 3 If the alarm persists, check whether an OTS_LOS_O alarm is generated at the opposite station
and all upstream stations. If it is, clear the OTS_LOS_O alarm by following proper handling
procedure.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.200 OCH_SSF_P
Description
Server signal (payload) failure at the OCh layer. This alarm is generated when the OMS layer
detects the loss of payload.
Attribute

Parameters
None

management.
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.
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.
Procedure
Step 2 Check whether the OTS_LOS_P or OMS_LOS_P alarm is generated on the FIU board connected
to the local board. If it is, clear the OTS_LOS_P or OMS_LOS_P alarm by following proper
handling procedure.
Step 3 If the alarm persists, check whether the OTS_LOS_P or OMS_LOS_P alarm is reported at the
opposite station and all upstream stations. If it is, clear the OTS_LOS_P or OMS_LOS_P alarm
by following proper handling procedure.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.201 ODU_AIS
Description
The ODU_AIS is an alarm indicating an optical demultiplexing unit (ODU) alarm.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is unavailable.
Possible Causes
The possible causes of the alarm are as follows:
l Severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur on the local NE.
l Upstream services are damaged.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur
on the local NE. If yes, clear these alarms first. Then, check whether the ODU_AIS alarm is
cleared.
Step 2 If the ODU_AIS alarm persists, locate the NE (FR NE) that initially reports the ODU_AIS alarm.
Then, repeat the preceding step.
Step 3 If the ODU_AIS alarm persists, check whether severer alarms occur on the upstream NE (PR
NE) of the FR NE. If yes, clear the alarms.
Step 4 If the ODU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the ODU_AIS
alarm or severer alarms. Then, perform the following steps:
1. Check whether configurations on the FL NE are correct. If no, correct connection and
configurations.
2. If the ODU_AIS persists, replace the line board on the FL NE.
3. If the ODU_AIS persists, replace the cross-connect board on the FL NE.

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.202 ODU_LCK
Description
The ODU_LCK is an alarm indicating that the signals of the optical demultiplexing unit (ODU)
channel are locked.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is locked so that no customer service can be
carried.
Possible Causes
l The ODU channel is being tested.

Procedure
Step 1 Check whether the ODU channel is being tested. If yes, wait until the test is completed and
unlock the ODU channel. Then, check whether the alarm is cleared.
Step 2 If the ODU channel is not being tested, unclock it. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, the board is faulty. Replace the board.
----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.203 ODU_OCI
Description
The ODU_OCI is an alarm indicating no connection at the optical demultiplexing unit (ODU)
layer.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is disconnected. As a result, services are
unavailable.
Possible Causes
l Severer alarms occur on the local NE, such as the R_LOS, FEC_LOF, and OTU_AIS
alarms.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS, FEC_LOF, and OTU_AIS, occur
on the local NE. If yes, clear these alarms first. Then, check whether the ODU_OCI alarm is
cleared.
Step 2 If the alarm persists, upstream services may be faulty. If the upstream device is an OSN device,
replace the line board. If the upstream device is not an OSN device, add cross-connections for
the downstream ODU channel that has received the ODU_OCI alarm according to the related
alarm handling document.
Step 3 If the alarm persists, the local board is faulty. Then, replace the local board.

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.204 ODU_SNCP_STA_INDI
Description
Status indication of an ODUk SNCP protection group. This alarm is generated on the board of
working channel when the working or protection channel of the protection group is faulty or the
user runs an external switching command, or the Status is WTR State.
Attribute
Parameters
Parameters 1 Indicate the switch requesting status. For example:

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR
Parameters 2 Indicate the current work state.

l 0x01: the standby channel.
l 0x02: the working channel.

OptiX OSN 8800/6800/3800

l When switching is performed to an ODUk SNCP group, the services will be transiently
interrupted.
l When the alarm is generated, the working or protection channel of the ODUk 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 ODUk SNCP
group are faulty.
l Cause 3: The switching is in the WTR state. After the time specified by WTR Times (s)
Procedure
l Cause 1: A user delivers an external switching command.
1. On the U2000, query the switching state of the protection group. If the switching state
is forced switching, manual switching, or locked switching, check whether the external
switching operation is necessary.
external switching.
l Cause 2: The services on the working channel or the protection channel of the ODUk 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.
Revertive. If the attribute is Revertive, the active channel will automatically switch
to the working channel, and after WTR Times the alarm will clear. If the attribute is
Non-Revertive, set it to Revertive, and after WTR Times the alarm will clear.
l Cause 3: The switching is in the WTR state. After the time specified by WTR Times
1. This alarm requires no handling. After the time specified by WTR Times (s) elapses,
the alarm clears.
----End

OptiX OSN 8800/6800/3800
Related Information
For details, see "ODUk SNCP Protection" in the Feature Description.
4.205 ODUk_LOFLOM
Description
Frame alignment signal (FAS) and multiframe alignment signal (MFAS) being abnormal. This
alarm is generated when the information about the upstream frame header does not match the
information about the downstream frame.

l For OptiX OSN 8800, its value is FLEX, 0, 1, 2 or 3.
l For OptiX OSN 6800, its value is FLEX, 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is FLEX, 0, 1, 2 or 5G.
Attribute
Parameters
None

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.
l The input optical power is abnormal.
l The FEC type is incorrectly configured.
l Bit errors in the received signals of the OTU board at the local station are excessive.
l The fiber of the transmission line is abnormal.
Procedure
Step 1 Check whether the equipment at the opposite end generates the alarm. If this alarm is generated,
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 permitted range by using the U2000. For the optical power specifications of the specific

OptiX OSN 8800/6800/3800
board, see "Technical Specifications" in 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 port 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.
----End
Related Information
ITU-T G.709
4.206 ODUk_PM_LCK
Description
ODUk PM signals being 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 server
layer adapts the source and sink. This alarm is generated when the STAT byte value is "101"
during locking.

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

Possible Causes
The signals are locked because they are being tested.
Procedure
Step 1 On the U2000, query and locate the slot ID, port ID, and channel ID of the board that generates
this alarm.
Step 2 Query the board information and set LCK Insertion to Disabled so that the local station does
not insert an LCK signal to the downstream.
----End
Related Information
ITU-T G.709
Related Cases:
l MC-A157 An OptiX OSN 6800 Network Cannot Be Reverted Back to the Working
Channel After Being Restored from an ODUk SNCP Protection Switching, The Board
Reports The ODU_SNCP_PS Alarm
4.207 ODUk_PM_OCI
Description
Indication for an ODUk PM open connection. This alarm is generated when the output port is
not connected to the input port and the STAT byte value is "110".

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

Possible Causes
l The corresponding board at the upstream station has the ODUk_PM_OCI alarm.
l There is a loopback on the corresponding board at the opposite station.
l The corresponding board at the opposite station has no cross-connection configuration and
the non-intrusive monitoring function at the local station is enabled.
Procedure
Step 1 On the U2000, query whether there is an alarm with a higher severity on the board. If there is,
handle the alarm with higher severity.
Step 2 If the alarm persists, query whether the upstream station generates the alarm. If this alarm is
generated, 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 a loopback is found, release the loopback.
Step 4 If the alarm persists, check the cross-connection configuration on the corresponding board at
the station where the alarm is triggered. If no cross-connection is configured, check whether
cross-connections need to be configured at the station. If yes, configure cross-connections. If
no, disable the non-intrusive monitoring function at the local station.
Step 5 Confirm the alarm has cleared. If the alarm persists, contact Huawei for assistance.
----End
Related Information
ITU-T G.709
Related Cases:
SPRing Protection
4.208 ODUk_PM_TIM
Description
Mismatch of the ODUk PM trace identifier. This alarm is generated during control process when
the 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.
For the set TIM detection mode, the network architecture can be classified into the following
types.

OptiX OSN 8800/6800/3800
l For the point-to-point topology, only the source access point identifiers (SAPI) is compared
for the sink of trail termination.
l For the point-to-multipoint topology, only the SAPI is compared for the sink of trail
termination.
l For the multipoint-to-multipoint topology, only the destination access point identifiers
(DAPI) is compared for the sink of trail termination.

Attribute
Parameters
None

If the alarm is generated, the signal quality of the services at the optical port is degraded. As a
result, the service signals may be unavailable.
Possible Causes
l The networking architecture and the TIM detection mode to be configured are not
consistent.
l The trail trace identifier (TTI) sent at the opposite end is not consistent with the TTI to be
received at the local end.
l The fiber connection is incorrect.
l 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 port 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.
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 on the U2000. If they are inconsistent, 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.

OptiX OSN 8800/6800/3800
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 it is not, correctly configure the
cross-connection.
----End
Related Information
ITU-T G.709
4.209 ODUk_TCMn_AIS
Description
ODUk TCMn alarm indication signal. An AIS signal is transmitted to the downstream, indicating
that a signal failure is detected in the upstream.

l For OptiX OSN 8800, its value is 0, 1, 2, 3, or 4.
l For OptiX OSN 6800, its value is 0, 1, 2, 3, 4, or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2, or 5G.
n indicates the level of TCM and its value ranges from 1 to 6.
Attribute
Parameters
None

The services carried at the optical port are unavailable.
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_AIS signal.
l The corresponding board at the opposite end transmits the ODUk_TCMn_AIS signals.
l The loopback or cross-connection is set at the upstream station, and the FEC type is
incorrectly configured.

OptiX OSN 8800/6800/3800
Procedure
handle the alarm with a higher severity.
Step 2 Query whether the alarm is reported from the client side. If it is, check the equipment on the
client side.
Step 3 On the U2000, 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. If the alarm exists, check the equipment at the opposite
end.
Step 4 On the U2000, query whether the loopback is set on the upstream station. If it is, 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.210 ODUk_TCMn_BDI
Description
ODUk TCMn backward defect indication. This alarm is generated when five consecutive BDI
bytes in the TCMn overhead field are "1".
Attribute
Parameters
None

Bit errors occur at the downstream station.

OptiX OSN 8800/6800/3800
Possible Causes
l Signals input from the client side contain the ODUk_TCMn_BDI signal.
l 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.
l 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 on the U2000. If it does, handle the corresponding alarm at the downstream station.
----End
Related Information
ITU-T G.709
4.211 ODUk_TCMn_DEG
Description
ODUk TCMn signal being degraded. This alarm is generated if signal degradation occurs or the
bit error count exceeds the threshold when the error detection is in burst mode and generated if
signal degradation occurs when the error detection in Poisson mode.

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

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.
l The optical interface at the opposite end is faulty.
Procedure
Step 1 On the U2000, 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 Check whether the input optical power of the place where the alarm is first generated is within
the permitted range on the U2000. If it is not, handle the alarm according to the handling
procedures of the IN_PWR_HIGH and IN_PWR_LOW alarms.
Step 5 If the alarm persists, the optical interface on the board at the local end may be faulty. Replace
the pluggable optical module or the faulty board.
Step 6 If the alarm persists, the optical interface on the OTU board at the opposite end may be faulty.
Replace the pluggable optical module on the OTU board or the faulty OTU board.
----End
Related Information
ITU-T G.709
4.212 ODUk_TCMn_EXC
Description
Count of ODUk TCMn section BIP8 errors exceeding the threshold. This alarm is generated
when the number of bit errors exceeds the threshold if the error detection is in the Poisson mode.

OptiX OSN 8800/6800/3800
l For OptiX OSN 8800, its value is 0, 1, 2, 3

l For OptiX OSN 6800, its value is 0, 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 0, 1, 2 or 5G.
Attribute
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.
l The transmit part of the opposite station is faulty.
Procedure
Step 1 Check whether the received optical power of the port is within the permitted range on the
U2000. For the optical power specifications of the specific board, see "Technical Specifications"
in 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 port on the
upstream board is within the permitted range on the U2000. For the optical power specifications
of the specific board, see "Technical Specifications" in 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 procedure of the OUT_PWR_LOW alarm.
Step 3 If the alarm persists, check whether the bit error alarm exists at the upstream station on the
U2000. Loop back the transmit optical port and receive optical port 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.
Step 4 If the alarm persists, replace the faulty board at the local station.
----End

OptiX OSN 8800/6800/3800
Related Information
ITU-T G.709
4.213 ODUk_TCMn_LCK
Description
ODUk TCMn signal being 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 server
layer adapts the source and sink. The alarm is generated when the STAT byte value is "101"
during locking.

Attribute
Parameters
None

The services carried at the optical port are unavailable.
Possible Causes
The current line signals are being tested.
Procedure
Step 1 On the U2000, query and locate the slot ID, port ID, and channel ID of the board that generates
this alarm.
Step 2 Set the LCK type to Disabled if it is Enabled.
----End

OptiX OSN 8800/6800/3800
Related Information
ITU-T G.709
4.214 ODUk_TCMn_LTC
Description
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
network node interface (NNI) to optical network node interface (NNI) monitors the connection
of the ODUk through the carrier network. This alarm is generated when the serial connection is
lost and the STAT byte is "000".

Attribute
Parameters
None

The TCM is not available.
Possible Causes
The TCM at the opposite end is not set as enabled, and there is no TCM source.
Procedure
Step 1 On the U2000, find the position that generates this alarm first according to the logical fibers
topology.
Step 2 Query whether the configuration of the position and its opposite position is correct. If not, modify
the configuration
----End

OptiX OSN 8800/6800/3800
Related Information
ITU-T G.709
4.215 ODUk_TCMn_OCI
Description
Indication for an ODUk TCMn open connection indication. This alarm is generated when the
output port is not connected to the input port and the STAT byte is "110".

Attribute
Parameters
None

Possible Causes
l The corresponding board at the upstream station has the ODUk_TCMn_OCI alarm.
l There is a loopback on the corresponding board at the opposite station.
l The corresponding board at the opposite station has no or incorrect cross-connection
configuration.
Procedure
Step 2 If the alarm persists, check whether the upstream station generates this alarm. If this alarm is
generated, 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 a loopback is found, release the loopback.

OptiX OSN 8800/6800/3800
Step 4 If the alarm persists, check whether a cross-connection is correctly configured for the
corresponding board of the station that triggers this alarm. If it is not, configure the correct cross-
connection.
----End
Related Information
ITU-T G.709
4.216 ODUk_TCMn_SSF
Description
Failure of ODUk TCMn serverlayer signals.

Attribute
Parameters
None

Possible Causes
l The ODUk_TCMn_AIS or ODUk_LOFLOM alarm is generated on the line.
l The OTUk_TIM alarm is generated on the line and the OTUk_TIM follow-up response is
set to be enabled.
l 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.

OptiX OSN 8800/6800/3800
1. Check whether the ODUk_PM_AIS or ODUk_LOFLOM alarm occurs at the station. If it

does, clear the alarm according to the corresponding handling procedure.
2. Check whether the OTUk_TIM alarm occurs at the station. If it does, 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. If it does, clear the
alarm according to the alarm handling procedure.
----End
Related Information
None
4.217 ODUk_TCMn_TIM
Description
ODUk TCMn trace identifier mismatch. This alarm is generated during control process when
the trail trace identifier at the opposite end mismatches that at the local end when the TIM
detection is enabled.
For the set TIM detection mode, the system compares the access point identifiers (API) in the
input signals and the expected API, and the network architecture can be classified into the
following types:
termination.

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

If the alarm is generated, the quality of the signals at the optical port is degraded. As a result,
the service signals may be unavailable.
Possible Causes
l The networking architecture and the TIM detection mode to be configured are inconsistent.
l The trail trace identifier (TTI) sent at the opposite end is inconsistent 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 TIM detection
mode for the local end on the U2000 port 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.
received at the local end through the U2000. If they are inconsistent, 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
4.218 ODUKSP_PS
Description
The ODUKSP_PS is an alarm indicating the ODUk SP protection switching. This alarm is
generated when the ODUk SP protection group actuates switching in which the current channel

OptiX OSN 8800/6800/3800
Attribute
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
switching. Such a command makes the current channel of the ODUk SP protection group
l Cause 2: The services of the working channel of the ODUk SP protection group are faulty.
reported.
Procedure
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.
----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

OptiX OSN 8800/6800/3800
services between all stations. For OptiX OSN 8800 and OptiX OSN 6800, see "ODUk SPRing
Protection" in the Feature Description.
Related Cases:
SPRing Protection
4.219 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
Parameters

OptiX OSN 8800/6800/3800
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.
l 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.

OptiX OSN 8800/6800/3800
Possible Causes
l The user issues an external switching command such as forced switching, manual
l The services of the working or protection channel of the ODUk SP protection group are
faulty.
l The switching is in the WTR state. After WTR Times, the alarm is cleared.
Procedure
switching, manual switching, or locked switching, check whether the external switching is
necessary.
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 WTR Times, 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 OptiX OSN 8800 and OptiX OSN 6800, see "ODUk SPRing
4.220 OH_LOOP
Description
The OH_LOOP is an alarm indicating an overhead bus loopback on a line board.
Attribute
Minor Security alarm

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 1 Indicates the loopback mode.
l 0x01: outloop
l 0x02: loopback of the clock board
l 0x03: loopback of the SCC board

When this alarm occurs, a loopback occurs on the overhead bus of the line board. Services are
not affected but ECC communications are interrupted.
Possible Causes
A loopback occurs on the overhead bus of the line board.
Procedure
Step 1 Release the loopback, and the alarm is automatically cleared.
----End
Related Information
None.
4.221 OLP_PS
Description
Optical line protection switching. This alarm is generated when the optical line protection group
undergoes switching and the active channel switches to the protection channel from the working
channel.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

When the optical line protection group undergoes switching, services are transiently interrupted.
When this alarm is reported, the working channel of the optical line protection group might have
Possible Causes
switching. Such a command makes the active channel of the optical line protection group
switch to the protection channel from the working channel.
l Cause 2: The receive optical power of the working channel of the optical line protection
group is abnormal. As a result, the active channel automatically switches to the working
channel and the alarm is reported.
l Cause 3: The difference between the optical power on the working channel and that on the
protection channel exceeds the threshold.
Procedure
1. Query whether the input optical power of the working channel is within the permitted range
on the U2000. For the optical power specifications of the specific board, see "Technical
Specifications" in 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 permitted
range.
is, after WTR Times the active channel automatically switches to the working channel and
the alarm clears. If the attribute is Non-Revertive, set the attribute to Revertive, and after
WTR Times the alarm clears.

OptiX OSN 8800/6800/3800
Step 3 If the alarm persists, check whether the POWER_DIFF_OVER alarm is generated. If it is, 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.
4.222 OLP_STA_INDI
Description
Status indication of an optical line protection group. This alarm is generated when the working
or protection channel of the protection group is faulty or the user runs an external switching
command.
Attribute
Parameters

l 0x0F: locked switching
l 0x0E: forced switching
l 0x06: Exercise switching
l 0x05: WTR

OptiX OSN 8800/6800/3800

l When protection switching is performed on an optical line, the services are transiently
interrupted.
l 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 delivers an external switching command such as forced switching, manual
l The services on the working channel or protection channel of the optical line protection
group are faulty.
l The switching is in the WTR state. After the WTR time elapses, the alarm is cleared.
Procedure
necessary.
2. If the external switching is unnecessary, deliver a switching clearing command to clear the
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
permitted range on the U2000. For the optical power specifications of the specific board,
see "Technical Specifications" in the Product Description. If the optical power is not within
the permitted 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 permitted range.
is, after WTR Times the active channel automatically switches to the working channel and
the alarm clears. If the attribute is Non-Revertive, set the attribute to Revertive, and after
WTR Times the alarm is cleared.
WTR state. This alarm requires no handling. After the WTR time elapses, 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.

OptiX OSN 8800/6800/3800
4.223 OMS_BDI
Description
Backward defect indication at the OMS layer. This alarm is generated to suppress the
OMS_BDI_P and OMS_BDI_O alarms when the two alarms coexist.
Attribute
Parameters
None

Services are not affected if this alarm is caused by incorrect fiber connections. If this alarm is
due to other causes, services are interrupted.
Possible Causes
The OMS_BDI_P and OMS_BDI_O alarms coexist.
Procedure
Step 2 Check whether the OTS_LOS, OTS_LOS_O, OTS_TIM or OMS_LOS_P alarm is generated at
the opposite station and all downstream stations. If it is, clear the OTS_LOS, OTS_LOS_O,
OTS_TIM or OMS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.224 OMS_BDI_O
Description
Backward defect indication (overhead) at the OMS layer. This alarm is generated when the local
station receives the OMS_BDI_O signal inserted back by the downstream station after the
downstream station detects no overhead signals.

OptiX OSN 8800/6800/3800
Attribute

Parameters
None

due to other causes, system monitoring and management is affected.
Possible Causes
l The logical fiber connection is inconsistent with the actual fiber connection.
l The local station receives the BDI_O overhead signal inserted back to the OMS layer by
the downstream station when the downstream station detects no overhead signals because
of a fiber cut, low optical power, or dispersion.
Procedure
Step 2 Check whether the OTS_LOS_O alarm is generated at the opposite station and all downstream
stations. If it is, clear the OTS_LOS_O alarm by following proper handling procedures.
----End
Related Information
None
4.225 OMS_BDI_P
Description
Backward defect indication (payload) at the OMS layer. This alarm is generated when the local
station receives the OMS_BDI_P signal inserted back by the downstream station after the
downstream station receives no payload signals from the local station.
Attribute


OptiX OSN 8800/6800/3800
Parameters
None

Possible Causes
The logical fiber connection is inconsistent with the actual fiber connection.The local station
receives the BDI_P overhead signal inserted back to the OMS layer by the downstream station
when the downstream station detects no overhead signals because of a fiber cut, low optical
power, or dispersion.
Procedure
Step 2 Check whether the OTS_LOS_P or OMS_LOS_P alarm is generated at the opposite station and
all downstream stations. If it is, clear the OTS_LOS_P or OMS_LOS_P alarm by following
proper handling procedures.
----End
Related Information
None
4.226 OMS_FDI_O
Description
Forward defect indication (overhead) at the OMS layer. This alarm is generated when the
downstream station receives the OMS_BDI_O signal inserted by the local station after the OTS-
layer board at local station detects loss of overhead signals and cannot send overhead signals to
the downstream station.
Attribute

Parameters
None

OptiX OSN 8800/6800/3800

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
Step 2 Check whether the OTS_LOS_O alarm is generated at the opposite station and all downstream
stations. If it is, clear the OTS_LOS_O alarm by following proper handling procedures.
----End
Related Information
None
4.227 OMS_FDI_P
Description
Forward defect indication (payload) at the OMS layer. This alarm is generated when the
downstream station receives the OMS_FDI_P signal inserted to the downstream station after
the OTS-layer board at the local station detects loss of overhead signals and cannot send overhead
signals to the downstream station.
Attribute
Parameters
None


OptiX OSN 8800/6800/3800
Possible Causes
The logical fiber connection is not consistent with the actual fiber connection.The FDI_P
overhead signal is inserted to the OMS layer of the downstream station when the local station
detects loss of payload signals because of a fiber cut, low optical power, or dispersion. This
alarm is generated when the downstream station receives the FDI_P overhead signal.
Procedure
Step 2 Check whether the OTS_LOS_P alarm is generated at the opposite station and all upstream
stations. If it is, clear the OTS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.228 OMS_LOS_P
Description
Loss of signal (payload) at the OMS layer. This alarm is generated when the OTU board detects
the LOS alarm but there is no OTS_LOS_P alarm at the OTS layer.
Attribute

Parameters
None

Possible Causes
The OMS layer detects no payload signals because of there is a fiber cut, low optical power, or
dispersion.

OptiX OSN 8800/6800/3800
Procedure
Step 2 Verify that the actual fiber connection between the board that reports this alarm and the FIU
board is correct.
Step 3 Check whether the OTS_LOS alarm is reported on the FIU board. If it is, clear the alarm
according to the procedure to handle OTS_LOS.
Step 4 Check whether the MUT_LOS alarm is generated at the local station and on upstream boards.
l If yes, clear the alarm according to the procedure to handle MUT_LOS.
l If no, replace the faulty board at the local station.
----End
Related Information
None
4.229 OMS_SSF
Description
Server signal failure at the OMS layer. This alarm is generated to suppress the OMS_SSF_P and
OMS_SSF_O alarms when the two alarms coexist.
Attribute

Parameters
None

Possible Causes
The OMS_SSF_P and OMS_SSF_O alarms coexist.

OptiX OSN 8800/6800/3800
Procedure
Step 2 Check whether the OTS_LOS, OTS_TIM, OTS_LOS_P, or OTS_LOS_O alarm is reported on
the FIU connected to the local board. If it is, 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 the OTS_LOS, OTS_TIM, OTS_LOS_P, or OTS_LOS_O
alarm is generated at the opposite station and all upstream stations. If it is, clear the OTS_LOS,
OTS_TIM, OTS_LOS_P, or OTS_LOS_O alarms by following proper handling procedures.
----End
Related Information
None
4.230 OMS_SSF_O
Description
Server signal (overhead) failure at the OMS layer. This alarm is generated when the OTS layer
detects the failure of the overhead signals, or receives the OMS_FDI_O signal from the upstream
station.
Attribute

Parameters
None

Possible Causes
l Because of a fiber cut, low optical power, or dispersion, the OTS layer cannot detect
overhead signals and the OMS layer receives an overhead signal failure message from the
OTS layer.

OptiX OSN 8800/6800/3800
Procedure
Step 2 Check whether the OTS_LOS_O or OOS_LOST alarm is reported on the FIU connected to the
local board. If it is, clear the OTS_LOS_O, or OOS_LOST alarm by following proper handling
procedures.
Step 3 If the alarm persists, check whether the OTS_LOS_O or OOS_LOST alarm is generated at the
opposite station and all upstream stations. If it is, clear the OTS_LOS_O or OOS_LOST alarm
by following proper handling procedures.
----End
Related Information
None
4.231 OMS_SSF_P
Description
Server signal fails (payload) at the OMS layer. This alarm is generated when the OTS layer
detects the failure of the payload signals or receives the OMS_FDI_P signal from the upstream
station.
Attribute

Parameters
None

Possible Causes
Because of a fiber cut, low optical power, or dispersion, the OTS layer cannot detect signals and
the OMS layer receives a payload signal failure message from the OTS layer.

OptiX OSN 8800/6800/3800
Procedure
Step 2 Check whether OTS_LOS_P alarm is generated on the FIU connected to the local board. If it
is, clear the OTS_LOS_P alarm by following proper handling procedures.
Step 3 If the alarm persists, check whether the OTS_LOS_P alarm is generated at the opposite station
and all upstream stations. If it is, clear the OTS_LOS_P alarms by following proper handling
procedures.
----End
Related Information
None
4.232 OOL
Description
The OOL is an alarm indicating that the phase-locked loop is out of lock. This alarm is generated
when the phase-locked loop on the clock board becomes faulty.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the failed phase-locked loop.
l 0x00: 155M system phase-locked loop

l 0x01: The first 2M phase-locked loop
l 0x02: The second 2M phase-locked loop

OptiX OSN 8800/6800/3800

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.
----End
Related Information
4.233 OOS_LOST
Description
Loss of OTM overhead signal (OOS). This alarm is generated when the local station receives
no overhead signals in 10 consecutive seconds and there is no OTS_LOS_O alarm.
Attribute

Parameters
None

Services are not affected when this alarm is caused by incorrect fiber connections. If this alarm
is due to other causes, optical-layer overheads are affected.
Possible Causes

OptiX OSN 8800/6800/3800
l The local station receives no overhead signals in 10 consecutive seconds because the
opposite station sends no overhead signals.
Procedure
Step 2 Check whether the opposite station supports the optical line supervision (OLS) function.
l If no, this alarm does not need to be handled.
l If yes, make sure that the opposite station sends the correct overhead signals.
----End
Related Information
None
4.234 OPA_FAIL_INDI
Description
Failure in automatic power adjustment of optical cross-connections. The alarm is generated when
the calculated attenuation exceeds the adjustment range of the board during an automatic optical
power adjustment.
Attribute
Major Process alarm
Parameters
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.
l 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.

OptiX OSN 8800/6800/3800
l Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or
VA4 board is used.
l 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.
Procedure
l Cause 1: The optical power budget is insufficient.
1. 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.
l Cause 2: The attenuation of the VA1 or VA4 board is manually modified if the VA1 or
VA4 board is used.
1. 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.
l 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 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
None
4.235 OPU1_MSIM
Description
OPU1 multiplex structure identifier mismatch.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The services may be unavailable.
Possible Causes
l Cause 1: Bit errors in services cause damages to overheads.
l Cause 2: Two boards interconnected by the WDM side have inconsistent cross-connection
configurations and therefore their multiplexing structures are inconsistent.
Procedure
Step 1 Check for alarms related to bit errors. If any alarm related to bit errors is present, preferentially
handle the alarm to eliminate the bit errors.
Step 2 Check whether the board that reported the OPU1_MSIM alarm and the board interconnected
have consistent cross-connection configurations. If their cross-connection configurations are
inconsistent, change the configurations to be consistent.
----End
Related Information
ITU-T G.709
4.236 OPU1_VCAT_SQM
Description
OPU1 sequence identifier mismatch. This alarm is generated when the received OPU1 sequence
identifier (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.

OptiX OSN 8800/6800/3800
Attribute
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. The services are interrupted.
Possible Causes
The cross-connection configuration is incorrect.
Procedure
Step 1 Check whether the cross-connection sequence of the virtual concatenated OPU1 at the local end
mismatches that at the opposite end. If it does not, re-configure the virtual concatenated OPU1s
at the local end.
----End
Related Information
Each channel on the WDM side has an SQ value. The SQ values of optical ports are in ascending
order. Compare the SQ value of the frame in each WDM-side optical port with that of its previous
frame. If mismatch is found, the SQ mismatch alarm of the optical port is reported. If the SQ
values of two optical ports are the same, the board also reports the SQ mismatch alarm.
4.237 OPU1_VCAT_VcPLM
Description
OPU1 virtual concatenation payload mismatch. This 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 are interconnected with each other, the alarm is generated if the service types at the
two ends mismatch.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

Possible Causes
l Service type configuration is incorrect.
l 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 it is 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 it is not, re-configure the
cross-connect service at the opposite end.
----End
Related Information
ITU-T G.709
4.238 OPU2_MSIM
Description
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Possible Causes
Procedure
----End
Related Information
ITU-T G.709
4.239 OPU3_MSIM
Description
Attribute
Parameters
None


OptiX OSN 8800/6800/3800
Possible Causes
Procedure
----End
Related Information
ITU-T G.709
4.240 OPU4_MSIM
Description
Attribute
Parameters
None

Possible Causes

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
ITU-T G.709
4.241 OPUk_CSF
Description
Client-side signal failure. This alarm is generated when the client-side signals of the remote end
fail. In this case, the OPU overhead is inserted at the local end and then an alarm is reported,
indicating the signal failure.
k indicates the level of rate and its value is 0, 1, 2 or FLEX.
Attribute
Parameters
None

Such an alarm indicates that client-side signals of the remote end fail.
Possible Causes
An R_LOS or a PORT_MODULE_OFFLINE alarm is generated on the client side of the remote
end.
Procedure
Step 1 On the U2000, check whether an R_LOS or a PORT_MODULE_OFFLINE alarm is generated
on the client side of the remote end. If it is, clear the alarm.
----End

OptiX OSN 8800/6800/3800
Related Information
ITU-T G.709
4.242 OPUk_PLM
Description
OPUk payload mismatch. The type of received payload mismatches the expected payload type
defined in the adaptation function.

Attribute
Parameters
None

Services may be unavailable.
Possible Causes
The payload types in the data on the WDM side of the interconnected board mismatch.
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.
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

OptiX OSN 8800/6800/3800
Related Information
ITU-T G.709
4.243 OSC_BDI
Description
Backward defect indication. This alarm is generated when a signal failure is detected and the
BDI byte value is 1.
Attribute
Parameters
None

The OSC signals carried by the optical port will fail.
Possible Causes
The BDI bit in the overhead field (byte 3, bit 5) is "1" for 5 consecutive frames.
Procedure
Step 1 Query whether an alarm with a higher severity is generated on the board on the U2000. If it is,
Step 2 If the alarm persists, check whether the corresponding board at the downstream station receives
the R_LOS orR_LOF alarm on the U2000. If it does, handle the corresponding alarm at the
downstream station.
----End
Related Information
None
4.244 OSC_DEG
Description
Signal degraded alarm. This alarm is generated when bit errors are of burst distribution and the
signal degradation or bit error count crosses the threshold.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

If the alarm is generated, the OSC signals carried by the optical port will generate bit errors,
which makes the OSC signals unavailable.
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 permitted range. For the optical
power specifications of the specific board, see "Technical Specifications" in the Product
Description. If the optical power is not within the permitted 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. Replace the board.
----End
Related Information
None
4.245 OSC_RDI
Description
Remote defect. This alarm is generated when the opposite station returns the RDI alarm to the
local station after receiving an R_LOF alarm.

OptiX OSN 8800/6800/3800
Attribute
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.
l The optical fiber is damaged.
Procedure
Step 1 Query whether the R_LOF alarm is generated at the opposite station. If it is not, clear the
OSC_RDI alarm as an R_LOF alarm.
Step 2 If the alarm persists, check whether the fiber between the two stations is damaged. If it is, repair
the fiber.
----End
Related Information
None
4.246 OTS_BDI
Description
backward defect at the OTS layer. This alarm is generated to suppress the OTS_BDI_P and
OTS_BDI_O alarms when the two alarms coexist.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Possible Causes
l The opposite station reports the OTS_LOS alarm and inserts BDI signals back to the local
station.
Procedure
Step 1 Check whether the logical fiber connection of the FIU board is consistent with the actual fiber
connection. If it is not, modify the logical fiber connection to make it consistent with the actual
fiber connection.
Step 2 Check whether the OTS_TIM or OTS_LOS alarm is generated at the opposite station. If it is,
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 ports on the local
FIU are correct and no fiber is disconnected.
----End
Related Information
None
4.247 OTS_BDI_O
Description
Backward defect (overhead) at the OTS layer. This alarm is generated when the local station
receives the OTS_BDI_O signal inserted by the upstream station.
Attribute

Parameters
None

OptiX OSN 8800/6800/3800

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, verify that the fiber connection of the "RM" port on the local FIU board is
correct and no fiber is disconnected.
Step 3 Check whether the OTS_LOS_O alarm is generated on the opposite FIU board. If it is, handle
the alarm by following proper handling procedures.
----End
Related Information
None
4.248 OTS_BDI_P
Description
Backward defect (payload) at the OTS layer. This alarm is generated when the local station
receives the OTS_BDI_P signal inserted back by the downstream station.
Attribute
Parameters
None


OptiX OSN 8800/6800/3800
Possible Causes
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
fiber connection.
Step 2 If the alarm persists, verify that fiber connections of the receive ports of the local FIU board are
Step 3 Check whether the OTS_LOS_P alarm is generated on the opposite FIU board. If it is, clear the
OTS_LOS_P alarm by following proper handling procedures.
----End
Related Information
None
4.249 OTS_LOS_O
Description
Loss of signals (overhead) at the OTS layer. This alarm is generated when the OSC board
connected to the "TM" port of the FIU board detects the LOS signals.
Attribute
Parameters
None

Possible Causes

OptiX OSN 8800/6800/3800
This alarm is generated when the OTS layer of the receive end detects no overhead signal because
Procedure
Step 1 Check whether the logical fiber connection of the FIU is consistent with the actual fiber
fiber connection.
Step 2 If the alarm persists, verify that the fiber connection between the "TM" port of the local FIU
board and the OSC board is correct and no fiber is disconnected.
Step 3 If the alarm persists, verify that the fiber connection between the "TM" port of the local FIU
board and the OSC board is correct and no fiber is disconnected.
Step 4 If the alarm persists, check whether the laser of the OSC board at the opposite station is "On".
If it is not, turn on the laser of the OSC board.
----End
Related Information
None
4.250 OTS_LOS_P
Description
Loss of signals (payload) at the OTS layer. This alarm is generated when the OA board or other
boards connected to the transmit port of the FIU detects the LOS signals.
Attribute
Parameters
None

Possible Causes
This alarm is generated when the OTS layer of the receive end detects no payload signal because

OptiX OSN 8800/6800/3800
Procedure
fiber connection.
Step 2 If the alarm persists, verify that the fiber connections of all ports on the local FIU board are
----End
Related Information
None
4.251 OTS_TIM
Description
Mismatch of the trail trace identifier at the OTS layer. This alarm is generated When the API of
the received TTI at the OTS layer is not consistent with the API to be received.
Attribute
Parameters
None

Services are not affected if this alarm is caused by incorrect TTI configuration and are interrupted
if this alarm is caused by incorrect fiber connections.
Possible Causes
l The TTI transmitted at the upstream station is not consistent with the TTI to be received at
the local station.
l 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 it is not, configure the TTI at the upstream station again.
Step 2 Check whether the fiber connection between the OSC and the "RM" or "TM" port of the FIU
board is compliant with the network regulation. If it is not, connect the fibers again.
----End

OptiX OSN 8800/6800/3800
Related Information
For details about the API and TTI, see ITU-T G.709.
4.252 OTU_AIS
Description
The OTU_AIS is an alarm indicating an optical transponder unit (OTU) alarm.
Attribute
Parameters
None.

When this alarm occurs, the entire ODU channel is disconnected. As a result, services are
unavailable.
Possible Causes
l Severer alarms occur on the local NE, such as the R_LOS, and FEC_LOF alarm.
Procedure
Step 1 On the NMS, check whether severer alarms, such as R_LOS and FEC_LOF, occur on the local
NE. If yes, clear these alarms first. Then, check whether the OTU_AIS alarm is cleared.
Step 2 If the OTU_AIS alarm persists, locate the NE (FR NE) that initially reports the OTU_AIS alarm.
Then, repeat the preceding step.
Step 3 If the OTU_AIS persists, check whether severer alarms occur on the upstream NE (PR NE) of
the FR NE. If yes, clear the alarms.
Step 4 If the OTU_AIS alarm persists, perform a loopback on the transmit optical ports of NEs from
the FR NE in the upward direction. Locate the NE (FL NE) that initially reports the OTU_AIS
alarm or severer alarms. You can skip this step because fiber loopback interrupts services. If
fiber loopback is not allowed, replace the receive board on the FR NE and transmit board on the
PR NE.
1. Check whether configurations on the FL NE are correct. If no, correct connection and
configurations.

OptiX OSN 8800/6800/3800
2. If the OTU_AIS persists, replace the line board on the FL NE.

3. If the OTU_AIS persists, replace the cross-connect board on the FL NE.
----End
Related Information
None.
4.253 OTU_LOF
Description
The OTU_LOF is an alarm indicating that the frame align signal (FAS) at the optical transponder
unit (OTU) layer is lost.
Attribute
Parameters
None.

When this alarm occurs, the FEC function fails, and services are interrupted.
Possible Causes
l The optical fiber is faulty or the optical power is out of range.
l The board has hardware faults.
l Services that are transmitted from the peer NE are abnormal.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the alarm.
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below the
lower threshold, clean the fiber end and the connector. If the input optical power is above the
upper threshold, add an optical attenuator to adjust the optical power. Then, check whether the
alarm is cleared.

OptiX OSN 8800/6800/3800
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with those
on the network. If not, set clock tracing. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
Step 6 If the alarm persists, replace the local cross-connect board.
Step 7 If the alarm persists, replace the peer line board.
Step 8 If the alarm persists, replace the peer cross-connect board.
----End
Related Information
None.
4.254 OTU_LOM
Description
The OTU_LOM is an alarm indicating that the frame align signal (FAS) at the optical transponder
unit (OTU) is lost.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, multiframes are lost, and services are interrupted.
Possible Causes
l The local NE has not received the expected consecutive number of frames.
l The bit errors during transmission are excessive.

OptiX OSN 8800/6800/3800
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the alarm.
Step 2 Check the input optical power of the board on the NMS. If the input optical power is below the
lower threshold, clean the fiber end and the connector. If the input optical power is above the
upper threshold, add an optical attenuator to adjust the optical power. Then, check whether the
alarm is cleared.
Step 3 If the alarm persists, check the output optical power of the peer board. If the optical power is
below the lower threshold, replace the peer board.
Step 4 If the alarm persists, check whether clocks of the local and peer NEs are synchronized with those
on the network. If not, set clock tracing. Then, check whether the alarm is cleared.
Step 5 If the alarm persists, check the transmission fiber. If the fiber is functioning properly, replace
the board that reports the alarm.
Step 6 If the alarm persists, replace the source board of the OTU channel (excluding the NEs that
transparently transmit the ODU channel).
----End
Related Information
None.
4.255 OTUk_AIS
Description
OTUk alarm indication. An AIS signal travels downstream, which indicates that a signal failure
is detected in the upstream.

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

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.
l The upstream station has loopback or cross-connection or the FEC type configuration is
incorrect.
Procedure
Step 1 Query whether there is an alarm with a higher severity on the board on the U2000. If there is,
Step 2 If the alarm is reported from the client side, check the equipment on the client side.
Step 3 On the U2000, query whether the upstream station has any loopback. If it does, release the
loopback.
Step 4 Check whether the configuration of the cross-connection and FEC type is correct at the upstream
station. If the configuration is incorrect, correct the configuration.
----End
Related Information
ITU-T G.709
4.256 OTUk_BDI
Description
OTUk backward defect indication. This alarm is generated when the SM section detects a signal
failure and the value of the BDI byte is 1.

Attribute
Parameters
None

OptiX OSN 8800/6800/3800

The services at the optical port are unavailable.
Possible Causes
l Signals input from the client side contain the OTUk_BDI alarm.
l The corresponding OTU board at the downstream station receives the LOF, LOM,
OTUk_AIS, or OTUk_TIM, OTUk_SSF alarm.
Procedure
Step 1 On the U2000, query whether an alarm with a higher severity is generated on the board. If it is,
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.
l 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.257 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.

Attribute

OptiX OSN 8800/6800/3800
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. 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 board.
----End
Related Information
ITU-T G.709
4.258 OTUk_EXC
Description
OTUk bit error count crossing 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
l For OptiX OSN 6800, its value is 1, 2, 3 or 5G.
l For OptiX OSN 3800, its value is 1, 2 or 5G.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The alarm has an impact 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 On the U2000, check whether the receive optical power of the port is within the permitted range.
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, replace the faulty board at the local station.
----End
Related Information
ITU-T G.709
4.259 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.


OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The alarm has an influence on the QoS of the service signals.
Possible Causes
l The FEC type is incorrectly configured.
l 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. 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.260 OTUk_TIM
Description
OTUk trail trace identifier (TTI) mismatch. This alarm is generated during the control process
when the TTI at the opposite end mismatches that at the local end if 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
types:

OptiX OSN 8800/6800/3800
termination.

Attribute
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.
l 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 U2000. Select the suitable topology for
the local end on the U2000 port 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.
received at the local end on 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.

OptiX OSN 8800/6800/3800
cross-connection.
----End
Related Information
ITU-T G.709
4.261 OUT_PWR_ABN
Description
The OUT_PWR_ABN is an alarm indicating that the output optical power is abnormal.
Attribute
Parameters
Name Meaning

Parameter 2, Parameter 3 Indicates the path number.

When the OUT_PWR_ABN alarm occurs, the service transmission performance is affected. In
the case of severe alarm, the services are interrupted.
Possible Causes
The possible causes of the OUT_PWR_ABN alarm are as follows:

OptiX OSN 8800/6800/3800
l The output optical power is extremely high or low.

Procedure
Step 1 Check whether the wavelength of the input optical signals is within the specified wavelength
range of the input optical signal of the boards, or check whether the boards report the
PUM_BCM_ALM alarm simultaneously. If the wavelength of the input optical signals is
beyond the specified wavelength range, adjust it to a proper value. Then, check whether the
OUT_PWR_ABN alarm is cleared.
Step 2 If the alarm persists, replace the board that generates the OUT_PWR_ABN alarm.
----End
Related Information
None.
4.262 OUT_PWR_LOW
Description
Output optical power being too low. This alarm is generated when the output optical power of
the laser is excessively low.
Attribute
Parameters
None

The output optical power of the laser is excessively low, which influences the normal
transmission of services.
Possible Causes
l The laser is aged.
Procedure
Step 1 Use an optical power meter to check whether the transmit optical power of the board is within

OptiX OSN 8800/6800/3800
l If the optical power is not within the permitted range, replace the module where the faulty
laser resides. If the alarm persists, replace the board.
l If the optical power is within the permitted range, perform a warm or cold reset on the
board. If the alarm persists, replace the board.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei engineers to handle
the alarm.
----End
Related Information
None
4.263 OWSP_PS
Description
The OWSP_PS is an alarm indicating the OWSP protection switching. This alarm is generated
when the OWSP protection group actuates switching in which the current channel switches to
the protection channel from the working channel.
Attribute
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
switching. Such a command makes the current channel of the OWSP protection group
l Cause 2: The services of the working channel of the OWSP protection group are faulty.
reported.

OptiX OSN 8800/6800/3800
Procedure
to the services, such as R_LOC, R_LOS. If yes, handle the alarms by referring 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.264 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
Minor Communication Alarm
Parameters

OptiX OSN 8800/6800/3800
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.
l When this alarm is reported, the working or protection channel of the OWSP protection
group may have faulty services that need to be restored.

OptiX OSN 8800/6800/3800
Possible Causes
l The user issues an external switching command such as the forced switching, manual
l The services of the working or protection channel of the OWSP protection group are faulty.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.
Procedure
necessary,
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.
WTR state. This alarm requires no handling. After the WTR Times, the alarm is cleared.
----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.265 PASSWORD_NEED_CHANGE
Description
The password of a default user must be changed to reduce risks. This alarm is generated if the
password of any default user is not changed in time.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

None.
Possible Causes
The password of the default user is never changed.
Procedure
Step 1 Change the default password.
----End
Related Information
None
4.266 PATCH_ACT_TIMEOUT
Description
Patch package activation timeout. This alarm is generated when the duration that a patch package
remains the activated state exceeds the threshold.
Attribute
Parameters
None

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 duration that the patch package remains the activated state exceeds the threshold.

OptiX OSN 8800/6800/3800
Procedure
Step 1 If the patch file is correct, run the patch file on 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 to the U2000.
----End
Related Information
None
4.267 PATCH_DEACT_TIMEOUT
Description
Patch package deactivation timeout. This alarm is generated when the duration that a patch
package remains the deactivated state exceeds the threshold.
Attribute
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.
Possible Causes
The duration that the patch package remains the deactivated state exceeds the threshold.
Procedure
Step 1 If the patch file is correct, activate the patch file on the U2000.
Step 2 If the patch file is incorrect, delete the patch file and reload the correct one to the U2000.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.268 PATCH_PKGERR
Description
Patch package file error.
Attribute
Minor Process
Parameters
None

Package loading management of some boards may be unavailable if this alarm is generated.
Possible Causes
Patch package files were damaged, deleted, or incomplete due to a committing failure.
Procedure
Step 1 Contact Huawei engineers to regenerate the patch package files.
----End
Related Information
None
4.269 PM_BDI
Description
The PM_BDI is an alarm indicating a backward defect in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is generated when a major alarm occurs at the
remote ODU and upper layers.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

This alarm is generated only on the ODU termination NE for services in the transmit direction,
which does not affect services in the receive direction.
Possible Causes
l Alarms occur on the remote ODU termination NE.
l The local transmit unit is faulty.
l The remote receive unit is faulty.
Procedure
Step 1 Check whether severer alarms occur on the remote ODU termination NE. If yes, clear these
alarms first. Then, check whether the PM_BDI alarm is cleared.
Step 2 If the alarms at the remote end persist, perform an inloop on the local optical ports. If any alarms
occur, correct configurations according to the alarms.
NOTICE
A loopback interrupts services.
Step 3 If the PM_BDI alarm persists, replace the local board.
Step 4 If the alarms at the remote end persist and the loopback test detects no abnormities on the local
optical ports, replace the remote board.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.270 PM_BEI
Description
The PM_BEI is an alarm indicating a backward error in PM overheads at the optical
demultiplexing unit (ODU) layer. This alarm is generated when PM-BIP check bit errors occur
at the remote end.
Attribute
Parameters
None.

When this alarm occurs, PM_BIP check bit errors occur on the ODU termination NE, which
does not affect the FEC function and performance on the local NE.
Possible Causes
l Bit errors occur on the remote ODU termination NE.
Procedure
Step 1 Check whether bit errors occur on the ODU termination NE. If any bit errors occur, clear these
bit errors. Then, check whether the PM_BEI alarm is cleared.
Step 2 If the bit errors at the remote end persist, perform an inloop on the local optical ports to check
for alarms. If any alarms occur, correct configurations according to the alarms.
NOTICE
Step 3 If the PM_BEI alarm persists, replace the local board.
Step 4 If the bit errors at the remote end persist and the inloop test detects no abnormities on the local

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.271 PM_BIP8_OVER
Description
The PM_BIP8_OVER is an alarm indicating that the number of bit errors in the PM section at
the optical demultiplexing unit (ODU) layer exceeds the threshold.
Attribute
Major Service alarm
Parameters
None.

When this alarm occurs, service transmission quality is affected.
Possible Causes
l The received signals are heavily attenuated.
l The connector is improperly connected.
Procedure
Step 1 On the NMS, check severer alarms, such as R_LOS and R_LOF, on the NMS. Clear these alarms
first and check whether the PM_BIP8_OVER alarm is cleared.
Step 2 Check whether the receive optical power of the alarm-reporting board is within the permitted
range. If yes, go to step 9.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then, check whether

OptiX OSN 8800/6800/3800
Step 4 Check whether the flange is correctly connected to the optical attenuator on the local NE, and
whether the attenuation value specified for the optical attenuator is proper. After determining
that the flange and optical attenuator are used properly, check whether the alarm is cleared.
Step 5 Check whether the transmit optical power on the peer end is within the permitted range. If not,
replace the line board.
Step 6 If the transmit optical power is within the permitted range, clean the peer pigtail connector. Then,
Step 7 Check whether the flange is correctly connected to the optical attenuator on the peer NE, and
Step 8 Verify that optical fibers are properly connected. Then, check whether the alarm is cleared.
Step 9 Replace the local line board that reports the alarm. Then, check whether the alarm is cleared.
Step 10 Replace the local cross-connect board. Then, check whether the alarm is cleared.
Step 11 Replace the peer line board. Then, check whether the alarm is cleared.
Step 12 Replace the peer cross-connect board. Then, check whether the alarm is cleared.
----End
Related Information
None.
4.272 PM_BIP8_SD
Description
The PM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the optical
transponder unit (OTU) layer.
Attribute
Major Service alarm
Parameters
None.


OptiX OSN 8800/6800/3800
Possible Causes
Procedure
Step 1 On the NMS, check severer alarms, such as R_LOS and R_LOF, on the NMS. Clear these alarms
first and check whether the PM_BIP8_SD alarm is cleared.
Step 3 Clean the local fiber connector and the receive optical port on the line board. Then, check whether
Step 5 Check whether the transmit optical power on the peer end is within the permitted range. If not,
replace the line board.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.273 PM_TIM
Description
The PM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM overheads
at the optical demultiplexing unit (ODU) layer.
Attribute
Parameters
None.

When this alarm occurs, the FEC function and services are not affected.
Possible Causes
The PM_TTI byte to be received by the local NE is incorrectly set.
Procedure
Step 1 Check whether the SM_TTI byte to be received by the board is consistent with the received
SM_TTI byte. If not, modify the settings.
----End
Related Information
None.
4.274 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC is an alarm indicating that traffic at Ethernet ports exceeds the
threshold. This alarm is generated when traffic at an Ethernet port exceeds the expected value.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Name Meaning
Parameter 1 Indicates that the bandwidth utilization rate on an Ethernet port exceeds the
threshold.
l 0x00: the RX direction

l 0x01: the TX direction

When this alarm occurs, overlarge traffic will cause network congestion.
Possible Causes
The possible causes of the PORT_EXC_TRAFFIC alarm are as follows:
l Cause 1: The configured value is small for the bandwidth threshold at the Ethernet port.
l Cause 2: The configured Ethernet port traffic is heavy.
Procedure
Step 1 Cause 1: The configured value is small for the bandwidth threshold at the Ethernet port.
1. Query the bandwidth threshold of the Ethernet port on the NMS.
2. If the bandwidth threshold is set low, configure it again to increase the bandwidth or expand
network capacity.
Step 2 Cause 2: The configured Ethernet port traffic is heavy.

1. Query the bandwidth utilization of the Ethernet port on the NMS.
2. If the port bandwidth utilization exceeds its threshold, check whether a network storm
occurs. If a network storm occurs, eliminate the source that transmits a large amount of
invalid data.
----End

OptiX OSN 8800/6800/3800
Related Information
None.
4.275 PORTSWITCH_FAIL
Description
Optical switch switching failure. This alarm is generated when the board detects that an optical
switch inside the board fails to switch.
Attribute
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 on the U2000 or remove the faulty board and insert it
again.
Step 2 After the board is reset, perform the spectrum analysis on the MCA again on the U2000.
----End
Related Information
None
4.276 POWER_ABNORMAL

OptiX OSN 8800/6800/3800
Description
The POWER_ABNORMAL is an alarm indicating a power supply failure. This alarm is
generated when the power supply of a board becomes abnormal.
Attribute
Parameters
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.
l Cause 2: The jumper cap of the SCC is not configured.
l Cause 3: The power module on the board is faulty.
Procedure
l Query current alarms on the U2000. Then, determine the board that reports the alarm. For
details, see Product Description.
l Cause 1: The input power of the PIU is abnormal.
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 Quick Installation Guide of the applicable equipment.
l 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.

OptiX OSN 8800/6800/3800
1. 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.
l 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 Supporting Tasks.
NOTICE
If the services that pass the board are not configured with protection, the services are
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
Supporting Tasks.
----End
Related Information
None
4.277 POWER_DIFF_OVER
Description
Optical power difference exceeding the system limit. This alarm is generated when the power
difference between the active and standby channels crosses the threshold.
Attribute
Parameters
None

The switching of the active and standby channels is affected. As a result, the quality of the
received services is affected.
Possible Causes
l During transmission, the optical power attenuation of signals is excessively large or the
board at the local end is added with an over-large optical attenuator. Therefore, the optical

OptiX OSN 8800/6800/3800
power difference between the active and standby OSCs at the receive end is excessively
large.
l The optical power difference of signals on the active and standby channels when the board
at the opposite end transmits signals is excessively large.
l The detection circuit of the board at the local end is faulty.
Procedure
Step 1 Replace the existing optical attenuators with suitable ones. Adjust the optical power on the active
and standby channels of the board at the local station to ensure that the power difference is within
5 dB.
NOTE
After the POWER_DIFF_OVER alarm is reported, the alarm can be cleared only when the power difference is
with the range of the preset threshold minus 2 dB to avoid alarm jitter.
Step 2 If the alarm persists, the detection circuit of the board at the local station is faulty. Replace the
faulty board.
----End
Related Information
None
4.278 PRBS_LSS
Description
Loss of pseudo-random binary sequence (PRBS) signals. This 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

Parameters
None

The PRBS test services on the board are interrupted.

OptiX OSN 8800/6800/3800
Possible Causes
l Cause 1: The link is abnormal. Therefore, the board, on which the PRBS bit error test is
performed, does not receive the PRBS signals from the local board.
l Cause 2: The board is faulty or the line is degraded.
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, the board is normal. See Step 2 to check the link.
l If the alarm persists, the board is faulty. Refer to Replace the board..
Step 2 Verify 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.279 PTP_SOURCE_SWITCH
Description
PTP time source switching alarm. When the ID of the Grandmaster source traced by the NE or
the tracing port changes, this alarm is reported to remind the user of switchover of the IEEE
1588v2 tracing source.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicates the ID of the line board before switching.
Parameters 3 The value is always 0x00.

OptiX OSN 8800/6800/3800
Name Meaning
Parameters 4 and 5 Indicates the port number before switching.
Parameters 6 to 9 Indicates the GrandmasterID1 before switching.
Parameters 10 to 13 Indicates the GrandmasterID2 before switching.
Parameters 14 and 15 Indicates the slot ID of the line board after switching.
Parameters 16 The value is always 0x00.
Parameters 17 and 18 Indicates the port number after switching.
Parameters 19 and 22 Indicates the GrandmasterID1 after switching.
Parameters 23 and 26 Indicates the GrandmasterID2 after switching.

After this alarm is generated, the IEEE 1588v2 tracing source is switched. As a result, the entire
clock domain undergoes switchover.
Possible Causes
The possible causes of the PTP_SOURCE_SWITCH alarm are as follows:
l Cause 1: The physical link is faulty.

l Cause 2: Quality level, priority 1, or priority 2 of the Grandmaster clock changes.
l Cause 3: The network topology changes.
Procedure
l Cause 1: The physical link is faulty.
1. On the NMS determine the number of the port where the alarm is reported.
2. Check whether a network cable or fiber is disconnected from this port. If yes, reconnect
the network cable or fiber, and then check whether the alarm is cleared.
3. If the alarm persists, check whether the network cable or fiber is faulty. If yes, replace
the network cable or fiber and then check whether the alarm is cleared.
4. If the alarm persists, query the transmit optical power of the opposite NE on the NMS.
If the transmit optical power is normal, replace the optical power of the board or the
board at the opposite NE.
5. If the alarm persists, check whether the local receive board is faulty. If yes, replace
the board that reports the alarm on the local NE.
l Cause 2: Quality level, priority 1, or priority 2 of the Grandmaster clock changes.

OptiX OSN 8800/6800/3800
1. Restore the quality level, priority 1, or priority 2 of the Grandmaster clock to that
before switching. The alarm is automatically cleared when the clock source after
switchover becomes stable.
l Cause 3: The network topology changes.
1. Check whether the new network topology complies with the live network planning.
If yes, the alarm is automatically cleared when the clock source after switchover
becomes stable.
----End
Related Information
None
4.280 PTP_TIMESTAMP_ABN
Description
PTP time stamp exception. When the PTP (IEEE 1588v2) time stamp freezes, this alarm is
reported.
Attribute
Parameters
Name Meaning
is located.

OptiX OSN 8800/6800/3800
Name Meaning
clock.
l 0x01: the first external clock
l 0x02: the second external clock
Parameter 5 Indicates that the time stamps do not change within the detection period.
l 0x01: The t1 time stamp does not change.
l 0x03: Both the t1 and t2 time stamps do not change.
Parameter 6 Indicates that the time stamps do not change within the detection period.
l 0x03: Both the t3 and t4 time stamps do not change.

A time stamp exception during PTP frequency synchronization results in a clock trace exception,
clock drift, PTP time trace exception, and time deviation.
Possible Causes
l Cause 1: The delay mode settings for the ports on two interconnected boards are
inconsistent.
l Cause 2: The hardware of the IEEE 1588v2 port currently traced is faulty.
l Cause 3: The hardware of the clock board is faulty.
l Cause 4: The clock module at the transmit end of the reference source is faulty.
Procedure
l Cause 1: The delay mode settings for the ports on two interconnected boards are
inconsistent.
1. Check whether the delay mode settings for the ports on two interconnected boards are
consistent. If not, modify them to be the same.
l Cause 2: The hardware of the IEEE 1588v2 port currently traced is faulty.
1. On the NMS, check for the HARD_BAD or HARD_ERR alarm on the board with the
IEEE 1588v2 port. Clear such an alarm if there is any.
l Cause 3: The hardware of the clock board is faulty.
1. On the NMS, check for the HARD_BAD or HARD_ERR alarm on the clock board.
Clear such an alarm if there is any.
l Cause 4: The clock module at the transmit end of the reference source is faulty.

OptiX OSN 8800/6800/3800
1. If no HARD_BAD or HARD_ERR alarm occurs on the board with the IEEE 1588v2
port that is currently traced and the clock board, replace the interface board that
corresponds to the transmitter of the reference source. Then, check whether the
PTP_TIMESTAMP_ABN alarm is cleared.
----End
Related Information
None
4.281 PUM_BCM_ALM
Description
Bias current of the pump laser crossing the threshold. This alarm is generated when the pump
laser bias current of the optical amplifier unit crosses the threshold.
Attribute
Parameters
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 to handle the alarm after a period of time; however, the output optical power of the board
or even the services are affected.
Possible Causes
l Excessively high or excessively low ambient temperature affects the laser.
Procedure
Step 1 Check whether the ambient temperature is normal. If it is 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.

OptiX OSN 8800/6800/3800
Step 3 If the alarm persists, remove and re-insert the board under the condition that the services are not
affected.
Step 4 If the alarm persists, replace the faulty board. Refer to Replace the board.
----End
Related Information
None
4.282 PUM_TEM_ALM
Description
Working temperature of the pump laser exceeding the threshold. This alarm is generated when
the operating temperature of the pump laser on the optical amplifier board crosses the threshold.
Attribute
Parameters

The pump laser may be aged. Report of this alarm has no impact on the services. If no measure
is taken to handle the alarm after a period of time; however, the output optical power of the board
or even the services are affected.
Possible Causes
l The ambient temperature is excessively high or excessively low.
l The cooling system of the pump laser is damaged.
l The pump laser has excessive current.
Procedure
Step 1 Check whether the ambient temperature is normal. If it is not, adjust the ambient temperature
of the equipment to a proper degree.

OptiX OSN 8800/6800/3800
Step 2 If the alarm persists, perform a warm reset on the faulty board on the U2000.
Step 3 If the alarm persists, remove and re-insert the board under the condition that the services are not
affected.
----End
Related Information
None
4.283 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC is an alarm indicating that a PW that carries services (such as L2VPN
services) has no traffic.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the direction in which the traffic is unavailable.
l 0x00: RX direction.
l 0x01: TX direction.

Services configured for the PW are interrupted.
Possible Causes
The possible causes of the PW_NO_TRAFFIC alarm are as follows:
l Cause 1: No service is configured.

OptiX OSN 8800/6800/3800
l Cause 2: The local services are abnormal and therefore no packet is transmitted to the
opposite end.
l Cause 3: The opposite services are abnormal and therefore no packet is transmit to the local
end.
l Cause 4: The port that corresponds to the faulty PW works improperly.
Procedure
Step 1 Determine the alarmed board, alarmed port, and direction in which the traffic is unavailable
according to the alarm information on the NMS.
If... Then...
Alarm parameter 1 = 0x00 and 0x01 Go to Step 2.
Parameter 1 = 0x00 Go to Step 4.
Parameter 1 = 0x01 Go to Step 3.
Step 2 Cause 1: No service is configured.

1. Check whether the port is configured with any service. If not, configure services correctly.
2. Check whether the PW_NO_TRAFFIC alarm is cleared. If the alarm persists, go to Step
5.
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to the opposite
end.
1. Check whether the local services carried by the PW are correctly configured.
5.
Step 4 Cause 3: The opposite services are abnormal and therefore no packet is transmit to the local end.
1. Check whether the opposite services carried by the PW are correctly configured.
5.
Step 5 Cause 4: The port that corresponds to the faulty PW works improperly.
1. Replace the board that reports the PW_NO_TRAFFIC alarm at the local end.
2. Check whether the PW_NO_TRAFFIC alarm is cleared. If the alarm persists, replace the
relevant board at the opposite end.
3. Check whether the PW_NO_TRAFFIC alarm is cleared. If the alarm persists, contact
Huawei technical support engineers to handle the alarm.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.284 PWAPS_LOST
Description
The PWAPS_LOST alarm indicates that the PW automatic protection switching (APS) frames
are lost. This alarm is generated when no PW APS frame is received from the protection channel.
Attribute
Parameters
None.

alarms related to the PW APS protection group.
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
Possible Causes
l Cause 1: The opposite NE is not configured with PW APS protection.

l Cause 2: The PW APS protocol is disabled on the opposite NE.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Cause 1: The opposite NE is not configured with PW APS protection.
1. On the NMS, check whether the opposite NE is configured with PW APS protection.
If... Then...
The opposite NE is not configured with PW APS protection Go to the next step.
The opposite NE is configured with PW APS protection Go to Step 2.
2. Configure a PW APS protection group on the opposite NE according to the NE planning

table. Ensure that the configuration on the opposite NE is consistent with the configuration
on the local NE. Then, enable the APS protocol. Check whether the alarm is cleared.
Step 2 Cause 2: The PW APS protocol is disabled on the opposite NE.

1. Check whether the PW APS protocol is enabled on the opposite NE.
If... Then...
The protocol is disabled Disable the PW APS protocol on the local NE and then enable
the protocol at both ends.
The protocol is enabled Go to Step 3.

is physically connected to the port on the protection channel, one end cannot receive APS
packets from the other end. If the fiber or cable is incorrectly connected, rectify the fiber
or cable connection. Check whether the alarm is cleared.
2. Check whether any faults such as signal loss, signal degrade, fiber or cable damage occur
on the protection channel. If yes, rectify these faults immediately.
----End
Related Information
None.
4.285 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH alarm indicates that the local NE and the opposite NE in a
PW APS protection group are configured with different working and protection paths.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
Possible Causes
l Cause 1: The local NE and the opposite NE in a PW APS protection group are configured
with different working and protection paths.
l Cause 2: Physical links are connected incorrectly.
Procedure
Step 1 Cause 1: The local NE and the opposite NE in a PW APS protection group are configured with
different working and protection paths.
1. On the NMS, check whether the PW APS settings at both ends are the same. For example,
check whether PW 1 is set to the working channel and PW 2 is set to the protection channel
at one end, whereas PW 1 is set to the protection channel and PW 2 is set to the working
channel at the other end. Check whether one end of a PW is the working channel, the other
end is the protection channel, and the working and protection channels are different.
2. If the PW APS settings at both ends are different, change them to the same. Then, check

OptiX OSN 8800/6800/3800
Step 2 Cause 2: Physical links are connected incorrectly.

1. Check whether the fiber or cable is correctly connected. For example, check whether the
port on the working channel at one end is physically connected to the port on the protection
channel at the other end due to a manual change of the required port. If the fiber or cable
is incorrectly connected, rectify the fiber or cable connection.
2. Then, check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers for handling the alarm.
----End
Related Information
None.
4.286 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL alarm indicates a PW APS switching failure. This alarm is
generated when the request signals in the transmitted automatic protection switching (APS)
frame are different from the bridge signals in the received APS frame and this symptom lasts
for 50 ms.
Attribute
Parameters
None.


OptiX OSN 8800/6800/3800
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
Possible Causes
l Cause 1: The configurations of the PW APS protection group differ at both ends.
l Cause 2: The physical link deteriorates or is connected incorrectly.
Procedure
Step 1 Cause 1: The configurations of the PW APS protection group differ at both ends.
1. On the NMS, check whether the PW APS settings at both ends are the same. For example,
if the APS protection group is enabled at one end but disabled at the other end, the other
end does not process a received switching request.
2. If the settings are different at the two ends, change them to the same. Then, deactivate and
activate the APS protection groups at both ends.
Step 2 Cause 2: The physical link deteriorates or is connected incorrectly.

is physically connected to the port on the protection channel, one end cannot receive a
switching request from the other end. If the fiber or cable is incorrectly connected, rectify
the fiber or cable connection.
2. Check whether the alarm is cleared. If the alarm persists, check whether any faults such as
signal loss or signal degrade occur on the protection channel. If yes, rectify these faults
immediately.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
4.287 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH alarm indicates that the local NE and the opposite NE are
configured with different PW protection types. This alarm is generated when the PW protection
type indicated in the received automatic protection switching (APS) frame is different from that
specified on the local NE.
Attribute
Parameters
None.

Service protection may fail.
PWAPS_PATH
_MISMATCH
PWAPS_LOST
PWAPS_TYPE_ PWAPS_
Possible Causes
l Cause 1: The protection modes (1+1 or 1:1) are different.

l Cause 2: The switching modes (single-ended or dual-ended) are different.
l Cause 3: The revertive modes (revertive or non-revertive) are different.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Cause 1: The protection modes (1+1 or 1:1) are different.
Cause 2: The switching modes (single-ended or dual-ended) are different.
Cause 3: The revertive modes (revertive or non-revertive) are different.
1. On the NMS, query the settings of the PW APS protection group on both ends, including
protection modes, switching modes, and revertive modes.
2. If the settings are different, change them to the same and enable the APS protocol.
----End
Related Information
None.
4.288 R_LOC
SF64, SF64A, SFD64, SL64, SLD64, 4.288.1 R_LOC (OCS)

Boards other than the SF64, SF64A, SFD64, 4.288.2 R_LOC (OTN)
SLO16, or EGSH
4.288.1 R_LOC (OCS)
Description
The R_LOC is an alarm indicating no clock on the receive side of the line. This alarm is reported
when the line board cannot extract the clock from line signals.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None.

When this alarm occurs, services on the line port are interrupted.
Possible Causes
l The link is faulty so that the board cannot extract the clock.
l Clock tracing is incorrectly configured on the board.
Procedure
Step 1 Check whether the physical link is functioning properly. If not, rectify the link fault. Then, check
Step 2 If the alarm persists, check whether clock tracing configured on the board is the same as planned.
If not, modify the clock tracing configuration. Then, check whether the alarm is cleared.
Step 3 If the alarm persists, cold reset the local line board that reports the alarm. Then, check whether
Step 4 If the alarm persists, the clock tracing module on the line board may be faulty. Replace the line
board and check whether the alarm is cleared.
Step 5 If the alarm still persists, check whether the clock board is faulty. If yes, replace the board. Then,
----End
Related Information
None.
4.288.2 R_LOC (OTN)
Description
Loss of clock on the receiving line. This alarm is generated when the clock signal fails to be
extracted from the received signals.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Services carried at this port are interrupted.
Possible Causes
l The link is abnormal and the board cannot properly extract clock signals.
l The setting of the board clock tracing is incorrect.
Procedure
Step 1 Perform a self-loop on the board. Check whether the physical link is normal. If any exception
such as OTUk_LOF is found, remove the exception.
Step 2 If the alarm persists, check whether the setting of the board clock tracing complies with the entire
network plan. Adjust the board clock setting if it is incorrect.
----End
Related Information
Related Cases:
l 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
l MC-A214 The LQG Board Works Abnormally Due to Incorrect Clock Configuration On
The Board And The Board Reports CLIENT_SF And R_LOC Alarm
l MC-A227 Services Cannot Be Provisioned and The LWX2 Boards Report The R_LOC
Alarm Due to Incorrect Service Rates on LWX2 Board of OptiX OSN 1800
4.289 RELAY_ALARM_CRITICAL
Description
Critical alarm of the alarm input.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

For the OptiX OSN 8800, the status of the external equipment connected to the alarm input port
of the EFI1 board changes.
of the EFI board changes.
of the AUX board changes.
Possible Causes
For the OptiX OSN 8800,
l The status of the alarm input of the EFI1 board changes.

l The alarm input port 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.

l The alarm input port of the EFI board reports the alarm by default. The alarm is reported
l The status of the alarm input of the AUX board changes.

l The alarm input port of the AUX board reports the alarm by default. The alarm is reported
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 port of the EFI1 board changes. If it does,
remove the fault of the external equipment.
access control system) connected to the alarm input port of the EFI board changes. If it does,
access control system) connected to the alarm input port of the AUX board changes. If it does,
Step 4 If no external equipment is connected to the alarm input port, set the input port to Unused and
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.290 RELAY_ALARM_IGNORE
Description
Warning alarm of the alarm input.
Attribute
Parameters
None

Possible Causes




OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
4.291 RELAY_ALARM_MAJOR
Description
Major alarm of the alarm input.
Attribute
Parameters
None

Possible Causes

OptiX OSN 8800/6800/3800



Procedure
----End
Related Information
None
4.292 RELAY_ALARM_MINOR
Description
Minor alarm of the alarm input.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None

Possible Causes



Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.293 REM_SD
Description
Remote signals being degraded. When the received signals on the client side of the board at the
opposite station is degraded, the alarm signal is inserted. This alarm is generated when the
client side of the board at the local station detects the signals.
Attribute
Parameters
None

The QoS of the service signals is affected or even the services are interrupted.
Possible Causes
l The client side of the OTU board at the opposite station has the B1_EXC alarm.
l The demultiplexed client signals on the WDM side of the OTU board at the local station
have the B1_EXC alarm.
Procedure
Step 1 Check whether the OTU board at the opposite station has the B1_EXC alarm. If it does, 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
board at the local station have the B1_EXC alarm. If the B1_EXC alarm is found, see the
procedure of handling B1_EXC to handle the alarm.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.294 RL_CRITICAL_HI
Description
Critical high return loss. This alarm is generated when the return loss is higher than the upper
threshold of the return loss alarm.
Attribute
Parameters
None

If the fiber near the Raman board is incorrectly connected, services may be interrupted.
Possible Causes
l The fiber near the Raman board is broken.
l The fiber near the Raman board is over-bent or pressed.
l The connector of the fiber near the Raman board is unclean.
l The connector of the fiber near the Raman board is incorrectly inserted.
Procedure
Step 1 Ensure that the pump laser on the port of the Raman board is shut down. Check whether the fiber
near the Raman board is properly connected. If it is not, reconnect it.
Step 2 Check whether the fiber near the Raman board is over-bent or pressed. If it is not, spool the fiber
again. If the fiber is broken because of the press, replace it or repair it by means of splicing.
Step 3 Check whether the end face of the fiber near the Raman board is clean. If it is not, clean it again
and properly connect the fiber.
Step 4 Turn on the pump laser on the port of the Raman board and check whether the alarm is cleared.
If the alarm persists, contact Huawei for help.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.295 RL_CRITICAL_LOW
Description
Critical low return loss. This alarm is generated when the return loss is lower than the lower
Attribute
Parameters
None

If the fiber near the Raman board is incorrectly connected, services may be interrupted.
Possible Causes
l The fiber near the Raman board is broken.
l The fiber near the Raman board is over-bent or pressed.
l The connector of the fiber near the Raman board is unclean.
l The connector of the fiber near the Raman board is incorrectly inserted.
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 it is not, reconnect it.
Step 2 If the alarm persists, check whether the fiber near the Raman board is over-bent or pressed. If it
is, 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 persists, check whether the end face of the fiber near the Raman board is clean. If
it is not, clean it again and properly connect the fiber.
Step 4 Turn on the pump laser on the port of the Raman board and check whether the alarm is cleared.
If the alarm persists, contact Huawei for help.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.296 RM_RLOS
Description
Loss of input reverse pump optical signals. This alarm is generated when input reverse pump
optical signals are lost.
Attribute
Parameters
None

Downstream receive optical power is decreased.
Possible Causes
The attenuation of the transmission line is excessively high, or a fiber cut occurs on the
transmission line.
Procedure
Step 1 Check the line status, sort out fibers and check for fiber cuts using a test instrument. Replace
fibers if there are fiber cuts to ensure that the line is in good conditions.
Step 2 Check the upstream and downstream IPA configurations and ensure that they are correct.
----End
Related Information
None
4.297 RS_CROSSTR
Description
Regenerator section performance crossing the threshold. This alarm is generated when the
performance module reports the threshold crossing of regenerator section performance.

OptiX OSN 8800/6800/3800
Attribute
Minor Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the performance statistics period.
l 0x40 indicates 15 minutes performance data.

l 0x80 indicates 24 hours performance data.
Parameter 2 and 3 Indicates the performance event that results in an alarm.
l 0x00 0x01 indicates that an alarm is generated when it is detected that

the RSBBE performance exceeds the limit.
the RSES performance exceeds the limit.
the RSSES performance exceeds the limit.
the RSUAS performance exceeds the limit.

The line has bit errors, which decreases the QoS.
Possible Causes
l The performance of the laser on the board at the opposite station deteriorates.
l The input optical power of the board at the local station is excessively high or excessively
low.
l The performance of the clock at the opposite station deteriorates.
l The fiber performance deteriorates.
Procedure
Step 1 Check whether the fiber is aging or has excessive attenuation. If it is aging or has excessive
attenuation, remove the fault of the fiber.
Step 2 Query whether the board has the B1_EXC, B1_SD, B2_EXC, B2_SD alarm on the U2000. If it
does, clear the alarm.
range on the U2000. For the optical power specifications of the specific board, see "Technical

OptiX OSN 8800/6800/3800
l If the optical power displayed on the U2000 is normal, the board may be faulty. Refer to
Replace the board.
l If the optical power displayed on the U2000 is abnormal, adjust the input optical power to
a value within the permitted range.
Step 4 If the alarm persists, remove the fault of the board at the opposite station.
----End
Related Information
A performance monitoring period can be 15 minutes or 24 hours. A performance threshold
crossing alarm check whether the requirement of alarm clearance is met only after a new
monitoring period starts. If the alarm persists after you perform the provided procedure, query
whether the service has been restored to normal by checking the accumulated performance
values. Or wait after a new monitoring period starts and then check whether the alarm is cleared.
4.298 RTC_FAIL
Description
Timing failure of the real time clock (RTC).
Attribute
Parameters
None

When the alarm is reported, the system employs the soft timing. Therefore, the timestamp
precision of the system decreases.
Possible Causes
l The clip of the RTC clock is damaged.
l The temperature of the board is excessively high.
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 board. For details, see "Replacing the SCC Board" in the
Parts Replacement.
----End

OptiX OSN 8800/6800/3800
Related Information
RTC is also called NE timing.
4.299 RX_POWER_ABNORMAL
Description
Receive optical power abnormal alarm. When the optical module demultiplexes one signal into
multiple channels of optical signals and transmits them at the same time. Although the input
multiplexed optical power is normal, this alarm will be reported if the optical power of any
channel is too high or too low.
Attribute
Parameters
None

When this alarm is generated, the receive end of the laser cannot analyze signals properly.
Possible Causes
l Cause 1: A pigtail is not properly connected to an optical port on the board that reports the
alarm.
l Cause 2: The attenuation of the line is larger than the threshold or the fiber is broken.
l Cause 3: The board that reports the alarm is malfunctioning.
l Cause 4: The peer board of the board that reports the alarm is malfunctioning.
Procedure
Step 1 Check whether the receive optical power is close to the larger than the upper limit or smaller
than the lower limit. If the receive optical power is abnormal, rectify the fault by referring to the
procedure for handling the IN_PWR_LOW or IN_PWR_HIGH alarm.
Step 2 Check whether a pigtail is connected to an optical port on the board or whether the pigtail is
properly connected. If no pigtail is connected or the pigtail is not properly connected, ensure
that the pigtail is properly connected.
Step 3 If the alarm persists, the board that reports the alarm may be malfunctioning. Replace the board.

OptiX OSN 8800/6800/3800
If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module.
modules.
The board does not support pluggable Replace the malfunctioning board. Replace the
optical modules. board.
Step 4 If the alarm persists, the peer board of the board that reports the alarm may be malfunctioning.
Replace the malfunctioning board.
If ... Then ...
The board supports pluggable optical Replace the specific pluggable optical module.
modules.
The board does not support pluggable Replace the malfunctioning board. Replace the
optical modules. board.
----End
Related Information
None
4.300 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the synchronous source is changed in the
S1 mode.
Attribute
Parameters

OptiX OSN 8800/6800/3800
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 Cause 1: The fiber connection is faulty.
l Cause 2: The upstream station generates the alarm.
Procedure
l Cause 1: The fiber connection is faulty.
1. Check the fiber connector. If it is dirty, clean or replace the fiber connector. For details,
2. If the alarm persists, replace the faulty board. For details, see the Parts
Replacement.
l 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.301 SCC_LOC
Description
Loss of system control board clock. This alarm is generated when the OSC board detects that
the clock source sent by the system control board is lost.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

The NE is out of control and the OSC is interrupted.
Possible Causes
l The system control board is faulty.
l The alarm is generated during the cold reset of the system control board and is automatically
cleared after the cold reset is complete.
Procedure
Step 1 Query the reset record of the system control board.
l If the time when the alarm is cleared is consistent with the time when the system control
board is reset, the alarm may be caused by resetting the system control board. There is no
need to handle the alarm.
l If the time when the alarm is cleared is not consistent with the time that the system control
board is reset, the board may be faulty. Replace the faulty board. For details, see "Replacing
the SCC Board" in the Parts Replacement.
Step 2 If the alarm persists, the system control board may be faulty. Replace the faulty system control
board. For details, see "Replacing the SCC Board" in the Parts Replacement.
----End
Related Information
None
4.302 SEC_RADIUS_FAIL
Description
Excessive failures in radius authentication. This alarm indicates that a large number of
authentication failures occur on the NE within a short period.

OptiX OSN 8800/6800/3800
Attribute
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 expires.
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.
Step 4 Check whether the shared key between the GNAS and the radius server is correct. For example,
whether the shared key is used.
----End
Related Information
None
4.303 SERVICE_TYPE_EXCEED_LICENSE
Description
Service type exceeding the license limit. This alarm indicates that the type of configured services
exceeds the license limit.
Attribute
Major Service

OptiX OSN 8800/6800/3800
Parameters
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; however, services corresponding to the alarm
cannot be configured for the subrack where the alarm is generated.
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 on the U2000.
Step 2 If it does, 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.304 SERVICE_CAPACITY_EXCEED_LICENSE
Description
Service capacity exceeding the license limit. This alarm indicates that the service capacity
configured in a subrack exceeds the license limit.
Attribute
Major Service

OptiX OSN 8800/6800/3800
Parameters
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; however, services corresponding to the alarm
cannot be configured for the subrack where the alarm is generated.
Possible Causes
The service capacity configured in the subrack exceeds the license limit.
Procedure
Step 1 According to the alarm parameters, query the license capacity for the subrack where the alarm
is generated. 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.305 SHELF_AREA_POWER_OVER
Description
Total optical power consumption of a subrack section exceeding the threshold. This alarm is
generated when the total power consumption of the boards in a section of the subrack is higher
than or equal to the power consumption threshold for this section.
Attribute

OptiX OSN 8800/6800/3800
Parameters
Name Meaning
Parameter 1 Indicates the subrack ID.
Parameter 2 Indicates the number of the subrack section.

The total power consumption of the boards in a section of the subrack exceeds the threshold,
making the system in a dangerous state. If the system runs in this state for a long period of time,
the power supply unit of the subrack may work abnormally and a power failure may occur in
the subrack.
Possible Causes
The total power consumption of the boards in a section of the subrack is higher than or equal to
the power consumption threshold for each section.
Procedure
Step 1 Remove boards from the subrack section until the alarm is cleared. For details on subrack
sections, see section "Power Redundancy" in Product Description.
----End
Related Information
None
4.306 SPAN_LOSS_HIGH
Description
Line insertion loss being too high. This alarm is generated when the actual line insertion loss is
greater than the reference value and the difference between the actual value and the reference
value exceeds the alarm threshold.

OptiX OSN 8800/6800/3800
Attribute
Parameters
Name Meaning

If the line insertion loss is excessively high, service signals may be instable and BER may
increase. As a result, the alarm indicating excessively low path optical power may occur and the
performance may be abnormal.
Possible Causes
l The line fiber is aging.
l The line insertion loss increases.
l The alarm threshold is incorrect.
l The insertion loss of a board on the line is abnormal.
l 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 unconfigured VOAs are found,
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 plan of the live network.
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, refer
to Replace the board.
Step 5 If none of the preceding problems occurs, re-sample the reference value.
----End

OptiX OSN 8800/6800/3800
Related Information
4.307 SPAN_LOSS_LOW
Description
Line insertion loss being too low. This 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
Parameters
Name Meaning

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 decreases.
l 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 sample the reference value again.
Step 2 Check whether any VOA is not configured on the line. If unconfigured VOAs are found,
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 plan of the live network.

OptiX OSN 8800/6800/3800
Step 4 Check whether the insertion loss of the board is normal. If board replacement is necessary, refer
to Replace the board.
Step 5 If none of the preceding problems occurs, re-sample the reference value.
----End
Related Information
4.308 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
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 board is not in position.

l Cause 2: The active cross-connect board is faulty.
Procedure
l Query current alarms on the NMS. Determine the board that reports the alarm. For details,
see Product Description.
l Cause 1: The active cross-connect board is not in position.

OptiX OSN 8800/6800/3800
1. Check whether the active cross-connect board is loose. If yes, tighten the active cross-
connect board. For details, see the Installation Guide. Then, check whether the alarm
is cleared.
l Cause 2: The active cross-connect board is faulty.
1. Replace the active cross-connect board. For details, see Supporting Tasks. Then, check
1. Perform cold reset on the service board that reports the alarm by using the NMS, or
reseat the service board that reports the alarm. For the operations that are performed
on the NMS, see Supporting Tasks. 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
Supporting Tasks.
----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.
4.309 SM_BDI
Description
The SM_BDI is an alarm indicating a backward defect in SM overheads at the optical transponder
unit (ODU) layer. This alarm is generated when major alarms occur at the remote OTU and
upper layers.
Attribute
Parameters
None.

This alarm is generated only on the OTU termination NE of services in the transmit direction,
which does not affect services in the receive direction.

OptiX OSN 8800/6800/3800
Possible Causes
l Alarms occur on the remote OTU termination NE.
Procedure
Step 1 Check whether severer alarms occur on the remote OTU termination NE. If yes, clear the alarms
according to the related alarm-handling methods. Then, check whether the SM_BDI alarm is
cleared.
Step 2 If alarms at the remote end persist, perform an inloop on the local optical ports to check for
alarms. If any alarms occur, correct configurations according to the alarms.
NOTICE
Step 3 If the SM_BDI alarm persists, replace the local board.
Step 4 If the alarms at the remote end persist and the inloop test detects no abnormities on the local
----End
Related Information
Related Cases:
l MC-A37 The LWFS in the OptiX BWS 1600G Transiently Reports FEC_LOF Alarm
l MC-A56 LWF Board Reports OTU_LOF Alarm
l MC-A57 How to Clear OTU Alarms Because of Unused Ports
4.310 SM_BEI
Description
The SM_BEI is an alarm indicating a backward error in PM overheads at the optical transponder
unit (OTU) layer. This alarm is generated when SM-BIP check bit errors occur at the remote
end.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

When this alarm occurs, SM_BIP check bit errors occur on the remote OTU termination NE,
which does not affect the FEC function and performance on the local NE.
Possible Causes
l Bit errors occur on the remote OTU termination NE.
Procedure
Step 1 Check board performance on the remote OTU termination NE and clear the remote bit errors.
----End
Related Information
None.
4.311 SM_BIP8_OVER
Description
The SM_BIP8_OVER is an alarm indicating that the number of bit errors in the SM section at
the optical transponder unit (OTU) layer exceeds the threshold.
Attribute
Major Service alarm

OptiX OSN 8800/6800/3800
Parameters
None.

Possible Causes
Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF alarms.
Clear these alarms first and check whether the SM_BIP8_OVER alarm is cleared.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then, check
Step 5 Check whether the peer transmit optical power is within the permitted range. If not, replace the
line board.
----End

OptiX OSN 8800/6800/3800
Related Information
Related Cases:
l MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently Reported
on the Board
4.312 SM_BIP8_SD
Description
The SM_BIP8_SD is an alarm indicating that the signals degrade in the PM section at the optical
transponder unit (OTU) layer.
Attribute
Major Service alarm
Parameters
None.

Possible Causes
Procedure
Step 1 On the NMS, check whether severer alarms occur, for example, the R_LOS and R_LOF alarms.
Clear these alarms first and check whether the SM_BIP8_SD alarm is cleared.
Step 3 Clean the local pigtail connector and the receive optical port on the line board. Then, check

OptiX OSN 8800/6800/3800
Step 5 Check whether the peer transmit optical power is within the permitted range. If not, replace the
line board.
----End
Related Information
Related Cases:
l MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently Reported
on the Board
4.313 SM_IAE
Description
The SM_IAE is an alarm indicating an incoming alignment error (IAE) in the SM section at the
optical transponder layer (OTU). When the ODU frame is synchronously mapped into the OTU
frame, the IAE flag is set to true if a frame alignment error occurs. This alarm is generated when
the sink NE detects the IAE which indicates subframe alignment bit errors occur in the received
services.
Attribute

OptiX OSN 8800/6800/3800
Parameters
None.

When this alarm occurs, services may be unavailable.
Possible Causes
l A clock jitter event occurs in the transmit unit on the remote NE (the source of the OTU/
ODU adaption function).
l The frame offset on the termination side of the remote NE (the source of the OTU/ODU
adaption function).
l The FEC processing chip on the remote NE (the source of the OTU/ODU adaption
function).
Procedure
Step 1 Adjust the frame offset on the board system side of the remote NE (the source of the OTU/ODU
adaption function). Then, check whether the alarm is cleared.
Step 2 If the alarm persists, replace the board on the remote NE (the source of the OTU/ODU adaption
function).
----End
Related Information
None.
4.314 SM_TIM
Description
The SM_TIM is an alarm indicating a trail trace identifier (TTI) mismatch in the PM overheads
at the optical transponder unit (ODU) layer.
Attribute
Parameters
None.

OptiX OSN 8800/6800/3800

When this alarm occurs, the FEC function and services are not affected.
Possible Causes
l The SM_TTI byte expected by the local NE is incorrectly set.
l The SM_TTI byte transmitted by the remote NE is incorrectly set.
l The fiber is improperly connected.
Procedure
Step 1 Determine the expected setting of the SM_TTI byte based on actual situations.
Step 2 Check whether the SM_TTI byte expected by the board is consistent with the received SM_TTI
byte. If the settings of the expected SM_TTI byte are incorrect, modify the setting.
Step 3 If the received SM_TTI byte is incorrect, verify that the fiber connection on the local optical
port is correct.
Step 4 Verify that the setting of the SM_TTI byte transmitted in the upstream services is correct.
----End
Related Information
None.
4.315 SNCP_FAIL
Description
The SNCP_FAIL is an alarm indicating an SNCP switching failure.
Attribute
Parameters

OptiX OSN 8800/6800/3800
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.316 SO_SK_MISMATCH
Description
The SO_SK_MISMATCH is an alarm indicating that the number of timeslots is different on the
source and sink of the link capacity adjustment scheme (LCAS). This alarm is generated when
the number of upstream (or downstream) timeslots configured for the local VCTRUNK port is
inconsistent with that of downstream (or upstream) timeslots configured for the peer VCTRUNK
port.
Attribute
Parameters
None.

When the alarm occurs, services are not affected.

OptiX OSN 8800/6800/3800
NOTICE
After this alarm occurs, the intermediate timeslots deleted from the sink are added to other
VCTRUNK ports. As a result, services on the VCTRUNK ports are interrupted. Make the
number of timeslots consistent between the source and sink before you proceed.
Possible Causes
The number of timeslots is different on the source and sink of the LCAS.
NOTE
If an intermediate timeslot is deleted from the sink but the corresponding timeslot is not deleted from the
source, this alarm is reported.
If the last timeslot is deleted from the sink, but the corresponding timeslot is not deleted from the source,
this alarm is not reported.
Procedure
Step 1 View the alarm on the NMS and determine the serial number of the VCTRUNK port.
Step 2 On the NMS, check whether the number of upstream (or downstream) timeslots configured for
the local VCTRUNK port is consistent with that of downstream (or upstream) timeslots
configured for the peer VCTRUNK port. If not, add or delete timeslots based on actual
requirements to make the number of timeslots consistent. Then, check whether the alarm is
cleared.
----End
Related Information
None.
4.317 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
port and the preset one. This alarm is generated when a board detects that the received rate
mismatches the preset one.

OptiX OSN 8800/6800/3800
Attribute
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 port 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
4.318 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD is an alarm indicating that Ethernet services are shut down. This
alarm is generated when an Ethernet service is shut down due to a service loopback. This alarm
is cleared after the Ethernet service is restarted.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None.

Possible Causes
The possible cause of the SRV_SHUTDOWN_LD alarm is as follows:
l There is a loopback in the network.
Procedure
Step 1 There is a loopback in the network.
1. Query alarm information on the NMS to find out the Ethernet service that is shut down.
2. Check whether a loopback is configured on the service trail that carries the Ethernet service.
If yes, release the loopback based on network planning.
3. Restart the shutdown service and the alarm is cleared automatically.
NOTE
If the loopback is not released, the network will report the alarm again after the Ethernet service is
restarted.
----End
Related Information
None.
4.319 SSL_CERT_NOENC
Description
Certificate file of SSL not encrypted.

OptiX OSN 8800/6800/3800
Attribute
Parameters
None

If certificate files are stored in plain text, the private key of the files maybe be intercepted.
Possible Causes
The certificate file of SSL is not encrypted.
Procedure
Step 1 On the U2000, download and activate the encrypted SSL certificate file.
----End
Related Information
None
4.320 SSM_LOS
Description
This alarm indicates that the SSM quality information fails to be received. In SSM mode, this
alarm is reported when a reference source port configured in the priority table fails to obtain
valid SSM quality information within the specified period (5 seconds).
Attribute
Parameters
None

This alarm triggers switching of the reference clock source.

OptiX OSN 8800/6800/3800
Possible Causes
l The upstream NE sends invalid SSM quality information.
l In SSM mode, the NE fails to obtain valid SSM quality information.
Procedure
Step 1 On the NMS, check whether the SSM quality information is properly sent by the upstream NE.
If it is properly sent, check whether the upstream and local NEs are properly interconnected.
Step 2 The alarm is cleared when valid SSM quality information is received.
----End
Related Information
None
4.321 SSM_QL_FAILED
Description
This alarm indicates that the received SSM quality is worse than the threshold. This alarm is
generated when the SSM quality received by a reference source port configured in the priority
table is worse than the threshold.
Attribute
Parameters
None

If the alarm is generated, the NE has to choose another timing source if available or has to go
into hold-over mode.
Possible Causes
The received SSM quality is worse than the configuration of SSM quality.
Procedure
Step 1 Query the received SSM quality on the NMS. Check whether the SSM quality is correct. If it is
incorrect, check whether the master NE traces the correct upstream NE.

OptiX OSN 8800/6800/3800
Step 2 If the received SSM quality is correct, check whether the threshold is properly set based on the
network planning. If not, set the threshold again.
----End
Related Information
None
4.322 STORM_CUR_QUENUM_OVER
Description
Alarm storm. Some alarms on the system control board may be lost when the alarm queue is
full. This alarm indicates that the alarm module is in the alarm storm state.
Attribute
Minor Service
Parameters
None

Some alarms may be overwritten when there are excessive alarms. As a result, 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 current alarms is equal to
or smaller than the STORM_CUR_QUENUM_OVER alarm threshold.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.323 SUBRACK_COMM_PS
Description
ETH2 interface status. This alarm indicates that the ETH2 interface in the master subrack is in
working state when the master subrack is under inter-subrack communication protection.
Attribute
Parameters
None

An NE detects that the link between subracks is broken but communication between the subracks
is protected.
Possible Causes
l Cause 1: The ETH2 interface in the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
Procedure
l Cause 1: The ETH2 interface in the master subrack is in working state when the master
subrack is under inter-subrack communication protection.
1. If the ETH2 interface in 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, inter-subrack communication
protection automatically switches the active channel to the original working channel.
In this manner, the ETH2 interface stops working and the SUBRACK_COMM_PS
alarm is cleared.
----End
Related Information
Description.

OptiX OSN 8800/6800/3800
4.324 SUBRACK_ID_MISMATCH
Description
Mismatch of subrack IDs.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates mismatch of the logical subrack ID.

The DIP switch of the subrack ID mismatches the subrack ID saved by the NE 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 mismatches the actual subrack ID.
Procedure
Step 1 Modify the DIP switch of the AUX board or EFI1 board to the subrack ID displayed in the
statistics diode of the system control board or power off the subrack.
----End
Related Information
Description.

OptiX OSN 8800/6800/3800
4.325 SUBRACK_LOOP
Description
Subracks being looped. This alarm is generated when the cascaded subracks form a closed loop.
Attribute
Parameters
None

A network storm occurs during intra-subrack communication, which may make intra-subrack
communication unavailable.
Possible Causes
l In the master/slave subrack mode, the internal network interfaces are connected in a closed
loop.
l The AUX board is faulty, which leads to the abnormal communication.
Procedure
Step 1 Confirm the subrack cascading mode according to the network plan. If the planned subrack
cascading mode is a ring mode, set the subrack cascading mode to ring on the NMS. If the
planned subrack cascading mode is a tree mode, check cable connections between subracks and
ensure that all subracks are cascaded in a tree mode.
Step 2 Check whether the alarm is cleared. If the alarm persists, perform a warm reset or perform a
cold reset on the faulty board through the U2000.
Step 3 If the alarm persists, replace the AUX board. For details, see "Replacing the AUX Board" in the
Parts Replacement.
----End
Related Information
Description.

OptiX OSN 8800/6800/3800
4.326 SUBRACK_TYPE_MISMATCH
Description
Subrack types mismatched.
Attribute
Parameters
Name Meaning
Parameter 1 The ID of the subrack.

The alarm does not affect the existing services and the operation of the system. Services,
however, cannot be configured for the subrack that generates this alarm. If an incorrect logical
slave subrack is deleted, services will be interrupted, and can be restored after a logical slave
subrack and services are configured again. For an incorrect logical master subrack, if another
NE is created, the services traversing the original NE will be interrupted, and can be restored
after a logical master subrack and services are configured again.
Possible Causes
The type of the configured logical subrack mismatches the type of the physical subrack.
Procedure
Step 1 Determine whether the logical subrack or the physical subrack is incorrect according to the actual
network.
Step 2 If the logical subrack is incorrect,

l If the logical subrack for a non-enhanced subrack is incorrect, delete the incorrect subrack
from the U2000 and configure a correct logical subrack that is consistent with the physical
subrack.

OptiX OSN 8800/6800/3800
l If the logical subrack of an enhanced subrack is falsely configured as a non-enhanced subrack

or that of a non-enhanced subrack is falsely configured as an enhanced subrack, perform the
following operations to clear the alarm:
1. If the logical master subrack is incorrect, delete the NE database from the U2000,
perform a cold reset on the system control board, delete the NE and create one again,
and configure a correct logical master subrack that is consistent with the physical
subrack.
NOTE
When creating the NE again, select Manual Configuration in the NE configuration wizard. If you
select other modes, the NE data loading will fail because the NE is in the installation state.
2. If the logical slave subrack is incorrect, delete the incorrect subrack from the U2000
and configure a correct logical subrack that is consistent with the physical subrack.
Step 3 If the physical subrack is incorrect, replace the subrack with a correct one and configure a correct
subrack ID. For details on the operations, see Feature Description.
----End
Related Information
Description.
4.327 SUM_INPWR_HI
Description
Input optical power of multiplexed wavelengths being too high. The alarm is generated when
the input optical power of multiplexed signals exceeds the threshold.
Attribute
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.

OptiX OSN 8800/6800/3800
Possible Causes
l The output optical power of the board at the upstream station is normal and the power of
the received optical signals received by the board at the local station is excessively high.
No proper attenuation is added.
l 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 port of the board at the local station is within
the permitted range using an optical power meter. For the optical power specifications of the
specific board, see "Technical Specifications" in the Product Description. If the power is not
within the permitted 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 permitted range using the U2000. For the optical power specifications of the specific
board, see "Technical Specifications" in 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 is within the permitted range.
l If the input and output optical power of the board at the upstream station is not within the
permitted range, adjust the input optical power to a value within the permitted range. For
the optical power specifications of the specific board, see "Technical Specifications" in the
l If the input optical power of the board at the upstream station is within the permitted range
but the output optical power is not, the board at the upstream station may be faulty. Replace
the board.
----End
Related Information
None
4.328 SW_SNCP_PS
Description
The SW_SNCP_PS is an alarm indicating the SW SNCP protection switching. This alarm is
generated when the SW SNCP protection group actuates switching in which the current channel

OptiX OSN 8800/6800/3800
Attribute
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
switching. Such a command makes the current channel of the SW SNCP protection group
l Cause 2: The services of the working channel of the SW SNCP protection group are faulty.
reported.
Procedure
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.
----End
Related Information
For details, see "SW SNCP Protection" in the Feature Description.

OptiX OSN 8800/6800/3800
4.329 SW_SNCP_STA_INDI
Description
The SW_SNCP_STA_INDI is an alarm indicating the state of the Sub-Wavelength SNCP
protection group. This alarm is generated when the working or protection channel of the
protection group is faulty or the user runs an external switching command.
Attribute
Parameters

l 0x0F: Lockout
l 0x0C: SF Switch
l 0x09: SD Switch
l 0x05: WTR

l When switching is performed in the SW SNCP group, the services are transiently
interrupted.
l 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
or locked switching.
l The services of the working or protection channel of the SW SNCP group are faulty.
l The switching is in the WTR state. After the WTR time, the alarm is cleared.

OptiX OSN 8800/6800/3800
Procedure
necessary.
external switching.
1. Query whether 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 is reported on the related boards for configuring
the protection group. If it is, handle the alarm according to the corresponding handling
procedure of the alarm to restore the services of the working or protection channel.
is, after WTR Times the services are automatically switched to the working channel. The
alarm is cleared. If the attribute is Non-Revertive, set it to Revertive, and after WTR
Times 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.330 SWDL_ACTIVATED_TIMEOUT
Description
Activation timeout. This alarm is generated when the activation operation is not committed
within 120s after the activation is complete during software package loading.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

The services are not affected.
Possible Causes
The activation operation is not committed within 120 seconds after the activation is complete
during software package loading.
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 contact Huawei engineers to determine a correct software package. On the NMS,
use the correct software package to perform package loading on the board again.
NOTICE
Services may be affected if an incorrect software package is used for package loading. Therefore,
perform the procedure under guidance from Huawei engineers.
----End
Related Information
None
4.331 SWDL_AUTOMATCH_INH
Description
Automatic match inhibited. This alarm indicates 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 the board software does not match the NE
software, the system control board upgrades the software of the new board.
Attribute
Minor Process alarm
Parameters
None

OptiX OSN 8800/6800/3800

The system control board cannot automatically update the software of the board that is newly
inserted. If the software of the new board mismatches the NE software, some functions of the
NE may operate abnormally.
Possible Causes
The automatic matching switch is turned off.
Procedure
----End
Related Information
None
4.332 SWDL_BD_EXCLUDE
Description
Board being excluded during software package loading. This alarm is generated when the
software package loading of a board fails and the board is added to the exclusion list because
the board goes offline, the storage space is insufficient, or the board fails to communicate with
the system control board.
Attribute
Major Process alarm
Parameters
None

After package loading, the software of excluded boards mismatches the NE software. As a result,
services may be interrupted. Therefore, this alarm must be handled in a timely manner.
Possible Causes
l Cause 1: The board is offline.
l Cause 2: The communication between the board and the system control board is abnormal.
l Cause 3: The flash memory space on the board is insufficient.

OptiX OSN 8800/6800/3800
l Cause 4: The board is repeatedly reset after activation because of a board software fault.
Procedure
Step 1 In the DC window of the U2000, view the information about the board that is excluded during
package loading.
Step 2 Check whether the excluded board is offline. If it is, enable the board to go online again.
Step 3 Check whether any COMMUN_FAIL alarm is generated on the excluded board. If the alarm is
generated, handle the problem by referring to the alarm processing method.
Step 4 Check whether the flash memory space on the board is sufficient. If the space is insufficient,
clean up the board for more space.
Step 5 Check whether the downloaded software matches the NE software version. If they mismatch,
download the correct software again.
Step 6 If the results of the preceding items are normal, select the excluded board in the DC window,
download software again, and activate the software.
Step 7 After handling all excluded boards, the SWDL_BD_EXCLUDE alarm clears when the board
exclusion is released.
----End
Related Information
None
4.333 SWDL_CHGMNG_NOMATCH
Description
Software mismatching alarm after system control board replacement. The system re-checks
whether the board software of each board matches the NE software after the NE starts up upon
a power failure or the system control board is replaced or reset (cold). This alarm is generated
when the board software of a board mismatches the NE software.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

l When this alarm occurs, the automatic matching function for package loading is disabled.
l The version of the NE software is inconsistent with that of the system control 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 system control board.
l The system control board is replaced and the software version of the new system control
board is inconsistent with the NE software version.
Procedure
Step 1 Contact Huawei engineers to determine a correct software package. On the NMS, use the correct
software package to perform package loading on the board. In normal cases, this alarm is
automatically cleared after the package loading succeeds.
NOTICE
----End
Related Information
Related Cases:
l MC-A85 SWDL_CHGMNG_NOMATCH Alarm Is Reported
l MC-A86 Inserting, Removing, and Resetting Operations Affect NG WDM Products
l MC-A87 SWDL_CHGMNG_NOMATCH Alarm Is Reported
l MC-A221 The Board Software Fails to Automatically Match a Board After the Board is
Replaced
4.334 SWDL_COMMIT_FAIL
Description
Commit failure. This alarm is generated when the commit operation fails during software
package loading.

OptiX OSN 8800/6800/3800
Attribute
Minor Process alarm
Parameters
None

The package loading fails and the upgrade of the software version fails.
Possible Causes
During package loading, the dual-partition board fails in copying the new software from one
partition to the other.
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
NOTICE
----End
Related Information
None
4.335 SWDL_INPROCESS
Description
NE being loading packages. This alarm is generated when the NE is performing package loading
and the alarm clears after the NE finishes the commit operation.

OptiX OSN 8800/6800/3800
Attribute
Warning Process alarm
Parameters
None

The working/protection backup function of the system control 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 and
the alarm clears.
----End
Related Information
None
4.336 SWDL_PKG_NOBDSOFT
Description
Board software canceled during the loading of customized packages. This alarm is generated
when a new board cannot be matched during the loading of a customized software package
because the software for the board is not found in the customized software package.
NOTE
A customized software package is the package in which some software is added or deleted based on the actual
requirement.
NOTE
This alarm is also generated if a board is inserted when the SWDL_CHGMNG_NOMATCH alarm is reported.
Attribute
Minor Process alarm

OptiX OSN 8800/6800/3800
Parameters
None

The software version of the board is inconsistent with the NE software version. As a result, some
functions of the NE may be affected.
Possible Causes
The user uses a customized software package that contains the software information of only
customized boards.
Procedure
NOTICE
----End
Related Information
None
4.337 SWDL_PKGVER_MM
Description
Package version consistency check failure. This alarm is generated when the software version
information (similar to the file list category) of the software package is not consistent with the
actual software version information.
Attribute
Minor Process alarm

OptiX OSN 8800/6800/3800
Parameters
None

Some functions of the NE may be affected.
Possible Causes
The files of the software package are faulty and therefore the software version information of
the software package is not consistent with the actual software version information.
Procedure
Step 1 Contact Huawei engineers to handle this alarm.
----End
Related Information
None
4.338 SWDL_ROLLBACK_FAIL
Description
NE rollback failure. This alarm is generated when the rollback of any board fail during an NE
rollback.
Attribute
Minor Process alarm
Parameters
None

The NE rollback fails. The board software cannot be restored to the version before the package
loading. As a result, the board software version and the NE software version may mismatch,
affecting some functions of the NE.
Possible Causes
Certain board rollbacks fail when the NE performs the rollback.

OptiX OSN 8800/6800/3800
Procedure
NOTICE
----End
Related Information
None
4.339 SYN_BAD
Description
SYN_BAD is a synchronization source degrade alarm. 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
Parameters
Name Meaning
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.

OptiX OSN 8800/6800/3800
Name Meaning
the port in the subrack where the clock source is located.
clock.

Parameter 5 l 0x01: The frequency deviation is larger than 9.2 ppm for physical-layer
synchronization.
l 0x02: The frequency deviation detected by DSP exceeds the permitted range
for PTP synchronization.

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.
l Cause 3: The clock board that reports the alarm is faulty.
Procedure
l 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.
l Cause 1: The frequency deviation of the synchronization source exceeds the permitted
range.
1. 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.
l Cause 3: The clock board that reports the alarm is faulty.

OptiX OSN 8800/6800/3800
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.
----End
Related Information
4.340 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
Parameters
When viewing an alarm on the U2000, 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.
l 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.

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.

OptiX OSN 8800/6800/3800
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.
l Cause 2: There is a fiber cut (when a line clock source is traced).
l Cause 4: The timing board is faulty.
Procedure
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).
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. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
2. If the alarm persists, replace the clock board.
----End
Related Information
4.341 SYNC_DISABLE
Description
Automatic synchronization of the system control board being disabled. When the automatic
synchronization of the system control board is disabled, batch backup is not supported and this
alarm is generated.
Attribute
Minor Process alarm

OptiX OSN 8800/6800/3800
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. The alarm
clears automatically.
----End
Related Information
None
4.342 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
Parameters
Name Meaning
Parameter 1 Indicates the number of the subrack where the switched clock source is located.

OptiX OSN 8800/6800/3800
Name Meaning
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.
l 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

OptiX OSN 8800/6800/3800
4.343 SYNC_LOCKOFF
Description
The SYNC_LOCKOFF is an alarm indicating that the clock source in the priority list is locked.
Attribute
Parameters
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.

OptiX OSN 8800/6800/3800
Procedure
l View the SYNC_LOCKOFF alarm on the U2000, and then determine the locked clock
source according to the alarm parameters.
l 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.344 SYNC_FAIL
Description
Batch backup failure.
Attribute
Minor Process alarm
Parameters
Parameter 1 Indicates the alarm cause.
0x1f indicates that backing up the database fails.
0x20 indicates that verifying the active and standby system control board file
versions fails.
0x21 indicates that the active and standby system control boards fails to
communicate.
0x22 indicates that the data on the system control boards changes during the
database backup.

The batch backup fails and the working/protection switching is unavailable.

OptiX OSN 8800/6800/3800
Possible Causes
l The database backup fails.
l Software versions of the working board and the protection board are not consistent.
l Protection board communication is not stable or available.
l During the database backup process, the user performs configuration on a system control
board, or other users log in to the NE.
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 they are not, upgrade the software for consistency.
Step 3 If the alarm parameter is 0x22, cold reset the standby system control board to perform database
backup again.
----End
Related Information
None
4.345 SYSLOG_COMM_FAIL
Description
Failed communication between an NE and the syslog server. This alarm is generated when the
session or the connection between an NE and the syslog server is abnormal.
Attribute
Parameters
Name Meaning
Parameters 1 to 4 Indicate the address of the syslog server.
Parameter 5 Indicates the type of the fault that causes the alarm. 0x0a indicates that the
connection fails. 0x02 indicates that the session is abnormal.

OptiX OSN 8800/6800/3800

There is no impact on services and no bit error is generated, but the syslog server cannot be
found.
Possible Causes
In TCP mode, the connection between an NE and the syslog server or the session between servers
is abnormal.
Procedure
Step 1 Check whether the board is a board returned for repair. If it is, there is no need to handle the
alarm.
Step 2 Select the Start Syslog Service check box.
----End
Related Information
None
4.346 SYSPARA_CFDB_NOSAME
Description
Inconsistency between the data in the system parameter area and the CF card. The system checks
the consistency between the data on the system control board and the CF card. If they are
inconsistent, the system does not back up the data and meanwhile the system generates this
alarm. If they are consistent, the system backs up the data.
Attribute
Minor Process alarm
Parameters
None

The data in the system parameter area is inconsistent with that saved in the CF card. The data
cannot be restored from the CF card.

OptiX OSN 8800/6800/3800
Possible Causes
The data on the system control board is inconsistent with that on the CF card upon the first
backup.
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
4.347 T_LOSEX
Description
The T_LOSEX is an alarm indicating a signal loss in the service bus of the backplane. This alarm
is generated when the board detects that the service bus of the backplane is in the LOS state.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the slot ID of the selected cross-connect board.
l 0x01: the cross-connect board with a smaller slot ID

l 0x02: the cross-connect board with a greater slot ID
Parameter 2, Parameter 3 Each bit indicates status of a backplane bus. If the value of bit[0]
is 1, the first bus is faulty.

OptiX OSN 8800/6800/3800

When this alarm occurs, all services on the board are interrupted. As a result, the board cannot
work properly.
Possible Causes
l The service board is installed improperly.
l The cross-connect board is installed improperly.
l The clock source for the active and standby cross-connect boards is faulty or has poor
quality.
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting board.
Step 2 Verify that the alarm-reporting board is installed properly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next step.
Step 3 Verify that the cross-connect board is installed properly. Then, check whether the alarm is
cleared. If the alarm persists, go to the next step.
Step 4 Replace the cross-connect board. Then, check whether the alarm is cleared. If the alarm persists,
Step 5 Replace the alarm-reporting board.
----End
Related Information
None.
4.348 T_SLIP
Description
Frame slipping occur at the transmit end. This alarm is generated when the phase deviation
occurs on the transmitted service frames of the board.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

Bit errors occur in the client services, or even services are interrupted.
Possible Causes
The clock signals are not synchronous.
Procedure
Step 1 Perform a cold reset on the faulty board on the U2000 or remove the faulty board.
----End
Related Information
None
4.349 TEM_HA
Description
Laser temperature being too high. This alarm is generated when the laser temperature is higher
than the upper laser temperature threshold.
Attribute
Parameters
None

When the temperature of the tube core of the optical module is excessively high, the working
wavelengths of the optical module and services are affected.
Possible Causes
l The working temperature of the board is excessively high.
l The module performance detection circuit is faulty.

OptiX OSN 8800/6800/3800
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. Refer to Replace the board.
----End
Related Information
None
4.350 TEM_LA
Description
Laser temperature being too low. This alarm is generated when the laser temperature is lower
than the lower threshold of the laser temperature.
Attribute
Parameters
None

When the temperature of the tube core of the optical module is excessively low, the working
wavelengths of the optical module and services are affected.
Possible Causes
l Working temperature of the board is excessively low.
l The module performance detection circuit is faulty.
Procedure
Step 1 Check the board ambient temperature. If it is excessively low, increase it.
Step 2 Replace the faulty board. Refer to Replace the board.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.351 TEST_STATUS
Description
The TEST_STATUS is an alarm indicating that a board is being tested.
Attribute
Warning Processing alarm
Parameters
None.

When this alarm occurs, a test command may affect the system.
Possible Causes
A user has issued a command for the board to switch to the test state.
Procedure
Step 1 View the alarm on the NMS and determine the alarm-reporting board.
Step 2 The alarm is automatically cleared after a command is issued to end the test. However, the system
is affected. Cold resetting the board can prevent the impact on the system.
----End
Related Information
None.
4.352 THUNDERALM
Description
Lighting protection circuit failure.

OptiX OSN 8800/6800/3800
The alarm is generated when the PIU board detects a lightning protection circuit failure of the
PIU board.
Attribute
Minor Environment alarm
Parameters
Parameter 1 Indicates the board that reports the alarm. For example,
This parameter indicates the PIU1 board when the parameter value is 0x01.
This parameter indicates the PIU2 board when the parameter value is 0x02.

The surge protection performance of the system deteriorates. If the equipment is attacked by a
strong current (for example, a strong lightning stroke), the boards in the subrack may fail. As a
result, the services are interrupted.
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. Therefore, the PIU detects the failure and reports
this alarm.
Procedure
Step 1 Replace the faulty PIU board.
----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.
Related Cases:

OptiX OSN 8800/6800/3800
l MC-A99 The PMU Reports the THUNDERALM Alarm
4.353 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
Parameters
When viewing an alarm on the U2000, 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.
l 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.

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.


OptiX OSN 8800/6800/3800
Procedure
1. Check the fiber connections. Check whether there are optical port alarms, such as
R_LOS and R_LOF. If there are optical port 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. If the alarm persists, replace the service board. For details, see the Parts
Replacement.
l Cause 3: The clock is faulty.
Supporting Tasks.
----End
Related Information
4.354 TIME_LOCK_FAIL
Description
Time lock failure alarm. When the time of an NE is synchronized from the upstream, the time
lock status is locking. When the time of an NE is not locked, this alarm is reported to remind
the user of the unlock status of the NE time.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
clock.
l 0x05: The accumulated offset adjustment is larger than 500 ns within 96

Parameter 5
consecutive seconds of the detection period.

When this alarm is generated, the NE time is unlocked. As a result, the time of the slave NE
cannot trace the time of the master NE, and services are prone to bit errors. Hence, handle this
alarm in time once it is reported.
Possible Causes
There is an excessive step change in the time stamp of the NE. As a result, the NE fails to trace
the upstream time or clock source.
Procedure
Step 1 Check for the CLK_LOCK_FAIL alarm on the NMS. If the CLK_LOCK_FAIL alarm is also
reported, handle the alarm according to the specified process.
Step 2 Check whether the upstream NE is adjusting time. If the upstream NE adjusts time to a great
extent, the digital signal processor (DSP) on the local NE automatically performs adjustment
for a period. The alarm is automatically cleared after the DSP on the local NE traces the upstream
time or clock source.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.355 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.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the alarm cause when the IEEE 1588v2 port is enabled or an external
time input port is configured.
l 0x01: indicates that the frequency is in the trace mode.

l 0x02: indicates that the frequency is in the non-trace mode.

When the alarm is reported, the time between the upstream and downstream NEs cannot be
synchronous, which may affect the clock synchronization performance of the system
degradation. (For the OCS system, that 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.

l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
Procedure
l Cause 1: The priority table is not configured.

OptiX OSN 8800/6800/3800
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.
1. Check the fiber connections. Check whether there are optical port alarms, such as
R_LOS and R_LOF. If there are optical port alarms, clear the alarms first.
l Cause 3: The attributes of the packets at the upstream NE are configured incorrectly.
1. 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.
Supporting Tasks.
----End
Related Information
4.356 TR_LOC
Description
The TR_LOC is an alarm indicating a transmit reference clock loss.
Attribute
Parameters

OptiX OSN 8800/6800/3800
Name Meaning
Parameter 1 l 0x01: indicates the transmit clock fails on the clock board with a smaller slot
ID.
l 0x02: indicates that the transmit clock fails on the clock board with a greater
slot ID.
l 0x03: indicates that the transmit clock fails on the active and standby clock
boards.
If the slot ID contains two bytes, the options for parameter 1 are as follows:
l bit[0]: indicates that the clock is lost on the cross-connect board with a smaller
slot ID.
l bit[1]: indicates that the frame header is lost on the cross-connect board with
a smaller slot ID.
l bit[2]: indicates that the cross-connect board with a smaller slot ID fails.
l bit[3]: indicates that the clock is lost on the cross-connect board with a greater
slot ID.
l bit[4]: indicates that the frame header is lost on the cross-connect board with
a greater slot ID.
l bit[5]: indicates that the cross-connect board with a greater slot ID fails.
Parameter 2 l 0x01: indicates that the clock is lost on the cross-connect board with a smaller
slot ID.
l 0x02: indicates that the frame header is lost on the cross-connect board with
a smaller slot ID.
l 0x04: indicates that the bus is faulty on the cross-connect board with a smaller
slot ID.
l 0x08: indicates that the clock is lost on the cross-connect board with a greater
slot ID.
l 0x10: indicates that the frame header is lost on the cross-connect board with
a greater slot ID.
l 0x20: indicates that the bus is faulty on the cross-connect board with a greater
slot ID.

When this alarm occurs, the board functions improperly. Services will not be affected if the
standby cross-connect board is faulty. Services will be transiently interrupted during the active/
standby switchover if the active cross-connect board is faulty.
Possible Causes
l The clock bus on the cross-connect board is faulty.
l The clock board is not installed or is faulty.
l The local board has hardware faults.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Verify that the clock board is installed. Then, go to the next step.
Step 2 Check clock-board-related alarms and determine the working status of the clock board.
l If the clock board reports an alarm, clear the alarm first.
l If the clock board does not report an alarm, the board that reports the TR_LOC alarm is
faulty. Cold reset or replace the board.
----End
Related Information
None.
4.357 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating an alarm indication signal (AIS) for a lower order
VC-3 TU channel. This alarm is generated when the board detects signals in the TU channel are
all "1"s.
Attribute
Parameters
None.

When this alarm occurs, VC-3 path services are interrupted.
Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
l The peer related channel is faulty.

OptiX OSN 8800/6800/3800
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, HP_SLM, and AU_AIS. Clear
these alarms first and check whether the TU_AIS_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
NOTICE
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board. Then,
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
----End
Related Information
None.
4.358 TU_LOP_VC3
Description
The TU_LOP_VC3 is an alarm indicating a pointer loss in the lower order VC-3 TU channel.
This alarm is generated when a board detects that the TU-PTR value is invalid or NDF reverses
in eight consecutive frames.
Attribute
Parameters
None.

OptiX OSN 8800/6800/3800

When this alarm occurs, VC-3 path services are interrupted.
Possible Causes
l Severer alarms, such as R_LOS, R_LOF, or AU_AIS, occur in the system.
l The peer related channel is faulty.
Procedure
Step 1 On the NMS, check for severer alarms, such as R_LOS, R_LOF, and AU_AIS. Clear these
alarms first and check whether the TU_LOP_VC3 alarm is cleared.
Step 2 Cold reset the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
NOTICE
Step 3 Replace the alarm-reporting board and check whether the alarm is cleared. If the alarm persists,
Step 4 Check whether the cross-connect board is faulty. If yes, replace the cross-connect board. Then,
Step 5 Check whether the peer board is faulty. If yes, replace the faulty board. Then, check whether
----End
Related Information
None.
4.359 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED alarm indicates the degradation of a tunnel protection group.
This alarm is generated if the protection tunnel in an APS protection group is unavailable. The
alarm is cleared if either of the following conditions is met:
l After the protection tunnel recovers, both the working and protection tunnels are available.
l Both the working and protection tunnels are unavailable.

OptiX OSN 8800/6800/3800
Attribute
Major Service alarm
Parameters
None.

Availability of the protection group is lowered. Services may be interrupted if the protection
switching occurs.
Possible Causes
The possible cause of the TUNNEL_APS_DEGRADED alarm is as follows:
Cause 1: The protection tunnel in the APS protection group is unavailable.
Procedure
Step 1 Cause 1: The protection tunnel in the APS protection group is unavailable.
1. In APS Protection Management, determine the protection tunnel based on the information
about the APS protection group.
2. Check whether the protection tunnel reports any alarm such as
MPLS_TUNNEL_LOCV. If yes, clear the alarm. Then check whether the
TUNNEL_APS_DEGRADED alarm is cleared. If the alarm persists, go to the next step.
3. Check whether the port that corresponds to the protection tunnel is disabled. If yes, enable
the port. Check whether the alarm is cleared. If the alarm persists, go to the next step.
4. Check for fiber faults at the corresponding port, such as loose or incorrect fiber connections,
or contaminated fiber connectors. Ensure that fiber faults do not exist. Then, check whether
----End
Related Information
None.
4.360 VCTRUNK_NO_FLOW
Description
VCTRUNK port traffic alarm. This alarm is generated when there is no traffic at a VCTRUNK
port.

OptiX OSN 8800/6800/3800
Attribute
Major Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the direction in which the traffic at a VCTRUNK port is interrupted.
For example, 0x00 indicates the receive direction and 0x01 receives the transmit
direction.

None
Possible Causes
l No services are configured at the local end.
l The local services are abnormal or no packets are transmitted from the local port.
l The opposite end is abnormal or no packets are transmitted to the local port.
Procedure
Step 1 Check whether services are configured at the VCTRUNK port where the alarm is generated.
Step 2 Query alarm parameters on the U2000 and determine the traffic interruption direction. If traffic
is interrupted in the transmit direction, check whether services at the local NE are normal. If the
services at the local NE are abnormal, handle the alarm by referring to the procedure for handling
other alarms.
Step 3 Check traffic is interrupted in the receive direction, check whether an exception occurs at the
peer NE and handle the alarm accordingly.
----End
Related Information
None
4.361 VCAT_LOA

OptiX OSN 8800/6800/3800
SF64, SF64A, SFD64, SL64, SLD64, 4.361.1 VCAT_LOA (OCS)

Boards other than the SF64, SF64A, SFD64, 4.361.2 VCAT_LOA (OTN)
SLO16, or EGSH
4.361.1 VCAT_LOA (OCS)
Description
The VCAT_LOA is an alarm indicating that the delay of a multiframe times out. This alarm is
reported when the delay between the timeslots bound with a VCTRUNK port exceeds the
acceptable time of the virtual concatenation.
Attribute
Parameters
None.

When this alarm occurs, aligning the virtual concatenation delay times out during service data
transmission. As a result, the timeslots cannot form a data frame, and packet loss occur in the
services.
Possible Causes
The actual SDH network delay exceeds the limit of the virtual concatenation delay
compensation.
Procedure
Step 1 View the alarm on the NMS and determine the VCTRUNK port ID of the alarm-reporting board
according parameters 2 and 3.
Step 2 Reconfigure the timeslots of the VCTRUNK port so that they traverse the same fiber. If they
need to traverse different fibers, ensure that the distance difference of the fibers is the smallest.

OptiX OSN 8800/6800/3800
----End
Related Information
ITU-T G.709
4.361.2 VCAT_LOA (OTN)

Description
The VCAT_LOA is an alarm indicating that the delay of a multiframe times out. This alarm is
generated when the delay between the timeslots bound with a VCTRUNK port exceeds the
acceptable time of the virtual concatenation.
Attribute
Parameters
None.

When this alarm occurs, aligning the virtual concatenation delay times out during service data
transmission. As a result, the timeslots cannot form a data frame, and packet loss occur in the
services.
Possible Causes
The actual SDH network delay exceeds the limit of the virtual concatenation delay
compensation.
Procedure
Step 1 View the alarm on the NMS and determine the VCTRUNK port ID of the alarm-reporting board
according parameters 2 and 3.
Step 2 Reconfigure the timeslots of the VCTRUNK port so that they traverse the same fiber. If they
need to traverse different fibers, ensure that the distance difference of the fibers is the smallest.
----End
Related Information
ITU-T G.709

OptiX OSN 8800/6800/3800
4.362 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating that a virtual concatenation multiframe loss in
the VC-3 channel. This alarm is generated when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-3 timeslot.
Attribute
Parameters
None.

l When this alarm occurs during data transmission, services will be transiently interrupted
due to an automatic switchover performed by the link capacity adjustment scheme (LCAS).
l If the LCAS is disabled, the services are interrupted.
Possible Causes
l Bit error alarms, such as B3_EXC and B3_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the VCAT_LOM_VC3 alarm.
Step 2 On the NMS, check whether bit error alarms, such as B3_EXC_VC3 and B3_SD_VC3, are
reported on the board. If yes, clear them first and check whether the VCAT_LOM_VC3 alarm
is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the virtual
concatenation delay times out. See the method of handling the VCAT_LOA alarm to clear it.
Then, check whether the VCAT_LOM_VC3 alarm is cleared.
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.

OptiX OSN 8800/6800/3800
----End
Related Information
None.
4.363 VCAT_LOM_VC4
Description
The VCAT_LOM_VC4 is an alarm indicating that a virtual concatenation multiframe loss in
the VC-4 channel. This alarm is generated when the system detects that the multiframe indicator
(MFI) field is incorrect in the H4 byte of the VC-4 timeslot.
Attribute
Parameters
None.

l When this alarm occurs during data transmission, services will be transiently interrupted
due to an automatic switchover performed by the link capacity adjustment scheme (LCAS).
l If the LCAS is disabled, the services are interrupted.
Possible Causes
l Bit error alarms, such as BIP_EXC and BIP_SD, occur on the line.
l The virtual concatenation delay times out.
l The MFI field in the K4 byte transmitted by the peer end is incorrect.
Procedure
Step 1 View the alarm on the NMS and determine the board that reports the VCAT_LOM_VC4 alarm.
Step 2 On the NMS, check whether bit error alarms, such as BIP_EXC and BIP_SD, are reported on
the board. If yes, clear them first and check whether the VCAT_LOM_VC4 alarm is cleared.
Step 3 On the NMS, check whether the VCAT_LOA alarm is reported on the board. If yes, the virtual
concatenation delay times out. See the method of handling the VCAT_LOA alarm to clear it.
Then, check whether the VCAT_LOM_VC4 alarm is cleared.

OptiX OSN 8800/6800/3800
Step 4 If the alarm persists, check whether the board is faulty. If yes, replace the faulty board. Then,
Step 5 If the alarm persists, the MFI domain transmitted from the peer SDH NE is incorrect. Replace
the peer related board and check whether the alarm is cleared.
----End
Related Information
None.
4.364 VLAN_SNCP_PS
Description
VLAN SNCP protection switching alarm. This alarm is generated when the working or
protection channel of the protection group is faulty or the user runs an external switching
command.
Attribute
Parameters
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.
l 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
or locked switching.
l The services of the working channel or the protection channel of the VLAN SNCP group
are faulty.

OptiX OSN 8800/6800/3800
l The switching is in WTR State. After WTR Times, the alarm clears.
Procedure
switching, manual switching or locked switching, check whether the external switching
operation is necessary,
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,
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.
is, after WTR Times 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 after WTR Times 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, 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
4.365 VOADATA_MIS
Description
Mismatch of attenuation attributes. This alarm is generated when the preset attenuation value
falls beyond the adjustable attenuation range of the board.
Attribute
Parameters
None

OptiX OSN 8800/6800/3800

Possible Causes
Cause 1: Replacing an attenuation board or optical module makes the stored attenuation value
issued by the NE software fall beyond the adjustable attenuation range of the new board.
Procedure
l Cause 1: Replacing an attenuation board or optical module makes the stored attenuation
value issued by the NE software fall beyond the adjustable attenuation range of the new
board.
1. Query the adjustable range of the current actual attenuation. Reset a valid attenuation
value for the optical port channel of the board based on the queried adjustable range.
----End
Related Information
None
4.366 W_R_FAIL
Description
Writing or reading chip register failed. This alarm is generated when the read value and the
written value of the register are not consistent.
Attribute
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 properly. In this case, the services may not be received or transmitted
properly. In addition, the board may fail to query the current performance value.

OptiX OSN 8800/6800/3800
Possible Causes
Procedure
----End
Related Information
None
4.367 WAVE_ADD_ABN
Description
APE detecting abnormal wavelength adding.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the index to APE.

The APE cannot detect wavelength adding.
Possible Causes
The spectrum analysis module of the detection board obtains the actually received wavelengths
on each optical port and compares the scanned wavelengths obtained during the defining. If a
new wavelength is detected, this alarm is generated.

OptiX OSN 8800/6800/3800
Procedure
Step 1 The U2000 prompts the user to re-define the APE standard optical power curve.
----End
Related Information
4.368 WAVE_DROP_ABN
Description
APE detecting abnormal wavelength dropping.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the index of APE.

The APE cannot detect wavelength dropping.
Possible Causes
The spectrum analysis module of the detection board obtains the actually received wavelengths
on each optical port and compares the scanned wavelengths during the defining. If a wavelength
is not received, this alarm is generated.
Procedure
Step 1 The network management system prompts the user to re-define the APE standard optical power
curve.
----End

OptiX OSN 8800/6800/3800
Related Information
4.369 WAVEDATA_MIS
Description
Mismatch of wavelength or band attributes. This alarm is generated when the configured logic
wavelength or band differs with the actual wavelength or band.
Attribute
Parameters
None

Possible Causes
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
Procedure
l Cause 1: The configured logic wavelength or band differs with the actual wavelength or
band.
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.
----End
Related Information
None

OptiX OSN 8800/6800/3800
4.370 WAVELEN_OVER
Description
Wavelength crossing the threshold. This alarm is generated when the wavelength drift of the
OTU board exceeds the threshold.
Attribute
Parameters
None

The services carried by the wavelength are 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.
l The wavelength locking is mis-adjusted because the logical fiber connection is inconsistent
with the physical fiber connection.
l 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 port connecting to the OTU board monitored by
the wavelength monitoring board is within the permitted range. If it is not, the OTU board enables
the wavelength locking function to adjust the monitored wavelength. When the monitored
wavelength restores to a value within the permitted 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 they are not, modify the logical fiber connections so that the logical fiber
connections are consistent with the physical fiber connections. Refer to Checking Logical
Fibers.
Step 3 If the alarm persists, perform a cold reset on the OTU board.
----End

OptiX OSN 8800/6800/3800
Related Information
None
4.371 XC_UNSWITCH
Description
Cross-connect matrix of the board being not switched.
Attribute
Parameters
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 cross-
connect matrix configured by the NE software.
l The board is in the BIOS state, and as a result cannot be updated with the cross-connect
matrix configured by the NE software.

OptiX OSN 8800/6800/3800
Procedure
Step 1 Check whether the board that reports the alarm has communication alarms. Clear the
communication alarms if such alarms are found and check whether the XC_UNSWITCH alarm
is cleared.
Step 2 If the alarm persists, perform a 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.
----End
Related Information
None

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 5 Performance Event List
5 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 topic lists the performance events of each board.

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
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
ETH_CFM_LS Packet loss seconds of the E-Line service
ETH_CFM_SLS Severe packet loss seconds of the E-Line service
ETH_CFM_CSLS Consecutive severe packet loss seconds of the E-

Line service
ETH_CFM_UAS Unavailable seconds of the E-Line service
FEC_AFT_COR_ER After FEC Correct Errored Rate
FEC_AFT_COR_ERAVR After FEC Correct Average Errored Rate in

monitor period
FEC_AFT_CORER_FLOAT After FEC Correct Errored Rate (FLOAT)
FEC_BEF_COR_ER Before FEC Correct Errored Rate
FEC_BEF_COR_ERAVR Before FEC Correct Average Errored Rate in

monitor period
FEC_BEF_CORER_FLOAT Before FEC Correct Errored Rate (FLOAT)
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

OptiX OSN 8800/6800/3800
Name Description
FEC_TMP The total period for monitoring FEC

performance
FEC_UNCOR_BLOCK_CNT Forward Error Correction - Uncorrected Block

Count
MPLS_PW_LS Packet loss seconds of the PW service
MPLS_PW_SLS Severe packet loss seconds of the PW service
MPLS_PW_CSLS Consecutive severe packet loss seconds of the

PW service
MPLS_PW_UAS Unavailable seconds of the PW service
OSC_BBE OSC Path Background Block Error
OSC_BBER OSC Path Background Block Error Ratio
OSC_BIAES OSC Path Backward Incoming Alignment

Errored Second
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 Path Unavailable Seconds
OSC_UAS OSC Path Unavailable Seconds
5.1.2 Performance Event of Pointer Justification

This topic lists the performance events for pointer justifications.

OptiX OSN 8800/6800/3800
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
Name Description
BCVCUR Average Pump Laser Backfacet Current

Value
BCVMAX Maximum Pump Laser Backfacet Current

Value
BCVMIN Minimum Pump Laser Backfacet Current

Value
BDTEMPMAX Maximum value of a board temperature
BDTEMPMIN Minimum value of a board temperature
BDTEMPCUR Current value of a board temperature
CCVCUR Average Pump Laser Cooling Current Value
CCVMAX Maximum Pump Laser Cooling Current

Value
CCVMIN Minimum Pump Laser Cooling Current

Value
EDRPLCUR Current Laser Input Optical Power Value
EDRPLMAX Maximum Laser Input Optical Power Value
EDRPLMIN Minimum Laser Input Optical Power Value
EDTMPCUR Current Laser Temperature Value
EDTMPMAX Maximum Laser Temperature Value
EDTMPMIN Minimum Laser Temperature Value
EDTPLCUR Current Laser Output Optical Power Value

OptiX OSN 8800/6800/3800
Name Description
EDTPLMAX Maximum Laser Output Optical Power Value
EDTPLMIN Minimum Laser Output Optical Power Value
EDWCSCUR Current value of Laser working current setup
EDWCSMAX Maximum value of Laser working current

setup
EDWCSMIN Minimum value of Laser working current

setup
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
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

OptiX OSN 8800/6800/3800
Name Description
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
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
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
PEAK_LSIOPMAX Maximum peak input optical power
PEAK_LSIOPCUR Current peak input optical power
PEAK_LSIOPMIN Minimum peak input optical power
PEAK_OOPMAX Maximum peak output optical power
PEAK_OOPCUR Current peak output optical power
PEAK_OOPMIN Minimum peak output optical power
PEAK_LSTMPMAX Maximum peak laser temperature

OptiX OSN 8800/6800/3800
Name Description
PEAK_LSTMPCUR Current peak laser temperature
PEAK_LSTMPMIN Minimum peak laser temperature
PEAK_LSBIASMAX Maximum peak bias current of the laser
PEAK_LSBIASCUR Current peak bias current of the laser
PEAK_LSBIASMIN Minimum peak bias current of the laser
PMDAVG Polarization mode average dispersion
PMDMAX Polarization mode maximum dispersion
PMDMIN Polarization mode minimum dispersion
PMDCUR Polarization mode cur-value dispersion
RMIOPCUR Maximum input optical power of the Raman

amplifier
RMIOPMAX Minimum input optical power of the Raman

amplifier
RMIOPMIN Current input optical power of the Raman

amplifier
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
TDCCUR The dispersion compensation current value
TDCMAX The dispersion compensation maximum

value
TDCMIN The dispersion compensation minimum

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

OptiX OSN 8800/6800/3800
Name Description
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
AVGPHASEOFFSET Average phase offset
MAXPHASEOFFSET Maximum phase offset
MINPHASEOFFSET Minimum phase offset
VALLEY_LSIOPMAX Maximum valley input optical power
VALLEY_LSIOPCUR Current valley input optical power
VALLEY_LSIOPMIN Minimum valley input optical power
VALLEY_OOPMAX Maximum valley output optical power
VALLEY_OOPCUR Current valley output optical power
VALLEY_OOPMIN Minimum valley output optical power
VALLEY_LSTMPMAX Maximum valley laser temperature
VALLEY_LSTMPCUR Current valley laser temperature
VALLEY_LSTMPMIN Minimum valley laser temperature
VALLEY_LSBIASMAX Maximum valley bias current of the laser
VALLEY_LSBIASCUR Current valley bias current of the laser
VALLEY_LSBIASMIN Minimum valley bias current of the laser
5.1.4 Performance Event of Multiplex Section Bit Error

Lists performance event of multiplex section bit error.

OptiX OSN 8800/6800/3800
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
Name Description
RSBBE RS Background Block Error
RSCSES RS Consecutive Severely Errored Second
RSES RS Errored Second
RSOFS RS Out-of-Frame Second
RSOOF RS Out-of-Frame
RSSES RS Severely Errored Second
RSUAS RS Unavailable Second
RS_TMP The total period for monitoring performance of

regenerator section
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.

OptiX OSN 8800/6800/3800
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
HPCSES Higher order path consecutive severely errored

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
HPFECSES Higher order path far end consecutive 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
Name Description
VC3BBE VC3 block of background error
VC3ES VC3 errored second
VC3SES VC3 severely errored second
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

OptiX OSN 8800/6800/3800
Name Description
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
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
ODU0_PM_SESR ODU0 PM Section Ratio of Severely Errored

Second
ODU0_PM_TMP The total period for period performance of

ODU0 signals in the PM section
ODU0_PM_UAS ODU0 PM Section Unavailable Second

Block Error

OptiX OSN 8800/6800/3800
Name Description

Block Error


Second

Errored Second

Second

Second


Block Error

Block Error


Second

Errored Second

Second

OptiX OSN 8800/6800/3800
Name Description

Second


Block Error

Block Error


Second

Errored Second

Second

Second


Block Error

Block Error


OptiX OSN 8800/6800/3800
Name Description

Second

Errored Second

Second

Second
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
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

OptiX OSN 8800/6800/3800
Name Description
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
ODUFLEX_PM_TMP The total period for period performance of

ODUFLEX signals in the PM section
Performance Event of TCM Section
Table 5-9 Performance Event of TCM Section
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

OptiX OSN 8800/6800/3800
Name Description
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 Section Ratio of Far End

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_TMP The total period for period performance of

ODU0 signals in the TCMn section
ODU0_TCMn_UAS ODU0 TCMn Section Unavailable Second

Error

Block Error


Block Error


Second

Errored Second


OptiX OSN 8800/6800/3800
Name Description

Second

Errored Second

Second

Errored Second


Error

Block Error


Block Error


Second

Errored Second


Second

Errored Second

Second

Errored Second

OptiX OSN 8800/6800/3800
Name Description

ODU2PMBIP8 Number of bit errors in the optical channel

data unit

Error

Block Error


Block Error


Second

Errored Second


Second

Errored Second

Second

Errored Second


Error

OptiX OSN 8800/6800/3800
Name Description

Block Error


Block Error


Second

Errored Second


Second

Errored Second

Second

Errored Second
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


OptiX OSN 8800/6800/3800
Name Description
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
Name Description
OTU5G_BBE OTU5G SM Section Background Block

Error
OTU5G_BBER OTU5G SM Section Ratio of Background

Block Error
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

OptiX OSN 8800/6800/3800
Name Description
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
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

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_TMP The total period for period performance of

OTU1 signals in the SM section

OptiX OSN 8800/6800/3800
Name Description
OTU1_UAS OTU1 SM Section Unavailable Second

Block Error


Block Error


Second

Errored Second

Second

Errored Second

Second

OTU2SMBIP8 Number of bit errors in the optical channel

transport unit

Block Error


OptiX OSN 8800/6800/3800
Name Description

Block Error


Second

Errored Second

Second

Errored Second

Second


Block Error


Block Error


Second

Errored Second

OptiX OSN 8800/6800/3800
Name Description

Second

Errored Second

Second
5.1.9 Performance Event List of RMON Function

Lists the performance event of RMON function.
The Figure 5-1 shows the transmit and receive directions of RMON performance events. The
transmit and receive directions of the internal logical ports or L2 module ports of a board are
the same as the transmit and receive directions of the board.
Figure 5-1 Transmit and receive directions of RMON performance events
Receive Transmit
direction direction
Board
Client WDM or
side backplane side
Transmit Receive
direction direction
Table 5-11 RMON Performance Event List
Name Description
Drop Events (ETHDROP) 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.

OptiX OSN 8800/6800/3800
Name Description
Octets Received (RXOCTETS) The total number of octets of data (including

those in bad packets) received on the network
(excluding framing bits but including FCS
octets).
Packets Received (RXPKTS) The total number of packets (including bad

packets, broadcast packets, and multicast
packets) received.
Broadcast Packets Received The total number of good packets received

(RXBRDCAST) that were directed to the broadcast address.
Note that this does not include multicast
packets.
Multicast Packets Received (RXMULCAST) The total number of good packets received
that were directed to a multicast address. Note
that this number does not include packets
directed to the broadcast address.
FCS and Alignment Errors (ETHCRCALI) 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).
Undersize Packets Received (ETHUNDER) 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.
Oversize Packets Received (ETHOVER) The total number of packets received that
were longer than 1518 octets (excluding
Fragments (ETHFRG) The total number of packets received that

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).

OptiX OSN 8800/6800/3800
Name Description
Jabbers (ETHJAB) The total number of packets received that

were longer than 1518 octets (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).
Packets Received, 64 Octets in Length The total number of packets (including bad
(RXPKT64) packets) received that were 64 octets in length
octets).
Packets Received, 65~127 Octets in Length The total number of packets (including bad
(RXPKT65) packets) received that were between 65 and
127 octets in length inclusive (excluding
framing bits but including FCS octets).
Packets Received, 512~1023 Octets in The total number of packets (including bad
Length (RXPKT512) packets) received that were between 512 and
Packets Received, 1024~1518 Octets in The total number of packets (including bad
Packets Received, 1519~MTU Octets in The total number of packets (including bad
MTU octets in length inclusive (excluding
Packets Received and Transmitted, 64 Octets The total number of packets (including bad
in Length (PKT64) packets) received and transmitted that were
64 octets in length (excluding framing bits but
including FCS octets).

OptiX OSN 8800/6800/3800
Name Description
Packets Received and Transmitted, 65~127 The total number of packets (including bad
Octets in Length (PKT65) packets) received and transmitted that were
between 65 and 127 octets in length inclusive
octets).
between 128 and 255 octets in length
inclusive (excluding framing bits but
Packets Received and Transmitted, The total number of packets (including bad
512~1023 Octets in Length (PKT512) packets) received and transmitted that were
1024~1518 Octets in Length (PKT1024) packets) received and transmitted that were
1519~MTU Octets in Length (PKT1519) packets) received and transmitted that were
between 1519 and MTU octets in length
Good Full Frame Octets Transmitted The total number of transmitted octets of
(TXFULLBGOOD) good packets (including framing bits and FCS
octets).
Good Full Frame Octets Received The total number of received octets of good
(RXFULLBGOOD) packets (including framing bits and FCS
octets).
Good Full Frame Speed Transmitted The rate of transmitted octets of good packets
(TXGOODFULLFRAMESPEED) (including framing bits and FCS octets).
Good Full Frame Speed Received The rate of received octets of good packets
(RXGOODFULLFRAMESPEED) (including framing bits and FCS octets).
Good Packets Transmitted The total number of transmitted octets of

(VCG_TXGOODPACKETS) good packets.

OptiX OSN 8800/6800/3800
Name Description
Good Packets Received The total number of received octets of good

(VCG_RXGOODPACKETS) packets.
Full Frame Speed Transmitted The rate of octets of data (including those in
(VCG_TXSPEED) bad packets) transmitted on the network
octets).
Full Frame Speed Received The rate of octets of data (including those in
(VCG_RXSPEED) bad packets) received on the network
octets).
Packets Transmitted, 64 Octets in Length The total number of packets (including bad
(TXPKT64) packets) transmitted that were 64 octets in
length (excluding framing bits but including
FCS octets).
Packets Transmitted, 65~127 Octets in The total number of packets (including bad
Length (TXPKT65) packets) transmitted that were between 65
and 127 octets in length inclusive (excluding
Packets Transmitted, 1519~MTU Octets in The total number of packets (including bad
and MTU octets in length inclusive
octets).
Unicast Packets Received (RXUNICAST) The total number of good packets received
that were directed to a unicast address.

OptiX OSN 8800/6800/3800
Name Description
Unicast Packets Transmitted (TXUNICAST) 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.
Multicast Packets Transmitted The total number of packets that higher-level

(TXMULCAST) protocols requested be transmitted, and
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.
Broadcast Packets Transmitted The total number of packets that higher-level

(TXBRDCAST) protocols requested be transmitted, and
which were addressed to a broadcast address
at this sub-layer, including those that were
discarded or not sent.
Pause Frames Received (RXPAUSE) A count of MAC Control frames received on

this interface with an opcode indicating the
PAUSE operation.
Pause Frames Transmitted (TXPAUSE) A count of MAC Control frames transmitted

on this interface with an opcode indicating the
PAUSE operation.
Good Octets Received (RXBGOOD) The total number of octets of good packets
received on the network (excluding framing
bits but including FCS octets).
Good Octets Transmitted (TXBGOOD) The total number of octets of good packets
transmitted on the network (excluding
Bad Octets Received (RXBBAD) The total number of octets of bad packets
received on the network (excluding framing
bits but including FCS octets).
Bad Octets Transmitted (TXBBAD) The total number of octets of bad packets
transmitted on the network (excluding
Alignment Errors (ETHALI) 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.

OptiX OSN 8800/6800/3800
Name Description
FCS Errors (ETHFCS) 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.
Control Frames Received (RXCTLPKTS) A count of MAC Control frames received on

this interface with an opcode indicating the
special operation.
Control Frames Transmitted (TXCTLPKTS) A count of MAC Control frames transmitted

on this interface with an opcode indicating the
special operation.
Drop Events at Transmission Direction The total number of events in which packets
(TXETHDROP) 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.
Oversize Packets Transmitted The total number of packets transmitted that

(TXETHOVER) were longer than 1518 octets (excluding
Packets Transmitted (TXPKTS) The total number of packets (including bad

packets, broadcast packets, and multicast
packets) Transmitted.
Octets Transmitted (TXOCTETS) The total number of octets of data (including

those in bad packets) Transmitted on the
network (excluding framing bits but
Good full-frame bytes transmitted The total number of transmitted good packets,
(TFULLBGOOD) including framing bits (20 bytes) and FCS
bytes.
Good full-frame bytes received The total number of received good packets,
(RXFULLBGOOD) including framing bits (20 bytes) and FCS
bytes.
Rate of good full-frame bytes received The rate of received good packets, including
(RXGOODFULLFRAMESPEED) framing bits (20 bytes) and FCS bytes.
Rate of good full-frame bytes transmitted The rate of transmitted good packets,
(TXGOODFULLFRAMESPEED) including framing bits (20 bytes) and FCS
bytes.

OptiX OSN 8800/6800/3800
Name Description
Count of lost packets of the PW service Number of data packets transmitted at the
(MPLS_PW_FL) source number of data packets received at
the sink. This difference is detected by the
OAM mechanism.
PW packet loss ratio (MPLS_PW_FLR) (Number of data packets transmitted at the

source number of data packets received at
the sink)/number of data packets transmitted
at the source.
Bits per second transmitted on PW Bits per second transmitted at the specified
(PW_TX_BPS) PW, that is, number of actually transmitted
bytes x 8/time unit.
Packets per second transmitted on PW Packets per second transmitted at the

(PW_TX_PPS) specified PW, that is, number of actually
transmitted packets/time unit.
Count of bytes transmitted on PW Number of bytes transmitted on the specified

(PW_SNDBYTES) PW of the specified service.
Count of packets transmitted on PW Number of packets transmitted on the

(PW_SNDPKTS) specified PW of the specified service.
Bits per second received on PW Bits per second received at the specified PW,
(PW_RX_BPS) that is, number of actually received bytes x 8/
time unit.
Packets per second received on PW Packets per second received at the specified
(PW_RX_PPS) PW, that is, number of actually received
packets/time unit.
Count of bytes received on PW Number of bytes received on the specified

(PW_RCVBYTES) PW of the specified service.
Count of packets received on PW Number of packets received on the specified

(PW_RCVPKTS) PW of the specified service.
Delay of the PW service (MPLS_PW_FD) Time when a request packet is transmitted at

the PW source -time when the response
packet is received at the PW source.
Delay variation of the PW service Difference in two frame delay tests.

(MPLS_PW_FDV)
Number of reversely transmitted packets on a Number of reversely transmitted packets on a

tunnel (TUNNEL_REVERSE_SNDPKTS) designated bi-directional transit tunnel.
Number of reversely transmitted bytes on a Number of reversely transmitted bytes on a

tunnel designated bi-directional transit tunnel.
(TUNNEL_REVERSE_SNDBYTES)

OptiX OSN 8800/6800/3800
Name Description
Number of reversely received bytes on a Number of reversely received bytes on a

tunnel designated bi-directional transit tunnel.
(TUNNEL_REVERSE_RCVBYTES)
Number of reversely received packets on a Number of reversely received packets on a

tunnel (TUNNEL_REVERSE_RCVPKTS) designated bi-directional transit tunnel.
Bits per second transmitted on tunnel Bits per second transmitted on tunnel of the
(TUNNEL_TX_BPS) specified service, that is, number of actually
transmitted bytes x 8/time unit.
Packets per second transmitted on tunnel Packets per second transmitted on tunnel of
(TUNNEL_TX_PPS) the specified service, that is, number of
actually transmitted packets/time unit.
Count of bytes transmitted on tunnel Number of bytes received at the specified V-

(TUNNEL_SNDBYTES) NNI of the specified service.
Count of packets transmitted on tunnel Number of packets received at the specified

(TUNNEL_SNDPKTS) V-NNI of the specified service.
Bits per second received on tunnel Bits per second received on tunnel of the
(TUNNEL_RX_BPS) specified service, that is, number of actually
received bytes x 8/time unit.
Packets per second received on tunnel Packets per second received on tunnel of the
(TUNNEL_RX_PPS) specified service, that is, number of actually
received packets/time unit.
Count of bytes received on tunnel Number of bytes transmitted at the specified

(TUNNEL_RCVBYTES) V-NNI of the specified service.
Count of packets received on tunnel Number of packets transmitted at the

(TUNNEL_RCVPKTS) specified V-NNI of the specified service.
Count of lost packets of the tunnel service Number of data packets transmitted at the
(MPLS_TUNNEL_FL) source - number of data packets received at
the sink. This difference is detected by the
OAM mechanism.
TUNNEL packet loss ratio (Number of data packets transmitted at the

(MPLS_TUNNEL_FLR) source - number of data packets received at
the sink)/number of data packets transmitted
at the source.
Delay of the tunnel service Time when a request packet is transmitted at

(MPLS_TUNNEL_FD) the tunnel source - time when the response
packet is received at the tunnel source.
Delay variation of the tunnel service Difference in two frame delay tests.
(MPLS_TUNNEL_FDV)

OptiX OSN 8800/6800/3800
Name Description
Count of bytes transmitted at V-UNI Indicates the number of bytes transmitted at

(VUNI_SNDBYTES) V-UNI of a service.
Count of packets transmitted at V-UNI Indicates the number of packets transmitted

(VUNI_SNDPKTS) at V-UNI of a service.
Count of bytes received at V-UNI Indicates the number of bytes received at V-

(VUNI_SNDBYTES) UNI of a service.
Count of packets received at V-UNI Indicates the number of packets received on

(VUNI_RCVPKTS) a V-UNI of a service.
number of discarded E_Line service packets. Number of lost packets = Number of packets
(ETH_CFM_FL) transmitted by the source - Number of packets
received by the sink (Both numbers are
detected by the performance monitoring
scheme of OAM.).
E_Line service packet loss ratio Packet loss ratio = (Number of packets
(ETH_CFM_FLR) transmitted by the source MEP - Number of
packets received by the sink MEP)/Number
of packets transmitted by the source MEP.
E_Line service delay(ETH_CFM_FD) Frame delay = Time when the source MEP
sends a request packet - Time when the source
MEP receives the response packet.
E_Line service delay variation Frame delay variation is the difference

(ETH_CFM_FDV) between two frame delay test results.
Bits per second transmitted on the reverse Bits per second of transmitted on the reverse
tunnel (TUNNEL_REVERSE_TX_BPS) tunnel, that is, number of actually transmitted
Packets per second transmitted on the reverse Packets per second of transmitted on the
tunnel (TUNNEL_REVERSE_TX_PPS) reverse tunnel, that is, number of actually
transmitted packets/time unit.
Bits per second received on the reverse tunnel Bits per second of received on the reverse
(TUNNEL_REVERSE_RX_BPS) tunnel, that is, number of actually received
Packets per second received on the reverse Packets per second of received on the reverse
tunnel (TUNNEL_REVERSE_RX_PPS) tunnel, that is, number of actually received
packets/time unit.
Bytes matching flow classification The number of bytes that match the flow
(QOS_STRM_MATCHBYTES) classification.
Packets matching flow classification The number of packets that match the flow
(QOS_STRM_MATCHPKTS) classification.

OptiX OSN 8800/6800/3800
Name Description
Bandwidth utilization at a port in the receive Bandwidth utilization ratio = (Number of

direction(PORT_RX_BW_UTILIZATION) received bytes x 8/Monitoring period)/
Configured or actual bandwidth.
Bandwidth utilization at a port in the transmit Bandwidth utilization ratio = (Number of

direction.(PORT_TX_BW_UTILIZATION) transmitted bytes x 8/Monitoring period)/
Configured or actual bandwidth.
Received flow classifier bandwidth Bandwidth utilization of the specified

utilization (FLOW_RX_UTILIZATION) received flow classifier, that is, number of
actually received bytes x 8/time unit/
configured CAR CIR bandwidth.
Port utilization (ETHUTILIZ) The best evaluation of average network

utilization (in percentage) at the physical
layer of the port during the sampling interval.
Port bandwidth availability Port bandwidth availability.

(PORT_RX_BYTES_AVAILABILITY)
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.
Description
Number of frames with wrong CRC at the client side
Number of times of BB Credit being 0 on a client port
Number of invalid 10B code received on a client port

OptiX OSN 8800/6800/3800
Description
Number of overlong frames received on a client port
Number of class-1 frames received on the client side
Number of class-f frames received on the client side
Number of Not Operat Sequences received on a client port
Utilization of receive bandwidth on a client port
Number of bytes received at the client side
Number of Link Resets Sequences received on a client port
Number of Link Resets Response Sequences received on a client port
Number of Offline Sequences received on a client port
Number of truncated frames received on a client port
Number of Not Operat Sequences transmitted on a client port
Utilization of transmit bandwidth on a client port
Number of bytes transmitted at the client side
Number of class-1 frames transmitted on the client side
Number of class-f frames transmitted on the client side
Number of frames transmitted at the client side
Number of Link Resets Sequences transmitted on a client port
Number of Link Resets Response Sequences transmitted on a client port
Number of Offline Sequences transmitted on a client port
Number of invalid Ordered Sets received at the client side
Number of frames received at the client side
Number of link resets
Number of frames with wrong CRC received at the WAN side

OptiX OSN 8800/6800/3800
Description
Number of link interruptions at the WAN side
Number of overlong frames received at the WAN side
Number of Pause Primitive received at the WAN side
Number of Ping ACK Primitive received at the WAN side
Number of Ping Primitive received at the WAN side
Number of Resume Primitive received at the WAN side
Number of truncated frames received at the WAN side
Number of Pause Primitive transmitted at the WAN side
Number of Ping ACK Primitive transmitted at the WAN side
Number of Ping Primitive transmitted at the WAN side
Number of Resume Primitive transmitted at the WAN side
Number of invalid Ordered Sets received at the WAN side
5.2 Board Performance Event List

This topic lists the performance events of each board.
5.2.1 BPA Board Performance Event List

BCVCUR EDRPLMAX EDTPLMIN
BCVMAX EDRPLMIN EDWCSCUR
BCVMIN EDTMPCUR EDWCSMAX
CCVCUR EDTMPMAX EDWCSMIN
CCVMAX EDTMPMIN WCVCUR
CCVMIN EDTPLCUR WCVMAX
EDRPLCUR EDTPLMAX WCVMIN
5.2.2 CRPC Board Performance Event List

BCVCUR EDTPLCUR LSIOPMAX
BCVMAX EDTPLMAX LSIOPMIN

OptiX OSN 8800/6800/3800
BCVMIN EDTPLMIN LSIOPCUR
CCVCUR ENVTMPCUR WCVCUR
CCVMAX ENVTMPMAX WCVMAX
CCVMIN ENVTMPMIN WCVMIN
5.2.3 DAS1 Board Performance Event List

BCVCUR LSBIASCUR OSC_FESES
BCVMAX LSBIASMAX OSC_FESESR
BCVMIN LSBIASMIN OSC_FEUAS
CCVCUR LSIOPCUR OSC_IAES
CCVMAX LSIOPMAX OSC_SES
CCVMIN LSIOPMIN OSC_SESR
EDTMPCUR LSOOPCUR OSC_UAS
EDTMPMAX LSOOPMAX SUMIOPCUR
EDTMPMIN LSOOPMIN SUMIOPMAX
FEC_AFT_COR_ER LSTMPCUR SUMIOPMIN
FEC_AFT_COR_ERAVR LSTMPMAX SUMOOPCUR
FEC_AFT_CORER_FLOAT LSTMPMIN SUMOOPMAX
FEC_BEF_COR_ER OSC_BBE SUMOOPMIN
FEC_BEF_COR_ERAVR OSC_BBER WCVCUR
FEC_BEF_CORER_FLOAT OSC_BIAES WCVMAX
FEC_COR_0BIT_CNT OSC_ES WCVMIN
FEC_COR_1BIT_CNT OSC_FEBBE BDTEMPCUR
FEC_COR_BYTE_CNT OSC_FEBBER BDTEMPMAX
FEC_UNCOR_BLOCK_CN OSC_FEES BDTEMPMIN

T
NOTE
When working in AFEC mode, the board cannot report the FEC_COR_BYTE_CNT performance event.

OptiX OSN 8800/6800/3800
5.2.4 D40V Board Performance Event List

ICTMPCUR SUMIOPCUR BDTEMPCUR
ICTMPMAX SUMIOPMAX BDTEMPMAX
ICTMPMIN SUMIOPMIN BDTEMPMIN
5.2.5 D40 Board Performance Event List

TN12D40
ICCLCCUR ICTMPMAX SUMIOPMIN
ICCLCMAX ICTMPMIN BDTEMPCUR
ICCLCMIN SUMIOPCUR BDTEMPMAX
ICTMPCUR SUMIOPMAX BDTEMPMIN
TN11D40
ICCLCCUR ICTMPMAX SUMIOPMIN
ICCLCMIN SUMIOPCUR BDTEMPMAX
ICTMPCUR SUMIOPMAX BDTEMPMIN
5.2.6 DCP Board Performance Event List

LSIOPCUR LSIOPMIN BDTEMPMAX
LSIOPMAX BDTEMPCUR BDTEMPMIN
5.2.7 EAS2 Board Performance Event List

HPBBE HPUAS LSOOPMIN
HPCSES LSBIASCUR LSTMPCUR
HPES LSBIASMAX LSTMPMAX
HPFEBBE LSBIASMIN LSTMPMIN

OptiX OSN 8800/6800/3800
HPFECSES LSIOPCUR BDTEMPCUR
HPFEES LSIOPMAX BDTEMPMAX
HPFESES LSIOPMIN BDTEMPMIN
HPFEUAS LSOOPCUR
HPSES LSOOPMAX
5.2.8 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 BDTEMPCUR
HPUAS LSTMPMIN BDTEMPMAX
LSBIASCUR VC3BBE BDTEMPMIN
LSBIASMAX VC3CSES
RMON Performance Event List
Broadcast Packets Multicast Packets Received Packets Received(64 Octets in

Transmitted Length)
Broadcast Packets Multicast Packets Transmitted Packets Received(65~127

Received Octets in Length)
Control Frames Octets Received Packets Transmitted

Received
Control Frames Octets Transmitted Packets Transmitted

Transmitted (1024~1518 Octets in Length)
Drop Events Oversize Packets Received Packets Transmitted(128~255

Octets in Length)

OptiX OSN 8800/6800/3800
FCS Errors Packets Received Packets Transmitted(256~511

Octets in Length)
Fragments Packets Received and Transmitted Packets Transmitted

(1024~1518 Octets in Length) (512~1023 Octets in Length)
Full Frame Speed Packets Received and Transmitted Packets Transmitted(64 Octets
Received (128~255 Octets in Length) in Length)
Full Frame Speed Packets Received and Transmitted Packets Transmitted(65~127

Transmitted (256~511 Octets in Length) Octets in Length)
Good Full Frame Packets Received and Transmitted Pause Frames Transmitted
Octets Received (512~1023 Octets in Length)
Good Full Frame Packets Received and Transmitted Pause Frames Received
Octets Transmitted (64 Octets in Length)
Good Full Frame Packets Received and Transmitted Undersize Packets Received
Speed Received (65~127 Octets in Length)
Good Full Frame Packets Received(1024~1518 Octets Unicast Packets Transmitted

Speed Transmitted in Length)
Good Packets Packets Received(128~255 Octets in Unicast Packets Received

Received Length)
Good Packets Packets Received(256~511 Octets in

Transmitted Length)
Jabbers Packets Received(512~1023 Octets

in Length)
5.2.9 ECOM Board Performance Event List

LSBIASCUR LSIOPMIN LSTMPMAX
LSBIASMAX LSOOPCUR LSTMPMIN
LSBIASMIN LSOOPMAX BDTEMPCUR
LSIOPCUR LSOOPMIN BDTEMPMAX
LSIOPMAX LSTMPCUR BDTEMPMIN
Undersize Packets
Broadcast Packets Received Multicast Packets Received Received
Fragments Jabbers Unicast Packets Received

OptiX OSN 8800/6800/3800
Unicast Packets Transmitted Multicast Packets Broadcast Packets

Transmitted Transmitted
Pause Frames Received Pause Frames Transmitted Good Octets Received
Good Octets Transmitted Bad Octets Received FCS Errors
Oversize Packets Transmitted
5.2.10 ELQX Board Performance Event List

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 ODU1_TCMn_FESESR OTU2_BBER

T
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

OptiX OSN 8800/6800/3800
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 BDTEMPCUR
ODU1_PM_FESESR ODU2_TCMn_BIAES BDTEMPMAX
ODU1_PM_FEUAS ODU2_TCMn_ES BDTEMPMIN
ODU1_PM_SES ODU2_TCMn_FEBBE
ODU1_PM_SESR ODU2_TCMn_FEBBER
NOTE
TCM6.
NOTE
Packets Received (128~255

Octets Received Octets in Length) Unicast Packets Received
Packets Received Packets Received (256~511 Unicast Packets Transmitted

Octets in Length)
Broadcast Packets Packets Received (512~1023 Multicast Packets Transmitted

Multicast Packets Packets Received (1024~1518 Broadcast Packets Transmitted

Undersize Packets Packets Transmitted (64 Pause Frames Received

Oversize Packets Packets Transmitted (65~127 Pause Frames Transmitted

Fragments Packets Transmitted (128~255 Alignment Errors

Octets in Length)
Jabbers Packets Transmitted (256~511 FCS Errors

Octets in Length)

OptiX OSN 8800/6800/3800
Packets Received (64 Packets Transmitted Packets Transmitted

Octets in Length) (512~1023 Octets in Length)
Packets Received Packets Transmitted Octets Transmitted

(65~127 Octets in (1024~1518 Octets in Length)
Length)
5.2.11 ENQ2 Board Performance Event List

TN54ENQ2(STND)
BDTEMPCUR BDTEMPMAX BDTEMPMIN
TN54ENQ2
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
FEC_COR_1BIT_CNT ODU1_TCMn_FEBBE ODU2_TCMn_FEUAS
FEC_COR_BYTE_CNT ODU1_TCMn_FEBBER ODU2_TCMn_IAES
FEC_UNCOR_BLOCK_CN ODU1_TCMn_FEES ODU2_TCMn_SES

T
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

OptiX OSN 8800/6800/3800
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 BDTEMPCUR
ODU1_PM_FEES ODU2_PM_SESR BDTEMPMAX
ODU1_PM_FESES ODU2_PM_UAS BDTEMPMIN
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
NOTE
5.2.12 EG16 Board Performance Event List

TN54EG16
BDTEMPCUR MPLS_PW_LS RPLMIN
BDTEMPMAX MPLS_PW_SLS TLBCUR
BDTEMPMIN MPLS_PW_UAS TLBMAX
ETH_CFM_CSLS OSPITMPCUR TLBMIN
ETH_CFM_LS OSPITMPMAX TPLCUR
ETH_CFM_SLS OSPITMPMIN TPLMAX
ETH_CFM_UAS RPLCUR TPLMIN
MPLS_PW_CSLS RPLMAX
Count of bytes transmitted at Good full-frame bytes

FCS Errors V-UNI received

OptiX OSN 8800/6800/3800
Count of lost packets of Count of packets transmitted at Rate of good full-frame bytes
the PW service V-UNI received
Count of bytes received at V-

PW packet loss ratio UNI Control Frames Received
Bits per second Number of discarded E_Line Bandwidth utilization at a port

transmitted on PW service packets. in the receive direction
Packets Received and

Packets per second E_Line service packet loss Transmitted, 64 Octets in
transmitted on PW ratio Length

Count of bytes transmitted Transmitted, 65~127 Octets in
on PW E_Line service delay Length

Count of packets Transmitted, 128~255 Octets
transmitted on PW E_Line service delay variation in Length

Bits per second transmitted on Transmitted, 256~511 Octets
PW availability the reverse tunnel in Length

Bits per second received Packets per second transmitted Transmitted, 512~1023 Octets
on PW on the reverse tunnel in Length

Packets per second Bits per second received on the Transmitted, 1024~1518
received on PW reverse tunnel Octets in Length

Count of bytes received on Packets per second received on Transmitted, 1519~MTU
PW the reverse tunnel Octets in Length
Count of packets received Good full-frame bytes

on PW transmitted Pause Frames Transmitted
Rate of good full-frame bytes

Delay of the PW service transmitted Packets Received
Delay variation of the PW Packets Received, 128~255

service Control Frames Transmitted Octets in Length
Number of reversely
transmitted packets on a Bandwidth utilization at a port Packets Received, 256~511
tunnel in the transmit direction. Octets in Length
Number of reversely
transmitted bytes on a Packets Received, 512~1023
tunnel Pause Frames Received Octets in Length

OptiX OSN 8800/6800/3800
Number of reversely Packets Received, 1024~1518

received bytes on a tunnel Packets Transmitted Octets in Length
Number of reversely
received packets on a Packets Transmitted, 64 Packets Received, 1519~MTU
tunnel Octets in Length Octets in Length
Bits per second Packets Transmitted, 65~127 Packets Transmitted,

transmitted on tunnel Octets in Length 1519~MTU Octets in Length
Packets per second Packets Transmitted, 128~255 Packets Transmitted,

transmitted on tunnel Octets in Length 1024~1518 Octets in Length
Count of bytes transmitted Packets Transmitted, 256~511

on tunnel Octets in Length Unicast Packets Received
Count of packets Packets Transmitted,

transmitted on tunnel 512~1023 Octets in Length Octets Received
Bits per second received Packets Received, 64 Octets in

on tunnel Length Broadcast Packets Received
Packets per second Packets Received, 65~127

received on tunnel Octets in Length Fragments
Count of bytes received on

tunnel Unicast Packets Transmitted Multicast Packets Received
Count of packets received

on tunnel Octets Transmitted Undersize Packets Received
Count of lost packets of Broadcast Packets

the tunnel service Transmitted Oversize Packets Received
Tunnel packet loss ratio Multicast Packets Transmitted Jabbers
Received flow classifier

Delay of the tunnel service Oversize Packets Transmitted bandwidth utilization
Delay variation of the Bytes matching flow

tunnel service classification Port utilization
Count of packets received Packets matching flow

at V-UNI classification Port bandwidth availability
5.2.13 EX2 Board Performance Event List

BDTEMPCUR MPLS_PW_LS RPLMIN
BDTEMPMAX MPLS_PW_SLS TLBCUR
BDTEMPMIN MPLS_PW_UAS TLBMAX

OptiX OSN 8800/6800/3800
ETH_CFM_CSLS OSPITMPCUR TLBMIN
ETH_CFM_LS OSPITMPMAX TPLCUR
ETH_CFM_SLS OSPITMPMIN TPLMAX
ETH_CFM_UAS RPLCUR TPLMIN
MPLS_PW_CSLS RPLMAX











OptiX OSN 8800/6800/3800



Number of reversely
Number of reversely

Number of reversely











OptiX OSN 8800/6800/3800


5.2.14 FIU Board Performance Event List

TN11FIU/TN12FIU
SUMIOPCUR SUMIOPMIN BDTEMPMAX
SUMIOPMAX BDTEMPCUR BDTEMPMIN
TN14FIU
RMIOPCUR RMIOPMAX RMIOPMIN
5.2.15 HSC1 Board Performance Event List

TN11HSC1
CRC4BBE LSBIASCUR LSIOPMIN
CRC4ES LSBIASMAX LSOOPCUR
CRC4FEBBE LSBIASMIN LSOOPMAX
CRC4FEES LSCLCCUR LSOOPMIN
CRC4FESES LSCLCMAX BDTEMPCUR
CRC4FEUAS LSCLCMIN BDTEMPMAX
CRC4SES LSIOPCUR BDTEMPMIN
CRC4UAS LSIOPMAX
5.2.16 HBA Board Performance Event List

BCVCUR EDTMPMAX SUMOOPMIN
BCVMAX EDTMPMIN WCVCUR

OptiX OSN 8800/6800/3800
BCVMIN SUMIOPCUR WCVMAX
CCVCUR SUMIOPMAX WCVMIN
CCVMAX SUMIOPMIN BDTEMPCUR
CCVMIN SUMOOPCUR BDTEMPMAX
EDTMPCUR SUMOOPMAX BDTEMPMIN
5.2.17 ITL Board Performance Event List

5.2.18 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 ODU5G_PM_FEUAS OTU5G_FEES

T
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

OptiX OSN 8800/6800/3800
LSOOPMAX ODU5G_TCMn_FESES RSOFS
LSOOPMIN ODU5G_TCMn_FESESR RSSES
LSTMPCUR ODU5G_TCMn_FEUAS RSUAS
LSTMPMAX ODU5G_TCMn_IAES BDTEMPCUR
LSTMPMIN ODU5G_TCMn_SES BDTEMPMAX
ODU5G_PM_BBE ODU5G_TCMn_SESR BDTEMPMIN
NOTE
TCM6.
NOTE
Octets Received Packets Received Broadcast Packets Received
Multicast Packets Received Undersize Packets Oversize Packets Received

Received
Fragments Jabbers Packets Received and

Transmitted (64 Octets in
Length)
Packets Received and Packets Received and Packets Received and

Transmitted (65~127 Octets Transmitted (128~255 Transmitted (256~511 Octets
in Length) Octets in Length) in Length)
Packets Received and Packets Received and Unicast Packets Received

Transmitted (512~1023 Transmitted (1024~1518
Octets in Length) Octets in Length)
Multicast Packets Broadcast Packets Pause Frames Received

Pause Frames Transmitted Alignment Errors FCS Errors
Control Frames Received Control Frames Oversize Packets Transmitted

Transmitted
Packets Transmitted Octets Transmitted
5.2.19 LDGD Board Performance Event List

FEC_AFT_COR_ER MSFEES ODU1_TCMn_SES

OptiX OSN 8800/6800/3800
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 ODU1_PM_ES OTU1_FEBBE

NT
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
LSTMPCUR ODU1_TCMn_ES RSOFS
LSTMPMAX ODU1_TCMn_FEBBE RSSES
LSTMPMIN ODU1_TCMn_FEBBER RSUAS
MSBBE ODU1_TCMn_FEES BDTEMPCUR
MSCSES ODU1_TCMn_FESES BDTEMPMAX
MSES ODU1_TCMn_FESESR BDTEMPMIN
MSFEBBE ODU1_TCMn_FEUAS
MSFECSES ODU1_TCMn_IAES
NOTE
TCM6.

OptiX OSN 8800/6800/3800
NOTE
Drop Events Broadcast Packets Received Multicast Packets Received
Undersize Packets Received Oversize Packets Received Fragments
Jabbers Packets Received (64 Octets Packets Received (65~127

in Length) Octets in Length)
Packets Received (128~255 Packets Received (256~511 Packets Received (512~1023

Octets in Length) Octets in Length) Octets in Length)
Packets Received Packets Received Packets Transmitted (64

(1024~1518 Octets in (1519~MTU Octets in Octets in Length)
Length) Length)
Packets Transmitted Packets Transmitted Packets Transmitted

(65~127 Octets in Length) (128~255 Octets in Length) (256~511 Octets in Length)

(512~1023 Octets in Length) (1024~1518 Octets in (1519~MTU Octets in
Length) Length)
Unicast Packets Received Unicast Packets Transmitted Multicast Packets

Transmitted
Broadcast Packets Pause Frames Received Pause Frames Transmitted

Transmitted
Good Octets Received Good Octets Transmitted Bad Octets Received
Bad Octets Transmitted FCS Errors
5.2.20 LDGS Board Performance Event List

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 ODU1_PM_ES OTU1_FEBBE

NT

OptiX OSN 8800/6800/3800
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
LSTMPCUR ODU1_TCMn_ES RSOFS
LSTMPMAX ODU1_TCMn_FEBBE RSSES
LSTMPMIN ODU1_TCMn_FEBBER RSUAS
MSBBE ODU1_TCMn_FEES BDTEMPCUR
MSCSES ODU1_TCMn_FESES BDTEMPMAX
MSES ODU1_TCMn_FESESR BDTEMPMIN
MSFEBBE ODU1_TCMn_FEUAS
MSFECSES ODU1_TCMn_IAES
NOTE
TCM6.
NOTE


OptiX OSN 8800/6800/3800


Length) Length)


Length) Length)

Transmitted

Transmitted
5.2.21 LDM Board Performance Event List

FEC_AFT_COR_ER ODU1_PM_ES OTU1_BBE
FEC_AFT_COR_ERAVR ODU1_PM_FEBBE OTU1_BBER
FEC_AFT_CORER_FLOAT ODU1_PM_FEBBER OTU1_BIAES
FEC_BEF_COR_ER ODU1_PM_FEES OTU1_ES
FEC_BEF_COR_ERAVR ODU1_PM_FESES OTU1_FEBBE
FEC_BEF_CORER_FLOAT ODU1_PM_FESESR OTU1_FEBBER
FEC_COR_0BIT_CNT ODU1_PM_FEUAS OTU1_FEES
FEC_COR_1BIT_CNT ODU1_PM_SES OTU1_FESES
FEC_COR_BYTE_CNT ODU1_PM_SESR OTU1_FESESR
FEC_UNCOR_BLOCK_CNT ODU1_PM_UAS OTU1_FEUAS
LSBIASCUR ODU1_TCMn_BBE OTU1_IAES
LSBIASMAX ODU1_TCMn_BBER OTU1_SES
LSBIASMIN ODU1_TCMn_BIAES OTU1_SESR
LSIOPCUR ODU1_TCMn_ES OTU1_UAS
LSIOPMAX ODU1_TCMn_FEBBE RSBBE

OptiX OSN 8800/6800/3800
LSIOPMIN ODU1_TCMn_FEBBER RSCSES
LSOOPCUR ODU1_TCMn_FEES RSES
LSOOPMAX ODU1_TCMn_FESES RSSES
LSOOPMIN ODU1_TCMn_FESESR RSOFS
LSTMPCUR ODU1_TCMn_FEUAS RSUAS
LSTMPMAX ODU1_TCMn_IAES BDTEMPCUR
LSTMPMIN ODU1_TCMn_SES BDTEMPMAX
ODU1_PM_BBE ODU1_TCMn_SESR BDTEMPMIN
ODU1_PM_BBER ODU1_TCMn_UAS
NOTE
TCM6.
NOTE
Packets Received
(1024~1518 Octets in Multicast Packets
Broadcast Packets Received Length) Transmitted
Multicast Packets Received Packets Received Broadcast Packets

(1519~MTU Octets in Transmitted
Length)
Undersize Packets Received Packets Transmitted (64 Pause Frames Received

Octets in Length)
Oversize Packets Received Packets Transmitted Pause Frames Transmitted

(65~127 Octets in Length)
Fragments Packets Transmitted Good Octets Received

Jabbers Packets Transmitted Good Octets Transmitted

Packets Received (64 Octets in Packets Transmitted Bad Octets Received

Length) (512~1023 Octets in Length)
Packets Received (65~127 Packets Transmitted Bad Octets Transmitted

Octets in Length) (1024~1518 Octets in
Length)

OptiX OSN 8800/6800/3800
Packets Received (128~255 Packets Transmitted Alignment Errors

Octets in Length) (1519~MTU Octets in
Length)
Packets Received (256~511 Unicast Packets Received Drop Events at

Octets in Length) Transmission Direction
Packets Received (512~1023 Unicast Packets Transmitted Oversize Packets

Octets in Length) Transmitted
5.2.22 LDMD 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
LSOOPMIN ODU1_TCMn_FESESR RSUAS
LSTMPCUR ODU1_TCMn_FEUAS BDTEMPCUR
LSTMPMAX ODU1_TCMn_IAES BDTEMPMAX

OptiX OSN 8800/6800/3800
LSTMPMIN ODU1_TCMn_SES BDTEMPMIN
ODU1_PM_BBE ODU1_TCMn_SESR
NOTE
TCM6.
NOTE
Packets Received

Length)

Octets in Length)





Length)

Length)



OptiX OSN 8800/6800/3800
5.2.23 LDMS Board Performance Event List

FEC_UNCOR_BLOCK_CNT ODU1_PM_FEUAS OTU1_FEES
NOTE
TCM6.
NOTE

OptiX OSN 8800/6800/3800
Packets Received

Length)

Octets in Length)





Length)

Length)


5.2.24 LDX Board Performance Event List

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

OptiX OSN 8800/6800/3800
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 BDTEMPCUR
LSTMPCUR ODU2_TCMn_IAES BDTEMPMAX
LSTMPMAX ODU2_TCMn_SES BDTEMPMIN
LSTMPMIN ODU2_TCMn_SESR
NOTE
Packets Transmitted(128~255
Alignment Errors Oversize Packets Received Octets in Length)
Broadcast Packets Packets Received Packets Transmitted(256~511

Transmitted Octets in Length)
Broadcast Packets Packets Received(1024~1518 Packets Transmitted(512~1023

Received Octets in Length) Octets in Length)
FCS Errors Packets Received(128~255 Packets Transmitted(64 Octets in

Octets in Length) Length)
Fragments Packets Received(256~511 Packets Transmitted(65~127


OptiX OSN 8800/6800/3800
Jabbers Packets Received(512~1023 Pause Frames Transmitted

Octets in Length)
Multicast Packets Packets Received(64 Octets in Pause Frames Received

Received Length)
Multicast Packets Packets Received(65~127 Octets Undersize Packets Received

Transmitted in Length)
Octets Received Packets Transmitted Unicast Packets Transmitted
Octets Transmitted Packets Transmitted(1024~1518 Unicast Packets Received

Octets in Length)
5.2.25 LEM24 Board Performance Event List

FEC_AFT_CORER_FLOAT ODU2_PM_BBER ODU2_TCMn_UAS
FEC_BEF_CORER_FLOAT ODU2_PM_FEBBE OTU2_BBER
FEC_BEF_COR_ER ODU2_PM_FEBBER OTU2_BIAES
FEC_UNCOR_BLOCK_CN ODU2_PM_FEUAS OTU2_FEES

T

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE

Received

Length)


Unicast Packets Transmitted Multicast Packets Broadcast Packets Transmitted

Transmitted
Pause Frames Received Pause Frames Transmitted FCS Errors

Transmitted
Packets Transmitted Octets Transmitted Collisions
Good Full Frame Octets Good Full Frame Octets Good Full Frame Speed
Received Transmitted Transmitted
Good Full Frame Speed Drop Events Packets Received(64 Octets in

Received Length)
Packets Received(65~127 Packets Received(128~255 Packets Received(256~511


OptiX OSN 8800/6800/3800
Packets Received(512~1023 Packets Received Packets Transmitted(64 Octets

Octets in Length) (1024~1518 Octets in in Length)
Length)
Packets Transmitted(65~127 Packets Transmitted Packets Transmitted(256~511

Octets in Length) (128~255 Octets in Length) Octets in Length)
Packets Transmitted Packets Transmitted

(512~1023 Octets in Length) (1024~1518 Octets in
Length)
5.2.26 LEX4 Board Performance Event List

FEC_AFT_CORER_FLOAT ODU2_PM_BBER ODU2_TCMn_UAS
FEC_BEF_CORER_FLOAT ODU2_PM_FEBBE OTU2_BBER
FEC_UNCOR_BLOCK_CN ODU2_PM_FEUAS OTU2_FEES

T

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE

Received

Length)


Unicast Packets Transmitted Multicast Packets Broadcast Packets Transmitted

Transmitted
Pause Frames Received Pause Frames Transmitted FCS Errors

Transmitted
Packets Transmitted Octets Transmitted Collisions
Good Full Frame Octets Good Full Frame Octets Good Full Frame Speed
Received Transmitted Transmitted
Good Full Frame Speed Drop Events Packets Received(64 Octets in

Received Length)
Packets Received(65~127 Packets Received(128~255 Packets Received(256~511

Packets Received(512~1023 Packets Received Packets Transmitted(64 Octets

Octets in Length) (1024~1518 Octets in in Length)
Length)

OptiX OSN 8800/6800/3800
Packets Transmitted(65~127 Packets Transmitted Packets Transmitted(256~511

Octets in Length) (128~255 Octets in Length) Octets in Length)
Packets Transmitted Packets Transmitted

(512~1023 Octets in Length) (1024~1518 Octets in
Length)
5.2.27 LOA Board Performance Event List

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
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

OptiX OSN 8800/6800/3800
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
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 BDTEMPCUR
ODU1_PM_FESESR ODUFLEX_PM_BBER BDTEMPMAX
ODU1_PM_FEUAS ODUFLEX_PM_ES BDTEMPMIN
NOTE
TCM6.
NOTE

OptiX OSN 8800/6800/3800
5.2.28 LOG Board Performance Event List

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 OTU2_BBE
FEC_BEF_CORER_FLOAT ODU2_PM_FEBBER OTU2_BBER
FEC_COR_0BIT_CNT ODU2_PM_FEES OTU2_BIAES
FEC_COR_1BIT_CNT ODU2_PM_FESES OTU2_ES
FEC_COR_BYTE_CNT ODU2_PM_FESESR OTU2_FEBBE
FEC_UNCOR_BLOCK_CNT ODU2_PM_FEUAS OTU2_FEBBER
LSBIASCUR ODU2_PM_SES OTU2_FEES
LSBIASMAX ODU2_PM_SESR OTU2_FESES
LSBIASMIN ODU2_PM_UAS OTU2_FESESR
LSCLCCUR ODU2_TCMn_BBE OTU2_FEUAS
LSCLCMAX ODU2_TCMn_BBER OTU2_IAES
LSCLCMIN ODU2_TCMn_BIAES OTU2_SES
LSIOPCUR ODU2_TCMn_ES OTU2_SESR
LSIOPMAX ODU2_TCMn_FEBBE OTU2_UAS
LSIOPMIN ODU2_TCMn_FEBBER BDTEMPCUR
LSOOPCUR ODU2_TCMn_FEES BDTEMPMAX
LSOOPMAX ODU2_TCMn_FESES BDTEMPMIN
LSOOPMIN ODU2_TCMn_FESESR
LSTMPCUR ODU2_TCMn_FEUAS
NOTE
TCM6.
NOTE

OptiX OSN 8800/6800/3800

Packets Received (128~255 Packets Received (256~511 Packets Received

Octets in Length) Octets in Length) (512~1023 Octets in
Length)
Packets Received (1024~1518 Packets Received Packets Transmitted (64

Octets in Length) (1519~MTU Octets in Octets in Length)
Length)
Packets Transmitted (65~127 Packets Transmitted Packets Transmitted

Octets in Length) (128~255 Octets in Length) (256~511 Octets in Length)

Length) Length)

Transmitted

Transmitted
NOTE
In the GFP-T mode, the TN11LOG board does not support the RMON performance event.
5.2.29 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

OptiX OSN 8800/6800/3800
FEC_COR_BYTE_CNT ODU2_PM_FESES OTU2_ES
FEC_UNCOR_BLOCK_CNT ODU2_PM_FESESR OTU2_FEBBE
LSBIASCUR ODU2_PM_FEUAS OTU2_FEBBER
LSBIASMAX ODU2_PM_SES OTU2_FEES
LSBIASMIN 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 BDTEMPCUR
LSOOPMAX ODU2_TCMn_FEES BDTEMPMAX
LSOOPMIN ODU2_TCMn_FESES BDTEMPMIN
LSTMPCUR ODU2_TCMn_FESESR
NOTE
TCM6.
NOTE
Multicast Packets
Drop Events Broadcast Packets Received Received


Length)

Length)

OptiX OSN 8800/6800/3800

Octets in Length) (128~255 Octets in Length) (256~511 Octets in
Length)

Length) Length)

Transmitted
Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted
Bad Octets Transmitted FCS Errors Drop Events at

Transmission Direction
Oversize Packets Transmitted
FC Performance Event List
FC_Client_RxOLSPrim_
CLIENT_CRC_ERR Cnt LINKTST_CNT
FC_Client_CreditZero_Cnt FC_Client_Truncated FC_Wsys_Crc_Err_Cnt

FrmCnt_sum
FC_Client_Invld_10BCode_ FC_Client_Tx_NOS_Cnt FC_Wsys_LinkDown_Cnt

Cnt
CLIENT_RXBYTECNT_S FC_Client_Tx_Utilization FC_Wsys_OverLongFrm_Su

UM m
CLIENT_RXFRMCNT_C1 CLIENT_TXBYTECNT_ FC_Wsys_Rx_PausePrim_Cn

SUM t
CLIENT_RXFRMCNT_C2 CLIENT_TXFRMCNT_C FC_Wsys_Rx_PingAckPrim_

1 Cnt
CLIENT_RXFRMCNT_C3 CLIENT_TXFRMCNT_C FC_Wsys_Rx_PingPrim_Cnt

2
CLIENT_RXFRMCNT_C4 CLIENT_TXFRMCNT_C FC_Wsys_Rx_ResumePrim_

3 Cnt
CLIENT_RXFRMCNT_CF CLIENT_TXFRMCNT_C FC_Wsys_Truncated

4 FrmCnt_sum
CLIENT_RXFRMCNT_SU CLIENT_TXFRMCNT_C FC_Wsys_Tx_PausePrim_Cn

M F t

OptiX OSN 8800/6800/3800
FC_Client_Rx_NOS_Cnt CLIENT_TXFRMCNT_S FC_Wsys_Tx_PingAckPrim_

UM Cnt
FC_Client_Rx_Utilization CLIENT_UNSUPOS_CN FC_Wsys_Tx_PingPrim_Cnt

T
FC_Client_OverLongFrm_S FC_Client_TxLRPrim_Cn FC_Wsys_Tx_ResumePrim_

um t Cnt
FC_Client_RxLRPrim_Cnt FC_Client_TxLRRPrim_ FC_Wsys_unsupos_cnt

Cnt
FC_Client_RxLRRPrim_Cnt FC_Client_TxOLSPrim_
Cnt
5.2.30 LQMD Board Performance Event List

FEC_UNCOR_BLOCK_C ODU1_PM_FEUAS OTU1_FEES

NT

OptiX OSN 8800/6800/3800
SEFS_S RSOFS
NOTE
TCM6.
NOTE
TN11LQMD
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Fragments Jabbers Packets Received (64 Octets

in Length)

Packets Received Packets Received Packets Received

(512~1023 Octets in Length) (1024~1518 Octets in Length) (1519~MTU Octets in
Length)
Packets Transmitted (64 Packets Transmitted (65~127 Packets Transmitted

Octets in Length) Octets in Length) (128~255 Octets in Length)

(256~511 Octets in Length) (512~1023 Octets in Length) (1024~1518 Octets in
Length)
Packets Transmitted Unicast Packets Received Unicast Packets Transmitted

(1519~MTU Octets in
Length)
Multicast Packets Broadcast Packets Pause Frames Received

Pause Frames Transmitted Good Octets Received Good Octets Transmitted
Bad Octets Received Bad Octets Transmitted Drop Events at Transmission

Direction

OptiX OSN 8800/6800/3800
Oversize Packets
Transmitted
TN12LQMD
Packets Received Broadcast Packets

(1024~1518 Octets in Transmitted
Drop Events Length)
Packets Received Pause Frames Received

(1519~MTU Octets in
Broadcast Packets Received Length)
Multicast Packets Received Packets Transmitted (64 Pause Frames Transmitted

Octets in Length)
Undersize Packets Received Packets Transmitted Good Octets Received

Oversize Packets Received Packets Transmitted Good Octets Transmitted

Fragments Packets Transmitted Bad Octets Received

Jabbers Packets Transmitted Bad Octets Transmitted

Packets Received (64 Octets in Packets Transmitted Alignment Errors

Length) (1024~1518 Octets in
Length)
Packets Received (65~127 Packets Transmitted Drop Events at

Octets in Length) (1519~MTU Octets in Transmission Direction
Length)
Packets Received (128~255 Unicast Packets Received Oversize Packets

Packets Received (256~511 Unicast Packets Transmitted

Octets in Length)
Packets Received (512~1023 Multicast Packets

5.2.31 LQMS Board Performance Event List


OptiX OSN 8800/6800/3800
FEC_UNCOR_BLOCK_C ODU1_PM_FEUAS OTU1_FEES

NT
SEFS_S RSOFS
NOTE
TCM6.
NOTE
TN11LQMS

OptiX OSN 8800/6800/3800
FCS and Alignment Errors Undersize Packets Received Oversize Packets Received
Fragments Jabbers Packets Received (64 Octets

in Length)

Packets Received Packets Received Packets Received

Length) Length)
Packets Transmitted (64 Packets Transmitted Packets Transmitted


Packets Transmitted Unicast Packets Received Unicast Packets Transmitted

(1519~MTU Octets in
Length)
Multicast Packets Multicast Packets Broadcast Pause Frames Received

Transmitted
Bad Octets Received Bad Octets Transmitted Drop Events at Transmission

Direction
Oversize Packets
Transmitted
TN12LQMS
Packets Received

Length)

Octets in Length)



OptiX OSN 8800/6800/3800



Length)

Length)


5.2.32 LQM Board Performance Event List

FEC_AFT_COR_ER ODU1_PM_ES ODU1_TCMn_UAS
FEC_AFT_COR_ERAVR ODU1_PM_FEBBE OTU1_BBE
FEC_BEF_COR_ER ODU1_PM_FEBBER OTU1_BBER
FEC_BEF_COR_ERAVR ODU1_PM_FEES OTU1_BIAES
FEC_COR_0BIT_CNT ODU1_PM_FESES OTU1_ES
FEC_COR_1BIT_CNT ODU1_PM_FESESR OTU1_FEBBE
FEC_COR_BYTE_CNT ODU1_PM_FEUAS OTU1_FEBBER
FEC_UNCOR_BLOCK_C ODU1_PM_SES OTU1_FEES

NT
FEC_BEF_CORER_FLOA ODU1_PM_SESR OTU1_FESES

T
FEC_AFT_CORER_FLOA ODU1_PM_UAS OTU1_FESESR

T
LSBIASCUR ODU1_TCMn_BBE OTU1_FEUAS
LSBIASMAX ODU1_TCMn_BBER OTU1_IAES
LSBIASMIN ODU1_TCMn_BIAES OTU1_SES
LSIOPCUR ODU1_TCMn_ES OTU1_SESR
LSIOPMAX ODU1_TCMn_FEBBE OTU1_UAS

OptiX OSN 8800/6800/3800
LSIOPMIN ODU1_TCMn_FEBBER RSBBE
LSOOPCUR ODU1_TCMn_FEES RSCSES
LSOOPMAX ODU1_TCMn_FESES RSES
LSOOPMIN ODU1_TCMn_FESESR RSSES
ODU1_PM_BBER RSOFS
NOTE
TCM6.
NOTE
Packets Received

Length)

Octets in Length)





Length)

OptiX OSN 8800/6800/3800

Length)


5.2.33 LSC Board Performance Event List

TN12LSC
BDTEMPCUR ODU4_PM_ES OTU4_IAES
BDTEMPMAX ODU4_PM_FEBBE OTU4_SES
BDTEMPMIN ODU4_PM_FEBBER OTU4_SESR
DGDAVG ODU4_PM_FEES OTU4_UAS
DGDCUR ODU4_PM_FESES PEAK_LSBIAS_CUR
DGDMAX ODU4_PM_FESESR PEAK_LSBIAS_MAX
DGDMIN ODU4_PM_FEUAS PEAK_LSBIAS_MIN
FEC_AFT_CORER_FLO
AT ODU4_PM_SES PEAK_INPOWER_CUR
FEC_AFT_COR_ER ODU4_PM_SESR PEAK_INPOWER_MAX
FEC_AFT_COR_ERAV
R ODU4_PM_UAS PEAK_INPOWER_MIN
FEC_BEF_CORER_FLO
AT ODU4_TCMn_BBE PEAK_LSTMP_CUR
FEC_BEF_COR_ER ODU4_TCMn_BBER PEAK_LSTMP_MAX
FEC_BEF_COR_ERAV
R ODU4_TCMn_BIAES PEAK_LSTMP_MIN
FEC_COR_0BIT_CNT ODU4_TCMn_ES PEAK_OUTPOWER_CUR
FEC_COR_1BIT_CNT ODU4_TCMn_FEBBE PEAK_OUTPOWER_MAX
FEC_COR_BYTE_CNT ODU4_TCMn_FEBBER PEAK_OUTPOWER_MIN
FEC_UNCOR_BLOCK_
CNT ODU4_TCMn_FEES SUMIOPCUR
LSBIASCUR ODU4_TCMn_FESES SUMIOPMAX

OptiX OSN 8800/6800/3800
LSBIASMAX ODU4_TCMn_FESESR SUMIOPMIN
LSBIASMIN ODU4_TCMn_FEUAS TDCCUR
LSCLCCUR ODU4_TCMn_IAES TDCMAX
LSCLCMAX ODU4_TCMn_SES TDCMIN
LSCLCMIN ODU4_TCMn_SESR VALLEY_LSBIAS_CUR
LSIOPCUR ODU4_TCMn_UAS VALLEY_LSBIAS_MAX
LSIOPMAX OTU4_BBE VALLEY_LSBIAS_MIN
LSIOPMIN OTU4_BBER VALLEY_INPOWER_CUR
LSOOPCUR OTU4_BIAES VALLEY_INPOWER_MAX
LSOOPMAX OTU4_ES VALLEY_INPOWER_MIN
LSOOPMIN OTU4_FEBBE VALLEY_LSTMP_CUR
LSTMPCUR OTU4_FEBBER VALLEY_LSTMP_MAX
LSTMPMAX OTU4_FEES VALLEY_LSTMP_MIN
VALLEY_OUTPOWER_CU
LSTMPMIN OTU4_FESES R
VALLEY_OUTPOWER_M
ODU4_PM_BBE OTU4_FESESR AX
VALLEY_OUTPOWER_MI
ODU4_PM_BBER OTU4_FEUAS N
TN12LSC
Packets Received
(1024~1518 Octets in
FCS Errors Octets Transmitted Length)
Unicast Packets
Pause Frames Transmitted Broadcast Packets Transmitted Received
Packets Transmitted Multicast Packets Transmitted Octets Received
Packets Transmitted (64 Broadcast Packets

Octets in Length) Pause Frames Received Received
Packets Transmitted
(65~127 Octets in Length) Packets Received Fragments

OptiX OSN 8800/6800/3800
Packets Transmitted Packets Received (64 Octets in Multicast Packets

(128~255 Octets in Length) Length) Received
Packets Transmitted Packets Received (65~127 Octets Undersize Packets

(256~511 Octets in Length) in Length) Received
Packets Transmitted
(512~1023 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers

Unicast Packets Transmitted Octets in Length)
5.2.34 LSQ Board Performance Event List

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_UNCOR_BLOCK_CN ODU3_PM_SES OTU3_FESESR

T

OptiX OSN 8800/6800/3800
NOTE
TCM6.
5.2.35 LSXLR Board Performance Event List

FEC_AFT_COR_ER LSTMPMAX ODU3_TCMn_FEUAS
FEC_AFT_COR_ERAVR LSTMPMIN ODU3_TCMn_IAES
FEC_AFT_CORER_FLOA ODU3_PM_BBE ODU3_TCMn_SES

T
FEC_BEF_COR_ER ODU3_PM_BBER ODU3_TCMn_SESR
FEC_BEF_COR_ERAVR ODU3_PM_ES ODU3_TCMn_UAS
FEC_BEF_CORER_FLOA ODU3_PM_FEBBE OTU3_BBE

T
FEC_UNCOR_BLOCK_C ODU3_PM_FESESR OTU3_FEBBE

NT

OptiX OSN 8800/6800/3800
NOTE
TCM6.
5.2.36 LSXL Board Performance Event List

TN11LSXL/TN12LSXL
FEC_AFT_CORER_FLOAT ODU3_PM_BBE ODU3_TCMn_UAS
FEC_AFT_COR_ERAVR ODU3_PM_ES OTU3_BBER
FEC_BEF_CORER_FLOAT ODU3_PM_FEBBE OTU3_BIAES
FEC_BEF_COR_ERAVR ODU3_PM_FEES OTU3_FEBBE
FEC_UNCOR_BLOCK_CN ODU3_PM_SES OTU3_FESESR

T

OptiX OSN 8800/6800/3800
TN15LSXL
FEC_AFT_CORER_FLO
AT ODU3_PM_FEBBE OTU3_FEBBER
FEC_AFT_COR_ER ODU3_PM_FEBBER OTU3_FEES
FEC_AFT_COR_ERAV
R ODU3_PM_FEES OTU3_FESES
FEC_BEF_CORER_FLO
AT ODU3_PM_FESES OTU3_FESESR
FEC_BEF_COR_ER ODU3_PM_FESESR OTU3_FEUAS
FEC_BEF_COR_ERAV
R ODU3_PM_FEUAS OTU3_IAES
FEC_COR_0BIT_CNT ODU3_PM_SES OTU3_SES
FEC_COR_1BIT_CNT ODU3_PM_SESR OTU3_SESR
FEC_COR_BYTE_CNT ODU3_PM_UAS OTU3_UAS
FEC_UNCOR_BLOCK_
CNT ODU3_TCMn_BBE DGDAVG
LSBIASCUR ODU3_TCMn_BBER DGDCUR
LSBIASMAX ODU3_TCMn_BIAES DGDMAX
LSBIASMIN ODU3_TCMn_ES DGDMIN
LSCLCCUR ODU3_TCMn_FEBBE RSBBE
LSCLCMAX ODU3_TCMn_FEBBER RSCSES
LSCLCMIN ODU3_TCMn_FEES RSES
LSIOPCUR ODU3_TCMn_FESES RSOFS

OptiX OSN 8800/6800/3800
LSIOPMAX ODU3_TCMn_FESESR RSSES
LSIOPMIN ODU3_TCMn_FEUAS RSUAS
LSOOPCUR ODU3_TCMn_IAES SUMIOPCUR
LSOOPMAX ODU3_TCMn_SES SUMIOPMAX
LSOOPMIN ODU3_TCMn_SESR SUMIOPMIN
LSTMPCUR ODU3_TCMn_UAS TDCCUR
LSTMPMAX OTU3_BBE TDCMAX
LSTMPMIN OTU3_BBER TDCMIN
ODU3_PM_BBE OTU3_BIAES BDTEMPCUR
ODU3_PM_BBER OTU3_ES BDTEMPMAX
ODU3_PM_ES OTU3_FEBBE BDTEMPMIN
NOTE
TCM6.
5.2.37 LSXR Board Performance Event List

FEC_AFT_CORER_FLOA ODU2_PM_ES OTU2_BBER

T
FEC_BEF_CORER_FLOA ODU2_PM_FEES OTU2_FEBBE

T
FEC_UNCOR_BLOCK_C ODU2_PM_SES OTU2_FESESR

NT

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE
5.2.38 LSX Board Performance Event List

FEC_AFT_CORER_FLOA ODU2_PM_ES OTU2_BBER

T
FEC_BEF_CORER_FLOA ODU2_PM_FEES OTU2_FEBBE

T

OptiX OSN 8800/6800/3800
FEC_UNCOR_BLOCK_C ODU2_PM_SES OTU2_FESESR

NT
NOTE
TCM6.
NOTE
TN12LSX
Packets Received, 65~127

FCS Errors Octets in Length Pause Frames Transmitted
Packets Received, 128~255 Packets Transmitted, 64

Fragments Octets in Length Octets in Length
Packets Received, 256~511 Packets Transmitted, 65~127

Jabbers Octets in Length Octets in Length
Packets Received, 512~1023 Packets Transmitted,

Oversize Packets Received Octets in Length 128~255 Octets in Length

OptiX OSN 8800/6800/3800
Packets Received, Packets Transmitted,

Undersize Packets Received 1024~1518 Octets in Length 256~511 Octets in Length
Packets Transmitted,
Broadcast Packets Received Packets Received 512~1023 Octets in Length
Multicast Packets Received Unicast Packets Received 1024~1518 Octets in Length
Broadcast Packets
Octets Received Transmitted Packets Transmitted
Multicast Packets Multicast Packets

Transmitted Transmitted Unicast Packets Transmitted
Packets Received, 64 Octets

in Length Octets Transmitted
TN13LSX
Packets Received, 64 Octets

Alignment Errors in Length Octets Transmitted

FCS Errors Octets in Length Pause Frames Transmitted
Packets Received, 128~255 Packets Transmitted, 64



Oversize Packets Received 512~1023 Octets in Length 128~255 Octets in Length

Undersize Packets Received 1024~1518 Octets in Length 256~511 Octets in Length
Broadcast Packets Received Packets Received 512~1023 Octets in Length
Multicast Packets Received Unicast Packets Received 1024~1518 Octets in Length
Broadcast Packets
Octets Received Transmitted Packets Transmitted
Multicast Packets Multicast Packets

Transmitted Transmitted Unicast Packets Transmitted

OptiX OSN 8800/6800/3800
5.2.39 LTX Board Performance Event List

TN11LTX
BDTEMPCUR ODU2_PM_BBE ODU4_TCMn_FESESR
BDTEMPMAX ODU2_PM_BBER ODU4_TCMn_FEUAS
BDTEMPMIN ODU2_PM_ES ODU4_TCMn_IAES
DGDAVG ODU2_PM_FEBBE ODU4_TCMn_SES
DGDCUR ODU2_PM_FEBBER ODU4_TCMn_SESR
DGDMAX ODU2_PM_FEES ODU4_TCMn_UAS
DGDMIN ODU2_PM_FESES OTU4_BBE
FEC_AFT_CORER_FLOAT ODU2_PM_FESESR OTU4_BBER
FEC_AFT_COR_ER ODU2_PM_FEUAS OTU4_BIAES
FEC_AFT_COR_ERAVR ODU2_PM_SES OTU4_ES
FEC_BEF_CORER_FLOAT ODU2_PM_SESR OTU4_FEBBE
FEC_BEF_COR_ER ODU2_PM_UAS OTU4_FEBBER
FEC_BEF_COR_ERAVR ODU4_PM_BBE OTU4_FEES
FEC_COR_0BIT_CNT ODU4_PM_BBER OTU4_FESES
FEC_COR_1BIT_CNT ODU4_PM_ES OTU4_FESESR
FEC_COR_BYTE_CNT ODU4_PM_FEBBE OTU4_FEUAS
FEC_UNCOR_BLOCK_CNT ODU4_PM_FEBBER OTU4_IAES
LSBIASCUR ODU4_PM_FEES OTU4_SES
LSBIASMAX ODU4_PM_FESES OTU4_SESR
LSBIASMIN ODU4_PM_FESESR OTU4_UAS
LSCLCCUR ODU4_PM_FEUAS RSBBE
LSCLCMAX ODU4_PM_SES RSCSES
LSCLCMIN ODU4_PM_SESR RSES
LSIOPCUR ODU4_PM_UAS RSOFS
LSIOPMAX ODU4_TCMn_BBE RSSES
LSIOPMIN ODU4_TCMn_BBER RSUAS
LSOOPCUR ODU4_TCMn_BIAES SUMIOPCUR
LSOOPMAX ODU4_TCMn_ES SUMIOPMAX

OptiX OSN 8800/6800/3800
LSOOPMIN ODU4_TCMn_FEBBE SUMIOPMIN
LSTMPCUR ODU4_TCMn_FEBBER TDCCUR
LSTMPMAX ODU4_TCMn_FEES TDCMAX
LSTMPMIN ODU4_TCMn_FESES TDCMIN
TN11LTX
Packets Received
(1519~MTU Octets in
FCS Errors Good Octets Transmitted Length)
Unicast Packets
Control Frames Transmitted Broadcast Packets Transmitted Received
Good Octets
Pause Frames Transmitted Multicast Packets Transmitted Transmitted
Packets Transmitted (64

Octets in Length) Oversize Packets Transmitted Bad Octets Transmitted
Packets Transmitted Broadcast Packets

(65~127 Octets in Length) Control Frames Received Received
Packets Transmitted
(128~255 Octets in Length) Pause Frames Received Fragments
Packets Transmitted Packets Received (64 Octets in Multicast Packets

(256~511 Octets in Length) Length) Received
Packets Transmitted
(512~1023 Octets in Packets Received (65~127 Octets Undersize Packets
Length) in Length) Received
Packets Transmitted
(1024~1518 Octets in Packets Transmitted (128~255 Oversize Packets
Length) Octets in Length) Received
Packets Transmitted
(1519~MTU Octets in Packets Received (256~511 Octets
Length) in Length) Jabbers


Bad Octets Transmitted Octets in Length)

OptiX OSN 8800/6800/3800
5.2.40 LWX2 Board Performance Event List

LSBIASCUR LSIOPMIN RSCSES
LSBIASMAX LSOOPCUR RSES
LSBIASMIN LSOOPMAX RSOFS
LSCLCCUR LSOOPMIN RSSES
LSCLCMAX LSTMPCUR RSUAS
LSCLCMIN LSTMPMAX BDTEMPCUR
LSIOPCUR LSTMPMIN BDTEMPMAX
LSIOPMAX RSBBE BDTEMPMIN
5.2.41 LWXD Board Performance Event List

5.2.42 LWXS Board Performance Event List


OptiX OSN 8800/6800/3800
5.2.43 M40V Board Performance Event List

ICTMPCUR SUMOOPCUR BDTEMPCUR
ICTMPMAX SUMOOPMAX BDTEMPMAX
ICTMPMIN SUMOOPMIN BDTEMPMIN
5.2.44 M40 Board Performance Event List

TN12M40
ICCLCCUR ICTMPMAX SUMOOPMIN
ICCLCMIN SUMOOPCUR BDTEMPMAX
ICTMPCUR SUMOOPMAX BDTEMPMIN
TN11M40
ICCLCCUR ICTMPMAX SUMOOPMIN
ICCLCMIN SUMOOPCUR BDTEMPMAX
ICTMPCUR SUMOOPMAX BDTEMPMIN
5.2.45 MCA4 Board Performance Event List

PCLSOPCUR PCLSSNMIN PCLSWLOMAX
PCLSOPMAX PCLSWLCUR PCLSWLOMIN
PCLSOPMIN PCLSWLMAX BDTEMPCUR
PCLSSNCUR PCLSWLMIN BDTEMPMAX
PCLSSNMAX PCLSWLOCUR BDTEMPMIN

OptiX OSN 8800/6800/3800
5.2.46 MCA8 Board Performance Event List

PCLSOPCUR PCLSSNMIN PCLSWLOMAX
PCLSOPMAX PCLSWLCUR PCLSWLOMIN
PCLSOPMIN PCLSWLMAX BDTEMPCUR
PCLSSNCUR PCLSWLMIN BDTEMPMAX
PCLSSNMAX PCLSWLOCUR BDTEMPMIN
5.2.47 MR8V Board Performance Event List

5.2.48 ND2 Board Performance Event List

TN53ND2
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

OptiX OSN 8800/6800/3800
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
ODU0_TCMn_FEBBE ODU2_PM_FEUAS BDTEMPCUR
ODU0_TCMn_FEBBER ODU2_PM_SES BDTEMPMAX

OptiX OSN 8800/6800/3800
ODU0_TCMn_FEES ODU2_PM_SESR BDTEMPMIN
TN53ND2 (COMP)
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

OptiX OSN 8800/6800/3800
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 BDTEMPCUR
ODU0_PM_FESESR ODU2_PM_FEES BDTEMPMAX
ODU0_PM_FEUAS ODU2_PM_FESES BDTEMPMIN
ODU0_PM_SES ODU2_PM_FESESR
ODU0_PM_SESR ODU2_PM_FEUAS
TN52ND2
FEC_AFT_CORER_FLO
AT ODU0_PM_UAS ODU2_PM_SES
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_ERAV
R ODU1_PM_FEBBER ODU2_TCMn_BIAES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS ODU2_TCMn_FEES

OptiX OSN 8800/6800/3800
TN12ND2
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
FEC_COR_1BIT_CNT ODU1_TCMn_FEBBE ODU2_TCMn_FEUAS

OptiX OSN 8800/6800/3800
FEC_COR_BYTE_CNT ODU1_TCMn_FEBBER ODU2_TCMn_IAES
FEC_UNCOR_BLOCK_CN ODU1_TCMn_FEES ODU2_TCMn_SES

T
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 BDTEMPCUR
ODU1_PM_FEES ODU2_PM_SESR BDTEMPMAX
ODU1_PM_FESES ODU2_PM_UAS BDTEMPMIN
ODU1_PM_FESESR ODU2_TCMn_BBE
ODU1_PM_FEUAS ODU2_TCMn_BBER
TN11ND2
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

OptiX OSN 8800/6800/3800
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 ODU1_TCMn_FEBBE ODU2_TCMn_IAES

T
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 BDTEMPCUR
ODU1_PM_FEBBE ODU2_PM_SES BDTEMPMAX
ODU1_PM_FEBBER ODU2_PM_SESR BDTEMPMIN
ODU1_PM_FEES ODU2_PM_UAS
ODU1_PM_FESES ODU2_TCMn_BBE

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE
5.2.49 NO2 Board Performance Event List

TN55NO2
FEC_AFT_CORER_FLO
FEC_AFT_COR_ERAV
FEC_BEF_CORER_FLO
FEC_BEF_COR_ERAV
FEC_UNCOR_BLOCK_

OptiX OSN 8800/6800/3800
TN55NO2(REG)
FEC_AFT_CORER_FLO
AT LSTMPMAX ODU2_TCMn_FEUAS
FEC_AFT_COR_ER LSTMPMIN ODU2_TCMn_IAES
FEC_AFT_COR_ERAV
R ODU2_PM_BBE ODU2_TCMn_SES
FEC_BEF_CORER_FLO
AT ODU2_PM_BBER ODU2_TCMn_SESR
FEC_BEF_COR_ER ODU2_PM_ES ODU2_TCMn_UAS
FEC_BEF_COR_ERAV
R ODU2_PM_FEBBE OTU2_BBE
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FESESR OTU2_FEBBE

OptiX OSN 8800/6800/3800
NOTE
TCM6.
5.2.50 NQ2 Board Performance Event List

TN54NQ2
FEC_AFT_CORER_FLO
AT ODU1_PM_BBER ODU2_PM_SESR
FEC_AFT_COR_ER ODU1_PM_ES ODU2_PM_TMP
FEC_AFT_COR_ERAV
R ODU1_PM_FEBBE ODU2_PM_UAS
FEC_BEF_CORER_FLO
AT ODU1_PM_FEBBER ODU2_TCMn_BBE
FEC_BEF_COR_ER ODU1_PM_FEES ODU2_TCMn_BBER
FEC_BEF_COR_ERAV
R ODU1_PM_FESES ODU2_TCMn_BIAES
FEC_COR_0BIT_CNT ODU1_PM_FESESR ODU2_TCMn_ES
FEC_COR_1BIT_CNT ODU1_PM_FEUAS ODU2_TCMn_FEBBE
FEC_COR_BYTE_CNT ODU1_PM_SES ODU2_TCMn_FEBBER

OptiX OSN 8800/6800/3800
FEC_TMP ODU1_PM_SESR ODU2_TCMn_FEES
FEC_UNCOR_BLOCK_
CNT ODU1_PM_TMP 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_TMP
LSOOPCUR ODU1_TCMn_FEBBER ODU2_TCMn_UAS
LSOOPMAX ODU1_TCMn_FEES OTU2_BBE
LSOOPMIN ODU1_TCMn_FESES OTU2_BBER
LSTMPCUR ODU1_TCMn_FESESR OTU2_BIAES
LSTMPMAX ODU1_TCMn_FEUAS OTU2_ES
LSTMPMIN ODU1_TCMn_IAES OTU2_FEBBE
ODU0_PM_BBE ODU1_TCMn_SES OTU2_FEBBER
ODU0_PM_BBER ODU1_TCMn_SESR OTU2_FEES
ODU0_PM_ES ODU1_TCMn_TMP OTU2_FESES
ODU0_PM_FEBBE ODU1_TCMn_UAS OTU2_FESESR
ODU0_PM_FEBBER ODU2_PM_BBE OTU2_FEUAS
ODU0_PM_FEES ODU2_PM_BBER OTU2_IAES
ODU0_PM_FESES ODU2_PM_ES OTU2_SES
ODU0_PM_FESESR ODU2_PM_FEBBE OTU2_SESR
ODU0_PM_FEUAS ODU2_PM_FEBBER OTU2_TMP
ODU0_PM_SES ODU2_PM_FEES OTU2_UAS
ODU0_PM_SESR ODU2_PM_FESES BDTEMPCUR
ODU0_PM_TMP ODU2_PM_FESESR BDTEMPMAX
ODU0_PM_UAS ODU2_PM_FEUAS BDTEMPMIN
ODU1_PM_BBE ODU2_PM_SES
TN53NQ2

OptiX OSN 8800/6800/3800
FEC_AFT_CORER_FLO
AT ODU0_TCMn_FESESR ODU2_PM_UAS
FEC_AFT_COR_ER ODU0_TCMn_FEUAS ODU2_TCMn_BBE
FEC_AFT_COR_ERAV
R ODU0_TCMn_IAES ODU2_TCMn_BBER
FEC_BEF_CORER_FLO
AT ODU0_TCMn_SES ODU2_TCMn_BIAES
FEC_BEF_COR_ER ODU0_TCMn_SESR ODU2_TCMn_ES
FEC_BEF_COR_ERAV
R ODU0_TCMn_TMP ODU2_TCMn_FEBBE
FEC_TMP ODU1_PM_ES ODU2_TCMn_FESESR
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEBBE ODU2_TCMn_FEUAS
LSBIASCUR ODU1_PM_FEBBER ODU2_TCMn_IAES
LSBIASMAX ODU1_PM_FEES ODU2_TCMn_SES
LSBIASMIN ODU1_PM_FESES ODU2_TCMn_SESR
LSCLCCUR ODU1_PM_FESESR ODU2_TCMn_TMP
LSCLCMAX ODU1_PM_FEUAS ODU2_TCMn_UAS
LSCLCMIN ODU1_PM_SES ODUFLEX_PM_BBE
LSIOPCUR ODU1_PM_SESR ODUFLEX_PM_BBER
LSIOPMAX ODU1_PM_TMP ODUFLEX_PM_ES

OptiX OSN 8800/6800/3800
ODU0_PM_BBER ODU1_TCMn_FESES ODUFLEX_PM_TMP
ODU0_PM_ES ODU1_TCMn_FESESR ODUFLEX_PM_UAS
ODU0_PM_FEBBE ODU1_TCMn_FEUAS OTU2_BBE
ODU0_PM_FEBBER ODU1_TCMn_IAES OTU2_BBER
ODU0_PM_FEES ODU1_TCMn_SES OTU2_BIAES
ODU0_PM_FESES ODU1_TCMn_SESR OTU2_ES
ODU0_PM_FESESR ODU1_TCMn_TMP OTU2_FEBBE
ODU0_PM_FEUAS ODU1_TCMn_UAS OTU2_FEBBER
ODU0_PM_SES ODU2_PM_BBE OTU2_FEES
ODU0_PM_SESR ODU2_PM_BBER OTU2_FESES
ODU0_PM_TMP ODU2_PM_ES OTU2_FESESR
ODU0_TCMn_ES ODU2_PM_FESESR OTU2_TMP
ODU0_TCMn_FEBBE ODU2_PM_FEUAS OTU2_UAS
ODU0_TCMn_FEBBER ODU2_PM_SES BDTEMPCUR
ODU0_TCMn_FEES ODU2_PM_SESR BDTEMPMAX
ODU0_TCMn_FESES ODU2_PM_TMP BDTEMPMIN
TN53NQ2(COMP)
FEC_AFT_CORER_FLO
FEC_AFT_COR_ERAV
R ODU1_PM_BBER ODU2_PM_TMP
FEC_BEF_CORER_FLO
AT ODU1_PM_ES ODU2_PM_UAS
FEC_BEF_COR_ER ODU1_PM_FEBBE ODU2_TCMn_BBE

OptiX OSN 8800/6800/3800
FEC_BEF_COR_ERAV
R ODU1_PM_FEBBER ODU2_TCMn_BBER
FEC_COR_0BIT_CNT ODU1_PM_FEES ODU2_TCMn_BIAES
FEC_COR_1BIT_CNT ODU1_PM_FESES ODU2_TCMn_ES
FEC_COR_BYTE_CNT ODU1_PM_FESESR ODU2_TCMn_FEBBE
FEC_TMP ODU1_PM_FEUAS ODU2_TCMn_FEBBER
FEC_UNCOR_BLOCK_
CNT ODU1_PM_SES ODU2_TCMn_FEES
LSBIASCUR ODU1_PM_SESR ODU2_TCMn_FESES
LSBIASMAX ODU1_PM_TMP ODU2_TCMn_FESESR
LSIOPCUR ODU1_TCMn_ES ODU2_TCMn_TMP
LSIOPMAX ODU1_TCMn_FEBBE ODU2_TCMn_UAS
LSIOPMIN ODU1_TCMn_FEBBER OTU2_BBE
LSOOPCUR ODU1_TCMn_FEES OTU2_BBER
LSOOPMAX ODU1_TCMn_FESES OTU2_BIAES
LSOOPMIN ODU1_TCMn_FESESR OTU2_ES
LSTMPCUR ODU1_TCMn_FEUAS OTU2_FEBBE
LSTMPMAX ODU1_TCMn_IAES OTU2_FEBBER
LSTMPMIN ODU1_TCMn_SES OTU2_FEES
ODU0_PM_BBE ODU1_TCMn_SESR OTU2_FESES
ODU0_PM_BBER ODU1_TCMn_TMP OTU2_FESESR
ODU0_PM_ES ODU1_TCMn_UAS OTU2_FEUAS
ODU0_PM_FEBBE ODU2_PM_BBE OTU2_IAES
ODU0_PM_FEBBER ODU2_PM_BBER OTU2_SES
ODU0_PM_FEES ODU2_PM_ES OTU2_SESR
ODU0_PM_FESES ODU2_PM_FEBBE OTU2_TMP
ODU0_PM_FESESR ODU2_PM_FEBBER OTU2_UAS

OptiX OSN 8800/6800/3800
ODU0_PM_FEUAS ODU2_PM_FEES BDTEMPCUR
ODU0_PM_SES ODU2_PM_FESES BDTEMPMAX
ODU0_PM_SESR ODU2_PM_FESESR BDTEMPMIN
ODU0_PM_TMP ODU2_PM_FEUAS
TN52NQ2
FEC_UNCOR_BLOCK_CN ODU1_PM_FEUAS ODU2_TCMn_FEES

T

OptiX OSN 8800/6800/3800
TN51NQ2

T

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE
5.2.51 NPO2 Board Performance Event List

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

OptiX OSN 8800/6800/3800
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 ODU1_PM_SESR ODU2_TCMn_FESES

T
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_UAS ODU2_PM_FEUAS

OptiX OSN 8800/6800/3800
NOTE
5.2.52 NPO2E Board Performance Event List

TN55NPO2E
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
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

OptiX OSN 8800/6800/3800
ODU0_PM_FEES ODU2_PM_ES OTU2_SES
ODU0_PM_FESES ODU2_PM_FEBBE OTU2_SESR
ODU0_PM_UAS ODU2_PM_FEUAS
NOTE
5.2.53 NS2 Board Performance Event List

TN53NS2
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_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

OptiX OSN 8800/6800/3800
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
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_TCMn_ES ODU2_PM_FESESR OTU2_UAS
ODU0_TCMn_FEBBE ODU2_PM_FEUAS BDTEMPCUR
ODU0_TCMn_FEBBER ODU2_PM_SES BDTEMPMAX
ODU0_TCMn_FEES ODU2_PM_SESR BDTEMPMIN

OptiX OSN 8800/6800/3800
TN53NS2 (COMP)
FEC_UNCOR_BLOCK_CNT ODU1_PM_FEUAS ODU2_TCMn_FEES

OptiX OSN 8800/6800/3800
TN52NS2
FEC_AFT_CORER_FLO
FEC_AFT_COR_ERAV
FEC_BEF_CORER_FLO
FEC_BEF_COR_ERAV
FEC_UNCOR_BLOCK_

OptiX OSN 8800/6800/3800
TN12NS2

T

OptiX OSN 8800/6800/3800
TN11NS2

OptiX OSN 8800/6800/3800

T
NOTE
TCM6.

OptiX OSN 8800/6800/3800
NOTE

TN55NS3
FEC_AFT_CORER_FLO
AT ODU1_PM_UAS ODU3_PM_FESESR
FEC_AFT_COR_ER ODU1_TCMn_BBE ODU3_PM_FEUAS
FEC_AFT_COR_ERAV
R ODU1_TCMn_BBER ODU3_PM_SES
FEC_BEF_CORER_FLO
AT ODU1_TCMn_BIAES ODU3_PM_SESR
FEC_BEF_COR_ER ODU1_TCMn_ES ODU3_PM_UAS
FEC_BEF_COR_ERAV
R ODU1_TCMn_FEBBE ODU3_TCMn_BBE
FEC_COR_0BIT_CNT ODU1_TCMn_FEBBER ODU3_TCMn_BBER
FEC_COR_1BIT_CNT ODU1_TCMn_FEES ODU3_TCMn_BIAES
FEC_COR_BYTE_CNT ODU1_TCMn_FESES ODU3_TCMn_ES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_FESESR ODU3_TCMn_FEBBE
LSBIASCUR ODU1_TCMn_FEUAS ODU3_TCMn_FEBBER
LSBIASMAX ODU1_TCMn_IAES ODU3_TCMn_FEES
LSBIASMIN ODU1_TCMn_SES ODU3_TCMn_FESES
LSCLCCUR ODU1_TCMn_SESR ODU3_TCMn_FESESR
LSCLCMAX ODU1_TCMn_UAS ODU3_TCMn_FEUAS
LSCLCMIN ODU2_PM_BBE ODU3_TCMn_IAES
LSIOPCUR ODU2_PM_BBER ODU3_TCMn_SES
LSIOPMAX ODU2_PM_ES ODU3_TCMn_SESR
LSIOPMIN ODU2_PM_FEBBE ODU3_TCMn_UAS
LSOOPCUR ODU2_PM_FEBBER OTU3_BBE
LSOOPMAX ODU2_PM_FEES OTU3_BBER
LSOOPMIN ODU2_PM_FESES OTU3_BIAES
LSTMPCUR ODU2_PM_FESESR OTU3_ES
LSTMPMAX ODU2_PM_FEUAS OTU3_FEBBE

OptiX OSN 8800/6800/3800
LSTMPMIN ODU2_PM_SES OTU3_FEBBER
ODU0_PM_BBE ODU2_PM_SESR OTU3_FEES
ODU0_PM_BBER ODU2_PM_UAS OTU3_FESES
ODU0_PM_ES ODU2_TCMn_BBE OTU3_FESESR
ODU0_PM_FEBBE ODU2_TCMn_BBER OTU3_FEUAS
ODU0_PM_FEBBER ODU2_TCMn_BIAES OTU3_IAES
ODU0_PM_FEES ODU2_TCMn_ES OTU3_SES
ODU0_PM_FESES ODU2_TCMn_FEBBE OTU3_SESR
ODU0_PM_FESESR ODU2_TCMn_FEBBER OTU3_UAS
ODU0_PM_FEUAS ODU2_TCMn_FEES DGDAVG
ODU0_PM_SES ODU2_TCMn_FESES DGDCUR
ODU0_PM_SESR ODU2_TCMn_FESESR DGDMAX
ODU0_PM_UAS ODU2_TCMn_FEUAS DGDMIN
ODU1_PM_BBE ODU2_TCMn_IAES SUMIOPCUR
ODU1_PM_BBER ODU2_TCMn_SES SUMIOPMAX
ODU1_PM_ES ODU2_TCMn_SESR SUMIOPMIN
ODU1_PM_FEBBE ODU2_TCMn_UAS TDCCUR
ODU1_PM_FEBBER ODU3_PM_BBE TDCMAX
ODU1_PM_FEES ODU3_PM_BBER TDCMIN
ODU1_PM_FESES ODU3_PM_ES BDTEMPCUR
ODU1_PM_FESESR ODU3_PM_FEBBE BDTEMPMAX
ODU1_PM_FEUAS ODU3_PM_FEBBER BDTEMPMIN
ODU1_PM_SES ODU3_PM_FEES
ODU1_PM_SESR ODU3_PM_FESES
TN54NS3
FEC_AFT_CORER_FLO
AT ODU1_PM_FEUAS ODU2_TCMn_UAS
FEC_AFT_COR_ER ODU1_PM_SES ODU3_PM_BBE
FEC_AFT_COR_ERAV
R ODU1_PM_SESR ODU3_PM_BBER

OptiX OSN 8800/6800/3800
FEC_BEF_CORER_FLO
AT ODU1_PM_TMP ODU3_PM_ES
FEC_BEF_COR_ER ODU1_PM_UAS ODU3_PM_FEBBE
FEC_BEF_COR_ERAV
R 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_TMP ODU1_TCMn_FEBBE ODU3_PM_FEUAS
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_FEBBER ODU3_PM_SES
LSBIASCUR ODU1_TCMn_FEES ODU3_PM_SESR
LSBIASMAX ODU1_TCMn_FESES ODU3_PM_TMP
LSBIASMIN ODU1_TCMn_FESESR ODU3_PM_UAS
LSCLCCUR ODU1_TCMn_FEUAS ODU3_TCMn_BBE
LSCLCMAX ODU1_TCMn_IAES ODU3_TCMn_BBER
LSCLCMIN ODU1_TCMn_SES ODU3_TCMn_BIAES
LSIOPCUR ODU1_TCMn_SESR ODU3_TCMn_ES
LSIOPMAX ODU1_TCMn_TMP 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_TMP
ODU0_PM_ES ODU2_PM_FEUAS ODU3_TCMn_UAS
ODU0_PM_FEBBE ODU2_PM_SES OTU3_BBE
ODU0_PM_FEBBER ODU2_PM_SESR OTU3_BBER
ODU0_PM_FEES ODU2_PM_TMP OTU3_BIAES

OptiX OSN 8800/6800/3800
ODU0_PM_FESES ODU2_PM_UAS OTU3_ES
ODU0_PM_FESESR ODU2_TCMn_BBE OTU3_FEBBE
ODU0_PM_FEUAS ODU2_TCMn_BBER OTU3_FEBBER
ODU0_PM_SES ODU2_TCMn_BIAES OTU3_FEES
ODU0_PM_SESR ODU2_TCMn_ES OTU3_FESES
ODU0_PM_TMP 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_TMP
ODU1_PM_FEBBER ODU2_TCMn_IAES OTU3_UAS
ODU1_PM_FEES ODU2_TCMn_SES BDTEMPCUR
ODU1_PM_FESES ODU2_TCMn_SESR BDTEMPMAX
ODU1_PM_FESESR ODU2_TCMn_TMP BDTEMPMIN
TN52NS3
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 ODU1_TCMn_FEBBE ODU3_PM_FEUAS

T
LSBIASCUR ODU1_TCMn_FEBBER ODU3_PM_SES
LSBIASMAX ODU1_TCMn_FEES ODU3_PM_SESR

OptiX OSN 8800/6800/3800
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
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 BDTEMPCUR

OptiX OSN 8800/6800/3800
ODU1_PM_FEES ODU2_TCMn_SES BDTEMPMAX
ODU1_PM_FESES ODU2_TCMn_SESR BDTEMPMIN
TN11NS3
ODU2_PM_ES ODU3_TCMn_FEBBE
FEC_AFT_COR_ER 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 BDTEMPCUR
LSTMPMIN ODU3_TCMn_BIAES BDTEMPMAX

OptiX OSN 8800/6800/3800
ODU2_PM_BBE ODU3_TCMn_ES BDTEMPMIN
ODU2_PM_BBER ODU3_TCMn_FEBBE
NOTE
TCM6.

TN54NS4
FEC_AFT_CORER_FLO
AT ODU1_TCMn_BIAES ODU4_PM_BBER
FEC_AFT_COR_ER ODU1_TCMn_ES ODU4_PM_ES
FEC_AFT_COR_ERAV
R ODU1_TCMn_FEBBE ODU4_PM_FEBBE
FEC_BEF_CORER_FLO
AT ODU1_TCMn_FEBBER ODU4_PM_FEBBER
FEC_BEF_COR_ER ODU1_TCMn_FEES ODU4_PM_FEES
FEC_BEF_COR_ERAV
R ODU1_TCMn_FESES ODU4_PM_FESES
FEC_COR_0BIT_CNT ODU1_TCMn_FESESR ODU4_PM_FESESR
FEC_COR_1BIT_CNT ODU1_TCMn_FEUAS ODU4_PM_FEUAS
FEC_COR_BYTE_CNT ODU1_TCMn_IAES ODU4_PM_SES
FEC_UNCOR_BLOCK_
CNT ODU1_TCMn_SES ODU4_PM_SESR
LSBIASCUR ODU1_TCMn_SESR ODU4_PM_UAS
LSBIASMAX ODU1_TCMn_UAS ODU4_TCMn_BBE
LSBIASMIN ODU2_PM_BBE ODU4_TCMn_BBER
LSCLCCUR ODU2_PM_BBER ODU4_TCMn_BIAES
LSCLCMAX ODU2_PM_ES ODU4_TCMn_ES
LSCLCMIN ODU2_PM_FEBBE ODU4_TCMn_FEBBE
LSIOPCUR ODU2_PM_FEBBER ODU4_TCMn_FEBBER
LSIOPMAX ODU2_PM_FEES ODU4_TCMn_FEES
LSIOPMIN ODU2_PM_FESES ODU4_TCMn_FESES

OptiX OSN 8800/6800/3800
LSOOPCUR ODU2_PM_FESESR ODU4_TCMn_FESESR
LSOOPMAX ODU2_PM_FEUAS ODU4_TCMn_FEUAS
LSOOPMIN ODU2_PM_SES ODU4_TCMn_IAES
LSTMPCUR ODU2_PM_SESR ODU4_TCMn_SES
LSTMPMAX ODU2_PM_UAS ODU4_TCMn_SESR
LSTMPMIN ODU2_TCMn_BBE ODU4_TCMn_UAS
ODU0_PM_BBE ODU2_TCMn_BBER ODUFLEX_PM_BBE
ODU0_PM_BBER ODU2_TCMn_BIAES ODUFLEX_PM_BBER
ODU0_PM_ES ODU2_TCMn_ES ODUFLEX_PM_ES
ODU0_PM_FEBBE ODU2_TCMn_FEBBE ODUFLEX_PM_FEBBE
ODU0_PM_FEBBER ODU2_TCMn_FEBBER ODUFLEX_PM_FEBBER
ODU0_PM_FEES ODU2_TCMn_FEES ODUFLEX_PM_FEES
ODU0_PM_FESES ODU2_TCMn_FESES ODUFLEX_PM_FESES
ODU0_PM_FESESR ODU2_TCMn_FESESR ODUFLEX_PM_FESESR
ODU0_PM_FEUAS ODU2_TCMn_FEUAS ODUFLEX_PM_FEUAS
ODU0_PM_SES ODU2_TCMn_IAES ODUFLEX_PM_SES
ODU0_PM_SESR ODU2_TCMn_SES ODUFLEX_PM_SESR
ODU0_PM_UAS ODU2_TCMn_SESR ODUFLEX_PM_UAS
ODU0_TCMn_BBE ODU2_TCMn_UAS OTU4_BBE
ODU0_TCMn_BBER ODU3_PM_BBE OTU4_BBER
ODU0_TCMn_BIAES ODU3_PM_BBER OTU4_BIAES
ODU0_TCMn_ES ODU3_PM_ES OTU4_ES
ODU0_TCMn_FEBBE ODU3_PM_FEBBE OTU4_FEBBE
ODU0_TCMn_FEBBER ODU3_PM_FEBBER OTU4_FEBBER
ODU0_TCMn_FEES ODU3_PM_FEES OTU4_FEES
ODU0_TCMn_FESES ODU3_PM_FESES OTU4_FESES
ODU0_TCMn_FESESR ODU3_PM_FESESR OTU4_FESESR
ODU0_TCMn_FEUAS ODU3_PM_FEUAS OTU4_FEUAS
ODU0_TCMn_IAES ODU3_PM_SES OTU4_IAES
ODU0_TCMn_SES ODU3_PM_SESR OTU4_SES

OptiX OSN 8800/6800/3800
ODU0_TCMn_SESR ODU3_PM_UAS OTU4_SESR
ODU0_TCMn_UAS ODU3_TCMn_BBE OTU4_UAS
ODU1_PM_BBE ODU3_TCMn_BBER PMDAVG
ODU1_PM_BBER ODU3_TCMn_BIAES PMDCUR
ODU1_PM_ES ODU3_TCMn_ES PMDMAX
ODU1_PM_FEBBE ODU3_TCMn_FEBBE PMDMIN
ODU1_PM_FEBBER ODU3_TCMn_FEBBER SUMIOPCUR
ODU1_PM_FEES ODU3_TCMn_FEES SUMIOPMAX
ODU1_PM_FESES ODU3_TCMn_FESES SUMIOPMIN
ODU1_PM_FESESR ODU3_TCMn_FESESR TDCCUR
ODU1_PM_FEUAS ODU3_TCMn_FEUAS TDCMAX
ODU1_PM_SES ODU3_TCMn_IAES TDCMIN
ODU1_PM_SESR ODU3_TCMn_SES BDTEMPCUR
ODU1_PM_UAS ODU3_TCMn_SESR BDTEMPMAX
ODU1_TCMn_BBE ODU3_TCMn_UAS BDTEMPMIN
ODU1_TCMn_BBER ODU4_PM_BBE
TN54NS4(REG)
FEC_AFT_CORER_FLO
AT ODU4_PM_BBER OTU4_BBER
FEC_AFT_COR_ER ODU4_PM_ES OTU4_BIAES
FEC_AFT_COR_ERAV
R ODU4_PM_FEBBE OTU4_ES
FEC_BEF_CORER_FLO
AT ODU4_PM_FEBBER OTU4_FEBBE
FEC_BEF_COR_ER ODU4_PM_FEES OTU4_FEBBER
FEC_BEF_COR_ERAV
R ODU4_PM_FESES OTU4_FEES
FEC_COR_0BIT_CNT ODU4_PM_FESESR OTU4_FESES
FEC_COR_1BIT_CNT ODU4_PM_FEUAS OTU4_FESESR
FEC_COR_BYTE_CNT ODU4_PM_SES OTU4_FEUAS

OptiX OSN 8800/6800/3800
FEC_UNCOR_BLOCK_
CNT ODU4_PM_SESR OTU4_IAES
LSBIASCUR ODU4_PM_UAS OTU4_SES
LSBIASMAX ODU4_TCMn_BBE OTU4_SESR
LSBIASMIN ODU4_TCMn_BBER OTU4_UAS
LSCLCCUR ODU4_TCMn_BIAES PMDAVG
LSCLCMAX ODU4_TCMn_ES PMDCUR
LSCLCMIN ODU4_TCMn_FEBBE PMDMAX
LSIOPCUR ODU4_TCMn_FEBBER PMDMIN
LSIOPMAX ODU4_TCMn_FEES SUMIOPCUR
LSIOPMIN ODU4_TCMn_FESES SUMIOPMAX
LSOOPCUR ODU4_TCMn_FESESR SUMIOPMIN
LSOOPMAX ODU4_TCMn_FEUAS TDCCUR
LSOOPMIN ODU4_TCMn_IAES TDCMAX
LSTMPCUR ODU4_TCMn_SES TDCMIN
LSTMPMAX ODU4_TCMn_SESR BDTEMPCUR
LSTMPMIN ODU4_TCMn_UAS BDTEMPMAX
ODU4_PM_BBE OTU4_BBE BDTEMPMIN
NOTE
TCM6.
NOTE
5.2.56 OAU1 Board Performance Event List


OptiX OSN 8800/6800/3800
5.2.57 OBU1 Board Performance Event List

5.2.58 OBU2 Board Performance Event List

5.2.59 OLP Board Performance Event List

LSIOPCUR SUMIOPCUR BDTEMPCUR
LSIOPMAX SUMIOPMAX BDTEMPMAX
LSIOPMIN SUMIOPMIN BDTEMPMIN
5.2.60 OPM8 Board Performance Event List

TN11OPM8

OptiX OSN 8800/6800/3800
PCLSOPCUR PCLSSNCUR BDTEMPCUR
PCLSOPMAX PCLSSNMAX BDTEMPMAX
PCLSOPMIN PCLSSNMIN BDTEMPMIN
5.2.61 PND2 Board Performance Event List

BDTEMPCUR LSOOPCUR ODU2_TCMn_FEBBE
BDTEMPMAX LSOOPMAX ODU2_TCMn_FEBBER
BDTEMPMIN LSOOPMIN ODU2_TCMn_FEES
ETH_CFM_CSLS LSTMPCUR ODU2_TCMn_FESES
ETH_CFM_LS LSTMPMAX ODU2_TCMn_FESESR
ETH_CFM_SLS LSTMPMIN ODU2_TCMn_FEUAS
ETH_CFM_UAS MPLS_PW_CSLS ODU2_TCMn_IAES
FEC_AFT_CORER_FLO
AT MPLS_PW_LS ODU2_TCMn_SES
FEC_AFT_COR_ER MPLS_PW_SLS ODU2_TCMn_SESR
FEC_AFT_COR_ERAV
R MPLS_PW_UAS ODU2_TCMn_UAS
FEC_BEF_CORER_FLO
AT ODU2_PM_BBE OTU2_BBE
FEC_BEF_COR_ER ODU2_PM_BBER OTU2_BBER
FEC_BEF_COR_ERAV
R ODU2_PM_ES OTU2_BIAES
FEC_COR_0BIT_CNT ODU2_PM_FEBBE OTU2_ES
FEC_COR_1BIT_CNT ODU2_PM_FEBBER OTU2_FEBBE
FEC_COR_BYTE_CNT ODU2_PM_FEES OTU2_FEBBER
FEC_UNCOR_BLOCK_
CNT ODU2_PM_FESES OTU2_FEES
LSBIASCUR ODU2_PM_FESESR OTU2_FESES
LSBIASMAX ODU2_PM_FEUAS OTU2_FESESR
LSBIASMIN ODU2_PM_SES OTU2_FEUAS
LSCLCCUR ODU2_PM_SESR OTU2_IAES

OptiX OSN 8800/6800/3800
LSCLCMAX ODU2_PM_UAS OTU2_SES
LSCLCMIN ODU2_TCMn_BBE OTU2_SESR
LSIOPCUR ODU2_TCMn_BBER OTU2_UAS
LSIOPMAX ODU2_TCMn_BIAES
LSIOPMIN ODU2_TCMn_ES
NOTE
TCM6.










OptiX OSN 8800/6800/3800




Number of reversely
Number of reversely

Number of reversely










OptiX OSN 8800/6800/3800



5.2.62 PTQX Board Performance Event List

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 ODU1_TCMn_FESESR OTU2_BBER

T
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

OptiX OSN 8800/6800/3800
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 BDTEMPCUR
ODU1_PM_FESESR ODU2_TCMn_BIAES BDTEMPMAX
ODU1_PM_FEUAS ODU2_TCMn_ES BDTEMPMIN
ODU1_PM_SES ODU2_TCMn_FEBBE
ODU1_PM_SESR ODU2_TCMn_FEBBER
NOTE
TCM6.
NOTE

Octets Received Octets in Length) Unicast Packets Received
Packets Received Packets Received (256~511 Unicast Packets Transmitted

Octets in Length)
Broadcast Packets Packets Received (512~1023 Multicast Packets Transmitted

Multicast Packets Packets Received (1024~1518 Broadcast Packets Transmitted

Undersize Packets Packets Transmitted (64 Pause Frames Received

Oversize Packets Packets Transmitted (65~127 Pause Frames Transmitted

Fragments Packets Transmitted (128~255 Alignment Errors

Octets in Length)
Jabbers Packets Transmitted (256~511 FCS Errors

Octets in Length)

OptiX OSN 8800/6800/3800
Packets Received (64 Packets Transmitted Packets Transmitted

Octets in Length) (512~1023 Octets in Length)
Packets Received Packets Transmitted Octets Transmitted

Length)
5.2.63 RAU1 Board Performance Event List

BCVCUR EDTMPMIN SUMOOPMAX
BCVMAX OOPRLCUR SUMOOPMIN
BCVMIN OOPRLMAX WCVCUR
CCVCUR OOPRLMIN WCVMAX
CCVMAX SUMIOPCUR WCVMIN
CCVMIN SUMIOPMAX BDTEMPCUR
EDTMPCUR SUMIOPMIN BDTEMPMAX
EDTMPMAX SUMOOPCUR BDTEMPMIN
5.2.64 RAU2 Board Performance Event List

BCVCUR EDTMPMIN SUMOOPMAX
BCVMAX OOPRLCUR SUMOOPMIN
BCVMIN OOPRLMAX WCVCUR
CCVCUR OOPRLMIN WCVMAX
CCVMAX SUMIOPCUR WCVMIN
CCVMIN SUMIOPMAX BDTEMPCUR
EDTMPCUR SUMIOPMIN BDTEMPMAX
EDTMPMAX SUMOOPCUR BDTEMPMIN
5.2.65 RDU9 Board Performance Event List

SUMIOPCUR SUMIOPMIN BDTEMPMAX
SUMIOPMAX BDTEMPCUR BDTEMPMIN

OptiX OSN 8800/6800/3800
5.2.66 RMU9 Board Performance Event List

ICTMPCUR SUMIOPMAX SUMOOPMIN
ICTMPMAX SUMIOPMIN BDTEMPCUR
ICTMPMIN SUMOOPCUR BDTEMPMAX
SUMIOPCUR SUMOOPMAX BDTEMPMIN
5.2.67 ROAM Board Performance Event List

ICTMPCUR LSOOPMIN SUMOOPMAX
ICTMPMAX SUMIOPCUR SUMOOPMIN
ICTMPMIN SUMIOPMAX BDTEMPCUR
LSOOPCUR SUMIOPMIN BDTEMPMAX
LSOOPMAX SUMOOPCUR BDTEMPMIN
5.2.68 SCC Board Performance Event List

TN16SCC
AVGFREQDEV MAXMEANPATHDELAY MINPHASEOFFSET
AVGMEANPATHDELA
Y MAXPHASEOFFSET BDTEMPCUR
AVGPHASEOFFSET MINFREQDEV BDTEMPMAX
MAXFREQDEV MINMEANPATHDELAY BDTEMPMIN
5.2.69 SC1 Board Performance Event List

CRC4BBE CRC4UAS LSOOPCUR
CRC4FEBBE LSBIASCUR LSOOPMAX
CRC4ES LSBIASMAX LSOOPMIN
CRC4FEES LSBIASMIN BDTEMPCUR

OptiX OSN 8800/6800/3800
CRC4FESES LSIOPCUR BDTEMPMAX
CRC4FEUAS LSIOPMAX BDTEMPMIN
CRC4SES LSIOPMIN
5.2.70 SC2 Board Performance Event List

CRC4BBE CRC4UAS LSOOPCUR
CRC4FEBBE LSBIASCUR LSOOPMAX
CRC4ES LSBIASMAX LSOOPMIN
CRC4FEES LSBIASMIN BDTEMPCUR
CRC4FESES LSIOPCUR BDTEMPMAX
CRC4FEUAS LSIOPMAX BDTEMPMIN
CRC4SES LSIOPMIN
5.2.71 SFD64 Board Performance Event List

AUPJCHIGH HPFEUAS OTU2SMBIP8
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 MSUAS TLBMAX

T
HPBBE ODU2PMBIP8 TLBMIN

OptiX OSN 8800/6800/3800
HPES OSPICCVCUR TPLCUR
HPCSES OSPICCVMAX TPLMAX
HPFEBBE OSPICCVMIN TPLMIN
HPFEES OSPITMPCUR BDTEMPCUR
HPFECSES OSPITMPMAX BDTEMPMAX
HPFESES OSPITMPMIN BDTEMPMIN
NOTE
5.2.72 SF64 Board Performance Event List

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
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 ODU2PMBIP8 TLBCUR

T
HPBBE OSPICCVCUR TLBMAX
HPES OSPICCVMAX TLBMIN
HPCSES OSPICCVMIN TPLCUR
HPFEBBE OSPITMPCUR TPLMAX
HPFEES OSPITMPMAX TPLMIN
HPFESES OSPITMPMIN BDTEMPCUR

OptiX OSN 8800/6800/3800
HPFECSES OTU2SMBIP8 BDTEMPMAX
HPFEUAS RPLCUR BDTEMPMIN
NOTE
5.2.73 SF64A Board Performance Event List

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 ODU2PMBIP8 TLBCUR

T
HPBBE OSPICCVCUR TLBMAX
HPES OSPICCVMAX TLBMIN
HPFEBBE OSPICCVMIN TPLCUR
HPFEES OSPITMPCUR TPLMAX
HPFESES OSPITMPMAX TPLMIN
HPFECSES OSPITMPMIN BDTEMPCUR
HPFEUAS OTU2SMBIP8 BDTEMPMAX
HPCSES RPLCUR BDTEMPMIN
HPSES RPLMAX
HPUAS RPLMIN
NOTE

OptiX OSN 8800/6800/3800
5.2.74 SL64 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 BDTEMPCUR
MSCSES RPLMAX BDTEMPMAX
MSES RPLMIN BDTEMPMIN
5.2.75 SLD64 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS

OptiX OSN 8800/6800/3800
5.2.76 SLH41 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.77 SLO16 Board Performance Event List


OptiX OSN 8800/6800/3800
HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.78 SLQ16 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS

OptiX OSN 8800/6800/3800
5.2.79 SLQ64 Board Performance Event List

HPBBE MSFESES RSOFS
HPES MSFEUAS RSOOF
HPCSES MSSES RSSES
HPFEBBE MSUAS RSUAS
5.2.80 ST2 Board Performance Event List

FEC_AFT_COR_ER LSIOPCUR OSC_FEBBE
FEC_AFT_COR_ERAVR LSIOPMAX OSC_FEBBER
FEC_AFT_CORER_FLOAT LSIOPMIN OSC_FEES
FEC_BEF_COR_ER LSOOPCUR OSC_FESES
FEC_BEF_COR_ERAVR LSOOPMAX OSC_FESESR

OptiX OSN 8800/6800/3800
FEC_BEF_CORER_FLOAT 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 OSC_BBE OSC_UAS

T
LSBIASCUR OSC_BBER BDTEMPCUR
LSBIASMAX OSC_BIAES BDTEMPMAX
LSBIASMIN OSC_ES BDTEMPMIN
NOTE
5.2.81 STG Board Performance Event List

AVGFREQDEV MAXMEANPATHDELAY MINPHASEOFFSET
AVGMEANPATHDELA
Y MAXPHASEOFFSET BDTEMPCUR
AVGPHASEOFFSET MINFREQDEV BDTEMPMAX
MAXFREQDEV MINMEANPATHDELAY BDTEMPMIN
5.2.82 SXM Board Performance Event List

5.2.83 SXH Board Performance Event List

5.2.84 TBE Board Performance Event List

LSBIASCUR LSOOPMAX RSES
LSBIASMAX LSOOPMIN RSOFS

OptiX OSN 8800/6800/3800
LSBIASMIN LSTMPCUR RSSES
LSIOPCUR LSTMPMAX RSUAS
LSIOPMAX LSTMPMIN BDTEMPCUR
LSIOPMIN RSBBE BDTEMPMAX
LSOOPCUR RSCSES BDTEMPMIN
Drop Events Octets Received Packets Received
Broadcast Packets Received Multicast Packets Received Undersize Packets

Received
Oversize Packets Received Fragments Jabbers
Packets Received (64 Octets in Packets Received (65~127 Packets Received

Length) Octets in Length) (128~255 Octets in
Length)

Length)
Packets Transmitted (64 Octets Packets Transmitted (65~127 Packets Transmitted

in Length) Octets in Length) (128~255 Octets in
Length)

Octets in Length) (512~1023 Octets in Length) (1024~1518 Octets in
Length)

Transmitted (64 Octets in Transmitted (65~127 Octets Transmitted (128~255
Length) in Length) Octets in Length)

Transmitted (256~511 Octets Transmitted (512~1023 Transmitted (1024~1518
in Length) Octets in Length) Octets in Length)

Transmitted
Broadcast Packets Transmitted Pause Frames Received Pause Frames Transmitted
FCS Errors Control Frames Received Control Frames

Transmitted
Oversize Packets Transmitted Packets Transmitted Octets Transmitted

OptiX OSN 8800/6800/3800
5.2.85 TD20 Board Performance Event List

BDTEMPCUR CCVMAX SUMIOPMIN
BDTEMPMAX CCVMIN SUMOOPCUR
BDTEMPMIN EDTMPCUR SUMOOPMAX
5.2.86 TDC Board Performance Event List

LSIOPCUR LSOOPCUR BDTEMPCUR
LSIOPMAX LSOOPMAX BDTEMPMAX
LSIOPMIN LSOOPMIN BDTEMPMIN
5.2.87 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 BDTEMPCUR
LSOOPMAX ODU1_PM_FEBBER BDTEMPMAX
LSOOPMIN ODU1_PM_FEES BDTEMPMIN

OptiX OSN 8800/6800/3800


Octets in Length) Octets in Length) (512~1023 Octets in Length)

Length) Length)


(512~1023 Octets in Length) (1024~1518 Octets in Length) (1519~MTU Octets in
Length)

Transmitted

Transmitted
5.2.88 TDX Board Performance Event List

TN53TDX
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

OptiX OSN 8800/6800/3800
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 RSSES
LSTMPMAX ODUFLEX_PM_BBER RSUAS
LSTMPMIN ODUFLEX_PM_ES BDTEMPCUR
ODU2_PM_BBE ODUFLEX_PM_FEBBE BDTEMPMAX
ODU2_PM_BBER ODUFLEX_PM_FEBBER BDTEMPMIN
ODU2_PM_ES ODUFLEX_PM_FEES
ODU2_PM_FEBBE ODUFLEX_PM_FESES
TN52TDX
FEC_AFT_COR_ERAV ODU2_PM_FEBBE OTU2_BBER

R
FEC_BEF_COR_ERAV ODU2_PM_FEES OTU2_ES

R
FEC_COR_1BIT_CNT ODU2_PM_FESESR OTU2_FEBBER

OptiX OSN 8800/6800/3800
FEC_COR_BYTE_CNT ODU2_PM_FEUAS OTU2_FEES
FEC_UNCOR_BLOCK_ ODU2_PM_SES OTU2_FESES

CNT
FEC_BEF_CORER_FL ODU2_PM_SESR OTU2_FESESR

OAT
FEC_AFT_CORER_FL ODU2_PM_UAS OTU2_FEUAS

OAT
LSIOPMIN ODU2_TCMn_FEBBER RSES
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

OptiX OSN 8800/6800/3800
LSIOPMIN ODU1_PM_FEES RSUAS
LSOOPCUR ODU1_PM_FESES BDTEMPCUR
LSOOPMAX ODU1_PM_FESESR BDTEMPMAX
LSOOPMIN ODU1_PM_FEUAS BDTEMPMIN
TN12TDX
LSIOPCUR ODU2_PM_FEBBE RSSES
LSIOPMAX ODU2_PM_FEBBER RSUAS
LSIOPMIN ODU2_PM_FEES BDTEMPCUR
LSOOPCUR ODU2_PM_FESES BDTEMPMAX
LSOOPMAX ODU2_PM_FESESR BDTEMPMIN
LSOOPMIN ODU2_PM_FEUAS
SEFS_S RSOFS
NOTE
TN53TDX
Packets Transmitted
(128~255 Octets in
Alignment Errors Octets Transmitted Length)
Packets Transmitted
Oversize Packets (1519~MTU Octets in
Bad Octets Received Received Length)

OptiX OSN 8800/6800/3800
Packets Transmitted
Oversize Packets (256~511 Octets in
Bad Octets Transmitted Transmitted Length)
Packets Transmitted
(512~1023 Octets in
Broadcast Packets Received Packets Received Length)
Packets Received
(1024~1518 Octets in Packets Transmitted (64
Broadcast Packets Transmitted Length) Octets in Length)
Packets Received
(128~255 Octets in Packets Transmitted
Control Frames Received Length) (65~127 Octets in Length)
Packets Received
(1519~MTU Octets in
Control Frames Transmitted Length) Pause Frames Received
Packets Received
(256~511 Octets in
FCS Errors Length) Pause Frames Transmitted
Packets Received
(512~1023 Octets in Undersize Packets
Fragments Length) Received
Packets Received (64

Jabbers Octets in Length) Unicast Packets Received
Packets Received (65~127 Unicast Packets

Multicast Packets Received Octets in Length) Transmitted
Multicast Packets Transmitted Packets Transmitted
Packets Transmitted
Octets Received Length)
TN52TDX
Packets Transmitted (128~255

Alignment Errors Octets Transmitted Octets in Length)
Bad Octets Oversize Packets Received Packets Transmitted (1519~MTU

Bad Octets Oversize Packets Transmitted Packets Transmitted (256~511

Broadcast Packets Packets Received Packets Transmitted (512~1023


OptiX OSN 8800/6800/3800
Broadcast Packets Packets Received (1024~1518 Packets Transmitted (64 Octets in

Received Octets in Length) Length)
Control Frames Packets Received (128~255 Packets Transmitted (65~127

Control Frames Packets Received (1519~MTU Pause Frames Transmitted

FCS Errors Packets Received (256~511 Pause Frames Received

Octets in Length)
Fragments Packets Received (512~1023 Undersize Packets Received

Octets in Length)
Jabbers Packets Received (64 Octets in Unicast Packets Transmitted

Length)
Multicast Packets Packets Received (65~127 Octets Unicast Packets Received

Received in Length)
Multicast Packets Packets Transmitted

Transmitted
Octets Received Packets Transmitted (1024~1518

Octets in Length)
TN11TDX
Broadcast Packets Received Multicast Packets Received FCS and Alignment Errors
Jabbers Packets Received (64 Packets Received (65~127



Length)


Length) Length)
Unicast Packets Received Unicast Packets Multicast Packets


OptiX OSN 8800/6800/3800

Transmitted
Bad Octets Transmitted FCS Errors Control Frames Received
Control Frames Transmitted Oversize Packets

Transmitted
TN12TDX
Octets Received Undersize Packets Received FCS Errors
Packets Received Oversize Packets Received
5.2.89 TEM28 Board Performance Event List

LSBIASCUR ODU0_PM_SES ODU2_PM_FESES
LSBIASMAX ODU0_PM_SESR ODU2_PM_FESESR
LSBIASMIN ODU0_PM_UAS ODU2_PM_FEUAS
LSIOPCUR ODU1_PM_BBE ODU2_PM_SES
LSIOPMAX ODU1_PM_BBER ODU2_PM_SESR
LSIOPMIN ODU1_PM_ES ODU2_PM_UAS
LSOOPCUR ODU1_PM_FEBBE ODUFLEX_PM_BBE
LSOOPMAX ODU1_PM_FEBBER ODUFLEX_PM_BBER
LSOOPMIN ODU1_PM_FEES ODUFLEX_PM_ES
LSTMPCUR ODU1_PM_FESES ODUFLEX_PM_FEBBE
LSTMPMAX ODU1_PM_FESESR ODUFLEX_PM_FEBBER
LSTMPMIN ODU1_PM_FEUAS ODUFLEX_PM_FEES
ODU0_PM_BBE ODU1_PM_SES ODUFLEX_PM_FESES
ODU0_PM_BBER ODU1_PM_SESR ODUFLEX_PM_FESESR
ODU0_PM_ES ODU1_PM_UAS ODUFLEX_PM_FEUAS
ODU0_PM_FEBBE ODU2_PM_BBE ODUFLEX_PM_SES
ODU0_PM_FEBBER ODU2_PM_BBER ODUFLEX_PM_SESR
ODU0_PM_FEES ODU2_PM_ES ODUFLEX_PM_UAS

OptiX OSN 8800/6800/3800
ODU0_PM_FESES ODU2_PM_FEBBE BDTEMPCUR
ODU0_PM_FESESR ODU2_PM_FEBBER BDTEMPMAX
ODU0_PM_FEUAS ODU2_PM_FEES BDTEMPMIN
Packets Received (64

FCS and Alignment Errors Octets Transmitted Octets in Length)
Packets Received
(65~127 Octets in
FCS Errors Broadcast Packets Transmitted Length)
Packets Transmitted
(128~255 Octets in
Drop Events Multicast Packets Transmitted Length)
Packets Received
Good Full Frame Octets (256~511 Octets in
Transmitted Good Full Frame Octets Received Length)
Packets Received
Good Full Frame Octets (512~1023 Octets in
Speed Transmitted Good Full Frame Octets Received Length)
Packets Received
Control Frames Transmitted Control Frames Received Length)
Packets Received and Transmitted Unicast Packets

Pause Frames Transmitted (64 Octets in Length) Received
Packets Received and Transmitted

Packets Transmitted (65~127 Octets in Length) Octets Received
Packets Transmitted (64 Packets Received and Transmitted Broadcast Packets

Octets in Length) (128~255 Octets in Length) Received
Packets Transmitted Packets Received and Transmitted

(65~127 Octets in Length) (256~511 Octets in Length) Fragments
Packets Transmitted Packets Received and Transmitted Multicast Packets

(128~255 Octets in Length) (512~1023 Octets in Length) Received
Packets Transmitted Packets Received and Transmitted Undersize Packets

(256~511 Octets in Length) (1024~1518 Octets in Length) Received
Packets Transmitted
(512~1023 Octets in Packets Received and Transmitted Oversize Packets
Length) (1519~MTU Octets in Length) Received

OptiX OSN 8800/6800/3800
Packets Transmitted
Length) Pause Frames Received Jabbers
Unicast Packets Transmitted Packets Received
5.2.90 THA Board Performance Event List

FEC_AFT_CORER_FLO
AT ODU0_PM_TMP 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_TMP
FEC_COR_BYTE_CNT ODU1_PM_FESES ODUFLEX_PM_UAS
FEC_TMP ODU1_PM_FESESR OTU1_BBE
FEC_UNCOR_BLOCK_
CNT ODU1_PM_FEUAS OTU1_BBER
LSBIASCUR ODU1_PM_SES OTU1_BIAES
LSBIASMAX ODU1_PM_SESR OTU1_ES
LSBIASMIN ODU1_PM_TMP 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

OptiX OSN 8800/6800/3800
LSTMPMAX ODU1_TCMn_FEES OTU1_SESR
LSTMPMIN ODU1_TCMn_FESES OTU1_TMP
ODU0_PM_BBE ODU1_TCMn_FESESR OTU1_UAS
ODU0_PM_BBER ODU1_TCMn_FEUAS RSBBE
ODU0_PM_ES ODU1_TCMn_IAES RSCSES
ODU0_PM_FEBBE ODU1_TCMn_SES RSES
ODU0_PM_FEBBER ODU1_TCMn_SESR RSSES
ODU0_PM_FEES ODU1_TCMn_TMP RSUAS
ODU0_PM_FESES ODU1_TCMn_UAS RS_TMP
ODU0_PM_FESESR ODUFLEX_PM_BBE BDTEMPCUR
ODU0_PM_FEUAS ODUFLEX_PM_BBER BDTEMPMAX
ODU0_PM_SES ODUFLEX_PM_ES BDTEMPMIN
ODU0_PM_SESR ODUFLEX_PM_FEBBE
NOTE
TCM6.
Bad Octets Packets Transmitted (1519~MTU

Received Multicast Packets Transmitted Octets in Length)
Bad Octets Oversize Packets Received Packets Transmitted (256~511

Broadcast Packets Oversize Packets Transmitted Packets Transmitted (512~1023


Drop Events Packets Received (128~255 Packets Transmitted (65~127

Drop Events at Packets Received (1519~MTU Pause Frames Transmitted

Transmission Octets in Length)
Direction

Octets in Length)

OptiX OSN 8800/6800/3800

Octets in Length)
Good Octets Packets Received (64 Octets in Unicast Packets Transmitted

Received Length)
Good Octets Packets Received (65~127 Octets Unicast Packets Received

Jabbers Packets Transmitted (1024~1518

Octets in Length)
Multicast Packets Packets Transmitted (128~255

5.2.91 TM20 Board Performance Event List

BDTEMPCUR ICTMPCUR SUMOOPCUR
BDTEMPMAX ICTMPMAX SUMOOPMAX
BDTEMPMIN ICTMPMIN SUMOOPMIN
5.2.92 TMX Board Performance Event List

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

OptiX OSN 8800/6800/3800
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
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 BDTEMPCUR
ODU1_PM_UAS ODU2_TCMn_SES BDTEMPMAX
ODU1_TCMn_BBE ODU2_TCMn_SESR BDTEMPMIN
NOTE
TCM6.
NOTE

OptiX OSN 8800/6800/3800
5.2.93 TOA Board Performance Event List

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

OptiX OSN 8800/6800/3800
ODU0_PM_FEBBER ODU1_TCMn_SESR RSUAS
ODU0_PM_FEES ODU1_TCMn_UAS BDTEMPCUR
ODU0_PM_FESES ODUFLEX_PM_BBE BDTEMPMAX
ODU0_PM_FESESR ODUFLEX_PM_BBER BDTEMPMIN
ODU0_PM_FEUAS ODUFLEX_PM_ES
ODU0_PM_SES ODUFLEX_PM_FEBBE
NOTE
TCM6.
Bad Octets Packets Transmitted (1519~MTU

Received Multicast Packets Transmitted Octets in Length)





Direction

Octets in Length)

Octets in Length)

Received Length)
Good Octets Packets Received (65~127 Octets Unicast Packets Received

Jabbers Packets Transmitted (1024~1518

Octets in Length)


OptiX OSN 8800/6800/3800
5.2.94 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 BDTEMPCUR
LSTMPMIN ODU1_PM_BBE BDTEMPMAX
ODU0_PM_BBE ODU1_PM_BBER BDTEMPMIN
Bad Octets Received Packets Received(512~1023

Multicast Packets Received Octets in Length)
Broadcast Packets Packets Received(64 Octets in

Received Oversize Packets Received Length)
FCS Errors Packets Received(1024~1518 Packets Received(65~127 Octets

Octets in Length) in Length)
Fragments Packets Received(128~255 Pause Frames Received

Octets in Length)
Good Octets Received Packets Received(1519~MTU Undersize Packets Received

Octets in Length)
Jabbers Packets Received(256~511 Unicast Packets Received

Octets in Length)
Drop Events
TN54TOG

OptiX OSN 8800/6800/3800
Bad Octets Received Packets Received (512~1023

Multicast Packets Received Octets in Length)
Broadcast Packets Packets Received (64 Octets in

Received Oversize Packets Received Length)
FCS Errors Packets Received (1024~1518 Packets Received (65~127 Octets

Octets in Length) in Length)
Fragments Packets Received (128~255 Pause Frames Received

Octets in Length)
Good Octets Received Packets Received (1519~MTU Undersize Packets Received

Octets in Length)
Jabbers Packets Received (256~511 Unicast Packets Received

Octets in Length)
Packets Transmitted Packets Transmitted (512~1023 Unicast Packets Transmitted

(64 Octets in Length) Octets in Length)
Packets Transmitted Packets Transmitted Multicast Packets Transmitted

Length)
Packets Transmitted Packets Transmitted Broadcast Packets Transmitted

(128~255 Octets in (1519~MTU Octets in Length)
Length)
Packets Transmitted Good Octets Transmitted Pause Frames Transmitted

(256~511 Octets in
Length)
Drop Events Bad Octets Transmitted
Drop Events at Oversize Packets Transmitted

Transmission
Direction
5.2.95 TOM Board Performance Event List

TN52TOM
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

OptiX OSN 8800/6800/3800
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 ODU1_PM_FEBBE OTU1_UAS

T
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
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 BDTEMPCUR
ODU0_PM_FEBBE ODU1_TCMn_FESES BDTEMPMAX
ODU0_PM_FEBBER ODU1_TCMn_FESESR BDTEMPMIN
ODU0_PM_FEES ODU1_TCMn_FEUAS
TN11TOM
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

OptiX OSN 8800/6800/3800
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
LSTMPMAX ODU1_TCMn_FESESR RSES
LSTMPMIN ODU1_TCMn_FEUAS RSSES
ODU1_PM_BBE ODU1_TCMn_IAES RSUAS
ODU1_PM_BBER ODU1_TCMn_SES BDTEMPCUR
ODU1_PM_ES ODU1_TCMn_SESR BDTEMPMAX
ODU1_PM_FEBBE ODU1_TCMn_UAS BDTEMPMIN
SEFS_S RSOFS
NOTE
TCM6.
TN52TOM
Packets Transmitted (1519~MTU

Bad Octets Received Multicast Packets Transmitted Octets in Length)




OptiX OSN 8800/6800/3800


Direction

Octets in Length)

Octets in Length)

Transmitted Length)
Good Octets Received Packets Received (65~127 Unicast Packets Received

Octets in Length)
Jabbers Packets Transmitted


TN11TOM
Packets Received

Length)
Undersize Packets Received Packets Transmitted(64 Pause Frames Received

Octets in Length)
Oversize Packets Received Packets Transmitted(65~127 Pause Frames



Packets Received(64 Octets in Packets Transmitted Bad Octets Received

Packets Received(65~127 Octets Packets Transmitted Bad Octets Transmitted

in Length) (1024~1518 Octets in
Length)

OptiX OSN 8800/6800/3800
Packets Received(128~255 Packets Transmitted FCS Errors

Octets in Length) (1519~MTUOctets in
Length)
Packets Received(256~511 Unicast Packets Received Drop Events at

Packets Received(512~1023 Unicast Packets Transmitted Oversize Packets

Drop Events
5.2.96 TOX Board Performance Event List

TN55TOX
FEC_AFT_CORER_FLO
AT ODU2_PM_ES OTU2_BBE
FEC_AFT_COR_ER ODU2_PM_FEBBE OTU2_BBER
FEC_AFT_COR_ERAV
R ODU2_PM_FEBBER OTU2_BIAES
FEC_BEF_CORER_FLO
AT ODU2_PM_FEES OTU2_ES
FEC_BEF_COR_ER ODU2_PM_FESES OTU2_FEBBE
FEC_BEF_COR_ERAV
R ODU2_PM_FESESR OTU2_FEBBER
FEC_UNCOR_BLOCK_
CNT ODU2_PM_UAS OTU2_FEUAS

OptiX OSN 8800/6800/3800
LSOOPMAX ODU2_TCMn_FESES RSOFS
NOTE
TCM6.
Packets Received, 64 Octets in

FCS Errors Length Octets Transmitted

Alignment Errors Octets in Length Pause Frames Transmitted
Packets Received, 128~255 Packets Transmitted, 64 Octets

Control Frames Received Octets in Length in Length
Control Frames Packets Received, 256~511 Packets Transmitted, 65~127

Transmitted Octets in Length Octets in Length


Oversize Packets Packets Received, Packets Transmitted,

Received 1519~MTU Octets in Length 512~1023 Octets in Length
Undersize Packets Packets Transmitted,

Received Packets Received 1024~1518 Octets in Length
Bad Octets Received Unicast Packets Received 1519~MTU Octets in Length
Broadcast Packets
Received Bad Octets Transmitted Packets Transmitted
Multicast Packets Broadcast Packets

Received Transmitted Unicast Packets Transmitted
Octets Received Oversize Packets Transmitted

OptiX OSN 8800/6800/3800
Pause Frames Received Multicast Packets Transmitted
5.2.97 TQM Board Performance Event List

TN11TQM
LSBIASCUR LSTMPMIN ODU1_PM_SESR
LSBIASMAX ODU1_PM_BBE ODU1_PM_UAS
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 BDTEMPCUR
LSOOPMIN ODU1_PM_FESESR BDTEMPMAX
LSTMPCUR ODU1_PM_FEUAS BDTEMPMIN
LSTMPMAX ODU1_PM_SES
TN12TQM
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_1BIT_CNT ODU1_PM_FEUAS OTU1_FEBBER
FEC_COR_BYTE_CNT ODU1_PM_SES OTU1_FEES
FEC_UNCOR_BLOCK_C ODU1_PM_SESR OTU1_FESES

NT
LSBIASCUR ODU1_PM_UAS OTU1_FESESR
LSBIASMAX ODU1_TCMn_BBE OTU1_FEUAS
LSBIASMIN ODU1_TCMn_BBER OTU1_IAES

OptiX OSN 8800/6800/3800
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
LSTMPMIN ODU1_TCMn_IAES BDTEMPCUR
ODU1_PM_BBE ODU1_TCMn_SES BDTEMPMAX
ODU1_PM_BBER ODU1_TCMn_SESR BDTEMPMIN
ODU1_PM_ES ODU1_TCMn_UAS
SEFS_S RSOFS
NOTE
TN11TQM
Multicast Packets
Drop Events Broadcast Packets Received Received
FCS Errors Undersize Packets Received Oversize Packets Received
Fragments Jabbers Packets Received (64

Octets in Length)

Length)
Packets Received Packets Received (1024~1518 Packets Received

(512~1023 Octets in Length) Octets in Length) (1519~MTU Octets in
Length)
Packets Transmitted (64 Packets Transmitted (65~127 Packets Transmitted

Length)

OptiX OSN 8800/6800/3800
Packets Transmitted Packets Transmitted (512~1023 Packets Transmitted

(256~511 Octets in Length) Octets in Length) (1024~1518 Octets in
Length)
Packets Transmitted Unicast Packets Received Unicast Packets

Length)
Multicast Packets Broadcast Packets Transmitted Pause Frames Received

Transmitted
Bad Octets Received Bad Octets Transmitted Drop Events at

Transmission Direction
Oversize Packets
Transmitted
TN12TQM
Packets Received

Length)

Octets in Length)





Length)

Length)

OptiX OSN 8800/6800/3800


5.2.98 TQS Board Performance Event List

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_1BIT_CNT ODU1_PM_FEUAS OTU1_FEBBER
FEC_COR_BYTE_CNT ODU1_PM_SES OTU1_FEES
FEC_UNCOR_BLOCK_C ODU1_PM_SESR OTU1_FESES

NT
LSBIASCUR ODU1_PM_UAS OTU1_FESESR
LSBIASMAX ODU1_TCMn_BBE OTU1_FEUAS
LSBIASMIN ODU1_TCMn_BBER OTU1_IAES
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 BDTEMPCUR
ODU1_PM_BBER ODU1_TCMn_SESR BDTEMPMAX
ODU1_PM_ES ODU1_TCMn_UAS BDTEMPMIN

OptiX OSN 8800/6800/3800
NOTE
TCM6.
NOTE
5.2.99 TQX Board Performance Event List

TN55TQX
FEC_AFT_CORER_FLO
AT ODU2_PM_FEES ODUFLEX_PM_FEUAS
FEC_AFT_COR_ER ODU2_PM_FESES ODUFLEX_PM_SES
FEC_AFT_COR_ERAV
R ODU2_PM_FESESR ODUFLEX_PM_SESR
FEC_BEF_CORER_FLO
AT ODU2_PM_FEUAS ODUFLEX_PM_TMP
FEC_BEF_COR_ER ODU2_PM_SES ODUFLEX_PM_UAS
FEC_BEF_COR_ERAV
R ODU2_PM_SESR OTU2_BBE
FEC_COR_0BIT_CNT ODU2_PM_TMP OTU2_BBER
FEC_COR_1BIT_CNT ODU2_PM_UAS OTU2_BIAES
FEC_COR_BYTE_CNT ODU2_TCMn_BBE OTU2_ES
FEC_TMP ODU2_TCMn_BBER OTU2_FEBBE
FEC_UNCOR_BLOCK_
CNT ODU2_TCMn_BIAES OTU2_FEBBER
LSBIASCUR ODU2_TCMn_ES OTU2_FEES
LSBIASMAX ODU2_TCMn_FEBBE OTU2_FESES
LSBIASMIN ODU2_TCMn_FEBBER OTU2_FESESR
LSCLCCUR ODU2_TCMn_FEES OTU2_FEUAS
LSCLCMAX ODU2_TCMn_FESES OTU2_IAES
LSCLCMIN ODU2_TCMn_FESESR OTU2_SES
LSIOPCUR ODU2_TCMn_FEUAS OTU2_SESR
LSIOPMAX ODU2_TCMn_IAES OTU2_TMP
LSIOPMIN ODU2_TCMn_SES OTU2_UAS
LSOOPCUR ODU2_TCMn_SESR RSBBE

OptiX OSN 8800/6800/3800
LSOOPMAX ODU2_TCMn_TMP 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 RS_TMP
ODU2_PM_BBER ODUFLEX_PM_FEBBER BDTEMPCUR
ODU2_PM_ES ODUFLEX_PM_FEES BDTEMPMAX
ODU2_PM_FEBBE ODUFLEX_PM_FESES BDTEMPMIN
ODU2_PM_FEBBER ODUFLEX_PM_FESESR
TN53TQX
FEC_AFT_CORER_FLO
AT ODU2_PM_BBE ODU2_TCMn_UAS
FEC_AFT_COR_ERAV
R ODU2_PM_ES OTU2_BBER
FEC_BEF_CORER_FLO
AT ODU2_PM_FEBBE OTU2_BIAES
FEC_BEF_COR_ERAV
R ODU2_PM_FEES OTU2_FEBBE
FEC_UNCOR_BLOCK_
CNT ODU2_PM_SES OTU2_FESESR

OptiX OSN 8800/6800/3800
TN52TQX
FEC_AFT_COR_ERAV ODU2_PM_FEBBE OTU2_BBER

R
FEC_BEF_COR_ERAV ODU2_PM_FEES OTU2_ES

R
FEC_COR_1BIT_CNT ODU2_PM_FESESR OTU2_FEBBER
FEC_COR_BYTE_CNT ODU2_PM_FEUAS OTU2_FEES
FEC_UNCOR_BLOCK_ ODU2_PM_SES OTU2_FESES

CNT
FEC_BEF_CORER_FL ODU2_PM_SESR OTU2_FESESR

OAT
FEC_AFT_CORER_FL ODU2_PM_UAS OTU2_FEUAS

OAT

OptiX OSN 8800/6800/3800
LSIOPMIN ODU2_TCMn_FEBBER RSES
ODU2_PM_BBE ODU2_TCMn_SESR SEFS_S
ODU2_PM_BBER ODU2_TCMn_UAS RSOFS
TN11TQX
LSIOPCUR ODU2_PM_FEBBE RSSES
LSIOPMAX ODU2_PM_FEBBER RSUAS
LSIOPMIN ODU2_PM_FEES BDTEMPCUR
LSOOPCUR ODU2_PM_FESES BDTEMPMAX
LSOOPMAX ODU2_PM_FESESR BDTEMPMIN
LSOOPMIN ODU2_PM_FEUAS
SEFS_S RSOFS
NOTE
TN55TQX

OptiX OSN 8800/6800/3800








Octets in Length)

Octets in Length)

Length)

Received in Length)

Transmitted

Octets in Length)
TN53TQX





OptiX OSN 8800/6800/3800




Octets in Length)

Octets in Length)

Length)

Received in Length)

Transmitted

Octets in Length)
TN52TQX








Octets in Length)

OptiX OSN 8800/6800/3800

Octets in Length)

Length)

Received in Length)

Transmitted

Octets in Length)
TN11TQX
Undersize Packets
Octets Received Received FCS Errors
Packets Received Oversize Packets Received
5.2.100 TSXL Board Performance Event List

TN11TSXL
LSIOPCUR ODU2_PM_FEBBE RSOFS
LSIOPMAX ODU2_PM_FEBBER RSSES
LSIOPMIN ODU2_PM_FEES RSUAS
LSOOPCUR ODU2_PM_FESES BDTEMPCUR
LSOOPMAX ODU2_PM_FESESR BDTEMPMAX
LSOOPMIN ODU2_PM_FEUAS BDTEMPMIN
TN53TSXL

OptiX OSN 8800/6800/3800
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_UNCOR_BLOCK_CN ODU3_PM_UAS OTU3_FEUAS

T
LSOOPMAX ODU3_TCMn_FESES RSOFS
TN54TSXL
ODU3_PM_BBE ODU3_PM_UAS VALLEY_INPOWER_MAX
ODU3_PM_BBER PEAK_INPOWER_CUR VALLEY_INPOWER_MIN
ODU3_PM_ES PEAK_INPOWER_MAX VALLEY_LSBIAS_CUR

OptiX OSN 8800/6800/3800
ODU3_PM_FEBBE PEAK_INPOWER_MIN VALLEY_LSBIAS_MAX
ODU3_PM_FEBBER PEAK_LSBIAS_CUR VALLEY_LSBIAS_MIN
VALLEY_OUTPOWER_CU
ODU3_PM_FEES PEAK_LSBIAS_MAX R
VALLEY_OUTPOWER_M
ODU3_PM_FESES PEAK_LSBIAS_MIN AX
VALLEY_OUTPOWER_MI
ODU3_PM_FESESR PEAK_OUTPOWER_CUR N
ODU3_PM_FEUAS PEAK_OUTPOWER_MAX BDTEMPCUR
ODU3_PM_SES PEAK_OUTPOWER_MIN BDTEMPMAX
ODU3_PM_SESR VALLEY_INPOWER_CUR BDTEMPMIN
NOTE
TCM6.
Unicast Packets
FCS Errors Good Octets Transmitted Received
Pause Frames Transmitted Broadcast Packets Transmitted Good Octets Received
Packets Transmitted (64

Octets in Length) Multicast Packets Transmitted Bad Octets Received
Packets Transmitted Broadcast Packets

(65~127 Octets in Length) Pause Frames Received Received
Packets Transmitted Packets Received (64 Octets in

(128~255 Octets in Length) Length) Fragments
Packets Transmitted Packets Received (65~127 Octets Multicast Packets

(256~511 Octets in Length) in Length) Received
Packets Transmitted
(512~1023 Octets in Packets Received (128~255 Octets Undersize Packets
Packets Transmitted
(1024~1518 Octets in Packets Received (256~511 Octets Oversize Packets
Packets Transmitted
(1519~MTU Octets in Packets Received (512~1023
Length) Octets in Length) Jabbers

OptiX OSN 8800/6800/3800

Packets Received (1519~MTU

Bad Octets Transmitted Octets in Length)
5.2.101 USXH Board Performance Event List

5.2.102 UXCH Board Performance Event List

5.2.103 UXCM Board Performance Event List

5.2.104 UXCT Board Performance Event List

5.2.105 VA1 Board Performance Event List

TN11VA1
TN12VA1

OptiX OSN 8800/6800/3800
5.2.106 VA4 Board Performance Event List

TN11VA4
ICTMPCUR ICTMPMIN BDTEMPMAX
ICTMPMAX BDTEMPCUR BDTEMPMIN
TN12VA4
5.2.107 WMU Board Performance Event List

PCLSOPCUR PCLSWLMAX PCLSWLOMIN
PCLSOPMAX PCLSWLMIN BDTEMPCUR
PCLSOPMIN PCLSWLOCUR BDTEMPMAX
PCLSWLCUR PCLSWLOMAX BDTEMPMIN
5.2.108 WSD9 Board Performance Event List

5.2.109 WSM9 Board Performance Event List

ICTMPCUR SUMOOPCUR BDTEMPCUR
ICTMPMAX SUMOOPMAX BDTEMPMAX
ICTMPMIN SUMOOPMIN BDTEMPMIN
5.2.110 WSMD2 Board Performance Event List


OptiX OSN 8800/6800/3800


5.2.113 XCH Board Performance Event List

TN16XCH
MAXFREQDEV MINFREQDEV AVGFREQDEV
MAXPHASEOFFSET MINPHASEOFFSET AVGPHASEOFFSET
MAXMEANPATHDELAY MINMEANPATHDELAY AVGMEANPATHDELAY
TN52XCH

OptiX OSN 8800/6800/3800
5.2.114 XCM Board Performance Event List

TN52XCM
5.2.115 XCT Board Performance Event List


OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 6 Handling Performance Event
6 Handling Performance Event
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 the value of a performance event exceeds the threshold, related alarms are generated.
Therefore, in case of a performance event, check the related alarms and handle the alarms
accordingly.
The following describes the meanings of the n and k in this topic:
l k indicates the level of rate and its value is 1, 2, 3 and 5G.
l n indicates the level of TCM and its value ranges from 1 to 6.
6.1 AUPJCHIGH
6.2 AUPJCLOW
6.3 AUPJCNEW
6.4 BCV
6.5 BDTEMP
6.6 CCV
6.7 CRC4ES
6.8 CRC4FEES
6.9 CRC4FESES
6.10 CRC4FEUAS
6.11 CRC4SES
6.12 CRC4UAS
6.13 DGD
6.14 EDRPL

OptiX OSN 8800/6800/3800
6.15 EDTMP
6.16 EDTPL
6.17 EDWCS
6.18 ENVTMP
6.19 ETH_CFM_LS
6.20 ETH_CFM_SLS
6.21 ETH_CFM_CSLS
6.22 ETH_CFM_UAS
6.23 FEC_AFT_COR_ER
6.24 FEC_AFT_COR_ERAVR
6.25 FEC_AFT_CORER_FLOAT
6.26 FEC_BEF_COR_ER
6.27 FEC_BEF_COR_ERAVR
6.28 FEC_BEF_CORER_FLOAT
6.29 FEC_COR_0BIT_CNT
6.31 FEC_COR_BYTE_CNT
6.32 FEC_TMP
6.33 FEC_UNCOR_BLOCK_CNT
6.34 FREQDEV
6.35 HPBBE
6.36 HPCSES
6.37 HPES
6.38 HPFEBBE
6.39 HPFECSES
6.40 HPFEES
6.41 HPFESES
6.42 HPFEUAS
6.43 HPSES
6.44 HPUAS
6.45 ICCLC
6.46 ICTMP

OptiX OSN 8800/6800/3800
6.47 LSBIAS
6.48 LSCLC
6.49 LSIOP
6.50 LSOOP
6.51 LSTMP
6.52 MEANPATHDELAY
6.53 MPLS_PW_LS
6.54 MPLS_PW_SLS
6.55 MPLS_PW_CSLS
6.56 MPLS_PW_UAS
6.57 MSBBE
6.58 MSCSES
6.59 MSES
6.60 MSFEBBE
6.61 MSFECSES
6.62 MSFEES
6.63 MSFESES
6.64 MSFEUAS
6.65 MSSES
6.66 MSUAS
6.67 ODU2PMBIP8
6.68 ODUk_PM_BBE
6.69 ODUk_PM_BBER
6.70 ODUk_PM_ES
6.71 ODUk_PM_FEBBE
6.72 ODUk_PM_FEBBER
6.73 ODUk_PM_FEES
6.74 ODUk_PM_FESES
6.75 ODUk_PM_FESESR
6.76 ODUk_PM_FEUAS
6.77 ODUk_PM_SES
6.78 ODUk_PM_SESR

OptiX OSN 8800/6800/3800
6.79 ODUk_PM_TMP
6.80 ODUk_PM_UAS
6.81 ODUk_TCMn_BBE
6.82 ODUk_TCMn_BBER
6.83 ODUk_TCMn_BIAES
6.84 ODUk_TCMn_ES
6.85 ODUk_TCMn_FEBBE
6.86 ODUk_TCMn_FEBBER
6.87 ODUk_TCMn_FEES
6.88 ODUk_TCMn_FESES
6.89 ODUk_TCMn_FESESR
6.90 ODUk_TCMn_FEUAS
6.91 ODUk_TCMn_IAES
6.92 ODUk_TCMn_SES
6.93 ODUk_TCMn_SESR
6.94 ODUk_TCMn_TMP
6.95 ODUk_TCMn_UAS
6.96 OOPRL
6.97 OSC_BBE
6.98 OSC_BBER
6.99 OSC_BIAES
6.100 OSC_ES
6.101 OSC_FEBBE
6.102 OSC_FEBBER
6.103 OSC_FEES
6.104 OSC_FESES
6.105 OSC_FESESR
6.106 OSC_FEUAS
6.107 OSC_IAES
6.108 OSC_SES
6.109 OSC_SESR
6.110 OSC_UAS

OptiX OSN 8800/6800/3800
6.111 OSPICCV
6.112 OSPITMP
6.113 OTU2SMBIP8
6.114 OTUk_BBE
6.115 OTUk_BBER
6.116 OTUk_BIAES
6.117 OTUk_ES
6.118 OTUk_FEBBE
6.119 OTUk_FEBBER
6.120 OTUk_FEES
6.121 OTUk_FESES
6.122 OTUk_FESESR
6.123 OTUk_FEUAS
6.124 OTUk_IAES
6.125 OTUk_SES
6.126 OTUk_SESR
6.127 OTUk_TMP
6.128 OTUk_UAS
6.129 PCLSOP
6.130 PCLSSN
6.131 PCLSWL
6.132 PCLSWLO
6.133 PHASEOFFSET
6.134 RMIOP
6.135 RPL
6.136 RS_TMP
6.137 RSBBE
6.138 RSCSES
6.139 RSES
6.140 RSOFS
6.141 RSOOF
6.142 RSSES

OptiX OSN 8800/6800/3800
6.143 RSUAS
6.144 SUMIOP
6.145 SUMOOP
6.146 TDC
6.147 TLB
6.148 TPL
6.149 VC3BBE
6.150 VC3CSES
6.151 VC3ES
6.152 VC3FEBBE
6.153 VC3FECSES
6.154 VC3FEES
6.155 VC3FESES
6.156 VC3FEUAS
6.157 VC3SES
6.158 VC3UAS
6.159 WCV

OptiX OSN 8800/6800/3800
6.1 AUPJCHIGH
Description
Positive justification count of the administrative unit (AU) pointer.
Impact on System
A small number of positive justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.
Generation Principle and Possible Causes

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
asynchronous. The possible causes of the event are as follows:
l The performance of the external clock deteriorates.
l The clocks on two NEs trace each other because optical fibers are connected incorrectly.
l The equipment performance deteriorates due to high temperature.
l The clocks are configured incorrectly. If the extended SSM protocol is enabled but clock
IDs are not set, the loss of the primary clock source causes the network-wide pointer
justification event.
l The clock quality deteriorates because the SSM clock protection is disabled.
l The performance of the line board deteriorates.
l The performance of the clock board deteriorates.
Related Alarms
None.
Procedure
Step 1 Check whether clock alarms, such as SYN_BAD, LTI, S1_SYN_CHANGE, and
EXT_SYNC_LOS, are generated on the entire network. If yes, clear them first.
Step 2 For network-wide pointer justification, check whether clock configurations are the same as
planned. The configurations to be checked include the clock ID, SSM protocol, and clock tracing
level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are correctly connected,
and whether the ambient temperature of the equipment is within the permitted range. If the AU
pointer justification event occurs continuously, contact Huawei for assistance.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
6.2 AUPJCLOW
Description
Negative justification count of the administrative unit (AU) pointer
Impact on System
A small number of negative justification events of the AU pointer occur in the data segment,
which does not affect the system. If the pointer justification event occurs frequently, you need
to check the causes and rectify the frequent adjustments so that the system runs stably.

The root cause of the AU pointer justification is that the clocks of NEs in the SDH network are
asynchronous. The possible causes of the event are as follows:
Related Alarms
None.
Procedure
level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are correctly connected,
----End
Related Information
None.

OptiX OSN 8800/6800/3800
6.3 AUPJCNEW
Description
New count of the administrative unit (AU) pointer
Impact on System
A new count of AU pointers is generated, which does not affect the system. If a new count of
AU pointers is generated frequently, you need to check the causes and rectify the frequent
adjustments so that the system runs stably.

The root cause of generating new data flag (pointer) for the AU pointer justification event is that
the clocks of NEs on the SDH network are asynchronous. As a result, the new AU data flag
(pointer) event is generated. The possible causes are as follows:

Related Alarms
None.
Procedure
level.
Step 3 For non-network-wide pointer justification, check whether optical fibers are connected correctly,
----End

OptiX OSN 8800/6800/3800
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.

l BCVMIN: stands for the minimum value during a period of time.
l 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. When this occurs, replace the board where this faulty laser resides.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.5 BDTEMP
Description
Board temperature. It contains the BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR, which
respectively indicates the maximum value, minimum value, and current value of the temperature
of a board.

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.

When the ambient temperature is abnormal, or when the heat-sinking and ventilation measures
are inappropriate, the BDTEMP event occurs.
Related Alarms
Alarm Name Correlation
TEMP_OVER This alarm is reported when the board temperature exceeds

the threshold.
Procedure
Step 1 If any alarm occurs, handle the alarm by referring to the alarm handling procedure.
----End
Related Information
None.
6.6 CCV
Description
Pump laser cooling current
It includes:
l CCVMAX: stands for the maximum value during a period of time.

l CCVMIN: stands for the minimum value during a period of time.
l CCVCUR: stands for the current value.
Impact on System
None

An A/D converter is used 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 laser.

OptiX OSN 8800/6800/3800
Related Alarms
PUMP_COOL_EXC This alarm is generated when the cooling

current of the laser exceeds the permitted
range.
Procedure
Step 1 If the PUMP_COOL_EXC alarm is generated, handle the alarm by referring to the alarm
handling procedure.
----End
Related Information
None
6.7 CRC4ES
Description
CRC4 errored seconds
Impact on System
There are bit errors in the services. If the CRC4 errored seconds are generated continuously,
identify the cause and solve the problem in a timely manner to avoid any alarm, therefore
ensuring the signal transmission quality.

CRC error is detected by checking the received parity bit. An errored second contains more than
one error block.
Related Alarms
CRC4_CROSSTR CRC4 multi-frame error code exceeds the

threshold. This alarm is generated when the
number of bit errors in the CRC4 multi-frame
exceeds the threshold.

OptiX OSN 8800/6800/3800
Procedure
Step 1 See the procedure for handling the CRC4_CROSSTR alarm.
----End
Related Information
None
6.8 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,
ensuring 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
CRC4_CROSSTR CRC4 multi-frame error code counter

exceeds the threshold. This alarm is generated
when the number of bit errors in the CRC4
multiframe exceeds the threshold.
Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.9 CRC4FESES
Description
CRC4 far end severely errored second
Impact on System
There are many bit errors in the services. Identify the cause and solve the problem in a timely
manner to avoid any alarm, and therefore ensuring 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 or 15% of the 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
CRC4_CROSSTR CRC4 multi-frame error code count exceeds

the threshold. This alarm is generated when
the number of bit errors in the CRC4
Procedure
----End
Related Information
None
6.10 CRC4FEUAS
Description
CRC4 far end unavailable second

OptiX OSN 8800/6800/3800
Impact on System
There are bit errors in the services. Identify the cause and solve the problem in a timely manner
because the bit errors have affected 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. 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
CRC4_CROSSTR CRC4 multi-frame bit error count exceeds the

threshold. This alarm is generated when the
number of bit errors in the CRC4 multiframe
exceeds the threshold.
Procedure
----End
Related Information
None
6.11 CRC4SES
Description
CRC4 severely errored second
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 15% of the data blocks are error blocks.

OptiX OSN 8800/6800/3800
Related Alarms

Procedure
----End
Related Information
None
6.12 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.
Related Alarms


OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.13 DGD
Description
Polarization mode dispersion
It includes:
l DGDMAX: stands for the maximum value.

l DGDMIN: stands for the minimum value.
l DGDCUR: stands for the current value.
l DGDAVG: stands for the average value.
Impact on System
None

The polarization mode dispersion is caused by imperfect symmetry of cross-sectional area of a
fiber.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.14 EDRPL
Description
EDFA input optical power
It includes:
l EDRPLMAX: stands for the maximum value during a period of time.

l EDRPLMIN: stands for the minimum value during a period of time.
l EDRPLCUR: stands for the current value.
Impact on System
When the input optical power is excessively high or very 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
EDPRL to show the input optical power performance of the EDFA module.
Related Alarms
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
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_LOW alarm.
Step 3 If an alarm is generated, see the alarm handling procedure.
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.15 EDTMP
Description
Laser temperature value
It includes:
l EDTMPMAX: stands for the maximum value during a period of time.

l EDTMPMIN: stands for the minimum value during a period of time.
l 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 within the permitted range, the EDFA
module might be faulty.
Related Alarms
PUM_TEM_ALM The working temperature of the pump laser exceeds the threshold.
This alarm is generated when the pump laser operating temperature
of the optical amplifier board exceeds the threshold.
Procedure
Step 1 See the procedure for handling the PUM_TEM_ALM alarm.
----End
Related Information
None
6.16 EDTPL
Description
Pump output optical power
It includes:

OptiX OSN 8800/6800/3800
l EDTPLMAX: stands for the maximum value during a period of time.

l EDTPLMIN: stands for the minimum value during a period of time.
l EDTPLCUR: stands for the current value.
Impact on System
Bit errors may be generated in the services and the services may be interrupted.

by the software for conversion. If the performance is not within the permitted range, the EDFA
module might be faulty.
Related Alarms
OUT_PWR_HIGH This alarm is generated when the optical power output by the pump
laser is higher than the upper threshold.
OUT_PWR_LOW This alarm is generated when the optical power output by the pump
laser is lower than the lower threshold.
Procedure
Step 1 See the procedure for handling the OUT_PWR_HIGH or OUT_PWR_LOW alarm.
----End
Related Information
None
6.17 EDWCS
Description
Value of EDFA working current setup
It includes:
l EDWCSMAX: stands for the maximum value during a period of time.
l EDWCSMIN: stands for the minimum value during a period of time.
l EDWCSCUR: stands for the current value.
Impact on System
None.

OptiX OSN 8800/6800/3800

Stands for the maximum, minimum and current value of EDFA working current setup during a
period of time.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.18 ENVTMP
Description
Board ambient temperature
It includes:
l ENVTMPMAX: stands for the maximum value during a period of time.

l ENVTMPMIN: stands for the minimum value during a period of time.
l 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
TEMP_OVER This alarm is generated when the board

working temperature exceeds the threshold.

OptiX OSN 8800/6800/3800
Procedure
Step 1 If the TEMP_OVER alarm is generated, see the related handling procedure.
----End
Related Information
None
6.19 ETH_CFM_LS
Description
Packet loss seconds of the E-Line service
Impact on System
During the statistics period (for example, 15 minutes or 24 hours), the severity of packet loss
ascends with the number of severe packet loss seconds. If the packet loss is severe, the service
quality is affected.

The possible cause of the ETH_CFM_LS performance event is insufficient network bandwidth.
Related Alarms
None.
Procedure
Step 1 Check the service bandwidth utilization. If the bandwidth reaches or exceeds the set bandwidth,
bandwidth expansion is needed.
----End
Related Information
If packet loss exists in a second, this second is included in packet loss seconds.
6.20 ETH_CFM_SLS
Description
Severe packet loss seconds of the E-Line service

OptiX OSN 8800/6800/3800
Impact on System

The possible cause of the ETH_CFM_SLS performance event is that the network is congested.
Related Alarms
None.
Procedure
----End
Related Information
If the packet loss ratio in a second exceeds the set threshold value, this second is included in the
severe packet loss seconds.
6.21 ETH_CFM_CSLS
Description
Consecutive severe packet loss seconds of the E-Line service
Impact on System
ascends with the number of consecutive severe packet loss seconds. If the packet loss is severe,
the service quality is affected.

The possible cause of the ETH_CFM_CSLS performance event is that the network is congested.
Related Alarms
None.

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
If the previous second is a severe packet loss second and this second is also a severe packet loss
second, this second is included in the consecutive severe packet loss seconds.
6.22 ETH_CFM_UAS
Description
Unavailable seconds of the E-Line service
Impact on System
ascends with the number of unavailable seconds. If the packet loss is severe, the service quality
is affected.

The possible cause of the ETH_CFM_UAS performance event is that the network is congested.
Related Alarms
None.
Procedure
----End
Related Information
If the packet loss ratio exceeds the set threshold value for ten consecutive seconds and this second
is a severe packet loss second, these seconds are included in the unavailable seconds.
6.23 FEC_AFT_COR_ER
Description
After FEC correct errored rate

OptiX OSN 8800/6800/3800
Impact on System
In normal cases, the value should be 0 after the error correction. If the value is not 0, the bit
errors in the services have affected the signal transmission quality. When this occurs, identify
the cause in a timely manner.

This performance event shows that there are still bit 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.
When there are post-FEC bit errors, there are also pre-FEC bit errors (FEC_BEF_COR_ER)
accompanied. In this case, check the services in a timely manner.
Related Alarms
BEFFEC_EXC Pre-FEC BER threshold-crossing alarm. If the FEC function is

enabled for the signals sent from the WDM side of the opposite OTU,
the local OTU counts the BER in the signals received on the WDM
side before performing FEC. This alarm is generated when the
counted BER exceeds the system threshold.
Procedure
Step 1 See the procedure for handling the BEFFEC_EXC alarm.
----End
Related Information
None
6.24 FEC_AFT_COR_ERAVR
Description
After FEC correct average errored rate in monitor period
Impact on System
the cause in a timely manner

This performance event shows there are still bit 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.

OptiX OSN 8800/6800/3800
When there are post-FEC bit errors, there are also pre-FEC bit errors
(FEC_BEF_COR_ERAVR) accompanied. In this case, check the services in a timely manner.
Related Alarms

enabled for the signals sent from the WDM side of the opposite-end
OTU, the local OTU counts the BER in the signals received on the
WDM side before performing FEC. This alarm is generated when the
Procedure
----End
Related Information
None
6.25 FEC_AFT_CORER_FLOAT
Description
After FEC correct errored rate (floating point values)
Impact on System
the cause in a timely manner.

This performance event shows there are still bit 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.
When there are post-FEC bit errors, there are also pre-FEC bit errors
(FEC_BEF_CORER_FLOAT) accompanied. In this case, check the services in a timely manner

OptiX OSN 8800/6800/3800
Related Alarms

Procedure
----End
Related Information
None
6.26 FEC_BEF_COR_ER
Description
BER before FEC
Impact on System
There are bit errors on the line. The services, however, may not be affected. If the bit error rate
(BER) is low, the system operates properly. If the BER is high, identify the causes and solve the
problem timely to avoid any alarm, therefore ensuring the signal transmission quality.

The cause for the pre-BER FEC is that the receiver detects bit errors, which are caused by
dispersion, unstable performance of the optical port, or excessively high attenuation.
Related Alarms


OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.27 FEC_BEF_COR_ERAVR
Description
Before FEC correct average errored Rate in monitor period
Impact on System
(BER) is low, the system operates properly. If the BER is high, identify the cause and solve the
problem in a timely manner to avoid any alarm, therefore ensuring the signal transmission
quality.

The cause for the pre-FEC BER is that the receiver detects bit errors, which are caused by low
OSNR at the receive end. In normal cases, it should be 0.
Related Alarms

Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.28 FEC_BEF_CORER_FLOAT
Description
Before FEC correct errored rate (floating point values)
Impact on System
(BER) is low, the system operates properly. If the BER is high, identify the cause and solve the
problem in a timely manner to avoid any alarm, therefore ensuring the signal transmission
quality.

The cause for the pre-FEC BER is that the receiver detects bit errors, which are caused by low
OSNR at the receive end.
Related Alarms

Procedure
----End
Related Information
None
Description
Forward error correction - corrected 0 bit count
Impact on System
None

OptiX OSN 8800/6800/3800

This performance event shows the number of 0 bits corrected by the 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 1 bits corrected by the FEC function of the board,
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.31 FEC_COR_BYTE_CNT
Description
Forward error correction - corrected byte count
Impact on System
None

This performance event shows the number of bytes corrected by the FEC function of the board,
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.32 FEC_TMP
Description
Total period for monitoring FEC performance
Impact on System
None

This performance event is used to collect statistics on the total period for monitoring performance
of FEC, including the FEC_AFT_COR_ER, FEC_AFT_COR_ERAVR,
FEC_AFT_CORER_FLOAT, FEC_BEF_COR_ER, FEC_BER_COR_ERAVR,
FEC_BEF_CORER_FLOAT, FEC_COR_0BIT_CNT, FEC_COR_1BIT_CNT,
FEC_COR_BYTE_CNT and FEC_UNCOR_BLOCK_CNT performance. When an optical
module cannot be found, an optical path is unavailable, or the port FEC is not enabled, the
FEC_TMP performance event is not collected statistics. When ports are working properly, the
value of FEC_TMP, which is expressed in seconds, increases with the working time.

OptiX OSN 8800/6800/3800
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.33 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. In
normal cases, the value should be 0.
Related Alarms

Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.34 FREQDEV
Description
Frequency deviation between the current input clock and input reference clock source. It includes
the MAXFREQDEV, MINFREQDEV, and AVGFREQDEV performance parameters, which
indicate the maximum, minimum, and average frequency deviations respectively.
Impact on System
It is an indicator of the IEEE 1588v2 performance and has no impact on services.

Users can determine the clock tracing performance based on the frequency deviation between
the current output clock and input reference clock source.
Related Alarms
SYN_BAD Synchronization source degrade alarm. 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.
Procedure
Step 1 None
----End
Related Information
None
6.35 HPBBE
Description
Background block error (BBE) on a higher-order path
Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated, the
system is not affected. You need to, however, identify the causes and resolve the problem in a

OptiX OSN 8800/6800/3800
timely manner. Otherwise, alarms may be generated, and the signal transmission quality of the
higher-order path deteriorates.

The HPBBEs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
l There is interference from the external environment.

l A fault occurs on the switch that interconnects with the SDH equipment.
l The signal cable is faulty.
l The line board malfunctions.
l The cross-connection unit is faulty.
l The clock unit is faulty.
Related Alarms
B3_SD This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (1106).
B3_EXC This alarm is generated when the B3 bit error rate on the alarm path
exceeds the threshold (110-3).
Procedure
Step 1 See the procedures for handling the B3_SD and B3_EXC alarms.
----End
Related Information
BBE
The BBE indicates that one or more bit errors occur in the data block during transmission.
6.36 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 alarms are generated,
the system is not affected. You need to, however, find out the causes and take proper measures

OptiX OSN 8800/6800/3800
in time to avoid generating alarms, which affect the quality of the signals transmitted in the
higher order path.

Bit errors in the higher order path are detected by the means of detecting the B3 byte. The SES
(severely errored second) refers to the second in which more than 30% errored blocks occur or
at least one SDP (serious disturbance period) occurs. Generally, the CSES (consecutive severely
errored second) is accompanied by the B3_EXC alarm. Consequently, the services are
interrupted. The possible causes of the event are as follows:
l A fault occurs in the switch that interworks with the SDH equipment.
l The line board is faulty.
l The tributary unit is faulty.
Related Alarms
B3_SD When the count of B3 bit errors in the alarm path is close to the
threshold (1 x 10-6), the alarm is reported.
B3_EXC When the count of B3 bit errors in the alarm path exceeds the
threshold (1 x 10-3), the alarm is reported.
Procedure
----End
Related Information
None.
6.37 HPES
Description
Errored second (ES) on a higher-order path
Impact on System
A small number of bit errors occur on the higher-order path. If no related alarm is generated, the

OptiX OSN 8800/6800/3800

The HPESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
Related Alarms
Procedure
----End
Related Information
ES
The ES indicates a second in which one or more errored blocks are detected.
6.38 HPFEBBE
Description
Far end background block error (BBE) on a higher-order path
Impact on System
The remote end detects that a small number of bit errors occur on the higher-order path. If no
related alarm is generated, the system is not affected. You need to, however, identify the causes
and resolve the problem in a timely manner. Otherwise, alarms may be generated, and the signal
transmission quality of the higher-order path deteriorates.

OptiX OSN 8800/6800/3800

HPFEBBEs indicate the block errors on the higher-order path detected at the remote end. The
possible causes of the event are as follows:
Related Alarms
HP_REI This alarm is generated when the board detects that the value is 1 to 8
for bits 1 to 4 of the G1 byte on the higher-order path.
Procedure
Step 1 See the procedure for handling the HP_REI alarm.
----End
Related Information
BBE
The BBE indicates that one or more bit errors occur in the data block during transmission.
6.39 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 alarms
are generated, the system is not affected. You need to, however, find out the causes and take
proper measures in time to avoid generating alarms, which affect the quality of the signals
transmitted in the higher order path.

The consecutive severely errored bits at the far end of the higher order path are detected by the
means of detecting the G1 byte. The possible causes of the event are as follows:

OptiX OSN 8800/6800/3800

l A fault occurs in the switch that interworks with the SDH equipment.
l The tributary unit is faulty.
Related Alarms
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 SES (severely errored second) refers to the second in which more than 30% errored blocks
occur or at least one SDP (serious disturbance period) occurs.
Consecutive Severely Errored Second
The CSES (consecutive severely errored second) refers to the SES (severely errored second)
event that occurs consecutively.
Remote Bit Error
The remote bit error refers to the bit error that is detected at the opposite station.
6.40 HPFEES
Description
Far end errored second (ES) on a higher-order path
Impact on System
The remote end detects that a small number of bit errors occur on the higher-order path. If no

OptiX OSN 8800/6800/3800

The HPFEESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:
Related Alarms
Procedure
----End
Related Information
Far End Errored Second
The far end errored second (FEES) indicates an errored second that is detected at the remote
end.
6.41 HPFESES
Description
Far end severely errored second (SES) on a higher-order path
Impact on System
The remote end detects that a large number of bit errors occur on the higher-order path. If no

The HPFESESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:

OptiX OSN 8800/6800/3800

Related Alarms
Procedure
----End
Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks occur or at least a
serious disturbance period (SDP) occurs.
6.42 HPFEUAS
Description
Far end unavailable second (UAS) on a higher-order path
Impact on System
If bit errors occur in the services on a remote NE, identify the causes and resolve the problem
in a timely manner. Otherwise, alarms may be generated, and the signal transmission quality
deteriorates.

HPFEUAS indicates the period of time that the UAT state lasts.
External causes:
l The fiber performance deteriorates or the attenuation is excessive on the remote NE.
l The fiber connector is contaminated or incorrect on the remote NE.

OptiX OSN 8800/6800/3800
l The remote NE is improperly grounded.

l There is a strong interference source around the remote NE.
l The peer NE runs in an environment with a temperature that exceeds the threshold.
Equipment problems:
l The signals received by the line board on the remote NE are greatly attenuated, the
transmitting circuit on the remote end is faulty, or the receive circuit on the local end is
faulty.
l The synchronization performance of the clock is poor on the remote NE.
l The cross-connection unit and the line board do not match on the remote NE.
l The fan on the remote NE is faulty.
l The board malfunctions or the board performance deteriorates on the remote NE.
Related Alarms
HP_REI Indicates a bit error on a higher-order path detected at the remote end.
HP_RDI Indicates a failure on a higher-order path detected at the remote end.
Procedure
Step 1 If any alarm is generated, handle the alarm by referring to the related handling procedure.
----End
Related Information
None.
6.43 HPSES
Description
Severely errored second on a higher-order path
Impact on System
A large number of bit errors occur on the higher-order path. If no related alarm is generated, the

OptiX OSN 8800/6800/3800

The HPSESs are detected by monitoring the B3 byte. The possible causes of the event are as
follows:

Related Alarms
Procedure
----End
Related Information
SES
The SES indicates a certain second in which more than 30% errored blocks occur or at least a
serious disturbance period (SDP) occurs.
6.44 HPUAS
Description
Unavailable second (UAS) on a higher-order path
Impact on System
l A large number of bit errors occur on the higher-order path. If no related alarm is generated,
the system is not affected. You need to, however, identify the causes and resolve the
problem in a timely manner. Otherwise, alarms may be generated, and the signal

OptiX OSN 8800/6800/3800
l When this performance event occurs, check whether alarms, such as AU_AIS, B3_EXC,
and HP_UNEQ, exist. If yes, services may be interrupted.

The HPUASs are detected by monitoring the B3 byte. When signals are consecutively received
for 10 seconds, and the bit error rate per second is more than 10-3, the period from the first second
is called a period of UAS. When signals are consecutively received for 10 seconds, and the bit
error rate per second is less than 10-3, the period from the first second is called a period of
available second. The ES indicates a second in which one or more errored blocks are detected.
The possible causes of the event are as follows:

Related Alarms
AU_AIS When this alarm occurs, the HPUAS value increases.
HP_TIM When this alarm occurs, the HPUAS value increases.
HP_UNEQ When this alarm occurs, the HPUAS value increases.
Procedure
Step 1 See the procedures for handling the B3_SD, B3_EXC, AU_AIS, HP_TIM, and HP_UNEQ
alarms.
----End
Related Information
None.

OptiX OSN 8800/6800/3800
6.45 ICCLC
Description
Module cooling current
It includes:
l ICCLCMAX: stands for the maximum value during a period of time.

l ICCLCMIN: stands for the minimum value during a period of time.
l ICCLCCUR: stands for the current value.
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
MODULE_COOLCUR_OVER This alarm 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 related handling procedure.
----End
Related Information
None
6.46 ICTMP
Description
Module temperature
It includes:

OptiX OSN 8800/6800/3800
l ICTMPMAX: stands for the maximum value during a period of time.

l ICTMPMIN: stands for the minimum value during a period of time.
l ICTMPCUR: stands for the current value.
Impact on System
None

This performance event is generated by checking the current working temperature of module to
show the working temperature of a module.
Related Alarms
MODULE_TEMP_OVER This alarm 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 related handling procedure.
----End
Related Information
None
6.47 LSBIAS
Description
Laser bias current
It includes:
l LSBIASMAX: stands for the maximum value during a period of time.

l LSBIASMIN: stands for the minimum value during a period of time.
l LSBIASCUR: stands for the current value.
l PEAK_LSBIAS_MAX: stands for the maximum peak value during a period of time.
l PEAK_LSBIAS_MIN: stands for the minimum peak value during a period of time.
l PEAK_LSBIAS_CUR: stands for the current peak value.
l VALLEY_LSBIAS_MAX: stands for the maximum valley value during a period of time.

OptiX OSN 8800/6800/3800
l VALLEY_LSBIAS_MIN: stands for the minimum valley value during a period of time.
l VALLEY_LSBIAS_CUR: stands for the current valley value.
Impact on System
None

The LSBIAS performance value is obtained by hardware check and software conversion.
Related Alarms
TD This alarm is generated when the working

current of a laser exceeds the threshold or a
multiple of the threshold.
LSR_WILL_DIE This alarm 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 related handling procedure.
Step 2 If the LSR_WILL_DIE alarm is generated, see the related handling procedure.
----End
Related Information
None
6.48 LSCLC
Description
Laser cooling current
It includes:
l LSCLCMAX: stands for the maximum value during a period of time.

l LSCLCMIN: stands for the minimum value during a period of time.
l LSCLCCUR: stands for the current value.
l PEAK_LSCLCMAX: stands for the maximum peak value during a period of time.
l PEAK_LSCLCMIN: stands for the minimum peak value during a period of time.

OptiX OSN 8800/6800/3800
l PEAK_LSCLCCUR: stands for the current peak value.

l VALLEY_LSCLCMAX: stands for the maximum valley value during a period of time.
l VALLEY_LSCLCMIN: stands for the minimum valley value during a period of time.
l VALLEY_LSCLCCUR: stands for the current valley 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 correctly transmitted or received.

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
LSR_COOL_ALM This alarm 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 related handling procedure.
----End
Related Information
None
6.49 LSIOP
Description
Input optical power
It includes:
l LSIOPMAX: stands for the maximum value during a period of time.

l LSIOPMIN: stands for the minimum value during a period of time.
l LSIOPCUR: stands for the current value.
l PEAK_INPOWER_MAX: stands for the maximum peak input optical power.
l PEAK_INPOWER_MIN: stands for the minimum peak input optical power.
l PEAK_INPOWER_CUR: stands for the current peak input optical power.

OptiX OSN 8800/6800/3800
l VALLEY_INPOWER_MAX: stands for the maximum valley input optical power.

l VALLEY_INPOWER_MIN: stands for the minimum valley input optical power.
l VALLEY_INPOWER_CUR: stands for the current valley input optical power.
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.

LSIOP to show the input optical power performance of a board.
Related Alarms
IN_PWR_HIGH This alarm is generated when the optical power input by board is
higher than the upper threshold.
IN_PWR_LOW This alarm is generated when the optical power input by board is lower
than the lower threshold.
Procedure
historical 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.
(such as expansion or upgrade), see the procedure for handling the IN_PWR_LOW alarm.
Step 3 If any alarm is generated, see the related handling procedure.
----End
Related Information
None
6.50 LSOOP
Description
Output optical power
It includes:

OptiX OSN 8800/6800/3800
l LSOOPMAX: stands for the maximum value during a period of time.

l LSOOPMIN: stands for the minimum value during a period of time.
l LSOOPCUR: stands for the current value.
l PEAK_OUTPOWER_MAX: stands for the maximum peak output optical power.
l PEAK_OUTPOWER_MIN: stands for the minimum peak output optical power.
l PEAK_OUTPOWER_CUR: stands for the current peak output optical power.
l VALLEY_OUTPOWER_MAX: stands for the maximum valley output optical power.
l VALLEY_OUTPOWER_MIN: stands for the minimum valley output optical power.
l VALLEY_OUTPOWER_CUR: stands for the current valley output optical power.
Impact on System
If the output optical power of the laser is abnormal, there is impact on the normal transmission
of services.

LSOOP to show the output optical power performance of the laser on a board.
Related Alarms
OUT_PWR_HIGH This alarm is generated when the optical power output by a board is
OUT_PWR_LOW This alarm is generated when the optical power output by a board is
lower than the lower threshold.
TF This alarm is generated when the optical power output by a board is

1 dB lower than the lower threshold.
Procedure
historical 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.
historical 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

OptiX OSN 8800/6800/3800
Related Information
None
6.51 LSTMP
Description
Laser temperature
It includes:
l LSTMPMAX: stands for the maximum value during a period of time.
l LSTMPMIN: stands for the minimum value during a period of time.
l LSTMPCUR: stands for the current value.
l PEAK_LSTMP_MAX: stands for the maximum peak laser temperature.
l PEAK_LSTMP_MIN: stands for the minimum peak laser temperature.
l PEAK_LSTMP_CUR: stands for the current peak laser temperature.
l VALLEY_LSTMP_MAX: stands for the maximum valley laser temperature.
l VALLEY_LSTMP_MIN: stands for the minimum valley laser temperature.
l VALLEY_LSTMP_CUR: stands for the current valley laser temperature.
Impact on System
None

In normal cases, 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
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 related handling procedure.
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.52 MEANPATHDELAY
Description
Path delay between the master clock and a slave clock. It includes the
MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY
performance parameters, which indicate the maximum, minimum, and average path delays
respectively.
Impact on System

This performance event is generated when a path delay occurs between the master clock and a
slave clock.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.53 MPLS_PW_LS
Description
Packet loss seconds of the PW service.
Impact on System
ascends with the number of packet loss seconds. If the packet loss is severe, the service quality
is affected.

OptiX OSN 8800/6800/3800

The possible cause of the MPLS_TUNNEL_LS performance event is insufficient network
bandwidth.
Related Alarms
None.
Procedure
----End
Related Information
During the statistics period, if packet loss exists in a second, this second is included in the packet
loss seconds.
6.54 MPLS_PW_SLS
Description
Severe packet loss seconds of the PW service.
Impact on System

The possible cause of the MPLS_TUNNEL_SLS performance event is that the network is
congested.
Related Alarms
None.
Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
If the packet loss ratio in a second exceeds the set threshold value, this second is included in the
severe packet loss seconds.
6.55 MPLS_PW_CSLS
Description
Consecutive severe packet loss seconds of the PW service
Impact on System
ascends with the number of consecutive severe packet loss seconds. If the packet loss is severe,
the service quality is affected.

The possible cause of the MPLS_TUNNEL_LS performance event is insufficient network
bandwidth.
Related Alarms
None.
Procedure
----End
Related Information
If the previous second is a severe packet loss second and this second is also a severe packet loss
second, this second is included in the consecutive severe packet loss seconds.
6.56 MPLS_PW_UAS
Description
Unavailable seconds of the PW service.
Impact on System

OptiX OSN 8800/6800/3800

The possible cause of the MPLS_TUNNEL_UAS performance event is that the network is
congested.
Related Alarms
None.
Procedure
----End
Related Information
If the packet loss ratio exceeds the set threshold value for ten consecutive seconds and this second
is a severe packet loss second, these seconds are included in the unavailable seconds.
6.57 MSBBE
Description
MS background block error
Impact on System
There are bit errors in the services. If the number of bit errors increases, identify the cause and
solve the problem in a timely manner to avoid any alarm, therefore ensuring 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
B2_EXC Multiplex section (B2) excessive errors alarm. This alarm is generated
when the B2 bit errors in the multiplex section exceed the threshold.
B2_SD Multiplex section (B2) signal degraded alarm. This alarm is generated
when the B2 bit errors in the multiplex section exceed the signal
degrade (SD) threshold.

OptiX OSN 8800/6800/3800
MS_AIS Multiplex section alarm indication. This 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. This 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 See the procedure for handling the B2_EXC alarm.
----End
Related Information
None
6.58 MSCSES
Description
MS consecutive severely errored second
Impact on System
There are a large number of bit errors in the services. Identify the cause and solve the problem
in a timely manner 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 the 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

OptiX OSN 8800/6800/3800

ms.
Procedure
----End
Related Information
None
6.59 MSES
Description
MS errored second
Impact on System
There are bit errors in the services. If the errored seconds are generated continuously, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the
signal transmission 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.

OptiX OSN 8800/6800/3800
Related Alarms

ms.
Procedure
----End
Related Information
None
6.60 MSFEBBE
Description
MS far end background block error
Impact on System
Bit errors are generated in the services on the far-end NE. If the number of bit errors increases,

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.

OptiX OSN 8800/6800/3800
Related Alarms
MS_RDI Multiplex section remote defect indication alarm. This 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 See the procedure for handling the MS_RDI alarm.
----End
Related Information
None
6.61 MSFECSES
Description
MS far end consecutive severely errored second
Impact on System

second, there is at least one defect or 30% of the data blocks are error blocks. The consecutive
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


OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.62 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
Related Alarms

Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.63 MSFESES
Description
MS far end severely errored second
Impact on System

second, there is at least one defect or 30% of the 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

Procedure
----End
Related Information
None
6.64 MSFEUAS
Description
MS far end unavailable second

OptiX OSN 8800/6800/3800
Impact on System

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

Procedure
----End
Related Information
None
6.65 MSSES
Description
MS severely errored second
Impact on System

second, there is at least one defect or 30% of the data blocks are error blocks.

OptiX OSN 8800/6800/3800
Related Alarms

ms.
Procedure
----End
Related Information
None
6.66 MSUAS
Description
MS unavailable second
Impact on System
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 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.

OptiX OSN 8800/6800/3800
Related Alarms

R_LOS Loss of signal on receiving line. This alarm is generated when the
receive side receives no signals.

MS_REI Multiplex section remote error indication. This alarm is generated

when the remote end detects the bit error block.
Procedure
----End
Related Information
None
6.67 ODU2PMBIP8
Description
Number of BIP8 bit errors in the PM section at the optical data unit (ODU) layer

OptiX OSN 8800/6800/3800
Attribute
Performance Event Performance Event Type
ID
0x104B Check and correction
Impact on System
Bit errors occur in the services. Identify the causes and resolve the problem in a timely manner.
Otherwise, alarms may be generated, and the signal transmission quality deteriorates.

This performance event indicates the number of bit errors that a board with an OTN interface
detects in the PM section at the ODU layer through the BIP8 check. In normal cases, the
performance value is 0.
Related Alarms
PM_BIP8_OVER This alarm is generated when the number of BIP8 bit

errors in the PM section of the ODU layer exceeds the
threshold.
PM_BIP8_SD This alarm is generated when the number of BIP8 bit

errors in the PM section of the ODU layer exceeds the
degrade threshold.
Procedure
----End
Related Information
None.
6.68 ODUk_PM_BBE
Description
ODU PM section background block error

OptiX OSN 8800/6800/3800
Impact on System
There are bit errors in the services. If the number of block errors increases, identify the cause
and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal

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
ODUk_PM_EXC Bit interleaved parity (BIP) in the PM section of the ODU layer
exceeds the upper threshold. This 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. This 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 See the procedure for handling the ODUk_PM_EXC or ODUk_PM_DEG alarm.
----End
Related Information
None
6.69 ODUk_PM_BBER
Description
ODU PM section ratio of background block error
Impact on System
When the value is not 0, there are bit errors in the services. When the value is large, identify the
cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring the signal

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

OptiX OSN 8800/6800/3800
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-UAS-
cSES) x blocks per second].
Related Alarms
ODUk_PM_EXC ODU layer PM section BIP exceeds the upper threshold. This 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.
of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.70 ODUk_PM_ES
Description
ODU PM section errored second
Impact on System

ODU PM section errors are detected by checking the received parity bit. An errored second
contains more than one error block.

OptiX OSN 8800/6800/3800
Related Alarms
of the PM section of the ODU layer exceeds the degraded threshold.
Procedure
----End
Related Information
None
6.71 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
ODUk_PM_BDI ODU PM section backward defect indication.

OptiX OSN 8800/6800/3800
Procedure
Step 1 See the procedure for handling the ODUk_PM_BDI alarm.
----End
Related Information
None
6.72 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
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
Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.73 ODUk_PM_FEES
Description
ODU PM section far end errored second
Impact on System

ODU PM section errors are 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
Procedure
----End
Related Information
None
6.74 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,

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 15% of the 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
Related Alarms
Procedure
----End
Related Information
None
6.75 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 15% of the 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.

OptiX OSN 8800/6800/3800
Related Alarms
Procedure
----End
Related Information
None
6.76 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
Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.77 ODUk_PM_SES
Description
ODU PM section severely errored second
Impact on System
There are bit errors in services. Identify the cause and solve the problem in a timely manner
because the bit errors have affected the signal transmission quality.

ODU PM Section errors are detected by checking the received parity bit. During a severely
errored second, there is at least one defect or 15% of the 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
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. This 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

OptiX OSN 8800/6800/3800
6.78 ODUk_PM_SESR
Description
ODU PM section ratio of severely errored second
Impact on System

Related Alarms
number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.79 ODUk_PM_TMP
Description
Total period for period performance of ODU signals in the PM section

OptiX OSN 8800/6800/3800
Impact on System
None

of ODU signals in the PM section, including the ODUk_PM_BBE, ODUk_PM_BBER,
ODUk_PM_ES, ODUk_PM_SES, ODUk_PM_SESR, and ODUk_PM_UAS performance. The
performance event is not collected statistics when an optical module cannot be found or an optical
path is not used. The statistics depends on the service configuration and monitoring
configuration, for example, whether the inherent monitoring and non-instrusive monitoring
functions are enabled. When ports are working properly, the value of ODUk_PM_TMP, which
is expressed in seconds, increases with the working time.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.80 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.

OptiX OSN 8800/6800/3800
Related Alarms
number of BIP8 bit errors of the PM section on the optical channel
Procedure
----End
Related Information
None
6.81 ODUk_TCMn_BBE
Description
ODUk TCMn section background block error
Impact on System

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
ODUk_TCMn_DEG ODU TCMn burst-mode signal degradation.
ODUk_TCMn_EXC ODU TCMn Poisson-mode excessive bit errors.

OptiX OSN 8800/6800/3800
Procedure
Step 1 On the U2000, check whether there are a large number 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 procedure for handling the
ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.82 ODUk_TCMn_BBER
Description
ODUk TCMn section ratio of background block error
Impact on System

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/[(P-
UAS-cSES) x blocks per second].
Related Alarms
Procedure

OptiX OSN 8800/6800/3800
Step 2 If the performance event persists, see the procedure for handling the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.83 ODUk_TCMn_BIAES
Description
ODU TCMn section backward introducing alignment errored second
Impact on System
There are errors in frame alignment. Identify the cause and solve the problem in a timely manner

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 port is within the permitted
range. For the optical power specifications of the specific board, see "Technical Specifications"
in the Product Description. If the input optical power is abnormal, see the procedures for
handling the IN_PWR_HIGH and IN_PWR_LOW alarms.
Step 2 If the performance event persists, handling bit error fault.
----End
Related Information
None
6.84 ODUk_TCMn_ES
Description
ODUk TCMn section errored second

OptiX OSN 8800/6800/3800
Impact on System

ODUk TCMn section errors are detected by checking the received parity bit. An errored second
contains more than one error block.
Related Alarms
Procedure
Step 2 If the performance event persists, see the procedure for handling the ODUk_TCMn_DEG or
ODUk_TCMn_EXC alarm.
----End
Related Information
None
6.85 ODUk_TCMn_FEBBE
Description
ODUk TCMn section far end background block error
Impact on System

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

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 errors are detected at the opposite end.
Related Alarms
None
Procedure
in the Product Description.. If the input optical power is abnormal, see the procedures for
----End
Related Information
None
6.86 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
cSES) x blocks per second].
Related Alarms
None
Procedure

OptiX OSN 8800/6800/3800
----End
6.87 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 See the procedure for handling the ODUk_TCMn_BDI alarm.
----End
Related Information
None
6.88 ODUk_TCMn_FESES
Description
ODUk TCMn section far end severely errored second
Impact on System

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
15% of the data blocks are error blocks. The fiber line may be faulty.
Related Alarms
None
Procedure
----End
Related Information
None
6.89 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. Identify the cause and solve the problem in
a timely manner, therefore ensuring the signal transmission quality.

During a far end severely errored second, there is at least one defect or 15% of the 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 See the procedure for handling the ODUk_TCMn_SESR alarm.
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.90 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
ODUk_TCMn_BDI ODU TCMn backward defect indication.
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_BDI alarm.
----End
Related Information
None
6.91 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.

The OTUk_OOF or OTUk_LOF alarm is generated at the upstream station.

OptiX OSN 8800/6800/3800
Related Alarms
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 See the procedure for handling the OTUk_LOF alarm.
----End
Related Information
None
6.92 ODUk_TCMn_SES
Description
ODUk TCMn section severely errored second
Impact on System

It is obtained by calculating the BIP-8 of ODUk TCMn section. During a severely errored second,
there is at least one defect or 15% of the data blocks are error blocks. The fiber line may be
faulty.
Related Alarms
Procedure
Step 1 See the procedure for handling the ODUk_TCMn_DEG or ODUk_TCMn_EXC alarm.
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.93 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 15% of the 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
Procedure
----End
Related Information
None
6.94 ODUk_TCMn_TMP
Description
Total period for monitoring performance of ODUk signals in the TCM section

OptiX OSN 8800/6800/3800
Impact on System
None

This performance event is used to collect statistics on the total duration for monitoring
performance of ODUk signals in the PM section, including the ODUk_TCMn_BBE,
ODUk_TCMn_BBER, ODUk_TCMn_BIAES, ODUk_TCMn_ES, ODUk_TCMn_IAES,
ODUk_TCMn_SES, ODUk_TCMn_SESR and ODUk_TCMn_UAS performance. The
functions are enabled. When ports are working properly, the value of ODUk_TCMn_TMP,
which is expressed in seconds, increases with the working time.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.95 ODUk_TCMn_UAS
Description
ODUk TCMn section unavailable second
Impact on System

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.

OptiX OSN 8800/6800/3800
Related Alarms
Procedure
----End
Related Information
None
6.96 OOPRL
Description
Optical output power return loss
It includes:
l OOPRLMAX: maximum value of the output optical power return loss within a time period
l OOPRLMIN: minimum value of the output optical power return loss within a time period
l OOPRLCUR: current value of the output optical power return loss
Impact on System

The fiber near the Raman board is broken, over-bent, or pressed, or the fiber connector is unclean
or installed incorrectly.
Related Alarms
RL_CRITICAL_HI This alarm is generated when the return loss is higher than the upper
RL_CRITICAL_LO This alarm is generated when the return loss is lower than the lower
W threshold of the return loss alarm.

OptiX OSN 8800/6800/3800
Procedure
Step 1 See the procedure for handling the RL_CRITICAL_HI or RL_CRITICAL_LOW alarm.
----End
Related Information
None
6.97 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, identify the cause

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
6.98 OSC_BBER
Description
OSC path section ratio of background block error

OptiX OSN 8800/6800/3800
Impact on System
When the value is not 0, there are bit errors in the OSC signals. When the value is large, identify
the cause and solve the problem in a timely manner to avoid any alarm, therefore ensuring 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.99 OSC_BIAES
Description
OSC path backward incoming alignment errored second
Impact on System

Backward incoming alignment errored second refers to the second where more than one
backward input frame alignment errors are generated.
Related Alarms
None

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.100 OSC_ES
Description
OSC path errored second
Impact on System
There are bit errors in the OSC signals. If the number of bit errors increases, identify the cause

An errored second contains more than one error block.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.101 OSC_FEBBE
Description
OSC path far end background block error

OptiX OSN 8800/6800/3800
Impact on System

OSC background block errors are detected by checking the received parity bit. The background
block error means that 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.102 OSC_FEBBER
Description
OSC path section ratio of far end background block error
Impact on System
When the value is not 0, there are bit errors in the signals. When the value is large, identify the

The background block error refers to a data block where at least one bit error is generated 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]. 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

OptiX OSN 8800/6800/3800
Procedure
Step 1 None
----End
Related Information
None
6.103 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,

Bit errors are 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
None
Procedure
Step 1 None
----End
Related Information
None
6.104 OSC_FESES
Description
OSC path section far end severely errored second

OptiX OSN 8800/6800/3800
Impact on System
There are bit errors in the signals on a far-end NE. Identify 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
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.105 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. Identify the cause and solve the problem in

the far end.
Related Alarms
None

OptiX OSN 8800/6800/3800
Procedure
Step 1 None
----End
Related Information
None
6.106 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.107 OSC_IAES
Description
OSC path section errored second

OptiX OSN 8800/6800/3800
Impact on System

None
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.108 OSC_SES
Description
OSC path section severely errored second
Impact on System
There are severely errored second in the OSC signals. Identify the cause and solve the problem
in a timely manner because the bit errors have affected the signal transmission quality.

Error is detected by checking the received parity bit. During a severely errored second, there is
at least one defect or 15% of the data blocks are error blocks.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.109 OSC_SESR
Description
OSC path section ratio of severely errored second
Impact on System
There are severely errored second in the signals. Identify 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.110 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.


OptiX OSN 8800/6800/3800
available.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.111 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.

l OSPICCVMIN: stands for the minimum value during a period of time.
l 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 permitted range, you do not need to take any action.

l The performance event records the historical maximum, historical minimum and current
value of the cooling current.
l 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.

OptiX OSN 8800/6800/3800
Related Alarms
LSR_COOL_ALM When the cooling current of the laser is beyond the specified range,
this alarm is generated.
Procedure
Step 1 See the procedure for handling the LSR_COOL_ALM alarm.
----End
Related Information
None
6.112 OSPITMP
Performance Event Meaning
Temperature in the tube core of the laser
It includes:
l OSPITMPMAX: stands for the maximum value during a period of time.

l OSPITMPMIN: stands for the minimum value during a period of time.
l 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 permitted range, you
do not need to take any action.

The performance event monitors the temperature of the laser core to help users know about the
historical maximum historical minimum and current temperature of the laser.
Related Alarms
TEM_HA When the temperature of the laser is higher than the upper threshold,

OptiX OSN 8800/6800/3800
TEM_LA When the temperature of the laser is less than the lower threshold,
Procedure
Step 1 See the procedure for handling the TEM_HA and TEM_LA alarms.
----End
Related Information
None
6.113 OTU2SMBIP8
Description
Number of BIP8 bit errors in the SM section at the optical channel transport unit (OTU) layer
Attribute
Performance Event Performance Event Type
ID
0x104A Check and correction
Impact on System
Bit errors occur in the services. Identify the causes and resolve the problem in a timely manner.
Otherwise, alarms may be generated, and the signal transmission quality deteriorates.

This performance event indicates the number of bit errors that a board with an OTN interface
detects in the SM section at the OTU layer through the BIP8 check. In normal cases, the
performance value is 0.
Related Alarms
SM_BIP8_OVER This alarm is generated when the number of BIP8 bit errors in the SM
section at the OTU layer exceeds the threshold.

OptiX OSN 8800/6800/3800
SM_BIP8_SD This alarm is generated when the number of BIP8 bit errors in the SM
section at the OTU layer exceeds the degrade threshold.
Procedure
----End
Related Information
None.
6.114 OTUk_BBE
Description
OTU background block error
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
OTUk_EXC OTU SM section bit interleaved parity exceeds threshold. This alarm
is generated when the number of BIP8 bit errors of the SM section on
the optical channel data unit layer exceeds the threshold.
OTUk_DEG OTU SM section bit interleaved parity deterioration. This alarm is

generated when the number of BIP8 bit errors of the SM section in
the optical channel data unit layer exceeds the degraded threshold.

OptiX OSN 8800/6800/3800
Procedure
Step 1 See the procedure for handling the OTUk_EXC or OTUk_DEG alarm.
----End
Related Information
None
6.115 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
of blocks during the unavailable time and SES period. BBER = cBBE/[(P-UAS-cSES) x blocks
per second].
Related Alarms
is generated when the number of BIP8 bit errors of the SM section in

generated when the number of BIP8 bit errors of the SM section on
Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.116 OTUk_BIAES
Description
OTU SM section backward introducing alignment errored second
Impact on System

OTU SM 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
----End
Related Information
None
6.117 OTUk_ES
Description
OTU errored second

OptiX OSN 8800/6800/3800
Impact on System

OTU errors are detected by checking the received parity bit. An errored second contains more
than one error block.
Related Alarms

Procedure
----End
Related Information
None
6.118 OTUk_FEBBE
Description
OTU SM section far end background block error
Impact on System

OTU SM section background block 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

OptiX OSN 8800/6800/3800
transmission. And the far end background block error refers to the background block error
Related Alarms
OTUk_BDI OTU SM section backward defect indication.
Procedure
Step 1 See the procedure for handling the OTUk_BDI alarm.
----End
Related Information
None
6.119 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
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

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.120 OTUk_FEES
Description
OTU SM section far end errored second
Impact on System

OTU SM section errors are 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
Related Alarms
Procedure
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.121 OTUk_FESES
Description
OTU SM section far end severely errored second
Impact on System

OTU SM Section errors are detected by checking the received parity bit. During a severely
errored second, there is at least one defect or 15% of the 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
Related Alarms
Procedure
----End
Related Information
None
6.122 OTUk_FESESR
Description
OTU SM section ratio of far end severely errored second
Impact on System

OptiX OSN 8800/6800/3800

the far end.
Related Alarms
Procedure
----End
Related Information
None
6.123 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

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.124 OTUk_IAES
Description
OTU SM section introducing alignment errored second
Impact on System

The OTUk_LOF alarm is generated at the upstream station.
Related Alarms
OTUk_LOF OTU frame loss. The upstream station detects the LOF alarm and then
inserts IAE. The local station reports OTUk_IAES.
Procedure
----End
Related Information
None
6.125 OTUk_SES
Description
OTU severely errored second

OptiX OSN 8800/6800/3800
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in a

Error is detected by checking the received parity bit. During a severely errored second, there is
at least one defect or 15% of the 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

Procedure
----End
Related Information
None
6.126 OTUk_SESR
Description
OTU ratio of severely errored second
Impact on System
There are severely errored second in the services. Identify the cause and solve the problem in a


OptiX OSN 8800/6800/3800
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

Procedure
----End
Related Information
None
6.127 OTUk_TMP
Description
Total period for monitoring performance of OTU signals in the SM section
Impact on System
None

of OTU signals in the SM section, including the OTUk_BBE, OTUk_BBER, OTUk_BIAES,
OTUk_ES, OTUk_IAES, OTUk_SES, OTUk_SESR and OTUk_UAS performance. The
functions are enabled. When ports are working properly, the value of OTUk_TMP, which is
expressed in seconds, increases with the working time.

OptiX OSN 8800/6800/3800
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.128 OTUk_UAS
Description
OTU unavailable second
Impact on System

available.
Related Alarms

Procedure
----End

OptiX OSN 8800/6800/3800
Related Information
None
6.129 PCLSOP
Description
Per-channel laser output power, indicating the optical power of a channel of signals monitored
by the spectrum analyzer unit.
It includes:
l PCLSOPMAX: stands for the maximum value during a period of time.

l PCLSOPMIN: stands for the minimum value during a period of time.
l PCLSOPCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signals to
check its optical power.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.130 PCLSSN
Description
Per-channel OSNR, indicating OSNR of a channel of signals monitored by the spectrum analyzer
unit.
It includes:
l PCLSSNMAX: stands for the maximum value during a period of time.

OptiX OSN 8800/6800/3800
l PCLSSNMIN: stands for the minimum value during a period of time.

l 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 signals.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None
6.131 PCLSWL
Description
Per-channel center wavelength, indicating the center 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.
l PCLSWLMIN: stands for the minimum value during a period of time.
l PCLSWLCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and selects a channel of signals to
check its center wavelength.
Related Alarms
None

OptiX OSN 8800/6800/3800
Procedure
Step 1 None
----End
Related Information
None
6.132 PCLSWLO
Description
Per-channel center wavelength deviation, indicating 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.

l PCLSWLOMIN: stands for the minimum value during a period of time.
l PCLSWLOCUR: stands for the current value.
Impact on System
None

The MCA board analyzes the multiplexed optical signals and checks and calculates the center
wavelength deviation of a channel of signals.
Related Alarms
None
Procedure
Step 1 None
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.133 PHASEOFFSET
Description
Time deviation between the master clock and a slave clock. It includes the
MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET performance
parameters, which indicate the maximum, minimum, and average time deviations respectively.
Impact on System

This performance event is generated when a deviation occurs between the master clock and a
slave clock.
Related Alarms
TIME_LOCK_FAIL Time lock failure alarm. When the time of an

NE is synchronized from the upstream, the
time lock status is locking. When the time of
an NE is not locked, this alarm is reported to
remind the user of the unlock status of the NE
time.
Procedure
Step 1 None
----End
Related Information
None
6.134 RMIOP
Description
Input optical power of the Raman amplifier
It includes:
l RMIOPMAX: Maximum input optical power of the Raman amplifier.

OptiX OSN 8800/6800/3800
l RMIOPMIN: Minimum input optical power of the Raman amplifier.

l RMIOPCUR: Current input optical power of the Raman amplifier.
Impact on System
None

This performance event is generated when the reverse pump optical power of a Raman amplifier
is detected.
Related Alarms
RM_RLOS Loss of input reverse pump optical signals. This alarm is reported
when input reverse pump optical signals are lost.
Procedure
Step 1 See the procedure for handling the RM_RLOS alarm.
----End
Reference
None
6.135 RPL
Description
Input optical power
It includes:
l RPLMAX: stands for the maximum value during a period of time.

l RPLMIN: stands for the minimum value during a period of time.
l 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 ports.

OptiX OSN 8800/6800/3800

The performance event is adopted to monitor the value of the input optical power of the laser,
and to know the historical maximum, historical minimum and current input optical power of the
laser.
Related Alarms
IN_PWR_LOW This alarm is generated when the input optical power is lower than
the lower threshold of the input optical power.
IN_PWR_HIGH This alarm is generated when the input optical power is higher than
the upper threshold of the input optical power.
Procedure
----End
Related Information
None
6.136 RS_TMP
Description
Total period for monitoring performance of regenerator section
Impact on System
None

of regenerator section, including the RSBBE, RSCSES, RSES, RSOFS, RSSES and RSUAS
performance. The performance event is not collected statistics when an optical module cannot
be found or an optical path is not used. When ports are working properly, the value of RS_TMP,
which is expressed in seconds, increases with the working time.
Related Alarms
None

OptiX OSN 8800/6800/3800
Procedure
Step 1 None
----End
Related Information
None
6.137 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
B1_EXC Regenerator section (B1) excessive errors.

This alarm is generated when the received
signals in SDH frame degrade and the B1 bit
errors in the multiplex section exceed the
threshold.
Procedure
Step 1 See the procedure for handling the B1_EXC alarms.
----End
Related Information
None

OptiX OSN 8800/6800/3800
6.138 RSCSES
Description
RS consecutive 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 15% of the 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

threshold.
Procedure
----End
Related Information
None
6.139 RSES
Description
Regenerator section (RS) errored second

OptiX OSN 8800/6800/3800
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.
Related Alarms

threshold.
Procedure
----End
Related Information
None
6.140 RSOFS
Description
RS out-of-frame second
Impact on System
This performance event 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 loss of frame (LOF) if it lasts more than 3 ms.

OptiX OSN 8800/6800/3800
Related Alarms
R_OOF Out of frame alarm. This alarm is generated

when the headers of five consecutive frames
fail to be detected.
R_LOF Loss of frame alarm. This alarm is generated

when the frame alignment processing is in the
OOF state for three consecutive milliseconds.
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 port of the board is within the permitted
range using an optical power meter. For the optical power specifications of the specific board,
see "Technical Specifications" in the Product Description. If the power is not within the
permitted range, add proper attenuation by adding a fix optical attenuator (FOA) or a variable
optical attenuator (VOA).
Step 3 Replace the board.
----End
Related Information
None
6.141 RSOOF
Description
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:

OptiX OSN 8800/6800/3800
l The performance of the optical fiber is degraded.

Related Alarms
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 See the procedures for handling the R_OOF and R_LOF alarms.
----End
Related Information
None
6.142 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 15% of blocks are error blocks.

OptiX OSN 8800/6800/3800
Related Alarms

threshold.
Procedure
----End
Related Information
None
6.143 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

threshold.

OptiX OSN 8800/6800/3800
Procedure
----End
Related Information
None
6.144 SUMIOP
Description
Total input optical power
It includes:
l SUMIOPMAX: stands for the maximum value during a period of time.

l SUMIOPMIN: stands for the minimum value during a period of time.
l SUMIOPCUR: stands for the current value.
Impact on System
If the total input optical power is excessively high, the optical modules on the local board and
the downstream board may be damaged and cause bit errors in the services or even service
interruption. If the total input optical power is excessively low, the single-wavelength optical
signals output by the board may be lost and cause bit errors in the services or even service
interruption.

by the software for conversion.
SUMIOP is the total input optical power of the demultiplexer and optical amplifier boards.
Related Alarms
IN_PWR_HIGH This alarm 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 This alarm 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.

OptiX OSN 8800/6800/3800
SUM_INPWR_HI This alarm is generated when the detected total input optical power
is higher than the upper threshold.
SUM_INPWR_LO This alarm is generated when the detected total input optical power
W is lower than the lower threshold.
Procedure
(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.
Step 3 If an alarm is generated, see the related handling procedure.
----End
Related Information
None
6.145 SUMOOP
Description
Total output optical power
It includes:
l SUMOOPMAX: stands for the maximum value during a period of time.

l SUMOOPMIN: stands for the minimum value during a period of time.
l SUMOOPCUR: stands for the current value.
Impact on System
The total output power has 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.

OptiX OSN 8800/6800/3800

by the software for conversion.
SUMOOP is the total optical power output by the multiplexer and optical amplifier boards. On
a multiplexer board, the input signals pass the multiplexer and then output the total optical power
at the OUT port, while on an amplifier board, the input signals pass the amplifier and then output
the total optical power at the OUT port.
Related Alarms
OUT_PWR_HIGH This alarm 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 This alarm 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.
Step 3 If an alarm is generated, see the related handling procedure.
----End
Related Information
None
6.146 TDC
Description
Dispersion compensation value
It includes:
l TDCMAX: stands for the maximum dispersion compensation value during a period of time.

OptiX OSN 8800/6800/3800
l TDCMIN: stands for the minimum dispersion compensation value during a period of time.
l TDCCUR: stands for the current dispersion compensation value during a period of time.
Impact on System
None

The TDC performance value is the dispersion compensation value during a period of time.
Related Alarms
OTUk_LOF Abnormal frame alignment signal alarm. This

alarm is generated when the dispersion
compensation value is excessively large or
small.
Procedure
----End
Related Information
None
6.147 TLB
Description
Laser bias current value
It includes:
l TLBMAX: stands for the maximum value during a period of time.

l TLBMIN: stands for the minimum value during a period of time.
l TLBCUR: stands for the current value.
Impact on System
This 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 permitted range,
you do not need to take any action.

OptiX OSN 8800/6800/3800

The performance event helps users monitor the bias current of the laser and its historical
maximum, historical minimum and current value.
Related Alarms
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.148 TPL
Description
Output optical power
It includes:
l TPLMAX: stands for the maximum value during a period of time.

l TPLMIN: stands for the minimum value during a period of time.
l 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
permitted 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 learn about its historical maximum, historical minimum and current value.

OptiX OSN 8800/6800/3800
Related Alarms
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.149 VC3BBE

VC-3 background block error

If bit errors occur in the services, identify the cause and solve the problem in a timely manner
to avoid any alarm, and therefore ensuring 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.
l The fiber connector is dirty or incorrect.
l The equipment is improperly grounded.
l There is a strong interference source around the equipment.
l The working temperature is excessively high or low, and the opposite equipment cannot
tolerate such temperature.
Equipment problems:

OptiX OSN 8800/6800/3800
l 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.
l The synchronization performance of the clock is poor.
l The cross-connect unit and the service board do not work with each other properly.
l The board becomes faulty, or the performance of the board is degraded.
Relevant Alarms
B3_EXC_VC3 B3 bit errors exceed 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. When this
occurs, 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.135
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. When this occurs,
replace the clock unit.
Step 3 If only a service board reports that bit errors exist, the local service board might be faulty or that
the opposite NE or fibers are faulty. Locate the faulty board using the loopback method. Then,
replace the faulty board.
----End
Reference
None.
6.150 VC3CSES

VC-3 continuous severely errored second

the B3 bit error threshold-crossing threshold and degrade threshold, the B3_EXC and B3_SD
alarms will be generated.

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:
Equipment problems:
faulty.
Relevant Alarms
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 See 6.151 VC3ES.
----End

OptiX OSN 8800/6800/3800
Reference
None.
6.151 VC3ES

VC-3 errored second

the 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 port, or
when the AU_AIS, AU_LOP and LP_UNEQ_VC3 alarms are detected over the path.
External causes:
Equipment problems:
faulty.
Relevant Alarms

OptiX OSN 8800/6800/3800
R_LOS The signal on the receiver line side is lost.
R_LOF The out-of-frame fault occurs on the receive line side.
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.
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.
whether the service board reports the AS_AIS alarm by performing self-loop on the fibers.

OptiX OSN 8800/6800/3800
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:

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. When this occurs, replace the faulty
board.
Step 6 See 6.149 VC3BBE.
----End
Reference
None.
6.152 VC3FEBBE

VC-3 far end background block error

If bit errors occur in the services on a remote NE, identify the cause and solve the problem in a
timely manner to avoid any alarm, and therefore ensuring 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 The fiber performance degrades and the attenuation is excessively high at the opposite
station.
l The fiber connector is dirty or incorrect at the opposite station.
l The equipment is improperly grounded at the opposite station.
l There is a strong interference source around the equipment at the opposite station.
Equipment problems:
l The signal attenuation at the receive side of the service 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.
l The synchronization performance of the clock is poor at the opposite station.

OptiX OSN 8800/6800/3800
l The cross-connect unit and the service board do not work with each other properly at the
opposite station.
l The fan of the opposite equipment becomes faulty.
l The board fails or the board performance degrades at the opposite station.
Relevant Alarms
LP_RDI_VC3 VC-3 path remote defect indication
Procedure
Step 1 See 6.149 VC3BBE to handle the NE at the opposite end.
----End
Reference
None.
6.153 VC3FECSES

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:

OptiX OSN 8800/6800/3800
opposite station.
Relevant Alarms
Procedure
Step 1 See 6.154 VC3FEES.
----End
Reference
None.
6.154 VC3FEES

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:
station.

OptiX OSN 8800/6800/3800
Equipment problems:
opposite station.
Relevant Alarms
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 See 6.152 VC3FEBBE.
----End
Reference
None.
6.155 VC3FESES

VC-3 far end severely errored second

OptiX OSN 8800/6800/3800

Possible Causes
The VC3FESES performance event occurs when not less than 15% 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:
station.
Equipment problems:
opposite station.
Relevant Alarms
Procedure
----End
Reference
None.

OptiX OSN 8800/6800/3800
6.156 VC3FEUAS

VC-3 far end unavailable second

Possible Causes
VC3FEUAS indicates the period of time that the unavailable time (UAT) state lasts.
External causes:
station.
Equipment problems:
opposite station.
Relevant Alarms
Procedure
----End

OptiX OSN 8800/6800/3800
Reference
None
6.157 VC3SES

VC-3 far end severely errored second

the 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 15% 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:
Equipment problems:
faulty.
Relevant Alarms

OptiX OSN 8800/6800/3800
Procedure
----End
Reference
None.
6.158 VC3UAS

VC-3 unavailable second

the 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:

OptiX OSN 8800/6800/3800
Equipment problems:
faulty.
Relevant Alarms
Procedure
----End
Reference
None
6.159 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).

OptiX OSN 8800/6800/3800
l WCVMIN: stands for the minimum value during a period of time (in 1 mA).
l WCVCUR: stands for the current value (in 1 mA).
Impact on System
When the pump laser works properly, there is no impact on the services. If an alarm is generated,
identify 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
PUM_BCM_ALM Pump laser bias current threshold-crossing alarm. The board reports
this alarm when the detected pump laser drive current is higher than
the threshold due to laser exceptions caused by laser aging, or over-
high/low ambient temperature.
LSR_WILL_DIE Laser life time termination alarm. The board reports this alarm when
the pump laser drive current is higher than the termination threshold
due to laser aging.
TD Transmitting laser degrade alarm. The threshold of the laser is set to

a value 1.2 times of the initial value of the bias current. This alarm is
generated when the bias current of the laser exceeds the threshold and
is smaller than the initial value by 1.5 times.
Procedure
Step 1 If the PUM_BCM_ALM alarm is generated, see the related handling procedure.
Step 2 If the LSR_WILL_DIE alarm is generated, see the related handling procedure.
Step 3 If the TD alarm is generated, see the related handling procedure.
----End
Related Information
None

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 7 Event List
7 Event List
This section list the common events.
Table 7-1 Events regarding APE
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.
Table 7-2 Events regarding IPA
IPA abnormal event Major When IPA adjustment is terminated due to a

fault of the laser, an IPA abnormal event is
reported.
Table 7-3 Events regarding ROADM
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.

OptiX OSN 8800/6800/3800
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 Critical After a wavelength resource consistency

event 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
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 Critical This event is reported when a protection

protection switching event switching occurs on a cross-connect board or
on the system control and communication
(SCC) board.
Table 7-5 Other events
RMON performance value is Minor This event is automatically reported when the
above the upper limit performance value in the sampling period is

OptiX OSN 8800/6800/3800
RMON module performance Minor In the sampling period, an event indicating

value is lower than the lower upper threshold crossing occurs. In a new
threshold sampling period, when the sampling value is
less than or is equal to the lower threshold
value, this event is reported.

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference 8 Event Processing
8 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 OWSP abnormal event
8.2 ODUk SPRing abnormal event
8.3 RMON performance value is above the upper limit
8.4 RMON module performance value is lower than the lower threshold
8.5 1+1 Equipment Level Protection Switching Event Report

OptiX OSN 8800/6800/3800
8.1 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
Parameter 1 Indicates the ID of the protection group where the

protection switching occurs.
Parameter 2 Indicates the status of the westbound working channel.

The values of the parameter are as follows:
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.


OptiX OSN 8800/6800/3800
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 Indicates the switching request of the eastbound channel.

The values of the parameter are the same as those of
Parameter 6.
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
Parameter 9 Indicates the indication of westbound remote and local

ends. The values of the parameter are as follows:
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

OptiX OSN 8800/6800/3800
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.
l Cause 2: An external switching command is issued.
Procedure
l Cause 1: The current working channel is abnormal.
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.
l Cause 2: An external switching command is issued.
1. Ignore the event.
----End
Related Information
None
8.2 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
Major Communication
Parameter
Parameter 1 Indicates the ID of the protection group where this event

occurs.

OptiX OSN 8800/6800/3800
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
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

OptiX OSN 8800/6800/3800
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.
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.
l 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.
l 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.
Procedure
l 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.
l Cause 2: The service is automatically switched to the protection channel

OptiX OSN 8800/6800/3800
1. On the U2000, query the related switching alarms. For details, see Handling Procedure
parts for respective alarms.
----End
Related Information
None
8.3 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
Minor Communication
Parameter
Parameter 1 Indicates the slot ID, port number and channel number,
such as 1-LOG-2(ETHER):1.

OptiX OSN 8800/6800/3800
Parameter 2 Indicates the performance event of threshold crossing.

Drop Events
FCS and Alignment Errors
Undersize Packets Received
Oversize Packets Received
Fragments
Jabbers
Collisions
Bad Octets Received
Bad Octets Transmitted
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.
l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
l Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
l Cause 4: The optical fiber is damaged or the fiber connector is untidy.
Procedure
l Cause 1: The client-side data equipment is faulty, and the equipment incorrectly transmits
the data packets.

OptiX OSN 8800/6800/3800
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.
l Cause 2: The working modes of the ports at the local and opposite ends mismatch.
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.
l Cause 3: The optical line attenuation is excessively large or the receive optical power is
abnormal.
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 the specific board, see
"Technical Specifications" in 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.
l Cause 4: The optical fiber is damaged or the fiber connector is untidy.
1. Check the fiber connector. If it is dirty, clean or replace the fiber connector.
1. If this event persists, replace the faulty board.
----End
Related Information
None
8.4 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
Minor Communication

OptiX OSN 8800/6800/3800
Parameter
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
FCS and Alignment Errors
Undersize Packets Received
Oversize Packets Received
Fragments
Jabbers
Collisions
Bad Octets Received
Bad Octets Transmitted
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

OptiX OSN 8800/6800/3800
Related Information
None
8.5 1+1 Equipment Level Protection Switching Event Report

Description
1+1 Equipment Level Protection Switching Event Report, when the cross-connect board, the
system auxiliary interface board or the SCC board protection switching occurs, this event is
reported.
Attribute
Critical Equipment
Parameter
Parameter 1 Indicates the ID of the protection group where this

event occurs, The values of the parameter are as
follows:
For Optix OSN 3800, the value is 1, indicates the
SCC board protection switching occurs.
For Optix OSN 6800 and Optix OSN 8800, the value
is 1, indicates the cross-connect board protection
switching occurs.
For Optix OSN 6800 and Optix OSN 8800, 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.

OptiX OSN 8800/6800/3800
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.
l 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.
Procedure
l Cause 1: The user issues an external switching command.
l 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

OptiX OSN 8800/6800/3800
Alarms and Performance Events Reference A Glossary
A Glossary
Numerics
3G See 3rd Generation.
3R reshaping, retiming, regenerating
3rd Generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to
19.2 kbit/s offered by second generation technology.
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
(QinQ) implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN
tag to allow the frame with double VLAN tags to be transmitted over the service
provider's backbone network based on the public VLAN tag. This provides a layer 2
VPN tunnel for customers and enables transparent transmission of packets over private
VLANs.
A
A/D analog/digit
AA authentication authorization
AAA See Authentication, Authorization and Accounting.
AC alternating current
ACH associated channel header
ACK See acknowledgement.
ACL See access control list.
ACR allowed cell rate
ACS See Application Control Server.
ADC analog to digital converter
ADM add/drop multiplexer
ADSL See asymmetric digital subscriber line.

OptiX OSN 8800/6800/3800
AF See assured forwarding.

AG See Access Gateway.
AGC automatic gain control
AH See Authentication Header.
AIN advanced intelligent network
AIS alarm indication signal
AK See access key ID.
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 fulfills optical
power control on the line that contains the link.
ALS See automatic laser shutdown.
APD See avalanche photodiode.
APE See automatic power equilibrium.
API See application programming interface.
APID access point identifier
APS automatic protection switching
APS 1+1 protection A protection architecture that comprises one protection facility and one working facility
and performs switchover by using the Automatic Protection Switching (APS) protocol.
Normally, signals are sent only over the working facility. If an APS switchover event is
detected by the working facility, services are switched over to the protection facility.
ARP See Address Resolution Protocol.
AS See autonomous system.
ASCII American Standard Code for Information Interchange
ASE amplified spontaneous emission
ASIC See application-specific integrated circuit.
ATAE See Advanced Telecommunications Application Environment.
ATM asynchronous transfer mode
AU adaptation unit
AUG See administrative unit group.
AWG arrayed waveguide grating
Access Gateway (AG) A type of gateway that provides a user-network interface (UNI) such as ISDN. An access
gateway is located at the edge access layer of the NGN structure, and provides various
methods for connecting users to the NGN.

OptiX OSN 8800/6800/3800
Address Resolution An Internet Protocol used to map IP addresses to MAC addresses. The ARP protocol
Protocol (ARP) enables hosts and routers to determine link layer addresses through ARP requests and
responses. The address resolution is a process by which the host converts the target IP
address into a target MAC address before transmitting a frame. The basic function of
ARP is to use the target equipment's IP address to query its MAC address.
Advanced A carrier-class processing platform that is designed to meet the service application
Telecommunications requirement of high performance, high specialization, and high integration.
Application
Environment (ATAE)
Application Control A subsystem of the Media Entertainment Middleware (MEM), used for providing a
Server (ACS) service control interface for the Electronic Program Guide (EPG) server.
Authentication Header A protocol that provides connectionless integrity, data origin authentication, and anti-
(AH) replay protection for IP data.
Authentication, A mechanism for configuring authentication, authorization, and accounting security
Authorization and services. Authentication refers to the verification of user identities and the related
Accounting (AAA) network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
access control list A list of entities, together with their access rights, which are authorized to access a
(ACL) resource.
access key ID (AK) An ID that confirms the identity of a user accessing the object-based storage system.
One access key ID belongs to only one user, but one user can have multiple access key
IDs. The object-based storage system recognizes the users accessing the system by their
access key IDs.
acknowledgement A response sent by a receiver to indicate reception of information. Acknowledgements
(ACK) may be implemented at any level, including the physical level (using voltage on one or
more wires to coordinate a transfer), link level (indicating transmission across a single
hardware link), or higher levels.
administrative unit One or more administrative units occupying fixed, defined positions in an STM payload.
group (AUG) An AUG consists of AU-4s.
aging time The time to live before an object becomes invalid.
alarm cascading The method of cascading alarm signals from several subracks or cabinets.
alarm indication A mechanism to indicate the alarm status of equipment. On the cabinet of an NE, four
differently-colored indicators specify the current status of the NE. When the green
indicator is on, the NE is powered on. When the red indicator is on, a critical alarm has
been generated. When the orange indicator is on, a major alarm has been generated.
When the yellow indicator is on, a minor alarm has been generated. The ALM alarm
indicator on the front panel of a board indicates the current status of the board.
application An application programming interface is a particular set of rules and specifications that
programming interface are used for communication between software programs.
(API)
application-specific A special type of chip that starts out as a nonspecific collection of logic gates. Late in
integrated circuit the manufacturing process, a layer is added to connect the gates for a specific function.
(ASIC) By changing the pattern of connections, the manufacturer can make the chip suitable for
many needs.

OptiX OSN 8800/6800/3800
assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.
(AF) It is suitable for certain key data services that require assured bandwidth and short delay.
For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that
exceeds the bandwidth limit, AF degrades the service class and continues to forward the
traffic instead of discarding the packets.
asymmetric digital A technology for transmitting digital information at a high bandwidth on existing phone
subscriber line (ADSL) 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 kbit/s to about 6 Mbit/s.
automatic laser A technique (procedure) to automatically shutdown the output power of laser transmitters
shutdown (ALS) and optical amplifiers to avoid exposure to hazardous levels.
automatic level control A function that keeps output power of components in a system essentially constant, even
(ALC) when line attenuation in a section of the system increases.
automatic power A function to automatically equalize channel optical power at the transmitter end,
equilibrium (APE) ensuring a required optical power flatness and OSNR at the receiver end.
autonomous system A network set that uses the same routing policy and is managed by the same technology
(AS) administration department. Each AS has a unique identifier that is an integer ranging
from 1 to 65535. The identifier is assigned by IANA. An AS can be divided into areas.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
(APD) 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.
B
B/S browser/server
BA booster amplifier
BBC See battery backup cabinet.
BBER background block error ratio
BC boundary clock
BDI See backward defect indication.
BE See best effort.
BEI backward error indication
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIAE backward incoming alignment error
BIOS See basic input/output system.
BIP-8 See bit interleaved parity-8.

OptiX OSN 8800/6800/3800
BITS See building integrated timing supply.

BMC best master clock
BOM bill of materials
BPDU See bridge protocol data unit.
BPS board protection switching
BPSK See binary phase shift keying.
BRA See basic rate access.
BRAS See broadband remote access server.
BTS base transceiver station
Bidirectional A fast and independent hello protocol that delivers millisecond-level link failure
Forwarding Detection detection and provides carrier-class availability. After sessions are established between
(BFD) neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system regards
that the bidirectional link fails and instructs the upper layer protocol to take actions to
recover the faulty link.
backplane An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to inform the
indication (BDI) upstream end of the LSP of a downstream defect along the return path.
basic input/output Firmware stored on the computer motherboard that contains basic input/output control
system (BIOS) programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
basic rate access (BRA) An ISDN interface typically used by smaller sites and customers. This interface consists
of a single 16 kbit/s data (or "D") channel plus two bearer (or "B") channels for voice
and/or data. Also known as Basic Rate Access, or BRI.
battery backup cabinet A cabinet that contains a built-in battery group to back up -48 V DC power and to supply
(BBC) power to the base station when there is no power input. It is a component of a base station.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of the
network and routers. The amount of resource that a diagram can use depends of the time
it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss
ratio, and high reliability.
binary phase shift 2-phase modulation for carrier based on binary baseband signal. In this modulation mode,
keying (BPSK) the binary character 0 represents phase 0 of the carrier, and character 1 represents the
phase 180. The phase of character 0 is 0, and the phase of character 1 needs to be
specified. This is an absolute phase shift mode that uses different phases to represent
digital information.
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.

OptiX OSN 8800/6800/3800
bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a
(BIP-8) transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte)
in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0"
over each column. Then fill a 1 in the corresponding bit for the result if the number is
odd, otherwise fill a 0.
bridge A device that connects two or more networks and forwards packets among them. Bridges
operate at the physical network level. Bridges differ from repeaters because bridges store
and forward complete packets, while repeaters forward all electrical signals. Bridges
differ from routers because bridges use physical addresses, while routers use IP
addresses.
bridge protocol data Data messages exchanged across switches within an extended LAN that uses a spanning
unit (BPDU) tree protocol (STP) topology. BPDU packets contain information on ports, addresses,
priorities, and costs, and they ensure that the data reaches its intended destination. BPDU
messages are exchanged across bridges to detect loops in a network topology. These
loops are then removed by shutting down selected bridge interfaces and placing
redundant switch ports in a backup, or blocked, state.
broadband remote A new type of access gateway for broadband networks. As a bridge between backbone
access server (BRAS) networks and broadband access networks, BRAS provides methods for fundamental
access and manages the broadband access network. It is deployed at the edge of network
to provide broadband access services, convergence, and forwarding of multiple services,
meeting the demands for transmission capacity and bandwidth utilization of different
users. BRAS is a core device for the broadband users' access to a broadband network.
broadcast domain A group of network stations that receives broadcast packets originating from any device
within the group. The broadcast domain also refers to the set of ports between which a
device forwards a multicast, broadcast, or unknown destination frame.
building integrated In the situation of multiple synchronous nodes or communication devices, one can use
timing supply (BITS) 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.
burst A process of forming data into a block of the proper size, uninterruptedly sending the
block in a fast operation, waiting for a long time, and preparing for the next fast sending.
byte A unit of computer information equal to eight bits.
C
CAPEX capital expenditure
CAR committed access rate
CBR See constant bit rate.
CBS See committed burst size.
CC See continuity check.
CCM continuity check message
CD chromatic dispersion
CDR See call detail record.
CE See customer edge.

OptiX OSN 8800/6800/3800
CENELEC European Committee for Electrotechnical Standardization

CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIR committed information rate
CIST See Common and Internal Spanning Tree.
CLI command-line interface
CLNP connectionless network protocol
CMEP connection monitoring end point
CMI coded mark inversion
CNP connection-not-possible signal
CORBA See Common Object Request Broker Architecture.
COS chip operating system
CP cyclic prefix
CPLD complex programmable logical device
CPRI See common public radio interface.
CPU See central processing unit.
CR carriage return
CR-LDP Constraint-based Routed Label Distribution Protocol
CRC See cyclic redundancy check.
CS class selector
CSA Canadian Standards Association
CSES consecutive severely errored second
CSF Client Signal Fail
CSMA/CD See carrier sense multiple access with collision detection.
CSPF Constrained Shortest Path First
CST See common spanning tree.
CSV See comma separated values.
CV connectivity verification
CW control word
CWDM See coarse wavelength division multiplexing.
CoS class of service

OptiX OSN 8800/6800/3800
Common Object A specification developed by the Object Management Group in 1992 in which pieces of
Request Broker programs (objects) communicate with other objects in other programs, even if the two
Architecture (CORBA) programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and therefore does not need to know the structure of the program from which the
object comes. CORBA is designed to work in object-oriented environments.
Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
cabinet A physical entity for containing one or more shelves, providing the cooling, power, and
security functions.
call detail record A record unit used to create billing records. A CDR contains details such as the called
(CDR) and calling parties, originating switch, terminating switch, call length, and time of day.
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:
detection (CSMA/CD)
l A carrier sensing scheme is used.
l A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
(CPU) and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
channel spacing The center-to-center difference in frequencies or wavelengths between adjacent channels
in a WDM device.
circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks. At the
service (CES) transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
circulation The number of copies of a newspaper or magazine per issue that are circulated in the
market
clock synchronization A process of synchronizing clocks, in which the signal frequency traces the reference
frequency, but the start points do not need to be consistent. This process is (also known
as frequency synchronization).
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
division multiplexing the same fiber. CWDM spaces wavelengths at a distance of several nm. CWDM does
(CWDM) not support optical amplifiers and is applied in short-distance chain networking.
comma separated A CSV file is a text file that stores data, generally used as an electronic table or by the
values (CSV) database software.

OptiX OSN 8800/6800/3800
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of an
IP packet to be forwarded.
common public radio A common standard of the key internal interface between the REC and the RE of the
interface (CPRI) wireless base station. This standard was established by Huawei, Ericsson, NEC, Siemens,
and Nortel in June 2003. It aims at standardizing the baseband and RF interface. The
CPRI has a set of mature standards, which advance the standard and equipment. The
major feature of the CPRI is that baseband is separated from RF to reduce the cost of
engineering, equipment room, and equipment.
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST region
(CST) is considered as a switch; therefore, the CST can be considered as their spanning tree
generated with STP/RSTP.
composite service An aggregation of a series of services relevant to each other.
configuration data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other NEs in a network. Therefore, configuration data is the key factor
that determines the operation of an entire network.
consistency check A function that is used to check the consistency of service data and resource data between
two softswitches that have the dual homing relation. This ensures the consistency of
service data and resource data between the softswitches.
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
continuity check (CC) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
control VLAN A VLAN that transmits only protocol packets.
crossover cable A twisted pair patch cable wired in such a way as to route the transmit signals from one
piece of equipment to the receive signals of another piece of equipment, and vice versa.
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly connecting
to the Service Provider (SP) network. A CE can be a router, switch, or host.
cyclic redundancy A procedure used to check for errors in data transmission. CRC error checking uses a
check (CRC) complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the transmission
is considered to be error free. This procedure is known as a redundancy check because
each transmission includes not only data but extra (redundant) error-checking values.
D
DAPI destination access point identifier
DB database
DBMS Database Management System

OptiX OSN 8800/6800/3800
DBPS distributed board protect system

DC direct current
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited with
(with ground) (DC-C) the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with
ground) (DC-I) the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC See data communications channel.
DCE See data circuit-terminating equipment.
DCF See dispersion compensation fiber.
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
DEI device emulation interrupt
DHCP See Dynamic Host Configuration Protocol.
DIP switch dual in-line package switch
DLAG See distributed link aggregation group.
DM See delay measurement.
DMUX demultiplexer
DPSK differential phase shift keying
DRDB dynamic random database
DRZ differential phase return to zero
DS See Data Source.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP See differentiated services code point.
DSCR dispersion slope compensation rate
DSE dispersion slope equalizer
DSF See Distributed Service Framework.
DSLAM See digital subscriber line access multiplexer.
DSP See digital signal processor.
DSS door status switch
DTE See data terminal equipment.
DTMF See dual tone multiple frequency.

OptiX OSN 8800/6800/3800
DVB digital video broadcasting

DVB-ASI digital video broadcast-asynchronous serial interface
DVMRP See Distance Vector Multicast Routing Protocol.
DWDM See dense wavelength division multiplexing.
Data Source (DS) A system, database, or file that can make BOs persistent. A data source can be a database
instance or a database user.
DiffServ See Differentiated Services.
Differentiated Services An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ) differentiated manner based on CoS settings to handle network congestion.
Distance Vector An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
Multicast Routing implements a typical dense mode IP multicast solution and uses IGMP to exchange
Protocol (DVMRP) routing datagrams with its neighbors.
Distributed Service A distributed service development and running framework, in which services comply
Framework (DSF) with standard specifications, and can be loaded and run by containers. This framework
provides a range of services including registration, detection, routing, and distributed
access.
DoS denial of service
Dynamic Host A client-server networking protocol. A DHCP server provides configuration parameters
Configuration Protocol specific to the DHCP client host requesting information the host requires to participate
(DHCP) on the Internet network. DHCP also provides a mechanism for allocating IP addresses
to hosts.
data circuit- The equipment that provides the signal conversion and coding between the data terminal
terminating equipment equipment (DTE) and the line. A DCE is located at a data station. The DCE may be
(DCE) separate equipment, or an integral part of the DTE or intermediate equipment. The DCE
may perform other functions that are normally performed at the network end of the line.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
channel (DCC) transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to as
the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12 is
referred to as the 576 kbit/s DCC-M channel.
data terminal A user device composing the UNI. The DTE accesses the data network through the DCE
equipment (DTE) equipment (for example, a modem) and usually uses the clock signals produced by DCE.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) node until the reception of the last bit of the loopbacked frame by the same source node,
when the loopback is performed at the frame's destination node.
dense wavelength The technology that utilizes the characteristics of broad bandwidth and low attenuation
division multiplexing of single mode optical fiber, employs multiple wavelengths with specific frequency
(DWDM) spacing as carriers, and allows multiple channels to transmit simultaneously in the same
fiber.
designated switch A designated switch of a device is a switch that is directly connected to the device and
forwards BPDUs to the device.

OptiX OSN 8800/6800/3800
detection sensitivity The capability for a detector to respond to an exception.

differentiated services According to the QoS classification standard of the Differentiated Service (Diff-Serv),
code point (DSCP) the type of services (ToS) field in the IP header consists of six most significant bits and
two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It is
the combination of IP precedence and types of service. The DSCP value is used to ensure
that routers supporting only IP precedence can be used because the DSCP value is
compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB). Therefore,
terminal devices can identify traffic using the DSCP value.
digital signal processor A microprocessor designed specifically for digital signal processing, generally in real
(DSP) time.
digital subscriber line A network device, usually situated in the main office of a telephone company, that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections and
(DSLAM) uses multiplexing techniques to put these signals on a high-speed backbone line.
dispersion A type of fiber that uses negative dispersion to compensate for the positive dispersion
compensation fiber of the transmitting fiber to maintain the original shape of the signal pulse.
(DCF)
dispersion A type of module that contains dispersion compensation fibers to compensate for the
compensation module dispersion of the transmitting fiber.
(DCM)
distributed link A board-level port protection technology that detects unidirectional fiber cuts and
aggregation group negotiates with the opposite port. In the case of a link down failure on a port or hardware
(DLAG) failure on a board, services are automatically switched to the slave board, thereby
achieving 1+1 protection for the inter-board ports.
domain A logical subscriber group based on which the subscriber rights are controlled.
dotted decimal notation A format of IP address. IP addresses in this format are separated into four parts by a dot
"." with each part is in the decimal numeral.
downlink traffic The network traffic transferred into an internal carrier network. Noticeably, downlink
refers to sending traffic to user-end link nodes.
downstream In an access network, the direction of transmission toward the subscriber end of the link.
dual feed and selective A channel used to transmit monitoring data on an optical transmission network. The
receiving monitoring data is transmitted on the data communications channel as part of the
overhead of the service signal.
dual tone multiple Multi-frequency signaling technology for telephone systems. According to this
frequency (DTMF) technology, 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 high frequencies, are
used.
dual-ended switching A protection method in which switching is performed at both ends of a protected entity,
such as a connection or path, even if a unidirectional failure occurs.
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.

OptiX OSN 8800/6800/3800
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides

thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization, and
timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as speech
channels. Each timeslot sends or receives an 8-bit data per second. Each frame sends or
receives 256-bit data per second. 8000 frames will be sent or received per second.
Therefore the line data rate is 2.048 Mbit/s.
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.
EEC Ethernet Electric Interface PMC Card
EEPROM See electrically erasable programmable read-only memory.
EF See expedited forwarding.
EFM Ethernet in the First Mile
EIR See excess information rate.
EMC See electromagnetic compatibility.
EMF element management framework
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logic device.
EPON See Ethernet passive optical network.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
ESCON See enterprise system connection.
ESD electrostatic discharge
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVC Ethernet virtual connection
EVOA electrical variable optical attenuator
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
EXP See experimental bits.
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).

OptiX OSN 8800/6800/3800
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
Ethernet passive A passive optical network based on Ethernet. It is a new generation broadband access
optical network technology that uses a point-to-multipoint structure and passive fiber transmission. It
(EPON) supports upstream/downstream symmetrical rates of 1.25 Gbit/s and a reach distance of
up to 20 km. In the downstream direction, the bandwidth is shared based on encrypted
broadcast transmission for different users. In the upstream direction, the bandwidth is
shared based on TDM. EPON meets the requirements for high bandwidth.
Ethernet private LAN A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
service (EPLAN) networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
(EPL) networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private LAN service networks. This service is carried over shared bandwidth between multipoint-to-
(EVPLAN) multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private line (EVPL) networks. This service is carried over shared bandwidth between point-to-point
connections.
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
(ETSI)
eDQPSK enhanced differential quadrature phase shift keying
eSFP enhanced small form-factor pluggable
egress The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory A technology that implements communication among all the nodes and transmission of
channel (ESC) monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable
programmable read- storage for long periods without electricity while still allowing reprograming. EEPROMs
only memory contain less memory than RAM, take longer to reprogram, and can be reprogramed only
(EEPROM) a limited number of times before wearing out.
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) 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.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer
channel (ECC) to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.

OptiX OSN 8800/6800/3800
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a message
from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
enterprise system A path protocol that connects the host to various control units in a storage system.
connection (ESCON) Enterprise system connection is a serial bit stream transmission protocol that operates a
rate of 200 Mbit/s.
erasable A logic array device which can be used to implement the required functions by
programmable logic programming the array. In addition, a user can modify and program the array repeatedly
device (EPLD) until the program meets the requirement.
erbium-doped fiber An optical device that amplifies optical signals. This device uses a short optical fiber
amplifier (EDFA) doped with the rare-earth element, Erbium. The signal to be amplified and a pump laser
are multiplexed into the doped fiber, and the signal is amplified by interacting with
doping ions. When the amplifier passes an external light source pump, it amplifies the
optical signals in a specific wavelength range.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode, traffic
control is achieved by token buckets C and E. The excess burst size parameter defines
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
greater than 0 but should be not less than the maximum length of an IP packet to be
forwarded.
excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
(EIR) actual transmission rate without the safety rate.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that
(EF) demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF
traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP
value of EF PHB is "101110".
experimental bits A field in the MPLS packet header, three bits long. This field is always used to identify
(EXP) the CoS of the MPLS packet.
eye pattern An oscilloscope display in which a digital data signal from a receiver is repetitively
sampled and applied to the vertical input, while the data rate is used to trigger the
horizontal sweep. It is so called because, for several types of coding, the pattern looks
like a series of eyes between a pair of rails.
F
FBG fiber Bragg grating
FC See Fibre Channel.
FDB flash database
FDD See frequency division duplex.
FDDI See fiber distributed data interface.
FDI See forward defect indication.

OptiX OSN 8800/6800/3800
FDV See frame delay variation.

FE fast Ethernet
FEC See forward error correction.
FICON See Fibre Connect.
FIFO See first in first out.
FLR See frame loss ratio.
FMC See fixed mobile convergence.
FMT See fiber management tray.
FOA fixed optical attenuator
FOADM fixed optical add/drop multiplexer
FPGA See field programmable gate array.
FR See frame relay.
FRR See fast reroute.
FTP File Transfer Protocol
Fibre Channel (FC) A high-speed transport technology used to build SANs. FC is primarily used for
transporting SCSI traffic from servers to disk arrays, but it can also be used on networks
carrying ATM and IP traffic. FC supports single-mode and multi-mode fiber
connections, and can run on twisted-pair copper wires and coaxial cables. FC provides
both connection-oriented and connectionless services.
Fibre Connect A new generation connection protocol that connects the host to various control units. It
(FICON) carries a single byte command protocol through the physical path of fibre channel, and
provides a higher transmission rate and better performance than ESCON.
fast reroute (FRR) A technology which provides a temporary protection of link availability when part of a
network fails. The protocol enables the creation of a standby route or path for an active
route or path. When the active route is unavailable, the traffic on the active route can be
switched to the standby route. When the active route is recovered, the traffic can be
switched back to the active route. FRR is categorized into IP FRR, VPN FRR, and TE
FRR.
fiber distributed data A standard developed by the American National Standards Institute (ANSI) for high-
interface (FDDI) speed fiber-optic LANs. FDDI provides specifications for transmission rates of 100
megabits per second on token ring networks.
fiber management tray A device used to coil up extra optical fibers.
(FMT)
field programmable A semi-customized circuit that is used in the Application Specific Integrated Circuit
gate array (FPGA) (ASIC) field and developed based on programmable components. FPGA remedies many
of the deficiencies of customized circuits, and allows the use of many more gate arrays.
first in first out (FIFO) A stack management method in which data that is stored first in a queue is also read and
invoked first.

OptiX OSN 8800/6800/3800
fixed mobile Communication service provided based on the combination of fixed-line and wireless
convergence (FMC) technologies. Service providing, access technologies, and terminal devices on an FMC
network are independent from each other. The same service can be obtained from various
access networks. Subscribers from different access networks can obtain and use the same
service.
flow An aggregation of packets that have the same characteristics. On boards, it is a group of
packets that have the same quality of service (QoS) operation.
forced switching The action of switching traffic signals between a working channel and protection
channel. The switching occurs even if the channel to which traffic is being switched is
faulty or an equal or higher priority switching command is in effect.
forward defect A packet generated and traced forward to the sink node of the LSP by the node that first
indication (FDI) detects defects. It includes fields to indicate the nature of the defect and its location. Its
primary purpose is to suppress alarms being raised at affected higher level client LSPs
and (in turn) their client layers.
forward error A bit error correction technology that adds correction information to the payload at the
correction (FEC) transmit end. Based on the correction information, the bit errors generated during
transmission can be corrected at the receive end.
frame delay variation A measurement of the variations in the frame delay between a pair of service frames,
(FDV) where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the number
of service frames not delivered is the difference between the number of service frames
arriving at the ingress ETH flow point and the number of service frames delivered at the
egress ETH flow point in a point-to-point ETH connection.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
frequency division An application in which channels are divided by frequency. In an FDD system, the uplink
duplex (FDD) and downlink use different frequencies. Downlink data is sent through bursts. Both
uplink and downlink transmission use frames with fixed time length.
G
G-ACH generic associated channel header
GAL generic associated channel header label
GCC general communication channel
GE Gigabit Ethernet

OptiX OSN 8800/6800/3800
GE ADM A technique that improves the transmission of GE services on a metropolitan area

network. Using this technique, equipment configured with a high-speed backplane can
separately transmit, aggregate, or divert GE services over electrical-layer wavelengths
or sub-wavelengths. This achieves cross-connections of wavelengths and end-to-end
management of sub-wavelengths over a single device. GE ADM enables GE
convergence and cross-connections at the same time, thereby ensuring that network
resources are used effectively.
GFF gain flattening filter
GFP See Generic Framing Procedure.
GMPLS generalized multiprotocol label switching
GNE See gateway network element.
GPON gigabit-capable passive optical network
GPS See Global Positioning System.
GSM See Global System for Mobile Communications.
GSSP General Snooping and Selection Protocol
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing A framing and encapsulated method that can be applied to any data type. GFP is defined
Procedure (GFP) by ITU-T G.7041.
Global Positioning A global navigation satellite system that provides reliable positioning, navigation, and
System (GPS) timing services to users worldwide.
Global System for The second-generation mobile networking standard defined by European
Mobile Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
Communications global mobile phone networks. The standard allows a subscriber to use a phone globally.
(GSM) GSM consists of three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway IP address The IP address of a gateway. A gateway is a node that forwards packets between
networks. Packets are sent to the gateway IP address when the destination network
address resides in a different network to the sender.
gateway network An NE that serves as a gateway for other NEs to communicate with a network
element (GNE) management system.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This is
(GTS) to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
granularity The extent to which a system is broken down into small parts, either the system itself or
its description or observation. It is the extent to which a larger entity is subdivided. If a
system has more granularity for you to choose, that is, there are more granules in the
system for you to choose, then you can customize the system more flexibly.

OptiX OSN 8800/6800/3800
HA system high availability system

HCS higher order connection supervision
HD-SDI high definition serial digital interface
HDB3 See high density bipolar of order 3 code.
HDLC High-Level Data Link Control
HDTV See high definition television.
HP higher order path
HPT higher order path termination
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
HSL See high-level script language.
HTML Hypertext Markup Language
HUAWEI Electronic The software used to view, search for, and upgrade electronic documentation of Huawei
Document Explorer products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and HedEx
(HedEx) Server.
HedEx See HUAWEI Electronic Document Explorer.
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement
Packet Access for asymmetric uplink and downlink transmission of data services. It enables the
(HSDPA) maximum downlink data service rate to reach 14.4 Mbit/s without changing the
WCDMA network topology.
high definition A type of TV that is capable of displaying at least 720 progressive or 1080 interlaced
television (HDTV) active scan lines. It must be capable of displaying a 16:9 image using at least 540
progressive or 810 interlaced active scan lines.
high density bipolar of A code used for baseband transmissions between telecommunications devices. The
order 3 code (HDB3) HDB3 code has the following feature: high capability of clock extraction, no direct
current component, error-checking capability, and a maximum of three consecutive
zeros.
high-level script A script language. Based on python, the HSL syntax is simple, clear, and extendable.
language (HSL)
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICMP See Internet Control Message Protocol.
ID See identity.
IEC International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
IF See intermediate frequency.

OptiX OSN 8800/6800/3800
IGMP See Internet Group Management Protocol.

IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IGRP Interior Gateway Routing Protocol
ILM incoming label map
IM See instant messaging.
IMA See inverse multiplexing over ATM.
IMP instant message platform
IP Internet Protocol
IP address A 32-bit (4-byte) binary number that uniquely identifies a host connected to the Internet.
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 identifies
the host itself.
IP subnet A special submap used to identify an IP network segment. It is displayed as the submap
icon in the topological view.
IPA See intelligent power adjustment.
IPTV See Internet Protocol television.
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISI intersymbol interference
ISL See Inter-Switch Link.
ISO International Organization for Standardization
IST internal spanning tree
ITU See International Telecommunication Union.
ITU-T International Telecommunication Union-Telecommunication Standardization Sector
IWF Interworking Function
Institute of Electrical A professional association of electrical and electronics engineers based in the United
and Electronics States, but with membership from numerous other countries. The IEEE focuses on
Engineers (IEEE) electrical, electronics, and computer engineering, and produces many important
technology standards.
Inter-Switch Link A kind of link that realizes VLAN by adding a 26-bit ISL header (with VLAN ID) to the
(ISL) traditional Ethernet packets.

OptiX OSN 8800/6800/3800
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward
Intermediate System datagram or packets through a packet-based network.
(IS-IS)
International A United Nations agency, one of the most important and influential recommendation
Telecommunication bodies, responsible for recommending standards for telecommunication (ITU-T) and
Union (ITU) radio networks (ITU-R).
Internet Assigned A department operated by the IAB. IANA delegates authority for IP address-space
Numbers Authority allocation and domain-name assignment to the NIC and other organizations. IANA also
(IANA) maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
Internet Control A network layer protocol that provides message control and error reporting between a
Message Protocol host server and an Internet gateway.
(ICMP)
Internet Group One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
Management Protocol groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
(IGMP) multicast group memberships.
Internet Protocol A system that provides TV services over the IP network. In the IPTV system, media
television (IPTV) streams from satellites, terrestrial, and studios are converted by the encoder to the media
streams applicable to the IP network. Then the media streams are transmitted to the
terminal layer on the IP network. Media content is displayed on a TV set after media
streams are processed by specified receiving devices (for example, an STB).
Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is
version 4 (IPv4) assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is
written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers together
are used for routing, and the host number is used to address an individual host within the
network or subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering Task Force
version 6 (IPv6) (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet
Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while
an IPv6 address has 128 bits.
identity (ID) The collective aspect of the set of characteristics by which a thing is definitively
recognizable or known.
input jitter tolerance The measure of a receiver's ability to tolerate jitter on an incoming waveform.
insertion loss The loss of power that results from inserting a component, such as a connector, coupler,
or splice, into a previously continuous path.
instant messaging (IM) A form of real-time communication between two or more people based on typed text.
The text is conveyed via devices connected over a network such as the Internet.
integrated circuit (IC) 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.
intelligent power A technology that reduces the optical power of all the amplifiers in an adjacent
adjustment (IPA) regeneration section in the upstream to a safe level if the system detects the loss of optical
signals on the link. IPA helps ensure that maintenance engineers are not injured by the
laser escaping from a broken fiber or a connector that is not plugged in properly.

OptiX OSN 8800/6800/3800
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF) signal.
inverse multiplexing A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a
over ATM (IMA) cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations, and
control system instability.
L
L2VPN Layer 2 virtual private network
L3VPN Layer 3 virtual private network
LACP See Link Aggregation Control Protocol.
LACPDU Link Aggregation Control Protocol data unit
LAG See link aggregation group.
LAN See local area network.
LAPS Link Access Protocol-SDH
LAS line assurance system
LB See loopback.
LBM See loopback message.
LBR See loopback reply.
LC Lucent connector
LCAS See link capacity adjustment scheme.
LCK See Locked signal function.
LCT local craft terminal
LDP Label Distribution Protocol
LER See label edge router.
LHP long hop
LLC See logical link control.
LLID local loopback ID
LM See loss measurement.
LMP link management protocol
LOP loss of pointer
LOS See loss of signal.
LPT link-state pass through
LRF location registration function

OptiX OSN 8800/6800/3800
LSA link-state advertisement

LSP See label switched path.
LSR See label switching router.
LSS loss of sequence synchronization
LT linktrace
LTC loss of tandem connection
LTE Long Term Evolution
LTM See linktrace message.
LTR See linktrace reply.
Layer 2 multicast A technology that maps IP multicast addresses to multicast MAC addresses. When
Ethernet is used as the link layer, Layer 2 multicast uses multicast MAC addresses for
traffic transmission.
Link Aggregation A dynamic link aggregation protocol that improves the transmission speed and
Control Protocol reliability. The two ends of the link send LACP packets to inform each other of their
(LACP) parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
Locked signal function A function administratively locks an MEG end point (MEP) at the server layer, informs
(LCK) consequential data traffic interruption to the peer MEP at the client layer, and suppresses
the alarm at the client layer.
label edge router (LER) A device that sits at the edge of an MPLS domain, that uses routing information to assign
labels to datagrams and then forwards them into the MPLS domain.
label switched path On an MPLS network, an LSR uses the same label switching mechanism to forward
(LSP) packets with the same features. The packets with the same features are called a
forwarding equivalence class (FEC). The path along which an FEC travels through the
MPLS network is called an LSP, or a tunnel.
label switching router Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is
(LSR) composed of two parts: control unit and forwarding unit. The former is responsible for
allocating the label, selecting the route, creating the label forwarding table, creating and
removing the label switch path; the latter forwards the labels according to groups
received in the label forwarding table.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
(LAG) aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitless increase or decrease the capacity of a link to meet the
(LCAS) 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 status The running status of a link, which can be Up, Down, backup, or unknown.

OptiX OSN 8800/6800/3800
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.
(LTM) LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.
linktrace reply (LTR) 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 LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus
1.
local area network A network formed by the computers and workstations within the coverage of a few square
(LAN) kilometers or within a single building, featuring high speed and low error rate. Current
LANs are generally based on switched Ethernet or Wi-Fi technology and run at 1,000
Mbit/s (that is, 1 Gbit/s).
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
(LLC) sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the destination
(LBM) node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the LBM.
The LBR carries the sending time of LBM, the receiving time of LBM and the sending
time of LBR.
loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames
where the counters maintain a count of transmitted and received data frames between a
pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM multiple add/drop multiplexer
MAN See metropolitan area network.
MBB mobile broadband
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDF See main distribution frame.
ME See maintenance entity.
MEG See maintenance entity group.

OptiX OSN 8800/6800/3800
MEP maintenance association end point

MFAS See multiframe alignment signal.
MGC media gateway controller
MIB See management information base.
MID message identification
MIN mobile identification number
MIP See maintenance entity group intermediate point.
MLD See multicast listener discovery.
MML man-machine language
MNO See mobile network operator.
MOP See method of procedure.
MP maintenance point
MPI-R main path interface at the receiver
MPI-S main path interface at the transmitter
MPID maintenance point identification
MPLS See Multiprotocol Label Switching.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MPLS-TP See MultiProtocol Label Switching Transport Profile.
MRI See measurement result integrity.
MRO mobility robustness optimization
MS multiplex section
MS-AIS See multiplex section alarm indication signal.
MS-PW See multi-segment pseudo wire.
MSA multiplex section adaptation
MSDP See Multicast Source Discovery Protocol.
MSI mobile station identifier
MSOH multiplex section overhead
MSP See multiplex section protection.
MST See multiplex section termination.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTU See maximum transmission unit.

OptiX OSN 8800/6800/3800
MUX See multiplexer.

MVOA mechanical variable optical attenuator
MWA mobile wireless access
Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of the
(MAC) data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
MultiProtocol Label A packet transport technology proposed by IETF that combines the packet experience
Switching Transport of MPLS with the operational experience of transport networks.
Profile (MPLS-TP)
Multicast Source A protocol that is applicable only to the PIM-SM domain and meaningful only for the
Discovery Protocol Any-Source Multicast (ASM) model. After the MSDP peer relationship is set up between
(MSDP) RPs of different PIM-SM domains, multicast source information can be shared between
PIM-SM domains, and the inter-domain multicast can be implemented. After the MSDP
peer relationship is set up between RPs of the same PIM-SM domain, multicast source
information can be shared in the PIM-SM domain, and anycast RP can be implemented.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) redundant paths so that the loop network can be trimmed as a tree network. In this case,
the proliferation and endless cycling of packets is avoided in the loop network. The
protocol that introduces the mapping between VLANs and multiple spanning trees. This
solves the problem that data cannot be normally forwarded in a VLAN because in STP/
RSTP, only one spanning tree corresponds to all the VLANs.
Multiple Spanning A region that consists of switches that support the MSTP in the LAN and links among
Tree region (MST them. Switches physically and directly connected and configured with the same MST
region) region attributes belong to the same MST region.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching (MPLS) layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols.
main distribution A device at a central office, on which all local loops are terminated.
frame (MDF)
maintenance domain The network or the part of the network for which connectivity is managed by connectivity
(MD) fault management (CFM). The devices in a maintenance domain are managed by a single
Internet service provider (ISP).
maintenance entity An ME consists of a pair of maintenance entity group end points (MEPs), two ends of a
(ME) transport trail, and maintenance association intermediate points (MIPs) on the trail.

OptiX OSN 8800/6800/3800
maintenance entity A MEG consists of MEs that meet the following criteria:
group (MEG)
l Exist within the same management edges.
l Have the same MEG hierarchy.
l Belong to the same P2P or P2MP connection.
maintenance entity An intermediate point in a MEG, which is able to forward OAM packets and respond to
group intermediate some OAM packets, but unable to initiate the transmission of OAM packets or perform
point (MIP) any operations on network connections.
management A type of database used for managing the devices in a communications network. It
information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies,
unit (MTU) depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between The average time between consecutive failures of a piece of equipment. It is a measure
failures (MTBF) of the reliability of the system.
measurement result Percentage of the number of the actually reported measurement results to the number of
integrity (MRI) the measurement results that should be reported.
message digest A hash function that is used in a variety of security applications to check message
algorithm 5 (MD5) integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
method of procedure A document that describes the process of executing a specific task. It facilitates the
(MOP) mutual understanding of and cooperation between a service provider and a carrier. Before
executing a task, the representatives from both parties confirm this document and reach
an agreement on it. This document describes who, when, where, why, and how to execute
a task and what to do.
metropolitan area A medium-scale computer network with area larger than that covered by a LAN and
network (MAN) smaller than that covered by a WAN. It interconnects multiple LAN networks in a
geographic region of a city.
mobile network A company that has a network infrastructure, sells large network capacities, and provides
operator (MNO) transparent network channels.
multi-segment pseudo A collection of multiple adjacent PW segments. Each PW segment is a point-to-point
wire (MS-PW) PW. The use of MS-PWs to bear services saves tunnel resources and can transport
services over different networks.
multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicast
group rather than a host.

OptiX OSN 8800/6800/3800
multicast listener A protocol used by an IPv6 router to discover the multicast listeners on their directly
discovery (MLD) connected network segments, and to 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 A distinctive signal inserted into every multiframe or once into every n multiframes,
signal (MFAS) always occupying the same relative position within the multiframe, and used to establish
and maintain multiframe alignment.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
instance (MSTI) and fully connected active topology for frames classified as belonging to a VLAN that
is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to
multiple MSTIs.
multiplex section alarm An all-ONES characteristic or adapted information signal. It's generated to replace the
indication signal (MS- normal traffic signal when it signal contains a defect condition in order to prevent
AIS) consequential downstream failures being declared or alarms being raised. AIS can be
identified as multiplex section alarm indication signal.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection (MSP) including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section A function that generates the multiplex section overhead (MSOH) during the formation
termination (MST) of an SDH frame signal and that terminates the MSOH in the reverse direction.
multiplexer (MUX) Equipment that 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 An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching virtual switching (MPLS) technology. It applies the MPLS technology for network routers and
private network switches, simplifies the routing mode of core routers, and combines traditional routing
(MPLS VPN) technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
NAS network access server
NBI See northbound interface.
NDF new data flag
NE network element
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.

OptiX OSN 8800/6800/3800
NE Panel A graphical user interface, of the network management system, which displays subracks,
boards, and ports on an NE. On the NE Panel, the user can complete most of the
configuration, management and maintenance functions for an NE.
NHLFE next hop label forwarding entry
NM network management
NMC network management center
NNI network-to-network interface
NOC network operations center
NOS network operating system
NP See network processor.
NPE network provider edge
NRZ non-return to zero
NRZ code non-return-to-zero code
NS network system
NSAP See network service access point.
NTP Network Time Protocol
network layer Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the TCP/
IP protocol suite, the functions of the network layer are specified and implemented by
IP protocols. Therefore, the network layer is also called IP layer.
network processor (NP) An integrated circuit which has a feature set specifically targeted at the networking
application domain. Network Processors are typically software programmable devices
and would have generic characteristics similar to general purpose CPUs that are
commonly used in many different types of equipment and products.
network segment Part of a network on which all message traffic is common to all nodes; that is, a message
broadcast from one node on the segment is received by all other nodes on the segment.
network service access A network address defined by ISO, at which the OSI Network Service is made available
point (NSAP) to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by network
connection or configuration problems.
noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components in
a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the output
noise power of a device to the portion thereof attributable to thermal noise in the input
termination at standard noise temperature T0 (usually 290 K). The noise figure is thus
the ratio of actual output noise to that which would remain if the device itself did not
introduce noise. It is a number by which the performance of a radio receiver can be
specified.
non-GNE See non-gateway network element.

OptiX OSN 8800/6800/3800
non-gateway network A network element that communicates with the NM application layer through the
element (non-GNE) gateway NE application layer.
northbound interface An interface that connects to the upper-layer device to provision services and report
(NBI) alarms and performance statistics.
O
O&M operation and maintenance
OA optical amplifier
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAMS Optical fiber line Automatic Monitoring System
OC ordinary clock
OCI open connection indication
OCP optical channel protection
OCS optical core switching
OCh optical channel with full functionality
OD optical demultiplexing
ODB optical duobinary
ODF optical distribution frame
ODUk optical channel data unit - k
OEQ optical equalizer
OFC optical fiber communication conference and exhibit
OIF See Optical Internetworking Forum.
OLP See optical line protection.
OM optical multiplexing
OMS optical multiplexing section
OMU optical multiplexer unit
ONE See optical network element.
ONT See optical network terminal.
ONU See optical network unit.
OOS out of service
OPEX operating expense
OPS optical physical section
OPU See optical channel payload unit.
OPUk optical channel payload unit - k

OptiX OSN 8800/6800/3800
ORT See operation response time.

OSA See optical spectrum analyzer.
OSC See optical supervisory channel.
OSI reference model See Open Systems Interconnection reference model.
OSN optical switch node
OSNR See optical signal-to-noise ratio.
OSPF See Open Shortest Path First.
OSS operations support system
OTDR See optical time domain reflectometer.
OTM optical terminal multiplexer
OTN optical transport network
OTS See optical transmission section.
OTU See optical transponder unit.
OTUk optical channel transport unit - k
OUI organizationally unique identifier
OWSP optical wavelength shared protection
Open Shortest Path A link-state, hierarchical interior gateway protocol (IGP) for network routing that uses
First (OSPF) 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 An open network architecture model developed by the International Organization for
Interconnection Standardization (ISO) and the ITU-T. This module consists of 7 layers. Each layer has
reference model (OSI special network functions, such as addressing, flow control, error control, encapsulation,
reference model) and reliable message transmission. The lowest layer (physical layer) is closest to media
technologies. The lower two layers are implemented in hardware and software, and the
upper five layers are implemented only in software. The highest layer (application layer)
is closest to users. The OSI reference model is a widely used method of understanding
network functions.
Optical A worldwide non-profit organization with membership open to any organization
Internetworking interested in shaping the future of optical internetworking.
Forum (OIF)
operation response The average time taken by a storage device to respond to each request. It is a critical
time (ORT) storage performance indicator.
operation, A set of network management functions that cover fault detection, notification, location,
administration and and repair.
maintenance (OAM)
optical add/drop A device that can be used to add the optical signals of various wavelengths to one channel
multiplexer (OADM) and drop the optical signals of various wavelengths from one channel.
optical attenuator A passive device that increases the attenuation in a fiber link. An optical attenuator is
used to ensure that the optical power of a signal at the receive end is not excessively
high.

OptiX OSN 8800/6800/3800
optical channel payload A protection architecture that allows one wavelength to provide protection for multiple
unit (OPU) services between different stations, saving wavelength resources and lowering costs.
optical line protection Optical line protection is implemented using the dual feeding and selective receiving
(OLP) function. Two pairs of fibers (that is, four fibers) are used. One pair of fibers function as
the working trail and is used to transmit service signals of a line when the line is normal.
The other pair of fibers function as the protection trail and is used to carry protection
switching signals when a fiber cut occurs or the signal attenuation is excessively large.
optical network A transport entity that implements the NE functions (terminal multiplexing, add/drop
element (ONE) multiplexing, cross-connection and regeneration) in a DWDM layer network. The types
of ONEs include OTM, OADM, OLA, REG and OXC.
optical network A device that terminates the fiber optical network at the customer premises.
terminal (ONT)
optical network unit A form of Access Node that converts optical signals transmitted via fiber to electrical
(ONU) signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise The ratio of signal power to noise power in a transmission link. OSNR is the most
ratio (OSNR) important index for measuring the performance of a DWDM system.
optical spectrum A device that can analyze a region of the optical spectrum and is commonly used to
analyzer (OSA) diagnose DWDM systems.
optical supervisory A technology that uses specific optical wavelengths to realize communication among
channel (OSC) nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical time domain A device that sends a series of short pulses of light down a fiber-optic cable and measures
reflectometer (OTDR) the strength of the return pulses. An OTDR is used to measure fiber length and light loss,
and to locate fiber faults.
optical transmission A section in the logical structure of an optical transport network (OTN). The OTS allows
section (OTS) the network operator to perform monitoring and maintenance tasks between NEs.
optical transponder A device or subsystem that converts accessed client signals into a G.694.1/G.694.2-
unit (OTU) compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PBS See peak burst size.
PCB See printed circuit board.
PCC protection communication channel
PCN product change notice
PCS physical coding sublayer
PDG polarization-dependent gain

OptiX OSN 8800/6800/3800
PDH See plesiochronous digital hierarchy.

PDL See polarization-dependent loss.
PDM pulse duration modulation
PDU See power distribution unit.
PE See provider edge.
PER packet error rate
PET polyester
PFI packet forward interface
PGA program global area
PHB See per-hop behavior.
PID photonics integrated device
PIM-DM Protocol Independent Multicast - Dense Mode
PIM-SM Protocol Independent Multicast - Sparse Mode
PIR peak information rate
PLC See packet loss compensation.
PLL See phase-locked loop.
PM performance monitoring
PMD polarization mode dispersion
PMI payload missing indication
PMS Product Management System
PMU power monitoring unit
POH path overhead
PON passive optical network
POS See packet over SDH/SONET.
POTS See plain old telephone service.
PPP Point-to-Point Protocol
PPPoE Point-to-Point Protocol over Ethernet
PPS pulse per second
PPT PDH physical terminal
PRBS See pseudo random binary sequence.
PRC primary reference clock
PSI payload structure identifier
PSN See packet switched network.
PSTN See public switched telephone network.
PT payload type

OptiX OSN 8800/6800/3800
PTI payload type indicator

PTN packet transport network
PTP Precision Time Protocol
PTP clock See Precision Time Protocol clock.
PVC permanent virtual channel
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
Precision Time A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588
Protocol clock (PTP V2 standard specifies the precision time protocol (PTP) in a measurement and control
clock) system. The PTP protocol ensures clock synchronization precise to sub-microseconds.
packet loss A technology of compensating packets according to an appropriate algorithm if packets
compensation (PLC) are lost in the transmission.
packet over SDH/ A MAN and WAN technology that provides point-to-point data connections. The POS
SONET (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 A telecommunications network that works in packet switching mode.
network (PSN)
packing case A case used for packing a board or subrack.
paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
parity check A method for character level error detection. An extra bit is added to a string of bits,
usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or
even parity). Both ends of a data transmission must use the same parity. When the
transmitting device frames a character, it counts the numbers of 1s in the frame and
attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error,
may ask for the data to be retransmitted.
patch loading During patch loading, the software is written into the Flash boards and the patch area of
the board memory from the specified storage area of the OMU board or the BAM of NEs
through commands.
peak burst size (PBS) A parameter that defines the capacity of token bucket P, that is, the maximum burst IP
packet size when the information is transferred at the peak information rate.
per-hop behavior IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop
(PHB) behaviors (PHB), such as, traffic scheduling and policing. A device in the network should
select the proper PHB behaviors, based on the value of DSCP. At present, the IETF
defines four types of PHB. They are class selector (CS), expedited forwarding (EF),
assured forwarding (AF), and best-effort (BE).
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
permanent virtual path Virtual path that consists of PVCs.
(PVP)

OptiX OSN 8800/6800/3800
phase-locked loop A circuit that consists essentially of a phase detector that compares the frequency of a
(PLL) voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator. The output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
ping A method used to test whether a device in the IP network is reachable according to the
sent ICMP Echo messages and received response messages.
plain old telephone The basic telephone service provided through the traditional cabling such as twisted pair
service (POTS) cables.
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
hierarchy (PDH) rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
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 this pointer is supported.
polarization-dependent A measure of the peak-to-peak insertion loss or gain variation caused by a component
loss (PDL) when stimulated by all possible polarization states. PDL is specified in dB.
power distribution unit A unit that performs AC or DC power distribution.
(PDU)
printed circuit board A board used to mechanically support and electrically connect electronic components
(PCB) using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
private line A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
protection path A path in a protection group that transports services when a fault occurs on the working
path.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
pseudo random binary A sequence that is random in the sense that the value of each element is independent of
sequence (PRBS) the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a
edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network
(PSN). PWE3 also emulates the essential attributes of low speed time division
multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real
situation.
public switched A telecommunications network established to perform telephone services for the public
telephone network subscribers. Sometimes it is called POTS.
(PSTN)

OptiX OSN 8800/6800/3800
Q
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
QoS See quality of service.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth period
or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are
evenly distributed on a circle. On these phases, each QPSK character can perform two-
bit coding and display the codes in Gray code on graph with the minimum BER.
quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial In User Service.
RAN See radio access network.
RBW reverse-band working
RDI remote defect indication
RED See random early detection.
REG See regenerator.
RF See radio frequency.
RFC See Request For Comments.
RIP See Routing Information Protocol.
RJ45 registered jack45
RMEP remote maintenance association end point
RMON remote network monitoring
RMS resource management system
RMU rack monitoring unit
RNC See radio network controller.
ROADM reconfigurable optical add/drop multiplexer
ROPA See remote optical pumping amplifier.
RPR resilient packet ring
RS regenerator section
RS232 See Recommended Standard 232.

OptiX OSN 8800/6800/3800
RS422 The specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSOH regenerator section overhead
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RSVP-TE See Resource Reservation Protocol-Traffic Engineering.
RTP real-time performance
RX receive
RXD receive data
RZ return to zero
RZ code return-to-zero code
Rapid Spanning Tree An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
Protocol (RSTP) convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Recommended A standard that defines the electrical characteristics, timing, and meaning of signals, and
Standard 232 (RS232) the physical size and pinout of connectors.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial In User Service access control mechanism. RADIUS uses the User Datagram Protocol (UDP) as its
(RADIUS) transmission protocol to ensure real-time quality. RADIUS also supports the
retransmission and multi-server mechanisms to ensure good reliability.
Request For Comments A document in which a standard, a protocol, or other information pertaining to the
(RFC) operation of the Internet is published. The RFC is actually issued, under the control of
the IAB, after discussion and serves as the standard. RFCs can be obtained from sources
such as InterNIC.
Resource Reservation A protocol that reserves resources on every node along a path. RSVP is designed for an
Protocol (RSVP) integrated services Internet.
Resource Reservation An extension to the RSVP protocol for setting up label switched paths (LSPs) in MPLS
Protocol-Traffic networks. The RSVP-TE protocol is used to establish and maintain the LSPs by initiating
Engineering (RSVP- label requests and allocating label binding messages. It also supports LSP rerouting and
TE) LSP bandwidth increasing.
RoHS restriction of the use of certain hazardous substances
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
Protocol (RIP) based on the smallest hop count between the source and destination. RIP is a distance
vector protocol that routinely broadcasts routing information to its neighboring routers
and is known to waste bandwidth.
radio access network The network that provides the connection between CPEs and the CN. It isolates the CN
(RAN) from wireless network.

OptiX OSN 8800/6800/3800
radio frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.
The AC with the frequency lower than 1 kHz is called low-frequency current. The AC
with frequency higher than 10 kHz is called high-frequency current. RF can be classified
into such high-frequency current.
radio network A device in a radio network subsystem that is in charge of controlling the usage and
controller (RNC) integrity of radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according
(RED) to the specified higher limit and lower limit of a queue so that global TCP synchronization
resulting from traditional tail drop can be prevented.
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference point
at an input to a receiver optical connector) to achieve a 1x10-12 BER when the FEC is
enabled.
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A stable and high-precision autonomous clock that provides frequencies as a reference
for other clocks.
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.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
regional root The root of the Internal Spanning Tree (IST) and Multiple Spanning Tree Instance
(MSTI) in the MST region. The regional root differs with the topology of the spanning
tree in the MST region.
remote optical A remote optical amplifier subsystem designed for applications where power supply and
pumping amplifier monitoring systems are unavailable. The ROPA subsystem is a power compensation
(ROPA) solution to the ultra-long distance long hop (LHP) transmission.
reservation An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action ensures
that the subscriber has sufficient balance to pay for services.
ring network A network topology in which each node connects to exactly two other nodes, forming a
circular pathway for signals.
route The path that network traffic takes from its source to its destination. Routes can change
dynamically.
router A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
routing table A table that stores and updates the locations (addresses) of network devices. Routers
regularly share routing table information to be up to date. A router relies on the
destination address and on the information in the table that gives the possible routes--in
hops or in number of jumps--between itself, intervening routers, and the destination.
Routing tables are updated frequently as new information is available.

OptiX OSN 8800/6800/3800
S-VLAN service virtual local area network

S1 byte A byte to transmit network synchronization status information. On an SDH network,
each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an 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.
SAI service area identifier
SAN See storage area network.
SAPI service access point identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SBS synchronous information backbone system
SCA selective call acceptance
SCE See service creation environment.
SD See signal degrade.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDI See serial digital interface.
SDP See Session Description Protocol.
SELV safety extra-low voltage
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SFTP See Secure File Transfer Protocol.
SHDSL See single-pair high-speed digital subscriber line.
SLA See service level agreement.
SLIP See Serial Line Interface Protocol.
SLM single longitudinal mode
SM section monitoring
SMB Server Message Block
SMF See single-mode fiber.
SNC subnetwork connection

OptiX OSN 8800/6800/3800
SNCP subnetwork connection protection

SNCTP subnetwork connection tunnel protection
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SO See security object.
SOH section overhead
SONET See synchronous optical network.
SPI SDH physical interface
SPM service processing module
SQL See structured query language.
SRG See shared risk group.
SRLG shared risk link group
SRP satellite reference point
SRS stimulated Raman scattering
SSD See service support data.
SSH See Secure Shell.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
STG synchronous timing generator
STM See synchronous transport module.
STP Spanning Tree Protocol
STS space time spreading
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol (SFTP)
Secure Shell (SSH) A set of standards and an associated network protocol that allows establishing a secure
channel between a local and a remote computer. A feature to protect information and
provide powerful authentication function for a network when a user logs in to the network
through an insecure network. It prevents IP addresses from being deceived and simple
passwords from being captured.
Secure Sockets Layer A security protocol that works at a socket level. This layer exists between the TCP layer
(SSL) and the application layer to encrypt/decode data and authenticate concerned entities.
Serial Line Interface A protocol that defines the framing mode over the serial line to implement transmission
Protocol (SLIP) of messages over the serial line and provide the remote host interconnection function
with a known IP address.
Session Description A protocol intended for describing multimedia sessions for the purposes of session
Protocol (SDP) announcement, session invitation, and other forms of multimedia session initiation.

OptiX OSN 8800/6800/3800
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
(SNMP) transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing link.
Message (SSM) SSM messages provide upstream clock information to nodes on an SDH network or
synchronization network.
security object (SO) A main part of the information security. It is not related with the communication mode
or terminal. It does not only focus on the security of the information exchange but also
provides feasible solutions of security for the user information, including the user identity
authentication, user password, and encryption.
segment A subset of an identity type. This is a different subset from a trust level including but is
not limited to the following examples: A subset based on customer age, a subset based
on where the identity was registered or based, a subset based on the customer's gender,
and a subset based on an association that the identity may have. For example, an
organization is confirmed as a supermarket or a customer is a member of a society.
serial digital interface An interface that transmits data in a single channel in sequence.
(SDI)
service creation A service generation tool that provides a graphical user interface (GUI) for programming.
environment (SCE)
service level agreement A service agreement between a customer and a service provider. SLA specifies the
(SLA) service level for a customer. The customer can be a user organization (source domain)
or another differentiated services domain (upstream domain). An SLA may include
traffic conditioning rules which constitute a traffic conditioning agreement as a whole
or partially.
service support data An identifier that defines data parameters of specific service feature descriptions in the
(SSD) global functional plane.
shaping A process of delaying packets within a traffic stream to cause it to conform to specific
defined traffic profile.
shared risk group A group of resources that share a common risk component whose failure can cause the
(SRG) failure of all the resources in the group.
signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defect
condition is active.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.

OptiX OSN 8800/6800/3800
single-mode fiber A type of optical fiber through which only one type of optical signal with a fixed wave
(SMF) length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber can transmit data over a long distance.
single-pair high-speed A symmetric digital subscriber line technology developed from HDSL, SDSL, and
digital subscriber line HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
(SHDSL) terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
split ratio The ratio of the number one to the number of optical signal channels that are split from
a channel of downstream optical signals in a GPON network. A larger split ratio implies
greater optical splitting which creates the need for an increased power budget to support
the physical reach.
standard definition- Standard definition video signal transported by serial digital interface.
serial digital interface
signal (SD-SDI)
storage area network An architecture to attach remote computer storage devices such as disk array controllers,
(SAN) tape libraries and CD arrays to servers in such a way that to the operating system the
devices appear as locally attached devices.
structured query A programming language widely used for accessing, updating, managing, and querying
language (SQL) data in a relational database.
subnet An abbreviation for subnetwork. A type of smaller networks that form a larger network
according to a rule, for example, according to different districts. This facilitates the
management of the large network.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the device and is matched
with the IP address.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
hierarchy (SDH) transmission features of digital signals, such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN.
synchronous optical A high-speed network that provides a standard interface for communications carriers to
network (SONET) connect networks based on fiber optical cable. SONET is designed to handle multiple
data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but
multiples of this base rate go as high as 2.488 Gbit/s.
synchronous transport An information structure used to support section layer connections in the SDH. It consists
module (STM) of information payload and Section Overhead (SOH) information fields organized in a
block frame structure which repeats every 125. The information is suitably conditioned
for serial transmission on the selected media at a rate which is synchronized to the
network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher
capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities
for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
T
T1 A North American standard for high-speed data transmission at 1.544Mbps. It provides
24 x 64 kbit/s channels.

OptiX OSN 8800/6800/3800
TCM tandem connection monitor

TCN topology change notification
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDD time division duplex
TDM See time division multiplexing.
TE terminal equipment
TFTP See Trivial File Transfer Protocol.
TIM trail trace identifier mismatch
TLS Transport Layer Security
TLV See type-length-value.
TM See terminal multiplexer.
TMN See telecommunications management network.
TOS type of service
TPID tag protocol identifier
TR token ring
TST See Test.
TTI trail trace identifier
TTL See time to live.
TUG tributary unit group
TX transmit
Telnet A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users
to log in to remote systems and use resources as if they were connected to a local system.
Telnet is defined in RFC 854.
Test (TST) A function which is used to perform one-way on-demand in-service or out-of-service
diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit errors,
and so on.
Time Division- A 3G mobile communications standard found in UMTS mobile telecommunications
Synchronous Code networks in China as an alternative to W-CDMA. TD-SCDMA integrates technologies
Division Multiple of CDMA, TDMA, and FDMA, and makes use of technologies including intelligent
Access (TD-SCDMA) antenna, joint detection, low chip rate (LCR), and adaptive power control. With the
flexibility of service processing, a TD-SCDMA network can connect to other networks
through the RNC.
Transmission Control The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol (TCP) be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.

OptiX OSN 8800/6800/3800
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol (TFTP) applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication.
telecommunications A protocol model defined by ITU-T for managing open systems in a communications
management network network. TMN manages the planning, provisioning, installation, and OAM of
(TMN) equipment, networks, and services.
terminal multiplexer A device used at a network terminal either to multiplex multiple channels of low rate
(TM) signals into one channel of high rate signals, or to demultiplex one channel of high rate
signals into multiple channels of low rate signals.
time division A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
multiplexing (TDM) (TSn, n=0, 1, 2, 3), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
time to live (TTL) A specified period of time for best-effort delivery systems to prevent packets from
looping endlessly.
token bucket algorithm The token bucket is a container for tokens. The capacity of a token bucket is limited, and
the number of tokens determines the traffic rate of permitted packets. The token bucket
polices the traffic. Users place the tokens into the bucket regularly according to the preset
rate. If the tokens in the bucket exceed the capacity, no tokens can be put in. Packets can
be forwarded when the bucket has tokens, otherwise they cannot be transferred till there
are new tokens in the bucket. This scheme adjusts the rate of packet input.
trTCM See two rate three color marker.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the entire
network. In this way, different traffic packets can be treated differently.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee the
performance and minimize the delay. It actively adjusts the output speed of traffic in the
scenario that the traffic matches network resources provided by the lower layer devices,
avoiding packet loss and congestion.
traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks. The
statistics also help the operators manage the device operating, locate problems, monitor
and maintain the networks, and plan the networks.
transparent mode A method of binary synchronous text transmission in which only transmission control
characters preceded by the data link escape (DLE) character are processed as
transmission control characters.
transparent A process during which the signaling protocol or data is not processed in the content but
transmission encapsulated in the format for the processing of the next phase.
trunk Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.

OptiX OSN 8800/6800/3800
two rate three color An algorithm that meters an IP packet stream and marks its packets based on two rates,
marker (trTCM) Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it
exceeds or does not exceed the CIR.
type-length-value An encoding type that features high efficiency and expansibility. It is also called Code-
(TLV) Length-Value (CLV). T indicates that different types can be defined through different
values. L indicates the total length of the value field. V indicates the actual data of the
TLV and is most important. TLV encoding features high expansibility. New TLVs can
be added to support new features, which is flexible in describing information loaded in
packets.
U
UDP See User Datagram Protocol.
UI user interface
UNI See user-to-network interface.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
UTC Coordinated Universal Time
User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol (UDP) datagram to an application program on another. UDP uses IP to deliver datagrams. UDP
provides application programs with the unreliable connectionless packet delivery
service. That is, UDP messages may be lost, duplicated, delayed, or delivered out of
order. The destination device does not actively confirm whether the correct data packet
is received.
upstream In an access network, the direction that is far from the subscriber end of the link.
upstream board A board that provides the upstream transmission function. Through an upstream board,
services can be transmitted upstream to the upper-layer device.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-NNI virtual network-network interface
V-UNI See virtual user-network interface.
VA value assurance
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC See virtual channel.

OptiX OSN 8800/6800/3800
VC trunk See virtual container trunk.

VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCPLM virtual concatenation payload mismatch
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VDSL2 See very-high-speed digital subscriber line 2.
VLAN virtual local area network
VLAN mapping A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at the
destination private network, VLAN mapping translates public VLAN tags back into
private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VM virtual memory
VOA variable optical attenuator
VPLS See virtual private LAN service.
VPN virtual private network
VPWS See virtual private wire service.
VRRP See Virtual Router Redundancy Protocol.
VSI See virtual switching instance.
Virtual Router A protocol designed for multicast or broadcast LANs such as an Ethernet. A group of
Redundancy Protocol routers (including an active router and several backup routers) in a LAN is regarded as
(VRRP) a virtual router, which is called a backup group. The virtual router has its own IP address.
The host in the network communicates with other networks through this virtual router.
If the active router in the backup group fails, one of the backup routers in this backup
group becomes active and provides routing service for the host in the network.
VoD See video on demand.
VoIP See Voice over Internet Protocol.
Voice over Internet A value-added service technology for IP calls. The VoIP service is a new IP telecom
Protocol (VoIP) service. It can run on fixed and mobile networks and support flexible access points. Fees
for VoIP subscribers are relatively low. Calls between VoIP subscribers who belong to
the same carrier are free of charge.
value-added service A service provided by carriers and service providers (SPs) together for subscribers based
(VAS) on voice, data, images, SMS messages, and so on. Communication network technologies,
computer technologies, and Internet technologies are used to provide value-added
services.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.

OptiX OSN 8800/6800/3800
very-high-speed digital An extension of the VDSL technology, which complies with ITU G.993.2, supports
subscriber line 2 multiple spectrum profiles and encapsulation modes, and provides short-distance and
(VDSL2) high-speed access solutions to the next-generation FTTx access service.
video on demand (VoD) An interactive video service system through which you can demand desired programs
at any time.
virtual channel (VC) Any logical connection in the ATM network. A VC is the basic unit of switching in the
ATM network and is uniquely identified by a virtual path identifier (VPI)/virtual channel
identifier (VCI) value. It is the channel on which ATM cells are transmitted by a switch.
virtual channel A VC logical trail that carries data between two end points in an ATM network. A point-
connection (VCC) to-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit A channel or circuit established between two points on a data communications network
with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or
switched virtual circuits (SVCs) .
virtual concatenation A group of co-located member trail termination functions that are connected to the same
group (VCG) virtual concatenation link.
virtual connection A logical tunnel built in a non-backbone area between two ABRs in a same OSPF routing
domain. It is used to maintain the logical connections between physical division areas.
The two ends of the virtual connection must be ABRs. In addition, to make a virtual
connection effective, the ABRs must be configured at the same time. The virtual
connection is identified by the ID of the peer router.
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
virtual private LAN A type of point-to-multipoint L2VPN service provided over the public network. VPLS
service (VPLS) enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
virtual private wire A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,
service (VPWS) Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.
virtual switching An instance through which the physical access links of VPLS can be mapped to the
instance (VSI) virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge
function and can terminate PW.
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
W
WAN wide area network
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRED See weighted random early detection.
WRR weighted round robin

OptiX OSN 8800/6800/3800
WSS wavelength selective switching

WTR See wait to restore.
WXCP See wavelength cross-connection protection.
Web LCT The local maintenance terminal of a transport network, which is located at the NE
management layer of the transport network.
Wideband Code A standard defined by the ITU-T for the third-generation wireless technology derived
Division Multiple from the Code Division Multiple Access (CDMA) technology.
Access (WCDMA)
wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.
wavelength cross- A type of channel protection based on ring network topology. WXCP employs the dual
connection protection feed and selective receiving principle and uses the cross-connection function to
(WXCP) implement service switching between the working and protection channels.
weighted fair queuing A fair queue scheduling algorithm based on bandwidth allocation weights. This
(WFQ) scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP
detection (WRED) synchronization caused by traditional tail-drop. WRED is favorable for the high-priority
packet when calculating the packet loss ratio.
wireless local area A hybrid of the computer network and the wireless communication technology. It uses
network (WLAN) wireless multiple address channels as transmission media and carriers out data interaction
through electromagnetic wave to implement the functions of the traditional LAN.
X
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
xDSL x digital subscriber line


OSN 8800 6800 3800 V100R007C00 Alarms and Performance Events Reference 06

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

OSN 8800 6800 3800 V100R007C00 Alarms and Performance Events Reference 06

Transféré par

Droits d'auteur :

Formats disponibles

OptiX OSN 8800/6800/3800

Alarms and Performance Events

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX OSN 8800 V100R007C00

OptiX OSN 6800 V100R007C00

OptiX OSN 3800 V100R007C00

iManager U2000 V100R006C02

iManager U2000 Web LCT V100R006C02

l System maintenance engineer

Indicates a hazard with a high level of risk, which if not

Issue 06 (2015-07-20) Huawei Proprietary and Confidential ii

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Updates in Issue 06 (2015-07-20) Based on Product Version

Issue 06 (2015-07-20) Huawei Proprietary and Confidential iii

Updates in Issue 05 (2013-11-30) Based on Product Version

Updates in Issue 04 (2013-08-19) Based on Product Version

4 Clearing l 3.7.2 COMMUN_FAIL (OTN) is modified.

Updates in Issue 03 (2012-12-15) Based on Product Version

2 Alarm List l 2.2.92 SCC Board Alarm List is modified.

4 Clearing l 4.326 SUBRACK_TYPE_MISMATCH is modified.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential iv

Updates in Issue 02 (2012-09-30) Based on Product Version

Updates in Issue 01 (2012-07-30) Based on Product Version

2 Alarm List l 2.2.27 EX2 Board Alarm List is added.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential v

4 Clearing l 4.17 ASE_NOT_CALIBRATE is added.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential vi

l 4.169 MPLS_TUNNEL_OAMFAIL is added.

5 Performance l 5.2.13 EX2 Board Performance Event List is added.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential vii

6 Handling l 6.5 BDTEMP is added.

Updates in Issue 04 (2012-10-30) Based on Product Version

2 Alarm List l 2.2.53 LSXL Board Alarm List is modified.

3 Clearing l 3.37 POWER_FAIL is modified.

4 Clearing l 4.5 ALS_TRIGGERED is modified.

5 Performance l 5.2.36 LSXL Board Performance Event List is modified.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential viii

Updates in Issue 03 (2012-06-22) Based on Product Version

2 Alarm List l 2.2.10 CRPC Board Alarm List is modified.

4 Clearing l 4.5 ALS_TRIGGERED is added.

5 Performance l 5.2.14 FIU Board Performance Event List is modified.

6 Handling l 6.32 FEC_TMP is added.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential ix

Updates in Issue 02 (2012-04-05) Based on Product Version

2 Alarm List l 2.2.56 LTX Board Alarm List is modified.

4 Clearing l 4.47 DBMS_DELETE is added.

5 Performance l 5.2.14 FIU Board Performance Event List is modified.

6 Handling l 6.146 TDC is added.

Issue 06 (2015-07-20) Huawei Proprietary and Confidential x

Updates in Issue 01 (2011-12-15) Based on Product Version

2 Alarm List l 2.2.56 LTX Board Alarm List is added.

4 Clearing l 4.21 BD_LEDTEST is added.

5 Performance l 5.2.39 LTX Board Performance Event List is added.

Updates in Issue 05 (2013-09-15) Based on Product Version

Issue 06 (2015-07-20) Huawei Proprietary and Confidential xi