Hit 7080 Tsmn

7/24/2019 Hit 7080 Tsmn

1/74

SURPASS hiT 7080

4.1

Troubleshooting Manual (TSMN)

A42022-L5977-A157-01-7620

7/24/2019 Hit 7080 Tsmn

2/74

2 A42022-L5977-A157-01-7620

Issue: 1 Issue date: April 2008


The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-

TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,

INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT

LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS

OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR

THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2008. All rights reserved.

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal

injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected

has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-

nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-

zungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

7/24/2019 Hit 7080 Tsmn

3/74

A42022-L5977-A157-01-7620



Statements of compliance

FCC statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:(1) this device may not cause harmful interference, and (2) this device must accept any interferencereceived, including interference that may cause undesired operation. Shielded cables must be used withthis unit to ensure compliance with the Class A FCC limits.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuantto Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmfulinterference when the equipment is operated in a commercial environment. This equipment generates,uses, and can radiate radio frequency energy and, if not installed and used in accordance with theinstruction manual, may cause harmful interference to radio communications. Operation of this equip-ment in a residential area is likely to cause harmful interference in which case the user will be requiredto correct the interference at his own expense.

CE statement

The CE conformity declaration for the product is fulfilled when the system is built and cabled in line withthe information given in the manual and the documentation specified within it, such as installationinstructions, cable lists or the like. Where necessary project-specific documentation should be taken intoconsideration. Deviations from the specifications or independent modifications to the layout, such asuse of cable types with lower screening values for example, can lead to violation of the CE protectionrequirements. In such cases the conformity declaration is invalidated. The responsibility for any prob-lems which subsequently arise rests with the party responsible for deviating from the installation spec-

ifications.

7/24/2019 Hit 7080 Tsmn

4/74

4 A42022-L5977-A157-01-7620



7/24/2019 Hit 7080 Tsmn

5/74

A42022-L5977-A157-01-7620Issue: 1 Issue date: April 2008

5


Table of ContentsThis document has 74 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3.1 Symbols used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.3.2 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Alarm lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1 Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.2 Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3 Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Quality of service alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5 Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1 Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1.1 Communication_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1.2 Equipment_OverHeating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.1.3 Fan_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1.4 Loss_of_Power_Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1.5 Low_Order_Capacity_Mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.1.6 No_Free_Low_Order_Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.7 OA-Power_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1.8 OA-Pump_Bias_out_of_Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.1.9 OA-Temperature_out_of_Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.1.10 PLL_Unlock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.1.11 Power_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.12 SC_CF_Module_Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.13 SC_CF_Module_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.14 SFP_Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.1.15 SFP_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.1.16 SFP_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.1.17 SPI-Temperature_out_of_Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.18 Unit_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.19 Unit_Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.20 UnitType_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.21 VCXO_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2 Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.1 AU_AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.2 AU_LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2.3 Embedded DCC channel (n) failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2.4 HCOC27-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2.5 HCOC9-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2.6 HP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

7/24/2019 Hit 7080 Tsmn

6/74

6 A42022-L5977-A157-01-7620Issue: 1 Issue date: April 2008


3.2.7 HP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.2.8 HP-GFP_Customer_Signal_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.2.9 HP-GFP_Loss_of_Frame_Delineation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.2.10 HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.2.11 HP-RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2.12 HP-TIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2.13 HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.2.14 HP-Virtual_Concatenation_LOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.15 HP-Virtual_Concatenation_LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.16 HP-Virtual_Concatenation_TLCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.17 Link_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2.18 Loss_of_Timing_Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2.19 Loss_of_Timing_Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2.20 LP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2.21 LP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.2.22 LP-GFP_Customer_Signal_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2.23 LP-GFP_Loss_of_Frame_Delineation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2.24 LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.2.25 LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.2.26 LP-RFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.2.27 LP-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.28 LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.29 LP-Virtual_Concatenation_LOA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.2.30 LP-Virtual_Concatenation_LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.2.31 LP-Virtual_Concatenation_TLCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.2.32 MS_AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.2.33 MS-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.2.34 MS_DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.2.35 MS_EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.2.36 MS-K1/K2_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.37 MS_RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.2.38 OA_Gain_High. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.39 OA_Input_LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.40 OA_Output_LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.41 OA_Output_Power_High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.2.42 PPI-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.2.43 PPI-LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.44 PPI-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.45 PPI-LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.46 PPI-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.47 RPR-Exceed_Max_Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.48 RPR-Link_Failure_East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.2.49 RPR-Link_Failure_West. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2.50 RPR-Miscabling_East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2.51 RPR-Miscabling_West . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.2.52 RPR-Protection_Misconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.2.53 RPR-Ringlet0_ReservedA0_Exceeding. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

7/24/2019 Hit 7080 Tsmn

7/74


7


3.2.54 RPR-Ringlet1_ReservedA0_Exceeding . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.2.55 RPR-Topology_Inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.2.56 RPR-Topology_Instability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.2.57 RS-DCC_Connection_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.2.58 RS_DEG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.59 RS_EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.60 RS_LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.61 RS_TIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.2.62 SPI_LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.2.63 Synchronization_Signal_Message_Mismatch . . . . . . . . . . . . . . . . . . . . . . 50

3.2.64 System_Clock_Holdover_Longer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.2.65 System_Clock_Unlocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.2.66 Timing_Reference_Degrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.2.67 Timing_Reference_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.2.68 TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.2.69 TU-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.2.70 TU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.3 Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.3.1 ENV_MDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.4 Quality of service alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.4.1 E1-Negative_Bit-slip_TCA_15m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.4.2 E1-Negative_Bit-slip_TCA_24h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.4.3 E1-Positive_Bit-slip_TCA_15m. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.4.4 E1-Positive_Bit-slip_TCA_24h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.4.5 Ethernet TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.4.6 PDH TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.4.7 SDH TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.5 Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.5.1 accountExpiredOrDisabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.5.2 logIsFull. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.5.3 logOccupancyThresholdReached. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.5.4 Unauthorized_Access_Attempt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.5.5 Unsuccessful_Logins_Exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4 Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.1 Replacing SC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

4.1.1 SC card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.1.2 CF card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.1.3 Both SC and CF cards fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4.1.4 Downloading boot image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4.1.5 Downloading software load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4.1.6 Downloading MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4.2 Replacing CC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4.3 Replacing fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.4 Replacing filter unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5 MIB switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5.1 Different data configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7/24/2019 Hit 7080 Tsmn

8/74



5.2 Same data configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6 Fiber cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.1 Dry cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.2 Wet cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7/24/2019 Hit 7080 Tsmn

9/74


9


List of TablesTable 1 List of used conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 2 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 3 Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Table 4 Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Table 5 Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Table 6 Quality of service alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 7 Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

7/24/2019 Hit 7080 Tsmn

10/74



7/24/2019 Hit 7080 Tsmn

11/74


11

Troubleshooting Manual (TSMN) Preface

1 PrefaceThis Troubleshooting Manual describes fault-clearing procedures to be performed in

reaction to alarm events that may occur in the SURPASS hiT 7080 system.

1.1 Intended audience

This document is intended for anyone tasked with clearing fault conditions to restore

normal system operation. Personnel performing these procedures must have general

experience with Synchronous Digital Hierarchy (SDH) transport networks as well as

specific experience with Nokia Siemens Networks SURPASS hiT 7080 hardware com-

ponents and network management software. Personnel must also comply with all

relevant safety practices whenever working with SURPASS hiT 7080 equipment.

1.2 Structure of this documentAlarm lists

When a fault condition occurs, the relevant alarm notification will be generated and dis-

played on craft terminal screens. All SURPASS hiT 7080 alarms are listed in the Alarm

listsin Chapter 2. The alarm lists are divided into separate tables that match the fault

categories as presented on craft terminal screens. These categories are as follows:

Equipment alarms

Communication alarms

Environment alarms

Quality of Service (QoS) alarms

Security alarms

Troubleshooting

For each entry in the Alarm lists, specific fault-clearing procedures are contained in

Chapter 3, Troubleshooting. Click the desired alarm name in the Alarm list to jump

directly to the instructions for that alarm.

Described Features

gSome features described in this document may not be available. To identify thefeatures released for your project, please refer to the Release Note delivered

together with the product.

1.3 Symbols and conventions

The following symbols and conventions are used in this document:

7/24/2019 Hit 7080 Tsmn

12/74


Troubleshooting Manual (TSMN)Preface

1.3.1 Symbols used

gUsed for notes, tips or additional information.

1.3.2 Conventions used

1.4 History of changes

! Caution: Means that the reader should be careful. In this situation, you might do some-thing that could result in equipment damage or loss of data.

Warning: This warning symbol means danger. You are in a situation that could cause

bodily injury. Before you work on any equipment, be aware of the hazards involved with

electrical circuitry and be familiar with standard practices for preventing accidents.

Representation Meaning

Inverted commas Window or wizard titles are represented in inverted commas.Example: Open the Help and Support Center window. The

New Connection wizard is displayed.

Bold Any field or text in the GUI is represented in boldtype.

Example: Click Shutdownand then click OKto turn off the

computer.

Italic Variables and file extensions are represented in italic.

Example: Enter 192.168.0.1in the IP addressfield. Click OKto

produce a .pdfrendition.

Courier Commands, screen output, file names and paths are

represented in courier.

Example: # ping -t 192.168.0.1

Used for keyboard actions or place holders for concrete names

or values are represented in . If used for a

filename the courierfont must be used also.

Example: The naming convention for the log files is

.txt, where is the name of the NE

sending the messages. Press + to open

the task manager.

> Used for menu sequences.

Example: Click File > Print...to print the document.

Table 1 List of used conventions

Issue Issue date

1 April 2008 Initial version

Table 2 History of changes

7/24/2019 Hit 7080 Tsmn

13/74


13

Troubleshooting Manual (TSMN) Preface

Issue Issue date

Table 2 History of changes (Cont.)

7/24/2019 Hit 7080 Tsmn

14/74


Troubleshooting Manual (TSMN)Alarm lists

2 Alarm listsSURPASS hiT 7080 alarms are divided into the following categories:

Equipment alarms: originate from specific hardware elements (e.g., traffic card, con-troller card, shelf, etc.)

Communication alarms: originate from termination points which represent a particu-

lar function of the network

Environmental alarms: originate from telemetry sensors that monitor condi-

tions/events external to the Network Element (NE)

Quality of Service alarms: originate from termination points where performance

measurement and threshold supervision is enabled

Security alarms: originate from termination points which detect the system authen-

tication and authorization

2.1 Equipment alarmsTable 3lists SURPASS hiT 7080 equipment alarms. Click the alarm name in the table

to jump directly to the troubleshooting procedure for that alarm.

Alarm name Alarm Message Text

Communication_Failure Communication failure

Equipment_OverHeating Equipment overheating

Fan_Failure Fan failure

Loss_of_Power_Input Loss of power input

Low_Order_Capacity_Mismatch Low order capacity mismatch

No_Free_Low_Order_Capacity No free low order capacity

OA-Power_Failure Optical Amplifier (OA) power failure

OA-Pump_Bias_out_of_Range OA pump bias out of range

OA-Temperature_out_of_Range OA temperature out of range

PLL_Unlock Phase Lock Loop (PLL) unlock

Power_Failure Power failure

SC_CF_Module_Absent Compact Flash (CF) card absent

SC_CF_Module_Failure CF card failureSFP_Absent Small Factor Pluggable (SFP) absent

SFP_Failure SFP failure

SFP_Mismatch SFP mismatch

SPI-Temperature_out_of_Range Synchronous Physical Interface (SPI) laser

temperature out of range

Unit_Failure Unit failure

Unit_Removal Unit removal

Table 3 Equipment alarms

7/24/2019 Hit 7080 Tsmn

15/74


15

Troubleshooting Manual (TSMN) Alarm lists

2.2 Communication alarms

Table 4lists SURPASS hiT 7080 communication alarms. Click the alarm name in the

table to jump directly to the troubleshooting procedure for that alarm.

UnitType_Mismatch Unit type mismatch

VCXO_Failure Voltage Control Crystal Oscillator (VCXO)

Failure


Table 3 Equipment alarms (Cont.)

Alarm Name Alarm Message Text

AU_AIS Administrative Unit (AU) Alarm IndicationSignal (AIS)

AU_LOP AU Loss Of Pointer (LOP)

Embedded DCC channel (n) failure Embedded DCC Channel 1 or 2 failure

HCOC27-DCC_Connection_Failure High Capacity Overhead Channel (HCOC)

27 Data Communication Channel (DCC)

connection failure

HCOC9-DCC_Connection_Failure HCOC 9 DCC connection failure

HP-DEG High order Path (HP) signal DEGraded

(DEG)

HP-EXC HP EXCessive (EXC) error

HP-GFP_Customer_Signal_Failure HP Generic Framing Procedure (GFP)

customer signal failure

HP-GFP_Loss_of_Frame_Delineation HP GFP loss of frame delineation

HP-PLM HP PayLoad Mismatch (PLM)

HP-RDI HP Remote Defect Indication (RDI)

HP-TIM HP Trace Identifier Mismatch (TIM)

HP-UNEQ HP UNEQuipped (UNEQ)

HP-Virtual_Concatenation_LOA HP virtual concatenation Loss Of Alignment(LOA)

HP-Virtual_Concatenation_LOM HP virtual concatenation Loss Of

Multiframe (LOM)

HP-Virtual_Concatenation_TLCT HP virtual concatenation Total Loss of

Capacity Transmit (TLCT)

Link_Failure Link failure

Loss_of_Timing_Input Loss of timing input

Loss_of_Timing_Output Loss of timing output

Table 4 Communication alarms

7/24/2019 Hit 7080 Tsmn

16/74



LP-DEG Low order Path (LP) signal DEG

LP-EXC LP EXC error

LP-GFP_Customer_Signal_Failure LP GFP customer signal failure

LP-GFP_Loss_of_Frame_Delineation LP GFP loss of frame delineation

LP-PLM LP PLM

LP-RDI LP RDI

LP-RFI LP Remote Failure Indication (RFI)

LP-TIM LP TIM

LP-UNEQ LP UNEQ

LP-Virtual_Concatenation_LOA LP virtual concatenation LOA

LP-Virtual_Concatenation_LOM LP virtual concatenation LOM

LP-Virtual_Concatenation_TLCT LP virtual concatenation TLCT

MS_AIS Multiplex Section (MS) AIS

MS-DCC_Connection_Failure MS DCC connection failure

MS_DEG MS signal DEG

MS_EXC MS EXC

MS-K1/K2_Mismatch K1/K2 mismatch

MS_RDI MS RDI

OA_Gain_High OA gain high

OA_Input_LOS OA input Loss Of Signal (LOS)

OA_Output_LOS OA output LOS

OA_Output_Power_High OA output power high

PPI-AIS Plesiochronous Digital Hierarchy (PDH)

Physical Interface (PPI) AIS

PPI-LOF PPI LOF

PPI-LOM PPI LOM

PPI-LOS PPI LOS

PPI-RDI PPI RDI

RPR-Exceed_Max_Stations Resilient Packet Ring (RPR) exceed

maximum stations

RPR-Link_Failure_East RPR link failure east

RPR-Link_Failure_West RPR link failure west

RPR-Miscabling_East RPR miscabling east

RPR-Miscabling_West RPR miscabling west

RPR-Protection_Misconfig RPR protection misconfiguration


Table 4 Communication alarms (Cont.)

7/24/2019 Hit 7080 Tsmn

17/74


17

Troubleshooting Manual (TSMN) Alarm lists

2.3 Environmental alarms

Table 5lists SURPASS hiT 7080 environmental alarms. Click the alarm name in the

table to jump directly to the troubleshooting procedure for that alarm.

2.4 Quality of service alarms

Table 6lists SURPASS hiT 7080 QoSalarms. Click the alarm name in the table to jump

directly to the troubleshooting procedure for that alarm.

RPR-Ringlet0_ReservedA0_Exceeding RPR ringlet 0 reserved A0 exceeding

RPR-Ringlet1_ReservedA0_Exceeding RPR ringlet 1 reserved A0 exceeding

RPR-Topology_Inconsistent RPR topology inconsistent

RPR-Topology_Instability RPR topology instability

RS-DCC_Connection_Failure Regeneration Section (RS) DCC

connection failure

RS_DEG RS signal DEG

RS_EXC RS EXC

RS_LOF RS Loss Of Frame (LOF)

RS_TIM RS TIM

SPI_LOS SPI LOS

Synchronization_Signal_Message_Mis

match

Synchronization Signal Message (SSM)

mismatch

System_Clock_Holdover_Longer System clock holdover longer

System_Clock_Unlocked System clock unlocked

Timing_Reference_Degrade Timing reference degraded

Timing_Reference_Failure Timing reference failure

TU-AIS Tributary Unit (TU) AIS

TU-LOM TU LOM

TU-LOP TU LOP


Table 4 Communication alarms (Cont.)


ENV_MDI ENVironment (ENV) MiscellaneousDiscrete Input (MDI) 1 ~ 8

Table 5 Environmental alarms

7/24/2019 Hit 7080 Tsmn

18/74



2.5 Security alarms

Table 7lists SURPASS hiT 7080 security alarms. Click the alarm name in the table to

jump directly to the troubleshooting procedure for that alarm.


E1-Negative_Bit-slip_TCA_15m E1 negative bit-slip Threshold Crossed

Alarm (TCA) 15 minutes

E1-Negative_Bit-slip_TCA_24h E1 negative bit-slip TCA 24 hours

E1-Positive_Bit-slip_TCA_15m E1 positive bit-slip TCA 15 hours

E1-Positive_Bit-slip_TCA_24h E1 positive bit-slip TCA 24 hours

Ethernet TCA Ethernet TCA

PDH TCA PDH TCA

SDH TCA SDHTCA

Table 6 Quality of service alarms


accountExpiredOrDisabled Account expired or disabled

logIsFull Log is full

logOccupancyThresholdReached Log occupancy threshold reached

Unauthorized_Access_Attempt Unauthorized access attempt

Unsuccessful_Logins_Exceeded Unsuccessful logins exceeded

Table 7 Security alarms

7/24/2019 Hit 7080 Tsmn

19/74


19

Troubleshooting Manual (TSMN) Troubleshooting

3 TroubleshootingThis chapter describes the general troubleshooting instructions for each alarm.

3.1 Equipment alarms

The equipment alarms are listed in the following sub-chapters.

3.1.1 Communication_Failure

Troubleshooting instructions

1 Reboot or change the service card.

2 Reboot or change the SC card.3 If the alarm persists, contact the next higher level of technical support.

3.1.2 Equipment_OverHeating


1 Verify the fan unit is working correctly.

2 Verify the filter unit is clean.

3 Verify the air-conditioning is working correctly.

4 Verify the equipment is working correctly.

5 Verify the card temperature threshold is configured properly.

Alarm name Communication_Failure

Default severity Major

Alarm object System Controller (SC), High Order Cross Connect

(HOCC), and Low Order Cross Connect (LOCC)cards

General information and causes The communication between a service card and the

SC, HOCC, or LOCC card fails. This also includes

communication between the SC, HOCC, and

LOCC cards.

Alarm name Equipment_OverHeating


Alarm object SC, HOCC, LOCC, and all service cards (not

including IO cards)

General information and causes The temperature of the equipment is not in the

normal working range which is specified in the card

properties configuration.

7/24/2019 Hit 7080 Tsmn

20/74


Troubleshooting Manual (TSMN)Troubleshooting

6 If the alarm persists, contact the next higher level of technical support.

3.1.3 Fan_Failure


1 Verify the fans in the fan unit are working correctly.

2 Change the fan unit.


3.1.4 Loss_of_Power_Input


1 Verify the power cables to the power module are connected correctly.


3.1.5 Low_Order_Capacity_Mismatch


Alarm name Fan_Failure


Alarm object Fan unit

General information and causes The fan unit is defective.

Alarm name Loss_of_Power_Input


Alarm object Power module

General information and causes The -48 V power input is absent.

The input power is lower than -40 V. The input power is higher than -72 V.

Alarm name Low_Order_Capacity_Mismatch


Alarm object NE

General information and causes Alarm triggered when the Management Information

Base (MIB) configuration files in a newly input SC

card do not match the actual configuration of the

LOCC card in the NE.

7/24/2019 Hit 7080 Tsmn

21/74


21


1 Download a backup MIB from the Personal Computer (PC) into the CFcard of the

newly inserted SC card. For more information on MIB download, please refer to

Chapter 4.1.6.


3.1.6 No_Free_Low_Order_Capacity


1 Upgrade the LOCC capacity.

2 Delete some existing low order mapping on relevant SDH cards.

3 Delete some existing low order mapping on unused PDH cards and remove them

from the system to reallocate low order capacity.


3.1.7 OA-Power_Failure


1 Change the OA card.


3.1.8 OA-Pump_Bias_out_of_Range

!Caution:

If there is no backup MIB the system will have to be reconfigured.

Alarm name No_Free_Low_Order_Capacity


Alarm object PDHcards

General information and causes Alarm triggered when a new PDH card is inserted in

the system, but there is no more available low order

capacity in the LOCC card.

Alarm name OA_Power_Failure

Default severity Critical

Alarm object OAcard

General information and causes The power for the OA card fails.

Alarm name OA-Pump_Bias_out_of_Range


7/24/2019 Hit 7080 Tsmn

22/74




1 Verify the OA output power is set properly.

2 Verify the OA input power is normal.

3 Verify the OA card is not aging.


3.1.9 OA-Temperature_out_of_Range


1 Verify the fan unit is working correctly.

2 Verify the OA setting is proper.


3.1.10 PLL_Unlock


1 If fault occurs during card boot or synchronization, please wait till the initialization

process of the card is complete.

2 If the alarm continues after initialization is complete, replace the card.


Alarm object OA card

General information and causes The OA pump bias exceeds the threshold which is

specified in the OA port properties configuration.

Alarm name OA-Temperature_out_of_Range


Alarm object OA card

General information and causes The OA modules temperature exceeds the

threshold which is specified in the OA port

properties configuration.

Alarm name PLL_Unlock


Alarm object Card (All cards except HOCC, SC, power module,

and fan unit)

General information and causes This alarm is triggered when the PLLis in the

unlock state.

7/24/2019 Hit 7080 Tsmn

23/74


23


3.1.11 Power_Failure


1 Change the shelf.


3.1.12 SC_CF_Module_Absent


1 Insert the CF card.For more information, please refer to the SURPASS hiT 7080 Installation and Test

Manual (ITMN).


3.1.13 SC_CF_Module_Failure


1 Change the CF card.

For more information, please refer to the SURPASS hiT 7080 Installation and Test

Manual (ITMN).


Alarm name Power_Failure


Alarm object Power module

General information and causes The power module is not working normally.

Alarm name SC_CF_Module_Absent


Alarm object SC card

General information and causes The CF card is absent.

Alarm name SC_CF_Module_Failure


Alarm object SC card

General information and causes The CF card can not be accessed.
http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/http://hit_7080_itmn.pdf/

7/24/2019 Hit 7080 Tsmn

24/74



3.1.14 SFP_Absent


1 Insert the proper SFP module.


3.1.15 SFP_Failure


1 Change the SFP module.2 If the alarm persists, contact the next higher level of technical support.

3.1.16 SFP_Mismatch


1 Change to a suitable SFP module.


3.1.17 SPI-Temperature_out_of_Range

Alarm name SFP_Absent


Alarm object Optical port

General information and causes The SFPmodule is absent.

Alarm name SFP_Failure


Alarm object SFP module

General information and causes The SFP module is not working normally.

Alarm name SFP_Mismatch


Alarm object SFP module

General information and causes The bit rate of the SFP is lower than the port

requirement.

Alarm name SPI-Temperature_out_of_Range


7/24/2019 Hit 7080 Tsmn

25/74


25



1 Verify the refrigeration part and the bias current part of the laser are working cor-

rectly.

2 Change the 10 Gigabit Small Form Factor Pluggable (XFP) module.


3.1.18 Unit_Failure


1 Change the card.


3.1.19 Unit_Removal


1 Insert the corresponding card.


3.1.20 UnitType_Mismatch

Alarm object STM-64 port

General information and causes The temperature of the laser exceeds the normal

range.

Alarm name Unit_Failure


Alarm object Cards

General information and causes The card is defective.

Alarm name Unit_Removal


Alarm object Cards

General information and causes The card is absent.

Alarm name UnitType_Mismatch


Alarm object Cards

7/24/2019 Hit 7080 Tsmn

26/74




1 Insert the correct type of card.

2 Verify the card type in SEEPROM is set correctly through the cards mini USB.


3.1.21 VCXO_Failure


1 Replace HOCC card.


3.2 Communication alarms

The communication alarms are listed in the following sub-chapters.

3.2.1 AU_AIS


1 Troubleshoot the SPI, RS, MS, or AU-LOP alarms in the upstream node.


3.2.2 AU_LOP

General information and causes The inserted card type is not consistent with the

preconfigured card type.

Alarm name VCXO_Failure

Default severity MajorAlarm object HOCC card

General information and causes The VCXOcomponent on the HOCC card has

failed.

Alarm name AU_AIS

Default severity Minor

Alarm object SDHAU

General information and causes The upstream signal is defective.

Alarm name AU_LOP


7/24/2019 Hit 7080 Tsmn

27/74


27



1 Verify the upstream external cable connections are correct.


3.2.3 Embedded DCC channel (n) failure


1 Verify routing configuration.


3.2.4 HCOC27-DCC_Connection_Failure


1 Verify the HCOC27-DCC is enabled and working normally at both ends of the DCC

link.


3.2.5 HCOC9-DCC_Connection_Failure

Alarm object SDH AU

General information and causes No valid AU-4 pointer is found in the received signal

due to:

Line unit failure in the remote node.

Local tributary unit failure in the station.

Alarm name Embedded DCC channel1 failure


Alarm object NE

General information and causes DCCcommunication channel has failed.

Alarm name HCOC27-DCC_Connection_Failure


Alarm object SDH HCOC

General information and causes The HCOC27-DCC is disabled at one side of

the DCC link.

DCC link is down.

Alarm name HCOC9-DCC_Connection_Failure

7/24/2019 Hit 7080 Tsmn

28/74




1 Verify the HCOC9-DCC is enabled and working normally at both ends of the DCC

link.


3.2.6 HP-DEG

Troubleshooting instructions1 Verify the upstream external cabling and equipment are normal.

2 Verify the threshold is set correctly.


3.2.7 HP-EXC


1 Verify the upstream external cabling and equipment are normal.




Alarm object SDH HCOC

General information and causes The HCOC9-DCC is disabled at one side of the

DCC link.

DCC link is down.

Alarm name HP-DEG


Alarm object SDH HP

General information and causes A degraded signal defect is detected when the

equivalent Bit Error Rate (BER) exceeds a preset

threshold of 10-x, x = 5, 6, 7, 8, 9.

Alarm name HP-EXC


Alarm object SDH HP

General information and causes An excessive error defect is detected when the

equivalent BER exceeds a preset threshold of 10-x,

x = 4, 5.

7/24/2019 Hit 7080 Tsmn

29/74


29


3.2.8 HP-GFP_Customer_Signal_Failure




3.2.9 HP-GFP_Loss_of_Frame_Delineation


1 Verify the upstream connection and equipment are normal.


3.2.10 HP-PLM


Alarm name HP-GFP_Customer_Signal_Failure


Alarm object Ethernet Wide Area Networks (WAN) ports

General information and causes The upstream Local Area Networks (LAN) port

connectivity is down.

Alarm name HP-GFP_Loss_of_Frame_Delineation


Alarm object Ethernet WAN ports

General information and causes The upstream Ethernet signal fails because of GFP

synchronization failure.

Alarm name HP-PLM


Alarm object SDH HP

General information and causes The mapping modes of the local side and the

remote side are not the same.

The expected payload value set via

management system in the local side is not the

same as the actual payload value from the

remote side.

7/24/2019 Hit 7080 Tsmn

30/74



1 Change the mapping mode of the local node to the same as the remote node.

2 Change the expected payload value of the local node to the same as the actual

payload value of the remote node.


3.2.11 HP-RDI


1 React to the far-end alarms.


3.2.12 HP-TIM


1 Verify the expected path trace identifier is correct.


3.2.13 HP-UNEQ


Alarm name HP-RDI


Alarm object SDH HP

General information and causes The downstream NE receives the malfunctioning

signal.

Alarm name HP-TIM


Alarm object SDH HP

General information and causes The received path trace identifier does not match

the expected value.

Alarm name HP-UNEQ


Alarm object SDH HP

General information and causes The VC-4, VC-4-Xc (X = 4, 16, 64) in the STM-N

signal is not in use.

7/24/2019 Hit 7080 Tsmn

31/74


31


1 Confirm or create the cross connection at the other side to be consistent with the

local side.


3.2.14 HP-Virtual_Concatenation_LOA


1 Check the SDH path for each VCG member to see which member passes through

the most equipment or is taking the most time, and investigate an alternative con-

nection route.


3.2.15 HP-Virtual_Concatenation_LOM


1 Check VCG member for relevant terminal point alarms and correct them. Verify if

HP-Virtual_Concatenation_LOM alarm still exists.

2 Check performance monitoring for relevant VCG member terminal point for errors

and correct them. Verify if HP-Virtual_Concatenation_LOM alarm still exists.


3.2.16 HP-Virtual_Concatenation_TLCT

Alarm name HP-Virtual_Concatenation_LOA


Alarm object HP VCG

General information and causes The time between the first and last member of a

Virtual Concatenation Group (VCG) to reach the

local node is outside of the differential delay period.

Alarm name HP-Virtual_Concatenation_LOMDefault severity Critical

Alarm object HP VCG member

General information and causes One VCG member failed or was received at the

local node with errors.

Alarm name HP-Virtual_Concatenation_TLCT


Alarm object HP VCG

7/24/2019 Hit 7080 Tsmn

32/74




1 Verify the connection to the upstream equipment is normal.


3.2.17 Link_Failure


1 Verify the connections of the physical layer are correct.

2 Verify the connectors are clean.

3 Verify the fiber type is correct.


General information and causes If both ends are in Link Capacity Adjustment

Scheme (LCAS) mode, all TPs status is failure:

The Terminal Point (TP) in the VCG has

alarms; The sink TP receives the IDLE signal sent

from the remote source TP.

If both ends are in non-LCAS mode, any TP has

the following alarms:

AU-AIS

AU-LOP

HP-PLM

HP-TIM

HP-UNEQ

HP-Virtual_Concatenation_LOM

If the following VCG alarms occur:

HP-Virtual_Concatenation_LOA

HP-GFP_Loss_of_Frame_Delineation

Alarm name Link_Failure


Alarm object Ethernet ports

General information and causes The interconnecting cable contacts fail.

The receiver fails in the indicated unit.

The transmitter fails in the upstream

equipment.

Discontinuity of the intermediate cabling

occurs.

The erroneous routing of intermediate cabling

occurs.

The fiber type is incorrect.

7/24/2019 Hit 7080 Tsmn

33/74


33


3.2.18 Loss_of_Timing_Input



2 Verify the cables and connectors are not damaged.


3.2.19 Loss_of_Timing_Output


1 Verify the synchronization configuration is correct.

2 Verify the external timing input is normal.

3 Change the local equipment using this timing output.


3.2.20 LP-DEG


Alarm name Loss_of_Timing_Input


Alarm object HOCC card

General information and causes No incoming signal is detected on the indicated

station clock port.

Alarm name Loss_of_Timing_Output



General information and causes The equipment related to timing output fails.

Alarm name LP-DEG


Alarm object SDH LP

General information and causes The bit error ratio in the LP has exceeded the

provisioned LP Degrade Threshold. The quality

of the transmission signal is degraded.

This error is caused by fault(s) in upstream

external cabling or equipment.

7/24/2019 Hit 7080 Tsmn

34/74



1 Verify the upstream external cabling and equipment.

2 Verify the threshold in the management system.


3.2.21 LP-EXC


1 Verify upstream external cabling and equipment.


3.2.22 LP-GFP_Customer_Signal_Failure




3.2.23 LP-GFP_Loss_of_Frame_Delineation


Alarm name LP-EXC


Alarm object SDH LP

General information and causes The bit error ratio in the LP has exceeded the

provisioned LP Excessive Error Threshold. The

quality of the transmission signal is degraded.

This error is caused by fault(s) in upstreamexternal cabling or equipment.

Alarm name LP-GFP_Customer_Signal_Failure



General information and causes The upstream LAN port connectivity is down.

Alarm name LP-GFP_Loss_of_Frame_Delineation



General information and causes The upstream Ethernet signal fails because of GFP

synchronization failure.

7/24/2019 Hit 7080 Tsmn

35/74


35


1 Verify the upstream connection and equipment are normal.


3.2.24 LP-PLM


1 Verify the traffic structure of the local node is the same as the far-end node.

2 Change the expected traffic type in the TP Configuration window of the local node

LCT to match the actual payload value in far-end node.


3.2.25 LP-RDI


1 No alarms in the reporting node. React on the far-end alarms. Follow the clearing

actions for those alarm(s).


3.2.26 LP-RFI

Alarm name LP-PLM


Alarm object SDH LP

General information and causes Mapping mode of local and far-end NEs is not

same.

Expected payload value set via the TP

Configuration window of the LCT system in

local node is not the same as the actual payload

value in far-end node.

Alarm name LP-RDI


Alarm object SDH LP

General information and causes The downstream far end station of the node that

reported the alarm detects a malfunction at its

receiving side: Tributary Unit Alarm Indication

Signal received (TU-AIS).

Alarm name LP-RFI


7/24/2019 Hit 7080 Tsmn

36/74




1 No alarms in the reporting node. React on the far-end alarms. Follow the clearing

actions for those alarm(s).


3.2.27 LP-TIM


1 Verify cross-connections.

2 Verify tributary cables and tributary units.

3 Verify the expected trace in the management system.


3.2.28 LP-UNEQ


1 Confirm or create the cross connection settings at the remote side to be consistent

with the local side.


Alarm object SDH LP

General information and causes The downstream far end station of the node that

reported the alarm detects a malfunction at its

receiving side: VC-12 byte synchronous pathRemote Failure.

Alarm name LP-TIM


Alarm object SDH LP

General information and causes A provisioned trace string inserted in a VC-12 path

was not received or was received corrupted, due to

wrong configuration, hardware failures, or

transmission failures. Mismatch between received

trace ID and expected trace ID.

Alarm name LP-UNEQ


Alarm object SDH LP

General information and causes Lower order path in STM-N signal is not in use.

7/24/2019 Hit 7080 Tsmn

37/74


37


gWhen defining or changing a cross-connection this alarm will almost inevitablycome up as it is practically impossible to issue the changes at both sides at the same

moment.

3.2.29 LP-Virtual_Concatenation_LOA


1 Check the SDH path for each VCG member to see which member passes through

the most equipment or is taking the most time, and investigate an alternative con-

nection route.


3.2.30 LP-Virtual_Concatenation_LOM


1 Check VCG member for relevant terminal point alarms and correct them. Verify if

LP-Virtual_Concatenation_LOM alarm still exists.

2 Check performance monitoring for relevant VCG member terminal point for errors

and correct them. Verify if LP-Virtual_Concatenation_LOM alarm still exists.


!WARNING!

The LP-UNEQ can not be reported from 126 E1 (W/P) cards monitored ports if there

is no cross connect card equipped in NE.

Alarm name LP-Virtual_Concatenation_LOA


Alarm object LP VCGGeneral information and causes The time between the first and last member of a

VCG group to reach the local node is outside of the

differential delay period.

Alarm name LP-Virtual_Concatenation_LOM


Alarm object LP VCG member

General information and causes One VCG member failed or was received at the

local node with errors.

7/24/2019 Hit 7080 Tsmn

38/74



3.2.31 LP-Virtual_Concatenation_TLCT


1 Verify connection to the upstream equipment.


3.2.32 MS_AIS


Alarm name LP-Virtual_Concatenation_TLCT


Alarm object LP VCG

General information and causes If both ends are in LCAS mode, all TPs status

is failure:

The TP in the VCG has alarms;

The sink TP receives the IDLE signal sent

from the remote source TP.

If both ends are in non-LCAS mode, any TP has

the following alarms:

AU-AIS

AU-LOP

TU-AIS

TU-LOP

HP-PLM

HP-TIM

HP-UNEQ

HP-Virtual_Concatenation_LOM

LP-PLM

LP-TIM

LP-UNEQ

LP-Virtual_Concatenation_LOM

If the following VCG alarms occur:

HP-Virtual_Concatenation_LOA HP-GFP_Loss_of_Frame_Delineation

LP-Virtual_Concatenation_LOA

LP-GFP_Loss_of_Frame_Delineation

Alarm name MS_AIS


Alarm object SDH MS

General information and causes An AISsignal is inserted in the upstream NE.

7/24/2019 Hit 7080 Tsmn

39/74


39


1 Clear the upstream inserted AIS signal.


3.2.33 MS-DCC_Connection_Failure

Troubleshooting instructions1 Verify the MS-DCC is enabled and working normally at both ends of the MS DCC

link.


3.2.34 MS_DEG





3.2.35 MS_EXC

Alarm name MS-DCC_Connection_Failure


Alarm object SDH MS

General information and causes MS-DCC is disabled at one side of the MS DCC

link.

Alarm name MS_DEG


Alarm object SDH MS



x = 5, 6, 7, 8, 9.

Alarm name MS_EXC


Alarm object SDH MS



x = 3, 4, 5.

7/24/2019 Hit 7080 Tsmn

40/74







3.2.36 MS-K1/K2_Mismatch


1 Verify the conditions of protection switching are normal.


3.2.37 MS_RDI



2 Verity the local transmitting equipment is working normally.

3 Clear the indicated faults in the far-end node.


Alarm name MS-K1/K2_Mismatch


Alarm object SDH MS

General information and causes The protection switching is not successful.

Alarm name MS_RDI


Alarm object SDH MS

General information and causes The downstream NE receives the malfunctioning

signal:

MS-AIS

RS-LOF

RS-TIM

SPI-LOS

The following situations occur in the far-end station:

No signal received

AIS signal received

Excessive error rate

7/24/2019 Hit 7080 Tsmn

41/74


41


3.2.38 OA_Gain_High

Troubleshooting instructions1 Verify the output power of the OA is set properly.

2 Verity the input power of the OA is normal.


3.2.39 OA_Input_LOS



2 Verity the operation of the transmitter in the far-end station is normal.

3 Verify the cables and connectors are not damaged.

4 Verify the pre-defined input power threshold is proper.


3.2.40 OA_Output_LOS

Alarm name OA_Gain_High


Alarm object OA ports

General information and causes 20 dB Pre-Optical Amplifier (POA): Gain > 21

dB

13 dBm Booster Optical Amplifier (BOA): Gain

> 19 dB

15 dBm BOA: Gain > 21 dB

18 dBm BOA: Gain > 24 dB

Alarm name OA_Input_LOS



General information and causes The cable ruptures.

The optical connector is dirty.

The input optical power is below the pre-defined

power threshold.

Alarm name OA_Output_LOS



7/24/2019 Hit 7080 Tsmn

42/74




1 Verify the local transmitting module is normal.

2 Verify the pre-defined output power threshold is proper.


3.2.41 OA_Output_Power_High


1 Verify the gain of the OA is set properly.2 Verify the input power of the OA is proper.


3.2.42 PPI-AIS


1 Verify the upstream external cabling and equipment.


General information and causes The local transmitting module fails.

The output optical power is below the pre-

defined power threshold.

Alarm name OA_Output_Power_High



General information and causes 20 dB POA: Output power > -9 dBm

13 dBm BOA: Output power > 14 dBm



Alarm name PPI-AIS


Alarm object Port

General information and causes In one of the upstream nodes a defect is detectedand led to the insertion of the alarm indication

signal.

7/24/2019 Hit 7080 Tsmn

43/74


43


3.2.43 PPI-LOF


1 Verify operation of the transmitter in the far-end station.


3.2.44 PPI-LOM


1 Verify operation of the transmitter in the far-end station.


3.2.45 PPI-LOS


Alarm name PPI-LOF


Alarm object PDH Port

General information and causes Alignment to the frame structure of the received

E1/E3/DS3 signal is not possible.

Alarm name PPI-LOM



General information and causes Alignment to the Cyclic Redundancy Check (CRC)

Multiframe structure of the received E1 signal is not

possible.

Alarm name PPI-LOS



General information and causes Interconnecting cabling contacts have a

problem.

Receiver fault in indicated tributary unit.

Transmitter fault in the upstream equipment

(not the Transmission System).

Discontinuity in the intermediate cabling.

Erroneous routing of intermediate cabling.

7/24/2019 Hit 7080 Tsmn

44/74



1 Verify the connections of the physical layer.

2 Verify for cable breaks or dirty connectors (measure it with power meter and clear it).


3.2.46 PPI-RDI


1 Verify operation of the transmitter in the local station.


3.2.47 RPR-Exceed_Max_Stations


1 Remove stations which exceed the maximum limit of 32.


3.2.48 RPR-Link_Failure_East


Alarm name PPI-RDI



General information and causes When an alarm from the local node is transmitted to

the remote (far-end) node, the far end node will

send this alarm back.

Alarm name RPR-Exceed_Max_Stations


Alarm object RPRCard

General information and causes Number of stations in the RPR ring exceeds 32.

Alarm name RPR-Link_Failure_East


Alarm object RPR Card

General information and causes The east RPR links keep alive detection has timed

out.

7/24/2019 Hit 7080 Tsmn

45/74


45


1 Verify that the optical fiber or the SDH cross-connection used for the east RPR path

is normal.


3.2.49 RPR-Link_Failure_West


1 Verify that the optical fiber or the SDH cross-connection used for the west RPR path

is normal.


3.2.50 RPR-Miscabling_East


1 Re-configure the RPR link direction of one of the links, either local or far end, to

make sure the west (east) link connects to the east (west) link. Ensure this change

is consistent with the rest of the topology structure.


3.2.51 RPR-Miscabling_West

Alarm name RPR-Link_Failure_West



General information and causes The west RPR links keep alive detection has timed

out.

Alarm name RPR-Miscabling_East



General information and causes The east link of one RPR station is wrongly

connected to the same side (east link) of another

RPR station.

Alarm name RPR-Miscabling_West



General information and causes The west link of one RPR station is wrongly

connected to the same side (west link) of another

RPR station.

7/24/2019 Hit 7080 Tsmn

46/74




1 Re-configure the RPR link direction of one of the links, either local or far end, to

make sure the west (east) link connects to the east (west) link. Ensure this changeis consistent with the rest of the topology structure.


3.2.52 RPR-Protection_Misconfig


1 Verify the protection mode in all of the RPR stations of the ring is the same. If not,

re-configure the protection mode to be the same.


3.2.53 RPR-Ringlet0_ReservedA0_Exceeding


1 Re-configure the A0 bandwidth reserved on RPR ringlet0 and make sure not toexceed the available link rate.


3.2.54 RPR-Ringlet1_ReservedA0_Exceeding

Alarm name RPR-Protection_Misconfig



General information and causes At least one stations protection mode is differentfrom other stations.

Alarm name RPR-Ringlet0_ReservedA0_Exceeding



General information and causes A0 bandwidth reserved on RPR ringlet0 exceeds

the link rate.

Alarm name RPR-Ringlet1_ReservedA0_Exceeding



General information and causes A0 bandwidth reserved on RPR ringlet1 exceeds

the link rate.

7/24/2019 Hit 7080 Tsmn

47/74


47



1 Re-configure the A0 bandwidth reserved on RPR ringlet1 and make sure not to

exceed the available link rate.


3.2.55 RPR-Topology_Inconsistent


1 Re-configure the duplicated RPR stations MAC address.


3.2.56 RPR-Topology_Instability


1 Re-configure the RPR networks topology (such as the Cross Connection (CC), the

WAN port trigger, the optical link, etc.) and make sure the configuration is correct.


3.2.57 RS-DCC_Connection_Failure

Alarm name RPR-Topology_Inconsistent



General information and causes Inconsistent topology of the RPR ring is usually

caused by the duplicate Media Access Control(MAC) addresses.

Alarm name RPR-Topology_Instability



General information and causes Topology instability is caused by the topology not

being discovered correctly, because of reasons

such as the incorrect configuration of RPR links and

stations.

Alarm name RS-DCC_Connection_Failure


Alarm object SDH RS

General information and causes RS-DCC is disabled at one side of the RS DCC link.

7/24/2019 Hit 7080 Tsmn

48/74




1 Verify the RS-DCC is enabled and working normally at both ends of the RS DCC

link.


3.2.58 RS_DEG





3.2.59 RS_EXC




3.2.60 RS_LOF

Alarm name RS-DEG


Alarm object SDH RS


equivalent BER exceeds a preset threshold of 10-x,x = 6, 7, 8, 9.

Alarm name RS_EXC


Alarm object SDH RS


equivalent BER exceeds a preset threshold of 10-5.

Alarm name RS_LOF


Alarm object SDH RS

7/24/2019 Hit 7080 Tsmn

49/74


49



1 Verify the intermediate fiber is normal.


3 Loop the signal from the transmitter to the receiver. Verify no LOFfault is reported.

4 Verify the port signal level is proper.

5 Verify the transmitter in the far-end is normal.


3.2.61 RS_TIM


1 Verify the line cables are connected correctly by interpreting the received STM-N RS

trace identifiers.

2 Verify the expected RS trace identifier is correct.


3.2.62 SPI_LOS

General information and causes The received signal does not match the port

rate.

The received signal of the SDH section

overhead is not correctly structured. The port input level (dBm) is too high or too low.

The fiber type is wrong.

Alarm name RS_TIM


Alarm object SDH RS

General information and causes Incorrect routing occurs in the network due to:

Incorrectly connected line cables.

An improper expected trace identifier.

Alarm name SPI_LOS


Alarm object SDH SPI

General information and causes The fiber ruptures.

The optical connectors are dirty.

The upstream far-end station fails.

7/24/2019 Hit 7080 Tsmn

50/74





2 Verify the operation of the transmitter in the far-end station is normal.



3.2.63 Synchronization_Signal_Message_Mismatch


1 Verify the SSM byte value is a legal value.


3.2.64 System_Clock_Holdover_Longer


1 Repair the failed timing reference.

2 Re-lock the system clock to a valid timing reference.


3.2.65 System_Clock_Unlocked

Alarm name Synchronization_Signal_Message_Mismatch



General information and causes The SSMbyte is invalid.

Alarm name System_Clock_Holdover_Longer

Default severity Warning


General information and causes The system clock is running in the holdover mode

and the holdover time is longer than 24 hours.

Alarm name System_Clock_Unlocked



7/24/2019 Hit 7080 Tsmn

51/74


51



1 Verify the selected timing reference works normally.

2 Re-select a valid timing reference.

3 Set the system clock working mode as locked.


3.2.66 Timing_Reference_Degrade


1 Verify the upstream related equipment is working normally.

2 Verify the local timing input equipment is working normally.


3.2.67 Timing_Reference_Failure



2 Verify the local timing input equipment is working normally.


General information and causes All selected timing references are lost or have

failed.

The system clock mode has been changed

from the locked mode to the holdover or free-running mode manually.

Alarm

Documents

Hit 7080 Tsmn