Anda di halaman 1dari 44

FibeAir

Troubleshooting Guide

Part ID: BM-0108-0 Doc ID: DOC-00015466 Rev a.01 November 2008

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 users authority to operate the equipment and the warranty for such equipment. Copyright 2008 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: info@ceragon.com 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: infous@ceragon.com

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: infoeuro@ceragon.com APAC Headquarters Ceragon Networks (HK) Ltd. Singapore RO Level 34 Centennial Tower 3 Temasek Avenue Singapore 039190 Tel - + 65 6549 7886 Fax: +65 6549 7011

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

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
IDU alarm LEDs Coax cable connection Coax cable All equipment Receive level (voltage in IDU/ODU/RFU, or using management) Torque on antenna mount bolts

Check for ...


All green Tight, no corrosion or moisture No cracks or kinks Dust or dirt Per installation records Tight mount

Comments
If not, perform troubleshooting Clean/repair as required Replace as required Clean as required Align/adjust as required

Adjust as required

FibeAir Troubleshooting Guide

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

FibeAir Troubleshooting Guide

IDU LED Indicators


The following table lists 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.

Color LED Red X X X X X X Yello w Green X X X X Description

PWR (Power) LINE LOF (Loss of Frame) BER (Bit Error Ratio)

Red - power supply problem Red - no input to main channel / high BER Yellow - JO mismatch Red - radio did not recognize information frame (radio link problem/radio LOF) 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) Red - loopback is active Yellow - Protected configuration. The unit is currently passive or Tx mute is operating Red - modem unlocked Yellow - high temperature / fan problem Red - no link, or ODU power, or ODU/RFU unlocked Yellow - radio interference, or high temperature, or Rx/Tx out of range Red - RF cable open / RF cable short 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)

LPBK (Loopback) STBY (Standby) IDU ODU

X X

X X

X X

X X

X X

CBL (Cable) RMT (Remote Unit)

X X X

X X

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10


LED Name Description Severity Color Info Probable Cause 1) Line is not properly connected. 2) External equipment is faulty. User configured system to loopback mode. User configured system to loopback mode. 1) Line is not properly connected. 2) External equipment is faulty. 1) Line is not properly connected. 2) External equipment is faulty. 1) Port is disabled. 2) Line is connected to a disabled port. Corrective Action 1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system. Cancel loopback configuration. Cancel loopback configuration. 1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system. 1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system. 1) Enable relevant port. 2) Disconnect cable from relevant port. --1) Check connection of FE cable. 2) Replace FE cable.

PDH

excessiveber

E1/T1 excessive BER on port #%1

Major

Red

Excessive BER alarm status

PDH

loopbacktowardsline loopbacktowardsradio

E1/T1 loopback towards line on port #%1 E1/T1 loopback towards radio on port #%1

Major

Red

Loopback towards line alarm status Loopback towards radio alarm status

PDH

Major

Red

PDH

loss-ofsignal

E1/T1 loss of signal on port #%1

Major

Red

No signal is detected on port

PDH

signaldegrade

E1/T1 signal degrade on port #%1

Minor

Yellow

Signal degrade is detected on port Unexpected signal is detected on port

PDH

unexpected -signal ext-inalarm eth-localarm

E1/T1 unexpected signal on port #%1 %1 Ethernet loss of carrier on port #%1

Warning

Yellow

IDU

Warning

Yellow

External Alarm Input Ethernet Loss of Carrier on Port #n 1) FE cable disconnected 2) Defected FE cable. Radio LOF/EXBER/ Link ID on local or remote side (in pipe application)

IDU

Major

Red

IDU

eth-txmute-alarm

Ethernet Tx mute override on port #%1

Major

Red

Ethernet TX Mute Override

Check link

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name

Description Gigabit ethernet loss of carrier on port #%1 Gigabit ethernet SFP not inserted Gigabit ethernet SFP Tx fault GBE Tx mute override on port #%1

Severity

Color

Alarm Info Gigabit loss of carrier Gigabit Ethernet SFP not intact Gigabit Ethernet SFP TX Fault GBE TX Mute Override Firmware file was not successfully loaded Firmware file was not found The system's alarm file was not found SW failed to properly initialize IDU is in extreme temperature condition Fan failure HW failure Backup kernel is running

Probable Cause 1) Cable is not connected to the port. 2) Cable is defected. SFP is not inserted SFP malfunction Radio LOF/EXBER/Link ID on local or remote side 1) Firmware file is missing. 2) System error in power up. 1) Firmware file is missing. The alarm file was deleted or is corrupted SW error during system intialization The external cooling/heating system is not operating. Defective fan unit Defected HW 1) The kernel (/boot/uImage) is corrupted or missing

Corrective Action 1) Connect cable to the port. 2) Replace cable. 1) Check SFP connector. 2) Replace fiber. Replace SFP

IDU

gbe-loc-alarm

Major

Red

IDU

gbe-sfp-alarm

Major

Red

IDU

gbe-sfp-tx-alarm

Major

Red

IDU

gbe-tx-mutealarm

Warning

Yellow

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

IDU

file-load-erroralarm

Firmware file load error (%1)

Critical

Red

IDU

file-not-foundalarm

Firmware file not found (%1) Alarm file not found SW error: entity initialization failure IDU extreme temperature conditions Fan failure General HW failure %1 Backup kernel is running

Critical

Red

IDU

alarms-file

Major

Red

IDU

entity-init-failalarm extremetemperature fan-failure generalhardware-failure kernel-backup

Major

Red

Reset system Turn on external cooling/heating systems. Replace fan unit 1) Reset system. 2) Replace IDU. 1) Re-install the SW.

IDU IDU IDU

Warning Minor Major

Yellow Yellow Red

IDU

Minor

Yellow

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED IDU

Alarm Name low-input-voltage param-set-failalarm

Description Low input voltage SW error: parameter set failed

Severity Warning

Color Yellow

Alarm Info Low input voltage detected Parameter set failure

Probable Cause Low input to the system SW error 1) Inventory file is missing. 2) Inventory file was found to be corrupt upon system power up. 1) Inventory file is missing. 1) Demo license activated by user.

Corrective Action 1) Check power supply voltage. Reset system

IDU

Warning

Yellow

IDU

corrupted-filealarm

Inventory file (%1) is corrupted

Critical

Red

The inventory file is corrupted

1) Reset system. 2) Download inventory file

IDU

file-not-foundalarm demo-licensealarm

Inventory file (%1) was not found Demo license

Critical

Red

Inventory file was not found Demo license is used by customer

1) Download inventory file. 2) Reset system. 1) Terminate demo license. 2) Activate operational license. 1) Check that the code was entered correctly. 2) Call tech support for new license generation. 1) Download Modem file. 2) Reset system. 1) Download file. 2) Reset system. 1) Download radio script LUT. 1) Download radio script.

IDU

Warning

Yellow

IDU

license-violationalarm

License violation %1

Warning

Yellow

License violation

1) Unit does not match license features set.

IDU

firmware-filemissing-alarm firmware-loaderror-alarm fpga-file-curruptalarm fpga-file-notfound-alarm

Modem firmware file not found Modem was not loaded successfully Radio script (LUT) is corrupt Radio script (LUT) not found

Critical

Red

Modem file was not found Modem was not loaded successfully Radio script LUT is not valid Radio script LUT not found

1) Modem file is missing. 1) File is corrupt. 2) System failure. 1) Faulty file. 1) File was not downloaded to system.

IDU

Critical

Red

IDU

Critical

Red

IDU

Critical

Red

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name incompatiblescript-alarm modem-scriptfile-corrupt-alarm modem-scriptfile-not-foundalarm mrmc-file-corruptalarm mrmc-file-notfound-alarm rfu-file-corruptalarm rfu-file-not-foundalarm if-loopback-alarm

Description Incompatible script: %1 %2 Radio script is corrupt Radio script not found MRMC file is corrupt MRMC file not found RFU file is corrupt RFU file not found IF loopback

Severity

Color

Alarm Info Incompatibilit y between RFU and loaded radio script Radio script is not valid Radio script not found MRMC file not valid MRMC file not found RFU file not valid RFU file not found IF loopback initiated IF synthesizer unlock

Probable Cause 1) Incompatibility between RFU and loaded radio script. File is corrupt File not found File is corrupt File not found File is corrupt File not found 1) User enabled IF loopback. 1) Extreme temperature condition. 2) HW failure.

Corrective Action 1) Change RFU. 2) Change Raido script. Download file Download file Download file Download file Download file Download file 1) Disable IF loopback. 1) Check installation. 2) Reset IDU. 1) Check IF cable and connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU. 1) Check IF cable and connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.

IDU

Critical

Red

IDU IDU IDU IDU IDU IDU IDU

Critical Critical Critical Critical Critical Critical Warning

Red Red Red Red Red Red Yellow

IDU

lock-detect-alarm

IF lock detection

Critical

Red

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.

IDU

cable-short

Cable short

Major

Red

There is a short in the IF cable

1) Physical short at the IF cable.

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name

Description

Severity

Color

Alarm Info

Probable Cause

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

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.

Protection

cabledisconnecte d-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) RFU properties are not identical. 2) Radio scripts are not identical. 1) User command - Force Protection Switch 1) SW fault in synchronization of databases User issued Protection Lockout

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

Protection

configuratio n-mismatchalarm forceswitch-alarm ipi-xml-filealarm lockoutalarm

Mate IDU configuration mismatch Protection force switch Protection SW activity fault Protection lockout

Major

Red

Mismatch between IDU in Protection mode Force switch command was issued SW fault in Protection mechanism Protection Lockout command was isused

1) Change RFU. 2) Download required radio script. 1) Clear Force Switch Command. 1) Reset Standby unit. Clear Lockout command

Protection

Warning

Yellow

Protection

Warning

Yellow

Protection

Major

Red

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name

Description

Severity

Color

Alarm Info

Probable Cause 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) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU. Link ID is not the same at both sides of link 1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU. 1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU.

Corrective Action

Protection

mate-commfailure-alarm

Mate IDU communication error

Major

Red

IDU cannot communicate with its mate IDU

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

Radio

radioexcessiveber

Radio excessive BER

Major

Red

Excessive BER on radio

1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU. Configure same Link ID for both sides of link. 1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU. 1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU.

Radio

radio-link-idmismatch

Link ID mismatch

Critical

Red

Link ID Mismatch Alarm

Radio

radio-lof

Radio loss of frame

Critical

Red

Loss Of Frame on radio

Radio

radio-signaldegrade

Radio signal degrade

Minor

Yellow

Signal Degrade on radio

FibeAir Troubleshooting Guide

LED Indications for FibeAir IP-10 - Continued

LED Remote

Alarm Name remotecommunicatio n-failure incompatiblerfu-txcalibration

Description Remote communication failure Incompatible RFU TX calibration

Severity Major

Color Red

Alarm Info Remote Communicati on Failure Alarm RFU calibration tables require IDC SW upgrade

Probable Cause 1) Fade in the link.

Corrective Action 1) Check link performance.

RFU

Major

Red

RFU calibration tables require IDC SW upgrade.

Upgrade IDU's SW.

RFU

communicatio n-failure

RFU communication failure

Warning

Yellow

Failure in communicati on 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 NType 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 1) Reset the IDU / RFU. 2) Replace RFU. Enter delay calibration value manually 1) Check installation conditions. 2) Verify operation as per product's specs. 3) Replace RFU.

RFU

delaycalibrationfailure-1 delaycalibrationfailure-2

RFU delay calibration failure 1 RFU delay calibration failure 2

Warning

Yellow

RX AGC is not locked Calibration cannot be completed due to notch detection RFU temperature is too high or low

Defective RFU Calibration cannot be completed due to notch detection

RFU

Warning

Yellow

RFU

extreme-tempcond

RFU extreme temperature

Warning

Yellow

1) Installation conditions. 2) Defective RFU.

FibeAir Troubleshooting Guide

10

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name

Description

Severity

Color

Alarm Info

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

Corrective Action 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 1) Replace RFU.

RFU

fan-failure

RFU fan failure

Warning

Yellow

RFU Fan Failure Alarm

RFU

hardware-failure1

RFU hardware failure 1

Critical

Red

RFU Hardware Failure 1 Alarm RFU Hardware Failure 2 Alarm

RFU

hardware-failure2

RFU hardware failure 2

Critical

Red

1) Defective RFU.

1) Replace RFU. 1) Check IF cable connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU. 1) Check IF cable and connectors. 2) Verify that NType 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

low-if-signal-torfu

Low IF signal to RFU

Major

Red

RFU is detecting low signal from IDU

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

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.

FibeAir Troubleshooting Guide

11

LED Indications for FibeAir IP-10 - Continued

LED RFU

Alarm Name pa-extreme-tempcond

Description RFU PA extreme temperature

Severity Warning

Color Yellow

Alarm Info RFU PA Extreme Temperature RFU Power Failure (12v) Alarm

Probable Cause 1) Installation conditions. 2) Defective RFU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU. 1) User action.

Corrective Action 1) Check installation conditions. 2) Replace RFU 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU. 1) Disable RFU loopback.

RFU

power-failure-12v

RFU power failure (12v)

Major

Red

RFU

power-failure1point5

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-6vsw

RFU power failure (6v SW)

Major

Red

RFU Power Failure (6v SW) Alarm

RFU

power-failureminus-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 loopback Alarm

RFU

rfu-loopbackactive

RFU loopback

Major

Red

FibeAir Troubleshooting Guide

12

LED Indications for FibeAir IP-10 - Continued

LED RFU

Alarm Name rfu-power-supplyfailure

Description RFU power supply failure

Severity Major

Color Red

Alarm Info RFU power supply failure

Probable Cause At least one of the PSU voltages is too low. 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).

Corrective Action 1) Replace RFU. 1) Check antenna alignment & link planning. 2) Check link settings (TX power, TX freq). 3) Check antenna connections. 4) Replace local/remote 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. 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-out-ofrange

Rx level out of range

Warning

Yellow

RFU RX Level Out of Range

RFU

rx-level-path1-outof-range

RFU Rx level path1 out of range

Warning

Yellow

RFU Rx Level Path1 Out of Range

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

RFU

rx-level-path2-outof-range

RFU Rx level path2 out of range

Warning

Yellow

RFU Rx Level Path2 Out of Range

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

FibeAir Troubleshooting Guide

13

LED Indications for FibeAir IP-10 - Continued

LED

Alarm Name synthesizer-1unlocked

Description Synthesizer 1 unlocked

Severity

Color

Alarm Info RFU synthesizer is unlocked

Probable Cause 1) Defective RFU. 2) Defective XPIC cable connection. 1) Defective RFU. 2) Defective XPIC cable connection. 1) Defective RFU. 2) Defective XPIC cable connection. One of the RFU synthesizers is unlocked. 1) Defective RFU (the RFU cannot transmit the requested TX power) RFU Transmitter muted by user. IDC's SW doesn't support the RFU.

Corrective Action 1) Replace XPIC cable. 2) Replace RFU.

RFU

Major

Red

RFU

synthesizer-2unlocked

Synthesizer 2 unlocked

Major

Red

RFU synthersizer is unlocked

1) Replace XPIC cable. 2) Replace RFU.

RFU

synthesizer-3unlocked

Synthesizer 3 unlocked

Major

Red

RFU synthesizer is unlocked One of the RFU Synthesizers is Unlocked RFU TX Level Out of Range RFU TX Mute IDC's SW doesn't support the RFU

1) Replace XPIC cable. 2) Replace RFU. 1) Replace RFU. 2) In XPIC mode, replace mate RFU as well. 1) Replace RFU. 2) Intermediate solution - reduce TX power. Unmute the RFU transmitter. Upgrade IDC SW.

RFU

synthesizerunlocked

Synthesizer unlocked

Major

Red

RFU

tx-level-out-ofrange

Tx level out of range

Minor

Yellow

RFU

tx-mute

Tx mute IDU SW does not support this type of RFU

Warning

Yellow

RFU

unknown-rfu-type

Major

Red

FibeAir Troubleshooting Guide

14

LED Indications for Hitless Systems For Hitless systems, the following table lists the LEDs and their indications: LOF (LED Panel) - LOF LED Color Yellow Red Alarm Explanation Local unit receives LOF from a receive path currently not in use. Local unit receives LOF from a receive path currently in use.

LOF (Interface Panel) - ALRM LED Color OFF Red Green Alarm Explanation Hitless mode is disabled. Local unit receives LOF from the mate unit. Hitless switching can be performed, if necessary.

Local Receiver (Interface Panel) - Rx ACTV LED Color OFF Green Alarm Explanation Local receiver not in use. Local receiver in use.

FibeAir Troubleshooting Guide

15

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 Insufficient System Configuration for Full XPIC Support Probable Cause One of the system elements does not support XPIC. Or, the system is missing one of the needed elements. One of the system elements does not support XPIC. Or, the system is missing one of the needed elements. Corrective Actions 1) Check the Block Radio command status on the protection configuration. 2) Check the remote radio alarms and solve the radio fault accordingly 1) Check the Block Radio command status on the protection configuration. 2) Check the remote radio alarms and solve the radio fault accordingly 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. Unmute the RFU transmitter. 1) Replace RFU. 2) Intermediate solution - reduce TX power.

10

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

11

Synthesizer #1/2/3 Unlocked

One of the RFU synthisizers is unlocked.

12 12

Tx Mute On/Off Tx Level Out of Range

RFU transmitter muted by user The RFU cannot transmit the requested Tx power.

FibeAir Troubleshooting Guide

16

Trap ID

Description

13

Rx Level Out of Range

14

ODU Temperature Out of Range

15

XPIC Cable Swap

Probable Cause 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). RFU temperature too high/low. 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.

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

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 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 1) Check -48 VDC supply to the IDU. 2) Replace IDU.

15

Power Input #1 is Down

Subrack redundant power feed failure.

15 15 15

IDU 5/8/3.3/-5V Power Supply Failure Drawer Power On/Off Drawer Internal Power Failure (Board #2) Drawer Internal Power Failure (Board #1)

Failure in an IDU power supply. Drawer power on/off. Board #1 - MUX card. Board #2 - Modem card. This alarm may also be generated if a drawer in Internal Protection was switched off. Drawer Internal Power Failure (Board #1)

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

15

FibeAir Troubleshooting Guide

17

Trap ID

Description

Probable Cause

Corrective Actions 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 1) Check IF cable and connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. 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. 1) Check IF cable and connectors. 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. 1) Download the Modem script to the IDC and reset the IDM. 1) In case of failure, replace IDM. 1) Check installation conditions. 2) Replace IDM. 1) Replace fan. 1) Disable loopback 1) Disable loopback 1) Disable loopback 1) Disable loopback 1) Disable loopback Disable Wayside line loopback Disable Wayside line loopback Disable loopback Disable loopback

16

Extension Link Communication Failure

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

16

Cable Short

IDM-RFU cable short.

16

Cable Open/Short

IDU-ODU cable open/short.

16

Cable Open

IDM-RFU cable open.

17

MRMC=???value??? Script File is Missing Drawer Internal Hardware Intact/Failure Board#1 IDU Temperature Out of Range Fan Failure XC Internal Loopback on Line #5 XC Internal Loopback on Line #4 XC Internal Loopback on Line #3 XC Internal Loopback on Line #2 XC Internal Loopback on Line #1 Wayside Channel Loopback Wayside Channel Loopback ODU Internal Loopback (Not) Active Internal Loopback on Fiber #n

Multi-Rate Multi-Constellation configuration script for the specified capacity/modulation is missing in the IDC. Drawer hardware intact ok / failure (Mux) IDU Temperature Out of Range Fan Failure XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback Wayside Line loopback applied by user in internal protection Wayside Left Line loopback applied by user RFU loopback applied by user Internal loopback on Fiber

17 18 18 19 19 19 19 19 19 19 19 19

FibeAir Troubleshooting Guide

18

Trap ID

19

19 19 19 19 19 20 21 21 22

Description 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 IDU Local Loopback (Not) Active Gigabit Ethernet Internal Loopback External Loopback on Fiber #n E1\T1 Internal Loopback on Port #n E1\T1 External Loopback on Port #n Remote Communication Failure PRBS Test is Running on Radio Link Group #1 N+1 Protection Fault: Locked by User Trib RS: LOF

Probable Cause

Corrective Actions

Loopback applied by user

Disable loopback

IDU IF loopback applied by user Gigabit Ethernet Internal Loopback applied by user. IDU Line loopback applied by user IDU Line loopback applied by user E1/T1 External loopback No communication between the IDUs over the link. PRBS test started. Lockout or Force Switch to Protecting Link Group maintenance command activated. Trib RS: LOF

Disable loopback Disable Gigabit Ethernet Internal Loopback 1) Disable loopback 1) Disable loopback 1) Disable loopback 1) Verify link is up and no errors over the link. 2) Check in-band management configuration. Disable PRBS test. Release maintenance command.

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 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. 1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH)

22

Radio RS: LOF

Radio RS: LOF (ADM)

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.

FibeAir Troubleshooting Guide

19

Trap ID

Description

Probable Cause

22

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

Loss Of Frame alarm on the line input.

22

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

Loss Of Frame alarm on the line input

22

Fiber RS: LOF

Fiber RS: LOF (ADM)

Corrective Actions 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. 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. 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 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. 1) Check line input. 2) Check fiber. 3) Verify end equipment transmits properly. 4) Replace IDM. 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. 1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDM. 1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDU.

23

Trib RS: LOS

Trib RS: LOS

23

Loss of Signal on Fiber #n

Loss Of Signal alarm on the line input

23

Gigabit Ethernet Loss of Signal

Gigabit Ethernet Loss of Signal

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

23

Fast Eth. #01/02 Loss of Carrier

Fast Ethernet Loss of Carrier

FibeAir Troubleshooting Guide

20

Trap ID

Description

Probable Cause

23

E1\T1 Loss of Signal on Port #n

E1\T1 Loss of Signal

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

24 24 24 24 24 24 24 24 24 24 24 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25

Trib RS: TIM Trib LP #n: TIM Trib HP: TIM Trace Identifier Mismatch on Fiber #n Radio LP #n: TIM Radio HP: TIM Fiber RS: TIM Fiber RS: TIM Fiber RS: TIM Fiber LP #n: TIM Fiber HP: TIM Trib RS: Excessive BER Trib MS: Excessive BER Trib LP #n Excessive BER Trib HP: Excessive BER Radio RS: Excessive BER Radio RS: Excessive BER Radio RS: Excessive BER Radio MS: Excessive BER Radio LP #n: Excessive BER Radio HP: Excessive BER Fiber RS: Excessive BER Fiber RS: Excessive BER Fiber RS: Excessive BER Fiber MS: Excessive BER Fiber LP #n Excessive BER Fiber HP: Excessive BER

Trib RS: TIM Trib LP #n: TIM Trib HP: TIM Trace Identifier Mismatch alarm (J0 mismatch). Radio LP: TIM Radio HP: TIM Fiber RS: TIM Fiber RS: TIM Fiber RS: TIM Fiber LP #n: TIM Fiber HP: TIM Trib RS: Excessive BER Trib MS: Excessive BER Trib LP #n Excessive BER Trib HP: Excessive BER Radio RS: Excessive BER (Regenerator) Radio RS: Excessive BER (Regenerator) Radio RS: Excessive BER (ADM) Radio MS: Excessive BER Radio LP: Excessive BER Radio HP: Excessive BER Fiber RS: Excessive BER (Regenerator) Fiber RS: Excessive BER (Regenerator) Fiber RS: Excessive BER (ADM) Fiber MS: Excessive BER Fiber LP #n Excessive BER Fiber HP: Excessive BER

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

FibeAir Troubleshooting Guide

21

Trap ID

Description

Probable Cause

25

Excessive BER on Radio #n

Major radio Excessive BER alarm

25

Excessive BER on Fiber #n

Major line Excessive BER alarm

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

25 25

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

E3/DS3 Excessive BER E1/T1 Excessive BER 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.

25

E1\T1 Excessive BER on Port #n

Major Excessive BER alarm on E1/T1 port

26 26 26 26

Trib RS: Signal Degrade Trib MS: Signal Degrade Trib LP #n Signal Degrade Trib HP: Signal Degrade

Trib RS: Signal Degrade Trib MS: Signal Degrade Trib LP #n Signal Degrade Trib HP: Signal Degrade 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 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

Signal Degrade on Radio #n

Minor radio BER alarm

26

Signal Degrade on Fiber #n

Minor line SD BER alarm

26 26 26 26 26

Radio RS: Signal Degrade Radio RS: Signal Degrade Radio RS: Signal Degrade Radio MS: Signal Degrade Radio LP #n: Signal Degrade

Radio RS: Signal Degrade Radio RS: Signal Degrade Radio RS: Signal Degrade Radio HP: Unequipped Radio LP #n: Signal Degrade

FibeAir Troubleshooting Guide

22

Trap ID 26 26 26

Description Radio HP: Signal Degrade Fiber RS: Signal Degrade Fiber RS: Signal Degrade

Probable Cause Radio HP: Signal Degrade Fiber RS: Signal Degrade (ADM) Fiber RS: Signal Degrade

Corrective Actions

26

Fiber RS: Signal Degrade

Minor line BER alarm

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.

26 26 26 26 26

Fiber MS: Signal Degrade Fiber LP #n Signal Degrade Fiber HP: Signal Degrade E1\T1\E3\DS3 #n Signal Degrade E1\T1\E3\DS3 #n Signal Degrade

Fiber MS: Signal Degrade Fiber LP #n Signal Degrade Fiber HP: Signal Degrade E3DS3 Signal Degrade E3DS3 Signal Degrade 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

E1\T1 Signal Degrade on Port #n

Minor BER alarm on E1/T1 port

27 27 27 27 27 27 27 27 27 28 28

Trib MS: AIS Trib LP #n: AIS Trib HP: AIS Radio MS: AIS Radio LP #n: AIS Radio HP: AIS Fiber MS: AIS Fiber LP #n: AIS Fiber HP: AIS Trib RS: Unexpected Signal Gigabit Ethernet Unexpected Signal Fiber RS: Unexpected ?10;E1\T1\E3\DS3 #n Unexpected Signal Fast Ethernet Unexpected Signal on Port #n Trib LP #n: LOP Trib HP: LOP Radio LP #n: LOP

Trib MS: AIS Trib LP #n: AIS Trib HP: AIS Radio MS: AIS Radio LP #n: AIS Radio HP: AIS Fiber MS: AIS Fiber LP #n: AIS Fiber HP: AIS Trib RS: Excessive BER GbE port is disabled but GbE data is detected. Unexpected signal on the line input. Port disabled but line is connected. Fast Ethernet Unexpected Signal on Port #n Trib LP #n: LOP Trib HP: LOP Radio LP: Loss of pointer (LOP) alarm occurs. 1) Enable GbE port, disable GbE port of the source, or disconnect the fiber 1) Enable line port or disconnect line

28

28 30 30 30

FibeAir Troubleshooting Guide

23

Trap ID 30 30 30 31 31 31 31 31 31 31 31 31 32 32 32 32 32 32 33 33 33 33 33 33 34 35 36 37

Description Radio HP: LOP Fiber LP #n: LOP Fiber HP: LOP Trib MS: RDI Trib LP #n: RDI Trib HP: RDI Radio MS: RDI Radio LP #n: RDI Radio HP: RDI Fiber MS: RDI Fiber LP #n: RDI Fiber HP: RDI Trib LP #n: PLM Trib HP: PLM Radio LP #n: PLM Radio HP: PLM Fiber LP #n: PLM Fiber HP: PLM Trib LP #n: Unequipped Trib HP: Unequipped Radio LP #n: Unequipped Radio HP: Unequipped Fiber LP #n: Unequipped Fiber HP: Unequipped External Alarm External Alarm External Alarm External Alarm

Probable Cause Radio HP: Loss of pointer (LOP) alarm occurs. Fiber LP: Loss of pointer (LOP) alarm occurs. Fiber HP: Loss of pointer (LOP) alarm occurs. Trib MS: RDI Trib LP #n: RDI Trib HP: RDI Radio MS: Remote Defect Identifier signal (RDI) occurs. Radio LP: Remote Defect Identifier signal (RDI) occurs. Radio HP: Remote Defect Identifier signal (RDI) occurs. Fiber MS: Remote Defect Identifier signal (RDI) occurs. Fiber LP: Remote Defect Identifier signal (RDI) occurs. Fiber HP: Remote Defect Identifier signal (RDI) occurs. Trib LP #n: PLM Trib HP: PLM Radio LP: Payload Label Mismatch (PLM) occurs. Radio HP: Payload Label Mismatch (PLM) occurs. Fiber LP: Payload Label Mismatch (PLM) occurs. Fiber HP: Payload Label Mismatch (PLM) occurs. Trib LP #n: Unequipped Trib HP: Unequipped Radio LP: Unequipped Radio HP: Unequipped Fiber LP: Unequipped Fiber HP: Unequipped External alarm input #1 configured and triggered by user. External alarm input #2 configured and triggered by user. External alarm input #3 configured and triggered by user. External alarm input #4 configured and triggered by user.

Corrective Actions

FibeAir Troubleshooting Guide

24

Trap ID 38 39 40 41

Description External Alarm External Alarm External Alarm External Alarm

Probable Cause External alarm input #5 configured and triggered by user. External alarm input #6 configured and triggered by user. External alarm input #7 configured and triggered by user. External alarm input #8 configured and triggered by user.

Corrective Actions

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 1) Download XC firmware file of the required type and reset the IDC. 1) Download Wayside firmware file to the IDC and reset the IDC. 1) Download Subrack Auxiliary firmware file and reset the IDC.

42 42 42 42

XC <Type> FPGA File is Missing Wayside Firmware File is Missing Subrack Auxiliary FPGA File is Missing Secondary Clock Source Failure Radio Card #n Powered Down Primary Clock Source Failure MUX Firmware File is Missing Modem Firmware File is Missing

XC firmware file is missing in the 2-floor IDC. Wayside firmware file is missing in the IDC. Subrack Auxiliary firmware file is missing in the 2-floor IDC. Secondary Clock Source Failure Radio module pertained to Link Protection group is powered down or extracted. Primary Clock Source Failure A Mux FW file is missing from the system. A Modem FW file is missing from the system.

42

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

42 42 42

42

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

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

Load the required FW file, and reset system. Load the required FW file, and reset system. 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

FibeAir Troubleshooting Guide

25

Trap ID 42

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

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

Corrective Actions 1) Check if XC module is powered on and no other alarm related to XC is active. 2) Replace XC module. 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. 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. 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. Load another MRMC with bit rate supported by the license 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. 1) Reset IDU. 2) Verify correct SW version. 3) Verify correct interfaces. 4) Replace IDU. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module.

42

N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.

42

Line Card #n Powered Down

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

42

Line Card #1 Powered Down

Line module in carrrier #1 of the Link Protection group is powered down or extracted. 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.

42

License Fault

42

IDU-ODU Inner Communication Failure

IDC cannot communicate with ODC card.

42

IDU-MUX Inner Communication Failure

IDC cannot communicate with MUX card, MUX card upload failure. Upper IDM Board (MUX or XC) EEPROM inventory information CRC error Upper IDM Board (MUX or XC) EEPROM read access error

42

General Hardware Fault #9

42

General Hardware Fault #8

FibeAir Troubleshooting Guide

26

Trap ID

Description

Probable Cause

42

General Hardware Fault #7

FPGA load failure - Subrack Auxiliary board.

42

General Hardware Fault #7

FPGA load failure - Modem

Corrective Actions 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. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Replace Subrack Auxiliary module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Extract and re-insert Subrack Auxiliary module. 2) Replace Subrack Auxiliary module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Download correct SW/FW/Configuration scripts. 2) Power IDM off/on. 3) 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 General Hardware Fault #11 General Hardware Fault #11

XO failure - Modem board Wrong card type detected in Subrack Auxiliary slot. Lower IDM Board (Modem or XC) EEPROM inventory information CRC error Subrack Auxiliary EEPROM checksum failure. Lower IDM Board (Modem or XC) EEPROM read access error

42

42

42

General Hardware Fault #10

42

General Hardware Fault #10

42

General Hardware Fault #1

IDU Synthesizer lock

FibeAir Troubleshooting Guide

27

Trap ID

Description

Probable Cause

42

EOW chaining Loss of Signal

No signal detected on Subrack Auxiliary EOW chaining input.

Corrective Actions 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 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 1) Check that proper Subrack Auxiliary module inserted. 2) Extract and re-insert Subrack Auxiliary module. 3) Replace Subrack Auxiliary module. 1) Disable loopback

42

Drawer-RFU Communication Failure

No communication between IDM and RFU.

42

Drawer Internal Power Failure (Board #2) Drawer Internal Loopback Copy IDC Configuration to Mate Copy Carrier Configuration To Mate Failed/Succedded Clock Unit Unlocked Clock Unit Out of Range Auxiliary Card Fault #01 ACM Configuration File is Missing TFTP IDU/MUX/ODU verxxx Download Succeeded/ Canceled/Failed IDU Configuration Download Succeeded/Error/Cancel led/Failed/Invalid File Boot/IDC/MUX/ODU/Mo dem Script/Modem/ Wayside/Mrmc table/RFU FPGA File Download Succeeded <file name>

Internal Power failure.

42 42 42 42 42 42

IDU IF loop applied by user IDC copy configuration by user in external protection Carrier configuration copied between two IDMs in protected configuration Clock Unit Unlocked Clock Unit Out of Range Subrack Auxiliary module failed or extracted. The ACM lookup table file cannot be found on the system disk. Software download operation status (from user's PC to IDC) Configuration download status, initiated by user

42

1) Check Subrack Auxiliary module is properly inserted. 2) Replace Subrack Auxiliary module. Load the lookup table file of the relevant release version or load the SFD file.

43

43

43

File download status. Initiated by user.

FibeAir Troubleshooting Guide

28

Trap ID 44 44 44 44 44 44 44

Description RFU FW Upload Failed RFU FW Upload Error RFU FW Upload Canceled ODU SW Upload Failed ODU SW Upload Error ODU SW Upload Canceled MUX/ODU Internal Download Succeeded/ Canceled/Failed/Error User Configuration Mismatch between IDC # and IDC #

Probable Cause Firmware upload operation status (from IDC to ODC) Firmware upload operation status (from IDC to ODC) Firmware upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) MUX/ODU Internal Download Succeeded/Canceled/Failed/ Error At least one configuration parameter which should be equal in these two IDCs has different values. Configuration in the IDC is different than in the drawers or Auxiliary channel board

Corrective Actions

46

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. 1) Check and compare configuration 2) See User Configuration Mismatch Alarm 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. 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. 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

46

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

46

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

Mismatch configuration between the IDC Database and the drawer.

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

46

User Configuration Mismatch

FibeAir Troubleshooting Guide

29

Trap ID

Description

Probable Cause 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. Internal system mismatch regarding the state of the radio - Mute/Unmute Mismatch in the internal protection configuration between the drawers. Mismatch configuration between local IDC Database and mate IDC database Configuartion mismatch between two IDCs in External Protection configuration. Configuartion mismatch between two drawers in External Protection configuration. Link ID is not identical on both ends of the link. Link ID Mismatch Link ID is not identical on both ends of the link. Link ID is not identical on both ends of the link. Different configuration between the IDUs on both sides of the link Different configuration between the IDUs on the same side of the link IDC MAC device failure loading with default MAC address 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

Corrective Actions 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. Reset IDM 1) Check and compare configuration 2) See mate Configuration Mismatch Alarm 1) Check and compare configuration 2) See mate Configuration Mismatch Alarm 1) Check and compare configuration. 2) Perform "copy to mate" from the IDC with the correct configuration 1) Check and compare configuration. 2) Perform "copy to mate" from the drawer with the correct configuration Set identical Link ID on both ends of the link. 1) Set identical Link ID on both ends of the link. 1) Set identical Link ID on both ends of the link. 1) Check and compare configurations 1) Check and compare configurations 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.

46

User Configuration Mismatch

46

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

46

46

46

46

Mate Configuration Mismatch Link ID Mismatch on Radio #n Link ID Mismatch Link ID Mismatch Link ID Mismatch IDU Hitless Remote Config Mismatch IDU Hitless Mate Config Mismatch General Hardware Fault #4 General Hardware Fault #3 General Hardware Fault #2

46 46 46 46 46 46

46

46

46

FibeAir Troubleshooting Guide

30

Trap ID 46 46

Description General Hardware Fault #1 General Cfg Mismatch

Probable Cause FPGA load failure - Wayside Channel Settings not supported by HW/SW. 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. 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) Incomapitibility alarm between link components. Typically refers to mixture of standard and "I" components in the link

Corrective Actions 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC. 1) Check if HW and SW support the requested configuration 1) Check link connections and settings. 2) Check XPIC configuration. 3) Verify that both links are up. 4) Check XPI 1) Check link connections and settings. 2) Check XPIC configuration. 3) Verify that both links are up. 4) Check XPI

46

Drawer ID Mismatch in Protecting Carrier

46

Drawer ID Mismatch

46

Device Incompatible Alarm (#103)

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

47 47

SW Mode Changed to Slave/Master?10;Chang e Remote Transmitter Request Sent Protection Internal/External Mate Not Exist Protection External Alarm Switch Protection Change to Standby Hitless Protection Configuration Mismatch Change Remote Transmitter Request Sent SDBER/EXBER/LOF/BE R Protection Communication Error on Cable

Change Master/Slave command System configured for protection without mate connected Protection switch by external alarm Different faults indicate hardware failure on the drawer Hitless is configred without protection Command was sent to remote end to switch when both local receivers identify Rx fault (for example, remote active transmitter fails) For External Protection configuration. Protection cable is connected but errors detected. 1) Check configuration. 2) Check Mate connected

47

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Enable protection or disable hitless

47

47

48

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

FibeAir Troubleshooting Guide

31

Trap ID 48

Description Protection Cable Disconnected Protection Cable Disconnect/Error/Power Error/Problem?10;Maste r-Slave Disconnect Heart Beat (Trap Only) Trib HP: LOM Radio HP: LOM Fiber HP: LOM Hitless Switch Locked to Self Radio By User Hitless Switch Locked to Right Radio By User Hitless Switch Locked to Mate/Self Radio By User Hitless Switch Locked to Left Radio By User Hitless Self/Mate Receiver in user Hitless Left/Right Receiver in Use Hitless Functionality Failure

Probable Cause Protection Cable Disconnected Problem with protection cable or the connection between the Master/Slave IDUs Heart Beat (Trap Only) Trib HP: LOM Radio HP: Loss of Multiframe (LOM) alarm occurs. Fiber HP: Loss of Multi-frame (LOM) alarm occurs. Hitless Switch Locked to Self Radio by User Hitless switching disabled by user and locked for one of the drawers. Hitless Switch Locked to Mate/Self Radio by User Hitless switching disabled by user and locked for one of the drawers. Hitless Self/Mate Receiver in user Left/Right receiver is used for processing data Hitless protection is not available. The link will fail in case of fade.

Corrective Actions 1) Connect Protection Cable. 2) Replace cable. 1) Replace cable. 2) Replace IDUs

48 49 50 50 50 51 51 51 51 51 51

1) Disable Hitless Lockout

1) Disable Hitless Lockout

51

52

Unused Radio Receiver LOF

Hitless Self Radio Receiver LOF

52

Own Radio BBLOF on Radio #n

Hitless Self Radio Receiver LOF

Not a real alarm since receiver switching is likely to happen during multipath fading. 1) Hitless cable disconnected. 2) Mate IDU is off. 3) Mate IDU has an alarm that prevents it from receiving data. 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 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

FibeAir Troubleshooting Guide

32

Trap ID

Description

Probable Cause 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. Hitless Self Radio Receiver LOF Hitless cable disconnected. In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected.

52

Loss of Frame on Unused Left/Right Radio

Corrective Actions 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 53 57

Hitless Self Radio Receiver LOF Hitless Cable Disconnect In-Band Radio PPP Link Disconnect?10;In-Band Line PPP Link Disconnect

Connect hitless cable. 1) Check the line connection. 2) Check in-band configuration. 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. 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. 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. 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. 1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module.

58

Wayside Channel Loss of Signal/Carrier

Wayside Channel Loss of Signal/Carrier in internal protection

58

Wayside Channel Loss of Signal/Carrier

Wayside Right Channel Loss of Signal/Carrier

58

Wayside 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

58

User Channel Ethernet Loss of Carrier

User Right Channel Loss of Carrier

FibeAir Troubleshooting Guide

33

Trap ID

Description

Probable Cause

Corrective Actions In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.

58

User Channel Ethernet Loss of Carrier

User Left Channel Loss of Carrier

59

ODU-2-ODU Cable Open

ODU-2-ODU Cable Open

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. 1) Check cable. 2) Replace cable. 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. 1) Upgrade MRMC scripts 2) Replace RFU 1) Disable Lockout

60

No Signal from ODU

No Rx (140 MHz) signal from RFU

60

Modem Script Not Supported Protection Lockout

61

61

Protection Force Switch RFU Power Supply Failure RFU Power Failure (Vd)

62

No modem script is available for this RFU. "Protection Lockout" command executed. Will lock the switching operation until removed. One of the system elements does not support XPIC. Or, the system is missing one of the needed elements. At least one of the PSU voltages is too low. RFU Power Supply Failure (Vd)

1) Disable "Force Switch"

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

62

62

RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)

62

RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)

FibeAir Troubleshooting Guide

34

Trap ID 62

Description RFU Power Failure (12v)

Probable Cause RFU Power Supply Failure (12v)

Corrective Actions 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 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. 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. 1) Check installation conditions. 2) Verify operation as per product's specs. 3) Replace 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 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 1) Check IF cable connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. 1) Reconnect XPIC clock cables at both RFUs 2) Replace XPIC cable 1) Check link performance 2) Re-perform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU

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

63

RFU Rx Level Path1 Out Of Range

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

64

RFU Extreme Temperature

RFU temperature is too high/low.

65

RFU Fan Failure

Fan Failure was detected by RFU

65

RFU Fan Failure

Fan Failure was detected by RFU

66

RFU Low Signal To ODU

RFU is detecting low signal from IDU

67

RFU XPIC Clock Failure

No XPIC clock is received from Master RFU

68

RFU Delay Calibration Failure 1

Delay calibration is unseccessfull since RX AGC is unlocked.

FibeAir Troubleshooting Guide

35

Trap ID

Description

Probable Cause Delay calibration is unseccessfull since wide or deep notch has been detected at the RX signal 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 SFP does not transmit Ethernet properly. SFP is not connected properly. HW encryption fault Encryption loss of frame The first encryption key exchange failed No session key exchange in the allowed time One of the built-in encryption system tests failed One of the Conditional tests failed Encryption mode changed by user, will take effect after next power up. Administrator password is the default value

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

69

RFU Delay Calibration Failure 2

70

Gigabit Ethernet TX Mute Override

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

70

Gigabit Ethernet SFP TX Fault Gigabit Ethernet SFP Not Intact Encryption Fault Encryption Sync Loss Initial KEP Failed Session Key Timer Elapsed Power-Up Test Failed Conditional Test Failed Encryption Will Turned Off On Next Reset Admin password in default state

1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM. 1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM. 1) Reset IDM. 1) Check link staus. 2) Reset IDM. 1) Check link status. 2) Reset IDC. 3) Reset IDM. 1)Check link status. 1) Reset IDC. 2) Reset IDM. 1) Reset IDC. 2) Reset IDM.

70 71 72 73 74 75 76 77 80

Change administrator password. 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 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: XC Peer Communication Failure

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

81

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

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

FibeAir Troubleshooting Guide

36

Trap ID

Description Link Group #1 N+1 Protection Fault: Protecting Radio Failure Link Group #1 N+1 Protection Fault: Locked by User

81

81

Probable Cause N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board. Lockout or Force Switch to Protecting Link Group maintenance command activated.

Corrective Actions 1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH) Release maintenance command. 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 1) Check if the power switch is on. 2) Replace standby IDM Load permanent license or disable the temporary license

81

Link Group #1 N+1 Protection Fault: LocalRemote Group Topology Mismatch

N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.

82 83

Loss of Protection Temp License is Active

There is no power on the standby IDM Temporary License activated by the user 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 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 IDC's SW doesn't support the RFU. RFU calibration tables requires IDC SW upgrade. This alarm occurs when the connection between the NMS and the network element is lost. This alarm occurs when the user fails to log in to the NMS system correctly several times consecutively.

84

Ingress Gigabit Ethernet blocked on Radio

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

84

Egress Gigabit Ethernet blocked on Radio

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

85 85

Unknown RFU Type Incompatible RFU TX Calibration Node down. User <name> (from <IP>) failed to login <n> times.

Upgrade IDC's SW. Upgrade IDC's SW.

401

402

FibeAir Troubleshooting Guide

37

Trap ID

403

Description Standby serevr failed to connect to main server (the main server is configured as Standalone). No communication between main and standby servers. License expires in less than two weeks. License expired. Network Elements number exceeds the license limit. Failed loading license file. Failed to start the TFTP server on <host> (address already in use). Disconnected User

Probable Cause This alarm occurs when a secondary standby NMS server tries to connect to a stand-alone NMS server. This alarm occurs for a primary NMS server when its connection to the standby NMS server is lost. This alarm occurs for the NMS server when the license is set to expire in less than two weeks. This alarm occurs for the NMS server when the license expires. This alarm occurs for the NMS server when the number of network elements exceeds the license limit. This alarm occurs for the NMS server when it fails to load the license file. This alarm occurs when NMS server attempts to start the TFTP, but the TFTP port (69) is already bound by another process. This alarm occurs when a user is disconnected by another user. This alarm occurs when a secondary standby NMS server tries to connect to a main NMS server,with a different software version. The enabled feature set is not licensed.

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

404

405

Contact customer support to obtain a license file for the server. Contact customer support to obtain a license file for the server. Remove some of the elements, or Contact customer support to obtain a license file for the updated number of elements. The license file is probably corrupted. Contact customer support to obtain a new license file. Check your system, and disable other TFTP servers.

406

407

408

409

410

411

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

414

Enabled feature set <feature name> is not licensed

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. Disable the feature or contact Support to get an appropriate license.

FibeAir Troubleshooting Guide

38

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

Equipment

101101110

Radio Link

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
Local IDU
101101110...

Equipment
101101110...

Local IDU Interfaces

Modem & IF

to ODU

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

FibeAir Troubleshooting Guide

39

Remote: 155 Mbps Line Interface Wayside Channel


Local IDU
101101110...

Equipment
101101110...

Local IDU Interfaces

Modem & IF

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).
Local Terminal
101101110...

Remote Terminal
Remote IDU Modem & IF Line Interface

Equipment
101101110...

Local IDU

Local ODU

155 MB/s Line Interface Loopback Loop

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.

FibeAir Troubleshooting Guide

40

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 computers address. The following figure shows a typical example of IP addresses and network configuration.
Terminal Site A Site B

Remote Terminal

3xRS-232
192.168.1.1 192.168.1.2 192.168.1.3 192.168.1.17 192.168.1.18 192.168.1.19

Te lne t

3200T GNE A

3200T NE B PPP / Ethernet


192.168.1.33

SNMP CeraView

IP Management Network

1500P NE C PPP / 1500P NE D

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

FibeAir Troubleshooting Guide

41