09 Troubleshoot

8/10/2019 09 Troubleshoot

1/45

FlexiPacket Hub 800R2.5

Troubleshoot

A25000-A0800-E020-01-76P1

Issue: 1 Issue date: May 2013

Nokia Siemens Networks is continually str iving to reduce the adverse environmental effects ofits products and services. We would like to encourage you as our customers and users to joinus in working towards a cleaner, safer environment. Please recycle product packaging andfollow the recommendations for power use and proper disposal of our products and theircomponents.

If you should have questions regarding our Environmental Policy or any of the environmentalservices we offer, please contact us at Nokia Siemens Networks for any additional information.


2/45

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

Troubleshoot

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmittedin any form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

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 liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However ,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens 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 NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOTLIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT ORTHE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

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

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

Copyright Nokia Siemens Networks 2013. All rights reserved.

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sourcesof danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handlethis product and only after having carefully read the safety information applicable to thisproduct.

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:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oderandere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durchgeschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-satzes.


3/45

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

3

Troubleshoot

Table of ContentsThis document has 45 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Structure of this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 History of changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . 111.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7 CE compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.8 MEF compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 About troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Troubleshooting tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Alarm-triggered troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1 Alarm list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.1 NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.2 P+E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.3 PW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.4 Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.5 STM-1/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.5.1 Regenerator section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1.5.2 Multiplex section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.5.3 High order path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.5.4 Low order path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.6 EOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.6.1 HOVC (AU-4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.6.2 LOVC (TU-12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.7 E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.8 FlexBus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1.9 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2 NE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.1 Cross First Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2.2 Cross Second Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.3 Function Card Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.4 Function Card Absent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.5 Function Card Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.6 Fan Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.7 Scheduled Action Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.8 SNTP Server Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.9 SFP_Absent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.10 SFP_Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.11 SFP Temperature Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.12 SFP Bias Current Abnormal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2.13 SFP Tx Power Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22


4/45


Troubleshoot

3.2.14 SFP Rx Power Abnormal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2.15 Service Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2.16 Power Supply to ODU Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2.17 NE OverHeating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.18 IDU Not in Shroud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.19 Communication Failure with Peer IDU . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.20 Peer IDU Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2.21 Not in Dual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.22 Load Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.23 License Not Match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.24 UNI Port Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.25 Wrong Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2.26 Manual Operation On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.2.27 Station Alarm 1/2 (default) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.3 P+E alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.1 Short Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.4 PW alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.4.1 PW Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.4.2 Remote Packet Loss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.5 Sync alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.1 Clock Source Deteriorate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.2 Timing Quality Level Degraded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.3 Timing SSM Missing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.4 Timing Configuration Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5.5 Timing Interface Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.5.6 Timing Unlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6 STM-1/4 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6.1 Regenerator section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6.1.1 LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6.1.2 LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6.1.3 RS-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6.2 Multiplex section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6.2.1 MS-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6.2.2 MS-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.6.2.3 MS-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.6.2.4 MS-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.6.3 High order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.6.3.1 AU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.6.3.2 AU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.6.3.3 HP-RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.6.3.4 HP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.6.3.5 HP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.6.3.6 HP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6.3.7 HP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6.3.8 HP-TIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.6.4 Low order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.6.4.1 TU-LOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35


5/45


5

Troubleshoot

3.6.4.2 TU-AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.6.4.3 TU-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.6.4.4 LP-TIM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.6.4.5 LP-UNEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.4.6 LP-RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.4.7 LP-PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.6.4.8 LP-DEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.6.4.9 LP-EXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.7 EOS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7.1 HOVC (AU-4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7.1.1 GFP-UPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7.1.2 GFP-LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7.1.3 GFP-LFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.7.1.4 HP-VCAT-LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3.7.1.5 HP-VCAT-LOA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.7.2 LOVC (TU-12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.7.2.1 LP-VCAT-LOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.7.2.2 LP-VCAT-LOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.8 E1 alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.8.1 AIS (Far) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.8.2 AIS (Near) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.8.3 RDI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.8.4 LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.8.5 LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.8.6 Looped. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.9 FlexBus alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.9.1 FB Port # Loss Of Frame (LOF). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.9.2 FB Port # Loss Of Signal (LOS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.10 Ethernet alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.10.1 Autonegotiation Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.10.2 OAM CCM LOSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.10.3 Mep Radio Link Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.10.4 1731 AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.10.5 SFP LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

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


6/45


Troubleshoot

List of FiguresFigure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 2 CE marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 3 MEF certified compliant logo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 4 FPH800 WebLCT window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 5 FPH800 alarm display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 6 Alarm detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


7/45


7

Troubleshoot

List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 2 List of symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 4 NE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 5 P+E alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 6 PW alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 7 Sync alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 8 Regenerator section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 9 Multiplex section alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 10 High order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 11 Low order path alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 12 HOVC (AU-4) alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 13 LOVC (TU-2) alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 14 E1 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 15 E1 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 16 Ethernet alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 17 LEDs indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


8/45


Troubleshoot


9/45


9

Troubleshoot Preface

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

1.1 Intended audienceThis document is intended for the operators in charge of troubleshooting the FPH800.

1.2 Structure of this documentThe document is divided into the following main chapters:

1.3 Symbols and conventionsThe following symbols and mark-up conventions are used in this document:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the docu-ment.

Chapter 2 About troubleshooting Provides information about how tolocate procedures related to alarms andother trouble indications.

Chapter 3 Alarm-triggered troubleshoot-ing

Provides an overview of alarm types,alarm printouts and alarm handling pro-cedures.

Chapter 4 Non-alarm triggered trouble-shooting

Provides procedures to troubleshootnon-alarm-triggered fault causes thatare involved with FPH800.

Table 1 Structure of this document

Representation Meaning

f DANGER!f

WARNING!f CAUTION!

A safety message indicates a dangerous situation wherepersonal injury is possible.

The keywords denote hazard levels with the following meaning:DANGER! - Indicates a hazardous situation which, if notavoided, will result in death or serious (irreversible) personalinjury.

WARNING! - Indicates a hazardous situation which, if notavoided, could result in death or serious (irreversible) personalinjury.

CAUTION! - Indicates a hazardous situation which, if notavoided, may result in minor or moderate (reversible) personalinjury.

Table 2 List of symbols and conventions


10/45


TroubleshootPreface

w NOTICE: A property damage message indicates a hazard that may resultin equipment damage, data loss, traffic interruption, and so on.

g A note provides important information related to the topic, forexample, not obvious exceptions to a rule or side effects.

t A tip provides additional information related to the topic which isnot essential in the context, but given for convenience.

Bold All names of graphical user interface (GUI) objects, such aswindows, 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 theglossary and list of abbreviations respectively

Important key words

Italic Files, folders, and file system paths.Example: /usr/etc/sbin/ftpd.exe

Emphasized words

typewriter Input to be typed in a command line or a GUI field.Examples:ping -t 192.168.0.1Enter World in the Domain field.

Output from a command, error messages, content of a statusline, 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:.png or :

[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 withspaces, for example [ESC] [SPACE] [M].

> The greater than symbol > is used to concatenate a series ofGUI items in order to depict a GUI path . This is an abridged pre-sentation of a procedure to be carried out in order to perform anaction 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 List of symbols and conventions (Cont.)


11/45


11

Troubleshoot Preface

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

1.5 Waste electrical and electronic equipment (WEEE) All waste electrical and electronic products must be disposed of separately from themunicipal waste stream via designated collection facilities appointed by the governmentor 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 poten-tial negative consequences for the environment and human health. It is a preconditionfor reuse and recycling of used electrical and electronic equipment.

For more detailed information about disposal of such equipment, please contact NokiaSiemens Networks.

The above statements are fully valid only for equipment installed in the countries of theEuropean Union and is covered by the directive 2002/96/EC. Countries outside theEuropean Union may have other regulations regarding the disposal of electrical andelectronic equipment.

1.6 RoHS complianceFPH800 complies with the European Union RoHS Directive 2002/95/EC on the restric-tion of use of certain hazardous substances in electrical and electronic equipment.

x(in card names)

For convenience, card names are sometimes listed with a lowercase 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.)

Issue Issue date Remarks1 May 2013 1st version

Table 3 History of changes


12/45


TroubleshootPreface

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-brominated biphenyls (PBB), and polybrominated diphenylethers (PBDE) in electricaland electronic equipment put on the market after 1 July 2006.

Materials usage information on Nokia Siemens Networks Electronic InformationProducts imported or sold in the Peoples Republic of China

FPH800 complies with the Chinese standard SJ/T 11364-2006 on the restriction of theuse of certain hazardous substances in electrical and electronic equipment. Thestandard applies to the use of lead, mercury, cadmium, hexavalent chromium, polybro-minated biphenyls (PBB), and polybrominated divinely ethers (PBDE) in electrical andelectronic equipment put on the market after 1 March 2007.

1.7 CE complianceFlexiPacket 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.

Figure 2 CE marking

1.8 MEF complianceFlexiPacket Hub 800 operating at the NNI delivers EPL, EVPL and E-LAN servicecomplies with the Metro Ethernet Forum MEF14 technical specification. FlexiPacketHub 800 operating at the UNI delivers EPL, EVPL and E-LAN service complies with the

Metro Ethernet Forum MEF9 technical specification.

Figure 3 MEF certified compliant logo

The product is marked with the CE marking


13/45


13

Troubleshoot About troubleshooting

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

2.1 OverviewIf 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 areprovided.

To troubleshoot a case where there is no alarm, go to Section 4 Non-alarm-triggeredtroubleshooting and locate the fault description that matches your case. Instructions forfurther investigating the problem and the steps needed to resolve the problem are pro-

vided.

2.2 Troubleshooting toolLoopback is used to test the network connection and diagnose the network problem. ForFPH800, all the physical interfaces, i.e, E1, SFP, GE ports, as well as the pseudowirecircuits can be tested by loopback.

For detailed information about loopback, please refer to Operate and Maintain Manual.


14/45


Troubleshoot Alarm-triggered troubleshooting

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

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

Figure 4 FPH800 WebLCT window

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

Figure 5 FPH800 alarm display

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


15/45


15


Figure 6 Alarm detailed information

3.1 Alarm list

3.1.1 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 UnavailableSFP_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 FailedNE 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 withPeer 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 NE alarms


16/45



3.1.2 P+E

3.1.3 PW

3.1.4 Synchronization

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)

Alarm name Action

Table 4 NE alarms (Cont.)

Alarm name Action

Short Circuit Section 3.3.1 Short Circuit

Table 5 P+E alarm

Alarm name Action

PW Down Section 3.4.1 PW Down

Remote Packet Loss Section 3.4.2 Remote Packet Loss

Table 6 PW alarms

Alarm name Action

Clock Source Deteriorate Section 3.5.1 Clock Source Deteriorate

Timing Quality Level Degraded Section 3.5.2 Timing Quality LevelDegraded

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 Sync alarms


17/45


17


3.1.5 STM-1/4

3.1.5.1 Regenerator section

3.1.5.2 Multiplex section

3.1.5.3 High order path

3.1.5.4 Low order path

Alarm name Action

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 Regenerator section alarms

Alarm name Action

MS-RDI 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

Table 9 Multiplex section alarms

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 High order path alarms

Alarm name Action

TU-LOP Section 3.6.4.1 TU-LOP

Table 11 Low order path alarms


18/45



3.1.6 EOS

3.1.6.1 HOVC (AU-4)

3.1.6.2 LOVC (TU-12)

3.1.7 E1

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

Alarm name Action

Table 11 Low order path alarms (Cont.)

Alarm name Action

GFP-UPM 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-LOMHP-VCAT-LOA Section 3.7.1.5 HP-VCAT-LOA

Table 12 HOVC (AU-4) alarms

Alarm name Action

LP-VCAT-LOM Section 3.7.2.1 LP-VCAT-LOM

LP-VCAT-LOA Section 3.7.2.2 LP-VCAT-LOA

Table 13 LOVC (TU-2) alarms

Alarm name Action

AIS (Far) Section 3.8.1 AIS (Far)

AIS (Near) Section 3.8.2 AIS (Near)

Table 14 E1 alarms


19/45


19


3.1.8 FlexBus

3.1.9 Ethernet

3.2 NE alarms

3.2.1 Cross First ThresholdSeverity

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 maycause the account log full.

Actions

Clear the account log or disable the account log feature.

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

Alarm name Action

Table 14 E1 alarms (Cont.)

Alarm name Action

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 E1 alarms

Alarm name Action

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 Ethernet alarms


20/45


21/45


21


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 FailSeverity

Major

Description

Fan failure.

Most Probable Cause

One of the fans in Fan card fault.

Actions

Replace the fan.

3.2.7 Scheduled Action FailureSeverity

Major

Description

The failure of a scheduled action to change Operational Status and SchedLastOpRe-sult.

Most Probable Cause

The scheduler did not invoke actions at appropriate time. Or the standby load isdamaged.

Actions

Check the standby load to see if it is a valid load.

3.2.8 SNTP Server UnavailableSeverity

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_AbsentSeverity

Critical


22/45



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_MismatchSeverity

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 AbnormalSeverity

Major

DescriptionSFP temperature is abnormal.

Most Probable Cause

SFP works not correct.

Actions

Check SFPs configuration and its status.

3.2.12 SFP Bias Current AbnormalSeverity

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 AbnormalSeverity


23/45


23


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 AbnormalSeverity

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 DownSeverity

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

SeverityMajor

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.


24/45



3.2.17 NE OverHeatingSeverity

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 ShroudSeverity

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 IDUSeverity

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 FailSeverity

Major

Description

The peer IDU is fail.

Most Probable Cause


25/45


25


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

Actions

Check peer IDU status.

3.2.21 Not in Dual ModeSeverity

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 plannedto work in dual-IDU mode, update dual-IDU license on both IDUs, then set working modeto dual-IDU mode.

3.2.22 Load MismatchSeverity

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 MatchSeverity

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 ShutdownSeverity

Critical


26/45



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 LoadSeverity

Minor

Description

SW switch is not allowed.

Most Probable Cause

Any component Standby FW version is not compatible with the HW version, the switchcommand can not be executed.

Actions

A new SW need to download.

3.2.26 Manual Operation OnSeverity

Test

Description

This alarm applies to E1/T1, STM-1/4 and Ethernet interface. This alarm is used indegugging 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 isconfigurable by the user. Dry contact is a RJ45 port on mainboard and generally connectto 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.


27/45


27


3.3 P+E alarm

3.3.1 Short CircuitSeverity

Major

Description

Overcurrent / undercurrent condition has been detected at the ODU Ethernet Inter-face.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 PW alarms

3.4.1 PW DownSeverity

Major

Description

PW#Operation status: lower layer down or mismatch in two ends

Most Probable CauseEthernet 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 LossSeverity

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 Lossalarm reports in local NE.

Actions

Check the CESoP servcie according to action of PW Down in peer NE.


28/45



3.5 Sync alarms

3.5.1 Clock Source DeteriorateSeverity

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

Actions

Check the link status of this clock source, and synchronization status of this sourcessource.

3.5.2 Timing Quality Level DegradedSeverity

Major

Description

Sync#Timing quality level degraded

Most Probable Cause

The quality level received from upstream synchronization network is lower than settingof SSM system clock threshold.

Actions

Check received quality level from upstream synchronization network.

3.5.3 Timing SSM MissingSeverity

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 con-nection between two NEs.

3.5.4 Timing Configuration Error Severity

Major

Description


29/45


29


The equipment is receiving SSM carrying a DNU code from at least one synchronizationinterface.

Most Probable Cause

The master slave state of PHY is master when the GE port is configured as a timingsource.

Actions

Make sure the master slave state of PHY is slave when the GE port is configured astiming source.

3.5.5 Timing Interface DownSeverity

Minor

DescriptionSync#Timing interface down

Most Probable Cause

A LinkState = Down has been detected in an Ethernet interface selected as synchroni-zation 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 UnlockSeverity

Major

Description

Sync#Timing unlock

Most Probable Cause

All timing sources are failed.

Actions

Check the failure cause of all timing sources.

3.6 STM-1/4 alarms

3.6.1 Regenerator section alarms

3.6.1.1 LOFSeverity

Critical

Description


30/45



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 LOSSeverity

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

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 thereceived STM-N RS trace identifiers.Check the correctness of expected RS trace iden-tifier.

3.6.2 Multiplex section alarms

3.6.2.1 MS-RDI

Severity


31/45


31


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

Most Probable Cause

In the upstream station (that reported the failure detects a malfunction at the receiveside), one of the following conditions is detected:

MS AIS (Multiplex Section Alarm Indication Signal), SPI-LOS (Loss Of Signal) or RS-LOF (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, orexcessive 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-AISSeverity

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, exclud-ing the STM-N MSOH.

Most Probable Cause

Upstream NE has inserted AIS signal.

Actions

Clear upstream inserted AIS.

3.6.2.3 MS-EXCSeverity

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 apreset threshold of 10-x, x = 3, 4, 5.

Actions


32/45



Check the upstream external cabling and equipment.

Check the threshold in the management system.

3.6.2.4 MS-DEGSeverity

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 apreset threshold of 10-x, x = 5, 6, 7, 8, 9.

Actions



3.6.3 High order path alarms

3.6.3.1 AU-LOPSeverity

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

Minor

Description

STM1/4#n Administrative Unit Alarm Indication Signal.AU-AIS is specified as all 1s inthe entire AU-4, including the AU-4 pointer. The VC-4 payload signal is replaced by thealarm indication signal.

Most Probable Cause


33/45


33


In one of the upstream nodes a defect is detected and led to the insertion of the alarmindication 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-RDISeverity

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

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

Critical

Description

STM1/4#n Higher Order Path Payload Mismatch.The received payload value, used toindication the composition of VC-4 payload, does not match the provisioned value.Thisalarm 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 viamanagement system in local node is not same as the actual payload value in far-endnode.


34/45



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

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



3.6.3.7 HP-EXCSeverity

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 apreset threshold of 10-x, x = 4, 5.

Actions


3.6.3.8 HP-TIMSeverity

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


35/45


35


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

3.6.4 Low order path alarms

3.6.4.1 TU-LOPSeverity

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

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

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. There-fore VC-12 overhead and payload data cannot be extracted.

Actions


Check on the management system if unit failure is reported for the unit generating themulti-frame alignment signal. In that node, remove the unit and replace it with a new one.


36/45



3.6.4.4 LP-TIMSeverity

Critical

Description

STM1/4#n LP#m lower order trace identifier mismatch. This alarm relies on the monitor-ing 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-UNEQSeverity

Major

Description

STM1/4#n LP#m lower order unequipped. This alarm relies on the monitoring switch: LPE1 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-RDISeverity

Minor

Description

STM1/4#n LP#m lower order remote defect indication. This alarm relies on the monitor-ing 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-PLMSeverity

Major

Description


37/45


37


STM1/4#n LP#m lower order path payload mismatch. The received payload value, usedto indication the composition of lower order path payload, does not match the provi-sioned value.

Most Probable CauseMapping mode of local and far-end nodes is not same. Expected payload value set viamanagement system in local node is not same as the actual payload value in far-endnode.

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 payloadvalue in far-end node.

3.6.4.8 LP-DEGSeverity

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 apreset threshold of 10-x, x = 5, 6, 7, 8, 9.

Actions



3.6.4.9 LP-EXCSeverity

Major

Description

STM1/4#n LP#m lower order path excessive error. This alarm relies on the monitoringswitch: LP E1 enable.

Most Probable Cause

An excessive error defect (dEXC) shall be detected if the equivalent BER exceeds apreset threshold of 10-x, x = 3, 4, 5.

Actions



38/45



3.7 EOS alarms

3.7.1 HOVC (AU-4)

3.7.1.1 GFP-UPMSeverity

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

Actions

Check configuration in both equipments.

3.7.1.2 GFP-LCSSeverity

Critical

Description

GFP customer signal failure

Most Probable CauseLink 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-LFSSeverity

Critical

Description

Loss of GFP frame synchronizationMost 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-LOMSeverity

Critical

Description


39/45


39


Higher order path virtual concatenation- loss of multiframe

Most Probable Cause

This alarm is detected when the multiframe alignment pattern error and virtual concate-

nation 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 witheach other.

3.7.1.5 HP-VCAT-LOASeverity

Critical

DescriptionHigher order path virtual concatenation - loss of alignment

Most Probable Cause

This alarm is detected when the differential delay exceeds the size of the alignmentbuffer.

Actions

Lessen the service paths or hops.

3.7.2 LOVC (TU-12)

3.7.2.1 LP-VCAT-LOMSeverity

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 concate-nation 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-LOASeverity

Critical

Description

Lower order path virtual concatenation - loss of alignment

Most Probable Cause


40/45



This alarm is detected when the differential delay exceeds the size of the alignmentbuffer.

Actions

Check the delay of VC member between two equipment and make sure the delay is lessthan alignment buffer.

3.8 E1 alarms

3.8.1 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 RDISeverity

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.


41/45


41


3.8.4 LOFSeverity

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 LOSSeverity

Critical

Description

E1/T1#n near end Loss of Signal.

The LOS state is considered to have occurred when the amplitude of the relevant signalhas 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 LoopedSeverity

Test

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


42/45



3.9 FlexBus alarms

3.9.1 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 Ethernet alarms

3.10.1 Autonegotiation MismatchSeverity

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 LOSSSeverity

Major

Description


43/45


43


IDU does not receive MCC loss threshold consecutive CCMs in the relevant MEP; analarm 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 DownSeverity

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 AISSeverity

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 LOSSeverity

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.


44/45


TroubleshootNon-alarm-triggered troubleshooting

4 Non-alarm-triggered troubleshootingThis section provides procedures to troubleshoot non-alarm-triggered fault causesinvolving the FPH800.

4.1 LEDs in FPH800FPH800 has four types of LEDs on the front panel to indicate the operational status ofthe system during operation.

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

Type Name Color State Function

Base

System

PWR Green ON Power on (either PWR A orPWR B or PWR A & PWR B)

Mode Blue/Green ON Blue indicates the Hybrid mode;

Green indicates the Packetmode

Blink

1 GHZ50%

The test condition is active (e.g.loopback, protection forcing)

ALM Red/Yellow ON Red indicates the alarm severityis Critical/Major;

Yellow indicates the alarmseverity is Minor/Warning

ODU Red ON ODU failure in at least one of theconnected ODUs, including bothon mainboard and plug-in cards

Ethernetelectricalinterfaces

Link (leftside)

Green ON Connection established

Active (rightside)

Green Blink Activity indication (on Rx or Tx)

SFP inter-face

Link Green ON Connection established

Active (leftside)

Green Blink Activity indication (on Rx or Tx)

STM-1interface

Active (rightside)

Green ON Activity indication (on Rx or Tx)and no LOS

FlexBusinterface

LOS/LOF Red ON Loss of signal or loss of frame

Connection Green ON Connection established;

No alarm

Table 17 LEDs indication


45/45

Troubleshoot Non-alarm-triggered troubleshooting

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

During the warm reboot period, the Microprocessor will be rebooted but the traffic willnot be interrupted, the system LEDs except the power LEDs will be set off; then after thereboot is finished system LEDs except the power LEDs will flash together one timewhich lasts for 1 second. Stop flashing is regarded as the finish point of reboot.

4.2 Cleaning dirty fiber optic ports and connectorsFiber optic transceivers are sensitive optical devices and should always be handled-carefully. 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 onthe ports when the ports are not in use.

f WARNING: The fiber optic lasers used in the device meet the regulatory requirementsfor casual exposure to the eye.

As with any source of bright light, however, Nokia Siemens Networks recommends notto 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 blowingacross all surfaces with a canned air duster.

A compressed gas, such as Chemtronics Ultrajet or the Triangle Tool GroupsLiquid-Tool Dust-A-Way, is recommended. Do not use commercial compressed airor 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.

Documents

09 Troubleshoot