Ceragon Alarms

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: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email: info@ceragon.com 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: infous@ceragon.com
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: infoeuro@ceragon.com 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
IDU alarm LEDs Coax cable connection Coax cable All equipment Receive level (voltage in IDU/ODU/RFU, or using management) Torque on antenna mount bolts
Check for ...

All green Tight, no corrosion or moisture No cracks or kinks Dust or dirt Per installation records Tight mount
Comments
If not, perform troubleshooting Clean/repair as required Replace as required Clean as required Align/adjust as required
Adjust as required
FibeAir Troubleshooting Guide
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 y y y y y y y Power supplies Fading (due to heavy rain, new obstacle in path, antenna misalignment) External equipment (SONET/SDH, ATM, FastEthernet, etc.) Indoor Unit (IDU) Outdoor Unit (ODU)or Radio Frequency Unit (RFU) RF cable between the ODU/RFU and IDU Exposure of equipment to severe conditions (high temperature, etc.) 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 Red X X X X X X Yello w Green X X X X Description
PWR (Power) LINE LOF (Loss of Frame) BER (Bit Error Ratio)
Red - power supply problem Red - no input to main channel / high BER Yellow - JO mismatch Red - radio did not recognize information frame (radio link problem/radio LOF) 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) Red - loopback is active Yellow - Protected configuration. The unit is currently passive or Tx mute is operating Red - modem unlocked Yellow - high temperature / fan problem Red - no link, or ODU power, or ODU/RFU unlocked Yellow - radio interference, or high temperature, or Rx/Tx out of range Red - RF cable open / RF cable short Red - no link / remote unit problem (red LED is lit in the remote unit) Yellow - warning in remote unit (yellow LED is lit in the remote unit)
LPBK (Loopback) STBY (Standby) IDU ODU
X X
X X
X X
X X
X X
CBL (Cable) RMT (Remote Unit)
X X X
X X
LED Indications for Hitless Systems For Hitless systems, the following table lists the LEDs and their indications: LOF (LED Panel) - LOF LED Color Yellow Red Alarm Explanation Local unit receives LOF from a receive path currently not in use. Local unit receives LOF from a receive path currently in use.
LOF (Interface Panel) - ALRM LED Color OFF Red Green Alarm Explanation Hitless mode is disabled. Local unit receives LOF from the mate unit. Hitless switching can be performed, if necessary.
Local Receiver (Interface Panel) - Rx ACTV LED Color OFF Green Alarm Explanation Local receiver not in use. 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 y y y External equipment Tx is connected to FibeAir Rx. External equipment Rx is connected to FibeAir Tx. Both external equipment and FibeAir are using the same interface (single mode, multi-mode). 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 Insufficient system configuration for full XPIC Support 0 Probable Cause One of the system elements does not support XPIC. Or, the system is missing one of the needed elements. Corrective Actions 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. 1) Reset IDU. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDU. 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.) 1) Reduce TX power gradually. 2) Replace ODU.
10
ODU 5/8/12/-12V Power Supply Failure
One of the system elements does not support XPIC. Or, the system is missing one of the needed elements. One of the ODU synthisizers is unlocked.
Synthesizer #1/2/3 Unlocked 11
12
Tx Level Out of Range
The ODU cannot transmit the requested Tx power.
Trap ID
Description Tx Mute On/Off
Probable Cause ODU muted by user
Corrective Actions 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. 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. 1) Check installation conditions. 2) Replace ODU. 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. 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. 1) Verify correct cable connection. Recommended connection is V to Right drawer and H to Left drawer
12
Rx Level Out of Range 13
RSL is very low (typically below -80 dBm), link is down.
14
ODU Temperature Out of Range Power Input #2 is Down
ODU temperature too high/low. Subrack redundant power feed failure.
15
Power Input #1 is Down
Subrack redundant power feed failure.
15
XPIC Cable Swap
15
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. Failure in an IDU power supply.
15
IDU 5/8/3.3/-5V Power Supply Failure
1) Check -48 VDC supply to IDU. 2) Replace IDU
Trap ID 15 15
Description Drawer Power On/Off Drawer Internal Power Failure (Board #1) Drawer Internal Power Failure (Board #2)
Probable Cause Drawer power on/off. Drawer Internal Power Failure (Board #1) Board #1 - MUX card. Board #2 - Modem card. This alarm may also be generated if a drawer in Internal Protection was switched off. Problem with extension cable or the connection between the two subracks.
Corrective Actions -
1) Switch off/on IDM. 2) Replace IDM
15
Extension Link Communication Failure
16
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. 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. 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. 1) Download the Modem script to the IDC and reset the IDM.
Cable Open/Short 16
IDU-ODU cable open/short.
Cable Open 16
IDM-ODU cable open
MRMC=<value> Script File is Missing 17
Multi-Rate MultiConstellation configuration script for the specified capacity/modulation is missing in the IDC. Drawer hardware intact ok / failure (Mux)
17
Drawer Internal Hardware Intact/Failure Board#1 IDU Temperature Out of Range
1) In case of failure, replace IDM.
18
IDU Temperature Out of Range
1) Check installation conditions. 2) Replace IDM.
Trap ID 18 19
Description Fan Failure XC Internal Loopback on Line #5 XC Internal Loopback on Line #4 XC Internal Loopback on Line #3 XC Internal Loopback on Line #2 XC Internal Loopback on Line #1 Wayside Channel Loopback
Probable Cause Fan Failure XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback XC board Internal port loopback Wayside Line loopback applied by user in internal protection Wayside Left Line loopback applied by user ODU RF loopback applied by user Loopback applied by user
Corrective Actions 1) Replace fan. 1) Disable loopback
19
1) Disable loopback
19
1) Disable loopback
19
1) Disable loopback
19
1) Disable loopback
Disable Wayside line loopback
19
19
Wayside Channel Loopback ODU Internal Loopback (Not) Active 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 Internal Loopback on Fiber #n External Loopback on Fiber #n E1\T1 Internal Loopback on Port #n IDU Local Loopback (Not) Active
Disable Wayside line loopback
19
1) Disable loopback
1) Disable loopback
19
19
Internal loopback on Fiber
1) Disable loopback
19
IDU Line loopback applied by user IDU Line loopback applied by user IDU IF loopback applied by user
1) Disable loopback
19
1) Disable loopback
19
1) Disable loopback
Trap ID 19
Description E1\T1 External Loopback on Port #n Remote Communication Failure
Probable Cause E1/T1 External loopback
Corrective Actions 1) Disable loopback
20
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. Disable PRBS test.
21
PRBS Test is Running on Radio Link Group #1 N+1 Protection Fault: Locked by User
PRBS test started.
21
Lockout or Force Switch to Protecting Link Group maintenance command activated. Trib RS: LOF Radio RS: LOF (ADM)
Release maintenance command.
22
Trib RS: LOF Radio RS: LOF
22
1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs. 1) Check Protecting Radio module is powered on and operates properly. 2) Replace faulty module. 3) see Radio RS: LOF (SDH) 1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM.
22
Link Group #1 N+1 Protection Fault: Protecting Radio Failure
N+1 Link Group protection degraded due to Loss Of Frame or Loss Of Signal alarm on the radio port detected by XC board. Loss Of Frame alarm on the radio, link is down
Radio RS: LOF (SDH) Radio Section: LOF (Sonet) 22
Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet) 22
Loss Of Frame alarm on the line input.
Trap ID
Description Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet)
Probable Cause Loss Of Frame alarm on the line input
Corrective Actions 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU. 1) Check 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
22
Fiber RS: LOF
Fiber RS: LOF (ADM)
22
23
Trib RS: LOS Loss of Signal on Fiber #n
Trib RS: LOS 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. 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU. 1) Check line input. 2) Check fiber. 3) Verify end equipment transmits properly. 4) Replace IDM. 1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDM. 1) Check line input. 2) Check cable. 3) Verify end equipment transmits properly. 4) Replace IDU.
23
23
Fiber RS: LOS or?10;E1\T1\E3\DS3 #n Loss of Signal?10;Fiber RS: LOS
Loss Of Signal alarm on the line input
23
Gigabit Ethernet Loss of Signal
Fast Ethernet Loss of Carrier on Port #n 23
Fast Ethernet Loss of Carrier
Fast Eth. #01/02 Loss of Carrier 23
Fast Ethernet Loss of Carrier
10
Trap ID
Description E1\T1 Loss of Signal on Port #n
Probable Cause E1\T1 Loss of Signal
Corrective Actions 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. -
23
24 24 24 24 24 24 24 24 24 24 24 25 25 25 25 25
Trib RS: TIM Trib LP #n: TIM Trib HP: TIM Trace Identifier Mismatch on Fiber #n Radio LP #n: TIM Radio HP: TIM Fiber RS: TIM Fiber RS: TIM Fiber RS: TIM Fiber LP #n: TIM Fiber HP: TIM Trib RS: Excessive BER Trib MS: Excessive BER Trib LP #n Excessive BER Trib HP: Excessive BER Radio RS: Excessive BER Radio RS: Excessive BER Radio RS: Excessive BER
Trib RS: TIM Trib LP #n: TIM Trib HP: TIM Trace Identifier Mismatch alarm (J0 mismatch). Radio LP: TIM Radio HP: TIM Fiber RS: TIM Fiber RS: TIM Fiber RS: TIM Fiber LP #n: TIM Fiber HP: TIM Trib RS: Excessive BER Trib MS: Excessive BER Trib LP #n Excessive BER
Trib HP: Excessive BER Radio RS: Excessive BER (Regenerator) Radio RS: Excessive BER (Regenerator) Radio RS: Excessive BER (ADM)
25
25
11
Trap ID 25
Description Radio MS: Excessive BER Radio LP #n: Excessive BER Radio HP: Excessive BER Excessive BER on Radio #n
Probable Cause Radio MS: Excessive BER
25
Radio LP: Excessive BER
25
Radio HP: Excessive BER
Major radio Excessive BER alarm
25
1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM. 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. -
Excessive BER on Fiber #n 25
Major line Excessive BER alarm
E1\T1 Excessive BER on Port #n 25
Major Excessive BER alarm on E1/T1 port
25
Fiber RS: Excessive BER Fiber RS: Excessive BER Fiber RS: Excessive BER Fiber MS: Excessive BER Fiber LP #n Excessive BER Fiber HP: Excessive BER
Fiber RS: Excessive BER (Regenerator) Fiber RS: Excessive BER (Regenerator) Fiber RS: Excessive BER (ADM) Fiber MS: Excessive BER
25
25
25
25
Fiber LP #n Excessive BER
25
Fiber HP: Excessive BER
12
Trap ID 25
Description E1\T1\E3\DS3 #n Excessive BER E1\T1\E3\DS3 #n Excessive BER Trib RS: Signal Degrade Trib MS: Signal Degrade Trib LP #n Signal Degrade Trib HP: Signal Degrade Radio RS: Signal Degrade Radio RS: Signal Degrade Radio RS: Signal Degrade Radio LP #n: Signal Degrade Radio MS: Signal Degrade Radio HP: Signal Degrade Signal Degrade on Radio #n
Probable Cause E3DS3 Excessive BER
25 26 26
E1/T1 Excessive BER
Trib RS: Signal Degrade Trib MS: Signal Degrade
26 26 26
Trib LP #n Signal Degrade
Trib HP: Signal Degrade Radio RS: Signal Degrade
26
Radio RS: Signal Degrade
26
Radio RS: Signal Degrade
26
Radio LP #n: Signal Degrade Radio HP: Unequipped
26
26
Radio HP: Signal Degrade
Minor radio BER alarm
26
1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM.
Signal Degrade on Fiber #n 26
Minor line SD BER alarm
13
Trap ID
Description Fiber RS: Signal Degrade
Probable Cause Minor line BER alarm
Corrective Actions 1) Check line input. 2) Check fibers/cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDU. 1) Check line input. 2) Check cables. 3) Verify end equipment transmits properly. 4) Use line loopbacks to confirm input/IDM is ok. 5) Replace IDM. -
26
E1\T1 Signal Degrade on Port #n 26
Minor BER alarm on E1/T1 port
26
Fiber RS: Signal Degrade Fiber RS: Signal Degrade Fiber MS: Signal Degrade Fiber LP #n Signal Degrade Fiber HP: Signal Degrade E1\T1\E3\DS3 #n Signal Degrade E1\T1\E3\DS3 #n Signal Degrade Trib MS: AIS Trib LP #n: AIS Trib HP: AIS Radio MS: AIS Radio LP #n: AIS Radio HP: AIS Fiber MS: AIS
Fiber RS: Signal Degrade (ADM) Fiber RS: Signal Degrade
26
26
Fiber MS: Signal Degrade
26
Fiber LP #n Signal Degrade
26
Fiber HP: Signal Degrade
26
E3DS3 Signal Degrade
26 27 27 27 27 27 27 27
E3DS3 Signal Degrade
Trib MS: AIS Trib LP #n: AIS Trib HP: AIS Radio MS: AIS Radio LP #n: AIS Radio HP: AIS Fiber MS: AIS
14
Trap ID 27 27
Description Fiber LP #n: AIS Fiber HP: AIS Fiber RS: Unexpected ?10;E1\T1\E3\DS3 #n Unexpected Signal Trib RS: Unexpected Signal Gigabit Ethernet Unexpected Signal
Fast Ethernet Unexpected Signal on Port #n
Probable Cause Fiber LP #n: AIS Fiber HP: AIS Unexpected signal on the line input. Port disabled but line is connected. Trib RS: Excessive BER
Corrective Actions 1) Enable line port or disconnect line
28
28
28
GbE port is disabled but GbE data is detected. Fast Ethernet Unexpected Signal on Port #n Trib LP #n: LOP Trib HP: LOP Radio LP: Loss of pointer (LOP) alarm occurs. Radio HP: Loss of pointer (LOP) alarm occurs. Fiber LP: Loss of pointer (LOP) alarm occurs. Fiber HP: Loss of pointer (LOP) alarm occurs. Trib MS: RDI Trib LP #n: RDI Trib HP: RDI Radio MS: Remote Defect Identifier signal (RDI) occurs. Radio LP: Remote Defect Identifier signal (RDI) occurs.
1) Enable GbE port, disable GbE port of source, or disconnect fiber. -
28 30 30 30
Trib LP #n: LOP Trib HP: LOP Radio LP #n: LOP
30
Radio HP: LOP
30
Fiber LP #n: LOP
30 31 31 31
Fiber HP: LOP
Trib MS: RDI Trib LP #n: RDI Trib HP: RDI Radio MS: RDI
31
Radio LP #n: RDI 31
15
Trap ID
Description Radio HP: RDI
Probable Cause Radio HP: Remote Defect Identifier signal (RDI) occurs. Fiber MS: Remote Defect Identifier signal (RDI) occurs. Fiber LP: Remote Defect Identifier signal (RDI) occurs. Fiber HP: Remote Defect Identifier signal (RDI) occurs. Trib LP #n: PLM Trib HP: PLM Radio LP: Payload Label Mismatch (PLM) occurs. Radio HP: Payload Label Mismatch (PLM) occurs. Fiber LP: Payload Label Mismatch (PLM) occurs. Fiber HP: Payload Label Mismatch (PLM) occurs. Trib LP #n: Unequipped Trib HP: Unequipped Radio LP: Unequipped
31
Fiber MS: RDI 31
Fiber LP #n: RDI 31
Fiber HP: RDI 31
32 32 32
Trib LP #n: PLM Trib HP: PLM Radio LP #n: PLM
32
Radio HP: PLM
32
Fiber LP #n: PLM
32 33 33 33 33 33 33
Fiber HP: PLM
Trib LP #n: Unequipped Trib HP: Unequipped Radio LP #n: Unequipped Radio HP: Unequipped Fiber LP #n: Unequipped Fiber HP: Unequipped External Alarm
Radio HP: Unequipped Fiber LP: Unequipped
Fiber HP: Unequipped External alarm input #1 configured and triggered by user.
34
16
Trap ID
Description External Alarm
Probable Cause External alarm input #2 configured and triggered by user. External alarm input #3 configured and triggered by user. External alarm input #4 configured and triggered by user. External alarm input #5 configured and triggered by user. External alarm input #6 configured and triggered by user. External alarm input #7 configured and triggered by user. External alarm input #8 configured and triggered by user. XO failure Mux board
35
External Alarm 36
External Alarm 37
External Alarm 38
External Alarm 39
External Alarm 40
External Alarm 41
42
General Hardware Fault #3
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download XC firmware file of the required type and reset the IDC. 1) Replace Subrack Auxiliary module. 1) Download Wayside firmware file to the IDC and reset the IDC.
42
XO failure Modem board
42
XC <Type> FPGA File is Missing
XC firmware file is missing in the 2-floor IDC.
42
General Hardware Fault #11 Wayside Firmware File is Missing
Wrong card type detected in Subrack Auxiliary slot. Wayside firmware file is missing in the IDC.
42
17
Trap ID
Description Auxiliary Card Fault #01
Probable Cause Subrack Auxiliary module failed or extracted.
Corrective Actions 1) Check Subrack Auxiliary module is properly inserted. 2) Replace Subrack Auxiliary module. 1) Download Subrack Auxiliary firmware file and reset the IDC.
42
42
Subrack Auxiliary FPGA File is Missing
Subrack Auxiliary firmware file is missing in the 2-floor IDC. Subrack Auxiliary EEPROM checksum failure.
42
1) Extract and re-insert Subrack Auxiliary module. 2) Replace Subrack Auxiliary module. -
42
Secondary Clock Source Failure Radio Card #n Powered Down
Secondary Clock Source Failure Radio module pertained to Link Protection group is powered down or extracted.
42
1) Check if Radio module is inserted properly in the subrack and is powered on. Replace module if faulty. -
42
Primary Clock Source Failure EOW chaining Loss of Signal
Primary Clock Source Failure No signal detected on Subrack Auxiliary EOW chaining input.
42
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. 1) Check if XC module is powered on and no other alarm pertained to XC is active. 2) Replace XC module.
42
Link Group #1 N+1 Protection Fault: Protecting Radio Failure XC Card Fault
N+1 Link Group protection degraded due to XC card fault.
18
Trap ID
Description Link Group #1 N+1 Protection Fault: XC Peer Communication Failure
Probable Cause N+1 Link Group protection degraded due to peer XC communication fault.
Corrective Actions 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). 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. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) Try SW Reset affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 3) Replace the module. 1) 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
Link Group #1 N+1 Protection Fault: LocalRemote Protection Mismatch
N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.
General Hardware Fault #9 42
Upper IDM Board (MUX or XC) EEPROM inventory information CRC error
Upper IDM Board (MUX or XC) EEPROM read access error
Lower IDM Board (Modem or XC) EEPROM inventory information CRC error
Lower IDM Board (Modem or XC) EEPROM read access error
Line Card #n Powered Down 42
Line module pertained to Link Protection group is powered down or extracted.
19
Trap ID
Description Line Card #1 Powered Down
Probable Cause Line module in carrrier #1 of the Link Protection group is powered down or extracted.
Corrective Actions 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. 1) Check that proper Subrack Auxiliary module inserted. 2) Extract and re-insert Subrack Auxiliary module. 3) Replace Subrack Auxiliary module. 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. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Power IDM off/on. 3) Replace IDM. 3) Replace IDC. 1) Disable loopback
42
Drawer Internal Power Failure (Board #2) 42
Internal Power failure.
XPIC Cable Swap
Internal IDC to IDC communication failure between modules requied for Link Group protection service.
42
42
IDU XPIC HW fault
IDU Synthesizer lock
42
Drawer Internal Loopback Copy IDC Configuration to Mate IDU-ODU Inner Communication Failure
IDU IF loop applied by user
42
IDC copy configuration by user in external protection IDC cannot communicate with ODC card.
42
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.
20
Trap ID
Description IDU-MUX Inner Communication Failure
Probable Cause IDC cannot communicate with MUX card, MUX card upload failure.
Corrective Actions 1) Reset IDU. 2) Verify correct SW version. 3) Verify correct interfaces. 4) Replace IDU. 1) Download correct Subrack Auxiliary FW file to 2-floor IDC, and then extract and re-insert Subrack Auxiliary board 2) Replace Subrack Auxiliary module. 3) Replace 2-floor IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. 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. For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU
42
FPGA load failure - Subrack Auxiliary board.
42
FPGA load failure - Mux
42
FPGA load failure - Modem
Drawer-ODU Communication Failure
Drawer cannot communicate with ODC card.
42
42
DAC failure
1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. -
42 42
Clock Unit Unlocked Clock Unit Out of Range Copy Carrier Configuration To Mate Failed/Succedded MUX Firmware File is Missing
Clock Unit Unlocked Clock Unit Out of Range Carrier configuration copied between two IDMs in protected configuration A Mux FW file is missing from the system.
42
42
Load the required FW file, and reset system.
21
Trap ID 42
Description Modem Firmware File is Missing TFTP IDU/MUX/ODU verxxx Download Succeeded/ Canceled/Failed Boot/IDC/MUX/ODU/Mo dem Script/Modem/ Wayside/Mrmc table/RFU FPGA File Download Succeeded <file name> IDU Configuration Download Succeeded/Error/Cance lled/Failed/Invalid File ODU SW Upload Failed
Probable Cause A Modem FW file is missing from the system. Software download operation status (from user's PC to IDC)
Corrective Actions Load the required FW file, and reset system. -
43
File download status. Initiated by user.?9;
43
43
Configuration download status, initiated by user
44
Software upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) Software upload operation status (from IDC to ODC) MUX/ODU Internal Download Succeeded/Canceled/Failed /Error Firmware upload operation status (from IDC to ODC) Firmware upload operation status (from IDC to ODC) Firmware upload operation status (from IDC to ODC) WSC board configuration failure Error during reading board configuration CRC error
44
ODU SW Upload Error
44
ODU SW Upload Canceled MUX/ODU Internal Download Succeeded/Canceled/F ailed/Error RFU FW Upload Failed
44
44
44
RFU FW Upload Error
44
RFU FW Upload Canceled General Hardware Fault #2
46
1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.
22
Trap ID
Description General Hardware Fault #3
Probable Cause WSC board configuration failure Can't detect board configuration (can't read from E2PROM) Settings not supported by HW/SW. Mismatch in the internal protection configuration between the drawers.
Corrective Actions 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC.
46
46
General Cfg Mismatch
1) Check if HW and SW support the requested configuration 1) Check and compare configuration 2) See mate Configuration Mismatch Alarm 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. 1) Check and compare configuration 2) See mate Configuration Mismatch Alarm Set identical Link ID on both ends of the link. 1) Set identical Link ID on both ends of the link. 1) Set identical Link ID on both ends of the link. Reset IDM
46
Mate Configuration Mismatch (<param name>) M=xx, L=xx
46
User Configuration Mismatch (<param name>) S=xx, D=xx
Mismatch configuration between the IDC Database and the drawer.
46
Mate Configuration Mismatch (<param name>) M=xx, L=xx
Mismatch configuration between local IDC Database and mate IDC database
46 46
Link ID Mismatch Link ID Mismatch on Radio #n Link ID Mismatch
Link ID Mismatch Link ID is not identical on both ends of the link. Link ID is not identical on both ends of the link. Link ID is not identical on both ends of the link. Internal system mismatch regarding the state of the radio Mute/Unmute Incorrect Auxiliary channel configuration
46
46
Link ID Mismatch
Protection Mismatch 46
Auxiliary Channel User Configuration Mismatch 46
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
23
Trap ID
Description Device Incompatible Alarm (#103)
Probable Cause Incomapitibility alarm between link components. Typically refers to mixture of standard and "I" components in the link IDC MAC device failure loading with default MAC address FPGA load failure Wayside Channel
Corrective Actions 1) Check link components
46
46
1) Download correct SW/FW/Configuration scripts. 2) Replace IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDC. 1) Check link connections and settings. 2) Check XPIC configuration. 3) Verify that both links are up. 4) Check XPI
46
Drawer ID Mismatch 46
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) 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. Different configuration between the IDUs on the same side of the link Different configuration between the IDUs on both sides of the link Configuration in the IDC is different than the configuration in the drawers or in the Auxiliary channels board Configuration mismatch between two IDCs in External Protection configuration.
Drawer ID Mismatch in Protecting Carrier 46
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
1) Check and compare configurations
46
IDU Hitless Remote Config Mismatch
1) Check and compare configurations
46
User Configuration Mismatch (<param name>) S=xx, D=xx
1) Check and compare configuration 2) See User Configuration Mismatch Alarm
46
Mate Configuration Mismatch
1) Check and compare configuration. 2) Perform "copy to mate" from the IDC with the correct configuration
24
Trap ID
Description Mate Configuration Mismatch
Probable Cause Configuration mismatch between two drawers in External Protection configuration.
Corrective Actions 1) Check and compare configuration. 2) Perform "copy to mate" from the drawer with the correct configuration 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.
46
User Configuration Mismatch 46
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. 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.
User Configuration Mismatch
46
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. 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. 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.
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.
46
46
User Configuration Mismatch between IDC # and IDC #
At least one configuration parameter which should be equal in these two IDCs has different values.
25
Trap ID
Description Protection Internal/External Mate Not Exist Protection External Alarm Switch Hitless Protection Configuration Mismatch Protection Change to Standby
Probable Cause System configured for protection without mate connected Protection switch by external alarm Hitless is configred without protection Different faults indicate hardware failure on the drawer
Corrective Actions 1) Check configuration. 2) Check Mate connected
47
47
47
1) Enable protection or disable hitless 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Replace IDC. -
47
47
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 Protection Cable Disconnected Protection Cable Disconnect/Error/Power Error/Problem?10; Master-Slave Disconnect Protection Communication Error on Cable
48
Protection Cable Disconnected Problem with protection cable or the connection between the Master/Slave IDUs
1) Connect Protection Cable. 2) Replace cable. 1) Replace cable. 2) Replace IDUs
48
48
For External Protection configuration. Protection cable is connected but errors detected. Heart Beat (Trap Only) Trib HP: LOM Radio HP: Loss of Multiframe (LOM) alarm occurs.
1) Check that cable is connected properly. 2) Replace protection cable. 3) Replace IDCs
49 50 50
Heart Beat (Trap Only) Trib HP: LOM Radio HP: LOM
26
Trap ID 50
Description Fiber HP: LOM
Probable Cause Fiber HP: Loss of Multiframe (LOM) alarm occurs. Left/Right receiver is used for processing data
51
Hitless Left/Right Receiver in Use
Not a real alarm since receiver switching is likely to happen during multipath fading. 1) Disable Hitless Lockout
51
Hitless Switch Locked to Right Radio By User
Hitless switching disabled by user and locked for one of the drawers. Hitless switching disabled by user and locked for one of the drawers. Hitless Switch Locked to Self Radio by User Hitless Switch Locked to Mate/Self Radio by User
51
Hitless Switch Locked to Left Radio By User
1) Disable Hitless Lockout
51
Hitless Switch Locked to Self Radio By User Hitless Switch Locked to Mate/Self Radio By User Hitless Self/Mate Receiver in user Hitless Functionality Failure
51
51
Hitless Self/Mate Receiver in user Hitless protection is not available. The link will fail in case of fade.
51
1) Hitless cable disconnected. 2) Mate IDU is off. 3) Mate IDU has an alarm that prevents it from receiving data. 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 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
Loss of Frame on Unused Left/Right Radio 52
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.
Unused Radio Receiver LOF 52
Hitless Self Radio Receiver LOF
27
Trap ID
Description Own Radio BBLOF on Radio #n
Probable Cause Hitless Self Radio Receiver LOF
Corrective Actions 1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check link settings (TX power,TX freq). 3) Verify no interference. 4) Use loopbacks to identify problem source. 5) Replace IDMs/ODUs -
52
52
Hitless Self Radio Receiver LOF Hitless Cable Disconnect In-Band Radio PPP Link Disconnect?10;In-Band Line PPP Link Disconnect User Channel Ethernet Loss of Carrier
Hitless Self Radio Receiver LOF Hitless cable disconnected.
53
Connect hitless cable.
57
In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected. User Right Channel Loss of Carrier
1) Check the line connection. 2) Check in-band configuration.
58
1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 1) Check line input. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.
User Channel Ethernet Loss of Carrier 58
User Left Channel Loss of Carrier
User Channel Ethernet Loss of Carrier 58
User Channel Loss of Carrier in internal protection
28
Trap ID
Description Wayside Channel Loss of Signal/Carrier
Probable Cause Wayside Channel Loss of Signal/Carrier in internal protection
Corrective Actions 1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 1) Check line input. 2) Verify user-end equipment. 3) Check / replace connecting cable. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 1) Check cable. 2) Replace cable. 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.
58
Wayside Channel Loss of Signal/Carrier 58
Wayside Right Channel Loss of Signal/Carrier
Wayside Channel Loss of Signal/Carrier 58
Wayside Left Channel Loss of Signal/Carrier
59
ODU-2-ODU Cable Open No Signal from ODU
ODU-2-ODU Cable Open
No Rx (140 MHz) signal from ODU
60
60
Modem Script Not Supported Protection Force Switch
Modem Script Not Supported One of the system elements does not support XPIC. Or, the system is missing one of the needed elements.
1) Disable "Force Switch"
61
29
Trap ID
Description Protection Lockout
Probable Cause "Protection Lockout" command executed. Will lock the switching operation until removed. RFU Power Supply Failure (Vd)
Corrective Actions 1) Disable Lockout
61
RFU Power Failure (Vd) 62
1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Reset IDM. 2) Check IF cable and connectors. 3) Replace ODU. 4) Replace IDM. 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU. 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4) Check antenna connections 5) Replace local/remote ODU. 1) Check installation conditions. 2) Replace RFU
62
RFU Power Failure (6v pro)
RFU Power Supply Failure (6v pro)
62
RFU Power Failure (6v pro)
RFU Power Supply Failure (6v pro)
62
RFU Power Failure (12v)
RFU Power Supply Failure (12v)
62
RFU Power Failure (1.5v)
RFU Power Failure (1.5v)
RFU Rx Level Path1 Out Of Range 63
RSL of Main channel is very low (typically below -80 dBm).
RFU Rx Level Path2 Out Of Range 63
RSL of Diversity channel is very low (typically below -80 dBm).
64
RFU Extreme Temperature
RFU temperature is too high/low.
30
Trap ID
Description RFU Rx Level Path2 Out Of Range
Probable Cause RSL of Diversity channel is very low (typically below 80dBm).
Corrective Actions 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Check link settings (TX power,TX freq). 3) Check anttena alignment. 4)Check antenna connections 5)Replace local/remote ODU. 1) Check 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 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 1) Check RFU IF cable connection 2) Reconnect the IF cable 3) Replace RFU 1) Reconnect XPIC clock cables at both RFUs 2) Replace XPIC cable 1) Check link performance 2) Re-perform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU 1) Check link performance 2) Reperform delay calibration 3) Re-perform delay calibration in RF loopback 4) Reset the RFU 5) Replace RFU 1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM.
65
RFU Fan Failure 65
Fan Failure was detected by RFU
RFU Fan Failure 65
Fan Failure was detected by RFU
66
RFU Low Signal To ODU
RFU is detecting low signal from IDU
RFU XPIC Clock Failure 67
No XPIC clock is received from Master RFU
RFU Delay Calibration Failure 1 68
Delay calibration is unseccessfull since RX AGC is unlocked.
RFU Delay Calibration Failure 2 69
Delay calibration is unseccessfull since wide or deep notch has been detected at the RX signal
70
Gigabit Ethernet SFP Not Intact
SFP is not connected properly.
31
Trap ID
Description Gigabit Ethernet SFP TX Fault
Probable Cause SFP does not transmit Ethernet properly.
Corrective Actions 1) Reconnect SFP. 2) Replace SFP. 3) Replace IDM. 1) Check the reason for the alarm (see the Probable Cause column) and correct it accordingly.
70
Gigabit Ethernet TX Mute Override
70
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) HW encryption fault Encryption loss of frame
71 72
Encryption Fault Encryption Sync Loss
1) Reset IDM. 1) Check link staus. 2) Reset IDM. 1) Check link status. 2) Reset IDC. 3) Reset IDM. 1)Check link status.
Initial KEP Failed 73
The first encryption key exchange failed
74
Session Key Timer Elapsed Power-Up Test Failed
No session key exchange in the allowed time One of the built-in encryption system tests failed One of the Conditional tests failed Encryption mode changed by user, will take effect after next power up. Administrator password is the default value N+1 Link Group protection degraded due to XC card fault.
75
1) Reset IDC. 2) Reset IDM.
76
Conditional Test Failed
1) Reset IDC. 2) Reset IDM. -
77
Encryption Will Turned Off On Next Reset
80
Admin password in default state Link Group #1 N+1 Protection Fault: XC Card is Down
Change administrator password.
81
1) Check if XC module is inserted and powered on and no other alarm pertained to XC is active. 2) Replace XC module.
32
Trap ID
Description Link Group #1 N+1 Protection Fault: XC Peer Communication Failure
Probable Cause N+1 Link Group protection degraded due to peer XC communication fault.
Corrective Actions 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). 1) Check Protecting Radio module is powered on and operates properly. Replace faulty module. 2) see Radio RS: LOF (SDH)
81
81
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. N+1 Link Group protection degraded due to LocalRemote Protection Mismatch.
Link Group #1 N+1 Protection Fault: LocalRemote Group Topology Mismatch
81
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). Release maintenance command.
81
Link Group #1 N+1 Protection Fault: Locked by User
Lockout or Force Switch to Protecting Link Group maintenance command activated. 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.
401
402
33
Trap ID
Description -
Probable Cause 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. This alarm occurs for the HighCapRadioNMS server when the license expires. This alarm occurs for the HighCapRadioNMS server when the number of network elements exceeds the license limit. This alarm occurs for the HighCapRadioNMS server when it fails to load the license file. This alarm occurs when HighCapRadioNMS attempts to start the TFTP, but the TFTP port (69) is already bound by another process. This alarm occurs when a user is disconnected by another user.
Corrective Actions Open the main server configuration, and in the Redundancy section, change the server roll from Stand Alone to Main Server.
403
404
405
Contact customer support to obtain a license file for the server.
406
Contact customer support to obtain a license file for the server.
407
Remove some of the elements, or Contact customer support to obtain a license file for the updated number of elements.
408
The license file is probably corrupted. Contact customer support to obtain a new license file.
409
Check your system, and disable other TFTP servers.
410
34
Trap ID
Description -
Probable Cause This alarm occurs when a secondary standby HighCapRadioNMS server tries to connect to a main HighCapRadioNMS server,with a different software version. The enabled feature set is not licensed.
Corrective Actions Re-install one of the servers, so that the same HighCapRadioNMS software version will be on both servers.
411
414
Disable the feature or contact Support to get an appropriate license.
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 y 155 Mbps Line Interface 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).
36
Remote: y y 155 Mbps Line Interface Wayside Channel

Local IDU
101101110...
Equipment
101101110...
Local IDU Interfaces
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
101101110...
Remote Terminal
Remote IDU Modem & IF Line Interface
Equipment
101101110...
Local IDU
Local ODU
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.
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 computers address. The following figure shows a typical example of IP addresses and network configuration.
Typical Network Configuration
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.
39

Ceragon Alarms

Cargado por

Información del documento

Descripción original:

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Ceragon Alarms

Cargado por

Copyright:

Formatos disponibles

FibeAir

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

Check for ...

FibeAir Troubleshooting Guide

Step 1: Define the Symptom

Step 2: Isolate the Problem

Step 3: Understand the Problem

Step 4: Solve the Problem

FibeAir Troubleshooting Guide

IDU LED Indicators

Color LED Red X X X X X X Yello w Green X X X X Description

LPBK (Loopback) STBY (Standby) IDU ODU

CBL (Cable) RMT (Remote Unit)

FibeAir Troubleshooting Guide

FibeAir Troubleshooting Guide

Alarm List Table

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

Synthesizer #1/2/3 Unlocked 11

Tx Level Out of Range

The ODU cannot transmit the requested Tx power.

FibeAir Troubleshooting Guide

Description Tx Mute On/Off

Probable Cause ODU muted by user

Rx Level Out of Range 13

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

ODU Temperature Out of Range Power Input #2 is Down

ODU temperature too high/low. Subrack redundant power feed failure.

Power Input #1 is Down

Subrack redundant power feed failure.

XPIC Cable Swap

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

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

FibeAir Troubleshooting Guide

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

Extension Link Communication Failure

IDU-ODU cable open/short.

IDM-ODU cable open

MRMC=<value> Script File is Missing 17

Drawer Internal Hardware Intact/Failure Board#1 IDU Temperature Out of Range

1) In case of failure, replace IDM.

IDU Temperature Out of Range

1) Check installation conditions. 2) Replace IDM.

FibeAir Troubleshooting Guide

Corrective Actions 1) Replace fan. 1) Disable loopback

Disable Wayside line loopback

Disable Wayside line loopback

Internal loopback on Fiber

FibeAir Troubleshooting Guide

Description E1\T1 External Loopback on Port #n Remote Communication Failure

Probable Cause E1/T1 External loopback

Corrective Actions 1) Disable loopback

No communication between the IDUs over the link.

PRBS test started.

Release maintenance command.

Trib RS: LOF Radio RS: LOF

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

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

Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet) 22

Loss Of Frame alarm on the line input.

FibeAir Troubleshooting Guide

Description Fiber RS: LOF (SDH) Fiber Section: LOF (Sonet)

Probable Cause Loss Of Frame alarm on the line input

Fiber RS: LOF