Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: DSLStats - Gathering the right data and interpreting the results  (Read 498 times)

MultumInParvo

  • Just arrived
  • *
  • Posts: 11

All,

Been doing some searching and reading in this sub-forum to see if I can educate myself a little, but wondered if a sticky could be added to help newbies like me create a well formed question with supporting data before we post queries?

Happy to compile a post if anyone has any suggestions, and perhaps this is easier to base on my problem right now:

I went live on Vodafone fttc on 14/12 and tolerated the settling-in period inconsistent data rates and connection drops, some no doubt caused by the Vodafone router.

I replaced the router with an HG612 and connected up to my RT-AC68U, and today installed DSLStats on my home server started gathering stats.

Speed test results (taken on the server) are lower than when I was on ADSL, see attached.

Server has both NICs attached to the Gig ports on the router and the server, router and modem are all under the stairs within a metre of one another, so I'd hope the data I'm gathering is consistent and has ruled out most other issues such as internal extensions, dodgy cabling, running different tests from different devices, etc.

If anyone can let me know what I need to gather and for how long, I'll get straight on it.

Thanks in advance,

Ian

Logged

j0hn

  • Kitizen
  • ****
  • Posts: 2392
Re: DSLStats - Gathering the right data and interpreting the results
« Reply #1 on: January 03, 2019, 11:50:26 AM »

Post the whole of Telnet Data > Connection Stats for starters.

The best graphs to see the lines general health are Hlog and QLN, and I like seeing the Bitloading graph.
Logged
Plusnet FTTC 80/20 -  ECI now Huawei cab
retx low @ 3dB target SNRM
Zyxel VMG1312-B10A bridged with 1508 MTU + Asus RT-AC68U running Asuswrt-Merlin

johnson

  • Reg Member
  • ***
  • Posts: 642
Re: DSLStats - Gathering the right data and interpreting the results
« Reply #2 on: January 03, 2019, 03:17:48 PM »

Indeed, need the line stats as j0hn mentioned.

Also did vodafone give you any sort of guaranteed minimum, or any indication at all what speeds to expect? What were you receiving on ADSL? What does the bt checker suggest the speed for your address (or one near) is?
Logged

MultumInParvo

  • Just arrived
  • *
  • Posts: 11
Re: DSLStats - Gathering the right data and interpreting the results
« Reply #3 on: January 03, 2019, 05:54:55 PM »

Morning J0hn,

Connection Stats:

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   0
Last initialization procedure status:   0
Max:   Upstream rate = 35516 Kbps, Downstream rate = 97528 Kbps
Bearer:   0, Upstream rate = 9999 Kbps, Downstream rate = 40000 Kbps
Bearer:   1, Upstream rate = 0 Kbps, Downstream rate = 0 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):    23.5       22.7
Attn(dB):    12.5       0.0
Pwr(dBm):    12.8      -0.2
         VDSL2 framing
         Bearer 0
MSGc:      -6      58
B:      178      236
M:      1      1
T:      0      23
R:      12      16
S:      0.1424      0.7543
L:      10727      2694
D:      16      1
I:      191      127
N:      191      254
Q:      16      0
V:      2      0
RxQueue:      22      0
TxQueue:      11      0
G.INP Framing:      18      0
G.INP lookback:      11      0
RRC bits:      0      24
         Bearer 1
MSGc:      90      -6
B:      0      0
M:      2      0
T:      2      0
R:      16      0
S:      10.6667      0.0000
L:      24      0
D:      1      0
I:      32      0
N:      32      0
Q:      0      0
V:      0      0
RxQueue:      0      0
TxQueue:      0      0
G.INP Framing:      0      0
G.INP lookback:      0      0
RRC bits:      0      0
         Counters
         Bearer 0
OHF:      0      1474282
OHFErr:      0      57
RS:      1010556384      4077912
RSCorr:      416      221
RSUnCorr:   0      0
         Bearer 1
OHF:      40486350      0
OHFErr:      0      0
RS:      242917728      0
RSCorr:      2      0
RSUnCorr:   0      0

         Retransmit Counters
rtx_tx:      342      0
rtx_c:      57      0
rtx_uc:      0      0

         G.INP Counters
LEFTRS:      1      0
minEFTR:   39991      0
errFreeBits:   396690241      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   2779059445      0
Data Cells:   2533634872      0
Drop Cells:   0
Bit Errors:   0      0

         Bearer 1
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   0      0
Data Cells:   0      0
Drop Cells:   0
Bit Errors:   0      0

ES:      0      55
SES:      0      0
UAS:      27      27
AS:      650319

         Bearer 0
INP:      47.00      0.00
INPRein:   0.00      0.00
delay:      0      0
PER:      0.00      8.70
OR:      0.01      58.79
AgR:      40055.74   10057.90

         Bearer 1
INP:      2.50      0.00
INPRein:   2.50      0.00
delay:      0      0
PER:      16.06      0.01
OR:      47.81      0.01
AgR:      47.81   0.01

Bitswap:   283868/284395      57/57

Total time = 1 days 12 hours 39 min 6 sec
FEC:      416      221
CRC:      0      57
ES:      0      55
SES:      0      0
UAS:      27      27
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 9 min 6 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:      0      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 = 12 hours 39 min 6 sec
FEC:      20      3
CRC:      0      6
ES:      0      5
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      21      65
CRC:      0      12
ES:      0      11
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 7 days 12 hours 38 min 39 sec
FEC:      416      221
CRC:      0      57
ES:      0      55
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

Hlog:


QLN:


Bitloading:
Logged

MultumInParvo

  • Just arrived
  • *
  • Posts: 11
Re: DSLStats - Gathering the right data and interpreting the results
« Reply #4 on: January 03, 2019, 06:14:10 PM »

Hi Johnson,

They guarantee a 25Mbps Sync Speed, unsurprising as I'm about 800ft from my cabinet.

Sync seems rock solid at 40Mbps if I'm looking at the data correctly.
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 2392
Re: DSLStats - Gathering the right data and interpreting the results
« Reply #5 on: January 03, 2019, 07:51:08 PM »

You are looking at it correct.
You would get the full 80Mb too (you could actually get 97Mb if they didn't cap it to 80).

This tells me you no longer need to look at DslStats.
The issue isn't with the xDSL part of the link.
Your line stats look great.

It's either something wrong with the ISP end of the link or the router/pc being used.
Logged
Plusnet FTTC 80/20 -  ECI now Huawei cab
retx low @ 3dB target SNRM
Zyxel VMG1312-B10A bridged with 1508 MTU + Asus RT-AC68U running Asuswrt-Merlin