OSN 8800 6800 3800 V100R011C10 Trouble Shooting 01
OSN 8800 6800 3800 V100R011C10 Trouble Shooting 01
V100R011C10
Troubleshooting
Issue 01
Date 2017-03-31
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: [email protected]
Related Versions
The following table lists the product versions related to this document.
Intended Audience
The intended audiences of this document are:
Field maintenance engineers
Network monitoring engineers
System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol 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
3 Basic Concepts 3.8 Test Frame: Added the TN17LSCM and the TN15LTX board.
and Common 3.10 Port Mirroring Analysis: Added the EX8 board.
Methods of Fault
Locating
Update Description
Update Description
Update Description
Fault Location Fault Location Using IP Ping: Added the description about IP ping
Using TP-Assist initiation functions.
E-LAN Service Loopback Detection: Added the procedure of
periodic loopback detection.
Update Description
Update Description
Fault Location Section "E-LAN Service Loopback Detection" has split to Section
Using TP-Assist "E-LAN Service Loopback Detection by Station" and Section
"Performing E-LAN Service Loopback Detection".
Update Description
Update Description
3 Basic Concepts Updated the list of boards supporting the test frame function in "3.8
and Common Test Frame".
Methods of Fault
Locating
Update Description
3 Basic Concepts Updated "3.8 Test Frame": optimized application 2 of ethernet test
and Common frame.
Methods of Fault
Locating
Fault Location Updated the procedure of "Performing Intelligent Service Fault
Using TP-Assist Diagnosis for Ethernet Services".
Update Description
3 Basic Concepts Updated "3.8 Test Frame", added TN54TSC board, added a application
and Common of ethernet test frames.
Methods of Fault
Locating
Update Description
Update Description
Update Description
3 Basic Concepts Updated "3.8 Test Frame": optimized application 2 of ethernet test
and Common frame.
Methods of Fault
Locating
Update Description
3 Basic Concepts Updated "3.8 Test Frame", added 100G OTU board.
and Common
Methods of Fault
Locating
Update Description
Update Description
3 Basic Concepts and Common 3.6 PRBS Test: Updated PRBS networking
Methods of Fault Locating applications.
3.8 Test Frame: Added the 40G service type and
the supported board.
Added "3.11 One-Click Data Collection".
10 Automatic Switching Failures 10.5 ODUk SNCP Protection: Updated the solution of
troubleshooting.
Update Description
12.4 IPA End Failure in a Raman Causes and diagnosis methods for the fault are added.
System
Update Description
Update Description
Entire manual This manual provides descriptions according to product series OptiX
OSN 8800, OptiX OSN 6800, and OptiX OSN 3800. Any difference
between the products is described in the manual.
Contents
7 Bit Errors............................................................................................................................... 83
7.1 Multi-Channel Bit Errors.................................................................................................................................................... 83
7.2 Single-Channel Bit Errors .................................................................................................................................................. 86
7.3 Bit Errors Due to Unfavorable Environmental Conditions .............................................................................................. 87
7.4 Bit Errors Due to Device Faults ......................................................................................................................................... 91
7.5 Bit Error Cases .................................................................................................................................................................... 93
1 Overview
1.1.1 Laser
When you install and maintain equipment, follow the safety precautions described below to
help prevent personal injury or equipment damage. The laser complies with IEC60825.
The safety precautions of lasers consist of two parts:
Personal injury
Equipment damage
Personal Injury
Laser beams from the optical ports on boards or from the fiber connectors cause eye damage.
Do not look directly at the optical ports or fiber connectors during the installation and
maintenance of boards or fibers. Do not shine laser beams into the eyes of other workers.
To prevent eye damage in the case of an optical port that is in use, use protective caps to cover
the optical interface and the fiber connector after you remove the fiber from the optical
interface.
The optical power of the LINE interface on the Raman amplifier board is very high. Shut
down the pump laser before you insert or remove fiber connectors on the Raman amplifier
board to help prevent personal injury that is caused by high optical power.
Equipment Damage
Use protective caps to cover unused optical ports and fiber connectors so that they do not
gather dust.
When performing a hardware loopback test on optical ports using a fiber, add an optical
attenuator to prevent damage to the equipment because of the high power of the laser beam.
Add the attenuator at the receive optical port on a board that supports optical attenuators.
When you use the optical time domain reflectometer (OTDR), disconnect the fiber between
the opposite station and the board to prevent damage to the receive optical module because of
high optical power.
Exercise caution when you remove or insert a board that is connected with fibers.
The optical power of the Raman amplifier board is very high. Observe the following
precautions when using the Raman amplifier board to prevent damage to the equipment.
Do not use fiber connectors within 0–20 km. The fibers at every joint point must be
spliced.
The single-point additional loss within 0–10 km must be smaller than 0.1 dB (G.652) or
0.2 dB (G.655) and the single-point return loss must not be smaller than 40 dB.
The single-point additional loss within 10–20 km must be smaller than 0.2 dB (G.652) or
0.4 dB (G.655) and the single-point return loss must not be smaller than 40 dB.
Fiber connections must be complete before you enable the lasers on the Raman amplifier
board. Make sure that the fiber connectors are clean. Otherwise, the fiber connectors might
be damaged when you insert or remove the fiber connectors.
The optical power of the LINE interface on the Raman amplifier board is very high. The
LSH/APC optical connectors must be used in the fiber that is connected to the LINE
interface.
For the Raman amplifier board with backward pump, the strong pump light enters the fiber
through the input end (LINE) instead of the output end (SYS). Do not add boards or
non-fiber devices, such as attenuators or fiber jumpers, at the input end.
The bent radius of the fiber that is connected to the LINE interface on the Raman amplifier
board must be larger than 30 mm to prevent the fiber from being burned.
Ensure that screws do not fall off into the subrack or chassis.
1.1.3 ESD
During installation and maintenance, follow ESD procedures to prevent equipment damage:
Always wear an ESD wrist strap during the operation.
Check that the equipment is securely grounded.
Wear a well-grounded ESD wrist strap whenever you touch equipment or boards. Make sure
that the wrist strap touches your skin. Insert the ESD strap connector into the ESD socket of
the equipment.
For information about how to wear an ESD wrist strap, see Figure 1-1.
Insert the connector of the ESD strap into the equipment port. For details, see the Quick Installation
Guide.
When you are following ESD procedures, take the following precautions:
Check the validity and functionality of the wrist strap. Its resistance value must be
between 0.75 mega ohm to 10 mega ohm. If the wrist strap validity period (usually two
years) has expired, or if the resistance value fails to meet requirements, replace it with a
wrist strap that provides the required resistance value.
Do not touch a board with your clothing. Clothing generates static electricity that is not
protected by the wrist strap.
Wear an ESD wrist strap and place the board on an ESD pad when you replace boards or
chips. Use ESD tweezers or extraction tools to replace chips. Do not touch chips, circuits,
or pins with your bare hands.
Keep the boards and other ESD-sensitive parts you are installing in ESD bags. Place the
removed boards and components on an ESD pad or ESD material. Do not use
non-antistatic materials such as white foams, common plastic bags, or paper bags to pack
boards, and do not let these materials touch the boards.
Wear an ESD wrist strap when operating the ports of boards because they are also
ESD-sensitive. Discharge the static electricity of cables and protective sleeves before
you connect them to the ports.
Keep packing materials (such as, ESD boxes and bags) available in the equipment room
for packing boards in the future.
ESD complies with IEC Publication 1000, EN 55022, EN 55024, IEC 61000 and
GR-1089-CORE.
Symbol Describes
CAUTION
HAZARD LEVEL 1M INVISIBLE
LASER RADIATION
DO NOT VIEW DIRECTLY WITH
NON-ATTENUATING OPTICAL
INSTRUMENTS
Grounding symbol.
Indicates the position of the grounding
point.
Name Usage
Fiberscope Checks whether the optical fiber end faces are clean.
Background Knowledge
WDM fundamentals
The WDM system alarm generation mechanism
Troubleshooting methods for common alarms
Basic Operations
Basic transmission equipment operations
Basic network management system (NMS) operations
For basic NMS operations, refer to the OptiX iManager U2000 Operator Guide or the on-line
help.
Network Layout
The network layout of the project
The service configuration, wavelength assignment, optical distribution frame (ODF), fiber
routing, board version, and equipment layout in each office.
The current equipment running status in local office
The relevant engineering files and documents (which need to be updated periodically)
2 Troubleshooting Workflow
2.1.1 Workflow
This topic describes how to handle general faults.
The following figure describes how to handle general faults.
External Faults
Handle faults caused by any of the following external factors:
Power failure
Optical cable fault
Environment variable (for example, telecommunications room temperature)
Terminal equipment
Technical Support
Contact Huawei Customer Service Center (CSC) for assistance locating and resolving any
issues beyond the scope of this document.
You can also contact the technical support personnel in Huawei's local representative office in
either of the following ways:
Hotline: 4008302118
E-mail: [email protected]
Troubleshooting Reports
After the fault is resolved, fill in the related troubleshooting report in a timely manner and
summarize how the fault was handled.
2.2.1 Workflow
This topic describes emergency handling workflow.
The emergency handling flow refers to the fault handling flow when the service of the
equipment is interrupted due to external faults (such as power supply fault or fiber cut),
misoperations, or software/hardware faults of the equipment. In the case of the OptiX WDM
optical transmission equipment, in addition to clearing the fault according to the
troubleshooting flow, take other emergency measures (such as providing standby channels) or
ask for help in time to reduce the service interruption duration. The emergency
troubleshooting process refers to the troubleshooting process when services on the equipment
are interrupted due to external faults, such as a power failure or damaged fiber cables,
incorrect operations, or software/hardware faults of the equipment. For the OptiX WDM
optical transmission equipment, in addition to clearing the fault according to the
troubleshooting process, take other emergency measures, such as providing standby channels,
or ask for help in time to reduce the duration of service interruption.
When handling service interruptions or other emergencies, note the following points:
No
No The
Locate the faulty
Yes R_LOS/R_LOF/MUT_L The power Yes
Yes section along the signal Yes
1 Check alarms with the NMS OS/IN_PWR- supply/optical cable
flow and confirm
LOW/PWR_HIGH/NE- is faulty?
whether the NE is
unreachable alarm
unreachable
exists?
No No No
No
The fault is a multi-
The fault is a cross- channel fault, go to 5
connect fault, go to 3
The
OTU_LOF/OTU_LOM/
Yes
ODU_LOF/ODU_LOM/
ODUk_PM_SSF/ODUk
_PM_BDI alarm
exists?
Yes
The fault is an Check the bit error The fault is a single- Replace the faulty
OTN/electrical layer performance and locate channel fault, go to 6 board
fault, go to 4 the channel with
excessive bit errors
The system
Yes OSNR/nonlinearity/fiber
jumper between the OTU
and MUX/DEMUX board
is faulty?
The fiber
Yes The system OSNR or Yes Yes connections between
nonlinearity is improper or The cross-connection OTU/tributary/line
the fiber jumper/optical configuration is correct? boards at the
cable is faulty? local/opposite end
are normal?
No No No
No
Replace the faulty
board
The
LSR_WILL_DIE/OUT_PWR_HIGH/
OUT_PWR/LOW alarm exists on
the OTU/line board at the opposite
end?
Handle the fiber
jumper/optical cable
fault
Replace the faulty Replace the faulty
board at the local end board at the opposite
end
Both
the transmit and receive Yes
optical power values are Compare the current optical power of the
abnormal? OTU/tributary/line board of the faulty
channel with the history normal value
No
Compare the current
optical power of the OA/
MUX/DEMUX board with
the history normal value
The
OTU/tributary/line Yes
board is faulty?
The
The OA/MUX/DEMUX
Yes Yes
OA/MUX/DEMUX boards at both the transmit
board is faulty? and receive ends
are No
faulty?
No No
Replace the internal fiber
Handle the fiber Replace the faulty Handle the fiber between the OTU and Replace the faulty board
jumper/optical cable fault board jumper/optical cable fault MUX/DEMUX boards
2.2.2 Description
This topic describes the emergency troubleshooting process.
Handling Alarms
If an R_LOS, R_LOF, MUT_LOS, IN_PWR_HIGH, IN_PWR_LOW, or
NE-unreachable alarm is reported, check and analyze the alarm.
− When such an alarm occurs, if the power supply or optical cable is faulty, handle
these faults first.
− Determine whether the fault is a multi-channel or single-channel issue based on the
the range of services affected, and handle it accordingly.
− If multiple channels are faulty, check the transmit/receive optical power and
compare the current optical power of the optical amplifier (OA)/multiplexer
(MUX)/ demultiplexer (DEMUX) board with the historical normal value. Check the
network section by section to determine whether the line, pigtail, or
OA/MUX/DEMUX board is faulty. Then handle the line/pigtail fault or replace the
board accordingly.
− If only one channel is faulty, compare the current optical power of the optical
transponder unit (OTU)/tributary/line board on the faulty channel with the historical
normal value to determine whether the board or intra-board fiber connection is
faulty. Then replace the faulty board or change the internal fiber connections
accordingly.
If no R_LOS, R_LOF, MUT_LOS, IN_PWR_HIGH, IN_PWR_LOW, or
NE-unreachable alarm is reported, check the bit error rate (BER) performance or optical
power performance for any of the following problems.
− If all channels have excessive bit errors, a system fault has occurred. Check the
network section by section along the signal flow to determine whether the system
OSNR and nonlinearity are correct and whether the pigtail/optical cable is faulty. If
the system OSNR and nonlinearity are incorrect and the pigtail/optical cable is
faulty, handle the pigtail/optical cable fault. If the pigtail/optical cable is functioning
normally, the OA/MUX/DEMUX board is faulty and should be replaced.
− If the fault is not a system fault and the BUS_ERR alarm is reported, the fault is a
cross-connection fault. If the cross-connection configuration is incorrect, modify it
to resolve the fault. If it is correct, the tributary/line/cross-connect board is faulty
and should be replaced.
− If the
OTU_LOF/OTU_LOM/ODU_LOF/ODU_LOM/ODUk_PM_SSF/ODUk_PM_BDI
alarm is reported, the OTN/electrical layer is faulty. Check whether the fiber
connections between OTU boards, tributary boards, or line boards at the local and
opposite ends are faulty. If any of these is faulty, handle the fiber connection faults,
including the inconsistency between logical and physical fiber connections and
physical fiber connection faults.
− If a TD/TF/LSR_WILL_DIE alarm is reported by an OTU/line board, the board is
faulty and should be replaced.
As shown in the flowchart, optical-layer faults and fiber connection faults cause OTN alarms. Therefore,
these faults must be handled first. After these faults are cleared, OTN alarms will typically clear also.
a: Common alarms are listed by board type in the table. Alarms for different boards of the same type
may differ slightly.
In addition, there are various running and alarm indicators with different colors on the
equipment. The On/Off and flashing states of these indicators indicate the current running
state or possible alarm of the equipment. Such indication helps you analyze the cause of the
fault and accordingly handle the alarm. Refer to the Indicators.
If you observe only the alarm indicators on the top of the cabinet, minor equipment alarms
may be missed (in the case of minor alarms, the alarm indicators on the top of the cabinet do
not light up, whereas the alarm indicators on the board do). In most cases, a minor alarm
indicates a potential fault at the local or opposite end. Such alarms cannot be neglected.
Equipment indicators indicate only the current operating status of the equipment, not the
faults that have already occurred and been cleared.
The indicator status that corresponds to a specific alarm category can be redefined on the
U2000, and certain alarm types can even be suppressed.
The board alarm indicator reports the alarm with the highest severity level detected by the
board.
Before short-circuiting the transmit port of the corresponding OTU/tributary board at the
opposite station to the receive port of the corresponding OTU/tributary board, determine
whether to add an optical attenuator to the receive optical port on the OTU/tributary board.
The appropriate optical attenuator is determined based on the optical power specification on
the transmit port of the OTU/tributary board. Otherwise, optical power overload might
damage the OTU/tributary board.
− Method 2: For an OTU/tributary board that supports B1 bit error detection, compare
whether the RSES performance value of the OTU/tributary board at the local station
is the same as that at the opposite station. If they are the same, the system has no
new bit errors and is operating normally, which indicates that the fault is located on
the client side.
− Method 3: If users check client equipment on site, they can perform a self-loop (an
optical attenuator is required) on the receive and transmit optical ports of the client
equipment to check the alarms on the equipment. If alarms persist or the bit error
meter still detects bit errors, the fault is occurring on the client side.
Troubleshooting an optical cable fault
To troubleshoot an optical cable fault, use any of the following methods:
− Method 1: Test the input optical power of the local station and the output optical
power of the upstream station. If the difference between the two values (that is, the
attenuation) is less than the designated value, the optical cable is functioning
normally; otherwise, the optical cable is faulty.
− Method 2: Check whether optical cable parameters such as the type and length meet
the design requirements. If not, the optical cable is faulty.
− Method 3: If the optical cable meets design requirements, check whether the optical
cable connector is properly attached. Ensure that the connection is normal.
− Method 4: Switch system services to the backup optical cable. If the alarm is
cleared, the optical cable is faulty.
− Method 5: Use an OTDR to measure the optical power and determine whether the
optical cable is faulty. If the reflectance of the tested optical fiber core is less than
27 dB and the attenuation of the fiber core is less than the designated value, the
optical cable is functioning normally. Otherwise, the optical cable is faulty. Note
that the OTDR has a blind spot within a short distance (smaller than 5 km), in
which the test results are inaccurate.
When you use the OTDR, separate the optical fiber from the equipment. Otherwise, the
intense OTDR light might damage the equipment.
Troubleshooting a power supply fault
If you cannot log in to a station and all boards connected to the station report alarms
indicating input signal loss, the power supply of this station might be faulty. This causes a
power failure at this station and triggers the alarm. If this station suddenly enters an abnormal
operating status, the optical power of the station will suddenly decrease, some boards will
operate abnormally, services will be interrupted, and abnormal login will occur. Check
whether the power supply voltage of the transmission equipment is or a low-frequency
transient voltage surge occurred.
Troubleshooting a grounding fault
If the equipment is struck by lightning or cannot be interconnected, check the grounding.
Check whether the equipment is grounded in compliance with the specifications, whether any
equipment is disconnected from the public ground bar, and whether all types of equipment in
the same telecommunications room are grounded similarly. Then use an earth resistance tester
to test whether the grounding resistance and the potential between working and protection
grounds are within the permitted range.
Figure 3-1 Signal flow analysis: Each station uses tributary and line boards
Tributary Line Line Tributary Client
Client
board board MUX OA OA DEMUX board board equipment
equipment
DEMUX OA OA MUX
Station A Station B
The U2000 provides the service signal flow interface. For details on how to view the service signal flow
using the GUIs, see "Viewing the Signal Flow Diagram for a WDM Trail" in the Online Help.
Fault analysis:
As shown in the preceding figure, the service signal flow of the client equipment at
station B is: client equipment at station A → the tributary board at station A → the
cross-connect board at station A → the line board at station A → MUX at station A →
OA at station A → OA at station B → DEMUX at station B → the line board at station B
→ the cross-connect board at station B → the tributary board at station B → client
equipment at station B.
Possible causes are as follows:
− The transmit unit of station A is faulty.
− The optical path (including the optical fibers and fiber connectors) is faulty.
− The receive unit of station B is faulty.
a. Analyze the alarms and performance of the tributary board at station A. If the
client-side port of this tributary board receives no optical signal or its receive
optical power is too low, the fault location can be refined to the transmit end of the
client equipment at station A, the pigtail from the client equipment to the tributary
board, or the client-side receive module of the tributary board.
b. If the client-side input optical power of the tributary board at station A is normal,
check whether the cross-connection configuration is correct. If it is correct, locate
the corresponding line board based on the cross-connection. Then, check the alarms
and performance events of the tributary and line boards at station B for BUS_ERR
alarms. If BUS_ERR alarms are reported, the fault may be occurring on the
tributary, cross-connect, or line board. If needed, you can change the configuration
or replace the related boards.
c. If no BUS_ERR alarms are reported, check whether the output optical power of the
line board is normal. If the optical power is abnormal, the fault is occurring on the
line board.
d. The remaining steps are similar to the fault analysis steps of a tributary/line
integrated board.
Client Client
equipment OTU MUX OA OA DEMUX OTU equipment
DEMUX OA OA MUX
Station A Station B
The U2000 provides the service signal flow interface. For information on how to view the service signal
flow in GUIs, see "Viewing the Signal Flow Diagram for a WDM Trail" in the Online Help.
Fault analysis:
The Client equipment at station B receives no optical signals or receives a large number
of bit errors. As shown in Figure 3-2, the service signal flow of the Client equipment at
station B is: Client equipment at station A → OTU at station A → MUX at station A →
OA at station A → OA at station B → DEMUX at station B → OTU at station B →
Client equipment at station B. Possible causes are as follows:
− The transmit unit of station A is faulty.
− The optical path (including the fibers and fiber connectors) is faulty.
− The receive unit of station B is faulty.
a. Analyze the alarms and performance of the OTU at station A. If the client-side
interface of this OTU receives no optical signal or its received optical power is too
low, locate the fault to the transmit end of the Client equipment at station A, the
fiber jumper from the client equipment to the OTU, or the client side receiver
module of the OTU.
b. If the input optical power of the OTU at station A is normal, check whether its
output optical power is normal. If not, locate the fault to this OTU.
c. If the output optical power of the OTU at station A is also normal, observe whether
the optical power of the MUX at station A sharply changes. If there are many
wavelengths at station A, the loss of one of them does not results in a great change
to the optical power. Therefore, feed the signals at the MON port of the MUX to the
MCA board and query for any loss-of-wavelength alarm.
d. The key components on the MUX are passive; therefore, the MUX is not likely to
be damaged. When the MCA detects the loss of a wavelength, the most possible
fault point is between the fiber jumper from the OTU to the MUX.
e. The OA provides a function of input and output optical power detection. If the OA
is faulty, multiple wavelengths are affected. As a result, the possibility is rather low
that the OA board is faulty.
f. At station B, analyze the signal flow in this order: OA at station B → DEMUX at
station B → OTU at station B → Client equipment at station B. The method to
analyze the signal flow at station B is similar to that of station A.
Before querying the performance data on the U2000, enable performance monitoring on
the U2000. Otherwise, the performance data will not be reported to the U2000.
Before querying the alarm or performance data on the U2000, ensure that the running time
of each NE is correctly set. Otherwise, the alarm and performance data will be incorrect or
not reported to the U2000.
During maintenance, after re-issuing the configuration to a NE, set the NE time to the
current time. Otherwise, the NE will operate at the incorrect default time.
The generation, detection, and transmission of an alarm varies with the OTU type and the type
of signals that the OTU receives. Alarm signal flow analysis allows you to quickly determine
where the fault is occurring.
Figure 3-3 Alarm and performance analysis: A Non-convergence OTU board processes
SDH-compliant signals
Client Client
equipment OTU MUX OA OA DEMUX OTU equipment
DEMUX OA OA MUX
Station A Station B
The automatic laser shutdown (ALS) function of the OTU board shown in the figure is disabled.
R_LOS
R_LOS REM_SF R_LOF
Alarm processing
As shown in Figure 3-4, the client side of the OTU board at station A receives R_LOS signals.
The WDM side of this OTU board reports an R_LOS alarm and sends the fault information to
station B. The client side of the OTU board at station B reports the REM_SF alarm and sends
the fault information to the downstream client device. The client device then reports an
R_LOF alarm.
If the client-side OTU board at station A reports the R_LOS alarm to the U2000, the
client-side equipment at station B reports the R_LOF alarm. In this case, the input signals on
the client side of the OTU board at station A are abnormal. Therefore, if the input signals on
the client side of the OTU board at station A are abnormal, the client device is normal and the
local device is faulty.
services are transmitted on the line, and the optical fiber between station A and station B
degrades.
Figure 3-5 Alarm and performance analysis: A non-convergence OTU board processes
OTN-compliant signals
Client Client
equipment OTU OTU-W OTU-E OTU equipment
The ALS function of the OTU board shown in this figure is disabled.
OTUk_LOF/
OTUk_LOM/ SF
OTUk_AIS OTUk_LOF/
OTUk_LOM/ ODUk_PM_AIS
OTUk_AIS
OTUk_BDI
ODUk_PM_BDI
As shown in Figure 3-6, when the optical fiber between station A and station B degrades, an
OTU2_LOF alarm is detected on the WDM side of the OTU-W at station B. After being
processed at station B, the OTU2_LOF alarm is transmitted to stations A and C. (If the optical
fiber is severely degraded, either an LOF or LOM alarm is generated. In this example, an LOF
alarm is generated.) At station C, an ODU2_PM_AIS alarm is detected on the WDM side of
the OTU board. After being processed at station C, the ODU2_PM_AIS alarm is transparently
transmitted to station B and then to station A. Then, station A reports OTU2_BDI and
ODU2_PM_BDI alarms.
If the WDM side of the OTU board at station A reports the OTU2_BDI and ODU2_PM_BDI
alarms to the U2000, the WDM side of the OTU-W board at station B reports the OTU2_LOF
alarm, and the WDM side of the OTU board at station C reports the ODU2_PM_AIS alarm.
In this case, the input signals on the WDM side of the OTU board at station B are abnormal.
Further analysis can be performed to determine whether the fault is caused by degraded
optical fibers.
Overview
The most commonly used test instruments for the WDM system include the optical power
meter, optical spectrum analyzer, SDH/SONET tester, SmartBits tester, communication signal
analyzer and multimeter. Among these tools, the optical power meter and optical spectrum
analyzer are most often used.
Application
Optical power meter
The optical power of each point can be obtained from the U2000 performance data.
However, to get a precise reading for a specific point, you must measure the optical
power at that point using an optical power meter.
When the output optical power of the MUX boards, the input optical power of the DEMUX
boards, or the input and output optical power of the OA boards are abnormal, all services are
interrupted if the line is disconnected for testing. Therefore, do not disconnect the line to test
the optical power of the main-path signal unless absolutely necessary.
You can test the output optical power on the MON port of various boards. Use this tested
value and the ratio of the tested value to the optical power of the main-path signal to
calculate the optical power of the main-path signal.
Optical spectrum analyzer
Use an optical spectrum analyzer to test the optical spectrum of the output signal on the
MON port of the board. Read from the spectrum analyzer the optical power, OSNR,
central wavelength and analyze the gain flatness of the OA. Compare this data with the
original data and check whether there is a significant performance deterioration (for the
original data, refer to the engineering documentation). Verify the following items:
− Per-channel optical power is normal and the gain flatness is normal.
− OSNR meets the design requirements.
− Deviation of the central wavelength is lower than the specification.
The main-path optical spectrum on the MON ports of boards can be tested online. If all the services
carried on the main path are affected, analyze the optical spectrum of the OA boards. If only one service
channel on the main path is affected, analyze the optical spectrum of the MUX and DEMUX boards.
SDH/SONET tester, SmartBits tester, and communication signal analyzer
If it is suspected that the poor interconnection is caused by signal error, use these
analyzers to check whether the frame signals and overhead bytes are normal, and check
whether there are any abnormal alarms.
Multimeter
If it is suspected that the power supply is too high or too low, use a multimeter to
measure the input voltage.
If it is suspected that the poor interconnection is caused by improper grounding, use a
multimeter to measure the voltage between the shield layers of the coaxial ports at the
transmit and receive ends of interconnected channels. If the voltage is more than 0.5 V,
the grounding is improper.
3.4 Loopback
The loopback method is the most common and effective method to locate a fault in a transport
network. The key feature of this method is that it does not require in-depth analysis of alarm
and performance information. Maintenance engineers should be familiar with this method.
There are software loopbacks and hardware loopbacks, which have the following advantages
and disadvantages:
A hardware loopback is performed on a physical port (optical port) using an optical fiber.
Compared with the software loopback, the hardware loopback is more reliable. The
hardware loopback, however, requires on-site operations. In addition, a receive optical
power overload must be avoided when performing a hardware loopback.
Compared with the hardware loopback, the software loopback is simpler but cannot
locate a fault as accurately. For example, during a single station test, if a software inloop
is performed on an optical port and the service is normal, the line board may not
necessarily be normal. However, if a selfloop is performed on the same optical port using
a pigtail and the service is normal, line board is normal.
For loopback configurations, refer to Performing Software Loopback on NMS and
Performing Hardware Loopback on Site.
When performing a loopback on the optical path of the multiplex section, ensure that the
OSNR and dispersion meet the OTU requirements.
This method affects service quality. Therefore, it is generally used in deployment
commissioning or fault location in situations where services have been interrupted.
If the protection scheme has been configured, loopback is not recommended. Otherwise,
protection switching may fail. If a loopback is required, lock the protected services on the
current channel before performing the loopback, and unlock the services after the loopback is
completed.
Application
The loopback method is applicable when the approximate range of the fault is known. The
fault is located by applying the loopback method on a section by section basis. This method
clears board and line faults. Figure 3-7 provides an example of fault isolation using the
loopback method.
Client Client
equipment OTU MUX OA OA DEMUX OTU equipment
DEMUX OA OA MUX
Inloop on
client side
Station A (OTM) Station B (OTM)
In Figure 3-7, the client side of the OTU at station A reports an R_LOS alarm whereas the
WDM side at station A reports no alarm. The WDM side and client sides of the OTU board at
station B report no alarms whereas the client equipment at station B reports an R_LOF alarm.
Perform an inloop on the client side of the OTU board at station A as shown in Figure 3-7.
If the alarms at both stations A and B are cleared, the OTU board at station A is receiving
no signal from the client equipment at station A. The fault is occurring on the client
equipment at station A or the optical fiber from the client equipment at station A to the
OTU board at station A.
If the alarms at stations A and B persist, the fault is occurring on the OTU board at
station A.
The faulty point can be identified quickly using the analysis method described in the "3.2 Alarm and
Performance Analysis" and analyzing the fault based on the alarm signal flow.
If the system is capable of automatically releasing a loopback, the automatic loopback release period
can be changed or entirely disabled on the U2000. By default, the automatic loopback release period
is five minutes.
3.5 Replacement
In this method, a component suspected to be malfunctioning is replaced with a functional
component, in order to locate and resolve the fault. The component might be a section of
pigtail, a board, a flange, or an attenuator.
Application
The replacement method is used to resolve problems on external equipment, such as optical
fibers, flanges, client equipment, and power supply equipment. It is also used to handle faults
on boards or modules at a single station. Figure 3-8 and Figure 3-9 provide two examples.
The advantage of the replacement method is that the fault can be located within a small range,
and is a relatively simple procedure for maintenance personnel to perform. This method
requires that spare components be available. In addition, the operator must exercise caution
when performing operations. For example, when a board is being inserted or removed,
careless operations that could damage board components should be avoided.
As shown in Figure 3-8, when the OTU or tributary board reports an R_LOS alarm on the
client side but the receive module of the client equipment reports no alarm, swap pigtails A
and B. If the R_LOS alarm persists, the transmit module of the client side or the receive
module of the OTU or tributary board is faulty. If the R_LOS alarm is cleared but the client
equipment reports an R_LOS alarm, pigtail A is faulty.
Before performing the test, disable the automatic laser shutdown (ALS) function of the lasers
on the OTU or tributary board and the client equipment.
DEMUX OA OA MUX
Replacement
OTU Station A (OTM) Station B (OTM)
As shown in Figure 3-9, when the OTU or tributary board reports an R_LOS alarm but the
receive module of the client equipment reports no alarm, replace the original OTU or tributary
board with a backup OTU board. Observe the alarms on the OTU board and client equipment.
If the alarm is cleared after the replacement, the original OTU board is faulty and needs to be
repaired. The following procedures can be used to narrow down the possible cause of the
OTU failure:
If it is suspected that one of the tributary board channels or some a tributary board is
faulty, change the timeslot configuration to switch services to another channel or
tributary board.
If it is suspected that a slot is faulty, change the slot configuration.
If it is suspected that a VC-4 channel is faulty, switch the time slot to another VC-4
channel.
WDM
network
Tester board: generates PRBS test signals and monitors the loopbacked PRBS test signals from the
remote board. By comparing the transmitted and received PRBS test signals, the board determines
whether the current link and equipment are normal. For example, an OTU board that supports the
PRBS function can be configured as a tester board to send PRBS signals, as shown in Figure 3-10.
Auxiliary board: connects a tester board and the network under test and transparently transmits the
PRBS test signals. On the auxiliary boards at the near end, PRBS Test Status need to be set to
Enabled, only when client-side services are other than OTN services.
When a tributary or line board is used as a tester or auxiliary board, cross-connections need to be
configured to form a service path.
The PRBS test function is targeted for use during deployment and fault location. After deployment
and fault location, users must set PRBS Test Status to Disabled.
PRBS codes vary according to the client-side service types. Therefore, to perform a client-side
PRBS test, users must ensure that the client-side service types for the tester board and auxiliary
board are the same.
WDM WDM
side side
When the NS4 and NS4M boards are used to implement the WDM-side PRBS function and lower-order
cross-connections are configured on the backplane side (that is, the received signals are ODU0, ODU1,
ODU2, ODU3, or ODUflex), the tester board and remote auxiliary board will report an OPU4_LOOMFI
alarm, which does not affect the PRBS function.
this case, use the replacement method or the loopback method to further locate the fault. This
method is applicable in the preliminary process of locating faults when spare boards are not
available. Other service channels or slots are used to resume the service temporarily.
The test frame function complies with the internal standard of Huawei.
When sending test frames during a test, you are not advised to perform any other operations.
The operation of sending test frames will affect user services. Perform this operation with caution.
Application
A network can be into divided into access networks and a transmission network. On the
access networks, boards on OptiX OTN products are interconnected with client-side devices;
on the transmission network, boards on OptiX OTN products are interconnected with each
other on the WDM side.
Figure 3-11 shows how to use test frames to assess the connectivity of network links.
Test Frame
MAC Internal Logical Internal Logical MAC
Port Port
Board A Response Frame Board B
Availability
Table 3-2 lists the boards that support the test frame function on OptiX OTN products.
Table 3-2 Boards that support the test frame function on OptiX OTN products
a: For the FE service, the board supports the test frame function only when the service is
mapping with GFP-F.
b: For the GE service, the board supports the test frame function only when the service is
mapping with GFP-T.
c: For the 10GE LAN service, the board supports the test frame function only when Port
Mapping (WDM Interface) is set to MAC Transparent Mapping (10.7 G).
When using the test frame function, take the following precautions:
For OTU boards, except for TOM boards with tributary-line mode, test frames are
independent of electrical cross-connections. The receive board can receive test frames if
the transmission link between the transmit and receive boards is connective.
When electrical cross-connections function from a tributary board to the WDM-side port
on an OTU board with the test frame, the OTU board processes GFP management frames.
Therefore, the tributary board cannot send or receive test frames.
Ethernet historical group: Queries statistical data on Ethernet ports over a historical
sampling period. The Ethernet history group supports the same performance items as the
Ethernet statistics group.
For details, refer to Performance Event List of RMON Function in the Alarms and
Performance Events Reference.
Application
This topic uses Ethernet convergence service as an example to describe how to locate data
service faults using the RMON function. As shown in Figure 3-12, there is an Ethernet service
from station A to station C. Ethernet boards 1, 2, and 3 are used on stations A, B, and D,
respectively. Figure 3-13 shows the service connections. The data service from Router 1 to
Router 2 is abnormal. In this example, the service from Router 1 to Router 2 is interrupted.
Board 2
Router 2
VCTRUNK1 PORT1
Board 1
Router 1
PORT1 VCTRUNK1
Board 3
VCTRUNK2
Router 3
PORT1
VCTRUNK1
The RMON function is enabled to remotely monitor the service between stations C and A. To
check the service performance of the Ethernet service board at the transmit end (station A)
you can query the RMON performance of the corresponding Ethernet service board at station
C. When service is interrupted or signals are degraded, diagnose the fault as follows:
1. Set the RMON performance monitoring parameters for the Ethernet port, including the
monitored objects (ports on the Ethernet board) and the monitoring period of the
performance event.
2. View the historical group performance and statistical group performance of the Ethernet
ports, and query the performance of PORT1 on Ethernet boards 1, 2, and 3 for a specific
period.
3. Analyze RMON performance and check whether the data is normal.
− When the PAUSE frame is found in the statistics report of the monitored port, use
the ping function to check whether the fault is occurring on the link between
Huawei equipment and the interconnected data communication equipment.
− If the FCS error, collision, or fragment is found in the statistics report of the
monitored port, refer to the procedure of handling the "the RMON performance
value is above the upper limit performance"event.
− If the problem is related to the maximum transmission unit (MTU), for example,
the set maximum transmission unit (MTU) is smaller than expected, change it.
4. Check whether the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is equal to
the traffic on PORT1 of Ethernet board 1.
− If the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is equal to the traffic
on PORT1 of Ethernet board 1, the fault may be located at the interconnection point
between Huawei equipment and the customer equipment instead of on Ethernet
boards 1, 2, and 3. Use the ping function to check the link between Huawei
equipment and the non-Huawei equipment.
− If the sum of the traffic on PORT1 of Ethernet boards 2 and 3 is not equal to the
traffic on PORT1 of Ethernet board 1, the fault is occurring on Ethernet board 1, 2,
or 3. Check whether the traffic on PORT1 on Ethernet board 1, 2, or 3 is equal to
the sum of the traffic on the corresponding VCTRUNK ports to locate the specific
board where the fault (congestion or signal degradation) is occurring.
5. Use the ping function to check whether the fault occurs on the link between Huawei
equipment and the interconnected data communication equipment.
For RMON configurations, refer to Configuring the RMON in the Supporting Tasks.
Application
You can configure port mirroring to perform packet monitoring, daily maintenance and
in-service commissioning. Port mirroring has the following features:
Port mirroring applies to online fault diagnosis. It mirrors the traffic from one or more
ports to another port, and then an analyzer is used for fault diagnosis.
After port mirroring is used, traffic can be monitored in real time using an analyzer.
Port mirroring implements fault diagnosis by mirroring and analyzing port data and without
affecting services. This method, which takes a long time and demands high maintenance skills,
is generally used by experienced maintenance personnel.
Mirroring Monitoring
port port
To monitor the data in different directions, port mirroring can be performed in the ingress
direction and in the egress direction.
In the ingress direction
Also in the upstream direction. The equipment duplicates the packets received from the
mirroring port to the observing port, and then transmits the packets from the observing
port to the Ethernet tester.
In the egress direction
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.
No services can be configured on an observing port. The observing port must have the same settings as
the mirroring port.
Port mirroring in the egress direction of a board cannot monitor packets initiated by the local board. To
monitor the packets initiated by the local board, perform port mirroring in the ingress direction of the
downstream board.
For LEX4, LEM24, TBE, and TEM28 boards, you can set Mirrored Upstream Port or Mirrored
DownstreamPort, but cannot set them at the same time.
For port mirroring configurations, see Configuring Port Mirroring in Supporting Tasks.
Availability
Table 3-3 lists the boards that support the port mirroring function.
Table 3-3 Boards that support the port mirroring for the OptiX OTN products
Related Information
For TBE, L4G, LEX4, LEM24, TEM28:
Uplink Listened Port For example: PORT3 Sets the uplink listened port.
Mirrored Upstream Port can be a
PORT or a VCTRUNK. As a PORT,
the port copies the packets that it
receives; as a VCTRUNK, the port
copies the packets that it transmits.
Mirrored Port sends the packets
copied from Mirrored Upstream
Port.
Downlink Listened For example: PORT5 Sets the downlink listened port.
Port Mirrored Downstream Port can be
Mirrored Upstream Port and Mirrored Downstream Port indicate the ports that copy
packets for Mirrored Port.
The transmit direction and receive direction mentioned in this section are related to the
local NE.
4 Service Interruptions
This topic describes the symptoms, impact, and possible causes of a service interruption
caused by faulty fibers, cables, and or connectors. In addition, this topic describes the required
tools, precautions, and procedures for rectifying the fault.
4.9 Service Interruptions Due to Inconsistency of Board Types or Board Settings
This topic describes the symptoms, impact, and possible causes of a service interruption
caused by inconsistent board types or board settings when the board is replaced or added. In
addition, this topic describes the required tools, precautions, and procedures for rectifying the
fault.
4.10 Service Interruptions on a Single Ethernet Port
This topic describes the symptoms, impact, and possible causes of a service interruption on a
single Ethernet port. In addition, this topic describes the required tools, precautions, and
procedures for rectifying the fault.
4.11 Service Interruptions on All Ethernet Ports
This topic describes the symptoms, impact, and possible causes of a service interruption on all
Ethernet ports of an Ethernet board. In addition, this topic describes the required tools,
precautions, and procedures for rectifying the fault.
4.12 Service Interruption Cases
This section lists cases related to Service Interruption.
Symptom
The OA (Station B) reports MUT_LOS alarm and all OTUs (Station B) report alarm R_LOS, ,
OTUk_LOF, OTUk_LOM alarm. All services are interrupted.
Networking configuration example is shown in Figure 4-1.
DEMUX MUX
OSC OSC
Station A (OTM) Station B (OTM)
Impact on System
All services are interrupted.
Possible Causes
Cause 1: The fiber is cut off.
Cause 2: The optical power is abnormal.
Cause 3: The optical amplifying board or the optical cable is faulty.
Cause 4: The demultiplexing/multiplexing board at station A or B is faulty.
Cause 5: The ring fiber adapter from the equipment to the ODF is damaged.
Procedure
Cause 1: The system provides an OSC board, the optical amplifier board reports a
MUT_LOS alarm, and the optical supervisory board reports a OSC_LOS alarm. In this
case, suspect that the optical cable is cut off.
a. Check the fiber jumper between the optical distribution frame (ODF) and WDM
equipment. If the fiber jumper is dirty, clean the fiber jumper; if it is faulty, replace
the fiber jumper.
b. If the fiber jumper is good, the optical cable is faulty. Clear the fault.
Cause 2: The system provides an OSC board, the optical amplifier board reports a
MUT_LOS alarm, and the OSC board reports no OSC_LOS alarm. It indicates that the
optical power is abnormal.
a. Check the fiber jumper between the FIU and optical amplifier board. If the fiber
jumper is dirty, clean the fiber jumper.
b. Check the optical power change of the OSC. If the received optical power of the
OSC declines, check whether the attenuation of the optical cable is excessive. If yes,
the optical cable is faulty. Clear the fault.
c. If the optical cable between station A and B is good, query the optical power on the
U2000 at station A.
If the input optical power of the optical amplifier board at station A is normal
but the output optical power is too low, replace the optical amplifier board at
station A.
If the input optical power of the optical amplifier board at station A declines
and thus results in a low output optical power, check the upstream against the
service signal flow to locate the fault.
d. If the optical cables of the faulty station B are good, check whether the input optical
power of the optical amplifier board is normal. If yes, and the output optical power
is too low, replace the board.
Cause 3: The system provides no OSC board, and the optical amplifier board reports a
MUT_LOS alarm. It indicates that the optical amplifying board or the optical cable is
faulty.
a. Refer to Testing Optical Power by Using an Optical Power Meter. Check whether
the input optical power of the optical amplifier board at station B is normal. If yes,
replace the optical amplifier board at station B.
b. Refer to Testing Optical Power by Using an Optical Power Meter. Check whether
the input and output optical power of the optical amplifier board at station A is
normal. If the input optical power is normal but the output optical power declines,
replace the optical amplifier board at station A.
c. Check the fiber jumper between the ODF and WDM equipment. If the fiber jumper
is dirty, clean it; if it is faulty, replace it.
d. If the fiber jumper is good, the optical cable is faulty. Clear the fault.
Cause 4: The MUX/DEMUX board at station A or B is faulty.
a. Query failure alarms of the MUX/DEMUX board at station A or B. If alarms are
found, replace the faulty board.
Before you replace the M40V or D40V board, record the attenuation of the internal VOA of each
channel.
Cause 5: The ring fiber adapter from the equipment to the ODF is damaged.
a. Check the ring fiber adapter between the ODF and WDM equipment. If the ring
fiber adapter is faulty, replace it.
----End
Symptom
The client-side RX interface of the OTU or tributary board reports alarms such as R_LOS,
R_LOF, OTUk_LOF at station A, and the client-side service is interrupted.
Networking configuration example is shown in Figure 4-2.
Impact on System
Single channel service is interrupted on the client side.
Possible Causes
Cause 1: The output optical power of the client equipment that is interconnected to the
OTU board is abnormal.
Cause 2: The fiber jumper between the OTU board and client equipment is faulty.
Cause 3: The optical interfaces of the OTU board are dirty.
Cause 4: The OTU board is faulty.
Cause 5: The client equipment is faulty.
Cause 6: The service type, wavelength and mode that configured on the board 1 are
different from those of the client equipment, and therefore services are interrupted.
Procedure
Cause 1: The output optical power of the client equipment that is interconnected to the
OTU board is abnormal.
a. Refer to Testing Optical Power by Using an Optical Power Meter. Check whether
the output optical power of the client equipment is normal. If not, remove the fault
of the client equipment.
Cause 2: The fiber jumper between the OTU board and client equipment is faulty.
a. If the output optical power of the client equipment is normal, check whether the
input optical power of the OTU board is normal. If not, clean the fiber jumper or
replace the fiber jumper.
Cause 3: The optical interfaces of the OTU board are dirty.
a. If the optical interfaces of the OTU board are dirty, blow them with compressed gas
to clean them.
Cause 4: The OTU board is faulty.
a. If the input optical power of the OTU board is normal, but the system reports an
alarm indicating that the optical power is abnormal or an alarm related to the optical
module, replace the client-side optical module on the OTU board.
b. If the fault still exists, replace the board.
Cause 5: The client equipment is faulty.
a. Remove the fault of the client equipment.
Cause 6: The service type, wavelength and mode that configured on the board 1 are
different from those of the client equipment, and therefore services are interrupted.
a. Query and set the client service type, wavelength and mode of the board 1. Make
sure that the service type, wavelength and mode of the board 1 board are the same
as those of the client equipment.
For GE service, query and set the auto-negotiation modes of the boards. Make sure that the
auto-negotiation modes are the same.
----End
Symptom
The WDM-side IN interface of the OTU, or tributary board and line board reports alarms such
as R_LOS, R_LOF, R_OOF and OTUk_LOF, and one channel of services is interrupted.
Networking configuration example is shown in Figure 4-3.
Client Client
equipment OTU MUX OA OA DEMUX OTU equipment
DEMUX OA OA MUX
Station A Station B
Signal Flow
Impact on System
One channel of the WDM-side services of an NE is interrupted.
Possible Causes
Cause 1: The OTU, or tributary board and line board in the opposite station (station A) is
faulty or the fiber jumper in the opposite station between the OTU board and MUX is
dirty.
Cause 2: The fiber jumper between the DEMUX and OTU, or tributary board and line
board is dirty or faulty.
Cause 3: The loopback testing on the OTU, or tributary board and line board in the local
station and the optical power of OTU, or tributary board and line board is normal. In this
case, the FEC mode of the OTU, or tributary board and line board in the local station and
the opposite station might be inconsistent.
Cause 4: The interconnection services type, wavelength and mode do not match.
Cause 5: The OTU, or tributary board and line board at the local station (station B) is
faulty.
Cause 6: New service wavelengths are added to the network and the new service
wavelengths conflict with existing service wavelengths.
Procedure
Cause 1: The OTU, or tributary board and line board in the opposite station (station A) is
faulty or the fiber jumper in the opposite station between the OTU, or tributary board and
line board and MUX is dirty.
a. Check whether the input optical power on the client side and the output optical
power on the WDM side of the OTU, or tributary board and line board in the
opposite station are normal. If either optical power is abnormal, replace the
corresponding board.
b. Check the input optical power of the optical amplifier board in the opposite station
(station A) to determine whether the fiber jumper between the OTU, or tributary
board and line board and MUX is dirty or faulty. If the fiber jumper is dirty, clean
the fiber jumper; if it is faulty, replace the fiber jumper.
Cause 2: The fiber jumper between the DEMUX and OTU, or tributary board and line
board is dirty or faulty.
a. Check whether the input optical power of the OTU, or tributary board and line
board is normal. If not, clean or replace the fiber jumper between the DEMUX and
OTU, or tributary board and line board.
Cause 3: The loopback testing on the OTU, or tributary board and line board in the local
station and the optical power of OTU, or tributary board and line board is normal. In this
case, the FEC mode of the OTU, or tributary board and line board in the local station and
the opposite station might be inconsistent.
a. Refer to Querying the FEC Mode to query the FEC states of the two interconnected
boards on the U2000. If the two modes differ, enable the FEC to ensure mode
matching.
Cause 4: The interconnection services type, wavelength and mode do not match.
a. Check and ensure that the interconnection services type, wavelength and mode
match.
If the services on the WDM side do not match, there is only LOOP_ALM alarm reported in the loopback
operation, but there will be OTUk_LOF or R_LOF if the loopback operation is canceled.
Cause 5: The OTU, or tributary board and line board at station B is faulty.
a. Check whether the input optical power of the OTU, or tributary board and line
board is normal. If yes, the OTU, or tributary board and line board in the local
station is faulty. Replace the pluggable optical module or Replace the board.
Cause 6: New service wavelengths are added to the network and the new service
wavelengths conflict with existing service wavelengths.
a. Check whether new services are added to the network. If new services are added,
check whether the new service wavelengths conflict with the existing service
wavelengths. Then, change the new service wavelengths so that they do not conflict
with the existing service wavelengths.
----End
Symptom
Human misoperation results in service interruptions.
Impact on System
The services carried on the OTU, or tributary board and line board are interrupted.
Possible Causes
Cause 1: When you disable the FEC function of an OTU, or tributary board and line
board, the equipment does not report any alarm, whereas the OTN services borne by the
equipment are interrupted.
Cause 2: The FEC mode of any OTU, or tributary board and line board is manually
changed, causing the services to be interrupted.
Cause 3: Hardware loopback or software loopback is set manually.
Procedure
Cause 1: When you disable the FEC function of an OTU, or tributary board and line
board, the equipment will not report any alarm, but the OTN services are interrupted.
a. Querying the FEC Mode, the equipment does not report any alarm when you enable
or disable the FEC function of the OTU, or tributary board and line board. The
engineer must pay attention to this during maintenance. Make sure to enable the
FEC function in application.
Cause 2: The FEC mode of any OTU, or tributary board and line board is manually
changed, causing the services to be interrupted.
a. Check whether the FEC modes of the two interconnected boards are different.
Cause 3: Hardware loopback or software loopback is set manually.
a. Check whether hardware loopback is set. If yes, release the hardware loopback.
b. On the U2000, check whether software loopback is set on the service channel
manually. If yes, release the software loopback.
----End
Symptom
A large number of boards on the device of a certain site are reset simultaneously and the
services are interrupted.
Impact on System
Power supply failures may cause service interruptions.
Possible Causes
Cause 1: The power supply of the board fails.
Procedure
Cause 1: The power supply of the board is faulty. As a result, services are interrupted.
a. Query the current alarms on the U2000.
If... Then...
If... Then...
The power cable connectors are not Fasten the power cable connectors by using
connected properly a screwdriver or replace the power cable
connectors, and proceed to the next step.
Power cable connectors are connected Check whether the fault is due to other
properly and the contact is good causes.
b. Check whether services recover. If the services do not recover, check whether the
fault is due to other causes.
Cause 3: The external power supply is off or the power fluctuates abnormally. As a result,
services are interrupted.
a. Switch off the DC PDU. Connect the positive pole of the multimeter to the NEG(-)
terminal of the DC PDU and the negative pole of the multimeter to the RTN(+)
terminal. Measure the voltage between the RTN(+) and NEG(-) terminals and check
whether the voltage meets the requirement. For details about voltage requirements,
refer to the Hardware Description.
If... Then...
The voltage between the RTN and -48V DC Proceed to the next step.
terminals does not meet the requirements
The voltage between the RTN and -48V DC Check whether the fault is due to other
terminals meets the requirements causes.
b. Contact the power supply engineers to rectify the fault of the external power supply.
Cause 4: The power board of the device is faulty. As a result, services are interrupted.
a. Replace the power board of the device.
b. Check whether services recover. If the services do not recover, check whether the
fault is due to other causes.
Cause 5: The DC PDU is faulty. Abnormality of the power supply system causes the
board reset.
a. Replace the DC PDU.
b. Check whether services recover. If the services do not recover, check whether the
fault is due to other causes.
----End
Symptom
A large number of boards on the device of a certain site are reset simultaneously and the
services are interrupted.
Impact on System
The grounding fault causes service interruptions.
Possible Causes
Cause 1: The PGND and BGND grounding is poor, and the grounding resistance is
higher than 10 ohms or the potential difference between BGND and PGND is higher
than 0.5 V.
Cause 2: The PGND and BGND share the same grounding with the AC neutral wire.
Cause 3: The PGND of the interconnected device is not joint grounding.
PGND means protection ground and BGND means power ground (also called working ground).
Use the multimeter to check whether the grounding resistance of the BGND and PGND meet the
requirements. Or, you can use a proper meter to check whether the waveform of the interconnected
signal is distorted.
Procedure
Cause 1-3: The device grounding is improper. As a result, services are interrupted.
a. Check whether the ground bar in the telecommunications room is properly
grounded. If the grounding is proper, proceed to the next step; otherwise, ground
the ground bar properly.
b. Check whether the contact between the cabinet of the transmission de vice and the
ground bar in the telecommunications room is good. If the contact is good, proceed
to the next step; otherwise, ground the cabinet of the transmission device properly.
c. Check whether the contact between the cabinet and the front door/side cover of the
cabinet is good. If the contact is good, proceed to the next step; otherwise, ground
the front door/side cover of the cabinet properly.
d. Check whether the contact between the subrack and the cabinet is good. If the
contact is good, proceed to the next step; otherwise, ground the subrack properly.
e. Check whether the DDF and ODF are properly grounded. If the DDF and ODF are
properly grounded, proceed to the next step; otherwise, ground the DDF and ODF
properly.
f. Check whether the NMS device and various power consumption devices are
properly grounded. If these devices are properly grounded, proceed to the next step;
otherwise, ground these devices properly.
g. Check whether the grounding of the interconnection devices is joint grounding.
----End
Symptom
A large number of boards on the device of a certain site are reset simultaneously and the
services are interrupted.
Impact on System
Unfavorable environmental conditions can cause a service interruption.
Possible Causes
Cause 1: The temperature and humidity of the environment have caused equipment
damage.
Cause 2: A strong external interference source exists.
Cause 3: Rodent animals damage equipment.
Procedure
Cause 1: The temperature and humidity of the environment have caused equipment
damage. As a result, services are interrupted.
a. Check whether the temperature and humidity of the environment meet the
requirements.
The detailed requirements are as follows:
Temperature: 0°C to 45 °C (32°F to 113°F)
Relative humidity: 10% to 90%
If... Then...
The temperature and humidity of the Check and adjust the air conditioner in the
environment do not meet the requirements telecommunications room to make sure that
the temperature and humidity of the
telecommunications room are in the proper
range. Check whether services recover. If
the services do not recover, check whether
the fault is due to other causes.
If... Then...
The NE does not report the temperature Check whether the fault is due to other
threshold-crossing alarms TEMP_OVER causes.
If... Then...
If... Then...
d. Check whether a hand-held mobile communication device is in use near the device.
If... Then...
If... Then...
No hand-held mobile communication device Check whether the fault is due to other
is in use near the device causes.
There are rodent animals or their excrement Remove the rodent animals and their
inside the cabinet excrement, replace any broken cable, and
install a rodent-proof mesh in the cabinet.
Check whether services recover. If the
services do not recover, check whether the
fault is due to other causes.
There are no rodent animals or their Check whether the fault is due to other
excrement inside the cabinet causes.
----End
Related Information
Table 4-1 lists the requirement for the electromagnetic interference.
Equipment rooms or equipment should be kept far away from strong electromagnetic
interference sources. If this requirement cannot be met, take additional radiation protection
measures. For example, place the equipment in a radiation-resistant network cabinet or a
sealed cabinet.
Symptom
Services of a certain site are interrupted.
Impact on System
Faulty fibers, cables, or connectors can cause a service interruption.
Possible Causes
Cause 1: The fibers are broken.
Cause 2: Attenuation of the fibers and the fiber adapter is too high.
Cause 3: The cable connectors are connected improperly or incorrectly, or are not
connected.
Precautions
Avoid direct eye exposure to laser beams launched from the optical interface and the fiber
jumper connector.
When removing fibers from the optical interface, make sure that the proper optical fiber is
removed; otherwise, it may cause service interruption to a larger area.
Procedure
Query alarms on the U2000 and clear the alarms according to the reported information.
a. Check the current alarms on the U2000.
If... Then...
The NE does not report the R_LOS, R_LOF Check whether the fault is due to other
or IN_PWR_LOW alarm causes.
position of the broken fibers. For how to use the OTDR meter, see the Operation
Guide of the OTDR meter.
If... Then...
The fibers are detected as broken Replace the fibers. Check whether services
recover. If the services do not recover,
check whether the fault is due to other
causes.
The fibers are not detected as broken Check whether the fault is due to other
causes.
Cause 2: Attenuation of the fibers and the fiber adapter is too high. As a result, services
are interrupted.
a. Measure the transmit optical power of the board in the upstream station and the
receive optical power of the board in downstream station.
If... Then...
The receive optical power of the board in Proceed to the next substep.
downstream station is abnormal
b. The difference between the transmit optical power of the board in the upstream
station and the receive optical power of the board in downstream station is the
actual optical power attenuation of the line. Compare the actual optical power
attenuation of the line with the designed value. If the actual attenuation is higher
than the designed value, locate and rectify the fault as follows.
Check whether the bending radius of the fibers is equal to or larger than Table
4-2. If the bending radius of the fibers is less than Table 4-2, re-route the fibers
and make sure that the bending radius is equal to or larger than Table 4-2.
Check whether there are many fiber connectors on the line and whether the
connectors are connected properly. If the connectors are connected improperly,
fasten the connectors with the optical modules.
Check whether there are aerial fibers on the line, which is easy to be affected
by the weather. If there are aerial fibers on the line, provide necessary
protection to the aerial fibers.
Check whether the fiber type and attenuation factor of the line are consistent
with the designed ones. If the fiber type and attenuation factor of the line are
inconsistent with the designed ones, replace the fiber.
Check whether the fiber connectors of the line are dirty. For details, see the
information about checking the fiber connectors. Clean the fiber connectors.
c. Check whether services recover. If the services do not recover, check whether the
fault is due to other causes.
Cause 3: The connection between the cable and the connector is loose, the cable
connectors are connected incorrectly, or the cable connectors are not connected. As a
result, services are interrupted.
If... Then...
The connection between the cable and the Connect the cables properly. Check whether
connector is loose services recover. If the services do not
recover, proceed to the next substep.
The connection of the cable and the Proceed to the next substep.
connectors is good
b. Check whether the connections of the cables to the board in the downstream station
are correct.
If... Then...
Connections of the cables to the board in the Connect the cables correctly. Check
downstream station are incorrect whether services recover. If the services do
not recover, check whether the fault is due
to other causes.
Connections of the cables to the board in the Check whether the fault is due to other
downstream station are correct causes.
----End
Related Information
G.652D 30 mm
Multi-mode fiber (A1B) 30 mm
G.657A2 10 mm
G.657B3 8 mm
Note: When fibers are connected to CRPC boards, the bending radius of the fibers must be
greater than or equal to 50 mm to ensure expected transmission performance.
addition, this topic describes the required tools, precautions, and procedures for rectifying the
fault.
Symptom
During a capacity expansion at a site, after a board is replaced or added, services are
interrupted.
Impact on System
Inconsistency of board types causes service interruption.
Possible Causes
Cause 1: The board types are inconsistent.
Procedure
Cause 1: The board types are inconsistent. As a result, services are interrupted.
a. Check the current alarms on the U2000.
If... Then...
The NE does not report the Check whether the fault is due to other
WRG_BD_TYPE alarm causes.
Related Information
For any capacity expansion, the type of the board to be replaced or added must be consistent
with that of the original board. Especially, when replacing or adding the cross-connect boards
with the active and standby relation, make sure that the types of the active and standby boards
are the same.
A list of compatible boards is available. For details, consult technical support engineers of Huawei.
Symptom
The service on a single Ethernet port of an Ethernet board is interrupted.
Impact on System
The service on a single Ethernet port is interrupted.
Possible Causes
Cause 1: The configuration is incorrect.
Cause 2: The fibers, network cables, or optical/electrical modules are faulty.
Cause 3: The optical module does not match the optical port.
Cause 4: The board port is faulty.
Procedure
Cause 1: The configuration is incorrect. As a result, services are interrupted.
a. On the U2000, query the configuration on the board.
If... Then...
b. On the U2000, query whether the board port is configured with loopback.
If... Then...
The board port is configured with a Release the loopback. Check whether
loopback services recover. If the service does not
recover, proceed to the next step.
The board port is not configured with a Proceed to the next step.
loopback
If... Then...
The attributes of the port are incorrect Set the attributes of the port again, including
the tag attributes and whether to enable the
port. Check whether services recover. If the
services do not recover, proceed to the next
step.
If... Then...
The attributes of the port are correct Proceed to the next step.
d. On the U2000, check whether the working mode of the local port is consistent with
the working mode of the opposite port.
If... Then...
The working mode of the local port is Set the local port to the same working mode
inconsistent with that of the opposite port as the opposite port. Check whether services
recover. If the services do not recover,
check whether the fault is due to other
causes.
The working mode of the local port is Check whether the fault is due to other
consistent with that of the opposite port causes.
Cause 2: The fibers, network cables, or optical/electrical modules are faulty. As a result,
services are interrupted.
a. Query the current alarms on the U2000.
If... Then...
The NE reports the LINK_ERR alarms Handle the LINK_ERR alarms. Check
whether services recover. If the services do
not recover, check whether the fault is due
to other causes.
The NE does not report the LINK_ERR Check whether the fault is due to other
alarms causes.
Cause 3: The optical module does not match the optical port. As a result, services are
interrupted.
a. Query the current alarms on the U2000.
If... Then...
The NE does not report the Check whether the fault is due to other
LASER_MODULE_MISMATCH alarm causes.
that indicates the mismatch of the optical
module
If... Then...
The Ethernet port receives data, but does Replace the board. Check whether services
not transmit data recover. If the services do not recover,
check whether the fault is due to other
causes.
The Ethernet port receives and also Check whether the fault is due to other
transmits data causes.
----End
Symptom
Services on all Ethernet ports of an Ethernet board are interrupted.
Impact on System
Services on all Ethernet ports are interrupted.
Possible Causes
Cause 1: The board is offline.
Cause 2: The configuration is incorrect.
Cause 3: The ports of the board are faulty.
Procedure
Cause 1: The board is offline. As a result, services are interrupted.
a. Query the current alarms on the U2000.
If... Then...
The NE reports the BD_STATUS alarm Handle the BD_STATUS alarm. Check
whether services recover. If the services do
not recover, check whether the fault is due
to other causes.
If... Then...
The NE does not report the BD_STATUS Check whether the fault is due to other
alarm causes.
b. On the U2000, query whether the board port is configured with loopback.
If... Then...
The board port is configured with a Release the loopback. Check whether
loopback services recover. If the services do not
recover, proceed to the next step.
The board port is not configured with a Proceed to the next substep.
loopback
c. On the U2000, query the tag attributes of the port on the board.
If... Then...
The attributes of the port are incorrect Re-configure the attributes of the port, such
as the tag attributes and whether to enable
the port. Check whether services recover. If
the services do not recover, proceed to the
next substep.
The attributes of the port are correct Proceed to the next substep.
d. On the U2000, check whether the working mode of the local port is consistent with
that of the opposite port.
If... Then...
The working mode of the local port is Set the local port to the same working mode
inconsistent with that of the opposite port as the opposite port. Check whether services
recover. If the services do not recover,
check whether the fault is due to other
causes.
The working mode of the local port is Check whether the fault is due to other
If... Then...
consistent with that of the opposite port causes.
Cause 3: The ports of the board are faulty. As a result, services are interrupted.
a. On the U2000, query the data of the Ethernet ports by using the remote monitoring
(RMON) function.
If... Then...
The Ethernet ports receive data, but do not Replace the board. Check whether services
transmit data recover. If the services do not recover,
check whether the fault is due to other
causes.
The Ethernet ports receive and transmit data Check whether the fault is due to other
causes.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A1 The OTU_LOF Alarm is Reporting on the OTU at the Downstream Station
MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS
Alarm on the Board
MC-A38 The Service Is Interrupted After the Protection Is Triggered
MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
MC-A69 Shutdown of the RPC Laser Interrupts SDH-Layer Services in a DWDM
Network
MC-A117 Analysis and Handling of the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Reported by the LBE
MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
MC-A147 Services Are Unavailable Due to Inappropriate FEC Configuration on the 40G
Regeneration Boards, The System Reports An OTU_LOF Alarm
MC-A188 The LDGF2 Board on the OptiX OSN 1800 Reports an OTU1_LOF Alarm
MC-A200 Fiber Faults Result in Service Interruption, The TDX Board Reports
ODU1_PM_SSF Alarms
MC-A206 Service Provisioning Fails on an LHP Network, The OTU2_LOF Alarm Is
Reported
MC-A207 Inaccurate System Commissioning Causes Poor System Performance
MC-A208 40G Service Provisioning Fails On a Network, The OTU_LOF And
DCM_INSUFF Alarms Are Reported
MC-A211 OTUk_LOF Alarm Is Reported Due to Mismatched Mapping Modes of the
LSX Boards in the Case of 10GE LAN Services
MC-A215 Incorrect Configuration of an Added Wavelength During Expansion Results in
Service Interruption of Another Normal Wavelength on an OTU Board, The
Corresponding OTU Board Reports OTU2_LOF Alarm
MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
MC-A227 Services Cannot Be Provisioned and The LWX2 Boards Report The R_LOC
Alarm Due to Incorrect Service Rates on LWX2 Board of OptiX OSN 1800
MC-A234 Services Are Interrupted After an Upgrade due to Improper Database
Restoration Operations on the OptiX OSN 6800
MC-A248 Network Services Are Interrupted After the Equipment Restarts Because the
Wavelengths Conflict After the Wavelength Configurations Are Modified
MC-A280 Service Interruption Occurs Because of a Channel Rate Mismatch Between
TN54NS3 Boards on the OptiX OSN 8800 Network
MC-A281 Service Interruption Occurs Because of the Data Board LAG Configuration
on the OptiX OSN 6800 Equipment Mismatches the LAG Configuration on the Router
MC-A294 Service Interruption Occurs Because of Incorrect Physical Fiber Connections
on OptiX OSN 6800 Equipment
MC-A298 After Fiber Splicing Is Completed for a Fiber Cut, Alarm RL_CRITICAL_HI
or RL_CRITICAL_LOW Is Reported upon the Enabling of Raman Boards and the Link
Cannot Be Restored in an Office
MC-A299 After a Regeneration Site Is Added in an Office, Board Performance Is
Improved, but Downstream Services Are Interrupted
MC-A300 Service Interruption Occurs at a Customer Office in Country A Because of
Incorrect Configuration of Cascading SNCP Protection
MC-A312 An ASON Service Is Interrupted Because OPA Fails
MC-A313 An ASON Service Is Interrupted Because Protection Switching Fails After a
Second Fiber Cut
Symptom
The OTU, or tributary board and line boards at station B may report the R_LOS, R_LOF,
OTUk_LOF, OTUk_LOM alarms on WDM side, and the alarms clear in a short time. All
services at station B are transiently interrupted.
Figure 5-1 shows an example of the network configuration in this case.
Figure 5-1 Example of the network configuration where all services are transiently interrupted
Client Client
DEMUX MUX
OSC OSC
Station A (OTM) Station B (OTM)
Impact on System
Services are interrupted for milliseconds at station B.
Possible Causes
Cause 1: The optical cable or fiber jumper in the multiplexing part is faulty.
Cause 2: The equipment temperature is too high.
Cause 3: The optical amplifier board is faulty.
Cause 4: The FIU board is faulty.
Procedure
Cause 1: The optical cable or fiber jumper in the multiplexing part is faulty.
a. Check the fiber jumper in the multiplexing part. If it is loose, secure it; if it is dirty,
clean it; if it is faulty, replace the fiber jumper.
The fiber jumpers in the multiplexing part are the fiber jumpers between:
The equipment and ODF
The OA and FIU
The OA and MUX/DEMUX
ODFs
TDC and RDC of the OAU
b. Clear the fault of the optical cable.
If the fault is located in a section of optical line, check:
Whether there are multiple fiber connectors in this section of optical line and
whether they are in good connection
Whether there are aerial optical cables, which are liable to be damaged by the
weather
Whether the type and attenuation coefficient of the optical fiber in this section
is correct
The optical line fault is the usual cause which results in a transient interruption. Usually, the transient
interruption caused by a line fault affects all channels (including the OSC). The optical line fault can be
caused by a fiber cut or excessive attenuation.
However, the fiber cut cannot cause a transient interruption. When you have a line fault, find the cause
of excessive attenuation of the fiber and then remove the fault.
Cause 2: The equipment temperature is too high.
a. Check whether the performance data of NE contain alarms such as TEMP_OVER.
If yes, the operating temperature of the board is too high. Check the environmental
conditions of the telecommunications room. Clean the air filter.
b. Check whether the fan tray assembly works normally. If not, replace the fan tray
assembly.
Cause 3: The optical power fluctuates by the fault of the optical amplifier board.
a. In the case of the DWDM application, on the U2000, query the historical
performance data of optical power of OA board. Check the input and output optical
power of the optical amplifier board. If the input optical power is normal but the
output optical power does not reach the standard output optical power, replace the
board.
Cause 4: The FIU board is faulty.
a. In the case of the DWDM application, replace the FIU board. If the fault clears,
determine that the FIU board is faulty.
----End
Symptom
The IN interface on the WDM side of OTU1 at station C reports the R_LOS, R_LOF, R_OOF,
IN_PWR_LOW, and OTUk_LOF alarms, and the alarms clear in a short time. The services in
a single channel of station C are transiently interrupted.
Figure 5-2 shows an example of the network configuration in this case.
Figure 5-2 Example of the network configuration where the services in a single channel are
transiently interrupted
MUX MUX
OTU1 DEMUX DEMUX OTU1
OA
DEMUX OA
OTU2 OTU2
Client Client
Station A OTM Station C OTM
Impact on System
Services are interrupted for milliseconds on one channel at station C.
Possible Causes
Cause 1: The services are configured with protection. When a fault in the working
channel triggers protection switching, the switching times out or occurs frequently.
Cause 2: The fiber jumper between the MUX/DEMUX and OTU1 is faulty.
Cause 3: The OTU1 board at station A is faulty.
Cause 4: The equipment temperature is extremely high.
Procedure
Cause 1: The services are configured with protection. When a fault in the working
channel triggers protection switching, the switching times out or occurs frequently.
a. On the U2000, query the historical data of alarms. Check whether the protection
switching alarm exists (the equipment reports a PS alarm when protection switching
occurs). Handle the related protection switching alarm.
Cause 2: The fiber jumper between the MUX/DEMUX and OTU1 is faulty.
a. Check the fiber jumper. If it is loose, secure it; if it is dirty, clean it; if it is faulty,
replace the fiber jumper.
Cause 3: The OTU1 board at station A is faulty.
a. Query on the U2000 the historical performance data of the output optical power of
OTU1 at station A. If the data contains a performance event showing a drastic
decline of output optical power of OTU1 at station A, then OTU1 at station A is
faulty. Replace OTU1 at station A.
Cause 4: The equipment temperature is extremely high. When the equipment
temperature is extremely high, the wavelength of the single channel deviates and the
services are interrupted.
a. On the U2000, query the historical data of alarms. If alarms such as TEMP_OVER
exists, determine that the operating temperature of the board is extremely high.
Check and lower the temperature in the telecommunications room. Clean the air
filter.
b. Check whether the fan tray assembly works normally. If not, replace the fan tray
assembly.
----End
Symptom
Symptom 1: The LINK_ERR alarm jitter occurs on a single Ethernet port of an Ethernet
board that works in auto-negotiation mode, and services recover after a period of
interruption.
Symptom 2: The ETH_CFM_LOC alarm jitter occurs on a single Ethernet port of an
Ethernet board, and services recover after a period of interruption.
Impact on System
Services on the Ethernet port are transiently interrupted.
Possible Causes
For symptom 1, the possible causes are as follows:
− Cause 1: Optical fibers in the transmit direction of the local Ethernet port are faulty
and recover within a short period.
− Cause 2: The port interconnected to the Ethernet port switches between the
auto-negotiation mode and the fixed mode continuously.
− Cause 3: The board is faulty.
For symptom 2, the possible causes are as follows:
− Cause 1: Optical fibers in the receive direction of the Ethernet port are faulty and
recover within a short period.
− Cause 2: The port interconnected to the Ethernet port is disabled or enabled within a
short period.
− Cause 3: The board is faulty.
Procedure
For symptom 1: The LINK_ERR alarm jitter occurs on a single Ethernet port of an
Ethernet board that works in auto-negotiation mode, and services recover after a period
of interruption.
a. Cause 1: Optical fibers in the transmit direction of thelocal Ethernet port are faulty
and recover within a short period.
i. Query the historical alarms of the port of the interconnected device on the
U2000.
If... Then...
The ETH_CFM_LOC alarm exists Indicates that the fibers in the transmit
direction of the local Ethernet port have
been broken. As a result, the negotiation
fails at the local end and the LINK_ERR
alarm is reported accordingly. In this case,
services are transiently interrupted. Check
whether services recover. If the services do
not recover, proceed to the next step.
The ETH_CFM_LOC alarm does not exist Proceed to the next step.
ii. Check whether the fibers or the line boards are removed and reinserted
manually. Query the historical alarms of the interconnected port of the device
on the U2000.
If... Then...
The fibers or the line boards are removed Make sure that the fibers or the line boards
and reinserted manually is not removed and reinserted manually.
Check whether services recover. If the
services do not recover, proceed to the next
step.
The fibers or the line boards are not Proceed to the next step.
removed and reinserted manually
iii. According to the transmission distance, check whether the optical module
types are correct.
If... Then...
The optical module type is incorrect Select a correct optical module and replace
the optical module on the device with the
correct one. Check whether services
recover. If the services do not recover,
proceed to the next step.
The optical module type is correct Proceed to the next step.
The fibers are faulty Replace the faulty fibers. Check whether
services recover. If the services do not
If... Then...
recover, proceed to the next step.
The fibers are normal Check whether the fault is due to other
causes.
b. Cause 2: The port interconnected to the Ethernet port switches between the
auto-negotiation mode and the fixed mode continuously.
i. Query the operation log on the U2000.
If... Then...
The working mode of the interconnected Indicates that the service transient
port is changed manually interruption is caused by the mismatch of
the working mode. Make sure that the
operation mode of the interconnected port is
not changed manually. Check whether
services recover. If the services do not
recover, check whether the fault is due to
other causes.
The working mode of the interconnected Check whether the fault is due to other
port is not changed manually causes.
If... Then...
The ETH_CFM_LOC alarm exists Indicates that the fibers in the receive
direction of the local Ethernet port have
been broken. Proceed to the next step.
The ETH_CFM_LOC alarm does not exist Check whether the fault is due to other
causes.
ii. Check whether the fibers or the line boards are removed and reinserted
manually. Query the historical alarms of the interconnected port of the device
on the U2000.
If... Then...
If... Then...
The fibers or the line boards are removed Make sure that the fibers or the line boards
and reinserted manually is not removed and reinserted manually.
Check whether services recover. If the
services do not recover, proceed to the next
step.
The fibers or the line boards are not Proceed to the next step.
removed and reinserted manually
iii. According to the transmission distance, check whether the optical module
types are correct.
If... Then...
The optical module type is incorrect Select a correct optical module and replace
the optical module on the device with the
correct one. Check whether services
recover. If the services do not recover,
proceed to the next step.
If... Then...
The fibers are faulty Replace the faulty fibers. Check whether
services recover. If the services do not
recover, proceed to the next step.
The fibers are normal Check whether the fault is due to other
causes.
The port interconnected to the Ethernet port Make sure that these ports are not enabled
is disable or enabled manually or disabled manually. Check whether
services recover. If the services do not
recover, check whether the fault is due to
other causes.
The port interconnected to the Ethernet port Check whether the fault is due to other
is not disable or enabled manually causes.
Related Information
None
Symptom
Symptom 1: The Rapid Spanning Tree Protocol (RSTP) is enabled, but the status of the
protocol jitters and the services are transiently interrupted.
Symptom 2: The Link Aggregation Control Protocol (LACP) is enabled, but the status of
the protocol jitters and the services are transiently interrupted.
Impact on System
The services are transiently interrupted.
Possible Causes
For symptom 1, the possible causes are as follows:
− Cause 1: The network topology is changed and the RSTP protocol reconstructs the
network topology.
− Cause 2: The RSTP protocol is reset.
− Cause 3: The RSTP protocol packets are lost. As a result, the status of the protocol
jitters.
For symptom 2, the possible causes are as follows:
− Cause 1: The NE reports the LAG_PORT_FAIL alarm and the services are
transiently interrupted.
− Cause 2: The LACP protocol is reset and the services are transiently interrupted.
Procedure
For symptom 1: The RSTP protocol has been enabled, but the state of the protocol jitters
and the services are transiently interrupted.
a. Cause 1: The network topology is changed and the RSTP protocol reconstructs the
network topology.
i. Check whether the network topology is changed manually.
If... Then...
The network topology is changed manually The transient service interruption is caused
by the reconstruction of the network
topology implemented by the RSTP
protocol.
If... Then...
The service interruption alarms are reported, After the link is faulty, the services are
such as the ETH_CFM_LOC and transiently interrupted due to the
LINK_ERRLINK-ERR alarms of the reconstruction of the network topology by
Ethernet port and the UNEQ and TU_LOP the RSTP protocol.
alarms on the SDH side
The service interruption alarms are not Check whether the fault is due to other
reported, such as the ETH_CFM_LOC and causes.
LINK_ERRLINK-ERR alarms of the
Ethernet port and the UNEQ and TU_LOP
alarms on the SDH side
If... Then...
Before the services are interrupted, the The service interruption is caused by the
RSTP protocol has been reset or the board reset of the RSTP protocol.
has been warm reset manually
Before the services are interrupted, the Check whether the fault is due to other
RSTP protocol has not been reset or the causes.
board has been warm reset manually
After the board is warm reset, the RSTP protocol is restarted automatically.
c. Cause 3: The RSTP protocol packets are lost. As a result, the status of the protocol
jitters.
i. Check the traffic flow of the services, and then check whether the QoS
function is enabled according to the service configuration.
If... Then...
If... Then...
The QoS function is enabled and the The state jitter of the RSTP protocol is
bandwidth is insufficient caused by the loss of the RSTP protocol
packets.
The QoS is not enabled Check whether the fault is due to other
causes.
Generally, the priority of the protocol packets is higher than the priority of the service packets. If the
QoS function is enabled, the priority of the service packets may be higher than that of the protocol
packets. In this case, the protocol packets may be discarded when the bandwidth is insufficient.
For symptom 2: The LACP protocol has been enabled, but the state of the protocol jitters
and the services are transiently interrupted.
a. Cause 1: The NE reports the LAG_PORT_FAIL alarm and the services are
transiently interrupted.
i. Check the current alarms on the U2000.
If... Then...
b. Cause 2: The LACP protocol is reset and the services are transiently interrupted.
i. Query the operation log on the U2000.
If... Then...
Before the services are interrupted, the The service interruption is caused by the
LACP protocol has been reset or the board reset of the LACP protocol.
has been warm reset manually
Before the services are interrupted, the Check whether the fault is due to other
LACP protocol has not been reset or the causes.
board has been warm reset manually
After the board is warm reset, the LACP protocol is restarted automatically.
----End
Related Information
None
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
ALM_DATA_RLOS Alarms Transiently
MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
Symptom
The optical power of all OTUs in the local station sharply declines, and the optical
signal-to-noise ratio (OSNR) is lower than the OSNR tolerance of the OTU.
Impact on System
A large number of bit errors occur in the services and the services are transiently interrupted
frequently.
Possible Causes
Cause 1: Any fiber jumper in the multiplexing part, or an optica l cable degrades or is
physically damaged.
Cause 2: The gain of the optical amplifier board in the upstream station or downstream
station declines.
Procedure
Cause 1: Any fiber jumper in the multiplexing part, or an optical cable degrades or is
physically damaged. Hence, the attenuation of the fiber increases and the received
optical power declines. As a result, the OSNR decreases.
a. Refer to Checking Fiber Jumpers by Using an Optical Power Meter. Check whether
the fiber jumper in the multiplexing part is faulty. If yes, replace the fiber jumper.
b. Remove the fault of the optical cable.
The fiber jumpers in the multiplexing part are the fiber jumpers between:
The equipment and ODF
The OA and FIU
The OA and MUX/DEMUX
ODFs
TDC and RDC of the OAU
Cause 2: The gain of the optical amplifier board in the upstream station or downstream
station declines.
a. Check whether the gain of the optical amplifier board is abnormal. If yes, replace
the board.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets
Close to the Threshold
MC-A15 The Downstream Optical Amplifier Board Does Not Report MUT_LOS
MC-A19 Use Power Monitoring To Process Problems on IN_PWR_LOW Alarm
MC-A24 Low Optical Power on the Client Side of the OTU Board Leads to R_LOS
Alarm on the Board
MC-A35 LWM Output Optical Power Is Unstable upon Forced Light Generation
MC-A36 The OTU in the OptiX BWS 1600G Reports IN_PWR_LOW Alarm
MC-A43 Too High Insertion Loss Between TDC and RDC of the E3OAUC01C
MC-A45 During the deployment of Raman, the OPU board reports MUT_LOS
MC-A52 Faults of End Face of the Fiber Connector Cannot Be Identified
MC-A54 After the Lasers of the Raman Amplifier Are Disabled, the Optical Power Is
Abnormal
MC-A62 The Minimum Optical Power of the SC2 Is Detected As -35 dBm
MC-A66 The Received Optical Power of Downstream Stations Is not Flat and Some
Wavelengths Report the IN_PWR_LOW Alarm
MC-A68 OTU Boards Report the IN_PWR_LOW Alarm Due to Wavelength Wander
MC-A90 The Incorrect Configuration of DWC Leads To Abnormal Optical Power and
Service Interruption, the WDM Side of the LBE Reports the IN_PWR_HIGH and
OTU_LOF Alarms Abruptly
MC-A93 The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the
OPU Board
MC-A101 The Wavelength Is Unstable or Changed Due to Optical Power Variation
MC-A126 VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm
Even If the Attenuation Is Decreased
MC-A169 T2000 Reports Errors After the Standard Optical Power of Single Wavelength
Is Set to 7 dBm with ALC in Power Reference Mode
MC-A174 Excessive PDL of Fiber Results in Slow Changes of the Received Optical
Power on an OTU Board
MC-A182 Receive Optical Power Is Excessively Low Because of the End Face Problem
of the Fiber Jumper, the OAU Board Reports the MUT_LOS Alarm
MC-A186 Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board
Causes Low Receive Optical Power, The Connected OAU Board At The Downstream
Station Reports MUT_LOS And R_LOS Alarms
MC-A194 A Malfunctioning VA1 Board Causes Abnormal Optical Power, The NS2
Boards Reports IN_PWR_HIGH Alarms For Three Times
MC-A196 The Insertion Loss of the FIU Board on OptiX OSN 6800 Is High Because the
Fiber and Fiber Connector Are Not Securely Connected
MC-A198 Optical Power Can Be Detected at the IN and OUT Ports of the FIU Board
Because of Incorrect Connections of Fiber Patch Cords
MC-A201 Frequent Fiber Cut Results in High Line Attenuation and the IN_PWR_LOW
Alarm Reported by the OTU Board
MC-A203 System of Few Wavelengths Fails to Function
MC-A239 Inappropriate Line Optical Power Adjustment Causes Deteriorated 40G
Performance
MC-A242 Excessively High Incident Optical Power Results in Poor Performance of
OTU Boards
MC-A244 The Insertion Loss of a Board Is Abnormal
7 Bit Errors
Symptom
The optical power is normal but a large number of bit errors occur in services on multiple
channels.
The OTU, or tributary board and line board reports alarms such as OTUk_EXC, OTUk_DEG,
BEFFEC_EXC, B1_EXC, and B1_SD.
Networking configuration example is shown in Figure 7-1.
Impact on System
A large number of bit errors occur in services on multiple channels.
Possible Causes
Cause 1: The attenuation of the optical cable or that of the fiber jumper in the
multiplexing part is too large.
Cause 2: The equipment temperature is too high.
Cause 3: The configuration of the dispersion compensation module (DCM) is improper.
Cause 4: The optical power of the main path is faulty.
Cause 5: The non-linearity of the optical fiber. Bit errors can be caused by the
non-linearity of the optical power but not often.
Cause 6: The ring fiber adapter from the equipment to the ODF is damaged.
Cause 7: The PMD exceeds the permitted range.
Multi-channel bit errors might be caused by the improper commissioning of the optical power
of the system, please check the optical power of system.
Procedure
Cause 1: The attenuation of the optical cable or that of the fiber jumper in the
multiplexing part is too large.
a. Refer to Checking Fiber Jumpers by Using an Optical Power Meter. Check whether
the fiber jumper in the multiplexing part is faulty. If yes, replace the fiber jumper.
The fiber jumpers in the multiplexing part are the fiber jumpers between:
The equipment and ODF
The OA and FIU
The OA and MUX/DEMUX
ODFs
TDC and RDC of the OAU
Cause 2: The equipment temperature is too high.
a. Check whether the NE generates alarms such as TEMP_OVER. If yes, check the
environmental conditions of the telecommunications room. Clean the air filter.
Cause 3: The configuration of the dispersion compensation module (DCM) is improper.
a. Check optical cable parameters such as the type and actual length of the optical
cable. Check the configuration of the DCM. After that, adjust the compensation
distance of the DCM to a value that matches the actual length of the optical cable.
Cause 4: The optical power of the main-path is abnormal.
a. Check the input and output optical power of boards between MUX of the transfer
station and the DEMUX of the receive station. If the input optical power is normal
but the output optical power does not reach the standard output optical power,
replace the board.
Cause 5: The non-linearity of the optical fiber. Bit errors can be caused by the
non-linearity of the optical power but not often.
a. Decrease or increase the optical power, to judge whether bit errors are caused by the
non-linearity of the optical fiber.
Increasing optical power causes bit errors to increase.
Decreasing optical power causes bit errors to decrease.
b. Increase the value of attenuator.
Perform this procedure only after all other possible causes have been checked.
Cause 6: The ring fiber adapter from the equipment to the ODF is damaged.
a. Check the ring fiber adapter between the ODF and WDM equipment. If the ring
fiber adapter is faulty, replace it.
Cause 7: The PMD exceeds the permitted range.
a. Test the PMD of optical fibers in all spans to obtain the PMD values. Resplice the
splicing points of optical fibers with very large PMD and resplice the splicing
points with large attenuation. The attenuation of optical fibers will improve.
b. The PMD values of several spans are larger than the recommended value in the
system design. It is recommended that the fiber core be replaced to ensure that the
total PMD value of optical fibers between electrical regenerators of all channels is
smaller than the system design. In this manner, the system can work stably in the
long run and the system instability caused by large PMD can be resolved radically.
The 40G services require a smaller PMD. When the accumulated PMD exceeds the threshold, a large
OSNR penalty will be introduced, deteriorating the system performance. In a short period of time, high
PMD leads to the generation of the BEFFEC_EXC alarm for some wavelengths and irregular changes to
the receive-end system performance.
----End
Symptom
The OTU, or tributary board and line board reports alarms such as OTUk_EXC, OTUk_DEG,
BEFFEC_EXC, B1_EXC, and B1_SD.
Networking configuration example is shown in Figure 7-2.
Impact on System
A large number of bit errors occur in one channel and the services are transiently interrupted.
Possible Causes
Cause 1: The input optical power of the OTU, or tributary board and line board on the
WDM side is abnormal.
Cause 2: The fiber jumper between the MUX and ODF is aged or bent. Hence, the
attenuation of the fiber jumper is too large.
Cause 3: The equipment temperature is too high.
Cause 4: The FEC modes of the two interconnected boards might be different.
Cause 5: The optical interfaces of the OTU, or tributary board and line boards are dirty.
Cause 6: The OTU, or tributary board and line board is faulty.
Procedure
Cause 1: The input optical power of the OTU, or tributary board and line board on the
WDM side is abnormal.
a. Checking fiber jumpers by using an optical power meter. Check whether the input
optical power of the OTU, or tributary board and line board is too low. If yes, clean
the fiber.
Cause 2: The fiber jumper between the OTU, or tributary board and line board,
MUX/DMUX or the fiber jumper between the MUX and ODF is aged or bent. Hence,
the attenuation of the fiber jumper is too large.
a. Replace the fiber jumper.
Cause 3: The equipment temperature is too high.
a. Check whether the NE contains alarms such as TEMP_OVER. If yes, the operating
temperature of the board is too high. Check the environmental conditions of the
telecommunications room. Clean the air filter.
Cause 4: The FEC modes of the two interconnected boards might be different.
a. Query the FEC mode of the two interconnected boards on the U2000. If the two
modes differ, re-set the FEC Working state and ensure state matching.
Cause 5: The optical interfaces of the OTU, or tributary board and line board board are
dirty.
a. If the optical interfaces of the OTU, or tributary board and line board board are
dirty, blow them with compressed gas to clean them.
Cause 6: The OTU, or tributary board and line board is faulty.
a. If the fiber jumper, input optical power and operating temperature are normal, and
the FEC modes of the OTU, or tributary board and line boards are matching,
replace the OTU, or tributary board and line board at receive end. If the bit errors
disappear, it indicates that the OTU, or tributary board and line board at receive end
is faulty.
b. If the OTU, or tributary board and line board at receive end is normal, replace the
OTU, or tributary board and line board at transmit end. If the bit errors disappear, it
indicates that the OTU, or tributary board and line board at transmit end is faulty.
----End
Symptom
The telecommunications room of a certain site does not meet the environmental requirements
of a device. The device reports bit errors.
Impact on System
Unfavorable environmental conditions may cause bit errors in services.
Possible Causes
Cause 1: The temperature and humidity of the environment do not meet the
environmental requirements of a device.
Cause 2: A strong external interference source exists.
Procedure
Cause 1: The temperature and humidity of the environment do not meet the requirements
of long term running of the device. As a result, bit errors are generated.
a. Check whether the temperature and humidity of the environment meet the
requirements.
The detailed requirements are as follows:
Temperature: 0°C to +45 °C (32°F to 113°F)
Relative humidity: 10% to 90%
If... Then...
The temperature and humidity of the Check and adjust the air conditioner in the
environment do not meet the requirements telecommunications room to make sure that
the temperature and humidity of the
telecommunications room are in the proper
range. Check whether the bit errors persist.
If the bit errors persist, check whether the
fault is due to other causes.
If... Then...
Cause 2: A strong external interference source exists. As a result, bit errors are generated.
a. Check whether there is a transformer, high-voltage transmission line, or
high-current device near the device.
If... Then...
If... Then...
the device whether the bit errors persist. If the bit
errors persist, check whether the fault is due
to other causes.
d. Check whether a hand-held mobile communication device is in use near the device.
If... Then...
If... Then...
is in use near the device causes.
Related Information
Table 7-1 lists the requirement for the electromagnetic interference.
Equipment rooms or equipment should be kept far away from strong electromagnetic
interference sources. If this requirement cannot be met, take additional radiation protection
measures. For example, place the equipment in a radiation-resistant network cabinet or a
sealed cabinet.
G.652D 30 mm
G.657A2 10 mm
G.657B3 8 mm
Note: When fibers are connected to CRPC boards, the bending radius of the fibers must be
greater than or equal to 50 mm to ensure expected transmission performance.
Symptom
Large amounts of regeneration section bit errors and multiplex section bit errors are generated
on the line.
Impact on System
Device faults cause bit errors.
Possible Causes
Cause 1: The clock unit is faulty.
Cause 2: The cross-connect unit is faulty.
Cause 3: The line board is faulty.
Procedure
Step 1 Cause 1: The clock unit is faulty. As a result, bit errors are generated.
1. Check the configuration of the clock on the NE.
If... Then...
The configuration of the clock on the NE is Re-configure the clock on the NE. Check
incorrect whether the bit errors persist. If the bit
errors persist, proceed to the next step.
If... Then...
The configuration of the clock on the NE is Re-configure the clock on the NE. Check
incorrect whether the bit errors persist. If the bit
errors persist, proceed to the next step.
Related Information
After the device reports bit errors, you need to analyze the features of the bit errors to locate
the fault to a single site.
You can use the loopback method to locate faults to a board of a certain site, and then use the
replacement method to reset or replace the doubted board.
The following cases are related to the OptiX WDM product series.
Related Cases:
MD-A13 Bit Error Alarm (BEFFEC_EXC) Is Generated When Optical Power Gets
Close to the Threshold
MC-A16 The R_LOF and R_OOF Alarms Are Reported in the 24-Hour Bit Error Test
Because the Line Fiber Loss Is Very Large
MC-A31 Wrong Calculation for Dispersion in One DWDM Project
MC-A40 Over Compensation Causes Very High Bit Error Rate of the Short Waves After
Correction and the SM_BIP8_OVER and SM_BIP8_SD Alarms Are Transiently
Reported on the Board
MC-A44 Bit Errors Generated in the Services, the Meter Reports the HP_RDI and
ERROR Alarms
MC-A55 Improper DCM Distribution Causes Abnormal Service and Bit Error Alarm
BEFFEC_EXC Is Detected on the Newly-added LWFS Board
MC-A63 MSBBE Bit Errors and OTU_LOF Alarm Occur in a DWDM 10G Network
Due to the Incorrect PMD
MC-A88 The OTU Board Reports the B1_EXC Alarm, And There Are the Difference in
BER Reported by the OTU Board and Test Instrument
MC-A118 An R_OOF Alarm Occurs When the LWC Interconnects with Third-Party
Equipment
MC-A124 Determine the Factors That Affect the OSNR By Using the ANT30 Tester
MC-A199 An OTU Board Reports Bit Errors Due to High Fiber Reflection
MC-A202 Mixing Compensation of DCMs Results in the Inconsistency of Channel
Performance
MC-A205 WDM-Side Pre-FEC BER Changes Drastically
MC-A240 Isolated Bit Errors Are Found in the Long-Term Bit Error Testing of a 40G
System
8 NE Offline Problems
Symptom
One NE at a station is unreachable by the U2000, whereas the other NEs at this station are
reachable. The NE_COMMU_BREAK and NE_NOT_LOGIN alarms are reported on the
U2000.
The services on the NE are not interrupted.
Impact on System
The NE is unreachable by the U2000.
Possible Causes
Cause 1: The network cable is disconnected or loose. For example, between the NE and
the HUB, between the GNE and the computer where the NMS server is installed,
between the GNE and non-GNEs, between the master and slave subrack of an NE.
Cause 2: The NE Attributes of the NE is changed by mistake, such as the IP address, ID,
Gateway Type, User Name or Password
Cause 3: The system control board on the NE is faulty.
Cause 4: ECC communication is interrupted.
Cause 5: The NE(non-first gateway NE) encounters system control board active/standby
switching.
Cause 6: Coherent and non-coherent boards are interconnected.
Procedure
Cause 1: The network cable is disconnected or loose. For example, between the NE and
the HUB, between the GNE and the computer where the NMS server is installed,
between the GNE and non-GNEs, between the master and slave subrack of an NE.
a. Determine if the network cable connection between the NE and the HUB is loose. If
the network cable connection is loose, secure it.
b. Check whether network cables are correctly connected between the GNE and the
computer where the NMS server is installed, between the GNE and non-GNEs,
between the master and slave subrack of an NE.
c. Use a cable tester to test the network cable and the network port. If the network
cable is faulty, replace it.
d. If the network cable is good, replace the interface, to which the network cable is
connected to the HUB. If the problem clears, the interface of the HUB may be
damaged.
e. If the network cable and the HUB is good, the interface board (such as EFI, EFI1,
EFI2, or AUX) is faulty, replace it.
Cause 2: The NE Attributes of the NE is changed by mistake, such as the IP address, ID,
Gateway Type, User Name or Password.
a. Log in to the NE on the Web LCT and restore the initial IP address , ID, gateway
type, NE user or password of the NE according to the record.
Cause 3: The system control board on the NE is faulty.
a. Log in to the NE on the Web LCT. If you fail to log in, the system control board is
faulty. Reset the board. If the problem persists, replacing the SCC board.
Cause 4: ECC communication is interrupted.
a. A maximum of 16 users can simultaneously log in to an NE. If the number of users
reaches the upper limit, other users are not permitted to log in to the NE. For the
method of handling the interruption of ECC communication, see 14.1 ECC
Communication Interruption.
Cause 5: The NE(non-first gateway NE) encounters system control board active/standby
switching.
a. No handling is required. Communication between the NE and U2000 will be
restored after the system control board active/standby switching.
Cause 6: Coherent and non-coherent boards are interconnected.
a. The DCN bytes are defined differently for coherent and non-coherent services, so
the two types of services cannot be interconnected. If DCN channels are unavailable,
check whether the interconnected boards are coherent boards.
----End
Symptom
All NEs in a subnet are unreachable by the U2000. The NE_COMMU_BREAK,
NE_NOT_LOGIN, and GNE_CONNECT_FAIL alarms are reported on the U2000.
Impact on System
The NEs are unreachable by the U2000 in the subnet.
Possible Causes
Cause 1: The gateway NE is faulty.
Cause 2: The network cable between the gateway NE and the HUB is disconnected or
the interface to the HUB is damaged.
Cause 3: The IP address of the gateway NE is changed.
Cause 4: The optical cable is faulty.
Cause 5: The gateway NE encounters the system control board active/standby switching
if only one gateway NE is provided. The primary gateway NE encounters the system
control board active/standby switching if the primary and secondary gateway NEs are
provided.
Procedure
Cause 1: The gateway NE is faulty. No backup gateway NE is configured for the subnet.
a. Determine if the power supply of the gateway NE is faulty. If yes, clear the fault of
the power supply.
b. Log in to the gateway NE on the Web LCT. If you fail to log in, the system control
board is faulty. replacing the SCC board.
Cause 2: The network cable between the gateway NE and the HUB is faulty.
a. Determine if the network cable connection between the gateway NE and the HUB is
loose. If the network cable connection is loose, secure it.
b. Use a cable tester to test whether the network cable is good. If the network cable is
faulty, replace it.
c. If the network cable is good, replace the interface to the HUB. If the problem clears,
the HUB is damaged.
Cause 3: The IP address of the gateway NE is changed.
a. Log in to the NE on the Web LCT and restore the initial IP address of the gateway
NE according to the record.
Cause 4: The optical cable is faulty.
a. When the optical cable is cut off in the main optical path, the NEs in the subnet
become unreachable by the U2000. At the same time, a large number of alarms and
performance events occur in the main optical path. Hence, the normal operation of
services is affected. In this case, the optical cable is faulty.
Cause 5: The gateway NE encounters the system control board active/standby switching
if only one gateway NE is provided. The primary gateway NE encounters system the
control board active/standby switching if the primary and secondary gateway NEs are
provided.
a. No handling is required. Communication between the gateway NE and U2000 will
be restored after the system control board active/standby switching.
----End
Solution
To prevent all NEs in a subnet from becoming unreachable by the U2000 when the gateway
NE fails, configure a backup gateway NE for the NEs in the subnet.
Symptom
An NE frequently becomes unreachable by the U2000. The NE_COMMU_BREAK,
NE_NOT_LOGIN, and GNE_CONNECT_FAIL alarms are reported on the U2000.
Impact on System
The NE is unreachable by the U2000.
Possible Causes
Cause 1: The IP address of the NE conflicts with that of another NE.
Cause 2: The ECC communication is intermittent.
Cause 3: The load of ECC communication is extremely heavy.
Cause 4: Another NE user with the same account as that of the current NE user in the
network has logged in to the NE.
Cause 5: When ESC and OSC coexist between station A and B, the system preferentially
selects the ESC for communication. Bit errors leads to the unstable link and the ESC
communication fails. The switching between ESC and OSC occurs frequently because
the route of ESC is shorter than the route of OSC.
Cause 6: The scale of the DCN subnetwork is extremely large.
Procedure
Cause 1: The IP address of the NE conflicts with that of another NE.
a. Determine if the IP addresses of the other devices (such as routers and servers) that
are newly configured in the network are the same as the IP address of the frequently
unreachable NE. Make sure that the IP address of the NE is unique.
Cause 2: The ECC communication is intermittent.
a. For the method of handling the intermittent ECC communication, see 14.2
Intermittent ECC Communication.
Cause 3: The load of ECC communication is extremely heavy.
a. For the method of handling the extremely heavy load of ECC communication, see
8.4 The System Control Board Is Frequently Reset.
Cause 4: Another NE user with the same account as that of the current NE user in the
network has logged in to the NE. As a result, the NE becomes unreachable, and the
NE_NOT_LOGIN alarm is frequently reported on the U2000.
a. Plan and manage the users that can log in to the NE. For the information on NE user
management, see "Creating an NE User".
Cause 5: When ESC and OSC coexist between station A and B, the system preferentially
selects the ESC for communication. Bit errors leads to the unstable link and the ESC
communication fails. The switching between ESC and OSC occurs frequently. The NEs
at station B are frequently unreachable by the U2000.
a. Disable the ESC communication between station A and B on the U2000, keep the
OSC communication.
In NE Explorer, select the NE.
Select Communication > DCC Management from Function Tree.
In DCC Rate Configuration, select the board. Double click the parameter
area of Enabled/Disabled.
Choose Disabled in the drop list.
Click Apply.
b. Rectify the bit errors on the link, for details refer to 7 Bit Errors.
c. Enable the ESC communication between station A and B after the link becomes
stable.
Cause 6: The scale of the DCN subnetwork is extremely large.
a. Due to the inherent limitations of the DCC protocol, there is a limit on the number
of NEs (physical NEs with unique IDs) in a network even though there are
sufficient GNEs. If the number of NEs in a network exceeds the limit, the network
must be divided into multiple DCN subnets. The details refer to DCN Networking
Capability.
Each GNE can connect to a maximum of 50 non-GNEs, regardless of the protocol. If there are more
than 50 non-NEs for one GNE, another GNE must be added.
----End
Symptom
Due to an ECC communication overload, the system control board is frequently reset and the
U2000 is frequently unable to reach the NE.
System Impact
The U2000 cannot reach the NE.
Possible Causes
Cause 1: The ECC communication load is extremely heavy.
Procedure
Cause 1: The ECC communication load is extremely heavy. The scale of the ECC
network is extremely large and the inter-NE ECC communication load exceeds the
maximum processing capability of the NEs in the network. As a result, the system
control board frequently resets.
a. Check the scale of the ECC network. The number of NEs in the network cannot
exceed 100. If there are more than 100 NEs in the network, divide the network into
subnets. Create a data communication network (DCN) management channel for
each subnet so the subnets are independent of each other.
b. Check the per-NE scale. When multiple pieces of equipment are connected by using
a HUB or are cascaded inter subracks, the extended ECC function of the network
interfaces of the equipment is used for communication. If not more than four pieces
of equipment are connected by using one HUB, the automatic extended ECC
function can be enabled. If more than four pieces of equipment are connected by
using one HUB, the manual extended ECC function is recommended for
communication to prevent ECC storms. For details on how to set the manual
extended ECC function, refer to "Configuring Extended ECC in Specified Mode".
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A20 The T2000 Cannot Log in to the Remote GNE Connected by the Router
MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser
MC-A64 Many BD_STATUS Alarms Occur Due to the ECC Storm
MC-A83 The OptiX OSN 6800 Is Not Reachable When the NE IP Is Modified
MC-A110 Question About the Extended ECC of WDM NEs
MC-A113 Communication Between the WDM Equipment And the DCN Network Fails
After a Hub Is Connected To the DCN Network
MC-A135 The Communication Between the NE and the T2000 Stops Because the NE
Software Cannot Switch the ECC from an OSC Board to an OTU Board Automatically
MC-A181 An NE Is Frequently Unreachable to the NMS Due to Insufficient Processing
Capacity of a Router
MC-A212 Secondary GNE Becomes Unavailable After a Change of the Maximum
Number of Route Hops of an NE
MC-A213 Internal Communication of an NE Is Abnormal And Many Boards Report
Transiently BD_STATUS or COMMUN_FAIL Alarms Due to Conflicted Subrack IDs
MC-A283 All NEs at New Sites Are Frequently Unreachable to the NMS
MC-A289 An OptiX OSN 1800 NE Is Unreachable by the NMS Due to the Incorrect
Subrack ID
Fault Description
The board is offline and unavailable on the U2000 while the other boards are online.
The board reports the BD_STATUS alarm.
Possible Causes
Cause 1: The slot that houses the board is faulty.
Cause 2: The board is faulty.
Procedure
Cause 1: The slot that houses the board is faulty.
a. Reseat the board to check whether the fault is removed.
b. If the fault persists, change the slot that houses the board.
Cause 2: The board is faulty.
a. Replace the faulty board.
----End
Fault Description
Multiple or all boards are offline and unavailable on the U2000.
Multiple or all boards on the NE report the BD_STATUS alarms.
Possible Causes
Cause 1: The NE is unreachable.
Cause 2: The network cable between the master and slave subracks is faulty.
Cause 3: The AUX board is faulty.
Cause 4: The backplane is faulty.
Procedure
Cause 1: The NE is unreachable.
a. If the U2000 reports NE_COMMU_BREAK or NE_NOT_LOGIN alarm, the NE is
likely unreachable. For details, see 8.1 Unreachability of One NE by the U2000.
Cause 2: The network cable between the master and slave subracks is faulty.
a. Check whether the network cable between the master and slave subracks is
damaged or loose and remove the fault accordingly.
Cause 3: The AUX board is faulty. Because the AUX board implements communication
between boards or subracks and inter-sburack management, multiple boards will become
offline if the AUX board is faulty.
a. Check whether the AUX board is faulty. If the BD_STATUS alarm on other boards
persists after the AUX board is reset (cold) or is removed and inserted again, go to
the next step.
This section describes the handling methods for services with DBPS protection that fail to
automatically switch to the protection channel when the working channel works abnormally.
10.9 Board 1+1 Protection
This topic describes how to resolve switchover issues when board-level protection fails to
automatically switch services to the protection channel. Board-level protection refers to an
equipment-level protection scheme, which includes M:N protection for the cross-connect
board and 1+1 protection for the system control board.
10.10 MS SNCP Protection
This section describes the handling methods for services with MS SNCP protection that fail to
automatically switch to the protection channel when the working channel works abnormally.
10.11 DLAG Protection
This section describes the handling methods for services with DLAG protection that fail to
automatically switch to the protection channel when the working channel works abnormally.
10.12 Board-Level Protection
This section describes the handling methods for services with board-level protection that fail
to automatically switch to the protection channel when the working channel works
abnormally.
10.13 ODUk SPRing Protection
This section describes the handling methods for services with ODUk SPRing protection that
fail to automatically switch to the protection channel when the working channel works
abnormally.
10.14 Optical Wavelength Shared Protection
This section describes the handling methods for services with optical wavelength shared
protection that fail to automatically switch to the protection channel when the working
channel works abnormally.
10.15 Inter-Subrack Communication Protection
This topic describes how to resolve switchover issues when inter-subrack communication
protection fails to automatically switch services to the standby route when communication
between master and slave subracks is interrupted.
10.16 Protection Cases
This section lists cases related to Protection.
Symptom
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The optical line protection (OLP) board may report an OLP_PS or OLP_STA_INDI alarm.
Possible Causes
Cause 1: The protection group parameters are incorrectly configured.
Cause 2: Locked or forced switching commands have been manually issued.
Cause 3: The optical fibers are improperly connected to the corresponding boards.
Cause 4: The protection channel is working abnormally.
Troubleshooting Workflow
The following figure illustrates the optical line protection automatic switching failure
troubleshooting process.
Figure 10-1 Optical line protection automatic switching failure troubleshooting flowchart
Start
Yes No
No No
Yes No
Yes No
Forcibly switch the End
services to
the protection channel.
Contact Huawei
engineers.
Procedure
Cause 1: The protection group parameters are incorrectly configured.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, click Query to query all protection group
parameter values. In the Operation Result dialog box, click Close.
c. Compare these values against those specified in "Dependency and Limitation" and
"Parameters" to ensure that the parameters are configured correctly.
Cause 2: Locked or forced switching commands have been manually issued.
a. In the Port Protection window, click Query to check the Switching Status
parameter of the protection group.
b. If Switching Status is Locked or Force to Working Channel, click Function and
choose Clear to clear the locked or forced switching commands.
Cause 3: The optical fibers are improperly connected to the corresponding boards.
a. Check whether the optical fibers are properly connected to optical ports 1 (RI1/TO1)
and 2 (RI2/TO2) on the OLP boards located at the two stations next to the failure
point. For details, refer to "Principles".
Cause 4: The protection channel is working abnormally.
a. In the Port Protection interface, click Query to check the Protection Channel
Status parameter of the protection group.
b. If Protection Channel Status is SF, check whether MUT_LOS and
POWER_DIFF_OVER alarms are being reported on the corresponding boards on
the protection channel, clear the alarms.
If Protection Channel Status is SF, faults have occurred on both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Symptom
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
When the OLP, DCP, or QCP boards initiate intra-board 1+1 protection, the OLP, DCP,
or QCP boards may report an INTRA_OTU_PS or INTRA_OTU_STA_INDI alarm.
When the intra-board 1+1 protection is realized by dual fed and selective receiving OTU,
the OTU board may report the INTRA_OTU_PS alarm or INTRA_OTU_STA_INDI
alarm.
Possible Causes
The protection group parameters are incorrectly configured.
Locked or forced switching commands have been manually issued.
The optical fibers are improperly connected to the corresponding boards.
The protection channel is working abnormally.
Troubleshooting Flow
The following figure illustrates the intra-board 1+1 protection automatic switching failure
troubleshooting process.
Figure 10-2 Intra-board 1+1 protection automatic switching failure troubleshooting flowchart
Start
Yes No
No No
Yes No
Yes No
Forcibly switch the End
services to
the protection channel.
Contact Huawei
engineers.
Procedure
Cause 1: The protection group parameters are incorrectly configured.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, click Query to query all protection group
parameter values. In the Operation Result dialog box, click Close.
c. Compare these values against those specified in "Dependency and Limitation" and
"Parameters" to ensure that the parameters are configured correctly.
If Protection Channel Status is SD, SF, faults have occurred on both the working and protection
channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Symptom
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
Possible Causes
The protection group parameters are incorrectly configured.
Locked or forced switching commands have been manually issued.
The optical fibers are incorrectly connected to the corresponding boards.
The protection channel is faulty.
Troubleshooting Workflow
The following figure illustrates troubleshooting process of the client 1+1 protection automatic
switching failure.
Figure 10-3 Troubleshooting flowchart of the client 1+1 protection automatic switching failure
Start
Yes No
No No
Yes No
Yes No
Contact Huawei
engineers.
Procedure
Cause 1: The protection group parameters are incorrectly configured.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, click Query to query all protection group
parameter values. In the Operation Result dialog box, click Close.
c. Compare these values against those specified in "Dependency and Limitation" and
"Parameters" to ensure that the parameters are configured properly.
If Protection Channel Status is SD or SF, both the working and protection channels are faulty.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The OTU board may report SW_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
Locked or forced switching is not released.
The electrical cross-connections are configured incorrectly.
The protection channel works abnormally.
Figure 10-4 Fault handling flow when automatic switching by SW SNCP protection fails
Start
No
No
Yes No
No No
End
Handle the faults on the
working channel.
Contact Huawei
engineers.
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree. Click the SNCP Service Control tab.
b. Click Query in the SNCP Service Control interface, to query the values of all
parameters of the protection group. Click Close in the Operation Result dialog
box.
c. Compare the values against the principles and requirements specified in
Dependency and Limitation and Parameters in the Feature Descriptionto ensure
that the parameters are configured properly.
If the Channel Status parameter of the protection cross-connection is displayed as SD, SF, it is
indicated that faults have occurred in both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Symptom
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
Tributary, line or PID board may report an ODU_SNCP_STA_INDI alarm.
Possible Causes
Cause 1: The SNCP Type is inappropriate for the service scenario.
Troubleshooting Workflow
The following figure illustrates the ODUk SNCP protection automatic switching failure
troubleshooting process.
Figure 10-5 ODUk SNCP protection automatic switching failure troubleshooting flowchart
Start
Are the
Do the parameter values No Yes
Modify the parameters. services switched
comply with the to the protection
specifications?
channel?
No
Yes
Is Are the
a locked or forced Yes Clear the locked or Yes
services switched
switching command forced switching
manually issued? to the protection
command.
channel?
No
No
Yes No
No No
Contact Huawei
engineers.
Procedure
Cause 1: The SNCP Type is inappropriate for the service scenario.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Then click the SNCP Service Control tab.
b. In the SNCP Service Control window, click Query to query the Protection Type
of the protection group. In the Operation Result dialog box, click Close.
c. Refer to "Dependency and Limitation" and "Parameters" to check whether the
Protection Type of the protection group is appropriate for the service scenario.
Cause 2: The protection group parameters are incorrectly configured.
a. In the SNCP Service Control window, click Query to query all protection group
parameter values.
b. Compare these values against those specified in "Dependency and Limitation" and
"Parameters" to ensure that the parameters are configured correctly.
Cause 3: Locked switching or forced switching commands have been manually issued.
a. In the SNCP Service Control interface, click Query to check the Status parameter
of the protection group.
b. If Status is displayed as Lockout or Forced (from protection to working)
switching state, select the protection group and right-click it. Choose Clear from
the shortcut menu to clear the locked or forced switching configuration.
Cause 4: The electrical cross-connections are configured incorrectly.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree.
b. Click Query on the bottom of the WDM Cross-Connection Configuration
interface to check the created cross-connections.
c. According to the network design, ensure the source and sink ports of the dual fed
cross-connections that are configured on the source end are correct.
Cause 5: The protection channel is working abnormally.
a. In the SNCP Service Control window, click Query to query the Channel Status
parameter of the protection cross-connection.
b. If Channel Status is SD or SF, check whether the alarms listed in Trigger
Conditions are being reported on the corresponding boards on the protection
channel, clear the alarms.
If the Channel Status parameter of the protection cross-connection is SD or SF, faults have occurred on
both the working and protection channels.
Cause 6: The line board is faulty.
a. Forcibly switch services to the protection channel, which will eventually restores
services.
b. Replace the faulty line board.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Before the working channel is restored from a failure (for example, the faulty board has not
yet been replaced), services on the protection channel may run without protection for a long
time. To avoid a second failure on the network, you are advised to convert an idle and
unprotected service to the SNCP service for protection. For details, refer to "Converting a
Normal WDM Service to an SNCP Service." After the working channel is restored, convert
the SNCP service back to an unprotected service. For details, refer to "Converting an SNCP
Service to a Normal WDM Service."
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
L4G, TBE, LEM24, LEX4 board of OptiX OSN 6800/OptiX OSN 3800 may report
VLAN_SNCP_PS.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
Locked or forced switching is not released.
The electrical cross-connections are configured incorrectly.
The protection channel works abnormally.
Figure 10-6 Fault handling flow when automatic switching by VLAN SNCP protection fails
Start
Yes No
Yes No
Contact Huawei
engineers.
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. Select the desired Ethernet board in the NE Explorer, and choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree.
b. Click Query in the VLAN SNCP Service Management tab to query the values of
all parameters of the protection group.
If the Link Status parameter of the protection service is displayed as SF, it is indicated that faults have
occurred in both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Symptom
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
Tributary, line or PID board may report an ODU_SNCP_PS alarm or
ODU_SNCP_STA_INDI alarm.
Possible Causes
Cause 1: The SNCP Type is inappropriate for the service scenario.
Cause 2: The protection group parameters are incorrectly configured.
Cause 3: Locked or forced switching commands have been manually issued.
Cause 4: The electrical cross-connections are incorrectly configured.
Cause 5: The protection channel is working abnormally.
Troubleshooting Workflow
The following figure illustrates the tributary SNCP protection automatic switching failure
troubleshooting process.
Figure 10-7 Tributary SNCP protection automatic switching failure troubleshooting flowchart
Start
Do Are the
the parameter No Yes
Modify the parameters. services switched
values comply with the
specifications? to the protection
channel?
No
Yes
No
No
Yes No
Yes No
Contact Huawei
engineers.
Procedure
Cause 1: The SNCP Type is inappropriate for the service scenario.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Then click the SNCP Service Control tab.
b. In the SNCP Service Control window, click Query to query the Protection Type
of the protection group.
If the Channel Status parameter of the protection cross-connection is SD or SF, faults have occurred on
both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The board may report DBPS_ABNORMAL alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
There is alarm to be solved.
Figure 10-8 Fault handling flow when automatic switching by DBPS protection fails
Start
Yes No
Yes No
End
Contact Huawei
engineers.
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. In the NE Explorer, select the NE and then choose Configuration > Distributed
Board-Level Protection from the Function Tree.
b. In the right pane, click Query to obtain the current information about the created
DBPS.
c. Compare the values against the principles and requirements specified in
Dependencies and Limitations and Parameters in the Feature Description to check
and ensure that the parameters are configured properly.
Cause 2: There is alarm to be solved.
a. Check if there is the DBPS_ABNORMAL, LINK_ERR, R_LOS, R_LOF,
HARD_BAD, PORT_MODULE_OFFLINE alarms.
b. Solve the alarms. For details, refer to the Alarms and Performance Events
Reference.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Background Information
The OptiX OSN 3800 supports 1+1 protection for only SCC boards.
The OptiX OSN 6800 supports 1+1 protection for only cross-connect boards and SCC boards.
Symptom
During normal network operations, conditions that trigger protection switching occur on the
equipment, but services do not automatically switch to the standby board.
If 1+1 protection for the system control board fails to be automatically switched, the
U2000 cannot reach the equipment. The services on the equipment, however, are
unaffected.
If the protection switching of the cross-connect boards or clock boards fails, the services
on the equipment are interrupted.
Possible Causes
Cause 1: No standby board is configured.
Procedure
Cause 1: No standby board is configured.
a. Configure a standby board.
Cause 2: The standby board is faulty.
a. Replace the faulty standby board.
----End
Solution
After configuring a standby board or replacing the faulty standby board, replace the faulty
active board to restore services.
To replace a board with active/standby protection, use a board of the same type.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The OTU board may report MS_SNCP_PS alarm or MS_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The related boards work abnormally.
The parameters of the protection group are improperly configured.
Locked switching or forced switching is not released.
The electrical cross-connections are configured incorrectly.
The protection channel works abnormally.
Figure 10-9 Fault handling flow when automatic switching by MS SNCP protection fails
Start
No
Yes
No
No
Modify the
No Are services Yes
Are the configurations of configurations of switched to the
electrical cross-connections electrical cross- protection channel?
correct?
connections.
Yes No
No
Does the protection Handle the faults on the Are services Yes
channel work protection channel. switched to the
normally? protection channel?
Yes No
Contact Huawei
engineers.
Procedure
Cause 1: The related boards work abnormally.
a. Allocate the board which works abnormally.
b. Replace the board. For details refer to Parts Replacement.
Cause 2: The parameters of the protection group are improperly configured.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree. Click SNCP Service Control tab.
b. Click Query in the SNCP Service Control interface, to query the values of all
parameters of the protection group.
c. Compare the values against the principles and requirements specified in
Dependency and Limitation and Parameters in the OptiX OSN 6800/3800 Feature
Description to check and ensure that the parameters are configured properly.
Cause 3: Locked switching or forced switching is not released.
a. In the SNCP Service Control interface, click Query to query the Status parameter
of the protection group.
b. If Status is displayed as Lockout or Forced (from protection to working)
switching state, right-click the protection group, and then choose Clear from the
shortcut menu, to clear the locked or forced switching configuration.
Cause 4: The electrical cross-connections are configured incorrectly.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree.
b. Click Query on the bottom of the WDM Cross-Connection Configuration
interface to query the created cross-connections.
c. According to the network design, check if source and sink ports of the dual fed
cross-connections that are configured on the source end are correct.
Cause 5: The protection channel works abnormally.
a. In the SNCP Service Control interface, click Query to query the Channel Status
parameter of the protection cross-connection.
b. If Channel Status is displayed as SD, SF, check whether the following alarms exist
on the relevant boards on the protection channel: R_LOF, R_LOS, R_LOC,
OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI,
ODUk_PM_LCK, ODUk_LOFLOM, REM_SF, B1_EXC, ODUk_PM_EXC,
OTUk_EXC, REM_SD. For the method of handling the alarms, see the Alarms and
Performance Events Reference.
If the Channel Status parameter of the protection cross-connection is displayed as SD, SF, it is
indicated that faults have occurred in both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The board may report DLAG_PROTECT_FAIL alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
There is alarm which needs to be cleared.
Figure 10-10 Fault handling flow when automatic switching by DLAG protection fails
Start
Yes No
Yes No
End
Contact Huawei
engineers.
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. In the NE Explorer, select the NE and then choose Configuration > Ethernet
Distributed Link Aggregation Management from the Function Tree.
b. In the right pane, click Query to obtain the current information about the created
DLAG.
c. For DLAG Protection(EoS), compare the values against the principles and
requirements specified in Dependency and Limitation and Parameters in the OptiX
OSN 6800/3800 Feature Descriptionto ensure that the parameters are configured
properly.
Cause 2: There is alarm which needs to be cleared.
a. On the U2000, determine if there is DLAG_PROTECT_FAIL or other alarms on
the protection channel.
b. Clear the alarms. For more information, refer to the Alarms and Performance
Events Reference.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
Forced switching is not released.
The protection board works abnormally.
Figure 10-11 Fault handling flow when automatic switching by board-level protection fails
Start
End
Perform forced
switching
Contact Huawei
engineers
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. Select the NE in the NE Explorer, and choose Configuration > Board-Level
Protection from the Function Tree.
b. Click Query in the interface, to query the values of all parameters of the protection
group.
c. Compare the values against the principles and requirements specified in
Dependency and Limitation and Parameters in the OptiX OSN 6800/3800 Feature
Descriptionto ensure that the parameters are configured properly.
Cause 2: Forced switching is not released.
a. In the window, click Query to check the Switching Status parameter of the
protection group.
b. If Switching Status is displayed as Forced Switch Request, right-click the
protection group, and then choose Clear from the shortcut menu to clear the locked
switching or forced switching configuration.
Cause 3: The protection board works abnormally.
a. In the window, click Query to check the parameter of the protection group.
b. If is displayed as Unusable, determine if the following alarms exist on the
relevant boards on the channels: HARD_BAD, BD_STATUS,
PORT_MODULE_OFFLINE, R_LOS, R_LOF. For more information, refer to the
Alarms and Performance Events Reference.
----End
Solution
If the problem persists after the above steps are performed and is Available, choose Forced
Switching to Protection to perform a forced switching on the protection group. Then, the
services are switched to the protection board and the services recover.
For more information regarding how to handle faults that have occurred on the working board,
refer to the Alarms and Performance Events Reference. If necessary, contact Huawei
engineers to resolve the problems.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
The NEs at both ends of the channel where the switching occurs may report the ODUKSP_PS
alarm or ODUKSP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The protection channel works abnormally.
Locked switching or forced switching is not released.
The parameters of the protection group are improperly configured.
The SD Switching is set to Disabled.
The protection protocol is not started.
The fibers are improperly connected to the corresponding boards.
Figure 10-12 Fault handling flow when automatic switching by ODUk SPRing protection fails
Start
No No
Do Are the
No Yes
the parameter Modify the services switched to
values comply with parameters. the protection
the specifications? channel?
Yes No
No No
No
Yes
Yes No
End
Perform manual
Handle the faults on the Contact Huawei
switching or forced
switching. working channel. engineers.
Procedure
Cause 1: The protection channel works abnormally.
a. In the Channel Mapping Relation interface, click Query to query the Channel
Status parameter of the protection channel.
b. If Channel Status is displayed as SD, SF, check whether the following alarms in
trigger conditions exist on the relevant boards on the protection channel. For the
method of handling the alarms, see the Alarms and Performance Events Reference.
Cause 2: Locked switching or forced switching is not released.
a. In the ODUk SPRing interface, click Query to query the Switching Request-East
or Switching Request-West parameter of the protection group.
b. If Switching Request-West or Switching Request-East is displayed as Locked or
Forced Switching - Ring, right-click the protection group, and then choose Clear
from the shortcut menu, to clear the locked or forced switching configuration.
Cause 3: The parameters of the protection group are improperly configured.
a. Select the NE in the NE Explorer, and choose Configuration > ODUk SPRing
from the Function Tree.
b. Click Query in the interface, to query the values of all parameters of the protection
group.
c. Check whether Span ID has been set correctly.
For example, if services are added/dropped at sites A and B and site B is east to site
A, then the span ID for the west working unit of site B must be the same as the span
ID for the east working unit of site A.
d. Compare the values against the principles and requirements specified in
Dependencies and Limitations and Parameters in the Feature Description to check
and ensure that the other parameters are configured properly.
Cause 4: SD Switching has been set to Disabled.
a. Click Query to query the SD Switching parameter of the protection group.
If SD Switching has been set to Disabled, services cannot be switched to the
protection channel when an OTUk_EXC, ODUk_TCM6_DEG, or
ODUk_TCM6_EXC alarm is generated on the working channel.
b. Set SD Switching to Enabled.
Cause 5: The protection protocol is not started.
a. Click Query to query the Switching Request-East or Switching Request-West
parameter of the protection group.
If the protection protocol has not started, Switching Request-East or Switching
Request-West is displayed as Unknown.
b. Select the protection group and click Start Protocol.
Cause 6: The fibers are improperly connected to the corresponding boards.
a. Refer to the protection principle in Principles. Check if the fiber connections are
correct on the optical interfaces of the east and west working channels and
protection channels of the line boards at the stations on the two ends.
----End
Solution
If the preceding measures are not successful in switching the services to the protection
channel, contact Huawei engineers to resolve the problem.
Fault Description
In normal operation of a network, the working channel has generated trigger conditions for
protection switching, but services cannot be automatically switched to the protection channel.
As a result, services are interrupted.
DCP board may report OWSP_PS alarm or OWSP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic switching failure are as follows:
The parameters of the protection group are improperly configured.
The protection protocol is not started.
Locked switching or forced switching is not released.
The fibers are improperly connected to the corresponding boards.
The protection channel works abnormally.
Figure 10-13 Fault handling flow when automatic switching by OWSP protection fails
Start
Do Are the
No Yes
the parameter Modify the services switched to
values comply with the parameters. the protection
specifications?
channel?
Yes No
Yes No
No No
Yes No
Yes No
End
Perform a manual
or forced switching.
Contact Huawei
engineers.
Procedure
Cause 1: The parameters of the protection group are improperly configured.
a. Select the NE in the NE Explorer, and choose Configuration > Optical
Wavelength Shared Protection from the Function Tree. Click OWSP Protection
tab.
b. Click Query in the OWSP Protection interface, to query the values of all
parameters of the protection group.
c. Compare the values against the principles and requirements specified in
Dependencies and Limitations and Parameters in the Feature Description to check
and ensure that the parameters are configured properly.
Cause 2: The protection protocol is not started.
a. In the OWSP Protection interface, select the protection group and click Start
Protocol.
Cause 3: Locked switching or forced switching is not released.
a. In the OWSP Protection interface, click Query to query the or parameter of
the protection group.
b. If or is displayed as Locked or Forced Switching - Ring, right-click the
protection group, and then choose Clear from the shortcut menu, to clear the locked
or forced switching configuration.
Cause 4: The fibers are improperly connected to the corresponding boards.
a. Refer to the protection principle in Principles. Check if the fiber connections are
correct on the optical interfaces of the east and west working channels and
protection channels of the DCP boards at the stations on the two ends.
Cause 5: The protection channel works abnormally.
a. In the OWSP Protection interface, click Query to query the Channel Status
parameter of the protection channel.
b. If Channel Status is displayed as SD, SF, check whether the following alarms exist
on the relevant boards on the protection channel: MUT_LOS, R_LOS, R_LOC,
R_LOF, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, OTUk_TIM, ODUk_PM_TIM,
ODUk_LOFLOM, IN_PWR_HIGH, IN_PWR_LOW, B1_EXC, ODUk_PM_DEG,
ODUk_PM_EXC, OTUk_DEG, OTUk_EXC. For the method of handling the
alarms, see the Alarms and Performance Events Reference.
If the Channel Status parameter of the protection channel is displayed as SD, SF, it is indicated that
faults have occurred in both the working and protection channels.
----End
Solution
If the preceding measures fail to switch services to the protection channel, and Protection
Channel Status is displayed as Normal, you need to perform a forced switching to switch the
services to the protection channel, which eventually restores the services.
Handle the faults in the working channel to clear the alarms and performance events reported
on the NE. If the alarms or performance events persist, contact Huawei engineers.
Background Information
The OptiX OSN 8800 and 6800 support protection for inter-subrack communication.
Symptom
During normal network operations, the communication between master and slave subracks is
interrupted, and services do not automatically switch to the standby route.
System Impact
When inter-subrack communication protection fails to automatically switch, the U2000
cannot reach the slave subracks. The services on the equipment, however, are unaffected.
Possible Causes
Cause 1: The protection network cable is loosely connected or is malfunctioning.
Procedure
Cause 1: The protection network cable is loosely connected or is malfunctioning.
a. Securely attach the protection network cable.
b. Replace the protection network cable.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled
MC-A25 The System Indicates that the Channel Number Is Illegal
MC-A38 The Service Is Interrupted After the Protection Is Triggered
MC-A41 Unsuccessful 1: N Protection Subnet Search
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
The OLP board may be reporting an OLP_PS or OLP_STA_INDI alarm.
Possible Causes
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive
Cause 2: The working channel works abnormally or failure has not been resolved.
Cause 3: Locked or forced switching commands have been manually issued.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Troubleshooting Workflow
The following figure illustrates the optical line protection automatic reverting failure
troubleshooting process.
Figure 11-1 Optical line protection automatic reverting failure troubleshooting flowchart
Start
Is Are the
No Set Yes
Revertive Mode set to services switched to
Revertive Mode
Revertive? the working
to Revertive. channel ?
Yes No
Are the
No Yes
Does the working Handle the faults on the services switched to
channel work normally? working channel. the working
channel ?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time.
channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, select one protection group and click Modify to
change Revertive Mode to Revertive.
Cause 2: The working channel is working abnormally.
a. In the Port Protection window, click Query to query the Working Channel
Status parameter of the protection group.
b. If Working Channel Status is not Normal, check whether MUT_LOS and
POWER_DIFF_OVER alarms are being reported on the corresponding boards on
the working channel, clear the alarms.
Cause 3: Locked or forced switching commands have been manually issued.
a. In the Port Protection interface, click Query to check the Switching Status
parameter of the protection group.
b. If Switching Status is displayed as Lock or Force to Protection Channel,
right-click the protection group, and choose Clear from the shortcut menu to clear
the switching configuration.
Cause 4: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the Port Protection window, click Query to check the WTR Time.
b. If service fails to be restored to the working channel after the time specified by
WTR Time elapses, check whether the working channel is normal.
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
When the intra-board 1+1 protection is achieved using the OLP, DCP, or QCP boards, the
OLP, DCP, or QCP boards reports an INTRA_OTU_PS or INTRA_OTU_STA_INDI
alarm.
When the intra-board 1+1 protection is realized by dual fed and selective receiving OTU,
the OTU board may report the INTRA_OTU_PS alarm or INTRA_OTU_STA_INDI
alarm.
Possible Causes
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive. In the case of the intra-board 1+1 protection configured using an
OLP, DCP, or QCP boards, when the Detection Channel is configured, the Revertive
Mode parameter must be set to Non-Revertive. This is not considered as one of the
possible causes when the protection cannot be restored automatically.
Cause 2: The working channel works abnormally or failure has not been resolved.
Cause 3: Locked, or forced switching commands have been manually issued.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Troubleshooting Workflow
The following figure illustrates the intra-board 1+1 protection automatic reverting failure
troubleshooting process.
Figure 11-2 Intra-board 1+1 protection automatic reverting failure troubleshooting flowchart
Start
Is Are the
No Set Yes
Revertive Mode set to services switched to
Revertive Mode
Revertive? the working
to Revertive. channel ?
Yes No
Are the
No Yes
Does the working Handle the faults on the services switched to
channel work normally? working channel. the working
channel ?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time.
channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, select one protection group and click Modify to
change Revertive Mode to Revertive.
In the case of intra-board 1+1 protection configured using an OLP, DCPboards, when the Monitoring
Channel is configured, Revertive Mode can only be set to Non-Revertive.
Cause 2: The working channel works abnormally or failure has not been resolved.
a. In the Port Protection interface, click Query to query the Working Channel
Status parameter of the protection group.
b. If Working Channel Status is not Normal, check whether R_LOS, R_LOF,
R_LOC, OTUk_LOF, OTUk_LOM, OTUk_AIS, ODUk_PM_AIS,
ODUk_PM_OCI, ODUk_PM_LCK, ODUk_LOFLOM, B1_EXC,
ODUk_PM_DEG, ODUk_PM_EXC, POWER_DIFF_OVER, IN_PWR_HIGH and
IN_PWR_LOW alarms are being reported on the corresponding boards on the
working channel, clear the alarms.
Cause 3: Forced switching commands have been manually issued.
a. In the Port Protection interface, click Query to check the Switching Status
parameter of the protection group.
b. If Switching Status is displayed as Lock or Force to Protection Channel,
right-click the protection group, and choose Clear from the shortcut menu to clear
the switching configuration.
Cause 4: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the Port Protection window, click Query to check the WTR Time.
b. If service fails to be restored to the working channel after the time specified by
WTR Time elapses, check whether the working channel is normal.
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
The DCP, OLP, or QCP boards may report a CLIENT_PORT_PS or
CLIENT_PORT_STA_INDI alarm.
If the protection is configured using the SCS board, the OTU or tributary board may
report the CLIENT_PORT_PS alarm or CLIENT_PORT_STA_INDI alarm.
Possible Causes
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
Cause 2: The working channel is faulty or a failure is still present.
Cause 3: Locked or forced switching commands have been manually issued.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Troubleshooting Workflow
The following figure illustrates the troubleshooting process of the client 1+1 protection
automatic reverting failure.
Figure 11-3 Troubleshooting flowchart of the client 1+1 protection automatic reverting failure
Start
Is Are the
No Set Yes
Revertive Mode set to services switched to
Revertive Mode
Revertive? the working
to Revertive. channel ?
Yes No
Are the
No Yes
Does the working Handle the faults on the services switched to
channel work normally? working channel. the working
channel ?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time.
channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. In the NE Explorer, click the NE and choose Configuration > Port Protection
from the Function Tree.
b. In the Port Protection window, select one protection group and click Modify to
change Revertive Mode to Revertive.
Cause 2: The working channel is faulty or a failure is still present.
a. In the Port Protection window, click Query to query the Working Channel
Status parameter of the protection group.
b. If Working Channel Status is not Normal, check whether the alarms listed in the
trigger conditions are being reported on the relevant boards on the working channel.
If the alarms are reported, clear them.
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
OTU board may report SW_SNCP_PS alarm or SW_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The value of the Revertive Mode parameter of the protection group has been set to
Non-Revertive.
The working channel works abnormally or failure has not been resolved.
Locked, or forced switching is not released.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-4 Fault handling flow when automatic switching back to the working channel by SW
SNCP protection fails
Start
Is Are the
No Set Yes
Revertive Mode set to services switched to
Revertive Mode
Revertive? the working
to Revertive. channel ?
Yes No
Are the
No Yes
Does the working Handle the faults on the services switched to
channel work normally? working channel. the working
channel ?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time.
channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree. Click the SNCP Service Control tab.
b. On the SNCP Service Control interface, select the desired protection group.
Double-click the Revertive Mode field, and then change Non-Revertive to
Revertive.
Cause 2: The working channel works abnormally or failure has not been resolved.
a. In the SNCP Service Control interface, click Query to query the Channel Status
parameter of the working cross-connection.
b. If Channel Status is not displayed as Normal, check whether the following alarms
of trigger conditions exist on the relevant boards on the working channel. For the
method of handling the alarms, see the Alarms and Performance Events Reference.
Cause 3: Locked, or forced switching is not released.
a. In the SNCP Service Control interface, click Query to check the Status parameter
of the protection group.
b. If Status is displayed as Lockout or Forced (from working to protection)
switching state, choose the protection group. Click Function and then choose
Clear from the shortcut menu to clear the switching configuration.
Cause 4: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the SNCP Service Control interface, click Query to check the WTR
Time(mm:ss).
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
Tributary, line or PID board may report an ODU_SNCP_PS alarm or
ODU_SNCP_STA_INDI alarm.
Possible Causes
Cause 1: The SNCP Type is inappropriate for the service scenario.
Cause 2: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
Cause 3: The working channel works abnormally or failure has not been resolved.
Cause 4: Locked or forced switching commands have been manually issued.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Troubleshooting Workflow
The following figure illustrates the ODUk SNCP protection automatic reverting failure
troubleshooting process.
Figure 11-5 ODUk SNCP protection automatic reverting failure troubleshooting flowchart
Start
No
Yes
No
Yes
No
No
No
No
Yes No
Contact Huawei
engineers. End
Procedure
Cause 1: The SNCP Type is inappropriate for the service scenario.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Then click the SNCP Service Control tab.
b. In the SNCP Service Control window, click Query to query the Protection Type
of the protection group. In the Operation Result dialog box, click Close.
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
L4G, TBE, LEM24, LEX4 board of OptiX OSN 6800/OptiX OSN 3800 may report
VLAN_SNCP_PS.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The value of the Revertive Mode parameter of the protection group has been set to
Non-Revertive.
The working channel works abnormally or failure has not been resolved.
Manual, locked or forced switching is not released.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-6 Fault handling flow when automatic switching back to the working channel by
VLAN SNCP protection fails
Start
Is Are the
No Set Yes
Revertive Mode set to services switched to
Revertive Mode
Revertive? the working
to Revertive. channel ?
Yes No
Are the
No Yes
Does the working Handle the faults on the services switched to
channel work normally? working channel. the working
channel ?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time.
channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. Select the desired Ethernet board in the NE Explorer, and choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree. Click the
VLAN SNCP Service Management tab.
b. On the VLAN SNCP Service Management interface, select the desired protection
group. Double-click the Revertive Mode field, and then change Non-Revertive to
Revertive.
Cause 2: The working channel works abnormally or failure has not been resolved.
a. In the VLAN SNCP Service Management interface, click Query to check the
Link Status parameter of the working service.
b. If Link Status is not displayed as Normal, check whether the following alarms
exist on the relevant boards on the working channel: R_LOF, R_LOS, R_OOF,
OTUk_LOF, OTUk_LOM, OTUk_AIS. For the method of handling the alarms, see
the Alarms and Performance Events Reference.
Cause 3: Manual, locked or forced switching is not released.
a. In the VLAN SNCP Service Management interface, click Set/Query Switching
and select Query Switching Status to check the Current Status parameter of the
protection group.
b. If Current Status is displayed as Manual (Active to Standby) Switching State,
Forced (Active to Standby) Switching State or Lockout State, click Set/Query
Switching. Then choose Clear from the shortcut menu, to clear the manual, locked
or forced switching configuration.
Cause 4: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the VLAN SNCP Service Management interface, click Query to check the
WTR Time (s).
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Symptom
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
Possible Causes
Cause 1: The SNCP Type is inappropriate for the service scenario.
Cause 2: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
Cause 3: The working channel works abnormally or failure has not been resolved.
Cause 4: Locked or forced switching commands have been manually issued.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-7 Tributary SNCP protection automatic reverting failure troubleshooting flowchart
Start
Is
the SNCP Type No Are the Yes
Change the SNCP
consistent with that required services switched to
in the service Type of the protection
group. the working
scenario? channel?
No
Yes
No
Yes
No
No
No
No
Yes No
Contact Huawei
engineers. End
Procedure
Cause 1: The SNCP Type is inappropriate for the service scenario.
a. In the NE Explorer, click the NE and choose Configuration > WDM Service
Management from the Function Tree. Then click the SNCP Service Control tab.
b. In the SNCP Service Control window, click Query to query Protection Type of
the protection group. In the Operation Result dialog box, click Close.
c. Refer to "Dependency and Limitation" and "Parameters" to check whether
Protection Type of the protection group is appropriate for the service scenario.
Cause 2: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. In the SNCP Service Control window, select the desired protection group.
Double-click the Revertive Mode field, and then change Non-Revertive to
Revertive.
Cause 3: The working channel works abnormally or failure has not been resolved.
a. In the SNCP Service Control window, click Query to check the Channel Status
parameter of the working cross-connection.
b. If Channel Status is SD or SF, check whether the alarms listed in Trigger
Conditions are being reported on the corresponding boards on the working channel,
clear the alarms.
Cause 4: Locked or forced switching commands have been manually issued.
a. In the SNCP Service Control interface, click Query to check the Status parameter
of the protection group.
b. If Status is displayed as Lockout or Forced (from working to protection)
switching state, choose the protection group. Click Function and then choose
Clear from the shortcut menu to clear the switching configuration.
Cause 5: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the SNCP Service Control window, click Query to check WTR Time.
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
SCC board may report MS_SNCP_PS alarm or MS_SNCP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The value of the Revertive Mode parameter of the protection group has been set to
Non-Revertive.
The working channel works abnormally or failure has not been resolved.
Locked switching or forced switching is not released.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-8 Fault handling flow when automatic switching back to the working channel by MS
SNCP protection fails
Start
Yes No
Are the
No Yes
Is Working Channel Handle the faults on the services switched to
Status Normal? working channel. the working
channel?
Yes No
No No
Are the
No Wait for a period Yes
Does the time exceed services switched to
longer than the working
WTR Time? WTR Time. channel?
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive.
a. Select the NE in the NE Explorer, and choose Configuration > WDM Service
Management from the Function Tree. Click SNCP Service Control tab.
b. On the SNCP Service Control interface, select the desired protection group.
Double-click the Revertive Mode field, and then change Non-Revertive to
Revertive.
Cause 2: The working channel works abnormally or failure has not been resolved.
a. In the SNCP Service Control interface, click Query to query the Channel Status
parameter of the working cross-connection.
b. If Channel Status is displayed as SD, SF check whether the following alarms exist
on the relevant boards: R_LOF, R_LOS, R_LOC, OTUk_LOF, OTUk_LOM,
OTUk_AIS, ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK,
ODUk_LOFLOM, REM_SF, B1_EXC, ODUk_PM_EXC, OTUk_EXC, REM_SD.
For the method of handling the alarms, see the Alarms and Performance Events
Reference.
Cause 3: Locked switching or forced switching is not released.
a. In the SNCP Service Control interface, click Query to query the Status parameter
of the protection group.
b. If Status is displayed as Lockout or Forced (from working to protection)
switching state , click Function, and then choose Clear from the shortcut menu, to
clear the manual, locked or forced switching configuration.
Cause 4: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the SNCP Service Control interface, click Query to query the WTR
Time(mm:ss).
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The value of the Revertive Mode parameter of the protection group has been set to
Non-Revertive.
The working channel works abnormally or failure has not been resolved.
Figure 11-9 Fault handling flow when automatic switching back to the working channel by
DLAG protection fails
Start
Yes No
Yes No
Contact Huawei
engineers. End
Procedure
Cause 1: The value of the Revertive Mode parameter of the protection group has been
set to Non-Revertive
a. Select the NE in the NE Explorer and then choose Configuration > Ethernet
Distributed Link Aggregation Management.
b. Click Query. Double-click Revertive Mode parameter and choose Revertive from
the drop-down list.
Cause 2: The working channel works abnormally or failure has not been resolved.
a. Resolve the problems with the working channel. Determine if the following alarms
exist on the relevant boards: HARD_BAD, PORT_MODULE_OFFLINE,
LINK_ERR, R_LOS, R_LOF. For more information regarding how to clear the
alarms, see the Alarms and Performance Events Reference.
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
The NEs at both ends of the channel where the switching occurs may report the ODUKSP_PS
alarm or ODUKSP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The working channel works abnormally or failure has not been resolved.
Manual switching, locked switching or forced switching is not released.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-10 Fault handling flow when automatic switching back to the working channel by
ODUk SPRing protection fails
Start
Yes No
No No
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The working channel works abnormally or failure has not been resolved.
a. Select the NE in the NE Explorer, and choose Configuration > ODUk SPRing
from the Function Tree.
b. In the Channel Mapping Relation interface, click Query to query the Channel
Status parameter of the working channel.
c. If Channel Status is displayed as SD, SF, check whether the following alarms in
trigger conditions exist on the relevant boards on the working channel. For the
method of handling the alarms, see the Alarms and Performance Events Reference.
Cause 2: Locked switching or forced switching is not released.
a. In the ODUk SPRing interface, click Query to query the Switching Request-East
or Switching Request-West parameter of the protection group.
b. If Switching Request-East or Switching Request-West is displayed as Forced
Switching-Ring, or Locked, right-click the protection group, and then choose
Clear from the shortcut menu, to clear the manual, locked or force switching
configuration.
Cause 3: When the working channel is restored, services are restored to the working
channel after the time specified by WTR Time elapses.
a. In the ODUk SPRing window, click Query to view the WTR Time(mm:ss) value.
During the WTR time, the value of Switching Request-East or Switching
Request-West parameter should be WTR - Ring Switching. After the WTR time
elapses, the protection switching will automatically take place.
----End
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
Fault Description
In normal operation of a network, services are switched to the protection channel after the
working channel generates the protection trigger conditions. When the working channel is
restored to normal, the services cannot be automatically switched back to the working
channel.
DCP board may report OWSP_PS alarm or OWSP_STA_INDI alarm.
Possible Causes
The possible causes of the automatic reverting failure are as follows:
The working channel works abnormally or failure has not been resolved.
Locked switching or forced switching is not released.
Cause 4: When the working channel is restored, service are restored to the working
channel after the time specified by WTR Time elapses.
Figure 11-11 Fault handling flow when automatic switching back to the working channel by
OWSP protection fails
Start
No
Yes
No
No
No
Yes
Procedure
Cause 1: The working channel works abnormally or failure has not been resolved.
a. Select the NE in the NE Explorer, and choose Configuration > Optical
Wavelength Shared Protection from the Function Tree. Click OWSP Protection
tab.
b. In the Channel interface, click Query to query the Channel Status parameter of
the working channel.
c. If Channel Status is displayed as SD, SF, check whether the following alarms exist
on the relevant boards on the working channel: MUT_LOS, R_LOS, R_LOC,
Solution
If the preceding measures fail to switch services to the working channel, contact Huawei
engineers to resolve the problem.
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
MC-A23 When the OTU Board Accesses Light, the Laser at Output End is Disabled
MC-A25 The System Indicates that the Channel Number Is Illegal
MC-A38 The Service Is Interrupted After the Protection Is Triggered
MC-A41 Unsuccessful 1: N Protection Subnet Search
MC-A91 Creation of Intra-Board Wavelength Protection on the LDG Fails
MC-A94 The WXCP Protection Configured for the LOG Board Is Invalid
MC-A98 The Protection Switching Times Out Severely
MC-A127 WXCP Protection Cannot Be Implemented Due To Wrong Configuration of
the LQG Boards
MC-A133 In a WDM System with 1:N Optical Channel Protection, the R_LOF Alarm Is
Reported in the Receive Direction on the Client Side When the Laser on the LWC1
Board in the Protection Channel Is Open
MC-A139 Automatic Switching Is Caused by the Incorrect Service Configuration of
ODUk SPRing Protection
MC-A150 How Signals Are Selected When the DCP Board Is Used
Symptom
During normal network operations, when a fiber cut occurs, and the intelligent power
adjustment (IPA) function may fail to start. As a result, the OAs at both ends of the optical
fiber fail to automatically shut down the lasers on the output optical ports.
Possible Causes
Cause 1: The IPA function is disabled.
Cause 2: The fault is resolved before the time specified by Start Hold-off Time elapses.
Cause 3: The IPA protection group is configured with auxiliary detection boards. When a
fiber cut occurs, some of the auxiliary detection boards do not report any alarm.
Cause 4: The IPA protection group is configured with auxiliary detection boards.
However, the auxiliary detection board ports are incorrectly set.
Troubleshooting Workflow
Figure 12-1 illustrates the IPA start failure troubleshooting process.
Start
No Yes
Is IPA Status set to
Set IPA Status to Enabled. Is IPA started?
Enabled?
No
Yes
No
Yes
Yes No
No
Yes
Contact Huawei
engineers.
End
Procedure
Cause 1: The IPA function is disabled.
a. In the NE Explorer, select the NE and choose Configuration > IPA Management.
Click Query to check the IPA Status of IPA.
b. If IPA Status is set to Disabled, change it to Enabled. Click Apply.
c. Query the IPA Status of the NE at the opposite end. Ensure that the IPA function
of the NEs at the two ends of the line is set to Enabled.
Cause 2: The fault is resolved before the time specified by Start Hold-off Time elapses.
In case of a fiber cut, the IPA function is enabled only after the start hold-off time
expires.
a. In the IPA Management window, click Set Start Delay. In the dialog box that is
displayed, click Query to query the Start Hold-off Time.
b. Check whether the fault is resolved before the time specified by Start Hold-off
Time elapses.
Cause 3: The IPA protection group is configured with auxiliary detection boards. When a
fiber cut occurs, some of the auxiliary detection boards do not report any alarm.
a. Check whether each auxiliary detection board is reporting IPA-triggering alarms,
such as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards
are not reporting such alarms, check whether the fiber connection between the OA
board and the FIU, and that between the FIU and the auxiliary detection board,
comply with the engineering design.
Cause 4: The IPA protection group is configured with auxiliary detection boards.
However, the auxiliary detection board ports are incorrectly set.
a. Check whether the auxiliary detection board ports are receiving optical signals from
the same direction as the detection board ports. If they are not receiving optical
ports, re-set the auxiliary detection board ports.
----End
Solution
If the problem persists after you take the preceding measures, handle the alarms and faults of
the NE, and contact Huawei technical support for resolving the IPA start failure.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function starts. The lasers
on the output optical ports of the OAs at the upstream station of the optical fiber are
automatically shut down. After the optical fiber is restored, the IPA function does not
automatically turn the lasers on the output optical ports back on. As a result, the output optical
power of the OAs is not restored.
Possible Causes
Cause 1: When the IPA protection group is not configured with any detection board and
is configured with only auxiliary detection boards, all the auxiliary detection boards are
reporting IPA-triggering alarms.
Cause 2: One or more of IPA function parameters are incorrectly set.
Troubleshooting Workflow
Figure 12-2 illustrates the IPA end failure troubleshooting process.
Start
No
Yes
No Yes
Do the parameter values Are the services
comply with the Modify the parameters.
restored?
specifications?
No
Yes
Yes
Yes
Contact Huawei
End
engineers.
Procedure
Cause 1: When the IPA protection group is not configured with any detection board and
is configured with only auxiliary detection boards, all the auxiliary detection boards are
reporting IPA-triggering alarms.
a. Check whether each auxiliary detection board is reporting IPA-triggering alarms,
such as R_LOS, R_LOF, and OSC_RDI. If any of these alarms is being reported,
check the fiber connection of each auxiliary detection board.
b. If the fiber connection of each auxiliary detection board is normal, check whether
one of the auxiliary detection boards is faulty.
Cause 2: One or more of IPA function parameters are incorrectly set.
a. In the NE Explorer, click the NE and choose Configuration > IPA Management.
b. In the IPA Management window, click Query and check whether the IPA
parameters are correctly set. For more information about how to set each parameter,
refer to "Dependency and Limitation" and "Parameters".
Check whether the Off Period, On Period, and Start Test Duration values of the two jointly used
IPA pairs are the same.
Check whether the On Period value of the two IPA pairs is the same as the recommended value
calculated based on the number of intermediate stations.
----End
Solution
If the problem persists after you take the preceding measures, disable the IPA function by
setting the IPA Status in the IPA Management window to Disabled. In the WDM interface
window of the corresponding board, confirm that Laser Status of the transmit optical port of
Laser Control Board is set to On.
Check whether the services are restored. If services are not restored, query the alarms of the
NE and clear the alarms and faults of the NE. If the services are still not restored, contact
Huawei technical support for resolving the IPA end failure.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function fails to start. As
a result, the OAs at both ends of the optical fiber fail to automatically shut down the lasers on
the output optical ports.
Possible Causes
The IPA function is disabled.
The fault is resolved before the time specified by Start Hold-off Time (ms) elapses.
The communication between the case-shape Raman pump amplifier unit for C-band
(CRPC) frame and the subrack is faulty.
The preset power threshold of the detection board is too low.
The preset power threshold of the Raman board is too low.
The IPA protection group is configured with auxiliary detection boards. When a fiber cut
occurs, some of the auxiliary detection boards do not report any alarm.
The IPA protection group is configured with auxiliary detection boards. However, the
auxiliary detection board ports are incorrectly set.
IPA parameters are incorrectly set.
Ensure that the optical fibers are properly connected and the configuration is correct.
When the RAU1 or RAU2 or SRAU board functions as the Raman amplifier,
The TN14FIU/TN16FIU and OSC boards function as the auxiliary detection boards to implement
IPA, you do not need to configure the detection board. In this case, IPA Detection Board Threshold
(dBm) cannot be set.
It does not support fiber-break detection and therefore the Raman Board Threshold (dBm) cannot
be set.
Troubleshooting Workflow
Figure 12-3 illustrates the IPA start failure in a Raman system troubleshooting process.
Start
No Yes
Is IPA Status set to Set IPA Status to
Enabled? Is IPA started?
Enabled.
Yes No
Yes No
Yes No
Yes
No Re-calculate and
Is the receive optical power change the threshold. Is IPA started?
of the Raman board lower
than the threshold? ?
Yes
Yes
Is the receive optical power No Re-calculate and
Is IPA started?
of the detection board lower change the threshold.
than the threshold? ?
Yes No
No Yes
Do all auxiliary detection Check the fiber connections
Are the line services
boards report IPA-triggering of the OA board.
restored?
alarms?
Yes No
Yes No
Yes No
Procedure
Cause 1: The IPA function is disabled.
a. In the NE Explorer, click the NE and choose Configuration > IPA Management.
Then click Query to query IPA Status.
b. If IPA Status is set to Disabled, change it to Enabled and click Apply.
c. Query IPA Status of the opposite NE. Ensure that IPA Status of the NEs at both
ends of the line is set to Enabled.
Cause 2: The fault is resolved before the time specified by Start Hold-off Time (ms)
elapses. After the fiber cut occurs, the IPA function is enabled only after the start hold-off
time elapses.
a. In the IPA Management window, click Set Start Delay. In the dialog box that is
displayed, click Query to query the Start Hold-off Time (ms).
b. Check whether the fault is resolved before the time specified by Start Hold-off
Time (ms) elapses.
Cause 3: The communication between the CRPC frame and the subrack is faulty.
a. On the U2000, check whether the CRPC board status is normal.
b. If the query fails, check whether the connectors and network cables are properly
installed.
Cause 4: The preset optical value of the detection board threshold is too low.
a. Test the actual receive optical power of the detection board, and compare the test
result with the value of the IPA parameter IPA Detection Board Threshold
(dBm).
b. If the actual receive optical power is higher than the value of Raman Board
Threshold (dBm), recalculate the Raman Board Threshold (dBm) value and
change it to a value higher than the actual receive optical power of the detection
board.
For the Raman Board Threshold (dBm) calculation method, refer to "Parameters".
c. If the actual receive optical power is higher than the value of IPA Detection Board
Threshold (dBm), recalculate the IPA Detection Board Threshold (dBm) value
and change it to a value higher than the actual receive optical power of the detection
board.
For the IPA Detection Board Threshold (dBm) calculation method, refer to "Parameters".
Cause 5: The preset value of the Raman board threshold is too low.
a. Test the actual receive optical power of the Raman board, and compare the test
result with the IPA parameter Raman Board Threshold (dBm).
b. If the actual receive optical power is lower than the Raman board threshold,
recalculate the Raman board threshold and change it to a value lower than the actual
receive optical power.
For the Raman Board Threshold (dBm) calculation method, refer to "Parameters".
Cause 6: The IPA protection group is configured with auxiliary detection boards. When a
fiber cut occurs, some of the auxiliary detection boards do not report any alarm.
a. Check whether each auxiliary detection board is reporting IPA-triggering alarms,
such as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards
are not reporting such alarms, check whether the fiber connection between the OA
board and the FIU, and that between FIU and the auxiliary detection board, comply
with the engineering design.
Cause 7: The IPA protection group is configured with auxiliary detection boards.
However, the auxiliary detection board ports are incorrectly set.
a. Check the auxiliary detection board ports are receiving optical signals from the
same direction as the detection board ports. If they are not receiving optical signals,
re-set the auxiliary detection board ports.
Cause 8: IPA parameters are incorrectly set.
a. In the IPA Management window, click Query and check whether IPA parameters
are correctly set. For more information about how to set each parameter, refer to
"Dependency and Limitation" and "Parameters".
Main IPA parameters include Detection Board, Laser Control Board, IPA Detection Board
Threshold (dBm), Raman Board Threshold (dBm), and Raman Board Alarm Reporting.
----End
Solution
If the problem persists after you take the preceding measures, clear the alarms and faults of
the NE. Contact Huawei technical support for resolving the IPA function failure.
Symptom
During normal network operations, when a fiber cut occurs, the IPA function starts. The lasers
on the output optical ports of the OAs at both ends of the optical fiber are automatically shut
down. After the optical fiber is restored, the IPA function does not automatically turn the
lasers on the output optical ports back on. As a result, the output optical power of the OAs is
not restored.
Possible Causes
When the IPA protection group is not configured with a Detection Board and is
configured with only auxiliary detection boards, all the auxiliary detection boards are
reporting IPA-triggering alarms.
The preset value of the Raman board threshold is too high.
The preset value of the detection board threshold is too high.
IPA parameters are incorrectly set.
The lasers on the local and remote Raman boards are not turned on manually within the
time specified by On Period (0.01s) or Start Test Duration (s).
When the RAU1 or RAU2 or SRAU board functions as the Raman amplifier,
The TN14FIU/TN16FIU and OSC boards function as the auxiliary detection boards to implement
IPA, you do not need to configure the detection board. In this case, IPA Detection Board Threshold
(dBm) cannot be set.
It does not support fiber-break detection and therefore the Raman Board Threshold (dBm) cannot
be set.
Troubleshooting Workflow
Figure 12-4 illustrates the IPA function failure in a Raman system troubleshooting process.
Start
No
No
No
Yes
No
Yes
No Yes
Do the other parameter Modify the Are the services
values comply with the parameters. restored?
specifications?
No
Yes
No
Yes
No
Are the services Query NE alarms and
restored? handle other faults.
Yes
End
Contact Huawei
engineers.
Procedure
Cause 1: When the IPA protection group is not configured with a Detection Board and is
configured with only auxiliary detection boards, all the auxiliary detection boards are
reporting IPA-triggering alarms.
a. Check whether each auxiliary detection board is reporting IPA-triggering alarms,
such as R_LOS, R_LOF, and OSC_RDI. If some of the auxiliary detection boards
are reporting such alarms, check the fiber connection of each auxiliary detection
board.
b. If the fiber connection of each auxiliary detection board is normal, check whether
one of the auxiliary detection boards is faulty.
Cause 2: The preset value of the Raman board threshold is too high.
a. Test the actual receive optical power of the Raman board, and compare the test
result with the IPA parameter Raman Board Threshold (dBm).
b. If the actual receive optical power is lower than the Raman board threshold,
recalculate the Raman board threshold and change it to a value lower than the actual
receive optical power.
For the Raman Board Threshold (dBm) calculation method, refer to "Parameters".
Cause 3: The preset value of the detection board threshold is too high.
a. Test the actual receive optical power of the detection board, and compare the test
result with the IPA parameter IPA Detection Board Threshold (dBm).
b. If the actual receive optical power is lower than the detection board threshold,
recalculate the detection board threshold and change it to a value lower than the
actual receive optical power.
For the IPA Detection Board Threshold (dBm) calculation method, refer to "Parameters".
Cause 4: IPA parameters are incorrectly set.
a. In the NE Explorer, click the NE and choose Configuration > IPA Management.
b. In the IPA Management window, click Query to check whether IPA parameters
are correctly set. For more information about how to set each parameter, refer to
"Dependency and Limitation" and "Parameters".
This operation applies only to the scenario where lasers need to be manually opened after Laser Restart
Mode is set to Manual.
If the CRPC03 and ROP board are involved in the IPA function, the laser on the CRPC03 and ROP
board need to be manually opened.
----End
Solution
If the problem persists after you take the preceding measures, set the IPA Status in the IPA
Management window to Disabled to disable the IPA function. In the WDM Interface
window of the corresponding board, confirm that the Laser Status of the transmit optical
interface of the laser control board is set to On.
Check whether the services are restored. If services have not been restored, query the alarms
of the NE and clear the alarms and faults of the NE. If the services are still not restored,
contact Huawei technical support for resolving the IPA function failure.
Symptom
During normal operations of an ALC-enabled network, the attenuation of a line section
changes and the ALC function does not start. As a result, all OAs at each downstream station
cannot make adjustments. This affects the system OSNR and service transmission.
Possible Causes
Cause 1: The ALC Automatic Regulation Switch is set to Disabled.
Cause 2: ALC stops abnormally due to other external causes. ALC nodes report the event
indicating that ALC has ended unexpectedly.
Cause 3: MUT_LOS or BD_STATUS alarms are being reported on the related board.
Cause 4: ALC parameters are configured incorrectly. Therefore, the consistency check
fails.
Troubleshooting Workflow
Figure 12-5 illustrates the ALC function failure troubleshooting process.
Start
Is Automatic No Yes
Regulation Switch Start ALC. Is ALC started?
set to Enabled ?
Yes No
Yes
No No
No Yes
Is the consistency check Check and modify
Is ALC started?
successful? ALC parameter values.
Yes No
Contact Huawei
End
engineers.
Procedure
Cause 1: The ALC Automatic Regulation Switch is set to Disabled.
a. Choose Configuration > WDM ALC Management from the Main Menu. In the
WDM ALC Management window that is displayed, click NG WDM Single
Station Configuration tab.
b. In the left-hand NE list, select the desired NE. Check whether the Automatic
Regulation Switch is set to Disabled. If it is disabled, enable ALC. For more
information, refer to "Starting Automatic Link Adjustment".
Cause 2: ALC stops abnormally due to other external causes. ALC nodes report the event
indicating that ALC has ended unexpectedly.
a. On the left of the WDM ALC Management window, query the ALC events
reported. Check whether there are events indicating that the ALC has ended
unexpectedly. If the ALC has ended unexpectedly, identify the reason.
Cause 3: MUT_LOS or BD_STATUS alarms are being reported on the related board.
Solution
If the problem persists after you take the preceding measures, query NE alarms and clear the
alarms and faults on the NE. Contact Huawei technical support for resolving ALC function
faults.
Background Information
The OptiX OSN 3800 does not support the APE function.
Fault Description
During normal operations on an APE-enabled network, the U2000 reports an optical power
equilibrium event and then starts APE adjustment. However, the system fails to automatically
adjust the optical power at the transmit end of each channel or report an event indicating that
APE has ended unexpectedly. In this case, the equilibrium of the receive-end optical power
and OSNR cannot be ensured.
If a fiber cut occurs along the line or communication is abnormal, handle the network faults.
If the U2000 reports both an ALC event and an optical power equilibrium event, start the ALC function.
If the optical power equilibrium event persists after the adjustment is completed, start the APE function.
Possible Causes
Cause 1: APE parameters are configured incorrectly.
Cause 2: The Optical Interface Attenuation Ratio of the APE power regulation unit
has reached a critical point and can no longer be adjusted. As a result, the adjustment
cannot be started.
Cause 3: Limited APE adjustment is performed and further adjustment is required.
Cause 4: The Standard Power Offset settings are insufficient to meet the requirements
of the live network.
Troubleshooting Workflow
Figure 12-6 illustrates the APE function exception troubleshooting process.
Start
No
Yes
No Yes
Do the APE parameter
Modify the parameters. Is optical power
values comply with the
adjusted?
specifications?
No
Yes
No
Yes
No Yes
Is the difference between
Restart APE. Is optical power
ActualPower Offset and Standard
adjusted?
Power Offset lower than the
threshold?
No
Yes
Yes
Re-calibrate the value of Is optical power
Standard Power Offset. adjusted?
No
Procedure
Cause 1: APE parameters are configured incorrectly.
a. In the NE Explorer, select the desired NE and choose Configuration > Optical
Power Equilibrium from the Function Tree.
b. Click Query to check whether APE parameters are configured correctly. For more
information about how to set each parameter, refer to "Dependency and Limitation
and Parameters".
Main APE parameters include Power Monitoring Unit, , , and Monitoring Flag of the related
wavelength.
Cause 2: The Optical Interface Attenuation Ratio of the APE power regulation unit
has reached a critical point and can no longer be adjusted. As a result, the adjustment
cannot be started.
a. In the NE Explorer, select the desired power regulation unit and choose
Configuration > WDM Interface to query the Optical Interface Attenuation
Ratio board parameter.
b. Check whether the Optical Interface Attenuation Ratio of each optical port where
the APE monitoring wavelength is located has reached the critical value and there is
no margin for adjustment.
c. If the Optical Interface Attenuation Ratio value has reached this point, adjust the
optical attenuation of the regulation unit at the upstream station, thereby decreasing
the optical attenuation required by the local station.
Cause 3: Insufficient APE adjustment has occurred and further adjustment is required.
a. In the NE Explorer, select the desired NE and choose Configuration > Optical
Power Equilibrium from the Function Tree.
b. Query the Actual Power Offset and Standard Power Offset of the APE
monitoring wavelength and the Power Unbalance Threshold.
c. If the maximum difference between Actual Power Offset and Standard Power
Offset in all monitoring wavelengths is less than 7 dB and Power Unbalance
Threshold uses the default value (1.5), start the APE function again.
d. If the maximum difference between Actual Power Offset and Standard Power
Offset in all monitoring wavelengths is greater than 7 dB and Power Unbalance
Threshold uses the default value (1.5), increase the value of Power Unbalance
Threshold and start the APE function again.
Solution
If the problem persists after you take the preceding measures, contact Huawei technical
support for resolving the APE function faults.
Fault Description
After the optical cross-connections in automatic mode are configured, the optical path is
unavailable.
Possible Causes
Cause 1: The rated optical power of the OA board is set incorrectly, and thus the NE
reports the OPA_FAIL_INDI alarm.
Cause 2: The optical power budget is insufficient, and thus the NE reports the
OPA_FAIL_INDI alarm.
Procedure
Cause 1: The rated optical power of the OA board is set incorrectly, and thus the NE
reports the OPA_FAIL_INDI alarm.
a. In Explorer, choose the desired OA board.
b. In Function Tree on the left side, choose Configuration > WDM Interface and
then select Advanced Attributes.
c. Double-click the Rated Optical Power (dBm) fields of the input and output
interfaces, and modify the values.
Cause 2: The optical power budget is insufficient, and thus the NE reports the
OPA_FAIL_INDI alarm.
a. Adjust the system optical power budget, which is insufficient.
----End
Solution
After the above steps are performed, contact Huawei engineers to remove the faults in the
OPA function.
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
MC-A8 The TN11OAU101 at the Transmit End Reports the MUT_LOS Alarm
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
MC-A77 Improper Configuration of Protocol Channels Results in a Failure of the ALC
to Start
MC-A81 The Created ALC Link on OptiX OSN 6800 Cannot Be Automatically
Adjusted
MC-A121 The T2000 Reports a Failure In Querying the ALC Link Status Because Of
Too Many NEs On the Link
MC-A169 T2000 Reports Errors After the Standard Optical Power of Single Wavelength
Is Set to 7 dBm with ALC in Power Reference Mode
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
MC-A78 When the IPA Is Set or Deleted, the OAU Alarm Threshold Changes Due to
Version Features
MC-A116 Failure in Configuring the SC2 as an Auxiliary Detection Board in the IPA
Protection Group
MC-A175 How to Clear the LASER_HAZARD_WARNING Alarms Reported on
Certain OBU and OAU Boards After an Upgrade of Software
The following cases are the cases relevant to the OptiX WDM product series.
Related Cases:
MC-A116 Failure in Configuring the SC2 as an Auxiliary Detection Board in the IPA
Protection Group
13 Ethernet Problems
Symptom
Services are degraded.
System Impact
Services are affected.
Possible Causes
Cause 1: The bandwidth is insufficient for heavy traffic or the bandwidth is sufficient but
the burst traffic is excessive.
Cause 2: There is a fault at the physical layer.
Troubleshooting Workflow
Figure 13-1 illustrates the Ethernet service degradation troubleshooting process.
Start
No No
No No
Yes Yes
The setting of a port attribute of Modify the Are services
the local equipment is different
from that of the opposite
mismatched setting. restored?
equipment.
No No
Yes Yes
Is there a fault at the Check for alarms and Are services
physical layer? handle them. restored?
No No
Contact Huawei
engineers. End
Procedure
Cause 1: The bandwidth is insufficient for heavy traffic or the bandwidth is sufficient but
the burst traffic is excessive.
a. Check for RMON performance events of the corresponding NE and handle them.
For information about how to handle RMON performance events, refer to the
Alarms and Performance Events Reference.
Cause 2: There is a fault at the physical layer.
a. Check for alarms. If an ETH_8B10B_ERR alarm is being reported, handle this
alarm.
----End
Symptom
The test frame cannot function normally.
System Impact
None.
Possible Cause
Cause 1: The timeslots in the cross-connection services of the interconnected ends are
inconsistent.
Cause 2: The bearing modes of the VC trunk ports at the two interconnected ends are
inconsistent.
Cause 3: The logic port on which the function of test frame is enabled is not bound with
timeslots.
Procedure
Cause 1: The timeslots in the cross-connection services of the interconnected ends are
inconsistent.
a. Check whether the timeslots in the cross-connection services of the interconnected
ends are consistent. If they are inconsistent, set them to the same.
Cause 2: The bearing modes of the VC trunk ports at the two interconnected ends are
inconsistent.
a. Check whether the bearing modes of the VC trunk ports at the two interconnected
ends are consistent. If they are inconsistent, set them to the same.
Cause 3: The logic port on which the function of test frame is enabled is not bound with
timeslots.
a. Check whether the logic port on which the function of test frame is enabled is
bound with timeslots.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
ALM_DATA_RLOS Alarms Transiently
MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER
Alarm
MC-A96 Packet Loss Occurs in Ethernet Service Testing of the L4G Board
MC-A117 Analysis and Handling of the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Reported by the LBE
MC-A158 How to Use the Ethernet Test Frames on the OptiX OSN 6800
MC-A219 EPL Service Is Interrupted Due to Mismatched Service Modes of the L4G
Boards, Sites Report The R_LOF, ODU5G_PM_AIS, OTU5G_LOF And LINK_ERR
Alarms
MC-A281 Service Interruption Occurs Because of the Data Board LAG Configuration
on the OptiX OSN 6800 Equipment Mismatches the LAG Configuration on the Router
14 ECC Problems
Symptom
The services on the main optical path are normal, but ECC communication is interrupted and
the NE cannot be reached by the U2000.
System Impact
The U2000 cannot reach the NE.
Possible Causes
Cause 1: The ID of the NE is a duplicate of another NE.
Procedure
Cause 1: The ID of the NE is a duplicate of another NE.
a. Log in to the NE on the WEB LCT and modify the NE ID of the NE according to
the record.
Cause 2: The pigtail connected to the OSC board is faulty.
a. Check the pigtail connected to the OSC board on the first faulty NE along the signal
flow. If the pigtail is loose, secure it; if it is dirty, clean it; if it is faulty, replace it.
b. Ensure that the pigtail is properly connected to the OSC board on the faulty NE.
During deployment commissioning, the pigtail might be incorrectly connected because the FIU board
and the OSC board have many ports marked with similar names. During commissioning, to prevent
incorrect pigtail connections in one direction of the OSC board, you can connect an optical attenuator
between the currently unused RM and TM optical ports in the other direction of the OSC board to form a
self-loop.
Cause 3: The system control board is faulty.
a. Reset the system control board on the faulty NE along the signal flow, and then
check whether you can log in to the NE.
b. If you cannot log in to the NE, remove the system control board on the faulty NE so
the ECC signals pass through the backplane. Then check whether the downstream
NE is restored. If the downstream NE is restored, the system control board is faulty.
Replace the system control board.
Cause 4: The OSC board is faulty.
a. Replace the OSC board on the first faulty NE along the signal flow, and check
whether the network is restored. If the network is restored, the OSC board is faulty.
Replace the OSC board.
Cause 5: The OTU or tributary or line board is faulty.
a. Replace the OTU, or tributary or line board on the first faulty NE along the signal
flow, and check whether the network is restored. If the network is restored, the
OTU, or tributary or line board is faulty. Replace the OTU, or tributary or line
board.
Cause 6: Coherent and non-coherent boards are interconnected.
a. The DCN bytes are defined differently for coherent and non-coherent services, so
the two types of services cannot be interconnected. If DCN channels are unavailable,
check whether the interconnected boards are coherent boards.
----End
Symptom
The ECC communication is intermittent, and the U2000 is frequently unable to reach the NE.
System Impact
The U2000 cannot reach the NE.
Possible Causes
Cause 1: Clock tracing is set incorrectly.
Cause 2: There are bit errors on the signal transmission.
Procedure
Cause 1: Clock tracing is set incorrectly.
a. Set clock tracing to the correct source. For details on how to set the correct clock
tracing, see "Synchronization".
All equipment on the network must trace the same clock source. In the case of WDM equipment, the
internal clock source of a specific NE should be given the highest priority, and the other NEs trace the
internal clock source of this NE. (In the case of chain networking, the internal clock source of a terminal
NE rather than an intermediate NE should be set as the clock source so it can be traced network-wide.)
Cause 2: There are bit errors on the signal transmission.
a. Refer to 7 Bit Errors.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A22 NE ESC Communication Interrupted Because of the Closure of the OTU Laser
15 Clock Problems
Symptom
After a fiber fault is rectified, the delay is not compensated. As a result, the downstream
NodeBs cannot trace the clock signals.
Impact on System
If protection is configured, the IEEE 1588v2 clock signals are switched from the working path
to the protection path. If no protection is configured, the IEEE 1588v2 clock signals are
interrupted and the downstream NodeBs cannot perform clock synchronization.
Figure 15-1 Networking diagram of the ring network configured with protection
NE1 NE2
East West
West East
NE4 NE3 NE5
OptiX PTN
BITS OptiX OSN equipment equipment NodeB
used on a ring network configured with protection to compensate for the delay on the faulty
fiber.
Symptom
In the case of a clock processing failure, the EXT_TIME_LOC, SYNC_C_LOS,
S1_SYN_CHANGE, LTI, SYN_BAD, EXT_SYNC_LOS, or CLK_NO_TRACE_MODE
alarm occurs.
When you clear the alarm reported by the equipment, the fault is rectified.
Impact on System
When the clock source of the network is lost or degrades, the services that trace the clock
source are affected. In this case, pointer justification occurs and BER increases.
Possible Causes
Cause 1: In the priority table, the synchronous time source for the service board is lost.
Cause 2: The synchronous clock source is lost and the clock of the NE is in an abnormal
state.
Cause 3: In SSM mode, the clock source is switched and the clock source traced by the
NE is also switched.
Cause 4: The signals of the synchronous clock source are degraded.
Cause 5: The external clock source is lost.
Cause 6: The clock enters the non-tracing working mode.
Procedure
Cause 1: In the priority table, the synchronous time source for the service board is lost.
a. Check for the SYNC_C_LOS alarm of the STG board on U2000. For details, refer
to "Querying the Current Alarms and Performance Events of a Component on the
U2000" in Supporting Tasks.
b. If the SYNC_C_LOS alarm occurs, handle the alarm according to the Alarms and
Performance Events Reference.
Cause 2: The synchronous clock source is lost and the clock of the NE is in an abnormal
state.
a. Check for the LTI alarm of the STG board on U2000. For details, refer to
"Querying the Current Alarms and Performance Events of a Component on the
U2000" in Supporting Tasks.
b. If the LTI alarm occurs, handle the alarm according to the Alarms and Performance
Events Reference.
Cause 3: In SSM mode, the clock source is switched and the clock source traced by the
NE is also switched.
a. Check for the S1_SYN_CHANGE alarm of the STG board on U2000. For details,
refer to "Querying the Current Alarms and Performance Events of a Component on
the U2000" in Supporting Tasks.
b. If the S1_SYN_CHANGE alarm occurs, handle the alarm according to the Alarms
and Performance Events Reference.
Cause 4: The signals of the synchronous clock source are degraded.
a. Check for the SYN_BAD alarm of the STG board on U2000. For details, refer to
"Querying the Current Alarms and Performance Events of a Component on the
U2000" in Supporting Tasks.
b. If the SYN_BAD alarm occurs, handle the alarm according to the Alarms and
Performance Events Reference.
Cause 5: The external clock source is lost.
a. Check for the EXT_SYNC_LOS alarm of the STG board on U2000. For details,
refer to "Querying the Current Alarms and Performance Events of a Component on
the U2000" in Supporting Tasks.
b. If the EXT_SYNC_LOS alarm occurs, handle the alarm according to the Alarms
and Performance Events Reference.
Cause 6: The clock enters the non-tracing working mode.
a. Check for the CLK_NO_TRACE_MODE alarm of the STG board on U2000. For
details, refer to "Querying the Current Alarms and Performance Events of a
Component on the U2000" in Supporting Tasks.
b. If the CLK_NO_TRACE_MODE alarm occurs, handle the alarm according to the
Alarms and Performance Events Reference.
----End
16 Orderwire Problems
Symptom
The services on the main optical path from station A to station C are normal, but the orderwire
is unavailable.
Figure 16-1 shows an example of the network configuration in this case.
OLA
OTM OTM
System Impact
The services are not affected.
Possible Causes
Cause 1: The parameters are incorrectly configured.
Cause 2: The setting of the phone set is incorrect.
Cause 3: The phone set or phone line is faulty.
Cause 4: The fiber connection of the SC2 board at station B is incorrect.
Cause 5: The system control board at station B is faulty.
Procedure
Cause 1: The parameters are incorrectly configured.
a. On the U2000, check the phone numbers of stations A and C. Ensure that each
phone number is correctly set to a unique value. For details, refer to "Configuring
Orderwire".
b. On the U2000, check the setting of the OSC boards at stations A, B, and C. Set
orderwire bytes to pass through each station; otherwise, the orderwire of station A
and that of station C are unavailable.
c. On the U2000, check the clock tracing settings of stations A and C. For details on
how to set the correct clock tracing, see "Setting the Priority List of Clock Sources"
or "Setting IEEE 1588v2" in the Configuration Guide.
Cause 2: The setting of the phone set is incorrect.
a. Check the port to which the phone set is connected and ensure that the interface is
correctly selected.
Generally, the orderwire phone line is inserted on the "PHONE1" port of the subrack.
b. Check whether the ringing current switch RING on the phone set is set to ON
(indicating that the phone rings when there is an incoming call).
c. Check whether the dialing mode switch is set to T (indicating the dual-tone
multifrequency (DTMF) dialing mode).
d. Check whether the called orderwire phone is on hook. If the red indicator in the
upper right corner on the front panel of the phone set is unlit, the phone set is on
hook. If the red indicator is lit, the phone set is not on hook. Press the "TALK"
button on the front panel of the phone set to hook it up.
Cause 3: The phone set or phone line is faulty.
a. Install a normal phone set at stations A and C and test the calling function of the
phone set. If the function is available, the original phone set is faulty.
b. Replace the phone line between the phone set and the equipment at stations A and C,
and test the calling function. If the function is available, the phone line is faulty.
Cause 4: The fiber connection of the SC2 board at station B is incorrect.
a. Along the signal flow, check the pigtail connected to the SC2 board at station B.
Ensure that the connection is correct.
Cause 5: The system control board at station B is faulty.
a. Remove the system control board at station B to make orderwire bytes pass through
station B. If the orderwire becomes available, the system control board is faulty.
Replace the system control board.
----End
Symptom
A called phone set in a conference call fails to exit the conference call state. That is, the called
phone set is still in the conference call state after being connected and then disconnected.
System Impact
The called phone set fails to exit the conference call state, and the orderwire is unavailable.
Possible Causes
Cause 1: During the conference call, the calling orderwire board of a certain phone set is
reset either due to an external cause or because the phone set was connected when
communication on the supervisory channel failed.
Procedure
Cause 1: During the conference call, the calling orderwire board of a certain phone set is
reset either due to an external cause or because the phone set was connected when
communication on the supervisory channel failed.
a. Leave the phone set in the connected state for two hours. The phone set will return
to the idle state two hours later.
b. Use an idle phone set to initiate a conference call. Then, connect this phone set,
causing all phone sets in orderwire communication with this phone set to exit the
conference call state.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A42 A Fault of the PMU for the OptiX BWS 1600G Results In an Orderwire
Ringing Failure
MC-A187 How to Change the IP Address of the OptiX OSN 1800 to the Default One
MC-A223 When a Self-Made Network Cable Is Used, the OptiX OSN 6800 Reports the
COMMUN_FAIL Alarm
MC-A224 The Network Cable at the COM Port on the EFI Board of the OptiX OSN
6800 Subrack Is Incorrectly Connected. Consequently, All the Boards on the OptiX OSN
6800 Subrack Report the COMMUN_FAIL Alarms
17 Interconnection Faults
Symptom
After a piece of WDM equipment is interconnected to a piece of data equipment, the two
pieces of equipment fail to communicate with each other and the equipment might report the
R_LOS, LINK_ERR and R_OOF alarms.
Impact on System
The two pieces of interconnected equipment fail to communicate with each other.
Possible Causes
Cause 1: The line between the WDM equipment and the data equipment is faulty.
Cause 2: The parameter configuration of interconnected board of the WDM equipment
on the client side is incorrect.
Cause 3: Either or both of the interconnected boards is/are faulty.
Procedure
Step 1 Cause 1: The line between the WDM equipment and the data equipment is faulty. In this case,
interconnected board of the WDM equipment may report the R_LOS, LINK_ERR alarms on
the client side.
1. Check whether the optical modules of the interconnected boards are of the same type. If
they are of the same type, check whether the supported transmission distance of the
optical modules is equal or longer than the actual distance away from the client side. The
single-mode optical module and the multimode optical module cannot be used together.
2. Check whether the fibers of the interconnected boards match each other. The
single-mode fiber and the multimode fiber cannot be used together.
Generally, the multimode fiber is nacarat-colored, and the single-mode fiber is yellow.
3. Check whether any fiber is inserted in an incorrect interface according to the fiber labels.
If any fiber is inserted in an incorrect interface, the equipment might not generate the
R_LOS alarm but generates a large number of performance events against anomalies. In
this case, insert the fiber in the correct interface.
4. Use an optical power meter to test the interconnect fiber jumper. If the fiber jumper is
abnormal, replace the fiber jumper. If the fiber jumper is good, check whether the optical
cable is faulty.
Step 2 Cause 2: The parameter configuration of interconnected board of the WDM equipment on the
client side is incorrect. In this case, interconnected board of the WDM equipment may report
R_LOS, LINK_ERR alarms on the client side.
1. In the case of the OTU board that can access various service data, check whether the
service type settings of the OTU board are different from those of the data equipment.
− On the interconnected board of the WDM equipment, query and set the client
service type of the board. Make sure that the service type of the WDM equipment is
the same as the interconnected data equipment.
2. Check whether the auto-negotiation modes or the service direction mode of the optical
interfaces on the interconnected boards are different from each other.
− Querying and Setting the Working Mode of the Ethernet Port. Make sure that the
auto-negotiation modes or the service direction mode are the same.
3. The Maximum Package Length of the optical interfaces on the interconnected boards
are different from each other.
− Log in to the U2000. In the NE Explorer interface, select the interconnected board.
− In Function Tree on the left side, choose Configuration > WDM Interface.
− Select Advanced Attributes, and click Query. Make sure that the Maximum
Package Length of the optical interfaces on the interconnected boards are same.
Symptom
After a piece of WDM equipment is interconnected to a piece of SDH equipment, the two
pieces of equipment fail to communicate with each other and the equipment might report the
R_LOS, R_LOF, and R_OOF alarms.
If the equipment reports the B1_EXC, B1_SD, B2_EXC, and B2_SD alarms, it indicates that
bit errors occur in the one of the two pieces of interconnected equipment. For details on how
to clear the fault, see Single-Channel Bit Errors.
Impact on System
The communication between the interconnected equipment is unavailable.
Possible Causes
Cause 1: The line between the WDM equipment and the SDH equipment is faulty.
Cause 2: The parameter configuration of interconnected board of the WDM equipment
on the client side is incorrect.
Cause 3: Either or both of the interconnected boards is/are faulty.
Procedure
Step 1 Cause 1: The line between the WDM equipment and the SDH equipment is faulty. In this case,
interconnected board of the WDM equipment may report the R_LOS and R_LOF alarms on
the client side.
1. Check whether the optical modules of the interconnected boards are of the same type. If
they are of the same type, check whether the supported transmission distance of the
optical modules is equal or longer than the actual distance away from the client side. The
single-mode optical module and the multimode optical module cannot be used together.
2. Check whether the fibers of the interconnected boards match each other. The
single-mode fiber and the multimode fiber cannot be used together.
Generally, the multimode fiber is nacarat-colored, and the single-mode fiber is yellow.
3. Check whether any fiber is inserted in an incorrect interface according to the fiber labels.
If any fiber is inserted in an incorrect interface, the equipment might not generate the
R_LOS alarm but generates a large number of performance events against anomalies. In
this case, insert the fiber in the correct interface.
4. Use an optical power meter to test the interconnect fiber jumper. If the fiber jumper is
abnormal, replace the fiber jumper. If the fiber jumper is good, check whether the optical
cable is faulty.
Step 2 Cause 2: The parameter configuration of interconnected board of the WDM equipment on the
client side is incorrect. In this case, interconnected board of the WDM equipment may report
R_OOF alarm on client side.
1. Check whether the service types of the interconnected boards mismatch each other.
− On the interconnected board of the WDM equipment, query and set the client
service type of the board. Make sure that the service type of the WDM equipment is
the same as the interconnected SDH equipment.
2. Check whether any interconnected interface is looped back.
− Log in to the U2000. In the NE Explorer interface, select the interconnected board.
− In Function Tree on the left side, choose Configuration > WDM Interface.
− Select Basic Attributes, and click Query. Check whether the optical interface on
the client side of each board is looped back. If yes, double-click the Loopback field.
In the drop-down list, select Non-Loopback and click Apply.
Step 3 Cause 3: Either or both of the interconnected boards is/are faulty.
1. At the optical interface on the client side of the interconnected board in the WDM
equipment, use the optical power meter to test the optical power. If the optical power is
abnormal, replace the board.
2. At the optical interface of the interconnected board in the SDH equipment, use the
optical power meter to test the optical power. If the optical power is abnorma l, replace
the board.
----End
Symptom
After local WDM equipment is interconnected with other OTN equipment, the two devices
fail to communicate with each other and the U2000 may report R_LOS, OTUk_LOF, and
OTUk_LOM alarms.
System Impact
Interconnected devices are unable to communicate with each other.
Possible Causes
Cause 1: The line between the local WDM equipment and the other OTN equipment is
faulty.
Cause 2: The client-side configuration for the interconnected board on the WDM
equipment is incorrect.
Cause 3: One or both of the interconnected boards is/are faulty.
Procedure
Step 1 Cause 1: The line between the local WDM equipment and the other OTN equipment is faulty.
In this case, the interconnected board on the WDM equipment may report the R_LOS alarm
on the client side.
1. Check whether the optical modules of the interconnected boards are of the same type. If
they are of the same type, check whether the supported transmission distance of the
optical modules is equal or longer than the actual distance away from the client side. The
single-mode optical module and the multimode optical module cannot be used together.
2. Check whether the optical fibers of the interconnected boards match each other. The
single-mode optical fiber and the multimode optical fiber cannot be used together.
Generally, the multimode optical fiber is nacarat, and the single-mode fiber is yellow.
3. Check whether any optical fiber is installed on an incorrect port according to the optical
fiber labels. If any optical fiber is installed on an incorrect port, the R_LOS alarm might
not be generated but a large number of performance events against anomalies may be
generated on the equipment. In this case, install the optical fiber on the correct port.
4. Use an optical power meter to test the pigtail interconnected with the equipment. If the
pigtail is abnormal, replace it. If it is normal, check whether the optical cable is faulty.
Step 2 Cause 2: The client-side configuration for the ports on the interconnected board of the WDM
equipment is incorrect. In this case, the interconnected board on the WDM equipment may
report the OTUk_LOF and OTUk_LOM alarms on the client side.
1. Check whether the service types, FEC mode, working modes, board mode of the
interconnected boards are inconsistent.
− Query and set the client service type of the interconnected board of the WDM
equipment. Ensure that the service type of the WDM equipment is the same as that
of the interconnected OTN equipment.
2. Check whether a loop is occurring on any interconnected port.
− Log in to the U2000. In NE Explorer, select the interconnected NE.
− Choose Configuration > WDM Interface from the Function Tree.
− On the Basic Attributes tab, click Query to check whether a loopback is enabled
on any optical port on the client side of each board. If a loopback is enabled,
double-click the Loopback field. In the drop-down list, select Non-Loopback and
click Apply.
Step 3 Cause 3: One or both of the interconnected boards is/are faulty.
1. Use the optical power meter to test the optical power of the client-side optical port on the
interconnected board of the WDM equipment. If the optical power is abnormal, replace
the board.
2. Use the optical power meter to test the optical power of the optical port on the
interconnected board of the OTN equipment. If the optical power is abnormal, replace
the board.
----End
The following cases are related to the OptiX WDM product series.
Related Cases:
MC-A4 The LOG Board Fails to Interwork With the FDG Board on the Client Sides.
The LOG board reports the R_LOS alarm on the client side. The FDG board reports the
LINK_STATUS alarm.
MC-A5 The LQG Board Reports the ALM_DATA_RLOS and ALM_DATA_TLOS
Alarms Transiently
MC-A6 The LDG Board Keeps Reporting the ALM_DATA_TLOS and
ALM_DATA_RLOS Alarms Transiently
MC-A11 The SSE3LWF Board Reports the OTU_LOF Alarm When Interworking with
the SSE1TMR
MC-A17 The LQG Reports ALM_DATA_RLOS and ALM_DATA_TLOS Alarms
MC-A21 An Interconnection Failure between the WDM and SDH Equipment
MC-A30 LDG Board of Metro 6100 Equipment Reports the INBADOCTS_OVER
Alarm
MC-A44 Bit Errors Generated in the Services, the Meter Reports the HP_RDI and
ERROR Alarms
MC-A49 An Incorrect Setting of CRC Results in an Interconnection Failure
MC-A67 The GE Port on the Client Side Reports LINK_DOWN Alarm
A.1 Overview
This topic provides remote maintenance overview.
The Huawei optical transmission equipment series supports remote maintenance. A remote
computer (remote end) can connect to an on-site U2000 server (local end) through a public
switched telephone network (PSTN) or through the Internet. The remote computer then can
perform maintenance to the equipment.
Figure A-1 is a networking diagram illustrating remote maintenance. A modem is installed at
the remote maintenance terminal and on the U2000 server, and dial-up programs are installed
at each end. These operations are performed during the U2000 installation.
serial
port Modem
PSTN/
Internet serial
Modem port
Remote
maintenance
ternimal
U2000
Server
WDM
network
During remote maintenance, the U2000 server needs to cooperate with the remote end to
perform the following operations:
Enable the remote maintenance user.
Establish the remote maintenance connection.
Prerequisites
You must be an NM user with "Network administrator" authority or higher.
Context
A remote maintenance user is the NM user who logs in to the U2000 server to maintain the
equipment. Remote maintenance users are in Disable status by default. You need to enable it
before you start the remote maintenance.
Procedure
Step 1 In the Main Menu choose System > Remote Maintenance User Management to display the
Remote Maintenance User Management dialog box.
Step 2 Set the Disable/Enable to be Enable. Set the other attributes of the remote user.
Step 3 Click Apply.
Step 4 Click OK to confirm the settings.
----End
Prerequisites
The communication connection between the remote maintenance terminal and the U2000
server must have been configured.
The remote maintenance user must have been enabled.
The user name and password of the U2000 server must be known to maintenance personnel at
the remote maintenance end.
Procedure
Step 1 On the U2000 server, query the connection status for remote maintenance. If the remote
maintenance connection is normal, go to step 5. If not, go to step 2.
The query methods are listed as follows.
If the Windows operating system is installed, right-click My Network Places and select
Properties to query the connection status for remote maintenance.
If the Solaris or Linux operating system is installed, open a terminal window and run the
ifconfig -a command to query the connection status for remote maintenance.
Step 2 Double-click the shortcut icon, which is created for dial-up connection, on the desktop, such
as Remote Maintenance to perform dial-up connection.
Step 3 Enter the user name (ppp_user) and password in the displayed dialog box.
Step 4 Enter the user name and password. Press the Enter key and click the D button at the right
bottom corner to establish the connection.
After you enter the password and press the Enter key, a line of illegal characters is displayed. This is
normal.
The address for dial-up access is IP address. If the dial-up connection of the server is disconnected,
re-dial to get a new IP address.
Step 6 Inform the maintenance personnel at the remote end of the queried IP address.
Step 7 Establish the dial-up connection between the remote maintenance personnel and the U2000
server. Log in to the U2000 client. After the login succeeds, you can perform the remote
maintenance.
To ensure network security, set the remote maintenance user to Disabled after the remote
maintenance.
----End
B Glossary
Numerics
3G See 3rd Generation.
3R reshaping, retiming, regenerating
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.
(QinQ) The 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
AA authentication authorization
AAA See Authentication, Authorization and Accounting.
AC alternating current
ACH associated channel header
ACK See acknowledgement.
ACL See access control list.
ACR allowed cell rate
ACS See Application Control Server.
ADC analog to digital converter
ADM add/drop multiplexer
frame. The basic function of ARP is to use the target equipment's IP address to
query its MAC address.
Advanced A carrier-class processing platform that is designed to meet the service application
Telecommunications requirement of high performance, high specialization, and high integration.
Application
Environment (ATAE)
Application Control A subsystem of the Media Entertainment Middleware (MEM), used for providing a
Server (ACS) service control interface for the Electronic Program Guide (EPG) server.
Authentication Header A protocol that provides connectionless integrity, data origin authentication, and
(AH) anti-replay protection for IP data.
Authentication, A mechanism for configuring authentication, authorization, and accounting security
Authorization and services. Authentication refers to the verification of user identities and the related
Accounting (AAA) network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
access control list A list of entities, together with their access rights, which are authorized to access a
(ACL) resource.
access key ID (AK) An ID that confirms the identity of a user accessing the object-based storage system.
One access key ID belongs to only one user, but one user can have multiple access
key IDs. The object-based storage system recognizes the users accessing the system
by their access key IDs.
acknowledgement A response sent by a receiver to indicate reception of information.
(ACK) Acknowledgements may be implemented at any level, including the physical level
(using voltage on one or more wires to coordinate a transfer), link level (indicating
transmission across a single hardware link), or higher levels.
administrative unit One or more administrative units occupying fixed, defined positions in an STM
group (AUG) payload. An AUG consists of AU-4s.
aging time The time to live before an object becomes invalid.
alarm cascading The method of cascading alarm signals from several subracks or cabinets.
alarm indication A mechanism to indicate the alarm status of equipment. On the cabinet of an NE,
four differently-colored indicators specify the current status of the NE. When the
green indicator is on, the NE is powered on. When the red indicator is on, a critical
alarm has been generated. When the orange indicator is on, a major alarm has been
generated. When the yellow indicator is on, a minor alarm has been generated. The
ALM alarm indicator on the front panel of a board indicates the current status of the
board.
application An application programming interface is a particular set of rules and specifications
programming that are used for communication between software programs.
interface (API)
application-specific A special type of chip that starts out as a nonspecific collection of logic gates. Late
integrated circuit in the manufacturing process, a layer is added to connect the gates for a specific
(ASIC) function. By changing the pattern of connections, the manufacturer can make the
chip suitable for many needs.
assured forwarding One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of
(AF) IETF. It is suitable for certain key data services that require assured bandwidth and
short delay. For traffic within the bandwidth limit, AF assures quality in forwarding.
For traffic that exceeds the bandwidth limit, AF degrades the service class and
continues to forward the traffic instead of discarding the packets.
asymmetric digital A technology for transmitting digital information at a high bandwidth on existing
subscriber line (ADSL) phone lines to homes and businesses. Unlike regular dialup phone service, ADSL
provides continuously-available, "always on" connection. ADSL is asymmetric in
that it uses most of the channel to transmit downstream to the user and only a small
part to receive information from the user. ADSL simultaneously accommodates
analog (voice) information on the same line. ADSL is generally offered at
downstream data rates from 512 kbit/s to about 6 Mbit/s.
automatic laser A technique (procedure) to automatically shutdown the output power of laser
shutdown (ALS) transmitters and optical amplifiers to avoid exposure to hazardous levels.
automatic level control A function that keeps output power of components in a system essentially constant,
(ALC) even when line attenuation in a section of the system increases.
automatic power A function to automatically equalize channel optical power at the transmitter end,
equilibrium (APE) ensuring a required optical power flatness and OSNR at the receiver end.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
(APD) Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher
voltages than other semiconductor electronics.
B
B/S Browser/Server
BA booster amplifier
BBC See battery backup cabinet.
BBER background block error ratio
BC boundary clock
BDI See backward defect indication.
BE See best effort.
BEI backward error indication
BER Bit error rate
BFD See Bidirectional Forwarding Detection.
BGP Border Gateway Protocol
BIAE backward incoming alignment error
BIOS See basic input/output system.
BIP-8 See bit interleaved parity-8.
BITS See building integrated timing supply.
BMC best master clock
BOM bill of materials
C
CAPEX capital expenditure
CAR committed access rate
CBS See committed burst size.
CCM continuity check message
CD chromatic dispersion
CDR See call detail record.
CE See customer edge.
CENELEC European Committee for Electrotechnical Standardization
CES See circuit emulation service.
CGMP Cisco Group Management Protocol
CIR committed information rate
CIST See Common and Internal Spanning Tree.
call detail record A record unit used to create billing records. A CDR contains details such as the
(CDR) called and calling parties, originating switch, terminating switch, call length, and
time of day.
carrier sense multiple Carrier sense multiple access with collision detection (CSMA/CD) is a computer
access with collision networking access method in which:
detection (CSMA/CD) A carrier sensing scheme is used.
A transmitting data station that detects another signal while transmitting a frame,
stops transmitting that frame, transmits a jam signal, and then waits for a random
time interval before trying to send that frame again.
circuit emulation A function with which the E1/T1 data can be transmitted through ATM networks.
service (CES) At 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.
circulation The number of copies of a newspaper or magazine per issue that are circulated in
the market
clock synchronization A process of synchronizing clocks, in which the signal frequency traces the
reference frequency, but the start points do not need to be consistent. This process is
(also known as frequency synchronization).
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels
division multiplexing into the same fiber. CWDM spaces wavelengths at a distance of several nm.
(CWDM) CWDM does not support optical amplifiers and is applied in short-distance chain
networking.
comma separated A CSV file is a text file that stores data, generally used as an electronic table or by
values (CSV) the database software.
committed burst size A parameter used to define the capacity of token bucket C, that is, the maximum
(CBS) burst 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.
common public radio A common standard of the key internal interface between the REC and the RE of
interface (CPRI) the wireless base station. This standard was established by Huawei, Ericsson, NEC,
Siemens, and Nortel in June 2003. It aims at standardizing the baseband and RF
interface. The CPRI has a set of mature standards, which advance the standard and
equipment. The major feature of the CPRI is that baseband is separated from RF to
reduce the cost of engineering, equipment room, and equipment.
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST
(CST) region is considered as a switch; therefore, the CST can be considered as their
spanning tree generated with STP/RSTP.
composite service An aggregation of a series of services relevant to each other.
configuration data A command file defining hardware configurations of an NE. With this file, an NE
can collaborate with other NEs in a network. Therefore, configuration data is the
key factor that determines the operation of an entire network.
consistency check A function that is used to check the consistency of service data and resource data
between two softswitches that have the dual homing relation. This ensures the
consistency of service data and resource data between the softswitches.
D
DAPI destination access point identifier
DB database
DBMS Database Management System
DBPS distributed board protect system
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 A power system, in which the BGND of the DC return conductor is short-circuited
(with 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.
DCE See data circuit-terminating equipment.
DCF See dispersion compensation fiber.
DCM See dispersion compensation module.
DCN See data communication network.
DDF digital distribution frame
DEI device emulation interrupt
DHCP See Dynamic Host Configuration Protocol.
DIP switch dual in-line package switch
produced by DCE.
delay measurement The time elapsed since the start of transmission of the first bit of the frame by a
(DM) source 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.
dense wavelength The technology that utilizes the characteristics of broad bandwidth and low
division multiplexing attenuation of single mode optical fiber, employs multiple wavelengths with specific
(DWDM) frequency spacing as carriers, and allows multiple channels to transmit
simultaneously in the same fiber.
designated switch A designated switch of a device is a switch that is directly connected to the device
and forwards BPDUs to the device.
detection sensitivity The capability for a detector to respond to an exception.
differentiated service An IETF standard that defines a mechanism for controlling and forwarding traffic in
(DiffServ) a differentiated manner based on CoS settings to handle network congestion.
differentiated services According to the QoS classification standard of the Differentiated Service
code point (DSCP) (Diff-Serv), 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 signal processor A microprocessor designed specifically for digital signal processing, generally in
(DSP) real time.
digital subscriber line A network device, usually situated in the main office of a telephone company, that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections
(DSLAM) and uses multiplexing techniques to put these signals on a high-speed backbone line.
dispersion A type of fiber that uses negative dispersion to compensate for the positive
compensation fiber dispersion of the transmitting fiber to maintain the original shape of the signal pulse.
(DCF)
dispersion A type of module that contains dispersion compensation fibers to compensate for
compensation module the dispersion of the transmitting fiber.
(DCM)
distribute service A distributed service development and running framework, in which ser vices
framework (DSF) comply with standard specifications, and can be loaded and run by containers. This
framework provides a range of services including registration, detection, routing,
and distributed access.
distributed link A board-level port protection technology that detects unidirectional fiber cuts and
aggregation group negotiates with the opposite port. In the case of a link down failure on a port or
(DLAG) hardware failure on a board, services are automatically switched to the slave board,
thereby achieving 1+1 protection for the inter-board ports.
domain A logical subscriber group based on which the subscriber rights are controlled.
dotted decimal A format of IP address. IP addresses in this format are separated into four parts by a
notation dot "." with each part is in the decimal numeral.
downlink traffic The network traffic transferred into an internal carrier network. Noticeably,
E
E-LAN See Ethernet local area network.
E-Line See Ethernet line.
E1 An European standard for high-speed data transmission at 2.048 Mbit/s. It provides
thirty-two 64 kbit/s channels. A time division multiplexing frame is divided in to 32
timeslots numbered from 0 to 31. Timeslot 0 is reserved for frame synchronization,
and timeslot 16 is reserved for signaling transmission. The rest 30 timeslots are use
as speech channels. Each timeslot sends or receives an 8-bit data per second. Each
frame sends or receives 256-bit data per second. 8000 frames will be sent or
received per second. Therefore the line data rate is 2.048 Mbit/s.
E2E end to end
EAPE enhanced automatic power pre-equilibrium
EBS See excess burst size.
EDFA See erbium-doped fiber amplifier.
EEC Ethernet Electric Interface PMC Card
EEPROM See electrically erasable programmable read-only memory.
EF See expedited forwarding.
EFM Ethernet in the First Mile
EIR See excess information rate.
EMC See electromagnetic compatibility.
EMF element management framework
EPL See Ethernet private line.
EPLAN See Ethernet private LAN service.
EPLD See erasable programmable logic device.
EPON See Ethernet passive optical network.
ERPS Ethernet ring protection switching
ESC See electric supervisory channel.
channel (ESC) is introduced into DCC service overhead and is transmitted with service signals.
electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable
programmable storage for long periods without electricity while still allowing reprograming.
read-only memory EEPROMs contain less memory than RAM, take longer to reprogram, and can be
(EEPROM) reprogramed only a limited number of times before wearing out.
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.
encapsulation A technology for layered protocols, in which a lower-level protocol accepts a
message from a higher-level protocol and places it in the data portion of the
lower-level frame. Protocol A's packets have complete header information, and are
carried by protocol B as data. Packets that encapsulate protocol A have a B header,
an A header, followed by the information that protocol A is carrying. Note that A
could equal to B, as in IP inside IP.
enterprise system A path protocol that connects the host to various control units in a storage system.
connection (ESCON) Enterprise system connection is a serial bit stream transmission protocol that
operates a rate of 200 Mbit/s.
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.
erbium-doped fiber An optical device that amplifies optical signals. This device uses a short optical
amplifier (EDFA) fiber doped with the rare-earth element, Erbium. The signal to be amplified and a
pump laser are multiplexed into the doped fiber, and the signal is amplified by
interacting with doping ions. When the amplifier passes an external light source
pump, it amplifies the optical signals in a specific wavelength range.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode,
traffic control is achieved by token buckets C and E. The excess burst size
parameter defines the capacity of token bucket E, that is, the maximum burst IP
packet size when the 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.
excess information rate The bandwidth for excessive or burst traffic above the CIR; it equa ls the result of
(EIR) the actual transmission rate without the safety rate.
expedited forwarding The highest order QoS in the Diff-Serv network. EF PHB is suitable for services
(EF) that demand low packet loss ratio, short delay, and broad bandwidth. In all the
cases, EF traffic can guarantee a transmission rate equal to or faster than the set rate.
The DSCP value of EF PHB is "101110".
experimental bits A field in the MPLS packet header, three bits long. This field is always used to
(EXP) identify the CoS of the MPLS packet.
eye pattern An oscilloscope display in which a digital data signal from a receiver is repetitively
sampled and applied to the vertical input, while the data rate is used to trigger the
horizontal sweep. It is so called because, for several types of coding, the pattern
looks like a series of eyes between a pair of rails.
field programmable A semi-customized circuit that is used in the Application Specific Integrated Circuit
gate array (FPGA) (ASIC) field and developed based on programmable components. FPGA remedies
many of the deficiencies of customized circuits, and allows the use of many more
gate arrays.
first in first out (FIFO) A stack management method in which data that is stored first in a queue is also read
and invoked first.
fixed mobile Communication service provided based on the combination of fixed-line and
convergence (FMC) wireless technologies. Service providing, access technologies, and terminal devices
on an FMC network are independent from each other. The same service can be
obtained from various access networks. Subscribers from different access networks
can obtain and use the same service.
flow An aggregation of packets that have the same characteristics. On boards, it is a
group of packets that have the same quality of service (QoS) operation.
forced switching The action of switching traffic signals between a working channel and protection
channel. The switching occurs even if the channel to which traffic is being switched
is faulty or an equal or higher priority switching command is in effect.
forward defect A packet generated and traced forward to the sink node of the LSP by the node that
indication (FDI) first detects defects. It includes fields to indicate the nature of the defect and its
location. Its primary purpose is to suppress alarms being raised at affected higher
level client LSPs and (in turn) their client layers.
forward error A bit error correction technology that adds correction information to the payload at
correction (FEC) the transmit end. Based on the correction information, the bit errors generated
during transmission can be corrected at the receive end.
frame delay variation A measurement of the variations in the frame delay between a pair of service
(FDV) frames, where the service frames belong to the same CoS instance on a point to
point ETH connection.
frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the
number of service frames not delivered is the difference between the number of
service frames arriving at the ingress ETH flow point and the number of service
frames delivered at the egress ETH flow point in a point-to-point ETH connection.
frame relay (FR) A packet-switching protocol used for WANs. Frame relay transmits variable-length
packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the
sake of speed.
frequency division An application in which channels are divided by frequency. In an FDD system, the
duplex (FDD) uplink and downlink use different frequencies. Downlink data is sent through bursts.
Both uplink and downlink transmission use frames with fixed time length.
G
G-ACH generic associated channel header
GAL generic associated channel header label
GCC general communication channel
GE Gigabit Ethernet
GE ADM A technique that improves the transmission of GE services on a metropolitan area
network. Using this technique, equipment configured with a high-speed backplane
can separately transmit, aggregate, or divert GE services over electrical-layer
wavelengths or sub-wavelengths. This achieves cross-connections of wavelengths
and end-to-end management of sub-wavelengths over a single device. GE ADM
enables GE convergence and cross-connections at the same time, thereby ensuring
that network resources are used effectively.
GFF gain flattening filter
GFP See Generic Framing Procedure.
GMPLS generalized multiprotocol label switching
GNE See gateway network element.
GPON gigabit-capable passive optical network
GPS See Global Positioning System.
GSM See Global system for mobile communications.
GSSP General Snooping and Selection Protocol
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,
System (GPS) and timing services to users worldwide.
Global system for The second-generation mobile networking standard defined by the European
mobile Telecommunications Standards Institute (ETSI). It is aimed at designing a standard
communications for global mobile phone networks. GSM consists of three main parts: mobile
(GSM) switching subsystem (MSS), base station subsystem (BSS), and mobile station
(MS).
gateway IP address The IP address of a gateway. A gateway is a node that forwards packets between
networks. Packets are sent to the gateway IP address when the destination network
address resides in a different network to the sender.
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.
(GTS) This is to adapt the traffic to network resources that can be provided by the
downstream router to avoid packet discarding and congestion.
granularity The extent to which a system is broken down into small parts, either the system
itself or its description or observation. It is the extent to which a larger entity is
subdivided. If a system has more granularity for you to choose, that is, there are
more granules in the system for you to choose, then you can customize the system
more flexibly.
H
HA system high availability system
HCS higher order connection supervision
HD-SDI high definition serial digital interface
HDB3 See high density bipolar of order 3 code.
HDTV See high definition television.
HP higher order path
HPT higher order path termination
HSDPA See High Speed Downlink Packet Access.
HSI high-speed Internet
HSL See high-level script language.
HTML Hypertext Markup Language
HUAWEI Electronic The software used to view, search for, and upgrade electronic documentation of
Document Explorer Huawei products. HedEx, pronounced as [hediks], has two editions, HedEx Lite and
(HedEx) HedEx Server.
HedEx See HUAWEI Electronic Document Explorer.
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.
high definition A type of TV that is capable of displaying at least 720 progressive or 1080
television (HDTV) interlaced active scan lines. It must be capable of displaying a 16:9 image using at
least 540 progressive or 810 interlaced active scan lines.
high density bipolar of A code used for baseband transmissions between telecommunications devices. The
order 3 code (HDB3) HDB3 code has the following feature: high capability of clock extraction, no direct
current component, error-checking capability, and a maximum of three consecutive
zeros.
high-level script A script language. Based on python, the HSL syntax is simple, clear, and
language (HSL) extendable.
I
IANA See Internet Assigned Numbers Authority.
IC See integrated circuit.
ICMP See Internet Control Message Protocol.
IEC International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers.
IETF Internet Engineering Task Force
(ICMP)
Internet Group One of the TCP/IP protocols for managing the membership of Internet Protocol
Management Protocol multicast groups. It is used by IP hosts and adjacent multicast routers to establish
(IGMP) and maintain multicast group memberships.
Internet Protocol A system that provides TV services over the IP network. In the IPTV system, media
television (IPTV) streams from satellites, terrestrial, and studios are converted by the encoder to the
media streams applicable to the IP network. Then the media streams are transmitted
to the terminal layer on the IP network. Media content is displayed on a TV set after
media streams are processed by specified receiving devices (for example, an STB).
Internet Protocol The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which
version 4 (IPv4) is assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and
is written as 4 octets separated by periods and may range from 0.0.0.0 through to
255.255.255.255. Each IPv4 address consists of a network number, an optional
subnetwork number, and a host number. The network and subnetwork numbers
together are used for routing, and the host number is used to address an individual
host within the network or subnetwork.
Internet Protocol An update version of IPv4, which is designed by the Internet Engineering Task
version 6 (IPv6) Force (IETF) and is also called IP Next Generation (IPng). It is a new version of the
Internet Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has
32 bits while an IPv6 address has 128 bits.
input jitter tolerance The measure of a receiver's ability to tolerate jitter on an incoming waveform.
insertion loss The loss of power that results from inserting a component, such as a connector,
coupler, or splice, into a previously continuous path.
instant messaging (IM) A form of real-time communication between two or more people based on typed
text. The text is conveyed via devices connected over a network such as the Internet.
integrated circuit (IC) A combination of inseparable associated circuit elements that are formed in place
and interconnected on or within a single base material to perform a microcircuit
function.
intelligent power A technology that reduces the optical power of all the amplifiers in an adjacent
adjustment (IPA) regeneration section in the upstream to a safe level if the system detects the loss of
optical signals on the link. IPA helps ensure that maintenance engineers are not
injured by the laser escaping from a broken fiber or a connector that is not plugged
in properly.
intermediate The transitional frequency between the frequencies of a modulated signal and an RF
frequency (IF) signal.
J
jitter The measure of short waveform variations caused by vibration, voltage fluctuations,
and control system instability.
L
L2VPN Layer 2 virtual private network
Link Aggregation A dynamic link aggregation protocol that improves the transmission speed and
Control Protocol reliability. The two ends of the link send LACP packets to inform each other of their
(LACP) parameters and form a logical aggregation link. After the aggregation link is formed,
LACP maintains the link status in real time and dynamically adjusts the ports on the
aggregation link upon detecting the failure of a physical port.
Locked signal function A function administratively locks an MEG end point (MEP) at the server layer,
(LCK) informs consequential data traffic interruption to the peer MEP at the client layer,
and suppresses the alarm at the client layer.
label edge router A device that sits at the edge of an MPLS domain, that uses routing information to
(LER) assign labels to datagrams and then forwards them into the MPLS domain.
label switching router Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR
(LSR) is composed of two parts: control unit and forwarding unit. The former is
responsible for allocating the label, selecting the route, creating the label forwarding
table, creating and removing the label switch path; the latter forwards the labels
according to groups received in the label forwarding table.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a
(LAG) link aggregation group so that a MAC client can treat the link aggregation group as
if it were a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitless increase or decrease the capacity of a link to meet the
(LCAS) bandwidth needs of the application. It also provides a means of removing member
links that have experienced failure. The LCAS assumes that in cases of capacity
initiation, increases or decreases, the construction or destruction of the end-to-end
path is the responsibility of the network and element management systems.
link status The running status of a link, which can be Up, Down, backup, or unknown.
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination
(LTM) MEP. LTM includes the Time to Live (TTL) and the MAC address of the
destination MEP2.
linktrace reply (LTR) For 802.1ag MAC Trace, the destination MEP replies with a response message to
the source MEP after the destination MEP receives the LTM, and the response
message is called LTR. LTR also includes the TTL that equals the result of the TTL
of LTM minus 1.
local area network A network formed by the computers and workstations within the coverage of a few
(LAN) square kilometers or within a single building, featuring high speed and low error
rate. Current LANs are generally based on switched Ethernet or Wi-Fi technology
and run at 1,000 Mbit/s (that is, 1 Gbit/s).
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the
(LLC) upper sublayer of the OSI data link layer. The LLC is the same for the various
physical media (such as Ethernet, token ring, WLAN).
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.
loopback message The loopback packet sent by the node that supports 802.2ag MAC Ping to the
(LBM) destination node. LBM message carries its own sending time.
loopback reply (LBR) A response message involved in the 802.2ag MAC Ping function, with which the
destination MEP replies to the source MEP after the destination MEP receives the
LBM. The LBR carries the sending time of LBM, the receiving time of LBM and
the sending time of LBR.
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.
MAC address A link layer address or physical address. It is six bytes long.
MAC address aging A function that deletes MAC address entries of a device when no packets are
received from this device within a specified time period.
MADM multiple add/drop multiplexer
MBB mobile broadband
MD See maintenance domain.
MD5 See message digest algorithm 5.
MDF See main distribution frame.
ME See maintenance entity.
MEG See maintenance entity group.
MEP maintenance association end point
MFAS See multiframe alignment signal.
MGC media gateway controller
MIB See management information base.
MID message identification
MIN mobile identification number
MIP See maintenance entity group intermediate point.
MLD See multicast listener discovery.
MML man-machine language
MNO See mobile network operator.
MOP See method of procedure.
MP maintenance point
MPI-R main path interface at the receiver
MPI-S main path interface at the transmitter
Multiple Spanning A protocol that can be used in a loop network. Using an algorithm, the MSTP
Tree Protocol (MSTP) blocks 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
Tree region (MST among them. Switches physically and directly connected and configured with the
region) same MST 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.
main distribution A device at a central office, on which all local loops are terminated.
frame (MDF)
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).
maintenance entity An ME consists of a pair of maintenance entity group end points (MEPs), two ends
(ME) of a transport trail, and maintenance association intermediate points (MIPs) on the
trail.
maintenance entity A MEG consists of MEs that meet the following criteria:
group (MEG) Exist within the same management edges.
Have the same MEG hierarchy.
Belong to the same P2P or P2MP connection.
maintenance entity An intermediate point in a MEG, which is able to forward OAM packets and
group intermediate respond to some OAM packets, but unable to initiate the transmission of OAM
point (MIP) packets or perform any operations on network connections.
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
(MIB) (such as routers and switches) in a network.
mean time between The average time between consecutive failures of a piece of equipment. It is a
failures (MTBF) measure of the reliability of the system.
measurement result Percentage of the number of the actually reported measurement results to the
integrity (MRI) number of the measurement results that should be reported.
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.
method of procedure A document that describes the process of executing a specific task. It facilitates the
(MOP) mutual understanding of and cooperation between a service provider and a carrier.
Before executing a task, the representatives from both parties confirm this document
and reach an agreement on it. This document describes who, when, where, why, and
how to execute a task and what to do.
mobile network A company that has a network infrastructure, sells large network capacities, and
operator (MNO) provides transparent network channels.
multi-segment pseudo A collection of multiple adjacent PW segments. Each PW segment is a
wire (MS-PW) point-to-point PW. The use of MS-PWs to bear services saves tunnel resources and
can transport services over different networks.
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.
multicast listener A protocol used by an IPv6 router to discover the multicast listeners on their directly
discovery (MLD) connected network segments, and to set up and maintain member relationships. On
IPv6 networks, after MLD is configured on the receiver hosts and the multicast
router to which the hosts are directly connected, the hosts can dynamically join
related groups and the multicast router can manage members on the local network.
multiframe alignment A distinctive signal inserted into every multiframe or once into every n multiframes,
signal (MFAS) always occupying the same relative position within the multiframe, and used to
establish and maintain multiframe alignment.
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 An all-ONES characteristic or adapted information signal. It's generated to replace
alarm indication signal the normal traffic signal when it signal contains a defect condition in order to
(MS-AIS) prevent consequential downstream failures being declared or alarms being raised.
AIS can be identified as multiplex section alarm indication signal.
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.
multiplex section A function that generates the multiplex section overhead (MSOH) during the
termination (MST) formation of an SDH frame signal and that terminates the MSOH in the reverse
direction.
multiplexer (MUX) Equipment that combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate
channels being fixed.
multiplexing A procedure by which multiple lower order path layer signals are adapted into a
higher order path or the multiple higher order path layer signals are adapted into a
multiplex section.
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
NAS network access server
noise figure A measure of degradation of the signal-to-noise ratio (SNR), caused by components
in a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the
output noise power of a device to the portion thereof attributable to thermal noise in
the input termination at standard noise temperature T0 (usually 290 K). The noise
figure is thus the ratio of actual output noise to that which would remain if the
device itself did not introduce noise. It is a number by which the performance of a
radio receiver can be specified.
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
OADM See optical add/drop multiplexer.
OAM See operation, administration and maintenance.
OAMPDU operation, administration and maintenance protocol data unit
OAMS Optical fiber line Automatic Monitoring System
OC ordinary clock
OCI open connection indication
OCP optical channel protection
OCS optical core switching
OCh optical channel with full functionality
OD optical demultiplexing
ODB optical duobinary
ODF optical distribution frame
ODUk optical channel data unit - k
OEQ optical equalizer
OFC optical fiber communication conference and exhibit
OIF See Optical Internetworking Forum.
OLP See optical line protection.
OMS optical multiplexing section
ONT See optical network terminal.
ONU See optical network unit.
OOS out of service
OPEX operating expense
excessively high.
optical channel A protection architecture that allows one wavelength to provide protection for
payload unit (OPU) multiple services between different stations, saving wavelength resources and
lowering costs.
optical line protection Optical line protection is implemented using the dual feeding and selective
(OLP) receiving function. Two pairs of fibers (that is, four fibers) are used. One pair of
fibers function as the working trail and is used to transmit service signals of a line
when the line is normal. The other pair of fibers function as the protection trail and
is used to carry protection switching signals when a fiber cut occurs or the signal
attenuation is excessively large.
optical network A device that terminates the fiber optical network at the customer premises.
terminal (ONT)
optical network unit A form of Access Node that converts optical signals transmitted via fiber to
(ONU) electrical signals that can be transmitted via coaxial cable or twisted pair copper
wiring to individual subscribers.
optical signal-to-noise The ratio of signal power to noise power in a transmission link. OSNR is the most
ratio (OSNR) important index for measuring the performance of a DWDM system.
optical supervisory A technology that uses specific optical wavelengths to realize communication
channel (OSC) among nodes in optical transmission network and transmit the monitoring data in a
certain channel.
optical time domain A device that sends a series of short pulses of light down a fiber-optic cable and
reflectometer (OTDR) measures the strength of the return pulses. An OTDR is used to measure fiber length
and light loss, and to locate fiber faults.
optical transmission A section in the logical structure of an optical transport network (OTN). The OTS
section (OTS) allows the network operator to perform monitoring and maintenance tasks between
NEs.
optical transponder A device or subsystem that converts accessed client signals into a
unit (OTU) G.694.1/G.694.2-compliant WDM wavelength.
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
P
P2MP point-to-multipoint
P2P See point-to-point service.
PCB See printed circuit board.
PCC protection communication channel
PCN product change notice
PCS physical coding sublayer
PDG polarization-dependent gain
PDH See plesiochronous digital hierarchy.
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the
hierarchy (PDH) minimum rate 64 kit/s into rates of 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s.
point-to-point service A service between two terminal users. In P2P services, senders and recipients are
(P2P) terminal users.
pointer An indicator whose value defines the frame offset of a virtual container with respect
to the frame reference of the transport entity on which this pointer is supported.
polarization-dependent A measure of the peak-to-peak insertion loss or gain variation caused by a
loss (PDL) component when stimulated by all possible polarization states. PDL is specified in
dB.
power distribution unit A unit that performs AC or DC power distribution.
(PDU)
printed circuit board A board used to mechanically support and electrically connect electronic
(PCB) components using conductive pathways, tracks, or traces, etched from copper sheets
laminated onto a non-conductive substrate.
protection path A path in a protection group that transports services when a fault occurs on the
working path.
provider edge (PE) A device that is located in the backbone network of the MPLS VPN structure. A PE
is responsible for managing VPN users, establishing LSPs between PEs, and
exchanging routing information between sites of the same VPN. A PE performs the
mapping and forwarding of packets between the private network and the public
channel. A PE can be a UPE, an SPE, or an NPE.
pseudo random binary A sequence that is random in the sense that the value of each element is independent
sequence (PRBS) of the values of any of the other elements, similar to a real random sequence.
pseudo wire (PW) An emulated connection between two PEs for transmitting frames. The PW is
established and maintained by PEs through signaling protocols. The status
information of a PW is maintained by the two end PEs of a PW.
pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes
edge-to-edge (PWE3) of 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.
Q
QPSK See quadrature phase shift keying.
QinQ See 802.1Q in 802.1Q.
quadrature phase shift A modulation method of data transmission through the conversion or modulation
keying (QPSK) and 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.
R
RADIUS See Remote Authentication Dial In User Service.
RAN See radio access network.
RBW reverse-band working
RDI remote defect indication
RED See random early detection.
REG See regenerator.
RF See radio frequency.
RFC See Request For Comments.
RIP See Routing Information Protocol.
RJ45 registered jack45
RMEP remote maintenance association end point
RMON remote network monitoring
RMS resource management system
RMU rack monitoring unit
RNC See radio network controller.
ROADM reconfigurable optical add/drop multiplexer
ROPA See remote optical pumping amplifier.
RPR resilient packet ring
RS regenerator section
RS232 See Recommended Standard 232.
RS422 The specification that defines the electrical characteristics of balanced voltage
digital interface circuits. The interface can change to RS232 via the hardware
jumper and others are the same as RS232.
RSOH regenerator section overhead
RST regenerator section termination
RSTP See Rapid Spanning Tree Protocol.
RSVP See Resource Reservation Protocol.
RSVP-TE See Resource Reservation Protocol-Traffic Engineering.
RTP real-time performance
RX receive
RXD receive data
RZ return to zero
RZ code return-to-zero code
Rapid Spanning Tree An evolution of the Spanning Tree Protocol (STP) that provides faster spanning tree
Protocol (RSTP) convergence after a topology change. The RSTP protocol is backward compatible
with the STP protocol.
Recommended A standard that defines the electrical characteristics, timing, and meaning of signals,
Standard 232 (RS232) and the physical size and pinout of connectors.
Remote Authentication A security service that authenticates and authorizes dial-up users and is a centralized
Dial In User Service access control mechanism. As a distributed server/client system, RADIUS provides
(RADIUS) the AAA function.
Request For A document in which a standard, a protocol, or other information pertaining to the
Comments (RFC) operation of the Internet is published. The RFC is actually issued, under the control
of the IAB, after discussion and serves as the standard. RFCs can be obtained from
sources such as InterNIC.
Resource Reservation A protocol that reserves resources on every node along a path. RSVP is designed for
Protocol (RSVP) an integrated services Internet.
Resource Reservation An extension to the RSVP protocol for setting up label switched paths (LSPs) in
Protocol-Traffic MPLS networks. The RSVP-TE protocol is used to establish and maintain the LSPs
Engineering by initiating label requests and allocating label binding messages. It also supports
(RSVP-TE) LSP rerouting and LSP bandwidth increasing.
RoHS restriction of the use of certain hazardous substances
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a
Protocol (RIP) route based on the smallest hop count between the source and destination. RIP is a
distance vector protocol that routinely broadcasts routing information to its
neighboring routers and is known to waste bandwidth.
radio access network The network that provides the connection between CPEs and the CN. It isolates the
(RAN) CN from wireless network.
radio frequency (RF) A type of electric current in the wireless network using AC antennas to create an
electromagnetic field. It is the abbreviation of high-frequency AC electromagnetic
wave. The AC with the frequency lower than 1 kHz is called low-frequency current.
The AC with frequency higher than 10 kHz is called high-frequency current. RF can
be classified into such high-frequency current.
radio network A device in a radio network subsystem that is in charge of controlling the usage and
controller (RNC) integrity of radio resources.
random early detection A packet loss algorithm used in congestion avoidance. It discards the packet
(RED) according to the specified higher limit and lower limit of a queue so that global TCP
synchronization resulting from traditional tail drop can be prevented.
receiver sensitivity The minimum acceptable value of mean received power at point Rn (a reference
point at an input to a receiver optical connector) to achieve a 1x10-12 BER when
the FEC is enabled.
recognition Consumer awareness of having seen or heard an advertising message.
reference clock A stable and high-precision autonomous clock that provides frequencies as a
reference for other clocks.
regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
regenerator (REG) A piece of equipment or device that regenerates electrical signals.
regional root The root of the Internal Spanning Tree (IST) and Multiple Spanning Tree Instance
(MSTI) in the MST region. The regional root differs with the topology of the
spanning tree in the MST region.
remote optical A remote optical amplifier subsystem designed for applications where power supply
pumping amplifier and monitoring systems are unavailable. The ROPA subsystem is a power
(ROPA) compensation solution to the ultra-long distance long hop (LHP) transmission.
reservation An action that the charging module performs to freeze a subscriber's balance
amount, free resources, credits, or quotas before the subscriber uses services. This
action ensures that the subscriber has sufficient balance to pay for services.
ring network A network topology in which each node connects to exactly two other nodes,
forming a circular pathway for signals.
S
S-VLAN service virtual local area network
S1 byte A byte to transmit network synchronization status information. On an SDH network,
each NE traces hop by hop to the same clock reference source through a specific
clock synchronization path, realizing synchronization on the entire network. If a
clock reference source traced by an NE is missing, this NE will trace another clock
reference source of a lower level. To implement protection switching of clocks in
the whole network, the NE must learn about clock quality information of the clock
reference source it traces. Therefore, ITU-T defines S1 byte to transmit network
synchronization status information. It uses the lower four bits of the multiplex
section overhead S1 byte to indicate 16 types of synchronization quality grades.
Auto protection switching of clocks in a synchronous network can be implemented
using S1 byte and a proper switching protocol.
SAI service area identifier
SAPI service access point identifier
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SBS synchronous information backbone system
SCA selective call acceptance
SCE See service creation environment.
SD-SDI See standard definition-serial digital interface signal.
SDH See synchronous digital hierarchy.
SDI See serial digital interface.
SDP See Session Description Protocol.
SELV safety extra-low voltage
SES severely errored second
SETS SDH equipment timing source
SF See signal fail.
Secure Shell (SSH) A set of standards and an associated network protocol that allows establishing a
secure channel between a local and a remote computer. A feature to protect
information and provide powerful authentication function for a network when a user
logs in to the network through an insecure network. It prevents IP addresses from
being deceived and simple passwords from being captured.
Serial Line Interface A protocol that defines the framing mode over the serial line to implement
Protocol (SLIP) transmission of messages over the serial line and provide the remote host
interconnection function with a known IP address.
Session Description A protocol intended for describing multimedia sessions for the purposes of session
Protocol (SDP) announcement, session invitation, and other forms of multimedia session initiation.
Simple network "An IETF protocol for monitoring and managing systems and devices in a network.
management protocol The data being monitored and managed is defined by a MIB. The functions
(SNMP) supported by the protocol are the request and retrieval of data, the setting or writing
of data, and traps that signal the occurrence of events."
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.
security object (SO) A main part of the information security. It is not related with the communication
mode or terminal. It does not only focus on the security of the information exchange
but also provides feasible solutions of security for the user information, including
the user identity authentication, user password, and encryption.
segment A subset of an identity type. This is a different subset from a trust level including
but is not limited to the following examples: A subset based on customer age, a
subset based on where the identity was registered or based, a subset based on the
customer's gender, and a subset based on an association that the identity may have.
For example, an organization is confirmed as a supermarket or a customer is a
member of a society.
serial digital interface An interface that transmits data in a single channel in sequence.
(SDI)
service creation A service generation tool that provides a graphical user interface (GUI) for
environment (SCE) programming.
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.
service support data An identifier that defines data parameters of specific service feature descriptions in
(SSD) the global functional plane.
shaping A process of delaying packets within a traffic stream to cause it to conform to
specific defined traffic profile.
shared risk group A group of resources that share a common risk component whose failure can cause
(SRG) the failure of all the resources in the group.
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
given point in time. SNR is expressed as 10 times the logarithm of the power ratio
T
T1 A North American standard for high-speed data transmission at 1.544Mbps. It
provides 24 x 64 kbit/s channels.
TCM tandem connection monitor
TCN topology change notification
TCP/IP Transmission Control Protocol/Internet Protocol
TD-SCDMA See Time Division-Synchronous Code Division Multiple Access.
TDM See time division multiplexing.
be transferred till there are new tokens in the bucket. This scheme adjusts the rate of
packet input.
trTCM See two rate three color marker.
traffic classification A function that enables you to classify traffic into different classes with different
priorities according to some criteria. Each class of traffic has a specified QoS in the
entire network. In this way, different traffic packets can be treated differently.
traffic shaping A way of controlling the network traffic from a computer to optimize or guarantee
the performance and minimize the delay. It actively adjusts the output speed of
traffic in the scenario that the traffic matches network resources provided by the
lower layer devices, avoiding packet loss and congestion.
traffic statistics An activity of measuring and collecting statistics of various data on devices and
telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks.
The statistics also help the operators manage the device operating, locate problems,
monitor and maintain the networks, and plan the networks.
transparent mode A method of binary synchronous text transmission in which only transmission
control characters preceded by the data link escape (DLE) character are processed as
transmission control characters.
transparent A process during which the signaling protocol or data is not processed in the content
transmission but encapsulated in the format for the processing of the next phase.
trunk Physical communications line between two offices. It transports media signals such
as speech, data and video signals.
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.
type-length-value An encoding type that features high efficiency and expansibility. It is also called
(TLV) Code-Length-Value (CLV). T indicates that different types can be defined through
different values. L indicates the total length of the value field. V indicates the actual
data of the TLV and is most important. TLV encoding features high expansibility.
New TLVs can be added to support new features, which is flexible in describing
information loaded in packets.
U
UNI See user-to-network interface.
UPE user-end provider edge
UPI user payload identifier
UPM uninterruptible power module
upstream In an access network, the direction that is far from the subscriber end of the link.
upstream board A board that provides the upstream transmission function. Through an upstream
board, services can be transmitted upstream to the upper-layer device.
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.
VA value assurance
VAS See value-added service.
VB virtual bridge
VBR See variable bit rate.
VC trunk See virtual container trunk.
VCC See virtual channel connection.
VCCV virtual circuit connectivity verification
VCG See virtual concatenation group.
VCPLM virtual concatenation payload mismatch
VCTRUNK A virtual concatenation group applied in data service mapping, also called the
internal port of a data service processing board.
VDSL2 See very-high-speed digital subscriber line 2.
VLAN mapping A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at
the destination private network, VLAN mapping translates public VLAN tags back
into private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VM virtual memory
VOA variable optical attenuator
VPN virtual private network
VPWS See virtual private wire service.
VRRP See Virtual Router Redundancy Protocol.
VSI See virtual switching instance.
Virtual Router A protocol designed for multicast or broadcast LANs such as an Ethernet. A group
Redundancy Protocol of routers (including an active router and several backup routers) in a LAN is
(VRRP) regarded as a virtual router, which is called a backup group. The virtual router has
its own IP address. The host in the network communicates with other networks
through this virtual router. If the active router in the backup group fails, one of the
backup routers in this backup group becomes active and provides routing service for
W
WAN wide area network
WCDMA See Wideband Code Division Multiple Access.
WDM wavelength division multiplexing
WFQ See weighted fair queuing.
WLAN See wireless local area network.
WRR weighted round robin
X
X.25 A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
xDSL x digital subscriber line