Академический Документы
Профессиональный Документы
Культура Документы
V100R002
Issue 03
Date 2008-8-30
Part Number 00425665
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
4 Troubleshooting Guide.............................................................................................................4-1
4.1 General Fault Locating Procedures.................................................................................................................4-3
4.2 Troubleshooting Service Interruptions............................................................................................................4-5
4.3 Troubleshooting Microwave Links...............................................................................................................4-10
4.4 Troubleshooting Bit Errors............................................................................................................................4-17
4.5 Troubleshooting Pointer Justifications..........................................................................................................4-22
4.6 Troubleshooting the Interconnection with the SDH Equipment...................................................................4-26
4.7 Troubleshooting the Interconnection with the PDH Equipment...................................................................4-30
4.8 Troubleshooting Ethernet Service Faults......................................................................................................4-32
4.9 Troubleshooting the Orderwire.....................................................................................................................4-38
A Alarm Reference.......................................................................................................................A-1
A.1 Alarm List......................................................................................................................................................A-1
A.2 Alarms and Corrective Procedures..............................................................................................................A-10
A.2.1 A_LOC...............................................................................................................................................A-10
A.2.2 APS_MANUAL_STOP.....................................................................................................................A-11
A.2.3 ALM_GFP_dCSF...............................................................................................................................A-12
A.2.4 ALM_GFP_dLFD..............................................................................................................................A-13
A.2.5 ALM_RTC_FAIL...............................................................................................................................A-14
A.2.6 APS_FAIL..........................................................................................................................................A-15
A.2.7 APS_INDI..........................................................................................................................................A-16
A.2.8 AU_AIS..............................................................................................................................................A-17
A.2.9 AU_LOP.............................................................................................................................................A-19
A.2.10 B1_EXC...........................................................................................................................................A-20
A.2.11 B1_SD..............................................................................................................................................A-21
A.2.12 B2_EXC...........................................................................................................................................A-22
A.2.13 B2_SD..............................................................................................................................................A-23
A.2.14 B3_EXC...........................................................................................................................................A-24
A.2.15 B3_EXC_VC3..................................................................................................................................A-25
A.2.16 B3_SD..............................................................................................................................................A-26
A.2.17 B3_SD_VC3.....................................................................................................................................A-27
A.2.18 BD_NOT_INSTALLED..................................................................................................................A-28
A.2.19 BD_STATUS...................................................................................................................................A-29
A.2.20 BIP_EXC..........................................................................................................................................A-32
A.2.21 BIP_SD.............................................................................................................................................A-33
A.2.22 BOOTROM_BAD............................................................................................................................A-33
A.2.23 C2_VCAIS.......................................................................................................................................A-35
A.2.24 CONFIG_NOSUPPORT..................................................................................................................A-35
A.2.25 DBMS_ERROR...............................................................................................................................A-37
A.2.26 DBMS_PROTECT_MODE.............................................................................................................A-39
A.2.27 DN_E1_AIS.....................................................................................................................................A-40
A.2.28 E1_LOC............................................................................................................................................A-41
A.2.29 E1_LOS............................................................................................................................................A-42
A.2.30 ESN_FAILED..................................................................................................................................A-43
A.2.31 ESN_INVALID................................................................................................................................A-44
A.2.32 ETH_LOS.........................................................................................................................................A-45
A.2.33 EXT_SYNC_LOS............................................................................................................................A-46
A.2.34 F1PORT_FAILED...........................................................................................................................A-48
A.2.35 FAN_FAIL.......................................................................................................................................A-48
A.2.36 FCS_ERR.........................................................................................................................................A-49
A.2.37 HARD_BAD....................................................................................................................................A-51
A.2.38 HP_CROSSTR.................................................................................................................................A-53
A.2.39 HP_LOM..........................................................................................................................................A-54
A.2.40 HP_RDI............................................................................................................................................A-55
A.2.41 HP_REI.............................................................................................................................................A-56
A.2.42 HP_SLM...........................................................................................................................................A-57
A.2.43 HP_TIM............................................................................................................................................A-59
A.2.44 HP_UNEQ........................................................................................................................................A-60
A.2.45 HPAD_CROSSTR...........................................................................................................................A-61
A.2.46 HSB_INDI........................................................................................................................................A-62
A.2.47 HSM_INDI.......................................................................................................................................A-63
A.2.48 IF_CABLE_OPEN...........................................................................................................................A-64
A.2.49 IF_INPWR_ABN.............................................................................................................................A-65
A.2.50 IF_MODE_UNSUPPORTED..........................................................................................................A-67
A.2.51 IN_PWR_HIGH...............................................................................................................................A-67
A.2.52 IN_PWR_LOW................................................................................................................................A-69
A.2.53 J0_MM.............................................................................................................................................A-70
A.2.54 K1_K2_M.........................................................................................................................................A-71
A.2.55 K2_M................................................................................................................................................A-72
A.2.56 LASER_CLOSED............................................................................................................................A-74
A.2.57 LASER_MOD_ERR_EX.................................................................................................................A-75
A.2.58 LCAS_FOPR....................................................................................................................................A-76
A.2.59 LCAS_FOPT....................................................................................................................................A-77
A.2.60 LCAS_PLCR....................................................................................................................................A-79
A.2.61 LCAS_PLCT....................................................................................................................................A-80
A.2.62 LCAS_TLCR....................................................................................................................................A-81
A.2.63 LCAS_TLCT....................................................................................................................................A-83
A.2.64 LCS_LIMITED................................................................................................................................A-84
A.2.65 LICENSE_LOST..............................................................................................................................A-85
A.2.66 LICENSE_ERR................................................................................................................................A-86
A.2.67 LINK_ERR.......................................................................................................................................A-87
A.2.68 LOOP_ALM.....................................................................................................................................A-88
A.2.69 LPS_UNI_BI_M...............................................................................................................................A-90
A.2.70 LP_CROSSTR..................................................................................................................................A-91
A.2.71 LP_R_FIFO......................................................................................................................................A-92
A.2.72 LP_RDI.............................................................................................................................................A-93
A.2.73 LP_RDI_VC12.................................................................................................................................A-94
A.2.74 LP_RDI_VC3...................................................................................................................................A-95
A.2.75 LP_REI.............................................................................................................................................A-96
A.2.76 LP_REI_VC12.................................................................................................................................A-97
A.2.77 LP_REI_VC3...................................................................................................................................A-97
A.2.78 LP_RFI.............................................................................................................................................A-98
A.2.79 LP_SIZE_ERR.................................................................................................................................A-99
A.2.80 LP_SLM.........................................................................................................................................A-100
A.2.81 LP_SLM_VC12..............................................................................................................................A-101
A.2.82 LP_SLM_VC3................................................................................................................................A-102
A.2.83 LP_T_FIFO....................................................................................................................................A-103
A.2.84 LP_TIM..........................................................................................................................................A-104
A.2.85 LP_TIM_VC12...............................................................................................................................A-105
A.2.86 LP_TIM_VC3.................................................................................................................................A-106
A.2.87 LP_UNEQ......................................................................................................................................A-107
A.2.88 LP_UNEQ_VC12...........................................................................................................................A-108
A.2.89 LP_UNEQ_VC3.............................................................................................................................A-109
A.2.90 LSR_NO_FITED............................................................................................................................A-111
A.2.91 LSR_WILL_DIE............................................................................................................................A-111
A.2.92 LTI..................................................................................................................................................A-112
A.2.93 MOD_TYPE_MISMATCH...........................................................................................................A-114
A.2.94 MS_AIS..........................................................................................................................................A-115
A.2.95 MS_CROSSTR...............................................................................................................................A-116
A.2.96 MS_RDI.........................................................................................................................................A-117
A.2.97 MS_REI..........................................................................................................................................A-118
A.2.98 MSAD_CROSSTR.........................................................................................................................A-119
A.2.99 MSSW_DIFFERENT.....................................................................................................................A-120
A.2.100 MW_FECUNCOR.......................................................................................................................A-121
A.2.101 MW_LIM.....................................................................................................................................A-122
A.2.102 MW_LOF.....................................................................................................................................A-124
A.2.103 MW_RDI......................................................................................................................................A-125
A.2.104 NESF_LOST................................................................................................................................A-126
A.2.105 NESTATE_INSTALL..................................................................................................................A-127
A.2.106 NO_BD_SOFT.............................................................................................................................A-128
A.2.107 NP1_MANUAL_STOP................................................................................................................A-129
A.2.108 NP1_SW_FAIL............................................................................................................................A-130
A.2.109 NP1_SW_INDI.............................................................................................................................A-131
A.2.110 OPM_FAIL...................................................................................................................................A-132
A.2.111 PORT_MODULE_OFFLINE......................................................................................................A-133
A.2.112 POWER_ALM.............................................................................................................................A-134
A.2.113 POWER_FAIL.............................................................................................................................A-135
A.2.114 P_AIS...........................................................................................................................................A-136
A.2.115 P_LOS..........................................................................................................................................A-137
A.2.116 PS..................................................................................................................................................A-138
A.2.117 R_F_RST......................................................................................................................................A-139
A.2.118 R_LOC.........................................................................................................................................A-140
A.2.119 R_LOF..........................................................................................................................................A-142
A.2.120 R_LOS..........................................................................................................................................A-143
A.2.121 R_S_ERR.....................................................................................................................................A-145
A.2.122 RADIO_MUTE............................................................................................................................A-146
A.2.123 RADIO_RSL_HIGH....................................................................................................................A-148
A.2.124 RADIO_RSL_LOW.....................................................................................................................A-149
A.2.125 RADIO_TSL_HIGH....................................................................................................................A-151
A.2.126 RADIO_TSL_LOW.....................................................................................................................A-151
A.2.127 RELAY_ALARM........................................................................................................................A-152
A.2.128 RP_LOC.......................................................................................................................................A-153
A.2.129 RS_CROSSTR.............................................................................................................................A-154
A.2.130 S1_SYN_CHANGE.....................................................................................................................A-155
A.2.131 SYN_BAD....................................................................................................................................A-156
A.2.132 SYNC_C_LOS.............................................................................................................................A-157
A.2.133 T_ALOS.......................................................................................................................................A-158
A.2.134 T_F_RST......................................................................................................................................A-159
A.2.135 T_FIFO_E.....................................................................................................................................A-160
A.2.136 T_LOC..........................................................................................................................................A-161
A.2.137 T_LOS..........................................................................................................................................A-163
A.2.138 TEMP_ALARM...........................................................................................................................A-164
A.2.139 TU_AIS........................................................................................................................................A-165
A.2.140 TU_AIS_VC12.............................................................................................................................A-167
A.2.141 TU_AIS_VC3...............................................................................................................................A-168
A.2.142 TU_LOP.......................................................................................................................................A-170
A.2.143 TU_LOP_VC12............................................................................................................................A-171
A.2.144 TU_LOP_VC3..............................................................................................................................A-172
A.2.145 UP_E1_AIS..................................................................................................................................A-173
A.2.146 VCAT_LOA.................................................................................................................................A-175
A.2.147 VCAT_LOM_VC12.....................................................................................................................A-176
A.2.148 VCAT_LOM_VC3.......................................................................................................................A-177
A.2.149 VCAT_SQM_VC12.....................................................................................................................A-178
A.2.150 VCAT_SQM_VC3.......................................................................................................................A-179
A.2.151 VOLT_LOS..................................................................................................................................A-181
A.2.152 WRG_BD_TYPE.........................................................................................................................A-183
A.2.153 WRG_DEV_TYPE.......................................................................................................................A-184
A.2.154 WS_LOS.......................................................................................................................................A-184
A.2.155 W_R_Failure................................................................................................................................A-186
A.2.156 XCP_INDI....................................................................................................................................A-186
A.2.157 XPIC_LOS...................................................................................................................................A-187
C Alarm Management.................................................................................................................C-1
C.1 NE Alarm Management.................................................................................................................................C-1
C.2 Board Alarm Management.............................................................................................................................C-1
C.2.1 Setting the Alarm Level........................................................................................................................C-1
C.2.2 Alarm Suppression................................................................................................................................C-1
C.2.3 Alarm Auto-Report...............................................................................................................................C-1
C.2.4 Alarm Reversion...................................................................................................................................C-2
C.2.5 Setting Bit Error Alarm Threshold.......................................................................................................C-2
C.2.6 AIS Insertion.........................................................................................................................................C-3
C.2.7 UNEQ Insertion....................................................................................................................................C-4
Figures
Tables
Purpose
This document is a maintenance guide of the OptiX RTN 600–based IDU 610/620. It also
contains details of alarms and performance events for reference purpose.
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document is intended for the maintenance engineers of the OptiX RTN 600. Before reading
this document, you need to:
l Know microwave communication basics.
l Know the basics of the OptiX RTN 600 product.
Organization
This document is organized as follows.
Chapter Content
1 Safety Describes parts of the safety precautions. Read and follow these safety
Precautions precautions before installing, commissioning, and maintaining the
OptiX RTN 600.
A Alarm Reference Describes all the possible alarms and clearing procedures of the OptiX
RTN 600.
B Performance Describes all the performance events and clearing procedures of the
Event Reference OptiX RTN 600.
C Alarm Describes the alarm management function of the OptiX RTN 600.
Management
E Alarm Describes the alarm suppression relation of the OptiX RTN 600.
Suppression
Relation
G Acronyms and Lists the acronyms and abbreviations used in this document.
Abbreviations
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Indicates a tip that may help you solve a problem or save time.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are in
boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Mouse Operation
The 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 without
moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain
position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
1 Safety Precautions
CAUTION
Before performing any operation, go through the instructions and precautions carefully to
minimize the possibility of accidents. The Caution, Warning and Danger items in other
documents do not cover all the safety precautions that must be followed. They are only
supplements to the safety precautions for operations as a whole. The personnel in charge of the
installation and maintenance must be trained to learn the proper operating methods and all safety
precautions. Only the trained and qualified personnel can install or maintain the device.
When operating the device, abide by the local safety regulations. The precautions listed in this
chapter are in compliance with the local safety regulations.
When operating the Huawei device, follow the full precautions and special safety instructions
from Huawei.
The personnel in charge of installation and maintenance must understand the basics of the safety
operations. Only trained and qualified personnel can install or maintain the device.
High Voltage
DANGER
l The high voltage power supply supplies power for the device operation. Direct or indirect
contact (through damp objects) with high voltage and AC mains supply may result in fatal
accident.
l Non-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
cables through a certain area. The personnel who perform high voltage operations must be
qualified for performing high voltage and AC operations.
l Do not wear conducting articles, such as watches, chains, bracelets and rings while
performing high voltage operations.
l Switch off the power supply immediately if you find water in the rack or if the rack is damp.
l Make sure that the device is kept away from water when being operated in a damp
environment.
Power Cable
DANGER
l Do not install or remove a live line. Transient contact between the core of the power cable
and the conductor might generate electric arc or spark, which can cause fire or damage to the
human body.
l During high voltage and AC operations, special tools must be used instead of common tools.
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 to
the requirements of the actual installation.
Thunderstorm
DANGER
High voltage and AC operations, or operations on a steel tower and a mast on a thunderstorm
day are prohibited.
On a thunderstorm day, the electromagnetic field generated in the thunderstorm area may cause
damage to electronic parts. To prevent the device from being damaged by lightning, use proper
grounding.
Electrostatic Discharge
CAUTION
The static electricity generated by the human body can damage the electrostatic sensitive
components on the circuit board, such as the large-scale integrated circuit (LIC).
Electrostatic discharge (ESD) is caused by body movement, friction between shoes and floor,
friction between clothes, and contact with plastic objects. ESD remains in the human body for
a long time.
Before touching the device or holding the boards, circuit boards, or ASICs, wear a grounded
ESD wrist strap. It can prevent the sensitive components from being damaged by the static
electricity in the human body.
Microwave
WARNING
Strong radio frequency can harm the human body.
Do not stay too close to the antenna in the emitting direction of the antenna when the microwave
communication equipment is working. Before installing or maintaining an antenna in a steel
tower or a mast with a large number of transmitter antennas, the operator should coordinate all
parties concerned to shut down the transmitter antennas.
Laser
WARNING
Laser radiation can cause injury to your eyes.
When handling optical fibers, do not stand close to or look into the optical fiber outlet directly
with naked eyes.
High Temperature
WARNING
When the ambient temperature is higher than 55℃, the surface temperature of the IDU boards
may exceed 70℃. In this case, wear protective gloves before touching the IDU boards.
Working at Heights
WARNING
When working at heights, prevent objects from falling down.
DANGER
During hoisting heavy objects, do not stand or walk under the boom or the objects.
Sharp Objects
WARNING
When carrying the device with hands, wear protection gloves to avoid injuries caused by sharp
objects.
IF Cable
WARNING
Before installing or removing the IF cable, turn off the ODU-PWR power switch on the IF board.
CAUTION
l When inserting a board, handle it gently to avoid distorting the pins on the backplane.
l Insert the board along the slot guide. Do not allow the board interfaces to come in contact
with that of another board as this can cause short-circuit or can damage the board.
l When holding a board in hand, do not touch the board circuit, components, connectors, or
the connection slots.
CAUTION
Bundle the signal cables separately from the strong current cables or high voltage cables. The
space between two adjacent ties must be at least 150 mm.
The aim of routine maintenance is to detect and rectify hidden faults in time before the equipment
becomes faulty and services are affected.
2.2.7 Testing the IF 1+1 Switching Half a year Applies only to the
equipment that is configured
in 1+1 protection mode.
During the 1+1 protection
switching (< 500 ms),
protection services are
interrupted. Hence, you are
recommended to carry out 1
+1 protection switching
when the traffic is light.
2.2.8 Testing the IF N+1 Switching Half a year Applies only to the
equipment that is configured
in N+1 protection mode.
2.2.9 Testing the Two-Fiber Bidirectional Half a year Applies only to the
MSP Ring Switching equipment that is configured
in two-fiber bidirectional
MSP.
2.3.7 Testing the IF 1+1 Switching Half a year Applies only to the
equipment that is configured
in 1+1 protection mode.
During the 1+1 protection
switching (< 500 ms),
protection services are
interrupted. Hence, you are
recommended to carry out 1
+1 protection switching
when the traffic is light.
2.3.8 Testing the IF N+1 Switching Half a year Applies only to the
equipment that is configured
in N+1 protection mode.
2.3.9 Testing the Two-Fiber Bidirectional Half a year Applies only to the
MSP Ring Switching equipment that is configured
in two-fiber bidirectional
MSP.
2.4.1 Cleaning the Two months Only for the IDU 620a
Air Filter
2.4.2 Testing the Two months Only if that the equipment is equipped with
Orderwire Phone the orderwire phone
2.4.3 Checking the Two months Only if that the equipment is installed indoors
Equipment Room
NOTE
a: If the IDU 620 is installed in an outdoor dust-proof cabinet, the IDU is not installed with an air filter.
2.5.1 Checking the Half a year Carry out a complete check after a level-8 or
ODU higher hurricane, an earthquake, or other
exceptional circumstances.
2.5.2 Checking the Half a year
Hybrid Coupler
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Log in to the Web LCT, open the NE List window, and check the Communication Status
column of a specific NE.
The Communication Status column should be Normal.
Step 2 If the Login Status column of a specific NE is Not Logged In, log in to the NE.
1. Right-click the NE, and choose NE Login from the shortcut menu.
The system displays the NE Login dialog box.
2. Specify User Name and Password.
l The user name is lct by default.
l The password for user lct is password by default.
NOTE
Step 5 Check the running status of the boards by referring to the legend description.
If a board is running normally, it should be green.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and click the icon in the toolbar.
NOTE
You can also click an alarm indicator on the toolbar to display the alarms of the specific severity.
From left to right, the alarm indicators and related alarm severities are as follows:
l Red: critical alarm
l Orange: major alarm
l Yellow: minor alarm
l Purple: warning
l Light blue: abnormal event
Step 3 If there are newly generated alarms after the last maintenance, select the newly generated alarms,
record the details of the alarms, and notify the troubleshooting personnel for clearing the alarms
in time.
For details about how to handle alarms, refer to "A Alarm Reference".
----End
Related Information
A current alarm is an alarm that is not cleared.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer, and click the icon in the toolbar.
Step 4 Specify Start Time and End Time, and then click Filter.
The start time should be the time when the last history alarm browsing operation was performed,
and the end time should be the current time.
The system displays the text file that lists the history alarms.
NOTE
----End
Related Information
A history alarm is an alarm that has been cleared. An NE stores a maximum of 1,000 history
alarms.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Select an NE from the NE Explorer, and choose Alarm > Browse Abnormal Events from the
Function Tree.
TIP
Alternatively, you can select an NE and then click the icon to switch to the Browse Abnormal
Events tab page.
----End
Related Information
An abnormal event is an abnormality that arises in the system at a particular time and not an
abnormality that persists for a long time. Being different from alarms, an abnormal event has
only occurrence time, with clearance time not provided.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The performance monitoring function must be enabled.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Select a specific board from the NE Explorer, and choose Performance > Current
Performance from the Function Tree.
Step 4 Select all the available performance events in Count, and select Display Continuous Severely
Errored Second in Display Options.
Step 7 Select all the available performance events in Gauge, and select Current Value and Maximum/
Minimum Value in Display Options.
Step 11 Repeat Step 4 to Step 9 to query the current performance events in a period of 24 hours.
----End
Related Information
The counter of current performance events measures all the performance events that arise
between the start time of the monitoring period and the current time.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The performance monitoring function must be enabled.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Select a specific board from the NE Explorer, and choose Performance > History
Performance from the Function Tree.
Step 2 Select All in Monitored Object Filter Condition.
Step 3 Select 15-Minute after Monitor Period.
Step 4 Specify the start time and end time of a specific time span. The time span starts from the time
when the last history performance event browsing operation was performed to the current time.
Step 5 Select all the available performance events in Count, and select Display Continuous Severely
Errored Second in Display Options.
Step 6 Click Query to browse the history performance events.
Step 7 Click Save As.
The system displays the text file that lists the history performance events. You can save the text
file as required.
Step 8 Select all the available performance events in Gauge, and select Current Value and Maximum/
Minimum Value in Display Options.
Step 9 Click Query to browse the history performance events.
Step 10 Click Save As to save the performance events.
The system displays the text file that lists the history performance events.
NOTE
----End
Related Information
A history performance event is a performance event where the monitor period ends in the past.
In the case of history performance events, an NE has only six 24-hour registers and sixteen 15-
minute registers for each performance indicator. Therefore, only the six most recent non-zero
24-hour performance events and the sixteen most-recent non-zero 15-minute performance events
can be obtained from the NE.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
l The IF 1+1 switching performed manually is a HSB switching. During the 1+1 protection
switching (< 500ms), protection services are interrupted. Hence, you are recommended to
carry 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 > Link Configuration from
the Function Tree.
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 to
Protection from the shortcut menu.
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 9 In Slot Mapping Relation, right-click the IF board, and choose Clear from the shortcut menu.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
l This task helps to check whether an NE implements the N+1 protocol properly and is
designed only for test. Therefore, the service is not switched over.
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 > Link Configuration from
the Function Tree.
Step 2 Select N+1 Protection tab.
Step 3 In Slot Mapping Relation, right-click a working unit, and choose Exercise switching from the
shortcut menu.
The system displays a prompt message indicating that the switching command is issued
successfully.
Step 4 Click OK.
Step 5 Click Query to check the protection switching status.
The status of the working unit should be Exercise switching.
Step 6 Repeat Step 1 to Step 2.
Step 7 In Slot Mapping Relation, right-click the protection unit or a working unit, and choose Clear
from the shortcut menu.
Step 8 Click OK.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
l This task helps to check whether an NE implements the MSP protocol properly and is
designed only for test. Therefore, the service is not switched over.
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 Object Tree in the NE Explorer, and choose Configuration > Ring
MSP from the Function Tree.
Step 2 In Protection Group, select the protection group that is to be switched over.
Step 3 In Slot Mapping Relation, right-click East Line, and choose Exercise switching from the
shortcut menu.
Step 4 Click OK to query the status of protection switching. The Switching Status of the east line
board should be Excise ring switching.
Step 5 Right-click the selected line, and choose Clear excise ring switching from the shortcut menu.
Step 6 Click OK to query the status of protection switching. The Switching Status of the east line
board should be Normal.
Step 7 In Slot Mapping Relation, right-click West Line of the protection group selected in Step 2,
and choose Excise ring switching from the shortcut menu.
Step 8 Repeat Step 4 to Step 6.
----End
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 Log in to the T2000 system, and check the color of the NE icon.
TIP
In the toolbar of the main view, click the icon, and select the Legend tab in the displayed window.
By moving the vertical scrolling bar, you can view all the status legends of the NE.
The NE icon should be green. In other cases, you can infer as follows:
l If the NE icon is gray, you can infer that the NE loses communication with the T2000.
l If the NE icon is light blue, you can infer that the NE status is unknown.
l If the NE icon is red, you can infer that a critical alarm is generated.
l If the NE icon is orange, you can infer that a major alarm is generated.
l If the NE icon is yellow, you can infer that a minor alarm is generated.
l If the NE icon is purple, you can infer that a warning is generated.
l If the NE icon is deep blue, you can infer that an alarm is generated but not reported.
Step 5 Check the running status of the boards by referring to the legend description.
If a board is running normally, it should be green.
----End
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 On the T2000, choose Fault > Browse Current Alarms from the main menu.
Step 2 Select one or multiple NEs from the left pane, and click .
All the alarms of the selected NE or NEs are displayed in Browse Current Alarms.
Step 3 Select Auto Refresh.
Step 5 Select the newly generated alarms, record the details of the alarms, and click OK.
Step 6 Notify the fault handling personnel of the alarms in a timely manner.
For details about how to handle alarms, refer to “A Alarm Reference”.
----End
Related Information
A current alarm is an alarm that is not cleared.
You can browse the network-wide alarms based on alarm severity by clicking the alarm
indicators in the upper right corner.
l The number to the right side of each indicator indicates the number of network-wide alarms of the specific
severity.
l If a square frame is displayed around an alarm indicator, you can infer that there are unacknowledged alarms.
Prerequisite
The NE user has the authority of monitor level or higher.
Procedure
Step 1 On the T2000, choose Fault > History Alarm Browse from the main menu.
Step 2 Select one or multiple NEs from the left pane, and click .
All the history alarms of the selected NE or NEs are displayed in History Alarm Browse.
Step 3 Click Filter.
The Filter dialog box is displayed.
Step 4 After specifying Start Time and End Time, click Filter.
The start time should be the time when the last history alarm browsing operation was performed,
and the end time should be the current time.
Step 5 Browse the alarms that are displayed.
Step 6 Click Save as to the history alarms as required.
----End
Related Information
A history alarm is an alarm that has been cleared.
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 On the T2000, choose Fault > Browse Abnormal Events from the main menu.
Step 2 Select one or multiple NEs from the left pane, and click .
All the abnormal events of the selected NE or NEs are displayed in Browse Abnormal
Events.
Step 3 Browse the abnormal events.
Step 4 Optional: Click Save as to save the abnormal events as required.
----End
Related Information
An abnormal event is an abnormality that arises in the system at a particular time rather than
persists for a period. Being different from alarms, an abnormal event has only occurrence time,
with clearance time not provided.
Prerequisite
l The T2000 is in normal communication with the NE.
l The performance monitoring function must be enabled.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 On the T2000, choose Performance > Browse SDH Performance from the main menu, and
than select Current Performance Data.
Step 2 Select one or multiple NEs from the left pane, and click .
Step 5 Select Count, select Select All in the tab page that is displayed, and select Consecutive Severely
Errored Seconds in the right pane.
Step 7 Select Gauge , select Select All in the tab page that is displayed, and select Current Value and
Maximum/Minimum Value in the right pane.
Step 9 Re-define the time span by setting Monitor Period to 24-Hour, and leave other fields
unchanged.
Step 10 Repeat Step 5 to Step 8 to query the performance events in a period of 24 hours.
----End
Related Information
The counter of current performance events measures all the performance events that arise
between the start time of the monitoring period and the current time.
Prerequisite
l The performance monitoring function must be enabled.
l The NE user has the authority of monitor level or higher.
Procedure
Step 1 On the T2000, choose Performance > Browse SDH Performance from the main menu, and
than select the History Performance Data tab.
Step 2 Select one or multiple NEs from the left pane, and click .
Step 5 Specify the start time and end time of a specific time span.
The time span starts from the time when the last history performance event browsing operation
was performed to the current time.
If this is the first browsing operation, you should select Query from NE and Save to Database. Otherwise,
you should select Query from T2000. In this case, the history performance databases of the T2000 and
NE are synchronized.
Step 7 Select the Count tab page, and then select Select All.
Step 10 Select Gauge, select Select All in the tab page that is displayed, and select Current Value and
Maximum/Minimum Value in the right pane.
Step 14 Repeat Step 5 to Step 12 to browse the history performance events in a period of 24 hours.
----End
Related Information
For history performance events, an NE has only six 24-hour registers and sixteen 15-minute
registers for each performance indicator. Therefore, only the six most recent non-zero 24-hour
performance events and the sixteen most-recent non-zero 15-minute performance events can be
obtained from the NE. The T2000, however, automatically stores the history data reported by
NEs. Therefore, you can obtain the performance data generated in the last months.
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Precautions
l The IF 1+1 switching performed manually is a HSB switching. During the 1+1 protection
switching (< 500ms), protection services are interrupted. Hence, you are recommended to
carry 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 > Link Configuration from
the Function Tree.
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 to
Protection from the shortcut menu.
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 9 In Slot Mapping Relation, right-click the IF board, and choose Clear from the shortcut menu.
Step 12 After the equipment runs properly for some time, query the current alarms and performance
events.
There should be no new alarms or performance events.
----End
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
l This task helps to check whether an NE implements the N+1 protocol properly and is
designed only for test. Therefore, the service is not switched over.
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 > Link Configuration from
the Function Tree.
Step 3 In Slot Mapping Relation, right-click a working unit, and choose Exercise switching from the
shortcut menu.
The system displays a prompt message indicating that the switching command is issued
successfully.
Step 7 In Slot Mapping Relation, right-click the protection unit or a working unit, and choose Clear
from the shortcut menu.
----End
Prerequisite
l The T2000 is in normal communication with the NE.
l The NE user has the authority of monitor level or higher.
Precautions
l This task helps to check whether an NE implements the MSP protocol properly and is
designed only for test. Therefore, the service is not switched over.
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 Object Tree in the NE Explorer, and choose Configuration > Ring
MSP from the Function Tree.
Step 2 In Protection Group, select the protection group that is to be switched over.
Step 3 In Slot Mapping Relation, right-click East Line, and choose Exercise switching from the
shortcut menu.
Step 4 Click OK to query the status of protection switching. The Switching Status of the east line
board should be Excise ring switching.
Step 5 Right-click the selected line, and choose Clear excise ring switching from the shortcut menu.
Step 6 Click OK to query the status of protection switching. The Switching Status of the east line
board should be Normal.
Step 7 In Slot Mapping Relation, right-click West Line of the protection group selected in Step 2,
and choose Excise ring switching from the shortcut menu.
----End
Prerequisite
None.
Procedure
Step 1 Loosen the captive screws on the panel of the fan box.
Step 2 Move the cables away from the front of the panel of the fan box.
Step 4 Use an air blower or a clean brush to clean the air filter.
Step 5 After the cleaning, insert the air filter back to its original position.
----End
Prerequisite
l The NE has been correctly installed with an orderwire phone.
l The orderwire data has been correctly configured.
Procedure
Step 1 Check the status of the orderwire phone.
The orderwire phone should meet the following requirements:
l The ringing switch is set to position ON.
l The dialing mode switch is set to position T, which indicates the dual tone multi-frequency
mode.
Step 2 Make orderwire calls.
1. Place the orderwire phone off the hook, and press the "TALK" button.
The red indicator on the front of phone set should be lit and you can hear the dialing prompt
tone.
2. Make orderwire calls to other NEs.
The calls should be normal and the voice should be clear.
Step 3 Receive orderwire calls.
1. The maintenance personnel of other NEs make calls to the orderwire phone.
The phone should ring.
2. Place the orderwire phone off the hook, press the "TALK" button, and have a conversation.
The red indicator on the front of the phone set should be lit. The call should be normal and
the voice should be clear.
----End
Prerequisite
None.
Procedure
Step 1 Record the reading of the thermometer in the equipment room.
Step 2 Record the reading of the humidity meter in the equipment room.
The normal humidity should be between 5% and 95%.
Step 3 Check whether the equipment room meets the disaster protection requirements.
Ensure the following points:
l There should be portable foam fire extinguishers in the equipment room. The fire
extinguishers should be in their service life.
l There should be no rain leakage or water penetration in the equipment room.
l There should be no mice or insects in the equipment room.
----End
Prerequisite
None.
Procedure
Step 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° under
it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester
protects the area that is located within an angle of 30° under it.
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
Prerequisite
None.
Procedure
Step 1 Ensure that the coupler 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° under
it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester
protects the area that is located within an angle of 30° under it.
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
Prerequisite
None.
Procedure
Step 1 Ensure that the antenna 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° under
it. For mountainous areas and the areas where lightning frequently occurs, the lightning arrester
protects the area that is located within an angle of 30° under it.
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 slants
from the original position. Ensure that the azimuth angle and the elevation angle of the antenna
meet 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
Prerequisite
None.
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.
----End
NOTE
In the case of emergency events, the customers in China can contact our 24-hour technical support center at
400-830-2118, and the customers in areas outside China can contact the local Huawei offices.
Start
Yes
Maloperation? Cancel the operation
No
2
Contact related
Service interrupted by Yes
departments to handle
external causes?
the problem
No
3
Query NE status and alarms
by using the T2000
4
NE access successful Yes
Handle the alarm
and alarms cleared?
No
No
Rectify the fault on site Go to the next step Service restored?
5
Yes
Check the fault handling
result
End
② Faults that occur due to external causes, such as faults of the power supply,
cables, environment, and terminal equipment (such as switching devices).
Start
No
1
No Handle the power
PWR indicator of
input alarm
PXC lights?
Yes
2
Browse alarms
by using the
Web LCT
3
Equipment Yes
Handle the alarm
alarm?
No
4
Yes
Line alarm? Handle the alarm
No
5
High order Yes
Handle the alarm
path alarm?
No
6
Low order Yes
Handle the alarm
path alarm?
No
SDH/PDH
7
Yes
interconnection Handle the fault
fault?
No
8
Ethernet Yes
Handle the fault
service fault?
No
Locate fault by using
section-by-section No
loopback Go to the next step Service restored?
Yes
End
Comment Description
No.
4 Troubleshooting Guide
This guide describes the general troubleshooting procedures for the OptiX RTN 600 and provides
troubleshooting methods for common faults.
If orderwire calls cannot get through when services are normal, there is an orderwire fault.
Start
2 Yes
Caused by external factors? Other handling procedures
3 No
Analyze fault causes and locate
the fault
4 No
Report to Huawei
No
Is the service restored?
Yes
No
Is the fault cleared?
Yes
End
Note Description
① When recording the fault phenomenon, make a true and detailed record of the
entire process of the fault. Record the exact time when the fault occurs, and
the operations performed before and after the fault occurs. Save the alarms,
performance events, and other important information.
② Faults that are caused by external factors include power failures, fiber faults,
environmental faults, and terminal equipment (such as switching equipment)
faults.
Fault Causes
l There are incorrect operations.
The data is wrongly modified. A board or cable is looped back or replaced.
l The transmission NE or link is faulty.
l There is an interconnection fault.
If the transmission equipment and connections are working normally, check whether there
is a fault in the interconnection between the transmission equipment and the switching
equipment.
CAUTION
If the fault cannot be rectified in a short time, first restore the services. Adjust the service routes
or perform a forced switching operation to restore the services.
Start
Yes
Maloperation? Cancel the operation
No
2
Contact related
Service interrupted Yes
departments to handle
by external causes?
the problem
No
3
Query NE status and alarms
by using the T2000
4
NE access successful Yes Handle the alarm
and alarms cleared?
No
No
Rectify the fault on site Go to the next step Service restored?
Yes
End
② Faults that occur due owing to external causes, such as faults of the power
supply, cables, environment, and terminal equipment (such as switching
devices).
Start
No
1
No Handle the power
PWR indicator of
input alarm
PXC lights?
Yes
2
Browse alarms
by using the
Web LCT
3
Equipment Yes
Handle the alarm
alarm?
No
4
Yes
Line alarm? Handle the alarm
No
5
High order Yes
Handle the alarm
path alarm?
No
6
Low order Yes
Handle the alarm
path alarm?
No
SDH/PDH
7
Yes
interconnection Handle the fault
fault?
No
8
Ethernet Yes
Handle the fault
service fault?
No
Locate fault by using
section-by-section No
loopback Go to the next step Service restored?
Yes
End
Comment Description
No.
The key to locating a microwave link fault is to check whether the transmit power and the receive
power 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 transmit
power exceeds the range that the ODU supports. The second case is that the difference between
the transmit power and the set value is more than 2 dB when the ATPC is disabled. The relevant
alarms 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 600 Radio Transmission
System Product Description.
In the following two cases, the RSL is abnormal. The one case is that the receive power is under
the lower threshold of the planned RSL. The second case is that the receive power is lower than
the receiver sensitivity or higher than the free space receive power due to fading. 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 detailed description of the receiver sensitivity, refer to the OptiX RTN 600 Radio Transmission System
Product Description.
Generally, external interference is classified into co-channel interference and adjacent channel
interference.
l Co-channel interference is crosstalk from two different radio transmitters reusing the same
frequency channel. Therefore, the entire spectrum may be impaired.
l Adjacent channel interference is signal impairment to one frequency due to presence of
another 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 microwave
link may be faulty in one direction only.
Fault Causes
The receive power is always l The antenna direction is not properly adjusted.
lower than the ideal value. l The antennas have different polarization directions.
l There is a mountain or obstacle in the transmit direction.
l The performance of the feeder degrades.
NOTE
Start
1 Yes
Is there a wrong
Cancel the operation
operation?
No
No
3
No
Normal transmit power? Handle the fault
Yes
4
The receive power Yes
always lower than the Handle the fault
ideal value?
No
5
Abnormal receive Yes
power caused by slow up- Handle the fault
fading?
No
6
Abnormal receive Yes
power caused by slow Handle the fault
down-fading?
No
7
Abnormal receive Yes
power caused by fast Handle the fault
fading?
No
8
Microwave link Yes
fault in one Handle the fault
direction?
No
9
No
Perform loopback operations Go to the next step Is the fault cleared?
Yes
End
Note Description
Note Description
The line board detects RS bit errors by the RS overhead byte B1. Related alarms and performance
events are listed below:
l B1_EXC
l B1_SD
l RS_CROSSTR
l RSBBE
l RSES
l RSSES
l RSCSES
l RSUAS
NOTE
When the IF board works in the PDH mode, the above RS bit error alarms and performance events may also be
reported. Such alarms and performance events are detected by the B1 that is defined in the PDH microwave
frame.
The line board detects MS bit errors by the MS overhead byte B2. Related alarms and
performance events are listed below:
l B2_EXC
l B2_SD
l MS_CROSSTR
l MSBBE
l MSES
l MSSES
l MSCSES
l MSUAS
The line board detects HP bit errors by the HP overhead byte B3. Related alarms and performance
events are listed below:
l B3_EXC
l B3_SD
l HP_CROSSTR
l HPBBE
l HPES
l HPSES
l HPCSES
l HPUAS
LP bit errors are detected by PDH service processing boards or Ethernet service processing
boards using the VC-3 overhead byte B3 or VC-12 overhead byte V5. Related alarms and
performance events are listed below:
l B2_EXC
l B2_SD
l B3_EXC_VC3_
l B3_SD_VC3
l BIP_EXC
l BIP_SD
l LP_CROSSTR
l VC3BBE
l VC3ES
l VC3SES
l VC3CSES
l VC3UAS
l LPBBE
l LPES
l LPSES
l LPCSES
l LPUAS
Fault Causes
There are only LP bit errors. l The PDH service processing board or the Ethernet service
processing board is faulty.
l The cross-connect unit is faulty.
l The working temperature of the PDH service processing
board or the Ethernet service processing board is
excessively high.
l The working temperature of the cross-connect unit is
excessively high.
l There is power surge or an external interference source, or
the equipment is not properly grounded.
Start
2
1
Is there an Yes
Handle the alarm
equipment alarm?
No
SDH optical 3
No interface board Handle the RS bit error of the
SDH optical interface board
4
Is there an If the
Yes IF board Handle the RS bit error of the
RS bit error alarm or a alarming
performance IF board
board is
event?
5
STM-1 electrical
No Handle the RS bit error of the
interface board
STM-1 electrical interface
board
6
Is there an
MS/HP alarm or a Yes
Handle the MS/HP bit error
performance
event?
No
7
Yes
Is there an LP alarm? Handle the LP bit error
No
Go to the next No
Is the fault cleared?
step
End
Note Description
Note Description
When the position of the first byte of the VC-4 in the AU-4 payload changes, the AU pointer
makes a justification accordingly. The performance events of the AU pointer justification are as
follows:
l AUPJCHIGH
l AUPJCLOW
l AUPJCNEW
NOTE
The AU pointer justification is generated at an upstream NE but is detected and reported at a downstream NE.
When the service is configured to be at the VC-12 level, apply the re-framing process to terminate
the AU pointer justification. The terminating method is to transform the AU pointer justification
into the TU pointer justification. The performance events of the TU pointer justification are as
follows:
l TUPJCHIGH
l TUPJCLOW
l TUPJCNEW
NOTE
The TU pointer justification is generated at the NE where the AU pointer is transformed into the TU pointer,
but is detected and reported by the tributary board of the NE where services are terminated.
Fault Causes
l The clock sources or the clock source levels are wrongly configured. As a result, there are
two clock sources in the same network or mutual clock tracing occurs.
l The optical fibers links are wrongly connected. As a result, mutual clock tracing occurs.
l The quality of the clock source degrades, the clock unit is faulty, or there are other clock
related faults.
l The tributary board is faulty (only for the TU pointer justification).
Start
No
2
Check the clock
configuration
No
3
Yes
Wrongly connected? Re-connect the fiber
No
4 5
Is there an AU pointer Yes Find the NE whose clock is
out of synchronization Locate the faulty board
justification event?
No
6 7
No
No
Go to the next step Is the fault cleared?
Yes
End
③ Query ECC routes to check if the fibers are correctly connected. Check the fiber
connection in the east and west directions of the NE that reports the pointer
justification event.
Note Description
⑦ Replace the possibly faulty boards. For a TU pointer justification, check the line
board, the clock board, and the tributary board.
Fault Causes
l The VC-12 numbering method of the OptiX equipment is different from the numbering
method of the equipment of certain vendors.
The OptiX equipment applies the timeslot numbering method. The numbering formula is:
VC-12 number = TUG-3 number + (TUG-2 number - 1) x 3 + (TU-12 number - 1) x 21.
This method is also called ordering method.
Some equipment applies the line numbering method. The numbering formula is: VC-12
number = (TUG-3 number - 1) x 21 + (TUG-2 number - 1) x 3 + TU-12 number. This
method is also called interval method.
When the interconnected equipment is the ATM or Ethernet equipment, the common cause for the
interconnection fault is that the service is not set to the VC-4 pass-through service. As a result, the overheads
are processed in the terminating mode instead of the pass-through mode.
Figure 4-7 Flow of troubleshooting the interconnection with the SDH equipment
Start
Is the
Set the interconnection
interconnected equipment Yes
service to be the VC-4 pass-
the ATM/IP equipment?
through service
No
Query the VC-12 numbering
method of the interconnected
equipment
No
No
2
3 No
End
Fault Causes
l There is an impedance mismatch between interfaces.
l The equipment is not properly grounded.
l The cable performance degrades.
l The indexes of PDH interfaces do not meet the requirements.
Figure 4-8 Flow of troubleshooting the interconnection with the PDH equipment
Start
1
Check the impedance of
the interfaces
No
2
Is the cable the Yes
Check the grounding
coaxial cable?
No
3
No
Is in good conditions? Adjust the cables
4 Yes
Test the indexes of
interfaces
Yes
Handle the faults of the
local equipment
End
① Check whether the type of the tributary board matches the type of the cable.
network speed is low, the equipment delay is long, loss of packets occurs, or incorrect packets
exist in the received or transmitted data.
Fault Causes
l There human-caused faults are as follows:
– An Ethernet board loopback or a transmission line loopback occurs.
– The settings of parameters of an Ethernet port such as port enabled, working mode, and
flow control are different from those of its interconnected equipment.
– The configuration of the encapsulation/mapping protocol or the LCAS protocol is
different from that of the opposite equipment.
– The VCTRUNK-bound timeslot is different from that of the opposite equipment.
– The service configuration is incorrect.
l The equipment faults are as follows:
– The line board is faulty or has bit errors.
– The interconnected equipment is faulty.
– The network cable is faulty.
– The external electromagnetic interference is severe.
Start
1
Yes
Incorrect operation? Roll back this operation.
No
2
Equipment Yes
or line alarm? Handle the alarm.
No
3
Yes
Ethernet interface Handle the alarm.
alarm?
No
4
Yes
Ethernet protocol Handle the alarm.
alarm?
No
5
Abnormal RMON Yes Troubleshoot according to
performance? the flow of handling the
RMON performance event.
No
No
Troubleshoot equipment
Proceed No Are faults
faults by performing
with the cleared?
loopbacks section by
next step.
section or replacing boards.
Yes
End
Note Description
⑤ For RMON performance events, refer to OptiX RTN 600 Radio Transmission
System Feature Description.
Start
1
Analyze the RMON
performance.
2
Collisions or Yes Check the working
fragements? mode of a port.
No
3
Yes
FCS errors? Handle the fault.
No
4
Yes Handle the flow
PAUSE frame? control problem or
add bandwidths.
No
5
Excessive Yes
broadcast Handle the fault.
packets?
No
No
6
Yes
MTU setting
Modify the MTU value.
errors?
No
Proceed No Are faults
Troubleshoot equipment
with the cleared?
faults by performing
next step.
loopbacks section by
section or replacing boards. Yes
End
Note Description
Fault Causes
l The phone set is incorrectly set.
l The phone line is wrongly connected.
l The orderwire is incorrectly configured.
l The SCC board is faulty.
Start
Is the phone No
Modify the phone setting
correctly set?
Yes
Yes
2
Check the orderwire
configuration
Is the configuration No
Modify the configuration
correct?
3 Yes
Replace the possibly faulty
board
Go to the next No
Is the fault cleared?
step
Yes
End
③ Replace the SCC board and the line board that extracts the orderwire byte to
locate the faulty board.
This topic describes the operations of loopback, resetting, PRBS test over the E1 interface, using
the Ethernet test frame, setting the working state of the ODU, turning on/shutting down the laser,
part replacement, and fiber connector and adapter cleaning that are commonly used in
maintenance.
5.1 Loopback
Loopback is a process in which a signal is sent to the device under test, which then returns the
signal to the originator.
5.2 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 600 supports
cold resetting, warm resetting, and SCC resetting.
5.3 PRBS Test
The PRBS test is an important method for network self-check and network maintenance. In the
absence of a dedicated test tool, you can perform a PRBS test by using the embedded test system
on the PDH interface board.
5.4 Using the Ethernet Test Frames
By using the Ethernet test frames in the OptiX RTN 600, you can check the connectivity of the
VCTRUNK.
5.5 Setting the State of the ODU Transmitter
In the OptiX RTN 600, the state of the ODU transmitter can be mute or unmute. When the
transmitter of the ODU is unmute, the ODU transmits and receives microwave signals. When
the transmitter is mute, the ODU only receives signals.
5.6 Setting the State of the Laser
The laser on the port of the optical interface board transmits optical signals only when the laser
is turned on. You can turn on or shut down the laser through the NM.
5.7 Setting the Automatic Release Function
An NE can automatically release the loopback operation or enable the laser after a default period
of five minutes. You can customize the related settings through the NM.
5.8 Part Replacement
Part replacement is a method frequently used to locate faults. The replacement operation varies
with the part types.
5.9 Cleaning Fiber Connectors and Adapters
The optical connecting components are easily contaminated in the maintenance. The minute dust
particles that can be seen only in the microscope can also affect the quality of optical signals. In
this case, it downgrades the system performance. Hence, clean the fiber connectors or adapters
that are terminated in a timely manner.
5.1 Loopback
Loopback is a process in which a signal is sent to the device under test, which then returns the
signal to the originator.
Loopback is a very important test method. Based on the implementing methods, loopbacks can
be classified into:
l Hardware loopback
Hardware loopback is a loopback implemented by changing the physical connections.
l Software loopback
Hardware loopback is a loopback implemented through software design.
In the IDU 610/620 system, the SDH optical interface board, SDH electrical interface board,
PDH interface board, IF board, and Ethernet board support the loopback function.
Prerequisite
l The Web LCT has a normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
Optical interface inloop is a process where the SDH signal is looped back at the overhead
processing unit towards the backplane.
SDH optical
Backplane interface board
SDH
Optical interface outloop is a process where the SDH signal is looped back at the overhead
processing unit towards the remote equipment.
SDH optical
Backplane interface board
SDH
VC-4 path outloop is a process where the VC-4 signal is looped back at the logic processing unit
towards the remote equipment.
SDH optical
Backplane
interface board
VC-4
VC-4 path inloop is a process where the VC-4 signal is looped back at the logic processing unit
towards the backplane.
SDH optical
Backplane
board
VC-4
Precaution
CAUTION
l Loopback may interrupt the services on the port or the path for which the loopback is
performed.
l A software loopback may be automatically released within a period (five minutes by default).
For details, refer to 5.7 Setting the Automatic Release Function.
Procedure
Step 1 Select SDH optical interface board in the object tree.
Step 3 Select By Function, and select the loopback mode in the drop-down list.
----End
Prerequisite
l The Web LCT has a normal communication with the NE.
l The NE user has the "maintenance level" authority or higher.
Context
For the inloop of the electrical interface, an SDH signal is looped back at the coding/decoding
unit of the board to the backplane.
SDH electrical
Backplane interface board
SDH
For the outloop of the electrical interface, an SDH signal is looped back at the coding/decoding
unit of the board to the remote equipment.
SDH electrical
Backplane
interface board
SDH
For the outloop of the VC-4 path, a VC-4 signal is looped back at the logic processing unit of
the board to the remote equipment.
SDH electrical
Backplane interface board
VC-4
Precaution
CAUTION
l Loopback can interrupt the services on the port or the path for which the loopback is
performed.
l A software loopback may be automatically released within a period (five minutes by default).
For details, refer to 5.7 Setting the Automatic Release Function.
Procedure
Step 1 Select an SDH electrical interface board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Select By Function, and select a loopback mode from the drop-down list.
----End
Prerequisite
l The Web LCT has a normal communication with the NE.
l The NE user has the "maintenance level" authority or higher.
Context
For the tributary inloop, a PDH signal is looped back at the coding/decoding unit of the board
to the backplane.
For the tributary outloop, a PDH signal is looped back at the coding/decoding unit of the board
to the remote equipment.
PDH
For the tributary outloop, a PDH signal is looped back at the coding/decoding unit of the board
to the remote equipment.
PDH
Precaution
CAUTION
Loopback can interrupt the services on the port or the path for which the loopback is performed.
Procedure
Step 1 Select a PDH interface board from the Object Tree.
Step 3 Select By Function, and select Tributary Loopback in the drop-down list.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
IF port inloop is a process where the IF signal is looped back at the modem unit of the board
towards the backplane.
Backplane IF board
IF signal
IF port outloop is a process where the IF signal is looped back at the modem unit of the board
towards the remote equipment.
Backplane IF board
IF signal
Port inloop is a process where the microwave signal is loopbacked at the MUX/DEMUX unit
of the board towards the backplane.
Backplane IF board
Microwave
baseband signal
Port outloop is a process where the microwave signal is loopbacked at the MUX/DEMUX unit
of the board towards the remote equipment.
Backplane IF board
Microwave
baseband
signal
VC-4 path inloop is a process where the VC-4 signal is looped back at the logic processing unit
of the board towards the backplane.
Backplane IF board
VC-4 signal
Precaution
CAUTION
l Loopback may interrupt the services on the port or in the path where the loopback operation
is performed.
l A software loopback may be automatically released within a period (five minutes by default).
For details, refer to 5.7 Setting the Automatic Release Function.
Procedure
Step 1 Select an IF board from the Object Tree in the NE Explorer.
Step 2 Choose the menus from the Function Tree.
Step 3 Select By Function, and then select the loopback mode in the drop-down list.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
A MAC layer inloop is an inloop where the service processing module loops back the Ethernet
physical signals towards the backplane direction through the MAC layer. A PHY layer internal
inloop is an inloop where the interface module loops back the Ethernet frame signals towards
the backplane direction through the PHY layer.
Ethernet service
Backplane
processing board
MAC PHY
VC-3 path inloop is an inloop where the logic processing unit of a board loops back the signals
in a specific VC-3 path towards the backplane direction.
VC-3 path inloop is an inloop where the logic processing unit of a board loops back the signals
in a specific VC-3 path towards the remote equipment.
Ethernet service
Backplane
processing board
VC-3 signal
Precautions
CAUTION
l A loopback operation may interrupt the services on the port or in the path where the loopback
is conducted.
l A loopback in a VC-3 path may be automatically released within a period (five minutes by
default). For details, refer to 5.7 Setting the Automatic Release Function.
Procedure
Step 1 Select an Ethernet processing board from the Object Tree in the NE Explorer.
To Perform... Choose...
Loopback at the PHY Layer, Configuration > Ethernet Interface Management >
Ethernet Interface
Loopback at the MAC Layer, Configuration > Ethernet Interface Management >
Ethernet Interface
Loopback in the VC-3 path Configuration > SDH Interface
To Perform... Choose...
Loopback at the PHY Layer, PHY Loopback
Loopback at teh MAC Layer, MAC Loopback
Loopback in the VC-3 path VC3 Loopback
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
An RF inloop is an inloop where the Diplexer of the ODU loops back the RF signals towards
the IF board direction.
IF board ODU
RF signal
Precautions
CAUTION
Because the loopback over an IF port may cause serious accidents, familiarize yourself with the
following precautions when performing loopback operations:
l During the loopback, the services on the related IF port are interrupted.
l During the loopback, the IF board can handle only the services in the first four VC-12s (IF1A/
IF1B) or the services on the first five E1 ports (IF0A/IF0B). The IFX board does not support
RF loopbak. The IF board in STM-1 mode does not support RF loppback.
l During the loopback, the NE may interfere with the nearby radio communication equipment
of which the receive or transmit frequency is lower than the lowest transmit frequency of the
ODU.
l During the loopback, do not modify the IF port-related or ODU-related parameters.
l If the system is configured with the 1+1 protection, to prevent the switching from occurring
during loopback, perform the forced switching to fix the service on the link where RF
loopback is to be performed before RF loopback is performed.
l During the loopback on an ODU that is configured in 1+1 FD mode, interference may arise
between the active and standby microwave links.
l Some types of ODUs do not support loopback over the RF port.
Procedure
Step 1 Select an ODU from the NE Explorer.
Step 2 Choose Configuration > ODU Interface from the Function Tree.
Step 3 Select By Function, and select RF Loopback from the drop-down list.
----End
5.2 Resetting
Resetting is an important method for handling software faults. The OptiX RTN 600 supports
cold resetting, warm resetting, and SCC resetting.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
CAUTION
Cold resetting causes service interruption because it is similar to the procedure of removing and
inserting a board.
Procedure
Step 1 In the slot layout of the T2000, right-click the board to be cold reset.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
Precautions
During the warm resetting, the running services are not affected.
Procedure
Step 1 In the slot layout of the T2000, right-click the board to be reset.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
During the resetting, protection switching and NMS operations are unavailable although the
running services are not affected.
Procedure
Step 1 In the slot layout of the T2000, right-click the SCC to be reset.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
The PRBS test in the tributary direction can be used to check the connection between the PDH
interface board and the DDF, as shown in Figure 5-19.
PRBS
Transmitter
PRBS
Recevicer
The PRBS test in the cross-connect direction can be used to check the connection between the
PDH interface board and the remote NE, as shown in Figure 5-20.
Transmitter
1 2 3
PRBS
IN
Receiver
Local NE Remote NE
VC4 inloop or
1 2 IF port inloop 3 IF port outloop
port inloop
Transmitter
1 2 3
PRBS
IN
Receiver
Local NE Remote NE
Precautions
CAUTION
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can only be conducted in one path and in one direction.
Procedure
Step 1 Set the loopback. For details, refer to Figure 5-19 and Figure 5-20.
Step 2 Select an PDH board from the Object Tree in the NE Explorer.
Step 3 Choose Configuration > PRBS Test from the Function Tree.
The PRBS Test tab page is displayed.
l The PRBS test supports three time units: one second, 10 minutes, and one hour.
l A maximum of 255 test cycles is permissible for the PRBS test.
Step 9 When Progress in the PRBS Test tab page is displayed as 100%, click Query to check the test
result.
NOTE
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
l The service traffic is encapsulated or mapped by using the GFP method.
Context
For test purposes, the Ethernet board sends, at an interval of about one second, one specific GFP
management frame or one specific Ethernet frame to the peer Ethernet board, which then returns
with a response frame. After receiving the response frame, the Ethernet board at the local end
can determine the connectivity of the VCTRUNK in between.
Test frame
Local Remote
Ehernet Ehernet
board board
Response frame
Precautions
CAUTION
Never use the test frames when the network traffic is heavy.
Procedure
Step 1 Select an Ethernet board from the NE Explorer.
Step 2 Choose Configuration > Ethernet Maintenance > Ethernet Test from the Function Tree.
The Ethernet Test tab page is displayed.
Step 3 Select the port to be tested, click Clear Counters and choose Clear All Counters from the
drop-down list.
Huawei recommends that you choose "Burst mode", and a maximum of 10 frames can be transmitted each
time.
Step 7 Check Counter of Frames Sent and Counter of Received Response of Test Frame.
Test frames are used to check the network connectivity. If some of the test frames are lost but
no alarm is reported on the SDH side, you can infer that the network connectivity is in good
condition. If all the test frames are lost, you can infer that network disconnection arises.
----End
Related Information
If you choose the "Continue" mode, the local port transmits test frames continuously until the
test is disabled.
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Context
When the transmitter of the ODU is unmute, the actual transmit power of the ODU takes the
preset value if the ATPC is disabled. The actual transmit power of the ODU, however, is a little
bit different from the preset value if the ATPC is enabled.
Procedure
Step 1 Select an NE from the NE Explorer.
Step 2 Choose Configuration > Link Configuration from the Function Tree.
Step 4 Click the slot icon of the ODU, and specify TX Status.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Procedure
Step 1 Select an SDH optical interface board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree, and then click the SDH
Interface tab.
Step 3 Select By Function.
----End
Prerequisite
l The Web LCT is in normal communication with the NE.
l The NE user has the authority of maintenance level or higher.
Precautions
NOTE
The PDH interface board does not support the loopback and automatic release functions.
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Automatic Disabling of NE Function from the Function Tree.
----End
SD1, SL1, SL4 5.8.3 Replacing the SDH Optical Interface Board
SLE and SDE 5.8.4 Replacing the SDH Electrical Interface Board
PO1, PH1, PD1, and PL3 5.8.5 Replacing the PDH Interface Board
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist
strap.
Step 2 If the board is connected with cables, remove the cables after marking them.
Step 3 Loosen the screws on the panel of the board.
Step 4 Hold the left and right ejector levers with hands. Push them outwards to disengage the board
from the backplane.
Step 5 Pull out the board gently along the guide rail in the slot. At this time, the board is in a parallel
manner.
CAUTION
Remove the board slowly, to prevent the components on the boards from colliding.
Step 6 Put the removed board into the antistatic box or bag.
----End
Procedure
Step 1 Insert one end of the ESD wrist strap into the ESD connector on the cabinet. Wear the ESD wrist
strap.
Step 2 Hold the ejector levers with hands on the panel. Push them outwards so that the angle between
the ejector lever and the panel is 45 degrees or so.
Step 3 Push the board gently along the slot guide rail until the board cannot slide further.
CAUTION
Insert the board slowly, to prevent the components on the boards from colliding.
Step 6 If the board is connected to cables originally, connect the cables based on the label marked on
them.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Know the service protection and protection channels of the board to be replaced.
l Make sure that the spare SDH optical interface board is at hand and that the version and
type of the spare board are consistent with those of the board to be replaced.
NOTE
You can identify the type of a board through the board feature code in the bar code on the ejector lever.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 When the service of the board to be replaced is the working service configured with the SNCP,
use the Web LCT or T2000 to perform the forced switching of the service.
Step 4 Make sure that the version and SFP type of the spare board are consistent with those of the board
to be replaced.
Step 5 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 7 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to
cancel it.
Step 8 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Know the service protection and protection channels of the board to be replaced.
l The spare SDH electrical interface board is at hand, and is of the same version as the board
to be replaced.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 When the service of the board to be replaced is the working service configured with the SNCP,
use the Web LCT or T2000 to perform the forced switching of the service.
Step 4 Make sure the version of the spare board is consistent with that of the board to be replaced.
Step 5 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 7 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to
cancel it.
Step 8 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Know the service protection and protection channels of the board to be replaced.
l Make sure that the spare PDH interface board is at hand and that the version and type of it
are consistent with the board to be replaced.
NOTE
The E1 interface boards PO1 and PH1 both have two types: A and B. The A type is of 75-ohm interface
impedance, and the B type 120-ohm. Identify them by the bar code on the board ejector lever.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 3 Make sure the version and type of the spare board are consistent with those of the board to be
replaced.
Step 4 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 6 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Know the service protection and protection channels of the board to be replaced.
l The backup part for the Ethernet service processing board must be available on site. The
version of the backup part must be the same as those of the board to be replaced. For the
EMS6 board, the type of the backup part must also be the same as those of the board to be
replaced.
NOTE
You can identify the type of a board through the board feature code in the bar code on the ejector lever.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 3 Check whether the version and type of the backup part are the same as those of the board to be
replaced.
Step 4 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 6 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Make clear the configuration of the board 1+1 protection.
l Know the service protection and protection channels of the board to be replaced.
l Make sure that the spare IF board is at hand and that the version and type of it are consistent
with those of the board to be replaced.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 When the board to be replaced is the working board configured with the 1+1 protection, use the
Web LCT or T2000 to perform the forced switching of the board.
After the successful switching, perform the step 4.
Step 3 When the service of the board to be replaced is the working service configured with the SNCP,
use the Web LCT or T2000 to perform the forced switching of the service.
Step 6 Make sure the version and type of the spare IF board are consistent with those of the board to
be replaced.
Step 7 Make sure that the ODU-PWR switch on the spare IF board is in the off position.
Step 8 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 11 If the SNCP forced switching was performed for the service, use the Web LCT or T2000 to
cancel it.
Step 12 If the 1+1 protection forced switching of the board was performed, use the Web LCT or T2000
to cancel it.
Step 13 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
Step 14 After you replace the IF1A/IF1B board, you should re-load and re-activate the FPGA file by
referring to the upgrade guide if the new board reports a NO_BD_SOFT alarm.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Make clear the configuration of the board 1+1 protection.
l Make sure that the spare PXC board is at hand and that the version is consistent with that
of the board to be replaced.
Precaution
When the PXC is configured with 1+1 protection and only one-channel power is accessed, it is
recommended to provide one-channel -48 V/-60 V power for the standby PXC board
temporarily. After the board is replaced, stop providing power for the standby board. This can
ensure that the equipment does not power off during the PXC replacement.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 When the board to be replaced is the active board configured with the 1+1 protection, perform
the active and standby switching using the Web LCT or T2000.
1. Select an NE from the NE Explorer, and choose Configuration > Board 1+1 Protection
from the Function Tree.
2. Select a PXC protection group.
3. Click Working/Protection Switching.
4. Click OK to begin the protection switching.
Step 3 Turn off the SYS-PWR switch of the PXC board to be replaced.
Step 4 Turn off the switch of the power that provides power for the PXC board to be replaced.
Step 5 Make sure that the version and type of the spare board are consistent with those of the board to
be replaced.
Step 6 Turn on the switch of the power that provides power for the PXC board.
Step 8 If the switching is performed before the replacement, perform a switchover operation on the
Web LCT or T2000 to make the working board be the active board, not the standby board.
1. Select an NE from the NE Explorer, and choose Configuration > Board 1+1 Protection
from the Function Tree.
2. Select a PXC protection group.
3. Click Working/Protection Switching.
4. Click OK to begin the protection switching.
Step 9 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l Know the impact of board replacement.
l Know the specific position of the board to be replaced.
l Make sure that the spare SCC is at hand and that the version of it is consistent with that of
the board to be replaced.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 3 When the PROG indicator is operating, Refer to section 3.2.1 Removing a Board, remove the
board.
Step 4 Make sure the version and the jumper settings of the spare board are consistent with those of the
board to be replaced.
Step 5 Remove the board to be replaced and portable memory card of the spare board.
1. Wear the ESD wrist strap.
2. Remove the screws on the portable memory card and pull the connector of the memory
card out from the socket of the dual edge connector on the SCC board.
Step 6 Install the portable memory card of the board to be replaced onto the spare board.
Step 7 Refer to 5.8.2 Inserting a Board, and insert the spare board.
Step 9 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
Make sure that the spare fan board is at hand and that the version of it is the same as that of the
board to be replaced.
Procedure
Step 1 Query the current alarm of the board using the Web LCT or T2000, and record the result.
Step 2 Loosen the captive screws on the panel of the fan tray assembly.
Step 3 Move cables away from the front panel of the fan tray assembly.
NOTE
Step 5 Remove the fan board gently and horizontally along the guide rail.
WARNING
Before the fan stops, do not touch the blades.
Step 6 Make sure the version of the spare board is consistent with that of the board to be replaced.
Step 7 Insert the spare board steadily along the guide rail.
Step 8 Install the panel of the fan tray assembly to the original position.
Step 11 Query the current alarm of the board using the Web LCT or T2000.
There should be no newly added alarms.
----End
Prerequisite
l The influence of replacing the ODU must be acknowledged.
l The specific locations of the ODU to be replaced and 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
Precautions
l Before you replace an ODU installed on the coupler, power off the ODU to be replaced,
but do not power off or mute the other ODU. Otherwise, the services may be affected. The
interface of the coupler ejects little RF radiation, and thus meets the safety standards for
microwave radiation.
l The following procedure illustrates only how to replace the ODU with a waveguide
interface.
Procedure
Step 1 Query the current alarm of the ODU using the Web LCT or T2000, and record the result.
Step 2 Turn off the ODU-PWR switch on the panel of the IF board.
Step 4 Loosen the four latches of the ODU and disconnect the ODU from the antenna or the hybrid
coupler.
Step 5 Make sure the type of the spare ODU is consistent with that of the ODU to be replaced.
CAUTION
Do not dispense the lubricant on the front panel of the feeder. Otherwise, it may affect the
signal transmission.
3. Align the antenna interface of the ODU with the feeder and then insert it to the feeder.
Make sure that the four hooks are engaged with the latches of the ODU.
CAUTION
When inserting, make sure that the arrow direction stenciled on the ODU is consistent with
the polarity direction of the antenna or the hybrid coupler.
----End
Prerequisite
l Disconnect both ends of the fiber. Make sure that there is no laser light on the fiber
connector.
l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.
Procedure
Step 1 Press down and hold the lever, and the shutter slides back and exposes a new cleaning area.
Step 2 Position the fiber tip slightly against the cleaning area and drag the fiber tip slightly in the
downward direction.
Figure 5-32 Dragging the fiber tip slightly on one cleaning area
Step 3 Repeat the same in the other cleaning area in the same direction as Step 2.
Figure 5-33 Dragging the fiber tip slightly on the other cleaning area
----End
Prerequisite
l Disconnect both ends of the fiber to be inspected. Make sure there is no laser light present
on the fiber connector.
l Inspect the fiber connector with a fiber microscope to make sure that the fiber connector
is contaminated.
l Using the isoamylol as the clean solvent is recommended, and the propyl can also be used. Do not use alcohol
or formalin.
l The fiber cleaning tissue or lint-free wipes can replace the non-woven lens tissue.
l The special cleaning roll can replace the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the lens tissue.
Step 3 Repeat step 2 several times on the areas of the lens tissue that have not been used.
----End
Prerequisite
l Before you clean the fiber adapter, make sure that you remove the optical fiber and shut
down the laser. For details about how to shut down a laser, refer to 5.6 Setting the State
of the Laser.
l Inspect the fiber adapter with a fiber microscope to make sure that the fiber adapter is
contaminated.
l For the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm, for the LC optical
interface, use the cleaning stick with a diameter of 1.25 mm.
l The medical cotton or long fiber cotton can replace the optical cleaning stick.
l Using the isoamylol as the clean solvent is preferred, and the propyl can also be used. Do not use alcohol
or formalin.
l The special cleaning roll can replace the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the optical cleaning stick.
Step 2 Hold the stick straight out from the adapter and turn the stick clockwise four to five times.
Ensure that there is direct contact between the stick tip and fiber tip so that the solvent can clean
the adapter tip.
Step 3 Using compressed gas, blow off the fiber tip.
When using compressed gas:
l First spray it into the air as the initial spray of condensation can contain some sediment.
l Keep the injector nozzle as close as possible to the connector surface without touching it.
----End
A Alarm Reference
A_LOC Add to bus - loss of clock Major PO1, PH1, PD1, and
PL3
B3_EXC Higher order path (B3) excessive Major SD1, SL1, SDE,
errors SLE, IF1A, IF1B,
IFX, SL4, and PL3
B3_SD Higher order path (B3) signal Minor SD1, SL1, SDE,
degraded SLE, IF1A, IF1B,
IFX, SL4, and PL3
B3_SD_VC3 VC-3 path (B3) signal degraded Minor EFT4 and EMS6
DN_E1_AIS 2M down signal alarm indication Minor PO1, PH1, and PD1
HP_RDI Higher order path remote defect Minor SD1, SL1, SDE,
indication SLE, IF1A, IF1B,
IFX, and SL4
HP_REI Higher order path remote error Warning SD1, SL1, SDE,
indication SLE, IF1A, IF1B,
IFX, and SL4
HP_SLM Higher order path signal label Minor SD1, SL1, SDE,
mismatch SLE, IF1A, IF1B,
IFX, and SL4
HP_TIM Higher order path trace identifier Minor SD1, SL1, SDE,
mismatch SLE, IF1A, IF1B,
IFX, and SL4
HPAD_CROSSTR Higher order path adaptation Minor PO1, PH1, and PD1
performance over threshold
IN_PWR_HIGH Input power too high Critical SD1, SL1 and SL4
IN_PWR_LOW Input power too low Critical SD1, SL1, and SL4
LASER_MOD_ER Pluggable optical module on the Major SD1, SL1, and SL4
R_EX board mismatches the optical
interface
LP_CROSSTR Lower order path performance Minor PO1, PH1, and PD1
parameter over threshold
LP_R_FIFO FIFO overflow on the receiving Minor PO1, PH1, PD1, and
side of the lower order path PL3
LP_RDI Lower order path remote defect Minor PO1, PH1, IF0A,
indication IF0B, PD1, and PL3
LP_RDI_VC12 VC-12 lower order path remote Minor EFT4 and EMS6
defect indication
LP_RDI_VC3 VC-3 lower order path remote Minor EFT4 and EMS6
defect indication
LP_REI Lower order path remote error Minor PO1, PH1, IF0A,
indication IF0B, PD1, and PL3
LP_REI_VC12 VC-12 lower order path remote Minor EFT4 and EMS6
receiving failure indication
LP_REI_VC3 VC-3 lower order path remote Minor EFT4 and EMS6
receiving failure indication
LP_RFI Lower order path remote failure Minor PO1, PH1, and PD1
indication
LP_SLM Lower order path signal label Minor PO1, PH1, PD1, and
mismatch PL3
LP_SLM_VC12 VC-12 lower order path signal Minor EFT4 and EMS6
flag mismatch
LP_SLM_VC3 VC-3 lower order path signal flag Minor EFT4 and EMS6
mismatch
LP_TIM Lower order path trace identifier Minor PO1, PH1, PD1, and
mismatch PL3
LP_TIM_VC12 VC-12 lower order path trace Minor EFT4 and EMS6
identifier mismatch
LP_TIM_VC3 VC-3 lower order path trace Minor EFT4 and EMS6
identifier mismatch
LP_UNEQ_VC12 VC-12 lower order path signal Minor EFT4 and EMS6
unequipped
LP_UNEQ_VC3 VC-3 lower order path signal Minor EFT4 and EMS6
unequipped
RP_LOC Loss of receiving phaselock ring Major PO1, PH1, and PD1
clock
T_ALOS E1 interface loss of analog signal Major PO1, PH1, and PD1
TU_LOP_VC3 VC-3 tributary unit loss of pointer Major EFT4 and EMS6
A.2.1 A_LOC
Description
The A_LOC is an alarm indicating that the clock signal is lost in the adding bus.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Name Meaning
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The board services are interrupted.
Possible Causes
The board is faulty.
Handling Procedure
Replace the faulty board.
----End
Related Information
None.
A.2.2 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is manually disabled.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of a protection group.
Name Meaning
Parameter 2 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
When the APS_MANUAL_STOP alarm arises, the MSP or the switching might fail.
Possible Causes
The MSP protocol is manually disabled.
Handling Procedure
Enable the MSP protocol.
----End
Related Information
None.
A.2.3 ALM_GFP_dCSF
Description
The ALM_GFP_dCSF is an alarm indicating that the generic framing procedure (GFP) customer
signal is lost. This alarm is reported if a board detects that a GFP customer signal management
frame, which indicates that the customer signal is lost, is received from the remote station.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The services are interrupted.
Possible Causes
The related Ethernet port on the remote board is not well connected.
Handling Procedure
Handle the alarm occurred to the remote board.
----End
Related Information
None.
A.2.4 ALM_GFP_dLFD
Description
The ALM_GFP_dLFD is an alarm indicating that the GFP frame is out of frame. This alarm is
reported if a board detects that the GFP frame is out of frame.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The services are interrupted.
Possible Causes
l The source and the sink VCTRUNKs are configured with different paths or timeslots.
l Errors exist on a link or the link is faulty.
Handling Procedure
Step 1 Check whether the VCTRUNK at the local end and the VCTRUNK at the remote end are
configured with the same number of physical paths and timeslots.
Step 2 Check whether a failure or bit errors occur in the line that services pass.
----End
Related Information
None.
A.2.5 ALM_RTC_FAIL
Description
The ALM_RTC_FAIL is an alarm indicating that the real time clock (RTC) of the equipment
fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
None.
Impact on System
None.
Possible Causes
The RTC of the SCC board is faulty.
Handling Procedure
Step 1 Reset the SCC board.
----End
Related Information
None.
A.2.6 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MSP switching fails.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of a protection group.
Parameter 2 Indicates the ID of the protection group that reports the APS_FAIL alarm. For
example, 0x01 indicates that the alarm is reported by protection group 1.
Impact on System
The services cannot be switched. If the current paths are not available, the services are
interrupted.
Possible Causes
l The parameters of the MSP are incorrectly configured.
l The parameters of the MSP are lost.
Handling Procedure
Step 1 Check whether the parameters of the MSP are correctly configured.
Step 2 Check the networkwide MSP protocol, and then disable and restart the protocol manually.
----End
Related Information
None.
A.2.7 APS_INDI
Description
The APS_INDI is an alarm indicating that MSP protection switching is detected.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of a protection group.
Parameter 2 Indicates the ID of the protection group that reports the APS_INDI alarm. For
example, 0x01 indicates that the alarm is reported by protection group 1.
Impact on System
During the MSP switching (within 50 ms), the services are interrupted. After the MSP switching
is complete, the services are restored to normal. During the MSP switching, the extra services
are interrupted.
Possible Causes
MSP switching occurs to the services.
Handling Procedure
Locate the causes of the switching and take appropriate measures.
NOTE
After the non-revertive 1+1 linear MSP switching occurs, the APS_INDI alarm is generated. When the
working path is restored to normal, the services are not automatically switched to the working path and the
APS_INDI alarm persists. In this case, you need to switch the services from the protection path to the
working path manually. After the switching is successful, the APS_INDI alarm is cleared.
----End
Related Information
None.
A.2.8 AU_AIS
Description
The AU_AIS is an alarm indicating AU alarms. This alarm is reported if the AU pointers of
three consecutive frames are detected to be all "1"s.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
Services in AU-4 paths are interrupted. If the services are configured with protection, protection
switching may be triggered.
Possible Causes
l The AU_AIS alarm is inserted at the remote station.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 Check whether the remote station has the alarms that can trigger the AU_AIS alarm.
Step 4 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.9 AU_LOP
Description
The AU_LOP is an alarm indicating that AU pointer is lost. This alarm is reported if a board
detects that the AU-PTR value of eight consecutive frames is invalid or is NDF revertive.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates the alarm is reported by port 1 of the board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
Services in AU-4 paths are interrupted. If the services are configured with protection, protection
switching may be triggered.
Possible Causes
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 channel that reports the alarm.
Step 3 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.10 B1_EXC
Description
The B1_EXC is an alarm indicating that the regenerator section (B1) has excessive errors. This
alarm is reported if a board detects that the B1 bit errors exceed the preset B1_EXC alarm
threshold (10-3 by default).
The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by
the self-defined overhead bytes B1 in PDH microwave frames.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services on the port are interrupted.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
For details, refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.11 B1_SD
Description
The B1_SD is an alarm indicating that the regenerator section (B1) signal degrades. This alarm
is reported if a board detects that the B1 bit errors exceed the preset B1_SD alarm threshold
(10-6 by default).
The IF boards that work in the PDH mode may also report this alarm. This alarm is detected by
the self-defined overhead bytes B1 in PDH microwave frames.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The service performance on the port degrades.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.12 B2_EXC
Description
The B2_EXC is an alarm indicating that the multiplex section (B2) has excessive errors. This
alarm is reported if a board detects that the B2 bit errors exceed the preset B2_EXC alarm
threshold (10-3 by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services on the port are interrupted. If the services are configured with protection, protection
switching may be triggered.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.13 B2_SD
Description
The B2_SD is an alarm indicating that the regenerator section (B2) signal degrades. This alarm
is reported if a board detects that the B2 bit errors exceed the preset B2_SD alarm threshold
(10-6 by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services on the interface degrade.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.14 B3_EXC
Description
The B3_EXC is an alarm indicating that the higher order path (B3) has excessive errors. This
alarm is reported if a board detects the B3 bit errors exceed the preset B3_EXC alarm threshold
(10-3 by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1.
Impact on System
The services in the path are interrupted.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.15 B3_EXC_VC3
Description
The B3_EXC_VC3 is an alarm indicating that excessive B3 bit errors exist in the VC-3 path.
This alarm is reported if a board detects that the B3 bit errors cross the preset threshold of the
B3_EXC_VC3 (10-3 by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by VC-3 path 1.
Impact on System
A large number of bit errors exist in the services in the VC-3 path.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.16 B3_SD
Description
The B3_SD is an alarm indicating that the higher order path (B3) signal degrades. This alarm is
reported if a board detects that the B3 bit errors exceed the preset B3_SD alarm threshold
(10-6 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1.
Impact on System
Services in the path degrade. If the services are configured with protection, protection switching
may be triggered.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.17 B3_SD_VC3
Description
The B3_SD_VC3 is an alarm indicating that the B3 bits in the VC-3 path deteriorate. This alarm
is reported if a board detects that the B3 bit errors cross the preset threshold of the B3_SD_VC3
(10-6 by default).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by VC-3 path 1.
Impact on System
The services in this VC-3 path degrade.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.18 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that a board is installed but the associated
logical board is not installed.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the slot ID.
Impact on System
The physical board installed in the slot fails to work.
Possible Causes
l The slot is not configured with the logical board.
l The physical board is installed into a wrong slot during the board replacement.
Handling Procedure
Step 1 Check whether the physical board is installed into a wrong slot.
----End
Related Information
None.
A.2.19 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board is not in position.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on System
The board that reports the alarm fails to work.
Possible Causes
If the board that reports the alarm is in the IDU, the possible causes are as follows:
If the board that reports the alarm is in the ODU, the possible causes are as follows:
Handling Procedure
Step 1 Handle the alarm appropriately based on the type of board that reports the alarm.
----End
Related Information
None.
A.2.20 BIP_EXC
Description
The BIP_EXC is an alarm indicating that excessive BIP errors arise. This alarm is reported if
the BIP2 bit errors in the V5 byte exceed the preset BIP_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services in the path are interrupted.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.21 BIP_SD
Description
The BIP_SD is an alarm indicating that the BIP signal degrades. This alarm is reported if the
BIP2 bit errors in the V5 byte exceed the preset BIP_SD alarm threshold (10-6 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services in the path degrade.
Possible Causes
l The line performance degrades.
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Refer to 4.4 Troubleshooting Bit Errors.
----End
Related Information
None.
A.2.22 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data check fails. This alarm
is reported if the system detects that the BOOTROM data is corrupted.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of BOOTROM data corruption.
l 0x01 indicates that the basic BIOS is corrupted.
l 0x02 indicates that the extended BIOS is corrupted.
Impact on System
This alarm indicates that errors arise in the system database processing. Some system
configuration data may be lost, and some query and setting commands may fail. Hence, some
system functions may fail.
l If an NE is working, the BOOTROM_BAD dose not affect the system and running services.
l If you hard reset the board in the case of a BOOTROM_BAD alarm, the board fails to load
the BIOS and thus fails to start.
Possible Causes
l The basic BIOS is corrupted
l The extended BIOS is corrupted
l The BOOTROM database is corrupted.
Handling Procedure
Replace the board that reports the alarm.
----End
Related Information
None.
A.2.23 C2_VCAIS
Description
The C2_VCAIS is an alarm indicating that a mismatched signal label byte is received. This alarm
is reported if the C2 byte received by the board is "0xFF".
Attribute
Alarm Severity Alarm Type
Minor alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
None.
Possible Causes
The C2 byte received from the remote end is incorrectly configured.
Handling Procedure
Step 1 Based on the alarm parameters, locate the VC path that reports the alarm.
Step 2 Change C2 to be Received of the remote station based on the actual situation.
----End
Related Information
None.
A.2.24 CONFIG_NOSUPPORT
Description
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. This
alarm is reported if the ODU detects that the configured parameters do not match those of the
ODU.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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, the
main ODU generates the CONFIG_NOSUPPORT alarm. In this case, IF 1+1 protection
switching 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 configured parameters meet the network planning requirements.
----End
Related Information
None.
A.2.25 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the system database processing.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of the database error.
l 0x01: Indicates that the entered parameter is illegal.
l 0x02: Indicates that no database file exists.
l 0x03: Indicates that the database storage area numbers are incorrect.
l 0x04: Indicates that a database overwriting occurs.
l 0x05: Indicates that errors occur in the header information check in the
database backup area.
l 0x06: Indicates that errors occur in the FAT table structure check in the
database storage area.
l 0x07: Indicates that errors occur in the database check in the database backup
area.
l 0x08: Indicates that restoring the database fails.
l 0x09: Indicates an invalid database ID.
l 0x0A: Indicates that the databases are different.
l 0x0B: Indicates that the data is unchecked.
l 0x0E: Indicates that the semaphore handle is invalid.
l 0x0F: Indicates that errors occur in memory applying.
l 0x10: Indicates that errors occur in memory releasing.
l 0x12: Indicates that transmitting the message packets fails.
l 0x13: Indicates that the start record is queried to be incorrect.
l 0x14: Indicates that the database is null.
l 0x15: Indicates that the mark is incorrectly set.
l 0x16: Indicates that the entered command parameters are incorrect.
l 0x17: Indicates that this is not a backup database.
l 0x18: Indicates that the database is in the protected mode.
l 0x19: Indicates that the configuration is not verified.
Impact on System
When the DBMS_ERR alarm occurs, it indicates that errors occur in the system database
processing. The system configuration may be lost. As a result, the failure indication is returned
for some query and setting commands, and some system functions cannot work.
Possible Causes
l The database operation fails.
l The data in the database is corrupted.
l The SCC board is faulty.
Handling Procedure
Step 1 SCC resets.
----End
Related Information
None.
A.2.26 DBMS_PROTECT_MODE
Description
The DBMS_PROTECT_MODE is an alarm indicating that the system database is in protection
mode.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
None.
Impact on System
When the DBMS_PROTECT_MODE alarm arises, you can infer that errors occur in the system
database processing, which then may cause configuration data loss. As a result, some query and
setting commands may fail, and some system functions may become unavailable.
Possible Causes
The NE software is reset frequently.
Handling Procedure
Replace the board that reports the DBMS_PROTECT_MODE alarm.
----End
Related Information
None.
A.2.27 DN_E1_AIS
Description
The DN_E1_AIS is an alarm indicating that the 2-MHz downlink signal is abnormal. This alarm
is reported if the tributary board detects that the downlink E1 signal is all "1"s.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The E1 signal is unavailable.
Possible Causes
l The tributary board of the remote station transmits the E1_AIS signal.
l The receive unit of the tributary board of the local station is faulty.
l The cross-connect board of the local station is faulty.
Handling Procedure
Step 1 Check whether the remote station has the UP_E1_AIS or T_ALOS alarm.
Step 3 Replace the cross-connect and timing board of the local station.
----End
Related Information
None.
A.2.28 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2-MHz clock signal is lost. This alarm is
reported if the tributary board fails to extract clock signals from the input E1 signal.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the tributary port or path that reports the alarm. For example,
0x01 indicates that the alarm is reported by the first port 1 or path 1 of the related
board.
Impact on System
This alarm does not affect the services.
Possible Causes
l The waveform of the input E1 signal is abnormal.
l The receive unit of the tributary board of the local station is faulty.
Handling Procedure
Step 1 Check whether the remote station is faulty.
Step 2 Check whether the wires of the E1 cable are correctly arranged.
Step 3 Check whether there is external interference that causes abnormal E1 signal waveform.
----End
Related Information
None.
A.2.29 E1_LOS
Description
The E1_LOS is an alarm indicating that the 2-MHz line signal (E1 signal) is lost. This alarm is
reported if the tributary board detects that the uplink E1 signal is all "0"s.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
E1 services are interrupted.
Possible Causes
l The input E1 signal is abnormal.
l The tributary board of the local station is faulty.
Handling Procedure
Step 1 Check whether the remote station is faulty.
----End
Related Information
None.
A.2.30 ESN_FAILED
Description
The ESN_FAILED is an alarm indicating that the electronic serial number (ESN) of the
equipment fails.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the SCC board that reports the ESN_FAILED alarm.
Impact on System
None.
Possible Causes
l Reading the equipment ESN fails.
l The verification of the equipment ESN fails.
Handling Procedure
Replace the SCC board that reports the ESN_FAILED alarm.
----End
Related Information
None.
A.2.31 ESN_INVALID
Description
The ESN_INVALID is an alarm indicating that the electronic serial number (ESN) of the
equipment is invalid.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the SCC board that reports the ESN_INVALID alarm.
Impact on System
None.
Possible Causes
The ESN that is read from the SCC board is verified, but it cannot be identified.
Handling Procedure
Contact the technical support engineers of Huawei to upgrade the NE software.
----End
Related Information
None.
A.2.32 ETH_LOS
Description
The ETH_LOS is an alarm indicating that the Ethernet port is disconnected.
Attribute
Alarm Severity Alarm Type
Critical alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the Ethernet port that reports the alarm. For example, 0x01
indicates that the alarm is reported by Ethernet port 1 of the related board.
Parameters 2–3 The values are always 0x00 and 0x01, respectively.
Impact on System
The services carried over the port are interrupted.
Possible Causes
l The Ethernet cable or optical fiber connected to the port is faulty.
l The equipment connected to the port is faulty.
l The working mode of the port does not match that of the port at the remote end.
Handling Procedure
Step 1 Check the Ethernet cable or optical fiber connected to the port.
Step 3 Check whether the working modes of the ports at both ends match each other.
----End
Related Information
None.
A.2.33 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm indicating that the external clock source is lost.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the external clock that reports the alarm. For example, 0x01
indicates that the alarm is reported by external clock 1.
Impact on System
l If the clock source priority table is configured with the external and internal clock sources
only, the internal clock source is traced and the clock enters the free-run mode after the
loss of the external clock source.
l If the clock source priority table is configured with other valid clock sources, the loss of
the external clock source can trigger clock protection switching.
Possible Causes
The clock priority table has the external clock source, but the external clock source cannot be
detected or is unavailable.
Handling Procedure
Step 1 Check whether the clock source device at the remote end is faulty.
Step 2 Check whether the cable of the external clock source is normal.
Step 3 Replace the cross-connect and timing board that connects to the clock source.
----End
Related Information
None.
A.2.34 F1PORT_FAILED
Description
The F1PORT_FAILED is an alarm indicating that the synchronous data port fails. This alarm
is reported if the synchronous data port–related data is configured but the SCC does not provide
a synchronous data port.
Attribute
Alarm Severity Alarm Type
Minor alarm Communication alarm
Parameters
None.
Impact on System
The synchronous data port–related configuration is invalid.
Possible Causes
The portable memory card located in the SCC is configured with synchronous data port–related
data, but the SCC does not provide a synchronous data port.
Handling Procedure
Step 1 Check whether the synchronous data port–related data is required.
----End
Related Information
None.
A.2.35 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan fails.
Attribute
Parameters
None.
Impact on System
The heat dissipation is affected.
Possible Causes
l The board is faulty.
l The board and the backplane are poorly connected.
Handling Procedure
Step 1 Remove and insert the fan board. Remove the dust on the fan and re-install the fan board.
----End
Related Information
None.
A.2.36 FCS_ERR
Description
The FCS_ERR is an alarm indicating that errors occur in the verification of the frame check
sequence (FCS). This alarm is reported if errors occur when a board performs FCS verification
for the received frames.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
When the encapsulation protocols or the encapsulation parameters at both ends of the Ethernet
service are different, the service is interrupted or bit errors arise.
Possible Causes
l The encapsulation protocols or the encapsulation parameters at both ends of the Ethernet
service are different.
l Bit errors exist in the service path.
Handling Procedure
Step 1 Check whether the encapsulation protocols at both ends of the Ethernet service are the same.
Step 2 Check whether the encapsulation parameters at both ends of the Ethernet service are the same.
Step 3 Check whether any bit error alarm or performance event occurs on the line boards through which
the service travels.
----End
Related Information
None.
A.2.37 HARD_BAD
Description
The HARD_BAD is an alarm indicating hardware errors.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the cause of the fault.
l 0x01: Indicates that the power module is working abnormally.
l 0x02: Indicates that the board is improperly installed.
l 0x03: Indicates that the 38-MHz system clock 1 is abnormal.
l 0x04: Indicates that the 38-MHz system clock 2 is abnormal.
l 0x05: Indicates that the 2-MHz clock source is abnormal.
l 0x06: Indicates that the digital phase-locked loop is abnormal.
l 0x07: Indicates that the 38-MHz service clock is lost.
l 0x08: Indicates that the bus is abnormal.
l 0x09: Indicates that the TPS protection board is abnormal.
l 0x0A: Indicates that the primary crystal oscillator stops oscillating.
l 0x0B: Indicates the frequency offset of the primary crystal oscillator is
excessive.
l 0x0C: Indicates that the secondary crystal oscillator stops oscillating.
l 0x0D: Indicates that the processor (CPU/DSP/coprocessor) is faulty.
l 0x0E: Indicates that the storage components are faulty.
l 0x0F: Indicates that the programmable logic device is faulty.
l 0x10: Indicates that the SDH components are faulty.
l 0x11: Indicates that the data communication components are faulty.
l 0x12: Indicates that the clock components are faulty.
l 0x13: Indicates that the interface components are faulty.
l 0x14: Indicates that the power components are faulty.
l 0x15: Indicates other faults.
l 0x16: Indicates that the analog phase-locked loop is abnormal.
l 0x17: Indicates that the 32-MHz clock is unavailable.
l 0x18: Indicates that the 66-MHz clock is unavailable.
l 0x19: Indicates that the 25-MHz clock is unavailable.
Impact on System
The board that reports the alarm fails to work.
Possible Causes
l The board is faulty.
l The board and the backplane are not properly connected.
l The slot is faulty.
Handling Procedure
Step 1 Remove and insert the board again.
Step 3 Install the board that reports the alarm into another slot.
If the board reports no alarm in the new slot, you can infer that the previous slot is faulty.
Step 4 Keep the board in the new slot, and contact the technical support engineers of Huawei for
rectifying the fault.
----End
Related Information
None.
A.2.38 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that a performance indicator of the higher order path
crosses the related threshold. This alarm is reported if a board detects that a bit error performance
indicator of the higher order path crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameters 4–5 l The two most significant bits of Parameter 4 indicate the performance
monitoring period. When the value of the two most significant is "01", the
monitoring period is 15 minutes. When the value of the two most
significant is "02", the monitoring period is 24 hours.
l The six least significant bits of Parameter 4 together with Parameter 5
indicate the performance event ID.
Impact on System
The services contain a large amount of bit errors, and the services may be interrupted.
Possible Causes
A bit error performance indicator of the higher order path crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of higher order path bit error performance events to
determine the performance event that crosses the preset threshold.
Step 2 Handle the performance event accordingly.
----End
Related Information
None.
A.2.39 HP_LOM
Description
The HP_LOM is an alarm indicating that the multiframe is lost in the higher order path. This
alarm is reported if a board detects that the H4 byte mismatches the expected multiframe
sequence.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
The services in the path are interrupted. If the services are configured with protection, protection
switching may be triggered.
Possible Causes
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Step 1 Replace the line board of the remote station.
Step 2 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.40 HP_RDI
Description
The HP_RDI is an alarm indicating that signal reception fails at the remote end of the higher
order path. This alarm is reported if a board detects that bit 5 of the G1 byte is "1".
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
The local station is not affected. Signal reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message indicates that
signal reception fails at the remote end of the higher order path.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 Clear the alarm in the AU-4 path of the remote station.
----End
Related Information
None.
A.2.41 HP_REI
Description
The HP_REI is an alarm indicating that an error is detected in the remote higher order path. This
alarm is reported if the board detects that the values of bit 1 through bit 4 of the G1 byte range
from "1" to "8".
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
The local station is not affected. The remote station, however, receives bit errors.
Possible Causes
The local station receives a message from the remote station, and the message indicates bit errors
over the remote higher order path.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 Handle the HP_BBE performance event in the AU-4 path of the remote station.
----End
Related Information
None.
A.2.42 HP_SLM
Description
The HP_SLM is an alarm indicating that a mismatched higher order path signal label is detected.
This alarm is reported if a board detects a mismatched C2 byte.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
None.
Possible Causes
l The C2 byte to be received at the local station mismatches the C2 byte transmitted by the
remote station.
l The data configuration is wrong.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment,
configure the services to be VC-4 pass-through services.
Step 3 Ensure that the service types at the local and remote stations of the AU-4 path are identical.
----End
Related Information
None.
A.2.43 HP_TIM
Description
The HP_TIM is an alarm indicating that a mismatched higher order path trace identifier is
detected. This alarm is reported if the board detects a mismatched J1 byte.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
If the services are configured with protection and this alarm is the triggering condition, protection
switching may be triggered.
Possible Causes
l The J1 byte to be received at the local station is different from the J1 byte transmitted from
the remote station.
l Data configuration at the intermediate nodes is incorrect.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
Step 2 If the port that reports the alarm is the SDH port used to interconnect ATM/Ethernet equipment,
configure the services to be VC-4 pass-through services.
Step 3 Set the J1 byte to be received at the local station to the disable mode. Alternatively, set the J1
byte to be received at the local station to be the same as that transmitted from the remote station.
Step 4 Check whether the cross-connections of the intermediate nodes through which the service travels
are correctly configured. If not, correct the cross-connection configuration.
----End
Related Information
None.
A.2.44 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating that the higher order path is unequipped. This alarm is
reported if a board detects that the C2 byte is "0".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
Services in the AU-4 path are unavailable. If the services are configured with protection and this
alarm is the triggering condition, protection switching may be triggered.
Possible Causes
The line port of the local station is configured with services, but the line port of the remote station
is not.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
----End
Related Information
None.
A.2.45 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that a higher order path adaptation performance
indicator crosses the threshold. This alarm is reported if a board detects that a TU pointer
adaptation performance indicator crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameters 4–5 l The higher two bits of Parameter 4 indicate the performance monitoring
period. When the value of the two most significant bits is "01", the
monitoring period is 15 minutes. When the value of the two most
significant bits is "02", the monitoring period is 24 hours.
l The six least significant bits of Parameter 4 together with Parameter 5
indicate the ID of a performance event.
Impact on System
Bit errors may occur to the services.
Possible Causes
A TU pointer adaptation performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the TU pointer adaptation performance events, and
locate the performance event that crosses the preset threshold.
----End
Related Information
None.
A.2.46 HSB_INDI
Description
The HSB_INDI is an alarm indicating that the microwave equipment is switched over.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group.
Parameter 2 Indicates the slot where the working board is installed.
Impact on System
The services are interrupted during the protection switching and return to normal after the
switching is complete.
Possible Causes
1+1 HSB protection switching occurs.
Handling Procedure
Locate the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.47 HSM_INDI
Description
The HSM_INDI is an alarm indicating that the microwave channel is switched over.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group.
Parameter 2 Indicates the slot where the working board is installed.
Impact on System
Bit errors are not generated during channel switching. This alarm has no impact on the services.
Possible Causes
1+1 FD/SD protection switching occurs.
Handling Procedure
Locate the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.48 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is disconnected.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by IF port 1 of the related board.
Impact on System
The services carried over the IF port are interrupted.
Possible Causes
l 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 properly
made.
----End
Related Information
None.
A.2.49 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an alarm indicating that the input IF power of the ODU is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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 System
The services on the ODU are interrupted. If 1+1 protection is configured, 1+1 HSB switching
may be triggered.
Possible Causes
l There is an inloop operation on the IF port.
l The IF board is faulty.
l The IF cables are faulty.
l The ODU is faulty.
Handling Procedure
Step 1 Check whether there is an inloop operation on the IF port.
Step 3 Check whether the cable connector workmanship meets the requirement.
Step 4 Replace the IF board connecting with the ODU that reports the alarm.
----End
Related Information
None.
A.2.50 IF_MODE_UNSUPPORTED
Description
The IF_MODE_UNSUPPORTED is an alarm indicating that the configured IF working mode
is not supported. This alarm is reported if the board is not loaded with the FPGA file that supports
the configured IF working mode.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by IF port 1 of the related board.
Impact on System
The services carried over the IF port are interrupted.
Possible Causes
The board is not loaded with the FPGA file that supports the configured IF working mode.
Handling Procedure
Contact the technical support engineers of Huawei to upgrade the board software and the FPGA
file.
----End
Related Information
None.
A.2.51 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input power is too high.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the board.
Impact on System
Bit errors occur to the services of the optical interface.
Possible Causes
l The transmit optical power of the remote station is too high.
l The type of the optical module is incorrect.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Based on the transmission distance, check whether the type of the SFP optical modules of the
receive and transmit ends is correct.
Step 3 Query the performance events of the transmit optical power at the remote station.
Step 4 Add a proper optical attenuator to reduce the receive optical power.
----End
Related Information
None.
A.2.52 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input power is too low.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
Bit errors may occur to the services on the optical interface.
Possible Causes
l The transmit optical power of the remote station is too low.
l The fiber performance degrades.
l The type of the optical module is incorrect.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Based on the transmission distance, check whether the type of the SFP optical modules of the
receive and transmit ends is correct .
Step 3 Query the performance events of the transmit optical power at the remote station.
Step 6 Add a proper optical amplifier to increase the receive optical power.
----End
Related Information
None.
A.2.53 J0_MM
Description
The J0_MM is an alarm indicating that a mismatched trace identifier is detected. This alarm is
reported if a board detects a mismatched J0 byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
None.
Possible Causes
The J0 byte to be received by the local station mismatches the J0 byte transmitted by the remote
station.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
Step 2 Set the J0 byte to be received at the local station to the disable mode.
----End
Related Information
None.
A.2.54 K1_K2_M
Description
The K1_K2_M is an alarm indicating that the K1 and K2 bytes are mismatched. This alarm is
reported if a board detects that the transmitted K1 byte (bits 5–8) contains a path ID different
from that contained in the received K2 byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of a protection group. For example, 0x01 indicates a linear
MSP group.
Parameter 2 Indicates the ID of the protection group that reports the K1_K2_M alarm. For
example, 0x01 indicates that the alarm is reported by protection group 1.
Impact on System
The MSP switching may be abnormal or even fail.
Possible Causes
l The switching modes at both ends are single-ended switching and dual-ended switching,
respectively.
l The equipment is faulty.
Handling Procedure
Step 1 Check whether the services are correctly configured.
----End
Related Information
None.
A.2.55 K2_M
Description
The K2_M is an alarm indicating that a mismatched K2 byte is detected. This alarm is reported
if a board detects that the received K2 byte (bit 5) contains a protection mode different from that
of the local station.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the type of a protection group. For example, 0x01 indicates a linear
MSP group.
Parameter 2 Indicates the ID of the protection group that reports the K2_M alarm. For
example, 0x01 indicates that the alarm is reported by protection group 1.
Impact on System
The MSP switching may be abnormal or even fail.
Possible Causes
l Two NEs on a linear MS are configured with different MSP modes, such as 1+1 and 1:N.
l When the MSP switching occurs, the MSP protocol at the remote station is disabled.
l The equipment is faulty.
Handling Procedure
Step 1 Check whether the two NEs on a linear MS are configured with the same MSP mode.
----End
Related Information
None.
A.2.56 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is closed.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
The optical interface fails to carry services.
Possible Causes
The laser is shut down at the local station.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Find the reason for shutting down the laser, and turn it on promptly.
----End
Related Information
None.
A.2.57 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR_EX is an alarm indicating that the pluggable optical module on the
board mismatches the optical interface.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the board.
Impact on System
The services on the optical interface are interrupted.
Possible Causes
l The rate of the optical module does not match that of the optical interface.
l The optical module is faulty.
l The board is faulty.
Handling Procedure
Step 1 Check whether the rate of the optical module and that of the optical interface match each other.
----End
Related Information
None.
A.2.58 LCAS_FOPR
Description
The LCAS_FOPR is an alarm indicating that the link capacity adjustment scheme (LCAS)
protocol in the receive direction fails. This alarm is reported if the receive unit of the LCAS
module of a board detects an abnormal state in which the LCAS might fail to negotiate or cannot
negotiate correctly.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The Ethernet service is abnormal.
Possible Causes
l The downlink virtual concatenation group (VCG) receives repeated sequence numbers due
to incorrect configuration or bit errors on the link.
l The LCAS function of the remote VCG is disabled.
l The downlink VCG receives the FIXED and other LCAS control bytes simultaneously
owing to incorrect configuration or bit errors on the link.
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at both ends of
the link.
Step 2 Check whether the configurations of the local and remote stations are correct. That is, check
whether an VCG of the local station is connected to multiple VCGs of the remote station.
Step 3 Check whether a fault such as failure or bit errors occurs on the service link.
Step 4 Disable the LCAS protocol at both the stations, and then restart the protocol.
----End
Related Information
None.
A.2.59 LCAS_FOPT
Description
The LCAS_FOPT is an alarm indicating that the LCAS protocol in the transmit direction fails.
This alarm is reported if the transmit unit of the LCAS module of a board detects an abnormal
state in which the LCAS might fail to negotiate or cannot negotiate correctly.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The Ethernet service is abnormal.
Possible Causes
l The LCAS protocol configuration is incorrect.
l The link is faulty.
Handling Procedure
Step 1 Check whether the LCAS enable state and the LCAS parameters are the same at both ends of
the link.
Step 2 Check whether a fault such as failure or bit errors occurs on the service link.
Step 3 Disable the LCAS protocol at both ends of the link, and then restart the protocol.
----End
Related Information
None.
A.2.60 LCAS_PLCR
Description
The LCAS_PLCR is an alarm indicating that a part of the LCAS bandwidth in the receive
direction is lost. This alarm is reported if a board detects that the number of paths that carry the
overloads in the receive direction of the VCTRUNK with the LCAS enabled is less than the
preset number but is not zero.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l The number of paths or timeslots that are configured for the VCTRUNK at the remote
station is different from that at the local station.
l Some paths in the transmit direction of the remote station are faulty.
l Some paths in the receive direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are
configured with the same number of physical paths and timeslots.
Step 2 Check whether any path alarm exists in the transmit direction of the remote station.
----End
Related Information
None.
A.2.61 LCAS_PLCT
Description
The LCAS_PLCT is an alarm indicating that part of the LCAS bandwidth in the transmit
direction is lost. This alarm is reported if a board detects that the number of paths that carry the
overloads in the transmit direction of the VCTRUNK with the LCAS enabled is less than the
preset number but is not zero.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The available Ethernet service bandwidth is smaller than the configured bandwidth.
Possible Causes
l The number of paths or timeslots that are configured for the VCTRUNK at the remote
station is different from that at the local station.
l Some paths in the receive direction of the remote station are faulty.
l Some paths in the transmit direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs in the transmit direction of the local station and the receive
direction of the remote station are configured with the same number of physical paths and
timeslots.
Step 2 Check whether any path alarm exists in the receive direction of the remote station.
----End
Related Information
None.
A.2.62 LCAS_TLCR
Description
The LCAS_TLCR is an alarm indicating that all the LCAS bandwidth in the receive direction
is lost. This alarm is reported if no path in the receive direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The Ethernet service is interrupted.
Possible Causes
l The number of paths or timeslots that are configured for the VCTRUNK at the remote
station is different from that at the local station.
l The paths in the transmit direction of the remote station are faulty.
l The paths in the receive direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are
configured with the same number of physical paths and timeslots.
Step 2 Check whether any path alarm exists in the transmit direction of the remote station.
----End
Related Information
None.
A.2.63 LCAS_TLCT
Description
The LCAS_TLCT is an alarm indicating that all the LCAS bandwidth in the transmit direction
is lost. This alarm is reported if no path in the transmit direction of the VCTRUNK with LCAS
enabled carries the overload but paths are configured to carry the overload.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The Ethernet service is interrupted.
Possible Causes
l The number of paths or timeslots that are configured for the VCTRUNK at the remote
station is different from that at the local station.
l The paths in the transmit direction of the remote station are faulty.
l The paths in the receive direction of the local station are faulty.
Handling Procedure
Step 1 Check whether the VCTRUNKs at the transmit and the receive directions at the local station are
configured with the same number of physical paths and timeslots.
Step 2 Check whether any path alarm exists in the transmit direction of the remote station.
----End
Related Information
None.
A.2.64 LCS_LIMITED
Description
The LCS_LIMITED is an alarm indicating that the capacity of the services configured for an
NE crosses the limit defined in the license file.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
None.
Impact on System
Changing the capacity of the microwave services through an NE does not take effect.
Possible Causes
The capacity of the configured services crosses the limit defined in the license file.
Handling Procedure
Step 1 Check whether the capacity of the microwave services is changed as required.
Step 2 Check whether the service capacity defined in the license file of the NE is in agreement with the
latest authorization terms.
Step 3 Contact the local Huawei office to apply for the authorization of greater service capability.
----End
Related Information
The microwave service capacity of an NE is calculated based on the cross-connections on the
IF board.
A.2.65 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the license file is not detected.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
None.
Impact on System
If no microwave service is configured, the microwave services with a default capacity of 4xE1
are configured. If microwave services are configured, there is no impact on the system except
that an alarm is reported.
Possible Causes
The license file is lost or not loaded.
Handling Procedure
Contact the technical support engineers of Huawei to reload the associated license file.
----End
Related Information
The microwave service capacity of an NE is calculated based on the cross-connections on the
IF board.
A.2.66 LICENSE_ERR
Description
The LICENSE_ERR is an alarm indicating that license verification of a NE fails.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the cause of verification failure.
Impact on System
If no microwave service is configured, the microwave services with a default capacity of 4xE1
are configured. If microwave services are configured, there is no impact on the system except
that an alarm is reported.
Possible Causes
The verification of the license file fails.
Handling Procedure
Contact the technical support engineers of Huawei to reload the associated license file.
----End
Related Information
The microwave service capacity of an NE is calculated based on the cross-connections on the
IF board.
A.2.67 LINK_ERR
Description
The LINK_ERR is an alarm indicating that the data link fails.
Attribute
Alarm Severity Alarm Type
Critical alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. For example, 0x01 indicates that the
alarm is reported by optical interface 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm. 0x00 0x01 indicates that
the alarm is reported by path 1.
Impact on System
The services carried over the path are interrupted.
Possible Causes
l The optical fiber connected to the Ethernet optical interface is faulty.
l The working modes of the ports at both ends do not match each other.
Handling Procedure
Step 1 Check whether the optical fiber connected to the Ethernet optical interface is faulty.
Step 2 Check whether the working modes of the ports at both ends match each other.
Step 3 Use an optical fiber to conduct a loopback test over the port that reports the alarm.
----End
Related Information
None.
A.2.68 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a path loopback arises.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameter 4 Indicates the type of loopback.
l 0x00: Indicates optical/electrical port inloop.
l 0x01: Indicates optical/electrical port outloop.
l 0x02: Indicates path inloop.
l 0x03: Indicates path outloop.
l 0x04: Indicates loopback at the user side.
l 0x05: Indicates loopback at the combination wave side.
l 0x06: Indicates SPI inloop.
l 0x07: Indicates SPI outloop.
l 0x08: Indicates ATM layer inloop.
l 0x09: Indicates ATM layer outloop.
l 0x0A: Indicates PHY layer inloop.
l 0x0B: Indicates PHY layer outloop.
l 0x0C: Indicates MAC layer inloop.
l 0x0D: Indicates MAC layer outloop.
l 0x0E: Indicates VC-4 timeslot inloop.
l 0x0F: Indicates VC-4 timeslot outloop.
l 0x10: Indicates VC-3 timeslot inloop.
l 0x11: Indicates VC-3 timeslot outloop.
l 0x12: Indicates VC-12 timeslot inloop.
l 0x13: Indicates VC-12 timeslot outloop.
l 0x14: Indicates IF outloop.
l 0x15: Indicates IF inloop.
l 0x16: Indicates RF inloop.
l 0xFF: Indicates one of the above loopback modes.
Impact on System
The loopback port or path fails to carry services.
Possible Causes
Loopback is performed at the local station.
Handling Procedure
Step 1 Based on the alarm parameters, determine the type of loopback.
Step 2 Find out the cause of loopback, and cancel the loopback.
----End
Related Information
None.
A.2.69 LPS_UNI_BI_M
Description
The LPS_UNI_BI_M is an alarm indicating that switching modes (single-ended or dual-ended)
at both ends of the linear MSP do not match each other.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
The system performs protection switching in single-ended mode.
Possible Causes
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
l The switching modes at the local and remote stations are different.
l The last three bits of the K2 byte are set to the indicated mode.
l The type of the protocol is set to the restructure protocol.
Handling Procedure
Change the MSP switching modes at both ends, and ensure that they are the same.
----End
Related Information
None.
A.2.70 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that a lower order path performance indicator crosses
the related threshold. This alarm is reported if a board detects that a lower order path bit error
performance indicator crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameter 4–5 l The two most significant bits of Parameter 4 indicate the performance
monitoring period. When the value of the two most significant bits is "01",
the monitoring period is 15 minutes. When the value of the two most
significant bits is "02", the monitoring period is 24 hours.
l The six least significant bits of Parameter 4 together with Parameter 5
indicate the performance event ID.
Impact on System
The services contain a large amount of bit errors and the services may be interrupted.
Possible Causes
Lower order path bit error performance events exceed the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of lower order path bit error performance events to
determine the performance event that crosses the preset threshold.
----End
Related Information
None.
A.2.71 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the receive side of a lower
order path.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
Bit errors occur to the services.
Possible Causes
l The board is faulty.
l The clock at the local station and that at the remote station are asynchronous.
Handling Procedure
Step 1 Check whether there are TU pointer adjustment performance events at the local and remote
stations.
----End
Related Information
None.
A.2.72 LP_RDI
Description
The LP_RDI is an alarm indicating that the remote end fails to receive signals over the lower-
order path. This alarm is reported if the board detects that bit 8 of the V5 byte (indicating E1
interface board) is 1 or bit 5 of the G1 byte (indicating E3/T3 interface board) is 1.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The local station is not affected, but the service reception at the remote station is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message says that signal
reception in the lower-order path fails.
Handling Procedure
Handle the alarm about the lower order path of the remote station.
----End
Related Information
None.
A.2.73 LP_RDI_VC12
Description
The LP_RDI_VC12 is an alarm indicating that data reception fails at the remote end of VC-12
lower order path. This alarm is reported if a board detects that bit 8 of the V5 byte is "1".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The local station is not affected. Data reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message says that data
reception fails at the remote end of a lower order path.
Handling Procedure
Handle the fault occurred to the remote station.
----End
Related Information
None.
A.2.74 LP_RDI_VC3
Description
The LP_RDI_VC3 is an alarm indicating that data reception at the remote end of a VC-3 lower
order path fails. This alarm is reported if a board detects that bit 5 of the G1 byte is "1".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The local station is not affected. Data reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message says that data
reception fails at the remote end of a lower order path.
Handling Procedure
Handle the fault occurred to the remote station.
----End
Related Information
None.
A.2.75 LP_REI
Description
The LP_REI is an alarm indicating that there are bit errors over the lower order path of the remote
station. This alarm is reported if the board detects that bit 3 of the V5 (indicating E1 interface
board) byte is 1 or bits 1–4 of the G1 byte (indicating E3/T3 interface board) are 1–8.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The local station is not affected, but there are bit errors in the received signals of the remote
station.
Possible Causes
The local station receives a message from the remote station, and the message says that there
are bit errors in the lower order path of the remote station.
Handling Procedure
Handle the LP_BBE performance event of the remote station.
----End
Related Information
None.
A.2.76 LP_REI_VC12
Description
The LP_REI_VC12 is an alarm indicating that there are bit errors at the remote end of a VC-12
lower order path. This alarm is reported if a board detects that bit 3 of the V5 byte is "1".
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The remote station has bit errors in the received data.
Possible Causes
The local station receives a message from the remote station, and the message says that there
are bit errors in the lower order path.
Handling Procedure
Handle the LP_BBE performance event of the remote station.
----End
Related Information
None.
A.2.77 LP_REI_VC3
Description
The LP_REI_VC3 is an alarm indicating that there are bit errors at the remote end of a VC-3
lower order path. This alarm is reported if a board detects that a bit of bits 1–4 of the G1 byte is
"1".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
Bit errors exist in the service in the receive direction of the remote station.
Possible Causes
The local station receives a message from the remote station, and the message says that there
are bit errors at the remote end of a lower order path.
Handling Procedure
Handle the VC3BBE performance event.
----End
Related Information
None.
A.2.78 LP_RFI
Description
The LP_RFI is an alarm indicating that the remote end of the lower order path fails. This alarm
is reported if a board detects that bit 4 of the V5 byte is "1".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The local station is not affected. The remote station, however, has bit errors in the received data.
Possible Causes
The local station receives a message from the remote station, and the message says that the
remote end of the lower order path fails.
Handling Procedure
Clear the alarm in the lower order path of the remote station.
----End
Related Information
None.
A.2.79 LP_SIZE_ERR
Description
The LP_SIZE_ERR is an alarm indicating that the TU structure is wrong.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services on the board are interrupted.
Possible Causes
l The configuration of the mapping structure is incorrect.
l The tributary board is faulty.
Handling Procedure
Step 1 Check whether the types of the add/drop services configured are consistent with the service types
that the board supports.
----End
Related Information
None.
A.2.80 LP_SLM
Description
The LP_SLM is an alarm indicating that a mismatched signal label is detected in the lower order
path. This alarm is reported if the board detects a signal label mismatch between the V5 bytes
(indicating E1 interface board) or the C2 bytes (indicating E3/T3 interface board) of both ends.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services in the lower order path are unavailable.
Possible Causes
The signal label contained in the V5 byte or C2 byte that is received by the local station does
not match that transmitted by the remote station.
Handling Procedure
Modify the signal label contained in the V5 byte or C2 byte at the local station or the remote
station and ensure that the signal labels at both ends match each other.
----End
Related Information
None.
A.2.81 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in a VC-12
lower order path. This alarm is reported if a board detects a mismatched signal label in the V5
byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by the first VC-12 path.
Impact on System
The service in this lower order path is unavailable.
Possible Causes
The signal label in the V5 byte to be received at the local station is different from that transmitted
from the remote station.
Handling Procedure
Modify the signal label in V5 byte to be received at the local station in consistent with that
transmitted from the remote station.
----End
Related Information
None.
A.2.82 LP_SLM_VC3
Description
The LP_SLM_VC3 is an alarm indicating that a mismatched signal label is detected in a VC-3
path. This alarm is reported if a board detects a mismatched signal label in the C2 byte.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The service in this lower order path is unavailable.
Possible Causes
The signal label in the C2 byte to be received at the local station is different from that at the
remote station.
Handling Procedure
Modify the signal label to be received at the local station to be the same as that transmitted from
the remote station.
----End
Related Information
None.
A.2.83 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmission side of the
lower order path.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
Bit errors occur to the services.
Possible Causes
l The board is faulty.
l The frequency offset of the input signal is too large.
Handling Procedure
Step 1 Test the frequency offset of the input signal.
----End
Related Information
None.
A.2.84 LP_TIM
Description
The LP_TIM is an alarm indicating a mismatched lower-order path trace identifier is received.
This alarm is reported if the board detects a mismatch between the J1 bytes (indicating E3/T3
interface board) or the J2 bytes (indicating E1 interface board) of both ends.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
None.
Possible Causes
l The J1 or J2 byte to be received by the local station does not match that transmitted by the
remote station..
l Data configuration at the intermediate nodes is incorrect.
Handling Procedure
Step 1 Set the byte mode of the J1/J2 byte to be received by the local station to the disable mode.
Alternatively, you can set the byte mode in consistent with the J1/J2 byte transmitted by the
remote station.
Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels
are correctly configured. If not, correct the cross-connection configuration.
----End
Related Information
None.
A.2.85 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating that a mismatched VC-12 lower path trace identifier
is detected. This alarm is reported if a board detects a mismatched J2 byte in a VC-12 path.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
None.
Possible Causes
l The J1 byte to be received at the local station is different from the J1 byte transmitted from
the remote station.
l Data configuration at the intermediate nodes is incorrect.
Handling Procedure
Step 1 Set the J2 byte to be received at the local station to disabled or to be the same as the J2 byte
transmitted from the remote station.
Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels
are correctly configured. If not, correct the cross-connection configuration.
----End
Related Information
None.
A.2.86 LP_TIM_VC3
Description
The LP_TIM_VC3 is an alarm indicating that a mismatched VC-3 lower path trace identifier is
detected. This alarm is reported if a board detects a mismatched J1 byte in a VC-3 path.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
None.
Possible Causes
l The J1 byte to be received at the local station is different from the J1 byte transmitted from
the remote station.
l Data configuration at the intermediate nodes is incorrect.
Handling Procedure
Step 1 Set the J1 byte to be received at the local station to disabled or to be the same as the J1 byte
transmitted from the remote station.
Step 2 Check whether the cross-connections of the intermediate nodes through which the service travels
are correctly configured. If not, correct the cross-connection configuration.
----End
Related Information
None.
A.2.87 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm is
reported if a board detects that the V5 byte signal label is "0".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The service in this path is unavailable.
Possible Causes
The tributary path of the local station is configured with services, but that of the remote station
is not.
Handling Procedure
Configure tributary services for the remote station.
----End
Related Information
None.
A.2.88 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 lower order path is unequipped.
This alarm is reported if a board detects that the signal label in the V5 byte is "0".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The service in the path is unavailable. If the service is configured with protection, protection
switching may be triggered.
Possible Causes
Data configuration has the following errors:
l The tributary path at the local station is configured with services but the corresponding
tributary path at the remote station is not configured with services.
l The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the remote station.
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not,
correct the configurations.
----End
Related Information
None.
A.2.89 LP_UNEQ_VC3
Description
The LP_UNEQ_VC3 is an alarm indicating that the VC-3 lower order path is unequipped. This
alarm is reported if a board detects that the signal label in the C2 byte is "0".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The service in this path is unavailable. If the service is configured with protection, protection
switching may be triggered.
Possible Causes
Data configuration has the following errors:
l The tributary path at the local station is configured with services but the corresponding
tributary path at the remote station is not configured with services.
l The cross-connection configurations are incorrect at intermediate NEs.
Handling Procedure
Step 1 Check whether the corresponding tributary path is configured with services at the remote station.
Step 2 Check whether the cross-connection configurations at intermediate NEs are correct. If not,
correct the configurations.
----End
Related Information
None.
A.2.90 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the laser is not installed.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
The optical interface fails to carry services.
Possible Causes
The laser of the local station is not installed.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Find out why the laser is not installed, and install it promptly.
----End
Related Information
None.
A.2.91 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the service life of the laser will end soon.
Attribute
Alarm Severity Alarm Type
Critical alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
The SFP optical module may not function reliably, and thus the services may be interrupted.
Possible Causes
The laser gets aged.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Contact the technical support engineers of Huawei to replace the SFP optical module with a new
one.
----End
Related Information
None.
A.2.92 LTI
Description
The LTI is an alarm indicating that the synchronization source is lost. This alarm is reported if
all the synchronization sources are lost for the NE.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 l 0x01: Indicates that all the synchronization sources of the system clock are
lost.
l 0x02: Indicates that all the synchronization sources of the 2-MHz phase-
locked source are lost.
Impact on System
The clock enters the free-run mode and loses synchronization with other NE clocks.
Possible Causes
l The clock configuration is incorrect.
l The clock sources in the clock source priority table fail.
Handling Procedure
Step 1 Check whether the data in the clock source priority table complies with the network planning
requirement.
Step 2 Based on the clock source priority table, locate the synchronization source.
----End
Related Information
None.
A.2.93 MOD_TYPE_MISMATCH
Description
The MOD_TYPE_MISMATCH is an alarm indicating that a mismatched port module is
detected.
Attribute
Alarm Severity Alarm Type
Critical alarm Maloperation
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by port 1 of the related board.
Impact on System
The services carried over the port are interrupted.
Possible Causes
The type defined by the customer for the SFP module is different from the actual module type.
Handling Procedure
Step 1 Based on the alarm parameters, locate the port that reports the alarm.
Step 2 Verify the type of the SFP module that connects to the port.
----End
Related Information
None.
A.2.94 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported if a board
detects that bit 6 to bit 8 of the K2 byte in three consecutive frames are "111".
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services on the line port are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The transmit unit of the remote station is faulty.
Handling Procedure
Step 1 Replace the line board of the remote station.
Step 2 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.95 MS_CROSSTR
Description
The MS_CROSSTR is an alarm indicating that a performance indicator of the multiplex section
crosses the threshold. This alarm is reported if a board detects that the multiplex section bit error
performance indicator crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameters 4–5 l The two most significant bits of the parameter 4 indicates the performance
monitoring period ("01" means that the monitoring period is 15 minutes,
and "02" means that the monitoring period is 24 hours).
l The parameter 5 and the six least significant bits of the parameter 4 together
indicate the ID of a performance event.
Impact on System
The services contain a large amount of bit errors, and the services may be interrupted.
Possible Causes
The multiplex section bit error performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of multiplex section bit error performance events to
determine the performance event that crosses the preset threshold.
Step 2 Handle the performance event that crosses the threshold.
----End
Related Information
None.
A.2.96 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception fails at the remote end of the multiplex
section. This alarm is reported if a board detects that bit 6 to bit 8 of the K2 byte are "110".
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The local station is not affected. Data reception at the remote station, however, is interrupted.
Possible Causes
The local station receives a message from the remote station, and the message says that data
reception fails at the remote end of the multiplex section.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
----End
Related Information
None.
A.2.97 MS_REI
Description
The MS_REI is an alarm indicating that there are errors at the remote end of the multiplex section.
This alarm is reported if a board detects that the M1 byte is non-zero.
Attribute
Alarm Severity Alarm Type
Warning Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The local station is not affected. The services received by the remote station, however, have bit
errors.
Possible Causes
The local station receives a message from the remote station, and the message says that there
are bit errors at the remote end of the multiplex section.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
----End
Related Information
None.
A.2.98 MSAD_CROSSTR
Description
The MSAD_CROSSTR is an alarm indicating that the adaptation performance indicator of the
multiplex section crosses the threshold. This alarm is reported if board detects that an AU pointer
adaptation performance indicator crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Parameters 4–5 l The two most significant bits of parameter 4 indicates the performance
monitoring period ("01" means that the monitoring period is 15 minutes,
and "02" means that the monitoring period is 24 hours).
l Parameter 5 and the six least significant bits of parameter 4 together
indicate the ID of a performance event.
Impact on System
Bit errors may occur to the services.
Possible Causes
l An AU pointer adaptation performance indicator crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the AU pointer adaptation performance events to
determine the performance event that crosses the preset threshold.
Step 2 Handle the performance event that crosses the threshold.
----End
Related Information
None.
A.2.99 MSSW_DIFFERENT
Description
The MSSW_DIFFERENT is an alarm indicating that the master and slave software mismatches
each other. This alarm is reported if the NE detects that the master and slave software mismatches
each other.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter 1 Indicates the file location.
l 0x01: Indicates the files in the flash.
l 0x02: Indicates the software that is currently running.
Parameters 2–3 Indicate the ID of the inconsistent file on the SCC board.
Parameters 4–5 Indicate the alarm cause.
l 0x04: Indicates that the file versions in the master and slave areas of an
SCC board are inconsistent.
l 0x08: Indicates that the file versions in the active and standby SCC boards
are inconsistent, or that the files in the corresponding directories of the
active and standby SCC boards have different names.
l 0x0c: Indicates that the file versions in the master and slave areas of an
SCC board are inconsistent and the file versions on the active and standby
SCC boards are also inconsistent.
Impact on System
If the working software is lost, the backup software fails to take over the running services. If no
NE software exists in the flash, the system is unable to restart upon power-off or resetting.
Possible Causes
Software loading is abnormal.
Handling Procedure
Contact the technical support engineers of Huawei for re-loading the software.
----End
Related Information
None.
A.2.100 MW_FECUNCOR
Description
The MW_FECUNCOR is an alarm indicating that the Reed Solomon (RS) encoding cannot be
corrected.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that the
alarm is reported by port 1 of the related board.
Impact on System
Bit errors occur to the services. If the system is configured with 1+1 FD/SD protection, channel
protection switching may be triggered.
Possible Causes
l 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
Refer to 4.3 Troubleshooting Microwave Links.
----End
Related Information
None.
A.2.101 MW_LIM
Description
The 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 frame
overheads.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that the
alarm is reported by port 1 of the related board.
Impact on System
The microwave link fails to carry services. If the services are configured with SNCP, protection
switching may be triggered.
Possible Causes
l 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 the
microwave from other stations.
l The polarization direction of the XPIC is wrong.
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.
Step 3 Check whether the receive/transmit frequencies at the local end are consistent with those at the
remote end.
Step 4 Check whether the XPIC configuration is correct if XPIC protection groups are provided.
Step 5 Adjust the direction of the antenna to align it properly with the antenna at the remote end.
----End
Related Information
None.
A.2.102 MW_LOF
Description
The MW_LOF is an alarm indicating that the Reed Solomon (RS) frame is lost.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that the
alarm is reported by port 1 of the related board.
Impact on System
The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l 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
Refer to 4.3 Troubleshooting Microwave Links.
----End
Related Information
None.
A.2.103 MW_RDI
Description
The MW_RDI is an alarm indicating that there are defects at the remote end of the microwave
link. This alarm is reported if an IF board detects an RDI in the microwave frame overheads.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the IF port that reports the alarm. For example, 0x01 indicates that the
alarm 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 boards
receive the MW_RDI alarm at the same time, the 1+1 switching may be triggered. This alarm
also 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 returns
a microwave link fault indication to the transmit station.
Handling Procedure
Handle the microwave alarm occurred to the remote station.
----End
Related Information
None.
A.2.104 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported if
the SCC board detects that the NE software in the flash memory is lost.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the inspection object.
l 0x01: Indicates an ordinary file.
l 0x02: Indicates the version file of the running software.
l 0x03: Indicates a special inspection object.
l 0x01, 0x03, and 0x05 indicate the scc.fpga, nesoft.hwx, and ne.ini in the
ofs1, respectively.
l 0x02, 0x04, and 0x06 indicate the scc.fpga, nesoft.hwx, and ne.ini in the
ofs2, respectively.
Parameter 4 Indicates the alarm cause.
l If the first bit is "1", you can infer that the file does not exist.
l If the second bit is "1", you can infer that verification of the file fails.
l If the third bit is "1", you can infer that the version of the file in the active
area is different from that of the file in the standby area.
l If the fourth bit is "1", you can infer that the version of the file in the active
board is different from that of the file in the standby board.
Impact on System
If the NE software does not exist in the master and slave storage areas, an NE cannot be restarted
after it is powered off or reset.
Possible Causes
l No NE software is loaded after the existing ones are erased.
l Loading the NE software is unsuccessful.
l The portable flash memory is not in position or is faulty.
Handling Procedure
Step 1 Check whether the alarm is caused by the loading operation.
----End
Related Information
None.
A.2.105 NESTATE_INSTALL
Description
The NESTATE_INSTALL is an alarm indicating that the NE is in the install state.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
None.
Impact on System
The NE fails to work.
Possible Causes
l The logical cross-connect board is not configured.
Handling Procedure
Step 1 Through the NMS, check whether the logical cross-connect board is configured.
----End
Related Information
None.
A.2.106 NO_BD_SOFT
Description
The NO_BD_SOFT is an alarm indicating that the board software is missing.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the type of the lost software.
l 0x01: Indicates board software.
l 0x02: Indicates the active FPGA.
l 0x03: Indicates the standby FPGA.
Impact on System
l If the board software is lost, the board fails to work normally.
Possible Causes
Software loading is abnormal.
Handling Procedure
Contact the technical support engineers of Huawei to re-load the software.
----End
Related Information
None.
A.2.107 NP1_MANUAL_STOP
Description
The NP1_MANUAL_STOP is an alarm indicating that the N+1 protection protocol is manually
disabled.
Attribute
Alarm Severity Alarm Type
Minor alarm Processing alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
The N+1 protection may fail, or the protection switching may fail.
Possible Causes
The N+1 protection protocol is manually disabled.
Handling Procedure
Enable the N+1 protection protocol.
----End
Related Information
None.
A.2.108 NP1_SW_FAIL
Description
The NP1_SW_FAIL is an alarm indicating that the N+1 protection switching fails.
Attribute
Alarm Severity Alarm Type
Major alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
The services cannot be switched. If the current paths are not available, the services are
interrupted.
Possible Causes
The N+1 protection switching fails.
Handling Procedure
Step 1 Check whether the parameters of the N+1 protection are correctly configured.
Step 2 Check the networkwide N+1 protection protocol, and then disable and restart the protocol
manually.
----End
Related Information
None.
A.2.109 NP1_SW_INDI
Description
The NP1_SW_INDI is an alarm indicating that the N+1 protection switching is detected.
Attribute
Alarm Severity Alarm Type
Major alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the protection group that reports the alarm. For example, 0x01
indicates that the alarm is reported by protection group 1.
Impact on System
During the switching (not more than 50 ms), the services are interrupted. After the switching is
complete, the services are restored to normal. During the switching, the extra services are
interrupted.
Possible Causes
The N+1 protection switching is performed.
Handling Procedure
Locate the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.110 OPM_FAIL
Description
The OPM_FAIL is an alarm indicating that the system fails to output optical power.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface that reports the alarm. For example, 0x01
indicates that the alarm is reported by optical interface 1 of the related board.
Impact on System
The services carried over the optical interface are interrupted.
Possible Causes
The SFP optical module is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the optical interface that reports the alarm.
Step 2 Contact the technical support engineers of Huawei to replace the SFP optical module with an
appropriate one.
----End
Related Information
None.
A.2.111 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE is an alarm indicating that the port is not in position.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the port that reports the alarm.
Parameters 2–3 The values are always 0x00 and 0x01, respectively.
Impact on System
The services over the port are interrupted.
Possible Causes
The port is enabled, but the SFP module is not installed.
Handling Procedure
Step 1 Verify whether to access services over the port.
----End
Related Information
None.
A.2.112 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the power module that reports the alarm. For example, 0x01
indicates that the alarm is reported by the first power module of the board.
Parameter 2 l 0x01: Indicates under-voltage.
l 0x02: Indicates over-voltage.
Impact on System
Power modules of the IDU 620 are configured with protection. If only one power module reports
the POWER_ALM alarm, the system is not affected.
Possible Causes
l The input power is abnormal.
l The power module is abnormal.
Handling Procedure
Step 1 Use a multimeter to test the power voltage supplied to the chassis.
----End
Related Information
l For the IDU 620, the two power modules on the two PXC boards make 1+1 backup.
l For the IDU 620, the two power modules on the FAN board make 1+1 backup.
A.2.113 POWER_FAIL
Description
The POWER_FAIL is an alarm indicating that the power supply fails. This alarm is reported if
the ODU detects that its power module fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the power supply that reports the alarm. For example, 0x01
indicates 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.
Impact on System
The ODU fails to work normally.
Possible Causes
The power module of the ODU is faulty.
Handling Procedure
Replace the ODU that reports the alarm.
----End
Related Information
None.
A.2.114 P_AIS
Description
The P_AIS is an alarm indicating that abnormal signal reception is detected over the PDH
interface. This alarm is reported if the tributary board detects all "1"s in the up signal flow of
the PDH.
Attribute
Alarm Severity Alarm Type
Major alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The signals transmitted over the PDH interface are not usable.
Possible Causes
l The PDH equipment at the remote end transmits the AIS signal.
l The tributary board at the local end fails to receive signals properly.
Handling Procedure
Step 1 Check whether the equipment at the remote end transmits the AIS signal.
----End
Related Information
None.
A.2.115 P_LOS
Description
The P_LOS is an alarm indicating that signals are lost over the PDH interface.
Attribute
Alarm Severity Alarm Type
Major alarm Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The PDH services are interrupted.
Possible Causes
l The PDH services are not accessed over the interface.
l The equipment at the remote end is faulty.
l The trunk cable is faulty.
l The board that reports the alarm is faulty.
Handling Procedure
Step 1 Check whether PDH services are accessed over the interface.
----End
Related Information
None.
A.2.116 PS
Description
The PS is an alarm indicating that protection switching is performed.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services are interrupted during the protection switching (<50 ms) and return to normal after
the switching is complete.
Possible Causes
Protection switching occurs to the services.
Handling Procedure
Locate the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.117 R_F_RST
Description
The R_F_RST is an alarm indicating that the receive FIFO is reset.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services are interrupted.
Possible Causes
l The board is faulty.
l Clock synchronization is lost between the local station and the remote station.
Handling Procedure
Step 1 Query whether there are TU pointer adjustment performance events at the local station or the
remote station.
----End
Related Information
None.
A.2.118 R_LOC
Description
The R_LOC is an alarm indicating that clock signal is not detected at the receive end. This alarm
is reported if the line board fails to extract clock signal from the line signal.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of 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 Causes
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
Step 4 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.119 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost at the receive side. This alarm is reported
if the OOF state lasts for 3 ms.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
l The line performance degrades.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
Step 2 If this alarm is reported by the IF board, check whether there is an MW_FECUNCOR alarm.
Step 3 If this alarm is reported by the optical interface board or STM-1 electrical interface board,
exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends.
Step 5 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.120 R_LOS
Description
The R_LOS is an alarm indicating that signal is lost at the receive side.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the path ID.
Impact on System
The services are interrupted. If the system is configured with protection, protection switching
may be triggered.
Possible Causes
l The transmit unit of the remote station is faulty.
l The receive unit of the local station is faulty.
l The line performance degrades.
Handling Procedure
Step 1 Based on the alarm parameters, locate the line port that reports the alarm.
Step 2 If this alarm is reported by the IF board, check whether there is an MW_FECUNCOR alarm.
Step 3 If this alarm is reported by the optical interface board or STM-1 electrical interface board,
exchange the receive/transmit fiber jumpers or cables at the receive and the transmit ends.
NOTE
This method applies only to the situation where only one end reports the alarm. If both ends reports the
alarm, check whether the transmission distance is too long or the cables are broken.
Step 5 Replace the cross-connect and timing board of the remote station.
----End
Related Information
None.
A.2.121 R_S_ERR
Description
The R_S_ERR is an alarm indicating that the received signal has errors.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services are interrupted.
Possible Causes
l The board is faulty.
l The frequency offset of the input signal is too large.
Handling Procedure
Step 1 Check whether the tributary board supports the type of the input signal.
----End
Related Information
None.
A.2.122 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.
Impact on System
The transmitter does not launch services.
Possible Causes
l The transmitter of the local station 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.
----End
Related Information
None.
A.2.123 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is too high. This
alarm is reported if the detected receive power is equal to or higher than the upper threshold of
the ODU (–20 dBm).
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.
Impact on System
The service transmission is affected. If the system is configured with 1+1 protection, protection
switching may be triggered.
Possible Causes
l The ODU is faulty.
l There is a strong interference source nearby.
Handling Procedure
Step 1 Replace the ODU.
----End
Related Information
None.
A.2.124 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is too low. This
alarm is reported if the detected receive power is equal to or below the lower threshold of the
ODU (–90 dBm).
Attribute
Alarm Severity Alarm Type
Critical Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.
Impact on System
If there is neither the MW_LOF nor the MW_FECUNCOR alarm, the services are not affected.
Possible Causes
l The microwave link signal is too much attenuated.
l The transmit power of the remote station is too low.
l The ODU of the local station is faulty.
Handling Procedure
Step 1 Check whether the transmit power of the remote station is normal.
Step 3 Check whether the antennas at both ends are properly adjusted.
Step 4 Check whether the polarization direction of the antenna, ODU, and hybrid coupler is correctly
set.
Step 5 Check whether the outdoor units such as antennas, combiner, ODU, and flexible waveguide are
wet, damp, or damaged.
Step 6 Check whether the antenna gain at both the transmit and receive sides meets the requirement.
Step 8 Replace the ODU and combiner at the local end in sequence.
Step 9 Replace the ODU and combiner at the remote end in sequence.
----End
Related Information
None.
A.2.125 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. This
alarm is reported if the detected transmit power is higher than the upper power threshold of the
ODU.
Attribute
Alarm Severity Alarm Type
Critical Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.
Impact on System
The service transmission is affected. If the system is configured with 1+1 protection, protection
switching may be triggered.
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU.
----End
Related Information
None.
A.2.126 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is too low. This
alarm is reported if the detected transmit power is below the lower power threshold of the ODU.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the RF port that reports the alarm.
Impact on System
The service transmission is affected. If the system is configured with 1+1 protection, protection
switching may be triggered.
Possible Causes
The ODU is faulty.
Handling Procedure
Replace the ODU.
----End
Related Information
None.
A.2.127 RELAY_ALARM
Description
The RELAY_ALARM is an alarm indicating relay errors.
Attribute
Alarm Severity Alarm Type
Critical Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the input alarm. For example, 0x01 indicates that the reported
external alarm is the first input alarm.
Impact on System
None.
Possible Causes
The input alarm signal reports the alarm.
Handling Procedure
Step 1 Based on the alarm parameters, locate the ID of the input alarm.
Step 2 Rectify the fault according to the meaning of the input alarm.
----End
Related Information
None.
A.2.128 RP_LOC
Description
The RP_LOC is an alarm indicating that the receiving phaselock ring clock is lost.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None.
Impact on System
The services on the board are interrupted.
Possible Causes
The board is faulty.
Handling Procedure
Replace the board that reports the alarm.
----End
Related Information
None.
A.2.129 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that a regenerator section performance indicator
crosses the threshold. This alarm is reported if board detects that a regenerator section
performance event crosses the preset threshold.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the path that reports the alarm.
Name Meaning
Parameters 4–5 l The two most significant bits of parameter 4 indicates the performance
monitoring period (01 means that the monitoring period is 15 minutes, and
02 means that the monitoring period is 24 hours).
l Parameter 5 and the six least significant bits of parameter 4 together
indicate the ID of a performance event.
Impact on System
The services contain a large amount of bit errors, and the services may be interrupted.
Possible Causes
A regenerator section performance event crosses the preset threshold.
Handling Procedure
Step 1 Check the threshold crossing records of the regenerator section performance events to determine
the performance event that crosses the preset threshold.
----End
Related Information
None.
A.2.130 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched over in S1 byte
mode.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 l 0x01: Indicates that the system clock is switched over.
l 0x02: Indicates that the 2-MHz phase-locked source is switched over.
Impact on System
This alarm does not affect the system.
Possible Causes
In S1 byte mode, switching occurs to the clock source.
Handling Procedure
Find out the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.131 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the synchronization source degrades.
Attribute
Parameters
None.
Impact on System
The NE clock is unlocked.
Possible Causes
l The synchronization source degrades.
l The cross-connect unit is faulty.
Handling Procedure
Step 1 If the traced synchronization source is the external clock, check whether the type of the external
clock configuration is correct.
Step 2 If the traced synchronization source is the external clock, check whether the remote clock source
device is faulty.
Step 3 If the traced synchronization source is the external clock, check whether the external clock cable
is normal.
Step 4 If the traced synchronization source is the line clock, replace the cross-connect and timing board
of the upstream NE.
Step 5 Replace the board that reports the alarm.
----End
Related Information
None.
A.2.132 SYNC_C_LOS
Description
The SYNC_C_LOS is an alarm indicating that the synchronization source is lost.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter Two parameters indicate one lost clock source.
l If the line clock source is lost, the first parameter indicates the slot number of
the clock source, and the second parameter indicates the port number of the
clock source.
l If the external clock source is lost, "xf0, 1"indicates the external clock 1, and
"0xf0, 2" indicates the external clock 2.
Impact on System
The NE clock degrades or enters the free-run mode.
Possible Causes
The clock source is lost.
Handling Procedure
Step 1 Based on the alarm parameters, locate the lost clock source.
Step 2 Find out why the clock source is lost, and rectify the fault.
----End
Related Information
None.
A.2.133 T_ALOS
Description
The T_ALOS is an alarm indicating that the 2-Mbit/s analog signal is lost at the specific port.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services are interrupted.
Possible Causes
l The port does not access the 2 Mbit/s service.
l The remote station is faulty.
l The trunk cable is faulty.
l The board that reports the alarm is faulty.
Handling Procedure
Step 1 Check whether the port that reports the alarm accesses the 2 Mbit/s service.
----End
Related Information
None.
A.2.134 T_F_RST
Description
The T_F_RST is an alarm indicating that the transmit FIFO is reset.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The service in the PDH path is interrupted.
Possible Causes
l The board is faulty.
l The frequency offset of the input signal is too large.
Handling Procedure
Step 1 Check whether the frequency offset of the input signal is too large.
----End
Related Information
None.
A.2.135 T_FIFO_E
Description
The T_FIFO_E is an alarm indicating that the transmit FIFO overflows.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
Bit errors occur to the services.
Possible Causes
l The board is faulty.
l The frequency offset of the input signal is too large.
Handling Procedure
Step 1 Check whether the frequency offset of the input signal is too large.
----End
Related Information
None.
A.2.136 T_LOC
Description
The T_LOC is an alarm indicating that the clock signal is lost at the transmit side.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
The services in the AU-4 path are interrupted.
Possible Causes
l The cross-connect and timing board is faulty.
l The line board is faulty.
Handling Procedure
Step 1 Based on the alarm parameters, locate the AU-4 path that reports the alarm.
----End
Related Information
None.
A.2.137 T_LOS
Description
The T_LOS is an alarm indicating that the input signal is lost at the transmit side.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the line port that reports the alarm. For example, 0x01
indicates that the alarm is reported by port 1 of the related board.
Parameters 2–3 Indicate the ID of the AU-4 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by AU-4 path 1 in the SDH signal.
Impact on System
The services in the AU-4 path are interrupted.
Possible Causes
l The SDH service configuration mismatches the type of the line board.
l The cross-connect and timing board is faulty.
l The line board is faulty.
Handling Procedure
Step 1 Check the SDH service configuration.
----End
Related Information
None.
A.2.138 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the temperature crosses the threshold.
Attribute
Alarm Severity Alarm Type
Minor Environment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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 System
The board fails to work normally.
Possible Causes
l 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.
Step 3 If the alarm is reported by a board of the IDU and the IDU has air filters, clean the air filters.
Step 4 If the ambient temperature is normal and there is no heat-sinking problem, replace the board that
reports the alarm.
----End
Related Information
None.
A.2.139 TU_AIS
Description
The TU_AIS is an alarm indicating that the TU has errors. This alarm is reported if a board
detects that the TU path is all "1"s.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services in the TU path are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The data configuration is wrong.
l The line is faulty.
l The cross-connect and timing board is faulty.
l The tributary board is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct.
Step 5 Replace the cross-connect and timing board of the local station.
----End
Related Information
None.
A.2.140 TU_AIS_VC12
Description
The TU_AIS_VC12 is an alarm indicating a VC-12 TU has errors. This alarm is reported if a
board detects that the TU pointer is "1".
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 1.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The services in the VC-12 TU path are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The data configuration is incorrect.
l The link is faulty.
l The cross-connect and timing board is faulty.
l A tributary board is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct.
Step 5 Replace the cross-connect and timing board at the local station.
----End
Related Information
None.
A.2.141 TU_AIS_VC3
Description
The TU_AIS_VC3 is an alarm indicating that a VC-3 TU has errors. This alarm is reported if a
board detects that the TU pointer is "1".
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The services in the VC-3 TU path are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The data configuration is incorrect.
l The link is faulty.
l The cross-connect and timing board is faulty.
l A tributary board is faulty.
Handling Procedure
Step 1 Check whether the SDH service data and the network protection data are correct.
Step 5 Replace the cross-connect and timing board at the local station.
----End
Related Information
None.
A.2.142 TU_LOP
Description
The TU_LOP is an alarm indicating that the TU pointer is lost. This alarm is reported if a board
detects that the TU-PTR value of eight consecutive frames is invalid or is NDF revertive.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The services on the TU channel are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The cross-connect and timing board is faulty.
l The tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board.
----End
Related Information
None.
A.2.143 TU_LOP_VC12
Description
The TU_LOP is an alarm indicating that the VC-12 TU pointer is lost. This alarm is reported if
a board detects that the VC-12 TU-PTR value of eight consecutive frames is invalid or is NDF
revertive.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 1.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
The services in the TU path are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The cross-connect and timing board is faulty.
l A tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board at the local station.
----End
Related Information
None.
A.2.144 TU_LOP_VC3
Description
The TU_LOP is an alarm indicating that the VC-3 TU pointer is lost. This alarm is reported if
a board detects that the TU-PTR value of eight consecutive frames is invalid or is NDF revertive.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The services in the TU path are interrupted. If the services are configured with protection,
protection switching may be triggered.
Possible Causes
l The cross-connect and timing board is faulty.
l A tributary board is faulty.
Handling Procedure
Step 1 Replace the cross-connect and timing board at the local station.
----End
Related Information
None.
A.2.145 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indicating that the 2-MHz uplink signal has errors. This alarm is
reported if the tributary board detects that the uplink E1 signal is all "1"s.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the path that reports the alarm. For example, 0x00 0x01
indicates that the alarm is reported by path 1.
Impact on System
The E1 signals are unavailable.
Possible Causes
l The remote station sends the AIS signal.
l The receive unit of the tributary board of the local station is faulty.
Handling Procedure
Step 1 Check whether the remote station sends the AIS signal.
----End
Related Information
None.
A.2.146 VCAT_LOA
Description
The VCAT_LOA is an alarm indicating that the delay of the virtual concatenation is too long.
This alarm is reported if a board detects that the time delay of the timeslots bound to a VCTRUNK
is out of the permissible limit.
Attribute
Alarm Severity Alarm Type
Critical Service alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VCTRUNK that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VCTRUNK 1.
Impact on System
The virtually concatenated services are interrupted.
Possible Causes
The differences between VC links are too large.
Handling Procedure
Step 1 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the
same.
Step 2 Check whether bit errors or a line alarm exists. If yes, handle the alarm.
----End
Related Information
None.
A.2.147 VCAT_LOM_VC12
Description
The VCAT_LOM_VC12 is an alarm indicating that the virtual concatenation multiframe in the
VC-12 path is lost. This alarm is reported if a board detects that the K4 byte of the VC-12 timeslot
mismatches the expected multiframe sequence.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
This path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l The link configuration is incorrect.
l The virtual concatenation delay time varies with each path.
l Bit errors exist in the line.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of the path are bound with the same timeslot.
Step 2 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the
same.
Step 3 Check whether any bit errors or line alarm exists. If yes, handle the alarms.
----End
Related Information
None.
A.2.148 VCAT_LOM_VC3
Description
The VCAT_LOM_VC3 is an alarm indicating the virtual concatenation multiframe in the VC-3
path is lost. This alarm is reported if a board detects that the H4 byte of the VC-3 timeslot
mismatches the expected multiframe sequence.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
This path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l The link configuration is incorrect.
Handling Procedure
Step 1 Check whether the VCTRUNKs at both ends of the path are bound with the same timeslot.
Step 2 Check whether the transmission routes for the paths that are bound to this VCTRUNK are the
same.
Step 3 Check whether bit errors or a line alarm exists. If yes, handle the alarms.
----End
Related Information
None.
A.2.149 VCAT_SQM_VC12
Description
The VCAT_SQM_VC12 is an alarm indicating that a mismatched virtual concatenation
sequence (SQ) is detected in the VC-12 path. This alarm is reported if a board detects that a
mismatched virtual concatenation (SQ).
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Name Meaning
Parameters 2–3 Indicate the ID of the VC-12 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-12 path 1.
Impact on System
This path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l Errors exist on a link or the link is faulty.
l The SQ number sent from the remote station is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists.
----End
Related Information
None.
A.2.150 VCAT_SQM_VC3
Description
The VCAT_SQM_VC3 is an alarm indicating that a mismatched virtual concatenation SQ is
detected in the VC-3 path. This alarm is reported if a board detects a mismatched virtual
concatenation SQ in the VC-3 path.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameters 2–3 Indicate the ID of the VC-3 path that reports the alarm. For example, 0x00
0x01 indicates that the alarm is reported by VC-3 path 1.
Impact on System
The path is unavailable. If the LCAS function is disabled, the services are interrupted.
Possible Causes
l Bit errors exist on a link or the link is faulty.
l The SQ number sent from the remote station is wrong.
Handling Procedure
Step 1 Check whether bit errors or a line alarm exists.
----End
Related Information
None.
A.2.151 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power is not available.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
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 PXC board, only one power input is available for the system.
If the alarm is reported by the IF board, the ODU connected to the IF board fails to work.
Possible Causes
l The input power is abnormal.
l The power module is abnormal.
l The power switch is turned off.
Handling Procedure
Step 1 Locate the board that reports the alarm, and handle the alarm accordingly.
Step 3 Locate the type of the power supply that reports the alarm, and handle the alarm accordingly.
----End
Related Information
None.
A.2.152 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that a board of the wrong type is detected.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the slot where the board is seated.
Impact on System
The board does not work.
Possible Causes
l The data configuration is wrong.
l The type of the board installed is incorrect.
Handling Procedure
Step 1 Check whether the board type configured complies with the planning requirement.
----End
Related Information
None.
A.2.153 WRG_DEV_TYPE
Description
The WRG_DEV_TYPE is an alarm indicating that a device of the wrong type is detected.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None.
Impact on System
The equipment does not work.
Possible Causes
The data configuration is incorrect.
Handling Procedure
Modify the type of the equipment to be consistent with the equipment.
----End
Related Information
None.
A.2.154 WS_LOS
Description
The WS_LOS is an alarm indicating that the wayside interface signal is lost.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the wayside service where the alarm occurs.
Impact on System
The wayside services are interrupted.
Possible Causes
l Wayside service data has been configured, but the services are not accessed.
l The remote station is faulty.
l The wayside cables are faulty.
l The PXC board is faulty.
Handling Procedure
Step 1 Check whether wayside service data is configured but the services are not accessed.
----End
Related Information
None.
A.2.155 W_R_Failure
Description
The W_R_Failure is an alarm indicating that reading and writing the chip register fail.
Attribute
Alarm Severity Alarm Type
Major alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the ID of the register.
Parameters 2–3 The values are always 0x00 and 0x01, respectively.
Impact on System
The services carried in the path are interrupted.
Possible Causes
l The chip register fails.
l The read/write time sequence is wrong.
Handling Procedure
Replace the board that reports the alarm.
----End
Related Information
None.
A.2.156 XCP_INDI
Description
The XCP_INDI is an alarm indicating that the active and standby PXC boards are switched over.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
Parameter 1 Indicates the slot where the working board is seated.
Impact on System
During the protection switching (< 50 ms), VC-3/VC-12 services are interrupted.
Possible Causes
Protection switching occurs to the PXC board.
Handling Procedure
Determine the cause of switching, and take appropriate measures.
----End
Related Information
None.
A.2.157 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
Attribute
Alarm Severity Alarm Type
Critical alarm Equipment alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
Name Meaning
Parameter 1 Indicates the ID of the IF port that reports the alarm. For example, 0x01 indicates
that the alarm is reported by IF port 1 of the related board.
Impact on System
Bit errors arise, and the services carried over the port may be interrupted.
Possible Causes
l The related data is incorrectly configured.
l The XPIC signal cable is faulty.
l The IF board is faulty.
l The ODU connected to the IF board is faulty.
Handling Procedure
Step 1 Check whether to enable the XPIC function.
Step 3 Replace the remote IF board connected to the XPIC signal cable.
----End
Related Information
None.
HPBBE Higher order path block of background error SL1, SD1, SLE,
SDE, IF1A,
HPES Higher order path errored second IF1B,IFX and
HPSES Higher order path severely errored second SL4
Unit Block
Relevant Alarms
When the AUPJCHIGH, AUPJCLOW, and AUPJCNEW events cross the preset thresholds, the
MSAD_CROSSTR alarm may be generated.
Probable Causes
The NE clock is not synchronized.
Procedure
See 4.5 Troubleshooting Pointer Justifications.
----End
Unit Block
Relevant Alarm
When the TUPJCHIGH, TUPJCLOW and TUPJCNEW cross the preset threshold, the
HPAD_CROSSTR alarm occurs.
Probable Causes
The NE clock is not synchronized.
Procedure
Refer to section 4.5 Troubleshooting Pointer Justifications.
----End
When the intermediate board works in the PDH mode, the performance events might also be reported. These
events are detected through the self-defining overhead byte B1 of the PDH microwave frame.
Relevant Alarms
When the RSBBE, RSES, RSSES, RSCSES, and RSUAS events cross the preset threshold, the
RS_CROSSTR alarm may be generated.
RSES 50 100
RSSES 20 50
RSUAS 20 50
Probable Causes
The system detects the RSBBE by using the B1 byte.
Procedure
See 4.4 Troubleshooting Bit Errors.
----End
Relevant Alarms
If RSOOF is received in five consecutive frames, the equipment will enter the OOF state. If the
OOF state lasts for 3 ms, the equipment will report the R_LOF alarm. As a result, all the services
are interrupted.
Probable Causes
The system detects that the A1 and A2 bytes are incorrect.
Procedure
If the R_LOF alarms are reported at the same time, process the errors according to the alarms.
Otherwise, refer to section 4.4 Troubleshooting Bit Errors .
----End
Attribute Description
Relevant Alarms
When the MSBBE, MSES, MSSES, MSCSES, and MSUAS events cross the preset thresholds,
the MS_CROSSTR alarm may be generated.
MSES 50 100
MSES 20 50
MSUAS 20 50
Probable Causes
The system detects the MSBBE according to the B2 byte.
Procedure
See 4.4 Troubleshooting Bit Errors.
----End
l MSFESES stands for "multiplex section far end severely errored second".
The FESES (far end severely errored second) indicates that the SES occurs at the opposite
end.
l MSFECSES stands for "Multiplex section far end consecutive severely errored second".
The FESES (far end consecutive severely errored second) indicates that the CSES occurs
at the opposite end.
l MSFEUAS stands for "multiplex section unavailable second".
The FEUAS (far end unavailable second) indicates that the UAS occurs at the opposite end.
Relevant Alarm
The MS_REI alarm occurs at the local end.
Probable Causes
The system detects the MSFEBBE by the M1 byte.
Procedure
Clear the corresponding event at the opposite end.
----End
Severely errored second (SES) refers the second in which more than 30% errored blocks
or at least one severely disturbed period (SDP) exists. The SDP refers to the period in which
the BER of all the consecutive blocks in a period of less than four consecutive blocks or
1ms (the longer period is applied) is equal to or higher than 10–2 or the signal is lost.
l HPCSES stands for "higher-order path consecutive severely errored second".
Consecutive severely errored second (CSES) refers to the second in which the SESs occur
in a consecutive mode and lasts for less than 10 seconds.
l HPUAS stands for "higher-order path unavailable second".
Unavailable second (UAS) refers to the period of unavailable time that begins at the onset
of ten CSESs. When SESs disappear for ten consecutive seconds, the available time begins
from the eleventh second, with the previous ten seconds included.
Relevant Alarms
When the HPBBE, HPES, HPSES, HPCSES, and HPUAS events cross the preset thresholds,
the HP_CROSSTR alarm may be generated.
HPES 50 100
HPSES 20 50
HPUAS 20 50
Probable Causes
The system detects higher order path bit errors according to the B3 byte.
Procedure
See 4.4 Troubleshooting Bit Errors.
----End
Relevant Alarms
The HP_REI alarm occurs at the local node at the same time.
Probable Causes
The system detects the HPFEBBE by the bit 1 to bit 4 of the G1 byte.
Procedure
Clear the corresponding performance events at the opposite end.
----End
Related Alarm
When the VC3BBE, VC3ES, VC3SES, VC3CSES, or VC3UAS performance event crosses the
preset threshold, the LP_CROSSTR alarm can occur.
VC3ES 50 100
VC3SES 20 50
VC3UAS 20 50
Probable Causes
The system detects the VC3BE by the B3 byte.
Procedure
Refer to section 4.4 Troubleshooting Bit Errors.
----End
Related Alarm
At the same time, the LP_REI_VC3 alarm is reported at the local NE.
Probable Causes
The system detects the VC3FEBE by bits 1–4 of the G1 byte.
Procedure
Clear the corresponding performance events at the opposite NE.
----End
Attribute Description
Relevant Alarm
When the LPBBE, LPES, LPSES, LPCSES, and LPUAS events crosses the preset thresholds,
the LP_CROSSTR alarm may be generated.
LPES 50 100
LPSES 20 50
LPUAS 20 50
Probable Causes
The system detects lower order path bit errors by using the BIP2 of the V5 byte (E1 interface
board or Ethernet board) or B3 byte (E3/T3 interface board).
Procedure
See 4.4 Troubleshooting Bit Errors.
----End
l LPFESES stands for "lower order path far end severely errored second".
The far end severely errored second (FESES) refers to the SES detected at the opposite
end.
l LPFECSES stands for "lower order path far end consecutive severely errored second".
The far end consecutive severely errored second (FESES) refers to the CSES detected at
the remote end.
l LPFEUAS stands for "lower order path unavailable second".
The far end unavailable second (UAS) refers to the UAS detected at the remote end.
Relevant Alarm
If the performance event occurs on the tributary board, the LP_REI alarm is generated at the
local NE at the same time. If the performance event occurs on the Ethernet board, the
LP_REI_VC12 alarm is generated at the local NE at the same time
Probable Causes
The system detects lower order path bit errors by using bit 3 of the V5 byte (E1 interface board
or Ethernet board) or bit 1 through bit 4 of the G1 byte (E3/T3 interface board).
Procedure
Clear the corresponding event at the opposite end.
----End
Unit Block
Probable Causes
There are interference signals on the transmission lines.
Procedure
Step 1 Check whether services are accessed at the signal reception end.
Step 3 Check whether the connectors of the transmission lines are properly made.
----End
Unit Block
Probable Causes
There are interference signals on the transmission lines.
Procedure
Step 1 Check whether services are accessed at the signal reception end.
Step 3 Check whether the connectors of the transmission lines are properly made.
----End
Relevant Alarm
If the transmit power crosses the threshold, the RADIO_TSL_HIGH or
RADIO_TSL_LOW alarm can occur.
Relevant Alarm
If the receive power crosses the threshold, the RADIO_RSL_HIGH or RADIO_RSL_LOW
alarm occurs.
Relevant Alarms
If any byte cannot be troubleshooted, the MW_FECUNCOR alarm occurs.
If the transmit power is overly low or high, the receive optical power might be overly low or
high at the opposite end. Thus, bit errors might occur and even the service might be interrupted.
Relevant Alarms
l If the receive optical power at the opposite end is lower than the receiver sensitivity, the
IN_PWR_LOW alarm can occur.
l If the receive optical power at the opposite end is higher than the overload power, the
IN_PWR_HIGH alarm can occur.
Unit dBm
When the receive optical power is excessively low or high, bit errors might occur and the service
might be interrupted.
Relevant Alarms
l If the receive optical power is lower than the receiver sensitivity, the IN_PWR_LOW
alarm can occur.
l If the receive optical power is higher than the receiver sensitivity, the IN_PWR_HIGH
alarm can occur.
Unit 0.1ºC
Relevant Alarm
If the board temperature crosses the threshold, the TEMP_ALARM alarm occurs.
Unit 0.1ºC
Relevant Alarms
None.
C Alarm Management
For the OptiX RTN 600, the NE alarm management function includes the following aspects:
For details of this function, refer to related manuals or online helps of the OptiX iManager
products.
upon query. The maintenance personnel can change the setting as required through the NM
system.
The alarm auto-report function is supported by all boards.
B3_SD_VC3 10-6
Enabled SL4
HP_TIM Disabled
HP_SLM Disabled
HP_UNEQ Disabled
LP_UNEQ Disabled
LP_SLM Disabled
T_ALOS Enabled
BIP_EXC Disabled
BIP_SD Disabled
NOTE
The T_ALOS alarm exists. Disabled PO1, PH1, PD1 and PL3
The NE performance event management function of the OptiX RTN 600 includes:
For details of these function, refer to the manuals or online Help of the NM system.
Setting 15-minute/24-hour SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
performance monitoring IF1B, PO1, PH1, PD1, PL3,EFT4, EMS6, PXC, SCC,
and ODU
Setting 15-minute/24-hour SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
performance event auto-reporting IF1B, PO1, PH1, PD1, PL3, EFT4, EMS6, PXC, SCC,
and ODU
Setting performance thresholds SD1, SL1, SDE, SL4, IFX, IF0A, IF0B, SLE, IF1A,
IF1B, PO1, PH1, PD1, PL3, EFT4 and EMS6
Resetting the performance register SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
IF1B, PO1, PH1, PD1, PL3, EFT4, EMS6 and ODU
Generating performance threshold SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
crossing alarms IF1B, PO1, PH1, PD1, PL3, EFT4 and EMS6
Monitoring UAT events SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
IF1B, PO1, PH1, PD1, PL3, EFT4 and EMS6
Monitoring CSES performance SD1, SL1, SDE, SLE, SL4, IFX, IF0A, IF0B, IF1A,
events IF1B, PO1, PH1, PD1, PL3, EFT4 and EMS6
MS_RDI MS_REI
HP_SLMa HP_LOM
LP_TIM LP_RDI
HP_RDI HP_REI
B1_EXC B1_SD
B2_EXC B2_SD
B3_EXC B3_SD
E1_LOS UP_E1_AIS
BIP_EXC BIP_SD
C2_VCAIS LP_SLM
NOTE
a: The alarm suppression relation works only when the AIS insertion function is enabled. The alarm
suppression relation is invalid in other cases.
F Glossary
1+1 protection A microwave link protection system composed of one working channel
and one protection channel. Two ODUs and two IF boards are used at
each end of a microwave link.
A
ATPC Automatic Transmit Power Control. A method of adjusting the transmit
power based on fading of the transmit signal detected at the receiver.
B
Bit error An error occurs to some bits in the digital code stream after being
received, judged, and regenerated, thus damaging the quality of the
transmitted information.
F
FD Frequency Diversity. Two or more microwave frequencies with certain
frequency space are used to transmit/receive the same signal and
selection is then performed between the two signals to ease the impact
of fading.
I
IDU Indoor Unit. The indoor unit implements accessing, multiplexing/
demultiplexing, and IF processing for services.
IF Intermediate Frequency. IF is the transitional frequency between the
frequencies of a modulated signal and an RF signal.
Line board A board that processes the services carried on line. As the OptiX RTN
600 involves SDH fiber line, STM-1 cable line, and microwave line, the
line boards include SDH optical interface board, STM-1 electrical
interface board, and IF board.
N
NE Network Element. An NE contains both the hardware and the software
running on it. One NE is at least equipped with one SCC board which
manages and monitors the entire network element. NE software runs on
the SCC board.
O
ODU Outdoor Unit. The outdoor unit implements frequency conversion and
amplification for RF signals.
Orderwire Orderwire is able to provide voice communication for operators or
maintenance engineers at different workstation.
P
PDH Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bit
stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s
into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s rates.
S
SD Space Diversity. Two or more antennas separated by a specific distance
transmit/receive the same signal and selection is then performed between
the two signals to ease the impact of fading. Currently, only receive SD
is used.
SDH Synchronous Digital Hierarchy. A hierarchical set of digital transport
structures, standardized for the transport of suitably adapted payloads
over physical transmission networks.
T
T2000 A subnet management system (SNMS). In the telecommunication
management network architecture, the T2000 is located between the NE
level and network level, which can supports all NE level functions and
part of the network level management functions.
Trail A type of transport entity, mainly engaged in transferring signal from the
input of the trail source to the output of the trail sink, and monitoring the
integrality of the transferred signal.
V
VC Virtual Container. The information structure used to support path layer
connections in the SDH. It consists of information payload, and path
overhead (POH) information fields organized in a block frame structure
which repeats every 125 or 500 microseconds.
W
Web LCT Web LCT is located in the NE management layer of a transmission
network. It performs management for a single NE.
A
AIS Alarm Indication Signal
APS Automatic Protection Switching
ASIC Application Specific Integrated Circuit
ATM Asynchronous Transfer Mode
ATPC Automatic Transmit Power Control
AU Administrative Unit
AU-4 Administrative Unit -4
B
BBE Background Block Error
BER Bit Error Rate
BIOS Basic Input Output System
BIP Bit-Interleaved Parity
C
CPU Central Processing Unit
D
DDF Digital Distribution Frame
E
ECC Embedded Control Channel
F
FCS Frame Check Sequence
FD Frequency Diversity
FEC Forward Error Correction
FIFO First In First Out
FPGA Field Programmable Gate Array
G
GFP Generic Framing Procedure
H
HP Higher Order Path
HSB Hot Standby
HSM Hitless Switch Mode
I
IDU Indoor Unit
IE Internet Explorer
IF Intermediate Frequency
L
LCAS Link Capacity Adjustment Scheme
LCT Generation-Local Craft Terminal
LOS Loss Of Signal
LP Lower Order Path
M
MAC Medium Access Control
MODEM MOdulator-DEModulator
MS Multiplex Section
O
ODU Outdoor Unit
P
PDH Plesiochronous Digital Hierarchy
PRBS Pseudo-random binary sequence
Q
QPSK Quadrature Phase Shift Keying
R
RDI Remote Defect Indication
REI Remote Error Indication
RMON Remote Monitoring
RS Regenerator Section
RSL Received Signal Level
RTC Real-time Clock
RTN Radio Transmission Node
S
SD Space Diversity
SDH Synchronous Digital Hierarchy
SES Severely Errored Seconds
SFP Small Form-Factor Pluggable
SNCP Sub-Network Connection Protection
STM-1 SDH Transport Module -1
T
TU Tributary Unit
U
UAS Unavailable Seconds
UAT Unavailable Time
UNI user-network interface
V
VB Virtual Bridge
VC Virtual Container
VC-12 Virtual Container -12
VC-3 Virtual Container -3
VC-4 Virtual Container -4
VC12 Virtual Container -12
VC3 Virtual Container -3
VC4 Virtual Container -4
VCG Virtual Concatenation Group
VLAN Virtual LAN
W
WS Wayside
X
XPIC Cross-polarization interference cancellation
Index
A BDTMPCUR, B-24
BDTMPMAX, B-24
A_LOC, A-10 BDTMPMIN, B-24
alarm, A-1 BIP_EXC, A-32
AIS insertion, C-3 BIP_SD, A-33
auto-report, C-2 board
bit error threshold, C-2 inserting, 5-23
corrective procedure, A-10 removing, 5-21
level, C-1 BOOTROM_BAD, A-33
list, A-1
management function, board level, C-1 C
management function, NE level, C-1
reversion, C-2 C2_VCAIS, A-35
suppression, C-1 cleaning fiber adapters, 5-37
suppression relation, E-1 cleaning fiber connectors
UNEQ insertion, C-4 using cartridge cleaners, 5-34
alarm management, C-1 using lens tissue, 5-36
ALM_GFP_dCSF, A-12 CONFIG_NOSUPPORT, A-35
ALM_GFP_dLFD, A-13
ALM_RTC_FAIL, A-14 D
APS_FAIL, A-15
APS_INDI, A-16 DBMS_ERROR, A-37
APS_MANUAL_STOP, A-11 DBMS_PROTECT_MODE, A-39
AU_AIS, A-17 DN_E1_AIS, A-40
AU_LOP, A-19
AUPJCHIGH, B-6 E
AUPJCLOW, B-6
AUPJCNEW, B-6 E1_LOC, A-41
automatic release E1_LOS, A-42
loopback operation, 5-20 E3_LCV_SDH, B-19
shut down the laser, 5-20 E3_LES_SDH, B-19
E3_LSES_SDH, B-19
B emergency maintenance, 3-1
ESN_FAILED, A-43
B1_EXC, A-20 ESN_INVALID, A-44
B1_SD, A-21 ETH_LOS, A-45
B2_EXC, A-22 Ethernet board
B2_SD, A-23 Ethernet test frame, 5-18
B3_EXC, A-24 Ethernet service processing board, 5-11
B3_EXC_VC3, A-25 EXT_SYNC_LOS, A-46
B3_SD, A-26
B3_SD_VC3, A-27 F
BD_NOT_INSTALLED, A-28
BD_STATUS, A-29 F1PORT_FAILED, A-48
L M
LASER_CLOSED, A-74 MOD_TYPE_MISMATCH, A-114
LASER_MOD_ERR_EX, A-75 MS_AIS, A-115
LCAS_FOPR, A-76 MS_CROSSTR, A-116
LCAS_FOPT, A-77 MS_RDI, A-117
LCAS_PLCR, A-79 MS_REI, A-118
LCAS_PLCT, A-80 MSAD_CROSSTR, A-119
LCAS_TLCR, A-81 MSBBE, B-10
LCAS_TLCT, A-83 MSCSES, B-10
LCS_LIMITED, A-84 MSES, B-10
LICENSE_ERR, A-86 MSFEBBE, B-11
U
UP_E1_AIS, A-173
V
VC3BBE, B-15
VC3CSES, B-15
VC3ES, B-15
VC3FEBBE, B-16
VC3FECSES, B-16
VC3FEES, B-16
VC3FESES, B-16
VC3FEUAS, B-16
VC3SES, B-15
VC3UAS, B-15
VCAT_LOA, A-175
VCAT_LOM_VC12, A-176