Issue Description
When the customer tries to create Huawei ONT trough TL1 in BMS R11, there is SQL error:
ADD-ONT::DEV=PRT45-1_OLT-HW_1,FN=0,SN=1,PN=0,ONTID=1:44422::NAME=devil,ALIAS=djdj,CAPABPROF=ONT_PROFILE_HW_HG850,SERIALNUM=2011-2E0A4C41, AUTH=SN,ALMPROF=alarm-profile_1;
0 2008-04-11 14:12:00
M SN COMPLD
EN=1610614891 ENDESC=Failed to execute SQL
Eventhough, the ONT is created:
OLTHW-TestPLant1(config-if-gpon-0/1)#display ont info 0 1
----------------------------------------------------------------------------
F/S/P : 0/1/0
ONT-ID : 1
Control flag : active
Run state : up
Config state : normal
Match state : match
DBA type : SR
Loop mode : disable
ONT RTD(us) : -
Transparent : disable
Ont Profile ID : 6
Authentic type : SN-auth
SN : 323031312E0A4C41(2011-2E0A4C41)
Description : ONT_NO_DESCRIPTION
Alarm profile-ID: 1
----------------------------------------------------------------------------
----------------------------------------------
T-CONT-ID DBA-profile Alloc-ID
----------------------------------------------
0 1 1
- ----------------------------------------------
This problems seems to happen in the case we had previously an ONT with the same ONT_ID in the same port.
If we create the Huawei ONT with a ONT_ID that was never used, the problem does not happen.
It seems that when we delete the ONT in the BMS, some information is not deleted in one of the tables.
ADD-ONT::DEV=PRT45-1_OLT-HW_1,FN=0,SN=1,PN=0,ONTID=1:44422::NAME=devil,ALIAS=djdj,CAPABPROF=ONT_PROFILE_HW_HG850,SERIALNUM=2011-2E0A4C41, AUTH=SN,ALMPROF=alarm-profile_1;
0 2008-04-11 14:12:00
M SN COMPLD
EN=1610614891 ENDESC=Failed to execute SQL
Eventhough, the ONT is created:
OLTHW-TestPLant1(config-if-gpon-0/1)#display ont info 0 1
----------------------------------------------------------------------------
F/S/P : 0/1/0
ONT-ID : 1
Control flag : active
Run state : up
Config state : normal
Match state : match
DBA type : SR
Loop mode : disable
ONT RTD(us) : -
Transparent : disable
Ont Profile ID : 6
Authentic type : SN-auth
SN : 323031312E0A4C41(2011-2E0A4C41)
Description : ONT_NO_DESCRIPTION
Alarm profile-ID: 1
----------------------------------------------------------------------------
----------------------------------------------
T-CONT-ID DBA-profile Alloc-ID
----------------------------------------------
0 1 1
- ----------------------------------------------
This problems seems to happen in the case we had previously an ONT with the same ONT_ID in the same port.
If we create the Huawei ONT with a ONT_ID that was never used, the problem does not happen.
It seems that when we delete the ONT in the BMS, some information is not deleted in one of the tables.
Alarm Information
Null
Handling Process
CLI deleting leads to in-consistence between the device and BMS, syn can solve the problem.
Root Cause
Null
Suggestions
Null
More related:
No comments:
Post a Comment