Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: Primus84 on November 27, 2014, 04:02:15 PM
-
Hi could anyone help me interpret my stats? I hope I've given you everything you need but let me know if not!
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 45967 Kbps, Downstream rate = 120200 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 Kbps
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
Medley Phase (Final) Band Plan
US: (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 45967 kbps 120200 kbps
Actual Aggregate Tx Power: 3.4 dBm 12.5 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 5.1 16.0 22.5 N/A N/A 8.5 19.2 29.8
Signal Attenuation(dB): N/A 15.1 21.7 N/A N/A 11.4 19.1 29.8
SNR Margin(dB): N/A 22.8 22.5 N/A N/A 18.3 18.3 18.3
TX Power(dBm): N/A -27.4 3.4 N/A N/A 8.2 8.0 6.8
#
-
A lot of people would be very envious of stats like that. There's such a large gap between the actual connection speeds ('Bearer') and the attainable ('Max') that you must be very close to the cabinet. If you want a detailed look at the finer points of the connection you could install DSLstats or HG612 Stats, but on the information you've given I would say it's close to perfect.
-
How do I tell if I'm on fast path or interleaved?
-
How do I tell if I'm on fast path or interleaved?
You will need to look at the output produced by the xdslcmd info --stats command line.
-
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 46071 Kbps, Downstream rate = 119336 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 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): 18.0 22.3
Attn(dB): 13.3 0.0
Pwr(dBm): 12.5 3.4
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 237
M: 1 1
T: 23 42
R: 0 16
S: 0.0955 0.3781
L: 20104 5374
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 17124697 2908696
OHFErr: 211 5
RS: 0 3227905
RSCorr: 0 28
RSUnCorr: 0 0
Bearer 0
HEC: 1434 0
OCD: 34 0
LCD: 34 0
Total Cells: 59552248 0
Data Cells: 753012072 0
Drop Cells: 0
Bit Errors: 0 0
ES: 158 5
SES: 0 0
UAS: 26 26
AS: 28322
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 3.98
OR: 116.09 64.22
AgR: 80103.09 20063.54
Bitswap: 23598/23598 13/13
Total time = 7 hours 52 min 28 sec
FEC: 0 28
CRC: 211 5
ES: 158 5
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 28 sec
FEC: 0 0
CRC: 3 0
ES: 3 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: 0 3
CRC: 4 0
ES: 4 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 7 hours 52 min 28 sec
FEC: 0 28
CRC: 211 5
ES: 158 5
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 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 = 7 hours 52 min 1 sec
FEC: 0 28
CRC: 211 5
ES: 158 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
FTTC doesnt use FAST path, but this
D: 1 1
states an interleave depth of 1, which in effect is the equivalent of no interleaving
-
Thanks, so it's looking like an excellent connection.
-
From the info provided yes. :)
There are also a few other things that could give a wider picture. For example your E/Secs total over the course of the day, bit loading and SNRm graphs etc. If you want those, I can only repeat what eric said
If you want a detailed look at the finer points of the connection you could install DSLstats or HG612 Stats,
-
Ok, now getting these stats on day 2, am I now being interleaved? I've lost some sync speed but cannot work out why.
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 47661 Kbps, Downstream rate = 122368 Kbps
Bearer: 0, Upstream rate = 19997 Kbps, Downstream rate = 72272 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): 16.3 21.4
Attn(dB): 13.3 0.0
Pwr(dBm): 12.4 3.8
VDSL2 framing
Bearer 0
MSGc: 18 34
B: 47 35
M: 1 1
T: 64 64
R: 16 12
S: 0.0211 0.0572
L: 24232 6715
D: 1137 563
I: 64 48
N: 64 48
Counters
Bearer 0
OHF: 32383482 2275121
OHFErr: 33 0
RS: 3995016762 4061882
RSCorr: 104762 5157
RSUnCorr: 96 0
Bearer 0
HEC: 20 0
OCD: 1 0
LCD: 1 0
Total Cells: 1812327932 0
Data Cells: 17995942 0
Drop Cells: 0
Bit Errors: 0 0
ES: 335 8
SES: 10 0
UAS: 60 50
AS: 43963
Bearer 0
INP: 3.00 4.00
INPRein: 0.00 0.00
delay: 6 8
PER: 1.35 4.59
OR: 141.43 69.67
AgR: 72413.13 20066.61
Bitswap: 34177/34177 29/29
Total time = 1 days 6 hours 32 min 13 sec
FEC: 104762 5157
CRC: 33 0
ES: 335 8
SES: 10 0
UAS: 60 50
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 2 min 13 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
Previous 15 minutes time = 15 min 0 sec
FEC: 3389 0
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 = 6 hours 32 min 13 sec
FEC: 60383 3763
CRC: 20 0
ES: 6 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 44379 1394
CRC: 13 0
ES: 329 8
SES: 10 0
UAS: 60 50
LOS: 1 0
LOF: 9 0
LOM: 0 0
Since Link time = 12 hours 12 min 41 sec
FEC: 104762 5157
CRC: 33 0
ES: 11 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
Ok, now getting these stats on day 2, am I now being interleaved?
Yes, at quite a high DS depth of 1137 & a very high US depth of 563 for US.
US interleaving depth is usually at 1 (fastpath equivalent) or very low depth (in the tens rather than hundreds).
It does 'appear' to have been due to some sort of Impulse Noise as Impulse Noise Protection (INP) & delay have been applied (quite unusually high regarding US):-
INP: 3.00 4.00
delay: 6 8
compared to your first stats:-
INP: 0.00 0.00
delay: 0 0
I've lost some sync speed but cannot work out why.
It would have been interesting to see some 24/7 logging graphs from the outset to see exactly what might have caused DLM to intervene.
-
I'm on a mac so due to it being a bit more involved to run the software hadn't bothered, is it worth firing up a VM and doing some logging now?
-
I'm on a mac so due to it being a bit more involved to run the software hadn't bothered, is it worth firing up a VM and doing some logging now?
I would, but I must admit that I'm a bit obsessed with VDSL2 connection stats.
In the meantime though, directly from your Mac (as regularly done by one of our other forum members), you could collate the output from these commands into a single plain text file, compress it & attach it to a reply in this thread.
I could then plot & attach a set of snapshot graphs for you to examine:-
xdslcmd info --stats
xdslcmd info --pbParams
xdslcmd info --Bits
xdslcmd info --SNR
xdslcmd info --QLN
xdslcmd info --Hlog
xdslcmd info --show
xdslcmd info --version
-
xdslcmd info --stats
xdslcmd info --pbParams
xdslcmd info --Bits
xdslcmd info --SNR
xdslcmd info --QLN
xdslcmd info --Hlog
xdslcmd info --show
xdslcmd info --version
And conclude that list of command lines with --
equipcmd swversion display
-
I've launched a VM and have DSLStats and HG612 modem stats now running - will these log everything I need?
-
I've launched a VM and have DSLStats and HG612 modem stats now running - will these log everything I need?
Yes, most certainly. :)
-
Do I need to let em run now or is there something I can post that will assist with identifying the reason the connection speed has dropped?
Thanks for all the help so far :)
-
With HG612 Modem Stats, you should see scheduled snapshot & Ongoing montages graphs auto-generated in the Current_Stats & Ongoing _Stats folders, but you can click the Run snapshot stats button any time you wish to obtain a snapshot montage of the most important stats.
You could do the same via the RunGraphPD button for Ongoing stats, but it would be best to leave that one until a few hours worth of stats have been logged.
-
Ok, it hasn't disconnected since the last set of data so it seems to have stabilised. I've been running the logging since yesterday evening so is there anything I can post up yet or do I need to leave it log for longer?
-
You can use HG612 modem stats to run a Graph PD (bottom right) When the cmd window comes up enter "1 d" for 1 day or 12 h for 12 hrs etc, then you can post the full_monty stats (the long mode which fits forum windows), which will be found in the Ongoing Stats folder.
Alternatively you can screen grab any of the DSLstats graphs when ever you like.
Running 24/7 gives a much better indication of your line particularly when it comes to things like SNRmargin and CRCs etc. Posting the one set of figures only gives us a snapshot of one second in time. I'd had a sneaky feeling that you may be seeing some ErrSecs, but the data from the one set of figures didnt give me enough info. This is surprising because I wouldnt expect to see them on such a good line.
Its obvious now that you must have been getting them, or the DLM wouldnt have interleaved you :(
-
Here they are
-
Hmmm I cant see anything which indicates the source of errors. The SNR Margin seems nice and steady. The Errored seconds seem low enough, but then again youve got some pretty heavy interleaving going on right now :/
Whats puzzling me is that I cant see anything which would have caused upstream Interleaving. Out of curiousity, did you reboot your modem lots of times on the 27th?
-
No, it's never been rebooted since it was installed.
-
Hmmmmmmmm again.
So on day 2, the DLM applies some really heavy interleaving on both upstream and downstream. Yet its a good line with plenty of spare SNRm that looks pretty flatlined.
I thought DLM was supposed to leave new lines alone for the first day - unless its seen lots of retrains. :hmm:
Whats going on here.. I can see that there are some CRCs and Err seconds, but based on the first set of stats that shouldnt have been enough to trigger DLM. I cant even see anything wrong with the upstream.
Thoughts anyone else? BE et al. Have I missed something
-
No, I don't think that anything has been missed. :no: It seems that this circuit has been penalised unnecessarily. :(
-
Is there anything I can do? If I leave it connected and wait will it fix itself by allowing the DLM to relax?
-
This kitteh is getting a real bad twitch in her whiskers.
Brand new line thats not even had a full day free from DLM. DLM goes in straight for the kill on the first night both barrels blasting.
Ive just checked starmans line, he was interleaved too last night. Although we've been expecting that, but what wasnt expected is it gone straight from 0 to 1105. He's not ever been that high before. He's previously been 643 when he had his line fault.
Im not liking the feeling Im getting one little bit. Is this the 'new' DLM? :hmm:
@Primus. Just right now I dont think theres much you can do. You can attempt to contact your ISP, but they'd only give you the "10 day training rubbish" Even though it doesnt apply to FTTC.
For now all you can do is sit tight and watch and monitor. If it was me though I would be mentioning it on your ISP forum board, because if it is what I hope it isnt, then I get a feeling that there may soon be others starting to complain.
Based on the evidence so far, I cannot see any legitimate reason why your line should be interleaved. The line would however need to be monitored for a longer period than it has been to be able to give you a definite answer.
-
I'm BT - is their user board worth mentioning this on - what I mean is do they actually monitor and help out or is it more peer-to-peer help?
-
Yes its worth it. They do have staff that monitor, theres also a few of the adsl techy types that post there (you may on occasion see names that post on both - but you wont see me/BE/b*cat post there as we're not with BT. If it was me I'd certainly be posting it on my ISP's forum.
I'd post your first day stats showing the attainable 120200. Its also worth mentioning that youre running DSLstats and your SNR Margin is flatlining. You never know one of the more decent reps with half a clue may spot it. Post your interleaving & INP totals now because they indicate youve been put on a really high profile which is why now you can only sync at 72,272 (mention that too).
Its up to you whether you mention that youve been here and we cannot see any valid reason why interleaving should have been applied because line conditions appear to be exceptionally good and if you wonder if could be related to the new DLM.
I would not mention anything though about ASSIA and why theres a new DLM, otherwise the BT staff may just stick their head in the sand and run a mile. :-\
I hope its not the new DLM and this is whats to come.. but the thing is, if it is a mistake and the line has been profiled incorrectly then it will need the assistance of your ISP to get it removed.
Please do keep us informed.. I'm really interested in seeing what happens. Good luck.
-
I would not mention anything though about ASSIA and why theres a new DLM, otherwise the BT staff may just stick their head in the sand and run a mile. :-\
There have been occasions, in the past, when something of the above ilk has been raised in a BT forum thread for the post in question being deleted. :o (Totally inappropriate action by a moderator. >:( )
-
Yes Ive heard similar too and I think its really bad that they delete the whole post/thread, especially if the EU is reporting a valid issue with their line :/
TBH Im hoping that its been wrongly profiled, it will be easier for the OP. I dont like DLMs that work backwards - which funny enough is what the ASSIA Sky one did. ::)
-
Is there anything I can do? If I leave it connected and wait will it fix itself by allowing the DLM to relax?
It may be helpful if we could see one of your snapshot montages (portrait format) from a subfolder of Current_Stats, just to see if we can spot any 'physical' line issues.
-
It's weird, look at today's stats! Speed is back and no interleaving or INP!
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 45689 Kbps, Downstream rate = 120472 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 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): 18.2 23.2
Attn(dB): 13.3 0.0
Pwr(dBm): 12.4 3.4
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 237
M: 1 1
T: 23 42
R: 0 16
S: 0.0955 0.3781
L: 20104 5374
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 16324149 2575087
OHFErr: 179 5
RS: 0 2107429
RSCorr: 0 50
RSUnCorr: 0 0
Bearer 0
HEC: 1409 0
OCD: 35 0
LCD: 35 0
Total Cells: 4150952443 0
Data Cells: 3726342 0
Drop Cells: 0
Bit Errors: 0 0
ES: 512 13
SES: 21 0
UAS: 95 74
AS: 26999
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 3.98
OR: 116.09 64.22
AgR: 80103.09 20063.54
Bitswap: 19140/19140 30/30
Total time = 1 days 21 hours 47 min 39 sec
FEC: 0 121
CRC: 6199 13
ES: 512 13
SES: 21 0
UAS: 95 74
LOS: 2 0
LOF: 19 0
LOM: 0 0
Latest 15 minutes time = 2 min 39 sec
FEC: 0 0
CRC: 1 0
ES: 1 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: 0 3
CRC: 13 0
ES: 8 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 21 hours 47 min 39 sec
FEC: 0 50
CRC: 179 5
ES: 162 5
SES: 11 0
UAS: 35 24
LOS: 1 0
LOF: 10 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 0
CRC: 0 0
ES: 21 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 7 hours 29 min 57 sec
FEC: 0 50
CRC: 179 5
ES: 138 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
One thing we know is that the DLM ILQ can quite quickly recover some good lines. BT are being quite secretive on the ILQ and its one of the areas where Ive struggled to find information on whilst trying to research the DLM. The ILQ is basically what decides how soon your line recovers when the DLM kicks in. From what I can gather it seems to double the recovery time at each offence. Incidentally it appears that it may also be part of the ILQ algorithm which has been involved in one of the ASSIA patent legal cases.
If its a first offence then it will recover the next day - Ive had this happen myself on one occasion on the previous system. But normally it will recover in steps.
I notice this morning that broadstairs has also been DLM'd and just like the yesterdays 2 cases, it went straight in at a very high level.
Yours has come down from a very high level back to 0. So no in between steps like we used to see. So perhaps this is what they are now doing. I honestly dont know and I doubt BT will tell us, especially when theres still another court case pending.
Thank you for providing your stats, the more people like you who are able to show us what is happening, then the more chance we have of figuring out what it is they are now doing.
-
Thank you to everyone for being so helpful and explaining things to me!
-
Still looking good I think:
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 44328 Kbps, Downstream rate = 119608 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 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): 17.9 23.1
Attn(dB): 13.3 0.0
Pwr(dBm): 12.4 3.4
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 237
M: 1 1
T: 23 42
R: 0 16
S: 0.0955 0.3781
L: 20104 5374
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 83603374 1021303
OHFErr: 763 25
RS: 0 2342021
RSCorr: 0 181
RSUnCorr: 0 0
Bearer 0
HEC: 5403 0
OCD: 129 0
LCD: 129 0
Total Cells: 4079202271 0
Data Cells: 189524264 0
Drop Cells: 0
Bit Errors: 0 0
ES: 975 33
SES: 21 0
UAS: 95 74
AS: 138271
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 3.98
OR: 116.09 64.22
AgR: 80103.09 20063.54
Bitswap: 105670/105670 110/110
Total time = 1 days 4 hours 42 min 11 sec
FEC: 0 252
CRC: 6783 33
ES: 975 33
SES: 21 0
UAS: 95 74
LOS: 2 0
LOF: 19 0
LOM: 0 0
Latest 15 minutes time = 12 min 11 sec
FEC: 0 1
CRC: 3 0
ES: 2 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: 0 1
CRC: 8 0
ES: 7 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 4 hours 42 min 11 sec
FEC: 0 24
CRC: 131 3
ES: 98 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 95
CRC: 399 15
ES: 322 15
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 14 hours 24 min 31 sec
FEC: 0 181
CRC: 763 25
ES: 601 25
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0