Huawei SmartAX MA5612 Maintenance Manual page 237

SmartAX MA5612 Multi-service Access Module
Maintenance Guide
Possible Cause
The optical splitter is
faulty or the connectors
on the optical splitter are
not clean.
The ODN is not properly
planned.
NOTE
Step 4 Check for the possible causes on the ONU and troubleshoot the faults accordingly. If the ONU
still fails to function properly after that, proceed to
Issue 01 (2012-07-25)
l The split ratio of the
ODN link is not
determined by the
number of ONTs
connected but by the
split ratio of optical
splitters. When an
optical splitter is
connected to the ODN,
attenuation occurs and
the split ratio of the
optical splitter needs to
be calculated.
l Protocols specify that
the receive optical
power of the OLT
should not exceed 15
dB. In addition, the
difference between the
maximum optical
power and the
minimum optical
power should not
exceed 15 dB.
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
Judgment Criterion
Measure the input and output
optical power of the optical
splitter by using the optical
power meter. It is found that the
actual attenuation exceeds the
theoretical attenuation.
NOTE
The faults in the optical splitter
cannot be located by the OTDR
because the OTDR cannot
penetrate the optical splitter.
The ODN does not meet the
requirements of the ODN link
plan or GPON Class B+.
l Three-level splitting exists
in the ODN.
l The network coverage of
the ODN exceeds 20 km by
far.
l The split ratio exceeds the
maximum split ratio that the
board allows. Assuming
that the maximum split ratio
of a board is 1:64. If the
first-level split ratio is 1:8
and the second-level split
ratio is 1:16, the actual split
ratio is 1:128, which
exceeds the maximum split
ratio of the board.
l The optical attenuation
difference of two optical
paths exceeds 15 dB.
Step
6 System Fault Handling
Troubleshooting Method
Replace the faulty optical
splitter or clean the connectors
on the optical splitter.
Optimize the ODN to meet
Huawei's ODN planning
requirements and protocol
requirements.
5.
228