Batch ONT can not be auto found in OLT 

Issue Description

Customer is deploying ONT to OLT, they found all ONT can not be auto found in any gpon port of OLT, no matter how to change ONT to which port.

Alarm Information

NO signals(LOS)

Handling Process

1: Check if all GPON ports are enable
laser on.

2: Check if all GPON ports are enable
auto find function.

3: Measure the receiving optical power
in ONT side, there are signal indeed. But ONT is still not be online

4: Check sending optical power of GPON
port is in normal range, and status, Max rate(not 2500000Kbps), undefined
vendor, model of optical module, if plugin wrong module.(e.g. plug in
PX20+)

MINE-OLT-3(config-if-gpon-0/0)#display  port
state 0
 ----------------------------------------------------------------------------
Port Information
----------------------------------------------------------------------------
F/S/P                       
0/0/0
Port
state                  
Online
Last down
cause             
-
 Last up
time                
2017-10-04 09:59:10+08:00
 Last down
time              
-
Port energy-saving flag      No
xPON MAC chipset state       Normal
Signal
detect               
Normal
Available bandwidth(Kbps)    1061492
 Illegal rogue
ONT           
Inexistent
----------------------------------------------------------------------------
Optical Module State
----------------------------------------------------------------------------
Optical Module status        Online
Laser
state                 
Normal
TX
fault                    
Normal
Temperature(C)              
30
TX Bias
current(mA)          24
Supply
Voltage(V)           
3.22
TX
power(dBm)               
3.79
----------------------------------------------------------------------------
Vendor
name                 
HISILICON       
Vendor
rev                  
Unspecified
Vendor
OUI                  
Unspecified
Vendor
PN                   
SSX1T1LTB       
Vendor
SN                   
030SRN6TG1753404
Date
Code                   
16-01-26
Vendor
specific             
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
----------------------------------------------------------------------------
 Optical Module Static Information
----------------------------------------------------------------------------
 Module
type                 
GPON
Module
ub-type             
CLASS B+
Used
type                   
OLT
Encapsulation
Type           SFP
SFF-8472
Compliance          Includes
functionality
described in Rev 9.5
Max
Distance(Km)            
20
 Max
rate(Kbps)              
2500000
 Rate
Identifier             
Unspecified(0x0)
  Wave
length(nm)             
1490
Fiber
type                  
Single Mode
Identifier                  
SFP or SFP interface ID only
Connector                   
SC
Encoding                    
NRZ
Length(9um)(km)             
20.0
Length(50um)(m)             
-
Length(62.5um)(m)           
-
Length(copper)(m)           
-
Length(50um,OM3)(m)          -
BR,max                      
Unspecified
BR,min                      
Unspecified
Diagnostic Monitoring Type   Digital diagnostic monitoring
 Externally Calibrated
                              
Power measurement type: Average Power
\
 
threshold(dBm)              
[-29.2,-8.0]
Rx power alarm
threshold(dBm)              
[-30.0,-7.0]
Tx power warning
threshold(dBm)              
[1.0,5.0]
tx power alarm
threshold(dBm)              
[0.6,5.6]

5: Check the statistics of GMAC in diagnoise,
Display statistics gmac
Display statistics gmac
Explanation to
key words:
Received SN: SN request from ONT to OLT
Ploam sent upstream overhead count: Request from OLT to ONT which need ONT sent OLT
Display more than two times to compare if all amounts are increased, to prove ONT connect to right gpon port or not.

Root Cause

1: Shut down GPON port on OLT1
2: Display ont autofind in OLT2
3: All ONT connected are reporting register information to OLT2

Solution

Configure Type B in both OLT1 and OLT2 to make sure the protective mechanism of main fiber when one fiber are broken.
OLT1:

huawei_A(config)#dual-parenting local-node ip-address 192.168.68.1 port 6076 key work_4234
huawei_A(config)#dual-parenting peer-node standby ip-address 192.168.68.8 port 6076 key protect_4234
huawei_A(config)#dual-parenting sync enable
huawei_A(config)#protect-group 1 protect-target gpon-uni-port workmode dual-parenting
huawei_A(protect-group-1)#protect-group member port 0/2/1 role work
huawei_A(protect-group-1)#peer-group-member peer-node standby peer-port 0/2/1
huawei_A(protect-group-1)#uplink-monitor port 0/19/1
huawei_A(protect-group-1)#quit

OLT2:

huawei_B(config)#dual-parenting local-node ip-address 192.168.68.8 port 6076 key protect_4234
huawei_B(config)#dual-parenting peer-node active ip-address 192.168.68.1 port 6076 key work_4234
huawei_B(config)#dual-parenting sync enable
huawei_B(config)#protect-group 1 protect-target gpon-uni-port workmode dual-parenting
huawei_B(protect-group-1)#protect-group member port 0/2/1 role protect
huawei_B(protect-group-1)#peer-group-member peer-node active peer-port 0/2/1
huawei_B(protect-group-1)#protect-group enable
huawei_B(protect-group-1)#uplink-monitor port 0/19/1
huawei_B(protect-group-1)#quit

Suggestions

Before project delivering, we need to know the whole topology first to avoid spending much time to check configuration, going to different site to plug in and out ONT. Maybe after reading topology and LLD, we can make our work efficient.