Maintenance Guide(V100R001C00 02)

OptiX RTN 950 Radio Transmission SystemV100R001C00

Maintenance Guide

Issue 02

Date 2009-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. 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 the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis document describes the following contents:l Items, periods, and procedures of routine maintenance, which help you complete the routine

maintenance tasks so that long-term stable operation of the equipment can be ensured.l Troubleshooting flow and typical methods for troubleshooting, which help you rectify

equipment faults in time.l Alarms and performance events of the equipment, which provide reference information for

equipment maintenance and repair in terms of the generation principle, classification, andtroubleshooting method.

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

Product Name Version

OptiX RTN 950 V100R001C00

OptiX iManager T2000 V200R007C03

Intended AudienceThis document is intended for:

l System maintenance engineer

l Network monitoring engineer

l On-site maintenance engineer

Before reading this document, you need to know microwave communication basics.

OrganizationThis document is organized as follows:

OptiX RTN 950 Radio Transmission SystemMaintenance Guide About This Document


iii

Table 1 Introduction to each chapter

Chapter Main Content

1 Safety Precautions This chapter describes safetysymbols and operation regulations.

2 Routine maintenance This chapter describes items,periods, and procedures of routinemaintenance.

3 Troubleshooting This chapter describes thephilosophy and flow oftroubleshooting.

4 Data Backup and Restoration This chapter describes methods forbacking up and restoring NM andNE data.

5 Replacing Components This chapter describes proceduresfor replacing boards and chassis.

6 Software Package Upgrade and Package Diffusion This chapter describes methods andprocedures for performing thepackage loading and packagediffusion.

7 Remote Maintenance Guide This chapter describes methods andprocedures for enabling a remotemaintenance user and establishingremote maintenance.

8 Task Set This chapter describes commonoperations for troubleshooting.

9 Alarm This chapter describes how alarmsare generated, and how to classifyand handle the alarms.

10 Performance Event This chapter describes howperformance events are generated,and how to classify and handle theperformance events.

A Glossary This chapter lists the glossary usedin this document.

B Acronyms and Abbreviations This chapter lists the acronyms andabbreviations used in thisdocument.

About This DocumentOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

Conventions

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

Symbol Description

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

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

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

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

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

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

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

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

Italic Book titles are in italics.

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

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

OptiX RTN 950 Radio Transmission SystemMaintenance Guide About This Document


v

Convention Description

Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are inboldface. For example, click OK.

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

Mouse OperationThe mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly withoutmoving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certainposition.

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

Updates in Issue 02 (2009-06-30) Based on Product Version V100R001C00This document is the second release of the V100R001C00 version.

Compared with the first release, this document contains the following updates:l The database activation procedures are added to the data backup and restoration part.

l The list of alarms that need to be cleared before an upgrade by using the package loadingor package diffusion method is added to the package loading and package diffusion part.

l The NO_BD_SOFT and SYSPARA_CFDB_NOSAME alarms are deleted.

l The known bugs are fixed.

Updates in Issue 01 (2009-04-30) Based on Product Version V100R001C00This document is the first release of the V100R001C00 version.

About This DocumentOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

Contents

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

1 Safety Precautions......................................................................................................................1-11.1 Warning and Safety Symbols..........................................................................................................................1-21.2 Safety Precautions for Using the Equipment..................................................................................................1-3

1.2.1 Safety Symbols.......................................................................................................................................1-41.2.2 Electrical Safety.....................................................................................................................................1-41.2.3 Battery....................................................................................................................................................1-81.2.4 Microwave..............................................................................................................................................1-91.2.5 Laser and Fibers...................................................................................................................................1-101.2.6 High-Altitude Operations.....................................................................................................................1-101.2.7 Installing and Removing Boards..........................................................................................................1-111.2.8 Miscellaneous.......................................................................................................................................1-12

1.3 Precautions for Using the T2000...................................................................................................................1-12

2 Routine maintenance.................................................................................................................2-12.1 Routine Maintenance Items and Periods.........................................................................................................2-22.2 Guide and Record Table for Routine Maintenance in the NMS Center.........................................................2-3

2.2.1 Checking the Status of the NE and Boards............................................................................................2-42.2.2 Browsing Network-Wide Alarms...........................................................................................................2-52.2.3 Browsing Abnormal Events...................................................................................................................2-62.2.4 Browsing the Current Performance Events............................................................................................2-82.2.5 Browsing the Performance Events of the RMON Statistics Group.......................................................2-92.2.6 Checking the Optical Power.................................................................................................................2-112.2.7 Browsing the History Performance Events..........................................................................................2-132.2.8 Browsing the RMON History Performance Events.............................................................................2-142.2.9 Backing up the MO Data of the T2000................................................................................................2-162.2.10 Backing up the NE Database..............................................................................................................2-182.2.11 Testing the IF 1+1 Switching.............................................................................................................2-182.2.12 Maintenance Record Table.................................................................................................................2-19

2.3 Field Maintenance and Record Table for Outdoor Equipment.....................................................................2-202.3.1 Checking the ODU...............................................................................................................................2-212.3.2 Checking the Hybrid Coupler..............................................................................................................2-212.3.3 Checking the Antenna..........................................................................................................................2-22

OptiX RTN 950 Radio Transmission SystemMaintenance Guide Contents


vii

2.3.4 Checking IF Cables..............................................................................................................................2-222.3.5 Maintenance Record Table...................................................................................................................2-23

2.4 Guide and Record Table for Routine Maintenance of the Spare Parts.........................................................2-242.4.1 Testing the Spare Parts.........................................................................................................................2-242.4.2 Maintenance Record Table...................................................................................................................2-25

3 Troubleshooting.........................................................................................................................3-13.1 General Fault Handling Flow..........................................................................................................................3-33.2 Emergency Flow of Handling the Service Interruption Fault.........................................................................3-53.3 Troubleshooting Microwave Links.................................................................................................................3-73.4 CES Service Troubleshooting.......................................................................................................................3-153.5 Ethernet Service Troubleshooting.................................................................................................................3-183.6 Clock Troubleshooting..................................................................................................................................3-203.7 QoS Troubleshooting....................................................................................................................................3-223.8 Inband DCN Troubleshooting.......................................................................................................................3-253.9 LAG Troubleshooting...................................................................................................................................3-283.10 ML-PPP Troubleshooting...........................................................................................................................3-313.11 IMA Troubleshooting..................................................................................................................................3-333.12 FRR Troubleshooting..................................................................................................................................3-373.13 MPLS APS Troubleshooting.......................................................................................................................3-403.14 Information Collection and Information Record.........................................................................................3-423.15 Fault Notification and Technical Support...................................................................................................3-43

4 Data Backup and Restoration..................................................................................................4-14.1 Backing Up and Restoring the T2000 Data....................................................................................................4-2

4.1.1 Methods of Backing Up and Restoring the T2000 Data........................................................................4-24.1.2 Backing Up the T2000 MO Data...........................................................................................................4-74.1.3 Backing Up All Data in the T2000 Database.........................................................................................4-84.1.4 Backing Up the T2000 Network Configuration Data by Means of Scripts...........................................4-94.1.5 Restoring the MO Data of the T2000...................................................................................................4-104.1.6 Restoring All Data of the T2000 Databases.........................................................................................4-114.1.7 Restoring the T2000 Network Configuration Data by Means of Scripts.............................................4-12

4.2 Backing Up and Restoring the NE Data........................................................................................................4-134.2.1 Methods of Backing Up and Restoring NE Data.................................................................................4-134.2.2 Backing Up the NE Database to the System Control Board................................................................4-154.2.3 Backing Up the NE Database to the CF Card......................................................................................4-164.2.4 Backing Up the NE Database to a Local Server..................................................................................4-164.2.5 Restoring the NE Database from the System Control Board...............................................................4-184.2.6 Restoring the NE Database from the CF Card.....................................................................................4-184.2.7 Recovering the NE Database from a Local Server...............................................................................4-19

5 Replacing Components.............................................................................................................5-15.1 Replacing the CXPR with the 1+1 Protection.................................................................................................5-35.2 Replacing the CXPR Without the 1+1 Protection...........................................................................................5-4

ContentsOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

5.3 Replacing the Processing Boards....................................................................................................................5-55.4 Replacing the IFE2 Board...............................................................................................................................5-75.5 Replacing the FAN Board...............................................................................................................................5-85.6 Replacing the PIU Board.................................................................................................................................5-95.7 Replacing the AUXQ Board.........................................................................................................................5-105.8 Replacing the Chassis....................................................................................................................................5-115.9 Replacing the Pluggable Optical Module......................................................................................................5-135.10 Replacing the ODU.....................................................................................................................................5-14

5.10.1 Replacing the ODU with Waveguide Interface..................................................................................5-155.10.2 Replacing the ODU with Coaxial Interface.......................................................................................5-16

5.11 Replacing the IF Cable................................................................................................................................5-17

6 Software Package Upgrade and Package Diffusion............................................................6-16.1 Software Package Upgrade............................................................................................................................. 6-2

6.1.1 Definition and Feature............................................................................................................................6-26.1.2 State Model............................................................................................................................................ 6-26.1.3 Realization Scheme................................................................................................................................6-46.1.4 Creating a Package Upgrade Task..........................................................................................................6-5

6.2 Software Package Diffusion..........................................................................................................................6-136.2.1 Definition and Feature..........................................................................................................................6-136.2.2 State Model..........................................................................................................................................6-146.2.3 Realization Scheme..............................................................................................................................6-166.2.4 Creating a Package Diffusion Upgrade Task.......................................................................................6-16

7 Remote Maintenance Guide....................................................................................................7-17.1 Introduce..........................................................................................................................................................7-27.2 Enabling a Remote Maintenance User............................................................................................................7-27.3 Establishing Remote Maintenance..................................................................................................................7-3

8 Task Set........................................................................................................................................8-18.1 Querying T2000 Operation Logs.................................................................................................................... 8-48.2 Querying Current Alarms of a Board..............................................................................................................8-48.3 Querying the Board Information Report.........................................................................................................8-58.4 Checking the Optical Power............................................................................................................................8-68.5 Performing the LSP Ping Test.........................................................................................................................8-78.6 Performing the LSP Traceroute Test ..............................................................................................................8-88.7 Checking Data Consistency Between an NE and the T2000........................................................................8-108.8 Uploading the NE Configuration Data..........................................................................................................8-118.9 Configuring Port Loopback...........................................................................................................................8-128.10 Performing the MPLS Tunnel Protection Switching..................................................................................8-148.11 Performing the 1+1 Protection Switching for CXPR boards......................................................................8-158.12 Performing IF 1+1 Protection Switch.........................................................................................................8-168.13 Querying an IF 1+1 Protection Group.........................................................................................................8-178.14 Querying the Working State of AM............................................................................................................8-17



ix

8.15 Setting the State of an ODU Transmitter....................................................................................................8-188.16 Resetting Boards.........................................................................................................................................8-198.17 Testing the Transmitted Optical Power of the Optical Interface.................................................................8-208.18 Testing the Receive Optical Power of the Optical Interface.......................................................................8-228.19 Replacing Boards on Site............................................................................................................................8-248.20 Powering On the Equipment.......................................................................................................................8-308.21 Powering Off the Equipment.......................................................................................................................8-308.22 Querying and Setting the Working Mode of Ethernet Interface.................................................................8-318.23 Querying Protection Configuration.............................................................................................................8-328.24 Inspecting and Cleaning the Optical Fiber Connectors...............................................................................8-32

8.24.1 Overview............................................................................................................................................8-338.24.2 Protection of Optical Connectors.......................................................................................................8-348.24.3 Tools, Equipment and Materials........................................................................................................8-358.24.4 Inspecting Optical Connectors...........................................................................................................8-368.24.5 Cleaning Optical Fiber Connectors Using Cartridge Cleaners..........................................................8-398.24.6 Cleaning Optical Fiber Connectors Using Lens Tissue.....................................................................8-428.24.7 Cleaning Optical Modules Using Optical Cleaning Sticks................................................................8-45

9 Alarm............................................................................................................................................9-19.1 Basic Concepts Related to Alarms..................................................................................................................9-2

9.1.1 Alarm Reporting Flow...........................................................................................................................9-29.1.2 Alarm Correlation..................................................................................................................................9-39.1.3 Alarm Category......................................................................................................................................9-69.1.4 Alarm Severity.......................................................................................................................................9-79.1.5 Alarm Notification.................................................................................................................................9-8

9.2 Alarm List.......................................................................................................................................................9-89.2.1 SL91CXPR Board Alarm List................................................................................................................9-99.2.2 TND1EF8T Board Alarm List.............................................................................................................9-109.2.3 TND1EF8F Board Alarm List..............................................................................................................9-109.2.4 TND1EG2 Board Alarm List...............................................................................................................9-109.2.5 TND1ML1/TND1ML1A Board Alarm List........................................................................................9-119.2.6 TND1IFE2 Board Alarm List..............................................................................................................9-119.2.7 TND1AUXQ Board Alarm List...........................................................................................................9-129.2.8 TND1PIU Board Alarm List................................................................................................................9-129.2.9 TND1FAN Board Alarm List..............................................................................................................9-129.2.10 ODU Alarm List.................................................................................................................................9-12

9.3 Alarm Handling.............................................................................................................................................9-129.3.1 Alarm Handling Flow...........................................................................................................................9-179.3.2 AM_DOWNSHIFT..............................................................................................................................9-199.3.3 ALM_ALS...........................................................................................................................................9-219.3.4 ALM_E1RAI........................................................................................................................................9-219.3.5 ALM_IMA_LIF...................................................................................................................................9-229.3.6 ALM_IMA_LODS...............................................................................................................................9-24


Maintenance Guide

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

Issue 02 (2009-06-30)

9.3.7 ALM_IMA_RE_RX_UNUSABLE.....................................................................................................9-259.3.8 ALM_IMA_RE_TX_UNUSABLE.....................................................................................................9-269.3.9 ALM_IMA_RFI...................................................................................................................................9-289.3.10 BD_NOT_INSTALLED....................................................................................................................9-299.3.11 BD_STATUS.....................................................................................................................................9-309.3.12 BFD_DOWN......................................................................................................................................9-319.3.13 BUS_ERR..........................................................................................................................................9-339.3.14 CES_JTROVR_EXC.........................................................................................................................9-349.3.15 CES_JTRUDR_EXC.........................................................................................................................9-359.3.16 CES_LOSPKT_EXC.........................................................................................................................9-369.3.17 CES_MALPKT_EXC........................................................................................................................9-389.3.18 CES_MISORDERPKT_EXC............................................................................................................9-399.3.19 CES_STRAYPKT_EXC....................................................................................................................9-409.3.20 CFCARD_FAILED............................................................................................................................9-419.3.21 CFCARD_OFFLINE.........................................................................................................................9-429.3.22 CLK_NO_TRACE_MODE...............................................................................................................9-439.3.23 COMMUN_FAIL...............................................................................................................................9-459.3.24 CONFIG_NOSUPPORT....................................................................................................................9-479.3.25 DBMS_ERROR.................................................................................................................................9-489.3.26 DBMS_PROTECT_MODE...............................................................................................................9-509.3.27 DOWN_E1_AIS.................................................................................................................................9-519.3.28 ETH_APS_LOST...............................................................................................................................9-529.3.29 ETH_APS_PATH_MISMATCH.......................................................................................................9-539.3.30 ETH_APS_SWITCH_FAIL...............................................................................................................9-549.3.31 ETH_APS_TYPE_MISMATCH.......................................................................................................9-559.3.32 ETH_AUTO_LINK_DOWN.............................................................................................................9-569.3.33 ETH_LINK_DOWN..........................................................................................................................9-589.3.34 ETH_LOS...........................................................................................................................................9-599.3.35 EXT_SYNC_LOS..............................................................................................................................9-609.3.36 EXT_TIME_LOC..............................................................................................................................9-629.3.37 FAN_FAIL.........................................................................................................................................9-639.3.38 FLOW_OVER....................................................................................................................................9-649.3.39 GSP_ISIS_NB_AUTH_ERR.............................................................................................................9-659.3.40 GSP_RSVP_NB_AUTH_ERR..........................................................................................................9-669.3.41 GSP_RSVP_NB_DOWN...................................................................................................................9-689.3.42 GSP_TNNL_DOWN.........................................................................................................................9-699.3.43 HARD_BAD......................................................................................................................................9-709.3.44 IMA_GROUP_LE_DOWN...............................................................................................................9-749.3.45 IMA_GROUP_RE_DOWN...............................................................................................................9-759.3.46 IMAE1_DELAY................................................................................................................................9-769.3.47 IN_PWR_ABN...................................................................................................................................9-779.3.48 LAG_DOWN.....................................................................................................................................9-78



xi

9.3.49 LAG_MEMBER_DOWN..................................................................................................................9-799.3.50 LASER_MOD_ERR..........................................................................................................................9-819.3.51 LASER_SHUT...................................................................................................................................9-829.3.52 LFA....................................................................................................................................................9-839.3.53 IF_CABLE_OPEN.............................................................................................................................9-849.3.54 IF_INPWR_ABN...............................................................................................................................9-869.3.55 LMFA.................................................................................................................................................9-879.3.56 LOOP_ALM.......................................................................................................................................9-899.3.57 LSR_BCM_ALM...............................................................................................................................9-919.3.58 LSR_NO_FITED...............................................................................................................................9-929.3.59 LSR_WILL_DIE................................................................................................................................9-939.3.60 LTI......................................................................................................................................................9-949.3.61 MAC_FCS_EXC................................................................................................................................9-969.3.62 MP_DELAY.......................................................................................................................................9-979.3.63 MP_DOWN........................................................................................................................................9-989.3.64 MPLS_TUNNEL_BDI.....................................................................................................................9-1009.3.65 MPLS_TUNNEL_Excess................................................................................................................9-1019.3.66 MPLS_TUNNEL_FDI.....................................................................................................................9-1029.3.67 MPLS_TUNNEL_LOCV.................................................................................................................9-1039.3.68 MPLS_TUNNEL_MISMATCH......................................................................................................9-1059.3.69 MPLS_TUNNEL_MISMERGE......................................................................................................9-1069.3.70 MPLS_TUNNEL_SD......................................................................................................................9-1079.3.71 MPLS_TUNNEL_SF.......................................................................................................................9-1089.3.72 MPLS_TUNNEL_UNKNOWN......................................................................................................9-1109.3.73 MW_BER_EXC...............................................................................................................................9-1119.3.74 MW_BER_SD..................................................................................................................................9-1129.3.75 MW_LIM.........................................................................................................................................9-1139.3.76 MW_LOF.........................................................................................................................................9-1149.3.77 MW_RDI..........................................................................................................................................9-1159.3.78 MW_FECUNCOR...........................................................................................................................9-1169.3.79 MSSW_DIFFERENT.......................................................................................................................9-1179.3.80 NESF_LOST....................................................................................................................................9-1199.3.81 NESTATE_INSTALL.....................................................................................................................9-1209.3.82 OUT_PWR_ABN.............................................................................................................................9-1219.3.83 PATCH_ACT_TIMEOUT...............................................................................................................9-1229.3.84 PATCH_DEACT_TIMEOUT.........................................................................................................9-1239.3.85 PATCH_ERR...................................................................................................................................9-1249.3.86 PATCH_PKGERR...........................................................................................................................9-1259.3.87 PATCHFILE_NOTEXIST...............................................................................................................9-1269.3.88 POWER_ABNORMAL...................................................................................................................9-1279.3.89 POWER_ALM.................................................................................................................................9-1299.3.90 PPP_LCP_FAIL...............................................................................................................................9-130


Maintenance Guide

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

Issue 02 (2009-06-30)

9.3.91 PPP_NCP_FAIL...............................................................................................................................9-1319.3.92 PW_DOWN.....................................................................................................................................9-1329.3.93 R_LOC.............................................................................................................................................9-1339.3.94 RADIO_FADING_MARGIN_INSUFF..........................................................................................9-1359.3.95 RADIO_RSL_LOW.........................................................................................................................9-1379.3.96 RADIO_RSL_HIGH........................................................................................................................9-1399.3.97 RADIO_TSL_LOW.........................................................................................................................9-1409.3.98 RADIO_TSL_HIGH........................................................................................................................9-1419.3.99 RADIO_MUTE................................................................................................................................9-1429.3.100 RELAY_ALARM_CRITICAL......................................................................................................9-1439.3.101 RELAY_ALARM_MAJOR...........................................................................................................9-1449.3.102 RELAY_ALARM_MINOR...........................................................................................................9-1459.3.103 RELAY_ALARM_IGNORE.........................................................................................................9-1469.3.104 RPS_INDI......................................................................................................................................9-1479.3.105 S1_SYN_CHANGE.......................................................................................................................9-1499.3.106 SECU_ALM...................................................................................................................................9-1509.3.107 SWDL_ACTIVATED_TIMEOUT................................................................................................9-1519.3.108 SWDL_AUTOMATCH_INH........................................................................................................9-1529.3.109 SWDL_COMMIT_FAIL...............................................................................................................9-1539.3.110 SWDL_INPROCESS.....................................................................................................................9-1549.3.111 SWDL_NEPKGCHECK................................................................................................................9-1559.3.112 SWDL_PKG_NOBDSOFT...........................................................................................................9-1569.3.113 SWDL_PKGVER_MM.................................................................................................................9-1579.3.114 SWDL_ROLLBACK_FAIL..........................................................................................................9-1589.3.115 SYN_BAD.....................................................................................................................................9-1599.3.116 SYNC_C_LOS...............................................................................................................................9-1609.3.117 SYNC_DISABLE..........................................................................................................................9-1619.3.118 SYNC_F_M_SWITCH..................................................................................................................9-1629.3.119 SYNC_FAIL..................................................................................................................................9-1639.3.120 SYNC_LOCKOFF.........................................................................................................................9-1649.3.121 SYSLOG_COMM_FAIL...............................................................................................................9-1659.3.122 T_ALOS.........................................................................................................................................9-1669.3.123 TEM_HA........................................................................................................................................9-1689.3.124 TEM_LA........................................................................................................................................9-1699.3.125 TEMP_ALARM.............................................................................................................................9-1709.3.126 TEMP_OVER................................................................................................................................9-1719.3.127 THUNDERALM............................................................................................................................9-1729.3.128 TR_LOC.........................................................................................................................................9-1739.3.129 UP_E1_AIS....................................................................................................................................9-1759.3.130 VC_AIS..........................................................................................................................................9-1769.3.131 VC_LOC........................................................................................................................................9-1789.3.132 VC_RDI.........................................................................................................................................9-179



xiii

9.3.133 VOLT_LOS....................................................................................................................................9-1819.3.134 VP_AIS..........................................................................................................................................9-1839.3.135 VP_LOC.........................................................................................................................................9-1849.3.136 VP_RDI..........................................................................................................................................9-1869.3.137 WRG_BD_TYPE...........................................................................................................................9-188

10 Performance Event.................................................................................................................10-110.1 Basic Concepts Related to Performance Events..........................................................................................10-2

10.1.1 Performance Reporting Flow.............................................................................................................10-210.1.2 Performance Event Category............................................................................................................. 10-410.1.3 Performance Threshold......................................................................................................................10-5

10.2 Performance Event List...............................................................................................................................10-510.2.1 SL91CXPR Performance Event List..................................................................................................10-510.2.2 TND1EF8T Performance Event List..................................................................................................10-710.2.3 TND1EF8F Performance Event List..................................................................................................10-810.2.4 TND1EG2 Performance Event List................................................................................................... 10-910.2.5 TND1ML1/TND1ML1A Performance Event List..........................................................................10-1010.2.6 TND1IFE2 Performance Event List.................................................................................................10-1310.2.7 TND1AUXQ Performance Event List.............................................................................................10-1510.2.8 TND1PIU Performance Event List..................................................................................................10-1510.2.9 TND1FAN Performance Event List.................................................................................................10-1510.2.10 ODU Performance Event List........................................................................................................10-16

10.3 Performance Event Handling....................................................................................................................10-1710.3.1 ATM_CELL_AVAILABILITY.......................................................................................................10-1710.3.2 ATMPW_LOSPKTS........................................................................................................................10-1810.3.3 ATMPW_MISORDERPKTS...........................................................................................................10-1910.3.4 CES_JTROVR.................................................................................................................................10-2010.3.5 CES_JTRUDR.................................................................................................................................10-2110.3.6 E1_LCV_SDH.................................................................................................................................10-2210.3.7 E1_LES_SDH..................................................................................................................................10-2310.3.8 E1_LSES_SDH................................................................................................................................10-2410.3.9 MEMUSAGECUR...........................................................................................................................10-2510.3.10 MEMUSAGEMAX........................................................................................................................10-2510.3.11 MEMUSAGEMIN.........................................................................................................................10-2610.3.12 ACMDOWNCNT and ACMUPCNT............................................................................................10-2710.3.13 BDTMPMAX, BDTMPMIN, and BDTMPCUR..........................................................................10-2710.3.14 RSLMAX, RSLMIN and RSLCUR...............................................................................................10-2810.3.15 TSLMAX, TSLMIN, and TSLCUR..............................................................................................10-2810.3.16 RLHTT, RLLTT, TLHTT, TLLTT................................................................................................10-2910.3.17 IFBBE, IFES, IFSES, IFCSES, and IFUAS..................................................................................10-2910.3.18 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and FEC_UNCOR_BLOCK_CNT..................10-3110.3.19 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256..................10-31

A Glossary.....................................................................................................................................A-1


Maintenance Guide

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

Issue 02 (2009-06-30)

B Acronyms and Abbreviations.................................................................................................B-1



xv

Figures

Figure 1-1 Wearing the ESD wrist strap..............................................................................................................1-7Figure 3-1 General flow diagram for handling faults...........................................................................................3-3Figure 3-2 Flow diagram for handling service interruption.................................................................................3-6Figure 3-3 Flow of handling microwave link faults...........................................................................................3-11Figure 3-4 Flowchart for troubleshooting CES service faults............................................................................3-16Figure 3-5 Flowchart for troubleshooting Ethernet service faults......................................................................3-19Figure 3-6 Flowchart for troubleshooting the QoS faults..................................................................................3-24Figure 3-7 Flowchart for troubleshooting the inband DCN faults.....................................................................3-26Figure 3-8 Troubleshooting Flowchart...............................................................................................................3-30Figure 3-9 Flowchart for troubleshooting the ML-PPP faults...........................................................................3-32Figure 3-10 Flowchart for troubleshooting the IMA faults................................................................................3-35Figure 3-11 Flowchart for troubleshooting the FRR faults................................................................................3-38Figure 3-12 Flowchart for troubleshooting the MPLS APS faults.....................................................................3-41Figure 5-1 Inserting and removing the optical module......................................................................................5-14Figure 6-1 State model of software package upgrade..........................................................................................6-3Figure 6-2 Flow diagram for software package upgrade......................................................................................6-4Figure 6-3 State model for package diffusion....................................................................................................6-15Figure 7-1 Connection for remote maintenance...................................................................................................7-2Figure 8-1 Connections for the test of the mean transmitted optical power at the optical interface..................8-21Figure 8-2 Connections for the test of the receive optical power at the optical interface..................................8-23Figure 8-3 Loosening screws with a screwdriver...............................................................................................8-25Figure 8-4 Removing the board (1)....................................................................................................................8-26Figure 8-5 Removing the board (2)....................................................................................................................8-27Figure 8-6 Inserting the board (1)......................................................................................................................8-28Figure 8-7 Inserting the board (2)......................................................................................................................8-29Figure 8-8 Tightening screws with a screwdriver..............................................................................................8-29Figure 8-9 Optical fiber connector.....................................................................................................................8-33Figure 8-10 Protective caps recommended........................................................................................................8-34Figure 8-11 Protective caps not recommended..................................................................................................8-35Figure 8-12 CLETOP cassette cleaner...............................................................................................................8-36Figure 8-13 Cleaning stick for the SC and FC optical interface (just for reference).........................................8-36Figure 8-14 Cleaning stick for the LC optical interface ....................................................................................8-36Figure 8-15 An intact fiber.................................................................................................................................8-37

OptiX RTN 950 Radio Transmission SystemMaintenance Guide Figures


xvii

Figure 8-16 Damaged or suspect fibers..............................................................................................................8-38Figure 8-17 An intact fiber.................................................................................................................................8-38Figure 8-18 Acceptable fibers with imperfections.............................................................................................8-39Figure 8-19 Unacceptable fibers with imperfections.........................................................................................8-39Figure 8-20 Using the CLETOP cassette cleaner...............................................................................................8-41Figure 8-21 Dragging the fiber tip lightly on one cleaning area........................................................................8-41Figure 8-22 Dragging the fiber tip lightly on the other cleaning area................................................................8-42Figure 8-23 Cleaning the fiber tip with the lens tissue on the desk...................................................................8-44Figure 8-24 Cleaning the fiber tip with the lens tissue on the hand...................................................................8-44Figure 9-1 Alarm reporting flow diagram............................................................................................................9-3Figure 9-2 Alarm correlation rules of the Ethernet services carried at the Ethernet port....................................9-5Figure 9-3 Illustration of the alarm correlation analysis......................................................................................9-6Figure 9-4 Flowchart for handling alarms..........................................................................................................9-17Figure 10-1 Performance reporting flow............................................................................................................10-3

FiguresOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

Tables

Table 1 Introduction to each chapter......................................................................................................................ivTable 1-1 Warning and safety symbols................................................................................................................1-2Table 1-2 Levels and meanings of the safety symbols.........................................................................................1-4Table 2-1 Maintenance items and periods............................................................................................................2-2Table 2-2 Maintenance Record Table.................................................................................................................2-23Table 2-3 Maintenance Record Table.................................................................................................................2-25Table 3-1 Troubleshooting for different services and functions..........................................................................3-4Table 3-2 Alarm description.................................................................................................................................3-7Table 3-3 Causes of microwave link faults..........................................................................................................3-9Table 3-4 Flow description.................................................................................................................................3-12Table 3-5 List of common symptoms of CES service faults..............................................................................3-15Table 3-6 List of common symptoms of Ethernet service faults........................................................................3-18Table 3-7 List of common symptoms of clock faults.........................................................................................3-21Table 3-8 List of common symptoms of the QoS faults.....................................................................................3-23Table 3-9 List of common symptoms of the LAG faults................................................................................... 3-29Table 3-10 List of common symptoms of the ML-PPP faults............................................................................3-32Table 3-11 List of common symptoms of the IMA faults..................................................................................3-34Table 3-12 List of common symptoms of the MPLS APS faults.......................................................................3-40Table 4-1 Script files supported by the T2000.....................................................................................................4-4Table 4-2 Features and application scenarios of the three methods of maintaining data.....................................4-6Table 4-3 Methods of backing up and restoring NE data and their application scenarios.................................4-14Table 6-1 Alarms to be cleared before package upgrade.....................................................................................6-6Table 6-2 Alarms to be cleared before package diffusion upgrade....................................................................6-17Table 8-1 General procedure of inspecting and cleaning the optical fiber connectors...................................... 8-34Table 9-1 Alarm severity......................................................................................................................................9-7Table 10-1 SDH Performance Event List...........................................................................................................10-5Table 10-2 RMON Performance Event..............................................................................................................10-6Table 10-3 SDH Performance Event List...........................................................................................................10-7Table 10-4 RMON Performance Event..............................................................................................................10-7Table 10-5 SDH Performance Event List...........................................................................................................10-8Table 10-6 RMON Performance Event..............................................................................................................10-9Table 10-7 SDH Performance Event List...........................................................................................................10-9Table 10-8 RMON Performance Event............................................................................................................10-10

OptiX RTN 950 Radio Transmission SystemMaintenance Guide Tables


xix

Table 10-9 SDH Performance Event List.........................................................................................................10-10Table 10-10 RMON Performance Event..........................................................................................................10-11Table 10-11 SDH Performance Events List.....................................................................................................10-13Table 10-12 Microwave Performance Events List...........................................................................................10-14Table 10-13 SDH Performance Event List.......................................................................................................10-15Table 10-14 RMON Performance Event..........................................................................................................10-15Table 10-15 SDH Performance Events List.....................................................................................................10-16Table 10-16 Microwave Performance Events List...........................................................................................10-16

TablesOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

1 Safety Precautions

About This Chapter

This section describes the safety precautions that should be taken during operating andmaintaining the equipment or using T2000 NMS (Network Management System). The safetyprecautions cover the safety rules related to the human beings and equipment. Adhere to thesesafety rules to avoid injury to the human body and damage to the equipment.

1.1 Warning and Safety SymbolsBefore using the equipment, carefully note the warning and safety symbols on the equipment.Perform operations on the equipment according to the indications of these symbols. This sectiondescribes the warning and safety symbols on the RTN equipment and the indications of thesesymbols.

1.2 Safety Precautions for Using the EquipmentBefore using the equipment, read the safety precautions carefully. During the operation of theequipment, follow the safety precautions to ensure the safety of human beings and the equipment.

1.3 Precautions for Using the T2000To use the T2000 correctly, you should be aware of the precautions for the running, setting, andoperation of the T2000.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 1 Safety Precautions


1-1

1.1 Warning and Safety SymbolsBefore using the equipment, carefully note the warning and safety symbols on the equipment.Perform operations on the equipment according to the indications of these symbols. This sectiondescribes the warning and safety symbols on the RTN equipment and the indications of thesesymbols.

Table 1-1 lists the warning and safety symbols on the equipment, and the indications of thesesymbols.

Table 1-1 Warning and safety symbols

Symbol Indication

This symbol is for anti-static protection.A notice with this symbol indicates that you should wear ananti-static wrist strip or gloves when you touch a board.Otherwise, damage might be caused to the board.

CLASS 1LASER

PRODUCT

This symbol is for laser class.A notice with this symbol indicates the class of the laser.Avoid direct exposure to the laser beams launched from theoptical interface. Otherwise, damage might be caused to theeye or skin.

This symbol is for chassis grounding.A notice with this symbol indicates where the equipment isgrounded.

This symbol is a fan safety warning.A notice with this symbol indicates that the fan leaves shouldnot be touched when the fan is rotating.

!

This symbol is for multi-channel power supply.A notice with this symbol indicates that the multiple channelsof power supply are available.

This symbol is for high temperature warning.The board surface temperature may exceed 70°C when theambient temperature is higher than 55°C. In this case, youneed to wear protective gloves before touching the board.

WARNING-48V OUTPUT

TURN OFF POWER BEFOREDISCONNECTING IF CABLE

! This symbol is for operation warning.The ODU-PWR switch must be turned off before the IF cableis removed.

1 Safety PrecautionsOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

1.2 Safety Precautions for Using the EquipmentBefore using the equipment, read the safety precautions carefully. During the operation of theequipment, follow the safety precautions to ensure the safety of human beings and the equipment.

CAUTIONl Before performing any operation on the equipment, read the operation instructions and

precautions carefully; during the operation, follow the equipment-specific precautions andoperation instructions provided by Huawei strictly to minimize the occurrence of accidents.

l When performing any operation on the equipment, follow the safety regulations of the localareas. The safety precautions described in the manual are only supplements to the local safetyregulations.

l The texts introduced by the word "Caution", "Warning", or "Danger" in each manual do notcover all the safety precautions that must be followed. They are only supplements to thesafety precautions for operations.

l The engineers that are responsible for installing and maintaining Huawei equipment must beequipped with the general knowledge of safety operation. Therefore, they must havecompleted relevant training to familiarize themselves with the proper operation methods andsafety precautions. In addition, they must possess relevant working certificates.

1.2.1 Safety SymbolsSafety symbols indicate the safety instructions that must be followed during the installation ormaintenance.

1.2.2 Electrical SafetyWhen installing or maintaining Huawei network equipment, follow relevant electrical safetyprecautions to ensure the safety of human beings and the equipment.

1.2.3 BatteryWhen installing or maintaining the battery, follow relevant safety precautions for the battery toensure the safety of human beings and the equipment.

1.2.4 MicrowaveWhen installing or maintaining microwave equipment, follow relevant safety precautions forthe microwave equipment to ensure the safety of human beings and the equipment.

1.2.5 Laser and FibersClean the fiber connector correctly. To avoid injury caused by the laser beam to the human body,replace and connect fibers safely.

1.2.6 High-Altitude OperationsWhen doing High-Altitude Operations, follow relevant safety precautions for High-AltitudeOperations to ensure the safety of human beings and the equipment.

1.2.7 Installing and Removing BoardsRemoving the in-service board may result in service interruption. Thus, remove or insert a boardduring off-peak hours.

1.2.8 Miscellaneous



1-3

When installing or maintaining Huawei network equipment, you also need to follow the safetyprecautions for lifting heavy objects, operating sharp-cornered objects and binding signal cablesto ensure the safety of human beings and the equipment.

1.2.1 Safety SymbolsSafety symbols indicate the safety instructions that must be followed during the installation ormaintenance.

Table 1-2 lists the levels and meanings of the safety symbols.

Table 1-2 Levels and meanings of the safety symbols

Levels of the safety symbols Meaning

Indicates a hazard with a high level of riskthat, if not avoided, could result in death orserious injury.

Indicates a hazard with a medium or low levelof risk that, if not avoided, could result inminor or moderate injury to the human body.

Indicates a potentially hazardous situationthat, if not avoided, could cause equipmentdamage, data loss, performance degradation,or other unexpected results.

1.2.2 Electrical SafetyWhen installing or maintaining Huawei network equipment, follow relevant electrical safetyprecautions to ensure the safety of human beings and the equipment.

High Voltage

DANGERThe high voltage power supply supplies power to the device so that it can operate. Direct orindirect contact (through damp objects) with high voltage and AC mains supply may result in afatal accident.

l When installing the AC power supply facility, comply with the local safety regulations.The personnel who install the AC facility must be qualified for performing high voltageand AC operations.

l Do not wear articles that conduct electricity, such as watches, chains, bracelets and ringswhen performing high voltage operations.

l Switch off the power supply immediately, if you find water in the rack or if the rack isdamp.


Maintenance Guide


Issue 02 (2009-06-30)

l Make sure that the device is kept away from water when being operated in a dampenvironment.

WARNINGNon-standard and improper high voltage operations can result in fire and electric shock.Therefore, you must abide by the local rules and regulations when bridging and wiring AC cablesthrough a certain area. The personnel who perform high voltage operations must be qualifiedfor performing high voltage and AC operations.

Power Cable

WARNINGDo not install or remove a live line. Transient contact between the core of the power cable andthe conductor may generate electric arc or spark, which can cause fire or injury to the eye.

l Before bringing the power cable into the power distribution frame (PDF), bind the bareparts of the power cable with insulating tapes.

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

l Before connecting the power cable, make sure that the power cable and label conform tothe requirements of the actual installation.

Short CircuitThe short circuit makes the components fail to work normally and even causes damage to theentire equipment. During the component replacement, avoid the short circuit that may occurwhen you do not operate the tools or boards properly.

Use tools such as a screwdriver according to the regulations. Do not place any tools on thehoneycomb plate of the equipment.

CAUTIONPrevent any screws from falling into the equipment and causing short circuit.

Tools

WARNINGUse special tools when performing high voltage and AC operations.



1-5

Drilling Holes

WARNINGDo not drill on the rack without permission. Drilling on the racks does not conform to the relatedrequirements and may damage the wires and cables inside the rack. If the metal shavings fromthe drilling enter the rack, it may result in short-circuit of the circuit boards. It may also damagethe Electromagnetic Compatibility (EMC) performance of the cabinet.

l Before drilling a hole on the rack, wear insulation gloves, and then remove the cables insidethe rack away.

l During the drilling, ensure that your eyes are completely protected. The hot metal shavingsmay cause injury to your eyes.

l Ensure that the metal shavings do not enter the rack.

l Non-standard drilling may damage the electromagnetic shielding performance of the rack.

l After drilling, clean the metal shavings.

Thunderstorm

DANGERHigh voltage and AC operations, or operations on a steel tower and a mast when there is athunderstorm are prohibited.

When there is a thunderstorm, the electromagnetic field generated in the thunderstorm area maycause damage to electronic components. To prevent the device from being damaged by lightning,use proper grounding.

Electrostatic DischargeThe electronic components on the board can be damaged by the electrostatic discharge. Thus,when replacing the board, make sure that the equipment is properly grounded and take propermeasures to protect the components against electrostatic discharge. For example, wear the ESDwrist strap during the operation.

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

Take the following measures to protect the components against electrostatic discharge:

l Make sure that the equipment is properly grounded according to the equipment groundingrequirement.


Maintenance Guide


Issue 02 (2009-06-30)

l Before touching the equipment, board or integrated circuit (IC) chip, you must wear theESD wrist strap to prevent the electrostatic discharge on the human body from damagingthe static-sensitive components, and ensure that the other end of the strap is properlygrounded. Figure 1-1 shows how to wear the ESD wrist strap.

Figure 1-1 Wearing the ESD wrist strap

CAUTIONMake sure that the metallic portion of the ESD wrist strap is in contact with the skin andthe other end of the ESD wrist strap is properly connected to the anti-static jack.

NOTE

If the ESD wrist strap is unavailable, wear antistatic gloves.

l When correctly wearing an ESD wrist strap, make sure that the resistance value of the ESDwrist strap range from 0.75 Mohms to 10 Mohms. The validity period of the ESD wriststrap is two years. When the resistance of the ESD wrist strap fails to meet the requirement,you need replace the ESD wrist strap.

l Avoid touching the boards with clothing because this may generate static electricity thatcannot be defended by the ESD wrist strap.

l Use the antistatic pad when replacing the board. Wear the ESD wrist strap properly anduse antistatic tweezers or extraction tools to take, remove, or insert chips. Do not touchchips, circuits, or pins with bare hands.

l Keep boards and other static-sensitive parts that are not installed in antistatic bags. Placesome desiccant inside the bag to keep the board dry.

l Place the boards or parts that are temporarily removed on the antistatic pad or other antistaticmaterials. Do not use non-antistatic materials such as white foams, common plastic bags,or paper bags to pack boards. Keep these materials away from boards.



1-7

l Wear an ESD wrist strap when operating the ports of boards because they are also static-sensitive. Discharge the static electricity of cables and protective sleeves before connectingthem to the ports.

l Reserve some board package materials, such as vacuum forming box and antistatic bags inthe equipment room for future use.

1.2.3 BatteryWhen installing or maintaining the battery, follow relevant safety precautions for the battery toensure the safety of human beings and the equipment.

DANGERBefore handling the battery, read the safety precautions and the procedure for connecting thebatteries.

Electrolyte overflow can cause potential damage to the device. It can lead to the corrosion ofmetal parts and circuit boards, and damage the device and cause short-circuit of the circuit boards.

General OperationsBefore installing and maintaining the battery, pay attention to the following:

l Do not wear metallic articles, such as a watch, hand chain, bracelet and ring.

l Use special insulation tools.

l Use eye protection devices.

l Wear rubber gloves. Wear an apron in case of electrolyte overflow.

l Always keep the electrode upright when handling the battery. Do not place the batteryupside down or tilt it.

Short Circuit

CAUTIONShort-circuit in a battery may cause injury. Though the voltage of a battery is low, high transientcurrent generated by a short-circuit releases a large amount of power.

Keep metal objects that can cause battery short-circuit away from the batteries. If metal objectshave to be used, first disconnect the batteries in use and then perform any operations.


Maintenance Guide


Issue 02 (2009-06-30)

Harmful Gas

CAUTIONDo not use unsealed lead-acid battery, because the gas emitted from the battery may result ininflammation or device corrosion. Place the battery horizontally and then fix it properly.

The battery in use may emit flammable gas. Therefore, store the battery in a place with goodventilation, and take precautions against fire.

High Temperature

CAUTIONHigh temperature may result in distortion, damage and electrolyte overflow in the battery.

When the temperature of the battery exceeds 60°C, check whether there is acid overflow. If yes,clean the acid immediately.

Acid Liquid

CAUTIONIn the case of acid overflow, absorb and neutralize the liquid immediately.

When moving or replacing a leaky battery, observe the damage caused by the acid. When acidspill is found, use the following materials to absorb and neutralize it.

l Sodium bicarbonate (baking soda): NaHCO3

l Sodium carbonate (pure alkali): Na2CO3

When using antacids, strictly follow the guide provided by the battery supplier.

1.2.4 MicrowaveWhen installing or maintaining microwave equipment, follow relevant safety precautions forthe microwave equipment to ensure the safety of human beings and the equipment.

WARNINGStrong radio frequency can harm the human body.

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



1-9

1.2.5 Laser and FibersClean the fiber connector correctly. To avoid injury caused by the laser beam to the human body,replace and connect fibers safely.

Laser

CAUTIONThe laser beam launched by the optical interface board or by a fiber can cause damage to youreyes! Do not stare into the fiber connector without wearing protective glasses during theinstallation or maintenance of the fiber.

Cleaning Fiber Connectors

Clean fiber connectors with special cleaning tools and materials. The common tools andmaterials used for cleaning fiber connectors are as follows:

l Special cleaning solvent (Isoamylol is preferred, propyl alcohol is the next, alcohol andformalin is forbidden.)

l Non-woven lens tissue

l Special compressed gas

l Cotton stick (medical cotton or long fiber cotton)

l Special cleaning roll, used with cleaning solvent listed in the first item

l Special magnifier for optical connectors

For cleaning steps, refer to OptiX RTN 950 Radio Transmission System Maintenance Guide.

Replacing Fibers

When replacing a fiber, cap the fiber connector of the unused fiber with the protective cap.

Connecting Fibers

Take the following precautions when connecting fibers.

l If the optical power is excessively high, an optical attenuator should be used to protect theoptical interfaces from being damaged.

l When the fiber connector does not match the optical interface, use an adapter to connectthe connector to the optical interface. In addition, ensure that the optical power meets thespecification requirement of the optical interface after the adapter is used because the useof an adapter introduces certain attenuation.

1.2.6 High-Altitude OperationsWhen doing High-Altitude Operations, follow relevant safety precautions for High-AltitudeOperations to ensure the safety of human beings and the equipment.


Maintenance Guide


Issue 02 (2009-06-30)

WARNINGWhen working at a height, prevent objects from falling down.

When working at a height, comply with the following requirements:

l Only trained personnel can work at a height.

l The operating machines and tools should be carried and handled safely to prevent themfrom falling.

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

l In cold areas, wear warm clothes before performing any high-altitude operation.

l Appliances used for lifting objects must be checked and ensured to be intact beforeperforming any high-altitude operation.

1.2.7 Installing and Removing BoardsRemoving the in-service board may result in service interruption. Thus, remove or insert a boardduring off-peak hours.

DANGERDo not remove the power cable and the PIU board when the power is on.

For details on how to replace the PIU, see "Replace the PIU".

CAUTIONl Before installing or removing a board, wear an ESD glove or ESD wrist strap.

l Do not remove or install the IF board and the IF cable when the equipment is powered on.

l When holding a board, never touch the circuits, components, cable connectors, and cablingtrough on the board.

l Before inserting a board, make sure that the protective tube on the backplane has been takenoff.

l Before inserting a board, make sure that no fiber or cable is connected to the board.

l Insert a board gently to prevent bending of the pins on the backplane.

l Insert a board along the slide rail of each slot to prevent the components on the board fromtouching each other and causing short circuit.

l The interval for removing and inserting a board should be longer than 10 seconds.

After a board is inserted into the equipment, it takes several minutes for the board to enter thenormal running state after the startup.



1-11

1.2.8 MiscellaneousWhen installing or maintaining Huawei network equipment, you also need to follow the safetyprecautions for lifting heavy objects, operating sharp-cornered objects and binding signal cablesto ensure the safety of human beings and the equipment.

lifting heavy objects

WARNINGDo not stand or walk under heavy objects when they are being lifted.

operating sharp-cornered objects

WARNINGWhen carrying the device, wear protection gloves to prevent injuries that can be caused by sharpobjects.

binding signal cables

CAUTIONBundle the signal cables separately from the strong current cables or high voltage cables. Thespace between two adjacent ties must be at least 30 mm.

1.3 Precautions for Using the T2000To use the T2000 correctly, you should be aware of the precautions for the running, setting, andoperation of the T2000.

Precautions for the Running of the T2000To ensure that the T2000 runs properly, be aware of the following precautions:l To ensure that the working power of the T2000 server is stable, use the uninterrupted power

supply (UPS).l Install the T2000 software in a file path that contains only English characters and numbers.

l A T2000 license file is an authorized file and must be kept confidential. Do not make anychange to the license file. Otherwise, the license becomes invalid.

l On the UNIX platform, use the t2000 user to log in to the operating system on which theT2000 server is installed.


Maintenance Guide


Issue 02 (2009-06-30)

l On the Windows platform, use the user that is chosen during the T2000 installation, to login to the operating system. Do not change the login user of Windows.

Precautions for the Setting of the T2000

When you set a computer on which the T2000 server or client runs, be aware of the followingprecautions:

l Do not modify the system time when the T2000 is running. Set the system time when youinstall the T2000.

– If the system time of the server needs to be modified, log out of the T2000 server andthen modify the system time. After the modification, restart the T2000 server.

– If the system time of the client needs to be modified, log out of the T2000 client andthen modify the system time. After the modification, restart the T2000 client.

l Do not modify the name and IP address of the computer where the T2000 server is installed,unless required. Otherwise, the communication among NEs may fail.

Precautions for the Operation of the T2000

When you operate the T2000, be aware of the following precautions:

l When the T2000 is running, ensure that the data is consistent between the T2000 and theNE.

– When the data on an NE has been configured and the NE runs properly, use the uploador synchronization function to keep the data consistent between the T2000 and the NE.

– When the NE data stored on the NE has errors and the NE data stored on the T2000 iscorrect, use the download or restoration function to keep the data consistent betweenthe T2000 and the NE.

l To change the configuration data, abide by the following rules:

– Before you change the configuration data, upload the NE data to keep the NE dataconsistent between the T2000 and the NE.

– Before you change the configuration data, back up the NE database and the T2000database, so that the data can be restored in the case of an operation failure.

– After you change the configuration data, back up the NE database and the T2000database, so that the data can be restored in the case of an NE anomaly.

l Before you set parameters, query the latest data from the NE.

l Be very careful before a dangerous operation is performed. Usually the T2000 presents aprompt to remind of the danger before a dangerous operation is performed.

l Periodically back up the MO data to minimize the loss caused by system anomalies.

– Back up the MO data of the T2000 every month.

– When the service configuration data is changed, immediately back up the MO data ofthe T2000.

l Periodically clear outdated backup data to ensure that there is sufficient disk space for newbackup data.

l For an T2000 system that has multiple clients, you are recommended to use only one clientfor configuration, and to use the other clients for monitoring.



1-13

2 Routine maintenance

About This Chapter

Routine maintenance includes the remote maintenance (on the T2000) and spare partsmaintenance. Check the current state of the equipment to determine the working condition ofthe equipment in time and to prevent any problem from occurring; Check the spare parts toensure that the spare parts can replace faulty components that operate in the network when aboard is faulty.

2.1 Routine Maintenance Items and PeriodsTo ensure the stable and long-term running of the equipment, the equipment should beperiodically maintained. This section describes the routine maintenance items and maintenanceperiods of the equipment according to different maintenance scenarios.

2.2 Guide and Record Table for Routine Maintenance in the NMS CenterTo ensure the normal running of the equipment, check the running status of the equipment, backup the data periodically by using the T2000 and record the maintenance results at the networkmanagement center.

2.3 Field Maintenance and Record Table for Outdoor EquipmentTo ensure the smooth operation of the ODU, you need to periodically check the ODU on siteand record the associated information.

2.4 Guide and Record Table for Routine Maintenance of the Spare PartsTo ensure that the spare parts of the equipment are normal, check the spare parts in the storehouseregularly and record the check results.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 2 Routine maintenance


2-1

2.1 Routine Maintenance Items and PeriodsTo ensure the stable and long-term running of the equipment, the equipment should beperiodically maintained. This section describes the routine maintenance items and maintenanceperiods of the equipment according to different maintenance scenarios.

Table 2-1 lists the routine maintenance items and periods.

Table 2-1 Maintenance items and periods

MaintenanceOwner

Maintenance Site

Maintenance Item Maintenance Period

T2000operator

NMS center Checking the status of the NE and boards Daily

Browsing network-wide alarms Daily

Browsing abnormal events Daily

Browsing the current performance events Daily

Browsing the performance events of theRMON statistics group

Daily

Checking the optical power Daily

Browsing DCN Communication Status Daily

Browsing the running status of dynamic tunnel Daily

Browsing the PW working status Daily

Browsing the history performance events Monthly

Browsing the RMON history performanceevents

Monthly

Backing up the MO data of the T2000 Monthly

Backing up the NE database Monthly

Testing the IF 1+1 Switching Monthly

Maintenance engineer

Installationsite

Checking the ODU Half-yearly

Checking the Hybrid Coupler Half-yearly

Checking the Antenna Half-yearly

Checking IF Cables Half-yearly

Maintenance engineer

Spare partscenter

Testing the spare parts Half-yearly

2 Routine maintenanceOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

2.2 Guide and Record Table for Routine Maintenance in theNMS Center

To ensure the normal running of the equipment, check the running status of the equipment, backup the data periodically by using the T2000 and record the maintenance results at the networkmanagement center.

2.2.1 Checking the Status of the NE and BoardsRegularly check the status of the NE and boards on the NE. In this way, the anomalies can bedetected and then handled in time.

2.2.2 Browsing Network-Wide AlarmsRegularly browse alarms to detect and rectify faults in time.

2.2.3 Browsing Abnormal EventsRegularly browse performance events of an NE. In this way, you can determine the currentrunning status of the NE and avoid the faults that are likely to occur.

2.2.4 Browsing the Current Performance EventsBrowse the current performance events periodically to check the current running state of theequipment. In this way, potential faults can be eliminated in time.

2.2.5 Browsing the Performance Events of the RMON Statistics GroupBrowse the performance events of the RMON statistics group periodically. this helps you tolearn the running status of the ports and links, and the quality of services (QoS).

2.2.6 Checking the Optical PowerIf the mean transmitted power and the receive power of the optical interface is excessively lowor high, bit errors occur or the optical components may be damaged, and thus services areaffected. To prevent this problem from occurring, you should check the optical power regularlyof every optical interface of the optical interface board.

2.2.7 Browsing the History Performance EventsBrowse the history performance events periodically to learn the long-term running state of theequipment. In this way, potential faults can be eliminated in time.

2.2.8 Browsing the RMON History Performance EventsBrowse the history RMON performance events periodically. This helps you to understand therunning status of the ports and channels, and the long-term quality of services.

2.2.9 Backing up the MO Data of the T2000Periodically back up the T2000 MO data. When the T2000 data is lost, use the MO data to fastrestore the T2000 data.

2.2.10 Backing up the NE DatabaseTo ensure that the NE data can be quickly restored after the database of the system control boardis lost or the power failure occurs to the equipment, you should back up the NE databaseperiodically.

2.2.11 Testing the IF 1+1 SwitchingPeriodically testing the IF 1+1 switching helps you to check whether the equipment can switchover normally.

2.2.12 Maintenance Record TableMaintenance record table is used to record the result of the maintenance operations.



2-3

2.2.1 Checking the Status of the NE and BoardsRegularly check the status of the NE and boards on the NE. In this way, the anomalies can bedetected and then handled in time.

Prerequisitel The T2000 must be started in the NMS center.

l The NE must be configured and the NE configuration data must be uploaded to the T2000.

l You must be a T2000 user with the "NE Monitor" authority or higher.

Maintenance Period

Daily

Tools, Instruments and Materials

T2000

Operation Criteria

The NE icon and boards icon should be displayed in green on the T2000, and their workingstatus is normal.

Procedure

Step 1 Click the shortcut icon in the T2000 Main Topology to display the description of NE status.

Step 2 Check the NE status in the T2000 Main Topology. Normally, The NE icon should be displayedin green and its working status is normal. If not, handle the problem with reference tothe following and the 3 Troubleshooting and 9 Alarm.

l If the NE icon is grey and is present above the NE icon, it indicates that thecommunication between the T2000 and NE is interrupted.

l If the NE icon is red , it indicates that the highest severity level of the alarms generatedon the NE is critical.

l If the NE icon is orange , it indicates that the highest severity level of the alarmsgenerated on the NE is major.

l If the NE icon is yellow , it indicates that the highest severity level of the alarmsgenerated on the NE is minor.

l If the NE icon is slight-blue , it indicates that the highest severity level of the alarmsgenerated on the NE is warning.

l If is present above the NE icon, it indicates that the T2000 and the NE are inconsistentwith respect to the NE configuration data. In this case, refer to 8.8 Uploading the NEConfiguration Data.

Step 3 Double-click the NE icon. The NE status displayed in the upper left portion of the NE slot layoutshould be "Running Status". If the NE status is "unknown", it indicates that the NE fails to


Maintenance Guide


Issue 02 (2009-06-30)

communicate with the T2000, or that the NE status cannot be detected because of a fault on theequipment. Handle the problem with reference to 3 Troubleshooting and 9 Alarm.

Step 4 Click the shortcut icon in the NE slot layout to display the description of board status.

Step 5 Query the working state of the board. The board icon should be green . If the board iconis of any other colors, take the following guidelines to handle the anomaly.

l If the board icon is slight-green , It indicates that the physical board is in position butthe logical board is not added on the T2000. Right-click the board, and choose AddBoard from the shortcut menu.

l If the board icon is blue , it indicates that the board is in the running state but not inposition. In this case, the physical board is not in position but the logical board is added onthe T2000. Check the board on site to ensure that the board is installed and the board is inproper contact with the backplane.

l If the board icon is grey , it indicates that the board is in the installation state and isrunning abnormally. In this case, check whether the configuration data of the board is corrector whether the board becomes faulty.

l If is displayed in the lower right portion of the board icon, it indicates that the board isin the protection state. If the original working board is in the protection state, troubleshootthe board.

l If is displayed in the lower left portion of the board icon or is displayed in the upperright portion of the board icon, it indicates that loopback is set to the board. Determinewhether to release the loopback on the board as required.

----End

2.2.2 Browsing Network-Wide AlarmsRegularly browse alarms to detect and rectify faults in time.


l The NE must be configured and the NE configuration data must be uploaded to the T2000.


Maintenance PeriodDaily

Tools, Equipment and MaterialsT2000

Operation CriteriaUse the T2000 to query the network-wide alarms. No new alarms exist.

NOTE

New alarms are the alarms generated during the query intervals.



2-5

Procedure

Step 1 Click in the upper right portion of the Main Topology of the T2000 to display theCurrent Alarms-[All Critical] interface. You can browse the current critical alarms.

NOTE

When the indicator is surrounded by a square frame , it indicates that there are critical alarmsto be acknowledged.

When the indicator is surrounded by a square frame and the square frame flashes, it indicatesthat there are new critical alarms to be acknowledged.The number in the middle of the indicator indicates the number of current network-wide uncleared criticalalarms. Keep the Current Alarms-[All Critical] interface open when alarms are monitored.

Step 2 Select the new cleared alarms and check the alarm causes. Check whether these alarms indicateany probable faults by referring to 3 Troubleshooting and 9 Alarm.

Step 3 Select all the alarms and click Acknowledge. The cleared alarms disappear and are stored ashistory alarms.

Step 4 Select the new uncleared alarms and then check the alarm causes. Handle the faults withreference to 3 Troubleshooting and 9 Alarm.

Step 5 Click in the upper right portion of the Main Topology of the T2000 to browse the currentmajor alarm, and follow Step 2 to Step 4 to check and handle the new major alarms.

NOTE

When the indicator is surrounded by a square frame , it indicates that there are major alarmsto be acknowledged.

When the indicator is surrounded by a square frame and the square frame flashes, it indicatesthat there are new major alarms to be acknowledged.The number in the middle of the indicator indicates the number of current network-wide uncleared majoralarms. Keep the Current Alarms-[All Major] interface open when alarms are monitored.

Step 6 Click in the upper right portion of the Main Topology of the T2000 to browse the currentminor alarm, and follow Step 2 to Step 4 to check and handle the new minor alarms.

NOTE

When the indicator is surrounded by a square frame , it indicates that there are minor alarms tobe acknowledged.

When the indicator is surrounded by a square frame and the square frame flashes, it indicatesthat there are new minor alarms to be acknowledged.The number in the middle of the indicator indicates the number of current network-wide uncleared minoralarms. Keep the Current Alarms-[All Minor] interface open when alarms are monitored.

----End

2.2.3 Browsing Abnormal EventsRegularly browse performance events of an NE. In this way, you can determine the currentrunning status of the NE and avoid the faults that are likely to occur.


Maintenance Guide


Issue 02 (2009-06-30)


l The NE must be configured and the data must be uploaded to the T2000.




Operation CriteriaNone

Procedure

Step 1 Choose Fault > Browse Event from the Main Menu of the T2000 to display the Events windowand filter dialog box.

NOTE

If you previously set the startup template for browsing performance events (set the filter conditions), theFilter dialog box is not displayed. Instead, the performance events matching the startup template are directlydisplayed. For details on how to create a startup template, refer to the OptiX iManager T2000 Online Help.

Step 2 Optional: Click Import in the lower left corner in the Basic Settings tab or Event Source tabto import the event browse template previously set. For details on how to create an event browsetemplate by setting filter conditions, refer to the OptiX iManager T2000 Online Help.

NOTE

The default event browse template covers all abnormal performance events and all NEs.

Step 3 Set the filter conditions for browsing performance events in the Basic Settings tab of theFilter dialog box.

1. Optional: Select the Event Name check box and click . In the displayed SelectEvent dialog box, select the performance events to be browsed.

2. In the Basic Settings tab of the Filter dialog box, set Severity, Type, and GeneratedTime for performance events.

3. Optional: Select the Remarks contain check box and enter the remarks made previouslyfor specific performance events in the text box behind the Remarks contain to filter theperformance events.

Step 4 In the Event Source tab of the Filter dialog box, select the NEs whose performance events areto be browsed.1. Set the mode for selecting NEs in the Select Mode group box.2. Adopt either of the following modes to select NEs whose performance events are to be

browsed.l Enter the key words of the NE name or NE type in the text box below Object name

(By object) or Type (By type). Fuzzy search is supported. During the search, separate



2-7

key words with spaces. Then, click Find. The matched NE names or NE types aredisplayed in the Navigation Tree.

l Select the NE name or NE type in the Object Navigation Tree (By object) or TypeNavigation Tree (By type).

Step 5 Click OK. The matched performance events, if there is any, are displayed in the Events window.

Step 6 Handle these abnormal performance events according to experience and by referring to the 3Troubleshooting and 9 Alarm.

Step 7 Optional: Click Print or Save As to output the performance event data.

----End

2.2.4 Browsing the Current Performance EventsBrowse the current performance events periodically to check the current running state of theequipment. In this way, potential faults can be eliminated in time.


l The service must be configured.

l The performance monitoring function must be enabled. In addition, the performancemonitoring parameters must be set.

NOTE

For details on how to enable the performance monitoring function and how to set the monitoringparameters, refer to the iManager T2000 Online Help.

l You must be a T2000 user with the "NE and network monitor" authority or higher.



Operation CriteriaFor different objects, the checking criteria are listed as follows:

l For the port, no bit errors are generated or received.

l For the board, the working temperature, CPU utilization and memory utilization are normal.

l For the MPLS tunnel and Ethernet service, no packet loss or error occurs.

ProcedureStep 1 On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose NE

Explorer to display the NE Explorer window.

Step 2 In the NE Explorer, select an NE, and then enter the browse performance interface of each objectin the following way.


Maintenance Guide


Issue 02 (2009-06-30)

Object Entry

Port/board Select the corresponding board, and then choose Performance >Current Performance from the Function Tree.

MPLS Tunnel 1. Choose Configuration > MPLS Management > Unicast TunnelManagement from the Function Tree.

2. Select one or multiple tunnels.3. Right-click the tunnel to choose Browse Performance to display

the Performance Management window.4. Select the Current Performance tab.

Ethernet service 1. Choose Configuration > Ethernet OAM Management >Ethernet Service OAM Management from the Function Tree.

2. Click the Maintenance Association tab, and then select one ormultiple MEP points.

3. Right-click the MEP points to choose Browse Performance todisplay the Performance Management window.

4. Select the Current Performance tab.

Step 3 Select a monitored Object and the Monitor Period for this object.

NOTE

l Choose whether to display the consecutive severe bit error seconds according to requirements.

l If the object to be viewed is a physical port, you can also set the related query parameters for Gaugeand Count as required.

Step 4 Click Query to query the data from the NE.

Step 5 Optional: Click Reset to reset the performance register of the queried performance event.

NOTE

After the performance register is reset, the current performance data of this type is cleared. Then, a newperformance monitoring period is started.


----End

2.2.5 Browsing the Performance Events of the RMON StatisticsGroup

Browse the performance events of the RMON statistics group periodically. this helps you tolearn the running status of the ports and links, and the quality of services (QoS).






2-9

NOTE

For details on how to enable the performance monitoring function and how to set the monitoringparameters, refer to the OptiX iManager T2000 Online Help.




Operation CriteriaNo packet loss and error packets occur.

Procedure

Step 1 On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose NEExplorer to display the NE Explorer window.

Step 2 In the NE Explorer, select the NE, and then enter the browse performance interface of eachobject in the following way.

Object Entry

Port/board Select the corresponding board, and then choose Performance >RMON Performance from the Function Tree.

MPLS tunnel 1. Choose Configuration > MPLS Management > Unicast TunnelManagement from the Function Tree.

2. Select one or multiple tunnels. Right-click the tunnel to chooseBrowse Performance to display the Performance Managementwindow.

PW 1. Choose Configuration > MPLS Management > PWManagement from the Function Tree.

2. Select one or multiple PWs, and then right-click the PW to chooseBrowse Performance to display the Performance Managementwindow.

ATM service 1. Choose Configuration > ATM Service Management from theFunction Tree.

2. Select one or multiple ATM services, and then right-click the serviceto choose Browse Performance to display the PerformanceManagement window.


Maintenance Guide


Issue 02 (2009-06-30)

Object Entry

CES service 1. Choose Configuration > CES Service Management from theFunction Tree.

2. Select one or multiple CES services, and then right-click the CESservice to choose Browse Performance to display the PerformanceManagement window.

Ethernet service 1. Choose Configuration > Ethernet Service Management from theFunction Tree, and then select an Ethernet service type.

2. Select one or more services, and then right-click the service to chooseBrowse Performance to display the Performance Managementwindow.

Step 3 Click the Statistics Group tab.

Step 4 Select the monitored objects and performance events and set Query Conditions and DisplayMode.

NOTE

l If a performance event does not support the display of the accumulated value, after you check theDisplay Accumulated Value check box in Query Conditions, perform the statistics. A dialog box isdisplayed, indicating that the performance event cannot display the accumulated value.

l When Display Mode is set to Graphics, the number of the selected performance events cannot exceed10.

Step 5 Click Start to display the results.NOTE

If performance statistics should be made again, click Resetting begins.

----End

2.2.6 Checking the Optical PowerIf the mean transmitted power and the receive power of the optical interface is excessively lowor high, bit errors occur or the optical components may be damaged, and thus services areaffected. To prevent this problem from occurring, you should check the optical power regularlyof every optical interface of the optical interface board.



NOTE






2-11

Tools, Equipment and Materials

T2000

Operation Criteria

For the technical specifications of the mean transmitted optical power and receive optical powerof different optical interfaces, refer to Technical Specifications of Boards in the OptiX RTN950 Radio Transmission System Product Description manual.

Procedure


Step 2 Select a board or interface board with the optical interface in the NE Explorer. Then, ChoosePerformance > Current Performance from the Function Tree.

Step 3 In Performance Event Type, select transmitted Optical Power and receive Optical Power.Then, click Query.

Step 4 Check whether the transmitted optical power and receive optical power are within the normalrange.

NOTE

The receive optical power must follow the standard: receiver sensitivity + 3 dBm < receive optical power (tested)< overload threshold - 5 dBm.

Step 5 Optional: If the mean transmitted optical power is not within the normal range, handle the faultwith reference to the following.1. Check and clean the fiber connector according to 8.24 Inspecting and Cleaning the

Optical Fiber Connectors.2. Perform Step 2 - Step 4 to test the mean transmitted optical power of the optical interface

again, until the mean transmitted optical power obtained is within the normal range.3. Restore the fiber connection at the tested optical interface.

Step 6 Optional: If the receive optical power is not within the normal range, handle the fault withreference to the following.l If the receive optical power is less than sensitivity + 3 dBm:

1. Check whether the fiber connector and the optical attenuator are clean.2. If the fiber connector is not clean, clean it according to 8.24 Inspecting and Cleaning

the Optical Fiber Connectors.


Maintenance Guide


Issue 02 (2009-06-30)

3. If the fiber flange or the optical attenuator on the ODF side is not clean, replace thefiber flange or the optical attenuator.

4. Perform Step 2 - Step 4 to test the receive optical power of the optical interface again,until the receive optical power obtained is within the normal range.

5. Restore the fiber connection at the tested optical interface.

l If the receive optical power is larger than overload threshold - 5 dBm

1. Check whether the optical attenuator is normal.

2. If the optical attenuator is normal, add an optical attenuator on the ODF side.

3. If the optical attenuator is not normal, replace the optical attenuator.

4. Perform Step 2 - Step 4 to test the receive optical power of the optical interface again,until the receive optical power obtained is within the normal range.

5. Restore the fiber connection at the tested optical interface.

Step 7 Repeat the previous steps to test the transmitted optical power and receive optical power at allthe other optical interfaces of the equipment one by one.

----End

2.2.7 Browsing the History Performance EventsBrowse the history performance events periodically to learn the long-term running state of theequipment. In this way, potential faults can be eliminated in time.




NOTE

For details on how to enable the performance monitoring function and how to set the monitoringparameters, refer to the iManager T2000 Online Help.


Maintenance Period

Monthly


T2000

Operation Criteria

Determine the stability of service links by analyzing the collected history performance data.Check the links working in an unstable state.



2-13

Procedure


Step 2 In the NE Explorer, select an NE, and then enter the browse performance interface of each objectin the following way.

Object Entry

Physical port/board

Select the corresponding board, and then choose Performance >History Performance from the Function Tree.


2. Select one or multiple tunnels.3. Right-click the tunnel to choose Browse Performance to display the

Performance Management window.4. Select the History Performance tab.

Ethernet service 1. Choose Configuration > Ethernet OAM Management > EthernetService OAM Management from the Function Tree.

2. Click the Maintenance Association tab, and then select one ormultiple MEP points.

3. Right-click the MEP points to choose Browse Performance todisplay the Performance Management window.

4. Select the History Performance tab.

Step 3 Choose monitored Object and set the Monitor Period, From, To and Data Source.

NOTE

l If you view the history performance data from NE, you can set save to database by your need.

l If the object is physical port, you can also set the parameters of Gauge and Count.

Step 4 Click Query to display the results.

Step 5 Optional: Click Reset to reset the performance registers.

NOTE

After the resetting, the history performance data is deleted and a new performance monitoring period isbeginning.


----End

2.2.8 Browsing the RMON History Performance EventsBrowse the history RMON performance events periodically. This helps you to understand therunning status of the ports and channels, and the long-term quality of services.


Maintenance Guide


Issue 02 (2009-06-30)




NOTE



Maintenance Period

Monthly


T2000

Operation Criteria

Determine the long-term running quality of the service by analyzing and collecting the historyperformance data. In the case of links with high loading for a long time, adjust the services. Takesome measures to prevent the high loading working state within a period. If the service linkworks in an unstable state, clear the interference in time.

Procedure


Step 2 In the NE Explorer, select the NE, and then enter the browse performance interface of eachobject in the following way.

Object Entry

Port/board Select the corresponding board, and then choose Performance >RMON Performance from the Function Tree.


2. Select one or multiple tunnels. Right-click the tunnel to chooseBrowse Performance to display the Performance Managementwindow.

PW 1. Choose Configuration > MPLS Management > PWManagement from the Function Tree.

2. Select one or multiple PWs, and then right-click the PW to chooseBrowse Performance to display thePerformance Managementwindow.



2-15

Object Entry

ATM service 1. Choose Configuration > ATM Service Management from theFunction Tree.

2. Select one or multiple ATM services, and then right-click the serviceto choose Browse Performance to display the PerformanceManagement window.

CES service 1. Choose Configuration > CES Service Management from theFunction Tree.

2. Select one or multiple CES services, and then right-click the CESservice to choose Browse Performance to display the PerformanceManagement window.

Ethernet service 1. Choose Configuration > Ethernet Service Management from theFunction Tree, and then select an Ethernet service type.

2. Select one or more services, and then right-click the service to chooseBrowse Performance to display the Performance Managementwindow.

Step 3 Click the History Group tab.

Step 4 Select the monitored objects and performance events and set From, To, History Table Typeand Display Mode.

NOTE

When Display Mode is set to Graphics, the number of the selected performance events cannot exceed 10.

Step 5 Click Query to display the results.

----End

2.2.9 Backing up the MO Data of the T2000Periodically back up the T2000 MO data. When the T2000 data is lost, use the MO data to fastrestore the T2000 data.

PrerequisiteYou must be a T2000 user with "NM Maintainer" authority or higher.

ContextThe default directories where the database file should be backed up are as follows.l On the UNIX platform, back up the MO data to /T2000/server/database/dbbackup.

l On the Windows platform, back up the MO data to \T2000\server\database\dbbackup.

NOTE

l The MO data backed up can not be restored on T2000 of different versions.

l Multiple modes of backing up the MO data are available. This section only describes the mode ofbacking up the MO data to the local server. For other backup modes, refer to the OptiX iManagerT2000 Online Help.


Maintenance Guide


Issue 02 (2009-06-30)

Maintenance Period

Monthly


T2000

Operation Criteria

The system indicates that the backup operation is successful.

Procedurel Back up the MO data on the T2000 client.

1. Choose System > Database > Database Backup from the Main Menu, and then theBackup dialog box is displayed.

2. To set the backup directory on the server, click Backup. The T2000 backs up thedatabase immediately and a progress bar is displayed.

NOTE

The backup directory should be short and should not contain special characters, such as spaces,punctuations or Chinese characters.

l Back up the MO data by using the database management tool.

1. Start Database Management Tool.

– On the Windows platform, open Windows Explorer. In the \T2000\server\database directory, run T2000DM.exe. The T2000DM.exe window appears andthen immediately disappears, and the Database Management Tool windowdisplays.

– On the UNIX platform, right-click on the CDE desktop and then choose Tools >Terminal to display a terminal window. In the /T2000/server/database directory,run T2000DM.sh to display the Database Management Tool window.

2. In Database Server List on the left, select T2000DBServer.

3. In the displayed dialog box, enter the password of user sa.

NOTE

By default, the password of user sa is null.

4. Click Backup MO to display the Description dialog box.

5. Set the backup directory on the server, and enter the relevant description information.Click Backup to display the Backup MO dialog box. In this case, the backup of theMO data of the T2000 is started.

NOTE

l Customizing the backup directory of the data prevents the backup data from being affectedwhen you reinstall the system or format disk C. In this way, the maintainability of thesystem is improved.

l The backup directory should be short and should not contain special characters, such asspaces, punctuations or Chinese characters.



2-17

6. In the Backup MO dialog box, the progress of MO data backup is displayed. Whenthe backup is finished, click OK in the dialog box. Return to the database managementtool interface.

----End

2.2.10 Backing up the NE DatabaseTo ensure that the NE data can be quickly restored after the database of the system control boardis lost or the power failure occurs to the equipment, you should back up the NE databaseperiodically.

Prerequisitel You must be a T2000 user with "NE and network operator" authority or higher.

l You must log in to the NE as an NE user of the system level.

Maintenance Period

Monthly


T2000

Operation Criteria

The system indicates that the backup operation is successful.

Procedure

Step 1 Choose Configuration > Configuration Data Management from the Main Menu.

Step 2 In the Object Tree on the left, select one or more NEs and click .

Step 3 Select one or more NEs from Configuration Data Management List.

Step 4 Click Back Up NE Data, select Back Up Database To SCC or Manually Back Up DatabaseTo SCC.

Step 5 Click OK in the Confirm dialog box, and then the system starts to back up the NE database.

Step 6 After the backup is complete, the Operation Result dialog box, which indicates that the backupis successful, is displayed. Click Close.

----End

2.2.11 Testing the IF 1+1 SwitchingPeriodically testing the IF 1+1 switching helps you to check whether the equipment can switchover normally.


Maintenance Guide


Issue 02 (2009-06-30)

Prerequisitel The T2000 is in normal communication with the NE.

l The NE user has the authority of maintenance level or higher.

Tools, Instruments, and MaterialsT2000

Precautionsl The IF 1+1 switching performed manually is a HSB switching. During the 1+1 protection

switching (< 200 ms), protection services are interrupted. Hence, you are recommended tocarry out 1+1 protection switching when the traffic is light.

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

Procedure

Step 1 Select an NE from the NE Explorer, and choose Configuration > Microwave LinkConfiguration from the Function Tree.

Step 2 Select the IF 1+1 Protection tab.

Step 3 In Protection Group, select the protection group that is to be switched over.

Step 4 In Slot Mapping Relation, right-click the IF board, and choose Manual Switch toProtection from the shortcut menu.

Step 5 Click OK to begin the protection switching.

Step 6 Click Query to check the protection switching status.After the switching is complete, the Switching Status of Device of the working board shouldbe Manual Switching.

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

Step 8 Repeat Step 1 to Step 3.

Step 9 In Slot Mapping Relation, right-click the 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.The Switching Status of Device of the working board should be Normal.

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

----End




2-19

Maintenance Item Maintenance Status Remarks MaintainerChecking the status of the NE and the boards □Normal □Abnormal

Browsing the network-wide alarms

Checking the optical power

Browsing the current performance

Maintenance date：

Problems and their solution:

Pending problems:

Verification:

Maintenance Record Table

□Normal □Abnormal


□Normal □AbnormalBrowsing DCN communication status

Browsing the performance of the RMON statistics group



Browsing the history performance□Normal □Abnormal

Browsing the RMON history performance


Backing up the MO data of the T2000 □Normal □AbnormalBacking up the NE database □Normal □Abnormal

Browsing Abnormal Events □Normal □Abnormal

Testing the IF 1+1 Switching □Normal □Abnormal

Browsing the running status ofdynamic tunnelBrowsing the PW working status



2.3 Field Maintenance and Record Table for OutdoorEquipment

To ensure the smooth operation of the ODU, you need to periodically check the ODU on siteand record the associated information.

2.3.1 Checking the ODUPeriodically checking the ODU helps you to find faults and hidden troubles of the ODU in atimely manner.


Maintenance Guide


Issue 02 (2009-06-30)

2.3.2 Checking the Hybrid CouplerPeriodically checking a hybrid coupler helps you to find faults and hidden troubles of the couplerin time.

2.3.3 Checking the AntennaPeriodically checking an antenna helps you to find faults and hidden troubles of the antenna ina timely manner.

2.3.4 Checking IF CablesPeriodically checking the IF cables helps you to find faults and hidden troubles of the cables ina timely manner.


2.3.1 Checking the ODUPeriodically checking the ODU helps you to find faults and hidden troubles of the ODU in atimely manner.

PrerequisiteNone.

Tools, Instruments, and MaterialsNone.

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

For plain areas, the lightning arrester protects the area that is located within an angle of 45° underit. For mountainous areas and the areas where lightning frequently occurs, the lightning arresterprotects the area that is located within an angle of 30° under it.

Step 2 Ensure that the ODU is properly fixed 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 firmly and reliably grounded.

----End

2.3.2 Checking the Hybrid CouplerPeriodically checking a hybrid coupler helps you to find faults and hidden troubles of the couplerin time.

PrerequisiteNone.




2-21

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


Step 2 Ensure that the coupler is reliably fixed 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

2.3.3 Checking the AntennaPeriodically checking an antenna helps you to find faults and hidden troubles of the antenna ina timely manner.

PrerequisiteNone.


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


Step 2 Ensure that the antenna is reliably fixed 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

2.3.4 Checking IF CablesPeriodically checking the IF cables helps you to find faults and hidden troubles of the cables ina timely manner.


Maintenance Guide


Issue 02 (2009-06-30)

PrerequisiteNone.


Procedure

Step 1 Check the appearance of cables.l There should be no bent or twisted cable.

l There should be no bare copper wire.

l The bending radius of the cable should be greater than 30 cm.

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

l The cable connector should be waterproof.

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

l The grounding cable should be routed from top downwards. The angle between the groundingcable and the IF cable should not be more than 15 degrees.

----End


Table 2-2 Maintenance Record Table

MaintenanceItem

MaintenanceStatus

MaintenancePeriod

Remarks Maintainer

Checking theODU


Half a year

Checking theHybrid Coupler


Half a year

Checking theAntenna


Half a year

Checking IFCables


Half a year


Pending problems:

Verification:



2-23

2.4 Guide and Record Table for Routine Maintenance of theSpare Parts

To ensure that the spare parts of the equipment are normal, check the spare parts in the storehouseregularly and record the check results.

2.4.1 Testing the Spare PartsCheck the status and versions of the spare parts regularly. This ensures that the spare parts canreplace the faulty boards in the existing network at any time and thus improves the maintenanceefficiency.

2.4.2 Maintenance Record TableMaintenance record table is used to record the result of maintenance operations.

2.4.1 Testing the Spare PartsCheck the status and versions of the spare parts regularly. This ensures that the spare parts canreplace the faulty boards in the existing network at any time and thus improves the maintenanceefficiency.

Prerequisitel Important boards must be available in the spare parts center.

l Spare NEs must be available in the spare parts center for testing the spare parts.

Maintenance PeriodHalf-yearly


Operation CriteriaIn terms of the BIOS version, software version, and the FPGA version, the spare parts shouldbe consistent with or compatible with the boards of the same type running on the network.

NOTEA portion of the boards of different printed circuit board (PCB) versions are mutually compatible. If thePCB versions of the spare parts are different from those of the running boards, consult local Huaweitechnical support engineers.

Procedure

Step 1 Log in to the T2000 client. Choose Report > Board Information Report from the Main Menu.

Step 2 Click on the left to refresh the Navigation Tree. Then, select the NE and boards for query

and click .


Maintenance Guide


Issue 02 (2009-06-30)

Step 3 Click Query. A dialog box is displayed to indicate that the operation is successful.

Step 4 Click Close. The status and version information of each board of the NE is displayed in theinterface.

Step 5 Record the BIOS version, software version, PCB version and logic version of the spare part.

Step 6 Check whether the version of the spare part is consistent with that of the board of the same typerunning in the network. If inconsistent, consult local Huawei technical support engineers forhandling.

----End

Reference Information

Follow the listed principles to maintain the spare parts.

l Principle for check of spare parts:– Check the version and quality of spare parts periodically.

– The version of spare part must be consistent with the version of the same type of boardrunning in the network in terms of software, BIOS, PCB and logic.

– When the network is to be upgraded, provide the parts in time and upgrade the versionof the running parts.

l Principle for storage of parts:– The spare parts must be stored in line with regulations and be kept for exclusive use.

– The spare parts must be stored in anti-static bags and no friction should be caused amongthem. These bags with parts inside should be kept in special anti-static cupboard andaway from sundries.

– Wear an anti-static glove to touch the spare parts.

– The inbound/outbound information must be recorded and timely refreshed. Hence, theparts can be supplemented accordingly.

2.4.2 Maintenance Record TableMaintenance record table is used to record the result of maintenance operations.

Table 2-3 Maintenance Record Table

Maintenance Item MaintenanceStatus

Remarks Maintainer

Testing the SpareParts



Pending problems:

Verification:



2-25

3 Troubleshooting

About This Chapter

This chapter describes the thought and process of troubleshooting equipment faults with respectto the common flow, emergency flow, information collection, and fault notification.

3.1 General Fault Handling FlowAdherence to the general fault handling flow helps you to rectify the system faults in time.

3.2 Emergency Flow of Handling the Service Interruption FaultIf any fault causes service interruption, follow the general fault handling flow and also take otheremergency measures, such as backup trails, to reduce the service interruption time to theminimum.

3.3 Troubleshooting Microwave LinksWhen an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade ofa microwave link, there is a microwave link fault.

3.4 CES Service TroubleshootingThis section describes how to troubleshoot interruption or bit errors of the CES service in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

3.5 Ethernet Service TroubleshootingThis section describes how to troubleshoot Ethernet service interruption or packet loss in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

3.6 Clock TroubleshootingThis section describes how to troubleshoot loss of the clock source and degrade of clock signalsin terms of the symptoms, impact on the system, possible causes, tools required fortroubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

3.7 QoS TroubleshootingThis section describes the QoS faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

3.8 Inband DCN Troubleshooting

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 3 Troubleshooting


3-1

This section describes the inband DCN faults in terms of the symptoms, impact on the system,possible causes, tools required for troubleshooting, troubleshooting procedure, and precautionsthat should be taken during the troubleshooting.

3.9 LAG TroubleshootingThis section describes the LAG faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

3.10 ML-PPP TroubleshootingThis section describes the ML-PPP faults such as service interruption, packet loss, or bit errorin terms of the symptoms, impact on the system, possible causes, tools required fortroubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

3.11 IMA TroubleshootingThis section describes the IMA faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

3.12 FRR TroubleshootingThis section describes the FRR faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

3.13 MPLS APS TroubleshootingThis section describes the MPLS APS faults in terms of the symptoms, impact on the system,possible causes, tools required for troubleshooting, troubleshooting procedure, and precautionsthat should be taken during the troubleshooting.

3.14 Information Collection and Information RecordCollect information and record the information in a timely manner for locating and rectifyingthe fault quickly.

3.15 Fault Notification and Technical SupportDuring troubleshooting, you can inform Huawei of the faults and apply for technical support, ifnecessary.

3 TroubleshootingOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

3.1 General Fault Handling FlowAdherence to the general fault handling flow helps you to rectify the system faults in time.

Flow DiagramFigure 3-1 shows the general flow diagram for handling faults.

Figure 3-1 General flow diagram for handling faults

Observe and record fault phenomenon

Yes

No

Start

Other handling flow

Find cause and locate fault

Fault rectified?

Write faulthandling report

End

Contact Huawei for technical support

Find solution together and rectify fault

Yes

No

Rectify fault

External anomalies?

Description of the Fault Handling FlowObserve and record fault phenomena

Observe the fault phenomena and record them. Record the details of the fault, especially thetime when the fault occurs, and the operations performed before and after the fault in details.



3-3

You can also save the important data such as the alarm and performance event information storedon the T2000.

Handle external anomalies

Check whether the fault lies in external anomalies concerning the power supply, fiber, ambiencein the equipment room (temperature, for example), and terminal equipment. If yes, handle theanomalies immediately.

Make experience-based judgment and theory-based analysis

According to the information on the fault phenomena and other fault-related information,analyze the probable causes based on the experience and related theories.

Rectify faults

According to the probable causes, make a plan to confirm each probable cause, find out the mostlikely cause, and rectify the fault. For details, refer to Table 3-1.

Table 3-1 Troubleshooting for different services and functions

SN

Type of trouble Contents

1 Microwave Links Refer to 3.3 Troubleshooting Microwave Links.

2 CES service Refer to 3.4 CES Service Troubleshooting.

3 Ethernet service Refer to 3.5 Ethernet Service Troubleshooting.

4 Clock Refer to 3.6 Clock Troubleshooting.

5 QoS Refer to 3.7 QoS Troubleshooting.

6 Inband DCN Refer to 3.8 Inband DCN Troubleshooting.

7 LAG Refer to 3.9 LAG Troubleshooting.

8 ML-PPP Refer to 3.10 ML-PPP Troubleshooting.

9 IMA Refer to 3.11 IMA Troubleshooting.

10 FRR Refer to 3.12 FRR Troubleshooting.

11 MPLS APS Refer to 3.13 MPLS APS Troubleshooting.

NOTE

Confirm the probable causes one by one.

Check whether the fault is rectified

After confirming a cause, analyze the result to check whether the fault is rectified and whetherany new fault occurs.

l If the fault persists, contact Huawei technical support engineers.

l If the fault is rectified, prepare the fault handling report.


Maintenance Guide


Issue 02 (2009-06-30)

l If new faults occur, refer to the fault handling flow and try to rectify them.

Contact Huawei engineers for co-work

If you fail to rectify the fault, contact Huawei technical support engineers and co-work withthem to find a solution. For contact information, see 3.15 Fault Notification and TechnicalSupport.

If remote maintenance is required, refer to 7 Remote Maintenance Guide and work withHuawei engineers for remote access.

Write the fault handling report

After rectifying a fault, record the work done for handling the fault in a timely manner. Whensummarizing the working experience, provide reference information for handling similar faults.

The report should contain the following key information:

l Description of the fault phenomenon and collected fault-related information

l Probable causes of the fault

l Plan and confirmation result for each probable cause

l List of involved equipment and instruments used for confirming the probable causes

l Experience of confirming probable causes

l Others such as the references used during the process

3.2 Emergency Flow of Handling the Service InterruptionFault

If any fault causes service interruption, follow the general fault handling flow and also take otheremergency measures, such as backup trails, to reduce the service interruption time to theminimum.

CAUTIONTake the following precautions when handling the service interruption fault or any otheremergency according to the emergency flow:

l Restore services as soon as possible. If backup channels are available, switch services tothe backup channels.

l Observe the fault phenomenon, find the cause, and rectify the fault.

l When you cannot handle the fault, contact Huawei for technical support and work withHuawei to handle the fault and to minimize the service interruption duration.

l Properly make a record when handling a fault and save the original data.

Flow Diagram

Figure 3-2 shows the flow diagram for handling service interruption.



3-5

Figure 3-2 Flow diagram for handling service interruption

Handle fiber cut/board fault/power supply problem

StartT2000

Any mis-operation?

No

Any equipment alarm on

NE?

Any signal loss alarm?

Any line alarm?

Perform inloop on oppositeport and recheck

alarm

Handle anomaly of interconnected equipment

Any line alarm on adjacent

NE?

Any protection switching

configured?

Change service route or use standby route

Reset/re-insert faulty board, disable protection protocol

Any loopback? Change port loopback configuration

Any service configuration

error

Change service configuration

Fault ratified?

EndContact Huawei for technical support

Perform reverse operation to restore service

Reset/re-insert/replace board

Yes

Reset/re-insert/replace board of the opposite NE

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

Yes

Yes

Yes

No

No

No

No

Check fiber and use standby route


Maintenance Guide


Issue 02 (2009-06-30)

Description of the Emergency Handling Flow

Check for misoperations

Check whether any misoperations are performed before the fault occurs, such as addition ordeletion of services or boards, and configuration change. In the case of any misoperation, performthe reverse operation to restore the services.

Check alarms

When the services are interrupted, check for any of the alarms listed in Table 3-2 and rectifythe fault indicated by the alarm accordingly.

Table 3-2 Alarm description

Alarm Type Alarm Name Indication

Equipment alarm HARD_BAD The board hardware becomesfaulty.

Signal loss alarm ETH_LOS A link breaks.The network interface has nosignals (PHY-layerdetection).The board has no signalinput.

EXT_SYNC_LOS The system detects loss of theexternal clock source tracedby the equipment.

Line alarm PW_DOWN A PW service connection isinterrupted.

NOTE

The alarms listed in Table 3-2 may cause service interruption. Therefore, take priority to handle thesealarms. For details on other alarms reported on the T2000, see 9.3 Alarm Handling.

Check loopback

Check whether any loopback is set along the service route.

Check service configuration

Check the service configuration section by section along the route.

3.3 Troubleshooting Microwave LinksWhen an NE reports MW_LOF or MW_FECUNCOR due to failure or performance degrade ofa microwave link, there is a microwave link fault.



3-7

ContextThe key to locating a microwave 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

NOTE

For a detailed description of the range of the transmit power, refer to the OptiX RTN 950 Radio TransmissionSystem Product Description.

In the following two cases, the RSL is abnormal. The one case is that the receive power is lowerthan the ideal value (Ideal 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

l RSL_MAX

l RSL_MIN

NOTE

For a microwave link on which the AM function is enabled, the receiver sensitivity refers to the receiversensitivity that guarantees the capacity.

For a detailed description of the receiver sensitivity, refer to the OptiX RTN 950 Radio Transmission SystemProduct 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 microwavelink may be faulty in one direction only.


Maintenance Guide


Issue 02 (2009-06-30)

Fault Causes

Table 3-3 Causes of microwave link faults

Fault Common Fault Causes

The transmit power is abnormal. The ODU is faulty.

The receive power is always lower than theideal value.

l The antenna direction is not properlyadjusted.

l The antennas have different polarizationdirections.

l There is a mountain or obstacle in thetransmit direction.

l The antenna is faulty or the antenna and theODU are connected abnormally. Forexample, the waveguide interface on theODU is wet, or the flexible waveguide isloose.

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 always normal, but themicrowave link becomes faulty occasionally.

There is external interference.

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 microwave link may befaulty in both directions.



3-9

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 always normal, but the microwave link becomes faulty occasionally.

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


Maintenance Guide


Issue 02 (2009-06-30)

Fault Locating Procedures

Figure 3-3 Flow of handling microwave link faults

Start

Is there an ODU or IFboard related fault?

YesHandle the alarm

Abnormal receivepower caused by slow

down-fading?

No

Go to the next step Is the fault cleared?

End

Yes

No

Normal transmit power?

Yes

No

2

Handle the fault

Perform loopback operations

No

The receive poweralways lower than the

ideal value?

Handle the fault

YesHandle the fault

Abnormal receivepower caused by slow up-

fading?

No

Handle the fault

3

Is there a wrongoperation? Cancel the operation

1

4

5

6

Yes

No

Yes

Abnormal receivepower caused by fast

fading?

No

Handle the fault

7Yes

Yes

No

Microwave linkfault in onedirection?

No

Handle the faultYes

8

9



3-11

Table 3-4 Flow description

Note Description

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

② Handleequipmentfaults.

Pay special attention to: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

③ Handletheanomalyof transmitpower.

Replace the ODU.


Maintenance Guide


Issue 02 (2009-06-30)

Note Description

④ Handlethe anomalythat thereceivepower issmaller thanthe idealvalue.

Follow the steps below:1. If the RSL decreases dramatically and does not recover, check the

installation of the antenna. Check whether the azimuth angle of the antennameets the requirement.

2. If the RSL difference between the main and standby ODUs on one end ofa 1+1 HSB microwave link exceeds the range 0 to 9 dB (for the unbalancedhybrid coupler) or the range 0 to 5 dB (for the balanced hybrid coupler),determine the faulty part by replacing the ODU or hybrid coupler.

3. If the RSL difference between the receive and transmit ends exceeds 10dB, determine the faulty ODU by replacing the ODU.

4. Check the antenna direction. Check whether the received signal is from themain lobe.If the antenna direction does not meet the requirement, adjust the antennain a wide range.

5. Check whether the setting of the polarization direction of the antenna iscorrect. Adjust wrong polarization direction.

6. Determine the faulty part by replacing the ODU or hybrid coupler.7. Check whether the antenna gain at both the transmit and receive sides meets

the indexes. Replace unqualified antennas.8. Check whether there is a mountain or obstacle in the transmit direction.

⑤ Handlethe up 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.

⑥ Handlethe downslow fadingfault.

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.



3-13

Note Description

⑦ Handlethe fastfading fault.

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.

⑧ Handletheinterferencefault.

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

⑨ Use theloopbackmethod tolocate a fault.

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

If the fault is not cleared after the loopback, replace the IF board.2. Check whether the cable connector is made in accordance with

specifications. If not, make the connector again. For details, refer toQuickly Installation Guide.

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

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


Maintenance Guide


Issue 02 (2009-06-30)

Experience and Summaryl During the hop commissioning, you must well adjust the antenna direction. Hence, the

dormant problems for future maintenance can be avoided.

l You should periodically collect, analyze the change of the transmit power and receivepower, and eliminate the dormant problems in a timely manner.

3.4 CES Service TroubleshootingThis section describes how to troubleshoot interruption or bit errors of the CES service in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

Symptoms

The symptoms of a CES service fault may be as follows. See Table 3-5. Clear up all the reportedalarms and the fault is rectified.

Table 3-5 List of common symptoms of CES service faults

Symptom Alarm Reported Board

The CES service isinterrupted.

HARD_BAD,TEMP_OVER, orBUS_ERR

CXPR, ML1 or ML1A

COMMUN_FAIL CXPR

T_ALOS ML1 or ML1A

UP_E1_AIS orDOWN_E1_AIS

ML1 or ML1A

MPLS_TUNNEL_LOCV CXPR

PW_DOWN

The CES service has biterrors and thecommunication is degraded.


CXPR, ML1 or ML1A

SYNC_C_LOS or LTI CXPR

CES_LOSPKT_EXC,CES_MISORDERPKT_EXC, CES_MALPKT_EXC,CES_STRAYPKT_EXC,CES_JTRUDR_EXC, orCES_JTROVR_EXC

ML1 or ML1A



3-15

Troubleshooting FlowchartFigure 3-4 shows the flowchart for troubleshooting CES service faults.

Figure 3-4 Flowchart for troubleshooting CES service faults

Start

Whether HARD_BAD, TEMP_OVER,

BUS_ERR, or COMMUN_FAIL alarm exists?

Whether T_ALOS, UP_E1AIS, or DN_E1AIS alarm

exists?

Rectify clock fault

Check cable and connections, and handle problems

Whether faultis rectified?

EndContact Huawei technical support engineers


Loop to locate the faulty physical path

Yes

Reset/re-insert/replace cross-connect board

Modify network configuration

Yes

Yes

Yes

No

No

No

No

No

No

Yes

Board is faulty or inter-board communication

fails

Signals are lost

Synchronous clock is lost

Lost packets, errored packets, or jitter

crosses threshold

Whether SYNC_C_LOS or LTI

alarm exists?

WhetherCES_LOSPKT_EXC, CES_JTRUDR_EXC

alarm exists?

Modify/replace the faulty physical path

Whether MPLS_TUNNEL_LOCV

or PW_DOWN alarm exists?

Rectify fault of physical link

Rectify fault of opposite equipment

Yes NoTunnel or PW which carries service is faulty

No

No

Impact on the SystemThe CES service in the network has bit errors or is interrupted. As a result, the communicationis degraded or interrupted. If the CES service fault is caused by the CXPR board, other servicesaccessed by the equipment may also be affected.

Possible CausesAs shown in the troubleshooting flowchart, a CES service fault may be due to the followingcauses:

l Cause 1: The board has a hardware fault or excessively high temperature, or the inter-boardcommunication fails. As a result, the board does not work normally.

l Cause 2: The signals are lost or degraded.

l Cause 3: The tunnel or PW that carries the CES service is interrupted.


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 4: The priority of the synchronous clock source or the synchronous clock sourceitself is lost.

l Cause 5: The number of lost packets or erorred packets, or the jitter buffer of the CESservice over the PW crosses the threshold.

Tools, Instruments, and Materials

T2000, optical power meter, and SDH analyzer or BER tester

Precautions

DANGERAvoid direct eye exposure to laser beams launched from optical interfaces or fiber connectors.Otherwise, the laser beams launched from the optical interfaces or fiber connectors may damagethe eyes.

Procedurel Cause 1: The board has a hardware fault or excessively high temperature, or the inter-board

communication fails. As a result, the board does not work normally.

1. Query the current alarms of the system to check for the HARD_BAD, TEMP_OVER,COMMUN_FAIL, or BUS_ERR alarm and determine which board reports the alarm.For details, refer to 8.2 Querying Current Alarms of a Board.

2. Handle the HARD_BAD, TEMP_OVER, COMMUN_FAIL, or BUS_ERR alarm.

l Cause 2: The signals are lost or degraded.

1. Check for the T_ALOS, UP_E1_AIS, or DOWN_E1_AIS alarm of the system andhandle the T_ALOS, UP_E1_AIS, or DOWN_E1_AIS alarm.

2. Check for the LASER_MOD_ERR, LSR_WILL_DIE, IN_PWR_ABN, TEM_HA,or LSR_BCM_ALM alarm of the system and handle the LASER_MOD_ERR,LSR_WILL_DIE, IN_PWR_ABN, TEM_HA, or LSR_BCM_ALM alarm.

l Cause 3: The tunnel or PW that carries the CES service is interrupted.

1. Check for the MPLS_TUNNEL_LOCV alarm of the system and handle theMPLS_TUNNEL_LOCV alarm.

2. Check for the PW_DOWN alarm of the system and handle the PW_DOWN alarm.

l Cause 4: The priority of the synchronous clock source or the synchronous clock sourceitself is lost.

1. Check whether the SYNC_C_LOS or LTI alarm exits.

2. If yes, handle the SYNC_C_LOS or LTI alarm.

l Cause 5: The number of lost packets or erorred packets, or the jitter buffer of the CESservice over the PW crosses the threshold.

1. Check whether the CES_LOSPKT_EXC or CES_MISORDERPKT_EXC alarmexits. If yes, handle the CES_LOSPKT_EXC or CES_MISORDERPKT_EXCalarm.



3-17

2. Check whether the CES_STRAYPKT_EXC or CES_MALPKT_EXC alarm exits. Ifyes, handle the CES_STRAYPKT_EXC or CES_MALPKT_EXC alarm.

3. Check whether the CES_JTRUDR_EXC or CES_JTROVR_EXC alarm exits. If yes,handle the CES_JTRUDR_EXC or CES_JTROVR_EXC alarm.

----End

3.5 Ethernet Service TroubleshootingThis section describes how to troubleshoot Ethernet service interruption or packet loss in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

SymptomsThe symptoms of Ethernet service faults may be as follows. See Table 3-6. Clear up all thereported alarms and the fault is rectified.

Table 3-6 List of common symptoms of Ethernet service faults


The Ethernet service isinterrupted.


CXPR, AUXQ, EF8T, EF8For EG2

COMMUN_FAIL CXPR

ETH_LOS,ETH_LINK_DOWN,ETH_AUTO_LINK_DOWN, LOOP_ALM, orMAC_FCS_EXC

AUXQ, EF8T, EF8F or EG2

LASER_SHUT orLSR_WILL_DIE

EF8F or EG2

The Ethernet service losespackets or has erorredpackets.


CXPR, AUXQ, EF8T, EF8For EG2

LSR_WILL_DIE EF8F or EG2

MAC_FCS_EXC orFLOW_OVER

AUXQ, EF8T, EF8F or EG2

Troubleshooting FlowchartFigure 3-5 shows the flowchart for troubleshooting Ethernet service faults.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 3-5 Flowchart for troubleshooting Ethernet service faults

Start

Whether HARD_BAD, TEMP_OVER,

BUS_ERR, or COMMUN_FAIL alarm exists?

Whether ETH_LOS or

MAC_FCS_EXC alarm exists?

Whether ETH_LINK_DOWN alarm

exists?

Modify port configuration, including port attributes

and working mode

Whether LOOP_ALM alarm

exists?

Modify port loopback configuration

WhetherFLOW_OVER alarm

exists?

Modify service configuration

Whether fault is rectified?

EndContact Huawei technical support engineers


Check fiber, optical module, and network cable,

and handle problems

Yes


Yes

Yes

Yes

Yes

No

No

No

No

No

No

Yes

Board is faulty or inter-board communication fails

Signals are lost or degraded

Port negotiation fails

Port loopback is set

Service configuration is incorrect

Impact on the System

The Ethernet service in the network is interrupted, loses packets, or has erorred packets. If thefault is caused by the CXPR board, other services accessed by the equipment may also beaffected.

Possible Causes

As shown in the troubleshooting flowchart, an Ethernet service fault may be due to the followingcauses:

l Cause 1: The board has a hardware fault or excessively high temperature, or the inter-boardcommunication fails. As a result, the board does not work normally.

l Cause 2: The signals on the receive side of the Ethernet interface are lost.

l Cause 3: The Ethernet port is misconnected and the port negotiation fails.

l Cause 4: Loopback is configured for the port.

l Cause 5: The configured traffic limit is excessively low at the port and configurations ofthe source and sink ports are inconsistent.



3-19

Tools, Instruments, and MaterialsT2000, optical power meter

Precautions

DANGERAvoid direct eye exposure to laser beams launched from optical interfaces or fiber connectors.Otherwise, the laser beams launched from the optical interfaces or fiber connectors may damagethe eyes.

Procedurel Cause 1: The board has a hardware fault or excessively high temperature, or the inter-board

communication fails. As a result, the board does not work normally.1. Query the current alarms of the system to check for the HARD_BAD, TEMP_OVER,

COMMUN_FAIL, or BUS_ERR alarm and the board that reports the alarm. Fordetails, refer to 8.2 Querying Current Alarms of a Board.

2. Clear the HARD_BAD, TEMP_OVER, COMMUN_FAIL, or BUS_ERR alarm.l Cause 2: The signals on the receive side of the Ethernet interface are lost.

1. Check for the ETH_LOS or ETH_AUTO_LINK_DOWN alarm of the system andclear the ETH_LOS or ETH_AUTO_LINK_DOWN alarm.

2. Check for the LASER_SHUT or LSR_WILL_DIE alarm of the system and clear theLASER_SHUT or LSR_WILL_DIE alarm.

3. Check for the IN_PWR_ABN or OUT_PWR_ABN alarm of the system and clear theIN_PWR_ABN or OUT_PWR_ABN alarm.

4. Check for the MAC_FCS_EXC alarm of the system and clear theMAC_FCS_EXC alarm.

l Cause 3: The Ethernet port is misconnected and the port negotiation fails.1. Check for the ETH_LINK_DOWN alarm of the system and clear the

ETH_LINK_DOWN alarm.l Cause 4: Loopback is configured for the port.

1. Check for the LOOP_ALM alarm of the system and clear the LOOP_ALM alarm.l Cause 5: The configured traffic limit is excessively low at the port and configurations of

the source and sink ports are inconsistent.1. Check for the FLOW_OVER alarm of the system and clear the FLOW_OVER alarm.

l If any problems occur during the troubleshooting, contact Huawei engineers. For thecontact information, see 3.15 Fault Notification and Technical Support.

----End

3.6 Clock TroubleshootingThis section describes how to troubleshoot loss of the clock source and degrade of clock signalsin terms of the symptoms, impact on the system, possible causes, tools required for


Maintenance Guide


Issue 02 (2009-06-30)

troubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

SymptomsThe symptoms of clock faults may be as follows. See Table 3-7. Clear up all the reported alarmsand the fault is rectified.

Table 3-7 List of common symptoms of clock faults


The service has bit errors. SYNC_C_LOS, LTI,S1_SYN_CHANGE,SYN_BAD,EXT_SYNC_LOS, orCLK_NO_TRACE_MODE

CXPR, AUXQ, EF8F, EF8T,EG2, ML1, or ML1A

EXT_TIME_LOC CXPR

Impact on the SystemLoss or quality degrade of a clock source in the network affects the service that traces this clocksource, causes pointer justification, and increases the BER.

Possible CausesA clock fault may be due to the following causes:

l Cause 1: The priority of the synchronous clock source on the service board is absent fromthe priority table.

l Cause 2: The synchronous clock source is lost and the clock of the NE works abnormally.

l Cause 3: The clock source is switched in the SSM mode and thus the clock source tracedby the NE is also switched.

l Cause 4: The signals of the synchronous clock source are degraded.

l Cause 5: The external clock source is lost.

l Cause 6: The clock does not work in the tracing mode.

l Cause 7: The external time source is lost.

Tools, Instruments, and MaterialsT2000, frequency meter, ANT20



3-21

Precautions

WARNINGIf no active and standby CXPR board that are working normally can be used for protection,cold-reset of CXPR board may completely interrupt the services.

Procedurel Cause 1: The priority of the synchronous clock source on the service board is absent from

the priority table.1. Check for the SYNC_C_LOS alarm of the system. For details, refer to 8.2 Querying

Current Alarms of a Board.2. If the SYNC_C_LOS alarm occurs, clear the SYNC_C_LOS alarm.

l Cause 2: The synchronous clock source is lost and the clock of the NE works abnormally.1. Check for the LTI alarm of the system and clear the LTI alarm.

l Cause 3: The clock source is switched in the SSM mode and thus the clock source tracedby the NE is also switched.1. Check for the S1_SYN_CHANGE alarm of the system and clear the

S1_SYN_CHANGE alarm.l Cause 4: The signals of the synchronous clock source are degraded.

1. Check for the SYN_BAD alarm of the system and clear the SYN_BAD alarm.l Cause 5: The external clock source is lost.

1. Check for the EXT_SYNC_LOS alarm of the system and clear theEXT_SYNC_LOS alarm.

l Cause 6: The clock does not work in the tracing mode.1. Check for the CLK_NO_TRACE_MODE alarm of the system and clear the

CLK_NO_TRACE_MODE alarm.l Cause 7: The external time source is lost.

1. Check for the EXT_TIME_LOC alarm of the system and clear theEXT_TIME_LOC alarm.


----End

3.7 QoS TroubleshootingThis section describes the QoS faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

PrerequisiteThe connection of services configured with the QoS policy must be normal.


Maintenance Guide


Issue 02 (2009-06-30)

SymptomsThe symptoms of the QoS faults may be as follows:

l The service is configured with bandwidth, but the actual traffic exceeds the limit. Hence,the traffic is large, and a congestion occurs.

l Different services preempt bandwidth of each other. The packets of the service are lost orbit errors occur in the service whose bandwidth is preempted.

l A service of a lower priority preempts the bandwidth of a service of a higher priority. Inthis case, the packets of the service are lost or bit errors occur in the service of a higherpriority.

Generally, in the case of the QoS faults, the system reports the alarms listed in Table 3-8. If thealarms reported by the equipment are cleared, the faults are rectified.

Table 3-8 List of common symptoms of the QoS faults


The traffic is large, and acongestion occurs.

FLOW_OVER AUXQ, EF8T, EF8F, or EG2

The service bandwidth ispreempted, and the packetsof the service are lost or biterrors occur.

CES_LOSPKT_EXC ML1, or ML1A

CES_JTROVR_EXC

CES_JTRUDR_EXC

Troubleshooting FlowchartFigure 3-6 shows the flowchart for troubleshooting the QoS faults.



3-23

Figure 3-6 Flowchart for troubleshooting the QoS faults

Whether fault is rectified?

EndContact Huawei technical engineers

No

Yes

Increase the configured bandwidth for the tunnel or PW

Yes

The traffic crosses the threshold or the service bandwidth is

insufficient

No

YesCheck whether the bandwidth of the tunnel or PW can

be increased

Clear the hardware alarms

Yes

Yes

No

Check whether the Qos policy

is configured

Reconfigure the port policy or PW policy

Check whether the hardware

alarms exist on the board

Check whether the alarms

listed in the preceding table exist

Check whether the Qos policy

for the service is correct

Reconfigure the service parameters

Yes

No

Start


If the service processing capability of the board is restricted, part of the services may not beprocessed, and the packets of the service are lost or bit errors occur.

Possible Causes

As shown in the troubleshooting flowchart, the QoS faults may be due to the following causes:

l Cause 1: The NE is not configured with the QoS policy.

l Cause 2: During the service configuration, an incorrect QoS policy is selected.

l Cause 3: The bandwidth configured in the tunnel or PW is small.

l Cause 4: The board is faulty, and the configuration data is not delivered to the board.


T2000 and BER tester


Maintenance Guide


Issue 02 (2009-06-30)

Procedurel Cause 1: The NE is not configured with the QoS policy.

1. Check whether the NE is configured with the related QoS policy such as the WREDpolicy, WFQ scheduling policy, port policy, CAR policy, V-UNI Ingress policy, orATM policy.

2. If the NE is not configured with the related QoS policy, configure the missing QoSpolicy. For details, see QoS-Related Operation Tasks in the Feature Descriptionmanual.

l Cause 2: During the service configuration, an incorrect QoS policy is selected.

1. Check whether the QoS policy that is currently configured is applicable. If it is notapplicable, configure a new policy. For details, see the Configuration Guide manual.

l Cause 3: The bandwidth configured in the tunnel or PW is small.

1. Check whether the bandwidth that is currently configured in the tunnel or PW meetsthe requirement for the traffic. If the configured bandwidth is excessively small,reconfigure the bandwidth. For details, see the Configuration Guide manual.

l Cause 4: The board is faulty, and the configuration data is not delivered to the board.

1. Check whether a hardware alarm such as HARD_BAD exists in the system. If thealarm exists, clear the HARD_BAD alarm.

2. Check whether the laser alarm such as LSR_WILL_DIE exists in the system. If thealarm exists, clear the LSR_WILL_DIE alarm.


----End

3.8 Inband DCN TroubleshootingThis section describes the inband DCN faults in terms of the symptoms, impact on the system,possible causes, tools required for troubleshooting, troubleshooting procedure, and precautionsthat should be taken during the troubleshooting.

PrerequisiteYou must ensure that each board on the NE is of the mapping version by checking the engineeringdocument.

Symptoms

The symptoms of the inband DCN faults may be as follows:

l The communication between the T2000 and the NE is interrupted. The NE icon on theT2000 is grey, and the NE is unreachable to the T2000.

l The operations on the T2000 are not responded. If the response interruption time lasts formore than two minutes, the communication between the T2000 and the NE is interrupted.

l When you query certain information on the T2000, the query result contains incompleteinformation.



3-25

Troubleshooting FlowchartFigure 3-7 shows the flowchart for troubleshooting the inband DCN faults.

Figure 3-7 Flowchart for troubleshooting the inband DCN faults

Start

Whether the NE icon turns

grey

Whether faultis rectified


No

Yes

The system control board is restting

The communication between the T2000 and

the NE is interrupted

Yes

Enablethe DCN port

No

Whetherthe T2000 query

information is lost

Whether the T2000 operation

command is not responded

Whetherthe physical connection is interrupted

Reconnect the network cable or

optical fiber

Whetherthe DCN port is

disabled

Whetherthe receive signals

are lost

Yes

No

No

Whether the board is

faultyReplace the board

No

Handle the alarms related to the optical power, fibers, and

cables

The bandwidth configured for the DCN

tunnel is too small

Yes

Yes

No

Yes

Yes

Yes

Increase the bandwidth configured for the inband

DCN tunnel

Wait until the reset of the system control

board is complete

Impact on the Systeml When the NE fails to communicate with the T2000, other NEs that communicate with the

T2000 through this NE become unreachable to the T2000, if they cannot be connected tothe T2000 in other manners. The other NEs are not affected.

l If the physical channel that carries the inband DCN is faulty, the other services carried inthis physical channel are affected.

Possible CausesAs shown in the troubleshooting flowchart, the inband DCN faults may be due to the followingcauses:


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 1: The physical connection between the faulty NE and the T2000 is interrupted.

l Cause 2: The inband DCN port of the faulty NE is not enabled.

l Cause 3: The received signals of the faulty NE are lost, or the received optical power isexcessively low, and thus the DCN packets cannot be extracted.

l Cause 4: The board is faulty.

l Cause 5: The bandwidth configured for the inband DCN channel is excessively small.

l Cause 6: The board on the faulty NE is being reset or the active/standby switching of boardsis performed, and thus the inband DCN packets cannot be responded.


T2000

Precautions

CAUTIONBefore locating the faults, you should check whether each board on the NE is of the mappingversion. If a board is not of the mapping version, replace the board in time.

NOTE

When handling the inband DCN faults, perform the following operations:

l If the NE communication is interrupted, you should handle the faults of the gateway NE, and thenhandle the faults of the non-gateway NEs.

l If the NE communication is not interrupted, handle the faults of the non-gateway NEs first, and thenhandle the faults of the gateway NE. Hence, the non-gateway NEs are prevented from being unreachableto the T2000.

Procedurel Cause 1: The physical connection between the faulty NE and the T2000 is interrupted.

1. Check whether the network cables or fibers of the faulty NE are disconnected fromthe ports. If the network cables or fibers are disconnected from the ports, insert thenetwork cables or fibers again.

l Cause 2: The inband DCN port of the faulty NE is not enabled.

1. Check whether the ports, which support the DCN function by default, are connectedwith the fibers or cables. If not, change the present port to a port whose DCN functionis enabled by default. Availability provides the information about the ports of OptiXRTN 950 whose DCN function is enabled by default.

2. Check whether the ports at the two ends of the link are enabled. If not, enable theinband DCN port. For details, see Enabling the Port DCN in the FeatureDescription manual.

l Cause 3: The received signals of the faulty NE are lost, or the received optical power isexcessively low, and thus the DCN packets cannot be extracted.



3-27

1. Check whether the ETH_LOS, or IN_PWR_ABN alarm exists on the boardconfigured with the inband DCN channel. For details, see 8.2 Querying CurrentAlarms of a Board. Clear these alarms.

l Cause 4: The board is faulty.1. Check whether the HARD_BAD alarm exists on the board configured with the inband

DCN channel.2. If the alarm exists, replace the board that reports the alarm. For details, see 5 Replacing

Components.l Cause 5: The bandwidth configured for the inband DCN channel is excessively small.

1. When the number of services configured on the port exceeds a certain number, partof the query information may be lost. In this case, you should properly increase thebandwidth configured for the inband DCN channel. For details, see Setting the VLANID and Bandwidth Used by an Inband DCN in the Feature Description manual.

l Cause 6: The board on the faulty NE is being reset or the active/standby switching isperformed, the inband DCN packets cannot be responded.1. Observe whether the PROG indicator on the system control board is blinking in green.

If the indicator is blinking in green, it indicates that the system control board is in thereset state. After the PROG indicator is always on in green, the reset of the systemcontrol board is complete and the DCN connection is automatically recovered.

NOTE

If the active/standby switching occurs on the system control board, a warm reset is performedon Active Board.

2. If the DCN response does not recover, check whether the protection switching occurson other boards. If other boards are switched, the inband DCN packets are in thererouting state. For details, see 8.23 Querying Protection Configuration.

3. If the protection switching occurs on the boards, after the DCN rerouting is complete,the response is automatically recovered.


----End

3.9 LAG TroubleshootingThis section describes the LAG faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

SymptomsThe symptoms of the LAG faults may be as follows. See Table 3-9. If the alarms reported bythe equipment are cleared, the faults are rectified.


Maintenance Guide


Issue 02 (2009-06-30)

Table 3-9 List of common symptoms of the LAG faults


The LAG is invalid, all themember ports cannot be used,and the services areinterrupted.

LAG_DOWN CXPR

The member ports in theLAG cannot be used, and thepacket of the service are lost.

LAG_MEMBER_DOWN CXPR

LOOP_ALM AUXQ, EF8T, EF8F, or EG2

ETH_LOS

ETH_LINK_DOWN

Troubleshooting FlowchartFigure 3-8 shows the flowchart for troubleshooting the LAG faults.



3-29

Figure 3-8 Troubleshooting Flowchart

Whetherthe LAG_DOWN

alarm exists



No

Yes

YesWhetherthe service is interrupted

Start

The link aggregation group is invalid

Yes

The link aggregation group member port

is invalid

Modify the LAG configurations at the two ends of the NE

Yes

Yes

Modify the working mode of the port to

full-duplex

Rectify the port connection fault,

and clear the related alarms

No

Whetherthe packet loss occurs

in the service

Whether the LAG_MEMBER_DOWN

alarm exists

WhetherLAG configurationsat the two ends are

incorrect

Whetherthe working mode

of the port ishalf-duplex

No

Release the port loopback status

Whetherthe ETH_LOS or

ETH_LINK_DOWN alarm exists

No

No

Yes

Yes

Yes

Yes

Whether theLoopback-related

alarm exists

Impact on the Systeml If the LAG is invalid, the service carried by the LAG is interrupted, but the services carried

by other channels are not affected.l If the members in the LAG are invalid, in the load sharing mode, consistent packet loss

may occur because of insufficient bandwidth. If the LAG is in the non-load sharing mode,the switching occurs in the link and the packets of the service are lost for a short time.

Possible CausesAs shown in the troubleshooting flowchart, the LAG faults may be due to the following causes:

l Cause 1: The NEs at the two ends of the LAG are incorrectly configured.

l Cause 2: The working mode of the member ports in the LAG is set to half-duplex.


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 3: The loopback is configured on the member ports in the LAG.

l Cause 4: The connection of the member ports in the LAG are improperly connected ordisconnected.


T2000

Procedurel Cause 1: The NEs at the two ends of the LAG are incorrectly configured.

1. 8.2 Querying Current Alarms of a Board, and check whether the LAG_DOWN orLAG_MEMBER_DOWN alarm exists.

2. Check whether the configurations of the NEs at the two ends of the LAG are consistent.If the configurations are inconsistent, modify the configuration as the same, and thencheck whether the alarm is cleared. For details, see Creating an LAG in the FeatureDescription manual.

l Cause 2: The working mode of the member ports in the LAG is set to half-duplex.

1. Check whether the working mode of each member port in the LAG is set to half-duplex. If the working mode is set to half-duplex, modify the working mode of theport to full-duplex. For details, see 8.22 Querying and Setting the Working Modeof Ethernet Interface.

l Cause 3: The loopback is configured on the member ports in the LAG.

1. Check whether the LOOP_ALM alarm exists on each member port in the LAG group.If yes, reconfigure the loopback status of the port to clear the LOOP_ALM alarm.For details, see 8.9 Configuring Port Loopback.

l Cause 4: The connection of the member ports in the LAG are improperly connected ordisconnected.

1. Check whether the ETH_LOS or ETH_LINK_DOWN alarm exists on each memberport in the LAG.

2. If the alarm exists, clear the ETH_LOS or ETH_LINK_DOWN alarm.


----End

3.10 ML-PPP TroubleshootingThis section describes the ML-PPP faults such as service interruption, packet loss, or bit errorin terms of the symptoms, impact on the system, possible causes, tools required fortroubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

Symptoms

The symptoms of the ML-PPP faults may be as follows. See Table 3-10. If the alarms reportedby the equipment are cleared, the faults are rectified.



3-31

Table 3-10 List of common symptoms of the ML-PPP faults


The MP group is invalid, andthe service is interrupted.

MP_DOWN ML1, or ML1A

The MP group member isinvalid, and the packets of theservice are lost.

PPP_LCP_FAIL orPPP_NCP_FAIL

ML1, or ML1A

T_ALOS

The MP group member isdelayed, and the packets ofthe service are lost.

MP_DELAY ML1, or ML1A

Troubleshooting FlowchartFigure 3-9 shows the flowchart for troubleshooting the ML-PPP faults.

Figure 3-9 Flowchart for troubleshooting the ML-PPP faults

Whether the MP_DOWN alarm

exists

No



No

Yes

Yes Replace the cable or board

No

Yes

Modify the configuration of the MP group, or restart the ML-PPP protocol

Whetherthe PPP_LCP_FAILor PPP_NCP_FAIL

alarm exists

Whetherthe service is interrupted

Start

The MP group is invalid

Yes

The configurations at the two ends of the MP group member

are inconsistent

Modify the configuration of the MP group member

port

The signals at the interface are lost

Check and then rectify the cable fault Replace the board

NoWhetherthe T_ALOS alarm

exists

Yes

Yes

No

No

Whetherthe packet loss occurs in the

service

Whetherthe MP_DELAY alarm

exists

YesThe delay of the MP

group member exceeds the

threshold

Increase the maximum reserved

bandwidth for the MP group

Replace the cable or board

No

No

Impact on the Systeml If the MP group is invalid, the carried service is interrupted, but the services carried by

other channels are not affected.


Maintenance Guide


Issue 02 (2009-06-30)

l If the MP group member is invalid, the bandwidth of this MP group is decreased, and thusthe packets of the service may lost.

Possible CausesAs shown in the troubleshooting flowchart, the ML-PPP fault may be due to the following causes:

l Cause 1: The MP group is invalid.

l Cause 2: The negotiation of the protocols at the two ends of the MP group member fails.

l Cause 3: The received signals of the MP group member port are lost.

l Cause 4: The MP group member delay exceeds the threshold.


Procedurel Cause 1: The MP group is invalid.

1. 8.2 Querying Current Alarms of a Board, and check whether the MP_DOWN alarmexists.

2. If yes, clear the MP_DOWN alarm.l Cause 2: The negotiation of the protocols at the two ends of the MP group member fails.

1. Check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm exists in any memberof the MP group.

2. If yes, modify the configurations at the two ends of the MP group member to clear thePPP_LCP_FAIL or PPP_NCP_FAIL alarm.

l Cause 3: The received signals of the MP group member port are lost.1. Check whether the T_ALOS alarm exists in any member of the MP group.2. If yes, clear the T_ALOS alarm.

l Cause 4: The MP group member delay exceeds the threshold.1. Check whether the MP_DELAY alarm exists in the MP group.2. If yes, clear the MP_DELAY alarm.


----End

3.11 IMA TroubleshootingThis section describes the IMA faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

SymptomsTable 3-11 lists the symptoms of the IMA faults. If the alarms reported by the equipment arecleared, the faults are rectified.



3-33

Table 3-11 List of common symptoms of the IMA faults


The IMA group is invalid,and the service is interrupted.

IMA_GROUP_LE_DOWN ML1, or ML1A

IMA_GROUP_RE_DOWN

One IMA group member linkis invalid, and the service onthe faulty link is shared byother member links. TheIMA port is congested, andthe packets of the service arelost.

ALM_IMA_LIF ML1, or ML1A

ALM_IMA_RFI

ALM_IMA_LODS

ALM_IMA_RE_RX_UNUSABLE

ALM_IMA_RE_TX_UNUSABLE

Troubleshooting FlowchartFigure 3-10 shows the flowchart for troubleshooting the IMA faults.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 3-10 Flowchart for troubleshooting the IMA faults

Start

WhetherIMA_GROUP_LE_

DOWN or IMA_GROUP_RE_DOWN alarm

exists



No

Yes

The IMA group is invalid

Yes

No

Yes

Modify the configuration of the interface attribute

No

The IMA group member link is

invalid

Yes

YesWhether theinterface attribute is

incorrectlyconfigured

Clear the hardware alarm

Clear the service alarm on the IMA link

Yes

Yes

Yes

No

No

No

whether ALM_IMA_LIF, ALM

_IMA_LODS, or ALM_IMA_RE_RX_UNUSABLE

alarm exists

Whetherthe negotiation of the two ends of the IMA

group fails

Whetherthe IMA protocols at

the two ends are disabled

Modify the configurations at the

two ends to the same, and enable the IMA

protocol again

Enable the IMA protocol at the two

ends

Whetherthe hardware

alarm exists on theboard

Whetherthe service alarm

exists in theIMA link

Impact on the Systeml If the IMA group is invalid, the carried service is interrupted, but the services carried by

other channels are not affected.

l If an IMA member link is invalid, the service is shared by the other member links. Whenthe number of valid links of an IMA group is smaller than the minimum number of activatedlinks configured for the IMA group, the IMA group is invalid.

Possible Causes

As shown in the troubleshooting flowchart, the IMA faults may be due to the following causes:

l Cause 1: The protocols at the two ends of the IMA group are not enabled.

l Cause 2: The negotiation of the two ends of the IMA group fail.

l Cause 3: The interface attribute of the IMA member link is incorrectly configured.



3-35

l Cause 4: Hardware faults exist on the board, and the IMA group members are invalid.

l Cause 5: Other service alarms exist in the IMA link.


Procedurel Cause 1: The protocols at the two ends of the IMA group are not enabled.

1. 8.2 Querying Current Alarms of a Board, and check whether theIMA_GROUP_LE_DOWN or IMA_GROUP_RE_DOWN alarm exists.

2. Enable the protocol status at the two ends of the IMA group again. For details, seeConfiguring Attributes of an ATM IMA Group in the Feature Description manual.

3. Check whether the ALM_IMA_LIF, ALM_IMA_RFI,ALM_IMA_RE_RX_UNUSABLE, ALM_IMA_RE_TX_UNUSABLE, orALM_IMA_LODS alarm exists in the IMA group member link. If the alarm exists,the IMA member links are invalid. In this case, clear the ALM_IMA_LIF,ALM_IMA_RFI, ALM_IMA_RE_RX_UNUSABLE,ALM_IMA_RE_TX_UNUSABLE, or ALM_IMA_LODS alarm.

l Cause 2: The negotiation of the two ends of the IMA group fail.1. Check whether the configurations at the two ends of the IMA group are consistent. If

the configurations are inconsistent, reconfigure the parameters for the IMA group, andenable the IMA protocol. For details, see Configuring Attributes of an ATM IMAGroup in the Feature Description manual.

l Cause 3: The interface attribute of the IMA member link is incorrectly configured.1. Check whether the interface attribute of the IMA group is correctly configured. If the

interface attribute of the IMA group is incorrectly configured, reconfigure the attributeof each interface, and enable the IMA protocol again. For details, see ConfiguringATM Interface Attributes in the Feature Description manual.

l Cause 4: Hardware faults exist on the board, and the IMA group members are invalid.1. Check whether a hardware alarm such as HARD_BAD, COMMUN_FAIL, or

TEMP_OVER exists in the system. If the alarm exists, clear the HARD_BAD,COMMUN_FAIL, or TEMP_OVER alarm.

2. Check whether the laser alarm such as IN_PWR_ABN, LSR_BCM_ALM, orTEM_HA exists in the system. If the alarm exists, clear the IN_PWR_ABN,LSR_BCM_ALM, or TEM_HA alarm.

l Cause 5: Other service alarms exist in the IMA link.1. Check whether the T_ALOS alarm exists in the system. If the alarm exists, clear the

T_ALOS alarm.l If any problems occur during the troubleshooting, contact Huawei engineers. For the

contact information, see 3.15 Fault Notification and Technical Support.

----End


Maintenance Guide


Issue 02 (2009-06-30)

3.12 FRR TroubleshootingThis section describes the FRR faults in terms of the symptoms, impact on the system, possiblecauses, tools required for troubleshooting, troubleshooting procedure, and precautions thatshould be taken during the troubleshooting.

SymptomsThe symptoms of the FRR faults may be as follows:

l The FRR switching fails, and the service is interrupted.

l The FRR switching time or overall restoration time exceeds 50 ms, jitter occurs in theservice.

l After the FRR switching is performed, the bandwidth configured for the bypass tunnel issmaller than the bandwidth configured for the protected tunnel. Hence, part of the packetsof the service are lost or bit errors occur.

Troubleshooting FlowchartFigure 3-11 shows the flowchart for troubleshooting the FRR faults.



3-37

Figure 3-11 Flowchart for troubleshooting the FRR faults

Start

Whetherthe service is interrupted



No

Yes

The FRR switching fails

Yes

Configure the FRR protection for the protected tunnel

No

Whetherthe jitter or bit error

occurs in theservice

Yes

No

No

Rectify theinter-board

communication fault

No

Rectify the board fault

The FRR switching time exceeds the threshold or

the bandwidth for the bypass tunnel is small

Yes

Yes

Yes

Yes

Increase the configured FRR bandwidth or create a

new Bypass Tunnel

Whether theprotected tunnel is not configured with FRR

protection

Whetherother normal usable

tunnels exist

Adjust the service to the normal tunnel

Whetherthe hardware

fault exists on theboard

Whetherthe inter-board communication

is faulty

Whetherthe bypass tunnel

is incorrectlyconfigured

Modify the configuration

parameters for the bypass tunnel

No

Yes


When the FRR switching is invalid, the service cannot be protected. In this case, if the protectedtunnel is faulty, the service is interrupted.

Possible Causes

As shown in the troubleshooting flowchart, the FRR faults may be due to the following causes:

l Cause 1: The protected tunnel is not configured with the FRR protection.

l Cause 2: The FRR switching cannot be performed, because the bypass tunnel is incorrectlyconfigured.


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 3: The board is faulty, and thus the FRR switching command cannot be delivered,or errors occur when the FRR switching command is responded.

l Cause 4: The inter-board communication is faulty, and thus the board cannot receive theswitching command issued by the system control board.

l Cause 5: In the FRR protection group, the bandwidth configured in the tunnel is small, andthus the transmission time of the FRR command times out or part of the packets arediscarded when the link is congested.


T2000

Precautions

When the service is interrupted in the case of the FRR failure, you should switch the service toa normal tunnel. After making sure that the service is restored, you can locate and then rectifythe faults.

Procedurel Cause 1: The protected tunnel is not configured with the FRR protection.

1. Check whether the protected tunnel is configured with the FRR protection. If theprotected tunnel is not configured with the FRR protection, you should reconfigurethe FRR protection. For details, see Creating the FRR Protection for MPLS Tunnelsin the Configuration Guide manual.

l Cause 2: The FRR switching cannot be performed, because the bypass tunnel is incorrectlyconfigured.

1. Check whether the configured parameters for the bypass tunnel are correct. If theparameters are incorrect, you should reconfigure the parameters for the bypass tunnel.For details, see Creating the FRR Protection for MPLS Tunnels in the ConfigurationGuide manual.

l Cause 3: The board is faulty, and thus the FRR switching command cannot be delivered,or errors occur when the FRR switching command is responded.

1. Check whether a hardware alarm such as HARD_BAD exists on the board. If thealarm exists, clear the HARD_BAD alarm, and then check whether the service isrestored.

l Cause 4: The inter-board communication is faulty, and thus the board cannot receive theswitching command issued by the system control board.

1. Check whether the COMMUN_FAIL alarm exists on the board. If the alarm exists,you should clear the COMMUN_FAIL alarm, and then check whether the service isrestored.

l Cause 5: In the FRR protection group, the bandwidth configured in the tunnel is smaller,and thus the transmission time of the FRR command times out or part of the packets arediscarded when the link is congested.

1. Properly increase the configured FRR bandwidth or create a new Bypass Tunnel. Fordetails, see Creating the FRR Protection for MPLS Tunnels in the ConfigurationGuide manual.



3-39


----End

3.13 MPLS APS TroubleshootingThis section describes the MPLS APS faults in terms of the symptoms, impact on the system,possible causes, tools required for troubleshooting, troubleshooting procedure, and precautionsthat should be taken during the troubleshooting.

SymptomsTable 3-12 lists the symptoms of the MPLS APS faults. If the alarms reported by the equipmentare cleared, the faults are rectified.

Table 3-12 List of common symptoms of the MPLS APS faults


The APS protection group isincorrectly configured, or theAPS frame cannot bereceived. In this case, theprotection fails.

ETH_APS_PATH_MISMATCH

CXPR

ETH_APS_LOST

ETH_APS_SWITCH_FAIL

ETH_APS_TYPE_MISMATCH

When the working tunnel orbypass tunnel is faulty, theswitching fails.

MPLS_TUNNEL_LOCV

MPLS_TUNNEL_MISMERGE

MPLS_TUNNEL_MISMATCH

MPLS_TUNNEL_Excess

MPLS_TUNNEL_SD

MPLS_TUNNEL_SF

MPLS_TUNNEL_UNKNOWN

Troubleshooting FlowchartFigure 3-12 shows the flowchart for troubleshooting the MPLS APS faults.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 3-12 Flowchart for troubleshooting the MPLS APS faults

Start

WhetherETH_APS_PATH_MISMATCH alarm

exists


End Contact Huawei engineers

No

Yes

The working and protection trails of

the APS are inconsistent

Yes

Reconnect the fibers or cables No

WhetherETH_APS_LOST

alarm exists

Whether theconfigurations of the twoends on the T2000 are

inconsistent

Modify the configurations, and make sure that the

working and protection trails are consistent

Yes

No

Activate the protocol status at the two

ends of the protection group

Yes

Modify the configurations, and make sure that the

working and protection trails are consistent

The APS frame of the bypass tunnel is

lost

Yes

No

No

Whetherthe fibers or cables

are incorrectlyconnected

Whetherthe protocol status of

the protection group isactivated

Whether the hardware alarmsuch as HARD_BAD

exists

Rectify the board hardware fault

Whetherthe clock alarm such as

TR_LOC exists

Rectify theclock fault

Whetherthe tunnel-level alarmexists in the bypass

tunnel

Rectify the fault of the bypass tunnel

Yes

Yes

Yes

Yes

Yes

No

No

Whether theconfigurations of the twoends on the T2000 are

consistent

Impact on the SystemWhen the APS protection group is invalid, the service cannot be protected. If the protected tunnelis faulty, the service is interrupted.

Possible CausesAs shown in the troubleshooting flowchart, the MPLS APS faults may be due to the followingcauses:

l Cause 1: The configurations at the two ends of the APS protection group are inconsistent.

l Cause 2: The protocols at the two ends of the APS protection group are in the inactive state.

l Cause 3: The optical fibers or cables are incorrectly connected.



3-41

l Cause 4: A hardware alarm exists on the board where the bypass tunnel resides, and thusthe APS frame cannot be transmitted.

l Cause 5: The clock alarms exist in the system.l Cause 6: The working tunnel or bypass tunnel is faulty.


Procedurel Cause 1: The configurations at the two ends of the APS protection group are inconsistent.

1. 8.2 Querying Current Alarms of a Board, and check whether alarms such asETH_APS_PATH_MISMATCH or ETH_APS_TYPE_MISMATCH exists.

2. If yes, clear the ETH_APS_PATH_MISMATCH orETH_APS_TYPE_MISMATCH alarm.

l Cause 2: The protocols at the two ends of the APS protection group are in the inactive state.1. Check whether the ETH_APS_LOST or ETH_APS_SWITCH_FAIL alarm exists in

the APS protection group.2. If yes, clear the ETH_APS_LOST or ETH_APS_SWITCH_FAIL alarm.

l Cause 3: The optical fibers or cables are incorrectly connected.1. Check whether the optical fibers or cables are correctly connected.2. If not, correct the fiber or cable connection.

l Cause 4: A hardware alarm exists on the board where the bypass tunnel resides, and thusthe APS frame cannot be transmitted.1. Check whether a hardware alarm such as the HARD_BAD, COMMUN_FAIL, or

BUS_ERR exists on the board where the APS bypass tunnel resides. If the alarm exists,clear the HARD_BAD, COMMUN_FAIL, or BUS_ERR alarm, and then checkwhether the switching can be normally performed in the APS protection group.

l Cause 5: The clock alarms exist in the system.1. Check whether the clock alarm such as TR_LOC, SYNC_C_LOS, or LTI exists in

the system.2. If yes, clear the TR_LOC, SYNC_C_LOS, or LTI alarm, and then check whether

the switching can be normally performed in the APS protection group.l Cause 6: The bypass tunnel is faulty.

1. Check whether any tunnel-level alarms listed in Table 3-12 exist in the working tunnelor bypass tunnel. If an alarm exist, it indicates that the protection capability of the verytunnel fails. In this case, clear the alarm, and then check whether the switching can benormally performed in the APS protection group.


----End

3.14 Information Collection and Information RecordCollect information and record the information in a timely manner for locating and rectifyingthe fault quickly.


Maintenance Guide


Issue 02 (2009-06-30)

When handling a fault, the maintenance personnel should record the fault phenomena, alarms,performance events, and detailed handling process. The recorded information is helpful foraccurately locating the fault, and handling the fault accordingly. In this way, the faults cannotpersist in the network and lead to further problems in the operation stability of the network.

3.15 Fault Notification and Technical SupportDuring troubleshooting, you can inform Huawei of the faults and apply for technical support, ifnecessary.

Contact Huawei Customer Service Center and notify the fault in the case of any difficulty inlocating or solving a problem.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang, Shenzhen, People's Republic of China

Zip code: 518129

Website: http://www.huawei.com/

Huawei Customer Service Center 24-hour hot line: 400-830-2118, 86-755-28560000

Huawei Customer Service Center fax: 86-755-28560111

Huawei Customer Service Center e-mail address: [email protected]

In the case of any serious accident on equipment, contact Huawei by phone or fax for technicalsupport.

If any replaced equipment component is returned to Huawei for repair, apply for a sparecomponent according to the service contract.

NOTE

The latest technical documents are available on the support website, which may help to analyze and solveproblems.

Website: http://support.huawei.com/



3-43

4 Data Backup and Restoration

About This Chapter

You can back up the T2000 data and the NE data in time so that the data can be quickly restoredafter it is damaged and the data security can be ensured. This chapter describes several methodsto back up and restore data. You can select these methods as needed.

4.1 Backing Up and Restoring the T2000 DataBack up the T2000 data in time for quick data restoration when the T2000 data is damaged.

4.2 Backing Up and Restoring the NE DataTo ensure security of the NE data, back up and restore the NE data in a timely manner.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 4 Data Backup and Restoration


4-1

4.1 Backing Up and Restoring the T2000 DataBack up the T2000 data in time for quick data restoration when the T2000 data is damaged.

4.1.1 Methods of Backing Up and Restoring the T2000 DataTo maintain the data stored on the T2000, you can back up and restore the managed object (MO)data, all data in the databases, or script-based network configuration data.

4.1.2 Backing Up the T2000 MO DataWhen the system becomes faulty, you can quickly restore the system data from the backed upMO data. This section describes how to back up the MO data of the T2000.

4.1.3 Backing Up All Data in the T2000 DatabaseThis section describes how to use the database management tool to immediately back up theT2000 database to the local server, and thus to quickly restore the data when the database isfaulty.

4.1.4 Backing Up the T2000 Network Configuration Data by Means of ScriptsBefore upgrading the T2000, export the data stored in the T2000 databases and save the data asa script file.

4.1.5 Restoring the MO Data of the T2000This section describes how to restore the MO data of the T2000.

4.1.6 Restoring All Data of the T2000 DatabasesThis section describes how to restore the data stored in the T2000 databases backed up beforeby using the database management tool.

4.1.7 Restoring the T2000 Network Configuration Data by Means of ScriptsWhen upgrade of the T2000 software is complete, restore the network configuration data fromthe backup script files.

4.1.1 Methods of Backing Up and Restoring the T2000 DataTo maintain the data stored on the T2000, you can back up and restore the managed object (MO)data, all data in the databases, or script-based network configuration data.

Backing Up and Restoring the T2000 MO DataTo back up the T2000 MO data, directly duplicate every database table in the MO structure ofthe T2000 databases to an OS file by using the scripts compiled by Huawei. The data for backupis the same for the MO backup and database backup, and covers the customization on the T2000,network-layer trail, NE configuration, alarms and performance events. Backup of the T2000MO data only involves the data listed in tables instead of the table structure, storage process,trigger, user name, and authority.

NOTE

Backup of the T2000 MO data excludes the following data:

l Data not stored on NEs, that is, data not uploaded

l User preferences of the system

4 Data Backup and RestorationOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

Backing up and Restoring All Data in the T2000 DatabasesThe T2000, when initially installed, automatically creates five databases, that is, the T2000databases.

l T2000DB, which stores the core data of the server, including all MO data and static data.This database can be accessed using the Ems Server process.

l iMapAlarmDB, which stores alarm data, including data about current and history alarms.This database can be accessed using the Ems Server process.

l iMapTopoDB, which stores topology data in the T2000 client. This database can beaccessed using the Topo Server process.

l iMapLogDB, which stores operation logs.

l iMapSecurityDB, which stores security data. This database can be accessed using theSecurity Server process.

To back up the T2000 databases is to save these five databases as OS files. The data for backupcovers customization on the T2000, network-layer trail, NE configuration, alarms, andperformance events. In addition, the complete database structure, tables in the databases (systemtable and user table), table structure, and storage process are also backed up.

NOTE

Backup of the T2000 databases excludes the following data:

l Data not stored on NEs, that is, data not uploaded

l User preferences of the system

Backing Up and Restoring Script-Based T2000 Network Configuration DataExport the data stored in the database as script files. Export or import the script files to back upor restore the T2000 network configuration data. The script files are basic data for script importand export. When the T2000 is upgraded, importing and exporting scripts is one way to achievesmooth upgrade of the configuration data. Table 4-1 lists the types of script files supported bythe T2000 and data contained in each script file.



4-3

Table 4-1 Script files supported by the T2000

Script FileType

File NamingRule

Data Importable/Exportable orNot

Networkwideconfiguration file

None Is a collection of script files,which include the T2000naming file, NE configurationfile, NE list file, and network-layer information file. Whenyou export the networkconfiguration file, these scriptfiles are all exported. Toimport the networkwideconfiguration file is to importthe NE configuration file andT2000 naming file in sequenceaccording to the NEscontained in the NE list file,and then to import thenetwork-layer informationfile.

Yes

NE port namingfile

NEPort_extendedID-basic ID_NEname.txt

Contains the naminginformation of ports on the NE.

Yes

NE configurationfile

NEData_extended ID-basic ID_NEname.txt

Is similar to the configurationinformation for the commandlines and contains all the dataused for setup and normaloperation of an NE. The datacovers the NE attributes,service configuration, clockattributes, board parameters,protection attributes, boardversion information, and boardmanufacturing information.

Yes

NE list file NWNeList_NMname.txt

Contains information aboutthe NEs, T2000 version,chassis, and physical IPaddresses. The T2000 namingfile and NE configuration fileare imported or exported insequence for NEs listed in thisfile.

Yes


Maintenance Guide


Issue 02 (2009-06-30)

Script FileType

File NamingRule

Data Importable/Exportable orNot

NMS computerinformation file

NMInfo_NMname.txt

Contains the configurationinformation of the T2000server, including the hardwareinformation, such as the OSname and version, OS patchversion, physical memory,CPU quantity and mainfrequency, computer name, IPaddress, database name andversion.

Exportable, butnot importable

Serviceconfiguration file

NWScvcData_NM name.txt

Contains data scripts for thesystem to provide transportservices. This file covers theNE attributes, slot layout,board protection, protectionrelation, service configuration,protection subnet, and circuitconfiguration.

Exportable, butnot importable

Network-layerinformation file

NWCfg_NMname.txt

Contains network-layerconfiguration information,covering the fiber/cableconnections, protectionsubnets, and circuitconfiguration.

Yes

Networksimulationplanninginformation file

None Contains the configurationinformation about networksimulation planning.

Yes

Comparison Among the Three Methods of Maintaining the T2000 DataThe features of the three methods of maintaining the T2000 data decide the application scenarios.Table 4-2 lists the comparison among the three methods.



4-5

Table 4-2 Features and application scenarios of the three methods of maintaining data

Method Backup Feature ApplicationScenario

SpecificOperation

Backingup andrestoringthe T2000MO data

l Back up all data in the T2000database as an MO file. Thedata is in the .txt format. Youcan read the data file only ifyou are familiar with the datastructure of the T2000.

l All data is backed up.

l This method features highprocessing speed and smallsize of the backup file.

This method ispreferred for backingup and restoring databetween the T2000systems of the sameversion. The backupMO files are version-specific and are notinterchangeable.

For details, see 4.1.2Backing Up theT2000 MO Data and4.1.5 Restoring theMO Data of theT2000.

Backingup andrestoringall data inthe T2000databases

l Back up the structure andcontents of the T2000databases. The data is inbinary.

l All data is backed up.

l This method features highprocessing speed and largesize of the backup file.

This method requiresthe storage mediumof large capacity.Tapes arerecommended forregular backup.

For details, see 4.1.3Backing Up AllData in the T2000Database and 4.1.6Restoring All Dataof the T2000Databases.

Backingup andrestoringscript-basedT2000networkconfiguration data

l Export the configurationdata of the T2000 as a textfile, which stores data and iseasy to read.

l Not all data is backed up. Thedata backed up only coversthe general configuration,port naming rule, andnetwork customization.

l This method features highprocessing speed and smallsize of the backup file.

The T2000 of a laterversion is compatiblewith the scripts forthe T2000 of anearlier version.Hence, this methodis generally adoptedfor upgrade of theT2000. Also, thismethod is applicableto back up andrestore the generalconfiguration data ofan NE, or to restorethe networkcustomization data.

For details, see 4.1.4Backing Up theT2000 NetworkConfiguration Databy Means ofScripts and 4.1.7Restoring theT2000 NetworkConfiguration Databy Means ofScripts.

NOTE

You can specify a remote server for restoring the T2000 databases. For specific operations, see the OptiXiManager T2000 Operation Guide for RTN for RTN NE Management.

Suggestion

l When you finish installing the T2000 for the first time, back up the T2000 databases. One-time backup is necessary if the databases are not expanded. If sufficient capacity (10G or


Maintenance Guide


Issue 02 (2009-06-30)

more idle capacity) is available on the hard disk, back up the T2000 databases by quarter.Regularly back up the databases in the case of sufficient capacity on the hard disk.

l Back up the MO data of the T2000 during routine maintenance. Whenever serviceconfiguration data changes, back up the MO data immediately. You can also set up ascheduled task to back up the MO data on a monthly basis.

l To release capacity of the hard disk, clear the data previously backed up, after a new backup.

l To restore the T2000 MO data and all data in the T2000 databases, first shut down theT2000 server.

4.1.2 Backing Up the T2000 MO DataWhen the system becomes faulty, you can quickly restore the system data from the backed upMO data. This section describes how to back up the MO data of the T2000.

Prerequisitel The T2000 user must log in and display the Main Topology interface.

l You must be a T2000 user with "NM administrator" authority or higher.

Background InformationThe default directories where the database file is backed up are as follows.l On the UNIX platform, the MO data is backed up to /T2000/server/database/

dbbackup.l On the Windows platform, the MO data is backed up to \T2000\server\database

\dbbackup.

PrecautionsThe method of restoring the system data from the backed up MO data is not applicable to upgradeof the T2000. In the case of upgrade of the T2000, import and export scripts to store the systemdata.

Procedure

Step 1 Start the Database Management Tool.

NOTE

l On the UNIX platform, right-click on the common desktop environment (CDE) and then chooseTools > Terminal to display a terminal window. In the /T2000/server/database directory, run"T2000DM.sh" to display the Database Management Tool window.

l On the Windows platform, open Windows Explorer. In the \T2000\server\database directory, run"T2000DM.exe". The T2000DM.exe window appears and then immediately disappears, and theDatabase Management Tool window displays.

Step 2 In Database Server List on the left, select T2000DBServer.

Step 3 In the displayed dialog box, enter the password of user sa.

NOTE


Step 4 Click Backup MO to display the Description dialog box.



4-7

Step 5 Set the backup directory on the server, and enter the relevant description information. ClickBackup to display the Back Up MO dialog box. In this case, the backup of the MO data of theT2000 is started.

NOTE

l If the customized directory of data backup is not disk C, you can avoid the effect on the backup datawhen you reinstall the system or format disk C, so that the maintainability of the system is improved.

l The backup directory should be short and should not contain special characters, such as spaces,punctuation, and Chinese characters.

Step 6 Click OK in the dialog box. Return to the Database Management Tool window.

----End

4.1.3 Backing Up All Data in the T2000 DatabaseThis section describes how to use the database management tool to immediately back up theT2000 database to the local server, and thus to quickly restore the data when the database isfaulty.

Prerequisitel On the UNIX platform, the current user must be a root user, and the Sybase database must

be started.l On the Windows platform, the current user must have the administrator authority of the

operating system. The MS SQL server database must be started.

Procedure

Step 1 Start the Database Management Tool.l On the UNIX platform, right-click the common desktop environment (CDE) and choose

Tools > Terminal to display a terminal window. In the /T2000/server/database directory,run "T2000DM.sh" to display the Database Management Tool window.

l On the Windows platform, open Windows Explorer. In the \T2000\server\databasedirectory, run "T2000DM.exe". The T2000DM.exe window appears and then immediatelydisappears, and the Database Management Tool window displays.

Step 2 In the Database Server List on the left, select T2000DBServer.

Step 3 In the dialog box displayed, enter the password of user sa.

NOTE


Step 4 Click Backup Database to display the Description dialog box.

Step 5 Enter the path and a description of the database backup.

NOTE

l By customizing the backup directory of the data, you can prevent the impact on the backup data whenyou re-install the system or format disk C, thus improving the maintainability of the system.

l Ensure that the backup directory is short and contains no space, punctuation, or Chinese character.

Step 6 Click Backup to back up the T2000 database.


Maintenance Guide


Issue 02 (2009-06-30)

Step 7 When the backup is complete, click OK in the displayed indication dialog box and return to thedatabase management tool interface.

----End

4.1.4 Backing Up the T2000 Network Configuration Data by Meansof Scripts

Before upgrading the T2000, export the data stored in the T2000 databases and save the data asa script file.



l Before exporting the script file, check the consistency of the configuration data to ensuredata consistency between the T2000 and the NEs. For specific operations, see 8.7 CheckingData Consistency Between an NE and the T2000.

Procedure

Step 1 Choose System > Import/Export Script File from the Main Menu and the Import/ExportScript File window is displayed.

Step 2 Select the file format, click Export and then select the script file type in Script File Type.

NOTE

l For types of exported script files, see Table 4-1 in 4.1.1 Methods of Backing Up and Restoring theT2000 Data.

l To export a script containing networkwide configuration data, select Networkwide ConfigurationFile. The files exported to the specified directory are as follows:

l Networkwide Configuration File "NGCfg_NM name.txt"

l NE List File "NWNeList_NM name.txt"

l NE Port Naming File "NEPort_extended ID-basic ID_NE name.txt"

l NE Configuration File "NEData_extended ID-basic ID_NE name.txt"

Step 3 Select the NE for which you want to export script files from the Export NE List on the left.

NOTE

Specify the NEs for exporting NE Configuration File, NE List File, NE Port Naming File, andNetworkwide Configuration File.

Step 4 Click Create File Directory to create a directory to save the exported script files.

Step 5 Input the name of the newly created directory and click OK. The newly created directory willbe displayed automatically in the Operation Directory List area.



4-9

NOTE

The script files are saved on the T2000 server. For the Windows platform, the script files are backed up to\T2000\server\script. For the UNIX platform, the script files are backed up to /T2000/server/script. Forboth cases, the user can create sub-folders further.

Step 6 Select a directory and click Apply.

Step 7 Click OK in the displayed Confirm dialog box. A progress bar appears, indicating the progressof exporting script files.

----End

4.1.5 Restoring the MO Data of the T2000This section describes how to restore the MO data of the T2000.

Prerequisitel The T2000 MO data must be backed up.

l The T2000 server must be shut down.

l On the UNIX platform, the current user must be root, and the Sybase database must bestarted.

l On the Windows platform, the current user must have the authority of administrator of theoperating system. The MS SQL server database must be started.

l The T2000 database must be initialized. The software of the T2000 server must be startedup and then shut down.

Context

CAUTIONIn the case of the MO data to be restored, the T2000 versions must be consistent.

NOTE

The default directories where the database file should be backed up are as follows.

l On the UNIX platform, back up the MO data to /T2000/server/database/dbbackup.

l On the Windows platform, if the T2000 server is installed in disk C, back up the MO data to C:\T2000\server\database\dbbackup.

Procedure

Step 1 Start Database Management Tool.l On the UNIX platform, right-click on the common desktop environment (CDE) and then

choose Tools > Terminal to display a terminal window. In the /T2000/server/databasedirectory, run "T2000DM.sh".

l On the Windows platform, open Windows Explorer. In the \T2000\server\databasedirectory, run "T2000DM.exe".



Maintenance Guide


Issue 02 (2009-06-30)


NOTE


Step 4 Click Restore MO to display the Select MO dialog box.

Step 5 Specify the directory where the MO data to be restored should be saved. Click Restore and clickYes in the displayed Confirm dialog box to restore the MO data of the T2000.

Step 6 When the restoration is complete, click OK in the Restore MO dialog box and return to thedatabase management tool interface.

----End

4.1.6 Restoring All Data of the T2000 DatabasesThis section describes how to restore the data stored in the T2000 databases backed up beforeby using the database management tool.

Prerequisitel The T2000 MO data must be backed up.

l The T2000 server must be shut down.

l On the UNIX platform, the current user must be root, and the Sybase database must bestarted.

l On the Windows platform, the current user must have the authority of administrator of theoperating system. The MS SQL server database must be started.

Context

CAUTIONIn the case of the data restoration, the T2000 versions must be consistent.

Procedure

Step 1 Start The Database Management Tool.l On the UNIX platform, right-click on the common desktop environment (CDE) and then

choose Tools > Terminal to display a terminal window. In the /T2000/server/databasedirectory, run "T2000DM.sh".

l On the Windows platform, open Windows Explorer. In the \T2000\server\databasedirectory, run "T2000DM.exe".



NOTE




4-11

Step 4 Click Restore Database to specify the directory where the database file is backed up.

Step 5 Click Restore and click Yes in the displayed Confirm dialog box to restore the database dataof the T2000.

Step 6 When the restoration is complete, click OK in the Restore Database dialog box and return tothe Database Management Tool interface.

----End

4.1.7 Restoring the T2000 Network Configuration Data by Means ofScripts

When upgrade of the T2000 software is complete, restore the network configuration data fromthe backup script files.



l You must have the license for the T2000 script import.

Precautions

CAUTIONBefore importing the script file, back up the T2000 database or the T2000 MO data. Then,initialize the T2000 database. Finally, import the networkwide configuration script file. Ifimporting the script files fails, restore the data from the backup database or MO data.

Procedure

Step 1 Choose System > Import/Export Script File from the Main Menu.

Step 2 Select the file format, click Import and then select the script file type in Script File Type.

NOTE

Service Actualization Script and NM Computer Information File cannot be imported.

Step 3 In Operation Directory List, select the directory where the script file for importing is located.

Step 4 Select the script file to be imported from Import File List.

Step 5 Click Apply. The system prompts twice that importing the script files causes data inconsistencybetween the T2000 and NE.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

When the script files are imported, deliver the configuration data from the T2000 to the NE for dataconsistency. For specific operations, see Downloading NE Configuration Data.

Step 6 Click OK. A progress bar appears, indicating the progress of importing script files.

NOTE

The script files are saved on the T2000 server. For the Windows platform, the script files are backed up to\T2000\server\script. For the UNIX platform, the script files are backed up to /T2000/server/script. Forboth cases, the user can create sub-folders further.

----End

4.2 Backing Up and Restoring the NE DataTo ensure security of the NE data, back up and restore the NE data in a timely manner.

4.2.1 Methods of Backing Up and Restoring NE DataSave important NE data during routine maintenance. In this way, if the system control board ofthe NE loses data or the equipment is powered off, the NE data can be restored for normaloperation of the NE. This section describes certain methods of backing up and restoring NE data.Select a proper method as required.

4.2.2 Backing Up the NE Database to the System Control BoardDuring routine maintenance, back up the NE database for restoring data when the system controlboard loses data or the equipment power-off is unexpectable. To back up the NE database to thesystem control board is to back up the NE data to the flash of the system control board. Whenthe NE restarts after a power failure, the system control board automatically reads theconfiguration data from the flash and delivers the configuration data to other boards.

4.2.3 Backing Up the NE Database to the CF CardDuring routine maintenance, back up the NE database for restoring data when the system controlboard loses data or the equipment power-off is unexpectable. You can back up the NE databaseto the CF card.

4.2.4 Backing Up the NE Database to a Local ServerTo improve the security of the NE database and prevent the loss of the database files due to anNE fault, you need to back up the NE database. Periodic backup of the database files isrecommended. You can back up the database files to NMS server or NMS client.

4.2.5 Restoring the NE Database from the System Control BoardIf the database file is lost due to NE maintenance or an NE fault, you can restore the NE databasefrom the backup database file on the system control board.

4.2.6 Restoring the NE Database from the CF CardWhen the database file is lost due to NE maintenance or an NE fault, you can restore the NEdatabase from the backup database file on the CF card of the system control board.

4.2.7 Recovering the NE Database from a Local ServerIf the database file is lost due to NE maintenance or an NE fault, you can recover the NE databasefrom the backup database file on the system control board.

4.2.1 Methods of Backing Up and Restoring NE DataSave important NE data during routine maintenance. In this way, if the system control board ofthe NE loses data or the equipment is powered off, the NE data can be restored for normal



4-13

operation of the NE. This section describes certain methods of backing up and restoring NE data.Select a proper method as required.

Comparison Among the Methods of Backing Up and Restoring NE DataIn the case of backup and restoration, the NE data can be saved on the system control board, CFcard, or local server. The methods of backing up and restoring NE data are specific to where theNE data is saved. For details, see Table 4-3.

Table 4-3 Methods of backing up and restoring NE data and their application scenarios

Backup andRestoration Method

Application Scenario Specific Operation

Back up NE data to orrestore NE data fromthe system controlboard.

This method is applicable to thesystem control board notconfigured with any CF card.l Back up NE data in the DRDB

to the flash of the systemcontrol board.

l To restore NE data, thesystem resets (warm) thesystem control board, readsthe configuration data storedin flash, and delivers theconfiguration data to otherboards.

For details, see 4.2.2 BackingUp the NE Database to theSystem Control Board and4.2.5 Restoring the NEDatabase from the SystemControl Board.

Back up NE data to orrestore NE data fromthe CF card.

This method is applicable to thesystem control board configuredwith a CF card.l Back up the NE data in the

DRDB to the CF card.l To restore the NE database,

copy the NE database fromthe CF card to the flash of thesystem control board. Afterreset (warm), the systemcontrol board readsconfiguration data in the flashand delivers the configurationdata to other boards.

For details, see 4.2.3 BackingUp the NE Database to the CFCard and 4.2.6 Restoring theNE Database from the CFCard.

Back up NEconfiguration data toor restore NEconfiguration datafrom the local server.

Back up NE configuration datato the computer where the T2000server or client is installed.

For details, see Backing Up theNE Configuration Data to aLocal Server and 4.2.7Recovering the NE Databasefrom a Local Server.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

You can also specify a remote server for restoring the NE databases. For specific operations, see the OptiXiManager T2000 Operation Guide for RTN NE Management.

NE DatabaseNE configuration data is stored in the NE databases on the system control board. The types ofNE databases are as follows:

l Memory database (MDB): The data in this database varies with the configurationinformation, and is lost when the system control board is reset or powered off.

l Dynamic random database (DRDB): This database automatically stores data that is verified.

l Flash database (FDB): FDB is divided into FDB0 and FDB1. The data in FDB is copiedfrom DRDB and can be stored permanently.

The NE configuration data, when delivered, is first stored in MDB. Then, the data is verified. Ifthe data passes the verification, the system control board automatically copies data from MDBto DRDB and delivers the generated configuration data to other boards. Data needs to be copiedfrom DRDB to FDB, which then backs up DRDB.

When the NE restarts upon a power failure, the system control board checks for configurationdata in DRDB. In the case of any configuration data in DRDB, the system control board restoresdata from DRDB; in the case any damage to the configuration data in DRDB, the system controlboard restores data from FDB0 and FDB1.

NE Configuration DataThe NE configuration data refers to the information in DRDB of the NE, such as the boardconfiguration, clock configuration, and protection relations of the NE. The NE configurationdata is the instruction file of the NE and the key for the NE to normally operate in the entirenetwork.

NE Database PackageThe NE database package indicates a collection of all database files on an NE. A file list definesand manages those files in the package.

The NE database package contains the same data as the NE configuration data. The data is calleddifferently for different NE releases. In the case of an NE of release 5.00.06 or later, you canback up and restore the NE database package.

4.2.2 Backing Up the NE Database to the System Control BoardDuring routine maintenance, back up the NE database for restoring data when the system controlboard loses data or the equipment power-off is unexpectable. To back up the NE database to thesystem control board is to back up the NE data to the flash of the system control board. Whenthe NE restarts after a power failure, the system control board automatically reads theconfiguration data from the flash and delivers the configuration data to other boards.

Prerequisitel You must log in to the NE as an NE user of the system level.

l You must be a T2000 user with "NE and Network Operator" authority or higher.



4-15

Procedure

Step 1 Choose Configuration > Configuration Data Management from the Main Menu. TheConfiguration Data Management window is displayed.

Step 2 In the Object Tree on the left, select an NE and click .


Step 4 Choose Back Up NE Data > Back Up Database To SCC. Click OK in the displayedConfirm to start the backup.

Step 5 Click Close in the displayed Operation Result dialog box to complete the operation.

----End

4.2.3 Backing Up the NE Database to the CF CardDuring routine maintenance, back up the NE database for restoring data when the system controlboard loses data or the equipment power-off is unexpectable. You can back up the NE databaseto the CF card.

Prerequisitel You must log in to the NE as an NE user with "System Level" authority.

l You must be an NM user with "NE and Network Operator" authority or higher.

l The system control board is configured with a CF card.

Procedure


Step 2 Select an NE from the Object Tree, and then click .


Step 4 Click Back Up NE Data > Manually back up database to CF Card . Click OK to start thebackup.

Step 5 In the displayed Operation Result dialog box, click Close.

----End

4.2.4 Backing Up the NE Database to a Local ServerTo improve the security of the NE database and prevent the loss of the database files due to anNE fault, you need to back up the NE database. Periodic backup of the database files isrecommended. You can back up the database files to NMS server or NMS client.


l You must be a T2000 user with "NE and Network Maintainer" authority or higher.


Maintenance Guide


Issue 02 (2009-06-30)

l The NE must be created on the T2000.

l The computer where the T2000 is installed must be able to normally communicate with theNE.

l The FTP/HFCP/SFTP server is configured and the FTP/HFCP/SFTP service is started.

Contextl Backup operation can be performed on multiple devices of the same device type.

l On selecting the device type in the device tree, all the devices and the device type versionsrelated to the device type is displayed in the Device View table.

l The files are backed up from the server can be viewed in the Backup Information tab.

Procedure

Step 1 Choose Data Center > Device Operation from the Main Menu to open the DeviceOperation tab. The device types are displayed in the device tree on the left.

Step 2 Select and right-click the device(s) that you want to backup in the right Device View table, andclick Backup.

NOTE

The Backup Information tab is unavailable when multiple devices are selected.

Step 3 In the displayed Backup dialog box, select backup to NMS Server or NMS Client.

l If the NMS Server is selected, the database file is stored on the NMS server.

l If the NMS Client is selected, the database file is stored on the NMS client and you need to

click to select the location where the device data have to be backed up.

Step 4 Click Start and the backup processing information is displayed in the Device View area.

----End

ResultThe selected NE's database is successfully backed up.



4-17

4.2.5 Restoring the NE Database from the System Control BoardIf the database file is lost due to NE maintenance or an NE fault, you can restore the NE databasefrom the backup database file on the system control board.

Prerequisitel You must log in to the NE as an NE user with "system level" authority.


l The NE Database must be backed up to the system control board.

Procedure

Step 1 Double-click an NE on the Main Topology to display the Running Status slot layout.

Step 2 Right-click a board and select Warm Reset.

Step 3 In the displayed dialog box, click OK to finish restoring the NE database.

----End

4.2.6 Restoring the NE Database from the CF CardWhen the database file is lost due to NE maintenance or an NE fault, you can restore the NEdatabase from the backup database file on the CF card of the system control board.

Prerequisitel You must log in to the NE as an NE user with "system level" authority.


l The system control board must be configured with a CF card and the NE database must bebacked up to the CF card.

Procedure


Step 2 Select an NE from the Object Tree, and then click .


Step 4 Click Restore NE Database. The Confirm dialog box is displayed, indicating that restoring theNE database may interrupt services.

Step 5 Click OK to start restoring the NE database.

Step 6 Click Close.

----End

PostrequisiteWhen the restoration is complete, the database on the CF card is restored to the memory of thesystem control board, but not delivered to other boards. To restore the configuration data of the


Maintenance Guide


Issue 02 (2009-06-30)

boards, perform warm reset on the system control board and then on other boards. During resetof other boards, the system control board delivers the configuration data to the boards again.

4.2.7 Recovering the NE Database from a Local ServerIf the database file is lost due to NE maintenance or an NE fault, you can recover the NE databasefrom the backup database file on the system control board.



l The NE must be created on the T2000.

l The computer where the T2000 is installed must be able to normally communicate with theNE.

l The database package for recovering is available. Only the data backed up when the NE isin the running state can be restored to the NE.

l The FTP/HFCP/SFTP server is configured and the FTP/HFCP/SFTP service is started.

Contextl You cannot perform the Recover operation for devices of different device types.

l On selecting the device type in the device tree, all the device information related to thedevice type is displayed in the Device View table.

Precautions

CAUTIONBefore recovering the NE database file to the NE, make sure that the database file for restorationis correct; otherwise, services are interrupted.

Procedure

Step 1 Choose Data Center > Device Operation from the Main Menu to open the DeviceOperation tab. The device types are displayed in the device tree on the left.

Step 2 Select and right-click the device(s) that you want to backup in the right Device View area, andclick Recover to open the Recover dialog box.



4-19

Step 3 Select the file to be recovered from the File Name drop-down list. If the file is not listed, clickBrowse to display the Select File dialog box.

Step 4 Select the file from NMS Server or NMS Client to recover.l If the NMS Server is selected, select the file to be recovered from the NMS Server. The

selected file path is displayed in the Select File dialog.

l If the NMS Client is selected, click to select the file to be recovered from the NMSClient. The selected file path is displayed in the following Selected File dialog.


Maintenance Guide


Issue 02 (2009-06-30)

Step 5 Click OK. The selected file path from the NMS Server or NMS Client is displayed in the FileName drop-down list.

Step 6 Click Start and click Yes in the displayed Operation Confirmation dialog box. The processinginformation is displayed in the Device View area.

NOTE

When the restoration is complete, the following information will be displayed in the Device View area.

Step 7 Right-click the device icon and click Activation Database to activate the database file whichis just restored.



4-21

----End

ResultThe selected NE's database is successfully recovered.


Maintenance Guide


Issue 02 (2009-06-30)

5 Replacing Components

About This Chapter

Component replacement refers to the replacement of a board or component for purpose ofmaintaining or expanding capacity for the equipment. This operation, though done on theequipment site, requires support from the T2000.

5.1 Replacing the CXPR with the 1+1 ProtectionWhen the CXPR becomes faulty or during capacity expansion, the board needs to be replaced.This section describes replacement of the CXPR with the 1+1 protection in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

5.2 Replacing the CXPR Without the 1+1 ProtectionWhen the CXPR becomes faulty or during capacity expansion, the board needs to be replaced.This section describes replacement of the CXPR not configured with the 1+1 protection in termsof prerequisite, impact on system, precautions, tools, and operation procedure.

5.3 Replacing the Processing BoardsThe processing boards include the EF8T, EF8F, EG2, ML1, and ML1A. When a processingboard becomes faulty or capacity expansion is required, the board needs to be replaced. Thissection describes replacement of a processing board in terms of prerequisite, impact on system,precautions, tools, and operation procedure.

5.4 Replacing the IFE2 BoardWhen the IFE2 board becomes faulty or capacity expansion is required, the IFE2 board needsto be replaced. This topic describes the replacement of the IFE2 board in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

5.5 Replacing the FAN BoardWhen the FAN board becomes faulty or during capacity expansion, the FAN board needs to bereplaced. This section describes replacement of the FAN board in terms of prerequisite, impacton system, precautions, tools, and operation procedure.

5.6 Replacing the PIU BoardWhen the PIU board becomes faulty or during capacity expansion, the PIU board needs to bereplaced. This section describes replacement of the PIU board in terms of prerequisite, impacton system, precautions, tools, and operation procedure.

5.7 Replacing the AUXQ Board

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 5 Replacing Components


5-1

When an AUXQ board becomes faulty or capacity expansion is required, the AUXQ board needsto be replaced. This section describes replacement of the AUXQ board in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

5.8 Replacing the ChassisThe entire case-shaped equipment needs to be replaced when the backplane of chassis becomesfaulty, or the equipment is severely damaged by external force. This section describesreplacement of the chassis in terms of prerequisite, impact on system, precautions, tools, andoperation procedure.

5.9 Replacing the Pluggable Optical ModuleThis section provides information on how to replace the pluggable optical module. When theoptical module becomes faulty, it needs to be replaced in time. So, the optical interface can worknormally.

5.10 Replacing the ODUThe method of replacing the ODU with the waveguide interface is different from the method ofreplacing the ODU with the coaxial interface.

5.11 Replacing the IF CableThis topic describes how to replace an IF cable.

5 Replacing ComponentsOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

5.1 Replacing the CXPR with the 1+1 ProtectionWhen the CXPR becomes faulty or during capacity expansion, the board needs to be replaced.This section describes replacement of the CXPR with the 1+1 protection in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

Prerequisitel You must be a T2000 user with "NE and Network Operator" authority or higher.

l The 1+1 board protection group must be available.

l The standby CXPR board is in service and works normally.

Impact on SystemIf the CXPR is configured with the 1+1 protection, replacing the faulty CXPR board does notaffect services when the switching is normally performed.

PrecautionsBefore replacing the CXPR, read Safety Precautions for Using the Equipment.

CAUTIONWhen replacing a board, make sure that the board is not connected to any cables. The cableconnectors must be properly enveloped to avoid short circuit.

Tools, Equipment and MaterialsAnti-static bag, ESD wrist strap, T2000, crosshead screwdriver

Procedure

Step 1 Make sure that the spare board is the same as the board to be replaced with respect to the name,model, and parameters.

Step 2 Query the current alarms of the board. When the replacement is complete, you can check whetherthe original alarms are cleared and no new alarms are generated. For details, see 8.2 QueryingCurrent Alarms of a Board.

Step 3 Query whether the 1+1 protection switching occurs on the board. For details, see 8.23 QueryingProtection Configuration.l If the slot and the board name of the faulty board is displayed in Active Board, it indicates

that the protection switching does not occur. Go to Step 4.l If the slot and the board name of the faulty board is not displayed in Active Board, it

indicates that the 1+1 protection switching is complete. Go to Step 5.

Step 4 On the T2000, perform the 1+1 protection switching for the faulty CXPR board. For details, see8.11 Performing the 1+1 Protection Switching for CXPR boards.



5-3

Step 5 Ask the on-site maintenance personnel to remove the faulty CXPR board. For specificoperations, see 8.19 Replacing Boards on Site.

NOTE

l When the replacement is complete, the PROG indicator on the newly inserted CXPR board flashesgreen, indicating that the board software is being loaded. This process will take about 5 minutes.

l CXPR will restore the original configuration data from the active board after the board software issuccessfully loaded. This process will take about 5 minutes.

Step 6 Optional: On the T2000, cancel the board 1+1 protection switching. For details, see 8.11Performing the 1+1 Protection Switching for CXPR boards.

NOTE

If the recovery of the board working/protection state is faulty, the working and protection boards may bein the backup state. In this case, wait for at least 5 min, and then perform the recovery operation.

Step 7 Check whether the fault is rectified.1. Check indicators of the newly inserted CXPR board. If any indicator flashes abnormally,

remove and then insert the board, or replace the board. For more details on the indicatorsof boards, see the OptiX RTN 950 Radio Transmission System IDU HardwareDescription..

2. Query the board alarms. Make sure that the alarms generated by the original faulty boardare cleared.

----End

5.2 Replacing the CXPR Without the 1+1 ProtectionWhen the CXPR becomes faulty or during capacity expansion, the board needs to be replaced.This section describes replacement of the CXPR not configured with the 1+1 protection in termsof prerequisite, impact on system, precautions, tools, and operation procedure.



Impact on System

Replacing the CXPR interrupts services for about 15 minutes.

Precautions

Before replacing the CXPR, read Safety Precautions for Using the Equipment.

CAUTIONWhen replacing a board, make sure that the board is not connected to any cables. The cableconnectors must be properly enveloped to avoid short circuit.


Maintenance Guide


Issue 02 (2009-06-30)


Anti-static bag, ESD wrist strap, T2000, crosshead screwdriver

Procedure


Step 2 Query and record the current alarms of the CXPR. When the replacement is complete, you cancheck whether the original alarms are cleared and no new alarms are generated. For specificoperations, see 8.2 Querying Current Alarms of a Board.

Step 3 Query and record the current NE user. When the board replacement is complete, restore dataabout the login NE user.1. Right-click the target NE and choose NE Explorer. The NE Explorer window is displayed.2. Choose Security > NE Login Management from the Function Tree on the left.3. Check the NE Login Management Table on the right, and record the current login NE

user.

Step 4 Back up the NE database to the CF card. When the replacement is complete, you can restore theNE database in time. For details, refer to 4.2.3 Backing Up the NE Database to the CFCard.

Step 5 Ask the on-site maintenance personnel to draw out the CXPR board, move the CF card to thespare CXPR board, and insert the spare CXPR board into the chassis. For specific operations,refer to 8.19 Replacing Boards on Site and the OptiX RTN 950 Radio Transmission SystemIDU Quick Installation Guide manual.

Step 6 Press and hold the CF RCV button of the CXPR board for 5 seconds to restore the NE databasefrom the CF card.

NOTE

l In the process of restoring NE database, the PROG indicator on the CXPR flashes green.

l When the STAT and PROG indicators on the CXPR stay green without flashing, it indicates that theNE database is completely restored and the board is working normally. In this case, you can performoperations on the T2000. Otherwise, re-insert the CXPR or replace it with another spare CXPR ifnecessary.

l The process of restoring NE database will take about 5 minutes.

Step 7 Use the NE user which is recorded in the step 3 and log in the T2000.

Step 8 Check whether the original alarms are cleared and no alarms are generated. If yes, it indicatesthat the board replacement is successful.

----End

5.3 Replacing the Processing BoardsThe processing boards include the EF8T, EF8F, EG2, ML1, and ML1A. When a processingboard becomes faulty or capacity expansion is required, the board needs to be replaced. Thissection describes replacement of a processing board in terms of prerequisite, impact on system,precautions, tools, and operation procedure.



5-5



Impact on SystemReplacing a processing board interrupts the service on the board for about 3 - 5 minutes.

PrecautionsBefore replacing a processing board, read Safety Precautions for Using the Equipment.

DANGERAvoid direct eye exposure to the laser beam launched from the optical interface board or frominside the fiber, for the laser beam may cause permanent damage to the eyes.

WARNINGl When replacing a processing board, make sure that the board is not connected to any fiber

jumpers or cables.l The optical interface and the fiber jumper connector must be clean. Seal the jumper connector

in protection cap.l The cable connectors must be properly sealed to prevent short circuit.

Tools, Meters, and MaterialsAnti-static bag, ESD wrist strap, T2000, crosshead screwdriver

ProcedureStep 1 Make sure that the spare board is the same as the board to be replaced with respect to the name,

model, and parameters.

Step 2 Query and record the current alarms of the processing board. When the replacement is complete,you can check whether the original alarms are cleared and no new alarms are generated. Forspecific operations, see 8.2 Querying Current Alarms of a Board.

Step 3 Ask the on-site maintenance personnel to remove the faulty processing board. For specificoperations, see 8.19 Replacing Boards on Site.

NOTE

All the processing boards support hot plugging. When the board replacement is complete, the newprocessing board is in the process of initialization and sets up service connections automatically. Thisprocess will take each board about one minute.

Step 4 Check indicators of the newly inserted processing board. If any indicator flashes abnormally,remove and then insert the board, or replace the board the second time. For more details on the


Maintenance Guide


Issue 02 (2009-06-30)

indicators of boards, see the OptiX RTN 950 Radio Transmission System IDU HardwareDescription..


----End

5.4 Replacing the IFE2 BoardWhen the IFE2 board becomes faulty or capacity expansion is required, the IFE2 board needsto be replaced. This topic describes the replacement of the IFE2 board in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

Prerequisitel The location of the board to be replaced must be specified.

l The service protection and protection channels of the board to be replaced must be specified.

l A spare board must be prepared, and the version and type of the spare board must be thesame as those of the board to be replaced.

Impact on Systeml On the equipment without 1+1 IF protection, the replacement of the IF board causes service

interruption.l On the equipment with 1+1 IF protection, the replacement of the current protection IF board

does not affect the service. The replacement of the currently working IF board, however,causes transient service interruption during the protection switching.

PrecautionsBefore you replace the IFE2 board, be sure to turn off the ODU-PWR switch on the IFE2 board.

Tools, Equipment and Materialsl ESD wrist strap

l Screwdriver

l T2000

Procedure

Step 1 Query the current alarms of the IFE2 board by referring to Querying the Current Alarms ofa Board, and record the alarms.

Step 2 Optional: If the microwave service is provided with 1+1 protection, be sure to switch the serviceto the protection IF board.1. Perform the task described in Querying the Working State of the IF 1+1 Protection

Group.2. If the board to be replaced acts as the working board instead of the protection board and

the protection channel is in the normal or SD state, performed forced switching.



5-7

Step 3 Turn off the ODU-PWR switch on the IF board to be replaced.

Step 4 Replace the IFE2 board by referring to Replacing Boards On Site.

Step 5 After the board starts to work, observe the indicators on the board.The STAT indicator should be lit green.

Step 6 Turn on the ODU-PWR switch on the IF board.

Step 7 Repeat Step 1.There should be no new alarms.

Step 8 Optional: If you have performed forced switching earlier between the radio links, release theswitching through the T2000.

----End

5.5 Replacing the FAN BoardWhen the FAN board becomes faulty or during capacity expansion, the FAN board needs to bereplaced. This section describes replacement of the FAN board in terms of prerequisite, impacton system, precautions, tools, and operation procedure.



Impact on System

If the FAN becomes faulty, replace it in a timely manner; otherwise, the equipment may becomefaulty because of poor heat dissipation.

Precautions

Before replacing the FAN board, read Safety Precautions for Using the Equipment.

WARNINGWhen the FAN board is removed, do not touch the rotating fan leaves.

Tools, Meters, and Materials

Anti-static bag, ESD wrist strap, T2000

Procedure



Maintenance Guide


Issue 02 (2009-06-30)

Step 2 Query and record the current alarms of the FAN board. When the replacement is complete, youcan check whether the original alarms are cleared and no new alarms are generated. For specificoperations, see 8.2 Querying Current Alarms of a Board.

Step 3 Ask the on-site maintenance personnel to remove the faulty FAN board. For specific operations,see 8.19 Replacing Boards on Site.

Step 4 Verify that the FAN board is successfully replaced.

1. When the board replacement is complete, check whether the FAN indicator on the newboard stays on and green. If not, re-insert the FAN board or replace it with another spareFAN board if necessary.

2. Query alarms of the board. Make sure that the original alarms of the FAN board are clearedand no new alarms are generated.

----End

5.6 Replacing the PIU BoardWhen the PIU board becomes faulty or during capacity expansion, the PIU board needs to bereplaced. This section describes replacement of the PIU board in terms of prerequisite, impacton system, precautions, tools, and operation procedure.



Impact on System

If the PIU boards are of 1+1 hot backup, replacing one PIU board does not affect the services.

Precautions

WARNINGWhen replacing the PIU board, turn off the switch on the power supply device connected to thePIU board and then remove all cables connected to the PIU board.


Anti-static bag, ESD wrist strap, T2000

Procedure




5-9

Step 2 Query and record the current alarms of the system. When the replacement is complete, you cancheck whether the original alarms are cleared and no new alarms are generated. For specificoperations, see 8.2 Querying Current Alarms of a Board.

Step 3 Ask the on-site maintenance personnel to turn off the switch on the power supply deviceconnected to the PIU board. For specific operations, see 8.21 Powering Off the Equipment.

CAUTIONTurn off the correct switch that corresponds to the PIU board to be replacement.

Step 4 Remove the power connectors of the faulty PIU board. Then, replace the faulty PIU board. Forspecific operations, see 8.19 Replacing Boards on Site.

Step 5 Power on the new PIU board. For specific operations, see 8.20 Powering On the Equipment.

Step 6 Verify that the PIU board is successfully replaced.1. Observe the indicators of all boards after the chassis is replaced. If any indicator flashes

abnormally, re-insert the PIU board or replace it with another spare one if necessary. Formore details on the indicators of boards, see the OptiX RTN 950 Radio Transmission SystemIDU Hardware Description.

2. Query alarms of the system. Make sure that the original alarms are cleared and no newalarms are generated.

----End

5.7 Replacing the AUXQ BoardWhen an AUXQ board becomes faulty or capacity expansion is required, the AUXQ board needsto be replaced. This section describes replacement of the AUXQ board in terms of prerequisite,impact on system, precautions, tools, and operation procedure.

Prerequisitel The T2000 user must log in and display the Main Topology interface.l You must be a T2000 user with "NE and Network Maintainer" authority or higher.

Impact on SystemReplacing the AUXQ board interrupts the service on the AUXQ board for about 3 minutes.

PrecautionsBefore replacing the AUXQ board, read Safety Precautions for Using the Equipment.

WARNINGWhen replacing a board, make sure that the board is not connected to any cable. The cableconnectors must be properly sealed to prevent short circuit.


Maintenance Guide


Issue 02 (2009-06-30)



Procedure


Step 2 Query and record the current alarms of the AUXQ board. When the replacement is complete,you can check whether the original alarms are cleared and no new alarms are generated. Forspecific operations, see 8.2 Querying Current Alarms of a Board.

Step 3 Ask the on-site maintenance personnel to remove the faulty AUXQ board. For specificoperations, see 8.19 Replacing Boards on Site.

NOTE

The AUXQ board support hot plugging. When the board replacement is complete, the new AUXQ boardis in the process of initialization and sets up service connections automatically. This process will take aboutone minute.

Step 4 Check the STAT, SRV and LINK indicators stay on and green. If not, re-insert the AUXQ boardor replace it with another spare AUXQ board if necessary.


----End

5.8 Replacing the ChassisThe entire case-shaped equipment needs to be replaced when the backplane of chassis becomesfaulty, or the equipment is severely damaged by external force. This section describesreplacement of the chassis in terms of prerequisite, impact on system, precautions, tools, andoperation procedure.



Impact on System

Replacing the chassis interrupts services for about 30 minutes, because the equipment has to bepowered off during the replacement.

Precautions

Before replacing the chassis, read Safety Precautions for Using the Equipment.



5-11

DANGERAvoid direct eye exposure to the laser beam launched from the optical interface board or frominside the fiber, for the laser beam may cause permanent damage to the eyes.

WARNINGl When replacing a processing board, make sure that the board is not connected to any fiber

jumpers or cables.

l The optical interface and the fiber jumper connector must be clean. Seal the jumper connectorin protection cap.

l The cable connectors must be properly sealed to prevent short circuit.



Procedure

Step 1 Make sure that the spare chassis is the same as the chassis to be replaced with respect to thename, model, and appearance.

Step 2 Query and record the current alarms of the system. When the replacement is complete, you cancheck whether the original alarms are cleared and no new alarms are generated. For specificoperations, see 8.2 Querying Current Alarms of a Board.

Step 3 Record every board's present slot, and the fiber or cable connections of interfaces on the boards.When the chassis replacement is complete, recover the fiber or cable connections.

Step 4 Ask the on-site maintenance personnel to power off the equipment. For specific operations, see8.21 Powering Off the Equipment.

Step 5 Remove the power connectors, all fibers and cables connected to the chassis. Then, remove allboards. For specific operations, see 8.19 Replacing Boards on Site.

Step 6 Remove the mounting ears on the chassis and then take down the chassis. (Skip this step if thechassis is installed on the desk.)

WARNINGHold the bottom of the chassis when you remove the mounting ears. Otherwise, the chassis maydrop, causing hurt to human bodies or damage to other equipment.

Step 7 Remove the PGND cable and mounting ears, and install them onto the spare chassis. Install thespare chassis to the previous position. Then, recover all board, and the fiber or cable connections


Maintenance Guide


Issue 02 (2009-06-30)

according to Step 3. For specific operations, see OptiX RTN 950 Radio Transmission SystemIDU Quick Installation Guide.

Step 8 Powering on the equipment. For specific operations, see 8.20 Powering On the Equipment.

Step 9 Verify that the chassis is successfully replaced.

1. Observe the indicators of all boards after the chassis is replaced. If any indicator flashesabnormally, re-insert boards, or replace the chassis if necessary. For indications onindicators of boards, see OptiX RTN 950 Radio Transmission System IDU HardwareDescription.

2. Query alarms of the system. Make sure that the original alarms are cleared and no newalarms are generated.

----End

5.9 Replacing the Pluggable Optical ModuleThis section provides information on how to replace the pluggable optical module. When theoptical module becomes faulty, it needs to be replaced in time. So, the optical interface can worknormally.



Context

For the optical modules used on the OptiX RTN 950, see the OptiX RTN 950 Radio TransmissionSystem IDU Hardware Description.

Impact on System

Replacement of the optical module causes service interruption.


Anti-static bag, T2000

Precautions

CAUTIONBefore replacing the pluggable optical module, 8.4 Checking the Optical Power and make surethat the input optical power is within the normal range to avoid exceeding the overload pointwhich can damage the optical module.



5-13

Procedure

Step 1 A spare part is required. The model and parameters of the spare part must be the same as thoseof the optical module to be replaced.

Step 2 Query and record the current alarms on the NE. For details, refer to 8.2 Querying CurrentAlarms of a Board.

Step 3 Check the optical power and make sure that the input optical power is within the normal rangeto avoid exceeding the overload point which can damage the optical module. For details, referto 8.4 Checking the Optical Power.

Step 4 Inform the on-site maintenance engineer and replace the optical module.

NOTE

l Before you remove an optical module, remove the fiber jumpers that connect to it.

l There should be no fiber jumper connecting to the interfaces when you insert an optical module.

Figure 5-1 Inserting and removing the optical module

12

Removing optical module:1. Pull out the fiber connectors first.2. Pull safety latch to pull out the optical module from the optical port.3. Cover the port with cover.

Inserting optical module:1. Insert the spare part into port.2. Push the optical module slowly to the bottom until hearing a pop voice.3. Insert the fiber connectors as before.

safety latchoptical port spare part

NOTE

When you insert the spare optical module, avoid excessive force; otherwise, the interface circuit might bedamaged.

Step 5 Check the indicators of the board where the new optical module resides. If the indicator givesabnormal indication, you need to reinsert the optical module, or replace the optical module again.For more details on the indicators of boards, see the OptiX RTN 950 Radio Transmission SystemIDU Hardware Description..

Step 6 Query board alarms and make sure that the original alarms are cleared and no new alarms aregenerated. Check whether the module is online, and whether the input/output optical power andthe performance of the module are normal.

----End

5.10 Replacing the ODUThe method of replacing the ODU with the waveguide interface is different from the method ofreplacing the ODU with the coaxial interface.

5.10.1 Replacing the ODU with Waveguide Interface


Maintenance Guide


Issue 02 (2009-06-30)

In the OptiX RTN 950 system, all the ODUs have waveguide interfaces except the ODUs thatoperate in the 6 GHz band.

5.10.2 Replacing the ODU with Coaxial InterfaceIn the OptiX RTN 950 system, only the ODUs that operate in the 6 GHz band uses coaxialinterfaces.

5.10.1 Replacing the ODU with Waveguide InterfaceIn the OptiX RTN 950 system, all the ODUs have waveguide interfaces except the ODUs thatoperate in the 6 GHz band.

Prerequisitel The positions of the ODU to be replaced and the position of the IF board that is connected

to the ODU must be specified.l Spare ODU must be available on site, and the spare part must be the same as those to be

replaced in version and type

PrecautionsBefore you replace an ODU installed on the coupler, power off the ODU to be replaced, but donot power off or mute the other ODU. Otherwise, the services may be affected. The interface ofthe coupler ejects little RF radiation, and thus meets the safety standards for microwave radiation.

Before you replace an ODU, turn off the ODU power switch on the IF board.

Impact on SystemReplacing an ODU that is not provided with protection interrupts the service.

Tools, Equipment and Materialsl Torque spanner

l T2000

l Silicon

l Waterproof adhesive tape

Procedure

Step 1 Query and record the current alarms of the ODU.

Step 2 Turn off the ODU-PWR switch on the panel of the IF board.

Step 3 Disconnect the IF cable and grounding cable of the ODU.

Step 4 Loosen the four latches of the ODU and disconnect the ODU from the antenna or the hybridcoupler.

Step 5 Make sure the type of the spare ODU is the same with the type of the ODU to be replaced.

Step 6 Install the ODU.1. Remove the protective cap on the antenna interface of the ODU. Apply an appropriate

amount of lubricant to the gasket of the feeder on the antenna, coupler, or ODU adapter.



5-15

CAUTIONDo not dispense the lubricant on the front panel of the feeder. Otherwise, it may affect thesignal transmission.

2. Keep the direction indicated by the polarization arrow on the ODU consistent with thepolarization direction of the antenna or hybrid coupler. (In the case of vertical polarization,keep the polarization arrow vertical. In the case of horizontal polarization, keep thepolarization arrow horizontal). Slowly fit the antenna interface of the ODU into the feederuntil the four latches on the ODU engage with the hooks on the antenna.

3. Lock the four latches in a diagonal order.

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

Step 8 Perform waterproof processing for the IF interface of the ODU.

Step 9 Turn on the ODU-PWR switch on the panel of the IF board.

Step 10 When the ODU is working, observe the indicators of the IF board: ODU and LINK.The indicators ODU and LINK should be on in green.

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

----End

5.10.2 Replacing the ODU with Coaxial InterfaceIn the OptiX RTN 950 system, only the ODUs that operate in the 6 GHz band uses coaxialinterfaces.

Prerequisitel The position of the ODU to be replaced and the position of the IF board that is connected

to the ODU must be specified.l Spare ODU must be available on site, and the spare part must be the same as those to be

replaced in version and type

Impact on SystemReplacing an ODU that is not provided with protection interrupts the service.

PrecautionsBefore you replace an ODU installed on the coupler, power off the ODU to be replaced, but donot power off or mute the other ODU. Otherwise, the services may be affected. The interface ofthe coupler ejects little RF radiation, and thus meets the safety standards for microwave radiation.

Tools, Equipment and Materialsl Torque spanner

l T2000


Maintenance Guide


Issue 02 (2009-06-30)

l Silicon


Procedure

Step 1 Query and record the current alarms of the ODU.

Step 2 Turn off the ODU-PWR switch on the panel of the IF board.

Step 3 Disconnect the IF cable and grounding cable of the ODU.

Step 4 Remove the old ODU from the pole.

Step 5 Make sure the type of the spare ODU is the same with the type of the ODU to be replaced.

Step 6 Mount the new ODU to the pole.

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

Step 8 Perform waterproof processing for the IF interface of the ODU.

Step 9 Turn on the ODU-PWR switch on the panel of the IF board.

Step 10 When the ODU is working, observe the indicators of the IF board: ODU and LINK.The indicators ODU and LINK should be on in green.

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

----End

5.11 Replacing the IF CableThis topic describes how to replace an IF cable.

Prerequisitel The impact of replacing an IF cable must be specified.

l The position of the IF cable to be replaced and the position of the IF board that is connectedto the IF jumper must be specified.

Impact on SystemReplacing the IF cable interrupts the services.

PrecautionsBefore you replace the IF cable, be sure to turn off the ODU-PWR switch on the IF board.

Tools, Equipment and Materialsl Ejector lever

l Electro-technical knife

l File



5-17

l Installation parts and accessories of the type-N connector

l IF cable


Procedure

Step 1 Query and record the current alarms of the IDU.

Step 2 Turn off the ODU-PWR switch on the front panel of the IF board.

Step 3 Disconnect the IF cable from the IF jumper and from the ODU.

Step 4 Use a multimeter to test whether the IF cable conducts electricity well, and check whether youneed to make a new IF connector or to replace the IF cable with a new one.

If... Then...

You need to make a new IF connector Refer to Quick Installation Guide and make anew IF connector.

You need to replace the IF cable with a newone

Replace the IF cable with a new one.

Step 5 Connect the IF cable to the IF jumper and to the ODU.

Step 6 Use waterproof adhesive tapes to waterproof the connectors at both ends of the IF cable.

Step 7 Turn on the ODU-PWR switch on the front panel of the IF board.

Step 8 After the ODU starts to work, observe the ODU and LINK indicators on the IF board.The ODU indicator and LINK indicator should be on in green.

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

----End


Maintenance Guide


Issue 02 (2009-06-30)

6 Software Package Upgrade and PackageDiffusion

About This Chapter

In the case of software package upgrade and package diffusion, the NE-level software of theentire network is upgraded, activated and managed in a centralized manner. The softwarepackage upgrade and package diffusion help simplify upgrade and maintenance operations andimprove the efficiency of upgrade and maintenance.

ContextPlease download and consult the OptiX RTN 910&950 Upgrade Guide from Huawei TechnicalSupport website (http://support.huawei.com/). You can directly apply for a user ID and apassword. Log in to the website by entering the user ID and password, and then clickSoftware to search for the required manual.

6.1 Software Package UpgradeIn the case of the NE software upgrade, you can perform the software package upgrade toupgrade, activate, and manage the NE software in a centralized manner, and thus to simplify theoperations to upgrade the NE software.

6.2 Software Package DiffusionThe software package diffusion function provides an upgrade and maintenance method thatfeatures higher efficiency and simpler operation for the networkwide upgrade.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 6 Software Package Upgrade and Package Diffusion


6-1

6.1 Software Package UpgradeIn the case of the NE software upgrade, you can perform the software package upgrade toupgrade, activate, and manage the NE software in a centralized manner, and thus to simplify theoperations to upgrade the NE software.

6.1.1 Definition and FeatureIn the case of software package upgrade, the NE-level software is upgraded, activated andmanaged in a centralized manner. With the help of the software package upgrade, the processof upgrading software of an NE is simplified and the availability of upgrade operations isimproved. In addition, the system checks whether the board software versions match, andupdates the unmatched board software versions automatically.

6.1.2 State ModelThis section describes the state model of software package upgrade.

6.1.3 Realization SchemeThis section describes the flow for implementing the software package upgrade.

6.1.4 Creating a Package Upgrade TaskThis section describes the operations for upgrading the software package in details.

6.1.1 Definition and FeatureIn the case of software package upgrade, the NE-level software is upgraded, activated andmanaged in a centralized manner. With the help of the software package upgrade, the processof upgrading software of an NE is simplified and the availability of upgrade operations isimproved. In addition, the system checks whether the board software versions match, andupdates the unmatched board software versions automatically.

Software package upgrade has the following features:

l The object of software package upgrade is the NE. A uniform interface is available to loadthe software.

l The complete software package is stored on the CF card of the CXPR for upgrading theentire NE. The NE software files are stored on the target directory, and the board softwarefiles are buffered on the CF card. Hence, after a board is newly housed, the board softwareis automatically updated. If any board software file is lost, the CXPR restores the file.

l An NE can be automatically managed. The software of a newly housed board isautomatically updated if the software does not match the software in the software packagefor the NE.

l Software package upgrade is an incremental upgrade process in which only the new filesare updated.

Software package upgrade applies to the following scenarios:

l Upgrade of NE software

l Replacement of the CXPR board

6.1.2 State ModelThis section describes the state model of software package upgrade.

Figure 6-1 shows the state model of software package upgrade.

6 Software Package Upgrade and Package DiffusionOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

Figure 6-1 State model of software package upgrade

Whether activatingthe software succeeds

Whether dispensingthe software succeeds

The NE is in the normal state before the upgrade

Whether copying the software succeeds

The software is copied

The software is dispensed

The software is activated

The software is committed and the NE returns the normal state

Yes

Yes

Yes

No

No

Rollback

No

Start

End

Whether committingthe software succeeds

Yes

Handle the trouble and re-upgrade

No

The state model of software package upgrade is described as follows:

l Before the software package upgrade, the software should be in the normal state.

l After the files are copied, the software state changes from the normal state to the file copyending state. In this way, the software package is downloaded. For details on theimplementation, see Step 1 and Step 2 in 6.1.3 Realization Scheme.



6-3

l After the software is delivered, the software state changes from the file copy ending stateto the software delivery ending state. In this way, the software package is dispensed. Fordetails on the implementation, see Step 3 and Step 4 in 6.1.3 Realization Scheme.

l After the software is activated, the software state changes from the software delivery endingstate to the active state. In this way, the NE is activated. For details on the implementation,see Step 5, Step 6, and Step 7 in 6.1.3 Realization Scheme.

l After the software state changes from the active state to the normal state, the software issubmitted. For details on the implementation, see Step 8 and Step 9 in 6.1.3 RealizationScheme.

l If any problem occurs before the software package is submitted or after the operation foreach state is completed, perform the rollback operation to revert software to the normalstate. In this way, the software package is rolled back.

NOTE

The rollback operation means that all the board software files on the entire NE are restored to the originalstate if any problem occurs. The rollback operation cannot be performed after the software package issubmitted. After the rollback operation is performed, the NE is in the to-be-steady state. In this case, youcannot load the software package. Instead, you need to wait for some time to perform other operations untilthe system becomes steady.If you want to stop the upgrade of the software when delivery of the software is in process, you can manuallyperform rollback.

6.1.3 Realization SchemeThis section describes the flow for implementing the software package upgrade.

ContextFigure 6-2 shows the flow for upgrading a software package.

Figure 6-2 Flow diagram for software package upgrade

Software system of theprotection CXPR board

3

5

6

2

7

9

1

Software package server

T2000

8

Software systemof the workingCXPR board

单板单板Board softwaresystem

4

89

6

Software system of theworking CXPR board

1+1 protection switching

1+1 protection switching


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

Numbers 1~9 in Figure 6-2 indicate the steps in the main flow of upgrading the software package.

PrecautionsNOTE

During software package upgrade, services maybe interrupted. The upgrade time depends on the numberof NEs and boards. Normally, upgrading a software package for an NE takes five to ten minutes.

Procedure

Step 1 Start the package upgrade procedure on the T2000.

Step 2 The sub-system of the software on the system control board downloads the new software packagefrom the software package server.

Step 3 The standby system control board then updates its software package to keep consistent with theactive system control board. (If only one system control board is configured, skip this step.)

Step 4 The active system control board then loads the new software onto the boards that support thesoftware package upgrade and require updated software.

Step 5 Activate the standby system control board. (If only one system control board is configured, skipthis step.)

Step 6 Switching the active CXPR to the standby CXPR. (If only one system control board isconfigured, skip this step.)

Step 7 Activate all the boards.

Step 8 The standby CXPR and other boards are then required to replace the software stored in thebackup area with the software stored in the working area.

NOTE

The working area and backup area refer to the areas where the software package is stored on the board.

Step 9 The software backup is complete and the result is reported.

----End

6.1.4 Creating a Package Upgrade TaskThis section describes the operations for upgrading the software package in details.

Prerequisitel You must be a T2000 user with "NE and network operator" authority or higher and enter

the Main Topology.l Make sure that the active and standby CXPR boards are of the same type, and NE software

versions are consistent. Otherwise, the database cannot be synchronized and services aredelivered abnormally during the package upgrade. As a result, the package upgrade maybe rolled back. For details, see 8.3 Querying the Board Information Report.

l Make sure that the protection switching can be performed normally for boards configuredwith 1+1 protection switching.



6-5

l If an NE is configured with only one CXPR board, a cold reset on the CXPR board mayresult in an automatic cold reset of all the service boards. As a result, services areinterrupted. Thus, prepare a spare board during the upgrade.

l Before upgrading the software package, perform "Precheck" to check the NE health. Loadthe software package if all the items pass the check.

l You would better clear all the alarms of the NE, but the alarms in Table 6-1 must be cleared,because the alarms may cause service interruption or rollback of the package upgrade. Thealarms that cannot be cleared may affect the services during switching or reset. It isrecommended to request Huawei technical support engineers to confirm the impact.

Table 6-1 Alarms to be cleared before package upgrade

BUS_ERR DBMS_PROTECT_MODE POWER_ABNORMAL

CFCARD_FAILED FAN_FAIL SWDL_AUTOMATCH_INH

CFCARD_OFFLINE HARD_BAD SYNC_DISABLE

COMMUN_FAIL NESTATE_INSTALL SYNC_FAIL

DBMS_ERROR - -

Impact on the Systeml A cold reset on the CXPR not configured with any configuration may result in service

interruption.l If NEs, configured with protection, are upgraded on the same ring, activating them at the

same time may result in service interruption.l If NEs, not configured with any protection, are upgraded on the same ring, activating them

at the same time may result in service interruption.

Tools, Instruments, and MaterialsT2000 and software package for the upgrade


Maintenance Guide


Issue 02 (2009-06-30)

Precautions

CAUTIONl During the process of the data backup, software rollback, and software submission, the active/

standby switching for the CXPR boards should not be performed.l During the package upgrade, do not insert, remove any board, configure any service, and

reset any board by using commands. Otherwise, the loading fails and rollback occurs.l During the package upgrade, do not modify any configuration. Otherwise, rollback may occur

or the modified configuration is lost.l When the board loaded with software is in service, the board automatically matches the

loaded software. In this case, if you query the software version, the query result may showthat the software is of the original version. The version information is updated only after theboard finishes writing the flash and the resetting.

NOTE

In the following cases, perform other operations five minutes later.

l The active board is restarted after a reset.

l The active and standby boards are switched.

l Matched loading is performed for the active and standby boards, and the loading operation is complete.

l The rollback is complete.

l The software is submitted.

Procedure

Step 1 Select Data Center > Device Operation from the main menu to open the Device Operationtab. The device types are displayed in the device tree on the left.

Step 2 Select the device type to be operated in the device tree area and right-click in the Device Viewtab. Select New Task > Package Upgrade Task. The Task Management tab is displayedautomatically.



6-7

Step 3 Enter the task name in the displayed Create Task [Package Upgrade] dialog box, and selectdevice type, device version and devices to be operated separately from the Device Type drop-down list, the Device Version drop-down list and the device tree area. The information ofselected devices is displayed in the Device Table area. This step is performed to confirm thedevices to be operated.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l Task name can only contain alpha numeric characters and underscore line. It can have a maximum 20characters.

l Click , and the selected device type, device version, device names and IP addresses will bedisplayed in the device tree area.

l Click , and the physical location, device name and IP address of the selected device will bedisplayed in the device tree area.

l Click to import the device IP address from the selected location. In the Import dialog box, selectthe text file that contains the device IP address to be imported, and click Import. In the Importingdialog box, click Details to view the device name and the operation result of the device IP address tobe imported. The device and its imported IP address will be displayed in the device tree area.

l Select the device to be exported in the device tree area. Click to export the device IP address. Inthe Export dialog, select the location to export the device IP address and click Export. The selecteddevice IP address will be exported successfully at the selected location. The Operation Result dialogappears, click OK to close the Operation Result dialog.

l Click to delete the selected device(s) from the Device Table area.

Step 4 Click Next. After the displayed Validating upgrade mode of selected devices process bardisappears automatically, the Operation Configuration [Package Upgrade] dialog box isdisplayed. This step is performed to select and configure the operations of the package upgradetask.

1. Select the target version from the Target Version drop-down list to load the package fileto the selected target version.

2. Optional: Select the check box Start Time, and click to select the date and time forthe task to be executed. Task operation is performed for the selected operations at thescheduled start time.



6-9

3. Select the check box PreCheck, and click the link Configure PreCheck Items in theSelect Operation(s) area. The Configure Pre-Check Operation dialog box is displayed.Select the Check item and click OK to finish the configuration to PreCheck operation.

l If the Alarm check box is selected, T2000 checks the device alarm status.

l If the Health check box is selected, T2000 checks if the device is up and running ornot.

4. Select the check box Backup, and click the link Configure Backup Information. TheConfigure Backup Operation dialog box is displayed. Select the appropriate content typein the Content Type drop-down list and click OK to finish the configuration to Backupoperation.

NOTE

If you select Pause Before Current Operation check box, T2000 will pause before performing thisoperation until you start it manually.

5. Select the check box Load Software, and click the link Configure Package. Select thesoftware package file(s) to be loaded and click OK in the displayed Select Package File(s) dialog box.

6. Select the check box Dispense and the package file(s) can be loaded to different boards ona device at the same time. No configuration is required for the dispense operation.


Maintenance Guide


Issue 02 (2009-06-30)

7. Select the check box Activate, and Click the link Configure Activation. Select andconfigure the parameters in the displayed Configure Activation dialog box and then clickOK.

NOTE

The check box Pause Before Current Operation is selected by default, but the selection could becancelled.

NOTE

l If you select the check box Activation time, click to set the activate date and time, at whichthe Group1 of boards will be activated automatically.

l If the quantity of devices to be operated is more than 1, you can click to display a CreateNew Group dialog box. Thus, device(s) can be moved to a new group.

l If the quantity of groups is more than 1, you can click to delete the selected group. Thedevice(s) in the deleted group will move to the next group automatically.

l The device(s) in the same group can be activated at the same time. But the device(s) in differentgroups will be activated in order.

8. Select the check box Commit to clear the former software of device(s) and commit thenewly loaded software to device(s). No configuration is required for the commit operation.

9. Select the check box PostCheck, and click the link Configure PostCheck Items. TheConfigure Post-Check Operation dialog box is displayed. Select the Check item andclick OK to finish the configuration to PostCheck operation.

Step 5 Click Next to display the Confirmation [Package Upgrade] dialog box. Make sure theconfiguration of every operation is correct.



6-11

NOTE

You can click Previous to re-configure every operation.

Step 6 Click OK. The task will be added into Task Management tab automatically.

Step 7 In the Task Management tab, right-click the newly created task and click Start Task. ClickYes in the displayed Task Start Confirmation dialog box and the process of package upgradewill be displayed in the Operation Status area.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l The task will be moved to Running automatically since started and will be moved to Completedautomatically when the task is finished.

l Right--click the task and click Delete Task to delete the task.

l If you select Pause Before Current Operation check box, T2000 will pause before performing thisoperation until you perform step 7 to start it manually.

l When the package upgrade task is finished or any operation fails, you can right-click the task and selectView Check Reports to check the details.

----End

Related Information

The problems that commonly occur during the package loading and their solutions are as follows:

l The submission of the software fails and the SWDL_COMMIT_FAIL alarm is reported.To solve this problem, handle SWDL_COMMIT_FAIL alarm, wait a while after the NEis activated and then submit the software.

l After rollback, the boards cannot start normally. To solve this problem, perform thefollowing operations:

– Check whether the SWDL_ROLLBACK_FAIL alarm is reported and handleSWDL_ROLLBACK_FAIL alarm.

– Check whether the SWDL_PKG_NOBDSOFT alarm is reported and handleSWDL_PKG_NOBDSOFT alarm.

6.2 Software Package DiffusionThe software package diffusion function provides an upgrade and maintenance method thatfeatures higher efficiency and simpler operation for the networkwide upgrade.

6.2.1 Definition and FeatureIn the case of package diffusion, the software package is diffused among NEs which then try toload the software package at the same time. In this way, the efficiency in software packageupgrade is highly increased, and less manual interference and fewer operations are reducedduring this process.

6.2.2 State ModelThis section describes the running state model for package diffusion inside an NE.

6.2.3 Realization SchemeCertain rules should be observed when using the software package diffusion technology.

6.2.4 Creating a Package Diffusion Upgrade TaskThis section describes how to upgrade the software package by means of diffusion.

6.2.1 Definition and FeatureIn the case of package diffusion, the software package is diffused among NEs which then try toload the software package at the same time. In this way, the efficiency in software packageupgrade is highly increased, and less manual interference and fewer operations are reducedduring this process.



6-13

The software package is diffused layer by layer. In this way, several NEs can load the softwarepackage simultaneously to balance the network load and to use the network bandwidth equally.This is the main feature of the package diffusion.

The package diffusion is applicable to all networking environment.

6.2.2 State ModelThis section describes the running state model for package diffusion inside an NE.

Background InformationAs a method of diffusing the software package in a network, the package diffusion is responsibleonly for loading and upgrading the software package between NEs in the network.

6.1.2 State Model shows the state model of software package upgrade.

State Model of Software Package DiffusionFigure 6-3 shows the state model for software package diffusion inside an NE.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 6-3 State model for package diffusion

NE is in the normal status

Initialization state

Pending state

Settinginformationsucceeds?

Transmission state

Completion state

Yes

Suspension state

Start

Downstream node exists?

Data is diffused to the downstream nodes

No

No

Receives software-ready

information?

Are files and data prepared on the

upstream node?

Receivingsoftware

succeeds?

Yes

Yes

Yes

Yes

No

No

No

Package upgrade

End

All the NEs are in completion state

The state model for package diffusion is described as follows.



6-15

l Normal state. No diffusion information is set on the node, or the diffusion is completed.

l Initialization state. Diffusion information is successfully set on the NE. This state isessential for later diffusion.

NOTE

l The source node receives the information, indicating that the files are ready, from the applicationmodule.

l A node rather than the source node receives the information, indicating that the files are ready,from the upstream node.

l Pending state. The local node is waiting for file data from the upstream node.

l Transmission state. The local node is receiving file data from the upstream node.

l Completion state. In this state, the local node waits until the diffusion on the downstreamnode is completed.

l Suspension state. In this state, the local node informs the upstream and downstream nodesof updating diffusion information.

6.2.3 Realization SchemeCertain rules should be observed when using the software package diffusion technology.

Precautions

Observe the following rules when using the software package diffusion technology.

l The diffusion network should not contain any NE of the type that is not supported by thesoftware package for diffusion.

l On all NEs involved in the diffusion, the FLASH on the CXPR board should have sufficientspace for the software package, and the file system in the memory can hold the file of themaximum size in the software package.

l All NEs involved in the package diffusion must be in the same diffusion network and thecommunication between every two NEs must be available.

l In one diffusion network, only one software package can be diffused at a time.

l Only one source node is present in a diffusion network. Except the source node, each nodeshould have a maximum of one upstream node. One upstream node should not repeat anydownstream node. Downstream nodes should not repeat each other.

l In a diffusion network, the quantity of nodes allowed is 100.

6.2.4 Creating a Package Diffusion Upgrade TaskThis section describes how to upgrade the software package by means of diffusion.

Prerequisitel You must be a T2000 user with "NE and network operator" authority or higher and enter

the Main Topology.l The target NEs and the gateway NE for them must be created and logged into. The T2000

server can normally communicate with NEs.l At least two target NEs supporting the package diffusion must be present. NEs in the same

diffusion group to be created must be of the same type and no diffusion group is created.


Maintenance Guide


Issue 02 (2009-06-30)

l Make sure that the active and standby CXPR boards are of the same type, and NE softwareversions are consistent. Otherwise, the database cannot be synchronized and services aredelivered abnormally during the package upgrade. As a result, the package upgrade maybe rolled back. For details, see 8.3 Querying the Board Information Report.

l Make sure that the protection switching can be performed normally for boards configuredwith 1+1 protection switching.

l If an NE is configured with only one CXPR board, a cold reset on the CXPR board mayresult in an automatic cold reset of all the service boards. As a result, services areinterrupted. Thus, prepare a spare board during the upgrade.

l Before upgrading the software package, perform "Precheck" to check the NE health. Loadthe software package if all the items pass the check.

l You would better clear all the alarms of the NE, but the alarms in Table 6-2 must be cleared,because the alarms may cause service interruption or rollback of the package upgrade. Thealarms that cannot be cleared may affect the services during switching or reset. It isrecommended to request Huawei technical support engineers to confirm the impact.

Table 6-2 Alarms to be cleared before package diffusion upgrade

BUS_ERR DBMS_PROTECT_MODE POWER_ABNORMAL

CFCARD_FAILED FAN_FAIL SWDL_AUTOMATCH_INH

CFCARD_OFFLINE HARD_BAD SYNC_DISABLE

COMMUN_FAIL NESTATE_INSTALL SYNC_FAIL

DBMS_ERROR - -

Impact on the Systeml A cold reset on the CXPR not configured with any configuration may result in service

interruption.l If NEs, configured with protection, are upgraded on the same ring, activating them at the

same time may result in service interruption.l If NEs, not configured with any protection, are upgraded on the same ring, activating them

at the same time may result in service interruption.

Tools, Instruments, and MaterialsT2000 and software package for the upgrade



6-17

Precautions

CAUTIONl When performing the package diffusion upgrade operation, the minimum number of NEs is

2. If there is only one NE, refer to 6.1.4 Creating a Package Upgrade Task.l During the process of the data backup, software rollback, and software submission, the active/

standby switching for the CXPR boards should not be performed.l During the package diffusion upgrade, do not insert, remove any board, configure any service,

and reset any board by using commands. Otherwise, the loading fails and rollback occurs.l During the package diffusion upgrade, do not modify any configuration. Otherwise, rollback

may occur or the modified configuration is lost.l When the board loaded with software is in service, the board automatically matches the

loaded software. In this case, if you query the software version, the query result may showthat the software is of the original version. The version information is updated only after theboard finishes writing the flash and the resetting.

NOTE

In the following cases, perform other operations five minutes later.

l The working board restarts after resetting.

l The active and standby boards are switched.

l Matched loading is performed for the active and standby boards, and the loading operation is complete.

l The rollback is completed.

l The software is submitted.

Procedure

Step 1 Select Data Center > Device Operation from the main menu to open the Device Operationtab. The device types are displayed in the device tree on the left.

Step 2 Select the device type to be operated in the device tree area and right-click in the Device Viewtab. Select New Task > Package Diffusion Upgrade Task. The Task Management tab isdisplayed automatically.


Maintenance Guide


Issue 02 (2009-06-30)

Step 3 Enter the task name and select the activation level in the displayed Create Task [PackageDiffusion Upgrade] dialog box. Select device type, device version and devices to be operatedseparately from the Device Type drop-down list, the Device Version drop-down list and thedevice tree area. The information of selected devices is displayed in the Device Table area. Thisstep is performed to confirm the devices to be operated.



6-19

NOTE

l Task name can only contain alpha numeric characters and underscore line. It can have a maximum 20characters.

l You can select Device or Board from the Activation Level drop-down list. If Board is selected, youcan get default activation groups

l Click , and the selected device type, device version, device names and IP addresses will bedisplayed in the device tree area.

l Click , and the physical location, device name and IP address of the selected device will bedisplayed in the device tree area.

l Click to import the device IP address from the selected location. In the Import dialog box, selectthe text file that contains the device IP address to be imported, and click Import. In the Importingdialog box, click Details to view the device name and the operation result of the device IP address tobe imported. The device and its imported IP address will be displayed in the device tree area.

l Select the device to be exported in the device tree area. Click to export the device IP address. Inthe Export dialog, select the location to export the device IP address and click Export. The selecteddevice IP address will be exported successfully at the selected location. The Operation Result dialogappears, click OK to close the Operation Result dialog.

l Click to delete the selected device(s) from the Device Table area.

Step 4 Click Next. After the displayed Validating upgrade mode of selected devices process bardisappears automatically, the Operation Configuration [Package Diffusion Upgrade] dialogbox is displayed. This step is performed to select and configure the operations of the packagediffusion upgrade task.

1. Optional: Select the target version from the Target Version drop-down list to load thepackage file to the selected target version.


Maintenance Guide


Issue 02 (2009-06-30)

2. Optional: Select the check box Start Time, and click to select the date and time forthe task to be executed. Task operation is performed for the selected operations at thescheduled start time.

3. Select the check box PreCheck, and click the link Configure PreCheck Items in theSelect Operation(s) area. The Configure Pre-Check Operation dialog box is displayed.Select the Check item and click OK to finish the configuration to PreCheck operation.

l If the Alarm check box is selected, T2000 checks the device alarm status.

l If the Health check box is selected, T2000 checks if the device is up and running ornot.

4. Select the check box Backup, and click the link Configure Backup Information. TheConfigure Backup Operation dialog box is displayed. Select the appropriate content typein the Content Type drop-down list and click OK to finish the configuration to Backupoperation.

NOTE

If you select Pause Before Current Operation check box, T2000 will pause before performing thisoperation until you start it manually.

5. Select the check box Load Software, and click the link Configure Package. Select thesoftware package file(s) to be loaded and click OK in the displayed Select Package File(s) dialog box.



6-21

6. Select the check box Dispense and the package file(s) can be loaded to different boards ona device at the same time. No configuration is required for the dispense operation.

NOTE

The dispense operation will be started only after the T2000 detected the software package has alreadybeen loaded to all the NEs to avoid the anomalies occurring in the expanding process.

7. Select the check box Activate, and click the link Configure Activation. Select andconfigure the parameters in the displayed Configure Activation dialog box and then clickOK.

NOTE

The check box Pause Before Current Operation is selected by default, but the selection could becancelled.

l If you select Device in the Activation Level drop-down list in Step 3, the ConfigureActivation dialog box will be as below.

NOTE

l If you select the check box Activation time, click to set the activate date and time, atwhich the Group1 of boards will be activated automatically.

l Click to display a Create New Group dialog box. Thus, device(s) can be moved to anew group.


l The device(s) in the same group can be activated at the same time. But the device(s) indifferent groups will be activated in order.

l If you select Board in the Activation Level drop-down list in Step 3, the ConfigureActivation dialog box will be as below.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l If you select the check box Activation time, click to set the activate date and time, atwhich the Group1 of boards will be activated automatically.

l Select the check box Select Files, and click . You can import the text file which containsboard information that can be used for grouping the board(s) in the displayed SelectSoftware dialog box.

l Click Get Default Activation Group, and click Close in the displayed process bar.

l Click to display a Create New Group dialog box. Thus, device(s) can be moved to anew group.


l The device(s) in the same group can be activated at the same time. But the device(s) indifferent groups will be activated in order.

l The default group cannot be deleted.

8. Select the check box Commit to clear the former software of device(s) and commit thenewly loaded software to device(s). No configuration is required for the commit operation.

9. Select the check box PostCheck, and click the link Configure PostCheck Items. TheConfigure Post-Check Operation dialog box is displayed. Select the Check item andclick OK to finish the configuration to PostCheck operation.

Step 5 Click Next to display the Confirmation [Package Diffusion Upgrade] dialog box. Make surethe configuration of every operation is correct.



6-23

NOTE

You can click Previous to re-configure every operation.

Step 6 Click OK. The task will be added into Task Management tab automatically.

Step 7 In the Task Management tab, right click the newly created task and click Start Task. ClickYes in the displayed Task Start Confirmation dialog box and the process of package upgradewill be displayed in the Operation Status area.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l The task will be moved to Running automatically since started and will be moved to Completedautomatically when the task is finished.

l Right-click the task and click Delete Task to delete the task.

l If you select Pause Before Current Operation check box, T2000 will pause before performing thisoperation until you perform step 7 to start it manually.

l When the package upgrade task is finished or any operation fails, you can right-click the task and selectView Check Reports to check the details.

----End

Related InformationThe problems that commonly occur during the package loading and their solutions are as follows:l The submission of the software fails and the SWDL_COMMIT_FAIL alarm is reported.

To solve this problem, handle SWDL_COMMIT_FAIL alarm, wait a while after the NEis activated and then submit the software.

l After rollback, the boards cannot start normally. To solve this problem, perform thefollowing operations:– Check whether the SWDL_ROLLBACK_FAIL alarm is reported and handle

SWDL_ROLLBACK_FAIL alarm.– Check whether the SWDL_PKG_NOBDSOFT alarm is reported and handle

SWDL_PKG_NOBDSOFT alarm.



6-25

7 Remote Maintenance Guide

About This Chapter

Remote maintenance guide the user how to enabling the remote maintenance user andestablishing the remote maintenance.

7.1 IntroduceSummarizes how to perform the remote maitenance.

7.2 Enabling a Remote Maintenance UserA remote maintenance user is a network management user who logs in to the T2000 server ona remote maintenance client. By default, the remote maintenance user is "Disabled". Hence,enable the remote maintenance user before starting the remote maintenance.

7.3 Establishing Remote MaintenanceThis section describes how the T2000 server establishes remote maintenance connection withthe remote terminal.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 7 Remote Maintenance Guide


7-1

7.1 IntroduceSummarizes how to perform the remote maitenance.

A remote computer (remote end) can connect to the T2000 server on site (local end) through thepublic switched telephone network (PSTN) or the Internet. The remote computer then canperform in-time maintenance to the equipment.

Figure 7-1 shows a connection for remote maintenance. A modem should be installed at eachof the remote maintenance terminal and the T2000 server. The dial-up connection programshould be set. The hardware and software should be configured before the T2000 is installed.

Connection for remote maintenance

Figure 7-1 Connection for remote maintenance

Remotemaintenance

terminal T2000server

Modem

PSTN/Internet

Modem

Serial port

Opticalnetwork

Serial port

When you use the remote maintenance function to maintain the equipment, the T2000 shouldperform the following operations in cooperation with the remote end.

l Enabling an remote maintenance userl Establishing remote maintenance

7.2 Enabling a Remote Maintenance UserA remote maintenance user is a network management user who logs in to the T2000 server ona remote maintenance client. By default, the remote maintenance user is "Disabled". Hence,enable the remote maintenance user before starting the remote maintenance.

7 Remote Maintenance GuideOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

PrerequisiteThe operator must have the "NM administrator" authority or higher.

Procedure

Step 1 Choose System > Remote Maintenance User Management from the Main Menu. The RemoteMaintenance User Management dialog box is displayed.

Step 2 In the dialog box, set the Enable/Disable parameter to Enable. Set other attributes of the remotemaintenance user.

Step 3 Click Apply and click Close in the displayed Operation Result dialog box.

Step 4 Click OK and click Close in the displayed Operation Result dialog box to finish the task.

----End

7.3 Establishing Remote MaintenanceThis section describes how the T2000 server establishes remote maintenance connection withthe remote terminal.



7-3

Prerequisitel The communication connection between the remote maintenance terminal and the T2000

server must have been configured.

l The remote maintenance user must have been enabled.

l The shortcut icon of the dial-up connection has already been created on the desktop, forexample, Remote Maintenance.

l The dial-up telephone number, user name and password of the T2000 server must be knownto maintenance personnel at the remote maintenance terminal.

Context

CAUTIONTo ensure network security, set the Enable/Disable parameter of the remote maintenance userto Disable after the remote maintenance.

Procedure

Step 1 On the T2000 server, query the status of the remote maintenance connection. If the remotemaintenance connection is established, go to Step 5. If not established, go to Step 2. The querymethods are listed as follows.

l If the Windows operating system is installed, right-click Network Neighbor and click theAttribute tab to query the status of the remote maintenance connection.

l If the Sun workstation is installed, open a terminal window and run the ifconfig -a commandto query the status of the remote maintenance connection.

Step 2 Double-click the shortcut icon of the dial-up connection on the desktop, for example, RemoteMaintenance, to dial up.

Step 3 Enter the user name(ppp_user) and password in the displayed dialog box.

Step 4 Enter the user name and password. Press the Enter key and click the D button in the lower rightcorner to establish the connection.

NOTE

After you enter the password and press the Enter key, a line of junk characters are displayed. This is normal.

Step 5 Query the IP address for dial-up access to network.

l If the Windows operating system is installed, choose Start > All Programs >Attachment > Command Prompt to display the Command Prompt window. Enter ipconfig-a in the dialog box and query the dynamic IP address for dial-up access to network.

l If the Sun workstation is installed, display a terminal window and run the ipconfig -acommand to query dynamic IP address for dial-up access to network.

Step 6 Inform the maintenance personnel at the remote end of the queried IP address.

7 Remote Maintenance GuideOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

Step 7 The remote maintenance user dials up the T2000 server and logs in to the T2000 client. Afterthe login succeeds, you can perform the remote maintenance.

----End



7-5

8 Task Set

About This Chapter

Common operation tasks include the operations performed by using the T2000 and the operationsperformed on site. Learning how to perform these operations helps quickly locate and rectifyfaults during the equipment maintenance.

8.1 Querying T2000 Operation LogsTo detect the illegal operations, you should check operation logs on the T2000 periodically.

8.2 Querying Current Alarms of a BoardPeriodically querying alarms helps detecting and rectifying a fault in time. This section describesthe prerequisites and procedures for querying the current alarms of a board by using the T2000.

8.3 Querying the Board Information ReportThis section describes how to query the board information report. The board informationincludes the board type, status, software version and so on.

8.4 Checking the Optical PowerWhen the receive or transmitted optical power of an optical interface is abnormal, bit errorsmaybe generated and the optical components may be damaged. This section describes theprerequisites and procedures for querying the board optical power by using the T2000.

8.5 Performing the LSP Ping TestYou can perform the LSP ping test to check the connectivity of the tunnel. This section describesthe prerequisites and procedures for performing the LSP ping test by using the T2000.

8.6 Performing the LSP Traceroute TestYou can perform the LSP Traceroute test to locate a fault. This section describes the prerequisitesand procedures for performing the LSP Traceroute test by using the T2000.

8.7 Checking Data Consistency Between an NE and the T2000By performing the data consistency check between an NE and the T2000, you can compare thedata configuration on the T2000 with the configuration data on the NE and then obtain a reporton the result of the consistency check. Perform the consistency check for all the NEs monthlyso that the T2000 can manage the NEs properly.

8.8 Uploading the NE Configuration Data

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 8 Task Set


8-1

The NE configuration data on the T2000 may be inconsistent with that on the NE. Duringmaintenance, you need to keep the data consistent on the T2000 and the NE. If the network runsnormally and the data on the NE is correct, upload the data from the NE to the T2000.

8.9 Configuring Port LoopbackThe port loopback configuration is usually changed for locating equipment faults. By changingthe loopback mode, you can locate the fault.

8.10 Performing the MPLS Tunnel Protection SwitchingYou can perform the MPLS tunnel protection switching on the T2000 to realize the switchingof services between different MPLS tunnels.

8.11 Performing the 1+1 Protection Switching for CXPR boardsYou can perform the 1+1 protection switching for CXPR boards on the T2000 to realize theswitching of status between two CXPR boards.

8.12 Performing IF 1+1 Protection SwitchThe IF 1+1 protection switching is an important maintenance operation.

8.13 Querying an IF 1+1 Protection GroupYou can know the current status of an 1+1 protection group by querying the IF 1+1 protectiongroup.

8.14 Querying the Working State of AMYou can know the change of the AM mode by querying the working state of AM.

8.15 Setting the State of an ODU Transmitterthe state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in theunmute state, the ODU transmits and receives microwave signals normally. When the ODUtransmitter is in the mute state, the ODU transmitter does not work, but the ODU can receivesmicrowave signals.

8.16 Resetting BoardsIn the case of resetting boards, the board software is reset. The board reset is classified into warmreset and cold reset. The warm reset does not affect running services. The cold reset, however,usually affects the running services.

8.17 Testing the Transmitted Optical Power of the Optical InterfaceIf the mean transmitted optical power is excessively high or low, bit errors occur on theequipment. The bit errors affect services and even damage components on the equipment. Thissection describes how to test the transmitted optical power at optical interfaces of the equipmenton site to ensure that the mean transmitted optical power of each optical interface is normal.

8.18 Testing the Receive Optical Power of the Optical InterfaceIf the receive optical power is excessively high or low, bit errors occur on the equipment. Thebit errors affect the services or even damage components on the equipment. This sectiondescribes how to test the receive optical power at optical interfaces of the equipment on site toensure that the receive optical power of each optical interface is normal.

8.19 Replacing Boards on SiteWhen replacing a board, remove and insert it as required; make sure that the mapping relationsbetween the interfaces and cables are not changed before and after the replacement; observeindicators to determine the running state of the board.

8.20 Powering On the EquipmentThis section describes how to connect the power supply to the equipment to ensure that theequipment can be powered on normally.

8.21 Powering Off the Equipment

8 Task SetOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

This section describes how to power off the equipment.

8.22 Querying and Setting the Working Mode of Ethernet InterfaceThis section describes how to query and set the working mode of Ethernet interface.

8.23 Querying Protection ConfigurationThis section describes the basic method for querying the protection scheme that is configuredin the equipment when a fault or service interruption occurs.

8.24 Inspecting and Cleaning the Optical Fiber ConnectorsCleaning optical components is to remove dust or other dirt to avoid performance degradationof optical transmission systems. Inspecting and cleaning fiber connectors used in fiber opticconnections are introduced here.



8-3

8.1 Querying T2000 Operation LogsTo detect the illegal operations, you should check operation logs on the T2000 periodically.

Prerequisitel The T2000 user must log in to the T2000 and enter the Main Topology.

l You must be a T2000 user with "NM Administrator" authority or higher.

Procedure

Step 1 Choose System > Browse NMS Log from the Main Menu. The Browse Log tab is displayed.

Step 2 Click Filter. Configure the appropriate parameters in the displayed Filter dialog box and clickOK.

Step 3 Optional: Click Refresh to check the logs.

Step 4 Make sure that no illegal operations such as abnormal or malicious operations and illegal loginsare recorded in the logs.

CAUTIONIf there are illegal operations recorded in the logs, you need to set the operation authority andmanagement authority again. For details, see "Security Management" of the OptiX iManagerT2000 Operation Guide for RTN NE Management.

----End

8.2 Querying Current Alarms of a BoardPeriodically querying alarms helps detecting and rectifying a fault in time. This section describesthe prerequisites and procedures for querying the current alarms of a board by using the T2000.


l You must be a T2000 user with "NE and Network Monitor" authority or higher.

Procedure

Step 1 Right-click the target NE icon in the Main Topology of the T2000. Choose Fault > BrowseCurrent Alarms to display the Browse Current Alarms window.


Maintenance Guide


Issue 02 (2009-06-30)

Step 2 Click Synchronize. The Operation Progress dialog box is displayed indicating thesynchronization progress.

NOTE

To stop the query, you can click Cancel.

Step 3 After the alarm query is complete, the Operation Result dialog box is displayed. Click Close.

Step 4 Record and confirm new alarms of the NE.

----End

8.3 Querying the Board Information ReportThis section describes how to query the board information report. The board informationincludes the board type, status, software version and so on.

Prerequisitel The T2000 user must log in to the T2000 and enter the Main Topology.l You must be a T2000 user with "NE and Network Operator" authority or higher.l The board must be created.

ProcedureStep 1 Choose Report > Board Information Report from the Main Menu.

Step 2 In the Object Tree, select an NE or a board on the NE and click .



8-5

Step 3 Click Query and the Query progress bar display.

NOTE

You can click Cancel and click Yes in the displayed Confirm dialog box to cancel the querying.

Step 4 Click the Board Information Report tab and view the board information.

NOTE

l Commonly, the software version of each board should be of the same version.

l You can double-click the Remarks field and enter the information. Then, click Apply to save theinformation.

Step 5 Optional: Click Print or Save As to export the report.

----End

8.4 Checking the Optical PowerWhen the receive or transmitted optical power of an optical interface is abnormal, bit errorsmaybe generated and the optical components may be damaged. This section describes theprerequisites and procedures for querying the board optical power by using the T2000.



l The performance monitoring function must be enabled and the parameters for this functionmust be set.

NOTE

For details on how to enable the performance monitoring function and how to set the parameters forthis function, see the relevant chapter about the performance management in the OptiX iManagerT2000 Operation Guide for RTN NE Management.


Checking CriteriaFor the technical specifications of the mean transmitted optical power and receive optical powerof different optical interfaces, refer to Technical Specifications of Boards in the OptiX RTN950 Radio Transmission System Product Description manual.

Procedure

Step 1 Select and right-click the target NE. Choose NE Explorer.

Step 2 Select the board installed with optical interface from the left-hand side of the NE Explorerwindow. Then, choose Performance > Current Performance from the Function Tree.

Step 3 In Performance Event Type, select Transmitted Optical Power and Receive OpticalPower. Then, click Query.


Maintenance Guide


Issue 02 (2009-06-30)

Step 4 Click OK in the displayed Operation Result dialog box to complete the querying operation.NOTE

If the query is stopped or fails, the Operation Result dialog box, indicating that the operation is partiallysuccessful, is displayed. Then, you can perform the following operations:

l Click Detail to check detailed information about the operation object, the operation result, and thecause.

l Click Save As to save the detailed information as a file.

Step 5 Check whether the performance values of Transmitted Optical Power and Receive OpticalPower are within the normal range.

Step 6 If the performance values of the laser are beyond the specified range, handle the situationaccording to 3.1 General Fault Handling Flow.

----End

8.5 Performing the LSP Ping TestYou can perform the LSP ping test to check the connectivity of the tunnel. This section describesthe prerequisites and procedures for performing the LSP ping test by using the T2000.



l An MPLS tunnel must be created.

ProcedureStep 1 Select and right-click the target NE. Choose NE Explorer.

Step 2 Click NEs from the left side of the NE Explorer window. Choose Configuration > MPLSManagement > Unicast Tunnel Management from the Function Tree.

Step 3 Click the OAM Parameters tab, and then select a tunnel.NOTE

When the Node Type of the tunnel is Ingress, you can perform the Ping test.

Step 4 Click OAM Operation, and then select Ping Test.

Step 5 In the displayed Ping Test dialog box, configure the corresponding parameters in the right-handValue pane.



8-7

Step 6 Click Start Test to start the test.

NOTE

To stop the test, you can click Stop Test.

Step 7 Determine the connectivity of the tunnel according to the test result displayed in the lower TestResult pane.

NOTE

If the contents of prerequisite are not conformed, the Operation Result dialog box will be displayed toshow the hint information.

----End

8.6 Performing the LSP Traceroute TestYou can perform the LSP Traceroute test to locate a fault. This section describes the prerequisitesand procedures for performing the LSP Traceroute test by using the T2000.


Maintenance Guide


Issue 02 (2009-06-30)



l An MPLS tunnel must be created.

Procedure


Step 2 Click NEs from the left side of the NE Explorer window. Choose Configuration > MPLSManagement > Unicast Tunnel Management from the Function Tree.

Step 3 Click the OAM Parameters tab, and then select a tunnel.

NOTE

When the Node Type of the tunnel is Ingress, you can perform the traceroute test.

Step 4 Click OAM Operation, and then select Traceroute Test.

Step 5 In the displayed Traceroute Test dialog box, configure the corresponding parameters in theright-hand Value pane.



8-9

Step 6 Click Start Test to start the test.

NOTE

To stop the test, you can click Stop Test.

Step 7 Determine whether the tunnel is faulty according to the test result displayed in the lower TestResult pane.

NOTE

If the contents of prerequisite are not conformed, the Operation Result dialog box will be displayed toshow the hint information.

----End

8.7 Checking Data Consistency Between an NE and theT2000

By performing the data consistency check between an NE and the T2000, you can compare thedata configuration on the T2000 with the configuration data on the NE and then obtain a report


Maintenance Guide


Issue 02 (2009-06-30)

on the result of the consistency check. Perform the consistency check for all the NEs monthlyso that the T2000 can manage the NEs properly.



Reference Standard

The operation result indicates that the data configuration on the NE is consistent with the dataconfiguration on the T2000.

Precautions

Checking data consistency between an NE and the T2000 does not affect the data configurationon the NE and the T2000.

Procedure


Step 2 Select the target NE from the left-hand Object Tree, and then click .

Step 3 Select one or more NEs from the Configuration Data Management List.

Step 4 Click Consistency Check, or right-click the NE or NEs to choose Consistency Check from theshortcut menu.

Step 5 Click OK in the displayed Confirm dialog box. Then, a progress bar is displayed indicating theoperation progress.

NOTE

To stop the consistency check, you can click Cancel.

Step 6 The Operation Result dialog box, indicating that the operation is successful, is displayed. ClickClose.

NOTE

If the uploading is stopped or the operation fails, the Operation Result dialog box, indicating that theoperation is partially successful, is displayed. Then, you can perform the following operations:



----End

8.8 Uploading the NE Configuration DataThe NE configuration data on the T2000 may be inconsistent with that on the NE. Duringmaintenance, you need to keep the data consistent on the T2000 and the NE. If the network runsnormally and the data on the NE is correct, upload the data from the NE to the T2000.



8-11



PrecautionsAfter uploading the data, you need to check whether the data is consistent. For details, see 8.7Checking Data Consistency Between an NE and the T2000.

Procedure


Step 2 Select the target NE from the left-hand Object Tree, and then click .

Step 3 Select one or more NEs from the Configuration Data Management List.

Step 4 Click Upload, or right-click the NE or NEs to choose Upload from the shortcut menu.

Step 5 Click OK in the displayed Confirm dialog box to start the uploading. Then, a progress bar isdisplayed in the Upload window to indicate the operation progress.

NOTE

To stop the uploading, you can click Cancel.

Step 6 The Operation Result dialog box, indicating that the operation is successful, is displayed. ClickClose.

NOTE

If the uploading is stopped or the operation fails, the Operation Result dialog box, indicating that theoperation is partially successful, is displayed. Then, you can perform the following operations:



----End

8.9 Configuring Port LoopbackThe port loopback configuration is usually changed for locating equipment faults. By changingthe loopback mode, you can locate the fault.




Maintenance Guide


Issue 02 (2009-06-30)

Context

Loopback Description

Non-Loopback Indicates the normal status. When the equipment is operating normally,loopback is not required.

Inloop At the local equipment, the outgoing services of an port are looped backand input to this port.

Outloop At the local equipment, the incoming services of an port are looped backand output to this port.

Procedure


Step 2 Select the target port in the NE Explorer.

Interface Configuration Entry

PDHinterface

1. Choose Configuration > Interface Management > PDH Interface fromthe Function Tree.

2. In the Advanced Attributes tab, select the target port.3. Double-click the relevant Loopback Mode parameter. You can choose

Non-Loopback, Inloop or Outloop from the drop-down list.

Ethernetinterface

1. Choose Configuration > Interface Management > Ethernet Interfacefrom the Function Tree.

2. In the Advanced Attributes tab, select the target port.3. Double-click the relevant MAC Loopback parameter. You can choose

Non-Loopback, Inloop or Outloop from the drop-down list.4. Double-click the relevant PHY Loopback parameter. You can choose

Non-Loopback or Inloop from the drop-down list.

Microwaveinterface

1. Choose Configuration > Interface Management > MicrowaveInterface from the Function Tree.

2. In the Advanced Attributes tab, select the target port.3. Double-click the relevant IF Port Loopback parameter. You can choose

Non-Loopback, Inloop or Outloop from the drop-down list.4. Double-click the relevant Composite Port Loopback parameter. You can

choose Non-Loopback, Inloop or Outloop from the drop-down list.

ATM IMAport

1. Choose Configuration > Interface Management > ATM IMAManagement from the Function Tree.

2. In the ATM Interface Management tab, select the target port.3. Double-click the relevant Loopback parameter. You can choose Non-

Loopback, Inloop or Outloop from the drop-down list.



8-13

Step 3 Select the appropriate loopback mode and click Apply. Then, the current loopback mode of theport is modified.

CAUTIONThe loopback may cause service interruption. After the loopback is set on the port for fiveminutes, the port will return to the Non-Loopback status automatically.

NOTE

Step 4 Optional: Click Query to query the loopback status of the port.

----End

8.10 Performing the MPLS Tunnel Protection SwitchingYou can perform the MPLS tunnel protection switching on the T2000 to realize the switchingof services between different MPLS tunnels.



Background InformationProtection switching includes forced switching, manual switching, and exercise switching.

l In the case of forced switching, the state of the protection channel is not considered, unlessthe protection channel is responding to the bridge request of a higher priority. When theautomatic switching fails due to some reason, the forced switching can be performed torestore the services.

l Commands for manual switching are valid only when there is no signal failure or signaldegradation on the protection tunnel. In the case of manual switching, services can bemanually switched to a working or protection tunnel.

l The exercise switching is used to test the APS protocol. In fact, the services are not switched,and only the computation result of the protocol is displayed.

NOTE

In the case of locked switching, services in the tunnel are not switched when they should be switched. Theservices, however, can be restored when they should be restored.

Procedure

Step 1 Select the source NE of the tunnel in the Main Topology of the T2000. Right-click the NE tochoose NE Explorer.

Step 2 Choose Configuration > APS Protection Management from the Function Tree.

Step 3 Click Query, and then select the protection group to be switched.


Maintenance Guide


Issue 02 (2009-06-30)

Step 4 Click Function in the lower-right area, and then select the target switching operation in thedisplayed menu.

Step 5 In the Confirmation dialog box, click OK.

Step 6 The Operation Result dialog box is displayed. ClickClose. The protection switching iscomplete.

----End

8.11 Performing the 1+1 Protection Switching for CXPRboards

You can perform the 1+1 protection switching for CXPR boards on the T2000 to realize theswitching of status between two CXPR boards.

Prerequisitel You must be a T2000 user with "NE and network operator" authority or higher.

l The 1+1 board protection group must be available.

l The protection board must be working normally.

Background Information

Board 1+1 protection switching includes working/protection switching, and restore working/protection.

l Working/protection switching is performed to change the protection status in the protectiongroup, when the slot and the board name of Active Board are the same as that of WorkingBoard.

l Restore working/protection is performed to cancel the protection switching and return tothe initial protection status, when the slot and the board name of Active Board are the sameas that of Protection Board.

Impact on System

Performing the 1+1 Protection Switching for CXPR boards does not affect services when theswitching is normally performed.



8-15

If the protection board is abnormal, the services may be interrupted when you perform theswitching.

Procedurel Working/protection switching.

1. Select an NE in the Main Topology of the T2000. Right-click the NE to choose NEExplorer.

2. Choose Configuration > Board 1+1 Protection from the Function Tree.

3. In the 1+1 Protection List tab, select SCC Protection Pair of the NE. ClickWorking/Protection Switching.

4. Click OK in the displayed Confirm dialog box. In the displayed Operation Resultdialog box, click Close.

5. Click Query. In the displayed Operation Result dialog box, click Close. If the slotand the board name of Protection Board are displayed in Active Board, it indicatesthat the 1+1 protection switching is complete.

6. Query the alarms and performance events on the T2000. If new alarms andperformance events do not occur and services are normal, it indicates that the switchingis successful.

l Restore working/protection.

1. Select an NE in the Main Topology of the T2000. Right-click the NE to choose NEExplorer.

2. Choose Configuration > Board 1+1 Protection from the Function Tree.

3. In the 1+1 Protection List tab, select SCC Protection Pair of the NE. Record theslot and the board name of Active Board. Then, click Restore Working/Protection.

4. Click OK in the displayed Confirm dialog box. In the displayed Operation Resultdialog box, click Close.

5. Click Query. In the displayed Operation Result dialog box, click Close. If the slotand the board name of Working Board are displayed in Active Board, it indicatesthat the 1+1 protection switching is already canceled..

6. Query the alarms and performance events on the T2000. If new alarms andperformance events do not occur and services are normal, it indicates that the switchingis successfully cancelled.

----End

8.12 Performing IF 1+1 Protection SwitchThe IF 1+1 protection switching is an important maintenance operation.

Prerequisitel An IF 1+1 protection group must be configured.

l The user must have the system level authority.


Maintenance Guide


Issue 02 (2009-06-30)

Procedure

Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > MicrowaveLink Configuration from the Function Tree.

Step 2 Click the IF 1+1 Protection tab.

Step 3 In Slot Mapping Relation, select the working unit or the protection unit of a protection group.Right-click on the selected unit and select the required switching mode from the displayed menu.The system displays a prompt dialog box.

Step 4 Click Yes.The system displays a prompt dialog box indicating that the command is successfully issued.

Step 5 Click OK.

Step 6 Click Query.

----End

8.13 Querying an IF 1+1 Protection GroupYou can know the current status of an 1+1 protection group by querying the IF 1+1 protectiongroup.

Prerequisitel An IF 1+1 protection group must be configured.

l The user must have the system level authority.


Procedure

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

Step 2 Click the IF 1+1 Protection tab.

Step 3 Click Query, and then check the working status of the IF 1+1 protection group in the SlotMapping Relation area.

----End

8.14 Querying the Working State of AMYou can know the change of the AM mode by querying the working state of AM.

Prerequisitel The communication between the T2000 and the NE must be normal.



8-17

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

Related Information

Only the equipment that is configured with Hybrid radio service supports the query of theworking state of AM.

Procedure

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

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

Step 3 Select the corresponding IFE2 board in the IF Attributes tab page.

Step 4 Click Query.The current modulation modes of the transmit end and the receive end of the IFE2 board aredisplayed.

----End

8.15 Setting the State of an ODU Transmitterthe state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in theunmute state, the ODU transmits and receives microwave signals normally. When the ODUtransmitter is in the mute state, the ODU transmitter does not work, but the ODU can receivesmicrowave signals.

Prerequisitel The communication between the T2000 and the NE must be normal.

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

Procedure

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

Step 2 Choose Configuration > Microwave Link Configuration from the Function Tree.

Step 3 Click the IF/ODU Configuration tab.

Step 4 Click the slot icon of the ODU, and then specify TX Status.

NOTE

If the automatic release function is set, the ODU releases the mute function five minutes after the ODUtransmitter is muted manually.

Step 5 Click Apply.

----End


Maintenance Guide


Issue 02 (2009-06-30)

8.16 Resetting BoardsIn the case of resetting boards, the board software is reset. The board reset is classified into warmreset and cold reset. The warm reset does not affect running services. The cold reset, however,usually affects the running services.



PrecautionsNOTE

l In the case of the warm reset, correct applications and data are loaded on the equipment. The warm resetof a board usually does not affect the running services.

l In the case of the cold reset, correct applications and data before the CPU power-off are restored. The coldreset takes a longer time than the warm reset. The cold reset of a board usually affects the running services.

l If the board is configured with 1+1 protection, a cold reset of the board triggers protection switching.

l During the cold reset of the board, the working status of the board is displayed in blue on the T2000, whichindicates the board is in "Running & Uninstalled" status. In this case, the BD_STATUS alarm is reported.When the cold reset is complete, the working status of the board is displayed in green on the T2000, whichindicates the board is in "Running & Installed" status. In this case, the BD_STATUS alarm stops.

l During the warm reset of the board, the T2000 displays nothing, but the PROG indicator on the board isgreen and blinks. When the warm reset is complete, the PROG indicator on the board turns green and isalways on.

l The board data is not lost after the board is reset.

Procedurel Performing a warm reset on the board

1. Double-click the target NE icon in the Main Topology of the T2000 to display theRunning Status slot view.

2. Select and right-click the CXPR board. Choose warm reset. Then, click OK in thedisplayed warning dialog box.

3. In the displayed Operation Result dialog box, click Close to complete the resetoperation.

NOTE

There is an RST button on the CXPR board. If the RST button is pressed, a warm reset is performed onthe board.

l Performing a cold reset on the board1. Double-click the target NE icon in the Main Topology of the T2000 to display the

Running Status slot view.2. Select and right-click the target board. Choose cold reset. Then, click OK in the

displayed warning dialog box.3. In the displayed Operation Result dialog box, click Close to complete the reset

operation.



8-19

l The board supports hot plugging. In the case of hot plugging, a cold reset is performed onthe board. It is not recommended to perform a cold reset on the board by means of hotplugging.

----End

8.17 Testing the Transmitted Optical Power of the OpticalInterface

If the mean transmitted optical power is excessively high or low, bit errors occur on theequipment. The bit errors affect services and even damage components on the equipment. Thissection describes how to test the transmitted optical power at optical interfaces of the equipmenton site to ensure that the mean transmitted optical power of each optical interface is normal.



l Fiber jumper connections at optical interfaces must be tested and the test result must benormal.

Checking CriteriaQuery the relevant interface specifications, such as the optical interface type and the workingwavelength, according to the barcode on the optical interface board. Refer to TechnicalSpecifications of Boards in the OptiX RTN 950 Radio Transmission System ProductDescription manual.

Tools, Instruments, and Materialsl T2000 and PC

l Optical power meter

l Test fiber jumpers with different connectors

l Fiber connectors

l Fiber cleaning tools

Test Connection DiagramFigure 8-1 shows the connections for the test of the mean transmitted optical power of the OptiXRTN 950 equipment.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-1 Connections for the test of the mean transmitted optical power at the optical interface

PC

CXPR

Opticalpower meter

Precautions

DANGERDuring the test, avoid direct eye exposure to the laser beams.

ProcedureStep 1 Set the target optical interface by using the T2000 to make the optical interface work in the

transmitted state.NOTE

For the Ethernet optical interface, set it to the enabled state on the T2000.

1. On the Main Topology of the T2000, select and right-click the target NE. Select NEExplorer from the displayed shortcut menu.

2. Select the target Ethernet board in the NE Explorer. Choose Configuration > InterfaceManagement > Ethernet Interface from the Function Tree.

3. Enable the target Ethernet optical interface in the Enable Port parameter of GeneralAttributes tab.

Step 2 Disconnect the fiber at the OUT port of the tested optical interface and put the protective cap onthe fiber connector.

Step 3 Draw out the optical module to check the label on it. Then, insert it back to the original position.You can learn the type of the optical interface. Based on the type of the optical interface, obtainthe specifications such as working wavelength and mean transmitted optical power of this opticalinterface from the checking criteria.

Step 4 Set the wavelength of the optical power meter to make it consistent with the working wavelengthof the tested optical interface.



8-21

CAUTIONSet the wavelength of the optical power meter consistent with the working wavelength of thetested optical interface so that the optical power work normally. Then, proceed with the nextstep.

Step 5 Connect the OUT port of the optical interface to the optical power meter by using the test fiberjumper that maps the optical interface.

Step 6 Observe the reading on the optical power meter. Record the value when the reading does notchange. The value indicates the mean transmitted optical power of the tested optical interface.

Step 7 Check whether the optical power value obtained is within the range of the mean transmittedoptical power.l If the optical power value obtained is within the range, proceed to Step 10.

l If the optical power value obtained is beyond the range, proceed to Step 8.

Step 8 Check and the fiber connector, and clean it if necessary, according to 8.24 Inspecting andCleaning the Optical Fiber Connectors.

Step 9 Perform Step 5 through Step 7 to test the mean transmitted optical power of the optical interfaceagain till the value obtained is within the normal range.

Step 10 Restore the fiber connection of the tested port.

Step 11 Repeat the previous steps to test the mean transmitted optical power at all the optical interfacesof the equipment one by one.

----End

8.18 Testing the Receive Optical Power of the OpticalInterface

If the receive optical power is excessively high or low, bit errors occur on the equipment. Thebit errors affect the services or even damage components on the equipment. This sectiondescribes how to test the receive optical power at optical interfaces of the equipment on site toensure that the receive optical power of each optical interface is normal.

Prerequisitel Fiber jumper connections at optical interfaces must be tested and the test result must be

normal.l The mean launched optical power at optical interfaces must be tested and the test result

must be normal.l Fibers from the adjacent station must be routed to the optical distribution frame (ODF) of

the local station and must provide optical signals to the local station.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l The Ethernet optical interface must be set to the enabled state on the T2000 for sending opticalsignals externally.

l For methods on how to set the optical interface, see 8.17 Testing the Transmitted OpticalPower of the Optical Interface.

l The flange must be clean and properly connected to the fiber connector.

Checking CriteriaQuery the relevant interface specifications, such as the optical interface type and the workingwavelength, according to the barcode on the optical interface board. Refer to TechnicalSpecifications of Boards in the OptiX RTN 950 Radio Transmission System ProductDescription manual.

Tools, Instruments, and Materialsl Optical power meter

l Test fiber jumpers with different connectors

l Fiber connector

l Fiber cleaning tools

l Optical attenuator

Test Connection DiagramThe OptiX RTN 950 equipment supports the Ethernet optical interfaces. Figure 8-2 shows theconnections for the test of the receive optical power at the optical interface of the local station.

Figure 8-2 Connections for the test of the receive optical power at the optical interface

INOUTINOUT

Local station

Optical power meter

Fiber jumper at the IN interface

Adjacent station

Fiber jumperODF

Optical interfaceOptical

interface

ODF

Procedure

Step 1 Set the wavelength of the optical power meter to make it consistent with the working wavelengthof the tested optical interface.

Step 2 Remove the fiber jumper from the IN port of the tested optical interface on the local station.Then, connect it to the optical power meter.



8-23

Step 3 Observe the reading on the optical power meter. Record the value when the reading does notchange. The value indicates the receive optical power of the tested optical interface.

Step 4 Check whether the optical power value obtained is within the normal range. The receive opticalpower must follow the standard: sensitivity + 3 dBm < receive optical power (tested) < overloadthreshold - 5 dBm. For the nominal values of the sensitivity and the overload threshold, see thechecking criteria.

l If the optical power value obtained is within the normal range, proceed to Step 8.

l If the optical power value obtained is beyond the normal range:

– When the receive optical power is less than the sensitivity plus 3 dBm, proceed to Step5.

– When the receive optical power is larger than the overload threshold minus 5 dBm,proceed to Step 6.

Step 5 Check whether the fiber connector, and the fiber flange and the optical attenuator on the ODFside are contaminated.

l If the fiber connector is contaminated, clean it according to 8.24 Inspecting and Cleaningthe Optical Fiber Connectors.

l If the fiber flange or the optical attenuator on the ODF side is contaminated, replace the fiberflange or the optical attenuator.

Proceed to Step 7.

Step 6 Check whether the optical attenuator is normal.

l If the optical attenuator is normal, add an optical attenuator on the ODF side.

l If the optical attenuator is not normal, replace the optical attenuator.

Step 7 Perform Step 2 to Step 4 to test the receive optical power of the optical interface again till thevalue obtained is within the normal range.

Step 8 Restore the fiber connection of the tested interface.

Step 9 Repeat the previous steps to test the receive optical power at all the optical interfaces of theequipment one by one.

----End

8.19 Replacing Boards on SiteWhen replacing a board, remove and insert it as required; make sure that the mapping relationsbetween the interfaces and cables are not changed before and after the replacement; observeindicators to determine the running state of the board.

PrerequisiteA new board must be available.


ESD wrist strap, ESD bag, and cross screwdriver


Maintenance Guide


Issue 02 (2009-06-30)

PrecautionsBefore replacing a board, read Safety Precautions for Using the Equipment carefully.

The chassis of the OptiX RTN 950 and the OptiX RTN 910 are different, but the boardreplacement operations are similar. Thus, the board replacement illustrations mentioned belowconsider the OptiX RTN 910 as an example.

DANGERAvoid direct eye exposure to the laser source from the optical interface board or from inside thefiber, because laser beams can cause permanent eye damage.

CAUTIONl When replacing a board, make sure that the board is not connected to any fibers or cables.l The optical interfaces and the fiber jumper connectors must be clean.l The cable connectors must be properly sealed to prevent short circuit.

ProcedureStep 1 Properly wear the ESD wrist strap according to .

Step 2 Record the connection relations between board interfaces and fibers or cables.

Step 3 Remove fibers or cables from the board interfaces.

Step 4 Remove the board.l Remove the CXPR or processing board:

Use a screwdriver to loosen the captive screws on the right and left sides of the board. Then,the screws are automatically sprung out. See Figure 8-3.

Figure 8-3 Loosening screws with a screwdriver

Loosen the captive screw



8-25

Hold the ejector levers of the board and pull them outward to disengage the board from thebackplane socket. Then, remove the board from the slot slowly with stable force. See Figure8-4.

Figure 8-4 Removing the board (1)

Remove the board gently

l Remove the FAN or PIU board:

Hold the front panel and tack switches of the board to disengage the board from the backplanesocket. Then, remove the board from the slot slowly with stable force until the board iscompletely disengaged from the chassis. See Figure 8-5.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-5 Removing the board (2)

Remove the boardslowly out of the slot

Step 5 Put the replaced board in an antistatic bag. Record the NE name and the fault on a maintenancelabel and then affix the label to the bag.

Step 6 Insert a new board.l Insert a new FAN or PIU board:

Hold the front panel and tact switches of the board, and slide the board slowly into the relevantslot along the guide rails of the chassis. Push the front panel of the board gently until theboard completely engages with the backplane sockets. Then, you can release the front paneland the tact switches. See Figure 8-6.



8-27

Figure 8-6 Inserting the board (1)

Insert the board slowlyinto the slot

l Insert the CXPR or processing board:

Use both hands to hold the ejector levers and pull them outward. Then, insert the board andslide it gently into the relevant slot along the right and left guide rails. In addition, align thegrooves of the upper and lower ejector levers on the front panel of the board with the upperand lower edges of the chassis. Push the front panel of the board into the slot gently until theboard engages with the backplane sockets. Then, pull the ejector levers inward to make theboard completely inserted into the slot. See Figure 8-7.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-7 Inserting the board (2)

Push it in gently

Use a screwdriver to tighten the captive screws on the right and left sides of the board. SeeFigure 8-8.

Figure 8-8 Tightening screws with a screwdriver

Tighten the captive screw

Step 7 According to the connection relations between interfaces and fibers or cables, insert the fibersor cables into the interfaces on the board. For details, see OptiX RTN 950 Radio TransmissionSystem IDU Quick Installation Guide.



8-29

Step 8 Check whether the STAT and PROG indicators on the front panel of each board are green. Ifthe STAT and PROG indicators are green, it indicates that the board is successfully replaced.Otherwise, repeat the previous steps to insert/remove or replace the board.

----End

8.20 Powering On the EquipmentThis section describes how to connect the power supply to the equipment to ensure that theequipment can be powered on normally.

PrerequisiteThe external power supply must be provided.

Tools, Instruments, and MaterialsScrewdriver

Precautions

CAUTIONDot insert or remove any power plugs and the PIU board when the power is on.

ProcedureStep 1 Make sure that the external power voltage is sufficient to avoid excessively high voltage

damaging the equipment.

Step 2 Check the power cable of the chassis. Make sure that the power cable is connected to the PIUboard correctly.

Step 3 Check the connector of the power cable to ensure that the connector is connected firmly. If theconnector is connected loosely, tighten the fastening screws of the connector by using ascrewdriver.

Step 4 Turn the power switch, which connects the external power supply and the PIU board, to the onposition.

Step 5 Observe the STAT and PROG indicators of the CXPR board.l If the PROG indicator flashes, the board software is being initialized and loaded.

l After the board software is loaded successfully, the STAT and PROG indicator, which stayon in green.

----End

8.21 Powering Off the EquipmentThis section describes how to power off the equipment.


Maintenance Guide


Issue 02 (2009-06-30)

Precautions

CAUTIONIf the equipment is powered off, it stops running and all the services on this equipment areinterrupted.

Procedure

Step 1 Turn off the power switch, which connects the external power supply and the PIU board, to theoff position.

Step 2 Make sure that indicators on all the boards are off and the equipment is powered off.

----End

8.22 Querying and Setting the Working Mode of EthernetInterface

This section describes how to query and set the working mode of Ethernet interface.

PrerequisiteYou must be an NM user with "NE and network operator" authority or higher.

Procedure

Step 1 Right-click the NE and choose NE Explorer. The NE Explorer dialog box is displayed.

Step 2 Select the desired board in the NE Explorer, and then choose Configuration > InterfaceManagement > Ethernet Interface from the Function Tree.

Step 3 In the General Attributes tab, click Query, you can query the working mode of the port.

Step 4 Double-click the Working Mode field of the desired port to modify the working mode of theboard.



8-31

NOTE

The working modes of different Ethernet interfaces are as follows:

l The FE electrical interface can be set to 100M full-duplex or auto-negotiation working mode.

l The FE optical interface can be set to 100M full-duplex working mode.

l The GE optical interface can be set to 1000M half-duplex, 1000M full-duplex or auto-negotiationworking mode.

Step 5 Click Apply and click Yes in the displayed Warning dialog box. The working mode of theEthernet interface is set.

----End

8.23 Querying Protection ConfigurationThis section describes the basic method for querying the protection scheme that is configuredin the equipment when a fault or service interruption occurs.

PrerequisiteYou must be an NM user with "NE and Network Operator" authority or higher.

Background InformationThe equipment supports the 1+1 protection of boards. For details, see the OptiX RTN 950 RadioTransmission System IDU Hardware Description.

ProcedureStep 1 Right-click the NE and choose NE Explorer. The NE Explorer dialog box is displayed.

Step 2 Select the desired NE in the NE Explorer. choose Configuration > Board 1+1 Protectionfrom the Function Tree. Then, the 1+1 protection pair is listed in the 1+1 Protection List tab.

Step 3 Select the desired protection, and click Query. Click Close on the Operation Result dialogbox. Then, the details of the protection pairs are displayed.

----End

8.24 Inspecting and Cleaning the Optical Fiber ConnectorsCleaning optical components is to remove dust or other dirt to avoid performance degradationof optical transmission systems. Inspecting and cleaning fiber connectors used in fiber opticconnections are introduced here.

8.24.1 OverviewOverview of the purpose and procedure of cleaning optical fiber connectors, the items that maycause pollution to optical connectors are also introduced here.

8.24.2 Protection of Optical ConnectorsThe requirements of optical connector protection are listed here.

8.24.3 Tools, Equipment and MaterialsThe recommended tools, equipment and materials used in cleaning the optical connector arelisted here.


Maintenance Guide


Issue 02 (2009-06-30)

8.24.4 Inspecting Optical ConnectorsThe following describes how to inspect the optical connectors and check the status of the fibersurface.

8.24.5 Cleaning Optical Fiber Connectors Using Cartridge CleanersClean the fiber optic only in the case that there are flaws on it. The following describes how toclean the fiber optic with a type of CLETOP cassette cleaner.

8.24.6 Cleaning Optical Fiber Connectors Using Lens TissueClean the fiber optic only in the case that there are flaws on it. The following procedure providesthe steps to clean the fiber connectors using lens tissue.

8.24.7 Cleaning Optical Modules Using Optical Cleaning SticksOptical modules must be cleaned with special cleaning tools and materials. The followingprocedure provides the steps to clean optical adapters using optical cleaning sticks.

8.24.1 OverviewOverview of the purpose and procedure of cleaning optical fiber connectors, the items that maycause pollution to optical connectors are also introduced here.

Cleaning optical components is to remove dust or other dirt to avoid performance degradationof optical transmission systems. Here describes how to inspect and clean fiber connectors usedin fiber optic connections.

Figure 8-9 shows the optical fiber connector.

Figure 8-9 Optical fiber connector

The following items should be removed because they pollute optical connectors that areextensively adopted in optical transmission systems:

l Dust

l Oils (frequently from human hands)

l Film residues (condensed from vapors in the air)

l Powdery coatings (left after water or other solvents evaporate)

Dust is the most common dirt in optical connectors. Even small dust that can be seen only undera microscope can affect the quality of optical signals, degrade the system performance and causepotential instability in network operation.

A one-micrometer dust granule on an optical connector of a single mode fiber can block 1%light and cause 0.05 dB lost. A nine-micrometer dust granule that cannot be seen by human eyes



8-33

can block an entire fiber core. Therefore, small dirt even that cannot be seen by human eyesshould be removed.

NOTE

Before you connect any optical component, make sure that you have inspected and cleaned the component.

General ProcedureTable 8-1 below introduces the general procedure of how to inspect and clean the optical fiberconnectors.

Table 8-1 General procedure of inspecting and cleaning the optical fiber connectors

Operation Details

Cleaning Optical Fiber Connectors UsingCartridge Cleaners

Refer to "8.24.5 Cleaning Optical FiberConnectors Using Cartridge Cleaners"

Cleaning Optical Fiber Connectors UsingLens Tissue

Refer to "8.24.6 Cleaning Optical FiberConnectors Using Lens Tissue"

Cleaning Optical Adapters Using OpticalCleaning Sticks

Refer to "8.24.7 Cleaning Optical ModulesUsing Optical Cleaning Sticks"

8.24.2 Protection of Optical ConnectorsThe requirements of optical connector protection are listed here.

The requirements of optical connector protection are:

l All optical interface boards must be transported and stored in reliable packing. This servesto avoid mechanical and electrostatic damages and to reduce vibrations.

l Store the protective caps in an antistatic bag.

l Cover the optical interfaces of the replaced boards with protective caps in time. Store themin proper packages to keep the optical interfaces clean.

l The protective caps recommended are shown in Figure 8-10, The protective caps notrecommended are shown in Figure 8-11.

Figure 8-10 Protective caps recommended


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-11 Protective caps not recommended

NOTE

The air filter caps made of soft rubber are not recommended, which tends to collect dust and sundries. Thistype of caps provides poor dustproof function.

8.24.3 Tools, Equipment and MaterialsThe recommended tools, equipment and materials used in cleaning the optical connector arelisted here.

The recommended tools, equipment and materials are listed below:


l Optical fiberscope with 400x magnification (a video fiberscope is recommended)

l CLETOP cassette cleaner, see Figure 8-12

l Clean solvent( Isoamylol is preferred, propyl can be used alcohol or formalin is never used)

l Non-woven lens tissue, lint-free wipes or fiber cleaning tissue (Non-woven lens tissue isrecommended)


l Special cleaning roll

l Optical cleaning sticks used for optical connectors or cotton swabs (medical cotton or longfiber cotton) See Figure 8-13 and Figure 8-14



8-35

Figure 8-12 CLETOP cassette cleaner

Figure 8-13 Cleaning stick for the SC and FC optical interface (just for reference)

Figure 8-14 Cleaning stick for the LC optical interface

8.24.4 Inspecting Optical ConnectorsThe following describes how to inspect the optical connectors and check the status of the fibersurface.

Tools, Equipment and MaterialsThe tools, equipment and materials are listed below:


Maintenance Guide


Issue 02 (2009-06-30)



Precautions

WARNINGLaser is dangerous. The light is not visible to the eyes with or without laser protective glasses.Do not look into optical connectors or interfaces. Failure to follow this warning can cause damageto the eyes, or even blindness.Use a fiberscope equipped with a safety device or a desktop video fiberscope when you inspectthe optical connectors. If one is not available, turn off the lasers and disconnect both ends of thefiber before you inspect the optical connectors

CAUTIONElectro static discharge (ESD) is hazardous to the electronic equipment. Use proper handlingsto prevent damage to the electronic equipment. Failure to follow this caution can causeequipment damage and/or loss of traffic

ProcedureStep 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.

Step 2 Test the optical power using a power meter. Ensure that there is no laser light on the opticalconnector.

Step 3 Use a fiberscope to inspect the fiber to check if there is any dirt or damage. Refer to the examplesshown below.l For an image of the intact fiber optic surface through a fiberscope that can be used

successfully in the equipment, see Figure 8-15.

Figure 8-15 An intact fiber



8-37

l For images of fibers through a fiberscope with imperfections that can impair the function of

the assembly, see Figure 8-16 . The image on the left shows clearly a damaged fiber. Severelydamaged fibers must not be used in the system equipment. Otherwise, permanent and severedamage to the assembly can occur. The image on the right shows a fiber that is suspect. Ifthe output power is within an acceptable range, the fiber might not cause any damage to theassembly. If the output power is unstable or falls outside the acceptable range, however, thefiber can cause damage to the assembly and must not be used.

Figure 8-16 Damaged or suspect fibers

NOTE

The views shown do not represent the entire surface of the fiber optic. Much of the surface is the metalconnector and only the 800-micron core is the actual fiber.

l For details on acceptable and unacceptable fibers, see Figure 8-17, Figure 8-18 and Figure

8-19.

Figure 8-17 An intact fiber


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-18 Acceptable fibers with imperfections

Figure 8-19 Unacceptable fibers with imperfections

Step 4 If any dirt is detected, clean the optical connector. For details, refer to "8.24.5 Cleaning OpticalFiber Connectors Using Cartridge Cleaners" and "8.24.6 Cleaning Optical FiberConnectors Using Lens Tissue".

Step 5 If any damage is detected, replace the fiber or board.

----End

8.24.5 Cleaning Optical Fiber Connectors Using Cartridge CleanersClean the fiber optic only in the case that there are flaws on it. The following describes how toclean the fiber optic with a type of CLETOP cassette cleaner.



8-39

Prerequisite

Before cleaning, inspect the fiber optic surface with a fiberscope or a magnifier to determine theextent to which the fiber optic might be damaged or dirty. Clean the fiber optic only in the casethat there are flaws on it. If there are not, do not clean it. That is because the cleaning itself mightintroduce dust, dirt, or cause potential damage to the fiber optic.

The following procedure provides the steps to clean the fiber connectors using cartridge typecleaners. There are several types of cartridge cleaners. The following describes a type ofCLETOP cassette cleaner.


The tools, equipment and materials are listed below:

l CLETOP cassette cleaner



Precautions

WARNINGLaser is dangerous. The light is not visible to the eyes with or without laser protective glasses.Do not look into optical connectors or interfaces. Failure to follow this warning can cause damageto the eyes, or even blindness.

CAUTIONThe electrostatic discharge may damage the equipment. Before touching the equipment, boardor integrated circuit (IC) chip, you must wear the ESD wrist strap to prevent electrostaticdischarge on human body from damaging the static-sensitive components, and ensure that theother end of the strap is properly grounded. Otherwise, the equipment may be damaged or theservice may be interrupted.

Procedure

Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.

Step 2 Use an optical power meter to measure and ensure that there is no laser light on the opticalconnector.

Step 3 Press down and hold the lever of the cassette cleaner, and the shutter slides back and exposes anew cleaning area. See Figure 8-20.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 8-20 Using the CLETOP cassette cleaner

Step 4 Place the fiber tip lightly against the cleaning area so that the end face is flat on the cleaningarea

Step 5 Drag the fiber tip lightly on one cleaning area in the direction of the arrow once. See Figure8-21. Do it again on the other cleaning area in the same direction as the first time once. SeeFigure 8-22.

CAUTIONDo not scrub the fiber against fabric or clean over the same cleaning area more than once.Otherwise, the connector can be dirtied or damaged.

Figure 8-21 Dragging the fiber tip lightly on one cleaning area



8-41

Figure 8-22 Dragging the fiber tip lightly on the other cleaning area

Step 6 Release the lever of the cassette cleaner to close the cleaning area.

Step 7 Use a fiberscope to inspect the adapter to check if there is any dirt. For details refer to theexamples shown in 8.24.4 Inspecting Optical Connectors. If the optical adapter is still dirty,repeat the Step 1 to Step 6.

Step 8 Connect the fiber connector to the board.

Step 9 Turn on the lasers after you connect the fiber to the board.

----End

8.24.6 Cleaning Optical Fiber Connectors Using Lens TissueClean the fiber optic only in the case that there are flaws on it. The following procedure providesthe steps to clean the fiber connectors using lens tissue.

PrerequisiteBefore cleaning, inspect the fiber optic surface with a fiberscope or a magnifier to determine theextent to which the fiber optic might be damaged or dirty. Clean the fiber optic only in the casethat there are flaws on it. If there are not, do not clean it. That is because the cleaning itself mightintroduce dust, dirt, or cause potential damage to the fiber optic.

The following procedure provides the steps to clean the fiber connectors using lens tissue. Useonly the special materials for cleaning the fiber connectors. Refer to the local site practices.

Tools, Equipment and MaterialsThe tools, equipment and materials are listed below:




Maintenance Guide


Issue 02 (2009-06-30)

l Clean solvent. (Isoamylol is preferred, propyl can be used. alcohol or formalin is neverused)

l Non-woven lens tissue, lint-free wipes or fiber cleaning tissue (Non-woven lens tissue isrecommended)


l Special cleaning roll

Precautions


CAUTIONThe electrostatic discharge may damage the equipment. Before touching the equipment, boardor integrated circuit (IC) chip, you must wear the ESD wrist strap to prevent electrostaticdischarge on human body from damaging the static-sensitive components, and ensure that theother end of the strap is properly grounded. Otherwise, the equipment may be damaged or theservice may be interrupted.

Procedure

Step 1 Turn off the lasers before the inspection. Disconnect both ends of the fiber to be inspected.

Step 2 Use an optical power meter to measure and ensure that there is no laser light on the opticalconnector.

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

Step 4 Clean the fiber tip on the lens tissue. See Figure 8-23 and Figure 8-24.

CAUTIONDo not scrub the fiber against fabric or clean over the same cleaning area more than once. Failureto comply can result in connector dirt or damage.



8-43

Figure 8-23 Cleaning the fiber tip with the lens tissue on the desk

Figure 8-24 Cleaning the fiber tip with the lens tissue on the hand

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

Step 6 Use the compressed gas to blow off the fiber tip.NOTE

l When you use the compressed gas, keep the injector nozzle as close as possible to the fiber connectorsurface without touching it.

l When you use the compressed gas, first spray it into the air as the initial spray of compressed air cancontain some condensation or propellant. Such condensation leaves behind a filmy deposit.

l If the compressed gas is not available, a clean roll can be used.

Step 7 Use a fiberscope to inspect the adapter to check if there is any dirt. For details refer to theexamples shown in 8.24.4 Inspecting Optical Connectors. If the optical adapter is still dirty,repeat the Step 1 to Step 6.

Step 8 Do not touch the fiber connector after you clean it. Connect it to the optical interface board atonce. If it is not used for the time being, put a protective cap on it.


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

A piece of lens tissue can be used for only one time.


----End

8.24.7 Cleaning Optical Modules Using Optical Cleaning SticksOptical modules must be cleaned with special cleaning tools and materials. The followingprocedure provides the steps to clean optical adapters using optical cleaning sticks.

Prerequisite

There are several types of optical cleaning sticks and cotton swabs that can be used. Refer to thelocal site practices. You can obtain these tools and materials from a fiber cable and connectormanufacturer.


The tools, equipment and materials are listed below:



l Clean solvent. (Isoamylol is preferred, propyl can be used. alcohol or formalin is neverused)


l Optical cleaning sticks used for optical connectors or cotton swabs (medical cotton or longfiber cotton)

Precautions


CAUTIONThe electrostatic discharge may damage the equipment. Before touching the equipment, boardor integrated circuit (IC) chip, to prevent the electrostatic discharge on the human body damagingthe static-sensitive components, you must wear the ESD wrist strap and ensure the other end ofthe strap is properly grounded. Otherwise, the equipment may be damaged or the service maybe interrupted.



8-45

Procedure

Step 1 Before checking the fiber connector, disable the laser and disconnect the two ends of the fiberfrom other components.

Step 2 Use the optical power meter to test and make sure that no laser light is present at the fiber module.

Step 3 Select the cleaning stick with a proper diameter for a certain type of the module.

NOTE

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. See Figure 8-13 and Figure 8-14.

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

Step 5 Place the optical cleaning stick lightly on the optical modules so that cleaning solvent is againstthe fiber tip. Turn the stick clockwise four to five times and make sure that there is direct contactbetween the stick tip and fiber tip. Hold the stick straight out from the module.

Step 6 Use the compressed gas to blow off the fiber tip.

NOTE

l When you use the compressed gas, keep the injector nozzle close to the connector surface withouttouching it.

l When you use the compressed gas, first spray it into the air as the initial spray of compressed air cancontain some condensation or propellant. Such condensation leaves behind a filmy deposit.

Step 7 Use a fiberscope to inspect the fiber tip to check if there is any dirt. For details refer to theexamples shown in "8.24.4 Inspecting Optical Connectors". If the optical fiber tip is still dirty,repeat the Step 1 to Step 6.

Step 8 Connect the fiber to the board, or put a protective cap on the interface.


----End


Maintenance Guide


Issue 02 (2009-06-30)

9 Alarm

About This Chapter

This chapter describes basic concepts related to alarms and how to handle related alarms of theequipment.

9.1 Basic Concepts Related to AlarmsAlarms are always the information sources for checking the running state of equipment and forlocating faults. Hence, it is necessary to understand the basic concepts related to alarms.

9.2 Alarm ListThis chapter describes all the alarms that may be generated by the OptiX RTN 950.

9.3 Alarm HandlingThis chapter describes how to handle related alarms of the equipment.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 9 Alarm


9-1

9.1 Basic Concepts Related to AlarmsAlarms are always the information sources for checking the running state of equipment and forlocating faults. Hence, it is necessary to understand the basic concepts related to alarms.

9.1.1 Alarm Reporting FlowThe alarm reporting flow indicates the entire process from alarm generation to alarm notification.The alarm reporting flow provides guidelines for the user to handle alarms.

9.1.2 Alarm CorrelationThe OptiX RTN 950 supports the alarm correlation analysis function. Learning the alarmcorrelation can facilitate the fault locating. This section mainly describes the correlation rulesof common service alarms of the OptiX RTN 950, and explains the alarm correlation by takingthe ETH_LINK_DOWN alarm as the example.

9.1.3 Alarm CategoryAccording to the standards and functions of the T2000, alarms are classified into severalcategories.

9.1.4 Alarm SeverityThe alarm severity always indicates the importance, impact and urgency of an alarm. Alarmsare classified into four categories by the severity, that is, critical alarms, major alarms, minoralarms and warning alarms.

9.1.5 Alarm NotificationInstant awareness of alarms is very important for handling alarms and maintaining the network.The equipment and the T2000 provide different means of notifying alarms to the user.

9.1.1 Alarm Reporting FlowThe alarm reporting flow indicates the entire process from alarm generation to alarm notification.The alarm reporting flow provides guidelines for the user to handle alarms.

Figure 9-1 shows the alarm reporting flow.

9 AlarmOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

Figure 9-1 Alarm reporting flow diagram

The board monitors the alarm and the alarm is saved in the alarm database of the board

No

No

No

No

Yes

Yes

Yes

Yes

No

Yes

Whether to set the alarm

shelter?

The alarm is saved in the alarm database of the system control

board

Whether to set the alarm suppression?

The alarm is automatically reported

Whether to set the equipment alarm

filtering?

The alarm data is saved in the NM server

Analyse the alarm correlation

The NM monitors the NM alarm and the alarm is saved in the NM server

Whether to set the alarm suppression?

Displayed on the NM client

Whether to set the alarm

reporting?

The alarm data is sent to the receive ternimal

Discard the alarm data

The alarm is suppressed and the board does not

report the alarm any more

The alarm is sheltered and the board does

not monitor the alarm

NOTE

For details on the alarm suppression, alarm synchronization, alarm automatic reporting, alarm filtering andalarm notification, see the OptiX iManager T2000 Online Help.

9.1.2 Alarm CorrelationThe OptiX RTN 950 supports the alarm correlation analysis function. Learning the alarmcorrelation can facilitate the fault locating. This section mainly describes the correlation rulesof common service alarms of the OptiX RTN 950, and explains the alarm correlation by takingthe ETH_LINK_DOWN alarm as the example.



9-3

ConceptsWhen faults or anomalies occur in the network, a series of alarms are reported. Some of thealarms are crucial to fault locating and these alarms are considered as key alarms. Some alarmsinterfere in the fault locating and these alarms are considered as interference alarms. Then, thekey alarms and the interference alarms have the alarm correlation.

Alarms with correlation have the following features:l Alarms (root alarm) directly caused by faults or anomalies can generate some other alarms

(non-root alarms). The root alarms and non-root alarms have the alarm correlation.l If multiple alarms result from the same fault or anomaly, these alarms have the alarm

correlation.

To make the alarm information facilitate the fault locating in a more effective manner, you canset the alarm correlation rules on the T2000 and enable the alarm correlation analysis function.Then, you can make the NE only report the key alarms, that is, make the key alarms suppressthe relevant interference alarms.

RulesThe alarm correlation rules for the OptiX RTN 950 are as follows:l The alarm suppression is realized in the same equipment.

l The root alarm suppresses the non-root alarm.

l The alarm resulting from the fault at the lower layer of the service hierarchical modelsuppresses the alarm resulting from the fault at the upper layer of the service hierarchicalmodel.

Layers, from the lower to the upper in the service hierarchical model, are physical, data link,tunnel, PW and emulated service. In the model, the upper layers depend on the services providedby the lower layers. When a lower layer and a upper layer have faults at the same time, to removethe fault at the upper layer, the fault at the lower layer must be removed first. At this time, thealarm resulting from the lower-layer fault suppresses the alarm resulting from the upper-layerfault.

NOTE

l Be cautious to set the alarm correlation rules, because they are the basis of the alarm correlation analysisand can affect the result of the analysis.

l Normally, use the default correlation rules on the T2000.

l The alarm correlation analysis function is disabled by default. To use the alarm correlation rules toperform the alarm correlation analysis, you need to manually enable the analysis function.

As show in Figure 9-2, the alarm correlation rules are illustrated based on the Ethernet servicescarried at the Ethernet port.


Maintenance Guide


Issue 02 (2009-06-30)

Figure 9-2 Alarm correlation rules of the Ethernet services carried at the Ethernet port

LSR_NO_FITED

LASER_SHUTETH_LOS

ETH_LINK_DOWNMPLS_TUNNEL_FDI

EmulatedService

（Ethernet）

PW

Tunnel

ETH_CFM_RDI

MPLS_PW_BDI

MPLS_TUNNEL_BDI与MPLS_PW_FDI

MPLS_PW_BDI

ETH_CFM_RDI

Physical

Data-Link

N

A1 A2

A N

Alarm A1 suppresses alarm A2

N indicates the notification message that is sentor received by the NE

The NE generates alarm A andsends the notification message N to

other NEs

A N Alarm A suppresses the notificationmessage N sent by the local NE

N1 N2 Notification message N1 suppressesnotification message N2

N A Notification message N suppressesalarm A

LAG_MEMBER_DOWN

LASER_MOD_ERR

ETH_EFM_LOOPBACK

MAC_FCS_EXC

MAC_FCS_SD ETH_EFM_REMFAULT

ETH_EFM_DF

ETH_EFM_EVENT

MPLS_TUNNEL_MISMERGE

MPLS_TUNNEL_MISMATCH

MPLS_TUNNEL_LOCV

MPLS_TUNNEL_Excess

MPLS_TUNNEL_UNKNOWN

MPLS_TUNNEL_SF

MPLS_TUNNEL_SD

MPLS_PW_MISMERGE

MPLS_PW_MISMATCH

MPLS_TUNNEL_FDI

MPLS_TUNNEL_BDI

MPLS_PW_FDI

MPLS_PW_LOCV

MPLS_PW_UNKNOWN

MPLS_PW_Excess MPLS_PW_SF

MPLS_PW_SD

ETH_CFM_MISMERGE

ETH_CFM_UNEXPERI

ETH_CFM_LOC

ETH_CFM_SF

ETH_CFM_SD

FDBSIZEALM_ELAN

ETH_CFM_DefMACstatus



9-5

IllustrationAs shown in Figure 9-3, an E-Line service is configured between NE1 and NE3, and NE2 isinvolved. Each segment of the service is over the FE link. In addition, the alarm correlationanalysis function is enabled for NE1, NE2 and NE3.

Figure 9-3 Illustration of the alarm correlation analysis

NE 1 NE 2 NE 3

ETH _LINK_ DOWN ETH_LINK _ DOWN MPLS_TUNNEL_FDI

When the receive working mode is inconsistent with the transmit working mode on the FE linkbetween NE1 and NE2, the ETH_LINK_DOWN alarm is reported at the relevant ports on NE1and NE2. Because the alarm correlation analysis function is enabled for the three NEs, theETH_LINK_DOWN alarm suppresses the MPLS_TUNNEL_BDI, LAG_MEMBER_DOWN(if there is an LAG), MAC_FCS_EXC and ETH_EFM_DF alarms. In the meantime, NE2transmits the MPLS_TUNNEL_FDI notification packet to NE3. After NE3 receives thenotification packet, the MPLS_TUNNEL_LOCV alarm is suppressed.

According to the previous illustration, if all the NEs in the network are enabled with the alarmcorrelation analysis function, when faults occur in the network, the NEs only need to report thekey alarms to the T2000. This can facilitate the fault location.

9.1.3 Alarm CategoryAccording to the standards and functions of the T2000, alarms are classified into severalcategories.

The six types of alarms are listed as follows:l Communication alarm, which indicates anomalies in NE communication and optical signal

communication, such as interruption of NE communication and loss of optical signals.l Processing alarm, which indicates anomalies in software processing, such as failure to back

up database, and failure to perform protection switching.l Equipment alarm, which indicates anomalies in equipment hardware, such as failure of the

laser and loopback of the optical interface.l Service alarm, which indicates anomalies in service status and network QoS, such as MS

performance over-threshold.l Environment alarm, which indicates anomalies in the power supply system and the

equipment room environment (temperature, relative humidity, access control, and so on),such as excessively high temperature of the power supply module.

l Security alarm, which indicates anomalies in security of the T2000 and NE, such as logoutof the NE user.


Maintenance Guide


Issue 02 (2009-06-30)

9.1.4 Alarm SeverityThe alarm severity always indicates the importance, impact and urgency of an alarm. Alarmsare classified into four categories by the severity, that is, critical alarms, major alarms, minoralarms and warning alarms.

Table 9-1 lists details on how to handle alarms at different severity levels.

Table 9-1 Alarm severity

Alarm Severity Definition Handling Principle

Critical alarm The critical severity levelindicates that a serviceaffecting condition hasoccurred and an immediatecorrective action is required.Such a severity can bereported, for example, whena managed object becomestotally out of service and itscapability must be restored.

Handle it immediately.

Major alarm The major severity levelindicates that a serviceaffecting condition hasdeveloped and an urgentcorrective action is required.Such a severity can bereported, for example, whenthere is a severe degradationin the capability of themanaged object and its fullcapability must be restored.

Handle it urgently.

Minor alarm The minor severity levelindicates the existence of anon-service affecting faultcondition and that correctiveaction should be taken inorder to prevent a moreserious (for example, serviceaffecting) fault. Such aseverity can be reported, forexample, when the detectedalarm condition is notcurrently degrading thecapacity of the managedobject.

Find the alarm cause, handleit correctly, and remove thepotential trouble.



9-7

Alarm Severity Definition Handling Principle

Warning alarm The warning severity levelindicates the detection of apotential or impendingservice affecting fault, beforeany significant effects havebeen felt. Action should betaken to further diagnose (ifnecessary) and correct theproblem in order to prevent itfrom becoming a moreserious service affectingfault.

Analyze the alarm cause, andremove the potential trouble.

9.1.5 Alarm NotificationInstant awareness of alarms is very important for handling alarms and maintaining the network.The equipment and the T2000 provide different means of notifying alarms to the user.

Alarm Notifying Means of the T2000The T2000 has the following means of notifying alarms.l Alarm color

l Alarm browsing interface

l Alarm box

l Sound box

l Remote alarm notification

Alarm Notifying Means of the EquipmentThe equipment mainly uses the alarm indicators on the cabinet and boards to notify alarms atdifferent severity levels.

9.2 Alarm ListThis chapter describes all the alarms that may be generated by the OptiX RTN 950.

9.2.1 SL91CXPR Board Alarm List

9.2.2 TND1EF8T Board Alarm List

9.2.3 TND1EF8F Board Alarm List

9.2.4 TND1EG2 Board Alarm List

9.2.5 TND1ML1/TND1ML1A Board Alarm List

9.2.6 TND1IFE2 Board Alarm List

9.2.7 TND1AUXQ Board Alarm List


Maintenance Guide


Issue 02 (2009-06-30)

9.2.8 TND1PIU Board Alarm List

9.2.9 TND1FAN Board Alarm List

9.2.10 ODU Alarm List

9.2.1 SL91CXPR Board Alarm ListBD_NOT_INSTALLED LTI RELAY_ALARM_MINOR

BD_STATUS MPLS_TUNNEL_BDI S1_SYN_CHANGE

BFD_DOWN MPLS_TUNNEL_Excess SECU_ALM

BUS_ERR MPLS_TUNNEL_FDI SWDL_ACTIVATED_TIMEOUT

CFCARD_FAILED MPLS_TUNNEL_LOCV SWDL_AUTOMATCH_INH

CFCARD_OFFLINE MPLS_TUNNEL_MISMATCH

SWDL_COMMIT_FAIL

CLK_NO_TRACE_MODE MPLS_TUNNEL_MISMERGE

SWDL_INPROCESS

COMMUN_FAIL MPLS_TUNNEL_SD SWDL_NEPKGCHECK

DBMS_ERROR MPLS_TUNNEL_SF SWDL_PKG_NOBDSOFT

DBMS_PROTECT_MODE MPLS_TUNNEL_UNKNOWN

SWDL_PKGVER_MM

ETH_APS_LOST MSSW_DIFFERENT SWDL_ROLLBACK_FAIL

ETH_APS_PATH_MISMATCH

NESF_LOST SYN_BAD

ETH_APS_SWITCH_FAIL NESTATE_INSTALL SYNC_C_LOS

ETH_APS_TYPE_MISMATCH

PATCH_ACT_TIMEOUT SYNC_DISABLE

EXT_SYNC_LOS PATCH_DEACT_TIMEOUT

SYNC_F_M_SWITCH

EXT_TIME_LOC PATCH_ERR SYNC_FAIL

GSP_ISIS_NB_AUTH_ERR

PATCH_PKGERR SYNC_LOCKOFF

GSP_RSVP_NB_AUTH_ERR

PATCHFILE_NOTEXIST SYSLOG_COMM_FAIL

GSP_RSVP_NB_DOWN POWER_ABNORMAL TEMP_OVER

GSP_TNNL_DOWN PW_DOWN TR_LOC



9-9

HARD_BAD RELAY_ALARM_CRITICAL

W_OFFLINE

LAG_DOWNRELAY_ALARM_IGNORE

WRG_BD_TYPE

LAG_MEMBER_DOWN RELAY_ALARM_MAJOR -

9.2.2 TND1EF8T Board Alarm List

ETH_LOS LOOP_ALM HARD_BAD

ETH_LINK_DOWN ETH_AUTO_LINK_DOWN

BD_STATUS

MAC_FCS_EXC TEMP_OVER TR_LOC

FLOW_OVER POWER_ABNORMAL WRG_BD_TYPE

9.2.3 TND1EF8F Board Alarm List

BD_STATUS LASER_MOD_ERR OUT_PWR_ABN

ETH_AUTO_LINK_DOWN

LASER_SHUT POWER_ABNORMAL

ETH_LINK_DOWN LOOP_ALM TEM_HA

ETH_LOS LSR_BCM_ALM TEM_LA

FLOW_OVER LSR_NO_FITED TEMP_OVER

HARD_BAD LSR_WILL_DIE TR_LOC

IN_PWR_ABN MAC_FCS_EXC WRG_BD_TYPE

9.2.4 TND1EG2 Board Alarm List

BD_STATUS LASER_MOD_ERR OUT_PWR_ABN

ETH_AUTO_LINK_DOWN

LASER_SHUT POWER_ABNORMAL

ETH_LINK_DOWN LOOP_ALM TEM_HA

ETH_LOS LSR_BCM_ALM TEM_LA

FLOW_OVER LSR_NO_FITED TEMP_OVER


Maintenance Guide


Issue 02 (2009-06-30)

HARD_BAD LSR_WILL_DIE TR_LOC

IN_PWR_ABN MAC_FCS_EXC WRG_BD_TYPE

9.2.5 TND1ML1/TND1ML1A Board Alarm ListALM_E1RAI DOWN_E1_AIS PPP_NCP_FAIL

ALM_IMA_LIF HARD_BAD T_ALOS

ALM_IMA_LODS IMA_GROUP_LE_DOWN TEMP_OVER

ALM_IMA_RE_RX_UNUSABLE

IMA_GROUP_RE_DOWN TR_LOC

ALM_IMA_RE_TX_UNUSABLE

IMAE1_DELAY UP_E1_AIS

ALM_IMA_RFI LFA VC_AIS

BD_STATUS LMFA VC_LOC

CES_JTROVR_EXC LOOP_ALM VC_RDI

CES_JTRUDR_EXC MP_DELAY VP_AIS

CES_LOSPKT_EXC MP_DOWN VP_LOC

CES_MALPKT_EXC POWER_ABNORMAL VP_RDI

CES_MISORDERPKT_EXC

PPP_LCP_FAIL WRG_BD_TYPE

CES_STRAYPKT_EXC - -

9.2.6 TND1IFE2 Board Alarm ListAM_DOWNSHIFT BUS_ERR HARD_BAD

IF_CABLE_OPEN LOOP_ALM MW_BER_EXC

MW_BER_SD MW_FECUNCOR MW_LIM

MW_LOF MW_RDI R_LOC

RADIO_FADING_MARGIN_INSUFF

RPS_INDI TEMP_ALARM

TR_LOC VOLT_LOS WRG_BD_TYPE



9-11

9.2.7 TND1AUXQ Board Alarm ListBD_STATUS FLOW_OVER POWER_ABNORMAL

ETH_AUTO_LINK_DOWN

HARD_BAD TEMP_OVER

ETH_LINK_DOWN LOOP_ALM TR_LOC

ETH_LOS MAC_FCS_EXC WRG_BD_TYPE

9.2.8 TND1PIU Board Alarm ListBD_STATUS THUNDERALM WRG_BD_TYPE

POWER_ABNORMAL - -

9.2.9 TND1FAN Board Alarm ListBD_STATUS FAN_FAIL WRG_BD_TYPE

9.2.10 ODU Alarm ListBD_STATUS CONFIG_NOSUPPORT HARD_BAD

IF_INPWR_ABN LOOP_ALM POWER_ALM

RADIO_MUTE RADIO_RSL_LOW RADIO_RSL_HIGH

RADIO_TSL_LOW RADIO_TSL_HIGH TEMP_ALARM

9.3 Alarm HandlingThis chapter describes how to handle related alarms of the equipment.

9.3.1 Alarm Handling FlowThis section describes the flowchart for handling alarms on the OptiX RTN 950 equipment.

9.3.2 AM_DOWNSHIFT

9.3.3 ALM_ALS

9.3.4 ALM_E1RAI

9.3.5 ALM_IMA_LIF

9.3.6 ALM_IMA_LODS


Maintenance Guide


Issue 02 (2009-06-30)

9.3.7 ALM_IMA_RE_RX_UNUSABLE

9.3.8 ALM_IMA_RE_TX_UNUSABLE

9.3.9 ALM_IMA_RFI

9.3.10 BD_NOT_INSTALLED

9.3.11 BD_STATUS

9.3.12 BFD_DOWN

9.3.13 BUS_ERR

9.3.14 CES_JTROVR_EXC

9.3.15 CES_JTRUDR_EXC

9.3.16 CES_LOSPKT_EXC

9.3.17 CES_MALPKT_EXC

9.3.18 CES_MISORDERPKT_EXC

9.3.19 CES_STRAYPKT_EXC

9.3.20 CFCARD_FAILED

9.3.21 CFCARD_OFFLINE

9.3.22 CLK_NO_TRACE_MODE

9.3.23 COMMUN_FAIL

9.3.24 CONFIG_NOSUPPORT

9.3.25 DBMS_ERROR

9.3.26 DBMS_PROTECT_MODE

9.3.27 DOWN_E1_AIS

9.3.28 ETH_APS_LOST

9.3.29 ETH_APS_PATH_MISMATCH

9.3.30 ETH_APS_SWITCH_FAIL

9.3.31 ETH_APS_TYPE_MISMATCH

9.3.32 ETH_AUTO_LINK_DOWN

9.3.33 ETH_LINK_DOWN

9.3.34 ETH_LOS

9.3.35 EXT_SYNC_LOS

9.3.36 EXT_TIME_LOC

9.3.37 FAN_FAIL

9.3.38 FLOW_OVER

9.3.39 GSP_ISIS_NB_AUTH_ERR



9-13

9.3.40 GSP_RSVP_NB_AUTH_ERR

9.3.41 GSP_RSVP_NB_DOWN

9.3.42 GSP_TNNL_DOWN

9.3.43 HARD_BAD

9.3.44 IMA_GROUP_LE_DOWN

9.3.45 IMA_GROUP_RE_DOWN

9.3.46 IMAE1_DELAY

9.3.47 IN_PWR_ABN

9.3.48 LAG_DOWN

9.3.49 LAG_MEMBER_DOWN

9.3.50 LASER_MOD_ERR

9.3.51 LASER_SHUT

9.3.52 LFA

9.3.53 IF_CABLE_OPEN

9.3.54 IF_INPWR_ABN

9.3.55 LMFA

9.3.56 LOOP_ALM

9.3.57 LSR_BCM_ALM

9.3.58 LSR_NO_FITED

9.3.59 LSR_WILL_DIE

9.3.60 LTI

9.3.61 MAC_FCS_EXC

9.3.62 MP_DELAY

9.3.63 MP_DOWN

9.3.64 MPLS_TUNNEL_BDI

9.3.65 MPLS_TUNNEL_Excess

9.3.66 MPLS_TUNNEL_FDI

9.3.67 MPLS_TUNNEL_LOCV

9.3.68 MPLS_TUNNEL_MISMATCH

9.3.69 MPLS_TUNNEL_MISMERGE

9.3.70 MPLS_TUNNEL_SD

9.3.71 MPLS_TUNNEL_SF

9.3.72 MPLS_TUNNEL_UNKNOWN


Maintenance Guide


Issue 02 (2009-06-30)

9.3.73 MW_BER_EXC

9.3.74 MW_BER_SD

9.3.75 MW_LIM

9.3.76 MW_LOF

9.3.77 MW_RDI

9.3.78 MW_FECUNCOR

9.3.79 MSSW_DIFFERENT

9.3.80 NESF_LOST

9.3.81 NESTATE_INSTALL

9.3.82 OUT_PWR_ABN

9.3.83 PATCH_ACT_TIMEOUT

9.3.84 PATCH_DEACT_TIMEOUT

9.3.85 PATCH_ERR

9.3.86 PATCH_PKGERR

9.3.87 PATCHFILE_NOTEXIST

9.3.88 POWER_ABNORMAL

9.3.89 POWER_ALM

9.3.90 PPP_LCP_FAIL

9.3.91 PPP_NCP_FAIL

9.3.92 PW_DOWN

9.3.93 R_LOC

9.3.94 RADIO_FADING_MARGIN_INSUFF

9.3.95 RADIO_RSL_LOW

9.3.96 RADIO_RSL_HIGH

9.3.97 RADIO_TSL_LOW

9.3.98 RADIO_TSL_HIGH

9.3.99 RADIO_MUTE

9.3.100 RELAY_ALARM_CRITICAL

9.3.101 RELAY_ALARM_MAJOR

9.3.102 RELAY_ALARM_MINOR

9.3.103 RELAY_ALARM_IGNORE

9.3.104 RPS_INDI

9.3.105 S1_SYN_CHANGE



9-15

9.3.106 SECU_ALM

9.3.107 SWDL_ACTIVATED_TIMEOUT

9.3.108 SWDL_AUTOMATCH_INH

9.3.109 SWDL_COMMIT_FAIL

9.3.110 SWDL_INPROCESS

9.3.111 SWDL_NEPKGCHECK

9.3.112 SWDL_PKG_NOBDSOFT

9.3.113 SWDL_PKGVER_MM

9.3.114 SWDL_ROLLBACK_FAIL

9.3.115 SYN_BAD

9.3.116 SYNC_C_LOS

9.3.117 SYNC_DISABLE

9.3.118 SYNC_F_M_SWITCH

9.3.119 SYNC_FAIL

9.3.120 SYNC_LOCKOFF

9.3.121 SYSLOG_COMM_FAIL

9.3.122 T_ALOS

9.3.123 TEM_HA

9.3.124 TEM_LA

9.3.125 TEMP_ALARM

9.3.126 TEMP_OVER

9.3.127 THUNDERALM

9.3.128 TR_LOC

9.3.129 UP_E1_AIS

9.3.130 VC_AIS

9.3.131 VC_LOC

9.3.132 VC_RDI

9.3.133 VOLT_LOS

9.3.134 VP_AIS

9.3.135 VP_LOC

9.3.136 VP_RDI

9.3.137 WRG_BD_TYPE


Maintenance Guide


Issue 02 (2009-06-30)

9.3.1 Alarm Handling FlowThis section describes the flowchart for handling alarms on the OptiX RTN 950 equipment.

Prerequisitel You must log in to the T2000 and display the Main Topology.

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

Alarm-Handling Flowchart

Figure 9-4 describes the process of handling alarms on the OptiX RTN 950 equipment.

Figure 9-4 Flowchart for handling alarms

Display Browse Current Alarms interface

Start

Query alarm locating information

Whetherthe alarms are

cleared

Clear the alarms according to the handling procedures

End

Whetherthere are alarm

parameters

Record alarm parameters

Yes

Click Details to display Online Help

No Click Details to display Online Help

Locate the alarm causes and clear the alarms step

by step according to handling procedure

Contact Huawei engineers for technical support

Yes

No

Whetheralarm parameters

indicate alarm causes

Yes

No



9-17

Procedure

Step 1 On the Main Topology of the T2000, right-click the NE icon and choose Fault > BrowseCurrent Alarms to display the Browse Current Alarms dialog box.

Step 2 View the Locating Info column and record the locating information for each alarm.

NOTE

l The alarm locating information includes the NE that reports the alarm, slot number, board name, sub-slot number, sub-board name, port ID, channel ID, clock source number, and other index information.

l The locating information is specific to alarms.

l If an alarm is displayed on a green background, it indicates that the alarm is cleared.

Step 3 Query and record alarm parameters in the Alarm Details field in the lower left corner.

NOTE

Certain alarm parameters indicate the alarm causes. The T2000 detects and analyzes the alarm causes, anddisplays the alarm information. You can quickly find the causes of alarms according to such alarmparameters.

Step 4 In the Handling Suggestion field in the lower right corner, click Details to display the T2000Online Help interface, where the details on alarm handling are displayed.


Maintenance Guide


Issue 02 (2009-06-30)

l If there are alarm parameters, check whether the alarm parameters indicate the alarm causes.If yes, go to Step 5.

l If not, go to Step 6.

l If there are no alarm parameters, go to Step 6.

Step 5 Try to clear the alarms according to the handling procedure for each alarm.

Go to Step 7.

Step 6 Find the cause of each alarm and clear the alarms step by step according to the Online Help andexperience of handling alarms.

Step 7 On the T2000, make sure that the alarms are cleared and no new alarm occurs.

NOTE

If any of the alarms cannot be cleared according to the Online Help, contact Huawei engineers for technicalsupport. For the contact information, see 3.15 Fault Notification and Technical Support.

----End

9.3.2 AM_DOWNSHIFT

DescriptionThe AM_DOWNSHIFT is an alarm indicating the downshift of the AM scheme. This alarmoccurs when the AM scheme is downshifted from the highest-efficiency scheme to the lower-efficiency scheme. When the AM scheme is upshifted from the lower-efficiency scheme to thehighest scheme, this alarm is cleared.

Attribute

Alarm ID Alarm Severity Alarm Type

0x32FA Major Communication alarm

ParametersNone.

None.



9-19

Impact on SystemWhen the AM_DOWNSHIFT alarm occurs, the transmission capacity is reduced.

Possible CausesThe possible cause of the AM_DOWNSHIFT alarm is the degradation of the working channels.l The external factors (for example, the climate) cause the degradation of the working

channels.l There are interferences around the working channels.

l The ODU at the transmit end has abnormal transmit power.

l The ODU at the receive end has abnormal receive power.

Handling Procedure

Step 1 Check whether the external factors (for example, the climate) cause the degradation of theworking channels.

If... Then...

Yes The downshift is a normal phenomenon and there is no need to handle it.

No Proceed to next step.

Step 2 Check whether there are interferences around the working channels.

If... Then...

Yes Eliminate the interferences.


Step 3 Use the T2000 to check whether the transmit power of the ODU at the transmit end is abnormal.

If... Then...

Yes Rectify the fault according to the alarm at the transmit end. For how to rectify the fault,see "Troubleshooting Microwave Links".


Step 4 Rectify the fault of the receive power at the receive end.

----End

Related InformationNone.


Maintenance Guide


Issue 02 (2009-06-30)

9.3.3 ALM_ALS

Description

The ALM_ALS is an alarm of automatic laser shutdown (ALS). When the ALS function isenabled on an optical interface of the board, but no input of light is detected, the laser is shutdown automatically. In this case, this alarm occurs on the board.

Attribute


0x0128 Minor Equipment alarm

Parameters

None.

None.

Impact on System

When the ALM_ALS alarm occurs, the system will suppresses the LSR_BCM_ALM andOUT_PWR_ABN alarms.

Possible Causes

The cause of the ALM_ALS alarm is as follows:

The laser detects no input of light and the ALS function is enabled.

Handling Procedure

l Cause: The laser detects no input of light and the ALS function is enabled.

1. Disable the ALS function, and the alarm will be cleared automatically.

2. Optional: Rectify the faulty of no input of light, and then restart the ALS function.

----End

Related Information

None.

9.3.4 ALM_E1RAI

Description

The ALM_E1RAI is an E1 link alarm indicator on the opposite NE.



9-21

Attribute


0xf886 Minor Communication alarm

ParametersNone

None

Impact on SystemWhen the ALM_E1RAI alarm occurs, the downlink services on the local NE are interrupted.

Possible CausesThe possible causes of the ALM_E1RAI alarm are as follows:

l Cause 1: The T_ALOS, LFA, LMFA, UP_E1_AIS or DOWN_E1_AIS alarm occurs at theopposite end of the E1 link, and the local end receives the ALM_E1RAI alarm inserted inthe downstream by the opposite end.

l Cause 2: The physical link is interrupted.

Handling Procedurel Cause 1: The T_ALOS, LFA, LMFA, UP_E1_AIS or DOWN_E1_AIS alarm occurs at the

opposite end of the E1 link, and the local end receives the ALM_E1RAI alarm inserted inthe downstream by the opposite end.1. Check whether the T_ALOS, LFA, LMFA, UP_E1_AIS, or DOWN_E1_AIS alarm

occurs at the opposite end of the E1 link. For details, refer to 8.2 Querying CurrentAlarms of a Board.

2. If yes, clear these alarms on the opposite NE firstly. Then, check whether theALM_E1RAI alarm is cleared.

l Cause 2: The physical link is interrupted.1. Check whether the physical link to the opposite NE is interrupted.2. If yes, modify the interrupted physical link.

----End


9.3.5 ALM_IMA_LIF

DescriptionThe ALM_IMA_LIF is an alarm of out-of-frame in the IMA link. This alarm indicatesdelimitation of received IMA frames is lost on the local NE.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


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

Name Meaning

Parameter 1, Parameter 2 Indicates the ATM trunk.

Impact on Systeml In the case of the ALM_IMA_LIF alarm, the IMA link in the IMA group indicated by the

alarm parameter is unavailable and thus the number of available links in the IMA groupdecreases. If the service bandwidth configured for this IMA group is greater than the servicebandwidth of the available links in the IMA group, congestion occurs at the IMA ports. Asa result, the cells are lost.

l After the ALM_IMA_LIF alarm is cleared, the IMA link automatically becomes available.

l The ALM_IMA_LIF alarm will be suppressed when the UP_E1_AIS alarms occurs.

Possible CausesThe possible causes of the ALM_IMA_LIF alarm are as follows:

l Cause 1: The IMA protocols at the two ends fail to negotiate with each other.

l Cause 2: The physical link for the IMA link becomes faulty.

Handling Procedurel Cause 1: The IMA protocols at the two ends fail to negotiate with each other.

1. On the T2000, set the IMA Protocol Enable Status parameter to Disabled for theNEs at the two ends. For details, refer to Configuring the IMA in FeatureDescription.

2. Check the configuration of the IMA group at the two ends and ensure that the IMAgroup parameters are matched.

3. Set the IMA Protocol Enable Status parameter to Enabled for the NEs at the twoends to re-activate the IMA protocol. Then, check whether the alarm is cleared.

l Cause 2: The physical link for the IMA link becomes faulty.1. Check whether the fibers or cables are correctly connected to the ports on the NEs at

the two ends. If not, correct the fiber or cable connection.



9-23

2. Check whether the fibers or cables are faulty. If yes, replace the fibers or cables.

----End

Related InformationFrame delimitation out-of-frame

The physical layer performs frame delimitation. The start bytes of frames indicate the start pointof the field carrying information. If the frame delimitation bytes in the input bit stream areunknown, the bit stream is considered as out-of-frame.

9.3.6 ALM_IMA_LODS

DescriptionThe ALM_IMA_LODS is an alarm indicating that the differential delay in the IMA link crossesthe threshold. This alarm indicates that the maximum differential delay among the receive linksin the local IMA group crosses the threshold.

Attribute


0xf87f Major Communication alarm


Name Meaning


Impact on Systeml In the case of the ALM_IMA_LODS alarm, the IMA link in the IMA group indicated by

the alarm parameter is unavailable and thus the number of available links in the IMA groupdecreases. If the service bandwidth configured for this IMA group is greater than the servicebandwidth of the available links in the IMA group, congestion occurs at the IMA ports. Asa result, the cells are lost.

l After the ALM_IMA_LODS alarm is cleared, the IMA link automatically becomesavailable.

Possible CausesThe possible causes of the ALM_IMA_LODS alarm are as follows:


Maintenance Guide


Issue 02 (2009-06-30)



Handling Procedure

l Cause 1: The IMA protocols at the two ends fail to negotiate with each other.1. On the T2000, set the IMA Protocol Enable Status parameter to Disabled for the

NEs at the two ends. For details, refer to Configuring the IMA in FeatureDescription.




the two ends. If not, correct the fiber or cable connection.2. Check whether the fibers or cables are faulty. If yes, replace the fibers or cables.

----End

Related Information

Differential Delay

Differential delay indicates the delay difference of the services among the E1 links. A buffer of1024 cells is provided for delay in each E1 link. The maximum differential delay is 256 ms.

9.3.7 ALM_IMA_RE_RX_UNUSABLE

Description

The ALM_IMA_RE_RX_UNUSABLE is an alarm indicating the unavailability of receivingsignals in the IMA link on the opposite NE. This alarm indicates that the IMA link fails to receivesignals and is unavailable.

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.



9-25

Name Meaning


Impact on Systeml In the case of the ALM_IMA_RE_RX_UNUSABLE alarm, the IMA link in the IMA group

indicated by the alarm parameter is unavailable and thus the number of available links inthe IMA group decreases. If the service bandwidth configured for this IMA group is greaterthan the service bandwidth of the available links in the IMA group, congestion occurs atthe IMA ports. As a result, the cells are lost.

l After the ALM_IMA_RE_RX_UNUSABLE alarm is cleared, the IMA link automaticallybecomes available.

Possible CausesThe possible causes of the ALM_IMA_RE_RX_UNUSABLE alarm are as follows:









----End


9.3.8 ALM_IMA_RE_TX_UNUSABLE

DescriptionThe ALM_IMA_RE_TX_UNUSABLE is an alarm indicating the unavailability of transmittingsignals in the IMA link on the opposite NE. This alarm indicates that the IMA link fails totransmit signals and is unavailable.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters


Name Meaning


Impact on Systeml In the case of the ALM_IMA_RE_TX_UNUSABLE alarm, the IMA link in the IMA group

indicated by the alarm parameter is unavailable and thus the number of available links inthe IMA group decreases. If the service bandwidth configured for this IMA group is greaterthan the service bandwidth of the available links in the IMA group, congestion occurs atthe IMA ports. As a result, the cells are lost.

l After the ALM_IMA_RE_TX_UNUSABLE alarm is cleared, the IMA link automaticallybecomes available.

Possible Causes

The possible causes of the ALM_IMA_RE_TX_UNUSABLE alarm are as follows:



Handling Procedure

l Cause 1: The IMA protocols at the two ends fail to negotiate with each other.1. On the T2000, set the IMA Protocol Enable Status parameter to Disabled for the

NEs at the two ends. For details, refer to Configuring the IMA in FeatureDescription.




the two ends. If not, correct the fiber or cable connection.



9-27

2. Check whether the fibers or cables are faulty. If yes, replace the fibers or cables.

----End

Related Information

None.

9.3.9 ALM_IMA_RFI

Description

The ALM_IMA_RFI alarm indicates out-of-frame of the frames received in the remote IMAlink. When delimitating the frames received in the remote IMA link fails, the ALM_IMA_RFIalarm is reported.

Attribute


0xf880 Major Communication alarm

Parameters


Name Meaning


Impact on Systeml In the case of the ALM_IMA_RFI alarm, the IMA link in the IMA group indicated by the

alarm parameter is unavailable and thus the number of available links in the IMA groupdecreases. If the service bandwidth configured for this IMA group is greater than the servicebandwidth of the available links in the IMA group, congestion occurs at the IMA ports. Asa result, the cells are lost.

l After the ALM_IMA_RFI alarm is cleared, the IMA link automatically becomes available.

Possible Causes

The possible causes of the ALM_IMA_RFI alarm are as follows:




Maintenance Guide


Issue 02 (2009-06-30)







----End

Related InformationFrame delimitation out-of-frame

The physical layer performs frame delimitation. The start bytes of frames indicate the start pointof the field carrying information. If the frame delimitation bytes in the input bit stream areunknown, the bit stream is considered as out-of-frame.

9.3.10 BD_NOT_INSTALLED

DescriptionThe BD_NOT_INSTALLED is an alarm indicating that the logical board is not created in thecorresponding slot. If a physical board is inserted in the corresponding slot, but the logical boardis not created on the T2000, the CXPR reports the BD_NOT_INSTALLED alarm.

Attribute



ParametersNone.

None.

Impact on Systeml When the BD_NOT_INSTALLED alarm occurs, the corresponding board cannot be

configured with services.l Alarms will not occur on the board which reports the BD_NOT_INSTALLED alarm.



9-29

Possible CausesThe causes of the BD_NOT_INSTALLED alarm is as follows:

A physical board is inserted in the slot, but the corresponding logical board is not created on theT2000.

Handling Procedurel Cause: A physical board is inserted in the slot, but the corresponding logical board is not

created on the T2000.1. Check whether the physical board keeps in use.

– If yes, go to step 2.

– If not, go to step 3.

2. On the T2000, add the logical board to the corresponding slot, and then the alarm isautomatically cleared. For details, refer to Adding Boards in the ConfigurationGuide manual.

3. Remove the board from the equipment and keep it in proper storage with anti-staticbag. The alarm will be automatically cleared.

----End


9.3.11 BD_STATUS

DescriptionThe BD_STATUS alarm indicates that the physical board is out of service. When the logicalboard is created on the T2000 but the physical board is not inserted in the equipment, theBD_STATUS alarm is reported.

Attribute


0x77 Major Equipment alarm

ParametersNone.

None.

Impact on Systeml The physical board is not inserted in the equipment, and thus the configuration data on the

system control board cannot be delivered to this physical board. As a result, configurationof services fails.


Maintenance Guide


Issue 02 (2009-06-30)

l Alarms will not occur on the board which reports the BD_STATUS alarm.

Possible Causes

The possible causes of the BD_STATUS alarm are as follows:

l Cause 1: The board is undergoing cold reset.

l Cause 2: The board is not inserted, or the board is inserted but in poor contact with thebackplane.

l Cause 3: The inter-board communication fails.

Handling Procedure

l Cause 1: The board is undergoing cold reset.

1. On the T2000, Check whether the working status of the board is displayed in blue inthe Running Status basic slots. If yes, the board is undergoing cold reset.

2. Wait for three to five minutes and the working status of the board turns green and isalways on. Then, check whether the BD_STATUS alarm ends.

l Cause 2: The board is not inserted, or the board is inserted but in poor contact with thebackplane.

1. Check whether the board is not inserted. If yes, insert the board.

2. Check whether the board properly contacts the backplane or the pins of connectors onthe backplane are all normal. If not, recover the abnormal pins and reinsert the board.

l Cause 3: The inter-board communication fails.

1. On the T2000. check whether the HARD_BAD or COMMUN_FAIL alarm occurson the board which reports the BD_STATUS alarm or on the system control board.

2. If yes, replace the board and then check whether the BD_STATUS alarm is cleared.For details, refer to 8.2 Querying Current Alarms of a Board.

----End

Related Information

None.

9.3.12 BFD_DOWN

Description

The BFD_DOWN is a BFD session interruption alarm. When the port detects that the BFD stateturns to DOWN, this alarm is reported.

Attribute


0x327F Minor Communication alarm



9-31

Parameters

None.

None.

Impact on System

When the BFD session is interrupted, the LPT switching is triggered.

Possible Causes

The possible causes of the BFD_DOWN alarm are as follows:

l Cause 1: The port is not enabled.

l Cause 2: The Tag configured at the two ends is inconsistent.

l Cause 3: The board of the opposite NE is faulty.

l Cause 4: The fiber or cable is faulty.

Handling Procedure

l Cause 1: The port is not enabled.1. On the T2000, check whether the ports at the two ends are all enabled. For details,

refer to Setting the General Attributes of Ethernet Interfaces in OptiX RTN 950 RadioTransmission System Configuration Guide manual.

2. If not, enable the ports first and then check whether the alarm is cleared.l Cause 2: The Tag configured at the two ends is inconsistent.

1. On the T2000, check whether the Tag configured at the two ends is consistent. Fordetails, refer to Setting the Layer 2 Attributes of Ethernet Interfaces in OptiX RTN950 Radio Transmission System Configuration Guide manual.

2. If not, modify the configuration to match each other and then check whether the alarmis cleared.

l Cause 3: The board of the opposite NE is faulty.1. Check whether any hardware alarm, such as the HARD_BAD alarm, occurs on the

opposite NE.2. If yes, clear the hardware alarm on the opposite NE first and then check whether the

BFD_DOWN alarm is cleared.l Cause 4: The fiber or cable is faulty.

1. Check whether the fiber or cable connected to the port is loose. If yes, fasten the loosefiber or cable.

2. If the BFD_DOWN alarm persists, replace the fiber or cable and then check whetherthe BFD_DOWN alarm is cleared.

----End

Related Information

None.


Maintenance Guide


Issue 02 (2009-06-30)

9.3.13 BUS_ERR

Description

The BUS_ERR alarm indicates that the bus is faulty. When the board detects that the busbecomes abnormal, the BUS_ERR alarm is reported.

Attribute


0x179 Critical Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the type of bus faults.

l 0x01: BUS_LOS.

l 0x02: BUS_OOF.

l 0x03: BUS_LOF.

l 0x04: BUS_OOA.

l 0x05: BUS_RX_DOWN. Refer to Cause 3.

l 0x06: BUS_TX_DOWN.

l 0x07: BUS_SPI_DOWN.

l 0x08: BUS_SCI_ERR.

l 0x09: BUS_OPP_CLK_LOC.

Parameter 2 Indicates the number of the faulty bus .

Impact on Systeml In the case of the BUS_ERR alarm, the services that are transmitted over the bus are

interrupted or have bit errors.l The BUS_ERR alarm will be suppressed when the HARD_BAD alarm occurs.

Possible Causes

The possible causes of the BUS_ERR alarm are as follows:



9-33

l Cause 1: The board is not properly housed in the slot.


l Cause 3: The board detects the inter-board bus is abnormal.

Handling Procedurel Cause 1: The board is not properly housed in the slot.

1. Check whether the pins on the backplane are in normal status. If not, modify theabnormal pins.

2. Re-insert the board that reports the BUS_ERR alarm. For details, refer to 8.19Replacing Boards on Site.

l Cause 2: The board is faulty.1. Cold-reset the board that reports the BUS_ERR alarm. For details, refer to 8.16

Resetting Boards.2. If the BUS_ERR alarm persists, replace the board that reports this alarm. For details,

refer to 5 Replacing Components.l Cause 3: The board detects the inter-board bus is abnormal.

1. On the T2000, check whether the alarms, which indicates the clock source is lost oris degraded, occurs. For details, refer to 8.2 Querying Current Alarms of a Board.

2. If yes, clear the clock-related alarms first, and then check whether the BUS_ERRalarm is cleared.

3. If the BUS_ERR alarm persists, check whether the board is properly housed in theslot. Please refer to the handling procedure of Cause 1.

----End


9.3.14 CES_JTROVR_EXC

DescriptionThe CES_JTROVR_EXC is an alarm indicating that the number of jitter buffer overflowsexceeds the specified threshold value. If the number of jitter buffer overflows exceeds thespecified threshold value in a period (by default, 2.5s), this alarm occurs.

Attribute


0x3201 Major Communication alarm

ParametersNone.

None.


Maintenance Guide


Issue 02 (2009-06-30)

Impact on Systeml The buffer area does not have enough space for the received frames, and thus the packet

loss occurs.l If the number of jitter buffer overflows is lower than the specified threshold value in another

period (by default, 10s), this alarm is cleared automatically.l The CES_JTROVR_EXC alarm will be suppressed when the CES_LOSPKT_EXC alarm

occurs.

Possible CausesThe possible causes of the CES_JTROVR_EXC alarm are as follows:

l Cause 1: The clocks may be not synchronous.

l Cause 2: The set buffer area is too small.

Handling Procedurel Cause 1: The clocks may be not synchronous.

1. On the T2000, check whether there is the LTI alarm, which indicates the clocks arenot synchronous so that the ingress rate and egress rate of the buffer area areinconsistent.

2. If yes, clear the LTI alarm first, and then check whether the CES_JTROVR_EXCalarm is cleared.

l Cause 2: The set buffer area is too small.1. On the T2000, query the configuration value of the buffer area. For details, refer to

CES Service Operation Tasks in the Configuration Guide manual.2. According to the network plan, confirm whether the Jitter Compensation Buffering

Time can be set to a bigger value. If yes, expand the buffer area. Then, check whetherthe alarm is cleared.

----End


9.3.15 CES_JTRUDR_EXC

DescriptionThe CES_JTRUDR_EXC is an alarm indicating that the number of jitter buffer underflowsexceeds the specified threshold value. If the number of jitter buffer underflows continuouslyexceeds the specified threshold value in a period (by default, 2.5s), this alarm occurs.

Attribute





9-35

Parameters

None.

None.

Impact on Systeml No packets are transmitted in the buffer area, and thus the buffer area underflows.

l If the number of jitter buffer underflows is continuously lower than the specified thresholdvalue in another period (by default, 10s), this alarm is cleared automatically.

l The CES_JTRUDR_EXC alarm will be suppressed when the CES_LOSPKT_EXC alarmoccurs.

Possible Causes

The possible causes of the CES_JTRUDR_EXC alarm are as follows:



Handling Procedure


1. On the T2000, check whether there is the LTI alarm, which indicates the clocks arenot synchronous so that the ingress rate and egress rate of the buffer area areinconsistent.

2. If yes, clear the LTI alarm first, and then check whether the CES_JTRUDR_EXCalarm is cleared.


1. On the T2000, query the configuration value of the buffer area. For details, refer toCES Service Operation Tasks in the Configuration Guide manual.

2. According to the network plan, confirm whether the Jitter Compensation BufferingTime can be set to a bigger value. If yes, expand the buffer area. Then, check whetherthe alarm is cleared.

----End

Related Information

None.

9.3.16 CES_LOSPKT_EXC

Description

The CES_LOSPKT_EXC is an alarm indicating that the number of lost CES packets exceedsthe specified threshold value in a unit time. If the number of lost frames continuously exceedsthe specified threshold value in a period (by default, 2.5s), this alarm occurs.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


0x31FC Major Communication alarm

Parameters

None.

None.

Impact on Systeml When the packet loss rate exceeds the threshold value, the all "1"s signal is inserted in the

downstream. Thus, the services may be interrupted.l If the number of lost frames is continuously lower than the specified threshold value in

another period (by default, 10s), this alarm is cleared automatically.l When the CES_LOSPKT_EXC alarm occurs, the system suppresses the

CES_JTROVR_EXC, CES_JTRUDR_EXC, CES_MALPKT_EXC,CES_MISORDERPKT_EXC and CES_STRAYPKT_EXC alarms.

Possible Causes

The possible causes of the CES_LOSPKT_EXC alarm are as follows:

l Cause 1: The bandwidth configured to the tunnel or PW is so low that the link is baffled.

l Cause 2: The cable, fiber or optical module is faulty and the signals on the link degrades.

Handling Procedure

l Cause 1: The bandwidth configured to the tunnel or PW is so low that the link is baffled.1. On the T2000, check whether the bandwidth configured to the tunnel or PW which

carries the service is too low.2. If yes, re-configure the tunnel or PW with a bigger bandwidth. Then, check whether

the alarm is cleared.l Cause 2: The cable, fiber or optical module is faulty and the signals on the link degrades.

1. Make sure that the cable or fiber is well connected to the port.2. Optional: clean the fiber and the optical module and then check whether the alarm is

cleared. For details, refer to 8.24 Inspecting and Cleaning the Optical FiberConnectors.

3. If the CES_LOSPKT_EXC alarm persists, replace the related fiber or optical module.For details, refer to 5.9 Replacing the Pluggable Optical Module.

----End

Related Information

None.



9-37

9.3.17 CES_MALPKT_EXC

DescriptionThe CES_MALPKT_EXC is an alarm indicating that the number of deformed CES packetsexceeds the specified threshold value in a unit time. If the CESoETH frame contains valid TDMdata without any error indication, but the data frame is not of the specified size, this frame istaken as a deformed frame. If the number of deformed frames continuously exceeds the specifiedthreshold value in a period (by default, 2.5s), this alarm occurs.

Attribute


0x31FC Major Communication alarm

ParametersNone.

None.

Impact on Systeml When the deformed frames are detected and then discarded, the packet loss rate is too high.

l If the rate of deformed frames is continuously lower than the specified threshold value inanother period (by default, 10s), this alarm is cleared automatically.

l The CES_MALPKT_EXC alarm will be suppressed when either the CES_LOSPKT_EXCalarm or the CES_STRAYPKT_EXC alarm occurs.

Possible CausesThe possible causes of the CES_MALPKT_EXC alarm are as follows:

l Cause 1: The configured parameters of the service is incorrect, such as the high path.



Handling Procedurel Cause 1: The configured parameters of the service is incorrect, such as the high path.

1. On the T2000, check whether the parameters of the service is correctly configured.For details, refer to CES Service Operation Tasks in the Configuration Guide manual.

2. If not, modify the parameter of the service and then check whether the alarm is cleared.l Cause 2: The bandwidth configured to the tunnel or PW is so low that the link is baffled.

1. On the T2000, check whether the bandwidth configured to the tunnel or PW whichcarries the service is too low.

2. If yes, re-configure the tunnel or PW with a bigger bandwidth. Then, check whetherthe alarm is cleared.


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 3: The cable, fiber or optical module is faulty and the signals on the link degrades.1. Make sure that the cable or fiber is well connected to the port.2. Optional: clean the fiber and the optical module and then check whether the alarm is



----End

Related Information

None.

9.3.18 CES_MISORDERPKT_EXC

Description

The CES_MISORDERPKT_EXC is an alarm indicating that the number of lost out-of-orderCES packets exceeds specified threshold value in a unit time. If the rate of lost out-of-orderpackets continuously exceeds the specified threshold value in a period (by default, 2.5s), thisalarm occurs.

Attribute


0x31FD Major Communication alarm

Parameters

None.

None.

Impact on Systeml The packets are out of order, and thus the packet loss rate is too high.

l Of the rate of rate out-of-order packets is continuously lower than the specified thresholdvalue in another period (by default, 10s), this alarm is cleared automatically.

l The CES_MISORDERPKT_EXC alarm will be suppressed when either theCES_LOSPKT_EXC alarm or the CES_STRAYPKT_EXC alarm occurs.

Possible Causes

The possible causes of the CES_MISORDERPKT_EXC alarm are as follows:





9-39

Handling Procedure

l Cause 1: The bandwidth configured to the tunnel or PW is so low that the link is baffled.1. On the T2000, check whether the bandwidth configured to the tunnel or PW which

carries the service is too low.2. If yes, re-configure the tunnel or PW with a bigger bandwidth. Then, check whether

the alarm is cleared.l Cause 2: The cable, fiber or optical module is faulty and the signals on the link degrades.

1. Make sure that the cable or fiber is well connected to the port.2. Optional: clean the fiber and the optical module and then check whether the alarm is



----End

Related Information

None.

9.3.19 CES_STRAYPKT_EXC

Description

The CES_STRAYPKT_EXC is an alarm indicating that the number of errored packets exceedsspecified threshold value in a unit time. If the number of errored packets continuously exceedsthe specified threshold value in a period (by default, 2.5s), this alarm occurs.

Attribute


0x31FE Major Communication alarm

Parameters

None.

None.

Impact on Systeml When the errored packets are detected and then discarded, the packet loss rate is too high.

l If the number of errored packets is continuously lower than the specified threshold valuedin another period (by default, 10s), this alarm is cleared automatically.

l The CES_STRAYPKT_EXC alarm will be suppressed when the CES_LOSPKT_EXCalarm occurs.


Maintenance Guide


Issue 02 (2009-06-30)

l When the CES_STRAYPKT_EXC alarm occurs, the system suppresses theCES_MALPKT_EXC and CES_MISORDERPKT_EXC alarms.

Possible Causes

The possible causes of the CES_STRAYPKT_EXC alarm are as follows:

l Cause 1: The parameter configuration of the service is incorrect.

l Cause 2: The fiber or cable is misconnected.

Handling Procedure

l Cause 1: The parameter configuration of the service is incorrect.1. On the T2000, check whether the parameter configuration of the service is correct.2. If not, modify the configuration to recover the correct service. For details, refer to

Configuring a CES Service in the Configuration Guide manual.l Cause 2: The fiber or cable is misconnected.

1. Check whether the fiber or cable is misconnected.2. If yes, reconnect the fiber or calbe and check whether the alarm is cleared.

----End

Related Information

None.

9.3.20 CFCARD_FAILED

Description

The CFCARD_FAILED alarm indicates that the operation on the CF card fails.

Attribute



Parameters

None.

None.

Impact on System

When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.



9-41

Possible Causes

The possible causes of the CFCARD_FAILED alarm are as follows:

l Cause 1: The CF card is faulty and initialization of the CF card fails.

l Cuase 2: The system control board is faulty and creation of the file system of the CF cardfails.

Handling Procedure

l Cause 1: The CF card is faulty and initialization of the CF card fails.1. Replace the CF card and check whether the alarm is cleared. For details, refer to the

OptiX RTN 950 Radio Transmission System IDU Quick Installation Guide manual.l Cause 2: The system control board is faulty and creation of the file system of the CF card

fails.1. Check whether the HARD_BAD alarm occurs on the system control board.2. If yes, cold-reset the system control board. For details, refer to 8.16 Resetting

Boards.3. If the CFCARD_FAILED alarm persists, replace the system control board. For details,

refer to 5 Replacing Components.

----End

Related Information

None.

9.3.21 CFCARD_OFFLINE

Description

The CFCARD_OFFLINE alarm indicates that the CF card is out of service.

Attribute



Parameters

None.

None.

Impact on System

When the CFCARD_FAILED alarm occurs, the database cannot be backed up to the CF cardor be restored from the CF card. This alarm may cause rollback of the package loading upgrade.


Maintenance Guide


Issue 02 (2009-06-30)

Possible CausesThe possible cause of the CFCARD_OFFLINE alarm is as follows:

l Cause 1: The CF card is not inserted.

l Cause 2: The CF card is in poor contact with the system control board.

l Cause 3: The system control board is faulty.

Handling Procedurel Cause 1: The CF card is not inserted.

1. Check whether the CF card is installed on the system control board.2. If not, install the CF card. For details, refer to the OptiX RTN 950 Radio Transmission

System IDU Quick Installation Guide manual.l Cause 2: The CF card is in poor contact with the system control board.

1. Check whether the CF card is loosened. If yes, re-insert the CF card.2. If the CFCARD_OFFLINE alarm persists, replace the CF board.

l Cause 3: The system control board is faulty.1. Check whether the HARD_BAD alarm occurs on the system control board.2. If yes, cold-reset the system control board. For details, refer to 8.16 Resetting

Boards.3. If the CFCARD_FAILED alarm persists, replace the system control board. For details,


----End


9.3.22 CLK_NO_TRACE_MODE

DescriptionThe CLK_NO_TRACE_MODE alarm indicates that the clock enters the non-tracing mode.When the current system clock has no clock source to trace, the CLK_NO_TRACE_MODEalarm is reported.

Attribute


0x014d Minor Equipment 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,



9-43

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

Name Meaning

Parameter 1 l 0x01: The clock changes from the tracing mode to the holdover mode.

l 0x02: The clock enters the free-run mode.

Impact on System

In the case of the CLK_NO_TRACE_MODE alarm, the clock is in the non-tracing mode. Inthis case, the system clock is of low quality. If the low-quality clock results in the asynchronousstate among NEs, the BER of services increases.

Possible Causes

The possible causes of the CLK_NO_TRACE_MOD alarm are as follows:

l Cause 1: The SSM protocol is not enabled.

l Cause 2: The priority table of system clock sources is not configured and the NE adoptsthe default priority table.

l Cause 3: Except the internal clock source, other clock sources in the priority table lose theexistence status and thus are not traceable.

l Cause 4: Except the internal clock source, other clock sources in the priority table haveexcessive frequency deviation and thus are not traceable.

Handling Procedure

l Cause 1: The SSM protocol is not enabled.1. On the T2000, check whether the SSM protocol is enabled at both ends. For details,

refer to Configuring the Clock Source Protection in Configuration Guide manual.2. If not, enable the SSM protocol at both ends.

l Cause 2: The priority table of system clock sources is not configured and the NE adoptsthe default priority table.1. On the T2000, check whether the priority table of clock sources is configured. For

details, refer to Configuring the NE Clock Source.2. If not, re-configure the priority table of clock sources, which should include other

available clock sources.l Cause 3: Except the internal clock source, other clock sources in the priority table lose the

existence status and thus are not traceable.1. On the T2000, check whether there is the SYNC_C_LOS alarm. For details, refer to

8.2 Querying Current Alarms of a Board.2. If yes, clear the SYNC_C_LOS alarm first. Then, the system clock can trace any other

clock source except the internal clock source.l Cause 4: Except the internal clock source, other clock sources in the priority table have

excessive frequency deviation and thus are not traceable.1. On the T2000, check whether there is the SYN_BAD alarm.


Maintenance Guide


Issue 02 (2009-06-30)

2. If yes, clear the SYN_BAD alarm first. Then, the system clock can trace any otherclock source except the internal clock source.

----End


9.3.23 COMMUN_FAIL

DescriptionThe COMMUN_FAIL alarm indicates that the inter-board communication fails. When thecommunication between the system control board and other boards is interrupted, theCOMMUN_FAIL alarm is reported.

Attribute


0xC7 Major Equipment alarm


Name Meaning

Parameter 1 Indicates the slot number of the board which fails in communicating with thesystem control board.

Parameter 2 Reserved. By default, parameter 2 is 0.

Parameter 3 Indicates the path number of the path that reports the alarm. The indication is asfollows:

l 0x01: An alarm that occurs in path 1 of the RS485.

l 0x02: An alarm that occurs in path 2 of the RS485.

l 0x03: Inter-board Ethernet communication.

l 0x04: Inter-subrack Ethernet emergency communication.



9-45

Impact on Systeml When the COMMUN_FAIL alarm occurs, the configuration data on the system control

board cannot be delivered to the board or the board fails to work. As a result, the servicecannot be configured or the equipment-level protection switching fails.

l The COMMUN_FAIL alarm will be suppressed when the HARD_BAD alarm occurs.

Possible CausesIn the case of the COMMUN_FAIL alarm, first check whether one board or multiple boardsreport the COMMUN_FAIL alarm. The possible causes of the COMMUN_FAIL alarm are asfollows:

l Cause 1 for one board reporting the alarm: The board is undergoing cold reset.

l Cause 2 for one board reporting the alarm: The board is faulty.

l Cause 1 for multiple boards reporting the alarm: The EXT interface on the system controlboard is directly connected to a hub or switch.

l Cause 2 for multiple boards reporting the alarm: The CXPR board is off service or is faulty.

l Cause 3 for multiple boards reporting the alarm: The PIU board is improperly inserted orfaulty. As a result, the power supply to the backplane is insufficient.

Handling Procedurel Cause 1 for one board reporting the alarm: The board is undergoing cold reset.

1. On the T2000, Check whether the working status of the board is displayed in blue inthe Running Status basic slots. If yes, the board is undergoing cold reset.

2. Wait for three to five minutes and the working status of the board turns green and isalways on. Then, check whether the COMMUN_FAIL alarm ends.

l Cause 2 for one board reporting the alarm: The board is faulty.1. Replace the board that reports the HARD_ERR alarm. For details, refer to 5 Replacing

Components.

l Cause 1 for multiple boards reporting the alarm: The EXT interface on the system controlboard is directly connected to a hub or switch.1. Check whether the EXT interface on the system control board is directly connected

to a hub or switch. If yes, the VLAN of the equipment may be lost, and thus the EXTinterface on the local NE is interconnected to the ETH ports of other transmissionequipment on the network. As a result, the IP addresses of the boards on differentequipment conflict.

2. Disconnect the EXT interface from the hub or switch, or connect the EXT interfaceindirectly to the hub or switch.

NOTE

l The VLAN of the equipment isolates different NEs on the network to ensure thatcommunication on each NE does not affect each other.

l The main subrack and extended subrack are connected through the EXT interface, whichtransfers the management information and thus cannot be connected to any hub or switch.

l Cause 2 for multiple boards reporting the alarm: The CXPR board is off service or is faulty.1. Check whether the CXPR board reports the BD_STATUS or BUS_ERR alarm.


Maintenance Guide


Issue 02 (2009-06-30)

2. If yes, clear the BD_STATUS or BUS_ERR alarm first and check whether theCOMMUN_FAIL alarm is cleared.

3. If the COMMUN_FAIL alarm persists, replace the CXPR board and check whetherthe COMMUN_FAIL alarm is cleared. For details, refer to 5 ReplacingComponents.

l Cause 3 for multiple boards reporting the alarm: The PIU board is improperly inserted orfaulty. As a result, the power supply to the backplane is insufficient.1. Check whether the PIU board is properly inserted. If not, re-insert the power input

board properly.2. Check whether the PIU board reports the HARD_BAD alarm. If yes, replace the

power input board. For details, refer to 5 Replacing Components.

----End


9.3.24 CONFIG_NOSUPPORT

DescriptionThe CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Thisalarm is reported if the ODU detects that the configured parameters do not match those of theODU.

Attribute


0x0280 Major Processing alarm




9-47

Name Meaning

Parameter 1 Indicates the mismatched parameter.l 0x01: Indicates the frequency configuration error.

l 0x02: Indicates the TR spacing configuration error.

l 0x03: Indicates the transmit power configuration error.

l 0x04: Indicates the ATPC threshold configuration error.

l 0x05: Indicates the bandwidth configuration error.

l 0x06: Indicates the modulation mode configuration error.

Impact on System

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

Possible Causes

The type of the ODU mismatches the configured parameters.

Handling Procedure

Step 1 Determine the mismatched parameter according to the alarm parameters.

Step 2 Check whether the ODU interface parameters meet the network planning requirements whenthe alarm parameters are 0x01–0x03. For details, refer to the OptiX RTN 950 Radio TransmissionSystem Configuration Guide manual.

If... Then...

Yes Replace the ODU with a correct one.

No Modify the parameters.

Step 3 Check whether the IF interface parameters meet the network planning requirements when thealarm parameters are 0x04–0x06.If not, modify the parameters. For details, refer to the OptiX RTN 950 Radio Transmission SystemIDU Configuration Guide manual.

----End

Related Information

None.

9.3.25 DBMS_ERROR

Description

The DBMS_ERROR is a database error alarm indicating the database file verification failure.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


0xB9 Major Processing alarm


Name Meaning

Parameter 1 Indicates the alarm type, which indicates the error code that causes the alarm.

Parameter 2 Indicates the database storage area that has errors.

l 0x00: FDB0.

l 0x01: FDB1.

l 0x02: DRDB.

Parameter 3 Indicates the ID of the database that has errors.

l 0x00: Entire database storage area that has errors.

l 0x01 - 0xFF: Specific database that has errors.

Impact on SystemWhen the DBMS_ERROR alarm occurs, the data in the database cannot be backed up orautomatically restored. Hence, the data in the database is lost.

Possible CausesThe possible causes of the DBMS_ERROR alarm are as follows:

l Cause 1: The database files are damaged, and thus the database operation fails.

l Cause 2: The CXPR board is faulty.

Handling Procedurel Cause 1: The database files are damaged, so the database operation fails.

1. Restore the database by backing up the database manually, and then check and testthe backup database. For details, refer to Backing Up the NE Configuration Data to aLocal Server.

2. After the database is restored, the alarm is cleared automatically.l Cause 2: The CXPR board is faulty.



9-49

1. Check whether the hardware alarms such as the HARD_BAD alarm occur on theCXPR board.

2. If yes, replace the CXPR board, and then check whether the DBMS_ERROR alarmis cleared. For details, refer to 5 Replacing Components.

----End

Related Information

None.

9.3.26 DBMS_PROTECT_MODE

Description

The DBMS_PROTECT_MODE is an alarm indicating that the NE database enters the protectionmode.

Attribute


0x00C6 Critical Processing alarm

Parameters

None.

None.

Impact on System

When the DBMS_PROTECT_MODE alarm occurs, the NE database is in the protection modeand cannot be backed up. In addition, all the new configuration data in the database is lost afterthe NE resets.

Possible Causes

The cause of the DBMS_PROTECT_MODE alarm is as follows:

The NE software is frequently reset in a certain period.

Handling Procedure

l Cause: The NE software is frequently reset in a certain period.1. Find out the cause for the frequent resetting of the NE software and then handle it.2. After the fault is rectified, reset the NE software. As a result, the database exits the

protection mode. Thus, check whether the alarm is cleared.

----End


Maintenance Guide


Issue 02 (2009-06-30)


9.3.27 DOWN_E1_AIS

DescriptionThe DOWN_E1_AIS is an alarm indicating the downstream 2 Mbit/s signals. If the board detectsthat the downstream E1 signals is all "1"s, this alarm occurs.

Attribute


0xC9 Minor Communication alarm

ParametersNone.

None.

Impact on SystemWhen the DOWN_E1_AIS alarm occurs, the services are interrupted..

Possible CausesThe possible causes of the DOWN_E1_AIS alarm are as follows:

l Cause 1: The UP_E1_AIS or T_ALOS alarm occurs on the same board.


Handling Procedurel Cause 1: The UP_E1_AIS or T_ALOS alarm occurs on the same board.

1. On the T2000, check whether the UP_E1_AIS or T_ALOS alarm occurs on the sameboard. For details, refer to 8.2 Querying Current Alarms of a Board.

2. If yes, clear the UP_E1_AIS or T_ALOS alarm first and check whether theDOWN_E1_AIS alarm is cleared.

l Cause 2: The board is faulty.1. On the T2000, check whether the hardware-related alarms occur on the local board or

on the cross-connect board, such as the HARD_BAD alarm.2. If yes, cold-reset the board that reports the hardware-related alarm and check whether

the DOWN_E1_AIS alarm is cleared. For details, refer to 8.16 Resetting Boards.3. If the DOWN_E1_AIS alarm persists, replace the related board and check whether

the DOWN_E1_AIS alarm is cleared. For details, refer to 5 ReplacingComponents.

----End



9-51


9.3.28 ETH_APS_LOST

DescriptionThe ETH_APS_LOST alarm indicates loss of the APS frames. When no APS frames are receivedfrom the protection channel, the ETH_APS_LOST alarm is reported.

Attribute


0x3222 Minor Communication alarm

ParametersNone.

None.

Impact on Systeml In the case of the ETH_APS_LOST alarm, service protection cannot be performed.

l The ETH_APS_LOST alarm will be suppressed when theETH_APS_PATH_MISMATCH alarm occurs.

l When the ETH_APS_LOST alarm occurs, the system suppresses theETH_APS_SWITCH_FAIL and ETH_APS_TYPE_MISMATCH alarms.

Possible CausesThe possible causes of the ETH_APS_LOST alarm are as follows:

l Cause 1: The opposite end is not configured with protection.

l Cause 2: The configuration of the APS protection group is inconsistent at the two ends.

l Cause 3: The APS protection group is not enabled.

l Cause 4: Services in the protection channel are interrupted.

Handling Procedurel Cause 1: The opposite end is not configured with protection.

1. On the T2000, check whether the opposite end is configured with protection. Fordetails, refer to Creating an MPLS Tunnel Protection Group in the OptiX RTN 950Radio Transmission System Configuration Guide.

2. If not, configure the APS protection group and make sue the configuration at the twoends is consistent. Then, enable the APS protocol.

l Cause 2: The configuration of the APS protection group is inconsistent at the two ends.


Maintenance Guide


Issue 02 (2009-06-30)

1. On the T2000, check whether the configuration is consistent at the two ends.2. If not, modify the configuration of the APS protection group so that the configuration

at the two ends is consistent.l Cause 3: The APS protection group is not enabled.

1. Check whether the APS protocol is enabled at the two ends.2. If not, set the status of the enabled APS protocol to Disabled. Then, enable the APS

protocol at the two ends.l Cause 4: Services in the protection channel are interrupted.

1. Check whether there are alarms indicating loss of signals or service degrade in theprotection channel, such as the ETH_LOS alarm.

2. If yes, take the first to clear these alarms.

----End

Related Information

None.

9.3.29 ETH_APS_PATH_MISMATCH

Description

The ETH_APS_PATH_MISMATCH is an alarm indicating that the working and protectionpaths of the APS are inconsistent. This alarm occurs when the working and protection paths ofthe equipment in the protection group are inconsistent at the two ends.

Attribute



Parameters

None.

None.

Impact on Systeml In the case of the ETH_APS_PATH_MISMATCH alarm, the services cannot be protected.

l When the ETH_APS_PATH_MISMATCH alarm occurs, the system suppresses theETH_APS_LOST, ETH_APS_SWITCH_FAIL, and ETH_APS_TYPE_MISMATCHalarms.

Possible Causes

The possible causes of the ETH_APS_PATH_MISMATCH alarm are as follows:



9-53

l Cause 1: The configured working and protection paths of the equipment in the protectiongroup at the two ends are inconsistent.

l Cause 2: Certain physical links are incorrectly connected.

Handling Procedure

l Cause 1: The configured working and protection paths of the equipment in the protectiongroup at the two ends are inconsistent.1. On the T2000, check whether the configuration is consistent at the two ends of the

APS protection group. For details, refer to Creating an MPLS Tunnel Protection Groupin the OptiX RTN 950 Radio Transmission System Configuration Guide.

2. If the configuration is inconsistent, modify the configuration of the APS protectiongroup, and make sure that the configuration is consistent at the two ends of the APSprotection group. Then, check whether the alarm is cleared.

l Cause 2: Certain physical links are incorrectly connected.1. Check whether the fiber and cable connections are correct on each NE from the local

end to the opposite end.2. If not, reconnect the fibers and cables, and then check whether this alarm is cleared.

----End

Related Information

None.

9.3.30 ETH_APS_SWITCH_FAIL

Description

The ETH_APS_SWITCH_FAIL alarm indicates a protection switching failure. When therequest signals in the transmitted APS frames are inconsistent with the bridge signals in thereceived APS frames for 50 ms, the switching fails and the ETH_APS_SWITCH_FAIL alarmis reported.

Attribute


0x3221 Major Processing failure alarm

Parameters

None.

None.

Impact on Systeml In the case of the ETH_APS_SWITCH_FAIL alarm, the services cannot be protected.


Maintenance Guide


Issue 02 (2009-06-30)

l The ETH_APS_SWITCH_FAIL alarm will be suppressed when theETH_APS_PATH_MISMATCH or ETH_APS_LOST alarm occurs.

Possible Causes

The possible cause of the ETH_APS_SWITCH_FAIL alarm is as follows:

The configuration of the APS protection group is inconsistent at the two ends.

Handling Procedure

l Cause: The configuration of the APS protection group is inconsistent at the two ends.

1. On the T2000, check whether the configuration is consistent at the two ends of theAPS protection group. For details, refer to Creating an MPLS Tunnel Protection Groupin the OptiX RTN 950 Radio Transmission System Configuration Guide.

2. Modify the configuration of the APS protection group so that the configuration at thetwo ends is consistent.

3. Re-deactivate and re-activate the APS protection at the two ends.

----End

Related Information

None.

9.3.31 ETH_APS_TYPE_MISMATCH

Description

The ETH_APS_TYPE_MISMATCH is an alarm indicating the protection scheme informationmismatch. This alarm occurs when the information in the received APS frames is inconsistentwith the APS protection scheme configured at the local end.

Attribute


0x321F Major Communication alarm

Parameters




9-55

Name Meaning

Parameter 1 The indication of Parameter 1 is as follows:l 0x01: Inconsistency of protection group protection type. Refer to Cause 1.

l 0x02: Inconsistency of protection group switching mode. Refer to Cause 2.

l 0x03: Inconsistency of protection group revertive mode. Refer to Cause 3.

Impact on Systeml The ETH_APS_TYPE_MISMATCH alarm may cause the APS protection failure, and thus

the services cannot be effectively protected.

l The ETH_APS_TYPE_MISMATCH alarm will be suppressed when theETH_APS_PATH_MISMATCH or ETH_APS_LOST alarm occurs.

Possible Causes

The possible causes of the ETH_APS_TYPE_MISMATCH alarm are as follows:

l Cause 1: Inconsistency of protection group protection type.

l Cause 2: Inconsistency of protection group switching mode.

l Cause 3: Inconsistency of protection group revertive mode.

Handling Procedure

l Cause: Inconsistency of protection group protection type, switching mode, or revertivemode.

1. On the T2000, check whether the configuration of the protection group is consistentat the two ends. For details, refer to Creating an MPLS Tunnel Protection Group inthe OptiX RTN 950 Radio Transmission System Configuration Guide.

2. If not, modify the configuration of the APS protection group so that the configurationat the two ends is consistent. Then, re-enable the APS protocol and the alarm will becleared automatically.

----End

Related Information

None.

9.3.32 ETH_AUTO_LINK_DOWN

Description

The ETH_AUTO_LINK_DOWN is a port automatic link down alarm. When the LPT triggersthe shutdown of the physical port, this alarm is reported.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters

None

None

Impact on System

When the alarm occurs, the LPT triggers the shutdown of the physical port, and related servicesat other ports are interrupted.

Possible Causes

The possible causes of the ETH_AUTO_LINK_DOWN alarm are as follows:

l Cause 1: BFD is bound to the active LPT port. When the board is faulty and the BFD stateis DOWN, the standby LPT port is disabled.

l Cause 2: The fiber or network cable connected to the active LPT port becomes faulty. Asa result, the standby LPT port is disabled.

Handling Procedure

l Cause 1: BFD is bound to the active LPT port. When the board is faulty and the BFD stateis DOWN, the standby LPT port is disabled.

1. Check whether any hardware alarm, such as the HARD_BAD alarm, occurs on thetwo NEs.

2. If yes, clear the hardware alarm first and then check whether theETH_AUTO_LINK_DOWN alarm is cleared.

l Cause 2: The fiber or network cable connected to the active LPT port becomes faulty. Asa result, the standby LPT port is disabled.

1. Remove and insert the fiber or network cable, and then check whether the alarm iscleared.

2. If the alarm persists, replace the fiber or the network cable.

----End

Related Information

None.



9-57

9.3.33 ETH_LINK_DOWN

DescriptionThe ETH_LINK_DOWN alarm indicates that the Ethernet port connection is faulty. When theEthernet port is incorrectly connected, the port fails to negotiate and the ETH_LINK_DOWNalarm is reported.

Attribute


0x31F9 Critical Communication alarm

ParametersNone.

None.

Impact on Systeml When the ETH_LINK_DOWN alarm occurs during data transmission, the Ethernet port

fails to negotiate and to receive data. As a result, the services are interrupted.l The ETH_LINK_DOWN alarm will be suppressed when the ETH_LOS alarm occurs.

l In the case of the ETH_LINK_DOWN alarm, the system suppresses theLAG_MEMBER_DOWN and MAC_FCS_EXC alarms.

Possible CausesThe possible causes of the ETH_LINK_DOWN alarm are as follows:

l Cause 1: The Ethernet ports on the local NE and opposite NE work in different modes andthus fail to negotiate.

l Cause 2: Inloop is set on the port.


Handling Procedurel Cause 1: The Ethernet ports on the local NE and opposite NE work in different modes and

thus fail to negotiate.1. On the T2000, check whether the Ethernet ports at the two ends work in the same

mode.2. If not, modify the configuration so that they work in the same mode. Then, check

whether the alarm is cleared. For details, refer to 8.22 Querying and Setting theWorking Mode of Ethernet Interface.

l Cause 2: Inloop is set on the port.1. On the T2000, check whether the ports at the two ends reports the LOOP_ALM alarm.

For details, refer to 8.2 Querying Current Alarms of a Board.


Maintenance Guide


Issue 02 (2009-06-30)

2. If yes, clear the LOOP_ALM alarm first and then check whether theETH_LINK_DOWN alarm is cleared.

l Cause 3: The board is faulty.1. On the T2000, check whether there is hardware-related alarm occurs on the board of

the two NEs, such as the HARD_BAD alarm.2. If yes, replace the board that reports the hardware-related alarm and then check

whether the ETH_LINK_DOWN alarm is cleared. For details, refer to 5 ReplacingComponents.

----End


9.3.34 ETH_LOS

DescriptionThe ETH_LOS alarm indicates that the connection to the Ethernet port is lost. When the Ethernetport receives no Ethernet signals, the ETH_LOS alarm is reported.

Attribute


0xeb Critical Communication alarm

ParametersNone.

None.

Impact on Systeml When the ETH_LOS alarm occurs, the Ethernet port cannot receive data and thus the

services are interrupted.l The ETH_LOS alarm will be suppressed when one of the LSR_NO_FITED and

LASER_MOD_ERR alarms occurs.l In the case of the ETH_LOS alarm, the system will suppresses the other alarms related to

Ethernet service.

Possible CausesThe possible causes of the ETH_LOS alarm are as follows:

l Cause 1: The cable or fiber is not properly connected to the Ethernet port.

l Cause 2: The network cable or fiber is faulty.

l Cause 3: The optical power received by the local NE is excessively low.



9-59


Handling Procedure

l Cause 1: The cable or fiber is not properly connected to the Ethernet port.

1. Check whether the cable or fiber is properly connected to the Ethernet port. Reconnectthe loosen cable or fiber.

l Cause 2: The network cable or fiber is faulty.

1. Check whether the cable or fiber is faulty. Replace the faulty cable or fiber.

l Cause 3: The optical power received by the local NE is excessively low.

1. On the T2000, check whether the OUT_PWR_ABN alarm occurs on the opposite NE.If yes, clear the OUT_PWR_ABN alarm first and check whether the ETH_LOS alarmon the local NE is cleared. For details, refer to 8.2 Querying Current Alarms of aBoard.

2. If the ETH_LOS alarm persists, clean the receive interface and the fiber header. Fordetails, refer to 8.24 Inspecting and Cleaning the Optical Fiber Connectors.

3. If the ETH_LOS alarm still persists, check whether the flange or optical attenuator iscorrectly connected and whether the attenuation of the optical attenuator is excessivelyhigh. Correctly use the flange and optical attenuator.

4. If the ETH_LOS alarm still persists, adjust the optical power so that the optical poweris within the normal range by adding or removing optical attenuators.


1. Replace the processing board that reports the alarm. For details, refer to 5 ReplacingComponents.

2. If the ETH_LOS alarm persists, replace the processing board on the opposite NE.

----End

Related Information

None.

9.3.35 EXT_SYNC_LOS

Description

The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm occurswhen the system detects the loss of the external clock source traced by the equipment.

Attribute


0xB8 Critical Equipment alarm


Maintenance Guide


Issue 02 (2009-06-30)

Parameters

Name Meaning

Parameter 1 Indicates the lost external clock source.

l 0x01: The first channel of the external clock source.

l 0x02: The second channel of the external clock source.

Impact on System

When the EXT_SYNC_LOS alarm occurs, the external clock source of the system is lost andcannot be traced by the equipment. In this case, the clock quality is degraded, which affects theservice quality. Thus, bit errors may be generated.

Possible Causes

The possible causes of the EXT_SYNC_LOS alarm are as follows:

l Cause 1: The configured mode of the external clock source is inconsistent with the actualmode of the clock input.


l Cause 3: The clock input cable connection is incorrect.

l Cause 4: The signal at the physical interface of the external clock source is lost.

Handling Procedure

l Cause 1: The configured mode of the external clock source is inconsistent with the actualmode of the clock input.

1. On the T2000, check whether the actual mode and the configured mode of the clockinput are consistent. For details, refer to Configuring the NE Clock Source in theConfiguration Guide manual.

2. If the actual mode and the configured mode of the clock input are inconsistent,reconfigure the mode of the external clock source. Make sure that both the configuredmode and the actual mode of the clock input are 2 MHz or 2 Mbit/s, and then checkwhether the alarm is cleared.


1. On the T2000, check whether the hardware alarms such as the HARD_BAD alarmoccur on the CXPR board.

2. If yes, clear these alarms and then check whether the EXT_SYNC_LOS alarm iscleared.

l Cause 3: The clock input cable connection is incorrect.

1. Check whether the clock input cable connection is correct.

2. If not, reconnect the clock cable and check whether the alarm is cleared.

l Cause 4: The signal at the physical interface of the external clock source is lost.

1. Check whether the output signals of the external clock equipment are normal.



9-61

2. If not, replace the faulty external clock equipment, and then check whether the alarmis cleared.

----End


9.3.36 EXT_TIME_LOC

DescriptionThe EXT_TIME_LOC alarm indicates loss of the external time source. When the external timeinput port is enabled but the board detects no input external time signals, the EXT_TIME_LOCalarm is reported.

Attribute


0x32AC Major Equipment alarm

ParametersNone.

None.

Impact on SystemIn the case of the EXT_TIME_LOC alarm, the time of the local NE cannot be synchronized withthe external time device that is connected to the enabled external time port on the local NE.

Possible CausesThe possible causes of the EXT_TIME_LOC alarm are as follows:

l Cause 1: The cable is disconnected or loosened from the external time interface.

l Cause 2: The external time device does not output signals.

Handling Procedurel Cause 1: The cable is disconnected or loosened from the external time interface.

1. Check whether the cable is disconnected or loosened from the external time interface.If the cable is disconnected or loosened from the external time interface, reconnectthe cable.

2. If the alarm persists, check whether the cable is faulty. If the cable is faulty, replacethe faulty cable.

l Cause 2: The external time device does not output signals.


Maintenance Guide


Issue 02 (2009-06-30)

1. Check whether the external time device outputs signals. If the external time devicedoes not output signals, replace the external time device.

----End


9.3.37 FAN_FAIL

DescriptionThe FAN_FAIL alarm indicates that a fan is faulty. When a fan becomes faulty, the FAN_FAILalarm is reported.

Attribute




Name Meaning

Parameter 1 Indicates the number of faulty fans.

Impact on Systeml When any fan on the FAN board becomes faulty, the other fans rotate at the full rate for

proper heat dissipation.l If the FAN_FAIL alarm is not cleared in a timely manner, the boards on the NE may be

damaged due to over-heat and thus the services on the NE may be interrupted.

Possible CausesThe cause of the FAN_FAIL alarm is as follows:

One or more fans on the fan board are faulty.

Handling Procedurel Cause: One or more fans on the fan board are faulty.



9-63

1. Re-insert the FAN board.2. If the FAN_FAIL alarm persists, replace the FAN board. For details, refer to 5.5

Replacing the FAN Board.

----End


9.3.38 FLOW_OVER

DescriptionThe FLOW_OVER is an alarm indicating that the received flow of the port exceeds the threshold.This alarm occurs when the received flow of the Ethernet port exceeds the Max ReservedBandwidth.

Attribute


0x300D Minor Equipment alarm


Name Meaning

Parameter 1, Parameter 2 Indicates that the received flow exceeds the threshold. The unit isMbit/s.

Impact on Systeml During the data transmission, if the configured bandwidth is lower than the actual flow at

the port, the FLOW_OVER alarm occurs and packet loss may occurs.l If the configured bandwidth is higher than the actual flow at the port, the alarm occurs but

the system and services are not affected.

Possible CausesThe cause of the FLOW_OVER alarm is as follows:

The actually received flow of the port is higher than the configured Max ReservedBandwidth.


Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedure

l Cause: The actually received flow of the port is higher than the configured Max ReservedBandwidth.

1. Refer to the alarm parameters and check whether the actually received flow reachesthe port bandwidth limit.



2. On the T2000, check whether the Max Reserved Bandwidth reaches the portbandwidth limit. For details, refer to Setting the Layer 3 Attributes of an EthernetInterface in the OptiX RTN 950 Radio Transmission System Configuration Guidemanual.



3. Increase the Max Reserved Bandwidth of the port to a value that is higher than theactually received flow. Then, check whether the alarm is cleared.

4. The port has no spare bandwidth. Decrease the data flow transmitted from the oppositeNE to avoid packet loss and check whether the alarm is cleared.

----End

Related Information

None.

9.3.39 GSP_ISIS_NB_AUTH_ERR

Description

The GSP_ISIS_NB_AUTH_ERRN alarm indicates the ISIS neighbor authentication error.When the authentication configured on the two neighbors is inconsistent, the alarm occurs.

Attribute


0x32C4 Major Communication alarm

Parameters




9-65

Name Meaning

Parameter 1 to parameter 4 Indicates the IP site of the local NE.

Parameter 5 to parameter 8 Indicates the IP site of the opposite NE.

Impact on Systeml When the GSP_ISIS_NB_AUTH_ERR alarm occurs, service signals are not affected. But

as the neighborhood cannot be created, the reachable of control packet is affected.

l When the authentication configured on the two neighbors is consistent, the alarm is clearedautomatically.

Possible Causes

The cause of the GSP_ISIS_NB_AUTH_ERR alarm is as follows:

The authentication configured on the two neighbors is inconsistent.

Handling Procedure

l Cause: The authentication configured on the two neighbors is inconsistent.

1. On the T2000, check whether the authentication configured on the two neighbors isconsistent. For details, refer to Configuring the IGP-ISIS Protocol in the OptiX RTN950 Radio Transmission System Configuration Guide manual.

NOTE

The short querying procedure is as follows:

NE Explorer > Configuration > Control Plane Configuration > IGP-ISISConfiguration > Port Configuration .

2. If not, modify the authentication configuration on the two neighbors and make theAuthentication Mode and Authentication Type be consistent. Then, check whetherthe alarm is cleared.

----End

Related Information

None.

9.3.40 GSP_RSVP_NB_AUTH_ERR

Description

The GSP_RSVP_NB_AUTH_ERRN alarm indicates the RSVP neighbor authentication error.When the authentication configured on the two neighbors is inconsistent, the alarm occurs.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters


Name Meaning



Impact on Systeml When the GSP_RSVP_NB_AUTH_ERR alarm occurs, service signals are not affected.

But as the neighborhood cannot be created, the reachable of control packet is affected.

l When the authentication configured on the two neighbors is consistent, the alarm is clearedautomatically.

Possible Causes

The cause of the GSP_RSVP_NB_AUTH_ERR alarm is as follows:

The authentication configured on the two neighbors is inconsistent.

Handling Procedure

l Cause: The authentication configured on the two neighbors is inconsistent.

1. On the T2000, check whether the authentication configured on the two neighbors isconsistent.

2. If not, modify the authentication configurations on the two neighbors and make surethat the configurations of Authentication Type be consistent. Then, check whetherthe alarm is cleared.

----End

Related Information

None.



9-67

9.3.41 GSP_RSVP_NB_DOWN

Description

The GSP_RSVP_NB_DOWN alarm indicates the RSVP neighbor down. When the receivingof RSVP hello packets is interrupted, the alarm occurs.

Attribute



Parameters


Name Meaning



Impact on Systeml When the GSP_RSVP_NB_DOWN alarm occurs, service signals are not affected. but the

reachable of control packet is affected.

l When the receiving of RSVP hello packets is recovered, the alarm is cleared automatically.

Possible Causes

The cause of the GSP_RSVP_NB_DOWN alarm is as follows:

l Cause 1: The RSVP protocol is disabled on the neighbor NE.

l Cause 2: The physical link is faulty.


Handling Procedure

l Cause 1: The RSVP protocol is disabled on the neighbor NE.

1. On the T2000, check whether the RSVP protocol is enabled on the neighbor NE. Fordetails, refer to Configuring the MPLS-RSVP Protocol in the OptiX RTN 950 RadioTransmission System Configuration Guide manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. If not, re-enable the RSVP protocol and check whether the GSP_RSVP_NB_DOWNalarm is cleared.

l Cause 2: The physical link is faulty.1. Check whether the physical link connected to the two neighbor NEs is faulty.2. If yes, repair the faulty link and check whether the alarm is cleared.

l Cause 3: The board is faulty.1. On the T2000, check whether the HARD_BAD alarm occurs on the line board or on

the system control board of the two neighbor NEs.2. If yes, cold-reset the board that reports the HARD_BAD alarm and check whether the

GSP_RSVP_NB_DOWN alarm is cleared. For details, refer to 8.16 ResettingBoards.

3. If the GSP_RSVP_NB_DOWN alarm persists, replace the related board and checkwhether the GSP_RSVP_NB_DOWN alarm is cleared. For details, refer to 5Replacing Components.

----End


9.3.42 GSP_TNNL_DOWN

DescriptionThe GSP_TNNL_DOWN alarm indicates the tunnel down. When the tunnel turns from the upstate into the down state, the alarm occurs.

Attribute



ParametersNone.

None.

Impact on Systeml When the GSP_TNNL_DOWN alarm occurs, services carried on the faulty tunnel are not

interrupted.l When the tunnel turns from the down state into the up state, the alarm is cleared

automatically.

Possible CausesThe cause of the GSP_TNNL_DOWN alarm is as follows:



9-69

l Cause 1: The Ethernet port is not enabled.



Handling Procedurel Cause 1: The Ethernet port is not enabled.

1. On the T2000, check whether the Ethernet ports at the two ends of the tunnel are allenabled. For details, refer to Setting the General Attributes of Ethernet Interfaces inOptiX RTN 950 Radio Transmission System Configuration Guide manual.

2. If not, enable the Ethernet ports first and then check whether the alarm is cleared.l Cause 2: The physical link is faulty.

1. Check whether the physical link connected to the two neighbor NEs is faulty.2. If yes, repair the faulty link and check whether the alarm is cleared.

l Cause 3: The board is faulty.1. On the T2000, check whether the HARD_BAD alarm occurs on the line board or on

the system control board of the two neighbor NEs.2. If yes, cold-reset the board that reports the HARD_BAD alarm and check whether the

GSP_TNNL_DOWNN alarm is cleared. For details, refer to 8.16 ResettingBoards.

3. If the GSP_TNNL_DOWN alarm persists, replace the related board and checkwhether the GSP_TNNL_DOWN alarm is cleared. For details, refer to 5 ReplacingComponents.

----End


9.3.43 HARD_BAD

DescriptionThe HARD_BAD alarm indicates a hardware fault. When a board detects a hardware fault, theboard reports the HARD_BAD alarm.

Attribute


0xEC Critical Equipment 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,


Maintenance Guide


Issue 02 (2009-06-30)

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



9-71

Name Meaning

Parameter 1 Indicates the type of the cause that results in the hardware failure.

l 0x01: The power module operates abnormally. Refer to Cause 1.

l 0x02: The board is improperly installed (the board is poorly connected to thebackplane. For example, the board is not seated tight). Refer to Cause 2.

l 0x03: The 38M system clock 1 is abnormal. Refer to Cause 3 when 0x03 andthe following parameters are detected.

l 0x04: The 38M system clock 2 is abnormal.

l 0x05: The 2M clock source is abnormal.

l 0x06: The digital phase-locked loop is faulty.

l 0x07: The 38M service clock is lost.

l 0x08: The bus is abnormal.

l 0x09: The TPS protection board is abnormal.

l 0x10: The main oscillator of the clock is faulty.

l 0x11: The frequency offset of the main oscillator is excessive.

l 0x12: The standby oscillator stops running.

l 0x13: The processor is faulty.

l 0x14: The memory component is faulty.

l 0x15: The programmable logic component is faulty.

l 0x16: The SDH component is faulty.

l 0x17: The data communication component is faulty.

l 0x18: The clock components are faulty.

l 0x19: The interface component is faulty.

l 0x20: The power supply components are faulty.

l 0x21: Other faults.

l 0x22: The analog phase-locked loop is abnormal.

l 0x23: The 32M clock fails.



l 0x26: The loop of the cross-connect chip fails.

l 0x27: The 8k in-service bus of the board is lowered.

l 0x28: The system 2M frame header 1 is lost.

l 0x29: The system 2M frame header 2 is lost.

l 0x30: The DSP clock-driver chip clock is lost.

l 0x31: The DSP output clock is lost.

l 0x32: RTM module is off service.

l 0x33: Chip faults.


Maintenance Guide


Issue 02 (2009-06-30)

Name Meaning

Parameter 2 l 0x01: Indicates the A bus is abnormal.

l 0x02: Indicates the B bus is abnormal.

l 0xff: No indications.

Parameter 3 0xff: Reserved.

Impact on Systeml If the board that reports the HARD_BAD alarm is the working board, the HARD_BAD

alarm triggers protection switching.l If the board that reports the HARD_BAD alarm is the protection board, protection switching

cannot be performed and the services may be interrupted.l If the board that reports HARD_BAD alarm is not configured with protection switching,

the services carried on the board will be affected.l When the HARD_BAD alarm occurs, the system suppresses COMMUN_FAIL and

BUS_ERR alarms.

Possible Causes

The possible causes of the HARD_BAD alarm are as follows:

l Cause 1: The external power supply fails.

l Cause 2: The board is poorly connected to the backplane.


Handling Procedure

l Cause 1: The external power supply fails.1. Make sure that the power supply to the NE is normal and then check whether the alarm

is cleared. For details, refer to OptiX RTN 950 IDU Quickly Installation Guide.l Cause 2: The board is poorly connected to the backplane.

1. Remove and re-insert the board to make the board is well connected to the backplane.Then, check whether the alarm is cleared. For details, refer to 8.19 Replacing Boardson Site.

l Cause 3: The board is faulty.1. Cold-reset the board that reports the alarm and then check whether the alarm is cleared.

For details, refer to 8.16 Resetting Boards.2. If the HARD_BAD alarm persists, replace the board that reports this alarm. For details,


----End

Related Information

None.



9-73

9.3.44 IMA_GROUP_LE_DOWN

Description

The IMA_GROUP_LE_DOWN alarm indicates a failure of the local IMA group. When theIMA protocol is not enabled on the local NE or the number of enabled links in the IMA groupis less than the minimum number of enabled links in the IMA group, theIMA_GROUP_LE_DOWN alarm is reported.

Attribute



Parameters

None.

None.

Impact on System

When the IMA_GROUP_LE_DOWN alarm occurs, the services in the IMA group areinterrupted.

Possible Causes

The possible causes of the IMA_GROUP_LE_DOWN alarm are as follows:

l Cause 1: The IMA protocol is not enabled on the local NE.

l Cause 2: The number of enabled links in the local IMA group is less than the configuredminimum number of the enabled links in the IMA group.

Handling Procedure

l Cause 1: The IMA protocol is not enabled on the local NE.1. Check the configuration of the IMA group at the two ends and ensure that the IMA

group parameters are matched. For details, refer to Configuring the IMA in the OptiXRTN 950 Radio Transmission System Feature Description manual.

2. On the T2000, set the IMA Protocol Enable Status parameter to Enabled for thelocal NE.

l Cause 2: The number of enabled links in the local IMA group is less than the configuredminimum number of the enabled links in the IMA group.1. On the T2000, check whether there is the ALM_IMA_LIF alarm. For details, refer to

8.2 Querying Current Alarms of a Board.2. If yes, clear the ALM_IMA_LIF alarm first to enable the member links in the local

IMA group. When the actual number of enabled links reaches the configured minimum


Maintenance Guide


Issue 02 (2009-06-30)

number of enabled links, the IMA_GROUP_LE_DOWN alarm will be clearedautomatically.

3. Optional: Configure new member links in the local IMA group.

----End


9.3.45 IMA_GROUP_RE_DOWN

DescriptionThe IMA_GROUP_RE_DOWN alarm indicates a failure of the remote IMA group. When theIMA protocol is not enabled on the remote NE or the number of enabled links in the IMA groupis less than the minimum number of enabled links in the IMA group, theIMA_GROUP_RE_DOWN alarm is reported.

Attribute



ParametersNone.

None.

Impact on SystemWhen the IMA_GROUP_LE_DOWN alarm occurs, the services in the IMA group areinterrupted.

Possible CausesThe possible causes of the IMA_GROUP_RE_DOWN alarm are as follows:

l Cause 1: The IMA protocol is not enabled on the remote NE.

l Cause 2: The number of enabled links in the remote IMA group is less than the configuredminimum number of the enabled links in the IMA group.

Handling Procedurel Cause 1: The IMA protocol is not enabled on the remote NE.

1. Check the configuration of the IMA group at the two ends and ensure that the IMAgroup parameters are matched. For details, refer to Configuring the IMA in the OptiXRTN 950 Radio Transmission System Feature Description manual.



9-75

2. On the T2000, set the IMA Protocol Enable Status parameter to Enabled for theremote NE.

l Cause 2: The number of enabled links in the remote IMA group is less than the configuredminimum number of the enabled links in the IMA group.1. On the T2000, check whether there is the ALM_IMA_RIF alarm. For details, refer to

8.2 Querying Current Alarms of a Board.2. If yes, clear the ALM_IMA_RIF alarm first to enable the member links in the remote

IMA group. When the actual number of enabled links reaches the configured minimumnumber of enabled links, the IMA_GROUP_LE_DOWN alarm will be clearedautomatically.

3. Optional: Configure new member links in the remote IMA group.

----End


9.3.46 IMAE1_DELAY

DescriptionThe IMAE1_DELAY is an E1 delay alarm. When the delay of the transmitted service in theIMA link exceeds the threshold value of the differential delay of the link, the alarm occurs.

Attribute


0x327D Minor Communication alarm

ParametersNone.

None.

Impact on SystemThe alarm indicates that delay or congestion occurs to the transmitted IMA service.

Possible CausesThe cause of the IMAE1_DELAY alarm is as follows:

The E1 physical route is faulty.

Handling Procedurel Cause: The E1 physical route is faulty.


Maintenance Guide


Issue 02 (2009-06-30)

1. Remove and then insert the electrical interface of the E1 link, and then check whetherthe alarm is cleared. For details, refer to OptiX RTN 950 Radio Transmission SysteIDU Quick Installation Guide.

2. If the IMAE1_DELAY alarm persists, replace the board that reports theIMAE1_DELAY alarm. For details, refer to 5 Replacing Components.

----End


9.3.47 IN_PWR_ABN

DescriptionThe IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.

Attribute



ParametersNone.

None.

Impact on SystemWhen the IN_PWR_ABN alarm occurs, the service transmission performance is affected. If theservice transmission performance is severely affected, the services are interrupted.

Possible CausesThe possible causes of the IN_PWR_ABN alarm are as follows:

l Cause 1: The transmitted optical power of the opposite NE is abnormal.

l Cause 2: The receive optical power is higher than the normal range.

l Cause 3: The receive optical power is lower than the normal range.

l Cause 4: The receive board is faulty.

Handling Procedurel Cause 1: The transmitted optical power of the opposite NE is abnormal.

1. On the T2000, check whether there is OUT_PWR_ABN on the opposite NE.2. If yes, clear the OUT_PWR_ABN alarm on the opposite NE first and check whether

the IN_PWR_ABN alarm is cleared.



9-77

3. If the IN_PWR_ABN alarm persists, query the receive optical power of the local NEon the T2000. For details, refer to 8.4 Checking the Optical Power.– If the receive optical power is higher than the normal range, refer to the handling

procedure of Cause 2.– If the receive optical power is lower than the normal range, refer to the handling

procedure of Cause 3.l Cause 2: The receive optical power is higher than the normal range.

1. Add proper attenuators at the receive optical interface which reports theIN_PWR_ABN alarm to adjust the receive optical power to the normal range. Thencheck whether the IN_PWR_ABN alarm is cleared.

l Cause 3: The receive optical power is lower than the normal range.1. Check whether the bending radius of the fiber is less than 6 cm. If yes, spool the fiber

jumper again, and then check whether the alarm is cleared.2. Check whether the optical attenuator is properly connected. If not, adjust the optical

attenuator to a proper position and check whether the IN_PWR_ABN alarm is cleared.3. Check whether the optical module is loose. If yes, fasten the optical module and check

whether the alarm is cleared.4. If the IN_PWR_ABN alarm persists, replace the optical module. For details, refer to

5.9 Replacing the Pluggable Optical Module.5. Clean the fiber headers of the NEs on the two ends. For details, refer to 8.24 Inspecting

and Cleaning the Optical Fiber Connectors.l Cause 4: The receive board is faulty.

1. Check whether the processing board or cross-connect board of the local NE reportsthe hardware alarms, such as the HARD_BAD or TEMP_OVER alarm.

2. If yes, replace the board. For details, refer to 5 Replacing Components.

----End

Related Information

9.3.48 LAG_DOWN

DescriptionThe LAG_DOWN alarm indicates that the link aggregation group (LAG) is unavailable. Whenthe number of enabled ports in the LAG is 0, the LAG_DOWN alarm is reported.

Attribute



ParametersNone.

None.


Maintenance Guide


Issue 02 (2009-06-30)

Impact on SystemIn the case of the LAG_DOWN alarm, the services are interrupted.

Possible CausesThe possible causes of the LAG_DOWN alarm are as follows:

l Cause 1: No LAG is configured on the opposite NE.

l Cause 2: All member ports in the LAG are unavailable.

Handling Procedurel Cause 1: No LAG is configured on the opposite NE.

1. On the T2000, query whether the LAG is configured on the opposite NE. For details,refer to LAG Operation Tasks in OptiX RTN 950 Radio Transmission System FeatureDescription manual.

2. If not, configure the LAG on the opposite NE and check whether the alarm is cleared.l Cause 2: All member ports in the LAG are unavailable.

1. When a port in the LAG is unavailable, the ETH_LOS, ETH_LINK_DOWN orLAG_MEMBER_DOWN alarm occurs in the system. For details, refer to 8.2Querying Current Alarms of a Board.

2. clear the ETH_LOS, ETH_LINK_DOWN or LAG_MEMBER_DOWN alarm toenable the member ports in the LAG and the LAG_DOWN alarm will be clearedautomatically.

----End


9.3.49 LAG_MEMBER_DOWN

DescriptionThe LAG_MEMBER_DOWN is an alarm indicating that the member port of the linkaggregation group (LAG) is unavailable. This alarm occurs when the member port cannot beactivated and cannot work as the backup.

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



9-79

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 1 Indicates the board ID.

Parameter 2 Indicates the sub-board ID.

0xff: No sub-board.

Parameter 3, Parameter 4 Indicates the port number ID.

Parameter 5 Indicates the cause that makes the port unavailable.l 0x01: The port connection is unavailable. Refer to cause 1.

l 0x02: The port fails to receive the LACP packet. Refer to cause2.

l 0x03: The port works in the half-duplex mode. Refer to cause3.

l 0x04: Loopback is set on the port. Refer to cause 4.

Impact on Systeml When the LAG_MEMBER_DOWN alarm occurs, in the case of the load-sharing mode,

packets may be continuously lost due to the insufficient bandwidth.l in other cases, the link switching is triggered and packets are lost in a short period.

l The LAG_MEMBER_DOWN alarm will be suppressed when the ETH_LINK_DOWNalarm occurs.

l When the LAG_MEMBER_DOWN alarm occurs, the system suppresses theMAC_FCS_EXC alarm.

Possible CausesThe possible causes of the LAG_MEMBER_DOWN alarm are as follows:

l Cause 1: The port connection is unavailable.

l Cause 2: The port fails to receive the LACP packet.

l Cause 3: The port works in the half-duplex mode.

l Cause 4: Loopback is set on the port.

Handling Procedurel Cause 1: The port connection is unavailable.

1. On the T2000, check whether the LAG member port which reports the alarm is enabledaccording to the alarm parameters. For details, refer to Setting the General Attributesof Ethernet Interfaces in OptiX RTN 950 Radio Transmission System ConfigurationGuide manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. If not, enable the LAG member port first and then check whether the alarm is cleared.3. If the alarm persists, check whether the ETH_AUTO_LINK_DOWN alarm occurs on

the port which reports the LAG_MEMBER_DOWN alarm. For details, refer to 8.2Querying Current Alarms of a Board.

4. If yes, clear the ETH_AUTO_LINK_DOWN alarm first and then check whether theLAG_MEMBER_DOWN alarm is cleared.

l Cause 2: The port fails to receive the LACP packet.1. On the T2000, check whether the opposite port is added into the LAG group. For

details, refer to LAG Operation Tasks in OptiX RTN 950 Radio TransmissionSystem Feature Description manual.

2. If not, add the opposite port into the LAG group and check whether this alarm iscleared.

3. If the alarm persists, check whether the ETH_LOS or FLOW_OVER alarm occurs onthe port which reports the LAG_MEMBER_DOWN alarm.

4. If yes, clear the ETH_LOS or FLOW_OVER alarm first and then check whether theLAG_MEMBER_DOWN alarm is cleared.

l Cause 3: The port works in the half-duplex mode.1. Modify the working mode of the port to Auto-Negotiation or Full-Duplex and then

check whether the LAG_MEMBER_DOWN alarm is cleared. For details, refer to8.22 Querying and Setting the Working Mode of Ethernet Interface.

l Cause 4: Loopback is set on the port.1. Release the loopback of the port and check whether the LAG_MEMBER_DOWN

alarm is cleared. For details, refer to 8.9 Configuring Port Loopback.

----End


9.3.50 LASER_MOD_ERR

DescriptionThe LASER_MOD_ERR alarm indicates mismatch of the optical module. When the insertedoptical module is not supported by the board, the LASER_MOD_ERR alarm occurs.

Attribute



ParametersNone.

None.



9-81

Impact on Systeml When the LASER_MOD_ERR alarm occurs, the optical module cannot start working, the

signals are lost and the services are interrupted.l The LASER_MOD_ERR alarm will be suppressed when the LSR_NO_FITED alarm

occurs.l When the LSR_NO_FITED alarm occurs, the system suppresses the ETH_LOS and other

alarms related to optical module.

Possible Causes

The cause of the LASER_MOD_ERR alarm is as follows:

The installed optical module is not of the same type or speed as requested.

Handling Procedure

l Cause: The installed optical module is not of the same type or speed as requested.1. Replace a proper optical module according to the version mapping table. For details,

refer to 5.9 Replacing the Pluggable Optical Module.

----End

Related Information

None.

9.3.51 LASER_SHUT

Description

The LASER_SHUT is an alarm indicating that the board laser is shut down.

Attribute


0xf815 Major Processing alarm

Parameters

None.

None.

Impact on Systeml When the LASER_SHUT alarm occurs, the services are interrupted.

l In the case of LASER_SHUT alarm, the system will suppresses the LSR_BCM_ALM andOUT_PWR_ABN alarms.


Maintenance Guide


Issue 02 (2009-06-30)

Possible Causes

The possible causes of the LASER_SHUT alarm are as follows:

l Cause 1: The user shuts down the laser.

l Cause 2: The board reports the HARD_BAD alarm, and the software shut the laserautomatically.

Handling Procedure

l Cause 1: The user shuts down the laser.

1. Remove the alarm shutdown setting, and then check whether the alarm is cleared. Fordetails, refer to Configuring Interfaces in OptiX RTN 950 Radio TransmissionSystem Configuration Guide manual.

l Cause 2: The board reports the HARD_BAD alarm, and the software shut the laserautomatically.

1. On the T2000, check the current alarms or the history alarms for the HARD_BADalarm.

2. If the HARD_BAD alarm occurs, cold-reset the board. For details, refer to 8.16Resetting Boards.

3. If the alarm persists, replace the board. For details, refer to 5 ReplacingComponents.

----End

Related Information

None.

9.3.52 LFA

Description

The LFA is an alarm indicating the loss of E1 basic frame alignment. This alarm indicates thatthe E1 double frame is failed in basic frame delimitation and that the delimitation synchronousstatus is lost.

Attribute



Parameters

None.

None.



9-83

Impact on Systeml When the LFA alarm occurs, the relevant E1 link is deactivated, and then the available

links in the IMA group are reduced.l For the VCTRUNK link that is bound with only one path, if the LFA alarm occurs, the

services are interrupted.l After the LFA alarm is cleared, the relevant E1 link in the IMA group is automatically

activated.l The LFA alarm will be suppressed when the UP_E1_AIS alarm occurs.

Possible CausesThe possible causes of the LFA alarm are as follows:

l Cause 1: The frame format of the E1 signals transmitted from the opposite NE isinconsistent with the received frame format that is specified at the local NE.

l Cause 2: The equipment is faulty.

Handling Procedurel Cause 1: The frame format of the E1 signals transmitted from the opposite NE is

inconsistent with the received frame format that is specified at the local NE.1. On the T2000, check whether the frame format of the E1 signals transmitted from the

opposite NE is consistent with the received frame format that is specified at the localNE. For details, refer to Setting the Advanced Attributes of PDH Interfaces in OptiXRTN 950 Radio Transmission System Configuration Guide manual.

2. If not, modify the configuration and make sure the frame formats of the E1 signals atthe two NEs match. Then, check whether the LFA alarm is cleared.

l Cause 2: The equipment is faulty.1. On the T2000, check whether the hardware-related alarms occur on the related boards

of the two NEs, such as the HARD_BAD alarm.2. If yes, cold-reset the board that reports the hardware-related alarm and check whether

the LFA alarm is cleared. For details, refer to 8.16 Resetting Boards.3. If the LFA alarm persists, replace the related board and check whether the LFA alarm

is cleared. For details, refer to 5 Replacing Components.

----End

Related InformationBasic frame

According to ITU-T Recommendation G.704, a basic frame shows the format in which the framesynchronization sequence (FAS) is carried in the even frames, and the non-framesynchronization sequence (NFAS) is carried in the odd frames.

9.3.53 IF_CABLE_OPEN

DescriptionThe IF_CABLE_OPEN is an alarm indicating that the IF cable is disconnected.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


0x323F Major Equipment 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 IF port 1 of the related board.

Impact on SystemThe services carried over the IF port are interrupted.

Possible Causesl The IF cable is loose or faulty.

l The IF port on the IF board is faulty.

l The power module of the ODU is faulty.

Handling Procedure

Step 1 Check whether the connector of the IF cable is loose or whether the connector is not properlymade.

If... Then...

The connector is loose Tighten the connector.

The connector is not properly made Make a new connector. For details refer to QuickInstallation Guide.

None of the above Go to the next step.

Step 2 Check whether the jacket of the IF cable is damaged.

If... Then...

Yes Use a multimeter to test whether the IF cable conducts electricity well, and replace thecable if the IF cable fails to conduct electricity.

No Go to the next step.

Step 3 Replace the IF board.



9-85

If... Then...

The alarm disappears after the IF board isreplaced

The fault is rectified, and the alarm handlingis complete.

The alarm persists after IF board is replaced Go to the next step.

Step 4 Replace the ODU.

----End


9.3.54 IF_INPWR_ABN

DescriptionThe IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.

Attribute


0x312D Major Equipment alarm


Name Meaning

Parameter 1 l 0x01 indicates that the input power is too high.

l 0x02 indicates that the input power is too low.

Impact on SystemThe services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switchingmay be triggered.

Possible Causesl There is an inloop operation on the IF port.

l The IF board is faulty.

l The IF cables are faulty.


Maintenance Guide


Issue 02 (2009-06-30)

l The ODU is faulty.

Handling Procedure

Step 1 Check whether there is an inloop operation on the IF port.

If... Then...

Yes Cancel the loopback operation.


Step 2 Check whether the IF cables are soggy, broken, or pressed.

If... Then...

Yes Replace the IF cables.


Step 3 Check whether the cable connector workmanship meets the requirement.

If... Then...

No Make a new connector.

Yes Go to the next step.

Step 4 Replace the IF board connecting to the ODU that reports the IF_INPWR_ABN alarm..

If... Then...

The alarm disappears after the board isreplaced


The alarm persists after the board isreplaced

Go to the next step.

Step 5 Replace the ODU that reports the IF_INPWR_ABN alarm.

----End

Related Information

None.

9.3.55 LMFA

Description

The LMFA is an alarm indicating the loss of E1 multiframe alignment. This alarm indicates thatthe E1 CRC-4 frame is failed in multiframe delimitation and that the delimitation synchronousstatus is lost.



9-87

Attribute



ParametersNone.

None.

Impact on Systeml When the LMFA alarm occurs, the relevant E1 link is deactivated, and then the available

links in the IMA group are reduced.l For the VCTRUNK link that is bound with only one path, if the LMFA alarm occurs, the

services are interrupted.l After the LMFA alarm is cleared, the relevant E1 link in the IMA group is automatically

activated.l The LMFA alarm will be suppressed when the UP_E1_AIS alarm occurs.

Possible CausesThe possible causes of the LMFA alarm are as follows:

l Cause 1: The frame format of the E1 signals transmitted from the opposite NE isinconsistent with the received frame format that is specified at the local NE.

l Cause 2: The equipment is faulty.

Handling Procedurel Cause 1: The frame format of the E1 signals transmitted from the opposite NE is

inconsistent with the received frame format that is specified at the local NE.1. On the T2000, check whether the frame format of the E1 signals transmitted from the

opposite NE is consistent with the received frame format that is specified at the localNE. For details, refer to Setting the Advanced Attributes of PDH Interfaces in OptiXRTN 950 Radio Transmission System Configuration Guide manual.

2. If not, modify the configuration and make sure the frame formats of the E1 signals atthe two NEs match. Then, check whether the LMFA alarm is cleared.

l Cause 2: The equipment is faulty.1. On the T2000, check whether the hardware-related alarms occur on the related boards

of the two NEs, such as the HARD_BAD alarm.2. If yes, cold-reset the board that reports the hardware-related alarm and check whether

the LMFA alarm is cleared. For details, refer to 8.16 Resetting Boards.3. If the LMFA alarm persists, replace the related board and check whether the LMFA

alarm is cleared. For details, refer to 5 Replacing Components.

----End


Maintenance Guide


Issue 02 (2009-06-30)

Related InformationBasic frame

According to ITU-T Recommendation G.704, a basic frame shows the format in which the framesynchronization sequence (FAS) is carried in the even frames, and the non-framesynchronization sequence (NFAS) is carried in the odd frames.

Multiframe

A multiframe contains 8 basic frames, and it can be checked in the CRC mode.

9.3.56 LOOP_ALM

DescriptionThe LOOP_ALM is an alarm indicating the loopback. This alarm occurs when the serviceloopback is set.

Attribute


0x00F0 Minor Equipment alarm




9-89

Name Meaning

Parameter 1 Indicates the loopback type.

l 0x00: Optical/Electrical interface inloop.

l 0x01: Optical/Electrical interface outloop.

l 0x02: Path inloop.

l 0x03: Path outloop.

l 0x04: Loopback at the client side.

l 0x05: Loopback at the multiplexing side.

l 0x06: SPI inloop.

l 0x07: SPI outloop.

l 0x08: Inloop at the ATM layer.

l 0x09: Outloop at the ATM layer.

l 0x0A: Inloop at the PHY layer.

l 0x0B: Outloop at the PHY layer.

l 0x0C: Inloop at the MAC layer.

l 0x0D: Outloop at the MAC layer.

l 0x0E: VC-4 timeslot inloop.

l 0x0F: VC-4 timeslot outloop.

l 0x10: VC-3 timeslot inloop.

l 0x11: VC-3 timeslot outloop.

l 0x12: VC-12 timeslot inloop.

l 0x13: VC-12 timeslot outloop.

Impact on SystemWhen the LOOP_ALM alarm occurs, there is the loopback in the system, and services at theoptical interface or in the path which reports the alarm are interrupted.

Possible CausesThe possible causes of the LOOP_ALM alarm are as follows:

l Cause 1: Loopback is set on the port.

l Cause 2: Loops exists in the service.

Handling Procedurel Cause 1: Loopback is set on the port.

1. On the T2000, check whether the loopback is set on the port which reports theLOOP_ALM alarm. For details, refer to 8.9 Configuring Port Loopback.

2. If yes, release the loopback of the port and check whether the LOOP_ALM alarm iscleared.


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 2: Loops exists in the service.

1. On the T2000, check whether loops exist in the service.

2. If yes, modify the service configuration and delete the loops.

3. Optional: For Ethernet services, enable the function of loopback port shutdown torelease the service loopback and then check whether the alarm is cleared. For details,refer to Setting the Advanced Attributes of Ethernet Interfaces in the OptiX RTN950 Radio Transmission System Configuration Guide manual.

----End

Related Information

None.

9.3.57 LSR_BCM_ALM

Description

The LSR_BCM_ALM is an alarm indicating that the bias current of the laser crosses thethreshold.

Attribute


0x003A Major Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the bias current crosses the threshold.

l 0x01: The bias current is excessively high.

l 0x02: The bias current is excessively low.

Impact on Systeml When the LSR_BCM_ALM alarm occurs, the gain is insufficient or the laser is damaged,

in the severe case of which the services may be interrupted.

l The LSR_BCM_ALM alarm will be suppressed when one of the LASER_MOD_ERR,ALM_ALS and LASER_SHUT alarms occurs.



9-91

Possible CausesThe possible causes of the LSR_BCM_ALM alarm are as follows:

l Cause 1: The laser is aged.

l Cause 2: This board is faulty.

Handling Procedurel Cause 1: The laser is aged.

1. Replace the optical module on the port which reports the LSR_BCM_ALM alarm andthen, check whether the alarm is cleared. For details, refer to 5.9 Replacing thePluggable Optical Module.

l Cause 2: This board is faulty.1. Replace the board which reports the LSR_BCM_ALM alarm and then, check whether

the alarm is cleared. For details, refer to 5 Replacing Components.

----End


9.3.58 LSR_NO_FITED

DescriptionThe LSR_NO_FITED is an alarm indicating that the laser is not installed. This alarm occurswhen the optical port is enabled but not installed with the optical module.

Attribute



ParametersNone.

None.

Impact on Systeml When the LSR_NO_FITED alarm occurs, the data cannot be transmitted on the optical

port.l In the case of the LSR_NO_FITED alarm, the system suppresses the ETH_LOS and all the

other alarms related to optical module.

Possible CausesThe possible causes of the LSR_NO_FITED alarm are as follows:


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 1: The enabled optical port is not installed with the optical module.

l Cause 2: The optical module or the board is faulty, so that the optical module cannot bedetected.

Handling Procedurel Cause 1: The enabled optical port is not installed with the optical module.

1. Check whether the optical port is installed with the optical module.2. If not, install a proper optical module to the optical port according to the version

mapping table. Then, check whether the alarm is cleared.l Cause 2: The optical module or the board is faulty, so that the optical module cannot be

detected.1. Replace the optical module on the port and then, check whether the alarm is cleared.

For details, refer to 5.9 Replacing the Pluggable Optical Module.2. Replace the board which reports the LSR_NO_FITED alarm and then, check whether

the alarm is cleared. For details, refer to 5 Replacing Components.

----End


9.3.59 LSR_WILL_DIE

DescriptionThe LSR_WILL_DIE is an alarm indicating that the a laser will be out of work soon. This alarmindicates that the laser is unavailable.

Attribute



ParametersNone.

None.

Impact on Systeml When the LSR_WILL_DIE alarm occurs, bit errors occur in the services. If the optical

module is not replaced in a timely manner, the services are interrupted after the laser isdamaged.

l The LSR_WILL_DIE alarm will be suppressed when one of the LSR_NO_FITED andLASER_MOD_ERR alarms occurs.



9-93

Possible CausesThe possible causes of the LSR_WILL_DIE alarm are as follows:

l Cause 1: The laser is aged.

l Cause 2: The detection circuit of the board is faulty.

Handling Procedurel Cause 1: The laser is aged.

1. Replace the optical module and check whether the alarm is cleared. For details, referto 5.9 Replacing the Pluggable Optical Module.

l Cause 2: The detection circuit of the board is faulty.1. Replace the board which reports the LSR_WILL_DIE alarm and check whether the

alarm is cleared. For details, refer to 5 Replacing Components.

----End


9.3.60 LTI

DescriptionThe LTI is an alarm indicating the loss of synchronization clock source.

Attribute





Maintenance Guide


Issue 02 (2009-06-30)

Name Meaning

Parameter 1 Indicates the type of the synchronization source that is lost.

l 0x01: All the synchronization sources of the system clock are lost.

l 0x02: All the synchronization sources of the first 2M phase-locked source arelost.

l 0x03: All the synchronization sources of the second 2M phase-locked sourceare lost.

Impact on System

When the LTI alarm occurs, the pointer justification may increase due to a low quality clockand make the bit error rate increase.

Possible Causes

The possible causes of the LTI alarm are as follows:

l Cause 1: The external clock source received by the clock interface of CXPR is lost.

l Cause 2: The line clock source is lost.

l Cause 3: The clock source is locked. In this case, when the current clock source is lost, itcannot be switched to other normal clock source automatically.

Handling Procedure

l Cause 1: The external clock source signal received by the clock interface of CXPR is lost.

1. On the T2000, check whether the EXT_SYNC_LOS alarm occurs. For details, referto 8.2 Querying Current Alarms of a Board.

2. If yes, clear the EXT_SYNC_LOS alarm and then check whether this alarm is cleared.

l Cause 2: The line clock source is lost.

1. On the T2000, check whether the signal loss alarms such as the ETH_LOS alarmsoccur. If yes, clear these alarms and then check whether the LTI alarm is cleared.

2. If the LTI alarm persists, perform a cold reset on the CXPR board, and then checkwhether this alarm is cleared. For details, refer to 8.16 Resetting Boards.

3. If the alarm persists, replace the CXPR board, and then check whether the alarm iscleared. For details, refer to 5 Replacing Components.

l Cause 3: The clock source is locked. In this case, when the current clock source is lost, itcannot be switched to other normal clock source automatically.

1. On the T2000, check whether the clock source is in the "non-revertive" state. If yes,re-configure the clock source so that it can recover automatically. Then, check whetherthe alarm is cleared. For details, refer to Configuring the Clock Source Reversion inConfiguration Guide manual.

2. Check whether the SYNC_LOCKOFF alarm occurs in the system. If yes, clear theSYNC_LOCKOFF alarm first and then check whether the TOP_LTI alarm is cleared.

----End



9-95

Related Information

None.

9.3.61 MAC_FCS_EXC

Description

The MAC_FCS_EXC is an alarm indicating that the bit error threshold-crossing event is detectedat the MAC layer. The software detects the number of bytes received by the MAC chip and thenumber of bytes that have bit errors, and calculates whether the number of bit errors exceeds thethreshold. Then MAC_FCS_EXC alarm occurs when the threshold is crossed.

Attribute


0x31FA Major Communication alarm

Parameters

None.

None.

Impact on Systeml When the MAC_FCS_EXC alarm occurs, the service performance may be degraded and

the services may be interrupted.l The MAC_FCS_EXC alarm will be suppressed when one of the ETH_LOS,

ETH_LINK_DOWN and LAG_MEMBER_DOWN alarms occurs.

Possible Causes

The possible causes of the MAC_FCS_EXC alarm are as follows:

l Cause 1: The line signals degrade.

l Cause 2: The input optical power is abnormal.

l Cause 3: The fiber header is dirty.

Handling Procedure

l Cause 1: The line signals degrade.1. On the T2000, check whether the LOOP_ALM alarm occurs. If yes, clear the

LOOP_ALM alarm first and then check whether the MAC_FCS_EXC alarm iscleared. For details, refer to 8.2 Querying Current Alarms of a Board.

2. If the MAC_FCS_EXC alarm persists, check whether the DOS attack exists. If yes,isolate the DOS attack source, and then check whether the MAC_FCS_EXC alarm iscleared.


Maintenance Guide


Issue 02 (2009-06-30)

3. If the MAC_FCS_EXC alarm still persists, check whether any fault occurs in the fiberor cable. Replace the faulty fiber or cable, and then check whether theMAC_FCS_EXC alarm is cleared.

l Cause 2: The input optical power is abnormal.

1. Check whether the IN_PWR_ABN alarm occurs on the port which reports theMAC_FCS_EXC alarm.

2. If yes, clear the IN_PWR_ABN alarm first and then check whether theMAC_FCS_EXC alarm is cleared.

l Cause 3: The fiber header is dirty.

1. Clean the fiber header and the receive optical interface on the board. For details, referto 8.24 Inspecting and Cleaning the Optical Fiber Connectors.

----End

Related Information

None.

9.3.62 MP_DELAY

Description

The MP_DELAY delay is an alarm indicating the group member delay. This alarm occurs whenthe delay of the group members exceeds the configured threshold.

Attribute



Parameters


Name Meaning



Parameter 3, Parameter 4 Indicates the port ID.



9-97

Name Meaning

Parameter 5 Indicates the timeslot number or the path number.

0xff: Parameter 5 is reserved.

Impact on System

When the MP_DELAY alarm occurs, the services in the MP group are affected and the servicesignals degrade.

Possible Causes

The possible causes of the MP_DELAY alarm are as follows:


l Cause 2: The configured value of the Enable Differential Delay is too low.

Handling Procedure


1. Check whether the congestion occurs at the network side. If yes, perform the expansionas required, and then check whether the alarm is cleared. For details, refer to the OptiXRTN 950 Radio Transmission System Configuration Guide manual.

2. If the MP_DELAY alarm persists, replace the cable of the port which reports the alarm.Then, check whether the MP_DELAY alarm is cleared.

l Cause 2: The configured value of the Enable Differential Delay is too low.

1. On the T2000, check whether the configured value of the Enable DifferentialDelay is too low. For details, refer to Creating MP Groups in the OptiX RTN 950 RadioTransmission System Configuration Guide manual.

2. Increase the value of the Enable Differential Delay depending on the actual scene,and check whether the MP_DELAY alarm is cleared.

----End

Related Information

None.

9.3.63 MP_DOWN

Description

The MP_DOWN alarm indicates a failure of the MP group. When the number of enabled linksin the MP group is less than the configured minimum number of enabled links in the MP group,the MP_DOWN alarm is reported. The default minimum number of enabled links is 1.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters

None.

None.

Impact on Systeml When the MP group fails, all the services transmitted over the MP group are interrupted.

l When the number of enabled links in the MP group is more than the configured minimumnumber of enabled links in the MP group, the MP_DOWN alarm is cleared automatically.

Possible Causes

The possible causes of the MP_DOWN alarm are as follows:

l Cause 1: The number of enabled links in the MP group is less than the configured MinActivated Link Count of the MP group.

l Cause 2: The configuration of MP group on the two ends is inconsistent.

l Cause 3: The NCP protocol is abnormal.


Handling Procedure

l Cause 1: The number of enabled links in the MP group is less than the configured MinActivated Link Count of the MP group.1. On the T2000, check whether the number of enabled links in the MP group is less than

the configured Min Activated Link Count of the MP group. For details, refer toConfiguring ML-PPP in the Configuration Guide manual.

2. If yes, modify the configuration value of Min Activated Link Count to less than thenumber of enabled links in the MP group, and check whether the MP_DOWN alarmis cleared.

l Cause 2: The configuration of MP group on the two ends is inconsistent.1. On the T2000, check whether the configuration of MP group on the two ends is

consistent. If not, modify the configuration on the two ends and make it be consistent.For details, refer to Configuring ML-PPP in the Configuration Guide manual.

2. Click Reset and enable the the MP protocol again. Then, check whether theMP_DOWN alarm is cleared.

l Cause 3: The NCP protocol is abnormal.1. On the T2000, check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm occurs

on the links in the MP group. For details, refer to 8.2 Querying Current Alarms ofa Board.



9-99

2. If yes, clear the PPP_LCP_FAIL or PPP_NCP_FAIL alarm first, and check whetherthe MP_DOWN alarm is cleared.


1. On the T2000, check whether any alarms occur on the links in the MP group indicatingloss of signals, such as the T_ALOS alarm.

2. If yes, clear the T_ALOS alarm first, and check whether the MP_DOWN alarm iscleared.

----End

Related Information

None.

9.3.64 MPLS_TUNNEL_BDI

Description

The MPLS_TUNNEL_BDI is an alarm of tunnel backward defect indication. This alarm occurswhen the BDI packet is received at the receive end indicating that the forward tunnel is faulty.

Attribute



Parameters


Name Meaning


Impact on System

When the MPLS_TUNNEL_BDI alarm occurs, the services at the transmit side are affected.

Possible Causes

The cause of the MPLS_TUNNEL_BDI alarm is as follows:

The upstream NE detects that the tunnel is faulty.


Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedurel Cause: The upstream NE detects that the tunnel is faulty.

1. Check whether an anomaly occurs on the physical link between the local NE and theupstream NE, such as a fiber or cable cut, an optical module fault or a board fault.

2. If yes, remove the anomaly, and then check whether the alarm is cleared.

----End


9.3.65 MPLS_TUNNEL_Excess

DescriptionThe MPLS_TUNNEL_Excess is an alarm indicating that excessive trail termination sourceidentifiers are received. During three consecutive CV/FFD periods, this alarm occurs when fiveor more than five correct CV/FFD packets are received.

Attribute


0x320F Minor Communication alarm


Name Meaning


Impact on SystemThe services may be interrupted or redundant packets are received.

Possible CausesThe possible causes of the MPLS_TUNNEL_Excess alarm are as follows:

l Cause 1: The OAM attributes configured at the two ends are inconsistent.

l Cause 2: The tunnel configuration is incorrect, that is, many tunnels are configured withthe same ingress node ID and same tunnel ID.



9-101

l Cause 3: The misconnection occurs on the physical link.

Handling Procedure

l Cause 1: The OAM attributes configured at the two ends are inconsistent.

1. On the T2000, check whether the OAM attributes configured at the two ends areconsistent. For details, refer to Setting the MPLS OAM Parameters of a Tunnel in theOptiX RTN 950 Radio Transmission System Feature Description manual.

2. If not, modify the configuration to match each other, and then check whether the alarmis cleared.

l Cause 2: The tunnel configuration is incorrect, that is, many tunnels are configured withthe same ingress node ID and same tunnel ID.

1. On the T2000, check whether there are many tunnels configured with the same ingressnode ID and same tunnel ID.

2. If yes, delete the redundant tunnels or modify the Tunnel ID as other numbers. Then,check whether the alarm is cleared.


1. Check whether the fiber or cable is correctly connected.

2. If not, recover the correct connection and check whether the alarm is cleared.

----End

Related Information

None.

9.3.66 MPLS_TUNNEL_FDI

Description

The MPLS_TUNNEL_FDI is an alarm of tunnel forward defect indication. This alarm occurswhen the FDI packet is received, indicating a tunnel at the physical layer is faulty.

Attribute



Parameters



Maintenance Guide


Issue 02 (2009-06-30)

Name Meaning


Impact on System

When the MPLS_TUNNEL_FDI alarm occurs, the services maybe interrupted.

Possible Causes

The cause of the MPLS_TUNNEL_FDI alarm is as follows:

The upstream NE detects that a fault occurs at the physical layer.

Handling Procedure

l Cause: The upstream NE detects that a fault occurs at the physical layer.1. Check whether an anomaly occurs on the physical link between the local NE and the

upstream NE, such as a fiber or cable cut, an optical module fault or a board fault.2. If yes, remove the anomaly, and then check whether the alarm is cleared.

----End

Related Information

None.

9.3.67 MPLS_TUNNEL_LOCV

Description

The MPLS_TUNNEL_LOCV is an alarm indicating the loss of tunnel connectivity verification.This alarm occurs when the expected CV/FFD packet is not received within a period of threeconsecutive cycles.

Attribute


0x320E Critical Communication alarm

Parameters




9-103

Name Meaning


Impact on Systeml When the MPLS_TUNNEL_LOCV alarm occurs, the services that the faulty tunnel carries

are interrupted.

l The MPLS_TUNNEL_LOCV alarm will be suppressed when the MPLS_TUNNEL_FDIalarm occurs.

Possible Causes

The possible causes of the MPLS_TUNNEL_LOCV alarm are as follows:

l Cause 1: The CV/FFD is stopped at the ingress node.

l Cause 2: The service is configured to an incorrect port.


l Cause 4: The network is severely congested.

Handling Procedure

l Cause 1: The CV/FFD is stopped at the ingress node.

1. On the T2000, check whether the CV/FFD is stopped at the ingress node. For details,refer to Starting the CV/FFD for a Tunnel in the OptiX RTN 950 Radio TransmissionSystem Feature Description manual.

2. If the CV/FFD is stopped, restart the CV/FFD and check whether the alarm is cleared.

l Cause 2: The service is configured to an incorrect port.

1. On the T2000, check whether the service is configured to the correct port.

2. If not, re-configure the service to the correct port and check whether the alarm iscleared.


1. On the T2000, check whether there is COMMUN_FAIL alarm on the opposite NE.For details, refer to 8.2 Querying Current Alarms of a Board. If yes, it indicatesthat the opposite NE is undergoing reset. Clear the COMMUN_FAIL first and checkwhether the MPLS_TUNNEL_LOCV alarm on the local NE is cleared.

2. On the T2000, check whether the alarms related to boards or optical modules occuron the two NEs that the faulty link connects. If yes, clear these alarms and then checkwhether the MPLS_TUNNEL_LOCV alarm is cleared.

3. If the alarm persists, check whether the fiber or cable is faulty. If yes, replace the faultyfiber or cable.


1. Select a bigger parameter value for the Detection Packet Period. For details, refer toSetting the MPLS OAM Parameters of a Tunnel in the OptiX RTN 950 RadioTransmission System Feature Description manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. Check the bandwidth utilization of the tunnel. If the bandwidth is already exhausted,increase the bandwidth or avoid the transmission of a large amount of unauthorizeddata. Then, check whether the alarm is cleared.

----End

Related Information

None.

9.3.68 MPLS_TUNNEL_MISMATCH

Description

The MPLS_TUNNEL_MISMATCH is an alarm indicating the trail termination source identifiermismatch. This alarm occurs when no CV/FFD packets with correct trail termination sourceidentifiers are received within a period of three consecutive CV/FFD cycles.

Attribute


0x3210 Critical Communication alarm

Parameters


Name Meaning


Impact on System

When the MPLS_TUNNEL_MISMATCH alarm occurs, the services maybe interrupted orpackets from other tunnels are received.

Possible Causes

The possible causes of the MPLS_TUNNEL_MISMATCH alarm are as follows:

l Cause 1: The tunnel configuration is incorrect, that is, the source NE and the sink NE in aspecific tunnel are configured with the inconsistent LSR ID or tunnel ID.




9-105

Handling Procedurel Cause 1: The tunnel configuration is incorrect, that is, the tunnel source NE and the tunnel

sink NE are configured with the inconsistent LSR ID or tunnel ID.1. On the T2000, check whether the tunnel configuration at the tunnel source NE is

consistent with the configuration at the tunnel sink NE.2. If not, modify the configuration to match each other and check whether the alarm is

cleared.l Cause 2: The misconnection occurs on the physical link.

1. Check whether the fiber or cable is correctly connected.2. If not, recover the correct connection and check whether the alarm is cleared.

----End


9.3.69 MPLS_TUNNEL_MISMERGE

DescriptionThe MPLS_TUNNEL_MISMERGE is an alarm indicating that the trail termination sourceidentifier is incorrectly merged. This alarm occurs when the CV/FFD packets with correct andincorrect trail termination source identifiers are received within a period of three consecutiveCV/FFD cycles.

Attribute




Name Meaning


Impact on SystemWhen the MPLS_TUNNEL_MISMERGE alarm occurs, the packets from other tunnels arereceived.


Maintenance Guide


Issue 02 (2009-06-30)

Possible Causes

The possible causes of the MPLS_TUNNEL_MISMERGE alarm are as follows:

l Cause 1: The tunnel configuration is incorrect, that is, there are many tunnels with the samelabels or IDs on the sink NE.


Handling Procedure

l Cause 1: The tunnel configuration is incorrect, that is, there are many tunnels with the samelabel or ID on the sink NE.

1. On the T2000, check whether there are many tunnels with the same label or ID on thesink NE.

2. If yes, delete the redundant tunnels or modify the Tunnel configuration. Then, checkwhether the alarm is cleared.


1. Check whether the fiber or cable is correctly connected.

2. If not, recover the correct connection and check whether the alarm is cleared.

----End

Related Information

None.

9.3.70 MPLS_TUNNEL_SD

Description

The MPLS_TUNNEL_SD is an alarm indicating the tunnel signal is degraded. This alarm occurswhen the packet loss ratio of the connectivity check (CC) packets exceeds the SD threshold butnot the SF threshold.

Attribute



Parameters




9-107

Name Meaning


Impact on System

When the MPLS_TUNNEL_SD alarm occurs, the service quality degrades and a small amountof packets are lost.

Possible Causes

The possible cause of the MPLS_TUNNEL_SD alarm are as follows:

l Cause 1: The service bit error ratio is excessively high.

l Cause 2: No bandwidth is available.

l Cause 3: Other anomalies occur on the carrier layer.

Handling Procedure


1. On the T2000, check whether the MAC_FCS_EXC alarm occurs. For details, refer to8.2 Querying Current Alarms of a Board.

2. If yes, clear the MAC_FCS_EXC first, and then check whether theMPLS_TUNNEL_SD alarm is cleared.


1. On the T2000, check whether the bandwidth configured to the tunnel is fully used.

2. If yes, expand the bandwidth of tunnel or eliminate the source where a large amountof illegal data is transmitted. Then, check whether the alarm is cleared.


1. On the T2000, check whether other anomalies occur on the carrier layer.

2. If yes, remove the configuration inconsistency fault or the protocol operation anomaly,and then check whether the alarm is cleared.

----End

Related Information

None.

9.3.71 MPLS_TUNNEL_SF

Description

The MPLS_TUNNEL_SF is an alarm indicating the tunnel signal is severely degraded. Thisalarm occurs when the loss ratio of the CC packets exceeds the SF threshold but CC packets canstill be received in three consecutive periods.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute




Name Meaning


Impact on SystemWhen the MPLS_TUNNEL_SF alarm occurs, the service quality degrades severely and a largeamount of packets are lost.

Possible CausesThe possible cause of the MPLS_TUNNEL_SF alarm are as follows:




Handling Procedurel Cause 1: The service bit error ratio is excessively high.

1. On the T2000, check whether the MAC_FCS_EXC alarm occurs. For details, refer to8.2 Querying Current Alarms of a Board.

2. If yes, clear the MAC_FCS_EXC first, and then check whether theMPLS_TUNNEL_SD alarm is cleared.

l Cause 2: No bandwidth is available.1. On the T2000, check whether the bandwidth configured to the tunnel is fully used.2. If yes, expand the bandwidth of tunnel or eliminate the source where a large amount

of illegal data is transmitted. Then, check whether the alarm is cleared.l Cause 3: Other anomalies occur on the carrier layer.

1. On the T2000, check whether other anomalies occur on the carrier layer.2. If yes, remove the configuration inconsistency fault or the protocol operation anomaly,

and then check whether the alarm is cleared.

----End



9-109

Related Information

None.

9.3.72 MPLS_TUNNEL_UNKNOWN

Description

The MPLS_TUNNEL_UNKNOWN is an alarm indicating the tunnel unknown defect. Thisalarm occurs when the type and the cycle of the continuity check packets received within acertain period (three times of the cycle) are not the expected type and cycle.

Attribute



Parameters


Name Meaning


Impact on System

When the MPLS_TUNNEL_UNKNOWN alarm occurs, the OAM function is affected.

Possible Causes

The cause of the MPLS_TUNNEL_UNKNOWN alarm is as follows:

The OAM attributes configured at the two ends are inconsistent, such as the type or cycle of theCC packet.

Handling Procedure

l Cause: The OAM attributes configured at the two ends are inconsistent, such as the typeor cycle of the CC packet.

1. On the T2000, check whether the OAM attributes configured at the two ends areconsistent. For details, refer to Setting the MPLS OAM Parameters of a Tunnel in theOptiX RTN 950 Radio Transmission System Feature Description manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. If not, modify the configuration to match each other, and then check whether the alarmis cleared.

----End

Related Information

None.

9.3.73 MW_BER_EXC

Description

The MW_BER_EXC is an alarm indicating that there are excessive bit errors on the microwavelink. This alarm is reported if the BER on the microwave link crosses the specified threshold(10-3 by default).

Attribute


0x3246 Minor Service alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01indicates that the alarm is reported by port 1 of the related board.

Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01indicates that the alarm is reported by path 1.

Impact on System

The services over the port are interrupted.

Possible Causesl Signal fading on the microwave link is too high.

l The transmitter at the remote end is faulty.

l The receiver at the local end is faulty.



9-111

Handling Procedure

Step 1 Check whether the MW_FECUNCOR alarm is reported.

If... Then...

Yes Clear the MW_FECUNCOR alarm.


Step 2 Replace the local IF board.

Step 3 Check whether the alarm is cleared. If the alarm persists, replace the opposite IF board.

----End

Related Information

None.

9.3.74 MW_BER_SD

Description

The MW_BER_SD is an alarm indicating that signal deteriorates on the microwave link. Thisalarm is reported if the BER on the microwave link crosses the specified threshold (10-6 bydefault) and does not reach the MW_BER_EXC alarm threshold (10-3 by default).

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01indicates that the alarm is reported by port 1 of the related board.

Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01indicates that the alarm is reported by path 1.


Maintenance Guide


Issue 02 (2009-06-30)

Impact on SystemThe service performance over the port deteriorates, and channel switching may be triggered ifthe 1+1 FD/SD protection is provided.

Possible Causesl Signal fading on the microwave link is too high.

l The transmitter at the remote end is faulty.

l The receiver at the local end is faulty.

Handling Procedure

Step 1 Check whether the MW_FECUNCOR alarm is reported.

If... Then...

Yes Clear the MW_FECUNCOR alarm.


Step 2 Replace the local IF board.

Step 3 Check whether the alarm is cleared. If the alarm persists, replace the opposite IF board.

----End


9.3.75 MW_LIM

DescriptionThe MW_LIM is an alarm indicating that a mismatched microwave link identifier is detected.This alarm is reported if a board detects a mismatched Link ID in the microwave frameoverheads.

Attribute






9-113

Name Meaning

Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that thealarm is reported by port 1 of the related board.

Impact on System

The microwave link fails to carry services.

Possible Causesl The Link ID of the local station mismatches the Link ID of the remote station.

l The receive frequency at the local end is incorrectly configured.

l The direction of the antenna is incorrectly configured. As a result, the antenna receives themicrowave from other stations.

Handling Procedure

Step 1 Determine the IF port that reports the alarm according to alarm parameters.

Step 2 Check whether the Link ID of the local station matches the Link ID of the remote station.

If ... Then ...

No, Modify the data configuration.

Yes, Go to the next step.

Step 3 Check whether the receive/transmit frequencies at the local end are consistent with those at theremote end.

If ... Then ...

No, Modify the data configurations.

Yes, Go to the next step.

Step 4 Adjust the direction of the antenna to align it properly with the antenna at the remote end.

----End

Related Information

None.

9.3.76 MW_LOF

Description

The MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters


Name Meaning


Impact on System

The services are interrupted. If the system is configured with protection, protection switchingmay be triggered.

Possible Causesl The microwave link performance degrades.

l The transmit unit of the remote station is faulty.

l The receive unit of the local station is faulty.

l The working modes of the IF units at the local and the remote stations are the same.

l The working modes of the ODUs at the local and the remote stations are the same.

Handling Procedure

Step 1 Refer to Troubleshooting Microwave Links.

----End

Related Information

None.

9.3.77 MW_RDI

Description

The MW_RDI is an alarm indicating that there are defects at the remote end of the microwavelink. This alarm is reported if an IF board detects an RDI in the microwave frame overheads.



9-115

Attribute


0x312B Minor Communication alarm

Parameters


Name Meaning

Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that thealarm is reported by port 1 of the board.

Impact on System

If the local station is configured with reverse switching and both the active and standby boardsreceive the MW_RDI alarm at the same time, the 1+1 switching may be triggered. This alarmalso indicates that service reception at the remote station may be interrupted.

Possible Causes

After detecting a service alarm that is caused by a microwave link fault, the receive station returnsa microwave link fault indication to the transmit station.

Handling Procedure

Step 1 Handle the microwave alarm occurred to the remote station.

----End

Related Information

None.

9.3.78 MW_FECUNCOR

Description

The MW_FECUNCOR is an alarm indicating that the Reed Solomon (RS) encoding cannot becorrected.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters


Name Meaning


Impact on System

Bit errors occur to the services. If the system is configured with 1+1 FD/SD protection, channelprotection switching may be triggered.

Possible Causesl The microwave link performance degrades.

l The transmit unit of the remote station is faulty.

l The receive unit of the local station is faulty.

Handling Procedure

Step 1 Refer to Troubleshooting Microwave Links.

----End

Related Information

None.

9.3.79 MSSW_DIFFERENT

Description

The MSSW_DIFFERENT is an alarm indicating that the NE software versions on the CXPRboards are inconsistent.



9-117

Attribute


0x023b Major Processing alarm


Name Meaning

Parameter 1 0x01: Files in the FLASH.

0x02: Software that is running currently.

0x03: Software in the CF card.

Parameter 2, Parameter 3 Indicates the number of the inconsistent file on the system controlboards.

Parameter 4 Indicates the alarm cause.

l 0x04: The versions of the files in the working and the protectionareas of a single system control board are inconsistent. Refer tocause 1.

l 0x08: The versions of the files on the working system controlboard are inconsistent with those on the protection systemcontrol board, or in the same directory, files of the working boarddo not have the same name as those of the protection board. Referto cause 2.

l 0x0C: The versions of the files in the working and the protectionareas of a single system control board are inconsistent, and theversions of the files of the working system control board and theprotection system control board are inconsistent. Refer to cause3.

Impact on Systeml When the NE software versions of the working system control board and the protection

system control board are inconsistent, the protection switching of the system is affected.l If no NE software exists on the FLASH, the system cannot restart after the system is

powered off or reset.

Possible CausesThe possible causes of the MSSW_DIFFERENT alarm are as follows:


Maintenance Guide


Issue 02 (2009-06-30)

l Cause 1: The versions of the files in the working and the protection areas of a single systemcontrol board are inconsistent.

l Cause 2: The versions of the files on the working system control board are inconsistentwith those on the protection system control board, or in the same directory, files of theworking board do not have the same name as those of the protection board.

l Cause 3: The versions of the files in the working and the protection areas of a single systemcontrol board are inconsistent, and the versions of the files of the working system controlboard and the protection system control board are inconsistent.

Handling Procedure

l Cause 1: The versions of the files in the working and the protection areas of a single systemcontrol board are inconsistent.1. Determine the correct software version according to the version mapping table.2. Reload the correct software. For details, refer to 6 Software Package Upgrade and

Package Diffusion.l Cause 2: The versions of the files on the working system control board are inconsistent

with those on the protection system control board, or in the same directory, files of theworking board do not have the same name as those of the protection board.1. On the T2000, query the software version of the two boards and determine the correct

software version according to the version mapping table. For details, refer to 8.3Querying the Board Information Report.

2. Reload the correct software. For details, refer to 6 Software Package Upgrade andPackage Diffusion.

3. If the alarm persists, replace the board with the incorrect software version. For details,refer to 5 Replacing Components.

l Cause 3: The versions of the files in the working and the protection areas of a single systemcontrol board are inconsistent, and the versions of the files of the working system controlboard and the protection system control board are inconsistent.1. On the T2000, query the software version of the two boards and determine the correct

software version according to the version mapping table. For details, refer to 8.3Querying the Board Information Report.

2. Reload the correct software. For details, refer to 6 Software Package Upgrade andPackage Diffusion.

3. If the alarm persists, replace the board with the incorrect software version. For details,refer to 5 Replacing Components.

----End

Related Information

None.

9.3.80 NESF_LOST

Description

The NESF_LOST is an alarm indicating that part of the NE software is lost.



9-119

Attribute


0x00d7 Critical Equipment alarm


Name Meaning

Parameter 1, Parameter 2 Indicates the type of the file that is lost in the board software.

Impact on Systeml When the NESF_LOST alarm occurs, if the NE is not reset, the services are not affected.

l Once the NE is reset, the services on the entire NE are interrupted.

Possible CausesThe possible cause of the NESF_LOST alarm is as follows:

Part of the software on the CXPR board is lost or damaged.

Handling Procedurel Cause: Part of the software on the CXPR board is lost or damaged.

1. Press and hold the CF RCV button of the CXPR board for 5 seconds to restore the NEdatabase from the CF card.

2. If the NESF_LOST alarm persists, replace the CF card for a new one which is loadedthe normal software. Then, reload the software to the CXPR board.

----End


9.3.81 NESTATE_INSTALL

DescriptionThe NESTATE_INSTALL is an alarm indicating that the NE is in the installing state. This alarmoccurs when the NE is just delivered from the factory or when the user issues the command toinitialize the NE.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


0xC5 Critical Processing alarm

Parameters

None.

None.

Impact on System

When the NESTATE_INSTALL alarm occurs, no configuration exists at the NE side. Reloadthe configuration at the NE side. Otherwise, the NE cannot be configured with services.

Possible Causes

The possible causes of the NESTATE_INSTALL alarm are as follows:

l Cause 1: The NE is configured with no data or the verification to the command issued bythe user to initialize the NE is not performed. Therefore, the NE is in the initializing state.


Handling Procedure

l Cause 1: The NE is configured with no data or the verification to the command issued bythe user to initialize the NE is not performed. Therefore, the NE is in the initializing state.1. Issue the NE configuration data and perform the verification. Then, check whether

the alarm is cleared.l Cause 2: The CXPR board is faulty.

1. Cold-reset the CXPR board and check whether the NESTATE_INSTALL alarm iscleared. For details, refer to 8.16 Resetting Boards.

2. If the NESTATE_INSTALL alarm persists, replace the CXPR board and checkwhether the NESTATE_INSTALL alarm is cleared. For details, refer to 5 ReplacingComponents.

----End

Related Information

None.

9.3.82 OUT_PWR_ABN

Description

The OUT_PWR_ABN is an alarm indicating that the output optical power is abnormal.



9-121

Attribute


0x001A Critical Equipment alarm

Parameters

None.

None.

Impact on System

When the OUT_PWR_ABN alarm occurs, the service transmission performance is affected. Insevere cases, the services are interrupted.

Possible Causes

The possible causes of the OUT_PWR_ABN alarm are as follows:

l Cause 1: The output optical power is excessively high or low.


Handling Procedure

l Cause 1: The output optical power is excessively high or low.

1. Replace the optical module on the port which reports the alarm and check whether thealarm is cleared. For details, refer to 5.9 Replacing the Pluggable Optical Module.


1. Replace the board which reports the alarm and check whether the alarm is cleared.For details, refer to 5 Replacing Components.

----End

Related Information

None.

9.3.83 PATCH_ACT_TIMEOUT

Description

The PATCH_ACT_TIMEOUT is an alarm indicating that activating the patch package timesout. This alarm occurs when the patch package is in the active state for a period longer than thespecified period of time. In this case, the user needs to process the patch package.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute


0x31E8 Minor Equipment alarm

Parameters

None.

None.

Impact on System

When the PATCH_ACT_TIMEOUT alarm occurs, it does not affect services.

Possible Causes

The cause of the PATCH_ACT_TIMEOUT alarm is as follows:

The patch package is in the active state for a period longer than the specified period of time.

Handling Procedure

l Cause: The patch package is in the active state for a period longer than the specified periodof time.1. Check whether the activated patch package is normal.2. If yes, run the patch package to make the it valid. If not, delete the patch package.

Then, the alarm is cleared automatically.

----End

Related Information

None.

9.3.84 PATCH_DEACT_TIMEOUT

Description

The PATCH_DEACT_TIMEOUT is an alarm indicating that deactivating the patch packagetimes out. This alarm occurs when the patch package is in the inactive state for a period longerthan the specified period of time. In this case, the user needs to process the patch package.

Attribute


0x31E7 Minor Equipment alarm



9-123

ParametersNone.

None.

Impact on SystemWhen the PATCH_DEACT_TIMEOUT alarm occurs, it does not affect services.

Possible CausesThe cause of the PATCH_DEACT_TIMEOUT alarm is as follows:

The patch package is in the inactive state for a period longer than the specified period of time.

Handling Procedurel Cause: The patch package is in the inactive state for a period longer than the specified

period of time.1. To make the patch package valid, activate the patch package.2. Otherwise, delete the patch package. Then, the alarm is cleared automatically.

----End


9.3.85 PATCH_ERR

DescriptionThe PATCH_ERR is an alarm indicating that the automatic patch loading fails. If there arepatches in the running state before the NE is reset, normally, the patches are automatically loadedand executed after the NE is reset. If the loading fails due to an anomaly, the PATCH_ERRalarm occurs.

Attribute


0x026D Major Equipment alarm

ParametersNone.

None.

Impact on SystemThe function of the patch is unavailable.


Maintenance Guide


Issue 02 (2009-06-30)

Possible Causes

The cause of the PATCH_ERR alarm is as follows:

The loading of the patches which are in the running state fails after the NE is reset.

Handling Procedure

l Cause: The loading of the patches which are in the running state fails after the NE is reset.

1. Reload the patch files and check whether the alarm is cleared.

2. If the PATCH_ERR alarm persists, download the correct patch files and then loadthem. For details, refer to the OptiX iManager T2000 Online Help.

3. If the PATCH_ERR alarm still persists, replace the board that reports the alarm andreload the patch files. For details, refer to 5 Replacing Components.

----End

Related Information

None.

9.3.86 PATCH_PKGERR

Description

The PATCH_PKGERR is an alarm indicating that the patch package file is incorrect.

Attribute


0x31F6 Minor Equipment alarm

Parameters

None.

None.

Impact on System

When the PATCH_PKGERR alarm occurs, if the board is protection board, the protectionswitching cannot be performed and the services maybe interrupted.

Possible Causes

The cause of the PATCH_PKGERR alarm is as follows:

The patch package file is damaged or deleted.



9-125

Handling Procedurel Cause: The patch package file is damaged or deleted.

1. Reload the patch files and check whether the alarm is cleared.2. If the PATCH_ERR alarm persists, download the correct patch files and then load

them. For details, refer to the OptiX iManager T2000 Online Help.3. If the PATCH_ERR alarm still persists, replace the board that reports the alarm and

reload the patch files. For details, refer to 5 Replacing Components.

----End


9.3.87 PATCHFILE_NOTEXIST

DescriptionThe PATCHFILE_NOTEXIST is an alarm indicating that the patch file does not exist. If thereare patches in the running state before the NE is reset, normally, the patches are automaticallyloaded and executed after the NE is reset. If the system finds that the patch files do not exist, thePATCHFILE_NOTEXIST alarm occurs.

Attribute


0x026C Major Equipment alarm

ParametersNone.

None.

Impact on SystemWhen the PATCHFILE_NOTEXIST alarm occurs, the patch cannot function.

Possible CausesThe possible cause of the PATCHFILE_NOTEXIST alarm is as follows:

The system finds that the patch files which are in the running state do not exist after the NE isreset.

Handling Procedurel Cause: The system finds that the patch files which are in the running state do not exist after

the NE is reset.


Maintenance Guide


Issue 02 (2009-06-30)

1. Newly download the patch files and then load them. For details, refer to the OptiXiManager T2000 Online Help.

2. If the PATCHFILE_NOTEXIST alarm persists, replace the board that reports thealarm and reload the patch files. For details, refer to 5 Replacing Components.

----End

Related Information

None.

9.3.88 POWER_ABNORMAL

Description

The POWER_ABNORMAL alarm indicates a power supply failure. When the power supply tothe board becomes abnormal, the POWER_ABNORMAL alarm is reported.

Attribute


0x19c Major Equipment alarm

Parameters

Name Meaning

Parameter 1 l 0x00: The 1.1 V power supply fails.

l 0x01: The 1.2 V power supply fails.





l 0x06: The 5 V power supply fails.


Parameter 2 l 0x00: The 1.2 V power supply fails.


l 0x03: The 3.3 VB power supply fails.






9-127

Name Meaning

Parameter 3 l 0x00: The 2nd -48 V power supply fails.

l 0x01: The 2nd 48 V power supply fails.

l 0x02: The 1st -48 V power supply fails.

l 0x03: The 1st 48 V power supply fails.

Impact on System

In the case of the POWER_ABNORMAL alarm, the power supply is abnormal and the boardmay fail to function normally.

Possible Causes

In the case of the POWER_ABNORMAL alarm, first check whether one board or multipleboards report the POWER_ABNORMAL alarm. The possible causes of thePOWER_ABNORMAL alarm are as follows:

l Cause for one board reporting the alarm: The power supply unit on the board is faulty.

l Cause 1 for multiple boards reporting the alarm: The PIU board is faulty.

l Cause 2 for multiple boards reporting the alarm: The power input is abnormal.

Handling Procedure

l Cause for one board reporting the alarm: The power supply unit on the board is faulty.

1. Cold-reset the board that reports the POWER_ABNORMAL alarm. For details, referto 8.16 Resetting Boards.

2. On the T2000, check whether the board enters state Running Status after cold reset.

NOTE

The COMMUN_FAIL alarm is reported during the cold reset. When the COMMUN_FAILalarm ends, the board enters state Running Status.

– If the board fails to enter state Running Status, it indicates that the board is faultyand needs to be replaced.

– If the board enters state Running Status, check whether thePOWER_ABNORMAL alarm ends

3. If the POWER_ABNORMAL alarm persists, replace the board that reports this alarm.For details, refer to 5 Replacing Components.

l Cause 1 for multiple boards reporting the alarm: The PIU board is faulty.

1. Check whether there is HARD_BAD, BUS_ERR or COMMUN_FAIL alarm on thePIU board which indicates the hardware is faulty.

2. If yes, clear these alarms first and then check whether the POWER_ABNORMALalarm is cleared.

l Cause 2 for multiple boards reporting the alarm: The power input is abnormal.

1. Check whether the power supply to the NE is normal. For details, refer to the OptiXRTN 950 Radio Transmission System IDU Quickly Installation Guide manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. If not, make sure that another power supply is connected to the NE and check whetherthe POWER_ABNORMAL alarm is cleared.

----End

Related Information

None.

9.3.89 POWER_ALM

Description

The POWER_ALM is an alarm indicating that the power supply fails. This alarm is reported ifthe ODU detects that its power module fails.

Attribute


0x017F Major Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the ID of the power supply that reports the alarm. For example, 0x01indicates that the alarm is reported by the first group of power supply of the board.

Parameter 2 l 0x01: Indicates that the active power fails.

l 0x02: Indicates that the standby power fails.

Parameter 3 l 0x01: Indicates over-voltage.

l 0x02: Indicates under-voltage.

Impact on System

The ODU fails to work normally.

Possible Causes

The power module of the ODU is faulty.



9-129

Handling Procedure

Step 1 Replace the ODU that reports the POWER_ALM alarm.

----End

Related Information

None.

9.3.90 PPP_LCP_FAIL

Description

The PPP_LCP_FAIL is an alarm of LCP protocol negotiation failure. This alarm occurs whenthe encapsulation type of the local port is set to PPP, but the negotiation with the opposite portfails.

Attribute



Parameters

None.

None.

Impact on System

When the PPP_LCP_FAIL alarm occurs, the LCP negotiation fails and the services areinterrupted.

Possible Causes

The possible causes of the PPP_LCP_FAIL alarm are as follows:

l Cause 1: The configuration parameters of the port are inconsistent at the two ends.

l Cause 2: The network is baffled or of poor quality and The LCP protocol runs abnormally.

l Cause 3: the physical link is interrupted.

Handling Procedure

l Cause 1: The configuration parameters of the port are inconsistent at the two ends.1. On the T2000, check whether the configuration parameters of the opposite port are

consistent with that of the local port. For details, refer to Configuring Interfaces in theConfiguration Guide manual.


Maintenance Guide


Issue 02 (2009-06-30)

2. If not, modify the configuration to make it consistent at the two ends. Then, checkwhether the alarm is cleared.

l Cause 2: The network is baffled or of poor quality and The LCP protocol runs abnormally.1. On the T2000, check whether the bandwidth configured to the tunnel which connects

to the port is too low. For details, refer to Configuring an MPLS Tunnel in theConfiguration Guide manual.

2. If yes, re-configure the tunnel with a bigger bandwidth. Then, check whether the alarmis cleared.

l Cause 3: the physical link is interrupted.1. Check whether the physical link is normal.2. If not, modify the faulty physical link and check whether this alarm is cleared.

----End


9.3.91 PPP_NCP_FAIL

DescriptionThe PPP_NCP_FAIL is an alarm of NCP negotiation failure. When it is detected that a link withPPP encapsulation type is not added into the MP group, this alarm occurs.

Attribute



ParametersNone.

None.

Impact on SystemWhen the PPP_NCP_FAIL alarm occurs, the NCP negotiation fails and the services areinterrupted.

Possible CausesThe possible causes of the PPP_NCP_FAIL alarm are as follows:

l Cause 1: A link with PPP encapsulation type is not added into the MP group.

l Cause 2: The network is baffled or of poor quality and The NCP protocol runs abnormally.

l Cause 3: the physical link is interrupted.



9-131

Handling Procedurel Cause 1: A link with PPP encapsulation type is not added into the MP group.

1. On the T2000, check whether all links with PPP encapsulation type are added into theMP group. For details, refer to Configuring ML-PPP in the Configuration Guidemanual.

2. If not, add the link into the MP group. Then, check whether the alarm is cleared.l Cause 2: The network is baffled or of poor quality and The NCP protocol runs abnormally.

1. On the T2000, check whether the bandwidth configured to the tunnel which connectsto the port is too low. For details, refer to Configuring an MPLS Tunnel in theConfiguration Guide manual.

2. If yes, re-configure the tunnel with a bigger bandwidth. Then, check whether the alarmis cleared.

l Cause 3: the physical link is interrupted.1. Check whether the physical link is normal.2. If not, modify the faulty physical link and check whether this alarm is cleared.

----End


9.3.92 PW_DOWN

DescriptionThe PW_DOWN alarm indicates that the PW service connection is interrupted.

Attribute



Parameters

ID Name

Parameter 1 to Parameter 4 Indicate the index number of the faulty PW.

Parameter 5 to Parameter 8 Indicate the running state of the local end.

Parameter 9 to Parameter 12 Indicate the running state of the opposite end.

Impact on SystemIn the case of the PW_DOWN alarm, the services carried by the PW are already interrupted.


Maintenance Guide


Issue 02 (2009-06-30)

Possible CausesThe possible causes of the PW_DOWN alarm are as follows:

l Cause 1: The PW configuration at the local and remote ends is inconsistent.


l Cause 3: The tail fiber is not properly connected to the optical interface on the board.

l Cause 4: The optical module is faulty.


Handling Procedurel Cause 1: The PW configuration at the local and remote ends is inconsistent.

1. On the T2000, query the type of the service that the PW carries and check whetherthe PW configuration at the two NEs is consistent.

2. If not, modify the configuration so that the PW configuration at the two NEs isconsistent.

l Cause 2: The network is severely congested.1. On the T2000, check whether the bandwidth configured to the tunnel is too small.2. If yes, expand the bandwidth or eliminate the source where a large amount of illegal

data is transmitted. Then, check whether the alarm is cleared.l Cause 3: The tail fiber is not properly connected to the optical interface on the board.

1. Check whether the tail fibers are properly connected to the optical interfaces on theboards at the two NEs.

2. If not, properly re-connect the tail fibers.l Cause 4: The optical module is faulty.

1. On the T2000, check whether the NEs at the two ends report any alarm related to theoptical module, such as the LSR_WILL_DIE alarm. For details, refer to 8.2Querying Current Alarms of a Board.

2. If yes, replace the faulty optical module. For details, refer to 5.9 Replacing thePluggable Optical Module.

l Cause 5: The board is faulty.1. On the T2000, check whether the hardware-related alarms occur on the board of the

two NEs, such as the HARD_BAD alarm.2. If yes, cold-reset the board that reports the hardware-related alarm and check whether

the DOWN_E1_AIS alarm is cleared. For details, refer to 8.16 Resetting Boards.3. If the DOWN_E1_AIS alarm persists, replace the related board and check whether

the DOWN_E1_AIS alarm is cleared. For details, refer to 5 ReplacingComponents.

----End


9.3.93 R_LOC



9-133

Description

The R_LOC is an alarm indicating that clock signal is not detected at the receive end. This alarmis reported if the line board fails to extract clock signal from the line signal.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01indicates that the alarm is reported by port 1 of the related board.

Parameters 2–3 Indicate the path ID.

Impact on System

The service carried over the port is interrupted. If the system is configured with protection,protection switching may be triggered.

Possible Causesl The transmit unit of the remote site is faulty.

l The receive unit of the local site is faulty.

Handling Procedure

Step 1 Based on the alarm parameters, locate the line port that reports the alarm.

Step 2 Perform port inloop at the local end.

If... Then...

The alarm persists Replace the local board that reports the R_LOC alarm.

The alarm disappears Go to the next step.

Step 3 Replace the line board at the opposite site.


Maintenance Guide


Issue 02 (2009-06-30)

If... Then...

The alarm disappears after the board isreplaced


The alarm persists after the board isreplaced


Step 4 Replace the CXPR board at the opposite.

If... Then...

The CXPR board at the opposite end isconfigured with the 1+1 protection scheme

Refer to 5.1 Replacing the CXPR with the 1+1 Protection.

The CXPR board at the opposite end is notconfigured with the 1+1 protection scheme

Refer to 5.2 Replacing the CXPR Withoutthe 1+1 Protection.

----End


9.3.94 RADIO_FADING_MARGIN_INSUFF

DescriptionThe RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean received powerof the ODU is lower than the threshold of the received power (the threshold value is about thereceiver sensitivity + 14dB).

When the received power of the ODU in consecutive six hours is lower than the threshold, thesystem reports the alarm. When the mean received power of the ODU becomes normal in threeminutes after the alarm is reported, the alarm is cleared. The alarm is reported once every 24hours.

Attribute

Alarm Severity Alarm Type

Minor Equipment alarm


Name Meaning

Parameter 0 The value is always 0x01.



9-135

Name Meaning

Parameter 1, Parameter 2 The value is always 0xff 0xff.

Parameter 3, Parameter 4 The value is always 0xff 0xff.

Impact on System

If the MW_LOF or MW_FECUNCOR alarm is not generated, the service is not affected.

Possible Causesl The ODU fault of the transmit end causes the abnormal transmit power.

l The direction of the antenna is deflected.

l The transmission environment changes.

l The fade margin in the case of rain and fog in the network planning is insufficient.

Handling Procedure

Step 1 Use the NMS to check whether the power of the ODU at the transmit end is normal.

If ... Then ...

The transmit power is abnormal Rectify the fault according to the alarm at the transmit end.For how to rectify the fault, see TroubleshootingMicrowave Links.

The transmit power is normal Proceed to the next step.

Step 2 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 Proceed to the next step.

Step 3 Check whether the transmission environment changes. For example, check whether any buildingblocks the transmission, any large area of water surface such as a lake changes the link fadingsignificantly.

If ... Then ...

The transmission environment changes Contact the network planning department forre-planning the transmission trail.

The transmission environment does notchange

Proceed to the next step.

Step 4 If the alarm is reported frequently, contact the network planning department for increasing thefade margin by re-planning the transmission trail.

----End


Maintenance Guide


Issue 02 (2009-06-30)


9.3.95 RADIO_RSL_LOW

DescriptionThe RADIO_RSL_LOW is an alarm indicating that the radio receive power is too low. Thisalarm is reported if the detected receive power is equal to or below the lower threshold of theODU (–90 dBm).

Attribute


0x027E Critical Service alarm


Name Meaning

Parameter 1 Indicates the RF port that reports the alarm.

Impact on SystemIf there is neither the MW_LOF nor the MW_FECUNCOR alarm, the services are not affected.

Possible Causesl The microwave link signal is too much attenuated.

l The transmit power of the remote site is too low.

l The ODU of the local site is faulty.

Handling Procedure

Step 1 Check whether the transmit power of the remote site is normal.

If... Then...

No Replace the ODU of the remote site.


Step 2 Check whether the alarm occurs frequently.



9-137

If... Then...

The alarm occurs occasionally Contact the network planning department to change thedesign to increase the anti-fading performance.

The alarm occurs frequently Go to the next step.

Step 3 Check whether the antennas at both ends are properly adjusted.

If... Then...

No Adjust the antenna again.


Step 4 Check whether the polarization direction of the antenna, ODU, and hybrid coupler is correctlyset.

If... Then...

No Correct the polarization direction.


Step 5 Check whether the outdoor units such as antennas, combiner, ODU, and flexible waveguide arewet, damp, or damaged.

If... Then...

Yes Replace the unit that is wet, damp, or damaged.


Step 6 Check whether the antenna gain at both the transmit and receive sides meets the requirement.

If... Then...

No Replace the antenna.


Step 7 Check whether there is a mountain or building in the transmit direction.

If... Then...

Yes Contact the network planning department to change the design to avoid mountain orbuilding interference.


Step 8 Replace the ODU and the coupler at the local site in turn.

If... Then...

The RADIO_RSL_LOW alarm is cleared after the ODUand the coupler are replaced

The alarm handling is complete.

The RADIO_RSL_LOW alarm persists after the ODUand the coupler are replaced



Maintenance Guide


Issue 02 (2009-06-30)

Step 9 Replace the ODU and the coupler at the opposite site in turn.

----End

Related Information

None.

9.3.96 RADIO_RSL_HIGH

Description

The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is too high. Thisalarm is reported if the detected receive power is equal to or higher than the upper threshold ofthe ODU (–20 dBm).

Attribute


0x027D Critical Service alarm

Parameters


Name Meaning


Impact on System

The service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causesl The ODU is faulty.

l There is a strong interference source nearby.

Handling Procedure




9-139

If... Then...

The alarm disappears after the ODU isreplaced


The alarm persists after the ODU is replaced Go to the next step.

Step 2 Remove the nearby strong interference source.

----End

Related Information

None.

9.3.97 RADIO_TSL_LOW

Description

The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is too low. Thisalarm is reported if the detected transmit power is below the lower power threshold of the ODU.

Attribute


0x027B Critical Service alarm

Parameters


Name Meaning


Impact on System

The service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible Causes

The ODU is faulty.


Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedure


----End


9.3.98 RADIO_TSL_HIGH

DescriptionThe RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. Thisalarm is reported if the detected transmit power is higher than the upper power threshold of theODU.

Attribute


0x027C Critical Service alarm


Name Meaning


Impact on SystemThe service transmission is affected. If the system is configured with 1+1 protection, protectionswitching may be triggered.

Possible CausesThe ODU is faulty.

Handling Procedure


----End



9-141

Related Information

None.

9.3.99 RADIO_MUTE

Description

The RADIO_MUTE is an alarm indicating that radio transmitter is muted.

Attribute


0x027F Warning Equipment alarm

Parameters


Name Meaning


Impact on System

The transmitter does not launch services.

Possible Causesl The transmitter of the local site is muted.

l The data configuration of the ODU is incorrect.

l The IF board is faulty, causing abnormal IF output.

Handling Procedure

Step 1 Check whether the transmitter of the ODU is muted.

If... Then...

Yes Cancel the muting operation.


Step 2 Check whether there is an CONFIG_NOSUPPORT alarm.


Maintenance Guide


Issue 02 (2009-06-30)

If... Then...

Yes Handle the CONFIG_NOSUPPORT alarm.


Step 3 Replace the IF board.

----End


9.3.100 RELAY_ALARM_CRITICAL

DescriptionThe RELAY_ALARM_CRITICAL is an alarm of critical alarm inputs. This alarm occurs whenthe user sets the severity of an available alarm input to critical and there is such an alarm input.

Attribute




Name Meaning

Parameter 1 Indicates the number of the alarm input/output.

Range of parameter 1: 0x01 to 0x08.

Impact on Systeml When the RELAY_ALARM_CRITICAL alarm occurs, it does not affect the operation of

the board or the services on the NE.l This alarm is a non-root alarm. When there is no other critical alarm on the equipment, this

alarm will be cleared automatically.

Possible CausesThe cause of the RELAY_ALARM_CRITICAL alarm is as follows:

There is a critical alarm input.



9-143

Handling Procedurel Cause: There is a critical alarm input.

1. Check the alarm parameters and confirm the number of the alarm input/output.2. Rectify the fault of the equipment to stop the alarm input, and then check whether the

RELAY_ALARM_CRITICAL alarm is cleared.

----End


9.3.101 RELAY_ALARM_MAJOR

DescriptionThe RELAY_ALARM_MAJOR is an alarm of major alarm inputs. This alarm occurs when theuser sets the severity of an alarm input to major and there is such an alarm input.

Attribute




Name Meaning



Impact on Systeml When the RELAY_ALARM_MAJOR alarm occurs, it does not affect the operation of the

board or the services on the NE.l This alarm is a non-root alarm. When there is no other major alarm on the equipment, this

alarm will be cleared automatically.

Possible CausesThe cause of the RELAY_ALARM_MAJOR alarm is as follows:


Maintenance Guide


Issue 02 (2009-06-30)

There is a major alarm input.

Handling Procedure

l Cause: There is a major alarm input.

1. Check the alarm parameters and confirm the number of the alarm input/output.

2. Rectify the fault of the equipment to stop the alarm input, and then check whether theRELAY_ALARM_MAJOR alarm is cleared.

----End

Related Information

None.

9.3.102 RELAY_ALARM_MINOR

Description

The RELAY_ALARM_MINOR is an alarm of minor alarm inputs. This alarm occurs when theuser sets the severity of an available alarm input to minor and there is such an alarm input.

Attribute



Parameters


Name Meaning



Impact on Systeml When the RELAY_ALARM_MINOR alarm occurs, it does not affect the operation of the

board or the services on the NE.

l This alarm is a non-root alarm. When there is no other minor alarm on the equipment, thisalarm will be cleared automatically.



9-145

Possible Causes

The cause of the RELAY_ALARM_MINOR alarm is as follows:

There is a minor alarm input.

Handling Procedure

l Cause: There is a minor alarm input.1. Check the alarm parameters and confirm the number of the alarm input/output.2. Rectify the fault of the equipment to stop the alarm input, and then check whether the

RELAY_ALARM_MINOR alarm is cleared.

----End

Related Information

None.

9.3.103 RELAY_ALARM_IGNORE

Description

The RELAY_ALARM_IGNORE is an alarm of warning alarm inputs. This alarm occurs whenthe user sets the severity of an available alarm input to warning and there is such an alarm input.

Attribute


0x3014 Warning Equipment alarm

Parameters


Name Meaning



Impact on Systeml When the RELAY_ALARM_IGNORE alarm occurs, it does not affect the operation of the

board or the services on the NE.


Maintenance Guide


Issue 02 (2009-06-30)

l This alarm is a non-root alarm. When there is no other warning alarm on the equipment,this alarm will be cleared automatically.

Possible CausesThe cause of the RELAY_ALARM_IGNORE alarm is as follows:

There is a warning alarm input.

Handling Procedurel Cause: There is a warning alarm input.

1. Check the alarm parameters and confirm the number of the alarm input/output.2. Rectify the fault of the equipment to stop the alarm input, and then check whether the

RELAY_ALARM_IGNORE alarm is cleared.

----End


9.3.104 RPS_INDI

DescriptionThe RPS_INDI is an alarm indicating that the microwave protection switching is detected.

Attribute




Name Meaning

Parameter 1 Indicates the ID of the protection group, and defaults as 0x01.

Parameter 2 Indicates the type of protection switching.

0x01 indicates HSB protection switching.

0x02 indicates HSM protection switching.



9-147

Impact on System

During the HSB protection switching, services are interrupted. After the HSB protectionswitching is complete, the services become normal.

During the HSM protection switching, no bit errors are generated, and services are not affected.

Possible Causesl The possible causes of the HSB protection switching are as follows:

– 1. The external switching triggered by the switching command that is issued by theNMS software, occurs.

– 2. The automatic switching triggered by equipment failure or a service defect, occurs.

– 3. The reverse switching occurs. When the reserve switching of the HSB protectiongroup is enabled, the HSB protection switching occurs if both the protection and theworking IF boards report the MW_RDI alarm.

l The possible cause of the HSM protection switching is as follows: The working pathdegrades.

Handling Procedure

l Determine the type of the protection switching based on the alarm parameters.

l Cause 1 of HSB switching: External switching occurs. That is, NMS issues a command totrigger the switching.Follow the steps:

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

2. The IF 1+1 protection group dialog box is displayed. Choose Configuration > IF 1+1 Protection from the Function Tree.

3. Click Query. Query Equipment Switching Status in Protection Group.If Equipment Switching Status in Protection Group is set to Forced switching orManual switching, the NMS issues a command to perform external switching.

4. Identify the cause of the forced switching, and clear the external switchingimmediately.In Slot Mapping Relation, select the working unit or the protection unitof a protection group. Right-click and choose Clear switching from the shortcut menu.Click OK in the displayed dialog box.

l Cause 2 of HSB switching: Automatic switching occurs. That is, the equipment is faulty,or the service is defective.Follow the steps:

1. Check whether any of the following faults or alarms occur. If any of the followingfaults or alarms occur, rectify the faults or clear the alarms.

– The IF board hardware is faulty, or the ODU hardware is faulty, focus on the alarmssuch as HARD_BAD and TEMP_ALARM.

– POWER_ALM, VOLT_LOS (IF board)

– RADIO_TSL_HIGH, RADIO_TSL_LOW or RADIO_RSL_HIGH

– IF_INPWR_ABN or CONFIG_NOSUPPORT

– R_LOC or MW_LOF


Maintenance Guide


Issue 02 (2009-06-30)

NOTE

l If the switching is non-revertive, the services are not automatically switched to the workingpath when the working path is restored to normal, and the RPS_INDI alarm persists. In thiscase, you need to manually switch the services from the protection path to the workingpath. The RPS_INDI alarm is cleared only when the switching is successful.

l If the switching is revertive, the services are automatically switched to the working pathonly when the specified wait-to-restore (WTR) time expires after the working path isrestored to normal. The RPS_INDI alarm is cleared only when the switching is successful.

l Cause 3 of HSB switching: Reverse switching occurs. If the reverse switching function ofthe HSB protection group is enabled, the switching is triggered when the MW_RDI alarmis reported by the working and protection IF boards.For the handling procedure, see MW_RDI.

l Switching cause of the HSM: The working path degrades. This symptom is normal withoutany impact on services. Hence, no measure is required to handle the symptom.

----End

Related Information

None.

9.3.105 S1_SYN_CHANGE

Description

The S1_SYN_CHANGE is an alarm indicating the switching of the clock source in the S1 bytemode. This alarm occurs when, in the SSM mode, the traced clock source is switched.

Attribute


0x00C1 Major Equipment alarm

Parameters


Name Meaning

Parameter 1 Indicates the type of the switched clock source.

l 0x01: System clock.

l 0x02: First 2M clock.

l 0x03: Second 2M clock.



9-149

Impact on System

When the S1_SYN_CHANGE alarm occurs, if the new clock source has a lower quality, pointerjustifications and bit errors are generated. As a result, the quality of services is affected.

Possible Causes

The possible causes of the S1_SYN_CHANGE alarm are as follows:

l Cause 1: The external BITS clock is lost.

l Cause 2: The service signals are lost.

l Cause 3: The S1_SYN_CHANGE alarm is generated at the upstream NE.

Handling Procedure

l Cause 1: The external BITS clock is lost.


2. If yes, clear the EXT_SYNC_LOS alarm and then check whether this alarm is cleared.

l Cause 2: The service signals are lost.

1. On the T2000, check whether the ETH_LOS or T_ALOS alarm occurs.

2. If yes, clear the ETH_LOS or T_ALOS alarm first and then check whether this alarmis cleared.

l Cause 3: The S1_SYN_CHANGE alarm is generated at the upstream NE.

1. On the T2000, check whether the S1_SYN_CHANGE alarm occurs at the upstreamNE.

2. If yes, clear the S1_SYN_CHANGE alarm occurs at the upstream NE first and checkwhether the S1_SYN_CHANGE alarm at the local NE is cleared.

----End

Related Information

None.

9.3.106 SECU_ALM

Description

The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.

Attribute


0x00C8 Major Equipment alarm


Maintenance Guide


Issue 02 (2009-06-30)


Name Meaning

Parameter 1 Indicates the type of the login terminal.

Parameter 2, Parameter 3 Indicates the login errors.

Parameter 4, Parameter 5 Indicates the first two characters of the user name that is lockedafter the login verification fails.

Impact on Systeml After the password is incorrectly entered for three consecutive times, the user account is

temporarily locked. Two minutes later, the user account can be used for another login.l The alarm ends immediately after it is reported.

Possible CausesThe cause of the alarm is as follows:

An illegal user fails to log in to the NE.

Handling Procedurel Cause: An illegal user fails to log in to the NE.

1. Query the NE security log to check the user name that is used for the login. For details,refer to 8.1 Querying T2000 Operation Logs.

2. Log in to the NE with a correct user name.

----End

Related InformationAfter the login password are incorrectly entered for three consecutive times, the networkmanagement system automatically locks the screen. Only the administrator can unlock thescreen.

9.3.107 SWDL_ACTIVATED_TIMEOUT

DescriptionThe SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of thesoftware package. This alarm occurs when the NE does not perform the commit operation acertain time later after the board software is activated during the software package loading.



9-151

Attribute


0x23d Critical Processing alarm

Parameters

None.

None.

Impact on System

When the SWDL_ACTIVATED_TIMEOUT alarm occurs, the software in the two areas of thedouble-area boards on the NE is inconsistent. If any board becomes abnormal, rollback.

Possible Causes

The cause of the SWDL_ACTIVATED_TIMEOUT alarm is as follows:

The NE does not perform the commit operation 30 minutes later after the software is activated.

Handling Procedure

l Cause: The NE does not perform the commit operation in 30 minutes later after the softwareis activated.1. Check whether the software package loading is complete.2. If yes, continue the commit operation of the software package loading. Then the alarm

is cleared automatically.

----End

Related Information

None.

9.3.108 SWDL_AUTOMATCH_INH

Description

The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function isdisabled.

Attribute


0x0a0e Minor Processing alarm


Maintenance Guide


Issue 02 (2009-06-30)

Parameters

None.

None.

Impact on System

When the SWDL_AUTOMATCH_INH alarm occurs, the alarmed board cannot automaticallymatch the software from the CXPR board. Thus, the consistency of the software version on theentire NE is affected and some functions of the NE may operate abnormally.

Possible Causes

The cause of the SWDL_AUTOMATCH_INH alarm is as follows:

The automatic match function is disabled.

Handling Procedure

l Cause: The automatic match function is disabled.

1. Issue the order to enable the automatic switch function, and then check whether thealarm is cleared.

----End

Related Information

None.

9.3.109 SWDL_COMMIT_FAIL

Description

The SWDL_COMMIT_FAIL is an alarm indicating that the NE fails to commit the software.This alarm occurs when the NE fails to commit the software for certain boards during thesoftware package loading.

Attribute


0x0a0b Minor Processing alarm

Parameters

None.

None.



9-153

Impact on SystemWhen the SWDL_COMMIT_FAIL alarm occurs, the software versions of the two file systemson the system control board are inconsistent.

Possible CausesThe possible causes of the SWDL_COMMIT_FAIL alarm are as follows:

l Cause 1: The commit operation on the NE fails for certain boards.

l Cause 2: The system control board is faulty.

Handling Procedurel Cause 1: The commit operation on the NE fails for certain boards.

1. Check whether the software currently running on the system control board is consistentwith the software to be loaded. For details, refer to 8.3 Querying the BoardInformation Report.

2. If the software currently running on the system control board is inconsistent with thesoftware to be loaded, restart the software package loading. After the software packageloading is successful, the alarm is cleared automatically. For details, refer to 6Software Package Upgrade and Package Diffusion.

l Cause 2: The system control board is faulty.1. Check whether the hardware alarms such as the HARD_BAD alarm occur on the

system control board. For details, refer to 8.2 Querying Current Alarms of aBoard.

2. If yes, replace the system control board, and then check whether theSWDL_COMMIT_FAIL alarm are cleared. For details, refer to 5 ReplacingComponents.

----End


9.3.110 SWDL_INPROCESS

DescriptionThe SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.

Attribute


0x0a0c Minor Processing alarm

ParametersNone.


Maintenance Guide


Issue 02 (2009-06-30)

None.

Impact on SystemWhen the SWDL_INPROCESS alarm occurs, the NE is loading the software package. Theoperations, including modifying configurations, uploading/downloading files, and backing upthe database, are prohibited.

Possible CausesThe cause of the SWDL_INPROCESS alarm is as follows:

The NE is loading the software package.

Handling Procedurel Cause: The NE is loading the software package.

1. Wait until the software package loading is complete, and check whether the alarm iscleared.

----End


9.3.111 SWDL_NEPKGCHECK

DescriptionThe SWDL_NEPKGCHECK is an alarm indicating that when a file in the software package islost or fails to pass the check, the file cannot be modified. When a file in the software packageis lost or fails to pass the check, the system will modify the file from the other normal files. Ifthe modification fails, the SWDL_NEPKGCHECK occurs.

Attribute


0x023e Critical Processing alarm

ParametersNone.

None.

Impact on Systeml When the alarm occurs, the operations of the package loading of the NE cannot be complete.

l When the file is complete and passes the check, the alarm will be cleared automatically.



9-155

Possible CausesThe cause of the SWDL_NEPKGCHECK alarm is as follows:

The file type mismatches or a file is lost.

Handling Procedurel Cause: The file type mismatches or a file is lost.

1. Check whether the file type matches, and whether a file is lost. If file mismatch or fieloss occurs, download the mapping software again.

2. Perform the software package loading again, and update the software package. Thencheck whether the alarm is cleared. For details, refer to 6.1.4 Creating a PackageUpgrade Task.

----End


9.3.112 SWDL_PKG_NOBDSOFT

DescriptionThe SWDL_PKG_NOBDSOFT is an alarm indicating that the files of some boards are not inthe software package for loading and the board matching fails.

Attribute


0x0a09 Minor Processing alarm

ParametersNone.

None.

Impact on SystemAs the software of the board is not contained in the software package, the board cannot performautomatic match. As a result, the software version of the board is inconsistent with that of theNE. Some functions may operate abnormally.

Possible CausesThe cause of the SWDL_PKG_NOBDSOFT alarm is as follows:

The files of some boards are not in the customized software package.


Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedurel Cause: The files of some boards are not in the customized software package.

1. Re-download an integrate software package and perform the software package loadingfor a second time. When the software package loading is complete, theSWDL_PKG_NOBDSOFT alarm is cleared automatically. For details, refer to 6Software Package Upgrade and Package Diffusion.

----End


9.3.113 SWDL_PKGVER_MM

DescriptionThe SWDL_PKGVER_MM is an alarm indicating that the consistency check of the softwarepackage version fails.

Attribute


0x0a0d Minor Processing alarm

ParametersNone.

None.

Impact on SystemIf the software versions on the NE are inconsistent, some functions of the NE may operateabnormally.

Possible CausesThe cause of the SWDL_PKGVER_MM alarm is as follows:

The version information in the description file of the software package is inconsistent with theactual version information.

Handling Procedurel Cause: The version information in the description file of the software package is

inconsistent with the actual version information.1. Re-download an correct software package and perform the software package loading

for a second time. When the software package loading is complete, the



9-157

SWDL_PKGVER_MM alarm is cleared automatically. For details, refer to 6Software Package Upgrade and Package Diffusion.

----End


9.3.114 SWDL_ROLLBACK_FAIL

DescriptionThe SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback fails for certain boardsduring the software package loading.

Attribute


0x0a0a Minor Processing alarm

ParametersNone.

None.

Impact on SystemWhen the SWDL_ROLLBACK_FAIL alarm occurs, The failed boards may have the softwareinconsistent with the NE software. Hence, some functions of the failed boards may be affected.

Possible CausesThe possible cause of the SWDL_ROLLBACK_FAIL alarm is as follows:

Rollback of certain boards fails during rollback of the entire NE.

Handling Procedurel Cause: Rollback of certain boards fails during rollback of the entire NE.

1. Check whether there is MSSW_DIFFERENT alarm. For details, refer to 8.2 QueryingCurrent Alarms of a Board.If yes, clear the alarm first.

2. Restart the software package loading. After the software package loading issuccessful, the alarm is cleared automatically. For details, refer to 6 Software PackageUpgrade and Package Diffusion.

----End



Maintenance Guide


Issue 02 (2009-06-30)

9.3.115 SYN_BAD

Description

The SYN_BAD is an alarm indicating that the synchronization clock source is degraded. Thisalarm occurs when the synchronization clock source traced by the equipment is degraded.

Attribute



Parameters

None.

None.

Impact on System

If the clock source is degraded, tracing it may cause bit errors to the services.

Possible Causes

The possible causes of the SYN_BAD alarm are as follows:

l Cause 1: The quality of the traced clock source is degraded.

l Cause 2: The board that reports the SYN_BAD alarm has a hardware failure.

Handling Procedure

l Cause 1: The quality of the traced clock source is degraded.1. Replace the current clock source with a normal one and check whether the SYN_BAD

alarm is cleared. For details, refer to Configuring the NE Clock Source in the OptiXRTN 950 Radio Transmission System Configuration Guide manual.

2. If the SYN_BAD alarm persists, check whether the input clock is correctly configured.If not, modify the configuration and check whether the SYN_BAD alarm is cleared.

l Cause 2: The board that reports the SYN_BAD alarm has a hardware failure.1. On the T2000, check whether there is the HARD_BAD or TEMP_OVER alarm

indicating the hardware is faulty.2. If yes, clear these alarms first and check whether the SYN_BAD alarm is cleared.

----End

Related Information

None.



9-159

9.3.116 SYNC_C_LOS

Description

The SYNC_C_LOS is an alarm indicating the loss of synchronization source level. This alarmoccurs when the clock source of a service board is lost in the priority table.

Attribute


0x006F Warning Equipment alarm

Parameters

None.

None.

Impact on System

When the SYNC_C_LOS alarm occurs, the relevant clock source is lost and cannot be tracedby the equipment. The services are slightly degraded.

Possible Causes

The possible causes of the SYNC_C_LOS alarm are as follows:

l Cause 1: The external clock is lost.

l Cause 2: The input service signals related to the clock source are lost.

Handling Procedure

l Cause 1: The external clock is lost.


2. If yes, clear the EXT_SYNC_LOS alarm and then check whether the SYNC_C_LOSalarm is cleared.

l Cause 2: The input service signals related to the clock source are lost.

1. On the T2000, check whether the T_ALOS or ETH_LOS alarm occurs whichindicates the input service signals are lost. For details, refer to 8.2 Querying CurrentAlarms of a Board.

2. If yes, clear the alarm indicating the loss of service signals fist, and then check whetherthe SYNC_C_LOS alarm is cleared.

----End


Maintenance Guide


Issue 02 (2009-06-30)

Related Information

9.3.117 SYNC_DISABLE

Description

The SYNC_DISABLE is an alarm indicating that the automatic synchronization function of thesystem control board is disabled. When the automatic synchronization function of the systemcontrol board is disabled, the SYNC_DISABLE alarm occurs.

Attribute


0x31F8 Minor Processing alarm

Parameters

None.

None.

Impact on Systeml When the SYNC_DISABLE alarm occurs, the batch backup cannot be initiated. Thus, the

data of the working and protection boards is inconsistent.

l When the automatic synchronization function of the system control board is enabled, thealarm is cleared automatically.

Possible Causes

The cause of the SYNC_DISABLE alarm is as follows:

The automatic synchronization function of the system control board is disabled.

Handling Procedure

l Cause: The automatic synchronization function of the system control board is disabled.

1. Issue an order to set the automatic synchronization state of the system control boardto enabled, and then check whether the alarm is cleared.

2. If the SYNC_DISABLE alarm persists, replace the board that reports the alarm. Fordetail, refer to 5 Replacing Components.

----End

Related Information

None.



9-161

9.3.118 SYNC_F_M_SWITCH

Description

The SYNC_F_M_SWITCH is an alarm indicating that the clock source is switched in a manualor forced manner.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the slot ID.


0xFF: No sub-board.

Parameter 3, Parameter 4 Indicates the port ID.

l Parameter 1=0x00, Parameter 2=0xf0, Parameter 3=0x00,Parameter 4=0x01: First external clock source.

l Parameter 1=0x00, Parameter 2=0xf0, Parameter 3=0x00,Parameter 4=0x02: Second external clock source.

l Parameter 1=0x00, Parameter 2=0xf1, Parameter 3=0x00,Parameter 4=0x01: Internal clock source.

Impact on System

When the SYNC_F_M_SWITCH alarm occurs, the NE clock works in the forced or manualswitching state. This alarm does not affect services.

Possible Causes

The cause of the SYNC_F_M_SWITCH alarm is as follows:

The NE issues the command of manual or forced switching to the clock source.


Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedure

l Cause: The NE issues the command of manual or forced switching to the clock source.

1. Check the alarm parameters to confirm the relevant clock source.

2. Referring to the actual scene, remove the manual or forced switching from the relevantclock source, and then check whether the alarm is cleared. For details, refer to theOptiX iManager T2000 Online Help.

----End

Related Information

None.

9.3.119 SYNC_FAIL

Description

The SYNC_FAIL is an alarm indicating that the backup of the databases on the active andstandby system control boards fails.

Attribute


0x24f Minor Processing alarm

Parameters

None.

None.

Impact on System

When the SYNC_FAIL alarm occurs, the data on the working CXPR and protection CXPRcannot be synchronized. When the CXPR 1+1 protection switching is performed, the systemmay run in an abnormal state as the data is lost or conflicts.

Possible Causes

The possible causes of the SYNC_FAIL alarm are as follows:

l Cause 1: The databases of the active and standby system control boards are damaged duringthe batch backup of the databases.

l Cause 2: The communication between the active and standby system control boards isinterrupted during the batch backup of the databases.

l Cause 3: The software versions of the active and standby system control boards areinconsistent.



9-163

Handling Procedurel Cause 1: The databases of the active and standby system control boards are damaged during

the batch backup of the databases.1. Check whether the DBMS_ERROR alarm occurs on the NE. For details, refer to 8.2

Querying Current Alarms of a Board.2. If yes, clear the DBMS_ERROR alarm first, and then check whether the SYNC_FAIL

alarm is cleared.l Cause 2: The communication between the active and standby system control boards are

interrupted during the batch backup of the databases.1. Check whether the COMMUN_FAIL alarm occurs on the NE.2. If yes, clear the COMMUN_FAIL alarm first, and then the NE restarts the batch

backup automatically.l Cause 3: The software versions of the active and standby system control boards are

inconsistent.1. On the T2000, query and record the software versions of the active and standby system

control boards. Then, check whether the software versions are consistent. For details,refer to 8.3 Querying the Board Information Report.

2. If the software versions are inconsistent, determine the correct software versionsaccording to the version mapping table. Then, replace the system control board withthe incorrect software. For details, refer to 5 Replacing Components.

----End


9.3.120 SYNC_LOCKOFF

DescriptionThe SYNC_LOCKOFF is an alarm indicating that the clock source is locked out.

Attribute



ParametersNone.

None.

Impact on Systeml When the SYNC_LOCKOFF alarm occurs, the relevant clock source is locked and cannot

be traced by the NE.


Maintenance Guide


Issue 02 (2009-06-30)

l This alarm does not affect services.

Possible CausesThe cause of the SYNC_LOCKOFF alarm is as follows:

A specific clock source is locked out.

Handling Procedurel Cause: A specific clock source is locked out.

1. On the T2000, confirm the locked clock source. For details, refer to Switching a ClockSource in the OptiX RTN 950 Radio Transmission System Configuration Guidemanual.

2. Unlock the clock source and then check whether the alarm is cleared.

----End


9.3.121 SYSLOG_COMM_FAIL

DescriptionThe SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NEand the SYSLOG server fails. This alarm occurs when the NE and the SYSLOG server have anabnormal connection or session in the TCP mode.

Attribute


0x312A Major Equipment alarm


Name Meaning

Parameters 1-4 Indicates the IP address of the SYSLOG server.

Parameter 5 l 0x01: The connection is interrupted.

l 0x02: The session is abnormal.



9-165

Impact on SystemWhen the SYSLOG_COMM_FAIL alarm occurs, the SYSLOG information of the NE cannotbe sent to the SYSLOG server.

Possible CausesThe possible causes of the SYSLOG_COMM_FAIL alarm are as follows:

l Cause 1: The connection between the NE and the SYSLOG server is interrupted.

l Cause 2: In the DCN communication mode, the gateway NE in not configured.

Handling Procedurel Cause 1: The connection between the NE and the SYSLOG server is interrupted.

1. Check whether the connection between the NE and the SYSLOG server is interrupted.2. If interrupted, modify the physical connection to recover the good connection. Then,

check whether the alarm is cleared.l Cause 2: In the DCN communication mode, the gateway NE in not configured.

1. On the T2000, check whether the gateway NE is configured.

NOTE

In the DCN communication mode, the logs of the NE that does not directly connect to theSYSLOG servers must be transmitted to a gateway NE that directly communicates with theSYSLOG servers through DCN.

2. If not, configure a proper gateway NE, and check whether the alarm is cleared.

----End


9.3.122 T_ALOS

DescriptionThe T_ALOS alarm indicates loss of signals at the E1 port. When an E1 port does not accessany service, the T_ALOS alarm is reported.

Attribute


0x6B Major Communication alarm

ParametersNone.

None.


Maintenance Guide


Issue 02 (2009-06-30)

Impact on System

In the case of the T_ALOS alarm, the service is interrupted.

Possible Causes

The possible causes of the T_ALOS alarm are as follows:

l Cause 1: No E1 service is transmitted from the opposite port.

l Cause 2: The E1 cable is loosened or disconnected from the port.

l Cause 3: The opposite equipment is faulty.

l Cause 4: The cable is faulty.

l Cause 5: The interface board that reports the T_ALOS alarm is faulty.

Handling Procedure

l Cause 1: No E1 service is transmitted from the opposite port.

1. Check whether the E1 service is transmitted from the opposite port normally.

2. If not, recover the normal E1 service transmission from the opposite port.

l Cause 2: The E1 cable is loosened or disconnected from the port.

1. Check whether the E1 cable is loosened or disconnected from the port.

2. If yes, properly re-insert the E1 cable. Make sure that the E1 cable is in good contactwith the port.

l Cause 3: The opposite equipment is faulty.

1. On the ODF, perform self-loop (hardware inloop) on the channel with the T_ALOSalarm.

2. If the T_ALOS alarm ends, it indicates that the opposite equipment is faulty. Takepriority to rectify the fault of the opposite equipment.

l Cause 4: The cable is faulty.

1. If the T_ALOS alarm ends after the self-loop, perform self-loop (hardware inloop) onthe channel with the T_ALOS alarm at the interface board.

2. If the T_ALOS alarm ends, it indicates that the E1 cable is faulty. In this case, replacethe E1 cable.

l Cause 5: The interface board that reports the T_ALOS alarm is faulty.

1. If the T_ALOS alarm ends after the self-loop, perform inloop on the channel with theT_ALOS alarm on the T2000. For details, refer to 8.9 Configuring PortLoopback.

2. If the T_ALOS alarm ends, it indicates that the interface board is faulty. In this case,replace the interface board. For details, refer to 5 Replacing Components.

----End

Related Information

None.



9-167

9.3.123 TEM_HA

Description

The TEM_HA is an alarm indicating that the temperature of the laser is excessively high.

Attribute


0x01d Major Equipment alarm

Parameters

None.

None.

Impact on System

If the TEM_HA alarm is not cleared for a long time, the laser may be faulty. Consequently, theservices are interrupted.

Possible Causes

The possible causes of the TEM_HA alarm are as follows:

l Cause 1: The working environment temperature is excessively high.


Handling Procedure

l Cause 1: The working environment temperature is excessively high.1. Check whether the environment temperature is higher than 60 centigrade.2. If yes, cool the environment temperature down to the range of -20 to 60 centigrade

and then check whether the TEM_HA alarm is cleared.l Cause 2: The optical module is faulty.

1. Replace the optical module on the port that reports the TEM_HA alarm, and thencheck whether the alarm is cleared. For details, refer to 5.9 Replacing the PluggableOptical Module.

2. If the TEM_HA alarm persists, replace the board that reports the alarm. For details,refer to 5 Replacing Components.

----End

Related Information

None.


Maintenance Guide


Issue 02 (2009-06-30)

9.3.124 TEM_LA

Description

The TEM_LA is an alarm indicating that the temperature of the laser is excessively low.

Attribute


0x01e Major Equipment alarm

Parameters

None.

None.

Impact on System

If the TEM_LA alarm is not cleared for a long time, the laser may be faulty. Consequently, theservices are interrupted.

Possible Causes

The possible causes of the TEM_LA alarm are as follows:

l Cause 1: The working environment temperature is excessively low.


Handling Procedure

l Cause 1: The working environment temperature is excessively low.1. Check whether the environment temperature is lower than -20 centigrade.2. If yes, warm the environment temperature up to the range of -20 to 60 centigrade and

then check whether the TEM_LA alarm is cleared.l Cause 2: The optical module is faulty.

1. Replace the optical module on the port that reports the TEM_LA alarm, and then checkwhether the alarm is cleared. For details, refer to 5.9 Replacing the Pluggable OpticalModule.

2. If the TEM_LA alarm persists, replace the board that reports the alarm. For details,refer to 5 Replacing Components.

----End

Related Information

None.



9-169

9.3.125 TEMP_ALARM

DescriptionThe TEMP_ALARM is an alarm indicating that the temperature crosses the threshold.

Attribute


0x00A6 Minor Environment alarm


Name Meaning

Parameter 1 l 0x01: Indicates that the temperature crosses the upper threshold.

l 0x02: Indicates that the temperature crosses the lower threshold.

Impact on SystemThe board fails to work normally.

Possible Causesl The board temperature crosses the threshold.

l The temperature detecting circuit is faulty.

Handling Procedure

Step 1 If the alarm is reported by the ODU, install a sunshade to control the temperature.

Step 2 If the alarm is reported by a board of the IDU, check whether the temperature control devices,such as air-conditioners, operate normally.

If... Then...

No Adjust the temperature control devices.


Step 3 If the ambient temperature is normal and there is no heat-sinking problem, replace the board thatreported the TEMP_ALARM.

----End


Maintenance Guide


Issue 02 (2009-06-30)


9.3.126 TEMP_OVER

DescriptionThe TEMP_OVER alarm indicates that the board working temperature reaches the threshold.When the system detects that the working temperature of the board reaches the lower or upperthreshold, the TEMP_OVER alarm is reported.

Attribute


0x1C Major Equipment alarm


Name Meaning

Parameter 1 Indicates the threshold-crossing type of the board working temperature.

l 0x01: The board working temperature is higher than the upper threshold.

l 0x02: The board working temperature is lower than the lower threshold.

Impact on Systeml Excessive (high or low) working temperature brings high risk for the system. If the system

operates with high risk for a long time, bit errors may occur and the services may beinterrupted. Hence, remove the risk in a timely manner.

l To avoid alarm jitter, the TEMP_OVER alarm is cleared only when the workingtemperature rises to 5°C higher than the lower threshold or drops to 5°C lower than theupper threshold.

Possible CausesThe possible causes of the TEMP_OVER alarm are as follows:

l Cause 1: The cooling or warming device is faulty and thus the working temperature isexcessively high or low.

l Cause 2: The upper and lower thresholds of the alarm are improperly set.

l Cause 3: The fan stops rotating .



9-171


Handling Procedurel Cause 1: The cooling or warming device is faulty and thus the working temperature is

excessively high or low.1. Check whether the environment temperature in the equipment room is higher than

60 centigrade or lower than -20 centigrade.2. If yes, check whether the cooling or warming device functions normally. If not, take

priority to rectify the fault of the cooling or warming device.l Cause 2: The upper and lower thresholds of the alarm are improperly set.

1. Check whether the current working temperature, upper and lower temperaturethresholds for the board are proper. For details, refer to 2.2.4 Browsing the CurrentPerformance Events in the Routine Maintenance.

2. If the upper and lower temperature thresholds are set improperly, re-set the upper andlower temperature thresholds.

l Cause 3: The fan stops rotating .1. Check whether the FAN_FAIL occurs. If yes, take priority to handle the

FAN_FAIL alarm.l Cause 4: The board is faulty.

1. Check whether the any hardware-related alarm occurs on the board that reports theTEMP_OVER alarm, such as the HARD_BAD alarm.

2. If yes, replace the board. For details, refer to 5 Replacing Components.

----End


9.3.127 THUNDERALM

DescriptionThe THUNDERALM is an alarm indicating the lightning protection failure. If the system detectsthe lightning protection circuit fails, the THUNDERALM occurs.

Attribute


0xF893 Minor Environment alarm

ParametersNone.

None.


Maintenance Guide


Issue 02 (2009-06-30)

Impact on System

When the THUNDERALM occurs, the system operation and services are not affected, but thelightning protection function fails.

Possible Causes

The possible causes of the THUNDERALM alarm are as follows:

l Cause 1: The fuse tube of the lightning protection circuit is interrupted.


Handling Procedure

l Cause 1: The fuse tube of the lightning protection circuit is interrupted.

1. Replace the fuse tube, and then check whether the alarm is cleared.


1. Replace the board that reports the THUNDERALM alarm. For details, refer to 5Replacing Components.

----End

Related Information

None.

9.3.128 TR_LOC

Description

The TR_LOC is an alarm indicating that the clock of the CXPR board is faulty. This alarm occurswhen a board detects that the clock of the CXPR board is lost, the frame header is lost, or theCXPR board is faulty.

Attribute


0x000E Major Equipment alarm

Parameters




9-173

Name Meaning

Parameter 1 Indicates the board ID from which the lost clock is transmitted.

l 0x01: CXPR board with the small slot number.

l 0x02: CXPR board with the big slot number.

l 0x03: The two CXPR boards.

Parameter 2 Indicates the detailed fault information.

l 0x01: Clock of the CXPR board with the small slot number is lost.

l 0x02: Frame header of the CXPR board with the small slot number is lost.

l 0x04: Bus indicating the status of the CXPR board with the small slot numberis faulty.

l 0x08: Clock of the CXPR board with the big slot number is lost.

l 0x10: Frame header of the CXPR board with the big slot number is lost.

l 0x20: Bus indicating the status of the CXPR board with the big slot numberis faulty.

Impact on SystemWhen the TR_LOC occurs, the board fails to work normally.

l If the protection CXPR board is detected to be faulty, the services are not affected.

l If the working CXPR board is detected to be faulty, the services are switched and someservices are transiently interrupted.

Possible CausesThe possible causes of the TR_LOC alarm are as follows:

l Cause 1: The clock line of the CXPR board is faulty.

l Cause 2: The board that reports the TR_LOC alarm is faulty.

Handling Procedurel Cause: The board is faulty.

1. On the T2000, check whether the alarm occurs on most service boards. For details,refer to 8.2 Querying Current Alarms of a Board.

2. If yes, the CXPR board is faulty. In this case, replace the faulty CXPR board and checkwhether the alarm is cleared. For details, refer to 5 Replacing Components.

3. If only the one board reports the alarm, replace it. Then, check whether the alarm iscleared.

----End



Maintenance Guide


Issue 02 (2009-06-30)

9.3.129 UP_E1_AIS

Description

The UP_E1_AIS is an alarm indicating the generation of an alarm in the upstream 2 Mbit/ssignals. This alarm occurs when the upstream E1 signals are detected to be all "1"s.

Attribute



Parameters

None.

None.

Impact on Systeml In the case of the UP_E1_AIS alarm, the E1 signals are unavailable and the service is

interrupted.l The UP_E1_AIS alarm will be suppressed when the T_ALOS alarms occurs.

l When the UP_E1_AIS alarm occurs, the system suppresses the LFA, LMFA andALM_IMA_LIF alarms.

Possible Causes

The possible causes of the UP_E1_AIS alarm are as follows:

l Cause 1: The T_ALOS alarm occurs on the opposite NE.

l Cause 2: Inloop is set for the E1 port.


Handling Procedure

l Cause 1: The T_ALOS alarm occurs on the opposite NE.1. On the T2000, check whether the T_ALOS alarm occurs on the opposite NE. For

details, refer to 8.2 Querying Current Alarms of a Board.2. If yes, clear the T_ALOS alarm on the oppostie NE first and check whether the

UP_E1_AIS alarm on the local NE is cleared.l Cause 2: Inloop is set for the E1 port.

1. On the T2000, check whether there is the LOOP_ALM alarm on the E1 port.2. If yes, set Non-Loopback for the E1 port and check whether the UP_E1_AIS alarm

is cleared. For details, refer to 8.9 Configuring Port Loopback.l Cause 3: The board is faulty.



9-175

1. On the T2000, check whether there is any hardware-related alarm on the two NEs,such as the HARD_BAD alarm.

2. If yes, cold-reset the board that reports the hardware-related alarm and check whetherthe UP_E1_AIS alarm is cleared. For details, refer to 8.16 Resetting Boards.

3. If the UP_E1_AIS alarm persists, replace the related board and check whether theUP_E1_AIS alarm is cleared. For details, refer to 5 Replacing Components.

----End


9.3.130 VC_AIS

DescriptionThe VC_AIS alarm indicates the generation of a virtual channel (VC) connection alarm. Whenthe VC with the segment and end point attributes receives AIS cells, the VC_AIS alarm isreported, indicating that the upstream ATM service is abnormal.

Attribute


0X00E4 Major Communication alarm


Name Meaning

Parameter 1, Parameter 2 Indicates the ATM Trunk.

Impact on Systeml If the continuity check (CC) sink is enabled on an upstream NE but the NE does not receive

any CC cells, the NE reports the VC_LOC alarm and inserts the AIS cells to thedownstream. In this way, the VC_AIS alarm occurs on the local NE. In this case, theconnection, though not interrupted, is not loaded with any service.

l In other cases, the local NE detects the VC connection is interrupted when the VC_AISalarm occurs. The local NE continues inserting the AIS cells to the downstream NE andreturns the RDI cells to the upstream NE.

l In the following case, the VC_AIS will be cleared automatically.


Maintenance Guide


Issue 02 (2009-06-30)

– Receiving the user CC cells

– The CC is disabled

– Not receiving any VCAIS cell in a period of 2.5s (±0.5s)

l When the VC_AIS alarm occurs, the system suppresses the VC_LOC alarm.

Possible CausesThe possible causes of the VC_AIS alarm are as follows:

l Cause 1: An upstream NE reports the VC_LOC alarm and thus inserts the AIS cells to thedownstream NE.

l Cause 4: The board on the local NE is faulty.

Handling Procedurel Cause 1: An upstream NE reports the VC_LOC alarm and thus inserts the AIS cells to the

downstream NE.1. On T2000, check whether there is any VC_LOC alarm with the same ATM connection

ID. For details, refer to 8.2 Querying Current Alarms of a Board.2. If yes, clear the VC_LOC alarm to stop insertion of the AIS cells.

l Cause 2: The board on the local NE is faulty.1. Cold-reset the board that reports the VC_AIS alarm. For details, refer to 8.16

Resetting Boards.2. If the VC_AIS alarm persists, replace the board that reports this alarm. For details,


----End

Related InformationUnidirectional connection

A complete bidirectional connection is divided into a forward unidirectional connection and abackward unidirectional connection. The same NE is for the reference of the forward andbackward connections.

End and segment

An end point refers to the termination point on the chain network and functions to monitor theentire virtual connection.

A segment point always refers to a segment on a link and the segment is monitored.

Segment end point

A segment end point is one segment end attribute. The segment end attributes include segmentpoint, end point, segment end point, and non-segment non-end-point.

l If the segment end attribute is set for an NE, the NE can capture alarms on the segment andend point.

l If the segment point attribute is set for an NE, the NE can only capture the alarms on thesegment.



9-177

l If the end point attribute is set for an NE, the NE can only capture the alarms on the endpoint.

l If the non-segment non-end-point attribute is set for an NE, the NE cannot capture anyalarm on the segment and end point.

9.3.131 VC_LOC

Description

The VC_LOC alarm indicates loss of connectivity check (CC) on the virtual channel (VC). Whenthe CC is enabled but no CC cells are received for more than 3.5s (±0.5s), the VC_LOC alarmis reported. When any CC cell is received, the VC_LOC alarm is cleared automatically.

Attribute



Parameters


Name Meaning


Impact on Systeml If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,

the service connection, though not interrupted, is not loaded with any user service.

l In other cases, the service is interrupted when the VC_LOC alarm occurs.

l When the VC_LOC alarm occurs, the system automatically inserts AIS cells to thedownstream.

l The VC_LOC alarm will be suppressed when the VC_AIS alarm occurs.

Possible Causes

The possible causes of the VC_LOC alarm are as follows:

l Cause 1: The CC sink is enabled on the local NE, but no CC source is enabled on theupstream NE. As a result, the local NE does not receive any CC cells.



Maintenance Guide


Issue 02 (2009-06-30)

Handling Procedure


1. On the T2000, check whether the CC Activate Flag on the local NE is set to Sinkactivate or Source + sink activate. For details, refer to Setting the CC ActivationStatus in the OptiX RTN 950 Radio Transmission System Feature Description manual.

2. If yes, modify the configuration of CC Activate Flag to Deactivate and check whetherthe alarm is cleared.


1. Cold-reset the board that reports the VC_LOC alarm. For details, refer to 8.16Resetting Boards.

2. Replace the board that reports the VC_LOC alarm. For details, refer to 5 ReplacingComponents.

----End

Related Information

None.

9.3.132 VC_RDI

Description

The VC_RDI is an alarm indicating that a fault occurs in the remote end of a virtual channel(VC) connection. When a forward or backward VC connection that is set with the segment andend point attribute receives the RDI cells, the VC_RDI alarm is reported, showing that thedownstream services are abnormal.

Attribute


0x00E5 Major Communication alarm

Parameters


Name Meaning




9-179

Impact on Systeml When the VC_RDI alarm occurs, it just shows that the services in the receive direction of

the downstream VC connection are abnormal. The AIS cells are received in a segment pointof the connection, and the RDI cells are returned to the upstream connection. The servicesare not affected.

l If no VCRDI cell is received in a period of 2.5s (±0.5s), the VC_RDI alarm is clearedautomatically.

Possible CausesThe possible causes of the VC_RDI alarm are as follows:

l Cause 1: The VC_AIS alarm occurs in the receive direction of the downstream connection.

l Cause 2: The ATM processing chip of the board is faulty.

Handling Procedurel Cause 1: The VC_AIS alarm occurs in the receive direction of the downstream connection.

1. On the T2000, check whether the VC_AIS alarm is generated on the VC connectionwhich reports the VC_RDI alarm on the downstream NE. For details, refer to 8.2Querying Current Alarms of a Board.

2. If yes, clear the VC_AIS alarm on the downstream NE first and then check whetherthe VC_RDI alarm on the local NE is cleared.

l Cause 2: The ATM processing chip of the board is faulty.1. Cold-reset the board that reports the VC_RDI alarm. For details, refer to 8.16

Resetting Boards.2. If the VC_RDI alarm persists, replace the board that reports this alarm. For details,


----End


A complete bidirectional connection is divided into a forward unidirectional connection and abackward unidirectional connection. The direction of the forward and backward connections isbased on the same node.

End and segment

An end point refers to the termination point in the chain network, and it is used to monitor theentire virtual connection.

The segment point is, generally, used to monitor a segment of the whole link.

Segment and end point

This is one of the segment end attributes. The segment end attributes include: segment point,end point, segment and end point, non segment and end point.

l If an NE is set with the segment end point attribute, it can capture the alarms that aregenerated at segments and ends.


Maintenance Guide


Issue 02 (2009-06-30)

l If an NE is set with the segment point attribute, it can capture the alarms that are generatedat segments.

l If an NE is set with the end point attribute, it can capture the alarms that are generated atends.

l If an NE is set with the non segment end point attribute, it fails to capture the alarms thatare generated at segments and ends.

9.3.133 VOLT_LOS

Description

The VOLT_LOS is an alarm indicating that the power is not available. When the IF board detectsthat the input or output voltage signals are lost, the VOLT_LOS alarm is reported.

Attribute



Parameters


Name Meaning

Parameter 1 Indicates the type of the power that reports the alarm.l 0x01: Indicates –48 V/+24 V power output.

l 0x02: Indicates –48 V/+24 V power input.

l 0x03: Indicates +5 V power output.

l 0x04: Indicates +3.3 V power output.

l 0x05: Indicates lightning power.

Impact on System

If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.

Possible Causesl The output power is abnormal.

l The input power is abnormal.

l Lightning occurs.



9-181

Handling Procedure

Step 1 Determine the type of the power supply that reports the alarm based on the alarm parameter.

If... Then...

In the case of the input power alarm Go to Step 2.

In the case of the output power alarm Go to Step 3.

In the case of the lightning alarm Contact the engineers to provide powersupply and to check whether lightningprotection is provided.

Step 2 Replace the IF board that reports the alarm.

Step 3 Check the power switch of the ODU.

If... Then...

The power switch is off Turn on the power switch.

The power switch is on Proceed to the next step.

Step 4 Check the IF jumper, IF cable, or ODU section by section for a short circuit.

If... Then...

A short circuit exists Replace the short-circuit component, andthen replace the IF board that reports thealarm.

No short circuit exists Replace the IF board that reports thealarm.

CAUTIONIf the alarm is generated due to a short circuit, replace the short-circuit cable or ODU, and thenreplace the IF board. Otherwise, the new IF board may be damaged.

----End



Maintenance Guide


Issue 02 (2009-06-30)

9.3.134 VP_AIS

DescriptionThe VP_AIS is an alarm indicating the generation of a virtual path (VP) connection alarm. Whena forward or backward VP connection that is set with the segment and end point attribute receivesthe AIS cells, the VP_AIS alarm is reported, showing that the upstream ATM service isabnormal.

Attribute




Name Meaning


Impact on Systeml If the continuity check (CC) sink is enabled on an upstream NE but the NE does not receive

any CC cells, the NE reports the VP_LOC alarm and inserts the AIS cells to the downstream.In this way, the VP_AIS alarm occurs on the local NE. In this case, the connection, thoughnot interrupted, is not loaded with any service.

l In other cases, the local NE detects the VP connection is interrupted when the VP_AISalarm occurs. The local NE continues inserting the AIS cells to the downstream NE andreturns the RDI cells to the upstream NE.

l In the following case, the VP_AIS will be cleared automatically.– Receiving the user CC cells

– The CC is disabled

– Not receiving any VPAIS cell in a period of 2.5s (±0.5s)

l When the VP_AIS alarm occurs, the system suppresses the VP_LOC alarm.

Possible CausesThe possible causes of the VP_AIS alarm are as follows:

l Cause 1: An upstream NE reports the VP_LOC alarm and thus inserts the AIS cells to thedownstream NE.



9-183


Handling Procedurel Cause 1: An upstream NE reports the VP_LOC alarm and thus inserts the AIS cells to the

downstream NE.1. On T2000, check whether there is any VP_LOC alarm with the same ATM connection

ID. For details, refer to 8.2 Querying Current Alarms of a Board.2. If yes, clear the VP_LOC alarm to stop insertion of the AIS cells.

l Cause 2: The board on the local NE is faulty.1. Cold-reset the board that reports the VP_AIS alarm. For details, refer to 8.16 Resetting

Boards.2. If the VP_AIS alarm persists, replace the board that reports this alarm. For details,


----End


A complete bidirectional connection is divided into a forward unidirectional connection and abackward unidirectional connection. The same NE is for the reference of the forward andbackward connections.

End and segment

An end point refers to the termination point on the chain network and functions to monitor theentire virtual connection.

A segment point always refers to a segment on a link and the segment is monitored.

Segment end point

A segment end point is one segment end attribute. The segment end attributes include segmentpoint, end point, segment end point, and non-segment non-end-point.

l If the segment end attribute is set for an NE, the NE can capture alarms on the segment andend point.

l If the segment point attribute is set for an NE, the NE can only capture the alarms on thesegment.

l If the end point attribute is set for an NE, the NE can only capture the alarms on the endpoint.

l If the non-segment non-end-point attribute is set for an NE, the NE cannot capture anyalarm on the segment and end point.

9.3.135 VP_LOC

DescriptionThe VP_LOC alarm indicates loss of connectivity check (CC) on the virtual channel (VP). Whenthe CC is enabled but no CC cells are received for more than 3.5s (±0.5s), the VP_LOC alarmis reported. When any CC cell is received, the VP_LOC alarm is cleared automatically.


Maintenance Guide


Issue 02 (2009-06-30)

Attribute



Parameters


Name Meaning


Impact on Systeml If the CC sink is enabled on the local NE but the local NE does not receive any CC cells,

the service connection, though not interrupted, is not loaded with any user service.

l In other cases, the service is interrupted when the VP_LOC alarm occurs.

l When the VP_LOC alarm occurs, the system automatically inserts AIS cells to thedownstream.

l The VP_LOC alarm will be suppressed when the VP_AIS alarm occurs.

Possible Causes

The possible causes of the VP_LOC alarm are as follows:


l Cause 2: No bandwidth is available on the local NE and thus the CC cells cannot be received.


Handling Procedure


1. On the T2000, check whether the CC Activate Flag on the local NE is set to Sinkactivate or Source + sink activate. For details, refer to Setting the CC ActivationStatus in the OptiX RTN 950 Radio Transmission System Feature Description manual.

2. If yes, modify the configuration of CC Activate Flag to Deactivate and check whetherthe alarm is cleared.

l Cause 2: No bandwidth is available on the local NE and thus the CC cells cannot be received.



9-185

1. On the T2000, check whether the bandwidth configured to the tunnel is fully used.For details, refer to the OptiX RTN 950 Radio Transmission System ConfigurationGuide manual.

2. If yes, expand the bandwidth of tunnel or eliminate the source where a large amountof illegal data is transmitted. Then, check whether the alarm is cleared.


1. Cold-reset the board that reports the VP_LOC alarm. For details, refer to 8.16Resetting Boards.

2. Replace the board that reports the VP_LOC alarm. For details, refer to 5 ReplacingComponents.

----End

Related Information

None.

9.3.136 VP_RDI

Description

The VP_RDI is an alarm indicating that a fault occurs in the remote end of a virtual path (VP)connection. When a forward or backward VP connection that is set with the segment and endpoint attribute receives the RDI cells, the VP_RDI alarm is reported, showing that thedownstream services are abnormal.

Attribute



Parameters


Name Meaning


Impact on Systeml When the VP_RDI alarm occurs, it just shows that the services in the receive direction of

the downstream VP connection are abnormal. The AIS cells are received in a segment point


Maintenance Guide


Issue 02 (2009-06-30)

of the connection, and the RDI cells are returned to the upstream connection. The servicesare not affected.

l If no VCRDI cell is received in a period of 2.5s (±0.5s), the VP_RDI alarm is clearedautomatically.

Possible Causes

The possible causes of the VP_RDI alarm are as follows:

l Cause 1: The VP_AIS alarm occurs in the receive direction of the downstream connection.

l Cause 2: The ATM processing chip of the board is faulty.

Handling Procedure

l Cause 1: The VP_AIS alarm occurs in the receive direction of the downstream connection.1. On the T2000, check whether the VP_AIS alarm is generated on the VP connection

which reports the VP_RDI alarm on the downstream NE. For details, refer to 8.2Querying Current Alarms of a Board.

2. If yes, clear the VP_AIS alarm on the downstream NE first and then check whetherthe VP_RDI alarm on the local NE is cleared.

l Cause 2: The ATM processing chip of the board is faulty.1. Cold-reset the board that reports the VP_RDI alarm. For details, refer to 8.16

Resetting Boards.2. If the VP_RDI alarm persists, replace the board that reports this alarm. For details,


----End

Related Information

Unidirectional connection

A complete bidirectional connection is divided into a forward unidirectional connection and abackward unidirectional connection. The direction of the forward and backward connections isbased on the same node.

End and segment

An end point refers to the termination point in the chain network, and it is used to monitor theentire virtual connection.

The segment point is, generally, used to monitor a segment of the whole link.

Segment and end point

This is one of the segment end attributes. The segment end attributes include: segment point,end point, segment and end point, non segment and end point.

l If an NE is set with the segment end point attribute, it can capture the alarms that aregenerated at segments and ends.

l If an NE is set with the segment point attribute, it can capture the alarms that are generatedat segments.



9-187

l If an NE is set with the end point attribute, it can capture the alarms that are generated atends.

l If an NE is set with the non segment end point attribute, it fails to capture the alarms thatare generated at segments and ends.

9.3.137 WRG_BD_TYPE

Description

The WRG_BD_TYPE alarm indicates that the physical board is of a wrong type. When onephysical board and its logical board are not of the same type, the WRG_BD_TYP alarm isreported.

Attribute



Parameters

None.

None.

Impact on Systeml When the WRG_BD_TYPE alarm occurs, the running services and system are not affected,

but no other service can be configured on the very board.

l The WRG_BD_TYPE alarm will be suppressed when the BD_STATUS alarm occurs.

l When the WRG_BD_TYPE alarm occurs, the system will suppress the other alarms.

Possible Causes

The possible causes of the WRG_BD_TYPE alarm are as follows:

l Cause 1: The physical board and its logical board configured on the T2000 are not of thesame type.


Handling Procedure

l Cause 1: The physical board and its logical board configured on the T2000 are not of thesame type.

1. Check the engineering documents to see whether the logical board configured on theT2000 is wrong or the physical board is wrong.

– If the logical board configured on the T2000 is wrong, re-configure a correct logicalboard on the T2000.


Maintenance Guide


Issue 02 (2009-06-30)

– If the physical board is wrong, replace the physical board with a board of the correcttype. For details, refer to 5 Replacing Components.

l Cause 2: The board is faulty.1. Check whether the board software is matched with the board hardware. If not, reload

the board software or replace the board.2. If the WRG_BD_TYPE alarm persists, replace the board that reports this alarm.

----End




9-189

10 Performance Event

About This Chapter

This chapter describes basic concepts related to performance events and how to handle relatedperformance events of the equipment.

10.1 Basic Concepts Related to Performance EventsYou can use the performance management function to find out the potential risks of the networkrunning and thus to minimize the network failure risks. Understand the basic concepts beforeperforming any operation to monitor the performance.

10.2 Performance Event ListThis chapter describes all performance events supported by the OptiX RTN 950.

10.3 Performance Event HandlingThis section describes performance events of the equipment in terms of the indication, attribute,parameter, impact on system, probable cause, related alarm, handling procedure, and referenceinformation in the alphabetical order (A to Z).

OptiX RTN 950 Radio Transmission SystemMaintenance Guide 10 Performance Event


10-1

10.1 Basic Concepts Related to Performance EventsYou can use the performance management function to find out the potential risks of the networkrunning and thus to minimize the network failure risks. Understand the basic concepts beforeperforming any operation to monitor the performance.

10.1.1 Performance Reporting FlowThe performance reporting flow indicates the entire process from the detection of performanceevents on the board to notification on the T2000. The performance reporting consists of theperformance monitoring enabling, performance automatic reporting, and over-thresholdperformance event notification.

10.1.2 Performance Event CategoryWhen the optical transport network is running normally, internal and external factors, such asnoise sources, dispersion, and fiber break, may affect the transmission quality in the forms ofbit error, jitter, drift, and delay. The influence is called transmission impairment. On the T2000,the performance events reflect the transmission impairment.

10.1.3 Performance ThresholdThe user can set the performance threshold to mask the performance events that vary within thenormal range. In this way, the user can focus on the performance events that are severelydegraded.

10.1.1 Performance Reporting FlowThe performance reporting flow indicates the entire process from the detection of performanceevents on the board to notification on the T2000. The performance reporting consists of theperformance monitoring enabling, performance automatic reporting, and over-thresholdperformance event notification.

Figure 10-1 shows the performance reporting flow.

10 Performance EventOptiX RTN 950 Radio Transmission System

Maintenance Guide


Issue 02 (2009-06-30)

Figure 10-1 Performance reporting flow

Whether to enable the performance

monitoring?

The board collects the performance data and saves the result in the performance register

Yes

No

Yes

No

Yes

No

The performance data is saved to the performance register on

the system control board

Does the current performance cross

the threshold?

The abnormal performance event is reported to the NM

Whether to enable the automatic

reporting?

The performance data is reported to the NM and saved in the database

End

End

NOTE

For details on the specific operations at each phase of the performance reporting flow, see the OptiXiManager T2000 Online Help.

Performance Monitoring

The board monitors the performance. By default, the performance monitoring function of a boardis enabled. For example, in the case of the 15-minute performance, the board detects a spareperformance register and clears the data in the register at the beginning of each period, and thencounts the performance events. At the end of a period, the statistics performance data is refreshedand then stored in the register.

NOTE

The data in the performance register supports wrapped storage.



10-3

Automatic ReportingIf the automatic reporting function is enabled, the system control board automatically reportsthe performance events to the T2000 at the end of each monitoring period.

NOTE

The performance data and NE management information are reported in the same DCC channel. In the caseof large-volume performance data, the network communication is affected. Hence, do not modify theconfiguration of the performance monitoring, unless required. By default, you can enable the performancemonitoring in the entire network, but only need to set performance automatic reporting for the ports wherefaults are likely to occur.

Performance Over-Threshold ReportingIf detecting performance over-threshold, the T2000 reports an abnormal event accordingly. Theperformance over-threshold abnormal event is different from the ordinary abnormal event,because the T2000 processes the former exceptionally and supports exclusive settings. In thecase of such an event, the T2000 displays a dialog box, reminding the user of the event.

10.1.2 Performance Event CategoryWhen the optical transport network is running normally, internal and external factors, such asnoise sources, dispersion, and fiber break, may affect the transmission quality in the forms ofbit error, jitter, drift, and delay. The influence is called transmission impairment. On the T2000,the performance events reflect the transmission impairment.

In the case of the OptiX RTN 950, there are SDH performance events and RMON performanceevents.

l SDH performance events, which mainly indicate the state of equipment point justificationcaused by the bit error and jitter.

l RMON performance events, which mainly indicate communication quality at the ports thatcarry data services.

SDH Performance EventThe SDH performance events are classified into the following categories:l Management layer performance event

l E1 performance event

RMON Performance EventThe RMON performance events are classified into the following categories:l Ethernet performance event

l CES performance event

l L2VPN performance event

l QoS performance event

l ATMoPWE3 performance event

l ATM/IMA performance event

l Tunnel performance event


Maintenance Guide


Issue 02 (2009-06-30)

l PW performance event

l MP performance event

l PPP performance event

10.1.3 Performance ThresholdThe user can set the performance threshold to mask the performance events that vary within thenormal range. In this way, the user can focus on the performance events that are severelydegraded.

Threshold, also called tolerance, indicates the extreme performance value for the transportnetwork to operate normally. The performance threshold is used to determine whether theequipment is working normally. If a performance specification crosses the expected performancethreshold, this indicates a performance degrade trend. In this case, the user should highly regardand handle the performance.

Normally, some margin should be reserved to set the performance threshold, and thus to findout problems beforehand.

10.2 Performance Event ListThis chapter describes all performance events supported by the OptiX RTN 950.

10.2.1 SL91CXPR Performance Event List

10.2.2 TND1EF8T Performance Event List

10.2.3 TND1EF8F Performance Event List

10.2.4 TND1EG2 Performance Event List

10.2.5 TND1ML1/TND1ML1A Performance Event List

10.2.6 TND1IFE2 Performance Event List

10.2.7 TND1AUXQ Performance Event List

10.2.8 TND1PIU Performance Event List

10.2.9 TND1FAN Performance Event List

10.2.10 ODU Performance Event List

10.2.1 SL91CXPR Performance Event List

Table 10-1 SDH Performance Event List

Performance EventName

Indication Performance Event Category

BDTEMPCUR Current board temperature Management layer performanceevent

BDTEMPMAX Maximum boardtemperature



10-5



BDTEMPMIN Minimum boardtemperature

CPUUSAGECUR Current CPU usage

CPUUSAGEMAX Maximum CPU usage

CPUUSAGEMIN Minimum CPU usage

MEMUSAGECUR Current memory usage

MEMUSAGEMAX Maximum memory usage

MEMUSAGEMIN Minimum memory usage

Table 10-2 RMON Performance Event

Performance Event Name Indication Performance EventCategory

MPLS_TUNNEL_FD Delay of the tunnel service Tunnel performance event

MPLS_TUNNEL_FDV Delay variation of thetunnel service

MPLS_TUNNEL_FL Count of lost packets of thetunnel service

MPLS_TUNNEL_FLR Tunnel packet loss ratio

PW_RCVBYTES Count of bytes received onPW

PW performance event

PW_RCVPKTS Count of packets receivedon PW

PW_SNDBYTES Count of bytes transmittedon PW

PW_SNDPKTS Count of packetstransmitted on PW

TUNNEL_RCVBYTES Count of bytes received ontunnel

Tunnel performance event

TUNNEL_RCVPKTS Count of packets receivedon tunnel

TUNNEL_SNDBYTES Count of bytes transmittedon tunnel

TUNNEL_SNDPKTS Count of packetstransmitted on tunnel


Maintenance Guide


Issue 02 (2009-06-30)


VUNI_RCVBYTES Count of bytes received atV-UNI

L2VPN performance event

VUNI_RCVPKTS Count of packets receivedat V-UNI

VUNI_SNDBYTES Count of bytes transmittedat V-UNI

VUNI_SNDPKTS Count of packetstransmitted at V-UNI

VUNI_RCVBYTES Count of bytes received atV-UNI

L3VPN performance event

VUNI_RCVPKTS Count of packets receivedat V-UNI

VUNI_SNDBYTES Count of bytes transmittedat V-UNI

VUNI_SNDPKTS Count of packetstransmitted at V-UNI

10.2.2 TND1EF8T Performance Event List









RXOCTETS Bytes received Ethernet performance event

RXPKTS Packets received

TXOCTETS Bytes transmitted



10-7


TXPKTS Packets transmitted

10.2.3 TND1EF8F Performance Event List







OSPITMPCUR Current value of lasertemperature

Laser performance event

OSPITMPMAX Maximum value of lasertemperature

OSPITMPMIN Minimum value of lasertemperature

RPLCUR Current value of laserreceiving power

RPLMAX Maximum value of laserreceiving power

RPLMIN Minimum value of laserreceiving power

TLBCUR Current value of lasertransmitting bias current

TLBMAX Maximum value of lasertransmitting bias current

TLBMIN Minimum value of lasertransmitting bias current

TPLCUR Current value of lasertransmitting power

TPLMAX Maximum value of lasertransmitting power


Maintenance Guide


Issue 02 (2009-06-30)



TPLMIN Minimum value of lasertransmitting power







10.2.4 TND1EG2 Performance Event List







OSPITMPCUR Current value of lasertemperature

Laser performance event

OSPITMPMAX Maximum value of lasertemperature

OSPITMPMIN Minimum value of lasertemperature

RPLCUR Current value of laserreceiving power

RPLMAX Maximum value of laserreceiving power

RPLMIN Minimum value of laserreceiving power



10-9



TLBCUR Current value of lasertransmitting bias current

TLBMAX Maximum value of lasertransmitting bias current

TLBMIN Minimum value of lasertransmitting bias current

TPLCUR Current value of lasertransmitting power

TPLMAX Maximum value of lasertransmitting power

TPLMIN Minimum value of lasertransmitting power







10.2.5 TND1ML1/TND1ML1A Performance Event List







E1_LCV_SDH Count of coding violationsat the E1 line side

E1 performance event


Maintenance Guide


Issue 02 (2009-06-30)



E1_LES_SDH Count of coding violationseconds at the E1 line side

E1_LLOSS_SDH Count of coding violationloss-of-signal seconds atthe E1 line side

E1_LSES_SDH Count of coding violationseverely errored seconds atthe E1 line side



ATM_CELL_AVAILABILITY

Availability of cells inpercentage

ATM/IMA performance event

ATM_CORRECTED_HCSERR

Count of cells receivedwith correctable HCSerrors

ATM_IF_INRATE_AVG Average rate of normalcells received by the port

ATM_IF_INRATE_MAX Maximum rate of normalcells received by the port

ATM_IF_INRATE_MIN Minimum rate of normalcells received by the port

ATM_IF_OUTRATE_AVG Average rate of normalcells transmitted by theport

ATM_IF_OUTRATE_MAX Maximum rate of normalcells transmitted by theport

ATM_IF_OUTRATE_MIN Minimum rate of normalcells transmitted by theport

ATM_RCVCELLS Count of total cellsreceived

ATM_RCVIDLECELLS Count of total idle cellsreceived



10-11


ATM_SNDCELLS Count of total cellstransmitted

ATM_UNCORRECTED_HCSERR

Count of cells receivedwith uncorrectable HCSerrors

ATMPW_LOSPKTS Count of packets lost ATMoPWE3 performanceevent

ATMPW_MISORDERPKTS Count of out-of-orderpackets

ATMPW_RCVCELLS Count of cells received

ATMPW_SNDCELLS Count of cells transmitted

ATMPW_UNKNOWNCELLS

Count of unknown cells

CES_JTROVR Count of jitter bufferoverflow times

CES performance event

CES_JTRUDR Count of jitter bufferunderflow times

CES_LOSPKTS Count of lost packets

CES_MALPKTS Count of malformedpackets

CES_MISORDERPKTS Count of packets lost dueto the out-of-ordercondition

CES_STRAYPKTS Count of misconnectedpackets

MP_RX_BW_UTILIZATION

MP bandwidth utilizationin receive direction

MP performance event

MP_RX_BYTES Count of received MPbytes

MP_RX_ERRPKTS Count of received erroredMP packets

MP_RX_PKTS Count of received MPservice packets

MP_RX_TOTALPKTS Count of received total MPpackets

MP_TX_BW_UTILIZATION

MP bandwidth utilizationin transmitted direction


Maintenance Guide


Issue 02 (2009-06-30)


MP_TX_BYTES Count of transmitted MPbytes

MP_TX_PKTS Count of transmitted MPservice packets

MP_TX_TOTALPKTS Count of transmitted totalMP packets

PPP_DROPLONGPKTS Count of oversize packets ML-PPP performance event

PPP_IFINPKTS Count of packets receivedat the interface

PPP_IFOUTPKTS Count of packetstransmitted at the interface

PPP_RX_BW_UTILIZATION

PPP bandwidth utilizationin receive direction

PPP performance event

PPP_RX_BYTES Count of receive bytes

PPP_RX_FCSPKTS Count of receive fcs errors

PPP_RX_LOSPKTS Count of lost PPP packetsin receive direction

PPP_RX_PKTS Count of receive packets

PPP_TX_BW_UTILIZATION

PPP bandwidth utilizationin transmitted direction

PPP_TX_BYTES Count of transmit bytes

PPP_TX_LOSPKTS Count of lost PPP packetsin transmitted direction

PPP_TX_PKTS Count of transmit packets

10.2.6 TND1IFE2 Performance Event List

Table 10-11 SDH Performance Events List



BDTEMPCUR Current board temperature Management layer performanceevents




10-13




Table 10-12 Microwave Performance Events List



ACMDOWNCNT Count of the downshift of theAM scheme

AM performance events

ACMUPCNT Count of the upshift of theAM scheme

IFBBE Microwave link backgroundblock errors

Microwave link bit errorperformance events

IFES Microwave link erroredseconds

IFSES Microwave link severelyerrored seconds

IFUAS Microwave link unavailableseconds

IFCSES Microwave link consecutiveseverely errored seconds

FEC_BEF_COR_ER FEC bit error rate beforecorrection

FEC performance events

FEC_COR_BYTE_CNT

Byte count corrected by FEC

FEC_UNCOR_BLOCK_CNT

Frame count uncorrect byFEC

QPSKWS Working time of the QPSKmode

AM performance events

QAMWS16 Working time of the 16QAMmode



QAMWS128 Working time of the128QAM mode


Maintenance Guide


Issue 02 (2009-06-30)



QAMWS256 Working time of the256QAM mode

10.2.7 TND1AUXQ Performance Event List



BDTEMPCUR Current board temperature Management layerperformance event

BDTEMPMAX Maximum board temperature

BDTEMPMIN Minimum board temperature







10.2.8 TND1PIU Performance Event ListNone

10.2.9 TND1FAN Performance Event ListNone



10-15

10.2.10 ODU Performance Event List

Table 10-15 SDH Performance Events List


Indication Performance EventCategory

BDTEMPCUR Current board temperature Management layerperformance events

BDTEMPMAX Maximum board temperature

BDTEMPMIN Minimum board temperature

Table 10-16 Microwave Performance Events List



TSL_MAX Maximum value ofmicrowave transmit signallevel

Microwave power performanceevents

TSL_MIN Minimum value ofmicrowave transmit signallevel

TSL_CUR Current value of microwavetransmit signal level

RSL_MAX Maximum value ofmicrowave receive signallevel

RSL_MIN Minimum value ofmicrowave receive signallevel

RSL_CUR Current value of microwavereceive signal level

RLHTT Duration when the receivepower of the ODU is lowerthan the upper threshold

RLLTT Duration when the receivepower of the ODU is lowerthan the lower threshold

TLHTT Duration when the transmitpower of the ODU is higherthan the upper threshold


Maintenance Guide


Issue 02 (2009-06-30)



TLLTT Duration when the transmitpower of the ODU is higherthan the lower threshold

10.3 Performance Event HandlingThis section describes performance events of the equipment in terms of the indication, attribute,parameter, impact on system, probable cause, related alarm, handling procedure, and referenceinformation in the alphabetical order (A to Z).

10.3.1 ATM_CELL_AVAILABILITY

10.3.2 ATMPW_LOSPKTS

10.3.3 ATMPW_MISORDERPKTS

10.3.4 CES_JTROVR

10.3.5 CES_JTRUDR

10.3.6 E1_LCV_SDH

10.3.7 E1_LES_SDH

10.3.8 E1_LSES_SDH

10.3.9 MEMUSAGECUR

10.3.10 MEMUSAGEMAX

10.3.11 MEMUSAGEMIN

10.3.12 ACMDOWNCNT and ACMUPCNT

10.3.13 BDTMPMAX, BDTMPMIN, and BDTMPCUR

10.3.14 RSLMAX, RSLMIN and RSLCUR

10.3.15 TSLMAX, TSLMIN, and TSLCUR

10.3.16 RLHTT, RLLTT, TLHTT, TLLTT

10.3.17 IFBBE, IFES, IFSES, IFCSES, and IFUAS

10.3.18 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, and FEC_UNCOR_BLOCK_CNT

10.3.19 QPSKWS, QAMWS16, QAMWS32, QAMWS64, QAMWS128, and QAMWS256

10.3.1 ATM_CELL_AVAILABILITY

Description

The ATM_CELL_AVAILABILITY indicates the percentage that the available cells count.



10-17

AttributePerformance Event ID Performance Event Type

519 RMON performance event

Impact on SystemNone.

Generation Principle and Possible CausesWhen the percentage of available cells is counted, the ATM_CELL_AVAILABILITYperformance event occurs.

ProcedureNone.


10.3.2 ATMPW_LOSPKTS

DescriptionThe ATMPW_LOSPKTS indicates the count of lost packets of the ATM emulation service.




Generation Principle and Possible CausesDetermine the quality of the received services by calculating the number of lost packets of thespecified ATM emulation service. The possible causes of the ATMPW_LOSPKTS performanceevent are as follows:l A strong interference source exists near the equipment.

l The board at the transmit or receive end is faulty.

l The fan is faulty.


Maintenance Guide


Issue 02 (2009-06-30)

Related Alarms

None.

Procedure

Step 1 Locate and remove the interference source near the equipment, and then check whether theperformance event is cleared.

Step 2 Replace the faulty board, and then check whether the performance event is cleared.

----End

Related Information

None.

10.3.3 ATMPW_MISORDERPKTS

Description

The ATMPW_MISORDERPKTS indicates the count of disordered packets of the ATMemulation service.

Attribute

Performance Event ID Performance Event Type


Impact on System

None.

Generation Principle and Possible Causes

Determine the quality of the received services at the port by calculating the number of disorderedpackets of the specified ATM emulation service. The possible causes of theATMPW_MISORDERPKTS performance event are as follows:

l A strong interference source exists near the equipment.

l The board at the transmit or receive end is faulty.

l The fan is faulty.

Related Alarms

None.



10-19

Procedure

Step 1 Locate and remove the interference source near the equipment, and then check whether theperformance event is cleared.

Step 2 Replace the faulty board, and then check whether the performance event is cleared.

----End


10.3.4 CES_JTROVR

DescriptionThe CES_JTROVR indicates the count of jitter buffer overflow times.




Generation Principle and Possible CausesWhen the packets in the buffer are full, if service packets are received, the buffer overflows. Themain causes of the CES_JTROVR performance event are as follows:l The clock mode is incorrectly set, and thus the frequencies for transmitting and receiving

packets are inconsistent.l During network congestion, burst packets may cause overflow of buffer.

Related AlarmsNone.

Procedure

Step 1 Check whether the clock modes of the NEs at the two ends are consistent. If the clock modesare consistent and the clock source is the system clock, check whether the system clocks of theNEs at the two ends are synchronized.

Step 2 Check whether the network traffic is congested. If yes, modify the parameters in the jitter bufferof the CES PW.

----End


Maintenance Guide


Issue 02 (2009-06-30)


10.3.5 CES_JTRUDR

DescriptionThe CES_JTRUDR indicates the count of jitter buffer underflow times.




Generation Principle and Possible CausesThe main causes of the CES_JTRUDR performance events are as follows:l The clock mode is incorrectly set, and thus the frequencies for transmitting and receiving

packets are inconsistent.l The network is faulty.

l The network is congested.

Related AlarmsNone.

Procedure

Step 1 Check whether the clock modes of the NEs at the two ends are consistent. If the clock modesare consistent and the clock source is the system clock, check whether the system clocks of theNEs at the two ends are synchronized.

Step 2 The performance event of packet loss may cause underflow of buffer. Hence, check whether theCES_LOSPKTS performance event is reported. If yes, see the procedure for handling theCES_LOSPKTS performance event.

Step 3 If the CES_LOSPKTS performance event is reported, the chip may be abnormal. In this case,replace the board.

----End




10-21

10.3.6 E1_LCV_SDH

Description

The E1_LCV_SDH indicates the count of coding violations at the E1 line side.

Attribute


0x0c SDH performance event

Impact on System

The service has bit errors. Find out the cause and handle the problem in a timely manner to avoidthe occurrence of any alarm, which may affect the signal transmission quality.


When the coding violations at the line side are counted, the E1_LCV_SDH performance eventoccurs.

l External causes– The cable performance is degraded, and the cable has extremely high attenuation.

– The cable connector is of an incorrect type.

– The equipment is improperly grounded.

– A strong interference source is present near the equipment.

– The working temperature is extremely high or extremely low, and the equipment cannottolerate such temperature.

l Equipment causes– An incorrect service code is selected.

– The board becomes faulty, or the performance of the board is degraded.

Related Alarms

None.

Procedure

Step 1 First eliminate external causes, such as poor grounding, extremely high operating temperature,extremely low or extremely high received optical power of the processing board.

Step 2 Check whether the correct E1 service code is selected. If not, modify the code of the servicesreceived by a board by setting the code type of the board.

----End


Maintenance Guide


Issue 02 (2009-06-30)

Related Information

None.

10.3.7 E1_LES_SDH

Description

The E1_LSES_SDH indicates the coding violation errored seconds at the E1 line side.

Attribute


0x0D SDH performance event

Impact on System



When the coding violation errored seconds at the E1 line side are counted, the E1_LSES_SDHperformance event occurs.







– The board becomes faulty, or the performance of the board is degraded.

Related Alarms

None.

Procedure

Step 1 Refer to the method of handling the E1_LCV_SDH performance event.

----End



10-23

Related Information

None.

10.3.8 E1_LSES_SDH

Description

The E1_LSES_SDH indicates the coding violation severely errored seconds at the E1 line side.

Attribute


0x0E SDH performance event

Impact on System



When the coding violation severely errored seconds at the E1 line side are counted, theE1_LSES_SDH performance event occurs.







– The board fails or the board performance is degraded.

Related Alarms

None.

Procedure

Step 1 Refer to the method of handling the E1_LCV_SDH performance event.

----End


Maintenance Guide


Issue 02 (2009-06-30)


10.3.9 MEMUSAGECUR

DescriptionThe MEMUSAGECUR performance event indicates the current memory usage ratio.


0x3A4C SDH performance event

Impact on SystemNone

Generation Principle and Possible CausesThe MEMUSAGECUR performance event is generated to indicate the current memory usageratio.

Related AlarmsNone

ProcedureNone

Related InformationNone

10.3.10 MEMUSAGEMAX

DescriptionThe MEMUSAGEMAX performance event indicates the maximum memory usage ratio.


0x3A4A SDH performance event



10-25


Generation Principle and Possible CausesThe MEMUSAGEMAX performance event is generated when the memory usage ratio reachesthe maximum value.

Related AlarmsNone

ProcedureNone

Related InformationNone

10.3.11 MEMUSAGEMIN

DescriptionThe MEMUSAGEMIN performance event indicates the minimum memory usage ratio.


0x3A4B SDH performance event


Generation Principle and Possible CausesThe MEMUSAGEMIN performance event is reported when the memory usage ratio reaches theminimum value.

Related AlarmsNone

ProcedureNone


Maintenance Guide


Issue 02 (2009-06-30)

Related Information

None

10.3.12 ACMDOWNCNT and ACMUPCNT

Descriptionl The ACMDOWNCNT indicates count of the downshift of the AM scheme.

l The ACMUPCNT indicates count of the upshift of the AM scheme.

Attribute

Attribute Description

Basic unit of a performance event ACMDCNT, ACMUCNT

Unit -


Related Alarms

None.

10.3.13 BDTMPMAX, BDTMPMIN, and BDTMPCUR

Performance Event Meaningl BDTMPMAX stands for "Maximum board temperature".

l BDTMPMIN stands for "Minimum board temperature".

l BDTMPCUR stands for "Current board temperature".

Performance Event Attribute

Performance Event Attribute Description

Performance event cell None

Unit 0.1ºC

Impact on the SystemExcessively high or low board temperature might cause faults such as degradation of the boardworking performance and bit errors.



10-27

Relevant Alarm

If the board temperature crosses the threshold, the TEMP_ALARM alarm occurs.

10.3.14 RSLMAX, RSLMIN and RSLCUR

Performance Event Meaningl RSLMAX stands for "Maximum value of microwave receive signal level".

l RSLMIN stands for "Maximum value of microwave receive signal level".

l RSLCUR "Current value of microwave receive power".



Performance event cell RSL

Unit 0.1 dBm

Impact on the SystemWhen the microwave receive power is overly low or overly high, bit errors might occur and theservice might be interrupted.

Relevant Alarm

If the receive power crosses the threshold, the RADIO_RSL_HIGH or RADIO_RSL_LOWalarm occurs.

10.3.15 TSLMAX, TSLMIN, and TSLCUR

Performance Event Meaningl TSLMAX stands for "maximum value of microwave transmit signal level".

l TSLMIN stands for "minimum value of microwave transmit signal level".

l TSLCUR stands for "current value of microwave transmit signal level".



Performance event cell TSL

Unit 0.1 dBm


Maintenance Guide


Issue 02 (2009-06-30)

Impact on the SystemWhen the microwave transmit power is too low or too high, the receive power at the oppositestation will be too low or too high. Moreover, bit errors might occur and services might beinterrupted.

Relevant AlarmIf the transmit power crosses the threshold, the RADIO_TSL_HIGH orRADIO_TSL_LOW alarm can occur.

10.3.16 RLHTT, RLLTT, TLHTT, TLLTT

Descriptionl The RLHTT indicates the duration when the ODU at the local end has a receive power

lower than the upper threshold.l The RLLTT indicates the duration when the ODU at the local end has a receive power

lower than the lower threshold.l The TLHTT indicates the duration when the ODU at the local end has a transit power lower

than the upper threshold.l The TLLTT indicates the duration when the ODU at the local end has a transit power lower

than the lower threshold.

AttributeAttribute Description

Basic unit of a performance event RLHTS, RLLTS, TLHTS, and TLLTS

Unit Second


Related AlarmsNone.

10.3.17 IFBBE, IFES, IFSES, IFCSES, and IFUAS

Meanings of Performance Eventsl IFBBE stands for "microwave link background block errors".

Background block error (BBE) is an errored block occurred outside the period of UAT andSES.

l IFES stands for "microwave link errored seconds".An errored second (ES) is a specific second with one or more errored blocks detected.



10-29

l IFSES stands for "microwave link severely errored seconds".

A severely errored second (SES) is a specific second with not less than 30% errored blocksor at least one serious disturbance period (SDP) detected. The SDP is a period when signalloss is detected or the error ratios of all the consecutive blocks are greater than or equal to10-2 in at least four consecutive blocks or 1 ms (taking the longer one).

l IFCSES stands for "microwave link consecutive severely errored seconds".

Consecutive severely errored second (CSES) is a second when consecutive SES eventsarise but last less than 10 seconds.

l IFUAS stands for "microwave link unavailable second".

An unavailable second (UAS) is counted from the first second of ten SESs, which areconsidered to be part of the unavailable time. A new available second period starts fromthe first second of ten consecutive non-SESs, which are considered to be part of the availabletime.

Attributes of Performance Events

Attributes of Performance Events Description

Performance event cell IFCNT

Unit Block (IFBBE)Second (IFES, IFSES, IFCSES, and IFUAS)

Impact on the SystemA small number of bit errors do not affect the service. Too many bit errors, however, mayinterrupt the service. Generally, the BER should be less than 10-3 for voice service and less than10-6for data service.

Relevant Alarms

MW_BER_SD or MW_BER_EXC alarm.

Probable Causes

The system detects microwave link bit errors by using the bit error detection overheads.

Procedure

Step 1 Check whether the MW_FECUNCOR and RPS_INDI alarms are generated.

If ... Then ...

Yes, See Troubleshooting Microwave Links.

No, Replace the IF Board.

----End


Maintenance Guide


Issue 02 (2009-06-30)

10.3.18 FEC_BEF_COR_ER, FEC_COR_BYTE_CNT, andFEC_UNCOR_BLOCK_CNT

Performance Event Meaningl FEC_BEF_COR_ER stands for "FEC bit error rate before correcting the errors".

This event indicates the impact of the external environment on the transmission.l FEC_COR_BYTE_CNT stands for "FEC corrected byte count".

This event indicates the impact of the FEC.l FEC_UNCOR_BLOCK_CNT stands for the number of frames that cannot be corrected by

FEC.This event reflects the number of bit errors after the errors are corrected by FEC.

Performance Event AttributePerformance Event Attribute Description

Performance event cell FECBEFCORER (FEC_BEF_COR_ER),FECUNCORBLOCKCNT(FEC_COR_BYTE_CNT),FECUNCORBLOCKCNT(FEC_UNCOR_BLOCK_CNT)

Unit None (FEC_BEF_COR_ER)Byte (FEC_COR_BYTE_CNT andFEC_UNCOR_BLOCK_CNT)

Impact on the SystemIf the FEC_BEF_COR_ER is too high, there will be residual bit errors in services after the FEC.

If the FEC_UNCOR_BLOCK_CNT is not zero, it indicates that uncorrectable bit errors existin microwave links, and bit errors exist in services.

Relevant AlarmsIf any byte cannot be troubleshooted, the MW_FECUNCOR alarm occurs.

10.3.19 QPSKWS, QAMWS16, QAMWS32, QAMWS64,QAMWS128, and QAMWS256

Descriptionl QPSKWS: Indicates the working time of the QPSK mode.

l QAMWS16: Indicates the working time of the 16QAM mode.





10-31



Performance Event AttributesPerformance Event Attribute Description

Basic unit of a performance event QPSKWSSECOND (QPSKWS)QAMWS16SECOND (QAMWS16)QAMWS32SECOND (QAMWS32)QAMWS64SECOND (QAMWS64)QAMWS128SECOND (QAMWS128)QAMWS256SECOND (QAMWS256)

Unit Second

Impact on SystemWhen the AM function is not enabled, the performance event does not affect the system.

When the AM function is enabled, normally, the seconds of the modulation mode for ensuringcapacity make up a larger percentage. In the duration set for good weather, the seconds of thelow modulation mode make up a larger percentage. The performance of the microwave link isabnormal.

Relevant AlarmsNone.


Maintenance Guide


Issue 02 (2009-06-30)

A Glossary

A

ACAP The Adjacent Channel Alternate Polarization (ACAP) operation providesorthogonal polarizations between two adjacent communication channels.

Alarm A visible or an audible indication to notify the person concerned that afailure or an emergency has occurred.

Alarm AutomaticReporting

A function used for the NE to report the alarms to the NMS upongeneration of the alarms.

Alarm Filter An function used for the NMS not to display the alarms reported by theNE.

AlarmSuppression

A function used not to monitor alarms for a specific object, which maybe the networkwide equipment, a specific NE, a specific board and evena specific function module of a specific board.

APS Automatic Protection Switching (APS) is the capability of a transmissionsystem to detect a failure on a working facility and to switch to a standbyfacility to recover the traffic.

ATPC Automatic Transmit Power Control. A method of automatically adjustingthe transmit power at the opposite end based on the transmit signaldetected at the receiver.

ATM The asynchronous transfer mode (ATM) is designed to transfer cell inwhich multiple service types (such as voice, video, or data) are conveyedin fixed-length (53-byte) cells. Fixed-length cells allow cell processingto occur in hardware, thereby reducing transit delays.

Attenuator A passive component used to adjust the signal attenuation.

B

Backup Backup is a method of copying data to the standby storage area to avoiddata loss when the primary storage area is damaged or crashed.

OptiX RTN 950 Radio Transmission SystemMaintenance Guide A Glossary


A-1

Bit error An error occurs on some bits in the code stream after the bits are received,judged and regenerated, and the error impairs the quality of informationtransmitted.

Bit error ratio The ratio of error bits to the transmitted bits during a specified time.

Bandwidth Amount of data that can be carried from one point to another in a giventime period (usually a second).

Bit Error Rate Percentage of bits that have errors relative to the total number of bitsreceived in a transmission.

Broadcast To transmit message frames to all stations in a network.

C

CCDP The co-channel dual polarization (CCDP) operation provides two parallelcommunication channels over the same link with orthogonalpolarizations, thus doubling the link capacity.

CCM Continuity check message. A type of packets used to check the link status.

CES Circuit emulation service (CES) is a technology that adapts the traditionalnarrowband services (that is, TDM services) to the wideband.

Channel Smallest subdivision of a circuit that provides a type of communicationservice; usually a path with only one direction.

Client A terminal (computer or workstation) that sends signaling to the serverand display the result on the user interface

Clock Tracing A method used by all nodes in a network to keep synchronous with oneclock source.

Connector A device installed at the end of a fiber, optical source or receive unit. Itis used to couple the optical wave to the fiber when connected to anotherdevice of the same type. A connector can either connect two fiber endsor connect a fiber end and a optical source (or a detector).

Current Alarm An alarm that is not cleared or cleared but not acknowledged.

E

Ejector lever A component at the two ends of the front panel of a board, which is usedfor inserting or removing the board.

Electrostaticdischarge

A sudden flow of electric current through a material that is normally aninsulator.

Exerciseswitching

An operation to check if the protection switching protocol functionsnormally. The protection switching is not really performed.

A GlossaryOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

Ethernet Ethernet uses a bus or star topology and supports data transfer rates of 10Mbps.The Ethernet specification served as the basis for the IEEE 802.3standard, which specifies the physical and lower software layers.Ethernet uses the CSMA/CD access method to handle simultaneousdemands. It is one of the most widely implemented LAN standards.

F

Failure A condition where a component does not function in the case of a lastingfault.

Fault A case where a function cannot perform the specified operation. The casewhere operations cannot be performed due to preventive maintenance,lack of external resources and intended settings is not included.

FD Frequency Diversity. Two or more microwave frequencies with certainfrequency space are used to transmit/receive the same signal and selectionis then performed between the two signals to ease the impact of fading.

FEC Forward Error Correction. A bit error correction technology that adds tothe payload at the transmit end the correction information based on whichthe bit errors generated during transmission are corrected at the receiveend.

Fiber jumper Fiber that is used for connections between the subrack and the ODF, andfor connections between subracks or inside a subrack.

Forced switching To forcibly switch the service to the protection board. Even though theprotection board is faulty, the switching will still occur.

Frame A cyclic set of consecutive timeslots in which the relative position of eachtime slot can be identified.

I

IDU Indoor Unit. The indoor unit implements accessing, multiplexing/demultiplexing, and IF processing for services.

IGMP Internet Group Management Protocol. The Protocol is used by IPv4systems (hosts and routers) to report their IP multicast groupmemberships to any neighboring multicast routers.

IGMP Snooping IGMP Snooping is the process of listening to IGMP traffic. IGMPsnooping, as implied by the name, is a feature that allows the switch to"listen in" on the IGMP conversation between hosts and routers byprocessing the layer 3 IGMP packets sent in a multicast network.

IMA The inverse multiplexing for ATM (IMA) technology is used todemultiplex an ATM integrated cell flow into several lower rate links. Atthe far end, the lower rate links are multiplexed to recover the originalintegrated cell flow.



A-3

Inloop Loop a signal from the cross-connect board, at a physical port, back tothe cross-connect board.

J

Jitter Short waveform variation caused by vibration, voltage fluctuations, orcontrol system instability.

L

Laser The device that generates the directional light covering a narrow rangeof wavelengths. Laser light is more coherent than ordinary light.Semiconductor diode lasers are the used light source in fiber-opticsystem.

LCAS Link Capacity Adjustment Scheme. A solution features flexiblebandwidth and dynamic adjustment. In addition, it provides a failuretolerance mechanism, which enhances the viability of virtualconcatenations and enables the dynamic adjustment to bandwidth (non-service affecting).

Loopback A troubleshooting technique that returns a transmitted signal to its sourceso that the signal or message can be analyzed for errors.

Locked switching In the case of locked switching, when the switching condition is satisfied,the service cannot be switched from the working path to the protectionpath; when the switching occurs, the service can be restored from theprotection path to the working path.

LSP Label switch path (LSP) is an ingress and egress switched path builtthrough a series of label switch routers to forward the packets of aparticular FEC using a label swapping forwarding mechanism.

M

MA A part of the maintenance domain.

Manual switching A protection switching. When the protection path is normal and there isno request of a higher level switching, the service is manually switchedfrom the working path to the protection path, to test whether the networkstill has the protection capability.

MD Network-edge equipment that can transmit or receive multicast packetsto or from each other

MEP Maintenance association end point. An edge node of the maintenanceassociation.

MPLS Multiprotocol label switching (MPLS) is a versatile solution to addressthe problems faced by present-day networks speed, scalability, quality-of-service (QoS) management, and traffic engineering.


Maintenance Guide


Issue 02 (2009-06-30)

MSP Multiplex section protection. The function performed to providecapability for switching a signal between and including two MSTfunctions, from a "working" to a "protection" channel.

N

N+1 protection A microwave link protection system that employs N working channelsand one protection channel.

NE Network element (NE) that contains hardware and the software that runson the hardware. Generally, one network element should contain one SCCboard at least, which manages and monitors the entire network element.The NE software runs on the SCC board.

NE Explorer A main operation interface of the T2000. A expandable object tree(function tree) is set at the lower left pane of the interface. The user canquickly locate the operation object from the object tree and then performconfiguration, management and maintenance accordingly.

O

OAM To operate, manage and maintain a network or network equipment.

ODU Outdoor Unit. The outdoor unit implements frequency conversion andamplification for RF signals.

Optical interface A component that connects several transmit or receive units

P

PDH Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bitstuffing and byte interleaving. It multiplexes the minimum rate 64 kit/sinto the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s rates.

Power supply box The DC power distribution box on the top of a cabinet, providing powersupply to the subracks in the cabinet.

ProtectionChannel

A channel labeled with the protection attribute in the protection group.

Q

QinQ The QinQ, a Layer 2 tunnel protocol developed based on the IEEE 802.1Qencapsulation, allows for individual VLANs with extra tag informationto traverse the backbone networks and thus provides Layer 2 VPN tunnelsfor users.

R



A-5

RSTP Rapid Spanning Tree Protocol. The protocol is an evolution of theSpanning Tree Protocol, providing for faster spanning tree convergenceafter a topology change.

S

SD Space Diversity. Two or more antennas separated by a specific distancetransmit/receive the same signal and selection is then performed betweenthe two signals to ease the impact of fading. Currently, only receive SDis used.

SDH Synchronous Digital Hierarchy. A hierarchical set of digital transportstructures, standardized for the transport of suitably adapted payloadsover physical transmission networks.

SNCP Subnetwork connection protection. A working subnetwork connection isreplaced by a protection subnetwork connection if the workingsubnetwork connection fails, or if its performance falls below a requiredlevel.

STP The Spanning Tree Protocol (STP), defined in the IEEE Standard 802.1D,is an OSI layer-2 protocol that ensures a loop free topology for anybridged LAN.

T

T2000 A subnet management system (SNMS). In the telecommunicationmanagement network architecture, the T2000 is located between the NElevel and network level, which can supports all NE level functions andpart of the network level management functions.

Tunnel A secure communication path between two peers, such as two routers.

U

Unicast The process of sending data from a source to a single recipient.


Maintenance Guide


Issue 02 (2009-06-30)

B Acronyms and Abbreviations

A

AIS Alarm Indication Signal

APS Automatic Protection Switching

ARP Address Resolution Protocol

ATPC Automatic Transmit Power Control

ATM Asynchronous Transfer Mode

AU Administrative Unit

B

BER Bit Error Rate

BIP Bit-Interleaved Parity

BPDU Bridge Protocol Data Unit

C

CAR Committed Access Rate

CBS Committed Burst Size

CCDP Co-Channel Dual Polarization

CCM Continuity Check Message

CES Circuit Emulation Service

CF Compact Flash

CGMP Cisco Group Management Protocol

CIR Committed Information Rate

CLNP Connectionless Network Protocol

OptiX RTN 950 Radio Transmission SystemMaintenance Guide B Acronyms and Abbreviations


B-1

CLNS Connectionless Network Service

CoS Class of Service

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CVLAN Customer VLAN

C-VLAN Customer VLAN

D

DC Direct Current

DCC Data Communications Channel

DCN Data Communication Network

DSCP Differentiated Services Code Point

DVMRP Distance Vector Multicast Routing Protocol

E

ECC Embedded Control Channel

EPL Ethernet Private Line

EPLAN Ethernet Private LAN

ES-IS End System to Intermediate System

EVPL Ethernet Virtual Private Line

F

FCS Frame Check Sequence

FD Frequency Diversity

FE Fast Ethernet

FEC Forward Error Correction

FIFO First In First Out

FLP Fast Link Pulse

FTP File Transfer Protocol

G

GE Gigabit Ethernet

B Acronyms and AbbreviationsOptiX RTN 950 Radio Transmission System

Maintenance Guide

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

Issue 02 (2009-06-30)

GFP Generic Framing Procedure

GTS Generic Traffic Shaping

GUI Graphical User Interface

H

HDLC High Level Data Link Control Procedure

HP Higher Order Path

HSB Hot Standby

HSM Hitless Switch Mode

I

ICMP Internet Control Message Protocol

IDU Indoor Unit

IEEE Institute of Electrical and ElectronicsEngineers

IETF The Internet Engineering Task Force

IF Intermediate Frequency

IGMP Internet Group Management Protocol

IMA Inverse Multiplexing for ATM

IP Internet Protocol

IPv6 Internet Protocol version 6

IS-IS Intermediate System to Intermediate System

ISO International Standard Organization

ITU-T International Telecommunication Union -Telecommunication Standardization Sector

IVL Independence VLAN Learning

L

LAN Local Area Network

LAPD Link Access Procedure on the D channel

LAPS Link Access Procedure-SDH

LCAS Link Capacity Adjustment Scheme

LMSP Linear Multiplex Section Protection



B-3

LOF Loss Of Frame

LOM Loss Of Multiframe

LOP Loss Of Pointer

LOS Loss Of Signal

LP Lower Order Path

LSP Label Switch Path

M

MA Maintenance Association

MAC Medium Access Control

MBS Maximum Burst Size

MD Maintenance Domain

MDI Medium Dependent Interface

MEP Maintenance Association End Point

MIB Management Information Base

MLM Multi-Longitudinal Mode

MPLS Multiprotocol Label Switching

MO Managed Object

MS Multiplex Section

MSP Multiplex Section Protection

MTU Maximum Transmission Unit

N

NE Network Element

NLP Normal Link Pulse

NMS Network Management System

NNI Network-to-Network Interface or NetworkNode Interface

NSAP Network Service Access Point

O

OAM Operation, Administration and Maintenance

ODU Outdoor Unit


Maintenance Guide


Issue 02 (2009-06-30)

OSI Open Systems Interconnection

OSPF Open Shortest Path First

P

PCB Printed Circuit Board

PDH Plesiochronous Digital Hierarchy

PIM-DM Protocol Independent Multicast-Dense Mode

PIM-SM Protocol Independent Multicast-Sparse Mode

PPP Point-to-Point Protocol

Q

QinQ 802.1Q in 802.1Q

QoS Quality of Service

R

RDI Remote Defect Indication

REI Remote Error Indication

RF Radio Frequency

RFC Request For Comment

RIP Routing Information Protocol

RMON Remote Network Monitoring

RSL Received Signal Level

RSTP Rapid Spanning Tree Protocol

RTN Radio Transmission Node

S

SD Signal Degrade

SDH Synchronous Digital Hierarchy

SDP Serious Disturbance Period

SES Severely Errored Second

SF Signal Fail

SLM Single-Longitudinal Mode



B-5

SNC SubNetwork Connection

SNCP Sub-Network Connection Protection

SNMP Simple Network Management Protocol

SNR Signal-to-Noise Ratio

STM Synchronous Transport Module

STM-1 SDH Transport Module -1

STM-1e STM-1 Electrical Interface

STM-1o STM-1 Optical Interface

STM-4 SDH Transport Module -4

STM-N SDH Transport Module -N

STP Spanning Tree Protocol

SVL Shared VLAN Learning

T

TCI Tag Control Information

TCP Transfer Control Protocol

TIM Trace Identifier Mismatch

TPS Tributary Protection Switching

TU Tributary Unit

U

UAS Unavailable Second

UDP User Datagram Protocol

UNI User-Network Interface

UPS Uninterruptible Power Supply

V

VC Virtual Container

VC12 Virtual Container -12

VC-12 Virtual Container -12




Maintenance Guide


Issue 02 (2009-06-30)



VCG Virtual Concatenation Group

VLAN Virtual LAN

VoIP Voice over IP

VPN Virtual Private Network

W

WAN Wide Area Network

WRR Weighted Round Robin

WTR Wait to Restore Time

X

XPD Cross-Polarization Discrimination

XPIC Cross-polarization interference cancellation



B-7

Maintenance Guide(V100R001C00 02)

Documents