OSN 3500-00449022-Maintenance Cases (V100R008 - 01)

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 V100R008
Maintenance Cases
Issue Date Part Number
01 2008-07-30 00449022
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2008. 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 the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases
Contents
Contents
About This Document.....................................................................................................................1 1 Classification by Products........................................................................................................1-1
1.1 OptiX OSN 1500.............................................................................................................................................1-2 1.2 OptiX OSN 2500.............................................................................................................................................1-2 1.3 OptiX OSN 3500.............................................................................................................................................1-3 1.4 OptiX OSN 3500T (19inch)............................................................................................................................1-4 1.5 OptiX OSN 7500.............................................................................................................................................1-5
2 Classification by Functions and Features..............................................................................2-1

2.1 LCAS...............................................................................................................................................................2-2 2.2 QoS..................................................................................................................................................................2-2 2.3 LPT..................................................................................................................................................................2-2 2.4 ETH-OAM......................................................................................................................................................2-2 2.5 ATM/IMA.......................................................................................................................................................2-2 2.6 RPR.................................................................................................................................................................2-2 2.7 QinQ................................................................................................................................................................2-3
3 Classification by Fault Phenomenon.....................................................................................3-1

3.1 Service Interruption.........................................................................................................................................3-2 3.2 Bit Error...........................................................................................................................................................3-2 3.3 Point Justification............................................................................................................................................3-2 3.4 Equipment Interconnection Failure.................................................................................................................3-2 3.5 Protection Switching Failure...........................................................................................................................3-2 3.6 ECC Fault........................................................................................................................................................3-3 3.7 Ethernet Fault..................................................................................................................................................3-3 3.8 Others..............................................................................................................................................................3-4
4 Classification by Alarms...........................................................................................................4-1
4.1 AU_AIS...........................................................................................................................................................4-2 4.2 B1_SD.............................................................................................................................................................4-2 4.3 B2_SD.............................................................................................................................................................4-2 4.4 B3_EXC..........................................................................................................................................................4-2 4.5 BD_STASTUS................................................................................................................................................4-2 4.6 ETH_LOS........................................................................................................................................................4-2 4.7 HP_TIM..........................................................................................................................................................4-3 Issue 01 (2008-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd i
Contents
4.8 HP_UNEQ.......................................................................................................................................................4-3 4.9 IN_PWR_ABN................................................................................................................................................4-3 4.10 LP_RDI.........................................................................................................................................................4-3 4.11 OOL...............................................................................................................................................................4-3 4.12 P_LOS...........................................................................................................................................................4-3 4.13 POWER_ABNORMAL................................................................................................................................4-3 4.14 R_LOS...........................................................................................................................................................4-4 4.15 SYN_BAD....................................................................................................................................................4-4 4.16 TEMP_OVER...............................................................................................................................................4-4 4.17 Others............................................................................................................................................................4-4
5 MC-B1 to MC-B51...................................................................................................................... 5-1

5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm ....................................................................................5-7 5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port..........................................................................................................................5-8 5.3 MC-B3 Timeslot Collision Occurs When Service Is Created.........................................................................5-9 5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line................................................................................5-10 5.5 MC-B5 Interconnection with SONET Equipment Fails...............................................................................5-11 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE .....................................................5-12 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails..............................................................................................5-14 5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode....................................................................................................................................................................5-14 5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available.............................................................................................................................................................5-15 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings...............................................5-16 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long............................................................5-17 5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm ...........................................................................5-18 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms.................................................................................................................................................................5-19 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR............................................................5-20 5.15 MC-B15 SNCP over MSP Switching Fails ................................................................................................5-21 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards........5-23 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails .......................................5-24 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded.................................................5-25 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment................5-27 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid.......................................................................................5-29 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm .........................................5-30 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm....................................................................5-32 5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards.......................................................................................................................................5-33 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not Closed When Standby XCS Board Is Inserted................................................................................................................5-34 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding...........................................5-35 5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack ...............................................................................................................................................................5-36 ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-07-30)
Contents
5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration............5-37 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm...............................................................................5-39 5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board....................................5-40 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value............5-41 5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack...........................................5-42 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated .............................................................................................................................................................................5-44 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64 ...........5-45 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service.......................................................................5-46 5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration.............................................5-47 5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock Is Configured...........................................................................................................................................................5-48 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service ......5-49 5.38 MC-B38 Extra-Short Detagged Packet Discarded......................................................................................5-50 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss......................................................5-51 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections.................................................5-52 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode...............................................5-54 5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR.......................................5-55 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board...................................................................................................................................................................5-57 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group.........................................................5-58 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link................................................................5-59 5.46 MC-B46 Failing to Create the 622 Mbit/s Service.....................................................................................5-60 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure .............................................................................................................................................................................5-61 5.48 MC-B48 Failing to Create ATM Services..................................................................................................5-62 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group.......................................................5-63 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time.....................................................................................................................................................5-64 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes..............................................5-65
Index.................................................................................................................................................i-1
Issue 01 (2008-07-30)
iii
Figures
Figures
Figure 5-1 Topology of the transmission network.............................................................................................5-13 Figure 5-2 Networking diagram.........................................................................................................................5-22 Figure 5-3 Networking diagram of the SDH network........................................................................................5-23 Figure 5-4 Networking diagram.........................................................................................................................5-27 Figure 5-5 Inter-board alarm suppression relations............................................................................................5-31 Figure 5-6 Suppression relations among key alarms..........................................................................................5-32 Figure 5-7 Two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500..........................................5-38 Figure 5-8 Cable connection between the main subrack and the extended subrack..........................................5-44 Figure 5-9 Incorrect fiber connections...............................................................................................................5-52 Figure 5-10 Correct fiber connections................................................................................................................5-53 Figure 5-11 Unidirectional point-to-point EPL service from PORT1 to PORT2..............................................5-55 Figure 5-12 Configuration of the VCTRUNK-shared EVPL service................................................................5-57
Issue 01 (2008-07-30)
Tables
Tables
Table 5-1 DCC allocation modes of the OptiX OSN 3500................................................................................5-26 Table 5-2 Fiber connection between the NEs.....................................................................................................5-28 Table 5-3 Transmitted and received K1/K2 bytes..............................................................................................5-28 Table 5-4 Bearing modes of the boards in equipment of different versions......................................................5-66
Issue 01 (2008-07-30)
vii
About This Document
About This Document
Purpose
This document lists 51 cases of actual project maintenance and provides four entries of case classification: classified by products, classified by faults, classified by alarms, and classified by functions and features. You can find the desired cases quickly with a proper entry of classification.
Related Versions
The following table lists the product versions related to this document. Product Name OptiX OSN 7500 OptiX OSN 3500 OptiX OSN 3500T (19inch) OptiX OSN 2500 OptiX OSN 1500 OptiX iManager T2000 Version V100R008 V100R008 V100R008 V100R008 V100R008 V200R006C03
Intended Audience
The intended audiences of this document are:
l l l
Field Maintenance Engineer Network Monitoring Engineer System maintenance engineer
Issue 01 (2008-07-30)
About This Document
Organization
This document is organized as follows. Chapter 1 Classification by Products Description When the entry of classification by products is selected, the cases of faults of the OptiX OSN 7500, OptiX OSN 3500, OptiX OSN 3500T (19inch), OptiX OSN 2500, and OptiX OSN 1500 are listed separately. When the entry of classification by functions and features is selected, the cases of LCAS, cases of QoS, cases of LPT, cases of Eth-OAM, cases of ATM/IMA, cases of RPR, and cases of QinQ are listed separately. When the entry of classification by faults is selected, the cases of service interruption, cases of bit errors, cases of abnormal pointer justification, cases of equipment interconnection faults, cases of protection switching faults, cases of ECC faults and cases of Ethernet faults are listed separately. When the entry of classification by alarms is selected, the cases of faults indicated by common alarms such as R_LOS are listed separately. Lists all the cases, that is, case 1 to case 51.
2 Classification by Functions and Features
3 Classification by Fault Phenomenon
4 Classification by Alarms
5 MC-B1 to MC-B51
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows. Symbol Description
DANGER
Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time.
WARNING
CAUTION
TIP
Issue 01 (2008-07-30)
About This Document
Symbol
NOTE
Description Provides more information to emphasize or supplement important points of the main text.
General Conventions
Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Terminal display is in Courier New.
Command Conventions
Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... } * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.
GUI Conventions
Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Issue 01 (2008-07-30)
About This Document
Keyboard Operation
Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operation
Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 01 (2008-07-30) Based on Product Version V100R008

This document of the V100R008 version is of the first release.
Issue 01 (2008-07-30)
1 Classification by Products
1
About This Chapter
1.1 OptiX OSN 1500 1.2 OptiX OSN 2500 1.3 OptiX OSN 3500 1.4 OptiX OSN 3500T (19inch) 1.5 OptiX OSN 7500
Classification by Products
Issue 01 (2008-07-30)
1-1
1.1 OptiX OSN 1500

For the cases concerning the OptiX OSN 1500, see the following:
l l
5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm 5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port 5.3 MC-B3 Timeslot Collision Occurs When Service Is Created 5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
l l l
l l l l l l l l
l l l
1.2 OptiX OSN 2500

l l l
5.5 MC-B5 Interconnection with SONET Equipment Fails 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails 5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-07-30)
l l l l l
1-2

l l l
5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
l l l
1.3 OptiX OSN 3500

l l
5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE 5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long 5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR 5.15 MC-B15 SNCP over MSP Switching Fails 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm 5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not Closed When Standby XCS Board Is Inserted 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding 5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 1-3
l l l l
l l l
l l l
l l l l
l l
Issue 01 (2008-07-30)
l l
5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value 5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service 5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes
l l
l l l
l l l l l l
l l l l
l l l
1.4 OptiX OSN 3500T (19inch)

For the cases concerning the OptiX OSN 3500T (19inch), see the following:
l
5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group
l l l l l
1-4

l l l
5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
l l l
1.5 OptiX OSN 7500

l
5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock Is Configured 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
l l l l l l l l
l l l
Issue 01 (2008-07-30)
1-5
Classification by Functions and Features
About This Chapter

2.1 LCAS 2.2 QoS 2.3 LPT 2.4 ETH-OAM 2.5 ATM/IMA 2.6 RPR 2.7 QinQ
Issue 01 (2008-07-30)
2-1
2.1 LCAS
For cases concerning LCAS, see the following: 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service
2.2 QoS
For cases concerning QoS, see the following:
l l
5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes
2.3 LPT
For cases concerning LPT, see the following: 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode
2.4 ETH-OAM
For cases concerning ETH-OAM, see the following: 5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm
2.5 ATM/IMA
For cases concerning ATM/IMA, see the following:
l l l l
5.44 MC-B44 Failing to Add ATM Connections into a Protection Group 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
l l l
2.6 RPR
2-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-07-30)
For cases concerning RPR, see the following:

l l l
5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board
2.7 QinQ
For cases concerning QinQ, see the following: 5.38 MC-B38 Extra-Short Detagged Packet Discarded
Issue 01 (2008-07-30)
2-3
Classification by Fault Phenomenon
About This Chapter

3.1 Service Interruption 3.2 Bit Error 3.3 Point Justification 3.4 Equipment Interconnection Failure 3.5 Protection Switching Failure 3.6 ECC Fault 3.7 Ethernet Fault 3.8 Others
Issue 01 (2008-07-30)
3-1
3.1 Service Interruption

For cases concerning service interruption, see the following:
l
5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not Closed When Standby XCS Board Is Inserted
l l
3.2 Bit Error

For cases concerning bit error, see the following:
l l l
5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64
l l
3.3 Point Justification

For cases concerning pointer justification, see the following: 5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock Is Configured
3.4 Equipment Interconnection Failure

For cases concerning an equipment interconnection failure, see the following:
l l l
5.5 MC-B5 Interconnection with SONET Equipment Fails 5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails
3.5 Protection Switching Failure

For cases concerning a protection switching failure, see the following:
l
5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode
3-2

l l
5.15 MC-B15 SNCP over MSP Switching Fails 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment 5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value 5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration
3.6 ECC Fault

For cases concerning a ECC fault, see the following:
l
5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded 5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration 5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value
l l l
l l
3.7 Ethernet Fault

For cases concerning an ECC fault, see the following:
l l l
5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to CrossConnect Service 5.38 MC-B38 Extra-Short Detagged Packet Discarded 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode 5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group
l l l l l l
Issue 01 (2008-07-30)

l l l
5.45 MC-B45 Displaying CAC Check Errors When Creating a Link 5.46 MC-B46 Failing to Create the 622 Mbit/s Service 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure 5.48 MC-B48 Failing to Create ATM Services 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes
l l l
3.8 Others
For cases concerning other faults, see the following:
l l l l l l l l
5.3 MC-B3 Timeslot Collision Occurs When Service Is Created 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm
3-4
Issue 01 (2008-07-30)
4
About This Chapter
4.1 AU_AIS 4.2 B1_SD 4.3 B2_SD 4.4 B3_EXC 4.5 BD_STASTUS 4.6 ETH_LOS 4.7 HP_TIM 4.8 HP_UNEQ 4.9 IN_PWR_ABN 4.10 LP_RDI 4.11 OOL 4.12 P_LOS 4.13 POWER_ABNORMAL 4.14 R_LOS 4.15 SYN_BAD 4.16 TEMP_OVER 4.17 Others
Classification by Alarms
Issue 01 (2008-07-30)
4-1
4.1 AU_AIS
For cases concerning the AU_AIS alarm, see the following:
l l
5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value
4.2 B1_SD
For cases concerning the B1_SD alarm, see the following: 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms
4.3 B2_SD
For cases concerning the B2_SD alarm, see the following: 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms
4.4 B3_EXC
For cases concerning the B3_EXC alarm, see the following: 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value
4.5 BD_STASTUS
For cases concerning the BD_STASTUS alarm, see the following:
l
5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration 5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board
4.6 ETH_LOS
For cases concerning the ETH_LOS alarm, see the following: 5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm
4.7 HP_TIM
For cases concerning the HP_TIM alarm, see the following:
l l
5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service
4.8 HP_UNEQ
For cases concerning the HP_UNEQ alarm, see the following:
l l
5.15 MC-B15 SNCP over MSP Switching Fails 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration
4.9 IN_PWR_ABN
For cases concerning the IN_PWR_ABN alarm, see the following: 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm
4.10 LP_RDI
For cases concerning the LP_RDI alarm, see the following: 5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port
4.11 OOL
For cases concerning the OOL alarm, see the following: 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm
4.12 P_LOS
For cases concerning the P_LOS alarm, see the following: 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long
4.13 POWER_ABNORMAL
For cases concerning the POWER_ABNORMAL alarm, see the following:
Issue 01 (2008-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 4-3
5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm
4.14 R_LOS
For cases concerning the R_LOS alarm, see the following: 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm
4.15 SYN_BAD
For cases concerning the SYN_BAD alarm, see the following: 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated
4.16 TEMP_OVER
For cases concerning the TEMP_OVER alarm, see the following: 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE
4.17 Others
Cases concerning other uncommon alarms are as follows:
APS_INDI
For cases concerning the APS_INDI alarm, see 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards.
B3_SD
For cases concerning the B3_SD alarm, see 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value.
HSC_UNAVAIL
For cases concerning the HSC_UNAVAIL alarm, see the following:
l
5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated
4-4
Issue 01 (2008-07-30)
RPR_PS_CHANGE
For cases concerning the RPR_PS_CHANGE alarm, see 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss.
Issue 01 (2008-07-30)
4-5
5 MC-B1 to MC-B51
5
About This Chapter
MC-B1 to MC-B51
5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm The EFS4 boards at certain stations report the ETH_LOS alarm after the cross-connections of the FE services are added or deleted. This fault can be rectified by disabling the unused MAC ports. 5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port When the OptiX OSN 1500 is connected to the 155 Mbit/s optical port of the router of company C, the LP_RDI alarm is generated in the 2 Mbit/s service. The relevant analysis shows that the higher order path overheads of the line board are in the pass-through state, which results in the service interruption. Hence, the overhead mode must be correctly set before a higher order service is changed to a lower order service. 5.3 MC-B3 Timeslot Collision Occurs When Service Is Created An incorrect VC-12 timeslot numbering scheme is used. Therefore, timeslot collision occurs when a VC-3 service is created. Hence, you need to perform the service configuration according to the selected VC-12 timeslot numbering scheme when creating a VC-12/VC-3 service. 5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line When optical ports of different types are interconnected, certain bit errors are reported on the SDH line. Hence, when connecting the fibers, ensure that the optical ports to be interconnected are of the same type. 5.5 MC-B5 Interconnection with SONET Equipment Fails The OptiX OSN equipment fails to interconnect with the SONET equipment. Check the relevant information. It is found that all the optical interface boards must be of the N2 series and that the pass-through services must be configured at the 3xAU-3 level. Otherwise, the interconnection fails. 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE When the temperature is very high, the cross-connect board constantly reports the temperature alarm. As a result, the PQ1 starts to abnormally report the LPBBE performance event. Hence, you need to ensure that the working temperature of the equipment is within the normal range during the routine maintenance. 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails
5 MC-B1 to MC-B51
When you delete the PQ1 boards on the T2000, you also need to delete the corresponding interface boards. Otherwise, deleting the tributary boards may fail. 5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode After the standby CXL board is switched to the main mode, the communication between the equipment and the NMS fails. Check the relevant information. It is found that the MAC address of the port is changed after the switching, and as a result the network is blocked. In this case, ensure that the router supports different MAC addresses of the same port. 5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available The fibers between the three independent subnetworks are not connected but the ECC communication is available. Check the relevant information. It is found that the OSI communication protocol is enabled by default and thus the routes are automatically created. In this case, to isolate the three subnetworks, you need to disable the OSI communication protocol. 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings During the deployment of the OptiX OSN equipment, two rings are isolated from each other, but the ECC communication is available between the two rings. Check the relevant information. It is found that the extended ECC function is automatically enabled. Hence, to isolated two rings, you need to disable the extended ECC function. 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long When the routed cable exceeds the maximum cable length supported by the equipment, the P_LOS alarm is generated. Hence, it is recommended that the cable length is maintained within 50 meters. Otherwise, the services may be affected. 5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm The J1 and C2 bytes of the interconnected equipment are inconsistent. Hence, the SEP1 board keeps reporting the AU_AIS alarm. Hence, you need to ensure that the overhead bytes are set to be consistent for the interconnected equipment. 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms The optical signal on the 1310 nm wavelength band is beyond the end wavelength of the G.655 fiber. Hence, in certain cases where the G.655 fiber is used to transmit an optical signal on the 1310 nm wavelength band, the optical interface board generates the B1_SD and B2_SD alarms. Note to prevent this problem when you use the G.655 fiber. 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR When the optical time domain reflectormeter (OTDR) is used to check the fibers, the optical ports on the SDH board are damaged because the routing connection is incorrect. Hence, you need to ensure that the test distance and the routing connection are correct when you use the OTDR for testing fibers. 5.15 MC-B15 SNCP over MSP Switching Fails In the case of SNCP over MSP, a switching fails due to the setting of the SNCP switching conditions. To solve this problem, set the HP_UNEQ alarm as a trigger condition of the SNCP switching. 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards Abnormal alarms are reported if the line connection is incorrect on the SDH ring network. Hence, note to ensure that the fiber connection between NEs is correct when networking the equipment. 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails
5 MC-B1 to MC-B51
The mode of the optical module on the board that is configured with the services is different from the fiber mode. Hence, the board fails to work normally. Note to ensure that the mode of the optical module is the same as the fiber mode when you select the board. 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded Connection between the equipment is interrupted when the SCC board is upgraded, because the new SCC board supports fewer DCC channels than the original SCC board. Hence, note to ensure that the new SCC board supports DCC channels not less than the original SCC board supports, when replacing the SCC board. 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment The MSP switching fails because the WDM equipment changes the value of the K byte. Hence, note to ensure that the interconnected WDM equipment does not affect the value of the K byte during the networking process. 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid The J0 and J1 bytes are set to the incorrect values and thus the settings become invalid. Hence, you need to set the J0 and J1 bytes according to the rules of the 16- byte mode of the J0 and J1 bytes. 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm If the higher level alarm R_LOS of an unused optical port is suppressed, the lower level alarm IN_PWR_ABN that is suppressed by the R_LOS alarm is reported. To solve this problem, suppress the corresponding lower level alarms. 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm The PIU board reports the POWER_ABNORMAL alarm. To clear this alarm, re-set the jumpers of the SCC board. 5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards If the main and standby XCS boards are inserted and removed repeatedly, all the boards will be reset in the case of switching when the standby XCS board is not activated. Hence, do not insert and remove the main and standby XCS board repeatedly and check whether the services may be affected before you perform switching for the main and standby XCS boards if the HSC_UNAVAIL is reported on the standby XCS board. 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not Closed When Standby XCS Board Is Inserted If the standby XCS board is inserted when the ejector lever on the main XCS board is not closed, the services are interrupted for tens of seconds after the insertion. Before you insert an XCS board into a subrack where the services are activated, ensure that the ejector lever on the front panel of the main CXS board is in the closed state. 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding To clear bit errors that occur due to loose connection of the PGND cable, reconnect the PGND cable. 5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack The XCE board in the extended subrack is faulty. As a result, the communication between the extended subrack and the main subrack becomes abnormal. To solve this problem, replace the XCE board. 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration
5 MC-B1 to MC-B51
When the N2SL64 board is off-service, data cannot be downloaded to the N2SL64 board. When the N2SL64 board reports the BD_STATUS, do not create any service. 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm The network-wide settings of the SSM clock protocol are different. As a result, the clock is lost. To solve this problem, unify the network-wide SSM protocol. 5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board The EXT ports on the AUX boards of two sets of the OptiX OSN 3500 are incorrectly connected. As a result, boards fail to be added. To solve this problem, remove the cable that incorrectly connects the EXT ports. 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value The B3_EXC and B3-SD thresholds are manually lowered. As a result, the services are interrupted during the MSP switching test. To solve this problem, modify the B3_EXC and B3_SD thresholds to the default values. 5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack The main subrack is still in the running state when it is reconstructed into the extended subrack. At this time, the tributary boards are not reset and thus the new slot IDs cannot be obtained. As a result, the tributary boards in the extended subrack are displayed as off-service on the T2000. To solve this problem, remove the boards without IDs and then insert the boards back to obtain the IDs. 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated The head of the external signal input cable is faulty, and then the external clock signal is deteriorated. As a result, the UXCSB board repeatedly reports the BUS_ERR alarm. To solve this problem, make a new head for the external clock signal input cable. 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64 Bit errors occur on the STM-64 signal board in a long-distance project, due to the impacts of the sensitivity, dispersion and distortion of the fiber. Hence, notice the impacts of the sensitivity, dispersion and distortion of the fiber on the system in a long-distance project. 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service Normally, the J1 byte to be transmitted and the J1 byte to be received in the higher order path should be the same. The HP_TIM alarm is generated on the EGT2 and EFS0 boards. To solve this problem, manually set the J1 byte to be received and the J1 byte to be transmitted to the same values. 5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration The working mode of the SPQ4 board is set incorrectly. As a result, the TPS fails. To solve the problem, set the working modes of the working and protection SPQ4 boards correctly. 5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock Is Configured The 120-ohm 2 MHz external clock is set as the clock source. As a result, the SYN_BAD alarm is reported on the entire network where the OptiX OSN 7500 is the gateway NE, and the networkwide clock jitter exceeds the threshold. 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service When the LCAS function is not enabled on either the source NE or the sink NE, LCAS negotiation faults arise and the LCAS configuration fails if the bound path is configured before
5 MC-B1 to MC-B51
the cross-connect service is configured. You can rectify the fault by deleting the existing configurations at both ends and enabling the LCAS function at both ends. 5.38 MC-B38 Extra-Short Detagged Packet Discarded If certain packets are discarded in a network that employs the QinQ function, you can solve the problem by adding bytes to short packets. 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss The VCTRUNK timeslot loss may result in RPR network switching. In this case, delete the damaged timeslots from the configuration. 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections Incorrect fiber connections may result in RPR network interruption. In this case, connect the fibers correctly and re-configure the cross-connections. 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode If the LPT bearer modes of the ports at both ends are inconsistent, LPT switching may fail. Hence, ensure that the LPT bearer modes of the ports at both ends are consistent. 5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR A flow is created after the relevant Ethernet service is created. After the flow is bound with a CAR, it is found that the CAR does not take effect. (On the instrument, the transmit bandwidth is equal to the receive bandwidth.) 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board After the shaping function is enabled for egress port queues, the services are interrupted. 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group After two connections are created, they cannot be added into a protection group. Hence, you need to configure the sink-source relation of the protection group. 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link CAC check errors are displayed when you create a link. Hence, you need to delete the useless connections on the port. 5.46 MC-B46 Failing to Create the 622 Mbit/s Service The ATM 622 Mbit/s service fails to be created. You need to adjust the VCTRUNCK that is bound with VC-4. 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groups to match with associated VCTRUNKs. 5.48 MC-B48 Failing to Create ATM Services ATM services fail to be created, thus failing to realize the protection. You need to add the two connections into the protection group. 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group IMA boards fail to be added into the DPS protection group, hence failing to realize the DPS protection. 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time Service becoming unavailable when the IMA protocol and VPRing protocol are configured at the same time. You need to rectify the faults at the opposite end. 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes
5 MC-B1 to MC-B51
When the Ethernet boards are interconnected, the test frame cannot function normally due to the inconsistent bearing modes.
5-6
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm

The EFS4 boards at certain stations report the ETH_LOS alarm after the cross-connections of the FE services are added or deleted. This fault can be rectified by disabling the unused MAC ports.
Product
OptiX OSN 1500
Fault Type
l l l
ETH-OAM Ethernet Fault ETH-LOS
Symptom
The network management (NM) center adds and deletes certain cross-connections of FE services when adjusting certain FE services between the nodes. After the services are adjusted, the EFS4 boards at certain stations report the ETH_LOS alarm.
Cause Analysis
During the service adjustment, the ETH_LOS alarm is generated after services are added or deleted. Hence, the fault may exist in the added or deleted FE services.
Procedure
Step 1 Check the FE services between two stations. It is found that the corresponding EFS4 board does not report the ETH_LOS alarm after an FE service is normally added. Step 2 Check the FE service trails that report the ETH_LOS alarm. It is found that the trails are deleted during the maintenance phase of the service adjustment process, that is, the trails do not exist. Step 3 Log in to the T2000 and select NE Explorer. Select the FE service where the ETH_LOS alarm is generated, and check the port attributes of the corresponding EFS4 board. It is found that Enable port of the deleted service is set to Enable. At this time, however, the client-side signals are not accessed. Hence, the board misreports the ETH_LOS alarm. Step 4 Set Enable port to Disable for the deleted service. Then, check the alarm. It is found that the ETH_LOS alarm is cleared. Step 5 Check all the Ethernet boards on which the ETH_LOS alarm is generated. It is found that this alarm occurs due to the same causes. Set Enable port to Disable for the boards on which the Ethernet services are already deleted. Then, the ETH_LOS alarm is cleared. ----End
Reference Information
For details on the parameter Enable port, see the Parameter References.
5 MC-B1 to MC-B51
5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with Router Through 155 Mbit/s Optical Port
When the OptiX OSN 1500 is connected to the 155 Mbit/s optical port of the router of company C, the LP_RDI alarm is generated in the 2 Mbit/s service. The relevant analysis shows that the higher order path overheads of the line board are in the pass-through state, which results in the service interruption. Hence, the overhead mode must be correctly set before a higher order service is changed to a lower order service.
Product
OptiX OSN 1500
Fault Type
l l
Service Interruption LP_RDI
Symptom
During network expansion, the SLQ1 board of the OptiX OSN 1500 is connected directly to the optical card of the router of company C. The network is configured with 1+1 linear multiplex section protection (MSP). One end of the MSP line is the 2 Mbit/s service and the other end is the 155 Mbit/s optical service. The LP_RDI alarm is reported in the 2 Mbit/s service.
Cause Analysis
Check the optical transmission paths, timeslot interconnection, and the modes of the overheads of the SDH boards.
Procedure
Step 1 After you confirm that the physical connections are normal, the SLQ1 board and the optical card of the router of company C receive and transmit signals normally but the link status of the router of company C is down. Step 2 Query the alarm. It is found that no abnormal alarms are generated on the SLQ1 board, but the LP_RDI alarm is reported in the 2 Mbit/s service on the other end. Step 3 Perform inloop at the optical port that is interconnected with the SLQ1 board. It is found that the LP_RDI alarm in the 2 Mbit/s service is cleared. It indicates that the optical transmission paths are normal. Step 4 Perform outloop at the optical port that is interconnected to the SLQ1 board. It is found that the link status of the router of company C is up. In this case, it is suspected that the fault exists in the interconnection. Step 5 Check the relevant information. It is found that the first VC-12s of the VC-4s on the SLQ1 board carry the services and that the first VC-12s of the VC-4s on the router of company C carry the services. Add a 2 Mbit/s service in the twenty-second VC-12 on the SLQ1 board that corresponds
5 MC-B1 to MC-B51
to the second VC-12 on the router of company C. It is found that the LP_RDI persists in the 2 Mbit/s at the opposite end. Step 6 Reset the router and then restart the router. It is found that the fault persists. Step 7 Check the SDH service configuration. The original service of the optical port that is interconnected to the SLQ1 board at the local end is a VC-4 service. Delete this VC-4 service and add a VC-12 service. In this case, the overhead mode should be Termination. Query the overhead mode. It is found that the actual overhead mode is Pass-Through. Then, change the overhead mode to Termination. It is found that the LP_RDI alarm is cleared and that the services are normal. ----End
When you configure a lower order service, the higher order path overheads must be set to the Terminal mode. Otherwise, the services may be interrupted.
5.3 MC-B3 Timeslot Collision Occurs When Service Is Created

An incorrect VC-12 timeslot numbering scheme is used. Therefore, timeslot collision occurs when a VC-3 service is created. Hence, you need to perform the service configuration according to the selected VC-12 timeslot numbering scheme when creating a VC-12/VC-3 service.
Product
OptiX OSN 1500
Fault Type
Configuration_Problem
Symptom
Create VC-12 services 115 one after another in the STM-1 frame. Then, create a VC-3 service in the second VC-3 of the STM-1 frame. It is found that an alarm is generated to report the timeslot collision.
Cause Analysis
The sequential mode (ITU-T) is used as the VC-12 timeslot numbering scheme. Hence, the 15 VC-12 services occupy the second VC-3. Then, timeslot collision is reported when you create the VC-3 service in the second VC-3.
Procedure
Step 1 Right-click the NE on the T2000 and select Configuration. Step 2 According to the service configuration and engineering planning, click Option and select ITUT or Interleaved as the VC-12 timeslot numbering scheme.
5 MC-B1 to MC-B51
Step 3 Create the services according to the selected VC-12 timeslot numbering scheme. ----End
When you create a VC-12/VC-3 service on the T2000, configure the service according to the selected VC-12 timeslot numbering scheme. The following VC-12 timeslot numbering schemes are available: 1. Sequential mode (ITU-T): The VC-12 timeslots that are numbered 1, 4, 7, 10, and so on belong to the first VC-3, the VC-12 timeslots that are numbered 2, 5, 8, 11, and so on belong to the second VC-3, and so on. Interleaved mode: The VC-12 timeslots numbered 121 belong to the first VC-3, and the VC-12 timeslots numbered 2243 belong to the second VC-3, and so on.
2.
5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line

When optical ports of different types are interconnected, certain bit errors are reported on the SDH line. Hence, when connecting the fibers, ensure that the optical ports to be interconnected are of the same type.
Product
OptiX OSN 1500
Fault Type
Bit Error
Symptom
The OptiX OSN 1500, OptiX OSN 2500, and OptiX OSN 9500 are deployed on a network. The 24-hour BER test is performed on the SDH line for three times. Each time the BER test is performed, the SDH analyzer reads certain B3 bit errors and unavailable seconds (UASs). Check the history performance events. It is found that the HPBBE performance events occur every day.
Cause Analysis
Check the receive power, transmit power, and the fiber connection of the SDH line.
Procedure
Step 1 It is found that the transmit power and receive power at each port on the line are normal. Step 2 It is found that the fiber connection of the OptiX OSN 1500 and the OptiX OSN 9500 is incorrect. The L-16.1 port at a station is connected to the L-16.2 port at another station. Replace the CXL board in slot 4 of the OptiX OSN 1500 with the CXL board in slot 5 of the CXL board in slot 4. It is found that the 24-hour BER test can be passed. ----End
5 MC-B1 to MC-B51
5.5 MC-B5 Interconnection with SONET Equipment Fails

The OptiX OSN equipment fails to interconnect with the SONET equipment. Check the relevant information. It is found that all the optical interface boards must be of the N2 series and that the pass-through services must be configured at the 3xAU-3 level. Otherwise, the interconnection fails.
Product
OptiX OSN 2500
Fault Type
Equipment Interconnection Failure
Symptom
On the STM-16 MSP ring comprising the OptiX OSN 2500, two stations are added with the N2SLQ1 boards, on which one STM-1 optical port is added to support the interconnection between the OptiX OSN 2500 and the SONET equipment. The pass-through services on the MSP ring are configured at the VC-4 level. Connect the analyzer to the OptiX OSN 2500 and the SONET equipment. It is found that the analyzer shows normal test results. Interconnect the OptiX OSN 2500 and the SONET equipment, perform the test again, and then find that the corresponding ports of the equipment on both the sides report AIS and that the services are unavailable.
Cause Analysis
The analysis result shows that the OptiX OSN 2500 and the SONET equipment are normal. Hence, the fault may exist in the interconnection. In this case, check whether the overheads of the OptiX OSN 2500 and the SONET equipment are consistent, whether the OptiX OSN 2500 and the SONET equipment has any restrictions on interconnection, or whether any special configurations are required.
Procedure
Step 1 Check the relevant information. It is found that the SDH service configuration is correct, that the N2-series boards are auto-adaptive in interconnecting with the SONET equipment, and that the overheads such as the S1 byte are transparently transmitted. Step 2 Check other SDH boards. It is found that the N2-series optical interface boards are only used for interconnection and that the boards on the line side are N1-series boards. Then, it is confirmed that all the boards should be of the N2 series. Step 3 Replace the in-service N1-series optical interface boards with N2-series optical interface boards (including the N2SL16 and N2SLQ1). Configure the pass-through services on the entire MSP ring at the VC-4 level. The services, however, are still unavailable. Step 4 Refer to the deployment guide. It is found that the 3xAU-3 services are added to the N2-series optical interface boards. Note that the pass-through services must be configured at the 3xAU-3 level, not at the VC-4 level, in the case of interconnection with the SONET equipment.
5 MC-B1 to MC-B51
Step 5 When the pass-through services on the entire transmission link are configured at the 3xAU-3 level, the services are normal and the interconnection between the OptiX OSN equipment and the SONET equipment is successful. ----End
The N2-series optical interface boards on the OptiX OSN equipment can interconnect with the SONET equipment only when the following conditions are met: 1. 2. All the line boards must work with N2-series optical interface boards (for example the N2SL64, N2SL16, and N2SQ1 boards), instead of the Q2SL16 and Q2SL4 boards. The pass-through services must be configured at the 3xAU-3 level, not at the VC-4 level.
5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE

When the temperature is very high, the cross-connect board constantly reports the temperature alarm. As a result, the PQ1 starts to abnormally report the LPBBE performance event. Hence, you need to ensure that the working temperature of the equipment is within the normal range during the routine maintenance.
Product
OptiX OSN 3500
Fault Type
l l
Bit Error TEMP_OVER
Symptom
As shown in Figure 5-1, NE1 is the gateway NE and only convergence services are configured between NE1 and other NEs. The clock source of NE1 is the external clock source, and other NEs trace the west line clock source. When the services between NE1 and NE6 become abnormal, the PQ1 boards on NE1 and NE6 report the LPBBE and LPES performance events. Bit errors exist in the paths where the performance events are generated. At the same time, the history alarms show that NE6 reports the TEMP_OVER alarm within a period of time.
5-12
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
Figure 5-1 Topology of the transmission network
BITS
e w 2 e w 3 e
Cause Analysis
If NE1 and NE6 report performance events, the fault may exist on NE1, NE5, or NE6. In this case, you can locate the fault by performing loopback. If NE6 reports the temperature alarm, the ambient temperature may be very high, and thus the PQ1 or EXCSA board becomes faulty.
w e w e w 4 5 6
Procedure
Step 1 Perform inloop for the SL16 board in slot 5, and then the performance events on NE1 are cleared. After the inloop is released, the performance events are generated again. It indicates that the fault may exist on NE5 or NE6. Step 2 Perform outloop for the SL16 board in slot 6, and then the performance events on NE1 are cleared. After the outloop is released, the performance events are generated again. It indicates that the fault may exist on NE6. Step 3 Replace the original PQ1 and SL16 boards on NE6 with the corresponding standby boards, but the performance events persist. Step 4 It indicates that the cross-connect unit is fault. Hence, replace the EXCSA board. Then, the performance events are cleared. The air-conditioner on NE6 is faulty. Then, the ambient temperature becomes very high in the narrow equipment room, and as a result damages the crossconnect unit. ----End
5 MC-B1 to MC-B51
5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails

When you delete the PQ1 boards on the T2000, you also need to delete the corresponding interface boards. Otherwise, deleting the tributary boards may fail.
Product
OptiX OSN 2500
Fault Type
Others
Symptom
On the OptiX OSN 2500, one PQ1 board is inserted in slot 13, which is protected by the other PQ1 board in slot 5. The PQ1 board in slot 13 needs to be deleted. Firstly, the TPS protection group between the PQ1 boards in slot 13 and slot 5 is deleted and then the PQ1 in slot 5 is deleted. When the PQ1 board in slot 13 is deleted, however, the T2000 returns a prompt indicating that the service source cannot be released and the error code is "39492". The NE software is 5.27.01.16 and the board software of the PQ1 is 1.17.
Cause Analysis
You may fail to delete the PQ1 board on the T2000 in the following cases:
l l l
The PQ1 board may belong to a TPS protection group. The PQ1 board is configured with services. The interface board corresponding to the PQ1 board is not deleted.
Procedure
Step 1 Check whether the PQ1 board belongs to the TPS protection group. It is found that the TPS protection group is already deleted before the PQ1 board in slot 13 deleted. Step 2 Check the services on the PQ1 board in slot 13. It is found that the PQ1 board is not configured with any services or paths. Step 3 It is found that the PQ1 board in slot 5 does not have the corresponding interface board, and can be deleted. Then, Check the relevant information. It is found that the PQ1 board in slot 13 has two D12S interface boards in slot 17 and slot 18. Delete the two interface boards, and then the PQ1 board in slot 13 is successfully deleted. ----End
5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to Main Mode
After the standby CXL board is switched to the main mode, the communication between the equipment and the NMS fails. Check the relevant information. It is found that the MAC address
5 MC-B1 to MC-B51
of the port is changed after the switching, and as a result the network is blocked. In this case, ensure that the router supports different MAC addresses of the same port.
Product
OptiX OSN 2500
Fault Type
Protection Switching Failure
Symptom
The OptiX OSN 2500 forms an STM-4 ring, where there is one gateway NE. During the acceptance test, the standby CXL4 board is switched to the main mode, and then the communication between the NEs and the NMS fails but the corresponding alarms are not reported.
Cause Analysis
The software of the standby CXL board may be different from the software of the main CXL board or the DCN may be faulty.
Procedure
Step 1 Access the NE at the local end and the switching of the CXL4 boards is successful. It indicates that the software of the main CXL4 board and the software of the standby CXL4 board are the same. Step 2 Contact the DCN service personnel. It is learnt that the router port in the DCN is already blocked. Although the OptiX OSN 2500 has only one ETH port, the MAC address of this port is still changed when the CXL boards are switched. As a result, the router port is blocked. Step 3 The DCN service personnel enable the two MAC addresses of the same router port. Then, the communication is restored to normal. ----End
5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment Is Available
The fibers between the three independent subnetworks are not connected but the ECC communication is available. Check the relevant information. It is found that the OSI communication protocol is enabled by default and thus the routes are automatically created. In this case, to isolate the three subnetworks, you need to disable the OSI communication protocol.
Product
OptiX OSN 3500
Fault Type
ECC Fault
5 MC-B1 to MC-B51
Symptom
The OptiX OSN 3500 forms three independent rings: north ring, southeast ring, and southwest ring. The fiber connection is unavailable between the three rings. Three sets of equipment on the three rings are respectively connected to the hub through a network cable. The hub is connected to the NM computer. Check the ECC routing. Log in to an NE on the north ring and query the ECC routing. It is found that the ECC can be connected to the equipment on the other two rings. The fiber connection, however, is unavailable between the three rings. Log in to an NE on the southeast and southwest rings respectively, and find the same fault exists. The extended ECC is disabled at the gateway NEs on the three rings. Normally, the NEs on the three rings cannot log in to each other in this case.
Cause Analysis
The problem may exist with the fiber connection or the communication protocol of the gateway NE.
Procedure
Step 1 Check whether the fibers are correctly connected. Remove the network from the gateway NE on the southwest ring to the hub. Log in to an NE on the north ring and check the ECC routing. It is found that the NE fails to connect to the NEs on the southwest ring. Then, remove the network from the gateway NE on the southeast ring to the hub. At this time, only the gateway NE on the north ring is connected to the NMS at the hub. Log in to an NE on the north ring, check the ECC routing. It is found that this NE fails to connect to the NEs on the southwest and southeast rings. It indicates that the fiber connection is correct. Step 2 Check the status of the OSI protocol of the gateway NEs. The OptiX OSN equipment supports the OSI communication protocol. Hence, the OSI protocol is enabled at the network port by default. That is, when the equipment is interconnected through a hub, the corresponding routes are automatically created. Disable the OSI protocol of the gateway NE and then the ECC communication between the subnetworks becomes unavailable. All the NEs can log in to NEs on the same ring only. ----End
5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings

During the deployment of the OptiX OSN equipment, two rings are isolated from each other, but the ECC communication is available between the two rings. Check the relevant information. It is found that the extended ECC function is automatically enabled. Hence, to isolated two rings, you need to disable the extended ECC function.
Product
OptiX OSN 3500
Fault Type
ECC Fault
5 MC-B1 to MC-B51
Symptom
The OptiX OSN 3500 forms two rings: north ring and south ring. The two rings are isolated from each other. The north and south rings are connected to the NMS in the central equipment room through a hub for centralized monitoring. Check the ECC routing of the NE. It is found that the ECC routes between the north ring and the south ring are abnormally available.
Cause Analysis
The possible causes are as follows:
l
The fiber connection between the north ring and the south ring in the central equipment room is incorrect. For example, the fibers of the south ring are connected to the north ring. The extended ECC function is automatically enabled.
Procedure
Step 1 Disable the laser by using the T2000. It is found that the fiber connection on the north and south rings is correct. Step 2 Check the ECC routing. The OptiX OSN equipment is newly deployed. Thus, the extended ECC function is not preset and is in the default mode. That is, the AUX board automatically enables the extended ECC function. Disable the extended ECC function. It is found that the ECC communication between the north and south rings is unavailable. ----End
5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long

When the routed cable exceeds the maximum cable length supported by the equipment, the P_LOS alarm is generated. Hence, it is recommended that the cable length is maintained within 50 meters. Otherwise, the services may be affected.
Product
OptiX OSN 3500
Fault Type
l l
Service Interruption P_LOS
Symptom
The OptiX OSN equipment provides a client with a VC-3 service. This service is mapped from the PL3 board to the SL64 board. The client complained that the PL3 board continues to report the P_LOS alarm for more than 30 seconds and the services were affected.
Cause Analysis
5 MC-B1 to MC-B51
l l l l
The interface board PL3 is faulty or the PL3 board is not inserted properly into the slot. The equipment grounding is improper. The connection of the DDF is loosened. The cable routed from the DDF to the equipment exceeds the maximum cable length supported by the equipment.
Procedure
Step 1 Check the interface board that corresponds to the PL3 board. It is found that the interface board is corrected inserted. It indicates that the problem is not with the interface board. Step 2 Check the connection between the equipment port and the DDF and find the connection is correct. Step 3 Check the length of the cable routed from the DDF to the equipment. It is found that the cable length exceeds 70 meters. In this case, adjust the position of the equipment to ensure that the cable length from the DDF to the equipment is less than 50 meters. Then, the alarm is cleared. ----End
5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm

The J1 and C2 bytes of the interconnected equipment are inconsistent. Hence, the SEP1 board keeps reporting the AU_AIS alarm. Hence, you need to ensure that the overhead bytes are set to be consistent for the interconnected equipment.
Product
OptiX OSN 3500
Fault Type
l l
Equipment Interconnection Failure AU_AIS
Symptom
The OptiX OSN 3500 is configured with the SEP1 board. After the OptiX OSN 3500 is interconnected with the data equipment from another manufacturer, the SEP1 board keeps reporting the AU_AIS alarm.
Cause Analysis
When the OptiX OSN 3500 interconnects with third-party data equipment, the J1 and C2 bytes of the OptiX OSN 3500 may be inconsistent with the J1 and C2 bytes of the third-party data equipment.
Procedure
Step 1 Log in to the T2000 and select NE Explorer.
5 MC-B1 to MC-B51
Step 2 Select SEP1 from the Object Tree and choose Configuration > Overhead Management > VC3 Path Overhead from the Function Tree. Step 3 Click Trace Byte J1 and Signal Flag C2 tabs respectively to check the J1 byte and C2 byte transmitted from the interconnected equipment and find the J1 and C2 bytes are inconsistent with the default values of the J1 and C2 bytes of the OptiX OSN 3500. In this case, modify the values of the J1 and C2 bytes to be consistent. Then, the AU_AIS alarm is cleared. ----End
5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SD Alarms
The optical signal on the 1310 nm wavelength band is beyond the end wavelength of the G.655 fiber. Hence, in certain cases where the G.655 fiber is used to transmit an optical signal on the 1310 nm wavelength band, the optical interface board generates the B1_SD and B2_SD alarms. Note to prevent this problem when you use the G.655 fiber.
Product
OptiX OSN 3500
Fault Type
l l l
Bit Error B1_SD B2_SD
Symptom
The client replaces the fiber, checks the optical power and finds that the optical power is within the normal range but the SL16 board reports the B1_1SD and B2_SD alarms. After all the relevant optical ports are cleaned, the alarms persist.
Cause Analysis
The alarms are generated after the fiber is replaced. Hence, the problem should be not with the optical interface board but with the fiber.
Procedure
Step 1 Replace the original fiber back. It is found that the optical power changes slightly and the bit errors disappear. Step 2 Check the models of the optical interface board and the fiber. It is found that the optical interface board operates on the 1310 nm wavelength band. Before the cutover, the G.652 fiber is used whereas after the cutover, the G.655 fiber is used. The G.652 fiber can transfer optical signals on the 1310 nm and 1550 nm wavelength bands whereas the G.655 fiber can transfer only optical
5 MC-B1 to MC-B51
signals on the 1550 nm wavelength band. The 1310 nm wavelength band is beyond the end wavelength of the G.655 fiber. As a result, bit errors occur in the signal. ----End
Normally, this problem does not occur when the G.655 is used to transfer an optical signal on the 1310 wavelength band. In terms of the technical specifications, however, the optical signal on the 1310 nm wavelength band is beyond the end wavelength of the G.655 fiber. As a result, the normal transfer of the optical signal is not ensured. Note to prevent this problem when using the G.655 fiber.
5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR

When the optical time domain reflectormeter (OTDR) is used to check the fibers, the optical ports on the SDH board are damaged because the routing connection is incorrect. Hence, you need to ensure that the test distance and the routing connection are correct when you use the OTDR for testing fibers.
Product
OptiX OSN 3500
Fault Type
Others
Symptom
Use the OTDR to test the fiber between NE A and NE B. The fiber length between NE A and NE B is 105 km. NE A and NE B are configured with the SSN1SL1602 boards (with the L-16.2Je port). The test distance of the OTDR is set to 100 km and the OTDR is connected to test the fiber between NE A and a place 5 km away from NE B. During the connection between the OTDR and the ODF, the OTDR is misconnected to NE B. The OTDR is started to test the fiber. The test result shows that the SSN1SL1602 board on NE B is damaged.
Cause Analysis
In the case of different distances, the output optical power of the OTDR has different values. The overload receive power of the L-16.2Je port is 9 dBm. The OTDR is misconnected to NE B, that is, the routing connection is incorrect. Hence, the power transmitted from the OTDR to the L-16.2Je port exceeds the overload receive power of the L-16.2Je port. As a result, the L-16.2Je port is damaged.
Procedure
Replace the damaged board with a new board. ----End
5 MC-B1 to MC-B51
Note the following points when you use the OTDR to test fibers:
l
Clearly mark the labels of the optical ports, fiber jumpers, and ODF when you install the equipment. Otherwise, misoperations may occur during later maintenance. Determine the required test distance and check the connection of the ODF when you use the OTDR. Remove the fiber jumpers from the line board when you use the OTDR to test fibers. In the case of long-distance optical ports, ensure that the routing connection is correct. The overload receive power of a long-distance optical port is low and thus may be damaged by the optical power that exceeds the overload receive power in the case of routing misconnection.
l l
5.15 MC-B15 SNCP over MSP Switching Fails

In the case of SNCP over MSP, a switching fails due to the setting of the SNCP switching conditions. To solve this problem, set the HP_UNEQ alarm as a trigger condition of the SNCP switching.
Product
OptiX OSN 3500
Fault Type
l l
Protection Switching Failure HP_UNEQ
Symptom
Figure 5-2 shows an SNCP over MSP ring.
Issue 01 (2008-07-30)
5-21
5 MC-B1 to MC-B51
Figure 5-2 Networking diagram
OptiX OSN 3500 NE2
OptiX OSN 9500
NE1
NE3
OptiX OSN 9500
NE5 OptiX OSN 3500
NE4
OptiX OSN 3500
NE1, NE2, NE3, NE4, and NE5 form an MSP ring, with an STM-1 chain An SNCP service is created between NE1 and NE3. The working source of this VC-4 service is on the working path of the MSP protection group and the protection source is on the STM-1 link. The SNCP holdoff time is 100 ms. When a fiber cut occurs for the first time (between NE1 and NE2), the MSP switching is normal. When a fiber cut occurs for the second time occurs (between NE3 and NE4), the SNCP service is interrupted but the SNCP switching does not occur.
Cause Analysis
When a fiber cut occurs for the second time, check the SNCP switching status. The SNCP switching of NE1 is in the normal state, which is the reason why the SNCP switching does not occur. On this VC-4 link, NE1 reports the HP_UNEQ alarm to the XCL board and the T2000. Analyze the cross-connections of NE4. It is found that no cross-connection is created. ON NE5, the MSP protection paths are pass-through. Hence, it is determined that no cross-connection is created on NE4 and thus the problem occurs. All the VC-4 signals are unavailable and then the downstream NEs report the HP_UNEQ alarm.
Procedure
Set the HP_UNEQ alarm as a trigger condition of the SNCP switching. Perform the test again. It is found that the switching is successful. ----End
5-22
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards
Abnormal alarms are reported if the line connection is incorrect on the SDH ring network. Hence, note to ensure that the fiber connection between NEs is correct when networking the equipment.
Product
OptiX OSN 3500
Fault Type
l l
Protection Switching Failure APS_INDI
Symptom
Figure 5-3 shows a 4xVC-4 SDH ring configured with path protection (PP). Figure 5-3 Networking diagram of the SDH network
BIT
1
NE1 is the central station and the services of other stations are converged on NE1. The clock source of NE1 is the external clock source, and other NEs trace the west line clock source. The fiber between NE2 and NE3 is cut but the services are not interrupted. At this time, point adjustment performance events occur on NE1, NE3, NE4, NE5, and NE6. The PQ1 boards on NE1, NE3, NE5, and NE6 reports the PS alarm but no alarm is reported on NE4.
5 MC-B1 to MC-B51
Cause Analysis
Normally, the PQ1 boards on NE3, NE4, NE5, and NE6 should report the PS alarm if the fiber between NE2 and NE3 is cut. The PQ1 board on NE4 does not report the PS but the services are normal. The west line board on NE4 can normally receive services from NE1. Hence, the fiber connection of NE4 may be incorrect. That is, the west line of NE4 is connected to the west line of NE5 and the east line of NE4 is connected to the east line of NE3.
Procedure
Check the fiber connection of NE4. It is found that the fibers are misconnected. After the fiber connection is corrected, the PQ1 board on NE4 reports the PS alarm. ----End
5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails

The mode of the optical module on the board that is configured with the services is different from the fiber mode. Hence, the board fails to work normally. Note to ensure that the mode of the optical module is the same as the fiber mode when you select the board.
Product
OptiX OSN 3500
Fault Type
Others
Symptom
The N1EGS2 boards of the OptiX OSN 3500 are configured with services. One N1EGS2 board can work normally but the other N1EGS2 board fails to work. Check the transmit optical power. It is found that the transmit optical power of the board that works normally is 9 dBm and the transmit optical power of the board that fails to work is 28 dBm.
Cause Analysis
One N1EGS2 board can work and the other N1EGS2 board fails to work. This problem may occur due to inconsistency between the type of the optical port on the N1EGS2 board and the fiber type.
Procedure
Step 1 Check the model of the optical board. It is found that the board that can be configured with services is the N1EGS211 and that the board that cannot be configured with services is the N1EGS210. That is the models of the two optical boards are different. Step 2 Query the indexes of the optical ports. It is found that the N1EGS210 adopts a multi-mode optical port of which the transmit optical power is 9.5 dBm, the sensitivity is 17 dBm, the working wavelength is 850 nm, and the overload power is not specified, and that the N1EGS211 board
5 MC-B1 to MC-B51
adopts a single-mode optical port of which the transmit optical power is 9 dBm, the sensitivity is 20 dBm, the working wavelength is 1310 nm, and the overload power is not specified. Step 3 Check the fiber jumpers and find that all the fiber jumpers are single-mode. Replace the original fiber jumpers with multi-mode fiber jumpers. Then, the transmit optical power becomes normal and the services are normally received and transmitted. ----End
5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded

Connection between the equipment is interrupted when the SCC board is upgraded, because the new SCC board supports fewer DCC channels than the original SCC board. Hence, note to ensure that the new SCC board supports DCC channels not less than the original SCC board supports, when replacing the SCC board.
Product
OptiX OSN 3500
Fault Type
ECC Fault
Symptom
Two sets of OptiX OSN 3500 equipment need to be upgraded to support ASON services. Hence, the N1SCC board needs to be replaced on the OptiX OSN 3500 with the N1GSCC board. After the replacement, however, the ECC connection between the OptiX OSN 3500 and other equipment is interrupted.
Cause Analysis
The ECC connection between the two sets of equipment is interrupted. The possible causes are as follows:
l l l
The DCC protocol is changed after the replacement. The DCC configuration is incorrect. The port is forbidden to use DCC channels.
Procedure
Step 1 The system is configured with two SLT1 boards, two SLQ4 boards, and two SLQ4 boards. Hence, 34 DCC channels are required. The N1SCC board supports 40 DCC channels, and thus can work normally. Step 2 After replacing the N1SCC with the N1GSCC, the ECC connection is interrupted. Check the used ECC channels. It is found that all the 10 channels are occupied. Step 3 When the ASON features are used, the N1GSCC supports only 10 D1D3 channels.
5 MC-B1 to MC-B51
Step 4 Remove the two SLT1 boards, and then power on the equipment. The SL64 boards occupy the DCC channels first, and the ECC connection is restored. ----End
Before you replace the SCC board, check the DCC channels to ensure that the new SCC board can provide sufficient DCC channels for the equipment. Table 5-1 lists the DCC allocation modes supported by the OptiX OSN 3500. Table 5-1 DCC allocation modes of the OptiX OSN 3500 DCC Allocation Channel type Operation mode Mode 1 Mode 2 N1GSCC N3GSCC/N4GSCC
Supports the D1D3 and D4D12 channel types. Supports 40 D1D3 channels. Supports 10 D1D3 channels. Supports 10 D4D12 channels. Mode 3 Supports 22 D1D3 channels. Supports 6 D4D12 channels. Mode 4 Supports 28 D1D3 channels. Supports 4 D4D12 channels. Mode 5 Mode 6 Mode 7 Supports 160 D1D3 channels. Supports 40 D1D3 channels. Supports 40 D4D12 channels. Supports 26 D1D3 channels. Supports 26 D4D12 channels. Supports 12 D1D3 channels. Supports 12 D4D12 channels. Supports 8 D1D3 channels. Supports 10 D1D3 channels. Supports 70 D1D3 channels. Supports 30 D4D12 channels. Mode 8 Supports 100 D1D3 channels. Supports 20 D4D12 channels.
Protocol type Default mode
Supports the HWECC, IP, and OSI protocols. Mode 1
5-26
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment
The MSP switching fails because the WDM equipment changes the value of the K byte. Hence, note to ensure that the interconnected WDM equipment does not affect the value of the K byte during the networking process.
Product
OptiX OSN 3500
Fault Type
Symptom
Four OptiX OSN 3500 NEs form an MSP ring, as shown in Figure 5-4. Figure 5-4 Networking diagram
NE 144
NE 143 NE 141 STM-16 Two-fiber bidirectional MSP ring
NE 142
Table 5-2 shows fiber connection between the NEs.
Issue 01 (2008-07-30)
5-27
5 MC-B1 to MC-B51
Table 5-2 Fiber connection between the NEs Local End NE Name NE141 NE141 NE142 NE142 NE143 NE143 NE144 NE144 Slot 7 7 7 7 7 7 7 7 Board Name N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 Port 1IN 1OUT 1IN 1OUT 1IN 1OUT 1IN 1OUT NE Name NE144 NE144 NE141 NE141 NE142 NE142 NE143 NE143 Opposite End Slot 12 12 12 12 12 12 12 12 Board Name N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 N1SL16 Port 1OUT 1IN 1OUT 1IN 1OUT 1IN 1OUT 1IN
During the MSP ring switching test, only NE-143 and NE-144 are successfully switched and switching for the other NEs fails.
Cause Analysis
All the K1/K2 bytes received at the west board (7-SL16) on NE-144 are "0". As a result, NE-144 and the downstream NEs fail to receive the K1/K2 byte from the east board (12-SL16) on NE-143. Hence, it is determined that NE-143 and NE-144 may be faulty. Table 5-3 lists the received and transmitted K1/K2 bytes. Table 5-3 Transmitted and received K1/K2 bytes NE-144 Transmit ted K1/ K2 byte Receive d K1/K2 byte K1/K2 0x0230 KC 0xcd KM 0xd3 NE-143 Transmit ted K1/ K2 byte Receive d K1/K2 byte k1/k2 0x0320 KC 0xdc KM 0xd3
0x0000
0xff
0xff
0x0230
0xfd
0xcf
Refer to Table 5-2. It is found that NE-143 can receive the K1/K2 bytes from NE-144 normally. The received K1/K2 bytes, however, are always "0x0000" regardless of whether NE-143 transmits any K1/K2 bytes whose values are "0x0000". In addition, the KC and KM bytes are abnormal. NE-144 fails to receive the K1/K2 byte that is normally transmitted from NE-143. The K1/K2 bytes received in slot 7 on NE-144 are always "0x0000". In addition, it is found that WDM equipment is located between NE-143 and NE-144. Hence, it is suspected that the WDM equipment changes the K1/K2 byte from NE-143 to NE-144. At the same time, WDM equipment in other segments may also affect the K1/K2 bytes, especially the KC and KM bytes.
5 MC-B1 to MC-B51
To check whether the WDM equipment between NE-143 and NE-144 changes the K1/K2 byte, do as follows: 1. Connect an SDH analyzer to NE-143 and an SDH analyzer to NE-144. The connection is as follows: #144-7-------SDH analyzer 1-------WDM equipment------- SDH analyzer 2-------#143-12. Shut down the laser on the board in slot 7 on NE-144. Then, MSP switching occurs. Record the K1, K2, KC, and KM bytes that are read from SDH analyzer 1 and SDH analyzer 2. The test results shows that the bytes read by the two SDH analyzers are different. Hence, it is verified that the WDM equipment changes the overhead bytes.
2. 3.
Procedure
Modify the MSP ring into an SNCP ring and then perform the SNCP switching. The switching is normal. ----End
5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid

The J0 and J1 bytes are set to the incorrect values and thus the settings become invalid. Hence, you need to set the J0 and J1 bytes according to the rules of the 16- byte mode of the J0 and J1 bytes.
Product
OptiX OSN 3500
Fault Type
l
HP_TIM
Symptom
Certain OptiX OSN 3500 that is connected to third-party equipment reports the HP_TIM alarm. To solve the problem, modify the J1 byte to be received and the J1 byte to be transmitted on the T2000 but find an error message is returned, indicating that the value of the J1 byte is invalid. The NE software version is 5.21.13.45, the T2000 version is T2000 V200R002C01B01H, and the J1 byte is "00 B8 F5 17 12 EF 78 13 62 74 05 29 C1 6B".
Cause Analysis
ITU-T G.707 recommends that when the J0 and J1 bytes adopt the 16-byte mode, the highest bits of the first byte and the other bytes must be "1" and "0" respectively. In addition, the other seven bits of the first byte are generated due to the result of a CRC-7 calculation over the previous frame. That is, the first bits of the J0 and J1 bytes do not need to be set manually. The value "00 B8 F5 17 12 EF 78 13 62 74 05 29 C1 6B" does not comply with the previous rule and hence is invalid.
Issue 01 (2008-07-30)
5-29
5 MC-B1 to MC-B51
Procedure
Replan the J1 byte in compliance with the previous rule, and then the problem is solved. ----End
The first bit is the parity bit, and thus you need only to ensure that the other bits are less than "0x80". The error codes of the valid J0 and J1 bytes are as follows:
l l l l
Valid J0 byte to be Received, Error code is 38718. Valid J1 byte to be Received, Error code is 38717. Valid J0 byte to be Sent, Error code is 38677. Valid J1 byte to be Sent, Error code is 38757.
For the method of configuring the J0 and J1 bytes on the T2000, see the OptiX OSN 3500 Intelligent Optical Transmission System Configuration Guide.
5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm

If the higher level alarm R_LOS of an unused optical port is suppressed, the lower level alarm IN_PWR_ABN that is suppressed by the R_LOS alarm is reported. To solve this problem, suppress the corresponding lower level alarms.
Product
OptiX OSN 3500
Fault Type
l l
R_LOS IN_PWR_ABN
Symptom
In an OSN project, the OptiX OSN 3500 and OptiX OSN 1500 form an SNCP ring. Three optical ports on the N1SLQ1 of the OptiX OSN 3500 are not used. Hence, the R_LOS alarm is suppressed for the three optical ports. Then, the IN_PWR_ABN alarm, however, is reported.
Cause Analysis
After a higher level alarm is suppressed, the lower level alarms that are suppressed by this higher level alarm are reported. For example, after the R_LOS alarm is suppressed, the IN_PWR_ABN alarm is reported.
5 MC-B1 to MC-B51
Procedure
Suppress the IN_PWR_ABN alarm. ----End
When you suppress an alarm, note that the lower level alarms that are suppressed by this alarm will be reported. Figure 5-5 shows the inter-board suppression relations among common alarms. Figure 5-5 Inter-board alarm suppression relations
R_LOS R_LOC R_LOF MS _AIS AU_LOP HP _LOM AU_AIS
TU_AIS _VC3 TU_AIS _VC12 C4_R_LAIS D DN_E1AIS

For example: A
TU_AIS
V5_VCAIS DOWN_T1_AIS C2_VCAIS
means A suppresses B
Figure 5-6 shows the suppression relations among key alarms.
Issue 01 (2008-07-30)
5-31
5 MC-B1 to MC-B51
Figure 5-6 Suppression relations among key alarms

R_LOS
R_LOF
TU_AIS
TU_LOP
J0_MM
MS_AIS
B1_EXC
B2_EXC BIP_EXC
AU_AIS
AU_LOP
B1_SD
B2_SD
B3_EXC
HP_TIM
HP_SLM
HP_LOM
HP_UNEQ
B3_SD
TU_AIS
TU_LOP
BIP_EXC
LP_UNEQ For example: A B
LP_TIM
LP_SLM
BIP_SD
means A suppresses B
5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm

The PIU board reports the POWER_ABNORMAL alarm. To clear this alarm, re-set the jumpers of the SCC board.
Product
OptiX OSN 3500
Fault Type
l
POWER_ABNORMAL
Symptom
The PWRB indicator on the N1GSCC board of the OptiX OSN 3500 is on. The T2000 reports the POWER ABNORMAL alarm. The voltage in the second path is 54 V20%. After the two power supplies are switched, the alarm is reported on the other N1GSCC board.
Cause Analysis
It is confirmed that the alarm is generated because the incorrect setting of the jumpers on the SCC board is sent to the field. The J17 and J16 jumpers on the N1GSCC board are used to control the input voltage of the equipment.

l
5 MC-B1 to MC-B51
Remove the jumper cap: The equipment adopts the power supply whose input voltage is 60 V. Maintain the jumper cap: The equipment adopts the power supply whose input voltage is 48 V.
WARNING
In areas other than in Russia, insert the jumper cap and the equipment adopts the 48 V power supply.
Procedure
To clear the alarm, re-set the jumpers according to the OptiX OSN 3500 N1GSCC Board Deployment Guide. ----End
For setting the jumpers on the SCC board, see the OptiX OSN 3500 Intelligent Optical Transmission System Installation Guide.
5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results in Resetting of All Boards
If the main and standby XCS boards are inserted and removed repeatedly, all the boards will be reset in the case of switching when the standby XCS board is not activated. Hence, do not insert and remove the main and standby XCS board repeatedly and check whether the services may be affected before you perform switching for the main and standby XCS boards if the HSC_UNAVAIL is reported on the standby XCS board.
Product
OptiX OSN 3500
Fault Type
l l
Protection Switching Failure HSC_UNAVAIL
Symptom
In the active/standby XCS switching test, the XCS board is switched from slot 9 to slot 10. Then, the XCS board in slot 10 is removed and then inserted back. As a result, all the boards are reset and cannot be restored to the original state.
5 MC-B1 to MC-B51
Cause Analysis
When the standby XCS board starts to work, it needs to synchronize certain data with the main XCS board. In the switching test, the main XCS board is reset before the standby XCS board in slot 9 starts to work. As a result, all the boards start to synchronize and the other boards on the same subrack are reset.
Procedure
Wait until the resetting of the boards is complete. ----End
If the main XCS board is reset, or removed and then inserted back before the standby XCS board starts to work, all the boards are reset. Hence, do not switch the XCS boards frequently. To preventing all the boards from being reset, the standby XCS board reports the HSC_UNAVAIL alarm. When the HSC_UNAVAIL alarm is reported, it does not necessarily indicate that the switching of the active and standby XCS boards is affected. The HSC_UNAVAIL alarm is used to inform the user of not performing cold reset on the main XCS board or not removing and then inserting the main XCS board back, thus preventing the services from being affected.
5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not Closed When Standby XCS Board Is Inserted
If the standby XCS board is inserted when the ejector lever on the main XCS board is not closed, the services are interrupted for tens of seconds after the insertion. Before you insert an XCS board into a subrack where the services are activated, ensure that the ejector lever on the front panel of the main CXS board is in the closed state.
Product
OptiX OSN 3500
Fault Type
Service Interruption
Symptom
Insert the standby XCS in the OptiX OSN 3500. If the ejector lever on the front panel of the main XCS in the current subrack is in the open state, in 30 seconds, the services are interrupted for tens of seconds.
Cause Analysis
None.
5 MC-B1 to MC-B51
Procedure
Step 1 Before you insert an XCS board into a subrack, especially when the services are activated, ensure that the ejector lever on the front panel of the main CXS board is in the closed state. Step 2 If the ejector lever on the front panel of the main XCS board is not in the closed state, close the ejector lever and then insert the standby XCS board. ----End
5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding
To clear bit errors that occur due to loose connection of the PGND cable, reconnect the PGND cable.
Product
OptiX OSN 3500
Fault Type
Bit Error
Symptom
In the transmission network, five sites form an MSP ring. The five sites are names as Site 1, Site 2, Site 3, Site 4, and Site 5 in the counter-clockwise direction. Site 1 is the gateway NE. Only 2 Mbit/s services are activated between Site 1 and other sites. The clock source of Site 1 is the external clock source, and the other sites trace the west line clock source. Query the alarms and performance events. It is found that a large number of bit errors exist in the lower order path at Site 1, Site 2, and Site 3. At the same time, bit errors also exist in the lower order path at Site 4 and Site 5.
Cause Analysis
If bit errors exist in the lower order path at each site, the possible causes are as follows:
l
Site 1 has services with all the other sites. Hence, the fault may exist at Site 1. There is little probability that all the PQ1 boards at Site 1 are faulty. Then, it is suspected that the line board SL16 is faulty. The fan may be faulty. In this case, bit errors occur in the higher order path, which results in bit errors in the lower order path. The 2M cables and fibers may be faulty or the cable connection may be faulty at Site 1.
Procedure
Step 1 Query the history performance data. Reset the performance, then query the current performance. It is found that bit errors persist. Step 2 Check the line boards at each site. It is found that there is no bit error in the higher order path.
5 MC-B1 to MC-B51
Step 3 Check the fan. It is found that there are no anomalies but bit errors persist. Step 4 Check the equipment environment. It is found that the PGND cable is properly connected. Fasten the PGND cable, then query the performance. It is found that bit errors are cleared. ----End
5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in Extended Subrack
The XCE board in the extended subrack is faulty. As a result, the communication between the extended subrack and the main subrack becomes abnormal. To solve this problem, replace the XCE board.
Product
OptiX OSN 3500
Fault Type
l l
ECC Fault BD_STASTUS
Symptom
The OptiX OSN 3500 is configured with an extended subrack. The AUX board on the extended subrack is abnormal. The communication over the EXT port fails. As a result, the main subrack fails to communicate with the extended subrack through the Ethernet path. The services, however, are normal. Connect the ETH, COM, and EXT ports on the AUX board. It is found that the STAT indicator is on and green, and that the other indicators are grey. The PQ1 boards in the extended subrack report the BD_STASTUS alarm.
Cause Analysis
l
The pins in the slots for the SCC (that is, slots 17 and 18) on the backplane in the extended subrack are bent. The pins in the slot for the AUX (that is, slot 37) on the backplane in the extended subrack are bent. The pins in the slots for the XCE (that is, slots 59 and 60) on the backplane in the extended subrack are bent. The XCE board in the extended subrack is faulty.
Procedure
Step 1 Check the pins in slots 17 and 18 on the backplane in the extended subrack. It is found that the pins are normal but the fault persists.
5 MC-B1 to MC-B51
Step 2 Remove the AUX board from the extended subrack. Check the pins in slot 37 on the backplane in the extended subrack. It is found that the pins are normal but the fault persists. Step 3 Remove the XCE board from slot 59 in the extended subrack. It is found that the fault is rectified. Check the pins in slot 59 on the backplane in the extended subrack. It is found that the pins are normal. Then, it is determined that the standby XCE board is damaged in the extended subrack. In this case, replace the XCE board. It is found that the fault is rectified. ----End
5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration
When the N2SL64 board is off-service, data cannot be downloaded to the N2SL64 board. When the N2SL64 board reports the BD_STATUS, do not create any service.
Product
OptiX OSN 3500
Fault Type
l l l
ECC Fault HP_UNEQ BD_STASTUS
Symptom
Figure 5-7 shows a two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500. The networking topology is as follows: A (11-SL64)(8-SL64) B (11-SL64)(8-SL64) C (11-SL64)DA.
Issue 01 (2008-07-30)
5-37
5 MC-B1 to MC-B51
Figure 5-7 Two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500
2-PQ1-1
A
11 8
11 STM-64 Two-fiber bidirectional MSP ring
B
11
D
8
11
2-PQ1-1
Create the E1 service from A (2-PQ1-1) to C (2-PQ1-1), and the E1 service occupies the first VC-4. Then, at the pass-through site B, the HP_UNEQ is generated in the 8-SL64-1-1 channel. Query the C2 byte. It is found that the C2 byte received by the 8-SL64-1-1 channel at site B is "0". The C2 byte transmitted from the 11-SL64-1-1 channel at site A, however, is "0x02". That is, the C2 byte transmitted from site A is different from the C2 byte received at site B.
Cause Analysis
l l
The services are incorrectly configured. The software is faulty.
Procedure
Step 1 Check the history alarms. It is found that the SL64 board in slot 8 at site B has the BD_STATUS alarm.
5 MC-B1 to MC-B51
Step 2 Deactivate the services at site B. Step 3 Activate the service at site B again. It is found that the HP_UNEQ alarm is cleared. ----End
Cause: When the SL64 board is off-service, data cannot be downloaded to the SL64 board. Suggestion: When the N2SL64 board reports the BD_STATUS, do not create any service.
5.28 MC-B28 The EXCSA Board Reports the OOL Alarm

The network-wide settings of the SSM clock protocol are different. As a result, the clock is lost. To solve this problem, unify the network-wide SSM protocol.
Product
OptiX OSN 3500
Fault Type
l l
OOL SYN_BAD
Symptom
The OOL alarms are generated irregularly. The last OOL alarm is generated when the main EXCSA board is switched to the standby EXCSA board. The equipment where the EXCSA board is located provides the main clock source for the other equipment on the network. The EXCSA board reports the OOL, SYN_BAD, and S1_SYN_CHANGE alarms. The OOL alarm indicates that the line clock of the input signal is not traced but is locked by the SDR phase-locked ring. The synchronization source of the EXCSA board is lost. Hence, the synchronization alarm is generated.
Cause Analysis
The standard SSM protocol is enabled for the equipment that generates the alarms, but the extended SSM protocol is enabled for the other equipment on the network. As a result, the input clock signal is not traced and the synchronization alarm is generated.
Procedure
Modify the configuration of the clock subnetwork, that is, enable the extended SSM protocol, and then find that the alarm is cleared. ----End
Issue 01 (2008-07-30)
5-39
5 MC-B1 to MC-B51
5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board
The EXT ports on the AUX boards of two sets of the OptiX OSN 3500 are incorrectly connected. As a result, boards fail to be added. To solve this problem, remove the cable that incorrectly connects the EXT ports.
Product
OptiX OSN 3500
Fault Type
l l
ECC Fault BD_STATUS
Symptom
One SEP1 board on the OptiX OSN 3500 reports the BD_STATUS in an interrupted manner. Erase the data on the SCC board, reset the SCC board. It is found that all boards fail to be added. After the boards are added through other methods, the BD_STATUS alarm on the original SEP1 board persists. The board type of the original SEP1 switches between the PQ1 and the SEP1. The board type of the original EU08 board in slot 19 switches between the EU08 and the D12S. In addition, the idle slot 20 is incorrectly shown to house the D12S board.
Cause Analysis
The data configuration on the SCC board may be incorrect or the inter-board communication may be faulty.
Procedure
Step 1 Erase the database and then reset the SCC board. It is found that no reset record exists and that all boards fail to be added. Step 2 Erase the database on the SCC board again. Then, reset the SCC board on site, and add boards again. It is found that the SCC board can be added but the other boards fail to be added. Step 3 After all the boards are successfully added, the original SEP1 board still reports the BD_STATUS alarm in an interrupted manner. The board type of the original SEP1 switches between the PQ1 and the SEP1. The board type of the original EU08 board in slot 19 switches between the EU08 and the D12S. In addition, the idle slot 20 is incorrectly shown to house the D12S board. Step 4 Exchange the SCC board with the SCC in the corresponding extended subrack (OptiX OSN 3500). Then, repeat Steps 1, 2, and 3, and then find that the problem persists. Step 5 Check the cables on site. It is found that a cable is used to connect the EXT ports on the two sets of OptiX OSN 3500. Remove the cable and then find that the problem is solved. ----End
5 MC-B1 to MC-B51
The EXT ports of the main subrack and the extended subrack can be connected only when the UCXSA board is configured to connect to the extended subrack. In this case, the alarms and configuration information of the extended subrack are transmitted to the SCC board in the main subrack through the EXT ports. The extended subrack need not be configured with the SCC board and the XCE board. When the extended subrack is connected to a non-protection chain, the main subrack and extended subrack are independent of each other. Hence, the EXT ports of the main subrack and the extended subrack need not be connected. If the EXT ports are connected by a cable, collision occurs. As a result, boards fail to be added or cannot be smoothly added. In addition, even the board type switches.
5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value
The B3_EXC and B3-SD thresholds are manually lowered. As a result, the services are interrupted during the MSP switching test. To solve this problem, modify the B3_EXC and B3_SD thresholds to the default values.
Product
OptiX OSN 3500
Fault Type
l l l
Protection Switching Failure B3_EXC AU_AIS
Symptom
Six sets of OptiX OSN 3500 that are configured with the N2SL64 boards form a 10 Gbit/s MSP ring. During the MSP ring switching test, the fiber is cut. The services, however, are not interrupted and the MSP switching is normal. Reconnect the fiber. The switching is restored after 10 minutes. The services, however, are interrupted immediately and are automatically restored in four minutes. At the same time, the optical board where switching is performed reports the B3_SD alarm. The B3_SD alarm lasts for two hours and then is automatically cleared. Check on the T2000. It is found that the MSP switching is normal. Replace the XSC board. It is found that the fault persists.
Cause Analysis
The problem occurs because the B3_EXC and B3_SD thresholds are lowered for the N2SL64 board on the entire network. As specified in G.806, the EXC threshold is 1.0E-x (x = 3, 4, or 5) and the SD threshold is 1.0E-x (x = 5, 6, 7, 8, or 9). Currently, the EXC threshold is defaulted to 1.0E-3 and the SD threshold is defaulted to 1.0E-6 for the OptiX OSN 3500. If the B3_EXC and B3_SD thresholds are lowered to 1.0E-8 and 1.0E-9 respectively, bit errors occur during the MSP ring switching. When the bit errors exceed the B3_EXC and B3_SD thresholds, the alarms are generated.
5 MC-B1 to MC-B51
As specified in G.806, when the bit error rate (BER) is 1.0E-8, the alarm clearing time is 1000s, and when the bit error rate (BER) is 1.0E-9, the alarm clearing time is 10000s. Hence, when the B3_EXC threshold is set to 1.0E-8, the alarm generally lasts for about 15 minutes and then is cleared even if the condition for triggering the B3_EXC alarm already disappears. Currently, the AU_AIS is inserted by default, when the B3_EXC is generated for the OptiX OSN equipment. As a result, the services are interrupted after the MSP switching. When the B3_SD threshold is set to 1.0E-9, generally the alarm lasts for more than two hours and then is cleared. During the previous switching test, the services are restored about 15 minutes (that is, the WTR time of 10 minutes plus service interruption of four minutes plus the time for reconnecting the fiber) after the switching.
Procedure
Modify the B3_EXC and B3_SD thresholds to the default values. Then, the problem is solved. ----End
It is recommended that you disable the AU_AIS insertion in the case of B3_EXC alarm.
5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack
The main subrack is still in the running state when it is reconstructed into the extended subrack. At this time, the tributary boards are not reset and thus the new slot IDs cannot be obtained. As a result, the tributary boards in the extended subrack are displayed as off-service on the T2000. To solve this problem, remove the boards without IDs and then insert the boards back to obtain the IDs.
Product
OptiX OSN 3500
Fault Type
ECC Fault
Symptom
Change the running OptiX OSN 3500 from a main subrack into an extended subrack. Mount the extended subrack to a newly created OptiX OSN 3500. Query the physical slots of the extended subrack. It is found that the boards in the extended subrack fail to be displayed and that the tributary boards in the extended subrack are displayed as off-service on the T2000.
Cause Analysis
l
The connection between the main subrack and the extended subrack is faulty.
5-42

l
5 MC-B1 to MC-B51
The SCC board in the main subrack and the AUX boards in the main subrack and in the extended subrack are faulty. The tributary boards in the extended subrack are not reset and thus the correct slot IDs cannot be obtained.
Procedure
Step 1 Check the connection between the main subrack and the extended subrack. It is found that the connection is normal. Step 2 Perform warm reset on the SCC board and the AUX boards in the main subrack and in the extended subrack. It is found that the problem persists. Step 3 Remove the off-service boards and then insert the boards back to force the boards to perform cold reset. Then, the boards obtain the new slot IDs. The problem is solved. ----End
The following part considers the UXCSB as the cross-connect board of the main subrack and describes the precautions for the connection between the main subrack and the extended subrack.
l
Cable connection between the UXCSB and the XCE: The EXA and EXB ports on the UXCSB board in slot 9 are connected to the EXA ports on the XCE board in slots 59 and 60. The EXA and EXB ports on the UXCSB board in slot 10 are connected to the EXB ports on the XCE board in slots 59 and 60. See Figure 5-8. The EXT port on the AUX board in the main subrack is connected to the EXT port on the AUX board in the extended subrack. See Figure 5-8. Cover the J9 jumper on the AUX board in the main subrack with the jumper cap and maintain the J9 jumper on the AUX board in the extended subrack uncapped. Do as follows to reconstruct a running main subrack into an extended subrack: 1. 2. 3. 4. Remove the SCC board, line board, and certain unused tributary boards. Connect the EXT ports on the two AUX boards and remove the J9 jumper on the AUX board in the extended subrack. Remove the two cross-connect boards. Insert two XCE boards instead and connect the two XCE boards to the UXCSB boards in the new main subrack.
After the two cross-connect boards are removed, the extended subrack has no crossconnections. Hence, the tributary boards in the extended subrack are automatically reset. After the J9 jumper is removed from the AUX board, the tributary boards can obtain the new slot IDs (that is, the original ID plus 50). After performing the operations, you need not remove the tributary boards and then insert the boards back again after the configuration.
Issue 01 (2008-07-30)
5-43
5 MC-B1 to MC-B51
Figure 5-8 Cable connection between the main subrack and the extended subrack
Power distribution unit
Optix OSN3500
Crossover network cable

CLK1 CLK2
A
Extended subrack
REV F&f
ETH COM
Extended subrack cables

EXA EXA
EXT
F1
A
EXB EXB
Optix OSN3500
Extended subrack cables
EXA EXA
Main subrack
EXB EXB
5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated
The head of the external signal input cable is faulty, and then the external clock signal is deteriorated. As a result, the UXCSB board repeatedly reports the BUS_ERR alarm. To solve this problem, make a new head for the external clock signal input cable.
Product
OptiX OSN 3500
Fault Type
l
HSC_UNAVAIL
Symptom
The OptiX OSN 3500 at site A uses the UXCSB board to connect the extended subrack. The clock signal used at site A is the external clock source. The OptiX OSN 3500 at site A forms an
5 MC-B1 to MC-B51
MSP ring with other OptiX OSN 3500. The clocks of the other OptiX OSN 3500 trace the clock source of site A. The standby UXCSB board in slot 10 at site A repeatedly reports the BUS_ERR and HSC_UNAVAIL alarms. At the same time, the SYN_BAD alarm is generated in the networkwide clock signals but the services are not affected.
Cause Analysis
l
The communication cable between the main subrack and the extended subrack is not properly connected or is damaged. The UXCSB board in slot 10 is faulty. The external clock source is faulty.
l l
Procedure
Step 1 Check the communication cable between the main subrack and the extended subrack and find the cable is properly connected. Replace the cable. It is found that the problem persists. Step 2 Perform warm reset and cold reset for the UXCSB boards in slots 9 and 10. It is found that the problem persists. Step 3 Replace the UXCSB board in slot 10. It is found that the problem persists. Hence, the problem should not be with the UXCSB board. Step 4 The SYN_BAD alarm is generated in the network-wide clock signals and the clocks over the entire network trace the clock of site A. Hence, check the external clock cable of the equipment at site A. It is found that the head of the external clock cable is loosely connected to the AUX board. Fasten the head of the external clock cable. It is found that the SYN_BAD, BUS_ERR, and HSC_UNAVAIL alarms are cleared immediately. It is determined that the head of the external clock cable is faulty. Step 5 Make a new head for the external clock cable and then the alarms are cleared. The problem is solved. ----End
5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64
Bit errors occur on the STM-64 signal board in a long-distance project, due to the impacts of the sensitivity, dispersion and distortion of the fiber. Hence, notice the impacts of the sensitivity, dispersion and distortion of the fiber on the system in a long-distance project.
Product
OptiX OSN 3500
Fault Type
Bit Error
5 MC-B1 to MC-B51
Symptom
On an STM-64 link, the line board is the SSN2SL6416 (V-64.2b, LC). The corresponding BPA (14) is used. The receive optical power of the line board is 13.00 dBm. The link has the required DCU board, but bit errors still occur in the fiber.
Cause Analysis
According to the specifications of the SSN2SL6416 (V-64.2b, LC), the receive optical power is within the normal range. Since the DCU board is used, it is determined that the problem should not be with the receive optical power or the DCU board. Compare the input power and the output power of the relevant BPA. It is found that the power of the pre-amplifier is 26.90 dBm. This is why the problem occurs. The power of the laser on the STM-64 signal board should not exceed 27.00 dBm. When the power of the laser approaches 27.00 dBm, the laser is distorted and thus bit errors occur.
Procedure
Step 1 Query the performance of the line board to check whether the power of the laser is within the normal range (between the overload point and the sensitivity). Step 2 Replace the DCU board to check whether the problem can be solved by adjusting the dispersion and attenuation. Step 3 Check the performance of the BPA. The input power of the two ports on the V-64.2b board should exceed 26 dBm (with a margin of 1 dBm). Step 4 It is found that the problem is with the sensitivity, dispersion, and distortion. Step 5 To solve the problem with distortion, check whether bit errors exist on the other side. If yes, replace the original fiber or the BPA (for example, replace the BPA-17 with the BPA-14). Step 6 If no bit error exists on the other side, detect the reason for the excessive attenuation (the difference within 1 dBm to 3 dBm is normal). The excessive attenuation may be caused by the fiber connector, fiber, or fiber head. ----End
The STM-6 signal is sensitive. Hence, notice the sensitivity (use the BPA), dispersion (use the DCU) and distortion (the power of the laser should not be lower than 27 dBm) of the fiber in the case of a long-distance project. Ensure that no bit error will be caused due to impacts of the sensitivity, dispersion and distortion of the fiber.
5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service

Normally, the J1 byte to be transmitted and the J1 byte to be received in the higher order path should be the same. The HP_TIM alarm is generated on the EGT2 and EFS0 boards. To solve this problem, manually set the J1 byte to be received and the J1 byte to be transmitted to the same values.
5 MC-B1 to MC-B51
Product
OptiX OSN 3500
Fault Type
l l
Ethernet Fault HP_TIM
Symptom
When the Ethernet services are configured, the J1 byte to be received and the J1 byte to be transmitted are set to the same values. The HP_TIM alarm, however, is generated on the EGT2 and EFS0 boards.
Cause Analysis
After the Ethernet services are configured, the Ethernet boards at both ends generate the HP_TIM alarm. Check the J1 byte in the single-byte mode on the overhead management interface on the T2000. It is found that the J1 byte to be received and the J1 byte to be transmitted are set to the same values (displayed in hexadecimal). Check the J1 byte in the 16-byte mode. It is found that the J1 byte to be received and the J1 byte to be transmitted are set to different values. Change the value of the J1 byte to be transmitted of the EGT2 or EFS0 board. It is found that the J1 byte received on the other board remains unchanged.
Procedure
Set the J1 byte to be received by the RX Ethernet board in the VC-4 on the SDH line board that corresponds to the TX Ethernet board. Then, the HP_TIM alarm is cleared. ----End
The J1 byte to be received of the RX Ethernet board should be set in the VC-4 on the SDH line board that corresponds to the TX Ethernet board. Change the values of the J1 byte to be transmitted and the J1 byte to be received on the SDH line to prevent the HP_TIM alarm form being generated on the line.
5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration
The working mode of the SPQ4 board is set incorrectly. As a result, the TPS fails. To solve the problem, set the working modes of the working and protection SPQ4 boards correctly.
Product
OptiX OSN 3500
Fault Type
5 MC-B1 to MC-B51
Symptom
On the OptiX OSN 3500, three SP14 boards form a TPS protection group. Slot 2 is the sot for the protection board. Slots 3 and 4 are the slots for the working boards. During the PTS test, the TPS switching time is longer than 50 ms.
Cause Analysis
The SPQ4 board can work in the 104 Mbit/s or 150 Mbit/s mode. The default working mode is the 140 Mbit/s mode. Check the TPS configuration. It is found that the working mode of the protection board in slot 2 is different from the working modes of the working boards in slots 3 and 4. The SPQ4 board in slot 2 is set to the 140 Mbit/s mode whereas the SPQ4 boards in slots 3 and 4 are set to the 150 Mbit/s mode.
Procedure
Set the SPQ4 in slot 2 to the 150 Mbit/s mode and then perform TPS. The TPS is successfully performed. ----End
When you configure the TPS function, ensure that the working modes of the multi-mode boards (for example, the SPQ4) are the same.
5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock Is Configured
The 120-ohm 2 MHz external clock is set as the clock source. As a result, the SYN_BAD alarm is reported on the entire network where the OptiX OSN 7500 is the gateway NE, and the networkwide clock jitter exceeds the threshold.
Product
OptiX OSN 7500
Fault Type
Point Justification
Symptom
After the OptiX OSN 7500 is adopted as the gateway NE and the 120-ohm 2 MHz external clock is configured as the clock source, a large number of SYN_BAD alarms are reported on the entire network and the network-wide clock jitter exceeds the threshold.
Cause Analysis
Because of high receiver sensitivity of the 120-ohm 2 MHz port, environmental noise and improper grounding of the OptiX OSN 7500 may result in amplification of noise in the 1205-48 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
ohm 2 MHz clock regeneration circuit and irregular reference clocks. If the OptiX OSN 7500 traces these irregular reference clocks, violent clock frequency jitter occurs. The other NEs on the ring trace the clock of the gateway NE. Hence, the SYN_BAD is reported on the entire network and the clock jitter exceeds the threshold.
Procedure
Adopt one of the following methods to solve this problem: l l Replace the 2 MHz external clock source with the 2 Mbit/s external clock source. Use the 120-ohm/75-ohm clock conversion cable and connector to convert the 120-ohm clock signal into a 75-ohm clock signal, and then transmits this signal to the 75-ohm port on the OptiX OSN 7500.
----End
High receiver sensitivity affects the circuit of the 120-ohm 2 MHz port only, and does not affect the 75-ohm port and 2 Mbit/s clock input. In addition, if the input clock is configured as the 2 MHz mode, do not set the external clock as the clock source when no external clock signal is accessed. Otherwise, the external clock source is traced even if there is no clock source input. As a result, the clock jitter exceeds the threshold.
5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service
When the LCAS function is not enabled on either the source NE or the sink NE, LCAS negotiation faults arise and the LCAS configuration fails if the bound path is configured before the cross-connect service is configured. You can rectify the fault by deleting the existing configurations at both ends and enabling the LCAS function at both ends.
Products
l l l l l
OptiX OSN 1500A/1500B OptiX OSN 2500 OptiX OSN 3500 OptiX OSN 3500T (19inch) OptiX OSN 7500
Fault Type
l l
LCAS Ethernet Fault
Case Description
For the point-to-point NE A and NE B, the LCAS function is enabled at NE A but disabled at NE B. After the bound paths are configured for the data processing boards at both ends and the cross-connect service is configured from the data processing board to the line board, LCAS
5 MC-B1 to MC-B51
negotiation at NE A becomes abnormal, that is, all the timeslots are deleted or only one timeslot remains.
Cause Analysis
The fault arises owning to the version and working principles of the LCAS function. Hence, the following situations should be prevented:
l l
The LCAS function is disabled at one end. The bound paths are configured before the cross-connection service is configured.
Procedure
Step 1 Query the status of the LCAS function at both ends, and ensure that the function is enabled at both ends. Step 2 Query the paths bound at both ends, and delete the existing configurations. Step 3 Query and delete the cross-connect service configured between the data processing board and the line board. Step 4 Configure the cross-connect service between the data processing board and the line board, and then configure the bound paths. The alarm disappears, and the troubleshooting is complete. ----End
5.38 MC-B38 Extra-Short Detagged Packet Discarded

If certain packets are discarded in a network that employs the QinQ function, you can solve the problem by adding bytes to short packets.
Products
l l l l l
OptiX OSN 1500A/1500B OptiX OSN 2500 OptiX OSN 3500 OptiX OSN 3500T (19 inch) OptiX OSN 7500
Fault Type
l l
QinQ Ethernet Fault
Case Description
The point-to-point protocol over Ethernet (PPPoE) client services enter a switch for convergence. The converged services are accessed to an OptiX NE for transmission over networks to the broadband access server at the destination end. The PPPoE active discovery session-confirmation (PADS) data packets in the downlink services returning from the broadband server to the client side are lost. As a result, the PPPoE verification fails.
5 MC-B1 to MC-B51
Cause Analysis
The PPPoE services include the PADI, PADO, PADR and PADS data packets. Compared with the other types of data packets, the PADS data packet is only of a 64-byte length which is the minimum data packet length that the Ethernet supports. After the QinQ function is configured, two tags are added without changing the original data packet length: C-VLAN and S-VLAN. When the downlink services travel over the OptiX NE to the client-side NE, the external S-VLAN tag is detagged. Hence, the data packet length changes from 64 bytes to 60 bytes. As a result, when the 60-byte services travel over the switch, they are regarded as abnormal and extra-short Ethernet data packets and are thus discarded. In this case, the PPPoE endpoint cannot receive the PADS data packet. As a result, the PPPoE verification fails and the services are not available. Currently, some Ethernet boards are added with the short-packet length extension function against the problem that the extra-short data packets caused during detagging are discarded. When the length of a data packet is extra-short, it can be complemented on the Ethernet boards on the client side and system side to ensure that the data packet is transmitted at a length compliant with the Ethernet specification.
5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss

The VCTRUNK timeslot loss may result in RPR network switching. In this case, delete the damaged timeslots from the configuration.
Product
l l l l l
OptiX OSN 1500A/1500B OptiX OSN 2500 OptiX OSN 3500 OptiX OSN 3500T(19inch) OptiX OSN 7500
Fault Type
l l l
RPR Ethernet Fault RPR_PS_CHANGE
Symptom
Services in the RPR network is connected. In this case, the RPR_PS_CHANGE alarm is reported and the switching occurs in the RPR network.
Cause Analysis
The fault may be caused due to VCTRUNK timeslot loss.
5 MC-B1 to MC-B51
Procedure
Step 1 Enable the LCAS protocol of the corresponding Ethernet board to check whether the timeslots work normally. If some timeslots are damaged or fail, the LCAS protocol can delete the timeslots from the VCTRUNK. Step 2 Query and check whether the timeslots actually bound to the VCTRUNK and the timeslots configured for the VCTRUNK are consistent. If not, it indicates that the damaged VC-4 timeslots are already deleted by the LCAS protocol. Then, the alarm is cleared and the fault is rectified. ----End
5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections

Incorrect fiber connections may result in RPR network interruption. In this case, connect the fibers correctly and re-configure the cross-connections.
Product
l l l l l
Fault Type
l l
RPR Ethernet Fault
Symptom
The fibers are incorrectly connected. In this case, the RPR_NB_INCONSIS alarm is reported, which results in the RPR network interruption. Figure 5-9 shows incorrect fiber connections. Figure 5-9 Incorrect fiber connections
S1 S2 S3
Cause Analysis
The previous fault is caused due to incorrect fiber connections. In this case, ringlet0 receives packets from ringlet1 or ringlet1 receives packets from ringlet0. As shown in Figure 5-9, the eastbound adjacent node of S2 is S3 but the westbound adjacent node of S3 is S1 rather than S2. Thus, the RPR_NB_INCONSIS alarm is reported.
5 MC-B1 to MC-B51
Procedure
Step 1 Query the cross-connection configuration on each board to check whether there are crossconnections that are not completely configured on a board. Configure cross-connections from the Ethernet board to the SDH line board for each NE. See Reference Information. Step 2 Check whether the fiber connections on the line board are correct. Connect fibers to make the input and output interfaces of the optical modules match. Figure 5-10 shows links between nodes. After fibers are connected properly, the alarm is cleared and the fault is rectified. Figure 5-10 Correct fiber connections
S1 S2 S3
----End
The steps of configuring Cross-Connections: 1. 2. 3. 4. In the Main View, select the desired NE. Right-click the NE and choose NE Explorer from the shortcut menu. Choose Configuration > SDH Service Configuration from the Function Tree. Click Create in the lower right of the window. The Create SDH Service dialog box is then displayed. Set the parameters in the dialog box as follows:
l l l l
Level: VC-4 Direction: Bidirectional Source Slot: 13-N2EGR2-1 Click parameters.

. In the Please select the source timeslot dialog box, set the following
Port: 1 Higher Order Timeslot: 1,3,5,7,9,11,13,15
l l l l
Sink Slot: 12-N2SL16-1(SDH-1) Sink Timeslot Range: 1 - 8 Activate Immediately: Yes Then, click Apply. Level: VC-4 Direction: Bidirectional Source Slot: 13-N2EGR2-1 Click parameters.
5.
Based on the operations in Step 4, set the parameters in the dialog box as follows:
l l l l
. In the Please select the source timeslot dialog box, set the following
Port: 1
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
l l l l
Higher Order Timeslot: 2,4,6,8,10,12,14,16
Sink Slot: 7-N2SL16-1(SDH-1) Sink Timeslot Range: 1 - 8 Activate Immediately: Yes Then, click Apply.
5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode
If the LPT bearer modes of the ports at both ends are inconsistent, LPT switching may fail. Hence, ensure that the LPT bearer modes of the ports at both ends are consistent.
Product
l l l l l
OptiX OSN 1500A/1500B OptiX OSN 2500 OptiX OSN 3500 OptiX OSN 3500T (19-inch) OptiX OSN 7500
Fault Type
l l
LPT Ethernet Fault
Symptom
In the case of version R006 or earlier than R006, LPT fails to work normally when the EFS board interconnects with the EMS4 board. After the service at the SDH layer is disconnected, automatic switching can be normally performed at both ends. After the network cable is removed from an Ethernet port, automatic switching at the opposite end fails.
Cause Analysis
In the case of version R006 or earlier than R006, the LPT function of the EFS board supports the MAC bearer mode only whereas the EMS4 board supports the GFP bearer mode only. Hence, the two boards fail to interconnect with each other because the LPT bearer modes are different.
Procedure
Modify the LPT bearer modes of the ports at both ends to be the same. ----End
None.
5 MC-B1 to MC-B51
5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR
A flow is created after the relevant Ethernet service is created. After the flow is bound with a CAR, it is found that the CAR does not take effect. (On the instrument, the transmit bandwidth is equal to the receive bandwidth.)
Product
l l l l l
Fault Type
l l
QoS Ethernet Fault
Symptom
As shown in Figure 5-11, a unidirectional point-to-point EPL service is configured from PORT1 to PORT2 on the same board. Figure 5-11 Unidirectional point-to-point EPL service from PORT1 to PORT2
Ethernet service processing board PORT1 SmartBits PORT2
Create the flow at PORT1. Set the flow type to port+VLAN+priority. Configure the CAR. Set both the CIR and PIR to 10 Mbit/s. Bind the CAR to the flow. Use the SmartBits to transmit packets at a rate higher than 10 Mbit/s. The receive bandwidth of the instrument, however, is found to be equal to the transmit bandwidth of the instrument.
5 MC-B1 to MC-B51
Cause Analysis
This problem has the following possible causes. 1. 2. The CAR is not enabled. After the CAR is bound to the flow, the CAR is effective for the flow only if the CAR is enabled. The flow type does not match the service type. In this fault case, a port flow should be configured for the point-to-point EPL service.
Procedure
Step 1 Cause 1: The CAR is not enabled. 1. Enable the CAR. a. b. c. d. e. On the Main Topology, right-click the NE and choose NE Explorer from the shortcut menu. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Flow Management from the Function Tree. Then click Click the CAR Configuration tab. Click New. Set the CAR attributes in the New CAR dialog box, according to the completed CAR planning and the description of CAR parameters. Click OK. The Operation Result dialog box is displayed, indicating that the CAR is successfully created. .
Step 2 Cause 2: The flow type does not match the service type. Re-create a flow of the type (that is, port flow) that matches the service type. Then bind the flow with a CAR. 1. Re-create a flow. a. b. c. d. e. 2. On the Main Topology, right-click the NE and choose NE Explorer from the shortcut menu. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Flow Management from the Function Tree. Then click Click the Flow Configuration tab. Click New. Set the flow attributes in the New Flow dialog box, according to the completed flow planning and the description of flow parameters. Click OK. The Operation Result dialog box is displayed, indicating that the flow is successfully created. On the Main Topology, right-click the NE and choose NE Explorer from the shortcut menu. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Flow Management from the Function Tree. Then click c. d. Click the Flow Configuration tab. Select a flow for which you want to configure the binding. In the Bound Shaping, Bound CoS and Bound CAR tabs, select the Shaping ID, CoS ID and CAR ID respectively.
Bind the flow with a CAR. a. b.
5-56
5 MC-B1 to MC-B51
e. ----End
Click Apply. The Operation Result dialog box is displayed, indicating that the binding is successful.
5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4 Board
After the shaping function is enabled for egress port queues, the services are interrupted.
Product
l l l l l
Fault Type
l l
RPR Ethernet Fault
Symptom
Figure 5-12 shows the VCTRUNK-shared EVPL service between NE2 and NE3. Figure 5-12 Configuration of the VCTRUNK-shared EVPL service
PORT
PORT1
VLAN 12
VCTRUNK
PORT
PORT1
VLAN 12
D E
D E
PORT2
VLAN 34
VCTRUNK1
VC4-1:VC3-1~VC3-3 VC4-2:VC3-1~VC3-3
VCTRUNK1
PORT2
VLAN 34
SDH
VC4-1:VC3-1~VC3-3 VC4-2:VC3-1~VC3-3
NE2
NE3
Two pairs of users (D and D', and E and E') share the 300 Mbit/s bandwidth of VCTRUNK1. 1. 2. 3. 4. Create port flows for PORT1 and PORT2 separately. Create a CoS of the simple type. Groom the port flow of PORT1 to queue 1 of VCTRUNK1, and groom the port flow of PORT2 to queue 3 of VCTRUNK1. Enable the traffic shaping function for queue 3 of VCTRUNK1. Set the CIR to 300 Mbit/ s. Enable the traffic shaping function for queue 1 of VCTRUNK1. Use the default shaping parameter values.
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
Now if the traffic that enters PORT2 reaches a rate of 300 Mbit/s, the service of PORT1 is interrupted.
Cause Analysis
This problem has the following possible causes. 1. In this fault case, the priority of queue 3 is higher than the priority of queue 1. As a result, the packets of the higher priority queue 3 occupy the entire 300 Mbit/s bandwidth, and there is no remaining bandwidth for the lower priority queue 1. Consequently, the service between D and D' is interrupted. The shaping function is enabled for queue 1, but the shaping bandwidth is not set. As the default shaping bandwidth is 0, the service is interrupted.
2.
Procedure
Step 1 Cause 1: the priority of queue 3 is higher than the priority of queue 1. 1. Decrease the bandwidth of the higher priority queue 3. a. b. On the Main Topology, right-click the NE and choose NE Explorer from the shortcut menu. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Then click . c. Set the committed information rate and committed burst size for the port queue. Step 2 Cause 1: The shaping function is enabled for queue 1, but the shaping bandwidth is not set. 1. See Configuring Traffic Shaping (for N1EMS4/N1EGS4/N3EGS4/N1EAS2) to set the shaping bandwidth for queue 1. a. b. On the Main Topology, right-click the NE and choose NE Explorer from the shortcut menu. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Then click . c. ----End Select a queue (of a port) for which you want to enable the shaping function. Set relevant parameters for the queue.
Similar Problems
After a flow is bound with a CAR, the service is interrupted. The possible cause is that, although the CAR is enabled, the CIR and PIR (which are both 0 by default) are not set for the CAR.
5.44 MC-B44 Failing to Add ATM Connections into a Protection Group

After two connections are created, they cannot be added into a protection group. Hence, you need to configure the sink-source relation of the protection group.
5 MC-B1 to MC-B51
Product
l l l l l
Fault Type
l l
ATM/IMA Ethernet Fault
Symptom
After creating two connections, you fail to add them into the protection group.
Cause Analysis
l
For 1+1 protection type:
In the case of source protection, the working and protection links must have the same sink but different sources. In the case of sink protection, the working and protection links must have the same source but different sinks. In the case of source + sink protection, the working and protection links must have different sinks and different sources.
For 1:1 protection, the working and protection links must have different sinks and different sources.
Procedure
Determine the relation between the source and sink of the protection group. After changing the connections, add them into the protection group again. ----End
None
5.45 MC-B45 Displaying CAC Check Errors When Creating a Link

CAC check errors are displayed when you create a link. Hence, you need to delete the useless connections on the port.
Product
l
OptiX OSN 1500A/1500B

Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
l l l l
OptiX OSN 2500 OptiX OSN 3500 OptiX OSN 3500T(19-inch) OptiX OSN 7500
Fault Type
l l
Symptom
When you create a connection, a CAC check error is displayed. A connection fails to be created.
Cause Analysis
The boards support the CAC check function. If a link needs to be created, and if the sum of selected traffic rate and the traffic rate of all the existing links at the port exceeds the total bandwidth of the port, a CAC check error is displayed. Consequently, the link fails to be created.
Procedure
Make sure that the selected traffic rate is less than the remaining bandwidth of the port when you create a link. Delete the links that are not required at the port, and then create new links again. ----End
None
5.46 MC-B46 Failing to Create the 622 Mbit/s Service

The ATM 622 Mbit/s service fails to be created. You need to adjust the VCTRUNCK that is bound with VC-4.
Product
l l l l l
Fault Type
l l

5-60
5 MC-B1 to MC-B51
Symptom
The 622 Mbit/s service fails to be created.
Cause Analysis
The four bound VC4 virtual connections are in the first ATM processing unit. The source end or sink end of the created connection belong to the same external port. The bandwidth used at the source end and sink end is 622 Mbit/s x 2 = 1244 Mbit/s, which exceeds the maximum bandwidth of a single ATM processing unit.
Procedure
Step 1 Delete the VCTRUNK that is bound with VC4 timeslots 1 4. Step 2 Set up the VCTRUNK that is bound with VC4 timeslots 5 8. ----End
None
5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure
IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groups to match with associated VCTRUNKs.
Product
l l l l l
Fault Type
l l
Symptom
The principle of binding VCTRUNKs is met, but VCTRUNKS fail to be bound.
Cause Analysis
Mutual check relation exists between IMA groups and associated VCTRUNKs.
5 MC-B1 to MC-B51
Procedure
Step 1 If IMA groups are symmetrically configured, make sure that the mapping VCTRUNKs are symmetrical. Step 2 If VCTRUNKs are nonsymmetrical, make sure that the mapping IMA groups are nonsymmetrical. ----End
None
5.48 MC-B48 Failing to Create ATM Services

ATM services fail to be created, thus failing to realize the protection. You need to add the two connections into the protection group.
Product
l l l l l
Fault Type
l l
Symptom
After you create two connections that have the same source but different sinks, or that have the same sink but different sources, the service of a connection fails to be created. The service fails to be created. The protection fails to be achieved accordingly.
Cause Analysis
The second connection takes effect only after you add the two connections that have the same source but different sinks, or that have the same sink but different sources into the protection group.
Procedure
Add the two connections into the protection group. ----End
5 MC-B1 to MC-B51
None
5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group
IMA boards fail to be added into the DPS protection group, hence failing to realize the DPS protection.
Product
l l l l l
Fault Type
l l
Symptom
Boards fail to be added into the DPS protection group. The configuration of the DPS protection fails to be performed. The boards fail to be added into the DPS protection group.
Cause Analysis
IMA boards that are added into the DPS protection group must be inserted in the paired slots.
Procedure
Make sure that the IMA boards that are configured with DPS protection are set to the paired slots. ----End
None
Issue 01 (2008-07-30)
5-63
5 MC-B1 to MC-B51
5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured at the Same Time
Service becoming unavailable when the IMA protocol and VPRing protocol are configured at the same time. You need to rectify the faults at the opposite end.
Product
l l l l l
Fault Type
l l
Symptom
If the IMA protocol is configured for symmetrical operation, and if the VPRing protocol is configured for single-ended switching, the services are unavailable in the case of hybrid configuration. The services become unavailable.
Cause Analysis
The IMA protocol is configured for symmetrical operation, and the VPRing is configured for 1 +1 or 1:1 single-ended switching. In this case, if a switching event occurs to the VPRing protocol, and if the IMA protocol detects the failure for the opposite end to receive signals, the local end stops transmitting cells.
Procedure
Rectify the faults at the opposite end. ----End
None
5-64
Issue 01 (2008-07-30)
5 MC-B1 to MC-B51
5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes
When the Ethernet boards are interconnected, the test frame cannot function normally due to the inconsistent bearing modes.
Product
OptiX OSN 3500
Fault Type
l l
QoS Ethernet Fault
Symptom
When the N2EFS4 board is interconnected to the N1EFT8/R1EFT4/N1EFT8A board, the receive end fails to receive any test frame, and the transmit end fails to receive any response frame.
Cause Analysis
The N2EFS4 board transmits the test frames in Ethernet bearing mode, but the N1EFT8/ R1EFT4/N1EFT8A board supports GFP bearing mode only.
Procedure
Step 1 Before enabling the function of the test frame, check whether the bearing modes at the two interconnected ends are consistent.
l
For the board whose bearing mode of the test frame can be set and queried, you just need to query on the T2000. For the board whose bearing mode of the test frame cannot be set or queried, you need to refer to Table 5-4 to obtain its bearing mode.
Step 2 If the bearing modes of the boards at the two interconnected ends are inconsistent, change the bearing modes to be the same so that the test frame can function normally. ----End
Reference
Before transmitting test frames, ensure that the VC trunk port on which the function of the test frame is enabled, and that the corresponding cross-connection is configured. The bearing modes of the boards at the two interconnected ends must be consistent. The boards in equipment of different versions may support different bearing modes for the test frame. For detailed information, refer to Table 5-4.
5 MC-B1 to MC-B51
Table 5-4 Bearing modes of the boards in equipment of different versions. Board N1EFS0, N1EFS4, N2EFS0, N1EGS2, N2EGS2 Equipment Version OptiX NG-SDH V100R003 OptiX NG-SDH V100R005 OptiX NG-SDH V100R006 OptiX NG-SDH V100R007 OptiX NG-SDH V100R008 N4EFS0, N2EFS4 OptiX NG-SDH V100R003 OptiX NG-SDH V100R005 OptiX NG-SDH V100R006 OptiX NG-SDH V100R007 OptiX NG-SDH V100R008 J2EGT6 OptiX OSN 9500 V100R004 OptiX OSN 9500 V100R005 N1EAS2 N1EGT2, R1EFT4, N1EFT8 OptiX NG-SDH V100R008 OptiX NG-SDH V100R003 OptiX NG-SDH V100R005 OptiX NG-SDH V100R006 OptiX NG-SDH V100R007 OptiX NG-SDH V100R008 N1EFT8A OptiX NG-SDH V100R006 OptiX NG-SDH V100R007 OptiX NG-SDH V100R008 N1EMS4, N1EGS4 OptiX NG-SDH V100R004 OptiX NG-SDH V100R006 OptiX NG-SDH V100R007 OptiX NG-SDH V100R008 N3EGS4 OptiX NG-SDH V100R007C02 OptiX NG-SDH V100R008 N2EGS4A OptiX NG-SDH V100R004 OptiX NG-SDH V100R008
Bearing Mode Ethernet bearing mode
Ethernet bearing mode
Ethernet bearing mode, GFP bearing mode
GFP Bearing Mode
Ethernet bearing mode, GFP bearing mode GFP Bearing Mode
GFP Bearing Mode
GFP Bearing Mode
GFP Bearing Mode GFP Bearing Mode GFP Bearing Mode
5 MC-B1 to MC-B51
Board J5EGS8J5E AS1
Equipment Version OptiX OSN 9500 V100R005
Bearing Mode Ethernet bearing mode, GFP bearing mode
Issue 01 (2008-07-30)
5-67
Index
Index
A
alarm suppression report lower level alarm, 5-30 AU_AIS, B3_EXC, B3_SD, MSP switching, 5-41 AUX, EXT port, BD_STATUS, 5-40
O
OTDR, 5-20
S
SL64, BD_STATUS, HP_UNEQ, C2 byte, 5-37 SNCP over MSP, HP_UNEQ alarm, 5-21 SPQ4, TPS protection, working mode, 5-47 SYN_BAD, threshold-crossing of clock jitter, 120-ohm 2 MHz external clock, 5-48
B
BER, SSN2SL64, STM-64, V-64.2b, LC, 5-45
C
clock, BUS_ERR, UXCSB, 5-44 Clock, PS alarm, 5-23
X
XCE, extended subrack, BD_STASTUS, 5-36 XCS, active/standby switching, HSC_UNAVAIL, 5-33 XCS, ejector level on the front panel, 5-34
E
EXCAS, OOL alarm, clock, SSM protocol, 5-39 extended subrack, 5-42
G
grounding, bit error, 5-35 GSCC, DCC, D1D3, 5-25
H
HP_TIM, J1 byte, 5-46
I
interconnect failure of MSP switching, 5-27
J
J0 byte, J1 byte, HP_TIM, 5-29
M
MSP switching failure, 5-27 multi-mode, single-mode, EGS2, 5-24
Issue 01 (2008-07-30)
i-1

OSN 3500-00449022-Maintenance Cases (V100R008 - 01)

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

OSN 3500-00449022-Maintenance Cases (V100R008 - 01)

Diunggah oleh

Hak Cipta:

Format Tersedia

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 V100R008

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

2 Classification by Functions and Features..............................................................................2-1

3 Classification by Fault Phenomenon.....................................................................................3-1

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

5 MC-B1 to MC-B51...................................................................................................................... 5-1

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

About This Document

About This Document

Field Maintenance Engineer Network Monitoring Engineer System maintenance engineer

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This Document

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

2 Classification by Functions and Features

3 Classification by Fault Phenomenon

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

About This Document

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

Updates in Issue 01 (2008-07-30) Based on Product Version V100R008

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

1.1 OptiX OSN 1500

1.2 OptiX OSN 2500

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

1.3 OptiX OSN 3500

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

1.4 OptiX OSN 3500T (19inch)

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

1.5 OptiX OSN 7500

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

2 Classification by Functions and Features

Classification by Functions and Features

About This Chapter

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2 Classification by Functions and Features

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

2 Classification by Functions and Features

For cases concerning RPR, see the following:

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

OptiX OSN 7500/3500/3500T(19inch)/2500/1500 Maintenance Cases

3 Classification by Fault Phenomenon

Classification by Fault Phenomenon

About This Chapter

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

3 Classification by Fault Phenomenon