Print

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

[mbb]

Hi all. I recently moved house, had infinity 2 installed and got a new hh5b. After day 10 of install the hub rebooted and interleaving was applied

The hub then ran for 40 days without rebooting and i posted the line stats over at bt forum and they said they were fine. another 10 days went by and i decided to hack my old hg6123b to get some stats. the modem had been running for approx 35 days without a resync then i woke up to a nice sexy fastpath connection. it only lasted 4 days and now im back on interleaving again.

would it be worth posting stats to try to diagnose possible issues on my line or is it worth just being patient and waiting for this g.inp mk2 to be applied? that willl get rid of the added 8ms right? and its coming very soon? right??? Im positive i have the correct firmware installed on my modem for it to work but as my line was installed May1st i assume i have to wait for the rollout to resume or something.

ive been gaming a while. i remember 2006 when it would take 9 months for friends to find a bt agent who knew what interleaving was. ive not really a clue tho when it comes to stats. i was on ntl back then but over time ther jitter got worse and my packets would sit waiting on ther network all night fttc has been great for jitter. jus i lose serious sleep over dlm so any help would be appreciated. thanks

[mbb]

thought id upload thse stats for people to look at. are thse the right ones. they look ok?

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 25636 Kbps, Downstream rate = 74732 Kbps
Bearer:   0, Upstream rate = 19999 Kbps, Downstream rate = 65639 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):    5.9       15.3
Attn(dB):    16.9       0.0
Pwr(dBm):    13.3       7.4
         VDSL2 framing
         Bearer 0
MSGc:      18      26
B:      51      237
M:      1      1
T:      64      42
R:      12      16
S:      0.0252      0.3781
L:      20312      5374
D:      1285      1
I:      64      127
N:      64      254
         Counters
         Bearer 0
OHF:      271400694      840921
OHFErr:      982      898
RS:      758944292      2352660
RSCorr:      2219996      7442
RSUnCorr:   67054      0

         Bearer 0
HEC:      14537      0
OCD:      283      0
LCD:      283      0
Total Cells:   3935289014      0
Data Cells:   360923555      0
Drop Cells:   0
Bit Errors:   0      0

ES:      6507      5285
SES:      52      0
UAS:      100      79
AS:      439545

         Bearer 0
INP:      3.00      0.00
INPRein:   0.00      0.00
delay:      8      0
PER:      1.61      3.98
OR:      118.55      64.22
AgR:      65757.13   20063.54

Bitswap:   296808/296854      3440/3465

Total time = 1 days 23 hours 5 min 31 sec
FEC:      8593504      38459
CRC:      7396      4872
ES:      6507      5285
SES:      52      0
UAS:      100      79
LOS:      2      0
LOF:      13      0
LOM:      0      0
Latest 15 minutes time = 5 min 31 sec
FEC:      773      2
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      256      2
CRC:      0      2
ES:      0      2
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 23 hours 5 min 31 sec
FEC:      201583      817
CRC:      23      170
ES:      7      155
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      437415      5355
CRC:      219      195
ES:      16      164
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 5 days 2 hours 5 min 45 sec
FEC:      2219996      7442
CRC:      982      898
ES:      103      780
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

[simoncraddock]

Total time = 1 days 23 hours 5 min 31 sec
FEC:      8593504      38459
CRC:      7396      4872
ES:      6507      5285
SES:      52      0
UAS:      100      79
LOS:      2      0
LOF:      13      0
LOM:      0      0

Since Link time = 5 days 2 hours 5 min 45 sec
FEC:      2219996      7442
CRC:      982      898
ES:      103      780
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

I don't use a HG612 myself but maybe someone can explain the above 'times' because one says '103 ES' errors since link time of 5 days --- the other says '6507 ES and 52 SES' in just under 2 days. Presuming BT Retail use the speed profile then 6507 ES will most likely flag your line 'red' and apply interleaving which it has done INP=3 DELAY=8 and probably reduced your synch speed down by around 7mbps. If that does indeed show 6507 ES in just under 48hrs then DLM will keep applying interleaving until it can get those errors under control. There's not much you can do apart from check your cables, it might be worth getting a shielded data cable to see if it helps or possibly try a Lantiq based modem/router that displays 'ES' rates. I'm guessing your cabinet is ECI based as their's no G.INP enabled.

[mbb]

thanks for the reply. i am most certain it is a hauwei cabinet as it is one of the big 'double' size cabs. all the cabs round here are. i have seen the small thin eci cabs around other parts of manchester but not around here. im pretty sure i did some test also that said it was broadcomm. my line was installed 1st of may so as it is a new install i guess thats why i dont have g.inp yet

[mbb]

also when i moved house. i had the socket moved to next to my desk. the engineer applied new cable from where the telegraph wire meets the house to a new master socket. i plug the modem directly into master socket and we dont have a phone plugged in.

i guess ther could be a number of things thats making my line unstable. the road is nearly 100 years old so any where underground could be a problem. the wire from telegraph pole passes through a tree but doesnt make contact to branches from what i can see. the new wire he ran to master socket runs next to sky cables. also before line was installed we had full signal to a bt hotspot so its likley a neigbour has fibre. probably on same pole

[simoncraddock]

the engineer applied new cable from where the telegraph wire meets the house to a new master socket

How is the new cable joined to the cable coming from the pole?

[mbb]

as the wire gets to the house it looks like it coils then attaches to the brick work with a metal loop. it looks as though another wire is somehow threaded with this coil and that goes behind the sat dish over the sat cables into a black tube. from that tube it goes round the house into the wall/socket

the engineer that came on install day was just a phone line engineer subcontracted and just came to reconnect the phone line and move socket. my actual fibre install was delayed 3 weeks because of a 'routing' issue

thanks

[simoncraddock]

Sounds pretty standard on the outside, is there a box still fitted where you say the old master socket was?

[mbb]

the old master socket is still on the wall yes but the engineer pulled out the cable form it. ive just double checked and it seems thers no other cables coming from the black box/pole.

[simoncraddock]

Is the new master socket closer or further away from the exterior steel securing loop?
If you plug a corded phone into the master socket and dial 17070 and do a quiet test can you hear any noise?

[mbb]

yes the old cable from securing loop dropped to the bottom of the house and went straight into master socket. now it goes round side and back of house and goes into dining room. i dont have a phone but i will try to get one to try quiet line test. also the line had to be reactivated at the exchange as it hadnt been in service for a while i was told

i have been uploading stats scince about 5pm on mdws username is markb

[mbb]

line rebooted today. interleaving still there but latency gone down to normal. now wheres that smiley with the party hat?  uploading stats to mdws for a few days username is markb

[Weaver]

Apologies if you know all this already, but if you need interleaving then you just need it. Occasional burst errors can come from anywhere (especially in an electrically noisy environment such as yours, urban). And interleave massively improves the effectiveness of error corrrection.

It’s worth trying to minimise the length of cable around the outside of the house, if you want to get the last drop of performance out of it. And it’s also vital to shorten the length of cable (which needs to be screened) between NTE and modem. I did a change-point-of-entry which cost a little cash but only needs to be done once, so that the outside cable comes straight to an upstairs window, NTE is around 2m away, and NTE to modem is 0.5m. From there on, use ethernet cable from modem to router, and then as much ethernet or wirelessness as you like to deal eith issues of positioning convenience and coverage.

Your VDSL2 sync rate is around 35 times faster than mine downstream. Hope that cheers you up.

[mbb]

just a proper ping has cheerd me up mate its not really unlimited if my ping is well.. limited. so u think it could be the new cable outside house thats causing issues. i would have thought possibly some cable join somewhere or underground possibly even rain somewhere thats the problem. i wouldnt say its urban either 15 yrs ago ther were cows grazing 30 secs from the main road. im right on the boarder between salford and wigan its quite green

do my stats on mdws reveal anything obvious about the line? username markb