ODU Troubleshooting Guide V2.0-20110711-A

Product name RTN Product Version
Confidentiality Level INTERNAL Total 25 pages
ODU Troubleshooting Guide

(For internal use only)
Prepared by Reviewed By Reviewed By Approved by
AOC/LMT R&D Development for Microwave Products
Date Date Date Date
2011-03-28
Huawei Technologies Co., Ltd.

All rights reserved
Change History
Change History
Date 2008-6-23 Change Version V1.0 Change Description Completed the initial draft Author Huang Xiongbin, Qu Guizeng, Hu Congjie, Zhong Xiang, Lin Hongyong, and Jiang Shidong Qu Guizeng and Huang Xiongbin Huang Xiongbin Huang Xiongbin
2008-9-17
V1.1
Updated the troubleshooting method in section "ODU Reports the IF-INPWR-ABN Alarm." Updated the section "ODU reports the RSL_LOW Alarm." Updated the section "Microwave Service Troubleshooting" and modified the sequence of IF cable check and ODU replacement.
2011-03-28
V1.2
Reviewed and updated the file comprehensively; add FAQs.
Yu Guobin and Wang Zeming
2013-10-30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Contents
Contents
Change History................................................................................. i 1 Overview...................................................................................... 1 2 Application................................................................................... 2 3 Principle....................................................................................... 3 4 Preparations................................................................................. 4 5 Locating Faults Occurred in the Live Network.................................5
5.1 Symptom 1: ODU Reports HARD_BAD Alarm......................................................................................................5 5.1.1 Symptom.............................................................................................................................................................5 5.1.2 Fault Analysis.....................................................................................................................................................5 5.1.3 Troubleshooting..................................................................................................................................................5 5.2 Symptom 2: ODU Reports POWER_ALM Alarm...................................................................................................5 5.2.1 Symptom.............................................................................................................................................................5 5.2.2 Fault Analysis.....................................................................................................................................................6 5.2.3 Troubleshooting..................................................................................................................................................6 5.3 Symptom 3: ODU Reports RADIO_MUTE Alarm.................................................................................................6 5.3.1 Symptom.............................................................................................................................................................6 5.3.2 Fault Analysis.....................................................................................................................................................6 5.3.3 Troubleshooting..................................................................................................................................................6 5.4 Symptom 4: ODU Reports RADIO_RADIO_TSL_LOW or RADIO_RADIO_TSL_HIGH Alarm......................7 5.4.1 Symptom.............................................................................................................................................................7 5.4.2 Fault Analysis.....................................................................................................................................................8 5.4.3 Troubleshooting..................................................................................................................................................8 5.5 Symptom 5: ODU Reports RADIO_RSL_LOW Alarm..........................................................................................8 5.5.1 Symptom.............................................................................................................................................................8 5.5.2 Fault Analysis.....................................................................................................................................................8 5.5.3 Troubleshooting................................................................................................................................................10 5.6 Symptom 6: ODU Keeps on Reporting RADIO_RSL_HIGH Alarm....................................................................10 5.6.1 Symptom...........................................................................................................................................................10 5.6.2 Fault Analysis...................................................................................................................................................10 5.6.3 Troubleshooting................................................................................................................................................10
2013-10-30
ii
Contents
5.7 Symptom 7: ODU Reports BD_STATUS Alarm....................................................................................................11 5.7.1 Symptom...........................................................................................................................................................11 5.7.2 Fault Analysis...................................................................................................................................................11 5.7.3 Troubleshooting................................................................................................................................................11 5.8 Symptom 8: ODU Reports IF_INPWR_ABN Alarm.............................................................................................12 5.8.1 Symptom...........................................................................................................................................................12 5.8.2 Fault Analysis...................................................................................................................................................12 5.8.3 Troubleshooting................................................................................................................................................12 5.9 Symptom 9: ODU Reports RADIO_FADING_MARGIN_INSUFF Alarm..........................................................12 5.9.1 Symptom...........................................................................................................................................................12 5.9.2 Fault Analysis...................................................................................................................................................12 5.9.3 Troubleshooting................................................................................................................................................13 5.10 Symptom 10: ODU Reports LOOP_ALM Alarm................................................................................................13 5.10.1 Symptom.........................................................................................................................................................13 5.10.2 Fault Analysis.................................................................................................................................................13 5.10.3 Troubleshooting..............................................................................................................................................13 5.11 Symptom 11: Receiving Signal Level of the ODU Keeps Low...........................................................................13 5.11.1 Symptom.........................................................................................................................................................13 5.11.2 Fault Analysis.................................................................................................................................................13 5.11.3 Troubleshooting..............................................................................................................................................13
6 Appendix: FAQs of the Live Network.............................................14

6.1 Link for HP/SP/LPA ODU Upgrade Guide............................................................................................................14 6.2 ODU Naming..........................................................................................................................................................14 6.3 Method on How to Distinguish Between Factories................................................................................................15 6.4 Page for Querying the SN Number of the ODU on the Network Management Shown in Figure 1......................15 6.5 Taking the principles Below to Check Factories That Produce the ODU Based on Software Versions................15 6.6 Guide for replacing HP(A)/LP(A)/SP(A)ODU with XMC....................................................................................16 6.7 ODU Radio-Frequency Loop and the Support status of Various ODUs................................................................16 6.8 SN Code of the ODU and the Support Status of the Factory Information ............................................................17 6.9 Configuration Status of the TR Interval Supported by ODU.................................................................................18 6.10 IF Cable Mode......................................................................................................................................................18 6.11 Frequency Sweep Guide and scripts.....................................................................................................................19
2013-10-30
iii
6 Appendix: FAQs of the Live Network
Overview
Maintenance problems occur frequently on microwave products manufactured by Huawei because these products are shortly launched for providing network services. This document aims to troubleshoot the frequently occurred network fault, that is, to enable engineers to check whether the fault is caused by the invalid ODU or the failure in other components. R&D drafts this document based on the analysis and discussions among key members of the maintenance team and other colleagues from the ODU Software, ODU Hardware, and IDU IF. During the analysis and discussions, relevant personnel found that no effective troubleshooting methods are available for microwave products at present. Base on the experiences in solving network problems and problems found in the laboratory, this guide provides troubleshooting methods as many as possible for field engineers' reference. In addition, this guide will be updated accordingly with more and more tools and experiences for troubleshooting emerged in the future.
Application
This guide is applicable to Huawei's own microwave products (including all matched ODUs), instead of purchased microwave products (that is, the turnkey microwave products). This guide assumes that field engineers can use the following troubleshooting methods: Network management (Mandatory) SDH meter (Optional) Other auxiliary tools such as the loopback box (optional) This guide does not involve those faults caused by configuration errors, for example, frequency configuration error. Therefore, the troubleshooting excludes the configuration check. However, this guide describes faults caused by network planning errors, for example, interference caused by the improper frequency planning.
3
The troubleshooting principles are as follows:

Principle
Listing symptoms related to the ODU as many as possible. Listing simple symptoms and then the complicated ones. Providing the method for checking the ODU invalidity of each symptom.
Preparations
To provide facilities for the R&D personnel's following-up and troubleshooting, ensure that all the relevant data has been collected according to the data collection tool provided by the R&D before any operation can be carried out on site. Check whether the configurations of the ODU (including the frequency, power, TR interval, mode, ATPC enabling, and AM function) are consistent with the network design values.
Locating Faults Occurred in the Live Network
5.1 Symptom 1: ODU Reports HARD_BAD Alarm

5.1.1 Symptom
ODU reports the HARD_BAD alarm when both the installation and configuration are correct.
5.1.2 Fault Analysis

Check the ODU configurations, such as the frequency configuration and TR interval configuration. If any of the configurations are incorrect, reconfigure these parameters according to the network files. In case there is no configuration error, the problem must be caused by the failure in the ODU.
5.1.3 Troubleshooting
1. Replace the failed ODU. 2. Check and record both the status information of the time when the alarm occurs on the power cabinet of the equipment room and the performance events of the NE for further fault locating and troubleshooting.
5.2 Symptom 2: ODU Reports POWER_ALM Alarm

5.2.1 Symptom
The ODU reports the POWER_ALM alarm when both the installation and configuration are correct.

Symptom 1: If the ODU reported a transient POWER_ALM, but there is no such alarm now. Check whether the IF board reported the IF_CABLE_OPEN or VOLT_LOS alarm before or when this alarm is reported. If yes, the problem must be caused by the abnormality of the power supply rather than the ODU itself. If no, the problem must be caused by the failure in the ODU. Symptom 2: If the ODU reports the POWER_ALM alarm all the time, Check whether the power output of the IF cable is normal at the ODU side. If no, check the power supply system and ensure the proper power supply to the ODU. If the alarm is cleared, the problem must be caused by the external power supply and the ODU is in normal status. If the power supply is normal but the alarm is still on, the problem must be caused by the failure in the ODU.
Replace the failed ODU.
5.3 Symptom 3: ODU Reports RADIO_MUTE Alarm

5.3.1 Symptom
The ODU reports the MUTE alarm when both the installation and configuration are correct.

1. Check by remote whether the ODU reported the CONFIG_NOSUPPORT alarm at the same time. If yes, the problem must be caused by improper configurations. Make proper configurations to solve this problem. If no, do as follows: 2. Check whether the ODU reported the IF_INPWR_ABN alarm. If yes, see section "5.8"Symptom 8: ODU Reports IF_INPWR_ABN Alarm" for troubleshooting. If no, do as follows: 3. Check whether the ODU is muted manually. If yes, unmute the ODU. If no, the problem must be caused by the failure in the ODU.
2013-10-30
5.4 Symptom 4: ODU Reports RADIO_RADIO_TSL_LOW or RADIO_RADIO_TSL_HIGH Alarm

5.4.1 Symptom
The ODU reports the RADIO_TSL_LOW or RADIO_TSL_HIGH alarm when both the installation and configuration are correct.
2013-10-30

Do as follows to check the networking environment: 1. If the networking is 1+0 and the alarm is a transient alarm, check the connection between the IF cable and the IDU as well as the ODU side, and check whether the waterproof treatment is normal at the ODU port. To upgrade the HOP ODU, see Notice on Pre-Warning for the TSL_LOW Alarm Transiently Reported by ODUs 2. If the alarm is cleared after the upgrade, that means the problem is solved already and no need any other operations. If the ODU reports the RADIO_TSL_LOW or RADIO_TSL_HIGH alarm again after the upgrade, the problem must be caused by the failure in the ODU. 3. If the networking is 1+0 and the alarm is steady on, the problem must be caused by the failure in the ODU. 4. If the networking is 1+1HSB or 1+1SD, perform hard resetting to the ODU first through the network management (If no network management, turn on/off the power switch of the IDU IF board) to check whether the alarm is cleared or not. If no, the problem must be caused by the failure in the ODU. If yes, switch manually to the ODU that has already reported the alarm. If the ODU works normally, follow step 1; if the alarm is reported and switched again, the problem must be caused by the failure in the ODU.
1. Reset first the ODU that has reported this alarm under the 1+1 networking protection. 2. Replace the failed ODU.
5.5 Symptom 5: ODU Reports RADIO_RSL_LOW Alarm

5.5.1 Symptom
The ODU reports the RADIO_RSL_LOW alarm transient ly when both the installation and configuration are correct. This alarm may be caused by those factors such as the interruption, space link fading, or hardware failures, which needs to be analyzed separately.

Symptom 1: The local end reports this alarm and the receiving power at the remote end is normal. 1. Check whether the transmission power at the remote end of the ODU is normal. Check the actual transmission power and alarms at the remote end of the ODU through the network management or survey on site. If the ODU reported the RADIO_TSL_LOW or MUTE, or HARD_BAD alarm, power failure occurred at the remote end of the ODU, or ODU reported the HARD_BAD alarm at the local end, handle the preceding alarms first (see the corresponding method for faults analysis). 2. If the problems described in section 1 do not exist, sweep the frequency at the local end to check whether there is any interruption on the ODU. Collect the relevant data and analyze it with the R&D department.
2013-10-30 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 8
Symptom 2: This alarm is reported at both the local end and the remote end during operation. 1. Check whether the ODU reported the Hard_bad alarm at both ends. If yes, handle this alarm first (refer to the corresponding method for fault analysis). If on other alarms occur, do as follows: 2. This problem may be caused by the frequency deviation at one end of the ODU. Reset the ODU at one end to check whether the alarm is cleared and whether the link is restored. If yes, this problem must be caused by the frequency deviation of the ODU. To solve the problem, replace the ODU. Otherwise, reset the ODU at the other end to check whether the alarm is cleared or whether the link is restored. If yes, this problem must be caused by the frequency deviation; replace the ODU to solve the problem. If no, do as follows: 3. Check whether the space link is blocked through a telescope or other methods. If there is no block, do as follows: 4. Check the power status when the alarm did not occur yet. If the receiving power at both ends lowered gradually and the alarm was reported eventually, check whether the antenna is in the right position. Adjust the antenna and check whether there is water penetration between the interface of the antenna and the combiner (the flexible waveguide needs to be checked, too). For other problems, do as follows: 5. Replace the ODU at one end and then check whether the alarm is cleared and whether the link is restored. If yes, the problem must be caused by the failure in the ODU. Otherwise, the problem must be caused by the ODU at the other end. Replace the ODU at the other end to solve this problem. Symptom 3: This alarm is reported at both ends during the deployment debugging. 1. Check whether the transmission power is normal at the remote end of the ODU. Check the actual transmission power and alarms at the remote end of the ODU through the network management or survey on site. If the ODU reported the RADIO_TSL_LOW or MUTE, or HARD_BAD alarm, the power failure occurred at the remote end of the ODU, or the ODU reported the HARD_BAD alarm at the local end, handle the preceding alarms first (see the corresponding method for faults analysis). 2. Check the polarization compatibility between the sites at both ends of the ODU and the antenna as well as the direction of the polarization at both ends of the link. This kind of polarization error should be checked and solved during the ODU and antenna installation. Adjust the inconsistence if any, otherwise, do as follows: 3. Check whether the space link is blocked through a telescope or contacting local agencies. If no block exists, do as follows: 4. Check whether the antenna is fixed correctly. Contact the local network planning department and check through professional software whether the antenna is placed too high or too low (this problem has occurred in Indonesia before). If yes, negotiate with the local network planning department and customers for solution. Otherwise, turn the antenna in both horizontal and vertical directions in a large scale. If this alarm is cleared during this process, this problem must be caused by the positioning of the antenna. Adjust the antenna carefully to solve the problem. Otherwise, do as follows: 5. Check whether the receiving link of the ODU is invalid at the local end.
2013-10-30
Cares must be taken during the antenna alignment due to the small bean width of the major lode of the high frequency antennas with big aperture. Because the echo flapping caused by poor connection of the interface has too much effect on the HF signal, ensure the high compatibility of both the HF ODU and the antenna during the connection.
1. According to step 2 in symptom 2, if the alarm is cleared after the ODU reset, ensure the continuous operation of this ODU first in case the spare parts are not sufficient, and keep relevant records. Replace the failed ODU when replace kits are available. 2. Check and record both the status information of the time when the alarm occurs on the power cabinet of the equipment room and the performance events of the NE for further fault locating and troubleshooting.
5.6 Symptom 6: ODU Keeps on Reporting RADIO_RSL_HIGH Alarm

5.6.1 Symptom
The ODU keeps reporting the RADIO_RSL_LOW alarm when both the installation and configuration are correct. If it is a transient alarm, the problem may be caused by the multipath fade. The relevant data needs to be collected for R&D personnel's analysis.

1. Check the actual receiving power of this ODU. If this power is smaller than the alarm threshold (the threshold of the RADIO_RSL_HIGH alarm is -20dBm) and the alarm still cannot be cleared, the problem must be caused by the failure in the ODU. Otherwise, do as follows: 2. Check whether the ODU configuration is consistent with the network file. If no, make configurations properly. Otherwise, do as follows: 3. Mute the transmission power at the remote end and sweep the in-band frequency at the local end of the ODU to check whether there is any interruption. Otherwise, do as follows: 4. Check whether the service is normal or not. If yes, the problem must be caused by the failure in the ODU at the local end. Otherwise, do as follows: 5. If the problem remains, collect the complete data at both ends of this HOP link thorough data collection tools and provide the data to R&D personnel for analysis.
2013-10-30
10
5.7 Symptom 7: ODU Reports BD_STATUS Alarm

5.7.1 Symptom
The ODU reports the BD_STATUS alarm when both the installation and configuration are correct.

Symptom 1: The service is not interrupted when the BD_STATUS occurs. 1. Check whether this problem meets the pre-alert conditions of the Notice on Pre-Warning for the ODU Offline Abnormally of OptiX RTN 600 Products . If no, do as follows: 2. If the service is not interrupted when the ODU reports the BD_STATUS alarm, something must be wrong with the ODU or the communication link of the IF board. Field engineers need to replace the IF board or the ODU to confirm this problem. 3. Replace the IF board first. If the alarm is cleared, the problem must be caused by the IF board rather than the ODU. If the alarm is cleared, something must be wrong with the ODU. Symptom 2: The service is interrupted when the BD_STATUS occurs. 1. Those reasons may cause this alarm, including the IDU fault, poor connection or damage of the IF cable, or ODU hardware failure. Do as follows for troubleshooting: 2. Check whether the output voltage of the IF board corresponding to the ODU is normal or not. If the voltage is abnormal, make adjustment according to the maintenance guide to ensure the normal voltage output. If the output voltage is normal, do as follows: 3. Connect the cable of the IF board, turn on the IF switch, and then check whether the IF cable output is normal at the ODU side. If no, the fault must lie in the IF cable. Remake the connector of the IF cable. If the problem still exists, change the IF cable. If the output is normal, do as follows: 4. Connect the IF cable with the ODU. If the alarm is cleared, the problem must be caused by the poor connection between the IF cable and the ODU. If the alarm still remains, the problem must be the failure in the ODU.
2013-10-30
11
5.8 Symptom 8: ODU Reports IF_INPWR_ABN Alarm

5.8.1 Symptom
The ODU reports the alarm when both the installation and configuration are correct.

Symptom 1: The ODU reports this alarm transiently. Check whether those operations are performed when the transient alarm occurs, including the loopback, power-off, and reset. If yes, this alarm must be caused by such operations. If the ODU runs normally, no need to take any action. However, if there are no such operations, collect 1HOP data for R&D personnel's analysis. Symptom 2: The ODU reports this alarm continuously. Continuous alarm means the alarm occurs suddenly after the equipment runs normally for a period of time. This alarm may be caused by the corresponding IF board failure, IF cable failure, or ODU failure. Do as follows for troubleshooting: 1. Perform soft reset to the ODU. If the alarm is cleared, the problem must be caused by the software the failure in the ODU. Otherwise, do as follows: 2. Perform hard reset to the ODU. If the alarm is cleared, the problem must be caused by the software the failure in the ODU. Otherwise, do as follows: 3. Replace the IF board. If the alarm is cleared, the problem must be caused by the software the failure in the ODU. Otherwise, do as follows: 4. Replace the ODU, if the alarm is cleared, the problem must be caused by the ODU failure.
5.9 Symptom 9: ODU Reports RADIO_FADING_MARGIN_INSUFF Alarm

5.9.1 Symptom
The ODU reports the RADIO_FADING_MARGIN_INSUFF alarm when both the installation and configuration are correct.

For details, see Chapter 5.5"Symptom 5: ODU Reports RADIO_RSL_LOW Alarm."
2013-10-30
12
5.10 Symptom 10: ODU Reports LOOP_ALM Alarm

5.10.1 Symptom
The ODU reports the LOOP_ALM alarm when both the installation and configuration are correct.

1. This alarm indicates that the loop operation has been performed on the ODU. Check whether the loop has been configured. If yes, this alarm is normal. To clear this alarm, just cancel the loop operation. Otherwise, do as follows: 2. Perform hard reset to the ODU to check whether the alarm is cleared. If yes, the problem must be caused by the failure in the ODU. Otherwise, something must be wrong with the ODU hardware.
1. Cancel the loop operation to clear this alarm. 2. Replace the ODU with hardware failure.
5.11 Symptom 11: Receiving Signal Level of the ODU Keeps Low
5.11.1 Symptom
When both the installation and configuration are correct, the ATPC is disabled and the actual receiving power of the ODU is much lower than the target value of the network design (more than 10 dB lower than the designed target value). Remark: This guide analyzes only the receiving signal level that are more than 10 dB lower than the network design value rather than level that are less than 10 dB lower than the network design value (no details provided here since it needs to be analyzed case by case).

2013-10-30
13
Appendix: FAQs of the Live Network
6.1 Link for HP/SP/LPA ODU Upgrade Guide

The link for HP/SP/LPA ODU upgrade guide is as follows:
http://support.huawei.com/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000569975&doc_type=1232/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000569975&doc_type=123-2.
The link for downloading the 1.10 version of the HP/SP/LPA ODU is as follows: http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do? actionFlag=getDetail&node=000001435394&colID=ROOTWEB|CO0000000065.
6.2 ODU Naming

1. The ODU consists of three series and each series contains multiple categories. 2. To distinguish between the series name and the ODU category name, Huawei describes the series in full name and the ODU category in abbreviation. 3. No new series will be added in the future. The ODU products, including the self-developed and newly-imported ones, will be categorized to these three series according to their features and specifications. For example, if the power of a newly-imported ODU is more than the current HP, this ODU will be named as HPA or HPB instead of VP. 4. Typical feature of the Low Capacity for PDH Series: Supports only the PDH microwave application. 5. Typical features of the Standard Power Series: Supports the microwave application for both the PDH and the SDH with standard transmission power. 6. Typical features of the High-Power Series: Supports the microwave application for both the PDH and the SDH with high transmission power.
6.3 Method on How to Distinguish Between Factories
1. Two digits 21 Barcode identification. 2. Eight digits Huawei BOM code. 3. Two Characters Product Code, 10XMC1/XMC-2,6CHP/SP/LPA,4G HPA/SPA/LP. 4. Two Characters -- Product Date, The first is Year, and the second is Month, A 10, B 11, C 12, and so on. For example, 91 2009.01, AB 2010.11. 5. Six digits serial number.
6.4 Page for Querying the SN Number of the ODU on the Network Management Shown in Figure 1
Figure a.1 Page for querying the SN number of the ODU on the network management
6.5 Taking the principles Below to Check Factories That Produce the ODU Based on Software Versions
8 xx indicates the ODU is Huawei's own product. 1 xx indicates the ODU is made by RBW. 2 xx indicates the ODU is made by Comba.
6.6 Guide for replacing HP(A)/LP(A)/SP(A)ODU with XMC

Visit the support web site to view the Guide for Replacing HP (A)/LP(A)/SP(A)ODU with XMC.
6.7 ODU Radio-Frequency Loop and the Support status of Various ODUs
1. Loop: Refers to an operation for cable troubleshooting, that is, to transmit the received signal back to the signal source end at the assigned site (or the loop site). Check the back transmission signal at the source end to check whether there is something wrong with the line. The loop consists of the inloop and outloop. 2. At present, the radio-frequency supports only the inloop. Those ODUs, including the RBM and the XMC ODU, can support the software radio-frequency inloop. ODUs made by Comba do not support the radio-frequency function. The ODU inloop can be performed through signal spill-over. After setting the radio-frequency inloop, set the bandwidth to 7M QPSK and configure the fixed frequency (the minimum frequency is +3.5 MHz at the Tx high site while the maximum frequency is -3.5 MHz at the Tx low site). Then configure the maximum transmission power as -0.5dB. In addition, if the loop is performed through the signal spill-over, the receiving power will change after the configuration, and the value of the receiving power varies with different frequency band. The 900R3 version or later supports the coupled loop of Huawei's own ODU. After setting, the modulation mode is QPSK and the bandwidth keeps unchanged. The frequency and power
vary with the ODU hardware. 3. Figure a.1 shows the query method through the network management (U2000). Figure a.1 Query method through the network management
6.8 SN Code of the ODU and the Support Status of the Factory Information
1. The ODU barcode version supports all IDU versions, and all ODUs support all IDU versions staring from October of 2009. Therefore, the ODU barcode can be checked on the IDU page. Figure a.1 shows the page for query based on the network management.
2013-10-30
17
Figure a.1 Page for query based on the network management
6.9 Configuration Status of the TR Interval Supported by ODU

All ODU can support the TR interval configuration that is supported by the product file. The ODU made by Comba does not support the TR interval configuration that is not included in the specification, however, The RBW and Huawei's own ODU can support this kind of TR interval configuration.
6.10 IF Cable Mode

The IF cable is used in actual application scenarios according to the IF cable length. 1. 5D cable Application scenario: 0120 m. 2. RG-8U cable Application scenario: 120180 m. 3. 1/2' Cable Application scenario: 180300 m.
6.11 Frequency Sweep Guide and scripts

For details, click the following link to view the section "Troubleshooting and Broken Pieces Handling" in RTN Maintenance Data Packet V2.0-20110130-A: http://support-hk.huawei.com/support/pages/kbcenter/view/product.do? actionFlag=detailProductSimple&web_doc_id=SC0000626357&doc_type=123-2.
2013-10-30
19

ODU Troubleshooting Guide V2.0-20110711-A

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ODU Troubleshooting Guide V2.0-20110711-A

Загружено:

Авторское право:

Доступные форматы

Product name RTN Product Version

Confidentiality Level INTERNAL Total 25 pages

ODU Troubleshooting Guide

Prepared by Reviewed By Reviewed By Approved by

AOC/LMT R&D Development for Microwave Products

Date Date Date Date

Huawei Technologies Co., Ltd.

ODU Troubleshooting Guide

Reviewed and updated the file comprehensively; add FAQs.

Yu Guobin and Wang Zeming

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network.............................................14

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

Locating Faults Occurred in the Live Network

5.1 Symptom 1: ODU Reports HARD_BAD Alarm

5.1.2 Fault Analysis

5.2 Symptom 2: ODU Reports POWER_ALM Alarm

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.2.2 Fault Analysis

5.3 Symptom 3: ODU Reports RADIO_MUTE Alarm

5.3.2 Fault Analysis

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.4 Symptom 4: ODU Reports RADIO_RADIO_TSL_LOW or RADIO_RADIO_TSL_HIGH Alarm

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.4.2 Fault Analysis

5.5 Symptom 5: ODU Reports RADIO_RSL_LOW Alarm

5.5.2 Fault Analysis

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.6 Symptom 6: ODU Keeps on Reporting RADIO_RSL_HIGH Alarm

5.6.2 Fault Analysis

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.7 Symptom 7: ODU Reports BD_STATUS Alarm

5.7.2 Fault Analysis

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

ODU Troubleshooting Guide

6 Appendix: FAQs of the Live Network

5.8 Symptom 8: ODU Reports IF_INPWR_ABN Alarm

5.8.2 Fault Analysis

5.9 Symptom 9: ODU Reports RADIO_FADING_MARGIN_INSUFF Alarm