Are my line stats good for more sync speed?

http://www.camieabz.co.uk/bb/bbdata.html

When the ADSL2+ change happened I was inexplicably popped onto Annex M. Sync as high as 12500, but the upload SNR was a little jumpy, and throughput was never higher than 9.9 Meg. The system also automatically applied interleaving. FWIW, upload sync was as high as 1450kbp/s, but generally around 1375kbp/s. Upload throughput got up to 1.2 Meg. Pings were initially good at 25ms / 0 jitter, but as the upload snr bottomed out, the sync speeds dropped and pings went up.

Now syncing on Annex A with 13267kbps / 32dB att. / 9dB snr - speedtest came back at 10.3 Meg / 1.0 Meg. Pings are solid 23ms. I have a request for interleaving to be switched off, and the target snr to be set to 6dB, then 3dB if the former is stable.

Do you think 3dB snr is likely, and what speeds should I expect on either, given the existing stats? Should I aim to keep interleaving, given the pings and the intention of dropping snr?

Since line was rejigged to Annex A (6.5 hours ago), here's a breakdown of the errors:

Down:

FEC 0
CRC 1651
HEC 1859
LOF 3
LOS 27
LPR 0
ES 428


Up:

FEC 0
CRC 7
HEC N/A

Thanks! See my bbdata link for more most of that data.

The DLM on ADSL2+ will automatically lower the SNRM to 3dB if it is stable on 6dB, so long as the 6dB is not locked on. I.e. the SNRM is set to Auto.

Is your router RouterStats (Lite) compatible?

If you get interleaving turned off but set to Auto, then again, it will turn it back on if the error rates are too high. You need to do count checks at least once a day for a few days, and more often if they go up a lot, so as to see if there is a particular time they occur.

I'm very surprised at zero FECs given those other errors and the error seconds count. Can you get the full stats? (In particular the D: line).

http://www.camieabz.co.uk/stats2.png

If you can hold 3db then 16,000 should be just about do-able. You need to run routerstats to monitor your SNR over 24 hours to see how likely that is.

Well over past few days the download snr has been in the 8.5 to 9.5 region. The fluctuations in the line were due to upload snr being jumpy on Annex M.

Prior to the changeover, my snr was always 8.0dB or 8.5dB (old router didn't get more specific, and routerstats wouldn't work with it).

Ummm. It does indeed say Interleaved, so I assume it refers to the downstream. The D: figure is usually only available through telnet and gives the depth in each direction, which doesn't need to be the same. 1 is fast path.

Netgear routers even say Fast because the upstream is, even when the downstream is interleaved.

Had a call from Plusnet to confirm Annex M to Annex A change and notice of target SNR 6 reset on the 20th (sigh).

One interesting point; He said my line is fastpath. My BQM does show a drop in ping, so if I'm reading things correctly:

Initial change to ADSL2+ : Pings at mid 20s : routerstats says interleaved : I request Annex A and fastpath

A few days later after a couple of reboots : pings rise to low 40s : interleaving is confirmed on the line by Plusnet

Today : Fastpath confirmed (contrary to routerstats) : pings at mid 20s.


Must be the routerstats and / or the router's reporting. After reboot, pings at 23ms and stats says interleaving.

If you can telnet into the router I reckon xdslcmd info --stats will show what we need.

______  Technicolor TG582n
                         ___/_____/\
                        /         /\\  8.4.4.J.BW
                  _____/__       /  \\
                _/       /\_____/___ \  Copyright (c) 1999-2011, Technicolor
               //       /  \       /\ \
       _______//_______/    \     / _\/______
      /      / \       \    /    / /        /\
   __/      /   \       \  /    / /        / _\__
  / /      /     \_______\/    / /        / /   /\
 /_/______/___________________/ /________/ /___/  \
 \ \      \    ___________    \ \        \ \   \  /
  \_\      \  /          /\    \ \        \ \___\/
     \      \/          /  \    \ \        \  /
      \_____/          /    \    \ \________\/
           /__________/      \    \  /
           \   _____  \      /_____\/
            \ /    /\  \    /___\/
             /____/  \  \  /
             \    \  /___\/
              \____\/

------------------------------------------------------------------------
{admin}=>xdslcmd info
Unknown command.
{admin}=>xdsl info
Modem state:                             up
Up time (Days hh:mm:ss):                 0 days, 3:08:18
xDSL Type:                               ADSL2+
Bandwidth (Down/Up - kbit/s):            13263/1219
{admin}=>

I tried the xdslcmd, to no avail. Never seen that one in the command index. 'xdsl info' gets basic sync data. If you state exactly which stats you're after, since:

1) They're on my linked page in my sig (updated at OP);

2) I posted them above since.

However, have another:

Noise Margin: 9.0 dB
Bandwidth: 13263 kbps
Attenuation: 32.0 dB
Power: 0.0 dBm

Errors:
FEC: 0
CRC: 113
HEC: 672

Failures since last reset: (3:10:58)
LOF: 0
LOS: 0
LPR: 0
ES : 78

Noise Margin: 5.5 dB
Bandwidth: 1219 kbps
Attenuation: 15.9 dB
Power: 12.4 dBm

Errors:
FEC: 0
CRC: 142
HEC: N/A

My bold added for clarity.

A ha!

Re-read one of your posts. Should have said 'line graph'.

http://www.camieabz.co.uk/line.png

First drop was a Plusnet re-sync, while the second was a reboot by me.

whar does xdsl help give you?

I'm looking for something like xdsl info --stats
or xdsl info --show

There has to be something that gives more detail .

For instance, the ones you have listed a couple of times, such as your latest post section 2, I would expect to have a block like:-

B:              239             31
M:              1               2
T:              64              36
R:              0               16
S:              0.1910          0.9922
L:              10054           645
D:              1               1
I:              240             80
N:              240             80

Nope.

http://wiki.aa.org.uk/images/3/33/TG582n_CLI_Guide_v...

See the available commands.

Interesting that doesn't have xdsl info.

How about
ip debug stats proto = <ip>
or
ip debug stats proto = <tcp>

Those just give TCP and IP datagram stats (connections etc.).

The examples you gave:

B:
M:
T:

and so on...if you explain what they mean, or at least what you are are trying to see...maybe I can figure it out myself.

Edited by camieabz (Mon 14-May-12 16:38:13)

I give up .

Unless - I don't know where you got the xdsl info command from, but if I do the equivalent on mine I just get the basic stats. But adding the --info or --show after it gives all the detail.

No idea what most of them are, just that the D: line is the interleaving depth.

But in one of your screen shots I see xdsl info expand=enabled

What does that give, and if "not a lot" how about xdsl info help ?

Just for info - the speedtests today have been very solid 10.5 Meg / 1 Meg.



TBB Meter screenshot of test

Regarding the syntax, no luck on that. I do have a command option xdsl config syslog enable/disable, but don't know how to see said log. xdsl info doesn't bring up anything additional after enabling it. Nor do I see any added info via the browser interface.

http://www.camieabz.co.uk/xdsl.png - Of no value imo.

Also:

http://www.camieabz.co.uk/statx.png

Might be the page I can't see, that's the problem. Not sure.

That enabled page does look like where it should be. But the likely lines are the Delay and Depth ones. The Depth one doesn't make sense though, with the up having a 2 decimal place number.

The 1 for the downstream would tie in with Fast Path, and the Interleaved description at the beginning could, in cocked-up programmimg, tie in with the 0.00 down, as if that is indeed the line than a value of zero is invalid.

As I said, we know that a 1 in the upstream D: on Netgear 834 series causes mode Fast Path to be reported, even when there is a high number in the downstream D:, so its absence here could cause Interleaving to be reported.

All hypothesis. Only a different router is likely to tell us.

Way back, what struck me before you commented on it was the huge drop in latency on the BQM. That did look like Interleaving being turned off.

In reply to a post by RobertoS:

Way back, what struck me before you commented on it was the huge drop in latency on the BQM. That did look like Interleaving being turned off.

I know. It had been that low prior to one or two reboots. I had assumed that my pings had shifted due to latency / gateway / DSLAM profiling or something.

Looks like it was fastpath all the time, then interleaving, then back to fastpath. Pity. I was getting 25ms on ADSL1, and was hoping for an improvement (not sure why).

Actually, it's been in the realms of 23ms; The pingtest servers are never quite as good as TBB's ping monitor.