Spark fibre, UFF ONT crashing

Forums › Spark New Zealand (including Skinny and BigPipe) › Spark fibre, UFF ONT crashing

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#248399 24-Mar-2019 19:42

I can reliably crash the ONT modem, by using VPN and RDP to connect into my home network.

Pretty sure it is the ONT, because rebooting the fritz does not fix the internet dropout. Only rebooting the ONT repairs the internet connection.

I could vpn into my fritz 7490 now (through 4g), start rdp, and the ONT will crash. That shouldn't be possible right?

Talkiet

4819 posts

Uber Geek
+1 received by user: 3934

Trusted

#2204399 24-Mar-2019 19:56

No, it shouldn't be. Does it happen with the standard 659b as well?

Cheers - N

Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#2204403 24-Mar-2019 20:02

Talkiet:

No, it shouldn't be. Does it happen with the standard 659b as well?

Cheers - N

I have only just returned home, I'll do some more testing.... this used to work just fine though.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#2204409 24-Mar-2019 20:22

can you dm me your details? i'd love to see what uff are recording for those drops.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

muppet

2642 posts

Uber Geek
+1 received by user: 1660

Trusted

#2204410 24-Mar-2019 20:27

If it turns out you are really crashing the ONT (I'm not so sure you are, but hey) then you must send me a Wireshark of the packets going to the ONT for, errr, scientific research purposes. Yeah. Science.

sparkz25

750 posts

Ultimate Geek
+1 received by user: 284
Inactive user

#2204412 24-Mar-2019 20:38

muppet:

If it turns out you are really crashing the ONT (I'm not so sure you are, but hey) then you must send me a Wireshark of the packets going to the ONT for, errr, scientific research purposes. Yeah. Science.

I too would be interested to know what is causing the ONT to crash.

Have you logged on to the ONT to see what the stats are and to see if it is the ONT that is crashing?

i wonder if the ONT will store some logs?

quickymart

14940 posts

Uber Geek
+1 received by user: 13952

ID Verified

#2204493 24-Mar-2019 21:42

I don't think you can login to/access the stats of an ONT, can you? I don't think you can with Chorus ones, anyway.

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

sparkz25

750 posts

Ultimate Geek
+1 received by user: 284
Inactive user

#2204518 25-Mar-2019 06:36

quickymart:

I don't think you can login to/access the stats of an ONT, can you? I don't think you can with Chorus ones, anyway.

the Huawei HG8240H you can the default ip is 192.168.100.1, user is telecomadmin, pass is admintelecom

looks like there is a log file of some sort under System Tools>User Log

Manufacturer:Huawei Technologies Co., Ltd;
ProductClass:HG8240H;
SerialNumber:485;
IP:192.168.100.1;
HWVer:474.B;
SWVer:V3R0;

1970-01-01 00:00:13 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on
1970-01-01 00:00:15 [Notice][Config-Log] Terminal:CLI(-),Type:Login,Username:
1970-01-01 00:00:13 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on
1970-01-01 00:00:15 [Notice][Config-Log] Terminal:CLI(-),Type:Login,Username:
1970-01-01 00:00:13 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on, Terminal:OTHER
1970-01-01 00:00:10 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on, Terminal:OTHER
1970-01-01 00:00:10 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on, Terminal:OTHER
1970-01-01 00:00:12 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on, Terminal:OTHER
1970-01-01 00:02:00 [Notice][Alarm-Log] AlarmID:104517,AlarmLevel:Error,[WEB] from ip:192.168.100.2 login fail!
1970-01-01 00:02:08 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Login,Username:telecomadmin
1970-01-01 00:08:07 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Logout,Username:telecomadmin
1970-01-01 00:12:37 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Login,Username:telecomadmin
1970-01-01 00:13:14 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Set,VoiceService:1,X_HW_Reset:1
1970-01-01 00:00:10 [Notice][Alarm-Log] AlarmID:104001,AlarmLevel:Error,Device reset. Cause: ONU reset after being powered on, Terminal:OTHER
1970-01-01 00:00:52 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Login,Username:telecomadmin
1970-01-01 00:02:37 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Set,Deviceinfo:,X_HW_LedSwitch:1
1970-01-01 00:04:19 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Set,APMPolicy:,EnablePowerSavingMode:0
1970-01-01 00:04:32 [Notice][Config-Log] Terminal:WEB(192.168.100.2),Result:Success,Type:Logout,Username:telecomadmin

surfisup1000

5288 posts

Uber Geek
+1 received by user: 2159

#2204636 25-Mar-2019 12:02

Now I am home and had time to test further , I think it is the fritzbox crashing, not the ONT.

After triggering the crash ( vpn / rdp), the fritzbox loses the internet connection and becomes 'almost' non responsive in the web management interface.

Restarting the fritzbox in this 'error' state takes far longer than a normal reboot, maybe 3 times as long.

So when my daughter rebooted the fritz and it didn't come up after the usual time, I asked her to reboot the ONT.... by which time the fritz had finished rebooting and everything came back online.

So it appeared that rebooting the ONT fixed it, but it was fritz reboot that actually fixed the issue.

It is not the easiest trying to fix such issues remotely, especially with my daughter who knows nothing about networking equipment and is too short to reach plugs etc.

Anyway, at least I know what to look at now.