Print

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

[Zenfield]

Hi,
A little bit of background before I start,
Unfortunately in the past year or so i've had issues with rein interferance caused by a faulty thermostat. Once the thermostat had been replaced the dropouts during early mornings and late evenings had stopped. Its been over a month since my issue has been fixed yet I seem to still be interleaved.
Im currently with IDnet on their gamers package (80/20) which gives me priority at the exchange with elevated traffic. Ive rang them numerous times asking for a DLM reset but they refuse to do so as im reaching the attainable speeds that BT have outlined for my property.
Im currently monitoring my stats on MDWS so all stats are available upon request
Ive tried uploading my stats on MDWS but to no avail (still trying to figure out why)

I apologise having to upload my stats in this format as this is the only way possible for the minute until i can figure out how to get them on the web page.

Thanks for all help and input provided in advance

Regards,

Zen

Stats recorded 27 Feb 2018 21:28:31

DSLAM/MSAN type:           BDCM:0xa48c / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    8 days 9 hours 6 min 56 sec
Resyncs:                   0 (since 27 Feb 2018 20:42:55)
         
            Downstream   Upstream
Line attenuation (dB):     9.3      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           6.6      15.6
Power (dBm):               12.6      -6.8
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0016      7.5942
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      18.0

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   0
Last initialization procedure status:   0
Max:   Upstream rate = 28559 Kbps, Downstream rate = 82392 Kbps
Bearer:   0, Upstream rate = 19999 Kbps, Downstream rate = 79999 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):    6.6       15.5
Attn(dB):    9.3       0.0
Pwr(dBm):    12.6      -6.8
         VDSL2 framing
         Bearer 0
MSGc:      -6      26
B:      130      237
M:      1      1
T:      0      42
R:      8      16
S:      0.0518      0.3781
L:      21468      5374
D:      16      1
I:      139      127
N:      139      254
Q:      16      0
V:      14      0
RxQueue:      60      0
TxQueue:      20      0
G.INP Framing:      18      0
G.INP lookback:      20      0
RRC bits:      0      24
         Bearer 1
MSGc:      186      -6
B:      0      0
M:      2      0
T:      2      0
R:      16      0
S:      5.3333      0.0000
L:      48      0
D:      3      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      691584
OHFErr:      52      4004
RS:      4164082640      2290839
RSCorr:      66357      53507
RSUnCorr:   0      0
         Bearer 1
OHF:      45083517      0
OHFErr:      0      0
RS:      541001463      0
RSCorr:      3      0
RSUnCorr:   0      0

         Retransmit Counters
rtx_tx:      7817893      0
rtx_c:      3698      0
rtx_uc:      3430      0

         G.INP Counters
LEFTRS:      47      0
minEFTR:   79966      0
errFreeBits:   883627495      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   4033043549      0
Data Cells:   2380904162      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:      12      2863
SES:      0      1
UAS:      27      27
AS:      724166

         Bearer 0
INP:      48.00      0.00
INPRein:   0.00      0.00
delay:      0      0
PER:      0.00      3.98
OR:      0.01      64.22
AgR:      80614.82   20063.54

         Bearer 1
INP:      4.00      0.00
INPRein:   4.00      0.00
delay:      3      0
PER:      16.06      0.01
OR:      95.62      0.01
AgR:      95.62   0.01

Bitswap:   311944/311944      1530/1530

Total time = 1 days 9 hours 9 min 53 sec
FEC:      66357      53507
CRC:      52      4004
ES:      12      2863
SES:      0      1
UAS:      27      27
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 9 min 53 sec
FEC:      81      9
CRC:      0      5
ES:      0      5
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      113      26
CRC:      0      7
ES:      0      5
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 9 hours 9 min 53 sec
FEC:      3589      982
CRC:      0      255
ES:      0      175
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      7441      6319
CRC:      0      516
ES:      0      377
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 8 days 9 hours 9 min 25 sec
FEC:      66357      53507
CRC:      52      4004
ES:      12      2863
SES:      0      1
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#

[Ixel]

Unless I'm mistaken, the stats you've posted show that you're on G.INP. You aren't on traditional interleaving, you're on the improved way (G.INP) which has no constant latency added to the connection. Also, assuming I'm not mistaken again, I believe you're on 'retransmission low', which is good.

To put it in very basic terms, G.INP is kind of like fastpath but with the benefit of error correction when it's needed, whereas the traditional interleaving is error correction all the time which adds a constant latency and reduces the sync rate too.

[j0hn]

As pointed out by Ixel, you are on the best possible DLM profile....
Downstream 0-80Mb, Retransmission low.

There's no way to improve your latency. The DSLAM isn't adding any to normal traffic. We can see this here...

Bearer 0
INP:      48.00      0.00
INPRein:   0.00      0.00
delay:      0      0

Bearer 0 INPRein 0 shows retransmission is on low (best possible throughput) and delay is 0 (no added latency).

If you are suffering from poor latency it is either the laws of physics, i.e your location in the UK, or IDNet have poor peering/routing.

Do you have specific issues with latency or did you simply misread the stats as your line was interleaved?

The above is why ISP's don't add detailed stats to their modems. You've been hassling IDNet to fix something they have no control over, that doesn't even exist 

Have a read up on retransmission (G.INP/Retx) from Kitz page on the subject.

http://www.kitz.co.uk/adsl/retransmission.htm

As for uploading to MyDSLWebStats, have you tried via DslStats? You need to input your MyDSLWebStats username and validation key (Not password) into the relevant tab in DslStats and tick the upload box, job done.

[Zenfield]

@John - Im a total novice when it comes to interpreting stats on my line, so when i saw interleaving depth of 16 I automatically assumed i was being interleaved. My stats are finally up on MDWS, but i dont really know if i have anything too concerning to be worried about at the moment. The only thing that sticks out to me is the high CRC upstream errors i keep getting which is a bummer as thats the band I need to be rock solid as I play first person shooters alot online.

@Ixel - Thanks for your input fella, I really appreciate it.

[Westie]

Apparently upstream errors may be induced by internal telephone wiring, among other things.

When I connect the router to the master socket with a VDSL faceplate instead of connecting to the end-of-internal-line telephone socket, errors are greatly reduced.

See http://forum.kitz.co.uk/index.php/topic,21079.msg366318.html#msg366318, for example. Might be worth trying.

[j0hn]

Having looked at your posted stats above the upstream errors are nothing to worry about.
The upstream is running fastpath with FEC (the default setting) and so should have considerably more CRC/ES than the downstream which has retransmission.

You shouldn't be noticing any packet loss from the small amount of errors on the upstream.

At the time of posting you have uploaded 1 m minutes worth of data to MyDSLWebStats at 5:16am.
The Hlog/QLN plots are uploaded once an hour so they are unavailable to view.

From the snapshot of stats above your line looks great. Max sync up/down, retransmission low is on downstream low errors on the upstream.
You have nothing to worry about. No need to go poking at internal wiring.

[Zenfield]

@john thats great news. I think my stats have finally updated, but like you said i doubt i have anything to worry about.
My only curiosity is with the speeds that are attainable and the actual speeds Im getting at home. On average im only getting upto 76 down and 16 up?? Is this okay from looking at my stats?? Should i not be achieveing higher speeds? or is this all down to the distance and degradation of the line?

[j0hn]

76Mb down is about the best you'll get with PPP overheads. Nothing to do with distance. It's just the max throughput on this 80Mb product

16Mb up is 1-2Mb lower than you should get. That's usually because some kind of QoS is in effect on the router. Have a look and see if you have any QoS enabled.

[Zenfield]

@john cheers for your input fella, I think i left the QOS on hg612 turned on which ive now turned off and getting slightly better speeds through a wired speedtest.
Final question john, im currently looking at my graphs on MDWS, on the top left corner there seems to be an icon which resembles three traffic lights?? Is there a link you can provide me with as to what these represent, or possibly just give a brief explanantion if its not too much trouble. Currently I have 2 which are fully green where as the middle one has yellows in the bottom 2.

And as always thanks again for all your time

[roseway]

there seems to be an icon which resembles three traffic lights?...

It indicates the likelihood of DLM intervening on your connection. Hover the mouse pointer over the traffic lights to get the details.

[Zenfield]

@Roseway, I already tried hovering the mouse over them, yet I cant really make much sense of it tbh.

[Westie]

Have you tried left-clicking on the 'traffic lights'? That brings up another window giving a fuller explanation of the results for your line.
Remember, that your profile will be reflected by either the top, middle or bottom row of lights, not by looking at left, centre or right. I think yours is the top row. If they are all green you are OK. 

If left-clicking the lights doesn't work for you, go to HELP>Menu>Version 2 Summary and scroll down to "ENHANCED DLM GADGET" to get the same, or better, explanation, but not specific to your line.

[Zenfield]

If left-clicking the lights doesn't work for you, go to HELP>Menu>Version 2 Summary and scroll down to "ENHANCED DLM GADGET" to get the same, or better, explanation, but not specific to your line.

Cheers, ill take a look now to see if i can find the explanation