Professional Documents
Culture Documents
NetStar O&M 21.1.810 Fiber Doctor System User Guide 01
NetStar O&M 21.1.810 Fiber Doctor System User Guide 01
NetStar O&M 21.1.810 Fiber Doctor System User Guide 01
21.1.810
Issue 01
Date 2023-05-19
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: https://www.huawei.com
Email: support@huawei.com
Purpose
This document describes the operations of the Fiber Doctor (FD) System.
Related Versions
The following table lists the product versions related to this document:
Intended Audience
The intended audiences of this document are technical support 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
Changes between document issues are cumulative. The latest document issue
contains all the changes in earlier issues.
Contents
3 Networking Scenarios.......................................................................................................... 29
3.1 Networking Scenarios (for OSN 9800/8800/6800/3800)....................................................................................... 29
3.2 Networking Scenarios (for OSN 1800)......................................................................................................................... 41
3.3 Networking Scenarios (for OptiXtrans E9600)........................................................................................................... 46
3.4 Networking Scenarios (for OptiXtrans E6600)........................................................................................................... 53
3.5 Networking Scenarios (for OptiXtrans DC908).......................................................................................................... 58
6.5.1.1 Near-End Detection Curve Undergoes an Undershoot and an Event Is Falsely Reported When the
TN12ST2 Board Is Used to Automatically Detect Line Fiber Quality...................................................................... 199
6.5.1.2 Near-End Detection Curve Becomes Abnormal When the TN12ST2 Board Is Used to Automatically
Detect Line Fiber Quality........................................................................................................................................................ 201
6.5.1.3 When the TN12ST2 Board Is Used to Automatically Detect Line Fiber Quality, the Reflection Peak
of the Detection Curve at the End Has a Slow Decrease, Which Conflicts with the Results of Detection
Using a Meter............................................................................................................................................................................. 201
6.5.1.4 When a Raman Board Is Configured and the TN12ST2 Board Is Used to Automatically Monitor
Fiber Quality, the Detection Curve at the End Goes Up, Affecting Event Reporting......................................... 202
6.5.2 Abnormal Detection Using the TNG2RPC Board................................................................................................. 202
6.5.3 Abnormal Operation Interfaces................................................................................................................................. 203
6.5.3.1 What Do I Do If a Failure Message Is Displayed but No Failure Cause Is Displayed After I Start
Fiber Quality Detection and a Success Message Is Displayed After I Restart Detection?................................203
11 FAQ....................................................................................................................................... 222
11.1 Events Cannot Be Parsed After OTDR Detection.................................................................................................. 222
1.1 Application
The FD system is used to monitor and manage line fibers in a network. By
precisely detecting the fiber connection status, the FD system helps maintenance
personnel analyze the quality of fiber connectors and splicing points, which
facilitates quick fiber issue diagnosis.
1.2 System Components
The FD system requires the interoperation between hardware and software.
1.3 Principles
The line fiber quality detection function calculates link loss calculation and locates
faults by emitting optical pulses into a fiber, and then receiving and analyzing the
Rayleigh scattering and Fresnel reflection signals that are generated at each point
during pulse transmission in the fiber.
1.1 Application
The FD system is used to monitor and manage line fibers in a network. By
precisely detecting the fiber connection status, the FD system helps maintenance
personnel analyze the quality of fiber connectors and splicing points, which
facilitates quick fiber issue diagnosis.
Online fiber status detection methods that can achieve remote, online, accurate,
and quick fiber status detection are necessary to improve maintenance efficiency
and reduce maintenance costs.
The line fiber quality detection function of the FD system helps maintenance
personnel quickly discover and rectify fiber quality issues, ensuring normal
network operations.
Raman This board is mainly used to ensure that the Raman pump laser is
boards properly started. It provides the following functions:
that ● Locates fault points when the fiber connection detection results
support are abnormal. The fiber connection detection can be performed
OTDR using the FCD button on the front panel of the Raman board in
detectio the fiber connection verification phase during hardware
n installation.
● Checks fiber quality before deployment commissioning.
● Locates fault points when the Raman laser cannot be turned on
and a LASER_OPEN_FAIL\ LASER-OPEN-FAIL alarm is reported.
● Checks fiber health status at any time during network operations.
● Analyzes whether a fiber quality issue occurs when the Raman
gain is excessively low and an OA_LOW_GAIN\ GAIN-LOW alarm
is reported.
● Locates fault points when a fiber cut occurs and a MUT_LOS \
LOS-MUT alarm is reported by FIU board, or verifies fiber recovery
status after a fiber cut is removed.
OSC This board is mainly used for fiber quality detection and fault
boards diagnosis during O&M. It provides the following functions:
that ● Checks fiber quality before deployment commissioning.
support
OTDR ● Performs real-time detection during network running and checks
detectio fiber status. If a fiber cut is detected, a FIBER_BREAK_POS alarm
n will be proactively reported to the NMS, indicating the position of
the fiber cut.
● Locates fault points when a fiber cut occurs and a MUT_LOS \
LOS-MUT alarm is reported by FIU board, or verifies fiber recovery
status after a fiber cut is removed.
The hardware emits detection light to obtain fiber performance data, which is
then uniformly scheduled by the software. The software provides user-friendly
GUIs to set detection modes in various scenarios.
● Hardware
The Raman or OSC boards that support OTDR detection are used to monitor
the line fiber quality. They emit detection light to obtain fiber performance
data, receive detection results, and report the obtained fiber performance
data to the FD system.
● Software
1.3 Principles
The line fiber quality detection function calculates link loss calculation and locates
faults by emitting optical pulses into a fiber, and then receiving and analyzing the
Rayleigh scattering and Fresnel reflection signals that are generated at each point
during pulse transmission in the fiber.
Raman ● If 97ERPC board is found on the live network, fiber detection using
board TN12RAU1/TN12RAU2/TN11SRAU/TN51RPC/TN97RPC/
TNG2WRPC/TN52SRAPXF/TNG3SRAPXF/TNG2SRAPXF/TNG2WRPC
board is not allowed.
● If G2ERPC board is found on the live network, fiber detection using
TN12RAU1/TN12RAU2/TN11SRAU/TN51RPC/TN97RPC/
TNG2WRPC/TN52SRAPXF/TNG2WRPC board is not allowed.
● In the TWRS fiber+backward Raman board+OSC (providing the
OTDR function) scenario, the online Fiber Doctor System function
of the OSC module is not supported.
● When an SRAPXF board is connected to an RPC, ERPC, or ROP
board, the line fiber quality monitoring function cannot be used. If
the detection result is displayed, ignore it.
● When the TNG2RPC and TNG2HSC1 boards are used together, the
OTDR signal optical signals at the peer end, the service optical
signals at the SYS port of the local TNG2RPC board, and the OSC
signal optical signals at the RFM3 1511 optical port have impacts
on the OTDR detection of the TNG2RPC board. As a result, the
OTDR detection result of the TNG2RPC board becomes abnormal.
● For TNG2RPC and TNG2HSC1 boards, if the lasers are not turned
off after being manually turned on, the lasers on these boards will
be automatically turned off 15 minutes later. If the OTDR function
is enabled, the lasers are automatically turned on, and you do not
need to manually turn on them.
Near- Ensure that the near-end end face of the fiber is clean. You are
end end advised to use a microscope to check the end face.
face NOTE
When a TN12ST2 board is used for detection and the STAT indicator on the
board front panel is quickly blinking yellow (250 ms on and 250 ms off),
contamination of the near-end fiber end face, optical module suspension, or
near-end fiber cuts may occur on either of the two detection ports on the
TN12ST2 board.
Raman ● Do not press the FCD button on the Raman board front panel to
scenario trigger fiber connection detection during line fiber quality
detection.
● When Auto OTDR Detection upon Pump Laser Start is set to
Enabled, do not turn on the Raman laser on the Raman board
during line fiber quality detection.
● Bidirectional detection is enabled in the Raman scenario. If both
the source NE or sink NE has the TN12ST2/TN11AST2/TN51AST2/
TNG2AST2/TNG2AST4/TNG2HSC1 board at the same time, the
TN12ST2/TN11AST2/TN51AST2/TNG2AST2/TNG2AST4/
TNG2HSC1 board is preferentially selected for detection.
● In Raman scenarios, if the SRAPXF board is used to monitor fiber
quality, the detection curve may be abnormal and event reporting
may be inaccurate when Raman laser is enabled. In this case, it is
recommended that you disable the Raman laser and use Offline
mode in Advanced Mode to monitor the fiber quality.
TN12ST ● When the TN12ST2 board works on wavelength 1491 nm, it does
2 not support detection using Default Mode.
● When the TN12ST2 board uses Default Mode for fiber quality
detection, in case of a fiber environment change such as a fiber
cut or fiber insertion or removal, the user has to wait 10 minutes
before obtaining the latest detection results in the new fiber
environment. During the wait duration, the user cannot perform
manual detection. If the user performs manual detection in the
wait duration, the user must wait 10 minutes again to obtain the
latest automatic detection results.
Fiber cut The Fiber Doctor (FD) system reports the FIBER_BREAK_POS alarm
alarm to the NMS and indicate the position of a fiber cut only when the
following conditions are met:
● Only alarm-triggered detection is reported.
● TN12ST2/TN11AST2/TN51AST2/TNG2AST2/TNG2AST4/
TNG2HSC1 board is used for optical fiber quality detection.
● Fiber quality detection has been enabled on the detection port,
and the detection reference curve exists.
IEEE When IEEE 1588v2 clocks and the single-fiber bidirectional networking
1588v2 containing the TN11AST2/TN51AST2/TNG2AST2/TNG2AST4/
clock TNG2HSC1 and SFIU, DAPXF (functioning as the SFIU), SRAPXF (dual-
OSC configuration) or OLSPA/OLSPB boards are used, there are the
following limitations:
● When OSN 8800/6800/3800 T16 subracks or other subracks are
used on the live network and the OSC_CLK_MISMATCH alarm is
reported, do not manually Default Mode or Online mode in
Advanced Mode to perform online fiber detection.
● If no OSC_CLK_MISMATCH alarm is found on the live network but
more than four OLA sites are deployed in an OMS, clock boards
that satisfy the following requirements need to be configured at the
next OLA site behind every four OLA sites. Otherwise, online fiber
detection using Default Mode or Online mode in Advanced Mode
is not allowed because IEEE 1588v2 clock synchronization is
affected in this scenario.
● If online detection has been started for an OTS of an OMS but the
detection is not completed, online detection cannot be started for
other OTSs on the OMS; otherwise, IEEE 1588v2 clock
synchronization is affected.
● If IEEE 1588v2 clock synchronization is also enabled, ensure that
online monitoring is started for no more than 14 spans on the
entire network; otherwise, IEEE 1588v2 clock synchronization is
affected.
● Configuration requirements of the clock board
– When OSN 8800/6800/3800 T32 subracks are used, TN54STG
clock boards are configured.
– When OSN 8800/6800/3800 T64 subracks are used, TNK3STG
clock boards are configured.
– When OSN 8800/6800/3800 universal platform subracks are
used, TN13STG clock boards are configured.
– When OSN 9800 universal platform subracks are used, TN13STG
clock boards are configured.
Raman If the line fiber quality detection function starts when the IPA restarts,
IPA the IPA may enter the IPA ended state and the Raman laser cannot be
turned on.
● If Laser Restart Mode is set to Manual, manually restart the IPA
and then turn on the Raman laser after the line fiber quality
detection is completed.
● If Laser Restart Mode is set to Automatic, manually turn on the
Raman laser after the line fiber quality detection is completed.
Near- Ensure that the near-end end face of the fiber is clean. You are advised
end to use a microscope to check the end face.
end
face
Fiber The Fiber Doctor (FD) system reports the FIBER_BREAK_POS alarm to
cut the NMS and indicate the position of a fiber cut only when the
alarm following conditions are met:
● Only alarm-triggered detection is reported.
● TNF1AST4/TMB1AST2/TMB2AST2 board is used for optical fiber
quality detection.
● Fiber quality detection has been enabled on the detection port, and
the detection reference curve exists.
Raman ● If G2ERPC board is found on the live network, fiber detection using
board TNG2WRPC board is not allowed.
● In the TWRS fiber+backward Raman board+OSC (providing the
OTDR function) scenario, the online Fiber Doctor System function
of the OSC module is not supported.
● When an SRAPXF board is connected to an RPC, ERPC, or ROP
board, the line fiber quality monitoring function cannot be used. If
the detection result is displayed, ignore it.
● When the TNG2RPC and TNG2HSC1 boards are used together, the
OTDR signal optical signals at the peer end, the service optical
signals at the SYS port of the local TNG2RPC board, and the OSC
signal optical signals at the RFM3 1511 optical port have impacts
on the OTDR detection of the TNG2RPC board. As a result, the
OTDR detection result of the TNG2RPC board becomes abnormal.
● For TNG2RPC and TNG2HSC1 boards, if the lasers are not turned
off after being manually turned on, the lasers on these boards will
be automatically turned off 15 minutes later. If the OTDR function
is enabled, the lasers are automatically turned on, and you do not
need to manually turn on them.
Near- Ensure that the near-end end face of the fiber is clean. You are
end end advised to use a microscope to check the end face.
face
Raman ● Do not press the FCD button on the Raman board front panel to
scenario trigger fiber connection detection during line fiber quality
detection.
● When Auto OTDR Detection upon Pump Laser Start is set to
Enabled, do not turn on the Raman laser on the Raman board
during line fiber quality detection.
● Bidirectional detection is enabled in the Raman scenario. If both
the source NE or sink NE has the TNG2AST4/TNG2AST4E/
TNG2HSC1 board at the same time, the board is preferentially
selected for detection.
● In Raman scenarios, if the SRAPXF board is used to monitor fiber
quality, the detection curve may be abnormal and event reporting
may be inaccurate when Raman laser is enabled. In this case, it is
recommended that you disable the Raman laser and use Offline
mode in Advanced Mode to monitor the fiber quality.
Fiber cut The Fiber Doctor (FD) system reports the FIBER_BREAK_POS alarm
alarm to the NMS and indicate the position of a fiber cut only when the
following conditions are met:
● Only alarm-triggered detection is reported.
● TNG2AST2 board is used for optical fiber quality detection.
● Fiber quality detection has been enabled on the detection port,
and the detection reference curve exists.
IEEE When IEEE 1588v2 clocks and the single-fiber bidirectional networking
1588v2 containing theTNG2AST2/TNG2AST4/TNG2AST4E/TNG2HSC1 and
clock SFIU, DAPXF (functioning as the SFIU), SRAPXF (dual-OSC
configuration) or OLSPA/OLSPB boards are used, there are the
following limitations:
● If online detection has been started for an OTS of an OMS but the
detection is not completed, online detection cannot be started for
other OTSs on the OMS; otherwise, IEEE 1588v2 clock
synchronization is affected.
● If IEEE 1588v2 clock synchronization is also enabled, ensure that
online detection is started for no more than 14 spans on the entire
network; otherwise, IEEE 1588v2 clock synchronization is affected.
Raman If the line fiber quality detection function starts when the IPA restarts,
IPA the IPA may enter the IPA ended state and the Raman laser cannot be
turned on.
● If Laser Restart Mode is set to Manual, manually restart the IPA
and then turn on the Raman laser after the line fiber quality
detection is completed.
● If Laser Restart Mode is set to Automatic, manually turn on the
Raman laser after the line fiber quality detection is completed.
OSC ● On the front panel of the TMB1AST2 board, ensure that TM1 is
board connected to TMI1 and TM2 is connected to TMI2 using fiber patch
cords so that detection light traverses dead zone fibers. Do not
directly connect TM1 or TM2 to the RM port of the FIU board or
the OSCy port on the SFIU board.
● For the TMB1AST2 board, ensure that the ports on the detection
optical path TMB1AST2 TMx > TMB1AST2 TMIx > TMB1AST2 TMOx
> FIU RM (or OSCy on SFIU) > FIU OUT (or LINE1 on SFIU) are
clean.
In Figure 2-4, connecting the TMB1AST2 board to an FIU board is
used as example to describe the fiber connection requirements.
Near- Ensure that the near-end end face of the fiber is clean. You are advised
end to use a microscope to check the end face.
end
face
TMB1 When the TMB1AST2 is used by the Default Mode or Online mode in
AST2 Advanced Mode board for detection:
● If online detection has been started for an OTS of an OMS but the
detection is not completed, online detection cannot be started for
other OTSs on the OMS. Otherwise, IEEE 1588v2 clock
synchronization is affected.
● If IEEE 1588v2 clock synchronization is also enabled, ensure that
online monitoring is started for no more than 14 spans on the
entire network. Otherwise, IEEE 1588v2 clock synchronization is
affected.
Fiber The Fiber Doctor (FD) system reports the FIBER_BREAK_POS alarm to
cut the NMS and indicate the position of a fiber cut only when the
alarm following conditions are met:
● Only alarm-triggered detection is reported.
● TMB1AST2 board is used for optical fiber quality detection.
● Fiber quality detection has been enabled on the detection port, and
the detection reference curve exists.
OSC When the TMB1AST2 is used by the Offline mode in Advanced Mode
comm board for detection, the OSC communication of the detection line is
unicati interrupted and the OSC_LOS alarm is reported. When this occurs,
on non-GNEs may be unreachable by the NMS, affecting functions such
as DCN communication, IEEE 1588v2 clock synchronization, and
orderwire phones.
Near- Ensure that the near-end end face of the fiber is clean. You are
end end advised to use a microscope to check the end face.
face
Single- The board at one end can be detected only after detection on the
fiber board at the other end is completed; otherwise, detection results will
bidirecti be affected.
onal
detectio
n
Fiber cut The Fiber Doctor (FD) system reports the FIBER_BREAK_POS alarm
alarm to the NMS and indicate the position of a fiber cut only when the
following conditions are met:
● Only alarm-triggered detection is reported.
● OSC board is used for optical fiber quality detection.
● Fiber quality detection has been enabled on the detection port,
and the detection reference curve exists.
OSC When the is used by the Offline mode in Advanced Mode board for
comm detection, the OSC communication of the detection line is interrupted
unicati and the OSC_LOS alarm is reported. When this occurs, non-GNEs may
on be unreachable by the NMS, affecting functions such as DCN
communication.
3 Networking Scenarios
Figure 3-1 Networking scenario equipped with FIU and Raman board
Figure 3-3 Networking scenario equipped with FIU, ST2/AST2/AST4 and Raman
board
NOTE
NOTE
● In the ST2/AST2 single-fiber bidirectional scenario, if the SFIU board is used on the
network, a fiber is monitored only when the ID of the NE where the source detection
port of the fiber is located is smaller than the ID of the NE where the sink port is
located. The other fiber cannot be monitored.
● For a fiber, the board at one end can be detected only after detection on the board at
the other end is completed; otherwise, detection results will be affected.
● When the TN12ST2 board works on wavelength 1491 nm, it does not support detection
using Default Mode.
NOTE
● For a fiber, the board at one end can be detected only after detection on the board at
the other end is completed; otherwise, detection results will be affected.
● When a P32/P32C optical line board is interconnected with another P32/P32C optical
line board, OTDR detection cannot be started on both the LOUT and LIN ports of an
XFIU board.
Figure 3-6 Optical line protection (1+1 OTS trail protection, bidirectional
switching)
NOTE
In the networking shown in Figure 3-6, the EVOA that is used to adjust the optical power
difference of the working and protection OLP boards must be configured between the
receive-end FIU or SFIU and OLP boards.
Figure 3-7 Optical line protection (1+1 OMS Trail Protection and 1+1 Multi-OTS
Trail Protection)
NOTE
In the networking shown in Figure 3-7, the EVOA that is used to adjust line attenuation or
optical power must be configured between the FIU or SFIU and OA boards.
Figure 3-8 Optical line protection (networking scenario equipped with ON32P)
NOTE
● In the single-fiber bidirectional scenario, a fiber is monitored only when the ID of the NE
where the source detection port of the fiber is located is smaller than the ID of the NE
where the sink port is located. The other fiber cannot be monitored.
● For a fiber, the ST2/AST2/AST4 board at one end can be detected only after detection
on the ST2/AST2/AST4 board at the other end is completed; otherwise, detection results
will be affected.
● When the TN12ST2 board works on wavelength 1491 nm, it does not support detection
using Default Mode.
Figure 3-12 Main optical channel services in two-fiber bidirectional scenarios &
OSC signals in two-fiber bidirectional networking with IEEE 1588v2 enabled
(integrated FIU/WSMD9XF, DSFIU with one subcard in each direction and AST4/
AST2 is configured)
NOTE
In the networking shown in Figure 3-12, a fiber is monitored only when the ID of the NE
where the source detection port of the fiber is located is smaller than the ID of the NE
where the sink port is located. The other fiber cannot be monitored. In addition, the AST4/
AST2 board at one end can be detected only after detection on the AST4/AST2 board at the
other end is completed; otherwise, detection results will be affected.
Figure 3-13 Main optical channel services in two-fiber bidirectional scenarios &
OSC Signals in single-fiber Bidirectional networking with IEEE 1588v2 enabled or
disabled (integrated FIU/WSMD9XF, and AST4/AST2 is configured)
NOTE
In the networking shown in Figure 3-13, the AST4/AST2 board at one end can be detected
only after the detection on the AST4/AST2 board at the other end is completed; otherwise,
detection results will be affected.
Figure 3-14 Main optical channel services in single-fiber bidirectional scenarios &
OSC signals in single-fiber bidirectional networking with IEEE 1588v2 enabled or
disabled (WSMD9XF, and AST4/AST2 is configured)
NOTE
In the networking shown in Figure 3-14, the AST4/AST2 board at one end can be detected
only after detection on the TNF1AST4/TMB1AST2 board at the other end is completed;
otherwise, detection results will be affected.
NOTE
In the networking shown in Figure 3-15, the EVOA that is used to adjust the optical power
difference of the working and protection OLP boards must be configured between the
receive-end DFIU or DSFIU and OLP boards.
NOTE
In the networking scenario equipped with AST2 and a Raman board, probe light is
amplified by a backward Raman board, which may affect detection data.
Figure 3-19 Networking scenario equipped with DAPXF, SRAXPF, and single-fiber
bidirectional TNG2AST2
NOTE
● In the AST2 single-fiber bidirectional scenario, if the SFIU board is used on the network,
a fiber is monitored only when the ID of the NE where the source detection port of the
fiber is located is smaller than the ID of the NE where the sink port is located. The other
fiber cannot be monitored.
● For a fiber, the board at one end can be detected only after detection on the board at
the other end is completed; otherwise, detection results will be affected.
Figure 3-20 Optical line protection (1+1 OTS trail protection, bidirectional
switching)
NOTE
In the networking shown in Figure 3-20, the EVOA that is used to adjust the optical power
difference of the working and protection OLP boards must be configured between the
receive-end FIU or SFIU and OLP boards.
Figure 3-21 Optical line protection (1+1 OMS Trail Protection and 1+1 Multi-OTS
Trail Protection)
NOTE
In the networking shown in Figure 3-21, the EVOA that is used to adjust line attenuation or
optical power must be configured between the FIU or SFIU and OA boards.
NOTE
● In the single-fiber bidirectional scenario, a fiber is monitored only when the ID of the NE
where the source detection port of the fiber is located is smaller than the ID of the NE
where the sink port is located. The other fiber cannot be monitored.
● For a fiber, the TNG2AST2/TNG2AST4/TNG2AST4E board at one end can be detected
only after detection on the TNG2AST2/TNG2AST4/TNG2AST4E board at the other end is
completed; otherwise, detection results will be affected.
● When the TN12ST2 board works on wavelength 1491 nm, it does not support detection
using Default Mode.
Figure 3-25 Main optical channel services in two-fiber bidirectional scenarios &
OSC signals in two-fiber bidirectional networking with IEEE 1588v2 enabled
(WSMD9XF, DSFIU with one subcard in each direction and AST2 is configured)
NOTE
In the networking shown in Figure 3-25, a fiber is monitored only when the ID of the NE
where the source detection port of the fiber is located is smaller than the ID of the NE
where the sink port is located. The other fiber cannot be monitored. In addition, the AST2
board at one end can be detected only after detection on the TMB1AST2 board at the other
end is completed; otherwise, detection results will be affected.
Figure 3-26 Main optical channel services in two-fiber bidirectional scenarios &
OSC signals in two-fiber bidirectional networking with IEEE 1588v2 enabled or
disabled (WSMD9XF, DSFIU with two subcards in each direction and AST2 is
configured)
NOTE
In the networking shown in Figure 3-26, the AST2 board at one end can be detected only
after the detection on the AST2 board at the other end is completed; otherwise, detection
results will be affected.
Figure 3-27 Main optical channel services in two-fiber bidirectional scenarios &
OSC signals in two-fiber bidirectional networking with IEEE 1588v2 enabled or
disabled (WSMD9XF, DSFIU with two subcards in each direction, and AST2 is
configured)
NOTE
In the networking shown in Figure 3-27, the AST2 board at one end can be detected only
after detection on the AST2 board at the other end is completed; otherwise, detection
results will be affected.
NOTE
In the networking shown in Figure 3-28, the EVOA that is used to adjust the optical power
difference of the working and protection OLP boards must be configured between the
receive-end DFIU or DSFIU and OLP boards.
NOTE
For a fiber, the board at one end can be detected only after detection on the board at the
other end is completed; otherwise, detection results will be affected.
This section describes the detection specifications, license and hardware versions,
and feature changes supported by the FD system.
4.1 Availability
This section describes the equipment version, NMS version, and licenses required
to support the Fiber Doctor (FD) system.
4.2 Specifications
This section describes the specifications of the line fiber quality monitoring
function.
4.3 Feature Updates
The Fiber Doctor (FD) system is implemented by WDM tools and OSN products.
This section describes the feature updates and reasons for the updates of the FD
system in different WDM tools and OSN product versions. The versions that are
not listed in the document are those without feature updates.
4.1 Availability
This section describes the equipment version, NMS version, and licenses required
to support the Fiber Doctor (FD) system.
Table 4-1 lists the license requirements of the line fiber quality detection function
of the FD system.
Table 4-1 License requirements of the line fiber quality detection function
LNSDFDMSF0 License for the Fiber Line fiber quality detection can be
1 Doctor management performed only after a license is
system software a obtained.
a: The line fiber quality detection function is controlled by the detection ports of
detection boards at both ends of the fiber.
● Detection based on an OSC board: One license is required for the first line
fiber quality detection on each detection port of the OSC board.
● Detection based on a Raman board: When the Raman board is used with an
OSC board, no additional license is required. When the Raman board is used
independently, one license is required for the first line fiber quality detection
on each detection port of the Raman board.
NOTE
The FD function is integrated in the OptiX NetStar O&M component package that matches the
NMS. To obtain the component package, contact the local Huawei engineers. The OptiX NetStar
O&M component package is available in the following navigation path:
● Carrier network: Support > Software > Optical Business > Optical Transmission
Network > WDM > WDM tools > Netstar O&M at http://support.huawei.com.
● Enterprise network: Support > Software Download > Enterprise Optical Transmission &
Access > Optical Transmission > Netstar O&M at http://support.huawei.com/
enterprise.
TNG2RPC/ - - V100R020C10 -
TNG2WRPC SPC200
TNG3SRAPXF - - V100R019C10 -
SPC300
TNG2SRAPXF - - V100R019C10 -
SPC600
TN51AST2 - V100R007C - - -
00SPC700
TNF1AST4a - - - - V100R006C
20
TMB1AST2 - - - - V100R009C
b 00SPC700
TMB2AST2 - - - - V100R019C
10SPC700
TMG2AST2 - - V100R019C - -
10SPC300
TNG2HSC1 - - V100R020C - -
10SPC100
TNG2AST4 - - V100R021C - -
00SPC200
TMP1ON3 - - - V100R007C -
2/ 00
TMP1ON3
2P
TMP3ON2 - - - V100R019C -
0/ 10SPC600
TMP3ON2
0P
TMP2ON3 - - - V100R020C -
2/ 10SPC200
TMP2ON3
2P
TMP2ON2 - - - V100R021C -
0/ 00SPC200
TMP2ON2
0P
TMB1PSB - - - - V100R019C
M6/ 10SPC600
TMB1SBM6
TMB1MD4 - - - - V100R020C
0AFS 10SPC200
TMB1MD4 - - - - V100R021C
8AFS 10SPC200
TMB1MR4 - - - - V100R021C
AFS/ 00SPC200
TMB1MR4
FS
TMB2MR4 - - - - V100R021C
AFS/ 10SPC100
TMB2MR4
FS
TNG3OH20H V100R020C10SPC200
TNG3OH20 V100R021C00SPC300
TNG2OH20H/TNG2OH20 V100R021C10SPC200
TNG3SRAPXF V100R019C10SPC300 -
TNG2SRAPXF V100R019C10SPC600 -
TNG2RPC/TNG2WRPC V100R020C10SPC200 -
TMB1AST2 - V100R009C00 -
SPC700
TMB2AST2 - V100R019C10 -
SPC700
TMG2AST2 V100R019C10S - -
PC300
TMN1EMR801 - - V100R019C10
TMN1OLS01/ - - V100R019C10
TMN1OLL01/
TMN1OLS02/
TMN1OLL02
TMN1OLAS01/ - - V100R019C10
TMN1OLAL01
TNG2HSC1 V100R020C10S - -
PC100
TNG2AST4 V100R021C00S - -
PC200
TNG2AST4E V100R021C10S - -
PC200
TMN1WOLS01/ - - V100R020C10
TMN1WOLL01
TMN1WOLAS01/ - - V100R020C10
TMN1WOLAL01
TMB1MD40AFS - V100R020C10 -
SPC200
TMB1MD48AFS - V100R021C10 -
SPC200
TMB1MR4AFS/ - V100R021C00 -
TMB1MR4FS SPC200
TMB2MR4AFS/ - V100R021C10 -
TMB2MR4FS SPC100
OptiXtrans E9600
TNG3OH20H V100R020C10SPC200
TNG3OH20 V100R021C00SPC300
TNG2OH20H/ V100R021C10SPC200
TNG2OH20
Table 4-8 Version mapping between the tool and NCE NMS
Tool Versio NCE NMS Versiona
OptiX_NetStar_O&M V100R018C10SPC201CP2117/
7.0.510 V100R018C10SPC201CP2116/
V100R018C10SPC201CP2115
OptiX_NetStar_O&M V100R019C00SPC600
19.1.310
OptiX_NetStar_O&M V100R019C00CP6111
19.1.510 V100R019C00CP6112
OptiX_NetStar_O&M V100R019C00SPC602
19.1.610
OptiX_NetStar_O&M V100R020C10SPC200
20.1.310
OptiX_NetStar_O&M V100R021C00SPC101
21.0.210
OptiX_NetStar_O&M V100R021C00SPC200
21.0.310
OptiX_NetStar_O&M V100R021C10SPC100
21.1.310
OptiX_NetStar_O&M V100R021C10SPC200
21.1.510
OptiX_NetStar_O&M V100R021C10SPC202
21.1.610
OptiX_NetStar_O&M V100R021C10SPC203
21.1.710
OptiX_NetStar_O&M V100R021C10SPC205
21.1.810
NOTE
OptiX_NetStar_O&M ● V200R016C60CP2025/V200R016C60CP2026/
6.0.210 V200R016C60CP2027/V200R016C60CP2028/
V200R016C60CP2225/V200R016C60CP2322/
V200R016C60CP2323/V200R016C60CP2325
● V200R017C50CP2003/V200R017C50CP2005
● V200R017C60SPC201/V200R017C60CP2012/
V200R017C60CP2013
● V200R018C50SPC200/V200R018C50CP2002/
V200R018C50CP2301
OptiX_NetStar_O&M ● V200R017C60CP2015/V200R017C60CP2312
7.0.310 ● V200R018C50CP2003/V200R018C50CP2102
● V200R018C60SPC200
OptiX_NetStar_O&M V200R018C60SPC500CP5001/
19.0.310 V200R018C60SPC200CP2001
OptiX_NetStar_O&M V200R018C60SPC501CP5011
19.1.110
4.2 Specifications
This section describes the specifications of the line fiber quality monitoring
function.
Specification Description
Pulse width Width of detection light pulses. When the pulse width
increases, the light emitting time increases and consequently a
larger energy is obtained. This means that a larger dynamic
range can be acquired but also larger dead zones will result.
Insertion loss Deviation of the measured event attenuation from the actual
precision event attenuation.
Specification Description
Dynamic range ● The service light affects the FD performance during co-
directional transmission. As long as there is service light,
the FD dynamic range decreases.
For example, as shown in the following figure:
When an OTDR sends light to the 1511 nm module at site
A, service light and FD probe light are transmitted in the
same direction. In this case, the dynamic range of this
module is affected.
When an OTDR sends light to the 1491 nm module at site
B, service light and FD probe light are transmitted in
reverse directions. In this case, the dynamic range of this
module is not affected.
Specification Description
Event dead Displayed distance between the two points 1.5 dB lower than
zone the reflection peak on the reflection signal trace for a given
reflection peak (unsaturated, reflection value being less than
-45 dB).
Specification Description
Attenuation Distance between two intersection points from the start point
dead zone of the reflection pulse to the point 0.5 dB higher than the
linear from the trailing edge of the reflection pulse to the
backscattering curve for a given reflection peak (unsaturated,
reflection value being less than -45 dB). The distance is the
minimum distance for distinguishing and reporting two
adjacent events.
The following figure shows the event dead zone and attenuation dead zone:
The detection wavelengths of the OSC board are 1511 nm and 1491 nm.
Defa - 800 < 1.0 < 5.0 17 ±20 < 160 < 300
ult
Mod
e
800 < 1.0 < 5.0 17 ±20 < 160 < 300
4000 < 1.0 < 5.0 22 ±20 < 800 < 800
10000 < 1.0 < 5.0 23 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 25 ±20 < 4000 < 4000
800 < 1.0 < 5.0 19 ±20 < 160 < 300
4000 < 1.0 < 5.0 24 ±20 < 800 < 800
10000 < 1.0 < 5.0 25 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 27 ±20 < 4000 < 4000
Defa - 800 < 1.0 < 5.0 16 ±20 < 160 < 300
ult
Mod
e
800 < 1.0 < 5.0 16 ±20 < 160 < 300
4000 < 1.0 < 5.0 21 ±20 < 800 < 800
10000 < 1.0 < 5.0 22 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 24 ±20 < 4000 < 4000
800 < 1.0 < 5.0 18 ±20 < 160 < 300
4000 < 1.0 < 5.0 23 ±20 < 800 < 800
10000 < 1.0 < 5.0 24 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 26 ±20 < 4000 < 4000
Defa - 800 < 1.0 < 5.0 15 ±20 < 160 < 300
ult
Mod
e
800 < 1.0 < 5.0 15 ±20 < 160 < 300
4000 < 1.0 < 5.0 20 ±20 < 800 < 800
10000 < 1.0 < 5.0 21 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 23 ±20 < 4000 < 4000
800 < 1.0 < 5.0 17 ±20 < 160 < 300
4000 < 1.0 < 5.0 22 ±20 < 800 < 800
10000 < 1.0 < 5.0 23 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 25 ±20 < 4000 < 4000
Specification Description
Pulse width Width of detection light pulses. When the pulse width
increases, the light emitting time increases and consequently a
larger energy is obtained. This means that a larger dynamic
range can be acquired but also larger dead zones will result.
Insertion loss Deviation of the measured event attenuation from the actual
precision event attenuation.
Specification Description
Specification Description
NOTE
● The service light affects the FD performance during co-directional
transmission. As long as there is service light, the FD dynamic
range decreases.
For example, as shown in the following figure:
When an OTDR sends light to the 1511 nm module at site A,
service light and FD probe light are transmitted in the same
direction. In this case, the dynamic range of this module is affected.
When an OTDR sends light to the 1491 nm module at site B,
service light and FD probe light are transmitted in reverse
directions. In this case, the dynamic range of this module is not
affected.
Specification Description
Event dead Displayed distance between the two points 1.5 dB lower than
zone the reflection peak on the reflection signal trace for a given
reflection peak (unsaturated, reflection value being less than
-45 dB).
Attenuation Distance between two intersection points from the start point
dead zone of the reflection pulse to the point 0.5 dB higher than the
linear from the trailing edge of the reflection pulse to the
backscattering curve for a given reflection peak (unsaturated,
reflection value being less than -45 dB). The distance is the
minimum distance for distinguishing and reporting two
adjacent events.
The following figure shows the event dead zone and attenuation dead zone:
The detection wavelengths of the OSC board are 1511 nm and 1491 nm.
● Use a 2 m short fiber patch cord to connect the T port of the OTDR SFP
module to the EXT port of the board to ensure that the event precision meets
the specifications.
● The TMB1PSBM6, TMB1SBM6 boards cannot be interconnected to form
single-fiber bidirectional detection networking. Only one channel of OTDR-
supported optical signals is allowed in a fiber.
● The insertion loss precision of events within 100 m at the near end is not
guaranteed.
Specification Description
Pulse width Width of detection light pulses. When the pulse width
increases, the light emitting time increases and consequently a
larger energy is obtained. This means that a larger dynamic
range can be acquired but also larger dead zones will result.
Insertion loss Deviation of the measured event attenuation from the actual
precision event attenuation.
Specification Description
Dynamic range ● The service light affects the FD performance during co-
directional transmission. As long as there is service light,
the FD dynamic range decreases.
For example, as shown in the following figure:
When an OTDR sends light to the 1511 nm module at site
A, service light and FD probe light are transmitted in the
same direction. In this case, the dynamic range of this
module is affected.
When an OTDR sends light to the 1491 nm module at site
B, service light and FD probe light are transmitted in
reverse directions. In this case, the dynamic range of this
module is not affected.
Specification Description
Event dead Displayed distance between the two points 1.5 dB lower than
zone the reflection peak on the reflection signal trace for a given
reflection peak (unsaturated, reflection value being less than
-45 dB).
Specification Description
Attenuation Distance between two intersection points from the start point
dead zone of the reflection pulse to the point 0.5 dB higher than the
linear from the trailing edge of the reflection pulse to the
backscattering curve for a given reflection peak (unsaturated,
reflection value being less than -45 dB). The distance is the
minimum distance for distinguishing and reporting two
adjacent events.
The following figure shows the event dead zone and attenuation dead zone:
The detection wavelengths of the OSC board are 1511 nm and 1491 nm.
Defa - 800 < 1.0 < 5.0 17 ±20 < 160 < 300
ult
Mod
e
800 < 1.0 < 5.0 17 ±20 < 160 < 300
4000 < 1.0 < 5.0 22 ±20 < 800 < 800
10000 < 1.0 < 5.0 23 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 25 ±20 < 4000 < 4000
800 < 1.0 < 5.0 19 ±20 < 160 < 300
4000 < 1.0 < 5.0 24 ±20 < 800 < 800
10000 < 1.0 < 5.0 25 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 27 ±20 < 4000 < 4000
Specification Description
Pulse width Width of detection light pulses. When the pulse width
increases, the light emitting time increases and consequently a
larger energy is obtained. This means that a larger dynamic
range can be acquired but also larger dead zones will result.
Insertion loss Deviation of the measured event attenuation from the actual
precision event attenuation.
Specification Description
Specification Description
NOTE
● The service light affects the FD performance during co-directional
transmission. As long as there is service light, the FD dynamic
range decreases.
For example, as shown in the following figure:
When an OTDR sends light to the 1511 nm module at site A,
service light and FD probe light are transmitted in the same
direction. In this case, the dynamic range of this module is affected.
When an OTDR sends light to the 1491 nm module at site B,
service light and FD probe light are transmitted in reverse
directions. In this case, the dynamic range of this module is not
affected.
Specification Description
Event dead Displayed distance between the two points 1.5 dB lower than
zone the reflection peak on the reflection signal trace for a given
reflection peak (unsaturated, reflection value being less than
-45 dB).
Attenuation Distance between two intersection points from the start point
dead zone of the reflection pulse to the point 0.5 dB higher than the
linear from the trailing edge of the reflection pulse to the
backscattering curve for a given reflection peak (unsaturated,
reflection value being less than -45 dB). The distance is the
minimum distance for distinguishing and reporting two
adjacent events.
The following figure shows the event dead zone and attenuation dead zone:
The detection wavelengths of the OSC board are 1511 nm and 1491 nm.
Specification Description
Pulse width Width of detection light pulses. When the pulse width
increases, the light emitting time increases and consequently a
larger energy is obtained. This means that a larger dynamic
range can be acquired but also larger dead zones will result.
Specification Description
Insertion loss Deviation of the measured event attenuation from the actual
precision event attenuation.
Specification Description
Event dead Displayed distance between the two points 1.5 dB lower than
zone the reflection peak on the reflection signal trace for a given
reflection peak (unsaturated, reflection value being less than
-45 dB).
Attenuation Distance between two intersection points from the start point
dead zone of the reflection pulse to the point 0.5 dB higher than the
linear from the trailing edge of the reflection pulse to the
backscattering curve for a given reflection peak (unsaturated,
reflection value being less than -45 dB). The distance is the
minimum distance for distinguishing and reporting two
adjacent events.
The following figure shows the event dead zone and attenuation dead zone:
The detection wavelengths of the OSC board are 1511 nm and 1491 nm.
Defaul - 800 < 1.0 < 5.0 15 ±20 < 160 < 300
t
mode
800 < 1.0 < 5.0 15 ±20 < 160 < 300
4000 < 1.0 < 5.0 20 ±20 < 800 < 800
10000 < 1.0 < 5.0 21 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 23 ±20 < 4000 < 4000
800 < 1.0 < 5.0 17 ±20 < 160 < 300
4000 < 1.0 < 5.0 22 ±20 < 800 < 800
10000 < 1.0 < 5.0 23 ±20 < 2000 < 2000
20000 < 1.0 < 5.0 25 ±20 < 4000 < 4000
20000 < 1.0 < 5.0 23 ±20 < 4000 < 4000
The batch fiber The fiber quality 5.6 Batch Mode Fiber
quality detection monitoring function is Quality Monitoring is
function is added. enhanced. added.
The adaptive fiber The fiber quality 5.4 Adaptive Mode Fiber
quality detection monitoring function is Quality Monitoring is
function is added. enhanced. added.
The fiber quality The fiber quality The description of the ON32/
monitoring function monitoring function is ON32P board is added.
of the ON32/ON32P enhanced.
board is added.
7.0.510
Feature Update Reason for the Update Information Update
You can set the When the MUT_LOS alarm is 5.2.1 Starting Fiber
reference curve used to trigger fiber quality Detection and 6 Viewing
of the online detection, the offline mode and Analyzing Detection
mode and reference curve can be Results: Added the
offline mode preferentially used for description of setting the
for fiber detection. reference curve.
quality 5.3 Triggering Fiber Quality
detection. Detection by Alarm: Added
the requirements for setting
the reference curve of each
alarm.
The setting The TN11AST2 board uses the 5.2 Manually Starting Fiber
description of OSC&OTDR SFP V2 optical Quality Monitoring: The
Fiber module. Therefore, the fiber setting description of Fiber
Refractive quality monitoring function is Refractive Index is added.
Index is added. enhanced.
The operations The GUI of the fiber quality 5 Starting Fiber Quality
of the fiber detection is updated. Monitoring (NCE) and 6
quality Viewing and Analyzing
detection are Detection Results: The
updated. involved operation steps are
updated.
The TN12RAU1/ The line fiber quality The entire chapter is added.
TN12RAU2 monitoring function is
board first provided to remotely detect
supports the the fiber status online and
feature from this help maintenance personnel
version. rapidly discover and rectify
fiber quality issues.
You can set the When the MUT_LOS alarm is 5.2 Manually Starting
reference curve of used to trigger fiber quality Fiber Quality Monitoring
the online mode detection, the offline mode and 6 Viewing and
and offline mode reference curve can be Analyzing Detection
for fiber quality preferentially used for Results: Added the
detection. detection. description of setting the
reference curve.
5.3 Triggering Fiber
Quality Detection by
Alarm: Added the
requirements for setting
the reference curve of each
alarm.
The fiber quality The TN11AST2 board uses the 4.2.1 OSN
monitoring OSC&OTDR SFP V2 optical 9800/8800/6800/3800
function of the module. Therefore, the fiber Specifications: The fiber
TN11AST2 board quality monitoring function is quality monitoring
(using the enhanced. specifications of the
OSC&OTDR SFP TN11AST2 board (using
V2 optical the OSC&OTDR SFP V2
module) is added. optical module) are added.
2 Dependencies and
Limitations: The
restrictions on the input
power of lower than -39
dBm are updated in
configuration and
commissioning rules.
The setting The TN11AST2 board uses the 5.2 Manually Starting
description of OSC&OTDR SFP V2 optical Fiber Quality Monitoring:
Fiber Refractive module. Therefore, the fiber The setting description of
Index is added. quality monitoring function is Fiber Refractive Index is
enhanced. added.
The operations of The GUI of the fiber quality 5 Starting Fiber Quality
the fiber quality detection is updated. Monitoring (NCE) and 6
detection are Viewing and Analyzing
updated. Detection Results: The
involved operation steps
are updated.
The TN12ST2 board The TN12ST2 board is added The description of the
is added to support so that the fiber quality can TN12ST2 board is added.
the fiber quality be monitored online using
monitoring OSC signals.
function.
You can set the reference When the MUT_LOS 5.2 Manually Starting
curve of the online mode alarm is used to trigger Fiber Quality
and offline mode for fiber quality detection, Monitoring and 6
fiber quality detection. the offline mode Viewing and Analyzing
reference curve can be Detection Results:
preferentially used for Added the description of
detection. setting the reference
curve.
5.3 Triggering Fiber
Quality Detection by
Alarm: Added the
requirements for setting
the reference curve of
each alarm.
The operations of the The GUI of the fiber 5 Starting Fiber Quality
fiber quality detection quality detection is Monitoring (NCE) and
are updated. updated. 6 Viewing and
Analyzing Detection
Results: The involved
operation steps are
updated.
The TNF1AST4 board first The line fiber quality The entire chapter is
supports the feature from monitoring function is added.
this version. provided to remotely
detect the fiber status
online and help
maintenance personnel
rapidly discover and
rectify fiber quality
issues.
V100R019C10SPC300
Feature Reason for the Update Information Update
Update
V100R019C10
Feature Update Reason for the Information Update
Update
V100R019C10
Feature Reason for the Update Information Update
Update
Fiber quality detection can be started in any of the following modes: manually,
alarm-triggered, and periodically.
NOTE
● Historical Curve:
Occupied disk space (MB) = Space occupied by a historical curve of one fiber in the
default detection scenario (0.06 MB) x Maximum number of saved historical curves x
Number of fibers.
For example, if the maximum numbers of manually triggered, alarm-triggered, and
cyclical detection curves saved for a fiber are all set to 100, the occupied disk space is 18
MB (0.06 MB x 100 x 3).
● If both Report FIBER_BREAK_POS alarms at both ends and Merging
FIBER_BREAK_POS by optical cable label are enabled, a FIBER_BREAK_POS alarm is
reported at both ends of a broken fiber.
are normal, you can start fiber detection. When fiber connections are abnormal,
you can start port detection.
Precaution
When the OSN 8800/6800/3800/9800 TN12ST2 board uses Default Mode for
fiber quality monitoring, in case of a fiber environment change such as a fiber cut
or fiber insertion or removal, the user has to wait 10 minutes before obtaining the
latest detection results in the new fiber environment. During the wait duration,
the user cannot perform manual detection. If the user performs manual detection
in the wait duration, the user must wait 10 minutes again to obtain the latest
automatic detection results.
When the OSC board uses Default Mode or Online mode in Advanced Mode for
fiber quality monitoring:
● Due to the limitations of IEEE 1588V2 clocks, when the OSC board is used for
single-fiber dual-ended detection, the following requirements must be met.
Otherwise, monitoring cannot be started.
– No OSC_CLK_MISMATCH alarm is found on the network.
– If more than four OLA sites are deployed in an OMS, clock boards that
satisfy the OSC_CLK_MISMATCH alarm processing requirements need to
be configured at the next OLA site behind every four OLA sites.
– When using the Offline mode in Advanced Mode board for detection,
the OSC communication of the detection line is interrupted and the
OSC_LOS alarm is reported. When this occurs, non-GNEs may be
unreachable by the NMS, affecting functions such as DCN
communication, IEEE 1588v2 clock synchronization, and orderwire
phones.
NOTE
For the OSC_CLK_MISMATCH alarm processing method, see 8.1 OSC_CLK_MISMATCH (for
OSN 8800/6800/3800/9800) or 8.2 OSC_CLK_MISMATCH (for OSN 1800).
● Detection cannot be started if the optical module version of downstream
AST2 or AST4 board is OSC&OTDR SFP V1 and the input optical power is less
than –39 dBm.
● Detection cannot be started if the input optical power of the TNF1AST4/
TMB1AST2 board is less than –39 dBm.
● If only one reference curve is in online mode, the MUT_LOS alarm is not
affected by the downstream –39 dB optical power and triggers the fiber
quality detection.
● If online monitoring has been started for an OTS of an OMS but the
monitoring is not completed, online monitoring cannot be started for other
OTSs on the OMS; otherwise, IEEE 1588v2 clock synchronization is affected.
● If IEEE 1588v2 clock synchronization is also enabled, ensure that online
monitoring is started for no more than 10 spans on the entire network;
otherwise, IEEE 1588v2 clock synchronization is affected.
Context
Fiber quality monitoring can be performed in any of the following modes: Intra-
site Mode, Near-end Mode, Default Mode, Advanced Mode, Projector Mode
and Reference Mode. For the typical application scenario of each mode, see 5.7
Parameters: Starting Fiber Quality Detection.
NOTICE
If you use the following detection mode for fiber quality monitoring, the OSC
communication of the detection line is interrupted and the OSC_LOS alarm is
reported. When this occurs, non-GNEs may be unreachable by the NMS, affecting
functions such as DCN communication, IEEE 1588v2 clock synchronization, and
orderwire phones.
● For the OSN 8800/6800/3800/9800 TN12ST2 board, Offline mode under
Advanced Mode is used to perform fiber quality monitoring.
● For the TN11AST2/TN51AST2/TNG2AST2 board or TNF1AST4/TMB1AST2
board, Offline mode in Advanced Mode is used to perform fiber quality
monitoring.
Intra-site When a Raman board is used for fiber quality monitoring, Intra-site
Mode/ Mode and Near-end Mode are supported.
Near-end In this mode, the user only needs to select the corresponding mode
Mode in the NMS GUI without setting detection parameters. Then, the
system performs detection based on the default parameters.
● Intra-site Mode: Quickly detects whether intra-office fibers are
properly connected and whether fiber end faces are
contaminated.
● Near-end Mode: Quickly detects the quality of fibers within 30
km from the Raman board to identify the events that affect the
Raman gain.
Default When an OSC board is used for fiber quality monitoring, Default
Mode Mode is supported.
In this mode, the user only needs to select the corresponding mode
in the NMS GUI without setting detection parameters. Then, the
system performs detection based on the default parameters.
This mode is applicable to the scenario where the user does not
know fiber parameters and therefore a preliminary analysis is
performed on fibers based on the default parameters.
Monitori Description
ng Mode
Type
Advance Advanced Modes include the following: Online mode and Offline
d Mode mode.
● When a Raman board is used for fiber quality monitoring, only
Offline mode is supported.
● When an OSC board is used for fiber quality monitoring, Online
mode and Offline mode are supported. When services are
running properly, you are advised to select the Online mode to
ensure that services and OSC communication are not affected.
When a fault occurs on the optical fiber, you are advised to select
the Offline mode with the most powerful detection capability.
● In any mode, the user can select Pulse Width, and set
Measurement Range and Detection Duration as required to
identify fault points.
Referenc This mode is mainly used to compare detection results. In this mode,
e Mode the OptiX NetStar O&M component monitors fiber quality again
based on the same parameters used in a historical detection
operation so that the user can compare detection results.
Projector When an OSC board boards are used for detection, Projector Mode
Mode is supported.
In this mode, you do not need to set detection parameters. You only
need to select the corresponding mode on the NMS. The system
uses the fixed pulse width parameters of the small, medium, and
large groups for three times, and displays the three detection results
in the detection topology.
This mode applies to scenarios where both local fiber details and
remote fiber status are concerned.
Procedure
Step 1 Enter the Fiber Doctor main window.
● Method 1: Choose Configuration > WDM Optical Management > Fiber
Doctor from the main menu on the NCE Network Management app.
● Method 2: In the topology view on the NCE Network Management app, select
one inter-site long fiber, left-click it, and choose Detect Fiber Quality from
the shortcut menu that is displayed.
Step 2 Optional: Click Fiber Doctor and choose System Configuration from the drop-
down menu to configure the reference threshold for comparing detection results
in reference mode or historical data comparison mode. If the difference between
the comparison results exceeds the configured reference threshold, the comparison
results are highlighted in red.
NOTE
● Reflection change threshold: indicates the reference object for the difference between
the two Reflected Power values that are compared. The default value is 3.0 dB.
● Attenuation change threshold: indicates the reference object for the difference
between the two Attenuation values that are compared. The default value is 3.0 dB.
● Historical Curve: This parameter indicates the maximum number of manual detection
curves that can be saved for each port supporting fiber quality monitoring. The default
value is 100.
A greater number of detection curves requires more disk space.
Ensure that the server has sufficient disk space.
Occupied disk space (MB) = Space occupied by a historical curve of one fiber in the
default detection scenario (0.06 MB) x Maximum number of saved curves x Number of
fibers.
For example: If the maximum numbers of manually-triggered, alarm-triggered, and
cyclical detection curves are all set to 100, the occupied disk space is 18 MB (0.06 MB x
100 x 3).
Step 3 Click Fiber Doctor, choose Fiber Detection from the drop-down menu, and set
filter criteria.
Step 4 Click the Fiber Detection tab to view the filtering result.
NOTE
● The filter result can be displayed in a table. The fibers to be detected on the subnets,
sites, or NEs and more details about fiber parameters are displayed.
● In the filter results listed in a table, if Fiber Length (Designed Value) (km) of a fiber is
1.0 , the fiber length may not be configured.
● In the filter results listed in a table, if Reference Curve of a fiber is Complete or
Incomplete, reference curves are configured for all or some detection ports of the fiber.
● In the filter result listed in a table, if the State of a fiber is Enable, the fiber supports
the detection and one license will be used. Set State to Disable. One license will be
released.
Step 5 In the table, click a detected fiber and set monitoring parameters.
1. If both the source and sink NEs of the fiber to be detected have detection
ports, you can select Bidirectional Detection in the Signal Flow Diagram
dialog box that is displayed. You can select the source and sink boards for
fiber detection at the same time and start bidirectional detection. The
bidirectional detection results can be merged. If you do not select
Bidirectional Detection, the system performs unidirectional detection only
through the board at the source end by default.
4. In the Detection Mode area on the right, set the detection mode and
parameters. For the parameter settings of boards in different modes, see 5.7
Parameters: Starting Fiber Quality Detection. For the detection capabilities
in different modes, see 4.2 Specifications.
NOTE
– In the case of bidirectional detection, you need to set the detection modes and
parameters for the source and sink boards. In the case of unidirectional detection,
you only need to set the detection mode and parameters for the source board.
– Different detection boards support different detection modes and parameters. If
the same detection modes and parameters are used for the bidirectional detection,
the detection modes and parameters must be supported by detection boards at
both source and sink ends.
– Use Intra-site Mode/Near-end Mode/Default Mode/Projector Mode
monitoring.
NOTE
NOTE
NOTE
NOTE
– Reference mode can be used to detect the quality of a fiber only when the fiber is
detected and the detection result curve is used as the reference curve (namely,
Reference Curve of the fiber is Complete or Incomplete).
– When viewing detection results, you can click Set As Reference Curve on the GUI
to configure a detection result curve as the reference curve. Currently, a maximum
of one online detection and one offline detection reference curve can be set for
each optical fiber. For the reference curve of the same type of detection mode, the
system retains only the latest setting record.
5. Optional: If is used for fiber quality monitoring, you can set Fiber Refractive
Index (value range: 1.40000-1.69999) in the Advance Setting area to
7. Click Start. The system automatically sets State of the detected fibers to
Enable and starts the detection.
----End
Result
● Viewing the current detection results
After fiber quality monitoring is manually started, the detection progress and
results are displayed in Detection Result area. For successful detection
records, click View Result, you can view the detection curve, events. For
details, see 6 Viewing and Analyzing Detection Results.
Choose Fiber Doctor > Historical Detection Records. Set filter conditions
such as Board and Trigger Mode to filter the manual detection results of the
fiber, you can view the detection curve and event of a successful detection
record. For details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to
set filter conditions or search for desired information by keywords. Detailed information
in historical records is not updated in real time. To filter detection records by NE
information, set filter criteria or search keywords based on the NE information when the
detection is started.
● You are advised to select Display only the curve generated after successful detection
to filter the records about successful detection.
● You can view any filtered detection record.
Procedure
Step 1 Enter the Fiber Doctor main window.
Choose Configuration > WDM Optical Management > Fiber Doctor from the
main menu on the NCE Network Management app.
Step 2 Optional: Click Fiber Doctor and choose System Configuration from the drop-
down menu to configure the reference threshold for comparing detection results
in reference mode or historical data comparison mode. If the difference between
the comparison results exceeds the configured reference threshold, the comparison
results are highlighted in red.
NOTE
● Reflection change threshold: indicates the reference object for the difference between
the two Reflected Power values that are compared. The default value is 3.0 dB.
● Attenuation change threshold: indicates the reference object for the difference
between the two Attenuation values that are compared. The default value is 3.0 dB.
● Historical Curve: This parameter indicates the maximum number of manual detection
curves that can be saved for each port supporting fiber quality monitoring. The default
value is 100.
A greater number of detection curves requires more disk space.
Ensure that the server has sufficient disk space.
Occupied disk space (MB) = Space occupied by a historical curve of one fiber in the
default detection scenario (0.06 MB) x Maximum number of saved curves x Number of
fibers.
For example: If the maximum numbers of manually-triggered, alarm-triggered, and
cyclical detection curves are all set to 100, the occupied disk space is 18 MB (0.06 MB x
100 x 3).
Step 3 Click Fiber Doctor, choose Fiber Detection from the drop-down menu, and set
filter criteria.
Step 4 Click the Port Detection tab to view the filtering result.
NOTE
● The filter result can be displayed in a table. The ports to be detected on the subnets,
sites, or NEs and more details about port parameters are displayed.
● In the filter results listed in a table, if Fiber Length (km) of a fiber is 1.0 , the fiber
length may not be configured.
● In the filter results listed in a table, if Reference Status of a port is Complete, reference
curves are configured for that port.
● In the filter result listed in a table, if the Enabling Status of a port is Enable, the port
supports the detection and one license will be used. Set Enabling Status to Disable.
One license will be released.
Step 5 In the table, click a detected fiber and set monitoring parameters.
1. In the Detection Mode area on the right, set the detection mode and
parameters. For the parameter settings of boards in different modes, see 5.7
Parameters: Starting Fiber Quality Detection. For the detection capabilities
in different modes, see 4.2 Specifications.
NOTE
– In the case of port detection, you only need to set the detection mode and
parameters for the source board.
– Different detection boards support different detection modes and parameters.
– Use Intra-site Mode/Near-end Mode/Default Mode/Projector Mode
monitoring.
NOTE
NOTE
NOTE
NOTE
– Reference mode can be used to detect the quality of a port only when the port is
detected and the detection result curve is used as the reference curve (namely,
Reference Status of the fiber is Complete).
– When viewing detection results, you can click Set As Reference Curve > OK on the
GUI to configure a detection result curve as the reference curve. Currently, a
maximum of one online detection and one offline detection reference curve can be
set for each optical port. For the reference curve of the same type of detection
mode, the system retains only the latest setting record.
2. Optional: If OSC board is used for fiber quality monitoring, you can set Fiber
Refractive Index (value range: 1.40000-1.69999) in the Advance Setting area
to improve the accuracy of small-pulse-width and high-precision detection. In
other situations, the setting of Fiber Refractive Index is invalid.
4. Click Start. The system automatically sets State of the detected fibers to
Enable and starts the detection.
----End
Result
● Viewing the current detection results
After fiber quality monitoring is manually started, the detection progress and
results are displayed in Detection Result area. For successful detection
records, click View Result, you can view the detection curve, events. For
details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to
set filter conditions or search for desired information by keywords. Detailed information
in historical records is not updated in real time. To filter detection records by NE
information, set filter criteria or search keywords based on the NE information when the
detection is started.
● You are advised to select Display only the curve generated after successful detection
to filter the records about successful detection.
● You can view any filtered detection record.
Prerequisites
● The user must be an NMS user with "Maintainer Group" rights or higher.
● Fiber quality detection has been manually started and a reference curve has
been configured. For details, see 5.2 Manually Starting Fiber Quality
Monitoring.
– For the SPAN_LOSS_EXCEED_EOL, SPAN_LOSS_UPPER_GAIN, and
SPAN_LOSS_LOWER_GAIN alarms, set a reference curve whose Detection
Mode is online.
– For the MUT_LOS alarm, there is no requirement for the Detection Mode
of the reference curve. You are advised to set a reference curve whose
Detection Mode is offline. The system preferentially uses the Detection
Mode and Detection Parameters that are the same as the reference
curve in offline mode to trigger fiber quality detection.
● NMS is reporting SPAN_LOSS_EXCEED_EOL, SPAN_LOSS_UPPER_GAIN,
SPAN_LOSS_LOWER_GAIN or MUT_LOS alarm.
Background Information
Currently, the alarms listed in Table 5-2 can trigger fiber quality detection.
Alarm Description
SPAN_LO Indicates that the actual span loss exceeds the EOL value.
SS_EXCE
ED_EOL
Alarm Description
SPAN_LO Indicates that the actual span loss exceeds the gain compensation
SS_UPPE value and the value of Line Attenuation Compensation Threshold
R_GAIN (default value: 2 dB).
SPAN_LO Indicates that the actual span loss is less than the gain
SS_LOW compensation value and the value of Line Attenuation
ER_GAIN Compensation Threshold (default value: 2 dB).
NOTE
● After MUT_LOS alarm detection is enabled, detection is triggered about 8 minutes after the
MUT_LOS alarm is generated if the configured reference curve is the detection curve of the
OSN 9800/8800/6800/3800 TN12ST2 and the Detection Mode is Default Mode. If the
configured reference curve is the detection curve of the TN11AST2/TN51AST2/TNG2AST2/
TNF1AST4/TMB1AST2 board, detection is triggered immediately after the MUT_LOS alarm is
generated.
Procedure
Step 1 Enter the Fiber Doctor main window.
● Method 1: On the main menu of the NMS, choose Configuration > WDM
Optical Management > Fiber Doctor.
● Method 2: In the topology of the NMS, select one inter-site long fiber, left-
click it, and choose Detect Fiber Quality from the shortcut menu that is
displayed.
Step 2 Choose Fiber Doctor > System Configuration to enable alarm monitoring and
see Table 5-2 to select the required alarm for triggering fiber quality detection.
NOTE
Historical Curve: This parameter indicates the maximum number of manual detection
curves that can be saved for each port supporting fiber quality monitoring. The default value is
100.
A greater number of detection curves requires more disk space. Ensure that the server has
sufficient disk space.
Occupied disk space (MB) = Space occupied by a historical curve of one fiber in the default
detection scenario (0.06 MB) x Maximum number of saved curves x Number of fibers.
For example: If the maximum numbers of manually-triggered, alarm-triggered, and cyclical
detection curves are all set to 100, the occupied disk space is 18 MB (0.06 MB x 100 x 3).
Optional. This parameter indicates the maximum number of manual detection curves that can
be saved for each port supporting fiber quality detection. The default value is 100.
----End
Result
Choose Fiber Doctor > Historical Detection Records. Set filter conditions such as
Board and Trigger Mode to filter the alarm-triggered detection results of the
fiber. You can view the detection curve and event of a successful detection record.
For details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to set
filter conditions or search for desired information by keywords. Detailed information in
historical records is not updated in real time. To filter detection records by NE information,
set filter criteria or search keywords based on the NE information when the detection is
started.
● You are advised to select Display only the curve generated after successful detection to
filter the records about successful detection.
● You can view any filtered detection record.
Result
Choose Fiber Doctor > Historical Detection Records. Set filter conditions such as
Board and Trigger Mode to filter the alarm-triggered detection results of the
fiber. You can view the detection curve and event of a successful detection record.
For details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to
set filter conditions or search for desired information by keywords. Detailed information
in historical records is not updated in real time. To filter detection records by NE
information, set filter criteria or search keywords based on the NE information when the
detection is started.
● You are advised to select Display only the curve generated after successful detection
to filter the records about successful detection.
● You can view any filtered detection record.
Prerequisites
● The user must be an NMS user with "Maintainer Group" rights or higher.
● Fiber quality monitoring has been manually started and a reference curve has
been configured, and the Detection Mode parameter of the reference curve
cannot be set to offline mode. For details, see 5.2 Manually Starting Fiber
Quality Monitoring.
Procedure
Step 1 Enter the Fiber Doctor main window.
● Method 1: On the main menu of the NMS, choose Configuration > WDM
Optical Management > Fiber Doctor.
● Method 2: In the topology of the NMS, select one inter-site long fiber, left-
click it, and choose Detect Fiber Quality from the shortcut menu that is
displayed.
Step 2 Choose Fiber Doctor > System Configuration to set the number of saved periodic
detection curves.
NOTE
Historical Curve: This parameter indicates the maximum number of manual detection curves
that can be saved for each port supporting fiber quality monitoring. The default value is 100.
NOTE
During fiber selection, you can click next to the table heading Fiber Name to select all
fibers in the current list, or click in front of each fiber to select the fibers one by one.
Step 4 Start periodic detection and set the validity period and detection interval.
NOTE
----End
Result
OSC boards are used for fiber quality detection, if a fiber cut occurs, the
FIBER_BREAK_POS alarm is proactively reported to the NMS, indicating the
position of the fiber cut.
NOTE
● If the total line loss exceeds the dynamic range of the current detection pulse width, the
FIBER_BREAK_POS alarm may not be reported. You are advised to use the maximum pulse
width or an optical time domain reflectometer (OTDR) for detecting fiber quality.
● After the fiber is repaired, the FIBER_BREAK_POS alarm is not automatically cleared. It is
cleared after you reset the reference curve and perform a manual detection (in reference
mode) or periodic detection.
Choose Fiber Doctor > Historical Detection Records. Set filter conditions such as
Board and Trigger Mode to filter the periodic detection results of the fiber. You
can view the detection curve and event of a successful detection record. For
details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to set
filter conditions or search for desired information by keywords. Detailed information in
historical records is not updated in real time. To filter detection records by NE information,
set filter criteria or search keywords based on the NE information when the detection is
started.
● You are advised to select Display only the curve generated after successful detection to
filter the records about successful detection.
● You can view any filtered detection record.
Procedure
Step 1 Enter the Fiber Doctor main window.
● Method 1: Choose Configuration > WDM Optical Management > Fiber
Doctor from the main menu on the NCE Network Management app.
Step 2 Optional: Click Fiber Doctor and choose System Configuration from the drop-
down menu to configure the reference threshold for comparing detection results
NOTE
● Reflection change threshold: indicates the reference object for the difference between
the two Reflected Power values that are compared. The default value is 3.0 dB.
● Attenuation change threshold: indicates the reference object for the difference
between the two Attenuation values that are compared. The default value is 3.0 dB.
● Historical Curve: This parameter indicates the maximum number of manual detection
curves that can be saved for each port supporting fiber quality monitoring. The default
value is 100.
A greater number of detection curves requires more disk space.
Ensure that the server has sufficient disk space.
Occupied disk space (MB) = Space occupied by a historical curve of one fiber in the
default detection scenario (0.06 MB) x Maximum number of saved curves x Number of
fibers.
For example: If the maximum numbers of manually-triggered, alarm-triggered, and
cyclical detection curves are all set to 100, the occupied disk space is 18 MB (0.06 MB x
100 x 3).
Step 3 Click Fiber Doctor, choose Fiber Detection from the drop-down menu, and set
filter criteria.
Step 4 Click the Fiber Detection tab to view the filtering result.
NOTE
● The filter result can be displayed in a table. The fibers to be detected on the subnets,
sites, or NEs and more details about fiber parameters are displayed.
● In the filter results listed in a table, if Fiber Length (Designed Value) (km) of a fiber is
1.0 , the fiber length may not be configured.
● In the filter results listed in a table, if Reference Curve of a fiber is Complete or
Incomplete, reference curves are configured for all or some detection ports of the fiber.
● In the filter result listed in a table, if the State of a fiber is Enable, the fiber supports
the detection and one license will be used. Set State to Disable. One license will be
released.
Step 5 In the table, click multiple detected fibers and set monitoring parameters.
----End
Result
Viewing historical detection results
Choose Fiber Doctor > Historical Detection Records. Set filter conditions such as
Board and Trigger Mode to filter the manual detection results of the fiber, you
can view the detection curve and event of a successful detection record. For
details, see 6 Viewing and Analyzing Detection Results.
NOTE
● To filter the historical records, click a column with symbol in the historical records to
set filter conditions or search for desired information by keywords. Detailed information
in historical records is not updated in real time. To filter detection records by NE
information, set filter criteria or search keywords based on the NE information when the
detection is started.
● You are advised to select Display only the curve generated after successful detection
to filter the records about successful detection.
● You can view any filtered detection record.
Performance Parameters
The performance parameters of fiber quality detection mainly refer to Pulse
Width, Measurement Range, and Detection Duration. To use Advanced Mode
to detect fiber quality, you can customize performance parameters to locate faults
at different locations.
Performa Description
nce
Parameter
Pulse Width of detection light pulses. When the pulse width increases,
Width the light emitting time increases and consequently a larger energy
is obtained. This means that a larger dynamic range can be
acquired but also larger dead zones will result.
Measurem Maximum distance for the line fiber quality detection function to
ent Range sample data. The distance determines the sampling resolution.
NOTE
The total fiber loss will affect the detection distance and the dynamic range
is fixed for the same detection mode. Therefore, a larger total fiber loss
indicates a smaller detection distance. To maximize the detection capability,
the value of Measurement Range is generally greater than the actual
detection capability. For example, if the TN12RAU1/TN12RAU2/TN11SRAU/
TN51RPC/TN97RPC/TNG2WRPC/TN52SRAPXF/TNG2SRAPXF/TNG3SRAPXF
board is used to perform fiber quality detection, when the detection mode
(with Pulse Width set to 20000 ns) is selected, the actual detection
capability is about 60 km, while the maximum value of Measurement
Range is 80 km. When the fault point is beyond the permitted distance
range of a detection mode and cannot be located, select a detection mode
that provides a larger pulse width to locate the fault point.
During online fiber quality detection when the Raman laser is turned on, energy exchange will
occur due to the Raman effect on the detection light in the fiber. The energy exchange will
affect the actual detection distance. For G.652 fibers, the detection distance will be shortened by
about 20%. This value is 30% for LEAF fibers, and 40% for G.653 fibers.
Near- - 400 Defa Defa When the Raman gain is excessively low
end ult: ult: and an OA_Low_Gain alarm is reported,
Modea 30 60 you can select this mode to quickly detect
the quality of fibers within 30 km from
the Raman board to identify the events
affecting the Raman gain.
Advan Offli 25 2-10 40-6 Using a longer detection time, this mode
ced ne Defa 5 detects the quality of fibers within 2 km
Mode mod ult: Defa from the Raman board after abnormal
e 2 ult: events are found through the line fiber
60 quality detection in near-end mode,
therefore improving the measurement
precision.
25 10-130 60-300
Default: 30 Default: 120
50 20-150 60-300
Default: 30 Default: 120
a: Except for the Default Mode, all other modes will interrupt OSC
communication of the detection line and the OSC_LOS alarm is reported, and
affect functions such as DCN communication, IEEE 1588v2 clock synchronization
and orderwire phones.
b: A larger pulse width brings a longer detection distance but lower event
precision. A smaller pulse width brings a shorter detection distance but better
event precision.
c: Events in the maximum dynamic range corresponding to a pulse width can be
reported normally. The actual distance corresponding to the dynamic range is
calculated based on the fiber attenuation coefficient. The value of
Measurement Range must be equal to or slightly greater than the actual fiber
length regardless of the detection on the near–end fiber quality or the entire
fiber quality; otherwise, an event that cannot be displayed in the detection
curve may be falsely reported. If you do not know the actual fiber length, you
are advised to set Pulse Width and Measurement Range to the maximum
values for first detection to obtain the actual fiber length and then perform
detection again using accurate parameters.
d: In the same pulse width, a longer detection time means a larger dynamic
range and a longer detection distance.
25 ● TN11AST2/ 120–600
TN51AST2/ Default: 240
TNG2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
10–130
● TNF1AST4/
TMB1AST2
/
TMB2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
10–60
Default: 30
50 ● TN11AST2/ 120–600
TN51AST2/ Default: 240
TNG2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
20–150
● TNF1AST4
whose
optical
modules
are
OSC&OTD
R SFP V2:
20–130
● TMB1AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
20–60
Default: 30
25 ● TN11AST2/ 60–300
TN51AST2/ Default: 120
TNG2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
10–130
● TNF1AST4/
TMB1AST2
/
TMB2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
10–60
Default: 30
50 ● TN11AST2/ 60–300
TN51AST2/ Default: 120
TNG2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
20–150
● TNF1AST4/
TMB1AST2
/
TMB2AST2
whose
optical
modules
are
OSC&OTD
R SFP V2:
20–130
Default: 30
a: Only the Offline mode in Advanced Mode will interrupt OSC communication
of the detection line and the OSC_LOS alarm is reported, and affect functions
such as DCN communication, IEEE 1588v2 clock synchronization and orderwire
phones.
b: A larger pulse width brings a longer detection distance but lower event
precision. A smaller pulse width brings a shorter detection distance but better
event precision. You can set TN11AST2 to 10 ns, 25 ns, or 50 ns only when
TNF1AST4 or Pulse Width is used for fiber quality detection and the optical
module on the board is OSC&OTDR SFP V2.
c: Events in the maximum dynamic range corresponding to a pulse width can be
reported normally. The actual distance corresponding to the dynamic range is
calculated based on the fiber attenuation coefficient. The value of
Measurement Range must be equal to or slightly greater than the actual fiber
length regardless of the detection on the near-end fiber quality or the entire
fiber quality; otherwise, an event that cannot be displayed in the detection
curve may be falsely reported. If you do not know the actual fiber length, you
are advised to set Pulse Width and Measurement Range to the maximum
values for first detection to obtain the actual fiber length and then perform
detection again using accurate parameters.
d: In the same pulse width, a longer detection time means a larger dynamic
range and a longer detection distance.
After the detection is completed, you can locate the fault points and analyze the
fault causes using the detection result curve and topology.
Prerequisites
The user must be an NMS user with Maintainer Group rights or higher.
Navigation Path
1. On the Fiber Detection main window, click a fiber whose State is Enable.
2. In the displayed Historical Detection Records area, click View Result in
Operation column.
GUI Example
NOTE
This document uses the reference mode and bidirectional detection result as an example. Green
indicates the current event, and blue indicates the reference event.
● For the unidirectional detection result, only the detection topology of the detection port
direction of the selected fiber source end is displayed.
● For the detection result in non-reference mode, only the current detection fiber and event
list are displayed.
Operation Description
No. Area Description
Detection You can view basic information including the optical fiber
fiber area detection port and detection parameters.
● When the OSN 9800 TN12ST2 board is used for
detection using Default Mode, the displayed value of
Detection Duration is the duration for continuous
detection in stable environment. Once the environment
changes, the FD starts detection and accumulates the
detection duration again. The previous detection
duration will be cleared.
Detection You can view the fiber detection events at the locations
topology with different distances from the detection port.
display ● If Detection mode is set to Projector Mode, the
area detection events of all pulse widths in the same direction
are combined for display in the Detection Topo area.
● You can scroll the mouse to zoom in or out on the
detection topology.
● You can click Landmark in this area to identify specific
geographical information corresponding to a location of
the forward or reverse fiber ruler and mark it with the
icon in the topology, facilitating fault location during
O&M. You can right-click a landmark and choose Delete
or Edit from the shortcut menu.
Event list You can view details about the detection events.
area Event definition:
● When an OSC board is used for fiber detection, events in
which the reflection value is less than -55 dB and the
absolute value of the insertion loss is less than 0.15 dB
are events related to splicing points, and other events
are events related to connectors.
● When a Raman board is used for fiber detection, events
in which the reflection value is less than or equal to -50
dB are events related to splicing points, and other events
are events related to connectors.
NOTE
● If the attenuation of an event is greater than 5 dB or the
reflective value of the event is greater than -30 dB, it is
equivalent that a fiber cut occurs, and the subsequent events on
the related fiber cannot be reported except that the reflective
value of the events is greater than -30 dB.
● If one point on a fiber is the interconnection point of two types
of fibers, the attenuation of the event may be a negative value.
● To ensure reporting of all events, some small-attenuation
(within 2 dB) events may be falsely reported on capability edge
points.
● When an OSC board is used for fiber detection, no attenuation
is reported in a fiber-end event.
● When a Raman board is used for fiber detection, events near
the noise zone are not reported.
Event operation:
● For an event related to connectors or splicing points,
click in the LandMark column to mark the specific
geographic information about the events. The
information about the landmarks is displayed in
Detection Topo and Event List, and the icon is used
for easy identification, facilitating fault locating during
the O&M process.
● Click Add to add an event such as Connector or
Splicing Point, which contains information about
Position. New events are displayed in Detection Topo
and Event List, and the icon is used for easy
identification, facilitating fault locating during the O&M
process.
● For a user-defined event, select the icon before the
event and click Delete to delete the event or click Edit
to modify the position or type of the event.
● Events that are automatically generated during the
detection cannot be deleted, and positions and types of
the events also cannot be modified.
● Click Export and select Save the detection result as an
event list to save the events in the current detection
Prerequisites
The user must be an NMS user with Maintainer Group rights or higher.
Navigation Path
1. On the Fiber Detection main window, click a fiber whose State is Enable.
2. In the displayed Historical Detection Records area, click View Result in
Operation column.
3. Click the Detection Curve tab.
GUI Example
NOTE
This document uses the reference mode and bidirectional detection result as an example. Red
indicates the current curve, and blue indicates the reference curve.
● For the unidirectional detection result, only the detection curve (forward curve) of the
detection port at the source end of the selected fiber are displayed.
● For the detection result in non-reference mode, only the current detection fiber, detection
curve, and detection event list are displayed.
● The detection curve supports noise reduction. The curve after noise reduction can better
display a valid waveform. To enable the noise reduction function, click Fiber Doctor,
choose System Configuration from the drop-down menu, and select Enable for Detection
curve denoising in the Others area.
Operation Description
No. Area Description
Detection You can view basic information including the optical fiber
fiber area detection port and detection parameters.
● When the OSN 9800/8800/6800/3800 TN12ST2 board is
used for detection using Default Mode, the displayed
value of Detection Duration is the duration for
continuous detection in stable environment. Once the
environment changes, the FD starts detection and
accumulates the detection duration again. The previous
detection duration will be cleared.
Detection You can view the change curve of the optical power at the
curve locations with different distances from the detection port.
display ● After you click the event point on the detection curve,
area the fiber distance and relative power of the
corresponding location are automatically displayed. In
addition, corresponding event information is highlighted
in Event List.
● You can click in this area to expand the detection
curve and click to zoom out the detection curve.
● If Detection mode is set to Projector Mode, the
Detection Curve area displays only the detection curve
with the minimum pulse width by default. You can select
another pulse width from the drop-down list box in the
Detection Curve area to view the detection curves of
other pulse widths.
Detection After the detection curve is expanded, only part of the curve
eagle eye can be displayed in the detection curve area. In this case,
area you can view the overall curve in the eagle eye area and
move the eagle eye position to quickly focus on the desired
detection curve range.
You can click in the area to expand the eagle eye range
and click to shrink the eagle eye range.
Measure You can view the fiber length, attenuation, and latency in
ment this area.
result - indicates the initial value and / indicates an invalid value.
area For Fiber Attenuation, / may also indicate that the
detection result is beyond the dynamic range.
Event list You can view details about the detection events.
area Event definition:
● When an OSC board is used for fiber detection, events in
which the reflection value is less than -55 dB and the
absolute value of the insertion loss is less than 0.15 dB
are events related to splicing points, and other events are
events related to connectors.
● When a Raman board is used for fiber detection, events
in which the reflection value is less than or equal to -50
dB are events related to splicing points, and other events
are events related to connectors.
NOTE
● If the attenuation of an event is greater than 5 dB or the
reflective value of the event is greater than -30 dB, it is
equivalent that a fiber cut occurs, and the subsequent events on
the related fiber cannot be reported except that the reflective
value of the events is greater than -30 dB.
● If one point on a fiber is the interconnection point of two types
of fibers, the attenuation of the event may be a negative value.
● To ensure reporting of all events, some small-attenuation
(within 2 dB) events may be falsely reported on capability edge
points.
● When an OSC board is used for fiber detection, no attenuation is
reported in a fiber-end event.
● When a Raman board is used for fiber detection, events near the
noise zone are not reported.
Event operation:
● For an event related to connectors or splicing points,
click in the LandMark column to mark the specific
geographic information about the events. The
information about the landmarks is displayed in
Detection Topo and Event List, and the icon is used
for easy identification, facilitating fault locating during
the O&M process.
● Click Add to add an event such as Connector or Splicing
Point, which contains information about Position. New
events are displayed in Detection Topo and Event List,
and the icon is used for easy identification, facilitating
fault locating during the O&M process.
● For a user-defined event, select the icon before the
event and click Delete to delete the event or click Edit to
modify the position or type of the event.
● Events that are automatically generated during the
detection cannot be deleted, and positions and types of
the events also cannot be modified.
● Click Export and select Save the detection result as an
event list to save the events in the current detection
Prerequisites
The user must be an NMS user with Maintainer Group rights or higher.
Procedure
● Editing a single remark:
– Method 1: On the Fiber Detection page, select a fiber record. In the
displayed Historical Detection Records area, select a detection record. In
the Remarks column, view or edit historical remarks.
Schematic Diagram
Description
The large reflection peak at about 9 km indicates that a PC/UPC fiber is cut. In this
scenario, the reflection value is generally greater than –20 dB.
Schematic Diagram
Description
The figure is the schematic diagram for an APC fiber cut event that occurs at
about 5.2 km. In this scenario, the reflective value is generally less than -45 dB but
the attenuation is greater than 5 dB.
Schematic Diagram
Description
The large reflection peak at about 0.2 km indicates that the fiber end face is
contaminated. In this scenario, the reflection value is generally greater than -43
dB.
Schematic Diagram
Description
The large reflection peak at about 0.45 km indicates that the fiber end face is
burnt. In this scenario, the reflection value is generally greater than –40 dB.
Schematic Diagram
Description
The figure is the schematic diagram for an event indicating a large insertion loss
on a connector at about 1.2 km. The insertion loss shown in the blue circle is close
to 3 dB.
Schematic Diagram
Description
The figure is the schematic diagram for an interconnection event between G.652
and G.653 fibers. The interconnection point is at about 0.25 km. In this scenario, a
negative insertion loss will be reported.
6.5 FAQs
This section describes methods of handling common problems about line fiber
quality monitoring.
Problem Description
When the TN12ST2 board is used to automatically detect line fiber quality, the
near-end detection curve undergoes an undershoot. As a result, an alarm is falsely
reported. The following figure shows the symptom.
Problem Analysis
A detection curve undershoot is an abnormal event, and the root cause is that the
end face where the undershoot occurs is contaminated.
Solution
Clean the contaminated end face first.
Problem Description
When the TN12ST2 board is used to automatically detect line fiber quality, the
near-end detection curve becomes abnormal. The following figure shows the
symptom.
Problem Analysis
The end faces of the near-end connectors are contaminated.
Solution
Clean the end faces of the near-end connectors.
6.5.1.3 When the TN12ST2 Board Is Used to Automatically Detect Line Fiber
Quality, the Reflection Peak of the Detection Curve at the End Has a Slow
Decrease, Which Conflicts with the Results of Detection Using a Meter
Problem Description
When a TN12ST2 board is used to automatically detect line fiber quality, the
reflection peak in the end detection curve decreases slowly, which is inconsistent
with the detection result of a test meter. The following figure shows the fault
symptom.
Problem Analysis
The principles of automatic detection are different from those of meter detection.
The difference between their modules causes different detection results. However,
this issue does not affect the actual application.
Solution
No solution needs to be taken.
6.5.1.4 When a Raman Board Is Configured and the TN12ST2 Board Is Used
to Automatically Monitor Fiber Quality, the Detection Curve at the End Goes
Up, Affecting Event Reporting
Problem Description
When a Raman board is configured and the TN12ST2 board is used to
automatically monitor fiber quality, the detection curve at the end goes up,
affecting event reporting. The following figure shows the fault symptom.
Problem Analysis
When a Raman board is configured, the fiber probe light of the TN12ST2 board
will be amplified by the Raman board. As a result, the detection curve at the end
will go up, which may affect event reporting.
Solution
No solution needs to be taken.
Problem Description
When the Raman laser is turned on and the TNG2RPC board is used to monitor
fiber quality, the detection curve at the transmit end is saturated or bent, affecting
event reporting. The following figure shows the symptom.
Problem Analysis
When a Raman board is configured, the fiber probe light of the TNG2RPC board
will be amplified by the Raman board. As a result, the detection curve is saturated
or bent, which may affect event reporting.
Solution
You are advised to turn off the Raman laser and use Offline in Advanced Mode
to monitor fiber quality.
Problem Description
After I start fiber quality detection in the FD system, a failure message is
displayed. After I move the cursor to the detection record, no failure cause is
displayed. After I restart detection, a success message is displayed.
Problem Analysis
During the first detection, the system time of the client may be changed. As a
result, the FD system regards that the client is unstable and determines that the
operation times out, and therefore displays a failure message falsely. In this case,
even if the detection is successful, a failure message is displayed but no failure
cause is displayed. After detection is restarted, the system time of the client is
stable and therefore a success message is displayed.
Solution
Do not change the system time of the client during fiber quality detection.
This section describes the standard and protocol that the Fiber Doctor (FD) system
complies with.
The following lists the standard and protocol with which the FD system complies:
● GR-196-CORE: Generic Requirements for Optical Time Domain Reflectometer
(OTDR)-Type Equipment
● SR-4731: Optical Time Domain Reflectometer (OTDR) Data Format
8 Alarm Description
Attribute
Alarm Severity Alarm Type
Warning Communication
Parameters
None
● If the system does not require the IEEE 1588 clock function, replacing the OSC
board (TN11AST2/TN51AST2/TNG2AST2) has no impact on services.
● If the system needs to enable the IEEE 1588 clock function, the system control
and cross-connect board or clock board needs to be replaced, which has
impact on services.
Possible Causes
The prerequisites for generating the OSC_CLK_MISMATCH alarm are that the IEEE
1588 protocol is enabled on the TN11AST2/TN51AST2/TNG2AST2 board and the
board is in the clock source priority table. The possible causes of the alarm are as
follows:
Procedure
Step 1 On the NCE, query the board that reports this alarm.
● If the system does not require the IEEE 1588 clock function, you are advised
to replace the OSC (TN11AST2/TN51AST2/TNG2AST2) board or disable the
IEEE 1588 clock function of the TN11AST2/TN51AST2/TNG2AST2 board.
● If the system needs to enable the IEEE 1588 clock function, replace the system
control and cross-connect board or clock board that reports this alarm. The
configurations of the clock board to be replaced are as follows:
a. For an OptiX OSN 8800 T16 subrack, replace the system control and
cross-connect board using a board except TN16XCH, TN16SCC, or
TN16UXCM, and ensure that no clock board is available on the subrack.
b. For an OptiX OSN 8800 T32 subrack, replace the TN52STG board using
TN54STG.
c. For an OptiX OSN 8800 T64 subrack, replace the TNK2STG board using
TNK3STG.
d. For an OptiX OSN 6800 subrack, replace the TN11STG or TN12STG board
using TN13STG.
e. For the UPS subrack, replace the TN11STG or TN12STG board using
TN13STG.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei
engineers to handle the alarm.
----End
Related Information
None
Attribute
Alarm Severity Alarm Type
Warning Communication
Parameters
None
Possible Causes
The prerequisites for generating the OSC_CLK_MISMATCH alarm are that the IEEE
1588 protocol is enabled on the TNF1AST4/TMB1AST2 board and the board is in
the clock source priority table. The possible causes of the alarm are as follows:
● The TNF1UXCL or TNF1UXC board is installed on the OptiX OSN 1800 I/II
Packet subrack.
● The TNF5UXCM, TNF5UXCME or TNF5XCH board is installed on the OptiX
OSN 1800 V Packet Enhanced subrack.
Procedure
Step 1 On the NCE, query the board that reports this alarm.
● If the system does not require the IEEE 1588 clock function, you are advised
to replace the OSC (TNF1AST4/TMB1AST2) board or disable the IEEE 1588
clock function of the TNF1AST4/TMB1AST2 board.
● If the system needs to enable the IEEE 1588 clock function, replace the system
control and cross-connect board or clock board that reports this alarm. The
configurations of the clock board to be replaced are as follows:
a. For an OptiX OSN 1800 I/II Compact subrack, replace the time board
using F3SCC.
b. For an OptiX OSN 1800 V Packet Enhanced subrack, replace the time
board using TNZ5UXCMS.
Step 2 Check whether the alarm is cleared. If the alarm persists, contact Huawei
engineers to handle the alarm.
----End
Related Information
None
8.3 FIBER_BREAK_POS
Description
Fiber cut location. After the MUT_LOS alarm is set to trigger the fiber quality
detection, the MUT_LOS alarm automatically triggers the fiber detection when the
fiber is disconnected. The system compares the reflection and attenuation values
of the new event points or end event points on the current curve and reference
curve to determine the fiber cut position and reports this alarm.
Attribute
Alarm Severity Alarm Type
Warning Equipment
Alarm Reporting
You can set alarm reporting parameters on the System Configuration page.
1. Choose Configuration > WDM Optical Management > Fiber Doctor from
the main menu.
2. Click Fiber Doctor, choose System Configuration from the drop-down menu,
and set alarm reporting parameters.
Parameters
When you view an alarm on the network management system, select the alarm.
In the Alarm Details field display the related parameters of the alarm. The alarm
parameters are in the following format: Alarm Parameters (hex): parameter1
parameter2...parameterN. For details about each parameter, refer to the following
table.
Possible Causes
● A fiber cut occurs, triggering the Fiber Doctor to start detection. After the
fiber cut location is detected, this alarm is reported.
● The reference curve is not reset after the fiber repair, and the alarm is not
eliminated.
Procedure
Step 1 Check whether the MUT_LOS alarm is reported. If yes, clear the alarm according
to the handling procedure of the alarm.
Step 2 Based on the fiber cut location detected by the Fiber Doctor, check whether the
fiber connection is normal on the NCE.
Step 3 Check whether fibers are aging, bent, or broken. If yes, coil the fibers again or
replace the faulty fibers.
Step 4 Check whether the fiber connectors are clean. If a fiber connector is contaminated,
clean the fiber end face and properly connect the fiber.
Step 5 Manually start fiber quality detection. Ensure that Detection Mode is not set to
Offline Mode. After the detection result is displayed, click Set as Reference
Curve. Set Detection Mode to Reference Mode and start detection again. For
details, see 5.2 Manually Starting Fiber Quality Monitoring.
NOTE
● If no optical fiber is connected (that is, the value of Position is 0), the
FIBER_BREAK_POS alarm is still generated during detection in the reference mode and
cannot be cleared even after detection in the reference mode using the same reference
curve is performed.
● Choose Monitor > Alarm > Current Alarms from the Main Menu, select the
FIBER_BREAK_POS alarm, click , and select Synchronize. The FIBER_BREAK_POS
alarm is cleared.
Step 6 Check whether the alarm is cleared. If the alarm persists, contact Huawei
engineers.
----End
Related Information
None
8.4 FIBER_ABN_POS
Description
Fiber abnormality point location. This alarm is generated when the system detects
the location of a fiber abnormality point after the loss or reflection change of a
fiber connector or splicing point is excessively large.
Alarm Reporting
You can set alarm reporting parameters on the System Configuration page.
1. Choose Configuration > WDM Optical Management > Fiber Doctor from
the main menu.
2. Click Fiber Doctor, choose System Configuration from the drop-down menu,
and set alarm reporting parameters.
Attribute
Alarm Severity Alarm Type
Warning Equipment
Parameters
When you view an alarm on the network management system, select the alarm.
In the Alarm Details field display the related parameters of the alarm. The alarm
parameters are in the following format: Alarm Parameters (hex): parameter1
parameter2...parameterN. For details about each parameter, refer to the following
table.
Possible Causes
The fiber loss is abnormal, triggering the Fiber Doctor to start detection. After the
fiber abnormality point location is detected, this alarm is reported.
Procedure
Step 1 Based on the fiber abnormality point location detected by the Fiber Doctor, check
whether the fiber connection is normal on the NCE.
Step 2 Check whether fibers are aging, bent, or broken. If yes, coil the fibers again or
replace the faulty fibers.
Step 3 Check whether the fiber connectors are clean. If a fiber connector is contaminated,
clean the fiber end face and properly connect the fiber.
Step 4 Check whether the alarm is cleared. If the alarm persists, contact Huawei
engineers.
NOTE
You can select this alarm and click Clear on the Current Alarms page to manually clear the
alarm.
----End
Prerequisites
The user must be an NMS user with Maintainer Group rights or higher.
Context
In the location information of a fiber alarm reported by the FD, port names are
statically configured. When a user customizes a port name on the NMS, the port
name in the alarm location information is still the original port name. Users can
change the port name in the alarm location information to be the same as the
port name on the NMS.
NOTE
Customized port names can be displayed only for the FIBER_ABN_POS and
FIBER_BREAK_POS alarms.
Procedure
Step 1 On the Network Management app of NCE, choose Monitor > Alarm > Current
Alarms from the main menu and view Location Info of the alarms.
NOTE
1. You can also view the fiber alarm location information using the following methods:
– On the Network Management app, choose Monitor > Alarm > Alarm Logs from
the main menu and view Location Info of the alarms.
– On the Network Management app, choose Monitor > Alarm > Historical Alarms
from the main menu and view Location Info of the alarms.
– On the Network Management app, choose Monitor > Alarm > Masked Alarms
from the main menu and view Location Info of the alarms.
2. To view the Masked Alarms, you need to set masking rules on the Alarm Logs,
Historical Alarms, or Current Alarms page and click OK.
Step 2 In the physical topology view of the Network Management app, click Subnet
and double-click NE to enter the running status of the NE whose alarms need to
be modified.
Step 3 Click the icon on the Running Status page. On the NE Explorer page, right-
click the corresponding subrack and choose Path View from the shortcut menu.
Step 4 Right-click the subrack to be modified and choose Modify Port Name from the
shortcut menu.
Step 5 In the displayed Modify Port Name dialog box, modify the port name and click
Apply.
----End
10 Reference Operations
Prerequisites
You are an NMS user with "Maintainer Group" authority or higher.
Background Information
If operations such as the adding, deletion, or modification on subnets, sites, NEs,
boards, and fibers are performed during data synchronization, data
synchronization will fail.
NOTE
When backing up the subnet performance data, do not synchronize data from the NE side
to NCE. Otherwise, data synchronization will fail.
Procedure
Step 1 Choose Configuration > WDM Optical Management > Parameter
Configuration from the main menu on the NCE Network Management app.
Step 2 Click the Synchronize Data on the NMS tab.
Step 3 Choose the subnet to be synchronized from the Root navigation tree and click
Start. A confirmation dialog box is displayed.
NOTE
When synchronizing data for the first time after the NetStar O&M component is installed,
you must select Root to synchronize the network-wide data. In other scenarios, you can
select subnets as required to synchronize data.
If data share conflicts during data synchronization on the NCE NMS, maybe another user is
deleting, uploading, copying or checking data consistency on the NE. When this occurs,
perform data synchronization again after another user completes the operations on the NE.
During synchronization, do not perform other commissioning operations on the NE.
Step 5 Click OK in the dialog box that is displayed after the synchronization.
NOTE
After the synchronization is completed, the refresh icon turns green. Click to refresh
the Root navigation tree.
----End
11 FAQ
This section describes methods of handling common problems when using the FD
system.
11.1 Events Cannot Be Parsed After OTDR Detection
[Analysis]:
This problem occurs probably because:
● The insertion loss of the near-end fiber is too large.
● A fiber cut occurs at the near end.
[Solution]:
Check whether the insertion loss of the near-end optical fiber is excessively large
or the near-end optical fiber is broken. If yes, rectify the fault.