Hello, everyone!
Today, I will explain ONU configuration failure and how we can fix it. There are two potential problems: OLT and ONU.
The ONU configuration status indicates whether restoration is enabled and whether it is complete. ONU configuration statuses are as follows:
initial,
config,
normal,
failed.
When the ONU connects to the network, it enters the initial phase briefly and then goes into the config state. And that phase ends quickly. In this phase, the ONU restores its capability data and configuration data. If this phase is completed successfully, the ONU goes into its normal state. On the opposite, the ONU configuration state is failed.
The problem with OLT is the problem in configuration. The real capabilities of the ONU do not match the configuration on the OLT. When we have this problem, the system shows us alarm 0x2e21a102. The configuration on the OLT needs to be corrected to solve the problem. This is generally rare. And usually at the beginning of activating the GPON system or when we introduce new types of ONT.
The second problem is ONU. Two problems are possible on it. The first is hardware. And that can only be solved by replacing the device. Another problem is that the ONU is configured locally (or has some old configuration) and does not accept the configuration sent by the OLT. Then you should try to solve the problem with a reset. Alternatively, we can delete the configuration via a web browser.
Next command show us normal config state:
TEST(config-if-gpon-0/13)#display ont info 11 2
{ <cr>||<K> }:
Command:
display ont info 11 2
-----------------------------------------------------------------------------
F/S/P : 0/13/11
ONT-ID : 2
Control flag : active
Run state : online
Config state : normal
Match state : match
DBA type : SR
ONT distance(m) : 984
ONT battery state : holding state
Memory occupation : 74%
CPU occupation : 1%
Temperature : 50(C)
Authentic type : SN-auth
SN : XXXXXXXX (HWTC-XXXXX)
Management mode : OMCI
Software work mode : normal
Isolation state : normal
ONT IP 0 address/mask : X.X.X.X/X
Description : XXXXXXXac7f736b0b4d28a20xx
Last down cause : dying-gasp
Last up time : 2001-12-17 17:27+01:00
Last down time : 2001-12-17 17:27+01:00
Last dying gasp time : 2001-12-17 17:27+01:00
ONT online duration : 27 day(s), 21 hour(s), 16 minute(s), 42 second(s)
Type C support : Not support
Interoperability-mode : ITU-T
-----------------------------------------------------------------------------
VoIP configure method : Default
-----------------------------------------------------------------------------
Line profile ID : 11
Line profile name : 0020m
-----------------------------------------------------------------------------
...
Thank you!
Reference:
HCIP-Access V2.5 Training Material
