Ceragon Alarms

7/28/2019 Ceragon Alarms

1/42

FibeAir

Troubleshooting

Guide

Part ID: BM-0108-0

Doc ID: DOC-00015466 Rev a.00

November 2006


2/42

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


CeraView


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


3/42

Contents

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

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

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

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

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

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

Alarm List Table............................................................................................ 5

Fault Isolation using Loopbacks ................................................................36

Connection Fault Guide ..............................................................................37


4/42

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


5/42

FibeAir


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.


6/42

FibeAir


IDU LED Indicators

The following table lists the LEDs on the IDU panel and their functions.

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/42

FibeAir


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


OFF Hitless mode is disabled.

Red Local unit receives LOF from the mate unit.

Green Hitless switching can be performed, if necessary.

Local Receiver (Interface Panel) - Rx ACTV


OFF Local receiver not in use.

Green Local receiver in use.


8/42

FibeAir


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

0

Insufficient systemconfiguration for fullXPIC Support

One of the system elementsdoes not support XPIC.Or, the system is missingone of the needed elements.

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 at theend of the "XPIC Insufficient" eventtext.

10

ODU 5/8/12/-12V PowerSupply Failure

One of the system elementsdoes not support XPIC.Or, the system is missingone of the needed elements.

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

11

Synthesizer #1/2/3Unlocked

One of the ODU synthisizersis unlocked.

Replace ODU. (In XPICconfiguration, the ODU may betaking the sync from the mateODU. In that case, check if alarmpersists in non-XPICconfiguration.)

12 Tx Level Out of Range The ODU cannot transmitthe requested Tx power.

1) Reduce TX power gradually.2) Replace ODU.


9/42

FibeAir



12

Tx Mute On/Off ODU muted by user 1) Check if Power Input connected

to -48 VDC supply.2) Check -48 VDC supply to thesubrack.3) Disable Power Input if you donot use redundant power feed.

13

Rx Level Out of Range RSL is very low (typicallybelow -80 dBm), link isdown.

1) Check that the fault is not due torain/multipath fading or lack ofLOS.2) Check link settings (TXpower,TX freq).3) Check anttena alignment.4) Replace local/remote ODU.

14ODU Temperature Outof Range

ODU temperature toohigh/low.

1) Check installation conditions.2) Replace ODU.

15

Power Input #2 is Down Subrack 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 if you donot use redundant power feed.

15

Power Input #1 is Down Subrack 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 if you do

not use redundant power feed.

15

XPIC Cable Swap Left/Right cables swap inXPIC configuration. IfDrawer ID Mismatch (seeabove) alarm is identified inboth drawers, the IF (coax)cables between the drawersand ODUs on one end areswapped.

1) Verify correct cable connection.

Recommended connection is V toRight drawer and H to Left drawer

15IDU 5/8/3.3/-5V PowerSupply Failure

Failure in an IDU powersupply.

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


10/42

FibeAir



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

15Drawer Internal PowerFailure (Board #1)

Drawer Internal PowerFailure (Board #1)

-

15


Board #1 - MUX card.Board #2 - Modem card.This alarm may also begenerated if a drawer inInternal Protection wasswitched off.

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

16

Extension Link

Communication Failure

Problem with extension

cable or the connectionbetween the two subracks.

1) If extended mode is not in use,

configure all IDCs in the subrackas "1 subrack out of 1".2) If extended mode is in use,verify that the other subrack isconfigured to extension modeproperly.3) Check that the XC boards inboth subracks are insertedproperly and the extension cable isplugged in.4) Replace extension cable.5) Replace XC boards.

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-ODU cable open 1) Check IF cable and connectors2) Check ODU's N-type connectorinner pin is not spliced (if yes,replace ODU).3) Replace IDM.

4) Replace ODU.

17

MRMC= ScriptFile is Missing

Multi-Rate Multi-Constellation configurationscript for the specifiedcapacity/modulation ismissing 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.

18 IDU Temperature Out ofRange

IDU Temperature Out ofRange

1) Check installation conditions.2) Replace IDM.


11/42

FibeAir



18 Fan Failure Fan Failure 1) Replace fan.

19XC Internal Loopbackon Line #5

XC board Internal portloopback

1) Disable loopback



1) Disable loopback



1) Disable loopback



1) Disable loopback



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

19 ODU Internal Loopback(Not) Active

ODU RF loopback appliedby user

1) Disable loopback

19

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

Loopback applied by user 1) Disable loopback

19Internal Loopback onFiber #n

Internal loopback on Fiber 1) Disable loopback

19External Loopback onFiber #n

IDU Line loopback appliedby user

1) Disable loopback

19E1\T1 Internal Loopbackon Port #n

IDU Line loopback appliedby user

1) Disable loopback

19IDU Local Loopback(Not) Active

IDU IF loopback applied byuser

1) Disable loopback


12/42

FibeAir



19

E1\T1 External

Loopback on Port #n

E1/T1 External loopback 1) Disable loopback

20

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

21

Link Group #1 N+1Protection Fault: Locked

by User

Lockout or Force Switch toProtecting Link Group

maintenance commandactivated.

Release maintenance command.

22 Trib RS: LOF Trib RS: LOF

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 (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.

5) Replace IDMs.

22

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

22

Radio 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 (TXpower,TX freq).

3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs

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.


13/42

FibeAir



22

Fiber RS: LOF (SDH)

Fiber Section: LOF(Sonet)

Loss Of Frame alarm on the

line input

1) Check line input.

2) Check fibers/cables.3) Verify end equipment 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 toother alarms that can lead to LOF.2) Check link settings (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs

23 Trib RS: LOS Trib RS: LOS

23

Loss of Signal onFiber #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.

23

Fiber RS: LOSor?10;E1\T1\E3\DS3 #nLoss of Signal?10;FiberRS: 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 confirminput/IDU is ok.5) Replace IDU.

23

- Gigabit Ethernet Loss ofSignal

1) Check line input.2) Check fiber.3) Verify end equipment transmits

properly.4) Replace IDM.

23

Fast Ethernet Loss ofCarrier on Port #n

Fast Ethernet Loss ofCarrier

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

23

Fast Eth. #01/02 Loss ofCarrier

Fast Ethernet Loss ofCarrier

1) Check line input.2) Check cable.3) Verify end equipment transmits

properly.4) Replace IDU.


14/42

FibeAir



23

E1\T1 Loss of Signal on

Port #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: 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 -

25 Trib 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)

-

25

Radio RS: Excessive

BER

Radio RS: Excessive BER

(ADM)

-


15/42

FibeAir



25

Radio MS: Excessive

BER

Radio MS: Excessive BER -

25Radio LP #n: ExcessiveBER

Radio LP: Excessive BER -

25Radio HP: ExcessiveBER

Radio HP: Excessive BER -

25

Excessive 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 (TXpower,TX freq).

3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs

25

Excessive BER onFiber #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 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.

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 -

25 Fiber HP: ExcessiveBER

Fiber HP: Excessive BER -


16/42

FibeAir



25

E1\T1\E3\DS3 #n

Excessive BER

E3DS3 Excessive BER -

25E1\T1\E3\DS3 #nExcessive BER

E1/T1 Excessive BER -

26 Trib RS: Signal Degrade Trib RS: Signal Degrade -

26Trib MS: SignalDegrade

Trib MS: Signal Degrade -

26Trib LP #n SignalDegrade

Trib LP #n Signal Degrade -

26 Trib HP: Signal Degrade Trib HP: Signal Degrade -

26Radio RS: SignalDegrade

Radio RS: Signal Degrade -





26Radio LP #n: SignalDegrade

Radio LP #n: SignalDegrade

-

26Radio MS: SignalDegrade

Radio HP: Unequipped -

26Radio HP: SignalDegrade

Radio HP: Signal Degrade -

26

Signal 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 (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs

26

Signal 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 confirm

that input/IDU is ok.5) Replace IDM.


17/42

FibeAir



26

Fiber RS: Signal

Degrade

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.

26

E1\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 confirminput/IDM is ok.5) Replace IDM.

26Fiber RS: SignalDegrade

Fiber RS: Signal Degrade(ADM)

-

26Fiber RS: SignalDegrade

Fiber RS: Signal Degrade -

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 -

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 -


18/42

FibeAir



27 Fiber LP #n: AIS Fiber LP #n: AIS -

27 Fiber HP: AIS Fiber HP: AIS -

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

Unexpected signal on theline input. Port disabled butline is connected.

1) Enable line port or disconnectline

28Trib RS: UnexpectedSignal

Trib RS: Excessive BER -

28Gigabit EthernetUnexpected Signal

GbE port is disabled butGbE data is detected.

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

28Fast Ethernet UnexpectedSignal on Port #n

Fast Ethernet UnexpectedSignal on Port #n

-

30 Trib LP #n: LOP Trib LP #n: LOP -

30 Trib HP: LOP Trib HP: LOP -

30Radio LP #n: LOP Radio LP: Loss of pointer

(LOP) alarm occurs.-

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

-

30Fiber LP #n: LOP Fiber LP: Loss of pointer


30Fiber HP: LOP Fiber HP: Loss of pointer


31 Trib MS: RDI Trib MS: RDI -

31 Trib LP #n: RDI Trib LP #n: RDI -

31 Trib HP: RDI Trib HP: RDI -

31Radio MS: RDI Radio MS: Remote Defect

Identifier signal (RDI)occurs.

-

31Radio LP #n: RDI Radio LP: Remote Defect


-


19/42

FibeAir



31Radio HP: RDI Radio HP: Remote Defect


-

31Fiber MS: RDI Fiber MS: Remote Defect


-

31Fiber LP #n: RDI Fiber LP: Remote Defect


-

31Fiber HP: RDI Fiber HP: Remote Defect


-

32 Trib LP #n: PLM Trib LP #n: PLM -

32 Trib HP: PLM Trib HP: PLM -

32Radio LP #n: PLM Radio LP: Payload Label

Mismatch (PLM) occurs.-

32 Radio HP: PLM Radio HP: Payload LabelMismatch (PLM) occurs. -

32Fiber LP #n: PLM Fiber LP: Payload Label


32Fiber HP: PLM Fiber HP: Payload Label


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:Unequipped

Fiber LP: Unequipped -

33 Fiber HP: Unequipped Fiber HP: Unequipped -

34 External Alarm External alarm input #1configured and triggered byuser.

-


20/42

FibeAir



35

External Alarm External alarm input #2

configured and triggered byuser.

-

36External Alarm External alarm input #3


-



-

38



-



-



-

41



-

42

General Hardware Fault#3

XO failure Mux board 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42


XO failure Modem board 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42XC FPGA Fileis Missing

XC firmware file is missingin the 2-floor IDC.

1) Download XC firmware file ofthe required type and reset theIDC.

42General Hardware Fault#11

Wrong card type detected inSubrack Auxiliary slot.

1) Replace Subrack Auxiliarymodule.

42Wayside Firmware Fileis Missing

Wayside firmware file ismissing in the IDC.

1) Download Wayside firmware fileto the IDC and reset the IDC.


21/42

FibeAir



42

Auxiliary Card Fault #01 Subrack Auxiliary modulefailed or extracted.

1) Check Subrack Auxiliary moduleis properly inserted.2) Replace Subrack Auxiliarymodule.

42Subrack Auxiliary FPGAFile is Missing

Subrack Auxiliary firmwarefile is missing in the 2-floorIDC.

1) Download Subrack Auxiliaryfirmware file and reset the IDC.

42


Subrack Auxiliary EEPROMchecksum failure.

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

module.

42Secondary ClockSource Failure

Secondary Clock SourceFailure

-

42

Radio Card #nPowered Down

Radio module pertained toLink Protection group ispowered down or extracted.

1) Check if Radio module isinserted properly in the subrack

and is powered on. Replacemodule if faulty.

42Primary Clock SourceFailure

Primary Clock SourceFailure

-

42

EOW 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 cable.5) Perform reset to the local / mateSubrack Auxiliary module (byextracting and inserting IDC2).6) Replace local / mate SubrackAuxiliary module.7) Check / replace IDC2 on matesubrack.

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 pertainedto XC is active.2) Replace XC module.


22/42

FibeAir



42

Link Group #1 N+1

Protection Fault: XCPeer CommunicationFailure

N+1 Link Group protection

degraded due to peer XCcommunication fault.

1) Verify Protection Radio link is up

and, 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 over Protecting Radiomodule (and not other Radiomodule).

42

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

N+1 Link Group protectiondegraded due to Local-Remote ProtectionMismatch.

1) Check that remote IDU isproperly configured with N+1 LinkGroup topology.2) Check that remote IDU has allrelevant N+1 Link Group protectionline modules operational.

42


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.

42

General Hardware Fault

#8

Upper IDM Board (MUX or

XC) EEPROM read accesserror

1) Try SW Reset affected module /

IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.

42


Lower IDM Board (Modemor XC) EEPROM inventoryinformation CRC error

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

42

General Hardware Fault

#10

Lower IDM Board (Modem

or XC) EEPROM readaccess error

1) Try SW Reset affected module /

IDM.2) Power cycle or re-insert affectedmodule / IDM.3) Replace the module.

42

Line Card #n PoweredDown

Line module pertained toLink Protection group ispowered down or extracted.

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


23/42

FibeAir



42

Line Card #1 Powered

Down

Line module in carrrier #1 of

the Link Protection group ispowered down or extracted.

1) Check if the card is inserted

properly in the subrack.2) Check if own or redundantpower supply / Radio module ispowered on.3) Replace module if faulty.

42


Internal Power failure. 1) Check that proper SubrackAuxiliary module inserted.2) Extract and re-insert SubrackAuxiliary module.3) Replace Subrack Auxiliarymodule.

42

XPIC Cable Swap Internal IDC to IDCcommunication failurebetween modules requiedfor Link Group protectionservice.

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, Ethernetcable (if applicable), IDC modules.Replace faulty module.

42


IDU XPIC HW fault 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42


IDU Synthesizer lock 1) Download correctSW/FW/Configuration scripts.2) Power IDM off/on.3) Replace IDM.3) Replace IDC.

42Drawer Internal

Loopback

IDU IF loop applied by user 1) Disable loopback

42Copy IDC Configurationto Mate

IDC copy configuration byuser in external protection

-

42

IDU-ODU InnerCommunication Failure

IDC cannot communicatewith ODC 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.


24/42

FibeAir



42

IDU-MUX Inner

Communication Failure

IDC cannot communicate

with MUX card, MUX cardupload failure.

1) Reset IDU.

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

42


FPGA load failure - SubrackAuxiliary board.

1) Download correct SubrackAuxiliary FW file to 2-floor IDC, andthen extract and re-insert SubrackAuxiliary board2) Replace Subrack Auxiliarymodule.3) Replace 2-floor IDC.


FPGA load failure - Mux 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42


FPGA load failure - Modem 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42

Drawer-ODUCommunication Failure

Drawer cannotcommunicate with ODC

card.

1) Check ODU connection to IDM.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 IDM.

For High Power RF Unit:1) Check BMA connector on OCB2) Check BMA connector on RFU

42


DAC failure 1) Download correctSW/FW/Configuration scripts.2) Replace IDM.3) Replace IDC.

42 Clock Unit Unlocked Clock Unit Unlocked -

42 Clock Unit Out of Range Clock Unit Out of Range -

42Copy CarrierConfiguration To MateFailed/Succedded

Carrier configuration copiedbetween two IDMs inprotected configuration

-

42MUX Firmware File isMissing

A Mux FW file is missingfrom the system.

Load the required FW file, andreset system.


25/42

FibeAir



42

Modem Firmware File is

Missing

A Modem FW file is missing

from the system.

Load the required FW file, and

reset system.

43

TFTP IDU/MUX/ODUverxxx DownloadSucceeded/Canceled/Failed

Software downloadoperation status (from user'sPC to IDC)

-

43

Boot/IDC/MUX/ODU/Modem Script/Modem/Wayside/Mrmctable/RFU FPGA FileDownload Succeeded

File download status.Initiated by user.?9;

-

43

IDU ConfigurationDownloadSucceeded/Error/Cancelled/Failed/Invalid File

Configuration downloadstatus, initiated by user

-

44ODU SW Upload Failed Software upload operation

status (from IDC to ODC)-

44ODU SW Upload Error Software upload operation


44ODU SW UploadCanceled

Software upload operationstatus (from IDC to ODC)

-

44

MUX/ODU InternalDownloadSucceeded/Canceled/Failed/Error

MUX/ODU InternalDownloadSucceeded/Canceled/Failed/Error

-

44RFU FW Upload Failed Firmware upload operation


44RFU FW Upload Error Firmware upload operation


44RFU FW UploadCanceled

Firmware upload operationstatus (from IDC to ODC)

-

46


WSC board configurationfailure Error duringreading board configuration CRC error

1) Download correctSW/FW/Configuration scripts.2) Replace IDC.


26/42

FibeAir



46


WSC board configurationfailure Can't detect boardconfiguration (can't readfrom E2PROM)


46General Cfg Mismatch Settings not supported by

HW/SW.1) Check if HW and SW supportthe requested configuration

46

Mate ConfigurationMismatch () M=xx, L=xx

Mismatch in the internalprotection configurationbetween the drawers.

1) Check and compareconfiguration2) See mate ConfigurationMismatch Alarm

46

User 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 configurationfrom XC to IDC, or "Copy toDrawer" for mismatch resolution.

46

Mate ConfigurationMismatch () M=xx, L=xx

Mismatch configurationbetween local IDC Databaseand mate IDC database

1) Check and compareconfiguration2) See mate ConfigurationMismatch Alarm

46 Link ID Mismatch Link ID Mismatch -

46Link ID Mismatch onRadio #n

Link ID is not identical onboth ends of the link.

Set identical Link ID on both endsof the link.

46Link ID Mismatch Link ID is not identical on

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

46Link ID Mismatch Link ID is not identical on

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

46Protection Mismatch Internal system mismatch

regarding the state of theradio Mute/Unmute

Reset IDM

46

Auxiliary Channel UserConfiguration Mismatch

Incorrect Auxiliary channelconfiguration

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


27/42

FibeAir



46

Device IncompatibleAlarm (#103)

Incomapitibility alarmbetween link components.Typically refers to mixture ofstandard and "I"components in the link

1) Check link components


IDC MAC device failure loading with default MACaddress



FPGA load failure Wayside Channel

1) Download correctSW/FW/Configuration scripts.

2) Replace IDC.

46

Drawer ID Mismatch Drawer receives signal ofthe other drawer across theXPIC link. Indicates problemin the XPIC link (such asfailure in one of thetransmitters or insufficientXPI)

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

46

Drawer ID Mismatch inProtecting Carrier

Drawer #1 receives signal ofthe mate drawer (#2) across

the XPIC link. Indicatesproblem in the XPIC link(such as failure in one of thetransmitters or insufficientXPI), detected by the XCboard.

1) Check link connections andsettings.

2) Check XPIC configuration.3) Verify that both links are up.4) Check XPI

46IDU Hitless Mate ConfigMismatch

Different configurationbetween the IDUs on thesame side of the link

1) Check and compareconfigurations

46IDU Hitless RemoteConfig Mismatch

Different configurationbetween the IDUs on bothsides of the link

1) Check and compareconfigurations

46

User ConfigurationMismatch () S=xx, D=xx

Configuration in the IDC isdifferent than theconfiguration in the drawersor in the Auxiliary channelsboard

1) Check and compareconfiguration2) See User ConfigurationMismatch Alarm

46

Mate ConfigurationMismatch

Configuration mismatchbetween two IDCs inExternal Protectionconfiguration.

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


28/42

FibeAir



46

Mate Configuration

Mismatch

Configuration mismatch

between two drawers inExternal Protectionconfiguration.

1) Check and compare

configuration.2) Perform "copy to mate" from thedrawer with the correctconfiguration

46

User ConfigurationMismatch

At least one Link Groupconfiguration parameter inthe IDC Database isdifferent than the actualconfiguration in the XC.Raised only after IDChotswap 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.

46


At least one IDCconfiguration parameter inthe IDC Data Base (XPICfor example) is different thanthe configuration in thedrawers or in the Auxiliarychannels.Raised only after IDChotswap / software reset.

1) Check the mismatchconfiguration in the alarms log.2) Use "Copy drawer to IDC"command to copy theXPIC/protection configuration fromthe drawer to the IDC (withoutreset). The process will eliminatethe mismatch. The IDC parameters(IP addresses, in-band, externalalarms) are not copied.3) Use "Upload/DownloadConfiguration" command followed

by S/W reset in order to copy ALLIDC configurations to the IDC.

46


At least one drawerconfiguration parameter inthe IDC Database isdifferent than the actualconfiguration in 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 theprotection or XPIC properties (thayare IDC parameters). IDCparameters (IP addresses, in-band) are not copied.3) Use "Upload/DownloadConfiguration" command followedby S/W reset in order to copy ALLIDC configurations to the IDC.

46

User 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 for

the mismatch alarm to clear.


29/42

FibeAir



47

Protection

Internal/External MateNot Exist

System configured for

protection without mateconnected

1) Check configuration.

2) Check Mate connected

47Protection ExternalAlarm Switch

Protection switch byexternal alarm

-

47Hitless ProtectionConfiguration Mismatch

Hitless is configred withoutprotection

1) Enable protection or disablehitless

47

Protection Change toStandby

Different faults indicatehardware failure on thedrawer

1) Download correctSW/FW/Configuration scripts.2) Replace IDM.

3) Replace IDC.

47

Change RemoteTransmitter RequestSent - SDBER / EXBER/ LOF / BER

Command was sent toremote end to switch whenboth local receivers identifyRx fault (for example,remote active transmitterfails)

-

47

SW Mode Changed toSlave/Master?10;Change Remote

Transmitter RequestSent

Change Master/Slavecommand

-

48Protection CableDisconnected

Protection CableDisconnected

1) Connect Protection Cable.2) Replace cable.

48

Protection CableDisconnect/Error/PowerError/Problem?10;Master-SlaveDisconnect

Problem with protectioncable or the connectionbetween the Master/SlaveIDUs

1) Replace cable.2) Replace IDUs

48

ProtectionCommunication Error onCable

For External Protectionconfiguration.Protection cable isconnected but errorsdetected.

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

49 Heart Beat (Trap Only) Heart Beat (Trap Only) -

50 Trib HP: LOM Trib HP: LOM -

50Radio HP: LOM Radio HP: Loss of Multi-

frame (LOM) alarm occurs.-


30/42

FibeAir



50

Fiber HP: LOM Fiber HP: Loss of Multi-

frame (LOM) alarm occurs.

-

51Hitless Left/RightReceiver in Use

Left/Right receiver is usedfor processing data

Not a real alarm since receiverswitching is likely to happen duringmultipath fading.

51Hitless Switch Locked toRight Radio By User

Hitless switching disabledby user and locked for oneof the drawers.

1) Disable Hitless Lockout

51Hitless Switch Locked toLeft Radio By User

Hitless switching disabledby user and locked for one

of the drawers.

1) Disable Hitless Lockout

51Hitless Switch Locked toSelf Radio By User

Hitless Switch Locked toSelf Radio by User

-

51Hitless Switch Locked toMate/Self Radio ByUser

Hitless Switch Locked toMate/Self Radio by User

-

51Hitless Self/MateReceiver in user

Hitless Self/Mate Receiverin user

-

51

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

52

Loss of Frame onUnused Left/Right Radio

Permanent Radio LOF inthe receiver (raised after 10consecutive seconds ofradio Loss Of Frame).Implies a permanentproblem, unlike fading dueto multipath condition, which

is intermittent in nature.

Same as Radio LOF alarm:1) Check that the fault is not due toother alarms that can lead to LOF.2) Check link settings (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identify

problem source.5) Replace IDMs/ODUs

52

Unused 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 (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs


31/42

FibeAir



52

Own Radio BBLOF on

Radio #n

Hitless Self Radio Receiver

LOF

1) Check that the fault is not due to

other alarms that can lead to LOF.2) Check link settings (TXpower,TX freq).3) Verify no interference.4) Use loopbacks to identifyproblem source.5) Replace IDMs/ODUs

52Hitless Self RadioReceiver LOF

Hitless Self Radio ReceiverLOF

-

53Hitless Cable

Disconnect

Hitless cable disconnected. Connect hitless cable.

57

In-Band Radio PPP LinkDisconnect?10;In-BandLine PPP LinkDisconnect

In-band connection over theline (STM-1/OC-3 orPPPoE) or over the radiowas disconnected.

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

58

User Channel EthernetLoss of Carrier

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

58


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 Auxiliary

module.

58


User Channel Loss ofCarrier in 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.


32/42

FibeAir



58

Wayside Channel Loss

of Signal/Carrier

Wayside Channel Loss of

Signal/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 ChannelLoss of Signal/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.

58

Wayside Channel Lossof Signal/Carrier

Wayside Left Channel Lossof Signal/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.

59ODU-2-ODU CableOpen

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

60

No Signal from ODU No Rx (140 MHz) signalfrom ODU

1) Check IF cable andconnectors2) Check that ODU's N-type connector inner pin isnot spliced (if yes, replaceODU).3) Replace IDM.4) Replace ODU.

For High Power RF Unit:Check BMA connector center pin isnot spliced both on RFU and onOCB.

60Modem Script NotSupported

Modem Script NotSupported

-

61

Protection Force Switch One of the system elementsdoes not support XPIC.Or, the system is missingone of the needed elements.

1) Disable "Force Switch"


33/42

FibeAir



61

Protection Lockout "Protection Lockout"

command executed. Willlock the switching operationuntil removed.

1) Disable Lockout

62

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

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

62

RFU Power Failure (6vpro)

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 (6vpro)

RFU Power Supply Failure(6v pro)


62

RFU Power Failure(12v)

RFU Power Supply Failure(12v)


62

RFU Power Failure(1.5v)

RFU Power Failure (1.5v) 1) Reset IDM.2) Check IF cable and connectors.3) Replace ODU.4) Replace IDM.

63

RFU Rx Level Path1Out Of Range

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

1) Check that the fault is not due torain/multipath fading or lack ofLOS.2) Check link settings (TXpower,TX freq).3) Check anttena alignment.4) Check antenna connections5) Replace local/remote ODU.

63

RFU Rx Level Path2Out Of Range

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

1) Check that the fault is not due torain/multipath fading or lack ofLOS.2) Check link settings (TXpower,TX freq).3) Check anttena alignment.4) Check antenna connections5) Replace local/remote ODU.

64RFU ExtremeTemperature

RFU temperature is toohigh/low.

1) Check installation conditions.2) Replace RFU


34/42

FibeAir



65

RFU Rx Level Path2

Out Of Range

RSL of Diversity channel is

very low (typically below -80dBm).

1) Check that the fault is not due to

rain/multipath fading or lack ofLOS.2) Check link settings (TXpower,TX freq).3) Check anttena alignment.4)Check antenna connections5)Replace local/remote ODU.

65

RFU Fan Failure Fan Failure was detected byRFU

1) Check RFU connection to BP2) Check that fans are connectedto PS3) Replace RFU BP cable4) Replace specific fan or fansdrawer5) Replace RFU

65

RFU Fan Failure Fan Failure was detected byRFU

1) Check RFU connection to BP2) Check that fans are connectedto PS3) Replace RFU BP cable4) Replace specific fan or fansdrawer5) Replace RFU

66

RFU Low Signal To

ODU

RFU is detecting low signal

from IDU

1) Check RFU IF cable connection

2) Reconnect the IF cable3) Replace RFU

67RFU XPIC Clock Failure No XPIC clock is received

from Master RFU1) Reconnect XPIC clock cables atboth RFUs2) Replace XPIC cable

68

RFU Delay CalibrationFailure 1

Delay calibration isunseccessfull since RXAGC is unlocked.

1) Check link performance2) Re-perform delay calibration3) Re-perform delay calibration inRF loopback4) Reset the RFU

5) Replace RFU

69

RFU Delay CalibrationFailure 2

Delay calibration isunseccessfull since wide ordeep notch has beendetected at the RX signal

1) Check link performance2) Reperform delay calibration3) Re-perform delay calibration inRF loopback4) Reset the RFU5) Replace RFU

70Gigabit Ethernet SFPNot Intact

SFP is not connectedproperly.

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


35/42

FibeAir



70

Gigabit Ethernet SFP

TX Fault

SFP does not transmit

Ethernet properly.

1) Reconnect SFP.

2) Replace SFP.3) Replace IDM.

70

Gigabit Ethernet TXMute Override

GbE port is enabled by theuser but the systemoverrides this and mutes theport.This alarm may appear inthe following cases:Radio LOF (local or remote),Link ID mismatch (local orremote), excessive BER(local or remote), Signaldegrade (local or remote),GbE LOS (remote)

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

71 Encryption Fault HW encryption fault 1) Reset IDM.

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

2) Reset IDM.

73Initial KEP Failed The first encryption key

exchange failed1) Check link status.2) Reset IDC.3) Reset IDM.

74Session Key TimerElapsed

No session key exchange inthe allowed time

1)Check link status.

75Power-Up Test Failed One of the built-in

encryption system testsfailed

1) Reset IDC.2) Reset IDM.

76Conditional Test Failed One of the Conditional tests

failed1) Reset IDC.2) Reset IDM.

77

Encryption Will Turned

Off On Next Reset

Encryption mode changed

by user, will take effect afternext power up.

-

80Admin password indefault state

Administrator password isthe default value

Change administrator password.

81

Link Group #1 N+1Protection Fault: XCCard is Down

N+1 Link Group protectiondegraded due to XC cardfault.

1) Check if XC module is insertedand powered on and no otheralarm pertained to XC is active.2) Replace XC module.


36/42

FibeAir



81

Link Group #1 N+1

Protection Fault: XCPeer CommunicationFailure

N+1 Link Group protection

degraded due to peer XCcommunication fault.

1) Verify Protection Radio link is up

and, 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 over Protecting Radiomodule (and not other Radiomodule).

81

Link 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. Replace faulty module.2) see Radio RS: LOF (SDH)

81

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

N+1 Link Group protectiondegraded due to Local-Remote ProtectionMismatch.

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 onesubrack, it should also beconfigured the same in the other

subrack).2) Check that remote IDU has allN+1 Link Group protectionpertained line modules operational.3) Verify that remote subrack is notconfigured to lockout or forcedswitch mode.4) Check that the extension cableis connected properly in the remotesubrack (if extended mode isused).

81

Link Group #1 N+1Protection Fault: Lockedby User

Lockout or Force Switch toProtecting Link Groupmaintenance commandactivated.

Release maintenance command.

401

- This alarm occurs when theconnection between theNMS and the networkelement is lost.

-

402

- This alarm occurs when theuser fails to log in to theNMS system correctly

several times consecutively.

-


37/42

FibeAir



403

- This alarm occurs when a

secondary standbyHighCapRadioNMS servertries to connect to a stand-alone HighCapRadioNMSserver.

Open the main server

configuration, and in theRedundancy section, change theserver roll from Stand Alone toMain Server.

404

- This alarm occurs for aprimary HighCapRadioNMSserver when its connectionto the standbyHighCapRadioNMS serveris lost.

-

405

- This alarm occurs for theHighCapRadioNMS serverwhen the license is set toexpire in less than twoweeks.

Contact customer support to obtaina license file for the server.

406- This alarm occurs for the

HighCapRadioNMS serverwhen the license expires.

Contact customer support to obtaina license file for the server.

407

- This alarm occurs for the

HighCapRadioNMS serverwhen the number of networkelements exceeds thelicense limit.

Remove some of the elements, or

Contact customer support to obtaina license file for the updatednumber of elements.

408

- This alarm occurs for theHighCapRadioNMS serverwhen it fails to load thelicense file.

The license file is probablycorrupted. Contact customersupport to obtain a new license file.

409

- This alarm occurs whenHighCapRadioNMSattempts to start the TFTP,

but the TFTP port (69) isalready bound by anotherprocess.

Check your system, and disableother TFTP servers.

410- This alarm occurs when a

user is disconnected byanother user.

-


38/42

FibeAir



411

- This alarm occurs when asecondary standbyHighCapRadioNMS servertries to connect to a mainHighCapRadioNMSserver,with a differentsoftware version.

Re-install one of the servers, sothat the same HighCapRadioNMSsoftware version will be on bothservers.

414- The enabled feature set is

not licensed.Disable the feature or contactSupport to get an appropriatelicense.


39/42

FibeAir


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


40/42

FibeAir


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.


41/42

FibeAir


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

Typical Network Configuration


42/42

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.

Documents

Ceragon Alarms