RTN 310 V100R001C00 Maintenance Guide 02

OptiX RTN 310 Radio Transmission SystemV100R001C00

Maintenance Guide

Issue 02

Date 2012-07-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2012-07-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX RTN 310 V100R001C00

iManager U2000 V100R006C02

Intended AudienceThis document provides the guidelines to maintaining the OptiX RTN 310. It also describes thealarms and performance events that are required for troubleshooting during the maintenance.

This document is intended for:

l Network planning engineerl Data configuration engineerl System maintenance engineer

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk,which if not avoided, will result in death orserious injury.

Indicates a hazard with a medium or low levelof risk, which if not avoided, could result inminor or moderate injury.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide About This Document


ii

Symbol Description

Indicates a potentially hazardous situation,which if not avoided, could result inequipment damage, data loss, performancedegradation, or unexpected results.

Indicates a tip that may help you solve aproblem or save time.

Provides additional information to emphasizeor supplement important points of the maintext.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.



iii


{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Updates in Issue 02 (2012-07-30) Based on Product Version V100R001C00This document is the second issue of the V100R001C00 product version.

Update Description

A.1 Alarm List Added the SSL_CERT_NOENC alarm.

Updates in Issue 01 (2012-04-25) Based on Product Version V100R001C00This document is the first issue of the V100R001C00 product version.



iv

Contents

About This Document.....................................................................................................................ii

1 Safety Precautions.........................................................................................................................11.1 General Safety Precautions.................................................................................................................................21.2 Warning and Safety Symbols.............................................................................................................................31.3 Electrical Safety..................................................................................................................................................41.4 Environment of Flammable Gas.........................................................................................................................61.5 Storage Batteries.................................................................................................................................................61.6 Radiation.............................................................................................................................................................8

1.6.1 Safe Usage of Optical Fibers.....................................................................................................................81.6.2 Electromagnetic Exposure.........................................................................................................................91.6.3 Forbidden Areas........................................................................................................................................91.6.4 Laser..........................................................................................................................................................91.6.5 Microwave...............................................................................................................................................10

1.7 Working at Heights...........................................................................................................................................101.7.1 Hoisting Heavy Objects...........................................................................................................................111.7.2 Using Ladders..........................................................................................................................................12

1.8 Mechanical Safety............................................................................................................................................131.9 Other Precautions.............................................................................................................................................14

2 Routine Maintenance..................................................................................................................16

3 Emergency Maintenance Guide................................................................................................183.1 Definition of Emergency..................................................................................................................................193.2 Purposes of Emergency Maintenance...............................................................................................................193.3 Procedure for Emergency Maintenance............................................................................................................19

4 Troubleshooting..........................................................................................................................264.1 General Troubleshooting Procedure.................................................................................................................274.2 Troubleshooting the Radio Link.......................................................................................................................284.3 Troubleshooting Ethernet Service Faults.........................................................................................................35

5 Part Replacement.........................................................................................................................415.1 Replacing an OptiX RTN 310..........................................................................................................................425.2 Replacing an SFP Module................................................................................................................................44

6 Database Backup and Restoration...........................................................................................46

OptiX RTN 310 Radio Transmission SystemMaintenance Guide Contents


v

6.1 NE Database.....................................................................................................................................................476.2 Backing Up the Database Manually.................................................................................................................486.3 Setting the Database Backup Policy.................................................................................................................49

6.3.1 Setting the User-Defined Backup Policy.................................................................................................496.3.2 Executing the Backup Policy of the Device............................................................................................516.3.3 Suspending the Backup Policy of the Device..........................................................................................52

6.4 Restoring the Database by NMS......................................................................................................................536.5 Recovering Databases from a USB Flash Drive..............................................................................................56

7 Supporting Task..........................................................................................................................607.1 Browsing Alarms, Abnormal Events, and Performance Events.......................................................................62

7.1.1 Checking the NE Status(U2000).............................................................................................................627.1.2 Checking the NE Status(Web LCT)........................................................................................................647.1.3 Browsing Current Alarms(U2000)..........................................................................................................657.1.4 Browsing Current Alarms(Web LCT).....................................................................................................677.1.5 Browsing History Alarms(U2000)..........................................................................................................697.1.6 Browsing History Alarms(Web LCT).....................................................................................................707.1.7 Browsing Current Performance Events(U2000)......................................................................................727.1.8 Browsing Current Performance Events(Web LCT)................................................................................737.1.9 Browsing History Performance Events(U2000)......................................................................................747.1.10 Browsing History Performance Events(Web LCT)...............................................................................747.1.11 Browsing Current Alarms of the radio link(U2000).............................................................................767.1.12 Browsing Current Alarms of the radio link(Web LCT)........................................................................767.1.13 Browsing Current Performance Events of the radio link(Web LCT)....................................................777.1.14 Browsing Historical Performance Data of a Radio Link(Web LCT)....................................................787.1.15 Browsing the Performance Event Threshold-Crossing Records(U2000)..............................................797.1.16 Browsing the Performance Event Threshold-Crossing Records(Web LCT)........................................807.1.17 Browsing Abnormal Events(U2000).....................................................................................................817.1.18 Browsing Abnormal Events(Web LCT)................................................................................................827.1.19 Browsing UAT Events(U2000).............................................................................................................837.1.20 Browsing UAT Events(Web LCT)........................................................................................................84

7.2 Setting Alarm and Performance Management Functions.................................................................................857.2.1 Configuring the Performance Monitoring Status of NEs........................................................................857.2.2 Suppressing Alarms.................................................................................................................................867.2.3 Reversing Alarms for Ports.....................................................................................................................877.2.4 Setting Bit Error Thresholds for Microwave Ports..................................................................................887.2.5 Setting Monitoring and Auto-Report Status of Performance Events......................................................897.2.6 Setting Performance Thresholds..............................................................................................................897.2.7 Resetting Performance Registers.............................................................................................................90

7.3 Querying a Report............................................................................................................................................917.3.1 Querying the Board Information Report(U2000)....................................................................................917.3.2 Querying the Board Information Report(Web LCT)...............................................................................927.3.3 Querying the Board Manufacturing Information Report(U2000)...........................................................93



vi

7.3.4 Querying the Board Manufacturing Information Report(Web LCT)......................................................947.3.5 Querying the Microwave Link Information Report.................................................................................957.3.6 Querying the Network-wide License Report...........................................................................................96

7.4 Software Loopback...........................................................................................................................................977.4.1 Setting Loopbacks for Ethernet Ports......................................................................................................977.4.2 Setting Loopback for the IF Board..........................................................................................................98

7.5 Reset...............................................................................................................................................................1017.5.1 Cold Reset..............................................................................................................................................1017.5.2 Warm Reset...........................................................................................................................................102

7.6 Detecting Consecutive Waves........................................................................................................................1047.7 PRBS Test.......................................................................................................................................................1047.8 Querying the License Capacity.......................................................................................................................1067.9 Scanning Interfering Signals..........................................................................................................................1077.10 Setting the Automatic Release Function......................................................................................................1077.11 Querying Power Consumption of NE...........................................................................................................1087.12 Querying the Attributes of an Ethernet Port.................................................................................................1097.13 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports.......................................1107.14 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet Ports...................................1117.15 End-to-End Management on Fibers, Tunnels, and PWE3 Services.............................................................112

7.15.1 Expanding/Collapsing Fibers and Cables............................................................................................1127.15.2 Querying the Radio Link Information.................................................................................................1127.15.3 Querying the Radio Link Performance................................................................................................113

A Alarm Reference.......................................................................................................................115A.1 Alarm List......................................................................................................................................................116A.2 Alarms and Handling Procedures..................................................................................................................120

A.2.1 AM_DOWNSHIFT..............................................................................................................................120A.2.2 BDTEMP_SENSOR_FAIL..................................................................................................................121A.2.3 BOOTROM_BAD................................................................................................................................122A.2.4 CLK_LOCK_FAIL...............................................................................................................................123A.2.5 DBMS_DELETE..................................................................................................................................124A.2.6 DBMS_ERROR....................................................................................................................................125A.2.7 DBMS_PROTECT_MODE.................................................................................................................126A.2.8 DCNSIZE_OVER.................................................................................................................................126A.2.9 ERPS_IN_PROTECTION....................................................................................................................127A.2.10 ETH_CFM_AIS..................................................................................................................................128A.2.11 ETH_CFM_LOC................................................................................................................................130A.2.12 ETH_CFM_MISMERGE...................................................................................................................132A.2.13 ETH_CFM_RDI.................................................................................................................................134A.2.14 ETH_CFM_UNEXPERI....................................................................................................................135A.2.15 ETH_EFM_DF...................................................................................................................................136A.2.16 ETH_EFM_EVENT...........................................................................................................................138A.2.17 ETH_EFM_LOOPBACK...................................................................................................................139



vii

A.2.18 ETH_EFM_REMFAULT...................................................................................................................140A.2.19 ETH_LOS...........................................................................................................................................141A.2.20 ETH_NO_FLOW...............................................................................................................................142A.2.21 ETHOAM_SELF_LOOP...................................................................................................................143A.2.22 FLOW_OVER....................................................................................................................................145A.2.23 HARD_BAD.......................................................................................................................................146A.2.24 IN_PWR_ABN...................................................................................................................................149A.2.25 LAG_DOWN......................................................................................................................................150A.2.26 LAG_MEMBER_DOWN..................................................................................................................150A.2.27 LASER_MOD_ERR...........................................................................................................................152A.2.28 LCS_LIMITED...................................................................................................................................153A.2.29 LICENSE_LOST................................................................................................................................154A.2.30 LOOP_ALM.......................................................................................................................................155A.2.31 LSR_NO_FITED................................................................................................................................156A.2.32 LTI......................................................................................................................................................157A.2.33 MAC_EXT_EXC...............................................................................................................................158A.2.34 MAC_FCS_EXC................................................................................................................................160A.2.35 MULTI_RPL_OWNER......................................................................................................................161A.2.36 MW_AM_TEST.................................................................................................................................162A.2.37 MW_BER_EXC.................................................................................................................................162A.2.38 MW_BER_SD....................................................................................................................................165A.2.39 MW_CFG_MISMATCH....................................................................................................................168A.2.40 MW_CONT_WAVE..........................................................................................................................169A.2.41 MW_FEC_UNCOR............................................................................................................................170A.2.42 MW_LIM............................................................................................................................................173A.2.43 MW_LOF...........................................................................................................................................174A.2.44 MW_RDI............................................................................................................................................177A.2.45 NB_UNREACHABLE.......................................................................................................................178A.2.46 NESF_LOST.......................................................................................................................................179A.2.47 NESOFT_MM....................................................................................................................................181A.2.48 NTP_SYNC_FAIL.............................................................................................................................183A.2.49 PASSWORD_NEED_CHANGE.......................................................................................................184A.2.50 PATCH_ACT_TIMEOUT.................................................................................................................184A.2.51 PATCH_DEACT_TIMEOUT............................................................................................................185A.2.52 PATCH_PKGERR.............................................................................................................................186A.2.53 PORT_EXC_TRAFFIC......................................................................................................................187A.2.54 PORTMODE_MISMATCH...............................................................................................................188A.2.55 POWER_ALM...................................................................................................................................189A.2.56 PTP_TIMESTAMP_ABN..................................................................................................................190A.2.57 RADIO_FADING_MARGIN_INSUFF.............................................................................................191A.2.58 RADIO_MUTE..................................................................................................................................193A.2.59 RADIO_RSL_BEYONDTH..............................................................................................................194



viii

A.2.60 RADIO_RSL_HIGH..........................................................................................................................195A.2.61 RADIO_RSL_LOW...........................................................................................................................196A.2.62 RADIO_TSL_HIGH...........................................................................................................................197A.2.63 RADIO_TSL_LOW...........................................................................................................................198A.2.64 S1_SYN_CHANGE...........................................................................................................................198A.2.65 SEC_RADIUS_FAIL.........................................................................................................................199A.2.66 SECU_ALM.......................................................................................................................................201A.2.67 SSL_CERT_NOENC.........................................................................................................................201A.2.68 STORM_CUR_QUENUM_OVER....................................................................................................202A.2.69 SWDL_ACTIVATED_TIMEOUT....................................................................................................203A.2.70 SWDL_COMMIT_FAIL....................................................................................................................204A.2.71 SWDL_INPROCESS.........................................................................................................................205A.2.72 SWDL_NEPKGCHECK....................................................................................................................205A.2.73 SWDL_PKGVER_MM......................................................................................................................206A.2.74 SWDL_ROLLBACK_FAIL...............................................................................................................207A.2.75 SYNC_C_LOS...................................................................................................................................208A.2.76 SYSLOG_COMM_FAIL...................................................................................................................209A.2.77 TEMP_ALARM.................................................................................................................................209A.2.78 TIME_LOCK_FAIL...........................................................................................................................210A.2.79 TIME_LOS.........................................................................................................................................211A.2.80 TIME_NO_TRACE_MODE..............................................................................................................212A.2.81 USB_PROCESS_FAIL......................................................................................................................213A.2.82 XPIC_LOS..........................................................................................................................................214

B Performance Event Reference.................................................................................................217B.1 Performance Event List..................................................................................................................................218

B.1.1 Microwave Performance Events...........................................................................................................218B.1.2 Other Performance Events....................................................................................................................220

B.2 Performance Events and Handling Procedures..............................................................................................222B.2.1 AMDOWNCNT and AMUPCNT........................................................................................................222B.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST.......................................................................................223B.2.3 MAXMEANPATHDELAY, MINMEANPATHDELAY, and AVGMEANPATHDELAY...............223B.2.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR..........................................................................224B.2.5 FEC_BEF_COR_ER and FEC_UNCOR_BLOCK_CNT....................................................................225B.2.6 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...............................................................................226B.2.7 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG............................................................................227B.2.8 MAXPHASEOFFSET, MINPHASEOFFSET, and AVGPHASEOFFSET.........................................227B.2.9 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR........................................................................228B.2.10 PATEMPMAX, PATEMPMIN, and PATEMPCUR.........................................................................229B.2.11 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16, QAMWS32, QAMWS64, QAMWS128,QAMWS256, QAMWS512, QAM_L_WS512, QAMWS1024, and QAM_L_WS1024..............................229B.2.12 RLHTT, RLLTT, TLHTT, and TLLTT..............................................................................................230B.2.13 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG........................................................................231



ix

B.2.14 TLBMAX, TLBMIN, and TLBCUR..................................................................................................231B.2.15 TPLMAX, TPLMIN, and TPLCUR...................................................................................................232B.2.16 RPLMAX, RPLMIN, and RPLCUR..................................................................................................233B.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG.........................................................................233B.2.18 XPIC_XPD_VALUE..........................................................................................................................234

C RMON Event Reference..........................................................................................................235C.1 RMON Alarm Entry List...............................................................................................................................236C.2 RMON Performance Entry List.....................................................................................................................237C.3 RMON Events and Handling Procedures......................................................................................................242

C.3.1 ETHDROP............................................................................................................................................242C.3.2 ETHFCS................................................................................................................................................243C.3.3 ETHFRG...............................................................................................................................................243C.3.4 ETHJAB................................................................................................................................................244C.3.5 ETHOVER............................................................................................................................................245C.3.6 ETHUNDER.........................................................................................................................................246C.3.7 RXBBAD..............................................................................................................................................246

D Alarm Suppression Relationship..........................................................................................248

E Glossary......................................................................................................................................250



x

1 Safety Precautions

About This Chapter

This topic describes the safety precautions that you must follow when installing, operating, andmaintaining Huawei devices.

1.1 General Safety PrecautionsThis topic describes essential safety precautions that instruct you in the selection of measuringand testing instruments when you install, operate, and maintain Huawei devices.

1.2 Warning and Safety SymbolsBefore using the equipment, note the following warning and safety symbols on the equipment.

1.3 Electrical SafetyThis topic describes safety precautions for high voltage, lightning strikes, high leakage current,power cables, fuses, and ESD.

1.4 Environment of Flammable GasThis topic describes safety precautions for the operating environment of a device.

1.5 Storage BatteriesThis topic describes safety precautions for operations of storage batteries.

1.6 RadiationThis topic describes safety precautions for electromagnetic exposure and lasers.

1.7 Working at HeightsThis topic describes safety precautions for working at heights.

1.8 Mechanical SafetyThis topic describes safety precautions for drilling holes, handling sharp objects, operating fans,and carrying heavy objects.

1.9 Other PrecautionsThis topic describes safety precautions for removing and inserting boards, binding signal cables,and routing cables.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 1 Safety Precautions


1

1.1 General Safety PrecautionsThis topic describes essential safety precautions that instruct you in the selection of measuringand testing instruments when you install, operate, and maintain Huawei devices.

All Safety PrecautionsTo ensure the safety of humans and a device, follow the marks on the device and all the safetyprecautions in this document when installing, operating, and maintaining a device.

The "CAUTION", "WARNING", and "DANGER" marks in this document do not cover all thesafety precautions that must be followed. They are supplements to the safety precautions.

Local Laws and RegulationsWhen operating a device, always comply with the local laws and regulations. The safetyprecautions provided in the documents are in addition/supplementary to the local laws andregulations.

Basic Installation RequirementsThe installation and maintenance personnel of Huawei devices must receive strict training andbe familiar with the proper operation methods and safety precautions before any operation.

l Only trained and qualified personnel are permitted to install, operate, and maintain a device.l Only certified professionals are permitted to remove the safety facilities, and to troubleshoot

and maintain the device.l Only the personnel authenticated or authorized by Huawei are permitted to replace or

change the device or parts of the device (including software).l The operating personnel must immediately report the faults or errors that may cause safety

problems to the person in charge.

Grounding RequirementsThe grounding requirements are applicable to the device that needs to be grounded.

l When installing the device, always connect the grounding facilities first. When removingthe device, always disconnect the grounding facilities last.

l Ensure that the grounding conductor is intact.l Do not operate the device in the absence of a suitably installed grounding conductor.l The device must be connected to the protection ground (PGND) permanently. Before

operating the device, check the electrical connections of the device, and ensure that thedevice is properly grounded.

Human Safetyl When there is a risk of a lightning strike, do not operate the fixed terminal or touch the

cables.l When there is risk of a lightning strike, unplug the AC power connector. Do not use the

fixed terminal or touch the terminal or antenna connector.



2

NOTEThe preceding requirements apply to wireless fixed station terminals.

l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits totelephone-network voltage (TNV) circuits.

l Do not look into optical ports without eye protection. Otherwise, human eyes may be hurtby laser beams.

l Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD wriststrap. In addition, you need to get off the conductive objects, such as jewelry and watches,to prevent electric shock and burn.

l In case of fire, escape from the building or site where the device is located and press thefire alarm bell or dial the telephone number for fire alarms. Do not enter the burning buildingagain in any situation.

Device Safetyl Before any operation, install the device firmly on the ground or other rigid objects, such as

on a wall or in a rack.l When the system is working, ensure that the ventilation hole is not blocked.l When installing the front panel, use a tool to tighten the screws firmly, if required.l After installing the device, clean up the packing materials.

1.2 Warning and Safety SymbolsBefore using the equipment, note the following warning and safety symbols on the equipment.

Table 1-1 lists the warning and safety symbols of the OptiX RTN 310 and their meanings.

Table 1-1 Warning and safety symbols of the OptiX RTN 310

Label Label Name Description

ESD protectionlabel

Indicates that theequipment issensitive to staticelectricity.

Radiation warninglabel

Indicates that theequipmentgenerateselectromagneticradiation.



3

Label Label Name Description

High temperaturewarning label

Indicates that theequipmentsurfacetemperature mayexceed 70°Cwhen theambienttemperature ishigher than 55°C. Wearprotectivegloves to handlethe equipment.

Grounding label Indicates thegroundingposition of achassis.

1.3 Electrical SafetyThis topic describes safety precautions for high voltage, lightning strikes, high leakage current,power cables, fuses, and ESD.

High Voltage

DANGERl A high-voltage power supply provides power for device operations. Direct human contact

with the high voltage power supply or human contact through damp objects can be fatal.

l Unspecified or unauthorized high voltage operations could result in fire or electric shock, orboth.

Thunderstorm

The requirements apply only to wireless base stations or devices with antennas and feeders.

DANGERDo not perform operations on high voltage, AC power, towers, or backstays in stormy weatherconditions.



4

High Leakage Current

WARNINGBefore powering on a device, ground the device. Otherwise, the safety of humans and the devicecannot be ensured.

If a high leakage current mark is labeled near the power connector of the device, you mustconnect the PGND terminal on the shell to the ground before connecting the device to an A/Cinput power supply. This is to prevent the electric shock caused by leakage current of the device.

Power Cables

DANGERDo not install or remove the power cable with a live line. Transient contact between the core ofthe power cable and the conductor may generate electric arc or spark, which may cause fire oreye injury.

l Before installing or removing power cables, you must power off the device.

l Before connecting a power cable, you must ensure that the label on the power cable iscorrect.

Device with Power On

DANGERInstalling or removing a device is prohibited if the device is on.

DANGERDo not install or remove the power cables of the equipment when it is powered on.

Short Circuits

When installing and maintaining devices, place and use the associated tools and instruments inaccordance with regulations to avoid short-circuits caused by metal objects.



5

Fuse

WARNINGIf the fuse on a device blows, replace the fuse with a fuse of the same type and specifications toensure safe operation of the device.

1.4 Environment of Flammable GasThis topic describes safety precautions for the operating environment of a device.

DANGERDo not place or operate devices in an environment of flammable or explosive air or gas.

Operating an electronic device in an environment of flammable gas causes a severe hazard.

1.5 Storage BatteriesThis topic describes safety precautions for operations of storage batteries.

DANGERBefore operating a storage battery, you must read the safety precautions carefully and be familiarwith the method of connecting a storage battery.

l Incorrect operations of storage batteries cause hazards. During operation, prevent any short-circuit, and prevent the electrolyte from overflowing or leakage.

l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte maycorrode metal parts and the circuit boards, and ultimately damage the circuit boards.

l A storage battery contains a great deal of energy. Misoperations may cause a short-circuit,which leads to human injuries.

Basic Precautions

To ensure safety, note the following points before installing or maintaining the storage battery:

l Use special insulation tools.

l Wear an eye protector and take effective protection measures.

l Wear rubber gloves and a protection coat to prevent the hazard caused by the overflowingelectrolyte.



6

l When handling the storage battery, ensure that its electrodes are upward. Leaning orreversing the storage battery is prohibited.

l Before installing or maintaining the storage battery, ensure that the storage battery isdisconnected from the power supply that charges the storage battery.

Short-Circuit

DANGERA battery short-circuit may cause human injuries. Although the voltage of an ordinary batteryis low, the instantaneous high current caused by a short-circuit emits a great deal of energy.

Avoid any short-circuit of batteries caused by metal objects. If possible, disconnect the workingbattery before performing other operations.

Hazardous Gas

CAUTIONDo not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix itproperly to prevent the battery from emitting flammable gas, which may cause fire or deviceerosion.

Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and fireproofingmeasures must be taken at the sites where lead-acid storage batteries are placed.

Battery Temperature

CAUTIONIf a battery overheats, the battery may be deformed or damaged, and the electrolyte mayoverflow.

When the temperature of the battery is higher than 60°C, you need to check whether theelectrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.

Battery Leakage

CAUTIONIn the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.



7

When handling a leaky battery, protect against the possible damage caused by the acid. Whenyou find the electrolyte leaks, you can use the following substances to counteract and absorb theleaking electrolyte:

l Sodium bicarbonate (NaHCO3)

l Sodium carbonate (Na2CO3)

In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended bythe battery manufacturer and any local regulations for acid disposal.

If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyteimmediately by using water. In case of a severe situation, the person must be sent to a hospitalimmediately.

1.6 RadiationThis topic describes safety precautions for electromagnetic exposure and lasers.

1.6.1 Safe Usage of Optical FibersThe laser beam can cause damage to your eyes. Hence, you must exercise caution when usingoptical fibers.

DANGERWhen installing or maintaining optical fibers, avoid direct eye exposure to the laser beamslaunched from the optical interface or fiber connectors. The laser beam can cause damage toyour eyes.

Cleaning Fiber Connectors and Optical Interfaces

CAUTIONIf fiber connectors or flanges are contaminated, optical power commissioning is seriouslyaffected. Therefore, the two endfaces and flange of every external fiber must be cleaned beforethe fiber is led into the equipment through the optical distribution frame (ODF) for being insertedinto an optical interface on the equipment.

The fiber connectors and optical interfaces of the lasers must be cleaned with the followingspecial cleaning tools and materials:

l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can alsobe used. It is prohibited that you use alcohol and formalin.

l Non-woven lens tissuel Special compressed gasl Cotton stick (medical cotton or long fiber cotton)



8

l Special cleaning roll, used with the recommended cleaning solventl Special magnifier for fiber connectors

1.6.2 Electromagnetic ExposureThis topic describes safety precautions for electromagnetic exposure.

If multiple transmit antennas are installed on a tower or backstay, keep away from the transmitdirections of the antennas when you install or maintain an antenna locally.

CAUTIONEnsure that all personnel are beyond the transmit direction of a working antenna.

1.6.3 Forbidden AreasThe topic describes requirements for a forbidden area.

l Before entering an area where the electromagnetic radiation is beyond the specified range,the associated personnel must shut down the electromagnetic radiator or stay at least 10meters away from the electromagnetic radiator, if in the transmit direction.

l A physical barrier and an eye-catching warning flag should be available in each forbiddenarea.

1.6.4 LaserThis topic describes safety precautions for lasers.

WARNINGWhen handling optical fibers, do not stand close to, or look into the optical fiber outlet directlywithout eye protection.

Laser transceivers are used in the optical transmission system and associated test tools. The lasertransmitted through the bare optical fiber produces a small beam of light, and therefore it hasvery high power density and is invisible to human eyes. When a beam of light enters eyes, theeyes may be damaged.

In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without eyeprotection at a distance greater than 150 mm does not cause eye injury. Eye injury may occur,however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used to viewan un-terminated optical fiber.

Safety Instructions Regarding LasersTo avoid laser radiation, obey the following instructions:

l All operations should be performed by authorized personnel who have completed therequired training courses.



9

l Wear a pair of eye-protective glasses when you are handling lasers or fibers.l Ensure that the optical source is switched off before disconnecting optical fiber connectors.l Do not look into the end of an exposed fiber or an open connector when you are not sure

whether the optical source is switched off.l Use an optical power meter to measure the optical power and ensure that the optical source

is switched off.l Before opening the front door of an optical transmission device, ensure that you are not

exposed to laser radiation.l Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe to

view the optical connector or fiber that is transmitting optical signals.

Instructions Regarding Fiber HandlingRead and abide by the following instructions before handling fibers:

l Only trained personnel are permitted to cut and splice fibers.l Before cutting or splicing a fiber, ensure that the fiber is disconnected from the optical

source. After disconnecting the fiber, cap to the fiber connectors.

1.6.5 MicrowaveWhen installing and maintaining the equipment of Huawei, follow the safety precautions ofmicrowave to ensure the safety of the human body and the equipment.

WARNINGStrong radio frequency can harm the human body.

When installing or maintaining an aerial on the tower or mast that is installed with multipleaerials, switch off the transmitter in advance.

1.7 Working at HeightsThis topic describes safety precautions for working at heights.

WARNINGWhen working at heights, be cautious to prevent objects from falling down.

The requirements for working at heights are as follows:

l The personnel who work at heights must be trained.l Carry and handle the operating machines and tools with caution to prevent them from falling

down.l Safety measures, such as wearing a helmet and a safety belt, must be taken.



10

l Wear cold-proof clothes when working at heights in cold areas.l Check all lifting appliances thoroughly before starting the work, and ensure that they are

intact.

1.7.1 Hoisting Heavy ObjectsThis topic describes the safety precautions for hoisting heavy objects that you must follow wheninstalling, operating, and maintaining Huawei devices.

WARNINGWhen heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.

l Only trained and qualified personnel can perform hoisting operations.l Before hoisting heavy objects, check that the hoisting tools are complete and in good

condition.l Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object or

wall with good weight-bearing capacity.l Issue orders with short and explicit words to ensure correct operations.l Ensure that the angle between the two cables is less than or equal to 90 degrees during the

lifting, as shown in Figure 1-1.

Figure 1-1 Hoisting heavy objects



11

1.7.2 Using LaddersThis topic describes safety precautions for using ladders.

Checking Laddersl Before using a ladder, check whether the ladder is damaged. After checking that the ladder

is in good condition, you can use the ladder.l Before using a ladder, you should know the maximum weight capacity of the ladder. Avoid

overweighing the ladder.

Placing LaddersThe proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the ladderwith an angle square or your arms, as shown in Figure 1-2. When using a ladder, to prevent theladder from sliding, ensure that the wider feet of the ladder are downward, or take protectionmeasures for the ladder feet. Ensure that the ladder is placed securely.

Figure 1-2 Slanting a ladder

Climbing Up a LadderWhen climbing up a ladder, pay attention to the following points:

l Ensure that the center of gravity of your body does not deviate from the edges of the twolong sides.

l Before operations, ensure that your body is stable to reduce risks.l Do not climb higher than the fourth rung of the ladder (counted from up to down).

If you want to climb up a roof, ensure that the ladder top is at least one meter higher than theroof, as shown in Figure 1-3.



12

Figure 1-3 Ladder top being one meter higher than the roof

1.8 Mechanical SafetyThis topic describes safety precautions for drilling holes, handling sharp objects, operating fans,and carrying heavy objects.

Drilling Holes

WARNINGDo not drill holes on the cabinet without prior permission. Drilling holes without complyingwith the requirements affects the electromagnetic shielding performance of the cabinet anddamages the cables inside the cabinet. In addition, if the scraps caused by drilling enter thecabinet, the printed circuit boards (PCBs) may be short-circuited.

l Before drilling a hole on the cabinet, remove the cables inside the cabinet.l Wear an eye protector when drilling holes. This is to prevent eyes from being injured by

the splashing metal scraps.l Wear protection gloves when drilling holes.l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,

clean up the metallic scraps.

Sharp Objects

WARNINGWear protection gloves when carrying the device. This is to prevent hands from being injuredby the sharp edges of the device.



13

Fansl When replacing parts, place the objects such as the parts, screws, and tools properly. This

is to prevent them from falling into the operating fans, which damages the fans or device.

l When replacing the parts near fans, keep your fingers or boards from touching operatingfans before the fans are powered off and stop running. Otherwise, the hands or the boardsare damaged.

Carrying Heavy Objects

Wear protection gloves when carrying heavy objects. This is to prevent hands from being hurt.

WARNINGl The carrier must be prepared for load bearing before carrying heavy objects. This is to prevent

the carrier from being strained or pressed by the heavy objects.

l When you pull a chassis out of the cabinet, pay attention to the unstable or heavy objects onthe cabinet. This is to prevent the heavy objects on the cabinet top from falling down, whichmay hurt you.

l Generally, two persons are needed to carry a chassis. It is prohibited that only one personcarries a heavy chassis. When carrying a chassis, the carriers should stretch their backs andmove stably to avoid being strained.

l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not holdthe handles of the modules installed in the chassis, such as the power modules, fan modules,and boards.

1.9 Other PrecautionsThis topic describes safety precautions for removing and inserting boards, binding signal cables,and routing cables.

Removing and Inserting a Board

CAUTIONWhen inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently toavoid distorting pins on the backplane.

l Slide the board along the guide rails.

l Do not contact one board with another to avoid short-circuits or damage.

l When holding a board in hand, do not touch the board circuits, components, connectors,or connection slots of the board to prevent damage caused by ESD of the human body tothe electrostatic-sensitive components.



14

Binding Signal Cables

CAUTIONBind the signal cables separately from the high-current or high-voltage cables.

Routing CablesIn the case of extremely low temperature, heavy shock or vibration may damage the plastic skinof the cables. To ensure the construction safety, comply with the following requirements:

l When installing cables, ensure that the environment temperature is above 0°C.l If the cables are stored in a place where the ambient temperature is below 0°C, transfer

them to a place at room temperature and store the cables for more than 24 hours beforeinstallation.

l Handle the cables gently, especially in a low-temperature environment. Do not performany improper operations, for example, pushing the cables down directly from a truck.

High Temperature

WARNINGIf the ambient temperature exceeds 55°C, the temperature of the front panel surface marked the

flag may exceed 70°C. When touching the front panel of the board in such an environment,you must wear the protection gloves.



15

2 Routine Maintenance

Routine maintenance operations are performed to detect and rectify hidden faults before thehidden faults cause damage to equipment and affect services.

Routine Maintenance Items Carried Out on the NMS

Table 2-1 Routine maintenance items carried out on the NMS

Maintenance Item RecommendedMaintenanceCycle

Remarks

7.1.1 Checking the NE Status(U2000)

Every day -

7.1.3 Browsing Current Alarms(U2000)

Every day -

7.1.5 Browsing History Alarms(U2000)

Everyweek

-

7.1.17 Browsing Abnormal Events(U2000)

Everyweek

-

7.1.7 Browsing CurrentPerformance Events(U2000)

Everyweek

-

7.1.9 Browsing History PerformanceEvents(U2000)

Everyweek

-

7.1.14 Browsing HistoricalPerformance Data of a Radio Link(Web LCT)

Everyweek

-

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 2 Routine Maintenance


16

Field Maintenance Items for Indoor Equipment

Table 2-2 Field maintenance items for indoor equipment

Maintenance Item RecommendedMaintenance Cycle

Remarks

Checking thetelecommunications room

Every two months -

Maintaining the environmentof outdoor cabinets

Half a year -

Field Maintenance Items for Outdoor Equipment

Table 2-3 Field maintenance items for outdoor equipment

Maintenance Item RecommendedMaintenance Cycle

Remarks

Checking the appearance ofthe OptiX RTN 310a

Half a year Perform a complete checkafter a level-8 or higher-levelhurricane, an earthquake, orother unexpectedcircumstances.

Checking the appearance andazimuth of the antenna

Half a year

Checking the appearance ofthe hybrid coupler

Half a year

Checking the appearance andconnection of the flexiblewaveguide

Half a year

Checking the appearance andconnection of outdoor cables

Half a year

NOTE

a: An area close to a pollution source refers to the area that covers a radius within any of the followingvalues:

l 3.7 km away from salty waters (such as an ocean and salty water)

l 3 km away from severe pollution sources (such as iron refinery works, and coal mines)

l 2 km away from intermediate pollution sources (such as chemical plants, rubber processing works, andelectroplating workshops)

l 1 km away from light pollution sources (such as food processing works, leather working plants, andheating boilers).

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 2 Routine Maintenance


17

3 Emergency Maintenance Guide

About This Chapter

3.1 Definition of EmergencyFor the microwave equipment, an emergency situation is depicted as a situation where themicrowave services are interrupted.

3.2 Purposes of Emergency MaintenanceEmergency maintenance operations are performed to restore the services quickly. This isdifferent from troubleshooting, whose purposes are to locate and rectify the faults.

3.3 Procedure for Emergency MaintenanceThe procedure of emergency maintenance consists of a main procedure and a sub-procedure thathandles faults on site.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 3 Emergency Maintenance Guide


18

3.1 Definition of EmergencyFor the microwave equipment, an emergency situation is depicted as a situation where themicrowave services are interrupted.

3.2 Purposes of Emergency MaintenanceEmergency maintenance operations are performed to restore the services quickly. This isdifferent from troubleshooting, whose purposes are to locate and rectify the faults.

3.3 Procedure for Emergency MaintenanceThe procedure of emergency maintenance consists of a main procedure and a sub-procedure thathandles faults on site.

NOTE

In the case of emergency events, the customers in China can contact the 24-hour technical support center ofHuawei at 400-830-2118, and the customers in areas outside China can contact the local Huawei offices.



19

Main Process of Emergency Maintenance

Figure 3-1 Main process of emergency maintenance

Start

End

Yes

Yes

No

No

Yes

Yes

No

Yes

No

1

5

Can the NMSconnect to the NE andcan alarms be cleared

using the NMS?

2

4

3

No

Query NE status andalarms by using the NMS.

Clear the alarm.

Rectify the fault onsite.

Is the servicerestored?

Contact Huaweiengineers.

Go to thenext step.


Are servicesinterrupted by external

causes?

Contact relateddepartments to handle

the problem.

Is therean incorrectoperation?

Undo the operation.

Check thetroubleshooting result.



20

Table 3-1 Description of the main process of emergency maintenance

Mark Description

1 The common maloperations are as follows:l Modifying the data configurationsl Loopbackl Muting the radio transmitterl Shutting down the laserl Resetting the NEl Loading the software

2 Check whether any external fault occurs (for example, the power supply orthe service equipment such as base stations are faulty, or the environment ofthe equipment room is abnormal).

3 Checking the NE statusl If the NE is unreachable to the NMS,

1. Check the status of the upstream NE. Clear alarms reported on theupstream NE. Alarms on the upstream NE may cause downstream NEsto be unreachable to the NMS.

2. If the fault cannot be rectified by using the NMS, follow instructionsin Figure 3-2 to handle the fault on site.

l If the NE is reachable to the NMS, browse the current alarms, analyzethe alarm causes, and check whether the alarms need to be handled on site.

NOTEBefore handling the alarms on site, prepare desired spare parts and NE configurationdata. The NE configuration data could be the network planning parameters or backupNE database.

If the protection trail is available, switch the services to the protection trail, thereforeminimizing the network interruption duration.

4 Generally, the following alarms can be cleared by using the NMS:l RADIO_MUTE, LOOP_ALM, MW_CFG_MISMATCH,

MW_CONT_WAVEl ETH_CFM_UNEXPERI, ETH_EFM_LOOPBACK

5 After rectifying the fault, proceed as follows:1. Check the alarms and ensure that the system is running smoothly.2. Arrange personnel to watch and guard the system during the peak service

hours, and be sure to solve the problems promptly, if any.3. Fill in the sheet for on-site operations, record the fault symptoms and

handling results, and then send them to Huawei. Table 3-2 shows the sheetfor on-site operations.



21

Table 3-2 Sheet for on-site operations

Maintained on Maintenance Personnel

Actual Step Step in the WholeProcedure

Handling Result Remarks



22

On-Site Fault Handling Sub-Process

Figure 3-2 On-site fault handling sub-process

No

Yes

Yes

No

Yes

No

Yes

No

Yes

No

Yes

Other alarms?

End

Start

1

2

5

6

No

7

3

No

Yes4

Obvious equipmentdamage?

Repair or replacethe equipment.

Browse alarms locallyby using the LCT

Equipment alarm?

Radio link alarm?

Go to thenext step.


Is the powersystem faulty? Rectify the fault.

Rectify the fault.

Rectify the fault.

Clear the alarms.

Rectify the fault.Is the

interconnectedequipment

faulty?

Troubleshoot the fault byperforming loopbacks sectionby section and replacing the

suspected faulty parts.



23

Table 3-3 On-site fault handling sub-process

Comment Description

1 The process are as follows:1. If a PI device is used to supply power to the OptiX RTN 310, check

whether the PI indicator states are correct.If the PI indicator states are normal, skip to the next step on the processflow.

2. Check whether the circuit breaker on the power supply device connectedto the OptiX RTN 310 is disconnected.If the circuit breaker is automatically disconnected, identify the cause(such as short circuits or insufficient fuse capacity), and handle the faultaccordingly.

3. Check whether the power supply equipment is functional.NOTE

For the OptiX RTN 310, the rated voltage of the input power is -48 V, the allowed powerrange is -38.4 V to -57.6 V, the fuse capacity is proposed to be 6 A.

2 Obvious equipment damages include:l The outdoor equipment is damaged or tilts, or cables are disconnected.l The indoor equipment is damaged or wet, or cables are disconnected.

3 The operations are as follows:1. Connecting the Web LCT to the Equipment2. Creating NEs Using the Search Method3. Logging In to an NE4. 7.1.3 Browsing Current Alarms(U2000)

4 Equipment alarms include:l HARD_BAD, POWER_ALM, TEMP_ALARMl RADIO_TSL_HIGH, RADIO_TSL_LOWl ETH_LOSl XPIC_LOS

5 Radio link alarms include:l MW_LOF, MW_LIM, MW_BER_EXCl RADIO_RSL_HIGH, RADIO_RSL_LOWl MW_CFG_MISMATCHl AM_DOWNSHIFT

6 Alarms of other types do not cause service interruption and NE unreachabilityat the same time. Handle the alarms (if any) according to the alarm referencedocument.

7 If a service fault is not caused by a fault on the OptiX RTN 310, check forand handle faults on the opposite equipment.



24

Comment Description

8 Locate the fault by performing loopbacks section by section, replace the faultyparts, and check whether the fault is rectified.l The OptiX RTN 310 supports software loopbacks including inloops at

Ethernet ports and inloops/outloops at IF ports.l Hardware loopbacks include optical fiber loopbacks and network cable

loopbacks.



25

4 Troubleshooting

About This Chapter

This guide describes the general troubleshooting procedure and the methods of rectifying thecommon faults.

4.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomena. The customers in Chinacan contact our 24-hour technical support center at 400-830-2118, and the customers in areasoutside China can contact the local Huawei offices.

4.2 Troubleshooting the Radio LinkRadio link faults include radio link unavailability and radio link performance degrade.

4.3 Troubleshooting Ethernet Service FaultsAn Ethernet service fault may be the Ethernet service interruption or Ethernet servicedeterioration.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 4 Troubleshooting


26

4.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomena. The customers in Chinacan contact our 24-hour technical support center at 400-830-2118, and the customers in areasoutside China can contact the local Huawei offices.

General Troubleshooting Procedure

Figure 4-1 General troubleshooting procedure

Start

Record fault symptoms

Diagnose, locate andhandle the fault

Is the faultrectified?

Report to Huawei

Work outsolutions together


Write atroubleshooting report

End

Rectify external faults

No

Yes

YesNo

No

Caused byexternal factors?

Yes

1

3 4

2



27

Table 4-1 General troubleshooting procedure

CommentNo.

Description

1 When recording the fault phenomena, make a true and detailed record of theentire process of the fault. Record the exact time when the fault occurs andthe operations performed before and after the fault occurs. Save the alarms,performance events, and other important information.You can use the click-to-collect function on the U2000 to collect data.

2 For the OptiX RTN 310, the common external cause is a fault on the powersupply.

3 l If a radio link is faulty, follow instructions in 4.2 Troubleshooting theRadio Link to handle the fault.

l If an Ethernet service is faulty, follow instructions in 4.3 TroubleshootingEthernet Service Faults to handle the fault.

l For faults of other types, handle alarms in descending order of theirseverities according to the alarm reference document.

4 To provide feedbacks or obtain technical support, customers in China cancontact the 24-hour technical support center at 400-830-2118, and thecustomers in areas outside China can contact the local Huawei offices.

4.2 Troubleshooting the Radio LinkRadio link faults include radio link unavailability and radio link performance degrade.

Radio Link FaultsRadio link faults are classified into:

l Equipment faults, including outdoor component faults, cable faults, and power supply faultsl Propagation faults, including fading, interference, and poor line of sight (LOS)l Poor construction quality, including poor antenna/component installation, poor grounding,

and poor waterproofing



28

Figure 4-2 Radio link faults

HardwareFaults

Causes of radiolink faults

Propagationfaults

Interference Fading Poor LOS

Externalinterference

Over-reachinterference

Rainfading

Multipathfading

Reflection

LOS notachieved

Near-fieldblocking

Poor constructionquality

Antennainstallation

Cables

Antennasnot aligned

Antennasloosened or

offset

Poorgrounding

Poorwaterproofing

Equipmentfaults

Powerfaults

Damagedcable

components

Fading Phenomena and Causes

During microwave network maintenance, link fading is the main cause for radio link faults. Linkfading is more difficult to locate and handle than hardware faults.

Table 4-2 Fading phenomena and causes

Fading Type Fading Phenomena Fading Cause

Classified by RSL

Downfading

The RSL is lower than the RSLafter free space fading. Thedifference can be tens ofdecibels.

l Multi-path fadingl Duct-type fadingl Rain fading

Upfading

The RSL is higher than the RSLin the free space. The differencecan be 10-odd decibels.

l Interferencel Long delay caused by terrain

reflection

Classified byfadingduration

Fastfading

The fading lasts from severalmilliseconds to tens of seconds.Generally, fast fading is causedby multipath fading. It occursperiodically. To be specific, fastfading occurs in the period from18:00 to 20:00 of a day or in acertain season of a year.

l Multi-path fadingl Duct-type fadingl Long delay caused by terrain

reflection



29

Fading Type Fading Phenomena Fading Cause

Slowfading

The fading lasts from tens ofseconds to several hours.

l Generally, slow up fading iscaused by interference.

l Slow down fading is causedby rain, and therefore is alsocalled rain fading. Rainfading occurs on linksworking at a frequency of 10GHz or in areas where heavyrain occurs.



30

Troubleshooting Procedure



31

Figure 4-3 Procedure for troubleshooting the radio link

Start

Does up-fading occur?

Is there anincorrect operation? Undo the operation.

Yes1

2

3

4

5

6

7

8

9

End

Hardwarealarms exist? Rectify equipment faults.

Co-channel or adjacent-channel interference

Long delay causedby terrain reflection

The link is blocked.

The antennas are offset.

Passive components likehybrid couplers or flexible

waveguides are faulty.

Rain fading

Multipath fading

Terrain reflection

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

Is the RSL valuealways less than the

designed value?

Analyze the historical RSLrecords and the current

RSL value

Are there IF or RFalarms on the link?

Troubleshoot the fault asa non-radio link fault.

Does the fault occurregularly?

Troubleshoot the fault byreplacing the suspected

faulty parts.

Is the fault rectified?

Is it raining when thefault occurs?



32

Table 4-3 Description of the procedure for troubleshooting the radio link

Mark Description

1 Check whether any maloperations have been performed:l Shutting down the power supply, which caused the local or remote NE to be

unreachable to the NMSl Muting the radio transmitter, which caused the RADIO_MUTE alarm to be

reportedl Looping back IF ports, which caused the LOOP_ALM alarm to be reportedl Configuring incorrect radio link data, which caused the

MW_CFG_MISMATCH alarm to be reportedl Enabling an AM self-checkl Enabling a PRBS testl Enabling IF consecutive wave output

2 Hardware fault alarms include:l HARD_BADl RADIO_TSL_HIGH, RADIO_TSL_LOWWhen a hardware fault occurs, replace the OptiX RTN 310.

3 IF and RF alarms include:l MW_LOF, MW_LIM, MW_RDIl MW_BER_EXC, MW_BER_SD, MW_FEC_UNCORl RADIO_RSL_HIGH, RADIO_RSL_LOWl RADIO_RSL_BEYONDTHl AM_DOWNSHIFT

4 RSL is the major reference for locating and handling propagation faults. Followinstructions in 7.1.14 Browsing Historical Performance Data of a Radio Link(Web LCT) and 7.1.13 Browsing Current Performance Events of the radio link(Web LCT) to browse and analyze the historical RSL records and the current RSLvalue.



33

Mark Description

5 If the RSL value is larger than the current receiver sensitivity but the radio link isstill unavailable or degrades, up fading occurs. Mute the opposite NE and check theRSL at the local NE.l If the RSL value is larger than –90 dBm, there may be co-channel interference

that affects long-term availability and error-second performance of the system.Follow instructions in 7.9 Scanning Interfering Signals or use a frequencyspectrum analyzer to locate the possible interfering frequencies.– If a third-party RF device is the interfering source, contact the local frequency

spectrum management department to clear the interference.– If interference is caused due to improper route planning, modify the

frequency plan to minimize the interference impacts.l If the RSL value is not larger than –90 dBm, there may be a fault caused by

terrain reflection. Check whether there are rivers or lakes on the propagationtrail.If there is an intensively reflective terrain, adjust the mounting height of theantenna to change the link elevation, therefore minimizing reflection impacts.Alternatively, replan the route to avoid the intensively reflective terrain.

5 If the RSL value had been smaller than the designed value for a long time beforethe fault occurred, the propagation trail is faulty. Proceed as follows:l Check whether the antenna connection is loose or the antenna is unaligned. If

yes, re-align the antenna.l Check whether there are any blocks in the radio transmission trail or in the near

field of the antenna. If yes, adjust the mounting height of the antenna to avoidblocks, replan the radio link route.

l Check whether loss increases because the antenna, hybrid coupler, and flexiblewaveguide are not intact or are wet. If yes, replace the faulty components.

6 If a radio link fault occurred in poor weather conditions (such as rainy, snowy, orfoggy) and was rectified after the conditions disappeared, the fault cause wasweather fading. For a fault caused by weather fading, check whether the link fadingmargin is insufficient.1. Calculate the actual link availability. Calculate the total link fault time within

one year or half a year. Calculate the actual link availability using the followingformula: <Link availability> = <Total fault time>/<Calculation period>.l If the actual link availability is lower than the designed value by an order of

magnitude, the link fading margin is insufficient. Re-plan the radio linkparameters.

l If the difference between the actual link availability and the designed valueis small, no special handling operations are required.

2. Before re-planning a radio link, check whether the rain zone parameters, therefractivity gradient, and the planning algorithm are incorrect. The practicablemeasure could be as follows:l Increase the transmit power or replace the original antenna with a new one

having a larger diameter to increase the system gain and the fading margin.l Use a frequency band on which rain fading has smaller impacts.



34

Mark Description

7 If the receive power fluctuates greatly and fast (by more than 10 dB or several 10dB within several seconds or several 10 seconds), fast fading occurs.Fast fading may occur due to:l Multi-path fading: Faults occur periodically, for example, at the day-and-night

alternating time period.l Duct-type fading: random fast fadingTo handle fast fading, proceed as follows:l Increase the path inclination: That is, adjust the antenna mount heights at both

ends to increase the height differences between the antennas at both ends.l Reduce surface reflection. For apparent strong reflection surfaces, for example,

large areas of water, flat lands, and bold mountain tops, adjust antennas to movereflection points out of the strong reflection areas or mask the reflection by usinglandforms.

l Reduce the path clearance. With LOS conditions guaranteed, lower antennamount heights as much as possible.

8 If all preceding actions cannot rectify the fault, replace the OptiX RTN 310 at bothends. Then, check whether services are functional. If the fault persists, replan theradio link by changing the operating frequency, using antennas with a largerdiameter, changing the antenna heights, or changing the routes.

4.3 Troubleshooting Ethernet Service FaultsAn Ethernet service fault may be the Ethernet service interruption or Ethernet servicedeterioration.

Fault PhenomenaThe Ethernet service interruption indicates that the Ethernet service is interrupted. The Ethernetservice deterioration indicates that the Ethernet service is abnormal. For example, the networkaccess speed is low, the equipment delay is long, the packet loss occurs, or incorrect packetsexist in the received or transmitted data.

Table 4-4 Common faults of Ethernet services

Symptom Alarm

Ethernet services areinterrupted.

HARD_BAD, TEMP_ALARM

ETH_LOS, ETH_EFM_LOOPBACK, LOOP_ALM

LASER_MOD_ERR

Ethernet services aredegraded.

HARD_BAD, TEMP_ALARM

FLOW_OVER, LAG_MEMBER_DOWN

AM_DOWNSHIFT



35

Fault Causesl The possible human factors are as follows:

– An Ethernet board loopback or a transmission line loopback occurs.– The parameter settings of the Ethernet ports, such as the port enabled state, working

mode, and flow control, are different from the parameter settings of the Ethernet portson the interconnected equipment.

– The service configuration is incorrect.l The equipment at the local end is faulty.l A link fault or bit errors occur.l When the AM function is enabled, the Ethernet service bandwidth decreases due to the

downward AM switch.l The interconnected equipment is faulty.l The network cable is faulty.l The external electromagnetic interference is severe.



36

Troubleshooting Procedure

Figure 4-4 Procedure for troubleshooting Ethernet service faults

End

Yes

No

微波链路

No

Yes

An Ethernet alarm?

Yes

No

Yes

Start

Incorrect operation?

No

Yes

An equipment alarm or radio link

alarm?

No

No

Any abnormal RMON performance

events?

Clear the alarm

Clear the alarm

Cancel this operation

Query the port and service traffic and

analyze the fault causes

Troubleshoot the fault according to the flow of

handling RMON performance events

Troubleshoot equipment faults by performing loopbacks

section by section or replacing parts

Proceed with the next step

3

2

1

4

5

Is the fault rectified?

Table 4-5 Description of the procedure for troubleshooting Ethernet service faults

No. Description

1 Check the following points:l Whether a loopback is set for the Ethernet portl Whether a loopback is set for the transmission linel Whether the parameter settings of the Ethernet port, such as the port

enabled state, working mode, and flow control, are the same as theparameter settings of the Ethernet port on the interconnected equipment

l Check whether the Ethernet protocol and the Ethernet serviceconfiguration (especially the attributes of the Ethernet port) are correct.



37

No. Description

2 Pay special attention to the following equipment alarms:l POWER_ALM, HARD_BAD, TEMP_ALARMl LASER_MOD_ERR, ETH_LOSPay special attention to the following radio link alarms:l RADIO_RSL_HIGH, RADIO_RSL_LOW, RADIO_TSL_HIGH,

RADIO_TSL_LOWl MW_LOF, MW_LIM, MW_BER_EXC, MW_BER_SD,

MW_FEC_UNCOR, MW_RDIl AM_DOWNSHIFT

3 Pay special attention to the following alarms:l ETH_LOS, LAG_DOWN, LAG_MEMBER_DOWNl ETH_NO_FLOW, FLOW_OVER

4 Query the Ethernet traffic, bandwidth, or bandwidth utilization ofEthernet ports. Diagnose faults by analyzing the traffic rate at the Ethernetports.l If the receive rate of an Ethernet port is out of range, the peer equipment

is faulty.l If the transmit rate of an Integrated IP radio port is close to or equal to the

service bandwidth supported by the current IF working mode, the servicebandwidth of the radio link is insufficient. Contact network planningpersonnel to replan the service bandwidth for a radio link. If the replannedservice bandwidth exceeds the limit specified by the license, apply toHuawei for a license that allows higher service bandwidth.

l If the traffic at the ingress port is markedly different from the traffic at theegress port (for an OptiX RTN 310, the ingress port is usually an Ethernetport and the egress port is usually an Integrated IP radio port), checkwhether the service and QoS configurations on the equipment are proper.

l If the transmitted traffic is equal to the received traffic, query the trafficon the same port in each VLAN to check whether bandwidth preemptionoccurs.

5 For RMON performance events, see the C RMON Event Reference.



38

Figure 4-5 Procedure for troubleshooting an RMON performance event

2

End

Yes

No

3

1

5

4

Rectify the faultof line bit errors

Check the workingmode of the port

Handle the problem onexcessive broadcast

packets

Rectify the fault of theinterconnected equipment

Modify the MTU value


Proceed withthe next step

Start

No

Yes

Yes

Yes

No

No

No

Yes

No

Yes

View the statistics gro upperformance on an Ethernet port

Is there anycollision or fragment?

Are broadcastpackets excessive?

Is there anyFCS error?

Use a meter toperform the test

Is the test passed?

Is it a MTU settingproblem?

Rectify the equipment fault byloopback section by section

or replacing the board

Table 4-6 Description of the procedure for troubleshooting an RMON performance event

No. Description

1 Query the real-time performance statistics of Ethernet ports.



39

No. Description

2 The troubleshooting procedure is as follows:l Check the Ethernet cable. If the Ethernet cable is not qualified, replace it

with a new one.l Change the Ethernet port that accesses the services on the Ethernet board.

If the new port does not have the RMON performance of an FCS error, itindicates that the hardware of the original port is faulty. Otherwise, thehardware of the Ethernet port on the equipment at the opposite end isfaulty.

3 Ensure that:l The negotiation results are the same at both ends if both ends use the

autonegotiation mode.l The working rate and full-duplex/half-duplex settings are the same at both

ends if the working modes at both ends are set manually.l The working modes at both ends are autonegotiation or are set manually.

4 Find out the cause of excessive broadcast packets (check whether loopbacksare configured at Ethernet ports by referring to 7.4.1 Setting Loopbacks forEthernet Ports, or check whether the VB filtering table is configuredcorrectly by referring to Managing a Native Ethernet Service), and rectify thefault. If the fault is caused by the opposite equipment, you can reduce thenumber of broadcast packets by setting a broadcast packet suppressionthreshold at the Ethernet port on the local equipment.

5 The maximum frame length that is set for a port should be longer than themaximum transmission unit (MTU) of the network.The MTU must be set according to the network plan. For the OptiX RTN310, the MTU is equal to the total length of the maximum payload,encapsulation labels, and frame header. The maximum payload length isusually 1500 bytes. You can obtain the MTU supported by the network usinga test instrument.



40

5 Part Replacement

About This Chapter

Part replacement is a method frequently used to locate faults. The replacement operation variesaccording to the specific part type.

5.1 Replacing an OptiX RTN 310When an OptiX RTN 310 is being replaced, services on it are interrupted.

5.2 Replacing an SFP ModuleWhen a small form pluggable (SFP) module at a port is being replaced, unprotected services onthe port are interrupted.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 5 Part Replacement


41

5.1 Replacing an OptiX RTN 310When an OptiX RTN 310 is being replaced, services on it are interrupted.

Prerequisitesl You are aware of the impact of replacing an OptiX RTN 310.

l The spare OptiX RTN 310 is at hand, whose model is the same as that of the OptiX RTN310 to be replaced.

l The RTN.CER file of the new NE has been copied to the root directory of the USB flashdrive.

NOTE

A RTN.CER file, which stores the account and password information at the system administration level(the password is MD5 encrypted), is generated by the system administrator of a network managementcenter using dedicated tools.

l NE data has been obtained.

– The backup NE data has been imported to a laptop where the Web LCT is installed, ifthere is a backup of the NE database on the NMS.

– The network plan document has been obtained if there is no backup of the NE databaseon the NMS.

Tools, Equipment, and Materialsl Wrench (Adjustable wrench, Hex key)

l Silicon

l Waterproof tape

l USB flash drive

The USB flash drive must be compatible with the OptiX RTN 310 and have a capacity noless than 4 GB.

l Web LCT

Precautionsl If OptiX RTN 310s are installed on a hybrid coupler, power off only the OptiX RTN 310

to be replaced, but do not power off or mute the other OptiX RTN 310. This can preventservices from being affected. The port of the hybrid coupler ejects little microwaveradiation, meeting the safety standards for microwave radiation.

l Do not damage the paint of the OptiX RTN 310 during the replacement. If the paint isdamaged, repaint the damaged areas.

Procedure

Step 1 Optional: If the NE is running, back up the NE data to the USB flash drive.

1. Set USB Access Control to Enabled on the Web LCT.

2. Insert the blank USB flash drive into the USB port on the OptiX RTN 310.



42

The indicator beside the USB port is blinking green during the data backup. The backupmay last for about 2 minutes based on the content to be backed up. The indicator will besteady green after the data backup is complete.

3. Remove the USB flash disk after the data backup is complete.

Step 2 Power off the OptiX RTN 310.l If power is supplied to the OptiX RTN 310 by the power injector (PI), switch off the circuit

breaker, on the power cabinet, connected to the PI, or disconnect the fuse on the powercabinet.

l If power is supplied to the OptiX RTN 310 through a DC port, switch off the circuit breaker,on the power cabinet, to which the DC power cable is connected, or disconnect the fuse onthe power cabinet.

Step 3 Remove the faulty OptiX RTN 310.1. Remove all the cables connected to the OptiX RTN 310.

NOTE

Remove XPIC cables by pulling rings attached on them.

2. Loosen the four captive screws in a diagonal sequence, and remove the OptiX RTN 310from the antenna, hybrid coupler, or mounting bracket.

Step 4 Ensure that the model of the spare OptiX RTN 310 is the same as that of the OptiX RTN 310 tobe replaced.

Step 5 Install the spare OptiX RTN 310 by following instructions in the OptiX RTN 310 QuickInstallation Guide. The main steps are as follows:1. Verify the polarization of the OptiX RTN 310 and change the polarization if it is necessary,

to ensure the polarization of the OptiX RTN 310 is the same as that of the antenna or hybridcoupler/OMT.

2. Mount the OptiX RTN 310 on the antenna, hybrid coupler, or mounting bracket.3. Tighten the four captive screws in a diagonal sequence.4. Connect cables to the OptiX RTN 310 and waterproof them.

Step 6 Connect the fuse or switch on the circuit breaker on the power cabinet of the OptiX RTN 310.The system indicator on OptiX RTN 310 is blinking green when the OptiX RTN 310 is beingpowered on and started, and is steady green after the OptiX RTN 310 is started.

Step 7 Restore the NE data according to the onsite situations.l If you have performed Step 1 to back up the NE data on the USB flash disk, restore the NE

data using the backup data.

1. Set USB Access Control to Enabled on the Web LCT.2. Insert the USB flash disk with the NE data backup into the USB port on the OptiX

RTN 310.The indicator beside the USB port is blinking green during the data restoration Therestoration may last for 2 to 12 minutes based on the content to be restored. Theindicator will be steady green after the data is restored.

3. After the data is restored, remove the USB flash drive.l If you have no NE data backup on the USB flash disk.

1. If there is a backup file in the NMS, restore the NE database using the backup file.



43

2. See Changing an NE ID and Setting NE Communication Parameters to modify theNE ID and IP.

l If there is no backup file, re-configure the NE data by referring to the CommissioningGuide and network plan document.

Step 8 Query the current alarms on the OptiX RTN 310. Ensure that the faults disappear and noalarm is generated after the replacement.

----End

5.2 Replacing an SFP ModuleWhen a small form pluggable (SFP) module at a port is being replaced, unprotected services onthe port are interrupted.

Prerequisitesl You are aware of the impact of replacing an SFP module.l You are aware of the position of the SFP module to be replaced.l You are aware of whether protection has been configured for services on the SFP module

to be replaced. If no protection is configured, the services will be interrupted during thereplacement.

l A spare SFP module with the same version and model as the SFP module to be replaced isavailable. To obtain information about the SFP module to be replaced, query the boardmanufacturing information.

Tools, Equipment, and Materialsl ESD wrist strapl U2000

Precaution

DANGERWhen handling optical fibers, do not stand close to, or look into the optical fiber outlet directlywithout eye protection.

Procedure

Step 1 Remove the cables connected to the SFP module.

Step 2 Remove the SFP module.



44

Step 3 Ensure that the model of the spare SFP module is the same as that of the SFP module to bereplaced.

Step 4 Insert the spare SFP module.

Step 5 Connect cables to the SFP module.

Step 6 Query the current alarms.Alarms on the SFP module have been cleared.

----End



45

6 Database Backup and Restoration

About This Chapter

The OptiX RTN 310 supports database backup and restoration through the NMS.

6.1 NE DatabaseAn NE database stores communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure, to facilitate data query and modification andto ensure that the data can be restored after the NE is reset.

6.2 Backing Up the Database ManuallyNE configuration data is stored in the database of an NE. To prevent the database from beingdamaged due to hardware faults or potentially service-affecting operations such as upgradingsoftware, you need to manually back up the database periodically and before these operations.

6.3 Setting the Database Backup Policy

6.4 Restoring the Database by NMSIf the database is damaged, you can restore the NE database by using the database file that issaved previously.

6.5 Recovering Databases from a USB Flash DriveWhen NE data is lost or becomes abnormal and NE DCN communication fails, you can recoverNE databases from a USB flash drive.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 6 Database Backup and Restoration


46

6.1 NE DatabaseAn NE database stores communication data, security data, alarm data, performance data, andconfiguration data of an NE in a certain structure, to facilitate data query and modification andto ensure that the data can be restored after the NE is reset.

NE Database TypeThree types of NE databases are available:

l Memory database (MDB)The data in the MDB varies according to the configuration and is lost when the systemcontrol unit is reset or when the NE is powered off.

l Dynamic random database (DRDB)The DRDB automatically stores the data that is checked successfully. The DRDB is residentin the reserved memory. Hence, the data in the DRDB is not lost when a warm reset isperformed on the system control unit. The data, however, is lost when a cold reset isperformed on the system control unit or when the NE is powered off.

l Flash database (FDB)The FDB includes FDB0 and FDB1. The FDB is resident in the flash memory on the board.Hence, the data in the FDB is permanently stored.

NE Database BackupNE configuration data, after being delivered to the system control unit, is stored in the MDB.Upon successful verification of the configuration data, the system control unit copies the datafrom the MDB to DRDB and delivers the data to boards.

Two modes are available to back up DRDB data to the FDB:

NOTE

During back up DRDB data to the FDB process, do not recover or backup NE data by USB flash drive.

l An NE backs up DRDB data to the FDB within five minutes after NE configuration datais modified.

l An NE backs up DRDB data to the FDB every 24 hours.

The following modes are available to back up FDB data:

l Upon a scheduled backup of DRDB data to the FDB, the NE backs up FDB data to adedicated partition of the flash memory (other than FDB0 and FDB1).

l On the NMS, FDB data can be backed up to an NMS server manually or at specifiedintervals.

l If a USB flash drive is connected to the USB port and the FDB data in the flash memoryis later than that in the USB flash drive, the NE backs up FDB data from flash memory to\db in the USB flash drive.

NE Database Restorationl When an NE is warm reset, the system control unit checks whether configuration data is

available in the DRDB. If configuration data is available in the DRDB, the system control



47

unit restores data from the DRDB. If the configuration data in the DRDB is damaged, thesystem control unit restores data from FDB0 and FDB1.

l When the NE is cold reset, the system control unit restores data from FDB0 and FDB1.l When the data in both FDB0 and FDB1 is corrupted, data can be restored from the dedicated

partition of the flash memory.l If a USB flash drive is connected to the USB port and the FDB data in the USB flash drive

is newer than that in the flash memory, the NE backs up FDB data from the USB flash driveto a dedicated directory in the flash memory.

NOTE

During the database recovering by the NMS, do not recover or backup data by USB flash drive.

6.2 Backing Up the Database ManuallyNE configuration data is stored in the database of an NE. To prevent the database from beingdamaged due to hardware faults or potentially service-affecting operations such as upgradingsoftware, you need to manually back up the database periodically and before these operations.

Prerequisitesl You must be an NM user with NE operator authority or higher.l You have logged in to the NE.

Tools, Equipment, and MaterialsU2000

PrecautionsNOTE

During the database backup by the NMS, do not recover or backup data by USB flash drive.

Procedure

Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.

Step 2 In NE View, click Find.

Step 3 In the Find NE dialog box, set the search conditions and search for the NE that requires databasebackup.

Step 4 Select the NE whose database needs to be backed up, and click Backup.

NOTE

By holding down Ctrl, you can select multiple NEs to back up their data at one time.

Step 5 Set the data backup path to NMS Server or NMS Client according to the requirements.

NOTE

If NMS Client is selected, you can click to set the path in which the client data is stored.

----End



48

6.3 Setting the Database Backup Policy

6.3.1 Setting the User-Defined Backup PolicyThrough this task, you can set the backup policy for a specific NE.

Prerequisitesl You must be an NM user with NE monitor authority or higher.l You must log in to the NE.


NOTE

The Web LCT does not support this operation.

Background InformationEach NE has a default data backup policy.

l Database packages are backed up once at 2:00.l The default backup policy is disabled by default.l A maximum of five database packages can be backed up at a time.l Data changes do not trigger any backup operations.

Procedure

Step 1 Choose Administration > NE Software Management > NE Backup Policy Managementfrom the Main Menu.



49

Then, the NE Backup Policy Management dialog box is displayed.

Step 2 In Auto Backup Policy window, set NE type.The version, name, and IP address of the selected NE are displayed.

Step 3 Click New Policy.

Step 4 Optional: Click to import the information of the NEs.

Step 5 Optional: Click to export the information of the NEs.The information of the selected NEs is stored in the specified location.

Step 6 In NE Table, select one or more NEs.

Step 7 Click Next.



50

Then, the Setting Policy dialog box is displayed.

Step 8 Set Policy Name, Period Backup Policy, and Period Save Policy.

NOTE

l If The Added NE's Policy Status is set to Enable, the NMS performs the backup operation withinthe specified period, day, and time.

l If The Added NE's Policy Status is set to Disable, the backup policy is still in the Disable statealthough the policy period reaches the specified period, day, and time.

Step 9 Click Advanced Settings, and set Backup Type, Max Backup Num, and ConfigurationChange Backup for a certain type of NEs.

Step 10 Click OK.

Step 11 Click OK.

----End

6.3.2 Executing the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the running state.

Prerequisites

You must be an NM user with NE monitor authority or higher.

Tools, Equipment, and Materials

U2000

NOTE


Procedure




51



Step 3 Right click the selected NE, Click Enable Backup Policy.

----End

6.3.3 Suspending the Backup Policy of the DeviceThrough this task, you can set the backup policy of a device to the suspended state.

PrerequisitesYou must be an NM user with NE monitor authority or higher.


NOTE


Procedure




52



Step 3 Right click the selected NE, Click Disable Backup Policy.

----End

6.4 Restoring the Database by NMSIf the database is damaged, you can restore the NE database by using the database file that issaved previously.

Prerequisitesl You must be an NM user with NE operator authority or higher.l NE data has been backed up.l You have logged in to the NE.




53

Precautions

CAUTIONExercise caution when activating the database because this operation may interrupt services.Activate the database within 5 minutes after the NE data is restored. Otherwise, the databaseautomatically rolls back.Ensure that the database file used for backing up the database is correct. Otherwise, services willbe interrupted.

NOTE

During the database recovering by the NMS, do not recover or backup data by USB flash drive.

Procedure

Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/Restoration from the Main Menu.

NOTE

The equivalent operations on the Web LCT are as follows:

In NE List, click .

In Login, click OK.

For the DC, the default user name is szhw and the default password is nesoft. For the license tool, the defaultuser name is lct and the default password is password. If the user name or password has been changed, use thelatest one.



54

The NE Data Backup/Restoration window is displayed.

Step 2 In NE View, click Find.Then, the Find NE dialog box is displayed.

Step 3 In the Find NE dialog box, set the search conditions to search for the NEs that need to restoredatabases.

Step 4 Click OK.

Step 5 Select the NE whose data needs to be recovered, and click Recover.

NOTE

You can select multiple NEs to recover the data at one time.



55

Then, the Recover dialog box is displayed.

Step 6 Select Browse in File Name.Then, the Select File dialog box is displayed.

Step 7 Select files from NMS Server or NMS Client, and then choose the files to be recovered. ClickOK.

Step 8 In the Recover dialog box, click Start.

Step 9 Click Yes in the prompt dialog box.The system starts recovering the selected data files on the specified NE.In the NE list of NE View, Operation Status indicates the progress of recovering the data.After the data is recovered, Operation Status displays a message, indicating that the operationis successful.

Step 10 In NE View, right-click the NE and choose Active Database from the shortcut menu.The Active Database dialog box is displayed.

Step 11 Click Start to start activating the database.

NOTE

If the NE transmits data services, select Deliver to Board.

Services are interrupted during the activation of databases.

In NE View, Operation Status indicates the progress of activating the database. After thedatabase is activated, Operation Status indicates that the operation is successful.

----End

6.5 Recovering Databases from a USB Flash DriveWhen NE data is lost or becomes abnormal and NE DCN communication fails, you can recoverNE databases from a USB flash drive.

Prerequisitesl You must be an NM user with NE maintainer authority or higher.l The NE database has been backed up.l You have logged in to the NE on the NMS.


USB flash drive

Procedure

Step 1 Copy the NE databases to be recovered from the NMS server to the \db directory in the USBflash drive.

NOTE

There should be no contents in the other directories of the USB flash drive.



56

Step 2 Insert the USB flash drive to the USB port on the OptiX RTN 310.

USB/RSSI/NMS

USB indicator

USB/RSSI/NMS (bottom view)

USB interface

System indicator

NOTE

During the database recovering process, do not perform operations such as data configuration, NE resets, andsoftware loading.

Step 3 Check the data-loading status based on the USB indicator.



57

Status of the USBIndicator

Data-Loading Status Operation

The indicator blinks green,goes off, blinks green, andturns steady green.

The loading ofcommissioning data iscomplete.NOTEl When the indicator is

blinking green, do notremove the USB flashdrive. Otherwise, the dataloading may be interrupted.

l After the data loading iscomplete, the NE willautomatically reset, whichtakes 2 minutes to 3minutes. After the reset iscomplete, the USBindicator and the systemindicator on the NE are bothsteady green, indicatingthat the data loading issuccessful.

l If only the script files areloaded using the USB flashdrive, the indicator blinksgreen for 1 to 2 seconds andthe NE will resetautomatically. In this case,you may fail to notice thatthe indicator has blinkedgreen because the blinkingduration is too short.

l If the script files andsoftware package are to beloaded using the USB flashdrive, the loading time maylast up to more than 10minutes.

Remove the USB flash drive.

The indicator turns off afterthe USB flash drive isinserted.

The USB flash drive is faultyand has failed to get online.NOTE

Another possible cause is thatthe USB flash drive is notproperly inserted.

l Copy the commissioningdata to another USB flashdrive.

l Repeat 2 to load the datato the NE.

The indicator blinks red. An incorrect type of USBflash drive is being used. Anerror occurred when the NEattempted to read/write theUSB flash drive.NOTE

Preparing Documents andTools lists the types of USBflash drives supported by thatthe OptiX RTN 310.

l Copy the commissioningdata to another USB flashdrive.




58

Status of the USBIndicator

Data-Loading Status Operation

The indicator is steady red. The loaded data is incorrect. Reload the data:l Save the correct NE

software andcommissioning scripts inthe correct directories ofthe USB flash drive.


----End



59

7 Supporting Task

About This Chapter

This chapter describes the common maintenance operations.

7.1 Browsing Alarms, Abnormal Events, and Performance EventsThe U2000 is used to browse alarms, abnormal events, and performance events at the networklayer. The Web LCT is used to browse alarms, abnormal events, and performance events at theNE layer.

7.2 Setting Alarm and Performance Management FunctionsThe OptiX RTN 310 supports various alarm and performance management functions.

7.3 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

7.4 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

7.5 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

7.6 Detecting Consecutive WavesThe consecutive wave detection function is used to check whether the transmit frequencydeviates.

7.7 PRBS TestThe OptiX RTN 310 supports the PRBS test function, allowing PRBSs to be transmitted tomicrowave ports.

7.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.

7.9 Scanning Interfering Signals

OptiX RTN 310 Radio Transmission SystemMaintenance Guide 7 Supporting Task


60

You can learn whether intra-frequency or inter-frequency interference exists by scanningfrequency spectra in microwave channels.

7.10 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the RF muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.

7.11 Querying Power Consumption of NEThis section describes how to query power consumption of NE.

7.12 Querying the Attributes of an Ethernet PortThis section describes how to learn about Ethernet service flow rates and physical bandwidthparameters of Ethernet ports.

7.13 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet PortsTo query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within acertain period, you need to enable the monitoring for the object before that period starts.

7.14 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization of Ethernet PortsThis section describes how to query the change curve of the traffic, physical bandwidth, orbandwidth utilization of Ethernet ports within a certain period.

7.15 End-to-End Management on Fibers, Tunnels, and PWE3 ServicesThis section describes the common maintenance operations for end-to-end management onfibers, MPLS tunnels, and PWE3 services.



61

7.1 Browsing Alarms, Abnormal Events, and PerformanceEvents

The U2000 is used to browse alarms, abnormal events, and performance events at the networklayer. The Web LCT is used to browse alarms, abnormal events, and performance events at theNE layer.

7.1.1 Checking the NE Status(U2000)You can learn about the basic information such as whether the NE fails to communicate withthe NMS and whether any alarms are reported by checking the NE status.



PrecautionsNOTE

By default, the color of the NE icon on the NMS indicates the NE status.

Procedure

Step 1 In Main Topology, select the required NE.

Step 2 In Main Topology, click .

Step 3 Click the Attribute tab.

Step 4 View the NE status and alarm status.



62



63

TIP

You can also determine the NE status based on the comparison between the NE icon and the descriptionat the Legend tab.

----End

7.1.2 Checking the NE Status(Web LCT)You can learn about the basic information such as whether the NE fails to communicate withthe NMS by checking the NE status.

Prerequisites



Web LCT

Procedure

Step 1 In NE List, check Communication Status of the NE.In normal cases, Communication Status is Normal.

Step 2 If Login Status of the NE is Not Logged In, log in to the NE.1. Select the desired NE, and choose NE Login.

The NE Login dialog box is displayed.2. Specify User Name and Password.



64

l The user name is lct by default.l The password of user lct is password by default.

NOTE

User lct has the authority at the system level.

3. Click OK.The Login Status column switches to Logged In.

Step 3 Click NE Explorer.

Step 4 Check NE STATE above NE Panel.

In normal cases, NE STATE is Running.

----End

7.1.3 Browsing Current Alarms(U2000)You can find the faults that occur on the equipment by browsing current alarms.



Procedure

Step 1 Choose Fault > Browse Current Alarm from the Main Menu.

Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.



65

1. In Severity, select the alarm severity to be queried.2. In Status, select the alarm status to be queried.3. In Type, select the alarm type.4. In Last Occurrence Time Segment, specify the alarm generation time.5. In Clearance Time Segment, specify the alarm clearance time.

Step 3 In the Filter dialog box, click the Alarm Source tab.

Step 4 Select the object to be queried.

Option Description

Browse all alarms on the NE. Select All Objects.

Browse certain alarms on the NE. 1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of Object

below NE, and click .4. Click OK.

Alarm Source displays Selected Alarm Source.

Step 5 Click OK.

Step 6 Browse the displayed alarms.



66

Step 7 Select the newly generated alarms, record the details of the alarms, and click Acknowledge.The Confirm dialog box is displayed.

Step 8 Click Yes.

Step 9 Notify the troubleshooting personnel to clear the alarms in time.For the details, see A.2 Alarms and Handling Procedures.

----End

Related InformationA current alarm refers to an alarm that is not cleared.

You can browse the network-wide alarms based on the alarm severity by clicking the alarmindicators in the upper right corner.

l You can click (red) to browse the network-wide critical alarms.

l You can click (orange) to browse the network-wide major alarms.

l You can click (yellow) to browse the network-wide minor alarms.

l You can click (light-blue) to browse the network-wide warning alarms.

NOTE

By default, the number shown by each indicator indicates the number of current network-wide alarms, whichare not cleared, of the specific severity.

7.1.4 Browsing Current Alarms(Web LCT)You can find the faults that occur on the equipment by browsing current alarms.


Tools, Equipment, and MaterialsWeb LCT

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon onthe toolbar.



67

TIP

You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.

From left to right, the alarm indicators and corresponding alarm severities are as follows:

l Red: critical alarm

l Orange: major alarm

l Yellow: minor alarm

l Purple: warning

l Light blue: abnormal event

The Browse Current Alarms tab is displayed by default.


Step 3 Optional: Click Filter.



68

The Filter dialog box is displayed.

Step 4 Optional: Set filtering conditions and click Filter.

Step 5 Optional: Click Save As.

A text file that lists the current alarms is displayed in Internet Explorer.

NOTE

You can save and archive the text file as required.

----End

7.1.5 Browsing History Alarms(U2000)You can know the faults that occur on the equipment in a past period of time by browsinghistorical alarms. A historical alarm refers to an alarm that is already cleared.



Procedure

Step 1 Choose Fault > Browse History Alarm from the Main Menu.

Step 2 Optional: In the Filter dialog box, click the Basic Settings tab.

1. In Severity, select the alarm severity to be queried.2. In Type, select the alarm type.3. In Occurrence Time Segment, specify the alarm generation time.



69

4. In Clearance Time Segment, specify the alarm clearance time.The time span starts from the time when the last historical alarm browsing operation wasperformed to the current time.

Step 3 In the Filter dialog box, click the Alarm Source tab.


Option Description

Browse all alarms on the NE. Select All Objects.

Browse certain alarms on the NE. 1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of Object

below NE, and click .4. Click OK.

Alarm Source displays Selected Alarm Source.

Step 5 Click OK.

Step 6 Browse the displayed historical alarms.

----End

7.1.6 Browsing History Alarms(Web LCT)You can know the faults that occur on the equipment in a past period of time by browsinghistorical alarms. A historical alarm refers to an alarm that is already cleared.



Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then click the icon onthe toolbar.

Step 2 Click the Browse History Alarms tab.



70

Step 3 Click Filter.

The Filter dialog box is displayed.

Step 4 Specify Rising Time and Cleared Time, and then click Filter.The time span starts from the time when the last historical alarm browsing operation wasperformed to the current time.

Step 5 Browse the filtered historical alarms.

Step 6 Click Save As.

A text file that lists the historical alarms is displayed in Internet Explorer.

NOTE


----End



71

7.1.7 Browsing Current Performance Events(U2000)You can know the running status of the equipment by browsing current SDH/PDH performanceevents. The counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.

Prerequisitesl The performance monitoring function must be enabled. For details about how to enable the

performance monitoring function, see 7.2.1 Configuring the Performance MonitoringStatus of NEs.

l You must be an NM user with NE monitor authority or higher.


Procedure

Step 1 Choose Performance > Browse SDH Performance from the Main Menu, and then click theCurrent Performance Data tab.

Step 2 Select one or more NEs from the left pane, and click .

Step 3 Select All in Monitored Object Filter Condition.

Step 4 Select 15-Minute in the Monitor Period field.

Step 5 Click the Count tab, and then select Display Continuous Severely Errored Seconds.

Step 6 Click Query to browse the current performance events.

Step 7 Click the Measure tab, select All

Step 8 Click Query to browse the displayed performance events.

Step 9 Re-define the time span by setting Monitor Period to 24-Hour.

Step 10 Repeat Step 5 through Step 8 to query the current performance events in a period of 24 hours.

----End



72

7.1.8 Browsing Current Performance Events(Web LCT)You can know the running status of the equipment by browsing current SDH/PDH performanceevents. The counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.





Web LCT

Procedure

Step 1 Select the 1-SHXA2 in the NE Explorer and choose Performance > Current Performancefrom the Function Tree.

Step 2 Select the object to be monitored from the Monitored Object Filter Condition drop-down list.

Step 3 Set Monitor Period.

Step 4 Select the performance events to be queried in Count. Set Consecutive Severely ErroredSecond in Display Options.

Step 5 Click Query.

Step 6 Browse the displayed performance events.

Step 7 Select the performance events to be queried in Gauge. Set Current Value and Maximum/Minimum Value in Display Options.

Step 8 Click Query.

Step 9 Browse the displayed performance events.

----End



73

7.1.9 Browsing History Performance Events(U2000)You can know the faults that occur on the equipment in a past period of time by browsinghistorical performance events.





U2000

Procedure

Step 1 Choose Performance > Browse SDH Performance from the main menu, and then click theHistory Performance Data tab.

Step 2 Select one or more NEs from the left pane, and click .

Step 3 Set the parameters, such as Monitored Object Filter Criteria, Monitor Period, DataSource.

Step 4 Click the Measure tab, and set Performance Event Type.

Step 5 Click the Count tab, and set Performance Event Type.

Step 6 Click Query.

----End

7.1.10 Browsing History Performance Events(Web LCT)You can know the faults that occur on the equipment in a past period of time by browsinghistorical performance events.



74





Procedure

Step 1 In the NE Explorer, select 1-SHXA2, and then choose Performance > History Performancefrom the Function Tree.

Step 2 Set Monitored Object Filter Condition.


Step 4 Specify the start time and the end time of a specific time span.The time span starts from the time when the last historical performance event browsing operationwas performed to the current time.

Step 5 Select all the available performance events in Count.

Step 6 Click Query to browse the historical performance events.


A text file that lists the historical performance events is displayed in Internet Explorer.

NOTE


Step 8 Select all the available performance events in Gauge, and select Current Value and Maximum/Minimum Value in Display Options.

Step 9 Click Query to browse the historical performance events.


A text file that lists the historical performance events is displayed in the IE system.



75

NOTE


----End

7.1.11 Browsing Current Alarms of the radio link(U2000)You can learn about the current exceptions on a radio link by browsing its current alarms.



Procedure

Step 1 In the Main topology, right click the desired radio link, choose Browse Current Alarm.


----End

7.1.12 Browsing Current Alarms of the radio link(Web LCT)You can learn about the current exceptions on a radio link by browsing its current alarms.



Procedure

Step 1 Select the desired radio link from the Object Tree in the NE Explorer, and chooseConfiguration > Radio Link Alarm from the Function Tree.



76

Step 2 Optional: Deselect Auto Refresh. Select Auto Refresh only after the update period is changedto a non-default value.

----End

7.1.13 Browsing Current Performance Events of the radio link(WebLCT)

You can learn about the current operating status of a radio link by browsing its currentperformance data.

Prerequisites



Web LCT

Procedure

Step 1 Select the desired radio link from the Object Tree in the NE Explorer, and chooseConfiguration > Radio Link Performance from the Function Tree.

Step 2 Optional: Deselect Auto Refresh and click Save As... to save the exported performance datain a text format.

----End



77

7.1.14 Browsing Historical Performance Data of a Radio Link(WebLCT)

You can learn about the operating status of a radio link by browsing its historical performancedata over a specific period.



Procedure

Step 1 Select the desired radio link from the Object Tree in the NE Explorer, and chooseConfiguration > Radio Link Performance from the Function Tree.

Step 2 Click the History Performance tab.

Step 3 Optional: Select the Display Format for the query result. The default value is Chart.

Step 4 Select Link Tx/Rx Power or Link Errors.



78

Step 5 Optional: Click Save As... to save the exported data as a .jpg file or in a text format.

----End

7.1.15 Browsing the Performance Event Threshold-CrossingRecords(U2000)

You can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.



Procedure

Step 1 Choose Performance > Browse SDH Performance from the Main Menu.

Step 2 Click the Performance Threshold-Crossing Record tab.

Step 3 Select an NE from the Object Tree in the NE Explorer. Click .

Step 4 Set the parameters such as Monitored Object Filter Condition, Monitor Period, andPerformance Event Type.

Step 5 Click Query.



79

----End

7.1.16 Browsing the Performance Event Threshold-CrossingRecords(Web LCT)

You can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.

Prerequisites



Web LCT

Procedure

Step 1 Select the1-SHXA2 from the NE Explorer and choose Performance > PerformanceThreshold-Crossing from the Function Tree.

Step 2 Set Monitored Object Filter Condition.




80

Step 4 Specify the start time and the end time of a specific time span.The time span starts from the time when the last historical performance event browsing operationwas performed to the current time.

Step 5 Specify Performance Event Type.

Step 6 Optional: Specify Display Options.

Step 7 Click Query.

Step 8 Browse the performance event threshold-crossing records that are displayed.


A text file that lists the historical performance events is displayed in the IE system.

NOTE


----End

7.1.17 Browsing Abnormal Events(U2000)You can find the faults that occur on the equipment in a specific time by browsing abnormalevents. An abnormal event refers to an exception that occurs on the system at a particular timerather than an exception that persists for a certain time of period.



Procedure

Step 1 Choose Fault > Browse Event Logs from the Main Menu.

Step 2 In the Filter dialog box, click the Event Source tab.


Option Description

Browse all performance events on the NE. Select All Objects.

Browse certain performance events on theNE.

1. Select Custom.2. Choose Add > Object below NE.3. Select the required NE in the left pane of

Object below NE, and click .4. Click OK.

Event Source displays Selected EventSource.



81

Step 4 Click OK.

Step 5 Browse the abnormal events.

----End

Related InformationBeing different from an alarm that has both the occurrence time and the clearance time, anabnormal event has only the occurrence time.

7.1.18 Browsing Abnormal Events(Web LCT)You can find the faults that occur on the equipment in a specific time by browsing abnormalevents. An abnormal event refers to an exception that occurs on the system at a particular timerather than an exception that persists for a certain time of period.



Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Alarm >Browse Abnormal Events from the Function Tree.



82

TIP

In the NE Explorer, you can also select the required NE from the Object Tree and click the iconto navigate to the Browse Abnormal Events tab.

Step 2 Click Filter.

Step 3 In the Abnormal Event Name combo box, select Select All, and then click OK.

Step 4 Browse the displayed abnormal events.


A text file that lists the abnormal events is displayed in Internet Explorer.

NOTE


----End

Related InformationBeing different from an alarm that has both the occurrence time and the clearance time, anabnormal event has only the occurrence time.

7.1.19 Browsing UAT Events(U2000)Learn about the severe abnormalities on the transmission line by browsing UAT events.



83


Tools, Instruments and MaterialsU2000

ContextUAT refers to a period of 10 consecutive seconds during which the bit error ratio per second ofthe digital signal in either of the transmission directions of a transmission system is inferior to10-3. These 10 seconds are considered to be part of the unavailable time.

Procedure

Step 1 In the NE Explorer, select 1-SHXA2.

Step 2 Choose Performance > UAT Event from the Function Tree.

Step 3 Set Monitored Object Filter Criteria, From, To, and Data Source.

Step 4 Set Function Block Type and Display Options.

Step 5 Click Query.

l If you select Query from NMS, the query result displays UAT events currently stored onthe NMS.

l If you select Query from NE, the query result displays UAT events currently stored on theNE, which are updated to the NMS database at the same time.

Step 6 Close the dialog box that is displayed.

----End

7.1.20 Browsing UAT Events(Web LCT)Learn about the severe abnormalities on the transmission line by browsing UAT events.


Tools, Instruments and MaterialsWeb LCT



84

Context

UAT refers to a period of 10 consecutive seconds during which the bit error ratio per second ofthe digital signal in either of the transmission directions of a transmission system is inferior to10-3. These 10 seconds are considered to be part of the unavailable time.

Procedure

Step 1 In the NE Explorer, select 1-SHXA2, and then choose Performance > UAT Event from theFunction Tree.

Step 2 Set the relevant parameters, such as Monitored Object Filter Condition.

Step 3 Set Function Block Type and Display Options.

Step 4 Click Query.


The system displays a text file that lists the queried UAT events in an IE window.

NOTE

You can save and archive the text file.

----End

7.2 Setting Alarm and Performance Management FunctionsThe OptiX RTN 310 supports various alarm and performance management functions.

7.2.1 Configuring the Performance Monitoring Status of NEsBy performing this operation task, you can manually enable or disable performance monitoringfor NEs, or set the performance monitoring period.

Prerequisites

You must be an NM user with NE operator authority or higher.



85


U2000

NOTE

Web LCT also supports this operation and the steps are the similar to those on the U2000.

Procedure

Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NEPerformance Monitoring Time from the Function Tree.

NOTE

If you configure the performance monitoring status of NEs using the Web LCT, perform the following steps:

In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE PerformanceMonitor Time from the Function Tree.

Step 2 Configure the performance monitoring parameters of the NEs.

1. Select 15-Minute or 24-Hour.

2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.

3. Set the start time and end time of the performance monitoring of NEs.

NOTE

l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.

l You can specify the start time of the performance monitoring function, only after selecting Enabledin the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

l You can specify the end time of the performance monitoring function, only after selecting Enabledand then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

4. Click Apply. Close the displayed dialog box.

----End

7.2.2 Suppressing AlarmsThis section describes how to suppress specific alarms.



86

Prerequisites

You must be an NM user with NE maintainer authority or higher.

Tools, Instruments and Materials

U2000

NOTE

Web LCT also supports this operation and the steps are the same as those on the U2000.

Procedure

Step 1 In the NE Explorer, select the NE.

Step 2 Choose Alarm > Alarm Suppression from the Function Tree.

Step 3 Set Status in Alarm Suppression.

Step 4 Click Apply.

----End

7.2.3 Reversing Alarms for PortsThis section describes how to reverse alarms for ports.

Prerequisites



U2000

NOTE


Procedure

Step 1 In the NE Explorer, select the NE.

Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.

Step 3 Set Alarm Reversion to Enable (Manually Restore).



87

Step 4 Click Apply.


Step 6 In the NE Explorer, select the desired board.

Step 7 Choose Alarm > Alarm Reversion from the Function Tree.

Step 8 Set Reversion Status for the required port.

Step 9 Click Apply.


----End

7.2.4 Setting Bit Error Thresholds for Microwave PortsThis section describes how to set bit error thresholds for microwave ports.

Prerequisites



U2000

NOTE


Procedure


Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.

Step 3 Set bit error thresholds.

Step 4 Click Apply.

----End



88

7.2.5 Setting Monitoring and Auto-Report Status of PerformanceEvents

This section describes how to set the monitoring and auto-report status of specific performanceevents for monitored objects.

Prerequisites



U2000

NOTE


Procedure


Step 2 Choose Performance > Performance Monitor Status from the Function Tree.

Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-Report.

Step 4 Click Apply.

----End

7.2.6 Setting Performance ThresholdsThis section describes how to set the thresholds of specific performance events for monitoredobjects.

Prerequisites




89


U2000

NOTE


Procedure

Step 1 In the NE Explorer, select the desired board.

Step 2 Choose Performance > Performance Threshold from the Function Tree.

Step 3 Set Threshold Value.

Step 4 Click Apply.


----End

7.2.7 Resetting Performance RegistersThis section describes how to reset performance registers. After performance registers are reset,their counts are cleared and they immediately start a new counting period.

Prerequisites




90


U2000

NOTE


Procedure


Step 2 Choose Performance > Reset Board Performance Register from the Function Tree.

Step 3 Set Monitored Object and register types.

Step 4 Click Reset.

Step 5 In the Hint dialog box that is displayed, click Yes.


----End

7.3 Querying a ReportYou can obtain the version, manufacture, and microwave link information of all the boards byquerying the corresponding report.

7.3.1 Querying the Board Information Report(U2000)You can obtain the software version of each board by querying the board information report.

Prerequisites




91


Procedure

Step 1 Choose Inventory > Physical Inventory from the Main Menu.

Step 2 Select Board from Physical Inventory Type in the Physical Inventory window.

Step 3 In Physical Inventory, click the Board List tab.

Step 4 Click Filter.In Filter window, set the board or board attributes that need to be queried. Click OK.

Step 5 The board information displayed in the Board List.

Step 6 Optional: Click Save As.Set the parameters in Saving Options.

Step 7 Click OK. Then, you can save and archive the board information as a text file.


----End

7.3.2 Querying the Board Information Report(Web LCT)You can obtain the software version of each board by querying the board information report.



Procedure

Step 1 Select the NE in the NE Explorer.



92

Step 2 Choose Report > Board Information Report from the Function Tree.

Step 3 All the board version information about the NE is displayed on the Board InformationReport tab.


The text file that describes the board information is displayed on Internet Explorer.

NOTE

You can save the text file as required.

----End

7.3.3 Querying the Board Manufacturing Information Report(U2000)

You can obtain the manufacturing information about each board and the SFP module by queryingthe board manufacturing information report.



Procedure

Step 1 Choose Inventory > Project Document > Board Manufacturer Information from the MainMenu.

Step 2 In Board Manufacturer Information, click the Board Manufacturer Information tab.

Step 3 Select one or multiple NEs from the left pane, and click .


Step 5 Click Query.The Query processing bar is displayed.




93


Step 8 Set the parameters in Saving Options.

Step 9 Click OK. Then, you can save and archive the board manufacturing information as a text file.

----End

7.3.4 Querying the Board Manufacturing Information Report(WebLCT)

You can obtain the manufacturing information about each board and the SFP module by queryingthe board manufacturing information report.



Procedure


Step 2 Choose Report > Board Detail Information Report from the Function Tree.

Step 3 All the board manufacture information about the NE is displayed on the Board DetailInformation Report tab.



94


The text file that describes the detailed board information is displayed on Internet Explorer.

NOTE

You can save the text file as required.

----End

7.3.5 Querying the Microwave Link Information ReportYou can obtain the current and recent transmit/receive power of microwave links by queryingthe microwave link information report.

PrerequisitesYou must be an NM user with NE maintainer authority or higher.


NOTE


Procedure

Step 1 In Main Menu, choose Inventory > Microwave Report > Microwave Link Report.



95

Step 2 In the left pane of the Microwave Link Report tab page, choose one or more NEs, and click

.




Step 6 Click OK. Then, you can save and archive the microwave link information as a text file.

----End

7.3.6 Querying the Network-wide License ReportBy querying the network-wide license report, you can check the license information of each NE.


Tools, Instruments, and MaterialsU2000

NOTE


Procedure

Step 1 Choose Inventory > Microwave Report > Microwave License Capacity Report from theMain Menu.

Step 2 Select one or more NEs in the left pane, and click .




96

Step 4 Optional: Click Save As. Save the license report as a file and archive the file properly.


Step 6 Click OK. Then, the license report is saved and archived as a file.

----End

7.4 Software LoopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS.During software loopback, you need not visit the engineering site. Hence, software loopback isused more widely than hardware loopback.

7.4.1 Setting Loopbacks for Ethernet PortsThe OptiX RTN 310 supports PHY-layer inloops and MAC-layer inloops at Ethernet ports.



NOTE


Contextl A MAC-layer inloop is an inloop where the Ethernet switching unit loops back the Ethernet

physical signals towards the baseband processing unit at the MAC layer.l A PHY-layer inloop is an inloop where the Ethernet access unit loops back the Ethernet

frame signals towards the baseband processing unit at the PHY layer.



97

Figure 7-1 Ethernet port inloop

RF processing

unit

FE/GE service

signal

Service bus

Modulated signal

RF signal

OptiX RTN 310

MUX unit

Modem unit

Baseband processing unit

Service bus

MACPHY

Ethernet switching

unit

Ethernet access

unit

Precautions

CAUTIONl A loopback operation results in service interruption.l A software loopback may be released automatically after a certain period (five minutes, by

defaults). For details, see 7.10 Setting the Automatic Release Function.

Procedure

Step 1 Select the desired NE.

Step 2 Choose Configuration > Interface Management > Ethernet Interface from the FunctionTree.

Step 3 Click the Advanced Attributes tab.

Step 4 Set the loopback status of the port based on the requirements.

Step 5 Click Apply.Then, the Confirm dialog box is displayed.

Step 6 Click OK.


----End

7.4.2 Setting Loopback for the IF BoardThe OptiX RTN 310 supports inloops/outloops at IF ports and composite ports.



98



NOTE


ContextThe IF port inloop is a process wherein the IF signals are looped back at the modem unit towardsthe MUX unit.

Figure 7-2 IF port inloop

Ethernet access

unit

RF processing

unit

Ethernet switching

unit

FE/GE service

signal

Service bus

Modulated signal

RF signal

OptiX RTN 310


Service bus

MUX unit

Modem unit

The IF port outloop is a process wherein the IF signals are looped back at the modem unit towardsthe RF processing unit.

Figure 7-3 IF port outloop

Ethernet access

unit

RF processing

unit

Ethernet switching

unit

FE/GE service

signal

Service bus

Modulated signal

RF signal

OptiX RTN 310


Service bus

MUX unit

Modem unit

The composite port inloop is a process wherein the microwave baseband signal is looped backat the MUX/DEMUX unit towards the Ethernet switching unit.



99

Figure 7-4 Composite port inloop

Ethernet access

unit

RF processing

unit

Ethernet switching

unit

FE/GE service

signal

Service bus Modulated

signal RF signal

OptiX RTN 310

Baseband processing unitService

busMUX unit

Modem unit

The composite outloop is a process wherein the microwave baseband signal is looped back atthe MUX/DEMUX unit towards the modem unit.

Figure 7-5 Composite port outloop

Ethernet access

unit

RF processing

unit

Ethernet switching

unit

FE/GE service

signal

Service bus Modulated

signal RF signal

OptiX RTN 310

Baseband processing unitService

busMUX unit

Modem unit

Precautions

CAUTIONl The services may be interrupted at the port or on the path where the loopback is performed.l A software loopback may be released automatically after a certain period (five minutes, by

defaults). For details, see 7.10 Setting the Automatic Release Function.

Procedure

Step 1 Select the desired navigation path based on the loopback type.



100

To Perform... Choose...

IF portloopback

1. Select 1-SHXA2 in the NE Explorer.2. Choose Configuration > IF Interface from the Function Tree.3. Select IF Attributes tab.4. Select the port where the loopback needs to be performed and set IF Port

Loopback.

Compositeport loopback

1. Select NE in the NE explorer.2. Choose Configuration > Ethernet Interface Management >

Microwave Interface from the Function Tree.3. Select Loopback Attributes tab.

NOTENOTE

Skip this step when the Web LCT is used for configuration.

4. Select the port where the loopback needs to be performed and setComposite Port Loopback.

Step 2 Click Apply.Then, the Confirm dialog box is displayed.


----End

7.5 ResetReset is an important method of troubleshooting software faults. Reset is classified into coldreset, warm reset.

7.5.1 Cold ResetDuring a cold reset, software is reset, hardware is initialized, and the FPGA file is reloaded.

Prerequisites



U2000



101

NOTE


Precautions

CAUTIONDuring a cold reset, services are interrupted, and NE configuration data that was configuredwithin five minutes before the cold reset may be lost.

Procedure

Step 1 In NE Panel, right-click 1-SHXA2.

Step 2 Choose Cold Reset from the shortcut menu.

Then, the Warning dialog box is displayed.

Step 3 Click OK.


----End

7.5.2 Warm ResetDuring a warm reset, only software is reset, hardware is not initialized, and the FPGA file is notreloaded.



102

Prerequisites



U2000

NOTE


Precautions

During warm reset, the board software is reset but the services are not interrupted.

Procedure

Step 1 In NE Panel, right-click 1-SHXA2.

Step 2 Choose Warm Reset from the shortcut menu.

Then, the Warning dialog box is displayed.

Step 3 Click OK.


----End



103

7.6 Detecting Consecutive WavesThe consecutive wave detection function is used to check whether the transmit frequencydeviates.



NOTE


Procedure

Step 1 Select 1-SHXA2 in the NE explorer.

Step 2 Choose Configuration > IF Interface from the Function Tree.

Step 3 Select IF Attributes tab.

Step 4 Select the port to be tested.

Step 5 Set Consecutive Wave Status to Start.

Step 6 Click Apply.

----End

7.7 PRBS TestThe OptiX RTN 310 supports the PRBS test function, allowing PRBSs to be transmitted tomicrowave ports.



NOTE




104

Precautions

Figure 7-6 PRBS test on the OptiX RTN 310

Local NE Opposite NE

Outloop at an IF port

11


1

PRBS transmitter

PRBS receiver


RF processing unit

1

RF processing unit

CAUTIONl During the PRBS test, the services in the tested path are interrupted.l The PRBS test can be performed only in one path and in one direction at one time.

Procedure

Step 1 Select the desired radio link in the NE Explorer, and choose Diagnosis&Maintenance > RadioLink Loopback from the Function Tree.

Step 2 Perform an outloop at the opposite IF port.

Step 3 Select 1-SHXA2 from the NE Explorer.

Step 4 Choose Configuration > PRBS Test from the Function Tree.

Step 5 Select the port to be tested.

Step 6 Set Duration and Measured in Time.



105

NOTE

The time unit of the PRBS test can be one second, 10 minutes, or one hour.

Step 7 Optional: Select Accumulating Mode.

Step 8 Click Start to Test.A prompt is displayed.

Step 9 Click OK.

Step 10 When Process is displayed as 100%, click Query to check the test result.

NOTE

The result of a PRBS test can be normal, error, or invalid.

l Invalid: indicates that no bit is received. In this case, the curve is yellow.

l Normal: indicates that the path is in normal state. In this case, the number of PRBSs is zero, and thecurve is green.

l Error: indicates that the path has errors. In this case, the number of total PRBSs is a non-zero number,and the curve is red.

----End

7.8 Querying the License CapacityYou can check whether the loaded license file meets the requirements by querying the licensecapacity.



NOTE


Procedure


Step 2 Choose Configuration > License Management.

Step 3 Click Query, browse the license capacity of the NE.

----End



106

7.9 Scanning Interfering SignalsYou can learn whether intra-frequency or inter-frequency interference exists by scanningfrequency spectra in microwave channels.

Prerequisitesl You must be an NM user with NE maintainer authority or higher.

l The opposite OptiX RTN 310 is muted before you scan interfering signals.


U2000

NOTE


Procedure

Step 1 Select an NE from the NE Explorer.

Step 2 Choose Diagnosis&Maintenance > RF Scan from the Function Tree.

NOTE

If you configure scanning interfering signals using the Web LCT, perform the following steps:

1. Choose Diagnosis&Maintenance > ODU Frequency Scan from the Function Tree.

2. Select ODU Frequency Scan tab.

Step 3 Set related parameters and click Start to Scan.

----End

7.10 Setting the Automatic Release FunctionTo protect the communication between the NMS and NE against improper operations, an NEsupports the automatic release of the RF muting, software loopback, and other operations thatrequire you to exercise caution. The automatic release time is five minutes by default. You canset whether to enable the automatic release function and the automatic release time through theNMS.

Prerequisites




107


U2000

NOTE


Procedure

Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Functionfrom the Main Menu.

NOTE

If you setting the automatic release function of NEs using the Web LCT, perform the following steps:

1. In the NE Explorer, select the desired NE.

2. Choose Configuration > Interface Management > Automatic Disabling of NE Function from theFunction Tree.

Step 2 Select the desired NE from the Object Tree. Click .

NOTE

Skip this step when the Web LCT is used for configuration.

Step 3 In Automatic Disabling of NE Function, set Auto Disabling and Auto Disabling Time(min).

Step 4 Click Apply to complete the settings for the automatic release function.

----End

7.11 Querying Power Consumption of NEThis section describes how to query power consumption of NE.

Prerequisites


Tools, Instruments, and Materials

U2000

NOTE




108

Procedure

Step 1 Choose Configuration > NE Batch Configuration > Power Management from the MainMenu.

Step 2 In the NE Power dialog box, select the NE Power tab.

Step 3 Select the required NE from the object tree, and then click .

Step 4 Click Query.The Query progress bar is displayed.


Step 6 On the NE Power tab page, browse NE Nominal Power Consumption and NE Current PowerConsumption of the selected board.

----End

7.12 Querying the Attributes of an Ethernet PortThis section describes how to learn about Ethernet service flow rates and physical bandwidthparameters of Ethernet ports.

Prerequisites



U2000

NOTE


Procedure

Step 1 Select an NE from the NE Explorer.

Step 2 Choose Configuration > Interface Management > Ethernet Interface from the FunctionTree.

Step 3 Click the Advanced Attributes tab.

Step 4 Click Query.

Step 5 Check the parameters such as Port Physical Parameters, Transmitting Rate, and ReceivingRate.



109

----End

7.13 Setting Traffic, Physical Bandwidth, or BandwidthUtilization of Ethernet Ports

To query the traffic, physical bandwidth, or bandwidth utilization of Ethernet ports within acertain period, you need to enable the monitoring for the object before that period starts.

Prerequisites



U2000

NOTE


Background Information

After the flow monitoring function is enabled, the system saves the statistics about the receivedtraffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system storesthe statistics that are collected in the last 30 days. In the system, every measurement entry showsthe average transmit rate and average receive rate within a period of 15 minutes. You can querythe statistics in the last 30 days.

Procedure

Step 1 Select 1-SHXA2 from the Object Tree in the NE Explorer.

Step 2 Choose Performance > Ethernet Port Flow Monitoring from the Function Tree.

Step 3 Select the Set Monitoring tab. Set Flow Monitoring, Physical Bandwidth Monitoring,Bandwidth Usage Monitoring to Enabled for the Ethernet port.

Step 4 Click Apply.

Step 5 Close the displayed Result dialog box.

----End



110

7.14 Querying Traffic, Physical Bandwidth, or BandwidthUtilization of Ethernet Ports

This section describes how to query the change curve of the traffic, physical bandwidth, orbandwidth utilization of Ethernet ports within a certain period.

Prerequisites


The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoringfunction on a port, see 7.13 Setting Traffic, Physical Bandwidth, or Bandwidth Utilizationof Ethernet Ports.


U2000

NOTE


Background Information

After the flow monitoring function is enabled, the system saves the statistics about the receivedtraffic and transmitted traffic with an interval of 15 minutes. In normal cases, the system storesthe statistics that are collected in the last 30 days. In the system, every measurement entry showsthe average transmit rate and average receive rate within a period of 15 minutes. You can querythe statistics in the last 30 days.

Procedure

Step 1 Select 1-SHXA2 from the Object Tree in the NE Explorer.

Step 2 Choose Performance > Ethernet Port Flow Monitoring from the Function Tree.

Step 3 Select the Query Flow tab.

Step 4 Set the Monitored Object, Monitored Indicator, Start Time, End Time, and DisplayMode.

Step 5 Click Query.

The system displays the query result in a table or in a graph.



111

Step 6 Close the displayed Result dialog box.

----End

7.15 End-to-End Management on Fibers, Tunnels, and PWE3Services

This section describes the common maintenance operations for end-to-end management onfibers, MPLS tunnels, and PWE3 services.

7.15.1 Expanding/Collapsing Fibers and CablesIf multiple fibers, cables, or tunnels are available between network elements (NEs), you cancollapse them to form a link, which is displayed in the topology. You can also expand the linkto display the fibers, cables, or tunnels.



NOTE


Procedure

Step 1 Optional: Expand fibers and cables.1. In the main topology, if an NE link is displayed as

, select the link and right-click it. Then chooseExpand Link from the shortcut menu.

Step 2 Optional: Collapse fibers and cables.

1. In the main topology, if an NE link is displayed as ,select the link and right-click it. Then choose Collapse Link from the shortcut menu.

----End

7.15.2 Querying the Radio Link InformationWhen fiber links are available between network elements (NEs), you can query the relevantinformation about radio links.



112



NOTE


Procedure

Step 1 In the main topology, select the required radio link and right-click it. Then choose MicrowaveLink Information from the shortcut menu.The Microwave Link Report dialog box is displayed.

Step 2 Select the required NE or board from the object tree, and then click .

Step 3 Click Query.

Step 4 In the Result dialog box that is displayed, click Close.

----End

7.15.3 Querying the Radio Link PerformanceWhen fiber links are available between network elements (NEs), you can query the relevantperformance information about radio links.



NOTE


Procedure

Step 1 In the main topology, select the required radio link and right-click it. Then choose Radio LinkPerformance Statistics from the shortcut menu.

NOTE

The equivalent operations on the Web LCT are as follows:

In the NE Explorer, choose the sink NE or source NE, choose Configuration > Radio Link PerformanceStatistics in the function.

The Radio Link Performance Statistics dialog box is displayed.

Step 2 In the Radio Link Performance Statistics dialog box, choose Current Performance tab.



113

Step 3 In the Current Performance dialog box, choose Auto Refresh to see the current performanceof the radio link.

Step 4 In the Radio Link Performance Statistics dialog box, choose History Performance tab.

Step 5 In the Radio Link Performance Statistics dialog box, set Monitor Period, Ended From,To, and Options. Then click OK below Options.

Step 6 Click Query.

Step 7 Click Save as, and save the data displayed in the current dialog box.

----End



114

A Alarm Reference

Alarms are important indicators when exceptions occur on the equipment. This section describesall the possible alarms on the OptiX RTN 310 and how to handle these alarms.

A.1 Alarm ListThe following table lists all the possible alarms on the OptiX RTN 310 in alphabetical order.

A.2 Alarms and Handling ProceduresThis section describes the alarms that frequently occur on the OptiX RTN 310 in alphabeticorder and how to handle these alarms.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide A Alarm Reference


115

A.1 Alarm ListThe following table lists all the possible alarms on the OptiX RTN 310 in alphabetical order.

Table A-1 Alarm list

Alarm Name Description Alarm Severity

AM_DOWNSHIFT AM downshifts Major

BDTEMP_SENSOR_FAIL

Board temperature sensorfailure

Major

BOOTROM_BAD BOOTROM data check fails. Major

CLK_LOCK_FAIL Clock locking fails Major

DBMS_DELETE A database is being deleted. Critical

DBMS_ERROR Database error Major

DBMS_PROTECT_MODE

Database in protected mode Critical

DCNSIZE_OVER The DCN network is over-sized.

Major

ERPS_IN_PROTECTION ERPS in protected mode Minor

ETH_CFM_AIS A local MEP_AIS occurs Major

ETH_CFM_LOC Loss of connectivity Critical

ETH_CFM_MISMERGE Misconnection Critical

ETH_CFM_RDI An opposite MEP_RDIoccurs.

Minor

ETH_CFM_UNEXPERI Errored frames Minor

ETH_EFM_DF Discovery failure Major

ETH_EFM_EVENT Performance events at theopposite end

Major

ETH_EFM_LOOPBACK A loopback occurs. Major

ETH_EFM_REMFAULT Faults occur at the oppositeend.

Critical

ETH_LOS The Ethernet port connectionis lost.

Critical

ETH_NO_FLOW No flow on the Ethernet port Major

ETHOAM_SELF_LOOP Point-to-point OAM detectsa port loopback.

Major



116


FLOW_OVER Received flow at a portexceeds the threshold.

Minor

HARD_BAD The hardware is faulty. Critical

IN_PWR_ABN Abnormal input power Major

LAG_DOWN A LAG is unavailable. Major

LAG_MEMBER_DOWN A member port of the LAG isunavailable.

Minor

LASER_MOD_ERR The pluggable opticalmodule on the board does notmatch the optical port.

Major

LCS_LIMITED An NE is configured with aservice capacity or functionbeyond the permission of theinstalled license.

Major

LICENSE_LOST A license file is lost orcorrupted.

Major

LOOP_ALM A loopback occurs. Minor

LSR_NO_FITED Laser not installed Critical

LTI Loss of the synchronoussource

Major

MAC_EXT_EXC The number of bit errors atthe MAC layer crosses thethreshold.

Major

MAC_FCS_EXC The software detects that thenumber of bit errors at theMAC layer crosses thethreshold.

Major

MULTI_RPL_OWNER The ring network containsmultiple RPL owner nodes.

Minor

MW_AM_TEST An IF port is in the AMtesting state.

Minor

MW_BER_EXC Excessive errors on radiolinks

Minor

MW_BER_SD Signal degrade due toexcessive errors on radiolinks

Minor

MW_CFG_MISMATCH Configuration mismatch onthe radio link

Critical



117


MW_CONT_WAVE Continuous wave Minor

MW_FEC_UNCOR Microwave frames containthe errors that cannot becorrected by using theforward error correction(FEC) technology.

Minor

MW_LIM Mismatched radio link ID Major

MW_LOF Loss of microwave frames Critical

MW_RDI Remote defect indication onradio links

Minor

NB_UNREACHABLE A neighboring NE isunreachable to the local NE.

Minor

NESF_LOST The NE software is lost. Critical

NESOFT_MM The software in the main areais different from that in thestandby area.

Major

NTP_SYNC_FAIL NTP time synchronizationfails.

Minor

PASSWORD_NEED_CHANGE

Password of the user whologs in is unchanged

Major

PATCH_ACT_TIMEOUT Patch package activationtimes out.

Minor

PATCH_DEACT_TIME-OUT

Patch package deactivationtimes out.

Minor

PATCH_PKGERR Patch package errors Minor

PORT_EXC_TRAFFIC The traffic is higher than theport bandwidth threshold.

Warning

PORTMODE_MIS-MATCH

The working mode of theremote FE port does notmatch that of the local FEport.

Minor

POWER_ALM Power module alarm Major

PTP_TIMESTAMP_ABN Abnormal PTP timestamps Major

RADIO_FADING_MARGIN_INSUFF

Insufficient radio fadingmargin

Minor

RADIO_MUTE The radio transmitter ismuted.

Warning



118


RADIO_RSL_BE-YONDTH

The received signal levelexceeds the threshold.

Minor

RADIO_RSL_HIGH Over high radio receivedsignal level

Critical

RADIO_RSL_LOW Over low radio receivedsignal level

Critical

RADIO_TSL_HIGH Over high radio transmittedsignal level

Critical

RADIO_TSL_LOW Over low radio transmittedsignal level

Critical

S1_SYN_CHANGE Clock source switching in S1mode

Major

SEC_RADIUS_FAIL Excessive RADIUSauthentication failures

Major

SECU_ALM Logins attempts ofunauthorized users

Major

SSL_CERT_NOENC The certificate file of SSL isnot encrypted

Major

STORM_CUR_QUENUM_OVER

Alarm storms Minor

SWDL_ACTIVATED_TIMEOUT

The activation operationtimes out.

Critical

SWDL_COMMIT_FAIL The submit operation fails. Minor

SWDL_INPROCESS The NE is in the process ofpackage loading.

Warning

SWDL_NEPKGCHECK Loss of package files Critical

SWDL_PKGVER_MM Inconsistent packageversions

Minor

SWDL_ROLLBACK_FAIL

The version rollback on anNE fails.

Minor

SYNC_C_LOS Loss of synchronizationclock sources

Warning

SYSLOG_COMM_FAIL Communication between theNE and the syslog server fails

Major

TEMP_ALARM The current temperatureexceeds the lower/higherthreshold.

Minor



119


TIME_LOCK_FAIL Time locking fails. Major

TIME_LOS The time source level is lost. Major

TIME_NO_TRACE_MODE

The NE time enters the non-tracing state.

Minor

USB_PROCESS_FAIL Data restoration from a USBflash drive fails.

Minor

XPIC_LOS Loss of XPIC compensationsignals

Critical

A.2 Alarms and Handling ProceduresThis section describes the alarms that frequently occur on the OptiX RTN 310 in alphabeticorder and how to handle these alarms.

A.2.1 AM_DOWNSHIFT

DescriptionThe AM_DOWNSHIFT alarm indicates the downshift of the AM scheme. This alarm occursafter the AM mode is downshifted from the highest-order modulation scheme to the lower-ordermodulation scheme. After the AM mode is upshifted from the lower-order modulation schemeto the highest-order modulation scheme, this alarm is cleared.

Attribute

Alarm Severity Alarm Type

Major Communication alarm

ParametersNone.

Impact on the SystemWhen the AM_DOWNSHIFT alarm occurs, the service transmission capacity over the radiolink decreases.

Possible CausesThe microwave channel performance deteriorates.l Cause 1: External factors (for example, the climate) cause the degradation of the working

channel.



120

l Cause 2: There are interferences around the working channel.l Cause 3: The OptiX RTN 310 at the transmit end has abnormal transmit power.l Cause 4: The OptiX RTN 310 at the receive end has abnormal receive power.

Procedure

Step 1 Cause 1: External factors (for example, the climate) cause the degradation of the workingchannel.1. When external factors (for example, the climate) cause the degradation of the working

channel, the downshift of the AM scheme is normal. Therefore, this alarm does not needto be handled.

Step 2 Cause 2: There are interferences around the working channel.1. Eliminate the interferences around the working channel.

Step 3 Cause 3: The OptiX RTN 310 at the transmit end has abnormal transmit power.1. Use the NMS to check whether the transmit power of the OptiX RTN 310 at the transmit

end is abnormal. For details on troubleshooting the fault at the transmit end, seeTroubleshooting Radio Links.

Step 4 Cause 4: The OptiX RTN 310 at the receive end has abnormal receive power.1. Use the NMS to check whether the receive power of the OptiX RTN 310 at the receive end

is abnormal. For details on troubleshooting the fault at the receive end, seeTroubleshooting Radio Links.

----End

Related InformationNone.

A.2.2 BDTEMP_SENSOR_FAIL

DescriptionThe BDTEMP_SENSOR_FAIL alarm indicates that the temperature sensor on the board fails.

Attribute


Major Equipment alarm

ParametersNone.

Impact on the SystemWhen the BDTEMP_SENSOR_FAIL alarm occurs, the board temperature data cannot becollected. As a result, the TMEP_ALARM alarm is absent when the board temperature is toohigh.



121

Possible CausesCause 1: The OptiX RTN 310 is faulty.

Procedure

Step 1 Replace the OptiX RTN 310.

----End


A.2.3 BOOTROM_BAD

DescriptionThe BOOTROM_BAD alarm indicates that the BOOTROM data verification fails. This alarmoccurs when the BOOTROM data is found damaged during a periodical system check.

Attribute



ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For detailsabout each parameter, refer to the following table.

Name Meaning

Parameter 1 The value is always 0x01.

Parameters 2 and 3 Indicates the type of the BOOTROM damage.

l 0x00 0x01: damage to basic BIOSl 0x00 0x02: damage to extended BIOS

Parameters 4 and 5 The values are always 0xff 0xff.

Impact on the SystemIf the NE is cold reset when the BOOTROM_BAD alarm occurred, BIOS loading fails and theNE fails to be started.




122

Procedure


----End


A.2.4 CLK_LOCK_FAIL

DescriptionThe CLK_LOCK_FAIL alarm indicates that clock locking fails.

Attribute



ParametersNone.

Impact on the SystemWhen the CLK_LOCK_FAIL alarm occurs, the slave clock is not coordinated with the masterclock, and bit errors may occur.

Possible Causesl Cause 1: Physical-layer synchronization is used but the clock priority table is not

configured.l Cause 2: Physical-layer synchronization is used but the frequency deviation of the clock

source is too large.l Cause 3: Physical-layer synchronization is used but the physical link of the clock source is

faulty.

Procedure

Step 1 Cause 1: Physical-layer synchronization is used but the clock priority table is not configured.1. Query the current clock priority table to check whether this table contains only internal

clock sources. If yes, reconfigure the clock priority table, ensuring this table contains otheravailable clock sources in addition to internal clock sources. Then, the alarm will beautomatically cleared.

2. If the current clock priority table contains other clock sources, the possible causes are asfollows:l The SYNC_C_LOS alarm is reported.



123

l The SSM protocol is enabled on the local NE but is disabled on its upstream NE. Enablethe SSM protocol for its upstream NE.

Step 2 Cause 2: Physical-layer synchronization is used but the frequency deviation of the clock sourceis too large.

1. Check whether there are higher-level BER alarms or performance events. If yes, handlethe alarms or performance events and check whether this alarm is cleared.

2. If the traced clock source is an external clock source, check whether the external clocksignal is functional. If not, replace the external clock source.

3. Check whether the clock configuration data is correct, for example, whether the clock inputmode and the clock output mode are the same. If any configuration is incorrect, rectify it.Then, check whether the alarm is cleared.

4. If the alarm persists, the clock unit is faulty. Replace the local OptiX RTN 310.

Step 3 Cause 3: Physical-layer synchronization is used but the physical link of the clock source is faulty.

1. Check whether the ETH_LOS alarm is reported. If yes, clear this alarm.

2. If the alarm persists, query the transmit optical power at the opposite end on the NMS. Ifthe transmit power is abnormal, replace the optical module used at the opposite end.

3. If the alarm persists, check whether the local receive port is faulty. If yes, replace the localOptiX RTN 310.

----End

Related Information

None.

A.2.5 DBMS_DELETE

Description

The DBMS_DELETE alarm indicates that a database is being deleted. This alarm is reportedwhen a user runs a command to delete the database and the NE is in the Deleting Database state.

Attribute


Critical Equipment alarm

Parameters

None.

Impact on the System

When the DBMS_DELETE alarm occurs, configuration data cannot be delivered or storedwithin 48 hours.



124

Possible CausesCause 1: A database is deleted.

Procedure

Step 1 Follow instructions in 6.4 Restoring the Database by NMS to restore the database.

----End


A.2.6 DBMS_ERROR

DescriptionThe DBMS_ERROR alarm indicates that an error occurred in the processing of the systemdatabase on the system control unit.

Attribute


Major Processing alarm

ParametersNone.

Impact on the SystemWhen the DBMS_ERROR alarm occurs, the system configuration may be lost. As a result, afailure indication is returned for some query and setting commands, and some system functionsare unavailable.

Possible Causesl Cause 1: The database processing fails or the database is damaged.l Cause 2: The NE is faulty.

Procedure

Step 1 Cause 1: The database processing fails or the database is damaged.1. Reset the NE.

If... Then...

The alarm is cleared after the board is reset End the fault handling.

The alarm persists after the board is reset Go to Cause 2.



125

Step 2 Cause 2: The NE is faulty.1. 5.1 Replacing an OptiX RTN 310.

----End


A.2.7 DBMS_PROTECT_MODE

DescriptionThe DBMS_PROTECT_MODE is an alarm indicating that the system database is in protectionmode.

Attribute


Critical Processing alarm

ParametersNone.

Impact on the SystemWhen the DBMS_PROTECT_MODE alarm occurs, the system configuration may be lost. Asa result, the failure indication is returned for some query and setting commands, and some systemfunctions are unavailable.

Possible CausesCause 1: The NE software is frequently reset due to a hardware problem.

ProcedureStep 1 Cold reset the OptiX RTN 310.

Step 2 If the alarm is not cleared, replace the OptiX RTN 310.

----End


A.2.8 DCNSIZE_OVER

DescriptionThe DCNSIZE_OVER alarm indicates an over-sized DCN network.



126

Attribute




Name Meaning

Parameters 1 and 2 Indicate the size of the DCN network.

Impact on the Systeml CPU resources are insufficient. As a result, DCN packets cannot be forwarded immediately

and some NEs are unreachable from the NMS.l The DCN is over-sized, resulting in route flapping or network storms.

Possible CausesCause 1: The size of the DCN network crosses the preset threshold.

Procedure

Step 1 Replan the DCN subnets as required.

----End

Related InformationThe DCNSIZE_OVER alarm occurs when the number of nodes (NEs, NMS servers, and NMSclients in a network segment) on an DCN subnet is greater than 150. The solution is to dividethe DCN subnet.

A.2.9 ERPS_IN_PROTECTION

DescriptionThe ERPS_IN_PROTECTION alarm indicates that a fault on an Ethernet ring protectionswitching (ERPS) ring causes an ERPS switchover.

Attribute


Minor Equipment alarm



127

Parameters

Parameters

When you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For detailsabout each parameter, refer to the following table.

Name Meaning

Parameter 1, Parameter 2 Indicate the ERPS ID.

Parameter 3 Indicates the direction where the fault locates on the ERPS ringagainst the ring protection link (RPL) owner.l 0x00: westl 0x01: east

Parameters 4 to 9 Indicate the MAC address of the faulty node.


Configured services may be interrupted because at least one node on the ERPS ring has lostconnectivity.

Possible Causes

Cause 1: A node on the EPRS ring is faulty.

Procedure

Step 1 Identify the faulty node based on the alarm parameters.

Step 2 Identify the blocked port on the faulty node.

Step 3 Rectify the fault related to the blocked port.

----End

Related Information

None

A.2.10 ETH_CFM_AIS

Description

The ETH_CFM_AIS alarm indicates local MEP AIS. This alarm occurs when the systemreceives AIS messages, indicating that a fault occurred at the server layer.



128

Attribute



Parameters


Name Meaning

Parameters 1 to 4 (Port) Indicate the ID of the alarmed port.

Parameters 5 and 6 (VLAN ID) Indicate the VLAN ID of the MEP.

Parameter 7 (Direction) Indicate the direction of the local MEP.l 0x01: The port is in the ingress direction.l 0x02: The port is in the egress direction.

Parameter 8 (Level) Indicates the maintenance domain (MD) level of the localMEP.l 0x00: operator MEP level (low)l 0x01: operator MEP level (medium)l 0x02: operator MEP level (high)l 0x03: provider MEP level (low)l 0x04: provider MEP level (high)l 0x05: consumer MEP level (low)l 0x06: consumer MEP level (medium)l 0x07: consumer MEP level (high)NOTE

Consumer indicates the user, provider indicates the supplier, andoperator indicates the carrier.

Parameters 9 and 10 (RMEPID) Indicate the ID of the remote MEP.

Impact on the Systeml The LoopBack (LB) and LinkTrace (LT) detection functions of Ethernet service OAM are

unavailable.

l The services between relevant standard MEPs may be interrupted.

Possible Causes

Cause 1: The upstream AIS-activated NE detected a fault in the Ethernet server layer.



129

Procedure

Step 1 Rectify the detected fault in the Ethernet server layer.

----End


A.2.11 ETH_CFM_LOC

DescriptionThe ETH_CFM_LOC alarm indicates the loss of continuity. This alarm occurs when the systemfails to receive CCMs from the remote MEP in 3.5 continuity check (CC) periods successively.

Attribute


Critical Communication alarm


Name Meaning



Parameter 7 (Direction) Indicate the direction of the local MEP.l 0x01: The port is in the ingress direction.l 0x02: The port is in the egress direction.



130

Name Meaning




Impact on the Systeml The LoopBack (LB) and LinkTrace (LT) detection functions of Ethernet service OAM are

unavailable.

l The services between relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The line between the local standard MEP and the remote standard MEP is

interrupted.

l Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.

l Cause 3: Serious congestion occurs on the network.

Procedure

Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.

1. Check whether the physical link between the two standard MEPs is normal.

If... Then...

The physical link is abnormal Rectify the link fault.

The physical link is normal Go to Cause 2.

Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.

1. Check whether the Ethernet service in the MA to which the alarmed MEP belongs isconfigured correctly.



131

If... Then...

The service is configured incorrectly Reconfigure the Ethernet service to ensureconsistency at both ends.

The service is configured correctly Go to Cause 3.

Step 3 Cause 3: Serious congestion occurs on the network.1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth

or eliminate the source that illegally sends a large amount of data.

----End


A.2.12 ETH_CFM_MISMERGE

DescriptionThe ETH_CFM_MISMERGE alarm indicates incorrect connection. This alarm occurs when thesystem receives the CCMs with a mismatched MA ID or a lower priority.

Attribute




Name Meaning



Parameter 7 (Direction) Indicates the direction of the local MEP.l 0x01: The port is in the ingress direction.l 0x02: The port is in the egress direction.



132

Name Meaning





The services between relevant standard MEPs may be interrupted or the dataflow may beincorrectly routed.

Possible Causesl Cause 1: The names of the MD/MA that the standard MEPs correspond to are not the same.

l Cause 2: The physical connection is incorrect.

Procedure

Step 1 Cause 1: The names of the MD/MA that the standard MEPs correspond to are not the same.

1. Check whether the names of the MD/MA that the standard MEPs correspond to are thesame.

If... Then...

They are not the same Reconfigure the names of the MD/MA to ensure consistency atboth ends.

They are the same Go to Cause 2.

Step 2 Cause 2: The physical connection is incorrect.

1. Check the physical connection of the Ethernet service route and rectify the connection fault.

----End

Related Information

None.



133

A.2.13 ETH_CFM_RDI

DescriptionThe ETH_CFM_RDI alarm indicates that the remote maintenance end point (MEP) receivesincorrect continuity check messages (CCMs). This alarm occurs when the system receives CCMswith remote defect indication (RDI).

Attribute


Minor Communication alarm


Name Meaning









134

Impact on the Systeml When the ETH_CFM_RDI alarm occurred, the LoopBack (LB) and LinkTrace (LT)

detection functions of Ethernet service OAM are unavailable.l The services between relevant standard MEPs may be interrupted.

Possible CausesCause 1: The remote MEP receives incorrect CCMs.

Procedure

Step 1 Cause 1: The remote MEP receives incorrect CCMs.1. Determine the alarmed port according to the alarm parameters.2. Check whether the remote MEP connected to the port reported the ETH_CFM_LOC

alarm.

----End


A.2.14 ETH_CFM_UNEXPERI

DescriptionThe ETH_CFM_UNEXPERI alarm indicates errored frames. This alarm occurs when the systemreceives incorrect CCMs.

Attribute




Name Meaning






135

Name Meaning




Impact on the Systeml When the ETH_CFM_UNEXPERI alarm occurred, the LoopBack (LB) and LinkTrace

(LT) detection functions of Ethernet service OAM are unavailable.l Services may become abnormal owing to the loop.

Possible Causesl Cause 1: The configurations of the MEPs at both ends are different.l Cause 2: The service is looped back.

ProcedureStep 1 Cause 1: The configurations such as the CC periods of the MEPs at both ends are different.

1. Check whether the settings of the MEPs at both ends are the same. if not, modify the settingsto ensure consistency at both ends.

Step 2 Cause 2: The service is looped back.1. Check whether any IP ports on the service path are looped back. If yes, release the loop

and clear the alarm.

----End


A.2.15 ETH_EFM_DF

DescriptionThe ETH_EFM_DF alarm indicates a port discovery failure. This alarm occurs when the point-to-point OAM protocol negotiation fails at the Ethernet port.



136

Attribute




Name Meaning

Parameter 1 Indicates the reason why the negotiation fails.

l 0x01: A connection fault occurs at the local end.l 0x02: The local end fails to receive any OAM packets in the specified period.l 0x03: The OAM settings of the remote end do not meet the requirements of

the local end.l 0x04: The OAM settings of the local end do not meet the requirements of the

remote end.l 0x05-0xff: Reserved.

Impact on the SystemWhen the ETH_EFM_DF alarm occurs, the services at the port may be interrupted.

Possible Causesl Cause 1: The physical port at the local end is faulty.l Cause 2: The point-to-point OAM protocol is not enabled at the remote end.l Cause 3: The OAM configuration at both ends is inconsistent.

Procedure

Step 1 Clear the alarm according to the alarm parameters.

If... Then...

The value of Parameter 1 is 0x01 Go to Cause 1.


The value of Parameter 1 is 0x03 or 0x04 Go to Cause 3.

Step 2 Cause 1: The physical port at the local end is faulty.1. Check whether the link connected to the alarmed port is faulty.2. If the link is normal, check whether the alarmed port is faulty. If yes, replace the OptiX

RTN 310.



137

Step 3 Cause 2: The point-to-point OAM protocol is not enabled at the remote end.1. Enable the point-to-point OAM protocol at the remote end.

Step 4 Cause 3: The OAM configuration at both ends is inconsistent.1. Reconfigure the point-to-point OAM protocol to ensure the consistency at both ends.

----End

Related Information

None.

A.2.16 ETH_EFM_EVENT

Description

The ETH_EFM_EVENT alarm indicates that an event occurred on the opposite NE. This alarmoccurs when the local end receives a link error indication packet (OAMPDU) from the oppositeend.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of the link event.

l 0x01: errored symbol periodl 0x02: errored framel 0x03: errored frame periodl 0x04: errored frame seconds


When the ETH_EFM_EVENT alarm occurs, the services at the port may be degraded orinterrupted.

Possible Causesl Cause 1: The link is faulty.



138

l Cause 2: The local NE is faulty.

Procedure

Step 1 Cause 1: The link is faulty.1. Rectify the link fault.

Step 2 Cause 2: The local NE is faulty.1. Replace the OptiX RTN 310.

----End


A.2.17 ETH_EFM_LOOPBACK

DescriptionThe ETH_EFM_LOOPBACK alarm indicates a loopback. This alarm occurs when the local endinitiates a loopback or responds to a loopback request from the opposite end.

Attribute




Name Meaning

Parameter 1 Indicates the state of the loopback.

l 0x01: The local end initiates a loopback.l 0x02: The local end responds to a loop request from the opposite end.

Impact on the SystemWhen the ETH_EFM_LOOPBACK alarm occurs, the services at the port may be looped back.

Possible Causesl Cause 1: The local end initiates a loopback.l Cause 2: The opposite end initiates a loopback.



139

Procedure

Step 1 Determine the loopback initiation end according to the alarm parameters.

Step 2 Cause 1: The local end initiates a loopback.

1. According to the alarm parameter, it is confirmed that the local end initiates a loopback.Find out the cause of the loopback at the local end and release the loopback.

Step 3 Cause 2: The opposite end initiates a loopback.

1. According to the alarm parameter, it is confirmed that the opposite end initiates a loopback.Determine the cause of the loopback at the opposite end and release the loopback.

----End

Related Information

None.

A.2.18 ETH_EFM_REMFAULT

Description

The ETH_EFM_REMFAULT alarm indicates that the opposite NE is faulty. This alarm occurswhen the local end receives the fault indication packet (OAMPDUM) from the opposite end.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the fault type at the opposite end.

l 0x01: link faultl 0x02: dying gaspl 0x03: critical event


When the ETH_EFM_REMFAULT alarm occurs, the services at the port may be interrupted.



140

Possible Causesl Cause 1: The opposite NE is reset frequently.l Cause 2: The opposite NE is faulty.

Procedure

Step 1 Cause 1: The opposite NE is reset frequently.1. Check whether the opposite NE is reset frequently.

If... Then...

The opposite NE is reset frequently Rectify the fault on the opposite NE.

The opposite NE is not reset frequently Reset the opposite NE, and the alarm iscleared.

Step 2 Cause 2: The opposite NE is faulty.1. Rectify the fault on the opposite NE.

----End


A.2.19 ETH_LOS

DescriptionThe ETH_LOS alarm indicates the loss of Ethernet port connection.

Attribute



ParametersNone.

Impact on the SystemWhen the ETH_LOS alarm occurs, the services at the port may be interrupted.

Possible Causesl Cause 1: The working modes of the ports at the local and opposite ends are different.l Cause 2: The link is faulty.l Cause 3: The local NE is faulty.l Cause 4: The opposite NE is faulty.



141

Procedure

Step 1 Cause 1: The working modes of the ports at the local and opposite ends are different.

1. Check for the PORTMODE_MISMATCH alarm by referring to 7.1.3 Browsing CurrentAlarms(U2000).

If... Then...

The PORTMODE_MISMATCH alarmexists

Clear the PORTMODE_MISMATCHalarm.

The PORTMODE_MISMATCH alarmdoes not exist

Go to Cause 2.

Step 2 Cause 2: The link is faulty.

1. Check the network cable or optical fiber connected to the alarmed port.

If... Then...

The network cable is loose or damaged Reconnect the network cable or replace thenetwork cable.

The optical fiber is loose Reconnect the optical fiber.

The SFP module is faulty. Replace the SFP module.

The connection is correct Go to Cause 3.

Step 3 Cause 3: The local NE is faulty.

1. Check whether the alarmed port is faulty.

If... Then...

The port is faulty Replace the local OptiX RTN 310.

The port is not faulty Go to Cause 4.

Step 4 Cause 4: The opposite NE is faulty.

1. Check whether the opposite NE connected to the alarmed port is faulty.

2. Rectify the fault on the opposite NE.

----End

Related Information

None.

A.2.20 ETH_NO_FLOW

Description

The ETH_NO_FLOW alarm indicates that the Ethernet port bears no traffic. This alarm occurswhen an enabled Ethernet port is in link up state but has no traffic.



142

Attribute


Major Service alarm


Name Meaning

Parameter 1 Indicates the direction in which there is no traffic.

l 0x00: receive directionl 0x01: transmission direction

Impact on the SystemWhen the ETH_NO_FLOW alarm occurs, the port bears no traffic.

Possible CausesCause 1: There is no traffic.

Procedure

Step 1 Determine which direction bears no traffic according to the alarm parameter.

If... Then...

There is no traffic in the transmit direction Check whether the service is normal at thelocal end.

There is no traffic in the receive direction Check whether the opposite NE is normal.

----End


A.2.21 ETHOAM_SELF_LOOP

DescriptionThe ETHOAM_SELF_LOOP alarm indicates the MAC port that runs the point-to-point OAMprotocol is looped back. This alarm occurs if a MAC port receives OAM protocol packets sentby itself or the local NE after the loop detection function is enabled.



143

Attribute


Major Environment alarm

Parameters


Name Meaning

Parameter 1 Indicates the loopback type.

l 0x01: self-loop of the portl 0x02: self-loop of the boardl 0x03-0xff: reserved


When the ETHOAM_SELF_LOOP alarm occurs, a network storm may occur due to loopback.

Possible Causesl Cause 1: The cable connected to the port is self-looped, the port joins a looped LAN, or a

PHY/MAC loopback is manually configured at the port.l Cause 2: Two ports on the NE are connected through a cable or join the same LAN.

Procedure

Step 1 Determine the loopback type according to Parameter 1, and then handle the loopbackaccordingly.

If... Then...



Step 2 Cause 1: The cable connected to the port is self-looped, the port joins a looped LAN, or a PHY/MAC loopback is manually configured at the port.

If... Then...

The PHY/MAC loopback is manuallyconfigured at the port

Manually release the PHY/MAC loopback atthe port. If the loopback automatically releasedfunction is enabled, wait five minutes for theautomatic release.



144

If... Then...

The cable connected to the port is self-looped

Reconnect the cables.

The port joins a looped LAN Eliminate the loop on the LAN, or disconnectthe port from the LAN.

Step 3 Cause 2: Two ports on the NE are connected through a cable or join the same LAN.1. Check whether two ports on the NE are connected through a cable or join the same LAN.

If... Then...

The two ports on the NE are connected through acable

Disconnect the cable.

The two ports on the NE join the same LAN Disconnect a port from the LAN.

----End


A.2.22 FLOW_OVER

DescriptionThe FLOW_OVER alarm indicates that the data traffic at the Ethernet port crosses the threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the direction in which the traffic crosses the threshold.

l 0x00: receive directionl 0x01: transmit direction

Impact on the SystemWhen the FLOW_OVER alarm occurs, some data at the port may be discarded.



145

Possible Causesl Cause 1: The traffic threshold at the local port is too low.l Cause 2: The opposite port transmits heavy data traffic.

Procedure

Step 1 Cause 1: The traffic threshold at the local port is too low.1. Follow instructions in Setting the Advanced Attributes for an Ethernet Port to raise the

traffic threshold at the local port. Note that the traffic threshold cannot exceed the rate ofthe local port.

Step 2 Cause 2: The opposite port transmits heavy data traffic.1. Configure the QoS policies at the opposite port to reduce the data traffic from the opposite

port.

----End


A.2.23 HARD_BAD

DescriptionThe HARD_BAD alarm indicates that the hardware is faulty.

Attribute






146

Name Meaning

Parameter 1 Indicates the cause of the fault.

l 0x06: The digital phase-locked loop is abnormal.l 0x0A: The primary crystal oscillator stops oscillating.l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.l 0x0E: The storage component is faulty.l 0x0F: The programmable logic device is faulty.l 0x11: The data communication component is faulty.l 0x12: The clock component is faulty.l 0x15: Other components are faulty.l 0x16: The analog phase-locked loop is abnormal.l 0x1C: The chip of the detection laser fails.l 0x1D: The chip of the compensation laser fails.l 0x25: The PHY chip self-check fails.l 0x26: The port status of the PHY chip cannot be detected.



147

Name Meaning

Parameter 2 Indicates the location of the fault.

When the value of Parameter 1 is 0x06, Parameter 2 has the following meanings:

l 0x01: Phase-locked loop 1 of the system clock is unlocked.l 0x02: Phase-locked loop 2 of the system clock is unlocked.l 0x03: Phase-locked loop 3 of the system clock is unlocked.l 0x04: Phase-locked loop 4 of the system clock is unlocked.

When the value of Parameter 1 is 0x0D, Parameter 2 has the following meanings:

l 0x03: The modem chip is faulty.l 0x04: The RF CPU is faulty.


l 0x01: The system clock component is faulty.l 0x02: The IF clock component is faulty.l 0x03: The 50 MHz IF clock is lost.l 0x04: The 50 MHz associated clock of the modem is lost.l 0x05: The modem fails to restore the DDS clock.l 0x06: The 125 MHz master clock is lost.l 0x07: The 50 MHz master clock is lost.


l 0x01: The TR module is faulty.l 0x02: The IF AD chip is faulty.l 0x03: The IF QMC AD chip is faulty.l 0x04: The IF DA chip is faulty.


l 0x01: The phase-locked loop of the IF clock is unlocked.l 0x02: The transmit phase-locked loop of the TR module is unlocked.l 0x03: The receive phase-locked loop of the TR module is unlocked.


l 0x01: The GE1 PHY chip is faulty.l 0x02: The GE2 PHY chip is faulty.


When the HARD_BAD alarm occurs, the NE cannot work.

Possible Causes

Cause 1: The NE hardware is faulty.



148

Procedure


----End


A.2.24 IN_PWR_ABN

DescriptionThe IN_PWR_ABN alarm indicates that the input optical power is abnormal.

Attribute



ParametersNone.

Impact on the SystemWhen the IN_PWR_ABN alarm occurs, bit errors occur in the services at the port, which maylead to service interruption.

Possible Causesl Cause 1: The transmit optical power of the opposite NE is too high or low.l Cause 2: The model of the optical module is improper.l Cause 3: The receive optical module of the local NE is faulty.

Procedure

Step 1 Cause 1: The transmit optical power of the opposite NE is too high or low.1. Check whether the transmit optical power of the opposite NE is proper. If no, replace the

optical module.

Step 2 Cause 2: The model of the optical module is improper.1. Query the board manufacturing information report, and check whether the models of

the SFP optical modules used at both ends are proper.

If... Then...

The models are improper Replace the optical module.

The models are proper Go to Cause 3.



149

Step 3 Cause 3: The receive optical module of the local NE is faulty.1. Use an optical power meter to measure the receive optical power, and check whether the

receive optical power meets the requirement. If yes, replace the SFP module.

----End


A.2.25 LAG_DOWN

DescriptionThe LAG_DOWN alarm indicates that the link aggregation group (LAG) is unavailable. Thisalarm occurs when no member port in a LAG is activated.

Attribute



ParametersNone.

Impact on the SystemWhen the LAG_DOWN alarm occurs, services at all ports in the LAG are interrupted.

Possible CausesCause 1: All member ports in the LAG fail.

Procedure

Step 1 Follow instructions in LAG_MEMBER_DOWN to troubleshoot each member port in the LAG.

----End


A.2.26 LAG_MEMBER_DOWN

DescriptionThe LAG_MEMBER_DOWN alarm indicates that a member port in a LAG is unavailable. Thisalarm occurs when a member port in a LAG cannot be activated or standby.



150

Attribute




Name Meaning

Parameters 1 and 2 Indicate the slot ID of the alarmed board.

Parameter 3 Indicates the subslot ID of the alarmed subboard. The value of thisparameter is always 0xff.

Parameters 4 and 5 Indicate the ID of the alarmed port.

Parameter 6 Indicates the cause of the fault.l 0x01: The port is in the link-down or disabled state.l 0x02: The port receives no LACP packet.l 0x03: The port works in half-duplex mode.l 0x04: The port is self-looped.

Impact on the SystemWhen the LAG_MEMBER_DOWN alarm occurs, the alarmed port in the LAG cannot shareany service load. The port does not receive or transmit any services.

Possible Causesl Cause 1: The link connected to the port is faulty or blocked.l Cause 2: The port receives no LACP packet.l Cause 3: The port is self-looped.

ProcedureStep 1 Determine the alarmed port and the cause according to the alarm parameters.

If... Then...

The value of Parameter 6 is 0x01 Go to Step 2.



Step 2 Cause 1: The link connected to the alarmed port is faulty or blocked.1. Follow instructions in Querying the Protocol Information About a LAG to check whether

the port is enabled.



151

If... Then...

The port is disabled Enable the port in the LAG.

The port is enabled Go to the next step.

2. Check the links connected to all member ports. See whether the ETH_LOS or MW_LOFalarm exists.

If... Then...

The ETH_LOS or MW_LOF alarmexists

Handle the ETH_LOS or MW_LOFalarm.

The ETH_LOS or MW_LOF alarm doesnot exist

Go to Cause 2.

Step 3 Cause 2: The port receives no LACP packet.1. Follow instructions in Querying the Protocol Information About a LAG to check whether

the local and remote ports transmit any LACP packets. If no, reconfigure the ports at bothends so LACP packets can be normally transmitted.

Step 4 Cause 3: The port is self-looped.1. Follow instructions in Setting the Advanced Attributes for an Ethernet Port to check

whether the port is self-looped. If yes, release the loopback at the port by referring to 7.4.1Setting Loopbacks for Ethernet Ports.

----End

Related Information

None.

A.2.27 LASER_MOD_ERR

Description

The LASER_MOD_ERR alarm indicates that the SFP module mismatches the optical port.

Attribute



Parameters

None.


When the LASER_MOD_ERR alarm occurs, the performance of the optical port degrades,which even causes service interruption.



152

Possible Causesl Cause 1: The NE does not support the type of the installed SFP module.

l Cause 2: The optical module is faulty.

l Cause 3: The NE is faulty.

Procedure

Step 1 Cause 1: The NE does not support the type of the installed SFP module.

1. Follow instructions in 7.3.3 Querying the Board Manufacturing Information Report(U2000) to check whether the optical module of the optical port matches the rate of theoptical port.

If... Then...

The optical module of the optical portdoes not match the rate of the opticalport

Contact Huawei engineers to replace theoptical module.

The optical module of the optical portmatches the rate of the optical port

Go to Cause 2.

Step 2 Cause 2: The optical module is faulty.

1. Replace the optical module.

If... Then...

The alarm clears after the optical module is replaced End the alarm handling.

The alarm persists after the optical module is replaced Go to Cause 3.

Step 3 Cause 3: The NE is faulty.

1. Replace the OptiX RTN 310.

----End

Related Information

None.

A.2.28 LCS_LIMITED

Description

The LCS_LIMITED alarm indicates that an NE is configured with a service capacity or functionbeyond the license permission.

Attribute





153


Name Meaning

Parameter 1 Indicates the license alarm type.

l 0x01: The service capacity is beyond the license permission.l 0x02: The AM license is not loaded.l 0x04: The IEEE 1588v2 license is not loaded.l 0x09: The license for air-interface frame header compression is not loaded.l 0x0d: The license for the GE2 port is not loaded.l 0x0e: The XPIC license is not loaded.l 0x0f: The ERPS license is not loaded.

Impact on the SystemWhen the LCS_LIMITED alarm occurs, the NE is configured with a service capacity or functionbeyond the license permission.

Possible Causesl Cause 1: The purchased license is not loaded.l Cause 2: The service capacity or function is beyond the license permission.

Procedure

Step 1 Query the license capacity on the NMS. Determine the license alarm type according to thealarm parameter.

Step 2 If the value of Parameter 1 is 0x01, see Setting Traffic Shaping for Egress Queues to checkwhether the PIR is beyond the license permission. If yes, decrease the service capacity, orpurchase and load a new license to support the service capacity.

Step 3 If the current license does not support a function, purchase and load a new license, too.

----End


A.2.29 LICENSE_LOST

DescriptionThe LICENSE_LOST alarm indicates that the NE fails to detect the license file.



154

Attribute




Name Meaning

Parameter 1 Indicates the type of the license file.

l 0x06: NE licensel 0x07: Ethernet license

Impact on the SystemWhen the LICENSE_LOST alarm occurs, the functions authorized by the license file cannottake effect.

Possible CausesCause 1: The license file is lost or is not loaded.

Procedure

Step 1 Cause 1: The license file is lost or is not loaded.1. Contact Huawei engineers to load the license file.

----End


A.2.30 LOOP_ALM

DescriptionThe LOOP_ALM alarm indicates loopback.

Attribute





155

Parameters


Name Meaning

Parameter 1 Indicates the type of loopback.

l 0x00: optical/electrical port inloopl 0x01: optical/electrical port outloopl 0x0A: PHY layer inloopl 0x0C: MAC layer inloopl 0x14: IF outloopl 0x15: IF inloopl 0x16: RF inloop


When the LOOP_ALM alarm occurs, services at the alarmed port are interrupted.

Possible Causes

Cause 1: Loopback is performed on the NE.

Procedure

Step 1 Determine the type of loopback according to the alarm parameter.

Step 2 Find out why loopback was performed, and set the loopback status of the alarmed port to Non-Loopback.

For details of loopback operations, see Software Loopback.

----End

Related Information

None.

A.2.31 LSR_NO_FITED

Description

The LSR_NO_FITED alarm indicates that the SFP optical module is not installed.



156

Attribute



ParametersNone.

Impact on the SystemWhen the LSR_NO_FITED alarm occurs, the port cannot bear services.

Possible Causesl Cause 1: The SFP optical module on the local NE is not installed.l Cause 2: The optical module is faulty.

Procedure

Step 1 Cause 1: The SFP optical module on the local NE is not installed.1. Find out why the SFP optical module is not installed, and install it as soon as possible.

Step 2 Cause 2: The optical module is faulty.1. Replace the SFP optical module.

----End


A.2.32 LTI

DescriptionThe LTI alarm indicates that the synchronization sources are lost. This alarm occurs when anNE loses all synchronization sources.

Attribute






157

Name Meaning

Parameter 1 0x01: system clock priority table


When the LTI alarm occurs, the system clock quality is not high. The bit error rate will increasewhen the NEs are not synchronized.

Possible Causesl Cause 1: The clock configuration is incorrect.

l Cause 2: All the clock sources in the clock source priority table fail.

l Cause 3: The synchronization source is set to the manual reversion mode.

Procedure

Step 1 Cause 1: The clock configuration is incorrect.

1. Follow instructions in Configuring Clock Sources to check the clock source priority tableaccording to the network plan.

If... Then...

The clock source priority table isconfigured incorrectly

Reconfigure the clock source priority table.

The clock source priority table isconfigured correctly

Go to Cause 2.

Step 2 Cause 2: All the clock sources in the clock source priority table fail.

1. Check whether the SYNC_C_LOS alarm exists. If yes, handle the SYNC_C_LOS alarm.

Step 3 Cause 3: The synchronization source is set to the manual reversion mode.

1. Follow instructions in Changing Clock Source Reversion Parameters to set the clock sourceto the automatic reversion mode.

----End

Related Information

None.

A.2.33 MAC_EXT_EXC

Description

The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crossesthe threshold.



158

Attribute




Name Meaning

Parameter 1 Indicates the threshold crossing type.

l 0x01: ETHDROP threshold crossingl 0x03: RXBBAD threshold crossing

Impact on the SystemWhen the MAC_EXT_EXC alarm occurs, the service performance deteriorates.

Possible Causesl Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the upper

threshold.l Cause 2: RXBBAD threshold crossing. The number of received bad packets crosses the

upper threshold.

Procedure

Step 1 Check whether the working modes of the ports at the transmit and receive ends are the same.1. On the NMS, query the working modes of the ports at both ends.

If... Then...

The ports at both ends work in differentmodes or in half-duplex mode

Set the working modes of the two ports toboth full-duplex or auto-negotiation byreferring to Setting the Basic Attributes foran Ethernet Port.

The ports at both ends work in the samemode and are not working in half-duplex mode

Go to the next step.

Step 2 Handle the packet transmission errors at the opposite end.

Step 3 Handle the line quality problem.Check whether the local end reports the alarms (ETH_LOS, for example) due to the damage toor large attenuation over the external line. If yes, clear these alarms.



159


----End


A.2.34 MAC_FCS_EXC

DescriptionThe MAC_FCS_EXC alarm indicates that the number of bit errors at the MAC layer crosses thethreshold. The software periodically computes whether the number of bit errors crosses thethreshold by comparing the number of service bytes and the number of bit errors received onthe MAC chip. The MAC_FCS_EXC alarm occurs when the number of bit errors crosses thethreshold.

Attribute



ParametersNone.

Impact on the SystemWhen the MAC_FCS_EXC alarm occurs, the service performance deteriorates.

Possible CausesCause 1: ETHFCS threshold crossing. The number of received Ethernet data frames with FCScheck errors crosses the threshold.

Procedure

Step 1 Check whether the working modes of the ports at both ends are the same.1. On the NMS, query the working modes of the ports at both ends.

If... Then...

The ports at both ends work in differentmodes or in half-duplex mode

Set the working modes of the two ports toboth full-duplex or auto-negotiation byreferring to Setting the Basic Attributes foran Ethernet Port.

The ports at both ends work in the samemode and are not working in half-duplex mode




160


----End


A.2.35 MULTI_RPL_OWNER

DescriptionThe MULTI_RPL_OWNER alarm indicates that the Ethernet ring network contains several RPLowner nodes.

Attribute


Minor Maloperation alarm


Name Meaning

Parameters 1 and 2 Indicate the ID of the ERPS instance.

Impact on the SystemThe MULTI_RPL_OWNER alarm occurs, ERPS protection fails and the services on theEthernet ring are interrupted.

Possible CausesCause: The ERPS protection is configured incorrectly.

Procedure

Step 1 See Querying the Status of the ERPS Protocol to check the ERPS protection configuration ateach node. Ensure that there is only one RPL owner node on the Ethernet ring network.

----End




161

A.2.36 MW_AM_TEST

DescriptionThe MW_AM_TEST alarm indicates that the IF port is in the AM testing state.

Attribute


Minor Other alarms

ParametersNone.

Impact on the SystemWhen the MW_AM_TEST alarm occurs, the service transmission capacity decreases during theAM test.

Possible CausesCause 1: The AM test is being performed.

ProcedureStep 1 This alarm automatically clears after the AM test is complete.

----End


A.2.37 MW_BER_EXC

DescriptionThe MW_BER_EXC is an alarm of excessive bit errors on a radio link. This alarm is reportedwhen bit errors on a radio link exceed the specified MW_BER_EXC threshold (10-3 by default).

Attribute


Minor Service alarm

ParametersNone.



162

Impact on the SystemServices at the alarmed port are interrupted.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.l Cause 2: The transmit unit of the opposite site is faulty.l Cause 3: The receive unit of the local site is faulty.l Cause 4: An interference source exists around the radio link.

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is too heavy.1. With reference to Querying History Transmit Power and Receive Power, check whether

the receive power of the OptiX RTN 310 at the local site is normal. If no, diagnose the faultand take proper measures.

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna toensure that the azimuth angle of the antennameets the requirement.

2. Check the antenna direction. Especially,check whether the received signal is from themain lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check the polarization direction of antennasand adjust the incorrect polarizationdirection.

4. Check the antenna gain at the two ends andreplace the antennas that do not providerequired antenna gain.

5. Check whether transmission is blocked byany mountains or buildings.If yes, contact the network planningdepartment for avoiding the block.



163

If... Then...

The RSL is higher than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours

Slow up fading occurs. Follow the steps:

1. Check for interference. For details, see 7.9Scanning Interfering Signals.

2. Use a spectrum analyzer to analyzeinterference sources.

3. Contact the spectrum managementdepartment for clearing the interferencespectrum, or change plans to minimize theinterference.

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibels. The duration is from tens ofseconds to several hours

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow down fading is imposed by thetransmission path. Contact the networkplanning department to make the followingchanges:

l Increase the installation heights of antennas.l Reduce the transmission distance.l Increase the antenna gain.l Increase the transmit power.

The RSL is lower than or higher than thespecified RSL of the network and theduration is from several milliseconds totens of seconds

Fast fading occurs. Contact the networkplanning department to make the followingchanges:

l Adjust the position of the antenna to blockthe reflected wave or make the reflectionpoint fall on the ground that has a smallreflection coefficient, reducing multipathfading.

l Increase the fading margin.

Step 2 Cause 2: The transmit unit of the opposite site is faulty.

1. Perform an inloop on the IF port at the opposite end. For details, see 7.4.2 Setting Loopbackfor the IF Board. Check whether the fault at the opposite site is rectified.

If... Then...

The alarm persists Replace the OptiX RTN 310 at the opposite site.

The alarm clears Go to the next step.

Step 3 Cause 3: The receive unit of the local site is faulty.

Locate the fault by looping back the opposite site and excluding the position one by one. Followthe steps:

1. Perform an inloop on the IF port at the local end. For details, see 7.4.2 Setting Loopbackfor the IF Board. Check whether the fault at the local site is rectified after the loopback.



164

If... Then...

The alarm persists Replace the OptiX RTN 310 at the local site.


Step 4 Cause 4: An interference source exists around the radio link.

1. With reference to 7.9 Scanning Interfering Signals, scan the frequency spectrum aroundthe radio link and check for co-frequency interference and bias-frequency interference.

2. Use a spectrum analyzer to analyze interference sources.

3. Contact the spectrum management department for clearing the interference spectrum, orchange plans to minimize the interference.

----End

Related Information

None.

A.2.38 MW_BER_SD

Description

The MW_BER_SD is an alarm of signal degrade on a radio link. This alarm is reported whenbit errors on a radio link exceed the MW_BER_SD threshold (10-6 by default) but does not reachthe MW_BER_EXC alarm threshold (10-3 by default).

Attribute


Minor Service alarm

Parameters

None.


The service performance on the alarmed port deteriorates.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.

l Cause 2: The transmit unit of the opposite site is faulty.

l Cause 3: The receive unit of the local site is faulty.

l Cause 4: An interference source exists around the radio link.

l Cause 5: A loop is performed on the composite port.



165

Procedure



If... Then...


Follow the steps:













166

If... Then...










If... Then...






If... Then...








167


Step 5 Cause 5: A loop is performed on the composite port.1. Find out the cause of the loopback, and wait five minutes for the automatic release.

Otherwise, you can manually release the loopback.

----End


A.2.39 MW_CFG_MISMATCH

DescriptionThe MW_CFG_MISMATCH is an alarm of configuration mismatch on radio links. This alarmis reported when an NE detects inconsistent settings of AM status, 1588 overhead status,modulation scheme, or other parameters on the two ends of a radio link.

Attribute




Name Meaning

Parameter 1 Indicates the cause of the alarm.

l 0x02: The AM status is configured differently.l 0x03: The 1588 overhead status is configured differently.l 0x04: The modulation scheme is configured differently.l 0x09: The IP frame header compression is configured differently.

Parameter 2 If Parameter 1 takes the value of 0x09, Parameter 2 has the following meanings.

l 0x01: The L2 frame header compression is configured differently.l 0x02: The L3 frame header compression is configured differently.

Impact on the SystemThis alarm indicates that service configurations do not take effect or services are interrupted.After the NE is power cycled or reset, the services may still be affected.



168

Possible Causesl Cause 1: The AM status is configured differently at the two ends.

l Cause 2: The 1588 overhead status is configured differently at the two ends.

l Cause 3: The modulation scheme is configured differently at the two ends.

l Cause 4: The IP frame header compression is configured differently at the two ends.

Procedure

Step 1 Determine the cause of the alarm by querying the alarm parameters.

Step 2 Check the configurations on both ends of the radio link. Ensure that the configurations areconsistent. For details, see Configuring a Single-Hop Radio Link or Creating VLAN ForwardingTable Entries.

----End

Related Information

None.

A.2.40 MW_CONT_WAVE

Description

The MW_CONT_WAVE is an alarm of the enabled continuous wave function. This alarmoccurs if the continuous wave is output by the IF unit.

Attribute



Parameters

None.


If the continuous wave function is enabled, radio links cannot transmit services.

Possible Causesl Cause 1: The continuous wave function is enabled.

l Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on theIF port.

l Cause 3: The IF unit is faulty.



169

Procedure

Step 1 Cause 1: The continuous wave function is enabled.

1. Disable the continuous wave function. For details, see 7.6 Detecting ConsecutiveWaves.

Step 2 Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the IFport.

1. Release the loopback by referring to 7.4.2 Setting Loopback for the IF Board.

2. Clear the MW_LOF alarm.

Step 3 Cause 3: The IF unit is faulty.

1. Replace the OptiX RTN 310.

----End

Related Information

The continuous wave function tests the frequency stability and frequency consistency and shouldbe disabled after a test is completed.

A.2.41 MW_FEC_UNCOR

Description

The MW_FEC_UNCOR is an alarm indicating that errors in the microwave frames cannot becorrected by using FEC.

Attribute



Parameters

None.


This alarm indicates that services contain bit errors.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.


l Cause 3: The receive unit of the local site is faulty.




170

Procedure



If... Then...


Follow the steps:













171

If... Then...










If... Then...






If... Then...








172


----End


A.2.42 MW_LIM

DescriptionThe MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. Thisalarm is reported if an IF board detects that the link ID in the microwave frame overheads isinconsistent with the specified link ID.

Attribute



ParametersNone.

Impact on the SystemThe IF board inserts the AIS alarm into the received signal, causing service interruption on theradio link.

Possible Causesl Cause 1: The link ID of the local site does not match the link ID of the opposite site.l Cause 2: The services on other radio links are received due to the incorrect configuration

of the radio link receive frequency at the local or opposite site.l Cause 3: The antenna receives microwave signals from another site, because the direction

of the antenna is set incorrectly.l Cause 4: The polarization direction of the XPIC is incorrect.

Procedure

Step 1 With reference to Browsing the Performance of a Hop of Radio Link, check the settings of linkID, receive/transmit frequency, polarization direction of the XPIC working group at the twoends. If any setting is incorrect, modify it according to the network planning information.

Step 2 Cause 3: The antenna receives microwave signals from another site, because the direction of theantenna is set incorrectly.1. Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.

----End



173

Related Information

The MW_LIM alarm is generated due to the inconsistency between the specified link ID andthe received link ID. If the MW-LOF alarm exists on the link, the received link ID is a randomvalue and therefore is invalid. In this case, the MW-LIM alarm is suppressed.

A.2.43 MW_LOF

Description

The MW_LOF is an alarm indicating the loss of microwave frames.

Attribute



Parameters

None.


This alarm indicates that services are interrupted.

Possible Causesl Cause 1: Certain other alarms occur.

l Cause 2: Settings of channel spacing, modulation scheme, and operating frequency aredifferent at the two ends of the radio link.


l Cause 4: The receive power of the OptiX RTN 310 is abnormal.


Procedure

Step 1 Cause 1: Certain other alarms occur.

1. Check whether any equipment-related alarms are reported at the local site. If yes, clearthem immediately.The possible alarms are as follows:

l HARD_BAD

l RADIO_RSL_LOW

l TEMP_ALARM

Step 2 Cause 2: Settings of channel spacing, modulation scheme, and operating frequency are differentat the two ends of the radio link.



174

1. With reference to Browsing the Performance of a Hop of Radio Link, check the settings ofchannel spacing, modulation scheme, and operating frequency at the two ends of the radiolink.

2. With reference to Configuring a Single-Hop Radio Link, modify the different settings.

Step 3 Cause 3: The transmit unit of the opposite site is faulty.1. Check whether any equipment-related alarms are reported at the opposite site. If yes, clear

them immediately.The possible alarms are as follows:l HARD_BADl RADIO_RSL_LOWl TEMP_ALARM

2. Locate the fault by performing loopbacks at the opposite site.

Follow the steps:

a. Perform an inloop on the IF port at the opposite site. For details, see 7.4.2 SettingLoopback for the IF Board. Check whether the fault at the opposite site is rectified.

If... Then...



Step 4 Cause 4: The receive power of the OptiX RTN 310 is abnormal.1. With reference to Querying History Transmit Power and Receive Power, check whether




175

If... Then...


Follow the steps:

a. Check the installation of the antenna toensure that the azimuth angle of theantenna meets the requirement.

b. Check the antenna direction. Especially,check whether the received signal is fromthe main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

c. Check the polarization direction ofantennas and adjust the incorrectpolarization direction.

d. Check the antenna gain at the two endsand replace the antennas that do notprovide required antenna gain.

e. Check whether transmission is blocked byany mountains or buildings.If yes, contact the network planningdepartment for avoiding the block.

The RSL is higher than the specifiedRSL of the network. The offset value istens of decibels. The duration is fromtens of seconds to several hours


a. Check for co-channel interference. Fordetails, see 7.9 Scanning InterferingSignals.

b. Use a spectrum analyzer to analyzeinterference sources.

c. Contact the spectrum managementdepartment for clearing the interferencespectrum, or change plans to minimize theinterference.

The RSL is lower than the specifiedRSL of the network. The offset value istens of decibels. The duration is fromtens of seconds to several hours

Slow down fading occurs. Generally, theradio link may be faulty in both directions,because slow down fading is imposed by thetransmission path. Contact the networkplanning department to make the followingchanges:

l Increase the installation heights ofantennas.

l Reduce the transmission distance.l Increase the antenna gain.l Increase the transmit power.



176

If... Then...

The RSL is lower than or higher thanthe specified RSL of the network andthe duration is from severalmilliseconds to tens of seconds




Step 5 Cause 5: Interference exists.1. With reference to 7.9 Scanning Interfering Signals, scan the frequency spectrum around

the radio link and check for co-frequency interference and bias-frequency interference.2. Use a spectrum analyzer to analyze interference sources.3. Contact the spectrum management department for clearing the interference spectrum, or

change plans to minimize the interference.

----End

Related Information

None.

A.2.44 MW_RDI

Description

The MW_RDI is an alarm indicating that there are defects at the remote end of the radio link.This alarm is reported when the IF board detects an RDI in the radio frame overheads.

Attribute



Parameters

None.


This alarm indicates that services are interrupted in the receive direction of the opposite site.

Possible Causes

Cause: The opposite site detects service alarms in the receive direction.



177

Procedure

Step 1 Handle the microwave alarms at the opposite site. The possible alarms are as follows:l MW_LOFl XPIC_LOSl MW_BER_SDl MW_BER_EXC

----End


A.2.45 NB_UNREACHABLE

DescriptionThe NB_UNREACHABLE is an alarm indicating that a neighboring NE is unreachable to thelocal NE.

Attribute



ParametersNone.

Impact on the SystemThe XPIC working group is abnormal.

Possible Causesl Cause 1: The XPIC cable is loose.l Cause 2: Configurations on the neighboring OptiX RTN 310 are inconsistent.l Cause 3: The neighboring NE is abnormal.

Procedure

Step 1 Cause 1: The XPIC cable is loose.1. Check whether the XPIC cable is loose. If yes, connect the cable correctly.

Step 2 Cause 2: Configurations on the neighboring OptiX RTN 310 are inconsistent.1. Check whether the XPIC function is enabled on the COMBO ports of the OptiX RTN

310. If no, enable the XPIC function.



178

Step 3 Cause 3: The neighboring NE is abnormal.1. Troubleshoot the faulty on the neighboring NE.

----End


A.2.46 NESF_LOST

DescriptionThe NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported whenthe system control unit detects the loss of NE software.

Attribute




Name Meaning

Parameter 1 The value is always 0x01.



179

Name Meaning

Parameters 2 and 3 Indicate the file code.

l 0x01: FPGA of the system control board in the OFS1 areal 0x02: FPGA of the system control board in the OFS2 areal 0x03: ofs1/hwx/nesoft.hwxl 0x04: ofs2/hwx/nesoft.hwxl 0x05: ofs1/hwx/ne.inil 0x06: ofs2/hwx/ne.inil 0x07: ofs1/hwx/ocp.inil 0x08: ofs2/hwx/ocp.inil 0x1f: ofs1/hwx/extbios.hwxl 0x20: ofs2/hwx/extbios.hwxl 0x23: ofs1/hwx/trsoft.hwxl 0x24: ofs2/hwx/trsoft.hwxl 0x25: ofs1/hwx/ifmodem.hwxl 0x26: ofs2/hwx/ifmodem.hwxl 0x27: ofs1/fpga/ifmodem.pgal 0x28: ofs2/fpga/ifmodem.pga

Parameter 4 Indicates the cause of the alarm.

l 0x01: The file does not exist.l 0x02: The file check fails.

Impact on the SystemIf the NE software is lost, the system cannot reboot after it is powered off or reset.

Possible Causesl Cause 1: No new NE software is loaded after the existing NE software is erased.l Cause 2: Loading the NE software is unsuccessful.l Cause 3: The NE is faulty.

ProcedureStep 1 Check whether the alarm is caused by the loading operation.

If... Then...

The alarm is caused by the loadingoperation

Contact the Huawei technical supportengineers for loading the NE software.

The alarm is not caused by the loadingoperation

5.1 Replacing an OptiX RTN 310.

----End



180


A.2.47 NESOFT_MM

DescriptionThe NESOFT_MM is an alarm indicating that the software files in the OFS1 and OFS2 areasof the system control unit are inconsistent. This alarm is reported when the software files in theOFS1 and OFS2 areas of the system control unit are inconsistent.

Attribute


Major Processing alarm


Name Meaning

Parameter 1 Indicates the location of the file.l 0x01: files in the flash memoryl 0x02: software that is currently running



181

Name Meaning

Parameters 2 and 3 If Parameter 1 takes the value of 0x01, Parameters 2 and 3 indicate theinconsistent files in the flash memory.l 0x01: FPGA of the system control board in the OFS1 areal 0x02: FPGA of the system control board in the OFS2 areal 0x03: ofs1/hwx/nesoft.hwxl 0x04: ofs2/hwx/nesoft.hwxl 0x05: ofs1/hwx/ne.inil 0x06: ofs2/hwx/ne.inil 0x07: ofs1/hwx/ocp.inil 0x08: ofs2/hwx/ocp.inil 0x1f: ofs1/hwx/luexbios.hwxl 0x20: ofs2/hwx/luexbios.hwxl 0x23: ofs1/hwx/trsoft.hwxl 0x24: ofs2/hwx/trsoft.hwxl 0x25: ofs1/hwx/ifmodem.hwxl 0x26: ofs2/hwx/ifmodem.hwxl 0x27: ofs1/fpga/ifmodem.pgal 0x28: ofs2/fpga/ifmodem.pga

If Parameter 1 takes the value of 0x02, Parameters 2 and 3 indicate theinconsistent files in the currently running software.

l 0x01: NeSoft(D)l 0x02: Platform(D)l 0x04: ExtBiosl 0x05: Logicl 0x06: Dsp

Parameter 4 Indicates the cause of the alarm.l 0x04: The software files in the OFS1 and OFS2 areas of the system

control unit are inconsistent.

Impact on the SystemAfter the system is powered off or reset, the system may fail to reboot or work correctly.

Possible CausesCause 1: Software files in the OFS1 and OFS2 areas of the system control unit are inconsistent.

Procedure

Step 1 Contact Huawei technical support engineers for loading the software.

----End



182


A.2.48 NTP_SYNC_FAIL

DescriptionThe NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.

Attribute



ParametersNone.

Impact on the SystemTime on the alarmed NE is different from time on the NTP server. The records on the NE, suchas performance events, alarms, and operations, cannot be kept with exact time.

Possible Causesl Cause 1: The NTP server is not configured or is configured incorrectly.l Cause 2: The NTP server cannot communicate with the NE.l Cause 3: The NTP server fails.

Procedure

Step 1 Cause 1: The NTP server is not configured or is configured incorrectly.1. Configure the NTP server correctly.2. Configure the NTP parameters for the NE.

Step 2 Cause 2: The NTP server cannot communicate with the NE.1. Check whether the cable connecting the gateway NE to the NTP server is normal. If no,

rectify the connection fault.2. Check whether the DCN communication between the NTP server and the NE is normal. If

no, configure the DCN communication correctly.

Step 3 Cause 3: The NTP server fails.1. Troubleshoot the NTP server.

----End




183

A.2.49 PASSWORD_NEED_CHANGE

Description

The PASSWORD_NEED_CHANGE alarm indicates that the password of the user who logs inis unchanged. This alarm is reported if any one default user's default password is not changedin time.

Attribute


Major Service alarm

Parameters

None.


The default user's default password must be changed to reduce risks.

Possible Causes

Cause 1: The default user's default password must be changed to reduce risks.

Procedure

Step 1 Modify the default user's password.

----End

Related Information

None.

A.2.50 PATCH_ACT_TIMEOUT

Description

The PATCH_ACT_TIMEOUT is an alarm indicating that patch package activation times out.This alarm occurs when a patch package stays in the activate state for a period longer than thepreset threshold. In this case, users need to handle the patch package.

Attribute





184

Parameters

None.


This alarm does not affect the system.

Possible Causes

Cause: A patch package stays in the activate state for a period longer than the preset threshold.

Procedure

Step 1 Cause: A patch package stays in the activate state for a period longer than the preset threshold.1. Check whether the patch package is normal.2. If yes, run the patch package. If no, deactivate and delete the patch package. The alarm will

clear.

----End

Related Information

None.

A.2.51 PATCH_DEACT_TIMEOUT

Description

The PATCH_DEACT_TIMEOUT is an alarm indicating that patch package deactivation timesout. This alarm occurs when a patch package stays in the deactivate state for a period longerthan the preset threshold. In this case, users need to handle the patch package.

Attribute



Parameters

None.


This alarm does not affect the system.

Possible Causes

Cause: A patch package stays in the deactivate state for a period longer than the preset threshold.



185

Procedure

Step 1 Cause: A patch package stays in the deactivate state for a period longer than the preset threshold.

1. If the patch package is expected to take effect, activate the patch package.

2. Otherwise, delete the patch package and the alarm will clear.

----End

Related Information

None.

A.2.52 PATCH_PKGERR

Description

The PATCH_PKGERR is an alarm indicating that a patch package is abnormal.

Attribute



Parameters

None.


The patch package cannot be loaded, activated, or ran correctly. This alarm does not affectservices.

Possible Causesl Cause 1: The patch package is incorrect.

l Cause 2: The patch package is corrupted.

l Cause 3: The patch package is deleted.

Procedure

Step 1 Load the correct patch package.

----End

Related Information

None.



186

A.2.53 PORT_EXC_TRAFFIC

DescriptionThe PORT_EXC_TRAFFIC is an alarm indicating that the bandwidth utilization ratio of a portexceeds the threshold. This alarm is reported when the bandwidth utilization ratio of a portexceeds the preset threshold.

Attribute


Warning Service alarm


Name Meaning

Parameter 1 Indicates the transmit or receive direction.

l 0x00: receivel 0x01: transmit

Impact on the SystemExcessive service traffic may cause service congestion.

Possible Causesl Cause 1: The configured bandwidth limit is too low.l Cause 2: The port handles excessive traffic.

Procedure

Step 1 Cause 1: The configured bandwidth limit is too low.1. With reference to Setting Traffic Shaping for Egress Queues, check the configured

bandwidth limit.2. If the bandwidth limit of the Ethernet port is too low, increase the bandwidth limit according

to Configuring Port Shaping or expand the network.3. If the bandwidth of the IF port is too low, use a higher order modulation scheme and increase

the channel spacing according to Configuring a Single-Hop Radio Link.

Step 2 Cause 2: The port handles excessive traffic.1. With reference to 7.14 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization

of Ethernet Ports, query the bandwidth utilization ratio of the alarmed port.



187

2. If the port bandwidth utilization is higher than the threshold, check whether a network stormoccurs. If a network storm occurs, eliminate the source that transmits a large amount ofinvalid data.

----End

Related Information

None.

A.2.54 PORTMODE_MISMATCH

Description

The PORTMODE_MISMATCH is an alarm indicating that the working mode of the oppositeEthernet port mismatches that of the local Ethernet port. For example, if the local Ethernet portworks in auto-negotiation mode and the opposite Ethernet port works in another mode, thePORTMODE_MISMATCH alarm will be reported.

Attribute


Minor Service alarm

Parameters


Name Meaning

Parameters 1 and 2 Indicate the current working mode.

l 0x01: auto-negotiationl 0x02: 10M full-duplexl 0x03: 100M full-duplexl 0x04: 1000M full-duplex


This alarm does not affect services.

Possible Causes

Cause: The local Ethernet port and opposite Ethernet port work in different modes.



188

Procedure

Step 1 With reference to Setting the Basic Attributes for an Ethernet Port, disable the local port. Withreference to Setting the Basic Attributes for an Ethernet Port, enable the local port and set theworking mode to auto-negotiation.

----End

Related Information

None.

A.2.55 POWER_ALM

Description

The POWER_ALM is an alarm indicating that the voltage of the power module is out of thenormal range.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the power channel with abnormal voltage.l 0x01: 1.0 V power channel of the baseband processing unitl 0x02: 1.2 V power channel of the baseband processing unitl 0x03: 1.8 V power channel of the baseband processing unitl 0x04: FPGA_SERDES 1.2 V power channel of the baseband processing unitl 0x05: 2.5 V power channel of the baseband processing unitl 0x06: 3.3 V power channel of the baseband processing unitl 0x07: 3.7 V power channel of the baseband processing unitl 0x08: 5.4 V power channel of the baseband processing unitl 0x09: 15 V power channel of the radio frequency processing unitl 0x0A: -6 V power channel of the radio frequency processing unitl 0x0B: 5.4 V power channel of the radio frequency processing unitl 0x0C: 3.7 V power channel of the radio frequency processing unit



189

Name Meaning

Parameter 2 l 0x01: undervoltagel 0x02: overvoltage


This alarm may cause the NE to work incorrectly.

Possible Causesl Cause 1: The input power is abnormal.

l Cause 2: The power module is abnormal.

Procedure

Step 1 Cause 1: The input power is abnormal.

1. Test the input power with a multimeter and check whether the input power is within thenormal range (-57.6 V to -38.4 V).

2. If the input power is out of the normal range, check whether the power supply and powercable are normal.

3. Change the abnormal power supply or power cable.

4. If the power is supplied through the P&E port, check whether the Ethernet power supplydevice and P&E cable are normal.

5. Change the abnormal device or cable.

Step 2 Cause 2: The power module is abnormal.

1. 5.1 Replacing an OptiX RTN 310.

----End

Related Information

None.

A.2.56 PTP_TIMESTAMP_ABN

Description

The PTP_TIMESTAMP_ABN is an alarm indicating that PTP timestamps are abnormal. Thisalarm is reported when PTP (1588v2) timestamps are abnormal.

Attribute





190

Parameters

None.


The slave node cannot trace the time of the master node and services contain bit errors.

Possible Causesl Cause 1: The opposite end is faulty.

l Cause 2: The local end is faulty.

l Cause 3: The physical-layer synchronization and 1588v2 time synchronization areconfigured, and the upstream node transmits less than one SYNC packet per second.

l Cause 4: The PTP ports at the two ends have different P/E attributes.

Procedure

Step 1 Cause 1: The opposite end is faulty.

1. Troubleshoot the opposite end or change the clock source of the local end.

Step 2 Cause 2: The local end is faulty.

1. 5.1 Replacing an OptiX RTN 310.

Step 3 Cause 3: The physical-layer synchronization and 1588v2 time synchronization are configured,and the upstream node transmits less than one SYNC packet per second.

1. With reference to Setting Parameters for IEEE 1588v2 Clock Packets, modify the SYNCpacket transmission rate of the upstream node.

Step 4 Cause 4: The PTP ports at the two ends have different P/E attributes.

1. With reference to Setting the PTP NE Attributes, re-set the P/E attributes.

----End

Related Information

None.

A.2.57 RADIO_FADING_MARGIN_INSUFF

Description

The RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive powerof the OptiX RTN 310 is lower than the threshold (receiver sensitivity plus 14 dB).

When the mean receive power of the OptiX RTN 310 in six consecutive hours is lower than thethreshold, the system reports the alarm. After the alarm is reported, if the mean receive powerof the OptiX RTN 310 becomes normal and maintains the state for three minutes, the alarmclears.



191

Attribute



Parameters

None.


This alarm does not affect services if it is not accompanied by MW_BER_EXC, MW_BER_SD,MW_LOF, or MW_FEC_UNCOR.

Possible Causesl Cause 1: The transmit power is abnormal due to the faulty OptiX RTN 310 at the opposite

site.l Cause 2: The direction of the antenna is deflected.l Cause 3: Transmission environment changes.l Cause 4: The fading margin planned for rain and fog is insufficient.

Procedure

Step 1 Cause 1: The transmit power is abnormal due to the faulty OptiX RTN 310 at the opposite site.1. Check whether the OptiX RTN 310 at the opposite site reports the RADIO_TSL_LOW

alarm.

If... Then...

The RADIO_TSL_LOW alarm is reported Handle the RADIO_TSL_LOW alarm.

The RADIO_TSL_LOW alarm is not reported Go to Cause 2.

Step 2 Cause 2: The direction of the antenna is deflected.1. Check whether the direction of the antenna is deflected.

If... Then...

The direction of the antenna is deflected Adjust the direction of the antenna.

The direction of the antenna is not deflected Go to Cause 3.

Step 3 Cause 3: Transmission environment changes.1. Check whether the transmission environment changes. For example, check whether any

building blocks the transmission and increases the link fading significantly.

If... Then...

The transmission environment changes Contact the network planning department forreplanning the transmission trail.



192

If... Then...

The transmission environment does notchange

Go to Cause 4.

Step 4 Cause 4: The fading margin planned for rain and fog is insufficient.1. If the alarm is frequently reported in rainy or foggy weather, contact the network planning

department for increasing the fading margin.

----End

Related Information

None.

A.2.58 RADIO_MUTE

Description

The RADIO_MUTE is an alarm indicating that the radio transmitter is muted.

Attribute


Warning Equipment alarm

Parameters

None.


This alarm indicates that the radio transmitter does not transmit signals.

Possible Causesl Cause 1: The transmitter of the local site is muted manually.

l Cause 2: The OptiX RTN 310 at the local site is faulty.

Procedure

Step 1 Cause 1: The transmitter of the local site is muted manually.1. With reference to Configuring a Single-Hop Radio Link, check whether the OptiX RTN

310 at the local site is muted. If yes, unmute the OptiX RTN 310.

Step 2 Cause 2: The OptiX RTN 310 at the local site is faulty.1. 5.1 Replacing an OptiX RTN 310.

----End



193


A.2.59 RADIO_RSL_BEYONDTH

DescriptionThe RADIO_RSL_BEYONDTH is an alarm indicating that antennas are not aligned. When thereceivable power is set on an NE, the NE automatically enables the antenna alignment indicationfunction. The RADIO_RSL_BEYONDTH alarm is reported if the actual receive power of theOptiX RTN 310 is 3 dB lower than the receivable power. After the antennas are aligned for 30minutes, the antenna alignment indication function is disabled automatically and theRADIO_RSL_BEYONDTH alarm clears. Afterwards, the RADIO_RSL_BEYONDTH alarmis reported only when the RADIO_FADING_MARGIN_INSUFF alarm is reported.

Attribute



ParametersNone.

Impact on the SystemThis alarm does not affect services if it is not accompanied by MW_BER_EXC, MW_BER_SD,MW_LOF, or MW_FEC_UNCOR.

Possible Causesl Cause 1: Antennas are not aligned during the equipment commissioning.l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.

Procedure

Step 1 Cause 1: Antennas are not aligned during the equipment commissioning.1. Align the antennas, and ensure that the actual receive power is within the range of receivable

power +3 dB.

Step 2 Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is running.1. Handle the RADIO_FADING_MARGIN_INSUFF alarm. After the

RADIO_FADING_MARGIN_INSUFF alarm clears, the RADIO_RSL_BEYONDTHalarm clears.

----End




194

A.2.60 RADIO_RSL_HIGH

DescriptionThe RADIO_RSL_HIGH is an alarm indicating that the radio received signal level (RSL) isvery high. This alarm is reported if the detected RSL is higher than or equal to the upper thresholdof the OptiX RTN 310 (-20 dBm).

Attribute



ParametersNone.

Impact on the SystemThis alarm affects service transmission.

Possible Causesl Cause 1: The OptiX RTN 310 at the local site is faulty.l Cause 2: There is a strong interference source nearby.l Cause 3: The transmit power of the OptiX RTN 310 at the opposite site is very high.

Procedure

Step 1 With reference to Configuring a Single-Hop Radio Link, check whether the transmit powersettings on the local and opposite NEs are consistent with the network planning documents.

Step 2 If no, set the transmit power according to the network planning documents.

Step 3 With reference to 7.1.3 Browsing Current Alarms(U2000), check whether the alarm is cleared.

If... Then...

The alarm is cleared End the alarm handling.

The alarm persists Go to the next step.

Step 4 With reference to 7.9 Scanning Interfering Signals, scan interference signals.

Step 5 Use a spectrum analyzer to scan interference signals nearby. If any interference signal is detected,shut down or remove the signal source. If the signal source cannot be shut down or removed,contact the network planning department for changing the frequency plan.

Step 6 With reference to 7.1.3 Browsing Current Alarms(U2000), check whether the alarm is cleared.

If... Then...

The alarm is cleared End the alarm handling.



195

If... Then...

The alarm persists Go to the next step.

Step 7 5.1 Replacing an OptiX RTN 310.

----End


A.2.61 RADIO_RSL_LOW

DescriptionThe RADIO_RSL_LOW is an alarm indicating that the radio received signal level (RSL) is verylow. This alarm is reported when the detected RSL is lower than or equal to the lower thresholdof the OptiX RTN 310 (-90 dBm).

Attribute



ParametersNone.

Impact on the SystemThis alarm does not affect services if it is not accompanied by the MW_BER_EXC,MW_BER_SD, MW_LOF, or MW_FEC_UNCOR alarm.

Possible Causesl Cause 1: Certain other alarms occur at the opposite site.l Cause 2: The transmitted signal level (TSL) at the opposite site is over low.l Cause 3: The OptiX RTN 310 at the local site is faulty.l Cause 4: Signal attenuation on the radio link is heavy.

Procedure

Step 1 Cause 1: Certain other alarms occur at the opposite site.Check whether any of the following alarms is reported at the opposite site. If yes, clear the alarmimmediately.l RADIO_MUTEl RADIO_TSL_LOW

Step 2 Cause 2: The transmitted signal level (TSL) at the opposite site is over low.



196

1. With reference to Configuring a Single-Hop Radio Link, check whether the preset transmitpower and actual transmit power at the opposite site are normal.

If... Then...

The preset transmit power is abnormal Change the transmit power according to thenetwork planning information.

The actual transmit power is abnormal Replace the OptiX RTN 310 at the oppositesite.

Step 3 Cause 3: The OptiX RTN 310 at the local site is faulty.1. Replace the OptiX RTN 310 at the local site.

Step 4 Cause 4: Signal attenuation on the radio link is heavy.1. With reference to 4.2 Troubleshooting the Radio Link, handle the signal attenuation.

----End


A.2.62 RADIO_TSL_HIGH

DescriptionThe RADIO_TSL_HIGH is an alarm indicating that the radio transmitted signal level (TSL) isvery high. This alarm is reported when the detected TSL is higher than the upper threshold ofthe OptiX RTN 310.

Attribute



ParametersNone.

Impact on the SystemThis alarm affects service transmission.


ProcedureStep 1 Replace the OptiX RTN 310.

----End



197

Related Information

None.

A.2.63 RADIO_TSL_LOW

Description

The RADIO_TSL_LOW is an alarm indicating that the radio transmitted signal level (TSL) isvery low. This alarm is reported when the detected TSL is lower than the lower threshold of theOptiX RTN 310.

Attribute



Parameters

None.


This alarm affects service transmission.

Possible Causes

Cause 1: The OptiX RTN 310 is faulty.

Procedure


----End

Related Information

None.

A.2.64 S1_SYN_CHANGE

Description

The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 bytemode.



198

Attribute




Name Meaning

Parameter 1 0x01: system clock priority table

Impact on the SystemIf the new clock source degrades, service quality will degrade due to pointer justifications andbit errors.

Possible CausesThe precondition is that the SSM or extended SSM is enabled.

l Cause 1: The original clock source is lost.l Cause 2: The upstream NE reports the S1_SYN_CHANGE alarm.

Procedure

Step 1 Cause 1: The original clock source is lost.1. Handle the SYNC_C_LOS alarm reported by the original clock source.

Step 2 Cause 2: The upstream NE reports the S1_SYN_CHANGE alarm.1. Handle the S1_SYN_CHANGE alarm on the upstream NE.

----End

Related InformationS1 byte mode refers to the SSM or extended SSM clock protection mode.

A.2.65 SEC_RADIUS_FAIL

DescriptionThe SEC_RADIUS_FAIL is an alarm indicating that consecutive RADIUS authenticationfailures are too many. This alarm is reported when the number of consecutive RADIUSauthentication failures reaches five.



199

Attribute



Parameters


Name Meaning

Parameters 1 to 5 Indicate the first five user accounts.


A user cannot log in to an NE.

Possible Causesl Cause 1: The active period of the user account expires.l Cause 2: Configurations on the RADIUS server such as passwords and access policies are

incorrect.l Cause 3: There are unauthenticated login attempts.l Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.

Procedure

Step 1 Cause 1: The active period of the user account expires.1. Use an active account.

Step 2 Cause 2: Configurations on the RADIUS server such as passwords and access policies areincorrect.1. Enter the correct password.2. Set correct access policies.

Step 3 Cause 3: There are unauthenticated login attempts.1. Eliminate the source that initiates unauthenticated login attempts.

Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.1. Set the shared key correctly.

----End

Related Information

None.



200

A.2.66 SECU_ALM

Description

The SECU_ALM is an alarm indicating that login attempts of unauthorized users fail.

Attribute



Parameters

None.


This alarm is reported transiently and does not affect services.

Possible Causes

Cause: Unauthorized users attempt to log in to the NE.

Procedure

Step 1 Query the NE logs and check the users that have attempted to log in.

----End

Related Information

If a user fails in more than five consecutive login attempts (two login attempts within threeminutes are considered consecutive), the SECU_ALM alarm will be reported at every failedattempt since the sixth one. In addition, the user account will be locked for 60 seconds. Thelocked user account cannot be used for logins.

A.2.67 SSL_CERT_NOENC

Description

SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.

Attribute


Major Equipment Alarm



201

ParametersNone.

Impact on the SystemPlaintext certificate file is stored on device, private key of the file maybe be get illegally.

Possible CausesCertificate file of SSL is not encrypted.

Procedure

Step 1 Download and verify the encrypted SSL certificate by NMS.

----End


A.2.68 STORM_CUR_QUENUM_OVER

DescriptionThe STORM_CUR_QUENUM_OVER is an alarm of alarm storms. This alarm is reported whenthe current alarm queue length is one smaller than the maximum. This alarm clears when thenumber of current alarms reduces to 950.

Attribute



ParametersNone.

Impact on the SystemThe earliest alarms in the current alarm queue will be overwritten and cannot be queried.

Possible CausesCause: More than 1000 current alarms are stored in the current alarm queue.

Procedure

Step 1 Check the current alarms and clear the frequently reported ones.

----End



202

Related Information

The STORM_CUR_QUENUM_OVER alarm will not be overwritten.

Registers store alarm data in discard or overwrite mode. The default mode is overwrite.

l In discard mode, registers discard the later alarm data if they are full.

l In overwrite mode, registers store the later alarm data in place of the earlier alarm data ifthey are full. To be specific, later alarm data is stored in the initial addresses of registers.

A.2.69 SWDL_ACTIVATED_TIMEOUT

Description

The SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the commit operation is notperformed in a package diffusion task. During package diffusion, the system reports the alarmif the commit operation is not performed within 30 minutes after activation of the NE software.

Attribute



Parameters

None.


Software files in the OFS1 and OFS2 areas of the system control unit are inconsistent.

Possible Causesl Cause 1: The commit operation is not performed within 30 minutes after activation of the

NE software.

l Cause 2: NEs included in the package diffusion task fail to receive the commit commanddue to radio link failures.

Procedure

Step 1 Cause 1: The commit operation is not performed within 30 minutes after activation of the NEsoftware.

1. Proceed the task with the commit operation.

Step 2 Cause 2: NEs included in the package diffusion task fail to receive the commit command dueto radio link failures.

1. Check whether any radio link is faulty.



203

If... Then...

The links are faulty Rectify the faults on the radio links and ensure that the linksalong which the package is diffused are normal.

The links are normal Perform the commit operation for the alarmed NE.

----End

Related Information

None.

A.2.70 SWDL_COMMIT_FAIL

Description

The SWDL_COMMIT_FAIL is an alarm indicating that the commit operation on an NE fails.This alarm is reported when the commit operation fails in a package diffusion task.

Attribute


Minor Processing alarm

Parameters

None.


This alarm indicates that the software versions in the OFS1 and OFS2 areas of the system controlunit are inconsistent.

Possible Causes

Cause: Software backup fails.

Procedure

Step 1 Check and ensure the loaded software package is correct.

Step 2 Perform another package diffusion task for the alarmed NE.

----End

Related Information

None.



204

A.2.71 SWDL_INPROCESS

Description

The SWDL_INPROCESS is an alarm indicating that the NE is performing a package diffusiontask.

Attribute


Warning Processing alarm

Parameters

None.


Do not change NE configurations, download/upload files, back up databases, or perform othersimilar operations before the task is completed.

Possible Causes

Cause: The NE is performing a package diffusion task.

Procedure

Step 1 Wait until the alarm clears. The alarm clears after the package diffusion task is completed orafter a rollback is completed in the case of a diffusion failure.

----End

Related Information

None.

A.2.72 SWDL_NEPKGCHECK

DescriptionThe SWDL_NEPKGCHECK is an alarm indicating that a file in the loaded software packageis lost or cannot be recovered after a file check failure.

The SWDL_NEPKGCHECK is an alarm indicating that a file in the loaded software packageis lost or cannot be recovered after a file check failure. This alarm is reported when the NEsoftware initiates a package file check, detects the loss of a file, and fails to recover the file fromany complete package in other areas.



205

Attribute



ParametersNone.

Impact on the Systeml If this alarm occurs in the process of package loading, the loading task fails.l If this alarm occurs in other cases, automatic software matching fails.

Possible CausesCause: A file in the software package is lost and cannot be recovered.

Procedure

Step 1 Load the correct software package onto the alarmed NE.

----End


A.2.73 SWDL_PKGVER_MM

DescriptionThe SWDL_PKGVER_MM is an alarm indicating that the consistency check on the softwarepackage version fails. This alarm is reported when the consistency check on the software packageversion fails.

Attribute



ParametersNone.

Impact on the SystemThe version of the software package is inconsistent with that described in the software package.As a result, certain functions of the NE may be affected.



206

Possible Causes

Cause: The software version information in the description file of the software package isinconsistent with the actual information about the software version.

Procedure

Step 1 Ensure that the loaded software package is correct. Perform package diffusion for the NEs thatreport the SWDL_PKGVER_MM alarm.

----End

Related Information

None.

A.2.74 SWDL_ROLLBACK_FAIL

Description

The SWDL_ROLLBACK_FAIL is an alarm indicating that an NE rollback fails.

Attribute



Parameters

None.


This alarm affects some functions of the system.

Possible Causes

Cause: The files for certain function modules are not loaded during software package loading.

Procedure

Step 1 Add the required files to the software package and load the software package.

----End

Related Information

None.



207

A.2.75 SYNC_C_LOS

DescriptionThe SYNC_C_LOS is an alarm indicating that the synchronization source level is lost. Thisalarm is reported when a clock source in the clock source priority list is lost.

Attribute


Warning Equipment alarm


Name Meaning

Parameters 1 and 2 Clock source

l If the local NE traces the clock of another NE through a certain port,Parameter 1 indicates the slot ID and Parameter 2 indicates the portID.

l The value 0xf1 0x01 indicates the internal clock source.

Impact on the SystemThe clock source is lost because it degrades and cannot be traced. This alarm has limited impactson services.

Possible CausesCause 1: A clock source is lost.

Procedure

Step 1 Check the clock source priority list and determine the synchronization source corresponding tothe lost clock source.

Step 2 Handle the link interruption alarms, if any, on the physical link that transmits the synchronizationsource.

----End




208

A.2.76 SYSLOG_COMM_FAIL

DescriptionThe SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NEand the syslog server fails.

Attribute



ParametersNone.

Impact on the SystemThe syslog information of the NE cannot be sent to the syslog server.

Possible CausesCause 1: In the TCP mode, the connection between the NE and syslog server is interrupted, orthe session between the NE and server is abnormal.

ProcedureStep 1 Rectify the fault of the link between the NE and syslog server, or rectify the fault of the protocol.

----End


A.2.77 TEMP_ALARM

DescriptionThe TEMP_ALARM is an alarm indicating that the temperature crosses the lower/upperthreshold.

Attribute


Minor Environment alarm

ParametersWhen you view an alarm on the network management system, select the alarm. In the AlarmDetails field display the related parameters of the alarm. The alarm parameters are in the



209

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN. For detailsabout each parameter, refer to the following table.

Name Meaning

Parameter 1 l 0x01: The temperature crosses the upper threshold.l 0x02: The temperature crosses the lower threshold.

Parameter 2 Indicates the alarmed location.

l 0x01: overall systeml 0x02: power amplifier


Services or the equipment may be affected, and the NE cannot work normally.

Possible Causesl Cause 1: The ambient temperature crosses the upper/lower threshold.

l Cause 2: The temperature detection circuit of the NE is faulty.

l Cause 3: The NE is faulty.

Procedure

Step 1 If the ambient temperature is over high, take appropriate measures (for example, installing asunshade) to control the temperature.

Step 2 Remove the materials that cover or shelter the equipment.

Step 3 If the ambient temperature is normal and no heat dissipation problem exists, 5.1 Replacing anOptiX RTN 310.

----End

Related Information

None.

A.2.78 TIME_LOCK_FAIL

Description

The TIME_LOCK_FAIL is an alarm indicating that time locking fails.

Attribute





210

Parameters

None.


The slave node cannot trace the time of the master node and services contain bit errors.

Possible Causesl Cause 1: Certain other alarms occur.

l Cause 2: Time adjustments occur at the upstream node.

Procedure

Step 1 On the NMS, check whether the CLK_LOCK_FAIL, LTI, or TIME_NO_TRACE_MODEalarm occurs. If yes, clear these alarms.

Step 2 Check whether time adjustments occur at the upstream node. If yes, the TIME_LOCK_FAILwill be cleared after the time adjustments are completed.

----End

Related Information

None.

A.2.79 TIME_LOS

Description

The TIME_LOS is an alarm indicating loss of the time source level. This alarm is reported whenthe high precision time function is enabled but the traced time source does not exist.

Attribute


Major Clock alarm

Parameters




211

Name Meaning

Parameters 1 and 2 Indicate ID of the time source.

Parameter 1 indicates the slot number and Parameter 2 indicates theoptical port number.

Impact on the SystemThe local NE cannot trace the time of its upstream NE.

Possible CausesCause 1: The link between the local NE and its upstream NE is faulty.

Procedure

Step 1 With reference to 7.1.3 Browsing Current Alarms(U2000), check whether any of the followingalarms exists: Ethernet link alarms ETH_LOS, MAC_EXT_EXC, and MAC_FCS_EXC;radio link alarms MW_LOF, MW_BER_EXC, and MW_BER_SD.

Step 2 If yes, clear these alarms before you proceed.

Step 3 If no, check for link-related alarms on the upstream NE. Clear these alarm if any.

----End


A.2.80 TIME_NO_TRACE_MODE

DescriptionThe TIME_NO_TRACE_MODE is an alarm indicating that the high precision time of an NEis in the non-tracing state. This alarm is reported when the high precision time function is enabledon an NE but the currently traced source is the internal source.

Attribute



ParametersNone.

Impact on the SystemThe local NE may not be time synchronized with its upstream NE.



212

Possible Causesl Cause 1: The link between the local NE and its upstream NE is faulty.

l Cause 2: BMC attributes are configured incorrectly.

Procedure

Step 1 Cause 1: The link between the local NE and its upstream NE is faulty.

1. Check whether the TIME_LOS alarm is reported by referring to 7.1.3 Browsing CurrentAlarms(U2000). If yes, clear this alarm.

Step 2 Cause 2: BMC attributes are configured incorrectly.

1. Check the clock tracing relationship on the network according to the network planninginformation.

----End

Related Information

The best master clock (BMC) algorithm is applied to clock source selection. IEEE 1588v2dynamically determines the master-slave hierarchy by using the BMC algorithm. The BMCalgorithm consists of:

l Data set comparison algorithm

l State decision algorithm

A.2.81 USB_PROCESS_FAIL

Description

The USB_PROCESS_FAIL is an alarm indicating that databases cannot be recovered from orbacked up to the USB flash drive.

Attribute



Parameters


Name Meaning

Parameter 1 l 0x01: data recoveryl 0x02: data backup



213

Name Meaning

Parameter 2 Indicates the file type.

l 0x01: software packagel 0x02: patch packagel 0x03: system parameter areal 0x04: script filel 0x05: database filel 0x06: license file

Impact on the SystemDatabase backup/recovery fails, and the system remains in the original state.

Possible Causesl Cause 1: Databases cannot be recovered from the USB flash drive.l Cause 2: Databases cannot be backed up to the USB flash drive.

Procedure

Step 1 Query parameter 2 for the file type.

Step 2 In a recovery failure, verify that the data in the USB flash drive is correct, and perform anotherrecovery attempt.

Step 3 In a backup failure, verify that the NE data is correct, and perform another backup attempt.

----End


A.2.82 XPIC_LOS

DescriptionThe XPIC_LOS is an alarm indicating that XPIC compensation signals are lost.

Attribute



ParametersNone.



214


At the alarmed port, the service may generate bit errors and even become interrupted.

Possible Causesl Cause 1: Configuration data is incorrect.

l Cause 2: The radio link is faulty.

l Cause 3: The XPIC cable is faulty.

l Cause 4: The OptiX RTN 310 is faulty.

Procedure

Step 1 Cause 1: Configuration data is incorrect.

1. Check whether the XPIC function needs to be enabled. If no, disable the XPIC function byreferring to Configuring a Single-Hop Radio Link.

Step 2 Cause 2: The radio link is faulty.

1. Check whether the MW_LOF alarm is reported in the other polarization direction of theXPIC function. If yes, clear the MW_LOF alarm.

Step 3 Cause 3: The XPIC cable is faulty.

1. Check the connection of the XPIC cable.

If... Then...

The cable is connected incorrectly Connect the XPIC cable properly.

The cable is properly connected Go to the next step.

2. Test the connectivity of the XPIC cable by using the multimeter. If the XPIC cable isdamaged, replace it.

NOTE

Remove XPIC cables by pulling rings attached on them.

Step 4 Cause 4: The OptiX RTN 310 is faulty.

1. Replace the OptiX RTN 310 that works with the XPIC function at the alarmed port.

If... Then...

The alarm clears after the OptiX RTN310 is replaced

End the alarm handling.

The alarm persists after the OptiX RTN310 is replaced


2. Replace the local OptiX RTN 310.

----End



215




216

B Performance Event Reference

Performance events are important indicators when the equipment performance changes. Thissection describes all the possible performance events on the OptiX RTN 310 and how to handlethese performance events.

B.1 Performance Event ListThe performance event list includes all the performance events of the OptiX RTN 310 andclassifies them into different types.

B.2 Performance Events and Handling ProceduresThis section describes all the possible performance events on the OptiX RTN 310 and how tohandle these events.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide B Performance Event Reference


217

B.1 Performance Event ListThe performance event list includes all the performance events of the OptiX RTN 310 andclassifies them into different types.

B.1.1 Microwave Performance EventsMicrowave performance events include performance events associated with microwave biterrors, ATPC, AM, XPIC, signal to noise ratio (SNR), and power.

Table B-1 Microwave power performance events

Performance Event Name Description

TSL_MAX Maximum radio transmitted signal level

TSL_MIN Minimum radio transmitted signal level

TSL_CUR Current radio transmitted signal level

TSL_AVG Average radio transmitted signal level

RSL_MAX Maximum radio received signal level

RSL_MIN Minimum radio received signal level

RSL_CUR Current radio received signal level

RSL_AVG Average radio received signal level

TLHTT Duration when the transmit power is higherthan the upper threshold

TLLTT Duration when the transmit power is higherthan the lower threshold

RLHTT Duration when the receive power is lowerthan the upper threshold

RLLTT Duration when the receive power is lowerthan the lower threshold

Table B-2 FEC performance events


FEC_BEF_COR_ER BER before the FEC is performed

FEC_UNCOR_BLOCK_CNT Number of frames that cannot be correctedthrough the FEC



218

Table B-3 Radio link bit error performance events


IF_BBE Radio link background block error

IF_ES Radio link errored second

IF_SES Radio link severely errored second

IF_UAS Radio link unavailable second

IF_CSES Radio link consecutive severely erroredsecond

Table B-4 ATPC performance events


ATPC_P_ADJUST Positive ATPC adjustment event

ATPC_N_ADJUST Negative ATPC adjustment event

Table B-5 AM performance events


QPSK_S_WS Working duration of the QPSK Strong mode

QPSKWS Working duration of the QPSK mode

QAM_S_WS16 Working duration of the 16QAM Strongmode

QAMWS16 Working duration of the 16QAM mode






QAM_L_WS512 Working duration of the 512QAM Lightmode


QAM_L_WS1024 Working duration of the 1024QAM Lightmode

AMDOWNCNT Count of AM downshifts



219


AMUPCNT Count of AM upshifts

Table B-6 XPIC performance events


XPIC_XPD_VALUE Value of XPIC XPD

Table B-7 SNR performance events


IF_SNR_MAX Maximum SNR

IF_SNR_MIN Minimum SNR

IF_SNR_AVG Average SNR

B.1.2 Other Performance EventsOther performance events include performance events associated with power of Ethernet opticalports, lasers, radio frequency (RF) power amplifiers, board temperature, and clock.

Table B-8 Optical power performance events


TPLMAX Maximum transmit power of a laser

TPLMIN Minimum transmit power of a laser

TPLCUR Current transmit power of a laser

RPLMAX Maximum receive power of a laser

RPLMIN Minimum receive power of a laser

RPLCUR Current receive power of a laser

Table B-9 Transmitted bias current performance events


TLBMAX Maximum transmitted bias current of thelaser



220


TLBMIN Minimum transmitted bias current of the laser

TLBCUR Current transmitted bias current of the laser

Table B-10 Board temperature performance events


BDTEMPMAX Maximum temperature of a board

BDTEMPMIN Minimum temperature of a board

BDTEMPCUR Current temperature of a board

Table B-11 Laser temperature performance events


OSPITMPMAX Maximum laser temperature

OSPITMPMIN Minimum laser temperature

OSPITMPCUR Current laser temperature

Table B-12 RF power amplifier temperature performance events


PATEMPMAX Maximum temperature of an RF poweramplifier

PATEMPMIN Minimum temperature of an RF poweramplifier

PATEMPCUR Current temperature of an RF poweramplifier

Table B-13 Clock performance events


MAXPHASEOFFSET Maximum phase offset

MINPHASEOFFSET Minimum phase offset

AVGPHASEOFFSET Average phase offset



221


MAXMEANPATHDELAY Maximum path delay

MINMEANPATHDELAY Minimum path delay

AVGMEANPATHDELAY Average path delay

B.2 Performance Events and Handling ProceduresThis section describes all the possible performance events on the OptiX RTN 310 and how tohandle these events.

B.2.1 AMDOWNCNT and AMUPCNT

Descriptionl AMDOWNCNT indicates the count of AM downshifts in the current performance

monitoring period.l AMUPCNT indicates the count of AM upshifts in the current performance monitoring

period.

AttributeAttribute Description

Performance event cell ACMDCNT (AMDOWNCNT),ACMUCNT (AMUPCNT)

Unit None

Impact on Systeml A large value of this event indicates frequent AM shifts.l If there is no factor that can affect a communication link such as sudden weather changes

but the AM shift count is very large, the communication link may be faulty. You must checkthe communication link to prevent link failures.

Relevant AlarmsAM_DOWNSHIFT

This alarm is not reported by default. If you need the reporting of this alarm, change the settingaccording to 7.2.5 Setting Monitoring and Auto-Report Status of Performance Events.

Possible CausesWhen the AM function is enabled on an IF board, the modulation scheme of the IF port changeswith the link quality. If the modulation scheme is changed from a lower order one to a higher



222

order one, the system counts one AM upshift in the AMUPCNT event; if the modulation schemeis changed from a higher order one to a lower order one, the system counts one AM downshiftin the AMDOWNCNT event.

B.2.2 ATPC_P_ADJUST and ATPC_N_ADJUST

Descriptionl ATPC_P_ADJUST indicates the positive ATPC adjustment event.

This performance event indicates that the quality of a communication link degrades. If thisevent occurs, you need to increase the transmit power of the OptiX RTN 310 to maintainthe communication quality.

l ATPC_N_ADJUST indicates the negative ATPC adjustment event.

This performance event indicates that the quality of a communication link improves or thetransmit power of the OptiX RTN 310 is very high. If this event occurs, you need to decreasethe transmit power of the OptiX RTN 310.

Attribute

Attribute Description

Performance event cell ATPCPADJUST (ATPC_P_ADJUST) andATPCNADJUST (ATPC_N_ADJUST)

Unit None

Impact on System

The ATPC adjustment indicates only the stability of a communication link and does not affectservices. A large value of this event indicates frequent ATPC adjustments.

If there is no factor that can affect a communication link such as sudden weather changes butthe ATPC adjustment count is very large, the communication link may be faulty. You must checkthe communication link to prevent link failures.

Relevant Alarms

None.

B.2.3 MAXMEANPATHDELAY, MINMEANPATHDELAY, andAVGMEANPATHDELAY

Descriptionl MAXMEANPATHDELAY indicates the maximum path delay between the master clock

and the slave clock.

l MINMEANPATHDELAY indicates the minimum path delay between the master clockand the slave clock.



223

l AVGMEANPATHDELAY indicates the average path delay between the master clock andthe slave clock.

Attribute


Performance event cell MAXMEANPATHDELAY(MAXMEANPATHDELAY)MINMEANPATHDELAY(MINMEANPATHDELAY)AVGMEANPATHDELAY(AVGMEANPATHDELAY)

Unit ns

Impact on System

The difference between MAXMEANPATHDELAY and MINMEANPATHDELAY reflects thevariation of path delay. If the difference is too large, the clock performance will be affected.

Relevant Alarms

None.

B.2.4 BDTEMPMAX, BDTEMPMIN, and BDTEMPCUR

Descriptionl BDTEMPMAX indicates the maximum temperature of a board.

l BDTEMPMIN indicates the minimum temperature of a board.

l BDTEMPCUR indicates the current temperature of a board.

Attribute


Performance event cell XCS_TEMP

Unit 0.1°C

Impact on System

If the temperature of a board is very high or very low, the performance of the board degradesand bit errors or other faults occur.



224

Relevant AlarmsThe TEMP_ALARM alarm is reported if the temperature of a board exceeds the specifiedthreshold.

B.2.5 FEC_BEF_COR_ER and FEC_UNCOR_BLOCK_CNT

Descriptionl FEC_BEF_COR_ER indicates the BER before FEC is performed.

This event reflects the impact of the external environment on transmission.l FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected

through FEC.This event presents the number of errored blocks after FEC is performed.

NOTE

If a radio link is interrupted, the performance events FEC_BEF_COR_ER cannot be counted and thereforeare shown as 0 upon queries.


Performance event cell FECBEFCORER (FEC_BEF_COR_ER)FECUNCORBLOCKCNT(FEC_UNCOR_BYTE_CNT)

Unit None (FEC_BEF_COR_ER)NOTE

If FEC_BEF_COR_ER shows 8, the BER beforeFEC functions is 10-8.

Block (FEC_UNCOR_BLOCK_CNT)

Impact on SystemIf the value of FEC_BEF_COR_ER is very large, residual bit errors will exist in services afterFEC is performed.

If the value of FEC_UNCOR_BLOCK_CNT is not zero, services will contain bit errors.

Relevant AlarmsThe MW_FEC_UNCOR alarm is reported if any bytes cannot be corrected. This alarm is notreported by default. If you need the reporting of this alarm, change the setting according to 7.2.5Setting Monitoring and Auto-Report Status of Performance Events.



225

B.2.6 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Descriptionl IF_BBE indicates the radio link background block error.

BBE refers to the errored blocks excluding those in the unavailable seconds and severelyerrored seconds.

l IF_ES indicates the radio link errored second.

An ES refers to a second in which one or more errored blocks are detected.

l IF_SES indicates the radio link severely errored second.

An SES refers to a second in which 30% or more errored blocks are detected or at least oneserious disturbance period (SDP) exists. The SDP refers to a period of at least fourconsecutive blocks or 1 ms (taking the longer one) in which the BER of all the consecutiveblocks is higher than or equal to 10-2 or the signal is lost.

l IF_CSES indicates the radio link consecutive severely errored second.

A CSES refers to a second in a period (shorter than 10 seconds) when severely erroredseconds occur continuously.

l IF_UAS indicates the radio link unavailable second.

A UAS period starts from the first second of 10 consecutive SESs. These ten seconds area part of the unavailable time. A new available second period starts from the first secondof ten consecutive non-SESs. These ten seconds are a part of the available time.

Attribute


Performance event cell IF_BIP8

Unit None

Impact on System

A small number of bit errors do not affect services. Excessive bit errors, however, cause serviceinterruptions. Generally, the BER requirement is less than 10-3 for voice services, and less than10-6 for data services.

Relevant Alarms

The MW_BER_SD or MW_BER_EXC alarm is reported if the BER exceeds the specifiedthreshold.

Possible Causes

The system detects bit errors on the radio link by using the bit error detection overheads inmicrowave frames.



226

Procedure

Step 1 See the MW_BER_SD or MW_BER_EXC alarm.

----End

B.2.7 IF_SNR_MAX, IF_SNR_MIN, and IF_SNR_AVG

Descriptionl IF_SNR_MAX indicates the maximum signal-to-noise ratio.l IF_SNR_MIN indicates the minimum signal-to-noise ratio.l IF_SNR_AVG indicates the average signal-to-noise ratio.


Performance event cell IF_SNR (IF_SNR_MAX, IF_SNR_MIN)IF_SNR_AVG_15M andIF_SNR_AVG_24H (IF_SNR_AVG)

Unit dB

Impact on SystemA higher signal-to-noise ratio indicate better link performance and a lower signal-to-noise ratioindicates worse link performance such as bit errors or service interruptions.

Relevant AlarmsNone.

B.2.8 MAXPHASEOFFSET, MINPHASEOFFSET, andAVGPHASEOFFSET

Descriptionl MAXPHASEOFFSET indicates the maximum phase offset between the master clock and

the slave clock.l MINPHASEOFFSET indicates the minimum phase offset between the master clock and

the slave clock.l AVGPHASEOFFSET indicates the average phase offset between the master clock and the

slave clock.



227

Attribute


Performance event cell MAXPHASEOFFSET(MAXPHASEOFFSET),MINPHASEOFFSET(MINPHASEOFFSET),AVGPHASEOFFSET(AVGPHASEOFFSET)

Unit ns

Impact on System

This performance event reflects the phase offset between the local NE and the upstream NE. Ifthe phase offset is larger than 100 ns for a while, the local NE cannot lock the time of the upstreamNE. That is, time synchronization fails between the local NE and the upstream NE.

Relevant Alarms

The TIME_LOCK_FAIL is reported if this performance event takes a value greater than 100ns.

B.2.9 OSPITMPMAX, OSPITMPMIN, and OSPITMPCUR

Descriptionl OSPITMPMAX indicates the maximum temperature of a laser.

l OSPITMPMIN indicates the minimum temperature of a laser.

l OSPITMPCUR indicates the current temperature of a laser.

Attribute


Performance event cell TEMMN

Unit 0.1°C

Impact on System

If the temperature of a laser is excessively high or low, the performance of the laser degradesand bit errors or other faults occur.

Relevant Alarms

None.



228

B.2.10 PATEMPMAX, PATEMPMIN, and PATEMPCUR

Descriptionl PATEMPMAX indicates the maximum temperature of the radio frequency signal power

amplifier.l PATEMPMIN indicates the minimum temperature of the radio frequency signal power

amplifier.l PATEMPCUR indicates the current temperature of the radio frequency signal power

amplifier.


Performance event cell XCS_TEMP

Unit 0.1°C

Impact on SystemIf the temperature of the radio frequency signal power amplifier is over low/high, the output ofradio frequency signal will become unstable, causing bit errors in services or other faults.

Relevant AlarmsThe TEMP_ALARM alarm is reported if the temperature of the radio frequency signal poweramplifier exceeds the lower/upper threshold.

B.2.11 QPSKWS, QPSK_S_WS, QAMWS16, QAM_S_WS16,QAMWS32, QAMWS64, QAMWS128, QAMWS256, QAMWS512,QAM_L_WS512, QAMWS1024, and QAM_L_WS1024

Descriptionl QPSKWS indicates the working duration of the QPSK mode.l QPSK_S_WS indicates the working duration of the QPSKW Strong mode.l QAMWS16 indicates the working duration of the 16QAM mode.l QAM_S_WS16 indicates the working duration of the 16QAM Strong mode.l QAMWS32 indicates the working duration of the 32QAM mode.l QAMWS64 indicates the working duration of the 64QAM mode.l QAMWS128 indicates the working duration of the 128QAM mode.l QAMWS256 indicates the working duration of the 256QAM mode.l QAMWS512 indicates the working duration of the 512QAM mode.l QAM_L_WS512 indicates the working duration of the 512QAM Light mode.l QAMWS1024 indicates the working duration of the 1024QAM mode.



229

l QAM_L_WS1024 indicates the working duration of the 1024QAM Light mode.

Attribute


Performance event cell QPSKWSSECOND (QPSKWS)QPSK_S_WSSECOND (QPSK_S_WS)QAMWS16SECOND (QAMWS16)QAM_S_WS16SECOND (QAM_S_WS16)QAMWS32SECOND (QAMWS32)QAMWS64SECOND (QAMWS64)QAMWS128SECOND (QAMWS128)QAMWS256SECOND (QAMWS256)QAMWS512SECOND (QAMWS512)QAM_L_WS512SECOND(QAM_L_WS512)QAMWS1024SECOND (QAMWS1024)QAM_L_WS1024SECOND(QAM_L_WS1024)

Unit Second

Impact on System

When the AM function is disabled, these performance events do not affect the system.

When the AM function is enabled, the working duration of the highest order modulation modeshould account for a large proportion of the total. In favorable weather, if the working durationof the low order modulation modes account for a large proportion of the total, the performanceof the radio link may be abnormal.

Relevant Alarms

None.

B.2.12 RLHTT, RLLTT, TLHTT, and TLLTT

Descriptionl RLHTT indicates the duration when the receive power is lower than the upper threshold.

l RLLTT indicates the duration when the receive power is lower than the lower threshold.

l TLHTT indicates the duration when the transmit power is higher than the upper threshold.

l TLLTT indicates the duration when the transmit power is lower than the lower threshold.



230


Performance event cell RLHTS (RLHTT), RLLTS (RLLTT),TLHTS (TLHTT), and TLLTS (TLLTT)

Unit Second

Impact on SystemNone.


B.2.13 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Descriptionl RSL_MAX indicates the maximum radio received signal level.l RSL_MIN indicates the minimum radio received signal level.l RSL_CUR indicates the current radio received signal level.l RSL_AVG indicates the average radio received signal level.


Performance event cell RSL

Unit 0.1 dBm

Impact on SystemWhen the radio received signal level is very low or very high, bit errors occur and even servicesare interrupted.

Relevant AlarmsIf the radio received signal level exceeds the specified threshold, the RADIO_RSL_HIGH orRADIO_RSL_LOW alarm is reported.

B.2.14 TLBMAX, TLBMIN, and TLBCUR

Descriptionl TLBMAX indicates the maximum transmitted bias current of a laser.



231

l TLBMIN indicates the minimum transmitted bias current of a laser.l TLBCUR indicates the current transmitted bias current of a laser.


Performance event cell LSBCM

Unit 0.1 mA

Impact on SystemExcessively high/low current may cause damage to lasers.

Relevant AlarmsThe IN_PWR_ABN alarm will be reported if the receive optical power of the opposite end isabnormal.

B.2.15 TPLMAX, TPLMIN, and TPLCUR

Descriptionl TPLMAX indicates the maximum transmit optical power at an optical port.l TPLMIN indicates the minimum transmit optical power at an optical port.l TPLCUR indicates the current transmit optical power at an optical port.


Performance event cell OPM

Unit 0.1 dBm

Impact on SystemIn normal cases, the receive optical power is 3 dB higher than the receiver sensitivity and 5 dBlower than the overload power.

If the transmit optical power is very low or very high, the receive optical power at the oppositesite is accordingly very low or very high. As a result, bit errors occur and even services areinterrupted.

Relevant AlarmsThe IN_PWR_ABN alarm will be reported if the receive optical power of the opposite site isabnormal.



232

B.2.16 RPLMAX, RPLMIN, and RPLCUR

Descriptionl RPLMAX indicates the maximum receive optical power at an optical port.

l RPLMAX indicates the minimum receive optical power at an optical port.

l RPLCUR indicates the current receive optical power at an optical port.

Attribute


Performance event cell IPM

Unit 0.1 dBm

Impact on System

In normal cases, the receive optical power is 3 dB higher than the receiver sensitivity and 5 dBlower than the overload power.

If the receive optical power is very low or very high, bit errors occur and even services areinterrupted.

Relevant Alarms

The IN_PWR_ABN alarm is reported if the receive optical power is abnormal.

B.2.17 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Descriptionl TSL_MAX indicates the maximum radio transmitted signal level.

l TSL_MIN indicates the minimum radio transmitted signal level.

l TSL_CUR indicates the current radio transmitted signal level.

l TSL_AVG indicates the average radio transmitted signal level.

Attribute


Performance event cell TSL

Unit 0.1 dBm



233

Impact on SystemWhen the radio transmitted signal level is very low or very high, the radio received signal levelat the opposite site is accordingly very low or very high. As a result, bit errors occur and evenservices are interrupted.

Relevant AlarmsIf the radio transmitted signal level is out of the range supported by the OptiX RTN 310, theRADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.

B.2.18 XPIC_XPD_VALUE

DescriptionXPIC_XPD_VALUE indicates the cross polarization discrimination (XPD) value after the XPICfunction is enabled.


Performance event cell XPD

Unit 0.1 dB

Impact on Systeml When the XPIC function is disabled, this performance event does not affect the system.l When the XPIC function is enabled, a greater XPD value indicates less interference between

H and V polarization directions and better signaling environment; a smaller XPD valueindicates more interference and worse signaling environment. If the XPD value is smallerthan a specific threshold, errors and even service interruptions occur on the radio link.




234

C RMON Event Reference

RMON events reflect the running status of Ethernet services. This section describes all thepossible RMON events on the OptiX RTN 310 and how to handle these events.

C.1 RMON Alarm Entry ListRMON alarm entries refer to the table entries in the RMON alarm group.

C.2 RMON Performance Entry ListRMON performance entries refer to the table entries in the RMON statistics group or RMONhistory group.

C.3 RMON Events and Handling ProceduresThis section describes the RMON events that indicate Ethernet service exceptions and how tohandle these events.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide C RMON Event Reference


235

C.1 RMON Alarm Entry ListRMON alarm entries refer to the table entries in the RMON alarm group.

Table C-1 RMON alarm entry list

Abbreviation

Description Remarks

ETHDROP Number of packet loss eventscrosses the threshold.

ETHDROP indicates the number ofpacket loss events caused byinsufficient Ethernet chip resources.

RXBBAD Number of bytes in the received badpackets crosses the threshold.

FCS bytes are included but framingbits are excluded.

ETHFCS Number of FCS error frames crossesthe threshold.

FCS error frames exclude oversizedframes and undersized frames.

ETHUNDER Number of received undersizedpackets crosses the threshold.

Undersized packets are the packetsshorter than 64 bytes (including FCSbytes but not framing bits).

ETHOVER Number of received oversizedpackets crosses the threshold.

Oversized packets are the packetslarger than MTU (including FCSbytes but not framing bits).

ETHFRG Number of received fragmentedpackets crosses the threshold.

ETHFRG indicates the number ofreceived packets that are shorter than64 bytes (including FCS bytes butnot framing bits) and contain FCSerrors or alignment errors.

ETHJAB Number of received oversized errorpackets crosses the threshold.

ETHJAB indicates the number ofreceived packets that are larger thanMTU (including FCS bytes but notframing bits) and contain FCS errorsor alignment errors.

PORT_RX_BW_UTILIZATION

Bandwidth utilization ratio at areceive port

Bandwidth utilization ratio =(Number of received bytes x 8/Monitoring period)/Configured oractual bandwidth

PORT_TX_BW_UTILIZATION

Bandwidth utilization ratio at atransmit port

Bandwidth utilization ratio =(Number of transmitted bytes x 8/Monitoring period)/Configured oractual bandwidth



236

C.2 RMON Performance Entry ListRMON performance entries refer to the table entries in the RMON statistics group or RMONhistory group.

Table C-2 RMON performance entry list

PerformanceEntryType

Performance EntryName

Description Remarks

Basicperformanceentry

RXPKTS Received packets(packets)

Bad packets, broadcastpackets, and multicastpackets are included.

ETHDROP Packet loss events (times) ETHDROP indicates thenumber of packet lossevents caused byinsufficient Ethernet chipresources.

RXOCTETS Received bytes (bytes) RXOCTETS indicates thetotal number of bytes inreceived packets(including bad packets),including framing bits butnot FCS bytes.

RXMULCAST Received multicastpackets (packets)

RXMULCAST indicatesthe total number ofreceived good packetswith multicast destinationaddresses, excludingbroadcast packets.

RXBRDCAST Received broadcastpackets (packets)

RXBRDCAST indicatesthe total number ofreceived good packetswith broadcastdestination addresses,excluding multicastpackets.

ETHOVER Received oversizedpackets (packets)

Oversized packets are thepackets larger than MTU(including FCS bytes butnot framing bits).



237



Description Remarks

ETHJAB Received oversized errorpackets (packets)

ETHJAB indicates thenumber of receivedpackets that are largerthan MTU (includingFCS bytes but not framingbits) and contain FCSerrors or alignment errors.

ETHUNDER Received undersizedpackets (packets)

Undersized packets arethe packets shorter than64 bytes (including FCSbytes but not framingbits).

ETHFRG Received fragments(packets)

ETHFRG indicates thenumber of receivedpackets that are shorterthan 64 bytes (includingFCS bytes but not framingbits) and contain FCSerrors or alignment errors.

PORT_RX_BW_UTI-LIZATION

Bandwidth utilizationratio at a receive port

Bandwidth utilizationratio = (Number ofreceived bytes x 8/Monitoring period)/Configured or actualbandwidth

PORT_TX_BW_UTI-LIZATION

Bandwidth utilizationratio at a transmit port

Bandwidth utilizationratio = (Number oftransmitted bytes x 8/Monitoring period)/Configured or actualbandwidth

RXPKT64 Total of received 64-bytepackets (including badpackets)

FCS bytes are includedbut framing bits areexcluded.

RXPKT65 Total of received packetsof 65 to 127 bytes(including bad packets)






238



Description Remarks







Extendedperformanceentry

RXBGOOD Bytes in received goodpackets (bytes)


TXBGOOD Bytes in transmitted goodpackets (bytes)


RXBBAD Bytes in received badpackets (bytes)


TXUNICAST Transmitted unicastpackets (packets)

The unicast packets thatare discarded or fail to betransmitted are included.

RXUNICAST Received unicast packets(packets)

RXUNICAST indicatesthe number of goodunicast packets.

TXMULCAST Transmitted multicastpackets (packets)

The multicast packets thatare discarded or fail to betransmitted are included.

TXBRDCAST Transmitted broadcastpackets (packets)

The broadcast packetsthat are discarded or fail tobe transmitted areincluded.

RXGOODFULLFRAMESPEED

Bit rate of received goodfull frames (kbit/s)

Framing bits (20 bytes)and FCS bytes areincluded.

TXGOODFULLFRAMESPEED

Bit rate of transmittedgood full frames (kbit/s)




239



Description Remarks

RXFULLBGOOD Number of bytes inreceived good full frames(bytes)


TXFULLBGOOD Number of bytes intransmitted good fullframes (bytes)


RXPAUSE Received PAUSE frames(frames)

RXPAUSE indicates thenumber of MAC flowcontrol frames with thePAUSE opcode.

TXPAUSE Transmitted PAUSEframes (frames)

TXPAUSE indicates thenumber of MAC flowcontrol frames with thePAUSE opcode.

RXPKT1519 Total of received packetsof 1519 to MTU bytes(including bad packets)


TXPKT64 Total of transmitted 64-byte packets (includingbad packets)


TXPKT65 Total of transmittedpackets of 65 to 127 bytes(including bad packets)


TXPKT128 Total of transmittedpackets of 128 to 255bytes (including badpackets)










240



Description Remarks

TXPKT1519 Total of transmittedpackets of 1519 to MTUbytes (including badpackets)


L2VPNa

performanceentry

VUNI_RCVPKTS Packets received on the V-UNI

-

ETHOAM802.1ag

ETH_CFM_FLR Packet loss ratio of an E-Line service

Packet loss ratio =(Number of packetstransmitted by the sourceMEP - Number of packetsreceived by the sinkMEP)/Number of packetstransmitted by the sourceMEP

ETH_CFM_FL Lost packets of an E-Lineservice

Number of lost packets =Number of packetstransmitted by the source- Number of packetsreceived by the sink (Bothnumbers are detected bythe performancemonitoring scheme ofOAM.)

ETH_CFM_FD Frame delay of an E-Lineservice

Frame delay = Time whenthe source MEP sends arequest packet - Timewhen the source MEPreceives the responsepacket

ETH_CFM_FDV Frame delay variation ofan E-Line service

Frame delay variation isthe difference betweentwo frame delay testresults.

NOTE

l a: L2VPN services include a variety of E-Line and E-LAN services supported by the equipment.

l VUNI refers to the virtual UNI corresponding to the service source or sink on the UNI side.



241

C.3 RMON Events and Handling ProceduresThis section describes the RMON events that indicate Ethernet service exceptions and how tohandle these events.

C.3.1 ETHDROP

Description

ETHDROP indicates the number of events that packet loss occurs due to insufficient Ethernetchip resources. If the number exceeds the threshold, an RMON threshold-crossing event will bereported.

NOTE

ETHDROP does not count the packet loss events caused by link congestion or any other factor.

Impact on System

Frequent packet loss events affect services and the system, and therefore require immediatetroubleshooting.

Relevant Alarms

MAC_EXT_EXC

Possible Causes

This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, orreverse pressure.

l The lower threshold is set to non-zero value.

l The hardware at the local end is faulty.

Procedure

Step 1 Handle this alarm according to the specific performance event.

If... Then...

The number is lower than the lowerthreshold

Change the lower threshold to 0.

The number is higher than the upperthreshold

Manually decrease the traffic from theopposite end. If the problem persists, go to thenext step.


----End



242

C.3.2 ETHFCS

DescriptionETHFCS indicates the number of received Ethernet data frames with FCS errors or alignmenterrors at the local end (excluding oversized and undersized frames). If the number exceeds thethreshold, an RMON threshold-crossing event will be reported.

Impact on SystemMost ports discard the packets with FCS errors or alignment errors. System services areinterrupted in the worst case.

Relevant AlarmsMAC_FCS_EXC

Possible Causes1. The working modes of the local port and opposite port mismatch. For example, one port

works in full-duplex mode, and the other port works in half-duplex mode.2. Bit errors exist on the transmission line.3. The local end is faulty.

ProcedureStep 1 Handle this alarm according to the specific performance event.

If... Then...

The number is lower than the lower threshold Change the lower threshold to 0.

The number is higher than the upper threshold Go to the next step.

Step 2 On the NMS, query the working modes of the local and opposite ports.

If... Then...

The working modes mismatch Change the working modes to the same.

The working modes match Go to the next step.

Step 3 Replace the fiber or optical module of the local or opposite port.


----End

C.3.3 ETHFRG

DescriptionETHFRG indicates the number of received packets that are smaller than 64 packets and containFCS errors or alignment errors. If the number exceeds the threshold, an RMON threshold-crossing event will be reported.



243

Impact on System

Data transmission is delayed or packet loss occurs.

Possible Causesl The local port and opposite port work in different modes.

l The local end is faulty.

l The local port and opposite port work in half-duplex mode and communicate a very highvolume of data.

Procedure

Step 1 Check whether the local port and opposite port work in the same mode.

If... Then...

The ports work in the same mode Go to the next step.

The ports work in different modes Change the working mode of the local port to the sameas the opposite port.

Step 2 Check whether the local port and opposite port work in half-duplex mode.

If... Then...

The ports do not work in half-duplexmode


The ports work in half-duplex mode Change the working modes to full-duplex orauto-negotiation.


----End

C.3.4 ETHJAB

Description

ETHJAB indicates the received packets that are larger than the preset maximum transmissionunit (MTU) and contain FCS errors or alignment errors. If the number of packets exceeds thethreshold, an RMON threshold-crossing event will be reported.

Impact on System

Data transmission is delayed or packet loss occurs.

Possible Causesl The local port and opposite port work in different modes.

l The local end is faulty.



244

Procedure

Step 1 Check whether the local port and opposite port work in the same mode.

If... Then...

The ports work in the same mode Go to the next step.

The ports work in different modes Change the working mode of the local port to the sameas the opposite port.


----End

C.3.5 ETHOVER

Description

ETHOVER indicates the number of received packets that are larger than the preset maximumtransmission unit (MTU). If the number exceeds the threshold, an RMON threshold-crossingevent will be reported.

Impact on System

A port discards the packets of a length greater than the preset maximum and therefore servicesare affected.

Possible Causes1. The received packets are larger than the preset MTU.

2. The local end is faulty.

Procedure

Step 1 Check whether the opposite end transmits packets larger than the preset maximum of the localend.

If... Then...

The opposite end transmits packets largerthan the preset maximum of the local end

Notify the opposite end that the length oftransmitted packets should be reduced.

The opposite end does not transmit packetslarger than the preset maximum of the localend



----End



245

C.3.6 ETHUNDER

DescriptionETHUNDER indicates the number of received packets that are error-free and shorter than 64bytes. If the number exceeds the threshold, an RMON threshold-crossing event will be reported.

Impact on SystemThe data frames of a length beyond the specific range are discarded. As a result, the systemservices are affected.

Possible Causes1. Excessive packets shorter than 64 bytes are received.2. The local end is faulty.

Procedure

Step 1 Check whether the opposite end transmits packets shorter than 64 bytes.

If... Then...

The opposite end transmits packets shorter than 64bytes

Rectify the fault at the opposite end.

The opposite end does not transmit packets shorterthan 64 bytes



----End

C.3.7 RXBBAD

DescriptionRXBBAD indicates the total number of bytes in received bad packets, excluding framing bitsbut including FCS bytes. If the number exceeds the threshold, an RMON threshold-crossingevent will be reported.

Impact on SystemBad packets are discarded at ports, and excessive bad packets may even interrupt system services.

Relevant AlarmsMAC_EXT_EXC

Possible Causes1. Errors occur when the opposite end transmits packets.



246

2. Bit errors exist on the transmission line.3. The local end is faulty.

Procedure

Step 1 Handle this alarm according to the specific performance event.

If... Then...

The number is lower than the lower threshold Change the lower threshold to 0.

The number is higher than the upper threshold Go to the next step.

Step 2 Browsing Current Performance Events of Ethernet, and handle the errors at the opposite enddepending on the type of bad types.

Step 3 Handle the bit errors on the transmission line.Check whether the local end reports ETH_LOS or similar alarms because the external line isdamaged or over attenuated. If yes, clear these alarms.


----End



247

D Alarm Suppression Relationship

When the alarm suppression function is disabled on an NE, the root alarm and certain correlatedalarms are reported if a fault occurs on this NE. After the alarm suppression function is enabled,the root alarm is reported but the reporting of correlated alarms is suppressed depending on thealarm suppression relationship.

Table D-1 Alarm suppression relationship

AlarmIdentifier

Identifier of the Suppressed Alarm

LSR_NO_FITED

ETH_LOS

LASER_MOD_ERR

ETH_LOS, IN_PWR_ABN

ETH_LOS ETH_NO_FLOW, IN_PWR_ABN

ETH_EFM_DF

ETH_EFM_REMFAULT

ETH_EFM_REMFAULT

ETH_EFM_EVENT

ETH_CFM_AIS

ETH_CFM_LOC

ETH_CFM_MISMERGE

ETH_CFM_UNEXPERI, ETH_CFM_LOC, ETH_CFM_RDI

ETH_CFM_UNEXPERI

ETH_CFM_LOC, ETH_CFM_RDI

ETH_CFM_LOC

ETH_CFM_RDI

MW_LOF MW_FEC_UNCOR, MW_RDI, MW_LIM, MW_BER_EXC,MW_BER_SD, AM_DOWNSHIFT, ETH_NO_FLOW

MW_LIM ETH_NO_FLOW

OptiX RTN 310 Radio Transmission SystemMaintenance Guide D Alarm Suppression Relationship


248

AlarmIdentifier

Identifier of the Suppressed Alarm

MW_BER_EXC

MW_BER_SD

OptiX RTN 310 Radio Transmission SystemMaintenance Guide D Alarm Suppression Relationship


249

E Glossary

Numerics

3G See 3rd Generation.

3rd Generation (3G) The third generation of digital wireless technology, as defined by the InternationalTelecommunications Union (ITU). Third generation technology is expected to deliverdata transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to19.2 kbit/s offered by second generation technology.

A

ABR See area border router.

ACAP See adjacent channel alternate polarization.

ACL See access control list.

AF See assured forwarding.

AIS alarm indication signal

AM See adaptive modulation.

ARP See Address Resolution Protocol.

ASBR See autonomous system boundary router.

ATM asynchronous transfer mode

ATPC See automatic transmit power control.

Address ResolutionProtocol (ARP)

An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts androuters to determine the link layer addresses through ARP requests and ARP responses.

access control list(ACL)

A list of entities, together with their access rights, which are authorized to have accessto a resource.

adaptive modulation(AM)

A technology that is used to automatically adjust the modulation mode according to thechannel quality. When the channel quality is favorable, the equipment uses a high-efficiency modulation mode to improve the transmission efficiency and the spectrumutilization of the system. When the channel quality is degraded, the equipment uses thelow-efficiency modulation mode to improve the anti-interference capability of the linkthat carries high-priority services.

OptiX RTN 310 Radio Transmission SystemMaintenance Guide E Glossary


250

adjacent channelalternate polarization(ACAP)

A channel configuration method, which uses two adjacent channels (a horizontalpolarization wave and a vertical polarization wave) to transmit two signals.

air interface The interface between the cellular phone set or wireless modem (usually portable ormobile) and the active base station.

alarm suppression An alarm management method. Alarms that are set to be suppressed are not reportedfrom NEs any more.

area border router(ABR)

A router that can belong to more than two areas of which one area must be a backbonearea.

assured forwarding(AF)

One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF.It is suitable for certain key data services that require assured bandwidth and short delay.For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic thatexceeds the bandwidth limit, AF degrades the service class and continues to forward thetraffic instead of discarding the packets.

automatic transmitpower control (ATPC)

A method of adjusting the transmit power based on fading of the transmit signal detectedat the receiver

autonomous systemboundary router(ASBR)

A router that exchanges routing information with other ASs.

B

BE See best effort.

BIOS See basic input/output system.

backup A periodic operation performed on the data stored in the database for the purposes ofdatabase recovery in case that the database is faulty. The backup also refers to datasynchronization between active and standby boards.

bandwidth A range of transmission frequencies that a transmission line or channel can carry in anetwork. In fact, it is the difference between the highest and lowest frequencies thetransmission line or channel. The greater the bandwidth, the faster the data transfer rate.

baseband A form of modulation in which the information is applied directly onto the physicaltransmission medium.

basic input/outputsystem (BIOS)

A firmware stored in the computer mainboard. It contains basic input/output controlprograms, power-on self test (POST) programs, bootstraps, and system settinginformation. The BIOS provides hardware setting and control functions for the computer.

best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwardedfollowing the sequence of the time they reach. All diagrams share the bandwidth of thenetwork and routers. The amount of resource that a diagram can use depends of the timeit reaches. BE service does not ensure any improvement in delay time, jitter, packet lossratio, and high reliability.

blacklist A method of filtering packets based on their source IP addresses. Compared with ACL,the match condition for the black list is much simpler. Therefore, the black list can filterpackets at a higher speed and can effectively screen the packet sent from the specific IPaddress.



251

bridge A device that connects two or more networks and forwards packets among them. Bridgesoperate at the physical network level. Bridges differ from repeaters because bridges storeand forward complete packets, while repeaters forward all electrical signals. Bridgesdiffer from routers because bridges use physical addresses, while routers use IPaddresses.

broadcast A means of delivering information to all members in a network. The broadcast range isdetermined by the broadcast address.

burst A process of forming data into a block of the proper size, uninterruptedly sending theblock in a fast operation, waiting for a long time, and preparing for the next fast sending.

C

CC See continuity check.

CCDP See co-channel dual polarization.

CSES consecutive severely errored second

CSMA/CD See carrier sense multiple access with collision detection.

carrier sense multipleaccess with collisiondetection (CSMA/CD)

Carrier sense multiple access with collision detection (CSMA/CD) is a computernetworking access method in which:

l A carrier sensing scheme is used.l A transmitting data station that detects another signal while transmitting a frame,

stops transmitting that frame, transmits a jam signal, and then waits for a randomtime interval before trying to send that frame again.

chain network One type of network that all network nodes are connected one after one to be in series.

channel spacing The center-to-center difference in frequency or wavelength between adjacent channelsin a WDM device.

co-channel dualpolarization (CCDP)

A channel configuration method, which uses a horizontal polarization wave and a verticalpolarization wave to transmit two signals. The Co-Channel Dual Polarization has twicethe transmission capacity of the single polarization.

congestionmanagement

A flow control measure to solve the problem of network resource competition. Whenthe network congestion occurs, it places packets into the queue for buffer and determinesthe packet forwarding order.

continuity check (CC) Ethernet CFM can detect the connectivity between MEPs. The detection is achieved afterMEPs transmit Continuity Check Messages (CCMs) periodically.

cross polarizationinterferencecancellation (XPIC)

A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminatethe cross-connect interference between two polarization waves in the CCDP.

D

DCC See data communications channel.

DCN See data communication network.

DD database description

DM See delay measurement.



252

DRDB dynamic random database

DS data service

DSCP differentiated services code point

data communicationnetwork (DCN)

A communication network used in a TMN or between TMNs to support the datacommunication function.

data communicationschannel (DCC)

The data channel that uses the D1–D12 bytes in the overhead of an STM-N signal totransmit information about operation, management, maintenance and provision(OAM&P) between NEs. The DCC channels that are composed of bytes D1–D3 arereferred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composedof bytes D4–D12 are referred to as the 576 kbit/s DCC-M channel.

delay measurement(DM)

The time elapsed since the start of transmission of the first bit of the frame by a sourcenode until the reception of the last bit of the loopbacked frame by the same source node,when the loopback is performed at the frame's destination node.

dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio wavesorthogonally polarized.

E

E-LAN See Ethernet local area network.

E-Line See Ethernet line.

E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It providesthirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization, andtimeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use as speechchannels. Each timeslot sends or receives an 8-bit data per second. Each frame sends orreceives 256-bit data per second. 8000 frames will be sent or received per second.Therefore the line data rate is 2.048 Mbit/s.

ECC See embedded control channel.

EF See expedited forwarding.

EMC See electromagnetic compatibility.

ERPS Ethernet ring protection switching

ES errored second

ESD electrostatic discharge

ETS European Telecommunication Standards

ETSI See European Telecommunications Standards Institute.

Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtualconnection).

Ethernet local areanetwork (E-LAN)

A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernetvirtual connection).

EuropeanTelecommunicationsStandards Institute(ETSI)

A standards-setting body in Europe. Also the standards body responsible for GSM.



253

electromagneticcompatibility (EMC)

A condition which prevails when telecommunications equipment is performing itsindividually designed function in a common electromagnetic environment withoutcausing or suffering unacceptable degradation due to unintentional electromagneticinterference to or from other equipment in the same environment.

embedded controlchannel (ECC)

A logical channel that uses a data communications channel (DCC) as its physical layer,to enable transmission of operation, administration, and maintenance (OAM)information between NEs.

expedited forwarding(EF)

The highest order QoS in the Diff-Serv network. EF PHB is suitable for services thatdemand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EFtraffic can guarantee a transmission rate equal to or faster than the set rate. The DSCPvalue of EF PHB is "101110".

extended ID The number of the subnet that an NE belongs to, for identifying different networksegments in a WAN. The physical ID of an NE is comprised of the NE ID and extendedID.

extended NE ID The serial number of a subnetwork where an NE resides, which is usually used todistinguish different network segments. An extended ID and an ID form the physical IDof an NE.

F

FE See fast Ethernet.

FEC See forward error correction.

FIFO See first in first out.

FPGA See field programmable gate array.

FTP File Transfer Protocol

fast Ethernet (FE) Any network that supports transmission rate of 100 Mbit/s. The Fast Ethernet is 10 timesfaster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and soon. Fast Ethernet is extended based on the IEEE802.3 standard, and it uses the followingthree types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core opticalfibers).

field programmablegate array (FPGA)

A type of semi-customized circuit used in the application specific integrated circuit(ASIC) field. It is developed on the basis of the programmable components, such as thePAL, GAL, and EPLD. It not only remedies the defects of customized circuits but alsoovercomes the disadvantage of the original programmable components in terms of thelimited number of gate arrays.

first in first out (FIFO) A stack management mechanism. The first saved data is first read and invoked.

flooding A type of incident, such as insertion of a large volume of data, that results in denial ofservice.

forward errorcorrection (FEC)

A bit error correction technology that adds the correction information to the payload atthe transmit end. Based on the correction information, the bit errors generated duringtransmission are corrected at the receive end.

G

GE See gigabit Ethernet.



254

GNE See gateway network element.

gateway A device that connects two network segments using different protocols. It is used totranslate the data in the two network segments.

gateway networkelement (GNE)

A network element that is used for communication between the NE application layer andthe NM application layer.

gigabit Ethernet (GE) A collection of technologies for transmitting Ethernet frames at a rate of a gigabit persecond, as defined by the IEEE 802.3z standard. GE is compatible with 10 Mbit/s and100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, andit does not support coaxial cables or other cables. It also supports the channels in thebandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidthsystem with a bridge (switch) or a router as the center, it gives full play to the performanceand the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links thatare private, causing the length of the links to be sufficient for backbone applications ina building and campus.

H

HSDPA See High Speed Downlink Packet Access.

HUAWEI ElectronicDocument Explorer(HedEx)

The software used to view, search for, and upgrade electronic documentation of Huaweiproducts. HedEx, pronounced as [hediks], has two editions, HedEx Lite and HedExServer.

HedEx See HUAWEI Electronic Document Explorer.

High Speed DownlinkPacket Access(HSDPA)

A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirementfor asymmetric uplink and downlink transmission of data services. It enables themaximum downlink data service rate to reach 14.4 Mbit/s without changing theWCDMA network topology.

I

ICMP See Internet Control Message Protocol.

IDU See indoor unit.

IEEE See Institute of Electrical and Electronics Engineers.

IETF See Internet Engineering Task Force.

IP Internet Protocol

IP address A 32-bit (4-byte) binary digit that uniquely identifies a host (computer) connected to theInternet for communication with other hosts in the Internet by transferring packets. AnIP address is expressed in dotted decimal notation, consisting of decimal values of its 4bytes, separated by periods (,), for example, 127.0.0.1. The first three bytes of an IPaddress identify the network to which the host is connected, and the last byte identifiesthe host itself.

IPv4 See Internet Protocol version 4.

IPv6 See Internet Protocol version 6.

ISO International Organization for Standardization

ITU See International Telecommunication Union.



255

ITU-T See International Telecommunication Union-Telecommunication StandardizationSector.

Institute of Electricaland ElectronicsEngineers (IEEE)

A society of engineering and electronics professionals based in the United States butboasting membership from numerous other countries. The IEEE focuses on electrical,electronics, computer engineering, and science-related matters.

InternationalTelecommunicationUnion (ITU)

A United Nations agency, one of the most important and influential recommendationbodies, responsible for recommending standards for telecommunication (ITU-T) andradio networks (ITU-R).

InternationalTelecommunicationUnion-TelecommunicationStandardization Sector(ITU-T)

An international body that develops worldwide standards for telecommunicationstechnologies. These standards are grouped together in series which are prefixed with aletter indicating the general subject and a number specifying the particular standard. Forexample, X.25 comes from the "X" series which deals with data networks and opensystem communications and number "25" deals with packet switched networks.

Internet ControlMessage Protocol(ICMP)

A network-layer (ISO/OSI level 3) Internet protocol that provides error correction andother information relevant to IP packet processing. For example, it can let the IP softwareon one machine inform another machine about an unreachable destination. See alsocommunications protocol, IP, ISO/OSI reference model, packet (definition 1).

Internet EngineeringTask Force (IETF)

A worldwide organization of individuals interested in networking and the Internet.Managed by the Internet Engineering Steering Group (IESG), the IETF is charged withstudying technical problems facing the Internet and proposing solutions to the InternetArchitecture Board (IAB). The work of the IETF is carried out by various working groupsthat concentrate on specific topics such as routing and security. The IETF is the publisherof the specifications that led to the TCP/IP protocol standard.

Internet Protocolversion 4 (IPv4)

The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which isassigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and iswritten as 4 octets separated by periods and may range from 0.0.0.0 through to255.255.255.255. Each IPv4 address consists of a network number, an optionalsubnetwork number, and a host number. The network and subnetwork numbers togetherare used for routing, and the host number is used to address an individual host within thenetwork or subnetwork.

Internet Protocolversion 6 (IPv6)

An update version of IPv4, which is designed by the Internet Engineering Task Force(IETF) and is also called IP Next Generation (IPng). It is a new version of the InternetProtocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits whilean IPv6 address has 128 bits.

indoor unit (IDU) The indoor unit of the split-structured radio equipment. It implements accessing,multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.

J

jitter Short waveform variations caused by vibration, voltage fluctuations, and control systeminstability.

L

L2VPN Layer 2 virtual private network

LACP See Link Aggregation Control Protocol.



256

LAG See link aggregation group.

LAN See local area network.

LB See loopback.

LBM See loopback message.

LBR See loopback reply.

LCT local craft terminal

LM See loss measurement.

LOS See loss of signal.

LSA link-state advertisement

LSDB link state database

LSR See label switching router.

LT linktrace

LTM See linktrace message.

LTR See linktrace reply.

Layer 2 switching A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switchtransmits and distributes packet data based on the MAC address. Since the MAC addressis at the second layer of the OSI model, this data forwarding method is called Layer 2switching.

Link AggregationControl Protocol(LACP)

A method of bundling a group of physical interfaces together as a logical interface toincrease bandwidth and reliability. For related protocols and standards, refer to IEEE802.3ad.

label switching router(LSR)

Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR iscomposed of two parts: control unit and forwarding unit. The former is responsible forallocating the label, selecting the route, creating the label forwarding table, creating andremoving the label switch path; the latter forwards the labels according to groupsreceived in the label forwarding table.

link aggregation group(LAG)

An aggregation that allows one or more links to be aggregated together to form a linkaggregation group so that a MAC client can treat the link aggregation group as if it werea single link.

linktrace message(LTM)

The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP.LTM includes the Time to Live (TTL) and the MAC address of the destination MEP2.

linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to thesource MEP after the destination MEP receives the LTM, and the response message iscalled LTR. LTR also includes the TTL that equals the result of the TTL of LTM minus1.

local area network(LAN)

A network formed by the computers and workstations within the coverage of a few squarekilometers or within a single building. It features high speed and low error rate. Ethernet,FDDI, and Token Ring are three technologies used to implement a LAN. Current LANsare generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/s (that is, 1 Gbit/s).

loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that thesignal or message can be analyzed for errors. The loopback can be a inloop or outloop.



257

loopback message(LBM)

The loopback packet sent by the node that supports 802.2ag MAC Ping to the destinationnode. LBM message carries its own sending time.

loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which thedestination MEP replies to the source MEP after the destination MEP receives the LBM.The LBR carries the sending time of LBM, the receiving time of LBM and the sendingtime of LBR.

loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frameswhere the counters maintain a count of transmitted and received data frames between apair of MEPs.

loss of signal (LOS) No transitions occurring in the received signal.

M

MA maintenance association

MAC See Media Access Control.

MAC address A link layer address or physical address. It is six bytes long.

MD See maintenance domain.

MDI medium dependent interface

ME maintenance entity

MEP maintenance end point

MIB See management information base.

MIP maintenance intermediate point

MP maintenance point

MPLS See Multiprotocol Label Switching.

MSTP See Multiple Spanning Tree Protocol.

MTBF See mean time between failures.

MTTR See mean time to repair.

MTU See maximum transmission unit.

Media Access Control(MAC)

A protocol at the media access control sublayer. The protocol is at the lower part of thedata link layer in the OSI model and is mainly responsible for controlling and connectingthe physical media at the physical layer. When transmitting data, the MAC protocolchecks whether to be able to transmit data. If the data can be transmitted, certain controlinformation is added to the data, and then the data and the control information aretransmitted in a specified format to the physical layer. When receiving data, the MACprotocol checks whether the information is correct and whether the data is transmittedcorrectly. If the information is correct and the data is transmitted correctly, the controlinformation is removed from the data and then the data is transmitted to the LLC layer.

Multiple SpanningTree Protocol (MSTP)

A protocol that can be used in a loop network. Using an algorithm, the MSTP blocksredundant paths so that the loop network can be trimmed as a tree network. In this case,the proliferation and endless cycling of packets is avoided in the loop network. Theprotocol that introduces the mapping between VLANs and multiple spanning trees. Thissolves the problem that data cannot be normally forwarded in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.



258

Multiprotocol LabelSwitching (MPLS)

A technology that uses short tags of fixed length to encapsulate packets in different linklayers, and provides connection-oriented switching for the network layer on the basis ofIP routing and control protocols. It improves the cost performance and expandability ofnetworks, and is beneficial to routing.

maintenance domain(MD)

The network or the part of the network for which connectivity is managed by connectivityfault management (CFM). The devices in a maintenance domain are managed by a singleInternet service provider (ISP).

managementinformation base (MIB)

A type of database used for managing the devices in a communications network. Itcomprises a collection of objects in a (virtual) database used to manage entities (such asrouters and switches) in a network.

maximum transmissionunit (MTU)

The largest packet of data that can be transmitted on a network. MTU size varies,depending on the network—576 bytes on X.25 networks, for example, 1500 bytes onEthernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining thesize of the MTU lies with the link layer of the network. When packets are transmittedacross networks, the path MTU, or PMTU, represents the smallest packet size (the onethat all networks can transmit without breaking up the packet) among the networksinvolved.

mean time betweenfailures (MTBF)

The average time between consecutive failures of a piece of equipment. It is a measureof the reliability of the system.

mean time to repair(MTTR)

The average time that a device will take to recover from a failure.

microwave The portion of the electromagnetic spectrum with much longer wavelengths than infraredradiation, typically above about 1 mm.

multicast A process of transmitting data packets from one source to many destinations. Thedestination address of the multicast packet uses Class D address, that is, the IP addressranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a multicastgroup rather than a host.

N

NAS network access server

NE network element

NE Explorer The main operation interface, of the network management system, which is used tomanage the telecommunication equipment. In the NE Explorer, the user can query,manage and maintain the NE, boards, and ports on a per-NE basis.

NTP Network Time Protocol

network segment A part of an Ethernet or other network, on which all message traffic is common to allnodes, that is, it is broadcast from one node on the segment and received by all others.

network storm A phenomenon that occurs during data communication. To be specific, mass broadcastpackets are transmitted in a short time; the network is congested; transmission qualityand availability of the network decrease rapidly. The network storm is caused by networkconnection or configuration problems.

O

OAM See operation, administration and maintenance.



259

ODF optical distribution frame

ODU See outdoor unit.

OSI See open systems interconnection.

OSPF See Open Shortest Path First.

Open Shortest PathFirst (OSPF)

A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra'salgorithm is used to calculate the shortest path tree. It uses cost as its routing metric. Alink state database is constructed with the network topology which is identical on allrouters in the area.

open systemsinterconnection (OSI)

A framework of ISO standards for communication between different systems made bydifferent vendors, in which the communications process is organized into seven differentcategories that are placed in a layered sequence based on their relationship to the user.Each layer uses the layer immediately below it and provides a service to the layer above.Layers 7 through 4 deal with end-to-end communication between the message sourceand destination, and layers 3 through 1 deal with network functions.

operation,administration andmaintenance (OAM)

A group of network support functions that monitor and sustain segment operation,support activities that are concerned with, but not limited to, failure detection,notification, location, and repairs that are intended to eliminate faults and keep a segmentin an operational state, and support activities required to provide the services of asubscriber access network to users/subscribers.

outdoor unit (ODU) The outdoor unit of the split-structured radio equipment. It implements frequencyconversion and amplification for radio frequency (RF) signals.

P

P2P See point-to-point service.

PBS See peak burst size.

PDU protocol data unit

PHB See per-hop behavior.

PLL See phase-locked loop.

PPP Point-to-Point Protocol

PPPoE Point-to-Point Protocol over Ethernet

PRBS See pseudo random binary sequence.

PSN See packet switched network.

PTP Precision Time Protocol

PWE3 See pseudo wire emulation edge-to-edge.

packet loss The discarding of data packets in a network when a device is overloaded and cannotaccept any incoming data at a given moment.

packet switchednetwork (PSN)

A telecommunications network that works in packet switching mode.

peak burst size (PBS) A parameter that is used to define the capacity of token bucket P, that is, the maximumburst IP packet size when the information is transferred at the peak information rate. Thisparameter must be larger than 0. It is recommended that PBS should be not less than themaximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR.



260

per-hop behavior(PHB)

IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hopbehaviors (PHB), such as, traffic scheduling and policing. A device in the network shouldselect the proper PHB behaviors, based on the value of DSCP. At present, the IETFdefines four types of PHB. They are class selector (CS), expedited forwarding (EF),assured forwarding (AF), and best-effort (BE).

phase-locked loop(PLL)

A circuit that consists essentially of a phase detector which compares the frequency ofa voltage-controlled oscillator with that of an incoming carrier signal or reference-frequency generator; the output of the phase detector, after passing through a loop filter,is fed back to the voltage-controlled oscillator to keep it exactly in phase with theincoming or reference frequency.

physical layer Layer 1 in the Open System Interconnection (OSI) architecture; the layer that providesservices to transmit bits or groups of bits over a transmission link between open systemsand which entails electrical, mechanical and handshaking.

point-to-point service(P2P)

A service between two terminal users. In P2P services, senders and recipients areterminal users.

polarization A kind of electromagnetic wave, the direction of whose electric field vector is fixed orrotates regularly. Specifically, if the electric field vector of the electromagnetic wave isperpendicular to the plane of horizon, this electromagnetic wave is called verticallypolarized wave; if the electric field vector of the electromagnetic wave is parallel to theplane of horizon, this electromagnetic wave is called horizontal polarized wave; if thetip of the electric field vector, at a fixed point in space, describes a circle, thiselectromagnetic wave is called circularly polarized wave.

policy A set of rules that are applied when the conditions for triggering an event are met.

pseudo random binarysequence (PRBS)

A sequence that is random in a sense that the value of an element is independent of thevalues of any of the other elements, similar to real random sequences.

pseudo wire emulationedge-to-edge (PWE3)

An end-to-end Layer 2 transmission technology. It emulates the essential attributes of atelecommunication service such as ATM, FR or Ethernet in a packet switched network(PSN). PWE3 also emulates the essential attributes of low speed time divisionmultiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the realsituation.

Q

QPSK See quadrature phase shift keying.

QoS See quality of service.

quadrature phase shiftkeying (QPSK)

A modulation method of data transmission through the conversion or modulation andthe phase determination of the reference signals (carrier). It is also called the fourth periodor 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots areevenly distributed on a circle. On these phases, each QPSK character can perform two-bit coding and display the codes in Gray code on graph with the minimum BER.

quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel.Depending on the specific system and service, it may relate to jitter, delay, packet lossratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of thetransmission system and the effectiveness of the services, as well as the capability of aservice provider to meet the demands of users.

R



261

RADIUS See Remote Authentication Dial-In User Service.

RADIUSauthentication

An authentication mode in which the BRAS sends the user name and the password tothe RADIUS server by using the RADIUS protocol. The RADIUS server authenticatesthe user, and then returns the result to the BRAS.

RDI remote defect indication

RED See random early detection.

RF See radio frequency.

RFC See Request For Comments.

RMON remote network monitoring

RNC See radio network controller.

RSL See received signal level.

RSSI See received signal strength indicator.

RTN radio transmission node

Remote AuthenticationDial-In User Service(RADIUS)

A security service that authenticates and authorizes dial-up users and is a centralizedaccess control mechanism. RADIUS uses the User Datagram Protocol (UDP) as itstransmission protocol to ensure real-time quality. RADIUS also supports theretransmission and multi-server mechanisms to ensure good reliability.

Request For Comments(RFC)

A document in which a standard, a protocol, or other information pertaining to theoperation of the Internet is published. The RFC is actually issued, under the control ofthe IAB, after discussion and serves as the standard. RFCs can be obtained from sourcessuch as InterNIC.

radio frequency (RF) A type of electric current in the wireless network using AC antennas to create anelectromagnetic field. It is the abbreviation of high-frequency AC electromagnetic wave.The AC with the frequency lower than 1 kHz is called low-frequency current. The ACwith frequency higher than 10 kHz is called high-frequency current. RF can be classifiedinto such high-frequency current.

radio networkcontroller (RNC)

A piece of equipment in the RNS which is in charge of controlling the use and the integrityof the radio resources.

random early detection(RED)

A packet loss algorithm used in congestion avoidance. It discards the packet accordingto the specified higher limit and lower limit of a queue so that global TCP synchronizationresulting from traditional tail drop can be prevented.

received signal level(RSL)

The signal level at a receiver input terminal.

received signal strengthindicator (RSSI)

The received wide band power, including thermal noise and noise generated in thereceiver, within the bandwidth defined by the receiver pulse shaping filter, for TDDwithin a specified timeslot. The reference point for the measurement shall be the antenna

receiver sensitivity The minimum acceptable value of average received power at point R to achieve a 1 x10-12 BER (The FEC is open).

route The path that network traffic takes from its source to its destination. In a TCP/IP network,each IP packet is routed independently. Routes can change dynamically.

routing table A mapping table that stores the relationship between the original address, destinationaddress, SMS protocol type, and account. The SMSC delivers an SMS message to thedesignated account according to the information in the routing table.



262

S

SD See signal degrade.

SF See signal fail.

SFP small form-factor pluggable

SNMP See Simple Network Management Protocol.

SNR See signal-to-noise ratio.

SPF shortest path first

SSL See Secure Sockets Layer.

SSM See Synchronization Status Message.

Secure Sockets Layer(SSL)

A security protocol that works at a socket level. This layer exists between the TCP layerand the application layer to encrypt/decode data and authenticate concerned entities.

Simple NetworkManagement Protocol(SNMP)

A network management protocol of TCP/IP. It enables remote users to view and modifythe management information of a network element. This protocol ensures thetransmission of management information between any two points. The pollingmechanism is adopted to provide basic function sets. According to SNMP, agents, whichcan be hardware as well as software, can monitor the activities of various devices on thenetwork and report these activities to the network console workstation. Controlinformation about each device is maintained by a management information block.

Synchronization StatusMessage (SSM)

A message that carries quality levels of timing signals on a synchronous timing link.Nodes on an SDH network and a synchronization network acquire upstream clockinformation through this message. Then the nodes can perform proper operations on theirclocks, such as tracing, switching, or converting to holdoff, and forward thesynchronization information to downstream nodes.

service flow An MAC-layer-based unidirectional transmission service. It is used to transmit datapackets, and is characterized by a set of QoS parameters, such as latency, jitter, andthroughput.

shaping A process of delaying packets within a traffic stream to cause it to conform to specificdefined traffic profile.

signal degrade (SD) A signal indicating that associated data has degraded in the sense that a degraded defectcondition is active.

signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defectcondition (non-degrade defect) is active.

signal-to-noise ratio(SNR)

The ratio of the amplitude of the desired signal to the amplitude of noise signals at agiven point in time. SNR is expressed as 10 times the logarithm of the power ratio andis usually expressed in dB (Decibel).

single-polarizedantenna

An antenna intended to radiate or receive radio waves with only one specifiedpolarization.

subnet mask The technique used by the IP protocol to determine which network segment packets aredestined for. The subnet mask is a binary pattern that is stored in the client machine,server or router matches with the IP address.

T



263

TCP/IP Transmission Control Protocol/Internet Protocol

TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.

Time Division-Synchronous CodeDivision MultipleAccess (TD-SCDMA)

A 3G mobile communications standard found in UMTS mobile telecommunicationsnetworks in China as an alternative to W-CDMA. TD-SCDMA integrates technologiesof CDMA, TDMA, and FDMA, and makes use of technologies including intelligentantenna, joint detection, low chip rate (LCR), and adaptive power control. With theflexibility of service processing, a TD-SCDMA network can connect to other networksthrough the RNC.

tail drop A congestion management mechanism, in which packets arrive later are discarded whenthe queue is full. This policy of discarding packets may result in network-widesynchronization due to the TCP slow startup mechanism.

tolerance Permissible degree of variation from a pre-set standard.

traffic classification A function that enables you to classify traffic into different classes with differentpriorities according to some criteria. Each class of traffic has a specified QoS in the entirenetwork. In this way, different traffic packets can be treated differently.

traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee theperformance and minimize the delay. It actively adjusts the output speed of traffic in thescenario that the traffic matches network resources provided by the lower layer devices,avoiding packet loss and congestion.

U

UAS unavailable second

UAT See unavailable time event.

UDP See User Datagram Protocol.

UNI See user-to-network interface.

User DatagramProtocol (UDP)

A TCP/IP standard protocol that allows an application program on one device to send adatagram to an application program on another. User Datagram Protocol (UDP) uses IPto deliver datagram. UDP provides application programs with the unreliableconnectionless packet delivery service. There is a possibility that UDP messages will belost, duplicated, delayed, or delivered out of order. The destination device does notconfirm whether a data packet is received.

unavailable time event(UAT)

An event that is reported when the monitored object generates 10 consecutive severelyerrored seconds (SES) and the SESs begin to be included in the unavailable time. Theevent will end when the bit error ratio per second is better than 10-3 within 10 consecutiveseconds.

unicast The process of sending data from a source to a single recipient.

user-to-networkinterface (UNI)

The interface between user equipment and private or public network equipment (forexample, ATM switches).

V

VB virtual bridge

VLAN virtual local area network

VM virtual memory



264

W

WAN See wide area network.

WEEE waste electrical and electronic equipment

WRED See weighted random early detection.

WRR weighted round robin

WTR See wait to restore.

Web LCT The local maintenance terminal of a transport network, which is located at the NEmanagement layer of the transport network.

wait to restore (WTR) The number of minutes to wait before services are switched back to the working line.

weighted random earlydetection (WRED)

A packet loss algorithm used for congestion avoidance. It can prevent the global TCPsynchronization caused by traditional tail-drop. WRED is favorable for the high-prioritypacket when calculating the packet loss ratio.

wide area network(WAN)

A network composed of computers which are far away from each other which arephysically connected through specific protocols. WAN covers a broad area, such as aprovince, a state or even a country.

window General method for speech preprocessing, like Haming window.

X

XPIC See cross polarization interference cancellation.



265