Print

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

[Vanburen]

Today Plusnet informed me, that my line had been upgraded to ADSL2+.

However, when I look at the line stats, it states that the connection is G.DMT and not ADSL2+:

Code: [Select]

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 --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max:    Upstream rate = 1220 Kbps, Downstream rate = 7480 Kbps
Channel:        Interleaved, Upstream rate = 1056 Kbps, Downstream rate = 6304 K
bps

Link Power State:       L0
Mode:                   G.DMT
TPS-TC:                 ATM Mode
Trellis:                ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        6.5             12.0
Attn(dB):        34.0            18.5
Pwr(dBm):        20.0            12.6
                        G.dmt framing
K:              198(0)          34
R:              10              4
S:              1               4
D:              32              8
                        Counters
                        Path 0
SF:             496130          496081
SFErr:          23              0
RS:             33736806                8433377
RSCorr:         4455            0
RSUnCorr:       139             0

                        Path 0
HEC:            83              0
OCD:            1               0
LCD:            1               0
Total Cells:    125395506               0
Data Cells:     1289092         0
Drop Cells:     0
Bit Errors:     5498            0

ES:             16              0
SES:            0               0
UAS:            145             145
AS:             8415

                        Path 0
INP:            0.76            0.45
PER:            1.75            1.75
delay:          8.00            8.00
OR:             32.00           32.00

Bitswap:        14              26

Total time = 2 hours 23 min 32 sec
FEC:            4455            0
CRC:            23              0
ES:             16              0
SES:            0               0
UAS:            145             145
LOS:            0               0
LOF:            0               0
Latest 15 minutes time = 8 min 32 sec
FEC:            210             0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            750             0
CRC:            1               0
ES:             1               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Latest 1 day time = 2 hours 23 min 32 sec
FEC:            4455            0
CRC:            23              0
ES:             16              0
SES:            0               0
UAS:            145             145
LOS:            0               0
LOF:            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
Since Link time = 2 hours 20 min 33 sec
FEC:            4455            0
CRC:            23              0
ES:             16              0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
#

So I'm wondering if I have set the router up incorrectly.

I have uploaded some screenshots of my settings pages and was wondering if someone could have a look to see if have set it up correctly? 

Screenshots: https://www.dropbox.com/sh/tbcancx49929gyu/YqTb7jNHCu?v=0mcn

For reference I am using an Huawei HG612, which is running Asbokids's latest custom firmware (from 26-3-13).

Thanks for any help.

[asbokid]

Hello Vanburen,

Welcome to the forum 

No great suggestions, sorry.

At a guess, you've already tried to force an ADSL2+ sync by disabling "All" except ADSL2+ modulation types on this page of the Huawei's web user interface?:

http://www.dropbox.com/sh/tbcancx49929gyu/YqTb7jNHCu?v=0mcn#f:Capture2.PNG

Your line attenuation, 34dB aggregate in the downstream, is moderately high.  It suggests a local loop of more than 2km, perhaps closer to 3km in length?

By comparison, this line, which will happily sync at 19Mbps in ADSL2+ mode, is 1.6km long and has an aggregate downstream attenuation of 25.5dB.   

So perhaps your line just has too great attenuation to support the higher tones used by ADSL2+.  Attenuation is a frequency-specific property.  The higher the tone, the higher its transmission frequency, and the greater the attenuation on that tone.  Once you get to the point that the SNR is too low to support useful modulation on a tone, it gets dropped from use.

During sync initialisation, each available tone (or a selection of them) is measured for attenuation to determine tone availability for bit loading.  Those tones that don't pass muster are dropped from the medley (final) band plan.  During sync, the DSLAM may have discovered that many/most of the higher tones have too low SNR to be used for modulation.  At that point, the DSL scheme is automatically dropped down from ADSL2+, via ADSL2 and ultimately to g.DMT (ADSL1).

Hopefully that's not what's happening in your case. 

Determining your distance from the DSLAM, and the Hlog (attenuation) graph for the tone map could be useful in discovering why your line won't sync in ADSL2+ mode.

cheers, a

[Vanburen]

Hi asbokid, thanks for the kind welcome! 

At a guess, you've already tried to force an ADSL2+ sync by disabling "All" except ADSL2+ modulation types on this page of the Huawei's web user interface?:

Yes, however the ADSL connection then disconnected. I had to select "ALL" to get it to connect again.

Your line attenuation, 34dB aggregate in the downstream, is moderately high.  It suggests a local loop of more than 2km, perhaps closer to 3km in length?

According to the kitz line checker my line is 2.7km (by road), which seems about right to me.

Determining your distance from the DSLAM, and the Hlog (attenuation) graph for the tone map could be useful in discovering why your line won't sync in ADSL2+ mode.

I have uploaded the Tone graph (along with a txt file with the text from telnet) which you can see here: https://www.dropbox.com/sh/y8sfkmiev8cba1t/PnMsQyTaR0


Even though Plusnet have told me ADSL2+ has been activated, could it be the case that BT haven't enabled it in the exchange yet? If so is there any way for me to test for that?

Thanks for your help your work on the HG612 firmware, its very much appreciated!

[Vanburen]

Determining your distance from the DSLAM, and the Hlog (attenuation) graph for the tone map could be useful in discovering why your line won't sync in ADSL2+ mode.

Just realised I misunderstood and didn't upload the Hlog, please find it here: https://www.dropbox.com/s/nkvbrp654hcvncy/HLog-2013-06-03-17.22.10.png

[asbokid]

The Hlog graph shows attenuation of -65dB attenuation at DMT#230 (~1MHz).  That's already a very high measurement. But we can extrapolate the Hlog graph.

Doing so suggests that attenuation simply becomes too great at those higher ADSL2+ frequencies to be loaded with data.   You're perhaps just too far from the exchange for ADSL2+, so the DSLAM falls back to G.DMT (ADSL1).   Just a guess though.

When the line is trying to sync up, it might be instructive to repeatedly invoke the command xdslcmd info --state.  It should indicate the stage that the synchronisation reaches, and why syncing at ADSL2+ is failing:

Code: [Select]

# xdslcmd start --up 

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Idle
Retrain Reason: 8000

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 8000

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.992 Started
Retrain Reason: 8000

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 8000

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.992 Message Exchange
Retrain Reason: 8000

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 8000
Max: Upstream rate = 1144 Kbps, Downstream rate = 20260 Kbps
Channel: INTR, Upstream rate = 1020 Kbps, Downstream rate = 19180 Kbps


cheers, a

[renluop]

As a resident non-tecchie I hesitate to post, but I am with PN and on ADSL2+ with att 47 and SNM 3dB and get some improvement over ADSL2.

PN do  not alter some upgrades immediately, but on the monthly accounting date. Could that be the case here?

I have no intention of disloyalty to Kitz, but have you raised a ticket with PN, or even looked in on its members' forum?

[c6em]

Something is odd
Router says G.DMT but also says upstream sync is 1000+
This is impossible - G.DMT is limited to 448 up stream

Plusnet criterion for ADSL2+ is a sync on 4000 or more will benefit
you are on 6000+ so should get better

Very strange is won't conect on ADSL2+
Something is odd somewhere
Interleaving D of only 32 is also odd - usually seems to be 64 for UK "standard" lines.

Bit loading has big dips and a sharp drop off in loading after mid tones.
dips suggestive of medium wave radio
Does OP have lots of overhead lengths of drop wire - all more prone to picking up Radio intereference at the dips and general intereference anyway from the tone loading drop off.
6300 is low for a 35 db line anyway on G.DMT - might be explained by the above

So my first suggestion is something is wrong with router
Second suggestion is indeed post on Plusnet forums
Some good people on there with the TIME to look into odd behavour of lines.
They are more familiar with routerstats/routerstaslite and the DMT tool as monitoring programs.

[roseway]

Router says G.DMT but also says upstream sync is 1000+
This is impossible - G.DMT is limited to 448 up stream

That's not actually correct - G.Dmt has a maximum upstream rate of 1300 kbps. See https://en.wikipedia.org/wiki/Asymmetric_digital_subscriber_line#ADSL_standards .

The BT implementation of it in ADSL Max limits it to 448 kbps, but on a 21CN enabled exchange I don't think there's any technical reason why it couldn't deliver a higher speed.

[Vanburen]

When the line is trying to sync up, it might be instructive to repeatedly invoke the command xdslcmd info --state.  It should indicate the stage that the synchronisation reaches, and why syncing at ADSL2+ is failing:

Please find my results below (I used a script that sent xdslcmd info --state every 750 Milliseconds, so that's why there where a lot of results, the actually syncing process seemed to happen fairly quickly):

Code: [Select]

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Idle
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.994 Training
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.992 Started
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.992 Started
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.992 Started
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: G.922 Channel Analysis
Retrain Reason: 1

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps

# xdslcmd info --state
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 1156 Kbps, Downstream rate = 6688 Kbps
Channel:        Interleaved, Upstream rate = 960 Kbps, Downstream rate = 6144 Kb
ps


PN do  not alter some upgrades immediately, but on the monthly accounting date. Could that be the case here?

I have no intention of disloyalty to Kitz, but have you raised a ticket with PN, or even looked in on its members' forum?

I didn't realise that, maybe I'll ring them up again to double check. I did call them on Monday (the day of the switchover), as they sent me an email saying they had turned off interleaving on the line, the support guy said this was part of the process when transferring to ADSL2+ and that the line had now been switched over too ADSL2+.

So my first suggestion is something is wrong with router
Second suggestion is indeed post on Plusnet forums
Some good people on there with the TIME to look into odd behavour of lines.
They are more familiar with routerstats/routerstaslite and the DMT tool as monitoring programs.

Good point, although the HG612 is new from Ebay (previously unused), So i wasn't expecting any isseus with it unless i'd got the configuration wrong.

I do have have another ADSL2+ router, I'll try that to see if it will sync at ADSL2+.

I'll start a thread on the Plusnet forums as well.

Thanks to everyone for all the help and input!

[renluop]

AFAICS no sign of thread over on PN Forum, so has OP, perhaps had his problem solved?

[Vanburen]

AFAICS no sign of thread over on PN Forum, so has OP, perhaps had his problem solved?

I tried my backup router today, and that wouldn't connect at ADSL2+ either.

I gave Plusnet another call, and it turns out that even though the exchange has been upgraded to ADSL2+, that my profile was only "half-enabled" for it.

They have put a request through to fully enable it, so it should work from tomorrow (fingers crossed).

[renluop]

Glad it's sorted! :clap2:

[Vanburen]

Just thought i'd post an update, so ADSL2+ has been enabled.

The HLOG now looks like this:
https://www.dropbox.com/s/n7wjs6ipfibmq1p/2013-06-06-10.28.32-HLog.png

And line stats are:

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 8000
Max: Upstream rate = 888 Kbps, Downstream rate = 7444 Kbps
Path: 0, Upstream rate = 888 Kbps, Downstream rate = 6309 Kbps

Link Power State: L0
Mode: ADSL2+
TPS-TC: ATM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.8 13.4
Attn(dB): 37.0 17.9
Pwr(dBm): 19.9 12.8
ADSL2 framing
Path 0
MSGc: 59 10
B: 196 13
M: 1 8
T: 1 9
R: 14 16
S: 0.9941 4.0000
L: 1698 256
D: 32 8
Counters
Path 0
SF: 185366 166364
SFErr: 16 0
RS: 12048723 2994560
RSCorr: 1218 0
RSUnCorr: 259 0

Path 0
HEC: 153 0
OCD: 0 0
LCD: 0 0
Total Cells: 44554296 6244738
Data Cells: 577003 161403
Drop Cells: 0
Bit Errors: 15070 0

ES: 11 0
SES: 0 0
UAS: 52 52
AS: 2991

Path 0
INP: 1.05 2.00
PER: 16.15 18.00
delay: 7.95 8.00
OR: 32.18 7.11

Bitswap: 633 17

Total time = 51 min 5 sec
FEC: 1218 0
CRC: 16 0
ES: 11 0
SES: 0 0
UAS: 52 52
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 6 min 5 sec
FEC: 89 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 424 0
CRC: 4 0
ES: 3 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 51 min 5 sec
FEC: 1218 0
CRC: 16 0
ES: 11 0
SES: 0 0
UAS: 52 52
LOS: 0 0
LOF: 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
Since Link time = 49 min 54 sec
FEC: 1218 0
CRC: 16 0
ES: 11 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

It looks like asbokid was right, that my line is quality is just to bad to get any speed improvements out of ADSL2+.

But can't complain really, I remember a few years ago it was barely going above 2000 kbps downstream 

[roseway]

Your connection is certainly underperforming, compared to what you could reasonably expect for that level of attenuation. Have you made sure that your own internal wiring is in good order? There's some good general advice on this subject here: http://www.kitz.co.uk/adsl/troubleshooting.htm . The only thing I would add is that you don't disconnect/reconnect the router too frequently, otherwise DLM is likely to interpret this as a sign of instability and slow your connection down even more.

The other thing to do is to continue to monitor the connection and see if the graphs throw up any indications of local interference issues which might be impacting on the performance of the connection.

[Vanburen]

Your connection is certainly underperforming, compared to what you could reasonably expect for that level of attenuation. Have you made sure that your own internal wiring is in good order? There's some good general advice on this subject here: http://www.kitz.co.uk/adsl/troubleshooting.htm . The only thing I would add is that you don't disconnect/reconnect the router too frequently, otherwise DLM is likely to interpret this as a sign of instability and slow your connection down even more.

The router is plugged into the Main socket, and I already have a BT i-plate installed. However I could look into fitting a filtered NTE5 Faceplate.

I've been messing around with the connection quite a bit recently, so i'll leave it be for a while, then try plugging the router directly into the test socket to see if it makes any difference.

Do filtered NTE5 Faceplates generally have a benefit over the i-plate?