• Author / Uploaded
• Du Vale

Citation preview

FibeAir®

Troubleshooting Guide

Part ID: BM-0108-0 Doc ID: DOC-00015466 Rev a.00 November 2006

Notice This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd. This document is provided as is, without warranty of any kind.

Registered TradeMarks Ceragon Networks® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

TradeMarks CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are trademarks of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders.

Statement of Conditions The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it.

Information to User Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment. Copyright © 2006 by Ceragon Networks Ltd. All rights reserved.

Corporate Headquarters: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email: [email protected] North American Headquarters: Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email: [email protected]

www.ceragon.com

European Headquarters: Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email: [email protected] APAC Headquarters Ceragon Networks (HK) Ltd. Singapore RO Level 34 Centennial Tower 3 Temasek Avenue Singapore 039190 Tel - + 65 6549 7886 Fax: +65 6549 7011

Contents General .......................................................................................................... 1 Maintenance Policy ........................................................................................... 1 Visual Inspection............................................................................................... 1

Troubleshooting Guide ................................................................................ 2 The Process ....................................................................................................... 2 IDU LED Indicators............................................................................................ 3

Alarm List Table ............................................................................................ 5 Fault Isolation using Loopbacks ................................................................36 Connection Fault Guide ..............................................................................37

General Ceragon designed FibeAir to be highly reliable and relatively maintenance free. In the event of a system failure, the system will provide detailed indications to assist troubleshooting and fault isolation. This guide explains the alarm indications of the FibeAir system, and contains procedures for troubleshooting and fault isolation.

Maintenance Policy To ensure simple and efficient system maintenance, the on-site technician will only replace IDU, ODU, or RFU modules, and not repair them. Under no circumstance will the technician be permitted to open the equipment in order to repair a module or circuit board. Opening equipment will terminate the Ceragon warranty. Maintenance procedures the technician can perform include visual inspection, cleaning, cable/connector repair, link alignment/adjustment, and retorquing antenna mount bolts.

Visual Inspection The following table lists the suggested preventive maintenance procedures, which include visual inspection of the equipment and verification of operational parameters. It is recommended to perform the procedures as often as local environmental conditions require. It is recommended to notify the end customer prior to performing any preventive maintenance procedures that could affect service on the circuit. What to check

Check for ...

Comments

IDU alarm LEDs

All green

If not, perform troubleshooting

Coax cable connection

Tight, no corrosion or moisture

Clean/repair as required

Coax cable

No cracks or kinks

Replace as required

All equipment

Dust or dirt

Clean as required

Receive level (voltage in IDU/ODU/RFU, or using management)

Per installation records

Align/adjust as required

Torque on antenna mount bolts

Tight mount

Adjust as required

FibeAir® Troubleshooting Guide

1

Troubleshooting Guide The Process Corrective maintenance consists of the steps described in the following sections. The steps provide a logical, sequential method for diagnosing and resolving system problems.

Step 1: Define the Symptom This step is generally peformed by the customer's field technician or supervisor. Examples of symptoms include “IDU alarm is red”, “complete loss of service”, and “excessive errors”. Symptoms may be constant or intermittent. Constant symptoms require immediate troubleshooting attention. Intermittent symptoms may require circuit monitoring or robust test procedures prior to troubleshooting.

Step 2: Isolate the Problem After you have a clear definition of the symptom, the malfunction can be isolated using diagnostics, loopback testing, fault isolation tables/flow charts, test equipment, and manual procedures. This step will identify the specific piece of equipment that is failing. Although it may be difficult at times to immediately determine which part of a radio link is causing the fault, the initial suspicion should be focused on one of the following near-end or far-end issues: y

Power supplies

y

Fading (due to heavy rain, new obstacle in path, antenna misalignment)

y

External equipment (SONET/SDH, ATM, 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.

FibeAir® Troubleshooting Guide

2

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

Color LED

Red

PWR (Power)

X

LINE

X

LOF (Loss of Frame)

X

BER (Bit Error Ratio)

X

LPBK (Loopback)

X

STBY (Standby)

Yello w

Green

Description

X

Red - power supply problem

X

Red - no input to main channel / high BER Yellow - JO mismatch

X

Red - radio did not recognize information frame (radio link problem/radio LOF)

X

Red - radio BER higher than radio excessive error threshold definition (see Sonet/SDH configuration window) Yellow - radio BER higher than radio signal degrade threshold definition (see Sonet/SDH configuration window)

X

Red - loopback is active

X

X

Yellow - Protected configuration. The unit is currently passive or Tx mute is operating

X

X

IDU

X

X

X

Red - modem unlocked Yellow - high temperature / fan problem

ODU

X

X

X

Red - no link, or ODU power, or ODU/RFU unlocked Yellow - radio interference, or high temperature, or Rx/Tx out of range

CBL (Cable)

X

X

Red - RF cable open / RF cable short

RMT (Remote Unit)

X

X

Red - no link / remote unit problem (red LED is lit in the remote unit)

FibeAir® Troubleshooting Guide

X

Yellow - warning in remote unit (yellow LED is lit in the remote unit)

3

LED Indications for Hitless Systems For Hitless systems, the following table lists the LEDs and their indications: LOF (LED Panel) - LOF LED Color

Alarm Explanation

Yellow

Local unit receives LOF from a receive path currently not in use.

Red

Local unit receives LOF from a receive path currently in use.

LOF (Interface Panel) - ALRM LED Color

Alarm Explanation

OFF

Hitless mode is disabled.

Red

Local unit receives LOF from the mate unit.

Green

Hitless switching can be performed, if necessary.

Local Receiver (Interface Panel) - Rx ACTV LED Color

Alarm Explanation

OFF

Local receiver not in use.

Green

Local receiver in use.

FibeAir® Troubleshooting Guide

4

Alarm List Table The table below lists trap IDs, trap descriptions, probable causes, and corrective actions. A note about interface troubleshooting: If, after the radio link is installed, the payload is not received, there may be a problem either with the line interface connection to FibeAir, or with external equipment. Before you perform line interface troubleshooting, check the following items, which are common causes of line interface failures: y

External equipment Tx is connected to FibeAir Rx.

y

External equipment Rx is connected to FibeAir Tx.

y

Both external equipment and FibeAir are using the same interface (single mode, multi-mode).

y

For multi-mode interfaces, check that you are using multi-mode fibers to connect the unit. For single mode interfaces, check that you are using single mode fibers.

If no problem is detected with any of the items above, proceed with the table below. Alarm List with Corrective Actions Trap ID

Description

Probable Cause

Corrective Actions

Insufficient system configuration for full XPIC Support

One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.

1) Verify the existence of all IDMs and ODU, and verify their connectivity. 2) Open the unit Alarm Log (using the element manager) and send to customer support the code at the end of the "XPIC Insufficient" event text.

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

One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.

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

Synthesizer #1/2/3 Unlocked

One of the ODU synthisizers is unlocked.

Replace ODU. (In XPIC configuration, the ODU may be taking the sync from the mate ODU. In that case, check if alarm persists in non-XPIC configuration.)

Tx Level Out of Range

The ODU cannot transmit the requested Tx power.

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

0

10

11

12

FibeAir® Troubleshooting Guide

5

Trap ID

Description

Probable Cause

Tx Mute On/Off

ODU muted by user

1) Check if Power Input connected to -48 VDC supply. 2) Check -48 VDC supply to the subrack. 3) Disable Power Input if you do not use redundant power feed.

Rx Level Out of Range

RSL is very low (typically below -80 dBm), link is down.

1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Replace local/remote ODU.

ODU Temperature Out of Range

ODU temperature too high/low.

1) Check installation conditions. 2) Replace ODU.

Power Input #2 is Down

Subrack redundant power feed failure.

1) Verify if the Power Input card exists in the subrack. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack. 4) Replace Power Input card if problem still exists. 5) Disable Power Input if you do not use redundant power feed.

Power Input #1 is Down

Subrack redundant power feed failure.

1) Verify if the Power Input card exists in the subrack. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack. 4) Replace Power Input card if problem still exists. 5) Disable Power Input if you do not use redundant power feed.

XPIC Cable Swap

Left/Right cables swap in XPIC configuration. If Drawer ID Mismatch (see above) alarm is identified in both drawers, the IF (coax) cables between the drawers and ODUs on one end are swapped.

1) Verify correct cable connection.

Failure in an IDU power supply.

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

12

13

14

15

15

15

15

Corrective Actions

IDU 5/8/3.3/-5V Power Supply Failure

FibeAir® Troubleshooting Guide

Recommended connection is V to Right drawer and H to Left drawer

6

Trap ID

Description

Probable Cause

Corrective Actions

15

Drawer Power On/Off

Drawer power on/off.

-

15

Drawer Internal Power Failure (Board #1)

Drawer Internal Power Failure (Board #1)

-

Drawer Internal Power Failure (Board #2)

Board #1 - MUX card. Board #2 - Modem card. This alarm may also be generated if a drawer in Internal Protection was switched off.

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

Extension Link Communication Failure

Problem with extension cable or the connection between the 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, verify that the other subrack is configured to extension mode properly. 3) Check that the XC boards in both subracks are inserted properly and the extension cable is plugged in. 4) Replace extension cable. 5) Replace XC boards.

Cable Open/Short

IDU-ODU cable open/short.

1) Check IF cable and connectors. 2) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 3) Replace IDU. 4) Replace ODU.

Cable Open

IDM-ODU cable open

1) Check IF cable and connectors 2) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 3) Replace IDM. 4) Replace ODU.

MRMC= Script File is Missing

Multi-Rate MultiConstellation configuration script for the specified capacity/modulation is missing in the IDC.

1) Download the Modem script to the IDC and reset the IDM.

Drawer Internal Hardware Intact/Failure Board#1

Drawer hardware intact ok / failure (Mux)

1) In case of failure, replace IDM.

17

18

IDU Temperature Out of Range

IDU Temperature Out of Range

1) Check installation conditions. 2) Replace IDM.

15

16

16

16

17

FibeAir® Troubleshooting Guide

7

Trap ID

Description

Probable Cause

Corrective Actions

18

Fan Failure

Fan Failure

1) Replace fan.

19

XC Internal Loopback on Line #5

XC board Internal port loopback

1) Disable loopback

19

XC Internal Loopback on Line #4

XC board Internal port loopback

1) Disable loopback

19

XC Internal Loopback on Line #3

XC board Internal port loopback

1) Disable loopback

19

XC Internal Loopback on Line #2

XC board Internal port loopback

1) Disable loopback

19

XC Internal Loopback on Line #1

XC board Internal port loopback

1) Disable loopback

Wayside Channel Loopback

Wayside Line loopback applied by user in internal protection

Disable Wayside line loopback

19

Wayside Channel Loopback

Wayside Left Line loopback applied by user

Disable Wayside line loopback

19

ODU Internal Loopback (Not) Active

ODU RF loopback applied by user

1) Disable loopback

Loopback applied by user

1) Disable loopback

19

IDU Remote Loopback (Not) Active ?10;IDU Line Loopback (Not) Active?10;E1\T1\E3\DS 3 #n Internal Loopback (Not) Active?10;E1\T1\E3\DS 3 #n External Loopback (Not) Active

19

Internal Loopback on Fiber #n

Internal loopback on Fiber

1) Disable loopback

19

External Loopback on Fiber #n

IDU Line loopback applied by user

1) Disable loopback

19

E1\T1 Internal Loopback on Port #n

IDU Line loopback applied by user

1) Disable loopback

19

IDU Local Loopback (Not) Active

IDU IF loopback applied by user

1) Disable loopback

19

FibeAir® Troubleshooting Guide

8

Trap ID 19

20

21

21

22

Description

Probable Cause

E1\T1 External Loopback on Port #n

E1/T1 External loopback

1) Disable loopback

Remote Communication Failure

No communication between the IDUs over the link.

1) Verify link is up and no errors over the link. 2) Check in-band management configuration.

PRBS Test is Running on Radio

PRBS test started.

Disable PRBS test.

Link Group #1 N+1 Protection Fault: Locked by User

Lockout or Force Switch to Protecting Link Group maintenance command activated.

Release maintenance command.

Trib RS: LOF

Trib RS: LOF

Radio RS: LOF

Radio 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,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs.

Link Group #1 N+1 Protection Fault: Protecting Radio Failure

N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board.

1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH)

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

Loss Of Frame alarm on the radio, link is down

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

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 transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM.

22

22

Corrective Actions

22

22

FibeAir® Troubleshooting Guide

9

Trap ID

Description

Probable Cause

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 transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU.

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,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs

Trib RS: LOS

Trib RS: LOS

Loss of Signal on Fiber #n

Loss Of Signal alarm on the line input

1) Check line input. 2) Check fibers/cables. 3) Verify that end equipment transmits properly. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM.

Fiber RS: LOS or?10;E1\T1\E3\DS3 #n Loss of Signal?10;Fiber RS: LOS

Loss Of Signal alarm on the line input

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU.

Gigabit Ethernet Loss of Signal

1) Check line input. 2) Check fiber. 3) Verify end equipment transmits properly. 4) Replace IDM.

Fast Ethernet Loss of Carrier on Port #n

Fast Ethernet Loss of Carrier

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

Fast Eth. #01/02 Loss of Carrier

Fast Ethernet Loss of Carrier

1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDU.

22

22

23

23

23

Corrective Actions

23

23

23

FibeAir® Troubleshooting Guide

10

Trap ID

Description

Probable Cause

Corrective Actions

E1\T1 Loss of Signal on Port #n

E1\T1 Loss of Signal

24

Trib RS: TIM

Trib RS: TIM

-

24

Trib LP #n: TIM

Trib LP #n: TIM

-

24

Trib HP: TIM

Trib HP: TIM

-

24

Trace Identifier Mismatch on Fiber #n

Trace Identifier Mismatch alarm (J0 mismatch).

24

Radio LP #n: TIM

Radio LP: TIM

-

24

Radio HP: TIM

Radio HP: TIM

-

24

Fiber RS: TIM

Fiber RS: TIM

-

24

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

-

25

Trib LP #n Excessive BER

Trib LP #n Excessive BER

-

25

Trib HP: Excessive BER

Trib HP: Excessive BER

-

25

Radio RS: Excessive BER

Radio RS: Excessive BER (Regenerator)

-

25

Radio RS: Excessive BER

Radio RS: Excessive BER (Regenerator)

-

25

Radio RS: Excessive BER

Radio RS: Excessive BER (ADM)

-

23

FibeAir® Troubleshooting Guide

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM.

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

11

Trap ID

Description

Probable Cause

Corrective Actions

25

Radio MS: Excessive BER

Radio MS: Excessive BER

-

25

Radio LP #n: Excessive BER

Radio LP: Excessive BER

-

25

Radio HP: Excessive BER

Radio HP: Excessive BER

-

Excessive BER on Radio #n

Major radio Excessive BER alarm

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

Excessive BER on Fiber #n

Major line Excessive BER alarm

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM.

E1\T1 Excessive BER on Port #n

Major Excessive BER alarm on E1/T1 port

1) Check line input. 2) Check cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDM is ok. 5) Replace IDM.

25

Fiber RS: Excessive BER

Fiber RS: Excessive BER (Regenerator)

-

25

Fiber RS: Excessive BER

Fiber RS: Excessive BER (Regenerator)

-

25

Fiber RS: Excessive BER

Fiber RS: Excessive BER (ADM)

-

25

Fiber MS: Excessive BER

Fiber MS: Excessive BER

-

25

Fiber LP #n Excessive BER

Fiber LP #n Excessive BER

-

25

Fiber HP: Excessive BER

Fiber HP: Excessive BER

-

25

25

25

FibeAir® Troubleshooting Guide

12

Trap ID

Description

Probable Cause

Corrective Actions

25

E1\T1\E3\DS3 #n Excessive BER

E3DS3 Excessive BER

-

25

E1\T1\E3\DS3 #n Excessive BER

E1/T1 Excessive BER

-

26

Trib RS: Signal Degrade

Trib RS: Signal Degrade

-

26

Trib MS: Signal Degrade

Trib MS: Signal Degrade

-

26

Trib LP #n Signal Degrade

Trib LP #n Signal Degrade

-

26

Trib HP: Signal Degrade

Trib HP: Signal Degrade

-

26

Radio RS: Signal Degrade

Radio RS: Signal Degrade

-

26

Radio RS: Signal Degrade

Radio RS: Signal Degrade

-

26

Radio RS: Signal Degrade

Radio RS: Signal Degrade

-

26

Radio LP #n: Signal Degrade

Radio LP #n: Signal Degrade

-

26

Radio MS: Signal Degrade

Radio HP: Unequipped

-

26

Radio HP: Signal Degrade

Radio HP: Signal Degrade

-

Signal Degrade on Radio #n

Minor radio BER alarm

1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

Signal Degrade on Fiber #n

Minor line SD BER alarm

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM.

26

26

FibeAir® Troubleshooting Guide

13

Trap ID

Description

Probable Cause

Corrective Actions

Fiber RS: Signal Degrade

Minor line BER alarm

1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU.

E1\T1 Signal Degrade on Port #n

Minor BER alarm on E1/T1 port

1) Check line input. 2) Check cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDM is ok. 5) Replace IDM.

26

Fiber RS: Signal Degrade

Fiber RS: Signal Degrade (ADM)

-

26

Fiber RS: Signal Degrade

Fiber RS: Signal Degrade

-

26

Fiber MS: Signal Degrade

Fiber MS: Signal Degrade

-

26

Fiber LP #n Signal Degrade

Fiber LP #n Signal Degrade

-

26

Fiber HP: Signal Degrade

Fiber HP: Signal Degrade

-

26

E1\T1\E3\DS3 #n Signal Degrade

E3DS3 Signal Degrade

-

26

E1\T1\E3\DS3 #n Signal Degrade

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

-

26

26

FibeAir® Troubleshooting Guide

14

Trap ID

Description

Probable Cause

Corrective Actions

27

Fiber LP #n: AIS

Fiber LP #n: AIS

-

27

Fiber HP: AIS

Fiber HP: AIS

-

28

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

Unexpected signal on the line input. Port disabled but line is connected.

28

Trib RS: Unexpected Signal

Trib RS: Excessive BER

-

28

Gigabit Ethernet Unexpected Signal

GbE port is disabled but GbE data is detected.

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

28

Fast Ethernet Unexpected Signal on Port #n

Fast Ethernet Unexpected Signal on Port #n

-

30

Trib LP #n: LOP

Trib LP #n: LOP

-

30

Trib HP: LOP

Trib HP: LOP

-

Radio LP #n: LOP

Radio LP: Loss of pointer (LOP) alarm occurs.

-

Radio HP: LOP

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

-

Fiber LP #n: LOP

Fiber LP: Loss of pointer (LOP) alarm occurs.

-

Fiber HP: LOP

Fiber 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

-

Radio MS: RDI

Radio MS: Remote Defect Identifier signal (RDI) occurs.

-

Radio LP #n: RDI

Radio LP: Remote Defect Identifier signal (RDI) occurs.

-

30

30

30

30

31

31

FibeAir® Troubleshooting Guide

1) Enable line port or disconnect line

15

Trap ID

Description

Probable Cause

Corrective Actions

Radio HP: RDI

Radio HP: Remote Defect Identifier signal (RDI) occurs.

-

Fiber MS: RDI

Fiber MS: Remote Defect Identifier signal (RDI) occurs.

-

Fiber LP #n: RDI

Fiber LP: Remote Defect Identifier signal (RDI) occurs.

-

Fiber HP: RDI

Fiber HP: Remote Defect Identifier signal (RDI) occurs.

-

32

Trib LP #n: PLM

Trib LP #n: PLM

-

32

Trib HP: PLM

Trib HP: PLM

-

Radio LP #n: PLM

Radio LP: Payload Label Mismatch (PLM) occurs.

-

Radio HP: PLM

Radio HP: Payload Label Mismatch (PLM) occurs.

-

Fiber LP #n: PLM

Fiber LP: Payload Label Mismatch (PLM) occurs.

-

Fiber HP: PLM

Fiber HP: Payload Label Mismatch (PLM) occurs.

-

33

Trib LP #n: Unequipped

Trib LP #n: Unequipped

-

33

Trib HP: Unequipped

Trib HP: Unequipped

-

33

Radio LP #n: Unequipped

Radio LP: Unequipped

-

33

Radio HP: Unequipped

Radio HP: Unequipped

-

33

Fiber LP #n: Unequipped

Fiber LP: Unequipped

-

33

Fiber HP: Unequipped

Fiber HP: Unequipped

-

External Alarm

External alarm input #1 configured and triggered by user.

-

31

31

31

31

32

32

32

32

34

FibeAir® Troubleshooting Guide

16

Trap ID

Description

Probable Cause

Corrective Actions

External Alarm

External alarm input #2 configured and triggered by user.

-

External Alarm

External alarm input #3 configured and triggered by user.

-

External Alarm

External alarm input #4 configured and triggered by user.

-

External Alarm

External alarm input #5 configured and triggered by user.

-

External Alarm

External alarm input #6 configured and triggered by user.

-

External Alarm

External alarm input #7 configured and triggered by user.

-

External Alarm

External alarm input #8 configured and triggered by user.

-

General Hardware Fault #3

XO failure – Mux board

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

General Hardware Fault #2

XO failure – Modem board

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

XC FPGA File is Missing

XC firmware file is missing in the 2-floor IDC.

1) Download XC firmware file of the required type and reset the IDC.

42

General Hardware Fault #11

Wrong card type detected in Subrack Auxiliary slot.

1) Replace Subrack Auxiliary module.

42

Wayside Firmware File is Missing

Wayside firmware file is missing in the IDC.

1) Download Wayside firmware file to the IDC and reset the IDC.

35

36

37

38

39

40

41

42

42

42

FibeAir® Troubleshooting Guide

17

Trap ID

Description

42

42

42

42

Subrack Auxiliary module failed or extracted.

1) Check Subrack Auxiliary module is properly inserted. 2) Replace Subrack Auxiliary module.

Subrack Auxiliary FPGA File is Missing

Subrack Auxiliary firmware file is missing in the 2-floor IDC.

1) Download Subrack Auxiliary firmware file and reset the IDC.

General Hardware Fault #10

Subrack Auxiliary EEPROM checksum failure.

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

Secondary Clock Source Failure

Secondary Clock Source Failure

Radio Card #n Powered Down

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

Primary Clock Source Failure

Primary Clock Source Failure

EOW chaining Loss of Signal

No signal detected on Subrack Auxiliary EOW chaining input.

1) Disable EOW chaining if not required. 2) Check EOW chaining line input on both subracks. 3) Check / fix EOW chaining configuration on mate subrack. Verify that EOW is defined on at least one working link on mate subrack. 4) Replace EOW chaining cable. 5) Perform reset to the local / mate Subrack Auxiliary module (by extracting and inserting IDC2). 6) Replace local / mate Subrack Auxiliary module. 7) Check / replace IDC2 on mate subrack.

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

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

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

42

42

Corrective Actions

Auxiliary Card Fault #01 42

42

Probable Cause

FibeAir® Troubleshooting Guide

-

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

18

Trap ID

Description

Probable Cause

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

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

1) Verify Protection Radio link is up and, no errors over the link. 2) Check that remote IDU is properly configured for N+1 Link Group protection. 3) Check that remote IDU has properly operational XC board. 4) Check that Protection Radio link terminates over Protecting Radio module (and not other Radio module).

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

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

1) Check that remote IDU is properly configured with N+1 Link Group topology. 2) Check that remote IDU has all relevant N+1 Link Group protection line modules operational.

General Hardware Fault #9

Upper IDM Board (MUX or XC) EEPROM inventory information CRC error

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

General Hardware Fault #8

Upper IDM Board (MUX or XC) EEPROM read access error

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

General Hardware Fault #11

Lower IDM Board (Modem or XC) EEPROM inventory information CRC error

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

General Hardware Fault #10

Lower IDM Board (Modem or XC) EEPROM read access error

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

Line Card #n Powered Down

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

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

42

42

Corrective Actions

42

42

42

42

42

FibeAir® Troubleshooting Guide

19

Trap ID

Description

Probable Cause

Corrective Actions

Line Card #1 Powered Down

Line module in carrrier #1 of the Link Protection group is powered down or extracted.

1) Check if the card is inserted properly in the subrack. 2) Check if own or redundant power supply / Radio module is powered on. 3) Replace module if faulty.

Drawer Internal Power Failure (Board #2)

Internal Power failure.

1) Check that proper Subrack Auxiliary module inserted. 2) Extract and re-insert Subrack Auxiliary module. 3) Replace Subrack Auxiliary module.

XPIC Cable Swap

Internal IDC to IDC communication failure between modules requied for Link Group protection service.

1) Check that IDC #n is power up and finished initialization. 2) Check & configure both IDCs with proper system configuration: System Type, Subrack#, Subrack IP Base Address, Link Group Topology. 3) Check for Hardware fault: Subrack Auxiliary module, Ethernet cable (if applicable), IDC modules. Replace faulty module.

General Hardware Fault #4

IDU XPIC HW fault

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

General Hardware Fault #1

IDU Synthesizer lock

1) Download correct SW/FW/Configuration scripts. 2) Power IDM off/on. 3) Replace IDM. 3) Replace IDC.

42

Drawer Internal Loopback

IDU IF loop applied by user

1) Disable loopback

42

Copy IDC Configuration to Mate

IDC copy configuration by user in external protection

-

IDU-ODU Inner Communication Failure

IDC cannot communicate with ODC card.

1) Check ODU connection to the IDU. 2) Check IF cable and connectors. 3) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 4) Replace ODU. 5) Replace IDU.

42

42

42

42

42

42

FibeAir® Troubleshooting Guide

20

Trap ID

42

Description

Probable Cause

IDU-MUX Inner Communication Failure

IDC cannot communicate with MUX card, MUX card upload failure.

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

General Hardware Fault #7

FPGA load failure - Subrack Auxiliary board.

1) Download correct Subrack Auxiliary FW file to 2-floor IDC, and then extract and re-insert Subrack Auxiliary board 2) Replace Subrack Auxiliary module. 3) Replace 2-floor IDC.

General Hardware Fault #6

FPGA load failure - Mux

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

General Hardware Fault #7

FPGA load failure - Modem

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

Drawer-ODU Communication Failure

Drawer cannot communicate with ODC card.

1) Check ODU connection to IDM. 2) Check IF cable and connectors. 3) Check ODU's N-type connector inner pin is not spliced (if yes, replace ODU). 4) Replace ODU. 5) Replace IDM.

42

42

42

Corrective Actions

42

For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU General Hardware Fault #5

DAC failure

42

Clock Unit Unlocked

Clock Unit Unlocked

-

42

Clock Unit Out of Range

Clock Unit Out of Range

-

Copy Carrier Configuration To Mate Failed/Succedded

Carrier configuration copied between two IDMs in protected configuration

-

42

42

MUX Firmware File is Missing

A Mux FW file is missing from the system.

42

FibeAir® Troubleshooting Guide

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

Load the required FW file, and reset system.

21

Trap ID

Description

Probable Cause

42

Modem Firmware File is Missing

A Modem FW file is missing from the system. Software download operation status (from user's PC to IDC)

-

43

TFTP IDU/MUX/ODU verxxx Download Succeeded/ Canceled/Failed

File download status. Initiated by user.?9;

-

43

Boot/IDC/MUX/ODU/Mo dem Script/Modem/ Wayside/Mrmc table/RFU FPGA File Download Succeeded

Configuration download status, initiated by user

-

43

IDU Configuration Download Succeeded/Error/Cance lled/Failed/Invalid File ODU SW Upload Failed

Software upload operation status (from IDC to ODC)

-

ODU SW Upload Error

Software upload operation status (from IDC to ODC)

-

44

ODU SW Upload Canceled

Software upload operation status (from IDC to ODC)

-

MUX/ODU Internal Download Succeeded/Canceled/Failed /Error

-

44

MUX/ODU Internal Download Succeeded/Canceled/F ailed/Error RFU FW Upload Failed

Firmware upload operation status (from IDC to ODC)

-

RFU FW Upload Error

Firmware upload operation status (from IDC to ODC)

-

RFU FW Upload Canceled

Firmware upload operation status (from IDC to ODC)

-

General Hardware Fault #2

WSC board configuration failure – Error during reading board configuration – CRC error

44

44

44

44

44

46

FibeAir® Troubleshooting Guide

Corrective Actions Load the required FW file, and reset system.

1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.

22

Trap ID

Description

Probable Cause

Corrective Actions

General Hardware Fault #3

WSC board configuration failure – Can't detect board configuration (can't read from E2PROM)

1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.

General Cfg Mismatch

Settings not supported by HW/SW.

1) Check if HW and SW support the requested configuration

Mate Configuration Mismatch () M=xx, L=xx

Mismatch in the internal protection configuration between the drawers.

1) Check and compare configuration 2) See mate Configuration Mismatch Alarm

User Configuration Mismatch () S=xx, D=xx

Mismatch configuration between the IDC Database and the drawer.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.

Mate Configuration Mismatch () M=xx, L=xx

Mismatch configuration between local IDC Database and mate IDC database

1) Check and compare configuration 2) See mate Configuration Mismatch Alarm

46

Link ID Mismatch

Link ID Mismatch

46

Link ID Mismatch on Radio #n

Link ID is not identical on both ends of the link.

Set identical Link ID on both ends of the link.

Link ID Mismatch

Link ID is not identical on both ends of the link.

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

Link ID Mismatch

Link ID is not identical on both ends of the link.

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

Protection Mismatch

Internal system mismatch regarding the state of the radio – Mute/Unmute

Reset IDM

Auxiliary Channel User Configuration Mismatch

Incorrect Auxiliary channel configuration

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

46

46

46

46

46

46

46

46

46

FibeAir® Troubleshooting Guide

-

23

Trap ID

Description

Probable Cause

Corrective Actions

Device Incompatible Alarm (#103)

Incomapitibility alarm between link components. Typically refers to mixture of standard and "I" components in the link

1) Check link components

46

General Hardware Fault #4

IDC MAC device failure – loading with default MAC address

1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.

46

General Hardware Fault #1

FPGA load failure – Wayside Channel

1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.

Drawer ID Mismatch

Drawer receives signal of the other drawer across the XPIC link. Indicates problem in the XPIC link (such as failure in one of the transmitters or insufficient XPI)

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

Drawer ID Mismatch in Protecting Carrier

Drawer #1 receives signal of the mate drawer (#2) across the XPIC link. Indicates problem in the XPIC link (such as failure in one of the transmitters or insufficient XPI), detected by the XC board.

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

46

IDU Hitless Mate Config Mismatch

Different configuration between the IDUs on the same side of the link

1) Check and compare configurations

46

IDU Hitless Remote Config Mismatch

Different configuration between the IDUs on both sides of the link

1) Check and compare configurations

46

User Configuration Mismatch () S=xx, D=xx

Configuration in the IDC is different than the configuration in the drawers or in the Auxiliary channels board

1) Check and compare configuration 2) See User Configuration Mismatch Alarm

Mate Configuration Mismatch

Configuration mismatch between two IDCs in External Protection configuration.

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

46

46

46

46

FibeAir® Troubleshooting Guide

24

Trap ID

Description

Probable Cause

Mate Configuration Mismatch

Configuration mismatch between two drawers in External Protection configuration.

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

User Configuration Mismatch

At least one Link Group configuration parameter in the IDC Database is different than the actual configuration in the XC. Raised only after IDC hotswap or S/W reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC, or "Copy to Drawer" for mismatch resolution.

User Configuration Mismatch

At least one IDC configuration parameter in the IDC Data Base (XPIC for example) is different than the configuration in the drawers or in the Auxiliary channels. Raised only after IDC hotswap / software reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy drawer to IDC" command to copy the XPIC/protection configuration from the drawer to the IDC (without reset). The process will eliminate the mismatch. The IDC parameters (IP addresses, in-band, external alarms) are not copied. 3) Use "Upload/Download Configuration" command followed by S/W reset in order to copy ALL IDC configurations to the IDC.

User Configuration Mismatch

At least one drawer configuration parameter in the IDC Database is different than the actual configuration in the drawers. Raised only after IDC hotswap or S/W reset.

1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from the drawer to the IDC, or "Copy to Drawer", eliminating the mismatch. However, "copy to drawer" command does not copy the protection or XPIC properties (thay are IDC parameters). IDC parameters (IP addresses, inband) are not copied. 3) Use "Upload/Download Configuration" command followed by S/W reset in order to copy ALL IDC configurations to the IDC.

User Configuration Mismatch between IDC # and IDC #

At least one configuration parameter which should be equal in these two IDCs has different values.

1) Check the mismatch configuration in the alarms log. 2) Configure the relevant IDC with the correct values for mismatch resolution, and wait one minute for the mismatch alarm to clear.

46

46

46

46

46

Corrective Actions

FibeAir® Troubleshooting Guide

25

Trap ID

Description

Probable Cause

Corrective Actions

47

Protection Internal/External Mate Not Exist

System configured for protection without mate connected

47

Protection External Alarm Switch

Protection switch by external alarm

47

Hitless Protection Configuration Mismatch

Hitless is configred without protection

1) Enable protection or disable hitless

Protection Change to Standby

Different faults indicate hardware failure on the drawer

1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC.

Change Remote Transmitter Request Sent - SDBER / EXBER / LOF / BER

Command was sent to remote end to switch when both local receivers identify Rx fault (for example, remote active transmitter fails)

-

Change Master/Slave command

-

47

SW Mode Changed to Slave/Master?10; Change Remote Transmitter Request Sent

48

Protection Cable Disconnected

Protection Cable Disconnected

1) Connect Protection Cable. 2) Replace cable.

Problem with protection cable or the connection between the Master/Slave IDUs

1) Replace cable. 2) Replace IDUs

48

Protection Cable Disconnect/Error/Power Error/Problem?10; Master-Slave Disconnect

48

Protection Communication Error on Cable

For External Protection configuration. Protection cable is connected but errors detected.

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

49

Heart Beat (Trap Only)

Heart Beat (Trap Only)

-

50

Trib HP: LOM

Trib HP: LOM

-

Radio HP: LOM

Radio HP: Loss of Multiframe (LOM) alarm occurs.

-

47

47

50

FibeAir® Troubleshooting Guide

1) Check configuration. 2) Check Mate connected

-

26

Trap ID

Description

Probable Cause

Corrective Actions

Fiber HP: LOM

Fiber HP: Loss of Multiframe (LOM) alarm occurs.

-

51

Hitless Left/Right Receiver in Use

Left/Right receiver is used for processing data

Not a real alarm since receiver switching is likely to happen during multipath fading.

Hitless Switch Locked to Right Radio By User

Hitless switching disabled by user and locked for one of the drawers.

1) Disable Hitless Lockout

51

Hitless Switch Locked to Left Radio By User

Hitless switching disabled by user and locked for one of the drawers.

1) Disable Hitless Lockout

51

51

Hitless Switch Locked to Self Radio By User

Hitless Switch Locked to Self Radio by User

-

Hitless Switch Locked to Mate/Self Radio By User

Hitless Switch Locked to Mate/Self Radio by User

-

51

51

Hitless Self/Mate Receiver in user

Hitless Self/Mate Receiver in user

-

Hitless Functionality Failure

Hitless protection is not available. The link will fail in case of fade.

1) Hitless cable disconnected. 2) Mate IDU is off. 3) Mate IDU has an alarm that prevents it from receiving data.

Loss of Frame on Unused Left/Right Radio

Permanent Radio LOF in the receiver (raised after 10 consecutive seconds of radio Loss Of Frame). Implies a permanent problem, unlike fading due to multipath condition, which is intermittent in nature.

Same as Radio LOF alarm: 1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs

Unused Radio Receiver LOF

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

50

51

52

52

FibeAir® Troubleshooting Guide

27

Trap ID

Description

Probable Cause

Corrective Actions

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

52

Hitless Self Radio Receiver LOF

Hitless Self Radio Receiver LOF

-

53

Hitless Cable Disconnect

Hitless cable disconnected.

Connect hitless cable.

57

In-Band Radio PPP Link Disconnect?10;In-Band Line PPP Link Disconnect

In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected.

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

User Channel Ethernet Loss of Carrier

User Right Channel Loss of Carrier

1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.

User Channel Ethernet Loss of Carrier

User Left Channel Loss of Carrier

1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.

User Channel Ethernet Loss of Carrier

User Channel Loss of Carrier in internal protection

1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.

52

58

58

58

FibeAir® Troubleshooting Guide

28

Trap ID

Description

Probable Cause

Wayside Channel Loss of Signal/Carrier

Wayside Channel Loss of Signal/Carrier in internal protection

1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.

Wayside Channel Loss of Signal/Carrier

Wayside Right Channel Loss of 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 Auxiliary module.

Wayside Channel Loss of Signal/Carrier

Wayside Left Channel Loss of 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 Auxiliary module.

ODU-2-ODU Cable Open

ODU-2-ODU Cable Open

1) Check cable. 2) Replace cable.

No Signal from ODU

No Rx (140 MHz) signal from ODU

58

58

58

59

Corrective Actions

60

1) Check IF cable and connectors 2) Check that ODU's Ntype connector inner pin is not spliced (if yes, replace ODU). 3) Replace IDM. 4) Replace ODU. For High Power RF Unit: Check BMA connector center pin is not spliced both on RFU and on OCB.

60

Modem Script Not Supported

Modem Script Not Supported

Protection Force Switch

One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.

61

FibeAir® Troubleshooting Guide

-

1) Disable "Force Switch"

29

Trap ID

Description

"Protection Lockout" command executed. Will lock the switching operation until removed.

1) Disable Lockout

RFU Power Failure (Vd)

RFU Power Supply Failure (Vd)

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

RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)

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

RFU Power Failure (6v pro)

RFU Power Supply Failure (6v pro)

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

RFU Power Failure (12v)

RFU Power Supply Failure (12v)

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

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.

RFU Rx Level Path1 Out Of Range

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

1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU.

RFU Rx Level Path2 Out Of Range

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

1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU.

RFU Extreme Temperature

RFU temperature is too high/low.

1) Check installation conditions. 2) Replace RFU

62

62

62

62

63

63

64

Corrective Actions

Protection Lockout 61

62

Probable Cause

FibeAir® Troubleshooting Guide

30

Trap ID

Description

Probable Cause

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 of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4)Check antenna connections 5)Replace local/remote ODU.

RFU Fan Failure

Fan Failure was detected by RFU

1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fans drawer 5) Replace RFU

RFU Fan Failure

Fan Failure was detected by RFU

1) Check RFU connection to BP 2) Check that fans are connected to PS 3) Replace RFU BP cable 4) Replace specific fan or fans drawer 5) Replace RFU

RFU Low Signal To ODU

RFU is detecting low signal from IDU

1) Check RFU IF cable connection 2) Reconnect the IF cable 3) Replace RFU

RFU XPIC Clock Failure

No XPIC clock is received from Master RFU

1) Reconnect XPIC clock cables at both RFUs 2) Replace XPIC cable

RFU Delay Calibration Failure 1

Delay calibration is unseccessfull since RX AGC is unlocked.

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

RFU Delay Calibration Failure 2

Delay calibration is unseccessfull since wide or deep notch has been detected at the RX signal

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

Gigabit Ethernet SFP Not Intact

SFP is not connected properly.

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

65

65

65

66

67

68

69

70

Corrective Actions

FibeAir® Troubleshooting Guide

31

Trap ID

70

Description

72

SFP does not transmit Ethernet properly.

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

Gigabit Ethernet TX Mute Override

GbE port is enabled by the user but the system overrides this and mutes the port. This alarm may appear in the following cases: Radio LOF (local or remote), Link ID mismatch (local or remote), excessive BER (local or remote), Signal degrade (local or remote), GbE LOS (remote)

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

Encryption Fault

HW encryption fault

1) Reset IDM.

Encryption Sync Loss

Encryption loss of frame

1) Check link staus. 2) Reset IDM.

Initial KEP Failed

The first encryption key exchange failed

1) Check link status. 2) Reset IDC. 3) Reset IDM.

Session Key Timer Elapsed

No session key exchange in the allowed time

1)Check link status.

Power-Up Test Failed

One of the built-in encryption system tests failed

1) Reset IDC. 2) Reset IDM.

Conditional Test Failed

One of the Conditional tests failed

1) Reset IDC. 2) Reset IDM.

Encryption Will Turned Off On Next Reset

Encryption mode changed by user, will take effect after next power up.

Admin password in default state

Administrator password is the default value

Change administrator password.

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

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

1) Check if XC module is inserted and powered on and no other alarm pertained to XC is active. 2) Replace XC module.

73

74

75

76

77

80

81

Corrective Actions

Gigabit Ethernet SFP TX Fault

70

71

Probable Cause

FibeAir® Troubleshooting Guide

-

32

Trap ID

Description

Probable Cause

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

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

1) Verify Protection Radio link is up and, no errors over the link. 2) Check that remote IDU is properly configured for N+1 Link Group protection. 3) Check that remote IDU has properly operational XC board. 4) Check that Protection Radio link terminates over Protecting Radio module (and not other Radio module).

Link Group #1 N+1 Protection Fault: Protecting Radio Failure

N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board.

1) Check Protecting Radio module is powered on and operates properly. Replace faulty module. 2) see Radio RS: LOF (SDH)

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

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

1) Check that remote IDU is properly configured with N+1 Link Group topology, and all protection members are configured with the same priority level (if extra traffic is configured as revertive in one subrack, it should also be configured the same in the other subrack). 2) Check that remote IDU has all N+1 Link Group protection pertained line modules operational. 3) Verify that remote subrack is not configured to lockout or forced switch mode. 4) Check that the extension cable is connected properly in the remote subrack (if extended mode is used).

Link Group #1 N+1 Protection Fault: Locked by User

Lockout or Force Switch to Protecting Link Group maintenance command activated.

Release maintenance command.

-

This alarm occurs when the connection between the NMS and the network element is lost.

-

-

This alarm occurs when the user fails to log in to the NMS system correctly several times consecutively.

-

81

81

81

81

Corrective Actions

401

402

FibeAir® Troubleshooting Guide

33

Trap ID

Description

Probable Cause

Corrective Actions

-

This alarm occurs when a secondary standby HighCapRadioNMS server tries to connect to a standalone HighCapRadioNMS server.

-

This alarm occurs for a primary HighCapRadioNMS server when its connection to the standby HighCapRadioNMS server is lost.

-

-

This alarm occurs for the HighCapRadioNMS server when the license is set to expire in less than two weeks.

Contact customer support to obtain a license file for the server.

-

This alarm occurs for the HighCapRadioNMS server when the license expires.

Contact customer support to obtain a license file for the server.

-

This alarm occurs for the HighCapRadioNMS server when the number of network elements exceeds the license limit.

Remove some of the elements, or Contact customer support to obtain a license file for the updated number of elements.

-

This alarm occurs for the HighCapRadioNMS server when it fails to load the license file.

The license file is probably corrupted. Contact customer support to obtain a new license file.

-

This alarm occurs when HighCapRadioNMS attempts to start the TFTP, but the TFTP port (69) is already bound by another process.

Check your system, and disable other TFTP servers.

-

This alarm occurs when a user is disconnected by another user.

403

404

405

406

407

408

409

410

FibeAir® Troubleshooting Guide

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

-

34

Trap ID

Description

Probable Cause

Corrective Actions

-

This alarm occurs when a secondary standby HighCapRadioNMS server tries to connect to a main HighCapRadioNMS server,with a different software version.

Re-install one of the servers, so that the same HighCapRadioNMS software version will be on both servers.

-

The enabled feature set is not licensed.

Disable the feature or contact Support to get an appropriate license.

411

414

FibeAir® Troubleshooting Guide

35

Fault Isolation using Loopbacks The loopback function provides a means of testing the link at various points. During the procedure, the external equipment sends a data pattern and monitors its receipt. If the received pattern is identical to the sent pattern, the connection between the equipment and the loop is confirmed. 101101110

Equipment

101101110

Radio Link

Loopback FibeAir is capable of performing loopback testing at several points in the link. The test is run from the CeraView management software, or via the SNMP protocol. During the loopback test, an alarm indication will appear to remind you to cancel the test when you are done. The following loopback tests can be performed from the window: Local: y

155 Mbps Line Interface

y

Wayside Channel Local IDU 101101110...

Equipment 101101110...

Local IDU Interfaces

Modem & IF

to ODU

Local Loop y

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

FibeAir® Troubleshooting Guide

36

Remote: y

155 Mbps Line Interface

y

Wayside Channel Local IDU 101101110...

Local IDU Interfaces

Equipment 101101110...

Modem & IF

Remote Loop Full Radio Link Loopback (local external equipment through the radio link, to the remote line interface module, back through the radio link, to the local external equipment). Local Terminal

Remote Terminal

101101110...

Equipment 101101110...

Local IDU

Local ODU

Remote IDU

Modem & IF

Line Interface

155 MB/s Line Interface Loopback Loop

Remote Terminal Loop

Connection Fault Guide Problems that occur when trying to connect to the FibeAir system using CeraView, may be due to incorrect cable configuration. If there is a connection problem in the system, CeraView will start, but an hour glass will appear when the software is loading to indicate that a problem exists. The following steps will help you identify and correct such problems. Check the Cables Refer to the figure below for the following procedures. 1.

For Ethernet connection between FibeAir and a PC network card, use a cross cable. For Ethernet connection between FibeAir and an Ethernet hub (for example, connecting to a LAN jack in a wall) use a straight cable.

2.

For serial connection between FibeAir and a PC serial port, use a straight cable.

FibeAir® Troubleshooting Guide

37

For serial connection using a dial-up modem, use a cross cable.

Cable Connections Check Read and Write Communities Ping FibeAir. If ping succeeds, the problem may be with the CeraView software installation, or the computer TCP\IP stack. Check the read and write communities in FibeAir and in the management station configuration. If ping fails, there may be a network connectivity problem. A typical conflict may occur between the IDU configuration and the related CeraView parameter. In addition, the Agent Address must be identical to the IDU IP address, and the source address must be identical to the computer’s address. The following figure shows a typical example of IP addresses and network configuration.

Typical Network Configuration

FibeAir® Troubleshooting Guide

38

Check the Serial Connection If the connection is via serial line, check the serial line speed in FibeAir, and in the Management station configuration. In the terminal, the serial line speed is specified using the IP Configuration menu. Check the Ethernet Connection Verify that the Management station and FibeAir IP interfaces have the same net ID. If they should not be included in the same network, check the default router address. After performing the verifications above, if there is still a problem with network connectivity, together with the system administrator check for firewalls and routing configuration errors.

FibeAir® Troubleshooting Guide

39