Professional Documents
Culture Documents
4.1
A42022-L5977-A157-01-7620
Troubleshooting Manual (TSMN)
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 which
the 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 respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
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 interference
received, including interference that may cause undesired operation. Shielded cables must be used with
this 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, pursuant
to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference 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 the
instruction 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 required
to 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 with
the information given in the manual and the documentation specified within it, such as installation
instructions, cable lists or the like. Where necessary project-specific documentation should be taken into
consideration. Deviations from the specifications or independent modifications to the layout, such as
use of cable types with lower screening values for example, can lead to violation of the CE protection
requirements. 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.
A42022-L5977-A157-01-7620 3
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
4 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
Table of Contents
This document has 74 pages.
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.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
A42022-L5977-A157-01-7620 5
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.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
6 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.2.69 TU-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.2.70 TU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.3 Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.3.1 ENV_MDI<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
A42022-L5977-A157-01-7620 7
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
6 Fiber cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.1 Dry cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.2 Wet cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
List of Tables
Table 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
A42022-L5977-A157-01-7620 9
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
10 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Preface
1 Preface
This Troubleshooting Manual describes fault-clearing procedures to be performed in
reaction to alarm events that may occur in the SURPASS hiT 7080 system.
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
g Some features described in this document may not be available. To identify the
features released for your project, please refer to the Release Note delivered
together with the product.
A42022-L5977-A157-01-7620 11
Issue: 1 Issue date: April 2008
Preface Troubleshooting Manual (TSMN)
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 bold type.
Example: Click Shutdown and then click OK to turn off the
computer.
Italic Variables and file extensions are represented in italic.
Example: Enter 192.168.0.1 in the IP address field. Click OK to
produce a .pdf rendition.
Courier Commands, screen output, file names and paths are
represented in courier.
Example: # ping -t 192.168.0.1
<Angle brackets> Used for keyboard actions or place holders for concrete names
or values are represented in <angle brackets>. If used for a
filename the courier font must be used also.
Example: The naming convention for the log files is
<NEname>.txt, where <NEName> is the name of the NE
sending the messages. Press <CTRL>+<ALT><DEL> to open
the task manager.
> Used for menu sequences.
Example: Click File > Print... to print the document.
12 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Preface
A42022-L5977-A157-01-7620 13
Issue: 1 Issue date: April 2008
Alarm lists Troubleshooting Manual (TSMN)
2 Alarm lists
SURPASS 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
14 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Alarm lists
A42022-L5977-A157-01-7620 15
Issue: 1 Issue date: April 2008
Alarm lists Troubleshooting Manual (TSMN)
16 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Alarm lists
A42022-L5977-A157-01-7620 17
Issue: 1 Issue date: April 2008
Alarm lists Troubleshooting Manual (TSMN)
18 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3 Troubleshooting
This chapter describes the general troubleshooting instructions for each alarm.
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
Troubleshooting instructions
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.
A42022-L5977-A157-01-7620 19
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
6 If the alarm persists, contact the next higher level of technical support.
3.1.3 Fan_Failure
Troubleshooting instructions
1 Verify the fans in the fan unit are working correctly.
2 Change the fan unit.
3 If the alarm persists, contact the next higher level of technical support.
3.1.4 Loss_of_Power_Input
Troubleshooting instructions
1 Verify the power cables to the power module are connected correctly.
2 If the alarm persists, contact the next higher level of technical support.
3.1.5 Low_Order_Capacity_Mismatch
Troubleshooting instructions
20 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
1 Download a backup MIB from the Personal Computer (PC) into the CF card of the
newly inserted SC card. For more information on MIB download, please refer to
Chapter 4.1.6.
2 If the alarm persists, contact the next higher level of technical support.
Caution:
!
If there is no backup MIB the system will have to be reconfigured.
3.1.6 No_Free_Low_Order_Capacity
Troubleshooting instructions
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.
4 If the alarm persists, contact the next higher level of technical support.
3.1.7 OA-Power_Failure
Troubleshooting instructions
1 Change the OA card.
2 If the alarm persists, contact the next higher level of technical support.
3.1.8 OA-Pump_Bias_out_of_Range
A42022-L5977-A157-01-7620 21
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
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.
4 If the alarm persists, contact the next higher level of technical support.
3.1.9 OA-Temperature_out_of_Range
Troubleshooting instructions
1 Verify the fan unit is working correctly.
2 Verify the OA setting is proper.
3 If the alarm persists, contact the next higher level of technical support.
3.1.10 PLL_Unlock
Troubleshooting instructions
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.
3 If the alarm persists, contact the next higher level of technical support.
22 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.1.11 Power_Failure
Troubleshooting instructions
1 Change the shelf.
2 If the alarm persists, contact the next higher level of technical support.
3.1.12 SC_CF_Module_Absent
Troubleshooting instructions
1 Insert the CF card.
For more information, please refer to the SURPASS hiT 7080 Installation and Test
Manual (ITMN).
2 If the alarm persists, contact the next higher level of technical support.
3.1.13 SC_CF_Module_Failure
Troubleshooting instructions
1 Change the CF card.
For more information, please refer to the SURPASS hiT 7080 Installation and Test
Manual (ITMN).
2 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 23
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.1.14 SFP_Absent
Troubleshooting instructions
1 Insert the proper SFP module.
2 If the alarm persists, contact the next higher level of technical support.
3.1.15 SFP_Failure
Troubleshooting instructions
1 Change the SFP module.
2 If the alarm persists, contact the next higher level of technical support.
3.1.16 SFP_Mismatch
Troubleshooting instructions
1 Change to a suitable SFP module.
2 If the alarm persists, contact the next higher level of technical support.
3.1.17 SPI-Temperature_out_of_Range
24 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
Troubleshooting instructions
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 If the alarm persists, contact the next higher level of technical support.
3.1.18 Unit_Failure
Troubleshooting instructions
1 Change the card.
2 If the alarm persists, contact the next higher level of technical support.
3.1.19 Unit_Removal
Troubleshooting instructions
1 Insert the corresponding card.
2 If the alarm persists, contact the next higher level of technical support.
3.1.20 UnitType_Mismatch
A42022-L5977-A157-01-7620 25
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
General information and causes The inserted card type is not consistent with the
preconfigured card type.
Troubleshooting instructions
1 Insert the correct type of card.
2 Verify the card type in SEEPROM is set correctly through the card’s mini USB.
3 If the alarm persists, contact the next higher level of technical support.
3.1.21 VCXO_Failure
Troubleshooting instructions
1 Replace HOCC card.
2 If the alarm persists, contact the next higher level of technical support.
3.2.1 AU_AIS
Troubleshooting instructions
1 Troubleshoot the SPI, RS, MS, or AU-LOP alarms in the upstream node.
2 If the alarm persists, contact the next higher level of technical support.
3.2.2 AU_LOP
26 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
Troubleshooting instructions
1 Verify the upstream external cable connections are correct.
2 If the alarm persists, contact the next higher level of technical support.
Troubleshooting instructions
1 Verify routing configuration.
2 If the alarm persists, contact the next higher level of technical support.
3.2.4 HCOC27-DCC_Connection_Failure
Troubleshooting instructions
1 Verify the HCOC27-DCC is enabled and working normally at both ends of the DCC
link.
2 If the alarm persists, contact the next higher level of technical support.
3.2.5 HCOC9-DCC_Connection_Failure
A42022-L5977-A157-01-7620 27
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 Verify the HCOC9-DCC is enabled and working normally at both ends of the DCC
link.
2 If the alarm persists, contact the next higher level of technical support.
3.2.6 HP-DEG
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the threshold is set correctly.
3 If the alarm persists, contact the next higher level of technical support.
3.2.7 HP-EXC
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the threshold is set correctly.
3 If the alarm persists, contact the next higher level of technical support.
28 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.8 HP-GFP_Customer_Signal_Failure
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.9 HP-GFP_Loss_of_Frame_Delineation
Troubleshooting instructions
1 Verify the upstream connection and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.10 HP-PLM
Troubleshooting instructions
A42022-L5977-A157-01-7620 29
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
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 If the alarm persists, contact the next higher level of technical support.
3.2.11 HP-RDI
Troubleshooting instructions
1 React to the far-end alarms.
2 If the alarm persists, contact the next higher level of technical support.
3.2.12 HP-TIM
Troubleshooting instructions
1 Verify the expected path trace identifier is correct.
2 If the alarm persists, contact the next higher level of technical support.
3.2.13 HP-UNEQ
Troubleshooting instructions
30 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
1 Confirm or create the cross connection at the other side to be consistent with the
local side.
2 If the alarm persists, contact the next higher level of technical support.
3.2.14 HP-Virtual_Concatenation_LOA
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.15 HP-Virtual_Concatenation_LOM
Troubleshooting instructions
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 If the alarm persists, contact the next higher level of technical support.
3.2.16 HP-Virtual_Concatenation_TLCT
A42022-L5977-A157-01-7620 31
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
General information and causes • If both ends are in Link Capacity Adjustment
Scheme (LCAS) mode, all TP’s 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
Troubleshooting instructions
1 Verify the connection to the upstream equipment is normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.17 Link_Failure
Troubleshooting instructions
1 Verify the connections of the physical layer are correct.
2 Verify the connectors are clean.
3 Verify the fiber type is correct.
4 If the alarm persists, contact the next higher level of technical support.
32 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.18 Loss_of_Timing_Input
Troubleshooting instructions
1 Verify the connections of the physical layer are correct.
2 Verify the cables and connectors are not damaged.
3 If the alarm persists, contact the next higher level of technical support.
3.2.19 Loss_of_Timing_Output
Troubleshooting instructions
1 Verify the synchronization configuration is correct.
2 Verify the external timing input is normal.
3 Change the local equipment using this timing output.
4 If the alarm persists, contact the next higher level of technical support.
3.2.20 LP-DEG
Troubleshooting instructions
A42022-L5977-A157-01-7620 33
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.2.21 LP-EXC
Troubleshooting instructions
1 Verify upstream external cabling and equipment.
2 If the alarm persists, contact the next higher level of technical support.
3.2.22 LP-GFP_Customer_Signal_Failure
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.23 LP-GFP_Loss_of_Frame_Delineation
Troubleshooting instructions
34 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.24 LP-PLM
Troubleshooting instructions
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 If the alarm persists, contact the next higher level of technical support.
3.2.25 LP-RDI
Troubleshooting instructions
1 No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).
2 If the alarm persists, contact the next higher level of technical support.
3.2.26 LP-RFI
A42022-L5977-A157-01-7620 35
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).
2 If the alarm persists, contact the next higher level of technical support.
3.2.27 LP-TIM
Troubleshooting instructions
1 Verify cross-connections.
2 Verify tributary cables and tributary units.
3 Verify the expected trace in the management system.
4 If the alarm persists, contact the next higher level of technical support.
3.2.28 LP-UNEQ
Troubleshooting instructions
1 Confirm or create the cross connection settings at the remote side to be consistent
with the local side.
2 If the alarm persists, contact the next higher level of technical support.
36 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
WARNING!
!
The LP-UNEQ can not be reported from 126 × E1 (W/P) card’s monitored ports if there
is no cross connect card equipped in NE.
3.2.29 LP-Virtual_Concatenation_LOA
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.30 LP-Virtual_Concatenation_LOM
Troubleshooting instructions
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.
3 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 37
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.2.31 LP-Virtual_Concatenation_TLCT
Troubleshooting instructions
1 Verify connection to the upstream equipment.
2 If the alarm persists, contact the next higher level of technical support.
3.2.32 MS_AIS
Troubleshooting instructions
38 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.33 MS-DCC_Connection_Failure
Troubleshooting instructions
1 Verify the MS-DCC is enabled and working normally at both ends of the MS DCC
link.
2 If the alarm persists, contact the next higher level of technical support.
3.2.34 MS_DEG
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the threshold is set correctly.
3 If the alarm persists, contact the next higher level of technical support.
3.2.35 MS_EXC
A42022-L5977-A157-01-7620 39
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the threshold is set correctly.
3 If the alarm persists, contact the next higher level of technical support.
3.2.36 MS-K1/K2_Mismatch
Troubleshooting instructions
1 Verify the conditions of protection switching are normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.37 MS_RDI
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verity the local transmitting equipment is working normally.
3 Clear the indicated faults in the far-end node.
4 If the alarm persists, contact the next higher level of technical support.
40 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.38 OA_Gain_High
Troubleshooting instructions
1 Verify the output power of the OA is set properly.
2 Verity the input power of the OA is normal.
3 If the alarm persists, contact the next higher level of technical support.
3.2.39 OA_Input_LOS
Troubleshooting instructions
1 Verify the connections of the physical layer are correct.
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.
5 If the alarm persists, contact the next higher level of technical support.
3.2.40 OA_Output_LOS
A42022-L5977-A157-01-7620 41
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 Verify the local transmitting module is normal.
2 Verify the pre-defined output power threshold is proper.
3 If the alarm persists, contact the next higher level of technical support.
3.2.41 OA_Output_Power_High
Troubleshooting instructions
1 Verify the gain of the OA is set properly.
2 Verify the input power of the OA is proper.
3 If the alarm persists, contact the next higher level of technical support.
3.2.42 PPI-AIS
Troubleshooting instructions
1 Verify the upstream external cabling and equipment.
2 If the alarm persists, contact the next higher level of technical support.
42 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
3.2.43 PPI-LOF
Troubleshooting instructions
1 Verify operation of the transmitter in the far-end station.
2 If the alarm persists, contact the next higher level of technical support.
3.2.44 PPI-LOM
Troubleshooting instructions
1 Verify operation of the transmitter in the far-end station.
2 If the alarm persists, contact the next higher level of technical support.
3.2.45 PPI-LOS
Troubleshooting instructions
A42022-L5977-A157-01-7620 43
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.2.46 PPI-RDI
Troubleshooting instructions
1 Verify operation of the transmitter in the local station.
2 If the alarm persists, contact the next higher level of technical support.
3.2.47 RPR-Exceed_Max_Stations
Troubleshooting instructions
1 Remove stations which exceed the maximum limit of 32.
2 If the alarm persists, contact the next higher level of technical support.
3.2.48 RPR-Link_Failure_East
Troubleshooting instructions
44 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
1 Verify that the optical fiber or the SDH cross-connection used for the east RPR path
is normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.49 RPR-Link_Failure_West
Troubleshooting instructions
1 Verify that the optical fiber or the SDH cross-connection used for the west RPR path
is normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.50 RPR-Miscabling_East
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.51 RPR-Miscabling_West
A42022-L5977-A157-01-7620 45
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.52 RPR-Protection_Misconfig
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.53 RPR-Ringlet0_ReservedA0_Exceeding
Troubleshooting instructions
1 Re-configure the A0 bandwidth reserved on RPR ringlet0 and make sure not to
exceed the available link rate.
2 If the alarm persists, contact the next higher level of technical support.
3.2.54 RPR-Ringlet1_ReservedA0_Exceeding
46 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
Troubleshooting instructions
1 Re-configure the A0 bandwidth reserved on RPR ringlet1 and make sure not to
exceed the available link rate.
2 If the alarm persists, contact the next higher level of technical support.
3.2.55 RPR-Topology_Inconsistent
Troubleshooting instructions
1 Re-configure the duplicated RPR stations MAC address.
2 If the alarm persists, contact the next higher level of technical support.
3.2.56 RPR-Topology_Instability
Troubleshooting instructions
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.
2 If the alarm persists, contact the next higher level of technical support.
3.2.57 RS-DCC_Connection_Failure
A42022-L5977-A157-01-7620 47
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 Verify the RS-DCC is enabled and working normally at both ends of the RS DCC
link.
2 If the alarm persists, contact the next higher level of technical support.
3.2.58 RS_DEG
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the threshold is set correctly.
3 If the alarm persists, contact the next higher level of technical support.
3.2.59 RS_EXC
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
3.2.60 RS_LOF
48 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
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.
Troubleshooting instructions
1 Verify the intermediate fiber is normal.
2 Verify the connectors are clean.
3 Loop the signal from the transmitter to the receiver. Verify no LOF fault is reported.
4 Verify the port signal level is proper.
5 Verify the transmitter in the far-end is normal.
6 If the alarm persists, contact the next higher level of technical support.
3.2.61 RS_TIM
Troubleshooting instructions
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 If the alarm persists, contact the next higher level of technical support.
3.2.62 SPI_LOS
A42022-L5977-A157-01-7620 49
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
Troubleshooting instructions
1 Verify the connections of the physical layer are correct.
2 Verify the operation of the transmitter in the far-end station is normal.
3 Verify the connectors are clean.
4 If the alarm persists, contact the next higher level of technical support.
3.2.63 Synchronization_Signal_Message_Mismatch
Troubleshooting instructions
1 Verify the SSM byte value is a legal value.
2 If the alarm persists, contact the next higher level of technical support.
3.2.64 System_Clock_Holdover_Longer
Troubleshooting instructions
1 Repair the failed timing reference.
2 Re-lock the system clock to a valid timing reference.
3 If the alarm persists, contact the next higher level of technical support.
3.2.65 System_Clock_Unlocked
50 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
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.
Troubleshooting instructions
1 Verify the selected timing reference works normally.
2 Re-select a valid timing reference.
3 Set the system clock working mode as locked.
4 If the alarm persists, contact the next higher level of technical support.
3.2.66 Timing_Reference_Degrade
Troubleshooting instructions
1 Verify the upstream related equipment is working normally.
2 Verify the local timing input equipment is working normally.
3 If the alarm persists, contact the next higher level of technical support.
3.2.67 Timing_Reference_Failure
Troubleshooting instructions
1 Verify the upstream external cabling and equipment are normal.
2 Verify the local timing input equipment is working normally.
3 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 51
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.2.68 TU-AIS
Troubleshooting instructions
1 Verify upstream external cabling and equipment.
2 If the alarm persists, contact the next higher level of technical support.
3.2.69 TU-LOM
Troubleshooting instructions
1 Verify upstream external cabling and equipment.
2 Using the management system, check if unit failure is reported for the unit generat-
ing the multi-frame alignment signal. In that NE, remove the unit and replace it with
a new one.
3 If a unit failure is not reported, loop the STM-1 signal at the transmitting NE and at
the receiving NE. In this condition, the network element reporting VC-4 Loss of mul-
tiframe contains the faulty unit.
4 If the alarm persists, contact the next higher level of technical support.
3.2.70 TU-LOP
52 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
Troubleshooting instructions
1 Verify upstream external cabling and equipment.
2 Verify whether the TP Multiplexer structure of the both ends of the stream is the
same.
3 If the alarm persists, contact the next higher level of technical support.
3.3.1 ENV_MDI<n>
Troubleshooting instructions
1 Keep the states of the MDI items same with what is pre-defined.
2 Verify the MDI items are pre-defined properly.
3 If the alarm persists, contact the next higher level of technical support.
3.4.1 E1-Negative_Bit-slip_TCA_15m
Troubleshooting instructions
1 Verify the clock frequency of E1 Ports.
2 Verify whether the system clock is in locked status.
3 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 53
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.4.2 E1-Negative_Bit-slip_TCA_24h
Troubleshooting instructions
1 Verify the clock frequency of E1 Ports.
2 Verify whether the system clock is in locked status.
3 If the alarm persists, contact the next higher level of technical support.
3.4.3 E1-Positive_Bit-slip_TCA_15m
Troubleshooting instructions
1 Verify the clock frequency of E1 Ports.
2 Verify whether the system clock is in locked status.
3 If the alarm persists, contact the next higher level of technical support.
3.4.4 E1-Positive_Bit-slip_TCA_24h
Troubleshooting instructions
1 Verify the clock frequency of E1 Ports.
2 Verify whether the system clock is in locked status.
3 If the alarm persists, contact the next higher level of technical support.
54 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
Troubleshooting instructions
1 Verify the upstream external cable and equipment are normal.
2 Verify the upstream NE sends the excessive bad bytes or packets on purpose.
3 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 55
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
General information and causes SURPASS hiT 7080 monitors various performance
parameters on many layers in order to calculate the
transmission quality:
• Far-end and near-end PPI
– Background Block Error (BBE)
– Errored Second (ES)
– Severely Errored Second (SES)
– UnAvailable Second (UAS)
Performance monitoring provides the capability to
signal performance degradation (via a TCA alarm)
before a more serious failure occurs. Each
transponder card accumulates its performance
measurements every 0, 15, 30, 45 minutes past
each hour. At the end of each 15-minute reporting
period, each card automatically reports its
performance counts to the SC card. In addition, 24-
hour performance counts are obtained by summing
all 15-minute counts of the day. The user may set
the desired 15-minute and 24-hour alarm
thresholds for each monitored parameter.
A monitored performance parameter counter
exceeds its user-defined threshold.
Troubleshooting instructions
1 Verify the upstream external cable and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
56 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
General information and causes SURPASS hiT 7080 monitors various performance
parameters on many layers in order to calculate the
transmission quality:
• Far-end and near-end MS
– BBE
– ES
– SES
– UAS
• Far-end and near-end HP
– BBE
– ES
– SES
– UAS
• Near-end RS
– BBE
– ES
– SES
– UAS
• Local AU
– PJCP
– PJCN
• Far-end and near-end LP
– BBE
– ES
– SES
– UAS
Performance monitoring provides the capability to
signal performance degradation (via a TCA alarm)
before a more serious failure occurs. Each
transponder card accumulates its performance
measurements every 00, 15, 30, 45 minutes past
each hour. At the end of each 15-minute reporting
period, each card automatically reports its
performance counts to the SC card. In addition, 24-
hour performance counts are obtained by summing
all 15-minute counts of the day. The user may set
the desired 15-minute and 24-hour alarm
thresholds for each monitored parameter.
A monitored performance parameter counter
exceeds its user-defined threshold.
Troubleshooting instructions
1 Verify the upstream external cable and equipment are normal.
2 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 57
Issue: 1 Issue date: April 2008
Troubleshooting Troubleshooting Manual (TSMN)
3.5.1 accountExpiredOrDisabled
Troubleshooting instructions
1 If the account has expired - enable the account using the LCT and set a new expi-
ration date.
2 If the account was automatically disabled by SNMPv3 - verify the security log for
reason of account suspension and if desired re-enable the user.
3 If the alarm persists, contact the next higher level of technical support.
3.5.2 logIsFull
Troubleshooting instructions
1 Upload log file and select option to delete log after upload.
2 Increase size of security file log using LCT.
3 If the alarm persists, contact the next higher level of technical support.
3.5.3 logOccupancyThresholdReached
58 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Troubleshooting
General information and causes Security log for tracking security and configuration
related events has reached the user defined
threshold (default 80%).
Troubleshooting instructions
1 Upload log file and select option to delete log after upload.
2 Increase size of security file log using LCT.
3 If the alarm persists, contact the next higher level of technical support.
3.5.4 Unauthorized_Access_Attempt
Troubleshooting instructions
1 Track down the source of the attempt.
2 In the LCT, go the “User Administration” window (NE Security > NE User Manage-
ment). Clear the alarm manually by right-clicking the desired user and selecting
Reset Unauthorized Access Counter from the context menu.
3 If the alarm persists, contact the next higher level of technical support.
3.5.5 Unsuccessful_Logins_Exceeded
Troubleshooting instructions
1 In the LCT, go the “User Administration” window (NE Security > NE User Manage-
ment). Check the desired user or user with high number of invalid logins. Re-enable
the user by right-clicking the user and selecting Enable from the context menu or
click Modify User and deselect the Account is disabled check box in the “Modify
User” window.
2 If the alarm persists, contact the next higher level of technical support.
A42022-L5977-A157-01-7620 59
Issue: 1 Issue date: April 2008
Card replacement Troubleshooting Manual (TSMN)
4 Card replacement
This section contains instructions for removing a faulty card and replacing it with a spare
of the same type.
The general instructions are as follows:
• When replacing cards, all the operations must comply with the SURPASS hiT 7080
Safety Instructions.
• When replacing cards, it is essential to check and record the optical transmitting
power, using an optical power meter, before the cards are returned to service.
• Cards can be removed or inserted the slots while they are live. The lever on the card
must be opened before the card is removed and be closed after the card is inserted.
• Before replacing a card which is suspected of being faulty, try to reactivate the
system by means of a hardware reset (e.g. removing and re-inserting the card).
Never do this when the red FAULT Light Emitting Diode (LED) on the card is illumi-
nated.
• The card setup procedure can only start once the card has been mated properly with
its backplane connector. Please make sure that the two levers of the card secure the
card pair in the shelf properly.
• After a card has been replaced, the card status must be confirmed on the LCT.
• Running the system without the Cross Connection (CC) card is prohibited. Please
make sure that the CC cards have been mounted properly before the system is
powered on. If the user has removed the CC card (on either working or protection
CC cards), a cold reboot is mandatory after re-installing it.
For instructions on how to execute many of the instructions described in this chapter,
please refer to the SURPASS hiT 7080 Installation and Test Manual (ITMN), Commis-
sioning Manual (COMN), and Operating Manual (OMN).
WARNING!
!
When an SC card is removed from the shelf, the management system will lose connec-
tivity to the NE.
During this time, the management interface is not functional.
60 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Card replacement
1 One PC connects to the new SC card via the console port and connects to the
System Interface with Engineering Order Wire (SI-E) or System Interface (SI) card
via the MGMT port.
2 The Hyper Terminal should be installed and properly set on the PC
See ........... The SURPASS hiT 7080 Commissioning Manual (COMN).
3 A File Transport Protocol (FTP) server program should be installed and properly set
on the PC. For convenience, it is suggested to use the built-in FTP server on
Windows XP. To activate this server please refer to the TNMS CT manual in the
section containing information on 3rd party software installation.
4 The unzip software like winzip or winrar should be installed on the PC.
5 The boot image file (e.g., 7080.bin) and software load file (e.g., PBm1r40bxxx.bld)
should be saved in the FTP server user directory.
For the boot image file and software load file, please contact Nokia Siemens
Networks Technical Support.
6 The MIB file saved by the LCT with the extension .mib should be changed into a .zip
file and unzipped to the local working directory on the PC.
The unzipped MIB file package on the PC includes the following files:
• %Local_working_drive%\ghead.txt
• %Local_working_drive%\headfile.txt
• %Local_working_drive%\ne\*.*
• %Local_working_drive%\gmpls\*.*
%Local_working_drive% specifies the drive letter of the hard disk drive containing
the local working directory on the PC.
WARNING!
!
If the boot process is not stopped in time and the system comes into the normal startup
process, the NE configuration may be lost and the traffic may be interrupted.
In this case, the operator must remove the SC card immediately and execute the step 4
and 5 again.
A42022-L5977-A157-01-7620 61
Issue: 1 Issue date: April 2008
Card replacement Troubleshooting Manual (TSMN)
WARNING!
!
If the boot process is not stopped in time and the system comes into the normal startup
process, the NE configuration may be lost and the traffic may be interrupted.
In this case, the operator must remove the SC card immediately and execute the step 4
and 5 again.
62 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Card replacement
14 After the system reboot finishes, verify the software version is correct through the
LCT.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).
PROCEDURE COMPLETE!
WARNING!
!
If the boot process is not stopped in time and the system comes into the normal startup
process, the NE configuration may be lost and the traffic may be interrupted.
In this case, the operator must remove the SC card immediately and execute the step 4
and 5 again.
A42022-L5977-A157-01-7620 63
Issue: 1 Issue date: April 2008
Card replacement Troubleshooting Manual (TSMN)
1 Launch the “Boot Mode” window in the Hyper Terminal by pressing <b> during the
system reboot when the Hyper Terminal shows the countdown 5 4 3 2 1 ...
2 Press <i> to enter the “IP Configuration” window.
3 Press <1> and set the boot device as fe.
4 Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
5 Press <3> and enter the NE Ethernet IP mask address.
6 Press <4> and enter the PC IP address. In order to communicate with the NE, the
PC IP address needs to be in the same sub-network as the NE Ethernet IP address.
7 Press <7> and enter the FTP user account name which is used for the NE to login
into the FTP server on the PC.
The PC is an FTP server.
The default user name is pm.
8 Press <8> and enter the FTP password which is used for the NE to login into the
FTP server.
The PC is an FTP server.
The default password is pm.
9 Press <x> to return to the “Boot Mode” window.
10 Press <o> to enter the “System Maintain” window.
11 Press <f> to enter the “Boot image” window.
12 Enter the corresponding boot image file name (e.g., 7080.bin) and press <Enter>.
The “File Size” prompt is displayed.
13 When all items show OK, the boot image file is downloaded to the SC card.
Press <Enter> to return to the “System Maintain” window.
14 Press <x> to return to the “Boot Mode” window.
PROCEDURE COMPLETE!
64 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Card replacement
1 Launch the “Boot Mode” window in the Hyper Terminal by pressing <b> during the
system reboot when the Hyper Terminal shows the countdown 5 4 3 2 1 ...
2 Press <i> to enter the “IP Configuration” window.
3 Press <2> and enter the NE Ethernet Internet Protocol (IP) address.
4 Press <3> and enter the NE Ethernet IP mask address.
5 Press <4> and enter the PC IP address. In order to communicate with the NE, the
PC IP address needs to be in the same sub-network as the NE Ethernet IP address.
6 Press <x> to return to the “Boot Mode” window.
7 On the PC, select Start > Programs > Accessories > Command Prompt menu
item.
The “Command Prompt” window is opened.
8 Use the following commands:
A42022-L5977-A157-01-7620 65
Issue: 1 Issue date: April 2008
Card replacement Troubleshooting Manual (TSMN)
66 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Card replacement
A42022-L5977-A157-01-7620 67
Issue: 1 Issue date: April 2008
MIB switching Troubleshooting Manual (TSMN)
5 MIB switching
This section contains instructions for switching between the active MIB and the backup
MIB.
Normally the MIB is saved in the active Board Flash (BF) in the SC card. There are three
additional copies for backup purposes, including:
• Active CF
• Backup CF
The MIB collects:
• Data managed by the external interfaces
• Data used in the cards settings
• Data used by the SC card for internal activities
MIB switching procedures vary, depending on the following different scenarios:
• The data configuration is different between the old and new MIB.
• The data configuration is the same between the old and new MIB.
For instructions on how to execute the instructions described in this chapter, please refer
to the SURPASS hiT 7080 Operating Manual (OMN).
68 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) MIB switching
A42022-L5977-A157-01-7620 69
Issue: 1 Issue date: April 2008
Fiber cleaning Troubleshooting Manual (TSMN)
6 Fiber cleaning
Two cleaning methods exist: wet cleaning and dry cleaning. General rules are as
follows:
• It is always preferable to clean fiber ends when there is no optical power being deliv-
ered. When no power is present, either method (wet or dry) may be employed.
• However, in certain situations, it may be necessary to clean fiber ends with optical
power present. This should be attempted only if there is no alternative (i.e., when
shutting off the power would cause a loss of traffic). If the optical power is 15 dBm
or less, either method (wet or dry) may be used. If the optical power is 15 dBm to 18
dBm, only wet cleaning should be performed.
• The optical power present should be read from craft terminal Graphical User Inter-
faces (GUI), as opposed to measuring with a power meter. The reason is that even
though the power meter’s fiber pigtail may be clean, it will be making physical
contact with a system fiber that likely has dust on it. At high power levels, this
physical contact will likely cause fiber damage.
70 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Abbreviations
7 Abbreviations
AIS Alarm Indication Signal
AU Administrative Unit
BF Board Flash
CC Cross-Connection
CF Compact Flash
DEG DEGraded
ENV ENVironment
ES Errored Second
EXC EXCessive
FC Fiber Channel
IP Internet Protocol
A42022-L5977-A157-01-7620 71
Issue: 1 Issue date: April 2008
Abbreviations Troubleshooting Manual (TSMN)
MS Multiplex Section
NE Network Element
OA Optical Amplifier
PC Personal Computer
RS Regeneration Section
SC System Controller
72 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN) Abbreviations
TP Terminal Point
TU Tributary Unit
UNEQ UNEQuipped
A42022-L5977-A157-01-7620 73
Issue: 1 Issue date: April 2008
Troubleshooting Manual (TSMN)
Index
A S
Alarm list 14 SC and CF failure replacement 63
communication alarm 15 SC card replacement 60
environmental alarm 17 CF failure 62
equipment alarm 14 SC and CF failure 63
quality of service alarm 17 SC failure 61
security alarm 18 SC failure replacement 61
Security alarm 18, 57
C Switching
MIB 68
Card replacement 60
CC card 66
fan unit 67 T
filter unit 67 Troubleshooting 19
SC card 60 communication alarm 26
CC card replacement 66 environmental alarm 53
CF failure replacement 62 equipment alarm 19
Communication alarm 15, 26 quality of service alarm 53
security alarm 57
D
Data difference MIB swtiching 68 W
Document structure 11 Wet fiber cleaning 70
Dry fiber cleaning 70
E
Environmental alarm 17, 53
Equipment alarm 14, 19
F
Fan unit replacement 67
Fiber cleaning 70
dry 70
wet 70
Filter unit replacement 67
H
Hardware and data sameness MIB switching 69
M
MIB
switching 68
MIB switching 68
data difference 68
hardware and data sameness 69
Q
Quality of service alarm 17, 53
74 A42022-L5977-A157-01-7620
Issue: 1 Issue date: April 2008