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: European Headquarters:

Ceragon Networks Ltd. Ceragon Networks (UK) Ltd.
24 Raoul Wallenberg St. 4 Oak Tree Park, Burnt Meadow Road
Tel Aviv 69719, Israel North Moons Moat, Redditch,
Tel: 972-3-645-5733 Worcestershire B98 9NZ, UK
Fax: 972-3-645-5499 Tel: 44-(0)-1527-591900
Email: [email protected] Fax: 44-(0)-1527-591903
www.ceragon.com Email: [email protected]
North American Headquarters: APAC Headquarters:
Ceragon Networks Inc. Ceragon Networks APAC
10 Forest Avenue, (S'pore) Pte Ltd
Paramus, NJ 07652, USA 100 Beach Road
Tel: 1-201-845-6955 #27-01/03 Shaw Towers
Toll Free: 1-877-FIBEAIR Singapore 189702
Fax: 1-201-845-5665 Tel.: 65 65724170
Email: [email protected] 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

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 Clean/repair as required

moisture
Coax cable No cracks or kinks Replace as required
All equipment Dust or dirt Clean as required
Receive level (voltage in Per installation Align/adjust as required

IDU/ODU/RFU, or using records
management)
Torque on antenna Tight mount Adjust as required

mount bolts
FibeAir® Troubleshooting Guide 1

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:
y Power supplies
y Fading (due to heavy rain, new obstacle in path, antenna misalignment)
y External equipment (SONET/SDH, ATM, Fast Ethernet, etc.)
y Indoor Unit (IDU)
y Outdoor Unit (ODU)or Radio Frequency Unit (RFU)
y RF cable between the ODU/RFU and IDU
y Exposure of equipment to severe conditions (high temperature, etc.)
y 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
1) Reconnect line.
1) Line is not
2) Check line
properly
Excessive cables.
excessive- E1/T1 excessive connected.
PDH Major Red BER alarm 3) Check external
ber BER on port #%1 2) External
status equipment.
equipment is
4) Power cycle the
faulty.
system.
loopback- E1/T1 loopback Loopback User configured
Cancel loopback
PDH towards- towards line on Major Red towards line system to
configuration.
line port #%1 alarm status loopback mode.
loopback- E1/T1 loopback Loopback User configured
Cancel loopback
PDH towards- towards radio on Major Red towards radio system to
configuration.
radio port #%1 alarm status loopback mode.
1) Reconnect line.
1) Line is not
2) Check line
properly
E1/T1 loss of No signal is cables.
loss-of- connected.
PDH signal on port Major Red detected on 3) Check external
signal 2) External
#%1 port equipment.
equipment is
4) Power cycle the
faulty.
system.
1) Reconnect line.
1) Line is not
2) Check line
Signal properly
E1/T1 signal cables.
signal- degrade is connected.
PDH degrade on port Minor Yellow 3) Check external
degrade detected on 2) External
#%1 equipment.
port equipment is
4) Power cycle the
faulty.
system.
E1/T1 Unexpected 1) Port is disabled. 1) Enable relevant
unexpected unexpected signal is 2) Line is port.
PDH Warning Yellow
-signal signal on port detected on connected to a 2) Disconnect cable
#%1 port disabled port. from relevant port.
ext-in-
IDU %1 Warning Yellow External Alarm Input ---
alarm
1) FE cable 1) Check connection
Ethernet loss of
eth-loc- Ethernet Loss of disconnected of FE cable.
IDU carrier on port Major Red
alarm Carrier on Port #n 2) Defected 2) Replace FE
#%1
FE cable. cable.
Radio
LOF/EXBER/
Ethernet Tx mute Link ID on
eth-tx- Ethernet TX Mute
IDU override on port Major Red local or Check link
mute-alarm Override
#%1 remote side
(in pipe
application)

LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
1) Cable is not
Gigabit ethernet connected to the 1) Connect cable to
Gigabit loss
IDU gbe-loc-alarm loss of carrier on Major Red port. the port.
of carrier
port #%1 2) Cable is 2) Replace cable.
defected.
Gigabit 1) Check SFP
Gigabit ethernet SFP is not
IDU gbe-sfp-alarm Major Red Ethernet SFP connector.
SFP not inserted inserted
not intact 2) Replace fiber.
Gigabit
Gigabit ethernet
IDU gbe-sfp-tx-alarm Major Red Ethernet SFP SFP malfunction Replace SFP
SFP Tx fault
TX Fault
Radio
GBE Tx mute GBE TX
gbe-tx-mute- LOF/EXBER/Link
IDU override on port Warning Yellow Mute Check link
alarm ID on local or
#%1 Override
remote side
1) Move
Firmware file 1) Firmware file is Management to
file-load-error- Firmware file was not missing. port 2.
IDU Critical Red
alarm load error (%1) successfully 2) System error 2) Download
loaded in power up. firmware file.
3) Reset system.
Firmware file 1) Download
file-not-found- Firmware file not 1) Firmware file is
IDU Critical Red was not firmware file.
alarm found (%1) missing.
found 2) Reset system.
The system's
The alarm file
Alarm file not alarm file
IDU alarms-file Major Red was deleted or is Download alarm file
found was not
corrupted
found
SW error: entity SW failed to SW error during
entity-init-fail-
IDU initialization Major Red properly system Reset system
alarm
failure initialize intialization
IDU is in The external
IDU extreme Turn on external
extreme- extreme cooling/heating
IDU temperature Warning Yellow cooling/heating
temperature temperature system is not
conditions systems.
condition operating.
IDU fan-failure Fan failure Minor Yellow Fan failure Defective fan unit Replace fan unit
general- General HW 1) Reset system.
IDU Major Red HW failure Defected HW
hardware-failure failure %1 2) Replace IDU.
1) The kernel
Backup
Backup kernel is (/boot/uImage) is 1) Re-install the
IDU kernel-backup Minor Yellow kernel is
running corrupted or SW.
running
missing

Low input
Low input Low input to the 1) Check power
IDU low-input-voltage Warning Yellow voltage
voltage system supply voltage.
detected
SW error:
param-set-fail- Parameter
IDU parameter set Warning Yellow SW error Reset system
alarm set failure
failed
1) Inventory
file is
missing.
Inventory file The inventory 2) Inventory 1) Reset system.
corrupted-file-
IDU (%1) is Critical Red file is file was 2) Download
alarm
corrupted corrupted found to be inventory file
corrupt upon
system
power up.
Inventory file Inventory file 1) Download
file-not-found- 1) Inventory file is
IDU (%1) was not Critical Red was not inventory file.
alarm missing.
found found 2) Reset system.
1) Terminate demo
Demo license
demo-license- 1) Demo license license.
IDU Demo license Warning Yellow is used by
alarm activated by user. 2) Activate
customer
operational license.
1) Check that the
code was entered
1) Unit does not
license-violation- License violation License correctly.
IDU Warning Yellow match license
alarm %1 violation 2) Call tech support
features set.
for new license
generation.
Modem file 1) Download
firmware-file- Modem firmware 1) Modem file is
IDU Critical Red was not Modem file.
missing-alarm file not found missing.
found 2) Reset system.
Modem was not Modem was
firmware-load- 1) File is corrupt. 1) Download file.
IDU loaded Critical Red not loaded
error-alarm 2) System failure. 2) Reset system.
successfully successfully
Radio script
fpga-file-currupt- Radio script 1) Download radio
IDU Critical Red LUT is not 1) Faulty file.
alarm (LUT) is corrupt script LUT.
valid
Radio script 1) File was not
fpga-file-not- Radio script 1) Download radio
IDU Critical Red LUT not downloaded to
found-alarm (LUT) not found script.
found system.

Incompatibilit
1) Incompatibility
y between 1) Change RFU.
incompatible- Incompatible between RFU
IDU Critical Red RFU and 2) Change Raido
script-alarm script: %1 %2 and loaded radio
loaded radio script.
script.
script
modem-script- Radio script is Radio script
IDU Critical Red File is corrupt Download file
file-corrupt-alarm corrupt is not valid
modem-script-
Radio script not Radio script
IDU file-not-found- Critical Red File not found Download file
found not found
alarm
mrmc-file-corrupt- MRMC file is MRMC file
alarm corrupt not valid
mrmc-file-not- MRMC file not MRMC file
IDU Critical Red File not found Download file
found-alarm found not found
rfu-file-corrupt- RFU file is RFU file not
alarm corrupt valid
rfu-file-not-found- RFU file not RFU file not
IDU Critical Red File not found Download file
alarm found found
IF loopback 1) User enabled 1) Disable IF
IDU if-loopback-alarm IF loopback Warning Yellow
initiated IF loopback. loopback.
1) Extreme
IF 1) Check
temperature
IDU lock-detect-alarm IF lock detection Critical Red synthesizer installation.
condition.
unlock 2) Reset IDU.
2) HW failure.
1) Check IF cable
and connectors.
Cable
2) Verify that N-
between IDU 1) Cable is not
Type connector
IDU cable-open Cable open Major Red and RFU is connected to IDU
inner pin is not
not properly or RFU.
spliced.
connected
3) Replace IDU.
4) Replace RFU.
1) Check IF cable
and connectors.
2) Verify that N-
There is a
1) Physical short Type connector
IDU cable-short Cable short Major Red short in the IF
at the IF cable. inner pin is not
cable
spliced.
3) Replace IDU.
4) Replace RFU.

Alarm
LED Description Severity Color Alarm Info Probable Cause Corrective Action
Name
1) Check MAID
definitions.
2) Check remote
MEP definitions.
1) Local MEP 3) Check local MEP
error indication. definitions.
Ethenet 2) Remote MEP 4) Run "CFM
Ethenet services
IDU cfm-failure Warning Yellow services error indication. traceroute" to the
failure
failure 3) Remote MEP remote MEP then
loss of perform "CFM ping"
connectivity. to each MP
(Maintenance
Point) in order to
find the broken
point.
1) Cable is not
connected
between 1) Connect
Protection
cable- protection ports. Ethernet cable to
Mate IDU cable cable is not
Protection disconnecte Major Red 2) Cable is protection port of
is not connected properly
d-alarm connected to both IDUs.
connected
wrong port. 2) Replace cable.
3) Cable is
damaged.
1) RFU
Mismatch 1) Change RFU.
configuratio Mate IDU properties are not
between IDU 2) Download
Protection n-mismatch- configuration Major Red identical.
in Protection required radio
alarm mismatch 2) Radio scripts
mode script.
are not identical.
Force switch 1) User
force- Protection force 1) Clear Force
Protection Warning Yellow command command - Force
switch-alarm switch Switch Command.
was issued Protection Switch
SW fault in 1) SW fault in
ipi-xml-file- Protection SW 1) Reset Standby
Protection Warning Yellow Protection synchronization
alarm activity fault unit.
mechanism of databases
Protection
User issued
lockout- Protection Lockout Clear Lockout
Protection Major Red Protection
alarm lockout command command
Lockout
was isused

Alarm
LED Description Severity Color Alarm Info Probable Cause Corrective Action
Name
1) IDU IP
addresses are
identical.
2) IDUs IP subnet
IDU cannot is not identical. 1) Check Protection
Mate IDU
mate-comm- communicate 3) Protection cable connectivity.
Protection communication Major Red
failure-alarm with its mate Cable is not 2) Replace
error
IDU properly Protection cable.
connected.
4) Protection
Cable is
damaged.
1) Check link
1) Fade in the
performance.
link.
radio- 2) Check IF cable,
Radio excessive Excessive 2) Defected IF
Radio excessive- Major Red and replace if
BER BER on radio cable.
ber required.
3) Fault in RFU.
3) Replace RFU.
4) Fault in IDU.
4) Replace IDU.
Link ID Link ID is not the Configure same
radio-link-id- Link ID
Radio Critical Red Mismatch same at both Link ID for both
mismatch mismatch
Alarm sides of link sides of link.
1) Check link
1) Fade in the
performance.
link.
Loss Of 2) Check IF cable,
Radio loss of 2) Defected IF
Radio radio-lof Critical Red Frame on and replace if
frame cable.
radio required.
3) Fault in RFU.
3) Replace RFU.
4) Fault in IDU.
4) Replace IDU.
1) Check link
1) Fade in the
performance.
link.
Signal 2) Check IF cable,
radio-signal- Radio signal 2) Defected IF
Radio Minor Yellow Degrade on and replace if
degrade degrade cable.
radio required.
3) Fault in RFU.
3) Replace RFU.
4) Fault in IDU.
4) Replace IDU.

Remote
remote- Remote
Communicati 1) Fade in the 1) Check link
Remote communicatio communication Major Red
on Failure link. performance.
n-failure failure
Alarm
RFU
incompatible- Incompatible calibration RFU calibration
RFU rfu-tx- RFU TX Major Red tables require tables require Upgrade IDU's SW.
calibration calibration IDC SW IDC SW upgrade.
upgrade
1) Check IF cable
and connectors.
2) Verify that N-
Type connector
1) Defected IF
inner pin is not
cable.
Failure in spliced.
RFU 2) IF cable not
communicatio communicati 3) Replace IDU.
RFU communication Warning Yellow connected
n-failure on between 4) Replace RFU.
failure properly.
IDU and RFU For High Power RF
3) Defected IDU.
Unit:
4) Defected RFU.
1) Check BMA
connector on OCB
2) Check BMA
connector on RFU
delay- RFU delay 1) Reset the IDU /
RX AGC is
RFU calibration- calibration Warning Yellow Defective RFU RFU.
not locked
failure-1 failure 1 2) Replace RFU.
Calibration
Calibration
delay- RFU delay cannot be Enter delay
cannot be
RFU calibration- calibration Warning Yellow completed calibration value
completed due to
failure-2 failure 2 due to notch manually
notch detection
detection
1) Check
installation
RFU 1) Installation
conditions.
extreme-temp- RFU extreme temperature conditions.
RFU Warning Yellow 2) Verify operation
cond temperature is too high or 2) Defective
as per product's
low RFU.
specs.
3) Replace RFU.

1) Defective / 1) Check RFU
non-existent fan connection to BP 2)
drawer. Check that fans are
2) Defective connected to PS
RFU Fan
RFU fan-failure RFU fan failure Warning Yellow RFU-to-fan 3) Replace RFU BP
Failure Alarm
drawer cable
connection. 4) Replace specific
3) Defective fan or fan drawer
RFU. 5)Replace RFU
RFU
hardware-failure- RFU hardware Hardware 1) Defective
RFU Critical Red 1) Replace RFU.
1 failure 1 Failure 1 RFU.
Alarm
RFU
hardware-failure- RFU hardware Hardware 1) Defective
RFU Critical Red 1) Replace RFU.
2 failure 2 Failure 2 RFU.
Alarm
1) Check IF cable
connectors.
1) IF cable
RFU is 2) Verify that N-
connection.
low-if-signal-to- Low IF signal to detecting low Type connector
RFU Major Red 2) Defective
rfu RFU signal from inner pin is not
RFU.
IDU spliced.
3) Defective IDU.
3) Replace IDU.
4) Replace RFU.
1) Check IF cable
and connectors.
2) Verify that N-
Type connector
inner pin is not
spliced.
IDU is not
3) Replace IDU.
No signal from detecting a No RX (140 MHz)
RFU no-signal-from-rfu Major Red 4) Replace RFU.
RFU signal from signal from RFU.
For High Power RF
the RFU
Unit:
Check BMA
connector center
pin is not spliced
both on RFU and
on OCB.

1) Installation 1) Check
RFU PA RFU PA
pa-extreme-temp- conditions. installation
RFU extreme Warning Yellow Extreme
cond 2) Defective conditions.
temperature Temperature
RFU. 2) Replace RFU
1) Defective IF
1) Replace IF
RFU Power cable/connector.
RFU power cable/connector.
RFU power-failure-12v Major Red Failure (12v) 2) Defective
failure (12v) 2) Replace RFU.
Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
power-failure- RFU power cable/connector.
RFU Major Red Failure (1.5v) 2) Defective
1point5 failure (1.5v) 2) Replace RFU.
Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
RFU power-failure-24v Major Red Failure (24v) 2) Defective
failure (24v) 2) Replace RFU.
Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
RFU power-failure-6v Critical Red Failure (6v 2) Defective
failure (6v pro) 2) Replace RFU.
pro) Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
power-failure-6v- RFU power cable/connector.
RFU Major Red Failure (6v 2) Defective
sw failure (6v SW) 2) Replace RFU.
SW) Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
power-failure- RFU power cable/connector.
RFU Major Red Failure (6v 2) Defective
minus-5v failure (-5v) 2) Replace RFU.
pro) Alarm RFU.
3) Replace IDU.
3) Defective IDU.
1) Defective IF
1) Replace IF
RFU power-failure-vd Critical Red Failure (Vd) 2) Defective
failure (Vd) 2) Replace RFU.
Alarm RFU.
3) Replace IDU.
3) Defective IDU.
RFU
rfu-loopback- 1) Disable RFU
RFU RFU loopback Major Red loopback 1) User action.
active loopback.
Alarm

At least one of
rfu-power-supply- RFU power RFU power
RFU Major Red the PSU voltages 1) Replace RFU.
failure supply failure supply failure
is too low.
RSL is very low
1) Check antenna
(typically below -
alignment & link
80 dBm), link is
planning.
down.
2) Check link
RFU RX For RFU-C:
rx-level-out-of- Rx level out of settings (TX power,
RFU Warning Yellow Level Out of RSL is too Low
range range TX freq).
Range (typically below -
3) Check antenna
83dBm) or
connections.
RSL is too High
4) Replace
(typically above -
local/remote RFU.
26dBm).
1) Check that the
fault is not due to
rain/multi-path
fading or lack of
LOS.
1) Improper
2) Check link
RFU Rx level RFU Rx installation.
rx-level-path1-out- settings (TX power,
RFU path1 out of Warning Yellow Level Path1 2) Fading event.
of-range TX freq).
range Out of Range 3) Defective
3) Check anttena
RFU.
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.
1) Improper
2) Check link
RFU Rx level RFU Rx installation.
rx-level-path2-out- settings (TX power,
RFU path2 out of Warning Yellow Level Path2 2) Fading event.
of-range TX freq).
range Out of Range 3) Defective
3) Check anttena
RFU.
alignment.
4) Check antenna
connections
5) Replace
local/remote RFU.

1) Defective
RFU RFU. 1) Replace XPIC
synthesizer-1- Synthesizer 1
RFU Major Red synthesizer is 2) Defective cable.
unlocked unlocked
unlocked XPIC cable 2) Replace RFU.
connection.
1) Defective
RFU Major Red synthersizer 2) Defective cable.
unlocked unlocked
is unlocked XPIC cable 2) Replace RFU.
connection.
1) Defective
RFU Major Red synthesizer is 2) Defective cable.
unlocked unlocked
unlocked XPIC cable 2) Replace RFU.
connection.
One of the 1) Replace RFU.
One of the RFU
synthesizer- Synthesizer RFU 2) In XPIC mode,
RFU Major Red synthesizers is
unlocked unlocked Synthesizers replace mate RFU
unlocked.
is Unlocked as well.
1) Defective RFU
1) Replace RFU.
RFU TX (the RFU cannot
tx-level-out-of- Tx level out of 2) Intermediate
RFU Minor Yellow Level Out of transmit the
range range solution - reduce
Range requested TX
TX power.
power)
RFU Transmitter Unmute the RFU
RFU tx-mute Tx mute Warning Yellow RFU TX Mute
muted by user. transmitter.
IDC's SW
IDU SW does
doesn't IDC's SW doesn't
RFU unknown-rfu-type not support this Major Red Upgrade IDC SW.
support the support the RFU.
type of RFU
RFU

LED Indications for other FibeAir Systems
Color
LED Description
Red Yello Green
w
PWR X X Red - power supply problem

(Power)
LINE X X X Red - no input to main channel / high BER
Yellow - JO mismatch
LOF (Loss X X Red - radio did not recognize information
of Frame) frame (radio link problem/radio LOF)
BER (Bit X X X Red - radio BER higher than radio
Error Ratio) 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 X X Red - loopback is active
(Loopback)
STBY X X Yellow - Protected configuration. The unit
(Standby) 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 X X X Red - no link / remote unit problem (red
(Remote LED is lit in the remote unit)
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:
y External equipment Tx is connected to FibeAir Rx.
y External equipment Rx is connected to FibeAir Tx.
y Both external equipment and FibeAir are using the same interface (single mode, multi-mode).
y 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

1) Check the Block Radio command
One of the system elements
Insufficient System status on the protection
does not support XPIC.
0 Configuration for Full configuration.
Or, the system is missing one
XPIC Support 2) Check the remote radio alarms
of the needed elements.
and solve the radio fault accordingly
1) Check the Block Radio command
status on the protection
ODU 5/8/12/-12V Power does not support XPIC.
10 configuration.
Supply Failure Or, the system is missing one
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
Synthesizer #1/2/3 One of the RFU synthisizers that the
11
Unlocked is unlocked. RFU is taking the synch from the
mate RFU.
In this case, check if alarm persists
in non-XPIC configuration.
RFU transmitter muted by
12 Tx Mute On/Off Unmute the RFU transmitter.
user
1) Replace RFU.
The RFU cannot transmit the
12 Tx Level Out of Range 2) Intermediate solution - reduce TX
requested Tx power.
power.

RSL is very low (typically
1) Check antennas alignment & link
below -80 dBm), link is down.
planning.
For RFU-C:
2) Check link settings (TX power,TX
13 Rx Level Out of Range RSL is too Low (typically
freq).
below -83dBm) or
3) Check antenna connections.
RSL is too High (typically
4) Replace local/remote RFU.
above -26dBm).
ODU Temperature Out RFU temperature too 1) Check installation conditions.
14
of Range high/low. 2) Replace RFU.
Left/Right cables swap in
XPIC configuration. If
???Drawer ID Mismatch???
1) Verify correct cable connection.
(see above) alarm is
15 XPIC Cable Swap Recommended connection is V to
identified in both drawers, the
Right drawer and H to Left drawer
IF (coax) cables between the
drawers and ODUs on one
end are swapped.
1) Verify if the Power Input card
exists in the subrack.
2) Check if Power Input connected
to -48 VDC supply.
Subrack redundant power
15 Power Input #2 is Down 3) Check -48 VDC supply to the
feed failure.
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.
Subrack redundant power
15 Power Input #1 is Down 3) Check -48 VDC supply to the
feed failure.
subrack.
4) Replace Power Input card if
problem still exists.
5) Disable Power Input
1) Check -48 VDC supply to the
IDU 5/8/3.3/-5V Power Failure in an IDU power
15 IDU.
Supply Failure supply.
2) Replace IDU.
15 Drawer Power On/Off Drawer power on/off.
Board #1 - MUX card. Board
#2 - Modem card. This alarm
Drawer Internal Power 1) Switch off/on IDM.
15 may also be generated if a
Failure (Board #2) 2) Replace IDM.
drawer in Internal Protection
was switched off.
Drawer Internal Power Drawer Internal Power Failure
15
Failure (Board #1) (Board #1)
1) If extended mode is not in use,
configure all IDCs in the subrack as
"1 subrack out of 1".
Problem with extension cable
Extension Link 2) If extended mode is in use, verify
16 or the connection between
Communication Failure that the other subrack is configured
the two subracks.
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
16 Cable Short IDM-RFU cable short. pin is not spliced.
3) Replace IDM.
4) Replace RFU.
2) Check ODU's N-type connector
inner pin is not spliced (if
16 Cable Open/Short IDU-ODU cable open/short.
yes, replace ODU).
3) Replace IDU.
4) Replace ODU.
2) Check N-type connector inner
16 Cable Open IDM-RFU cable open. pin is not spliced.
3) Replace IDM.
4) Replace RFU.
Multi-Rate Multi-Constellation
MRMC=???value??? configuration script for the 1) Download the Modem script to
17
Script File is Missing specified capacity/modulation the IDC and reset the IDM.
is missing in the IDC.
Drawer Internal
Drawer hardware intact ok /
17 Hardware Intact/Failure 1) In case of failure, replace IDM.
failure (Mux)
Board#1
IDU Temperature Out of IDU Temperature Out of 1) Check installation conditions.
18
Range Range 2) Replace IDM.
18 Fan Failure Fan Failure 1) Replace fan.
XC Internal Loopback on XC board Internal port
19 1) Disable loopback
Line #5 loopback
Line #4 loopback
Line #3 loopback
Line #2 loopback
Line #1 loopback
Wayside Line loopback
Wayside Channel
19 applied by user in internal Disable Wayside line loopback
Loopback
protection
Wayside Channel Wayside Left Line loopback
19 Disable Wayside line loopback
Loopback applied by user
ODU Internal Loopback RFU loopback applied by
19 Disable loopback
(Not) Active user
Internal Loopback on
19 Internal loopback on Fiber Disable loopback
Fiber #n
IDU Remote Loopback
(Not) Active ?10;IDU
Line Loopback (Not)
Active?10;E1\T1\E3\DS3
19 Loopback applied by user Disable loopback
#n Internal Loopback
(Not) Active?10;E1\T1\
E3\DS3 #n External
Loopback (Not) Active
IDU Local Loopback IDU IF loopback applied by
19 Disable loopback
(Not) Active user

Gigabit Ethernet Internal Gigabit Ethernet Internal Disable Gigabit Ethernet Internal
19
Loopback Loopback applied by user. Loopback
External Loopback on IDU Line loopback applied by
Fiber #n user
E1\T1 Internal Loopback IDU Line loopback applied by
on Port #n user
E1\T1 External
19 E1/T1 External loopback 1) Disable loopback
Loopback on Port #n
1) Verify link is up and no errors
Remote Communication No communication between over the link.
20
Failure the IDUs over the link. 2) Check in-band management
configuration.
PRBS Test is Running
21 PRBS test started. Disable PRBS test.
on Radio
Lockout or Force Switch to
Link Group #1 N+1
Protecting Link Group
21 Protection Fault: Locked Release maintenance command.
maintenance command
by User
activated.
22 Trib RS: LOF Trib RS: LOF
1) Check that the fault is not due to
other alarms that can lead to LOF.
Radio RS: LOF (SDH) 2) Check link settings (TX power,
Loss Of Frame alarm on the
22 Radio Section: LOF TX freq).
radio, link is down
(Sonet) 3) Verify no interference.
4) Use loopbacks to identify source.
5) Replace IDMs/ODUs
2) Check link settings (TX power,
TX freq).
22 Radio RS: LOF Radio RS: LOF (ADM)
3) Verify no interference.
4) Use loopbacks to identify
problem source.
5) Replace IDMs.
N+1 Link Group protection 1) Check Protecting Radio module
Link Group #1 N+1 degraded due to Loss Of is powered on and operates
22 Protection Fault: Frame or Loss Of Signal properly.
Protecting Radio Failure alarm on the radio port 2) Replace faulty module.
detected by XC board. 3) see Radio RS: LOF (SDH)
1) Check line input.
2) Check fibers/cables.
Fiber RS: LOF (SDH) 3) Verify end equipment transmits
22 Fiber Section: LOF properly.
line input.
(Sonet) 4) Use line loopbacks to confirm
input/IDU is ok.
5) Replace IDM.
Fiber RS: LOF (SDH) 3) Verify end equipment transmits
22 Fiber Section: LOF properly.
line input
(Sonet) 4) Use line loopbacks to confirm
input/IDU is ok.
5) Replace IDU.

freq).
22 Fiber RS: LOF Fiber RS: LOF (ADM)
problem source.
5) Replace IDMs
23 Trib RS: LOS Trib RS: LOS
3) Verify that end equipment
Loss of Signal on Fiber Loss Of Signal alarm on the
23 transmits properly.
#n line input
4) Use line loopbacks to confirm
that input/IDU is ok.
5) Replace IDM.
2) Check fiber.
Gigabit Ethernet Loss of Gigabit Ethernet Loss of
23 3) Verify end equipment transmits
Signal Signal
properly.
4) Replace IDM.
Fiber RS: LOS
3) Verify end equipment transmits
or?10;E1\T1\E3\DS3 #n Loss Of Signal alarm on the
23 properly.
Loss of Signal?10;Fiber line input
RS: LOS
input/IDU is ok.
5) Replace IDU.
2) Check cable.
Fast Ethernet Loss of
23 Fast Ethernet Loss of Carrier 3) Verify end equipment transmits
Carrier on Port #n
properly.
4) Replace IDM.
2) Check cable.
Fast Eth. #01/02 Loss of
23 Fast Ethernet Loss of Carrier 3) Verify end equipment transmits
Carrier
properly.
4) Replace IDU.
E1\T1 Loss of Signal on
23 E1\T1 Loss of Signal properly.
Port #n
input/IDU is ok.
5) Replace IDM.
24 Trib RS: TIM Trib RS: TIM
24 Trib LP #n: TIM Trib LP #n: TIM
24 Trib HP: TIM Trib HP: TIM
Trace Identifier Trace Identifier Mismatch Verify J0 settings in the IDU and in
24
Mismatch on Fiber #n alarm (J0 mismatch). 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 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
Trib LP #n Excessive
25 Trib LP #n Excessive BER
BER
25 Trib HP: Excessive BER Trib HP: Excessive BER
Radio RS: Excessive Radio RS: Excessive BER
25
BER (Regenerator)
25
BER (Regenerator)
25
BER (ADM)
Radio MS: Excessive
25 Radio MS: Excessive BER
BER
Radio LP #n: Excessive
25 Radio LP: Excessive BER
BER
Radio HP: Excessive
25 Radio HP: Excessive BER
BER
Fiber RS: Excessive Fiber RS: Excessive BER
25
BER (Regenerator)
25
BER (Regenerator)
25
BER (ADM)
Fiber MS: Excessive
25 Fiber MS: Excessive BER
BER
Fiber LP #n Excessive
25 Fiber LP #n Excessive BER
BER
Fiber HP: Excessive
25 Fiber HP: Excessive BER
BER
Excessive BER on Major radio Excessive BER freq).
25
Radio #n alarm 3) Verify no interference.
problem source.
Excessive BER on Fiber Major line Excessive BER
25 properly.
#n alarm
input/IDU is ok.
5) Replace IDM.
E1\T1\E3\DS3 #n
25 E3/DS3 Excessive BER
Excessive BER
E1\T1\E3\DS3 #n
25 E1/T1 Excessive BER
Excessive BER

2) Check cables.
E1\T1 Excessive BER Major Excessive BER alarm
25 properly.
on Port #n on E1/T1 port
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
Trib LP #n Signal
26 Trib LP #n Signal Degrade
Degrade
26 Trib HP: Signal Degrade Trib HP: Signal Degrade
Signal Degrade on freq).
26 Minor radio BER alarm
Radio #n 3) Verify no interference.
problem source.
Signal Degrade on Fiber
26 Minor line SD BER alarm properly.
#n
that input/IDU is ok.
5) Replace IDM.
Radio RS: Signal
26 Radio RS: Signal Degrade
Degrade
Radio RS: Signal
Degrade
Radio RS: Signal
Degrade
Radio MS: Signal
26 Radio HP: Unequipped
Degrade
Radio LP #n: Signal
26 Radio LP #n: Signal Degrade
Degrade
Radio HP: Signal
26 Radio HP: Signal Degrade
Degrade
Fiber RS: Signal Fiber RS: Signal Degrade
26
Degrade (ADM)
Fiber RS: Signal
26 Fiber RS: Signal Degrade
Degrade
Fiber RS: Signal
26 Minor line BER alarm properly.
Degrade
input/IDU is ok.
5) Replace IDU.
Fiber MS: Signal
26 Fiber MS: Signal Degrade
Degrade
Fiber LP #n Signal
26 Fiber LP #n Signal Degrade
Degrade
Fiber HP: Signal
26 Fiber HP: Signal Degrade
Degrade

E1\T1\E3\DS3 #n Signal
26 E3DS3 Signal Degrade
Degrade
E1\T1\E3\DS3 #n Signal
26 E3DS3 Signal Degrade
Degrade
2) Check cables.
E1\T1 Signal Degrade Minor BER alarm on E1/T1
26 properly.
on Port #n port
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
Trib RS: Unexpected
28 Trib RS: Excessive BER
Signal
1) Enable GbE port, disable GbE
Gigabit Ethernet GbE port is disabled but GbE
28 port of the source, or disconnect the
Unexpected Signal data is detected.
fiber
Fiber RS: Unexpected Unexpected signal on the line
1) Enable line port or disconnect
28 ?10;E1\T1\E3\DS3 #n input. Port disabled but line is
line
Unexpected Signal connected.
Fast Ethernet
Fast Ethernet Unexpected
28 Unexpected Signal on
Signal on Port #n
Port #n
30 Trib LP #n: LOP Trib LP #n: LOP
30 Trib HP: LOP Trib HP: LOP
Radio LP: Loss of pointer
30 Radio LP #n: LOP
(LOP) alarm occurs.
Radio HP: Loss of pointer
30 Radio HP: LOP
(LOP) alarm occurs.
Fiber LP: Loss of pointer
30 Fiber LP #n: LOP
(LOP) alarm occurs.
Fiber HP: Loss of pointer
30 Fiber HP: LOP
(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
Radio MS: Remote Defect
31 Radio MS: RDI
Identifier signal (RDI) occurs.
Radio LP: Remote Defect
31 Radio LP #n: RDI
Radio HP: Remote Defect
31 Radio HP: RDI
Fiber MS: Remote Defect
31 Fiber MS: RDI

Fiber LP: Remote Defect
31 Fiber LP #n: RDI
Fiber HP: Remote Defect
31 Fiber HP: RDI
32 Trib LP #n: PLM Trib LP #n: PLM
32 Trib HP: PLM Trib HP: PLM
Radio LP: Payload Label
32 Radio LP #n: PLM
Mismatch (PLM) occurs.
Radio HP: Payload Label
32 Radio HP: PLM
Fiber LP: Payload Label
32 Fiber LP #n: PLM
Fiber HP: Payload Label
32 Fiber HP: PLM
33 Trib LP #n: Unequipped Trib LP #n: Unequipped
33 Trib HP: Unequipped Trib HP: Unequipped
Radio LP #n:
33 Radio LP: Unequipped
Unequipped
33 Radio HP: Unequipped Radio HP: Unequipped
Fiber LP #n:
33 Fiber LP: Unequipped
Unequipped
33 Fiber HP: Unequipped Fiber HP: Unequipped
External alarm input #1
34 External Alarm configured and triggered by
user.
user.
user.
user.
user.
user.
user.
user.

1) Check that IDC #n is power up

and finished initialization.
2) Check & configure both IDCs
Internal IDC to IDC
with proper system configuration:
communication failure
42 XPIC Cable Swap System Type, Subrack#, Subrack
between modules requied for
IP Base Address, Link Group
Link Group protection service.
Topology.
3) Check for Hardware fault:
Subrack Auxiliary module
XC <Type> FPGA File is XC firmware file is missing in 1) Download XC firmware file of the
42
Missing the 2-floor IDC. required type and reset the IDC.
Wayside Firmware File Wayside firmware file is 1) Download Wayside firmware file
42
is Missing missing in the IDC. to the IDC and reset the IDC.
Subrack Auxiliary firmware
Subrack Auxiliary FPGA 1) Download Subrack Auxiliary
42 file is missing in the 2-floor
File is Missing firmware file and reset the IDC.
IDC.
Secondary Clock Source Secondary Clock Source
42
Failure Failure
1) Check if Radio module is
Radio module pertained to
Radio Card #n Powered inserted properly in the subrack and
42 Link Protection group is
Down is powered on. Replace module if
powered down or extracted.
faulty.
Primary Clock Source
42 Primary Clock Source Failure
Failure
MUX Firmware File is A Mux FW file is missing from Load the required FW file, and reset
42
Missing the system. system.
Modem Firmware File is A Modem FW file is missing Load the required FW file, and reset
42
Missing from the system. system.
1) Verify Protection Radio link is up
and, no errors over the link.
2) Check that remote IDU is
Link Group #1 N+1
N+1 Link Group protection properly configured for N+1 Link
Protection Fault: XC
42 degraded due to peer XC Group protection.
Peer Communication
communication fault. 3) Check that remote IDU has
Failure
properly operational XC board.
4) Check that Protection Radio link
terminates
Link Group #1 N+1 1) Check if XC module is powered
N+1 Link Group protection
Protection Fault: on and no other alarm related to XC
42 degraded due to XC card
Protecting Radio Failure is active.
fault.
XC Card Fault 2) Replace XC module.
Link Group #1 N+1 properly configured with N+1 Link
Protection Fault: Local- Group topology.
42 degraded due to Local-
Remote Protection 2) Check that remote IDU has all
Remote Protection Mismatch.
Mismatch N+1 Link Group protection related
line modules operational.

1) Check if the card is inserted
properly in the subrack.
Line module pertained to Link
Line Card #n Powered 2) Check if own or redundant power
42 Protection group is powered
Down supply / Radio module
down or extracted.
(in drawer #1) is powered on.
Replace module if faulty.
1) Check if the card is inserted
properly in the subrack.
Line module in carrrier #1 of
Line Card #1 Powered 2) Check if own or redundant power
42 the Link Protection group is
Down supply / Radio module is powered
powered down or extracted.
on.
3) Replace module if faulty.
The MRMC loaded to the
system is not supported by
the license, or the ACM Load another MRMC with bit rate
42 License Fault
function is enabled while not supported by the license
supported by the license.
The link is not operative.
1) Check ODU connection to the
IDU.
IDU-ODU Inner IDC cannot communicate with 3) Check ODU's N-type connector
42
Communication Failure ODC card. inner pin is not spliced (if yes,
replace ODU).
4) Replace ODU.
5) Replace IDU.
1) Reset IDU.
IDC cannot communicate with
IDU-MUX Inner 2) Verify correct SW version.
42 MUX card, MUX card upload
Communication Failure 3) Verify correct interfaces.
failure.
4) Replace IDU.
1) Try SW Reset affected module /
Upper IDM Board (MUX or IDM.
General Hardware Fault
42 XC) EEPROM inventory 2) Power cycle or re-insert affected
#9
information CRC error module / IDM.
3) Replace the module.
Upper IDM Board (MUX or IDM.
42 XC) EEPROM read access 2) Power cycle or re-insert affected
#8
error module / IDM.
1) Download correct Subrack
Auxiliary FW file to 2-floor IDC, and
then extract and re-insert Subrack
General Hardware Fault FPGA load failure - Subrack
42 Auxiliary board
#7 Auxiliary board.
2) Replace Subrack Auxiliary
module.
3) Replace 2-floor IDC.
1) Download correct
General Hardware Fault SW/FW/Configuration scripts.
42 FPGA load failure - Modem
#7 2) Replace IDM.
3) Replace IDC.
1) Download correct
42 FPGA load failure - Mux
#6 2) Replace IDM.
3) Replace IDC.

1) Download correct
42 DAC failure
#5 2) Replace IDM.
3) Replace IDC.
1) Download correct
42 IDU XPIC HW fault
#4 2) Replace IDM.
3) Replace IDC.
1) Download correct
42 XO failure - Mux board
#3 2) Replace IDM.
3) Replace IDC.
1) Download correct
42 XO failure - Modem board
#2 2) Replace IDM.
3) Replace IDC.
General Hardware Fault Wrong card type detected in 1) Replace Subrack Auxiliary
42
#11 Subrack Auxiliary slot. module.
Lower IDM Board (Modem or IDM.
42 XC) EEPROM inventory 2) Power cycle or re-insert affected
#11
information CRC error module / IDM.
1) Extract and re-insert Subrack
General Hardware Fault Subrack Auxiliary EEPROM Auxiliary module.
42
#10 checksum failure. 2) Replace Subrack Auxiliary
module.
Lower IDM Board (Modem or IDM.
42 XC) EEPROM read access 2) Power cycle or re-insert affected
#10
error module / IDM.
1) Download correct
SW/FW/Configuration scripts.
42 IDU Synthesizer lock 2) Power IDM off/on.
#1
3) Replace IDM.
3) Replace IDC.
1) Disable EOW chaining if not
required.
2) Check EOW chaining line input
on both subracks.
No signal detected on
EOW chaining Loss of 3) Check / fix EOW chaining
42 Subrack Auxiliary EOW
Signal configuration on mate subrack.
chaining input.
Verify that EOW is defined on at
least one working link on mate
subrack.
4) Replace EOW chaining


pin is not spliced.
Drawer-RFU No communication between 3) Replace IDM.
42
Communication Failure IDM and RFU. 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.
Drawer Internal Power 2) Extract and re-insert Subrack
42 Internal Power failure.
Failure (Board #2) Auxiliary module.
module.
Drawer Internal
42 IDU IF loop applied by user 1) Disable loopback
Loopback
Copy IDC Configuration IDC copy configuration by
42
to Mate user in external protection
Copy Carrier Carrier configuration copied
42 Configuration To Mate between two IDMs in
Failed/Succedded protected configuration
42 Clock Unit Unlocked Clock Unit Unlocked
42 Clock Unit Out of Range Clock Unit Out of Range
1) Check Subrack Auxiliary module
Subrack Auxiliary module is properly inserted.
42 Auxiliary Card Fault #01
failed or extracted. 2) Replace Subrack Auxiliary
module.
The ACM lookup table file Load the lookup table file of the
ACM Configuration File
42 cannot be found on the relevant release version or load the
is Missing
system disk. SFD file.
TFTP IDU/MUX/ODU
Software download operation
verxxx Download
43 status (from user's PC to
Succeeded/
IDC)
Canceled/Failed
IDU Configuration
Download Configuration download
43
Succeeded/Error/Cancel status, initiated by user
led/Failed/Invalid File
Boot/IDC/MUX/ODU/Mo
dem Script/Modem/
Wayside/Mrmc File download status. Initiated
43
table/RFU FPGA File by user.
Download Succeeded
<file name>
Firmware upload operation
44 RFU FW Upload Failed
status (from IDC to ODC)
Firmware upload operation
44 RFU FW Upload Error
RFU FW Upload Firmware upload operation
44
Canceled status (from IDC to ODC)
Software upload operation
44 ODU SW Upload Failed

Software upload operation
44 ODU SW Upload Error
ODU SW Upload Software upload operation
44
Canceled status (from IDC to ODC)
MUX/ODU Internal MUX/ODU Internal Download
44 Download Succeeded/ Succeeded/Canceled/Failed/
Canceled/Failed/Error Error
1) Check the mismatch
At least one configuration configuration in the alarms log.
User Configuration
parameter which should be 2) Configure the relevant IDC with
46 Mismatch between IDC
equal in these two IDCs has the correct values for mismatch
# and IDC #
different values. resolution, and wait one minute for
the mismatch alarm to clear.
1) Check and compare
User Configuration Configuration in the IDC is
configuration
46 Mismatch (<param different than in the drawers
2) See User Configuration
name>) S=xx, D=xx or Auxiliary channel board
Mismatch Alarm
configuration in the alarms log.
User Configuration Mismatch configuration
2) Use "Copy to IDC" command to
46 Mismatch (<param between the IDC Database
copy the configuration from XC to
name>) S=xx, D=xx and the drawer.
IDC, or "Copy to Drawer" for
mismatch resolution.
At least one Link Group 1) Check the mismatch
configuration parameter in the configuration in the alarms log.
User Configuration IDC Database is different 2) Use "Copy to IDC" command to
46
Mismatch than the actual configuration copy the configuration
in the XC. Raised only after from XC to IDC, or "Copy to
IDC hotswap or S/W reset. Drawer" for mismatch resolution.
At least one drawer 1) Check the mismatch

configuration parameter in configuration in the alarms log.
the 2) Use "Copy to IDC" command to
User Configuration IDC Database is different copy the configuration from the
46
Mismatch than the actual configuration drawer to the IDC, or "Copy to
in the drawers. Drawer", eliminating the mismatch.
Raised only after IDC However, "copy to drawer"
hotswap or S/W reset. command does not copy the protec
At least one IDC configuration

parameter in the IDC Data
configuration in the alarms log.
Base (XPIC for example) is
2) Use "Copy drawer to IDC"
User Configuration different than the
46 command to copy the
Mismatch configuration in the drawers
XPIC/protection configuration from
or Auxiliary channels.
the drawer to the IDC (without
Raised only after IDC
reset). This will end the mismatch.
hotswap / software reset.
Internal system mismatch
46 Protection Mismatch regarding the state of the Reset IDM
radio - Mute/Unmute
Mate Configuration Mismatch in the internal
configuration
46 Mismatch (<param protection configuration
2) See mate Configuration
name>) M=xx, L=xx between the drawers.
Mismatch Alarm

Mate Configuration Mismatch configuration
configuration
46 Mismatch (<param between local IDC Database
2) See mate Configuration
name>) M=xx, L=xx and mate IDC database
Mismatch Alarm
Configuartion mismatch
Mate Configuration configuration.
46 between two IDCs in External
Mismatch 2) Perform "copy to mate" from the
Protection configuration.
IDC with the correct configuration
Configuartion mismatch
configuration.
Mate Configuration between two drawers in
46 2) Perform "copy to mate" from the
Mismatch External Protection
drawer with the correct
configuration.
configuration
Link ID Mismatch on Link ID is not identical on Set identical Link ID on both ends
46
Radio #n both ends of the link. of the link.
46 Link ID Mismatch Link ID Mismatch
Link ID is not identical on 1) Set identical Link ID on both
46 Link ID Mismatch
both ends of the link. ends of the link.
Link ID is not identical on 1) Set identical Link ID on both
46 Link ID Mismatch
both ends of the link. ends of the link.
Different configuration
IDU Hitless Remote 1) Check and compare
46 between the IDUs on both
Config Mismatch configurations
sides of the link
Different configuration
IDU Hitless Mate Config 1) Check and compare
46 between the IDUs on the
Mismatch configurations
same side of the link
IDC MAC device failure - 1) Download correct
46 loading with default MAC SW/FW/Configuration scripts.
#4
address 2) Replace IDC.
WSC board configuration
1) Download correct
General Hardware Fault failure - Can't detect board
46 SW/FW/Configuration scripts.
#3 configuration (can't read from
2) Replace IDC.
E2PROM)
WSC board configuration
1) Download correct
General Hardware Fault failure - Error during reading
#2 board configuration - CRC
2) Replace IDC.
error
1) Download correct
General Hardware Fault FPGA load failure - Wayside
#1 Channel
2) Replace IDC.
Settings not supported by 1) Check if HW and SW support the
46 General Cfg Mismatch
HW/SW. requested configuration
Drawer #1 receives signal of
the mate drawer (#2) across 1) Check link connections and
the XPIC link. Problem in the settings.
Drawer ID Mismatch in
46 XPIC link (such as failure in 2) Check XPIC configuration.
Protecting Carrier
one of the transmitters or 3) Verify that both links are up.
insufficient XPI), detected by 4) Check XPI
the XC board.
Drawer receives signal of the
1) Check link connections and
other drawer across the XPIC
settings.
link. Indicates problem in the
46 Drawer ID Mismatch 2) Check XPIC configuration.
XPIC link (such as failure in
3) Verify that both links are up.
one of the transmitters or
4) Check XPI
insufficient XPI)

Incomapitibility alarm
between link components.
Device Incompatible
46 Typically refers to mixture of 1) Check link components
Alarm (#103)
standard and "I" components
in the link
1) Check and correct configuration:
Use "Copy IDC to AUX" to copy the
Auxiliary Channel User Incorrect Auxiliary channel Auxiliary channel configuration
46
Configuration Mismatch configuration to the IDC, or "Copy AUX to IDC" to
copy the Auxiliary channel
configuration to the AUX
SW Mode Changed to
Slave/Master?10;Chang Change Master/Slave
47
e Remote Transmitter command
Request Sent
Protection System configured for
1) Check configuration.
47 Internal/External Mate protection without mate
2) Check Mate connected
Not Exist connected
Protection External Protection switch by external
47
Alarm Switch alarm
1) Download correct
Different faults indicate
Protection Change to SW/FW/Configuration scripts.
47 hardware failure on the
Standby 2) Replace IDM.
drawer
3) Replace IDC.
Hitless Protection Hitless is configred without 1) Enable protection or disable
47
Configuration Mismatch protection hitless
Change Remote Command was sent to
Transmitter Request remote end to switch when
47 Sent - both local receivers identify
SDBER/EXBER/LOF/BE Rx fault (for example, remote
R active transmitter fails)
For External Protection 1) Check that cable is connected
Protection
configuration. properly.
48 Communication Error on
Protection cable is connected 2) Replace protection cable.
Cable
but errors detected. 3) Replace IDCs
Protection Cable Protection Cable 1) Connect Protection Cable.
48
Disconnected Disconnected 2) Replace cable.
Protection Cable
Problem with protection cable
Disconnect/Error/Power 1) Replace cable.
48 or the connection between
Error/Problem?10;Maste 2) Replace IDUs
the Master/Slave IDUs
r-Slave Disconnect
49 Heart Beat (Trap Only) Heart Beat (Trap Only)
50 Trib HP: LOM Trib HP: LOM
Radio HP: Loss of Multi-
50 Radio HP: LOM
frame (LOM) alarm occurs.
Fiber HP: Loss of Multi-frame
50 Fiber HP: LOM
(LOM) alarm occurs.
Hitless Switch Locked to Hitless Switch Locked to Self
51
Self Radio By User Radio by User
Hitless switching disabled by
Hitless Switch Locked to
51 user and locked for one of the 1) Disable Hitless Lockout
Right Radio By User
drawers.

Hitless Switch Locked to Hitless Switch Locked to
51
Mate/Self Radio By User Mate/Self Radio by User
Hitless switching disabled by
Hitless Switch Locked to
51 user and locked for one of the 1) Disable Hitless Lockout
Left Radio By User
drawers.
Hitless Self/Mate Hitless Self/Mate Receiver in
51
Receiver in user user
Not a real alarm since receiver
Hitless Left/Right Left/Right receiver is used for
51 switching is likely to happen during
Receiver in Use processing data
multipath fading.
1) Hitless cable disconnected.
Hitless protection is not
Hitless Functionality 2) Mate IDU is off.
51 available. The link will fail in
Failure 3) Mate IDU has an alarm that
case of fade.
prevents it from receiving data.
Unused Radio Receiver Hitless Self Radio Receiver freq).
52
LOF LOF 3) Verify no interference.
problem source.
Own Radio BBLOF on Hitless Self Radio Receiver freq).
52
Radio #n LOF 3) Verify no interference.
problem source.
Same as Radio LOF alarm:
Permanent Radio LOF in the
receiver (raised after 10
consecutive seconds of radio
Loss of Frame on Loss Of Frame).
52 freq).
Unused Left/Right Radio Implies a permanent problem,
unlike fading due to multipath
condition, which is
problem source.
intermittent in nature.
Hitless Self Radio Hitless Self Radio Receiver
52
Receiver LOF LOF
Hitless Cable
53 Hitless cable disconnected. Connect hitless cable.
Disconnect
In-Band Radio PPP Link In-band connection over the
Disconnect?10;In-Band line (STM-1/OC-3 or PPPoE) 1) Check the line connection.
57
Line PPP Link or over the radio was 2) Check in-band configuration.
Disconnect disconnected.
2) Verify user-end equipment.
3) Check / replace connecting
Wayside Channel Loss of
Wayside Channel Loss cable.
58 Signal/Carrier in internal
of Signal/Carrier 4) Replace IDC module.
protection
In case of N+1 Trunk Radio:
module.

Wayside Channel Loss Wayside Right Channel Loss cable.
58
of Signal/Carrier of Signal/Carrier 4) Replace IDC module.
module.
Wayside Channel Loss Wayside Left Channel Loss of cable.
58
of Signal/Carrier Signal/Carrier 4) Replace IDC module.
module.
2) Verify user-end Ethernet
equipment.
User Channel Ethernet User Channel Loss of Carrier
58 cable.
Loss of Carrier in internal protection
4) Replace IDC module.
module.
equipment.
User Channel Ethernet User Right Channel Loss of
58 cable.
Loss of Carrier Carrier
module.
equipment.
User Channel Ethernet User Left Channel Loss of
58 cable.
Loss of Carrier Carrier
module.
ODU-2-ODU Cable 1) Check cable.
59 ODU-2-ODU Cable Open
Open 2) Replace cable.
1) Check IF cable and connectors
pin is not spliced.
3) Replace IDM.
No Rx (140 MHz) signal from
60 No Signal from ODU 4) Replace RFU.
RFU
For High Power RF Unit:
Check BMA connector center pin is
not spliced both on RFU and on
OCB.
Modem Script Not No modem script is available 1) Upgrade MRMC scripts
60
Supported for this RFU. 2) Replace RFU

"Protection Lockout"
command executed. Will lock
61 Protection Lockout 1) Disable Lockout
the switching operation until
removed.
does not support XPIC.
61 Protection Force Switch 1) Disable "Force Switch"
Or, the system is missing one
RFU Power Supply At least one of the PSU
62 Replace RFU.
Failure voltages is too low.
1) Reset IDM.
RFU Power Supply Failure 2) Check IF cable and connectors.
62 RFU Power Failure (Vd)
(Vd) 3) Replace ODU.
4) Replace IDM.
1) Reset IDM.
RFU Power Failure (6v RFU Power Supply Failure 2) Check IF cable and connectors.
62
pro) (6v pro) 3) Replace ODU.
4) Replace IDM.
1) Reset IDM.
RFU Power Failure (6v RFU Power Supply Failure 2) Check IF cable and connectors.
62
pro) (6v pro) 3) Replace ODU.
4) Replace IDM.
1) Reset IDM.
RFU Power Failure RFU Power Supply Failure 2) Check IF cable and connectors.
62
(12v) (12v) 3) Replace ODU.
4) Replace IDM.
1) Reset IDM.
RFU Power Failure 2) Check IF cable and connectors.
62 RFU Power Failure (1.5v)
(1.5v) 3) Replace ODU.
4) Replace IDM.
rain/multipath fading or lack of LOS.
RSL of Diversity channel is 2) Check link settings (TX power,TX
RFU Rx Level Path2 Out
63 very low (typically below -80 freq).
Of Range
dBm). 3) Check anttena alignment.
4) Check antenna connections
5) Replace local/remote ODU.
rain/multipath fading or lack of LOS.
RFU Rx Level Path1 Out RSL of Main channel is very
63 freq).
Of Range low (typically below -80 dBm).
3) Check anttena alignment.
4) Check antenna connections
5) Replace local/remote ODU.
1) Check installation conditions.
RFU Extreme RFU temperature is too 2) Verify operation as per product's
64
Temperature high/low. specs.
3) Replace RFU
1) Check RFU connection to BP
2) Check that fans are connected to
Fan Failure was detected by PS
65 RFU Fan Failure
RFU 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
Fan Failure was detected by
65 RFU Fan Failure 3) Replace RFU BP cable
RFU
4) Replace specific fan or fans
drawer
5) Replace RFU
1) Check IF cable connectors.
2) Check N-Type connector inner
RFU Low Signal To RFU is detecting low signal
66 pin is not spliced.
ODU from IDU
3) Replace IDM.
4) Replace RFU.
1) Reconnect XPIC clock cables at
No XPIC clock is received
67 RFU XPIC Clock Failure both RFUs
from Master RFU
2) Replace XPIC cable
1) Check link performance
2) Re-perform delay calibration
Delay calibration is
RFU Delay Calibration 3) Re-perform delay calibration in
68 unseccessfull since RX AGC
Failure 1 RF loopback
is unlocked.
4) Reset the RFU
5) Replace RFU
1) Check link performance
Delay calibration is 2) Reperform delay calibration
RFU Delay Calibration unseccessfull since wide or 3) Re-perform delay calibration in
69
Failure 2 deep notch has been RF loopback
detected at the RX signal 4) Reset the RFU
5) Replace RFU
GbE port is enabled by the
user but the system overrides
this and mutes the port.
This alarm may appear in the
1) Check the reason for the alarm
Gigabit Ethernet TX following cases:
70 (see the Probable Cause column)
Mute Override Radio LOF (local or remote),
and correct it accordingly.
Link ID mismatch (local or
remote), excessive BER
(local or remote), Signal
degrade (local or re
1) Reconnect SFP.
Gigabit Ethernet SFP TX SFP does not transmit
70 2) Replace SFP.
Fault Ethernet properly.
3) Replace IDM.
1) Reconnect SFP.
Gigabit Ethernet SFP SFP is not connected
70 2) Replace SFP.
Not Intact properly.
3) Replace IDM.
71 Encryption Fault HW encryption fault 1) Reset IDM.
1) Check link staus.
72 Encryption Sync Loss Encryption loss of frame
2) Reset IDM.

1) Check link status.
The first encryption key
73 Initial KEP Failed 2) Reset IDC.
exchange failed
3) Reset IDM.
Session Key Timer No session key exchange in
74 1)Check link status.
Elapsed the allowed time
One of the built-in encryption 1) Reset IDC.
75 Power-Up Test Failed
system tests failed 2) Reset IDM.
One of the Conditional tests 1) Reset IDC.
76 Conditional Test Failed
failed 2) Reset IDM.
Encryption mode changed by
Encryption Will Turned
77 user, will take effect after next
Off On Next Reset
power up.
Admin password in Administrator password is the
80 Change administrator password.
default state default value
1) Verify Protection Radio link is up
and, no errors over the link.
Link Group #1 N+1
N+1 Link Group protection properly configured for N+1 Link
Protection Fault: XC
81 degraded due to peer XC Group protection.
Peer Communication
communication fault. 3) Check that remote IDU has
Failure
properly operational XC board.
4) Check that Protection Radio link
termin
1) Check if XC module is inserted
Link Group #1 N+1 N+1 Link Group protection
and powered on and no other alarm
81 Protection Fault: XC degraded due to XC card
pertained to XC is active.
Card is Down fault.
2) Replace XC module.
N+1 Link Group protection 1) Check Protecting Radio module
Link Group #1 N+1 degraded due to Loss Of is powered on and operates
81 Protection Fault: Frame or Loss Of Signal properly.
Protecting Radio Failure alarm on the radio port 2) Replace faulty module.
detected by XC board. 3) see Radio RS: LOF (SDH)
Lockout or Force Switch to
Link Group #1 N+1
Protecting Link Group
81 Protection Fault: Locked Release maintenance command.
maintenance command
by User
activated.
properly configured with N+1 Link
Link Group #1 N+1 Group topology, and all protection
Protection Fault: Local- members are configured with the
81 degraded due to Local-
Remote Group Topology same priority level (if extra traffic is
Remote Protection Mismatch.
Mismatch configured as revertive in one
subrack, it should also be
configured the
There is no power on the 1) Check if the power switch is on.
82 Loss of Protection
standby IDM 2) Replace standby IDM
Temporary License activated Load permanent license or disable

83 Temp License is Active
by the user the temporary license

There is a Radio fault on the
remote radio or the "Block
Radio Command on the
protection configuration" is 1) Check the Block Radio command
enabled. status on the protection
Ingress Gigabit Ethernet
84 The Alarm should be raised configuration.
blocked on Radio
only on Multi Radio. The 2) Check the remote radio alarms
cause for radio fault are: and solve the radio fault accordingly
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 1) Check the Block Radio command
enabled. status on the protection
Egress Gigabit Ethernet
84 The Alarm should be raised configuration.
blocked on Radio
only on Multi Radio. The 2) Check the local radio alarms and
cause for radio fault are: solve the radio fault accordingly.
Radio LOF, Link ID
mismatch, Drawer ID
mismatch, Excessive B
IDC's SW doesn't support the
85 Unknown RFU Type Upgrade IDC's SW.
RFU.
Incompatible RFU TX RFU calibration tables
85 Upgrade IDC's SW.
Calibration requires IDC SW upgrade.
This alarm occurs when the
connection between the NMS
401 Node down.
and the network element is
lost.
This alarm occurs when the
User <name> (from
user fails to log in to the NMS
402 <IP>) failed to login <n>
system correctly several
times.
times consecutively.
Standby serevr failed to
This alarm occurs when a Open the main server configuration,
connect to main server
secondary standby NMS and in the Redundancy section,
403 (the main server is
server tries to connect to a change the server roll from Stand
configured as
stand-alone NMS server. Alone to Main Server.
Standalone).
This alarm occurs for a
No communication
primary NMS server when its
404 between main and
connection to the standby
standby servers.
NMS server is lost.
This alarm occurs for the
License expires in less NMS server when the license Contact customer support to obtain
405
than two weeks. is set to expire in less than a license file for the server.
two weeks.
This alarm occurs for the
Contact customer support to obtain
406 License expired. NMS server when the license
a license file for the server.
expires.
This alarm occurs for the Remove some of the elements, or
Network Elements
NMS server when the number Contact customer support to obtain
407 number exceeds the
of network elements exceeds a license file for the updated
license limit.
the license limit. number of elements.

This alarm occurs for the The license file is probably
Failed loading license
408 NMS server when it fails to corrupted. Contact customer
file.
load the license file. support to obtain a new license file.
This alarm occurs when NMS
Failed to start the TFTP server attempts to start the
Check your system, and disable
409 server on <host> TFTP, but the TFTP port (69)
other TFTP servers.
(address already in use). is already bound by another
process.
This alarm occurs when a
410 Disconnected User user is disconnected by
another user.
1) Verify the existence of all IDMs
and ODU, and verify their
This alarm occurs when a
connectivity.
Standby serevr failed to secondary standby NMS
2) Open the unit Alarm Log (using
411 connect to main server server tries to connect to a
the element manager) and send to
(versions mismatch). main NMS server,with a
customer support the code in the
different software version.
end the "XPIC Insufficient" event
text.
Enabled feature set Disable the feature or contact
The enabled feature set is not
414 <feature name> is not Support to get an appropriate
licensed.
licensed 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.
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:
y 155 Mbps Line Interface
y Wayside Channel
Local IDU
101101110...
Local IDU Modem & to ODU
Equipment IF
Interfaces
101101110...
Local Loop
y Full IDU (all three inputs through the IDU, modulator, and looped in the IF).

Remote:
y 155 Mbps Line Interface
y Wayside Channel
Local IDU
101101110...
Local IDU Modem &
Equipment IF
Interfaces
101101110...
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 Remote Terminal

101101110...
Modem
Local Local Remote Line
Equipment &
101101110... IDU ODU IDU Interface
IF
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.

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 Site A Site B
Remote
Terminal
3xRS-232
192.168.1.1
192.168.1.17
192.168.1.2 192.168.1.18
192.168.1.3 192.168.1.19
3200T GNE A 3200T NE B

Te PPP /
lne Ethernet
t
IP Management 192.168.1.33
Network
SNMP 1500P NE C PPP /
Ethernet
CeraView 192.168.1.34
1500P NE D
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

Uploaded by

Copyright:

Available Formats

Ceragon IP10 Troubleshooting Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ceragon IP10 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What troubleshooting steps are outlined?

What troubleshooting steps are outlined?

FibeAir®

Part ID: BM-0108-0

Corporate Headquarters: European Headquarters:

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

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

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

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

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

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

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

It is recommended to perform the procedures as often as local environmental conditions require. It is

What to check Check for ... Comments

IDU alarm LEDs All green If not, perform troubleshooting

Coax cable connection Tight, no corrosion or 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 Per installation Align/adjust as required

Torque on antenna Tight mount Adjust as required

FibeAir® Troubleshooting Guide 1

Step 1: Define the Symptom

Step 2: Isolate the Problem

Step 3: Understand the Problem

Step 4: Solve the Problem

IDU LED Indicators

FibeAir® Troubleshooting Guide 2

LED Indications for FibeAir IP-10 G-Series

FibeAir® Troubleshooting Guide 3

FibeAir® Troubleshooting Guide 4

FibeAir® Troubleshooting Guide 5

FibeAir® Troubleshooting Guide 6

FibeAir® Troubleshooting Guide 7

FibeAir® Troubleshooting Guide 8

FibeAir® Troubleshooting Guide 9

FibeAir® Troubleshooting Guide 10

FibeAir® Troubleshooting Guide 11

FibeAir® Troubleshooting Guide 12

FibeAir® Troubleshooting Guide 13

PWR X X Red - power supply problem

FibeAir® Troubleshooting Guide 14

LOF (LED Panel) - LOF

LED Color Alarm Explanation

Yellow Local unit receives LOF from a receive path

Red Local unit receives LOF from a receive path

LOF (Interface Panel) - ALRM

LED Color Alarm Explanation

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

LED Color Alarm Explanation

OFF Local receiver not in use.

Green Local receiver in use.

FibeAir® Troubleshooting Guide 15

A note about interface troubleshooting:

y External equipment Tx is connected to FibeAir Rx.