Flexi Hybrid Troubleshooting

FlexiHybrid

Troubleshoot

A25000-A0300-F020-01-76P1

Issue: 1 Issue date: October 2009

2 A25000-A0300-F020-01-76P1Issue: 1 Issue date: October 2009

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 DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved.

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

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

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

A25000-A0300-F020-01-76P1Issue: 1 Issue date: October 2009

3

Troubleshoot

Table of ContentsThis document has 32 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5 Waste electrical and electronic equipment (WEEE) . . . . . . . . . . . . . . . . 91.6 RoHS compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Troubleshooting by front panel LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Troubleshooting by LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3 Protection against the short-circuits on the IDU-ODU cable . . . . . . . . . 222.4 Communication problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4.1 Cannot access the equipment using IP (Web / Telnet / SSH) . . . . . . . . 222.4.2 Web page resolution is improper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4.3 Unable to establish a safe connection . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4.4 Unable to access different network services . . . . . . . . . . . . . . . . . . . . . 222.4.5 Hardware Reset to Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1 IDU unit removing/installing/replacing procedures. . . . . . . . . . . . . . . . . 243.2 Replacing an IDU unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2.1 Controller unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2.2 Modem unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.3 Master IO unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.2.4 Expansion IO unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 Battery replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.4.1 Procedure for HC AP/CC ODU replacement . . . . . . . . . . . . . . . . . . . . . 313.4.2 Procedure for HC AP ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . 31


Troubleshoot

List of FiguresFigure 1 WEEE label. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Figure 2 LEDs of a 1+0/1+1 system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 3 Alarm code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 4 Units layout of the “FlexiHybrid” assembly . . . . . . . . . . . . . . . . . . . . . . . 24Figure 5 Thumbscrew and Corner Screw Locations . . . . . . . . . . . . . . . . . . . . . . . 25Figure 6 Threaded Hole Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 7 Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 8 Removing the Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 9 Battery location and holder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 10 Removing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 11 Contact lever correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 12 Replacing the battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 13 HC AP/CC ODU Disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 14 HC AP ODU Disconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


5

Troubleshoot

List of TablesTable 1 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Table 2 List of conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . 7Table 3 History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 4 Modem status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 5 Alarms mapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 6 Alarm descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


Troubleshoot


7

Troubleshoot Preface

1 PrefaceThis document provides the information to troubleshoot the FlexiHybrid and to restore the normal operating conditions.

1.1 Intended audienceThis document is intended to the Operators in charge to troubleshoot the FlexiHybrid.

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

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

Chapter Title Subject

Chapter 1 Preface Provides an introduction to the document and the safety instructions

Chapter 2 Troubleshooting Provides the information to troubleshoot the FlexiHybrid

Chapter 3 Replacement procedure Provides the information to replace the FlexiHybrid and to restore the normal operating conditions

Table 1 Structure of this document

Representation Meaning

Bold Text in the graphical user interface (window and wizard titles, field names, buttons, etc.) is represented in bold face.

Example: Click Shutdown and then click OK to turn off the com-puter.

Italic Field values, file names, file extensions, folder and directory names are denoted by italic text.

Examples: Enter 192.168.0.1 in the IP address field. Click OK to produce a .pdf file.

Courier Command and screen output are denoted by courier font.

Example: ping -t 192.168.0.1

Table 2 List of conventions used in this document


TroubleshootPreface

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

<Angle brackets> Place holders for distinct names or values are represented by enclosing them in <angle brackets>. If a file name is involved, italic text will also be used.

Example: The naming convention for the log files is <NEname>.txt, where <NEname> is the name of the NE sending the messages.

Keyboard button Keyboard keys are represented with a surrounding box.

Example: Press Enter .

[Square brackets] Keyboard shortcuts are represented using square brackets.

Example: Press [CTRL+ALT+DEL] to open the Task Manager.

> The “>” symbol is used as short form to define a path through indi-vidual elements of the graphical user interface, e.g., menus and menu commands.

Example: On the Windows taskbar, select Start > Programs > TNMS > Client menu command to start the TNMS Core/CDM Client.

☞ A tip provides additional information related to the topic described.

g A note provides important information on a situation that can cause property damage or data loss.

A note introduced in the text by the keyword NOTICE: describes a hazard that may result in property damage but not in personal injury.

f A safety message provides information on a dangerous situation that could cause bodily injury.

The different hazard levels are introduced in the text by the follow-ing keywords:

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.

Representation Meaning

Table 2 List of conventions used in this document (Cont.)


9

Troubleshoot Preface

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 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 poten-tial 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 complianceFlexiPacket Radio complies with the European Union RoHS Directive 2002/95/EC on the restriction of use of certain hazardous substances in electrical and electronic equip-ment.

The directive applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-brominated 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 People’s Republic of ChinaFlexiPacket Radio complies with the Chinese standard SJ/T 11364-2006 on the restric-tion of the use of certain hazardous substances in electrical and electronic equipment. The standard applies to the use of lead, mercury, cadmium, hexavalent chromium, poly-

Issue Issue date Remarks

1 October 2009 First version

Table 3 History of changes


TroubleshootPreface

brominated biphenyls (PBB), and polybrominated diphenyl ethers (PBDE) in electrical and electronic equipment put on the market after 1 March 2007.


11

Troubleshoot Troubleshooting

2 Troubleshooting

2.1 Troubleshooting by front panel LEDsThe malfunctions are pointed out through LEDs on the equipment and on the indoor assembly front panel (see Figure 2).

The function of the front panel indications is described in section 2.2 Troubleshooting by LCT.

All models of the “FlexiHybrid” support a variety of front panel configurations that depend on the capacity configuration.

Figure 2 shows a typical “FlexiHybrid” 1+0 and 1+1 configuration and the associated LEDs displayed on the front panel. The controller, standard I/O, and each modem card have a status LED.

Figure 2 LEDs of a 1+0/1+1 system

The modem status LED indicates the modem status as described in Table 4.

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

Status LED

1+0 configuration

1+1 configuration


TroubleshootTroubleshooting

The controller status LED is the primary front panel indicator of alarms. An alarm is gen-erated when a specific condition is identified and is cleared when the specified condition is no longer detected. When an alarm is posted:

1. The controller status LED turns orange for 5 seconds2. The controller status LED turns off for 5 seconds3. The controller status LED flashes orange for the number of times specified by the

first digit of the alarm code4. The controller status LED turns off for 3 seconds5. The controller status LED flashes orange for the number of times specified by the

second digit of the alarm code

Steps 2-5 are repeated for each alarm posted. The entire process is repeated as long as the alarms are still posted.

The standard I/O and modem status LEDs set to red when certain alarms are posted. A complete list of alarms is given in Table 5.

LED STATUS

Green Active Locked Link

Orange Standby Locked Link (1+1 Non-Diversity Only)

Flashing Green Low SNR

Flashing Orange Unlocked

Flashing Red ODU -48V power is disabled

Red ODU Power Fault (occurs when the -48V to the WBMODEM provides low or excessive current. In either case, the -48V is disabled by the hardware).

Modem Hardware Fault (occurs when any of the power-on self tests failed or in case of IF Power Fault, or Digital Power Fault detected during normal operation)

Table 4 Modem status LED


13


2.2 Troubleshooting by LCTThe equipment is provided with an alarm system, with different signaling modes (via software, LED, connector outputs), that starting from an alarm signal allows the operator to promptly identify the failed module or function.

Each time an alarm is posted or cleared, a log of such posting or clearing is localized on the IDU (300 message deep circular buffer) and sent to a syslog server, if so configured.

The alarm severity mapping is based on Syslog severity as in Table 5.

Each alarm can be masked by the user via GUI or SNMP. Each posted alarm generates an SNMP trap (if SNMP traps are configured), as well as when cleared.

Each alarm can be mapped to the output alarms 1-4 as per user configuration.

The alarm codes shown in Table 6 start flashing orange to indicate the alarm status on the Controller Card LED. The Alarm codes for the controller card faults flash red.

When an alarm is posted the LED to RED column in Table 6 specifies which, if any LED is set to the red color.

Alarm severity Syslog Severity

Critical Critical

Major Error

Info Info

Table 5 Alarms mapped

Alarm Affected Component

Description LED to RED

Alarm Code

Severity

Modem Fault Lower

Modem The specified Modem card has indicated a fault.

Modem Lower

11 Critical

Modem Comm Failiure Lower

Modem The Controller Card is unable to communi-cate with the specified Modem card.

Modem Lower

12 Critical

Modem Card Removed Lower

Modem The specific Modem card has been removed from the IDU (only if the specified Modem card has been enabled for use). This alarm is not shown in the Active alarm list but only in the Alarm history.

N/A 13 Major

Modem Card Installed Lower

Modem The specified Modem card has been installed into the IDU (only if the specified Modem card is not enabled for use). Alarm is raised then lowered.

N/A 14 Info

Modem Unlock Lower

Modem The demodulation functional components of the modem have not locked to the incoming signal. The data received through the RF link is not valid.

N/A N/A Critical

Table 6 Alarm descriptions



RSL Low Lower Modem RSSI is approaching the minimum opera-tional level of the link.

N/A N/A Major

Synthesizer Unlock Lower

Modem Modem synthesizer has unlocked. N/A N/A Critical

SNR Low Lower Modem The signal-to-noise ratio is below the minimum operational level of the link.

N/A N/A Major

Modem Fault Upper

Modem The specified Modem card has indicated a fault.

Modem Upper

16 Critical

Modem Comm Failiure Upper

Modem The Controller Card is unable to communi-cate with the specified Modem card.

Modem Upper

17 Critical

Modem Card Removed Upper

Modem The specific Modem card has been removed from the IDU (only if the specified Modem card has been enabled for use). This alarm is not shown in the Active alarm list but only in the Alarm history.

N/A 18 Major

Modem Card Installed Upper

Modem The specified Modem card has been installed into the IDU (only if the specified Modem card is not enabled for use).

N/A 19 Info

Modem Unlock Upper

Modem The demodulation functional components of the modem have not locked to the incoming signal. The data received through the RF link is not valid.

N/A N/A Critical

RSL Low Upper Modem RSSI is approaching the minimum opera-tional level of the link.

N/A N/A Major

SNR Low Upper Modem The signal-to-noise ratio is below the minimum operational level of the link.

N/A N/A Major

Synthesizer Unlock Upper

Modem Modem synthesizer has unlocked. N/A N/A Critical

Fan Failure Controller The Fan rotational speed is too low. (Control-ler card LED flashed red rather than orange).

Controller 21 Major

Controller Card Fault

Controller The CPU has detected a fault in the controller card. (Controller card LED flashes red rather than orange).

Controller 22 Critical

Low Battery Voltage

Controller The CPU has detected a low-battery voltage condition. (Controller card LED flashes red rather than orange).

Controller 23 Info



Alarm Code

Severity

Table 6 Alarm descriptions (Cont.)


15


Power Supply Fault Lower

Power Supply

The Power Supply card has indicated a fault.

Note: When both power supply modules are installed, the LED will turn to red on the faulty supply when either the +5V or the -48V is not-present.

No LED light: either or both-48V or 5V not present

Red LED: 3.3Vnot present

31 Critical

Power Supply Card Removed Lower

Power Supply

The specified Power Supply card has been removed from the IDU.

N/A 32 Major

Power Supply Fault Upper

Power Supply

The Power Supply card has indicated a fault.

Note: When both power supply modules are installed, the LED will turn to red on the faulty supply when either the +5V or the -48V is not-present.

No LED light: either or both-48V or 5V not present

Red LED: 3.3Vnot present

36 Critical

Power Supply Card Removed Upper

Power Supply

The specified Power Supply card has been removed from the IDU.

N/A 37 Major

Master I/O Card Removed

Master IO The Master I/O card has been removed from the IDU.

N/A 41 Critical

Ethernet Payload Discon-nect

Master IO There is no cable detected at either Ethernet payload on Standard I/O card (only if Ethernet mode enabled).

I/O 42 Critical

Mini I/O Card Removed

Mini IO The Mini I/O card has been removed from the IDU (only if Mini I/O card has been enabled for use).

I/O 46 Critical

Mini I/O Card Installed

Mini IO The Mini I/O card has been installed into the IDU (only if Mini I/O card is enabled for use).

I/O 47 Info

Expansion I/O Card Removed

Exp IO The Expansion I/O card has been removed from the IDU (only if the Optional I/O card has been enabled for use).

N/A 26 Critical

Expansion I/O Card Installed

Exp IO The Expansion I/O card has been installed into the IDU.

Expansion I/O

27 Info



Alarm Code

Severity




T1E1 Channel Alarm Ch x

(see Note 2 at the bottom of the table)

Master IO (1-42)

Exp IO (1-21)

There is either no cable detected at the spec-ified E1 channel port on Standard I/O Card or there is an AIS condition detected (only for active E1 channels). If both conditions are present, then the disconnect alarm shall be prioritized with respect to the AIS alarm.

Master I/O

Expansion I/O

Turn LED orange rather than RED

43-58 (1-16) and 142-167 (17-42)

81-96 (1-16) and 168-172 (17-21)

Critical

E1 Test Mode Master IO The user has selected a E1 test mode (loop-back or Tx Data).

N/A 59 Info

BERT/LB/CW Test Mode

Master IO This alarm shall be set when the user enables either BERT,, Loopback, or CW mode, and cleared when all BERT, Loopback and CW modes are disabled.

N/A 69 Info

ODU Fault Lower

ODU The ODU has indicated a fault condition. Fault detection via polling of ODU or unsolic-ited message, if supported. (The IDU then maps the alarm into a 2-digit code to match the alarms reported in the Protection Switch code For example, Bit 0 corresponds to the TX_ALM, Bit 1 corresponds to the mP_TX_DET_ALM and so on for the Alarm Code returned with the ODU_FAULT alarm).

N/A 71 Critical

ODU Comm Failure Lower

ODU The IDU is unable to communicate with the ODU. The cause of the problem might be the ODU or the cable connecting the ODU to the IDU.

N/A 72 Critical

ODU Fault Upper

ODU The ODU has indicated a fault condition or unsolicited message, if supported. (The IDU then maps the alarm into a 2-digit code to match the alarms reported in the Protection Switch code For example, Bit 0 corresponds to the TX_ALM, Bit 1 corresponds to the mP_TX_DET_ALM and so on for the Alarm Code returned with the ODU_FAULT alarm)

N/A 73 Critical



Alarm Code

Severity



17


ODU Comm Failure Upper

ODU The IDU is unable to communicate with the ODU. This could be a problem with the ODU or a problem with the cable connecting the ODU to the IDU.

N/A 74 Critical

Protection Switch (see Note 3 at the bottom of the table)

MODEM/ODU

This alarm shall be set then cleared when a TX protection switch occurs during 1+1 hot standby operation.

N/A 75 Major

East ATPC Tx at Max Power

ODU The IDU is unable to increase the Tx Power as requested by link partner due to the maximum power being reached.

N/A 76 Info

West ATPC Tx at Max Power

ODU The IDU is unable to increase the Tx Power as requested by link partner due to the maximum power being reached.

N/A 78 Info

Link Fault IDU Failed to receive link heartbeat from link partner via Radio Overhead (ROH) channel.

N/A 81 Critical

Remote Fault IDU Link Partner IDU indicating it has a fault con-dition. Local IDU receives Link Partner.

N/A 82 Info

Encryption Failure

IDU Data is not being decrypted properly due to encryption key mismatch between link part-ners.

N/A 83 Critical

Encryption OneWay

IDU Only one IDU has data encryption enabled. N/A 84 Major

External Alarm 1 External The external Alarm 1 input has been acti-vated.

N/A 91 Info


N/A 92 Info


N/A 93 Info


N/A 94 Info

Remote IDU Alarm

Link Partner IDU

The link partner IDU has indicated an alarm condition.

N/A 95 Major

Remote IDU External Alarm 1

Link Partner External

The link partner IDU has indicated via ROH that its external alarm input 1 has been acti-vated.

N/A 96 Info




N/A 97 Info



Alarm Code

Severity







N/A 98 Info



The link partner IDU has indicated via ROH its external alarm input 4 has been activated.

N/A 99 Info

STM Loss of Clock

IDU The SDH clock has not locked. N/A Solid Critical

STM_LOS IDU The SDH has a Loss of Signal Defect. N/A Solid Critical

STM RS_B1 IDU The SDH Mux/Demux has a B1 Defect. N/A Solid Major

STM RS_LOF IDU The SDH Mux/Demux has a Loss of Frame Defect.

N/A Solid Critical

STM RS_OOF IDU The SDH Mux/Demux has a Out of Frame Defect.

N/A Solid Critical

STM RS_TIM IDU The SDH Mux/Demux has a Trace Identifier Mismatch Defect.

N/A Solid Major

STM MS-AIS IDU The SDH Mux/Demux has detected an AIS at the Multiplexer Level.

N/A Solid Critical

STM MS-REI IDU The SDH Mux/Demux has detected a Remote Error at the Multiplexer Level.

N/A Solid Major

STM MS-RDI IDU The SDH Mux/Demux has detected a Remote Defect at the Multiplexer Level.

N/A Solid Major

STM MS_B2 IDU The SDH Mux/Demux has a B2 Defect at the Multiplex level.

N/A Solid Major

STM AU-AIS x IDU The SDH Mux/Demux has detected an AIS at the AU Level (see Note 1 at the bottom of the table).

N/A Solid Critical

STM AU-LOP x IDU The SDH Mux/Demux has detected a Loss of Pointer Defect at the AU Level (see Note 1 at the bottom of the table).

N/A Solid Critical

STM HP-UNEQ x

IDU The SDH Mux/Demux HP number 'x' is Unequipped.

N/A Solid Major

STM HP-TIM x IDU The SDH Mux/Demux HP number 'x' has a Trace Identifier Mismatch (see Note 1 at the bottom of the table).

N/A Solid Major

STM HP-REI x IDU The SDH Mux/Demux HP number 'x' has a Remote Error Indication.

N/A Solid Major

STM HP-RDI x IDU The SDH Mux/Demux HP number 'x' has a Remote Defect Indication.

N/A Solid Major



Alarm Code

Severity



19


STM HP-PLM x IDU The SDH Mux/Demux HP number 'x' has a Path Identifier Mismatch.

N/A Solid Critical

STM HP_B3 x IDU The SDH Mux/Demux HP number 'x' has a CRC Error.

N/A Solid Major

STM TU-LOM x (x: ch#1..#63)

IDU The SDH Mux/Demux TU number 'x' has a Loss of Multiframe.

N/A Solid Critical

STM TU-AIS x (x: ch#1..#63)

IDU The SDH Mux/Demux TU number 'x' has an AIS (see Note 1 at the bottom of the table).

N/A Solid Critical

STM TU-LOP x (x: ch#1..#63)

IDU The SDH Mux/Demux TU number 'x' has a Loss of Pointer Defect (see Note 1 at the bottom of the table).

N/A Solid Critical

STM LP-UNEQ x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' is Unequipped (see Note 1 at the bottom of the table).

N/A Solid Major

STM LP-TIM x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a Trace Identifier Mismatch (see Note 1 at the bottom of the table).

N/A Solid Major

STM LP-REI x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a Remote Error Indication (see Note 1 at the bottom of the table).

N/A Solid Mahor

STM LP-RDI x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a Remote Defect Indication (see Note 1 at the bottom of the table).

N/A Solid Major

STM LP-PLM x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a Path Identifier Mismatch (see Note 1 at the bottom of the table).

N/A Solid Critical

STM LP-RFI x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a Remote Fault Indication (see Note 1 at the bottom of the table).

N/A Solid Critical

STM LP-BIP2 x (x: ch#1..#63)

IDU The SDH Mux/Demux LP number 'x' has a CRC Error (see Note 1 at the bottom of the table).

N/A Solid Major

SDIDU Power-Up

IDU Indicates the SDIDU has been powered-on. N/A Solid Info

SDIDU Re-boot IDU Indicates the SDIDU has been re-booted. N/A Solid Info

NTP Update IDU Indicates the system time is updated via NTP. N/A Solid Info

FPGA Mismatch IDU When the FPGA image(s) does not match the installed Master IO card, this alarm shall be set.

N/A Solid Critical



Alarm Code

Severity




FPGA Program-ming Failure

IDU When the FPGA programming fails, this alarm shall be set.

N/A Solid Critical

Reconfiguration Failure

IDU When the local SDIDU configuration fails then lower this alarm.

N/A Solid Info

East PDH Pro-tection Switch

IDU When the FPGA initiates a PDH Ring Protec-tion Switch this Alarm shall be set.

N/A Solid Major

West PDH Pro-tection Switch

IDU When the FPGA initiates PDH Ring Protec-tion Switch this Alarm shall be set.

N/A Solid Major

Receive Protec-tion Switch

IDU It informs the user that a receive side protec-tion switch has occurred. There are no user controls for a receive protection switch. The framer is always receiving from both east and west modems in a 1+1 configuration and may switch active receivers if the quality is better on one side versus the other. The receive pro-tection switch is an informational alarm to note a switch occurred. Both east and west receivers are always receiving the data. The system chooses the cleanest receive channel. The 0x1 code indicates that there was one receive protection switch, since the system software read the count in the Master IO FPGA. The count is the number of receive protection switches since the last read. Receive protection switching would be expected in fade testing, since the quality of the signal is being diminished and the Framer is having to try to choose the best signal.

N/A Solid Info

SFP Module Installed

Master IO The SFP module has been installed into the IDU (only if GigE card is installed). This alarm is not shown in the Active alarm list but only in the Alarm history.

Master IO N/A Info

SFP Module Removed

Master IO The SFP module has been removed from the IDU (only if GigE card is installed). This alarm is not shown in the Active alarm list but only in the Alarm history.

Master IO N/A Info

SFP Module TX Fault

Master IO The SFP module fault (only if GigE card is installed). This alarm is not shown in the Active alarm list but only in the Alarm history.

Master IO N/A Major



Alarm Code

Severity



21


☞ Note 1: The information of which channel has the active alarm is shown in the Alarm History only. In Active alarm list and SNMP interface only one alarm is present. It is the OR function of all the detailed alarms: it is active if at least one alarm is active. It is inactive if all the detailed alarms are inactive.

☞ Note 2: In the "Alarm Configuration" screen, the entry, "T1/E1 Channel Disconnect" is used to configure two alarms - T1/E1 Disconnect and T1/E1 AIS. The "Active Alarms" & "Alarms History" page displays "T1/E1 Channel Disconnect" when the cable is disconnected; displays "T1/E1 channel AIS" when the AIS condition exists when the cable is connected.

☞ Note 3:

SFP Payload Disconnect

Master IO There is no cable detected at the SFP module (only if Ethernet mode enabled and GigE card installed). If this alarm is active but it is masked, the Link LED in the Gigabit Card is Orange instead of Green.

Master IO N/A Info

SDIDUTemperature out of Range

IDU The specified operating temperature of the SDIDU has exceeded the upper or lower tem-perature limit.

N/A N/A Info

ODU East Tem-perature Out Of Range

ODU The specified operating temperature of the East ODU has exceeded the upper or lower temperature limit.

N/A N/A Info

ODU West Tem-perature Out Of Range

ODU The specified operating temperature of the East ODU has exceeded the upper or lower temperature limit

N/A N/A Info

ODU MODE NOT AUTHO-RIZED

IDU When the system detects that the ODU oper-ational mode is not authorized during bootup.

N/A N/A Critical

IDU MODE NOT AUTHORIZED

IDU When the system detects that the IDU opera-tional mode is not authorized during bootup.

N/A N/A Critical

Adaptive Modu-lation Lower Level

Modem ACM feature is working for specific link and the mode is switched to level 2 or 3

N/A N/A Critical

Adaptive Modu-lation Upper Level

Modem ACM feature is working for specific link and the mode is switched to level 2 or 3

N/A N/A Critical



Alarm Code

Severity




Figure 3 Alarm code

2.3 Protection against the short-circuits on the IDU-ODU cableIf the protection against the short-circuits becomes active, to restore the operation disable the ODU by the LCT and then enable again the ODU.

2.4 Communication problems

2.4.1 Cannot access the equipment using IP (Web / Telnet / SSH)– Verify the IP Address or Hostname of the equipment– Determine if the terminal is up by pinging the equipment– Check your PC’s Network Configuration– Check Cables

2.4.2 Web page resolution is improper– The pages are best viewed at resolutions of 1024x768 or greater– The pages are best viewed using Microsoft Internet Explorer Version 5.5 and above.

2.4.3 Unable to establish a safe connection– Ensure that the HTTP Access in the Security Configuration of the system is set to

HTTP (SSL)– Check if “Use SSL 2.0” and “Use SSL 3.0” options are selected in the Security

Options of the browser

2.4.4 Unable to access different network services– Telnet

1. Verify possibilities mentioned in section 2.4.12. Telnet may be disabled.

– SSH1. Verify possibilities mentioned in section 2.4.12. SSH may be disabled

– Serial


23


1. Verify the serial cable and proper connection.2. Serial port may be disabled.

– WEB1. Verify possibilities mentioned in section 2.4.1.2. HTTP / Secure-HTTP access may be disabled.

☞ The User can automatically logon (default) through:

– Telnet– Web HTTP support– SNMP Manager– Serial Connection

These interfaces can be configured in:

1. The “Security Configuration Screen” as:a) Command Line Interface – Telnet / SSH / Disabledb) HTTP Access – HTTP With SSL / HTTP Without SSL / Disabled

2. The “Serial Configuration Screen” as:a) Device Selection – Modem with IP / Modem Without IP / RS232

2.4.5 Hardware Reset to Factory DefaultsThe equipment may be reset to factory defaults during power up. A power on reset affects the IP address and the user logins/passwords.

To power on reset:

1. Power on the equipment2. During bootup, the equipment controller-card LED will start blinking3. Make sure the call button is not active for five seconds at startup4. While the LED is flashing first press the call button and then release it.


TroubleshootReplacement procedure

3 Replacement procedure

3.1 IDU unit removing/installing/replacing proceduresAt times, it may be necessary to service the “FlexiHybrid”.

This may include:

– removing a unit– installing a unit – replacing a unit

There may be up to 8 modules installed in a single “FlexiHybrid” chassis. Figure 4 shows the front panel of the “FlexiHybrid” with each module labeled

The basic procedure for removing and installing a module is common to all the modules, with slight variations for the Power Supply Module, Controller Module, and Mini IO Module.

These basic procedures are described below.

Figure 4 Units layout of the “FlexiHybrid” assembly

☞ If a different type of unit has to be installed, then the following process should be used: Power down the equipment, replace the unit, power up the equipment, reload the FPGA (if required for IO change), and then perform a link reconfiguration.

Removing a unit

1. Units are static sensitive and should only be handled in an ESD-safe environment.When packaging units for shipment or storage, place in an ESD bag.

2. Remove front panel connections from the unit.3. Remove the two thumbscrews on either side of the unit. Figure 5 shows the loca-

tions of these thumb screws.3.1 The thumbscrew for the Standard IO unit is located on the right of the Mini IO

unit slot.3.2 If a Mini IO unit is installed and the Standard IO unit is to be removed, both units

will be removed as one unit.3.3 When removing only the Mini IO card, remove the corner screw indicated in

Figure 5 and one thumb screw.

Power Supply Unit 1

Power Supply Unit 2 Controller Unit E1 Expansion I/O Unit West Modem and IF/Telemetry Unit

East Modem and IF/Telemetry Unit Master I/O Unit STM-1

Mini I/O Unit


25

Troubleshoot Replacement procedure

Figure 5 Thumbscrew and Corner Screw Locations

4. Thread thumbscrew(s) into hole(s) shown in Figure 6. Remove the unit by grasping the thumbscrew(s) and pulling unit straight out of the “FlexiHybrid”.Both thumbscrews should be used for all units except for the Power Supply and the Mini IO units.4.1 The Power Supply and Mini IO units have only one threaded hole each.4.2 When removing the Standard IO unit, the ground lug indicated in Figure 6 is

used as the second threaded hole. If the “FlexiHybrid” is to remain powered ON and the ground lug is being used to ground the unit, first move the ground con-nection from the ground lug located on the Controller unit.

The “FlexiHybrid” keeps its current configuration when a unit is removed, except when that unit is the Controller unit. In which case, the IP addresses will need to be repro-grammed.

Figure 6 Threaded Hole Locations

☞ Note on Modem unit extractionWhen a Modem unit is extracted alarm "Remore fault" arises in the local equipment and alarms "Modem unlock" "SNR lower" "RSL lower" arise in the remote equip-ment.

When the alarm disappear, alarm "Modem card removed" will appear in the local history.

Installing a unit

1. Units are static sensitive and should only be handled in an ESD-safe environment.When packaging units for shipment or storage, place in an ESD bag.

2. Line up the unit board with the guides in the chassis and slide the unit into the “Flex-iHybrid”. Figure 7 shows a photo of the guides. As the unit face plate abuts with the face of the “FlexiHybrid”, connectors on the back of the unit will fit into the “FlexiHy-brid” backplane. Interference from adjacent unit front-panels might be encountered. If this occurs, loosen the thumbscrews holding the adjacent panels and adjust them accordingly until correctly in place.

Tumbsscrew

Corner screw

Threaded Hole

Ground Lug



2.1 Only the Mini IO unit has one guide on the right. Take care to insert the Mini IO unit carefully, and correctly engage the rear connector with its mate on the Standard IO unit.

Figure 7 Guides

3. Install thumbscrews on either side of the unit as shown in Figure 6.3.1 The Mini IO card has a corner screw, which should be installed. This corner

screw is shown in Figure 6.4. Make front panel connections to the unit and, if necessary, power ON the “FlexiHy-

brid”.5. Verify proper unit operation.

5.1 If the Controller unit has been changed, reprogram the IP addresses.

☞ Note on the hot insertion of the Modem unitThere is no problem, when a unit is fully inserted in one shot, but if the unit is plugged just to light up some LEDs, then the "modem_fault" alarm switches on (complete with a steady red LED on the unit itself); fully inserting the unit at this stage (i.e. pushing it all the way) keeps the alarm forever, even if all seems to be working all right. In a case like this, it is required to extract and plug the Modem unit again.

☞ Note on the extraction/insertion of the modem unitIt is possible to extract and insert the modem quickly enough to not allow the system to appropriately shutdown the modem related processes. Extracting and inserting the modem again will re-send the appropriate system signal and appropriately shutdown and restart the modem related processes.


27


3.2 Replacing an IDU unitg Pay attention to pull out the units, because no special tool is available.

3.2.1 Controller unit replacementThe replacement of the Controller unit can be hot-swap or cold-swap.

The spare controller must be a "clone" of the Controller unit to be replaced. "Clone" means that the same versions of software components (Application, Kernel, FPGA of the equipped units etc.) reside in the same banks as are in the Controller being replaced.

☞ If the spare controller has different versions of the software components and comes from IDU with different Master I/O equipped as to the Controller unit to be replaced, insert the spare Controller unit (No mismatch alarm will appear and the Reprogram-ming screen will shows correctly the running version), upgrade all the SW compo-nents different and FPGA controller and Master I/O with FTP and finally modify the alarm masking, if it has been modified as to the defualt version (the modified alarm masking resides only in the Controller unit).

☞ The system is designed so as not to lose link on a Controller unit hot-swap. Conse-quently, the framer FPGA on the Master IO card is not reprogrammed, when a new Controller is hot-swapped. The check for a mismatch is only valid and done at the time the Master IO FPGA is being programmed.

Case 1: Hot-swapWhen the Controller is hot-swapped (or warm booted) a copy of the system configura-tion (kept in the equipment, apart from the Controller unit) is loaded to the new Control-ler unit. So the IP address and other configuration data are preserved from the old Controller unit.

1. Remove the failed Controller unit.2. Insert the clone spare Controller unit. Automatically will start the reboot of the equip-

ment.3. Modify the alarm masking, if it has been modified as to the defualt version. (the

modified alarm masking resides only in the Controller unit).

Case 2: Cold-swapWhen the equipment power is turned off, the Controller is replaced and power is turned on, the configuration is loaded from the new Controller unit. So the IP address and other configuration data are loaded from the last configuration stored in the new Controller FLASH memory. If the system configuration stored in the new controller card is desired (e.g. IP address), the system should be powered off before the new controller is inserted.

1. Power off the equipment.2. Remove the failed Controller unit.3. Insert the clone spare Controller unit.4. Power on the equipment. Automatically will start the reboot of the equipment.



3.2.2 Modem unit replacementReplace the Modem unit with the spare Modem unit and verify the firmware version. If different, upload the new version.

3.2.3 Master IO unit replacementWhen replacing a faulty Master IO unit with a spare Master IO unit, a FPGA mismatch alarm appears, always re-download the FPGA with the running version also if in the Reprogramming screen the version is correct.

☞ All the QoS settings have to be reconfigured even if the reprogramming show them active.

3.2.4 Expansion IO unit replacementWhen replacing a faulty Expansion IO unit with a spare Expansion IO unit, always re-download the FPGA with the running version also if in the Reprogramming screen the version is correct.

3.3 Battery replacementg The battery might explode if not replaced properly. Replace only with the same type

or with an equivalent one recommended by the manufacturer. Dispose of used bat-teries according to the manufacturer's instructions.Panasonic is the battery manufacturer of the (Part Number: 2032). Disposal instructions are available on the Panasonic website. Please dispose in accordance with local laws.

These instructions state how to replace the battery on the Controller Unit in the IDU. It may be necessary to replace the battery after a “Low Battery Voltage” alarm (alarm code 23). A “Low Battery Voltage” alarm code is usually generated when the battery’s charge is depleted due to usage or ageing, or because the battery contacts are slack. Both causes are dealt with below.

Before You BeginBefore starting the replacement procedure make sure that the following items are avail-able:

– Small flat head screw driver– Small needle-nose pliers– Panasonic CR2032 or equivalent battery– Electrostatic Discharge (ESD) safe workspace

Replacement Procedure

1. Handle the Controller Module in an ESD safe work area.2. Remove the Controller Module from the IDU chassis by unscrewing the thumb-

screws on either side of the card, as indicated in Figure 8. Move the thumbscrews to the threaded holes indicated in Figure 8. If the threaded hole closest to the ground stud is not accessible, the ground stud may be used in its place. Grasp the thumb-screws and pull the Controller Module assembly straight out from the chassis.


29


Figure 8 Removing the Controller Module

3. The battery is located near the rear edge of the card, as shown in Figure 9 The battery holder has a locking tab, a contact lever and a bottom contact plate (not shown).

Figure 9 Battery location and holder

4. Use the flat head screw driver to depress the locking tab on the battery holder and gently slide the battery out from underneath the contact arm, as shown in Figure 10. Be very careful not to bend the contact arm. Also, be careful not to break the locking tab, as it is made of plastic.

Figure 10 Removing the battery

5. Once the battery has been removed, the contact arm should make contact with the bottom contact plate. If it does not (an example is shown in Figure 11), the lever contact should be bent back into position. Grasp the lever contact with the needle nose pliers next to the bend location and gently torque down on the arm to bend it slightly, as shown in Figure 11. Repeat this procedure until the lever arm makes contact with the base contact. Figure 11 shows the lever arm position after correc-tion.



Figure 11 Contact lever correction

6. Before installing a new battery, clean the contact surfaces by scraping them with the screwdriver.

7. To install the new battery, depress the locking tab with the screwdriver, slide the new battery into place under the lever arm, and release the locking tab (Figure 12). The battery should be oriented with the positive (+) side up. Again, be careful not to bend the lever arm or break the locking tab.

Figure 12 Replacing the battery

8. Slide the Controller Module back into the chassis until it is flushed with the rest of the front panel. There will be some resistance as the board engages with the back plane.

9. Remove the thumbscrews from the threaded holes and return them to their original position on either side of the Controller Module.

10. The Controller Module should be powered on within one hour after battery replace-ment is completed.

11. The “Low Battery Voltage” alarm will not be cleared till the Controller Module is powered again. This can be accomplished by removing the module and re-engaging it in a powered-on IDU or by powering the entire IDU. Allow at least 1 minute between the power cycles.

12. The time and date must be reset after battery replacement. Instructions for setting the time and date are reported in the OMN Manual.

3.4 ODU replacementThis paragraph illustrates the procedure to follow when having to replace the faulty ODU.

To simplify the description, the following procedures concern the disassembling of the parts to replace. Obviously to place the spare part back proceed in the reverse manner.


31


3.4.1 Procedure for HC AP/CC ODU replacement To replace the ODU remove the ODU from the supporting framework fastened to the mast.

The procedure to follow is specified below (refer to Figure 13):

a) Power off the “FlexiHybrid” IDU b) Pull out the IF cable.c) Disconnect ground.d) Disconnect the RF waveguide.

Unhook the four hooks (H1-H4) (HC AP/CC ODU).Lift the ODU, so as to free it from the hooks on the support, and remove it.

Figure 13 HC AP/CC ODU Disconnection

3.4.2 Procedure for HC AP ODU replacement To replace the ODU remove the ODU from the supporting framework fastened to the mast.

The procedure to follow is specified below (refer to Figure 14):

a) Power off the “SRA HighConnectivity” IDU b) Pull out the IF cable.c) Disconnect ground.d) Disconnect the RF waveguide.

Loosen and remove the ODU to the antenna using the four clamps (C1-C4).Lift the ODU, so as to free it from the hooks on the support, and remove it.

H1

H2

H3

H4



Figure 14 HC AP ODU Disconnection

C2C1

C3 C4

Flexi Hybrid Troubleshooting

Documents

supporting

trace identifier

demodulation

nokia siemens

minimum operational

receive protection

modem related

lower temperature