Print

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

[Black Sheep]

Oh, I see. My bad. 

[ben1066]

Also, not sure if it's just the ECI modem being dumb or there is actually an issue but

Code: [Select]

24 hours Near End Far End
CRC 4294967287 0
FEC 4294965975 0
ES 0 0
SES 0 0
UAS 77 0
Have some pretty graphs too

Just to clarify my previous point, my master socket is where the drop wire comes in. From that a wire goes to the extension sockets, I do not know if it is a "star" or "bus" configuration. Then, one of the extension sockets has had their faceplate replaced with the VDSL SSFP. To that I have connected the VDSL modem and also via another 2 filters as an adapter my HHv2 for it's DECT functionality. I've used 2 filters since 1 didn't seem to stop it trying to tie up the line, adding the second seemed to remedy that. I also have another extension, to which nothing is connected.

EDIT: Since adding the second filter my downstream SNR has shot up from <6dB to 6.4dB. D1 is still only 5.9dB but interestingly D2 is 7.1dB.  Also, for some reason, U2 is hardly being used if you look at the bitloading graph. I have no idea what that's about. Before the uplift more or less all of it was being used (http://forum.kitz.co.uk/index.php?action=dlattach;topic=10635.0;attach=6081;image). Does ADSL overlap U2 at all? I didn't think it would since it's a high frequency.

EDIT2: I'm hoping this data is bogus:

Code: [Select]

Current 15 mins Near End Far End
CRC 4294967256 0
FEC 4294947535 1
ES 4294967256 4294967264
SES 0 4294967291
UAS 0 0
24 hours Near End Far End
CRC 47 0
FEC 24707 1
ES 42 0
SES 4294967295 0
UAS 30 0
EDIT3:
Found the band plan command, first is upstream, second is downstream.

Code: [Select]

Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_fir
stToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2324),(2073,2315))
"
Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_fir
stToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1849))
(02,(2795,3391),(2795,3373))

[ben1066]

Argh! My line now keeps cutting out. The stats show low SNR again Seems I'll have to phone BT and get this installation botch fixed. Yes I removed the (filtered) HHv2 and it has made bugger all difference.

Code: [Select]

Current 15 mins Near End Far End
CRC 4294967292 0
FEC 4294967137 0
ES 114 0
SES 29 0
UAS 66 0
24 hours Near End Far End
CRC 4294967292 0
FEC 4294967137 0
ES 114 0
SES 29 0
UAS 66 0
I'm REALLY hoping that that is bogus. It's not like I can use it to report the damn fault.

[asbokid]

Also, not sure if it's just the ECI modem being dumb or there is actually an issue but

Code: [Select]

24 hours Near End Far End
CRC 4294967287 0
FEC 4294965975 0
ES 0 0
SES 0 0
UAS 77 0

CRC is definitely not identified correctly.  You wouldn't have a connection at all with that error rate.

What you have labelled "CRC" is possibly the count of data blocks passed to the RS decoder (both good and bad data blocks).

Can we see the raw data though?  How is it being labelled by dsl_cpe_control?

EDIT2: I'm hoping this data is bogus:

Code: [Select]

Current 15 mins Near End Far End
CRC 4294967256 0
FEC 4294947535 1
ES 4294967256 4294967264
SES 0 4294967291
UAS 0 0
24 hours Near End Far End
CRC 47 0
FEC 24707 1
ES 42 0
SES 4294967295 0
UAS 30 0

Those aren't parsed correctly.. Reset the counters and maybe watch closely to identify the fields.

EDIT3:
Found the band plan command, first is upstream, second is downstream.

Code: [Select]

Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3 nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2324),(2073,2315))
"
Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3 nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1849))
(02,(2795,3391),(2795,3373))

That was an important find..

cheers, a

[ben1066]

Those error counts are pulled directly from the web interface, aka ECI's not mine. I'll add band plans to eDMT shortly. Still with my connection, could it just be that the DSLAM needs to retrain? That's what I'm hoping for, an uplift really shouldn't be detrimental

[asbokid]

Those error counts are pulled directly from the web interface, aka ECI's not mine.

Any chance you could do a screenshot so we can see all the other stats, please?

I'll add band plans to eDMT shortly.

It would be good to document the strings that are passed to dsl_cpe_control socket to obtain each stat.

Still with my connection, could it just be that the DSLAM needs to retrain? That's what I'm hoping for, an uplift really shouldn't be detrimental

I'm missing the problem.  According to those SpeedTests (which were performed using different servers..) your downstream rate has actually gone up from 37.31Mbps on 13 April to 42.43Mbps on 16 April (today).

[ben1066]

My upstream has significantly decreased, as has the maximum attainable and my latency has increased. I have since then reset my router due to causing the pipe to hang (got a command wrong, causes pipe to hang sometimes). I have had the modem on for just over an hour, and the 24 hour count resets on every reboot so that's one hours worth. That doesn't look so bad. Also, 42/5 is significantly less than the 55/20 I'm estimated.

[asbokid]

My upstream has significantly decreased, as has the maximum attainable and my latency has increased. I have since then reset my router due to causing the pipe to hang (got a command wrong, causes pipe to hang sometimes). I have had the modem on for just over an hour, and the 24 hour count resets on every reboot so that's one hours worth. That doesn't look so bad. Also, 42/5 is significantly less than the 55/20 I'm estimated.

Thank you!

How weird! They look like the sort of nonsensical values you get from referencing uninitialised integers.

cheers, a

[burakkucat]

How weird!

Seconded. That GUI screen shows pure nonsense. 

[ben1066]

Good, still not sure what to about my line though. The fact such a tiny amount of upstream is being used is concerning. And my rates that are about 15 less than estimated is damn well annoying. Could it be the fact that the internal extension has cross-talk on that upstream band?

[ben1066]

Still, what should I do about my upstream going down?

[asbokid]

Still, what should I do about my upstream going down?

Can you provide some raw stats?

If you can get the QLN data that should give some pointers.  Failing that, maybe the error counts plotted over time would offer an indication of the cause.

cheers, a

[ben1066]

I can't get QLN data and I can't find the command for errors, and as you have seen, the web ui errors quickly turn to mush. Before they did I didn't notice many errors, I had a couple thousand FEC after a few hours but that is all.

[asbokid]

Could it be the fact that the internal extension has cross-talk on that upstream band?

Not very likely. But you could eliminate that by Going Commando: plug the modem directly into the test socket behind the NTE faceplate. For good measure, forget the filter.  Re-sync.  If the poor upstream performance persists, then it's not due to consumer wiring.

Still, what should I do about my upstream going down?

I would try to quantify the upstream bandwidth drop over a period of time.  Does it rise and fall?  Are particular times of day worse?

cheers, a

[ben1066]

It's constant across day and night. It was considerably higher before the uplift, and has since dropped. The sync and attainable have barely changed and the band used hasn't either.