Академический Документы
Профессиональный Документы
Культура Документы
V100R009C00
Maintenance Guide
Issue 02
Date 2016-08-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
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 all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document provides the guidelines to maintaining the OptiX RTN 905E. It also describes
the alarms and performance events that are required for troubleshooting during the
maintenance.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Update Description
Contents
3 Routine Maintenance..................................................................................................................24
4 Network Monitoring...................................................................................................................28
4.1 Checking the NE Status................................................................................................................................................ 29
4.2 Checking the Board Status........................................................................................................................................... 30
4.3 Alarm and Performance Data Query............................................................................................................................ 31
4.3.1 Browsing Current Alarms..........................................................................................................................................31
4.3.2 Browsing Historical Alarms...................................................................................................................................... 36
4.3.3 Browsing Current Performance Events..................................................................................................................... 39
4.3.4 Browsing Historical Performance Events..................................................................................................................41
4.3.5 Browsing the Performance Event Threshold-Crossing Records............................................................................... 42
5 Troubleshooting.......................................................................................................................... 91
5.1 General Troubleshooting Procedure............................................................................................................................. 93
5.2 Troubleshooting Service Interruptions......................................................................................................................... 95
A.3.27 BUS_ERR.............................................................................................................................................................303
A.3.28 CES_ACR_LOCK_ABN..................................................................................................................................... 305
A.3.29 CES_JTROVR_EXC............................................................................................................................................ 307
A.3.30 CES_JTRUDR_EXC............................................................................................................................................ 308
A.3.31 CES_LOSPKT_EXC............................................................................................................................................ 309
A.3.32 CES_MALPKT_EXC...........................................................................................................................................310
A.3.33 CES_MISORDERPKT_EXC............................................................................................................................... 311
A.3.34 CES_RDI.............................................................................................................................................................. 312
A.3.35 CES_STRAYPKT_EXC.......................................................................................................................................313
A.3.36 CESPW_OPPOSITE_ACFAULT.........................................................................................................................313
A.3.37 CESPW_OPPOSITE_RAI................................................................................................................................... 314
A.3.38 CLK_LOCK_FAIL...............................................................................................................................................315
A.3.39 CLK_NO_TRACE_MODE..................................................................................................................................316
A.3.40 COMMUN_FAIL................................................................................................................................................. 317
A.3.41 COMPRESS_MISMATCH.................................................................................................................................. 318
A.3.42 COM_EXTECC_FULL........................................................................................................................................319
A.3.43 CONFIG_NOSUPPORT...................................................................................................................................... 320
A.3.44 DBMS_DELETE.................................................................................................................................................. 322
A.3.45 DBMS_ERROR....................................................................................................................................................323
A.3.46 DBMS_PROTECT_MODE................................................................................................................................. 325
A.3.47 DCNLINK_OVER............................................................................................................................................... 325
A.3.48 DCNSIZE_OVER.................................................................................................................................................326
A.3.49 DDN_LFA............................................................................................................................................................ 327
A.3.50 DOWN_E1_AIS................................................................................................................................................... 328
A.3.51 DROPRATIO_OVER........................................................................................................................................... 329
A.3.52 E1_LOC................................................................................................................................................................ 331
A.3.53 E1_LOS................................................................................................................................................................ 332
A.3.54 ELAN_SMAC_FLAPPING................................................................................................................................. 333
A.3.55 ENVHUM_SENSOR_FAIL.................................................................................................................................334
A.3.56 ENVTEMP_SENSOR_FAIL................................................................................................................................335
A.3.57 ENVTEMP1_SENSOR_FAIL..............................................................................................................................336
A.3.58 ENVTEMP2_SENSOR_FAIL..............................................................................................................................337
A.3.59 ERPS_IN_PROTECTION....................................................................................................................................339
A.3.60 ETH_APS_LOST................................................................................................................................................. 340
A.3.61 ETH_APS_PATH_MISMATCH...........................................................................................................................341
A.3.62 ETH_APS_SWITCH_FAIL................................................................................................................................. 342
A.3.63 ETH_APS_TYPE_MISMATCH.......................................................................................................................... 343
A.3.64 ETH_AUTO_LINK_DOWN................................................................................................................................344
A.3.65 ETH_CFM_AIS....................................................................................................................................................345
A.3.66 ETH_CFM_LOC.................................................................................................................................................. 346
A.3.67 ETH_CFM_MISMERGE..................................................................................................................................... 348
A.3.68 ETH_CFM_RDI................................................................................................................................................... 350
A.3.195 MS_CROSSTR...................................................................................................................................................491
A.3.196 MS_RDI..............................................................................................................................................................493
A.3.197 MS_REI.............................................................................................................................................................. 494
A.3.198 MSAD_CROSSTR............................................................................................................................................. 495
A.3.199 MULTI_RPL_OWNER...................................................................................................................................... 496
A.3.200 MW_AM_TEST................................................................................................................................................. 497
A.3.201 MW_BER_EXC................................................................................................................................................. 497
A.3.202 MW_BER_SD.................................................................................................................................................... 501
A.3.203 MW_CFG_MISMATCH.................................................................................................................................... 504
A.3.204 MW_CONT_WAVE........................................................................................................................................... 507
A.3.205 MW_E1_LOST...................................................................................................................................................508
A.3.206 MW_FEC_UNCOR............................................................................................................................................509
A.3.207 MW_LIM............................................................................................................................................................512
A.3.208 MW_LOF........................................................................................................................................................... 514
A.3.209 MW_RDI............................................................................................................................................................ 518
A.3.210 NB_CFG_MISMATCH...................................................................................................................................... 519
A.3.211 NB_UNREACHABLE....................................................................................................................................... 522
A.3.212 NEIP_CONFUSION...........................................................................................................................................523
A.3.213 NESF_LOST.......................................................................................................................................................524
A.3.214 NESOFT_MM.................................................................................................................................................... 525
A.3.215 NTP_SYNC_FAIL..............................................................................................................................................526
A.3.216 ODC_BATTERY_CURRENT_ABN................................................................................................................. 527
A.3.217 ODC_BATTERY_PWRDOWN......................................................................................................................... 529
A.3.218 ODC_DOOR_OPEN.......................................................................................................................................... 531
A.3.219 ODC_FAN_FAILED.......................................................................................................................................... 533
A.3.220 ODC_HUMI_ABN.............................................................................................................................................534
A.3.221 ODC_LOAD_PWRDOWN................................................................................................................................535
A.3.222 ODC_MDL_ABN...............................................................................................................................................538
A.3.223 ODC_POWER_FAIL......................................................................................................................................... 540
A.3.224 ODC_SMOKE_OVER....................................................................................................................................... 542
A.3.225 ODC_SURGE_PROTECTION_FAIL............................................................................................................... 543
A.3.226 ODC_TEC_ALM............................................................................................................................................... 545
A.3.227 ODC_TEMP_ABN.............................................................................................................................................546
A.3.228 ODC_WATER_ALM..........................................................................................................................................548
A.3.229 OSPFNBRSTATECHANGE.............................................................................................................................. 549
A.3.230 OUT_PWR_ABN............................................................................................................................................... 551
A.3.231 OUT1TEMP_SENSOR_FAIL............................................................................................................................552
A.3.232 OUT2TEMP_SENSOR_FAIL............................................................................................................................554
A.3.233 PASSWORD_NEED_CHANGE........................................................................................................................555
A.3.234 PATCH_BD_EXCLUDE....................................................................................................................................556
A.3.235 PATCH_BD_MATCH_FAIL.............................................................................................................................. 556
A.3.236 PATCH_CHGSCC_NOTMATCH......................................................................................................................557
A.3.279 RPS_INDI...........................................................................................................................................................606
A.3.280 RS_CROSSTR....................................................................................................................................................608
A.3.281 RTC_FAIL.......................................................................................................................................................... 609
A.3.282 RT_TBL_LACK................................................................................................................................................. 610
A.3.283 S1_SYN_CHANGE............................................................................................................................................611
A.3.284 SEC_RADIUS_FAIL..........................................................................................................................................612
A.3.285 SECU_ALM....................................................................................................................................................... 614
A.3.286 SOFTWARE_UNCOMMIT............................................................................................................................... 615
A.3.287 SRV_SHUTDOWN_LD.....................................................................................................................................615
A.3.288 SSL_CERT_DAMAGED................................................................................................................................... 616
A.3.289 SSL_CERT_NOENC..........................................................................................................................................617
A.3.290 SSL_CERT_TO_EXPIRE.................................................................................................................................. 618
A.3.291 STORM_CUR_QUENUM_OVER.................................................................................................................... 619
A.3.292 SUBNET_RT_CONFLICT................................................................................................................................ 619
A.3.293 SWDL_ACTIVATED_TIMEOUT..................................................................................................................... 621
A.3.294 SWDL_AUTOMATCH_INH.............................................................................................................................622
A.3.295 SWDL_CHGMNG_NOMATCH....................................................................................................................... 623
A.3.296 SWDL_COMMIT_FAIL.................................................................................................................................... 624
A.3.297 SWDL_INPROCESS......................................................................................................................................... 625
A.3.298 SWDL_NEPKGCHECK.................................................................................................................................... 625
A.3.299 SWDL_PKG_NOBDSOFT................................................................................................................................ 626
A.3.300 SWDL_PKGVER_MM...................................................................................................................................... 627
A.3.301 SWDL_ROLLBACK_FAIL...............................................................................................................................628
A.3.302 SYN_BAD.......................................................................................................................................................... 629
A.3.303 SYNC_C_LOS................................................................................................................................................... 630
A.3.304 SYSLOG_COMM_FAIL....................................................................................................................................631
A.3.305 T_ALOS............................................................................................................................................................. 631
A.3.306 T_LOC................................................................................................................................................................ 633
A.3.307 TEM_HA............................................................................................................................................................ 633
A.3.308 TEM_LA.............................................................................................................................................................634
A.3.309 TEMP_ALARM................................................................................................................................................. 635
A.3.310 TF........................................................................................................................................................................636
A.3.311 THUNDERALM.................................................................................................................................................637
A.3.312 TIME_LOCK_FAIL........................................................................................................................................... 638
A.3.313 TIME_LOS......................................................................................................................................................... 639
A.3.314 TIME_NO_TRACE_MODE.............................................................................................................................. 640
A.3.315 TU_AIS...............................................................................................................................................................641
A.3.316 TU_AIS_VC12................................................................................................................................................... 643
A.3.317 TU_LOP............................................................................................................................................................. 644
A.3.318 TU_LOP_VC12.................................................................................................................................................. 645
A.3.319 TUNNEL_APS_DEGRADED........................................................................................................................... 646
A.3.320 TUNNEL_APS_OUTAGE................................................................................................................................. 648
C.3.11 ETHFCS................................................................................................................................................................841
C.3.12 CES_MISORDERPKTS.......................................................................................................................................842
C.3.13 CES_STRAYPKTS...............................................................................................................................................843
C.3.14 CES_MALPKTS...................................................................................................................................................843
C.3.15 CES_JTRUDR...................................................................................................................................................... 844
C.3.16 CES_JTROVR...................................................................................................................................................... 845
C.3.17 CES_LOSPKTS.................................................................................................................................................... 845
G Indicators................................................................................................................................... 889
H Glossary......................................................................................................................................897
1 Safety Precautions
This topic describes the safety precautions that you must follow when installing, operating,
and maintaining Huawei devices.
Grounding Requirements
The grounding requirements are applicable to the device that needs to be grounded.
l When installing the device, always connect the grounding facilities first. When removing
the device, always disconnect the grounding facilities last.
l Ensure that the grounding conductor is intact.
l Do not operate the device in the absence of a suitably installed grounding conductor.
l The device must be connected to the PGND permanently. Before operating the device,
check the electrical connections of the device, and ensure that the device is properly
grounded.
Human Safety
l When there is a risk of a lightning strike, do not operate the fixed terminal or touch the
cables.
l When there is risk of a lightning strike, unplug the AC power connector. Do not use the
fixed terminal or touch the terminal or antenna connector.
NOTE
The preceding requirements apply to wireless fixed station terminals.
l To avoid electric shocks, do not connect safety extra-low voltage (SELV) circuits to
telephone-network voltage (TNV) circuits.
l Do not look into optical ports without eye protection. Otherwise, human eyes may be
hurt by laser beams.
l Before operating the device, wear an ESD protective coat, ESD gloves, and an ESD
wrist strap. In addition, you need to get off the conductive objects, such as jewelry and
watches, to prevent electric shock and burn.
l In case of fire, escape from the building or site where the device is located and press the
fire alarm bell or dial the telephone number for fire alarms. Do not enter the burning
building again in any situation.
Device Safety
l Before any operation, install the device firmly on the ground or other rigid objects, such
as on a wall or in a rack.
l When the system is working, ensure that the ventilation hole is not blocked.
l When installing the front panel, use a tool to tighten the screws firmly, if required.
l After installing the device, clean up the packing materials.
Table 1-1 Warning and safety symbols of the OptiX RTN 905E
Symbol Indication
Symbol Indication
High Voltage
DANGER
l A high-voltage power supply provides power for device operations. Direct human contact
with the high voltage power supply or human contact through damp objects can be fatal.
l Unspecified or unauthorized high voltage operations could result in fire or electric shock,
or both.
Thunderstorm
The requirements apply only to wireless base stations or devices with antennas and feeders.
DANGER
Do not perform operations on high voltage, AC power, towers, or backstays in stormy
weather conditions.
CAUTION
Before powering on a device, ground the device. Otherwise, the safety of humans and the
device cannot be ensured.
If a high leakage current mark is labeled near the power connector of the device, you must
connect the PGND terminal on the shell to the ground before connecting the device to an A/C
input power supply. This is to prevent the electric shock caused by leakage current of the
device.
Power Cables
DANGER
Do not install or remove the power cable with a live line. Transient contact between the core
of the power cable and the conductor may generate electric arc or spark, which may cause fire
or eye injury.
l Before installing or removing power cables, you must power off the device.
l Before connecting a power cable, you must ensure that the label on the power cable is
correct.
DANGER
Installing or removing a device is prohibited if the device is on.
DANGER
Do not install or remove the power cables of the equipment when it is powered on.
Short Circuits
When installing and maintaining devices, place and use the associated tools and instruments
in accordance with regulations to avoid short-circuits caused by metal objects.
NOTICE
To avoid short-circuits when using a tool (such as a screwdriver), do not place the tool on the
ventilation plate of the subrack.
NOTICE
Prevent any screws from dropping into the subrack or chassis to avoid short-circuits.
Fuse
CAUTION
If the fuse on a device blows, replace the fuse with a fuse of the same type and specifications
to ensure safe operation of the device.
Electrostatic Discharge
NOTICE
The static electricity generated by the human body may damage the electrostatic sensitive
components on the board, such as the large-scale integrated circuit (LSI).
l The human body can generate static electromagnetic fields in the following situations:
physical movement, clothing friction, friction between shoes and the ground, plastics in
the hand. Such static electromagnetic effects can remain for an appreciable time.
l Before operating a device, circuit boards, or ASICs, wear an ESD wrist strap that is
properly grounded. The ESD wrist strap can prevent the electrostatic-sensitive
components from being damaged by the static electricity in the human body.
Figure 1-1 shows the method of wearing an ESD wrist strap.
DANGER
Do not place or operate devices in an environment of flammable or explosive air or gas.
DANGER
Before operating a storage battery, you must read the safety precautions carefully and be
familiar with the method of connecting a storage battery.
l Incorrect operations of storage batteries cause hazards. During operation, prevent any
short-circuit, and prevent the electrolyte from overflowing or leakage.
l If the electrolyte overflows, it causes potential hazards to the device. The electrolyte may
corrode metal parts and the circuit boards, and ultimately damage the circuit boards.
l A storage battery contains a great deal of energy. Misoperations may cause a short-
circuit, which leads to human injuries.
Basic Precautions
To ensure safety, note the following points before installing or maintaining the storage
battery:
l Use special insulation tools.
l Wear an eye protector and take effective protection measures.
l Wear rubber gloves and a protection coat to prevent the hazard caused by the
overflowing electrolyte.
l When handling the storage battery, ensure that its electrodes are upward. Leaning or
reversing the storage battery is prohibited.
l Before installing or maintaining the storage battery, ensure that the storage battery is
disconnected from the power supply that charges the storage battery.
Short-Circuit
DANGER
A battery short-circuit may cause human injuries. Although the voltage of an ordinary battery
is low, the instantaneous high current caused by a short-circuit emits a great deal of energy.
Avoid any short-circuit of batteries caused by metal objects. If possible, disconnect the
working battery before performing other operations.
Hazardous Gas
NOTICE
Do not use any unsealed lead-acid storage battery. Lay a storage battery horizontally and fix it
properly to prevent the battery from emitting flammable gas, which may cause fire or device
erosion.
Working lead-acid storage batteries emit flammable gas. Therefore, ventilation and
fireproofing measures must be taken at the sites where lead-acid storage batteries are placed.
Battery Temperature
NOTICE
If a battery overheats, the battery may be deformed or damaged, and the electrolyte may
overflow.
When the temperature of the battery is higher than 60C, you need to check whether the
electrolyte overflows. If the electrolyte overflows, take appropriate measures immediately.
Battery Leakage
NOTICE
In the event of acid overflow or spillage, neutralize the acid and clean it up appropriately.
When handling a leaky battery, protect against the possible damage caused by the acid. When
you find the electrolyte leaks, you can use the following substances to counteract and absorb
the leaking electrolyte:
In the event of acid overflow or spillage, neutralize the acid and clean it up as recommended
by the battery manufacturer and any local regulations for acid disposal.
If a person contacts battery electrolyte, clean the skin that contacts the battery electrolyte
immediately by using water. In case of a severe situation, the person must be sent to a hospital
immediately.
1.6 Radiation
This topic describes safety precautions for electromagnetic exposure and lasers.
DANGER
When installing or maintaining an optical interface board or optical fibers, avoid direct eye
exposure to the laser beams launched from the optical interface board or fiber connectors. The
laser beam can cause damage to your eyes.
NOTICE
If fiber connectors or flanges are contaminated, optical power commissioning is seriously
affected. Therefore, the two endfaces and flange of every external fiber must be cleaned
before the fiber is led into the equipment through the ODF for being inserted into an optical
interface on the equipment.
The fiber connectors and optical interfaces of the lasers must be cleaned with the following
special cleaning tools and materials:
l Special cleaning solvent: It is preferred to use isoamylol. Propyl alcohol, however, can
also be used. It is prohibited that you use alcohol and formalin.
l Non-woven lens tissue
l Special compressed gas
l Cotton stick (medical cotton or long fiber cotton)
l Special cleaning roll, used with the recommended cleaning solvent
l Special magnifier for fiber connectors
For cleaning steps, see Task Collection "Cleaning Fiber Connectors and Adapters" in the
OptiX RTN 905E Radio Transmission System Maintenance and Troubleshooting.
Figure 1-2 shows a slanting optical interface, and Figure 1-3 shows a level optical interface.
Slanting optical
interface
Level optical
interface
NOTICE
Ensure that all personnel are beyond the transmit direction of a working antenna.
1.6.4 Laser
This topic describes safety precautions for lasers.
CAUTION
When handling optical fibers, do not stand close to, or look into the optical fiber outlet
directly without eye protection.
Laser transceivers are used in the optical transmission system and associated test tools. The
laser transmitted through the bare optical fiber produces a small beam of light, and therefore it
has very high power density and is invisible to human eyes. When a beam of light enters eyes,
the eyes may be damaged.
In normal cases, viewing an un-terminated optical fiber or a damaged optical fiber without
eye protection at a distance greater than 150 mm does not cause eye injury. Eye injury may
occur, however, if an optical tool such as a microscope, magnifying glass, or eye loupe is used
to view an un-terminated optical fiber.
l All operations should be performed by authorized personnel who have completed the
required training courses.
l Wear a pair of eye-protective glasses when you are handling lasers or fibers.
l Ensure that the optical source is switched off before disconnecting optical fiber
connectors.
l Do not look into the end of an exposed fiber or an open connector when you are not sure
whether the optical source is switched off.
l Use an optical power meter to measure the optical power and ensure that the optical
source is switched off.
l Before opening the front door of an optical transmission device, ensure that you are not
exposed to laser radiation.
l Do not use an optical tool such as a microscope, a magnifying glass, or an eye loupe to
view the optical connector or fiber that is transmitting optical signals.
1.6.5 Microwave
When installing and maintaining the equipment of Huawei, follow the safety precautions of
microwave to ensure the safety of the human body and the equipment.
CAUTION
Strong radio frequency can harm the human body.
When installing or maintaining an aerial on the tower or mast that is installed with multiple
aerials, switch off the transmitter in advance.
CAUTION
When working at heights, be cautious to prevent objects from falling down.
CAUTION
When heavy objects are being hoisted, do not walk below the cantilever or hoisted objects.
Checking Ladders
l Before using a ladder, check whether the ladder is damaged. After checking that the
ladder is in good condition, you can use the ladder.
l Before using a ladder, you should know the maximum weight capacity of the ladder.
Avoid overweighing the ladder.
Placing Ladders
The proper slant angle of the ladder is 75 degrees. You can measure the slant angle of the
ladder with an angle square or your arms, as shown in Figure 1-5. When using a ladder, to
prevent the ladder from sliding, ensure that the wider feet of the ladder are downward, or take
protection measures for the ladder feet. Ensure that the ladder is placed securely.
Climbing Up a Ladder
When climbing up a ladder, pay attention to the following points:
l Ensure that the center of gravity of your body does not deviate from the edges of the two
long sides.
l Before operations, ensure that your body is stable to reduce risks.
l Do not climb higher than the fourth rung of the ladder (counted from up to down).
If you want to climb up a roof, ensure that the ladder top is at least one meter higher than the
roof, as shown in Figure 1-6.
Figure 1-6 Ladder top being one meter higher than the roof
Drilling Holes
CAUTION
Do not drill holes on the cabinet without prior permission. Drilling holes without complying
with the requirements affects the electromagnetic shielding performance of the cabinet and
damages the cables inside the cabinet. In addition, if the scraps caused by drilling enter the
cabinet, the printed circuit boards (PCBs) may be short-circuited.
l Before drilling a hole on the cabinet, remove the cables inside the cabinet.
l Wear an eye protector when drilling holes. This is to prevent eyes from being injured by
the splashing metal scraps.
l Wear protection gloves when drilling holes.
l Take measures to prevent the metallic scraps from falling into the cabinet. After the
drilling, clean up the metallic scraps.
Sharp Objects
CAUTION
Wear protection gloves when carrying the device. This is to prevent hands from being injured
by the sharp edges of the device.
Fans
l When replacing parts, place the objects such as the parts, screws, and tools properly. This
is to prevent them from falling into the operating fans, which damages the fans or device.
l When replacing the parts near fans, keep your fingers or boards from touching operating
fans before the fans are powered off and stop running. Otherwise, the hands or the
boards are damaged.
CAUTION
l The carrier must be prepared for load bearing before carrying heavy objects. This is to
prevent the carrier from being strained or pressed by the heavy objects.
l When you pull a chassis out of the cabinet, pay attention to the unstable or heavy objects
on the cabinet. This is to prevent the heavy objects on the cabinet top from falling down,
which may hurt you.
l Generally, two persons are needed to carry a chassis. It is prohibited that only one person
carries a heavy chassis. When carrying a chassis, the carriers should stretch their backs
and move stably to avoid being strained.
l When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold
the handles of the modules installed in the chassis, such as the power modules, fan
modules, and boards.
NOTICE
When inserting a board, wear an ESD wrist strap or ESD gloves, and handle the board gently
to avoid distorting pins on the backplane.
NOTICE
Bind the signal cables separately from the high-current or high-voltage cables.
Routing Cables
In the case of extremely low temperature, heavy shock or vibration may damage the plastic
skin of the cables. To ensure the construction safety, comply with the following requirements:
l When installing cables, ensure that the environment temperature is above 0C.
l If the cables are stored in a place where the ambient temperature is below 0C, transfer
them to a place at room temperature and store the cables for more than 24 hours before
installation.
l Handle the cables gently, especially in a low-temperature environment. Do not perform
any improper operations, for example, pushing the cables down directly from a truck.
High Temperature
CAUTION
If the ambient temperature exceeds 55C, the temperature of the front panel surface marked
the flag may exceed 70C. When touching the front panel of the board in such an
environment, you must wear the protection gloves.
IF Cables
CAUTION
Before installing or removing an IF cable, you must turn off the power switch of the IF board.
This topic provides notices for the operations that may cause bodily injury or equipment
damage if they are not performed properly during the commissioning and maintenance of
microwave equipment.
I : ON
Procedure
Step 1 For an IF board with a power switch:
1. Shut down the ODU power supply.
For the OptiX RTN 905E 1E, shut down the IDU power supply.
For the OptiX RTN 905E 2E, follow instructions in 2.1 Operation Guide for the
Toggle Lever Switch to power off the ODU.
1 2
1. Ensure that the IF jumper is already connected to its IF cable and ODU.
2. Disconnect/Connect the IF jumper.
----End
Procedure
Step 1 For an IF board with a power switch:
1. Shut down the ODU power supply.
For the OptiX RTN 905E 1E, shut down the IDU power supply.
For the OptiX RTN 905E 2E, follow instructions in 2.1 Operation Guide for the
Toggle Lever Switch to power off the ODU.
1 2
----End
3 Routine Maintenance
Routine maintenance operations are performed to detect and rectify hidden faults before the
hidden faults cause damage to equipment and affect services. Routine maintenance operations
are preventive measures.
Routine maintenance items are classified into routine maintenance items carried out on the
NMS, field maintenance items for indoor equipment, and field maintenance items for outdoor
equipment.
NOTE
4.1 Checking the NE Every day l If the NE icon is green, the NE operates
Status properly.
l If the NE icon is gray, the NE is
unreachable due to DCN faults.
l If the NE icon is in other colors, alarms
are reported or exceptions occur. You
need to troubleshoot in time.
4.3.1 Browsing Current Every day l Handle the alarms by referring to A.3
Alarms Alarms and Handling Procedures.
l For port alarms due to the interconnected
equipment, see 4.9.5 Reversing Alarms
for Service Ports to reduce the number
of alarms and prevent interference to
emergent alarms.
Browsing abnormal events Every week l Security events are generally records of
normal operations. Investigate the illegal
operations if there are any.
l Abnormal events about equipment have
been properly solved.
4.3.3 Browsing Current Every week l Gauge type performance events such as
Performance Events the board temperature and laser power
are stable.
4.3.4 Browsing Historical Every week
Performance Events l Bit error type performance events meet
requirements on link availability.
4.4.1 Querying the Every week l Historical received signal levels do not
Historical Transmit Power exceed the fade margin for a long time.
and Receive Power l When automatic transmit power control
(ATPC) is disabled, historical
transmitted signal levels are allowed to
be 3 dB larger or smaller than the
specified value.
Testing IF 1+1 Protection Half a year For equipment that is configured with 1+1
Switching (OptiX RTN 905 protection, perform manual switching to
1E)Testing IF 1+1 check whether the protection has taken
Protection Switching (OptiX effect. After the test is completed, clear the
RTN 905 2E) switching to restore to the normal protection
status.
NOTE
During the 1+1 protection switching, the
protected services are interrupted. It is
recommended that you perform the 1+1
protection switching when the traffic is light.
NOTE
For the RTN 905 2E, an IF port does not report service alarms (such as MW_LOF and IF_CABLE_OPEN),
IF performance events, or RMON performance statistics if the corresponding logical ODU board is not added
for the port. This minimizes the impact of invalid alarms on routine maintenance.
Maximum number of alarms and performance events that the NE can store
The NE can record and store NE alarm and performance data in a 15-minute or 24-hour
monitoring period.
NOTE
You can use the performance management system (PMS) on the U2000 to store historical performance
data for a long term.
Item Specifications
NOTE
a:An area close to a pollution source refers to the area that covers a radius within any of the following
values:
l 3.7 km away from salty waters (such as an ocean and salty water)
l 3 km away from severe pollution sources (such as iron refinery works, and coal mines)
l 2 km away from intermediate pollution sources (such as chemical plants, rubber processing works,
and electroplating workshops)
l 1 km away from light pollution sources (such as food processing works, leather working plants, and
heating boilers).
4 Network Monitoring
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Precautions
NOTE
By default, the color of the NE icon on the U2000 indicates the NE status.
Procedure
Step 1 Query NE running status.
NOTE
You can also determine NE running status by referring to information on the Legend tab.
NOTE
Complete the following steps to check NE running status from the WebLCT:
1. Query Communication status and Login status of the NE in NE List.
2. If Login status is Offline, log in to the NE.
3. Select the NE and click Log in.
4. Set User Name and Password.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Procedure
Step 1 Query board running status.
3
Determine the board
1 running status by referring
to legend information.
4
Right-click
the desired
NE.
NOTE
Complete the following step to query board running status from the WebLCT:
Click the Slot Layout tab in NE Explorer.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Procedure
Step 1 Open the current alarm window.
1
2
6
Select the desired
8 NEs.
10
11
NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
The Browse Current Alarms tab page is displayed by default.
----End
Related Information
A current alarm refers to an alarm that is not cleared.
By U2000, you can browse the network-wide alarms based on the alarm severity by clicking
the alarm indicators in the upper right corner.
By default, the number shown by each indicator indicates the number of current network-wide alarms, which
are not cleared, of the specific severity.
By Web LCT, you can also click an alarm indicator on the toolbar to display the NE alarms of
the specific severity.
From left to right, the alarm indicators and corresponding alarm severities are as follows:
l Red: critical alarm
Prerequisites
You must be an NM user with NE monitor authority or higher.
Procedure
Step 1 Open the historical alarm window.
6
Select the desired
8 NEs.
10
11
NOTE
Complete the following steps to browse current alarms from the WebLCT:
Select the NE from the NE Explorer and click in the tool bar.
Click the Browse Historical alarms tab.
----End
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable
the performance monitoring function, see Configuring the Performance Monitoring
Status of NEs.
l You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Open the performance data window.
1
3
Configure the query type.
Select the desired For example, Measure is
NEs. selected here.
7 8
NOTE
Complete the following steps to query current performance data from the WebLCT:
Select the desired board in the NE Explorer and choose Performance > Current Performance from the
Function Tree.
----End
Prerequisites
l The performance monitoring function must be enabled. For details about how to enable
the performance monitoring function, see Configuring the Performance Monitoring
Status of NEs.
l You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Open the performance data window.
1
2
3
6
4
7
Select Data Source.
6 If you select Query from NMS, historical performance data will be obtained from
Configure the query type. For the U2000 database.
example, Count is selected here. 6 If you select Query from NE, a message will be sent through an interface to obtain
historical performance data from NEs.
6 Historical performance data of NEs changes with services. To query the latest
historical performance data of NEs and save the data to the U2000 database, set
Data Source to Query from NE and select Save to Database. Then the data is
saved to the U2000 database and you can query it from the database by selecting
Query from NMS next time.
NOTE
Complete the following steps to query historical performance data from the Web LCT:
Select the desired board in the NE Explorer and choose Performance > Historical Performance from the
Function Tree.
The Web LCT does not support data source selection.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Open the Performance Threshold-Crossing Record window.
2
3
NOTE
Complete the following steps to query performance threshold-crossing records from the WebLCT:
Select a desired board in the NE explorer and choose Performance > Threshold-Crossing Record from the
Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
UAT refers to a period of 10 consecutive seconds during which the bit error ratio per second
of the digital signal in either of the transmission directions of a transmission system is inferior
to 10-3. These 10 seconds are considered to be part of the unavailable time.
Procedure
Step 1 Open the UAT window
1
2
3
5
Specify the time period, data source
6 and functional block type.
Select the
desired board.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Query historical receive power or transmit power information.
Click Draw.
The power curve is
1 displayed.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The IF boards and the ODUs to which the IF boards are connected have been added in
the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Query how the SNR or Root-mean-square (RMS) error changes on microwave links.
In the NE Explorer,
select the desired IF 4
board.
Click Draw.
The SNR or MSE curve is
displayed.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
Procedure
Step 1 Right-click a microwave link in the main topology and choose Microwave Link
Performance Statistics.
1
Right-click the desired
microwave link.
NOTE
Uncheck Auto Refresh. Click Save as to save current performance of the microwave link into a TXT file.
Complete the following steps to query current performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
Prerequisites
You must be an NM user with NE monitor authority or higher.
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Query historical performance of the microwave link.
1
Right-click the desired
microwave link.
NOTE
Complete the following steps to query historical performance of the microwave link from the WebLCT:
Select the desired microwave link in the NE Explorer and choose Configuration > Microwave Link
Performance from the Function Tree.
----End
Context
NOTE
You can query real-time performance data and recent performance data.
Ethernet performance is monitored through RMON. Available performance monitoring periods include 30s,
30 minutes, custom period 1 (15 minutes by default), and custom period 2 (24 hours by default).
Prerequisites
l You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation Creating Traffic before monitoring the port
traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation Creating Traffic before monitoring the port
traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
Step 2 Click the Event tab and set the corresponding parameters.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
NOTE
To set parameters for monitoring historical Ethernet performance of multiple NEs on the U2000, choose
Performance > RMON History Control Group Management from the main menu.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON
History Control Group.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding boards must be added in the NE Panel.
l The objects and performance events to be monitored must be set.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, navigate to the performance query interfaces for different objects
according to the following tables.
Basic Ethernet Select the corresponding board from the Object Tree in the NE
performan porta Explorer. Choose Performance > RMON Performance from
ce/ the Function Tree.
Extended
performan
ce
PLA group PLA 1. In the NE Explorer, select the required NE from the Object
performan group Tree and choose Configuration > Physical Link
ce Aggregation.
2. Select the desired PLA group, right-click, and choose
Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > Link Configuration.
performan 2. Select the desired XPIC group, right-click, and choose
ce Browse Performance from the shortcut menu.
XPIC XPIC 1. In the NE Explorer, select the required NE from the Object
group group Tree and choose Configuration > IF 1+1 Protection.
performan 2. Select the desired 1+1 protection group, right-click, and
ce choose Browse Performance from the shortcut menu.
MPLS MPLS 1. In the NE Explorer, select the required NE from the Object
tunnel Tunnel Tree and choose Configuration > MPLS Management >
performan Unicast Tunnel Management from the Function Tree.
ce 2. Click the Static Tunnel tab.
3. Select one or more tunnels, right-click the tunnel(s), and
choose Browse Performance from the shortcut menu.
L2 VPN- ETH 1. Select the NE from the Object Tree in the NE Explorer.
PW PWE3 Choose Configuration > Ethernet Service Management >
performan service E-Line Service from the Function Tree.
ce 2. Select one or more ETH PWE3 services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
L2 VPN UNI-UNI 1. Select the NE from the Object Tree in the NE Explorer.
performan E-Line Choose Configuration > Ethernet Service Management >
ce service E-Line Service from the Function Tree.
2. Select one or more UNI-UNI E-Line services, right-click the
service(s), and choose Browse Performance from the
shortcut menu.
Port traffic Ports that 1. Select the NE from the Object Tree in the NE Explorer.
classificati perform Choose Configuration > QoS Management > Policy
on complex Management > Port Policy from the Function Tree.
performan traffic 2. Click the Application Object tab.
ce classificati
on 3. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
NOTE
Complete the operation Creating Traffic before monitoring the port
traffic classification performance.
Port DS Ports in a 1. Select the NE from the Object Tree in the NE Explorer.
domain DS Choose Configuration > QoS Management > Diffserv
performan domain Domain Management > Diffserv Domain Management
ce from the Function Tree.
2. Select the desired DS domain.
3. Click the Application Object tab.
4. Select one or multiple ports, right-click and choose Browse
Performance from the shortcut menu.
ETH OAM E-Line 1. In the NE Explorer, select the required NE from the Object
E-Line service Tree and choose Configuration > Ethernet OAM
service Management > Ethernet Service OAM Management.
performan 2. Select the desired MEP, right-click, and choose Browse
ce Performance from the shortcut menu.
MPLS-TP TUNNEL 1. In the NE Explorer, select the required NE from the Object
OAM Tree and choose Configuration > MPLS Management >
Unicast Tunnel Management.
2. Click the MPLS-TP OAM tab.
3. Select the desired MEP, right-click, and choose Browse
Performance from the shortcut menu.
NOTE
If you browse current Ethernet performance using the Web LCT: Select the corresponding board from the
Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring
function on a port, see 4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization
of Ethernet Ports.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
Procedure
Step 1 Set Ethernet performance monitoring parameters.
1
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
The flow monitoring function is enabled on the Ethernet port. To enable the flow monitoring
function on a port, see 4.6.1 Setting Traffic, Physical Bandwidth, or Bandwidth Utilization
of Ethernet Ports.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Background Information
After the flow monitoring function is enabled, the system saves the statistics about the
received traffic and transmitted traffic with an interval of 15 minutes. In normal cases, the
system stores the statistics that are collected in the last 30 days. In the system, every
measurement entry shows the average transmit rate and average receive rate within a period
of 15 minutes. You can query the statistics in the last 30 days.
This operation allows only the queries about port-based Ethernet traffic by using U2000. For
how to query tunnel- or PW-based traffic, see 4.5.1 Browsing Current Ethernet
Performance.
Procedure
Step 1 Query traffic, physical bandwidth, and bandwidth utilization.
1
Select the
desired board. 5
3
Select the port
of the board.
4
Specify the time
period and display
mode.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Context
NOTE
You can create data monitoring templates and remote network monitoring (RMON) TCA monitoring
templates. To monitor Ethernet performance counters supporting TCAs, create RMON TCA monitoring
templates. To monitor other counters, create data monitoring templates.
Procedure
Step 1 Create a data monitoring template.
2 3
7
Click Add, and select the
performance monitoring
indicators.
2 3
10
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Procedure
Step 1 Open the Create Monitoring Instance dialog box.
11
13
NOTE
14
NOTE
Skip this step for the OptiX RTN 905E, which does not support the setting of monitoring time.
15
NOTE
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l There is at least one performance monitoring instance.
NOTE
Procedure
Step 1 Open the real-time monitoring window.
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l There is at least one performance monitoring instance.
NOTE
Procedure
Step 1 Open the historical performance data window.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Query the microwave link information report.
2 3
5
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Query the license capacity report of NEs.
2
3
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Export the microwave configuration report of an RTN NE.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Open the board information query window.
1
2
4
Set Physical
Inventory Type to
Board.
3
10
NOTE
Complete the following steps to query the board information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Information Report from the Function
Tree.
Version information of all boards is displayed in Board Information Report.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Query the board manufacturing information report.
1
2 3
5
NOTE
Complete the following steps to query the board manufacturing information report from the WebLCT:
Select the NE from in the NE Explorer and choose Report > Board Details Information Report from the
Function Tree.
Manufacturing information of all boards is displayed in Board Details Information Report.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Procedure
Step 1 Query ODU information.
----End
Context
NOTE
The performance management in this section does not cover Ethernet performance
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
NOTE
To perform batch NE configurations on the U2000, choose Performance > Set NE Performance
Monitoring Time from the main menu.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE
Performance Monitoring Time from the Function Tree.
Step 2 Configure the performance monitoring parameters of the NEs.
1. Select 15-Minute or 24-Hour.
2. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring.
3. Set the start time and end time of the performance monitoring of NEs.
NOTE
Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled.
You can specify the start time of the performance monitoring function, only after selecting Enabled
in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
You can specify the end time of the performance monitoring function, only after selecting Enabled
and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired object.
Step 2 Choose Alarm > Alarm Severity and Auto Reporting from the Function Tree.
Step 3 Select any items in the column Event and set Severity and Auto Reporting Status for them.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > Alarm Suppression from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the NE.
Step 2 Choose Alarm > NE Alarm Attribute from the Function Tree.
Step 7 Choose Alarm > Alarm Reversion from the Function Tree.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > QoS Alarm > AIS Insertion from the Function Tree.
Step 3 Set the trigger conditions of AIS insertion. If you select Enabled under an alarm, the AIS
signal is inserted when this alarm occurs; otherwise, the AIS signal is not inserted when this
alarm occurs.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > QoS Alarm > UNEQ Insertion Switch from the Function Tree.
Step 3 Set the trigger conditions of UNEQ insertion. If you select Enabled under an alarm, the
UNEQ signal (all 0s) is inserted when this alarm occurs; otherwise, the UNEQ signal is not
inserted when this alarm occurs.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Alarm > QoS Alarm > Bit Error Alarm Threshold from the Function Tree.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 Specify Alarm Threshold for Fade Margin Shortage.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Performance > Performance Monitor Status from the Function Tree.
Step 3 Set the following parameters: Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-
Report.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Performance > Performance Threshold from the Function Tree.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Procedure
Step 1 In the NE Explorer, select the desired board.
Step 2 Choose Performance > Reset Board Performance Register from the Function Tree.
----End
5 Troubleshooting
This guide describes the general troubleshooting procedure and the methods of rectifying the
common faults.
Start
3 No
Analyze fault causes and locate
the fault
4 No
Report to Huawei
No
Is the service restored?
Yes
No Is the fault
rectified?
Yes
Fill in the troubleshooting
report
End
Comment Description
No.
1 When recording the fault phenomena, 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. You can use
the click-to-collect function on the NMS to collect data.
Fault Causes
l The operation is improper.
The configuration data changes, the loopback is performed, the cable is replaced, or the
board is replaced.
l The transmission NE or link is faulty.
l The interconnection is improper.
If the transmission equipment functions normally and the connection is normal, check
whether the interconnection between the transmission equipment is proper and whether
the switch equipment is faulty.
NOTICE
If the fault cannot be rectified immediately, restore the services quickly by adjusting the
service route or performing a forced switching.
Troubleshooting Procedure
Handle the fault by following the emergency maintenance process.
Start
1 Yes
Is there an incorrect Cancel the operation
operation?
No
No
3
4 Yes
NE access successful and Clear the alarm
alaarms cleared?
No
No Is the service
Proceed with the next step
Rectify the fault on site restored?
Yes
No
Is the service restored? Contact Huawei engineers
Yes
5
End
Comment Description
No.
Start
No
1
Is the PWR No Troubleshoot the
indicator on? power input
2 Yes
Browse alarms
locally by using the
LCT
3 Yes
Equipment
Clear the alarm
alarm?
No
4 Yes
Radio link Clear the alarm
alarm?
No
5 High order Yes
Clear the alarm
path alarm?
No
6 Low order Yes
Clear the alarm
path alarm?
No
7
Faulty inter- Yes Troubleshoot the
connection with SDH/PDH inter-connection
equipment? faulty
No
8
Yes Troubleshoot the
Packet service
packet service fault
fault?
No
Yes
End
Comment Description
No.
l Equipment faults, including outdoor component faults, cable faults, and power supply
faults
l Propagation faults, including fading, interference, and poor line of sight (LOS)
l Poor construction quality, including poor antenna/component installation, poor
grounding, and poor waterproofing
Antenna Cables
Interference Fading Poor LOS installation
Damaged
Reflection cable
components
Classifie Down The RSL is lower than the RSL l Multi-path fading
d by RSL fading after free space fading. The l Duct-type fading
difference can be tens of
decibels. l Rain fading
Troubleshooting Procedure
Start
1 Yes
Is there an
Undo the operation.
incorrect operation?
No
2 Hardware Yes
alarms exist? Rectify equipment faults.
No
3 Yes
Are there IF or RF
alarms on the link?
4
No Analyze the historical RSL
records and the current
RSL value
Co-channel or adjacent-
5
RSL greater than the Yes channel interference
Troubleshoot the fault as
a non-radio link fault. receiver sensitivity? Long delay caused
by terrain reflection
No
The link is blocked.
6 Is the RSL value Yes
always less than the The antennas are offset.
designed value?
Passive components like
No hybrid couplers or flexible
waveguides are faulty.
7 Yes
Is it raining when the
Rain fading
fault occurs?
No
8 Multipath fading
Does the fault occur Yes
regularly?
Terrain reflection
No
9
Troubleshoot the fault by
replacing the suspected
faulty parts.
Yes
Is the fault rectified? End
No
Table 5-6 Description of the procedure for troubleshooting the radio link
Mark Description
4 RSL is the major reference for locating and handling propagation faults. Follow
instructions in 4.4.3 Browsing Current Performance Events of the radio link
and 4.4.4 Browsing Historical Performance Data of a Radio Link to browse
and analyze the historical RSL records and the current RSL value.
Mark Description
5 l If the receive power fluctuates within a range less than 10 dB, mute the
opposite ODU and check the RSL at the local NE.
After the opposite ODU is muted, if the RSL value is greater than -80 dBm
for the 112 MHz channel bandwidth or if the RSL value is greater than -90
dBm for the other channel bandwidth, there may be co-channel interference
that affects long-term availability and error-second performance of the
system.
1. Follow instructions in 8.1.2 Scanning Interfering Signals or use a
frequency spectrum analyzer to locate the possible interfering frequencies.
2. If a third-party RF device is the interfering source, contact the local
frequency spectrum management department to clear the interference.
If interference is caused due to improper route planning, modify the
frequency plan to minimize the interference impacts.
l If the receive power fluctuates dramatically and quickly (by more than ten
dBs to dozens of dBs over seconds), or fluctuates periodically (for example,
always at midnight), the fault may be caused by terrain reflection. Check
whether there are rivers or lakes on the propagation path.
If excessive reflection exists, adjust the antenna height to change the path
inclination to reduce the impact of the reflection, or replan the propagation
path.
6 If the RSL value had been smaller than the designed value for a long time before
the fault occurred, the propagation trail is faulty. Proceed as follows:
l Check whether the antenna connection is loose or the antenna is unaligned. If
yes, re-align the antenna.
NOTICE
In high-corrosion areas, check whether outdoor components and fasteners are loose due
to corrosion. If yes, take rust- and corrosion-proof measures or replace the corroded
components or fasteners.
l Check whether there are any blocks in the radio transmission trail or in the
near field of the antenna. If yes, adjust the mounting height of the antenna to
avoid blocks, replan the radio link route.
l Check whether the antenna, hybrid coupler, and flexible waveguide are
damaged or suffer from water leakage, which causes high attenuation. If any
of the preceding components is damaged or suffers from water leakage,
replace the component.
Mark Description
7 If a radio link fault occurred in poor weather conditions (such as rainy, snowy, or
foggy) and was rectified after the conditions disappeared, the fault cause was
weather fading. For a fault caused by weather fading, check whether the link
fading margin is insufficient.
1. Calculate the actual link availability. Calculate the total link fault time within
one year or half a year. Calculate the actual link availability using the
following formula: <Link availability> = <Total fault time>/<Calculation
period>.
l If the actual link availability is lower than the designed value by an order
of magnitude, the link fading margin is insufficient. Re-plan the radio link
parameters.
l If the difference between the actual link availability and the designed
value is small, no special handling operations are required.
2. Before re-planning a radio link, check whether the rain zone parameters, the
refractivity gradient, and the planning algorithm are incorrect. The practicable
measure could be as follows:
l Increase the transmit power or replace the original antenna with a new one
having a larger diameter to increase the system gain and the fading margin.
l Use a frequency band on which rain fading has smaller impacts.
8 If the receive power fluctuates greatly and fast (by more than 10 dB or several 10
dB within several seconds or several 10 seconds), fast fading occurs.
Fast fading may occur due to:
l Multi-path fading: Faults occur periodically, for example, at the day-and-night
alternating time period.
l Duct-type fading: random fast fading
To handle fast fading, proceed as follows:
l Increase the path inclination: That is, adjust the antenna mount heights at both
ends to increase the height differences between the antennas at both ends.
l Reduce surface reflection. For apparent strong reflection surfaces, for
example, large areas of water, flat lands, and bold mountain tops, adjust
antennas to move reflection points out of the strong reflection areas or mask
the reflection by using landforms.
l Reduce the path clearance. With LOS conditions guaranteed, lower antenna
mount heights as much as possible.
9 If all preceding actions cannot rectify the fault, replace the ODU at both ends.
Then, check whether services are functional. If the fault persists, replan the radio
link by changing the operating frequency, using antennas with a larger diameter,
changing the antenna heights, or changing the routes.
l Periodically collect and analyze the data about the changes in the transmit power and
receive power so that you can detect and then rectify the incipient faults accordingly in
time.
Fault Phenomena
Fault Causes
There are not any RS l The line processing unit or IF board is faulty.
bit errors but there l The quality of the clock over the network declines.
are MS bit errors or
HP bit errors. When the quality of the clock over the network declines, a
pointer justification event occurs.
l The working temperature of the line processing unit or IF board
is excessively high.
Troubleshooting Procedure
Start
2
1
Is there an Yes
Clear the alarm
equipment alarm?
No
3
Is there a pointer Yes Troubleshoot the pointer
justification event? justification
No SDH optical
interface board Troubleshoot RS bit errors
on the SDH optical interface
board
Is there an If the
RS bit error alarm or a
Yes
alarming
performance board is
event?
4
No IF board Troubleshoot RS bit errors
on the IF board
Is there an
5
MS/ HP alarm or Yes Troubleshoot MS/HP bit
performance errors
event?
No
6
Is there an LP Yes Troubleshoot LP bit
alarm? errors
No
Locate the fault by performing No Is the fault
loopback operations section Proceed with the next step rectified?
by section
Yes
End
Comment Description
No.
Fault Phenomena
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 related to the AU pointer
justification are as follows:
l AUPJCHIGH
l AUPJCLOW
l AUPJCNEW
NOTE
The AU pointer justification is made 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 reframing 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 related to the TU
pointer justification are as follows:
l TUPJCHIGH
l TUPJCLOW
l TUPJCNEW
NOTE
The TU pointer justification is made 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 configured incorrectly. As a result, there
are two clock sources on the same network or a timing loop occurs.
l The fiber connections are incorrect. As a result, a timing loop occurs.
l The quality of the clock source declines, the clock unit is faulty, or there are other clock-
related faults.
l The tributary board is faulty (only for the TU pointer justification).
Troubleshooting Procedure
Start
1 Yes
Is there a clock-related Clear the alarm
alarm?
No
2
Check the clock
configuration
No
3
Check the fiber
connection
No
4 5
An AU pointer Yes Locate the NE whose clock
justification event? Locate the faulty board
is out of synchronization
No
6 7
A TU pointer Yes Locate the NE whose clock
justification event? Locate the faulty board
is out of synchronization
No
Proceed with the No
Is the fault rectified?
next step
Yes
End
3 Query ECC routes to check whether the fibers are connected correctly.
Check the fiber connections in the east and west directions of the NE that
reports the pointer justification event.
Comment Description
No.
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 as the method of numbering by order.
Certain 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 as the interleaved method.
l The overhead bytes at both ends are inconsistent.
l The indexes of the SDH interfaces do not meet the requirements.
NOTE
In the case of interconnection with Ethernet equipment, the common cause for an interconnection failure
is that the service is not set to the VC-4 pass-through service and thus the overheads are processed in the
terminating mode instead of the pass-through mode.
Troubleshooting Procedure
Figure 5-8 Procedure for troubleshooting the interconnection with 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
Table 5-11 Description of the procedure for troubleshooting the interconnection with SDH
equipment
Comment Description
No.
Fault Causes
l There is an impedance mismatch between interfaces.
l The equipment is not grounded properly.
l The cable performance deteriorates.
l The indexes of the PDH interfaces do not meet the requirements.
Troubleshooting Procedure
Figure 5-9 Procedure for troubleshooting the interconnection with PDH equipment
Start
1
Check the impedance of
the interfaces.
2
Is there an Yes
impedance mismatch? Modify cable impedance.
No
3
Is the cable a Yes
Check the grounding.
coaxial cable?
No
4
Check the cables.
No
Is in good conditions? Adjust the cables.
Yes
5
Test the indexes of
Interfaces.
Yes
No
Troubleshoot the faults Proceed with the next step. Is the fault rectified?
on the local equipment.
Yes
End
Table 5-12 Description of the procedure for troubleshooting the interconnection with PDH
equipment
Comment Description
No.
1 Check the impedance of the E1 path. Ensure that the impedance of the E1
path is consistent with the cable type.
In the case of interconnection with PDH equipment, improper grounding is the most common
cause for an interconnection failure.
Fault Phenomena
The Ethernet service interruption indicates that the Ethernet service is interrupted. The
Ethernet service deterioration indicates that the Ethernet service is abnormal. For example, the
network access speed is low, the equipment delay is long, the packet loss occurs, or incorrect
packets exist in the received or transmitted data.
Symptom Alarm
Fault Causes
l The possible human factors are as follows:
An Ethernet board loopback or a transmission line loopback occurs.
The parameter settings of the Ethernet ports, such as the port enabled state, working
mode, and flow control, are different from the parameter settings of the Ethernet
ports on the interconnected equipment.
The service configuration is incorrect.
l The equipment at the local end is faulty.
Table 5-14 Description of the procedure for troubleshooting Ethernet services configured in
an end-to-end manner
Comment Description
No.
Fault Phenomena
Common faults of MPLS tunnels are as follows:
MW_CFG_MISMATCH ISU3,
MW_LIM
MW_LOF
Fault Causes
l Incorrect operations are performed.
The transmission link is looped back.
Service configuration data is inconsistent between the local end and the opposite
end.
Service configuration is incorrect.
Troubleshooting Procedure
Start
1 Yes
Any incorrect Cancel the operation.
operation?
No
2 Yes
Any equipment- or
link-related alarm? Clear the alarm.
No
3 Yes
Clear the alarm using
Any alarm related to MPLS
LB/LT/LSP Ping/LSP Tracerout.
tunnel ?
No
Any fault in
Yes
interconnection
Handle the fault.
equipment?
No
Yes
End
Comment Description
No.
3 Check whether the tunnel is faulty using LSP Ping, LSP Tracerout, or
MPLS-TP Tunnel OAM.
Pay special attention to the following alarms:
l ARP_FAIL
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_OAMFAIL
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
l MPLS_TUNNEL_UNEXPMEG
l MPLS_TUNNEL_UNEXPMEP
l MPLS_TUNNEL_UNEXPPER
Fault Phenomena
CES services are interrupted if they are completely unavailable. CES services are degraded if
they have packet loss or incorrect packets.
AM_DOWNSHIFT ISV3
MW_CFG_MISMATCH
AM_DOWNSHIFT ISV3
MW_CFG_MISMATCH
Fault Causes
l Incorrect operations are performed.
The transmission link is looped back.
Service configuration data is inconsistent between the local end and the opposite
end.
Service configuration is incorrect.
l The clock source is asynchronous.
l Jitters and delays on the network are too great.
l The local NE is faulty.
l The transmission link is faulty or has bit errors.
l Service bandwidth decreases due to an AM downshift.
l The opposite NE is faulty.
l External electromagnetic interference is severe.
Troubleshooting Procedure
Start
1 Yes
Any incorrect Cancel the operation
operation?
No
2 Yes
Any equipment- or
link-related alarm? Clear the alarm
No
Yes
3
Any alarm related to Clear the alarm
tunnels/PWs?
No
4
Any alarm related to Yes
CES services? Clear the alarm
5 Yes
Any alarm on E1
ports? Clear the alarm
No
6
Any RMON Yes
performance event? Handle the performance event
No
No
Yes
End
Commen Description
t No.
4 Run PW ping or LSP Tracerout to check whether the MPLS tunnel is faulty.
Handle the tunnel fault by referring to instructions in 5.9 Troubleshooting
MPLS Tunnels.
Check whether PW configurations are correct. If the configurations are
incorrect, re-configure the PW according to the network plan.
Fault Symptoms
Ethernet services are interrupted if they are unavailable. Ethernet services deteriorate if they
have great delays, packet loss, or incorrect packets.
ETH_LOS,
ETH_EFM_LOOPBACK,
or LOOP_ALM
LASER_MOD_ERR
Fault Causes
l Incorrect operations are performed.
The transmission link is looped back.
Service configuration data is inconsistent between the local end and the opposite
end.
Service configuration is incorrect.
l The local NE is faulty.
l The transmission link is faulty or has bit errors.
l Service bandwidth decreases due to an AM downshift.
l The opposite NE is faulty.
l External electromagnetic interference is severe.
2. Check whether the PW works properly by using the PW ping or MPLS-TP PW OAM
function. If the PW is faulty, check whether the MPLS tunnel works properly by using
the LSP ping or MPLS-TP Tunnel OAM function. If the MPLS tunnel works properly,
check whether the PW has the same configuration at both ends. If the configuration is the
same, replace the NE on the NNI side.
3. If the PW works properly, check whether the PE data configured at both ends is the
same. If the PE data is different, change the PE data to the same.
4. Check whether UNI-side data and CE-side data are consistent.
5. Analyze the RMON performance events of Ethernet services.
6. Check whether there is impedance mismatch on channels and whether any electrical
cables are connected incorrectly.
7. Replace the NE.
Table 5-20 Description of the procedure for troubleshooting Ethernet services configured in
an end-to-end manner
Comment Description
No.
Context
If links or lines that bear DCN channels, including data communication channels (DCCs) and
inband DCN channels, are faulty, the DCN communication is interrupted. In this case, handle
the fault in the same manner as a service fault. In other cases, the DCN communication
between an NE and the NMS is interrupted or unstable, but the services between them are
normal for the moment. This fault also needs to be rectified in time, otherwise, you will fail to
check the NE information, obtain NE alarms, or change NE configurations when the services
become faulty.
NEs connected through their l Cause 1: The network cable of the NMS is disconnected
NMS ports are unreachable or damaged.
to their NMS. l Cause 2: DCN parameters are incorrectly set.
l Cause 3: System control boards are faulty.
A few NEs are unreachable l Cause 1: DCN parameters are incorrectly set.
or their connection to the l Cause 2: An NE ID or NE IP address conflict occurs
NMS is unstable. between NEs on the DCN subnet.
l Cause 3: The DCN subnet is too large.
l Cause 4: The system control unit of the NE is faulty.
Troubleshooting Procedure
Start
1
Locate a
faulty NE
2
Icon of the Yes Yes Check for hardware
The NMS cannot Hardware
faulty NE in alarms and check
reach the NE fault? cable connections
gray
NO
NO 3
Settings Yes Check settings
incorrectly or undo
modified? modifications
NO
4
Yes
Large DCN Divide the DCN
subnet? subnet
5
NM Yes
Too low DCN Increase the DCN
Information channel bandwidth channel bandwidth
loss?
NO
6
No response to Yes Wait for the
SCC boards are
commands from the completion of SCC
being reset
NMS resetting
NO Fault
rectified
Yes
Contact Huawei
technical service End
engineers
1 Locate the Locate the faulty NE l If the faulty NE has a service fault, rectify the
faulty NE. based on a DCN service fault first.
networking diagram. l If an unreachable NE connects to its NMS through
l If all NEs within an an external DCN, verify that the external DCN
area are unreachable equipment or the cable used for DCN connection is
to their NMS, the working correctly.
unreachable NE
closest to a normal
NE is probably the
faulty NE.
l If only one NE is
unreachable to its
NMS, the NE is the
faulty NE.
2 Handle l The faulty NE reports l Handle hardware alarms based on the maintenance
hardware faults. hardware alarms like and fault management procedure.
HARD_BAD. l Remove and then install, or replace the network
l Check whether the cable and optical fibers.
NMS/COM port on
the faulty NE is
connected to a correct
cable or whether the
network cable of the
faulty NE is damaged.
3 Modify The following operations l Check for unplanned NE IDs and NE IP addresses
incorrect are performed before a in the ECC routing table of the faulty NE's
configurations. faulty NE becomes upstream NE. If there is an unplanned NE ID or IP
unreachable to its NMS: address in the ECC routing table, the faulty NE is
l Modifying NE incorrectly configured. To rectify the fault, log in
attributes or NE to the faulty NE using the unplanned NE ID and
communication NE IP address on the NMS and correct the
settings settings.
l Adding a new NE to l Change the DCC settings or inband DCN settings
the network, or of the faulty NE to interrupt the DCN channel
replacing the faulty between the faulty NE and its upstream NE. Then,
NE or its system check for the ID and IP address of the faulty NE in
control board the ECC routing table of the upstream NE. If the
ID and IP address of the faulty NE exist in the
ECC routing table of the upstream NE, another NE
on the ECC subnet has the same ID and IP address
as the faulty NE. In this case, correct the settings to
ensure that each NE on the ECC subnet has a
unique ID and IP address.
l If the inband DCN is enabled for the faulty NE and
its upstream NE, verify that the VLAN ID is
correctly set on the upstream NE.
l Verify that static routes are correctly set on the
faulty NE's upstream NE.
l Verify that OSPF parameters are correctly set on
the faulty NE's upstream NE. OSPF parameter
settings must be consistent for all NEs on the same
ECC subnet.
4 Analyze the Check the number of NEs If there is a large number of NEs in the routing table,
DCN subnet in the IP routing table or the DCN subnet is too large in size and some NEs on
size. ECC routing table of the the DCN subnet may occasionally become
faulty NE's upstream NE. unreachable to their NMS. It is recommended that an
DCN subnet consist of no more than 120 NEs, if a 192
kbit/s bandwidth is provided. If L2 DCN is used, an
L2 DCN subnet consists of not more than 30 NEs.
5 Troubleshoot Some NEs may l Verify that a minimum of 192 kbit/s bandwidth is
NMS occasionally become allocated to the inband DCN. If the allocated
information unreachable to their bandwidth is lower than 192 kbit/s, packets from
loss. NMS. the NMS may be lost.
l Check whether the QoS priority allocated to the
inband DCN by a third-party network is high
enough if inband DCN packets are transmitted
over the third-party network. Lower QoS priority
of inband DCN packets may cause NEs
unreachable to the NMS due to congestive packet
loss. The per-hop behavior (PHB) priority of
inband DCN packets must not lower than
expedited forwarding (EF).
6 Troubleshoot l The NE fails to be l Search for the IP address of the faulty NE on the
no-response logged in to onsite. NMS.
problems. l The NE does not l If the IP address is not found, or if the IP address is
respond to commands. found but the NMS still cannot reach the faulty
NE, restart the OptiX RTN 905E after a power-off,
in a authorized maintenance window which service
can be interrupted.
The difference between the maximum receive power and the minimum receive power
was more than 40 dB, and the minimum receive power was close to or less than the
receiver sensitivity. Therefore, it was inferred that the fault was caused by spatial fading.
2. Checked the network planning design.
The ODU operated at the 8 GHz band, which was less prone to rain fading, and therefore
multipath fading caused intermittent link interruptions. In addition, 1+1 HSB protection
does not well protect radio links against multipath fading.
3. Replaced 1+1 HSB protection with 1+1 space diversity (SD) protection.
Fault Symptoms
The received signal levels (RSLs) at both ends of a 1+1 SD cross-ocean radio link fluctuated
dramatically, leading to bit errors or even link interruptions.
NOTE
The value of K generally ranges from 0.67 to 1.33. In this case, the RSLs of the main and standby
antennas are not correlated with each other. When designing mounting heights for main and standby
antennas, keep appropriate antenna spacing for minimizing the impact of reflection on radio links.
When reflection causes high attenuation on the main path, the attenuation on the standby path is low.
Fault Symptoms
On a 900-meter 1+0 microwave hop, working with 18 GHz HP ODUs, at 28 MHz channel
bandwidth and in 256QAM modulation, with XPIC disabled. One end of the link
continuously reports MW_LOF alarms and the other end reports MW_RDI alarms.
On this microwave hop, ODUs are mounted onto 0.3-meter diameter dual-polarized antennas
in separate-mount manner. Both ends of the radio hop are located on roofs. Antennas are
installed at the middle of poles about 5 meters high standing on the roofs.
Site A
Site B
Reflected signal
Main signal
Move poles near the building roof edges to decrease the inter-building reflection possibility or number
of reflection times. Generally, antennas can be adjusted upwards, downwards, leftwards, or rightwards.
During antenna adjustment, notice the MSE changes and ensure that the RSL is within its allowed
range.
The larger the antenna diameter, the denser the beams. The smaller the beam angle at the receive end,
the powerful the capabilities to suppress reflection.
3. By means of the preceding methods, you can adjust the MSE values at both ends to be
-30 dB to clear alarms.
Fault Symptoms
A 1+0 microwave link between NE A and NE B was configured with QPSK/28M modulation
and 8G/HP ODUs. The link is available only in one direction after the link is expanded from
mode 5 (QPSK/28M/16E1) to mode 7 (128QAM/28M/STM-1).
Check the above items to prevent the link from being interrupted before the link capacity
expansion.
Fault Symptoms
Bit errors were detected in a microwave link hop (between NE A and NE B) during
acceptance checks. The distance between two ends of the link hop was 2.5 km. The link was
configured with 0.6 m antennas, 15G ODUs, and QPSK/28M modulation.
5. Deleted 1+1 HSB protection settings and configured 1+1 SD protection. The link
availability met service requirements.
6 Part Replacement
Part replacement is a method frequently used to locate faults. The replacement operation
varies according to the specific part type.
Background Information
Prerequisites
l You are aware of the impact of replacing the IDU.
l You are aware of the location of replacing the IDU.
l The spare IDU is at hand, whose model is the same as that of the IDU to be replaced.
l NE data has been obtained.
The backup NE data has been imported to a laptop where the Web LCT is installed,
if there is a backup of the NE database on the NMS.
The network plan document has been obtained if there is no backup of the NE
database on the NMS.
Precautions
For an OptiX RTN 905E, if an XPIC workgroup has been configured on it, mute the opposite
ODU in the same polarization direction before replacing the IDU.
Procedure
Step 1 If the NE is running, Query the current alarms of the IDU.
Step 2 Optional: If the NE is running, back up the NE data to the USB flash drive.
1. Connect the USB flash drive to the USB port on the OptiX RTN 905E.
The indicator beside the USB port is blinking yellow during the data backup, and is
steady green after the data backup is complete.
2. Remove the USB flash drive after the data backup is complete.
Step 3 If the OptiX RTN 905E 2E is used, be sure to set the ODU-2 and ODU-1 switches on the
front panel of the IDU to "0".
Step 4 Turn off the circuit breaker for the input power of the IDU.
Step 5 Mark and remove all the cables connected to the IDU.
NOTE
Loose the screws on the power connector before removing the power cable.
Step 6 Remove the IDU from the cabinet, wall, or desk-mounted rack.
Step 7 See OptiX RTN 905E IDU Quick Installation Guide and install the spare IDUs.
Step 8 Re-connect the cables of the IDU as marked earlier.
Step 9 See Commissioning Guide and power on the equipment.
Step 10 Restore the NE data.
If... Then...
The original NE is in the running Connect the USB flash drive to the USB port on the
state and NE database is backed up new NE (spare OptiX RTN 905).
to a USB flash drive
The indicator beside the USB port is blinking yellow
during data restoration, and is steady green after the
data is restored. It takes more than 10 minutes to
restore data.
The original NE is not in the Set ID and IP address of the new NE to those of the
running state and NE database is original NE using Web LCT. Then restore NE
backed up to a USB flash drive database using a USB flash drive.
The original NE is not in the Configure NE data according to the network plan.
running state and NE database is
not backed up
----End
Prerequisites
l Impact of replacing an MN1 subboard is known.
l Location of the MN1 subboard to be replaced is known.
l A spare MN1 subboard is available, and the version and model of the spare subboard are
consistent with those of the subboard to be replaced. (You can obtain subboard version
information beforehand by referring to instruction in querying board manufacture
information.)
Procedure
Step 1 Query current alarms on the MN1 subboard.
Step 5 Observe the indicators after the subboard is started. The STAT indicator should be green.
----End
Prerequisites
l You must know the impact of SFP replacement.
l You must know the specific position of the SFP to be replaced.
l You must know the service protection and protection channels of the SFP to be replaced.
l The spare SFP must be available, and the version and type of the spare SFP must be the
same as the version and type of the SFP to be replaced. You can query the board
manufacturing information to obtain the version of the SFP to be replaced.
Procedure
Step 1 Query the current alarms of the board.
Step 2 Optional: If SNCP is configured for services at the optical interface, ensure that the services
are already switched to the protection channel.
l Press the release button before removing the STM-1 electrical module.
Step 6 Insert the standby SFP module and reconnect cables based on the record.
Step 7 Query the current alarms of the board.
There should be no new alarms on the board.
Step 8 Optional: If the forced switching has been performed on the board, release the forced
switching.
Step 9 Optional: If the linear MSP switching has been performed for the services, release the forced
switching.
----End
Prerequisites
l You must know the impact of ODU replacement.
l You must know the specific positions of the ODU to be replaced and the IDU connected
to the ODU.
l The spare ODU must be at hand, whose type must be the same as the type of the ODU to
be replaced.
Precautions
CAUTION
l Before replacing an ODU, power off the ODU.
l Considering live-line working and radiation risks, it is advised to power off ODUs on
adjacent channels before replacing an ODU installed on a hybrid coupler.
NOTICE
l Replacing an ODU installed on a hybrid coupler may temporarily affect services on other
channels. It is advised to mute the peer ODU to minimize the impact.
l Do not damage the coating when you replace an ODU. In the case of any coating damage,
repair the coating timely.
Procedure
Step 1 Query the current alarms on the ODU and then record the results.
Step 2 Turn off the ODU-PWR switch on the front panel of the IDU.
NOTICE
To turn off the ODU-PWR switch, pull the switch lever outwards slightly and set the switch to
the "O" position.
Step 3 Remove the IF cable and the PGND cable from the ODU.
Option Description
If... Then...
You need to remove the RTN 600 ODU Loosen the four latches of the ODU and
with a waveguide interface disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
You need to remove the RTN 600 ODU Remove the ODU from the post.
with a coaxial interface
You need to remove the RTN XMC ODU Loosen the captive screws on the ODU and
disconnect the ODU from the antenna, the
hybrid coupler, or ODU adapter.
Step 5 Ensure the type of the spare ODU is the same as the type of the ODU to be replaced.
Option Description
If... Then...
You need to install a new RTN 600 ODU with a See the RTN 600 ODU Quick
waveguide interface Installation Guide.
You need to install a new RTN 600 ODU with a See the RTN 600 ODU Quick
coaxial interface Installation Guide.
You need to install a new RTN XMC ODU See the RTN XMC ODU Installation
Guide.
Step 7 Connect the PGND cable and the IF cable to the ODU.
NOTICE
To turn on the ODU-PWR switch, pull the switch lever outwards slightly and set the switch to
the "I" position.
Step 10 After the ODU starts to work, check the LINK indicator on the IDU.
The LINK indicator should be on and green.
Step 11 Query the current alarms of the ODU. There should be no new alarms on the ODU.
----End
Prerequisites
l You must know the impact of IF cable replacement.
l You must know the specific positions of the IF cable to be replaced and the IDU
connected to the IF jumper.
l In the case of the RG-8U IF cable or the 1/2-inch IF cable, an IF jumper is required to
connect the IF cable to the IDU and both ends of the IF cable should be terminated with
type-N connectors. In the case of the 5D IF cable, the IF cable is connected directly to
the IDU and the cable end connecting to the IDU should be terminated with the TNC
connector and the cable end connecting to the ODU should be terminated with the type-
N connector.
Procedure
Step 1 Query and record the current alarm of the IDU.
Step 2 Turn off the ODU-PWR switch on the front panel of the IDU.
NOTICE
To turn off the ODU-PWR switch, pull the switch lever outwards slightly and set the switch to
the "O" position.
Step 3 Disconnect the IF cable from the IF jumper and from the ODU.
Step 4 Use a multimeter to test the connectivity of the IF cable to determine whether you need to
make new connectors for the IF cable or replace the IF cable with a new one.
If... Then...
You need to make new connectors for the See the Installation Reference and make new
IF cable connectors for the IF cable.
You need to replace the IF cable with a Replace the IF cable with a new one.
new one
Step 6 Waterproof the connectors at the two ends of the IF cable with the waterproof adhesive tape.
NOTICE
To turn on the ODU-PWR switch, pull the switch lever outwards slightly and set the switch to
the "I" position.
Step 8 After the ODU starts to work, check the LINK indicator on the IDU.
The LINK indicator should be on and green.
Step 9 Query the current alarms of the IDU.
There should be no new alarms on the IDU.
----End
The OptiX RTN 905E supports database backup and restoration through the NMS.
7.1 NE Database
An NE database stores communication data, security data, alarm data, performance data, and
configuration data of an NE in a certain structure, to facilitate data query and modification
and to ensure that the data can be restored after the NE is reset.
7.2 Backing Up the Database Manually
The NE configuration data is stored in the database of an NE. To prevent the database from
being damaged due to certain risky operations such as replacing a faulty system control,
cross-connect, and timing board or upgrading the software, you need to manually back up the
database on a regular basis and before performing any risk operation.
7.3 Setting the Database Backup Policy
You can set the policy of backing up a database to realize the function of periodically backing
up the database.
7.4 Restoring the Database by NMS
If the database is damaged, you can restore the NE database by using the database files that
are saved previously.
7.5 Recovering Databases from a USB Flash Drive
When NE data is lost or abnormal and DCN communication fails, you can recover NE
databases from a USB flash drive.
7.6 Restoring Databases for an NE from Its Peer NE
This section describes how to restore databases for an NE from its peer NE. After the
databases of an NE are damaged, configure a microwave link between the NE and its peer
NE, turn up the microwave link, and restore its databases from its peer NE.
7.1 NE Database
An NE database stores communication data, security data, alarm data, performance data, and
configuration data of an NE in a certain structure, to facilitate data query and modification
and to ensure that the data can be restored after the NE is reset.
Three types of NE databases are available:
l Memory database (MDB)
The data in the MDB varies according to the configuration and is lost when the system
control unit is reset or when the NE is powered off.
l Dynamic random database (DRDB)
The DRDB automatically stores the data that is checked successfully. The DRDB is
resident in the reserved memory. Hence, the data in the DRDB is not lost when a warm
reset is performed on the system control unit. The data, however, is lost when a cold
reset is performed on the system control unit or when the NE is powered off.
l Flash database (FDB)
The FDB includes FDB0 and FDB1. The FDB is resident in the flash memory on the
board. Hence, the data in the FDB is permanently stored.
NE Database Backup
NE configuration data, after being delivered to the system control unit, is stored in the MDB.
Upon successful verification of the configuration data, the system control unit copies the data
from the MDB to DRDB and delivers the data to boards.
Two modes are available to back up DRDB data to the FDB:
l An NE backs up DRDB data to the FDB within five minutes after NE configuration data
is modified.
l An NE backs up DRDB data to the FDB every 24 hours.
The following modes are available to back up FDB data:
l Upon a scheduled backup of DRDB data to the FDB, the NE backs up FDB data to a
dedicated partition of the flash memory (other than FDB0 and FDB1).
l On the NMS, FDB data can be backed up to an NMS server manually or at specified
intervals.
l Before backing up the NE database to a USB flash drive, it is advisable to delete all
folders and files except the RTN.CER file from the USB flash drive.
The NE automatically backs up its database locally, and also backs up its database and system
parameters such as NE ID and NE IP address to the peer NE at an interval of 72 hours.
NE Database Restoration
l When an NE is warm reset, the system control unit checks whether configuration data is
available in the DRDB. If configuration data is available in the DRDB, the system
control unit restores data from the DRDB. If the configuration data in the DRDB is
damaged, the system control unit restores data from FDB0 and FDB1.
l When the NE is cold reset, the system control unit restores data from FDB0 and FDB1.
l When the data in both FDB0 and FDB1 is damaged, data can be restored from the
dedicated partition of the flash memory.
l On the NMS, the FDB data in flash memory can be restored from an NMS server
without interruption of TDM services.
l If a USB flash drive is inserted in the USB port and the FDB data in the USB flash drive
is newer than that in the flash memory, the NE backs up the FDB data from the USB
flash drive to the flash drive.
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l You must log in to the NE.
NOTE
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/
Restoration from the Main Menu.
Step 3 In the Find NE dialog box, set the search conditions and search for the NE that requires
database backup.
Step 4 Click OK.
Press and hold the Ctrl button on the keyboard, you can select multiple NEs to back up the data at one
time.
Step 6 Set the data backup path to NMS Server or NMS Client according to the requirements.
Step 7 Click Start to start backing up the NE data. In NE View, Operation Status indicates the
progress of backing up the data. After the data backup is successful, Operation Status
displays a message, indicating that the operation is successful.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l You must log in to the NE.
NOTE
Background Information
Each NE has a default data backup policy.
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy Management
from the Main Menu.
Step 8 Set Policy Name, Period Backup Policy, and Period Save Policy.
NOTE
l If The Added NE's Policy Status is set to Enable, the NMS performs the backup operation within
the specified period, day, and time.
l If The Added NE's Policy Status is set to Disable, the backup policy is still in the Disable state
although the policy period reaches the specified period, day, and time.
Step 9 Click Advanced Settings, and set Backup Type, Max Backup Num, and Configuration
Change Backup for a certain type of NEs.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy Management
from the Main Menu.
Step 3 Right click the selected NE, Click Enable Backup Policy.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
NOTE
Procedure
Step 1 Choose Administration > NE Software Management > NE Backup Policy Management
from the Main Menu.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The data to be restored must be backed up.
l You must log in to the NE.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Precautions
Before restoring the database of an NE, ensure that the KMC key for the NE is the same as
the key for the backup database. If they are different, database restoration fails. For details
about KMC key settings, see Configuring a KMC Key.
A V100R009C00 NE can restore its database from a backup database of an NE earlier than
V100R009C00. An NE earlier than V100R009C00 can restore its database only from a
backup database of an NE in the same version.
Context
If NE configurations have been modified after the database is backed up, using the backup
database to restore configurations may interrupt DCN communication or services. Therefore,
you must manually configure service parameters if NE configurations have been modified
after the database is backed up.
Procedure
Step 1 On the NMS, choose Administration > NE Software Management > NE Data Backup/
Restoration from the Main Menu.
NOTE
In NE List, click .
In Login, click OK.
For the DC, the default user name is szhw and the default password is Changeme_123. For the license tool,
the default user name is lct and the default password is Changeme_123. If the user name or password has
been changed, use the latest one.
The NE Data Backup/Restoration window is displayed.
Step 2 In NE View, click Find.
Then, the Find NE dialog box is displayed.
Step 3 In the Find NE dialog box, set the search conditions to search for the NEs that need to restore
databases.
You can select multiple NEs to recover the data at one time.
Then, the Recover dialog box is displayed.
Step 6 Select Browse in File Name.
NOTE
l If Activate Type is No Reboot, only database files are overwritten and the NE will not be warm
reset. The database does not take effect until the NE is reset.
l If Activate Type is With Service Interruption, database files will be overwritten, the NE will be
warm reset, and then the database will take effect.
NOTE
The system starts recovering the selected data files on the specified NE.
In the NE list of NE View, Operation Status indicates the progress of recovering the data.
After the data is recovered, Operation Status displays a message, indicating that the
operation is successful.
Step 11 In NE View, right-click the NE and choose Active Database from the shortcut menu.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l The NE database has been backed up.
l You have logged in to the NE on the NMS.
Precautions
Before restoring the database of an NE, ensure that the KMC key for the NE is the same as
the key for the backup database. If they are different, database restoration fails. For details
about KMC key settings, see Configuring a KMC Key.
A V100R009C00 NE can restore its database from a backup database of an NE earlier than
V100R009C00. An NE earlier than V100R009C00 can restore its database only from a
backup database of an NE in the same version.
Procedure
Step 1 Copy all NE database files backed up on the NMS server to the \db directory in the USB flash
drive.
NOTE
Other directories related to the NE (\pkg, \patch, \sysdata, \script, and \license) cannot exist.
Step 2 Copy the RTN.CER and RTNEXTRA.CER files of the NE to the root directory of the USB
flash drive.
NOTE
The RTN.CER and RTNEXTRA.CER files, which store the account and password information at the
system administration level (the password is encrypted), are generated by the system administrator of a
network management center using dedicated tools. For details about how to generate the file, refer to
instructions in Preparing the Certificate File for NE Access from a USB Flash Drive.
Step 3 Insert the USB flash drive in the USB port on the OptiX RTN 905E.
NOTE
During the database recovering process, do not perform operations such as data configuration, NE resets, and
software loading.
Step 4 Check the data loading status based on the indicator on the USB flash drive.
The indicator blinks yellow The loading of Remove the USB flash
and then turns steady green. commissioning data is drive.
complete.
NOTE
l When the indicator is
blinking yellow, do not
remove the USB flash
drive. Otherwise, the data
loading may be
interrupted.
l After the data loading is
complete, the NE will
automatically reset, which
takes 2 minutes to 3
minutes. After the reset is
complete, the USB
indicator and the system
indicator (SRV) on the NE
are both steady green,
indicating that the data
loading is successful.
The indicator is off. The USB flash drive is l Copy the commissioning
faulty and fails to get online. data to another USB
NOTE flash drive.
Another possible cause is that l Repeat 1 to load the
the USB flash drive is not
commissioning data to
properly inserted.
the NE.
The indicator blinks red. The type of the USB flash l Copy the commissioning
drive is incorrect or an error data to another USB
occurs when the NE flash drive.
attempts to read/write the l Repeat 1 to load the
USB flash drive. commissioning data to
NOTE the NE.
Preparing Documents and
Tools provides the USB flash
drive types that the OptiX
RTN 905E supports.
The indicator is steady red. The loaded commissioning Reload the data:
data is abnormal. l Save the correct NE
software and
commissioning data
scripts in the correct
directories of the USB
flash drive.
l Repeat 1 to load the
commissioning data to
the NE.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
A microwave link between the NE and its peer NE has been configured, and the DCN channel
has been set up.
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
Before restoring the database of an NE, ensure that the KMC key for the NE is the same as
the key for the backup database. If they are different, database restoration fails. For details
about KMC key settings, see Configuring a KMC Key.
A V100R009C00 NE can restore its database from a backup database of an NE earlier than
V100R009C00. An NE earlier than V100R009C00 can restore its database only from a
backup database of an NE in the same version.
Context
If NE configurations have been modified after the database is backed up, using the backup
database to restore configurations may interrupt DCN communication or services. Therefore,
you must manually configure service parameters if NE configurations have been modified
after the database is backed up.
Procedure
Step 1 Restore databases for the NE from its peer NE.
3
2
Execution results.
5
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The time and time zone of an NE on which microwave link indicators are sampled must
be the same as those on the NMS.
NOTE
Procedure
Step 1 Navigate to the interface for monitoring the RSL and MSE indicators of radio links.
Step 2 Configure parameters for monitoring the RSL and MSE indicators of radio links.
----End
Prerequisites
l You must be an NM user with NE maintainer authority or higher.
l Mute the ODU at the opposite end, before scanning the reference signal.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Background Information
When interfering signals are scanned, services and DCN communication are interrupted.
Both local frequency scanning and remote frequency scanning are supported. You can obtain
results of remote frequency scanning after DCN communication restores.
Procedure
Step 1 Scan interfering signals.
1
Select an ODU, and specify the scanning range, frequency
3 adjustment step, and bandwidth parameters.
4
5
----End
Prerequisites
l You must be an NM user with NE operator authority or higher.
l The corresponding IF boards and the ODUs connected to the IF boards must be added to
the NE Panel.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
l Mute/Unmute an ODU.
2
4
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
Two PRBS test types are available, PRBS frames are transmitted through the specified E1
timeslot or transmitted as Ethernet frames.
PRBS
transmitter
1 1 1
PRBS
transmitter
NOTICE
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can be performed only in one path and in one direction at one time.
l The standby IF unit does not support the PRBS test. Before you perform the PRBS test for
the standby IF Unit of a 1+1 HSB/FD/SD protection group, you must switch the standby
IF Unit to the working state.
Procedure
Step 1 Configure an outloop on the peer IF board by referring to instructions in and 8.4.3 Setting
Loopback for the IF Port.
Step 2 Start a PRBS test on the IF board.
2 6
8
View test results.
Green indicates no
exception.
10
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Procedure
Step 1 Optional: Query the attributes of the FE or GE port on the packet plane.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
1. In NE Explorer, select the required NE from the Object Tree.
2. Choose Configuration > Interface Management > Ethernet Interface from the
Function Tree.
3. Click the Advanced Attributes tab.
4. Check the parameters such as Port Physical Parameters, Transmitting Rate, and
Receiving Rate.
Step 2 Optional: Querying the attributes of the port.
NOTE
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Optional: Search for an E-Line service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Search for an E-LAN service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for an E-LAN service path.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been deployed.
Procedure
Step 1 Search for services.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for an E-LAN service path.
NOTE
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-end Ethernet services have been created and the related fibers/cables have been
created.
Procedure
Step 1 Search for service paths.
Step 2 Query the real-time and historical performance data of each measured object on each service
path.
The following figure shows how to query the real-time performance data of priority queues on
a port. Querying the real-time and historical performance data of other measured objects is
similar.
----End
Prerequisites
You must be an NM user with NE administrator authority or higher.
End-to-End Ethernet services and associated fibers have been created.
Procedure
Step 1 Search out service paths.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
Two types of IP ping functions are supported:
l Near-end IP ping
The near-end IP ping function is typically used to check whether the link between a
customer edge (CE) device and a near-end transmission NE is faulty. Near-end IP ping
can be initiated from the CE device to a UNI on the near-end transmission NE, or from a
UNI on the transmission NE to the near-end CE device. For example, the RNC initiates
IP ping packets to the UNI port on NE1, as shown in Figure 8-2.
l Far-end IP ping
The far-end IP ping function is typically used to check whether the link between a CE
device and a far-end transmission NE is faulty. Far-end IP ping can be initiated from the
CE device to a UNI on the far-end transmission NE, or from a UNI on the transmission
NE to the far-end CE device. For example, the RNC initiates IP ping packets to the UNI
port on NE2, as shown in Figure 8-2.
Near-end IP Ping
NodeB RNC
NE2 NE1
Near-end IP Ping
Far-end IP Ping
Precautions
l IP ping can be enabled only for UNI Ethernet ports.
l IP ping can be enabled only for a maximum of four ports on an NE.
l To support far-end IP ping, the protocol VLAN ID (if any) must be configured to the
same value as the VLAN ID carried by IP packets initiated by the local CE. This enables
NEs enabled with the IP ping function can select the correct PW for transmitting IP ping
packets based on the configured protocol VLAN ID.
l If IP ping packets initiated by the local CE do not carry any VLAN ID (for example,
when the port tag attribute is access), the protocol VLAN ID must be set to 0 or /. This
enables NEs enabled with the IP ping function to select the correct service for
transmitting IP ping packets based on the PVIDs of UNI ports.
l The CE device or transmission NE on which IP ping is initiated must support non-strict
ARP learning mode. That is, the CE must be able to learn MAC addresses based on ARP
request packets.
l The maximum length of the IP ping packet is 1494 bytes.
137.0.0.2/
255.255.255.0 137.0.0.4/ 137.0.0.3/ 137.0.0.1/
255.255.255.0 255.255.255.0 255.255.255.0
PORT 1 PORT 1
NodeB NE 2 NE 1 RNC
The Ethernet service between NE1 and NE2 has the VLAN ID 100. The tag attributes of both
PORT1s on NE2 and NE1 are tag aware.
You can perform IP ping on a transmission NE by initiating the ping from the transmission
NE or from a CE device. The following describes the two methods of initiating IP ping.
Procedure
l Initiate IP ping from a transmission NE.
a. Configure near-end IP ping on NE1.
i. In the NE Explorer, select the desired NE and choose Configuration > IP
Ping Test
.
ii. Enable IP ping for the port and configure related parameters.
NOTE
If NE1 and the RNC are on the same network segment, set Next Hop IP Address to
the IP address of the RNC. If NE1 and the RNC are on different network segment, set
Next Hop IP Address to the IP address of the router near NE1.
iii. Click Apply.
iv. Click IP PING TEST.
v. Click Add.
vi. Configure near-end IP ping parameters.
NOTE
A port supports multiple IP ping tests. A maximum of 16 IP ping tests can be initiated
on a network.
c. Configure near-end IP ping on NE2 by referring to a.
d. On NE1, click Start to initiate near-end IP ping. If response packets are received
from the RNC, go to the next step. If no response packets are received from the
RNC, the link between NE1 and the RNC is faulty.
e. On NE1, click Start to initiate far-end IP ping. If response packets are received
from the NodeB, the link is normal. If no response packets are received from the
NodeB, go to the next step.
f. On NE2, click Start to initiate near-end IP ping. If response packets are received
from the NodeB, the link between NE1 and NE2 is faulty. If no response packets
are received from the NodeB, the link between NE2 and the NodeB is faulty.
l Initiate IP ping from a CE device.
NOTE
If NE1 and the RNC are on the same network segment, set Next Hop IP Address to
the IP address of the RNC. If NE1 and the RNC are not in the same network segment,
set Next Hop IP Address to the IP address of the router port on the NE1 side.
iii. Click Apply.
b. On NE1, configure the far-end IP ping agent.
i. In the NE Explorer, click the NE and choose Configuration > IP Ping Test.
ii. Set the far-end IP ping agent to NE2.
NOTE
Next Hop IP Address applies to near-end IP ping only. It is recommended to set Next Hop IP
Address here to the IP address of the NodeB, so that NE2 can respond to near-end IP ping
commands.
d. On the RNC, initiate IP ping to the NodeB (that is, ping 137.0.0.2).
If... Then...
If... Then...
The operation times out A fault occurs between NE1 and the
RNC. Handle the fault.
If... Then...
The operation result is normal A fault occurs between NE2 and the
NodeB. Handle the fault.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
Forwarding
Mirroring Port
Ethernet equipment port
Ethernet tester
Also in the downstream direction. The equipment duplicates the packets transmitted by
the mirroring port to the observing port, and then transmits the packets from the
observing port to the Ethernet tester.
Precautions
The port mirroring function cannot be simultaneously enabled for the ingress and egress
directions of a port on the OptiX RTN 905E.
Procedure
Step 1 Configure the port mirroring function.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
Ethernet tester
Port traffic mirroring duplicates only service traffic matching the specified rule to the
listening port.
Precautions
NOTE
l One NE supports a maximum of four port traffic mirroring (only ingress) or port mirroring
configurations.
l One port supports only one port traffic mirroring configuration. If port traffic mirroring is
configured, ingress port mirroring cannot be configured.
l Port traffic mirroring takes effect only to services packets that are not dropped by the port.
l Port traffic mirroring cannot be configured on the slave port in a LAG.
l Traffic classification rules can be specified by source IP address, destination IP address, protocol
type, source port, destination port, ICMP packet type code, source MAC address, destination MAC
address, C-VLAN ID, C-VLAN PRI, S-VLAN ID, S-VLAN PRI, or IP DSCP, but L2 and L3 rules
cannot coexist.
l MPLS packets can be mirrored only by Ethernet frame header before the MPLS label.
l Only data boards support port traffic mirroring.
l After port traffic mirroring is configured, traffic mirroring rules must not be modified or deleted.
Procedure
Step 1 Configure the port traffic mirroring function.
8
6
2
----End
Prerequisites
l Only OptiX RTN 950(CSHU/CSHUA), OptiX RTN 950A, OptiX RTN 905 1E/2E and
OptiX RTN 910A support this operation.
l You are an NMS user with administrator rights or higher rights.
l Native Ethernet services or PW-carried Ethernet services have been created.
Procedure
Step 1 Click a desired NE in the NE Explorer and choose Diagnose&Maintenance > IP Packet
Marking from the main menu.
Step 2 (Optional) Set the coloring bit. The default value is IP FLAG BIT0.
1. Set the following parameters: ID, Name, Role, Action, and Auto Stop After(minutes).
2. Set the packet matching rules and the logical relationship between the matching rules.
NOTE
l For a QinQ measurement point, set Direction, Service, and QinQ Link.
l For a tunnel measurement point, set Direction, Tunnel ID, Port, PW Label, Service
Tag Role, and PW Type.
Step 6 Click Stop to stop a test or wait for the test to automatically stop.
NOTE
l To stop a test, stop the test for an uplink node and then for a downlink node.
l To delete measurement instances, delete the measurement instance from an uplink node and then from a
downlink node.
----End
Prerequisites
l You must be an NM user with NE administrator authority or higher.
l Ethernet services have been created, and service packets are being forwarded.
l The port is not configured with complex traffic classification.
Context
Headers of Layer 2 and Layer 3 packets can be captured. The header length of smallest Layer
2 packets is 16 bytes, consisting of an SMAC (6 bytes), a DMAC (6 bytes), and a VLAN
header (4 bytes). The header length of largest Layer 3 packets is 74 bytes, consisting of a
longest frame header (34 bytes), an IPv4 header (20 bytes), and a TCP header (20 bytes).
NOTE
This operation is intended to detect transmission faults or errors as required, but may require the collection
and storage of some communication content (at most the first 74 bytes of transmitted packets collected and
stored). Huawei is forbidden to collect or storage communication content without your awareness. It is
recommended that you enable the related function in line with the objective and scope allowed by the local
laws and regulation. You should also take proper measures before performing this operation, to ensure
communication confidentiality.
Precautions
l In a link aggregation group (LAG), physical link aggregation (PLA) group, or enhanced
PLA (EPLA) group, the packet header capturing function can be enabled only for the
master port.
l One-off packet header capturing allows you to capture a maximum of 1000 packets. In
consecutive packet header capturing, the NMS stores the latest 5000 packets captured.
l On the OptiX RTN 905E, headers of Layer 3 packets cannot be captured by source MAC
address or sink MAC address.
l On OptiX RTN 905E, Layer 3 ports allow MPLS packet capturing only based on the
Ethernet header before the MPLS label.
Procedure
l Capture headers of Layer 2 packets.
Select the
desired NE. 3
Set basic parameters.
Select the 3
desired NE.
Set basic parameters.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired CD1 board from the Object Tree in the NE Explorer.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select the desired SDH optical interface board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Automatic Laser Shutdown from the Function Tree.
Step 3 Select a port, and then set Automatic Shutdown to Enabled.
Step 4 Click Apply to save the settings.
Step 5 Close the dialog box that is displayed.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Context
The OptiX RTN 905E supports the PRBS test in the tributary direction and in the cross-
connect direction.
The PRBS test in the tributary direction can be performed to check the connection between
the tributary Unit and the DDF, as shown in Figure 8-6.
PRBS
Transmitter
PRBS
Recevicer
The PRBS test in the cross-connect direction can be performed to check the connection
between the tributary Unit and the remote NE, as shown in Figure 8-7.
PRBS
IN
receiver
Precautions
NOTICE
l During the PRBS test, the services in the tested path are interrupted.
l The PRBS test can be performed only in one path and in one direction at one time.
l A PRBS test can be performed for a CES service that is encapsulated in CESoPSN mode
and is carried by timeslots 1 to 31 on either UNI or NNI side.
l In a PRBS test in the NNI direction for an SATOP CES service, the LOOP_ALM alarm
will be reported on the E1 service where this service is deployed.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Configure a loopback as required by referring to Figure 8-6 and Figure 8-7.
Select an E1
interface board in the
NE Explorer.
1
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Procedure
Step 1 Select a PDH tributary board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > PDH Interface from the Function Tree.
----End
NOTICE
l Before performing a loopback, ensure that the corresponding services are not E-LAN
services. A loopback is forbidden for E-LAN services. Loopbacks include software/
hardware loopback at an Ethernet port, loopback at an IF port, and loopback at an SDH
port or E1 port that carries EoPDH or EoSDH services.
l Loopback operations on E-LAN services may cause network storms and service
interruptions.
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
The optical/electrical interface inloop is a process wherein the signals over an SDH port are
looped back at the overhead processing unit towards the cross-connect unit.
SDH
The optical/electrical interface outloop is a process wherein the signals over an SDH port are
looped back at the overhead processing unit towards a remote device.
SDH
The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at the
logic processing unit towards the cross-connect unit.
VC-4
The VC-4 path outloop is a process wherein the signals on a VC-4 path are looped back at the
logic processing unit towards a remote device.
VC-4
Precautions
NOTICE
l The services may be interrupted at the port or on the path where the loopback is
performed.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
Procedure
Step 1 Select the CD1 board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Select By Function, and select the loopback mode from the drop-down list.
To Perform... Choose...
Optical/electrical interface loopback Optical(Electrical) Interface Loopback
VC-4 path loopback VC4 Loopback
Step 4 Set the loopback status of the port or path based on the requirements.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Context
The E1 port inloop is a process wherein the signals over an E1 port are looped back at the
coding/decoding unit towards the packet switching unit.
Packet
E1 interface unit
switching unit
E1
The E1 port outloop is a process wherein the signals on an E1 port are looped back at the E1
interface board of the local IDU towards the remote equipment.
Packet E1 interface
switching unit unit
E1
Precautions
NOTICE
The services may be interrupted on the port or on the path where the loopback is performed.
Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > PDH Interface from the Function Tree.
Step 3 Select By Function, and select Tributary Loopback from the drop-down list.
Step 4 Set the loopback status of the path based on the requirements.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The IF port inloop is a process wherein the IF signals are looped back at the modem unit
towards the timeslot cross-connect unit.
Timeslot
cross-connect IF unit
unit
IF signal
The IF port outloop is a process wherein the IF signals are looped back at the modem unit of
the NE towards the remote equipment.
Precautions
NOTICE
l The services may be interrupted at the port or on the path where the loopback is
performed.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
l To perform the software loopback on the standby IF board of the 1+1 HSB/FD/SD
protection group, switch the standby IF board to the working state forcedly. Otherwise, the
operation may fail.
NOTICE
When Port Mode of an port is set to Layer 3, do not perform any loopback on the port. In
this case, LSP Traceroute is recommended for locating faults.
Procedure
Step 1 Select the corresponding IF board from the Object Tree in the NE explorer.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The Ethernet port MAC inloop is a process wherein the Ethernet physical signals are looped
back at the service processing module of the board at the MAC layer towards the packet
switching unit. The Ethernet port PHY inloop is a process wherein the Ethernet frame signals
are looped back at the interface module of the board at the PHY layer towards the packet
switching unit.
MAC PHY
Precautions
NOTICE
l A loopback operation results in service interruption.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
NOTICE
When Port Mode of an Ethernet port is set to Layer 3, do not perform any loopback on the
port. In this case, LSP Traceroute is recommended for locating faults.
Procedure
Step 1 Select an Ethernet processing board from the Object Tree in the NE Explorer.
Step 2 Choose Configuration > Interface Management > Ethernet Interface from the Function
Tree.
Step 3 Select the Advanced Attributes tab.
Step 4 Set the loopback status of the port based on the requirements.
Step 5 Click Apply.
Then, the Confirm dialog box is displayed.
Step 6 Click OK.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
The TDM cascading interface inloop is a process wherein the signals over a TDM port are
looped back at the overhead processing unit towards the backplane.
The TDM Cascading Interface outloop is a process wherein the signals over an SDH port are
looped back at the overhead processing unit towards the remote equipment.
Precautions
NOTICE
l The services may be interrupted at the port or on the path where the loopback is
performed.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
Procedure
Step 1 Select the TDM cascading interface board from the NE Explorer.
Step 2 Choose Configuration > SDH Interface from the Function Tree.
Step 3 Set the loopback status of the port or path based on the requirements.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
NOTICE
l The services may be interrupted at the port or on the path where the loopback is
performed.
l A software loopback may be released automatically after a certain period (five minutes, by
defaults). For details, see 8.7 Setting the Automatic Release Function.
Procedure
Step 1 Select the NE in the NE Explorer.
Step 3 Select the desired loopback status for the desired port in the table.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the similar to those on the U2000.
Precautions
NOTICE
The services may be interrupted at the port or on the path where the loopback is performed.
Procedure
Step 1 Select the NE in the NE Explorer.
Step 2 ChooseDiagnoses&Maintenance > Radio Link Loopback from the Function Tree.
Step 4 Select the desired loopback status for the desired object.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Service Trail
Figure 8-19 shows how to locate a fault by performing a loopback operation.
NE1 NE2
PDH TDM
Cross-connect Cross-connect
tributary IF unit ODU ODU IF unit cascading
unit unit
unit interface
NE4 NE3
Cable
Precautions
The LSP Traceroute method, instead of sectional loopbacks, is recommended for locating the
faults of PWE3 services.
Procedure
Step 1 If the services are available on the radio links, perform the inter-station loopbacks to narrow
down the fault to a specific hop.
1. Set the outloops for the TDM cascading interface on NE2 and NE3, and then perform
the inter-station loopbacks to locate the fault.
Step 2 After the fault is located on the specific radio link, perform the intra-station loopbacks to
narrow down the fault to a specific NE or unit.
1. Set inloop for the IF unit on the NEs at both ends of the radio link where the fault
occurs, to check whether the service receiver or the RF/IF faulty.
2. If the fault is located in the service receiver, set outloop for the E1 port to check
whether the interface unit or switch unit is faulty.
3. If the radio link is faulty, replace the IF unitand ODU to check whether the IF unit or
ODU is faulty.
----End
Background Information
Hardware loopback is classified into optical cable loopback, PDH cable loopback, and
Ethernet electrical port loopback.
l Optical cable loopback indicates that the receive and transmit optical fibers are
connected through a fiber jumper on the ODF. In certain occasions, an optical attenuator
is added based on the actual situation, to prevent the optical SFP from being damaged by
the excessive receive optical power.
l PDH cable loopback indicates that the receive and transmit PDH cables are connected
through a short-circuiting cable or connector on the DDF.
l Ethernet electrical port loopback indicates that the receive and transmit service signals
on one Ethernet port are looped back through a special loopback Ethernet cable.
NOTICE
l Before performing a loopback, ensure that the corresponding services are not E-LAN
services. A loopback is forbidden for E-LAN services. Loopbacks include software/
hardware loopback at an Ethernet port, loopback at an IF port, and loopback at an SDH
port or E1 port that carries EoPDH or EoSDH services.
l Loopback operations on E-LAN services may cause network storms and service
interruptions.
8.6 Reset
Reset is an important method of troubleshooting software faults. Reset is classified into cold
reset, warm reset.
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
NOTICE
l Cold reset causes service interruption because it is similar to the procedure of removing
and inserting a board.
l Do not configure a board that is being reset.
l Do not modify IF configurations when an ODU is being reset. Otherwise, the
configurations may be incorrect or do not take effect.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the cold reset needs to be
performed.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Precautions
During warm reset, the board software is reset but the services are not interrupted.
NOTICE
l Do not configure a board that is being reset.
l Do not modify IF configurations when an ODU is being reset. Otherwise, the
configurations may be incorrect or do not take effect.
Procedure
Step 1 In Running Status of the U2000, right-click the board where the warm reset needs to be
performed.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function
from the Main Menu.
NOTE
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Power Management from the Main
Menu.
Step 2 In the NE Power dialog box, select the Board Power tab.
Step 3 Select the required NE or board from the object tree, and then click .
Step 6 On the Board Power tab page, browse Nominal Power Consumption and Current Power
Consumption of the selected board.
----End
Prerequisites
You must be an NM user with NE maintainer authority or higher.
NOTE
Procedure
Step 1 Query the optical power and alarm thresholds of SDH ports.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
l If a UNI receives a loop detection packet whose destination MAC address is the same as
the source MAC address of the loop detection packet sent by the UNI, a service loop
occurs. If a UNI does not receive a loop detection packet within the specified duration, a
service loop does not occur. The duration ranges from 3s to 10s and the default value is
3s. Upon the detection of a service loop, the looped service is automatically disabled.
l Automatic service loop detection disables the looped service rather than the UNI.
Disabling of the looped service does not affect the other services on the UNI.
l Service loop detection packets are forwarded along the service forwarding path.
Precautions
l If Initiate upon Service Creation is Auto, service loop detection will be automatically
initiated after a logical port is added. If multiple services carrying different VLAN IDs
are added on a logical port, service loop detection will be initiated on any two services
among them. If a loop is detected on either of the two services, all the newly added
services are disabled.
l If Initiate upon Port Status Change is Auto, service loop detection will be
automatically initiated on all logical ports on a physical port after the physical port
changes from Down to Up. If a logical port is configured with multiple services carrying
different VLAN IDs, service loop detection will be automatically initiated on any two
services among them. If a loop is detected on either of the two services, the logical port
is disabled. If the other services are looped, no service loop can be detected.
Procedure
Step 1 In the NE Explorer, select an NE from the object tree, and choose Diagnosis&Maintenance >
E-LAN LD Test Management from the function tree.
----End
Prerequisites
You must be an NM user with NE operator authority or higher.
NOTE
Web LCT also supports this operation and the steps are the same as those on the U2000.
Context
Upon detection of MAC address flapping, an NE reports A.3.54 ELAN_SMAC_FLAPPING
alarms.
Precautions
NOTE
l EG6 boards support the suppression of broadcast, unknown multicast, and unknown unicast packets.
l ISV3 boards support the suppression of broadcast, unknown multicast, and unknown unicast
packets.
l In a LAG group, PLA group consisting of IF boards, IF 1+1 protection group, or IF N+1 protection
group, the slave/standby port automatically synchronizes the broadcast packet suppression threshold
from the master/main port.
l In an EPLA group, the slave port automatically synchronizes the broadcast packet suppression
threshold from the master port and supports the suppression of broadcast, unknown multicast, and
unknown unicast packets.
l If MAC address flapping occurs on multiple ports, the automatic broadcast packet suppression
function can suppress packets at only two ports.
Procedure
Step 1 Enable the automatic broadcast packet suppression function.
1
3
Select the NE.
4
Enable automatic
broadcast packet
suppression
3
Select the NE.
4
Threshold for enabling
automatic broadcast
packet suppression
NOTE
If an automatic broadcast packet suppression threshold is specified and another broadcast packet
suppression threshold is set in the Ethernet port attributes, the smaller threshold will actually take effect.
----End
In this case, the system performance deteriorates. Hence, the fiber connectors or adapters that
are terminated need to be cleaned in time.
Prerequisites
l Disconnect both ends of the fiber. Ensure that there is no laser light on the fiber
connectors.
l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.
Procedure
Step 1 Press down and hold the lever. Then, 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 8-21 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 8-22 Dragging the fiber tip slightly on the other cleaning area
----End
Prerequisites
l Disconnect both ends of the fiber. ensure that there is no laser light on the fiber
connectors.
l Inspect the fiber connector with a fiber microscope to ensure that the fiber connectors are
contaminated.
l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.
Do not use alcohol or formalin.
l The fiber cleaning tissue or lint-free wipes can substitute the non-woven lens tissue.
l The special cleaning roll can substitute the special compressed gas.
Procedure
Step 1 Place a small amount of cleaning solvent on the lens tissue.
Step 2 Drag the fiber tip slightly on the lens tissue.
Step 3 Repeat Step 2 several times on the areas of the lens tissue that have not been used.
Step 4 Use the compressed gas to blow the fiber tip.
When using compressed gas, note the following points:
l First spray it into the air because the initial spray of condensation may contain certain
sediment.
l Ensure that the injector nozzle is as close as possible to (but does not touch) the
connector surface.
----End
Prerequisites
l Before you clean the fiber adapter, remove the optical fiber and shut down the laser. For
details about how to shut down a laser, see 8.3.1 Setting the On/Off State of the Laser.
l Inspect the fiber adapter with a fiber microscope to ensure that the fiber adapter is
contaminated.
l In the case of the SC and FC optical interface, use the cleaning stick with a diameter of 2.5 mm. In
the case of the LC optical interface, use the cleaning stick with a diameter of 1.25 mm.
l The medical cotton or long fiber cotton can substitute the optical cleaning stick.
l The isoamylol is preferred as the clean solvent, and the propyl can also be used as the clean solvent.
Do not use alcohol or formalin.
l The special cleaning roll can substitute the special compressed gas.
Procedure
Step 1 Apply a small amount of cleaning solvent on the optical cleaning stick.
Step 2 Touch the adapter gently with the optical cleaning stick 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 Use the compressed gas to blow the fiber adapter.
When using compressed gas, note the following points:
l First spray the compressed gas into the air because the initial spray of condensation gas
may contain some sediment.
l Ensure that the injector nozzle is as close as possible to (but does not touch) the inner
surface of the connector.
----End
A Alarm Reference
Alarms are important indicators when abnormalities occur on the equipment. This chapter
describes all the possible alarms on the OptiX RTN 905E and how to handle these alarms.
A.1 Alarm List (in Alphabetical Order)
The following table lists all the possible alarms generated by the OptiX RTN 905E in
alphabetical order.
A.2 Alarm List (Classified by Logical Boards)
This part lists the alarms that are reported by each board.
A.3 Alarms and Handling Procedures
This chapter describes all the alarms on the OptiX RTN 905E in alphabetical order and how to
handle these alarms.
LCS_DAYS_OF_GR The license file has expired but is still in the Major
ACE grace period.
LCS_EXPIRED The license file has expired and its grace period Critical
has timed out.
LPT_CFG_CLOSEP The LPT closes the access port of the local NE. Major
ORT
MAC_FCS_SD Signal degrade bit errors at the MAC layer cross Major
the threshold.
ODC_BATTERY_P The storage battery fails to supply power for the Major
WRDOWN equipment.
V5_VCAIS Bits 5-7 in the V5 byte of a VC-12 path are set Major
to "1"s.
NOTE
The NE software consider a physical board as one or more logical boards when managing the physical board.
The NMS also considers a physical board as one or more logical boards when managing the physical board.
Figure A-1 shows the logical boards corresponding to all physical boards
Figure A-1 Logical board layout of the OptiX RTN 905 IDU
IDU 905 1E
PIU ISV3 CSHP AUX EG6 VS2 MP1 CD1 MN1 FAN
Slot 5 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
IDU 905 2E
PIU ISV3 ISV3 CSHP AUX EG6 VS2 MP1 CD1 MN1 FAN
Slot 5 Slot 4 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
NOTE
The logical slot number of the ODU is 20 plus the slot number for the IF board that is connected to the
ODU
A.2.1 AUX
l BD_STATUS
l HARD_BAD
l RELAY_ALARM_CRITICAL
l RELAY_ALARM_IGNORE
l RELAY_ALARM_MAJOR
l RELAY_ALARM_MINOR
A.2.2 CD1
l ALM_E1RAI l CES_STRAYPKT_E l LMFA l OUT_PWR_ABN
l AU_AIS XC l LOOP_ALM l PPP_LCP_FAIL
l CESPW_OPPOSITE_ l LP_RDI_VC12 l PPP_NCP_FAIL
l AU_LOP
ACFAULT
l B1_EXC l LP_REI_VC12 l R_LOC
l CESPW_OPPOSITE_
l B1_SD RAI l LP_RFI l R_LOF
A.2.3 CSHP
l ACR_LOCK_FAIL l LCS_LIMITED l MPLSLSP_TBL_LA l SSL_CERT_DAMAG
l APS_FAIL l LCS_TRIAL_PERIO CK ED
A.2.4 EG2
l ARP_FAIL l ETH_EFM_DF l LAG_MEMBER_DO l OUT_PWR_ABN
l BD_STATUS l ETH_EFM_EVENT WN l PORT_EXC_TRAFFI
l BRDCASTRATIO_O l LASER_MOD_ERR C
l ETH_EFM_LOOPBA
VER CK l LASER_SHUT l PORTMODE_MISM
l BUS_ERR l LOOP_ALM ATCH
l ETH_EFM_REMFAU
l DROPRATIO_OVER LT l LPT_CFG_CLOSEP l R_LOS
l ERPS_IN_PROTECT l ETH_LOS ORT l TF
ION l ETH_NO_FLOW l LSR_NO_FITED l WRG_BD_TYPE
l ETH_AUTO_LINK_ l LSR_WILL_DIE
l ETH_PWR_SUPPLY
DOWN l MAC_EXT_EXC
_FAIL
l ETH_CFM_AIS l MAC_FCS_EXC
l ETHOAM_SELF_LO
l ETH_CFM_LOC OP l MAC_FCS_SD
l ETH_CFM_MISMER l FLOW_OVER l MULTI_RPL_OWNE
GE R
l HARD_BAD
l ETH_CFM_RDI
l IN_PWR_ABN
l ETH_CFM_UNEXPE
RI l LAG_DOWN
A.2.5 EG6
l ARP_FAIL l ETH_EFM_DF l LAG_DOWN l MULTI_RPL_OWNE
l BD_STATUS l ETH_EFM_EVENT l LAG_MEMBER_DO R
l BRDCASTRATIO_O l ETH_EFM_LOOPBA WN l OUT_PWR_ABN
VER CK l LASER_MOD_ERR l PORT_EXC_TRAFFI
l BUS_ERR l ETH_EFM_REMFAU l LASER_SHUT C
l DROPRATIO_OVER LT l LSR_WILL_DIE l PORTMODE_MISM
l ETH_LOS ATCH
l ERPS_IN_PROTECT l LOOP_ALM
ION l ETH_NO_FLOW l R_LOS
l LPT_CFG_CLOSEP
l ETH_AUTO_LINK_ l ETH_PWR_SUPPLY ORT l TF
DOWN _FAIL l LSR_NO_FITED l WRG_BD_TYPE
l ETH_CFM_AIS l ETHOAM_SELF_LO l MAC_EXT_EXC
l ETH_CFM_LOC OP
l MAC_FCS_EXC
l ETH_CFM_MISMER l FLOW_OVER
l MAC_FCS_SD
GE l HARD_BAD
l ETH_CFM_RDI l IN_PWR_ABN
l ETH_CFM_UNEXPE
RI
A.2.6 FAN
l BD_STATUS
l FAN_AGING
l FAN_FAIL
l POWER_ALM
l WRG_BD_TYPE
A.2.7 ISV3
l AM_DOWNSHIFT l ETH_CFM_RDI l LAG_DOWN l MW_CFG_MISMAT
l ARP_FAIL l ETH_CFM_UNEXPE l LAG_MEMBER_DO CH
l AU_AIS RI WN l MW_CONT_WAVE
l AU_LOP l ETH_EFM_DF l LCS_LIMITED l MW_E1_LOST
l B1_EXC l ETH_EFM_EVENT l LICENSE_LOST l MW_FEC_UNCOR
l B1_SD l ETH_EFM_LOOPBA l LOOP_ALM l MW_LIM
l B2_EXC CK l LP_RDI l MW_LOF
l B2_SD l ETH_EFM_REMFAU l LP_REI l MW_RDI
LT l LP_UNEQ l PORT_EXC_TRAFFI
l B3_EXC
l ETH_NO_FLOW l MAC_EXT_EXC C
l B3_SD
l ETHOAM_SELF_LO l MAC_FCS_EXC l PASSWORD_NEED_
l BD_STATUS CHANGE
OP
l BIP_EXC l MS_AIS
l FLOW_OVER l R_LOC
l BIP_SD l MS_CROSSTR
l FLOW_EXC_LCS l R_LOF
l BRDCASTRATIO_O l MS_RDI
l HARD_BAD l RS_CROSSTR
VER l MS_REI
l T_LOC
l BUS_ERR l HP_CROSSTR l MSAD_CROSSTR
l TU_AIS
l COMPRESS_MISM l HP_LOM l MULTI_RPL_OWNE
ATCH R l TU_LOP
l HP_RDI
l DROPRATIO_OVER l MW_AM_TEST l VOLT_LOS
l HP_REI
l ERPS_IN_PROTECT l MW_BER_EXC l WRG_BD_TYPE
l HP_SLM
ION l MW_BER_SD l XPIC_LOS
l HP_TIM
l ETH_CFM_AIS
l HP_UNEQ
l ETH_CFM_LOC
l ETH_CFM_MISMER l IF_CABLE_OPEN
GE l LAG_BWMM
A.2.8 MN1
l BD_STATUS
l BUS_ERR
l HARD_BAD
l WRG_BD_TYPE
A.2.9 MP1
l A_LOC l CES_RDI l LMFA l LP_UNEQ
l ALM_E1RAI l CES_STRAYPKT_E l LOOP_ALM l MP_DELAY
XC l LP_CROSSTR l MP_DOWN
l BD_STATUS
l CESPW_OPPOSITE_ l LP_R_FIFO l PPP_LCP_FAIL
l BIP_EXC
ACFAULT
l BIP_SD l LP_RDI l PPP_NCP_FAIL
l CESPW_OPPOSITE_
l CES_ACR_LOCK_A RAI l LP_REI l T_ALOS
BN l DDN_LFA l LP_RFI l TU_AIS
l CES_JTROVR_EXC l DOWN_E1_AIS l LP_SLM l TU_LOP
l CES_JTRUDR_EXC l E1_LOC l LP_T_FIFO l UP_E1_AIS
l CES_LOSPKT_EXC l E1_LOS l LP_TIM
l CES_MALPKT_EXC l HARD_BAD
l CES_MISORDERPK l HPAD_CROSSTR
T_EXC l LFA
A.2.10 ODU
l BD_STATUS l LOOP_ALM l RADIO_RSL_BEYO l RADIO_TSL_LOW
l CONFIG_NOSUPPO l POWER_ALM NDTH l TEMP_ALARM
RT l RADIO_FADING_M l RADIO_RSL_HIGH l WRG_BD_TYPE
l HARD_BAD ARGIN_INSUFF l RADIO_RSL_LOW
l IF_INPWR_ABN l RADIO_MUTE l RADIO_TSL_HIGH
A.2.11 PIU
l BD_STATUS
l HARD_BAD
l POWER_ABNORMAL
l THUNDERALM
l WRG_BD_TYPE
A.2.12 PMU
l BAT1TEMP_SENSO l ENVTEMP2_SENSO l ODC_HUMI_ABN l ODC_SURGE_PROT
R_FAIL R_FAIL l ODC_LOAD_PWRD ECTION_FAIL
l BAT2TEMP_SENSO l HARD_BAD OWN l ODC_TEMP_ABN
R_FAIL l ODC_BATTERY_CU l ODC_MDL_ABN l ODC_WATER_ALM
l BD_STATUS RRENT_ABN l ODC_POWER_FAIL l WRG_BD_TYPE
l ENVHUM_SENSOR l ODC_BATTERY_PW l ODC_SMOKE_OVE
_FAIL RDOWN R
l ENVTEMP1_SENSO l ODC_DOOR_OPEN
R_FAIL
A.2.13 TCU
l BD_STATUS l INTEMP_SENSOR_ l ODC_SURGE_PROT l OUT1TEMP_SENSO
l BDTEMP_SENSOR_ FAIL ECTION_FAIL R_FAIL
FAIL l ODC_DOOR_OPEN l ODC_TEC_ALM l OUT2TEMP_SENSO
l ENVTEMP_SENSOR l ODC_FAN_FAILED l ODC_TEMP_ABN R_FAIL
_FAIL l ODC_SMOKE_OVE l ODC_WATER_ALM l WRG_BD_TYPE
l HARD_BAD R
A.2.14 VS2
l ALM_E1RAI l CES_STRAYPKT_EXC l PORT_MODULE_OFFL
l BD_STATUS l CESPW_OPPOSITE_A INE
CFAULT l PPP_LCP_FAIL
l CES_ACR_LOCK_ABN
l CESPW_OPPOSITE_R l PPP_NCP_FAIL
l CES_JTROVR_EXC
AI l R_LOS
l CES_JTRUDR_EXC l LFA l TU_AIS
l CES_LOSPKT_EXC l LMFA l TU_AIS_VC12
l CES_MALPKT_EXC l LOOP_ALM l UP_E1_AIS
l CES_MISORDERPKT_ l LSR_NO_FITED
EXC
l MP_DELAY
l CES_RDI l MP_DOWN
A.3.1 A_LOC
Description
The A_LOC is an alarm indicating that a clock signal is lost in the uplink bus.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: A certain board is faulty.
Procedure
Step 1 Cause 1: A certain board is faulty.
----End
Related Information
None
A.3.2 ACR_LOCK_FAIL
Description
The ACR_LOCK_FAIL is an alarm indicating an IEEE 1588 ACR locking failure. This alarm
is reported when the NE works in 1588 ACR mode and the clock fails to be locked.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: indicates that the phase-locked loop (PLL) is in holdover or free-run
mode.
l 0x02: indicates that the Sync timestamp remains unchanged when the
Precision Time Protocol (PTP) clock is synchronized.
l 0x03: indicates that the PDV on the transport network exceeds the upper
threshold.
l 0x04: indicates that the ACR algorithm is in the quick lockout phase.
Possible Causes
l Cause 1: The frequency deviation of the clock source or the delay of the intermediate
network exceeds the upper threshold.
l Cause 2: The physical link where the traced clock source resides is faulty.
Procedure
Step 1 Handle the alarm according to the alarm parameters.
If... Then...
Parameter 1 = 0x04 No further action is required. Wait for a while (about 15 minutes).
Then, check whether the alarm is cleared.
Step 2 Check whether a hardware alarm such as HARD_BAD occurs on the SCC board or interface
board that accesses clocks. If yes, clear the alarm immediately.
Step 3 Query the PDV performance of the NE to determine whether the third-party network is
running properly. If not, ask the customer to optimize the PDV. For details about how to
query PDV performance of the local NE, see B.3.6 CURPOSITIVEPDV and
CURNEGATIVEPDV.
Step 4 Check the status of the master NE. If the master NE is abnormal, troubleshoot the abnormality
first.
----End
Related Information
None
A.3.3 ALM_E1RAI
Description
The ALM_E1RAI is an alarm indicating that the E1 link on the opposite NE reports alarms.
This alarm is reported on the local NE when the T_ALOS, UP_E1_AIS, DOWN_E1_AIS,
LFA, or LMFA alarm is reported on the opposite NE.
Attribute
Parameters
None
Possible Causes
l Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA,
UP_E1_AIS, or DOWN_E1_AIS alarm.
Procedure
Step 1 Cause 1: The E1 link on the opposite NE reports the T_ALOS, LFA, LMFA, UP_E1_AIS,
or DOWN_E1_AIS alarm.
----End
Related Information
None
A.3.4 AM_DOWNSHIFT
Description
The AM_DOWNSHIFT alarm indicates the downshift of the AM scheme. This alarm occurs
after the AM mode is downshifted from the highest-order modulation scheme to the lower-
order modulation scheme. After the AM mode is upshifted from the lower-order modulation
scheme to the highest-order modulation scheme, this alarm is cleared.
Figure A-2 shows the process of reporting an AM_DOWNSHIFT alarm. To be specific, upon
detecting that the signal-to-noise ratio (SNR) deteriorates, the receive end transmits an AM
shift indication signal to the transmit end; upon receiving the signal, the transmit end
downshifts the AM mode and reports an AM_DOWNSHIFT alarm, and the receive end also
downshifts the AM mode but does not report any AM_DOWNSHIFT alarm.
NOTE
AM mode shifts in the two microwave directions are independent of each other.
4 1
IF board IF board
3 2
Transmit end Receive end
Attribute
Parameters
None
Possible Causes
l Cause 1: The external factors (for example, the climate) cause the degradation of the
working channels.
l Cause 2: There are interferences around the working channels.
l Cause 3: The ODU at the transmit end has abnormal transmit power.
l Cause 4: The ODU at the receive end has abnormal receive power.
Procedure
Step 1 Cause 1: The external factors (for example, the climate) cause the degradation of the working
channels.
1. When the external factors (for example, the climate) cause the degradation of the
working channels, the downshift of the AM scheme is normal. Hence, no measures
should be taken to handle the alarm.
Step 3 Cause 3: The ODU at the transmit end has abnormal transmit power.
1. Use the NMS to check whether the transmit power of the ODU at the transmit end is
normal. For details on troubleshooting at the transmit end, see Troubleshooting
Microwave Links.
Step 4 Cause 4: The ODU at the receive end has abnormal receive power.
1. Use the NMS to check whether the receive power of the ODU at the receive end is
normal. For details on troubleshooting at the receive end, see Troubleshooting
Microwave Links.
----End
Related Information
None
A.3.5 APS_FAIL
Description
The APS_FAIL is an alarm indicating that the MS protection 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
Possible Causes
l Cause 1: The parameters of the MSP protocol are set incorrectly.
l Cause 2: The parameters of the MSP protocol are lost.
Procedure
Step 1 Cause 1: The parameters of the MSP protocol are set incorrectly.
1. Check whether the parameters of the MSP protocol are set correctly.
If... Then...
The parameters are set incorrectly Set the parameters correctly.
The parameters are set correctly Go to the next step.
If... Then...
The alarm is cleared after the protocol is End the alarm handling.
restarted
The alarm persists after the protocol is Contact Huawei engineers to handle
restarted the alarm.
----End
Related Information
None
A.3.6 APS_INDI
Description
The APS_INDI alarm indicates that MS protection switching occurs.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
Possible Causes
Cause 1: MS protection switching occurs.
Procedure
Step 1 Cause 1: MS protection switching occurs.
1. Query the linear MSP group.
2. Check whether the MSP protocol is in the manual switching state, forced switching state,
or locked switching state. If yes, release the switching and check whether the alarm is
cleared.
3. Check whether the MSP protocol is in the automatic switching state. Do as follows:
a. Handle the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm that the
equipment reports. After the alarms are cleared, wait until the MSP protocol is
changed from the automatic switching state to the normal state. Then, check
whether the APS_INDI alarm is cleared.
b. Check whether the service board configured with the MSP protocol is faulty. If yes,
replace the faulty board and then check whether the APS_INDI alarm is cleared.
----End
Related Information
This alarm is also reported upon a packet-based linear MSP switching. For querying the
packet-based Linear MSP group, refer toQuerying the Status of a Packet-based Linear MSP
Group.
A.3.7 APS_MANUAL_STOP
Description
The APS_MANUAL_STOP is an alarm indicating that the MSP protocol is stopped
manually.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
Possible Causes
Cause 1: The MSP protocol is stopped manually.
Procedure
Step 1 Cause 1: The MSP protocol is stopped manually.
1. Enable/Disable the linear MSP protocol.
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For enabling/disabling the
packet linear MSP protocol, refer toEnabling/Disabling the Linear MSP Protocol.
A.3.8 ARP_FAIL
Description
The ARP_FAIL alarm indicates that an Ethernet port fails to learn the MAC address of the
remote end using the ARP.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicate the VLAN ID of a VLAN subinterface. The parameters take
the fixed value of 0xfff for a non-VLAN sub-interface.
Possible Causes
l Cause 1: IP addresses of ports at both ends are not in the same network segment, or the
ports are not configured with IP addresses.
l Cause 2: A physical loop exists.
Procedure
Step 1 Cause 1: IP addresses of ports at both ends are not in the same network segment, or the ports
are not configured with IP addresses.
1. Check whether the interconnected ports at both ends are configured with IP addresses. If
no, configure IP addresses according to the network plan.
2. Check whether IP addresses of the ports at both ends are in the same network segment. If
no, reconfigure IP addresses according to the network plan.
Step 2 Cause 2: A physical loop exists.
1. Check the physical connections between NEs to release the physical loop.
----End
Related Information
None
A.3.9 AU_AIS
Description
The AU_AIS is an alarm indicating the administrative unit (AU). This alarm occurs when the
board detects the AU pointer of all 1s for three consecutive frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The opposite NE inserts the AU_AIS alarm.
l Cause 2: The transmit unit of the opposite NE is faulty.
l Cause 3: The receive unit of the local NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE inserts the AU_AIS alarm.
If... Then...
The alarm that triggers the AU_AIS insertion occurs Clear the alarm immediately.
No such alarms that trigger the AU_AIS insertion occur Go to Cause 2.
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm
handling.
The alarm persists after replacement Go to the next step.
----End
Related Information
None
A.3.10 AU_LOP
Description
The AU_LOP is an alarm indicating the loss of the AU pointer. This alarm occurs when a
board detects the AU pointer of invalid values or with the NDF for eight consecutive frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The transmit unit of the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite NE is faulty.
1. Replace the IDU or the line board at the opposite end.
If... Then...
The alarm is cleared after replacement The fault is rectified. End the alarm
handling.
The alarm persists after replacement Go to the next step.
----End
Related Information
None
A.3.11 B1_EXC
Description
The B1_EXC is an alarm indicating that the B1 errors (in the regenerator section) exceed the
threshold. This alarm occurs when the board detects that the B1 errors exceed the preset
B1_EXC alarm threshold (10-3 by default).
An IF board that works in PDH mode may also report this alarm. This alarm is detected by
using the self-defined overhead byte B1 in PDH microwave frames.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity.
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber.
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, clear the alarm.
If... Then...
The clock source of the local NE The clock may become asynchronous and B1
is different from the clock source errors may occur. Reconfigure the clock source,
of the opposite NE and ensure that the clock is synchronized on the
local NE and opposite NE.
The clock of the local NE and the This may cause errors and even service
clock of the opposite NE form a interruption. In this case, reconfigure the clock
timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces
of the NE by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical interfaces are Replace the local IDU.
looped back
The fault is rectified after the optical interfaces are Replace the opposite IDU.
looped back
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the local IDU.
interface is looped back
The fault is rectified after the multiplexing interface is Replace the opposite
looped back IDU.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.
A.3.12 B1_SD
Description
The B1_SD is an alarm indicating that the signal degrades due to the excessive B1 errors (in
the regenerator section). This alarm occurs when the board detects that the B1 errors exceed
the preset B1_SD alarm threshold (10-6 by default) but do not reach the preset B1_EXC alarm
threshold (10-3 by default).
An IF board that works in PDH mode may also report this alarm. This alarm is detected by
using the self-defined overhead byte B1 in PDH microwave frames.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is
generated. If yes, clear the alarm.
If... Then...
The clock source of the local NE The clock may become asynchronous and errors
is different from the clock source may occur. Reconfigure the clock source, and
of the opposite NE ensure that the clock is synchronized on the local
NE and opposite NE.
If... Then...
The clock of the local NE and the This may cause errors and even service
clock of the opposite NE form a interruption. In this case, reconfigure the clock
timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The SDH optical line board of the local NE is faulty. Loop back the optical interfaces of
the NE by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical Replace the IDU.
interfaces are looped back
The fault is rectified after the optical Replace the IDU or the board where
interfaces are looped back the line unit is located on the
opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the IDU.
interface is looped back
The fault is rectified after the multiplexing Replace the IDU or the alarmed
interface is looped back IF board on the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.
A.3.13 B2_EXC
Description
The B2_EXC is an alarm indicating that the B2 errors (in the multiplex section) exceed the
threshold. This alarm occurs when the board detects that the number of B2 errors exceeds the
preset B2_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel to locate the fault.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, clear the alarm.
If... Then...
The clock source of the local NE The clock may become asynchronous and errors
is different from the clock source may occur. Reconfigure the clock source, and
of the opposite NE ensure that the clock is synchronized on the local
NE and opposite NE.
The clock of the local NE and the This may cause errors and even service
clock of the opposite NE form a interruption. In this case, reconfigure the clock
timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces
of the NE by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical Replace the IDU.
interfaces are looped back
The fault is rectified after the optical Replace the IDU or the board where
interfaces are looped back the line unit is located on the
opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the IDU.
interface is looped back
The fault is rectified after the multiplexing Replace the IDU or the alarmed
interface is looped back IF board on the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.
A.3.14 B2_SD
Description
The B2_SD is an alarm indicating that the signal degrades due to the excessive B2 errors (in
the multiplex section). This alarm occurs when the board detects that the number of B2 errors
is higher than the preset B2_SD alarm threshold (10-6 by default) and lower than the preset
B2_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel to locate the fault.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is
generated. If yes, clear the alarm.
Step 3 Cause 3: The network clock quality degrades.
1. Check the network clock status of the alarmed NE.
If... Then...
The clock source of the local NE The clock may become asynchronous and errors
is different from the clock source may occur. Reconfigure the clock source, and
of the opposite NE ensure that the clock is synchronized on the local
NE and opposite NE.
The clock of the local NE and the This may cause errors and even service
clock of the opposite NE form a interruption. In this case, reconfigure the clock
timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical Replace the IDU.
interfaces are looped back
The fault is rectified after the optical Replace the IDU or the board where
interfaces are looped back the line unit is located on the
opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the IDU.
interface is looped back
The fault is rectified after the multiplexing Replace the IDU or the alarmed
interface is looped back IF board on the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
Handle the errors of TDM services.
A.3.15 B3_EXC
Description
The B3_EXC is an alarm indicating that the B3 errors (in the higher order path) exceed the
threshold. This alarm occurs when the board detects that the number of B3 errors exceeds the
preset B3_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel to locate the fault.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR or
RPS_INDI alarm is reported. If yes, clear the alarm.
If... Then...
The clock source of the local NE In this case, the clock may become asynchronous
is different from the clock source and errors may occur. Reconfigure the clock
of the opposite NE source, and ensure that the clock is synchronized
on the local NE and opposite NE.
The clock of the local NE and This may cause errors and even service
the clock of the opposite NE interruption. In this case, reconfigure the clock
form a timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The board of the SDH line unit on the local NE is faulty. Loop back the optical interfaces
of the NE by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical Replace the IDU.
interfaces are looped back
The fault is rectified after the optical Replace the IDU or the board where
interfaces are looped back the line unit is located on the
opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the IDU.
interface is looped back
The fault is rectified after the multiplexing Replace the IDU or the alarmed
interface is looped back IF board on the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
A.3.16 B3_SD
Description
The B3_SD is an alarm indicating that the signal degrades due to the excessive B3 errors (in
the higher order path). This alarm occurs when the board detects that the number of B3 errors
is higher than the preset B3_SD alarm threshold (10-6 by default) and lower than the preset
B3_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 2: The line performance degrades (if the alarm is reported by an IF board).
l Cause 3: The network clock quality degrades.
l Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
l Cause 5: The board is faulty (if the alarm is reported by an IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. Check whether the transmit power at the opposite end and the receive power at the local
end meet the specifications of the optical interfaces. For details, see 4.3.3 Browsing
Current Performance Events.
If... Then...
The transmit power of the opposite NE is over low Replace the SFP on the
opposite NE.
If... Then...
The transmit power of the opposite NE is normal, but The fiber is faulty. Go to the
the receive power of the local NE is close to the value next step.
(for example, within 3 dB) of the receiver sensitivity
2. Exchange the core fibers of the optical cables in the receive and transmit directions of a
channel to locate the fault.
If... Then...
The errors vary with the change of the fiber The fiber is faulty. Go to the next step.
The errors do not vary with the change of Ensure that the board is normal.
the fiber
3. If the fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out of the equipment room are pressed,
and whether the fiber connector is dirty. If yes, replace the fiber jumper or fiber
connector.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an IF board).
1. Check whether the MW_BER_EXC, MW_BER_SD, MW_FEC_UNCOR alarm is
generated. If yes, clear the alarm.
If... Then...
The clock source of the local NE In this case, the clock may become asynchronous
is different from the clock source and errors may occur. Reconfigure the clock
of the opposite NE source, and ensure that the clock is synchronized
on the local NE and opposite NE.
The clock of the local NE and This may cause errors and even service
the clock of the opposite NE interruption. In this case, reconfigure the clock
form a timing loop source and release the timing loop.
Step 4 Cause 4: The board is faulty (if the alarm is reported by an SDH optical interface board).
1. The SDH optical/electrical line board of the local NE is faulty. Loop back the optical
interfaces of the station by using a fiber jumper to locate the fault.
If... Then...
The fault is not rectified after the optical Replace the IDU.
interfaces are looped back
The fault is rectified after the optical Replace the IDU or the board where
interfaces are looped back the line unit is located on the
opposite NE.
Step 5 Cause 5: The board is faulty (if the alarm is reported by an IF board).
1. Perform an inloop for the multiplexing interface of the IF board on the local NE.
If... Then...
The fault is not rectified after the multiplexing Replace the IDU.
interface is looped back
The fault is rectified after the multiplexing Replace the IDU or the alarmed
interface is looped back IF board on the opposite NE.
----End
Related Information
The handling procedure applies when this alarm is reported by the STM-1e port.
A.3.17 BAT1TEMP_SENSOR_FAIL
Description
The BAT1TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of
battery group 1 fails.
Attribute
Parameters
None
Possible Causes
l Cause 1: The temperature sensor of battery group 1 is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The temperature sensor is not installed.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 1 is faulty.
1. Replace the temperature sensor of battery group 1.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.18 BAT2TEMP_SENSOR_FAIL
Description
The BAT2TEMP_SENSOR_FAIL is an alarm indicating that the temperature sensor of
battery group 2 fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The temperature sensor of battery group 2 is faulty.
Procedure
Step 1 Cause 1: The temperature sensor of battery group 2 is faulty.
1. Replace the temperature sensor of battery group 2.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.19 BD_NOT_INSTALLED
Description
The BD_NOT_INSTALLED is an alarm indicating that the physical board is installed in a
certain slot, but the logical board is not added.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicates the ID of the slot.
Possible Causes
Cause 1: The logical board is not added in the corresponding logical slot.
Procedure
Step 1 Cause 1: The logical board is not added in the corresponding logical slot.
1. Configure the logical board.
2. If the BD_NOT_INSTALLED alarm persists, replace the IDU.
----End
Related Information
None
A.3.20 BD_STATUS
Description
The BD_STATUS is an alarm indicating that the board cannot be detected.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
If the alarm is reported by the IDU, the possible causes are as follows:
If the alarm is reported by the ODU, the possible causes are as follows:
l Cause 1 of the alarm reported by the ODU: The other alarms are generated.
l Cause 2 of the alarm reported by the ODU: The ODU is faulty.
Procedure
Step 1 Cause 1 of the alarm reported by the IDU: The NE is faulty.
1. Replace the alarmed IDU.
Step 2 Cause 1 of the alarm reported by the ODU: The other alarms are generated.
1. Query whether the IF unit reports the HARD_BAD, BD_STATUS,
IF_CABLE_OPEN, BD_NOT_INSTALLED or VOLT_LOS alarm.
If... Then...
The IF unit reports any of the preceding alarms Clear the alarm immediately.
The IF unit does not report any of the preceding Replace the alarmed ODU.
alarms
Step 3 Cause 2 of the alarm reported by the ODU: The ODU is faulty.
1. Replace the alarmed ODU.
----End
Related Information
None
A.3.21 BDTEMP_SENSOR_FAIL
Description
The BDTEMP_SENSOR_FAIL is an alarm indicating that the board temperature sensor of
the cabinet fails.
Attribute
Parameters
None
Possible Causes
l Cause 1: The board temperature sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The board temperature sensor is not installed.
Procedure
Step 1 Cause 1: The board temperature sensor is faulty.
1. Replace the board temperature sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.22 BGPBACKTRANSITION
Description
The BGPBACKTRANSITION alarm indicates that a Border Gateway Protocol (BGP)
connection is interrupted because the status of the BGP peer changes.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 5-7 Indicate the error code contained in the BGP notification returned
during the last BGP connection interruption.
Possible Causes
l Cause 1. The BGP configurations change.
l Cause 2: There is no reachable IP route to the BGP peer.
Procedure
Step 1 Cause 1. The BGP configurations change.
1. Ensure that the BGP configurations are consistent at the local end and the BGP peer.
----End
Related Information
None
A.3.23 BIP_EXC
Description
The BIP_EXC is an alarm indicating that the BIP errors exceed the threshold. This alarm
occurs when the board detects that the number of BIP-2 errors (in byte V5) exceeds the preset
BIP_EXC alarm threshold (10-3 by default).
Attribute
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service
board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio
link along which the E1 service signal travels. If yes, clear the alarm immediately.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the
service signal. If yes, clear the alarm immediately.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the IDU
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the IDU
----End
Related Information
Handle the errors of TDM services.
A.3.24 BIP_SD
Description
The BIP_SD is an alarm indicating that the signal degrades due to the BIP errors. This alarm
occurs when the board detects that the number of BIP-2 errors (in byte V5) is higher than the
preset BIP_SD alarm threshold (10-6 by default) and lower than the preset BIP_EXC alarm
threshold (10-3 by default).
Attribute
Parameters
None
Possible Causes
l Cause 1: The line performance degrades (if the alarm is reported by an E1 service
board).
l Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
l Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
l Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
Procedure
Step 1 Cause 1: The line performance degrades (if the alarm is reported by an E1 service board).
1. Check whether the performance degradation alarm occurs on the STM-1 path or radio
link along which the E1 service signal travels. If yes, clear the alarm immediately.
If... Then...
There is any of the preceding alarms Clear the alarm immediately.
No such alarms occur Ensure that the board is normal.
Step 2 Cause 2: The line performance degrades (if the alarm is reported by a Hybrid IF board).
1. Check whether any alarm occurs on the tributary board or IF board that transmits the
service signal. If yes, clear the alarm immediately.
Step 3 Cause 3: The board is faulty (if the alarm is reported by an E1 service board).
1. Replace the IDU
Step 4 Cause 4: The board is faulty (if the alarm is reported by a Hybrid IF board).
1. Replace the IDU
----End
Related Information
Handle the errors of TDM services.
A.3.25 BOOTROM_BAD
Description
The BOOTROM_BAD is an alarm indicating that the BOOTROM data consistency check
fails. This alarm occurs when the BOOTROM data is damaged during a periodical check by
the system.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2, Parameter 3 Indicates the type of the BOOTROM damage.
l 0x00, 0x01: damage of the basic BIOS
l 0x00, 0x02: damage of the extended BIOS
Parameter 4, Parameter 5 The values are always 0xff 0xff.
l When the NE is already started, the BOOTROM_BAD alarm does not affect the system
and services.
l If the BOOTROM_BAD alarm occurs and a hard reset is performed on a alarmed unit,
the alarmed unit fails to load the BIOS and cannot be started.
Possible Causes
l Cause 1: The basic BIOS is damaged.
l Cause 2: The extended BIOS is damaged.
l Cause 3: The BOOTROM database is damaged.
l Cause 4: The system control and communication unitis faulty.
Procedure
Step 1 Replace the IDU.
----End
Related Information
None
A.3.26 BRDCASTRATIO_OVER
Description
The BRDCASTRATIO_OVER alarm indicates that the ratio of broadcast traffic exceeds the
threshold. This alarm is reported when the ratio of broadcast and multicast packets to all
packets exceeds the specified threshold.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the service flow direction.
l 0x00: receive direction
l 0x01: transmit direction
Possible Causes
l Cause 1: A service loop is formed.
l Cause 2: The broadcast packet suppression threshold is improperly set in IPTV
scenarios.
l Cause 3: The PLA group configurations are deleted from the local NE, but not from the
other NEs in the same PLA group.
Procedure
Step 1 Cause 1: A service loop is formed.
1. Check for and release port self-loops or service loops on the service path.
Step 2 Cause 2: The broadcast packet suppression threshold is improperly set in IPTV scenarios.
1. Re-plan and modify the broadcast packet suppression threshold for IPTV services. For
detailed operations, see Setting the Advanced Attributes of Ethernet Ports.
Step 3 Cause 3: The PLA group configurations are deleted from the local NE, but not from the other
NEs in the same PLA group.
1. Delete PLA group configurations from other NEs in the same PLA group.
----End
Related Information
None
A.3.27 BUS_ERR
Description
The BUS_ERR alarm indicates a bus fault or a data service exception on an NE.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 For a service board or a switching and timing board, Parameter 1 indicates the
bus error type.
l 0x01: BUS_LOS
l 0x02: BUS_OOF
l 0x03: BUS_LOF
l 0x04: BUS_OOA
l 0x05: BUS_RX_DOWN
l 0x06: BUS_TX_DOWN
l 0x07: BUS_SPI_DOWN
l 0x08: BUS_SCI_ERR
l 0x09: BUS_OPP_CLK_LOC
l 0x0a: BUS_SERDS_ERR
l 0x0b: BUS_MII_ERR
l 0x0c: BUS_HW_ERR
l 0x0d: BUS_FE_ERR
l 0x0e: BUS_EMIF_ERR
l 0x0f: BUS_IIC_ERR
l 0x10: BUS_GE_LINK_ERR
l 0x11: BUS_EMIF
For a system control board, Parameter 1 has a fixed value of 0x32.
For an IF board, meanings of Parameter 1 are as follows:
l 0x00: Bus signals from the analog to digital converter (ADC) to the
modem are abnormal in the downlink direction.
l 0x01: Bus signals from the ADC to the modem are abnormal in the uplink
direction.
l 0x02: Bus signals from the modem to the ADC are abnormal in the
downlink direction.
l 0x03: IF signals from the backplane are abnormal.
l 0x04: The phase-locked loop (PLL) on a data service serial interface is out
of lock.
l 0x05: Decapsulation of data services is abnormal in the downlink
direction.
l 0x06: Communication between the master and slave boards in a PLA
group is abnormal.
l 0x07: The packet segment sequence numbers of the master and slave PLA
boards do not match.
l 0x08: Services on a PLA member is abnormal.
Name Meaning
Parameter 2, For a service board, Parameter 2 and Parameter 3 indicate the ID of the faulty
Parameter 3 bus.
For a system control board, Parameter 2 and Parameter 3 indicate that the
TELECOM or LVDS bus is faulty.
For an IF board, when Parameter 1 is 0x08, Parameter 2 and Parameter 3
indicate the ID of the PLA member port on which services are abnormal.
Possible Causes
The possible causes of the BUS_ERR alarm are as follows:
l Cause 1: Service configurations or basic configurations (such as the number of E1
services) on an IF board are incorrect.
l Cause 2: The NE is faulty.
Procedure
Step 1 Cause 1: Service configurations or basic configurations (such as the number of E1 services)
on an IF board are incorrect.
1. Check whether service configurations or basic configurations on IF boards are correct
(For example, check for the A.3.203 MW_CFG_MISMATCH alarm on IF boards). If
any alarms indicating incorrect service configurations or basic configurations are
reported, clear them.
2. Check whether the BUS_ERR alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The NE is faulty.
1. Replace the alarmed IDU.
Check whether the BUS_ERR alarm is cleared. If the BUS_ERR alarm persists, contact
Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.28 CES_ACR_LOCK_ABN
Description
The CES_ACR_LOCK_ABN is an alarm indicating that the locking function of CES ACR
service clock is abnormal.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
Name Meaning
Parameter 1 to Indicate the index of PW that carries the services associated with
Parameter 4 the ACR clock source.
Possible Causes
l Cause 1: CES ACR services are unavailable or have alarms.
l Cause 2: The network is unstable.
l Cause 3: NEs on the service path are abnormal.
Procedure
Step 1 Cause 1: CES ACR services are unavailable or have alarms.
1. Query the CES services associated with the ACR clock source. For details, see
Configuring the Primary Clock for an ACR Clock Domain.
2. Check whether these services have alarms. For details, see 4.3.1 Browsing Current
Alarms.
Step 2 Cause 2: The network is unstable.
1. Check for jitters and delays on the network. Query service performance statistics. For
details, see 4.3.3 Browsing Current Performance Events.
2. Analyze service performance statistics. If the network is unstable, rectify the faults on
the network, or switch the affected services to a stable network.
Step 3 Cause 3: NEs on the service path are abnormal.
1. Query alarms reported by the NEs on the service path. For details, see 4.3.1 Browsing
Current Alarms.
2. Handle the alarms. For details, see A.3 Alarms and Handling Procedures.
----End
Related Information
None
A.3.29 CES_JTROVR_EXC
Description
The CES_JTROVR_EXC is an alarm indicating that the number of jitter buffer overflows
crosses the specified threshold. This alarm occurs when the board detects that, the number of
jitter buffer overflows per second crosses the specified threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The size of buffer area is set to a low value.
l Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
Procedure
Step 1 Cause 1: The size of buffer area is set to a low value.
1. Query the size of buffer area. For details, see Querying CES Service Information.
2. Determine whether the size can be increased according to network planning. If yes,
change the size to a greater value. For details, see Managing CES Services.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
1. Synchronize the PSN network clock by setting clock synchronization, reducing
transmission nodes, and optimizing transmission routes.
----End
Related Information
None
A.3.30 CES_JTRUDR_EXC
Description
The CES_JTRUDR_EXC is an alarm indicating that the number of jitter buffer underflows
crosses the specified threshold. This alarm occurs when the board detects that, within a period
(10s), the number of jitter buffer underflows per second crosses the specified threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
l Cause 3: The link is looped.
l Cause 4: The link is congested.
l Cause 5: The size of buffer area is set to a low value.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Cause 2: The PSN network clocks used for the transmission of CES services are not
synchronized.
1. Synchronize the PSN network clock by setting clock synchronization, reducing
transmission nodes, and optimizing transmission routes.
Step 3 Cause 3: The link is looped.
1. Release the loop.
Step 4 Cause 4: The link is congested.
1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth
or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
A.3.31 CES_LOSPKT_EXC
Description
The CES_LOSPKT_EXC is an alarm indicating that the number of lost packets of CES
services crosses the threshold in a time unit. This alarm occurs when the board detects that the
number of lost packets per second crosses the specified threshold.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The link is looped.
l Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Cause 2: The link is looped.
1. Release the loop.
Step 3 Cause 3: The link is congested.
1. Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth
or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
Packets are lost when the sequence numbers of received packets are greater than expected.
A.3.32 CES_MALPKT_EXC
Description
The CES_MALPKT_EXC is an alarm indicating that, in a time unit, the number of deformed
frames in CES services crosses the threshold. This alarm occurs when the board detects that
the number of deformed frames in CES services crosses the specified threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: The RTP head enabling status is different between the two ends of the PW.
l Cause 2: Bit errors occur on the link.
Procedure
Step 1 Cause 1: The RTP head enabling status is different between the two ends of the PW.
1. Set the RTP head enabling status to the same on the two ends of the PW. For details, see
Modifying CES Service Parameters.
----End
Related Information
If a CESoPSN frame contains valid TDM data and does not contain any error indication, but
the size of the CESoPSN frame is not consistent with the specified size, a deformed
CESoPSN frame is generated.
A.3.33 CES_MISORDERPKT_EXC
Description
The CES_MISORDERPKT_EXC is an alarm indicating that, in a unit time, the number of
lost disordered packets crosses the specified threshold. This alarm occurs when the board
detects that the number of lost disordered packets per second crosses the specified threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The link is looped.
l Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. See 5.3 Troubleshooting the Radio Link.
----End
Related Information
Packets are disordered when the sequence numbers of received packets are smaller than
expected.
A.3.34 CES_RDI
Description
The CES_RDI is an alarm of remote defect indication. When the CES_LOSPKT_EXC alarm
is reported at the remote end, the remote end sets the R bit in control word to 1. Upon
receiving a packet in which the R bit is 1, the local end reports the CES_RDI alarm.
Attribute
Parameters
None
Possible Causes
l Cause 1: Signals degrade on the link.
l Cause 2: The link is looped.
l Cause 3: The link is congested.
Procedure
Step 1 Cause 1: Signals degrade on the link.
1. See 5.3 Troubleshooting the Radio Link.
----End
Related Information
None
A.3.35 CES_STRAYPKT_EXC
Description
The CES_STRAYPKT_EXC is an alarm indicating that, in a time unit, the number of error
packets in CES services crosses the threshold. This alarm occurs when the board detects that
the number of error packets in CES services per second crosses the specified threshold.
Attribute
Parameters
None
Possible Causes
Cause 1: Links are misconnected.
Procedure
Step 1 Cause 1: Links are misconnected.
1. Check the link configuration and rectify the fault.
----End
Related Information
Incorrect packets are received when the tracing source field in the RTP head is different from
expected.
A.3.36 CESPW_OPPOSITE_ACFAULT
Description
The CESPW_OPPOSITE_ACFAULT is an alarm indicating that the AC circuit on the remote
NE is faulty. On detection of an AC circuit fault, the remote NE sets the L bit in the control
word to 1. When receiving a packet in which the L bit is 1, the local NE reports the
CESPW_OPPOSITE_ACFAULT alarm.
Attribute
Parameters
None
Possible Causes
Cause 1: The remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS, R_LOF, or
MS_AIS alarm.
Procedure
Step 1 Check whether the remote NE reports the T_ALOS, UP_E1_AIS, LFA, LMFA, R_LOS,
R_LOF, or MS_AIS alarm.
1. If yes, handle these alarms.
----End
Related Information
None
A.3.37 CESPW_OPPOSITE_RAI
Description
The CESPW_OPPOSITE_RAI is a remote alarm indication. On detection of the RAI alarm,
the remote NE sets the L bit of the control word to 0 and the M field of the control word to
10. When receiving the packet in which the L bit is 0 and the M field is 10, the local NE
reports the CESPW_OPPOSITE_RAI alarm.
Attribute
Parameters
None
Possible Causes
Cause 1: The remote NE detects the RAI alarm.
Procedure
Step 1 Cause 1: The remote NE detects the RAI alarm.
1. Clear the ALM_E1RAI alarm on the remote NE.
----End
Related Information
None
A.3.38 CLK_LOCK_FAIL
Description
The CLK_LOCK_FAIL is an alarm indicating a clock locking failure.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: Frequency deviation of the clock source has crossed the upper threshold in
physical synchronization mode.
l Cause 2: The physical link where the clock source resides is faulty in physical
synchronization mode.
Procedure
Step 1 Cause 1: Frequency deviation of the clock source has crossed the upper threshold in physical
synchronization mode.
1. Check whether high-level bit error alarms or performance events have been reported on
the NMS. If yes, handle them immediately.
2. If there is an external clock source, check whether its clock signals are normal. If no,
replace the external clock source. For details, see Configuring the Clock Sources.
3. Check whether clock configurations are correct. For example, if the input and output
modes of the external clock source do not match each other, modify the configurations.
For details, see Modifying the Parameters of the Clock Output.
Step 2 Cause 2: The physical link where the clock source resides is faulty in physical
synchronization mode.
1. If there is an external clock source, check whether the NE reports the SYNC_C_LOS
alarm. If yes, clear the alarm immediately.
2. If the CLK_LOCK_FAIL alarm persists, 6.1 Replace the IDU.
----End
Related Information
None
A.3.39 CLK_NO_TRACE_MODE
Description
The CLK_NO_TRACE_MODE alarm indicates that a clock source is not in locked mode.
This alarm is reported when the current clock does not trace any clock sources.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the clock mode.
l 0x02: free-run
Possible Causes
l Cause 1: The system clock source priority table is not configured.
l Cause 2: All the clock sources in the clock source priority table fail.
Procedure
Step 1 Cause 1: The system clock source priority table is not configured.
1. Configure the system clock source priority table. For details, see Configuring the Clock
Sources.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. If any clock source is lost, check for the SYNC_C_LOS alarm and clear it, if any.
2. If the SSM protocol is enabled on the local NE but is disabled on its upstream NE,
enable the SSM protocol for its upstream NE.
----End
Related Information
None
A.3.40 COMMUN_FAIL
Description
The COMMUN_FAIL is an alarm indicating the inter-board communication failure. This
alarm is reported when the communication between functional units and the system control
unit is interrupted.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the port. The value is always 0x01.
Name Meaning
Parameter 2, Indicates the ID of the path on which the alarm is generated.
Parameter 3 Parameter 2 is always 0x00. Parameter 3 has the following
meanings:
0x03: inter-board Ethernet communication
Parameter 4,
Parameters 4 and 5 are reserved, and their values are always 0xFF.
Parameter 5
Possible Causes
l Cause 1: The alarmed NE is reset.
l Cause 2: The alarmed NE is faulty.
Procedure
Step 1 Cause 1: The alarmed NE is reset.
1. After the NE resetting is complete, the alarm clears automatically.
----End
Related Information
None
A.3.41 COMPRESS_MISMATCH
Description
The COMPRESS_MISMATCH alarm indicates a mismatch of header compression.
Attribute
Parameters
Name Meaning
Parameters 1 and 2 Indicate an interface ID.
Parameter 3 Takes the fixed value of 0x01 and indicates that a compressed frame
received by equipment cannot be identified.
Possible Causes
Cause: Negotiation on frame header compression between NEs at both ends fails.
Procedure
Step 1 Disable and re-enable frame header compression for the peer NE according to the Configuring
Ethernet Header Compression and Error Frame Discarding Over Air Interfaces.
----End
Related Information
None
A.3.42 COM_EXTECC_FULL
Description
The COM_EXTECC_FULL is an alarm indicating an excessive number of TCP connections
between automatically extended ECC NEs.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 5 The value is always 0x00.
Possible Causes
The number of TCP connections between automatically extended ECC NEs is larger than
four.
Procedure
Step 1 Set ECC Extended Mode to Specified mode by referring to Configuring Extended ECC
Communication.
----End
Related Information
None
A.3.43 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 specified parameters do not meet the
requirements of the ODU.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates that the configuration data does not meet the requirements.
l 0x01: The frequency is set incorrectly.
l 0x02: The T/R spacing is set incorrectly.
l 0x03: The transmit power is set incorrectly.
l 0x04: The ATPC threshold is set incorrectly.
l 0x05: The bandwidth is set incorrectly.
l 0x06: The modulation mode is set incorrectly.
Possible Causes
l Cause 1: The type and configuration parameters of the ODU do not match the
requirements.
l Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only
when Parameter 1 is 0x03.)
NOTE
Perform the handling procedure of Cause 2 if the following conditions are met: The AM function is
enabled on the radio link; the transmit power configured for the ODU is lower than the maximum rated
power in AM guaranteed capacity mode.
Procedure
Step 1 Cause 1: The type and configuration parameters of the ODU do not match the requirements.
1. Determine the parameter that does not meet the requirement according to the alarm
parameter. Then, handle the fault accordingly.
If... Then...
The alarm parameter takes a value from 0x01 Perform the operation described in
to 0x03 Step 1.2.
The alarm parameter takes a value from 0x04 Perform the operation described in
to 0x06 Step 1.3.
2. Check whether the parameters of the ODU interface meet the requirements of network
planning. For details, see Configuring a Single-Hop Radio Link.
If... Then...
The parameters meet the requirements of Use the ODU of the proper model.
network planning
If... Then...
The parameters do not meet the requirements Modify the ODU interface
of network planning parameters.
3. Check whether the parameters of the IF interface meet the requirements of network
planning. For details, see Configuring a Single-Hop Radio Link.
If... Then...
The parameters meet the requirements Replace the IF board.
of network planning
The parameters do not meet the Modify the IF interface parameters. For
requirements of network planning details, see Configuring a Single-Hop
Radio Link.
Step 2 Cause 2: The AM parameters are incorrectly changed. (This cause can be verified only when
Parameter 1 is 0x03.)
1. Verify that the alarm is caused by incorrect change of AM parameters.
Perform the handling procedure of Cause 2 if the following conditions are met:
If... Then...
The conditions are met and the transmit Perform a cold reset for the alarmed
power needs to be changed ODU.
The conditions are met but the transmit Change the parameters of ODU
power does not need to be changed interfaces to recover the original value
of transmit power.
----End
Related Information
None
A.3.44 DBMS_DELETE
Description
The DBMS_DELETE alarm indicates that a database is being deleted. This alarm is reported
when a user runs a command to delete the database and the NE is in Deleting Database state.
Attribute
Parameters
None
Possible Causes
l Cause 1: A database is deleted.
Procedure
Step 1 Follow instructions in 7.4 Restoring the Database by NMS to restore the database.
----End
Related Information
None
A.3.45 DBMS_ERROR
Description
The DBMS_ERROR is an alarm indicating that errors occur in the processing of the system
database.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the error code.
l 0x00: The NE is running properly.
l 0x01: The database is being checked.
l 0x02: The database is undergoing a periodical backup.
l 0x04: The system is faulty.
l 0x08: Data on the active system control unit and that on the standby
system control unit are inconsistent.
l 0x10: Incremental data fails to be backed up.
l 0x20: Incremental data fails to be backed up to the NVRAM.
l 0x40: Incremental data fails to be backed up to the flash memory.
Name Meaning
Parameter 2 Indicates the storage area of the database.
l 0x00: OFS1
l 0x01: OFS2
l 0x02: DRDB storage area
l 0x03: MDB storage area
l 0x04: TDRDB storage area
l 0x05: CF storage area
l 0x06: shared storage area
l 0x0C: NVRAM storage area
Parameter 4,
Reserved fields
Parameter 5
Possible Causes
Cause: The database processing fails or the database is damaged.
Procedure
Step 1 Obtain NE backup data (backed up periodically by the U2000 or backed up manually) or NE
service configuration information.
Step 2 Contact Huawei technical support engineers for handling the alarm.
Step 3 In case of emergency, 6.1 Replace the IDU and restore the database or reconfigure service
data.
----End
Related Information
None
A.3.46 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
Possible Causes
Cause 1: The database enters the protection mode due to frequent resets of the NE software.
Procedure
Step 1 Cause 1: The database enters the protection mode due to frequent resets of the NE software.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.47 DCNLINK_OVER
Description
The DCNLINK_OVER alarm indicates that the number of links on a DCN exceeds the
recommended value.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: The total number of OSPF neighbors on the DCN exceeds the
recommended value.
l 0x02: The total number of OSPF neighbors to the same peer NE on the
DCN exceeds the recommended value.
Possible Causes
l Cause 1: The total number of OSPF neighbors on the DCN exceeds the recommended
value.
l Cause 2: The total number of OSPF neighbors to the same peer NE on the DCN exceeds
the recommended value.
Procedure
Step 1 Disable unnecessary DCN channels on NEs to ensure that the total number of OSPF
neighbors on the DCN and the total number of OSPF neighbors to the same peer NE are
within the recommended ranges.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei technical support
engineers to handle the alarm.
----End
Related Information
None
A.3.48 DCNSIZE_OVER
Description
The DCNSIZE_OVER is an alarm indicating an over-sized DCN network.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter If these parameters are 0xFF 0xFF, the NE works in L2DCN mode.
2 Otherwise, these parameters indicate the current size of the DCN
subnet.
Possible Causes
Cause 1: The number of NEs on an L3 DCN subnet exceeds 400.
Procedure
Step 1 Replan the DCN network based on actual networking conditions.
----End
A.3.49 DDN_LFA
Description
The DDN_LFA is an alarm indicating loss of basic frame alignment for framed E1 services.
This alarm occurs when DDN (digital data network) side fails to receive the basic frame
alignment signal for framed E1 services.
Attribute
Parameters
None
Possible Causes
l Cause 1: The interconnected user equipment is faulty.
l Cause 2: The service frame format is configured incorrectly.
l Cause 3: The alarmed NE has hardware faults.
Procedure
Step 1 Cause 1: The interconnected user equipment is faulty.
1. Troubleshoot the interconnected user equipment.
NOTICE
If the service on the alarmed NE is not protected, a cold reset on the board causes service
interruptions.
----End
Related Information
Basic frame
As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence
(FAS) or an odd frame with non frame alignment sequence (NFAS).
A.3.50 DOWN_E1_AIS
Description
The DOWN_E1_AIS is an alarm of the 2 Mbit/s downlink signal. This alarm occurs when the
tributary unit detects the 2 Mbit/s downlink signal of all 1s.
Attribute
Parameters
None
Possible Causes
l Cause 1: The opposite NE transmits the E1_AIS alarm.
l Cause 2: An upstream alarm triggers this alarm.
l Cause 3: On the local NE, the receive unit of the tributary board or the system control
and cross-connect unit is faulty.
Procedure
Step 1 Cause 1: The opposite NE transmits the E1_AIS alarm.
1. Check whether the opposite NE reports the UP_E1_AIS or T_ALOS alarm.
If... Then...
The opposite NE reports the UP_E1_AIS or Clear the alarm immediately.
T_ALOS alarm
The opposite NE does not report the Ensure that the unit on the local NE is
UP_E1_AIS or T_ALOS alarm normal.
Step 3 Cause 3: On the local NE, the receive unit of the tributary unit or the system control and
cross-connect unit is faulty.
1. If the alarm persists, replace the IDU.
----End
Related Information
None
A.3.51 DROPRATIO_OVER
Description
The DROPRATIO_OVER alarm indicates that the number of lost packets crosses the
threshold when queue congestion occurs at a port. This alarm is reported when the ratio of lost
packets on an object under performance monitoring is higher than the expected ratio.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the direction in which traffic crosses the threshold.
l 0x00: The ratio of lost packets in the receive direction exceeds the
threshold.
l 0x01: The ratio of lost packets in the transmit direction exceeds the
threshold.
Possible Causes
l Cause 1: Service configuration is incorrect.
l Cause 2: Actual traffic exceeds the configured port bandwidth or committed information
rate (CIR).
Procedure
Step 1 Cause 1: Service configuration is incorrect.
1. Check and reconfigure services according to the network plan.
Step 2 Cause 2: Actual traffic exceeds the configured port bandwidth or CIR.
1. 4.6.2 Querying Traffic, Physical Bandwidth, or Bandwidth Utilization. If traffic is
large, check whether a network storm has occurred, and eliminate the source that
illegally sends a large amount of data.
2. If the port bandwidth is too low, follow instructions in Modifying the Port Policy to
increase port bandwidth or expand the network.
----End
Related Information
If packet loss is indicated in the receive direction, check the method of handling red packets in
the traffic classification configuration. If the method of handling red packets is non-discard,
packets may not be actually lost in the receive direction.
A.3.52 E1_LOC
Description
The E1_LOC is an alarm indicating that the uplink 2M clock is lost. This alarm occurs when
the tributary board fails to extract the clock from the E1 signal.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The opposite NE is faulty.
l Cause 2: The wiring sequence of the cable is incorrect.
l Cause 3: The receive unit of the tributary board on the local NE is faulty.
l Cause 4: The input E1 signal has an abnormal waveform.
Procedure
Step 1 Cause 1: The opposite NE is faulty.
1. Rectify the fault on the opposite NE.
Step 2 Cause 2: The wiring sequence of the cable is incorrect.
1. Redo the cable.
Step 3 Cause 3: The receive unit of the tributary board on the local NE is faulty.
1. Replace the board where the line unit is located.
Step 4 Cause 4: The input E1 signal has an abnormal waveform.
1. Check whether any external interference causes the abnormal waveform of the E1 signal.
If... Then...
There is the external interference The fault is rectified. End the alarm handling.
There is no external interference Contact Huawei engineers.
----End
Related Information
None
A.3.53 E1_LOS
Description
The E1_LOS is an alarm indicating the loss of the E1 signal. This alarm occurs when the
tributary board detects the uplink E1 signal of all 0s.
Attribute
Parameters
None
Possible Causes
l Cause 1: The cable is not connected or the cable is faulty.
l Cause 2: The opposite NE is faulty.
l Cause 3: The tributary board on the local NE is faulty.
Procedure
Step 1 Cause 1: The cable is not connected or the cable is faulty.
1. Check whether the cable is connected properly.
If... Then...
The cable is not connected properly Connect the cable properly.
The cable is prepared incorrectly Redo the cable.
----End
Related Information
None
A.3.54 ELAN_SMAC_FLAPPING
Description
The ELAN_SMAC_FLAPPING alarm indicates that the source MAC address learned by a
bridge-based or PW-carried E-LAN service flaps. This alarm is reported when two ports that
carry a bridge-based or PW-carried E-LAN service learn the same source MAC address.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 6 Indicate the source MAC address that flaps.
Parameter 9 Indicate the type of the port that learns the source MAC address
before the flapping occurs.
l 0x02: UNI
l 0x03: NNI
Possible Causes
Cause: A loop exists on a UNI or NNI that carries the E-LAN service.
Procedure
Step 1 Determine the E-LAN service according to the service ID on the NMS.
Step 2 Check the E-LAN service path by referring to instructions in Detecting an E-LAN Service
Loop.
----End
Related Information
None
A.3.55 ENVHUM_SENSOR_FAIL
Description
The ENVHUM_SENSOR_FAIL is an alarm indicating that the ambient humidity sensor of
the cabinet fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The ambient humidity sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The ambient humidity sensor is not installed.
Procedure
Step 1 Cause 1: The ambient humidity sensor is faulty.
1. Replace the ambient humidity sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
If... Then...
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.56 ENVTEMP_SENSOR_FAIL
Description
The ENVTEMP_SENSOR_FAIL is an alarm indicating that the ambient temperature sensor
of the cabinet fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The ambient temperature sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The ambient temperature sensor is not installed.
Procedure
Step 1 Cause 1: The ambient temperature sensor is faulty.
1. Replace the ambient temperature sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.57 ENVTEMP1_SENSOR_FAIL
Description
The ENVTEMP1_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 1 of
the cabinet fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: Ambient temperature sensor 1 is faulty.
Procedure
Step 1 Cause 1: Ambient temperature sensor 1 is faulty.
1. Replace ambient temperature sensor 1.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.58 ENVTEMP2_SENSOR_FAIL
Description
The ENVTEMP2_SENSOR_FAIL is an alarm indicating that ambient temperature sensor 2 of
the cabinet fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: Ambient temperature sensor 2 is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: Ambient temperature sensor 2 is not installed.
Procedure
Step 1 Cause 1: Ambient temperature sensor 2 is faulty.
1. Replace ambient temperature sensor 2.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.59 ERPS_IN_PROTECTION
Description
ERPS_IN_PROTECTION indicates that EPRS ring is in protection mode.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 3 DIR, indicating whether the faulty node is in the east or west
direction of the ERPS RPL-OWNER node.
l 0x01: east
l 0x00: west
Parameter 4 - Parameter 9 NODE ID, indicating the MAC address of the faulty node.
Possible Causes
Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS
ring.
Procedure
Step 1 Cause 1: This alarm is reported when EPRS switching is triggered by a fault on the ERPS
ring.
1. Locate the faulty node on the ERPS ring based on the alarm parameters.
2. Locate the ERPS blocked port on the faulty node.
3. Rectify the fault.
----End
Related Information
This alarm is not reported on an ERPS V2 network where virtual channels are disabled.
A.3.60 ETH_APS_LOST
Description
The ETH_APS_LOST is an alarm indicating that the APS frame is lost. This alarm is reported
when an ingress/egress node of a bidirectional tunnel does not receive any APS frames from
the protection channel.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: The opposite NE is not configured with the APS protection.
l Cause 2: The APS protection group is deactivated.
l Cause 3: The settings of the APS protection group differ between the two ends.
l Cause 4: The service on the protection channel is interrupted.
Procedure
Step 1 Cause 1: The opposite NE is not configured with the APS protection.
1. On the NMS, check whether the opposite NE is configured with the APS protection. For
details, see Querying MPLS APS Status.
If... Then...
The opposite NE is not configured with the APS protection Go to the next step.
The opposite NE is configured with the APS protection Go to Cause 2.
2. Create a matching APS protection group on the opposite NE, and activate the APS
protocol. Check whether the alarm clears.
3. If the alarm persists, proceed to cause 4.
If... Then...
The APS protocol is deactivated at one end Activate the APS protocol at the end.
The APS protocol is activated at both ends Go to Cause 3.
2. Check whether the alarm clears. If the alarm persists, go to Cause 3.
Step 3 Cause 3: The settings of the APS protection group differ between the two ends.
1. On the NMS, check whether the settings of the APS protection group are the same at the
two ends. If the settings differ between the two ends, change them to the same. Then,
deactivate and activate the APS protection group at the two ends.
2. Check whether the alarm clears. If the alarm persists, go to Cause 4.
----End
Related Information
None
A.3.61 ETH_APS_PATH_MISMATCH
Description
The ETH_APS_PATH_MISMATCH is an alarm indicating that the working and protection
paths of the APS protection group differ between the two ends. This alarm is reported when
the working and protection paths of one APS protection group at one end are different from
those at the other end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The configured working and protection paths differ between the two ends.
l Cause 2: The physical link is connected incorrectly.
Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
1. Check whether the APS settings at the two ends are the same. For details, see Querying
MPLS APS Status.
2. If the APS settings are different, change the settings to the same. Then, deactivate and
activate the APS protection group at the two ends. Then, check whether the alarm clears.
3. If the alarm persists, go to Cause 2.
----End
Related Information
None
A.3.62 ETH_APS_SWITCH_FAIL
Description
The ETH_APS_SWITCH_FAIL is an alarm of a protection switching failure. This alarm is
reported when the request signal in the transmitted Automatic Protection Switching (APS)
frame is different from the bridge signal in the received APS frame and this symptom lasts for
50 ms.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: The settings of the APS protection group differ between the two ends.Cause 2: APS
fails due to other reasons.
Procedure
Step 1 Cause 1: The settings of the APS protection group differ between the two ends.
1. Change the settings to the same. For details, see Creating an MPLS APS Protection
Group. Then, deactivate and activate the APS protection group at the two ends.
Step 2 Cause 2: APS fails due to other reasons.
1. Reactivate APS protection at both ends.
----End
Related Information
None
A.3.63 ETH_APS_TYPE_MISMATCH
Description
The ETH_APS_TYPE_MISMATCH is an alarm of protection scheme mismatch. This alarm
is reported when the information in the received Automatic Protection Switching (APS) frame
is different from the APS settings at the local end.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the specific difference.
l 0x01: Indicates that the switching type is different.
l 0x02: Indicates that the switching direction is different.
l 0x03: Indicates that the revertive mode is different.
Possible Causes
l Cause 1: The switching type is different.
l Cause 2: The switching direction is different.
l Cause 3: The revertive mode is different.
Procedure
Step 1 Determine the possible cause of the alarm according to the alarm parameters.
1. Change the settings of the APS protection group to the same at the two ends. For details,
see Querying MPLS APS Status. Then, deactivate and activate the APS protection group
at the two ends.
----End
Related Information
None
A.3.64 ETH_AUTO_LINK_DOWN
Description
The ETH_AUTO_LINK_DOWN alarm indicates that an Ethernet port is automatically
switched to the link down state upon a fault detected by link-state pass through (LPT).
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: The radio link connected to the alarmed port is faulty.
l Cause 2: The opposite service access port is faulty.
Procedure
Step 1 Cause 1: The radio link connected to the alarmed port is faulty.
1. Check for MW_LIM, MW_LOF, and MW_RDI alarms on the local and opposite
microwave ports, and clear them if any. Then, check whether the
ETH_AUTO_LINK_DOWN alarm is cleared.
Step 2 Cause 2: The opposite service access port is faulty.
1. Check for ETH_LOS alarm, and optical-module-related alarms on the opposite port, and
clear them if any.
----End
Related Information
None
A.3.65 ETH_CFM_AIS
Description
The ETH_CFM_AIS is an alarm indicating that an AIS packet is received by the local MEP.
This alarm is reported when the system receives an AIS packet, which indicates that the
Ethernet server layer is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicate the ID of the port that reports the alarm.
(port)
Parameters 5 and 6 Indicate the VLAN ID of the MEP.
(VLAN ID)
Parameter 7 Indicate the direction of the local MEP.
(direction) l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (level) Indicates the maintenance domain (MD) level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the customer, provider indicates the supplier, and operator
indicates the carrier.
Possible Causes
Cause 1: The upstream NE detects a fault at the Ethernet server layer.
Procedure
Step 1 Check whether there is any defect in the Ethernet server layer between source and sink NE.
----End
Related Information
None
A.3.66 ETH_CFM_LOC
Description
The ETH_CFM_LOC is an alarm indicating the loss of connectivity. This alarm occurs when
the system fails to receive the CCM packet from the remote MEP in 3.5 connectivity check
(CC) periods successively.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicates the ID of the alarmed port.
(port)
Parameters 5 and 6 Indicates the VLAN ID of the MEP.
(VLAN ID)
Name Meaning
Parameter 7 Indicates the direction of the local MEP.
(direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (level) Indicates the MD level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the user, provider indicates the supplier, and operator
indicates the carrier.
Possible Causes
l Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
l Cause 2: The Ethernet service in the maintenance association (MA) to which the local
MEP belongs is faulty.
l Cause 3: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The line between the local standard MEP and the remote standard MEP is
interrupted.
1. Check whether the physical links (such as network cables and fibers) between the
standard MEPs are connected properly.
If... Then...
The physical links are connected improperly Connect the physical links properly.
The physical links are connected properly Go to Cause 2.
Step 2 Cause 2: The Ethernet service in the maintenance association (MA) to which the local MEP
belongs is faulty.
1. Check whether Ethernet service in the maintenance association (MA) to which the local
MEP belongs is configured correctly.
If... Then...
The service is configured Modify the configuration of the service to ensure
incorrectly consistency at two ends.
The service is configured Go to Cause 3.
correctly
----End
Related Information
None
A.3.67 ETH_CFM_MISMERGE
Description
The ETH_CFM_MISMERGE is an alarm indicating an incorrect connection. This alarm
occurs when the system receives the CCM packet whose MA mismatches or whose priority is
lower.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicates the ID of the alarmed port.
(port)
Parameters 5 and 6 Indicates the VLAN ID of the MEP.
(VLAN ID)
Name Meaning
Parameter 7 Indicates the direction of the local MEP.
(direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (level) Indicates the MD level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the user, provider indicates the supplier, and operator
indicates the carrier.
Possible Causes
l Cause 1: The names of the maintenance domain and the maintenance alliance that the
standard MEPs correspond to are inconsistent.
l Cause 2: The levels of the maintenance domains that the standard MEPs correspond to
are different.
l Cause 3: The physical connection is incorrect.
Procedure
Step 1 Cause 1: The names of the maintenance domain and the maintenance alliance that the
standard MEPs correspond to are inconsistent.
1. Check whether the names of the maintenance domain and the maintenance alliance that
the standard MEPs correspond to are consistent.
If... Then...
The names are inconsistent Set the other names of maintenance domain and
maintenance alliance to ensure consistency at both ends.
The names are consistent Go to Cause 2.
Step 2 Cause 2: The levels of the maintenance domains that the standard MEPs correspond to are
different.
1. Check whether the MD levels of the standard MEPs are the same.
If... Then...
The levels are different Set the MD levels again to ensure consistency at both ends.
The levels are the same Go to Cause 3.
----End
Related Information
None
A.3.68 ETH_CFM_RDI
Description
The ETH_CFM_RDI is an alarm indicating the CCM packet with RDI received from the
remote MEP. This alarm occurs when the system receives the CCM packet with RDI from the
remote maintenance end point (MEP).
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicates the ID of the alarmed port.
(port)
Parameters 5 and 6 Indicates the VLAN ID of the MEP.
(VLAN ID)
Parameter 7 Indicates the direction of the local MEP.
(direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Name Meaning
Parameter 8 (level) Indicates the MD level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the user, provider indicates the supplier, and operator
indicates the carrier.
Possible Causes
l Cause 1: The remote MEP fails to receive the correct CCM packet.
Procedure
Step 1 Cause 1: The remote MEP fails to receive the correct CCM packet.
1. Determine the alarmed port according to the alarm parameter.
2. Check whether the remote MEP that is connected to the port reports the
ETH_CFM_MISMERGE, ETH_CFM_UNEXPERI, or ETH_CFM_LOC alarm.
----End
Related Information
None
A.3.69 ETH_CFM_UNEXPERI
Description
The ETH_CFM_UNEXPERI is an alarm indicating the errored frame. This alarm occurs
when the system receives invalid CCM packets.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicates the ID of the alarmed port.
(port)
Parameters 5 and 6 Indicates the VLAN ID of the MEP.
(VLAN ID)
Parameter 7 Indicates the direction of the local MEP.
(direction) l 0x00: The port is direction insensitive.
l 0x01: The port is in the ingress direction.
l 0x02: The port is in the egress direction.
Parameter 8 (level) Indicates the MD level of the local MEP.
l 0x00: operator MEP level (low)
l 0x01: operator MEP level (medium)
l 0x02: operator MEP level (high)
l 0x03: provider MEP level (low)
l 0x04: provider MEP level (high)
l 0x05: consumer MEP level (low)
l 0x06: consumer MEP level (medium)
l 0x07: consumer MEP level (high)
NOTE
Consumer indicates the user, provider indicates the supplier, and operator
indicates the carrier.
Possible Causes
l Cause 1: No remote MEP is configured.
l Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.
l Cause 3: The service is looped back and the looped packet is received.
Procedure
Step 1 Cause 1: No remote MEP is configured.
1. Check whether the remote MEP is configured. If not, configure the remote MEP first.
Step 2 Cause 2: The configuration of the MEPs at both ends is inconsistent. For example, the
connectivity check (CC) periods are different, and the IDs of the MEPs are in conflict.
1. Check whether the CC periods set at the MEPs are the same.
If... Then...
The CC periods are different Change the CC periods to ensure consistency at both
ends.
The CC periods are the same Go to the next step.
2. Check whether the IDs of the MEPs in the maintenance domain are in conflict.
If... Then...
The IDs are in conflict Change the conflicting IDs.
The IDs are not in conflict Go to Cause 3.
Step 3 Cause 3: The service is looped back and the looped packet is received.
1. Check whether any loop exists at each IP port of the service trail. If yes, release the loop
and clear the alarm.
----End
Related Information
None
A.3.70 ETH_EFM_DF
Description
The ETH_EFM_DF is an alarm indicating negotiation failure. This alarm occurs when the
point-to-point OAM protocol negotiation fails at the Ethernet 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the reason why the negotiation fails.
Possible Causes
l Cause 1: The physical port of the local end is faulty.
l Cause 2: The point to point OAM protocol is not enabled at the opposite end.
l Cause 3: The OAM configuration at both ends is inconsistent.
Procedure
Step 1 Cause 1: The physical port of the local end is faulty.
1. Check whether the physical port is faulty. If yes, replace the board where the Ethernet
port is located.
Step 2 Cause 2: The point to point OAM protocol is not enabled at the opposite end.
1. Enable the point to point OAM protocol at the opposite end.
----End
Related Information
None
A.3.71 ETH_EFM_EVENT
Description
The ETH_EFM_EVENT is an alarm indicating the performance event reported on the
opposite NE. This alarm occurs when the local end receives the link error indication packet
(OAMPDUM) from the opposite end.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the link event.
l 0x01: errored symbol period.
l 0x02: errored frame.
l 0x03: errored frame period.
l 0x04: errored frame seconds summary.
Possible Causes
l Cause 1: The physical port at the local end is faulty.
l Cause 2: The equipment at the opposite end is faulty.
l Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet optical
port).
l Cause 4: The line performance deteriorates (the alarm is reported by an Ethernet
electrical port).
Procedure
Step 1 Cause 1: The physical port at the local end is faulty.
1. Check whether the physical port is faulty. If yes, 6.1 Replace the IDU.
Step 3 Cause 3: The line performance deteriorates (the alarm is reported by an Ethernet optical port).
1. Check whether the transmit power at the opposite site and the receive power at the local
site meet the specifications of the optical ports. For details, see Browsing Current
Performance Events.
If... Then...
The transmit power at the opposite site is too low Replace the optical module
at the opposite site.
The transmit power at the opposite site is normal, A fiber is faulty. Go to the
but the receive power at the local site is close to the next step.
receiver sensitivity (for example, a difference within
3 dB)
2. If a fiber is faulty, check whether the fiber jumper from the equipment to the optical
distribution frame (ODF) and the fiber that is led out from the equipment room are
pressed, and whether any fiber connector is dirty or damaged. If yes, clean or replace the
fiber connector, or replace the fiber jumper. Check whether the alarm is cleared.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 1 or 2.
Step 4 Cause 4: The line performance deteriorates (the alarm is reported by an Ethernet electrical
port).
1. Check whether the cable grounding, cable connectors, and cables are damaged. If yes,
replace the faulty cables.
2. Check whether the alarm is cleared.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 1 or 2.
----End
Related Information
None
A.3.72 ETH_EFM_LOOPBACK
Description
The ETH_EFM_LOOPBACK is an alarm indicating the loopback. This alarm occurs when
the local end initiates a loopback or responds to a loopback request from the opposite end.
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 state of the loopback.
l 0x01: The local end initiates a loopback.
l 0x02: The local end responds to a loop request from the opposite end.
Possible Causes
l Cause 1: The local end initiates a loopback.
l Cause 2: The opposite end initiates a loopback.
Procedure
Step 1 Cause 1: The local end initiates a loopback.
1. According to the alarm parameter, it is determined that the local end initiates a loopback.
Determine the causes of the loopback initiated at the local end and release the loopback
as soon as possible.
----End
Related Information
None
A.3.73 ETH_EFM_REMFAULT
Description
The ETH_EFM_REMFAULT is an alarm indicating the fault on the opposite NE. This alarm
occurs when the local end receives the fault indication packet (OAMPDUM) from the
opposite end.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the fault type at the opposite end.
l 0x01: link fault.
l 0x02: dying gasp.
l 0x03: critical event.
Possible Causes
l Cause 1: The opposite NE is reset.
l Cause 2: The opposite NE is faulty.
Procedure
Step 1 Cause 1: The opposite NE is reset.
1. Check whether the opposite NE is reset frequently.
If... Then...
The opposite NE is reset frequently Reset the opposite NE, and the alarm is
cleared.
The opposite NE is not reset Rectify the fault on the opposite NE.
frequently
----End
Related Information
None
A.3.74 ETH_LOS
Description
The ETH_LOS alarm indicates the loss of Ethernet port connection.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l Cause 1: The negotiation fails because the transmit port and receive port work in
different modes.
l Cause 2: The cable or fiber is faulty.
l Cause 3: The local receive end is faulty.
l Cause 4: The remote transmit end is faulty.
Procedure
Step 1 Cause 1: The negotiation fails because the transmit port and receive port work in different
modes.
1. Check whether the transmit port and receive port work in the same mode.
If... Then...
The transmit port and receive port work in Correctly set the working modes of the
different modes transmit port and receive port.
If... Then...
The network cable is loose or damaged Connect the network cable properly or
replace the damaged network cable.
The connector of the fiber jumper is Clean the connector.
dirty
The connector or fiber is damaged Insert the connector properly or replace the
damaged fiber jumper.
The connection is normal Go to Cause 3.
If... Then...
The equipment is faulty Replace the NE.
The equipment is normal Go to Cause 4.
----End
Related Information
None
A.3.75 ETH_NO_FLOW
Description
The ETH_NO_FLOW is an alarm indicating that the Ethernet port has no flow. This alarm is
reported when an enabled Ethernet port is in link up state but has no flow.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the MAC port number.
Parameter 2, Indicate the path ID.
Parameter 3
Parameter 2 indicates the most significant bits and the value is
always 0x00. Parameter 3 indicates the least significant bits and the
value is always 0x01.
Possible Causes
l Cause 1: The port is enabled and in link up state, but is configured with no service.
l Cause 2: The port is enabled and in link up state, but does not transmit any packet due to
the service fault at the local end.
l Cause 3: The port is enabled and in link up state, but does not receive any packet due to
the service fault at the remote end.
Procedure
Step 1 Determine the MAC port number, alarmed board, and cause according to the parameters.
If... Then...
No services are available in the transmit Check whether the service is normal at the local
direction end.
No services are available in the receive Check whether the service is normal at the
direction remote end.
----End
Related Information
None
A.3.76 ETH_PWR_SUPPLY_FAIL
Description
The ETH_PWR_SUPPLY_FAIL alarm indicates a power outputting failure of an Ethernet
port. This alarm is reported when an Ethernet port is enabled with the PE function but outputs
no power.
Attribute
Parameters
Name Meaning
Parameter 1 Indicates the cause of power failure.
l 0x01: A short-circuit occurs.
l 0x02: An overcurrent event occurs.
l 0x03: The temperature exceeds the upper threshold.
l 0x04: The 3.3 V power supply is undervoltage.
l 0x05: The 4.8 V power supply is undervoltage.
l 0x06: A field effect transistor (FET) is faulty.
Possible Causes
l Cause: The board is faulty.
Procedure
Step 1 Cause: The board is faulty.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.77 ETHOAM_SELF_LOOP
Description
The ETHOAM_SELF_LOOP is an alarm indicating the loopback of the MAC port that runs
the point-to-point OAM protocol. This alarm occurs when the MAC port of a NE receives the
OAM protocol packet sent by the port itself or the NE after the loop detection function is
enabled.
Attribute
Alarm Severity Alarm Type
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 5 Indicates the ID of the virtual bridge whose MAC address flaps.
Possible Causes
l Cause 1: The cable connected to the port is self-looped, or the port is connected to a
LAN that has a loopback, or the PHY/MAC loopback is manually configured at the port.
l Cause 2: Two ports of the NE are connected through cables or two ports of the NE are
connected to the same LAN.
Procedure
Step 1 Determine the loopback type according to Parameter 1, and then handle the loopback
accordingly.
If... Then...
The value of Parameter 1 is 0x01 Go to Cause 1.
The value of Parameter 1 is 0x02 Go to Cause 2.
Step 2 Cause 1: The cable connected to the port is self-looped, or the port is connected to a LAN that
has a loopback, or the PHY/MAC loopback is manually configured at the port.
If... Then...
The PHY/MAC loopback is Manually release the PHY/MAC loopback (or wait five
manually configured at the port minutes for the automatic release by the NE if the
automatic loopback release function is enabled on the
NE). Then, the self-loop is released.
If... Then...
The cable connected to the port Connect the cable properly to release the self-loop.
is self-looped
The port is connected to a LAN Release the loopback on the LAN, or break the
that has a loopback connection between the port and the LAN, to release the
self-loop.
Step 3 Cause 2: Two ports of the NE are connected through cables or two ports of the NE are
connected to the same LAN.
1. Check whether two ports of the NE are connected through cables or whether two ports of
the NE are connected to the same LAN.
If... Then...
The two ports are connected Disconnect the cables to release the self-loop.
through cables
The two ports are connected to the Break the connection between a port and the
same network LAN to release the self-loop.
----End
Related Information
None
A.3.78 EXT_SYNC_LOS
Description
The EXT_SYNC_LOS is an alarm of the loss of the external clock source.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: the first external clock source
l 0x02: the second external clock source
Possible Causes
Cause 1: The external clock source is configured in the clock source priority list, but the
external clock source cannot be detected or become invalid.
Procedure
Step 1 Cause 1: The external clock source is configured in the clock source priority list, but the
external clock source cannot be detected or become invalid.
1. Check whether the equipment that provides the external clock source is faulty.
If... Then...
The equipment is faulty Rectify the fault.
The equipment is normal Go to the next step.
2. Check whether the cable that connects the external clock source is normal.
If... Then...
The cable is abnormal Replace the cable.
The cable is normal Replace the NE.
----End
Related Information
None
A.3.79 EXT_TIME_LOC
Description
The EXT_TIME_LOC is an alarm of the loss of the external time source.
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The link at a port is faulty.
l Cause 2: The external time device is faulty.
Procedure
Step 1 Cause 1: The link at a port is faulty.
1. Check cable connections. If cables are incorrectly connected, connect the cables again.
----End
Related Information
None
A.3.80 FAN_AGING
Description
The FAN_AGING is an alarm of the aged fan. This alarm occurs when the fan rotates at a
speed lower than eighty percent of the nominal speed.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the alarmed fan.
Possible Causes
Cause 1: The fan is aged.
Procedure
Step 1 Cause 1: The fan is aged.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.81 FAN_FAIL
Description
The FAN_FAIL is an alarm indicating that the fan is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the fan.
Possible Causes
Cause 1: Fan failure occurs.
Procedure
Step 1 Cause 1: Fan failure occurs.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.82 FDBSIZEALM_ELAN
Description
The FDBSIZEALM_ELAN alarm indicates that items listed in an E-LAN forwarding table
are all used. This alarm is reported when the number of actual items in the MAC address table
for the E-LAN service is greater than Address Detection Upper Threshold. This alarm is
cleared automatically when the number of items in the MAC address table of the E-LAN
service is lower than Address Detection Upper Threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The possible causes of the FDBSIZEALM_E-LAN alarm are as follows:
Procedure
l Cause 1: The value of Address Detection Upper Threshold is too low.
a. Check whether the value of Address Detection Upper Threshold is too small. For
details, see Configuring the MAC Address Learning Parameters.
b. If yes, set the parameter to a larger value based on actual situations. Check whether
the alarm is cleared. If the alarm persists, go to Cause 2.
l Cause 2: The E-LAN service is attacked.
a. Modify the settings so that the E-LAN service discards unknown packets. For
details, see Setting the Mode for Processing an Unknown Frame of the E-LAN
Service.
----End
Related Information
None
A.3.83 FLOW_EXC_LCS
Description
The FLOW_EXC_LCS alarm indicates that the traffic exceeds the range allowed by the
license.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
The actual transmitted service rate over an Ethernet port exceeds the maximum capacity
allowed by the license.
Procedure
Step 1 Check for any storm on the network. If there is a network storm, eliminate the source illegally
transmitting large volume of data. If there is no network storm, proceed to the next step.
----End
Related Information
None
A.3.84 FLOW_OVER
Description
The FLOW_OVER is an alarm indicating the received or transmitted traffic over the
threshold for some performance object
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the receive or transmit direction in which traffic crosses the specified
threshold.
l 0x00: the receive direction
l 0x01: the transmit direction
Possible Causes
l Cause 1: The traffic threshold is very low.
l Cause 2: The opposite end transmits excessive data flow.
l Cause 3: The network exists data storm.
Procedure
Step 1 Cause 1: The traffic threshold is very low.
1. Increase the traffic threshold to a value that is lower than the rate of the local threshold.
----End
Related Information
None
A.3.85 GSP_RSVP_NB_AUTH_ERR
Description
The GSP_RSVP_NB_AUTH_ERR alarm indicates a Resource Reservation Protocol (RSVP)
neighbor authentication error.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.
Possible Causes
The RSVP authentication parameters are set inconsistently on the local NE and the RSVP
neighbor.
Procedure
Step 1 Check the RSVP authentication parameters of the local NE and the RSVP neighbor. If the
parameters are set inconsistently, modify them to make them consistent.
----End
Related Information
None
A.3.86 GSP_RSVP_NB_DOWN
Description
The GSP_RSVP_NB_DOWN alarm indicates an interruption between the local NE and the
RSVP neighbor. This alarm is reported if the local NE does not receive any RSVP response
messages from the RSVP neighbor within three consecutive intervals.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1-4 Indicate the IP address of the local interface.
Parameters 5-8 Indicate the IP address of the RSVP neighbor's interface.
Possible Causes
l Cause 1: RSVP is disabled on the RSVP neighbor.
l Cause 2: There is no reachable route to the RSVP neighbor.
l Cause 3: The link between the local NE and the RSVP neighbor is faulty.
l Cause 4: The RSVP neighbor is faulty.
Procedure
Step 1 Cause 1: RSVP is disabled on the RSVP neighbor.
Step 3 Cause 3: The link between the local NE and the RSVP neighbor is faulty.
1. Check whether the link between the local NE and the RSVP neighbor is faulty, for
example, whether an ETH_LOS or MW_LOF alarm is reported.
2. If the link is faulty, rectify the fault by following instructions in Troubleshooting
Microwave Links or Troubleshooting Native Ethernet Services.
----End
Related Information
None
A.3.87 GSP_TNNL_DOWN
Description
The GSP_TNNL_DOWN alarm indicates that an RSVP-TE tunnel is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the RSVP-TE tunnel fault. The values are as follows:
l 0x01: indicates a route calculation failure.
l 0x02: indicates a signaling response time-out.
l 0x03: indicates a bandwidth resource request error.
l 0x04: indicates that the resources (including interface and label
information) requested by RSVP are invalid.
l 0x05: indicates a label allocation failure.
l 0x06: indicates a cross-connection control failure.
l 0x07: indicates a tunnel cross-connection setup failure.
l 0x08: indicates an unavailable data link.
l 0x09: indicates a signaling negotiation failure.
l 0x0a: indicates an unknown cause.
l 0x0b: indicates a link fault.
l 0x0c: indicates an RSVP tunnel creation failure.
l 0x0d: indicates a restoration failure during an RSVP restart.
l 0x0e: indicates an RSVP summary refresh time-out.
l 0x0f: indicates an RSVP GR time-out.
l 0x10: indicates that a lower-priority RSVP tunnel goes Down because its
bandwidth resources are preempted by a higher-priority tunnel.
Parameters Indicate the IP address of the faulty NE on the RSVP-TE tunnel.
2-5
Possible Causes
l Cause 1:
The system control board on the peer NE has a hardware fault or software fault.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 2:
The link to the peer NE is faulty.
This may be the cause for 0x01, 0x02, 0x06, 0x07, 0x08, 0x09, 0x0b, 0x0c, 0x0d, 0x0e,
or 0x0f.
l Cause 3:
There is no reachable route to the destination NE, or no route complies with the explicit
LSP.
This may be the cause for 0x01, 0x02, 0x09, 0x0c, 0x0d, 0x0e, or 0x0f.
l Cause 4:
The RSVP-TE tunnel configurations are incorrect.
This may be the cause for 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x09, 0x0a, 0x0c, 0x0f,
or 0x10.
l Cause 5:
The bandwidth of the NE is insufficient.
This may be the cause for 0x03, 0x04, or 0x10.
Procedure
Step 1 Cause 1: The system control board on the peer NE has a hardware or software fault.
1. Check whether the system control board on the peer NE has a hardware or software fault.
If the board has a fault, rectify it.
Step 2 Cause 2: The link to the peer NE is faulty.
1. Check whether the link to the peer NE is faulty. If the link is faulty and it is a microwave
link, rectify the fault by following instructions in Troubleshooting Microwave Links. If
the link is faulty and it is an Ethernet link, rectify the fault by following instructions in
Troubleshooting Native Ethernet Services.
Step 3 Cause 3: There is no reachable route to the destination NE, or no route complies with the
explicit LSP.
1. Ping the IP address of the destination NE and each NE along the explicit LSP. Ensure
that there is a reachable route to the destination NE or each NE along the explicit LSP.
2. Ensure that the IS-IS configurations on all the NEs between the local NE and destination
NE are correct.
Step 4 Cause 4: The RSVP-TE tunnel configurations are incorrect.
1. Ensure that the RSVP-TE tunnel configurations are correct. If IS-IS TE is enabled on an
interface, ensure that the RSVP authentication and RSVP-TE explicit path configurations
are correct.
Step 5 Cause 5: The bandwidth of the NE is insufficient.
1. Ensure that the bandwidth resources reserved for tunnels are configured correctly.
2. If a higher-priority tunnel preempts the bandwidth resources of a lower-priority tunnel,
check whether the tunnel priorities are configured properly. If the tunnel priorities are not
configured properly, configure them again.
3. If the reserved bandwidth resources are correctly configured and tunnel priorities are
configured properly but the link bandwidth cannot meet requirements, increase the
network bandwidth.
----End
Related Information
None
A.3.88 HARD_ERR
Description
The HARD_BAD alarm indicates an hardware error. This alarm is reported when there are
minor hardware errors.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameter 1 Indicates that a storage component is faulty. The value is fixed to 0x14.
Parameter 3 Reserved.
Possible Causes
Cause: The board hardware is faulty.
Procedure
Step 1 Perform a warm reset or perform a cold reset on the board that reports the alarm on the
NMS.
----End
Related Information
None
A.3.89 HARD_BAD
Description
The HARD_BAD alarm indicates that hardware is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2, Indicate the internal fault detected by the board. For details
Parameter 3 about the parameters, see the HARD_BAD alarm parameter
query tool.
Possible Causes
Cause 1: The NE hardware is faulty.
Procedure
Step 1 6.1 Replace the IDU
----End
Related Information
None
A.3.90 HP_CROSSTR
Description
The HP_CROSSTR is an alarm indicating that the higher order path error crosses the
threshold. This alarm occurs when the board detects that the performance event that the higher
order path error crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.
l 0x30: HPBBE
l 0x31: HPES
l 0x32: HPSES
l 0x33: HPFEBBE
l 0x34: HPFEES
l 0x35: HPFESES
l 0x36: HPUAS
l 0x4c: HPFEUAS
Possible Causes
Cause 1: The higher order path error crosses the preset threshold.
Procedure
Step 1 Cause 1: The higher order path error crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event that the higher
order path error crosses the preset threshold. For details, see 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
2. Handle the threshold-crossing performance event.
----End
Related Information
None
A.3.91 HP_LOM
Description
The HP_LOM is an alarm indicating the loss of the higher order path multiframe. This alarm
occurs when the board detects that byte H4 is inconsistent with the expected multiframe
sequence.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The service level is inconsistently configured at both ends.
l Cause 2: The transmit unit of the peer NE is faulty.
l Cause 3: The receive unit of the local NE is faulty.
Procedure
Step 1 Cause 1: The service level is inconsistently configured at both ends.
1. Verify that cross-connection configurations (signal mapping) are consistent at both ends.
For example, if the VC-12 structure is configured at the local end and the VC-3 structure
is configured at the peer end, rectify the configurations.
Step 2 Cause 2: The transmit unit of the peer NE is faulty.
1. Replace the IDU. Then, check whether the alarm is cleared.
If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Replace the IDU or the line board at the opposite end.
----End
Related Information
None
A.3.92 HP_RDI
Description
The HP_RDI is an alarm indicating the higher order path remote receive failure. This alarm
occurs when the board detects that bit 5 of byte G1 is 1.
Attribute
Parameters
None
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the higher order path remote receive failure.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the higher order path remote receive failure.
1. Clear the alarms such as HP_LOM and B3_EXC that the AU-4 path reports on the
opposite NE.
----End
Related Information
None
A.3.93 HP_REI
Description
The HP_REI is an alarm indicating the higher order path remote error. This alarm occurs
when the board detects that bits 1-4 of G1 take a value from 1 to 8.
Attribute
Parameters
None
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the higher order path remote errors.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the higher order path remote receive failure.
1. Handle the HP_BBE performance event that the AU-4 path reports on the opposite NE.
----End
Related Information
None
A.3.94 HP_SLM
Description
The HP_SLM is an alarm indicating the lower order path label mismatch. This alarm occurs
when the board detects the C2 byte mismatch.
Attribute
Parameters
None
Possible Causes
l Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte
configured to be received at the local end.
l Cause 2: Configuration data is incorrect.
Procedure
Step 1 Cause 1: The C2 byte sent from the peer end is not 0 and differs from the C2 byte configured
to be received at the local end.
1. Configure the same service type at the source and sink of the AU-4 path. For details, see
Configuring Overhead Bytes.
----End
Related Information
None
A.3.95 HP_TIM
Description
The HP_TIM is an alarm indicating the higher order path trace identifier mismatch. This
alarm occurs when the board detects the J1 byte mismatch.
Attribute
Parameters
None
Possible Causes
l Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte
transmitted on the opposite NE.
l Cause 2: Configuration data is incorrect.
Procedure
Step 1 Cause 1: The receivable J1 byte on the local NE does not match with the J1 byte transmitted
on the opposite NE.
1. Disable the receivable J1 byte on the local NE or set the receivable J1 byte on the local
NE to the same as the transmitted J1 byte on the opposite NE. For details, see
Configuring VC-4 POHs.
If... Then...
The alarm is cleared after the configuration is The fault is rectified. End the alarm
changed handling.
The alarm persists after the configuration is Go to the next step.
changed
2. Check whether the cross-connections are configured correctly at the intermediate nodes
where the service travels. If not, reconfigure the cross-connections. For details, see
Creating Cross-Connections of SNCP Services or Creating the Cross-Connections of
Point-to-Point Services.
----End
Related Information
None
A.3.96 HP_UNEQ
Description
The HP_UNEQ is an alarm indicating the unequipped higher order path. This alarm occurs
when the board detects that the C2 byte is 0.
Attribute
Parameters
None
Possible Causes
l Cause 1: The line port at the local NE is configured with services, but the corresponding
line port at the opposite NE is not configured with services.
l Cause 2: Byte C2 is set to 0 at the opposite NE.
Procedure
Step 1 Cause 1: The line port at the local NE is configured with services, but the corresponding line
port at the opposite NE is not configured with services.
1. Configure line services on the opposite NE. For details, see Creating Cross-Connections
of SNCP Services or Creating the Cross-Connections of Point-to-Point Services.
----End
Related Information
None
A.3.97 HPAD_CROSSTR
Description
The HPAD_CROSSTR is an alarm indicating that the higher order path adaptation
performance crosses the threshold. This alarm occurs when a board detects that the
performance event of TU pointer justification 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Name Meaning
Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.
l 0xaa: TUPJCHIGH
l 0xab: TUPJCLOW
l 0xac: TUPJCNEW
Possible Causes
Cause 1: The performance event of TU pointer justification crosses the preset threshold.
Procedure
Step 1 Cause 1: The performance event of TU pointer justification crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event of TU pointer
justification that crosses the preset threshold. For details, see 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
2. Handle the threshold-crossing performance event.
----End
Related Information
None
A.3.98 IF_CABLE_OPEN
Description
The IF_CABLE_OPEN is an alarm indicating that the IF cable is open.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The IF cable is loose or faulty.
l Cause 2: The IF port is damaged.
l Cause 3: The power module of the ODU is faulty.
NOTE
When rectifying the faults of the IF cable, IF port, and ODU, you must turn off the ODU before the
operation. You can turn on the ODU only after the operation is complete.
Procedure
Step 1 Cause 1: The IF cable is loose or faulty.
1. Check whether the connector of the IF cable is loose or whether the connector is made
properly.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
The connector is loose Connect the connector tightly.
The connector is made See the Installation Reference and make new
improperly connectors for the IF cable.
None of the above Go to the next step.
2. Check whether the surface of the IF fiber jumper and the IF cable is damaged.
If... Then...
The cable does not meet the requirement Replace the cable with a qualified one.
----End
Related Information
None.
A.3.99 IF_INPWR_ABN
Description
The IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an
ODU is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: Indicates that the input power of the ODU is too high.
l 0x02: Indicates that the input power of the ODU is too low.
Possible Causes
l Cause 1: The IF board is faulty.
l Cause 2: The IF cable is faulty.
l Cause 3: The ODU is faulty.
l Cause 4: The IF fiber jumper and the IF board are connected incorrectly.
Procedure
Step 1 Cause 1: The IF board is faulty.
1. ReReplace the IDU.
The connectors to be checked include the connector between the IF fiber jumper and the
IF board, the connector between the IF fiber jumper and the IF cable, and the connector
between the IF cable and the ODU.
If... Then...
Any of the connectors is prepared See the Installation Reference and make
incorrectly new connectors for the IF cable.
2. Check whether the surface of the IF fiber jumper and the IF cable is damaged or
deformed, and test the connectivity between the IF fiber jumper and the IF cable. For
details, see Testing the Connectivity of the IF Cable.
If... Then...
----End
Related Information
For single-IF boards:
l The logical slot ID of an OptiX RTN 910A/950/950A ODU is the logical slot ID of the
IF board that is connected to the ODU plus 20.
l The logical slot ID of an OptiX RTN 980 ODU is the logical slot ID of the IF board that
is connected to the ODU plus 50.
For dual-IF boards:
l The logical slot ID of the OptiX RTN 910A/950/950A ODU connected to the first IF
port is the logical slot ID of the IF board plus 20. The logical slot ID of the OptiX RTN
980 ODU connected to the first IF port is the logical slot ID of the IF board plus 50.
l The logical slot ID of the OptiX RTN 910A, 950, 950A, or 980 ODU connected to the
second IF port is the logical slot ID of the ODU connected to the first IF port plus 20.
A.3.100 IGSP_ENTRIES_EXC
Description
The IGSP_ENTRIES_EXC alarm is reported when the number of IGMP Snooping multicast
table entries exceeds its upper threshold, and will be cleared when the number of IGMP
Snooping multicast table entries is smaller than its lower threshold.
Attribute
Alarm Severity Alarm Type
Minor Security 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 whether the number of IGMP Snooping multicast table entries
exceeds its upper threshold.
l 0x00: indicates that the number of IGMP Snooping multicast table entries
does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast table entries
exceeds its upper threshold.
Parameter 2 Indicates whether the number of IGMP Snooping multicast group members
exceeds its upper threshold.
l 0x00: indicates that the number of IGMP Snooping multicast group
members does not exceed its upper threshold.
l 0x01: indicates that the number of IGMP Snooping multicast group
members exceeds its upper threshold.
Possible Causes
l Cause 1: The configured upper threshold for the number of IGMP Snooping multicast
table entries is too small.
l Cause 2: IGMP Snooping protocol attack packets are generated on the network.
Procedure
Step 1 Cause 1: The configured upper threshold for the number of IGMP Snooping multicast table
entries is too small.
1. Check whether the configured upper threshold for the number of IGMP Snooping
multicast table entries is too small. If the upper threshold is too small, set another larger
value according to the network plan.
2. Check whether the alarm is cleared. If it persists, go to Cause 2.
Step 2 Cause 2: IGMP Snooping protocol attack packets are generated on the network.
1. Check whether IGMP Snooping protocol attack packets are generated on the network.
Upon detection of any IGMP Snooping attack packets, locate the attack source and
shield it.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
Related Information
None
A.3.101 IN_PWR_ABN
Description
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.
Attribute
Parameters
None
Possible Causes
l Cause 1: The transmit power of the opposite NE is over high or over low.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over high or over low.
1. Browse current performance events, and query the performance event of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not meet Replace the optical module.
the requirement
The transmit optical power is over high Add a proper attenuator to reduce the
receive optical power.
If... Then...
The models are incorrect Replace the optical module.
The models are correct Go to Cause 3.
If... Then...
The connector of the fiber jumper is dirty Clean fiber connectors.
The connector or fiber is damaged Insert the connector properly or replace the
damaged fiber jumper.
----End
Related Information
None
A.3.102 IN_PWR_HIGH
Description
The IN_PWR_HIGH is an alarm indicating that the input optical power is over high.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The transmit power of the opposite NE is over high.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
Procedure
Step 1 Cause 1: The transmit power of the opposite site is over high.
1. Browse current performance events, and query the performance event of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not Contact Huawei engineers to replace the
meet the requirement optical module.
The transmit optical power meets the Add a proper attenuator to reduce the
requirement receive optical power.
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
The models are correct Go to Cause 3.
----End
Related Information
The optical power threshold set for the IN_PWR_HIGH alarm is lower than the overload
point.
A.3.103 IN_PWR_LOW
Description
The IN_PWR_LOW is an alarm indicating that the input optical power is over low.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The transmit power of the opposite NE is over low.
l Cause 2: The model of the selected optical module is incorrect.
l Cause 3: The optical module at the receive end is faulty.
l Cause 4: The fiber performance degrades.
Procedure
Step 1 Cause 1: The transmit power of the opposite NE is over low.
1. Browse current performance events, and query the performance event of the transmit
optical power on the opposite NE.
If... Then...
The transmit optical power does not meet the Contact Huawei engineers to replace
requirement the optical module.
The transmit optical power meets the Go to Cause 2.
requirement
If... Then...
The models are incorrect Contact Huawei engineers to replace the optical module.
The models are correct Go to Cause 3.
If... Then...
The receive optical power meets the Contact Huawei engineers to replace
requirement the optical module.
The receive optical power does not meet the Go to Cause 4.
requirement
If... Then...
The alarm is cleared after the connector is The fault is rectified. End the alarm
cleaned handling.
The alarm persists after the connector is cleaned Replace the fiber.
----End
Related Information
The optical power threshold set for the IN_PWR_LOW alarm is higher than the sensitivity
point.
A.3.104 INTEMP_SENSOR_FAIL
Description
The INTEMP_SENSOR_FAILL is an alarm indicating that the air inlet temperature sensor of
the cabinet fails.
Attribute
Parameters
None
Possible Causes
l Cause 1: The air inlet temperature sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The air inlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air inlet temperature sensor is faulty.
1. Replace the air inlet temperature sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.105 IPFPM_INST_TLP_ERR
Description
The IPFPM_INST_TLP_ERR alarm indicates that binding an IP FPM instance to the Target
Logical Port (TLP) 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x00: ACL resources are insufficient.
l 0x01: The IPFPM measurement instance configuration is inconsistent with
the planned IP packet coloring.
Possible Causes
l Cause 1: ACL resources are insufficient.
l Cause 2: The IPFPM measurement instance configuration is inconsistent with the
planned IP packet coloring.
Procedure
Step 1 Cause 1: ACL resources are insufficient.
1. Delete useless IP FPM instances or undesired complex traffic classification
configurations to release ACL resources.
2. Re-bind the IP FPM instance to the TLP.
3. Check whether the alarm is cleared. If the alarm persists, go to Step 2.
Step 2 Cause 2: The IPFPM measurement instance configuration is inconsistent with the planned IP
packet coloring.
1. Change the IPFPM measurement instance configuration to be consistent with the
planned IP packet coloring.
2. Check whether the alarm is cleared. If the alarm persists, contact Huawei technical
support engineers to handle the alarm.
----End
A.3.106 IPFPM_LOSSRATIO_EXCE
Description
The IPFPM_LOSSRATIO_EXCE alarm indicates that the packet loss ratio measured by the
IPFPM function exceeds the upper threshold. This alarm is reported when the packet loss
ratio exceeds the upper threshold for five consecutive measurement periods.
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
Name Meaning
Parameters 1 to 4 Indicate the test instance ID.
Possible Causes
l Cause 1: Excessive bit errors exist.
l Cause 2: Bandwidth is insufficient due to traffic bursts or AM downshifts.
Procedure
Step 1 Cause 1: Excessive bit errors exist.
1. Check for and clear any MW_FEC_UNCOR, MW_BER_EXC, and MW_BER_SD
alarms.
2. Check whether the IPFPM_LOSSRATIO_EXCE alarm is cleared. If the
IPFPM_LOSSRATIO_EXCE alarm persists, go to Step 2.
----End
A.3.107 IPFPM_ONEDELAY_EXCE
Description
The IPFPM_ONEDELAY_EXCE alarm indicates that the service one-way delay exceeds the
upper threshold. This alarm is reported when the service one-way delay exceeds the upper
threshold for five consecutive measurement periods.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicate the test instance ID.
Possible Causes
Cause 1: The link quality is poor.
Procedure
Step 1 Check whether services are switched to a poor-quality link. If yes, troubleshoot the link
switching. If no, go to the next step.
Step 2 Check whether any congestion occurs on the network due to traffic bursts or insufficient
bandwidth. If yes, troubleshoot the congestion. If no, contact Huawei engineers to handle the
alarm.
----End
A.3.108 IPFPM_TWODELAY_EXCE
Description
The IPFPM_TWODELAY_EXCE alarm indicates that the service two-way delay exceeds the
upper threshold. This alarm is reported when the service two-way delay exceeds the upper
threshold for five consecutive measurement periods.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 to 4 Indicate the test instance ID.
Possible Causes
Cause 1: The link quality is poor.
Procedure
Step 1 Check whether services are switched to a poor-quality link. If yes, troubleshoot the link
switching. If no, go to the next step.
Step 2 Check whether any congestion occurs on the network due to traffic bursts or insufficient
bandwidth. If yes, troubleshoot the congestion. If no, contact Huawei engineers to handle the
alarm.
----End
A.3.109 ISISADJACENCYCHANGE
Description
The ISISADJACENCYCHANGE alarm indicates that the status of an IS-IS neighbor
changes.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1-4 Indicate the IS-IS process ID.
Possible Causes
l Cause 1: The IS-IS configurations are incorrect.
l Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
l Cause 3: The IS-IS neighbor fails.
Procedure
Step 1 Cause 1: The IS-IS configurations are incorrect.
1. Ensure that the IS-IS configurations are consistent on the local NE and the IS-IS
neighbor.
Step 2 Cause 2: The link between the local NE and the IS-IS neighbor is faulty.
1. Check whether the link between the local NE and the IS-IS neighbor is faulty, for
example, whether an ETH_LOS alarm is reported.
2. If the link is faulty, rectify the fault.
----End
Related Information
None
A.3.110 J0_MM
Description
The J0_MM is an alarm indicating the trace identifier mismatch. This alarm occurs when the
board detects the J0 byte mismatch.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the
opposite NE.
Procedure
Step 1 Cause 1: The receivable J0 byte on the local NE does not match the transmitted J0 byte on the
opposite NE.
1. Disable the receivable J0 byte on the local NE. For details, see Configuring RSOHs.
----End
Related Information
None
A.3.111 K1_K2_M
Description
The K1_K2_M is an alarm indicating the K1/K2 byte mismatch. This alarm occurs when the
board detects inconsistent channel numbers that the transmitted K1 byte (bits 5-8) and the
received K2 byte (bits 1-4) indicate.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the protection group type.
l 0x01: linear MS protection.
l 0x02: ring MS protection.
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates
that the alarm is reported by protection group 1.
Possible Causes
l Cause 1: The switching modes configured at both ends are single-ended switching and
dual-ended switching separately.
l Cause 2: The fiber connection is incorrect.
l Cause 3: A certain board is faulty.
Procedure
Step 1 Cause 1: The switching modes configured at both ends are single-ended switching and dual-
ended switching separately.
1. Check whether the switching modes at both ends are the same.
If... Then...
The switching modes are different Configure the switching modes as the same.
The switching modes are the same Go to Cause 2.
If... Then...
The fiber connection is incorrect Connect the fiber properly.
The connection is correct Go to Cause 3.
If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Replace the IDU.
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer to Creating a Packet-based Linear MSP Group
A.3.112 K2_M
Description
The K2_M is an alarm indicating the K2 byte mismatch. This alarm occurs when the board
detects that the protection mode indicated by the received K2 (bit 5) is different from the
protection mode of the NE.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the protection group type.
l 0x01: linear MS protection.
l 0x02: ring MS protection.
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates
that the alarm is reported by protection group 1.
Possible Causes
l Cause 1: Two NEs of the linear MSP group are configured with different protection
modes (1+1 or 1:N).
l Cause 2: The MSP protocol is stopped when the protection switching occurs.
l Cause 3: The fiber connection is incorrect.
l Cause 4: A certain board is faulty.
Procedure
Step 1 Cause 1: Two NEs of the linear MSP group are configured with different protection modes
(1+1 or 1:N).
1. Query the status of the linear MSP, and check whether two NEs of the linear MSP group
are configured with different protection modes (1+1 or 1:N).
If... Then...
The protection modes are different Configure the protection modes as the same.
The protection modes are the same Go to Cause 2.
Step 2 Cause 2: The MSP protocol is stopped when the protection switching occurs.
1. Query the status of the linear MSP, and check whether the MSP protocol is stopped on
the opposite NE.
If... Then...
The protocol is stopped Restart the MSP protocol on the opposite NE. For details,
see Starting/Stopping the Linear MSP Protocol.
The protocol is running Go to Cause 3.
If... Then...
The connection is incorrect Connect the fiber properly
If... Then...
The connection is correct Go to Cause 4.
If... Then...
The alarm is cleared The fault is rectified. End the alarm handling.
The alarm persists Replace the IDU.
----End
Related Information
This alarm is also reported upon a packet linear MSP switching. For configuration details on
linear MSP, refer toCreating a Packet-based Linear MSP Group.
A.3.113 KMC_KEY_SYNC_FAIL
Description
The KMC_KEY_SYNC_FAIL alarm indicates a KMC key synchronization failure. (KMC is
short for key management center.)
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l Cause 1: The database on the alarmed NE is abnormal.
l Cause 2: The database backup fails on the alarmed NE.
Procedure
Step 1 Restore NE data from the latest backup database.
Step 2 If NE data restoration fails, contact Huawei engineers to handle the alarm.
----End
Related Information
None
A.3.114 L3V_TRAP_THRE_EXCEED
Description
The L3V_TRAP_THRE_EXCEED alarm indicates that the number of VPN route prefixes
exceeds the maximum number allowed.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-35 Indicates the current number of route prefixes.
Parameters 36-39 Indicates the maximum number of route prefixes.
Possible Causes
l Cause 1: Data configuration is incorrect.
l Cause 2: The maximum number of route prefixes in a VPN instance routing table is set
to a small value.
l Cause 3: The network structure is not appropriate.
Procedure
Step 1 Cause 1: Data configuration is incorrect.
1. Check the data configuration, especially BGP route configuration, to ensure that the NE
receives only required routes.
Step 2 Cause 2: The maximum number of route prefixes in a VPN instance routing table is set to a
small value.
1. Increase the maximum number of route prefixes in a VPN instance routing table.
Step 3 Cause 3: The network structure is not appropriate.
1. Optimize the network structure.
----End
Related Information
None
A.3.115 L3V_TRAP_VRF_DOWN
Description
The L3V_TRAP_VRF_DOWN alarm indicates that a VPN instance is in the Down state. This
alarm is reported when all the interfaces bound to a VPN instance go Down or the binding
relationships between a VPN instance and interfaces in the Up state are deleted.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
Name Meaning
Parameters 1-31 Indicate the name of a VPN instance.
Parameters 32-33 Indicate the slot ID.
Parameter 34 Indicates the sub-slot ID.
Parameters 35-36 Indicate the interface ID.
Parameters 37-40 Indicate the interface running status. The values are as follows:
l 0x01: active
l 0x02: notInService
Parameters 41-44 Indicate the VPN instance running status.
l 0x01: up
l 0x02: down
Possible Causes
l Cause 1: The VPN instance is not bound with any interfaces.
l Cause 2: All the interfaces bound to the VPN instance go Down.
Procedure
Step 1 Cause 1: The VPN instance is not bound with any interfaces.
1. Bind interfaces to the VPN instance according to the plan. Ensure that the status of these
interfaces is Up.
Step 2 Cause 2: All the interfaces bound to the VPN instance go Down.
1. Ensure that the interfaces are enabled and configured with IP addresses. For details, see
Setting Ethernet Interface Parameters. If the interfaces are still in the Down state, go to
the next step.
2. Check whether the links to the interfaces are faulty. If they are faulty, rectify the faults by
following instructions in Troubleshooting Native Ethernet Services.
----End
Related Information
None
A.3.116 LAG_BWMM
Description
LAG_BWMM is an alarm indicating the bandwidth inconsistency in the LAG group.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: In the LAG group, the license capacities of the ports differ from each other.
Procedure
Step 1 Cause 1: In the LAG group, the license capacities of the ports differ from each other.
1. Query the license capacities of the LAG group by using the NMS.
2. If the license capacities of the ports differ from each other, reload a license file of an
appropriate capacity.
----End
Related Information
None
A.3.117 LAG_DOWN
Description
The LAG_DOWN is an alarm indicating that the link aggregation group (LAG) is
unavailable. This alarm occurs when the LAG does not have activated members.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: All the member ports of the aggregation group are invalid for the same causes as the
LAG_MEMBER_DOWN alarm.
Procedure
Step 1 Cause 1: All the member ports of the LAG are invalid for the same causes as the
LAG_MEMBER_DOWN alarm.
1. Determine the alarmed port according to the alarm parameter.
2. Rectify the fault at each member port according to the description of
LAG_MEMBER_DOWN.
----End
Related Information
None
A.3.118 LAG_MEMBER_DOWN
Description
The LAG_MEMBER_DOWN is an alarm indicating that a member port of a link aggregation
group (LAG) is unavailable. This alarm occurs when a member port of an LAG can neither be
activated nor function as a protection port.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter Indicates the slot ID of the alarmed board.
2
Parameter 3 Indicates the ID of the alarmed subboard. The value is always 0xff.
Parameter 4, Parameter Indicates the ID of the alarmed port.
5
Parameter 6 Indicates the cause that makes the port unavailable.
l 0x01: The port link is faulty or disabled.
l 0x02: The port fails to receive the LACP packets.
l 0x03: The port works in half-duplex mode.
l 0x04: The port is self-looped.
Possible Causes
l Cause 1: The port link is faulty or disabled.
l Cause 2: The port receives no LACP packets.
l Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.
l Cause 4: The port is self-looped.
Procedure
Step 1 Determine the alarmed port and the cause of the alarm according to the alarm parameters.
If... Then...
The value of Parameter 4 is 0x01 Perform the operations described in Step 2.
The value of Parameter 4 is 0x02 Perform the operations described in Step 3.
The value of Parameter 4 is 0x03 Perform the operations described in Step 4.
The value of Parameter 4 is 0x04 Perform the operations described in Step 5.
If... Then...
The port is not enabled Enable the port in the LAG.
The port is enabled Go to the next step.
2. Check the link status of all ports and check whether the ETH_LOS alarm is reported.
If... Then...
The alarm is reported Clear the ETH_LOS alarm immediately and rectify the
fault of the port link.
The alarm is not reported Go to Cause 2.
Step 4 Cause 3: The port works in half-duplex mode or not in Auto-Negotiation mode.
1. On the NMS, check whether the port in the LAG works in half-duplex mode. For details,
see Querying the Protocol Information of the LAG. If the port works in half-duplex
mode, change the working mode of the port into full-duplex.
2. On the NMS, change the working mode of the port into full-duplex and Auto-
Negotiation.
----End
Related Information
None
A.3.119 LAN_LOC
Description
The LAN_LOC is an alarm indicating the Ethernet communication failure.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the network port ID. For example, 0x01 indicates network
port 1 and 0x02 indicates network port 2.
Parameter 2, Indicates the number of the path on which the alarm is reported.
Parameter 3
Parameter 2 indicates the most significant bits and the value is always
0x00. Parameter 3 indicates the least significant bits and the value is
always 0x01.
Possible Causes
l Cause 1: The cable is not connected to the network port, or the cable is faulty.
l Cause 2: The network port is faulty.
l Cause 3: The NE is faulty.
Procedure
Step 1 View the alarm on the NMS. Determine the network port ID according to the alarm parameter
1.
Step 2 Cause 1: The cable is not connected to the network port, or the cable is faulty.
1. Check whether the cable of the network port is loose or no cable is connected. Properly
connect the NMS to the network port. The LINK indicator is in green.
Step 4 Cause 3: The system control, switching, and timing board is faulty.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.120 LASER_CLOSED
Description
The LASER_CLOSED is an alarm indicating that the laser is shut down. This alarm occurs
when the laser is shut down by using the NMS.
Attribute
Parameters
None
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.
1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None
A.3.121 LASER_MOD_ERR
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the NE does not match the type of the optical interface.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of
the optical interface.
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface
type.
l Cause 3: The optical module is faulty.
l Cause 4: The NE is faulty.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
1. Check whether the optical module installed at the optical interface matches the rate of
the optical interface. For details, see 4.8.5 Querying the Board Manufacturing
Information Report.
If... Then...
The optical module does not match the Contact Huawei engineers to replace the
rate of the optical interface optical module with one that matches the
rate of the optical interface.
The optical module matches the rate of Go to Cause 2.
the optical interface
Step 2 Cause 2: The SFP module does not match the interface type.
1. Replace the existing SFP module with a proper SFP module.
Step 3 Cause 3: The optical module is faulty.
If... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.
----End
Related Information
None
A.3.122 LASER_MOD_ERR_EX
Description
The LASER_MOD_ERR is an alarm indicating that the type of the pluggable optical module
on the board does not match the type of the optical interface.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The optical module installed at the optical interface does not match the rate of
the optical interface.
l Cause 2: The small form-factor pluggable (SFP) module does not match the interface
type.
l Cause 3: The optical module is faulty.
l Cause 4: A certain board is faulty.
Procedure
Step 1 Cause 1: The optical module installed at the optical interface does not match the rate of the
optical interface.
1. Check whether the optical module installed at the optical interface matches the rate of
the optical interface. For details, see 4.8.5 Querying the Board Manufacturing
Information Report.
If... Then...
The optical module does not match the Contact Huawei engineers to replace the
rate of the optical interface optical module with one that matches the
rate of the optical interface.
The optical module matches the rate of Go to Cause 2.
the optical interface
Step 2 Cause 2: The SFP module does not match the interface type.
1. Replace the existing SFP module with a proper SFP module.
If.. Then...
The port type is incorrectly set See Configuring an SFP Port.to rectify the port type
setting
The SFP type is incorrect Replace it with an SFP module of the correct type.
If... Then...
The alarm is cleared after the optical module is replaced End the alarm handling.
The alarm persists after the optical module is replaced Go to Cause 3.
----End
Related Information
None
A.3.123 LASER_SHUT
Description
The LASER_SHUT is an alarm indicating that the laser is shut down. This alarm occurs when
the laser is shut down by using the NMS.
Attribute
Parameters
None
Possible Causes
Cause 1: The laser on the local NE is shut down by using the NMS.
Procedure
Step 1 Cause 1: The laser on the local NE is shut down by using the NMS.
1. Find out the cause of shutting down the laser and start up the laser as soon as possible.
----End
Related Information
None
A.3.124 LCS_DAYS_OF_GRACE
Description
The LCS_DAYS_OF_GRACE alarm indicates that a license file has expired but is in the
grace period of 60 days.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 and 2 Indicate the ID of a control item.
Parameters 3 and 4 Indicate the remaining grace period (days) of the license file.
Name Meaning
Parameter 5 Indicates the cause for the license file to become invalid:
l 0x00: The license file is naturally invalid.
l 0x01: The license file is forcibly invalid.
l 0x02: The ESN does not match.
l 0x03: The V/R version does not match.
l 0x04: Both the ESN and V/R version do not match.
Possible Causes
l Cause 1: The license file has expired, but is in the grace period of 60 days.
l Cause 2: The ESN of the license file or the V/R version does not match, and the license
file is in the grace period of 60 days.
l Cause 3: A certain control item expires but is in the grace period of 60 days.
Procedure
Step 1 Contact Huawei technical support engineers to reload the associated license file.
----End
Related Information
None
A.3.125 LCS_EXPIRED
Description
The LCS_EXPIRED alarm indicates that a license file has expired and the grace period of 60
days times out.
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
Name Meaning
Parameters 1 Indicate the days since the grace period of a license has expired or the ID
and 2 of the expired license.
Parameter 3 Indicates the cause for the license file to become invalid:
l 0x00: The license file is naturally invalid.
l 0x01: The license file is forcibly invalid.
l 0x02: The ESN does not match.
l 0x03: The V/R version does not match.
l 0x04: Both the ESN and V/R version do not match.
l 0xff: Parameters 1 and 2 indicate the ID of the expired license.
Possible Causes
l Cause 1: The system has run for more than 60 days after the license file expired.
l Cause 2: The system has run for more than 60 days after the ESN or V/R version of the
license file does not match.
Procedure
Step 1 Contact Huawei technical support engineers to reload the associated license file.
----End
Related Information
None
A.3.126 LCS_FILE_NOT_EXIST
Description
The LCS_FILE_NOT_EXIST alarm indicates that an NE fails to detect the ESDP license file.
Attribute
Parameters
None
Possible Causes
The system fails to find the ESDP license file when being started.
Procedure
Step 1 Purchase and load the ESDP license file.
----End
Related Information
None
A.3.127 LCS_LIMITED
Description
The LCS_LIMITED alarm indicates that the configuration capacity of an NE exceeds the
capacity authorized by the license file.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The service capacity exceeds the capacity authorized by the license
file.
l 0x02: The AM license capacity exceeds the capacity authorized by the
license file.
l 0x03: For IF protection, the bandwidth at the standby port authorized by
the license file is lower than the bandwidth at the main port authorized by
the license file.
l 0x04: The 1588v2 capacity exceeds the capacity authorized by the license
file.
l 0x05: The ATM/IMA capacity exceeds the capacity authorized by the
license file.
l 0x06: The air port LAG capacity exceeds the capacity authorized by the
license file.
l 0x07: The E1PRIOR function is restricted.
l 0x08: The synchronous Ethernet capacity exceeds the capacity authorized
by the license file.
l 0x09: The air port compression capacity exceeds the capacity authorized by
the license file
l 0x0a: The MPLS service license capacity exceeds the capacity authorized
by the license file.
l 0x0b: The PLA license capacity exceeds the capacity authorized by the
license file.
l 0x0c: The total service bandwidth (TDM service bandwidth and data
service bandwidth) exceeds the bandwidth allowed by the Ethernet license
file for the working and protection links.
l 0x0d: The GE port capacity exceeds the capacity authorized by the license
file.
l 0x0e: No XPIC license is available.
l 0x0f: No ERPS license is available.
l 0x10: The number of configured VC-12 cross connections exceeds the
number authorized by the license file.
l 0x11: The number of ports configured with the 1024QAM modulation
scheme exceeds the number authorized by the license file.
l 0x12: No microwave 1+1 protection license is available.
l 0x13: No enhanced QoS license is available.
l 0x14: The capacity configured for the COMBO port exceeds the licensed
capacity.
l 0x15: No second-IF-port license is available.
l 0x16: No MPLS-TP OAM license is available.
l 0x17: No WRED license is available.
l 0x18: No AMAC license is available.
Name Meaning
l 0x19: L3 functions are restricted.
l 0x1a: No HQoS license is available.
l 0x1b: No L2DCN license is available.
l 0x1c: No ITU-T Y.1731 license is available.
l 0x1d: No LLDP license is available.
l 0x1e: No STM-1 license is available.
l 0x1f: No PoE license is available.
l 0x20: No IS3 mode license is available.
l 0x21: No IP FPM license is available.
l 0x22: The 62.5M or 125M sub-bandwidth function is restricted.
l 0x23: The 1.25 Gbit/s CPRI function is restricted.
l 0x24: The 2.5 Gbit/s CPRI function is restricted.
l 0x25: The 250M bandwidth extension function is restricted.
l 0x26: The 2048QAM function is restricted.
l 0x27: The enhanced N+1 function is restricted.
l 0x28: The total capacity over air interfaces on an NE exceeds the total
licensed capacity.
l 0x29: The number of configurable IF air interfaces exceeds the licensed
capacity.
l 0x2a: The 2048QAM function is restricted.
l 0x2b: The AES function is restricted.
l 0x2c: The 4096QAM function is restricted.
l 0x2d: The XPIC capacity on an ISM6 board exceeds the licensed capacity.
l 0x2E: The virtual master function is restricted.
l 0x2F: The virtual AP function is restricted.
l 0x30: The number of connected virtual APs exceeds the upper threshold.
l 0x32: The number of boards supporting Super Dual Band exceeds the limit
authorized by the license file.
l 0x34: The license for the bandwidth notification function is not loaded.
Possible Causes
l Cause 1: The configured capacity exceeds the licensed capacity.
l Cause 2: The configured function is unlicensed.
Procedure
Step 1 Determine the alarm cause according to alarm data on the NMS.
Step 2 Query the capacity of the license on the NMS.
Step 3 Cause 1: The configured capacity exceeds the licensed capacity.
1. Check whether the capacity suggested in the alarm data is required.
2. If yes, purchase and load the license with the desired capacity.
3. If not, rectify the capacity configuration.
Step 4 Cause 2: The configured function is unlicensed.
1. Check whether the configured function is required.
2. If yes, purchase and load the desired license.
3. If not, do not enable the function.
----End
Related Information
For TDM services, radio service capacities of NEs are calculated based on the service cross-
connections on IF boards.
A.3.128 LCS_TRIAL_PERIOD
Description
The LCS_TRIAL_PERIOD alarm indicates that an NE is in the trial period. This alarm is
reported when an NE that is powered on and does not have a license is in the trial period of 90
days.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the remaining trial period (days).
Possible Causes
Cause: An NE that is not loaded with a license is in the trial period of 90 days.
Procedure
Step 1 Purchase and load the license file.
----End
Related Information
None
A.3.129 LFA
Description
The LFA is an alarm indicating that the E1 frame alignment at the local end of the inverse
multiplexing for ATM (IMA) link in the receive direction 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicates the path ID.
Possible Causes
The possible causes of the LFA alarm are as follows:
l Cause 1: The demultiplexing module of the E1 frame cannot perform the frame
alignment function, and therefore the frame alignment loss alarms are reported. These
alarms include TU_LOP, TU_AIS, and alarm indicating that the cross-connection is not
configured.
l Cause 2: The alarmed board is faulty.
Procedure
Step 1 Cause 1: Check for the TU_LOP and TU_AIS alarms on the NMS. If these alarms occur,
handle these alarms first.
Step 2 Cause 2: The alarmed board is faulty.
1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware
failure alarm, and check whether the alarm clears.
NOTICE
If the service on the board is not protected, a cold reset on the board causes service
interruptions.
3. If the alarm persists, replace the board. For details, see 6.1 Replace the IDU.
----End
Related Information
Basic frame
As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence
(FAS) or an odd frame with non frame alignment sequence (NFAS).
A.3.130 LICENSE_LOST
Description
The LICENSE_LOST is an alarm indicating that the NE fails to detect the license file.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 Indicates the type of the license file.
l 0x02: Hybrid license
l 0x03: TDM license
l 0x06: NE license
Possible Causes
The license file is lost or is not loaded.
Procedure
Step 1 Contact Huawei engineers to reload the license file to the NE.
----End
Related Information
None
A.3.131 LMFA
Description
The LMFA is an alarm indicating the E1 multiframe alignment is lost when the E1 frame is a
CRC-4 multiframe.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicates the path ID.
Possible Causes
The possible cause of the LMFA alarm is as follows:
l Cause 1: The alarmed board is faulty.
l Cause 2: The frame format is incorrect.
Procedure
Step 1 Cause 1: The alarmed board is faulty.
1. Check whether the HARD_BAD alarm occurs on the board.
2. If the alarm occurs, perform a cold reset on the board that reports the hardware
failure alarm, and check whether the alarm clears.
NOTICE
If the service on the board is not protected, a cold reset on the board causes service
interruptions.
----End
Related Information
Basic frame
As defined in ITU-T G.704, a basic frame is an even frame with frame alignment sequence
(FAS) or an odd frame with non frame alignment sequence (NFAS).
Multiframe
A multiframe is composed of sixteen PCM frames, and can implement cyclic redundancy
check (CRC).
A.3.132 LOOP_ALM
Description
The LOOP_ALM is an alarm indicating that a loop occurs.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of loopback.
l 0x00: optical/electrical port inloop
l 0x01: optical/electrical port outloop
l 0x02: path inloop
l 0x03: path outloop
l 0x04: loopback on the user side
l 0x05: loopback on the multiplexing side
l 0x06: SPI inloop
l 0x07: SPI outloop
l 0x08: ATM layer inloop
l 0x09: ATM layer outloop
l 0x0A: PHY layer inloop
l 0x0B: PHY layer outloop
l 0x0C: MAC layer inloop
l 0x0D: MAC layer outloop
l 0x0E: VC-4 timeslot inloop
l 0x0F: VC-4 timeslot outloop
l 0x10: VC-3 timeslot inloop
l 0x11: VC-3 timeslot outloop
l 0x12: VC-12 timeslot inloop
l 0x13: VC-12 timeslot outloop
l 0x14: IF outloop
l 0x15: IF inloop
l 0x16: RF inloop
l 0xFF: any of the preceding loopback modes
Possible Causes
Cause 1: A loop is performed on the local NE.
Procedure
Step 1 Cause 1: A loop is performed on the local NE.
1. Determine the type of loopback according to the alarm parameter.
2. Find out the cause of the loopback, and set the loopback status of the alarmed port to
Non-Loopback.
----End
Related Information
None
A.3.133 LP_CROSSTR
Description
The LP_CROSSTR is an alarm indicating that the lower order path error crosses the
threshold. This alarm occurs when the board detects that the performance event that the lower
order path error crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.
l 0x90: LPBBE
l 0x91: LPES
l 0x92: LPSES
l 0x93: LPFEBBE
l 0x94: LPFEES
l 0x95: LPFESES
l 0x96: LPUAS
l 0x8e: LPFEUAS
Possible Causes
Cause 1: The lower order path error crosses the preset threshold.
Procedure
Step 1 Cause 1: The lower order path error crosses the preset threshold.
1. Check the threshold crossing records to find out the performance event that the lower
order path error crosses the preset threshold.
2. Handle the threshold-crossing performance event.
----End
Related Information
None
A.3.134 LP_R_FIFO
Description
The LP_R_FIFO is an alarm indicating that the FIFO overflows on the receive side of the
lower order path.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The clock of the local NE is not synchronized with the clock of the opposite
NE.
l Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The clock of the local NE is not synchronized with the clock of the opposite NE.
1. Browse current performance events, and check whether the performance event of TU
pointer justification occurs on the local NE and the opposite NE.
If... Then...
The TU pointer justification Handle the performance event. For details, see
occurs B.3.38 TUPJCHIGH, TUPJCLOW, and
TUPJCNEW.
If... Then...
The TU pointer justification does Go to Cause 2.
not occur
----End
Related Information
None
A.3.135 LP_RDI
Description
The LP_RDI is an alarm indicating the lower order path remote receive failure. This alarm
occurs when the board detects that bit 8 of byte V5 is 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote receive failure.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote receive failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None
A.3.136 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 occurs when the board detects that bit 8 of byte V5 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that
data reception fails at the remote end of a lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that
data reception fails at the remote end of a lower order path.
1. Handle the alarm of the lower order path on the remote site.
----End
Related Information
None
A.3.137 LP_REI
Description
The LP_REI is an alarm indicating the lower order path remote error. This alarm occurs when
the board detects that bit 3 of V5 is 1.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote errors.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote errors.
1. Handle the LP_BBE performance event on the opposite NE.
----End
Related Information
None
A.3.138 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 occurs when the board detects that bit 3 of byte V5 is 1.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
Cause 1: The local site receives a message from the remote site, and the message says that
there are bit errors in the lower order path.
Procedure
Step 1 Cause 1: The local site receives a message from the remote site, and the message says that
there are bit errors in the lower order path.
1. Handle the LPBBE performance event of the remote site.
----End
Related Information
None
A.3.139 LP_RFI
Description
The LP_RFI is an alarm indicating the lower order path remote failure. This alarm occurs
when the board detects that bit 4 of V5 is 1.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote failure.
Procedure
Step 1 Cause 1: The local NE detects the message that is returned by the opposite NE and indicates
the lower order path remote failure.
1. Handle the lower order path alarm on the opposite NE.
----End
Related Information
None
A.3.140 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 when the board detects a signal label mismatch between the
V5 bytes.
Attribute
Parameters
None
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match with the signal label contained in the V5 byte that is transmitted by the remote site.
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match with the signal label contained in the V5 byte that is transmitted by the remote site.
1. Modify the signal label contained in the V5 byte that is to be received by the local site or
is to be transmitted by the remote site. Ensure that the signal labels at both ends match
with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None
A.3.141 LP_SLM_VC12
Description
The LP_SLM_VC12 is an alarm indicating that a mismatched signal label is detected in the
lower order path. This alarm is reported when the board detects a signal label mismatch
between the V5 bytes.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match with the signal label contained in the V5 byte that is transmitted by the remote site.
Procedure
Step 1 Cause 1: The signal label contained in the V5 byte that is received by the local site does not
match with the signal label contained in the V5 byte that is transmitted by the remote site.
1. Modify the signal label contained in the V5 byte that is to be received by the local site or
is to be transmitted by the remote site. Ensure that the signal labels at both ends match
with each other. For details, see Configuring VC-12 POHs.
----End
Related Information
None
A.3.142 LP_T_FIFO
Description
The LP_T_FIFO is an alarm indicating that the FIFO overflows on the transmit side of the
lower order path.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The frequency offset of the input signal is very large.
l Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The frequency offset of the input signal is very large.
1. Use an SDH analyzer to check whether the frequency offset of the input signal is within
50 ppm.
If... Then...
The frequency offset is very large Troubleshoot the remote site.
The frequency offset is within 50 ppm Go to Cause 2.
----End
Related Information
None
A.3.143 LP_TIM
Description
The LP_TIM is an alarm indicating a mismatched trace identifier is detected in the lower
order path. This alarm is reported when the board detects a mismatch between the J2 bytes at
both ends.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to
be transmitted by the remote site.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
transmitted by the remote site.
1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.
Alternatively, set the J2 byte to be received by the local site to match with the J2 byte to
be transmitted by the remote site. For details, see Configuring VC-12 POHs.
----End
Related Information
None
A.3.144 LP_TIM_VC12
Description
The LP_TIM_VC12 is an alarm indicating a mismatched trace identifier is detected in the
lower order path. This alarm is reported when the board detects a mismatch between the J2
bytes at 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
l Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to
be transmitted by the remote site.
l Cause 2: The data configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The J2 byte to be received by the local site does not match with the J2 byte to be
transmitted by the remote site.
1. Set the byte mode of the J2 byte to be received by the local site to the disable mode.
Alternatively, set the J2 byte to be received by the local site to match with the J2 byte to
be transmitted by the remote site. For details, see Configuring VC-12 POHs.
1. Check whether the cross-connections of the intermediate nodes where the service travels
are configured correctly. If not, reconfigure the cross-connections. For details, see
Querying TDM Services.
----End
Related Information
None
A.3.145 LP_UNEQ
Description
The LP_UNEQ is an alarm indicating that the lower order path is unequipped. This alarm is
reported when the board detects that the V5 byte signal label is 0.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
The data configuration is incorrect.
l Cause 1: The tributary path at the local site is configured with services, but the tributary
path at the remote site is not configured with services.
l Cause 2: The cross-connection configuration at the intermediate nodes is incorrect.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path
at the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with services. For
details, see Querying TDM Services.
If... Then...
The tributary path at the remote site is not Configure services for the tributary
configured with services path at the remote site.
If... Then...
The tributary path at the remote site is Go to Cause 2.
configured with services
----End
Related Information
None
A.3.146 LP_UNEQ_VC12
Description
The LP_UNEQ_VC12 is an alarm indicating that the VC-12 path is unequipped. This alarm
occurs when the 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
The data configuration is incorrect.
l Cause 1: The tributary path at the local site is configured with services, but the tributary
path at the remote site is not configured with services.
Procedure
Step 1 Cause 1: The tributary path at the local site is configured with services, but the tributary path
at the remote site is not configured with services.
1. Check whether the tributary path at the remote site is configured with services. For
details, see Querying TDM Services.
If... Then...
The tributary path at the remote site is not configured with Configure services.
services
The tributary path at the remote site is configured with Go to Cause 2.
services
----End
Related Information
None
A.3.147 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 with each other.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the protection group.
Name Meaning
Parameter 2 Indicates the ID of the alarmed protection group. For example, 0x01 indicates
that the alarm is reported by protection group 1.
Possible Causes
Cause 1: The linear MSP is configured incorrectly.
The LPS_UNI_BI_M alarm is generated only when the following conditions are met:
l The switching modes (single-ended or dual-ended) at the local and remote sites 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 a restructure protocol.
Procedure
Step 1 Cause 1: The linear MSP is configured incorrectly.
1. Change the MSP switching modes at both ends, and ensure that they are the same. For
details, see Querying the Status of the Linear MSP.
----End
Related Information
None
A.3.148 LPT_CFG_CLOSEPORT
Description
The LPT_CFG_CLOSEPORT is an alarm indicating that the LPT closes the access port of the
local NE. Upon detecting that the convergence port of the local NE or the access port of the
remote NE is faulty, the LPT automatically closes the access port of the local NE. Then, the
LPT_CFG_CLOSEPORT alarm is reported.
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
Name Meaning
Parameter 1, Parameter 2 Indicates the board ID.
Possible Causes
l Cause 1: The convergence port of the local NE or the access port of the remote NE is
faulty.
Procedure
Step 1 Cause 1: The convergence port of the local NE or the access port of the remote NE is faulty.
1. Check whether the convergence port of the local NE, the access port and the
convergence port of the remote NE report the ETH_LOS alarm or other alarms related
to boards and optical modules.
2. If yes, clear these alarms. Then, check whether the LPT_CFG_CLOSEPORT alarm is
cleared.
----End
Related Information
None
A.3.149 LSR_BCM_ALM
Description
The LSR_BCM_ALM is an alarm indicating a threshold-crossing of the bias current of a
laser. This alarm is reported when the bias current of a laser exceeds the threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: The laser is aged.
l Cause 2: The laser is faulty.
Procedure
Step 1 Browse alarms on the NMS and determine the board that reports the alarm.
Step 2 Replace the pluggable optical module. For details, see Replacing Pluggable Optical
Modules.
----End
Related Information
None
A.3.150 LSR_NO_FITED
Description
The LSR_NO_FITED is an alarm indicating that the SFP optical module is not installed.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The laser of the local site is not installed.
l Cause 2: The optical module is faulty.
Procedure
Step 1 Cause 1: The SFP optical module of the local site is not installed.
1. Find out why the SFP optical module is not installed, and contact Huawei technical
support engineers for the installation. If SFP module is not needed, see Configuring an
SFP Port to delete this port.
Step 2 Cause 2: The optical module is faulty.
1. 6.3 Replacing the SFP.
----End
Related Information
None
A.3.151 LSR_WILL_DIE
Description
The LSR_WILL_DIE is an alarm indicating that the laser is to stop working.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The laser is aged.
l Cause 2: The detection circuit of the board is faulty.
Procedure
Step 1 Cause 1: The laser is aged.
1. 6.3 Replacing the SFP.
Step 2 Cause 2: The detection circuit of the board is faulty.
1. Replacing the alarm Board.
----End
Related Information
None
A.3.152 LTI
Description
The LTI is an alarm indicating that the synchronization sources are lost. This alarm is reported
when all the synchronization sources for the NE are 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 0x01: system priority list
Possible Causes
l Cause 1: The clock configuration is incorrect.
l Cause 2: All the clock sources in the clock source priority table fail.
l Cause 3: A fiber cut or a cable cut occurs.
l Cause 4: The synchronization source is set to the manual reversion mode.
l Cause 5: No input is available from the external clock source.
l Cause 5: The NE is faulty.
Procedure
Step 1 Cause 1: The clock configuration is incorrect.
1. Check whether the data in the clock source priority table meets the network planning
requirement. For details, see Querying the Clock Synchronization Status.
If... Then...
The configuration is incorrect Correct the configuration.
The configuration is correct Go to Cause 2.
Step 2 Cause 2: All the clock sources in the clock source priority table fail.
1. Troubleshoot the synchronization sources based on the clock source priority table.
Handle the alarm that occurs on the NE.
Step 4 Cause 4: The synchronization source is set to the manual reversion mode.
1. See Modifying the Recovery Parameter of the Clock Source, and set the clock source to
the automatic reversion mode.
----End
Related Information
None
A.3.153 MAC_EXT_EXC
Description
The MAC_EXT_EXC alarm indicates that the number of bit errors at the MAC layer crosses
the threshold.
Attribute
Parameters
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the threshold crossing type.
l 0x01: ETHDROP threshold crossing
l 0x02: ETHEXCCOL threshold crossing
l 0x03: RXBBAD threshold crossing
Possible Causes
l Cause 1: ETHDROP threshold crossing. The number of packet loss events crosses the
upper threshold.
l Cause 2: ETHEXCCOL threshold crossing. The number of frames unsuccessfully
transmitted after successive collisions crosses the upper threshold.
l Cause 3: RXBBAD threshold crossing. The number of bytes in received bad packets
crosses the upper threshold.
Procedure
Step 1 Check whether the working modes of the ports at the transmit and receive ends are the same.
1. On the NMS, query the working modes of the ports at the transmit and receive ends.
If... Then...
The ports at the transmit and Set the working modes of the ports at the
receive ends work in different transmit and receive ends to full-duplex or auto-
modes or in half-duplex mode negotiation. Ensure that the working modes of
the ports at the transmit and receive ends are the
same. For details, see Setting the Basic
Attributes of Ethernet Ports.
The ports at the transmit and Go to the next step.
receive ends work in the same
mode and neither port works in
half-duplex mode.
Step 2 Handle the problem that the opposite site transmits packets abnormally.
----End
Related Information
None
A.3.154 MAC_FCS_EXC
Description
The MAC_FCS_EXC alarm indicates that the software detects that the number of bit errors at
the MAC layer crosses the threshold. The software periodically detects the number of bytes
received by the MAC chip and the number of bytes that have bit errors. The MAC_FCS_EXC
alarm is reported when the number of bit errors crosses the threshold.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x00: indicates that a performance threshold is crossed.
l 0x01: indicates bit-error-triggered switching.
Possible Causes
l Cause 1: The performance of the line signals degrades.
l Cause 2: The input optical power is abnormal.
l Cause 3: A fiber connector is dirty.
Procedure
Step 1 Cause 1: The performance of the line signals degrades.
1. On the NMS, check for a LOOP_ALM alarm. If there is any, clear it. For details, see 8.4
Software Loopback.
2. If the MAC_FCS_EXC alarm persists, check whether the NMS is under a denial-of-
service (DOS) attack. If yes, eliminate the source that transmits a large amount of invalid
data, and then check whether the MAC_FCS_EXC alarm is cleared.
3. If the MAC_FCS_EXC alarm persists, check whether a cable or fiber is faulty. Replace
the faulty cable or fiber, and then check whether the MAC_FCS_EXC alarm is cleared.
Step 2 Cause 2: The input optical power is abnormal.
1. Check whether the alarmed port reports an IN_PWR_ABN alarm as well.
----End
Related Information
None
A.3.155 MAC_FCS_SD
Description
The MAC_FCS_SD alarm indicates that bit errors detected at the MAC layer exceed the
threshold. NE software periodically detects the number of bytes received by MAC chips and
the bytes that contain bit errors, and check the number of bit errors against the signal degrade
(SD) threshold. This alarm is reported if bit errors cross the threshold.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: Line signals degrade.
l Cause 2: Input optical power is abnormal.
l Cause 3: Fiber connectors are dirty.
Procedure
Step 1 Cause 1: Line signals degrade.
1. On the NMS, check whether a LOOP_ALM alarm is reported. If a LOOP_ALM alarm
is reported, clear it. For details, see 8.4 Software Loopback.
2. If the MAC_FCS_SD alarm persists, check whether any source unexpectedly sends a
large amount of data, such as DOS attacks. If yes, eliminate the data source.
3. If the alarm persists, check whether the cable or fiber is faulty. If the cable or fiber is
faulty, replace the faulty cable or fiber.
----End
Related Information
None
A.3.156 MOD_COM_FAIL
Description
The MOD_COM_FAIL is an alarm indicating that Module communicates abnormally.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 0x11 indicates that the communication between the system control unit and
packet switching unit is failed.
Possible Causes
l Cause 1: The software processing of the related modules of the NE is faulty.
l Cause 2: The NE hardware is faulty.
Procedure
Step 1 6.1 Replace the IDU.
----End
Related Information
None
A.3.157 MP_DELAY
Description
The MP_DELA is an alarm indicating a delay of the Multi-link Point-to-Point (ML-PPP)
group. This alarm is reported when the differential delay between MP group members
exceeds the threshold.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The signal quality of the MP group members deteriorates.
Procedure
Step 1 Cause 1: The signal quality of the MP group members deteriorates.
1. Check whether the network is congested. If yes, expand the network and then check
whether the alarm is cleared.
2. If the alarm persists, replace the cable connecting to the port that reports the alarm. Then,
check whether the alarm is cleared.
Step 2 Cause 2: The maximum differential delay is configured low.
1. Check whether the maximum differential delay is configured properly on the NMS. For
details, see Creating MP Groups.
2. If the maximum differential delay is configured low, increase the value based on the
actual situation or disable the fragment function.
----End
Related Information
None
A.3.158 MP_DOWN
Description
The MP_DOWN is an alarm indicating a failure of the Multi-link Point-to-Point (ML-PPP)
group. This alarm is reported when the number of the valid activated MP group members is
less than that of the specified minimum activated links. The minimum activated links is 1 by
default.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The number of the valid activated MP group members is less than that of the
minimum activated links.
l Cause 2: The configurations at both ends of the MP group are inconsistent.
l Cause 3: The NCP protocol on the member links of the MP group is running improperly.
l Cause 4: The physical link is interrupted.
l Cause 5: The MP group is not configured with an IP address or a subnet mask.
Procedure
Step 1 Cause 1: The number of the valid activated MP group members is less than that of the
minimum activated links.
1. On the NMS, check whether the number of the valid activated MP group members is less
than that of the minimum activated links. For details, see Querying the MP Group
Protocol Information.
2. If the number is less than that of the minimum activated links, change the minimum
activated links to a value less than the number of configured MP group members.
Step 2 Cause 2: The configurations at both ends of the MP group are inconsistent.
1. On the NMS, check whether the configurations at both ends of the MP group are
consistent. If not, modify the parameters. For details, see Creating MP Groups.
Step 3 Cause 3: The NCP protocol on the member links of the MP group is running improperly.
1. On the NMS, check whether the PPP_LCP_FAIL or PPP_NCP_FAIL alarm exists on
the member links of the MP group.
2. If yes, clear the PPP_LCP_FAIL or PPP_NCP_FAIL alarm immediately. Then, check
whether the MP_DOWN alarm is cleared.
1. On the NMS, check whether a signal alarm such as R_LOS or T_ALOS exists on the
member links of the MP group.
2. If yes, clear the R_LOS or T_ALOS alarm immediately.
Step 5 Cause 5: The MP group is not configured with an IP address or a subnet mask.
1. Configure an IP address and a subnet mask for the MP group. For details, see Creating
MP Groups.
----End
Related Information
None
A.3.159 MPLSLDPSESSIONDOWN
Description
The MPLSLDPSESSIONDOWN alarm indicates the interruption of an LDP session.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameters 1-4 Indicate the peer LSR ID.
Possible Causes
l Cause 1: Parameters configured for the service interfaces are incorrect.
l Cause 2: The LDP configurations at both ends are inconsistent.
l Cause 3: The link between the local NE and its neighbor NE is faulty.
l Cause 4: The neighbor NE is faulty.
Procedure
Step 1 Cause 1: Parameters configured for the service interfaces are incorrect.
1. Check whether parameters configured for interfaces at both ends are correct, for
example, whether the interfaces are enabled and whether the interface IP addresses
match.
Step 3 Cause 3: The link between the local NE and its neighbor NE is faulty.
1. Check whether the link between the local NE and its neighbor NE is faulty. For example,
check whether the ETH_LOS alarm is reported at the local end. If yes, clear the
ETH_LOS alarm first.
----End
Related Information
None
A.3.160 MPLSLSP_TBL_LACK
Description
The MPLSLSP_TBL_LACK alarm indicates that MPLS label resources are deficient. This
alarm is reported when MPLS label resources are deficient because the number of MPLS
LSPs exceeds equipment specifications.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameter 1 Indicates the LSP type. This parameter takes the fixed value of 0x01
(LDP LSP).
Name Meaning
Parameter 2 Indicates an ingress or egress label.
l 0x01: ingress label
l 0x02: egress label
Parameters 3-6 Indicate the label value.
Parameters 7-10 Indicate the VRF ID, which is used to identify an L3 VPN instance.
Possible Causes
Cause: The policy to set up LDP LSPs is incorrect, which causes the occupation of lots of
MPLS label resources.
Procedure
Step 1 Check whether the setup of LDP LSPs is triggered by host routes. If no, modify the
configuration.
Step 2 If the the LDP LSP setup policy is correct, re-plan services.
----End
Related Information
None
A.3.161 MPLS_PW_AIS
Description
The MPLS_PW_AIS is an alarm indicating a defect in the forward direction of a PW. This
alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault occurs
on the tunnel at the server layer of the PW.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs.
Procedure
Step 1 Cause 1: The MPLS-TP OAM is incorrectly configured for tunnels between upstream NEs.
1. Check whether the MPLS-TP OAM is configured correctly for tunnels between the local
NE and its upstream NEs. If not, modify the configuration. For details, see Configuring
MEP Parameters for MPLS-TP PW OAM.
Step 2 Cause 2: An upstream NE detects a fault on the tunnel at the PW server layer.
1. Check whether a tunnel fault occurs on the S-PE. If an alarm such as
MPLS_TUNNEL_LOCV exists, clear the alarm immediately.
----End
Related Information
None
A.3.162 MPLS_PW_CSF
Description
The MPLS_PW_CSF alarm indicates that client signals fail at the peer end of a PW. This
alarm is reported when one end of a PW receives Client Signal Fail (CSF) OAM packets from
the peer end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
Procedure
Step 1 Cause 1: A link or hardware is faulty on the UNI side of the peer NE.
1. Check whether the peer NE reports any link- or hardware-related alarm on the UNI side.
If yes, clear the alarm.
Possible alarms include:
Link-related alarm: ETH_LOS
Hardware-related alarm: BD_STATUS, HARD_BAD
Alarm related to the IEEE 802.3ah protocol: ETH_EFM_DF,
ETH_EFM_LOOPBACK
----End
Related Information
None
A.3.163 MPLS_PW_BDI
Description
The MPLS_PW_BDI is an alarm of PW backward defect indication. This alarm occurs when
the local NE receives the BDI packet, notifying that the remote NE detects that the PW is
faulty.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: The remote NE detects that the PW is faulty.
Procedure
Step 1 Cause 1: The remote NE detects that the PW is faulty.
If... Then...
A board on the remote NE is reset or faulty Rectify the fault on the remote NE.
The physical link between the local NE and the Rectify the fault on the physical link.
remote NE is faulty
The bandwidth allocated to the PW is fully Increase the bandwidth of the PW.
occupied.
----End
Related Information
None
A.3.164 MPLS_PW_Excess
Description
The MPLS_PW_Excess is an alarm indicating that excessive trail termination source
identifiers (TTSIs) are received on the PW. This alarm occurs when five or more correct
CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Parameters
None
Possible Causes
l Cause 1: Multiple PWs are configured with the same label and PW ID.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple PWs are configured with the same label and PW ID.
1. Check whether multiple PWs are configured with the same label and PW ID.
2. If yes, delete the redundant PWs or change the PW ID and label of each PW to unique
values.
3. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
----End
Related Information
None
A.3.165 MPLS_PW_LCK
Description
The MPLS_PW_LCK alarm indicates that a server layer tunnel is administratively locked.
This alarm is reported when the MEP receives a LCK message.
Attribute
Parameters
None
Possible Causes
Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for a tunnel-layer MEP.
1. Check whether tunnel locking is enabled on the nodes along the PW path. If yes, disable
the CLK after administrative locking (for diagnostic testing or other administrative
purpose) is no longer needed.
----End
Related Information
None
A.3.166 MPLS_PW_LOCK
Description
The MPLS_PW_LOCK alarm indicates that the locked signal function (LCK) is enabled for
the PW layer.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: Administrative locking is enabled for the PW layer.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the PW layer.
1. Check whether the LCK is enabled for the PW layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no
longer needed.
----End
Related Information
None
A.3.167 MPLS_PW_LOCV
Description
The MPLS_PW_LOCV is an alarm of PW connectivity loss. This alarm occurs when no
expected CV/FFD packets are received within three consecutive CV/FFD periods.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
l Cause 2: The OAM is different between the ends of the PW.
l Cause 3: The PW that carries services is faulty.
l Cause 4: The remote NE of the PW is faulty.
l Cause 5: The service interface is configured incorrectly.
l Cause 6: Serious congestion occurs on the network.
Procedure
Step 1 Cause 1: The remote NE of the PW stops transmitting CV/FFD packets.
1. Check whether the remote NE of the PW stops transmitting CV/FFD packets.
If... Then...
The remote NE of the PW stops transmitting Enable the CV/FFD detection and
CV/FFD packets then check whether the alarm clears.
The remote NE of the PW keeps transmitting Go to Cause 2.
CV/FFD packets
Step 2 Cause 2: The OAM is different between the ends of the PW.
1. Check whether the OAM is different between the ends of the PW. If no, Setting PW
OAM (Y.1711) Parameters according to the plan. If yes, go to cause 3.
Step 3 Cause 3: The PW that carries services is faulty.
1. Check whether the local NE and remote NE of the PW report any alarm related to
boards. If yes, clear the alarm. Then, check whether the MPLS_PW_LOCV alarm is
cleared.
2. Check whether any link-related alarm is reported. If yes, clear the alarm. Then, check
whether the MPLS_PW_LOCV alarm is cleared.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 4.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 5.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 6.
----End
Related Information
None
A.3.168 MPLS_PW_MISMATCH
Description
The MPLS_PW_MISMATCH is an alarm indicating that the trail termination source
identifiers (TTSIs) on the PW do not match with the specified one. This alarm occurs when
only the packets with wrong TTSIs are received within three consecutive CV/FFD periods.
Attribute
Parameters
None
Possible Causes
l Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The ingress node or egress node of the faulty PW is configured incorrectly.
1. Check whether the ingress node and egress node of the faulty PW are configured
correctly according to NE planning.
2. If the ingress node or egress node is configured incorrectly, correct the configuration and
then check whether the alarm clears.
----End
Related Information
None
A.3.169 MPLS_PW_MISMERGE
Description
The MPLS_PW_MISMERGE is an alarm indicating that the trail termination source
identifiers (TTSIs) are mismerged on the PW. This alarm is reported if the CV/FFD packets
with correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFD
periods.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The PW is configured incorrectly.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The PW is configured incorrectly.
1. Check whether the PW are configured correctly according to NE planning.
2. If the PW is configured incorrectly, correct the configuration and then check whether the
alarm clears.
----End
Related Information
None
A.3.170 MPLS_PW_OAMFAIL
Description
The MPLS_PW_OAMFAIL is an alarm indicating a failure of the OAM protocol negotiation.
This alarm is reported when the OAM protocol negotiation fails on NEs at both ends of the
PW.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: The OAM function is enabled only on the NE at one end of the PW.
NOTE
Only the NE that is enabled with the OAM function reports the MPLS_PW_OAMFAIL alarm.
Cause 2: The PW has been interrupted when enabling the OAM function.
NOTE
When the PW is interrupted in the forward or reverse direction, the peer or local NE reports the
MPLS_PW_OAMFAIL alarm.
Procedure
Step 1 Cause 1: The OAM function is enabled only on the NE at one end of the PW.
1. On the NMS, query this alarm and check whether the OAM function is enabled on NEs
at both ends of the PW. If the OAM function is enabled only on one NE, set OAM
Status to Enabled on the other NE.
Step 2 Cause 2: The PW has been interrupted when enabling the OAM function.
1. On the NMS, check whether tunnel-related alarms such as A.3.186
MPLS_TUNNEL_OAMFAIL occur on NEs at both ends of the PW. If yes, clear them
immediately.
2. Check whether service-related alarms such as A.3.167 MPLS_PW_LOCV occur on
NEs at both ends of the PW. If yes, clear them immediately.
----End
Related Information
None
A.3.171 MPLS_PW_RDI
Description
The MPLS_PW_RDI is an alarm indicating a defect in the backward direction of a PW. The
local MEP sends an RDI packet to the remote MEP when detecting a PW fault. The
MPLS_PW_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Parameters
None
Possible Causes
The local MEP NE detects a PW fault.
Procedure
Step 1 Handle the PW fault according to the MPLS-TP OAM-related alarm reported by the remote
MEP.
Step 2 If the alarm persists, check whether the physical link between faulty NEs is faulty. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical
fiber or cable.
Step 3 Check whether the bandwidth allocated to the PW is used up. If yes, increase the bandwidth
allocated to the PW.
----End
Related Information
None
A.3.172 MPLS_PW_SD
Description
The MPLS_PW_SD is an alarm of signal degrade on the PW. This alarm is reported when the
packet loss rate of the connectivity check (CC) crosses the SD threshold but is lower than the
SF threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large
amount of invalid data. Then, check whether the MPLS_PW_SD alarm is cleared.
Step 2 Cause 2: The physical port has bit errors or packet loss.
1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.
Step 3 Cause 3: The fiber connector or the optical module is dirty.
1. Clean the fiber connector or the optical module. For details, see Checking and cleaning
fiber connectors.
----End
Related Information
None
A.3.173 MPLS_PW_SF
Description
The MPLS_PW_SF is an alarm of signal failure on the PW. This alarm occurs when the
number of received connectivity check (CC) packets is less than the signal failure (SF)
threshold.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The bandwidth of the PW is fully occupied.
l Cause 2: The physical port has bit errors or packet loss.
l Cause 3: The fiber connector or the optical module is dirty.
Procedure
Step 1 Cause 1: The bandwidth of the PW is fully occupied.
1. Check whether the bandwidth allocated to the faulty PW is fully occupied.
2. If yes, increase the bandwidth of the PW or eliminate the sources that transmit a large
amount of invalid data. Then, check whether the MPLS_PW_SF alarm is cleared.
Step 2 Cause 2: The physical port has bit errors or packet loss.
1. Check whether the fiber connector is loose. If yes, insert the fiber connector securely.
Step 3 Cause 3: The fiber connector or the optical module is dirty.
1. Clean the fiber connector or the optical module. For details, see Checking and cleaning
fiber connectors.
----End
Related Information
None
A.3.174 MPLS_PW_UNEXPMEG
Description
The MPLS_PW_UNEXPMEG is an alarm indicating that the MEP receives a packet with
correct MEG level but incorrect MEG ID.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
l Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
Procedure
Step 1 Cause 1: MEG IDs configured on NEs at both ends of the PW are different.
1. Check whether the PW configurations are consistent between NEs at both ends of the
PW. MEG IDs on NEs at both ends of a PW must be set to the same value. For details,
see Querying Information and Running Status of PWs.
Step 2 Cause 2: The PW is configured incorrectly. Multiple PWs use the same label.
1. Check whether the PW label is configured correctly. If multiple PWs use the same label,
reconfigure the PW label. For details, see Querying Information and Running Status of
PWs.
----End
Related Information
None
A.3.175 MPLS_PW_UNEXPMEP
Description
The MPLS_PW_UNEXPMEP is an alarm indicating an error in the PW OAM CCM
information. This alarm is reported when the sink NE of the PW receives a CCM packet with
an unexpected MEP ID.
Attribute
Parameters
None
Possible Causes
MEP IDs are inconsistent between NEs at both ends of a PW.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of a PW.
1. Check whether the remote MEP ID on the source NE is correctly configured with the
MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None
A.3.176 MPLS_PW_UNEXPPER
Description
The MPLS_PW_UNEXPPER is an alarm indicating that the PW does not receive the CCM
packet in the expected period. This alarm is reported when the sink NE of the PW receives a
CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected period. For
example, the transmit interval configured on the source and sink NEs is 10 ms, but the sink
NE receives the CCM packet from the source NE after 20 ms.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the
PW.
Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the
PW.
1. Check whether PW configurations are consistent between the source and sink NEs. CCM
packet periods on NEs at both ends of a PW must be set to the same value. For details,
see Querying Information and Running Status of PWs.
----End
Related Information
None
A.3.177 MPLS_PW_UNKNOWN
Description
The MPLS_PW_UNKNOWN is an alarm of unknown defects on the PW. This alarm occurs
when the connectivity check (CC) packets of unexpected types, periods, and values are
received within three consecutive periods.
Attribute
Parameters
None
Possible Causes
Cause 1: The PW OAM configuration at the two ends is different.
Procedure
Step 1 Cause 1: The PW OAM configuration at the two ends is different.
1. Change the PW OAM configuration to the same at the two ends.
----End
Related Information
None
A.3.178 MPLS_TUNNEL_AIS
Description
The MPLS_TUNNEL_AIS is an alarm indicating a defect in the forward direction of a tunnel.
This alarm is reported when the Ethernet port receives an AIS packet, indicating that a fault
occurs on the physical link at the server layer of the tunnel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
An upstream NE detects a fault on the physical link at the server layer of the tunnel.
Procedure
Step 1 An upstream NE detects a fault on the physical link at the server layer of the tunnel.
1. Check whether the physical link is faulty between the local NE and the upstream NE.
Physical link faults may be caused by a fiber cut, a faulty optical module, or a faulty NE.
If yes, rectify the faults.
----End
Related Information
None
A.3.179 MPLS_TUNNEL_BDI
Description
The MPLS_TUNNEL_BDI is an alarm of tunnel backward defect indication. This alarm
occurs when the port of the local NE receives the backward defect indication (BDI) packet,
notifying that the opposite NE detects that the tunnel is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: The opposite NE detects MPLS alarms.
Procedure
Step 1 Cause 1: The opposite NE detects MPLS alarms.
1. Clear the MPLS alarms reported on the opposite NE.
----End
Related Information
None
A.3.180 MPLS_TUNNEL_EXCESS
Description
The MPLS_TUNNEL_EXCESS is an alarm indicating that excessive trail termination source
identifiers (TTSIs) are received in the tunnel. This alarm occurs when the Ethernet port of the
local NE receives five or more correct CV/FFD packets within three consecutive CV/FFD
periods.
Attribute
Parameters
None
Possible Causes
l Cause 1: Physical links are misconnected.
Procedure
Step 1 Cause 1: Physical links are misconnected.
1. Check whether any fiber or cable is misconnected between the two ends. If yes,
reconnect the fiber or cable.
----End
Related Information
None
A.3.181 MPLS_TUNNEL_FDI
Description
The MPLS_TUNNEL_FDI alarm indicates a tunnel forward defect. This alarm is reported
when the local NE receives the forward defect indication (FDI) packet, notifying that the
upstream tunnel at the physical layer is faulty.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameters 1 to 4 Indicate the IP address of the node where the fault occurs.
Possible Causes
Cause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.
Procedure
Step 1 Cause 1: The upstream NE detects that the physical link that carries the tunnel is faulty.
If... Then...
The link-related alarms, such as MW_BER_EXC, MW_BER_SD, Clear these alarms
MW_FEC_UNCOR and MW_LOF, are reported first.
The transmit board of the local NE reports hardware-related Clear these alarms
alarms (alarms on the optical modules or boards), such as first.
HARD_BAD and LSR_NO_FITED
----End
Related Information
None
A.3.182 MPLS_TUNNEL_LOCV
Description
The MPLS_TUNNEL_LOCV is an alarm of tunnel connectivity loss. This alarm occurs when
the port of the local NE fails to receive expected CV/FFD packets within three CV/FFD
periods. (The expected CV/FFD packets must carry correct TTSIs and have the correct type,
period, and value.)
Attribute
Parameters
None
Possible Causes
l Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection
packet type and detection packet period, differ at the two ends.
l Cause 2: Severe congestion occurs on the network.
l Cause 3: A certain board is faulty.
l Cause 4: The physical link between the two ends is faulty.
Procedure
Step 1 Cause 1: In detection mode of manual, the MPLS OAM settings, such as detection packet
type and detection packet period, differ at the two ends.
1. Check whether the MPLS OAM settings are the same at the two ends.
2. If the MPLS OAM settings are different at the two ends, change them to the same.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 3.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to the next step.
2. Check whether the local NE and the remote NE report alarms related to optical modules
or boards, such as HARD_BAD and LSR_NO_FITED. If yes, clear these alarms first.
3. Then, check whether the MPLS_TUNNEL_LOCV alarm clears.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Go to Cause 4.
Step 4 Cause 4: The physical link between the two ends is faulty.
1. Check whether any fiber or cable is damaged. If yes, replace the damaged fiber or cable.
----End
Related Information
None
A.3.183 MPLS_TUNNEL_LOCK
Description
The MPLS_TUNNEL_LOCK alarm the locked signal function (LCK) is enabled for a tunnel.
Attribute
Parameters
None
Possible Causes
Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
Procedure
Step 1 Cause 1: Administrative locking is enabled for the tunnel layer on the source MEP.
1. Check whether the LCK is enabled for the tunnel layer. If yes, disable the CLK after
administrative locking (for diagnostic testing or other administrative purpose) is no
longer needed.
----End
Related Information
None
A.3.184 MPLS_TUNNEL_MISMATCH
Description
The MPLS_TUNNEL_MISMATCH is an alarm indicating that the trail termination source
identifiers (TTSIs) on the tunnel do not match with the specified one. This alarm is reported if
no CV/FFD packets with correct TTSIs are received in three consecutive CV/FFD periods.
Attribute
Parameters
None
Possible Causes
l Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ
at the two ends of the tunnel.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: The tunnel settings are incorrect. For example, the LSR IDs or tunnel IDs differ at
the two ends of the tunnel.
1. Check whether the tunnel settings are the same at the two ends.
If the source NE is an ingress node, Sink Node is the LSR ID of the sink NE. If the
sink NE is an egress node, Source Node is the LSR ID of the source NE.
Tunnel IDs of the source NE and sink NE of a tunnel must be set to the same.
2. If the tunnel IDs are different, change them to the same.
----End
Related Information
None
A.3.185 MPLS_TUNNEL_MISMERGE
Description
The MPLS_TUNNEL_MISMERGE is an alarm indicating that the trail termination source
identifiers (TTSIs) are mismerged in the tunnel. This alarm is reported if the CV/FFD packets
with correct TTSIs and those with wrong TTSIs are received in three consecutive CV/FFD
periods.
Attribute
Parameters
None
Possible Causes
l Cause 1: Multiple tunnels are configured with the same label.
l Cause 2: Physical links are misconnected.
Procedure
Step 1 Cause 1: Multiple tunnels are configured with the same label.
1. Check whether multiple tunnels are configured with the same label.
2. If multiple tunnels are configured with the same label, delete the redundant labels or
change the label of each tunnel to a unique value.
----End
Related Information
On the NE, the label of each MPLS tunnel is unique.
A.3.186 MPLS_TUNNEL_OAMFAIL
Description
The MPLS_TUNNEL_OAMFAIL is an alarm indicating that the OAM protocol negotiation
between the two ends of the tunnel fails.
Attribute
Parameters
None
Possible Causes
l Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one
end and is disabled on the other end.
l Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection
mode is auto-sensing.
Procedure
Step 1 Cause 1: The OAM function is enabled and the detection mode is auto-sensing on one end
and is disabled on the other end.
1. Enable the OAM function.
Step 2 Cause 2: The tunnel is unavailable when the OAM function is enabled and the detection mode
is auto-sensing.
1. Check whether the sink node of the alarmed tunnel reports the HARD_BAD,
ETH_LOS, or R_LOS alarm.
2. If yes, clear the alarm. After the OAM protocol negotiation succeeds, the
MPLS_TUNNEL_OAMFAIL alarm clears.
----End
Related Information
None
A.3.187 MPLS_TUNNEL_RDI
Description
The MPLS_TUNNEL_RDI is an alarm indicating a defect in the backward direction of a
tunnel. The local MEP sends an RDI packet to the remote MEP when detecting a tunnel fault.
The MPLS_TUNNEL_RDI alarm is reported when the remote MEP receives the RDI packet.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The local MEP NE detects a tunnel fault.
Procedure
Step 1 Handle the tunnel fault according to the MPLS-TP OAM-related alarm reported by the remote
MEP. Then, check whether the MPLS_TUNNEL_RDI alarm is cleared.
Step 2 If the alarm persists, check whether the physical link is faulty between faulty NEs. For
example, the optical fiber or cable is damaged or pressed. If yes, replace the faulty optical
fiber or cable.
----End
Related Information
None
A.3.188 MPLS_TUNNEL_SD
Description
The MPLS_TUNNEL_SD is an alarm of signal degrade on the tunnel. This alarm is reported
when the packet loss rate of the CV/FFD crosses the SD threshold but is lower than the SF
threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. If the alarm persists, proceed to cause 2.
----End
Related Information
None
A.3.189 MPLS_TUNNEL_SF
Description
The MPLS_TUNNEL_SF is an alarm indicating that the tunnel signal degrades severely. This
alarm is reported if the loss ratio of the CV/FFD packets is higher than the SF threshold and
CV/FFD packets are received in three consecutive periods.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: Excessive bit errors occur.
l Cause 2: The bandwidth of the tunnel is fully used.
Procedure
Step 1 Cause 1: Excessive bit errors occur.
1. If the MPLS_TUNNEL_SF persists, go to Cause 2.
1. On the NMS, check whether the bandwidth of the tunnel is fully used. If the bandwidth
of the tunnel is fully used, increase the bandwidth allocated to the tunnel or eliminate any
source that transmits a large amount of invalid data. Check whether the alarm is cleared.
----End
Related Information
None
A.3.190 MPLS_TUNNEL_UNEXPMEG
Description
The MPLS_TUNNEL_UNEXPMEG is an alarm indicating an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with an
unexpected MEG ID.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
l Cause 2: There are multiple tunnels with the same label between the source and sink
NEs.
Procedure
Step 1 Cause 1: MEG IDs are inconsistent between NEs at both ends of a tunnel.
1. Check whether PW configurations are consistent between the source and sink NEs. MEG
IDs must be set to the same value on NEs at both ends of a tunnel. For details, see
Querying MPLS Tunnel Information.
Step 2 Cause 2: There are multiple tunnels with the same label between the source and sink NEs.
1. Check whether there are multiple tunnels with the same label on the source and sink
NEs. If yes, reconfigure labels for tunnels. For details, see Querying MPLS Tunnel
Information.
----End
Related Information
None
A.3.191 MPLS_TUNNEL_UNEXPMEP
Description
The MPLS_TUNNEL_UNEXPMEP is an alarm indicating an error in the tunnel OAM CCM
information. This alarm is reported when the sink NE receives a CCM packet with an
unexpected MEP ID.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
MEP IDs are inconsistent between NEs at both ends of the tunnel.
Procedure
Step 1 MEP IDs are inconsistent between NEs at both ends of the tunnel.
1. Check whether the remote MEP ID on the source NE is correctly configured with the
MEP ID of the sink NE. If not, reconfigure the remote MEP ID on the source NE.
----End
Related Information
None
A.3.192 MPLS_TUNNEL_UNEXPPER
Description
The MPLS_TUNNEL_UNEXPPER is an alarm indicating that the tunnel does not receive the
CCM packet in the expected period. This alarm is reported when the sink NE of the PW
receives a CCM packet with correct MEG level, MEG ID, and MEP ID but in an unexpected
period.
For example, the transmit interval is set to 10 ms on the source and sink NEs, but the sink NE
receives the CCM packet from the source NE after 20 ms.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
CCM packet periods are inconsistent between the source and sink NEs at both ends of the
tunnel.
Procedure
Step 1 CCM packet periods are inconsistent between the source and sink NEs at both ends of the
tunnel.
1. Check whether tunnel configurations are consistent between the source and sink NEs.
CCM packet periods on NEs at both ends of a PW must be set to the same value. For
details, see Querying MPLS Tunnel Information.
----End
Related Information
None
A.3.193 MPLS_TUNNEL_UNKNOWN
Description
The MPLS_TUNNEL_UNKNOWN is an alarm indicating that certain unknown defects exist
on the tunnel. This alarm is reported when the port receives the CV packets and the FFD
packets.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The OAM settings differ at the two ends.
l Cause 2: The NE receives packets from an unknown source.
Procedure
Step 1 Cause 1: The OAM settings differ at the two ends.
1. If the MPLS_TUNNEL_UNKNOWN alarm is reported transiently, check whether
Tunnel OAM configuration is changed on the local NE and the opposite NE.
2. If the local NE and the opposite NE have different Tunnel OAM configuration, the
MPLS_TUNNEL_UNKNOWN alarm is reported transiently and then the
MPLS_TUNNEL_LOCV alarm is reported. Ensure that both ends have the same Tunnel
OAM configuration. Then, check whether the alarm is cleared.
----End
Related Information
None
A.3.194 MS_AIS
Description
The MS_AIS is an alarm indicating multiplex section alarms. This alarm is reported when the
board detects that bits 6-8 of the K2 byte in the three consecutive frames are 111.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The transmit unit of the opposite station is faulty.
l Cause 2: The receive unit of the local site is faulty.
Procedure
Step 1 Cause 1: The transmit unit of the opposite station is faulty.
1. Replace the line board at the opposite site based on the type of the alarmed board.
If... Then...
The line board reports the Replace the IDU or the line board at the opposite
alarm end.
The IF board reports the Replace the IDU or the IF board at the opposite
alarm end.
2. Replace the board and then check whether the alarm is cleared.
If... Then...
The alarm is cleared after replacement End the fault handling.
The alarm persists after replacement Go to the next step.
3. Replace the IDU or the system control, cross-connect, and timing board at the
opposite end.
If... Then...
The alarm is cleared after the board replacement End the fault handling.
The alarm persists after the board replacement Go to Cause 2.
----End
Related Information
None
A.3.195 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 when the board detects that the MS BER
performance indicator crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 2 is always 0x00. Parameter 3 indicate the ID of a
Parameter 3 performance event that causes the alarm and has the following
meanings:
l 0x10: MSBBE
l 0x11: MSES
l 0x12: MSSES
l 0x13: MSFEBBE
l 0x14: MSFEES
l 0x15: MSFESES
l 0x16: MSUAS
l 0x21: MSFEUAS
Possible Causes
l Cause 1: Services are interrupted for a long time.
l Cause 2: The MS BER performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x16:
1. Check whether fibers are properly connected. If not, connect the fibers again according
to planning information.
2. Check whether cross-connections are configured for service ports. If not, configure
cross-connections again according to planning information.
Step 2 Cause 2: The MS BER performance indicator crosses the preset threshold.
1. Check the threshold crossing records of MS BER performance events to find out the
performance event that crosses the preset threshold. For details, see 4.3.5 Browsing the
Performance Event Threshold-Crossing Records.
2. Handle the performance event that crosses the threshold.
----End
Related Information
None
A.3.196 MS_RDI
Description
The MS_RDI is an alarm indicating that data reception at the remote end of the multiplex
section fails. This alarm is reported when the board detects that bits 6-8 of the K2 byte are
110.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message
indicates that data reception at the remote end of the multiplex section fails.
Procedure
Step 1 Cause 1: The local site receives a message from the opposite station, and the message
indicates that data reception at the remote end of the multiplex section fails.
1. Rectify the fault that occurs on the opposite station.
The possible alarms are as follows:
MS_AIS
R_LOS
R_LOF
B2_EXC
B2_SD
----End
Related Information
None
A.3.197 MS_REI
Description
The MS_REI is an alarm indicating that bit errors occur on the remote end of the multiplex
section. This alarm is reported when the board detects that the M1 byte is non-zero.
Attribute
Parameters
None
Possible Causes
Cause 1: The local site receives a message from the opposite station, and the message
indicates that bit errors occur on the remote end of the multiplex section.
Procedure
Step 1 Cause 1: The local site receives a message from the opposite station, and the message
indicates that bit errors occur on the remote end of the multiplex section.
1. Handle the MS_BBE performance event on the port of the opposite station.
----End
Related Information
None
A.3.198 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 when the 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Parameter 2, Parameter 3 Indicate the ID of a performance event that causes the alarm.
l 0x2a: AUPJCHIGH
l 0x2b: AUPJCLOW
l 0x2c: AUPJCNEW
Possible Causes
Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.
Procedure
Step 1 Cause 1: An AU pointer adaptation performance indicator crosses the preset threshold.
1. Check the threshold crossing records of the AU pointer adaptation performance events to
find out the performance event that crosses the preset threshold. For details, see 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
2. Handle the performance event that crosses the threshold.
----End
Related Information
None
A.3.199 MULTI_RPL_OWNER
Description
The MULTI_RPL_OWNER is an alarm indicating that the ring network contains several
RPL_OWNER nodes.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the ID of the ERPS instance.
Possible Causes
Cause 1: The related data is configured incorrectly.
Procedure
Step 1 Cause 1: The related data is configured incorrectly.
1. Reconfigure the ERPS protection. For details, see Creating Ethernet Ring Protection
Instances.
----End
Related Information
None
A.3.200 MW_AM_TEST
Description
The MW_AM_TEST is an alarm indicating that the IF port is in the AM testing state.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause: The AM testing is enabled.
Procedure
Step 1 Cause: The AM testing is enabled.
1. After the AM testing ends, disable the AM testing.
----End
Related Information
None
A.3.201 MW_BER_EXC
Description
The MW_BER_EXC is an alarm indicating that excessive bit errors occur on the radio link.
This alarm is reported when the bit errors on the radio link exceed the specified threshold
(10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: Signal attenuation on the radio link is very heavy.
l Cause 2: The transmit unit of the opposite station is faulty.
l Cause 3: The receive unit of the local site is faulty.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power of the ODU is normal. If yes,
determine the abnormality and take proper measures. For details, see 4.4.1 Querying the
Historical Transmit Power and Receive Power
If... Then...
If... Then...
The RSL is higher than Slow up fading occurs. Follow the steps:
the specified RSL of the
network. The offset value 1. Follow instructions in 8.1.2 Scanning Interfering Signals to
is tens of decibels. The scan the frequency spectrum around the radio link and check
duration is from tens of for co-frequency interference and bias-frequency
seconds to several hours. interference.
2. Use a spectrum analyzer to analyze the interference source.
3. Contact the spectrum management department to clear the
interference spectrum or change plans to minimize the
interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may be
the specified RSL of the faulty in both directions, because slow fading is imposed by the
network. The offset value transmission path. Contact the network planning department to
is tens of decibels. The make the following changes:
duration is from tens of
seconds to several hours. l Increase the installation height of the antenna.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.
If the RSL is lower than Fast fading occurs. Contact the network planning department to
or higher than the make the following changes:
specified RSL of the
network and if the l Adjust the position of the antenna to block the reflected
duration is from several wave or make the reflection point fall on the ground that has
milliseconds to tens of a small reflection coefficient, therefore reducing the
seconds. multipath fading.
l Adjust the RF configuration to make the links in the 1+1 SD
configuration.
l If the links are configured with the 1+1 SD protection,
adjust the height offset between two antennas to make the
receive power of one antenna stronger than the receive
power of the other antenna.
l Increase the fading margin.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the opposite end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the opposite end is rectified after
the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite
end.
The fault at the opposite end is rectified End the alarm handling.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the local end is rectified after the
loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the local end.
The fault at the opposite end is rectified End the alarm handling.
----End
Related Information
None
A.3.202 MW_BER_SD
Description
The MW_BER_SD is an alarm indicating that signal deteriorates on the radio link. This alarm
is reported when the bit errors on the radio link exceed the specified threshold (10-6 by
default) but does not reach the MW_BER_EXC alarm threshold (10-3 by default).
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
None
Possible Causes
l Cause 1: Signal attenuation on the radio link is very heavy.
l Cause 2: The transmit unit of the opposite station is faulty.
l Cause 3: The receive unit of the local site is faulty.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power of the ODU is normal. If yes,
determine the abnormality and take proper measures. For details, see 4.4.1 Querying the
Historical Transmit Power and Receive Power
If... Then...
The RSL is higher than Slow up fading occurs. Follow the steps:
the specified RSL of the
network. The offset value 1. Follow instructions in 8.1.2 Scanning Interfering Signals
is tens of decibels. The to scan the frequency spectrum around the radio link and
duration is from tens of check for co-frequency interference and bias-frequency
seconds to several hours. interference.
2. Use a spectrum analyzer to analyze the interference source.
3. Contact the spectrum management department to clear the
interference spectrum or change plans to minimize the
interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may be
the specified RSL of the faulty in both directions, because slow fading is imposed by the
network. The offset value transmission path. Contact the network planning department to
is tens of decibels. The make the following changes:
duration is from tens of
seconds to several hours. l Increase the installation height of the antenna.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.
If... Then...
If the RSL is lower than Fast fading occurs. Contact the network planning department to
or higher than the make the following changes:
specified RSL of the
network and if the l Adjust the position of the antenna to block the reflected
duration is from several wave or make the reflection point fall on the ground that has
milliseconds to tens of a small reflection coefficient, therefore reducing the
seconds. multipath fading.
l Adjust the RF configuration to make the links in the 1+1 SD
configuration.
l If the links are configured with the 1+1 SD protection,
adjust the height offset between two antennas to make the
receive power of one antenna stronger than the receive
power of the other antenna.
l Increase the fading margin.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the opposite end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the opposite end is rectified after
the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite
end.
The fault at the opposite end is rectified End the alarm handling.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the local end is rectified after the
loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the local end.
The fault at the opposite end is rectified End the alarm handling.
----End
Related Information
None
A.3.203 MW_CFG_MISMATCH
Description
The MW_CFG_MISMATCH is an alarm of configuration mismatch on radio links. This
alarm occurs when an NE detects configuration mismatch on both ends of a radio link. For
example, the number of E1 signals, the number of STM-1 signals, AM enabling, 1588
overhead enabling, modulation mode may be configured differently on both ends of a radio
link.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter Indicates the cause of the fault.
1
l 0x01: The number of E1 signals or the E1 timeslot priority at the local end
of a radio link is different from that at the other end.
l 0x02: The AM enabling is different.
l 0x03: The 1588 overhead enabling is different.
l 0x04: The modulation mode is different.
l 0x05: The service mode is different.
l 0x06: The number of STM-1 signals is different.
l 0x09: The IP header compression enabling is different.
l 0x0A: AES configurations at two ends of a link are inconsistent.
l 0x10: The IF board or its working mode does not match the type of the RF
unit.
l 0x12: Configurations of enhanced compression at both ends of a link are
inconsistent.
Name Meaning
Parameter When the value of Parameter 1 is 0x09:
2
l 0x01: The air interface compression at L2 is different.
l 0x02: The air interface compression at L3 is different.
When the value of Parameter 1 is 0x0A:
l 0x01: AES is enabled only at one end of a link.
l 0x02: AES message authentication codes (MACs) are inconsistent at both
ends of a link.
When the value of Parameter 1 is 0x12:
l 0x01: The enabling/disabling statuses of enhanced compression for CS7
queues are inconsistent at both ends of a link.
l 0x02: The enabling/disabling statuses of enhanced compression for CS6
queues are inconsistent at both ends of a link.
l 0x03: The enabling/disabling statuses of enhanced compression for EF
queues are inconsistent at both ends of a link.
l 0x04: The enabling/disabling statuses of enhanced compression for AF4
queues are inconsistent at both ends of a link.
l 0x05: The enabling/disabling statuses of enhanced compression for AF3
queues are inconsistent at both ends of a link.
l 0x06: The enabling/disabling statuses of enhanced compression for AF2
queues are inconsistent at both ends of a link.
l 0x07: The enabling/disabling statuses of enhanced compression for AF1
queues are inconsistent at both ends of a link.
l 0x08: The enabling/disabling statuses of enhanced compression for BE
queues are inconsistent at both ends of a link.
When Parameter 1 takes another value, Parameter 2 is reserved.
NOTE
If the value of Parameter 1 is 0x01, 0x03, 0x12, 0x0A, or 0x09, the number of E1 signals configured
over a radio link, 1588 overhead enabling status, enhanced compression configuration, and IP header
compression may not take effect.
Possible Causes
l Cause 1: The number of E1 signals or the E1 timeslot priority at the local end of a radio
link is different from that at the other end.
l Cause 2: The AM enabling is different on both ends of a radio link.
l Cause 3: The 1588 overhead enabling is different on both ends of a radio link.
Procedure
Step 1 Determine the possible cause of the alarm according to the alarm parameters.
Step 2 Check the configuration on both ends of the radio link. Ensure that the configuration is the
same on both ends of the radio link. For details, see Managing Radio Links.
----End
Related Information
None
A.3.204 MW_CONT_WAVE
Description
The MW_CONT_WAVE is an alarm of continuous wave. This alarm occurs if the continuous
wave is output by the IF board.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The continuous wave function is enabled.
l Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on
the IF port or composite port.
l Cause 3: The IF unit is faulty.
Procedure
Step 1 Cause 1: The continuous wave function is enabled.
1. Disable the continuous wave function. For details, see Setting IF Attributes.
Step 2 Cause 2: The MW_LOF alarm exists on the radio link and an outloop is performed on the IF
port or composite port.
1. Release the loopback by referring to 8.4.3 Setting Loopback for the IF Port.
2. Clear the MW_LOF alarm.
Step 3 Cause 3: The IF unit is faulty.
1. Replace the OptiX RTN 905E.
----End
Related Information
The continuous wave function tests the frequency stability and frequency consistency and
should be disabled after a test is completed.
A.3.205 MW_E1_LOST
Description
The MW_E1_LOST is an alarm indicating that E1 services are lost. When the AM
modulation scheme is downshifted, this alarm is reported by the discarded E1 services.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the timeslots of E1 services.
Possible Causes
Cause 1: The AM downshifts the modulation scheme.
Procedure
Step 1 Cause 1: The AM downshifts the modulation scheme.
1. Handle the alarm according to AM_DOWNSHIFT.
----End
Related Information
None
A.3.206 MW_FEC_UNCOR
Description
The MW_FEC_UNCOR is an alarm indicating that radio frames forward error correction
(FEC) encoding cannot be corrected.
Attribute
Parameters
None
Possible Causes
l Cause 1: Signal attenuation on the radio link is very heavy.
l Cause 2: The transmit unit of the opposite station is faulty.
l Cause 3: The receive unit of the local site is faulty.
l Cause 4: An interference event occurs.
Procedure
Step 1 Cause 1: Signal attenuation on the radio link is very heavy.
1. At the local end, check whether the receive power of the ODU is normal. If yes,
determine the abnormality and take proper measures. For details, see 4.4.1 Querying the
Historical Transmit Power and Receive Power.
If... Then...
The RSL is higher than Slow up fading occurs. Follow the steps:
the specified RSL of the
network. The offset value 1. Check whether intra-frequency or inter-frequency
is tens of decibels. The interference exists by scanning frequency spectra in
duration is from tens of microwave channels. For details, see 8.1.2 Scanning
seconds to several hours. Interfering Signals.
2. Use a spectrum analyzer to analyze the interference source.
3. Contact the spectrum management department to clear the
interference spectrum or change plans to minimize the
interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may be
the specified RSL of the faulty in both directions, because slow fading is imposed by the
network. The offset value transmission path. Contact the network planning department to
is tens of decibels. The make the following changes:
duration is from tens of
seconds to several hours. l Increase the installation height of the antenna.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.
If... Then...
If the RSL is lower than Fast fading occurs. Contact the network planning department to
or higher than the make the following changes:
specified RSL of the
network and if the l Adjust the position of the antenna to block the reflected
duration is from several wave or make the reflection point fall on the ground that has
milliseconds to tens of a small reflection coefficient, therefore reducing the
seconds. multipath fading.
l Adjust the RF configuration to make the links in the 1+1 SD
configuration.
l If the links are configured with the 1+1 SD protection,
adjust the height offset between two antennas to make the
receive power of one antenna stronger than the receive
power of the other antenna.
l Increase the fading margin.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the opposite end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the opposite end is rectified after
the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the cable connector is prepared according to the requirement. If any cable
connector does not meet the requirement, make a new connector.
3. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the opposite
end.
The fault at the opposite end is rectified End the alarm handling.
Locate the fault by looping back the opposite station and excluding the position one by one.
Follow the steps:
1. Perform an inloop on the IF port at the local end. For details, see 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the local end is rectified after the
loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
2. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does not
meet the requirement.
3. Check whether the IF cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
4. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not rectified Replace the ODU at the local end.
The fault at the opposite end is rectified End the alarm handling.
----End
Related Information
None
A.3.207 MW_LIM
Description
The MW_LIM is an alarm indicating that a mismatched radio link identifier is detected. This
alarm is reported if an IF unit detects that the link ID in the radio frame overheads is
inconsistent with the specified link ID.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The link ID of the local site does not match with the link ID of the opposite
station.
l Cause 2: The services on other radio links are received due to the incorrect configuration
of the radio link receive frequency at the local or opposite station.
l Cause 3: The antenna receives the radio signals from the other stations, because the
direction of the antenna is set incorrectly.
l Cause 4: The polarization direction of the XPIC is incorrect.
Procedure
Step 1 Cause 1: The link ID of the local site does not match with the link ID of the opposite station.
1. Check whether the link ID of the local site matches with the link ID of the opposite
station. For details, see Configuring a Single-Hop Radio Link. If not, set the link IDs of
the two stations to the same value according to the requirements of the networking
planning.
Step 2 Cause 2: The services on other radio links are received due to the incorrect configuration of
the radio link receive frequency at the local or opposite station.
1. Check whether the receive and transmit frequencies of the local site are consistent with
the receive and transmit frequencies of the opposite station. For details, see Configuring
a Single-Hop Radio Link. If not, set the receive and transmit frequencies of the two
stations again.
Step 3 Cause 3: The antenna receives radio signals from the other stations, because the direction of
the antenna is set incorrectly.
1. Adjust the direction of the antenna and ensure that the antennas at both ends are aligned.
Step 4 Cause 4: The polarization direction of the XPIC is incorrect.
1. If XPIC protection groups are configured, check whether the XPIC configuration is
correct. For details, see Configuring a Single-Hop Radio Link.
a. Check whether the settings of XPIC IF unit in polarization direction-V and
polarization direction-H meet the requirement of the planning.
If... Then...
The polarization direction does not Delete the working XPIC group that is
meet the requirement of the planning configured incorrectly and create the
other working XPIC group again.
b. Check whether Link ID-V and Link ID-H meet the requirement of the planning.
If... Then...
The link ID does not meet the Reset the ID of the radio link of the
requirement of the planning XPIC IF unit according to the
planning. For details, see Creating an
XPIC Working Group.
If... Then...
2. Check and modify the mapping relationship among the XPIC IF unit, ODU, OMT, and
antenna feed. Ensure that the XPIC IF unit in the polarization direction V of the two ends
are interconnected with each other through the radio link in the polarization direction V,
and the XPIC IF unit in the polarization direction H of the two ends are interconnected
with each other through the radio link in the polarization direction H.
----End
Related Information
The MW_LIM alarm is generated due to the inconsistency between the specified link ID and
the received link ID. When the MW_LOF alarm is generated on the link, the received link ID
is a random value. In this case, the link ID is invalid. The MW_LIM alarm is also suppressed
by the MW_LOF alarm.
A.3.208 MW_LOF
Description
The MW_LOF is an alarm indicating that the radio frame is lost.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: In the case of TDM radio services, the IF working modes at the local site and
the opposite station are different. In the case of services, the channel bandwidth and
modulation modes at the local site and the opposite station are different.
l Cause 3: The operating frequency of the ODU at the local site is inconsistent with the
operating frequency of the ODU at the opposite station.
Procedure
Step 1 Cause 1: The other alarms are generated.
1. Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
The relevant alarms are as follows:
HARD_BAD
VOLT_LOS
IF_CABLE_OPEN
BD_STATUS
RADIO_RSL_LOW
CONFIG_NOSUPPORT
TEMP_ALARM
Step 2 Cause 2: In the case of TDM radio services, the IF working modes at the local site and the
opposite station are different. In the case of services, the channel bandwidth and modulation
modes at the local site and the opposite station are different.
1. In the case of TDM radio services, check whether the working mode of the IF board at
the local site is consistent with the working mode of the IF board at the opposite station.
For details, see Configuring a Single-Hop Radio Link. If not, reset the working mode of
the IF board according to the network planning.
In the case of Hybrid radio services, check whether the channel bandwidth and
modulation modes are the same at both ends. If not, change the channel bandwidth and
modulation modes according to the network planning. For details, see Configuring a
Single-Hop Radio Link.
Step 3 Cause 3: The operating frequency of the ODU at the local site is inconsistent with the
operating frequency of the ODU at the opposite station.
1. Ensure that the type of the ODU at the local site is consistent with the type of the ODU
at the opposite station.
2. Reset the operating frequency of the ODU according to the network planning. For
details, see Setting ODU Transmit Frequency Attributes.
Set the transmit frequency of the local site to the same as the receive frequency of the
opposite station. Then, set the receive frequency of the local site to the same as the
transmit frequency of the opposite station.
Step 4 Cause 4: The transmit unit of the opposite station is faulty.
1. Check whether any alarms are generated in the equipment of the local site. If yes, take
priority to clear them.
The relevant alarms are as follows:
HARD_BAD
BD_STATUS
VOLT_LOS
IF_CABLE_OPEN
RADIO_MUTE
RADIO_TSL_HIGH
RADIO_TSL_LOW
TEMP_ALARM
2. Locate the fault by looping back the opposite station.
a. Perform an inloop on the IF port at the opposite end. For details, see and 8.4.3
Setting Loopback for the IF Port. Check whether the fault at the opposite end is
rectified after the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
b. Check whether the cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does
not meet the requirement.
d. Then, check whether the fault at the opposite end is rectified.
If... Then...
The fault at the opposite end is not Replace the ODU at the opposite
rectified end.
The fault at the opposite end is rectified End the alarm handling.
a. Perform an inloop on the IF port at the local end. For details, see and 8.4.3 Setting
Loopback for the IF Port. Check whether the fault at the local end is rectified
after the loopback.
If... Then...
The fault at the opposite end is not rectified Replace the IDU.
The fault at the opposite end is rectified Go to the next step.
b. Check whether the cable connector is prepared according to the requirement. If any
cable connector does not meet the requirement, make a new connector.
c. Check whether the IF cable is wet, broken, or pressed. Replace the cable that does
not meet the requirement.
d. Check whether the fault at the local end is rectified.
1. At the local site, check whether the receive power of the ODU is abnormal. For details,
see Browse historical performance events. If yes, determine the abnormality and take
proper measures.
If... Then...
The RSL is higher than Slow up fading occurs. Follow the steps:
the specified RSL of the
network. The offset value 1. Check for co-channel interference. For details, see 8.1.2
is tens of decibels. The Scanning Interfering Signals.
duration is from tens of 2. Use a spectrum analyzer to analyze the interference source.
seconds to several hours. 3. Contact the spectrum management department to clear the
interference spectrum or change plans to minimize the
interference.
The RSL is lower than Slow down fading occurs. Generally, the radio link may be
the specified RSL of the faulty in both directions, because slow fading is imposed by the
network. The offset value transmission path. Contact the network planning department to
is tens of decibels. The make the following changes:
duration is from tens of
seconds to several hours. l Increase the installation height of the antenna.
l Reduce the transmission distance.
l Increase the antenna gain.
l Increase the transmit power.
If... Then...
If the RSL is lower than Fast fading occurs. Contact the network planning department to
or higher than the make the following changes:
specified RSL of the
network and if the l Adjust the position of the antenna to block the reflected
duration is from several wave or make the reflection point fall on the ground that
milliseconds to tens of has a small reflection coefficient, therefore reducing the
seconds. multipath fading.
l Adjust the RF configuration to make the links in the 1+1
SD configuration.
l If the links are configured with the 1+1 SD protection,
adjust the height offset between two antennas to make the
receive power of one antenna stronger than the receive
power of the other antenna.
l Increase the fading margin.
----End
Related Information
NOTE
If the MW_LOF alarm is reported frequently, check whether Anti-jitter Time(s) is set to 0. You can
modify the configuration by following instructions in Modifying the Parameters of IF 1+1 Protection.
A.3.209 MW_RDI
Description
The MW_RDI is an alarm indicating that there are defects at the remote end of the radio link.
This alarm is reported when the IF board detects an RDI in the radio frame overheads. If RTN
905s are cascaded at the remote end of a PLA/EPLA link and the slave RTN 905 detects a
fault in the cascading line, the NE connected to the slave RTN 905 reports the alarm.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
Cause 1: After detecting a service alarm that is caused by the fault in a radio link, the receive
station returns a radio link fault indication to the transmit station.
Cause 2: RTN 905s are cascaded at the remote end of a PLA/EPLA link and the slave RTN
905 detects a fault in the cascading line.
Procedure
Step 1 Clear the radio alarms that occur at the opposite station. The possible alarms are as follows:
l MW_LOF
l R_LOF
l R_LOC
l MW_FEC_UNCOR
l XPIC_LOS
l MW_BER_SD
l MW_BER_EXC
l NB_UNREACHABLE
----End
Related Information
None
A.3.210 NB_CFG_MISMATCH
Description
The NB_CFG_MISMATCH alarm indicates that the neighboring NEs in a physical link
aggregation (PLA) group, 1+1 protection group, or cross polarization interference
cancellation (XPIC) workgroup are inconsistently configured.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: Indicates that two neighboring NEs have different PLA
configuration.
l 0x02: Indicates that two neighboring NEs have different 1+1 protection
configuration.
l 0x01: Indicates that two neighboring NEs have different XPIC
configuration.
Name Meaning
Parameter 2 When Parameter 1 is 0x01, Parameter 2 has the following meanings:
Possible Causes
l Cause 1: The neighboring NEs in a PLA group are inconsistently configured.
l Cause 2: The neighboring NEs in a 1+1 protection group are inconsistently configured.
l Cause 3: The neighboring NEs in an XPIC group are inconsistently configured.
Procedure
Step 1 Determine the alarm cause according to the alarm parameters.
If... Then...
PLA configurations are inconsistent See Creating a PLA/EPLA/EPLA+/Super EPLA
Group.
1+1 protection configurations are See Creating an IF 1+1 Protection Group.
inconsistent
XPIC configurations are See Configuring a Single-Hop Radio Link.
inconsistent
----End
Related Information
None
A.3.211 NB_UNREACHABLE
Description
The NB_UNREACHABLE alarm indicates that the neighboring NE is unreachable.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
Name Meaning
Parameter 1 0x02: The cascading channel is faulty.
Possible Causes
l Cause 1: The cascading cable (SFP) is loose or damaged.
Procedure
Step 1 Cause 1: The cascading cable (SFP) is loose or damaged.
1. Check the cascading cable (SFP). If it is loose or damaged, secure the connection or
replace the cable.
----End
Related Information
None
A.3.212 NEIP_CONFUSION
Description
The NEIP_CONFUSION alarm indicates an IP address conflict.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Parameter 4 Indicate the IP address.
Possible Causes
Cause 1: An IP address conflict occurs on the network.
Procedure
Step 1 Modify IP addresses for the affected NEs according to the network plan.
----End
Related Information
None
A.3.213 NESF_LOST
Description
The NESF_LOST is an alarm indicating that the NE software is lost. This alarm is reported
when the system control, cross-connect, and timing board detects that the NE software is lost.
Attribute
Alarm Severity Alarm Type
Critical 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 The value is always 0x01.
Parameter 2,
Indicate the ID of the routine inspection object.
Parameter 3
Parameter 4 Indicates the specific alarm cause when a different bit is 1.
l 0x01: If the first bit is 1, it indicates that the file does not exist.
l 0x02: If the second bit is 1, it indicates that verification of the file
fails.
Possible Causes
l Cause 1: No new NE software is loaded after the existing NE software is erased.
l Cause 2: Loading the NE software is unsuccessful.
l Cause 3: The NE is faulty.
Procedure
Step 1 Cause 1: No new NE software is loaded after the existing NE software is erased.
If... Then...
The alarm is caused by the loading Contact the Huawei technical support
operation engineers to reload the software.
The alarm is not caused by the loading Go to the next step.
operation
----End
Related Information
None
A.3.214 NESOFT_MM
Description
The NESOFT_MM is an alarm indicating that the first software system is different from the
second software system. This alarm is reported when the NE detects that the first software
system and the second software system of the system control, cross-connect, and timing board
mismatch with each other.
Attribute
Alarm Severity Alarm Type
Major Processing alarm
Parameters
Name Meaning
Parameter 1 Indicates the location of the file.
l 0x01: the files in the flash memory
Name Meaning
Parameter 2, Indicate the IDs of the inconsistent files in the flash memory of the
Parameter 3 system control board if the value of Parameter 1 is 0x01,
Parameter 4 Indicate the cause of the alarm.
l 0x04: The file versions in the master and slave areas are
inconsistent.
Parameters
None
Possible Causes
Cause 1: The software stored in the ofs1 and ofs2 areas of the active SCC board has different
versions.
Procedure
Step 1 Contact Huawei technical support engineers for reloading the software.
----End
Related Information
None
A.3.215 NTP_SYNC_FAIL
Description
The NTP_SYNC_FAIL is an alarm indicating that NTP time synchronization fails.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: The NTP server is not configured or is configured incorrectly.
l Cause 2: The NTP server cannot communicate with the NE.
l Cause 3: The NTP server fails.
Procedure
Step 1 Cause 1: The NTP server is not configured or is configured incorrectly.
1. Configure the NTP server correctly.
2. Re-configure the NTP parameters for the NE.
Step 2 Cause 2: The NTP server cannot communicate with the NE.
1. Check whether the cable connecting the gateway NE to the NTP server is normal. If not,
rectify the connection fault.
2. Check whether the DCN communication between the NTP server and the NE is normal.
If not, configure the DCN communication correctly.
----End
Related Information
None
A.3.216 ODC_BATTERY_CURRENT_ABN
Description
The ODC_BATTERY_CURRENT_ABN is an alarm indicating that the current of the storage
battery 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: The internal current loop of the storage battery is broken.
l 0x02: The recharge current of the storage battery is very high.
l 0x03: The storage battery is discharged unevenly.
Possible Causes
l Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
l Cause 2: The positive and negative polarities of the storage battery are connected
inversely.
l Cause 3: The power module frame is faulty.
l Cause 4: The power monitoring module is faulty.
l Cause 5: The power module is faulty.
Procedure
Step 1 Cause 1: The circuit breaker or fuse of the storage battery in the cabinet is off.
If... Then...
The circuit breaker of the storage battery is open Close the circuit breaker.
The fuse of the storage battery is broken Replace the fuse.
Step 2 Cause 2: The positive and negative polarities of the storage battery are connected inversely.
1. Connect the positive and negative polarities of the storage battery correctly.
Step 3 Cause 3: The power module frame is faulty.
1. Check whether the power module frame is damaged. If the power module frame is
damaged, replace the power module frame.
Step 4 Cause 4: The power monitoring module is faulty.
1. Replace the power monitoring module.
Step 5 Cause 5: The power module is faulty.
1. Check whether the ODC_MDL_ABN alarm is reported.
If... Then...
The ODC_MDL_ABN alarm is Rectify the fault by referring the solution to
reported the ODC_MDL_ABN alarm.
The ODC_MDL_ABN alarm is not Replace the power module.
reported
----End
Related Information
None
A.3.217 ODC_BATTERY_PWRDOWN
Description
The ODC_BATTERY_PWRDOWN is an alarm indicating that the storage battery fails to
provide power for the equipment.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: power-off due to low voltage
l 0x02: power-off due to NMS control
l 0x03: power-off due to human interference
l 0x04: power-off due to high temperature
Possible Causes
l Cause 1 of power-off due to NMS control: The storage battery fails to provide power for
the equipment due to NMS control.
l Cause 1 of power-off due to local human interference: The BAT button on the front
panel of the PMU is set to OFF.
l Cause 1 of power-off due to low voltage: The AC input power is abnormal.
l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the storage battery due to high temperature is set to an inappropriate value.
l Cause 2 of power-off due to high temperature: The temperature of the storage battery is
very high.
l Cause 3 of power-off due to high temperature: The temperature sensor of the power
module is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The storage battery fails to provide power for the
equipment due to NMS control.
1. Enable the battery to power on the equipment.
Step 3 Cause 1 of power-off due to local human interference: The BAT button on the front panel of
the PMU is set to OFF.
1. On the front panel of the PMU, hold the BAT ON button for 5-10 seconds to turn on the
storage battery.
Step 4 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
1. Query the threshold that results in an alarm when the AC power voltage is abnormal.
Then, determine whether the threshold is appropriate according to the configuration and
planning information.
If... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
The threshold is appropriate Go to the next step.
2. Check whether the AC circuit breaker is closed.
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is incorrect. Connect the cable properly.
The AC power cable is deteriorated and damaged. Replace the cable.
Step 5 Cause 2 of power-off due to low voltage: The power module is faulty.
1. Rectify the fault of the power module by referring to the solution to the
ODC_MDL_ABN alarm.
Step 6 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
1. Rectify the fault of the power monitoring module.
Step 7 Cause 1 of power-off due to high temperature: The temperature that results in power-off of the
power module due to high temperature is set to an inappropriate value.
1. Query the threshold that results in an alarm due to high temperature. Then, determine
whether the threshold is appropriate according to the configuration and planning
information.
If... Then...
The threshold is Set the threshold to an appropriate value.
inappropriate
The threshold is Perform the operations required when the alarm is
appropriate generated by cause 2 of power-off due to high
temperature.
Step 8 Cause 2 of power-off due to high temperature: The temperature of the storage battery is very
high.
1. Replace the storage battery.
Step 9 Cause 3 of power-off due to high temperature: The temperature sensor of the power module is
faulty.
1. Replace the temperature sensor of the power module.
----End
Related Information
None
A.3.218 ODC_DOOR_OPEN
Description
The ODC_DOOR_OPEN is an alarm indicating that the door of an outdoor cabinet is open.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The door access alarm is set incorrectly.
l Cause 2: The cabinet door is open.
l Cause 3: The cable between the door sensor and the monitor device is connected
incorrectly.
Procedure
Step 1 Cause 1: The door access alarm is set incorrectly.
1. Check whether the door access alarm is set correctly according to the configuration and
planning information.
If... Then...
The door access alarm is set correctly Go to Cause 2.
The door access alarm is set incorrectly Set the door access alarm correctly.
Step 3 Cause 3: The cable between the door sensor and the monitor device is connected incorrectly.
1. Check the cable between the door sensor and the monitor device.
If... Then...
The cable is connected incorrectly or is loose Connect the cable properly.
The cable is deteriorated or damaged Replace the cable.
The connection is correct Go to Cause 4.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 5.
----End
Related Information
None
A.3.219 ODC_FAN_FAILED
Description
The ODC_FAN_FAILED is an alarm indicating that the fan is faulty.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the position of the fault.
l 0x01: The internal fan is faulty.
l 0x02: The external fan is faulty.
Possible Causes
l Cause 1: The fan cable is connected incorrectly.
l Cause 2: The fan is faulty.
l Cause 3: The fan is not installed.
Procedure
Step 1 Determine the faulty fan according to the alarm parameters displayed on the NMS.
----End
Related Information
None
A.3.220 ODC_HUMI_ABN
Description
The ODC_HUMI_ABN is an alarm indicating that the relative humidity in the cabinet
environment exceeds the specified 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: The relative humidity is very high.
l 0x02: The relative humidity is very low.
Possible Causes
l Cause 1: The threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the humidity sensor and the monitoring equipment is
connected incorrectly.
l Cause 3: The humidity sensor is faulty.
l Cause 4: The associated monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The threshold that results in an alarm is set incorrectly.
1. Check whether the humidity threshold is set correctly according to the configuration and
planning information.
If... Then...
The humidity threshold is set Perform the operations required when the
correctly alarm is generated due to cause 2.
The humidity threshold is set Set the humidity threshold to an appropriate
incorrectly value.
Step 2 Cause 2: The cable between the humidity sensor and the monitoring equipment is connected
incorrectly.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Handle the exceptions of the cable.
The cable is not deteriorated and Perform the operations required when the
damaged alarm is generated due to cause 3.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Perform the operations required when the alarm is
generated due to cause 4.
----End
Related Information
None
A.3.221 ODC_LOAD_PWRDOWN
Description
The ODC_LOAD_PWRDOWN is an alarm indicating that the secondary load is powered off.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: power-off due to low voltage
l 0x02: power-off due to background control
l 0x03: power-off due to startup in the case of low temperature
l 0x04: power-off due to high temperature
Possible Causes
l Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
l Cause 1 of power-off due to low voltage: The AC input power is abnormal.
l Cause 2 of power-off due to low voltage: The power module is faulty.
l Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
l Cause 1 of power-off due to low temperature: The cabinet temperature is very low.
l Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.
l Cause 1 of power-off due to high temperature: The temperature that results in power-off
of the load due to high temperature is set to an inappropriate value.
l Cause 2 of power-off due to high temperature: The cabinet temperature is very high.
l Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.
Procedure
Step 1 Determine the cause of the alarm according to the alarm parameters displayed on the NMS.
Step 2 Cause 1 of power-off due to NMS control: The load is powered off due to NMS control.
1. Turn on the storage battery for the equipment.
Step 3 Cause 1 of power-off due to low voltage: The AC input power is abnormal.
1. Query the threshold that results in an alarm when the AC power voltage is abnormal.
Then, determine whether the threshold is appropriate according to the configuration and
planning information.
If... Then...
The threshold is inappropriate Set the threshold to an appropriate value.
The threshold is appropriate Go to the next step.
If... Then...
The AC circuit breaker is closed Go to the next step.
The AC circuit breaker is open Close the AC circuit breaker.
3. Check the connection of the AC power cable.
If... Then...
The connection of the AC power cable is Connect the cable properly.
incorrect.
The AC power cable is deteriorated and Handle the exceptions of the
damaged. cable.
Step 4 Cause 2 of power-off due to low voltage: The power module is faulty.
1. Rectify the fault of the power module by referring to the solution to the
ODC_MDL_ABN alarm.
Step 5 Cause 3 of power-off due to low voltage: The power monitoring module is faulty.
1. Rectify the fault of the power monitoring module.
Step 6 Cause 1 of power-off due to low temperature: The cabinet temperature is very low.
1. Check whether the heat exchanger works properly.
If... Then...
The heat exchanger does not Rectify the fault of the heat exchange.
work properly
The heat exchanger works Perform the operations required when the alarm is
properly generated by cause 2 of power-off due to low
temperature.
Step 7 Cause 2 of power-off due to low temperature: The ambient temperature sensor is faulty.
1. Replace the temperature sensor of the power module.
Step 8 Cause 1 of power-off due to high temperature: The temperature that results in power-off of the
load due to high temperature is set to an inappropriate value.
1. Query the threshold that results in an alarm in the case of power-off due to high
temperature of the load. Then, determine whether the threshold is appropriate according
to the configuration and planning information.
If... Then...
The threshold is Set the threshold to an appropriate value.
inappropriate
The threshold is Perform the operations required when the alarm is
appropriate generated by cause 2 of power-off due to high
temperature.
Step 9 Cause 2 of power-off due to high temperature: The cabinet temperature is very high.
1. Check whether the ambient temperature is very high all the time.
If... Then...
The heat exchanger does not Rectify the fault of the heat exchange.
work properly
The heat exchanger works Perform the operations required when the alarm is
properly generated by cause 3 of power-off due to high
temperature.
Step 10 Cause 3 of power-off due to high temperature: The ambient temperature sensor is faulty.
1. Replace the ambient temperature sensor.
----End
Related Information
The secondary load refers to the load that the DC power outlet of the cabinet corresponds to.
A.3.222 ODC_MDL_ABN
Description
The ODC_MDL_ABN is an alarm indicating that the power module is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the alarmed power module.
Name Meaning
Parameter 2, Indicates the cause of the alarm.
Parameter 3
l 0x01: The power module is switched off.
l 0x02: The power module is faulty.
l 0x03: The power module stops self-protection.
l 0x04: The power module fails to communicate with the power
monitoring module, or the power module is not in position.
l 0x05: The number of PSUs configured on the NMS is incorrect.
l 0x06: The power module status cannot be identified.
Possible Causes
l Cause 1: The number of PSUs configured on the NMS is incorrect.
l Cause 2: The power module is not in position.
l Cause 3: The power module is faulty.
l Cause 4: The power monitoring unit is abnormal.
Procedure
Step 1 Cause 1: The power module is not configured on the NMS.
1. Set the logical slot of the power module on the NMS.
Step 2 Cause 2: The power module is not in position, or the power module is not inserted properly.
If... Then...
The power module is not in position Install the power module.
The power module is not inserted securely Install the power module properly.
----End
Related Information
None
A.3.223 ODC_POWER_FAIL
Description
The ODC_POWER_FAIL is an alarm indicating that the AC input power voltage and DC
output power voltage of an outdoor cabinet are 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the fault.
l 0x56: The AC input power is very high.
l 0x57: The AC input power is very low.
l 0x58: The DC output power is very high.
l 0x59: The DC output power is very low.
l 0x5b: No AC input power is available.
l 0x5c: The AC power voltage is abnormal.
Possible Causes
l Cause 1: The AC input power voltage is abnormal.
l Cause 2: The DC output power voltage is abnormal.
Procedure
Step 1 Cause 1: The AC input power voltage is abnormal.
1. The threshold that results in an alarm due to the AC input power voltage is set
incorrectly.
If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The AC circuit breaker is open.
If... Then...
The AC circuit breaker is open Close the AC circuit breaker.
The AC circuit breaker is closed Go to the next step.
3. The AC power cable is connected incorrectly.
If... Then...
The cable is connected incorrectly or is loose Connect the cable properly.
The cable is deteriorated and damaged Handle the exceptions of the cable.
The cable is connected correctly Go to the next step.
4. The AC power grid distributes the power abnormally.
If... Then...
The AC power grid distributes the power Rectify the fault of the power module
abnormally at the base station.
The AC power grid distributes the power Go to the next step.
normally
5. The monitoring equipment is faulty.
If... Then...
The monitoring equipment is Rectify the fault of the monitoring equipment.
faulty
The monitoring equipment is not Perform the operations required when the
faulty alarm is generated due to cause 2.
If... Then...
The threshold is set incorrectly Set the threshold to an appropriate value.
The threshold is set correctly Go to the next step.
2. The PSU module is faulty.
If... Then...
The PSU module is faulty Rectify the fault of the PSU module.
The PSU module is not faulty Go to the next step.
3. The power of the storage battery is insufficient.
If... Then...
The power of the storage battery is Recharge the storage battery.
insufficient
The power of the storage battery is sufficient Rectify the fault of the monitoring
equipment.
----End
Related Information
None
A.3.224 ODC_SMOKE_OVER
Description
The ODC_SMOKE_OVER is an alarm indicating that smoke occurs in an outdoor cabinet.
Attribute
Parameters
None
Possible Causes
l Cause 1: The smoke alarm is set incorrectly.
l Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
l Cause 3: The cable between the smoke sensor and the monitoring equipment is
connected incorrectly.
l Cause 4: The smoke sensor is faulty.
l Cause 5: The associated monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The smoke alarm is set incorrectly.
1. Check whether the smoke alarm is set correctly according to the configuration and
planning information.
If... Then...
The smoke alarm is set correctly Perform the operations required when the
alarm is generated due to cause 2.
The smoke alarm is set incorrectly Set the smoke alarm correctly.
Step 2 Cause 2: A fire and heavy smoke occur at the equipment in the cabinet.
1. Extinguish the fire in the cabinet.
Step 3 Cause 3: The cable between the smoke sensor and the monitoring equipment is connected
incorrectly.
1. Check whether the cable between the sensor and the monitoring equipment is connected
correctly.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Replace the cable.
The cable is not deteriorated and Perform the operations required when
damaged the alarm is generated due to cause 4.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Perform the operations required when the alarm is
generated due to cause 5.
----End
Related Information
None
A.3.225 ODC_SURGE_PROTECTION_FAIL
Description
The ODC_SURGE_PROTECTION_FAIL is an alarm indicating that the surge protection
function of the outdoor cabinet 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the type of the alarm.
l 0x01: AC surge protection alarm
l 0x02: DC surge protection alarm
Possible Causes
l Cause 1: The alarm is set incorrectly.
l Cause 2: The cable between the lightning sensor and the monitoring equipment is
connected incorrectly.
l Cause 3: The lightning sensor is faulty.
l Cause 3: The lightning arrestor is faulty.
l Cause 5: The associated monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The alarm is set incorrectly.
1. Check whether the alarm is set correctly according to the configuration and planning
information.
If... Then...
The alarm is set correctly Perform the operations required when the alarm is
generated due to cause 2.
The alarm is set incorrectly Set the surge protection alarm correctly.
Step 2 Cause 2: The cable between the lightning sensor and the monitoring equipment is connected
incorrectly.
1. Check the cable connection between the sensor and the monitoring equipment.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Replace the cable.
The cable is not deteriorated and Perform the operations required when
damaged the alarm is generated due to cause 3.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Perform the operations required when the alarm is
generated due to cause 4.
If... Then...
The alarm output end of the lightning Perform the operations required
arrestor works properly when the alarm is generated due to
cause 5.
The alarm output end of the lightning Replace the lightning arrestor.
arrestor does not work properly
----End
Related Information
None
A.3.226 ODC_TEC_ALM
Description
The ODC_TEC_ALM is an alarm indicating that the TEC air conditioning module in the
cabinet does not work properly.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The TEC cable is connected incorrectly.
l Cause 2: The TEC module is faulty.
l Cause 3: The monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The TEC cable is connected incorrectly.
1. Connect the TEC cable correctly.
Step 2 Cause 2: The TEC module is faulty.
1. Replace the TEC module.
Step 3 Cause 3: The monitoring equipment is faulty.
1. Rectify the fault of the monitoring equipment.
----End
Related Information
None
A.3.227 ODC_TEMP_ABN
Description
The ODC_TEMP_ABN is an alarm indicating that the ambient temperature of the cabinet or
the temperature of the storage battery is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the cause of the alarm.
l 0x01: The ambient temperature is higher than the upper threshold.
l 0x01: The ambient temperature is lower than the lower threshold.
Parameter 2 Indicates the temperature type.
l 0x01: The temperature at the air outlet is very high or low.
l 0x0b: Ambient temperature 1 is very high or low.
l 0x0c: Ambient temperature 2 is very high or low.
l 0x0d: The temperature of the battery group is very high or low.
Possible Causes
l Cause 1: The temperature threshold that results in an alarm is set incorrectly.
l Cause 2: The cable between the temperature sensor and the monitoring equipment is
connected incorrectly.
l Cause 3: The temperature sensor is faulty.
l Cause 4: The associated monitoring equipment is faulty.
Procedure
Step 1 Cause 1: The temperature threshold that results in an alarm is set incorrectly.
1. Check whether the temperature alarm is set correctly according to the configuration and
planning information.
If... Then...
The temperature alarm is set Perform the operations required when the
correctly alarm is generated due to cause 2.
The temperature alarm is set Set the temperature alarm correctly.
incorrectly
Step 2 Cause 2: The cable between the temperature sensor and the monitoring equipment is
connected incorrectly.
1. Check whether the cable between the sensor and the monitoring equipment is connected
correctly.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Handle the exceptions of the cable.
If... Then...
The cable is not deteriorated and Perform the operations required when
damaged the alarm is generated due to cause 3.
If... Then...
The alarm is cleared End the alarm handling.
The alarm persists Perform the operations required when the alarm is
generated due to cause 4.
----End
Related Information
None
A.3.228 ODC_WATER_ALM
Description
The ODC_WATER_ALM is an alarm indicating that certain water enters the cabinet.
Attribute
Alarm Severity Alarm Type
Critical Environment alarm
Parameters
None
Possible Causes
l Cause 1: The water alarm is set incorrectly.
l Cause 2: Certain water enters the cabinet.
l Cause 3: The cable between the water sensor and the monitoring equipment is connected
incorrectly.
l Cause 4: The water sensor is faulty.
Procedure
Step 1 Cause 1: The water alarm is set incorrectly.
1. Check whether the water alarm is set correctly according to the configuration and
planning information.
If... Then...
The water alarm is set correctly Perform the operations required when the
alarm is generated due to cause 2.
The water alarm is set incorrectly Set the water alarm correctly.
Step 3 Cause 3: The cable between the sensor and the monitoring equipment is connected
incorrectly.
1. Check whether the cable between the sensor and the monitoring equipment is connected
correctly.
If... Then...
The cable is connected incorrectly or is Connect the cable properly.
loose
The cable is deteriorated and damaged Handle the exceptions of the cable.
The cable is not deteriorated and Perform the operations required when
damaged the alarm is generated due to cause 4.
----End
Related Information
None
A.3.229 OSPFNBRSTATECHANGE
Description
The OSPFNBRSTATECHANGE alarm indicates that the OSPF neighbor state changes.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Parameter 4 Indicate the router ID.
Parameter 5 to Parameter 8 Indicate the IP address of the OSPF neighbor.
Parameter 9 to Parameter 12 Indicate the index number of the interface on the OSPF
neighbor.
Parameter 13 to Parameter 16 Indicate the router ID of the OSPF neighbor.
Parameter 17 to Parameter 20 Indicate the OSPF neighbor state.
l 0x01: Down
l 0x02: Attempt
l 0x03: Init
l 0x04: 2-Way
l 0x05: ExStart
l 0x06: Exchange
l 0x07: Loading
l 0x08: Full
Parameter 21 to Parameter 24 Indicate the OSPF process ID.
Parameter 25 to Parameter 28 Indicate the OSPF area ID.
Parameter 29 to Parameter 32 Indicate the index number of the local interface.
Parameter 33 to Parameter 36 Indicate the IP address of the local interface.
Parameter 37 to Parameter 100 Indicate the name of the local interface.
Parameter 101 to Parameter 131 Indicate the name of the VPN instance.
Parameter 132 to Parameter 135 Indicate the alarm cause.
NOTE
State changes from Down to Full: Down > Init > 2-way > Exstart > Exchange > Loading >Full
Possible Causes
l Cause 1: OSPF configurations are changed at the peer end.
l Cause 2: The peer port is faulty.
l Cause 3: The physical link is faulty.
l Cause 4: The peer NE is faulty.
Procedure
Step 1 Cause 1: OSPF configurations are changed at the peer end.
1. Check whether OSPF configurations are correct at the peer end. If the OSPF
configurations are incorrect (such as incorrect interface IP address configurations,
inconsistent authentication mode configurations, and inconsistent OSPF area
configurations), rectify the configurations to ensure configuration consistency at both
ends.
----End
A.3.230 OUT_PWR_ABN
Description
The OUT_PWR_ABN alarm indicates that the output optical power is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the port ID.
Name Meaning
Parameter 2, Parameter 3 Indicate the path ID. The parameters have a fixed value of 0x00
0x01.
Parameter 4, Parameter 5 Are reserved. The value is always 0xFF.
Possible Causes
l Cause 1: The output optical power is too high or low.
l Cause 2: A board is faulty.
Procedure
Step 1 Cause 1: The output optical power is too high or low.
1. Browse optical power performance events.
If... Then...
The output optical power does not meet the Replace the optical module.
requirement
The output optical power is too high Add a proper attenuator to reduce the
input optical power.
----End
Related Information
None
A.3.231 OUT1TEMP_SENSOR_FAIL
Description
The OUT1TEMP_SENSOR_FAIL is an alarm indicating that the air outlet temperature sensor
of the cabinet fails.
Attribute
Parameters
None
Possible Causes
l Cause 1: The air outlet temperature sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The air outlet temperature sensor is faulty.
1. Replace the air outlet temperature sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
----End
Related Information
None
A.3.232 OUT2TEMP_SENSOR_FAIL
Description
The OUT2TEMP_SENSOR_FAIL is an alarm indicating that the external cycling air outlet
temperature sensor of the cabinet fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The external cycling air outlet temperature sensor is faulty.
l Cause 2: The control board of the cabinet is faulty.
l Cause 3: Cables are misconnected or damaged.
l Cause 4: The external cycling air outlet temperature sensor is not installed.
Procedure
Step 1 Cause 1: The external cycling air outlet temperature sensor is faulty.
1. Replace the external cycling air outlet temperature sensor.
2. Then, check whether the alarm clears.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 2.
If... Then...
The alarm clears End the alarm handling.
The alarm persists Go to Cause 3.
Step 4 Cause 4: The external cycling air outlet temperature sensor is not installed.
1. Install the external cycling air outlet temperature sensor.
----End
Related Information
None
A.3.233 PASSWORD_NEED_CHANGE
Description
The PASSWORD_NEED_CHANGE alarm indicates that the default user password, WLAN
password, or AES authentication code has not been changed and must been changed timely to
prevent security risks.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Possible Causes
l Cause 1: The default user password has not been changed.
l Cause 2: The default WLAN password has not been changed.
l Cause 3: The default AES authentication code has not been changed.
Procedure
Step 1 Change the default user password, WLAN password, or AES authentication code. After the
related password is changed, the PASSWORD_NEED_CHANGE alarm is automatically
cleared.
----End
Related Information
None
A.3.234 PATCH_BD_EXCLUDE
Description
The PATCH_BD_EXCLUDE alarm indicates that an error occurs when a patch package is
being loaded to an NE. The NE is automatically isolated from patch package loading.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause: An error occurs when a patch package is being loaded to the NE.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
A.3.235 PATCH_BD_MATCH_FAIL
Description
The PATCH_BD_MATCH_FAIL alarm indicates that the patch package does not match the
NE to which the patch package is loaded.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause: The patch package does not match the NE to which the patch package is loaded.
Procedure
Step 1 Reload a correct patch package to the NE.
----End
Related Information
None
A.3.236 PATCH_CHGSCC_NOTMATCH
Description
The PATCH_CHGSCC_NOTMATCH alarm indicates a mismatch between the patch package
and the NE after the NE is replaced.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause: The NE is replaced.
Procedure
Step 1 Re-load the patch package.
----End
Related Information
None
A.3.237 PATCH_PKGERR
Description
The PATCH_PKGERR alarm indicates that a patch package is incorrect or has been damaged
or deleted.
Attribute
Parameters
None
NOTE
Possible Causes
l Cause 1: A patch package is incorrect.
l Cause 2: A patch package has been damaged.
l Cause 3: A patch package has been deleted.
Procedure
Step 1 Load a correct patch package.
----End
Related Information
None
A.3.238 PG_LINK_FAIL
Description
The PG_LINK_FAIL is an alarm indicating that the links in a 1+1 protection group fail.
Attribute
Alarm Severity Alarm Type
Critical Service alarm
Parameters
None
Possible Causes
Cause: Service alarms occur on the main and standby unit.
Procedure
Step 1 Set the Alarm Report Mode to Protection group and board alarms. For details, see
Querying the IF 1+1 Protection Status.
NOTE
When alarms with different priorities occur on a board at the same time, the board reports only the
alarms with the highest priority. Alarms can be arranged in descending order by priority: hardware
alarms > configuration alarms > service alarms.
----End
Related Information
None
A.3.239 PG_PRT_DEGRADED
Description
The PG_PRT_DEGRADED alarm indicates that a 1+1 protection group is degraded. This
alarm is reported when a fault occurs on the active or standby link in a 1+1 protection group.
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
Name Meaning
Parameter 1 Indicates the slot ID of the board.
Parameter 2 Indicates the slot ID of the subboard.
Parameter 3 Indicates the port ID.
Parameter 4 Indicates the fault type.
Possible Causes
l Cause 1: A service or hardware alarm exists on the board that has reported the alarm.
l Cause 2: The 1+1 protection group is locked out, or forced switching is performed
manually.
Procedure
Step 1 Query the PG_PRT_DEGRADE alarm on the NMS and identify the faulty board based on
alarm parameters.
Step 2 Cause 1: A service or hardware alarm exists on the board that has reported the alarm.
1. Check for R_LOF, MW_LOF, and HARD_BAD alarms on the faulty board or
corresponding ODU and clear them by following instructions in A.3.265 R_LOF, A.
3.208 MW_LOF, and A.3.89 HARD_BAD if any.
Step 3 Cause 2: The 1+1 protection group is locked out, or forced switching is performed manually.
1. Identify the cause of manual switching and clear the switching by following instructions
in Testing IF 1+1 Protection Switching (OptiX RTN 905 2E).
Step 4 Check whether the alarm PG_PRT_DEGRADE is cleared. If the alarm persists, contact
Huawei technical support engineers to handle the alarm.
----End
Related Information
None
A.3.240 PLA_CFG_MISMATCH
Description
The PLA_CFG_MISMATCH alarm indicates that physical link aggregation (PLA)
configurations are inconsistent at two ends of a microwave link.
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 details
about each parameter, refer to the following table.
Name Meaning
Name Meaning
NOTE
If the value of Parameter 4 is 0x06-0x0D, 0x01 or 0x02, the enhanced compression configurations for
each queue, Layer 2 header compression configuration and Layer 3 header compression configuration in
the PLA protection group may not take effect.
Possible Causes
l Cause 1: The PLA group is configured on the local NE, but not configured on the peer
NE.
l Cause 2: Frame header compression is enabled for only one NE.
l Cause 3: The number of member links in the PLA group is different at both ends.
l Cause 4: Local member ports and peer member ports do not belong to the same PLA
group.
Procedure
Step 1 Cause 1: The PLA group is configured on the local NE, but not configured on the peer NE.
1. Configure the PLA group on the peer NE by referring to Creating a PLA/EPLA/EPLA+/
Super EPLA Group.
Step 2 Cause 2: Frame header compression is enabled for only one NE.
1. Determine the port that needs to be re-configured. For details, see Querying the Status of
a PLA/EPLA/EPLA+/Super EPLA Group and the network plan.
2. Enable or disable frame header compression on the port to ensure configuration
consistency at both ends. For details, see Configuring Ethernet Frame Header
Compression over Air Interfaces.
Step 3 Cause 3: The number of member links in the PLA group is different at both ends.
1. Set the number of member links consistently at both ends by referring to Creating a
PLA/EPLA/EPLA+/Super EPLA Group.
Step 4 Cause 4: Local member ports and peer member ports do not belong to the same PLA group.
1. Check whether PLA configurations of the interconnected IF boards comply with the
network plan. For details, see Creating a PLA/EPLA/EPLA+/Super EPLA Group.
Option Description
If... Then...
The configurations do not comply Re-configure the PLA group according to the
with the network plan network plan.
The configurations comply with Verify the IF cable connections between the IF
the network plan boards and ODUs to make sure the radio links
are correctly established.
----End
Related Information
None
A.3.241 PLA_DOWN
Description
The PLA_DOWN alarm indicates that a PLA group is faulty. This alarm is reported when the
number of active member links in a PLA group is 0 or smaller than the preset minimum
number of active member links.
NOTE
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
Name Meaning
Possible Causes
The number of active member links in the PLA group is 0 or smaller than the preset minimum
number of active member links.
Procedure
Step 1 Check whether the specified minimum number of active links is consistent with the network
plan. If not, re-configure the minimum number of active links. For details, see querying PLA
group status.
----End
Related Information
None
A.3.242 PLA_MEMBER_DOWN_EXT
Description
The PLA_MEMBER_DOWN_EXT alarm is reported when a member link of a PLA group is
faulty.
Attribute
Alarm Severity Alarm Type
Minor QoS alarm
Parameters
Name Meaning
Parameter 1 and Indicate the ID of the PLA group. For example, 0x00 0x08
Parameter 2 indicates that the protection group ID is 8. For details, see
Parameter Examples.
Parameter 3 to Indicate the NE ID. For example, 0x00 0x09 0xac 0x02 indicates
Parameter 6 that the NE ID is 9-44034. That is, parameters 3 and 4 indicate the
extended ID, and parameters 5 and 6 indicate the basic ID.
Parameter 7 and Indicate the slot ID of the board. For example, 0x00 0x01 indicates
Parameter 8 that the slot ID is 1.
Parameter 9 Indicates the slot ID of the subboard. The parameter takes a fixed
value of 0xff.
Parameter 10 and
Indicate the port ID. For example, 0x00 0x05 indicates port 5.
Parameter 11
Possible Causes
l Cause 1: A member link of the PLA group is faulty on the local NE or cascaded NE.
l Cause 2: The hardware of an IF board in the PLA group is faulty on the local NE or
cascaded NE.
l Cause 3: The cascaded NE is faulty.
l Cause 4: The cascade port is faulty.
Procedure
Step 1 Cause 1: A member link of the PLA group is faulty on the local NE or cascaded NE.
1. Determine the faulty IF board and microwave link based on the ID of the PLA group.
For details, see querying the status of a PLA group.
2. Check whether a member link of the PLA group reports MW_LOF, MW_LIM,
MW_RDI, R_LOC, or R_LOF alarms. If any of the preceding alarms is reported, clear
it.
Step 2 Cause 2: The hardware of an IF board in the PLA group is faulty on the local NE or cascaded
NE.
1. Determine the faulty IF board based on the ID of the PLA group. For details, see
querying the status of a PLA group.
2. Check whether any IF board in the PLA group reports HARD_BAD, BD_STATUS,
VOLT_LOS, WRG_BD_TYPE, or RADIO_MUTE alarms. If any of the preceding
hardware-related alarms is reported, clear it.
----End
Related Information
A.3.243 PLA_PKT_ERR
Description
The PLA_PKT_ERR alarm indicates that packet reassembly fails in the receive direction.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameters 1 and 2 Indicate the ID of the PLA group.
Possible Causes
Cause 1: The clock tracing relationship is incorrectly configured for the active and standby
NEs.
Procedure
Step 1 Check whether the clock tracing relationship is correctly configured for the active and standby
NEs. If the clock tracing relationship is incorrect, configure the clock sources again. If the
clock tracing relationship is correct, go to the next step.
Step 2 Check for MW_LOF, MW_LIM, MW_RDI, and R_LOF alarms on links in the PLA group
and clear them if any. If no such alarm is reported, go to the next step.
Step 3 Check for the HARD_BAD alarm on the local and cascaded NEs. If the local or cascaded NE
reports the HARD_BAD alarm, replace the alarmed board by following instructions in 6.1
Replace the IDU.
----End
Related Information
None
A.3.244 PORTMODE_MISMATCH
Description
The PORTMODE_MISMATCH is an alarm indicating that the working mode of the remote
FE port does not match with that of the local FE port. This alarm is reported when the local
FE port works in auto-negotiation mode and the opposite FE port works in non-auto-
negotiation mode.
NOTE
Both GE and FE ports support the PORTMODE_MISMATCH alarm.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicate the working mode of the FE port.
Possible Causes
l Cause 1: The local port works in auto-negotiation mode and the opposite port works in
non-auto-negotiation mode.
Procedure
Step 1 Cause 1: The local port works in auto-negotiation mode and the opposite port works in non-
auto-negotiation mode.
1. Disable the opposite port. For details, refer to Setting the Basic Attributes of Ethernet
Ports.
2. Enable the opposite port and set work mode of the port to auto-negotiation. For details,
refer to Setting the Basic Attributes of Ethernet Ports.
----End
Related Information
None
A.3.245 PORT_EXC_TRAFFIC
Description
The PORT_EXC_TRAFFIC alarm indicates that the traffic over a port exceeds its threshold.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the traffic in the receive or transmit direction exceeds its threshold.
Possible Causes
l Cause 1: The configured bandwidth limit is too low.
l Cause 2: The port traffic is too high.
Procedure
Step 1 Cause 1: The configured bandwidth limit is too low.
1. Follow instructions in Configuring Traffic Shaping for Egress Queues to check the
configured bandwidth limit.
2. If the configured bandwidth limit is too low, follow instructions in Configuring Traffic
Shaping for Egress Queues to increase the bandwidth limit value or perform network
expansion.
----End
Related Information
None
A.3.246 PORT_MODULE_OFFLINE
Description
The PORT_MODULE_OFFLINE alarm indicates that a port is offline.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
The alarmed port is enabled but house no SFP module.
Procedure
Step 1 Cause: The alarmed port is enabled but house no SFP module.
1. Check whether the alarmed port needs to receive/transmit a service.
If... Then...
The alarmed port needs to receive/ Go to the next step.
transmit a service
The alarm port does not need to Follow instructions in Setting the Basic
receive/transmit a service Attributes of Ethernet Ports to disable the
alarmed port.
2. Check whether the alarmed port houses an SFP module.
If... Then...
The alarmed port houses no SFP Follow instructions in Installing an SFP
module Module to add an SFP module.
The alarmed port houses an SFP Go to the next step.
module
3. Re-install the SFP module.
If... Then...
The alarm clears No further action is required.
The alarm persists Follow instructions in Replacing an SFP Module to replace the
SFP module.
----End
Related Information
If a port is not configured with services, the port does not detect this alarm.
A.3.247 POWER_ABNORMAL
Description
The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the number of the voltage channel.
l 0x01: the first channel of voltage
l 0x02: the second channel of voltage
Name Meaning
Parameter 2 Indicates the type of the alarm.
l 0x00: voltage loss
l 0x01: undervoltage
l 0x02: overvoltage
Possible Causes
l Cause 1: The power cable is cut, damaged, or incorrectly connected.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The power cable is cut, damaged, or incorrectly connected.
1. Check whether the power cable is cut, damaged, or incorrectly connected. If the power
cable is cut or damaged, replace it with a proper power cable. If the power cable is
incorrectly connected, reconnect the power cable.
----End
Related Information
None
A.3.248 POWER_ALM
Description
The POWER_ALM is an alarm indicating that the power module is abnormal.
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
Name Meaning
Parameter 1 If the POWER_ALM alarm is reported on the IDU, this parameter indicates
the voltage channel ID.
If the POWER_ALM is reported on the ODU, this parameter indicates the type
of the power fault.
l 0x01: The -5 V power supply is faulty.
l 0x02: The power supply for the power amplifier is faulty.
Possible Causes
If the alarm is reported by the IDU, the possible causes are as follows:
l Cause 1: The input power or the PIU is abnormal.
l Cause 2: The power module is abnormal.
Procedure
Step 1 (POWER_ALM reported by the IDU) Cause 1: The input power or the PIU is abnormal.
1. Check whether alarms are reported on the PIU, If yes, clear these alarms immediately.
Step 2 (POWER_ALM reported by the IDU) Cause 2: The power module is abnormal.
1. Replace the IDU. For details, see 6 Part Replacement.
Step 3 (POWER_ALM reported on the ODU) Cause 1: The power module of the ODU is faulty.
1. Replace the ODU. For details, see 6.4 Replacing an ODU.
----End
Related Information
None
A.3.249 PRO_PKT_FLOODING
Description
The PRO_PKT_FLOODING alarm indicates that an NE has detected a protocol packet flood
attack. This alarm is reported when the rate of a type of protocol packets is greater than the
upper threshold for consecutive 30s.
Attribute
Alarm Severity Alarm Type
Parameters
Name Meaning
Parameters 1 to 2 Indicate the slot ID.
Possible Causes
Cause: The rate of a type of protocol packets is greater than the upper threshold for 30
consecutive seconds.
Procedure
Step 1 Check for and handle packet attacks on the network.
----End
Related Information
None
A.3.250 PPP_LCP_FAIL
Description
The PPP_LCP_FAIL is an alarm indicating an LCP negotiation failure. This alarm is reported
when the port uses the PPP encapsulation type and fails to negotiate with the opposite port.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: Parameter configurations on the opposite port are inconsistent with those on the
local port.
l Cause 2: The network is congested or its quality is poor, which causes improper running
of the LCP protocol.
l Cause 3: The physical link is interrupted.
Procedure
Step 1 Cause 1: Parameter configurations on the opposite port are inconsistent with those on the
local port.
1. On the NMS, check whether parameter configurations on the peer port are consistent
with those on the local port.
2. If the parameter configurations are inconsistent, modify the parameters. Then, check
whether the alarm is cleared.
3. For an optical interface, shut down and then start the laser. Then, check whether the
alarm is cleared.
Step 2 Cause 2: The network is congested or its quality is poor, which causes improper running of
the LCP protocol.
1. On the NMS, check whether the bandwidth for the tunnel connected to the ports is
configured low. For details, see Querying MPLS Tunnel Information.
2. If yes, configure the tunnel with a higher bandwidth. Then, check whether the alarm is
cleared.
----End
Related Information
None
A.3.251 PPP_NCP_FAIL
Description
The PPP_NCP_FAIL is an alarm indicating an NCP negotiation failure. This alarm is reported
when the NCP configuration attributes are inconsistent between the local and opposite NEs.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l The NCP configurations are inconsistent between the local and opposite NEs.
Procedure
Step 1 The NCP configurations are inconsistent between the local and opposite NEs.
1. Reconfigure the NCP attributes on the local and opposite NEs and ensure they are
consistent.
----End
Related Information
None
A.3.252 PTP_SOURCE_SWITCH
Description
The PTP_SOURCE_SWITCH is an alarm indicating a switchover between PTP time sources.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Parameter 2 Indicates the slot ID of the board before the switching.
Parameter 3 Indicates the ID of the subboard before the switching. 0xFF
indicates that there is no subboard.
Parameter 4, Parameter 5 Indicates the ID of the port before the switching.
Parameters 6 to 9 Indicates the ID 1 of the grandmaster clock before the
switching.
Parameters 10 to 13 Indicates the ID 2 of the grandmaster clock before the
switching.
Parameter 14, Parameter 15 Indicates the slot ID of the board after the switching.
Parameter 16 Indicates the ID of the subboard after the switching. 0xFF
indicates that there is no subboard.
Parameter 17, Parameter 18 Indicates the ID of the port after the switching.
Parameters 19 to 22 Indicates the ID 1 of the grandmaster clock after the switching.
Parameters 23 to 26 Indicates the ID 2 of the grandmaster clock after the switching.
Possible Causes
l Cause 1: The physical link between the local NE and the clock source is faulty.
l Cause 2: Information about the grandmaster clock such as the priority 1, quality level,
and priority 2 has changed.
l Cause 3: The network topology has changed.
Procedure
Step 1 Cause 1: The physical link between the local NE and the clock source is faulty.
1. Check the physical link between the NE and the clock source for troubleshooting.
Step 2 Cause 2: Information about the grandmaster clock such as the priority 1, quality level, and
priority 2 has changed.
1. If NE configurations are correct, no further action is required.
----End
Related Information
None
A.3.253 PTP_TIMESTAMP_ABN
Description
The PTP_TIMESTAMP_ABN is an alarm indicating an exception of the PTP timestamp. This
alarm is reported when the PTP (IEEE 1588V2) timestamp 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x02: indicates that timestamp t1 remains unchanged in three consecutive
seconds.
l 0x03: indicates that timestamp t2 remains unchanged in three consecutive
seconds.
l 0x04: indicates that timestamps t1 and t2 remain unchanged in three
consecutive seconds.
Parameter 2 l 0x02: indicates that timestamp t3 remains unchanged in 17 consecutive
seconds.
l 0x03: indicates that timestamp t4 remains unchanged in 17 consecutive
seconds.
l 0x04: indicates that timestamps t3 and t4 remain unchanged in 17
consecutive seconds.
Possible Causes
l Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
l Cause 2: The transmit NE is faulty.
l Cause 3: The receive NE is faulty.
Procedure
Step 1 Cause 1: The P/E attributes are different on the PTP ports of the local and opposite NEs.
1. Reconfigure the P/E attribute. For details, see Setting the PTP NE Attributes.
----End
Related Information
None
A.3.254 PW_DOWN
Description
The PW_DOWN alarm indicates that a PW is disconnected.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Parameter 4 Indicate the index number of the faulty service.
Parameter 5 to Parameter 8 Indicate the running status at the local end.
Parameter 9 to Parameter 12 Indicate the running status at the peer end.
Possible Causes
l Cause 1: Configurations are changed at the peer end.
l Cause 2: Severe network congestion occurs.
l Cause 3: The physical link is faulty.
l Cause 4: The peer NE is faulty.
Procedure
Step 1 Cause 1: Configurations are changed at the peer end.
1. Check whether PW configurations are consistent at both ends. If the configurations are
inconsistent, rectify the configurations.
----End
A.3.255 PW_DROPPKT_EXC
Description
The PW_DROPPKT_EXC alarm indicates that the packet loss ratio on a PW exceeds its
threshold.
Attribute
Parameters
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Has a fixed value of 0x00, indicating that the traffic in the ingress or egress
direction crosses its threshold.
Possible Causes
Cause: A small number of packets are lost on the alarmed PW.
Procedure
Step 1 Cause: A small number of packets are lost on the alarmed PW.
1. Follow instructions in Querying Information and Running Status of PWs to check the
bandwidth utilization of the alarmed PW. If the PW bandwidth is exhausted, increase the
bandwidth or eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
A.3.256 PW_NO_TRAFFIC
Description
The PW_NO_TRAFFIC is an alarm indicating that a PW has no traffic. This alarm is reported
when the PW that carries services has no traffic.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: No service is configured.
l Cause 2: The local services are abnormal and therefore no packet is transmitted to the
peer end.
l Cause 3: The peer services are abnormal and therefore no packet is transmitted to the
local end.
l Cause 4: The port that corresponds to the faulty works improperly.
Procedure
Step 1 Determine the alarmed port, and direction in which traffic is unavailable according to the
alarm information on the NMS.
If... Then...
If... Then...
0x00 Go to Step 4.
0x01 Go to Step 3.
Step 3 Cause 2: The local services are abnormal and therefore no packet is transmitted to the peer
end.
1. Check whether the local PW services are correctly configured. For details, see Querying
Information and Running Status of PWs.
Step 4 Cause 3: The peer services are abnormal and therefore no packet is transmitted to the local
end.
1. Check whether the opposite PW services are correctly configured.
Step 5 Cause 4: The port that corresponds to the faulty works improperly.
1. Replace the IDU.For details, see 6 Part Replacement.
2. Check whether the alarm is cleared. If the alarm persists, Replace the opposite NE.
----End
Related Information
None
A.3.257 PWAPS_LOST
Description
The PWAPS_LOST is an alarm indicating that the APS frame is lost. This alarm occurs when
no APS frame is received from the protection channel.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The remote NE of the PW is not configured with any protection group.
l Cause 2: The service on the protection channel is interrupted.
Procedure
Step 1 Cause 1: The remote NE of the PW is not configured with any protection group.
1. Check whether the remote NE of the PW is configured with a protection group. If yes,
ensure that the configuration is the same at the two ends.
Step 2 Cause 2: The service on the protection channel is interrupted.
1. Check whether the protection channel is faulty. If yes, rectify the fault.
----End
Related Information
None
A.3.258 PWAPS_PATH_MISMATCH
Description
The PWAPS_PATH_MISMATCH is an alarm indicating that the working and protection paths
of the APS protection group differ between the two ends. This alarm is reported when the
working and protection paths of one APS protection group at one end are different from those
at the other end.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The configured working and protection paths differ between the two ends.
l Cause 2: Certain physical links are incorrectly connected.
Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
----End
Related Information
None
A.3.259 PWAPS_SWITCH_FAIL
Description
The PWAPS_SWITCH_FAIL is an alarm indicating a switching failure of the PW APS
protection group. This alarm is reported when the request signal in the transmitted Automatic
Protection Switching (APS) frame is different from the bridge signal in the received APS
frame and this symptom lasts for 50 ms.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The configured working and protection paths differ between the two ends.
l Cause 2: Certain physical links are incorrectly connected.
Procedure
Step 1 Cause 1: The configured working and protection paths differ between the two ends.
1. Check whether the APS settings at the two ends are the same.
2. If the APS settings are different, change the settings to the same.
----End
Related Information
None
A.3.260 PWAPS_TYPE_MISMATCH
Description
The PWAPS_TYPE_MISMATCH is an alarm indicating that the local NE and the opposite
NE are configured with different PW protection types. This alarm occurs when the
information in the received APS frames is inconsistent with the APS protection scheme
configured at the local end.
Attribute
Parameters
None
Possible Causes
l Cause 1: The configured protection modes (1+1 protection or 1:1 protection) differ at the
two ends of the PW.
l Cause 2: The configured switching modes (single-ended or dual-ended) differ at the two
ends of the PW.
l Cause 3: The configured revertive modes (revertive or non-revertive) differ at the two
ends of the PW.
Procedure
Step 1 Check whether the APS protection settings, such as protection mode, switching mode, and
revertive mode, are the same at the local and remote ends. For details, see Querying PW APS
Status.
Step 2 If the APS protection settings are different, change the settings to the same.
----End
Related Information
None
A.3.261 PWD_ENCRYPT_RISK
Description
The PWD_ENCRYPT_RISK alarm indicates that the user password encryption mode of an
NE has security risks.
Attribute
Parameters
None
Possible Causes
Cause: The user password encryption mode of the NE is MD5 or SHA256.
Procedure
Step 1 In the NE Explorer, click the NE and choose Security > NE User Password Encryption
Management. Change Encryption Type to PBKDF2.
----End
Related Information
None
A.3.262 PW_APS_DEGRADED
Description
The PW_APS_DEGRADED alarm indicates that a PW automatic protection switching (APS)
protection group is degraded. This alarm is reported when a PW in the protection group is
faulty and availability of the protection group declines. This alarm is cleared when both the
working and protection PWs are functional or faulty.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause: A PW in the protection group is faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.
Step 2 Check whether a PWAPS_PATH_MISMATCH alarm is reported. If the alarm is reported,
handle the alarm.
----End
Related Information
None
A.3.263 PW_APS_OUTAGE
Description
The PW_APS_OUTAGE alarm indicates that a PW automatic protection switching (APS)
protection group is unavailable. This alarm is reported when both the working and protection
PWs in the protection group are faulty and the protection group is unavailable. This alarm is
cleared when a PW becomes available.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause: The working and protection PWs in the protection group are faulty.
Procedure
Step 1 Check whether the PWs in the protection group are correctly configured. If the PWs are
incorrectly configured, rectify the configurations.
----End
Related Information
None
A.3.264 R_LOC
Description
The R_LOC is an alarm indicating that the clock is lost on the receive line side. This alarm is
reported when the IF board fails to extract clock signal from the IF signal.
Attribute
Parameters
None
Possible Causes
l Cause 1: The receive unit of the local site is faulty.
l Cause 2: The transmit unit of the opposite station is faulty.
Procedure
Step 1 Cause 1: The receive unit of the local site is faulty.
1. At the local end, perform an inloop on the port of the alarmed board. For details, see 8.4
Software Loopback.
If... Then...
The alarm persists after the loopback Replace the IDU.
The alarm is cleared after the loopback Go to Cause 2.
----End
Related Information
None
A.3.265 R_LOF
Description
The R_LOF is an alarm indicating that frames are lost on the receive side.
Attribute
Parameters
None
Possible Causes
l Cause 1: Certain alarms are generated (if the alarm is reported by an IF board).
l Cause 2: The line performance degrades (if the alarm is reported by an SDH optical
interface board).
l Cause 3: The transmit unit of the opposite station is faulty.
l Cause 4: The receive unit of the local site is faulty.
Procedure
Step 1 Cause 1: Certain high-level alarms are generated (if the alarm is reported by an IF board).
1. If the alarm is reported by the IF board, check whether the MW_BER_EXC,
MW_BER_SD, MW_FEC_UNCOR alarm is generated.
If... Then...
Step 2 Cause 2: The line performance degrades (if the alarm is reported by an SDH optical interface
board).
1. If the alarm is reported by an optical interface board, exchange the transmit and receive
fiber jumpers at both ends.
If... Then...
The line port of the opposite station Troubleshoot the optical fibers.
reports the R_LOF alarm
----End
Related Information
None.
A.3.266 R_LOS
Description
For IF boards, the R_LOS alarm indicates that microwave frames are lost on the receive line
side. For SDH line boards, the R_LOS alarm indicates that signals are lost on the receive line
side. For TDM cascading interface boards, the R_LOS alarm indicates that cascading signals
are lost on the receive line side.
Attribute
Alarm Severity Alarm Type
Critical Communication alarm
Parameters
None
Possible Causes
l Cause 1: Other alarms trigger the R_LOS alarm (if the R_LOS alarm is reported by an IF
board).
l Cause 2: The line performance deteriorates (if the R_LOS alarm is reported by an SDH
line board).
l Cause 3: The TDM cascade cable connection is abnormal (if the R_LOS alarm is
reported by a TDM cascading interface board).
l Cause 4: The transmit unit of the peer NE is faulty.
l Cause 5: The receive unit of the local NE is faulty.
l Cause 6: No fiber jumper is connected to the optical port on the board that reports the
R_LOS alarm.
l Cause 7: The laser on the peer NE is closed.
l Cause 8: A fiber cut occurs on the transmission line.
l Cause 9. The optical loss is beyond the normal range.
Procedure
Step 1 Cause 1: Other alarms trigger the R_LOS alarm (if the R_LOS alarm is reported by an IF
board).
1. If the R_LOS alarm is reported by an IF board, check for and clear any
MW_BER_EXC, MW_BER_SD, and MW_FEC_UNCOR alarms on the IF board. If
no such alarm exists, go to the next step.
2. Set an inloop on the IF port that reports the R_LOS alarm.
3. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 2 Cause 2: The line performance deteriorates (if the R_LOS alarm is reported by an SDH line
board).
1. If the R_LOS alarm is reported by an SDH line board, exchange the transmit and receive
fiber jumpers at both ends.
2. If the peer line port reports an R_LOF alarm after fiber jumpers are exchanged, go to
Cause 8.
3. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 3 Cause 3: The TDM cascade cable connection is abnormal (if the R_LOS alarm is reported by
a TDM cascading interface board).
1. If the R_LOS alarm is reported by a TDM cascading interface board, check whether the
TDM cascade cable is properly connected and functional. If the cable is not properly
connected, connect it properly. If the cable is faulty, replace it.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 4 Cause 4: The transmit unit of the peer NE is faulty.
1. Replace the peer NE.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 5 Cause 5: The receive unit of the local NE is faulty.
1. Replace the IDU.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 6 Cause 6: No fiber jumper is connected to the optical port on the board that reports the R_LOS
alarm.
1. Check fiber connections and ensure that fiber jumpers are properly connected.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 7 Cause 7: The laser on the peer NE is closed.
1. Turn on the laser on the peer NE.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 8 Cause 8: A fiber cut occurs on the transmission line.
1. Test the transmission line connectivity, identify the cause of fiber cuts, and re-connect or
replace related optical fibers.
2. If the R_LOS alarm persists, perform the operations required when the R_LOS alarm is
reported due to the other causes.
Step 9 Cause 9. The optical loss is beyond the normal range.
1. Check whether there are any blocks in the microwave transmission path or in the near
field of the antenna. If there are any blocks in the microwave transmission path or in the
near field of the antenna, adjust the mounting height of the antenna to ensure good line
of sight (LOS) or re-plan the microwave link route.
2. Verify that the optical power of the optical module at the transmit end matches that of the
optical module at the receive end.
3. Check whether loss increases because the antenna, hybrid coupler, or flexible waveguide
is damaged or wet. If loss increases because any of the preceding components are
damaged or wet, replace the faulty components.
4. If the R_LOS alarm persists, contact Huawei technical support engineers to handle the
alarm.
----End
Related Information
The handling procedure also applies when the R_LOS alarm is reported by an STM-1e port.
A.3.267 R_OOF
Description
The R_OOF is an alarm indicating an out-of-frame event on the receive side of the line.
Attribute
Parameters
None
Possible Causes
l Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated.
l Cause 2: The receive board on the local NE is faulty.
l Cause 3: The transmit board on the opposite NE is faulty.
Procedure
Step 1 Cause 1: The transmit cable is faulty, and the fiber connector is loose or contaminated.
1. Check whether the transmit optical power of the board connected to the board that
reports the alarm is within the normal range.
If... Then...
The transmit optical power of the opposite board is normal Go to the next step.
2. On the NMS, check whether the receive optical power of the local board is within the
normal range.
If... Then...
The receive optical power of the local board is too low Go to the next step.
The receive optical power of the local board is too high Go to Step 2.
3. Check whether the bend radius of the fiber jumper is within the normal range. If the bend
radius is less than 6 cm, re-roll the tail fiber. Check whether the alarm is cleared.
4. If the alarm persists, check whether the optical interface on the board is firmly connected
to the fiber jumper. Ensure that the fiber connector is firmly connected. Then, check
whether the R_LOS alarm is cleared.
5. If the alarm persists, check whether the fiber connector is contaminated. If yes, clean the
fiber and fiber connector. For details, see 8.11 Cleaning Fiber Connectors and
Adapters.
6. Check whether the optical cable is aged out, damaged, or pressed. If yes, replace the
optical cable.
NOTICE
A loopback causes service interruption. To prevent optical power overload during
hardware inloop, you can add an optical attenuator to the optical interface according to
the optical power specifications of the board.
If... Then...
The alarm persists The local board is faulty. Go to the next step.
2. Replace the board that reports the R_OOF alarm on the local NE. If the board supports
the pluggable optical module, replace the pluggable optical module. For details, see 6.3
Replacing the SFP. Otherwise, replace the faulty board. For details, see 6.1 Replace the
IDU.
----End
Related Information
None
A.3.268 RADIO_FADING_MARGIN_INSUFF
Description
The RADIO_FADING_MARGIN_INSUFF is an alarm indicating that the mean receive
power of the ODU is lower than the threshold of the receive power (the threshold value is
about the receiver sensitivity + 14 dB).
When the receive power of the ODU in consecutive six hours is lower than the threshold, the
system reports the alarm. When the mean receive power of the ODU becomes normal and
lasts for three minutes after the alarm is reported, the alarm is cleared.
Attribute
Parameters
None
Possible Causes
l Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
l Cause 2: The direction of the antenna is deflected.
l Cause 3: The transmission environment changes.
l Cause 4: The fade margin in the case of rain and fog in the network planning is
insufficient.
Procedure
Step 1 Cause 1: The ODU fault of the transmit end causes the abnormal transmit power.
1. Check whether the ODU at the transmit end reports the RADIO_TSL_LOW alarm.
If... Then...
The ODU at the transmit end reports the Handle the RADIO_TSL_LOW
RADIO_TSL_LOW alarm alarm.
The ODU at the transmit end does not report the Go to Cause 2.
RADIO_TSL_LOW alarm
If... Then...
The direction of the antenna is deflected Adjust the direction of the antenna.
The direction of the antenna is not deflected Go to Cause 3.
If... Then...
The transmission environment Contact the network planning department for re-
changes planning the transmission trail.
The transmission environment does Go to Cause 4.
not change
Step 4 Cause 4: The fade margin in the case of rain and fog in the network planning is insufficient.
1. If the alarm is reported frequently, contact the network planning department to increase
the fade margin by re-planning the transmission trail.
----End
Related Information
None
A.3.269 RADIO_MUTE
Description
The RADIO_MUTE is an alarm indicating that radio transmitter is muted.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The other alarms are generated.
l Cause 2: The transmitter of the local site is muted manually.
l Cause 3: The IF board is faulty, causing abnormal IF output.
l Cause 4: The data output is abnormal because the ODU is faulty.
Procedure
Step 1 Cause 1: The other alarms are generated.
1. Check whether the CONFIG_NOSUPPORT or IF_INPWR_ABN alarm is generated.
If yes, take priority to clear the alarm.
Step 4 Cause 4: The data output is abnormal because the ODU is faulty.
1. Replace the ODU.
----End
Related Information
None
A.3.270 RADIO_RSL_BEYONDTH
Description
The RADIO_RSL_BEYONDTH is an alarm indicating that the antennas are not aligned.
When the receive power is set on the NE, the NE enables the antenna alignment indication
function. If the actual receive power of the ODU is lower than the power to be received 3 dB,
the RADIO_RSL_BEYONDTH alarm is reported. Then, if the antennas are aligned for
continuous 30 minutes, the antenna alignment indication function is disabled automatically.
Afterwards, the RADIO_RSL_BEYONDTH alarm is reported only when the
RADIO_FADING_MARGIN_INSUFF alarm is reported.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
l Cause 1: Antennas are not aligned during the equipment commissioning.
l Cause 2: The RADIO_FADING_MARGIN_INSUFF is reported when the NE is
running.
Procedure
Step 1 Cause 1: Antennas are not aligned during the equipment commissioning.
1. Align the antennas, and ensure that the actual receive power is within the range of preset
receive power +/-3 dB.
----End
Related Information
None
A.3.271 RADIO_RSL_HIGH
Description
The RADIO_RSL_HIGH is an alarm indicating that the radio receive power is very 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
None
Possible Causes
l Cause 1: The local ODU is faulty.
l Cause 2: There is a strong interference source nearby.
l Cause 3: The transmit power of the opposite ODU is very high.
Procedure
Step 1 Cause 1: The local ODU is faulty.
1. 6.4 Replacing an ODU.
Step 3 Cause 3: The transmit power of the opposite ODU is very high
1. Reset the transmit power of the ODU at the opposite end. For details, see Configuring a
Single-Hop Radio Link.
----End
Related Information
None
A.3.272 RADIO_RSL_LOW
Description
The RADIO_RSL_LOW is an alarm indicating that the radio receive power is very low. This
alarm is reported if the detected receive power is equal to or lower than the upper threshold of
the ODU (The upper threshold is 80 dBm for the 112 MHz channel bandwidth and 90
dBm for the other channel bandwidths).
Attribute
Parameters
None
Possible Causes
l Cause 1: Other alarms occur at the opposite station.
l Cause 2: The transmit power of the opposite station is very low.
l Cause 3: The local ODU is faulty.
l Cause 4: Signal attenuation on the radio link is very heavy.
Procedure
Step 1 Cause 1: Other alarms occur at the opposite station.
Check whether any of the following alarms is generated in the equipment of the opposite
station. If yes, take priority to clear the alarm.
l RADIO_MUTE
l CONFIG_NOSUPPORT
l RADIO_TSL_LOW
l BD_STATUS
Step 2 Cause 2: The transmit power of the opposite station is very low.
1. See Configuring a Single-Hop Radio Link. Check whether the transmit power of the
opposite station is normal. If not, replace the ODU of the opposite station.
Step 3 Cause 3: The local ODU is faulty.
1. Replace the ODU at the local end.
Step 4 Cause 4: Signal attenuation on the radio link is very heavy.
1. Browse history alarms and check whether the alarm is generated continuously.
If the alarm is generated occasionally, contact the network planning department to
change the design to increase the anti-fading performance.
2. Check whether the antennas at both ends are adjusted properly.
If not, align the antennas again.
3. Check whether any mountain or building obstacle exists in the transmit direction.
If yes, contact the network planning department for proper modification of the planning
design, hence preventing the block of the mountain or building obstacle.
4. Check whether the polarization direction of the antenna, ODU, and hybrid coupler is set
correctly.
If not, correct the polarization direction.
5. Check whether the outdoor units such as antennas, hybrid coupler, ODU, and flexible
waveguide are wet, damp, or damaged.
If yes, replace the unit that is wet, damp, or damaged. For the operations, see 6 Part
Replacement
6. Check whether the antenna gain at both the transmit and receive ends meets the
requirement.
----End
Related Information
None
A.3.273 RADIO_TSL_HIGH
Description
The RADIO_TSL_HIGH is an alarm indicating that the radio transmit power is too high. This
alarm is reported when the detected transmit power is higher than the upper power threshold
of the ODU.
Attribute
Parameters
None
Possible Causes
Cause 1: The local ODU is faulty.
Procedure
Step 1 Cause 1: The local ODU is faulty.
1. Replace the ODU.
----End
Related Information
None
A.3.274 RADIO_TSL_LOW
Description
The RADIO_TSL_LOW is an alarm indicating that the radio transmit power is very low. This
alarm is reported when the detected transmit power is less than the lower power threshold of
the ODU.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
Cause 1: The local ODU is faulty.
Procedure
Step 1 Cause 1: The local ODU is faulty.
1. Replace the ODU.
----End
Related Information
None
A.3.275 RELAY_ALARM_CRITICAL
Description
The RELAY_ALARM_CRITICAL is an alarm indicating the critical alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to critical and there is such
an alarm input.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
Cause 1: There is a critical alarm input.
Procedure
Step 1 Cause 1: There is a critical alarm input.
1. Clear the alarms of the external equipment according to the defined meanings of the
alarms. Then, the RELAY_ALARM_CRITICAL alarm is cleared.
----End
Related Information
None
A.3.276 RELAY_ALARM_IGNORE
Description
The RELAY_ALARM_IGNORE is an alarm indicating the warning alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to warning and there is such
an alarm input.
Attribute
Alarm Severity Alarm Type
Warning Equipment alarm
Parameters
None
Possible Causes
Cause 1: There is a warning alarm input.
Procedure
Step 1 Cause 1: There is a warning alarm input.
1. Clear the alarms of the external equipment according to the defined meanings of the
alarms. Then, the RELAY_ALARM_IGNORE alarm is cleared.
----End
Related Information
None
A.3.277 RELAY_ALARM_MAJOR
Description
The RELAY_ALARM_MAJOR is an alarm indicating the major alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to major and there is such an
alarm input.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: There is a major alarm input.
Procedure
Step 1 Cause 1: There is a major alarm input.
1. Clear the alarms of the external equipment according to the defined meanings of the
alarms. Then, the RELAY_ALARM_MAJOR alarm is cleared.
----End
Related Information
None
A.3.278 RELAY_ALARM_MINOR
Description
The RELAY_ALARM_MINOR is an alarm indicating the minor alarm inputs. This alarm
occurs when the user sets the severity of an available alarm input to minor and there is such
an alarm input.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: There is a minor alarm input.
Procedure
Step 1 Cause 1: There is a minor alarm input.
1. Clear the alarms of the external equipment according to the defined meanings of the
alarms. Then, the RELAY_ALARM_MINOR alarm is cleared.
----End
Related Information
None
A.3.279 RPS_INDI
Description
The RPS_INDI is an alarm indicating that the radio protection switching is detected.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the protection group.
Parameter 2 Indicates the type of protection switching.
0x01: HSB protection switching
Possible Causes
l The possible causes of the HSB protection switching are as follows:
Cause 1: An external switching event occurs
Cause 2: An automatic switching event occurs.
Cause 3: A reverse switching event occurs.
Procedure
Step 1 Determine the type of the protection switching based on the alarm parameters.
Step 2 Cause 1 of HSB switching: An external switching event occurs. That is, the NMS issues a
command to trigger the switching.
1. Check whether the switching is the forced switching or manual switching. For details,
see Querying the IF 1+1 Protection Status.
If... Then...
The switching is the forced switching or Find the cause and release the switching
manual switching immediately.
The switching is not the forced switching Go to Cause 2 of HSB switching.
or manual switching
Step 3 Cause 2 of HSB switching: An automatic switching event occurs. That is, the equipment is
faulty, or the service is defective.
1. Check whether the following faults or alarms occur. If yes, rectify the faults or clear the
alarms.
The hardware of the IF unit or the ODU is faulty.
VOLT_LOS
RADIO_TSL_HIGH, RADIO_TSL_LOW, or RADIO_RSL_HIGH
IF_INPWR_ABN or CONFIG_NOSUPPORT
If the switching is non-revertive, the services are not automatically switched to the working
path when the working path is restored to normal, and the RPS_INDI alarm persists. In this
case, you need to manually switch the services from the protection path to the working path.
The RPS_INDI alarm is cleared only when the switching is successful.
If the switching is revertive, the services are automatically switched to the working path only
when the specified wait-to-restore (WTR) time expires after the working path is restored to
normal. The RPS_INDI alarm is cleared only when the switching is successful.
----End
Related Information
None
A.3.280 RS_CROSSTR
Description
The RS_CROSSTR is an alarm indicating that a regenerator section performance indicator
crosses the threshold. This alarm is reported if a board detects that a regenerator section bit
error performance event crosses the preset threshold.
Attribute
Alarm Severity Alarm Type
Minor Service alarm
Parameters
Name Meaning
Parameter 1 Indicates the performance monitoring period:
l 0x01: 15 minutes
l 0x02: 24 hours
Name Meaning
Parameter 2, Parameter 2 is always 0x00. Parameter 3 indicate the ID of a
Parameter 3 performance event that causes the alarm and has the following
meanings:
l 0x01: RSBBE
l 0x02: RSES
l 0x03: RSSES
l 0x04: RSOOF
l 0x05: RSOFS
l 0x06: RSUAS
Possible Causes
l Cause 1: Services are interrupted for a long time.
l Cause 2: The regenerator section bit error performance indicator crosses the preset
threshold.
Procedure
Step 1 Cause 1: Services are interrupted for a long time.
NOTE
Handle the alarm as follows if the value of parameter 3 is 0x06:
1. Check whether fibers are properly connected. If not, connect the fibers again according
to planning information.
2. Check whether cross-connections are configured for service ports. If not, configure
cross-connections again according to planning information.
Step 2 Cause 2: The regenerator section bit error performance indicator crosses the preset threshold.
1. Find out the performance event that crosses the preset threshold. For details, see 4.3.5
Browsing the Performance Event Threshold-Crossing Records.
2. Handle the performance event that crosses the threshold.
----End
Related Information
None
A.3.281 RTC_FAIL
Description
The RTC_FAIL is an alarm indicating that the real-time clock (RTC) on the system control
board fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The RTC on the system control unit is abnormal.
l Cause 2: The unit temperature is too high.
Procedure
Step 1 Cause 1: The RTC on the system control unit is abnormal.
1. 6.1 Replace the IDU.
Step 2 Cause 2: The unit temperature is too high.
1. 4.3.1 Browsing Current Alarms, and if theunit reports the TEMP_ALARM alarm,
clear this alarm first.
----End
Related Information
None
A.3.282 RT_TBL_LACK
Description
The RT_TBL_LACK alarm indicates that routing table resources are insufficient.
Attribute
Alarm Severity Alarm Type
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
Parameters 1-4 Indicate the IP address.
Possible Causes
The number of routes or next hops in the routing table exceeds the maximum number
allowed.
Procedure
Step 1 Reduce service routes by re-planning services.
----End
Related Information
None
A.3.283 S1_SYN_CHANGE
Description
The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte
mode.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 0x01: system priority list
Possible Causes
When the SSM protocol or extended SSM protocol is enabled.
Procedure
Step 1 Cause 1: The original clock source is lost.
1. Handle the SYNC_C_LOS alarm that is related to the original clock source.
----End
Related Information
None
A.3.284 SEC_RADIUS_FAIL
Description
The SEC_RADIUS_FAIL is an alarm indicating that RADIUS authentication fails over many
times. This alarm is reported when the RADIUS authentication fails for five consecutive
times.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Parameter 16 Indicates the username.
Possible Causes
l Cause 1: The active period of the account expires.
l Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and
access policies.
l Cause 3: There are unauthenticated login attempts.
l Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
Procedure
Step 1 Cause 1: The active period of the account expires.
1. Use an active account.
Step 2 Cause 2: Configurations on the RADIUS server are incorrect, such as passwords and access
policies.
1. Enter the correct password.
2. Set correct access policies.
Step 4 Cause 4: The shared key for the NE and the RADIUS server is configured incorrectly.
1. Set the shared key correctly.
----End
Related Information
None
A.3.285 SECU_ALM
Description
The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the terminal type used in the login attempt.
Parameters 2 and 3 Indicate the errors that occur in the login attempt.
Parameters 4 and 5 Indicate the first two characters of the user name.
Possible Causes
An illegal user tries to log in to the NE.
Procedure
Step 1 An illegal user tries to log in to the NE.
1. Query the NE log to check the user name that is used for the login.
----End
Related Information
After a user fails to log in to an NE for five consecutive times (if the interval between two
logins is less than 3 minutes, the two logins are consecutive logins), the SECU_ALM alarm is
reported upon each subsequent login failure and meanwhile the user is locked for 900
seconds. During the 900 seconds, the user cannot log in to the NE.
A.3.286 SOFTWARE_UNCOMMIT
Description
The SOFTWARE_UNCOMMIT alarm indicates that the board software is unauthorized. This
alarm is reported when the software version of a board is later than that of the system control
board and is unauthorized.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: The board software is unauthorized.
Procedure
Step 1 Load the software license to the board.
----End
Related Information
None
A.3.287 SRV_SHUTDOWN_LD
Description
The SRV_SHUTDOWN_LD alarm indicates that an Ethernet service is deactivated. This
alarm is reported when an Ethernet service is deactivated due to a service loop. This alarm is
cleared after the Ethernet service is reactivated.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is
deactivated.
Procedure
Step 1 Cause 1: A loop occurs in an Ethernet service and therefore the Ethernet service is
deactivated.
1. Check whether a service is looped back on the path of the alarmed Ethernet service.
2. Re-configure the preceding service based on the network plan.
----End
Related Information
None
A.3.288 SSL_CERT_DAMAGED
Description
The SSL_CERT_DAMAGED is an alarm indicating that a user-customized SSL certificate
file is damaged. This alarm is reported to notify the user to rectify the SSL certificate file and
is cleared after the file is rectified.
Attribute
Parameters
None
Possible Causes
Cause: The user-customized SSL certificate file is damaged.
Procedure
Step 1 Cause: The user-customized SSL certificate file is damaged.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
A.3.289 SSL_CERT_NOENC
Description
SSL_CERT_NOEN indicates the certificate file of SSL is not encrypted.
Attribute
Alarm Severity Alarm Type
Major Equipment Alarm
Parameters
None
Possible Causes
Cause: Certificate file of SSL is not encrypted.
Procedure
Step 1 Cause: Certificate file of SSL is not encrypted.
1. Download and verify the encrypted SSL certificate by NMS.
----End
Related Information
None
A.3.290 SSL_CERT_TO_EXPIRE
Description
The SSL_CERT_TO_EXPIRE alarm indicates that a customized SSL certificate file is about
to expire. This alarm is reported when a customized SSL certificate file will expire after two
months to prompt users to reload and activate the SSL certificate file. This alarm is
automatically cleared after the SSL certificate file is reloaded and activated.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the certificate type.
Possible Causes
Cause: A customized SSL certificate file is about to expire.
Procedure
Step 1 Cause: A customized SSL certificate file is about to expire.
1. Log in to the U2000, and load and activate the customized SSL certificate file again. For
details, see the section about loading board-level software in the iManager U2000
Product Documentation.
----End
Related Information
None
A.3.291 STORM_CUR_QUENUM_OVER
Description
The STORM_CUR_QUENUM_OVER alarm is reported when the number of alarms on an
NE is only one less than the maximum length of the alarm list.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
The current alarm list is full.
Procedure
Step 1 Browse current alarms and clear alarms that are frequently reported.
Step 2 This alarm automatically clears when the number of alarms in the alarm list drops to a certain
value.
----End
Related Information
None
A.3.292 SUBNET_RT_CONFLICT
Description
The SUBNET_RT_CONFLICT is an alarm indicating a subnetwork route conflict. This alarm
occurs when the subnet route of an NMS port, that is, the IP subnet route of an NE, covers the
learned route of an OSPF subnet whose mask is longer than that of the IP subnet.
Attribute
Alarm Severity Alarm Type
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 to Indicate the IP address of the subnet whose route is covered by the NE
Parameter 4 IP subnet route and whose mask is longer than that of the NE IP
subnet. When the routes of multiple subnets are covered by the IP
subnet route, this parameter is the IP address of the subnet with the
longest mask.
Parameter 5 Indicates the mask length.
Possible Causes
The subnet route of an NMS port (the IP subnet route of an NE) covers the learned route of an
OSPF subnet whose mask is longer than that of the IP subnet.
Procedure
Step 1 Collect the information about all NEs that report this alarm and check the DCN networking
based on the planned network topology.
Step 2 Obtain the information about the conflicting subnets and their masks based on the alarm
parameters.
Step 3 Determine the rectification plan based on the network topology and subnet information to
ensure that the subnet masks of non-gateway NEs are consistent with the mask of the gateway
NE. When subnet masks of multiple NEs need to be changed, change their subnet masks from
the farthest NE to the nearest one.
CAUTION
If the mask of a gateway NE needs to be changed, ensure that the DCN route after the change
is correct. If the DCN route is incorrect, NEs may be unreachable to the NMS.
----End
Related Information
The SUBNET_RT_CONFLICT alarm is generally caused by incorrect configurations of
subnet masks on NEs. For example, NE1 and NE2 are connected using air interfaces and the
OSPF protocol is enabled. The communication parameters and routing information of the two
NEs are listed in the following table.
If the NMS whose IP address is 129.9.0.254 is connected to the NMS port of NE1, the route
of packets transmitted from NE1 to the NMS is "129.9.0.0/255.255.255.0/129.9.0.2/OSPF/air
interface" according to the longest match principle. That is, the packets are transmitted from
the air interface of NE1 to the air interface of NE2 and finally to the NMS port of NE2.
Therefore, the NMS cannot manage NE1 properly.
NE Parameter
A.3.293 SWDL_ACTIVATED_TIMEOUT
Description
The SWDL_ACTIVATED_TIMEOUT is an alarm indicating the activation timeout of the
software package. During the package loading, the system reports the alarm if no data is
submitted within 30 minutes after activation of the NE software.
Attribute
Alarm Severity Alarm Type
Critical Processing alarm
Parameters
None
Possible Causes
l Cause 1: The package loading or diffusion task is suspended during package activation.
l Cause 2: The radio link is faulty. As a result, the NE involved in the package loading
fails to receive the submit command.
Procedure
Step 1 Cause 1: The package loading or diffusion task is suspended during package activation.
1. Restart the package loading or diffusion task.
Step 2 Cause 2: The radio link is faulty. As a result, the NE involved in the package loading fails to
receive the submit command.
1. Check whether the radio link is faulty.
If... Then...
The radio link is faulty Troubleshoot the radio link to ensure that the link
between the nodes to be loaded is normal.
The radio link is normal Perform the package loading to the NE again.
----End
Related Information
None
A.3.294 SWDL_AUTOMATCH_INH
Description
The SWDL_AUTOMATCH_INH is an alarm indicating that the automatic match function is
disabled. When the automatic match function of the board is disabled, the system reports the
alarm if the board cannot match the software from the system control board.
Attribute
Parameters
None
Possible Causes
Cause 1: The automatic match function is disabled.
Procedure
Step 1 Cause 1: The automatic match function is disabled.
1. Contact the Huawei technical support engineers for troubleshooting.
----End
Related Information
None
A.3.295 SWDL_CHGMNG_NOMATCH
Description
The SWDL_CHGMNG_NOMATCH is an alarm of software inconsistency.if the system
detects that the ofs1 and ofs2 are inconsistent in software packages, the system reports the
SWDL_CHGMNG_NOMATCH alarm.
Attribute
Parameters
None
Possible Causes
Cause 1: After a system control board is replaced, the ofs1 and ofs2 are inconsistent in
software packages.
Procedure
Step 1 Cause 1: After a system control board is replaced, the ofs1 and ofs2 are inconsistent in
software packages.
1. Re-load the software packages on the NE where the SWDL_CHGMNG_NOMATCH
alarm is reported.
----End
Related Information
None
A.3.296 SWDL_COMMIT_FAIL
Description
The SWDL_COMMIT_FAIL is an alarm indicating that the commission operation on the NE
fails. This alarm is reported when the commission operation fails in the package diffusion.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None
Possible Causes
Cause 1: File backup fails.
Procedure
Step 1 Cause 1: File backup fails.
1. Check whether the loaded package is correct.
2. Perform the package diffusion again on the NE where the alarm is reported.
----End
Related Information
None
A.3.297 SWDL_INPROCESS
Description
The SWDL_INPROCESS is an alarm indicating that the NE is loading the software package.
Attribute
Parameters
None
Possible Causes
The NE is loading the software package.
Procedure
Step 1 The SWDL_INPROCESS alarm is cleared automatically after the loading or rollback is
complete. Hence, this alarm can be neglected.
----End
Related Information
None
A.3.298 SWDL_NEPKGCHECK
Description
The SWDL_NEPKGCHECK is an alarm indicating that a file in the loaded software package
is lost or cannot be recovered after a file check failure. This alarm is reported when the NE
software initiates a package file check, detects the loss of a file, and fails to recover the file
from any complete package in other areas.
Attribute
Parameters
None
Possible Causes
Cause 1: Certain files of the package are missing and cannot be recovered.
Procedure
Step 1 Cause 1: Certain files of the package are missing and cannot be recovered.
1. Ensure that the loaded software package is correct. Perform the package loading again on
the NE where the SWDL_NEPKGCHECK alarm is reported.
----End
Related Information
None
A.3.299 SWDL_PKG_NOBDSOFT
Description
The SWDL_PKG_NOBDSOFT is an alarm indicating that certain board software is missing
from the software package. This alarm is reported when the required software is missing from
the software package during the automatic match of the board.
Attribute
Parameters
None
Possible Causes
Cause 1: Certain board software is uninstalled during the software package loading.
Procedure
Step 1 Cause 1: Certain board software is uninstalled during the software package loading.
1. Add the required board software to the software package. Alternatively, perform the
software package loading again.
----End
Related Information
None
A.3.300 SWDL_PKGVER_MM
Description
The SWDL_PKGVER_MM is an alarm indicating that the consistency check on the software
package version fails. This alarm is reported when the consistency check on the software
package version fails.
Attribute
Parameters
None
Possible Causes
Cause 1: The software version information in the description file of the software package is
inconsistent with the actual software version information.
Procedure
Step 1 Cause 1: The software version information in the description file of the software package is
inconsistent with the actual software version information.
1. Ensure that the loaded software package is correct. Perform the package diffusion again
on the NE where the alarm is reported.
----End
Related Information
None
A.3.301 SWDL_ROLLBACK_FAIL
Description
The SWDL_ROLLBACK_FAIL is an alarm indicating that the rollback on the NE fails. This
alarm is reported when the rollback fails for any board on the NE.
Attribute
Alarm Severity Alarm Type
Minor Processing alarm
Parameters
None
Possible Causes
Cause 1: Certain board software is uninstalled during the software package loading.
Procedure
Step 1 Cause 1: Certain board software is uninstalled during the software package loading.
1. Add the required board software to the software package. Alternatively, perform the
software package loading again.
----End
Related Information
None
A.3.302 SYN_BAD
Description
The SYN_BAD is an alarm indicating that the quality of the synchronization source declines.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The quality of the synchronization source declines.
l Cause 2: A certain board is faulty.
Procedure
Step 1 Cause 1: The quality of the synchronization source declines.
1. Take different measures based on the traced synchronization source.
If... Then...
The traced synchronization source is an Perform Steps Step 1.2 to Step 1.4.
external clock
The traced synchronization source is a line Replace the upstream NE.
clock
2. Check whether the configuration of the external clock is correct.
If... Then...
The configuration is incorrect Change the configuration data.
The configuration is correct Go to the next step.
3. Check whether the opposite equipment that provides the clock source is faulty.
If... Then...
The equipment is faulty Rectify the fault.
The equipment functions normally Go to the next step.
4. Check whether the cable that is connected to the external clock source is in normal
status.
If... Then...
The cable is not in normal status Replace the cable.
The cable is in normal status Go to Cause 2.
----End
Related Information
None
A.3.303 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
None
Possible Causes
Cause 1: The clock source is lost.
Procedure
Step 1 Cause 1: The clock source is lost.
1. See Querying the Clock Synchronization Status, troubleshoot the synchronization
sources of the lost clock source based on the clock source priority table.
If... Then...
The synchronization source is an Handle the EXT_SYNC_LOS alarm.
external clock
The synchronization source is an IF Handle the alarm that occurs on the IF unit.
clock
If... Then...
The synchronization source is a Handle the alarm that occurs on the tributary
tributary clock unit.
----End
Related Information
None
A.3.304 SYSLOG_COMM_FAIL
Description
The SYSLOG_COMM_FAIL is an alarm indicating that the communication between the NE
and the syslog server fails.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
Cause 1: In the TCP mode, the connection between the NE and syslog server is interrupted, or
the session between the NE and server is abnormal.
Procedure
Step 1 Rectify the fault of the link between the NE and syslog server, or rectify the fault of the
protocol.
----End
Related Information
None
A.3.305 T_ALOS
Description
The T_ALOS is an alarm indicating that the E1 analog signal is lost at the specific port.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: No E1 services are received on the port.
l Cause 2: The opposite NE is faulty.
l Cause 3: The E1 cable is faulty.
l Cause 4: The NE is faulty.
Procedure
Step 1 Cause 1: No E1 services are received on the port.
1. Check whether the alarmed port receives the 2 Mbit/s service.
If... Then...
The services are not received Transmit the services to the port or delete the
unnecessary service configuration.
The services are received Go to Cause 2.
If... Then...
The equipment is faulty Rectify the fault.
The equipment is normal Go to Cause 3.
If... Then...
The E1 cable is faulty Rectify the fault.
The E1 cable is not faulty Go to Cause 4.
----End
Related Information
None
A.3.306 T_LOC
Description
The T_LOC is an alarm indicating that the clock is lost on the transmit line side.
Attribute
Parameters
None
Possible Causes
l Cause 1: The cross-connect and timing board is faulty.
l Cause 2: The line board is faulty.
Procedure
Step 1 Cause 1: The cross-connect and timing board is faulty.
1. Replace the IDU.
----End
Related Information
None
A.3.307 TEM_HA
Description
The TEM_HA is an alarm indicating that the laser temperature is too high.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The ambient temperature of the board is too high.
l Cause 2: The optical module is faulty.
Procedure
Step 1 Check whether the temperature of the equipment room is too high. If yes, decrease the
temperature to an appropriate temperature. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details,
see 6.3 Replacing the SFP.
----End
Related Information
None
A.3.308 TEM_LA
Description
The TEM_LA is an alarm indicating that the laser temperature is too low.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: The ambient temperature of the board is too low.
l Cause 2: The optical module is faulty.
Procedure
Step 1 Check whether the temperature of the equipment room is too low. If yes, increase the
temperature to an appropriate temperature. Then, check whether the alarm is cleared.
Step 2 If the alarm persists, the optical module may be faulty. Replace the faulty board. For details,
see 6.3 Replacing the SFP.
----End
Related Information
None
A.3.309 TEMP_ALARM
Description
The TEMP_ALARM is an alarm indicating that the unit temperature crosses the threshold.
Attribute
Alarm Severity Alarm Type
Minor Environmental 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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 l 0x01: The temperature crosses the upper threshold.
l 0x02: The temperature crosses the lower threshold.
Possible Causes
l Cause 1: The alarmed unit temperature crosses the threshold.
l Cause 2: The temperature detection circuit of the alarmed unit is faulty.
Procedure
Step 1 Cause 1: The alarmed unit temperature crosses the threshold.
1. If the alarm is reported by the ODU, take appropriate measures (for example, installing a
sunshade) to control the temperature.
2. If the alarm is reported by the IDU, check whether the temperature control devices, such
as air-conditioners, work normally.
If... Then...
The temperature control devices work Adjust the temperature control devices.
abnormally
The temperature control devices work Go to the next step.
normally
3. Check whether the heat dissipation hole on the IDU is covered or blocked.
If... Then...
The heat dissipation hole is covered or Clear or remove the covering
blocked materials or obstacles.
The heat dissipation hole is not covered or Go to Cause 2.
blocked
Step 2 Cause 2: The temperature detection circuit of the alarmed unit is faulty.
1. If the ambient temperature is normal and no other heat dissipation problems exist,
replace the IDU.
----End
Related Information
None
A.3.310 TF
Description
The TF is an alarm indicating that the laser transmission fails. This alarm is reported when a
board detects that the output optical power of the laser exceeds the preset failure alarm
threshold.
Attribute
Parameters
None
Possible Causes
l Cause 1: The laser module is damaged.
l Cause 2: The laser is aged out.
Procedure
Step 1 6.3 Replacing the SFP.
----End
Related Information
None
A.3.311 THUNDERALM
Description
The THUNDERALM is an alarm indicating the surge protection failure. If the system detects
the surge protection circuit fails, the THUNDERALM occurs.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the PIU that reports the alarm.
l 0x01: PIU1
Possible Causes
The possible causes of the THUNDERALM alarm are as follows:
l Cause 1: The fuse tube of the surge protection circuit is interrupted.
l Cause 2: The NE is faulty.
Procedure
Step 1 Replace the IDU
----End
Related Information
None
A.3.312 TIME_LOCK_FAIL
Description
The TIME_LOCK_FAIL is an alarm indicating a time locking failure.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
The timestamp change on the NE is too large.
Procedure
Step 1 Check whether there are CLK_LOCK_FAIL or TIME_NO_TRACE_MODE alarms on the
NE. If yes, clear them before you proceed.
----End
Related Information
None
A.3.313 TIME_LOS
Description
The TIME_LOS is an alarm indicating that the time source is unavailable. This alarm is
reported only when the IEEE 1588v2 time function is enabled and no time source exists.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1, Indicates the ID of the time source. The ID of the time source
Parameter 2 occupies two bytes.
The first byte indicates the slot ID and the second byte indicates the
optical port ID.
Possible Causes
The link between the traced upstream time source and the NE is faulty.
Procedure
Step 1 Check whether the NE reports Ethernet link alarms, such as ETH_LOS, MAC_EXT_EXC,
or MAC_FCS_EXC, or radio link alarms, such as MW_LOF, MW_BER_EXC, or
MW_BER_SD.
Step 2 If yes, clear them immediately.
Step 3 If not, check these alarms on the upstream NE where the time source resides and clear them.
----End
Related Information
None
A.3.314 TIME_NO_TRACE_MODE
Description
The TIME_NO_TRACE_MODE is an alarm indicating that the high precision time of the
boards is in the non-traced status. This alarm is reported when the high precision time
function of an NE is enabled and the current tracing source is the internal time source.
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The clock source priority table is not configured when an external clock
interface is used to trace the upstream NE clock.
l Cause 2: The link between the traced upstream time source and the NE is faulty.
l Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream
NE. As a result, the time source cannot be traced.
Procedure
Step 1 Cause 1: The clock source priority table is not configured when an external clock interface is
used to trace the upstream NE clock.
1. Set the clock source priority. For details, see Configuring the Clock Sources.
Step 2 Cause 2: The link between the traced upstream time source and the NE is faulty.
1. Check whether the NE reports the TIME_LOS. If yes, clear the alarm immediately.
Step 3 Cause 3: The announce attribute of the local NE is inconsistent with that of the upstream NE.
As a result, the time source cannot be traced.
1. Check clock tracing relationships on the entire network based on the network plan.
----End
Related Information
None
A.3.315 TU_AIS
Description
The AU_AIS is an alarm indicating that the TU has errors. This alarm is reported if the NE
detects that the signal in the TU path is all 1s.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: Configuration data is incorrect.
l Cause 2: The line is faulty.
l Cause 3: The NE at the opposite end is faulty.
l Cause 4: The NE at the local end is faulty.
Procedure
Step 1 Cause 1: Configuration data is incorrect.
1. See Creating the Cross-Connections of Point-to-Point Services to check whether the
service data is incorrect.
If... Then...
The service data is incorrect Change the configuration data.
The service data is correct Go to Cause 2.
If... Then...
The line alarm is reported Clear the line alarms that cause AIS insertion.
No line alarms are reported Go to the next step.
2. See 8.4 Software Loopback to locate whether the board at the local end or at the
opposite end is faulty.
If... Then...
The board at the opposite end is faulty Go to Cause 3.
The board at the local end is faulty Go to Cause 4.
If... Then...
The alarm is cleared after the board is The fault is rectified. End the alarm
replaced handling.
The alarm persists after the board is Go to the next step.
replaced
----End
Related Information
None
A.3.316 TU_AIS_VC12
Description
The TU_AIS_VC12 is an indication of TU alarms at VC-12 level. This alarm occurs when a
board detects TU pointers of all 1s.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
l Cause 1: Configuration data is incorrect.
l Cause 2: The line is faulty.
l Cause 3: The board at the opposite site is faulty.
l Cause 4: The board at the local site is faulty.
Procedure
Step 1 Cause 1: Configuration data is incorrect.
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Cause 2.
1. Check whether a line alarm that causes AIS insertion is reported on the service trail.
NOTE
For details about the line alarms that cause AIS insertion, see D.2.6 AIS Insertion.
If... Then...
The line alarm is reported Change the configuration data.
No line alarms are reported Go to Step 3.
Step 3 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.1
Setting Loopback for the SDH Port.
If... Then...
The board at the opposite site is faulty Go to Cause 3.
The board at the local site is faulty Go to Cause 4.
----End
Related Information
None
A.3.317 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 is an invalid pointer or NDF reversion in eight
consecutive frames.
Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
None
Possible Causes
l Cause 1: The system control, cross-connect, and timing board is faulty.
l Cause 2: The tributary board is faulty.
Procedure
Step 1 Cause 1: The system control, cross-connect, and timing board is faulty.
1. Replace the IDU.
----End
Related Information
None
A.3.318 TU_LOP_VC12
Description
The TU_LOP_VC12 is an alarm indicating that the VC-12 TU pointer is lost. This alarm is
reported when a board receives invalid pointers or new data flags (NDFs) in eight consecutive
VC-12 frames.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the ID of the optical interface. The value is always
0x01.
Parameter 2, Parameter 3 Indicate the ID of the VC-12 path.
Possible Causes
l Cause 1: Configuration data is incorrect.
l Cause 2: The board at the opposite site is faulty.
l Cause 3: The board at the local site is faulty.
Procedure
Step 1 Cause 1: Configuration data is incorrect.
1. Check whether the SDH service data is correct. For details, see Creating the Cross-
Connections of Point-to-Point Services.
If... Then...
The SDH service data is incorrect Change the configuration data.
The SDH service data is correct Go to Step 2.
Step 2 Check whether the fault occurs at the local site or at the opposite site. For details, see 8.4.1
Setting Loopback for the SDH Port.
If... Then...
The board at the opposite site is faulty Go to Cause 2.
The board at the local site is faulty Go to Cause 3.
----End
Related Information
None
A.3.319 TUNNEL_APS_DEGRADED
Description
The TUNNEL_APS_DEGRADED is an alarm indicating that a tunnel protection group
degrades.
Attribute
Parameters
None
Possible Causes
Cause: The protection tunnel in the tunnel protection group is faulty.
Procedure
Step 1 Check the status of the tunnel protection group, locate the failed tunnel in the protection
group.
Step 2 Querying MPLS tunnel information, locate the board and port used by the failed tunnel.
Step 3 If the port is a Ethernet port, refer to Setting the Basic Attributes of Ethernet Ports, check
whether the port is disabled.
Enable the port if it was disabled.
Step 4 Refer to 4.3.1 Browsing Current Alarms, check whether any relevant Ethernet services
alarms are generated in the port or board. If yes, take priority to clear them.
The relevant alarms are as follows:
l Hardware alarms: Such as HARD_BAD, POWER_ALM, BD_STATUS,
COMMUN_FAILand LASER_MOD_ERR.
l Link alarms: Such as ETH_LOS, ETH_AUTO_LINK_DOWN,
ETH_EFM_LOOPBACK, LOOP_ALM, PORTMODE_MISMATCH, and
LAG_DOWN.
l Radio link alarms: Such as MW_LOF, MW_LIM.
Step 5 Refer to 4.3.1 Browsing Current Alarms, check whether any alarms are generated in the
failed tunnel. If yes, take priority to clear them.
The relevant alarms are as follows:
l MPLS_TUNNEL_BDI
l MPLS_TUNNEL_Excess
l MPLS_TUNNEL_FDI
l MPLS_TUNNEL_LOCV
l MPLS_TUNNEL_MISMATCH
l MPLS_TUNNEL_MISMERGE
l MPLS_TUNNEL_OAMFAIL
l MPLS_TUNNEL_SD
l MPLS_TUNNEL_SF
l MPLS_TUNNEL_UNKNOWN
l MPLS_TUNNEL_AIS
l MPLS_TUNNEL_RDI
l MPLS_TUNNEL_UNEXPMEG
l MPLS_TUNNEL_UNEXPMEP
l MPLS_TUNNEL_UNEXPPER
----End
Related Information
None
A.3.320 TUNNEL_APS_OUTAGE
Description
The TUNNEL_APS_OUTAGE alarm indicates that a tunnel APS protection group is
unavailable. This alarm is reported when both the working and protection tunnels of the
protection group fail.
Attribute
Alarm Severity Alarm Type
Major Service alarm
Parameters
None
Possible Causes
Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
Procedure
Step 1 Cause 1: The working and protection tunnels of the tunnel APS protection group fail.
1. Determine the boards and port IDs associated with the faulty tunnels. For details, see
Querying MPLS APS Status.
2. Handle tunnel faults by referring to 5.9 Troubleshooting MPLS Tunnels.
----End
Related Information
None
A.3.321 UP_E1_AIS
Description
The UP_E1_AIS is an alarm indication of the 2 Mbit/s uplink signal. This alarm is reported
when the tributary board detects that the 2 Mbit/s uplink signal is all 1s.
Attribute
Alarm Severity Alarm Type
Minor Communication alarm
Parameters
None
Possible Causes
l Cause 1: The opposite equipment transmits the AIS signal.
l Cause 2: The receive unit of the tributary unit on the local equipment is faulty.
Procedure
Step 1 Cause 1: The opposite equipment transmits the AIS signal.
1. Check whether the opposite equipment transmits the AIS signal.
If... Then...
The opposite equipment transmits the AIS Rectify the fault on the opposite
signal equipment.
The opposite equipment does not transmit Go to Cause 2.
the AIS signal
Step 2 Cause 2: The receive unit of the tributary unit on the local equipment is faulty.
1. 6.1 Replace the IDU.
----End
Related Information
None
A.3.322 USB_FILE_UNSEC
Description
The USB_FILE_UNSEC alarm indicates that the USB flash drive used by the NE is insecure.
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 details
about each parameter, refer to the following table.
Name Meaning
Parameter 1 Indicates the alarm cause.
l 0x01: The file is not encrypted.
l 0x02: Decryption fails.
l 0x03: The integrity check fails.
If the integrity check or decryption fails, data backup or restoration on the USB flash drive
will fail.
Possible Causes
l Cause 1: The file is not encrypted.
l Cause 2: Decryption fails.
l Cause 3: The integrity check fails.
Procedure
Step 1 Determine the alarm cause based on alarm parameters.
Step 2 If the file is not encrypted, encrypt the file using an NMS tool.
Step 3 If the integrity check or decryption fails, re-copy the database backup file.
----End
Related Information
None
A.3.323 USB_PROCESS_FAIL
Description
The USB_PROCESS_FAIL is an alarm indicating that data recovery from or data backup to a
USB disk fails.
Attribute
Alarm Severity Alarm Type
Minor Equipment alarm
Parameters
Name Meaning
Parameter 1 l 0x01 indicates data recovery.
l 0x02 indicates data backup.
Parameter 2 Indicates the file type.
l 0x01: indicates the software package.
l 0x02: indicates the patch package.
l 0x03: indicates the system parameter area.
l 0x04: indicates the script.
l 0x05: indicates the database.
l 0x06: indicates the license file.
Possible Causes
l Cause 1: Recovering data from a USB disk fails.
l Cause 2: Backing up data to a USB disk fails.
Procedure
Step 1 Cause 1: Recovering data from a USB disk fails.
1. Verify that the USB flash drive can be identified by the NE.
2. Check whether the data in the USB flash drive is correct. If the data is incorrect, upload
the USB flash drive with correct data.
3. Verify that the operations for recovering data from the USB flash drive are correct.
1. Verify that the USB flash drive has enough capacity for data backup.
2. Check whether the USB flash drive is properly inserted. If the USB flash drive is not
properly inserted, re-insert the USB flash drive.
3. Replace the USB flash drive and re-back up data.
----End
Related Information
None
A.3.324 V5_VCAIS
Description
The V5_VCAIS is an alarm indicating that bits 5-7 in the V5 byte of a VC-12 path are set to
"1"s.
Attribute
Alarm Severity Alarm Type
Parameters
None
Possible Causes
l Cause 1: Hardware fault alarms occur on boards of an upstream NE.
l Cause 2: The alarmed board is faulty.
Procedure
Step 1 Check whether any hardware fault alarms occur on boards of an upstream NE. If yes, clear
them. Then, check whether the V5_VCAIS alarm is cleared.
Step 2 If the alarm persists, the alarmed board is faulty. Cold Reset the board and check whether
the alarm is cleared.
Step 3 If the alarm persists, 6.1 Replace the IDU.
----End
Related Information
None
A.3.325 VOLT_LOS
Description
The VOLT_LOS is an alarm indicating that the power voltage is unavailable.
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 details
about each parameter, refer to the following table.
Name Meaning
Possible Causes
l Cause 1: The output power is abnormal.
l Cause 2: The input power is abnormal.
Procedure
Step 1 Cause 1: The output power is abnormal.
1. Use the multimeter to check the IF fiber jumper, IF cable, or ODU section by section for
a short circuit.
NOTICE
If the alarm is reported due to a short circuit, replace the short-circuited cable or ODU,
and then replace the IDU. Otherwise, the new IDU may be damaged again.
If... Then...
If... Then...
----End
Related Information
None
A.3.326 WRG_BD_TYPE
Description
The WRG_BD_TYPE is an alarm indicating that the type of the board is incorrect.
Attribute
Alarm Severity Alarm Type
Major Equipment alarm
Parameters
None
Possible Causes
l Cause 1: Configuration data is incorrect.
Procedure
Step 1 Cause 1: Configuration data is incorrect.
1. See Configuring the Logical Board to check whether the board type complies with the
planning requirement.
If... Then...
The board type does not meet the planning Change the configuration data.
requirement
The board type meets the planning requirement Go to Cause 2.
----End
Related Information
None
A.3.327 XPIC_LOS
Description
The XPIC_LOS is an alarm indicating that the XPIC compensation signals are lost.
Attribute
Alarm Severity Alarm Type
Critical Equipment alarm
Parameters
None
Possible Causes
l Cause 1: The radio link is faulty.
l Cause 2: The IF unit or ODU is faulty.
Procedure
Step 1 Cause 1: The radio link is faulty.
1. Check whether the paired board that is connected to the XPIC IF board through the
XPIC cable reports the MW_LOF alarm. If yes, first clear the MW_LOF alarm.
The alarm is cleared after the board is End the alarm handling.
replaced
----End
Related Information
None
Performance events are important indicators when the equipment performance changes. This
chapter describes all the possible performance events on the and how to handle these
performance events.
NOTE
The NE software consider a physical board as one or more logical boards when managing the physical board.
The NMS also considers a physical board as one or more logical boards when managing the physical board.
Figure A-1 shows the logical boards corresponding to all physical boards
Figure B-1 Logical board layout of the OptiX RTN 905 IDU
IDU 905 1E
PIU ISV3 CSHP AUX EG6 VS2 MP1 CD1 MN1 FAN
Slot 5 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
IDU 905 2E
PIU ISV3 ISV3 CSHP AUX EG6 VS2 MP1 CD1 MN1 FAN
Slot 5 Slot 4 Slot 3 Slot 1 Slot 10 Slot 7 Slot 8 Slot 9 Slot 15 Slot 16 Slot 6
NOTE
The logical slot number of the ODU is 20 plus the slot number for the IF board that is connected to the
ODU
B.2.1 CD1
The CD1 board reports two types of performance events: SDH performance events and laser
performance events.
B.2.2 CSHP
The CSHP board reports five types of performance events: board temperature performance
events, IF 1+1 protection group error performance events, clock performance events, PW
performance events, and MPLS performance events.
B.2.3 EG2
The EG2 board reports optical power performance events.
B.2.4 EG6
The EG6 board reports optical power performance events.
B.2.5 ISV3
The ISV3 board reports four types of performance events: SDH performance events, PDH
performance events, and microwave performance events.
B.2.6 ISU3
The ISU3 board reports radio performance events.
B.2.7 MP1
The MP1 board reports PDH performance events.
B.2.8 ODU
The ODU reports radio performance events and board temperature performance events.
B.2.9 VS2
The VS2 board reports Multiplex Section performance events.
Attribute
Attribute Description
Unit times
Related Alarms
None
Attribute
Attribute Description
Unit times
Impact on System
l When the value of the performance event is larger, more AM scheme are made.
l When the factors that affect a communication link, such as sudden change of the
weather, do not exist, and when the AM scheme count is very large, the communication
link may be faulty. You must check the communication link to prevent it from failure.
Related Alarms
AM_DOWNSHIFT
Possible Causes
When the AM function is enabled, the transmission modulation scheme that the IF port on the
IF board uses varies according to the quality of the link. Accordingly, the system counts the
performance events of the modulation scheme shift. When the low-efficiency modulation
scheme is shifted to the high-efficiency modulation scheme, an upshift is recorded and one
AMUPCNT event is counted. Similarly, when the high-efficiency modulation scheme is
shifted to the low-efficiency modulation scheme, a downshift is recorded and one
AMDOWNCNT event is counted.
Description
l AUPJCHIGH indicates the count of positive AU pointer justifications.
l AUPJCLOW indicates the count of negative AU pointer justifications.
l AUPJCNEW indicates the count of new AU pointer justifications.
Attribute
Attribute Description
Unit Block
Impact on System
Less than six AUPJCHIGH and AUPJCLOW events do not affect the system. If the pointer is
justified for many times, or the AUPJCNEW event occurs, bit errors may occur in the service.
Related Alarms
When the AUPJCHIGH, AUPJCLOW, or AUPJCNEW performance event crosses the preset
threshold, the MSAD_CROSSTR alarm is reported.
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
Description
l BDTEMPMAX indicates the maximum temperature of a board.
l BDTEMPMIN indicates the minimum temperature of a board.
l BDTEMPCUR indicates the current temperature of a board.
Attribute
Attribute Description
Unit 0.1C
Impact on System
If the temperature of a board is very high or very low, the performance of the board declines,
and bit errors or other faults occur.
Related Alarms
If the temperature of a board crosses the specific threshold, the TEMP_ALARM alarm is
reported.
Description
l CPUUSAGEMAX indicates the maximum CPU usage.
l CPUUSAGEMIN indicates the minimum CPU usage.
l CPUUSAGECUR indicates the current CPU usage.
l CPUUSAGEAVG indicates the average CPU usage.
Attribute
Attribute Description
Unit Percentage
Relevant Alarms
None
Description
l CURPOSITIVEPDV indicates the current positive packet delay variation (PDV).
l CURNEGATIVEPDV indicates the current negative PDV.
Attribute
Attribute Description
Unit ns
Impact on System
The less the PDV, the better the clock performance.
Related Alarms
None.
Description
l The E1_LCV_SDH is a performance event indicating the E1 line side code violation
count.
l The E1_LLOSS_SDH is a performance event indicating the E1 line side loss-of-signal
seconds.
l The E1_LES_SDH is a performance event indicating the E1 line side code violation
errored second.
ES refers to a second in which one or more errored blocks are detected.
l The E1_LSES_SDH is a performance event indicating the E1 line side code violation
severely errored second.
An SES refers to a certain second in which 30% or more errored blocks are detected or at
least one serious disturbance period (SDP) exists. The SDP refers to a period of at least
four consecutive blocks or 1 ms (taking the longer one) in which the BER of all the
consecutive blocks is equal to or higher than 10-2 or the signal is lost.
Attribute
Attribute Description
Related Alarms
None
Possible Causes
l External causes:
The fiber performance is degraded, and the fiber has extremely high attenuation.
The fiber connector is dirty or incorrect.
The equipment is improperly grounded.
A strong interference source is present near the equipment.
The working temperature is extremely high or extremely low, and the opposite
equipment cannot tolerate such temperature.
l Equipment problems:
The service code types are incorrect.
The board becomes faulty, or the performance of the board is degraded.
Procedure
Step 1 First eliminate external causes, such as poor grounding, too high operating temperature, too
low or too high the receiving optical power of the line board.
Step 2 Check whether the correct E1 service code is selected. If not, modify the code of the services
received by a board by setting the code type of the board.
----End
Description
l E1_BBE indicates the E1 background block error.
Background block error (BBE) refers to the errored blocks excluding the errored blocks
in the unavailable and severely errored seconds. This performance event can be detected
only when the E1 frame format is CRC-4.
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,
and 10-6 for the data service).
Related Alarms
None
E1_ES 50 100
E1_SES 20 50
E1_UAS 20 50
Possible Causes
The system detects the E1 bit errors.
Procedure
Step 1 Check whether the frame format of the local E1 port is the same as that of the opposite port.
----End
Description
l FEC_BEF_COR_ER indicates the BER before the FEC is performed.
This event indicates the impact of the external environment on the transmission.
l FEC_UNCOR_BLOCK_CNT indicates the number of frames that cannot be corrected
through the FEC.
This event indicates the number of blocks that cannot be corrected through the FEC.
Attribute
Attribute Description
Impact on System
If the value of FEC_BEF_COR_ER is very high, residual bit errors exist in the service after
the FEC is performed.
If the value of FEC_UNCOR_BLOCK_CNT is not zero, it can be inferred that bit errors that
cannot be corrected exist on a radio link. Bit errors exist in the service accordingly.
Related Alarms
If a byte cannot be corrected, the MW_FEC_UNCOR alarm is reported.
Description
l HPBBE indicates the higher order path background block error.
BBE refers to the errored blocks excluding the errored blocks in the unavailable and
severely errored seconds.
l HPES indicates the higher order path errored second.
ES refers to a second in which one or more errored blocks are detected.
l HPSES indicates the higher order path severely errored second.
SES refers to a second in which 30% or more than 30% errored blocks exist or at least
one SDP exists. SDP is the period in which the BER of all the consecutive blocks in a
period of less than four consecutive blocks or 1 ms (the longer period is applied) is equal
to or higher than 10-2 or the signal is lost.
l HPCSES indicates the higher order path consecutive severely errored second.
CSES refers to a second in which the SES occurs continuously for less than 10 seconds.
l HPUAS indicates the higher order path unavailable second.
The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs
included. When SESs disappear for 10 consecutive seconds, the available time begins
from the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
When the HPBBE, HPES, HPSES, or HPUAS performance event crosses the preset
threshold, the HP_CROSSTR alarm is reported.
HPES 50 100
HPSES 20 50
HPUAS 20 50
Possible Causes
The system detects higher order path bit errors through the B3 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.
----End
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
The HP_REI alarm is reported at the local end.
Possible Causes
The system detects the higher order path far end bit errors through bits 1 to 4 in the G1 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
The MW_BER_SD or MW_BER_EXC alarm is reported when the BER crosses the specific
threshold.
Possible Causes
The system detects bit errors on the radio link through the bit error detection overheads in a
radio frame.
Description
l IF_SNR_MAX indicates the maximum signal to noise ratio.
l IF_SNR_MIN indicates the minimum signal to noise ratio.
l IF_SNR_AVG indicates the average signal to noise ratio.
Attribute
Attribute Description
Unit dB
Impact on System
A greater SNR value indicates a steady radio link; a smaller SNR value indicates a worse
radio link, errors and even interruptions occur on the radio link.
Related Alarms
None
Description
l IF_MSE_MAX indicates the maximum MSE.
l IF_MSE_MIN indicates the minimum MSE.
Attribute
Attribute Meaning
Unit dB
Related Alarms
None
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
When the LPBBE, LPES, LPSES, or LPUAS performance event crosses the preset threshold,
the LP_CROSSTR alarm is reported.
LPES 50 100
LPSES 20 50
LPUAS 20 50
Possible Causes
The system detects lower order path bit errors through the BIP2 in the V5 byte (E1 interface
board or Hybrid IF board).
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.
----End
l LPFESES indicates the lower order path far end severely errored second.
FESES indicates that the SES occurs at the opposite end.
l LPFECSES indicates the lower order path far end consecutive severely errored second.
FECSES indicates that the CSES occurs at the opposite end.
l LPFEUAS indicates the lower order path far end unavailable second.
FEUAS indicates that the UAS occurs at the opposite end.
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
The LP_REI alarm is reported at the local end.
Possible Causes
The system detects the lower order path far end bit errors through bit 3 in the V5 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End
Attribute
Attribute Description
Attribute Description
Unit ns
Impact on System
If the frequency offset exceeds the acceptable range, clock signals deteriorate.
Related Alarms
None.
Description
l MAXMEANPATHDELAY indicates the maximum path delay between the master and
slave clocks.
l MINMEANPATHDELAY indicates the minimum path delay between the master and
slave clocks.
l AVGMEANPATHDELAY indicates the average path delay between the master and slave
clocks.
Attribute
Attribute Description
Unit ns
Impact on System
The deviation between the maximum and minimum path delays indicates the delay and jitter.
If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None
Description
l MAXPHASEOFFSET indicates the maximum time deviation between the master and
slave clocks.
l MINPHASEOFFSET indicates the minimum time deviation between the master and
slave clocks.
l AVGPHASEOFFSET indicates the average time deviation between the master and slave
clocks.
Attribute
Attribute Description
Unit ns
Impact on System
This performance indicates the time deviation between the local and upstream NEs. If the
time deviation exceeds the acceptable range (greater than 100 ns), the time of the upstream
NE cannot be locked, and NE time synchronization fails.
Related Alarms
When the time deviation between the master and slave clocks is greater than 100 ns, the
TIME_LOCK_FAIL alarm is reported.
Description
l MAXPOSITIVEDELAY indicates the maximum positive delay between the master and
slave clocks.
l MINPOSITIVEDELAY indicates the minimum positive delay between the master and
slave clocks.
l AVGPOSITIVEDELAY indicates the average positive delay between the master and
slave clocks.
Attribute
Attribute Description
Unit ns
Impact on System
The deviation between the maximum and minimum positive delays indicates the delay and
jitter. If the deviation exceeds the acceptable range, clock performance will be affected.
Related Alarms
None
Description
l MPLS_PW_LS indicates the packet loss seconds of the PW service.
l MPLS_PW_SLS indicates the severe packet loss seconds of the PW service.
l MPLS_PW_CSLS indicates the consecutive severe packet loss seconds of the PW
service.
l MPLS_PW_UAS indicates the unavailable seconds of the PW service.
Attribute
Attribute Description
Unit s
Impact on System
The greater of the seconds of packets that are lost in one measurement period (for example, 15
minutes or 24 hours), the more packets are lost. Then, the QoS will be affected.
Procedure
Check the bandwidth utilization. If the bandwidth utilization equals to or exceeds the
specified bandwidth threshold, expand the network.
Attribute
Attribute Meaning
Unit Second
Procedure
Check the bandwidth utilization. If the set bandwidth has been reached or exceeded, capacity
expansion is required.
Attribute
Attribute Meaning
Unit Second
Procedure
Check the bandwidth utilization. If the set bandwidth has been reached or exceeded, capacity
expansion is required.
Description
l MPLS_TUNNEL_LS_N indicates packet loss seconds of MPLS services at the local
end.
l MPLS_TUNNEL_SLS_N indicates severe packet loss seconds of MPLS services at the
local end.
l MPLS_TUNNEL_CSLS_N indicates consecutive severe packet loss seconds of MPLS
services at the local end.
l MPLS_TUNNEL_UAS_N indicates unavailable seconds of MPLS services at the local
end.
Attribute
Attribute Meaning
Unit Second
Procedure
Check the bandwidth utilization. If the set bandwidth has been reached or exceeded, capacity
expansion is required.
Description
l MSBBE indicates the multiplex section background block error.
BBE refers to the errored blocks excluding the errored blocks in the unavailable and
severely errored seconds.
Attribute
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Possible Causes
The system detects bit errors in TDM service and cascading interfaces.
Procedure
Step 1 Check whether TDM service and cascading connection is normal. Check whether the
cascading cable end is damaged.
----End
Attribute
Attribute Description
Related Alarms
The MS_REI alarm is reported at the local end.
Possible Causes
The system detects multiplex section far end bit errors through the M1 byte.
Procedure
Step 1 Clear the corresponding performance event at the opposite end.
----End
Description
l OSPITMPMAX indicates the maximum temperature of a laser core.
l OSPITMPMIN indicates the minimum temperature of a laser core.
l OSPITMPCUR indicates the current temperature of a laser core.
Attribute
Attribute Description
Unit C
Impact on System
If the temperature of a laser core is very high or very low, the performance of the laser
degrades, and bit errors or other faults occur.
Relevant Alarms
None
Description
l PG_IF_BBE indicates the protection group background block error.
Background block error (BBE) refers to the errored blocks excluding the errored blocks
in the unavailable and severely errored seconds.
l PG_IF_ES indicates the protection group errored second.
Errored second (ES) refers to a second in which one or more errored blocks are detected.
l PG_IF_SES indicates the protection group severely errored second.
Severely errored second (SES) refers to a second in which 30% or more than 30%
errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the
period in which the BER of all the consecutive blocks in a period of less than four
consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2
or the signal is lost.
l PG_IF_CSES indicates the protection group consecutive severely errored second.
Consecutive severely errored second (CSES) refers to a second in which the SES occurs
continuously for less than 10 seconds.
l PG_IF_UAS indicates the protection group unavailable second.
The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs
included. When SESs disappear for 10 consecutive seconds, the available time begins
from the eleventh second, with the previous 10 seconds included.
Attribute
Attribute Description
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than -3 for the voice service,
and 10-6 for the data service).
Related Alarms
PG_LINK_FAIL, PG_PRT_DEGRADED
PG_IF_ES 50 100
PG_IF_SES 20 50
PG_IF_UAS 20 50
Possible Causes
The system detects the protection group bit errors.
Procedure
Step 1 See PG_LINK_FAIL, PG_PRT_DEGRADED.
----End
Description
l RPLMAX indicates the maximum receive optical power at an optical interface.
l RPLMIN indicates the minimum receive optical power at an optical interface.
l RPLCUR indicates the current receive optical power at an optical interface.
Attribute
Attribute Description
Unit 0.1dBm
Impact on System
In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,
and 5 dB lower than the overload power.
If the receive optical power is very low or very high, bit errors occur and even services are
interrupted.
Description
l RSBBE indicates the regenerator section background block error.
Background block error (BBE) refers to the errored blocks excluding the errored blocks
in the unavailable and severely errored seconds.
l RSES indicates the regenerator section errored second.
Errored second (ES) refers to a second in which one or more errored blocks are detected.
l RSSES indicates the regenerator section severely errored second.
Severely errored second (SES) refers to a second in which 30% or more than 30%
errored blocks exist or at least one severely disturbed period (SDP) exists. SDP is the
period in which the BER of all the consecutive blocks in a period of less than four
consecutive blocks or 1 ms (the longer period is applied) is equal to or higher than 10-2
or the signal is lost.
l RSCSES indicates the regenerator section consecutive severely errored second.
Consecutive severely errored second (CSES) refers to a second in which the SES occurs
continuously for less than 10 seconds.
l RSUAS indicates the regenerator section unavailable second.
The unavailable time begins at the onset of 10 consecutive SESs, with the 10 SESs
included. When SESs disappear for 10 consecutive seconds, the available time begins
from the eleventh second, with the previous 10 seconds included.
NOTE
When the IF board works in PDH mode, these performance events may also be reported. These events
are detected through the self-defined overhead byte B1 in the PDH radio frame.
Attribute
Attribute Description
Attribute Description
Impact on System
Excessive bit errors interrupt the service (the BER should be less than 10-3 for the voice
service, and 10-6 for the data service).
Related Alarms
When the RSBBE, RSES, RSSES, or RSUAS performance event crosses the preset threshold,
the RS_CROSSTR alarm is reported.
RSES 50 100
RSSES 20 50
RSUAS 20 50
Possible Causes
The system detects the regenerator section bit errors through the B1 byte.
Procedure
Step 1 See 5.4 Troubleshooting Bit Errors in TDM Services for handling.
Step 2 When an RSUAS performance event is reported, check whether cross-connections are
configured and whether fibers are properly connected at service ports. If cross-connections are
not configured, configure cross-connections again according to planning information; if fibers
are incorrectly connected, connect the fibers again according to planning information.
----End
Description
l RSL_MAX indicates the maximum radio received signal level.
l RSL_MIN indicates the minimum radio received signal level.
l RSL_CUR indicates the current radio received signal level.
Attribute
Attribute Description
Unit 0.1dBm
Impact on System
When the radio received signal level is very low or very high, bit errors occur and even
services are interrupted.
Related Alarms
If the radio received signal level crosses the specific threshold, the RADIO_RSL_HIGH or
RADIO_RSL_LOW alarm is reported.
Attribute
Attribute Description
Impact on System
The system discards OOF data blocks. Therefore, an RSOOF event is equivalent to a big error
(if one RSOOF exists in a second, the BER is not less than 1.25 x 10-5).
Related Alarms
If RSOOF is received in five consecutive frames, the equipment changes to the OOF state. If
the OOF state lasts for 3 ms, the R_LOF alarm is reported and all the services are interrupted.
Possible Causes
The system detects incorrect A1 and A2 bytes.
Procedure
Step 1 If the R_LOF alarm, as well as the performance event, is reported, eliminate the errors
according to the alarm. Otherwise, see 5.4 Troubleshooting Bit Errors in TDM Services for
handling.
----End
Attribute
Attribute Description
Unit Second
Impact on System
When the AM function is disabled, the performance event does not affect the system.
When the AM function is enabled, in normal cases, the seconds of the modulation scheme for
maximum capacity should account for a larger percentage. In the duration set for good
weather, if the seconds of the low-efficiency modulation scheme account for a larger
percentage, the performance of the radio link is abnormal.
Related Alarms
None
Attribute
Attribute Description
Unit 0.1 mA
Impact on System
If the bias current of the laser is over-high or over-low, the laser is damaged.
Related Alarms
If the receive optical power on the opposite NE is abnormal, the IN_PWR_ABN alarm is
reported.
Description
l The RLHTT indicates the duration when the ODU at the local end has a receive power
lower than the upper threshold.
l The RLLTT indicates the duration when the ODU at the local end has a receive power
lower than the lower threshold.
l The TLHTT indicates the duration when the ODU at the local end has a transit power
higher than the upper threshold.
l The TLLTT indicates the duration when the ODU at the local end has a transit power
higher than the lower threshold.
Attribute
Attribute Description
Unit Second
Impact on System
When the receive power of an ODU is lower than the receiver sensitivity, bit errors occur and
services may even be interrupted.
Related Alarms
None
Description
l TPLMAX indicates the maximum transmit optical power at an optical interface.
l TPLMIN indicates the minimum transmit optical power at an optical interface.
l TPLCUR indicates the current transmit optical power at an optical interface.
Attribute
Attribute Description
Unit 0.1dBm
Impact on System
In normal cases, the receive optical power should be 3 dB higher than the receiver sensitivity,
and 5 dB lower than the overload power.
If the transmit optical power is very low or very high, the receive optical power at the
opposite site is accordingly very low or very high. As a result, bit errors occur and even
services are interrupted.
Description
l TSL_MAX indicates the maximum radio transmitted signal level.
l TSL_MIN indicates the minimum radio transmitted signal level.
l TSL_CUR indicates the current radio transmitted signal level.
l TSL_AVG indicates the average radio transmitted signal level.
Attribute
Attribute Description
Unit 0.1dBm
Impact on System
When the radio transmitted signal level is very low or very high, the radio received signal
level at the opposite site is very low or very high. As a result, bit errors occur and even
services are interrupted.
Related Alarms
If the radio transmitted signal level is not within the range supported by the ODU, the
RADIO_TSL_HIGH or RADIO_TSL_LOW alarm is reported.
Description
l TUPJCHIGH indicates the count of positive TU pointer justifications.
l TUPJCLOW indicates the count of negative TU pointer justifications.
l TUPJCNEW indicates the count of new TU pointer justifications.
Attribute
Attribute Description
Unit Block
Impact on System
Less than six TUPJCHIGH and TUPJCLOW events on each port do not affect the system. If
the pointer is justified for many times, or the TUPJCNEW event occurs, bit errors may occur
in the service.
Related Alarms
When the TUPJCHIGH, TUPJCLOW, or TUPJCNEW performance event crosses the preset
threshold, the HPAD_CROSSTR alarm is reported.
Possible Causes
The NE clock is out-of-synchronization.
Procedure
Step 1 See 5.5 Troubleshooting Pointer Justifications for handling.
----End
B.3.39 XPIC_XPD_VALUE
Description
The XPIC_XPD_VALUE indicates the XPD value after the XPIC function is enabled.
Attribute
Attribute Description
Unit dB
Impact on System
l When the XPIC function is disabled, the performance event does not affect the system.
l When the XPIC function is enabled, a greater XPD value indicates less interference
between H and V polarization directions and better signaling environment; a smaller
XPD value indicates more interference and worse signaling environment. If the XPD
value is smaller than a specific value, errors and even interruptions occur on the radio
link.
Related Alarms
None
RMON events reflect the running of the Ethernet services. This chapter describes the possible
RMON events on the OptiX RTN 905E and how to handle these events.
ETHDR The number of packet ETHDROP indicates the EG6, ISV3, ISU3
OP loss events number of packet loss
events caused by
insufficient Ethernet
chip resources. The
count is not the number
of discarded packets but
the number of times
packet loss is detected.
C.2.1 EG6/EG2
The RMON performance that the EG6/EG2 board supports includes basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
TS the bytes ated packets (including bad packets), including framing bits but
received. value not FCS bytes.
NOTE
If the packets received by an EG6/EG2 board are larger than the
MTU, byte count is calculated based on actual packet size.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
ETHOVE Indicates Packets Accumul Oversized packets are the packets larger than MTU
R the ated (including FCS bytes but not framing bits).
oversized value NOTE
packets For EG6/EG2 board, an oversized packet is larger than the MTU.
received.
ETHJAB Indicates Packets Accumul ETHJAB indicates the number of received packets that are
the ated larger than MTU (including FCS bytes but not framing bits)
oversized value and contain FCS errors or alignment errors.
error NOTE
packets For EG6/EG2 board, an oversized error packet is larger than 1518
received. bytes.
ETHUN Indicates Packets Accumul Undersized packets are the packets shorter than 64 bytes
DER the ated (including FCS bytes but not framing bits).
undersize value
d packets
received.
ETHFRG Indicates Packets Accumul ETHFRG indicates the number of received packets that are
the ated shorter than 64 bytes (including FCS bytes but not framing
fragments value bits) and contain FCS errors or alignment errors. Increase of
received. the count is normal because noise collisions exist.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value NOTE
frames. For the EG6/EG2 boards, this count does not include undersized
frames and oversized frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
RXPAUS Indicates Frames Accumul RXPAUSE indicates the number of MAC flow control
E the pause ated frames with the PAUSE opcode.
frames value
received.
TXPAUS Indicates Frames Accumul TXPAUSE indicates the number of MAC flow control
E the pause ated frames with the PAUSE opcode.
frames value
transmitte
d.
RX_DRO Packet 0.0001 Value The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate obtained number of actually drop packets/ received packets.
in the in the last
ingress sampling
direction period
TX_DRO Packet 0.0001 Value The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate obtained number of actually drop packets/ transmitted packets.
in the in the last
egress sampling
direction period
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
ETH_RX Indicates kbit/s Minimum Minimum throughput = Number of received bytes (including
_THROU the value inter-frame gaps and preambles)/Monitoring period
GHPUT_ minimum obtained
MIN throughp among all
ut on a sampling
port in periods
the
receive
direction.
ETH_RX Indicates kbit/s Average Average throughput = Number of received bytes (including
_THROU the value of inter-frame gaps and preambles)/Monitoring period
GHPUT_ average counts in
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.
RXBPS Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
the bit obtained x 8/Monitoring period
rate in the in the last
receive sampling
direction period
of an
Ethernet
port.
TXBPS Indicates Bits/s Value Bit rate in the transmit direction = Number of transmitted
the bit obtained bytes x 8/Monitoring period
rate in the in the last
transmit sampling
direction period
of an
Ethernet
port.
RXPPS Indicates Packets/s Value Packet rate in the receive direction = Number of received
the obtained packets/Monitoring period
packet in the last
rate in the sampling
receive period
direction
of an
Ethernet
port.
TXPPS Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
the obtained packets/Monitoring period
packet in the last
rate in the sampling
transmit period
direction
of an
Ethernet
port.
RXBRD Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
CAST_R traffic obtained receive direction
ATIO ratio in in the last
the sampling
receive period
direction
TXBRDC Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
AST_RA traffic obtained transmit direction
TIO ratio in in the last
the sampling
transmit period
direction
PORTST Indicates 0.0001 Value Packet loss rate in the egress direction = Number of
RM_SHA the ratio obtained discarded packets in the egress direction/Number of packets
PING_D of packet in the last matching the traffic classification rule in the egress direction
ROPRAT loss due sampling
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
QOS_PO Indicates 0.0001 Value Proportion of packets marked in red in the ingress direction
RTCAR_ the obtained = Number of packets marked in red in the ingress direction/
MarkedR proportio in the last Number of packets matching the traffic classification rule in
edRATIO n of sampling the ingress direction
packets period
marked in
red when
the traffic
policing
function
is
enabled.
QOS_PO Indicates Packets/s Value Packet rate in the receive direction = Number of received
RTSTRM the obtained packets/Monitoring period
_RX_PPS packet in the last
rate in the sampling
receive period
direction
of a
matched
flow.
QOS_PO Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
RTSTRM the obtained packets/Monitoring period
_TX_PPS packet in the last
rate in the sampling
transmit period
direction
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
RTSTRM the bit obtained (including inter-frame gaps and preambles) x 8/Monitoring
_RX_BP rate in the in the last period
S receive sampling
direction period
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the transmit direction = Number of received bytes
RTSTRM the bit obtained (including inter-frame gaps and preambles) x 8/Monitoring
_TX_BP rate in the in the last period
S transmit sampling
direction period
of a
matched
flow.
QOS_PO Indicates 0.0001 Average Packet loss rate in an egress queue = Number of discarded
RTQUEU the ratio value of packets with a priority in the egress queue/Number of
E_DROP of packet counts in packets with the priority in the egress queue
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.
PORT_P Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
RI_TX_B the bit obtained period
PS rates of in the last
egress sampling
queues period
with
different
priorities
in the
transmit
direction.
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
TS the bytes ated packets (including bad packets), including framing bits but
received. value not FCS bytes.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
ETHOVE Indicates Packets Accumul Oversized packets are the packets larger than MTU
R the ated (including FCS bytes but not framing bits).
oversized value NOTE
packets An oversized packet is larger than the MTU.
received.
ETHJAB Indicates Packets Accumul ETHJAB indicates the number of received packets that are
the ated larger than MTU (including FCS bytes but not framing bits)
oversized value and contain FCS errors or alignment errors.
error NOTE
packets An oversized error packet is larger than the MTU.
received.
ETHUN Indicates Packets Accumul Undersized packets are the packets shorter than 64 bytes
DER the ated (including FCS bytes but not framing bits).
undersize value
d packets
received.
ETHFRG Indicates Packets Accumul ETHFRG indicates the number of received packets that are
the ated shorter than 64 bytes (including FCS bytes but not framing
fragments value bits) and contain FCS errors or alignment errors. Increase of
received. the count is normal because noise collisions exist.
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value NOTE
frames. This count does not include undersized frames and oversized
frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
RXPAUS Indicates Frames Accumul RXPAUSE indicates the number of MAC flow control
E the pause ated frames with the PAUSE opcode.
frames value
received.
TXPAUS Indicates Frames Accumul TXPAUSE indicates the number of MAC flow control
E the pause ated frames with the PAUSE opcode.
frames value
transmitte
d.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
NOTE
Ports whose Port Mode is Layer 3 do not support RMON performance events of traffic classifications or
port DS domains.
C.2.2 ISV3/ISU3
The RMON performance that the ISV3/ISU3 board supports includes basic performance,
extended performance, port traffic classification performance, port priority performance, and
Port DS domain performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
RXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
received.
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The count is
packet value not the number of discarded packets but the number of times
loss packet loss is detected.
events. NOTE
For the ISV3 board, ETHDROP counts packet loss events caused by
congestion.
For other boards, ETHDROP counts packet loss events caused by
insufficient Ethernet chip resources, but does not count packet loss
events caused by link congestion and other reasons.
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
TS the bytes ated packets (including bad packets), including framing bits but
received. value not FCS bytes.
NOTE
If the packets received by an ISV3/ISU3 board are larger than the
MTU, byte count is calculated based on MTU.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value NOTE
frames. For the ISV3/ISU3 board, this count does not include undersized
frames and oversized frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
RX_DRO Packet 0.0001 Value The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate obtained number of actually drop packets/received packets.
in the in the last
ingress sampling
direction period
TX_DRO Packet 0.0001 Value The discarded packets ratio in the ingress direction, that is,
P_RATIO loss rate obtained number of actually drop packets/transmitted packets.
in the in the last
egress sampling
direction period
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
ETH_RX Indicates kbit/s Minimum Minimum throughput = Number of received bytes (including
_THROU the value inter-frame gaps and preambles)/Monitoring period
GHPUT_ minimum obtained
MIN throughp among all
ut on a sampling
port in periods
the
receive
direction.
ETH_RX Indicates kbit/s Average Average throughput = Number of received bytes (including
_THROU the value of inter-frame gaps and preambles)/Monitoring period
GHPUT_ average counts in
AVG throughp all
ut on a sampling
port in periods
the
receive
direction.
RXBPS Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
the bit obtained x 8/Monitoring period
rate in the in the last
receive sampling
direction period
of an
Ethernet
port.
TXBPS Indicates Bits/s Value Bit rate in the transmit direction = Number of transmitted
the bit obtained bytes x 8/Monitoring period
rate in the in the last
transmit sampling
direction period
of an
Ethernet
port.
RXPPS Indicates Packets/s Value Packet rate in the receive direction = Number of received
the obtained packets/Monitoring period
packet in the last
rate in the sampling
receive period
direction
of an
Ethernet
port.
TXPPS Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
the obtained packets/Monitoring period
packet in the last
rate in the sampling
transmit period
direction
of an
Ethernet
port.
RXBRD Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
CAST_R traffic obtained receive direction
ATIO ratio in in the last
the sampling
receive period
direction
TXBRDC Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
AST_RA traffic obtained transmit direction
TIO ratio in in the last
the sampling
transmit period
direction
PORTST Indicates 0.0001 Value Packet loss rate in the egress direction = Number of
RM_SHA the ratio obtained discarded packets in the egress direction/Number of packets
PING_D of packet in the last matching the traffic classification rule in the egress direction
ROPRAT loss due sampling
IO to period
network
congestio
n when
the traffic
shaping
function
is enabled
in the
egress
direction.
QOS_PO Indicates 0.0001 Value Proportion of packets marked in red in the ingress direction
RTCAR_ the obtained = Number of packets marked in red in the ingress direction/
MarkedR proportio in the last Number of packets matching the traffic classification rule in
edRATIO n of sampling the ingress direction
packets period
marked in
red when
the traffic
policing
function
is
enabled.
QOS_PO Indicates Packets/s Value Packet rate in the receive direction = Number of received
RTSTRM the obtained packets/Monitoring period
_RX_PPS packet in the last
rate in the sampling
receive period
direction
of a
matched
flow.
QOS_PO Indicates Packets/s Value Packet rate in the transmit direction = Number of transmitted
RTSTRM the obtained packets/Monitoring period
_TX_PPS packet in the last
rate in the sampling
transmit period
direction
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the receive direction = Number of received bytes
RTSTRM the bit obtained (including inter-frame gaps and preambles) x 8/Monitoring
_RX_BP rate in the in the last period
S receive sampling
direction period
of a
matched
flow.
QOS_PO Indicates Bits/s Value Bit rate in the transmit direction = Number of received bytes
RTSTRM the bit obtained (including inter-frame gaps and preambles) x 8/Monitoring
_TX_BP rate in the in the last period
S transmit sampling
direction period
of a
matched
flow.
QOS_PO Indicates 0.0001 Average Packet loss rate in an egress queue = Number of discarded
RTQUEU the ratio value of packets with a priority in the egress queue/Number of
E_DROP of packet counts in packets with the priority in the egress queue
RATIO loss due all
to sampling
congestio periods
n in
egress
queues
with
different
priorities.
PORT_P Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
RI_TX_B the bit obtained period
PS rates of in the last
egress sampling
queues period
with
different
priorities
in the
transmit
direction.
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The count is
packet value not the number of discarded packets but the number of times
loss packet loss is detected.
events.
RXOCTE Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
TS the bytes ated packets (including bad packets), including framing bits but
received. value not FCS bytes.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value NOTE
frames. This count does not include undersized frames and oversized
frames.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
NOTE
C.2.3 MP1
The RMON performance that the MP1 board supports includes CES performance, PW
performance, PPP performance, and MLPPP performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
receive
direction.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
transmit
direction.
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
transmitte
d MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
received
MP
packets.
C.2.4 CSHP
The RMON performance that the CSHP board supports includes L2VPN performance, tunnel
performance, PW performance of L2VPN, ETH OAM 802.1ag performance, ETH OAM E-
LAN service performance, and MPLS-TP OAM performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
VUNI_R Indicates Packets Accumul Indicates the number of packets received on a V-UNI of a
CVPKTS the ated service.
number value
of
packets
received
on the V-
UNI.
VUNI_S Indicates Packets Accumul Indicates the number of packets transmitted on a V-UNI of a
NDPKTS the ated service.
number value
of
packets
transmitte
d on the
V-UNI.
VUNI_R Indicates Bytes Accumul Indicates the number of bytes received on a V-UNI of a
CVBYTE the ated service.
S number value
of bytes
received
on the V-
UNI.
VUNI_S Indicates Bytes Accumul Indicates the number of bytes in the packets transmitted on a
NDBYTE the ated V-UNI of a service.
S number value
of bytes
sent on
the V-
UNI.
VLAN_R Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
X_BPS the bit obtained
rate in the in the last
receive sampling
direction period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_T Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
X_BPS the bit obtained period
rate in the in the last
transmit sampling
direction period
of a
VLAN to
which a
V-UNI
belongs.
VLAN_R Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
X_PPS the obtained
packet in the last
rate in the sampling
receive period
direction
of a
VLAN to
which a
V-UNI
belongs.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in the reverse
_REVER the ated tunnel of a bidirectional transit tunnel.
SE_RCV number value
PKTS of
packets
received
in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in the reverse
_REVER the ated tunnel of a bidirectional transit tunnel.
SE_SND number value
PKTS of
packets
transmitte
d in the
reverse
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in the reverse tunnel
_REVER the ated of a bidirectional transit tunnel.
SE_RCV number value
BYTES of bytes
received
in the
reverse
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes transmitted in the reverse
_REVER the ated tunnel of a bidirectional transit tunnel.
SE_SND number value
BYTES of bytes
transmitte
d in the
reverse
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets received in a tunnel.
_RCVPK the ated
TS number value
of
packets
received
in the
tunnel.
TUNNEL Indicates Packets Accumul Indicates the number of packets transmitted in a tunnel.
_SNDPK the ated
TS number value
of
packets
transmitte
d in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes received in a tunnel.
_RCVBY the ated
TES number value
of bytes
received
in the
tunnel.
TUNNEL Indicates Bytes Accumul Indicates the number of bytes transmitted in a tunnel.
_SNDBY the ated
TES number value
of bytes
transmitte
d in the
tunnel.
TUNNEL Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
_REVER the bit obtained
SE_RX_ rate in the in the last
BPS receive sampling
direction period
of a
reverse
tunnel.
TUNNEL Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
_REVER the bit obtained
SE_TX_ rate in the in the last
BPS transmit sampling
direction period
of a
reverse
tunnel.
TUNNEL Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
_REVER the obtained
SE_RX_ packet in the last
PPS rate in the sampling
receive period
direction
of a
reverse
tunnel.
TUNNEL Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
_RX_BP the bit obtained
S rate in the in the last
receive sampling
direction period
of a
monitore
d object.
TUNNEL Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
_TX_BP the bit obtained period
S rate in the in the last
transmit sampling
direction period
of a
tunnel.
TUNNEL Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
_RX_PPS the obtained
packet in the last
rate in the sampling
receive period
direction
of a
monitore
d object.
PW_SND Indicates Packets Accumul Indicates the number of packets transmitted on a PW.
PKTS the ated
number value
of
packets
transmitte
d on the
PW.
PW_SND indicates Bytes Accumul Indicates the number of bytes transmitted on a PW.
BYTES the ated
number value
of bytes
transmitte
d on a
PW.
PW_RX_ Indicates Bits/s Value Bit rate = Number of received bytes x 8/Monitoring period
BPS the bit obtained
rate in the in the last
receive sampling
direction period
of a
monitore
d object.
PW_TX_ Indicates Bits/s Value Bit rate = Number of transmitted bytes x 8/Monitoring
BPS the bit obtained period
rate in the in the last
transmit sampling
direction period
of a PW.
PW_RX_ Indicates Packets/s Value Packet rate = Number of received packets/Monitoring period
PPS the obtained
packet in the last
rate in the sampling
receive period
direction
of a
monitore
d object.
Table C-21 ETH OAM E-Line service performance entry list (CSHP)
Brief Full Perform Perform Remarks
Name of Name of ance ance
a a Count Countin
Perform Perform Unit g
ance ance Method
Entry Entry
ETH_CF Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
M_FLR the obtained source MEP - Number of packets received by the sink
E_Line in the last MEP)/Number of packets transmitted by the source MEP
service sampling
packet period
loss rate.
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
M_FL the ated the source - Number of packets received by the sink (Both
number value numbers are detected by the performance monitoring scheme
of of OAM.)
discarded
E_Line
service
packets.
ETH_CF Indicates s Value Frame delay = Time when the source MEP sends a request
M_FD the obtained packet - Time when the source MEP receives the response
E_Line in the last packet
service sampling
delay. period
ETH_CF Indicates s Value Frame delay variation is the difference between two frame
M_FDV the obtained delay test results.
E_Line in the last
service sampling
delay period
variation.
ETH_CF Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
M_FLR_ the obtained source MEP - Number of packets received by the sink
PRIn packet in the last MEP)/Number of packets transmitted by the source MEP
NOTE loss rate sampling
0n7 of the E- period
Line
service
with a
priority
of n.
ETH_CF Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
M_FL_P the ated the source - Number of packets received by the sink (Both
RIn number value numbers are detected by the performance monitoring scheme
NOTE of lost of OAM.)
0n7 packets in
the E-
Line
service
with a
priority
of n.
ETH_CF Indicates s Value Bidirectional frame delay = Time when the source sends a
M_FD_P the delay obtained request packet - Time when the source receives the response
RIn of the E- in the last packet
NOTE Line sampling
0n7 service period
with a
priority
of n.
ETH_CF Indicates s Value Frame delay variation is the difference between two frame
M_FDV_ the delay obtained delay test results.
PRIn variation in the last
NOTE of the E- sampling
0n7 Line period
service
with a
priority
of n.
MPLS_P Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
W_FLR the obtained source - Number of packets received by the sink)/Number of
packet in the last packets transmitted by the source
loss rate sampling
on the period
PW.
MPLS_P Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
W_FLR_ the obtained source - Number of packets received by the sink)/Number of
N packet in the last packets transmitted by the source
loss rate sampling
on the period
PW at the
near end.
MPLS_P Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
W_FL the ated the source - Number of packets received by the sink (Both
packet value numbers are detected by the performance monitoring scheme
loss of OAM.)
number
on the
PW.
MPLS_P Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
W_FL_N the ated the source - Number of packets received by the sink (Both
number value numbers are detected by the performance monitoring scheme
of lost of OAM.)
packets
on the
PW at the
near end.
MPLS_P Indicates s Value Frame delay = Time when the source sends a request packet
W_FD the frame obtained - Time when the source receives the response packet
delay on in the last
the PW. sampling
period
MPLS_P Indicates s Value Frame delay variation is the difference between two frame
W_FDV the frame obtained delay test results.
delay in the last
variation sampling
on the period
PW.
MPLS_T Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
UNNEL_ the obtained source tunnel - Number of packets received by the sink
FLR packet in the last tunnel)/Number of packets transmitted by the source tunnel
loss rate sampling
on the period
tunnel.
MPLS_T Indicates 0.0001 Value Packet loss rate = (Number of packets transmitted by the
UNNEL_ the obtained source tunnel - Number of packets received by the sink
FLR_N packet in the last tunnel)/Number of packets transmitted by the source tunnel
loss rate sampling
on the period
tunnel at
the near
end.
MPLS_T Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
UNNEL_ the ated the source - Number of packets received by the sink (Both
FL packet value numbers are detected by the performance monitoring scheme
loss of OAM.)
number
in the
tunnel.
MPLS_T Indicates Packets Accumul Number of lost packets = Number of packets transmitted by
UNNEL_ the ated the source - Number of packets received by the sink (Both
FL_N number value numbers are detected by the performance monitoring scheme
of lost of OAM.)
packets
on the
tunnel at
the near
end.
MPLS_T Indicates s Value Frame delay = Time when the source tunnel sends a request
UNNEL_ the frame obtained packet - Time when the source tunnel receives the response
FD delay in in the last packet
the sampling
tunnel. period
MPLS_T Indicates s Value Frame delay variation is the difference between two frame
UNNEL_ the frame obtained delay test results.
FDV delay in the last
variation sampling
in the period
tunnel.
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The count is
packet value not the number of discarded packets but the number of times
loss packet loss is detected.
events.
Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
RXOCTE the bytes ated packets (including bad packets), including framing bits but
TS received. value not FCS bytes.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value
frames.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
ETHDRO Indicates Times Accumul ETHDROP indicates the number of packet loss events
P the ated caused by insufficient Ethernet chip resources. The count is
packet value not the number of discarded packets but the number of times
loss packet loss is detected.
events.
Indicates Bytes Accumul RXOCTETS indicates the total number of bytes in received
RXOCTE the bytes ated packets (including bad packets), including framing bits but
TS received. value not FCS bytes.
RXMUL Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
multicast value broadcast packets.
packets
received.
RXBRD Indicates Packets Accumul RXMULCAST indicates the total number of received good
CAST the ated packets with multicast destination addresses, excluding
broadcast value broadcast packets.
packets
received.
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
4 received ated
(64 bytes value
in length)
RXPKT6 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
5 received ated
(65-127 value
bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
28 received ated
(128-255 value
bytes in
length)
RXPKT2 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
56 received ated
(256-511 value
bytes in
length)
RXPKT5 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
12 received ated
(512-102 value
3 bytes in
length)
RXPKT1 Packets Packets Accumul FCS bytes are included, but framing bits are excluded.
024 received ated
(1024-15 value
18 bytes
in length)
TXPKTS Indicates Packets Accumul Bad packets, broadcast packets, and multicast packets are
the ated included.
packets value
transmitte
d.
TX_DRO Indicates 0.0001 Value Packet loss rate in the transmit direction = Number of
P_RATIO the obtained packets lost in the transmit direction/Total number of
packet in the last transmitted packets
loss rate sampling
in the period
transmit
direction.
TXBPS Indicates Bit/s Value Bit rate in the transmit direction = Number of transmitted
the bit obtained bytes x 8/Monitoring period
rate in the in the last
transmit sampling
direction. period
TXPPS Indicates Packets/ Value Packet rate in the transmit direction = Number of transmitted
the second obtained packets/Monitoring period
packet in the last
rate in the sampling
transmit period
direction.
TXOCTE Indicates Bytes Accumul Indicates the total number of bytes in transmitted packets
TS the bytes ated (including bad packets), including framing bits but not FCS
transmitte value bytes.
d
ETHFCS Indicates Frames Accumul Indicates the number of received frames that are an integral
the FCS ated number of octets in length but do not pass the FCS check.
errored value
frames.
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
received
good
packets.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the bytes ated
in value
transmitte
d good
packets.
RXBBA Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
D the bytes ated
in value
received
bad
packets.
TXUNIC Indicates Packets Accumul The unicast packets that are discarded or fail to be
AST the ated transmitted are included.
unicast value
packets
transmitte
d.
RXUNIC Indicates Packets Accumul RXUNICAST indicates the number of good unicast packets.
AST the ated
unicast value
packets
received.
TXMUL Indicates Packets Accumul The multicast packets that are discarded or fail to be
CAST the ated transmitted are included.
multicast value
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The broadcast packets that are discarded or fail to be
AST the ated transmitted are included.
broadcast value
packets
transmitte
d.
RXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
received.
TXGOO Indicates kbit/s Value Framing bits (20 bytes) and FCS bytes are included.
DFULLF the rate of obtained
RAMESP good full- in the last
EED frame sampling
bytes period
transmitte
d.
RXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
received.
TXFULL Indicates Bytes Accumul Framing bits (20 bytes) and FCS bytes are included.
BGOOD the good ated
full-frame value
bytes
transmitte
d.
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
4 the count ated
of value
transmitte
d 64-byte
packets
(errored
packets
included)
TXPKT6 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
5 the count ated
of value
transmitte
d packets
with a
length of
65 to 127
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
28 the count ated
of value
transmitte
d packets
with a
length of
128 to
255 bytes
(errored
packets
included)
TXPKT2 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
56 the count ated
of value
transmitte
d packets
with a
length of
256 to
511 bytes
(errored
packets
included)
TXPKT5 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
12 the count ated
of value
transmitte
d packets
with a
length of
512 to
1023
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
024 the count ated
of value
transmitte
d packets
with a
length of
1024 to
1518
bytes
(errored
packets
included)
TXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
transmitte
d packets
with a
length of
over 1518
bytes
(errored
packets
included)
RXPKT1 Indicates Packets Accumul FCS bytes are included, but framing bits are excluded.
519 the count ated
of value
received
packets
with a
length of
over 1518
bytes
(errored
packets
included)
RXBRD Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
CAST_R traffic obtained receive direction
ATIO ratio in in the last
the sampling
receive period
direction
TXBRDC Broadcast 0.0001 Value Ratio of broadcast and multicast packets to all packets in the
AST_RA traffic obtained transmit direction
TIO ratio in in the last
the sampling
transmit period
direction
Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
the ated
number value
of bytes
in
received
packets
(includin
g
RXOCTE corrupted
TS packets).
PORT_R Indicates 0.0001 Value Bandwidth utilization on a port in the receive direction =
X_BW_U the obtained (Number of received bytes x 8/Monitoring period)/
TILIZATI bandwidt in the last Configured or actual bandwidth
ON h sampling
utilization period
on a port
in the
receive
direction.
PORT_T Indicates 0.0001 Value Bandwidth utilization on a port in the transmit direction =
X_BW_U the obtained (Number of received bytes x 8/Monitoring period)/
TILIZATI bandwidt in the last Configured or actual bandwidth
ON h sampling
utilization period
on a port
in the
transmit
direction.
TXPKTS Indicates Packets Accumul Corrupted packets, broadcast packets, and multicast packets
the ated are included.
number value
of
transmitte
d packets.
TXOCTE Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
TS the ated
number value
of bytes
in
transmitte
d packets
(includin
g
corrupted
packets).
TXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the ated
number value
of bytes
in error-
free
packets
transmitte
d.
RXBGO Indicates Bytes Accumul FCS bytes are included, but framing bits are excluded.
OD the ated
number value
of bytes
in error-
free
packets
received.
TXUNIC Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
AST the ated included.
number value
of unicast
packets
transmitte
d.
TXMUL Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
CAST the ated included.
number value
of
multicast
packets
transmitte
d.
TXBRDC Indicates Packets Accumul The packets that are dropped and fail to be transmitted are
AST the ated included.
number value
of
broadcast
packets
transmitte
d.
RXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
DFULLF the rate of obtained
RAMESP receiving in the last
EED error-free sampling
full-frame period
bits.
TXGOO Indicates kbit/s Value FCS bytes and framing bits are included.
DFULLF the rate of obtained
RAMESP transmitti in the last
EED ng error- sampling
free full- period
frame
bits.
RXFULL Indicates Bytes Accumul FCS bytes and framing bits are included.
BGOOD the ated
number value
of error-
free full-
frame
bytes
received.
TXFULL Indicates Bytes Accumul FCS bytes and framing bits are included.
BGOOD the ated
number value
of error-
free full-
frame
bytes
transmitte
d.
RX_DRO Indicates 0.0001 Value Packet loss rate in the receive direction = Number of
P_RATIO the obtained discarded packets/Total number of received packets
packet in the last
loss rate sampling
in the period
receive
direction.
TX_DRO Indicates 0.0001 Value Packet loss rate in the transmit direction = Number of
P_RATIO the obtained discarded packets/Total number of transmitted packets
packet in the last
loss rate sampling
in the period
transmit
direction.
NOTE
a:
l VUNI represents virtual UNI, represents the sink or source of services on the UNI side.
l The E-LAN services transmitted by the OptiX RTN 905E do not support the VLAN-based and
VUNI-based RMON performance statistics.
C.2.5 CD1
The RMON performance that the CD1 board supports includes CES performance, PPP
performance, and MLPPP performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
receive
direction.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
transmit
direction.
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
transmitte
d MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
received
MP
packets.
C.2.6 VS2
The RMON performance that the VS2 board supports includes CES performance, PPP
performance, and MLPPP performance.
NOTE
The current performance statistics of an RMON performance item are the count of performance events
within the current sampling period (which is usually a few seconds). The historical performance
statistics of an RMON performance item are calculated using the corresponding method based on counts
in sampling periods within a specific statistical period. The following table lists calculation methods for
historical performance statistics.
Accumulated value Accumulates the counts in all sampling periods within a statistical
period and takes the accumulated value as the historical
performance count.
Maximum value obtained Takes the maximum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Minimum value obtained Takes the minimum value among counts in all sampling periods
among all sampling periods within a statistical period as the historical performance count.
Value obtained in the last Takes the count of the last sampling period within a statistical
sampling period period as the historical performance count.
Average value of counts in all Takes the average value of counts in all sampling periods within a
sampling periods statistical period as the historical performance count.
PPP_RX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of received bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
receive
direction.
PPP_TX_ Indicates 0.0001 Value PPP bandwidth usage = (Number of transmitted bytes x 8/
BW_UTI the PPP obtained Monitoring period)/Configured or actual bandwidth
LIZATIO bandwidt in the last
N h usage in sampling
the period
transmit
direction.
MP_TX_ Indicates Packets Accumul The transmitted MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
transmitte
d MP
packets.
MP_RX_ Indicates Packets Accumul The received MP packets include service and protocol
TOTALP the total ated packets.
KTS number value
of
received
MP
packets.
C.3.1 ETHDROP
Description
ETHDROP indicates the number of events in which packet loss occurs due to resource
deficiency of Ethernet chips. An RMON threshold-crossing event is reported when the
number of packet loss events is higher than the upper threshold or lower than the lower
threshold.
NOTE
For the ISV3 board, ETHDROP counts packet loss events caused by congestion.
For other boards, ETHDROP counts packet loss events caused by insufficient Ethernet chip resources,
but does not count packet loss events caused by link congestion and other reasons.
Impact on System
When packet loss occurs frequently, services are affected and the system is affected seriously.
Hence, you must rectify the fault immediately.
Possible Causes
This performance event indicates packet loss due to the full MAC buffer, FIFO overflow, or
backward pressure.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower Change the lower threshold to 0.
threshold
The number is higher than the Manually decrease the traffic transmitted from the
upper threshold opposite end. If the problem persists, go to the next
step.
----End
Reference
None
C.3.2 ETHEXCCOL
Description
ETHEXCCOL indicates the number of frames that fail to be transmitted due to continuous
port collisions. An RMON threshold-crossing event is reported when the number of frames
that fail to be transmitted is higher than the upper threshold or lower than the lower threshold.
Generally, the value indicates that 16 port collisions occur continuously when the same frame
is transmitted.
Impact on System
The opposite equipment fails to normally receive services.
Possible Causes
Generally, this event is caused when the local port is connected to a device that work in half-
duplex mode.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends work Set the working modes of the ports on
in inconsistent modes, or any port works in the equipment at both ends to full-duplex
half-duplex mode or auto-negotiation, so that these ports
work in consistent modes.
The ports on the equipment at both ends work Go to the next step.
in consistent modes and no ports work in half-
duplex mode
----End
Reference
None
C.3.3 ETHLATECOL
Description
ETHLATECOL indicates the number of collisions detected within a timeslot period after a
packet is transmitted. An RMON threshold-crossing event is reported when the number of
collisions is higher than the upper threshold or lower than the lower threshold.
Impact on System
The opposite equipment fails to normally receive services.
Possible Causes
Generally, this performance event is caused by a large network diameter.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
If... Then...
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends work Set the working modes of the ports on
in inconsistent modes, or any port works in the equipment at both ends to full-duplex
half-duplex mode or auto-negotiation, so that these ports
work in consistent modes.
The ports on the equipment at both ends work Go to the next step.
in consistent modes and no ports work in half-
duplex mode
Step 3 Check whether the network diameter of the LAN is very large according to the networking
planning information.
If... Then...
The network diameter is Divide the network and deploy equipment to different buses or
very large physically shared devices (such as hubs).
NOTE
In the case of the 10 Mbit/s port rate, the maximum Ethernet diameter is
2000 m. In the case of the 100 Mbit/s port rate, the maximum Ethernet
diameter is 200 m.
----End
Reference
None
C.3.4 RXBBAD
Description
RXBBAD indicates the total number of bytes in received bad packets, excluding the framing
bit but including the FCS byte. An RMON threshold-crossing event is reported when the total
number of bytes in received bad packets is higher than the upper threshold or lower than the
lower threshold.
Impact on System
A port discards bad packets. This may even interrupt system services.
Possible Causes
1. Errors occur when the opposite end transmits packets.
2. The transmission line is of the poor quality and bit errors exist.
3. The hardware at the local end is faulty.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 Correct the errors that occur when the opposite end transmits packets.
----End
Reference
None
C.3.5 TXDEFFRM
Description
TXDEFFRM indicates the number of frames the first transmission of which is delayed due to
the congestion on the transmission media, excluding the number of frames the first
transmission of which is delayed due to collisions. An RMON threshold-crossing event is
reported when the number of frames that fail to be transmitted is higher than the upper
threshold and lower than the lower threshold.
Impact on System
The rate of frame transmission decreases, and therefore packets are congested at a port and
the throughput of the port decreases.
Possible Causes
Generally, this event is caused when the external port at the local end is connected to a device
that work in half-duplex mode.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends work Set the working modes of the ports on
in inconsistent modes, or any port works in the equipment at both ends to full-duplex
half-duplex mode or auto-negotiation, so that these ports
work in consistent modes.
The ports on the equipment at both ends work Go to the next step.
in consistent modes and no ports work in half-
duplex mode
----End
Reference
None
C.3.6 ETHUNDER
Description
ETHUNDER indicates that an RMON threshold-crossing event is reported when the number
of packets that are shorter than 64 bytes and are received on the line side crosses the preset
threshold.
Impact on System
The data frames whose length is not within the specific range are discarded. As a result, the
system services are affected.
Possible Causes
1. The length of a data frame that is received at a port is shorter than 64 bytes.
2. The hardware at the local end is faulty.
Procedure
Step 1 Check whether the opposite equipment transmits the packet that is shorter than 64 bytes.
If... Then...
The opposite equipment transmits the packet that is Rectify the fault on the opposite
shorter than 64 bytes equipment.
If... Then...
The opposite end does not transmit the packet that is Go to the next step.
shorter than 64 bytes
----End
Reference
None
C.3.7 ETHOVER
Description
ETHOVER indicates that an RMON threshold-crossing event is reported when the number of
packets that are longer than MTU and are received at a port crosses the preset threshold.
Impact on System
If the length of the data frame received at a port is more than the preset maximum frame
length, the data frame is discarded and therefore the system services are affected.
Possible Causes
1. The preset maximum frame length is less than the length of the frame that is received at
a port.
2. The hardware at the local end is faulty.
Procedure
Step 1 Check whether the opposite equipment transmits the packet that is longer than the maximum
frame length set for the local equipment.
If... Then...
The opposite equipment transmits the packet that is Notify the opposite equipment
longer than the maximum frame length set for the that the length of transmitted
local equipment frames should be changed.
The opposite equipment does not transmit the packet Go to the next step.
that is longer than the maximum frame length set for
the local equipment
----End
Reference
None
C.3.8 ETHFRG
Description
ETHFRG indicates that an RMON threshold-crossing event is reported when the number of
received packets that are shorter than 64 bytes and have FCS or alignment errors exceeds the
preset upper threshold.
Impact on System
Data transmission is delayed or packet loss occurs.
Possible Causes
l The working modes of the ports on the equipment at both ends are not consistent.
l The hardware at the local end is faulty.
l The ports on the equipment at both ends work in half-duplex mode, and the data traffic is
very heavy.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... Then...
The working modes are Go to the next step.
consistent
The working modes are not Change the working mode of the local port so that the
consistent ports on the equipment at both ends work in consistent
modes.
Step 2 Check whether the working modes of the ports on the equipment at both ends are set to the
half-duplex mode.
If... Then...
The working modes are not set to the Go to the next step.
half-duplex mode
The working modes are set to the half- Change the working modes of the ports on the
duplex mode equipment at both ends to the full-duplex mode
or adaptive mode.
----End
C.3.9 ETHJAB
Description
ETHJAB indicates that an RMON threshold-crossing alarm is reported when the number of
received packets that are longer than MTU and have FCS or alignment errors is higher than
the upper threshold.
Possible Causes
l The working modes of the ports on the equipment at both ends are not consistent.
l The hardware at the local end is faulty.
Procedure
Step 1 Check whether the working modes of the ports on the equipment at both ends are consistent.
If... Then...
The working modes are Go to the next step.
consistent
The working modes are not Change the working mode of the local port so that the
consistent ports on the equipment at both ends work in consistent
modes.
----End
C.3.10 ETHCOL
Description
ETHCOL indicates the number of detected packet collisions. An RMON threshold-crossing
event is reported when the number of collisions is higher than the upper threshold or lower
than the lower threshold.
Impact on System
The opposite equipment fails to normally receive services.
Possible Causes
Generally, this event is caused when the local port is connected to a large number of devices
that work in half-duplex mode.
Procedure
Step 1 Handle this alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends work Set the working modes of the ports on
in inconsistent modes, or any port works in the equipment at both ends to full-duplex
half-duplex mode or auto-negotiation, so that these ports
work in consistent modes.
The ports on the equipment at both ends work Go to the next step.
in consistent modes and no ports work in half-
duplex mode
----End
Reference
None
C.3.11 ETHFCS
Description
ETHFCS indicates the number of received Ethernet data frames with FCS check errors at the
local end (excluding the oversized and undersized frames). An RMON threshold-crossing
event is reported when the number is higher than the upper threshold or lower than the lower
threshold.
Impact on System
Most ports discard the packets with FCS check errors. The system services are interrupted in
the worst case.
Possible Causes
1. The local port and opposite port work in inconsistent modes. For example, one port
works in full-duplex mode, and the opposite port works in half-duplex mode.
2. The transmission line is of the poor quality and bit errors exist.
3. The hardware at the local end is faulty.
Procedure
Step 1 Therefore, handle the alarm according to the specific performance event.
If... Then...
The number is lower than the lower threshold Change the lower threshold to 0.
The number is higher than the upper threshold Go to the next step.
Step 2 On the NMS, query the working modes of the ports on the equipment at both ends.
If... Then...
The ports on the equipment at both ends Change the working modes of the ports on
work in inconsistent modes the equipment at both ends so that they can
work in consistent modes
The ports on the equipment at both ends Go to the next step.
work in consistent modes
----End
Reference
None
C.3.12 CES_MISORDERPKTS
Description
The CES_MISORDERPKTS is a performance event indicating the count of lost disordered
CES PW packets.
Possible Causes
1. Signals degrade on the link.
2. The link is looped.
3. The link is congested.
Related Alarms
CES_MISORDERPKT_EXC
Procedure
Step 1 See 5.3 Troubleshooting the Radio Link.
Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
C.3.13 CES_STRAYPKTS
Description
The CES_STRAYPKTS is a performance event indicating the number of misconnected
packets in a period.
Possible Causes
1. Links are misconnected.
Related Alarms
CES_STRAYPKT_EXC
Procedure
Step 1 Check the link configuration and rectify the fault.
----End
Related Information
None
C.3.14 CES_MALPKTS
Description
The CES_MALPKTS is a performance event indicating the number of deformed CES packets
in a period.
Possible Causes
1. The RTP head enabling status is different between the two ends of the PW.
2. Bit errors occur on the link.
Related Alarms
CES_MALPKT_EXC
Procedure
Step 1 Set the RTP head enabling status to the same on the two ends of the PW. For details, see
Modifying CES Service Parameters.
----End
Related Information
None
C.3.15 CES_JTRUDR
Description
The CES_JTRUDR is a performance event indicating the number of jitter buffer underflows.
Possible Causes
1. Signals degrade on the link.
2. The PSN network clocks used for the transmission of CES services are not synchronized.
3. The link is looped.
4. The link is congested.
5. The size of buffer area is set to a low value.
Related Alarms
CES_JTRUDR_EXC
Procedure
Step 1 Troubleshoot the link. For details, see 5.3 Troubleshooting the Radio Link.
Step 2 Synchronize the PSN network clock by setting clock synchronization, reducing transmission
nodes, and optimizing transmission routes.
Step 3 Release the loop.
Step 4 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
eliminate any source that transmits a large amount of invalid data.
Step 5 Query the size of buffer area. For details, see Querying CES Service Information.
Step 6 Determine whether the size can be increased according to network planning. If yes, change
the size to a greater value. For details, see Managing CES Services.
----End
Related Information
None
C.3.16 CES_JTROVR
Description
The CES_JTROVR is a performance event indicating the number of jitter buffer overflows.
Possible Causes
1. The jitter buffer area is too small.
2. The clocks are not synchronous.
3. Link quality deteriorates, causing more jitters.
4. There are too many hops of radio link on the network side, causing a large number of
jitters.
Related Alarms
CES_JTROVR_EXC
Procedure
Step 1 Allocate a larger jitter buffer area.
Step 2 Check whether the LTI and other clock-related alarms are reported.
Step 3 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.
Step 4 Determine whether the hops can be reduced according to network planning. If yes, reduce the
hops of radio link on the network side.
----End
Related Information
None
C.3.17 CES_LOSPKTS
Description
The CES_LOSPKTS is a performance event indicating the number of CES packets lost in a
period.
Possible Causes
1. The link transmission quality is poor.
2. The link is configured as a loop.
3. Link congestion occurs.
Related Alarms
CES_LOSPKT_EXC
Procedure
Step 1 Handle the fault on the radio link. For details, see 5.3 Troubleshooting the Radio Link.
Step 3 Check the bandwidth utilization. If the bandwidth is exhausted, increase the bandwidth or
eliminate any source that transmits a large amount of invalid data.
----End
Related Information
None
D Alarm Management
The alarm management on the OptiX RTN 905E is classified into the NE alarm management
and board alarm management.
when alarm query is performed on the NMS. The maintenance personnel can change the
setting on the NMS.
The alarm reversion function is available in three modes, namely, non-reversion, automatic
reversion, and manual reversion.
l Non-revertive (Disable)
In this mode, the alarms are monitored by default and alarm reversion cannot be enabled
for a port.
l Auto restore
In this mode, alarm reversion can be enabled for a port where alarms are reported. After
alarm reversion is enabled at a port, alarms are not reported. When the current alarm is
cleared, the alarm reversion automatically changes to the disabled status. That is, it
changes to the non-reversion mode. Then, the alarm reporting status at the port is the
same as the actual status.
l Manual restore
In this mode, alarm reversion can be enabled for a port regardless of whether any alarms
are reported at the port. After alarm reversion is enabled, the alarm reporting status at the
port is opposite to the actual status. After alarm reversion is manually disabled, the alarm
reversion status changes to the non-reversion mode. Then, the alarm reporting status at
the port is the same as the actual status.
Pay attention to the following points when you set the alarm reversion function:
l For OptiX RTN 905E, only R_LOS, T_ALOS, MW_LOF, ETH_LOS, and LAN_LOC
alarms support alarm reversion.
l Alarm reversion is set based on ports. Configurations are required at both the NE level
and the port level.
l Alarm reversion does not change the actual status of alarms on the board, as well as the
indication status of the alarm indicators.
l Alarm reversion is realized on the NE software. The alarm data is the same on the NE
and the NMS, which indicates the status after the alarm reversion. If you directly query
the alarm data of a board, however, the actual alarm status is returned.
NOTE
The functions of the upper and lower thresholds are as follows: When the detected value is greater than
the upper threshold, a threshold-crossing alarm is reported; when the detected value is lower than the
lower threshold, the threshold-crossing alarm clears.
100M: Upper
0-65535 threshold: 1
(frames) Lower
threshold: 0
10M: Upper
0-20480 threshold: 1
(frames) Lower
threshold: 0
100M: Upper
0-204800 threshold: 1
(times) Lower
threshold: 0
10M: Upper
0-20480 threshold: 1
(times) Lower
threshold: 0
2.5G: Upper
0-15000 threshold: 9
(times) Lower
threshold: 0
400M: Upper
0-204800 threshold: 4
(times) Lower
threshold: 0
100M: Upper
0-65535 threshold: 10
(frames) Lower
threshold: 0
10M: Upper
0-20480 threshold: 10
(frames) Lower
threshold: 0
MPLS_TUN SD on a - 1-100 0
NEL_SD tunnel
MPLS_PW_ SD on a PW - 1-100 0
SD
MPLS_PW_ SF on a PW - 1-100 0
SF
GE: Upper
0-15000000 threshold:
0 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
0-15000000 threshold:
(kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)
10M: Upper
0-1500000 threshold:
(kbit/s) 9500 (kbit/s)
Lower
threshold:
7500 (kbit/s)
4G: Upper
0-15000000 threshold:
0 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)
2.5G: Upper
0-15000000 threshold:
0 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
0-15000000 threshold:
(kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
GE: Upper
0-15000000 threshold:
0 (kbit/s) 950000
(kbit/s)
Lower
threshold:
750000
(kbit/s)
100M: Upper
0-15000000 threshold:
(kbit/s) 95000
(kbit/s)
Lower
threshold:
75000
(kbit/s)
10M: Upper
0-1500000 threshold:
(kbit/s) 9500 (kbit/s)
Lower
threshold:
7500 (kbit/s)
4G: Upper
0-15000000 threshold:
0 (kbit/s) 3800000
(kbit/s)
Lower
threshold:
3000000
(kbit/s)
2.5G: Upper
0-15000000 threshold:
0 (kbit/s) 2375000
(kbit/s)
Lower
threshold:
1875000
(kbit/s)
400M: Upper
0-15000000 threshold:
(kbit/s) 380000
(kbit/s)
Lower
threshold:
300000
(kbit/s)
GE: Upper
0-12500000 threshold:
0 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)
100M: Upper
0-12500000 threshold:
(bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
0-1250000 threshold:
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
GE: Upper
0-12500000 threshold:
0 (bytes) 100000000
(bytes)
Lower
threshold:
75000000
(bytes)
100M: Upper
0-12500000 threshold:
(bytes) 10000000
(bytes)
Lower
threshold:
7500000
(bytes)
10M: Upper
0-1250000 threshold:
(bytes) 1000000
(bytes)
Lower
threshold:
750000
(bytes)
MW_BER_SD Disabled
B2_SD Disabled
B2_EXC Disabled
HP_LOM Enabled
HP_TIM Disabled
HP_SLM Disabled
HP_UNEQ Disabled
B3_EXC Enabled
B3_SD Disabled
B1_SD Disabled
LP_UNEQ Disabled
LP_SLM Disabled
BIP_EXC Disabled
NOTE
When the ISV3 and ISU3 board detect the MW_LOF, MW_LIM, or R_LOF alarm, it forcibly inserts
the AIS.
When the SP3S board detect the T_ALOS alarm, it forcibly inserts the AIS.
When the TS2 board detect the R_LOS alarm, it forcibly inserts the AIS.
The performance event management is classified into the NE performance event management
and board performance event management.
When the alarm suppression function is disabled on an NE, the root alarm and certain
correlated alarms are reported if a fault occurs on this NE. After the alarm suppression
function is enabled, the reporting of the correlated alarms is suppressed according to the
relationship between alarms when the root alarm is reported. The alarm suppression
relationship can be classified into the suppression relationship between intra-board alarms and
suppression relationship between inter-board alarms.
MW_BER_E MW_BER_SD
XC
MW_LIM MW_RDI
B3_EXC B3_SD
HP_UNEQ HP_TIM
MS_RDI MS_REI
HP_RDI HP_REI
B3_EXC B3_SD
LP_RDI LP_REI
BIP_EXC BIP_SD
E1_LOS UP_E1_AIS
UP_E1_AIS DDN_LFA
UP_E1_AIS DDN_LFA
R_LOS TU_AIS
PG_LINK_F PG_PRT_DEGRADED
AIL
LICENSE_L LCS_LIMITED
OST
LCS_EXPIR LCS_LIMITED
ED
LCS_FILE_N LCS_LIMITED
OT_EXIST
POWER_AB THUNDERALM
NORMAL
FAN_FAIL FAN_AGING
TF OUT_PWR_ABN, LSR_WILL_DIE
ETH_EFM_D ETH_EFM_REMFAULT
F
ETH_EFM_R ETH_EFM_EVENT
EMFAULT
ETH_AUTO_ LASER_SHUT
LINK_DOW
N
LPT_CFG_C LASER_SHUT
LOSEPORT
MPLS_TUNN MPLS_TUNNEL_SD
EL_SF
MPLS_PW_S MPLS_PW_SD
F
ETH_APS_P ETH_APS_LOST
ATH_MISMA
TCH
ETH_CFM_ ETH_CFM_LOC
MISMERGE
ETH_CFM_U
NEXPERI
ETH_CFM_A
IS
Table F-17 Suppression relationship between intra-board alarms (tunnel service - PW service)
Root Alarm Suppressed Alarm
MPLS_TUNN MPLS_PW_LOCV
EL_LOCV
MPLS_TUNN MPLS_PW_BDI
EL_BDI
MPLS_TUNN MPLS_PW_RDI
EL_RDI
MPLS_TUNN MPLS_PW_OAMFAIL
EL_OAMFAI
L
MPLS_TUNN MPLS_PW_LOCV
EL_LOCK
GSP_TNNL_ PW_DOWN
DOWN
Table F-18 Suppression relationship between inter-board alarms (Ethernet Interface board-
Switching board)
Root Alarm Suppressed Alarm
Table F-19 Suppression relationship between inter-board alarms (IF board-Switching board)
Root Alarm Suppressed Alarm
G Indicators
Blinks on (green) and off Data is being written into the flash
at 100 ms intervals memory, or software is being loaded
during the equipment power-on or
resetting process.
USB USB flash Blinks (red) The USB flash drive is online but
drive faulty, or the NE does not support the
USB flash drive.
STAT Blinks on (red) and off at The boot ROM self-check has failed
100 ms intervals during the equipment power-on or
resetting process.
Blinks on (green) and off Data is being written into the flash
at 100 ms intervals memory, or software is being loaded
during the equipment power-on or
resetting process.
USB USB flash Blinks (red) The USB flash drive is online but
drive faulty, or the NE does not support the
USB flash drive.
H Glossary
Numerics
3G See 3rd Generation.
3GPP 3rd Generation Partnership Project
3rd Generation (3G) The third generation of digital wireless technology, as defined by the International
Telecommunications Union (ITU). Third generation technology is expected to deliver
data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s
to 19.2 kbit/s offered by second generation technology.
802.1Q in 802.1Q A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The
(QinQ) implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN
tag to allow the frame with double VLAN tags to be transmitted over the service
provider's backbone network based on the public VLAN tag. This provides a layer 2
VPN tunnel for customers and enables transparent transmission of packets over
private VLANs.
A
A/D analog/digit
ABR See available bit rate.
ACAP See adjacent channel alternate polarization.
ACL See access control list.
ADC analog to digital converter
ADM add/drop multiplexer
AF See assured forwarding.
AIS alarm indication signal
ALS See automatic laser shutdown.
AM See adaptive modulation.
APS automatic protection switching
ARP See Address Resolution Protocol.
ASBR See autonomous system boundary router.
available bit rate A kind of service categories defined by the ATM forum. ABR only provides possible
(ABR) forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
B
B-ISDN See broadband integrated services digital network.
BDI See backward defect indication.
BE See best effort.
BER bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIOS See basic input/output system.
BIP See bit interleaved parity.
BPDU See bridge protocol data unit.
BSC See base station controller.
BTS base transceiver station
Bidirectional A fast and independent hello protocol that delivers millisecond-level link failure
Forwarding Detection detection and provides carrier-class availability. After sessions are established between
(BFD) neighboring systems, the systems can periodically send BFD packets to each other. If
one system fails to receive a BFD packet within the negotiated period, the system
regards that the bidirectional link fails and instructs the upper layer protocol to take
actions to recover the faulty link.
backbone network A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an
important architectural element for building enterprise networks. It provides a path for
the exchange of information between different LANs or subnetworks. A backbone can
tie together diverse networks in the same building, in different buildings in a campus
environment, or over wide areas. Generally, the backbone network's capacity is greater
than the networks connected to it.
backward defect A function that the sink node of a LSP, when detecting a defect, uses to inform the
indication (BDI) upstream end of the LSP of a downstream defect along the return path.
base station controller A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It
(BSC) interworks with the BTS through the Abis interface, the MSC through the A interface.
It provides the following functions: radio resource management, base station
management, power control, handover control, and traffic measurement. One BSC
controls and manages one or more BTSs in an actual network.
basic input/output Firmware stored on the computer motherboard that contains basic input/output control
system (BIOS) programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the
computer.
baud rate The number of times per second the signal can change on a transmission line.
Commonly, the transmission line uses only two signal states, making the baud rate
equal to the number of bits per second that can be transferred. The underlying
transmission technique may use some of the bandwidth, so it may not be the case that
user data transfers at the line's specified bit rate.
best effort (BE) A traditional IP packet transport service. In this service, the diagrams are forwarded
following the sequence of the time they reach. All diagrams share the bandwidth of
the network and routers. The amount of resource that a diagram can use depends of the
time it reaches. BE service does not ensure any improvement in delay time, jitter,
packet loss ratio, and high reliability.
bit interleaved parity A method of error monitoring. With even parity, the transmitting equipment generates
(BIP) an X-bit code over a specified portion of the signal in such a manner that the first bit
of the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-
bit sequences within the specified portion, and so forth. Even parity is generated by
setting the BIP-X bits so that an even number of 1s exist in each monitored partition
of the signal. A monitored partition comprises all bits in the same bit position within
the X-bit sequences in the covered portion of the signal. The covered portion includes
the BIP-X.
bridge A device that connects two or more networks and forwards packets among them.
Bridges operate at the physical network level. Bridges differ from repeaters because
bridges store and forward complete packets, while repeaters forward all electrical
signals. Bridges differ from routers because bridges use physical addresses, while
routers use IP addresses.
bridge protocol data Data messages exchanged across switches within an extended LAN that uses a
unit (BPDU) spanning tree protocol (STP) topology. BPDU packets contain information on ports,
addresses, priorities, and costs, and they ensure that the data reaches its intended
destination. BPDU messages are exchanged across bridges to detect loops in a
network topology. These loops are then removed by shutting down selected bridge
interfaces and placing redundant switch ports in a backup, or blocked, state.
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as
services digital voice. It currently uses the ATM technology to transmit data over SONNET-based
network (B-ISDN) circuits at 155 to 622 Mbit/s or higher speed.
broadcast A means of delivering information to all members in a network. The broadcast range
is determined by the broadcast address.
broadcast domain A group of network stations that receives broadcast packets originating from any
device within the group. The broadcast domain also refers to the set of ports between
which a device forwards a multicast, broadcast, or unknown destination frame.
C
CAR committed access rate
CBR See constant bit rate.
CBS See committed burst size.
CC See continuity check.
CCDP See co-channel dual polarization.
CDMA See Code Division Multiple Access.
channel A telecommunication path of a specific capacity and/or speed between two or more
locations in a network. The channel can be established through wire, radio
(microwave), fiber, or any combination of the three. The amount of information
transmitted per second in a channel is the information transmission speed, expressed
in bits per second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s
(109 bit/s), and Tb/s (1012 bit/s).
circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks. At
service (CES) the transmission end, the interface module packs timeslot data into ATM cells. These
ATM cells are sent to the reception end through the ATM network. At the reception
end, the interface module re-assigns the data in these ATM cells to E1/T1 timeslots.
The CES technology guarantees that the data in E1/T1 timeslots can be recovered to
the original sequence at the reception end.
clock tracing The method of keeping the time on each node synchronized with a clock source in the
network.
co-channel dual A channel configuration method, which uses a horizontal polarization wave and a
polarization (CCDP) vertical polarization wave to transmit two signals. The Co-Channel Dual Polarization
has twice the transmission capacity of the single polarization.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum burst
(CBS) IP packet size when information is transferred at the committed information rate. This
parameter must be greater than 0 but should be not less than the maximum length of
an IP packet to be forwarded.
constant bit rate A kind of service categories defined by the ATM forum. CBR transfers cells based on
(CBR) the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
continuity check (CC) An Ethernet connectivity fault management (CFM) method used to detect the
connectivity between MEPs by having each MEP periodically transmit a Continuity
Check Message (CCM).
cross-polarization A technology used in the case of the Co-Channel Dual Polarization (CCDP) to
interference eliminate the cross-connect interference between two polarization waves in the CCDP.
cancellation (XPIC)
customer edge (CE) A part of the BGP/MPLS IP VPN model that provides interfaces for directly
connecting to the Service Provider (SP) network. A CE can be a router, switch, or
host.
cyclic redundancy A procedure used to check for errors in data transmission. CRC error checking uses a
check (CRC) complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before performing the transmission and includes the
generated number in the packet it sends to the receiving device. The receiving device
then repeats the same calculation. If both devices obtain the same result, the
transmission is considered to be error free. This procedure is known as a redundancy
check because each transmission includes not only data but extra (redundant) error-
checking values.
D
DC direct current
DC-C See DC-return common (with ground).
DC-I See DC-return isolate (with ground).
DC-return common A power system, in which the BGND of the DC return conductor is short-circuited
(with ground) (DC-C) with the PGND on the output side of the power supply cabinet and also on the line
between the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited
ground) (DC-I) with the PGND on the output side of the power supply cabinet and is isolated from the
PGND on the line between the output of the power supply cabinet and the electric
equipment.
DCC See data communications channel.
DCN See data communication network.
DDF digital distribution frame
DDN See digital data network.
DE discard eligible
DM See delay measurement.
DS boundary node A DS node that connects one DS domain to a node either in another DS domain or in a
domain that is not DS-capable.
DS interior node A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node A DS-compliant node, which is subdivided into DS boundary node and ID interior
node.
DSCP See differentiated services code point.
DVMRP See Distance Vector Multicast Routing Protocol.
DiffServ See differentiated service.
Distance Vector An Internet gateway protocol based primarily on the RIP. The DVMRP protocol
Multicast Routing implements a typical dense mode IP multicast solution and uses IGMP to exchange
Protocol (DVMRP) routing datagrams with its neighbors.
data communication A communication network used in a TMN or between TMNs to support the data
network (DCN) communication function.
data communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
channel (DCC) transmit information on the operation, management, maintenance, and provisioning
(OAM&P) between NEs. The DCC channel composed of bytes D1-D3 is referred to
as the 192 kbit/s DCC-R channel. The other DCC channel composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a source
(DM) node until the reception of the last bit of the loopbacked frame by the same source
node, when the loopback is performed at the frame's destination node.
differentiated service An IETF standard that defines a mechanism for controlling and forwarding traffic in a
(DiffServ) differentiated manner based on CoS settings to handle network congestion.
differentiated services According to the QoS classification standard of the Differentiated Service (Diff-Serv),
code point (DSCP) the type of services (ToS) field in the IP header consists of six most significant bits
and two currently unused bits, which are used to form codes for priority marking.
Differentiated services code point (DSCP) is the six most important bits in the ToS. It
is the combination of IP precedence and types of service. The DSCP value is used to
ensure that routers supporting only IP precedence can be used because the DSCP
value is compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB).
Therefore, terminal devices can identify traffic using the DSCP value.
digital data network A data transmission network that is designed to transmit data on digital channels (such
(DDN) as the fiber channel, digital microwave channel, or satellite channel).
digital modulation A method that controls the changes in amplitude, phase, and frequency of the carrier
based on the changes in the baseband digital signal. In this manner, the information
can be transmitted by the carrier.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-Aggr See Ethernet aggregation.
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
ECC See embedded control channel.
EMC See electromagnetic compatibility.
EMI See electromagnetic interference.
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logic device.
ERPS Ethernet ring protection switching
ESD electrostatic discharge
ETS European Telecommunication Standards
ETSI See European Telecommunications Standards Institute.
EVPL See Ethernet virtual private line.
EVPLAN See Ethernet virtual private LAN service.
Ethernet A LAN technology that uses the carrier sense multiple access with collision detection
(CSMA/CD) media access control method. The Ethernet network is highly reliable
and easy to maintain. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s,
1000 Mbit/s, or 10,000 Mbit/s.
Ethernet aggregation A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual
(E-Aggr) connection).
Ethernet line (E-Line) A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual
connection).
Ethernet local area A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet
network (E-LAN) virtual connection).
Ethernet private LAN A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
service (EPLAN) networks. This service is carried over dedicated bandwidth between multipoint-to-
multipoint connections.
Ethernet private line A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
(EPL) networks. This service is carried over dedicated bandwidth between point-to-point
connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private LAN service networks. This service is carried over shared bandwidth between multipoint-to-
(EVPLAN) multipoint connections.
Ethernet virtual A type of Ethernet service provided by SDH, PDH, ATM, or MPLS server layer
private line (EVPL) networks. This service is carried over shared bandwidth between point-to-point
connections.
European A standards-setting body in Europe. Also the standards body responsible for GSM.
Telecommunications
Standards Institute
(ETSI)
electromagnetic A condition which prevails when telecommunications equipment is performing its
compatibility (EMC) individually designed function in a common electromagnetic environment without
causing or suffering unacceptable degradation due to unintentional electromagnetic
interference to or from other equipment in the same environment.
electromagnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
interference (EMI) limits the performance of electronics/electrical equipment.
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer
channel (ECC) to enable the transmission of operation, administration, and maintenance (OAM)
information between NEs.
engineering label A mark on a cable, a subrack, or a cabinet for identification.
erasable A logic array device which can be used to implement the required functions by
programmable logic programming the array. In addition, a user can modify and program the array
device (EPLD) repeatedly until the program meets the requirement.
F
FD See frequency diversity.
FDDI See fiber distributed data interface.
FDI See forward defect indication.
FEC See forward error correction.
FFD fast failure detection
FFD packet A path failure detection method independent from CV. Different from a CV packet,
the frequency for generating FFD packets is configurable to satisfy different service
requirements. By default, the frequency is 20/s. An FFD packet contains information
the same as that in a CV packet. The destination end LSR processes FFD packets in
the same way for processing CV packets.
FIFO See first in first out.
G
GCRA generic cell rate algorithm
GFC generic flow control
GFP See Generic Framing Procedure.
GNE See gateway network element.
GPS See Global Positioning System.
GTS See generic traffic shaping.
GUI graphical user interface
Generic Framing A framing and encapsulated method that can be applied to any data type. GFP is
Procedure (GFP) defined by ITU-T G.7041.
Global Positioning A global navigation satellite system that provides reliable positioning, navigation, and
System (GPS) timing services to users worldwide.
gateway A device that connects two network segments using different protocols. It is used to
translate the data in the two network segments.
gateway network An NE that serves as a gateway for other NEs to communicate with a network
element (GNE) management system.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This
(GTS) is to adapt the traffic to network resources that can be provided by the downstream
router to avoid packet discarding and congestion.
H
HDLC High-Level Data Link Control
HQoS See hierarchical quality of service.
HSDPA See High Speed Downlink Packet Access.
HSM hitless switch mode
High Speed Downlink A modulating-demodulating algorithm put forward in 3GPP R5 to meet the
Packet Access requirement for asymmetric uplink and downlink transmission of data services. It
(HSDPA) enables the maximum downlink data service rate to reach 14.4 Mbit/s without
changing the WCDMA network topology.
hierarchical quality of A type of QoS that controls the traffic of users and performs the scheduling according
service (HQoS) to the priority of user services. HQoS has an advanced traffic statistics function, and
the administrator can monitor the usage of bandwidth of each service. Hence, the
bandwidth can be allocated reasonably through traffic analysis.
hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio
supports the AM function.
I
I/O input/output
ICMP See Internet Control Message Protocol.
IDU See indoor unit.
IEEE See Institute of Electrical and Electronics Engineers.
IF See intermediate frequency.
IGMP See Internet Group Management Protocol.
IGMP snooping A multicast constraint mechanism running on a layer 2 device. This protocol manages
and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented
efficiently.
IGP See Interior Gateway Protocol.
IMA See inverse multiplexing over ATM.
IP Internet Protocol
IPv4 See Internet Protocol version 4.
IPv6 See Internet Protocol version 6.
IS-IS See Intermediate System to Intermediate System.
ISDN integrated services digital network
ISO International Organization for Standardization
L
L2VPN Layer 2 virtual private network
LACP See Link Aggregation Control Protocol.
LAG See link aggregation group.
loopback (LB) A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loss measurement A method used to collect counter values applicable for ingress and egress service
(LM) frames where the counters maintain a count of transmitted and received data frames
between a pair of MEPs.
loss of signal (LOS) No transitions occurring in the received signal.
M
MA maintenance association
MAC See Media Access Control.
MADM multiple add/drop multiplexer
MBS maximum burst size
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDI medium dependent interface
MEP maintenance association end point
MIB See management information base.
MLPPP Multi-Link Point-to-Point Protocol
MP maintenance point
MPLS See Multiprotocol Label Switching.
MPLS L2VPN A network that provides the Layer 2 VPN service based on an MPLS network. In this
case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of
different media types, such as ATM, FR, VLAN, Ethernet, and PPP.
MPLS TE multiprotocol label switching traffic engineering
MPLS VPN See multiprotocol label switching virtual private network.
MS multiplex section
MSP See multiplex section protection.
MST region See Multiple Spanning Tree region.
MSTI See multiple spanning tree instance.
MSTP See Multiple Spanning Tree Protocol.
MTBF See mean time between failures.
MTTR See mean time to repair.
MTU See maximum transmission unit.
Media Access Control A protocol at the media access control sublayer. The protocol is at the lower part of
(MAC) the data link layer in the OSI model and is mainly responsible for controlling and
connecting the physical media at the physical layer. When transmitting data, the MAC
protocol checks whether to be able to transmit data. If the data can be transmitted,
certain control information is added to the data, and then the data and the control
information are transmitted in a specified format to the physical layer. When receiving
data, the MAC protocol checks whether the information is correct and whether the
data is transmitted correctly. If the information is correct and the data is transmitted
correctly, the control information is removed from the data and then the data is
transmitted to the LLC layer.
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks
Tree Protocol (MSTP) redundant paths so that the loop network can be trimmed as a tree network. In this
case, the proliferation and endless cycling of packets is avoided in the loop network.
The protocol that introduces the mapping between VLANs and multiple spanning
trees. This solves the problem that data cannot be normally forwarded in a VLAN
because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
Multiple Spanning A region that consists of switches that support the MSTP in the LAN and links among
Tree region (MST them. Switches physically and directly connected and configured with the same MST
region) region attributes belong to the same MST region.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different
Switching (MPLS) link layers, and provides connection-oriented switching for the network layer on the
basis of IP routing and control protocols.
maintenance domain The network or the part of the network for which connectivity is managed by
(MD) connectivity fault management (CFM). The devices in a maintenance domain are
managed by a single Internet service provider (ISP).
management A type of database used for managing the devices in a communications network. It
information base comprises a collection of objects in a (virtual) database used to manage entities (such
(MIB) as routers and switches) in a network.
maximum The largest packet of data that can be transmitted on a network. MTU size varies,
transmission unit depending on the network576 bytes on X.25 networks, for example, 1500 bytes on
(MTU) Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the
size of the MTU lies with the link layer of the network. When packets are transmitted
across networks, the path MTU, or PMTU, represents the smallest packet size (the one
that all networks can transmit without breaking up the packet) among the networks
involved.
mean time between The average time between consecutive failures of a piece of equipment. It is a measure
failures (MTBF) of the reliability of the system.
mean time to repair The average time that a device will take to recover from a failure.
(MTTR)
message digest A hash function that is used in a variety of security applications to check message
algorithm 5 (MD5) integrity. MD5 processes a variable-length message into a fixed-length output of 128
bits. It breaks up an input message into 512-bit blocks (sixteen 32-bit little-endian
integers). After a series of processing, the output consists of four 32-bit words, which
are then cascaded into a 128-bit hash number.
multicast A process of transmitting data packets from one source to many destinations. The
destination address of the multicast packet uses Class D address, that is, the IP address
ranges from 224.0.0.0 to 239.255.255.255. Each multicast address represents a
multicast group rather than a host.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a
instance (MSTI) simply and fully connected active topology for frames classified as belonging to a
VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be
assigned to multiple MSTIs.
multiplex section A function, which is performed to provide capability for switching a signal between
protection (MSP) and including two multiplex section termination (MST) functions, from a "working" to
a "protection" channel.
multiprotocol label An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol
switching virtual label switching (MPLS) technology. It applies the MPLS technology for network
private network routers and switches, simplifies the routing mode of core routers, and combines
(MPLS VPN) traditional routing technology and label switching technology. It can be used to
construct the broadband Intranet and Extranet to meet various service requirements.
N
N+1 protection A radio link protection system composed of N working channels and one protection
channel.
NE network element
NE Explorer The main operation interface of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, a user can query, manage, and
maintain NEs, boards, and ports.
NNI network-to-network interface
NPE network provider edge
NSAP See network service access point.
NSF non-stop forwarding
network service access A network address defined by ISO, at which the OSI Network Service is made
point (NSAP) available to a Network service user by the Network service provider.
network storm A phenomenon that occurs during data communication. To be specific, mass broadcast
packets are transmitted in a short time; the network is congested; transmission quality
and availability of the network decrease rapidly. The network storm is caused by
network connection or configuration problems.
node A managed device in the network. For a device with a single frame, one node stands
for one device. For a device with multiple frames, one node stands for one frame of
the device.
non-GNE See non-gateway network element.
non-gateway network A network element that communicates with the NM application layer through the
element (non-GNE) gateway NE application layer.
O
O&M operation and maintenance
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
ODF optical distribution frame
P
P2P See point-to-point service.
PBS See peak burst size.
PCB See printed circuit board.
PDH See plesiochronous digital hierarchy.
PDU protocol data unit
PE See provider edge.
PHB See per-hop behavior.
PIR peak information rate
PLA See physical link aggregation.
PLL See phase-locked loop.
PPP Point-to-Point Protocol
PRBS See pseudo random binary sequence.
PRI primary rate interface
PSN See packet switched network.
PSTN See public switched telephone network.
PTN packet transport network
PTP Precision Time Protocol
PTP clock See Precision Time Protocol clock.
PVP See permanent virtual path.
PW See pseudo wire.
PWE3 See pseudo wire emulation edge-to-edge.
Precision Time A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588
Protocol clock (PTP V2 standard specifies the precision time protocol (PTP) in a measurement and control
clock) system. The PTP protocol ensures clock synchronization precise to sub-microseconds.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of
edge-to-edge (PWE3) a telecommunication service such as ATM, FR or Ethernet in a packet switched
network (PSN). PWE3 also emulates the essential attributes of low speed time
division multiplexing (TDM) circuit and SONET/SDH. The simulation approximates
to the real situation.
public switched A telecommunications network established to perform telephone services for the
telephone network public subscribers. Sometimes it is called POTS.
(PSTN)
Q
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
QoS See quality of service.
quadrature phase shift A modulation method of data transmission through the conversion or modulation and
keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth
period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four
dots are evenly distributed on a circle. On these phases, each QPSK character can
perform two-bit coding and display the codes in Gray code on graph with the
minimum BER.
quality of service A commonly-used performance indicator of a telecommunication system or channel.
(QoS) Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.
R
RADIUS See Remote Authentication Dial In User Service.
RADIUS accounting An accounting mode in which the BRAS sends the accounting packets to the RADIUS
server. Then the RADIUS server performs accounting.
RDI remote defect indication
RED See random early detection.
REI remote error indication
RF See radio frequency.
RFC See Request For Comments.
RMEP remote maintenance association end point
RMON remote network monitoring
RNC See radio network controller.
RSL See received signal level.
RSSI See received signal strength indicator.
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
router A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
rt-VBR See real-time variable bit rate.
S
SAI service area identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SCSI Small Computer System Interface
SD See space diversity.
SDH See synchronous digital hierarchy.
SEC security screening
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
SFP small form-factor pluggable
SLA See service level agreement.
SNCP subnetwork connection protection
SNMP See Simple Network Management Protocol.
SNR See signal-to-noise ratio.
SSL See Secure Sockets Layer.
SSM See Synchronization Status Message.
STM See synchronous transport module.
STM-1 See Synchronous Transport Module level 1.
STM-4 Synchronous Transport Module level 4
STM-N Synchronous Transport Module level N
STP Spanning Tree Protocol
Secure Sockets Layer A security protocol that works at a socket level. This layer exists between the TCP
(SSL) layer and the application layer to encrypt/decode data and authenticate concerned
entities.
Simple Network A network management protocol of TCP/IP. It enables remote users to view and
Management Protocol modify the management information of a network element. This protocol ensures the
(SNMP) transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents,
which can be hardware as well as software, can monitor the activities of various
devices on the network and report these activities to the network console workstation.
Control information about each device is maintained by a management information
block.
Synchronization Status A message that carries the quality levels of timing signals on a synchronous timing
Message (SSM) link. SSM messages provide upstream clock information to nodes on an SDH network
or synchronization network.
Synchronous Synchronous transfer mode at 155 Mbit/s.
Transport Module
level 1 (STM-1)
service level agreement A service agreement between a customer and a service provider. SLA specifies the
(SLA) service level for a customer. The customer can be a user organization (source domain)
or another differentiated services domain (upstream domain). An SLA may include
traffic conditioning rules which constitute a traffic conditioning agreement as a whole
or partially.
signal fail (SF) A signal indicating that associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal-to-noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
(SNR) given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB.
single-ended switching A protection mechanism that takes switching action only at the affected end of the
protected entity in the case of a unidirectional failure.
single-polarized An antenna intended to radiate or receive radio waves with only one specified
antenna polarization.
space diversity (SD) A diversity scheme that enables two or more antennas separated by a specific distance
to 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.
subnet mask The technique used by the IP protocol to determine which network segment packets
are destined for. The subnet mask is a binary pattern that is stored in the device and is
matched with the IP address.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. SDH defines the
hierarchy (SDH) transmission features of digital signals, such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN.
synchronous transport An information structure used to support section layer connections in the SDH. It
module (STM) consists of information payload and Section Overhead (SOH) information fields
organized in a block frame structure which repeats every 125. The information is
suitably conditioned for serial transmission on the selected media at a rate which is
synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed
STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic
rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are
under consideration.
T
T1 A North American standard for high-speed data transmission at 1.544Mbps. It
provides 24 x 64 kbit/s channels.
TCI tag control information
TCP See Transmission Control Protocol.
TCP/IP Transmission Control Protocol/Internet Protocol
traffic engineering A technology that is used to dynamically monitor the traffic of the network and the
(TE) load of the network elements, to adjust in real time the parameters such as traffic
management parameters, route parameters and resource restriction parameters, and to
optimize the utilization of network resources. The purpose is to prevent the congestion
caused by unbalanced loads.
traffic engineering A type of database that every router generates after collecting the information about
database (TEDB) TE of every links in its area. TEDB is the base of forming the dynamic TE path in the
MPLS TE network.
tributary loopback A fault can be located for each service path by performing loopback to each path of
the tributary board. There are three kinds of loopback modes: no loopback, outloop,
and inloop.
tunnel A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The
tunnel ensures secure and transparent transmission of VPN information. In most cases,
a tunnel is an MPLS tunnel.
two rate three color An algorithm that meters an IP packet stream and marks its packets based on two
marker (trTCM) rates, Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether
it exceeds or does not exceed the CIR.
U
UART universal asynchronous receiver/transmitter
UAS unavailable second
UBR unspecified bit rate
UBR+ Unspecified Bit Rate Plus
UDP See User Datagram Protocol.
UI user interface
UNI See user-to-network interface.
UPC See usage parameter control.
User Datagram A TCP/IP standard protocol that allows an application program on one device to send
Protocol (UDP) a datagram to an application program on another. UDP uses IP to deliver datagrams.
UDP provides application programs with the unreliable connectionless packet delivery
service. That is, UDP messages may be lost, duplicated, delayed, or delivered out of
order. The destination device does not actively confirm whether the correct data
packet is received.
unicast The process of sending data from a source to a single recipient.
usage parameter During communications, UPC is implemented to monitor the actual traffic on each
control (UPC) virtual circuit that is input to the network. Once the specified parameter is exceeded,
measures will be taken to control. NPC is similar to UPC in function. The difference is
that the incoming traffic monitoring function is divided into UPC and NPC according
to their positions. UPC locates at the user/network interface, while NPC at the network
interface.
user-to-network The interface between user equipment and private or public network equipment (for
interface (UNI) example, ATM switches).
V
V-NNI virtual network-network interface
V-UNI See virtual user-network interface.
VB virtual bridge
VBR See variable bit rate.
VC See virtual container.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCI virtual channel identifier
VCTRUNK A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VLAN virtual local area network
VPI See virtual path identifier.
VPLS virtual private LAN segment
VPN virtual private network
VSWR voltage standing wave ratio
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice
calls.
virtual channel A VC logical trail that carries data between two end points in an ATM network. A
connection (VCC) point-to-multipoint VCC is a set of ATM virtual connections between two or multiple
end points.
virtual circuit A channel or circuit established between two points on a data communications
network with packet switching. Virtual circuits can be permanent virtual circuits
(PVCs) or switched virtual circuits (SVCs) .
virtual concatenation A group of co-located member trail termination functions that are connected to the
group (VCG) same virtual concatenation link.
virtual container (VC) An information structure used to support path layer connections in the SDH. A VC
consists of a payload and path overhead (POH), which are organized in a block frame
structure that repeats every 125 s or 500 s.
virtual path identifier The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to
(VPI) which virtual path the cell belongs.
virtual user-network A virtual user-network interface, works as an action point to perform service
interface (V-UNI) classification and traffic control in HQoS.
X
XPIC See cross-polarization interference cancellation.