Anda di halaman 1dari 74

SURPASS hiT 7080

4.1
Troubleshooting Manual (TSMN)
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 DOCUMENTATION 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.

Important Notice on Product Safety


Elevated 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 Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen 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.

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 equipment 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 problems which subsequently arise rests with the party responsible for deviating from the installation specifications.

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

Troubleshooting Manual (TSMN)

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

Troubleshooting Manual (TSMN)

Table of Contents
This document has 74 pages.
1
1.1
1.2
1.3
1.3.1
1.3.2
1.4

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Symbols used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
11
11
11
12
12
12

2
2.1
2.2
2.3
2.4
2.5

Alarm lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of service alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14
14
15
17
17
18

3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
3.1.8
3.1.9
3.1.10
3.1.11
3.1.12
3.1.13
3.1.14
3.1.15
3.1.16
3.1.17
3.1.18
3.1.19
3.1.20
3.1.21
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment_OverHeating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loss_of_Power_Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Low_Order_Capacity_Mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
No_Free_Low_Order_Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OA-Power_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OA-Pump_Bias_out_of_Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OA-Temperature_out_of_Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLL_Unlock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SC_CF_Module_Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SC_CF_Module_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP_Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPI-Temperature_out_of_Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit_Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UnitType_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VCXO_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AU_AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AU_LOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Embedded DCC channel (n) failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HCOC27-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HCOC9-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19
19
19
19
20
20
20
21
21
21
22
22
23
23
23
24
24
24
24
25
25
25
26
26
26
26
27
27
27
28

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

Troubleshooting Manual (TSMN)

3.2.7
3.2.8
3.2.9
3.2.10
3.2.11
3.2.12
3.2.13
3.2.14
3.2.15
3.2.16
3.2.17
3.2.18
3.2.19
3.2.20
3.2.21
3.2.22
3.2.23
3.2.24
3.2.25
3.2.26
3.2.27
3.2.28
3.2.29
3.2.30
3.2.31
3.2.32
3.2.33
3.2.34
3.2.35
3.2.36
3.2.37
3.2.38
3.2.39
3.2.40
3.2.41
3.2.42
3.2.43
3.2.44
3.2.45
3.2.46
3.2.47
3.2.48
3.2.49
3.2.50
3.2.51
3.2.52
3.2.53

HP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
HP-GFP_Customer_Signal_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
HP-GFP_Loss_of_Frame_Delineation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
HP-RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HP-TIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
HP-Virtual_Concatenation_LOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
HP-Virtual_Concatenation_LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
HP-Virtual_Concatenation_TLCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Link_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Loss_of_Timing_Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Loss_of_Timing_Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
LP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
LP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
LP-GFP_Customer_Signal_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
LP-GFP_Loss_of_Frame_Delineation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
LP-RFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
LP-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
LP-Virtual_Concatenation_LOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
LP-Virtual_Concatenation_LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
LP-Virtual_Concatenation_TLCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
MS_AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
MS-DCC_Connection_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
MS_DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
MS_EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
MS-K1/K2_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
MS_RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
OA_Gain_High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OA_Input_LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OA_Output_LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
OA_Output_Power_High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
PPI-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
PPI-LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
PPI-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
PPI-LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
PPI-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RPR-Exceed_Max_Stations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RPR-Link_Failure_East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
RPR-Link_Failure_West. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RPR-Miscabling_East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RPR-Miscabling_West . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
RPR-Protection_Misconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
RPR-Ringlet0_ReservedA0_Exceeding. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

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

Troubleshooting Manual (TSMN)

3.2.54
3.2.55
3.2.56
3.2.57
3.2.58
3.2.59
3.2.60
3.2.61
3.2.62
3.2.63
3.2.64
3.2.65
3.2.66
3.2.67
3.2.68
3.2.69
3.2.70
3.3
3.3.1
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5

RPR-Ringlet1_ReservedA0_Exceeding . . . . . . . . . . . . . . . . . . . . . . . . . . .
RPR-Topology_Inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RPR-Topology_Instability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS-DCC_Connection_Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS_DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS_EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS_LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS_TIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPI_LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronization_Signal_Message_Mismatch . . . . . . . . . . . . . . . . . . . . . .
System_Clock_Holdover_Longer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System_Clock_Unlocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing_Reference_Degrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing_Reference_Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TU-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ENV_MDI<n> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of service alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1-Negative_Bit-slip_TCA_15m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1-Negative_Bit-slip_TCA_24h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1-Positive_Bit-slip_TCA_15m. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1-Positive_Bit-slip_TCA_24h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PDH TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDH TCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
accountExpiredOrDisabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
logIsFull. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
logOccupancyThresholdReached. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unauthorized_Access_Attempt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsuccessful_Logins_Exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46
47
47
47
48
48
48
49
49
50
50
50
51
51
52
52
52
53
53
53
53
54
54
54
55
55
56
57
58
58
58
59
59

4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.2
4.3
4.4

Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing SC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SC card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CF card failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Both SC and CF cards fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading boot image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading software load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Downloading MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing CC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing fan unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing filter unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

60
60
61
62
63
63
64
64
66
67
67

5
5.1

MIB switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Different data configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

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

Troubleshooting Manual (TSMN)

5.2

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

6
6.1
6.2

Fiber cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Dry cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Wet cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

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

Troubleshooting Manual (TSMN)

List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7

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

List of used conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quality of service alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12
12
14
15
17
18
18

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.

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


Alarm lists
When a fault condition occurs, the relevant alarm notification will be generated and displayed on craft terminal screens. All SURPASS hiT 7080 alarms are listed in the Alarm
lists in 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

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.

1.3

Symbols and conventions


The following symbols and conventions are used in this document:

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

11

Preface

Troubleshooting Manual (TSMN)

1.3.1

Symbols used
g Used for notes, tips or additional information.

Caution: Means that the reader should be careful. In this situation, you might do something 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.

1.3.2

Conventions used
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.
Commands, screen output, file names and paths are
represented in courier.

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.

Table 1

1.4

History of changes
Issue
1
Table 2

12

List of used conventions

Issue date
April 2008

Initial version

History of changes

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

Troubleshooting Manual (TSMN)

Issue

Table 2

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

Preface

Issue date

History of changes (Cont.)

13

Alarm lists

Troubleshooting Manual (TSMN)

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

2.1

Equipment alarms: originate from specific hardware elements (e.g., traffic card, controller card, shelf, etc.)
Communication alarms: originate from termination points which represent a particular function of the network
Environmental alarms: originate from telemetry sensors that monitor conditions/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 authentication and authorization

Equipment alarms
Table 3 lists SURPASS hiT 7080 equipment alarms. Click the alarm name in the table
to jump directly to the troubleshooting procedure for that alarm.
Alarm name
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 failure

SFP_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

14

Alarm Message Text

Equipment alarms

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

Troubleshooting Manual (TSMN)

Alarm lists

Alarm name
UnitType_Mismatch

Unit type mismatch

VCXO_Failure

Voltage Control Crystal Oscillator (VCXO)


Failure

Table 3

2.2

Alarm Message Text

Equipment alarms (Cont.)

Communication alarms
Table 4 lists SURPASS hiT 7080 communication alarms. Click the alarm name in the
table to jump directly to the troubleshooting procedure for that alarm.
Alarm Name

Alarm Message Text

AU_AIS

Administrative Unit (AU) Alarm Indication


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

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

Communication alarms

15

Alarm lists

Troubleshooting Manual (TSMN)

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

16

Alarm Message Text

Communication alarms (Cont.)

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

Troubleshooting Manual (TSMN)

Alarm lists

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

2.3

Alarm Message Text

Communication alarms (Cont.)

Environmental alarms
Table 5 lists SURPASS hiT 7080 environmental alarms. Click the alarm name in the
table to jump directly to the troubleshooting procedure for that alarm.
Alarm name
ENV_MDI<n>

Table 5

2.4

Alarm Message Text


ENVironment (ENV) Miscellaneous
Discrete Input (MDI) 1 ~ 8

Environmental alarms

Quality of service alarms


Table 6 lists SURPASS hiT 7080 QoS alarms. Click the alarm name in the table to jump
directly to the troubleshooting procedure for that alarm.

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

17

Alarm lists

Troubleshooting Manual (TSMN)

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

SDH TCA

Table 6

2.5

Alarm Message Text

Quality of service alarms

Security alarms
Table 7 lists SURPASS hiT 7080 security alarms. Click the alarm name in the table to
jump directly to the troubleshooting procedure for that alarm.
Alarm name
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

18

Alarm Message Text

Security alarms

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

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

3.1.1

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

Troubleshooting instructions

3.1.2

Reboot or change the service card.

Reboot or change the SC card.

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

Equipment_OverHeating
Alarm name

Equipment_OverHeating

Default severity

Major

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.

Troubleshooting instructions
1

Verify the fan unit is working correctly.

Verify the filter unit is clean.

Verify the air-conditioning is working correctly.

Verify the equipment is working correctly.

Verify the card temperature threshold is configured properly.

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

19

Troubleshooting

Troubleshooting Manual (TSMN)

3.1.3

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

Fan_Failure
Alarm name

Fan_Failure

Default severity

Major

Alarm object

Fan unit

General information and causes The fan unit is defective.

Troubleshooting instructions

3.1.4

Verify the fans in the fan unit are working correctly.

Change the fan unit.

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

Loss_of_Power_Input
Alarm name

Loss_of_Power_Input

Default severity

Major

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.

Troubleshooting instructions

3.1.5

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

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

Low_Order_Capacity_Mismatch
Alarm name

Low_Order_Capacity_Mismatch

Default severity

Major

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.

Troubleshooting instructions

20

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

Troubleshooting Manual (TSMN)

3.1.6

Troubleshooting

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.

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.

No_Free_Low_Order_Capacity
Alarm name

No_Free_Low_Order_Capacity

Default severity

Major

Alarm object

PDH cards

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.

Troubleshooting instructions

3.1.7

Upgrade the LOCC capacity.

Delete some existing low order mapping on relevant SDH cards.

Delete some existing low order mapping on unused PDH cards and remove them
from the system to reallocate low order capacity.

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

OA-Power_Failure
Alarm name

OA_Power_Failure

Default severity

Critical

Alarm object

OA card

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

Troubleshooting instructions

3.1.8

Change the OA card.

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

OA-Pump_Bias_out_of_Range
Alarm name

OA-Pump_Bias_out_of_Range

Default severity

Major

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

21

Troubleshooting

Troubleshooting Manual (TSMN)

Alarm object

OA card

General information and causes The OA pump bias exceeds the threshold which is
specified in the OA port properties configuration.

Troubleshooting instructions

3.1.9

Verify the OA output power is set properly.

Verify the OA input power is normal.

Verify the OA card is not aging.

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

OA-Temperature_out_of_Range
Alarm name

OA-Temperature_out_of_Range

Default severity

Major

Alarm object

OA card

General information and causes The OA modules temperature exceeds the


threshold which is specified in the OA port
properties configuration.

Troubleshooting instructions

3.1.10

Verify the fan unit is working correctly.

Verify the OA setting is proper.

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

PLL_Unlock
Alarm name

PLL_Unlock

Default severity

Major

Alarm object

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


and fan unit)

General information and causes This alarm is triggered when the PLL is in the
unlock state.

Troubleshooting instructions

22

If fault occurs during card boot or synchronization, please wait till the initialization
process of the card is complete.

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

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

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

Troubleshooting Manual (TSMN)

3.1.11

Troubleshooting

Power_Failure
Alarm name

Power_Failure

Default severity

Major

Alarm object

Power module

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

Troubleshooting instructions

3.1.12

Change the shelf.

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

SC_CF_Module_Absent
Alarm name

SC_CF_Module_Absent

Default severity

Major

Alarm object

SC card

General information and causes The CF card is absent.

Troubleshooting instructions
1

Insert the CF card.


For more information, please refer to the SURPASS hiT 7080 Installation and Test
Manual (ITMN).

3.1.13

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

SC_CF_Module_Failure
Alarm name

SC_CF_Module_Failure

Default severity

Major

Alarm object

SC card

General information and causes The CF card can not be accessed.

Troubleshooting instructions
1

Change the CF card.


For more information, please refer to the SURPASS hiT 7080 Installation and Test
Manual (ITMN).

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

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

23

Troubleshooting

3.1.14

Troubleshooting Manual (TSMN)

SFP_Absent
Alarm name

SFP_Absent

Default severity

Major

Alarm object

Optical port

General information and causes The SFP module is absent.

Troubleshooting instructions

3.1.15

Insert the proper SFP module.

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

SFP_Failure
Alarm name

SFP_Failure

Default severity

Major

Alarm object

SFP module

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

Troubleshooting instructions

3.1.16

Change the SFP module.

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

SFP_Mismatch
Alarm name

SFP_Mismatch

Default severity

Major

Alarm object

SFP module

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

Troubleshooting instructions

3.1.17

24

Change to a suitable SFP module.

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

SPI-Temperature_out_of_Range
Alarm name

SPI-Temperature_out_of_Range

Default severity

Major

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

Troubleshooting Manual (TSMN)

Alarm object

Troubleshooting

STM-64 port

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

Troubleshooting instructions

3.1.18

Verify the refrigeration part and the bias current part of the laser are working correctly.

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

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

Unit_Failure
Alarm name

Unit_Failure

Default severity

Major

Alarm object

Cards

General information and causes The card is defective.

Troubleshooting instructions

3.1.19

Change the card.

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

Unit_Removal
Alarm name

Unit_Removal

Default severity

Major

Alarm object

Cards

General information and causes The card is absent.

Troubleshooting instructions

3.1.20

Insert the corresponding card.

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

UnitType_Mismatch
Alarm name

UnitType_Mismatch

Default severity

Major

Alarm object

Cards

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

25

Troubleshooting

Troubleshooting Manual (TSMN)

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

Troubleshooting instructions

3.1.21

Insert the correct type of card.

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

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

VCXO_Failure
Alarm name

VCXO_Failure

Default severity

Major

Alarm object

HOCC card

General information and causes The VCXO component on the HOCC card has
failed.

Troubleshooting instructions

3.2

Replace HOCC card.

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

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

3.2.1

AU_AIS
Alarm name

AU_AIS

Default severity

Minor

Alarm object

SDH AU

General information and causes The upstream signal is defective.

Troubleshooting instructions

3.2.2

26

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

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

AU_LOP
Alarm name

AU_LOP

Default severity

Critical

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

Troubleshooting Manual (TSMN)

Alarm object

Troubleshooting

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.

Troubleshooting instructions

3.2.3

Verify the upstream external cable connections are correct.

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

Embedded DCC channel (n) failure


Alarm name

Embedded DCC channel1 failure

Default severity

Major

Alarm object

NE

General information and causes DCC communication channel has failed.

Troubleshooting instructions

3.2.4

Verify routing configuration.

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

HCOC27-DCC_Connection_Failure
Alarm name

HCOC27-DCC_Connection_Failure

Default severity

Major

Alarm object

SDH HCOC

General information and causes

The HCOC27-DCC is disabled at one side of


the DCC link.
DCC link is down.

Troubleshooting instructions

3.2.5

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

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

HCOC9-DCC_Connection_Failure
Alarm name

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

HCOC9-DCC_Connection_Failure

27

Troubleshooting

Troubleshooting Manual (TSMN)

Default severity

Major

Alarm object

SDH HCOC

General information and causes

The HCOC9-DCC is disabled at one side of the


DCC link.
DCC link is down.

Troubleshooting instructions

3.2.6

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

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

HP-DEG
Alarm name

HP-DEG

Default severity

Minor

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.

Troubleshooting instructions

3.2.7

Verify the upstream external cabling and equipment are normal.

Verify the threshold is set correctly.

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

HP-EXC
Alarm name

HP-EXC

Default severity

Major

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.

Troubleshooting instructions

28

Verify the upstream external cabling and equipment are normal.

Verify the threshold is set correctly.

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

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

Troubleshooting Manual (TSMN)

3.2.8

Troubleshooting

HP-GFP_Customer_Signal_Failure
Alarm name

HP-GFP_Customer_Signal_Failure

Default severity

Critical

Alarm object

Ethernet Wide Area Networks (WAN) ports

General information and causes The upstream Local Area Networks (LAN) port
connectivity is down.

Troubleshooting instructions

3.2.9

Verify the upstream external cabling and equipment are normal.

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

HP-GFP_Loss_of_Frame_Delineation
Alarm name

HP-GFP_Loss_of_Frame_Delineation

Default severity

Critical

Alarm object

Ethernet WAN ports

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

Troubleshooting instructions

3.2.10

Verify the upstream connection and equipment are normal.

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

HP-PLM
Alarm name

HP-PLM

Default severity

Critical

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.

Troubleshooting instructions

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

29

Troubleshooting

3.2.11

Troubleshooting Manual (TSMN)

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

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

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

HP-RDI
Alarm name

HP-RDI

Default severity

Minor

Alarm object

SDH HP

General information and causes The downstream NE receives the malfunctioning


signal.

Troubleshooting instructions

3.2.12

React to the far-end alarms.

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

HP-TIM
Alarm name

HP-TIM

Default severity

Critical

Alarm object

SDH HP

General information and causes The received path trace identifier does not match
the expected value.

Troubleshooting instructions

3.2.13

Verify the expected path trace identifier is correct.

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

HP-UNEQ
Alarm name

HP-UNEQ

Default severity

Critical

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.

Troubleshooting instructions

30

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

Troubleshooting Manual (TSMN)

3.2.14

Troubleshooting

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

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

HP-Virtual_Concatenation_LOA
Alarm name

HP-Virtual_Concatenation_LOA

Default severity

Critical

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.

Troubleshooting instructions

3.2.15

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 connection route.

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

HP-Virtual_Concatenation_LOM
Alarm name

HP-Virtual_Concatenation_LOM

Default severity

Critical

Alarm object

HP VCG member

General information and causes One VCG member failed or was received at the
local node with errors.

Troubleshooting instructions

3.2.16

Check VCG member for relevant terminal point alarms and correct them. Verify if
HP-Virtual_Concatenation_LOM alarm still exists.

Check performance monitoring for relevant VCG member terminal point for errors
and correct them. Verify if HP-Virtual_Concatenation_LOM alarm still exists.

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

HP-Virtual_Concatenation_TLCT
Alarm name

HP-Virtual_Concatenation_TLCT

Default severity

Critical

Alarm object

HP VCG

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

31

Troubleshooting

Troubleshooting Manual (TSMN)

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

Troubleshooting instructions

3.2.17

Verify the connection to the upstream equipment is normal.

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

Link_Failure
Alarm name

Link_Failure

Default severity

Critical

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.

Troubleshooting instructions

32

Verify the connections of the physical layer are correct.

Verify the connectors are clean.

Verify the fiber type is correct.

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

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

Troubleshooting Manual (TSMN)

3.2.18

Troubleshooting

Loss_of_Timing_Input
Alarm name

Loss_of_Timing_Input

Default severity

Critical

Alarm object

HOCC card

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


station clock port.

Troubleshooting instructions

3.2.19

Verify the connections of the physical layer are correct.

Verify the cables and connectors are not damaged.

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

Loss_of_Timing_Output
Alarm name

Loss_of_Timing_Output

Default severity

Critical

Alarm object

HOCC card

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

Troubleshooting instructions

3.2.20

Verify the synchronization configuration is correct.

Verify the external timing input is normal.

Change the local equipment using this timing output.

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

LP-DEG
Alarm name

LP-DEG

Default severity

Minor

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.

Troubleshooting instructions

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

33

Troubleshooting

3.2.21

Troubleshooting Manual (TSMN)

Verify the upstream external cabling and equipment.

Verify the threshold in the management system.

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

LP-EXC
Alarm name

LP-EXC

Default severity

Major

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 upstream
external cabling or equipment.

Troubleshooting instructions

3.2.22

Verify upstream external cabling and equipment.

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

LP-GFP_Customer_Signal_Failure
Alarm name

LP-GFP_Customer_Signal_Failure

Default severity

Critical

Alarm object

Ethernet WAN ports

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

Troubleshooting instructions

3.2.23

Verify the upstream external cabling and equipment are normal.

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

LP-GFP_Loss_of_Frame_Delineation
Alarm name

LP-GFP_Loss_of_Frame_Delineation

Default severity

Critical

Alarm object

Ethernet WAN ports

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

Troubleshooting instructions

34

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

Troubleshooting Manual (TSMN)

3.2.24

Troubleshooting

Verify the upstream connection and equipment are normal.

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

LP-PLM
Alarm name

LP-PLM

Default severity

Major

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.

Troubleshooting instructions

3.2.25

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

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.

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

LP-RDI
Alarm name

LP-RDI

Default severity

Minor

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

Troubleshooting instructions

3.2.26

No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).

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

LP-RFI
Alarm name

LP-RFI

Default severity

Minor

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

35

Troubleshooting

Troubleshooting Manual (TSMN)

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 path
Remote Failure.

Troubleshooting instructions

3.2.27

No alarms in the reporting node. React on the far-end alarms. Follow the clearing
actions for those alarm(s).

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

LP-TIM
Alarm name

LP-TIM

Default severity

Critical

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.

Troubleshooting instructions

3.2.28

Verify cross-connections.

Verify tributary cables and tributary units.

Verify the expected trace in the management system.

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

LP-UNEQ
Alarm name

LP-UNEQ

Default severity

Critical

Alarm object

SDH LP

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

Troubleshooting instructions

36

Confirm or create the cross connection settings at the remote side to be consistent
with the local side.

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

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

Troubleshooting Manual (TSMN)

Troubleshooting

g When defining or changing a cross-connection this alarm will almost inevitably


come up as it is practically impossible to issue the changes at both sides at the same
moment.

3.2.29

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.

LP-Virtual_Concatenation_LOA
Alarm name

LP-Virtual_Concatenation_LOA

Default severity

Critical

Alarm object

LP VCG

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

Troubleshooting instructions

3.2.30

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 connection route.

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

LP-Virtual_Concatenation_LOM
Alarm name

LP-Virtual_Concatenation_LOM

Default severity

Critical

Alarm object

LP VCG member

General information and causes One VCG member failed or was received at the
local node with errors.

Troubleshooting instructions
1

Check VCG member for relevant terminal point alarms and correct them. Verify if
LP-Virtual_Concatenation_LOM alarm still exists.

Check performance monitoring for relevant VCG member terminal point for errors
and correct them. Verify if LP-Virtual_Concatenation_LOM alarm still exists.

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

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

37

Troubleshooting

3.2.31

Troubleshooting Manual (TSMN)

LP-Virtual_Concatenation_TLCT
Alarm name

LP-Virtual_Concatenation_TLCT

Default severity

Critical

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

Troubleshooting instructions

3.2.32

Verify connection to the upstream equipment.

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

MS_AIS
Alarm name

MS_AIS

Default severity

Minor

Alarm object

SDH MS

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

Troubleshooting instructions

38

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

Troubleshooting Manual (TSMN)

3.2.33

Troubleshooting

Clear the upstream inserted AIS signal.

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

MS-DCC_Connection_Failure
Alarm name

MS-DCC_Connection_Failure

Default severity

Major

Alarm object

SDH MS

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

Troubleshooting instructions

3.2.34

Verify the MS-DCC is enabled and working normally at both ends of the MS DCC
link.

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

MS_DEG
Alarm name

MS_DEG

Default severity

Minor

Alarm object

SDH MS

General information and causes A degraded signal defect is detected when the
equivalent BER exceeds a preset threshold of 10-x,
x = 5, 6, 7, 8, 9.

Troubleshooting instructions

3.2.35

Verify the upstream external cabling and equipment are normal.

Verify the threshold is set correctly.

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

MS_EXC
Alarm name

MS_EXC

Default severity

Major

Alarm object

SDH MS

General information and causes An excessive error defect is detected when the
equivalent BER exceeds a preset threshold of 10-x,
x = 3, 4, 5.

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

39

Troubleshooting

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.2.36

Verify the upstream external cabling and equipment are normal.

Verify the threshold is set correctly.

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

MS-K1/K2_Mismatch
Alarm name

MS-K1/K2_Mismatch

Default severity

Major

Alarm object

SDH MS

General information and causes The protection switching is not successful.

Troubleshooting instructions

3.2.37

Verify the conditions of protection switching are normal.

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

MS_RDI
Alarm name

MS_RDI

Default severity

Minor

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

Troubleshooting instructions

40

Verify the upstream external cabling and equipment are normal.

Verity the local transmitting equipment is working normally.

Clear the indicated faults in the far-end node.

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

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

Troubleshooting Manual (TSMN)

3.2.38

Troubleshooting

OA_Gain_High
Alarm name

OA_Gain_High

Default severity

Major

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

Troubleshooting instructions

3.2.39

Verify the output power of the OA is set properly.

Verity the input power of the OA is normal.

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

OA_Input_LOS
Alarm name

OA_Input_LOS

Default severity

Critical

Alarm object

OA ports

General information and causes

The cable ruptures.


The optical connector is dirty.
The input optical power is below the pre-defined
power threshold.

Troubleshooting instructions

3.2.40

Verify the connections of the physical layer are correct.

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

Verify the cables and connectors are not damaged.

Verify the pre-defined input power threshold is proper.

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

OA_Output_LOS
Alarm name

OA_Output_LOS

Default severity

Critical

Alarm object

OA ports

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

41

Troubleshooting

Troubleshooting Manual (TSMN)

General information and causes

The local transmitting module fails.


The output optical power is below the predefined power threshold.

Troubleshooting instructions

3.2.41

Verify the local transmitting module is normal.

Verify the pre-defined output power threshold is proper.

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

OA_Output_Power_High
Alarm name

OA_Output_Power_High

Default severity

Major

Alarm object

OA ports

General information and causes

20 dB POA: Output power > -9 dBm


13 dBm BOA: Output power > 14 dBm
15 dBm BOA: Output power > 16 dBm
18 dBm BOA: Output power > 19 dBm

Troubleshooting instructions

3.2.42

Verify the gain of the OA is set properly.

Verify the input power of the OA is proper.

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

PPI-AIS
Alarm name

PPI-AIS

Default severity

Minor

Alarm object

Port

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

Troubleshooting instructions

42

Verify the upstream external cabling and equipment.

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

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

Troubleshooting Manual (TSMN)

3.2.43

Troubleshooting

PPI-LOF
Alarm name

PPI-LOF

Default severity

Critical

Alarm object

PDH Port

General information and causes Alignment to the frame structure of the received
E1/E3/DS3 signal is not possible.

Troubleshooting instructions

3.2.44

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

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

PPI-LOM
Alarm name

PPI-LOM

Default severity

Critical

Alarm object

PDH Port

General information and causes Alignment to the Cyclic Redundancy Check (CRC)
Multiframe structure of the received E1 signal is not
possible.

Troubleshooting instructions

3.2.45

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

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

PPI-LOS
Alarm name

PPI-LOS

Default severity

Critical

Alarm object

PDH Port

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.

Troubleshooting instructions

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

43

Troubleshooting

3.2.46

Troubleshooting Manual (TSMN)

Verify the connections of the physical layer.

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

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

PPI-RDI
Alarm name

PPI-RDI

Default severity

Minor

Alarm object

PDH Port

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.

Troubleshooting instructions

3.2.47

Verify operation of the transmitter in the local station.

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

RPR-Exceed_Max_Stations
Alarm name

RPR-Exceed_Max_Stations

Default severity

Critical

Alarm object

RPR Card

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

Troubleshooting instructions

3.2.48

Remove stations which exceed the maximum limit of 32.

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

RPR-Link_Failure_East
Alarm name

RPR-Link_Failure_East

Default severity

Critical

Alarm object

RPR Card

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

Troubleshooting instructions

44

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

Troubleshooting Manual (TSMN)

3.2.49

Troubleshooting

Verify that the optical fiber or the SDH cross-connection used for the east RPR path
is normal.

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

RPR-Link_Failure_West
Alarm name

RPR-Link_Failure_West

Default severity

Critical

Alarm object

RPR Card

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

Troubleshooting instructions

3.2.50

Verify that the optical fiber or the SDH cross-connection used for the west RPR path
is normal.

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

RPR-Miscabling_East
Alarm name

RPR-Miscabling_East

Default severity

Critical

Alarm object

RPR Card

General information and causes The east link of one RPR station is wrongly
connected to the same side (east link) of another
RPR station.

Troubleshooting instructions

3.2.51

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.

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

RPR-Miscabling_West
Alarm name

RPR-Miscabling_West

Default severity

Critical

Alarm object

RPR Card

General information and causes The west link of one RPR station is wrongly
connected to the same side (west link) of another
RPR station.

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

45

Troubleshooting

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.2.52

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.

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

RPR-Protection_Misconfig
Alarm name

RPR-Protection_Misconfig

Default severity

Critical

Alarm object

RPR Card

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

Troubleshooting instructions

3.2.53

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.

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

RPR-Ringlet0_ReservedA0_Exceeding
Alarm name

RPR-Ringlet0_ReservedA0_Exceeding

Default severity

Major

Alarm object

RPR Card

General information and causes A0 bandwidth reserved on RPR ringlet0 exceeds


the link rate.

Troubleshooting instructions

3.2.54

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

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

RPR-Ringlet1_ReservedA0_Exceeding
Alarm name

RPR-Ringlet1_ReservedA0_Exceeding

Default severity

Major

Alarm object

RPR Card

General information and causes A0 bandwidth reserved on RPR ringlet1 exceeds


the link rate.

46

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

Troubleshooting Manual (TSMN)

Troubleshooting

Troubleshooting instructions

3.2.55

Re-configure the A0 bandwidth reserved on RPR ringlet1 and make sure not to
exceed the available link rate.

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

RPR-Topology_Inconsistent
Alarm name

RPR-Topology_Inconsistent

Default severity

Critical

Alarm object

RPR Card

General information and causes Inconsistent topology of the RPR ring is usually
caused by the duplicate Media Access Control
(MAC) addresses.

Troubleshooting instructions

3.2.56

Re-configure the duplicated RPR stations MAC address.

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

RPR-Topology_Instability
Alarm name

RPR-Topology_Instability

Default severity

Critical

Alarm object

RPR Card

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.

Troubleshooting instructions

3.2.57

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.

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

RS-DCC_Connection_Failure
Alarm name

RS-DCC_Connection_Failure

Default severity

Major

Alarm object

SDH RS

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

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

47

Troubleshooting

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.2.58

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

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

RS_DEG
Alarm name

RS-DEG

Default severity

Minor

Alarm object

SDH RS

General information and causes A degraded signal defect is detected when the
equivalent BER exceeds a preset threshold of 10-x,
x = 6, 7, 8, 9.

Troubleshooting instructions

3.2.59

Verify the upstream external cabling and equipment are normal.

Verify the threshold is set correctly.

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

RS_EXC
Alarm name

RS_EXC

Default severity

Major

Alarm object

SDH RS

General information and causes An excessive error defect is detected when the
equivalent BER exceeds a preset threshold of 10-5.

Troubleshooting instructions

3.2.60

48

Verify the upstream external cabling and equipment are normal.

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

RS_LOF
Alarm name

RS_LOF

Default severity

Critical

Alarm object

SDH RS

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting

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

3.2.61

Verify the intermediate fiber is normal.

Verify the connectors are clean.

Loop the signal from the transmitter to the receiver. Verify no LOF fault is reported.

Verify the port signal level is proper.

Verify the transmitter in the far-end is normal.

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

RS_TIM
Alarm name

RS_TIM

Default severity

Critical

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.

Troubleshooting instructions

3.2.62

Verify the line cables are connected correctly by interpreting the received STM-N RS
trace identifiers.

Verify the expected RS trace identifier is correct.

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

SPI_LOS
Alarm name

SPI_LOS

Default severity

Critical

Alarm object

SDH SPI

General information and causes

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

The fiber ruptures.


The optical connectors are dirty.
The upstream far-end station fails.

49

Troubleshooting

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.2.63

Verify the connections of the physical layer are correct.

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

Verify the connectors are clean.

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

Synchronization_Signal_Message_Mismatch
Alarm name

Synchronization_Signal_Message_Mismatch

Default severity

Major

Alarm object

HOCC card

General information and causes The SSM byte is invalid.

Troubleshooting instructions

3.2.64

Verify the SSM byte value is a legal value.

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

System_Clock_Holdover_Longer
Alarm name

System_Clock_Holdover_Longer

Default severity

Warning

Alarm object

HOCC card

General information and causes The system clock is running in the holdover mode
and the holdover time is longer than 24 hours.

Troubleshooting instructions

3.2.65

50

Repair the failed timing reference.

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

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

System_Clock_Unlocked
Alarm name

System_Clock_Unlocked

Default severity

Major

Alarm object

HOCC card

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting

All selected timing references are lost or have


failed.
The system clock mode has been changed
from the locked mode to the holdover or freerunning mode manually.

Troubleshooting instructions

3.2.66

Verify the selected timing reference works normally.

Re-select a valid timing reference.

Set the system clock working mode as locked.

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

Timing_Reference_Degrade
Alarm name

Timing_Reference_Degrade

Default severity

Minor

Alarm object

Input clock reference

General information and causes

The frequency offset of the timing source is out


of range.
The phase change of the timing source is
abnormal.

Troubleshooting instructions

3.2.67

Verify the upstream related equipment is working normally.

Verify the local timing input equipment is working normally.

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

Timing_Reference_Failure
Alarm name

Timing_Reference_Failure

Default severity

Major

Alarm object

Input clock reference

General information and causes The reference clock fails.

Troubleshooting instructions
1

Verify the upstream external cabling and equipment are normal.

Verify the local timing input equipment is working normally.

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

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

51

Troubleshooting

3.2.68

Troubleshooting Manual (TSMN)

TU-AIS
Alarm name

TU-AIS

Default severity

Minor

Alarm object

SDH TU

General information and causes In one of the upstream nodes a defect is detected
which led to the insertion of the alarm indication
signal.

Troubleshooting instructions

3.2.69

Verify upstream external cabling and equipment.

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

TU-LOM
Alarm name

TU-LOM

Default severity

Critical

Alarm object

SDH TU

General information and causes Alignment to the multiframe structure of the


received VC-4 signal is not possible. Therefore VC12 overhead and payload data cannot be extracted.

Troubleshooting instructions

3.2.70

Verify upstream external cabling and equipment.

Using the management system, check if unit failure is reported for the unit generating the multi-frame alignment signal. In that NE, remove the unit and replace it with
a new one.

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 multiframe contains the faulty unit.

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

TU-LOP
Alarm name

TU-LOP

Default severity

Critical

Alarm object

SDH TU

General information and causes No valid tributary unit pointer interpretation


obtained in the received signal.

52

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

Troubleshooting Manual (TSMN)

Troubleshooting

Troubleshooting instructions

3.3

Verify upstream external cabling and equipment.

Verify whether the TP Multiplexer structure of the both ends of the stream is the
same.

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

Environmental alarms
The environmental alarm is listed in the following sub-chapter.

3.3.1

ENV_MDI<n>
Alarm name

EVN_MDI<n>

Default severity

Warning

Alarm object

MDI module

General information and causes The states of the MDI items are changed.

Troubleshooting instructions

3.4

Keep the states of the MDI items same with what is pre-defined.

Verify the MDI items are pre-defined properly.

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

Quality of service alarms


The quality of service alarms are listed in the following sub-chapters.

3.4.1

E1-Negative_Bit-slip_TCA_15m
Alarm name

E1-Negative_Bit-slip_TCA_15m

Default severity

Minor

Alarm object

PDH E1

General information and causes The clock frequency of the E1 service is faster than
the frequency of the system clock.

Troubleshooting instructions
1

Verify the clock frequency of E1 Ports.

Verify whether the system clock is in locked status.

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

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

53

Troubleshooting

Troubleshooting Manual (TSMN)

3.4.2

E1-Negative_Bit-slip_TCA_24h
Alarm name

E1-Negative_Bit-slip_TCA_24h

Default severity

Minor

Alarm object

PDH E1

General information and causes The clock frequency of the E1 service is faster than
the frequency of the system clock.

Troubleshooting instructions

3.4.3

Verify the clock frequency of E1 Ports.

Verify whether the system clock is in locked status.

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

E1-Positive_Bit-slip_TCA_15m
Alarm name

E1-Positive_Bit-slip_TCA_15m

Default severity

Minor

Alarm object

PDH E1

General information and causes The clock frequency of the E1 service is slower than
the frequency of the system clock.

Troubleshooting instructions

3.4.4

Verify the clock frequency of E1 Ports.

Verify whether the system clock is in locked status.

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

E1-Positive_Bit-slip_TCA_24h
Alarm name

E1-Positive_Bit-slip_TCA_24h

Default severity

Minor

Alarm object

PDH E1

General information and causes The clock frequency of the E1 service is slower than
the frequency of the system clock.

Troubleshooting instructions

54

Verify the clock frequency of E1 Ports.

Verify whether the system clock is in locked status.

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

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

Troubleshooting Manual (TSMN)

3.4.5

Troubleshooting

Ethernet TCA
Alarm name

Ethernet TCA

Default severity

Minor

Alarm object

Monitored performance parameter

General information and causes SURPASS hiT 7080 monitors the Ethernet
performance parameters in order to calculate the
transmission quality:

The bad packet rate

The range of the threshold is from 0% to 99%.


The default threshold is 10%.
A bad parameter rate exceeds its user-defined
threshold.

Troubleshooting instructions

3.4.6

Verify the upstream external cable and equipment are normal.

Verify the upstream NE sends the excessive bad bytes or packets on purpose.

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

PDH TCA
Alarm name

PDH TCA

Default severity

Minor

Alarm object

Monitored performance parameter

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

55

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, 24hour 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

3.4.7

56

Verify the upstream external cable and equipment are normal.

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

SDH TCA
Alarm name

SDH TCA

Default severity

Minor

Alarm object

Monitored performance parameter

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, 24hour 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

3.5

Verify the upstream external cable and equipment are normal.

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

Security alarms
The security alarms are listed in the following sub-chapters.

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

57

Troubleshooting

Troubleshooting Manual (TSMN)

3.5.1

accountExpiredOrDisabled
Alarm name

accountExpiredOrDisabled

Default severity

Minor

Alarm object

NE

General information and causes This alarm is triggered because:

A specific account has reached its configured


expiration date
Account has been disabled due to SNMPv3
error detection

Troubleshooting instructions

3.5.2

If the account has expired - enable the account using the LCT and set a new expiration date.

If the account was automatically disabled by SNMPv3 - verify the security log for
reason of account suspension and if desired re-enable the user.

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

logIsFull
Alarm name

logIsFull

Default severity

Major

Alarm object

NE

General information and causes Security log for tracking security and configuration
related events has reached its maximum number
of entries. All entries past this point will either be
dropped or replace earliest entries.

Troubleshooting instructions

3.5.3

58

Upload log file and select option to delete log after upload.

Increase size of security file log using LCT.

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

logOccupancyThresholdReached
Alarm name

logOccupancyThresholdReached

Default severity

Minor

Alarm object

NE

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

3.5.4

Upload log file and select option to delete log after upload.

Increase size of security file log using LCT.

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

Unauthorized_Access_Attempt
Alarm name

Unauthorized_Access_Attempt

Default severity

Minor

Alarm object

NE

General information and causes The Simple Network Management Protocol


(SNMP) engine detects unauthorized access to the
system.

Troubleshooting instructions

3.5.5

Track down the source of the attempt.

In the LCT, go the User Administration window (NE Security > NE User Management). Clear the alarm manually by right-clicking the desired user and selecting
Reset Unauthorized Access Counter from the context menu.

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

Unsuccessful_Logins_Exceeded
Alarm name

Unsuccessful_Logins_Exceeded

Default severity

Major

Alarm object

NE

General information and causes 5 or more unsuccessful login attempts for the same
user account.

Troubleshooting instructions
1

In the LCT, go the User Administration window (NE Security > NE User Management). 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.

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

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

59

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 illuminated.
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), Commissioning Manual (COMN), and Operating Manual (OMN).

4.1

Replacing SC card
Each NE includes an SC card, which functions as the central management controller for
the NE. Replacement of the SC card requires special care since it contains a fieldreplaceable CF card used for persistent storage of the MIB and system software. Card
replacement procedures vary, depending on the failure scenario.
These different scenarios are as follows:

SC card failure
CF card failure
Both the SC and CF cards fail

WARNING!
When an SC card is removed from the shelf, the management system will lose connectivity to the NE.
During this time, the management interface is not functional.
Before the SC card replacement, the following preparation should be done:

60

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

Troubleshooting Manual (TSMN)

Card replacement

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.

The Hyper Terminal should be installed and properly set on the PC


See ........... The SURPASS hiT 7080 Commissioning Manual (COMN).

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.

The unzip software like winzip or winrar should be installed on the PC.

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.

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.

4.1.1

SC card failure
To replace the SC card, complete the following steps:
1

Remove the faulty SC card.

Remove the CF card from the faulty SC card.


See ........... The SURPASS hiT 7080 Installation and Test Manual (ITMN).

Insert the original CF card into a new SC card.


See ........... The SURPASS hiT 7080 Installation and Test Manual (ITMN).

Insert the new SC card.


The system will automatically reboot.

During the system reboot, press <b> to stop the boot process when the Hyper
Terminal shows the countdown 5 4 3 2 1 ... .

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.
The Boot Mode window is opened in the Hyper Terminal.
6

Press <f> to enter the Flash Commands window.

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

61

Card replacement

Troubleshooting Manual (TSMN)

Press <1> to format the board flash in the SC card.

After the formatting finishes, press <x> to return to the Boot Mode window.

Download the boot image from the PC to the SC card.


See ........... Steps in Chapter 4.1.4.

10 Press <i> to enter the IP Configuration window.


11 Press <1> and set the boot device as auto.
12 Press <x> to return to the Boot Mode window.
13 Press <r> to reboot the system and press <y> to confirm.
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!

4.1.2

CF card failure
To replace the CF card, complete the following steps:
1

Remove the SC card.

Remove the faulty CF card from the SC card.


See ........... The SURPASS hiT 7080 Installation and Test Manual (ITMN).

Insert a new CF card into the SC card.


See ........... The SURPASS hiT 7080 Installation and Test Manual (ITMN).

Insert the new SC card.


The system will automatically reboot.

During the system reboot, press <b> to stop the boot process when the Hyper
Terminal shows the countdown 5 4 3 2 1 ... .

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.
The Boot Mode window is opened in the Hyper Terminal.
6

Press <f> to enter the Flash Commands window.

Press <2> to format the CF in the SC card.

After the formatting finishes, press <x> to return to the Boot Mode window.

Download the boot image from the PC to the SC card.


See ........... Steps in Chapter 4.1.4.

10 Press <i> to enter the IP Configuration window.


11 Press <1> and set the boot device as auto.
12 Press <x> to return to the Boot Mode window.
13 Press <r> to reboot the system and press <y> to confirm.

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!

4.1.3

Both SC and CF cards fail


To replace the SC and CF card, complete the following steps:
1

Remove the faulty SC card.

Insert a new SC card with a new CF card.


The system will automatically reboot.

During the system reboot, press <b> to stop the boot process when the Hyper
Terminal shows the countdown 5 4 3 2 1 ... .

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.
The Boot Mode window is opened in the Hyper Terminal.
4

Press <f> to enter the Flash Commands window.

Press <1> to format the board flash in the SC card.

Press <2> to format the CF in the SC card.

Press <x> to return to the Boot Mode window.

Press <r> to reboot the system and press <y> to confirm.

Download the boot image from the PC to the SC card.


See ........... Steps in Chapter 4.1.4.

10 Download the software load from the PC to the SC card.


See ........... Steps in Chapter 4.1.5.
11 Upload the MIB from the PC to the SC card.
See ........... Steps in Chapter 4.1.6.
12 Press <c> to enter the Command Mode window.
13 In the boot area, input @ and press <Enter> to reboot the system.
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!

4.1.4

Downloading boot image


To download the boot image from the PC to the SC card, complete the following steps:

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

63

Card replacement

Troubleshooting Manual (TSMN)

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

Press <i> to enter the IP Configuration window.

Press <1> and set the boot device as fe.

Press <2> and enter the NE Ethernet Internet Protocol (IP) address.

Press <3> and enter the NE Ethernet IP mask address.

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.

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.

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.

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!

4.1.5

Downloading software load


To download the software load from the PC to the SC card, complete the following steps:
1

Set the FTP configuration.


See ........... Step 1 to step 8 in Chapter 4.1.4.

In the IP Configuration window, press <6> and enter the corresponding software
load file name (e.g., PBm1r40bxxx.bld).

Press <x> to return to the Boot Mode window.

Press <r> to reboot the system and press <y> to confirm.

After the system has finished rebooting, veriify the software version is correct
through the NE LCT system using the TNMS CT or TNMS Core.

PROCEDURE COMPLETE!

4.1.6

Downloading MIB
To download the MIB from the PC to the SC card, complete the following steps:

64

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

Troubleshooting Manual (TSMN)

Card replacement

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

Press <i> to enter the IP Configuration window.

Press <2> and enter the NE Ethernet Internet Protocol (IP) address.

Press <3> and enter the NE Ethernet IP mask address.

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.

Press <x> to return to the Boot Mode window.

On the PC, select Start > Programs > Accessories > Command Prompt menu
item.
The Command Prompt window is opened.

Use the following commands:


cd

To enter the local working directory.

ftp

To login to the NE Ethernet IP address.


The NE is an FTP server.

Enter the FTP user account name and password for the PC to login to the FTP
server on the NE.
The NE is an FTP server.
The default user name is root.
The default password is <Enter>.

10 Use the following commands:


cd /cfg/

To enter the default MIB directory, named cfg.

mkdir mib

To create the sub-directory of cfg, named mib.

cd mib

To enter the directory, /cfg/mib.

mkdir active

To create the sub-directory of mib, named active.

cd active

To enter the directory, /cfg/mib/active.

bin

To set the binary file transport mode.

prom

To turn off the interactive mode.

put ghead.txt

To upload the file, ghead.txt, from the local working root


directory to the directory, /cfg/mib/active.

put headfile.txt

To upload the file, headfile.txt, from the local working root


directory to the directory, /cfg/mib/active.

mkdir ne

To create the sub-directory of active, named ne.

cd ne

To enter the directory, /cfg/mib/active/ne.

lcd ne

To enter the local working directory,


%Local_working_drive%\ne.

mput *.*

To upload all the files from the local working directory,


%Local_working_drive%\ne, to the directory,
/cfg/mib/active/ne.

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

65

Card replacement

Troubleshooting Manual (TSMN)

dir

To verify all the files have been uploaded successfully.

cd ..

To return to the directory, /cfg/mib/active.

mkdir gmpls

To create the sub-directory of active, named gmpls.

cd gmpls

To enter the directory, /cfg/mib/active/gmpls.

lcd ..

To return to the local working root directory.

lcd gmpls

To enter the local working directory,


%Local_working_drive%\gmpls.

mput *.*

To upload all the files from the local working directory,


%Local_working_drive%\gmpls, to the directory,
/cfg/mib/active/gmpls.

dir

To verify all the files have been uploaded successfully.

pwd

To check the path.

bye

To logout the FTP server on the NE.

The MIB file package on the NE includes the following files:

/cfg/mib/active/ghead.txt
/cfg/mib/active/headfile.txt
/cfg/mib/active/ne/*.*
/cfg/mib/active/gmpls/*.*

PROCEDURE COMPLETE!

4.2

Replacing CC card
Each NE has CC cards, which function as the cross-connection and timing management
controller. Replacement of the CC card requires special care since it deals with all traffic
of the NE.
To replace the CC card, complete the following steps:
1

Before replacing the CC card, verify that the traffic has been transfered to the CC
card which is NOT being replaced via the LCT.
When the working CC card fails, the traffic will switch to the protection card automatically.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Remove the faulty CC card.

Insert a new CC card.

If the CC card is switched manually in Step 1, clear the switch request command set
in Step 1 via the LCT.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

PROCEDURE COMPLETE!

g There must be three minutes between two consecutive CC card switches to ensure
no traffic hit.

66

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

Troubleshooting Manual (TSMN)

4.3

Card replacement

Replacing fan unit


Each NE includes two fan units each with three fans, which are used to cool the system.
Replacement of the fan unit requires special care and th following requirements must be
fulfilled:

The whole fan unit must be replaced if any fan fails.


The system can not work without any fan unit.
The system can still work normally for 16 hours when only one fan unit fails and the
failed unit is still inserted in the NE.
The system can not work when a fan unit is absent for more than two minutes. The
action of exchanging the faulty fan unit must be finished within two minutes.

Detailed instructions for replacing the fan unit can be found in the SURPASS hiT 7080
Installation and Test Manual (ITMN).

4.4

Replacing filter unit


Each NE includes one filter unit, which functions as protection for the system from the
environmental dust or other airborne contaminants. Replacement of the fan unit requires
special care since and the following requirements must be fulfilled:

The filter unit replacement must be treated as a periodic maintenance procedure to


ensure that the fans are able to sustain optimum shelf operating temperature.
It is recommended to clean the filter unit every two months, otherwise the efficiency
of the fan unit may be reduced.
The filter unit can be cleaned by water, but must be dry when placed back.
The filter unit must be placed back within 24 hours, otherwise the system may be
polluted by the dust.

Detailed instructions for replacing the filter unit can be found in the SURPASS hiT 7080
Installation and Test Manual (ITMN).

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

67

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

5.1

Different data configuration


To switch the MIB from the old to the new configuration, complete the following steps:
1

Upload the MIB of the old configuration from the NE to the local PC to backup the
old configuration.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Download the MIB of the new configuration from the local PC to the NE.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Switch the new MIB into the active MIB.


See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Activate the new configuration in the MIB in the following two methods:

Method 1:
Cold reboot the NE to activate all the new configuration in the MIB.
g All traffic will be dropped while the NE is cold rebooting.
Method 2:
1. Warm reboot the NE to activate the configuration in the MIB except the new
data configuration.
g The Ethernet traffic related to the new data configuration will not be
normal after the NE warm reboots.
2. Cold reboot all the Ethernet cards related to the new data configuration to
activate the new data configuration.
g The Ethernet traffic will be dropped while the card is cold rebooting.

See ........... The SURPASS hiT 7080 Operating Manual (OMN).


PROCEDURE COMPLETE!

68

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

Troubleshooting Manual (TSMN)

5.2

MIB switching

Same data configuration


To switch the MIB from the old to the new configuration, complete the following steps:
1

Upload the MIB of the old configuration from the NE to the local PC to backup the
old configuration.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Download the MIB of the new configuration from the local PC to the NE.
See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Switch the new MIB into the active MIB.


See ........... The SURPASS hiT 7080 Operating Manual (OMN).

Warm reboot the NE to activate the new configuration in the MIB.


See ........... The SURPASS hiT 7080 Operating Manual (OMN).

PROCEDURE COMPLETE!

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

69

Fiber cleaning

Troubleshooting Manual (TSMN)

6 Fiber cleaning
Two cleaning methods exist: wet cleaning and dry cleaning. General rules are as
follows:

6.1

It is always preferable to clean fiber ends when there is no optical power being delivered. 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 Interfaces (GUI), as opposed to measuring with a power meter. The reason is that even
though the power meters 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.

Dry cleaning
Dry cleaning can be performed for connectors without optical power and for connectors
with an optical power level up to 15 dBm. Use the CLETOP Cleaning Sticks, Type 1.25
mm (NTT-ME, Alcoa Fujikura) strictly adhering to the following rules:

6.2

Do not use cleaning sticks from other manufactures (risk of connector damage).
Only remove the cleaning stick from the package immediately before use.
Use the cleaning stick only once.
Insert the stick into the fiber adapter and press it gently to the connector face.
Avoid pressing too hard on the cleaning stick as this may cause the cotton covering
to fray.
Clean by turning the stick slowly. Do not turn more than five minutes; otherwise, it is
possible that the cotton covering will be damaged.

Wet cleaning
Wet cleaning can be performed for fiber without optical power and for fiber with an
optical power level up to 18 dBm. Use the Westover Scientific CleanBlast system (WOSFCL-P1100) and cleaning fluid FCLP-SOL1 according to the manufacturers instructions.

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

BBE

Background Block Error

BER

Bit Error Rate

BF
BOA

Board Flash
Booster Optical Amplifier

CC

Cross-Connection

CF

Compact Flash

COMN

Commissioning Manual

CRC

Cyclic Redundancy Check

DCC

Data Communication Channel

DEG

DEGraded

ENV

ENVironment

ES
EXC
FC

Errored Second
EXCessive
Fiber Channel

FTP

File Transport Protocol

GFP

Generic Framing Procedure

GUI

Graphical User Interface

HCOC

High Capacity Overhead Channel

HOCC

High Order Cross Connection

HP

High order Path

IP

Internet Protocol

LAN
LCAS

Local Area network


Link Capacity Adjustment Scheme

LCT

Local Craft Terminal

LED

Light Emitting Diode

LOA

Loss Of Alignment

LOF

Loss Of Frame

LOM

Loss Of Multiframe

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

71

Abbreviations

Troubleshooting Manual (TSMN)

LOP

Loss Of Pointer

LOS

Loss Of Signal

LP

Low order Path

ITMN

Installation and Test Manual

MAC

Media Access Control

MDI

Miscellaneous Discrete Input

MIB

Management Information Base

MS

Multiplex Section

NE

Network Element

OA

Optical Amplifier

OMN
PC

Personal Computer

PDH

Plesiochronous Digital Hierarchy

PLM

PayLoad Mismatch

POA

Pre-Optical Amplifier

PLL

Phase Lock Loop

PPI

PDH Physical Interface

QoS

Quality of Service

RDI

Remote Defect Indication

RFI

Remote Failure Indication

RPR

Resilient Packet Ring

RS

Regeneration Section

SC

System Controller

SDH

Synchronous Digital Hierarchy

SES

Severely Errored Second

SFP

Small Factor Pluggable

SI-E

System Interface with Engineering Order Wire

SNMP

72

Operating Manual

Simple Network Management Protocol

SPI

Synchronous Physical Interface

SSM

Synchronization Signal Message

TCA

Threshold Crossed Alarm

TIM

Trace Identifier Mismatch

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

Troubleshooting Manual (TSMN)

TLCT

Total Loss of Capacity Transmit

TP

Terminal Point

TU

Tributary Unit

UAS
UNEQ
VCG
VCXO
WAN
XFP

Abbreviations

UnAvailable Second
UNEQuipped
Virtual Concatenation Group
Voltage Control Crystal Oscillator
Wide Area Network
10 Gigabit Small Form Factor Pluggable

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

73

Troubleshooting Manual (TSMN)

Index
A

Alarm list 14
communication alarm 15
environmental alarm 17
equipment alarm 14
quality of service alarm 17
security alarm 18

SC and CF failure replacement 63


SC card replacement 60
CF failure 62
SC and CF failure 63
SC failure 61
SC failure replacement 61
Security alarm 18, 57
Switching
MIB 68

C
Card replacement 60
CC card 66
fan unit 67
filter unit 67
SC card 60
CC card replacement 66
CF failure replacement 62
Communication alarm 15, 26

T
Troubleshooting 19
communication alarm 26
environmental alarm 53
equipment alarm 19
quality of service alarm 53
security alarm 57

D
Data difference MIB swtiching 68
Document structure 11
Dry fiber cleaning 70

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

Anda mungkin juga menyukai