FlexiPacket Hub 800

R2.5
Troubleshoot

Issue: 1

Issue date: May 2013

A25000-A0800-E020-01-76P1

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of
its products and services. We would like to encourage you as our customers and users to join
us in working towards a cleaner, safer environment. Please recycle product packaging and
follow the recommendations for power use and proper disposal of our products and their
components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Siemens Networks for any additional information.

Troubleshoot

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 2013. All rights reserved.

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Table of Contents
This document has 45 pages.
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 11
RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CE compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MEF compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2
2.1
2.2

About troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Troubleshooting tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.5.1
3.1.5.2
3.1.5.3
3.1.5.4
3.1.6
3.1.6.1
3.1.6.2
3.1.7
3.1.8
3.1.9
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
3.2.10
3.2.11
3.2.12
3.2.13

Alarm-triggered troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P+E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STM-1/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Regenerator section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiplex section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High order path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Low order path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HOVC (AU-4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOVC (TU-12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexBus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross First Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross Second Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Function Card Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Function Card Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Function Card Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduled Action Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SNTP Server Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP_Absent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP Temperature Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP Bias Current Abnormal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP Tx Power Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

14
15
15
16
16
16
17
17
17
17
17
18
18
18
18
19
19
19
19
20
20
20
20
21
21
21
21
22
22
22
22

Troubleshoot

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.3
3.3.1
3.4
3.4.1
3.4.2
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.6
3.6.1
3.6.1.1
3.6.1.2
3.6.1.3
3.6.2
3.6.2.1
3.6.2.2
3.6.2.3
3.6.2.4
3.6.3
3.6.3.1
3.6.3.2
3.6.3.3
3.6.3.4
3.6.3.5
3.6.3.6
3.6.3.7
3.6.3.8
3.6.4
3.6.4.1

SFP Rx Power Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Service Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Power Supply to ODU Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
NE OverHeating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IDU Not in Shroud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Communication Failure with Peer IDU . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Peer IDU Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Not in Dual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Load Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
License Not Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
UNI Port Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Wrong Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Manual Operation On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Station Alarm 1/2 (default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
P+E alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Short Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PW alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
PW Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Remote Packet Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Sync alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Clock Source Deteriorate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Timing Quality Level Degraded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Timing SSM Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Timing Configuration Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Timing Interface Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Timing Unlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
STM-1/4 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Regenerator section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
RS-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Multiplex section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MS-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MS-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MS-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MS-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
High order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
AU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
AU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
HP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
HP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
HP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
HP-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Low order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
TU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

3.6.4.2
3.6.4.3
3.6.4.4
3.6.4.5
3.6.4.6
3.6.4.7
3.6.4.8
3.6.4.9
3.7
3.7.1
3.7.1.1
3.7.1.2
3.7.1.3
3.7.1.4
3.7.1.5
3.7.2
3.7.2.1
3.7.2.2
3.8
3.8.1
3.8.2
3.8.3
3.8.4
3.8.5
3.8.6
3.9
3.9.1
3.9.2
3.10
3.10.1
3.10.2
3.10.3
3.10.4
3.10.5

TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TU-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EOS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HOVC (AU-4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GFP-UPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GFP-LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GFP-LFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-VCAT-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-VCAT-LOA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOVC (TU-12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-VCAT-LOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LP-VCAT-LOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E1 alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AIS (Far) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AIS (Near) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Looped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexBus alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FB Port # Loss Of Frame (LOF). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FB Port # Loss Of Signal (LOS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Autonegotiation Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OAM CCM LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mep Radio Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1731 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFP LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4
4.1
4.2

Non-alarm-triggered troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
LEDs in FPH800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Cleaning dirty fiber optic ports and connectors . . . . . . . . . . . . . . . . . . . 45

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

35
35
36
36
36
36
37
37
38
38
38
38
38
38
39
39
39
39
40
40
40
40
41
41
41
42
42
42
42
42
42
43
43
43

Troubleshoot

List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6

WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CE marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MEF certified compliant logo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
FPH800 WebLCT window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
FPH800 alarm display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Alarm detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9
Table 10
Table 11
Table 12
Table 13
Table 14
Table 15
Table 16
Table 17

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
NE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
P+E alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
PW alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Sync alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Regenerator section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Multiplex section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
High order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Low order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HOVC (AU-4) alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
LOVC (TU-2) alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
E1 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
E1 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Ethernet alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
LEDs indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Troubleshoot

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Preface

1 Preface
This document provides the information to troubleshoot the FlexiPacket Hub 800
(FPH800) and to restore the normal operating conditions.

1.1

Intended audience
This document is intended for the operators in charge of troubleshooting the FPH800.

1.2

Structure of this document

The document is divided into the following main chapters:
Chapter

Subject

Chapter 1

Preface

Provides an introduction to the document.

Chapter 2

About troubleshooting

Provides information about how to

locate procedures related to alarms and
other trouble indications.

Chapter 3

Alarm-triggered troubleshooting

Provides an overview of alarm types,

alarm printouts and alarm handling procedures.

Chapter 4

Non-alarm triggered troubleshooting

Provides procedures to troubleshoot

non-alarm-triggered fault causes that
are involved with FPH800.

Table 1

1.3

Title

Structure of this document

Symbols and conventions

The following symbols and mark-up conventions are used in this document:
Representation

f DANGER!
f WARNING!
f CAUTION!

Meaning
A safety message indicates a dangerous situation where
personal injury is possible.
The keywords denote hazard levels with the following meaning:
DANGER! - Indicates a hazardous situation which, if not
avoided, will result in death or serious (irreversible) personal
injury.
WARNING! - Indicates a hazardous situation which, if not
avoided, could result in death or serious (irreversible) personal
injury.
CAUTION! - Indicates a hazardous situation which, if not
avoided, may result in minor or moderate (reversible) personal
injury.

Table 2

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

List of symbols and conventions

Preface

Troubleshoot

Representation

Meaning

w NOTICE:

A property damage message indicates a hazard that may result

in equipment damage, data loss, traffic interruption, and so on.

A note provides important information related to the topic, for

example, not obvious exceptions to a rule or side effects.

A tip provides additional information related to the topic which is

not essential in the context, but given for convenience.

Bold

Italic

typewriter

<angle brackets>

All names of graphical user interface (GUI) objects, such as

windows, field names, buttons, and so on.
Example: Select the Full Screen check box and press OK.
Terms and abbreviations which are linked to an entry in the
glossary and list of abbreviations respectively
Important key words
Files, folders, and file system paths.
Example: /usr/etc/sbin/ftpd.exe
Emphasized words
Input to be typed in a command line or a GUI field.
Examples:
ping -t 192.168.0.1
Enter World in the Domain field.
Output from a command, error messages, content of a status
line, and so on
File content, such as program sources, scripts, logs, and
settings

Placeholders, for example as part of a file name or field value.

Examples:
<picture name>.png or <ip address>:<port number>

[square brackets]

A key to be pressed on a PC keyboard, for example [F11].

Keys to be pressed simultaneously are concatenated with a +
sign, for example [CTRL]+[ALT]+[DEL].
Keys to be pressed one after another are concatenated with
spaces, for example [ESC] [SPACE] [M].

>

The greater than symbol > is used to concatenate a series of

GUI items in order to depict a GUI path. This is an abridged presentation of a procedure to be carried out in order to perform an
action or display a window or dialog box.
Examples:
A simple menu path: File > Save as ...
A more complex GUI path:
SURPASS TransNet window > Tools menu >
3R-Matrix Report command > 3R-Matrix Report dialog box

Table 2

10

List of symbols and conventions (Cont.)

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Preface

Representation
x
(in card names)

Meaning
For convenience, card names are sometimes listed with a lower
case x variable, in order to concisely represent multiple cards.
Example:
I01T40G-x (is to be interpreted as I01T40G-1 and I01T40G-2)

Table 2

List of symbols and conventions (Cont.)

Screenshots of the graphical user interface are examples only to illustrate principles.
This especially applies to a software version number visible in a screenshot.

1.4

History of changes
Issue
1
Table 3

1.5

Issue date
May 2013

Remarks
1st version

History of changes

Waste electrical and electronic equipment (WEEE)

All waste electrical and electronic products must be disposed of separately from the
municipal waste stream via designated collection facilities appointed by the government
or the local authorities. The WEEE label (see Figure 1) is applied to all such devices.

Figure 1

WEEE label

The correct disposal and separate collection of waste equipment will help prevent potential negative consequences for the environment and human health. It is a precondition
for reuse and recycling of used electrical and electronic equipment.
For more detailed information about disposal of such equipment, please contact Nokia
Siemens Networks.
The above statements are fully valid only for equipment installed in the countries of the
European Union and is covered by the directive 2002/96/EC. Countries outside the
European Union may have other regulations regarding the disposal of electrical and
electronic equipment.

1.6

RoHS compliance
FPH800 complies with the European Union RoHS Directive 2002/95/EC on the restriction of use of certain hazardous substances in electrical and electronic equipment.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

11

Preface

Troubleshoot

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, polybrominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electrical
and electronic equipment put on the market after 1 July 2006.
Materials usage information on Nokia Siemens Networks Electronic Information
Products imported or sold in the Peoples Republic of China
FPH800 complies with the Chinese standard SJ/T 11364-2006 on the restriction of the
use of certain hazardous substances in electrical and electronic equipment. The
standard applies to the use of lead, mercury, cadmium, hexavalent chromium, polybrominated biphenyls (PBB), and polybrominated divinely ethers (PBDE) in electrical and
electronic equipment put on the market after 1 March 2007.

1.7

CE compliance
FlexiPacket Hub 800 is in compliance with the essential requirements and other relevant
provisions of Directive: 2006/95/EC, 2004/108/EC, and 1999/5/EC.

The product is marked with the CE marking

Figure 2

1.8

CE marking

MEF compliance
FlexiPacket Hub 800 operating at the NNI delivers EPL, EVPL and E-LAN service
complies with the Metro Ethernet Forum MEF14 technical specification. FlexiPacket
Hub 800 operating at the UNI delivers EPL, EVPL and E-LAN service complies with the
Metro Ethernet Forum MEF9 technical specification.

Figure 3

12

MEF certified compliant logo

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

About troubleshooting

2 About troubleshooting
This section provides an overview of the general troubleshooting process and specific
troubleshooting tools for the FPH800.

2.1

Overview
If a single alarm has been generated, go to Section 3 Alarm-triggered troubleshooting.
For each alarm, a description and the steps you need to take to resolve the alarm are
provided.
To troubleshoot a case where there is no alarm, go to Section 4 Non-alarm-triggered
troubleshooting and locate the fault description that matches your case. Instructions for
further investigating the problem and the steps needed to resolve the problem are provided.

2.2

Troubleshooting tool
Loopback is used to test the network connection and diagnose the network problem. For
FPH800, all the physical interfaces, i.e, E1, SFP, GE ports, as well as the pseudowire
circuits can be tested by loopback.
For detailed information about loopback, please refer to Operate and Maintain Manual.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

13

Alarm-triggered troubleshooting

Troubleshoot

3 Alarm-triggered troubleshooting
The troubleshooting is performed by using WebLCT with the information given in the
alarm window, as shown in the following Figures.
1

Start WebLCT and establish a local connection. A list of alarms is showing at the
bottom of the window (see Figure 4).

Figure 4

Show or hide the alarms by clicking the different color of bell symbols (see Figure 5).

Figure 5

14

FPH800 WebLCT window

FPH800 alarm display

The detailed information of each alarm item is shown by clicking the certain alarm
item (see Figure 6).

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Figure 6

3.1
3.1.1

Alarm detailed information

Alarm list
NE
Alarm name

Action

Cross First Threshold

Section 3.2.1 Cross First Threshold

Cross Second Threshold

Section 3.2.2 Cross Second Threshold

Function Card Failed

Section 3.2.3 Function Card Failed

Function Card Absent

Section 3.2.4 Function Card Absent

Function Card Mismatch

Section 3.2.5 Function Card Mismatch

Fan Fail

Section 3.2.6 Fan Fail

Scheduled Action Failure

Section 3.2.7 Scheduled Action Failure

SNTP Server Unavailable

Section 3.2.8 SNTP Server Unavailable

SFP_Absent

Section 3.2.9 SFP_Absent

SFP_Mismatch

Section 3.2.10 SFP_Mismatch

SFP Temperature Abnormal

Section 3.2.11 SFP Temperature Abnormal

SFP Bias Current Abnormal

Section 3.2.12 SFP Bias Current Abnormal

SFP Tx Power Abnormal

Section 3.2.13 SFP Tx Power Abnormal

SFP Rx Power Abnormal

Section 3.2.14 SFP Rx Power Abnormal

Service Down

Section 3.2.15 Service Down

Power Supply to ODU Failed

Section 3.2.16 Power Supply to ODU Failed

NE OverHeating

Section 3.2.17 NE OverHeating

IDU Not in Shroud

Section 3.2.18 IDU Not in Shroud

Communication Failure with Peer IDU Section 3.2.19 Communication Failure with
Peer IDU
Peer IDU Fail

Section 3.2.20 Peer IDU Fail

Not in Dual Mode

Section 3.2.21 Not in Dual Mode

Load Mismatch

Section 3.2.22 Load Mismatch

License Not Match

Section 3.2.23 License Not Match

Table 4

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

NE alarms

15

Alarm-triggered troubleshooting

Troubleshoot

Alarm name
UNI Port Shutdown

Section 3.2.24 UNI Port Shutdown

Wrong Load

Section 3.2.25 Wrong Load

Manual Operation On

Section 3.2.26 Manual Operation On

Station Alarm 1/2 (default)

Section 3.2.27 Station Alarm 1/2 (default)

Table 4

3.1.2

NE alarms (Cont.)

P+E
Alarm name
Short Circuit
Table 5

3.1.3

P+E alarm

PW
Action

PW Down

Section 3.4.1 PW Down

Remote Packet Loss

Section 3.4.2 Remote Packet Loss

Table 6

PW alarms

Synchronization
Alarm name

Action

Clock Source Deteriorate

Section 3.5.1 Clock Source Deteriorate

Timing Quality Level Degraded

Section 3.5.2 Timing Quality Level

Degraded

Timing SSM Missing

Section 3.5.3 Timing SSM Missing

Timing Configuration Error

Section 3.5.4 Timing Configuration Error

Timing Interface Down

Section 3.5.5 Timing Interface Down

Timing Unlock

Section 3.5.6 Timing Unlock

Table 7

16

Action
Section 3.3.1 Short Circuit

Alarm name

3.1.4

Action

Sync alarms

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

3.1.5
3.1.5.1

STM-1/4
Regenerator section
Alarm name
LOF

Section 3.6.1.1 LOF

LOS

Section 3.6.1.2 LOS

RS-TIM

Section 3.6.1.3 RS-TIM

Table 8

3.1.5.2

Regenerator section alarms

Multiplex section
Alarm name

Section 3.6.2.1 MS-RDI

MS-AIS

Section 3.6.2.2 MS-AIS

MS-EXC

Section 3.6.2.3 MS-EXC

MS-DEG

Section 3.6.2.4 MS-DEG

Multiplex section alarms

High order path

Alarm name

Action

AU-LOP

Section 3.6.3.1 AU-LOP

AU-AIS

Section 3.6.3.2 AU-AIS

HP-RDI

Section 3.6.3.3 HP-RDI

HP-UNEQ

Section 3.6.3.4 HP-UNEQ

HP-PLM

Section 3.6.3.5 HP-PLM

HP-DEG

Section 3.6.3.6 HP-DEG

HP-EXC

Section 3.6.3.7 HP-EXC

HP-TIM

Section 3.6.3.8 HP-TIM

Table 10

3.1.5.4

Action

MS-RDI

Table 9

3.1.5.3

Action

High order path alarms

Low order path

Alarm name
TU-LOP
Table 11

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Action
Section 3.6.4.1 TU-LOP

Low order path alarms

17

Alarm-triggered troubleshooting

Troubleshoot

Alarm name
TU-AIS

Section 3.6.4.2 TU-AIS

TU-LOM

Section 3.6.4.3 TU-LOM

LP-TIM

Section 3.6.4.4 LP-TIM

LP-UNEQ

Section 3.6.4.5 LP-UNEQ

LP-RDI

Section 3.6.4.6 LP-RDI

LP-PLM

Section 3.6.4.7 LP-PLM

LP-DEG

Section 3.6.4.8 LP-DEG

LP-EXC

Section 3.6.4.9 LP-EXC

Table 11

3.1.6
3.1.6.1

Low order path alarms (Cont.)

EOS
HOVC (AU-4)
Alarm name

Section 3.7.1.1 GFP-UPM

GFP-LCS

Section 3.7.1.2 GFP-LCS

GFP-LFS

Section 3.7.1.3 GFP-LFS

HC-VCAT-LOM

Section 3.7.1.4 HP-VCAT-LOM

HP-VCAT-LOA

Section 3.7.1.5 HP-VCAT-LOA

HOVC (AU-4) alarms

LOVC (TU-12)
Alarm name

Section 3.7.2.1 LP-VCAT-LOM

LP-VCAT-LOA

Section 3.7.2.2 LP-VCAT-LOA

LOVC (TU-2) alarms

E1
Alarm name

Action

AIS (Far)

Section 3.8.1 AIS (Far)

AIS (Near)

Section 3.8.2 AIS (Near)

Table 14

18

Action

LP-VCAT-LOM

Table 13

3.1.7

Action

GFP-UPM

Table 12

3.1.6.2

Action

E1 alarms

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Alarm name
RDI

Section 3.8.3 RDI

Loss Of Frame (LOF)

Section 3.8.4 LOF

Loss Of Signal (LOS)

Section 3.8.5 LOS

Looped

Section 3.8.6 Looped

Table 14

3.1.8

Action

E1 alarms (Cont.)

FlexBus
Alarm name
FB Port # Loss Of Frame (LOF)

Section 3.9.1 FB Port # Loss Of Frame

(LOF)

FB Port # Loss Of Signal (LOS)

Section 3.9.2 FB Port # Loss Of Signal

(LOS)

Table 15

3.1.9

Action

E1 alarms

Ethernet
Alarm name
Autonegotiation Mismatch

Section 3.10.1 Autonegotiation Mismatch

OAM CCM LOSS

Section 3.10.2 OAM CCM LOSS

Mep Radio Link Down

Section 3.10.3 Mep Radio Link Down

1731 AIS

Section 3.10.4 1731 AIS

SFP LOS

Section 3.10.5 SFP LOS

Table 16

3.2
3.2.1

Action

Ethernet alarms

NE alarms
Cross First Threshold
Severity
Warning
Description
Notification of first threshold crossing alert.
Most Probable Cause
Account Log is filled to the first threshold. Accessing NE by WebLCT or NetViewer may
cause the account log full.
Actions
Clear the account log or disable the account log feature.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

19

Alarm-triggered troubleshooting

3.2.2

Troubleshoot

Cross Second Threshold

Severity
Major
Description
Notification of second threshold crossing alert.
Most Probable Cause
Account Log is filled to the second threshold. Accessing NE by WebLCT or NetViewer
may cause the account log full.
Actions
Clear the account log or disable the account log feature.

3.2.3

Function Card Failed

Severity
Critical
Description
Function card in Slot#n failed.
Most Probable Cause
Failure during initialization or system periodic self check mainly caused by hardware.
Failure causes include: FPGA download failure, Register Access Failure, Hardware
Selfcheck Failure.
Actions
Repair or replace the function card.

3.2.4

Function Card Absent

Severity
Critical
Description
Function card in Slot#n is absent.
Most Probable Cause
Function card is absent.
Actions
Check whether the function card is present.

3.2.5

Function Card Mismatch

Severity
Critical
Description
Function card in Slot#n is mismatched.
Most Probable Cause

20

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Inserted function card type is not consistent with the preconfigured type.
Actions
Replace the mismatched function card with a suitable function card. Or re-assign
fucntion card as actual card displayed in slot status of NE management.

3.2.6

Fan Fail
Severity
Major
Description
Fan failure.
Most Probable Cause
One of the fans in Fan card fault.
Actions
Replace the fan.

3.2.7

Scheduled Action Failure

Severity
Major
Description
The failure of a scheduled action to change Operational Status and SchedLastOpResult.
Most Probable Cause
The scheduler did not invoke actions at appropriate time. Or the standby load is
damaged.
Actions
Check the standby load to see if it is a valid load.

3.2.8

SNTP Server Unavailable

Severity
Minor
Description
Time server unavailable.
Most Probable Cause
The link to the time server is not working. Or the time server hangs up.
Actions
Check the time server, it will be cleared when time server answers.

3.2.9

SFP_Absent
Severity
Critical

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

21

Alarm-triggered troubleshooting

Troubleshoot

Description
SFP#n is absent
Most Probable Cause
SFP module is absent or is not working.
Actions
Check whether the SFP module is present. Or replace the unworkable module.

3.2.10

SFP_Mismatch
Severity
Critical
Description
SFP#n is mismatch
Most Probable Cause
Inserted SFP module type is not consistent with the preconfigured type.
Actions
Replace the mismatched SFP module with a suitable SFP module.

3.2.11

SFP Temperature Abnormal

Severity
Major
Description
SFP temperature is abnormal.
Most Probable Cause
SFP works not correct.
Actions
Check SFPs configuration and its status.

3.2.12

SFP Bias Current Abnormal

Severity
Major
Description
The SFP bias current is abnormal.
Most Probable Cause
The SFP is broken.
Actions
Check the SFP status.

3.2.13

SFP Tx Power Abnormal

Severity

22

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Major
Description
The transmited Power is abnormal.
Most Probable Cause
The SFP is broken.
Actions
Check the SFP status.

3.2.14

SFP Rx Power Abnormal

Severity
Major
Description
The received Power is abnormal.
Most Probable Cause
The peer SFP is broken or the attenuation is too large.
Actions
Check the peer SFP status.

3.2.15

Service Down
Severity
Major
Description
The service operational status is down.
Most Probable Cause
The ports of the service may link down or the service abnormal.
Actions
Check the link state for the service, or delete and recreate the service.

3.2.16

Power Supply to ODU Failed

Severity
Major
Description
The status of power supply to ODU.
Most Probable Cause
Short / open circuit in ODU cable; wrong cable manufacturing; ODU failure.
Actions
Check the ODU cable and ODU.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

23

Alarm-triggered troubleshooting

3.2.17

Troubleshoot

NE OverHeating
Severity
Major
Description
The board temperature is higher than the threshold
Most Probable Cause
Temperature of equipment is not in normal working range.
Actions
Check whether fan is working correctly.
Check whether the temperature of equipment is really out of working allowed range.
Check if temperature threshold is configured properly.

3.2.18

IDU Not in Shroud

Severity
Major
Description
The IDU is not in shroud (only reported in idle mode).
Most Probable Cause
The shroud is not connected with Dual IDU.
Actions
Check the connection between shroud and Dual IDU.

3.2.19

Communication Failure with Peer IDU

Severity
Major
Description
The peer IDU is not responding.
Most Probable Cause
Peer IDU is not existing; not powered up; in Initial status; in standby status; or in Idle
status.
Actions
Check the Peer IDU.

3.2.20

Peer IDU Fail

Severity
Major
Description
The peer IDU is fail.
Most Probable Cause

24

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

3 continuous I-CCM message missing, will notice Dual IDU State Machine that peer IDU
is fail; or FPGA heartbeat loss.
Actions
Check peer IDU status.

3.2.21

Not in Dual Mode

Severity
Major
Description
The IDU is not working in Dual-IDU mode.
Most Probable Cause
The IDU is working in single IDU mode, but IDU is in shroud.
Actions
If IDU is planned to work in single mode, plug out the IDU from shroud. If IDU is planned
to work in dual-IDU mode, update dual-IDU license on both IDUs, then set working mode
to dual-IDU mode.

3.2.22

Load Mismatch
Severity
Major
Description
SW load mismatch.
Most Probable Cause
Dual IDU with different SW loaded at IDUs.
Actions
Check the SW loads on Dual IDU, make them consistent.

3.2.23

License Not Match

Severity
Major
Description
The license between two IDUs are not match.
Most Probable Cause
Dual IDU with different license.
Actions
Check the licenses on IDUs, make them consistent.

3.2.24

UNI Port Shutdown

Severity
Critical

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

25

Alarm-triggered troubleshooting

Troubleshoot

Description
UNI port is shutdown because there is error in related NNI port.
Most Probable Cause
There is error in related NNI port.
Actions
Check the link status and their OAM status on related NNI port.

3.2.25

Wrong Load
Severity
Minor
Description
SW switch is not allowed.
Most Probable Cause
Any component Standby FW version is not compatible with the HW version, the switch
command can not be executed.
Actions
A new SW need to download.

3.2.26

Manual Operation On
Severity
Test
Description
This alarm applies to E1/T1, STM-1/4 and Ethernet interface. This alarm is used in
degugging in manual operation in NE, i.e., loopback.
Most Probable Cause
Loop back is implemented at E1/T1 port, STM-1 port or GE port.
Actions
Wait for timeout or stop loopback manually.

3.2.27

Station Alarm 1/2 (default)

Severity
Intermediate (default)
Description
The station alarm is configurable alarm for dry contact. Both alarm name and severity is
configurable by the user. Dry contact is a RJ45 port on mainboard and generally connect
to sensor or other equipment, i.e., station over-heat, humidity, open-door indications.
Most Probable Cause
Configuration is wrong in NE or input polarity is same as configured one.
Actions
Check the configuration or solve the problem from external equipment.

26

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

3.3

P+E alarm

3.3.1

Short Circuit
Severity
Major
Description
Overcurrent / undercurrent condition has been detected at the ODU Ethernet Interface.Each ODU-enabled GE interface has its own Overcurrent/Undercurrent alarm.
Most Probable Cause
Short / open circuit in ODU cable; wrong cable manufacturing; ODU failure.
Actions
Check ODU cable and ODU.

3.4
3.4.1

PW alarms
PW Down
Severity
Major
Description
PW#Operation status: lower layer down or mismatch in two ends
Most Probable Cause
Ethernet service carrying this CESoP service is down.
MAC address is not learnt.
UDP port mismatch.
C-VLAN mismatch.
Packet loss.
Actions
Check Ethernet connection, CESoP configuration and/or network connection.

3.4.2

Remote Packet Loss

Severity
Minor
Description
PW#Remote packet loss indication
Most Probable Cause
PW Down alarm reports in peer NE and it sets R bit to local NE, Remote Packet Loss
alarm reports in local NE.
Actions
Check the CESoP servcie according to action of PW Down in peer NE.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

27

Alarm-triggered troubleshooting

3.5
3.5.1

Troubleshoot

Sync alarms
Clock Source Deteriorate
Severity
Major
Description
The source of transmit clock is deteriorate.
Most Probable Cause
The clock source is not good enough, maybe big jitter, big wander, or unlocked to its
source.
Actions
Check the link status of this clock source, and synchronization status of this sources
source.

3.5.2

Timing Quality Level Degraded

Severity
Major
Description
Sync#Timing quality level degraded
Most Probable Cause
The quality level received from upstream synchronization network is lower than setting
of SSM system clock threshold.
Actions
Check received quality level from upstream synchronization network.

3.5.3

Timing SSM Missing

Severity
Major
Description
Sync#Timing SSM missing
Most Probable Cause
SSM message cannot be received at this timing source.
Actions
Check whether the switch of SSM is opened in local and upstream NE. Check the connection between two NEs.

3.5.4

Timing Configuration Error

Severity
Major
Description

28

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

The equipment is receiving SSM carrying a DNU code from at least one synchronization
interface.
Most Probable Cause
The master slave state of PHY is master when the GE port is configured as a timing
source.
Actions
Make sure the master slave state of PHY is slave when the GE port is configured as
timing source.

3.5.5

Timing Interface Down

Severity
Minor
Description
Sync#Timing interface down
Most Probable Cause
A LinkState = Down has been detected in an Ethernet interface selected as synchronization interface;
A LOS has been detected in the E1 interface selected as synchronization interface.
LOF and AIS also cause this alarm.
Actions
Check the interface.

3.5.6

Timing Unlock
Severity
Major
Description
Sync#Timing unlock
Most Probable Cause
All timing sources are failed.
Actions
Check the failure cause of all timing sources.

3.6
3.6.1
3.6.1.1

STM-1/4 alarms
Regenerator section alarms
LOF
Severity
Critical
Description

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

29

Alarm-triggered troubleshooting

Troubleshoot

STM1/4#n loss of frame.

Most Probable Cause
When an OOF state persists for a defined period of time.
Actions
Check the operation of transmitter in both near-end and far-end stations.

3.6.1.2

LOS
Severity
Critical
Description
STM1/4#n loss of signal.
Most Probable Cause
Fibre cut.
Optical power is too large.
Attenuation is too large.
Transmitter fault in peer NE.
Actions
Check fibre connection.
If optical power is too large, please add an attenuator.
Change SFP module.

3.6.1.3

RS-TIM
Severity
Critical
Description
STM1/4#n RS trace identifier mismatch
Most Probable Cause
Wrong routing somewhere in the network due to:
Wrong connected line cables.
Wrong expected trace identifier filled in via the management system.
Actions
Determine in which node(s) the line cables are wrongly connected by interpreting the
received STM-N RS trace identifiers.Check the correctness of expected RS trace identifier.

3.6.2
3.6.2.1

Multiplex section alarms

MS-RDI
Severity

30

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Minor
Description
STM1/4#n Remote Defect Indication is used to return an indication to the transmit end
that the received end has detected an incoming section defect or is receiving MS-AIS.
MS-RDI is generated by inserting a 110 code in positions 6, 7 and 8 of the K2 byte
before scrambling.
Most Probable Cause
In the upstream station (that reported the failure detects a malfunction at the receive
side), one of the following conditions is detected:
MS AIS (Multiplex Section Alarm Indication Signal), SPI-LOS (Loss Of Signal) or RSLOF (Loss Of Frame).
Or RS-TIM (Regenerator Section Trace Identifier Mismatch).
The far end station of the node: no signal received, alarm indication signal received, or
excessive error rate.
Actions
Check upstream external cabling and equipment.
Check local transmitting equipment.
Locally no actions can be taken.
In the far-end node, clear the indicated receive side fault(s).

3.6.2.2

MS-AIS
Severity
Minor
Description
STM1/4#n Multiplex Section alarm indication signal.
The Multiplex Section AIS (MS-AIS) is specified as all 1s in the entire STM-N, excluding the STM-N MSOH.
Most Probable Cause
Upstream NE has inserted AIS signal.
Actions
Clear upstream inserted AIS.

3.6.2.3

MS-EXC
Severity
Major
Description
STM1/4#n Multiplex Section Excessive error
Most Probable Cause
An excessive error defect (dEXC) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 3, 4, 5.
Actions

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

31

Alarm-triggered troubleshooting

Troubleshoot

Check the upstream external cabling and equipment.

Check the threshold in the management system.

3.6.2.4

MS-DEG
Severity
Minor
Description
STM1/4#n Multiplex Section Degrade Signal
Most Probable Cause
A degraded signal defect (dDEG) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 5, 6, 7, 8, 9.
Actions
Check upstream external cabling and equipment.
Check the threshold in the management system.

3.6.3
3.6.3.1

High order path alarms

AU-LOP
Severity
Critical
Description
STM1/4#n Administrative Unit Loss Of Pointer.
Most Probable Cause
Wrong configuration.
Received error is too large.
Fault in peer NE.
Actions
Check the configuration.
Change the SFP module.
Check synchronization state.
Check configuration in peer NE.

3.6.3.2

AU-AIS
Severity
Minor
Description
STM1/4#n Administrative Unit Alarm Indication Signal.AU-AIS is specified as all 1s in
the entire AU-4, including the AU-4 pointer. The VC-4 payload signal is replaced by the
alarm indication signal.
Most Probable Cause

32

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

In one of the upstream nodes a defect is detected and led to the insertion of the alarm
indication signal.
Wrong configurations.
LOS, LOF, MS-AIS in local NE.
Actions
Check and clear upstream NEs SPI, RS, MS or AU-LOP alarms.
Check configurations.
Release high order alarms in local NE.

3.6.3.3

HP-RDI
Severity
Minor
Description
STM1/4#n Higher Order Path Remote Defect Indication.
Most Probable Cause
A fault exists in received direction of peer NE, it sends HP-RDI to local NE.
Actions
Check the fault in peer NE.

3.6.3.4

HP-UNEQ
Severity
Critical
Description
STM1/4#n Higher Order Path Unequipped.
Most Probable Cause
VC-4 in STM-N signal is not in use.
Actions
Define or change the cross-connection at the other side to be consistent with local side.

3.6.3.5

HP-PLM
Severity
Critical
Description
STM1/4#n Higher Order Path Payload Mismatch.The received payload value, used to
indication the composition of VC-4 payload, does not match the provisioned value.This
alarm does not rely on port alarm monitored mode.
Most Probable Cause
Mapping mode of local and far-end nodes is not same.Expected payload value set via
management system in local node is not same as the actual payload value in far-end
node.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

33

Alarm-triggered troubleshooting

Troubleshoot

Actions
Change the mapping mode of local node to be the same as far-end node.
Change the expected payload value in local node to be the same as the actual payload
value in far-end node.

3.6.3.6

HP-DEG
Severity
Minor
Description
STM1/4#n Higher Order Path Degraded Signal
Most Probable Cause
A degraded signal defect (dDEG) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 5, 6, 7, 8, 9.
Actions
Check the upstream external cabling and equipment.
Check the threshold in the management system.

3.6.3.7

HP-EXC
Severity
Major
Description
STM1/4#n Higher Order Path Excessive error
Most Probable Cause
An excessive error defect (dEXC) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 4, 5.
Actions
Check the upstream external cabling and equipment.

3.6.3.8

HP-TIM
Severity
Critical
Description
STM1/4# J1 Trace Identifier Mismatch, the receive is not the same to expected.
Most Probable Cause
Wrong routing somewhere in the network due to:
Wrong connected line cables.
Wrong expected trace identifier filled in via the management system.
Actions

34

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Determine in which node(s) the line cables are wrongly connected by interpreting the
received STM-N J1 trace identifiers. Check the correctness of expected J1 trace identifier.

3.6.4
3.6.4.1

Low order path alarms

TU-LOP
Severity
Critical
Description
STM1/4#n LP#m tributary unit loss of pointer.
Most Probable Cause
No valid tributary unit pointer interpretation obtained in received signal.
Actions
Check the configurations.

3.6.4.2

TU-AIS
Severity
Minor
Description
STM1/4#n LP#m tributary unit alarm indication signal.
Most Probable Cause
Wrong configuration.
High order alarm exists.
Actions
Check the configurations.
Release high order alarms.

3.6.4.3

TU-LOM
Severity
Critical
Description
STM1/4#n LP#m tributary unit loss of multi-frame.
Most Probable Cause
Alignment to the multi frame structure of the received VC-4 signal is not possible. Therefore VC-12 overhead and payload data cannot be extracted.
Actions
Check upstream external cabling and equipment.
Check on the management system if unit failure is reported for the unit generating the
multi-frame alignment signal. In that node, remove the unit and replace it with a new one.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

35

Alarm-triggered troubleshooting

3.6.4.4

Troubleshoot

LP-TIM
Severity
Critical
Description
STM1/4#n LP#m lower order trace identifier mismatch. This alarm relies on the monitoring switch: LP E1 enable.
Most Probable Cause
Mismatch between received trace id and expected trace id.
Actions
Check the cross-connections.
Check the tributary cables and tributary units.
Check the expected trace in the management system.

3.6.4.5

LP-UNEQ
Severity
Major
Description
STM1/4#n LP#m lower order unequipped. This alarm relies on the monitoring switch: LP
E1 enable.
Most Probable Cause
Lower order path in STM-N signal is not in use.
Actions
Define or change the cross-connection at the other side consistently with the local side.

3.6.4.6

LP-RDI
Severity
Minor
Description
STM1/4#n LP#m lower order remote defect indication. This alarm relies on the monitoring switch: LP E1 enable.
Most Probable Cause
A lower order fault exists in received direction of peer NE. It sends LP-RDI to local NE.
Actions
React the far-end alarms. Follow the clearing action for those alarm(s).

3.6.4.7

LP-PLM
Severity
Major
Description

36

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

STM1/4#n LP#m lower order path payload mismatch. The received payload value, used
to indication the composition of lower order path payload, does not match the provisioned value.
Most Probable Cause
Mapping mode of local and far-end nodes is not same. Expected payload value set via
management system in local node is not same as the actual payload value in far-end
node.
Actions
Change the mapping mode of local node same as far-end node.
Change the expected payload value in local node to be the same as the actual payload
value in far-end node.

3.6.4.8

LP-DEG
Severity
Minor
Description
STM1/4#n LP#m lower order path degraded. This alarm relies on the monitoring switch:
LP E1 enable.
Most Probable Cause
A degraded signal defect (dDEG) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 5, 6, 7, 8, 9.
Actions
Check the upstream external cabling and equipment.
Check the threshold in the management system.

3.6.4.9

LP-EXC
Severity
Major
Description
STM1/4#n LP#m lower order path excessive error. This alarm relies on the monitoring
switch: LP E1 enable.
Most Probable Cause
An excessive error defect (dEXC) shall be detected if the equivalent BER exceeds a
preset threshold of 10-x, x = 3, 4, 5.
Actions
Check the upstream external cabling and equipment.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

37

Alarm-triggered troubleshooting

3.7

EOS alarms

3.7.1

HOVC (AU-4)

3.7.1.1

Troubleshoot

GFP-UPM
Severity
Critical
Description
STM1#n LP VCG#m GFP user payload mismatch
Most Probable Cause
The received PTI (payload type identifier) is not equal to 0000 0001 (frame-mapped
Ethernet).
Actions
Check configuration in both equipments.

3.7.1.2

GFP-LCS
Severity
Critical
Description
GFP customer signal failure
Most Probable Cause
Link operation status of internal EOS port is down.
Actions
The link operation status of internal EOS port is set to up.

3.7.1.3

GFP-LFS
Severity
Critical
Description
Loss of GFP frame synchronization
Most Probable Cause
Bit errors are detected in the Core Header by the cHEC.
Actions
Send a correct cHEC to match with the next candidate GFP frame.

3.7.1.4

HP-VCAT-LOM
Severity
Critical
Description

38

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

Higher order path virtual concatenation- loss of multiframe

Most Probable Cause
This alarm is detected when the multiframe alignment pattern error and virtual concatenation multiframe counters value error occur in three consecutive times.
Actions
Check if there is higher level alarms and release them if any.
Check the cross connection and the bandwidth configuration. Keep them in line with
each other.

3.7.1.5

HP-VCAT-LOA
Severity
Critical
Description
Higher order path virtual concatenation - loss of alignment
Most Probable Cause
This alarm is detected when the differential delay exceeds the size of the alignment
buffer.
Actions
Lessen the service paths or hops.

3.7.2
3.7.2.1

LOVC (TU-12)
LP-VCAT-LOM
Severity
Critical
Description
Lower order path virtual concatenation - loss of multiframe
Most Probable Cause
This alarm is detected when the multiframe alignment pattern error and virtual concatenation multiframe counters value error occur in three consecutive times.
Actions
Check the configuration in both equipment or the synchronization state.

3.7.2.2

LP-VCAT-LOA
Severity
Critical
Description
Lower order path virtual concatenation - loss of alignment
Most Probable Cause

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

39

Alarm-triggered troubleshooting

Troubleshoot

This alarm is detected when the differential delay exceeds the size of the alignment
buffer.
Actions
Check the delay of VC member between two equipment and make sure the delay is less
than alignment buffer.

3.8
3.8.1

E1 alarms
AIS (Far)
Severity
Warning
Description
E1/T1#n receive all 1 signal.
Most Probable Cause
Wrong configuration in local NE or in the far end NE.
Fault in far end NE.
Actions
Check the configurations in local NE or in the far end NE.
Solve the fault in far end NE.

3.8.2

AIS (Near)
Severity
Warning
Description
E1/T1#n transmit all 1 signal.
Most Probable Cause
Wrong configuration in local NE.
Actions
Check the configurations in local NE.

3.8.3

RDI
Severity
Minor
Description
E1/T1#n receive far end alarm failure.
Most Probable Cause
The fault exists in peer NE, and it sends RDI to local NE.
Actions
Check alarms in peer NE, e.g., LOS, LOF and AIS.

40

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

3.8.4

LOF
Severity
Critical
Description
E1/T1#n receive far end loss of frame.
Most Probable Cause
Frame type between two E1/T1 interfaces is mismatching.
Or consecutive 3 OOF is detected.
Actions
Check the configurations between connected E1/T1 interfaces.
Or check the synchronization state.

3.8.5

LOS
Severity
Critical
Description
E1/T1#n near end Loss of Signal.
The LOS state is considered to have occurred when the amplitude of the relevant signal
has dropped below prescribed limits for a prescribed period.
Most Probable Cause
Cable rupture.
Equipment fault(s) in the upstream far end station of the node that reported the alarm.
Actions
Check the connections of the physical layer.
Check for cable breaks or dirty connectors (measure it with power meter and clear it).

3.8.6

Looped
Severity
Test
Description
The incoming E1 or T1 signal is looped to egress port and copied to the remote site.
Most Probable Cause
E1 or T1 interface is looped from local manually.
Actions
Wait for timeout or stop loopback manually.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

41

Alarm-triggered troubleshooting

3.9
3.9.1

Troubleshoot

FlexBus alarms
FB Port # Loss Of Frame (LOF)
Severity
Major
Description
FB port receives far end loss of frame.
Most Probable Cause
FB card cannot de-linear the FB frames for a certain time.
Actions
Check cable connection or cable length.

3.9.2

FB Port # Loss Of Signal (LOS)

Severity
Critical
Description
FB port near end loss of signal.
Most Probable Cause
Cable rupture.
Actions
Check the connections of the physical layer.

3.10
3.10.1

Ethernet alarms
Autonegotiation Mismatch
Severity
Critical
Description
Eth#n auto negotiating mismatch.
Most Probable Cause
Two ethernet port failed to negotiate the master and slave status.
Actions
Check the duplex / speed configuration of the two ports.

3.10.2

OAM CCM LOSS

Severity
Major
Description

42

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Alarm-triggered troubleshooting

IDU does not receive MCC loss threshold consecutive CCMs in the relevant MEP; an
alarm is raised and RDI is sent back.
Most Probable Cause
Connection problem, CPU did not process the CCM message in time.
Actions
Check the connection, or whether there is many messages to process.

3.10.3

Mep Radio Link Down

Severity
Minor
Description
Eth#n OAM MEP radio link down
Most Probable Cause
The radio link of the ODU is down.
Actions
Check the ODU configuration, role (active or standby).

3.10.4

1731 AIS
Severity
Minor
Description
Indicates MEP is in AIS condition.
Most Probable Cause
AIS condition occurs when it receives an AIS frame.
Actions
Check all link status between these two MEPs.

3.10.5

SFP LOS
Severity
Major
Description
Optical SFP # LOS.
Most Probable Cause
The ifOperStatus=down and the notification sent to the EMS is linkDown (linkUp).
Actions
Check the optical SFP ports.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

43

Non-alarm-triggered troubleshooting

Troubleshoot

4 Non-alarm-triggered troubleshooting
This section provides procedures to troubleshoot non-alarm-triggered fault causes
involving the FPH800.

4.1

LEDs in FPH800
FPH800 has four types of LEDs on the front panel to indicate the operational status of
the system during operation.
Type
Base

Name

Color

State

Function

PWR

Green

ON

Power on (either PWR A or

PWR B or PWR A & PWR B)

Mode

Blue/Green

ON

Blue indicates the Hybrid mode;

System

Green indicates the Packet

mode
Blink
1 GHZ
50%
ALM

Red/Yellow

ON

The test condition is active (e.g.

loopback, protection forcing)
Red indicates the alarm severity
is Critical/Major;
Yellow indicates the alarm
severity is Minor/Warning

ODU

Red

ON

ODU failure in at least one of the

connected ODUs, including both
on mainboard and plug-in cards

Ethernet
Link (left
electrical side)
interfaces Active (right
side)

Green

ON

Connection established

Green

Blink

Activity indication (on Rx or Tx)

SFP inter- Link

face
Active (left
side)

Green

ON

Connection established

Green

Blink

Activity indication (on Rx or Tx)

STM-1
interface

Active (right
side)

Green

ON

Activity indication (on Rx or Tx)

and no LOS

FlexBus
interface

LOS/LOF

Red

ON

Loss of signal or loss of frame

Connection

Green

ON

Connection established;
No alarm

Table 17

LEDs indication

The LEDs will display differently during the warm reboot and cold reboot period:

44

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

Troubleshoot

Non-alarm-triggered troubleshooting

During the cold reboot period, the Microprocessor will be rebooted, FPGA image will be
downloaded, all of the ASICs on the mainboard and plug-in cards will be reset, and all
of the LEDs except the power LEDs will be set off; then after the reboot is finished all of
the LEDs including the system LEDs and LEDs for each interface will flash together one
time which lasts for 1 second. Stop flashing is regarded as the finish point of reboot and
this can be used for LED test as well.
During the warm reboot period, the Microprocessor will be rebooted but the traffic will
not be interrupted, the system LEDs except the power LEDs will be set off; then after the
reboot is finished system LEDs except the power LEDs will flash together one time
which lasts for 1 second. Stop flashing is regarded as the finish point of reboot.

4.2

Cleaning dirty fiber optic ports and connectors

Fiber optic transceivers are sensitive optical devices and should always be handledcarefully. If dirt collects on a fiber optic lens, light may not be able to penetrate the lens.
This may cause a reduction in port performance.
To prevent dust from collecting on the fiber optic lens, always keep the dust covers on
the ports when the ports are not in use.

WARNING: The fiber optic lasers used in the device meet the regulatory requirements
for casual exposure to the eye.
As with any source of bright light, however, Nokia Siemens Networks recommends not
to look into the laser light source.

To clean the fiber optic lens:

1. Remove any accumulated dust or debris from the port or connector by blowing
across all surfaces with a canned air duster.
A compressed gas, such as Chemtronics Ultrajet or the Triangle Tool Groups
Liquid-Tool Dust-A-Way, is recommended. Do not use commercial compressed air
or house air because of the risk of oil contamination.
2. Reconnect the cable to the port to check whether dusting has corrected the problem.
3. Gently wipe the ports with a lint-free, nonabrasive, nonadhesive swab. Micro swabs
by Tex wipe are recommended.
4. Gently wipe the connectors with a lint-free, nonabrasive wipe or pad. Tex wipe pads
are recommended.
Avoid touching any connector surface after cleaning the connectors.

A25000-A0800-E020-01-76P1
Issue: 1 Issue date: May 2013

45