ceragon ip10 troubleshooting guide

FibeAir®

Troubleshooting Guide

Part ID: BM-0108-0 Doc ID: DOC-00015466 Rev a.02

September 2009

Notice This document contains information that is proprietary to Ceragon Networks Ltd.

No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd.

This document is provided as is, without warranty of any kind.

Registered TradeMarks Ceragon Networks® is a registered trademark of Ceragon Networks Ltd.

FibeAir® is a registered trademark of Ceragon Networks Ltd.

CeraView® is a registered trademark of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

TradeMarks CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are trademarks of Ceragon Networks Ltd.

Other names mentioned in this publication are owned by their respective holders.

Statement of Conditions The information contained in this document is subject to change without notice.

Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

Information to User Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment.

Copyright © 2009 by Ceragon Networks Ltd. All rights reserved.

Corporate Headquarters: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email: [email protected] www.ceragon.com

European Headquarters: Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email: [email protected]

North American Headquarters: Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email: [email protected]

APAC Headquarters: Ceragon Networks APAC (S'pore) Pte Ltd 100 Beach Road #27-01/03 Shaw Towers Singapore 189702 Tel.: 65 65724170 Fax: 65 65724199

Contents

General .......................................................................................................... 1

Maintenance Policy ........................................................................................... 1

Visual Inspection............................................................................................... 1

Troubleshooting Guide ................................................................................ 2

The Process....................................................................................................... 2

IDU LED Indicators............................................................................................ 3

Alarm List Table ...........................................................................................16

Fault Isolation using Loopbacks ................................................................39

Connection Fault Guide ..............................................................................40

FibeAir® Troubleshooting Guide 1

General Ceragon designed FibeAir to be highly reliable and relatively maintenance free. In the event of a system failure, the system will provide detailed indications to assist troubleshooting and fault isolation.

This guide explains the alarm indications of the FibeAir system, and contains procedures for troubleshooting and fault isolation.

Maintenance Policy To ensure simple and efficient system maintenance, the on-site technician will only replace IDU, ODU, or RFU modules, and not repair them. Under no circumstance will the technician be permitted to open the equipment in order to repair a module or circuit board. Opening equipment will terminate the Ceragon warranty.

Maintenance procedures the technician can perform include visual inspection, cleaning, cable/connector repair, link alignment/adjustment, and retorquing antenna mount bolts.

Visual Inspection The following table lists the suggested preventive maintenance procedures, which include visual inspection of the equipment and verification of operational parameters.

It is recommended to perform the procedures as often as local environmental conditions require. It is recommended to notify the end customer prior to performing any preventive maintenance procedures that could affect service on the circuit.

What to check Check for ... Comments

IDU alarm LEDs All green If not, perform troubleshooting

Coax cable connection Tight, no corrosion or moisture

Clean/repair as required

Coax cable No cracks or kinks Replace as required

All equipment Dust or dirt Clean as required

Receive level (voltage in IDU/ODU/RFU, or using management)

Per installation records

Align/adjust as required

Torque on antenna mount bolts

Tight mount Adjust as required


Troubleshooting Guide

The Process

Corrective maintenance consists of the steps described in the following sections. The steps provide a logical, sequential method for diagnosing and resolving system problems.

Step 1: Define the Symptom

This step is generally peformed by the customer's field technician or supervisor. Examples of symptoms include “IDU alarm is red”, “complete loss of service”, and “excessive errors”.

Symptoms may be constant or intermittent. Constant symptoms require immediate troubleshooting attention. Intermittent symptoms may require circuit monitoring or robust test procedures prior to troubleshooting.

Step 2: Isolate the Problem

After you have a clear definition of the symptom, the malfunction can be isolated using diagnostics, loopback testing, fault isolation tables/flow charts, test equipment, and manual procedures.

This step will identify the specific piece of equipment that is failing.

Although it may be difficult at times to immediately determine which part of a radio link is causing the fault, the initial suspicion should be focused on one of the following near-end or far-end issues:

Power supplies

Fading (due to heavy rain, new obstacle in path, antenna misalignment)

External equipment (SONET/SDH, ATM, Fast Ethernet, etc.)

Indoor Unit (IDU)

Outdoor Unit (ODU)or Radio Frequency Unit (RFU)

RF cable between the ODU/RFU and IDU

Exposure of equipment to severe conditions (high temperature, etc.)

System configuration

Step 3: Understand the Problem

Once the fault has been isolated, you will need to understand why the fault occurred and what is required to correct it. Use the tables provided in the following sections to understand the problem, and for suggestions of possible solutions.

Step 4: Solve the Problem

Use the troubleshooting information in this guide to help solve the problem.

IDU LED Indicators


The following tables list the LEDs on the IDU panel and their functions.

Note: In the tables below, critical and major alarms are red, and minor and warning alarms are yellow.

LED Indications for FibeAir IP-10 G-Series

LED Name Description Severity Color Info Probable Cause Corrective Action

PDH excessive-ber

E1/T1 excessive BER on port #%1 Major Red

Excessive BER alarm status

1) Line is not properly connected. 2) External equipment is faulty.

1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system.

PDH loopback-towards-line

E1/T1 loopback towards line on port #%1

Major Red Loopback towards line alarm status

User configured system to loopback mode.

Cancel loopback configuration.

PDH loopback-towards-radio

E1/T1 loopback towards radio on port #%1

Major Red Loopback towards radio alarm status

User configured system to loopback mode.

Cancel loopback configuration.

PDH loss-of-signal

E1/T1 loss of signal on port #%1

Major Red No signal is detected on port



PDH signal-degrade

E1/T1 signal degrade on port #%1

Minor Yellow

Signal degrade is detected on port



PDH unexpected-signal

E1/T1 unexpected signal on port #%1

Warning Yellow

Unexpected signal is detected on port

1) Port is disabled. 2) Line is connected to a disabled port.

1) Enable relevant port. 2) Disconnect cable from relevant port.

IDU ext-in-alarm %1 Warning Yellow External Alarm Input ---

IDU eth-loc-alarm

Ethernet loss of carrier on port #%1

Major Red Ethernet Loss of Carrier on Port #n

1) FE cable disconnected 2) Defected FE cable.

1) Check connection of FE cable. 2) Replace FE cable.

IDU eth-tx-mute-alarm

Ethernet Tx mute override on port #%1

Major Red Ethernet TX Mute Override

Radio LOF/EXBER/Link ID on local or remote side (in pipe application)

Check link


LED Indications for FibeAir IP-10 - Continued

LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action

IDU gbe-loc-alarm Gigabit ethernet loss of carrier on port #%1

Major Red Gigabit loss of carrier

1) Cable is not connected to the port. 2) Cable is defected.

1) Connect cable to the port. 2) Replace cable.

IDU gbe-sfp-alarm Gigabit ethernet SFP not inserted Major Red

Gigabit Ethernet SFP not intact

SFP is not inserted

1) Check SFP connector. 2) Replace fiber.

IDU gbe-sfp-tx-alarm Gigabit ethernet SFP Tx fault Major Red

Gigabit Ethernet SFP TX Fault

SFP malfunction Replace SFP

IDU gbe-tx-mute-alarm

GBE Tx mute override on port #%1

Warning YellowGBE TX Mute Override

Radio LOF/EXBER/Link ID on local or remote side

Check link

IDU file-load-error-alarm

Firmware file load error (%1) Critical Red

Firmware file was not successfully loaded

1) Firmware file is missing. 2) System error in power up.

1) Move Management to port 2. 2) Download firmware file. 3) Reset system.

IDU file-not-found-alarm

Firmware file not found (%1) Critical Red

Firmware file was not found

1) Firmware file is missing.

1) Download firmware file. 2) Reset system.

IDU alarms-file Alarm file not found Major Red

The system's alarm file was not found

The alarm file was deleted or is corrupted

Download alarm file

IDU entity-init-fail-alarm

SW error: entity initialization failure

Major Red SW failed to properly initialize

SW error during system intialization

Reset system

IDU extreme-temperature

IDU extreme temperature conditions

Warning Yellow

IDU is in extreme temperature condition

The external cooling/heating system is not operating.

Turn on external cooling/heating systems.

IDU fan-failure Fan failure Minor Yellow Fan failure Defective fan unit Replace fan unit

IDU general-hardware-failure

General HW failure %1 Major Red HW failure Defected HW 1) Reset system.

2) Replace IDU.

IDU kernel-backup Backup kernel is running Minor Yellow

Backup kernel is running

1) The kernel (/boot/uImage) is corrupted or missing

1) Re-install the SW.




IDU low-input-voltage Low input voltage Warning Yellow

Low input voltage detected

Low input to the system

1) Check power supply voltage.

IDU param-set-fail-alarm

SW error: parameter set failed

Warning Yellow Parameter set failure SW error Reset system

IDU corrupted-file-alarm

Inventory file (%1) is corrupted

Critical Red The inventory file is corrupted

1) Inventory file is missing. 2) Inventory file was found to be corrupt upon system power up.

1) Reset system. 2) Download inventory file

IDU file-not-found-alarm

Inventory file (%1) was not found

Critical Red Inventory file was not found

1) Inventory file is missing.

1) Download inventory file. 2) Reset system.

IDU demo-license-alarm Demo license Warning Yellow

Demo license is used by customer

1) Demo license activated by user.

1) Terminate demo license. 2) Activate operational license.

IDU license-violation-alarm

License violation %1 Warning Yellow License

violation

1) Unit does not match license features set.

1) Check that the code was entered correctly. 2) Call tech support for new license generation.

IDU firmware-file-missing-alarm

Modem firmware file not found Critical Red

Modem file was not found

1) Modem file is missing.

1) Download Modem file. 2) Reset system.

IDU firmware-load-error-alarm

Modem was not loaded successfully

Critical Red Modem was not loaded successfully

1) File is corrupt. 2) System failure.

1) Download file. 2) Reset system.

IDU fpga-file-currupt-alarm

Radio script (LUT) is corrupt Critical Red

Radio script LUT is not valid

1) Faulty file. 1) Download radio script LUT.

IDU fpga-file-not-found-alarm

Radio script (LUT) not found Critical Red

Radio script LUT not found

1) File was not downloaded to system.

1) Download radio script.




IDU incompatible-script-alarm

Incompatible script: %1 %2 Critical Red

Incompatibility between RFU and loaded radio script

1) Incompatibility between RFU and loaded radio script.

1) Change RFU. 2) Change Raido script.

IDU modem-script-file-corrupt-alarm

Radio script is corrupt Critical Red Radio script

is not valid File is corrupt Download file

IDU modem-script-file-not-found-alarm

Radio script not found Critical Red Radio script

not found File not found Download file

IDU mrmc-file-corrupt-alarm

MRMC file is corrupt Critical Red MRMC file

not valid File is corrupt Download file

IDU mrmc-file-not-found-alarm

MRMC file not found Critical Red MRMC file

not found File not found Download file

IDU rfu-file-corrupt-alarm

RFU file is corrupt Critical Red RFU file not

valid File is corrupt Download file

IDU rfu-file-not-found-alarm

RFU file not found Critical Red RFU file not

found File not found Download file

IDU if-loopback-alarm IF loopback Warning Yellow IF loopback initiated

1) User enabled IF loopback.

1) Disable IF loopback.

IDU lock-detect-alarm IF lock detection Critical Red IF synthesizer unlock

1) Extreme temperature condition. 2) HW failure.

1) Check installation. 2) Reset IDU.

IDU cable-open Cable open Major Red

Cable between IDU and RFU is not properly connected

1) Cable is not connected to IDU or RFU.

1) Check IF cable and connectors. 2) Verify that N-Type connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.

IDU cable-short Cable short Major Red There is a short in the IF cable

1) Physical short at the IF cable.

1) Check IF cable and connectors. 2) Verify that N-Type connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.




IDU cfm-failure Ethenet services failure Warning Yellow

Ethenet services failure

1) Local MEP error indication. 2) Remote MEP error indication. 3) Remote MEP loss of connectivity.

1) Check MAID definitions. 2) Check remote MEP definitions. 3) Check local MEP definitions. 4) Run "CFM traceroute" to the remote MEP then perform "CFM ping" to each MP (Maintenance Point) in order to find the broken point.

Protection cable-disconnected-alarm

Mate IDU cable is not connected Major Red

Protection cable is not properly connected

1) Cable is not connected between protection ports. 2) Cable is connected to wrong port. 3) Cable is damaged.

1) Connect Ethernet cable to protection port of both IDUs. 2) Replace cable.

Protection configuration-mismatch-alarm

Mate IDU configuration mismatch

Major Red

Mismatch between IDU in Protection mode

1) RFU properties are not identical. 2) Radio scripts are not identical.

1) Change RFU. 2) Download required radio script.

Protection force-switch-alarm

Protection force switch Warning Yellow

Force switch command was issued

1) User command - Force Protection Switch

1) Clear Force Switch Command.

Protection ipi-xml-file-alarm

Protection SW activity fault Warning Yellow

SW fault in Protection mechanism

1) SW fault in synchronization of databases

1) Reset Standby unit.

Protection lockout-alarm

Protection lockout Major Red

Protection Lockout command was isused

User issued Protection Lockout

Clear Lockout command




Protection mate-comm-failure-alarm

Mate IDU communication error

Major Red

IDU cannot communicate with its mate IDU

1) IDU IP addresses are identical. 2) IDUs IP subnet is not identical. 3) Protection Cable is not properly connected. 4) Protection Cable is damaged.

1) Check Protection cable connectivity. 2) Replace Protection cable.

Radio radio-excessive-ber

Radio excessive BER Major Red Excessive

BER on radio

1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU.

1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU.

Radio radio-link-id-mismatch

Link ID mismatch Critical Red

Link ID Mismatch Alarm

Link ID is not the same at both sides of link

Configure same Link ID for both sides of link.

Radio radio-lof Radio loss of frame Critical Red

Loss Of Frame on radio



Radio radio-signal-degrade

Radio signal degrade Minor Yellow

Signal Degrade on radio






Remote remote-communication-failure

Remote communication failure

Major Red

Remote Communication Failure Alarm

1) Fade in the link.

1) Check link performance.

RFU incompatible-rfu-tx-calibration

Incompatible RFU TX calibration

Major Red

RFU calibration tables require IDC SW upgrade

RFU calibration tables require IDC SW upgrade.

Upgrade IDU's SW.

RFU communication-failure

RFU communication failure

Warning Yellow

Failure in communication between IDU and RFU

1) Defected IF cable. 2) IF cable not connected properly. 3) Defected IDU. 4) Defected RFU.

1) Check IF cable and connectors. 2) Verify that N-Type connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU. For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU

RFU delay-calibration-failure-1

RFU delay calibration failure 1

Warning Yellow RX AGC is not locked Defective RFU

1) Reset the IDU / RFU. 2) Replace RFU.

RFU delay-calibration-failure-2

RFU delay calibration failure 2

Warning Yellow

Calibration cannot be completed due to notch detection

Calibration cannot be completed due to notch detection

Enter delay calibration value manually

RFU extreme-temp-cond

RFU extreme temperature Warning Yellow

RFU temperature is too high or low

1) Installation conditions. 2) Defective RFU.

1) Check installation conditions. 2) Verify operation as per product's specs. 3) Replace RFU.




RFU fan-failure RFU fan failure Warning Yellow RFU Fan Failure Alarm

1) Defective / non-existent fan drawer. 2) Defective RFU-to-fan drawer connection. 3) Defective RFU.

1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fan drawer 5)Replace RFU

RFU hardware-failure-1

RFU hardware failure 1 Critical Red

RFU Hardware Failure 1 Alarm

1) Defective RFU. 1) Replace RFU.

RFU hardware-failure-2

RFU hardware failure 2 Critical Red

RFU Hardware Failure 2 Alarm

1) Defective RFU. 1) Replace RFU.

RFU low-if-signal-to-rfu

Low IF signal to RFU Major Red

RFU is detecting low signal from IDU

1) IF cable connection. 2) Defective RFU. 3) Defective IDU.

1) Check IF cable connectors. 2) Verify that N-Type connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.

RFU no-signal-from-rfu No signal from RFU Major Red

IDU is not detecting a signal from the RFU

No RX (140 MHz) signal from RFU.

1) Check IF cable and connectors. 2) Verify that N-Type connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU. For High Power RF Unit: Check BMA connector center pin is not spliced both on RFU and on OCB.




RFU pa-extreme-temp-cond

RFU PA extreme temperature

Warning YellowRFU PA Extreme Temperature

1) Installation conditions. 2) Defective RFU.

1) Check installation conditions. 2) Replace RFU

RFU power-failure-12v RFU power failure (12v) Major Red

RFU Power Failure (12v) Alarm

1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.

1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.

RFU power-failure-1point5

RFU power failure (1.5v) Major Red

RFU Power Failure (1.5v) Alarm



RFU power-failure-24v RFU power failure (24v) Major Red

RFU Power Failure (24v) Alarm



RFU power-failure-6v RFU power failure (6v pro) Critical Red

RFU Power Failure (6v pro) Alarm



RFU power-failure-6v-sw

RFU power failure (6v SW) Major Red

RFU Power Failure (6v SW) Alarm



RFU power-failure-minus-5v

RFU power failure (-5v) Major Red

RFU Power Failure (6v pro) Alarm



RFU power-failure-vd RFU power failure (Vd) Critical Red

RFU Power Failure (Vd) Alarm



RFU rfu-loopback-active RFU loopback Major Red

RFU loopback Alarm

1) User action. 1) Disable RFU loopback.




RFU rfu-power-supply-failure

RFU power supply failure Major Red RFU power

supply failure

At least one of the PSU voltages is too low.

1) Replace RFU.

RFU rx-level-out-of-range

Rx level out of range Warning Yellow

RFU RX Level Out of Range

RSL is very low (typically below -80 dBm), link is down. For RFU-C: RSL is too Low (typically below -83dBm) or RSL is too High (typically above -26dBm).

1) Check antenna alignment & link planning. 2) Check link settings (TX power, TX freq). 3) Check antenna connections. 4) Replace local/remote RFU.

RFU rx-level-path1-out-of-range

RFU Rx level path1 out of range

Warning YellowRFU Rx Level Path1 Out of Range

1) Improper installation. 2) Fading event. 3) Defective RFU.

1) Check that the fault is not due to rain/multi-path fading or lack of LOS. 2) Check link settings (TX power, TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote RFU.

RFU rx-level-path2-out-of-range

RFU Rx level path2 out of range

Warning YellowRFU Rx Level Path2 Out of Range

1) Improper installation. 2) Fading event. 3) Defective RFU.

1) Check that the fault is not due to rain/multi path fading or lack of LOS. 2) Check link settings (TX power, TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote RFU.




RFU synthesizer-1-unlocked

Synthesizer 1 unlocked Major Red

RFU synthesizer is unlocked

1) Defective RFU. 2) Defective XPIC cable connection.

1) Replace XPIC cable. 2) Replace RFU.



RFU synthersizer is unlocked





RFU synthesizer is unlocked



RFU synthesizer-unlocked

Synthesizer unlocked Major Red

One of the RFU Synthesizers is Unlocked

One of the RFU synthesizers is unlocked.

1) Replace RFU. 2) In XPIC mode, replace mate RFU as well.

RFU tx-level-out-of-range

Tx level out of range Minor Yellow

RFU TX Level Out of Range

1) Defective RFU (the RFU cannot transmit the requested TX power)

1) Replace RFU. 2) Intermediate solution - reduce TX power.

RFU tx-mute Tx mute Warning Yellow RFU TX Mute RFU Transmitter muted by user.

Unmute the RFU transmitter.

RFU unknown-rfu-type IDU SW does not support this type of RFU

Major Red

IDC's SW doesn't support the RFU

IDC's SW doesn't support the RFU. Upgrade IDC SW.


LED Indications for other FibeAir Systems

Color

LED Red Yellow

Green Description

PWR (Power)

X X Red - power supply problem

LINE X X X Red - no input to main channel / high BER Yellow - JO mismatch

LOF (Loss of Frame)

X X Red - radio did not recognize information frame (radio link problem/radio LOF)

BER (Bit Error Ratio)

X X X Red - radio BER higher than radio excessive error threshold definition (see Sonet/SDH configuration window) Yellow - radio BER higher than radio signal degrade threshold definition (see Sonet/SDH configuration window)

LPBK (Loopback)

X X Red - loopback is active

STBY (Standby)

X X Yellow - Protected configuration. The unit is currently passive or Tx mute is operating

IDU X X X Red - modem unlocked Yellow - high temperature / fan problem

ODU X X X Red - no link, or ODU power, or ODU/RFU unlocked Yellow - radio interference, or high temperature, or Rx/Tx out of range

CBL (Cable) X X Red - RF cable open / RF cable short

RMT (Remote Unit)

X X X Red - no link / remote unit problem (red LED is lit in the remote unit)

Yellow - warning in remote unit (yellow LED is lit in the remote unit)


LED Indications for Hitless Systems

For Hitless systems, the following table lists the LEDs and their indications:

LOF (LED Panel) - LOF

LED Color Alarm Explanation

Yellow Local unit receives LOF from a receive path currently not in use.

Red Local unit receives LOF from a receive path currently in use.

LOF (Interface Panel) - ALRM


OFF Hitless mode is disabled.

Red Local unit receives LOF from the mate unit.

Green Hitless switching can be performed, if necessary.

Local Receiver (Interface Panel) - Rx ACTV


OFF Local receiver not in use.

Green Local receiver in use.


Alarm List Table The table below lists trap IDs, trap descriptions, probable causes, and corrective actions.

A note about interface troubleshooting:

If, after the radio link is installed, the payload is not received, there may be a problem either with the line interface connection to FibeAir, or with external equipment.

Before you perform line interface troubleshooting, check the following items, which are common causes of line interface failures:

External equipment Tx is connected to FibeAir Rx.

External equipment Rx is connected to FibeAir Tx.

Both external equipment and FibeAir are using the same interface (single mode, multi-mode).

For multi-mode interfaces, check that you are using multi-mode fibers to connect the unit. For single mode interfaces, check that you are using single mode fibers.

If no problem is detected with any of the items above, proceed with the table below.

Alarm List with Corrective Actions

Trap ID Description Probable Cause Corrective Actions

0 Insufficient System Configuration for Full XPIC Support

One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.

1) Check the Block Radio command status on the protection configuration. 2) Check the remote radio alarms and solve the radio fault accordingly

10 ODU 5/8/12/-12V Power Supply Failure



11 Synthesizer #1/2/3 Unlocked

One of the RFU synthisizers is unlocked.

Replace RFU. For non RFU-C radios: In XPIC configuration, it might be that the RFU is taking the synch from the mate RFU. In this case, check if alarm persists in non-XPIC configuration.

12 Tx Mute On/Off RFU transmitter muted by user Unmute the RFU transmitter.

12 Tx Level Out of Range The RFU cannot transmit the requested Tx power.

1) Replace RFU. 2) Intermediate solution - reduce TX power.



13 Rx Level Out of Range

RSL is very low (typically below -80 dBm), link is down.For RFU-C: RSL is too Low (typically below -83dBm) or RSL is too High (typically above -26dBm).

1) Check antennas alignment & link planning. 2) Check link settings (TX power,TX freq). 3) Check antenna connections. 4) Replace local/remote RFU.

14 ODU Temperature Out of Range

RFU temperature too high/low.

1) Check installation conditions. 2) Replace RFU.

15 XPIC Cable Swap

Left/Right cables swap in XPIC configuration. If ???Drawer ID Mismatch??? (see above) alarm is identified in both drawers, the IF (coax) cables between the drawers and ODUs on one end are swapped.

1) Verify correct cable connection. Recommended connection is V to Right drawer and H to Left drawer

15 Power Input #2 is Down Subrack redundant power feed failure.

1) Verify if the Power Input card exists in the subrack. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack. 4) Replace Power Input card if problem still exists. 5) Disable Power Input

15 Power Input #1 is Down Subrack redundant power feed failure.

1) Verify if the Power Input card exists in the subrack. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack. 4) Replace Power Input card if problem still exists. 5) Disable Power Input

15 IDU 5/8/3.3/-5V Power Supply Failure

Failure in an IDU power supply.

1) Check -48 VDC supply to the IDU. 2) Replace IDU.

15 Drawer Power On/Off Drawer power on/off.

15 Drawer Internal Power Failure (Board #2)

Board #1 - MUX card. Board #2 - Modem card. This alarm may also be generated if a drawer in Internal Protection was switched off.

1) Switch off/on IDM. 2) Replace IDM.

15 Drawer Internal Power Failure (Board #1)

Drawer Internal Power Failure (Board #1)

16 Extension Link Communication Failure

Problem with extension cable or the connection between the two subracks.

1) If extended mode is not in use, configure all IDCs in the subrack as "1 subrack out of 1". 2) If extended mode is in use, verify that the other subrack is configured to extension mode properly. 3) Check that the XC boards in both subracks are



16 Cable Short IDM-RFU cable short.

1) Check IF cable and connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.

16 Cable Open/Short IDU-ODU cable open/short.

1) Check IF cable and connectors. 2) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 3) Replace IDU. 4) Replace ODU.

16 Cable Open IDM-RFU cable open.

1) Check IF cable and connectors. 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.

17 MRMC=???value??? Script File is Missing

Multi-Rate Multi-Constellation configuration script for the specified capacity/modulation is missing in the IDC.

1) Download the Modem script to the IDC and reset the IDM.

17 Drawer Internal Hardware Intact/Failure Board#1

Drawer hardware intact ok / failure (Mux) 1) In case of failure, replace IDM.

18 IDU Temperature Out of Range

IDU Temperature Out of Range

1) Check installation conditions. 2) Replace IDM.

18 Fan Failure Fan Failure 1) Replace fan.

19 XC Internal Loopback on Line #5

XC board Internal port loopback 1) Disable loopback









19 Wayside Channel Loopback

Wayside Line loopback applied by user in internal protection

Disable Wayside line loopback

19 Wayside Channel Loopback

Wayside Left Line loopback applied by user Disable Wayside line loopback

19 ODU Internal Loopback (Not) Active

RFU loopback applied by user Disable loopback

19 Internal Loopback on Fiber #n Internal loopback on Fiber Disable loopback

19

IDU Remote Loopback (Not) Active ?10;IDU Line Loopback (Not) Active?10;E1\T1\E3\DS3 #n Internal Loopback (Not) Active?10;E1\T1\ E3\DS3 #n External Loopback (Not) Active

Loopback applied by user Disable loopback

19 IDU Local Loopback (Not) Active

IDU IF loopback applied by user Disable loopback



19 Gigabit Ethernet Internal Loopback

Gigabit Ethernet Internal Loopback applied by user.

Disable Gigabit Ethernet Internal Loopback

19 External Loopback on Fiber #n

IDU Line loopback applied by user 1) Disable loopback

19 E1\T1 Internal Loopback on Port #n

IDU Line loopback applied by user 1) Disable loopback

19 E1\T1 External Loopback on Port #n E1/T1 External loopback 1) Disable loopback

20 Remote Communication Failure

No communication between the IDUs over the link.

1) Verify link is up and no errors over the link. 2) Check in-band management configuration.

21 PRBS Test is Running on Radio PRBS test started. Disable PRBS test.

21 Link Group #1 N+1 Protection Fault: Locked by User

Lockout or Force Switch to Protecting Link Group maintenance command activated.

Release maintenance command.

22 Trib RS: LOF Trib RS: LOF

22 Radio RS: LOF (SDH) Radio Section: LOF (Sonet)

Loss Of Frame alarm on the radio, link is down

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power, TX freq). 3) Verify no interference. 4) Use loopbacks to identify source.5) Replace IDMs/ODUs

22 Radio RS: LOF Radio RS: LOF (ADM)

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power, TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs.

22 Link Group #1 N+1 Protection Fault: Protecting Radio Failure

N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board.

1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH)

22 Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet)

Loss Of Frame alarm on the line input.

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM.

22 Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet)

Loss Of Frame alarm on the line input

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU.



22 Fiber RS: LOF Fiber RS: LOF (ADM)

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs

23 Trib RS: LOS Trib RS: LOS

23 Loss of Signal on Fiber #n

Loss Of Signal alarm on the line input

1) Check line input. 2) Check fibers/cables. 3) Verify that end equipment transmits properly. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM.

23 Gigabit Ethernet Loss of Signal

Gigabit Ethernet Loss of Signal

1) Check line input. 2) Check fiber. 3) Verify end equipment transmits properly. 4) Replace IDM.

23

Fiber RS: LOS or?10;E1\T1\E3\DS3 #n Loss of Signal?10;Fiber RS: LOS

Loss Of Signal alarm on the line input


23 Fast Ethernet Loss of Carrier on Port #n Fast Ethernet Loss of Carrier

1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDM.

23 Fast Eth. #01/02 Loss of Carrier Fast Ethernet Loss of Carrier

1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDU.

23 E1\T1 Loss of Signal on Port #n E1\T1 Loss of Signal


24 Trib RS: TIM Trib RS: TIM 24 Trib LP #n: TIM Trib LP #n: TIM 24 Trib HP: TIM Trib HP: TIM

24 Trace Identifier Mismatch on Fiber #n

Trace Identifier Mismatch alarm (J0 mismatch).

Verify J0 settings in the IDU and in the end equipment.

24 Radio LP #n: TIM Radio LP: TIM 24 Radio HP: TIM Radio HP: TIM 24 Fiber RS: TIM Fiber RS: TIM 24 Fiber RS: TIM Fiber RS: TIM 24 Fiber RS: TIM Fiber RS: TIM


Trap ID Description Probable Cause Corrective Actions 24 Fiber LP #n: TIM Fiber LP #n: TIM 24 Fiber HP: TIM Fiber HP: TIM 25 Trib RS: Excessive BER Trib RS: Excessive BER 25 Trib MS: Excessive BER Trib MS: Excessive BER

25 Trib LP #n Excessive BER Trib LP #n Excessive BER

25 Trib HP: Excessive BER Trib HP: Excessive BER

25 Radio RS: Excessive BER

Radio RS: Excessive BER (Regenerator)


Radio RS: Excessive BER (Regenerator)


Radio RS: Excessive BER (ADM)

25 Radio MS: Excessive BER Radio MS: Excessive BER

25 Radio LP #n: Excessive BER Radio LP: Excessive BER

25 Radio HP: Excessive BER Radio HP: Excessive BER

25 Fiber RS: Excessive BER

Fiber RS: Excessive BER (Regenerator)


Fiber RS: Excessive BER (Regenerator)


Fiber RS: Excessive BER (ADM)

25 Fiber MS: Excessive BER Fiber MS: Excessive BER

25 Fiber LP #n Excessive BER Fiber LP #n Excessive BER

25 Fiber HP: Excessive BER Fiber HP: Excessive BER

25 Excessive BER on Radio #n

Major radio Excessive BER alarm

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

25 Excessive BER on Fiber #n

Major line Excessive BER alarm


25 E1\T1\E3\DS3 #n Excessive BER E3/DS3 Excessive BER

25 E1\T1\E3\DS3 #n Excessive BER E1/T1 Excessive BER



25 E1\T1 Excessive BER on Port #n

Major Excessive BER alarm on E1/T1 port

1) Check line input. 2) Check cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDM is ok. 5) Replace IDM.

26 Trib RS: Signal Degrade Trib RS: Signal Degrade 26 Trib MS: Signal Degrade Trib MS: Signal Degrade

26 Trib LP #n Signal Degrade Trib LP #n Signal Degrade

26 Trib HP: Signal Degrade Trib HP: Signal Degrade

26 Signal Degrade on Radio #n Minor radio BER alarm


26 Signal Degrade on Fiber #n Minor line SD BER alarm

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM.

26 Radio RS: Signal Degrade Radio RS: Signal Degrade



26 Radio MS: Signal Degrade Radio HP: Unequipped

26 Radio LP #n: Signal Degrade Radio LP #n: Signal Degrade

26 Radio HP: Signal Degrade Radio HP: Signal Degrade

26 Fiber RS: Signal Degrade

Fiber RS: Signal Degrade (ADM)

26 Fiber RS: Signal Degrade Fiber RS: Signal Degrade

26 Fiber RS: Signal Degrade Minor line BER alarm


26 Fiber MS: Signal Degrade Fiber MS: Signal Degrade

26 Fiber LP #n Signal Degrade Fiber LP #n Signal Degrade

26 Fiber HP: Signal Degrade Fiber HP: Signal Degrade



26 E1\T1\E3\DS3 #n Signal Degrade E3DS3 Signal Degrade

26 E1\T1\E3\DS3 #n Signal Degrade E3DS3 Signal Degrade

26 E1\T1 Signal Degrade on Port #n

Minor BER alarm on E1/T1 port

1) Check line input. 2) Check cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDM is ok. 5) Replace IDM.

27 Trib MS: AIS Trib MS: AIS 27 Trib LP #n: AIS Trib LP #n: AIS 27 Trib HP: AIS Trib HP: AIS 27 Radio MS: AIS Radio MS: AIS 27 Radio LP #n: AIS Radio LP #n: AIS 27 Radio HP: AIS Radio HP: AIS 27 Fiber MS: AIS Fiber MS: AIS 27 Fiber LP #n: AIS Fiber LP #n: AIS 27 Fiber HP: AIS Fiber HP: AIS

28 Trib RS: Unexpected Signal Trib RS: Excessive BER

28 Gigabit Ethernet Unexpected Signal

GbE port is disabled but GbE data is detected.

1) Enable GbE port, disable GbE port of the source, or disconnect the fiber

28 Fiber RS: Unexpected ?10;E1\T1\E3\DS3 #n Unexpected Signal

Unexpected signal on the line input. Port disabled but line is connected.

1) Enable line port or disconnect line

28 Fast Ethernet Unexpected Signal on Port #n

Fast Ethernet Unexpected Signal on Port #n

30 Trib LP #n: LOP Trib LP #n: LOP 30 Trib HP: LOP Trib HP: LOP

30 Radio LP #n: LOP Radio LP: Loss of pointer (LOP) alarm occurs.

30 Radio HP: LOP Radio HP: Loss of pointer (LOP) alarm occurs.

30 Fiber LP #n: LOP Fiber LP: Loss of pointer (LOP) alarm occurs.

30 Fiber HP: LOP Fiber HP: Loss of pointer (LOP) alarm occurs.

31 Trib MS: RDI Trib MS: RDI 31 Trib LP #n: RDI Trib LP #n: RDI 31 Trib HP: RDI Trib HP: RDI

31 Radio MS: RDI Radio MS: Remote Defect Identifier signal (RDI) occurs.

31 Radio LP #n: RDI Radio LP: Remote Defect Identifier signal (RDI) occurs.

31 Radio HP: RDI Radio HP: Remote Defect Identifier signal (RDI) occurs.

31 Fiber MS: RDI Fiber MS: Remote Defect Identifier signal (RDI) occurs.



31 Fiber LP #n: RDI Fiber LP: Remote Defect Identifier signal (RDI) occurs.

31 Fiber HP: RDI Fiber HP: Remote Defect Identifier signal (RDI) occurs.

32 Trib LP #n: PLM Trib LP #n: PLM 32 Trib HP: PLM Trib HP: PLM

32 Radio LP #n: PLM Radio LP: Payload Label Mismatch (PLM) occurs.

32 Radio HP: PLM Radio HP: Payload Label Mismatch (PLM) occurs.

32 Fiber LP #n: PLM Fiber LP: Payload Label Mismatch (PLM) occurs.

32 Fiber HP: PLM Fiber HP: Payload Label Mismatch (PLM) occurs.

33 Trib LP #n: Unequipped Trib LP #n: Unequipped 33 Trib HP: Unequipped Trib HP: Unequipped

33 Radio LP #n: Unequipped Radio LP: Unequipped

33 Radio HP: Unequipped Radio HP: Unequipped

33 Fiber LP #n: Unequipped Fiber LP: Unequipped

33 Fiber HP: Unequipped Fiber HP: Unequipped

34 External Alarm External alarm input #1 configured and triggered by user.










42 XPIC Cable Swap

Internal IDC to IDC communication failure between modules requied for Link Group protection service.

1) Check that IDC #n is power up and finished initialization. 2) Check & configure both IDCs with proper system configuration: System Type, Subrack#, Subrack IP Base Address, Link Group Topology. 3) Check for Hardware fault: Subrack Auxiliary module

42 XC <Type> FPGA File is Missing

XC firmware file is missing in the 2-floor IDC.

1) Download XC firmware file of the required type and reset the IDC.

42 Wayside Firmware File is Missing

Wayside firmware file is missing in the IDC.

1) Download Wayside firmware file to the IDC and reset the IDC.

42 Subrack Auxiliary FPGA File is Missing

Subrack Auxiliary firmware file is missing in the 2-floor IDC.

1) Download Subrack Auxiliary firmware file and reset the IDC.

42 Secondary Clock Source Failure

Secondary Clock Source Failure

42 Radio Card #n Powered Down

Radio module pertained to Link Protection group is powered down or extracted.

1) Check if Radio module is inserted properly in the subrack and is powered on. Replace module if faulty.

42 Primary Clock Source Failure Primary Clock Source Failure

42 MUX Firmware File is Missing

A Mux FW file is missing from the system.

Load the required FW file, and reset system.

42 Modem Firmware File is Missing

A Modem FW file is missing from the system.

Load the required FW file, and reset system.

42

Link Group #1 N+1 Protection Fault: XC Peer Communication Failure

N+1 Link Group protection degraded due to peer XC communication fault.

1) Verify Protection Radio link is up and, no errors over the link. 2) Check that remote IDU is properly configured for N+1 Link Group protection. 3) Check that remote IDU has properly operational XC board. 4) Check that Protection Radio link terminates

42

Link Group #1 N+1 Protection Fault: Protecting Radio Failure XC Card Fault

N+1 Link Group protection degraded due to XC card fault.

1) Check if XC module is powered on and no other alarm related to XC is active. 2) Replace XC module.

42

Link Group #1 N+1 Protection Fault: Local-Remote Protection Mismatch

N+1 Link Group protection degraded due to Local-Remote Protection Mismatch.

1) Check that remote IDU is properly configured with N+1 Link Group topology. 2) Check that remote IDU has all N+1 Link Group protection related line modules operational.



42 Line Card #n Powered Down

Line module pertained to Link Protection group is powered down or extracted.

1) Check if the card is inserted properly in the subrack. 2) Check if own or redundant power supply / Radio module (in drawer #1) is powered on. Replace module if faulty.

42 Line Card #1 Powered Down

Line module in carrrier #1 of the Link Protection group is powered down or extracted.

1) Check if the card is inserted properly in the subrack. 2) Check if own or redundant power supply / Radio module is powered on. 3) Replace module if faulty.

42 License Fault

The MRMC loaded to the system is not supported by the license, or the ACM function is enabled while not supported by the license. The link is not operative.

Load another MRMC with bit rate supported by the license

42 IDU-ODU Inner Communication Failure

IDC cannot communicate with ODC card.

1) Check ODU connection to the IDU. 2) Check IF cable and connectors. 3) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 4) Replace ODU. 5) Replace IDU.

42 IDU-MUX Inner Communication Failure

IDC cannot communicate with MUX card, MUX card upload failure.

1) Reset IDU. 2) Verify correct SW version. 3) Verify correct interfaces. 4) Replace IDU.

42 General Hardware Fault #9

Upper IDM Board (MUX or XC) EEPROM inventory information CRC error

1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module.


Upper IDM Board (MUX or XC) EEPROM read access error



FPGA load failure - Subrack Auxiliary board.

1) Download correct Subrack Auxiliary FW file to 2-floor IDC, and then extract and re-insert Subrack Auxiliary board 2) Replace Subrack Auxiliary module. 3) Replace 2-floor IDC.

42 General Hardware Fault #7 FPGA load failure - Modem

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

42 General Hardware Fault #6 FPGA load failure - Mux




42 General Hardware Fault #5 DAC failure


42 General Hardware Fault #4 IDU XPIC HW fault


42 General Hardware Fault #3 XO failure - Mux board


42 General Hardware Fault #2 XO failure - Modem board



Wrong card type detected in Subrack Auxiliary slot.

1) Replace Subrack Auxiliary module.


Lower IDM Board (Modem or XC) EEPROM inventory information CRC error



Subrack Auxiliary EEPROM checksum failure.

1) Extract and re-insert Subrack Auxiliary module. 2) Replace Subrack Auxiliary module.


Lower IDM Board (Modem or XC) EEPROM read access error


42 General Hardware Fault #1 IDU Synthesizer lock

1) Download correct SW/FW/Configuration scripts. 2) Power IDM off/on. 3) Replace IDM. 3) Replace IDC.

42 EOW chaining Loss of Signal

No signal detected on Subrack Auxiliary EOW chaining input.

1) Disable EOW chaining if not required. 2) Check EOW chaining line input on both subracks. 3) Check / fix EOW chaining configuration on mate subrack. Verify that EOW is defined on at least one working link on mate subrack. 4) Replace EOW chaining



42 Drawer-RFU Communication Failure

No communication between IDM and RFU.

1) Check IF cable and connectors. 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU

42 Drawer Internal Power Failure (Board #2) Internal Power failure.

1) Check that proper Subrack Auxiliary module inserted. 2) Extract and re-insert Subrack Auxiliary module. 3) Replace Subrack Auxiliary module.

42 Drawer Internal Loopback IDU IF loop applied by user 1) Disable loopback

42 Copy IDC Configuration to Mate

IDC copy configuration by user in external protection

42 Copy Carrier Configuration To Mate Failed/Succedded

Carrier configuration copied between two IDMs in protected configuration

42 Clock Unit Unlocked Clock Unit Unlocked 42 Clock Unit Out of Range Clock Unit Out of Range

42 Auxiliary Card Fault #01 Subrack Auxiliary module failed or extracted.

1) Check Subrack Auxiliary module is properly inserted. 2) Replace Subrack Auxiliary module.

42 ACM Configuration File is Missing

The ACM lookup table file cannot be found on the system disk.

Load the lookup table file of the relevant release version or load the SFD file.

43

TFTP IDU/MUX/ODU verxxx Download Succeeded/ Canceled/Failed

Software download operation status (from user's PC to IDC)

43

IDU Configuration Download Succeeded/Error/Cancelled/Failed/Invalid File

Configuration download status, initiated by user

43

Boot/IDC/MUX/ODU/Modem Script/Modem/ Wayside/Mrmc table/RFU FPGA File Download Succeeded <file name>

File download status. Initiated by user.

44 RFU FW Upload Failed Firmware upload operation status (from IDC to ODC)

44 RFU FW Upload Error Firmware upload operation status (from IDC to ODC)

44 RFU FW Upload Canceled

Firmware upload operation status (from IDC to ODC)

44 ODU SW Upload Failed Software upload operation status (from IDC to ODC)



44 ODU SW Upload Error Software upload operation status (from IDC to ODC)

44 ODU SW Upload Canceled

Software upload operation status (from IDC to ODC)

44 MUX/ODU Internal Download Succeeded/ Canceled/Failed/Error

MUX/ODU Internal Download Succeeded/Canceled/Failed/Error

46 User Configuration Mismatch between IDC # and IDC #

At least one configuration parameter which should be equal in these two IDCs has different values.

1) Check the mismatch configuration in the alarms log. 2) Configure the relevant IDC with the correct values for mismatch resolution, and wait one minute for the mismatch alarm to clear.

46 User Configuration Mismatch (<param name>) S=xx, D=xx

Configuration in the IDC is different than in the drawers or Auxiliary channel board

1) Check and compare configuration 2) See User Configuration Mismatch Alarm

46 User Configuration Mismatch (<param name>) S=xx, D=xx

Mismatch configuration between the IDC Database and the drawer.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.

46 User Configuration Mismatch

At least one Link Group configuration parameter in the IDC Database is different than the actual configuration in the XC. Raised only after IDC hotswap or S/W reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.


At least one drawer configuration parameter in the IDC Database is different than the actual configuration in the drawers. Raised only after IDC hotswap or S/W reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from the drawer to the IDC, or "Copy to Drawer", eliminating the mismatch. However, "copy to drawer" command does not copy the protec


At least one IDC configuration parameter in the IDC Data Base (XPIC for example) is different than the configuration in the drawers or Auxiliary channels. Raised only after IDC hotswap / software reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy drawer to IDC" command to copy the XPIC/protection configuration from the drawer to the IDC (without reset). This will end the mismatch.

46 Protection Mismatch Internal system mismatch regarding the state of the radio - Mute/Unmute

Reset IDM

46 Mate Configuration Mismatch (<param name>) M=xx, L=xx

Mismatch in the internal protection configuration between the drawers.

1) Check and compare configuration 2) See mate Configuration Mismatch Alarm



46 Mate Configuration Mismatch (<param name>) M=xx, L=xx

Mismatch configuration between local IDC Database and mate IDC database

1) Check and compare configuration 2) See mate Configuration Mismatch Alarm

46 Mate Configuration Mismatch

Configuartion mismatch between two IDCs in External Protection configuration.

1) Check and compare configuration. 2) Perform "copy to mate" from the IDC with the correct configuration

46 Mate Configuration Mismatch

Configuartion mismatch between two drawers in External Protection configuration.

1) Check and compare configuration. 2) Perform "copy to mate" from the drawer with the correct configuration

46 Link ID Mismatch on Radio #n

Link ID is not identical on both ends of the link.

Set identical Link ID on both ends of the link.

46 Link ID Mismatch Link ID Mismatch

46 Link ID Mismatch Link ID is not identical on both ends of the link.

1) Set identical Link ID on both ends of the link.

46 Link ID Mismatch Link ID is not identical on both ends of the link.

1) Set identical Link ID on both ends of the link.

46 IDU Hitless Remote Config Mismatch

Different configuration between the IDUs on both sides of the link

1) Check and compare configurations

46 IDU Hitless Mate Config Mismatch

Different configuration between the IDUs on the same side of the link

1) Check and compare configurations


IDC MAC device failure - loading with default MAC address

1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.


WSC board configuration failure - Can't detect board configuration (can't read from E2PROM)



WSC board configuration failure - Error during reading board configuration - CRC error



FPGA load failure - Wayside Channel


46 General Cfg Mismatch Settings not supported by HW/SW.

1) Check if HW and SW support the requested configuration

46 Drawer ID Mismatch in Protecting Carrier

Drawer #1 receives signal of the mate drawer (#2) across the XPIC link. Problem in the XPIC link (such as failure in one of the transmitters or insufficient XPI), detected by the XC board.

1) Check link connections and settings. 2) Check XPIC configuration. 3) Verify that both links are up. 4) Check XPI

46 Drawer ID Mismatch

Drawer receives signal of the other drawer across the XPIC link. Indicates problem in the XPIC link (such as failure in one of the transmitters or insufficient XPI)

1) Check link connections and settings. 2) Check XPIC configuration. 3) Verify that both links are up. 4) Check XPI



46 Device Incompatible Alarm (#103)

Incomapitibility alarm between link components. Typically refers to mixture of standard and "I" components in the link

1) Check link components

46 Auxiliary Channel User Configuration Mismatch

Incorrect Auxiliary channel configuration

1) Check and correct configuration: Use "Copy IDC to AUX" to copy the Auxiliary channel configuration to the IDC, or "Copy AUX to IDC" to copy the Auxiliary channel configuration to the AUX

47

SW Mode Changed to Slave/Master?10;Change Remote Transmitter Request Sent

Change Master/Slave command

47 Protection Internal/External Mate Not Exist

System configured for protection without mate connected

1) Check configuration. 2) Check Mate connected

47 Protection External Alarm Switch

Protection switch by external alarm

47 Protection Change to Standby

Different faults indicate hardware failure on the drawer


47 Hitless Protection Configuration Mismatch

Hitless is configred without protection

1) Enable protection or disable hitless

47

Change Remote Transmitter Request Sent - SDBER/EXBER/LOF/BER

Command was sent to remote end to switch when both local receivers identify Rx fault (for example, remote active transmitter fails)

48 Protection Communication Error on Cable

For External Protection configuration. Protection cable is connected but errors detected.

1) Check that cable is connected properly. 2) Replace protection cable. 3) Replace IDCs

48 Protection Cable Disconnected

Protection Cable Disconnected

1) Connect Protection Cable. 2) Replace cable.

48

Protection Cable Disconnect/Error/Power Error/Problem?10;Master-Slave Disconnect

Problem with protection cable or the connection between the Master/Slave IDUs

1) Replace cable. 2) Replace IDUs

49 Heart Beat (Trap Only) Heart Beat (Trap Only) 50 Trib HP: LOM Trib HP: LOM

50 Radio HP: LOM Radio HP: Loss of Multi-frame (LOM) alarm occurs.

50 Fiber HP: LOM Fiber HP: Loss of Multi-frame (LOM) alarm occurs.

51 Hitless Switch Locked to Self Radio By User

Hitless Switch Locked to Self Radio by User

51 Hitless Switch Locked to Right Radio By User

Hitless switching disabled by user and locked for one of the drawers.

1) Disable Hitless Lockout



51 Hitless Switch Locked to Mate/Self Radio By User

Hitless Switch Locked to Mate/Self Radio by User

51 Hitless Switch Locked to Left Radio By User

Hitless switching disabled by user and locked for one of the drawers.

1) Disable Hitless Lockout

51 Hitless Self/Mate Receiver in user

Hitless Self/Mate Receiver in user

51 Hitless Left/Right Receiver in Use

Left/Right receiver is used for processing data

Not a real alarm since receiver switching is likely to happen during multipath fading.

51 Hitless Functionality Failure

Hitless protection is not available. The link will fail in case of fade.

1) Hitless cable disconnected. 2) Mate IDU is off. 3) Mate IDU has an alarm that prevents it from receiving data.

52 Unused Radio Receiver LOF

Hitless Self Radio Receiver LOF


52 Own Radio BBLOF on Radio #n



52 Loss of Frame on Unused Left/Right Radio

Permanent Radio LOF in the receiver (raised after 10 consecutive seconds of radio Loss Of Frame). Implies a permanent problem, unlike fading due to multipath condition, which is intermittent in nature.

Same as Radio LOF alarm: 1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

52 Hitless Self Radio Receiver LOF


53 Hitless Cable Disconnect Hitless cable disconnected. Connect hitless cable.

57

In-Band Radio PPP Link Disconnect?10;In-Band Line PPP Link Disconnect

In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected.

1) Check the line connection. 2) Check in-band configuration.

58 Wayside Channel Loss of Signal/Carrier

Wayside Channel Loss of Signal/Carrier in internal protection

1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.




Wayside Right Channel Loss of Signal/Carrier



Wayside Left Channel Loss of Signal/Carrier


58 User Channel Ethernet Loss of Carrier

User Channel Loss of Carrier in internal protection

1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.


User Right Channel Loss of Carrier



User Left Channel Loss of Carrier


59 ODU-2-ODU Cable Open ODU-2-ODU Cable Open 1) Check cable.

2) Replace cable.

60 No Signal from ODU No Rx (140 MHz) signal from RFU

1) Check IF cable and connectors 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. For High Power RF Unit: Check BMA connector center pin is not spliced both on RFU and on OCB.

60 Modem Script Not Supported

No modem script is available for this RFU.

1) Upgrade MRMC scripts 2) Replace RFU



61 Protection Lockout

"Protection Lockout" command executed. Will lock the switching operation until removed.

1) Disable Lockout

61 Protection Force Switch


1) Disable "Force Switch"

62 RFU Power Supply Failure

At least one of the PSU voltages is too low. Replace RFU.

62 RFU Power Failure (Vd) RFU Power Supply Failure (Vd)

1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM.

62 RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)


62 RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)


62 RFU Power Failure (12v)

RFU Power Supply Failure (12v)


62 RFU Power Failure (1.5v) RFU Power Failure (1.5v)


63 RFU Rx Level Path2 Out Of Range

RSL of Diversity channel is very low (typically below -80 dBm).

1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU.

63 RFU Rx Level Path1 Out Of Range

RSL of Main channel is very low (typically below -80 dBm).

1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU.

64 RFU Extreme Temperature

RFU temperature is too high/low.

1) Check installation conditions. 2) Verify operation as per product's specs. 3) Replace RFU

65 RFU Fan Failure Fan Failure was detected by RFU

1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fans drawer


Trap ID Description Probable Cause Corrective Actions 5) Replace RFU

65 RFU Fan Failure Fan Failure was detected by RFU

1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fans drawer 5) Replace RFU

66 RFU Low Signal To ODU

RFU is detecting low signal from IDU

1) Check IF cable connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.

67 RFU XPIC Clock Failure No XPIC clock is received from Master RFU

1) Reconnect XPIC clock cables at both RFUs 2) Replace XPIC cable

68 RFU Delay Calibration Failure 1

Delay calibration is unseccessfull since RX AGC is unlocked.

1) Check link performance 2) Re-perform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU

69 RFU Delay Calibration Failure 2

Delay calibration is unseccessfull since wide or deep notch has been detected at the RX signal

1) Check link performance 2) Reperform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU

70 Gigabit Ethernet TX Mute Override

GbE port is enabled by the user but the system overrides this and mutes the port. This alarm may appear in the following cases: Radio LOF (local or remote), Link ID mismatch (local or remote), excessive BER (local or remote), Signal degrade (local or re

1) Check the reason for the alarm (see the Probable Cause column) and correct it accordingly.

70 Gigabit Ethernet SFP TX Fault

SFP does not transmit Ethernet properly.

1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM.

70 Gigabit Ethernet SFP Not Intact

SFP is not connected properly.

1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM.

71 Encryption Fault HW encryption fault 1) Reset IDM.

72 Encryption Sync Loss Encryption loss of frame 1) Check link staus. 2) Reset IDM.



73 Initial KEP Failed The first encryption key exchange failed

1) Check link status. 2) Reset IDC. 3) Reset IDM.

74 Session Key Timer Elapsed

No session key exchange in the allowed time 1)Check link status.

75 Power-Up Test Failed One of the built-in encryption system tests failed

1) Reset IDC. 2) Reset IDM.

76 Conditional Test Failed One of the Conditional tests failed

1) Reset IDC. 2) Reset IDM.

77 Encryption Will Turned Off On Next Reset

Encryption mode changed by user, will take effect after next power up.

80 Admin password in default state

Administrator password is the default value Change administrator password.

81

Link Group #1 N+1 Protection Fault: XC Peer Communication Failure

N+1 Link Group protection degraded due to peer XC communication fault.

1) Verify Protection Radio link is up and, no errors over the link. 2) Check that remote IDU is properly configured for N+1 Link Group protection. 3) Check that remote IDU has properly operational XC board. 4) Check that Protection Radio link termin

81 Link Group #1 N+1 Protection Fault: XC Card is Down

N+1 Link Group protection degraded due to XC card fault.

1) Check if XC module is inserted and powered on and no other alarm pertained to XC is active. 2) Replace XC module.

81 Link Group #1 N+1 Protection Fault: Protecting Radio Failure

N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board.

1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH)

81 Link Group #1 N+1 Protection Fault: Locked by User

Lockout or Force Switch to Protecting Link Group maintenance command activated.

Release maintenance command.

81

Link Group #1 N+1 Protection Fault: Local-Remote Group Topology Mismatch

N+1 Link Group protection degraded due to Local-Remote Protection Mismatch.

1) Check that remote IDU is properly configured with N+1 Link Group topology, and all protection members are configured with the same priority level (if extra traffic is configured as revertive in one subrack, it should also be configured the

82 Loss of Protection There is no power on the standby IDM

1) Check if the power switch is on. 2) Replace standby IDM

83 Temp License is Active Temporary License activated by the user

Load permanent license or disable the temporary license



84 Ingress Gigabit Ethernet blocked on Radio

There is a Radio fault on the remote radio or the "Block Radio Command on the protection configuration" is enabled. The Alarm should be raised only on Multi Radio. The cause for radio fault are: Radio LOF, Link ID mismatch, Drawer ID mismatch, Excessive


84 Egress Gigabit Ethernet blocked on Radio

There is a Radio fault on the local radio or the "Block Radio Command on the protection configuration" is enabled. The Alarm should be raised only on Multi Radio. The cause for radio fault are: Radio LOF, Link ID mismatch, Drawer ID mismatch, Excessive B

1) Check the Block Radio command status on the protection configuration. 2) Check the local radio alarms and solve the radio fault accordingly.

85 Unknown RFU Type IDC's SW doesn't support the RFU. Upgrade IDC's SW.

85 Incompatible RFU TX Calibration

RFU calibration tables requires IDC SW upgrade. Upgrade IDC's SW.

401 Node down.

This alarm occurs when the connection between the NMS and the network element is lost.

402 User <name> (from <IP>) failed to login <n> times.

This alarm occurs when the user fails to log in to the NMS system correctly several times consecutively.

403

Standby serevr failed to connect to main server (the main server is configured as Standalone).

This alarm occurs when a secondary standby NMS server tries to connect to a stand-alone NMS server.

Open the main server configuration, and in the Redundancy section, change the server roll from Stand Alone to Main Server.

404 No communication between main and standby servers.

This alarm occurs for a primary NMS server when its connection to the standby NMS server is lost.

405 License expires in less than two weeks.

This alarm occurs for the NMS server when the license is set to expire in less than two weeks.

Contact customer support to obtain a license file for the server.

406 License expired. This alarm occurs for the NMS server when the license expires.

Contact customer support to obtain a license file for the server.

407 Network Elements number exceeds the license limit.

This alarm occurs for the NMS server when the number of network elements exceeds the license limit.

Remove some of the elements, or Contact customer support to obtain a license file for the updated number of elements.



408 Failed loading license file.

This alarm occurs for the NMS server when it fails to load the license file.

The license file is probably corrupted. Contact customer support to obtain a new license file.

409 Failed to start the TFTP server on <host> (address already in use).

This alarm occurs when NMS server attempts to start the TFTP, but the TFTP port (69) is already bound by another process.

Check your system, and disable other TFTP servers.

410 Disconnected User This alarm occurs when a user is disconnected by another user.

411 Standby serevr failed to connect to main server (versions mismatch).

This alarm occurs when a secondary standby NMS server tries to connect to a main NMS server,with a different software version.

1) Verify the existence of all IDMs and ODU, and verify their connectivity. 2) Open the unit Alarm Log (using the element manager) and send to customer support the code in the end the "XPIC Insufficient" event text.

414 Enabled feature set <feature name> is not licensed

The enabled feature set is not licensed.

Disable the feature or contact Support to get an appropriate license.


Fault Isolation using Loopbacks The loopback function provides a means of testing the link at various points. During the procedure, the external equipment sends a data pattern and monitors its receipt. If the received pattern is identical to the sent pattern, the connection between the equipment and the loop is confirmed.

Loopback

FibeAir is capable of performing loopback testing at several points in the link. The test is run from the CeraView management software, or via the SNMP protocol.

During the loopback test, an alarm indication will appear to remind you to cancel the test when you are done.

The following loopback tests can be performed from the window:

Local:

155 Mbps Line Interface

Wayside Channel

EquipmentLocal IDUInterfaces

101101110...

101101110...

Modem &IF

Local IDU

to ODU

Local Loop

Full IDU (all three inputs through the IDU, modulator, and looped in the IF).

Equipment Radio Link

101101110

101101110Equipment Radio Link

101101110

101101110


Remote:

155 Mbps Line Interface

Wayside Channel

EquipmentLocal IDUInterfaces

101101110...

101101110...

Modem &IF

Local IDU

Remote Loop

Full Radio Link Loopback (local external equipment through the radio link, to the remote line interface module, back through the radio link, to the local external equipment).

Equipment

101101110...

101101110...

Local Terminal

Local IDU

LocalODU

Modem&IF

LineInterface

Remote IDU

Remote Terminal

155 MB/sLine Interface

LoopbackLoop

Remote Terminal Loop

Connection Fault Guide

Problems that occur when trying to connect to the FibeAir system using CeraView, may be due to incorrect cable configuration. If there is a connection problem in the system, CeraView will start, but an hour glass will appear when the software is loading to indicate that a problem exists.

The following steps will help you identify and correct such problems.

Check the Cables

Refer to the figure below for the following procedures.

1. For Ethernet connection between FibeAir and a PC network card, use a cross cable.

For Ethernet connection between FibeAir and an Ethernet hub (for example, connecting to a LAN jack in a wall) use a straight cable.

2. For serial connection between FibeAir and a PC serial port, use a straight cable.


For serial connection using a dial-up modem, use a cross cable.

Cable Connections

Check Read and Write Communities

Ping FibeAir. If ping succeeds, the problem may be with the CeraView software installation, or the computer TCP\IP stack. Check the read and write communities in FibeAir and in the management station configuration.

If ping fails, there may be a network connectivity problem.

A typical conflict may occur between the IDU configuration and the related CeraView parameter.

In addition, the Agent Address must be identical to the IDU IP address, and the source address must be identical to the computer’s address.

The following figure shows a typical example of IP addresses and network configuration.

Terminal

CeraView

IP ManagementNetwork

3200T GNE A

SNMP

RemoteTerminal

Telnet

3200T NE B

1500P NE C

PPP /Ethernet

1500P NE D

PPP /Ethernet

3xRS-232

Site A Site B

192.168.1.33

192.168.1.3192.168.1.2192.168.1.1 192.168.1.17

192.168.1.18192.168.1.19

192.168.1.34

Typical Network Configuration

Check the Serial Connection

If the connection is via serial line, check the serial line speed in FibeAir, and in the Management station configuration. In the terminal, the serial line speed is specified using the IP Configuration menu.

Check the Ethernet Connection

Verify that the Management station and FibeAir IP interfaces have the same net ID. If they should not be included in the same network, check the default router address.

After performing the verifications above, if there is still a problem with network connectivity, together with the system administrator check for firewalls and routing configuration errors.

ceragon ip10 troubleshooting guide

Documents

e1t1e3ds3

e1t1 loss

ais trib hp

unequipped

ethenet services

fibeair troubleshooting

payload label

tim trib hp