FibeAir®
Troubleshooting Guide
Part ID: BM-0108-0 Doc ID: DOC-00015466 Rev a.02 September 2009
Notice This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.
Registered TradeMarks Ceragon Networks® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.
TradeMarks CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are trademarks of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.
Statement of Conditions The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.
Information to User Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment. Copyright © 2009 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email:
[email protected] North American Headquarters: Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email:
[email protected]
www.ceragon.com
European Headquarters: Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email:
[email protected] APAC Headquarters: Ceragon Networks APAC (S'pore) Pte Ltd 100 Beach Road #27-01/03 Shaw Towers Singapore 189702 Tel.: 65 65724170 Fax: 65 65724199
Contents General .......................................................................................................... 1 Maintenance Policy ........................................................................................... 1 Visual Inspection............................................................................................... 1
Troubleshooting Guide ................................................................................ 2 The Process ....................................................................................................... 2 IDU LED Indicators............................................................................................ 3
Alarm List Table ...........................................................................................16 Fault Isolation using Loopbacks ................................................................39 Connection Fault Guide ..............................................................................40
General Ceragon designed FibeAir to be highly reliable and relatively maintenance free. In the event of a system failure, the system will provide detailed indications to assist troubleshooting and fault isolation. This guide explains the alarm indications of the FibeAir system, and contains procedures for troubleshooting and fault isolation.
Maintenance Policy To ensure simple and efficient system maintenance, the on-site technician will only replace IDU, ODU, or RFU modules, and not repair them. Under no circumstance will the technician be permitted to open the equipment in order to repair a module or circuit board. Opening equipment will terminate the Ceragon warranty. Maintenance procedures the technician can perform include visual inspection, cleaning, cable/connector repair, link alignment/adjustment, and retorquing antenna mount bolts.
Visual Inspection The following table lists the suggested preventive maintenance procedures, which include visual inspection of the equipment and verification of operational parameters. It is recommended to perform the procedures as often as local environmental conditions require. It is recommended to notify the end customer prior to performing any preventive maintenance procedures that could affect service on the circuit. What to check
Check for ...
Comments
IDU alarm LEDs
All green
If not, perform troubleshooting
Coax cable connection
Tight, no corrosion or moisture
Clean/repair as required
Coax cable
No cracks or kinks
Replace as required
All equipment
Dust or dirt
Clean as required
Receive level (voltage in IDU/ODU/RFU, or using management)
Per installation records
Align/adjust as required
Torque on antenna mount bolts
Tight mount
Adjust as required
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 FibeAir® Troubleshooting Guide
2
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. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system.
PDH
excessiveber
E1/T1 excessive BER on port #%1
Major
Red
Excessive BER alarm status
1) Line is not properly connected. 2) External equipment is faulty.
PDH
loopbacktowardsline
E1/T1 loopback towards line on port #%1
Major
Red
Loopback towards line alarm status
User configured system to loopback mode.
Cancel loopback configuration.
PDH
loopbacktowardsradio
E1/T1 loopback towards radio on port #%1
Major
Red
Loopback towards radio alarm status
User configured system to loopback mode.
Cancel loopback configuration.
No signal is detected on port
1) Line is not properly connected. 2) External equipment is faulty.
1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system.
Yellow
Signal degrade is detected on port
1) Line is not properly connected. 2) External equipment is faulty.
1) Reconnect line. 2) Check line cables. 3) Check external equipment. 4) Power cycle the system.
Unexpected signal is detected on port
1) Port is disabled. 2) Line is connected to a disabled port.
1) Enable relevant port. 2) Disconnect cable from relevant port.
PDH
loss-ofsignal
E1/T1 loss of signal on port #%1
Major
Red
PDH
signaldegrade
E1/T1 signal degrade on port #%1
PDH
unexpected -signal
E1/T1 unexpected signal on port #%1
Warning
Yellow
IDU
ext-inalarm
%1
Warning
Yellow
IDU
eth-localarm
Ethernet loss of carrier on port #%1
IDU
eth-txmute-alarm
Ethernet Tx mute override on port #%1
FibeAir® Troubleshooting Guide
Minor
Major
Major
Red
Red
External Alarm Input
---
Ethernet Loss of Carrier on Port #n
1) FE cable disconnected 2) Defected FE cable.
1) Check connection of FE cable. 2) Replace FE cable.
Ethernet TX Mute Override
Radio LOF/EXBER/ Link ID on local or remote side (in pipe application)
Check link
3
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
Description
Severity
Color
Alarm Info
Probable Cause
Corrective Action 1) Connect cable to the port. 2) Replace cable.
Major
Red
Gigabit loss of carrier
1) Cable is not connected to the port. 2) Cable is defected.
IDU
gbe-loc-alarm
Gigabit ethernet loss of carrier on port #%1
IDU
gbe-sfp-alarm
Gigabit ethernet SFP not inserted
Major
Red
Gigabit Ethernet SFP not intact
SFP is not inserted
1) Check SFP connector. 2) Replace fiber.
IDU
gbe-sfp-tx-alarm
Gigabit ethernet SFP Tx fault
Major
Red
Gigabit Ethernet SFP TX Fault
SFP malfunction
Replace SFP
IDU
gbe-tx-mutealarm
GBE Tx mute override on port #%1
Yellow
GBE TX Mute Override
Radio LOF/EXBER/Link ID on local or remote side
Check link
1) Firmware file is missing. 2) System error in power up.
1) Move Management to port 2. 2) Download firmware file. 3) Reset system.
Warning
IDU
file-load-erroralarm
Firmware file load error (%1)
Critical
Red
Firmware file was not successfully loaded
IDU
file-not-foundalarm
Firmware file not found (%1)
Critical
Red
Firmware file was not found
1) Firmware file is missing.
1) Download firmware file. 2) Reset system.
IDU
alarms-file
Alarm file not found
Major
Red
The system's alarm file was not found
The alarm file was deleted or is corrupted
Download alarm file
IDU
entity-init-failalarm
SW error: entity initialization failure
Major
Red
SW failed to properly initialize
SW error during system intialization
Reset system
IDU
extremetemperature
IDU extreme temperature conditions
Warning
Yellow
IDU is in extreme temperature condition
The external cooling/heating system is not operating.
Turn on external cooling/heating systems.
IDU
fan-failure
Fan failure
Minor
Yellow
Fan failure
Defective fan unit
Replace fan unit
IDU
generalhardware-failure
General HW failure %1
Major
Red
HW failure
Defected HW
1) Reset system. 2) Replace IDU.
kernel-backup
Backup kernel is running
Yellow
Backup kernel is running
1) The kernel (/boot/uImage) is corrupted or missing
1) Re-install the SW.
IDU
FibeAir® Troubleshooting Guide
Minor
4
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
Description
Severity
Color
Alarm Info
Probable Cause
Corrective Action
IDU
low-input-voltage
Low input voltage
Warning
Yellow
Low input voltage detected
Low input to the system
1) Check power supply voltage.
IDU
param-set-failalarm
SW error: parameter set failed
Warning
Yellow
Parameter set failure
SW error
Reset system
1) Reset system. 2) Download inventory file
IDU
corrupted-filealarm
Inventory file (%1) is corrupted
Critical
Red
The inventory file is corrupted
1) Inventory file is missing. 2) Inventory file was found to be corrupt upon system power up.
IDU
file-not-foundalarm
Inventory file (%1) was not found
Critical
Red
Inventory file was not found
1) Inventory file is missing.
1) Download inventory file. 2) Reset system.
IDU
demo-licensealarm
Yellow
Demo license is used by customer
1) Demo license activated by user.
1) Terminate demo license. 2) Activate operational license.
Demo license
Warning
IDU
license-violationalarm
License violation %1
Warning
Yellow
License violation
1) Unit does not match license features set.
1) Check that the code was entered correctly. 2) Call tech support for new license generation.
IDU
firmware-filemissing-alarm
Modem firmware file not found
Critical
Red
Modem file was not found
1) Modem file is missing.
1) Download Modem file. 2) Reset system.
IDU
firmware-loaderror-alarm
Modem was not loaded successfully
Critical
Red
Modem was not loaded successfully
1) File is corrupt. 2) System failure.
1) Download file. 2) Reset system.
IDU
fpga-file-curruptalarm
Radio script (LUT) is corrupt
Critical
Red
Radio script LUT is not valid
1) Faulty file.
1) Download radio script LUT.
IDU
fpga-file-notfound-alarm
Radio script (LUT) not found
Critical
Red
Radio script LUT not found
1) File was not downloaded to system.
1) Download radio script.
FibeAir® Troubleshooting Guide
5
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
Description
Severity
Color
Alarm Info
Probable Cause
Corrective Action
1) Incompatibility between RFU and loaded radio script.
1) Change RFU. 2) Change Raido script.
IDU
incompatiblescript-alarm
Incompatible script: %1 %2
Critical
Red
Incompatibilit y between RFU and loaded radio script
IDU
modem-scriptfile-corrupt-alarm
Radio script is corrupt
Critical
Red
Radio script is not valid
File is corrupt
Download file
IDU
modem-scriptfile-not-foundalarm
Radio script not found
Critical
Red
Radio script not found
File not found
Download file
IDU
mrmc-file-corruptalarm
MRMC file is corrupt
Critical
Red
MRMC file not valid
File is corrupt
Download file
IDU
mrmc-file-notfound-alarm
MRMC file not found
Critical
Red
MRMC file not found
File not found
Download file
IDU
rfu-file-corruptalarm
RFU file is corrupt
Critical
Red
RFU file not valid
File is corrupt
Download file
IDU
rfu-file-not-foundalarm
RFU file not found
Critical
Red
RFU file not found
File not found
Download file
IDU
if-loopback-alarm
IF loopback
Warning
Yellow
IF loopback initiated
1) User enabled IF loopback.
1) Disable IF loopback.
Red
IF synthesizer unlock
1) Extreme temperature condition. 2) HW failure.
1) Check installation. 2) Reset IDU.
1) Cable is not connected to IDU or RFU.
1) Check IF cable and connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.
1) Physical short at the IF cable.
1) Check IF cable and connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.
IDU
IDU
IDU
lock-detect-alarm
cable-open
cable-short
IF lock detection
Cable open
Cable short
FibeAir® Troubleshooting Guide
Critical
Major
Major
Red
Red
Cable between IDU and RFU is not properly connected
There is a short in the IF cable
6
LED Indications for FibeAir IP-10 - Continued
LED
IDU
Alarm Name
cfm-failure
Description
Ethenet services failure
Severity
Warning
Color
Probable Cause
Corrective Action
Ethenet services failure
1) Local MEP error indication. 2) Remote MEP error indication. 3) Remote MEP loss of connectivity.
1) Check MAID definitions. 2) Check remote MEP definitions. 3) Check local MEP definitions. 4) Run "CFM traceroute" to the remote MEP then perform "CFM ping" to each MP (Maintenance Point) in order to find the broken point.
Red
Protection cable is not properly connected
1) Cable is not connected between protection ports. 2) Cable is connected to wrong port. 3) Cable is damaged.
1) Connect Ethernet cable to protection port of both IDUs. 2) Replace cable.
1) RFU properties are not identical. 2) Radio scripts are not identical.
1) Change RFU. 2) Download required radio script.
Yellow
Alarm Info
Protection
cabledisconnecte d-alarm
Mate IDU cable is not connected
Protection
configuratio n-mismatchalarm
Mate IDU configuration mismatch
Major
Red
Mismatch between IDU in Protection mode
Protection
forceswitch-alarm
Protection force switch
Warning
Yellow
Force switch command was issued
1) User command - Force Protection Switch
1) Clear Force Switch Command.
Protection
ipi-xml-filealarm
Protection SW activity fault
Warning
Yellow
SW fault in Protection mechanism
1) SW fault in synchronization of databases
1) Reset Standby unit.
Protection
lockoutalarm
Protection lockout
Red
Protection Lockout command was isused
User issued Protection Lockout
Clear Lockout command
FibeAir® Troubleshooting Guide
Major
Major
7
LED Indications for FibeAir IP-10 - Continued
LED
Protection
Alarm Name
mate-commfailure-alarm
Description
Mate IDU communication error
Severity
Major
Color
Red
Alarm Info
Probable Cause
Corrective Action
IDU cannot communicate with its mate IDU
1) IDU IP addresses are identical. 2) IDUs IP subnet is not identical. 3) Protection Cable is not properly connected. 4) Protection Cable is damaged.
1) Check Protection cable connectivity. 2) Replace Protection cable.
1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU.
Radio
radioexcessiveber
Radio excessive BER
Major
Red
Excessive BER on radio
1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU.
Radio
radio-link-idmismatch
Link ID mismatch
Critical
Red
Link ID Mismatch Alarm
Link ID is not the same at both sides of link
Configure same Link ID for both sides of link.
Loss Of Frame on radio
1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU.
1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU.
Signal Degrade on radio
1) Fade in the link. 2) Defected IF cable. 3) Fault in RFU. 4) Fault in IDU.
1) Check link performance. 2) Check IF cable, and replace if required. 3) Replace RFU. 4) Replace IDU.
Radio
Radio
radio-lof
radio-signaldegrade
Radio loss of frame
Radio signal degrade
FibeAir® Troubleshooting Guide
Critical
Minor
Red
Yellow
8
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
Description
Remote
remotecommunicatio n-failure
Remote communication failure
RFU
incompatiblerfu-txcalibration
Incompatible RFU TX calibration
Severity
Major
Major
Color
Alarm Info
Probable Cause
Corrective Action
Red
Remote Communicati on Failure Alarm
1) Fade in the link.
1) Check link performance.
Red
RFU calibration tables require IDC SW upgrade
RFU calibration tables require IDC SW upgrade.
Upgrade IDU's SW.
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
RFU
communicatio n-failure
RFU communication failure
Warning
Yellow
Failure in communicati on between IDU and RFU
RFU
delaycalibrationfailure-1
RFU delay calibration failure 1
Warning
Yellow
RX AGC is not locked
Defective RFU
1) Reset the IDU / RFU. 2) Replace RFU.
RFU
delaycalibrationfailure-2
RFU delay calibration failure 2
Yellow
Calibration cannot be completed due to notch detection
Calibration cannot be completed due to notch detection
Enter delay calibration value manually
1) Installation conditions. 2) Defective RFU.
1) Check installation conditions. 2) Verify operation as per product's specs. 3) Replace RFU.
RFU
extreme-tempcond
RFU extreme temperature
FibeAir® Troubleshooting Guide
Warning
Warning
Yellow
RFU temperature is too high or low
9
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
Description
RFU
fan-failure
RFU fan failure
RFU
hardware-failure1
RFU hardware failure 1
RFU
hardware-failure2
RFU hardware failure 2
RFU
RFU
low-if-signal-torfu
no-signal-from-rfu
Low IF signal to RFU
No signal from RFU
FibeAir® Troubleshooting Guide
Severity
Warning
Critical
Critical
Major
Major
Color
Alarm Info
Probable Cause
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
Yellow
RFU Fan Failure Alarm
1) Defective / non-existent fan drawer. 2) Defective RFU-to-fan drawer connection. 3) Defective RFU.
Red
RFU Hardware Failure 1 Alarm
1) Defective RFU.
1) Replace RFU.
Red
RFU Hardware Failure 2 Alarm
1) Defective RFU.
1) Replace RFU.
1) IF cable connection. 2) Defective RFU. 3) Defective IDU.
1) Check IF cable connectors. 2) Verify that NType connector inner pin is not spliced. 3) Replace IDU. 4) Replace RFU.
No RX (140 MHz) signal from 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.
Red
Red
RFU is detecting low signal from IDU
IDU is not detecting a signal from the RFU
10
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
RFU
pa-extreme-tempcond
RFU
RFU
RFU
RFU
RFU
RFU
power-failure-12v
power-failure1point5
power-failure-24v
power-failure-6v
power-failure-6vsw
power-failureminus-5v
Description RFU PA extreme temperature
RFU power failure (12v)
RFU power failure (1.5v)
RFU power failure (24v)
RFU power failure (6v pro)
RFU power failure (6v SW)
RFU power failure (-5v)
RFU
power-failure-vd
RFU power failure (Vd)
RFU
rfu-loopbackactive
RFU loopback
FibeAir® Troubleshooting Guide
Severity
Warning
Major
Major
Major
Critical
Major
Major
Color
Alarm Info
Probable Cause
Corrective Action
Yellow
RFU PA Extreme Temperature
1) Installation conditions. 2) Defective RFU.
1) Check installation conditions. 2) Replace RFU
Red
RFU Power Failure (12v) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
Red
RFU Power Failure (1.5v) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
Red
RFU Power Failure (24v) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
Red
RFU Power Failure (6v pro) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
Red
RFU Power Failure (6v SW) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
Red
RFU Power Failure (6v pro) Alarm
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
1) Defective IF cable/connector. 2) Defective RFU. 3) Defective IDU.
1) Replace IF cable/connector. 2) Replace RFU. 3) Replace IDU.
1) User action.
1) Disable RFU loopback.
Critical
Red
RFU Power Failure (Vd) Alarm
Major
Red
RFU loopback Alarm
11
LED Indications for FibeAir IP-10 - Continued
LED
Alarm Name
RFU
rfu-power-supplyfailure
RFU
RFU
RFU
rx-level-out-ofrange
rx-level-path1-outof-range
rx-level-path2-outof-range
Description RFU power supply failure
Rx level out of range
RFU Rx level path1 out of range
RFU Rx level path2 out of range
FibeAir® Troubleshooting Guide
Severity
Color
Major
Red
Warning
Warning
Warning
Yellow
Yellow
Yellow
Alarm Info
Probable Cause
Corrective Action
RFU power supply failure
At least one of the PSU voltages is too low.
1) Replace RFU.
RFU RX Level Out of Range
RSL is very low (typically below 80 dBm), link is down. For RFU-C: RSL is too Low (typically below 83dBm) or RSL is too High (typically above 26dBm).
1) Check antenna alignment & link planning. 2) Check link settings (TX power, TX freq). 3) Check antenna connections. 4) Replace local/remote RFU.
1) Improper installation. 2) Fading event. 3) Defective RFU.
1) Check that the fault is not due to rain/multi-path fading or lack of LOS. 2) Check link settings (TX power, TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote RFU.
1) Improper installation. 2) Fading event. 3) Defective RFU.
1) Check that the fault is not due to rain/multi path fading or lack of LOS. 2) Check link settings (TX power, TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote RFU.
RFU Rx Level Path1 Out of Range
RFU Rx Level Path2 Out of Range
12
LED Indications for FibeAir IP-10 - Continued
LED
RFU
RFU
Alarm Name
synthesizer-1unlocked
synthesizer-2unlocked
Description
Synthesizer 1 unlocked
Synthesizer 2 unlocked
RFU
synthesizer-3unlocked
Synthesizer 3 unlocked
RFU
synthesizerunlocked
Synthesizer unlocked
Severity
Major
Major
Major
Major
Color
Alarm Info
Probable Cause
Corrective Action
Red
RFU synthesizer is unlocked
1) Defective RFU. 2) Defective XPIC cable connection.
1) Replace XPIC cable. 2) Replace RFU.
Red
RFU synthersizer is unlocked
1) Defective RFU. 2) Defective XPIC cable connection.
1) Replace XPIC cable. 2) Replace RFU.
Red
RFU synthesizer is unlocked
1) Defective RFU. 2) Defective XPIC cable connection.
1) Replace XPIC cable. 2) Replace RFU.
Red
One of the RFU Synthesizers is Unlocked
One of the RFU synthesizers is unlocked.
1) Replace RFU. 2) In XPIC mode, replace mate RFU as well.
1) Defective RFU (the RFU cannot transmit the requested TX power)
1) Replace RFU. 2) Intermediate solution - reduce TX power.
RFU
tx-level-out-ofrange
Tx level out of range
Minor
Yellow
RFU TX Level Out of Range
RFU
tx-mute
Tx mute
Warning
Yellow
RFU TX Mute
RFU Transmitter muted by user.
Unmute the RFU transmitter.
unknown-rfu-type
IDU SW does not support this type of RFU
Red
IDC's SW doesn't support the RFU
IDC's SW doesn't support the RFU.
Upgrade IDC SW.
RFU
FibeAir® Troubleshooting Guide
Major
13
LED Indications for other FibeAir Systems
Color LED
Red
PWR (Power)
X
LINE
X
LOF (Loss of Frame)
X
BER (Bit Error Ratio)
X
LPBK (Loopback)
X
STBY (Standby)
Yello w
Green
Description
X
Red - power supply problem
X
Red - no input to main channel / high BER Yellow - JO mismatch
X
Red - radio did not recognize information frame (radio link problem/radio LOF)
X
Red - radio BER higher than radio excessive error threshold definition (see Sonet/SDH configuration window) Yellow - radio BER higher than radio signal degrade threshold definition (see Sonet/SDH configuration window)
X
Red - loopback is active
X
X
Yellow - Protected configuration. The unit is currently passive or Tx mute is operating
X
X
IDU
X
X
X
Red - modem unlocked Yellow - high temperature / fan problem
ODU
X
X
X
Red - no link, or ODU power, or ODU/RFU unlocked Yellow - radio interference, or high temperature, or Rx/Tx out of range
CBL (Cable)
X
X
Red - RF cable open / RF cable short
RMT (Remote Unit)
X
X
Red - no link / remote unit problem (red LED is lit in the remote unit)
FibeAir® Troubleshooting Guide
X
Yellow - warning in remote unit (yellow LED is lit in the remote unit)
14
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 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
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
0
Insufficient System Configuration for Full XPIC Support
One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.
10
ODU 5/8/12/-12V Power Supply Failure
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
11
Synthesizer #1/2/3 Unlocked
One of the RFU synthisizers is unlocked.
Replace RFU. For non RFU-C radios: In XPIC configuration, it might be that the RFU is taking the synch from the mate RFU. In this case, check if alarm persists in non-XPIC configuration.
12
Tx Mute On/Off
RFU transmitter muted by user
Unmute the RFU transmitter.
12
Tx Level Out of Range
The RFU cannot transmit the requested Tx power.
1) Replace RFU. 2) Intermediate solution - reduce TX power.
FibeAir® Troubleshooting Guide
16
Trap ID
Description
13
Rx Level Out of Range
14
ODU Temperature Out of Range
15
XPIC Cable Swap
15
Power Input #2 is Down
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 installation conditions. 2) Replace RFU.
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) Check antennas alignment & link planning. 2) Check link settings (TX power,TX freq). 3) Check antenna connections. 4) Replace local/remote RFU.
1) Verify correct cable connection. Recommended connection is V to Right drawer and H to Left drawer
15
Power Input #1 is Down
Subrack redundant power feed failure.
1) Verify if the Power Input card exists in the subrack. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack. 4) Replace Power Input card if problem still exists. 5) Disable Power Input
15
IDU 5/8/3.3/-5V Power Supply Failure
Failure in an IDU power supply.
1) Check -48 VDC supply to the IDU. 2) Replace IDU.
15
Drawer Power On/Off
15
Drawer Internal Power Failure (Board #2)
15
Drawer Internal Power Failure (Board #1)
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)
16
Extension Link Communication Failure
FibeAir® Troubleshooting Guide
Problem with extension cable or the connection between the two subracks.
1) Switch off/on IDM. 2) Replace IDM.
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
17
Trap ID
16
16
Description
Cable Short
Cable Open/Short
Probable Cause
Corrective Actions
IDM-RFU cable short.
1) Check IF cable and connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.
IDU-ODU cable open/short.
1) Check IF cable and connectors. 2) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 3) Replace IDU. 4) Replace ODU.
16
Cable Open
IDM-RFU cable open.
1) Check IF cable and connectors. 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.
17
MRMC=???value??? Script File is Missing
Multi-Rate Multi-Constellation configuration script for the specified capacity/modulation is missing in the IDC.
1) Download the Modem script to the IDC and reset the IDM.
Drawer hardware intact ok / failure (Mux)
1) In case of failure, replace IDM.
17 18 18 19 19 19 19 19 19 19 19 19
19
19
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 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
FibeAir® Troubleshooting Guide
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
1) Check installation conditions. 2) Replace IDM. 1) Replace fan.
Internal loopback on Fiber
Disable loopback
Loopback applied by user
Disable loopback
IDU IF loopback applied by user
Disable loopback
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
18
Trap ID
Description
Probable Cause
Gigabit Ethernet Internal Loopback External Loopback on Fiber #n E1\T1 Internal Loopback on Port #n E1\T1 External Loopback on Port #n
Gigabit Ethernet Internal Loopback applied by user. IDU Line loopback applied by user IDU Line loopback applied by user
Disable Gigabit Ethernet Internal Loopback
E1/T1 External loopback
1) Disable loopback
20
Remote Communication Failure
No communication between the IDUs over the link.
1) Verify link is up and no errors over the link. 2) Check in-band management configuration.
21
PRBS Test is Running on Radio
PRBS test started.
Disable PRBS test.
21
Link Group #1 N+1 Protection Fault: Locked by User
22
Trib RS: LOF
19 19 19 19
22
Radio RS: LOF (SDH) Radio Section: LOF (Sonet)
Lockout or Force Switch to Protecting Link Group maintenance command activated. Trib RS: LOF
Loss Of Frame alarm on the radio, link is down
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.
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
FibeAir® Troubleshooting Guide
Corrective Actions
1) Disable loopback 1) Disable loopback
Release maintenance command.
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) 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.
19
Trap ID
Description
Probable Cause
22
Fiber RS: LOF
Fiber RS: LOF (ADM)
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
23
E1\T1 Loss of Signal on Port #n
E1\T1 Loss of Signal
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
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
24 24 24 24 24 24 24 24 24
FibeAir® Troubleshooting Guide
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 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. 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.
Verify J0 settings in the IDU and in the end equipment.
20
Trap ID
Description
24 24 25 25
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
25 25 25 25 25 25 25 25 25 25 25 25 25 25
Probable Cause 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
25
Excessive BER on Radio #n
Major radio Excessive BER alarm
25
Excessive BER on Fiber #n
Major line Excessive BER alarm
25 25
E1\T1\E3\DS3 #n Excessive BER E1\T1\E3\DS3 #n Excessive BER
FibeAir® Troubleshooting Guide
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.
E3/DS3 Excessive BER E1/T1 Excessive BER
21
Trap ID
25
26 26 26 26
Description
Probable Cause
E1\T1 Excessive BER on Port #n
Major Excessive BER alarm on E1/T1 port
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
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 26 26 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 HP: Signal Degrade Fiber RS: Signal Degrade Fiber RS: Signal Degrade
Fiber RS: Signal Degrade
Fiber MS: Signal Degrade Fiber LP #n Signal Degrade Fiber HP: Signal Degrade
FibeAir® Troubleshooting Guide
Corrective Actions 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.
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.
Radio RS: Signal Degrade Radio RS: Signal Degrade Radio RS: Signal Degrade Radio HP: Unequipped Radio LP #n: Signal Degrade Radio HP: Signal Degrade Fiber RS: Signal Degrade (ADM) 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.
Fiber MS: Signal Degrade Fiber LP #n Signal Degrade Fiber HP: Signal Degrade
22
Trap ID 26 26
Description E1\T1\E3\DS3 #n Signal Degrade E1\T1\E3\DS3 #n Signal Degrade
Probable Cause
Corrective Actions
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.
E1\T1 Signal Degrade on Port #n
Minor BER alarm on E1/T1 port
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
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
Gigabit Ethernet Unexpected Signal
GbE port is disabled but GbE data is detected.
1) Enable GbE port, disable GbE port of the source, or disconnect the fiber
Unexpected signal on the line input. Port disabled but line is connected.
1) Enable line port or disconnect line
30 30
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
30
Radio LP #n: LOP
30
Radio HP: LOP
30
Fiber LP #n: LOP
30
Fiber HP: LOP
31 31 31
Trib MS: RDI Trib LP #n: RDI Trib HP: RDI
31
Radio MS: RDI
31
Radio LP #n: RDI
31
Radio HP: RDI
31
Fiber MS: RDI
26
27 27 27 27 27 27 27 27 27 28 28
28
28
FibeAir® Troubleshooting Guide
Trib RS: Excessive BER
Fast Ethernet Unexpected Signal on Port #n Trib LP #n: LOP Trib HP: LOP Radio LP: Loss of pointer (LOP) alarm occurs. 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.
23
Trap ID
Description
31
Fiber LP #n: RDI
31
Fiber HP: RDI
32 32
Trib LP #n: PLM Trib HP: PLM
32
Radio LP #n: PLM
32
Radio HP: PLM
32
Fiber LP #n: PLM
32
Fiber HP: PLM
33 33
33
Trib LP #n: Unequipped Trib HP: Unequipped Radio LP #n: Unequipped Radio HP: Unequipped Fiber LP #n: Unequipped Fiber HP: Unequipped
34
External Alarm
35
External Alarm
36
External Alarm
37
External Alarm
38
External Alarm
39
External Alarm
40
External Alarm
41
External Alarm
33 33 33
FibeAir® Troubleshooting Guide
Probable Cause
Corrective Actions
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. 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.
24
Trap ID
Description
Probable Cause
Corrective Actions 1) Check that IDC #n is power up and finished initialization. 2) Check & configure both IDCs with proper system configuration: System Type, Subrack#, Subrack IP Base Address, Link Group Topology. 3) Check for Hardware fault: Subrack Auxiliary module
42
XPIC Cable Swap
Internal IDC to IDC communication failure between modules requied for Link Group protection service.
42
XC FPGA File is Missing
XC firmware file is missing in the 2-floor IDC.
1) Download XC firmware file of the required type and reset the IDC.
42
Wayside Firmware File is Missing
1) Download Wayside firmware file to the IDC and reset the IDC.
42
Subrack Auxiliary FPGA File is Missing
42
Secondary Clock Source Failure
Wayside firmware file is missing in the IDC. Subrack Auxiliary firmware file is missing in the 2-floor IDC. Secondary Clock Source Failure
42
Radio Card #n Powered Down
42 42 42
Primary Clock Source Failure MUX Firmware File is Missing Modem Firmware File is Missing
Radio module pertained to Link Protection group is powered down or extracted.
1) Check if Radio module is inserted properly in the subrack and is powered on. Replace module if faulty.
Primary Clock Source Failure A Mux FW file is missing from the system. A Modem FW file is missing from the system.
42
Link Group #1 N+1 Protection Fault: XC Peer Communication Failure
N+1 Link Group protection degraded due to peer XC communication fault.
42
Link Group #1 N+1 Protection Fault: Protecting Radio Failure XC Card Fault
N+1 Link Group protection degraded due to XC card fault.
42
Link Group #1 N+1 Protection Fault: LocalRemote Protection Mismatch
FibeAir® Troubleshooting Guide
1) Download Subrack Auxiliary firmware file and reset the IDC.
N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.
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 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.
25
Trap ID
42
42
42
Description
Probable Cause
Corrective Actions
Line module pertained to Link Protection group is powered down or extracted.
1) Check if the card is inserted properly in the subrack. 2) Check if own or redundant power supply / Radio module (in drawer #1) is powered on. Replace module if faulty.
Line Card #1 Powered Down
Line module in carrrier #1 of the Link Protection group is powered down or extracted.
1) Check if the card is inserted properly in the subrack. 2) Check if own or redundant power supply / Radio module is powered on. 3) Replace module if faulty.
License Fault
The MRMC loaded to the system is not supported by the license, or the ACM function is enabled while not supported by the license. The link is not operative.
Load another MRMC with bit rate supported by the license
Line Card #n Powered Down
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.
42
General Hardware Fault #9
Upper IDM Board (MUX or XC) EEPROM inventory information CRC error
42
General Hardware Fault #8
Upper IDM Board (MUX or XC) EEPROM read access error
42
General Hardware Fault #7
FPGA load failure - Subrack Auxiliary board.
42
General Hardware Fault #7
FPGA load failure - Modem
42
General Hardware Fault #6
FibeAir® Troubleshooting Guide
FPGA load failure - Mux
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. 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.
26
Trap ID
Description
42
General Hardware Fault #5
42
General Hardware Fault #4
42
General Hardware Fault #3
Probable Cause
Corrective Actions
DAC failure
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.
IDU XPIC HW fault
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.
XO failure - Mux board
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.
42
General Hardware Fault #2
XO failure - Modem board
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.
42
General Hardware Fault #11
Wrong card type detected in Subrack Auxiliary slot.
42
General Hardware Fault #11
Lower IDM Board (Modem or XC) EEPROM inventory information CRC error
42
General Hardware Fault #10
Subrack Auxiliary EEPROM checksum failure.
42
General Hardware Fault #10
Lower IDM Board (Modem or XC) EEPROM read access error
42
42
General Hardware Fault #1
EOW chaining Loss of Signal
FibeAir® Troubleshooting Guide
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.
IDU Synthesizer lock
1) Download correct SW/FW/Configuration scripts. 2) Power IDM off/on. 3) Replace IDM. 3) Replace IDC.
No signal detected on Subrack Auxiliary EOW chaining input.
1) Disable EOW chaining if not required. 2) Check EOW chaining line input on both subracks. 3) Check / fix EOW chaining configuration on mate subrack. Verify that EOW is defined on at least one working link on mate subrack. 4) Replace EOW chaining
27
Trap ID
42
42
42 42 42 42 42
Description
Drawer-RFU Communication Failure
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
Probable Cause
No communication between IDM and RFU.
1) Check IF cable and connectors. 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU
Internal Power failure.
1) Check that proper Subrack Auxiliary module inserted. 2) Extract and re-insert Subrack Auxiliary module. 3) Replace Subrack Auxiliary module.
IDU IF loop applied by user
1) Disable loopback
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
42
Auxiliary Card Fault #01
Subrack Auxiliary module failed or extracted.
42
ACM Configuration File is Missing
The ACM lookup table file cannot be found on the system disk.
43
43
43
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
44
RFU FW Upload Failed
44
RFU FW Upload Error
44
RFU FW Upload Canceled
44
ODU SW Upload Failed
FibeAir® Troubleshooting Guide
Corrective Actions
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.
Software download operation status (from user's PC to IDC) Configuration download status, initiated by user
File download status. Initiated by user.
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)
28
Trap ID 44 44 44
Description ODU SW Upload Error ODU SW Upload Canceled MUX/ODU Internal Download Succeeded/ Canceled/Failed/Error
Probable Cause
Corrective Actions
Software upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) MUX/ODU Internal Download Succeeded/Canceled/Failed/ Error 1) Check the mismatch configuration in the alarms log. 2) Configure the relevant IDC with the correct values for mismatch resolution, and wait one minute for the mismatch alarm to clear.
46
User Configuration Mismatch between IDC # and IDC #
At least one configuration parameter which should be equal in these two IDCs has different values.
46
User Configuration Mismatch () S=xx, D=xx
Configuration in the IDC is different than in the drawers or Auxiliary channel board
1) Check and compare configuration 2) See User Configuration Mismatch Alarm
User Configuration Mismatch () S=xx, D=xx
Mismatch configuration between the IDC Database and the drawer.
1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.
User Configuration Mismatch
At least one Link Group configuration parameter in the IDC Database is different than the actual configuration in the XC. Raised only after IDC hotswap or S/W reset.
1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.
User Configuration Mismatch
At least one drawer configuration parameter in the IDC Database is different than the actual configuration in the drawers. Raised only after IDC hotswap or S/W reset.
1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from the drawer to the IDC, or "Copy to Drawer", eliminating the mismatch. However, "copy to drawer" command does not copy the protec
46
User Configuration Mismatch
At least one IDC configuration parameter in the IDC Data Base (XPIC for example) is different than the configuration in the drawers or Auxiliary channels. Raised only after IDC hotswap / software reset.
1) Check the mismatch configuration in the alarms log. 2) Use "Copy drawer to IDC" command to copy the XPIC/protection configuration from the drawer to the IDC (without reset). This will end the mismatch.
46
Protection Mismatch
Internal system mismatch regarding the state of the radio - Mute/Unmute
Reset IDM
46
Mate Configuration Mismatch () M=xx, L=xx
Mismatch in the internal protection configuration between the drawers.
1) Check and compare configuration 2) See mate Configuration Mismatch Alarm
46
46
46
FibeAir® Troubleshooting Guide
29
Trap ID
Description
Probable Cause
46
Mate Configuration Mismatch () M=xx, L=xx
Mismatch configuration between local IDC Database and mate IDC database
46
Mate Configuration Mismatch
Configuartion mismatch between two IDCs in External Protection configuration.
46
Mate Configuration Mismatch
Configuartion mismatch between two drawers in External Protection configuration.
46
Link ID Mismatch on Radio #n Link ID Mismatch
46
Link ID Mismatch
46
Link ID Mismatch
46
IDU Hitless Remote Config Mismatch
46
IDU Hitless Mate Config Mismatch
46
General Hardware Fault #4
46
General Hardware Fault #3
46
General Hardware Fault #2
46
General Hardware Fault #1
46
General Cfg Mismatch
46
46
46
Drawer ID Mismatch in Protecting Carrier
Drawer ID Mismatch
FibeAir® Troubleshooting Guide
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 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)
Corrective Actions 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. 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
30
Trap ID
46
46
47
47 47
47
47
47
Description Device Incompatible Alarm (#103)
Auxiliary Channel User Configuration Mismatch
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
Probable Cause Incomapitibility alarm between link components. Typically refers to mixture of standard and "I" components in the link
Incorrect Auxiliary channel configuration
Corrective Actions
1) Check link components
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
Change Master/Slave command System configured for protection without mate connected Protection switch by external alarm Different faults indicate hardware failure on the drawer
1) Check configuration. 2) Check Mate connected
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.
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) Enable protection or disable hitless
1) Check that cable is connected properly. 2) Replace protection cable. 3) Replace IDCs
48
Protection Communication Error on Cable
48
Protection Cable Disconnected
Protection Cable Disconnected
1) Connect Protection Cable. 2) Replace cable.
48
Protection Cable Disconnect/Error/Power Error/Problem?10;Maste r-Slave Disconnect
Problem with protection cable or the connection between the Master/Slave IDUs
1) Replace cable. 2) Replace IDUs
49 50
Heart Beat (Trap Only) Trib HP: LOM
50
Radio HP: LOM
50
Fiber HP: LOM
51
Hitless Switch Locked to Self Radio By User
51
Hitless Switch Locked to Right Radio By User
FibeAir® Troubleshooting Guide
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.
1) Disable Hitless Lockout
31
Trap ID
Description
Probable Cause
51
Hitless Switch Locked to Mate/Self Radio By User
51
Hitless Switch Locked to Left Radio By User
51
Hitless Self/Mate Receiver in user
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
51
Hitless Left/Right Receiver in Use
Left/Right receiver is used for processing data
51
Hitless Functionality Failure
Hitless protection is not available. The link will fail in case of fade.
52
Unused Radio Receiver LOF
Hitless Self Radio Receiver LOF
52
Own Radio BBLOF on Radio #n
Hitless Self Radio Receiver LOF
Loss of Frame on Unused Left/Right Radio
Permanent Radio LOF in the receiver (raised after 10 consecutive seconds of radio Loss Of Frame). Implies a permanent problem, unlike fading due to multipath condition, which is intermittent in nature.
52
52 53
57
58
Hitless Self Radio Receiver LOF Hitless Cable Disconnect In-Band Radio PPP Link Disconnect?10;In-Band Line PPP Link Disconnect
Wayside Channel Loss of Signal/Carrier
FibeAir® Troubleshooting Guide
Corrective Actions
1) Disable Hitless Lockout
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 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
Hitless Self Radio Receiver LOF Hitless cable disconnected.
Connect hitless cable.
In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected.
1) Check the line connection. 2) Check in-band configuration.
Wayside Channel Loss of Signal/Carrier in internal protection
1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.
32
Trap ID
Description
Probable Cause
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
58
User Channel Ethernet Loss of Carrier
User Left Channel Loss of Carrier
59
ODU-2-ODU Cable Open
ODU-2-ODU Cable Open
Corrective Actions 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. 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 cable. 2) Replace cable.
60
No Signal from ODU
No Rx (140 MHz) signal from RFU
1) Check IF cable and connectors 2) Check N-type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU. For High Power RF Unit: Check BMA connector center pin is not spliced both on RFU and on OCB.
60
Modem Script Not Supported
No modem script is available for this RFU.
1) Upgrade MRMC scripts 2) Replace RFU
FibeAir® Troubleshooting Guide
33
Trap ID
Description
61
Protection Lockout
61
Protection Force Switch
62
RFU Power Supply Failure
Probable Cause "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.
Corrective Actions 1) Disable Lockout
1) Disable "Force Switch"
Replace RFU. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM.
62
RFU Power Failure (Vd)
RFU Power Supply Failure (Vd)
62
RFU Power Failure (6v pro)
RFU Power Supply Failure (6v pro)
1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM.
62
RFU Power Failure (6v pro)
RFU Power Supply Failure (6v pro)
1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM.
62
RFU Power Failure (12v)
RFU Power Supply Failure (12v)
1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM.
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
FibeAir® Troubleshooting Guide
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
34
Trap ID
65
Description
RFU Fan Failure
Probable Cause
Corrective Actions 5) Replace RFU
Fan Failure was detected by RFU
1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fans drawer 5) Replace RFU
66
RFU Low Signal To ODU
RFU is detecting low signal from IDU
1) Check IF cable connectors. 2) Check N-Type connector inner pin is not spliced. 3) Replace IDM. 4) Replace RFU.
67
RFU XPIC Clock Failure
No XPIC clock is received from Master RFU
1) Reconnect XPIC clock cables at both RFUs 2) Replace XPIC cable
RFU Delay Calibration Failure 1
Delay calibration is unseccessfull since RX AGC is unlocked.
1) Check link performance 2) Re-perform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU
RFU Delay Calibration Failure 2
Delay calibration is unseccessfull since wide or deep notch has been detected at the RX signal
1) Check link performance 2) Reperform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU
70
Gigabit Ethernet TX Mute Override
GbE port is enabled by the user but the system overrides this and mutes the port. This alarm may appear in the following cases: Radio LOF (local or remote), Link ID mismatch (local or remote), excessive BER (local or remote), Signal degrade (local or re
1) Check the reason for the alarm (see the Probable Cause column) and correct it accordingly.
70
Gigabit Ethernet SFP TX Fault
SFP does not transmit Ethernet properly.
1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM.
70
Gigabit Ethernet SFP Not Intact
SFP is not connected properly.
71
Encryption Fault
HW encryption fault
72
Encryption Sync Loss
Encryption loss of frame
68
69
FibeAir® Troubleshooting Guide
1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM. 1) Reset IDM. 1) Check link staus. 2) Reset IDM.
35
Trap ID
Description
73
Initial KEP Failed
74
Session Key Timer Elapsed
75
Power-Up Test Failed
76
Conditional Test Failed
77
Encryption Will Turned Off On Next Reset
80
Admin password in default state
Probable Cause 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
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.
81
Link Group #1 N+1 Protection Fault: Protecting Radio Failure
81
Link Group #1 N+1 Protection Fault: Locked by User
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 link status. 2) Reset IDC. 3) Reset IDM. 1)Check link status. 1) Reset IDC. 2) Reset IDM. 1) Reset IDC. 2) Reset IDM.
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. 1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH) Release maintenance command.
81
Link Group #1 N+1 Protection Fault: LocalRemote Group Topology Mismatch
N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.
82
Loss of Protection
There is no power on the standby IDM
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
83
Temp License is Active
Temporary License activated by the user
Load permanent license or disable the temporary license
FibeAir® Troubleshooting Guide
36
Trap ID
84
Description
Ingress Gigabit Ethernet blocked on Radio
84
Egress Gigabit Ethernet blocked on Radio
85
Unknown RFU Type
85
Incompatible RFU TX Calibration
401
Node down.
402
User (from ) failed to login times.
403
Standby serevr failed to connect to main server (the main server is configured as Standalone).
404
No communication between main and standby servers.
405
License expires in less than two weeks.
406
License expired.
407
Network Elements number exceeds the license limit.
FibeAir® Troubleshooting Guide
Probable Cause 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. 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.
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 local radio alarms and solve the radio fault accordingly.
Upgrade IDC's SW. Upgrade IDC's SW.
Open the main server configuration, and in the Redundancy section, change the server roll from Stand Alone to Main Server.
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.
37
Trap ID
Description
408
Failed loading license file.
409
Failed to start the TFTP server on (address already in use).
410
Disconnected User
Probable Cause
Corrective Actions
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.
The license file is probably corrupted. Contact customer support to obtain a new license file.
411
Standby serevr failed to connect to main server (versions mismatch).
This alarm occurs when a secondary standby NMS server tries to connect to a main NMS server,with a different software version.
414
Enabled feature set is not licensed
The enabled feature set is not licensed.
FibeAir® Troubleshooting Guide
Check your system, and disable other TFTP servers.
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.
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: y
155 Mbps Line Interface
y
Wayside Channel Local IDU 101101110...
Equipment 101101110...
Local IDU Interfaces
Modem & IF
to ODU
Local Loop y
Full IDU (all three inputs through the IDU, modulator, and looped in the IF).
FibeAir® Troubleshooting Guide
39
Remote: y
155 Mbps Line Interface
y
Wayside Channel Local IDU 101101110...
Local IDU Interfaces
Equipment 101101110...
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
Remote Terminal
101101110...
Equipment 101101110...
Local IDU
Local ODU
Remote IDU
Modem & IF
Line Interface
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 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.2 192.168.1.3
3200T GNE A Te lne t
SNMP
IP Management Network
192.168.1.17 192.168.1.18 192.168.1.19
3200T NE B PPP / Ethernet 192.168.1.33
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.
FibeAir® Troubleshooting Guide
41
