Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Roxy]

Well, sadly it's happened again. On Wednesday we had a call from tech support on the back of the engineer visit and he wanted me to do a line test, so I had to unplug everything and do a hard reset. I expressed concern because it was 6:30 in the evening, not a good time to resync. Never the less I did it and to my surprise it came back up even faster than it was before, if albeit only slightly. Everything seemed fine until Thursday around 13:00 when it all went down for a minute, then came back online. Since then speed has been capped around 40mbps.

I decided it was a fluke and would wait till the weekend around 11am in the morning, usually a good time for my sync. Sadly, the reconnect shows about the same speed and my ping is high again so looks like interleaving is on.

Argh.

[Dray]

Sounds like DLM has taken an interest in your connection and has capped your line speed to raise the SNRM to deal with disconnections and also applied interleaving due to errors.

[Roxy]

I found Bald Eagle talking about something similar with PPP sessions and near instant resyncs/connects not affecting the IP profile and BRAS.
http://community.plus.net/forum/index.php?topic=100862.msg861070

Seems like Plus forum mods a bit more clued up than BT .

[Dray]

You mean the BT Helpdesk in India? I agree.

Anyway, I saw in an earlier discussion that DLM was interested in disconnections and Error Seconds, especially when certain limits are exceeded. I think it's likely that your connection has exceeded the limits. 

[Roxy]

Think it's time I got the HG612 as well and tried to unlock it. I need to be able to monitor any errors locally, instead of waiting on random engineers to check. If this most recent disconnect/reconnect had put me back at the proper speeds, I could have left it as a fluke.

[Roxy]

I plugged my HH5 back in and the max rate is 48.2! Highest it's ever been, but my connection is stuck at 40.56

I also picked up this data from the 'system' log. Note the OpenRG entries :

21:33:32, 07 Sep.   (10825.510000) OpenRG is going for reboot by IPC command
21:33:27, 07 Sep.   (10820.510000) OpenRG will go down for reboot in 5 seconds
18:33:37, 07 Sep.   ( 30.350000) The system is UP!
01:00:28, 01 Jan.   ( 3628.450000) The system is going DOWN for reboot.
01:00:28, 01 Jan.   ( 3628.450000) OpenRG is going for reboot by IPC command
01:00:23, 01 Jan.   ( 3623.450000) OpenRG will go down for reboot in 5 seconds
00:00:29, 01 Jan.   ( 29.710000) The system is UP!
17:31:45, 07 Sep.   (259925.490000) The system is going DOWN for reboot.
17:31:45, 07 Sep.   (259925.490000) OpenRG is going for reboot by IPC command
17:31:40, 07 Sep.   (259920.490000) OpenRG will go down for reboot in 5 seconds

[burakkucat]

Yes, that snippet of your HH5 log file is similar to that which has been reported by others in the past. Unfortunately I do not have any links (to paw) that I can share with you. If you make a search of the TBB forum, using the string "HH5 rebooting", you should find a whole succession of posts dating back to earlier this year. Essentially that effect is why so many people have stopped using the device. 

[Roxy]

Thanks burakku. Sadly as mentioned previously, I got put back on interleaving even with the ECI modem and ASUS N56U.
I have a HG612 arriving this week, going to use the newest unlocked firmware image and HG612 stats 3.0. Hopefully that will shed some light on what's happening.

[Bald_Eagle1]

Be sure to allow Beta updates via the v 3.0 GUI to allow the latest HG612 Modem Stats v 4.x.x.x program updates to be automatically downloaded & set up to provide better efficiency & more detailed stats graphs.

[Roxy]

Be sure to allow Beta updates via the v 3.0 GUI to allow the latest HG612 Modem Stats v 4.x.x.x program updates to be automatically downloaded & set up to provide better efficiency & more detailed stats graphs.

OK


See attached zips for what I have so far from the baked HG612 GUI after unlock 'WEB GUI' flash. I assume all the auto settings are correct hough note circles and "??"
I have the modem to router via LAN 1 and also modem to router via LAN 2.

I've setup the HG612 logging tool and here is snapshot below(don't forget to scroll over):

That's enough for me tonight, thank you for reading. I have another engineer due on the 8th November and hope to put something useful together for them this time.

[Roxy]

Stats from today just after twenty four hours of uptime.
Yikes FEC!



Am I going out on a limb here by saying that isn't good?

[burakkucat]

Stats from today just after twenty four hours of uptime.
Yikes FEC!

<snip>

Am I going out on a limb here by saying that isn't good?

FEC == Forward Error Correction. 1969 FECs are far preferable than 1969 CRCs! 

Regard any number of FECs as proof that the equipment is operating correctly. If they were not FECs then they would appear as CRCs.

[Black Sheep]

Not ever having seen the stats harvesting screens before, could Roxy be on about the 35 million FEC's shown on the right-hand side of the screen capture ??

I wouldn't know if the left side shows a snap of a real-time test, and the right side shows the stats over the total uptime (1 day 12 mins etc) All new to me. 

[Roxy]

Not ever having seen the stats harvesting screens before, could Roxy be on about the 35 million FEC's shown on the right-hand side of the screen capture ??

I wouldn't know if the left side shows a snap of a real-time test, and the right side shows the stats over the total uptime (1 day 12 mins etc) All new to me. 

That's how I thought it worked, in that the left is more real time and the right side is accumulative. I don't often see CRC on the current sessions, but I do see them growing on the right side.
Currently I'm on 1055 CRC, about 10000 HEC and 92 million FEC.

[Black Sheep]

If that is the case as we assume it to be, then if the accumulative FEC's for just over one day being at almost 36 million, would be a concern for me.

I must again point out, I am not a 'stats-man' at all, so my musings are, just that.