Download - Trouble Shooting Guide IP 10 1500P Nov
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
1/44
FibeAir
Troubleshooting
Guide
Part ID: BM-0108-0
Doc ID: DOC-00015466 Rev a.01
November 2008
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
2/44
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 writtenauthorization 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.
TradeMarksCeraMap
TM, PolyView
TM, EncryptAir
TM,ConfigAir
TM, CeraMon
TM, EtherAir
TM, 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 orconsequential damage in connection with the furnishing, performance, or use of thisdocument or equipment supplied with it.
Information to User
Any changes or modifications of equipment not expressly approved by the manufacturercould void the users authority to operate the equipment and the warranty for such equipment.
Copyright 2008 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters:Ceragon Networks Ltd.24 Raoul Wallenberg St.Tel Aviv 69719, IsraelTel: 972-3-645-5733Fax: 972-3-645-5499Email: [email protected]
www.ceragon.com
European Headquarters:Ceragon Networks (UK) Ltd.4 Oak Tree Park, Burnt Meadow RoadNorth Moons Moat, Redditch,Worcestershire B98 9NZ, UKTel: 44-(0)-1527-591900Fax: 44-(0)-1527-591903Email: [email protected]
North American Headquarters:Ceragon Networks Inc.10 Forest Avenue,Paramus, NJ 07652, USATel: 1-201-845-6955Toll Free: 1-877-FIBEAIRFax: 1-201-845-5665
Email: [email protected]
APAC HeadquartersCeragon Networks (HK) Ltd.Singapore ROLevel 34 Centennial Tower3 Temasek AvenueSingapore 039190Tel - + 65 6549 7886
Fax: +65 6549 7011
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
3/44
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
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
4/44
FibeAir
Troubleshooting Guide 1
General
Ceragon designed FibeAir to be highly reliable and relatively maintenance free. In the event of a systemfailure, 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 Ceragonwarranty.
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 inIDU/ODU/RFU, or usingmanagement)
Per installationrecords
Align/adjust as required
Torque on antennamount bolts
Tight mount Adjust as required
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
5/44
FibeAir
Troubleshooting Guide 2
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, FastEthernet, 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.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
6/44
FibeAir
Troubleshooting Guide 3
IDU LED Indicators
The following table lists the LEDs on the IDU panel and their functions.
Note: In the tables below, critical and major alarms are red, and minor and warning alarms are yellow.
Color
LEDRed Yello
w
GreenDescription
PWR(Power)
X X Red - power supply problem
LINE X X X Red - no input to main channel / high BER
Yellow - JO mismatch
LOF (Lossof Frame)
X X Red - radio did not recognize informationframe (radio link problem/radio LOF)
BER (BitError Ratio)
X X X Red - radio BER higher than radioexcessive error threshold definition (seeSonet/SDH configuration window)
Yellow - radio BER higher than radiosignal degrade threshold definition (seeSonet/SDH configuration window)
LPBK(Loopback) X X Red - loopback is active
STBY(Standby)
X X Yellow - Protected configuration. The unitis currently passive or Tx mute isoperating
IDU X X X Red - modem unlocked
Yellow - high temperature / fan problem
ODU X X X Red - no link, or ODU power, or ODU/RFUunlocked
Yellow - radio interference, or hightemperature, or Rx/Tx out of range
CBL (Cable) X X Red - RF cable open / RF cable short
RMT(RemoteUnit)
X X X Red - no link / remote unit problem (redLED is lit in the remote unit)
Yellow - warning in remote unit (yellowLED is lit in the remote unit)
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
7/44
FibeAir
Troubleshooting Guide 4
LED Indications for FibeAir IP-10
LED Name Description Severity Color Info Probable Cause Corrective Action
PDHexcessive-ber
E1/T1 excessiveBER on port #%1
Major RedExcessiveBER alarmstatus
1) Line is notproperlyconnected.2) Externalequipment isfaulty.
1) Reconnect line.2) Check linecables.3) Check externalequipment.4) Power cycle thesystem.
PDHloopback-towards-line
E1/T1 loopbacktowards line onport #%1
Major RedLoopbacktowards linealarm status
User configuredsystem toloopback mode.
Cancel loopbackconfiguration.
PDH
loopback-
towards-radio
E1/T1 loopback
towards radio onport #%1
Major Red
Loopback
towards radioalarm status
User configured
system toloopback mode.
Cancel loopbackconfiguration.
PDHloss-of-signal
E1/T1 loss ofsignal on port#%1
Major RedNo signal isdetected onport
1) Line is notproperlyconnected.2) Externalequipment isfaulty.
1) Reconnect line.2) Check linecables.3) Check externalequipment.4) Power cycle thesystem.
PDH signal-degrade
E1/T1 signal
degrade on port#%1
Minor Yellow
Signal
degrade isdetected onport
1) Line is notproperly
connected.2) Externalequipment isfaulty.
1) Reconnect line.2) Check linecables.
3) Check externalequipment.4) Power cycle thesystem.
PDHunexpected-signal
E1/T1unexpectedsignal on port#%1
Warning Yellow
Unexpectedsignal isdetected onport
1) Port is disabled.2) Line isconnected to adisabled port.
1) Enable relevantport.2) Disconnect cablefrom relevant port.
IDUext-in-alarm
%1 Warning Yellow External Alarm Input ---
IDU eth-loc-alarm
Ethernet loss ofcarrier on port#%1
Major Red Ethernet Loss ofCarrier on Port #n
1) FE cable
disconnected2) DefectedFE cable.
1) Check connection
of FE cable.2) Replace FEcable.
IDUeth-tx-mute-alarm
Ethernet Tx muteoverride on port#%1
Major RedEthernet TX MuteOverride
RadioLOF/EXBER/Link ID onlocal orremote side(in pipeapplication)
Check link
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
8/44
FibeAir
Troubleshooting Guide 5
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
IDU gbe-loc-alarmGigabit ethernetloss of carrier onport #%1
Major RedGigabit lossof carrier
1) Cable is notconnected to theport.2) Cable isdefected.
1) Connect cable tothe port.2) Replace cable.
IDU gbe-sfp-alarmGigabit ethernetSFP not inserted
Major RedGigabitEthernet SFPnot intact
SFP is notinserted
1) Check SFPconnector.2) Replace fiber.
IDU gbe-sfp-tx-alarmGigabit ethernetSFP Tx fault
Major RedGigabitEthernet SFPTX Fault
SFP malfunction Replace SFP
IDUgbe-tx-mute-alarm
GBE Tx muteoverride on port#%1
Warning YellowGBE TXMuteOverride
RadioLOF/EXBER/LinkID on local orremote side
Check link
IDUfile-load-error-alarm
Firmware fileload error (%1)
Critical Red
Firmware filewas notsuccessfullyloaded
1) Firmware file ismissing.2) System errorin power up.
1) MoveManagement toport 2.2) Downloadfirmware file.3) Reset system.
IDU file-not-found-alarm Firmware file notfound (%1) Critical Red
Firmware file
was notfound
1) Firmware file ismissing.
1) Download
firmware file.2) Reset system.
IDU alarms-fileAlarm file notfound
Major Red
The system'salarm filewas notfound
The alarm filewas deleted or iscorrupted
Download alarm file
IDUentity-init-fail-alarm
SW error: entityinitializationfailure
Major RedSW failed toproperlyinitialize
SW error duringsystemintialization
Reset system
IDU
extreme-
temperature
IDU extreme
temperatureconditions Warning Yellow
IDU is inextreme
temperaturecondition
The externalcooling/heating
system is notoperating.
Turn on external
cooling/heatingsystems.
IDU fan-failure Fan failure Minor Yellow Fan failure Defective fan unit Replace fan unit
IDUgeneral-hardware-failure
General HWfailure %1
Major Red HW failure Defected HW1) Reset system.2) Replace IDU.
IDU kernel-backupBackup kernel isrunning
Minor YellowBackupkernel isrunning
1) The kernel(/boot/uImage) iscorrupted ormissing
1) Re-install theSW.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
9/44
FibeAir
Troubleshooting Guide 6
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
IDU low-input-voltageLow inputvoltage
Warning YellowLow inputvoltagedetected
Low input to thesystem
1) Check powersupply voltage.
IDUparam-set-fail-alarm
SW error:parameter setfailed
Warning YellowParameterset failure
SW error Reset system
IDUcorrupted-file-
alarm
Inventory file(%1) iscorrupted
Critical RedThe inventoryfile iscorrupted
1) Inventoryfile ismissing.2) Inventoryfile wasfound to becorrupt uponsystempower up.
1) Reset system.2) Downloadinventory file
IDUfile-not-found-alarm
Inventory file(%1) was notfound
Critical RedInventory filewas notfound
1) Inventory file ismissing.
1) Downloadinventory file.2) Reset system.
IDUdemo-license-alarm
Demo license Warning YellowDemo licenseis used bycustomer
1) Demo licenseactivated by user.
1) Terminate demolicense.2) Activateoperational license.
IDUlicense-violation-alarm
License violation%1
Warning YellowLicenseviolation
1) Unit does notmatch licensefeatures set.
1) Check that thecode was enteredcorrectly.2) Call tech supportfor new licensegeneration.
IDUfirmware-file-missing-alarm
Modem firmwarefile not found
Critical RedModem filewas notfound
1) Modem file ismissing.
1) DownloadModem file.2) Reset system.
IDUfirmware-load-error-alarm
Modem was notloadedsuccessfully
Critical RedModem wasnot loadedsuccessfully
1) File is corrupt.2) System failure.
1) Download file.2) Reset system.
IDUfpga-file-currupt-alarm
Radio script(LUT) is corrupt
Critical RedRadio scriptLUT is notvalid
1) Faulty file.1) Download radioscript LUT.
IDUfpga-file-not-found-alarm
Radio script(LUT) not found
Critical RedRadio scriptLUT notfound
1) File was notdownloaded tosystem.
1) Download radioscript.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
10/44
FibeAir
Troubleshooting Guide 7
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
IDUincompatible-script-alarm
Incompatiblescript: %1 %2
Critical Red
Incompatibility betweenRFU andloaded radioscript
1) Incompatibilitybetween RFUand loaded radioscript.
1) Change RFU.2) Change Raidoscript.
IDUmodem-script-file-corrupt-alarm
Radio script iscorrupt
Critical RedRadio scriptis not valid
File is corrupt Download file
IDUmodem-script-file-not-found-alarm
Radio script notfound
Critical RedRadio scriptnot found
File not found Download file
IDU mrmc-file-corrupt-alarm
MRMC file iscorrupt
Critical Red MRMC filenot valid
File is corrupt Download file
IDUmrmc-file-not-found-alarm
MRMC file notfound
Critical RedMRMC filenot found
File not found Download file
IDUrfu-file-corrupt-alarm
RFU file iscorrupt
Critical RedRFU file notvalid
File is corrupt Download file
IDUrfu-file-not-found-alarm
RFU file notfound
Critical RedRFU file notfound
File not found Download file
IDU if-loopback-alarm IF loopback Warning YellowIF loopbackinitiated
1) User enabledIF loopback.
1) Disable IFloopback.
IDU lock-detect-alarm IF lock detection Critical RedIFsynthesizerunlock
1) Extremetemperaturecondition.2) HW failure.
1) Checkinstallation.2) Reset IDU.
IDU cable-open Cable open Major Red
Cablebetween IDUand RFU isnot properlyconnected
1) Cable is notconnected to IDUor RFU.
1) Check IF cableand connectors.2) Verify that N-Type connectorinner pin is notspliced.3) Replace IDU.4) Replace RFU.
IDU cable-short Cable short Major RedThere is ashort in the IFcable
1) Physical shortat the IF cable.
1) Check IF cableand connectors.2) Verify that N-Type connectorinner pin is notspliced.3) Replace IDU.4) Replace RFU.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
11/44
FibeAir
Troubleshooting Guide 8
LED Indications for FibeAir IP-10 - Continued
LED AlarmName Description Severity Color Alarm Info Probable Cause Corrective Action
IDU cfm-failureEthenet servicesfailure
Warning YellowEthenetservicesfailure
1) Local MEPerror indication.2) Remote MEPerror indication.3) Remote MEPloss ofconnectivity.
1) Check MAIDdefinitions.2) Check remoteMEP definitions.3) Check local MEPdefinitions.4) Run "CFMtraceroute" to theremote MEP thenperform "CFM ping"to each MP(MaintenancePoint) in order tofind the brokenpoint.
Protectioncable-disconnected-alarm
Mate IDU cableis not connected
Major Red
Protectioncable is notproperlyconnected
1) Cable is notconnectedbetweenprotection ports.2) Cable isconnected towrong port.3) Cable is
damaged.
1) ConnectEthernet cable toprotection port ofboth IDUs.2) Replace cable.
Protectionconfiguration-mismatch-alarm
Mate IDUconfigurationmismatch
Major Red
Mismatchbetween IDUin Protectionmode
1) RFUproperties are notidentical.2) Radio scriptsare not identical.
1) Change RFU.2) Downloadrequired radioscript.
Protectionforce-switch-alarm
Protection forceswitch
Warning YellowForce switchcommandwas issued
1) Usercommand - ForceProtection Switch
1) Clear ForceSwitch Command.
Protectionipi-xml-file-alarm
Protection SWactivity fault
Warning YellowSW fault inProtection
mechanism
1) SW fault insynchronization
of databases
1) Reset Standbyunit.
Protectionlockout-alarm
Protectionlockout
Major Red
ProtectionLockoutcommandwas isused
User issuedProtectionLockout
Clear Lockoutcommand
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
12/44
FibeAir
Troubleshooting Guide 9
LED Indications for FibeAir IP-10 - Continued
LED AlarmName Description Severity Color Alarm Info Probable Cause Corrective Action
Protectionmate-comm-failure-alarm
Mate IDUcommunicationerror
Major Red
IDU cannotcommunicatewith its mateIDU
1) IDU IPaddresses areidentical.2) IDUs IP subnetis not identical.3) ProtectionCable is notproperlyconnected.4) ProtectionCable isdamaged.
1) Check Protectioncable connectivity.2) ReplaceProtection cable.
Radioradio-excessive-ber
Radio excessiveBER
Major RedExcessiveBER on radio
1) Fade in thelink.2) Defected IFcable.3) Fault in RFU.4) Fault in IDU.
1) Check linkperformance.2) Check IF cable,and replace ifrequired.3) Replace RFU.4) Replace IDU.
Radioradio-link-id-mismatch
Link IDmismatch
Critical RedLink IDMismatchAlarm
Link ID is not thesame at bothsides of link
Configure sameLink ID for bothsides of link.
Radio radio-lofRadio loss offrame
Critical RedLoss OfFrame onradio
1) Fade in thelink.2) Defected IFcable.3) Fault in RFU.4) Fault in IDU.
1) Check linkperformance.2) Check IF cable,and replace ifrequired.3) Replace RFU.4) Replace IDU.
Radioradio-signal-degrade
Radio signaldegrade
Minor YellowSignalDegrade onradio
1) Fade in thelink.2) Defected IFcable.3) Fault in RFU.
4) Fault in IDU.
1) Check linkperformance.2) Check IF cable,and replace ifrequired.
3) Replace RFU.4) Replace IDU.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
13/44
FibeAir
Troubleshooting Guide 10
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
Remoteremote-communication-failure
Remotecommunicationfailure
Major Red
RemoteCommunication FailureAlarm
1) Fade in thelink.
1) Check linkperformance.
RFUincompatible-rfu-tx-calibration
IncompatibleRFU TXcalibration
Major Red
RFUcalibrationtables requireIDC SWupgrade
RFU calibrationtables requireIDC SW upgrade.
Upgrade IDU's SW.
RFUcommunication-failure
RFUcommunicationfailure
Warning Yellow
Failure incommunication betweenIDU and RFU
1) Defected IFcable.2) IF cable notconnectedproperly.3) Defected IDU.4) Defected RFU.
1) Check IF cableand connectors.2) Verify that N-Type connectorinner pin is notspliced.3) Replace IDU.4) Replace RFU.For High Power RFUnit:1) Check BMAconnector on OCB2) Check BMAconnector on RFU
RFUdelay-calibration-failure-1
RFU delaycalibrationfailure 1
Warning YellowRX AGC isnot locked
Defective RFU1) Reset the IDU /RFU.2) Replace RFU.
RFUdelay-calibration-failure-2
RFU delaycalibrationfailure 2
Warning Yellow
Calibrationcannot becompleteddue to notchdetection
Calibrationcannot becompleted due tonotch detection
Enter delaycalibration valuemanually
RFUextreme-temp-
cond
RFU extreme
temperatureWarning Yellow
RFUtemperature
is too high orlow
1) Installationconditions.
2) DefectiveRFU.
1) Checkinstallationconditions.2) Verify operationas per product'sspecs.3) Replace RFU.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
14/44
FibeAir
Troubleshooting Guide 11
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
RFU fan-failure RFU fan failure Warning YellowRFU FanFailure Alarm
1) Defective /non-existent fandrawer.2) DefectiveRFU-to-fandrawerconnection.3) DefectiveRFU.
1) Check RFUconnection to BP 2)Check that fans areconnected to PS3) Replace RFU BPcable4) Replace specificfan or fan drawer5)Replace RFU
RFUhardware-failure-
1
RFU hardware
failure 1Critical Red
RFUHardware
Failure 1Alarm
1) Defective
RFU.1) Replace RFU.
RFUhardware-failure-2
RFU hardwarefailure 2
Critical Red
RFUHardwareFailure 2Alarm
1) DefectiveRFU.
1) Replace RFU.
RFUlow-if-signal-to-rfu
Low IF signal toRFU
Major Red
RFU isdetecting lowsignal fromIDU
1) IF cableconnection.2) DefectiveRFU.
3) Defective IDU.
1) Check IF cableconnectors.2) Verify that N-Type connectorinner pin is notspliced.
3) Replace IDU.4) Replace RFU.
RFU no-signal-from-rfuNo signal fromRFU
Major Red
IDU is notdetecting asignal fromthe RFU
No RX (140 MHz)signal from RFU.
1) Check IF cableand connectors.2) Verify that N-Type connectorinner pin is notspliced.3) Replace IDU.4) Replace RFU.For High Power RFUnit:
Check BMAconnector centerpin is not splicedboth on RFU andon OCB.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
15/44
FibeAir
Troubleshooting Guide 12
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
RFUpa-extreme-temp-cond
RFU PAextremetemperature
Warning YellowRFU PAExtremeTemperature
1) Installationconditions.2) DefectiveRFU.
1) Checkinstallationconditions.2) Replace RFU
RFU power-failure-12vRFU powerfailure (12v)
Major RedRFU PowerFailure (12v)Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.3) Replace IDU.
RFU power-failure-1point5
RFU powerfailure (1.5v)
Major RedRFU PowerFailure (1.5v)Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IF
cable/connector.2) Replace RFU.3) Replace IDU.
RFU power-failure-24vRFU powerfailure (24v)
Major RedRFU PowerFailure (24v)Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.3) Replace IDU.
RFU power-failure-6vRFU powerfailure (6v pro)
Critical RedRFU PowerFailure (6v
pro) Alarm
1) Defective IFcable/connector.2) Defective
RFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.
3) Replace IDU.
RFUpower-failure-6v-sw
RFU powerfailure (6v SW)
Major RedRFU PowerFailure (6vSW) Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.3) Replace IDU.
RFUpower-failure-minus-5v
RFU powerfailure (-5v)
Major RedRFU PowerFailure (6vpro) Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.3) Replace IDU.
RFU power-failure-vdRFU powerfailure (Vd)
Critical RedRFU PowerFailure (Vd)Alarm
1) Defective IFcable/connector.2) DefectiveRFU.3) Defective IDU.
1) Replace IFcable/connector.2) Replace RFU.3) Replace IDU.
RFUrfu-loopback-active
RFU loopback Major RedRFUloopbackAlarm
1) User action.1) Disable RFUloopback.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
16/44
FibeAir
Troubleshooting Guide 13
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
RFUrfu-power-supply-failure
RFU powersupply failure
Major RedRFU powersupply failure
At least one ofthe PSU voltagesis too low.
1) Replace RFU.
RFUrx-level-out-of-range
Rx level out ofrange
Warning YellowRFU RXLevel Out ofRange
RSL is very low(typically below -80 dBm), link isdown.For RFU-C:RSL is too Low(typically below -83dBm) or
RSL is too High(typically above -26dBm).
1) Check antennaalignment & linkplanning.2) Check linksettings (TX power,TX freq).3) Check antennaconnections.4) Replacelocal/remote RFU.
RFUrx-level-path1-out-of-range
RFU Rx levelpath1 out ofrange
Warning YellowRFU RxLevel Path1Out of Range
1) Improperinstallation.2) Fading event.3) DefectiveRFU.
1) Check that thefault is not due torain/multi-pathfading or lack ofLOS.2) Check linksettings (TX power,TX freq).3) Check anttena
alignment.4) Check antennaconnections5) Replacelocal/remote RFU.
RFUrx-level-path2-out-of-range
RFU Rx levelpath2 out of
range
Warning YellowRFU RxLevel Path2
Out of Range
1) Improperinstallation.2) Fading event.
3) DefectiveRFU.
1) Check that thefault is not due torain/multi pathfading or lack ofLOS.2) Check linksettings (TX power,TX freq).
3) Check anttenaalignment.4) Check antennaconnections5) Replacelocal/remote RFU.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
17/44
FibeAir
Troubleshooting Guide 14
LED Indications for FibeAir IP-10 - Continued
LED Alarm Name Description Severity Color Alarm Info Probable Cause Corrective Action
RFUsynthesizer-1-unlocked
Synthesizer 1unlocked
Major RedRFUsynthesizer isunlocked
1) DefectiveRFU.2) DefectiveXPIC cableconnection.
1) Replace XPICcable.2) Replace RFU.
RFUsynthesizer-2-unlocked
Synthesizer 2unlocked
Major RedRFUsynthersizeris unlocked
1) DefectiveRFU.2) DefectiveXPIC cableconnection.
1) Replace XPICcable.2) Replace RFU.
RFUsynthesizer-3-unlocked
Synthesizer 3unlocked
Major RedRFUsynthesizer isunlocked
1) DefectiveRFU.2) DefectiveXPIC cableconnection.
1) Replace XPICcable.2) Replace RFU.
RFUsynthesizer-unlocked
Synthesizerunlocked
Major Red
One of theRFUSynthesizersis Unlocked
One of the RFUsynthesizers isunlocked.
1) Replace RFU.2) In XPIC mode,replace mate RFUas well.
RFUtx-level-out-of-range
Tx level out ofrange
Minor YellowRFU TXLevel Out of
Range
1) Defective RFU(the RFU cannottransmit the
requested TXpower)
1) Replace RFU.2) Intermediatesolution - reduce
TX power.
RFU tx-mute Tx mute Warning Yellow RFU TX MuteRFU Transmittermuted by user.
Unmute the RFUtransmitter.
RFU unknown-rfu-typeIDU SW doesnot support thistype of RFU
Major Red
IDC's SWdoesn'tsupport theRFU
IDC's SW doesn'tsupport the RFU.
Upgrade IDC SW.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
18/44
FibeAir
Troubleshooting Guide 15
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 notin 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.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
19/44
FibeAir
Troubleshooting Guide 16
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 singlemode 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
0Insufficient SystemConfiguration for FullXPIC Support
One of the system elementsdoes not support XPIC.Or, the system is missing oneof the needed elements.
1) Check the Block Radio commandstatus on the protectionconfiguration.2) Check the remote radio alarmsand solve the radio fault accordingly
10ODU 5/8/12/-12V PowerSupply Failure
One of the system elementsdoes not support XPIC.Or, the system is missing oneof the needed elements.
1) Check the Block Radio commandstatus on the protectionconfiguration.2) Check the remote radio alarmsand solve the radio fault accordingly
11Synthesizer #1/2/3Unlocked
One of the RFU synthisizersis unlocked.
Replace RFU.For non RFU-C radios:In XPIC configuration, it might bethat theRFU is taking the synch from themate RFU.In this case, check if alarm persistsin non-XPIC configuration.
12 Tx Mute On/OffRFU transmitter muted byuser
Unmute the RFU transmitter.
12 Tx Level Out of RangeThe RFU cannot transmit therequested Tx power.
1) Replace RFU.2) Intermediate solution - reduce TX
power.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
20/44
FibeAir
Troubleshooting Guide 17
Trap ID Description Probable Cause Corrective Actions
13 Rx Level Out of Range
RSL is very low (typicallybelow -80 dBm), link is down.
For RFU-C:RSL is too Low (typicallybelow -83dBm) orRSL is too High (typicallyabove -26dBm).
1) Check antennas alignment & linkplanning.
2) Check link settings (TX power,TXfreq).3) Check antenna connections.4) Replace local/remote RFU.
14ODU Temperature Outof Range
RFU temperature toohigh/low.
1) Check installation conditions.2) Replace RFU.
15 XPIC Cable Swap
Left/Right cables swap inXPIC configuration. If???Drawer ID Mismatch???(see above) alarm isidentified in both drawers, theIF (coax) cables between the
drawers and ODUs on oneend are swapped.
1) Verify correct cable connection.Recommended connection is V toRight drawer and H to Left drawer
15 Power Input #2 is DownSubrack redundant powerfeed failure.
1) Verify if the Power Input cardexists in the subrack.2) Check if Power Input connectedto -48 VDC supply.3) Check -48 VDC supply to thesubrack.4) Replace Power Input card ifproblem still exists.5) Disable Power Input
15 Power Input #1 is DownSubrack redundant powerfeed failure.
1) Verify if the Power Input cardexists in the subrack.2) Check if Power Input connectedto -48 VDC supply.3) Check -48 VDC supply to thesubrack.4) Replace Power Input card ifproblem still exists.5) Disable Power Input
15IDU 5/8/3.3/-5V PowerSupply Failure
Failure in an IDU powersupply.
1) Check -48 VDC supply to theIDU.2) Replace IDU.
15 Drawer Power On/Off Drawer power on/off.
15Drawer Internal PowerFailure (Board #2)
Board #1 - MUX card. Board#2 - Modem card. This alarmmay also be generated if adrawer in Internal Protectionwas switched off.
1) Switch off/on IDM.2) Replace IDM.
15Drawer Internal PowerFailure (Board #1)
Drawer Internal Power Failure(Board #1)
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
21/44
FibeAir
Troubleshooting Guide 18
Trap ID Description Probable Cause Corrective Actions
16Extension LinkCommunication Failure
Problem with extension cableor the connection betweenthe two subracks.
1) If extended mode is not in use,configure all IDCs in the subrack as
"1 subrack out of 1".2) If extended mode is in use, verifythat the other subrack is configuredto extension mode properly.3) Check that the XC boards in bothsubracks are
16 Cable Short IDM-RFU cable short.
1) Check IF cable and connectors.2) Check N-Type connector innerpin is not spliced.3) Replace IDM.4) Replace RFU.
16 Cable Open/Short IDU-ODU cable open/short.
1) Check IF cable and connectors.2) Check ODU's N-type connectorinner 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 innerpin is not spliced.3) Replace IDM.4) Replace RFU.
17 MRMC=???value???Script File is Missing
Multi-Rate Multi-Constellation
configuration script for thespecified capacity/modulationis missing in the IDC.
1) Download the Modem script tothe IDC and reset the IDM.
17Drawer InternalHardware Intact/FailureBoard#1
Drawer hardware intact ok /failure (Mux)
1) In case of failure, replace IDM.
18IDU Temperature Out ofRange
IDU Temperature Out ofRange
1) Check installation conditions.2) Replace IDM.
18 Fan Failure Fan Failure 1) Replace fan.
19XC Internal Loopback onLine #5
XC board Internal portloopback
1) Disable loopback
19XC Internal Loopback onLine #4
XC board Internal portloopback
1) Disable loopback
19XC Internal Loopback onLine #3
XC board Internal portloopback
1) Disable loopback
19XC Internal Loopback onLine #2
XC board Internal portloopback
1) Disable loopback
19XC Internal Loopback onLine #1
XC board Internal portloopback
1) Disable loopback
19Wayside ChannelLoopback
Wayside Line loopbackapplied by user in internalprotection
Disable Wayside line loopback
19Wayside ChannelLoopback
Wayside Left Line loopbackapplied by user
Disable Wayside line loopback
19ODU Internal Loopback
(Not) Active
RFU loopback applied by
user
Disable loopback
19Internal Loopback onFiber #n
Internal loopback on Fiber Disable loopback
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
22/44
FibeAir
Troubleshooting Guide 19
Trap ID Description Probable Cause Corrective Actions
19
IDU Remote Loopback(Not) Active ?10;IDU
Line Loopback (Not)Active?10;E1\T1\E3\DS3#n Internal Loopback(Not) Active?10;E1\T1\E3\DS3 #n ExternalLoopback (Not) Active
Loopback applied by user Disable loopback
19IDU Local Loopback(Not) Active
IDU IF loopback applied byuser
Disable loopback
19Gigabit Ethernet InternalLoopback
Gigabit Ethernet InternalLoopback applied by user.
Disable Gigabit Ethernet InternalLoopback
19External Loopback onFiber #n
IDU Line loopback applied byuser
1) Disable loopback
19
E1\T1 Internal Loopback
on Port #n
IDU Line loopback applied by
user 1) Disable loopback
19E1\T1 ExternalLoopback on Port #n
E1/T1 External loopback 1) Disable loopback
20Remote CommunicationFailure
No communication betweenthe IDUs over the link.
1) Verify link is up and no errorsover the link.2) Check in-band managementconfiguration.
21PRBS Test is Runningon Radio
PRBS test started. Disable PRBS test.
21Link Group #1 N+1Protection Fault: Lockedby User
Lockout or Force Switch toProtecting Link Groupmaintenance commandactivated.
Release maintenance command.
22 Trib RS: LOF Trib RS: LOF
22Radio RS: LOF (SDH)Radio Section: LOF(Sonet)
Loss Of Frame alarm on theradio, link is down
1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TX power,TX freq).3) Verify no interference.4) Use loopbacks to identify source.5) Replace IDMs/ODUs
22 Radio RS: LOF Radio RS: LOF (ADM)
1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TX power,
TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs.
22Link Group #1 N+1Protection Fault:Protecting Radio Failure
N+1 Link Group protectiondegraded due to Loss OfFrame or Loss Of Signalalarm on the radio portdetected by XC board.
1) Check Protecting Radio moduleis powered on and operatesproperly.2) Replace faulty module.3) see Radio RS: LOF (SDH)
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
23/44
FibeAir
Troubleshooting Guide 20
Trap ID Description Probable Cause Corrective Actions
22 Fiber RS: LOF (SDH)Fiber Section: LOF(Sonet)
Loss Of Frame alarm on theline input.
1) Check line input.2) Check fibers/cables.
3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/IDU is ok.5) Replace IDM.
22Fiber RS: LOF (SDH)Fiber Section: LOF(Sonet)
Loss Of Frame alarm on theline input
1) Check line input.2) Check fibers/cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/IDU is ok.5) Replace IDU.
22 Fiber RS: LOF Fiber RS: LOF (ADM)
1) Check that the fault is not due to
other alarms that can lead to LOF.2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs
23 Trib RS: LOS Trib RS: LOS
23Loss of Signal on Fiber#n
Loss Of Signal alarm on theline input
1) Check line input.2) Check fibers/cables.3) Verify that end equipmenttransmits properly.
4) Use line loopbacks to confirmthat input/IDU is ok.5) Replace IDM.
23Gigabit Ethernet Loss ofSignal
Gigabit Ethernet Loss ofSignal
1) Check line input.2) Check fiber.3) Verify end equipment transmitsproperly.4) Replace IDM.
23
Fiber RS: LOSor?10;E1\T1\E3\DS3 #nLoss of Signal?10;Fiber
RS: LOS
Loss Of Signal alarm on theline input
1) Check line input.2) Check fibers/cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirm
input/IDU is ok.5) Replace IDU.
23Fast Ethernet Loss ofCarrier on Port #n
Fast Ethernet Loss of Carrier
1) Check line input.2) Check cable.3) Verify end equipment transmitsproperly.4) Replace IDM.
23Fast Eth. #01/02 Loss ofCarrier
Fast Ethernet Loss of Carrier
1) Check line input.2) Check cable.3) Verify end equipment transmitsproperly.4) Replace IDU.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
24/44
FibeAir
Troubleshooting Guide 21
Trap ID Description Probable Cause Corrective Actions
23 E1\T1 Loss of Signal onPort #n
E1\T1 Loss of Signal
1) Check line input.2) Check fibers/cables.
3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/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
24Trace IdentifierMismatch on Fiber #n
Trace Identifier Mismatchalarm (J0 mismatch).
Verify J0 settings in the IDU and inthe end equipment.
24 Radio LP #n: TIM Radio LP: TIM
24 Radio HP: TIM Radio HP: TIM
24 Fiber RS: TIM Fiber RS: TIM24 Fiber RS: TIM Fiber RS: 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
25Trib LP #n ExcessiveBER
Trib LP #n Excessive BER
25 Trib HP: Excessive BER Trib HP: Excessive BER
25Radio RS: ExcessiveBER
Radio RS: Excessive BER(Regenerator)
25Radio RS: ExcessiveBER
Radio RS: Excessive BER(Regenerator)
25Radio RS: ExcessiveBER
Radio RS: Excessive BER(ADM)
25Radio MS: ExcessiveBER
Radio MS: Excessive BER
25Radio LP #n: ExcessiveBER
Radio LP: Excessive BER
25Radio HP: ExcessiveBER
Radio HP: Excessive BER
25Fiber RS: ExcessiveBER
Fiber RS: Excessive BER(Regenerator)
25 Fiber RS: ExcessiveBER Fiber RS: Excessive BER(Regenerator)
25Fiber RS: ExcessiveBER
Fiber RS: Excessive BER(ADM)
25Fiber MS: ExcessiveBER
Fiber MS: Excessive BER
25Fiber LP #n ExcessiveBER
Fiber LP #n Excessive BER
25Fiber HP: ExcessiveBER
Fiber HP: Excessive BER
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
25/44
FibeAir
Troubleshooting Guide 22
Trap ID Description Probable Cause Corrective Actions
25Excessive BER onRadio #n
Major radio Excessive BERalarm
1) Check that the fault is not due toother alarms that can lead to LOF.
2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs
25Excessive BER on Fiber#n
Major line Excessive BERalarm
1) Check line input.2) Check fibers/cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/IDU is ok.5) Replace IDM.
25 E1\T1\E3\DS3 #nExcessive BER
E3/DS3 Excessive BER
25E1\T1\E3\DS3 #nExcessive BER
E1/T1 Excessive BER
25E1\T1 Excessive BERon Port #n
Major Excessive BER alarmon E1/T1 port
1) Check line input.2) Check cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/IDM is ok.5) Replace IDM.
26 Trib RS: Signal Degrade Trib RS: Signal Degrade
26 Trib MS: Signal Degrade Trib MS: Signal Degrade
26Trib LP #n SignalDegrade
Trib LP #n Signal Degrade
26 Trib HP: Signal Degrade Trib HP: Signal Degrade
26Signal Degrade onRadio #n
Minor radio BER alarm
1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs
26Signal Degrade on Fiber#n
Minor line SD BER alarm
1) Check line input.
2) Check fibers/cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirmthat input/IDU is ok.5) Replace IDM.
26Radio RS: SignalDegrade
Radio RS: Signal Degrade
26Radio RS: SignalDegrade
Radio RS: Signal Degrade
26Radio RS: SignalDegrade
Radio RS: Signal Degrade
26
Radio MS: Signal
Degrade Radio HP: Unequipped
26Radio LP #n: SignalDegrade
Radio LP #n: Signal Degrade
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
26/44
FibeAir
Troubleshooting Guide 23
Trap ID Description Probable Cause Corrective Actions
26Radio HP: SignalDegrade
Radio HP: Signal Degrade
26 Fiber RS: SignalDegrade
Fiber RS: Signal Degrade(ADM)
26Fiber RS: SignalDegrade
Fiber RS: Signal Degrade
26Fiber RS: SignalDegrade
Minor line BER alarm
1) Check line input.2) Check fibers/cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirminput/IDU is ok.5) Replace IDU.
26Fiber MS: SignalDegrade
Fiber MS: Signal Degrade
26 Fiber LP #n SignalDegrade
Fiber LP #n Signal Degrade
26Fiber HP: SignalDegrade
Fiber HP: Signal Degrade
26E1\T1\E3\DS3 #n SignalDegrade
E3DS3 Signal Degrade
26E1\T1\E3\DS3 #n SignalDegrade
E3DS3 Signal Degrade
26E1\T1 Signal Degradeon Port #n
Minor BER alarm on E1/T1port
1) Check line input.2) Check cables.3) Verify end equipment transmitsproperly.4) Use line loopbacks to confirm
input/IDM is ok.5) Replace IDM.
27 Trib MS: AIS Trib MS: AIS
27 Trib LP #n: AIS Trib LP #n: AIS
27 Trib HP: AIS Trib HP: AIS
27 Radio MS: AIS Radio MS: AIS
27 Radio LP #n: AIS Radio LP #n: AIS
27 Radio HP: AIS Radio HP: AIS
27 Fiber MS: AIS Fiber MS: AIS
27 Fiber LP #n: AIS Fiber LP #n: AIS
27 Fiber HP: AIS Fiber HP: AIS
28 Trib RS: UnexpectedSignal
Trib RS: Excessive BER
28Gigabit EthernetUnexpected Signal
GbE port is disabled but GbEdata is detected.
1) Enable GbE port, disable GbEport of the source, or disconnect thefiber
28Fiber RS: Unexpected?10;E1\T1\E3\DS3 #nUnexpected Signal
Unexpected signal on the lineinput. Port disabled but line isconnected.
1) Enable line port or disconnectline
28Fast EthernetUnexpected Signal onPort #n
Fast Ethernet UnexpectedSignal on Port #n
30 Trib LP #n: LOP Trib LP #n: LOP
30 Trib HP: LOP Trib HP: LOP30 Radio LP #n: LOP
Radio LP: Loss of pointer(LOP) alarm occurs.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
27/44
FibeAir
Troubleshooting Guide 24
Trap ID Description Probable Cause Corrective Actions
30 Radio HP: LOPRadio HP: Loss of pointer(LOP) alarm occurs.
30 Fiber LP #n: LOP Fiber LP: Loss of pointer(LOP) alarm occurs.
30 Fiber HP: LOPFiber HP: Loss of pointer(LOP) alarm occurs.
31 Trib MS: RDI Trib MS: RDI
31 Trib LP #n: RDI Trib LP #n: RDI
31 Trib HP: RDI Trib HP: RDI
31 Radio MS: RDIRadio MS: Remote DefectIdentifier signal (RDI) occurs.
31 Radio LP #n: RDIRadio LP: Remote DefectIdentifier signal (RDI) occurs.
31 Radio HP: RDIRadio HP: Remote Defect
Identifier signal (RDI) occurs.
31 Fiber MS: RDIFiber MS: Remote DefectIdentifier signal (RDI) occurs.
31 Fiber LP #n: RDIFiber LP: Remote DefectIdentifier signal (RDI) occurs.
31 Fiber HP: RDIFiber HP: Remote DefectIdentifier signal (RDI) occurs.
32 Trib LP #n: PLM Trib LP #n: PLM
32 Trib HP: PLM Trib HP: PLM
32 Radio LP #n: PLMRadio LP: Payload LabelMismatch (PLM) occurs.
32 Radio HP: PLM Radio HP: Payload LabelMismatch (PLM) occurs.
32 Fiber LP #n: PLMFiber LP: Payload LabelMismatch (PLM) occurs.
32 Fiber HP: PLMFiber HP: Payload LabelMismatch (PLM) occurs.
33 Trib LP #n: Unequipped Trib LP #n: Unequipped
33 Trib HP: Unequipped Trib HP: Unequipped
33Radio LP #n:Unequipped
Radio LP: Unequipped
33 Radio HP: Unequipped Radio HP: Unequipped
33Fiber LP #n:
UnequippedFiber LP: Unequipped
33 Fiber HP: Unequipped Fiber HP: Unequipped
34 External AlarmExternal alarm input #1configured and triggered byuser.
35 External AlarmExternal alarm input #2configured and triggered byuser.
36 External AlarmExternal alarm input #3configured and triggered byuser.
37 External AlarmExternal alarm input #4configured and triggered byuser.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
28/44
FibeAir
Troubleshooting Guide 25
Trap ID Description Probable Cause Corrective Actions
38 External AlarmExternal alarm input #5configured and triggered by
user.
39 External AlarmExternal alarm input #6configured and triggered byuser.
40 External AlarmExternal alarm input #7configured and triggered byuser.
41 External AlarmExternal alarm input #8configured and triggered byuser.
42 XPIC Cable Swap
Internal IDC to IDCcommunication failurebetween modules requied forLink Group protection service.
1) Check that IDC #n is power upand finished initialization.2) Check & configure both IDCswith proper system configuration:System Type, Subrack#, SubrackIP Base Address, Link GroupTopology.3) Check for Hardware fault:Subrack Auxiliary module
42XC FPGA File isMissing
XC firmware file is missing inthe 2-floor IDC.
1) Download XC firmware file of therequired type and reset the IDC.
42Wayside Firmware Fileis Missing
Wayside firmware file ismissing in the IDC.
1) Download Wayside firmware fileto the IDC and reset the IDC.
42 Subrack Auxiliary FPGAFile is Missing
Subrack Auxiliary firmwarefile is missing in the 2-floorIDC.
1) Download Subrack Auxiliaryfirmware file and reset the IDC.
42Secondary Clock SourceFailure
Secondary Clock SourceFailure
42Radio Card #n PoweredDown
Radio module pertained toLink Protection group ispowered down or extracted.
1) Check if Radio module isinserted properly in the subrack andis powered on. Replace module iffaulty.
42Primary Clock SourceFailure
Primary Clock Source Failure
42MUX Firmware File isMissing
A Mux FW file is missing fromthe system.
Load the required FW file, and resetsystem.
42Modem Firmware File isMissing
A Modem FW file is missingfrom the system.
Load the required FW file, and resetsystem.
42
Link Group #1 N+1Protection Fault: XCPeer CommunicationFailure
N+1 Link Group protectiondegraded due to peer XCcommunication fault.
1) Verify Protection Radio link is upand, no errors over the link.2) Check that remote IDU isproperly configured for N+1 LinkGroup protection.3) Check that remote IDU hasproperly operational XC board.4) Check that Protection Radio linkterminates
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
29/44
FibeAir
Troubleshooting Guide 26
Trap ID Description Probable Cause Corrective Actions
42
Link Group #1 N+1Protection Fault:
Protecting Radio FailureXC Card Fault
N+1 Link Group protectiondegraded due to XC cardfault.
1) Check if XC module is poweredon and no other alarm related to XC
is active.2) Replace XC module.
42
Link Group #1 N+1Protection Fault: Local-Remote ProtectionMismatch
N+1 Link Group protectiondegraded due to Local-Remote Protection Mismatch.
1) Check that remote IDU isproperly configured with N+1 LinkGroup topology.2) Check that remote IDU has allN+1 Link Group protection relatedline modules operational.
42Line Card #n PoweredDown
Line module pertained to LinkProtection group is powered
down or extracted.
1) Check if the card is insertedproperly in the subrack.2) Check if own or redundant powersupply / Radio module
(in drawer #1) is powered on.Replace module if faulty.
42Line Card #1 PoweredDown
Line module in carrrier #1 ofthe Link Protection group ispowered down or extracted.
1) Check if the card is insertedproperly in the subrack.2) Check if own or redundant powersupply / Radio module is poweredon.3) Replace module if faulty.
42 License Fault
The MRMC loaded to thesystem is not supported bythe license, or the ACMfunction is enabled while not
supported by the license.The link is not operative.
Load another MRMC with bit ratesupported by the license
42IDU-ODU InnerCommunication Failure
IDC cannot communicate withODC card.
1) Check ODU connection to theIDU.2) Check IF cable and connectors.3) Check ODU's N-type connectorinner pin is not spliced (if yes,replace ODU).4) Replace ODU.5) Replace IDU.
42IDU-MUX InnerCommunication Failure
IDC cannot communicate withMUX card, MUX card upload
failure.
1) Reset IDU.2) Verify correct SW version.3) Verify correct interfaces.
4) Replace IDU.
42General Hardware Fault#9
Upper IDM Board (MUX orXC) EEPROM inventoryinformation CRC error
1) Try SW Reset affected module /IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.
42General Hardware Fault#8
Upper IDM Board (MUX orXC) EEPROM read accesserror
1) Try SW Reset affected module /IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
30/44
FibeAir
Troubleshooting Guide 27
Trap ID Description Probable Cause Corrective Actions
42 General Hardware Fault#7
FPGA load failure - SubrackAuxiliary board.
1) Download correct SubrackAuxiliary FW file to 2-floor IDC, and
then extract and re-insert SubrackAuxiliary board2) Replace Subrack Auxiliarymodule.3) Replace 2-floor IDC.
42General Hardware Fault#7
FPGA load failure - Modem
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.
42General Hardware Fault#6
FPGA load failure - Mux
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.
3) Replace IDC.
42General Hardware Fault#5
DAC failure
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.
42General Hardware Fault#4
IDU XPIC HW fault
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.
42General Hardware Fault#3
XO failure - Mux board
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.
3) Replace IDC.
42General Hardware Fault#2
XO failure - Modem board
1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.
42General Hardware Fault#11
Wrong card type detected inSubrack Auxiliary slot.
1) Replace Subrack Auxiliarymodule.
42General Hardware Fault#11
Lower IDM Board (Modem orXC) EEPROM inventoryinformation CRC error
1) Try SW Reset affected module /IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.
42General Hardware Fault#10
Subrack Auxiliary EEPROMchecksum failure.
1) Extract and re-insert SubrackAuxiliary module.2) Replace Subrack Auxiliarymodule.
42General Hardware Fault#10
Lower IDM Board (Modem orXC) EEPROM read accesserror
1) Try SW Reset affected module /IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.
42General Hardware Fault#1
IDU Synthesizer lock
1) Download correctSW/FW/Configuration scripts.2) Power IDM off/on.
3) Replace IDM.3) Replace IDC.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
31/44
FibeAir
Troubleshooting Guide 28
Trap ID Description Probable Cause Corrective Actions
42EOW chaining Loss ofSignal
No signal detected onSubrack Auxiliary EOWchaining input.
1) Disable EOW chaining if notrequired.
2) Check EOW chaining line inputon both subracks.3) Check / fix EOW chainingconfiguration on mate subrack.Verify that EOW is defined on atleast one working link on matesubrack.4) Replace EOW chaining
42Drawer-RFU
Communication Failure
No communication between
IDM and RFU.
1) Check IF cable and connectors.2) Check N-type connector innerpin is not spliced.3) Replace IDM.
4) Replace RFU.For High Power RF Unit:1) Check BMA connector on OCB2) Check BMA connector on RFU
42Drawer Internal PowerFailure (Board #2)
Internal Power failure.
1) Check that proper SubrackAuxiliary module inserted.2) Extract and re-insert SubrackAuxiliary module.3) Replace Subrack Auxiliarymodule.
42Drawer InternalLoopback
IDU IF loop applied by user 1) Disable loopback
42 Copy IDC Configurationto Mate
IDC copy configuration byuser in external protection
42Copy CarrierConfiguration To MateFailed/Succedded
Carrier configuration copiedbetween two IDMs inprotected configuration
42 Clock Unit Unlocked Clock Unit Unlocked
42 Clock Unit Out of Range Clock Unit Out of Range
42 Auxiliary Card Fault #01Subrack Auxiliary modulefailed or extracted.
1) Check Subrack Auxiliary moduleis properly inserted.2) Replace Subrack Auxiliarymodule.
42
ACM Configuration File
is Missing
The ACM lookup table file
cannot be found on thesystem disk.
Load the lookup table file of the
relevant release version or load theSFD file.
43
TFTP IDU/MUX/ODUverxxx DownloadSucceeded/Canceled/Failed
Software download operationstatus (from user's PC toIDC)
43
IDU ConfigurationDownloadSucceeded/Error/Cancelled/Failed/Invalid File
Configuration downloadstatus, initiated by user
43
Boot/IDC/MUX/ODU/Modem Script/Modem/Wayside/Mrmc
table/RFU FPGA FileDownload Succeeded
File download status. Initiated
by user.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
32/44
FibeAir
Troubleshooting Guide 29
Trap ID Description Probable Cause Corrective Actions
44 RFU FW Upload FailedFirmware upload operationstatus (from IDC to ODC)
44 RFU FW Upload Error Firmware upload operationstatus (from IDC to ODC)
44RFU FW UploadCanceled
Firmware upload operationstatus (from IDC to ODC)
44 ODU SW Upload FailedSoftware upload operationstatus (from IDC to ODC)
44 ODU SW Upload ErrorSoftware upload operationstatus (from IDC to ODC)
44ODU SW UploadCanceled
Software upload operationstatus (from IDC to ODC)
44MUX/ODU InternalDownload Succeeded/Canceled/Failed/Error
MUX/ODU Internal DownloadSucceeded/Canceled/Failed/Error
46User ConfigurationMismatch between IDC# and IDC #
At least one configurationparameter which should beequal in these two IDCs hasdifferent values.
1) Check the mismatchconfiguration in the alarms log.2) Configure the relevant IDC withthe correct values for mismatchresolution, and wait one minute forthe mismatch alarm to clear.
46User ConfigurationMismatch () S=xx, D=xx
Configuration in the IDC isdifferent than in the drawersor Auxiliary channel board
1) Check and compareconfiguration2) See User ConfigurationMismatch Alarm
46User ConfigurationMismatch () S=xx, D=xx
Mismatch configurationbetween the IDC Databaseand the drawer.
1) Check the mismatchconfiguration in the alarms log.2) Use "Copy to IDC" command tocopy the configuration from XC toIDC, or "Copy to Drawer" formismatch resolution.
46User ConfigurationMismatch
At least one Link Groupconfiguration parameter in theIDC Database is differentthan the actual configurationin the XC. Raised only afterIDC hotswap or S/W reset.
1) Check the mismatchconfiguration in the alarms log.2) Use "Copy to IDC" command tocopy the configurationfrom XC to IDC, or "Copy toDrawer" for mismatch resolution.
46User ConfigurationMismatch
At least one drawerconfiguration parameter intheIDC Database is differentthan the actual configurationin the drawers.Raised only after IDChotswap or S/W reset.
1) Check the mismatchconfiguration in the alarms log.2) Use "Copy to IDC" command tocopy the configuration from thedrawer to the IDC, or "Copy toDrawer", eliminating the mismatch.However, "copy to drawer"command does not copy the protec
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
33/44
FibeAir
Troubleshooting Guide 30
Trap ID Description Probable Cause Corrective Actions
46User ConfigurationMismatch
At least one IDC configurationparameter in the IDC Data
Base (XPIC for example) isdifferent than theconfiguration in the drawersor Auxiliary channels.Raised only after IDChotswap / software reset.
1) Check the mismatch
configuration in the alarms log.2) Use "Copy drawer to IDC"command to copy theXPIC/protection configuration fromthe drawer to the IDC (withoutreset). This will end the mismatch.
46 Protection MismatchInternal system mismatchregarding the state of theradio - Mute/Unmute
Reset IDM
46Mate ConfigurationMismatch () M=xx, L=xx
Mismatch in the internalprotection configurationbetween the drawers.
1) Check and compareconfiguration2) See mate Configuration
Mismatch Alarm
46Mate ConfigurationMismatch () M=xx, L=xx
Mismatch configurationbetween local IDC Databaseand mate IDC database
1) Check and compareconfiguration2) See mate ConfigurationMismatch Alarm
46Mate ConfigurationMismatch
Configuartion mismatchbetween two IDCs in ExternalProtection configuration.
1) Check and compareconfiguration.2) Perform "copy to mate" from theIDC with the correct configuration
46Mate ConfigurationMismatch
Configuartion mismatchbetween two drawers inExternal Protectionconfiguration.
1) Check and compareconfiguration.2) Perform "copy to mate" from thedrawer with the correct
configuration
46Link ID Mismatch onRadio #n
Link ID is not identical onboth ends of the link.
Set identical Link ID on both endsof the link.
46 Link ID Mismatch Link ID Mismatch
46 Link ID MismatchLink ID is not identical onboth ends of the link.
1) Set identical Link ID on bothends of the link.
46 Link ID MismatchLink ID is not identical onboth ends of the link.
1) Set identical Link ID on bothends of the link.
46IDU Hitless RemoteConfig Mismatch
Different configurationbetween the IDUs on bothsides of the link
1) Check and compareconfigurations
46IDU Hitless Mate ConfigMismatch
Different configuration
between the IDUs on thesame side of the link
1) Check and compareconfigurations
46General Hardware Fault#4
IDC MAC device failure -loading with default MACaddress
1) Download correctSW/FW/Configuration scripts.2) Replace IDC.
46General Hardware Fault#3
WSC board configurationfailure - Can't detect boardconfiguration (can't read fromE2PROM)
1) Download correctSW/FW/Configuration scripts.2) Replace IDC.
46General Hardware Fault#2
WSC board configurationfailure - Error during readingboard configuration - CRCerror
1) Download correctSW/FW/Configuration scripts.2) Replace IDC.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
34/44
FibeAir
Troubleshooting Guide 31
Trap ID Description Probable Cause Corrective Actions
46General Hardware Fault#1
FPGA load failure - WaysideChannel
1) Download correctSW/FW/Configuration scripts.
2) Replace IDC.
46 General Cfg MismatchSettings not supported byHW/SW.
1) Check if HW and SW support therequested configuration
46Drawer ID Mismatch inProtecting Carrier
Drawer #1 receives signal ofthe mate drawer (#2) acrossthe XPIC link. Problem in theXPIC link (such as failure inone of the transmitters orinsufficient XPI), detected bythe XC board.
1) Check link connections andsettings.2) Check XPIC configuration.3) Verify that both links are up.4) Check XPI
46 Drawer ID Mismatch
Drawer receives signal of theother drawer across the XPIClink. Indicates problem in theXPIC link (such as failure inone of the transmitters orinsufficient XPI)
1) Check link connections andsettings.
2) Check XPIC configuration.3) Verify that both links are up.4) Check XPI
46Device IncompatibleAlarm (#103)
Incomapitibility alarmbetween link components.Typically refers to mixture ofstandard and "I" componentsin the link
1) Check link components
46Auxiliary Channel UserConfiguration Mismatch
Incorrect Auxiliary channelconfiguration
1) Check and correct configuration:Use "Copy IDC to AUX" to copy theAuxiliary channel configurationto the IDC, or "Copy AUX to IDC" to
copy the Auxiliary channelconfiguration to the AUX
47
SW Mode Changed toSlave/Master?10;Change Remote TransmitterRequest Sent
Change Master/Slavecommand
47ProtectionInternal/External MateNot Exist
System configured forprotection without mateconnected
1) Check configuration.2) Check Mate connected
47Protection ExternalAlarm Switch
Protection switch by externalalarm
47 Protection Change toStandby
Different faults indicate
hardware failure on thedrawer
1) Download correct
SW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.
47Hitless ProtectionConfiguration Mismatch
Hitless is configred withoutprotection
1) Enable protection or disablehitless
47
Change RemoteTransmitter RequestSent -SDBER/EXBER/LOF/BER
Command was sent toremote end to switch whenboth local receivers identifyRx fault (for example, remoteactive transmitter fails)
48ProtectionCommunication Error on
Cable
For External Protectionconfiguration.Protection cable is connectedbut errors detected.
1) Check that cable is connectedproperly.2) Replace protection cable.3) Replace IDCs
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
35/44
FibeAir
Troubleshooting Guide 32
Trap ID Description Probable Cause Corrective Actions
48Protection CableDisconnected
Protection CableDisconnected
1) Connect Protection Cable.2) Replace cable.
48
Protection CableDisconnect/Error/PowerError/Problem?10;Master-Slave Disconnect
Problem with protection cableor the connection betweenthe Master/Slave IDUs
1) Replace cable.2) Replace IDUs
49 Heart Beat (Trap Only) Heart Beat (Trap Only)
50 Trib HP: LOM Trib HP: LOM
50 Radio HP: LOMRadio HP: Loss of Multi-frame (LOM) alarm occurs.
50 Fiber HP: LOMFiber HP: Loss of Multi-frame(LOM) alarm occurs.
51 Hitless Switch Locked toSelf Radio By User Hitless Switch Locked to SelfRadio by User
51Hitless Switch Locked toRight Radio By User
Hitless switching disabled byuser and locked for one of thedrawers.
1) Disable Hitless Lockout
51Hitless Switch Locked toMate/Self Radio By User
Hitless Switch Locked toMate/Self Radio by User
51Hitless Switch Locked toLeft Radio By User
Hitless switching disabled byuser and locked for one of thedrawers.
1) Disable Hitless Lockout
51Hitless Self/MateReceiver in user
Hitless Self/Mate Receiver inuser
51 Hitless Left/RightReceiver in Use Left/Right receiver is used forprocessing data
Not a real alarm since receiver
switching is likely to happen duringmultipath fading.
51Hitless FunctionalityFailure
Hitless protection is notavailable. The link will fail incase of fade.
1) Hitless cable disconnected.2) Mate IDU is off.3) Mate IDU has an alarm thatprevents it from receiving data.
52Unused Radio ReceiverLOF
Hitless Self Radio ReceiverLOF
1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identify
problem source.5) Replace IDMs/ODUs
52Own Radio BBLOF onRadio #n
Hitless Self Radio ReceiverLOF
1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
36/44
FibeAir
Troubleshooting Guide 33
Trap ID Description Probable Cause Corrective Actions
52Loss of Frame onUnused Left/Right Radio
Permanent Radio LOF in thereceiver (raised after 10
consecutive seconds of radioLoss Of Frame).Implies a permanent problem,unlike fading due to multipathcondition, which isintermittent in nature.
Same as Radio LOF alarm:1) Check that the fault is not due to
other alarms that can lead to LOF.2) Check link settings (TX power,TXfreq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs
52Hitless Self RadioReceiver LOF
Hitless Self Radio ReceiverLOF
53Hitless CableDisconnect
Hitless cable disconnected. Connect hitless cable.
57
In-Band Radio PPP LinkDisconnect?10;In-Band
Line PPP LinkDisconnect
In-band connection over theline (STM-1/OC-3 or PPPoE)
or over the radio wasdisconnected.
1) Check the line connection.
2) Check in-band configuration.
58Wayside Channel Lossof Signal/Carrier
Wayside Channel Loss ofSignal/Carrier in internalprotection
1) Check line input.2) Verify user-end equipment.3) Check / replace connectingcable.4) Replace IDC module.In case of N+1 Trunk Radio:5) Replace Subrack Auxiliarymodule.
58 Wayside Channel Lossof Signal/Carrier
Wayside Right Channel Lossof Signal/Carrier
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 Auxiliarymodule.
58Wayside Channel Lossof Signal/Carrier
Wayside Left Channel Loss ofSignal/Carrier
1) Check line input.2) Verify user-end equipment.3) Check / replace connectingcable.4) Replace IDC module.In case of N+1 Trunk Radio:5) Replace Subrack Auxiliarymodule.
58User Channel EthernetLoss of Carrier
User Channel Loss of Carrierin internal protection
1) Check line input.2) Verify user-end Ethernetequipment.3) Check / replace connectingcable.4) Replace IDC module.In case of N+1 Trunk Radio:5) Replace Subrack Auxiliarymodule.
58User Channel Ethernet
Loss of Carrier
User Right Channel Loss of
Carrier
1) Check line input.2) Verify user-end Ethernetequipment.
3) Check / replace connectingcable.4) Replace IDC module.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
37/44
FibeAir
Troubleshooting Guide 34
Trap ID Description Probable Cause Corrective Actions
In case of N+1 Trunk Radio:5) Replace Subrack Auxiliary
module.
58User Channel EthernetLoss of Carrier
User Left Channel Loss ofCarrier
1) Check line input.2) Verify user-end Ethernetequipment.3) Check / replace connectingcable.4) Replace IDC module.In case of N+1 Trunk Radio:5) Replace Subrack Auxiliarymodule.
59ODU-2-ODU CableOpen
ODU-2-ODU Cable Open1) Check cable.2) Replace cable.
60 No Signal from ODUNo Rx (140 MHz) signal fromRFU
1) Check IF cable and connectors2) Check N-type connector innerpin is not spliced.3) Replace IDM.4) Replace RFU.For High Power RF Unit:Check BMA connector center pin isnot spliced both on RFU and onOCB.
60 Modem Script NotSupported
No modem script is availablefor this RFU.
1) Upgrade MRMC scripts2) Replace RFU
61 Protection Lockout
"Protection Lockout"command executed. Will lockthe switching operation untilremoved.
1) Disable Lockout
61 Protection Force Switch
One of the system elementsdoes not support XPIC.Or, the system is missing oneof the needed elements.
1) Disable "Force Switch"
62RFU Power SupplyFailure
At least one of the PSUvoltages is too low.
Replace RFU.
62 RFU Power Failure (Vd)RFU Power Supply Failure(Vd)
1) Reset IDM.2) Check IF cable and connectors.3) Replace ODU.4) Replace IDM.
62RFU Power Failure (6vpro)
RFU Power Supply Failure(6v pro)
1) Reset IDM.2) Check IF cable and connectors.3) Replace ODU.4) Replace IDM.
62RFU Power Failure (6vpro)
RFU Power Supply Failure(6v pro)
1) Reset IDM.2) Check IF cable and connectors.3) Replace ODU.4) Replace IDM.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
38/44
FibeAir
Troubleshooting Guide 35
Trap ID Description Probable Cause Corrective Actions
62RFU Power Failure
(12v)
RFU Power Supply Failure
(12v)
1) Reset IDM.2) Check IF cable and connectors.
3) Replace ODU.4) Replace IDM.
62RFU Power Failure(1.5v)
RFU Power Failure (1.5v)
1) Reset IDM.2) Check IF cable and connectors.3) Replace ODU.4) Replace IDM.
63RFU Rx Level Path2 OutOf Range
RSL of Diversity channel isvery low (typically below -80dBm).
1) Check that the fault is not due torain/multipath fading or lack of LOS.2) Check link settings (TX power,TXfreq).3) Check anttena alignment.4) Check antenna connections
5) Replace local/remote ODU.
63RFU Rx Level Path1 OutOf Range
RSL of Main channel is verylow (typically below -80 dBm).
1) Check that the fault is not due torain/multipath fading or lack of LOS.2) Check link settings (TX power,TXfreq).3) Check anttena alignment.4) Check antenna connections5) Replace local/remote ODU.
64RFU ExtremeTemperature
RFU temperature is toohigh/low.
1) Check installation conditions.2) Verify operation as per product'sspecs.3) Replace RFU
65 RFU Fan FailureFan Failure was detected byRFU
1) Check RFU connection to BP
2) Check that fans are connected toPS3) Replace RFU BP cable4) Replace specific fan or fansdrawer5) Replace RFU
65 RFU Fan FailureFan Failure was detected byRFU
1) Check RFU connection to BP2) Check that fans are connected toPS3) Replace RFU BP cable4) Replace specific fan or fansdrawer5) Replace RFU
66RFU Low Signal ToODU
RFU is detecting low signalfrom IDU
1) Check IF cable connectors.2) Check N-Type connector innerpin is not spliced.3) Replace IDM.4) Replace RFU.
67 RFU XPIC Clock FailureNo XPIC clock is receivedfrom Master RFU
1) Reconnect XPIC clock cables atboth RFUs2) Replace XPIC cable
68RFU Delay Calibration
Failure 1
Delay calibration isunseccessfull since RX AGC
is unlocked.
1) Check link performance2) Re-perform delay calibration3) Re-perform delay calibration in
RF loopback4) Reset the RFU5) Replace RFU
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
39/44
FibeAir
Troubleshooting Guide 36
Trap ID Description Probable Cause Corrective Actions
69 RFU Delay CalibrationFailure 2
Delay calibration is
unseccessfull since wide ordeep notch has beendetected at the RX signal
1) Check link performance2) Reperform delay calibration
3) Re-perform delay calibration inRF loopback4) Reset the RFU5) Replace RFU
70Gigabit Ethernet TXMute Override
GbE port is enabled by theuser but the system overridesthis and mutes the port.This alarm may appear in thefollowing cases:Radio LOF (local or remote),Link ID mismatch (local orremote), excessive BER(local or remote), Signaldegrade (local or re
1) Check the reason for the alarm(see the Probable Cause column)and correct it accordingly.
70Gigabit Ethernet SFP TXFault
SFP does not transmitEthernet properly.
1) Reconnect SFP.2) Replace SFP.3) Replace IDM.
70Gigabit Ethernet SFPNot Intact
SFP is not connectedproperly.
1) Reconnect SFP.2) Replace SFP.3) Replace IDM.
71 Encryption Fault HW encryption fault 1) Reset IDM.
72 Encryption Sync Loss Encryption loss of frame1) Check link staus.2) Reset IDM.
73 Initial KEP FailedThe first encryption keyexchange failed
1) Check link status.
2) Reset IDC.3) Reset IDM.
74Session Key TimerElapsed
No session key exchange inthe allowed time
1)Check link status.
75 Power-Up Test FailedOne of the built-in encryptionsystem tests failed
1) Reset IDC.2) Reset IDM.
76 Conditional Test FailedOne of the Conditional testsfailed
1) Reset IDC.2) Reset IDM.
77Encryption Will TurnedOff On Next Reset
Encryption mode changed byuser, will take effect after nextpower up.
80Admin password in
default state
Administrator password is the
default valueChange administrator password.
81
Link Group #1 N+1Protection Fault: XCPeer CommunicationFailure
N+1 Link Group protectiondegraded due to peer XCcommunication fault.
1) Verify Protection Radio link is upand, no errors over the link.2) Check that remote IDU isproperly configured for N+1 LinkGroup protection.3) Check that remote IDU hasproperly operational XC board.4) Check that Protection Radio linktermin
81Link Group #1 N+1Protection Fault: XC
Card is Down
N+1 Link Group protectiondegraded due to XC card
fault.
1) Check if XC module is insertedand powered on and no other alarmpertained to XC is active.
2) Replace XC module.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
40/44
FibeAir
Troubleshooting Guide 37
Trap ID Description Probable Cause Corrective Actions
81
Link Group #1 N+1
Protection Fault:Protecting Radio Failure
N+1 Link Group protectiondegraded due to Loss Of
Frame or Loss Of Signalalarm on the radio portdetected by XC board.
1) Check Protecting Radio moduleis powered on and operates
properly.2) Replace faulty module.3) see Radio RS: LOF (SDH)
81Link Group #1 N+1Protection Fault: Lockedby User
Lockout or Force Switch toProtecting Link Groupmaintenance commandactivated.
Release maintenance command.
81
Link Group #1 N+1Protection Fault: Local-Remote Group TopologyMismatch
N+1 Link Group protectiondegraded due to Local-Remote Protection Mismatch.
1) Check that remote IDU isproperly configured with N+1 LinkGroup topology, and all protectionmembers are configured with thesame priority level (if extra traffic isconfigured as revertive in one
subrack, it should also beconfigured the
82 Loss of ProtectionThere is no power on thestandby IDM
1) Check if the power switch is on.2) Replace standby IDM
83 Temp License is ActiveTemporary License activatedby the user
Load permanent license or disablethe temporary license
84
Ingress Gigabit Ethernet
blocked on Radio
There is a Radio fault on theremote radio or the "BlockRadio Command on theprotection configuration" isenabled.
The Alarm should be raisedonly on Multi Radio. Thecause for radio fault are:Radio LOF, Link IDmismatch, Drawer IDmismatch, Excessive
1) Check the Block Radio commandstatus on the protection
configuration.2) Check the remote radio alarmsand solve the radio fault accordingly
84Egress Gigabit Ethernetblocked on Radio
There is a Radio fault on thelocal radio or the "BlockRadio Command on theprotection configuration" isenabled.The Alarm should be raisedonly on Multi Radio. The
cause for radio fault are:Radio LOF, Link IDmismatch, Drawer IDmismatch, Excessive B
1) Check the Block Radio commandstatus on the protectionconfiguration.2) Check the local radio alarms and
solve the radio fault accordingly.
85 Unknown RFU TypeIDC's SW doesn't support theRFU.
Upgrade IDC's SW.
85Incompatible RFU TXCalibration
RFU calibration tablesrequires IDC SW upgrade.
Upgrade IDC's SW.
401 Node down.
This alarm occurs when theconnection between the NMSand the network element islost.
402User (from) failed to login times.
This alarm occurs when the
user fails to log in to the NMSsystem correctly severaltimes consecutively.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
41/44
FibeAir
Troubleshooting Guide 38
Trap ID Description Probable Cause Corrective Actions
403
Standby serevr failed toconnect to main server
(the main server isconfigured asStandalone).
This alarm occurs when asecondary standby NMS
server tries to connect to astand-alone NMS server.
Open the main server configuration,and in the Redundancy section,
change the server roll from StandAlone to Main Server.
404No communicationbetween main andstandby servers.
This alarm occurs for aprimary NMS server when itsconnection to the standbyNMS server is lost.
405License expires in lessthan two weeks.
This alarm occurs for theNMS server when the licenseis set to expire in less thantwo weeks.
Contact customer support to obtaina license file for the server.
406 License expired.This alarm occurs for theNMS server when the license
expires.
Contact customer support to obtaina license file for the server.
407Network Elementsnumber exceeds thelicense limit.
This alarm occurs for theNMS server when the numberof network elements exceedsthe license limit.
Remove some of the elements, orContact customer support to obtaina license file for the updatednumber of elements.
408Failed loading licensefile.
This alarm occurs for theNMS server when it fails toload the license file.
The license file is probablycorrupted. Contact customersupport to obtain a new license file.
409Failed to start the TFTPserver on (address already in use).
This alarm occurs when NMSserver attempts to start theTFTP, but the TFTP port (69)is already bound by another
process.
Check your system, and disableother TFTP servers.
410 Disconnected UserThis alarm occurs when auser is disconnected byanother user.
411Standby serevr failed toconnect to main server(versions mismatch).
This alarm occurs when asecondary standby NMSserver tries to connect to amain NMS server,with adifferent software version.
1) Verify the existence of all IDMsand ODU, and verify theirconnectivity.2) Open the unit Alarm Log (usingthe element manager) and send tocustomer support the code in theend the "XPIC Insufficient" eventtext.
414
Enabled feature set
is notlicensed
The enabled feature set is notlicensed.
Disable the feature or contact
Support to get an appropriatelicense.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
42/44
FibeAir
Troubleshooting Guide 39
Fault Isolation using Loopbacks
The loopback function provides a means of testing the link at various points. During the procedure, theexternal equipment sends a data pattern and monitors its receipt. If the received pattern is identical to the sent
pattern, the connection between the equipment and the loop is confirmed.
Loopback
FibeAir is capable of performing loopback testing at several points in the link. The test is run from the
CeraView management software, or via the SNMP protocol.
During the loopback test, an alarm indication will appear to remind you to cancel the test when you are done.
The following loopback tests can be performed from the window:
Local:
y 155 Mbps Line Interface
y Wayside Channel
EquipmentLocal IDU
Interfaces
101101110...
101101110...
Modem &
IF
Local IDU
to ODU
Local Loop
y Full IDU (all three inputs through the IDU, modulator, and looped in the IF).
Equipment Radio Link
101101110
101101110Equipment Radio Link
101101110
101101110
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
43/44
FibeAir
Troubleshooting Guide 40
Remote:
y 155 Mbps Line Interface
y Wayside Channel
EquipmentLocal IDU
Interfaces
101101110...
101101110...
Modem &
IF
Local IDU
Remote Loop
Full Radio Link Loopback (local external equipment through the radio link, to the remote line interface
module, back through the radio link, to the local external equipment).
Equipment
101101110...
101101110...
Local Terminal
Local
IDU
Local
ODU
Modem
&
IF
Line
Interface
Remote
IDU
Remote Terminal
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.
-
7/28/2019 Trouble Shooting Guide IP 10 1500P Nov
44/44
For serial connection using a dial-up modem, use a cross cable.
Cable Connections
Check Read and Write Communities
Ping FibeAir. If ping succeeds, the problem may be with the CeraView software installation, or the computer
TCP\IP stack. Check the read and write communities in FibeAir and in the management station configuration.
If ping fails, there may be a network connectivity problem.
A typical conflict may occur between the IDU configuration and the related CeraView parameter.
In addition, the Agent Address must be identical to the IDU IP address, and the source address must be
identical to the computers address.
The following figure shows a typical example of IP addresses and network configuration.
Terminal
CeraView
IP Management
Network
3200T GNE A
SNMP
Remote
Terminal
Telnet
3200T NE B
1500P NE C
PPP /
Ethernet
1500P NE D
PPP /
Ethernet
3xRS-232
Site A Site B
192.168.1.33
192.168.1.3