I have issues with my Router

[Mikkel Dahr]

Hey guys. Can you just look at this log file, and see if it is ok? I would appreciate it alot.
I am experiencing sudden dropps of ping. And sometimes it completely stops working, and I solve it by powering it of.
For several years it worked perfect, and it works perfect in between these events.

Manufacturer:Huawei Technologies Co., Ltd;
ProductClass:HG8245T;
SerialNumber:48575443599C2427;
IP:10.194.46.211;
HWVer:211DC601;
SWVer:V2R006C00S207;

1970-01-01 00:00:19 [Notice] Login
1970-01-01 00:00:21 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 273.
1970-01-01 00:00:22 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 6.
1970-01-01 00:00:22 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 661.
1970-01-01 00:00:29 [Critical] Reset reason: monitor process!
2014-06-26 15:07:27 [Notice] Start to load a packet file by OMCI
2014-06-26 15:10:56 [Notice] Finish to load a packet file!!
2014-06-26 15:10:56 [Notice] Load Success!
1970-01-01 00:00:20 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 273.
1970-01-01 00:00:20 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 274.
1970-01-01 00:00:21 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 6.
1970-01-01 00:00:21 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 661.
1970-01-01 00:00:24 [Notice] Login
2014-06-26 15:12:01 [Critical] [PSI]Start to download config file from bms!
2014-06-26 15:12:01 [Notice] The Result Of Check Xml :0
2014-06-26 15:12:04 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.DeviceInfo
2014-06-26 15:12:04 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.QueueManagement
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.ManagementServer
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.X_HW_ALG
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.X_HW_AmpInfo
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.X_HW_APMPolicy
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.X_HW_Security
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.Services.X_HW_AccessLimit
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.UserInterface.X_HW_CLITelnetAccess
2014-06-26 15:12:05 [Notice] [PSI]Return(0) to Set instance path: InternetGatewayDevice.X_HW_Security.Dosfilter
2014-06-26 14:12:35 [Critical] [PSI]Success to process config file from bms!
2014-06-26 14:13:16 [Critical] [CWMP]Success to set parameter value, path:InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.SSID
2014-06-26 14:13:18 [Critical] [CWMP]Success to set parameter value, path:InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.TransmitPower
1970-01-01 00:00:34 [Critical] Reset reason: normal!, Reset time: 1969-06-02 13:19:27
2016-01-21 02:11:13 [Critical] [PSI]Start to download config file from olt!
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:35 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
2016-04-04 04:19:55 [Critical] [PSI]Start to download config file from olt!
2016-04-06 04:39:38 [Critical] [PSI]Start to download config file from olt!
2016-06-07 08:44:34 [Critical] [PSI]Start to download config file from olt!
2016-08-18 02:47:37 [Critical] [PSI]Start to download config file from olt!
1970-01-01 00:00:38 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
2016-10-01 08:07:20 [Critical] [PSI]Start to download config file from olt!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:36 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:36 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:36 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:35 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:35 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:36 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:36 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:36 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:37 [Critical] Reset reason: unknown reason!, Reset time: 1970-01-01 00:00:37 Terminal: ERR-TERMINAL
1970-01-01 00:00:37 [Critical] Reset reason: power off!
1970-01-01 00:00:36 [Critical] Reset reason: power off!
1970-01-01 00:00:24 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 278.
1970-01-01 00:00:26 [Warning] [VOIP] Get Attribute From DataBase Check Parameter Failed! The Reason is 0x1. The CMO is 671.
1970-01-01 00:00:34 [Critical] Reset reason: normal!, Reset time: 2017-04-17 13:36:07 Terminal: ERR-TERMINAL
2017-04-17 14:37:13 [Notice] Terminal:OLT(-),Result:Success,Type:Set,DialSN:,IsHaveAuthed:1
2017-04-17 14:37:16 [Critical] [PSI]Start to download config file from olt!
2017-04-17 14:37:16 [Notice] AlarmID:303501,AlarmLevel:Error,OLT started to issue XML configurations
2017-04-17 14:37:16 [Notice] The Result Of Check Xml :0
2017-04-17 13:37:58 [Critical] [CWMP]Success to set parameter value, path:InternetGatewayDevice.LANDevice.1.WLANConfiguration.1.PreSharedKey.1
2017-04-17 13:37:59 [Critical] [CWMP]Success to set parameter value, path:InternetGatewayDevice.LANDevice.1.WLANConfiguration.1

 

[Ralston18]

I would suspect that the router is failing - some power supply related component(s).

Just be sure that the power connections are all snug and tight - nothing loose to where there can be even minor disconnects.

Does the router feel hot at all? Good airflow all around?

Note that the date/time stamps (other than the last six or so lines) are way off and almost appear to be some default values: 1970, 00:00:xx (?).

A firmware upgrade, if available, may help if the problem is not physical.

However, being several years old, the router may be reaching its designed EOL (End of Life).

 

[nigelivey]

Given that it is picking up the correct time and date when trying to sync (17.04.2017) but failing to load the config file from olt (optical line terminal) either your router is duff or there is a problem with your ISP. I would call support.

 

[Mikkel Dahr]

Given that it is picking up the correct time and date when trying to sync (17.04.2017) but failing to load the config file from olt (optical line terminal) either your router is duff or there is a problem with your ISP. I would call support.

Thanks alot for answering me! Seems that you are probably right.
I had one pc connected through cable, and two through wifi. Several times the wifi users had major issues, while the cabeled pc had perfect internet connection. That would suggest that it is not the ISP, but the router that´s having issues right?

 

[Mikkel Dahr]

I would suspect that the router is failing - some power supply related component(s).

Just be sure that the power connections are all snug and tight - nothing loose to where there can be even minor disconnects.

Does the router feel hot at all? Good airflow all around?

Note that the date/time stamps (other than the last six or so lines) are way off and almost appear to be some default values: 1970, 00:00:xx (?).

A firmware upgrade, if available, may help if the problem is not physical.

However, being several years old, the router may be reaching its designed EOL (End of Life).

Thanks to you too for taking the time. No it does not feel especially hot or anything. I could not find a upgrade.
Again, thanks for your views!

 

[Ralston18]

You are welcome.

Heat is a good sign of a problem - especially when the heat is obviously present.

Some small component may be failing but with little or no heat up if the overall cooling and airflow are sufficient to diffuse any sense of it. Happening but one cannot feel the heat nor smell the results. Larger devices that accumulate internal dust and debris will emit an odor if some component gets overly hot. Or sometimes just if something (e.g., a dust bunnie, paper shred, a bug) gets inside and makes contact with a hot component.

I have had a couple of USB wireless adapters get quite hot to the touch when a failure occurs.