RTN 605 Maintenance Guide(V100R005C00_03)

OptiX RTN 605 Radio Transmission SystemV100R005C00

Maintenance Guide

Issue 03

Date 2010-05-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. 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 the 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 03 (2010-05-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 605 1D/2D/1E/2E V100R005C00

iManager U2000 V100R002C00

Product Name Version

OptiX RTN 605 1F/2F V100R003C00

iManager U2000 V100R002C00

Intended AudienceThis document is intended for the maintenance engineers of the OptiX RTN 605. Before readingthis document, you need to:

l Network planning engineer

l Data configuration engineer

l System maintenance engineer

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

OptiX RTN 605Maintenance Guide About This Document


iii

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.

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.

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

Convention Description

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 versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 03 (2010-05-30)

This document is the third release of the V100R005C00 version.

Updates in Issue 02 (2010-03-30)

This document is the second release of the V100R005C00 version.

About This DocumentOptiX RTN 605

Maintenance Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

Update Description

A Alarm Reference Deleted the alarm SWDL_PKGVER_MM.

Updates in Issue 01 (2009-12-30)This document is the first release of the V100R005C00 version.

OptiX RTN 605Maintenance Guide About This Document


v

Contents

About This Document...................................................................................................................iii

1 Safety Precautions......................................................................................................................1-11.1 General Safety Precautions.............................................................................................................................1-11.2 Electrical Safety..............................................................................................................................................1-31.3 Flammable Air Environment...........................................................................................................................1-51.4 Radiation.........................................................................................................................................................1-51.5 Working at Heights.........................................................................................................................................1-61.6 Mechanical Safety...........................................................................................................................................1-91.7 Other Precautions..........................................................................................................................................1-10

2 Guides to High-Risk Operations............................................................................................2-12.1 Operation Guide to a Toggle Lever Switch.....................................................................................................2-22.2 Operation Guide to IF Jumpers.......................................................................................................................2-32.3 Operation Guide to IF Cables..........................................................................................................................2-4

3 Routine Maintenance................................................................................................................3-13.1 Routine Maintenance Items.............................................................................................................................3-23.2 Guidelines for Routine Maintenance Items.....................................................................................................3-3

3.2.1 Checking the Status of NEs....................................................................................................................3-43.2.2 Browsing the Current Alarms................................................................................................................3-53.2.3 Browsing the History Alarms.................................................................................................................3-53.2.4 Browsing the Abnormal Events.............................................................................................................3-63.2.5 Browsing the Current Performance........................................................................................................3-73.2.6 Browsing the History Performance........................................................................................................3-83.2.7 Browsing the History Transmit Power and Receive Power...................................................................3-93.2.8 Testing IF 1+1 Switching.....................................................................................................................3-103.2.9 Checking the Equipment Room...........................................................................................................3-113.2.10 Checking the ODU.............................................................................................................................3-113.2.11 Checking the Hybrid Coupler............................................................................................................3-123.2.12 Checking the Antenna........................................................................................................................3-123.2.13 Checking the IF Cables......................................................................................................................3-133.2.14 Checking the LOS Condition.............................................................................................................3-14

4 Emergency Maintenance...........................................................................................................4-14.1 Definition of Emergency.................................................................................................................................4-2

OptiX RTN 605Maintenance Guide Contents


vii

4.2 Purposes of Emergence Maintenance..............................................................................................................4-24.3 Procedure of Emergency Maintenance............................................................................................................4-2

5 Troubleshooting.........................................................................................................................5-15.1 General Troubleshooting Procedure................................................................................................................5-25.2 Troubleshooting Service Interruption.............................................................................................................5-45.3 Troubleshooting Radio Links..........................................................................................................................5-95.4 Troubleshooting the Interconnection with the PDH Equipment...................................................................5-175.5 Troubleshooting Ethernet Service Faults......................................................................................................5-195.6 Troubleshooting Orderwire Faults................................................................................................................5-24

6 Part Replacement........................................................................................................................6-16.1 Replacing the IDU...........................................................................................................................................6-26.2 Replacing an ODU..........................................................................................................................................6-26.3 Replacing the IF Cable....................................................................................................................................6-4

7 Supporting Task.........................................................................................................................7-17.1 Hardware Loopback........................................................................................................................................7-37.2 Cleaning Fiber Connectors and Adapters........................................................................................................7-3

7.2.1 Cleaning Fiber Connectors Using Cartridge Cleaners...........................................................................7-37.2.2 Cleaning Fiber Connectors Using Lens Tissue......................................................................................7-57.2.3 Cleaning Fiber Adapters Using Optical Cleaning Sticks.......................................................................7-6

7.3 Browsing Alarms, Abnormal Events, and Performance Events.....................................................................7-77.3.1 Checking the NE Status..........................................................................................................................7-87.3.2 Checking the Board Status.....................................................................................................................7-97.3.3 Browsing the Current Alarms................................................................................................................7-97.3.4 Browsing History Alarms.....................................................................................................................7-107.3.5 Browsing the Abnormal Events...........................................................................................................7-117.3.6 Browsing Current Performance Events................................................................................................7-127.3.7 Browsing the History Performance......................................................................................................7-127.3.8 Browsing the Performance Event Threshold-Crossing Records..........................................................7-14

7.4 Querying a Report.........................................................................................................................................7-147.4.1 Querying a Board Information Report Through the Web LCT............................................................7-157.4.2 Querying a Board Manufacture Information Report............................................................................7-157.4.3 Querying the Status of a Radio Link....................................................................................................7-16

7.5 Software loopback.........................................................................................................................................7-177.5.1 Setting Tributary Loopback.................................................................................................................7-177.5.2 Setting Loopback for the IF Port..........................................................................................................7-187.5.3 Setting Loopback for the Ethernet Port of the RTN 605 1F/2F...........................................................7-197.5.4 Locating the Fault by Performing Loopbacks......................................................................................7-20

7.6 SCC Resetting...............................................................................................................................................7-227.7 PRBS Test.....................................................................................................................................................7-22

7.7.1 PRBS Test of the Tributary Unit..........................................................................................................7-227.7.2 PRBS Test of the IF Unit.....................................................................................................................7-24

ContentsOptiX RTN 605

Maintenance Guide

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

7.8 Setting the Automatic Release Function.......................................................................................................7-267.9 Configuring Performance Monitoring Status of NEs....................................................................................7-267.10 Querying the Impedance of an E1 Channel.................................................................................................7-277.11 Querying the Working Status of an Ethernet Port.......................................................................................7-287.12 Setting the Threshold of Received Traffic Flow on an Ethernet Port.........................................................7-287.13 Performing Statistics for the Traffic Flow on an Ethernet Port..................................................................7-29

A Alarm Reference.......................................................................................................................A-1A.1 Alarm List......................................................................................................................................................A-2A.2 Alarms and Handling Procedures..................................................................................................................A-5

A.2.1 BD_STATUS.......................................................................................................................................A-5A.2.2 CONFIG_NOSUPPORT......................................................................................................................A-6A.2.3 DBMS_ERROR...................................................................................................................................A-8A.2.4 DBMS_PROTECT_MODE...............................................................................................................A-10A.2.5 DOWN_E1_AIS.................................................................................................................................A-11A.2.6 E1_LOC..............................................................................................................................................A-12A.2.7 ETH_CFM_MISMERGE...................................................................................................................A-13A.2.8 ETH_CFM_UNEXPERI....................................................................................................................A-15A.2.9 ETH_CFM_LOC................................................................................................................................A-17A.2.10 ETH_CFM_RDI...............................................................................................................................A-19A.2.11 ETH_LOS.........................................................................................................................................A-21A.2.12 ETHOAM_DISCOVER_FAIL........................................................................................................A-22A.2.13 ETHOAM_RMT_CRIT_FAULT....................................................................................................A-24A.2.14 ETHOAM_RMT_LOOP..................................................................................................................A-25A.2.15 ETHOAM_RMT_SD.......................................................................................................................A-27A.2.16 ETHOAM_SELF_LOOP.................................................................................................................A-28A.2.17 EX_ETHOAM_CC_LOS.................................................................................................................A-30A.2.18 EX_ETHOAM_MPID_CNFLCT....................................................................................................A-32A.2.19 FLOW_OVER..................................................................................................................................A-34A.2.20 HARD_BAD....................................................................................................................................A-35A.2.21 IF_CABLE_OPEN...........................................................................................................................A-37A.2.22 IF_INPWR_ABN.............................................................................................................................A-38A.2.23 LAG_PORT_FAIL...........................................................................................................................A-40A.2.24 LOOP_ALM.....................................................................................................................................A-42A.2.25 MSSW_DIFFERENT.......................................................................................................................A-44A.2.26 MW_BER_EXC...............................................................................................................................A-46A.2.27 MW_BER_SD..................................................................................................................................A-47A.2.28 MW_FEC_UNCOR.........................................................................................................................A-48A.2.29 MW_LIM.........................................................................................................................................A-53A.2.30 MW_LOF.........................................................................................................................................A-54A.2.31 MW_RDI..........................................................................................................................................A-59A.2.32 NESF_LOST....................................................................................................................................A-60A.2.33 NESTATE_INSTALL......................................................................................................................A-62



ix

A.2.34 POWER_ALM.................................................................................................................................A-63A.2.35 R_LOC.............................................................................................................................................A-64A.2.36 R_LOF..............................................................................................................................................A-65A.2.37 R_LOS..............................................................................................................................................A-67A.2.38 RADIO_FADING_MARGIN_INSUFF..........................................................................................A-68A.2.39 RADIO_MUTE................................................................................................................................A-70A.2.40 RADIO_RSL_BEYONDTH............................................................................................................A-71A.2.41 RADIO_RSL_HIGH........................................................................................................................A-72A.2.42 RADIO_RSL_LOW.........................................................................................................................A-74A.2.43 RADIO_TSL_HIGH........................................................................................................................A-75A.2.44 RADIO_TSL_LOW.........................................................................................................................A-76A.2.45 RELAY_ALARM............................................................................................................................A-77A.2.46 RP_LOC...........................................................................................................................................A-78A.2.47 RPS_INDI.........................................................................................................................................A-79A.2.48 SWDL_ACTIVATED_TIMEOUT..................................................................................................A-81A.2.49 SWDL_AUTOMATCH_INH..........................................................................................................A-82A.2.50 SWDL_COMMIT_FAIL.................................................................................................................A-83A.2.51 SWDL_CHGMNG_NOMATCH.....................................................................................................A-83A.2.52 SWDL_INPROCESS.......................................................................................................................A-84A.2.53 SWDL_NEPKGCHECK..................................................................................................................A-85A.2.54 SWDL_PKG_NOBDSOFT..............................................................................................................A-86A.2.55 SWDL_ROLLBACK_FAIL............................................................................................................A-87A.2.56 T_ALOS...........................................................................................................................................A-87A.2.57 TEMP_ALARM...............................................................................................................................A-89A.2.58 UP_E1_AIS......................................................................................................................................A-90A.2.59 VOLT_LOS......................................................................................................................................A-91

B Abnormal Event Reference.....................................................................................................B-1B.1 Important Abnormal Events...........................................................................................................................B-2B.2 Important Abnormal Events and Handling Procedures.................................................................................B-2

B.2.1 IF 1+1 Protection Switching.................................................................................................................B-2B.2.2 RMON Performance Value Below the Lower Limit............................................................................B-4B.2.3 RMON Performance Value Above the Upper Limit............................................................................B-5

C Performance Event Reference................................................................................................C-1C.1 Performance Event List..................................................................................................................................C-2

C.1.1 Microwave Performance Events...........................................................................................................C-2C.1.2 Other Performance Events....................................................................................................................C-4

C.2 Performance Events and Handling Procedures..............................................................................................C-5C.2.1 ATPC_P_ADJUST and ATPC_N_ADJUST.......................................................................................C-5C.2.2 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS...............................................................................C-6C.2.3 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG...........................................................................C-7C.2.4 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG..........................................................................C-8C.2.5 RLHTT, RLLTT, TLHTT, and TLLTT................................................................................................C-8

ContentsOptiX RTN 605

Maintenance Guide

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

C.2.6 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and FEC_UNCOR_BLOCK_CNT.........................C-9C.2.7 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256.......................C-10C.2.8 BDTMPMAX, BDTMPMIN, and BDTMPCUR...............................................................................C-10

D RMON Event Reference.........................................................................................................D-1D.1 List of RMON Alarm Entries........................................................................................................................D-2D.2 List of RMON Performance Entries..............................................................................................................D-2D.3 RMON Alarm Clearance Reference..............................................................................................................D-4

D.3.1 UndersizePkts.......................................................................................................................................D-4D.3.2 OversizePkts.........................................................................................................................................D-5D.3.3 Fragments.............................................................................................................................................D-6D.3.4 Jabbers..................................................................................................................................................D-6D.3.5 FCSErrors.............................................................................................................................................D-7

E Alarm Management..................................................................................................................E-1E.1 NE Alarm Management..................................................................................................................................E-2E.2 Board Alarm Management.............................................................................................................................E-2

E.2.1 Setting the Alarm Severity....................................................................................................................E-2E.2.2 Alarm Suppression................................................................................................................................E-3E.2.3 Alarm Auto-Report................................................................................................................................E-3E.2.4 Alarm Reversion....................................................................................................................................E-3E.2.5 Setting of the Bit Error Alarm Threshold..............................................................................................E-4

F Performance Event Management............................................................................................F-1F.1 NE Performance Event Management............................................................................................................. F-2F.2 Board Performance Event Management......................................................................................................... F-2

G Alarm Suppression Relationship.........................................................................................G-1

H Glossary.....................................................................................................................................H-1H.1 0-9..................................................................................................................................................................H-2H.2 A-E................................................................................................................................................................H-2H.3 F-J................................................................................................................................................................H-11H.4 K-O..............................................................................................................................................................H-16H.5 P-T...............................................................................................................................................................H-22H.6 U-Z..............................................................................................................................................................H-30



xi

Figures

Figure 1-1 Wearing an ESD wrist strap...............................................................................................................1-5Figure 1-2 Weight lifting......................................................................................................................................1-7Figure 1-3 Schematic diagram of slanting a ladder..............................................................................................1-8Figure 1-4 Schematic diagram of the ladder one meter higher than the eave......................................................1-8Figure 2-1 Toggle lever switch............................................................................................................................2-2Figure 4-1 Main procedure of emergency maintenance.......................................................................................4-3Figure 4-2 Procedure of on-site fault handling.....................................................................................................4-6Figure 5-1 General fault locating procedures.......................................................................................................5-3Figure 5-2 Flow of handling a service interruption..............................................................................................5-5Figure 5-3 Procedure of on-site fault handling.....................................................................................................5-7Figure 5-4 Flow of handling radio link faults....................................................................................................5-13Figure 5-5 Flow of troubleshooting the interconnection with the PDH equipment...........................................5-18Figure 5-6 Flow of handling an Ethernet service fault.......................................................................................5-21Figure 5-7 Flow of handling an abnormal RMON performance event..............................................................5-23Figure 5-8 Flow of handling orderwire faults....................................................................................................5-25Figure 7-1 CLETOP cassette cleaner...................................................................................................................7-4Figure 7-2 Dragging the fiber tip slightly on one cleaning area...........................................................................7-4Figure 7-3 Dragging the fiber tip slightly on the other cleaning area..................................................................7-5Figure 7-4 Cleaning the fiber with the lens tissue ...............................................................................................7-6Figure 7-5 Inloop................................................................................................................................................7-17Figure 7-6 Outloop.............................................................................................................................................7-17Figure 7-7 Inloop................................................................................................................................................7-18Figure 7-8 Outloop.............................................................................................................................................7-19Figure 7-9 Inloop................................................................................................................................................7-20Figure 7-10 Service trail.....................................................................................................................................7-21Figure 7-11 PRBS test in the tributary direction................................................................................................7-23Figure 7-12 PRBS test in the cross-connect direction........................................................................................7-23

OptiX RTN 605Maintenance Guide Figures


xiii

Tables

Table 4-1 Description of the main procedure of emergency maintenance...........................................................4-4Table 4-2 Sheet for on-site operations..................................................................................................................4-4Table 4-3 Procedure of on-site fault handling......................................................................................................4-7Table 5-1 Flow description...................................................................................................................................5-4Table 5-2 Flow description...................................................................................................................................5-6Table 5-3 Procedure of on-site fault handling......................................................................................................5-8Table 5-4 Causes of radio link faults..................................................................................................................5-10Table 5-5 Flow description.................................................................................................................................5-14Table 5-6 Flow description.................................................................................................................................5-19Table 5-7 Flow description.................................................................................................................................5-22Table 5-8 Flow description.................................................................................................................................5-23Table 5-9 Flow description.................................................................................................................................5-26Table A-1 Alarm list............................................................................................................................................A-2Table B-1 Important abnormal events.................................................................................................................B-2Table C-1 Microwave power performance events...............................................................................................C-2Table C-2 FEC performance events....................................................................................................................C-3Table C-3 Performance events regarding radio link bit errors............................................................................C-3Table C-4 ATPC performance events..................................................................................................................C-4Table C-5 AM performance events.....................................................................................................................C-4Table C-6 Performance events regarding board temperature..............................................................................C-4Table D-1 List of RMON alarm entries...............................................................................................................D-2Table D-2 List of RMON performance entries....................................................................................................D-2Table E-1 Setting of the bit error alarm threshold...............................................................................................E-4Table F-1 Board performance event management function.................................................................................F-2Table G-1 Suppression relationship between intra-board alarms........................................................................G-1Table G-2 Suppression relationship between inter-board alarms........................................................................G-1

OptiX RTN 605Maintenance Guide Tables


xv

1 Safety Precautions

1.1 General Safety PrecautionsThe general safety precautions include parts of the safety precautions. Read and follow thesesafety precautions before installing, operating, and maintaining the equipment. This topic alsoprovides guidelines on how to select the appropriate measuring instruments and test devices.

Specific Safety PrecautionsBefore installing, operating, and maintaining the equipment, read through the instructions andprecautions carefully to minimize the possibility of accidents. The Danger, Caution, Warning,and Note items in this document do not cover all the safety precautions that must be followed.They are only parts of the safety precautions as a whole.

Symbols

DANGERIndicates a hazard with a high level of risk that, if not avoided, could result in death or seriousinjury.

WARNINGIndicates a hazard with a medium or low level of risk that, if not avoided, could result in minoror moderate injury.

OptiX RTN 605Maintenance Guide 1 Safety Precautions


1-1

CAUTIONIndicates a potentially hazardous situation that, if not avoided, could cause equipment damage,data loss, performance degradation, or unexpected results.

NOTE

Provides additional information to emphasize or supplement important points of the main text.

Local Rules and Regulations

When operating the equipment, you must obey the local rules and regulations. The safetyprecautions provided in this document are supplementary and should be in compliance with thelocal safety regulations.

Basic Requirements for Installation

The installation and maintenance personnel of Huawei equipment must receive strict trainingand be familiar with the proper operation methods and safety precautions before any operation.

l Only the qualified and skilled personnel are allowed to install, operate, and maintain theequipment.

l Only the certified professionals are allowed to remove the safety facilities, and totroubleshoot and maintain the equipment.

l Any replacement or change of the equipment or parts of the equipment (including thesoftware) must be performed by the certified or authorized personnel of Huawei.

l Any fault or error that may cause a safety problem must be reported immediately to theperson in charge.

Grounding Requirements

The grounding requirements are applicable to the equipment that needs to be grounded.

l When installing the equipment, always connect the grounding facilities first. Whenremoving the equipment, always disconnect the grounding facilities last.

l Do not damage the grounding conductor.

l Do not operate the equipment in the absence of a suitably installed grounding conductor.

l The equipment should be connected to the protection ground permanently. Before operatingthe equipment, check the electrical connections of the equipment, and ensure that theequipment is properly grounded.

Human Safetyl Do not operate the equipment and cables in the case of lightning.

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

l To prevent laser radiation from injuring your eyes, do not look at the optical port directly.

1 Safety PrecautionsOptiX RTN 605

Maintenance Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

l Before operating the equipment, put on the electrostatic discharge (ESD) work uniforms,wear ESD gloves or an ESD wrist strap, and take off metallic articles, such as watch,bracelet, and ring, to prevent electric stock or injury of the human body.

l In the case of fire, keep away from the building or the area where the equipment is locatedand press the fire alarm system or dial the phone number for a fire call. In this case, do notenter the building which is on fire.

Equipment Safetyl Before operation, install the equipment firmly on the ground or other rigid objects, such as

a wall or a rack.l When the system is operating, ensure that the ventilation hole is not blocked.

l When installing the front panel, use a tool to tighten the screws firmly.

l After installing the equipment, clean up the packing materials.

1.2 Electrical Safety

High Voltage

DANGERl The high-voltage power supply provides the power for the equipment. Direct or indirect

contact of high voltage and mains supply through damp objects may result in fatal danger.l Non-standard and improper high-voltage operations may result in certain accidents such as

fire or electric shock.

l The personnel who perform high-voltage operations must be certified for high-voltage andAC operations.

l The AC cables must be bridged and routed according to the local rules and regulations.

l When operating AC power supply facilities, obey the local rules and regulations.

l When performing high-voltage and AC operations, use special tools rather than generaltools.

l When performing operations in a damp environment, ensure that the equipment is keptaway from water. Switch off the power supply immediately if you find any water in therack or if the rack is damp.

Thunderstorm

DANGERDo not perform operations on high voltage, AC power, iron tower, or backstay in stormy weatherconditions.



1-3

Power Cable

CAUTIONDo not install or remove the power cable with the power on. Transient contact between the coreof the power cable and the conductor may generate electric arc or spark, which may cause fireor injury to the eye.

l Before installing or removing the power cable, switch off the power supply.

l Before connecting the power cable, ensure that the power cable and label conform to therequirements for the installation.

Fuse

CAUTIONIf the fuse on the equipment blows, replace the fuse with a fuse of the same type and specificationsto ensure safe operation of the equipment.

Electrostatic Discharge

CAUTIONThe static electricity generated by the human body may damage the electrostatic sensitivecomponents on the board, such as the large-scale integrated circuit (LSI).

l The human body generates a static electromagnetic field in the following situations: movingof the human body, friction of the clothes, friction between shoes and the ground, andholding ordinary plastic in hand. The static electromagnetic field will remain within thehuman body for a long time.

l Before operating the equipment, parts, circuit boards, or ASICs, wear an ESD wrist strapthat is properly grounded. The ESD wrist strap can prevent the electrostatic-sensitivecomponents from being damaged by the static electricity in the human body.

Figure 1-1 shows the method of wearing an ESD wrist strap.


Maintenance Guide


Issue 03 (2010-05-30)

Figure 1-1 Wearing an ESD wrist strap

1.3 Flammable Air Environment

DANGERDo not place or operate the equipment in an environment where flammable gas, explosive gas,or smog exists.

Operations on any electronic device in an environment where explosive gas exists may causeextreme risks.

1.4 Radiation

Electromagnetic Exposure

DANGERDanger indicates a hazard that, if not avoided, will result in death or serious injury.

WARNINGWarning indicates a hazard that, if not avoided, could result in moderate or serious injury.



1-5

CAUTIONCaution indicates a hazard that, if not avoided, could result in minor or moderate injury.

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.

Forbidden AreaThe following requirements should be met:

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.5 Working at Heights

CAUTIONWhen 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 The operating machines and tools should be carried and handled safely to prevent themfrom falling down.

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

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 areintact.

Weight Lifting

CAUTIONDo not enter the areas under the jib arm and the goods in suspension when lifting weight.


Maintenance Guide


Issue 03 (2010-05-30)

l Ensure that the operators have completed the related training and have been certified.

l Check the weight lifting tools and ensure that they are intact.

l Lift the weight only when the weight lifting tools are firmly fixed onto the weight-bearingobject or the wall.

l Use a concise command to prevent any incorrect operation.

l Ensure that the angle between the two cables is less than or equal to 90 degrees during thelifting, as shown in Figure 1-2.

Figure 1-2 Weight lifting

Using the LadderChecking the Ladder

l Before using the ladder, check and ensure that the ladder is intact.

l Before using the ladder, check the maximum weight that the ladder can support. Overweighton the ladder is strictly prohibited.

Placing the Ladder

A slant angle of 75 degrees is recommended. The slant can be measured with the angle squareor with arms, as shown in Figure 1-3. When a ladder is used, the wide part of the ladder shouldstand on the ground. Otherwise, take certain protective measures on the base part of the ladderto prevent against sliding. Place the ladder on a rigid ground.



1-7

Figure 1-3 Schematic diagram of slanting a ladder

When climbing the ladder, note the following points:

l Ensure that the gravity center of your body does not deviate from the ladder edge.

l To lessen the danger and ensure the safety, keep your balance on the ladder before anyoperation.

l Do not climb higher than the forth highest step of the ladder.

If you intend to climb to the top, the length of the ladder should be at least one meter higher thanthe eave, as shown in Figure 1-4.

Figure 1-4 Schematic diagram of the ladder one meter higher than the eave


Maintenance Guide


Issue 03 (2010-05-30)

1.6 Mechanical Safety

Drilling Holes

CAUTIONDo not drill holes on the cabinet without prior permission. Improper drilling may cause damageto the internal cables and the EMC function of the cabinet. Metallic scraps produced by thedrilling may fall into the cabinet and cause short circuits of the circuit boards.

l Before drilling a hole on the cabinet, remove the cables inside the cabinet.

l During the drilling, ensure that your eyes are protected properly. The flying metallic scrapsmay cause injury to your eyes.

l Before drilling a hole on the cabinet, wear the protection gloves.

l Take measures to prevent the metallic scraps from falling into the cabinet. After the drilling,clean up the metallic scraps.

Sharp Objects

CAUTIONWhen handling the equipment by hands, wear the protection gloves to avoid injury by sharpobjects.

Fansl When replacing components, ensure that no objects such as components, screws, and tools

fall into a fan that is running, to prevent damage to the fan or equipment.l When replacing the equipment close to a fan, do not put a finger or a board into a fan that

is running before the fan is switched off and stops running, to prevent injury to your handsor damage to the equipment.

Handling Heavy ObjectsWhen handling heavy objects, wear the protection gloves to prevent injury to your hands.



1-9

CAUTIONl When handling heavy objects, ensure that the weight bearing measures are taken to prevent

you from being pressed or sprained.l When taking the chassis out from the cabinet, draw attention to the equipment that is unstable

or heavy on the cabinet, to prevent any pressing or smashing injury.

l When handling a chassis, generally, two persons rather than one person are required tohandle a heavy chassis. When handling a chassis, keep your back straight and move gentlyto prevent you from being sprained.

l When moving or lifting a chassis, hold the handle or bottom of the chassis rather than thehandle of a module (such as a power supply module, a fan module, or a board) that hasbeen installed inside the chassis.

1.7 Other Precautions

Removing and Inserting Boards

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

l Insert the board along the guiding slot.

l The contact of board circuits is not allowed to avoid short circuits or scratches.

l Do not touch the circuit, components, connectors, or routing channels of the board toprevent damage caused by electrostatic discharge of the human body to the electrostatic-sensitive components.

Binding Signal Cables

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

Routing Cables

In the case of extremely low temperature, heavy shock or vibration may damage the externalplastic coatings of the cables. The following requirements should be observed to ensure safeimplementation:

l All the cables can be routed only when the ambient temperature is higher than zero degrees.


Maintenance Guide


Issue 03 (2010-05-30)

l If the cables are stored in a place where the ambient temperature is lower than zero degrees,you must transfer them to a place where the ambient temperature is room temperature atleast 24 hours before the operation.

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.

IF Cables

WARNINGBefore installing or removing an IF cable, you must turn off the power switch of the IF board.



1-11

2 Guides to High-Risk Operations

About This Chapter

This topic describes the operations that easily cause human body injuries and equipment damagein the process of commissioning and maintenance.

2.1 Operation Guide to a Toggle Lever SwitchThe ODU-PWR switch is a toggle lever switch. When you turn on or turn off the toggle leverswitch, perform the operations in strict compliance with the guidelines. Otherwise, the IDUboard may be damaged.

2.2 Operation Guide to IF JumpersBefore removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IDU or the ODU may be damaged.

2.3 Operation Guide to IF CablesBefore removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IF board or the ODU may be damaged.

OptiX RTN 605Maintenance Guide 2 Guides to High-Risk Operations


2-1

2.1 Operation Guide to a Toggle Lever SwitchThe ODU-PWR switch is a toggle lever switch. When you turn on or turn off the toggle leverswitch, perform the operations in strict compliance with the guidelines. Otherwise, the IDUboard may be damaged.

Position and Description of the Toggle Lever Switch

The toggle lever switch resides on the IF board and controls the power that is fed to the ODU,as shown in Figure 2-1.

Figure 2-1 Toggle lever switch

O:OFF

I:ON

Turning On the Toggle Lever Switch

1. Pull the toggle lever switch out slightly.2. Turn it to the left.

2 Guides to High-Risk OperationsOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

3. Release the toggle lever switch.

Turning Off the Toggle Lever Switch

1. Pull the toggle lever switch out slightly.2. Turn it to the right.3. Release the toggle lever switch.

2.2 Operation Guide to IF JumpersBefore removing or installing an IF jumper, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IDU or the ODU may be damaged.

Procedure

Step 1 Turn off the ODU power switch on the IDU. For details, see 2.1 Operation Guide to a ToggleLever Switch.



2-3

1 2

DANGERDo not remove any IF jumper before the ODU is powered off!

Step 2 Remove or install an IF jumper.

----End

2.3 Operation Guide to IF CablesBefore removing or installing an IF cable, turn off the ODU-PWR switch. Otherwise, humanbody injuries may be caused, and the IF board or the ODU may be damaged.

Procedure

Step 1 Turn off the ODU power switch on the IDU. For details, see 2.1 Operation Guide to a ToggleLever Switch.

2 Guides to High-Risk OperationsOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

1 21

DANGERDo not remove any IF cable before the ODU is powered off!

Step 2 Install or remove an IF cable.

----End



2-5

3 Routine Maintenance

About This Chapter

The aim of routine maintenance is to detect and rectify latent faults in time before the equipmentbecomes faulty and services are affected.

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into the routine maintenance items carried out throughthe network management system (NMS), field maintenance items for indoor equipment, andfield maintenance items for outdoor equipment.

3.2 Guidelines for Routine Maintenance ItemsThis topic describes the guidelines for each routine maintenance item.

OptiX RTN 605Maintenance Guide 3 Routine Maintenance


3-1

3.1 Routine Maintenance ItemsRoutine maintenance items are classified into the routine maintenance items carried out throughthe network management system (NMS), field maintenance items for indoor equipment, andfield maintenance items for outdoor equipment.

Routine Maintenance Items Carried Out Through the NMSMaintenance Item Recomm

endedCycle

Remarks

3.2.1 Checking the Status of NEs Every day -

3.2.2 Browsing the Current Alarms Every day -

3.2.3 Browsing the History Alarms Everyweek

-

3.2.4 Browsing the Abnormal Events Everyweek

-

3.2.5 Browsing the CurrentPerformance

Everyweek

-

3.2.6 Browsing the HistoryPerformance

Everyweek

-

3.2.7 Browsing the History TransmitPower and Receive Power

Everyweek

-

3.2.8 Testing IF 1+1 Switching Half ayear

Applies to only the equipment that isconfigured in 1+1 protection mode.During the 1+1 protection switchingtime (<500 ms), the protected servicesare interrupted. Hence, it isrecommended that you perform 1+1protection switching when the trafficis light.

Field Maintenance Items for Indoor EquipmentMaintenance Item Recommended Cycle Remarks

3.2.9 Checking theEquipment Room

Every two months -

3 Routine MaintenanceOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

Field Maintenance Items for Outdoor EquipmentMaintenance Item Recommended

CycleRemarks

3.2.10 Checking the ODU Half a year Perform acomplete checkafter a level-8 orhigher-levelhurricane, anearthquake, orother exceptionalcircumstances.

3.2.11 Checking the Hybrid Coupler Half a year

3.2.12 Checking the Antenna Half a year

3.2.13 Checking the IF Cables Half a year

3.2.14 Checking the LOS Condition Half a year

3.2 Guidelines for Routine Maintenance ItemsThis topic describes the guidelines for each routine maintenance item.

3.2.1 Checking the Status of NEsBy checking the NE status periodically, you can detect the abnormal statuses of one or moreNEs in time.

3.2.2 Browsing the Current AlarmsA current alarm refers to an alarm that is not cleared. By browsing the current alarms periodically,you can detect and rectify faults in time.

3.2.3 Browsing the History AlarmsA history alarm is an alarm that is cleared. Periodically browsing and storing the history alarminformation helps in locating and rectifying faults.

3.2.4 Browsing the Abnormal EventsAn abnormal event refers to an exception that arises in the system at a particular time. Bybrowsing the abnormal events periodically, you can find the exceptions that occur in theequipment in time.

3.2.5 Browsing the Current PerformanceThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time. By browsing the currentperformance events periodically, you can learn about the performance change of the equipmentin time. Hence, you can detect the latent hazards in time when the performance of the equipmentstarts to degrade.

3.2.6 Browsing the History PerformanceA history alarm is an alarm that is cleared. By browsing and saving the history performanceevents periodically, you can provide fault locating information for troubleshooting.

3.2.7 Browsing the History Transmit Power and Receive PowerBy browsing the history transmit power and receive power periodically, you can learn about thechange trend of the transmit power and receive power, which provides a reference fortroubleshooting radio links.

3.2.8 Testing IF 1+1 SwitchingBy testing IF 1+1 switching periodically, you can check whether the equipment is normallyswitched over.



3-3

3.2.9 Checking the Equipment RoomPeriodically checking the equipment room not only ensures that the equipment can operatenormally at appropriate temperature and humidity conditions, but also reduces the fault rate, andincreases the service life of the equipment.

3.2.10 Checking the ODUBy checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.

3.2.11 Checking the Hybrid CouplerBy checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybridcoupler in time.

3.2.12 Checking the AntennaBy checking an antenna periodically, you can detect faults and latent hazards of the antenna intime.

3.2.13 Checking the IF CablesBy checking the IF cables periodically, you can detect faults and latent hazards of the IF cablesin time.

3.2.14 Checking the LOS ConditionBy checking the LOS condition of the transmission link periodically, you can detect latent LOSfaults on the transmission link in time.

3.2.1 Checking the Status of NEsBy checking the NE status periodically, you can detect the abnormal statuses of one or moreNEs in time.

PrerequisiteThe NE user must have the authority of NE monitor or higher.

Tools, Instruments, and MaterialsWeb LCT

Procedure

Step 1 In NE List, query Communication Status of an NE. Communication Status needs to beNormal.

Step 2 Check Login Status of an NE. If the Login Status column of an NE is Not Logged In, log into the NE.1. Select an NE, and then click NE Login.

The NE Login dialog box is displayed.2. Enter a user name in User Name and a password in Password.

l The user name is lct by default.

l The password for the user lct is password by default.

NOTE

The user lct has the authority at the system level.

3. Click OK.


Maintenance Guide


Issue 03 (2010-05-30)

After you log in to the NE successfully, Login Status in NE List changes to Logged In.

----End

3.2.2 Browsing the Current AlarmsA current alarm refers to an alarm that is not cleared. By browsing the current alarms periodically,you can detect and rectify faults in time.



Procedure

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

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 2 Browse the displayed alarms.

Step 3 If there are newly generated alarms after the last maintenance, select the newly generated alarms,record the details of these newly generated alarms, and then notify the troubleshooting personnelto clear these alarms in time.For details about how to handle an alarm, refer to A Alarm Reference.

Step 4 Optional: Click Save As.

A text file that lists the current alarms is displayed in the IE system.

NOTE

You can save and archive the text file as required.

----End

3.2.3 Browsing the History AlarmsA history alarm is an alarm that is cleared. Periodically browsing and storing the history alarminformation helps in locating and rectifying faults.



3-5

Prerequisite

The NE user must have the authority of NE monitor or higher.

Tools, Instruments, and Materials

Web LCT

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.

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 history alarm browsing operation was performedto the current time.

Step 5 Browse the filtered history alarms.

Step 6 Click Save As.

A text file that lists the history alarms is displayed in the IE system.

NOTE


----End

3.2.4 Browsing the Abnormal EventsAn abnormal event refers to an exception that arises in the system at a particular time. Bybrowsing the abnormal events periodically, you can find the exceptions that occur in theequipment in time.

Prerequisite



Web LCT

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.


Maintenance Guide


Issue 03 (2010-05-30)

TIP

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

Step 2 Click Filter.The Filter dialog box is displayed.

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

Step 4 Browse the displayed abnormal events.

For details on how to handle an abnormal event, see B Abnormal Event Reference.


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

NOTE


----End

Related InformationAn abnormal event refers to an exception that arises in the system at a particular time rather thanpersists for a period. Being different from alarms, an abnormal event has the occurrence timerather than the clearance time.

3.2.5 Browsing the Current PerformanceThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time. By browsing the currentperformance events periodically, you can learn about the performance change of the equipmentin time. Hence, you can detect the latent hazards in time when the performance of the equipmentstarts to degrade.

Prerequisitel The performance monitoring function of the NE must be enabled. For details about how to

enable the performance monitoring function, see 7.9 Configuring PerformanceMonitoring Status of NEs.

l The NE user must have the authority of NE monitor or higher.


Procedure

Step 1 In the NE Explorer, select the required board, and then choose Performance > CurrentPerformance from the Function Tree.

Step 2 Select All in Monitored Object Filter Condition.

Step 3 Select 15-Minute next to Monitor Period.



3-7

Step 4 Select all the available performance events in Count, and select Consecutive Severely ErroredSecond in Display Options.

Step 5 Click Query.

Step 6 Browse the displayed performance events.In normal cases, no bit error performance events are displayed, and the number of pointerjustification events is less than six per day on each port.

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

Step 8 Click Query.

Step 9 Browse the displayed performance events.Compared with the history records, the gauge indicators, such as board temperature, do notchange drastically.

Step 10 Select 24-Hour next to Monitor Period.

Step 11 Repeat Step 4 to Step 9 to query the current performance events in a period of 24 hours.

----End

3.2.6 Browsing the History PerformanceA history alarm is an alarm that is cleared. By browsing and saving the history performanceevents periodically, you can provide fault locating information for troubleshooting.





Procedure

Step 1 In the NE Explorer, select the requried board, and then choose Performance > HistoryPerformance from the Function Tree.



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 history 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 history performance events.


Maintenance Guide


Issue 03 (2010-05-30)


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

NOTE






NOTE



Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.


----End

3.2.7 Browsing the History Transmit Power and Receive PowerBy browsing the history transmit power and receive power periodically, you can learn about thechange trend of the transmit power and receive power, which provides a reference fortroubleshooting radio links.





Procedure

Step 1 In the NE Explorer, select the required ODU for the history transmit power and receive power,and then choose Configuration > Performance Graph Analyse from the Function Tree.

Step 2 Specify the start time and end time of a time span.The time span starts from the last routing maintenance time to the current time.

Step 3 Set CounterType to 15M.

Step 4 Click Drawing.The history transmit and receive power curve of the ODU in the specified time span is displayed.



3-9

Step 5 Analyze the power curve. If the receive power fading of two adjacent points exceeds 20 dB, butthe weather does not change, contact the troubleshooting engineers.

----End

3.2.8 Testing IF 1+1 SwitchingBy testing IF 1+1 switching periodically, you can check whether the equipment is normallyswitched over.



Precautionsl This task carries out IF 1+1 switching in manual switching mode, which is used for

equipment switching (that is, HSB switching). During the 1+1 protection switching time(< 500 ms), the protected services are interrupted. Hence, it is recommended that youperform IF 1+1 protection switching when the traffic is light.

l Before you perform the switching, ensure that the standby equipment works properly. Ifthe switching fails, contact Huawei engineers for further assistance.

Procedure

Step 1 In the NE Explorer, select the required NE from the Object Tree, and then chooseConfiguration > Link Configuration from the Function Tree.

Step 2 Click the IF 1+1 Protection tab.

Step 3 In Protection Group, select the protection group for IF 1+1 switching.

Step 4 In Slot Mapping Relation, right-click an IF board and choose Manual Switch to from theshortcut menu.

Step 5 Click OK to start the protection switching.

Step 6 Click Query to check the protection switching status.After the switching is completed, Switching Status of Device in Protection Group changes toManual Switching, and the current board functions as the standby board.

Step 7 After the equipment works for a period of time, query the current alarms and performance eventsof the service.There should be no new alarms or bit error performance events.

Step 8 Repeat Step 1 to Step 3.

Step 9 In Slot Mapping Relation, right-click an IF board and choose Clear from the shortcut menu.

Step 10 Click OK to restore the protection switching.

Step 11 Click Query to check the protection switching status.


Maintenance Guide


Issue 03 (2010-05-30)

After the switching is completed, Switching Status of Device in Protection Group changes toAutomatic Switching.

Step 12 After the equipment runs properly for a period of time, query the current alarms and performanceevents.There should be no new alarms or performance events.

----End

3.2.9 Checking the Equipment RoomPeriodically checking the equipment room not only ensures that the equipment can operatenormally at appropriate temperature and humidity conditions, but also reduces the fault rate, andincreases the service life of the equipment.

PrerequisiteNone.


None.

Procedure

Step 1 Record the reading of the thermometer in the equipment room.The normal temperature ranges from -5°C to +50°C

Step 2 Record the reading of the humidity meter in the equipment room.The normal humidity ranges from 5% to 95%.

Step 3 Check whether the equipment room meets the disaster protection requirements.Ensure the following points:

l Certain portable foam fire extinguishers are available in the equipment room and theseextinguishers need to be within their service life.

l No rain leakage or water penetration is found in the equipment room.

l No mice or insects are found in the equipment room.

Step 4 Clean the equipment room.Ensure that the cabinets, equipment shelves, equipment, desks, and floors are clean. Theequipment needs to be tidy.

----End

3.2.10 Checking the ODUBy checking an ODU periodically, you can detect faults and latent hazards of the ODU in time.

PrerequisiteNone.



3-11

Tools, Instruments, and MaterialsNone.

ProcedureStep 1 Ensure that the ODU is located within the protected area of a lightning arrester.

In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under the lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects an area that is located within an angle of 30° underthe lightning arrester.

Step 2 Ensure that the ODU is fixed properly on the antenna.

Step 3 Ensure that the ODU is not damaged.

Step 4 Ensure that the interface between the ODU and the antenna is waterproof.

Step 5 Ensure that the protection grounding cable of the ODU is grounded firmly and reliably.

----End

3.2.11 Checking the Hybrid CouplerBy checking a hybrid coupler periodically, you can detect faults and latent hazards of the hybridcoupler in time.

PrerequisiteNone.


ProcedureStep 1 Ensure that the hybrid coupler is located within the protected area of the lightning arrester.

In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under the lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects the area that is located within an angle of 30°under the lightning arrester.

Step 2 Ensure that the coupler is fixed reliably on the antenna.

Step 3 Ensure that the coupler is not damaged.

Step 4 Ensure that the interface between the coupler and the antenna is waterproof.

Step 5 Ensure that the interface between the coupler and the ODU is waterproof.

----End

3.2.12 Checking the AntennaBy checking an antenna periodically, you can detect faults and latent hazards of the antenna intime.


Maintenance Guide


Issue 03 (2010-05-30)

PrerequisiteNone.


Procedure

Step 1 Ensure that the antenna is located within the protected area of the lightning arrester.In the case of plain areas, a lightning arrester protects an area that is located within an angle of45° under lightning arrester. In the case of mountainous areas and the areas where lightningfrequently occurs, a lightning arrester protects an area that is located within an angle of 30° underthe lightning arrester.

Step 2 Ensure that the antenna is fixed reliably on the mast.

Step 3 Ensure that the antenna radome is not damaged.

Step 4 Ensure that there is no accumulated water in the antenna.

Step 5 Check whether the fastening bolts on the antenna are loose. Check whether the antenna slantsfrom the original position. Ensure that the azimuth angle and the elevation angle of the antennameet the design requirements.

Step 6 In the case of split mounting, ensure that the installation parts (ODU adapter, antenna adapter,and flexible waveguide) are installed firmly, and that the connectors are fastened.

Step 7 Check and ensure that the interface of the feed boom is properly sealed and waterproof.

----End

3.2.13 Checking the IF CablesBy checking the IF cables periodically, you can detect faults and latent hazards of the IF cablesin time.

PrerequisiteNone.


Procedure

Step 1 Check the cables.l No cables are bent or twisted.

l No bare copper wires are found.

l The bending radius of a cable needs to greater than 30 cm.

l The IF cables are bound in accordance with IF Cable Routing and Binding Specificationsspecified in the Installation Reference. The feeder clip or binding strap is not loosen.



3-13

Step 2 Check the cable connectors.l The cable connector needs to be connected reliably to the ODU.

l The cable connector needs to be waterproof.

Step 3 Check the grounding of the cables.l The grounding clip needs to be waterproof.

l The grounding cable needs to be routed from top downwards. The angle between thegrounding cable and an IF cable needs to be not more than 15 degrees.

----End

3.2.14 Checking the LOS ConditionBy checking the LOS condition of the transmission link periodically, you can detect latent LOSfaults on the transmission link in time.

PrerequisiteNone.

Tools, Instruments, and MaterialsTelescope

Procedure

Step 1 Use the telescope to search for the antenna at the opposite end from a location nearby the localantenna. No buildings or maintains exist on the transmission link, which may block the LOS.

Step 2 Check whether the spanning tree in the transmission path is blocked.

Step 3 Check whether any new buildings exist in the transmission path.

----End


Maintenance Guide


Issue 03 (2010-05-30)

4 Emergency Maintenance

About This Chapter

Emergency maintenance is performed when emergencies occur or possible emergencies owingto natural factors may occur during the operation of the equipment.

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency situation is where the microwave servicesare interrupted.

4.2 Purposes of Emergence MaintenanceEmergency maintenance is performed to restore the normal operation of a system or a devicerapidly. This is different from troubleshooting, which helps to locate and rectify the faults.

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

OptiX RTN 605Maintenance Guide 4 Emergency Maintenance


4-1

4.1 Definition of EmergencyIn the case of the microwave equipment, an emergency situation is where the microwave servicesare interrupted.

4.2 Purposes of Emergence MaintenanceEmergency maintenance is performed to restore the normal operation of a system or a devicerapidly. This is different from troubleshooting, which helps to locate and rectify the faults.

4.3 Procedure of 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 our 24-hour technical support center at400-830-2118, and the customers in areas outside China can contact the local Huawei offices.

4 Emergency MaintenanceOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

Main Procedure of Emergency Maintenance

Figure 4-1 Main procedure of emergency maintenance

Start

Is there anincorrect operation? Cancel the operation

Is there any backuptransmission resource?

Switch the service tothe backup resource

Is the power down Contact the powersupply engineer

Troubleshoot theswitching failure

Proceed to the nextstep

Is the servicerestored?

Is the service restored? Contact Huaweiengineers

Check thetroubleshooting result

End

Is there any alarm onthe NE? Clear the alarm

1

2

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Yes

Yes

No

Yes Troubleshoot theinterconnection fault

No

No

3

Yes

No

4Is the Ethernet

service interrupted

5

Is the serviceconfigured with

protection

Is theinterconnection

faulty?

Troubleshoot theEthernet service fault

Locate the fault byperforming loopback

operations section by section

6



4-3

Table 4-1 Description of the main procedure of emergency maintenance

CommentNo.

Description

1 The common incorrect operations are as follows:l Modifying the data configurations

l Performing loopback operations

l Muting the ODU

l Changing cables

l Loading software

2 Check the notice issued by associated departments, and check whether thereare any external factors that may cause service faults, such as faults in thepower supply, environment, and terminal equipment (such as switchingdevices).

3 See 7.3.1 Checking the NE Status and 7.3.3 Browsing the CurrentAlarms.

4 The following alarms can be cleared through the NM:DBMS_ERROR,LOOP_ALM, MSSW_DIFFERENT, NESF_LOST,NESTATE_INSTALL, andRADIO_MUTE.

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

6 After the fault is handled, 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 4-2 shows the sheetfor on-site operations.

Table 4-2 Sheet for on-site operations

Maintained on maintained by

Actual Step Step in the WholeProcedure

Handling Result Remarks


Maintenance Guide


Issue 03 (2010-05-30)

Procedure of On-Site Fault Handling



4-5

Figure 4-2 Procedure of on-site fault handling

No

YesClear the alarm

YesClear the alarm

No

5 YesClear the alarm

No

YesClear the alarm

End


Servicerestored?

Yes

No

Repair or replacethe equipment

No Troubleshoot thepower input

Yes

1No

No

YesClear the alarm

7

Equipment alarm?

Radio link alarm?

R_LOS/R_LOF/R_LOC

alarm?

Tributary alarm?

Start

Browse alarmslocally by using the

Web LCT

PDHinterconnection

alarm?



2

3

4

No

Yes 8

No

Clear thealarm

6

YesObviousequipmentdamage?

Is the PWRindicator on the

IDU on?

Ethernetservice fault?


Maintenance Guide


Issue 03 (2010-05-30)

Table 4-3 Procedure of on-site fault handling

CommentNo.

Description

1 The handling procedure is as follows:1. Check whether the air circuit breaker for the input power is off. If the air

circuit breaker is automatically turned off, identify the cause (such as shortcircuits or insufficient fuse capacity), and handle the fault accordingly.

2. Check the power cables, especially the power connectors, and replace thepower cables or re-make power connectors if required.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contact thepower engineers and handle the fault.

NOTEFor detailed specifications of the fuse capacity and input power, refer to the topic of"Powering On the Equipment" in the Commissioning Guide.

2 The handling procedure is as follows:1. Refer to the Commissioning Guide and Connecting the Web LCT to the

IDU.2. Refer to the Configuration Guide and Creating NEs by Using the Search

Method.3. Refer to Commissioning Guide, and Checking Alarms.NOTE

If you fail to log in to a created NE, ensure that the operations you performed are correct,and then identify and rectify the fault according to the indicators of the IDU. For detailsabout the indicators, refer to the IDU Hardware Description.

3 Pay special attention to the following alarms:l HARD_BAD

l POWER_ALM

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

l IF_CABLE_OPEN

l VOLT_LOS

4 Pay special attention to the following alarms:l MW_LIM

l MW_LOF

l MW_BER_EXC



4-7

CommentNo.

Description

5 The R_LOS, R_LOF, and R_LOC alarms indicate that the microwaveframes received by the IF unit are abnormal.

6 Pay special attention to the following alarms:l T_ALOS

l E1_LOC

7 See 5.4 Troubleshooting the Interconnection with the PDH Equipment.


Maintenance Guide


Issue 03 (2010-05-30)

5 Troubleshooting

About This Chapter

This guide describes the general troubleshooting procedures for the OptiX RTN 605 and providestroubleshooting methods for common faults.

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomenon. 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.

5.2 Troubleshooting Service InterruptionThe service interruption fault indicates the service transmission failure due to an equipment faultor a link fault.

5.3 Troubleshooting Radio LinksWhen an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performancedegradation of a radio link, there is a radio link fault.

5.4 Troubleshooting the Interconnection with the PDH EquipmentIn the case that the OptiX RTN equipment is interconnected with the PDH equipment, if thePDH service cannot be transmitted between the equipment sets, there is an interconnection fault.

5.5 Troubleshooting Ethernet Service FaultsEthernet services can be transmitted over Hybrid radio or Mini IP radio. An Ethernet servicefault may refer to Ethernet service interruption or Ethernet service deterioration.

5.6 Troubleshooting Orderwire FaultsIf orderwire calls cannot get through when services are normal, there is an orderwire fault.

OptiX RTN 605Maintenance Guide 5 Troubleshooting


5-1

5.1 General Troubleshooting ProcedureWhen handling a fault, make a detailed record of the fault phenomenon. 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.

5 TroubleshootingOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

Figure 5-1 General fault locating procedures

Start

Record the fault phenomenon

Analyze fault causes and locatethe fault

Is the fault cleared?

Report to Huawei

Make a solution together

Attempt to clear the fault

Is the service restored?

Observe the operating

Is the fault cleared?

Fill in the fault handling report

End

Other handling procedures

1

3

4

No

Yes

Yes

Yes

No

No

No

Caused by external factors?2

Yes



5-3

Table 5-1 Flow description

Note Description

1 When recording the fault phenomenon, makea true and detailed record of the entire processof the fault. Record the exact time when thefault occurs, and the operations performedbefore and after the fault occurs. Save thealarms, performance events, and otherimportant information.

2 Check the notice issued by associateddepartments, and check whether there are anyexternal factors that may cause service faults,such as faults in the power supply,environment, and terminal equipment (suchas switching devices).

3 If the fault is caused by the equipment, referto 5.2 Troubleshooting ServiceInterruption.

4 The customers in China can contact our 24-hour technical support center at400-830-2118, and the customers in areasoutside China can contact the local Huaweioffices.

5.2 Troubleshooting Service InterruptionThe service interruption fault indicates the service transmission failure due to an equipment faultor a link fault.

Fault Causesl The operation is improper.

If the configuration data changes, the loopback occurs, or the cable is replaced, the servicesmay be interrupted.

l The transmission NE or link is faulty.

l The interconnection is improper.

If the transmission equipment functions properly and the connection is proper, checkwhether the interconnection between the transmission equipment is proper and whether theswitching equipment is faulty.

Fault Locating Methods1. Check whether an abnormal operation causes the service interruption by performing a

loopback on the previous operations.


Maintenance Guide


Issue 03 (2010-05-30)

2. Query alarms on the centralized NMS or the NMS on the site, and then locate the faultbased on the alarm analysis.

3. If the fault cannot be located through the alarm analysis method, locate the fault by loopbacksection by section and part replacement.

CAUTIONIf the fault cannot be rectified immediately, focus on the service recovery. You can recover theservices by adjusting the service route or performing forced switching as soon as possible.

Fault Locating Procedure

Figure 5-2 Flow of handling a service interruption

End

Service interruptedby external causes?

Maloperation

NE accesssuccessful and alarm

cleared?

Rectify the fault on site

Query NE status andalarm by using the

NMS

Contact relateddepartments to

handle the problem

Cancel the operation

Start

Handle the alarm

Go to the next step Servicerestored?

Yes

No

1

2

3

4

No

Yes

Yes

Yes

No

No



5-5


Note Description

1 The common abnormal operations are as follows:l Modifying the data configuration

l Loopback

l Muting the ODU

l Replacing the cable.

l Loading the software

2 Check the notice issued by associated departments, and check whether thereare any external factors that may cause service faults, such as faults in thepower supply, environment, and terminal equipment (such as switchingdevices).

3 See 3.2.1 Checking the Status of NEs and 3.2.2 Browsing the CurrentAlarms.

4 The alarms that can be cleared through the operations on the NMS are asfollows: DBMS_ERROR, LOOP_ALM, MSSW_DIFFERENT,NESF_LOST, NESTATE_INSTALL, and RADIO_MUTE.


Maintenance Guide


Issue 03 (2010-05-30)

Figure 5-3 Procedure of on-site fault handling

No

YesClear the alarm

YesClear the alarm

No

5 YesClear the alarm

No

YesClear the alarm

End


Servicerestored?

Yes

No

Repair or replacethe equipment

No Troubleshoot thepower input

Yes

1No

No

YesClear the alarm

7

Equipment alarm?

Radio link alarm?

R_LOS/R_LOF/R_LOC

alarm?

Tributary alarm?

Start

Browse alarmslocally by using the

Web LCT

PDHinterconnection

alarm?



2

3

4

No

Yes 8

No

Clear thealarm

6

YesObviousequipmentdamage?

Is the PWRindicator on the

IDU on?

Ethernetservice fault?



5-7

Table 5-3 Procedure of on-site fault handling

CommentNo.

Description

1 The handling procedure is as follows:1. Check whether the air circuit breaker for the input power is off. If the air

circuit breaker is automatically turned off, identify the cause (such as shortcircuits or insufficient fuse capacity), and handle the fault accordingly.

2. Check the power cables, especially the power connectors, and replace thepower cables or re-make power connectors if required.

3. Check the voltage and polarization of the input power. If the voltage orpolarization of the input power does not meet the requirements, contact thepower engineers and handle the fault.

NOTEFor detailed specifications of the fuse capacity and input power, refer to the topic of"Powering On the Equipment" in the Commissioning Guide.

2 The handling procedure is as follows:1. Refer to the Commissioning Guide and Connecting the Web LCT to the

IDU.2. Refer to the Configuration Guide and Creating NEs by Using the Search

Method.3. Refer to Commissioning Guide, and Checking Alarms.NOTE

If you fail to log in to a created NE, ensure that the operations you performed are correct,and then identify and rectify the fault according to the indicators of the IDU. For detailsabout the indicators, refer to the IDU Hardware Description.

3 Pay special attention to the following alarms:l HARD_BAD

l POWER_ALM

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

l IF_CABLE_OPEN

l VOLT_LOS

4 Pay special attention to the following alarms:l MW_LIM

l MW_LOF

l MW_BER_EXC


Maintenance Guide


Issue 03 (2010-05-30)

CommentNo.

Description

5 The R_LOS, R_LOF, and R_LOC alarms indicate that the microwaveframes received by the IF unit are abnormal.

6 Pay special attention to the following alarms:l T_ALOS

l E1_LOC

7 See 5.4 Troubleshooting the Interconnection with the PDH Equipment.

Experience and Summary

The maintenance personnel need to perform the regular maintenance to reduce the equipmentfaulty rate. Thus, equipment faults can be discovered and rectified before they affect the services.

5.3 Troubleshooting Radio LinksWhen an NE reports MW_LOF or MW_FEC_UNCOR due to failure or performancedegradation of a radio link, there is a radio link fault.

The key to locating a radio link fault is to check whether the transmit power and the receivepower are abnormal, and to check whether there is an external interference.

In the following two cases, the transmit power is abnormal. The first case is that the transmitpower exceeds the range that the ODU supports. The second case is that the difference betweenthe transmit power and the set value is more than 2 dB when the ATPC is disabled. The relevantalarms and performance events are as follows:

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l TSL_CUR

l TSL_MAX

l TSL_MIN

l TSL_AVG

NOTE

For a detailed description of the range of the transmit power, refer to the Product Description.

In the following two cases, the RSL is abnormal. The first case is that the receive power is lowerthan the normal value (Normal value = Planned value - 3 dB). The second case is that the receivepower is lower than the receiver sensitivity or higher than the free space receive power due tofading. The relevant alarms and performance events are as follows:

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RSL_CUR



5-9

l RSL_MAX

l RSL_MIN

l RSL_AVG

NOTE

For a detailed description of the receiver sensitivity, refer to the Product Description.

Generally, external interference is classified into co-channel interference and adjacent channelinterference.

l Co-channel interference is crosstalk from two different radio transmitters reusing the samefrequency channel. Therefore, the entire spectrum may be impaired.

l Adjacent channel interference is signal impairment to one frequency due to presence ofanother signal on a nearby frequency. Therefore, a part of the spectrum is impaired.

Because interference is closely related to the frequency in use, the transmission over a radio linkmay be faulty in one direction only.

Fault Causes

Table 5-4 Causes of radio link faults

Fault Common Fault Causes

The transmit power is abnormal. The ODU is faulty.

The receive power is always lower than thenormal value.

l The antenna direction is not properlyadjusted.

l The antennas have different polarizationdirections.

l There is a mountain or building in thetransmit direction.

l The antenna is faulty or the connectionbetween the antenna and the ODU isabnormal (for example, the waveguideinterface of the ODU is wet or the flexiblewaveguide is not connected properly).

l The ODU is faulty.

The receive power is abnormal due to slowup-fading.

There is an external interference.

The receive power is abnormal due to slowdown-fading.

The fading margin is not sufficient.

The receive power is abnormal due to fastfading.

The multipath fading is fast.

The receive power is normal, but the radiolink is faulty in one direction.

There is external interference.


Maintenance Guide


Issue 03 (2010-05-30)

NOTE

Depending on the received level, there is up fading and down fading.

l Up fading

The received level is higher than the value after free space fading. The difference can be 10-odd decibels.

l Down fading

The received level is lower than the value after free space fading. The difference can be tens of decibels.

Depending on the fading time, there is fast fading and slow fading.

l Fast fading

The fading duration time ranges from several milliseconds to tens of seconds.

l Slow fading

The fading duration time ranges from tens of seconds to several hours.

Because slow down fading and fast fading are imposed by the propagation paths, the radio link may be faultyin both directions.

Fault Locating Methods1. Check whether the ODU is mute, powered off, or looped back. Check whether the data

configuration is correct.2. Check whether the ODU and the IF board are faulty.3. If the transmit power is abnormal, replace the ODU.4. If the receive power is abnormal, check out the possible causes based on the fading type.5. If the receive power is normal but faults occur on the radio link intermittently, check

whether there is interference before you proceed.6. If the transmit/receive power is normal, perform loopback operations.

NOTE

The OptiX RTN 605 is the integrated equipment. An IF board is a logical board for the OptiX RTN 605. In fact,replacing the IF board is equivalent to replacing the OptiX RTN 605 in this topic.



5-11

Fault Locating Procedures


Maintenance Guide


Issue 03 (2010-05-30)

Figure 5-4 Flow of handling radio link faults

Start

ODU or IF relatedalarm?

Yes

Clear the alarm

No

Proceed tothe next step

Is the faultrectified?

End

Yes

No

Transmit powernormal?

Yes

No

2

Rectify the fault

Perform loopbackoperations

9

No

Rectify the fault

YesRectify the fault

Slow up fadingcauses abnormal

RSL?

No

Rectify the fault

3

Cancel theoperation

1

4

5

6

Yes

No

Yes

No

Rectify the fault

8Yes

Yes

No

No

Rectify the fault

7Yes

Incorrect operation?

RSL always lowerthan the normal

value?

Slow down fadingcauses abnormal

RSL?

Fast fadingcauses abnormal

RSL?

Radio linkfaulty in onedirection?



5-13


Note Description

1 Handleincorrectoperations.

Check the following points:l Check whether the ODU is powered off.

l Check whether the ODU is muted.

l Check whether the IF board is looped back.

l Check whether the data configuration at the transmit end is the same as thedata configuration at the receive end.

l Check whether the data configuration matches the type of the ODU andthe hybrid coupler.

2 Handleequipmentfaults.

Pay special attention to:l VOLT_LOS

l CONFIG_NOSUPPORT

l HARD_BAD

l TEMP_ALARM

l IF_INPWR_ABN

l RADIO_MUTE

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l RADIO_RSL_HIGH

l IF_CABLE_OPEN

3 Handle theexception oftransmitpower.

6.2 Replacing an ODU


Maintenance Guide


Issue 03 (2010-05-30)

Note Description

4 Handle theexceptionthat thereceivepower issmaller thanthe normalvalue.

Follow the steps below:1. If the receive power decreases sharply and does not recover, check the

installation of the antenna. Ensure that the azimuth angle of the antennameets the requirement.Check whether the antenna is aligned properly. Check whether the receivedsignal is from the main lobe.If the antenna direction is not aligned properly, adjust the antenna in a widerange.

2. If the difference between the receive power of the main ODU and standbyODU at one end of the 1+1 HSB radio link is beyond the range from 0 dBto 9 dB (in the case of an unbalanced hybrid coupler) or beyond the rangefrom 0 dB to 5 dB (in the case of a balanced hybrid coupler), perform 1+1HSB switching or replace the ODUs and hybrid coupler to identify thefaulty part.

3. If the difference between the RSL at the receive end and transmit end islarger than 10 dB, replace the ODUs to check whether the main or standbyODU is faulty.

4. Check whether the setting of the polarization direction of the antenna iscorrect. Rectify the wrong polarization direction.

5. Replace the ODUs and hybrid coupler to identify the faulty part.6. Check whether there is a mountain or building in the transmit direction.7. Check whether the gains of the antennas at the receive and transmit ends

comply with the specifications. Replace the antenna whose gain does notcomply with the specifications.

5 Handle theup slowfading fault.

Follow the steps below:1. Check whether there is co-channel interference.

1. Mute the opposite ODU.2. Check the RSL at the local end. If the RSL exceeds -90 dBm, you can

infer that there is co-channel interference that may impair the long-termavailability and performance of the system.

2. Use a spectrum analyzer to analyze the interference source.3. Contact the spectrum management department to clear the interference

spectrum or change plans to reduce the interference.

6 Handle thedown slowfading fault.

Contact the network planning department to make the following changes:l Increase the installation height of the antenna.

l Reduce the transmission distance.

l Increase the antenna gain.

l Increase the transmit power.



5-15

Note Description

7 Handle thefast fadingfault.

Contact the network planning department to make the following changes:l Adjust the position of the antenna to block the reflected wave or make the

reflection point fall on the ground that has a small reflection coefficient,thus reducing the multipath fading.

l Adjust the RF configuration to make the links in the 1+1 SD configuration.

l For the links in the 1+1 SD configuration, adjust the height differencebetween two antennas to make the receive power of one antenna muchstronger than that of another.

l Increase the fading margin, by replacing the original antennas withantennas of a larger diameter or increasing the transmit power of theoriginal antennas.

8 Handle theinterferencefault.

The handling procedure is as follows:1. Check whether there is co-channel interference.

1. Mute the opposite ODU.2. Check the RSL at the local end. If the RSL exceeds -90 dBm, you can

infer that there is co-channel interference that may impair the long-termavailability and performance of the system.

2. Check whether there is adjacent channel interference.1. Mute the opposite ODU.2. Adjust the RF working mode at the local end and use the minimum

channel spacing.3. Decrease the received frequency at the local end by a half of the channel

spacing.4. Test and record the RSL.5. Increase the received frequency at the local end, with a step length of

0.5 MHz or 1 MHz, and record the RSL accordingly until the receivedfrequency is equal to the original received frequency plus a half of thechannel spacing.

6. Compare the recorded RSLs, and check whether the RSL in a certainspectrum is abnormal if the received frequency is within the permittedrange.

3. Use a spectrum analyzer to analyze the interference source.4. Contact the spectrum management department to clear the interference

spectrum or change plans to reduce the interference.


Maintenance Guide


Issue 03 (2010-05-30)

Note Description

9 Use theloopbackmethod tolocate a fault.

Follow the steps below:1. Perform an inloop on the IF port.

If the fault is not cleared after the loopback, replace the IDU.2. Check whether the IF cable is soggy, broken or pressed. Make the

connector again.3. Check whether the IF cable is soggy, broken, or pressed. If yes, replace

the IF board.4. Replace the ODU.

If the fault is cleared after the replacement, the original ODU is faulty.

Experience and Summaryl During a commissioning process, make sure that the antenna direction is correctly adjusted

to prevent possible incipient faults.l Periodically collect the change data of the transmit power and receive power, and analyze

the change data to remove incipient faults in time.

5.4 Troubleshooting the Interconnection with the PDHEquipment

In the case that the OptiX RTN equipment is interconnected with the PDH equipment, if thePDH service cannot be transmitted between the equipment sets, there is an interconnection fault.

Fault Causesl There is an impedance mismatch between interfaces.

l The equipment is not properly grounded.

l The cable performance degrades.

l The indexes of PDH interfaces do not meet the requirements.

Fault Locating MethodsAnalyze the fault phenomenon and alarms. Check the possible fault causes one by one.



5-17


Figure 5-5 Flow of troubleshooting the interconnection with the PDH equipment

Start

Is there animpedance mismatch?

Yes Modify the interfaceimpedance of the

tributary board

Check the cables

Is in good conditions?No

Yes

Go to the nextstep Is the fault cleared?

End

Yes

No

Is the cable thecoaxial cable?

No

Check the impedance ofthe interfaces

Yes

1

Adjust the cables

Test the indexes ofinterfaces

Do the interfacesmeet standards?

Handle the faults of thelocal equipment

Handle the faults of theinterconnected equipment

Yes

No

4

Check the grounding

2

3

No


Maintenance Guide


Issue 03 (2010-05-30)


Note Description

1 Check whether 7.10 Querying the Impedance of an E1 Channel matchesthe type of the cable.

2 Check the following points:l Check whether all the equipment and the DDF in the equipment room are

jointly grounded.l Check whether the shielding layer of the coaxial cable connector on the

DDF is connected to the protection ground.l Check whether the shielding layers of coaxial cables are grounded in the

same way.NOTE

Disconnect all the signal cables between the interconnecting equipment. Use amultimeter to measure the level between the shielding layers of the coaxial cables at thereceive and transmit ends of the PDH equipment. Also measure the level between theshielding layers of the coaxial cables at the receive and transmit ends of the oppositeequipment. If the potential difference is large (about 0.5 V), the fault may be caused bythe grounding.

3 Check the following points:l Check whether the wires of the cable are correctly connected.

l Check whether the cable is broken or pressed.

l Check whether the cable signal is interfered (for example, when the trunkcable is bound with the power cable, the cable signal is interfered by thepower signal).

NOTEChecking the cables involves checking the cables from the DDF to the client side andchecking the cables from the DDF to the transmission equipment side.

4 Check the following indexes:l Input jitter tolerance

l Permitted input frequency deviation

l Output jitter

l Output frequency deviation

Experience and SummaryGrounding problems are the most common reasons that cause an interconnection failure whenthe OptiX RTN 600 is interconnected with the PDH equipment.

5.5 Troubleshooting Ethernet Service FaultsEthernet services can be transmitted over Hybrid radio or Mini IP radio. An Ethernet servicefault may refer to Ethernet service interruption or Ethernet service deterioration.

The Ethernet service interruption indicates that the Ethernet service is completely interrupted.The Ethernet service degradation indicates that the Ethernet service is abnormal. For example,



5-19

the network access speed is low, the equipment delay is long, the packet loss occurs, or incorrectpackets exist in the received or transmitted data.

Fault Causesl The human factors are as follows:

– An Ethernet port loopback or a transmission line loopback occurs.

– The settings of the parameters of an Ethernet port, such as the port enabling, workingmode, and flow control are different from those of the interconnected equipment.

– The configuration of the encapsulation/mapping or LCAS protocol is different fromthat of the remote equipment.

– The VCTRUNK-bound timeslot is different from that of the remote equipment.

– The service configuration is incorrect.

l The local equipment is faulty.

l The line board is faulty or has bit errors.

l The modulation mode changes because of the degradation of the link performance whenthe AM function is enabled.

l The interconnected equipment is faulty.

l The network cable is faulty.

l The external electromagnetic interference is severe.

Fault Locating Methods1. Rectify the human-caused faults such as a loopback and a data configuration error.2. Locate the fault cause according to the equipment alarm.3. Locate the fault cause according to the RMON performance event and alarm.


Maintenance Guide


Issue 03 (2010-05-30)

Fault Locating Procedure

Figure 5-6 Flow of handling an Ethernet service fault

Clear the alarm

5

No

Yes

Ethernetservice alarm?

Yes Query the port andservice traffic and

analyze the fault causes

No

Yes

Yes Troubleshoot theopposite equipment

No

3

2

Troubleshoot the equipmentby performing loopback

operations section by sectionby replacing boards

Proceed tothe next step


End

Yes

No

No

Start

Incorrect operation?1 Cancel the operation

No

Yes

Clear the alarm

4 YesRelease the loop

Loop formed by theE-LAN service

trails?

Equipmentalarm or line

alarm?

Rectify the fault according tothe flow of handling abnormalRMON performance events

Abnormal RMONperformance

events?

Fault on the oppositeequipment?



5-21


Note Description

1 Check the following points:l Whether a loopback is set for the Ethernet port

l Whether a loopback is set for the transmission line

l Whether the settings of the parameters of an Ethernet port, such as the portenabling, working mode, and flow control are the same as those of theinterconnected equipment

l Whether the configuration of the encapsulation/mapping or LCAS protocolis the same as that of the remote equipment

l Whether the VCTRUNK-bound timeslot is the same as that of the remoteequipment

l Whether the Ethernet protocol and the Ethernet service configuration(especially the attributes of the Ethernet port) are correct.

2 Check the following equipment alarms:l POWER_ALM

l HARD_BAD

l BD_STATUS

l NESF_LOST

l TEMP_ALARM

l RADIO_RSL_HIGH

l RADIO_RSL_LOW

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l IF_INPWR_ABN

Check the following line alarms:l MW_LIM

l MW_LOF

l MW_BER_EXC

l MW_BER_SD

l MW_LIM

l MW_LOF

l MW_RDI

l MW_FEC_UNCOR

3 Check the following alarms:ETH_LOS

4 For RMON performance events, refer to the D RMON Event Reference.


Maintenance Guide


Issue 03 (2010-05-30)

Figure 5-7 Flow of handling an abnormal RMON performance event

Start

Rectify the fault of line biterrors

No

YesIs there any FCS error?

Is there any collisionor fragment?

Yes Check the working modeof the port

Is it a MTU settingproblem?

YesModify the MTU value

No

2

Proceed withthe next step


End

Yes

No

Is there anyPAUSE frame?

3

No

No

Yes Handle the flow controlproblem or increase the

bandwidth

View the statistics groupperformance on an Ethernet port

Is the test passed?

No

Yes

Use a meter to perform the test

Rectify the fault of theinterconnected equipment

Rectify the equipment fault byloopback section by section or

replacing the board

1

4

6

Are broadcast packetsexcessive?

No

Yes Handle the problem onexcessive broadcast

packets

5


Note Description

1 View the statistics group performance on an Ethernet port to understand thereal-time performance statistics data of the Ethernet port.



5-23

Note Description

2 The handling procedure is as follows:l Check the network cable. If the network cable does not meet the

requirements, replace the network cable.l Change the Ethernet port of the access service. If the new port does not

have the RMON performance of an FCS error, it indicates that the hardwareof the original port is faulty. Otherwise, the hardware of the Ethernet porton the opposite equipment is faulty.

3 Check the following points:l Whether the port operating rate of the equipment is the same as that of the

interconnected equipmentl Whether the full-duplex/half-duplex mode of a port on the equipment is

the same as that on the interconnected equipmentl Do not set the auto-negotiation at one end and the full-duplex at the other

end.

4 Check the following points:l Whether the flow control mode of the equipment is the same as that of the

interconnected equipmentl Whether the Ethernet service volume is greater than the configured

VCTRUNK bandwidth

5 Find out of the reason of excessive broadcast packets (such as 7.5.3 SettingLoopback for the Ethernet Port of the RTN 605 1F/2F or improper VBfilter table setting) and solve the problem. If the problem is caused by theopposite equipment, set the threshold of broadcast packet suppression for anEthernet port to reduce broadcast packets.

6 Test the MTU of the network by using a test meter. The maximum framelength that is set for a port should be longer than the MTU of the network.

Experience and Summary

Understand the features, working mode, and configured protocols of interfaces on the Ethernetequipment, which is required to troubleshoot Ethernet faults.

5.6 Troubleshooting Orderwire FaultsIf orderwire calls cannot get through when services are normal, there is an orderwire fault.

Fault Causesl The phone set is incorrectly set.

l The phone line is connected incorrectly.

l The orderwire is incorrectly configured.


Maintenance Guide


Issue 03 (2010-05-30)

NOTEWhen services are transmitted over E1 lines, the orderwire traffic needs to be transmitted in othermeans, for example, through the synchronous data interface or external clock interface.

l The IDU is faulty.

Fault Locating Methodsl Check whether the phone set is correctly set, whether the phone line is correctly connected,

and whether the orderwire is correctly configured.l Replace the possibly faulty IDU to locate the fault.


Figure 5-8 Flow of handling orderwire faults

Start

Is the phonecorrectly set?

No Modify the phone setting

Check the orderwireconfiguration

Is the configurationcorrect?

No

Yes

Go to the nextstep Is the fault cleared?

End

Yes

No

Is the phone linecorrectly connected?

Yes

Check the phone setting

No

1

Modify the configuration

Replace the possibly faultyboard

3

Re-connect the phone line

2

Yes



5-25


Note Description

1 Check the following points:l Check whether the ring current switch "RING" on the phone set is set to

"ON".l Check whether the dialing mode switch is set to "T", that is, the dual tone

multi-frequency mode.l An orderwire phone set should be on-hook when it is not in communication,

and the upper-right red indicator in the front view of the orderwire phoneset should be off.If the red indicator is on, it indicates that the phone set is in the off-hookstate. Press the "TALK" button in front of phone set to hook it up. In certainoccasions the "TALK" button is pressed by the maintenance personnel dueto carelessness. This makes the phone set stay in the off-hook state all thetime and the orderwire call from other NEs cannot get through.

2 Check the following points:l Check whether all orderwire phone numbers in a subnet are of the same

length.l Check whether all orderwire phone numbers in a subnet are unique.

3 Replace the IDU to locate the fault.

Experience and SummaryIt is necessary to periodically check the orderwire phone set.


Maintenance Guide


Issue 03 (2010-05-30)

6 Part Replacement

About This Chapter

Part replacement is a method frequently used to locate faults. The replacement operation varieswith the part types.

6.1 Replacing the IDUDuring the replacement of the IDU 605, the service carried by the IDU 605 is interrupted.

6.2 Replacing an ODUIf the radio link provided by an ODU is not configured with protection and the services on theODU are not configured with protection, replacing the ODU interrupts the services. In addition,the services on the radio link of the other polarization direction are affected if the radio linkprovided by the ODU is configured with XPIC.

6.3 Replacing the IF CableThe IF cable cannot transmit radio services when it is replaced.

OptiX RTN 605Maintenance Guide 6 Part Replacement


6-1

6.1 Replacing the IDUDuring the replacement of the IDU 605, the service carried by the IDU 605 is interrupted.

Prerequisitel The influence of replacing the IDU must be acknowledged.

l The location of the IDU to be replaced must be specified.

l Spare IDUs must be available on site, and the spare parts must be the same as those to bereplaced in version and type.

Tools, Instruments, and Materialsl Screwdriver

l ESD wrist strap

l Web LCT

ContextOptiX RTN 605 1D can be a substitute for OptiX RTN 605 1A/1B, and OptiX RTN 605 2D canbe a substitute for OptiX RTN 605 2B. After replacement, the IDU configuration needs to bechanged.

ProcedureStep 1 Use the Web LCT to query the current alarms of the board.

Step 2 If the OptiX RTN 605 2D/2E/2F is used, be sure to set the ODU-S and ODU-M switches on thefront panel of the IDU to "0".

Step 3 Set the POWER switch on the front panel of the IDU to "0".

Step 4 Turn off the air circuit breaker for the input power of the IDU.

Step 5 Mark and remove all the cables connected to the IDU.

Step 6 Remove the IDU from the cabinet, wall, or desk-mounted rack.

Step 7 Refer to Installation Guide and install the spare IDUs.

Step 8 Re-connect the cables of the IDU as marked earlier.

Step 9 Refer to Commissioning Guide and power on the equipment.

Step 10 Query the current alarms by using the Web LCT.There should be no new alarms.

----End

6.2 Replacing an ODUIf the radio link provided by an ODU is not configured with protection and the services on theODU are not configured with protection, replacing the ODU interrupts the services. In addition,

6 Part ReplacementOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

the services on the radio link of the other polarization direction are affected if the radio linkprovided by the ODU is configured with XPIC.

Prerequisitel You must be aware of the impact of ODU replacement.

l You must know the specific positions of the ODU to be replaced and the IF board connectedto the ODU.

l The spare ODU must be available and the type must be the same as the type of the ODUto be replaced.

Tools, Instruments, and Materialsl Torque wrench

l Web LCT

l Silicon

l Waterproof adhesive tape

Notes

Before you replace an ODU that is installed on the coupler, power off the ODU to be replaced,but do not power off or mute the other ODU. Otherwise, the services may be affected. Theinterface of the coupler generates little RF radiation, thus meeting the safety standards forelectromagnetic radiation.

Procedure

Step 1 Query the current alarms on the ODU.

Step 2 Turn off the ODU switch on the OptiX RTN 605 panel.

Step 3 Remove the IF cable and the PGND cable connected to the ODU.

Step 4 Remove the ODU.

If... Then...

You need to remove the OptiX RTN 600ODU with a waveguide interface

Loosen the four latches of the ODU anddisconnect the ODU from the antenna, thehybrid coupler, or ODU adapter.

You need to remove the OptiX RTN 600ODU with a coaxial interface

Remove the ODU from the post.

You need to remove the RTN XMC ODUwith a coaxial interface

Loosen the four M6 captive screws of theODU cornerwise, Remove the ODU.

Step 5 Ensure that the type of the spare ODU is the same as the type of the ODU to be replaced.

Step 6 Install the ODU.



6-3

If... Then...

You need to install a new OptiX RTN 600ODU with a waveguide interface

See the OptiX RTN 600 ODU QuickInstallation Guide to install the ODU.

You need to install a new OptiX RTN 600ODU with a coaxial interface

See the OptiX RTN 600 ODU QuickInstallation Guide to install the ODU.

You need to install a new RTN XMC ODUwith a coaxial interface

See the RTN XMC ODU Quick InstallationGuide to install the ODU.

Step 7 Connect the PGND cable and the IF cable to the ODU.

Step 8 Waterproof the IF interface on the ODU.

Step 9 Turn on the ODU switch on the OptiX RTN 605 panel.

Step 10 After the ODU starts to work, observe the ODU indicator on the IDU 605 panel.The ODU indicator should be on and green.

Step 11 Query the current alarms of the ODU.There should be no new alarms.

----End

6.3 Replacing the IF CableThe IF cable cannot transmit radio services when it is replaced.

Prerequisitel You must be aware of the impact of IF cable replacement.

l You must know the specific positions of the IF cable to be replaced and the IF boardconnected to the IF jump.

l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required toconnect the IF cable to the IDU and both ends of the IF cable should be terminated withtype-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to theIDU and the cable end connecting to the IDU should be terminated with the TNC connectorand the cable end connecting to the ODU should be terminated with the type-N connector.

Tools, Instruments, and Materialsl Ejector lever

l Electro-technical knife

l File

l Installation parts and accessories of the connector

l IF cable

l Waterproof adhesive tape

6 Part ReplacementOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Use the Web LCT to query the current alarms of the board.

Step 2 Turn off the ODU switch on the OptiX RTN 605 panel.

Step 3 Disconnect the IF cable and the IF jump, and the IF cable and the ODU.

Step 4 Use a multimeter to test the cable circuit so as to determine whether to make the IF cable withconnectors again or replace the IF cable.

If... Then...

If the IF cable with connectors need be made again Make new connectors for the IF cable.

If the IF cable need be replaced Replace with a new IF cable.

Step 5 Connect the IF cable and the IF jump, and the IF cable and the ODU.

Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.

Step 7 Turn on the ODU switch on the OptiX RTN 605 panel.

Step 8 After the ODU starts to work, observe the ODU indicator on the OptiX RTN 605 panel.The ODU indicator should be on and green.

Step 9 Query the current alarms of the IDU.There should be no new alarms.

----End



6-5

7 Supporting Task

About This Chapter

This topic describes the common maintenance operations.

7.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

7.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

7.3 Browsing Alarms, Abnormal Events, and Performance EventsThe Web LCT is used to browse alarms, abnormal events, and performance events at the NElayer.

7.4 Querying a ReportYou can obtain the version, manufacture, and radio link information of all the boards by queryingthe corresponding report.

7.5 Software loopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS. Inthe OptiX RTN 605, the tributary unit, IF ports, and Ethernet ports support loopback.

7.6 SCC ResettingSCC resetting is a process in which all the software modules on the SCC are reset, the SCC isre-initiated.

7.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method for networkmaintenance and self-check.

7.8 Setting the Automatic Release FunctionTo protect the NM and NE communication from improper operations, an NE supports theautomatic release of the ODU mute, loopback, and other operations that require you to exercisecaution. The automatic release time is five minutes by default. You can set whether to enablethe automatic release function and the automatic release time using the NMS.

OptiX RTN 605Maintenance Guide 7 Supporting Task


7-1

7.9 Configuring Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.

7.10 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through theNMS but cannot be set through the NMS.

7.11 Querying the Working Status of an Ethernet PortThrough the operation, you can learn about the enable/disable state, loopback status, and theactual working mode of an Ethernet port.

7.12 Setting the Threshold of Received Traffic Flow on an Ethernet PortThe FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceedsthe specified threshold.

7.13 Performing Statistics for the Traffic Flow on an Ethernet PortYou can perform this operation to perform statistics for the traffic flow on an Ethernet port withina specified period.

7 Supporting TaskOptiX RTN 605

Maintenance Guide


Issue 03 (2010-05-30)

7.1 Hardware LoopbackHardware loopback refers to the loopback operation performed by changing the physicalconnection.

Hardware loopback is classified into optical cable loopback, SDH/PDH cable loopback, andEthernet port loopback.l Optical cable loopback indicates that the receive and transmit optical fibers are connected

through a fiber jumper on the ODF. In certain occasions, an optical attenuator is addedbased on the actual situation, to prevent the optical board from being damaged by theexcessive receive optical power.

l SDH/PDH cable loopback indicates that the receive and transmit SDH/PDH cables areconnected through a short-circuiting cable or connector on the DDF.

l Ethernet port loopback indicates that the receive and transmit service signals on oneEthernet port are looped back through a special loopback Ethernet cable.

7.2 Cleaning Fiber Connectors and AdaptersThe optical connectors are easily contaminated in the maintenance process. The minute dustparticles that can be seen only in the microscope can also affect the quality of optical signals. Inthis case, the system performance deteriorates. Hence, the fiber connectors or adapters that areterminated need to be cleaned in time.

7.2.1 Cleaning Fiber Connectors Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

7.2.2 Cleaning Fiber Connectors Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

7.2.3 Cleaning Fiber Adapters Using Optical Cleaning SticksClean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiberadapters on the optical interface board. The method of cleaning fiber adapters on the opticalattenuators and flanges is the same.

7.2.1 Cleaning Fiber Connectors Using Cartridge CleanersWhen there are special cartridge cleaners (such as the CLETOP cassette cleaner), use them forcleaning the fiber connectors.

Prerequisitel Disconnect both ends of the fiber. Make sure that there is no laser light on the fiber

connector.l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector

is contaminated.

Tools, Equipment, and MaterialsCartridge cleaner



7-3

Procedure

Step 1 Press down and hold the lever, and the shutter slides back and exposes a new cleaning area.

Figure 7-1 CLETOP cassette cleaner

Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in thedownward direction.

Figure 7-2 Dragging the fiber tip slightly on one cleaning area


Maintenance Guide


Issue 03 (2010-05-30)

Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.

Figure 7-3 Dragging the fiber tip slightly on the other cleaning area

Step 4 Release the lever to close the cleaning area.

----End

7.2.2 Cleaning Fiber Connectors Using Lens TissueWhen there is no cartridge cleaners, use the lens tissue for cleaning fiber connectors.

Prerequisitel Disconnect both ends of the fiber to be inspected. Make sure there is no laser light present

on the fiber connector.

l Inspect the fiber connector with a fiber microscope to make sure that the fiber connectoris contaminated.

Tools, Equipment, and Materialsl Clean solvent

l Non-woven lens tissue

l Special compressed gas



7-5

NOTE

l Using the isoamylol as the clean solvent is recommended, and the propyl can also be used. Do not use alcoholor formalin.

l The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue.

l The special cleaning roll can replace the special compressed gas.

Procedure

Step 1 Place a small amount of cleaning solvent on the lens tissue.

Step 2 Drag the fiber tip slightly on the lens tissue.

Figure 7-4 Cleaning the fiber with the lens tissue

Step 3 Repeat step 2 several times on the areas of the lens tissue that have not been used.

Step 4 Using compressed gas, blow off the fiber tip.When using compressed gas:

l First spray it into the air as the initial spray of condensation can contain some sediment.

l Keep the injector nozzle as close as possible to the connector surface without touching it.

----End

7.2.3 Cleaning Fiber Adapters Using Optical Cleaning SticksClean fiber adapters with optical cleaning sticks. This part describes the method of cleaning fiberadapters on the optical interface board. The method of cleaning fiber adapters on the opticalattenuators and flanges is the same.


Maintenance Guide


Issue 03 (2010-05-30)

Prerequisitel Before you clean the fiber adapter, ensure that you remove the optical fiber and shut down

the laser. For details about how to shut down a laser, refer to Setting the State of a Laser.l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is

contaminated.

Tools, Equipment, and Materialsl Optical cleaning sticks

l Clean solvent

l Special compressed gas

NOTE

l For the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm, for the LC opticalinterface, use the cleaning stick with a diameter of 1.25 mm.

l The medical cotton or long fiber cotton can replace the optical cleaning stick.

l Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcoholor formalin.

l The special cleaning roll can replace the special compressed gas.

Procedure

Step 1 Place a small amount of cleaning solvent on the optical cleaning stick.

Step 2 Hold the stick straight out from the adapter and turn the stick clockwise four to five times.Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can cleanthe adapter tip.

Step 3 Using compressed gas, blow off the fiber tip.When using compressed gas:l First spray it into the air as the initial spray of condensation can contain some sediment.

l Keep the injector nozzle as close as possible to the connector surface without touching it.

----End

7.3 Browsing Alarms, Abnormal Events, and PerformanceEvents

The Web LCT is used to browse alarms, abnormal events, and performance events at the NElayer.

7.3.1 Checking the NE StatusYou 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.

7.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.

7.3.3 Browsing the Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.



7-7

7.3.4 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms.

7.3.5 Browsing the Abnormal EventsPeriodically browsing abnormal events helps you to find abnormalities in the equipment in time.

7.3.6 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

7.3.7 Browsing the History PerformancePeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

7.3.8 Browsing the Performance Event Threshold-Crossing RecordsYou can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.

7.3.1 Checking the NE StatusYou 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.

Prerequisite


Tools, Equipment, and Materials

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 NE, and choose NE Login.

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

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 Slot Layout.


Maintenance Guide


Issue 03 (2010-05-30)

In normal cases, NE STATE is Running.

----End

7.3.2 Checking the Board StatusYou can learn about the board status in a visual manner by checking the slot diagram.


Tools, Equipment, and MaterialsWeb LCT

Procedure

Step 1 Double-click an NE in the Main Topology. Then, the Slot Layout is displayed. The NE shouldbe in Running Status.

Step 2 Click the icon. Then, the legend description is displayed.

Step 3 Check the running status of the boards according to the legend description. If a board is runningnormally, the board icon should be green.

----End

7.3.3 Browsing the Current AlarmsYou can find the faults that occur on the equipment by browsing current alarms.



Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer, and click the icon in the toolbar.



7-9

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

NOTE

The number shown by each indicator indicates the number of current network-wide alarms, which are notcleared, of the specific severity.

The Browse Current Alarms tab is displayed by default.

Step 2 Browse the displayed alarms.

Step 3 Select the newly generated alarms, record the details of the alarms.

Step 4 Notify the troubleshooting personnel to clear the alarms in time.

----End

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

7.3.4 Browsing History AlarmsYou can know the faults that occur on the equipment in a past period of time by browsing historyalarms.



Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer, and click the icon in the toolbar.

Step 2 Click the Browse History Alarm tab.

Step 3 Click Filter. The Filter dialog box is displayed.1. In Severity, select the alarm severity to be queried.2. In Alarm Type, select the alarm type.3. In Rising Time, specify the alarm generation time.4. In Cleared Time, specify the alarm clearance time.


Maintenance Guide


Issue 03 (2010-05-30)

The start time should be the time when the last history alarm browsing operation wasperformed, and the end time should be the current time.

Step 4 Click Filter.

Step 5 Browse the displayed history alarms.

Step 6 Optional: Click Save As. Then, the history alarms are saved and archived as a file.

----End

Related Information

A history alarm is an alarm that has been cleared. An NE stores a maximum of 1,000 historyalarms.

7.3.5 Browsing the Abnormal EventsPeriodically browsing abnormal events helps you to find abnormalities in the equipment in time.



Web LCT

Procedure

Step 1 Select an NE from the NE Explorer, and choose Alarm > Browse Abnormal Events from theFunction Tree.

TIP

Alternatively, you can select an NE and then click the icon to switch to the Browse AbnormalEvents tab page.

Step 2 Click Filter. The Filter dialog box is displayed.1. Set Level and Type.2. In Abnormal Event, select Select All.

Step 3 Click OK.

Step 4 Browse the abnormal events.

Step 5 Optional: Click Save As. Then, the abnormal events are saved and archived as a file.

----End

Related Information

An abnormal event is an abnormality that arises in the system at a particular time and not anabnormality that persists for a long time. Being different from alarms, an abnormal event hasonly occurrence time, with clearance time not provided.



7-11

7.3.6 Browsing Current Performance EventsPeriodically browsing the performance events helps you to check the long-term running statusof the equipment.

Prerequisitel The performance monitoring function must be enabled.



Procedure

Step 1 In the NE Explorer, select the required board from the Object Tree, and then choosePerformance > Current Performance from the Function Tree.


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

Step 4 Click Count, select all the performance events, and select Consecutive Severely ErroredSecond in Display Options.

Step 5 Click Query.

Step 6 Browse the current performance events.In normal cases, no bit error performance events is displayed, and the number of pointerjustification events is less than six per day on each port.

Step 7 Click Gauge, select all the performance events, and select Current Value and Maximum/Minimum Value in Display Options.

Step 8 Click Query.

Step 9 Browse the current performance events.Compared with the history records, the gauge indicators, such as board temperature, do notchange drastically.

Step 10 Set Monitor Period to 24-Hour.

Step 11 Repeat steps Step 4 to Step 9 query the performance events in a period of 24 hours.

----End

Related InformationThe counter of current performance events measures all the performance events that arisebetween the start time of the monitoring period and the current time.

7.3.7 Browsing the History PerformancePeriodically browsing the performance events helps you to check the long-term running statusof the equipment.


Maintenance Guide


Issue 03 (2010-05-30)




Web LCT

Procedure

Step 1 Select a specific board from the NE Explorer, and choose Performance > HistoryPerformance from the Function Tree.


Step 3 Select 15-Minute after Monitor Period.

Step 4 Specify the start time and end time of a specific time span. The time span starts from the timewhen the last history performance event browsing operation was performed to the current time.

Step 5 Select all the available performance events in Count, and select Zero Data in DisplayOptions.


Step 7 Click Save As.The system displays the text file that lists the history performance events.

NOTE

You can also save the text file as required.



Step 10 Click Save As to save the performance events.The system displays the text file that lists the history performance events.

NOTE

You can also save the text file as required.

Step 11 Select 24-Hour after Monitor Period.

Step 12 Repeat Step 4 to Step 10 to query the history performance events in a period of 24 hours.

----End

Related Information

The history performance event refers to a performance event whose statistics period ends in thepast. Only the performance events on the NE side can be queried using the Web LCT. Currently,the NE can store thirty 24-hour and six hundreds and seventy-two 15-minute history performanceevents related to the receive level and bit errors on the radio link; the NE can store a maximumof six 24-hour and sixteen 15-minute other history performance events.



7-13

7.3.8 Browsing the Performance Event Threshold-Crossing RecordsYou can learn about the threshold-crossing information of the performance events of an NE bybrowsing the performance event threshold-crossing records.




Procedure

Step 1 In the NE Explorer, select the required board, and then choose Performance > PerformanceThreshold-Crossing from the Function Tree.The Performance Threshold-Crossing dialog box is displayed.



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 history performance event browsing operationwas performed to the current time.

Step 5 In Performance Event Type, select Select All.

Step 6 Optional: Specify Display Options.

Step 7 Click Query. Browsing the threshold-crossing performance events.



NOTE



Step 10 Repeat steps Step 4 to Step 8 to query the performance events in a period of 24 hours.

----End

7.4 Querying a ReportYou can obtain the version, manufacture, and radio link information of all the boards by queryingthe corresponding report.

7.4.1 Querying a Board Information Report Through the Web LCTYou can know the PCB version, logic version, and software version of each board by queryinga board information report.


Maintenance Guide


Issue 03 (2010-05-30)

7.4.2 Querying a Board Manufacture Information ReportYou can know the manufacture information of each board and the SFP module by querying aboard manufacture information report.

7.4.3 Querying the Status of a Radio LinkThe Web LCT supports the end-to-end management of a microwave link. You can query theinformation about the two ends of a radio link in an interface.

7.4.1 Querying a Board Information Report Through the Web LCTYou can know the PCB version, logic version, and software version of each board by queryinga board information report.



Web LCT

Procedure

Step 1 Select an NE from the Object Tree in the NE Explorer.

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

Step 3 All the board version information of the NE is displayed in the Board Information Report tabpage.


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

NOTE

You can save the text file as required.

----End

Related Information

Focus on the PCB version, logic version, and software version of each board when you querythe board information.

7.4.2 Querying a Board Manufacture Information ReportYou can know the manufacture information of each board and the SFP module by querying aboard manufacture information report.

Prerequisitel The communication between the Web LCT and the NE must be normal.




7-15


Web LCT

Procedure


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

Step 3 All the board manufacture information of the NE is displayed in the Board Detail InformationReport tab page.


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

NOTE

You can save the text file as required.

----End

7.4.3 Querying the Status of a Radio LinkThe Web LCT supports the end-to-end management of a microwave link. You can query theinformation about the two ends of a radio link in an interface.


l The NE user must have the authority of Maintenance Level or higher.

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer, and then choose Configuration > LinkConfiguration from the Function Tree.

Step 2 Click the IF/ODU Configuration tab page, right-click the corresponding IF board, and thenchoose HOP Management from the shortcut menu.

Step 3 In the HOP Management Function Tree, choose Configuration > Link Configuration, andthen click the IF/ODU Configuration tab.

Step 4 Select the corresponding IF board in the IF/ODU Configuration tab page, and then clickQuery.The configuration information of the links at two ends is displayed.

Step 5 Check whether the configuration information of the link at one end is consistent with theconfiguration information of the link at the other end and whether the configuration informationof the links at the two ends is correct.

----End


Maintenance Guide


Issue 03 (2010-05-30)

7.5 Software loopbackSoftware loopback refers to the loopback operation that is implemented by using the NMS. Inthe OptiX RTN 605, the tributary unit, IF ports, and Ethernet ports support loopback.

7.5.1 Setting Tributary LoopbackThe OptiX RTN 605 supports the tributary inloop/outloop.7.5.2 Setting Loopback for the IF PortThe OptiX RTN 605 1E/2E supports the IF port inloop/outloop. The OptiX RTN 605 1F/2Fsupports the IF port outloop.7.5.3 Setting Loopback for the Ethernet Port of the RTN 605 1F/2FThe RTN 605 1F/2F/1E/2E board supports the Ethernet port inloop at the PHY layer.7.5.4 Locating the Fault by Performing LoopbacksLoopback is a common method to locate a fault.

7.5.1 Setting Tributary LoopbackThe OptiX RTN 605 supports the tributary inloop/outloop.

Prerequisitel The communication between the Web LCT and the NE must be normal.l The NE user must have the authority of Maintenance Level or higher.

ContextThe tributary inloop is a process where signals at an E1 port are looped back at the tributary unittowards the IF unit.

Figure 7-5 Inloop

Tributary unitIF unit

PDH

The tributary outloop is a process where an E1 signal is looped back at the tributary unit of thelocal IDU towards the remote equipment.

Figure 7-6 Outloop

PDH

Tributary unitIF unit



7-17

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 cleared automatically after some time (by default, it is clearedwithin five minutes). For details, see 7.8 Setting the Automatic Release Function.

ProcedureStep 1 Select the PDH interface board from the Object Tree.

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

Step 3 Choose By Function, and select Tributary Loopback from the drop-down list.

Step 4 Set the loopback status of the port or path according to the requirements.

Step 5 Click Apply.The system displays a prompt dialog box for confirmation.

Step 6 Click OK.

----End

7.5.2 Setting Loopback for the IF PortThe OptiX RTN 605 1E/2E supports the IF port inloop/outloop. The OptiX RTN 605 1F/2Fsupports the IF port outloop.



ContextThe IF port inloop is a process where the IF signals are looped back at the IF unit of the IDUtowards the tributary unit.

Figure 7-7 Inloop

IF unitTributaryunit

IF signal


Maintenance Guide


Issue 03 (2010-05-30)

The IF port outloop of the IDU 605 is a process where the IF signals are looped back at the IFunit of the IDU towards the remote equipment.

Figure 7-8 Outloop

IF unitTributaryunit

IF signal

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 cleared automatically after some time (by default, it is clearedwithin five minutes). For details, see 7.8 Setting the Automatic Release Function.

l To perform the software loopback on the protection IF unit of 1+1 HSB/FD/SD, switch theprotection IF unit to the working state manually. Otherwise, the operation may fail.

l Before performing the loopback operation for the the RTN 605 1F/2F IF port, disable theAM function at the two ends of a link.

Procedure

Step 1 Select the IF board from the Object Tree.

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

Step 3 Choose By Function, and select IF Port Loopback from the drop-down list.

Step 4 Set the loopback status of the port or path according to the requirements.


Step 6 Click OK.

----End

7.5.3 Setting Loopback for the Ethernet Port of the RTN 605 1F/2FThe RTN 605 1F/2F/1E/2E board supports the Ethernet port inloop at the PHY layer.



7-19



ContextThe Ethernet port PHY inloop is a process where the Ethernet frame signals are looped back atthe interface module of the board at the MAC layer toward the backplane.

Figure 7-9 Inloop

Ethernet ServiceProcessing UnitBackplane

PHY

Precautions

CAUTIONThe services may be interrupted at the port or on the path where the loopback is performed.

Procedure

Step 1 Select the Ethernet processing board from the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface > ExternalPort > Basic Attributes from the Function Tree.

Step 3 Choose External Port in the Ethernet Interface tab, and choose PHY Loopback in the BasicAttributes tab.

Step 4 Set the loopback status of the port according to the requirements.


Step 6 Click OK.

----End

7.5.4 Locating the Fault by Performing LoopbacksLoopback is a common method to locate a fault.


Maintenance Guide


Issue 03 (2010-05-30)



Service Trail

Figure 7-10 shows how to locate a fault by performing loopback.

Figure 7-10 Service trail

IF Board PXC SDH InterfaceBoard

ODU

NE2(IDU 620)

ODU

NE3(IDU 620)

Fiber

ODU

NE4(IDU 605)

IF UnitPXC ODU

NE1(IDU 605)

TributaryUnit

TributaryUnit

PXC IF Unit IF Board PXC SDH InterfaceBoard

Procedure

Step 1 If the services are available on the radio links, first perform the inter-station loopback to locatethe fault on a certain hop when using the loopback method.

1. Set the outloops for the SDH optical interface boards on NE2 and NE3, and then performthe inter-station loopback to locate the fault.

Step 2 After the fault is located to a certain radio link, perform the intra-station loopback to locate thefault to a certain NE or board.

1. Set inloop for the IF board or Set inloop for the IF port on the NEs at two ends of theradio link where the fault occurs, and then locate the fault to the service receiver or theradio link.

2. If the fault is located in the service receiver, Replace the IDU to locate the fault.

3. If the radio link is faulty, replace the board to locate the fault to the ODU.

----End



7-21

7.6 SCC ResettingSCC resetting is a process in which all the software modules on the SCC are reset, the SCC isre-initiated.

Prerequisitel The Web LCT is in normal communication with the NE.


Precautions

During the resetting, protection switching and NMS operations are unavailable although therunning services are not affected.

Procedure

Step 1 In the Slot Layout of the Web LCT, right-click the SCC to be reset.

Step 2 Choose SCC Reset from the shortcut menu.A prompt dialog box is displayed.

Step 3 Click OK.The system displays the Operation Succeed dialog box.

Step 4 Click Close.

----End

7.7 PRBS TestThe pseudorandom binary sequence (PRBS) test is an important method for networkmaintenance and self-check.

7.7.1 PRBS Test of the Tributary UnitIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the tributary unit of the IDU 605.

7.7.2 PRBS Test of the IF UnitIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the OptiX RTN 605 1F/2F.

7.7.1 PRBS Test of the Tributary UnitIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the tributary unit of the IDU 605.



Maintenance Guide


Issue 03 (2010-05-30)


ContextThe OptiX RTN 605 supports the PRBS test in the tributary direction and the cross-connectdirection.

NOTE

The cross-connect direction of the RTN 605 refers to the IF direction.

The PRBS test in the tributary direction can be used to check the connection between the tributaryunit and the DDF, as shown in Figure 7-11.

Figure 7-11 PRBS test in the tributary direction

PRBSTransmitter

PRBSRecevicer

Tributary unitDDF frame

1

1 Inloop at the DDF frame

The PRBS test in the cross-connect direction can be used to check the connection between thetributary unit and the remote NE, as shown in Figure 7-12.

Figure 7-12 PRBS test in the cross-connect direction

Local NE Remote NE

IF unit

IN

OUTTributary unit IF unit

PRBSTransmitter

PRBSReceiver

IF port inloop

1 2

1 2 IF port outloop



7-23

Precautions

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.

Procedure

Step 1 Set the loopback at the proper location. For details, see Figure 7-11 and Figure 7-12.

Step 2 Select an E1 interface board from the Object Tree in the NE Explorer.

Step 3 Choose Configuration > PRBS Test from the Function Tree.The PRBS Test tab page is displayed.

Step 4 Select the port to be tested.

Step 5 Specify Direction, Duration, and Measured in Time.

NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start the test.The The operation may interrupt the service. Are you sure to continue? dialog box isdisplayed.

Step 8 Click OK.

Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the testresult.

NOTE

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

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and thecurve should be in green.

l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and thecurve should be in red.

l Invalid: It indicates that no bit is received. The curve should be in yellow.

----End

7.7.2 PRBS Test of the IF UnitIn the absence of a special test tool, you can perform the PRBS test by using the embedded testsystem on the OptiX RTN 605 1F/2F.


Maintenance Guide


Issue 03 (2010-05-30)



Precautions

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.

l The protection IF unit does not support the PRBS test. Hence, you need to power off theworking ODU and perform the PRBS test on the working IF unit if you need to test theprotection radio link. In this manner, the PRBS signals from the protection IF unit aretransmitted through the protection bus, and thus PRBS test is performed for the protectionradio link.

Procedure

Step 1 See 7.5.2 Setting Loopback for the IF Port to perform the inloop on the ODU.

Step 2 Select an IF board from the Object Tree in the NE Explorer.

Step 3 Choose Configuration > PRBS Test from the Function Tree.The PRBS Test tab page is displayed.

Step 4 Select the port to be tested.

Step 5 Specify Direction, Duration, and Measured in Time.

NOTE

l The PRBS test supports three time units: one second, 10 minutes, and one hour.

l A maximum of 255 test cycles is permissible for the PRBS test.

Step 6 Optional: Select Accumulating Mode.

Step 7 Click Start the test.The The operation may interrupt the service. Are you sure to continue? dialog box isdisplayed.

Step 8 Click OK.

Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the testresult.



7-25

NOTE

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

l Normal: It indicates that the path is working properly. The number of PRBSs should be zero, and thecurve should be in green.

l Error: It indicates that the path has errors. The number of PRBSs should be greater than zero, and thecurve should be in red.

l Invalid: It indicates that no bit is received. The curve should be in yellow.

----End

7.8 Setting the Automatic Release FunctionTo protect the NM and NE communication from improper operations, an NE supports theautomatic release of the ODU mute, loopback, and other operations that require you to exercisecaution. The automatic release time is five minutes by default. You can set whether to enablethe automatic release function and the automatic release time using the NMS.



Procedure


Step 2 Choose Configuration > Automatic Disabling of NE Function from the Function Tree.

Step 3 Specify Auto Disabling and Auto Disabling Time (min).

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

----End

7.9 Configuring Performance Monitoring Status of NEsBy default, the performance monitoring of NEs is enabled. You can disable or enable thisfunction manually and set the period of the performance monitoring of NEs manually.

PrerequisiteThe NE user must have the authority of Operation Level or higher.


Procedure

Step 1 In the NE Explorer, select the NE and then choose Performance > NE Performance MonitorTime from the Function Tree.


Maintenance Guide


Issue 03 (2010-05-30)

Step 2 Set the parameters of NE performance monitoring.

1. Select 15-Minute or 24-Hour.2. Select Enable or Disable 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 Set 15-Minute Monitoring and Set 24-Hour Monitoring are generally set to Enable.

l You can specify the start time of the performance monitoring function, only after selecting Enable inthe 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 Enable andthen selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.

Step 3 Click Apply.

----End

7.10 Querying the Impedance of an E1 ChannelThe impedance of an E1 channel is 75 ohms or 120 ohms, which can be queried through theNMS but cannot be set through the NMS.

Prerequisitel The communication between the Web LCT and the NE must be normal.l The NE user must have the authority of Maintenance Level or higher.




7-27

Procedure

Step 1 Select A PDH tributary board from the Object Tree in the NE Explorer.

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

Step 3 Select By Board/Port(Channel).

Step 4 Select Port in the list.

Step 5 Select a port, and check Port Impedance.

----End

7.11 Querying the Working Status of an Ethernet PortThrough the operation, you can learn about the enable/disable state, loopback status, and theactual working mode of an Ethernet port.




Procedure

Step 1 Select an Ethernet board from the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from theFunction Tree.

Step 3 Select External Port.

Step 4 By default, click the Basic Attributes tab page.

Step 5 Check Enabled/Disabled, Working Mode, and Port Physical Parameters of the associatedport.

----End

7.12 Setting the Threshold of Received Traffic Flow on anEthernet Port

The FLOW_OVER alarm is reported when the traffic flow received on an Ethernet port exceedsthe specified threshold.



Maintenance Guide


Issue 03 (2010-05-30)


Tools, Equipment and MaterialsWeb LCT

ContextThis operation can be performed on the PORT port of the EM4T board, which is a logical boardof the OptiX RTN 605 1E/2E.

Procedure

Step 1 Select the required Ethernet board from the Object Tree.

Step 2 Choose Configuration > Ethernet Interface Management > Ethernet Interface from theFunction Tree.

Step 3 Select External Port.

Step 4 Select the Advanced Attributes tab.

Step 5 Set Zero-Flow Monitor to Enable.

Step 6 Set Flow Threshold(Mbps).

Step 7 Optional: Set Zero-Flow Monitor Interval(min).l If this parameter takes the default value of 0, the FLOW_OVER alarm is reported whenever

the traffic flow received on the port exceeds Flow Threshold(Mbps).l If the value of this parameter is not 0, the FLOW_OVER alarm is reported only when the

traffic flow received on the port within a period of Zero-Flow Monitor Interval(min) alwaysexceeds Flow Threshold(Mbps).

Step 8 Click Apply.

----End

7.13 Performing Statistics for the Traffic Flow on an EthernetPort

You can perform this operation to perform statistics for the traffic flow on an Ethernet port withina specified period.



l The flow monitoring function must be enabled on the associated Ethernet port. To enablethe flow monitoring function on a port, do as follows:

1. Select the required Ethernet board from the Object Tree.2. Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.



7-29

3. Select the Set Monitoring tab.4. Set Monitor Status to Enabled for the Ethernet port.

Tools, Equipment and MaterialsWeb LCT

Contextl After the flow monitoring function is enabled, the system saves the statistics about the

received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, thesystem stores the statistics that are collected in the last 30 days. In the system, everymeasurement entry shows the average transmit rate and average receive rate within a periodof 15 minutes. You can query the statistics in the last 30 days.

l This operation can be performed on the PORT port of the EM4T board, which is a logicalboard of the OptiX RTN 605 1E/2E.

Procedure

Step 1 Select the required Ethernet board from the Object Tree.

Step 2 Choose Performance > Ethernet Port Traffic Monitor from the Function Tree.

Step 3 Select the Query traffic tab.

Step 4 Set the object to be queried, the required time, and display mode, and then click Query.The system displays the query result in a table or in a graph.

----End


Maintenance Guide


Issue 03 (2010-05-30)

A Alarm Reference

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

A.1 Alarm ListThe following table lists all the possible alarms generated by the OptiX RTN 605 in alphabeticalorder.

A.2 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 605 in an alphabet order and how to handlethese alarms.

OptiX RTN 605Maintenance Guide A Alarm Reference


A-1

A.1 Alarm ListThe following table lists all the possible alarms generated by the OptiX RTN 605 in alphabeticalorder.

Table A-1 Alarm list

Alarm Name Description Level Source

BD_STATUS Board not in position Major ODU

CONFIG_NOSUPPORT

Configuration is not supported. Major ODU

DBMS_ERROR Database errors Major SCC

DBMS_PROTECT_MODE

Database in protection mode Critical SCC

DOWN_E1_AIS Alarm indication of 2 Mbit/sdownstream signals

Minor PH1

E1_LOC Loss of 2M clock in upstreamsignals

Major PH1

ETH_CFM_LOC Loss of connectivity Critical EMS4, EM4T

ETH_CFM_MISMERGE

Misconnection Critical EMS4, EM4T

ETH_CFM_RDI An MEP fails to receive CCMpackets.

Minor EMS4, EM4T

ETH_CFM_UNEXPERI

Errored frames Critical EMS4, EM4T

EX_ETHOAM_CC_LOS

Loss of periodical connectivitycheck packets

Critical EMS4, EM4T

EX_ETHOAM_MPID_CNFLCT

Conflict of MPIDs Major EMS4, EM4T

ETH_LOS Loss of Ethernet port connection Critical EMS4, EM4T

ETHOAM_DISCOVER_FAIL

Discovery failure detected bypoint-to-point Ethernet OAM

Minor EMS4, EM4T

ETHOAM_RMT_LOOP

Remote loopback detected bypoint-to-point Ethernet OAM

Minor EMS4, EM4T

ETHOAM_RMT_SD

Remote Ethernet performancedegradation detected by point-to-point Ethernet OAM

Minor EMS4, EM4T

A Alarm ReferenceOptiX RTN 605

Maintenance Guide

A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


ETHOAM_RMT_CRIT_FAULT

Severe fault detected by point-to-point Ethernet OAM at theremote end

Minor EMS4, EM4T

FLOW_OVER Excessive data traffic received byEthernet ports

Minor EM4T

LAG_PORT_FAIL A port of an LAG fails. Minor EMS4, EM4T

ETHOAM_SELF_LOOP

MAC port loopback detected bypoint-to-point Ethernet OAM

Major EMS4, EM4T

HARD_BAD Hardware fault Critical SCC, ODU, IF0,PW48A, PW48B,IFH1, EMS4, EM4T

IF_CABLE_OPEN IF cables are disconnected. Major IF0, IFH1

IF_INPWR_ABN The power supplied by an IFboard to an ODU is abnormal.

Major ODU

LOOP_ALM A loopback occurs. Minor ODU, IF0, PH1,IFH1, EMS4, EM4T

MSSW_DIFFERENT

The active board and the standbyboard have inconsistent software.

Major SCC

MW_BER_EXC Excessive errors on radio links Minor IF0, IFH1

MW_BER_SD Signal degradation due toexcessive errors on radio links

Minor IF0, IFH1

MW_FEC_UNCOR

Uncorrectable errors in RSencoding

Minor IF0, IFH1

MW_LIM Label mismatch on radio links Major IF0, IFH1

MW_LOF Loss of RS frames Critical IF0, IFH1

MW_RDI Remote defect indication onradio links

Minor IF0, IFH1

NESF_LOST Loss of NE software Critical SCC

NESTATE_INSTALL

The NE is in the installation state. Critical SCC

POWER_ALM Power module alarm Major ODU, PW48A,PW48B

R_LOC Loss of clock on the receive lineside

Critical IF0, IFH1

R_LOF Loss of frame on the receive lineside

Critical IF0, IFH1



A-3


R_LOS Loss of signal on the receive lineside

Critical IF0

RADIO_FADING_MARGIN_INSUFF

Radio fading margin isinsufficient.

Minor ODU

RADIO_RSL_BE-YONDTH

Antennas are not aligned. Minor ODU

RADIO_MUTE The radio transmitter is muted. Warning ODU

RADIO_RSL_HIGH

Over high radio receive signallevel

Critical ODU

RADIO_RSL_LOW

Over low radio receive signallevel

Critical ODU

RADIO_TSL_HIGH

Over high radio transmit signallevel

Critical ODU

RADIO_TSL_LOW

Over low radio transmit signallevel

Critical ODU

RELAY_ALARM Relay alarm Critical EOW

RP_LOC Loss of the received phase-locked clock

Major SCC

RPS_INDI Indication of the radio protectionswitching

Major SCC

SWDL_ACTIVATED_TIMEOUT

The activation timeout of thesoftware package

Critical SCC

SWDL_AUTOMATCH_INH

The automatic match function isdisabled

Minor SCC

SWDL_CHGMNG_NOMATCH

The board software version andthe running software version areinconsistent

Critical SCC

SWDL_COMMIT_FAIL

NE submission failure Minor SCC

SWDL_INPROCESS

The NE is in the process ofpackage loading.

Minor SCC

SWDL_NEPKGCHECK

Loss of files in a softwarepackage

Critical SCC

SWDL_PKG_NOBDSOFT

Files are deleted when they arecustomized.

Minor SCC

SWDL_ROLLBACK_FAIL

The version rollback on an NEfails.

Minor SCC


Maintenance Guide


Issue 03 (2010-05-30)


T_ALOS Loss of analog signals at 2 Mbit/s interfaces

Major PH1

TEMP_ALARM The ambient temperature of theboard crosses the threshold.

Minor SCC, ODU

UP_E1_AIS Alarm indication of 2 Mbit/supstream signals

Minor PH1

VOLT_LOS Loss of voltage Major IF0, PW48A,PW48B, IFH1

NOTEAll alarmed boards refer to the logical boards displayed on the NMS.

A.2 Alarms and Handling ProceduresThis topic describes all the alarms on the OptiX RTN 605 in an alphabet order and how to handlethese alarms.

A.2.1 BD_STATUS

Description

The BD_STATUS is an alarm indicating that the board is not in position.

Attribute

Alarm Severity Alarm Type

Major Equipment alarm

Parameters

None.

Impact on the System

The ODU fails to work.

Possible Causesl Cause 1: Other alarms are generated.

l Cause 2: The ODU is faulty.



A-5

Procedure

Step 1 Cause 1: Other alarms are generated.(1) Query the IDU 605 to see whether the HARD_BAD, IF_CABLE_OPEN or

VOLT_LOS alarm is generated.

If... Then...

Yes Clear these alarms first.

No Clear the alarm according to the solutionfor the alarm that is generated when theODU is faulty.

Step 2 Cause 2: The ODU is faulty.(1) Replace the ODU that reports the alarm. For details, see 6.2 Replacing an ODU.

----End

Related InformationNone.

A.2.2 CONFIG_NOSUPPORT

DescriptionThe CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Thisalarm is reported if an ODU detects that the specified parameters do not meet the requirementsof the ODU.

Attribute


Major Processing 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 thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.


Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 1 Indicates that the configuration data does not meet the specified requirement.l 0x01: The frequency is set incorrectly.

l 0x02: The T/R spacing is set incorrectly.

l 0x03: The transmit power is set incorrectly.

l 0x04: The ATPC threshold is set incorrectly.

l 0x05: The bandwidth is set incorrectly.

l 0x06: The modulation mode is set incorrectly.


The ODU fails to work normally. If the equipment is configured with 1+1 FD protection, theactive ODU generates the CONFIG_NOSUPPORT alarm. In this case, IF 1+1 protectionswitching may be triggered.

Possible Causes

Cause 1: The type and configuration parameters of the ODU do not match the requirements.

Procedure

Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.

(1) Determine the parameter that does not meet the requirement according to the alarmparameter. Then, handle the fault accordingly.

If... Then...

The alarm parameter takes a value from 0x01 to 0x03 Run Step 1.2.

The alarm parameter takes a value from 0x04 to 0x06 Run Step 1.3.

(2) Check whether the parameters of the ODU interface meet the requirements of networkplanning. For details, see Setting Parameters of ODU Interfaces.

If... Then...

Yes Replace the ODU with a correct one.

No Modify the parameters of the ODU interface.

(3) Check whether the parameters of the IF interface meet the requirements of networkplanning. For details, see Configuring the IF/ODU Information of a Radio Link.

If... Then...

Yes Replace the IDU.

No Configure the IF/ODU information of radio links.

----End



A-7


A.2.3 DBMS_ERROR

DescriptionThe DBMS_ERROR is an alarm indicating that errors occur in the processing of the systemdatabase.

Attribute





Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 1 Indicates the types of the database errors.l 0x01: The input parameters are invalid.

l 0x02: The database files do not exist.

l 0x03: The database memory area numbers are incorrect.

l 0x04: The database overwriting occurs.

l 0x05: Errors occur in the header information check in the database backuparea.

l 0x06: Errors occur in the FAT table structure check in the database storagearea.

l 0x07: Errors occur in the database check in the database backup area.

l 0x08: Restoring the database fails.

l 0x09: The database ID is invalid.

l 0x0A: The databases are different.

l 0x0B: The data is unchecked.

l 0x0E: The semaphore handle is invalid.

l 0x0F: Errors occur in applying for memory.

l 0x10: Errors occur in releasing memory.

l 0x12: Transmitting the message capsule fails.

l 0x13: The starting and ending records of the database are incorrect.

l 0x14: The database is null.

l 0x15: The flag is incorrectly set.

l 0x16: The input command parameters are incorrect.

l 0x17: Non-backup database.

l 0x18: The database is in protection mode.

l 0x19: The configuration is not verified.

Parameter 2 Indicates the errored data storage area.l 0x00: database in fdb0

l 0x01: database in fdb1

l 0x02: database in drdb

Parameter 3 Indicates the ID of the errored database.l 0x00: all databases in the entire storage area.

l 0x01-0xff: ID of the errored database


When the DBMS_ERROR alarm occurs, it indicates that errors occur in the system databaseprocessing. The system configuration may be lost. As a result, the failure indication is returnedfor certain query and setting commands, and certain system functions cannot work.



A-9

Possible Causesl Cause 1: The database processing fails or the database is damaged.

l Cause 2: The IDU is faulty.

Procedure

Step 1 Cause 1: The database operation fails.(1) Reset the SCC board. For details, see Resetting the SCC board.

If... Then...

The alarm clears after the board is reset End the fault handling.

The alarm persists after the board is reset Go to Cause 2.

Step 2 Cause 2: The IDU is faulty.(1) Replace the IDU.

----End


A.2.4 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, it indicates that errors occur in the systemdatabase processing. The system configuration may be lost. As a result, the failure indication isreturned for certain query and setting commands, and certain system functions cannot work.

Possible CausesCause 1: The data enters the protection mode due to frequent resets of the NE software.


Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Cause 1: The data enters the protection mode due to frequent resets of the NE software.(1) Replace the IDU.

----End


A.2.5 DOWN_E1_AIS

DescriptionThe DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when theIDU detects the 2 Mbit/s downlink signal of all 1s.

Attribute


Major Communication alarm


Name Meaning

Parameter 1 The value is always 0x01.

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicates that the alarm is reported in path 1.

Impact on the SystemThe E1 signal is unavailable.

Possible Causesl Cause 1: The opposite site transmits the E1_AIS alarm.


Procedure

Step 1 Cause 1: The opposite site transmits the E1_AIS alarm.



A-11

(1) Check whether the opposite site reports the UP_E1_AIS or T_ALOS alarm.

If... Then...

The opposite site reports the UP_E1_AISor T_ALOS alarm

Clear the alarm immediately.

The opposite site does not report theUP_E1_AIS or T_ALOS alarm

Solve the problem according to the solutionfor the problem that occurs when a board isfaulty.

Step 2 Cause 2: The IDU on the local site is faulty.

(1) Replace the IDU.

----End

Related Information

None.

A.2.6 E1_LOC

Description

The E1_LOC is an alarm indicating that the upstream 2M clock is lost. This alarm occurs whena tributary board fails to extract the clock from E1 signals.

Attribute



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 example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1 Indicates the ID of the tributary port (path) that reports the alarm. For example,0x01 indicates that the alarm is reported by port (path) 1 of the tributary board.


When E1_LOC occurs, the service is not affected.


Maintenance Guide


Issue 03 (2010-05-30)

Possible Causesl Cause 1: The opposite NE is faulty.

l Cause 2: The line sequence of the cable is incorrect.

l Cause 3: The IDU on the local NE is faulty.

l Cause 4: The input E1 signal has an abnormal waveform.

Procedure

Step 1 Cause 1: The opposite NE is faulty.(1) Rectify the fault on the opposite NE.

Step 2 Cause 2: The line sequence of the cable is incorrect.(1) Redo the cable.

Step 3 Cause 3: The IDU on the local NE is faulty.(1) Replace the IDU of the local site.

Step 4 Cause 4: The input E1 signal has an abnormal waveform.(1) Check whether any external interference causes the abnormal waveform of the E1 signal.

If... Then...

There is external interference The fault is rectified. End the alarm handling.

There is no external interference Contact Huawei engineers.

----End


A.2.7 ETH_CFM_MISMERGE

DescriptionThe ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm occurswhen the system receives the CCM packet whose MA ID mismatches or whose priority is lower.

Attribute


Critical Communication 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 thefollowing format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,



A-13

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning

Parameter 1, Parameter 2, Parameter 3,Parameter 4 (Port)

Indicate the ID of the port that reports the alarm.

Parameter 5, Parameter 6 (VLAN ID) Indicate the VLAN ID of the MEP.

Parameter 7 (Direction) Indicates the direction of the local MEP.l 0x00: The port is direction insensitive.

l 0x01: The port is in the ingress direction.

l 0x02: The port is in the egress direction.

Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00: consumer MEP level (low).

l 0x01: consumer MEP level (medium).

l 0x02: consumer MEP level (high).

l 0x03: provider MEP level (low).

l 0x04: provider MEP level (high).

l 0x05: operator MEP level (low).

l 0x06: operator MEP level (medium).

l 0x07: operator MEP level (high).NOTE

Consumer indicates the customer, provider indicatesthe supplier, and operator indicates the carrier.


The services among relevant standard MEPs may be interrupted or the data flow may beincorrectly routed.

Possible Causesl Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to are

inconsistent.

l Cause 2: The levels of the MDs that the standard MEPs correspond to are different.

l Cause 3: The physical connection is incorrect.

Procedure

Step 1 Cause 1: The names of the MDs and the MAs that the standard MEPs correspond to areinconsistent.

(1) Check whether the names of the MDs and the MAs that the standard MEPs correspond toare the same.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The MD names or MA names aredifferent

Re-configure the MA names and MA namesto ensure consistency at both ends.

The MD names or MA names are thesame at both ends

Go to Cause 2.

Step 2 Cause 2: The levels of the MDs that the standard MEPs correspond to are different.(1) Check whether the MD levels of the standard MEPs are the same.

If... Then...

The MD levels are different Re-configure the MD levels to ensureconsistency at both ends.

The MD levels are the same at both ends Go to Cause 3.

Step 3 Cause 3: The physical connection is incorrect.(1) Check the physical connection of the Ethernet service route and rectify the fault on the

physical connection if any.

----End


A.2.8 ETH_CFM_UNEXPERI

DescriptionThe ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs whenthe system receives invalid CCM packets.

Attribute


Minor Communication alarm


Name Meaning





A-15

Name Meaning














Impact on the Systeml The LB and LT detection functions of IEEE 802.1ag ETH-OAM are unavailable.

l The service may become abnormal due to the loop.

Possible Causesl Cause 1: No remote MEP is configured.

l Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, theconnectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.

l Cause 3: The service is looped back and the looped packet is received.

l Cause 4: A software fault occurs at the MEP at the transmit end.

Procedure

Step 1 Cause 1: No remote MEP is configured.(1) Check whether the remote MEP is configured. If not, configure the remote MEP first.

Step 2 Cause 2: The configuration of the MEPs at both ends are inconsistent. For example, theconnectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.(1) Check whether the CC periods set at the MEPs are the same.

If... Then...

The CC periods are different Change the CC periods to ensure consistency at bothends.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The CC periods are the same Go to the next step.

(2) Check whether the IDs of the MEPs in the maintenance domain are in conflict.

If... Then...

The IDs are in conflict Change the conflicting IDs.

The IDs are not in conflict Go to Cause 2.

Step 3 Cause 3: The service is looped back and the looped packet is received.(1) Enable the loop detection function of IEEE 802.3ah ETH-OAM. Check whether any loop

exists at each IP port of the service trail. If yes, release the loop and clear the alarm.

Step 4 Cause 4: A software fault occurs at the MEP at the transmit end.(1) Perform a warm reset on the Ethernet board where the remote MEP is located. For details,

see Warm Resetting.

----End


A.2.9 ETH_CFM_LOC

DescriptionThe ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs whenthe system fails to receive CCM packets from the remote MEP in 3.5 connectivity check (CC)periods successively.

Attribute




Name Meaning


Indicate the number of the port where the alarmis reported.




A-17

Name Meaning













Parameter 9, Parameter 10 (RMEPID) Indicate the ID of the remote MEP.

Impact on the Systeml The LB and LT detection functions of IEEE 802.1ag ETH-OAM are unavailable.l The services among 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 MEP

belongs is faulty.l Cause 3: Serious congestion occurs on the network.

ProcedureStep 1 Cause 1: The line between the local standard MEP and the remote standard MEP is interrupted.

(1) Check whether the physical links (such as cables or fibers) connecting the services at theMEPs of the two ends are correct.

If... Then...

The connection is not correct Re-connect the cables to rectify the faults on physicallinks.

The connection is correct Go to Cause 2.

Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEPbelongs is faulty.


Maintenance Guide


Issue 03 (2010-05-30)

(1) Check whether the Ethernet service in the maintenance association (MA) to which the localMEP belongs is configured correctly.

If... Then...

The connection is not correct Modify the configuration of the Ethernet services toensure consistency at both ends.

The connection is correct Go to Cause 3.

Step 3 Cause 3: Serious congestion occurs on the network.(1) Check the utilization of bandwidth. If the bandwidth is exhausted, increase the bandwidth

or eliminate the source that transmits a large amount of invalid data.

----End


A.2.10 ETH_CFM_RDI

DescriptionThe ETH_CFM_RDI is an alarm indicating CCM packets with RDI received from the remoteMEP. This alarm occurs when the system receives CCM packets with RDI from the remoteMEP.

Attribute




Name Meaning






A-19

Name Meaning

Parameter 7 (Direction) Indicate the direction of the local MEP.l 0x00: The port is direction insensitive.



Parameter 8 (Level) Indicates the MD level of the local MEP.l 0x00:0x00: consumer MEP level (low).









Parameter 9, Parameter 10 (RMEPID) Indicate the ID of the remote MEP.

Impact on the Systeml The LoopBack (LB) and LinkTrace (LT) detection functions of IEEE 802.1ag ETH-OAM

are unavailable.l The services among relevant standard MEPs may be interrupted.

Possible Causesl Cause 1: The remote MEP fails to receive correct CCM packets.

l Cause 2: The software is reset or another software fault occurs at the remote MEP.

Procedure

Step 1 Cause 1: The remote MEP fails to receive correct CCM packets.(1) Determine the port that reports the alarm according to the alarm parameters.(2) Check whether the remote MEP that is connected to the port reports the

ETH_CFM_LOC, ETH_CFM_MISMERGE, or ETH_CFM_UNEXPERI alarm.

If... Then...

Any of the preceding alarms occurs Clear the alarm at the remote end.

No such alarms occur Go to Cause 2.

Step 2 Cause 2: The software is reset or another software fault occurs at the remote MEP.(1) Check whether the equipment at the remote MEP is reset.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The equipment is reset Rectify the fault and then end the alarm handling.

The alarm is not reported Perform a warm reset on the board where the remote MEPis located. For details, see Warm Resetting.

----End


A.2.11 ETH_LOS

DescriptionThe ETH_LOS is an alarm indicating the loss of Ethernet port connection.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm. For example,0x01 indicates that the alarm is reported by Ethernet port 1 of theboard.

Parameter 2, Parameter 3 The values are always 0x00 0x01.

Impact on the SystemWhen the ETH_LOS alarm occurs, the service at the port that reports the alarm is interrupted.

Possible Causesl Cause 1: The negotiation fails because the transmit port and receive port work in different

modes.l Cause 2: The link of electrical cable or optical fiber is faulty.

l Cause 3: The equipment is faulty.



A-21

Procedure

Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different modes.(1) Check whether the transmit port and receive port work in the same mode.

If... Then...

The transmit port and receive port workin different modes

Correctly set the working modes of thetransmit port and receive port.

The transmit port and receive port workin the same mode

Go to Cause 2.

Step 2 Cause 2: The link of electrical cable or optical fiber is faulty.(1) Check the network cable or optical fiber connected to the port that reports the alarm.

If... Then...

The network cable is loose or damaged Connect the network cable properly orreplace the damaged network cable.

The connector of the fiber jumper is dirty Clean the connector.

The connector is loosely connected ordamaged

Insert the connector properly or replace thedamaged fiber jumper.

The connection is normal Go to Cause 3.

Step 3 Cause 3: The equipment is faulty.(1) Check whether any fault occurs on the equipment interconnected with the port that reports

the alarm.

If... Then...

The equipment is faulty Rectify the fault.

The equipment is normal Replace the IDU of the local site.

----End


A.2.12 ETHOAM_DISCOVER_FAIL

DescriptionThe ETHOAM_DISCOVER_FAIL is an alarm indicating that the point-to-point Ethernet OAMnegotiation fails. This alarm occurs when the OAM function is enabled at a port of a board andthe negotiation between the port and the opposite equipment fails.


Maintenance Guide


Issue 03 (2010-05-30)

Attribute


Minor Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the port that reports the alarm.


Parameter 4 Indicates the reason why the negotiation fails.

l 0x01: A fault occurs on the local receive link.

l 0x02: The local end fails to transmit OAM packets.

l 0x03: The OAM packets from the opposite end are not received.

l 0x04: The OAM configuration of the opposite end does not meetthe requirements of the local end.

l 0x05: The OAM configuration of the local end does not meet therequirements of the opposite end.

l 0x06-0xFF: Other unknown reasons.


The OAM function based on IEEE802.3ah is unavailable.

Possible Causesl Cause 1: The physical port of the local end is faulty.

l Cause 2: The P2P OAM protocol is not enabled at the opposite end.

l Cause 3: The OAM configuration at both ends is inconsistent.

Procedure

Step 1 Cause 1: The physical port of the local end is faulty.

(1) Check whether the physical port is faulty. Replace the IDU.

Step 2 Cause 2: The P2P OAM protocol is not enabled at the opposite end.



A-23

(1) Enable the P2P OAM protocol at the opposite end. For details, see Enabling the OAMAuto-Discovery Function.

Step 3 Cause 3: The OAM configuration at both ends is inconsistent.

(1) Reconfigure the P2P OAM protocol and ensure the consistency at both ends. For details,see Enabling the OAM Auto-Discovery Function.

----End

Related Information

None.

A.2.13 ETHOAM_RMT_CRIT_FAULT

Description

The ETHOAM_RMT_CRIT_FAULT is an alarm indicating that a critical fault occurs regardingthe point-to-point Ethernet OAM function at the remote end. This alarm occurs when a port withthe OAM function enabled receives the OAM packets that contain critical fault information fromthe opposite end.

Attribute



Parameters


Name Meaning



Parameter 4 Indicates the type of the fault.

l 0x01: A link fault occurs at the port of the opposite end.

l 0x02: Irrecoverable problems such as power failure occur at theopposite end.

l 0x03-0xFF: Other faults.


Maintenance Guide


Issue 03 (2010-05-30)


When the ETHOAM_RMT_CRIT_FAULT alarm occurs, the services on the link may beinterrupted.

Possible Causesl Cause 1: A link fault occurs at the remote MEP.

l Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.

l Cause 3: Other faults occur at the remote MEP.

Procedure

Step 1 Determine the fault type according to Parameter 4 and handle the fault accordingly.

If... Then...

The value of Parameter 4 is 0x01 Go to Cause 1.


The value of Parameter 4 is 0x03-0xFF, Go to Cause 3.

Step 2 Cause 1: A link fault occurs at the remote MEP.(1) Handle ETH_LOS of the remote port.

Step 3 Cause 2: Irrecoverable problems such as power failure occur at the remote MEP.(1) Handle the problems such as power failure at the remote MEP.

Step 4 Cause 3: Other faults occur at the remote MEP.(1) Contact Huawei technical support engineers.

----End

Related Information

None.

A.2.14 ETHOAM_RMT_LOOP

Description

The ETHOAM_RMT_LOOP is an alarm indicating that the point-to-point Ethernet OAMfunction detects a remote loopback. This alarm occurs when the local equipment initiates aremote loopback or responds to the remote loopback initiated by the opposite equipment.

Attribute





A-25


Name Meaning



Parameter 4 l 0x01: The local equipment initiates a remote loopback.

l 0x02: The local equipment responds to the remote loopbackinitiated by the opposite equipment.

Impact on the SystemWhen the ETHOAM_RMT_LOOP alarm occurs, the services on the link are interrupted.

Possible Causesl Cause 1: The local end issues a loopback command and the opposite end responds to the

command.l Cause 2: The opposite end issues a loopback command and the local end responds to the

command.

Procedure

Step 1 Check whether the loopback is initiated by the local end or by the remote end.

Step 2 Cause 1: The local end issues a loopback command and the opposite end responds to thecommand.(1) Determine the causes of the loopback at the local end and release the loopback.

Step 3 Cause 2: The opposite end issues a loopback command and the local end responds to thecommand.(1) Determine the causes of the loopback at the opposite end and release the loopback.

----End



Maintenance Guide


Issue 03 (2010-05-30)

A.2.15 ETHOAM_RMT_SD

DescriptionThe ETHOAM_RMT_SD is an alarm indicating that the point-to-point Ethernet OAM functiondetects signal degradation at the remote end. This alarm occurs when a port with the OAMfunction enabled receives link event notification packets from the opposite end.

Attribute




Name Meaning



Parameter 4 Indicates the type of the received link event:

l 0x01: Errored frame event

l 0x02: Errored frame period event

l 0x03: Errored frame second event

Impact on the SystemWhen the ETHOAM_RMT_SD alarm occurs, the performance of services degrade.

Possible Causesl Cause 1: The link event notification function is enabled at the opposite end.

l Cause 2: The link performance thresholds of the opposite end are inappropriate.

l Cause 3: The link performance deteriorates.

Procedure

Step 1 Cause 1: The link event notification function is enabled at the opposite end.(1) Check whether the link event notification function is enabled at the opposite end.



A-27

If... Then...

The link event notification function isenabled at the opposite end

Disable the link event notification functionat the opposite end.

The link event notification function isdisabled at the opposite end

Go to Cause 2.

Step 2 Cause 2: The link performance thresholds of the opposite end are inappropriate.(1) Check whether the link performance thresholds of the opposite end are appropriate.

If... Then...

The link performance thresholds of theopposite end are inappropriate

Set the thresholds to appropriate values.

The link performance thresholds of theopposite end are appropriate

Go to Cause 3.

Step 3 Cause 3: The link performance deteriorates.(1) Improve the link performance at the opposite end so that the opposite end does not send

any link event packet to the local end. Then, the ETHOAM_RMT_SD alarm at the localend clears automatically.

----End

Related Information

None.

A.2.16 ETHOAM_SELF_LOOP

Description

The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs thepoint-to-point OAM protocol. This alarm occurs when the MAC port of a board receives theOAM protocol packets sent by the port or the board after the loopback detection function isenabled.

Attribute


Major Environmental alarms

Parameters



Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 1 Indicates the port ID.


Parameter 4 Indicates the loopback type.

l 0x01: self-loop of the port.

l 0x02: self-loop of the board.

l 0x03-0xFF: unknown types.

Impact on the SystemA network storm may occur owing to the loopback.

Possible Causesl Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN

that has a loopback, or a PHY/MAC loopback is manually configured at the port.l Cause 2: Two ports of the board are connected through cables or two ports of the board are

accessed to the same LAN.

Procedure

Step 1 Determine the loopback type according to Parameter 4, and then handle the loopbackaccordingly.

If... Then...



Step 2 Cause 1: The cable connected to the port is self-looped, or the port is accessed to a LAN thathas a loopback, 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 (orwait five minutes for the automatic release bythe NMS). Then, the self-loop is released.

A self-loop is performed at the cables of theport

Reconnect the cables to release the self-loop.

The port is accessed to a LAN with a self-loop

Release the loopback of the LAN, ordisconnect the port from the LAN.

Step 3 Cause 2: Two ports of the board are connected through cables or two ports of the board areaccessed to the same LAN.(1) Check whether two ports of the board are connected through cables or whether two ports

of the board are accessed to the same LAN.



A-29

If... Then...

The two ports are connected throughcables

Disconnect the cables to release the self-loop.

The two ports are accessed to the sameLAN

Disconnect a port from the LAN to releasethe self-loop.

----End

Related Information

None.

A.2.17 EX_ETHOAM_CC_LOS

Description

The EX_ETHOAM_CC_LOS is an alarm indicating the loss of periodic connectivity check(CC) packets. This alarm occurs when the sink MEP fails to receive CC packets from the samesource MEP in a period (3.5 transmission periods of CC packets at the source MEP).

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the MEP that reports the alarm.

Parameter 2, Parameter 3 Indicates the number of the Ethernet port that reports the alarm.

l Port number: 0x0001-0x0000 + MAX_ETH_PORT.

l VCTRUNK port number: 0x8001-0x8000 +MAX_ETH_VCTRUNK.

NOTE

l MAX_ETH_PORT indicates the maximum MAC port numbersupported by a board.

l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK portnumber supported by a board.


Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from0x0000 to 0x0FFF.

l For a service without any VLAN tag, the VLAN ID is 0xFFFF.

Parameter 6 Indicates the maintenance domain level.



l 0x02: consumer MEP level (low).



l 0x05: operator MEP level (high).


l 0x07: operator MEP level (low).NOTE

Consumer indicates the customer, provider indicates the supplier, andoperator indicates the carrier.

Parameter 7 Indicates the source MEP ID of CC packets.

Parameter 8 Indicates the sink MEP ID of CC packets.

NOTEThe sink MEP ID of CC packets is the ID of the MEP that reports the alarm.Parameter 1 and Parameter 8 indicate the same information.

Impact on the SystemA unidirectional connectivity failure occurs in the Ethernet service between two MEPs.

Possible Causesl Cause 1: The line between two MEPs is interrupted.

l Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.

l Cause 3: The services between two MEPs are congested or interrupted.

Procedure

Step 1 Cause 1: The line between two MEPs is interrupted.(1) Check whether the physical links (such as network cables or optical fibers) that carry

services between the two MEPs are correctly connected.



A-31

If... Then...

The physical links are incorrectlyconnected

Re-connect the cables to rectify the faultson physical links.

The physical links are correctly connected Go to Cause 2.

Step 2 Cause 2: The Ethernet services in the MA to which the alarmed MEP belongs are faulty.

(1) Check whether the Ethernet services in the MA to which the alarmed MEP belongs areconfigured correctly.

If... Then...

The Ethernet services are configuredincorrectly

Change the configuration and ensureconsistency at both ends.

The Ethernet services are configuredcorrectly

Go to Cause 3.

Step 3 Cause 3: The services between two MEPs are congested or interrupted.

(1) Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth oreliminate any source that transmits a large amount of invalid data.

----End

Related Information

None.

A.2.18 EX_ETHOAM_MPID_CNFLCT

Description

The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the conflict of MPIDs. This alarmoccurs when two MEPs on one MD have the same maintenance point identity (MPID) and oneMEP receives the packets from the other MEP.

Attribute


Major Environment alarm

Parameters



Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 1 Indicates the MPID associated with the alarm.

Parameters 2, Parameter 3 Indicate the number of the Ethernet port that reports the alarm.

l MAC port number: 0x0001-0x0000 + MAX_ETH_PORT.

l VCTRUNK port number: 0x8001-0x8000 +MAX_ETH_VCTRUNK.

NOTE

l MAX_ETH_PORT indicates the maximum MAC port numbersupported by a board.

l MAX_ETH_VCTRUNK indicates the maximum VCTRUNK portnumber supported by a board.

Parameters 4, Parameter 5 Indicate the service VLAN ID.

l For a service with a VLAN tag, the VLAN ID ranges from0x0000 to 0x0FFF.

l For a service without any VLAN tag, the VLAN ID is 0xFFFF.

Parameter 6 Indicates the maintenance domain level.

l 0x00: Consumer MEP level (high).

l 0x01: Consumer MEP level (middle).

l 0x02: Consumer MEP level (low).

l 0x03: Provider MEP level (high).

l 0x04: Provider MEP level (low).

l 0x05: Operator MEP level (high).

l 0x06: Operator MEP level (medium).

l 0x07: Operator MEP level (low).NOTE

Consumer indicates the customer, provider indicates the supplier, andoperator indicates the carrier.

Parameter 7 Indicates the ID of the local MEP.

NOTEThe ID of the local MEP is the ID of the MEP that reports the alarm.Parameter 1 and Parameter 7 indicate the same information.

Impact on the SystemMPIDs must be unique on a network. When the EX_ETHOAM_MPID_CNFLCT alarm occurs,the LB and LT functions are abnormal and OAM packets are received incorrectly.

Possible CausesCause 1: At least two MEPs in an MD have the same MPID.



A-33

Procedure

Step 1 Cause 1: At least two MEPs in an MD have the same MPID.(1) Check this alarm on the NMS. Determine the associated MPID according to Parameter 1.(2) Query the information about the MEP. Delete the incorrect MEPs and create MEPs with

unique MPIDs.

----End

Related Information

None.

A.2.19 FLOW_OVER

Description

The FLOW_OVER is an alarm indicating that the data flow received by the Ethernet port exceedsthe threshold.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the path that reports the alarm.

Parameter 2 Indicates the ID of the subboard.

Parameter 3 Indicates the port ID. For example, 0x01 indicates that the alarm is reported byEthernet port 1 of the board.


When the FLOW_OVER alarm occurs, the extra data may be discarded by the port.

Possible Causes

Cause 1: The opposite end transmits excessive data flow.


Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Cause 1: The opposite end transmits excessive data flow.(1) Configure the QoS policies at the opposite end to reduce the data flow that the opposite

end transmits to the local end.

----End


A.2.20 HARD_BAD

DescriptionThe HARD_BAD is an alarm indicating hardware errors.

Attribute


Critical Equipment alarm




A-35

Name Meaning

Parameter 1 Indicates the cause of the fault.l 0x01: The power module is working abnormally.

l 0x02: The board is installed improperly.

l 0x03: 38 MHz system clock 1 is abnormal.

l 0x04: 38 MHz system clock 2 is abnormal.

l 0x05: 2 MHz clock source is abnormal.

l 0x06: The digital phase-locked loop is abnormal.

l 0x07: The 38 MHz service clock is lost.

l 0x08: The bus is abnormal.

l 0x09: The TPS protection board is abnormal.

l 0x0A: The primary crystal oscillator stops oscillating.

l 0x0B: The frequency offset of the primary crystal oscillator is excessive.

l 0x0C: The secondary crystal oscillator stops oscillating.

l 0x0D: The processor (CPU/DSP/coprocessor) is faulty.

l 0x0E: The storage components are faulty.

l 0x0F: The programmable logic device is faulty.

l 0x10: The SDH components are faulty.

l 0x11: The data communication components are faulty.

l 0x12: The clock components are faulty.

l 0x13: The interface components are faulty.

l 0x14: The power components are faulty.

l 0x15: Another fault occurs.

l 0x16: The analog phase-locked loop is abnormal.

l 0x17: The 32 MHz clock is unavailable.



Impact on the SystemThe board that reports the alarm fails to work. If the board is configured with 1+1 protection,the protection switching may be triggered.

Possible CausesCause of the alarm reported by a board of the IDU: The IDU is faulty.

Cause of the alarm reported by a board of the ODU: The ODU is faulty.


Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Cause of the alarm reported by a board of the IDU: The IDU is faulty.(1) Power on the IDU again.

If... Then...

The alarm disappears after the IDU ispowered on

The fault is rectified. End the alarmhandling.

The alarm persists after the IDU ispowered on

Go to the next step.


Step 2 Cause of the alarm reported by a board of the ODU: The ODU is faulty.(1) Replace the ODU that reports the alarm. For details, see 6.2 Replacing an ODU.

----End


A.2.21 IF_CABLE_OPEN

DescriptionThe IF_CABLE_OPEN is an alarm indicating that the IF cable is open-circuited.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by IF port 1 of the corresponding board.

Impact on the SystemThe services on the IF port are interrupted.



A-37

Possible Causes

l Cause 1: The IF cable is loose or faulty.

l Cause 2: The IF port of the IDU is damaged.

l Cause 3: The power module of the ODU is faulty.

Procedure

Step 1 Cause 1: The IF cable is loose or faulty. Check whether the connector of the IF cable is loose orwhether the connector is not made properly.

(1) Check whether the connector of the IF cable is loose or whether the connector is not madeproperly.

The connectors to be checked include the connector between the IF fiber jumper and theIF board, the connector between the IF fiber jumper and the IF cable, and the connectorbetween the IF cable and the ODU.

If... Then...

The connector is loose Connect the connector tightly.

The connector is not made properly Make a new IF cable connector.

None of the above Go to the next step.

(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged, and test theconnectivity between the IF fiber jumper and the IF cable. For details, see Testing theconnectivity between cables.

If... Then...

The cable does not meet the specifiedrequirement

Replace the cable with a proper one.

The cable meets the specified requirement Go to Cause 2 or Cause 3.

Step 2 Cause 2: The IF port of the IDU is damaged.


Step 3 Cause 3: The power module of the ODU is faulty.

(1) Replace the ODU connected to the IF board that reports the alarm.

----End

Related InformationNOTEWhen rectifying the faults on the IF cable, IF port, and ODU, you must turn off the ODU before theoperation. You can turn on the ODU only after the operation is complete.

A.2.22 IF_INPWR_ABN


Maintenance Guide


Issue 03 (2010-05-30)

DescriptionThe IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.

Attribute




Name Meaning

Parameter 1 l 0x01: Indicates that the input power of the ODU is over high.

l 0x02: Indicates that the input power of the ODU is over low.

Impact on the SystemThe services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switchingmay be triggered.

Possible Causesl Cause 1: The IDU is faulty.

l Cause 2: The IF cable is faulty.

l Cause 3: The ODU is faulty.

Procedure

Step 1 Cause 1: The IDU is faulty.(1) Replace the IDU.

Step 2 Cause 2: The IF cable is faulty.(1) Check whether the connector of the IF cable is loose or whether the connector is not made

properly.

The connectors to be checked include the connector between the IF fiber jumper and theIF board, the connector between the IF fiber jumper and the IF cable, and the connectorbetween the IF cable and the ODU.

If... Then...

The connector is loose Connect the connector tightly.

The connector is not made properly Terminating the IF Cable with Connectors again.



A-39

If... Then...

None of the above Go to the next step.

(2) Check whether the surface of the IF fiber jumper and the IF cable is damaged or deformed,and test the connectivity between the IF fiber jumper and the IF cable. For details, seeTesting the Connectivity of the IF Cable.

If... Then...

The cable does not meet the specifiedrequirement

Replace the cable with a proper one.

The cable meets the specified requirement The IF board or ODU may be faulty.

Step 3 Cause 3: The ODU is faulty.(1) Replace the ODU that reports the alarm.

----End

Related Information

The number of the logical slot for the ODU is the slot number of the IF board connected to theODU plus 10.

A.2.23 LAG_PORT_FAIL

Description

The LAG_PORT_FAIL is an alarm indicating that a port in the LAG of the Ethernet fails. Thisalarm occurs when a port in the LAG is unavailable.

Attribute


Minor Processing alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the IP port.



Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 4 Indicates the cause of the protection failure.

l 0x01: Indicates that the link of the port is faulty or fails.

l 0x02: Indicates that the port is in half-duplex mode.

l 0x03: Indicates that the port fails to receive LACP packets.

l 0x04: Indicates that the port detects a self-loop.

l 0x05: Indicates other unknown reasons.

Parameter 5 The value is always 0xff.

Impact on the SystemThe port in the LAG cannot share the service load, or the port does not transmit or receive anyservices.

Possible Causesl Cause 1: The port is disabled or the link is faulty.

l Cause 2: The port is in the half-duplex mode.

l Cause 3: The port fails to receive LACP packets.

l Cause 4: The port detects a self-loop.

l Cause 5: other unknown reasons.

Procedure

Step 1 Determine the port where the alarm occurs and the alarm cause based on the alarm parameter.

If... Then...






Step 2 Cause 1: The port is disabled or the link is faulty.(1) On the NMS, check whether the port in the LAG is enabled.

If... Then...

The port is not enabled Enable the port in the LAG group.

The port is enabled Check the link state of each port. If any link is faulty, rectifythe fault.

Step 3 Cause 2: The port is in the half-duplex mode.



A-41

(1) On the NMS, check the working mode of the port in the LAG group. If the port is in half-duplex mode, change the working mode of the port into full-duplex.

Step 4 Cause 3: The port fails to receive the LACP packets.(1) On the NMS, check whether the LAG group is properly configured on the opposite end.

If... Then...

The LAG group is not properly configured Reconfigure the LAG group.

The LAG group is properly configured Go to the next step.

(2) Check whether the local port and the remote port transmit the LACP packets. If the LACPpackets are not transmitted, configure the ports at both ends to ensure that the packets canbe normally transmitted.

Step 5 Cause 4: The port detects a self-loop.(1) Release the self-loop of the port.

Step 6 Cause 5: other unknown reasons(1) Contact Huawei engineers to handle the fault.

----End


A.2.24 LOOP_ALM

DescriptionThe LOOP_ALM is an alarm indicating that a loopback event occurs.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the line port that reports the alarm. For example,0x01 indicates that the alarm is reported by port 1 of thecorresponding board.


Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm.

Parameter 4 Indicates the type of loopback.

l 0x00: Indicates optical/electrical port inloop.

l 0x01: Indicates optical/electrical port outloop.

l 0x02: Indicates path inloop.

l 0x03: Indicates path outloop.

l 0x04: Indicates loopback on the user side.

l 0x05: Indicates loopback on the combination wave side.

l 0x06: Indicates SPI inloop.

l 0x07: Indicates SPI outloop.

l 0x08: Indicates ATM layer inloop.

l 0x09: Indicates ATM layer outloop.

l 0x0A: Indicates PHY layer inloop.

l 0x0B: Indicates PHY layer outloop.

l 0x0C: Indicates MAC layer inloop.

l 0x0D: Indicates MAC layer outloop.

l 0x0E: Indicates VC-4 timeslot inloop.

l 0x0F: Indicates VC-4 timeslot outloop.

l 0x10: Indicates VC-3 timeslot inloop.

l 0x11: Indicates VC-3 timeslot outloop.

l 0x12: Indicates VC-12 timeslot inloop.

l 0x13: Indicates VC-12 timeslot outloop.

l 0x14: Indicates IF outloop.

l 0x15: Indicates IF inloop.

l 0x16: Indicates RF inloop.

l 0xFF: Indicates any of the preceding loopback modes.

Impact on the SystemThe loopback port or path fails to transmit services.

Possible CausesLoopback is performed at the local site.

Procedure

Step 1 Cause: Loopback is performed at the local site.(1) Determine the type of loopback based on the alarm parameters.



A-43

(2) Find out the cause of loopback, and set the loopback status of the port that reports the alarmto Non-Loopback.

For more information about the loopback operation, see 7.5 Software loopback.

----End


A.2.25 MSSW_DIFFERENT

DescriptionThe MSSW_DIFFERENT is an alarm indicating that the master and slave software areasmismatches with each other. This alarm occurs when the NE detects that the first software systemand the second software system of the system control, cross-connect, and timing board mismatchwith each other.

Attribute




Name Meaning

Parameter 1 Indicates the location of the file.l 0x01: Indicates the files in the flash memory

l 0x02: Indicates the software that is currently running


Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning

Parameter 2, Parameter 3 Indicate the IDs of the inconsistent files on the system controlboard.l 0x01: FPGA of the system control board in ofs1

l 0x02: FPGA of the system control board in ofs2

l 0x03: ofs1/hwx/nesoft.hwx

l 0x04: ofs2/hwx/nesoft.hwx

l 0x05: ofs1/hwx/ne.ini

l 0x06: ofs2/hwx/ne.ini

l 0x07: ofs1/hwx/ocp.ini

l 0x08: ofs2/hwx/ocp.ini

l 0x09: ofs1/fpga/if1_002.pga

l 0x0a: ofs2/fpga/if1_002.pga

l 0x0b: ofs1/fpga/if1_250.pga

l 0x0c: ofs2/fpga/if1_250.pga

l 0x0d: ofs1/fpga/sl1d.pga

l 0x0e: ofs2/fpga/sl1d.pga

l 0x0f: ofs1/fpga/sl91ifu2.pga

l 0x10: ofs2/fpga/sl91ifu2.pga

l 0x11: ofs1/fpga/sl91ifx2.pga

l 0x12: ofs2/fpga/sl91ifx2.pga

l 0x13: ofs1/fpga/sl91aux.pga

l 0x14: ofs2/fpga/sl91aux.pga

l 0x15: ofs1/hwx/lusoft.hwx

l 0x16: ofs2/hwx/lusoft.hwx

l 0x17: ofs1/hwx/lusoft.ini

l 0x18: ofs2/hwx/lusoft.ini

l 0x19: ofs1/fpga/sl91em6t.pga

l 0x1a: ofs2/fpga/sl91em6t.pga

l 0x1b: ofs1/fpga/pvg610.pga

l 0x1c: ofs2/fpga/pvg610.pga

l 0x1d: ofs1/fpga/pvg610x.pga

l 0x1e: ofs2/fpga/pvg610x.pga



A-45

Name Meaning

Parameter 4, Parameter 5 Indicate the cause of the alarm.l 0x04: The file versions in the master and slave areas of a single

system control board are inconsistent.l 0x08: The file versions in the active and standby system control

boards are inconsistent, or that the files in the correspondingdirectories of the active and standby system control boards havedifferent names.

l 0x0c: The file versions in the master and slave areas of a singlesystem control board are inconsistent and the file versions on theactive and standby system control boards are also inconsistent.

Impact on the SystemIf the currently running software is lost, the backup software fails to take over. If no NE softwareexists in the flash memory, the system is unable to restart after power-off or reset.

Possible CausesCause 1: An exception occurs during the software loading.

ProcedureStep 1 Cause 1: An exception occurs during the software loading.

(1) Contact Huawei engineers to re-load the software.

----End


A.2.26 MW_BER_EXC

DescriptionThe MW_BER_EXC is an alarm indicating that there are excessive bit errors on the radio link.This alarm occurs when the bit errors on the radio link exceed the specified threshold (10-3 bydefault).

Attribute


Minor Service 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


Maintenance Guide


Issue 03 (2010-05-30)

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path that reports the alarm. For example, 0x000x01 indicate that the alarm is reported in path 1.


The services on the port are interrupted.

Possible Causesl Cause 1: Signal attenuation on the radio link is too heavy.

l Cause 2: The transmit unit at the opposite site is faulty.

l Cause 3: The receive unit at the local site is faulty.

Procedure

Step 1 Cause 1: Signal attenuation on the radio link is too heavy.

(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.

Step 2 Cause 2: The receive unit at the local site is faulty.

(1) Replace the IDU at the local site.

Step 3 Cause 3: The transmit unit at the opposite site is faulty.

(1) Replace the IDU at the opposite site.

----End

Related Information

None.

A.2.27 MW_BER_SD

Description

The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarmoccurs when the bit errors on the radio link exceed the specified threshold (10-6 by default) butdoes not reach the MW_BER_EXC alarm threshold (10-3 by default).



A-47

Attribute


Minor Service alarm


Name Meaning



Impact on the SystemThe service performance on the port deteriorates. If the equipment is configured with 1+1 FD/SD protection, HSM channel switching may be triggered.

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.

ProcedureStep 1 Cause 1: Signal attenuation on the radio link is too heavy.

(1) Check whether the MW_FEC_UNCOR alarm is reported. If so, clear the alarm.

Step 2 Cause 2: The receive unit at the local site is faulty.(1) Replace the IDU at the local site.

Step 3 Cause 3: The transmit unit at the opposite site is faulty.(1) Replace the IDU at the opposite site.

----End


A.2.28 MW_FEC_UNCOR


Maintenance Guide


Issue 03 (2010-05-30)

DescriptionThe MW_FEC_UNCOR alarm indicates that microwave frames forward error correction (FEC)encoding cannot be corrected.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicatesthat the alarm is reported by port 1 of the corresponding board.

Impact on the SystemBit errors occur in the services. If the equipment is configured with 1+1 FD/SD protection, HSMchannel protection switching may be triggered.

Possible Causesl Cause 1: The receive power of the ODU is abnormal.



l Cause 4: An interference event occurs.

Procedure

Step 1 Cause 1: The receive power of the ODU is abnormal.(1) Check whether the receive power of the ODU at the local site is normal. If yes, determine

the abnormality and take proper measures. For details, see Querying History TransmitPower and Receive Power.



A-49

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth angle of the antenna meets therequirement.

2. Check the antenna direction. Check whetherthe received signal is from the main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check whether the setting of the polarizationdirection of the antenna is correct. Adjust theincorrect polarization direction.

4. Check whether the antenna gain at both thetransmit and receive ends meets thespecifications. Replace the antennas that donot meet the requirement.

5. Check whether any mountain or buildingobstacle exists in the transmit direction.If yes, contact the network planningdepartment for proper modification of theplanning design, hence preventing the blockof the mountain or building obstacle.

The RSL is higher than the specified RSLof the network. The offset value is tens ofdecibles. The duration is from tens ofseconds to several hours

Slow up fading occurs. Follow the steps:

1. Check whether any co-channel interferenceoccurs.a. Mute the ODU at the opposite end. For

details, seeConfiguring the IF/ODUInformation of a Radio Link.

b. Check the RSL at the local end. For details,seeConfiguring the IF/ODU Information ofa Radio Link. If the RSL exceeds -90 dBm,you can infer that there is co-channelinterference that may affect the long-termavailability and errored-secondperformance of the system.

2. Use a spectrum analyzer to analyze theinterference source.

3. Contact the spectrum managementdepartment to clear the interference spectrumor change plans to minimize the interference.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibles. The duration is from tens ofseconds to several hours

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow fading is imposed by the transmission path.Contact the network planning department tomake the following changes:

l Increase the installation height of the antenna.




If the RSL is lower than or higher thanthe specified RSL of the network and ifthe duration is from several millisecondsto tens of seconds

Fast fading occurs. Contact the network planningdepartment to make the following changes:

l Adjust the position of the antenna to block thereflected wave or make the reflection point fallon the ground that has a small reflectioncoefficient, thus reducing the multipathfading.

l Adjust the RF configuration to make the linksin the 1+1 SD configuration.

l If the links are in the 1+1 SD configuration,adjust the height offset between two antennasto make the receive power of one antennamuch stronger than the receive power of theother antenna.

l Increase the fading margin.

Step 2 Cause 2: The transmit unit of the opposite 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 opposite end. For details, see 7.5.2 Setting Loopbackfor the IF Port. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...

The alarm persists Replace the IDU.

The alarm clears Go to the next step.

(2) Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does notmeet the requirement.

(4) Then, check whether the alarm clears.

If... Then...

The alarm persists Replace the ODU at the opposite site.



A-51

If... Then...

The alarm clears End the alarm handling.

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.5.2 Setting Loopbackfor the IF Port. Check whether the fault at the opposite end is rectified after the loopback.

If... Then...



(2) Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

(3) Check whether the IF cable is soggy, broken, or pressed. Replace the cable that does notmeet the requirement.

(4) Then, check whether the alarm clears.

If... Then...

The alarm persists Replace the ODU of the local site.

The alarm clears End the alarm handling.

Step 4 Cause 4: An interference event occurs.

(1) Check whether any co-channel interference occurs.

a. Mute the opposite ODU.

b. Check the RSL at the local end. For details, see Configuring the IF/ODU Informationof a Radio Link. If the RSL exceeds -90 dBm, you can infer that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.

(2) Check whether any adjacent channel interference occurs.

a. Mute the opposite ODU.

b. Adjust the radio working mode at the local end and use the minimum channel spacing.For details, see Configuring the IF/ODU Information of a Radio Link.

c. Decrease the received frequency at the local end by a half of the channel spacing. Fordetails, see Configuring the IF/ODU Information of a Radio Link.

d. Test and record the RSL.

e. Increase the received frequency at the local end, with a step length of 0.5 MHz or 1MHz, and record the RSL accordingly until the received frequency is equal to theoriginal received frequency plus a half of the channel spacing.

f. Compare the recorded RSLs, and check whether the RSL in a certain spectrum isabnormal if the received frequency is within the permitted range.

(3) Use a spectrum analyzer to analyze the interference source.


Maintenance Guide


Issue 03 (2010-05-30)

(4) Contact the spectrum management department to clear the interference spectrum or changeplans to minimize the interference.

----End

Related Information

None.

A.2.29 MW_LIM

Description

The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. Thisalarm occurs when the IDU detects that the link ID in the microwave frame overheads isinconsistent with the specified link ID.

Attribute



Parameters


Name Meaning



After reporting the MW_LIM alarm, the IDU inserts the AIS alarm to the received signals. Then,the services on the radio link are interrupted. If the services are configured with SNCP, theprotection switching may be triggered.

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 configurationof the radio link receive frequency at the local or opposite site.

l Cause 3: The antenna receives microwave signals from the other site, because the directionof the antenna is set incorrectly.



A-53

Procedure

Step 1 Determine the IF port that reports the alarm based on the alarm parameters.

Step 2 Cause 1: The link ID of the local site does not match the link ID of the opposite site.

(1) Check whether the link ID of the local site matches with the link ID of the opposite site.For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the linkIDs at both ends to the same according to the network planning.

Step 3 Cause 2: The services on other radio links are received due to the incorrect configuration of theradio link receive frequency at the local or opposite site.

(1) Check whether the receive and transmit frequencies of the local site are consistent with thereceive and transmit frequencies of the opposite site. For details, see Configuring the IF/ODU Information of a Radio Link. If not, set the receive and transmit frequencies of thetwo sites again according to the network planning.

Step 4 Cause 3: The antenna receives microwave signals from the other sites, because the direction ofthe antenna is set incorrectly.

(1) Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.

----End

Related Information

The MW_LIM alarm is generated due to the inconsistency between the specified link ID andthe received link ID. When the MW_LOF alarm is generated on the link, the received link IDis a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressedby the MW_LOF alarm.

A.2.30 MW_LOF

Description

The MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.

Attribute



Parameters



Maintenance Guide


Issue 03 (2010-05-30)

Name Meaning



The services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl Cause 1: The other alarms are generated.

l Cause 2: In the case of TDM radio services, the IF working modes at the local site and theopposite site are different. In the case of Hybrid radio services, the channel bandwidth andmodulation modes at the local site and the opposite site are different.

l Cause 3: The working frequency of the ODU at the local site is inconsistent with theworking frequency of the ODU at the opposite site.



l Cause 6: The receive power of the ODU is abnormal.

l Cause 7: An interference event occurs.

Procedure

Step 1 Cause 1: The other alarms are generated.

(1) Check whether any alarms are generated in the equipment at the local site. If yes, takepriority to clear them.The relevant alarms are as follows:

l HARD_BAD

l VOLT_LOS

l IF_CABLE_OPEN

l BD_STATUS

l RADIO_RSL_LOW

l CONFIG_NOSUPPORT

l TEMP_ALARM

Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and theopposite site are different. In the case of Hybrid radio services, the channel bandwidth andmodulation modes at the local site and the opposite site are different.

(1) In the case of TDM radio services, check whether the working mode of the IF board at thelocal site is consistent with the working mode of the IF board at the opposite site. For details,see Configuring the IF/ODU Information of a Radio Link. If not, reset the working modeof the IF board according to the network planning.



A-55

In the case of Hybrid radio services, check whether the channel bandwidth and modulationmodes are the same at both ends. If not, change the channel bandwidth and modulationmodes according to the network planning. For details, see Setting the Hybrid/AM Attribute.

Step 3 Cause 3: The working frequency of the ODU at the local site is inconsistent with the workingfrequency of the ODU at the opposite site.(1) Ensure that the type of the ODU at the local site is consistent with the type of the ODU at

the opposite site.(2) Reset the working frequency of the ODU according to the network planning. For details,

see Setting Parameters of ODU Interfaces.Set the value of the transmit frequency of the local site the same as the value of the receivefrequency of the opposite site. Then, set the value of the receive frequency of the local sitethe same as the value of the transmit frequency of the opposite site.

Step 4 Cause 4: The transmit unit of the opposite site is faulty.(1) Check whether any alarms are generated in the equipment of the local site. If yes, take

priority to clear them.The relevant alarms are as follows:l HARD_BAD

l BD_STATUS

l VOLT_LOS

l IF_CABLE_OPEN

l RADIO_MUTE

l RADIO_TSL_HIGH

l RADIO_TSL_LOW

l TEMP_ALARM

(2) Locate the fault by looping back the opposite site.

Follow the steps:

a. Perform an inloop on the IF port at the opposite end. For details, see 7.5.2 SettingLoopback for the IF Port. Check whether the fault at the opposite end is rectifiedafter the loopback.

If... Then...



b. Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that doesnot meet the requirement.

d. Then, check whether the alarm clears.

Step 5 Cause 5: The receive unit of the local site is faulty.(1) Locate the fault by looping back the opposite site.

Follow the steps:


Maintenance Guide


Issue 03 (2010-05-30)

a. Perform an inloop on the IF port at the local end. For details, see 7.5.2 SettingLoopback for the IF Port. Check whether the fault at the opposite end is rectifiedafter the loopback.

If... Then...



b. Check whether the cable connector workmanship meets the requirement. If any cableconnector does not meet the requirement, make a new connector.

c. Check whether the IF cable is soggy, broken, or pressed. Replace the cable that doesnot meet the requirement.

d. Then, check whether the alarm clears.

Step 6 Cause 6: The receive power of the ODU is abnormal.(1) Check whether the receive power of the ODU at the local site is abnormal. If yes, determine

the abnormality and take proper measures. For details, see 7.3.7 Browsing the HistoryPerformance.

If... Then...

The RSL is lower than the receiversensitivity

Follow the steps:

1. Check the installation of the antenna to ensurethat the azimuth angle of the antenna meets therequirement.

2. Check the antenna direction. Check whetherthe received signal is from the main lobe.If the antenna direction does not meet therequirement, adjust the antenna in a widerange.

3. Check whether the setting of the polarizationdirection of the antenna is correct. Adjust theincorrect polarization direction.

4. Check whether the antenna gain at both thetransmit and receive ends meets thespecifications. Replace the antennas that donot meet the requirement.

5. Check whether any mountain or buildingobstacle exists in the transmit direction.If yes, contact the network planningdepartment for proper modification of theplanning design, hence preventing the blockof the mountain or building obstacle.



A-57

If... Then...

The RSL is higher than the specified RSLof the network. The offset value is tens ofdecibles. The duration is from tens ofseconds to several hours

Slow up fading occurs. Follow the steps:

1. Check whether any co-channel interferenceoccurs.a. Mute the ODU at the opposite end. For

details, see Configuring the IF/ODUInformation of a Radio Link.

b. Check the RSL at the local end. For details,see Configuring the IF/ODU Information ofa Radio Link. If the RSL exceeds -90 dBm,you can infer that there is co-channelinterference that may affect the long-termavailability and errored-secondperformance of the system.

2. Use a spectrum analyzer to analyze theinterference source.

3. Contact the spectrum managementdepartment to clear the interference spectrumor change plans to minimize the interference.

The RSL is lower than the specified RSLof the network. The offset value is tens ofdecibles. The duration is from tens ofseconds to several hours

Slow down fading occurs. Generally, the radiolink may be faulty in both directions, becauseslow fading is imposed by the transmission path.Contact the network planning department tomake the following changes:

l Increase the installation height of the antenna.




If the RSL is lower than or higher thanthe specified RSL of the network and ifthe duration is from several millisecondsto tens of seconds

Fast fading occurs. Contact the network planningdepartment to make the following changes:

l Adjust the position of the antenna to block thereflected wave or make the reflection point fallon the ground that has a small reflectioncoefficient, thus reducing the multipathfading.

l Adjust the RF configuration to make the linksin the 1+1 SD configuration.

l If the links are in the 1+1 SD configuration,adjust the height offset between two antennasto make the receive power of one antennamuch stronger than the receive power of theother antenna.

l Increase the fading margin.


Maintenance Guide


Issue 03 (2010-05-30)

Step 7 Cause 7: An interference event occurs.

Follow the steps:

(1) Check whether any co-channel interference occurs.

a. Mute the opposite ODU.b. Check the RSL at the local end. For details, see Configuring the IF/ODU Information

of a Radio Link. If the RSL exceeds -90 dBm, you can infer that there is co-channelinterference that may affect the long-term availability and errored-secondperformance of the system.

(2) Check whether any adjacent channel interference occurs.

a. Mute the opposite ODU.b. Adjust the radio working mode at the local end and use the minimum channel spacing.

For details, see Configuring the IF/ODU Information of a Radio Link.c. Decrease the received frequency at the local end by a half of the channel spacing. For

details, see Configuring the IF/ODU Information of a Radio Link.d. Test and record the RSL.e. Increase the received frequency at the local end, with a step length of 0.5 MHz or 1

MHz, and record the RSL accordingly until the received frequency is equal to theoriginal received frequency plus a half of the channel spacing.

f. Compare the recorded RSLs, and check whether the RSL in a certain spectrum isabnormal if the received frequency is within the permitted range.

(3) Use a spectrum analyzer to analyze the interference source.(4) Contact the spectrum management department to clear the interference spectrum or change

plans to minimize the interference.

----End


A.2.31 MW_RDI

DescriptionThe MW_RDI alarm indicates that there are defects at the remote end of a radio link. This alarmoccurs when the IF board detects an RDI in the radio frame overheads.

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 the



A-59

following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning



If the local site is configured with reverse switching, 1+1 switching on the IF board is triggeredwhen the working and protection boards receive the MW_RDI alarm at the same time. Thisalarm also indicates that the services received at the opposite site are interrupted.

Possible Causes

After detecting a service alarm that is caused by the fault on a radio link, the receive end returnsa radio link fault indication to the transmit end.

Procedure

Step 1 Cause: After detecting a service alarm that is caused by the fault on a radio link, the receive endreturns a radio link fault indication to the transmit end.(1) Clear the microwave alarms that occur at the opposite site. The possible alarms are as

follows:l MW_LOF

l R_LOF

l R_LOC

----End

Related Information

None.

A.2.32 NESF_LOST

Description

The NESF_LOST is an alarm indicating that the NE software is lost. This alarm occurs whenthe system control, cross-connect, and timing board detects that the NE software in the flashmemory is lost.

Attribute




Maintenance Guide


Issue 03 (2010-05-30)


Name Meaning

Parameter 1 Indicates the routine inspection object.

l 0x01: Indicates an ordinary file

l 0x02: Indicates the version of the running software

l 0x03: Indicates a special routine inspection object

Parameter 2, Parameter 3 Indicate the ID of the routine inspection object.

l 0x01, 0x03, 0x05, 0x07, and 0x09 indicate the scc.fpga,nesoft.hwx, ne.ini, ocp.ini, and DSSPCfg.xml in the ofs1,respectively.

l 0x02, 0x04, 0x06, 0x08, and 0x0A indicate the scc.fpga,nesoft.hwx, ne.ini, ocp.ini, and DSSPCfg.xml in the ofs2,respectively.

Parameter 4 Alarm Cause

l If the first bit is 1, it indicates that the file does not exist.

l If the second bit is 1, it indicates that verification of the file fails.

l If the third bit is 1, it indicates that the version of the file in theactive area is different from the version of the file in the standbyarea.

l If the fourth bit is 1, it indicates that the version of the file of theactive board is different from the version of the file in the standbyboard.

Impact on the SystemIf the NE software does not exist in the active and standby areas, an NE cannot be restarted afterit 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 fails.l Cause 3: The portable flash memory card is not in position or is faulty.

ProcedureStep 1 Cause 1: No new NE software is loaded after the existing NE software is erased.

Cause 2: Loading the NE software fails.



A-61

(1) Check whether the alarm is caused by the loading operation.

If... Then...

The alarm is caused by the loadingoperation

Contact the Huawei engineers to re-load thesoftware.

The alarm is not caused by the loadingoperation


Step 2 Cause 3: The portable flash memory card is not in position or is faulty.(1) Re-install or replace the portable flash memory card.

----End


A.2.33 NESTATE_INSTALL

DescriptionThe NESTATE_INSTALL is an alarm indicating that the NE is in the install state.

Attribute



ParametersNone.

Impact on the SystemThe NE fails to work.

Possible CausesCause 1: The NE database check fails.

ProcedureStep 1 Cause: The NE database check fails.

(1) Restore the data from the backup database.

----End



Maintenance Guide


Issue 03 (2010-05-30)

A.2.34 POWER_ALM

DescriptionThe POWER_ALM is a power module alarm indication.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the power module that reports the alarm. For example, 0x01indicates that the alarm is reported by power module 1 of the board.

Parameter 2 l 0x01: under-voltage

l 0x02: over-voltage

Impact on the SystemThe power module of the IDU 605 that accesses the -48 V/-60 V power supply is underprotection. Therefore, if only one power module reports the POWER_ALM alarm, the systemis not affected.

Possible Causesl Cause 1: The accessed power is abnormal.

l Cause 2: The power module is abnormal.

Procedure

Step 1 Cause 1: The accessed power is abnormal.(1) Use a multimeter to test the power voltage supplied to the chassis.

If... Then...

The voltage is beyond the range of -38.4 V to -72 V Clear the alarm immediately.

The voltage is within the range of -38.4 V to -72 V Go to Cause 2.

Step 2 Cause 2: The power module is abnormal.



A-63


----End


A.2.35 R_LOC

DescriptionThe R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm isreported when the line board fails to extract the clock signal from the line signal or the IF boardfails to extract the clock signal from the IF signal.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path.

Impact on the SystemThe services on the line port or the IF port are interrupted. If the system is configured withprotection, protection switching may be triggered.

Possible Causesl Cause 1: The receive unit at the local site is faulty.

l Cause 2: The transmit unit at the opposite site is faulty.

Procedure

Step 1 Cause 1: The receive unit at the local site is faulty.


Maintenance Guide


Issue 03 (2010-05-30)

(1) At the local site, perform an inloop on the port of the board that reports the alarm. Fordetails, see 7.5 Software loopback.

If... Then...

The alarm persists after the loopback Replace the board that reports the alarm atthe local site.

The alarm clears after the loopback Go to Cause 2.

(2) Replace the board and then check whether the alarm clears.

If... Then...

The alarm clears after the board isreplaced


The alarm persists after the board isreplaced

Replace the PXC board of the local site.

Step 2 Cause 2: The transmit unit at the opposite site is faulty.(1) Replace the board of the opposite site.

If... Then...

The alarm clears after the board isreplaced


The alarm persists after the board isreplaced

Replace the PXC board of the opposite site.

----End


A.2.36 R_LOF

DescriptionThe R_LOF is an alarm indicating that frames are lost on the receive side. This alarm is reportedwhen the OOF state lasts for 3 ms.

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 example,



A-65

Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the followingtable.

Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path.

Impact on the SystemServices are interrupted. If the system is configured with protection, protection switching maybe triggered.

Possible Causesl Cause 1: Certain other alarms occur.



Procedure

Step 1 Cause 1: Certain high-level alarms occur.(1) Check whether the MW_FEC_UNCOR alarm is reported.

If... Then...

The MW_FEC_UNCOR alarm isreported

Handle the MW_FEC_UNCOR alarmimmediately.

The MW_FEC_UNCOR alarm is notreported


(2) Perform an inloop on the IF port that reports the alarm.

If... Then...

The alarm clears after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thetransmit unit of the opposite site is faulty.

The alarm persists after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thereceive unit of the local site is faulty.

Step 2 Cause 2: The transmit unit of the opposite site is faulty.(1) Perform the operation according to the IDU configuration of the opposite site.

l If the opposite site is configured with the IDU 605, replace the IDU of the oppositesite.

l If the opposite site is configured with the IDU 620

a. Replace the IF board of the opposite site.


Maintenance Guide


Issue 03 (2010-05-30)

b. The alarm persists after the IF board is replaced, replace the PXC board of theopposite site.

Step 3 Cause 3: The receive unit of the local site is faulty.(1) Replace the IDU of the local site.

----End


A.2.37 R_LOS

DescriptionThe R_LOS is an alarm indicating that the signals received by the tributary on the receive lineside or the microwave frames on the receive line side are lost.

Attribute




Name Meaning


Parameter 2, Parameter 3 Indicate the ID of the path. For example, 0x00 0x01 indicate thatthe alarm is reported in path 1.

Impact on the SystemServices are interrupted. If the system is configured with protection, protection switching maybe triggered.





A-67


Procedure

Step 1 Cause 1: Certain high-level alarms occur.(1) Check whether the MW_FEC_UNCOR alarm is reported.

If... Then...

The MW_FEC_UNCOR alarm isreported

Handle the MW_FEC_UNCOR alarmimmediately.

The MW_FEC_UNCOR alarm is notreported


(2) Perform an inloop on the IF port that reports the alarm.

If... Then...

The alarm clears after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thetransmit unit of the opposite site is faulty.

The alarm persists after the inloop isperformed

Clear the alarm according to the solutionfor the alarm that is reported when thereceive unit of the local site is faulty.

Step 2 Cause 2: The transmit unit of the opposite site is faulty.(1) Perform the operation according to the IDU configuration of the opposite site.

l If the opposite site is configured with the IDU 605, replace the IDU of the oppositesite.

l If the opposite site is configured with the IDU 620

a. Replace the IF board of the opposite site.b. If the alarm persists after the IF board is replaced, replace the PXC board of the

opposite site.

Step 3 Cause 3: The receive unit of the local site is faulty.(1) Replace the IDU of the local site.

----End


A.2.38 RADIO_FADING_MARGIN_INSUFF

DescriptionThe RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive powerof the ODUs are lower than the threshold of the receive power (the threshold value is about thereceiver sensitivity plus 14 dB).


Maintenance Guide


Issue 03 (2010-05-30)

When the receive power of the ODUs in consecutive six hours is lower than the threshold, thesystem reports the alarm. When the mean receive power of the ODUs becomes normal in threeminutes after the alarm is reported, the alarm clears.

Attribute



Parameters


Name Meaning


Parameter 2, Parameter 3 The values are always 0xff 0xff.



If the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.

Possible Causesl Cause 1: The ODU fault at the transmit end causes abnormal transmit power.

l Cause 2: The direction of the antenna is deflected.

l Cause 3: Transmission environment changes.

l Cause 4: The fading margin in the case of rain and fog in the network planning isinsufficient.

Procedure

Step 1 Cause 1: The ODU fault at the transmit end causes abnormal transmit power.(1) Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.

If... Then...

The ODU at the transmit end reports theRADIO_TSL_LOW alarm

Handle the RADIO_TSL_LOW alarm.

The ODU at the opposite end does not report theRADIO_TSL_LOW alarm

Go to Cause 2.

Step 2 Cause 2: The direction of the antenna is deflected.



A-69

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

The transmission environment does notchange

Go to Cause 4.

Step 4 Cause 4: The fading margin in the case of rain and fog in the network planning is insufficient.(1) If the alarm is reported frequently, contact the network planning department for increasing

the fading margin by replanning the transmission trail.

----End


A.2.39 RADIO_MUTE

DescriptionThe RADIO_MUTE is an alarm indicating that the radio transmitter is muted.

Attribute


Warning Equipment alarm


Name Meaning

Parameter 1 Indicates the RF port that reports the alarm.


Maintenance Guide


Issue 03 (2010-05-30)


The transmitter does not transmit services.


l Cause 2: The transmitter of the local site is muted manually.

l Cause 3: The IDU is faulty, causing abnormal IF output.

l Cause 4: The data output is abnormal because the ODU is faulty.

Procedure

Step 1 Cause 1: Certain other alarms occur.

(1) Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated. Ifyes, clear the alarm immediately.

Step 2 Cause 2: The transmitter of the local site is muted manually.

(1) Check whether the transmitter of the ODU is muted. For details, see Configuring the IF/ODU Information of a Radio Link. If yes, unmute the ODU. Then, enable the ODU totransmit signals.

Step 3 Cause 3: The IDU is faulty, causing abnormal IF output.


Step 4 Cause 4: The data output is abnormal because the ODU is faulty.

(1) 6.2 Replacing an ODU.

----End

Related Information

The number of the logical slot for the ODU is the number of the slot for the IF board connectedto the ODU plus 10.

A.2.40 RADIO_RSL_BEYONDTH

Description

The RADIO_RSL_BEYONDTH is an alarm indicating that antennas are not aligned. When thereceivable power is set on an NE, the NE enables the antenna alignment indication functionautomatically. If the actual receive power of the ODU is lower than the preset receive powerminus 3 dB, the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are alignedfor continuous 30 minutes, the antenna alignment indication function is disabled automatically.Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when theRADIO_FADING_MARGIN_INSUFF alarm is reported.



A-71

Attribute



Parameters


Name Meaning





If the MW_LOF or MW_FEC_UNCOR alarm is not generated, services are not affected.

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 presetreceive 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. When theRADIO_FADING_MARGIN_INSUFF alarm clears, the RADIO_RSL_BEYONDTHalarm clears.

----End

Related Information

None.

A.2.41 RADIO_RSL_HIGH


Maintenance Guide


Issue 03 (2010-05-30)

Description

The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is high. This alarmis reported if the detected receive power is equal to or higher than the upper threshold of theODU (-20 dBm).

Attribute


Critical Service alarm

Parameters


Name Meaning



Normal transmission of services is affected. If the system is configured with 1+1 protection,protection switching may be triggered.

Possible Causesl Cause 1: The local ODU is faulty.

l Cause 2: There is a strong interference source nearby.

l Cause 3: The transmit power of the opposite ODU is high.

Procedure

Step 1 Cause 1: The local ODU is faulty.(1) Replace the ODU.

Step 2 Cause 2: There is a strong interference source nearby.(1) Check whether any nearby signal source transmits signals whose frequency is close to the

specified range. If yes, check whether the signal source can be closed or moved. If not,contact the network planning department for replanning the frequency.

Step 3 Cause 3: The transmit power of the opposite ODU is high.(1) Reset the transmit power of the opposite ODU. For details, see Configuring the IF/ODU

Information of a Radio Link.

----End



A-73


A.2.42 RADIO_RSL_LOW

DescriptionThe RADIO_RSL_LOW is an alarm indicating that the radio receive power is low. This alarmis reported if the detected receive power is equal to or lower than the lower threshold of the ODU(-90 dBm).

Attribute




Name Meaning


Impact on the SystemIf no MW_LOF or MW_FEC_UNCOR alarm is generated, services are not affected.

Possible Causesl Cause 1: Certain other alarms occur at the opposite site.

l Cause 2: The transmit power of the opposite site is low.

l Cause 3: The local ODU 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 generated on the equipment of the opposite site.If yes, clear the alarm immediately.l RADIO_MUTE

l CONFIG_NOSUPPORT

l RADIO_TSL_LOW


Maintenance Guide


Issue 03 (2010-05-30)

l BD_STATUS

Step 2 Cause 2: The transmit power of the opposite site is low.

(1) Check whether the transmit power of the opposite site is normal. For details, seeConfiguring the IF/ODU Information of a Radio Link. If the transmit power is abnormal,replace the ODU of the opposite site.

Step 3 Cause 3: The local ODU is faulty.

(1) Replace the ODU of the local site.

Step 4 Cause 4: Signal attenuation on the radio link is heavy.

(1) Browse history alarms, and check whether the RADIO_RSL_LOW alarm occurscontinuously.

If the alarm occurs occasionally, contact the network planning department to change thedesign to improve anti-fading performance.

(2) Check whether the antennas at both ends are aligned.

If the antennas are not aligned, align the antennas again.

(3) Check whether any mountain or building obstacle exists in the transmit direction.

If yes, contact the network planning department for proper modification to the planningdesign, therefore avoiding the block of the mountain or building obstacle.

(4) Check whether the polarization direction of the antenna, ODU, and hybrid coupler at bothends is set correctly.

If not, correct the polarization direction.

(5) Check whether the outdoor units such as the antenna, hybrid coupler, ODU, and flexiblewaveguide are wet, damp, or damaged.

If yes, replace the unit that is wet, damp, or damaged. For details, see 6 PartReplacement.

(6) Check whether the antenna gain at both the transmit and receive ends meets the requirement.

If not, replace the antenna.

----End

Related Information

None.

A.2.43 RADIO_TSL_HIGH

Description

The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is high. This alarmis reported if the detected transmit power is higher than the upper power threshold of the ODU.



A-75

Attribute




Name Meaning


Impact on the SystemNormal transmission of services is affected. If the system is configured with 1+1 protection,protection switching may be triggered.

Possible CausesCause 1: The ODU is faulty.

Procedure

Step 1 Cause 1: The ODU is faulty.(1) Replace the ODU.

----End


A.2.44 RADIO_TSL_LOW

DescriptionThe RADIO_TSL_LOW is an alarm indicating that the radio transmit power is low. This alarmis reported if the detected transmit power is less than the lower power threshold of the ODU.

Attribute




Maintenance Guide


Issue 03 (2010-05-30)


Name Meaning


Impact on the SystemNormal transmission of services is affected. If the system is configured with 1+1 protection,protection switching may be triggered.

Possible CausesCause 1: The ODU is faulty.

Procedure

Step 1 Cause 1: The ODU is faulty.(1) Replace the ODU.

----End


A.2.45 RELAY_ALARM

DescriptionThe RELAY_ALARM is an alarm indicating relay errors.

Attribute


Critical Environment alarm




A-77

Name Meaning

Parameter 1 Indicates the ID of the input alarm signal. For example, 0x01 indicates that thereported external alarm is from the first input alarm signal.

Impact on the SystemNone.

Possible CausesCause 1: There is an input alarm signal.

Procedure

Step 1 Cause 1: There is an input alarm signal.(1) Based on the alarm parameter, determine the ID of the input alarm signal.(2) Rectify the fault according the meaning of the input alarm signal.

----End


A.2.46 RP_LOC

DescriptionThe RP_LOC is an alarm indicating that the clock of the receive phase-locked loop is lost.

Attribute



ParametersNone.

Impact on the SystemThe services are interrupted.

Possible Causesl Cause 1: The service configuration data is incorrect.



Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Cause 1: The service configuration data is incorrect.

(1) Check whether the service is correctly configured.

If... Then...

The service is configured incorrectly Reconfigure the service.

The service is configured correctly Go to Cause 2.

Step 2 Cause 2: The IDU is faulty.


----End

Related Information

None.

A.2.47 RPS_INDI

Description

The RPS_INDI is a radio protection switching alarm indication.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the protection group.

Parameter 2 Indicates the type of protection switching.

0x01: HSB protection switching

0x02: HSM protection switching



A-79


During the HSB protection switching, services are interrupted. After the HSB switching iscomplete, the services are restored to normal.

During the HSM protection switching, no bit errors occur and services are not affected.

Possible Causesl The possible causes of the HSB protection switching are as follows:

– Cause 1: An external switching event occurs.

– Cause 2: An automatic switching event occurs.

– Cause 3: A reverse switching event occurs.

l Possible cause of the HSM protection switching: At the local site, the radio link in thereceive direction is faulty.

Procedure

Step 1 Determine the type of the protection switching based on the alarm parameter.

Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, a command is issuedon the NMS to trigger the switching.(1) Check whether the switching is the forced switching or manual switching. For details, see

Querying the IF 1+1 Protection Status.

If... Then...

The switching is the forced switching ormanual switching

Find the cause and clear the switchingimmediately.

The switching is not the forcedswitching or manual switching

Go to Cause 2 of HSB switching.

Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is faulty,or the service is defective.(1) Check whether the following faults or alarms occur. If yes, rectify the faults or clear the

alarms.l Hardware fault on the IDU, or hardware fault on the ODU

l POWER_ALM or VOLT_LOS

l RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH

l IF_INPWR_ABN or CONFIG_NOSUPPORT

l R_LOC, R_LOF, R_LOS, or MW_LOF

NOTE

l If the switching is non-revertive, the services are not automatically switched back to the workingpath when the working path is restored to normal, and the RPS_INDI alarm persists. In this case,you need to manually switch the services from the protection path to the working path. TheRPS_INDI alarm clears only when the switching is successful.

l If the switching is revertive, the services are automatically switched back to the working pathwhen the specified wait-to-restore (WTR) time expires after the working path is restored tonormal. The RPS_INDI alarm clears only when the switching is successful.


Maintenance Guide


Issue 03 (2010-05-30)

Step 4 Cause 3 of HSB switching: A reverse switching event occurs.(1) Check whether the active and standby IF ports report the MW_RDI alarm. If yes, clear the

MW_RDI alarm immediately.

Step 5 Cause of the HSM switching: The radio link is faulty.(1) Check whether any alarm that triggers HSM switching is generated on the IF port in the IF

1+1 protection group. If yes, clear the alarm immediately.HSM switching may be triggered by any of the following alarms:l R_LOC, R_LOF, R_LOS, or MW_LOF

l MW_FEC_UNCOR

----End


A.2.48 SWDL_ACTIVATED_TIMEOUT

DescriptionThe SWDL_ACTIVATED_TIMEOUT is an alarm indicating that the commit operation is notperformed during software package loading. During simulation package diffusion, the systemreports the alarm if the commit operation is not performed within 30 minutes after activation ofthe NE software.

Attribute



ParametersNone.

Impact on the SystemIf an NE fails to perform the commit operation for a long period, the software in the two areasof the NE is inconsistent.

Possible CausesCertain radio links are faulty. As a result, the NE involved in the simulation package diffusionfails to receive the commit command.

Procedure

Step 1 Cause: Certain radio links are faulty. As a result, the NE involved in the simulation packagediffusion fails to receive the commit command.



A-81

(1) Check whether any radio link is faulty.

If... Then...

Certain radio links are faulty Rectify the faults on the radio links and ensure thatthe links between the nodes on which the softwarepackage is loaded are normal.

Radio links are normal Perform simulation package diffusion for the NEsthat fail to be upgraded through simulation packagediffusion.

----End


A.2.49 SWDL_AUTOMATCH_INH

DescriptionThe SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function isdisabled. When the automatic match function of the service logical board is disabled, the systemreports the alarm if the service logical board cannot find out the mapping software from thesoftware on the SCC board.

Attribute



ParametersNone.

Impact on the SystemIf the service logical board fails to find out the mapping software from the software on the SCCboard, the software versions of the entire NE are inconsistent. As a result, certain functions ofthe NE cannot run normally.

Possible CausesThe automatic match function is disabled.

ProcedureStep 1 Cause: The automatic match function is disabled.

(1) Contact Huawei technical support engineers for troubleshooting.

----End


Maintenance Guide


Issue 03 (2010-05-30)


A.2.50 SWDL_COMMIT_FAIL

DescriptionThe 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 simulation package diffusion.

Attribute



ParametersNone.

Impact on the SystemWhen the SWDL_COMMIT_FAIL alarm occurs, the software versions in the two areas of thedouble-area board are inconsistent.

Possible CausesCause 1: The loaded software package is incorrect.

ProcedureStep 1 Cause 1: The loaded software package is incorrect.

(1) Check whether the loaded software package is correct.(2) Perform simulation package diffusion again for the NE that reports the

SWDL_COMMIT_FAIL alarm.

----End


A.2.51 SWDL_CHGMNG_NOMATCH

DescriptionThe SWDL_CHGMNG_NOMATCH is an alarm indicating that the board software version andthe version of the running software are inconsistent. This alarm is reported when the systemdetects that the software version of any online board is inconsistent with the version of therunning software after the SCC board is replaced.



A-83

Attribute



ParametersNone.

Impact on the SystemWhen the SWDL_CHGMNG_NOMATCH alarm is reported, certain functions of the NE maybe affected because the board software version is inconsistent with the version of the runningsoftware.

Possible CausesThe software package of the SCC board does not match the software version of the board afterthe SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm is reported.

Procedure

Step 1 Cause: The software package of the SCC board does not match the software version of the boardafter the SCC board is replaced. In this case, the SWDL_CHGMNG_NOMATCH alarm isreported.(1) Perform simulation package diffusion again for the NE that reports the

SWDL_CHGMNG_NOMATCH alarm.

----End


A.2.52 SWDL_INPROCESS

DescriptionThe SWDL_INPROCESS is an alarm indicating that the simulation package diffusion is inprocess on the NE.

Attribute


Warning Processing alarm

ParametersNone.


Maintenance Guide


Issue 03 (2010-05-30)

Impact on the SystemWhen the software package is being loaded to an NE, the operations, such as modifyingconfiguration, uploading/downloading files, and backing up the database, are not allowed.

Possible CausesCause: The simulation package diffusion is being performed on the NE.

Procedure

Step 1 Cause: The simulation package diffusion is being performed on the NE.(1) The SWDL_INPROCESS alarm clears automatically after the loading or rollback is

complete. Hence, this alarm does not require handling.

----End


A.2.53 SWDL_NEPKGCHECK

DescriptionThe SWDL_NEPKGCHECK is an alarm indicating that a certain file of the package stored inthe flash memory of the NE is lost. During the routine inspection on the flash memory in thedouble areas of the SCC board, the NE software detects that a certain file of the package in onearea is missing or cannot be verified. If the corresponding file in the other area is normal, theNE software recovers the missing or faulty file with the normal one. This alarm is reported whenthe file is found missing and cannot be recovered at the end of the routine inspection. This alarmclears when the file is recovered in the next routine inspection.

Attribute



ParametersNone.

Impact on the SystemA certain file of the package is missing and the NE may malfunction.

Possible CausesCause 1: A certain file is missing and cannot be recovered.



A-85

Procedure

Step 1 Cause 1: A certain file is missing and cannot be recovered.(1) Ensure that the loaded software package is correct. Perform simulation package diffusion

again for the NE that reports the SWDL_NEPKGCHECK alarm.

----End


A.2.54 SWDL_PKG_NOBDSOFT

DescriptionThe SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing inthe software package. This alarm is reported when the required software is missing in thesoftware package during the automatic match of the board.

Attribute



ParametersNone.

Impact on the SystemThe board cannot perform automatic match, because the required board software is missing inthe software package. Therefore, the board software version is inconsistent with the NE softwareversion, and certain functions of the NE may be affected.

Possible CausesCause 1: Certain board software is not loaded during software package loading.

Procedure

Step 1 Cause 1: Certain board software is not loaded during software package loading.(1) Add the required board software to the software package, Alternatively, perform software

package loading again.

----End



Maintenance Guide


Issue 03 (2010-05-30)

A.2.55 SWDL_ROLLBACK_FAIL

DescriptionThe SWDL_ROLLBACK_FAIL is an alarm indicating that an NE rollback fails. If a boardrollback fails when the NE rollback is being performed, this alarm is reported.

Attribute



ParametersNone.

Impact on the SystemThe board software version fails to match the NE software version, and therefore certainfunctions of the NE may be affected.

Possible CausesCause 1: Certain board software is not loaded during software package loading.

Procedure

Step 1 Cause 1: Certain board software is not loaded during software package loading.(1) Add the required board software to the software package, Alternatively, perform software

package loading again.

----End


A.2.56 T_ALOS

DescriptionThe T_ALOS is an alarm indicating that analog signals are lost at the 2 Mbit/s interface.

Attribute





A-87

Parameters


Name Meaning




2 Mbit/s services are interrupted.

Possible Causesl Cause 1: The interface does not access 2 Mbit/s services.

l Cause 2: The opposite equipment is faulty.

l Cause 3: The trunk cable is faulty.

l Cause 4: The board that reports the alarm is faulty.

Procedure

Step 1 Cause 1: The interface does not access 2 Mbit/s services.(1) Check whether the interface accesses 2 Mbit/s services.

If... Then...

The interface does not access services Enable the port to access services or deleteunnecessary services.

The interface accesses services Go to Cause 2.

Step 2 Cause 2: The opposite equipment is faulty.(1) Check whether the opposite equipment is faulty.

If... Then...

The equipment is faulty Rectify the fault.

The equipment runs normally Go to Cause 3.

Step 3 Cause 3: The trunk cable is faulty.(1) Check whether the trunk cable is faulty.

If... Then...

The trunk cable is faulty Rectify the fault.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The trunk cable is in normal status Go to Cause 4.

Step 4 Cause 4: The board that reports the alarm is faulty.(1) Replace the IDU.

----End


A.2.57 TEMP_ALARM

DescriptionThe TEMP_ALARM alarm indicates that the board temperature crosses the threshold.

Attribute


Minor Environment alarm


Name Meaning

Parameter 1 l 0x01: The temperature crosses the upper threshold.

l 0x02: The temperature crosses the lower threshold.

Impact on the SystemThe board fails to work normally.

Possible Causesl Cause 1: The board temperature crosses the threshold.

l Cause 2: The temperature detection circuit of the board is faulty.

Procedure

Step 1 Cause 1: The board temperature crosses the threshold.



A-89

(1) If the alarm is reported by the ODU, take appropriate measures (for example, installing asunshade) to control the temperature.

(2) If the alarm is reported by the IDU, check whether the temperature control devices, suchas air-conditioners, operate normally.

If... Then...

The temperature control devicesmalfunction

Adjust the temperature control devices.

The temperature control devices worknormally


(3) Check whether the heat dissipation hole on the IDU is covered or blocked.

If... Then...

The heat dissipation hole is covered orblocked

Clear or remove the covering materials orobstacles.

The heat dissipation hole is not covered orblocked


(4) Check whether 1U space is reserved above and below the IDU for natural heat dissipation.

If... Then...

The heat dissipation space does not meetthe requirement

Change the position of the IDU and reservea sufficient space for heat dissipation.

The heat dissipation space meets therequirement

Clear the alarm according to the solutionfor the alarm that is generated when thetemperature detection circuit of a board isfaulty.

Step 2 Cause 2: The temperature detection circuit of the board is faulty.(1) If the ambient temperature is normal and no heat dissipation problem exists, replace the

IDU.

----End


A.2.58 UP_E1_AIS

DescriptionThe UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reportedwhen the tributary board detects that the 2 Mbit/s uplink signal is all 1s.


Maintenance Guide


Issue 03 (2010-05-30)

Attribute




Name Meaning



Impact on the SystemE1 signals are unavailable.

Possible Causesl Cause 1: The opposite equipment transmits the AIS signal.

l Cause 2: The receive unit of the tributary unit at the local site is faulty.

Procedure

Step 1 Cause 1: The opposite equipment transmits the AIS signal.(1) Check whether the opposite equipment transmits the AIS signal.

If... Then...

The opposite equipment transmits theAIS signal

Rectify the fault on the opposite equipment.

The opposite equipment does nottransmit the AIS signal

Go to Cause 2.

Step 2 Cause 2: The receive unit of the tributary unit at the local site is faulty.(1) Replace the IDU.

----End


A.2.59 VOLT_LOS



A-91

DescriptionThe VOLT_LOS is an alarm indicating that the power voltage is unavailable.

Attribute




Name Meaning

Parameter 1 Indicates the type of the power that reports the alarm.l 0x01: -48 V/+24 V power output

l 0x02: -48 V/+24 V power input

l 0x03: +5 V power output

l 0x04: +3.3 V power output

l 0x05: lightning

Impact on the Systeml If the alarm is reported by the PW48A/PW48B/PW24A board, the power module that

reports the alarm fail to work. If the system is not configured with a protection powermodule, the system fails to work normally.

l If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.

Possible Causesl Cause 1: The output power is abnormal.

l Cause 2: The input power is abnormal.

l Cause 3: Lightning occurs.

Procedure

Step 1 Determine the type of the power supply that reports the alarm based on the alarm parameter.

Step 2 Cause 1: The output power is abnormal.(1) Clear the alarm according to the type of the power supply that reports the alarm.

If... Then...

The alarm is reported by the PW48A/PW48B/PW24A board Replace the IDU.


Maintenance Guide


Issue 03 (2010-05-30)

If... Then...

The alarm is reported by the IF board Go to the next step.

(2) Check the power switch of the ODU.

If... Then...

The power switch is turned off Turn on the power switch.

The power switch is turned on Go to the next step.

(3) Check the IF fiber jumper, IF cable, or ODU section by section for a short circuit.

If... Then...

A short circuit exists Replace the short-circuited component, and then replace theIDU.

No short circuit exists Replace the IDU.

CAUTIONIf the alarm is caused by a short circuit, replace the short-circuited cable or ODU, and thenreplace the IDU. Otherwise, the new IDU may be damaged.

Step 3 Cause 2: The input power is abnormal.

(1) Clear the alarm according to the type of the power supply that reports the alarm.

If... Then...

The alarm is reported by the IDU Replace the IDU.

The alarm is reported by the power board Go to the next step.

(2) Check the power switch.

If... Then...

The power switch is turned off Turn on the power switch.

The power switch is turned on Contact the engineers for power supply to rectify thefault.

Step 4 Cause 3: Lightning occurs.

(1) Contact the engineers for power supply to check the grounding lightning facilities.

----End

Related Information

None.



A-93

B Abnormal Event Reference

An abnormal event is an important indicator when a fault occurs on the equipment. This topicdescribes all the possible important abnormal events of the OptiX RTN 605 and how to handlethese events.

B.1 Important Abnormal EventsImportant abnormal events include protection switching events and RMON alarms.

B.2 Important Abnormal Events and Handling ProceduresThis topic describes all the important abnormal performance events of the OptiX RTN 605 inalphabetic order and how to handle these events.

OptiX RTN 605Maintenance Guide B Abnormal Event Reference


B-1

B.1 Important Abnormal EventsImportant abnormal events include protection switching events and RMON alarms.

Table B-1 Important abnormal events

Event Name Source

IF 1+1 Protection Switching IFH1 and IF0

RMON Performance Value Below theLower Limit

EMS4

RMON Performance Value Above theUpper Limit

EMS4

NOTEAll alarmed boards refer to the logical boards that are displayed on the NMS.

B.2 Important Abnormal Events and Handling ProceduresThis topic describes all the important abnormal performance events of the OptiX RTN 605 inalphabetic order and how to handle these events.

B.2.1 IF 1+1 Protection Switching

B.2.2 RMON Performance Value Below the Lower Limit

B.2.3 RMON Performance Value Above the Upper Limit

B.2.1 IF 1+1 Protection Switching

DescriptionThis abnormal event indicates that 1+1 HSB, 1+1 FD, or 1+1 SD switching occurs on theequipment.

AttributeSeverity Type

Major Service

B Abnormal Event ReferenceOptiX RTN 605

Maintenance Guide

B-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

ParametersName Meaning

Protection Group ID Indicates the ID of the protection group wherean IF 1+1 protection switching occurs.

Slot ID of Working Board Indicates the slot ID of the current workingboard.

Current Working Board Indicates the current working board.l 0: main board

l 1: standby board

Main Board State Indicates the current state of the main board.l Normal

l Failed

l MW_RDI

Standby Board State Indicates the current state of the standbyboard.l Normal

l Failed

l MW_RDI

Switching Request Type Indicates the type of an IF 1+1 protectionswitching request.l No request

l Automatic switching

l Manual switching

l Forced switching

l Lockout of switching

l Wait-to-restore

l RDI switching

Impact on Systeml During HSB protection switching, the services are interrupted. After the switching is

completed, the services are restored to normal.l During HSM protection switching, no bit errors occur and the services are not affected.

When the AM function is enabled, the protection path works in modulation mode forensuring capacity after HSM switching is completed. Hence, the services of lower prioritiesare impaired.

Relevant AlarmsWhen IF 1+1 protection switching occurs, the RPS_INDI alarm is reported.



B-3

Possible Causesl The possible causes of the HSB protection switching are as follows:

– The hardware of the ODU or IF unit at the local end is faulty.

– The working path at the local end receives the MW_RDI alarm.

– An external switching, which is triggered by the switching command that is issued fromthe NMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

l The possible causes of HSM protection switching are as follows:

– The radio link in the receive direction of the local end is faulty.

– An external switching, which is triggered by the switching command that is issued fromthe NMS software, occurs. The external switching includes lockout of switching, forcedswitching, and manual switching.

Procedure

Step 1 Rectify the fault according to the switching request type indicated by the parameter and thedescription in RPS_INDI.

----End

B.2.2 RMON Performance Value Below the Lower Limit

Description

This abnormal event indicates that the current RMON performance value is lower than the presetlower limit.

Attribute

Severity Type

Major Service

Parameters

Name Meaning

Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Lower Limit Indicates the lower limit of the currentRMON performance event.


Maintenance Guide


Issue 03 (2010-05-30)

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeList of RMON Alarm Entries.

Relevant AlarmsDifferent alarms are reported when different RMON performance values are lower than thelower limits. For details, see D.3 RMON Alarm Clearance Reference.

Possible CausesThe lower limit of a performance event is set to a non-zero value.

Procedure

Step 1 Set the lower limit of the performance event to zero.

----End

B.2.3 RMON Performance Value Above the Upper Limit

DescriptionThis abnormal event indicates that the current RMON performance value is higher than the presetupper limit.

AttributeSeverity Type

Major Service

ParametersName Meaning

Performance ID Indicates the ID of the current RMONperformance event.

Current Performance Value Indicates the value of the current RMONperformance event.

Upper Limit Indicates the upper limit of the currentRMON performance event.

Impact on SystemDifferent abnormal performance events have different impacts on the system. For details, seeList of RMON Alarm Entries.



B-5

Relevant AlarmsDifferent alarms are reported when different RMON performance values are higher than theupper limits. For details, see D.3 RMON Alarm Clearance Reference.

Possible CausesWhen the performance values of different abnormal RMON performance events are higher thanthe upper limits, the causes are different from each other. For details, see D RMON EventReference.

Procedure

Step 1 See D.3 RMON Alarm Clearance Reference to handle different abnormal performance events.

----End


Maintenance Guide


Issue 03 (2010-05-30)

C Performance Event Reference

Performance events are important indicators when the equipment performance changes. Thistopic describes all the possible performance events on the OptiX RTN 605 and how to handlethese performance events.

C.1 Performance Event ListPerformance events are categorized on the basis of the performance event type, and include allthe events of the OptiX RTN 605.

C.2 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 605 and how to handle these performance events.

OptiX RTN 605Maintenance Guide C Performance Event Reference


C-1

C.1 Performance Event ListPerformance events are categorized on the basis of the performance event type, and include allthe events of the OptiX RTN 605.

C.1.1 Microwave Performance EventsMicrowave performance events include the performance events regarding the microwave power,FEC, and radio link bit errors.

C.1.2 Other Performance EventsIn addition to the SDH and microwave performance events, the OptiX RTN 605 supportsperformance events regarding the temperature.

C.1.1 Microwave Performance EventsMicrowave performance events include the performance events regarding the microwave power,FEC, and radio link bit errors.

Table C-1 Microwave power performance events

Event Name Description Source

TSL_MAX Indicates the maximum radiotransmit signal level.

ODU

TSL_MIN Indicates the minimum radiotransmit signal level.

TSL_CUR Indicates the current radiotransmit signal level.

TSL_AVG Indicates the average radiotransmit signal level.

RSL_MAX Indicates the maximum radioreceived signal level.

RSL_MIN Indicates the minimum radioreceived signal level.

RSL_CUR Indicates the current radioreceived signal level.

RSL_AVG Indicates the average radioreceived signal level.

TLHTT Indicates the duration whenthe transmit power is higherthan the upper threshold.

TLLTT Indicates the duration whenthe transmit power is higherthan the lower threshold.

C Performance Event ReferenceOptiX RTN 605

Maintenance Guide

C-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)


RLHTT Indicates the duration whenthe receive power is lowerthan the upper threshold.

RLLTT Indicates the duration whenthe receive power is lowerthan the lower threshold.

Table C-2 FEC performance events


FEC_BEF_COR_ER Indicates the BER before theFEC is performed.

IF0 and IFH1

FEC_COR_BYTE_CNT Indicates the number of bytesthat are corrected through theFEC.

IF0

FEC_UNCOR_BLOCK_CNT

Indicates the number offrames that cannot becorrected through the FEC.

IFH1

Table C-3 Performance events regarding radio link bit errors


IF_BBE Indicates the radio linkbackground block error.

IF0 and IFH1

IF_ES Indicates the radio linkerrored second.

IF_SES Indicates the radio linkseverely errored second.

IF_UAS Indicates the radio linkunavailable second.

IF_CSES Indicates the radio linkconsecutively severelyerrored second.



C-3

Table C-4 ATPC performance events


ATPC_P_ADJUST Indicates the positive ATPCadjustment event.

ODU

ATPC_N_ADJUST Indicates the negative ATPCadjustment event.

Table C-5 AM performance events


QPSKWS Indicates the workingduration of the QPSK mode.

IFH1

QAMWS16 Indicates the workingduration of the 16QAMmode.






C.1.2 Other Performance EventsIn addition to the SDH and microwave performance events, the OptiX RTN 605 supportsperformance events regarding the temperature.

Table C-6 Performance events regarding board temperature


BDTEMPMAX Indicates the maximumboard temperature.

ODU, and SCC


Maintenance Guide


Issue 03 (2010-05-30)


BDTEMPMIN Indicates the minimum boardtemperature.

BDTEMPCUR Indicates the current boardtemperature.


C.2 Performance Events and Handling ProceduresBased on the type of a performance event, this topic describes all the performance events on theOptiX RTN 605 and how to handle these performance events.

C.2.1 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 communications link degrades.Therefore, you must increase the transmit power of the ODU to maintain thecommunication quality.

l ATPC_N_ADJUST indicates the negative ATPC adjustment event.

This performance event indicates that the quality of a communication link becomes wellor the transmit power of the ODU is very large. Therefore, you can decrease the transmitpower of the ODU.

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 it does not affectservices. When the value of the performance event is larger, more adjustments are made.

When the factors that affect a communication link, such as sudden change of the weather, donot exist, and when the ATPC adjustment count is very large, the communication link may befaulty. You must check the communication link to prevent it from failure.



C-5

Relevant Alarms

None.

C.2.2 IF_BBE, IF_ES, IF_SES, IF_CSES, and IF_UAS

Descriptionl IF_BBE indicates the radio link background block error.

A BBE refers to the errored block excluding the errored block in the unavailable andseverely errored second.

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 certain second in which 30% or more than 30% errored blocks aredetected or at least one serious disturbance period (SDP) exists. The SDP refers to a periodof at least four consecutive blocks or 1 ms (whichever longer) in which the BER of all theconsecutive blocks is equal to or higher than 10-2 or the signal is lost.

l IF_CSES indicates the radio link consecutively severely errored second.

A CSES refers to a second in which an SES event occurs continuously for less than 10seconds.

l IF_UAS indicates the radio link unavailable second.

A UAS period is counted from the first second of 10 consecutive SES events. These tenseconds are considered to be a part of the unavailable time. A new available second periodstarts from the first second of ten consecutive non-SES events. These ten seconds areconsidered to be a part of the available time.

Attribute


Performance event cell IFCNT

Unit Block (IFBBE)Second (IFES, IFSES, IFCSES, and IFUAS)

Impact on SystemA small number of bit errors do not affect the services. In the case of excessive bit errors,however, the services are interrupted. Generally, the BER is less than 10-3 in the case of voiceservices, and 10-6 in the case of data services.

Relevant Alarms

the MW_BER_SD or MW_BER_EXC alarm is reported when the BER exceeds the specifiedthreshold.


Maintenance Guide


Issue 03 (2010-05-30)

Possible CausesThe system detects bit errors on the radio link through the bit error detection overheads in theoverheads of a microwave frame.

Procedure

Step 1 Check whether the MW_FEC_UNCOR or RPS_INDI alarm is reported.

If... Then...

The MW_FEC_UNCOR or RPS_INDI alarm isreported

See 5.3 Troubleshooting Radio Links.

The MW_FEC_UNCOR or RPS_INDI alarm isnot reported

Replace the IDU.

----End

C.2.3 TSL_MAX, TSL_MIN, TSL_CUR, and TSL_AVG

Descriptionl TSL_MAX indicates the maximum radio transmit signal level.

l TSL_MIN indicates the minimum radio transmit signal level.

l TSL_CUR indicates the current radio transmit signal level.

l TSL_AVG indicates the average radio transmit signal level.

AttributeAttribute Description

Performance event cell TSL

Unit dBm

Impact on SystemWhen the radio transmit signal level is very low or very high, the radio received signal level atthe opposite site is very low or very high. As a result, bit errors occur and even services areinterrupted.

Related AlarmsIf the radio transmit signal level is beyond the range supported by the ODU, theRADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.



C-7

C.2.4 RSL_MAX, RSL_MIN, RSL_CUR, and RSL_AVG

Descriptionl RSL_MAX indicates the maximum radio received signal level.

l RSL_MAX 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.

Attribute


Performance event cell RSL

Unit dBm

Impact on SystemWhen the radio received signal level is very low or very high, bit errors occur and even servicesare interrupted.

Relevant Alarms

If the radio received signal level exceeds the specified threshold, the RADIO_RSL_HIGH orRADIO_RSL_LOW alarm is reported.

C.2.5 RLHTT, RLLTT, TLHTT, and TLLTT

Descriptionl RLHTT indicates the duration when the ODU at the local end has a receive power lower

than the upper threshold.l RLLTT indicates the duration when the ODU at the local end has a receive power lower

than the lower threshold.l TLHTT indicates the duration when the ODU at the local end has a transit power higher

than the upper threshold.l TLLTT indicates the duration when the ODU at the local end has a transit power higher

than the lower threshold.

Attribute


Performance event cell RLHTS, RLLTS, TLHTS, and TLLTS

Unit Second


Maintenance Guide


Issue 03 (2010-05-30)

Impact on System

None.

Relevant Alarms

None.

C.2.6 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, andFEC_UNCOR_BLOCK_CNT

Descriptionl FEC_BEF_COR_ER indicates the BER before the FEC is performed.

This event indicates the impact of the external environment on the transmission.

l FEC_COR_BYTE_CNT indicates the number of bytes corrected through the FEC.

This event indicates the impact of the FEC.

l FEC_UNCOR_BLOCK_CN indicates the number of frames that cannot be correctedthrough the FEC.

This event indicates the number of error blocks after the FEC is performed.

Attribute


Performance event cell FECBEFCORER (FEC_BEF_COR_ER),FECUNCORBLOCKCNT(FEC_COR_BYTE_CNT), andFECUNCORBLOCKCNT(FEC_UNCOR_BLOCK_CNT)

Unit None (FEC_BEF_COR_ER)None (FEC_COR_BYTE_CNT)Block (FEC_UNCOR_BLOCK_CNT)

Impact on System

If the value of FEC_BEF_COR is very high, residual bit errors are generated after the FEC isperformed.

If the value of FEC_UNCOR_BLOCK_CNT is not zero, bit errors that cannot be corrected aregenerated on a radio link, and bit errors are generated in the service accordingly.

Relevant Alarms

If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.



C-9

C.2.7 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128,and QAMWS256

Descriptionl QPSKWS indicates the working duration of the QPSK mode.

l QAMWS16 indicates the working time of the 16QAM mode.





Attribute


Performance event cell QPSKWSSECOND (QPSKWS)QAMWS16SECOND (QAMWS16)QAMWS32SECOND (QAMWS32)QAMWS64SECOND (QAMWS64)QAMWS128SECOND (QAMWS128)QAMWS256SECOND (QAMWS256)

Unit Second

Impact on System

When the AM function is not enabled, the performance event does not affect the system.

When the AM function is enabled, in normal cases, the seconds of the modulation mode forensuring capacity account for a larger percentage. In the duration set for good weather, if theseconds of the low-efficiency modulation mode account for a larger percentage, the performanceof the radio link is abnormal.

Relevant Alarms

None.

C.2.8 BDTMPMAX, BDTMPMIN, and BDTMPCUR

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.


Maintenance Guide


Issue 03 (2010-05-30)

AttributeAttribute Description

Performance event cell None.

Unit °C

Impact on SystemIf the temperature of a board is very high or very low, the performance of the board degrades,and bit errors or other faults occur.

Relevant AlarmsIf the temperature of a board exceeds the specified threshold, the TEMP_ALARM alarm isreported.



C-11

D RMON Event Reference

RMON events reflect the running status of the Ethernet services. This topic describes all thepossible RMON events on the OptiX RTN 605 and how to handle these events.

D.1 List of RMON Alarm EntriesRMON alarm entries refer to the table entries in the RMON alarm group.

D.2 List of RMON Performance EntriesRMON performance entries refer to the table entries in the RMON statistics group or historygroup.

D.3 RMON Alarm Clearance ReferenceThis topic describes the RMON events of the OptiX RTN 605 and how to handle these events.

OptiX RTN 605Maintenance Guide D RMON Event Reference


D-1

D.1 List of RMON Alarm EntriesRMON alarm entries refer to the table entries in the RMON alarm group.

Table D-1 List of RMON alarm entries

Alarm Name Description Source

UndersizePkts Number of undersized packetsexceeding the threshold

EMS4, EM4T

OversizePkts Number of oversized packetsexceeding the threshold

Fragments Number of fragment packetsexceeding the threshold

Jabbers Number of jabber packets exceedingthe threshold

FCSErrors Number of packets with FCS errorsexceeding the threshold

D.2 List of RMON Performance EntriesRMON performance entries refer to the table entries in the RMON statistics group or historygroup.

Table D-2 List of RMON performance entries

Categoryof

Performance

Entries

Name of a Performance Entry Source

Basicperformance

Packets received (64 bytes in length)(packets)

EMS4, EM4T

Packets received (65-127 bytes inlength) (packets)




D RMON Event ReferenceOptiX RTN 605

Maintenance Guide

D-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

Categoryof

Performance

Entries

Name of a Performance Entry Source


Multicast packets received (packets)

Broadcast packets received (packets)

Undersized packets received(packets)

Oversized packets received (packets)

Packets received (packets)

Fragments received (packets)

Oversized error packets received(packets)

Extendedperformance

Unicast packets transmitted (packets) EMS4, EM4T

Pause frames received (frames)

Pause frames transmitted (frames)

FCS error frames (frames)

Packets transmitted (packets)

Unicast packets received (packets)

Multicast packets transmitted(packets)

Broadcast packets transmitted(packets)

Rate of good full-frame bytes received(bytes/second)

Rate of good full-frame bytestransmitted (bytes/second)

Good full-frame bytes received(bytes)

Good full-frame bytes transmitted(bytes)

NOTE

The OptiX RTN 605 1E/2E/1F/2F PORT and IFUP support basic performance and extended performance.



D-3

D.3 RMON Alarm Clearance ReferenceThis topic describes the RMON events of the OptiX RTN 605 and how to handle these events.

D.3.1 UndersizePkts

D.3.2 OversizePkts

D.3.3 Fragments

D.3.4 Jabbers

D.3.5 FCSErrors

D.3.1 UndersizePkts

Description

UndersizePkts indicates that an RMON threshold-crossing event is reported when the numberof packets that are shorter than 64 bytes and are received on the line side crosses the presetthreshold.

Impact on System

The data frames whose length is beyond the specific range are discarded. As a result, the systemservices are affected.

Possible Causes1. The length of a data frame that is received by the board is shorter than 64 bytes.2. The hardware of a local board is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits a packet that is shorter than 64 bytes.

If... Then...

The opposite equipment transmits a packet that isshorter than 64 bytes

Rectify the fault on the opposite NE.

The opposite end does not transmit a packet that isshorter than 64 bytes


Step 2 Replace the IDU.

----End

Relevant Informationl The length range of the data frames that are processed by each type of board is different.

The length of the data frames transmitted by the opposite end is within the normal range,


Maintenance Guide


Issue 03 (2010-05-30)

but it may be beyond the length range of the data frames that can be processed by the localend.

l Undersized frames may be relevant to services. The opposite equipment may change thelength of data frames by an operation such as encapsulation. As a result, a downstreamnode considers the data frames as undersized frames.

D.3.2 OversizePkts

DescriptionOversizePkts indicates that an RMON threshold-crossing event is reported when the number ofpackets that are longer than the MTU specified for the port and are received on the line sidecrosses the preset threshold.

Impact on SystemIf the length of a data frame received at a port is longer than the preset maximum frame length,the data frame is discarded and thus the system services are affected.

Possible Causes1. The length of an oversized frame configured for a board is shorter than the length of a frame

that is received by the board.2. The hardware of the local board is faulty.

Procedure

Step 1 Check whether the opposite equipment transmits a frame that is longer than the maximum frameof the local equipment.

If... Then...

The opposite equipment transmits a framethat is longer than the maximum framelength set for the local equipment

Notify the opposite equipment that the lengthof transmitted frames is changed.

The opposite equipment does not transmita frame that is longer than the maximumframe length set for the local equipment


Step 2 Replace the IDU.

----End

Relevant Informationl The length range of the data frames that are processed by each type of board is different.

The length of the data frames transmitted by the opposite end is within the normal range,but it may be beyond the length range of the data frames that can be processed by the localend.

l Oversized frames may be relevant to services. The opposite equipment may change thelength of data frames by an operation such as encapsulation. As a result, a downstreamnode considers the data frames as oversized frames.



D-5

D.3.3 Fragments

Description

Fragments indicates that an RMON threshold-crossing event is reported when the number ofreceived packets that are shorter than 64 bytes and have FCS or alignment errors exceeds thespecified upper threshold.

Impact on System

Data transmission is delayed or packet loss occurs.

Possible Causesl The working modes of the ports on the equipment at both ends are different from each

other.l The hardware of the local board is faulty.

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.

If... Then...

The working modes are the same Go to the next step.

The working modes are different fromeach other

Change the working mode of the port on thelocal equipment to ensure that the workingmodes of the ports on the equipment at bothends are the same.

Step 2 Replace the IDU. For details, see 6.1 Replacing the IDU.

----End

D.3.4 Jabbers

Description

Jabbers indicates that an RMON threshold-crossing event is reported when the received packetsare longer than 1518 bytes and have FCS or alignment errors.

Impact on System

Data transmission is delayed or packet loss occurs.


other.l The hardware of the local IDU is faulty.


Maintenance Guide


Issue 03 (2010-05-30)

Procedure

Step 1 Check whether the working modes of the ports on the equipment at both ends are the same.

If... Then...

The working modes are the same Go to the next step.

The working modes are different fromeach other

Change the working mode of the port on thelocal equipment to ensure that the workingmodes of the ports on the equipment at bothends are the same.


----End

D.3.5 FCSErrors

Description

FCSErrors indicates that the number of Ethernet data frames that contain FCS check errors(excluding the oversized and undersized frames) and are received by the local end exceeds thespecified threshold. FCSErrors includes FCSErrOv and FCSErrUd. FCSErrOv indicates that thenumber of Ethernet data frames that contain FCS check errors is higher than the upper threshold,and FCSErrUd indicates the number of Ethernet data frames that contain FCS check errors islower than the lower threshold.

Impact on System

Most boards discard the packets of FCS check errors. The system services are interrupted in theworst case.


other. For example, the port at one end works in half-duplex mode, and the port at the otherend works in half-duplex mode.

l The transmission line is of the poor quality and bit errors exist.

l The hardware of the local IDU is faulty.

Procedure

Step 1 Rectify the fault based on the alarm parameters.

If... Then...

The FCSErrUd performance event occurs Change the lower threshold to 0.

The FCSErrOv performance event occurs Go to the next step.

Step 2 If the FCSErrOv performance event occurs, on the NMS, check whether the working modes ofthe ports on the equipment at both ends are the same.



D-7

If... Then...

The ports on the equipment at both ends aredifferent from each other

Change the working modes of the ports on theequipment at both ends to ensure that they arethe same.

The ports on the equipment at both ends arethe same



----End

Relevant InformationAll the RMON performance events are threshold-crossing events. That is, you can check whetherthe count of RMON performance events in a sampling period exceeds the specified threshold.You can set the sampling period, which is defaulted to 10 seconds.


Maintenance Guide


Issue 03 (2010-05-30)

E Alarm Management

Alarm management of the OptiX RTN 605 is classified into NE alarm management and boardalarm management.

E.1 NE Alarm ManagementThe NE alarm management function set by a user is applicable to all the boards on an NE.

E.2 Board Alarm ManagementThe board alarm management function is valid for only a board on which a user configures thisfunction.

OptiX RTN 605Maintenance Guide E Alarm Management


E-1

E.1 NE Alarm ManagementThe NE alarm management function set by a user is applicable to all the boards on an NE.

The NE alarm management function of the OptiX RTN 605 includes:

l Sets the method for saving an alarm.

l Sets the delay of an alarm.

l Sets the reversion mode of an alarm.

For details about these functions, see the manuals or online Help of the NMS.

E.2 Board Alarm ManagementThe board alarm management function is valid for only a board on which a user configures thisfunction.

E.2.1 Setting the Alarm SeverityAlarms are classified into four severity levels: critical, major, minor, and warning. Themaintenance personnel can change the alarm severity by using the NMS.

E.2.2 Alarm SuppressionA board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need notbe monitored, the maintenance personnel can set alarm suppression.

E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately tothe NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarmquery is performed on the NMS. The maintenance personnel can change the setting as requiredon the NMS.

E.2.4 Alarm ReversionIf a port is not configured with a service, certain alarms may be reported. To filter the alarmsthat are not concerned, set these alarms to be reversed. In this manner, the alarm status at thisport is contrary to the actual status. That is, the status is displayed to be normal when an alarmis actually reported.

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified value, the board generatesa bit error alarm. This specified value is the bit error alarm threshold, and the setting of thisthreshold is supported by all the bit error threshold-crossing and degrading alarms on the OptiXRTN 605.

E.2.1 Setting the Alarm SeverityAlarms are classified into four severity levels: critical, major, minor, and warning. Themaintenance personnel can change the alarm severity by using the NMS.

This function is supported by all the boards.

E Alarm ManagementOptiX RTN 605

Maintenance Guide

E-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

E.2.2 Alarm SuppressionA board detects only the alarms whose Alarm Monitoring is set to Yes. If the alarms need notbe monitored, the maintenance personnel can set alarm suppression.


E.2.3 Alarm Auto-ReportIf Alarm Auto-Report is set to Reported, all the detected alarms are reported immediately tothe NMS. If Alarm Auto-Report is set to Not Report, the alarms are reported only when alarmquery is performed on the NMS. The maintenance personnel can change the setting as requiredon the NMS.


E.2.4 Alarm ReversionIf a port is not configured with a service, certain alarms may be reported. To filter the alarmsthat are not concerned, set these alarms to be reversed. In this manner, the alarm status at thisport is contrary to the actual status. That is, the status is displayed to be normal when an alarmis actually reported.

The alarm reversion function is available in three modes, namely, non-revertive, automaticreversion, and manual reversion.

l Non-revertive

In this mode, the alarms are monitored by default and alarm reversion cannot be enabledfor a port.

l Auto reversion

In this mode, alarm reversion can be enabled for a port where alarms are reported. Afteralarm reversion is enabled at a port, alarms are not reported. When the current alarm iscleared, the alarm reversion changes automatically to the disabled status. That is, the alarmreversion changes to the non-revertive mode. Then, the alarm reporting status at the portis the same as the actual status.

l Manual reversion

In this mode, alarm reversion can be enabled for a port regardless of whether any alarmsare reported at the port. After alarm reversion is enabled, the alarm reporting status at theport is the same as the actual status. After alarm reversion is manually disabled, the alarmreversion status changes to the non-revertive mode. Then, the alarm reporting status at theport is the same as the actual status.

Pay attention to the following points when you set the alarm reversion function:

l Alarm reversion does not change the actual status of alarms on the board, as well as theindication status of the alarm indicators.

l Alarm reversion is implemented by the NE software. The alarm data is the same on the NEand the NMS, which indicates the status after the alarm reversion. If you directly query thealarm data of a board, however, the actual alarm status is returned.

l Alarm reversion is set on the basis of a port. Alarm reversion is supported by each port ofthe PH1, and IF0.

OptiX RTN 605Maintenance Guide E Alarm Management


E-3

E.2.5 Setting of the Bit Error Alarm ThresholdWhen the number of bit errors detected by a board exceeds a specified value, the board generatesa bit error alarm. This specified value is the bit error alarm threshold, and the setting of thisthreshold is supported by all the bit error threshold-crossing and degrading alarms on the OptiXRTN 605.

Table E-1 Setting of the bit error alarm threshold

Alarm Name Default Alarm Threshold Applicable Board

MW_BER_EXC 10-3 IF0 and IFH1

MW_BER_SD 10-6

E Alarm ManagementOptiX RTN 605

Maintenance Guide

E-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

F Performance Event Management

Performance event management of the OptiX RTN 605 is classified into NE performance eventmanagement and board performance event management.

F.1 NE Performance Event ManagementThe NE performance event management function set by a user is applicable to all the boards onan NE.

F.2 Board Performance Event ManagementThe performance event management function is valid for only a board on which a user configuresthis function.

OptiX RTN 605Maintenance Guide F Performance Event Management


F-1

F.1 NE Performance Event ManagementThe NE performance event management function set by a user is applicable to all the boards onan NE.

The NE performance event management function supported by OptiX RTN 605 includes:

l Sets the monitoring of NE performance events

l Sets the start/end time of performance events

For details about these functions, see the manuals or online Help of the NMS.

F.2 Board Performance Event ManagementThe performance event management function is valid for only a board on which a user configuresthis function.

Table F-1 Board performance event management function

Function Applicable Board

Sets 15-minute/24-hourperformancemonitoring.

SCC, IF0, IFH1, ODU, EMS4, and EM4T

Sets 15-minute/24-hourperformance event auto-reporting.

SCC, IF0, IFH1, ODU, EMS4, and EM4T

Sets performancethresholds.

IFH1, IF0, EMS4, and EM4T

Resets the performanceregister.

IFH1, IF0, ODU, EMS4, and EM4T

Generates performancethreshold-crossingalarms.

IFH1, IF0, EMS4, and EM4T

Monitors UAT events. IFH1 and IF0

Monitors CSESperformance events.

IFH1 and IF0

F Performance Event ManagementOptiX RTN 605

Maintenance Guide

F-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

G Alarm Suppression Relationship

Table G-1 Suppression relationship between intra-board alarms

Alarm Identifier Identifier of the Suppressed Alarm

MW_LOF R_LOS, R_LOF, R_LOC,MW_FEC_UNCOR, MW_RDI,MW_LIM, MW_BER_EXC, andMW_BER_SD

R_LOS and R_LOC R_LOF, MW_RDI, MW_LIM,MW_BER_EXC, and MW_BER_SD

R_LOF MW_RDI, MW_LIM, MW_BER_EXC,and MW_BER_SD

T_ALOS E1_LOC and UP_E1_AIS

MW_BER_EXC MW_BER_SD

Table G-2 Suppression relationship between inter-board alarms

Alarm Identifier Identifier of the Suppressed Alarm

R_LOS, R_LOF, MW_LOF, andMW_LIM

DOWN_E1_AIS

OptiX RTN 605Maintenance Guide G Alarm Suppression Relationship


G-1

H Glossary

Terms are listed in an alphabetical order.

H.1 0-9

H.2 A-E

H.3 F-J

H.4 K-O

H.5 P-T

H.6 U-Z

OptiX RTN 605Maintenance Guide H Glossary


H-1

H.1 0-91+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection

SNC/trail and a permanent bridge. At the source end, the normal traffic signal ispermanently bridged to both the working and protection SNC/trail. At the sink end, thenormal traffic signal is selected from the better of the two SNCs/trails. Due to thepermanent bridging, the 1+1 architecture does not allow an extra unprotected trafficsignal to be provided.

1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)

802.1Q in 802.1Q 802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLANtag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to aframe with a private VLAN tag, making the frame encapsulated with two layers of VLANtags. The frame is forwarded over the service provider's backbone network based on thepublic VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQfeature enables the transmission of the private VLANs to the peer end transparently.

H.2 A-E

A

ABR See Available Bit Rate

ACAP See adjacent channel alternate polarization

Access Control List Access Control List (ACL) is a list of IP address. The addresses listed in the ACL areused for authentication. If the ACL for the user is not null, it indicates that the addresswhere the user logged in is contained in the list.

ACL See Access Control List

adaptive modulation A technology that is used to automatically adjust the modulation mode according to thechannel quality. When the channel quality is favorable, the equipment adopts a high-efficiency modulation mode to improve the transmission efficiency and the spectrumutilization of the system. When the channel quality is degraded, the equipment adoptsthe low-efficiency modulation mode to improve the anti-interference capability of thelink that carries high-priority services.

ADC See Analog to Digital Converter

add/drop multiplexer Add/Drop Multiplexing. Network elements that provide access to all or some subset ofthe constituent signals contained within an STM-N signal. The constituent signals areadded to (inserted), and/or dropped from (extracted) the STM-N signal as it passedthrough the ADM.

Address ResolutionProtocol

Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses toMAC addresses. It allows hosts and routers to determine the link layer addresses throughARP requests and ARP responses. The address resolution is a process in which the hostconverts the target IP address into a target MAC address before transmitting a frame.The basic function of the ARP is to query the MAC address of the target equipmentthrough its IP address.

H GlossaryOptiX RTN 605

Maintenance Guide

H-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2010-05-30)

adjacent channelalternate polarization

A channel configuration method, which uses two adjacent channels (a horizontalpolarization wave and a vertical polarization wave) to transmit two signals.

ADM See add/drop multiplexer

Administrative Unit The information structure which provides adaptation between the higher order path layerand the multiplex section layer. It consists of an information payload (the higher orderVC) and an AU pointer which indicates the offset of the payload frame start relative tothe multiplex section frame start.

AF See Assured Forwarding

AGC See Automatic Gain Control

aggregation A collection of objects that makes a whole. An aggregation can be a concrete orconceptual set of whole-part relationships among objects.

AIS See Alarm Indication Signal

Alarm automaticreport

When an alarm is generated on the device side, the alarm is reported to the N2000. Then,an alarm panel prompts and the user can view the details of the alarm.

alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.

Alarm Filtering An NE reports the detected alarm to the element management system (EMS). Based onthe filter state of the alarm, the EMS determines whether to display or save the alarminformation. If the filter state of an alarm is set to Filter, the alarm is not displayed orstored on the EMS. The alarm, however, is still monitored by the NE.

Alarm IndicationSignal

A code sent downstream in a digital network as an indication that an upstream failurehas been detected and alarmed. It is associated with multiple transport layers. Note: SeeITU-T Rec. G.707/Y.1322 for specific AIS signals.

Alarm suppression A function used not to monitor alarms for a specific object, which may be thenetworkwide equipment, a specific NE, a specific board and even a specific functionmodule of a specific board.

AM See adaptive modulation

Analog to DigitalConverter

An electronic circuit that converts continuous signals to discrete digital numbers. Thereverse operation is performed by a digital-to-analog converter (DAC).

APS See Automatic Protection Switching

ARP See Address Resolution Protocol

ASK amplitude shift keying

Assured Forwarding Assured Forwarding (AF) is one of the four per-hop behaviors (PHB) defined by theDiff-Serv workgroup of IETF. AF is suitable for certain key data services that requireassured bandwidth and short delay. For traffic within the limit, AF assures quality inforwarding. For traffic that exceeds the limit, AF degrades the service class and continuesto forward the traffic instead of discarding the packets.

AsynchronousTransfer Mode

A data transfer technology based on cell, in which packets allocation relies on channeldemand. It supports fast packet switching to achieve efficient utilization of networkresources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byteheader.

ATM See Asynchronous Transfer Mode

ATM PVC ATM Permanent Virtual Circuit



H-3

ATPC See automatic transmit power control

attenuator A device used to increase the attenuation of an Optical Fibre Link. Generally used toensure that the signal at the receive end is not too strong.

AU See Administrative Unit

Automatic GainControl

A process or means by which gain is automatically adjusted in a specified manner as afunction of a specified parameter, such as received signal level.

Automatic ProtectionSwitching

Automatic Protection Switching (APS) is the capability of a transmission system todetect a failure on a working facility and to switch to a standby facility to recover thetraffic.

automatic transmitpower control

A method of adjusting the transmit power based on fading of the transmit signal detectedat the receiver

Available Bit Rate A kind of service categories defined by the ATM forum. ABR only provides possibleforwarding service and applies to the connections that does not require the real-timequality. It does not provide any guarantee in terms of cell loss or delay.

B

Backward DefectIndication

When detecting a defect, the sink node of a LSP uses backward defect indication (BDI)to inform the upstream end of the LSP of a downstream defect along the return path.

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.

Base Station Controller A logical entity that connects the BTS with the MSC in a GSM network. It interworkswith the BTS through the Abis interface, the MSC through the A interface. It providesthe following functions: Radio resource management, Base station management, Powercontrol, Handover control, and Traffic measurement. One BSC controls and managesone or more BTSs in an actual network.

Base TransceiverStation

A Base Transceiver Station terminates the radio interface. It allows transmission of trafficand signaling across the air interface. The BTS includes the baseband processing, radioequipment, and the antenna.

BDI See Backward Defect Indication

BE See best effort

BER See Bit Error Rate

best effort A kind of PHB (Per-Hop-Behavior). In the forwarding process of a DS domain, the trafficof this PHB type features reachability but the DS node does not guarantee the forwardingquality.

BIOS Basic Input Output System

BIP Bit-Interleaved Parity

bit error An incompatibility between a bit in a transmitted digital signal and the correspondingbit in the received digital signal.

Bit Error Rate Bit error rate. Ratio of received bits that contain errors. BER is an important index usedto measure the communications quality of a network.


Maintenance Guide


Issue 03 (2010-05-30)

blank filler panel A piece of board to cover vacant slots, to keep the frame away from dirt, to keep properairflow inside the frame, and to beautify the frame appearance.

BPDU See Bridge Protocol Data Unit

Bridge Protocol DataUnit

The data messages that are exchanged across the switches within an extended LAN thatuses a spanning tree protocol (STP) topology. BPDU packets contain information onports, addresses, priorities and costs and ensure that the data ends up where it wasintended to go. BPDU messages are exchanged across bridges to detect loops in anetwork topology. The loops are then removed by shutting down selected bridgesinterfaces and placing redundant switch ports in a backup, or blocked, state.

Broadcast A means of delivering information to all members in a network. The broadcast range isdetermined by the broadcast address.

BSC See Base Station Controller

BTS See Base Transceiver Station

Buffer A storage area used for handling data in transit. Buffers are used in internetworking tocompensate for differences in processing speed between network devices. Bursts of datacan be stored in buffers until they can be handled by slower processing devices.

C

C-VLAN Customer VLAN

Cable distribution plate A component which is used to arrange the cables in order.

cable ladder (1) A cable ladder is a frame which supports electrical cables. (2) Two metal cablesusually made of stainless steel with rungs of lightweight metal tubing such as aluminum,six or eight inches wide spaced about eighteen inches apart. It can be rolled into a compactlightweight bundle for transport ease.

cable tie The tape used to bind the cables.

cabling trough The trough which is used for cable routing in the cabinet.

captive nut Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses butare more commonly used in the hobby for engine fixing (securing engine mounts to thefirewall), wing fixings, and undercarriage fixing.

CAR See committed access rate

CBR See Constant Bit Rate

CCC See Circuit Cross Connect

CCDP See Co-Channel Dual Polarization

CCM See continuity check message

CE See Customer Edge

Central ProcessingUnit

The CPU is the brains of the computer. Sometimes referred to simply as the processoror central processor, the CPU is where most calculations take place.

CES See Circuit Emulation Service

CF See compact flash

CGMP Cisco Group Management Protocol



H-5

CIR See Committed Information Rate

Circuit Cross Connect An implementation of MPLS L2VPN through the static configuration of labels.

Circuit EmulationService

A function with which the E1/T1 data can be transmitted through ATM networks. At thetransmission end, the interface module packs timeslot data into ATM cells. These ATMcells are sent to the reception end through the ATM network. At the reception end, theinterface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CEStechnology guarantees that the data in E1/T1 timeslots can be recovered to the originalsequence at the reception end.

CIST See Common and Internal Spanning Tree

CIST root A switch of the highest priority is elected as the root in an MSTP network.

Class of Service A class object that stores the priority mapping rules. When network congestion occurs,the class of service (CoS) first processes services by different priority levels from highto low. If the bandwidth is insufficient to support all services, the CoS dumps the servicesof low priority.

Clock tracing The method to keep the time on each node being synchronized with a clock source in anetwork.

Co-Channel DualPolarization

A channel configuration method, which uses a horizontal polarization wave and a verticalpolarization wave to transmit two signals. The Co-Channel Dual Polarization is twicethe transmission capacity of the single polarization.

Coarse WavelengthDivision Multiplexing

A signal transmission technology that multiplexes widely-spaced optical channels intothe same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDMdoes not support optical amplifiers and is applied in short-distance chain networking.

Colored packet A packet whose priority is determined by defined colors.

Combined cabinet Two or multiple BTS cabinets of the same type are combined to serve as one BTS.

committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.CAR is a configurable method by which incoming and outgoing packets can be classifiedinto QoS (Quality of Service) groups, and by which the input or output transmission ratecan be defined.

CommittedInformation Rate

The rate at which a frame relay network agrees to transfer information in normalconditions. Namely, it is the rate, measured in bit/s, at which the token is transferred tothe leaky bucket.

Common and InternalSpanning Tree

Common and Internal Spanning Tree. The single Spanning Tree calculated by STP andRSTP together with the logical continuation of that connectivity through MST Bridgesand regions, calculatedby MSTP to ensure that all LANs in the Bridged Local AreaNetwork are simply and fully connected.

compact flash Compact flash (CF) was originally developed as a type of data storage device used inportable electronic devices. For storage, CompactFlash typically uses flash memory ina standardized enclosure.

Concatenation A process that combines multiple virtual containers. The combined capacities can beused a single capacity. The concatenation also keeps the integrity of bit sequence.

connecting plate forcombining cabinets

A plate that connects two adjacent cabinet together at the cabinet top for fixing.


Maintenance Guide


Issue 03 (2010-05-30)

Connectivity Check Ethernet CFM can detect the connectivity between MEPs. The detection is achieved byeach MEP transmitting a Continuity Check Message (CCM) periodically. This detectionis called CC detection.

Constant Bit Rate constant bit rate. A kind of service categories defined by the ATM forum. CBR transferscells based on the constant bandwidth. It is applicable to service connections that dependon precise clocking to ensure undistorted transmission.

Constraint ShortestPath First

An extension of shortest path algorithms like OSPF and IS-IS. The path computed usingCSPF is a shortest path fulfilling set of constrains. It simply means that it runs shortestpath algorithm after pruning those links that violate a given set of constraints. Aconstraint could be minimum bandwidth required per link (also know as bandwidthguaranteed constraint), end-to-end delay, maximum number of link traversed etc. CSPFis widely used in MPLS Traffic Engineering. The routing using CSPF is known asConstraint Based Routing (CBR).

Constraint-basedRouted-LabelDistribution Protocol

An alternative to RSVP (Resource ReSerVation Protocol) in MPLS (MultiProtocolLabel Switching) networks. RSVP, which works at the IP (Internet Protocol) level, usesIP or UDP datagrams to communicate between LSR (Label Switched Routing) peers.RSVP does not require the maintenance of TCP (Transmission Control Protocol)sessions, although RSVP must assume responsibility for error control. CR-LDP isdesigned to facilitate the routing of LSPs (Label Switched Paths) through TCP sessionsbetween LSR peers through the communication of label distribution messages duringthe session.

continuity checkmessage

CCM is used to detect the link status.

corrugated tube A pipe which is used for fiber routing.

CoS See Class of Service

CPU See Central Processing Unit

CR-LDP See Constraint-based Routed-Label Distribution Protocol

CRC See Cyclic Redundancy Check

cross polarizationinterferencecancellation

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.

CSPF See Constraint Shortest Path First

Customer Edge A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to theService Provider (SP) network. A CE can be a router, switch, or host.

CWDM See Coarse Wavelength Division Multiplexing

Cyclic RedundancyCheck

A procedure used in checking for errors in data transmission. CRC error checking usesa complex calculation to generate a number based on the data transmitted. The sendingdevice performs the calculation before transmission and includes it in the packet that itsends to the receiving device. The receiving device repeats the same calculation aftertransmission. If both devices obtain the same result, it is assumed that the transmissionwas error free. The procedure is known as a redundancy check because each transmissionincludes not only data but extra (redundant) error-checking values.



H-7

D

Data Circuit-terminalEquipment

Also Data Communications Equipment (DCE) and Data Carrier Equipment (DCE). Thebasic function of a DCE is to convert data from one interface, such as a digital signal, toanother interface, such as an analog signal. One example of DCE is a modem.

Data CommunicationNetwork

A communication network used in a TMN or between TMNs to support the DataCommunication Function (DCF).

Data CommunicationsChannel

The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal totransmit information on operation, management, maintenance and provision (OAM&P)between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12is referred to as the 576 kbit/s DCC-M channel.

Datagram A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram,UDP datagram.

DC See Direct Current

DC-C See DC-Return Common (with Ground)

DC-I See DC-Return Isolate (with Ground)

DC-Return Common(with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited withthe PGND on the output side of the power supply cabinet and also on the line betweenthe output of the power supply cabinet and the electric equipment.

DC-Return Isolate(with Ground)

A power system, in which the BGND of the DC return conductor is short-circuited withthe PGND on the output side of the power supply cabinet and is isolated from the PGNDon the line between the output of the power supply cabinet and the electric equipment.

DCC See Data Communications Channel

DCE See Data Circuit-terminal Equipment

DCN See Data Communication Network

DDF See Digital Distribution Frame

DDN See Digital Data Network

DE See discard eligible

Detour LSP The LSP that is used to re-route traffic around a failure in one-to-one backup.

diamond-shaped nut A type of nut that is used to fasten the wiring frame to the cabinet.

Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a seriesof functional units implemented at the network nodes, including a small group of per-hop forwarding behaviors, packet classification functions, and traffic conditioningfunctions such as metering, marking, shaping and policing.

Differentiated ServicesCode Point

Differentiated Services CodePoint. A marker in the header of each IP packet using bits0-6 in the DS field. Routers provide differentiated classes of services to various servicestreams/flows based on this marker. In other words, routers select corresponding PHBaccording to the DSCP value.

DiffServ See Differentiated Services

Digital Data Network A high-quality data transport tunnel that combines the digital channel (such as fiberchannel, digital microwave channel, or satellite channel) and the cross multiplextechnology.


Maintenance Guide


Issue 03 (2010-05-30)

Digital DistributionFrame

A type of equipment used between the transmission equipment and the exchange withtransmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,cable patching, and test of loops that transmitting digital signals.

digital modulation A digital modulation controls the changes in amplitude, phase, and frequency of thecarrier based on the changes in the baseband digital signal. In this manner, theinformation can be transmitted by the carrier.

Direct Current Electrical current whose direction of flow does not reverse. The current may stop orchange amplitude, but it always flows in the same direction.

discard eligible A bit in the frame relay header. It indicates the priority of a packet. If a node supportsthe FR QoS, the rate of the accessed FR packets is controlled. When the packet trafficexceeds the specified traffic, the DE value of the redundant packets is set to 1. In thecase of network congestion, the packets with DE value as 1 are discarded at the node.

Distance VectorMulticast RoutingProtocol

Distance Vector Multicast Routing Protocol. The DVMRP protocol is an Internetgateway protocol mainly based on the RIP. The protocol implements a typical densemode IP multicast solution. The DVMRP protocol uses IGMP to exchange routingdatagrams with its neighbors.

DS boundary node A DS node that connects one DS domain to a node either in another DS domain or in adomain that is not DS-capable.

DS domain In the DifferServ mechanism, the DS domain is a domain consisting of a group ofnetwork nodes that share the same service provisioning policy and same PHB. It providespoint-to-point QoS guarantees for services transmitted over this domain.

DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.

DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior node.

DSCP See Differentiated Services Code Point

dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio wavesorthogonally polarized.

DVMRP See Distance Vector Multicast Routing Protocol

E

E-AGGR Ethernet-Aggregation

E-LAN See Ethernet LAN

E-Tree See Ethernet-Tree

EBS See Excess Burst Size

ECC See Embedded Control Channel

EF See Expedited Forwarding

EFM See Ethernet in the First mile

Electro MagneticInterference

Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades orlimits the effective performance of electronics/electrical equipment.



H-9

electromagneticcompatibility

Electromagnetic compatibility is the condition which prevails when telecommunicationsequipment is performing its individually designed function in a common electromagneticenvironment without causing or suffering unacceptable degradation due to unintentionalelectromagnetic interference to or from other equipment in the same environment.[NTIA]

ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at differentelectrical potentials caused by direct contact or induced by an electrostatic field.

Embedded ControlChannel

An ECC provides a logical operations channel between SDH NEs, utilizing a datacommunications channel (DCC) as its physical layer.

EMC See electromagnetic compatibility

EMI See Electro Magnetic Interference

Engineering label A mark on a cable, a subrack, or a cabinet for identification.

EPLn See Ethernet Private LAN

equalization A method of avoiding selective fading of frequencies. Equalization can compensate forthe changes of amplitude frequency caused by frequency selective fading.

ERPS See ethernet ring protection switching

ES-IS End System to Intermediate System

ESD See ElectroStatic Discharge

ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf orcabinet to the insertion of ESD wrist strap.

ETH-CC Ethernet Continuity Check

ETH-LB Ethernet Loopback

ETH-LT Ethernet Link Trace

Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/CollisionDetection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..

Ethernet in the Firstmile

Last mile access from the broadband device to the user community. The EFM takes theadvantages of the SHDSL.bis technology and the Ethernet technology. The EFMprovides both the traditional voice service and internet access service of high speed. Inaddition, it meets the users' requirements on high definition television system (HDTV)and Video On Demand (VOD).

Ethernet LAN Ethernet LAN. A L2VPN service type that is provided for the user Ethernet in differentdomains over the PSN network. For the user Ethernet, the entire PSN network serves asa Layer 2 switch.

Ethernet Private LAN Both a LAN service and a private service. Transport bandwidth is never shared betweendifferent customers.

ethernet ringprotection switching

protection switching mechanisms for ETH layer Ethernet ring topologies.

Ethernet VirtualPrivate LAN

A service that is both a LAN service and a virtual private service.

Ethernet-Tree etherenet tree. An Ethernet service type that is based on a Point-to-multipoint EthernetVirtual Connection.


Maintenance Guide


Issue 03 (2010-05-30)

ETS European Telecommunication Standards

ETSI See European Telecommunications Standards Institute

ETSI 300mm cabinet A cabinet which is 600mm in width and 300mm in depth, compliant with the standardsof the ETSI.

EuropeanTelecommunicationsStandards Institute

A standards-setting body in Europe. Also the standards body responsible for GSM.

EVPL Ethernet Virtual Private Line

EVPLn See Ethernet Virtual Private LAN

Excess Burst Size excess burst size. In the single rate three color marker (srTCM) mode, the traffic controlis realized by the token buckets C and E. Excess burst size is a parameter used to definethe capacity of token bucket E, that is, the maximum burst IP packet size when theinformation is transferred at the committed information rate. This parameter must belarger than 0. It is recommended that this parameter should be not less than the maximumlength of the IP packet that might be forwarded.

Exercise Switching An operation to check if the protection switching protocol functions normally. Theprotection switching is not really performed.

Expedited Forwarding Expedited Forwarding (EF) is the highest order QoS in the Diff-Serv network. EF PHBis suitable for services that demand low packet loss ratio, short delay, and broadbandwidth. In all the cases, EF traffic can guarantee a transmission rate equal to or fasterthan the set rate. The DSCP value of EF PHB is "101110".

H.3 F-J

F

Failure If the fault persists long enough to consider the ability of an item with a required functionto be terminated. The item may be considered as having failed; a fault has now beendetected.

Fast Ethernet A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies withthe IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard.

fast link pulse The likn pulse that is used to encode information during automatic negotiation.

FCS Frame Check Sequence

FD See frequency diversity

FDI See Forward Defect Indication

FE See Fast Ethernet

FEC See Forward Error Correction

FFD Fast Failure Detection

Fiber Connector A device installed at the end of a fiber, optical source or receive unit. It is used to couplethe optical wave to the fiber when connected to another device of the same type. Aconnector can either connect two fiber ends or connect a fiber end and a optical source(or a detector).



H-11

fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and forconnections between subracks or inside a subrack.

Field ProgrammableGate Array

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 arraies.

FIFO See First in First out

File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computerson the Internet. Both computers must support their respective FTP roles: one must be anFTP client and the other an FTP server.

First in First out A stack management mechanism. The first saved data is first read and invoked.

FLP See fast link pulse

Forced switch This function forces the service to switch from the working channel to the protectionchannel, with the service not to be restored automatically. This switch occurs regardlessof the state of the protection channels or boards, unless the protection channels or boardsare satisfying a higher priority bridge request.

Forward DefectIndication

Forward defect indication (FDI) is generated and traced forward to the sink node of theLSP by the node that first detects defects. It includes fields to indicate the nature of thedefect and its location. Its primary purpose is to suppress alarms being raised at affectedhigher level client LSPs and (in turn) their client layers.

Forward ErrorCorrection

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.

Forwarding plane Also referred to as the data plane. The forwarding plane is connection-oriented, and canbe used in Layer 2 networks such as an ATM network.

FPGA See Field Programmable Gate Array

Fragment Piece of a larger packet that has been broken down to smaller units.

Fragmentation Process of breaking a packet into smaller units when transmitting over a network mediumthat can not support the original size of the packet.

frame A frame, starting with a header, is a string of bytes with a specified length. Frame lengthis represented by the sampling circle or the total number of bytes sampled during a circle.A header comprises one or a number of bytes with pre-specified values. In other words,a header is a code segment that reflects the distribution (diagram) of the elements pre-specified by the sending and receiving parties.

frequency diversity A diversity scheme that enables two or more microwave frequencies with a certainfrequency interval are used to transmit/receive the same signal and selection is thenperformed between the two signals to ease the impact of fading.

FTP See File Transfer Protocol

Full duplex The system that can transmit information in both directions on a communication link.Onthe communication link, both parties can send and receive data at the same time.


Maintenance Guide


Issue 03 (2010-05-30)

G

gateway networkelement

A network element that is used for communication between the NE application layer andthe NM application layer

GCP See GMPLS control plan

GE See Gigabit Ethernet

Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This isto adapt the traffic to network resources that can be provided by the downstream routerto avoid packet discarding and congestion.

GFP Generic Framing Procedure

Gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.Itruns at 1000Mbit/s. Gigabit Ethernet uses a private medium, and it does not supportcoaxial cables or other cables. It also supports the channels in the bandwidth mode. IfGigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge(switch) or a router as the center, it gives full play to the performance and the bandwidth.In the network structure, Gigabit Ethernet uses full duplex links that are private, causingthe length of the links to be sufficient for backbone applications in a building and campus.

Global PositioningSystem

A global navigation satellite system. It provides reliable positioning, navigation, andtiming services to worldwide users .

GMPLS control plan The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei.The OptiX GCP applies to the OptiX OSN product series. By using this software, thetraditional network can evolve into the ASON network. The OptiX OSN product seriessupport the ASON features.

GNE See gateway network element

GPS See Global Positioning System

GR See Graceful Restart

Graceful Restart In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/MPLS) such as Open Shortest Path First (OSPF), Intermediate System-IntermediateSystem (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP),and Resource Reservation Protocol (RSVP) are extended to ensure that the forwardingis not interrupted when the system is restarted. This reduces the flapping of the protocolsat the control plane when the system performs the active/standby switchover. This seriesof standards is called Graceful Restart.

Graphical UserInterface

A visual computer enviroment that represents programs, files, and options with graphicalimages, such as icons, menus, and dialog boxes, on the screen.

ground resistance (electricity) Opposition of the earth to the flow of current through it; its value dependson the nature and moisture content of the soil, on the material, composition, and natureof connections to the earth, and on the electrolytic action present.

GTS See Generic traffic shaping

GUI See Graphical User Interface

guide rail Components to guide, position, and support plug-in boards.



H-13

H

H-QoS Hierarchical Quality of Service

HA See High Availability

half-duplex A transmitting mode in which a half-duplex system provides for communication in bothdirections, but only one direction at a time (not simultaneously). Typically, once a partybegins receiving a signal, it must wait for the transmitter to stop transmitting, beforereplying.

HDB3 High Density Bipolar Code 3

HDLC See High level Data Link Control procedure

High Availability The ability of a system to continuously perform its functions during a long period, whichmay exceeds the suggested working time of the independent components. You can obtainthe high availability (HA) by using the error tolerance method. Based on learning casesone by one, you must also clearly understand the limitations of the system that requiresan HA ability and the degree to which the ability can reach.

High level Data LinkControl procedure

A data link protocol from ISO for point-to-point communications over serial links.Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocolsincluding X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLChave been developed under the name of Link Access Procedure (LAP).

High Speed DownlinkPacket Access

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.

Hold priority The priority of the tunnel with respect to holding resources, ranging from 0 (indicatesthe highest priority) to 7. It is used to determine whether the resources occupied by thetunnel can be preempted by other tunnels.

Hop A network connection between two distant nodes. For Internet operation a hop representsa small step on the route from one main computer to another.

hot standby A mechanism of ensuring device running security. The environment variables andstorage information of each running device are synchronized to the standby device. Whenthe faults occur on the running device, the standby device can take over the services inthe faulty device in automatic or manual way to ensure the normal running of the entiresystem.

HP Higher Order Path

HSDPA See High Speed Downlink Packet Access

HSM Hitless Switch Mode

HTB High Tributary Bus

hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supportsthe AM function.

I

ICMP See Internet Control Messages Protocol

IDU See indoor unit


Maintenance Guide


Issue 03 (2010-05-30)

IEC See International Electrotechnical Commission

IEEE See Institute of Electrical and Electronics Engineers

IETF The Internet Engineering Task Force

IF See intermediate frequency

IGMP See Internet Group Management Protocol

IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol managesand controls the multicast group by listening to and analyze the Internet GroupManagement Protocol (IGMP) packet between hosts and layer 3 devices. In this manner,the spread of the multicast data on layer 2 network can be prevented efficiently.

IMA See Inverse Multiplexing over ATM

indoor unit The indoor unit of the split-structured radio equipment. It implements accessing,multiplexing/demultiplexing, and IF processing for services.

Inloop A method of looping the signals from the cross-connect unit back to the cross-connectunit.

Institute of Electricaland ElectronicsEngineers

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.

Interface board area The area for the interface boards on the subrack.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RFsignal.

Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generateroutes.

Intermediate System toIntermediate System

A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol(IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF)algorithm to calculate the route.

Internal Spanning Tree Internal spanning tree. A segment of CIST in a certain MST region. An IST is a specialMSTI whose ID is 0.

InternationalElectrotechnicalCommission

The International Electrotechnical Commission (IEC) is an international and non-governmental standards organization dealing with electrical and electronical standards.

InternationalOrganization forStandardization

ISO (International Organization for Standardization) is the world's largest developer andpublisher of International Standards.

Internet ControlMessages Protocol

ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messagesduring the transmission of IP-type data packets.

Internet GroupManagement Protocol

The protocol for managing the membership of Internet Protocol multicast groups amongthe TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establishand maintain multicast group memberships.

Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sentacross an internet and provides the basis for connectionless, best-effort packet deliveryservice. IP includes the ICMP control and error message protocol as an integral part. Theentire protocol suite is often referred to as TCP/IP because TCP and IP are the twofundamental protocols. IP is standardized in RFC 791.



H-15

Internet ProtocolVersion 6

A update version of IPv4. It is also called IP Next Generation (IPng). The specificationsand standardizations provided by it are consistent with the Internet Engineering TaskForce (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of theInternet Protocol, designed as the successor to IPv4. The specifications andstandardizations provided by it are consistent with the Internet Engineering Task Force(IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits whilean IPv6 address has 128 bits.

Inverse Multiplexingover ATM

Inverse Multiplexing over ATM. The ATM inverse multiplexing technique involvesinverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among linksgrouped to form a higher bandwidth logical link whose rate is approximately the sum ofthe link rates. This is referred to as an IMA group.

IP See Internet Protocol

IPv6 See Internet Protocol Version 6

IS-IS See Intermediate System to Intermediate System

ISO See International Organization for Standardization

IST See Internal Spanning Tree

ITU-T International Telecommunication Union - Telecommunication Standardization Sector

IVL Independence VLAN learning

J

Jitter Short waveform variations caused by vibration, voltage fluctuations, and control systeminstability.

H.4 K-O

L

L2VPN See Layer 2 virtual private network

Label Switched Path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through labelswitching mechanisms. A label-switched path can be chosen dynamically, based onnormal routing mechanisms, or through configuration.

Label Switching Router The Label Switching Router (LSR) is the basic element of MPLS network. All LSRssupport the MPLS protocol. The LSR is composed of two parts: control unit andforwarding unit. The former is responsible for allocating the label, selecting the route,creating the label forwarding table, creating and removing the label switch path; the latterforwards the labels according to groups received in the label forwarding table.

LACP See Link Aggregation Control Protocol

LAG See link aggregation group

LAN See Local Area Network

LAPD Link Access Procedure on the D channel

LAPS Link Access Procedure-SDH


Maintenance Guide


Issue 03 (2010-05-30)

Laser A component that generates directional optical waves of narrow wavelengths. The laserlight has better coherence than ordinary light. The fiber system takes the semi-conductorlaser as the light source.

layer 2 switch A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmitsand distributes packet data based on the MAC address. Since the MAC address is thesecond layer of the OSI model, this data forwarding method is called layer 2 switch.

Layer 2 virtual privatenetwork

A virtual private network realized in the packet switched (IP/MPLS) network by Layer2 switching technologies.

LB See Loopback

LCAS See Link Capacity Adjustment Scheme

LDPC Low-Density Parity Check code

line rate forwarding The line rate equals the maximum transmission rate capable on a given type of media.

Link AggregationControl Protocol

Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad)that allows you to bundle several physical ports to form a single logical channel. LACPallows a switch to negotiate an automatic bundle by sending LACP packets to the peer.

link aggregation group An aggregation that allows one or more links to be aggregated together to form a linkaggregation group so that a MAC clientcan treat the link aggregation group as if it werea single link.

Link CapacityAdjustment Scheme

The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamicprovisioning of bandwidth, using VCAT, to meet customer requirements.

Link Protection Protection provided by the bypass tunnel for the link on the working tunnel. The link isa downstream link adjacent to the PLR. When the PLR fails to provide node protection,the link protection should be provided.

LMSP Linear Multiplex Section Protection

Local Area Network 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).

Locked switching When the switching condition is satisfied, this function disables the service from beingswitched from the working channel to the protection channel. When the service has beenswitched, the function enables the service to be restored from the protection channel tothe working channel.

LOF See Loss Of Frame

LOM Loss Of Multiframe

Loopback A troubleshooting technique that returns a transmitted signal to its source so that thesignal or message can be analyzed for errors.

LOP See Loss Of Pointer

LOS See Loss Of Signal

Loss Of Frame A condition at the receiver or a maintenance signal transmitted in the PHY overheadindicating that the receiving equipment has lost frame delineation. This is used to monitorthe performance of the PHY layer.



H-17

Loss Of Pointer Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in thePHY overhead indicating that the receiving equipment has lost the pointer to the start ofcell in the payload. This is used to monitor the performance of the PHY layer.

Loss Of Signal Loss of signal (LOS) indicates that there are no transitions occurring in the receivedsignal.

Lower subrack The subrack close to the bottom of the cabinet when a cabinet contains several subracks.

LP Lower Order Path

LPT Link State Path Through

LSP See Label Switched Path

LSR See Label Switching Router

M

MA See Maintenance Association

MAC See Medium Access Control

MAC See Media Access Control

MADM Multi Add-Drop Multiplexer

MaintenanceAssociation

That portion of a Service Instance, preferably all of it or as much as possible, theconnectivity of which is maintained by CFM. It is also a full mesh of MaintenanceEntities.

Maintenanceassociation End Point

A MEP is an actively managed CFM Entity, associated with a specific DSAP of a ServiceInstance, which can generate and receive CFM frames and track any responses. It is anend point of a single Maintenance Association, and terminates a separate MaintenanceEntity for each of the other MEPs in the same Maintenance Association.

Maintenance Domain The Maintenance Domain (MD) refers to the network or the part of the network for whichconnectivity is managed by CFM. The devices in an MD are managed by a single ISP.

Maintenance Point Maintenance Point (MP) is one of either a MEP or a MIP.

ManagementInformation Base

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.

Manual switching A protection switching. When the protection path is normal and there is no request of ahigher level switching, the service is manually switched from the working path to theprotection path, to test whether the network still has the protection capability.

Maximum TransferUnit

The MTU (Maximum Transmission Unit) is the size of the largest datagram that can besent over a network.

MBS Maximum Burst Size

MCF See Message Communication Function

MD See Maintenance Domain

MDI See Medium Dependent Interface

Mean Time To Repair The average time that a device will take to recover from a failure.


Maintenance Guide


Issue 03 (2010-05-30)

Media Access Control 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.

Medium AccessControl

A general reference to the low-level hardware protocols used to access a particularnetwork. The term MAC address is often used as a synonym for physical addresses.

Medium DependentInterface

The electrical and mechanical interface between the equipment and the mediatransmission.

MEP See Maintenance association End Point

MessageCommunicationFunction

The MCF is composed of a protocol stack that allows exchange of managementinformation with their prs .

MIB See Management Information Base

MIP Maintenance Intermediate Point

MLPPP See Multi-link Point to Point Protocol

mount angle An L-shape steel sheet. One side is fixed on the front panel with screws, and the otherside is fixed on the installation hole with screws. On both sides of a rack, there is an L-shaped metal fastener. This ensures that internal components are closely connected withthe rack. Normally, an internal component is installed with two mount angles.

MP See Maintenance Point

MPID Maintenance Point Identification

MPLS See Multi-Protocol Label Switch

MPLS L2VPN The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network.Inthis case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs ofdifferent media types, such as ATM, FR, VLAN, Ethernet, and PPP.

MPLS OAM The MPLS OAM provides continuity check for a single LSP, and provides a set of faultdetection tools and fault correct mechanisms for MPLS networks. The MPLS OAM andrelevant protection switching components implement the detection function for the CR-LSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs.In this way, the impact of a fault can be lowered to the minimum.

MPLS TE Multiprotocol Label Switching Traffic Engineering

MPLS TE tunnel In the case of reroute deployment, or when traffic needs to be transported throughmultiple trails, multiple LSP tunnels might be used. In traffic engineering, such a groupof LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has twoidentifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquelydefine the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE orFILTER_SPEC object.

MS See Multiplex Section

MSP See multiplex section protection



H-19

MSTI See Multiple Spanning Tree Instance

MSTP See Multiple Spanning Tree Protocol

MTBF Mean Time Between Failure

MTTR See Mean Time To Repair

MTU See Maximum Transfer Unit

Multi-link Point toPoint Protocol

A protocol used in ISDN connections. MLPPP lets two B channels act as a single line,doubling connection rates to 128Kbps.

Multi-Protocol LabelSwitch

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.

Multicast A process of transmitting packets of data 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.

Multiple SpanningTree Instance

Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTPwithin an MST Region, to provide a simply and fully connected active topology forframes classified as belonging to a VLAN that is mapped to the MSTI by the MSTConfiguration. A VLAN cannot be assigned to multiple MSTIs.

Multiple SpanningTree Protocol

Multiple spanning tree protocol. The MSTP can be used in a loop network. Using analgorithm, the MSTP blocks redundant paths so that the loop network can be trimmedas a tree network. In this case, the proliferation and endless cycling of packets is avoidedin the loop network.The protocol that introduces the mapping between VLANs andmultiple spanning trees. This solves the problem that data cannot be normally forwardedin a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.

Multiple SpanningTree Region

The MST region consists of switches that support the MSTP in the LAN and links amongthem. Switches physically and directly connected and configured with the same MSTregion attributes belong to the same MST region. The attributes for the same MST regionare as follows: Same region name Same revision level Same mapping relation betweenthe VLAN ID to MSTI

Multiplex Section The trail between and including two multiplex section trail termination functions.

multiplex sectionprotection

A function, which is performed to provide capability for switching a signal between andincluding two multiplex section termination (MST) functions, from a "working" to a"protection" channel.

N

N+1 protection A radio link protection system composed of N working channels and one protectionchannel.

NE See Network Element

NE Explorer The main operation interface, of the U2000, which is used to manage the OptiXequipment. In the NE Explorer, the user can configure, manage and maintain the NE,boards, and ports on a per-NE basis.


Maintenance Guide


Issue 03 (2010-05-30)

Network Element A network element (NE) contains both the hardware and the software running on it. OneNE is at least equipped with one system control board which manages and monitors theentire network element. The NE software runs on the system control board.

network managementsystem

The network management system in charge of the operation, administration, andmaintenance of a network.

Network Service AccessPoint

A network address defined by ISO, through which entities on the network layer canaccess OSI network services.

Network to NetworkInterface

This is an internal interface within a network linking two or more elements.

next hop The next router to which a packet is sent from any given router as it traverses a networkon its journey to its final destination.

NLP Normal Link Pulse

NMS See network management system

NNHOP Next-Next-Hop

NNI See Network to Network Interface

Node A node stands for a managed device in the network.For a device with a single frame, onenode stands for one device.For a device with multiple frames, one node stands for oneframe of the device.Therefore, a node does not always mean a device.

Node Protection A parameter of the FRR protection. It indicates that the bypass tunnel should be able toprotect the downstream node that is involved in the working tunnel and adjacent to thePLR. The node cannot be a merge point, and the bypass tunnel should also be able toprotect the downstream link that is involved in the working tunnel and adjacent to thePLR.

non-gateway networkelement

A network element whose communication with the NM application layer must betransferred by the gateway network element application layer.

non-GNE See non-gateway network element

NSAP See Network Service Access Point

NSF Not Stop Forwarding

NSMI Network Serial Multiplexed Interface

O

OAM See Operation, Administration and Maintenanc

ODF See Optical Distribution Frame

ODU See outdoor unit

One-to-One Backup A local repair method in which a backup tunnel is separately created for each protectedtunnel at a PLR.

Open Shortest PathFirst

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 of the network topology which is identical on all routersin the area.



H-21

Open SystemsInterconnection

A standard or "reference model" (officially defined by the International Organization ofStandards (ISO)) for how messages should be transmitted between any two points in atelecommunication network. The reference model defines seven layers of functions thattake place at each end of a communication.

Operation,Administration andMaintenanc

Operation, Administration and Maintenance. A group of network support functions thatmonitor and sustain segment operation, activities that are concerned with, but not limitedto, failure detection, notification, location, and repairs that are intended to eliminate faultsand keep a segment in an operational state and support activities required to provide theservices of a subscriber access network to users/subscribers.

Optical DistributionFrame

A frame which is used to transfer and spool fibers.

orderwire A channel that provides voice communication between operation engineers ormaintenance engineers of different stations.

OSI See Open Systems Interconnection

OSP OptiX Software Platform

OSPF See Open Shortest Path First

outdoor unit The outdoor unit of the split-structured radio equipment. It implements frequencyconversion and amplification for RF signals.

Outloop A method of looping back the input signals received at an port to an output port withoutchanging the structure of the signals.

Output optical power The ranger of optical energy level of output signals.

H.5 P-T

P

Packet over SDH/SONET

A MAN and WAN technology that provides point-to-point data connections. The POSinterface uses SDH/SONET as the physical layer protocol, and supports the transport ofpacket data (such as IP packets) in MAN and WAN.

packet switchednetwork

A telecommunication network which works in packet switching mode.

Packing case A case which is used for packing the board or subrack.

Path/Channel A logical connection between the point at which a standard frame format for the signalat the given rate is assembled, and the point at which the standard frame format for thesignal is disassembled.

PBS See peak burst size

PCB See Printed Circuit Board

PCI bus PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bitfor interconnecting chips, expansion boards, and processor/memory subsystems.

PDH See Plesiochronous Digital Hierarchy

PDU Protocol Data Unit

PE See Provider Edge


Maintenance Guide


Issue 03 (2010-05-30)

peak burst size A parameter used to define the capacity of token bucket P, that is, the maximum burstIP packet size when the information is transferred at the peak information rate. Thisparameter must be larger than 0. It is recommended that this parameter should be notless than the maximum length of the IP packet that might be forwarded.

Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should benot less than the committed information rate.

Penultimate HopPopping

Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLSenabled network. It refers to the process whereby the outermost label of an MPLS taggedpacket is removed by a Label Switched Router (LSR) before the packet is passed to anadjacent Label Edge Router (LER).

Per-Hop-Behavior A forwarding behavior applied at a DS-compliant node. This behavior belongs to thebehavior aggregate defined in the DiffServ domain.

PHB See Per-Hop-Behavior

PHP See Penultimate Hop Popping

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM See Protocol Independent Multicast-Sparse Mode

PIR See Peak Information Rate

Plesiochronous DigitalHierarchy

A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimumrate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.

Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulatesdata packets on the network layer. It is located in layer 2 of the IP protocol stack.

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.

POS See Packet over SDH/SONET

Power box A direct current power distribution box at the upper part of a cabinet, which suppliespower for the subracks in the cabinet.

PPP See Point-to-Point Protocol

PPVPN Provider Provisioned VPN

PQ See Priority Queuing

PRBS Pseudo-Random Binary Sequence

PRC Primary Reference Clock

Printed Circuit Board A board used to mechanically support and electrically connect electronic componentsusing conductive pathways, tracks, or traces, etched from copper sheets laminated ontoa non-conductive substrate.



H-23

Priority Queuing A priority queue is an abstract data type in computer programming that supports thefollowing three operations: 1) InsertWithPriority: add an element to the queue with anassociated priority 2) GetNext: remove the element from the queue that has the highestpriority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3)PeekAtNext (optional): look at the element with highest priority without removing it

Processing board area An area for the processing boards on the subrack.

protection groundingcable

A cable which connects the equipment and the protection grounding bar. Usually, onehalf of the cable is yellow; while the other half is green.

Protection path A specific path that is part of a protection group and is labeled protection.

Protocol IndependentMulticast-Sparse Mode

A protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This protocol is named protocol independent because it is notdependent on any particular unicast routing protocol for topology discovery, and sparse-mode because it is suitable for groups where a very low percentage of the nodes (andtheir routers) will subscribe to the multicast session. Unlike earlier dense-mode multicastrouting protocols such as DVMRP and PIM-DM which flooded packets everywhere andthen pruned off branches where there were no receivers, PIM-SM explicitly constructsa tree from each sender to the receivers in the multicast group. Multicast packets fromthe sender then follow this tree.

Provider Edge A device that is located in the backbone network of the MPLS VPN structure. A PE isresponsible for VPN user management, establishment of LSPs between PEs, andexchange of routing information between sites of the same VPN. During the process, aPE performs the mapping and forwarding of packets between the private network andthe public channel. A PE can be a UPE, an SPE, or an NPE.

Pseudo wire An emulated connection between two PEs for transmitting frames. The PW is establishedand maintained by PEs through signaling protocols. The status information of a PW ismaintained by the two end PEs of a PW.

Pseudo WireEmulation Edge-to-Edge

Pseudo-Wire Emulation Edge to Edge (PWE3) is a type of end-to-end Layer 2transmitting technology. It emulates the essential attributes of a telecommunicationservice such as ATM, FR or Ethernet in a Packet Switched Network (PSN). PWE3 alsoemulates the essential attributes of low speed Time Division Multiplexed (TDM) circuitand SONET/SDH. The simulation approximates to the real situation.

PSN See packet switched network

PTN Packet Transport Network

PW See Pseudo wire

PWE3 See Pseudo Wire Emulation Edge-to-Edge

Q

QoS See Quality of Service

QPSK See Quadrature Phase Shift Keying

Quadrature Phase ShiftKeying

Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmissionthrough the conversion or modulation and the phase determination of the referencesignals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK usesfour dots in the star diagram. The four dots are evenly distributed on a circle. On thesephases, each QPSK character can perform two-bit coding and display the codes in Graycode on graph with the minimum BER.


Maintenance Guide


Issue 03 (2010-05-30)

Quality of Service Quality of Service, which determines the satisfaction of a subscriber for a service. QoSis influenced by the following factors applicable to all services: service operability,service accessibility, service maintainability, and service integrity.

R

Radio Freqency 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

A device used in the RNS to control the usage and integrity of radio resources.

Random EarlyDetection

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 synchronizationresulted in traditional Tail-Drop can be prevented.

Rapid Spanning TreeProtocol

An evolution of the Spanning Tree Protocol, providing for faster spanning treeconvergence after a topology change. The RSTP protocol is backward compatible withthe STP protocol.

RDI See Remote Defect Indication

Received SignalStrength Indicator

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 Receiver sensitivity is defined as the minimum acceptable value of average receivedpower at point R to achieve a 1 x 10-10 BER.

RED See Random Early Detection

REI See Remote Error Indication

Remote DefectIndication

A signal transmitted at the first opportunity in the outgoing direction when a terminaldetects specific defects in the incoming signal.

Remote ErrorIndication

A remote error indication (REI) is sent upstream to signal an error condition. There aretwo types of REI alarms: Remote error indication line (REI-L) is sent to the upstreamLTE when errors are detected in the B2 byte. Remote error indication path (REI-P) issent to the upstream PTE when errors are detected in the B3 byte.

remote networkmonitoring

A manage information base (MIB) defined by the Internet Engineering Task Force(IETF). RMON is mainly used to monitor the data flow of one network segment or theentire network.

Resource ReservationProtocol

The Resource Reservation Protocol (RSVP) is designed for Integrated Service and isused to reserve resources on every node along a path. RSVP operates on the transportlayer; however, RSVP does not transport application data. RSVP is a network controlprotocol like Internet Control Message Protocol (ICMP).

Reverse pressure A traffic control method. In telecommunication, when detecting that the transmit endtransmits a large volume of traffic, the receive end sends signals to ask the transmit endto slow down the transmission rate.

RF See Radio Freqency

RFC Request For Comment



H-25

RIP See Routing Information Protocol

RMON See remote network monitoring

RNC See Radio Network Controller

Root alarm An alarm directly caused by anomaly events or faults in the network. Some lower-levelalarms always accompany a root alarm.

route A route is 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 InformationProtocol

Routing Information Protocol: A simple routing protocol that is part of the TCP/IPprotocol suite. It determines a route based on the smallest hop count between source anddestination. RIP is a distance vector protocol that routinely broadcasts routinginformation to its neighboring routers and is known to waste bandwidth.

routing table A table that stores and updates the locations (addresses) of network devices. Routersregularly share routing table information to be up to date. A router relies on thedestination address and on the information in the table that gives the possible routes--inhops or in number of jumps--between itself, intervening routers, and the destination.Routing tables are updated frequently as new information is available.

RS Reed-Solomon encoding

RSL Received Signal Level

RSSI See Received Signal Strength Indicator

RSTP See Rapid Spanning Tree Protocol

RSVP See Resource Reservation Protocol

RTN Radio Transmission Node

S

SD See space diversity

SDH See Synchronous Digital Hierarchy

SDP Serious Disturbance Period

SEMF Synchronous Equipment Management Function

Service LevelAgreement

A management-documented agreement that defines the relationship between serviceprovider and its customer. It also provides specific, quantifiable information aboutmeasuring and evaluating the delivery of services. The SLA details the specific operatingand support requirements for each service provided. It protects the service provider andcustomer and allows the service provider to provide evidence that it has achieved thedocumented target measure.

SES Severely Errored Second

Setup Priority The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicatesthe highest priority) to 7. It is used to determine whether the tunnel can preempt theresources required by other backup tunnels.

SF See Signal Fail

SFP See Small Form-Factor Pluggable


Maintenance Guide


Issue 03 (2010-05-30)

side trough The trough on the side of the cable rack, which is used to place nuts so as to fix thecabinet.

signal cable Common signal cables cover the E1cable, network cable, and other non-subscriber signalcable.

Signal Fail SF is a signal indicating the associated data has failed in the sense that a near-end defectcondition (not being the degraded defect) is active.

Signal Noise Ratio The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to theamplitude of noise signals at a given point in time. SNR is expressed as 10 times thelogarithm of the power ratio and is usually expressed in dB (Decibel).

Simple NetworkManagement Protocol

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.

simplex Of or relating to a telecommunications system in which only one message can be sentin either direction at one time.

SLA See Service Level Agreement

Slicing To divide data into the information units proper for transmission.

Small Form-FactorPluggable

A specification for a new generation of optical modular transceivers.

SNC See SubNetwork Connection

SNCP See SubNetwork Connection Protection

SNMP See Simple Network Management Protocol

SNR See Signal Noise Ratio

SP Strict Priority

space diversity A diversity scheme that enables two or more antennas separated by a specific distanceto transmit/receive the same signal and selection is then performed between the twosignals to ease the impact of fading. Currently, only receive SD is used.

Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop.STP applies to the redundant network to block some undesirable redundant paths throughcertain algorithms and prune a loop network into a loop-free tree network.

SSM See Synchronization Status Message

Static Virtual Circuit Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPNinformation by manual configuration of VC labels, instead of by a signaling protocol.

Statistical multiplexing A multiplexing technique whereby information from multiple logical channels can betransmitted across a single physical channel. It dynamically allocates bandwidth only toactive input channels, to make better use of available bandwidth and allow more devicesto be connected than with other multiplexing techniques. Compare with TDM.

STM See synchronous transport module

STM-1 SDH Transport Module -1



H-27

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

STP See Spanning Tree Protocol

sub-network Sub-network is the logical entity in the transmission network and comprises a group ofnetwork management objects. The network that consists of a group of interconnected orcorrelated NEs, according to different functions. For example, protection subnet, clocksubnet and so on. A sub-network can contain NEs and other sub-networks. Generally, asub-network is used to contain the equipments which are located in adjacent regions andclosely related with one another, and it is indicated with a sub-network icon on atopological view. The U2000 supports multilevels of sub-networks. A sub-networkplanning can better the organization of a network view. On the one hand, the view spacecan be saved, on the other hand, it helps the network management personnel focus onthe equipments under their management.

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 and is matched with the IP address.

SubNetworkConnection

A "transport entity" that transfers information across a subnetwork, it is formed by theassociation of "ports" on the boundary of the subnetwork.

SubNetworkConnection Protection

A working subnetwork connection is replaced by a protection subnetwork connection ifthe working subnetwork connection fails, or if its performance falls below a requiredlevel.

SVC See Static Virtual Circuit

SVL Shared VLAN Learning

Switch To filter, forward frames based on label or the destination address of each frame. Thisbehavior operates at the data link layer of the OSI model.

Synchronization StatusMessage

A message that is used to transmit the quality levels of timing signals on the synchronoustiming link. Through this message, the node clocks of the SDH network and thesynchronization network can aquire upper stream clock information, and the two performoperations on the corresponding clocks, such as tracing, switchover, or converting hold),and then forward the synchronization information of this node to down stream.

Synchronous DigitalHierarchy

SDH is a transmission scheme that follows ITU-T G.707, G.708, and G.709. It definesthe transmission features of digital signals such as frame structure, multiplexing mode,transmission rate level, and interface code. SDH is an important part of ISDN and B-ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speedcounterparts, and the line coding of scrambling is only used only for signals. SDH issuitable for the fiber communication system with high speed and a large capacity sinceit uses synchronous multiplexing and flexible mapping structure.

synchronous transportmodule

An STM is the information structure used to support section layer connections in theSDH. It consists of information payload and Section Overhead (SOH) information fieldsorganized in a block frame structure which repeats every 125 . The information is suitablyconditioned for serial transmission on the selected media at a rate which is synchronizedto the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Highercapacity STMs are formed at rates equivalent to N times this basic rate. STM capacitiesfor N = 4, N = 16 and N = 64 are defined; higher values are under consideration.


Maintenance Guide


Issue 03 (2010-05-30)

T

tail drop A type of QoS. When a queue within a network router reaches its maximum length,packet drops can occur. When a packet drop occurs, connection-based protocols such asTCP slow down their transmission rates in an attempt to let queued packets be serviced,thereby letting the queue empty. This is also known as tail drop because packets aredropped from the input end (tail) of the queue.

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.

TCI Tag Control Information

TCP See TransmissionControl Protocol

TDM See Time Division Multiplexing

TE See traffic engineering

TEDB See Traffic Engineering DataBase

TelecommunicationManagement Network

The Telecommunications Management Network is a protocol model defined by ITU-Tfor managing open systems in a communications network.An architecture formanagement, including planning, provisioning, installation, maintenance, operation andadministration of telecommunications equipment, networks and services.

TIM Trace Identifier Mismatch

Time DivisionMultiplexing

It is a multiplexing technology. TDM divides the sampling cycle of a channel into timeslots (TSn, n=0, 1, 2, 3......), and the sampling value codes of multiple signals engrosstime slots in a certain order, forming multiple multiplexing digital signals to betransmitted over one channel.

Time To Live A technique used in best-effort delivery systems to prevent packets that loop endlessly.The TTL is set by the sender to the maximum time the packet is allowed to be in thenetwork. Each router in the network decrements the TTL field when the packet arrives,and discards any packet if the TTL counter reaches zero.

TMN See Telecommunication Management Network

ToS priority A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header.

TPS See Tributary Protection Switch

traffic engineering A task that effectively maps the service flows to the existing physical topology.

Traffic EngineeringDataBase

TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to knowthe features of the dynamic TE of every links by expanding the current IGP, which usesthe link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS containsome TE features, such as the link bandwidth and color. The maximum reservedbandwidth of the link and the unreserved bandwidth of every link with priority are ratherimportant. Every router collects the information about TE of every links in its area andgenerates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLSTE network.

Traffic shaping It is a way of controlling the network traffic from a computer to optimize or guaranteethe performance and minimize the delay. It actively adjusts the output speed of trafficin the scenario that the traffic matches network resources provided by the lower layerdevices, avoiding packet loss and congestion.



H-29

trail A type of transport entity, mainly engaged in transferring signals from the input of thetrail source to the output of the trail sink, and monitoring the integrality of the transferredsignals.

TransmissionControlProtocol

The protocol within TCP/IP that governs the breakup of data messages into packets tobe sent via IP (Internet Protocol), and the reassembly and verification of the completemessages from packets received by IP. A connection-oriented, reliable protocol (reliablein the sense of ensuring error-free delivery), TCP corresponds to the transport layer inthe ISO/OSI reference model.

Tributary ProtectionSwitch

Tributary protection switching, a function provided by the equipment, is intended toprotect N tributary processing boards through a standby tributary processing board.

trTCM See Two Rate Three Color Marker

TTL See Time To Live

TU Tributary Unit

Tunnel A channel on the packet switching network that transmits service traffic between PEs.In VPN, a tunnel is an information transmission channel between two entities. The tunnelensures secure and transparent transmission of VPN information. In most cases, a tunnelis an MPLS tunnel.

Two Rate Three ColorMarker

The trTCM meters an IP packet stream and marks its packets based on two rates, PeakInformation Rate (PIR) and Committed Information Rate (CIR), and their associatedburst sizes to be either green, yellow, or red. A packet is marked red if it exceeds thePIR. Otherwise it is marked either yellow or green depending on whether it exceeds ordoesn't exceed the CIR.

H.6 U-Z

U

UAS Unavailable Second

UBR See Unspecified Bit Rate

UDP See User Datagram Protocol

underfloor cabling The cables connected cabinets and other devices are routed underfloor.

UNI See User Network Interface

Unicast The process of sending data from a source to a single recipient.

Unspecified Bit Rate No commitment to transmission. No feedback to congestion. This type of service is idealfor the transmission of IP datagrams. In case of congestion, UBR cells are discarded,and no feedback or request for slowing down the data rate is delivered to the sender.

Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.

UPS Uninterruptible Power Supply

upward cabling Cables or fibres connect the cabinet with other equipment from the top of the cabinet.


Maintenance Guide


Issue 03 (2010-05-30)

User DatagramProtocol

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 datagrams. UDP provides application programs with the unreliableconnectionless packet delivery service. Thus, UDP messages can be lost, duplicated,delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is,the destination device does not actively confirm whether the correct data packet isreceived.

User Network Interface A type of ATM Forum specification that defines an interoperability standard for theinterface between ATM-based products (a router or an ATM switch) located in a privatenetwork and the ATM switches located within the public carrier networks. Also used todescribe similar connections in Frame Relay networks.

V

V-NNI See virtual network-network interface

V-UNI See Virtual User-Network Interface

Variable Bit Rate One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike apermanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidthand is better suited to non real time transfers than to real-time streams such as voice calls.

VBR See Variable Bit Rate

VC See Virtual Channel

VC-12 Virtual Container -12



VCC Virtual Channel Connection

VCC,VPL See Virtual Chanel Connection

VCG See virtual concatenation group

VCI See Virtual Channel Identifier

Virtual ChanelConnection

Virtual Channel Connection. The VC logical trail that carries data between two endpoints in an ATM network. A logical grouping of multiple virtual channel connectionsinto one virtual connection.

Virtual Channel Any logical connection in the ATM network. A VC is the basic unit of switching in theATM network uniquely identified by a virtual path identifier (VPI)/virtual channelidentifier (VCI) value. It is the channel on which ATM cells are transmitted by the sw

Virtual ChannelIdentifier

virtual channel identifier. A 16-bit field in the header of an ATM cell. The VCI, togetherwith the VPI, is used to identify the next destination of a cell as it passes through a seriesof ATM switches on its way to its destination.

virtual concatenationgroup

A group of co-located member trail termination functions that are connected to the samevirtual concatenation link

Virtual Leased Line A point-to-point, layer-2 channel that behaves like a leased line by transparentlytransporting different protocols with a guaranteed throughput.



H-31

Virtual Local AreaNetwork

A logical grouping of two or more nodes which are not necessarily on the same physicalnetwork segment but which share the same IP network number. This is often associatedwith switched Ethernet.

virtual network-network interface

A virtual network-network interface (V-NNI) is a network-side interface.

Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to whichVP (Virtual Path) the cell belongs.

Virtual Private LANService

A type of point-to-multipoint L2VPN service provided over the public network. VPLSenables geographically isolated user sites to communicate with each other through theMAN/WAN as if they are on the same LAN.

Virtual PrivateNetwork

The extension of a private network that encompasses encapsulated, encrypted, andauthenticated links across shared or public networks. VPN connections can provideremote access and routed connections to private networks over the Internet.

Virtual Private WireService

A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR,Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.

Virtual Routing andForwarding

A technology included in IP (Internet Protocol) network routers that allows multipleinstances of a routing table to exist in a router and work simultaneously.

Virtual Switch Instance An instance through which the physical access links of VPLS can be mapped to thevirtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridgefunction and can terminate PW.

Virtual User-NetworkInterface

virtual user-network interface. A virtual user-network interface, works as an action pointto perform service claissification and traffic control in HQoS.

VLAN See Virtual Local Area Network

VLL See Virtual Leased Line

Voice over IP An IP telephony term for a set of facilities used to manage the delivery of voiceinformation over the Internet. VoIP involves sending voice information in a digital formin discrete packets rather than by using the traditional circuit-committed protocols of thepublic switched telephone network (PSTN).

VoIP See Voice over IP

VPI See Virtual Path Identifier

VPLS See Virtual Private LAN Service

VPN See Virtual Private Network

VPWS See Virtual Private Wire Service

VRF See Virtual Routing and Forwarding

VSI See Virtual Switch Instance

W

Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection canbe used again to transport the normal traffic signal and/or to select the normal trafficsignal from.

WAN See Wide Area Network


Maintenance Guide


Issue 03 (2010-05-30)

Web LCT The local maintenance terminal of a transport network, which is located on the NEmanagement layer of the transport network

Weighted Fair Queuing Weighted Fair Queuing (WFQ) is a fair queue scheduling algorithm based on bandwidthallocation weights. This scheduling algorithm allocates the total bandwidth of aninterface to queues, according to their weights and schedules the queues cyclically. Inthis manner, packets of all priority queues can be scheduled.

Weighted RandomEarly Detection

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.

WFQ See Weighted Fair Queuing

Wide Area Network 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.

Winding pipe A tool for fiber routing, which acts as the corrugated pipe.

wire speed Wire speed refers to the maximum packet forwarding capacity on a cable. The value ofwire speed equals the maximum transmission rate capable on a given type of media.

WMS Wholesale Managed Services

WRED See Weighted Random Early Detection

WRR Weighted Round Robin

WTR See Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC See cross polarization interference cancellation



H-33

RTN 605 Maintenance Guide(V100R005C00_03)

Documents

Transcript of RTN 605 Maintenance Guide(V100R005C00_03)