OSN 3500-00449022-Maintenance Cases(V100R008_01)

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

V100R008

Maintenance Cases

Issue 01

Date 2008-07-30

Part Number 00449022

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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 writtenconsent 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. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Classification by Products........................................................................................................1-11.1 OptiX OSN 1500.............................................................................................................................................1-21.2 OptiX OSN 2500.............................................................................................................................................1-21.3 OptiX OSN 3500.............................................................................................................................................1-31.4 OptiX OSN 3500T (19inch)............................................................................................................................1-41.5 OptiX OSN 7500.............................................................................................................................................1-5

2 Classification by Functions and Features..............................................................................2-12.1 LCAS...............................................................................................................................................................2-22.2 QoS..................................................................................................................................................................2-22.3 LPT..................................................................................................................................................................2-22.4 ETH-OAM......................................................................................................................................................2-22.5 ATM/IMA.......................................................................................................................................................2-22.6 RPR.................................................................................................................................................................2-22.7 QinQ................................................................................................................................................................2-3

3 Classification by Fault Phenomenon.....................................................................................3-13.1 Service Interruption.........................................................................................................................................3-23.2 Bit Error...........................................................................................................................................................3-23.3 Point Justification............................................................................................................................................3-23.4 Equipment Interconnection Failure.................................................................................................................3-23.5 Protection Switching Failure...........................................................................................................................3-23.6 ECC Fault........................................................................................................................................................3-33.7 Ethernet Fault..................................................................................................................................................3-33.8 Others..............................................................................................................................................................3-4

4 Classification by Alarms...........................................................................................................4-14.1 AU_AIS...........................................................................................................................................................4-24.2 B1_SD.............................................................................................................................................................4-24.3 B2_SD.............................................................................................................................................................4-24.4 B3_EXC..........................................................................................................................................................4-24.5 BD_STASTUS................................................................................................................................................4-24.6 ETH_LOS........................................................................................................................................................4-24.7 HP_TIM..........................................................................................................................................................4-3

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

Issue 01 (2008-07-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

4.8 HP_UNEQ.......................................................................................................................................................4-34.9 IN_PWR_ABN................................................................................................................................................4-34.10 LP_RDI.........................................................................................................................................................4-34.11 OOL...............................................................................................................................................................4-34.12 P_LOS...........................................................................................................................................................4-34.13 POWER_ABNORMAL................................................................................................................................4-34.14 R_LOS...........................................................................................................................................................4-44.15 SYN_BAD....................................................................................................................................................4-44.16 TEMP_OVER...............................................................................................................................................4-44.17 Others............................................................................................................................................................4-4

5 MC-B1 to MC-B51...................................................................................................................... 5-15.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm ....................................................................................5-75.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment Is Interconnected with RouterThrough 155 Mbit/s Optical Port..........................................................................................................................5-85.3 MC-B3 Timeslot Collision Occurs When Service Is Created.........................................................................5-95.4 MC-B4 Certain Bit Errors Are Reported on SDH Line................................................................................5-105.5 MC-B5 Interconnection with SONET Equipment Fails...............................................................................5-115.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE .....................................................5-125.7 MC-B7 Deleting PQ1 Boards on T2000 Fails..............................................................................................5-145.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is Switched to MainMode....................................................................................................................................................................5-145.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between Equipment IsAvailable.............................................................................................................................................................5-155.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings...............................................5-165.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long............................................................5-175.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm ...........................................................................5-185.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board Generates B1_SD and B2_SDAlarms.................................................................................................................................................................5-195.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR............................................................5-205.15 MC-B15 SNCP over MSP Switching Fails ................................................................................................5-215.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of Line Boards........5-235.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails .......................................5-245.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded.................................................5-255.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDM Equipment................5-275.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid.......................................................................................5-295.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm .........................................5-305.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm....................................................................5-325.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCS Board Results inResetting of All Boards.......................................................................................................................................5-335.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCS Board Is Not ClosedWhen Standby XCS Board Is Inserted................................................................................................................5-345.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding...........................................5-355.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board in ExtendedSubrack ...............................................................................................................................................................5-36

ContentsOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases

ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-07-30)

5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect Configuration............5-375.28 MC-B28 The EXCSA Board Reports the OOL Alarm...............................................................................5-395.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board....................................5-405.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a Low Value............5-415.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack...........................................5-425.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External Clock Signal Is Deteriorated.............................................................................................................................................................................5-445.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit Errors Exist on N2SL64 ...........5-455.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service.......................................................................5-465.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration.............................................5-475.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2 MHz External Clock IsConfigured...........................................................................................................................................................5-485.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service ......5-495.38 MC-B38 Extra-Short Detagged Packet Discarded......................................................................................5-505.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss......................................................5-515.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections.................................................5-525.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode...............................................5-545.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR.......................................5-555.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Port of the N1EMS4Board...................................................................................................................................................................5-575.44 MC-B44 Failing to Add ATM Connections into a Protection Group.........................................................5-585.45 MC-B45 Displaying CAC Check Errors When Creating a Link................................................................5-595.46 MC-B46 Failing to Create the 622 Mbit/s Service.....................................................................................5-605.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure.............................................................................................................................................................................5-615.48 MC-B48 Failing to Create ATM Services..................................................................................................5-625.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group.......................................................5-635.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing Protocol Are Configured atthe Same Time.....................................................................................................................................................5-645.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes..............................................5-65

Index.................................................................................................................................................i-1

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


iii

Figures

Figure 5-1 Topology of the transmission network.............................................................................................5-13Figure 5-2 Networking diagram.........................................................................................................................5-22Figure 5-3 Networking diagram of the SDH network........................................................................................5-23Figure 5-4 Networking diagram.........................................................................................................................5-27Figure 5-5 Inter-board alarm suppression relations............................................................................................5-31Figure 5-6 Suppression relations among key alarms..........................................................................................5-32Figure 5-7 Two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500..........................................5-38Figure 5-8 Cable connection between the main subrack and the extended subrack..........................................5-44Figure 5-9 Incorrect fiber connections...............................................................................................................5-52Figure 5-10 Correct fiber connections................................................................................................................5-53Figure 5-11 Unidirectional point-to-point EPL service from PORT1 to PORT2..............................................5-55Figure 5-12 Configuration of the VCTRUNK-shared EVPL service................................................................5-57

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


v

Tables

Table 5-1 DCC allocation modes of the OptiX OSN 3500................................................................................5-26Table 5-2 Fiber connection between the NEs.....................................................................................................5-28Table 5-3 Transmitted and received K1/K2 bytes..............................................................................................5-28Table 5-4 Bearing modes of the boards in equipment of different versions......................................................5-66

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


vii

About This Document

PurposeThis document lists 51 cases of actual project maintenance and provides four entries of caseclassification: classified by products, classified by faults, classified by alarms, and classified byfunctions and features. You can find the desired cases quickly with a proper entry ofclassification.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX OSN 7500 V100R008


OptiX OSN 3500T (19inch) V100R008



OptiX iManager T2000 V200R006C03

Intended AudienceThe intended audiences of this document are:

l Field Maintenance Engineer

l Network Monitoring Engineer

l System maintenance engineer

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


1

OrganizationThis document is organized as follows.

Chapter Description

1 Classification by Products When the entry of classification by products is selected,the cases of faults of the OptiX OSN 7500, OptiX OSN3500, OptiX OSN 3500T (19inch), OptiX OSN 2500, andOptiX OSN 1500 are listed separately.

2 Classification by Functionsand Features

When the entry of classification by functions and featuresis selected, the cases of LCAS, cases of QoS, cases of LPT,cases of Eth-OAM, cases of ATM/IMA, cases of RPR, andcases of QinQ are listed separately.

3 Classification by FaultPhenomenon

When the entry of classification by faults is selected, thecases of service interruption, cases of bit errors, cases ofabnormal pointer justification, cases of equipmentinterconnection faults, cases of protection switching faults,cases of ECC faults and cases of Ethernet faults are listedseparately.

4 Classification by Alarms When the entry of classification by alarms is selected, thecases of faults indicated by common alarms such asR_LOS are listed separately.

5 MC-B1 to MC-B51 Lists all the cases, that is, case 1 to case 51.

Conventions

Symbol Conventions

The following symbols may be found in this document. They are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk which, if notavoided, will result in death or serious injury.

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

CAUTIONIndicates a potentially hazardous situation that, if notavoided, could cause equipment damage, data loss, andperformance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or saveyour time.

About This DocumentOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases

2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-07-30)

Symbol Description

NOTE Provides more information to emphasize or supplementimportant points of the main text.

General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. Forexample, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] areoptional.

{ x | y | ... } Alternative items are grouped in braces and separated byvertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square bracketsand separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated byvertical bars. A minimum of one or a maximum of all canbe selected.

GUI Conventions


Boldface Buttons, menus, parameters, tabs, window, and dialog titles are inboldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. Forexample, choose File > Create > Folder.

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


3

Keyboard OperationFormat Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means thethree keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keysshould be pressed in turn.

Mouse OperationAction Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly withoutmoving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certainposition.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 01 (2008-07-30) Based on Product Version V100R008This document of the V100R008 version is of the first release.

About This DocumentOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases

4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-07-30)

1 Classification by Products

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

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 1 Classification by Products


1-1

1.1 OptiX OSN 1500

For the cases concerning the OptiX OSN 1500, see the following:

l 5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm

l 5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When EquipmentIs Interconnected with Router Through 155 Mbit/s Optical Port

l 5.3 MC-B3 Timeslot Collision Occurs When Service Is Created

l 5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line

l 5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-Connect Service

l 5.38 MC-B38 Extra-Short Detagged Packet Discarded

l 5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot Loss

l 5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber Connections

l 5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer Mode

l 5.44 MC-B44 Failing to Add ATM Connections into a Protection Group

l 5.45 MC-B45 Displaying CAC Check Errors When Creating a Link

l 5.46 MC-B46 Failing to Create the 622 Mbit/s Service

l 5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, HenceCausing the Binding Failure

l 5.48 MC-B48 Failing to Create ATM Services

l 5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection Group

l 5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRingProtocol Are Configured at the Same Time

1.2 OptiX OSN 2500


l 5.5 MC-B5 Interconnection with SONET Equipment Fails

l 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails

l 5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXLBoard Is Switched to Main Mode







1 Classification by ProductsOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-07-30)







1.3 OptiX OSN 3500


l 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE

l 5.9 MC-B9 Fibers Are Not Connected Between Equipment but ECC CommunicationBetween Equipment Is Available

l 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings

l 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long

l 5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS Alarm

l 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 BoardGenerates B1_SD and B2_SD Alarms

l 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR

l 5.15 MC-B15 SNCP over MSP Switching Fails

l 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnectionof Line Boards

l 5.17 MC-B17 As Multi-mode Port Uses Single-Mode Fibers, Interconnection Fails

l 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded

l 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDMEquipment

l 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid

l 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm

l 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm

l 5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of MainXCS Board Results in Resetting of All Boards

l 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of MainXCS Board Is Not Closed When Standby XCS Board Is Inserted

l 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding

l 5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication ofAUX board in Extended Subrack

l 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to IncorrectConfiguration

l 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm



1-3

l 5.29 MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board

l 5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Setto a Low Value

l 5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack

l 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because ExternalClock Signal Is Deteriorated

l 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit ErrorsExist on N2SL64

l 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service

l 5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect Configuration






l 5.42 MC-B42 Failure in Restricting the Bandwidth After Binding flows to the CAR

l 5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at theEgress Port of the N1EMS4 Board








l 5.51 MC-B51 Failure of the Test Frame Due to the Inconsistent Bearing Modes

1.4 OptiX OSN 3500T (19inch)

For the cases concerning the OptiX OSN 3500T (19inch), see the following:







1 Classification by ProductsOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)







1.5 OptiX OSN 7500


l 5.36 MC-B36 SYN_BAD Alarm Is Reported on Entire Network After 120-Ohm 2MHz External Clock Is Configured















1-5

2 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

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 2 Classification by Functions and Features


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 Cross-Connect Service

2.2 QoS

For cases concerning QoS, see the following:



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:








2.6 RPR

2 Classification by Functions and FeaturesOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

For cases concerning RPR, see the following:




2.7 QinQ

For cases concerning QinQ, see the following:

5.38 MC-B38 Extra-Short Detagged Packet Discarded

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 2 Classification by Functions and Features


2-3

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

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 3 Classification by Fault Phenomenon


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 EquipmentIs Interconnected with Router Through 155 Mbit/s Optical Port

l 5.11 MC-B11 P_LOS Alarm Is Generated Because Cable Is Too Long

l 5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of MainXCS Board Is Not Closed When Standby XCS Board Is Inserted

3.2 Bit Error

For cases concerning bit error, see the following:

l 5.4 MC-B4 Certain Bit Errors Are Reported on SDH Line

l 5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBE

l 5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 BoardGenerates B1_SD and B2_SD Alarms

l 5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper Grounding

l 5.33 MC-B33 Receive Optical Power Is Normal But a Large Number of Bit ErrorsExist on N2SL64

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 MHzExternal Clock Is Configured

3.4 Equipment Interconnection Failure

For cases concerning an equipment interconnection failure, see the following:

l 5.5 MC-B5 Interconnection with SONET Equipment 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 CXLBoard Is Switched to Main Mode

3 Classification by Fault PhenomenonOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

l 5.15 MC-B15 SNCP over MSP Switching Fails

l 5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnectionof Line Boards

l 5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500 Interconnects with WDMEquipment



l 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 CommunicationBetween Equipment Is Available

l 5.10 MC-B10 ECC Communication Is Available Between Two Isolated Rings

l 5.18 MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded





3.7 Ethernet Fault

For cases concerning an ECC fault, see the following:

l 5.1 MC-B1 T2000 Reports Abnormal ETH_LOS Alarm

l 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service









OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 3 Classification by Fault Phenomenon


3-3








3.8 Others

For cases concerning other faults, see the following:

l 5.3 MC-B3 Timeslot Collision Occurs When Service Is Created

l 5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails

l 5.14 MC-B14 SDH Board Is Damaged Due to Misoperation on OTDR


l 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalid

l 5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN Alarm

l 5.22 MC-B22 PIU Board Reports POWER_ABNORMAL Alarm

l 5.28 MC-B28 The EXCSA Board Reports the OOL Alarm

3 Classification by Fault PhenomenonOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

4 Classification by Alarms

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

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 4 Classification by Alarms


4-1

4.1 AU_AIS

For cases concerning the AU_AIS alarm, see the following:



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 GeneratesB1_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 GeneratesB1_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 aLow Value

4.5 BD_STASTUS

For cases concerning the BD_STASTUS alarm, see the following:




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 Classification by AlarmsOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

4.7 HP_TIMFor cases concerning the HP_TIM alarm, see the following:

l 5.20 MC-B20 Settings of J0 and J1 Bytes Are Invalidl 5.34 MC-B34 HP_TIM Alarm Is Generated in Ethernet Service

4.8 HP_UNEQFor cases concerning the HP_UNEQ alarm, see the following:

l 5.15 MC-B15 SNCP over MSP Switching Failsl 5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to Incorrect

Configuration

4.9 IN_PWR_ABNFor 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_RDIFor cases concerning the LP_RDI alarm, see the following:

5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment IsInterconnected with Router Through 155 Mbit/s Optical Port

4.11 OOLFor cases concerning the OOL alarm, see the following:

5.28 MC-B28 The EXCSA Board Reports the OOL Alarm

4.12 P_LOSFor 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_ABNORMALFor cases concerning the POWER_ABNORMAL alarm, see the following:



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 ExternalClock 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 Reportedon 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 AbnormalBecause B3_EXC Threshold Is Set to a Low Value.

HSC_UNAVAIL

For cases concerning the HSC_UNAVAIL alarm, see the following:


l 5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because ExternalClock Signal Is Deteriorated

4 Classification by AlarmsOptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

RPR_PS_CHANGEFor cases concerning the RPR_PS_CHANGE alarm, see 5.39 MC-B39 RPR NetworkSwitching Due to VCTRUNK Timeslot Loss.



4-5

5 MC-B1 to MC-B51

About This Chapter

5.1 MC-B1 T2000 Reports Abnormal ETH_LOS AlarmThe EFS4 boards at certain stations report the ETH_LOS alarm after the cross-connections ofthe FE services are added or deleted. This fault can be rectified by disabling the unused MACports.

5.2 MC-B2 Incorrect Settings of Path Overheads Result in Failure When Equipment IsInterconnected with Router Through 155 Mbit/s Optical PortWhen the OptiX OSN 1500 is connected to the 155 Mbit/s optical port of the router of companyC, the LP_RDI alarm is generated in the 2 Mbit/s service. The relevant analysis shows that thehigher order path overheads of the line board are in the pass-through state, which results in theservice interruption. Hence, the overhead mode must be correctly set before a higher orderservice is changed to a lower order service.

5.3 MC-B3 Timeslot Collision Occurs When Service Is CreatedAn incorrect VC-12 timeslot numbering scheme is used. Therefore, timeslot collision occurswhen a VC-3 service is created. Hence, you need to perform the service configuration accordingto 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 LineWhen optical ports of different types are interconnected, certain bit errors are reported on theSDH line. Hence, when connecting the fibers, ensure that the optical ports to be interconnectedare of the same type.

5.5 MC-B5 Interconnection with SONET Equipment FailsThe OptiX OSN equipment fails to interconnect with the SONET equipment. Check the relevantinformation. It is found that all the optical interface boards must be of the N2 series and that thepass-through services must be configured at the 3xAU-3 level. Otherwise, the interconnectionfails.

5.6 MC-B6 High Temperature Causes PQ1 to Abnormally Report LPBBEWhen the temperature is very high, the cross-connect board constantly reports the temperaturealarm. 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 rangeduring the routine maintenance.

5.7 MC-B7 Deleting PQ1 Boards on T2000 Fails

OptiX OSN 7500/3500/3500T(19inch)/2500/1500Maintenance Cases 5 MC-B1 to MC-B51


5-1

When you delete the PQ1 boards on the T2000, you also need to delete the correspondinginterface boards. Otherwise, deleting the tributary boards may fail.

5.8 MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board IsSwitched to Main ModeAfter the standby CXL board is switched to the main mode, the communication between theequipment and the NMS fails. Check the relevant information. It is found that the MAC addressof 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 BetweenEquipment Is AvailableThe fibers between the three independent subnetworks are not connected but the ECCcommunication is available. Check the relevant information. It is found that the OSIcommunication protocol is enabled by default and thus the routes are automatically created. Inthis 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 RingsDuring 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 LongWhen the routed cable exceeds the maximum cable length supported by the equipment, theP_LOS alarm is generated. Hence, it is recommended that the cable length is maintained within50 meters. Otherwise, the services may be affected.

5.12 MC-B12 SEP1 Board Keeps Reporting AU_AIS AlarmThe J1 and C2 bytes of the interconnected equipment are inconsistent. Hence, the SEP1 boardkeeps reporting the AU_AIS alarm. Hence, you need to ensure that the overhead bytes are setto be consistent for the interconnected equipment.

5.13 MC-B13 In the Case of Fiber Cut, Optical Power Is Normal but SL16 Board GeneratesB1_SD and B2_SD AlarmsThe optical signal on the 1310 nm wavelength band is beyond the end wavelength of the G.655fiber. Hence, in certain cases where the G.655 fiber is used to transmit an optical signal on the1310 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 OTDRWhen the optical time domain reflectormeter (OTDR) is used to check the fibers, the opticalports on the SDH board are damaged because the routing connection is incorrect. Hence, youneed to ensure that the test distance and the routing connection are correct when you use theOTDR for testing fibers.

5.15 MC-B15 SNCP over MSP Switching FailsIn the case of SNCP over MSP, a switching fails due to the setting of the SNCP switchingconditions. To solve this problem, set the HP_UNEQ alarm as a trigger condition of the SNCPswitching.

5.16 MC-B16 Abnormal Alarms Are Reported on Station in the Case of Misconnection of LineBoardsAbnormal 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-B51OptiX OSN 7500/3500/3500T(19inch)/2500/1500

Maintenance Cases


Issue 01 (2008-07-30)

The mode of the optical module on the board that is configured with the services is differentfrom the fiber mode. Hence, the board fails to work normally. Note to ensure that the mode ofthe 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 UpgradedConnection between the equipment is interrupted when the SCC board is upgraded, because thenew SCC board supports fewer DCC channels than the original SCC board. Hence, note to ensurethat 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 WDMEquipmentThe 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 byteduring the networking process.

5.20 MC-B20 Settings of J0 and J1 Bytes Are InvalidThe 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 J1bytes.

5.21 MC-B21 After R_LOS Is Suppressed, Board Reports IN_PWR_ABN AlarmIf the higher level alarm R_LOS of an unused optical port is suppressed, the lower level alarmIN_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 AlarmThe PIU board reports the POWER_ABNORMAL alarm. To clear this alarm, re-set the jumpersof the SCC board.

5.23 MC-B23 After Main XCS Board Is Switched to Standby Mode, Resetting of Main XCSBoard Results in Resetting of All BoardsIf the main and standby XCS boards are inserted and removed repeatedly, all the boards will bereset in the case of switching when the standby XCS board is not activated. Hence, do not insertand remove the main and standby XCS board repeatedly and check whether the services maybe affected before you perform switching for the main and standby XCS boards if theHSC_UNAVAIL is reported on the standby XCS board.

5.24 MC-B24 Services Are Interrupted Because Ejector Lever on Front Panel of Main XCSBoard Is Not Closed When Standby XCS Board Is InsertedIf 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 XCSboard into a subrack where the services are activated, ensure that the ejector lever on the frontpanel of the main CXS board is in the closed state.

5.25 MC-B25 Bit Errors Occur in Lower Order Path Due to Improper GroundingTo clear bit errors that occur due to loose connection of the PGND cable, reconnect the PGNDcable.

5.26 MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX boardin Extended SubrackThe XCE board in the extended subrack is faulty. As a result, the communication between theextended subrack and the main subrack becomes abnormal. To solve this problem, replace theXCE board.

5.27 MC-B27 N2SL64 Board Repeatedly Reports HP_UNEQ Alarm Due to IncorrectConfiguration



5-3

When the N2SL64 board is off-service, data cannot be downloaded to the N2SL64 board. Whenthe N2SL64 board reports the BD_STATUS, do not create any service.

5.28 MC-B28 The EXCSA Board Reports the OOL AlarmThe 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 BoardThe 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 incorrectlyconnects the EXT ports.

5.30 MC-B30 MSP Ring Switching Is Abnormal Because B3_EXC Threshold Is Set to a LowValueThe B3_EXC and B3-SD thresholds are manually lowered. As a result, the services areinterrupted during the MSP switching test. To solve this problem, modify the B3_EXC andB3_SD thresholds to the default values.

5.31 MC-B31 Anomalies Occur After Main Subrack Becomes Extended SubrackThe 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. Asa 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 obtainthe IDs.

5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERR Alarm Because External ClockSignal Is DeterioratedThe head of the external signal input cable is faulty, and then the external clock signal isdeteriorated. As a result, the UXCSB board repeatedly reports the BUS_ERR alarm. To solvethis 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 onN2SL64Bit errors occur on the STM-64 signal board in a long-distance project, due to the impacts ofthe 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 ServiceNormally, the J1 byte to be transmitted and the J1 byte to be received in the higher order pathshould be the same. The HP_TIM alarm is generated on the EGT2 and EFS0 boards. To solvethis problem, manually set the J1 byte to be received and the J1 byte to be transmitted to thesame values.

5.35 MC-B35 SP14 Board Fails to Execute TPS Due to Incorrect ConfigurationThe working mode of the SPQ4 board is set incorrectly. As a result, the TPS fails. To solve theproblem, 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 ExternalClock Is ConfiguredThe 120-ohm 2 MHz external clock is set as the clock source. As a result, the SYN_BAD alarmis reported on the entire network where the OptiX OSN 7500 is the gateway NE, and the network-wide clock jitter exceeds the threshold.

5.37 MC-B37 LCAS Negotiation Abnormal if Bound Paths Configured Prior to Cross-ConnectServiceWhen the LCAS function is not enabled on either the source NE or the sink NE, LCASnegotiation faults arise and the LCAS configuration fails if the bound path is configured before


Maintenance Cases


Issue 01 (2008-07-30)

the cross-connect service is configured. You can rectify the fault by deleting the existingconfigurations at both ends and enabling the LCAS function at both ends.

5.38 MC-B38 Extra-Short Detagged Packet DiscardedIf certain packets are discarded in a network that employs the QinQ function, you can solve theproblem by adding bytes to short packets.

5.39 MC-B39 RPR Network Switching Due to VCTRUNK Timeslot LossThe VCTRUNK timeslot loss may result in RPR network switching. In this case, delete thedamaged timeslots from the configuration.

5.40 MC-B40 RPR Network Interruption Due to Incorrect Fiber ConnectionsIncorrect fiber connections may result in RPR network interruption. In this case, connect thefibers correctly and re-configure the cross-connections.

5.41 MC-B41 LPT Switching Fails Due to Inconsistency of LPT Bearer ModeIf 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 CARA flow is created after the relevant Ethernet service is created. After the flow is bound with aCAR, it is found that the CAR does not take effect. (On the instrument, the transmit bandwidthis equal to the receive bandwidth.)

5.43 MC-B43 Service Interruption After Enabling Queue Shaping Function at the Egress Portof the N1EMS4 BoardAfter 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 GroupAfter two connections are created, they cannot be added into a protection group. Hence, youneed to configure the sink-source relation of the protection group.

5.45 MC-B45 Displaying CAC Check Errors When Creating a LinkCAC check errors are displayed when you create a link. Hence, you need to delete the uselessconnections on the port.

5.46 MC-B46 Failing to Create the 622 Mbit/s ServiceThe ATM 622 Mbit/s service fails to be created. You need to adjust the VCTRUNCK that isbound with VC-4.

5.47 MC-B47 Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causingthe Binding FailureIMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groupsto match with associated VCTRUNKs.

5.48 MC-B48 Failing to Create ATM ServicesATM services fail to be created, thus failing to realize the protection. You need to add the twoconnections into the protection group.

5.49 MC-B49 Failing to Add IMA Boards into the DPS Protection GroupIMA boards fail to be added into the DPS protection group, hence failing to realize the DPSprotection.

5.50 MC-B50 Service Becoming Unavailable When the IMA Protocol and VPRing ProtocolAre Configured at the Same TimeService becoming unavailable when the IMA protocol and VPRing protocol are configured atthe 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-5

When the Ethernet boards are interconnected, the test frame cannot function normally due to theinconsistent bearing modes.


Maintenance Cases


Issue 01 (2008-07-30)

5.1 MC-B1 T2000 Reports Abnormal ETH_LOS AlarmThe EFS4 boards at certain stations report the ETH_LOS alarm after the cross-connections ofthe FE services are added or deleted. This fault can be rectified by disabling the unused MACports.

ProductOptiX OSN 1500

Fault Typel ETH-OAM

l Ethernet Fault

l ETH-LOS

SymptomThe network management (NM) center adds and deletes certain cross-connections of FE serviceswhen adjusting certain FE services between the nodes. After the services are adjusted, the EFS4boards at certain stations report the ETH_LOS alarm.

Cause AnalysisDuring the service adjustment, the ETH_LOS alarm is generated after services are added ordeleted. 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 doesnot 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 deletedduring 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 alarmis generated, and check the port attributes of the corresponding EFS4 board. It is found thatEnable port of the deleted service is set to Enable. At this time, however, the client-side signalsare 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 theETH_LOS alarm is cleared.

Step 5 Check all the Ethernet boards on which the ETH_LOS alarm is generated. It is found that thisalarm occurs due to the same causes. Set Enable port to Disable for the boards on which theEthernet services are already deleted. Then, the ETH_LOS alarm is cleared.

----End

Reference InformationFor details on the parameter Enable port, see the Parameter References.



5-7

5.2 MC-B2 Incorrect Settings of Path Overheads Result inFailure When Equipment Is Interconnected with RouterThrough 155 Mbit/s Optical Port

When the OptiX OSN 1500 is connected to the 155 Mbit/s optical port of the router of companyC, the LP_RDI alarm is generated in the 2 Mbit/s service. The relevant analysis shows that thehigher order path overheads of the line board are in the pass-through state, which results in theservice interruption. Hence, the overhead mode must be correctly set before a higher orderservice is changed to a lower order service.


Fault Typel Service Interruption

l LP_RDI

SymptomDuring network expansion, the SLQ1 board of the OptiX OSN 1500 is connected directly to theoptical card of the router of company C. The network is configured with 1+1 linear multiplexsection protection (MSP). One end of the MSP line is the 2 Mbit/s service and the other end isthe 155 Mbit/s optical service. The LP_RDI alarm is reported in the 2 Mbit/s service.

Cause AnalysisCheck the optical transmission paths, timeslot interconnection, and the modes of the overheadsof the SDH boards.

Procedure

Step 1 After you confirm that the physical connections are normal, the SLQ1 board and the optical cardof the router of company C receive and transmit signals normally but the link status of the routerof company C is down.

Step 2 Query the alarm. It is found that no abnormal alarms are generated on the SLQ1 board, but theLP_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 thatthe LP_RDI alarm in the 2 Mbit/s service is cleared. It indicates that the optical transmissionpaths are normal.

Step 4 Perform outloop at the optical port that is interconnected to the SLQ1 board. It is found that thelink status of the router of company C is up. In this case, it is suspected that the fault exists inthe interconnection.

Step 5 Check the relevant information. It is found that the first VC-12s of the VC-4s on the SLQ1 boardcarry the services and that the first VC-12s of the VC-4s on the router of company C carry theservices. Add a 2 Mbit/s service in the twenty-second VC-12 on the SLQ1 board that corresponds


Maintenance Cases


Issue 01 (2008-07-30)

to the second VC-12 on the router of company C. It is found that the LP_RDI persists in the 2Mbit/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 isinterconnected to the SLQ1 board at the local end is a VC-4 service. Delete this VC-4 serviceand add a VC-12 service. In this case, the overhead mode should be Termination. Query theoverhead mode. It is found that the actual overhead mode is Pass-Through. Then, change theoverhead mode to Termination. It is found that the LP_RDI alarm is cleared and that the servicesare normal.

----End

Reference InformationWhen you configure a lower order service, the higher order path overheads must be set to theTerminal mode. Otherwise, the services may be interrupted.

5.3 MC-B3 Timeslot Collision Occurs When Service IsCreated

An incorrect VC-12 timeslot numbering scheme is used. Therefore, timeslot collision occurswhen a VC-3 service is created. Hence, you need to perform the service configuration accordingto the selected VC-12 timeslot numbering scheme when creating a VC-12/VC-3 service.


Fault TypeConfiguration_Problem

SymptomCreate VC-12 services 1–15 one after another in the STM-1 frame. Then, create a VC-3 servicein the second VC-3 of the STM-1 frame. It is found that an alarm is generated to report thetimeslot collision.

Cause AnalysisThe sequential mode (ITU-T) is used as the VC-12 timeslot numbering scheme. Hence, the 15VC-12 services occupy the second VC-3. Then, timeslot collision is reported when you createthe 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 ITU-T or Interleaved as the VC-12 timeslot numbering scheme.



5-9

Step 3 Create the services according to the selected VC-12 timeslot numbering scheme.

----End

Reference Information

When you create a VC-12/VC-3 service on the T2000, configure the service according to theselected VC-12 timeslot numbering scheme. The following VC-12 timeslot numbering schemesare available:

1. Sequential mode (ITU-T): The VC-12 timeslots that are numbered 1, 4, 7, 10, and so onbelong to the first VC-3, the VC-12 timeslots that are numbered 2, 5, 8, 11, and so on belongto the second VC-3, and so on.

2. Interleaved mode: The VC-12 timeslots numbered 1–21 belong to the first VC-3, and theVC-12 timeslots numbered 22–43 belong to the second VC-3, and so on.

5.4 MC-B4 Certain Bit Errors Are Reported on SDH LineWhen optical ports of different types are interconnected, certain bit errors are reported on theSDH line. Hence, when connecting the fibers, ensure that the optical ports to be interconnectedare 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. The24-hour BER test is performed on the SDH line for three times. Each time the BER test isperformed, the SDH analyzer reads certain B3 bit errors and unavailable seconds (UASs). Checkthe 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 CXLboard in slot 4 of the OptiX OSN 1500 with the CXL board in slot 5 of the CXL board in slot4. It is found that the 24-hour BER test can be passed.

----End


Maintenance Cases


Issue 01 (2008-07-30)

5.5 MC-B5 Interconnection with SONET Equipment FailsThe OptiX OSN equipment fails to interconnect with the SONET equipment. Check the relevantinformation. It is found that all the optical interface boards must be of the N2 series and that thepass-through services must be configured at the 3xAU-3 level. Otherwise, the interconnectionfails.

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 theN2SLQ1 boards, on which one STM-1 optical port is added to support the interconnectionbetween the OptiX OSN 2500 and the SONET equipment. The pass-through services on theMSP ring are configured at the VC-4 level. Connect the analyzer to the OptiX OSN 2500 andthe SONET equipment. It is found that the analyzer shows normal test results. Interconnect theOptiX OSN 2500 and the SONET equipment, perform the test again, and then find that thecorresponding ports of the equipment on both the sides report AIS and that the services areunavailable.

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 ofthe OptiX OSN 2500 and the SONET equipment are consistent, whether the OptiX OSN 2500and the SONET equipment has any restrictions on interconnection, or whether any specialconfigurations are required.

Procedure

Step 1 Check the relevant information. It is found that the SDH service configuration is correct, thatthe N2-series boards are auto-adaptive in interconnecting with the SONET equipment, and thatthe 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 usedfor interconnection and that the boards on the line side are N1-series boards. Then, it is confirmedthat 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 MSPring 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-seriesoptical interface boards. Note that the pass-through services must be configured at the 3xAU-3level, not at the VC-4 level, in the case of interconnection with the SONET equipment.



5-11

Step 5 When the pass-through services on the entire transmission link are configured at the 3xAU-3level, the services are normal and the interconnection between the OptiX OSN equipment andthe SONET equipment is successful.

----End

Reference InformationThe N2-series optical interface boards on the OptiX OSN equipment can interconnect with theSONET equipment only when the following conditions are met:

1. All the line boards must work with N2-series optical interface boards (for example theN2SL64, N2SL16, and N2SQ1 boards), instead of the Q2SL16 and Q2SL4 boards.

2. 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 AbnormallyReport LPBBE

When the temperature is very high, the cross-connect board constantly reports the temperaturealarm. 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 rangeduring the routine maintenance.


Fault Typel Bit Error

l TEMP_OVER

SymptomAs shown in Figure 5-1, NE1 is the gateway NE and only convergence services are configuredbetween NE1 and other NEs. The clock source of NE1 is the external clock source, and otherNEs trace the west line clock source. When the services between NE1 and NE6 becomeabnormal, 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, thehistory alarms show that NE6 reports the TEMP_OVER alarm within a period of time.


Maintenance Cases


Issue 01 (2008-07-30)

Figure 5-1 Topology of the transmission network

1

2

3 4

5 6

we

w

e

ew e

w

w

e

BITS

Cause Analysis

If NE1 and NE6 report performance events, the fault may exist on NE1, NE5, or NE6. In thiscase, you can locate the fault by performing loopback. If NE6 reports the temperature alarm, theambient temperature may be very high, and thus the PQ1 or EXCSA board becomes faulty.

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 thefault may exist on NE5 or NE6.

Step 2 Perform outloop for the SL16 board in slot 6, and then the performance events on NE1 arecleared. After the outloop is released, the performance events are generated again. It indicatesthat the fault may exist on NE6.

Step 3 Replace the original PQ1 and SL16 boards on NE6 with the corresponding standby boards, butthe performance events persist.

Step 4 It indicates that the cross-connect unit is fault. Hence, replace the EXCSA board. Then, theperformance events are cleared. The air-conditioner on NE6 is faulty. Then, the ambienttemperature becomes very high in the narrow equipment room, and as a result damages the cross-connect unit.

----End



5-13

5.7 MC-B7 Deleting PQ1 Boards on T2000 FailsWhen you delete the PQ1 boards on the T2000, you also need to delete the correspondinginterface boards. Otherwise, deleting the tributary boards may fail.


Fault TypeOthers

SymptomOn the OptiX OSN 2500, one PQ1 board is inserted in slot 13, which is protected by the otherPQ1 board in slot 5. The PQ1 board in slot 13 needs to be deleted. Firstly, the TPS protectiongroup 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 thatthe service source cannot be released and the error code is "39492". The NE software is5.27.01.16 and the board software of the PQ1 is 1.17.

Cause AnalysisYou may fail to delete the PQ1 board on the T2000 in the following cases:l The PQ1 board may belong to a TPS protection group.

l The PQ1 board is configured with services.

l 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 TPSprotection 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 configuredwith any services or paths.

Step 3 It is found that the PQ1 board in slot 5 does not have the corresponding interface board, and canbe deleted. Then, Check the relevant information. It is found that the PQ1 board in slot 13 hastwo D12S interface boards in slot 17 and slot 18. Delete the two interface boards, and then thePQ1 board in slot 13 is successfully deleted.

----End

5.8 MC-B8 Communication Between Equipment and NMSFails After Standby CXL Board Is Switched to Main Mode

After the standby CXL board is switched to the main mode, the communication between theequipment and the NMS fails. Check the relevant information. It is found that the MAC address


Maintenance Cases


Issue 01 (2008-07-30)

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.


Fault TypeProtection Switching Failure

SymptomThe OptiX OSN 2500 forms an STM-4 ring, where there is one gateway NE. During theacceptance test, the standby CXL4 board is switched to the main mode, and then thecommunication between the NEs and the NMS fails but the corresponding alarms are notreported.

Cause AnalysisThe software of the standby CXL board may be different from the software of the main CXLboard or the DCN may be faulty.

ProcedureStep 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 thesame.

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 stillchanged 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, thecommunication is restored to normal.

----End

5.9 MC-B9 Fibers Are Not Connected Between Equipmentbut ECC Communication Between Equipment Is Available

The fibers between the three independent subnetworks are not connected but the ECCcommunication is available. Check the relevant information. It is found that the OSIcommunication protocol is enabled by default and thus the routes are automatically created. Inthis case, to isolate the three subnetworks, you need to disable the OSI communication protocol.


Fault TypeECC Fault



5-15

Symptom

The OptiX OSN 3500 forms three independent rings: north ring, southeast ring, and southwestring. The fiber connection is unavailable between the three rings. Three sets of equipment onthe three rings are respectively connected to the hub through a network cable. The hub isconnected to the NM computer. Check the ECC routing. Log in to an NE on the north ring andquery the ECC routing. It is found that the ECC can be connected to the equipment on the othertwo rings. The fiber connection, however, is unavailable between the three rings. Log in to anNE on the southeast and southwest rings respectively, and find the same fault exists. Theextended ECC is disabled at the gateway NEs on the three rings. Normally, the NEs on the threerings 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 gatewayNE.

Procedure

Step 1 Check whether the fibers are correctly connected. Remove the network from the gateway NEon 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 thenetwork from the gateway NE on the southeast ring to the hub. At this time, only the gatewayNE 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 andsoutheast 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 supportsthe OSI communication protocol. Hence, the OSI protocol is enabled at the network port bydefault. That is, when the equipment is interconnected through a hub, the corresponding routesare automatically created. Disable the OSI protocol of the gateway NE and then the ECCcommunication between the subnetworks becomes unavailable. All the NEs can log in to NEson the same ring only.

----End

5.10 MC-B10 ECC Communication Is Available BetweenTwo 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


Maintenance Cases


Issue 01 (2008-07-30)

SymptomThe OptiX OSN 3500 forms two rings: north ring and south ring. The two rings are isolatedfrom each other. The north and south rings are connected to the NMS in the central equipmentroom through a hub for centralized monitoring. Check the ECC routing of the NE. It is foundthat the ECC routes between the north ring and the south ring are abnormally available.

Cause AnalysisThe 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.l 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 southrings is correct.

Step 2 Check the ECC routing. The OptiX OSN equipment is newly deployed. Thus, the extended ECCfunction is not preset and is in the default mode. That is, the AUX board automatically enablesthe extended ECC function. Disable the extended ECC function. It is found that the ECCcommunication between the north and south rings is unavailable.

----End

5.11 MC-B11 P_LOS Alarm Is Generated Because Cable IsToo Long

When the routed cable exceeds the maximum cable length supported by the equipment, theP_LOS alarm is generated. Hence, it is recommended that the cable length is maintained within50 meters. Otherwise, the services may be affected.


Fault Typel Service Interruption

l P_LOS

SymptomThe OptiX OSN equipment provides a client with a VC-3 service. This service is mapped fromthe PL3 board to the SL64 board. The client complained that the PL3 board continues to reportthe P_LOS alarm for more than 30 seconds and the services were affected.

Cause AnalysisThe possible causes are as follows:



5-17

l The interface board PL3 is faulty or the PL3 board is not inserted properly into the slot.

l The equipment grounding is improper.

l The connection of the DDF is loosened.

l The cable routed from the DDF to the equipment exceeds the maximum cable lengthsupported by the equipment.

Procedure

Step 1 Check the interface board that corresponds to the PL3 board. It is found that the interface boardis 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 iscorrect.

Step 3 Check the length of the cable routed from the DDF to the equipment. It is found that the cablelength exceeds 70 meters. In this case, adjust the position of the equipment to ensure that thecable 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 AlarmThe J1 and C2 bytes of the interconnected equipment are inconsistent. Hence, the SEP1 boardkeeps reporting the AU_AIS alarm. Hence, you need to ensure that the overhead bytes are setto be consistent for the interconnected equipment.

Product

OptiX OSN 3500

Fault Typel Equipment Interconnection Failure

l AU_AIS

Symptom

The OptiX OSN 3500 is configured with the SEP1 board. After the OptiX OSN 3500 isinterconnected with the data equipment from another manufacturer, the SEP1 board keepsreporting the AU_AIS alarm.

Cause Analysis

When the OptiX OSN 3500 interconnects with third-party data equipment, the J1 and C2 bytesof the OptiX OSN 3500 may be inconsistent with the J1 and C2 bytes of the third-party dataequipment.

Procedure

Step 1 Log in to the T2000 and select NE Explorer.


Maintenance Cases


Issue 01 (2008-07-30)

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 bytetransmitted from the interconnected equipment and find the J1 and C2 bytes are inconsistentwith the default values of the J1 and C2 bytes of the OptiX OSN 3500. In this case, modify thevalues 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 IsNormal but SL16 Board Generates B1_SD and B2_SDAlarms

The optical signal on the 1310 nm wavelength band is beyond the end wavelength of the G.655fiber. Hence, in certain cases where the G.655 fiber is used to transmit an optical signal on the1310 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 Typel Bit Error

l B1_SD

l B2_SD

Symptom

The client replaces the fiber, checks the optical power and finds that the optical power is withinthe normal range but the SL16 board reports the B1_1SD and B2_SD alarms. After all therelevant 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 theoptical 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 biterrors disappear.

Step 2 Check the models of the optical interface board and the fiber. It is found that the optical interfaceboard operates on the 1310 nm wavelength band. Before the cutover, the G.652 fiber is usedwhereas after the cutover, the G.655 fiber is used. The G.652 fiber can transfer optical signalson the 1310 nm and 1550 nm wavelength bands whereas the G.655 fiber can transfer only optical



5-19

signals on the 1550 nm wavelength band. The 1310 nm wavelength band is beyond the endwavelength 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 onthe 1310 wavelength band. In terms of the technical specifications, however, the optical signalon 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 usingthe G.655 fiber.

5.14 MC-B14 SDH Board Is Damaged Due to Misoperationon OTDR

When the optical time domain reflectormeter (OTDR) is used to check the fibers, the opticalports on the SDH board are damaged because the routing connection is incorrect. Hence, youneed to ensure that the test distance and the routing connection are correct when you use theOTDR for testing fibers.

Product

OptiX OSN 3500

Fault Type

Others

SymptomUse the OTDR to test the fiber between NE A and NE B. The fiber length between NE A andNE B is 105 km. NE A and NE B are configured with the SSN1SL1602 boards (with the L-16.2Jeport). The test distance of the OTDR is set to 100 km and the OTDR is connected to test thefiber between NE A and a place 5 km away from NE B. During the connection between theOTDR 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 NEB, that is, the routing connection is incorrect. Hence, the power transmitted from the OTDR tothe L-16.2Je port exceeds the overload receive power of the L-16.2Je port. As a result, theL-16.2Je port is damaged.

Procedure

Replace the damaged board with a new board.

----End


Maintenance Cases


Issue 01 (2008-07-30)

Reference InformationNote 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 theequipment. Otherwise, misoperations may occur during later maintenance.

l Determine the required test distance and check the connection of the ODF when you usethe OTDR.

l Remove the fiber jumpers from the line board when you use the OTDR to test fibers.

l In the case of long-distance optical ports, ensure that the routing connection is correct. Theoverload receive power of a long-distance optical port is low and thus may be damaged bythe optical power that exceeds the overload receive power in the case of routingmisconnection.

5.15 MC-B15 SNCP over MSP Switching FailsIn the case of SNCP over MSP, a switching fails due to the setting of the SNCP switchingconditions. To solve this problem, set the HP_UNEQ alarm as a trigger condition of the SNCPswitching.


Fault Typel Protection Switching Failure

l HP_UNEQ

SymptomFigure 5-2 shows an SNCP over MSP ring.



5-21

Figure 5-2 Networking diagram

OptiXOSN 3500

OptiXOSN 9500

NE2

OptiXOSN 3500

NE3 OptiXOSN 9500

NE5

OptiXOSN 3500

NE1

NE4

NE1, NE2, NE3, NE4, and NE5 form an MSP ring, with an STM-1 chain An SNCP service iscreated between NE1 and NE3. The working source of this VC-4 service is on the working pathof the MSP protection group and the protection source is on the STM-1 link. The SNCP hold-off time is 100 ms. When a fiber cut occurs for the first time (between NE1 and NE2), the MSPswitching 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 AnalysisWhen a fiber cut occurs for the second time, check the SNCP switching status. The SNCPswitching of NE1 is in the normal state, which is the reason why the SNCP switching does notoccur. 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 iscreated on NE4 and thus the problem occurs. All the VC-4 signals are unavailable and then thedownstream NEs report the HP_UNEQ alarm.

ProcedureSet 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


Maintenance Cases


Issue 01 (2008-07-30)

5.16 MC-B16 Abnormal Alarms Are Reported on Station inthe 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.


Fault Typel Protection Switching Failurel APS_INDI

SymptomFigure 5-3 shows a 4xVC-4 SDH ring configured with path protection (PP).

Figure 5-3 Networking diagram of the SDH network

16

54

3

BIT

2

NE1 is the central station and the services of other stations are converged on NE1. The clocksource of NE1 is the external clock source, and other NEs trace the west line clock source. Thefiber between NE2 and NE3 is cut but the services are not interrupted. At this time, pointadjustment performance events occur on NE1, NE3, NE4, NE5, and NE6. The PQ1 boards onNE1, NE3, NE5, and NE6 reports the PS alarm but no alarm is reported on NE4.



5-23

Cause AnalysisNormally, the PQ1 boards on NE3, NE4, NE5, and NE6 should report the PS alarm if the fiberbetween NE2 and NE3 is cut. The PQ1 board on NE4 does not report the PS but the servicesare normal. The west line board on NE4 can normally receive services from NE1. Hence, thefiber connection of NE4 may be incorrect. That is, the west line of NE4 is connected to the westline of NE5 and the east line of NE4 is connected to the east line of NE3.

ProcedureCheck the fiber connection of NE4. It is found that the fibers are misconnected. After the fiberconnection 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 differentfrom the fiber mode. Hence, the board fails to work normally. Note to ensure that the mode ofthe optical module is the same as the fiber mode when you select the board.


Fault TypeOthers

SymptomThe N1EGS2 boards of the OptiX OSN 3500 are configured with services. One N1EGS2 boardcan 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 thetransmit optical power of the board that fails to work is –28 dBm.

Cause AnalysisOne N1EGS2 board can work and the other N1EGS2 board fails to work. This problem mayoccur due to inconsistency between the type of the optical port on the N1EGS2 board and thefiber type.

Procedure

Step 1 Check the model of the optical board. It is found that the board that can be configured withservices is the N1EGS211 and that the board that cannot be configured with services is theN1EGS210. 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 opticalport of which the transmit optical power is –9.5 dBm, the sensitivity is –17 dBm, the workingwavelength is 850 nm, and the overload power is not specified, and that the N1EGS211 board


Maintenance Cases


Issue 01 (2008-07-30)

adopts a single-mode optical port of which the transmit optical power is –9 dBm, the sensitivityis –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 originalfiber jumpers with multi-mode fiber jumpers. Then, the transmit optical power becomes normaland the services are normally received and transmitted.

----End

5.18 MC-B18 ECC Connection Is Interrupted When SCCBoard Is Upgraded

Connection between the equipment is interrupted when the SCC board is upgraded, because thenew SCC board supports fewer DCC channels than the original SCC board. Hence, note to ensurethat 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. Afterthe replacement, however, the ECC connection between the OptiX OSN 3500 and otherequipment is interrupted.

Cause Analysis

The ECC connection between the two sets of equipment is interrupted. The possible causes areas follows:

l The DCC protocol is changed after the replacement.

l The DCC configuration is incorrect.

l 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 thuscan work normally.

Step 2 After replacing the N1SCC with the N1GSCC, the ECC connection is interrupted. Check theused 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 D1–D3 channels.



5-25

Step 4 Remove the two SLT1 boards, and then power on the equipment. The SL64 boards occupy theDCC channels first, and the ECC connection is restored.

----End

Reference InformationBefore you replace the SCC board, check the DCC channels to ensure that the new SCC boardcan 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 N1GSCC N3GSCC/N4GSCC

Channel type Supports the D1–D3 and D4–D12 channel types.

Operationmode

Mode 1 Supports 40 D1–D3 channels. Supports 160 D1–D3channels.

Mode 2 Supports 10 D1–D3 channels.Supports 10 D4–D12channels.

Supports 40 D1–D3 channels.Supports 40 D4–D12channels.

Mode 3 Supports 22 D1–D3 channels.Supports 6 D4–D12 channels.


Mode 4 Supports 28 D1–D3 channels.Supports 4 D4–D12 channels.


Mode 5 - Supports 8 D1–D3 channels.

Mode 6 - Supports 10 D1–D3 channels.

Mode 7 - Supports 70 D1–D3 channels.Supports 30 D4–D12channels.

Mode 8 - Supports 100 D1–D3channels.Supports 20 D4–D12channels.

Protocol type Supports the HWECC, IP, and OSI protocols.

Default mode Mode 1


Maintenance Cases


Issue 01 (2008-07-30)

5.19 MC-B19 MSP Switching Fails When OptiX OSN 3500Interconnects 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 byteduring the networking process.



SymptomFour OptiX OSN 3500 NEs form an MSP ring, as shown in Figure 5-4.

Figure 5-4 Networking diagram

STM-16 Two-fiberbidirectional MSP ring

NE 144

NE 141

NE 142

NE 143

Table 5-2 shows fiber connection between the NEs.



5-27

Table 5-2 Fiber connection between the NEs

Local End Opposite End

NEName

Slot BoardName

Port NEName

Slot BoardName

Port

NE141 7 N1SL16 1IN NE144 12 N1SL16 1OUT

NE141 7 N1SL16 1OUT NE144 12 N1SL16 1IN







During the MSP ring switching test, only NE-143 and NE-144 are successfully switched andswitching for the other NEs fails.

Cause AnalysisAll the K1/K2 bytes received at the west board (7-SL16) on NE-144 are "0". As a result, NE-144and the downstream NEs fail to receive the K1/K2 byte from the east board (12-SL16) onNE-143. Hence, it is determined that NE-143 and NE-144 may be faulty. Table 5-3 lists thereceived and transmitted K1/K2 bytes.

Table 5-3 Transmitted and received K1/K2 bytes

NE-144 K1/K2 KC KM NE-143 k1/k2 KC KM

Transmitted K1/K2 byte

0x0230 0xcd 0xd3 Transmitted K1/K2 byte

0x0320 0xdc 0xd3

Received K1/K2byte

0x0000 0xff 0xff Received K1/K2byte

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-143transmits any K1/K2 bytes whose values are "0x0000". In addition, the KC and KM bytes areabnormal. 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 thatWDM equipment is located between NE-143 and NE-144. Hence, it is suspected that the WDMequipment changes the K1/K2 byte from NE-143 to NE-144. At the same time, WDM equipmentin other segments may also affect the K1/K2 bytes, especially the KC and KM bytes.


Maintenance Cases


Issue 01 (2008-07-30)

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 isas follows: #144-7-------SDH analyzer 1-------WDM equipment------- SDH analyzer2-------#143-12.

2. Shut down the laser on the board in slot 7 on NE-144. Then, MSP switching occurs.

3. Record the K1, K2, KC, and KM bytes that are read from SDH analyzer 1 and SDH analyzer2. 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.

Procedure

Modify the MSP ring into an SNCP ring and then perform the SNCP switching. The switchingis normal.

----End

5.20 MC-B20 Settings of J0 and J1 Bytes Are InvalidThe 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 J1bytes.

Product

OptiX OSN 3500

Fault Typel 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 theT2000 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, andthe 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 highestbits of the first byte and the other bytes must be "1" and "0" respectively. In addition, the otherseven bits of the first byte are generated due to the result of a CRC-7 calculation over the previousframe. That is, the first bits of the J0 and J1 bytes do not need to be set manually. The value "00B8 F5 17 12 EF 78 13 62 74 05 29 C1 6B" does not comply with the previous rule and hence isinvalid.



5-29

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 Valid J0 byte to be Received, Error code is 38718.

l Valid J1 byte to be Received, Error code is 38717.

l Valid J0 byte to be Sent, Error code is 38677.

l 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 3500Intelligent Optical Transmission System Configuration Guide.

5.21 MC-B21 After R_LOS Is Suppressed, Board ReportsIN_PWR_ABN Alarm

If the higher level alarm R_LOS of an unused optical port is suppressed, the lower level alarmIN_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 Typel R_LOS

l IN_PWR_ABN

Symptom

In an OSN project, the OptiX OSN 3500 and OptiX OSN 1500 form an SNCP ring. Three opticalports on the N1SLQ1 of the OptiX OSN 3500 are not used. Hence, the R_LOS alarm issuppressed 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 higherlevel alarm are reported. For example, after the R_LOS alarm is suppressed, the IN_PWR_ABNalarm is reported.


Maintenance Cases


Issue 01 (2008-07-30)

ProcedureSuppress the IN_PWR_ABN alarm.

----End

Reference InformationWhen you suppress an alarm, note that the lower level alarms that are suppressed by this alarmwill 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 TU_AIS V5_VCAIS DOWN_T1_AIS C2_VCAIS

A BFor example: means A suppresses B

Figure 5-6 shows the suppression relations among key alarms.



5-31

Figure 5-6 Suppression relations among key alarmsR_LOS

R_LOF

J0_MM MS_AIS B1_EXC B2_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 LP_TIM LP_SLM BIP_SD

For example: A B means A suppresses B

BIP_EXC

TU_AIS TU_LOP

5.22 MC-B22 PIU Board Reports POWER_ABNORMALAlarm

The PIU board reports the POWER_ABNORMAL alarm. To clear this alarm, re-set the jumpersof the SCC board.

Product

OptiX OSN 3500

Fault Typel POWER_ABNORMAL

Symptom

The PWRB indicator on the N1GSCC board of the OptiX OSN 3500 is on. The T2000 reportsthe POWER ABNORMAL alarm. The voltage in the second path is –54 V±20%. After the twopower 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 theSCC board is sent to the field.

The J17 and J16 jumpers on the N1GSCC board are used to control the input voltage of theequipment.


Maintenance Cases


Issue 01 (2008-07-30)

l Remove the jumper cap: The equipment adopts the power supply whose input voltage is –60 V.

l Maintain the jumper cap: The equipment adopts the power supply whose input voltage is–48 V.

WARNINGIn areas other than in Russia, insert the jumper cap and the equipment adopts the –48 V powersupply.

Procedure

To clear the alarm, re-set the jumpers according to the OptiX OSN 3500 N1GSCC BoardDeployment Guide.

----End


For setting the jumpers on the SCC board, see the OptiX OSN 3500 Intelligent OpticalTransmission System Installation Guide.

5.23 MC-B23 After Main XCS Board Is Switched to StandbyMode, Resetting of Main XCS Board Results in Resetting ofAll Boards

If the main and standby XCS boards are inserted and removed repeatedly, all the boards will bereset in the case of switching when the standby XCS board is not activated. Hence, do not insertand remove the main and standby XCS board repeatedly and check whether the services maybe affected before you perform switching for the main and standby XCS boards if theHSC_UNAVAIL is reported on the standby XCS board.

Product

OptiX OSN 3500


l 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 resetand cannot be restored to the original state.



5-33

Cause AnalysisWhen the standby XCS board starts to work, it needs to synchronize certain data with the mainXCS board. In the switching test, the main XCS board is reset before the standby XCS board inslot 9 starts to work. As a result, all the boards start to synchronize and the other boards on thesame subrack are reset.

ProcedureWait until the resetting of the boards is complete.

----End

Reference InformationIf the main XCS board is reset, or removed and then inserted back before the standby XCS boardstarts 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 theHSC_UNAVAIL alarm. When the HSC_UNAVAIL alarm is reported, it does not necessarilyindicate that the switching of the active and standby XCS boards is affected. TheHSC_UNAVAIL alarm is used to inform the user of not performing cold reset on the main XCSboard or not removing and then inserting the main XCS board back, thus preventing the servicesfrom being affected.

5.24 MC-B24 Services Are Interrupted Because Ejector Leveron Front Panel of Main XCS Board Is Not Closed WhenStandby 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 XCSboard into a subrack where the services are activated, ensure that the ejector lever on the frontpanel of the main CXS board is in the closed state.


Fault TypeService Interruption

SymptomInsert the standby XCS in the OptiX OSN 3500. If the ejector lever on the front panel of themain XCS in the current subrack is in the open state, in 30 seconds, the services are interruptedfor tens of seconds.

Cause AnalysisNone.


Maintenance Cases


Issue 01 (2008-07-30)

Procedure

Step 1 Before you insert an XCS board into a subrack, especially when the services are activated, ensurethat 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 theejector lever and then insert the standby XCS board.

----End

5.25 MC-B25 Bit Errors Occur in Lower Order Path Due toImproper Grounding

To clear bit errors that occur due to loose connection of the PGND cable, reconnect the PGNDcable.


Fault TypeBit Error

SymptomIn the transmission network, five sites form an MSP ring. The five sites are names as Site 1, Site2, Site 3, Site 4, and Site 5 in the counter-clockwise direction. Site 1 is the gateway NE. Only 2Mbit/s services are activated between Site 1 and other sites. The clock source of Site 1 is theexternal clock source, and the other sites trace the west line clock source. Query the alarms andperformance events. It is found that a large number of bit errors exist in the lower order path atSite 1, Site 2, and Site 3. At the same time, bit errors also exist in the lower order path at Site 4and Site 5.

Cause AnalysisIf 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 littleprobability that all the PQ1 boards at Site 1 are faulty. Then, it is suspected that the lineboard SL16 is faulty.

l The fan may be faulty. In this case, bit errors occur in the higher order path, which resultsin bit errors in the lower order path.

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

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. Fastenthe 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 inAbnormal Communication of AUX board in ExtendedSubrack

The XCE board in the extended subrack is faulty. As a result, the communication between theextended subrack and the main subrack becomes abnormal. To solve this problem, replace theXCE board.

Product

OptiX OSN 3500

Fault Typel ECC Fault

l BD_STASTUS

Symptom

The OptiX OSN 3500 is configured with an extended subrack. The AUX board on the extendedsubrack is abnormal. The communication over the EXT port fails. As a result, the main subrackfails 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 foundthat the STAT indicator is on and green, and that the other indicators are grey. The PQ1 boardsin the extended subrack report the BD_STASTUS alarm.

Cause Analysis

The possible causes are as follows:l The pins in the slots for the SCC (that is, slots 17 and 18) on the backplane in the extended

subrack are bent.l The pins in the slot for the AUX (that is, slot 37) on the backplane in the extended subrack

are bent.l The pins in the slots for the XCE (that is, slots 59 and 60) on the backplane in the extended

subrack are bent.l 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 thepins are normal but the fault persists.


Maintenance Cases


Issue 01 (2008-07-30)

Step 2 Remove the AUX board from the extended subrack. Check the pins in slot 37 on the backplanein 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 arenormal. 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_UNEQAlarm Due to Incorrect Configuration

When the N2SL64 board is off-service, data cannot be downloaded to the N2SL64 board. Whenthe N2SL64 board reports the BD_STATUS, do not create any service.



l HP_UNEQ

l BD_STASTUS

SymptomFigure 5-7 shows a two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500. Thenetworking topology is as follows: A (11-SL64)——(8-SL64) B (11-SL64)——(8-SL64) C(11-SL64)——D——A.



5-37

Figure 5-7 Two-fiber bidirectional STM-64 ring formed by the OptiX OSN 3500

A

C

DB

11

11

11

8

8

8

8

11

STM-64 Two-fiberbidirectional MSP ring

2-PQ1-1

2-PQ1-1

Create the E1 service from A (2-PQ1-1) to C (2-PQ1-1), and the E1 service occupies the firstVC-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". Thatis, the C2 byte transmitted from site A is different from the C2 byte received at site B.

Cause Analysis

The possible causes are as follows:l The services are incorrectly configured.

l 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_STATUSalarm.


Maintenance Cases


Issue 01 (2008-07-30)

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 AlarmThe 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 Typel OOL

l SYN_BAD

Symptom

The OOL alarms are generated irregularly. The last OOL alarm is generated when the mainEXCSA board is switched to the standby EXCSA board. The equipment where the EXCSAboard 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 OOLalarm indicates that the line clock of the input signal is not traced but is locked by the SDRphase-locked ring. The synchronization source of the EXCSA board is lost. Hence, thesynchronization alarm is generated.

Cause Analysis

The standard SSM protocol is enabled for the equipment that generates the alarms, but theextended SSM protocol is enabled for the other equipment on the network. As a result, the inputclock 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



5-39

5.29 MC-B29 Adding Boards Fails Due to Incorrect Use ofEXT 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 incorrectlyconnects the EXT ports.



l BD_STATUS

SymptomOne 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 SEP1board 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 AnalysisThe data configuration on the SCC board may be incorrect or the inter-board communicationmay be faulty.

Procedure

Step 1 Erase the database and then reset the SCC board. It is found that no reset record exists and thatall boards fail to be added.

Step 2 Erase the database on the SCC board again. Then, reset the SCC board on site, and add boardsagain. 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 theBD_STATUS alarm in an interrupted manner. The board type of the original SEP1 switchesbetween the PQ1 and the SEP1. The board type of the original EU08 board in slot 19 switchesbetween the EU08 and the D12S. In addition, the idle slot 20 is incorrectly shown to house theD12S board.

Step 4 Exchange the SCC board with the SCC in the corresponding extended subrack (OptiX OSN3500). 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 setsof OptiX OSN 3500. Remove the cable and then find that the problem is solved.

----End


Maintenance Cases


Issue 01 (2008-07-30)

Reference InformationThe EXT ports of the main subrack and the extended subrack can be connected only when theUCXSA board is configured to connect to the extended subrack. In this case, the alarms andconfiguration information of the extended subrack are transmitted to the SCC board in the mainsubrack through the EXT ports. The extended subrack need not be configured with the SCCboard and the XCE board.

When the extended subrack is connected to a non-protection chain, the main subrack andextended subrack are independent of each other. Hence, the EXT ports of the main subrack andthe extended subrack need not be connected. If the EXT ports are connected by a cable, collisionoccurs. As a result, boards fail to be added or cannot be smoothly added. In addition, even theboard type switches.

5.30 MC-B30 MSP Ring Switching Is Abnormal BecauseB3_EXC Threshold Is Set to a Low Value

The B3_EXC and B3-SD thresholds are manually lowered. As a result, the services areinterrupted during the MSP switching test. To solve this problem, modify the B3_EXC andB3_SD thresholds to the default values.



l B3_EXC

l AU_AIS

SymptomSix sets of OptiX OSN 3500 that are configured with the N2SL64 boards form a 10 Gbit/s MSPring. During the MSP ring switching test, the fiber is cut. The services, however, are notinterrupted and the MSP switching is normal. Reconnect the fiber. The switching is restoredafter 10 minutes. The services, however, are interrupted immediately and are automaticallyrestored in four minutes. At the same time, the optical board where switching is performed reportsthe B3_SD alarm. The B3_SD alarm lasts for two hours and then is automatically cleared. Checkon the T2000. It is found that the MSP switching is normal. Replace the XSC board. It is foundthat the fault persists.

Cause AnalysisThe problem occurs because the B3_EXC and B3_SD thresholds are lowered for the N2SL64board 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 defaultedto 1.0E-3 and the SD threshold is defaulted to 1.0E-6 for the OptiX OSN 3500. If the B3_EXCand B3_SD thresholds are lowered to 1.0E-8 and 1.0E-9 respectively, bit errors occur duringthe MSP ring switching. When the bit errors exceed the B3_EXC and B3_SD thresholds, thealarms are generated.



5-41

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 theB3_EXC threshold is set to 1.0E-8, the alarm generally lasts for about 15 minutes and then iscleared 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 OSNequipment. As a result, the services are interrupted after the MSP switching. When the B3_SDthreshold 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 WTRtime of 10 minutes plus service interruption of four minutes plus the time for reconnecting thefiber) 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 SubrackBecomes 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. Asa 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 obtainthe 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 theextended subrack to a newly created OptiX OSN 3500. Query the physical slots of the extendedsubrack. It is found that the boards in the extended subrack fail to be displayed and that thetributary boards in the extended subrack are displayed as off-service on the T2000.

Cause Analysis

The possible causes are as follows:

l The connection between the main subrack and the extended subrack is faulty.


Maintenance Cases


Issue 01 (2008-07-30)

l The SCC board in the main subrack and the AUX boards in the main subrack and in theextended subrack are faulty.

l The tributary boards in the extended subrack are not reset and thus the correct slot IDscannot be obtained.

Procedure

Step 1 Check the connection between the main subrack and the extended subrack. It is found that theconnection is normal.

Step 2 Perform warm reset on the SCC board and the AUX boards in the main subrack and in theextended 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 performcold reset. Then, the boards obtain the new slot IDs. The problem is solved.

----End

Reference InformationThe following part considers the UXCSB as the cross-connect board of the main subrack anddescribes 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 theUXCSB board in slot 9 are connected to the EXA ports on the XCE board in slots 59 and60. The EXA and EXB ports on the UXCSB board in slot 10 are connected to the EXBports on the XCE board in slots 59 and 60. See Figure 5-8.

l The EXT port on the AUX board in the main subrack is connected to the EXT port on theAUX board in the extended subrack. See Figure 5-8.

l Cover the J9 jumper on the AUX board in the main subrack with the jumper cap andmaintain the J9 jumper on the AUX board in the extended subrack uncapped.

l Do as follows to reconstruct a running main subrack into an extended subrack:

1. Remove the SCC board, line board, and certain unused tributary boards.2. Connect the EXT ports on the two AUX boards and remove the J9 jumper on the AUX

board in the extended subrack.3. Remove the two cross-connect boards.4. 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 cross-connections. 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 thenew slot IDs (that is, the original ID plus 50). After performing the operations, you neednot remove the tributary boards and then insert the boards back again after the configuration.



5-43

Figure 5-8 Cable connection between the main subrack and the extended subrack

Optix OSN3500

Optix OSN3500

A

Power distribution unit

B

EXA EXA

EXB EXB

EXB EXB

EXA EXA

Main subrack

Extendedsubrack

Extendedsubrack cables

Crossovernetwork cable

Extendedsubrack cables

CLK

1R

EV

F&f

F1

EX

TC

OM

ETH

CLK

2

A B

5.32 MC-B32 UXCSB Board Repeatedly Reports BUS_ERRAlarm Because External Clock Signal Is Deteriorated

The head of the external signal input cable is faulty, and then the external clock signal isdeteriorated. As a result, the UXCSB board repeatedly reports the BUS_ERR alarm. To solvethis problem, make a new head for the external clock signal input cable.


Fault Typel HSC_UNAVAIL

SymptomThe OptiX OSN 3500 at site A uses the UXCSB board to connect the extended subrack. Theclock signal used at site A is the external clock source. The OptiX OSN 3500 at site A forms an


Maintenance Cases


Issue 01 (2008-07-30)

MSP ring with other OptiX OSN 3500. The clocks of the other OptiX OSN 3500 trace the clocksource of site A.

The standby UXCSB board in slot 10 at site A repeatedly reports the BUS_ERR andHSC_UNAVAIL alarms. At the same time, the SYN_BAD alarm is generated in the network-wide clock signals but the services are not affected.

Cause AnalysisThe possible causes are as follows:l The communication cable between the main subrack and the extended subrack is not

properly connected or is damaged.l The UXCSB board in slot 10 is faulty.

l The external clock source is faulty.

Procedure

Step 1 Check the communication cable between the main subrack and the extended subrack and findthe 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 theproblem persists.

Step 3 Replace the UXCSB board in slot 10. It is found that the problem persists. Hence, the problemshould not be with the UXCSB board.

Step 4 The SYN_BAD alarm is generated in the network-wide clock signals and the clocks over theentire network trace the clock of site A. Hence, check the external clock cable of the equipmentat site A. It is found that the head of the external clock cable is loosely connected to the AUXboard. 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 theexternal clock cable is faulty.

Step 5 Make a new head for the external clock cable and then the alarms are cleared. The problem issolved.

----End

5.33 MC-B33 Receive Optical Power Is Normal But a LargeNumber of Bit Errors Exist on N2SL64

Bit errors occur on the STM-64 signal board in a long-distance project, due to the impacts ofthe 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.


Fault TypeBit Error



5-45

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 requiredDCU 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 poweris within the normal range. Since the DCU board is used, it is determined that the problem shouldnot be with the receive optical power or the DCU board. Compare the input power and the outputpower of the relevant BPA. It is found that the power of the pre-amplifier is –26.90 dBm. Thisis why the problem occurs.

The power of the laser on the STM-64 signal board should not exceed –27.00 dBm. When thepower 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 thenormal 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 dispersionand attenuation.

Step 3 Check the performance of the BPA. The input power of the two ports on the V-64.2b boardshould 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 (thedifference within 1 dBm to 3 dBm is normal). The excessive attenuation may be caused by thefiber connector, fiber, or fiber head.

----End


The STM-6 signal is sensitive. Hence, notice the sensitivity (use the BPA), dispersion (use theDCU) and distortion (the power of the laser should not be lower than –27 dBm) of the fiber inthe case of a long-distance project. Ensure that no bit error will be caused due to impacts of thesensitivity, dispersion and distortion of the fiber.

5.34 MC-B34 HP_TIM Alarm Is Generated in EthernetService

Normally, the J1 byte to be transmitted and the J1 byte to be received in the higher order pathshould be the same. The HP_TIM alarm is generated on the EGT2 and EFS0 boards. To solvethis problem, manually set the J1 byte to be received and the J1 byte to be transmitted to thesame values.


Maintenance Cases


Issue 01 (2008-07-30)


Fault Typel Ethernet Fault

l HP_TIM

SymptomWhen the Ethernet services are configured, the J1 byte to be received and the J1 byte to betransmitted are set to the same values. The HP_TIM alarm, however, is generated on the EGT2and EFS0 boards.

Cause AnalysisAfter the Ethernet services are configured, the Ethernet boards at both ends generate the HP_TIMalarm. Check the J1 byte in the single-byte mode on the overhead management interface on theT2000. It is found that the J1 byte to be received and the J1 byte to be transmitted are set to thesame values (displayed in hexadecimal). Check the J1 byte in the 16-byte mode. It is found thatthe J1 byte to be received and the J1 byte to be transmitted are set to different values. Changethe value of the J1 byte to be transmitted of the EGT2 or EFS0 board. It is found that the J1 bytereceived on the other board remains unchanged.

ProcedureSet the J1 byte to be received by the RX Ethernet board in the VC-4 on the SDH line board thatcorresponds to the TX Ethernet board. Then, the HP_TIM alarm is cleared.

----End

Reference InformationThe J1 byte to be received of the RX Ethernet board should be set in the VC-4 on the SDH lineboard that corresponds to the TX Ethernet board. Change the values of the J1 byte to betransmitted and the J1 byte to be received on the SDH line to prevent the HP_TIM alarm formbeing generated on the line.

5.35 MC-B35 SP14 Board Fails to Execute TPS Due toIncorrect Configuration

The working mode of the SPQ4 board is set incorrectly. As a result, the TPS fails. To solve theproblem, set the working modes of the working and protection SPQ4 boards correctly.





5-47

SymptomOn the OptiX OSN 3500, three SP14 boards form a TPS protection group. Slot 2 is the sot forthe protection board. Slots 3 and 4 are the slots for the working boards. During the PTS test, theTPS switching time is longer than 50 ms.

Cause AnalysisThe SPQ4 board can work in the 104 Mbit/s or 150 Mbit/s mode. The default working mode isthe 140 Mbit/s mode. Check the TPS configuration. It is found that the working mode of theprotection board in slot 2 is different from the working modes of the working boards in slots 3and 4. The SPQ4 board in slot 2 is set to the 140 Mbit/s mode whereas the SPQ4 boards in slots3 and 4 are set to the 150 Mbit/s mode.

ProcedureSet the SPQ4 in slot 2 to the 150 Mbit/s mode and then perform TPS. The TPS is successfullyperformed.

----End

Reference InformationWhen 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 EntireNetwork After 120-Ohm 2 MHz External Clock IsConfigured

The 120-ohm 2 MHz external clock is set as the clock source. As a result, the SYN_BAD alarmis reported on the entire network where the OptiX OSN 7500 is the gateway NE, and the network-wide clock jitter exceeds the threshold.


Fault TypePoint Justification

SymptomAfter the OptiX OSN 7500 is adopted as the gateway NE and the 120-ohm 2 MHz external clockis configured as the clock source, a large number of SYN_BAD alarms are reported on the entirenetwork and the network-wide clock jitter exceeds the threshold.

Cause AnalysisBecause of high receiver sensitivity of the 120-ohm 2 MHz port, environmental noise andimproper grounding of the OptiX OSN 7500 may result in amplification of noise in the 120-


Maintenance Cases


Issue 01 (2008-07-30)

ohm 2 MHz clock regeneration circuit and irregular reference clocks. If the OptiX OSN 7500traces these irregular reference clocks, violent clock frequency jitter occurs. The other NEs onthe ring trace the clock of the gateway NE. Hence, the SYN_BAD is reported on the entirenetwork and the clock jitter exceeds the threshold.

ProcedureAdopt one of the following methods to solve this problem:l Replace the 2 MHz external clock source with the 2 Mbit/s external clock source.l 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 porton the OptiX OSN 7500.

----End

Reference InformationHigh receiver sensitivity affects the circuit of the 120-ohm 2 MHz port only, and does not affectthe 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 asthe clock source when no external clock signal is accessed. Otherwise, the external clock sourceis 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 PathsConfigured Prior to Cross-Connect Service

When the LCAS function is not enabled on either the source NE or the sink NE, LCASnegotiation faults arise and the LCAS configuration fails if the bound path is configured beforethe cross-connect service is configured. You can rectify the fault by deleting the existingconfigurations at both ends and enabling the LCAS function at both ends.

Productsl OptiX OSN 1500A/1500B

l OptiX OSN 2500

l OptiX OSN 3500

l OptiX OSN 3500T (19inch)

l OptiX OSN 7500

Fault Typel LCAS

l Ethernet Fault

Case DescriptionFor the point-to-point NE A and NE B, the LCAS function is enabled at NE A but disabled atNE B. After the bound paths are configured for the data processing boards at both ends and thecross-connect service is configured from the data processing board to the line board, LCAS



5-49

negotiation at NE A becomes abnormal, that is, all the timeslots are deleted or only one timeslotremains.

Cause AnalysisThe fault arises owning to the version and working principles of the LCAS function. Hence, thefollowing situations should be prevented:

l The LCAS function is disabled at one end.

l 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 atboth 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 andthe line board.

Step 4 Configure the cross-connect service between the data processing board and the line board, andthen configure the bound paths. The alarm disappears, and the troubleshooting is complete.

----End

5.38 MC-B38 Extra-Short Detagged Packet DiscardedIf certain packets are discarded in a network that employs the QinQ function, you can solve theproblem by adding bytes to short packets.

Productsl OptiX OSN 1500A/1500B

l OptiX OSN 2500

l OptiX OSN 3500

l OptiX OSN 3500T (19 inch)

l OptiX OSN 7500

Fault Typel QinQ

l Ethernet Fault

Case DescriptionThe point-to-point protocol over Ethernet (PPPoE) client services enter a switch forconvergence. The converged services are accessed to an OptiX NE for transmission overnetworks to the broadband access server at the destination end. The PPPoE active discoverysession-confirmation (PADS) data packets in the downlink services returning from thebroadband server to the client side are lost. As a result, the PPPoE verification fails.


Maintenance Cases


Issue 01 (2008-07-30)

Cause Analysis

The PPPoE services include the PADI, PADO, PADR and PADS data packets. Compared withthe other types of data packets, the PADS data packet is only of a 64-byte length which is theminimum data packet length that the Ethernet supports.

After the QinQ function is configured, two tags are added without changing the original datapacket length: C-VLAN and S-VLAN. When the downlink services travel over the OptiX NEto the client-side NE, the external S-VLAN tag is detagged. Hence, the data packet lengthchanges 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. Inthis case, the PPPoE endpoint cannot receive the PADS data packet. As a result, the PPPoEverification fails and the services are not available.

Currently, some Ethernet boards are added with the short-packet length extension functionagainst 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 boardson the client side and system side to ensure that the data packet is transmitted at a lengthcompliant with the Ethernet specification.

5.39 MC-B39 RPR Network Switching Due to VCTRUNKTimeslot Loss

The VCTRUNK timeslot loss may result in RPR network switching. In this case, delete thedamaged timeslots from the configuration.

Productl OptiX OSN 1500A/1500B

l OptiX OSN 2500

l OptiX OSN 3500

l OptiX OSN 3500T(19inch)

l OptiX OSN 7500

Fault Typel RPR

l Ethernet Fault

l RPR_PS_CHANGE

Symptom

Services in the RPR network is connected. In this case, the RPR_PS_CHANGE alarm is reportedand the switching occurs in the RPR network.

Cause Analysis

The fault may be caused due to VCTRUNK timeslot loss.



5-51

Procedure

Step 1 Enable the LCAS protocol of the corresponding Ethernet board to check whether the timeslotswork normally. If some timeslots are damaged or fail, the LCAS protocol can delete the timeslotsfrom the VCTRUNK.

Step 2 Query and check whether the timeslots actually bound to the VCTRUNK and the timeslotsconfigured for the VCTRUNK are consistent. If not, it indicates that the damaged VC-4 timeslotsare 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 IncorrectFiber Connections

Incorrect fiber connections may result in RPR network interruption. In this case, connect thefibers correctly and re-configure the cross-connections.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel RPR

l Ethernet Fault

SymptomThe 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 AnalysisThe previous fault is caused due to incorrect fiber connections. In this case, ringlet0 receivespackets 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 adjacentnode of S3 is S1 rather than S2. Thus, the RPR_NB_INCONSIS alarm is reported.


Maintenance Cases


Issue 01 (2008-07-30)

Procedure

Step 1 Query the cross-connection configuration on each board to check whether there are cross-connections that are not completely configured on a board. Configure cross-connections fromthe 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 theinput and output interfaces of the optical modules match. Figure 5-10 shows links betweennodes. After fibers are connected properly, the alarm is cleared and the fault is rectified.

Figure 5-10 Correct fiber connections

S1 S2 S3

----End

Reference InformationThe steps of configuring Cross-Connections:

1. In the Main View, select the desired NE. Right-click the NE and choose NE Explorer fromthe shortcut menu.

2. Choose Configuration > SDH Service Configuration from the Function Tree.3. Click Create in the lower right of the window. The Create SDH Service dialog box is then

displayed.4. Set the parameters in the dialog box as follows:

l Level: VC-4

l Direction: Bidirectional

l Source Slot: 13-N2EGR2-1

l Click . In the Please select the source timeslot dialog box, set the followingparameters.– Port: 1

– Higher Order Timeslot: 1,3,5,7,9,11,13,15

l Sink Slot: 12-N2SL16-1(SDH-1)

l Sink Timeslot Range: 1 - 8

l Activate Immediately: Yes

l Then, click Apply.

5. Based on the operations in Step 4, set the parameters in the dialog box as follows:l Level: VC-4

l Direction: Bidirectional

l Source Slot: 13-N2EGR2-1

l Click . In the Please select the source timeslot dialog box, set the followingparameters.– Port: 1



5-53

– Higher Order Timeslot: 2,4,6,8,10,12,14,16

l Sink Slot: 7-N2SL16-1(SDH-1)

l Sink Timeslot Range: 1 - 8

l Activate Immediately: Yes

l Then, click Apply.

5.41 MC-B41 LPT Switching Fails Due to Inconsistency ofLPT 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.


l OptiX OSN 2500

l OptiX OSN 3500

l OptiX OSN 3500T (19-inch)

l OptiX OSN 7500

Fault Typel LPT

l Ethernet Fault

Symptom

In the case of version R006 or earlier than R006, LPT fails to work normally when the EFSboard 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 removedfrom 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 supportsthe 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.


Maintenance Cases


Issue 01 (2008-07-30)

5.42 MC-B42 Failure in Restricting the Bandwidth AfterBinding flows to the CAR

A flow is created after the relevant Ethernet service is created. After the flow is bound with aCAR, it is found that the CAR does not take effect. (On the instrument, the transmit bandwidthis equal to the receive bandwidth.)


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel QoS

l Ethernet Fault

Symptom

As shown in Figure 5-11, a unidirectional point-to-point EPL service is configured from PORT1to PORT2 on the same board.

Figure 5-11 Unidirectional point-to-point EPL service from PORT1 to PORT2

Ethernet serviceprocessing board

PORT1

PORT2

SmartBits

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 theSmartBits to transmit packets at a rate higher than 10 Mbit/s. The receive bandwidth of theinstrument, however, is found to be equal to the transmit bandwidth of the instrument.



5-55

Cause AnalysisThis problem has the following possible causes.

1. The CAR is not enabled. After the CAR is bound to the flow, the CAR is effective for theflow only if the CAR is enabled.

2. The flow type does not match the service type. In this fault case, a port flow should beconfigured for the point-to-point EPL service.

Procedure

Step 1 Cause 1: The CAR is not enabled.1. Enable the CAR.

a. On the Main Topology, right-click the NE and choose NE Explorer from the shortcutmenu.

b. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoSManagement > Flow Management from the Function Tree. Then click .

c. Click the CAR Configuration tab.d. Click New. Set the CAR attributes in the New CAR dialog box, according to the

completed CAR planning and the description of CAR parameters.e. 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 flowwith a CAR.

1. Re-create a flow.



c. Click the Flow Configuration tab.d. Click New. Set the flow attributes in the New Flow dialog box, according to the

completed flow planning and the description of flow parameters.e. Click OK. The Operation Result dialog box is displayed, indicating that the flow is

successfully created.2. Bind the flow with a CAR.



c. Click the Flow Configuration tab.d. 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 IDrespectively.


Maintenance Cases


Issue 01 (2008-07-30)

e. Click Apply. The Operation Result dialog box is displayed, indicating that thebinding is successful.

----End

5.43 MC-B43 Service Interruption After Enabling QueueShaping Function at the Egress Port of the N1EMS4 Board

After the shaping function is enabled for egress port queues, the services are interrupted.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel RPR

l 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

PORT1D

VLAN 1～2

E

PORT

PORT2

SDHVC4-1:VC3-1~VC3-3VC4-2:VC3-1~VC3-3

VCTRUNK

VCTRUNK1

PORT1 D’

E’

PORT

PORT2

NE2 NE3

VLAN 3～4VC4-1:VC3-1~VC3-3VC4-2:VC3-1~VC3-3

VCTRUNK1

VLAN 1～2

VLAN 3～4

Two pairs of users (D and D', and E and E') share the 300 Mbit/s bandwidth of VCTRUNK1.

1. Create port flows for PORT1 and PORT2 separately.2. 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.3. Enable the traffic shaping function for queue 3 of VCTRUNK1. Set the CIR to 300 Mbit/

s.4. Enable the traffic shaping function for queue 1 of VCTRUNK1. Use the default shaping

parameter values.



5-57

Now if the traffic that enters PORT2 reaches a rate of 300 Mbit/s, the service of PORT1 isinterrupted.

Cause AnalysisThis 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 thereis no remaining bandwidth for the lower priority queue 1. Consequently, the servicebetween D and D' is interrupted.

2. The shaping function is enabled for queue 1, but the shaping bandwidth is not set. As thedefault shaping bandwidth is 0, the service is interrupted.

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.


b. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoSManagement > 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.


b. Select the relevant Ethernet board in the Object Tree. Choose Configuration > QoSManagement > Port Shaping Management from the Function Tree. Then click

.c. Select a queue (of a port) for which you want to enable the shaping function. Set

relevant parameters for the queue.

----End

Similar ProblemsAfter a flow is bound with a CAR, the service is interrupted. The possible cause is that, althoughthe 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 aProtection Group

After two connections are created, they cannot be added into a protection group. Hence, youneed to configure the sink-source relation of the protection group.


Maintenance Cases


Issue 01 (2008-07-30)


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

SymptomAfter creating two connections, you fail to add them into the protection group.

Cause Analysisl For 1+1 protection type:

– In the case of source protection, the working and protection links must have the samesink but different sources.

– In the case of sink protection, the working and protection links must have the samesource but different sinks.

– In the case of source + sink protection, the working and protection links must havedifferent sinks and different sources.

l For 1:1 protection, the working and protection links must have different sinks and differentsources.

ProcedureDetermine the relation between the source and sink of the protection group. After changing theconnections, add them into the protection group again.

----End

Reference InformationNone

5.45 MC-B45 Displaying CAC Check Errors When Creatinga Link

CAC check errors are displayed when you create a link. Hence, you need to delete the uselessconnections on the port.




5-59

l OptiX OSN 2500

l OptiX OSN 3500

l OptiX OSN 3500T(19-inch)

l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

SymptomWhen you create a connection, a CAC check error is displayed. A connection fails to be created.

Cause AnalysisThe boards support the CAC check function. If a link needs to be created, and if the sum ofselected traffic rate and the traffic rate of all the existing links at the port exceeds the totalbandwidth of the port, a CAC check error is displayed. Consequently, the link fails to be created.

ProcedureMake sure that the selected traffic rate is less than the remaining bandwidth of the port whenyou create a link. Delete the links that are not required at the port, and then create new linksagain.

----End


5.46 MC-B46 Failing to Create the 622 Mbit/s ServiceThe ATM 622 Mbit/s service fails to be created. You need to adjust the VCTRUNCK that isbound with VC-4.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault


Maintenance Cases


Issue 01 (2008-07-30)

SymptomThe 622 Mbit/s service fails to be created.

Cause AnalysisThe four bound VC4 virtual connections are in the first ATM processing unit. The source endor sink end of the created connection belong to the same external port. The bandwidth used atthe source end and sink end is 622 Mbit/s x 2 = 1244 Mbit/s, which exceeds the maximumbandwidth 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


5.47 MC-B47 Mismatching Between MA Groups andAssociated VCTRUNKs, Hence Causing the BindingFailure

IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groupsto match with associated VCTRUNKs.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

SymptomThe principle of binding VCTRUNKs is met, but VCTRUNKS fail to be bound.

Cause AnalysisMutual check relation exists between IMA groups and associated VCTRUNKs.



5-61

Procedure

Step 1 If IMA groups are symmetrically configured, make sure that the mapping VCTRUNKs aresymmetrical.

Step 2 If VCTRUNKs are nonsymmetrical, make sure that the mapping IMA groups arenonsymmetrical.

----End


None

5.48 MC-B48 Failing to Create ATM ServicesATM services fail to be created, thus failing to realize the protection. You need to add the twoconnections into the protection group.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

Symptom

After you create two connections that have the same source but different sinks, or that have thesame 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 samesource but different sinks, or that have the same sink but different sources into the protectiongroup.

Procedure

Add the two connections into the protection group.

----End


Maintenance Cases


Issue 01 (2008-07-30)


5.49 MC-B49 Failing to Add IMA Boards into the DPSProtection Group

IMA boards fail to be added into the DPS protection group, hence failing to realize the DPSprotection.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

SymptomBoards 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 intothe DPS protection group.

Cause AnalysisIMA boards that are added into the DPS protection group must be inserted in the paired slots.

ProcedureMake sure that the IMA boards that are configured with DPS protection are set to the pairedslots.

----End




5-63

5.50 MC-B50 Service Becoming Unavailable When the IMAProtocol and VPRing Protocol Are Configured at the SameTime

Service becoming unavailable when the IMA protocol and VPRing protocol are configured atthe same time. You need to rectify the faults at the opposite end.


l OptiX OSN 2500

l OptiX OSN 3500


l OptiX OSN 7500

Fault Typel ATM/IMA

l Ethernet Fault

Symptom

If the IMA protocol is configured for symmetrical operation, and if the VPRing protocol isconfigured for single-ended switching, the services are unavailable in the case of hybridconfiguration.

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 endstops transmitting cells.

Procedure

Rectify the faults at the opposite end.

----End


None


Maintenance Cases


Issue 01 (2008-07-30)

5.51 MC-B51 Failure of the Test Frame Due to theInconsistent Bearing Modes

When the Ethernet boards are interconnected, the test frame cannot function normally due to theinconsistent bearing modes.

Product

OptiX OSN 3500

Fault Typel QoS

l Ethernet Fault

Symptom

When the N2EFS4 board is interconnected to the N1EFT8/R1EFT4/N1EFT8A board, thereceive end fails to receive any test frame, and the transmit end fails to receive any responseframe.

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 twointerconnected ends are consistent.

l For the board whose bearing mode of the test frame can be set and queried, you just need toquery on the T2000.

l For the board whose bearing mode of the test frame cannot be set or queried, you need torefer 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 thebearing 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 testframe 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 boardsin equipment of different versions may support different bearing modes for the test frame. Fordetailed information, refer to Table 5-4.



5-65

Table 5-4 Bearing modes of the boards in equipment of different versions.

Board Equipment Version Bearing Mode

N1EFS0,N1EFS4,N2EFS0,N1EGS2,N2EGS2

OptiX NG-SDH V100R003 Ethernet bearing mode

OptiX NG-SDH V100R005




N4EFS0,N2EFS4

OptiX NG-SDH V100R003 Ethernet bearing mode



OptiX NG-SDH V100R007 Ethernet bearing mode, GFP bearing mode


J2EGT6 OptiX OSN 9500 V100R004 GFP Bearing Mode


N1EAS2 OptiX NG-SDH V100R008 Ethernet bearing mode, GFP bearing mode

N1EGT2,R1EFT4,N1EFT8

OptiX NG-SDH V100R003 GFP Bearing Mode





N1EFT8A OptiX NG-SDH V100R006 GFP Bearing Mode



N1EMS4,N1EGS4





N3EGS4 OptiX NG-SDHV100R007C02

GFP Bearing Mode


N2EGS4A OptiX NG-SDH V100R004 GFP Bearing Mode



Maintenance Cases


Issue 01 (2008-07-30)

Board Equipment Version Bearing Mode

J5EGS8J5EAS1

OptiX OSN 9500 V100R005 Ethernet bearing mode, GFP bearing mode



5-67

Index

Aalarm suppression

report lower level alarm, 5-30AU_AIS, B3_EXC, B3_SD, MSP switching, 5-41AUX, EXT port, BD_STATUS, 5-40

BBER, SSN2SL64, STM-64, V-64.2b, LC, 5-45

Cclock, BUS_ERR, UXCSB, 5-44Clock, PS alarm, 5-23

EEXCAS, OOL alarm, clock, SSM protocol, 5-39extended subrack, 5-42

Ggrounding, bit error, 5-35GSCC, DCC, D1–D3, 5-25

HHP_TIM, J1 byte, 5-46

Iinterconnect

failure of MSP switching, 5-27

JJ0 byte, J1 byte, HP_TIM, 5-29

MMSP

switching failure, 5-27multi-mode, single-mode, EGS2, 5-24

OOTDR, 5-20

SSL64, BD_STATUS, HP_UNEQ, C2 byte, 5-37SNCP over MSP, HP_UNEQ alarm, 5-21SPQ4, TPS protection, working mode, 5-47SYN_BAD, threshold-crossing of clock jitter, 120-ohm2 MHz external clock, 5-48

XXCE, extended subrack, BD_STASTUS, 5-36XCS, active/standby switching, HSC_UNAVAIL,5-33XCS, ejector level on the front panel, 5-34

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


i-1

OSN 3500-00449022-Maintenance Cases(V100R008_01)

Documents