FibeAir®Troubleshooting Guide Part ID: BM-0108-0 Doc ID: DOC-00015466 Rev a.00 November 2006 Notice This document contains information that is proprietary to Ceragon Networks Ltd. No part of this publication may be reproduced, modified, or distributed without prior written authorization of Ceragon Networks Ltd. This document is provided as is, without warranty of any kind. Registered TradeMarks Ceragon Networks® is a registered trademark of Ceragon Networks Ltd. FibeAir® is a registered trademark of Ceragon Networks Ltd. CeraView® is a registered trademark of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders. TradeMarks CeraMapTM, PolyViewTM, EncryptAirTM, ConfigAirTM, CeraMonTM, EtherAirTM, and MicroWave FiberTM, are trademarks of Ceragon Networks Ltd. Other names mentioned in this publication are owned by their respective holders. Statement of Conditions The information contained in this document is subject to change without notice. Ceragon Networks Ltd. shall not be liable for errors contained herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this document or equipment supplied with it. Information to User Any changes or modifications of equipment not expressly approved by the manufacturer could void the user’s authority to operate the equipment and the warranty for such equipment. Copyright © 2006 by Ceragon Networks Ltd. All rights reserved. Corporate Headquarters: Ceragon Networks Ltd. 24 Raoul Wallenberg St. Tel Aviv 69719, Israel Tel: 972-3-645-5733 Fax: 972-3-645-5499 Email:
[email protected] North American Headquarters: Ceragon Networks Inc. 10 Forest Avenue, Paramus, NJ 07652, USA Tel: 1-201-845-6955 Toll Free: 1-877-FIBEAIR Fax: 1-201-845-5665 Email:
[email protected] www.ceragon.com European Headquarters: Ceragon Networks (UK) Ltd. 4 Oak Tree Park, Burnt Meadow Road North Moons Moat, Redditch, Worcestershire B98 9NZ, UK Tel: 44-(0)-1527-591900 Fax: 44-(0)-1527-591903 Email:
[email protected] APAC Headquarters Ceragon Networks (HK) Ltd. Singapore RO Level 34 Centennial Tower 3 Temasek Avenue Singapore 039190 Tel - + 65 6549 7886 Fax: +65 6549 7011 Contents General .......................................................................................................... 1 Maintenance Policy ........................................................................................... 1 Visual Inspection............................................................................................... 1 Troubleshooting Guide ................................................................................ 2 The Process ....................................................................................................... 2 IDU LED Indicators............................................................................................ 3 Alarm List Table ............................................................................................ 5 Fault Isolation using Loopbacks ................................................................36 Connection Fault Guide ..............................................................................37 General Ceragon designed FibeAir to be highly reliable and relatively maintenance free. In the event of a system failure, the system will provide detailed indications to assist troubleshooting and fault isolation. This guide explains the alarm indications of the FibeAir system, and contains procedures for troubleshooting and fault isolation. Maintenance Policy To ensure simple and efficient system maintenance, the on-site technician will only replace IDU, ODU, or RFU modules, and not repair them. Under no circumstance will the technician be permitted to open the equipment in order to repair a module or circuit board. Opening equipment will terminate the Ceragon warranty. Maintenance procedures the technician can perform include visual inspection, cleaning, cable/connector repair, link alignment/adjustment, and retorquing antenna mount bolts. Visual Inspection The following table lists the suggested preventive maintenance procedures, which include visual inspection of the equipment and verification of operational parameters. It is recommended to perform the procedures as often as local environmental conditions require. It is recommended to notify the end customer prior to performing any preventive maintenance procedures that could affect service on the circuit. What to check 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 1 Use the tables provided in the following sections to understand the problem. the malfunction can be isolated using diagnostics. Intermittent symptoms may require circuit monitoring or robust test procedures prior to troubleshooting. “complete loss of service”.) 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. Step 1: Define the Symptom This step is generally peformed by the customer's field technician or supervisor. loopback testing. you will need to understand why the fault occurred and what is required to correct it. new obstacle in path. ATM. Although it may be difficult at times to immediately determine which part of a radio link is causing the fault. Step 4: Solve the Problem Use the troubleshooting information in this guide to help solve the problem. antenna misalignment) External equipment (SONET/SDH. test equipment. and manual procedures. FibeAir® Troubleshooting Guide 2 . fault isolation tables/flow charts. Constant symptoms require immediate troubleshooting attention. The steps provide a logical.) System configuration Step 3: Understand the Problem Once the fault has been isolated.Troubleshooting Guide The Process Corrective maintenance consists of the steps described in the following sections. Step 2: Isolate the Problem After you have a clear definition of the symptom. sequential method for diagnosing and resolving system problems. Examples of symptoms include “IDU alarm is red”. Symptoms may be constant or intermittent. 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. This step will identify the specific piece of equipment that is failing. and for suggestions of possible solutions. and “excessive errors”. FastEthernet. etc. etc. modem unlocked Yellow .Protected configuration.JO mismatch Red . or high temperature. or Rx/Tx out of range Red . or ODU power.no link / remote unit problem (red LED is lit in the remote unit) Yellow .radio did not recognize information frame (radio link problem/radio LOF) Red . 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 .radio BER higher than radio excessive error threshold definition (see Sonet/SDH configuration window) Yellow .radio interference.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 FibeAir® Troubleshooting Guide 3 .high temperature / fan problem Red . or ODU/RFU unlocked Yellow .no input to main channel / high BER Yellow .loopback is active Yellow .RF cable open / RF cable short Red .IDU LED Indicators The following table lists the LEDs on the IDU panel and their functions.radio BER higher than radio signal degrade threshold definition (see Sonet/SDH configuration window) Red . The unit is currently passive or Tx mute is operating Red .power supply problem Red .no link. FibeAir® Troubleshooting Guide 4 .LED Indications for Hitless Systems For Hitless systems. Local Receiver (Interface Panel) . LOF (Interface Panel) .LOF LED Color Yellow Red Alarm Explanation Local unit receives LOF from a receive path currently not in use.Rx ACTV LED Color OFF Green Alarm Explanation Local receiver not in use.ALRM LED Color OFF Red Green Alarm Explanation Hitless mode is disabled. Hitless switching can be performed. if necessary. the following table lists the LEDs and their indications: LOF (LED Panel) . Local unit receives LOF from a receive path currently in use. Local receiver in use. Local unit receives LOF from the mate unit. Corrective Actions 1) Verify the existence of all IDMs and ODU. probable causes. the payload is not received. the system is missing one of the needed elements. which are common causes of line interface failures: y y y y External equipment Tx is connected to FibeAir Rx. Synthesizer #1/2/3 Unlocked 11 12 Tx Level Out of Range The ODU cannot transmit the requested Tx power. and corrective actions. If no problem is detected with any of the items above. (In XPIC configuration. 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. For multi-mode interfaces. In that case. External equipment Rx is connected to FibeAir Tx. For single mode interfaces. A note about interface troubleshooting: If. Before you perform line interface troubleshooting. FibeAir® Troubleshooting Guide 5 . 2) Replace ODU. multi-mode). and verify their connectivity. proceed with the table below.Alarm List Table The table below lists trap IDs. check that you are using single mode fibers. or with external equipment. Or. Both external equipment and FibeAir are using the same interface (single mode. 1) Reset IDU. the system is missing one of the needed elements. after the radio link is installed. check that you are using multi-mode fibers to connect the unit. trap descriptions. 10 ODU 5/8/12/-12V Power Supply Failure One of the system elements does not support XPIC. there may be a problem either with the line interface connection to FibeAir. the ODU may be taking the sync from the mate ODU. check if alarm persists in non-XPIC configuration. check the following items.) 1) Reduce TX power gradually. 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. One of the ODU synthisizers is unlocked. 4) Replace IDU. 3) Replace ODU. 2) Check IF cable and connectors. Replace ODU. Or. 1) Verify if the Power Input card exists in the subrack. 4) Replace local/remote ODU. Subrack redundant power feed failure. 2) Check if Power Input connected to -48 VDC supply.TX freq). 2) Check link settings (TX power. 2) Replace IDU FibeAir® Troubleshooting Guide 6 . 1) Verify correct cable connection. 1) Check installation conditions. Failure in an IDU power supply. 2) Check -48 VDC supply to the subrack.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. 3) Check anttena alignment. 15 Power Input #1 is Down Subrack redundant power feed failure. 2) Replace ODU. 5) Disable Power Input if you do not use redundant power feed. 4) Replace Power Input card if problem still exists. 15 IDU 5/8/3. 3) Check -48 VDC supply to the subrack. 14 ODU Temperature Out of Range Power Input #2 is Down ODU temperature too high/low. If Drawer ID Mismatch (see above) alarm is identified in both drawers. 5) Disable Power Input if you do not use redundant power feed. link is down. the IF (coax) cables between the drawers and ODUs on one end are swapped. 3) Disable Power Input if you do not use redundant power feed. 2) Check if Power Input connected to -48 VDC supply. 3) Check -48 VDC supply to the subrack.3/-5V Power Supply Failure 1) Check -48 VDC supply to IDU. 4) Replace Power Input card if problem still exists. 1) Verify if the Power Input card exists in the subrack. 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 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). 15 XPIC Cable Swap 15 Left/Right cables swap in XPIC configuration. verify that the other subrack is configured to extension mode properly. 4) Replace ODU. 2) Replace IDM 15 Extension Link Communication Failure 16 1) If extended mode is not in use. FibeAir® Troubleshooting Guide 7 . This alarm may also be generated if a drawer in Internal Protection was switched off. 2) If extended mode is in use. 3) Check that the XC boards in both subracks are inserted properly and the extension cable is plugged in. configure all IDCs in the subrack as "1 subrack out of 1". 2) Check ODU's N-type connector inner pin is not spliced (if yes. 18 IDU Temperature Out of Range 1) Check installation conditions. Problem with extension cable or the connection between the two subracks.MUX card. replace ODU). Corrective Actions - 1) Switch off/on IDM. 4) Replace extension cable.Modem card. 2) Replace IDM. Cable Open/Short 16 IDU-ODU cable open/short. Board #2 . 4) Replace ODU. replace IDM. Drawer Internal Power Failure (Board #1) Board #1 . 3) Replace IDM. 3) Replace IDU. 1) Download the Modem script to the IDC and reset the IDM. 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.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. 1) Check IF cable and connectors 2) Check ODU's N-type connector inner pin is not spliced (if yes. replace ODU). 5) Replace XC boards. 1) Check IF cable and connectors. 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 FibeAir® Troubleshooting Guide 8 .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.IDU Line Loopback (Not) Active?10.E1\T1\E3\DS 3 #n Internal Loopback (Not) Active?10. 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. 2) Replace faulty module. 22 Trib RS: LOF Radio RS: LOF 22 1) Check that the fault is not due to other alarms that can lead to LOF. 4) Use loopbacks to identify problem source. 21 PRBS Test is Running on Radio Link Group #1 N+1 Protection Fault: Locked by User PRBS test started. 5) Replace IDMs/ODUs 1) Check line input. 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.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. 2) Check fibers/cables. 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. 3) Verify end equipment transmits properly. 3) Verify no interference. Trib RS: LOF Radio RS: LOF (ADM) Release maintenance command. 4) Use loopbacks to identify problem source. FibeAir® Troubleshooting Guide 9 . Disable PRBS test. 3) Verify no interference. 2) Check link settings (TX power. 5) Replace IDMs. 5) Replace IDM. 3) see Radio RS: LOF (SDH) 1) Check that the fault is not due to other alarms that can lead to LOF. 2) Check in-band management configuration.TX freq). 1) Verify link is up and no errors over the link. 4) Use line loopbacks to confirm input/IDU is ok. 2) Check link settings (TX power. 21 Lockout or Force Switch to Protecting Link Group maintenance command activated.TX freq). 1) Check Protecting Radio module is powered on and operates properly. 3) Verify end equipment transmits properly. 2) Check fibers/cables. 4) Use line loopbacks to confirm that input/IDU is ok. 2) Check cable. 4) Replace IDM. 4) Use line loopbacks to confirm input/IDU is ok. 4) Use loopbacks to identify problem source. #01/02 Loss of Carrier 23 Fast Ethernet Loss of Carrier FibeAir® Troubleshooting Guide 10 . 5) Replace IDU. 4) Replace IDU. 1) Check line input.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. 1) Check line input. 2) Check fiber. 4) Replace IDM.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 cable. 23 23 Fiber RS: LOS or?10. 3) Verify end equipment transmits properly. 3) Verify end equipment transmits properly. 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. 3) Verify that end equipment transmits properly. 3) Verify no interference. 3) Verify end equipment transmits properly. 2) Check fibers/cables. 5) Replace IDU. 1) Check line input.TX freq). 5) Replace IDM.E1\T1\E3\DS3 #n Loss of Signal?10. 2) Check fibers/cables. 1) Check that the fault is not due to other alarms that can lead to LOF. 4) Use line loopbacks to confirm input/IDU is ok. 1) Check line input. 2) Check link settings (TX power. 3) Verify end equipment transmits properly. - 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).Trap ID Description E1\T1 Loss of Signal on Port #n Probable Cause E1\T1 Loss of Signal Corrective Actions 1) Check line input. 3) Verify end equipment transmits properly. 2) Check fibers/cables. 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM. 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 - FibeAir® Troubleshooting Guide 11 . Verify J0 settings in the IDU and in the end equipment. 5) Replace IDM. 3) Verify no interference.TX freq). 3) Verify end equipment transmits properly.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 Corrective Actions - 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. 1) Check line input. 4) Use loopbacks to identify problem source. 4) Use line loopbacks to confirm input/IDU is ok. 2) Check cables. 3) Verify end equipment transmits properly. 5) Replace IDMs/ODUs 1) Check line input. 5) Replace IDM. 2) Check fibers/cables. 2) Check link settings (TX power. 4) Use line loopbacks to confirm input/IDM is ok. - 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 - FibeAir® Troubleshooting Guide 12 . 2) Check link settings (TX power. 5) Replace IDMs/ODUs 1) Check line input. Signal Degrade on Fiber #n 26 Minor line SD BER alarm FibeAir® Troubleshooting Guide 13 . 3) Verify end equipment transmits properly.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 Corrective Actions - 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. 3) Verify no interference. 4) Use loopbacks to identify problem source. 4) Use line loopbacks to confirm that input/IDU is ok. 5) Replace IDM. 2) Check fibers/cables.TX freq). 4) Use line loopbacks to confirm input/IDU is ok. 5) Replace IDM. 2) Check fibers/cables. - 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 - FibeAir® Troubleshooting Guide 14 .Trap ID Description Fiber RS: Signal Degrade Probable Cause Minor line BER alarm Corrective Actions 1) Check line input. 2) Check cables. 4) Use line loopbacks to confirm input/IDM is ok. 1) Check line input. 3) Verify end equipment transmits properly. 3) Verify end equipment transmits properly. 5) Replace IDU. 1) Enable GbE port. Fiber HP: Loss of pointer (LOP) alarm occurs. Fiber LP: Loss of pointer (LOP) alarm occurs. 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.Trap ID 27 27 Description Fiber LP #n: AIS Fiber HP: AIS Fiber RS: Unexpected ?10. 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. or disconnect fiber.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. - 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 - FibeAir® Troubleshooting Guide 15 . disable GbE port of source. Radio LP: Remote Defect Identifier signal (RDI) occurs. Port disabled but line is connected. Trib MS: RDI Trib LP #n: RDI Trib HP: RDI Radio MS: Remote Defect Identifier signal (RDI) occurs. Trib LP #n: Unequipped Trib HP: Unequipped Radio LP: Unequipped Corrective Actions - 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 FibeAir® Troubleshooting Guide 16 . Fiber MS: 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. Fiber LP: Payload Label Mismatch (PLM) occurs. Fiber HP: Payload Label Mismatch (PLM) occurs. Fiber LP: Remote Defect Identifier signal (RDI) occurs. Radio HP: Payload Label Mismatch (PLM) occurs.Trap ID Description Radio HP: RDI Probable Cause Radio HP: Remote Defect Identifier signal (RDI) occurs. 1) Download correct SW/FW/Configuration scripts. External alarm input #7 configured and triggered by user. 42 FibeAir® Troubleshooting Guide 17 . 42 General Hardware Fault #2 XO failure – Modem board 42 XC <Type> FPGA File is Missing XC firmware file is missing in the 2-floor IDC. 1) Download XC firmware file of the required type and reset the IDC. External alarm input #5 configured and triggered by user. External alarm input #3 configured and triggered by user. 2) Replace IDM.Trap ID Description External Alarm Probable Cause External alarm input #2 configured and triggered by user. 3) Replace IDC. External alarm input #8 configured and triggered by user. 1) Replace Subrack Auxiliary module. 2) Replace IDM. 42 General Hardware Fault #11 Wayside Firmware File is Missing Wrong card type detected in Subrack Auxiliary slot. 1) Download Wayside firmware file to the IDC and reset the IDC. External alarm input #6 configured and triggered by user. 3) Replace IDC. External alarm input #4 configured and triggered by user. XO failure – Mux board Corrective Actions - 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. Wayside firmware file is missing in the IDC. 1) Check if XC module is powered on and no other alarm pertained to XC is active. 2) Replace XC module. 2) Replace Subrack Auxiliary module. - 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. Corrective Actions 1) Check Subrack Auxiliary module is properly inserted. 4) Replace EOW chaining cable. - 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 42 Subrack Auxiliary FPGA File is Missing Subrack Auxiliary firmware file is missing in the 2-floor IDC. 1) Download Subrack Auxiliary firmware file and reset the IDC. 42 General Hardware Fault #10 1) Extract and re-insert Subrack Auxiliary module. 7) Check / replace IDC2 on mate subrack. 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.Trap ID Description Auxiliary Card Fault #01 Probable Cause Subrack Auxiliary module failed or extracted. Verify that EOW is defined on at least one working link on mate subrack. 42 1) Check if Radio module is inserted properly in the subrack and is powered on. 6) Replace local / mate Subrack Auxiliary module. Replace module if faulty. FibeAir® Troubleshooting Guide 18 . 5) Perform reset to the local / mate Subrack Auxiliary module (by extracting and inserting IDC2). 3) Check / fix EOW chaining configuration on mate subrack. Subrack Auxiliary EEPROM checksum failure. 2) Check EOW chaining line input on both subracks. 2) Replace Subrack Auxiliary module. 2) Check that remote IDU has all relevant N+1 Link Group protection line modules operational. General Hardware Fault #9 42 Upper IDM Board (MUX or XC) EEPROM inventory information CRC error General Hardware Fault #8 42 Upper IDM Board (MUX or XC) EEPROM read access error General Hardware Fault #11 42 Lower IDM Board (Modem or XC) EEPROM inventory information CRC error General Hardware Fault #10 42 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. 1) Check that remote IDU is properly configured with N+1 Link Group topology. 3) Replace the module. 3) Replace the module. 1) Try SW Reset affected module / IDM. 2) Check if own or redundant power supply / Radio module (in drawer #1) is powered on. 1) Try SW Reset affected module / IDM. 2) Check that remote IDU is properly configured for N+1 Link Group protection. Replace module if faulty. FibeAir® Troubleshooting Guide 19 . 1) Check if the card is inserted properly in the subrack. 3) Replace the module. 2) Power cycle or re-insert affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 4) Check that Protection Radio link terminates over Protecting Radio module (and not other Radio module).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. 1) Try SW Reset affected module / IDM. Corrective Actions 1) Verify Protection Radio link is up and. 3) Check that remote IDU has properly operational XC board. 42 42 Link Group #1 N+1 Protection Fault: LocalRemote Protection Mismatch N+1 Link Group protection degraded due to LocalRemote Protection Mismatch. 1) Try SW Reset affected module / IDM. no errors over the link. 3) Replace the module. 2) Power cycle or re-insert affected module / IDM. 2) Power cycle or re-insert affected module / IDM. 1) Check that proper Subrack Auxiliary module inserted. 1) Check that IDC #n is power up and finished initialization. Link Group Topology.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. replace ODU). Replace faulty module. Ethernet cable (if applicable). 3) Replace module if faulty. 2) Power IDM off/on. 3) Replace Subrack Auxiliary module. - 42 1) Check ODU connection to the IDU. 42 42 General Hardware Fault #4 IDU XPIC HW fault General Hardware Fault #1 42 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. XPIC Cable Swap Internal IDC to IDC communication failure between modules requied for Link Group protection service. 2) Replace IDM. 1) Download correct SW/FW/Configuration scripts. FibeAir® Troubleshooting Guide 20 . 5) Replace IDU. Subrack#. 2) Extract and re-insert Subrack Auxiliary module. 3) Check for Hardware fault: Subrack Auxiliary module. 1) Download correct SW/FW/Configuration scripts. 3) Replace IDC. 2) Check IF cable and connectors. Corrective Actions 1) Check if the card is inserted properly in the subrack. Subrack IP Base Address. 2) Check & configure both IDCs with proper system configuration: System Type. 3) Replace IDM. 1) Disable loopback 42 Drawer Internal Power Failure (Board #2) 42 Internal Power failure. 2) Check if own or redundant power supply / Radio module is powered on. 4) Replace ODU. 3) Check ODU's N-type connector inner pin is not spliced (if yes. IDC modules. 3) Replace IDC. 42 General Hardware Fault #6 FPGA load failure . 4) Replace IDU. 3) Replace IDC. FibeAir® Troubleshooting Guide 21 . 3) Check ODU's N-type connector inner pin is not spliced (if yes.Subrack Auxiliary board. replace ODU). 3) Replace 2-floor IDC. 1) Download correct SW/FW/Configuration scripts. MUX card upload failure. 2) Replace IDM. Corrective Actions 1) Reset IDU. and then extract and re-insert Subrack Auxiliary board 2) Replace Subrack Auxiliary module. - 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.Mux 42 General Hardware Fault #7 FPGA load failure . 4) Replace ODU. 42 42 General Hardware Fault #5 DAC failure 1) Download correct SW/FW/Configuration scripts. 5) Replace IDM. 42 42 Load the required FW file.Modem Drawer-ODU Communication Failure Drawer cannot communicate with ODC card. 3) Replace IDC. 1) Check ODU connection to IDM. 2) Verify correct SW version. 1) Download correct Subrack Auxiliary FW file to 2-floor IDC. 1) Download correct SW/FW/Configuration scripts. 2) Replace IDM. 3) Verify correct interfaces. 2) Check IF cable and connectors. 3) Replace IDC. For High Power RF Unit: 1) Check BMA connector on OCB 2) Check BMA connector on RFU 42 General Hardware Fault #7 42 FPGA load failure . and reset system. 2) Replace IDM.Trap ID Description IDU-MUX Inner Communication Failure Probable Cause IDC cannot communicate with MUX card. ?9. - 43 File download status. - 43 43 Configuration download status. Initiated by user. and reset system. 2) Replace IDC. FibeAir® Troubleshooting Guide 22 . 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.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. Mismatch in the internal protection configuration between the drawers. 1) Set identical Link ID on both ends of the link. 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. D=xx Mismatch configuration between the IDC Database and the drawer. Reset IDM 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. Corrective Actions 1) Download correct SW/FW/Configuration scripts. or "Copy AUX to IDC" to copy the Auxiliary channel configuration to the AUX FibeAir® Troubleshooting Guide 23 . or "Copy to Drawer" for mismatch resolution. L=xx 46 User Configuration Mismatch (<param name>) S=xx.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. 1) Check and compare configuration 2) See mate Configuration Mismatch Alarm Set identical Link ID 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. 46 Mate Configuration Mismatch (<param name>) M=xx. 1) Set identical Link ID 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. 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. 3) Verify that both links are up. 4) Check XPI 46 General Hardware Fault #1 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). 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. 1) Check link connections and settings. 2) Check XPIC configuration. Drawer ID Mismatch in Protecting Carrier 46 1) Check link connections and settings.Trap ID Description Device Incompatible Alarm (#103) Probable Cause Incomapitibility alarm between link components. 1) Download correct SW/FW/Configuration scripts. 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 General Hardware Fault #4 1) Download correct SW/FW/Configuration scripts. 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. 2) Check XPIC configuration. 2) Replace IDC. 3) Verify that both links are up. 2) Replace IDC. 2) Perform "copy to mate" from the IDC with the correct configuration FibeAir® Troubleshooting Guide 24 . D=xx 1) Check and compare configuration 2) See User Configuration Mismatch Alarm 46 Mate Configuration Mismatch 1) Check and compare configuration. 1) Check the mismatch configuration in the alarms log. 2) Use "Copy to IDC" command to copy the configuration from XC to IDC. 3) Use "Upload/Download Configuration" command followed by S/W reset in order to copy ALL IDC configurations to the IDC. "copy to drawer" command does not copy the protection or XPIC properties (thay are IDC parameters). or "Copy to Drawer" for mismatch resolution. The process will eliminate the mismatch. FibeAir® Troubleshooting Guide 25 . 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 / software reset. The IDC parameters (IP addresses. IDC parameters (IP addresses. external alarms) are not copied.Trap ID Description Mate Configuration Mismatch Probable Cause Configuration mismatch between two drawers in External Protection configuration. 1) Check the mismatch configuration in the alarms log. Raised only after IDC hotswap or S/W reset. Corrective Actions 1) Check and compare configuration. inband) are not copied. 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. 2) Perform "copy to mate" from the drawer with the correct configuration 1) Check the mismatch configuration in the alarms log. User Configuration Mismatch 46 1) Check the mismatch configuration in the alarms log. 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. 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. or "Copy to Drawer". 3) Use "Upload/Download Configuration" command followed by S/W reset in order to copy ALL IDC configurations to the IDC. eliminating the mismatch. Raised only after IDC hotswap or S/W reset. 2) Use "Copy to IDC" command to copy the configuration from the drawer to the IDC. 2) Use "Copy drawer to IDC" command to copy the XPIC/protection configuration from the drawer to the IDC (without reset). 2) Configure the relevant IDC with the correct values for mismatch resolution. and wait one minute for the mismatch alarm to clear. However. in-band. 3) Replace IDCs 49 50 50 Heart Beat (Trap Only) Trib HP: LOM Radio HP: LOM - FibeAir® Troubleshooting Guide 26 . 1) Check that cable is connected properly. 2) Replace IDUs 48 48 For External Protection configuration.SDBER / EXBER / LOF / BER Command was sent to remote end to switch when both local receivers identify Rx fault (for example. 2) Check Mate connected 47 47 - 47 1) Enable protection or disable hitless 1) Download correct SW/FW/Configuration scripts. Heart Beat (Trap Only) Trib HP: LOM Radio HP: Loss of Multiframe (LOM) alarm occurs. 3) Replace IDC. Change Remote Transmitter Request Sent Protection Cable Disconnected Protection Cable Disconnect/Error/Power Error/Problem?10. 2) Replace IDM. Protection cable is connected but errors detected. 2) Replace cable. remote active transmitter fails) Change Master/Slave command 47 SW Mode Changed to Slave/Master?10. 2) Replace protection cable. 1) Replace cable. 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.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. - 47 47 Change Remote Transmitter Request Sent . 3) Verify no interference.Trap ID 50 Description Fiber HP: LOM Probable Cause Fiber HP: Loss of Multiframe (LOM) alarm occurs.TX freq). 3) Verify no interference. 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.TX freq). The link will fail in case of fade. 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. which is intermittent in nature. Hitless switching disabled by user and locked for one of the drawers. 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. 3) Mate IDU has an alarm that prevents it from receiving data. 2) Mate IDU is off. Unused Radio Receiver LOF 52 Hitless Self Radio Receiver LOF FibeAir® Troubleshooting Guide 27 . 2) Check link settings (TX power. 5) Replace IDMs/ODUs 1) Check that the fault is not due to other alarms that can lead to LOF. 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. unlike fading due to multipath condition. - 51 1) Hitless cable disconnected. 4) Use loopbacks to identify problem source. Left/Right receiver is used for processing data Corrective Actions - 51 Hitless Left/Right Receiver in Use Not a real alarm since receiver switching is likely to happen during multipath fading. 4) Use loopbacks to identify problem source. 1) Check line input. 5) Replace IDMs/ODUs - 52 52 Hitless Self Radio Receiver LOF Hitless Cable Disconnect In-Band Radio PPP Link Disconnect?10. 2) Verify user-end Ethernet equipment. 3) Check / replace connecting cable. 3) Check / replace connecting cable. 4) Replace IDC module. 2) Check link settings (TX power. 4) Use loopbacks to identify problem source.In-Band Line PPP Link Disconnect User Channel Ethernet Loss of Carrier Hitless Self Radio Receiver LOF Hitless cable disconnected. 3) Check / replace connecting cable. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.TX freq). 2) Verify user-end Ethernet equipment. 57 In-band connection over the line (STM-1/OC-3 or PPPoE) or over the radio was disconnected. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 53 Connect hitless cable. 4) Replace IDC module. 1) Check line input. User Right Channel Loss of Carrier 1) Check the line connection. 58 1) Check line input. 2) Check in-band configuration. 4) Replace IDC module. 2) Verify user-end Ethernet equipment. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module.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. 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 FibeAir® Troubleshooting Guide 28 . 3) Verify no interference. 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. 3) Check / replace connecting cable. 3) Check / replace connecting cable. 1) Check IF cable and connectors 2) Check that ODU's Ntype connector inner pin is not spliced (if yes. 2) Verify user-end equipment. 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. 2) Verify user-end equipment. 4) Replace IDC module. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 4) Replace ODU. the system is missing one of the needed elements. 1) Check line input. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. For High Power RF Unit: Check BMA connector center pin is not spliced both on RFU and on OCB. 1) Check cable. In case of N+1 Trunk Radio: 5) Replace Subrack Auxiliary module. 4) Replace IDC module. 2) Replace cable. 1) Check line input. 2) Verify user-end equipment. 3) Replace IDM. 3) Check / replace connecting cable. - 1) Disable "Force Switch" 61 FibeAir® Troubleshooting Guide 29 . replace ODU). 4) Replace IDC module. Or. 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) Check anttena alignment. 4) Replace IDM.Trap ID Description Protection Lockout Probable Cause "Protection Lockout" command executed. 3) Replace ODU. 3) Replace ODU.5v) RFU Power Failure (1. 4) Replace IDM. 2) Check link settings (TX power. 4) Replace IDM. 3) Check anttena alignment. Will lock the switching operation until removed. FibeAir® Troubleshooting Guide 30 . 1) Check that the fault is not due to rain/multipath fading or lack of LOS. RFU Rx Level Path2 Out Of Range 63 RSL of Diversity channel is very low (typically below -80 dBm). 2) Check IF cable and connectors. 2) Check IF cable and connectors. 3) Replace ODU. 2) Check link settings (TX power.5v) RFU Rx Level Path1 Out Of Range 63 RSL of Main channel is very low (typically below -80 dBm). 1) Reset IDM. 4) Replace IDM. 1) Reset IDM. 3) Replace ODU. 2) Check IF cable and connectors. 2) Check IF cable and connectors. 4) Replace IDM. 3) Replace ODU.TX freq). 1) Reset IDM. 1) Check installation conditions. 4) Check antenna connections 5) Replace local/remote ODU. 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. 4) Check antenna connections 5) Replace local/remote ODU. 64 RFU Extreme Temperature RFU temperature is too high/low.TX freq). 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 1) Reset 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. FibeAir® Troubleshooting Guide 31 .TX freq). 2) Check link settings (TX power. 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. 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. 3) Replace IDM.Trap ID Description RFU Rx Level Path2 Out Of Range Probable Cause RSL of Diversity channel is very low (typically below 80dBm). 2) Replace SFP. 3) Check anttena alignment. 4)Check antenna connections 5)Replace local/remote ODU. Corrective Actions 1) Check that the fault is not due to rain/multipath fading or lack of LOS. 2) Reset IDM. 2) Replace SFP. 2) Reset IDM. 81 1) Check if XC module is inserted and powered on and no other alarm pertained to XC is active. 1) Check link status. Signal degrade (local or remote). 3) Replace 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. will take effect after next power up. 3) Reset IDM. 76 Conditional Test Failed 1) Reset IDC. Corrective Actions 1) Reconnect SFP. excessive BER (local or remote). 2) Reset IDM. Link ID mismatch (local or remote). 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. 70 Gigabit Ethernet TX Mute Override 70 GbE port is enabled by the user but the system overrides this and mutes the port. 2) Replace XC module. 1) Check link staus. FibeAir® Troubleshooting Guide 32 . GbE LOS (remote) HW encryption fault Encryption loss of frame 71 72 Encryption Fault Encryption Sync Loss 1) Reset IDM. 2) Reset IDC. 75 1) Reset IDC.Trap ID Description Gigabit Ethernet SFP TX Fault Probable Cause SFP does not transmit Ethernet properly. 1) Check the reason for the alarm (see the Probable Cause column) and correct it accordingly. Administrator password is the default value N+1 Link Group protection degraded due to XC card fault. This alarm may appear in the following cases: Radio LOF (local or remote). 1)Check link status. Replace faulty module. no errors over the link. This alarm occurs when the connection between the NMS and the network element is lost. 401 - 402 - FibeAir® Troubleshooting Guide 33 . 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. This alarm occurs when the user fails to log in to the NMS system correctly several times consecutively. Release maintenance command. 2) Check that remote IDU is properly configured for N+1 Link Group protection. 3) Verify that remote subrack is not configured to lockout or forced switch mode. 3) Check that remote IDU has properly operational XC board. 4) Check that the extension cable is connected properly in the remote subrack (if extended mode is used). 2) Check that remote IDU has all N+1 Link Group protection pertained line modules operational. 1) Check Protecting Radio module is powered on and operates properly. 4) Check that Protection Radio link terminates over Protecting Radio module (and not other Radio module). it should also be configured the same in the other subrack). 81 Link Group #1 N+1 Protection Fault: Locked by User Lockout or Force Switch to Protecting Link Group maintenance command activated. and all protection members are configured with the same priority level (if extra traffic is configured as revertive in one subrack. 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.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. and in the Redundancy section. change the server roll from Stand Alone to Main Server. Contact customer support to obtain a new license file. 410 - FibeAir® Troubleshooting Guide 34 . This alarm occurs for a primary HighCapRadioNMS server when its connection to the standby HighCapRadioNMS server is lost. 409 Check your system.Trap ID Description - Probable Cause This alarm occurs when a secondary standby HighCapRadioNMS server tries to connect to a standalone HighCapRadioNMS server. 407 Remove some of the elements. and disable other TFTP servers. This alarm occurs when a user is disconnected by another user. This alarm occurs for the HighCapRadioNMS server when the number of network elements exceeds the license limit. Corrective Actions Open the main server configuration. This alarm occurs for the HighCapRadioNMS server when it fails to load the license file. 403 404 - 405 Contact customer support to obtain a license file for the server. 408 The license file is probably corrupted. but the TFTP port (69) is already bound by another process. This alarm occurs for the HighCapRadioNMS server when the license expires. This alarm occurs for the HighCapRadioNMS server when the license is set to expire in less than two weeks. This alarm occurs when HighCapRadioNMS attempts to start the TFTP. 406 Contact customer support to obtain a license file for the server. or Contact customer support to obtain a license file for the updated number of elements. Corrective Actions Re-install one of the servers.Trap ID Description - Probable Cause This alarm occurs when a secondary standby HighCapRadioNMS server tries to connect to a main HighCapRadioNMS server. 411 414 Disable the feature or contact Support to get an appropriate license. so that the same HighCapRadioNMS software version will be on both servers. FibeAir® Troubleshooting Guide 35 .with a different software version. The enabled feature set is not licensed. modulator.. During the loopback test. Local IDU Interfaces Modem & IF to ODU Local Loop y Full IDU (all three inputs through the IDU.Fault Isolation using Loopbacks The loopback function provides a means of testing the link at various points. FibeAir® Troubleshooting Guide 36 . The test is run from the CeraView management software.. During the procedure. If the received pattern is identical to the sent pattern.. and looped in the IF). the external equipment sends a data pattern and monitors its receipt.. Equipment 101101110. or via the SNMP protocol. 101101110 Equipment 101101110 Radio Link Loopback FibeAir is capable of performing loopback testing at several points in the link. 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. the connection between the equipment and the loop is confirmed. 1. Remote Terminal Remote IDU Modem & IF Line Interface Equipment 101101110. Check the Cables Refer to the figure below for the following procedures. to the remote line interface module. back through the radio link. 2... For Ethernet connection between FibeAir and an Ethernet hub (for example. use a cross cable.. The following steps will help you identify and correct such problems.Remote: y y 155 Mbps Line Interface Wayside Channel Local IDU 101101110.. For serial connection between FibeAir and a PC serial port. FibeAir® Troubleshooting Guide 37 . use a straight cable. If there is a connection problem in the system. Local Terminal 101101110.. connecting to a LAN jack in a wall) use a straight cable. may be due to incorrect cable configuration. Local IDU Interfaces Modem & IF Remote Loop Full Radio Link Loopback (local external equipment through the radio link. CeraView will start. Equipment 101101110. For Ethernet connection between FibeAir and a PC network card... 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.. but an hour glass will appear when the software is loading to indicate that a problem exists. to the local external equipment). In addition. Cable Connections Check Read and Write Communities Ping FibeAir. use a cross cable. or the computer TCP\IP stack. If ping succeeds.For serial connection using a dial-up modem. If ping fails. there may be a network connectivity problem. The following figure shows a typical example of IP addresses and network configuration. the Agent Address must be identical to the IDU IP address. the problem may be with the CeraView software installation. Check the read and write communities in FibeAir and in the management station configuration. Typical Network Configuration FibeAir® Troubleshooting Guide 38 . A typical conflict may occur between the IDU configuration and the related CeraView parameter. and the source address must be identical to the computer’s address. If they should not be included in the same network. After performing the verifications above. In the terminal. and in the Management station configuration. if there is still a problem with network connectivity. Check the Ethernet Connection Verify that the Management station and FibeAir IP interfaces have the same net ID. the serial line speed is specified using the IP Configuration menu. check the serial line speed in FibeAir. check the default router address.Check the Serial Connection If the connection is via serial line. together with the system administrator check for firewalls and routing configuration errors. FibeAir® Troubleshooting Guide 39 .