Register (or login) on our website and you will not see this ad.
|
|
<snip>
Well, don't waste too much time re-inventing the wheel.
There is already a Linux script available that graphs the stats such a bit loading / SNR / band plan / Profile data etc. (via a manually obtained PuTTY log file).
<snip> For those persons wishing to use it, it is available to download from Asbokid's Google Docs pages.
Graphing Script for the line statistics data of the Broadcom BCM63xx VDSL2 chipset modems
Version 2.1
Tue Nov 22 23:37:30 UTC 2011
Based on the ideas of Asbokid and Little_bird.
Enhanced by Bald_Eagle1 and Mystica.
Developed by Burakkucat.
For this script to produce meaningful results, the raw data file
should contain the output of the following four "xdslcmd info"
command interrogations (in no particular order):
xdslcmd info --Bits
xdslcmd info --linediag
xdslcmd info --pbParams
xdslcmd info --show No prize for guessing who's tail was repeatedly pecked by those two birds until the script was ready . . .
-----------------------------------------------------
100% Linux and, previously, Unix.
Edited by burakkucat (Fri 25-Nov-11 16:38:04)
|
|
|
That's what we found as well, epyon!
My parents have an LLU TalkTalk line. Since January, they have some how burnt their way through five or six of the D-Link DSL-2680TT models that TalkTalk supplies to new subscribers.[1] One of those D-Links didn't even last a week 
They've now got a HG612 running on the ADSL2+ line (Infineon DSLAM chipset) and it's getting excellent speeds.
cheers, a
[1] http://forums.thinkbroadband.com/talktalk/t/4015376-...
Edited by deleted (Sat 26-Nov-11 00:05:12)
|
|
|
Hey been lurking around this thread for a while, having had fibre installed last month and being curious about what possible speeds I could get when the cap is lifted to 80/20mbps.
Finally got round to unlocking the modem (thanks to Asbokid and others) to get at the stats earlier, and after picking myself up off the floor  , I got these results (taken about 20 mins ago);
# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 27191 Kbps, Downstream rate = 79360 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39998 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3939)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3939)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 27191 kbps 79360 kbps
Actual Aggregate Tx Power: 6.9 dBm 13.7 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 4.6 22.0 31.7 N/A 11.8 27.2 41.4
Signal Attenuation(dB): 7.2 21.2 30.7 N/A 11.8 27.2 41.4
SNR Margin(dB): 22.8 23.2 23.8 N/A 20.0 18.3 15.3
TX Power(dBm): -4.7 -25.0 6.6 N/A 10.9 8.0 6.6
# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 27199 Kbps, Downstream rate = 79360 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39998 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 17.6 23.6
Attn(dB): 0.0 0.0
Pwr(dBm): 13.7 6.9
Which I think are pretty good results because I estimate the line length to the cabinet to be about 500-600m, probably nearer 600m adding in some error to my estimating.
I did take some other results earlier around 8pm which had the attainable rates nearer 70/25mbps (SNR was 14/22), so possibly a slight drop during peak times assuming those stats are accurate.
Better than I thought, as I was thinking around 60/20mbps tops before based on line length
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
The line statistics are below, and show a 12dB SNRM. I assume that DLM has set it this high, and this is the reason that I used to have a slower speed with the 8c profile. Shame, 'cos the line used to be perfect under ADSLmax.
A high SNR is only a problem if you are syncing at a low speed, in your case it's a good thing.
Even though your SNR is 12dB, thats a good thing since you are synced at the maximum limit, it just means your line has a bit of SNR to spare.
Doh. With ADSLmax doing exactly this for the last 5 years, you'd think I'd be able to remember that little gem.
I guess I'm still slightly annoyed that I didn't get around to unlocking the modem while I was still on the 8c profile - then I'd have really seen what DLM thought was wrong with my line!
|
|
|
curiouser and curiouser.... It seems that my line just had an interesting weekend!
Judging by the BQM, at 8AM Sunday, DLM kicked in and changed my interleaving, as latency went from 13ms up to 22ms. There were a couple of bursts of packet loss noticeable on Saturday (early morning and mid-evening, but still under 5%), but other than that, nothing other than the re-flash to unlock the modem on friday.
The line still syncs at a couple of bps below 40Mb - the IP profile changed from 38716 to 38714. However, the SNRM has dropped by 2dB and the maximum attainable rate has gone up by 2mbps!
I guess the cause can be seen in the ES: over 6,000 in 127,000s of uptime, or about 5%.
The new line statistics are:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
6667
6869
7071
7273
7475
7677
7879
8081
8283
8485
86 | VDSL2 at 600-650 metres, Profile 17a
====================================# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 2Max: Upstream rate = 16936 Kbps, Downstream rate = 60992 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39996 Kbps
Discovery Phase (Initial) Band PlanUS: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3939)Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)DS: (32,859) (1216,1963) (2792,3939)
VDSL Port Details Upstream DownstreamAttainable Net Data Rate: 16936 kbps 60992 kbps
Actual Aggregate Tx Power: 6.7 dBm 12.3 dBm============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3 Line Attenuation(dB): 5.5 28.0 41.2 N/A 14.2 34.8 53.6
Signal Attenuation(dB): 11.0 27.2 40.2 N/A 14.2 34.8 53.6 SNR Margin(dB): 11.4 11.5 11.4 N/A 10.6 10.9 10.9
TX Power(dBm): -3.8 -16.6 6.3 N/A 8.6 7.9 5.3
Line Statistics
===============# xdslcmd info --show
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 2Max: Upstream rate = 16969 Kbps, Downstream rate = 60992 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39996 Kbps
Link Power State: L0Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17aTPS-TC: PTM Mode
Trellis: U:ON /D:ONLine Status: No Defect
Training Status: Showtime Down Up
SNR (dB): 10.8 11.4Attn(dB): 0.0 0.0
Pwr(dBm): 12.3 6.7 VDSL2 framing
Path 0B: 57 111
M: 1 2T: 64 50
R: 16 16S: 0.0461 0.7101
L: 12835 2704D: 701 1
I: 74 120N: 74 240
Counters Path 0
OHF: 57530705 1175287OHFErr: 47 21
RS: 2456009154 3038874RSCorr: 819552 146
RSUnCorr: 1764 0
Path 0HEC: 461 0
OCD: 0 0LCD: 0 0
Total Cells: 1243233476 0Data Cells: 33523218 0
Drop Cells: 0Bit Errors: 0 0
ES: 6136 56
SES: 8 0UAS: 35 35
AS: 127872
Path 0INP: 3.00 0.00
PER: 2.21 8.87delay: 8.00 0.00
OR: 86.72 55.88
Bitswap: 5496 1002 |
I've left Friday's " before" statistics below, for easy comparison.
I finally unlocked the modem, and here are my line statistics...
This was a line that, for the first 2 days on profile 8c, got full 40Mbps but 4% packet loss. DLM intervened, added interleaving and I lost about 4Mbps in profile speed (it was around 34799 according to the BT Speedtester). My line (600-650 metre) should have been able to handle 40 Mbps properly, but I couldn't persuade Plusnet to get Openreach to investigate, as the original estimate was for 30.1Mbps.
When I first changed to the 17a profile, my profile speed returned to the full amount (well, 38716), with no loss of upstream speed.
The line statistics are below, and show a 12dB SNRM. I assume that DLM has set it this high, and this is the reason that I used to have a slower speed with the 8c profile. Shame, 'cos the line used to be perfect under ADSLmax.
It does seem to show that my line is using both U2 and D3.
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
6667
6869
7071
7273
7475
7677
7879
8081
8283
8485
86 | VDSL2 at 600-650 metres, Profile 17a
====================================# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 0Max: Upstream rate = 16835 Kbps, Downstream rate = 58848 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39998 Kbps
Discovery Phase (Initial) Band PlanUS: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3939)Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)DS: (32,859) (1216,1963) (2792,3939)
VDSL Port Details Upstream DownstreamAttainable Net Data Rate: 16835 kbps 58848 kbps
Actual Aggregate Tx Power: 6.6 dBm 11.6 dBm============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3 Line Attenuation(dB): 5.5 28.0 41.2 N/A 14.2 34.7 53.6
Signal Attenuation(dB): 10.6 27.2 40.3 N/A 14.2 34.7 53.6 SNR Margin(dB): 11.2 11.4 11.4 N/A 12.6 12.6 12.8
TX Power(dBm): -3.9 -16.5 6.3 N/A 8.3 7.8 2.3
Line Statistics
===============# xdslcmd info --show
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 0Max: Upstream rate = 16843 Kbps, Downstream rate = 58848 Kbps
Path: 0, Upstream rate = 10000 Kbps, Downstream rate = 39998 Kbps
Link Power State: L0Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17aTPS-TC: PTM Mode
Trellis: U:ON /D:ONLine Status: No Defect
Training Status: Showtime Down Up
SNR (dB): 12.6 11.4Attn(dB): 0.0 0.0
Pwr(dBm): 11.6 6.6 VDSL2 framing
Path 0B: 239 111
M: 1 2T: 64 50
R: 0 16S: 0.1909 0.7101
L: 10055 2704D: 1 1
I: 240 120N: 240 240
Counters Path 0
OHF: 354474 122709OHFErr: 7 1
RS: 0 1839623RSCorr: 0 3
RSUnCorr: 0 0
Path 0HEC: 49 0
OCD: 0 0LCD: 0 0
Total Cells: 83459324 0Data Cells: 759 0
Drop Cells: 0Bit Errors: 0 0
ES: 6 1
SES: 0 0UAS: 17 17
AS: 1089
Path 0INP: 0.00 0.00
PER: 3.05 8.87delay: 0.00 0.00
OR: 65.46 55.88
Bitswap: 1 2 |
Now for the graphs this afternoon...
|
|
|
Thanks for that suggestion, but it looks a little top-heavy when considering all the other software needed to go with it.
It is indeed, but on a Linux box, most of that stuff is there already.
On the whole, it sounds like you are using it the same way I was - to show the line stats & error counts over time, so you can show a faulty line.
It sounds like I might need to do the same now - even though mine isn't as bad as yours, I got the same response out of Plusnet. A good set of graphs can help show how the line changes over the next few months.
Well, don't waste too much time re-inventing the wheel.
There is already a Linux script available that graphs the stats such a bit loading / SNR / band plan / Profile data etc. (via a manually obtained PuTTY log file).
Yes, I'll grab those scripts too - it'll be good to see the bit-loading graphs on a one-off basis; my cacti scripts can handle indicidual numbers over time (they're polled every 5 minutes), but they can't do those kind of graphs.
It was the really high error count, depicted graphically that swung it for me.
I was getting up to 2 MILLION CRC errors per day, but Plusnet's own remote tests showed the connection as all O.K.
They only really see Sync speed & connection up time.
With ADSLmax, we had an 8128 connection, without interleaving, and getting about 10 CRC errors every hour - extremely clean. It obviously isn't behaving so well with FTTC (6,000 ES in the last 127,000s or 36 hours), but that's not a patch on your numbers!
Strange that BT want to hide these numbers from us, when they can be a key part of identifying problems.
If you really do want to start from scratch again, just one useful modem URL to "curl" for data is "http://192.168.1.1/html/status/xdslStatus.asp"
That looks incredibly useful. No authentication needed 
|
|
|
Interesting, your TX Power has increased too, especially in D3.
Also your Retrain Reason has changed from 0 to 2. I asked a while ago on here if anyone knew what the values for Retrain Reason meant and didn't get a reply. I wonder if anyone can now deduce something from your before and after.
Mine changed from 0 to 2 while on 8c and has stayed there. The maximum attainable rate decreased and the sync increased. Below are my before and after.
I've only ever seen the values 0 and 2 on both my and others stats. My guess is 0 = Retrain but no changes and 2 = Retrain for changes to take effect. If that is true I don't see why when the value cahnges to 2 it stays there and doesn't revert back to 0.
I think it would be usefull to know for sure what the Retrain Reason values represent.
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.09.24 02:17:24 =~=~=~=~=~=~=~=~=~=~=~=
# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 0Max: Upstream rate = 15880 Kbps, Downstream rate = 40956 Kbps
Path: 0, Upstream rate = 9999 Kbps, Downstream rate = 34947 Kbps
Discovery Phase (Initial) Band PlanUS: (0,95) (696,1183)
DS: (32,687) (1192,1627) Medley Phase (Final) Band Plan
US: (0,95) (696,1183) DS: (32,687) (1192,1627)
VDSL Port Details Upstream DownstreamAttainable Net Data Rate: 15880 kbps 40956 kbps
Actual Aggregate Tx Power: - 13.8 dBm 8.8 dBm============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3 Line Attenuation(dB): 3.6 18.6 N/A N/A 9.6 23.3 N/A
Signal Attenuation(dB): 0.0 17.5 N/A N/A 9.6 23.3 N/A SNR Margin(dB): 14.6 14.6 N/A N/A 6.3 6.3 N/A
TX Power(dBm): -25.0 -14.1 N/A N/A 7.5 2.8 N/A |
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2011.09.26 14:58:03 =~=~=~=~=~=~=~=~=~=~=~=
# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY statusStatus: Showtime
Retrain Reason: 2Max: Upstream rate = 15934 Kbps, Downstream rate = 39448 Kbps
Path: 0, Upstream rate = 9999 Kbps, Downstream rate = 39001 Kbps
Discovery Phase (Initial) Band PlanUS: (0,95) (696,1183)
DS: (32,687) (1192,1627) Medley Phase (Final) Band Plan
US: (0,95) (696,1183) DS: (32,687) (1192,1627)
VDSL Port Details Upstream DownstreamAttainable Net Data Rate: 15934 kbps 39448 kbps
Actual Aggregate Tx Power: - 13.6 dBm 8.8 dBm============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3 Line Attenuation(dB): 3.6 18.6 N/A N/A 9.6 23.4 N/A
Signal Attenuation(dB): 0.0 17.5 N/A N/A 9.6 23.4 N/A SNR Margin(dB): 14.8 14.8 N/A N/A 6.3 6.3 N/A
TX Power(dBm): -25.0 -13.9 N/A N/A 7.5 2.7 N/A |
|
|
|
I am on profile 17a & my Retrain reason is 0.
I rebooted the modem erlier on today.
Don't know if that is relevant or not.
Paul.
P.S. I'm now using Plink rather than PuTTy as it enables autologin to the modem in order to download the whole log & create the graphs with just a double click.
I have created Windows batch files to do all this & will relase them soon.
Paul.
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
| =~=~=~=~=~=~=~=~=~=~=~= Plink log 2011.11.29 20:37:33 =~=~=~=~=~=~=~=~=~=~=~=
BusyBox v1.9.1 (2010-10-15 17:59:06 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslcmd info --pbParams xdslcmd: ADSL driver and PHY status
Status: ShowtimeRetrain Reason: 0
Max: Upstream rate = 5675 Kbps, Downstream rate = 30856 KbpsPath: 0, Upstream rate = 5679 Kbps, Downstream rate = 27942 Kbps
Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783) DS: (32,859) (1216,1963) (2792,3939)
Medley Phase (Final) Band PlanUS: (0,95) (868,1207)
DS: (32,859) (1216,1963) VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 5675 kbps 30856 kbpsActual Aggregate Tx Power: 6.3 dBm 12.1 dBm
============================================================================ VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 8.2 53.5 64.1 N/A 21.9 63.8 70.0 Signal Attenuation(dB): 14.7 52.8 N/A N/A 21.9 63.8 N/A
SNR Margin(dB): 6.1 6.1 N/A N/A 4.7 4.7 N/A TX Power(dBm): -4.4 5.9 N/A N/A 11.1 5.3 N/A |
Edited by deleted (Tue 29-Nov-11 21:30:24)
|
|
|
|
Good work Paul. I look forward to giving your batch files a whirl!
Barry
|
|
|
Interesting, your TX Power has increased too, especially in D3.
Also your Retrain Reason has changed from 0 to 2. I asked a while ago on here if anyone knew what the values for Retrain Reason meant and didn't get a reply. I wonder if anyone can now deduce something from your before and after.
Mine changed from 0 to 2 while on 8c and has stayed there. The maximum attainable rate decreased and the sync increased. Below are my before and after.
I've only ever seen the values 0 and 2 on both my and others stats. My guess is 0 = Retrain but no changes and 2 = Retrain for changes to take effect. If that is true I don't see why when the value cahnges to 2 it stays there and doesn't revert back to 0.
I think it would be useful to know for sure what the Retrain Reason values represent.
Hi Croftie!
JustAnother has launched a much-needed project to understand and document the functionality of the xdslcmd tool from the Broadcom firmware. [1]
According to the ITU-T Recommendations, the re-training procedure is "optional and vendor proprietary". See the State Diagrams in G992.3 [2] The reason codes reported by the Huawei for re-training are presumably vendor-specific, too.
In those State Diagrams from the specs, the only reason given for a re-train is a high Bit Error Rate (BER). A high BER could occur for a number of reasons, including a complete loss of signal.
However, we can look under the bonnet at the source code of Broadcom's 63xx drivers to uncover reason codes reported by the Huawei [3]
A case of "Grep the Source, Luke!" :
From the bcmdrivers/broadcom/include/impl1/AdslMibDef.h header file, we find:
| Text | 1
23
45
67
8 | /* AdslPhys status definitions */
#define kAdslPhysStatusNoDefect (1 << 0)
#define kAdslPhysStatusLOF (1 << 1) /* lossOfFraming (not receiving valid frame) */#define kAdslPhysStatusLOS (1 << 2) /* lossOfSignal (not receiving signal) */
#define kAdslPhysStatusLPR (1 << 3) /* lossOfPower */#define kAdslPhysStatusLOSQ (1 << 4) /* lossOfSignalQuality */
#define kAdslPhysStatusLOM (1 << 5) /* lossOfMargin */ |
The << symbol is used in C as the bitwise operator symbol for a logical left shift of n bits.
For example, 1<<3 means left shift by three bits. In other words, 2^3, or 8.
So these are likely to be the reason codes for re-training:
Loss Of Framing (not receiving valid frame) : re-train reason code of 2.
Loss Of Signal (not receiving signal) : re-train reason code of 4.
Loss Of Power : re-train reason code of 8.
Loss Of Signal Quality : re-train reason code of 16.
Loss Of Margin : re-train reason code of 32.
cheers, a
[1] http://forum.kitz.co.uk/index.php/topic,10269.msg205...
[2] http://www.analytic.ru/articles/lib26.pdf
[3] http://huaweihg612hacking.wordpress.com/2011/07/26/b...
Edited by deleted (Wed 30-Nov-11 14:33:39)
|
|
|
Pages in this thread: 
Print Thread
