Print

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

[paul0000]

Hi all

Newly registered at the site and have been doing lots of reading!  I'm hoping for some help...

We've been experiencing what I would describe as short periods of unresponsive internet (e.g. web pages take an age to load, and then maybe timeout.  hit refresh and they may then load).  I suspected an issue with our router Asus AC3200  but I've reset to factory, loaded merlins firmware and it seems stable.

Searching led to me this site, as I'm wondering if the problem is with my line / the Huawei HG612 modem.

I ran through the helpful steps to unlock my modem.  Today I noticed something, I had a web browser open on status>WAN>xDSL and it looked like the modem was re-syncing the connection.

I've also turned on logging a little earlier and see this in the logs:

Manufacturer:Huawei Technologies Co., Ltd.
Style:EchoLife HG612
SN.:21530315408K1A063782
IP:192.168.1.3
HW Ver:VER.B
SW Ver:V100R001C01B030SP08

2000-1-1 1:58:28 Notice 0 admin login
2000-1-1 1:56:40 Notice 0 admin login
2000-1-1 1:40:5 Notice 104500 DSL activate succeed
2000-1-1 1:39:42 Notice 104500 DSL deactivate
2000-1-1 0:46:51 Notice 0 admin login
2000-1-1 0:46:26 Error 104143 User has failed to login 1 time
2000-1-1 0:42:35 Notice 104500 DSL activate succeed
2000-1-1 0:42:12 Notice 104500 DSL deactivate
2000-1-1 0:1:40 Notice 0 admin login
2000-1-1 0:0:27 Notice 104500 DSL activate succeed
2000-1-1 0:0:17 Debug 104500 LAN1 up
2000-1-1 0:0:15 Debug 104500 LAN2 up
2000-1-1 0:0:14 Notice 1 System up
2000-1-1 0:0:3 Warning 10400 KLOB Pool 1 Initialized: 1048576 bytes <0x80300000 ... 0x80400000>
2000-1-10 8:19:43 Notice 104500 DSL activate succeed
2000-1-10 8:19:20 Notice 104500 DSL deactivate
2000-1-10 8:16:27 Notice 0 admin login
2000-1-10 6:57:42 Notice 104500 DSL activate succeed
2000-1-10 6:57:20 Notice 104500 DSL deactivate

These are the stats from the modem.

xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status:   0
Max:    Upstream rate = 9238 Kbps, Downstream rate = 40440 Kbps
Bearer: 0, Upstream rate = 9238 Kbps, Downstream rate = 35000 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        7.8             6.4
Attn(dB):        21.8            0.0
Pwr(dBm):        11.3            7.2
                        VDSL2 framing
                        Bearer 0
MSGc:           -6              54
B:              73              237
M:              1               1
T:              0               33
R:              6               16
S:              0.0666          0.8180
L:              9610            2484
D:              8               1
I:              80              127
N:              80              254
Q:              8               0
V:              5               0
RxQueue:                132             0
TxQueue:                33              0
G.INP Framing:          18              0
G.INP lookback:         31              0
RRC bits:               0               24
                        Bearer 1
MSGc:           90              -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              10.6667         0.0000
L:              24              0
D:              1               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0
                        Counters
                        Bearer 0
OHF:            0               215701
OHFErr:         0               1
RS:             174161624               1347612
RSCorr:         557             3
RSUnCorr:       0               0
                        Bearer 1
OHF:            181291          0
OHFErr:         0               0
RS:             1087378         0
RSCorr:         4               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         86206105                0
rtx_c:          41044           0
rtx_uc:         148641          0

                        G.INP Counters
LEFTRS:         49              0
minEFTR:        34999           0
errFreeBits:    9179477         0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    195980487               0
Data Cells:     4969319         0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             48              4
SES:            42              0
UAS:            111             69
AS:             2912

                        Bearer 0
INP:            52.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            13.55
OR:             0.01            35.42
AgR:            35418.64        9273.88

                        Bearer 1
INP:            2.50            0.00
INPRein:        2.50            0.00
delay:          0               0
PER:            16.06           0.01
OR:             47.81           0.01
AgR:            47.81   0.01

Bitswap:        2361/2361               13/13

Total time = 2 hours 28 min 33 sec
FEC:            132381          9
CRC:            1349            4
ES:             48              4
SES:            42              0
UAS:            111             69
LOS:            2               0
LOF:            14              0
LOM:            0               0
Latest 15 minutes time = 13 min 33 sec
FEC:            135             2
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            205             1
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 2 hours 28 min 33 sec
FEC:            132381          9
CRC:            1349            4
ES:             48              4
SES:            42              0
UAS:            111             69
LOS:            2               0
LOF:            14              0
LOM:            0               0
Previous 1 day time = 0 sec
FEC:            0               0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 48 min 31 sec
FEC:            557             3
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

If anyone can provide some guidance it'd be much appreciated.

Thanks!

[burakkucat]

Welcome to the Kitz forum. 

The internal log of an HG612 is not one of the easiest to read but the way I do it is to scan down from the top until I find a line that includes --

Warning 10400 KLOB Pool 1 Initialized:

Take that line as the starting point and then read upwards. So we then see the following sequence --

2000-1-1 0:0:27 Notice 104500 DSL activate succeed
2000-1-1 0:42:12 Notice 104500 DSL deactivate
2000-1-1 0:42:35 Notice 104500 DSL activate succeed
2000-1-1 1:39:42 Notice 104500 DSL deactivate
2000-1-1 1:40:5 Notice 104500 DSL activate succeed

That sequence ties in with your observations of "short periods of unresponsive internet".

At this point, we have no evidence as to the cause . . . it could be that the cabinet based DSLAM is responsible; it could be that the HG612 is responsible; it could be that the metallic pathway is responsible.

In your reading, I expect that you have come across mentions of DSLstats and MyDSLWebStats (normally abbreviated as MDWS). If you were to make use of both utilities, we could then see the circuit's statistics and examine its performance.

[banger]

As B*cat says the problem could be DSLAM, modem or line. How old is the HG612 as they have a bit of a reputation of rebooting when old although looking at your log that does not appear to be the problem as the line is deactivating several times in the log? Have you got another modem, preferably younger?

[paul0000]

Hi guys,

Thanks for responding!

The HG612 is the original modem that BT installed when I took out Infinity, at a guess I'd say it must be at least 6 or 7 years old ... I pretty much took infinity as soon as it was available at my local exchange.

I have dslstats running on my laptop and also setup on the website (same username).

If it's relevant until recently my line was syncing at approx 40mb download and 10mb upload (was also getting these figures from speedtest.net) -- both seemed to have dropped quite a lot.

What should I be looking for?

[j0hn]

The lines still capable of 40Mb, but DLM has banded/capped the line at 35Mb.
This is usually caused by the DSL retraining too many times in a short period.

2000-1-1 0:42:35 Notice 104500 DSL activate succeed
2000-1-1 0:42:12 Notice 104500 DSL deactivate

Which looks like what this is.

If it continues to resync/retrain too many times I would expect the 35Mb banding to be lowered further.

[paul0000]

Thanks j0hn

From what I can see with DSLstats my line has been stable (at the lower speed) since about 4am UK this morning.  Not sure what happened just before then!

[burakkucat]

I now have your circuit as my "viewing target" by MDWS and, from the small amount of data that has currently been uploaded, the DS & US SNRM values confirm j0hn's observation about the circuit being banded. I also note that one SES had been flagged up during the time I was looking . . .

Once there has been about 24 hours of data, more of the circuit's characteristics should become apparent. In particular, I would be interested to see the Hlog and QLN plots.

[paul0000]

Thanks, what is SES?

Added screenshots of QLN and Hlog graphs.

[burakkucat]

Thanks, what is SES?

Looking at the alphabetical list of line parameters and counters on the main site --

SES - Severely Errored Seconds

    As the name indicates this is more worse than an Errored Second (which only needs one event to trigger an ES).
    A Severely Errored Second is a one second period which contains 30% or more errored blocks OR several other events such as one or more OOF.

[paul0000]

I also called BT a little earlier re the issues.  They did the usual, but interestingly, whilst they found no fault with the line did say they saw some "drops" on the line.

Have arranged an engineer to visit on Dec 27th to investigate further.  We'll see what happens next!

[paul0000]

BT engineer came today and made some changes.

1) he added one of the latest wall boxes in the house

2) found a "loose" connection in the local cabinet - it had one of the new push connections not spliced, and when he pulled the cables, one came completely away

My line was reset and it's currently syncing a little higher and my download sync is also higher.  He said he suspected the cause of the high SNR on the D/L was due to the loose cable.

He also mentioned that with his modem tester he was getting approx 41MB sync from the new wall box but approx 37 at the end of my RJ11 when he unplugged from the 612.  Recommended I change the cable.

I had a quick look on DSLstats and I can still see some SES since he left this morning, G.INP is now also removed from my line.

Welcome any comments on the above and what I should keep an eye on in the coming days.

[burakkucat]

Working backwards --

• With a DLM reset (a "circuit recalc" in Openreach speak) G.998.4 (G.Inp) will be removed and, all being well, will be reinstated in the coming days/weeks. (N*Star has the ability to estimate how long will elapse before it is re-applied.)
• An odd SES should not be a cause for concern. However if you experience more than an odd one then that is something that will require further investigation. (By you/us, not Openreach.)
  
• Do as the technician recommended and replace that patch lead which connects the modem to the NT5E/SSFP. Use the shortest lead possible.
• I am aware that -- just occasionally -- there might be an odd problem with a "push fit" joint made in the PCP. They are still being made with IDCs, when the mechanics of the joint is examined, just not via gel-crimps.

Overall it reads as if you have had a successful visit. 

Edited to add: Once there is 24+ hours worth of data to view via MDWS we should then be able to see just how well the circuit is now behaving.

[paul0000]

Thanks burakkucat,

Appreciate the feedback.

interesting comment on the patch lead, exactly the same as the engineer, as i have a longer than necessary cable     He said short as possible is the way to go.  i may relocate the 612 next to the wall box.

Ref the SES, DSLsats shows 33 in the last 12hours (since the engineer finished up) - I'm sill learning but this could be read as under 3 per hour, and acceptable?

[burakkucat]

Ref the SES, DSLsats shows 33 in the last 12hours (since the engineer finished up) - I'm sill learning but this could be read as under 3 per hour, and acceptable?

Hmm . . . I would like the circuit to have at least 24 hours to "settle" before taking a close look at the various statistics. Just to be sure, are you definitely looking at the SES counter and not the ES counter?   

Just one other point, hopefully you are not looking at the HG612's GUI as it tells lies! The data harvested & displayed by DSLstats is obtained via the CLI and is correct. 

I am going to be out for most of the day, tomorrow, so perhaps one or more other members will take a look and then comment.

[paul0000]

Yes, been looking at DSLstats for the data and SES detail, although it seems to have improved so far today.