TSguide 11 06 PDF

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 users authority to operate the equipment and the warranty for such equipment.
Copyright 2006 by Ceragon Networks Ltd. All rights reserved.
Corporate Headquarters: European Headquarters:

Ceragon Networks Ltd. Ceragon Networks (UK) Ltd.
24 Raoul Wallenberg St. 4 Oak Tree Park, Burnt Meadow Road
Tel Aviv 69719, Israel North Moons Moat, Redditch,
Tel: 972-3-645-5733 Worcestershire B98 9NZ, UK
Fax: 972-3-645-5499 Tel: 44-(0)-1527-591900
Email: info@ceragon.com Fax: 44-(0)-1527-591903
www.ceragon.com Email: infoeuro@ceragon.com
North American Headquarters: APAC Headquarters
Ceragon Networks Inc. Ceragon Networks (HK) Ltd.
10 Forest Avenue, Singapore RO
Paramus, NJ 07652, USA Level 34 Centennial Tower
Tel: 1-201-845-6955 3 Temasek Avenue
Toll Free: 1-877-FIBEAIR Singapore 039190
Fax: 1-201-845-5665 Tel - + 65 6549 7886
Email: infous@ceragon.com 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 Clean/repair as required

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

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

mount bolts
FibeAir Troubleshooting Guide 1

Troubleshooting Guide
The Process
Corrective maintenance consists of the steps described in the following sections. The steps provide a logical,
sequential method for diagnosing and resolving system problems.
Step 1: Define the Symptom
This step is generally peformed by the customer's field technician or supervisor. Examples of symptoms
include IDU alarm is red, complete loss of service, and excessive errors.
Symptoms may be constant or intermittent. Constant symptoms require immediate troubleshooting attention.
Intermittent symptoms may require circuit monitoring or robust test procedures prior to troubleshooting.
Step 2: Isolate the Problem
After you have a clear definition of the symptom, the malfunction can be isolated using diagnostics, loopback
testing, fault isolation tables/flow charts, test equipment, and manual procedures.
This step will identify the specific piece of equipment that is failing.
Although it may be difficult at times to immediately determine which part of a radio link is causing the fault,
the initial suspicion should be focused on one of the following near-end or far-end issues:
y Power supplies
y Fading (due to heavy rain, new obstacle in path, antenna misalignment)
y External equipment (SONET/SDH, ATM, 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.

IDU LED Indicators
The following table lists the LEDs on the IDU panel and their functions.
Color
LED Description
Red Yello Green
w
PWR X X Red - power supply problem

(Power)
LINE X X X Red - no input to main channel / high BER
Yellow - JO mismatch
LOF (Loss X X Red - radio did not recognize information
of Frame) frame (radio link problem/radio LOF)
BER (Bit X X X Red - radio BER higher than radio
Error Ratio) excessive error threshold definition (see
Sonet/SDH configuration window)
Yellow - radio BER higher than radio
signal degrade threshold definition (see
Sonet/SDH configuration window)
LPBK X X Red - loopback is active
(Loopback)
STBY X X Yellow - Protected configuration. The unit
(Standby) is currently passive or Tx mute is
operating
IDU X X X Red - modem unlocked
Yellow - high temperature / fan problem
ODU X X X Red - no link, or ODU power, or ODU/RFU
unlocked
Yellow - radio interference, or high
temperature, or Rx/Tx out of range
CBL (Cable) X X Red - RF cable open / RF cable short
RMT X X X Red - no link / remote unit problem (red
(Remote LED is lit in the remote unit)
Unit)
Yellow - warning in remote unit (yellow
LED is lit in the remote unit)

LED Indications for Hitless Systems
For Hitless systems, the following table lists the LEDs and their indications:
LOF (LED Panel) - LOF
LED Color Alarm Explanation
Yellow Local unit receives LOF from a receive path

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

currently in use.
LOF (Interface Panel) - ALRM
OFF Hitless mode is disabled.
Red Local unit receives LOF from the mate unit.
Green Hitless switching can be performed, if necessary.
Local Receiver (Interface Panel) - Rx ACTV
OFF Local receiver not in use.
Green Local receiver in use.

Alarm List Table
The table below lists trap IDs, trap descriptions, probable causes, and corrective actions.
A note about interface troubleshooting:
If, after the radio link is installed, the payload is not received, there may be a problem either with the line
interface connection to FibeAir, or with external equipment.
Before you perform line interface troubleshooting, check the following items, which are common causes of
line interface failures:
y External equipment Tx is connected to FibeAir Rx.
y External equipment Rx is connected to FibeAir Tx.
y Both external equipment and FibeAir are using the same interface (single mode, multi-mode).
y For multi-mode interfaces, check that you are using multi-mode fibers to connect the unit. For single
mode interfaces, check that you are using single mode fibers.
If no problem is detected with any of the items above, proceed with the table below.
Alarm List with Corrective Actions
Trap ID Description Probable Cause Corrective Actions
Insufficient system One of the system elements 1) Verify the existence of all IDMs
configuration for full does not support XPIC. and ODU, and verify their
XPIC Support Or, the system is missing connectivity.
one of the needed elements. 2) Open the unit Alarm Log (using
0
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 One of the system elements 1) Reset IDU.

Supply Failure does not support XPIC. 2) Check IF cable and connectors.
10
Or, the system is missing 3) Replace ODU.
one of the needed elements. 4) Replace IDU.
Synthesizer #1/2/3 One of the ODU synthisizers Replace ODU. (In XPIC
Unlocked is unlocked. configuration, the ODU may be
taking the sync from the mate
11
ODU. In that case, check if alarm
persists in non-XPIC
configuration.)
Tx Level Out of Range The ODU cannot transmit 1) Reduce TX power gradually.
12
the requested Tx power. 2) Replace ODU.

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
12
subrack.
3) Disable Power Input if you do
not use redundant power feed.
Rx Level Out of Range RSL is very low (typically 1) Check that the fault is not due to
below -80 dBm), link is rain/multipath fading or lack of
down. LOS.
13 2) Check link settings (TX
power,TX freq).
3) Check anttena alignment.
4) Replace local/remote ODU.
ODU Temperature Out ODU temperature too 1) Check installation conditions.

14
of Range high/low. 2) Replace ODU.
Power Input #2 is Down Subrack redundant power 1) Verify if the Power Input card
feed failure. exists in the subrack.
2) Check if Power Input connected
to -48 VDC supply.
15
subrack.
4) Replace Power Input card if
problem still exists.
Power Input #1 is Down Subrack redundant power 1) Verify if the Power Input card
feed failure. exists in the subrack.
2) Check if Power Input connected
to -48 VDC supply.
15
subrack.
4) Replace Power Input card if
problem still exists.
XPIC Cable Swap Left/Right cables swap in 1) Verify correct cable connection.
XPIC configuration. If
Drawer ID Mismatch (see Recommended connection is V to
above) alarm is identified in Right drawer and H to Left drawer
15
both drawers, the IF (coax)
cables between the drawers
and ODUs on one end are
swapped.
IDU 5/8/3.3/-5V Power Failure in an IDU power 1) Check -48 VDC supply to IDU.
15
Supply Failure supply. 2) Replace IDU

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

15
Failure (Board #1) Failure (Board #1)
Drawer Internal Power Board #1 - MUX card. 1) Switch off/on IDM.

Failure (Board #2) Board #2 - Modem card. 2) Replace IDM
This alarm may also be
15
generated if a drawer in
Internal Protection was
switched off.
Extension Link Problem with extension 1) If extended mode is not in use,

Communication Failure cable or the connection configure all IDCs in the subrack
between the two subracks. as "1 subrack out of 1".
2) If extended mode is in use,
verify that the other subrack is
configured to extension mode
16 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,
16
replace ODU).
3) Replace IDU.
4) Replace ODU.
Cable Open IDM-ODU cable open 1) Check IF cable and connectors

16
replace ODU).
3) Replace IDM.
4) Replace ODU.
MRMC=<value> Script Multi-Rate Multi- 1) Download the Modem script to

File is Missing Constellation configuration the IDC and reset the IDM.
17 script for the specified
capacity/modulation is
missing in the IDC.
Drawer Internal Drawer hardware intact ok / 1) In case of failure, replace IDM.

17 Hardware Intact/Failure failure (Mux)
Board#1
IDU Temperature Out of IDU Temperature Out of 1) Check installation conditions.

18
Range Range 2) Replace IDM.

18 Fan Failure Fan Failure 1) Replace fan.
XC Internal Loopback XC board Internal port 1) Disable loopback

19
on Line #5 loopback

19
on Line #4 loopback

19
on Line #3 loopback

19
on Line #2 loopback

19
on Line #1 loopback
Wayside Channel Wayside Line loopback Disable Wayside line loopback

19 Loopback applied by user in internal
protection
Wayside Channel Wayside Left Line loopback Disable Wayside line loopback
19
Loopback applied by user
ODU Internal Loopback ODU RF loopback applied 1) Disable loopback

19
(Not) Active by user
IDU Remote Loopback Loopback applied by user 1) Disable loopback

(Not) Active ?10;IDU
Line Loopback (Not)
Active?10;E1\T1\E3\DS
19 3 #n Internal Loopback
(Not)
Active?10;E1\T1\E3\DS
3 #n External Loopback
(Not) Active
Internal Loopback on Internal loopback on Fiber 1) Disable loopback

19
Fiber #n
External Loopback on IDU Line loopback applied 1) Disable loopback

19
Fiber #n by user
E1\T1 Internal Loopback IDU Line loopback applied 1) Disable loopback

19
on Port #n by user
IDU Local Loopback IDU IF loopback applied by 1) Disable loopback

19
(Not) Active user

E1\T1 External E1/T1 External loopback 1) Disable loopback

19
Loopback on Port #n
Remote Communication No communication between 1) Verify link is up and no errors

Failure the IDUs over the link. over the link.
20
2) Check in-band management
configuration.
PRBS Test is Running PRBS test started. Disable PRBS test.

21
on Radio
Link Group #1 N+1 Lockout or Force Switch to Release maintenance command.

Protection Fault: Locked Protecting Link Group
21
by User maintenance command
activated.
22 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).
22
3) Verify no interference.
4) Use loopbacks to identify
problem source.
5) Replace IDMs.
Link Group #1 N+1 N+1 Link Group protection 1) Check Protecting Radio module
Protection Fault: degraded due to Loss Of is powered on and operates
22 Protecting Radio Failure Frame or Loss Of Signal properly.
alarm on the radio port 2) Replace faulty module.
detected by XC board. 3) see Radio RS: LOF (SDH)
Radio RS: LOF (SDH) Loss Of Frame alarm on the 1) Check that the fault is not due to
Radio Section: LOF radio, link is down other alarms that can lead to LOF.
(Sonet) 2) Check link settings (TX
power,TX freq).
22
problem source.
5) Replace IDMs/ODUs
Fiber RS: LOF (SDH) Loss Of Frame alarm on the 1) Check line input.
Fiber Section: LOF line input. 2) Check fibers/cables.
(Sonet) 3) Verify end equipment transmits
22 properly.
4) Use line loopbacks to confirm
input/IDU is ok.
5) Replace IDM.

Fiber RS: LOF (SDH) Loss Of Frame alarm on the 1) Check line input.
Fiber Section: LOF line input 2) Check fibers/cables.
(Sonet) 3) Verify end equipment transmits
22 properly.
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.
power,TX freq).
22
problem source.
5) Replace IDMs
23 Trib RS: LOS Trib RS: LOS
Loss of Signal on Loss Of Signal alarm on the 1) Check line input.

Fiber #n line input 2) Check fibers/cables.
3) Verify that end equipment
23 transmits properly.
that input/IDU is ok.
5) Replace IDM.
Fiber RS: LOS Loss Of Signal alarm on the 1) Check line input.
or?10;E1\T1\E3\DS3 #n line input 2) Check fibers/cables.
Loss of Signal?10;Fiber 3) Verify end equipment transmits
23 RS: LOS properly.
input/IDU is ok.
5) Replace IDU.
- Gigabit Ethernet Loss of 1) Check line input.

Signal 2) Check fiber.
23 3) Verify end equipment transmits
properly.
4) Replace IDM.
Fast Ethernet Loss of Fast Ethernet Loss of 1) Check line input.

Carrier on Port #n Carrier 2) Check cable.
properly.
4) Replace IDM.
Fast Eth. #01/02 Loss of Fast Ethernet Loss of 1) Check line input.
Carrier Carrier 2) Check cable.
properly.
4) Replace IDU.

E1\T1 Loss of Signal on E1\T1 Loss of Signal 1) Check line input.

Port #n 2) Check fibers/cables.
3) Verify end equipment transmits
23 properly.
input/IDU is ok.
5) Replace IDM.
24 Trib RS: TIM Trib RS: TIM -
24 Trib LP #n: TIM Trib LP #n: TIM -
24 Trib HP: TIM Trib HP: TIM -
Trace Identifier Trace Identifier Mismatch Verify J0 settings in the IDU and in
24
Mismatch on Fiber #n alarm (J0 mismatch). the end equipment.
24 Radio LP #n: TIM Radio LP: TIM -
24 Radio HP: TIM Radio HP: TIM -
24 Fiber RS: TIM Fiber RS: TIM -
24 Fiber LP #n: TIM Fiber LP #n: TIM -
24 Fiber HP: TIM Fiber HP: TIM -
25 Trib RS: Excessive BER Trib RS: Excessive BER -
25 Trib MS: Excessive BER Trib MS: Excessive BER -
Trib LP #n Excessive Trib LP #n Excessive BER -

25
BER
25 Trib HP: Excessive BER Trib HP: Excessive BER -
Radio RS: Excessive Radio RS: Excessive BER -

25
BER (Regenerator)

25
BER (Regenerator)

25
BER (ADM)

Radio MS: Excessive Radio MS: Excessive BER -

25
BER
Radio LP #n: Excessive Radio LP: Excessive BER -

25
BER
Radio HP: Excessive Radio HP: Excessive BER -

25
BER
Excessive BER on Major radio Excessive BER 1) Check that the fault is not due to
Radio #n alarm other alarms that can lead to LOF.
power,TX freq).
25
problem source.
Excessive BER on Major line Excessive BER 1) Check line input.

Fiber #n alarm 2) Check fibers/cables.
25 properly.
input/IDU is ok.
5) Replace IDM.
E1\T1 Excessive BER Major Excessive BER alarm 1) Check line input.
on Port #n on E1/T1 port 2) Check cables.
25 properly.
input/IDM is ok.
5) Replace IDM.
Fiber RS: Excessive Fiber RS: Excessive BER -

25
BER (Regenerator)

25
BER (Regenerator)

25
BER (ADM)
Fiber MS: Excessive Fiber MS: Excessive BER -

25
BER
Fiber LP #n Excessive Fiber LP #n Excessive BER -

25
BER
Fiber HP: Excessive Fiber HP: Excessive BER -

25
BER

E1\T1\E3\DS3 #n E3DS3 Excessive BER -

25
Excessive BER
E1\T1\E3\DS3 #n E1/T1 Excessive BER -

25
Excessive BER
26 Trib RS: Signal Degrade Trib RS: Signal Degrade -
Trib MS: Signal Trib MS: Signal Degrade -

26
Degrade
Trib LP #n Signal Trib LP #n Signal Degrade -

26
Degrade
26 Trib HP: Signal Degrade Trib HP: Signal Degrade -
Radio RS: Signal Radio RS: Signal Degrade -

26
Degrade

26
Degrade

26
Degrade
Radio LP #n: Signal Radio LP #n: Signal -

26
Degrade Degrade
Radio MS: Signal Radio HP: Unequipped -

26
Degrade
Radio HP: Signal Radio HP: Signal Degrade -

26
Degrade
Signal Degrade on Minor radio BER alarm 1) Check that the fault is not due to
Radio #n other alarms that can lead to LOF.
power,TX freq).
26
problem source.
Signal Degrade on Fiber Minor line SD BER alarm 1) Check line input.
#n 2) Check fibers/cables.
26 properly.
that input/IDU is ok.
5) Replace IDM.

Fiber RS: Signal Minor line BER alarm 1) Check line input.
Degrade 2) Check fibers/cables.
26 properly.
input/IDU is ok.
5) Replace IDU.
E1\T1 Signal Degrade Minor BER alarm on E1/T1 1) Check line input.
on Port #n port 2) Check cables.
26 properly.
input/IDM is ok.
5) Replace IDM.
Fiber RS: Signal Fiber RS: Signal Degrade -

26
Degrade (ADM)
Fiber RS: Signal Fiber RS: Signal Degrade -

26
Degrade
Fiber MS: Signal Fiber MS: Signal Degrade -

26
Degrade
Fiber LP #n Signal Fiber LP #n Signal Degrade -

26
Degrade
Fiber HP: Signal Fiber HP: Signal Degrade -

26
Degrade
E1\T1\E3\DS3 #n Signal E3DS3 Signal Degrade -

26
Degrade
E1\T1\E3\DS3 #n Signal E3DS3 Signal Degrade -

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

27 Fiber LP #n: AIS Fiber LP #n: AIS -
27 Fiber HP: AIS Fiber HP: AIS -
Fiber RS: Unexpected Unexpected signal on the 1) Enable line port or disconnect
28 ?10;E1\T1\E3\DS3 #n line input. Port disabled but line
Unexpected Signal line is connected.
Trib RS: Unexpected Trib RS: Excessive BER -

28
Signal
Gigabit Ethernet GbE port is disabled but 1) Enable GbE port, disable GbE
28
Unexpected Signal GbE data is detected. port of source, or disconnect fiber.
Fast Ethernet Unexpected Fast Ethernet Unexpected -

28 Signal on Port #n 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 -

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

30
(LOP) alarm occurs.
Fiber LP #n: LOP Fiber LP: Loss of pointer -

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

30
(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 -

31 Identifier signal (RDI)
occurs.
Radio LP #n: RDI Radio LP: Remote Defect -

occurs.

Radio HP: RDI Radio HP: Remote Defect -

occurs.
Fiber MS: RDI Fiber MS: Remote Defect -

occurs.
Fiber LP #n: RDI Fiber LP: Remote Defect -

occurs.
Fiber HP: RDI Fiber HP: Remote Defect -

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 -

32
Mismatch (PLM) occurs.
Radio HP: PLM Radio HP: Payload Label -

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

32
Fiber HP: PLM Fiber HP: Payload Label -

32
33 Trib LP #n: Unequipped Trib LP #n: Unequipped -
33 Trib HP: Unequipped Trib HP: Unequipped -
Radio LP #n: Radio LP: Unequipped -

33
Unequipped
33 Radio HP: Unequipped Radio HP: Unequipped -
Fiber LP #n: Fiber LP: Unequipped -

33
Unequipped
33 Fiber HP: Unequipped Fiber HP: Unequipped -
External Alarm External alarm input #1 -

34 configured and triggered by
user.


user.

user.

user.

user.

user.

user.

user.
General Hardware Fault XO failure Mux board 1) Download correct

#3 SW/FW/Configuration scripts.
42
2) Replace IDM.
3) Replace IDC.
General Hardware Fault XO failure Modem board 1) Download correct

42
2) Replace IDM.
3) Replace IDC.
XC <Type> FPGA File XC firmware file is missing 1) Download XC firmware file of

42 is Missing in the 2-floor IDC. the required type and reset the
IDC.
General Hardware Fault Wrong card type detected in 1) Replace Subrack Auxiliary
42
#11 Subrack Auxiliary slot. module.
Wayside Firmware File Wayside firmware file is 1) Download Wayside firmware file
42
is Missing missing in the IDC. to the IDC and reset the IDC.

Auxiliary Card Fault #01 Subrack Auxiliary module 1) Check Subrack Auxiliary module
failed or extracted. is properly inserted.
42
2) Replace Subrack Auxiliary
module.
Subrack Auxiliary FPGA Subrack Auxiliary firmware 1) Download Subrack Auxiliary

42 File is Missing file is missing in the 2-floor firmware file and reset the IDC.
IDC.
General Hardware Fault Subrack Auxiliary EEPROM 1) Extract and re-insert Subrack
#10 checksum failure. Auxiliary module.
42
module.
Secondary Clock Secondary Clock Source -

42
Source Failure Failure
Radio Card #n Radio module pertained to 1) Check if Radio module is

Powered Down Link Protection group is inserted properly in the subrack
42
powered down or extracted. and is powered on. Replace
module if faulty.
Primary Clock Source Primary Clock Source -

42
Failure Failure
EOW chaining Loss of No signal detected on 1) Disable EOW chaining if not

Signal Subrack Auxiliary EOW required.
chaining input. 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
42 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 N+1 Link Group protection 1) Check if XC module is powered
Protection Fault: degraded due to XC card on and no other alarm pertained
42
Protecting Radio Failure fault. to XC is active.
XC Card Fault 2) Replace XC module.

Link Group #1 N+1 N+1 Link Group protection 1) Verify Protection Radio link is up
Protection Fault: XC degraded due to peer XC and, no errors over the link.
Peer Communication communication fault. 2) Check that remote IDU is
Failure properly configured for N+1 Link
Group protection.
42 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 N+1 Link Group protection 1) Check that remote IDU is
Protection Fault: Local- degraded due to Local- properly configured with N+1 Link
Remote Protection Remote Protection Group topology.
42
Mismatch Mismatch. 2) Check that remote IDU has all
relevant N+1 Link Group protection
line modules operational.
General Hardware Fault Upper IDM Board (MUX or 1) Try SW Reset affected module /
#9 XC) EEPROM inventory IDM.
42 information CRC error 2) Power cycle or re-insert affected
module / IDM.
3) Replace the module.
General Hardware Fault Upper IDM Board (MUX or 1) Try SW Reset affected module /
#8 XC) EEPROM read access IDM.
42 error 2) Power cycle or re-insert affected
module / IDM.
General Hardware Fault Lower IDM Board (Modem 1) Try SW Reset affected module /
#11 or XC) EEPROM inventory IDM.
42 information CRC error 2) Power cycle or re-insert affected
module / IDM.
General Hardware Fault Lower IDM Board (Modem 1) Try SW Reset affected module /
#10 or XC) EEPROM read IDM.
42 access error 2) Power cycle or re-insert affected
module / IDM.
Line Card #n Powered Line module pertained to 1) Check if the card is inserted
Down Link Protection group is properly in the subrack.
powered down or extracted. 2) Check if own or redundant
42
power supply / Radio module
(in drawer #1) is powered on.
Replace module if faulty.

Line Card #1 Powered Line module in carrrier #1 of 1) Check if the card is inserted
Down the Link Protection group is properly in the subrack.
powered down or extracted. 2) Check if own or redundant
42
power supply / Radio module is
powered on.
3) Replace module if faulty.
Drawer Internal Power Internal Power failure. 1) Check that proper Subrack
Failure (Board #2) Auxiliary module inserted.
2) Extract and re-insert Subrack
42
Auxiliary module.
module.
XPIC Cable Swap Internal IDC to IDC 1) Check that IDC #n is power up
communication failure and finished initialization.
between modules requied 2) Check & configure both IDCs
for Link Group protection with proper system configuration:
service. System Type, Subrack#, Subrack
42 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 IDU XPIC HW fault 1) Download correct

42
2) Replace IDM.
3) Replace IDC.
General Hardware Fault IDU Synthesizer lock 1) Download correct

42 2) Power IDM off/on.
3) Replace IDM.
3) Replace IDC.
Drawer Internal IDU IF loop applied by user 1) Disable loopback

42
Loopback
Copy IDC Configuration IDC copy configuration by -

42
to Mate user in external protection
IDU-ODU Inner IDC cannot communicate 1) Check ODU connection to the

Communication Failure with ODC card. IDU.
2) Check IF cable and connectors.
42
replace ODU).
4) Replace ODU.
5) Replace IDU.

IDU-MUX Inner IDC cannot communicate 1) Reset IDU.

Communication Failure with MUX card, MUX card 2) Verify correct SW version.
42
upload failure. 3) Verify correct interfaces.
4) Replace IDU.
General Hardware Fault FPGA load failure - Subrack 1) Download correct Subrack
#7 Auxiliary board. Auxiliary FW file to 2-floor IDC, and
then extract and re-insert Subrack
42 Auxiliary board
module.
3) Replace 2-floor IDC.
General Hardware Fault FPGA load failure - Mux 1) Download correct

42
2) Replace IDM.
3) Replace IDC.
General Hardware Fault FPGA load failure - Modem 1) Download correct

42
2) Replace IDM.
3) Replace IDC.
Drawer-ODU Drawer cannot 1) Check ODU connection to IDM.

Communication Failure communicate with ODC 2) Check IF cable and connectors.
card. 3) Check ODU's N-type connector
replace ODU).
42 4) Replace ODU.
5) Replace IDM.
For High Power RF Unit:
1) Check BMA connector on OCB
2) Check BMA connector on RFU
General Hardware Fault DAC failure 1) Download correct

42
2) Replace IDM.
3) Replace IDC.
42 Clock Unit Unlocked Clock Unit Unlocked -
42 Clock Unit Out of Range Clock Unit Out of Range -
Copy Carrier Carrier configuration copied -

42 Configuration To Mate between two IDMs in
Failed/Succedded protected configuration
MUX Firmware File is A Mux FW file is missing Load the required FW file, and
42
Missing from the system. reset system.

Modem Firmware File is A Modem FW file is missing Load the required FW file, and
42
Missing from the system. reset system.
TFTP IDU/MUX/ODU Software download -

verxxx Download operation status (from user's
43
Succeeded/ PC to IDC)
Canceled/Failed
Boot/IDC/MUX/ODU/Mo File download status. -

dem Script/Modem/ Initiated by user.?9;
Wayside/Mrmc
43
table/RFU FPGA File
Download Succeeded
<file name>
IDU Configuration Configuration download -

Download status, initiated by user
43
Succeeded/Error/Cance
lled/Failed/Invalid File
ODU SW Upload Failed Software upload operation -

44
status (from IDC to ODC)
ODU SW Upload Error Software upload operation -

44
ODU SW Upload Software upload operation -

44
Canceled status (from IDC to ODC)
MUX/ODU Internal MUX/ODU Internal -

Download Download
44
Succeeded/Canceled/F Succeeded/Canceled/Failed
ailed/Error /Error
RFU FW Upload Failed Firmware upload operation -

44
RFU FW Upload Error Firmware upload operation -

44
RFU FW Upload Firmware upload operation -

44
Canceled status (from IDC to ODC)
General Hardware Fault WSC board configuration 1) Download correct

#2 failure Error during SW/FW/Configuration scripts.
46
reading board configuration 2) Replace IDC.
CRC error

General Hardware Fault WSC board configuration 1) Download correct

#3 failure Can't detect board SW/FW/Configuration scripts.
46
configuration (can't read 2) Replace IDC.
from E2PROM)
General Cfg Mismatch Settings not supported by 1) Check if HW and SW support

46
HW/SW. the requested configuration
Mate Configuration Mismatch in the internal 1) Check and compare

Mismatch (<param protection configuration configuration
46
name>) M=xx, L=xx between the drawers. 2) See mate Configuration
Mismatch Alarm
User Configuration Mismatch configuration 1) Check the mismatch

Mismatch (<param between the IDC Database configuration in the alarms log.
name>) S=xx, D=xx and the drawer. 2) Use "Copy to IDC" command to
46
copy the configuration
from XC to IDC, or "Copy to
Drawer" for mismatch resolution.
Mate Configuration Mismatch configuration 1) Check and compare

Mismatch (<param between local IDC Database configuration
46
name>) M=xx, L=xx and mate IDC database 2) See mate Configuration
Mismatch Alarm
46 Link ID Mismatch Link ID Mismatch -
Link ID Mismatch on Link ID is not identical on Set identical Link ID on both ends
46
Radio #n both ends of the link. of the link.
Link ID Mismatch Link ID is not identical on 1) Set identical Link ID on both

46
both ends of the link. ends of the link.
Link ID Mismatch Link ID is not identical on 1) Set identical Link ID on both

46
both ends of the link. ends of the link.
Protection Mismatch Internal system mismatch Reset IDM

46 regarding the state of the
radio Mute/Unmute
Auxiliary Channel User Incorrect Auxiliary channel 1) Check and correct configuration:
Configuration Mismatch configuration Use "Copy IDC to AUX" to copy
the Auxiliary channel configuration
46
to the IDC, or "Copy AUX to IDC"
to copy the Auxiliary channel
configuration to the AUX

Device Incompatible Incomapitibility alarm 1) Check link components

Alarm (#103) between link components.
46 Typically refers to mixture of
standard and "I"
components in the link
General Hardware Fault IDC MAC device failure 1) Download correct

46 #4 loading with default MAC SW/FW/Configuration scripts.
address 2) Replace IDC.
General Hardware Fault FPGA load failure 1) Download correct

46 #1 Wayside Channel SW/FW/Configuration scripts.
2) Replace IDC.
Drawer ID Mismatch Drawer receives signal of 1) Check link connections and

the other drawer across the settings.
XPIC link. Indicates problem 2) Check XPIC configuration.
46 in the XPIC link (such as 3) Verify that both links are up.
failure in one of the 4) Check XPI
transmitters or insufficient
XPI)
Drawer ID Mismatch in Drawer #1 receives signal of 1) Check link connections and

Protecting Carrier the mate drawer (#2) across settings.
the XPIC link. Indicates 2) Check XPIC configuration.
problem in the XPIC link 3) Verify that both links are up.
46
(such as failure in one of the 4) Check XPI
transmitters or insufficient
XPI), detected by the XC
board.
IDU Hitless Mate Config Different configuration 1) Check and compare

46 Mismatch between the IDUs on the configurations
same side of the link
IDU Hitless Remote Different configuration 1) Check and compare

46 Config Mismatch between the IDUs on both configurations
sides of the link
User Configuration Configuration in the IDC is 1) Check and compare

Mismatch (<param different than the configuration
46 name>) S=xx, D=xx configuration in the drawers 2) See User Configuration
or in the Auxiliary channels Mismatch Alarm
board
Mate Configuration Configuration mismatch 1) Check and compare

Mismatch between two IDCs in configuration.
46
External Protection 2) Perform "copy to mate" from the
configuration. IDC with the correct configuration

Mate Configuration Configuration mismatch 1) Check and compare

Mismatch between two drawers in configuration.
46 External Protection 2) Perform "copy to mate" from the
configuration. drawer with the correct
configuration
User Configuration At least one Link Group 1) Check the mismatch

Mismatch configuration parameter in configuration in the alarms log.
the IDC Database is 2) Use "Copy to IDC" command to
46 different than the actual copy the configuration
configuration in the XC. from XC to IDC, or "Copy to
Raised only after IDC Drawer" for mismatch resolution.
hotswap or S/W reset.
User Configuration At least one IDC 1) Check the mismatch

the IDC Data Base (XPIC 2) Use "Copy drawer to IDC"
for example) is different than command to copy the
the configuration in the XPIC/protection configuration from
drawers or in the Auxiliary the drawer to the IDC (without
channels. reset). The process will eliminate
46
Raised only after IDC the mismatch. The IDC parameters
hotswap / software reset. (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 At least one drawer 1) Check the mismatch

the IDC Database is 2) Use "Copy to IDC" command to
different than the actual copy the configuration from the
configuration in the drawers. drawer to the IDC, or "Copy to
Raised only after IDC Drawer", eliminating the mismatch.
hotswap or S/W reset. However, "copy to drawer"
command does not copy the
46
protection or XPIC properties (thay
are IDC parameters). IDC
parameters (IP addresses, in-
band) 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 At least one configuration 1) Check the mismatch

Mismatch between IDC parameter which should be configuration in the alarms log.
# and IDC # equal in these two IDCs has 2) Configure the relevant IDC with
46
different values. the correct values for mismatch
resolution, and wait one minute for
the mismatch alarm to clear.

Protection System configured for 1) Check configuration.

47 Internal/External Mate protection without mate 2) Check Mate connected
Not Exist connected
Protection External Protection switch by -

47
Alarm Switch external alarm
Hitless Protection Hitless is configred without 1) Enable protection or disable

47
Configuration Mismatch protection hitless
Protection Change to Different faults indicate 1) Download correct

Standby hardware failure on the SW/FW/Configuration scripts.
47
drawer 2) Replace IDM.
3) Replace IDC.
Change Remote Command was sent to -

Transmitter Request remote end to switch when
Sent - SDBER / EXBER both local receivers identify
47
/ LOF / BER Rx fault (for example,
remote active transmitter
fails)
SW Mode Changed to Change Master/Slave -

Slave/Master?10; command
47 Change Remote
Transmitter Request
Sent
Protection Cable Protection Cable 1) Connect Protection Cable.

48
Disconnected Disconnected 2) Replace cable.
Protection Cable Problem with protection 1) Replace cable.

Disconnect/Error/Power cable or the connection 2) Replace IDUs
48 Error/Problem?10; between the Master/Slave
Master-Slave IDUs
Disconnect
Protection For External Protection 1) Check that cable is connected

Communication Error on configuration. properly.
48 Cable Protection cable is 2) Replace protection cable.
connected but errors 3) Replace IDCs
detected.
49 Heart Beat (Trap Only) Heart Beat (Trap Only) -
50 Trib HP: LOM Trib HP: LOM -
Radio HP: LOM Radio HP: Loss of Multi- -

50
frame (LOM) alarm occurs.

Fiber HP: LOM Fiber HP: Loss of Multi- -

50
frame (LOM) alarm occurs.
Hitless Left/Right Left/Right receiver is used Not a real alarm since receiver
51 Receiver in Use for processing data switching is likely to happen during
multipath fading.
Hitless Switch Locked to Hitless switching disabled 1) Disable Hitless Lockout

51 Right Radio By User by user and locked for one
of the drawers.
Hitless Switch Locked to Hitless switching disabled 1) Disable Hitless Lockout

51 Left Radio By User by user and locked for one
of the drawers.
Hitless Switch Locked to Hitless Switch Locked to -

51
Self Radio By User Self Radio by User
Hitless Switch Locked to Hitless Switch Locked to -

51 Mate/Self Radio By Mate/Self Radio by User
User
Hitless Self/Mate Hitless Self/Mate Receiver -

51
Receiver in user in user
Hitless Functionality Hitless protection is not 1) Hitless cable disconnected.

Failure available. The link will fail in 2) Mate IDU is off.
51
case of fade. 3) Mate IDU has an alarm that
prevents it from receiving data.
Loss of Frame on Permanent Radio LOF in Same as Radio LOF alarm:

Unused Left/Right Radio the receiver (raised after 10 1) Check that the fault is not due to
consecutive seconds of other alarms that can lead to LOF.
radio Loss Of Frame). 2) Check link settings (TX
52 Implies a permanent power,TX freq).
problem, unlike fading due 3) Verify no interference.
to multipath condition, which 4) Use loopbacks to identify
is intermittent in nature. problem source.
Unused Radio Receiver Hitless Self Radio Receiver 1) Check that the fault is not due to
LOF LOF other alarms that can lead to LOF.
power,TX freq).
52
problem source.

Own Radio BBLOF on Hitless Self Radio Receiver 1) Check that the fault is not due to
Radio #n LOF other alarms that can lead to LOF.
power,TX freq).
52
problem source.
Hitless Self Radio Hitless Self Radio Receiver -

52
Receiver LOF LOF
Hitless Cable Hitless cable disconnected. Connect hitless cable.

53
Disconnect
In-Band Radio PPP Link In-band connection over the 1) Check the line connection.
Disconnect?10;In-Band line (STM-1/OC-3 or 2) Check in-band configuration.
57
Line PPP Link PPPoE) or over the radio
Disconnect was disconnected.
User Channel Ethernet User Right Channel Loss of 1) Check line input.
Loss of Carrier Carrier 2) Verify user-end Ethernet
equipment.
3) Check / replace connecting
58 cable.
4) Replace IDC module.
In case of N+1 Trunk Radio:
module.
User Channel Ethernet User Left Channel Loss of 1) Check line input.
Loss of Carrier Carrier 2) Verify user-end Ethernet
equipment.
58 cable.
module.
User Channel Ethernet User Channel Loss of 1) Check line input.

Loss of Carrier Carrier in internal protection 2) Verify user-end Ethernet
equipment.
58 cable.
module.

Wayside Channel Loss Wayside Channel Loss of 1) Check line input.

of Signal/Carrier Signal/Carrier in internal 2) Verify user-end equipment.
protection 3) Check / replace connecting
cable.
58
module.
Wayside Channel Loss Wayside Right Channel 1) Check line input.

of Signal/Carrier Loss of Signal/Carrier 2) Verify user-end equipment.
cable.
58
module.
Wayside Channel Loss Wayside Left Channel Loss 1) Check line input.
of Signal/Carrier of Signal/Carrier 2) Verify user-end equipment.
cable.
58
module.
ODU-2-ODU Cable ODU-2-ODU Cable Open 1) Check cable.

59
Open 2) Replace cable.
No Signal from ODU No Rx (140 MHz) signal 1) Check IF cable and

from ODU connectors
2) Check that ODU's N-
type connector inner pin is
not spliced (if yes, replace
ODU).
60 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.
Modem Script Not Modem Script Not -

60
Supported Supported
Protection Force Switch One of the system elements 1) Disable "Force Switch"
does not support XPIC.
61
Or, the system is missing
one of the needed elements.

Protection Lockout "Protection Lockout" 1) Disable Lockout

command executed. Will
61
lock the switching operation
until removed.
RFU Power Failure (Vd) RFU Power Supply Failure 1) Reset IDM.
(Vd) 2) Check IF cable and connectors.
62
3) Replace ODU.
4) Replace IDM.
RFU Power Failure (6v RFU Power Supply Failure 1) Reset IDM.
pro) (6v pro) 2) Check IF cable and connectors.
62
3) Replace ODU.
4) Replace IDM.
RFU Power Failure (6v RFU Power Supply Failure 1) Reset IDM.
pro) (6v pro) 2) Check IF cable and connectors.
62
3) Replace ODU.
4) Replace IDM.
RFU Power Failure RFU Power Supply Failure 1) Reset IDM.

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

(1.5v) 2) Check IF cable and connectors.
62
3) Replace ODU.
4) Replace IDM.
RFU Rx Level Path1 RSL of Main channel is very 1) Check that the fault is not due to
Out Of Range low (typically below -80 rain/multipath fading or lack of
dBm). LOS.
63
power,TX freq).
4) Check antenna connections
RFU Rx Level Path2 RSL of Diversity channel is 1) Check that the fault is not due to
Out Of Range very low (typically below -80 rain/multipath fading or lack of
dBm). LOS.
63
power,TX freq).
4) Check antenna connections
RFU Extreme RFU temperature is too 1) Check installation conditions.

64
Temperature high/low. 2) Replace RFU

RFU Rx Level Path2 RSL of Diversity channel is 1) Check that the fault is not due to
Out Of Range very low (typically below - rain/multipath fading or lack of
80dBm). LOS.
65
power,TX freq).
4)Check antenna connections
5)Replace local/remote ODU.
RFU Fan Failure Fan Failure was detected by 1) Check RFU connection to BP
RFU 2) Check that fans are connected
to PS
65 3) Replace RFU BP cable
4) Replace specific fan or fans
drawer
5) Replace RFU
RFU Fan Failure Fan Failure was detected by 1) Check RFU connection to BP
RFU 2) Check that fans are connected
to PS
65 3) Replace RFU BP cable
4) Replace specific fan or fans
drawer
5) Replace RFU
RFU Low Signal To RFU is detecting low signal 1) Check RFU IF cable connection
66 ODU from IDU 2) Reconnect the IF cable
3) Replace RFU
RFU XPIC Clock Failure No XPIC clock is received 1) Reconnect XPIC clock cables at
67 from Master RFU both RFUs
2) Replace XPIC cable
RFU Delay Calibration Delay calibration is 1) Check link performance

Failure 1 unseccessfull since RX 2) Re-perform delay calibration
AGC is unlocked. 3) Re-perform delay calibration in
68
RF loopback
4) Reset the RFU
5) Replace RFU
RFU Delay Calibration Delay calibration is 1) Check link performance

Failure 2 unseccessfull since wide or 2) Reperform delay calibration
deep notch has been 3) Re-perform delay calibration in
69
detected at the RX signal RF loopback
4) Reset the RFU
5) Replace RFU
Gigabit Ethernet SFP SFP is not connected 1) Reconnect SFP.

70 Not Intact properly. 2) Replace SFP.
3) Replace IDM.

Gigabit Ethernet SFP SFP does not transmit 1) Reconnect SFP.

70 TX Fault Ethernet properly. 2) Replace SFP.
3) Replace IDM.
Gigabit Ethernet TX GbE port is enabled by the 1) Check the reason for the alarm
Mute Override user but the system (see the Probable Cause column)
overrides this and mutes the and correct it accordingly.
port.
This alarm may appear in
the following cases:
70
Radio LOF (local or remote),
Link ID mismatch (local or
remote), excessive BER
(local or remote), Signal
degrade (local or remote),
GbE LOS (remote)
71 Encryption Fault HW encryption fault 1) Reset IDM.
Encryption Sync Loss Encryption loss of frame 1) Check link staus.

72
2) Reset IDM.
Initial KEP Failed The first encryption key 1) Check link status.
73 exchange failed 2) Reset IDC.
3) Reset IDM.
Session Key Timer No session key exchange in 1)Check link status.

74
Elapsed the allowed time
Power-Up Test Failed One of the built-in 1) Reset IDC.

75 encryption system tests 2) Reset IDM.
failed
Conditional Test Failed One of the Conditional tests 1) Reset IDC.

76
failed 2) Reset IDM.
Encryption Will Turned Encryption mode changed -

77 Off On Next Reset by user, will take effect after
next power up.
Admin password in Administrator password is Change administrator password.

80
default state the default value
Link Group #1 N+1 N+1 Link Group protection 1) Check if XC module is inserted
Protection Fault: XC degraded due to XC card and powered on and no other
81
Card is Down fault. alarm pertained to XC is active.
2) Replace XC module.

Link Group #1 N+1 N+1 Link Group protection 1) Verify Protection Radio link is up
Protection Fault: XC degraded due to peer XC and, no errors over the link.
Peer Communication communication fault. 2) Check that remote IDU is
Failure properly configured for N+1 Link
Group protection.
81 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 N+1 Link Group protection 1) Check Protecting Radio module
Protection Fault: degraded due to Loss Of is powered on and operates
81 Protecting Radio Failure Frame or Loss Of Signal properly. Replace faulty module.
alarm on the radio port 2) see Radio RS: LOF (SDH)
detected by XC board.
Link Group #1 N+1 N+1 Link Group protection 1) Check that remote IDU is
Protection Fault: Local- degraded due to Local- properly configured with N+1 Link
Remote Group Remote Protection Group topology, and all protection
Topology Mismatch Mismatch. 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).
81 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 Lockout or Force Switch to Release maintenance command.

Protection Fault: Locked Protecting Link Group
81
by User maintenance command
activated.
- This alarm occurs when the -

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

user fails to log in to the
402
NMS system correctly
several times consecutively.

- This alarm occurs when a Open the main server

secondary standby configuration, and in the
HighCapRadioNMS server Redundancy section, change the
403
tries to connect to a stand- server roll from Stand Alone to
alone HighCapRadioNMS Main Server.
server.
- This alarm occurs for a -

primary HighCapRadioNMS
server when its connection
404
to the standby
HighCapRadioNMS server
is lost.
- This alarm occurs for the Contact customer support to obtain

HighCapRadioNMS server a license file for the server.
405 when the license is set to
expire in less than two
weeks.
- This alarm occurs for the Contact customer support to obtain

406 HighCapRadioNMS server a license file for the server.
when the license expires.
- This alarm occurs for the Remove some of the elements, or

HighCapRadioNMS server Contact customer support to obtain
407 when the number of network a license file for the updated
elements exceeds the number of elements.
license limit.
- This alarm occurs for the The license file is probably

HighCapRadioNMS server corrupted. Contact customer
408
when it fails to load the support to obtain a new license file.
license file.
- This alarm occurs when Check your system, and disable

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

410 user is disconnected by
another user.

- This alarm occurs when a Re-install one of the servers, so

secondary standby that the same HighCapRadioNMS
HighCapRadioNMS server software version will be on both
411 tries to connect to a main servers.
HighCapRadioNMS
server,with a different
software version.
- The enabled feature set is Disable the feature or contact

414 not licensed. Support to get an appropriate
license.

Fault Isolation using Loopbacks
The loopback function provides a means of testing the link at various points. During the procedure, the
external equipment sends a data pattern and monitors its receipt. If the received pattern is identical to the sent
pattern, the connection between the equipment and the loop is confirmed.
101101110
Equipment 101101110 Radio Link
Loopback
FibeAir is capable of performing loopback testing at several points in the link. The test is run from the
CeraView management software, or via the SNMP protocol.
During the loopback test, an alarm indication will appear to remind you to cancel the test when you are done.
The following loopback tests can be performed from the window:
Local:
y 155 Mbps Line Interface
y Wayside Channel
Local IDU
101101110...
Local IDU Modem & to ODU
Equipment IF
Interfaces
101101110...
Local Loop
y Full IDU (all three inputs through the IDU, modulator, and looped in the IF).

Remote:
y 155 Mbps Line Interface
y Wayside Channel
Local IDU
101101110...
Local IDU Modem &
Equipment IF
Interfaces
101101110...
Remote Loop
Full Radio Link Loopback (local external equipment through the radio link, to the remote line interface
module, back through the radio link, to the local external equipment).
Local Terminal Remote Terminal

101101110...
Modem
Local Local Remote Line
Equipment &
101101110... IDU ODU IDU Interface
IF
155 MB/s
Line Interface
Loopback
Loop
Remote Terminal Loop
Connection Fault Guide

Problems that occur when trying to connect to the FibeAir system using CeraView, may be due to incorrect
cable configuration. If there is a connection problem in the system, CeraView will start, but an hour glass will
appear when the software is loading to indicate that a problem exists.
The following steps will help you identify and correct such problems.
Check the Cables
Refer to the figure below for the following procedures.
1. For Ethernet connection between FibeAir and a PC network card, use a cross cable.
For Ethernet connection between FibeAir and an Ethernet hub (for example, connecting to a LAN jack in
a wall) use a straight cable.
2. For serial connection between FibeAir and a PC serial port, use a straight cable.

For serial connection using a dial-up modem, use a cross cable.
Cable Connections
Check Read and Write Communities
Ping FibeAir. If ping succeeds, the problem may be with the CeraView software installation, or the computer
TCP\IP stack. Check the read and write communities in FibeAir and in the management station configuration.
If ping fails, there may be a network connectivity problem.
A typical conflict may occur between the IDU configuration and the related CeraView parameter.
In addition, the Agent Address must be identical to the IDU IP address, and the source address must be
identical to the computers address.
The following figure shows a typical example of IP addresses and network configuration.
Typical Network Configuration

Check the Serial Connection
If the connection is via serial line, check the serial line speed in FibeAir, and in the Management station
configuration. In the terminal, the serial line speed is specified using the IP Configuration menu.
Check the Ethernet Connection

Verify that the Management station and FibeAir IP interfaces have the same net ID. If they should not be
included in the same network, check the default router address.
After performing the verifications above, if there is still a problem with network connectivity, together with
the system administrator check for firewalls and routing configuration errors.

TSguide 11 06 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TSguide 11 06 PDF

Uploaded by

Copyright:

Available Formats

FibeAir

Part ID: BM-0108-0

Corporate Headquarters: European Headquarters:

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

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

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

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

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

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

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

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

What to check Check for ... Comments

IDU alarm LEDs All green If not, perform troubleshooting

Coax cable connection Tight, no corrosion or Clean/repair as required

Coax cable No cracks or kinks Replace as required

All equipment Dust or dirt Clean as required

Receive level (voltage in Per installation Align/adjust as required

Torque on antenna Tight mount Adjust as required

FibeAir Troubleshooting Guide 1

Step 1: Define the Symptom

Step 2: Isolate the Problem

Step 3: Understand the Problem

Step 4: Solve the Problem

FibeAir Troubleshooting Guide 2

PWR X X Red - power supply problem

FibeAir Troubleshooting Guide 3

LOF (LED Panel) - LOF

LED Color Alarm Explanation

Yellow Local unit receives LOF from a receive path

Red Local unit receives LOF from a receive path

LOF (Interface Panel) - ALRM

LED Color Alarm Explanation

OFF Hitless mode is disabled.

Red Local unit receives LOF from the mate unit.

Green Hitless switching can be performed, if necessary.

Local Receiver (Interface Panel) - Rx ACTV

LED Color Alarm Explanation

OFF Local receiver not in use.

Green Local receiver in use.

FibeAir Troubleshooting Guide 4

A note about interface troubleshooting:

y External equipment Tx is connected to FibeAir Rx.

y External equipment Rx is connected to FibeAir Tx.

Alarm List with Corrective Actions

Trap ID Description Probable Cause Corrective Actions

ODU 5/8/12/-12V Power One of the system elements 1) Reset IDU.

FibeAir Troubleshooting Guide 5

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

ODU Temperature Out ODU temperature too 1) Check installation conditions.

FibeAir Troubleshooting Guide 6

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

Drawer Internal Power Drawer Internal Power -

Drawer Internal Power Board #1 - MUX card. 1) Switch off/on IDM.

Extension Link Problem with extension 1) If extended mode is not in use,

Cable Open/Short IDU-ODU cable open/short. 1) Check IF cable and connectors.

Cable Open IDM-ODU cable open 1) Check IF cable and connectors

MRMC=<value> Script Multi-Rate Multi- 1) Download the Modem script to

Drawer Internal Drawer hardware intact ok / 1) In case of failure, replace IDM.

IDU Temperature Out of IDU Temperature Out of 1) Check installation conditions.

FibeAir Troubleshooting Guide 7

18 Fan Failure Fan Failure 1) Replace fan.

XC Internal Loopback XC board Internal port 1) Disable loopback

XC Internal Loopback XC board Internal port 1) Disable loopback