Yes you were right.

My connection went down over 20 minutes ago. For some reason I was disconnected, Don�t know if it was because of telnet but it would not re connect, even when renew ip address. So here they are. Back on the other modem for now.


# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 13587 Kbps, Downstream rate = 49860 Kbps
Path: 0, Upstream rate = 11999 Kbps, Downstream rate = 49681 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): 6.1 7.2
Attn(dB): 0.0 0.0
Pwr(dBm): 12.0 6.9
VDSL2 framing
Path 0
B: 239 118
M: 1 2
T: 64 58
R: 0 16
S: 0.1537 0.6293
L: 12489 3229
D: 1 1
I: 240 127
N: 240 254
Counters
Path 0
OHF: 2260492 612100
OHFErr: 60 3
RS: 0 1125968
RSCorr: 0 84
RSUnCorr: 0 0

Path 0
HEC: 234 0
OCD: 0 0
LCD: 0 0
Total Cells: 532125864 0
Data Cells: 200983 0
Drop Cells: 0
Bit Errors: 0 0

ES: 45 3
SES: 0 0
UAS: 3136 3136
AS: 5583

Path 0
INP: 0.00 0.00
PER: 2.45 9.12
delay: 0.00 0.00
OR: 81.30 56.11

Bitswap: 0 2775

Total time = 2 hours 57 min 17 sec
FEC: 0 0
CRC: 60 0
ES: 45 3
SES: 0 0
UAS: 3136 3136
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 12 min 17 sec
FEC: 0 0
CRC: 7 0
ES: 5 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 15 0
ES: 8 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 2 hours 57 min 17 sec
FEC: 0 0
CRC: 60 0
ES: 45 3
SES: 0 0
UAS: 3136 3136
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 = 1 hours 33 min 3 sec
FEC: 0 84
CRC: 60 3
ES: 45 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

Edited by deleted (Wed 19-Dec-12 18:57:20)

they not useless just remember FEC and CRC are backwards.

From personal experience on adsl (and so far on vdsl) normal errored seconds can be ignored, its severely errored seconds that are enough to impact the connection.

On my own sync uptime which is now around 6 days (since I unlocked modem). I have had 3 bursts of crc errors on seperate occasions which causes severely errored seconds, all 3 didnt register on my TBB graph. Outside of those 3 occasions I have a trickle of crc errors averaging around 3-10 per 15 minutes.

If CRC is very close to the ES count and SES is 0 then I would say nothing at all to worry about on line errors.

Here is my previous 24h.

Previous 1 day time = 24 hours 0 sec
FEC: 0 0
CRC: 611 0
ES: 283 46
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

so no severely errored seconds, and the errored seconds I have had average 3 CRC per errored second. As a comparison on a lower bitrate adsl connection some years ago I used to average 30k or so crc errors a day on fast path.

since the sync uptime which includes the 3 bursts of CRC that caused severely errored seconds.

Since Link time = 6 days 3 hours 8 min 5 sec
FEC: 0 3017
CRC: 12116 247
ES: 1858 218
SES: 16 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

This hasnt been enough to trigger DLM and if it wasnt for these modem stats I would have been unaware of errors as my line has seemed fine whenever I have used it. No speed loss, packet loss etc.

you now have mine to compare to.

Errors are minimal!

Sorry, I've been busy the last day, and I start moving around the country a lot for the next 2-3 weeks, so I won't be on here much.

I can comment on the stats, but they've not been running too long...

In reply to a post by superspeed:

My connection went down over 20 minutes ago. For some reason I was disconnected, Don�t know if it was because of telnet but it would not re connect, even when renew ip address. So here they are. Back on the other modem for now.

Yes, I can see from the set of statistics. The first batch (usually the accumulated set for the whole time that the modem has been turned on) show a high UAS (unavailable seconds), compared with the final set (the accumulated set since the last sync).

In the first batch, you normally see UAS jump in small batches (say 20) each time a resync occurs.

B: 239 118
M: 1 2
T: 64 58
R: 0 16
S: 0.1537 0.6293
L: 12489 3229
D: 1 1
I: 240 127
N: 240 254

Path 0
INP: 0.00 0.00
PER: 2.45 9.12
delay: 0.00 0.00
OR: 81.30 56.11

So there is no interleaving required on either upstream or downstream (INP and delay both zero).

Downstream doesn't have FEC running (R=0) either, so there's no protection. Upstream is using R=16, which suggests there's some parity in use for protection - and explains why the upstream speed doesn't quite reach the full attainable figure (16/254 is 6%). However, it isn't being used for real noise protection (otherwise INP and delay would also be non-zero).

This is backed up by:

RSCorr: 0 84
RSUnCorr: 0 0

Total time = 2 hours 57 min 17 sec
FEC: 0 0
CRC: 60 0
ES: 45 3
SES: 0 0
UAS: 3136 3136
LOS: 0 0
LOF: 0 0

From this batch, I'd certainly wonder why UAS ended up so high. That's 50 minutes it stayed disconnected.

Since Link time = 1 hours 33 min 3 sec
FEC: 0 84
CRC: 60 3
ES: 45 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

It certainly looks very clean to me. As someone (sorry) said earlier, the SES indicates serious stuff, and is an indicator of a bigger problem, so zero is good.

A zero SES and an ES:CRC ratio close to 1:1 show errors are spread over time, suggesting no individual bursts of interference.

Ideal really, except:

Max: Upstream rate = 13587 Kbps, Downstream rate = 49860 Kbps
Path: 0, Upstream rate = 11999 Kbps, Downstream rate = 49681 Kbps

[alongside SNR values of 6dB and 7dB respectively]

The distance just limits what speed can be attained. You could give more detail with the "xdslcmd info --pbParams" command, but I probably won't get to see that.

But it certainly appears to be *just* distance, and not interference of any sort.

BTW: Upstream sync of 12Mbps is equivalent to an 11.6Mbps IP profile. Upload speeds (on a tester) probably ought to top out at 9.8Mbps.

You can probably gain 10% of upstream throughput (for the same upstream sync speed) by turning off QoS - which you can now do in the unlocked modem.

In reply to a post by Chrysalis:

they not useless just remember FEC and CRC are backwards.

I know I *ought* to be able to transpose the figures in the GUI, but I can never seem to remember at the time

If CRC is very close to the ES count and SES is 0 then I would say nothing at all to worry about on line errors.

Agreed, so long as the number doesn't increase at too fast a rate. We just don't know where the threshold is (yet).

As a comparison on a lower bitrate adsl connection some years ago I used to average 30k or so crc errors a day on fast path.

My old line could sustain 8Mbps (ADSL1) at 10 CRC errors per hour without interleaving. When running ADSL2+ it gets to 14Mbps with interleaving, but the FEC mount up at an astonishing rate. Millions.

Since Link time = 6 days 3 hours 8 min 5 sec
FEC: 0 3017
CRC: 12116 247
ES: 1858 218
SES: 16 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

This hasnt been enough to trigger DLM and if it wasnt for these modem stats I would have been unaware of errors as my line has seemed fine whenever I have used it. No speed loss, packet loss etc.

It's good to see those numbers, as it gives us a feel for what DLM will let through unhindered. I hope I remember those numbers after Christmas...

Thanks for the reply and detailed analysis. Much of that was a bit above my head.

I am not likely going to be able to use the modem much more than a few hours as i'm having problems with it. Posted a bit about it here. http://forums.thinkbroadband.com/dslrouter/t/4191131...

I will try again another time but will leave it until the weekend.

I was thinking how would I approach PN with this if my speeds or other issues were a problem, using them stats? Would they even do something to sort it based on them stats?

Well have to see how it goes.

Thanks. You have more errors than mine but then you were connected for 6 days.

yeah your error rate is much better than mine, here is after another day with no new crc burst.

Previous 1 day time = 24 hours 0 sec
FEC: 0 0
CRC: 1234 0
ES: 309 30
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 7 days 1 hours 29 min 17 sec
FEC: 0 3309
CRC: 13324 273
ES: 2159 244
SES: 16 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

my normal error rate has increased somewhat, earlier days I was averaging 300 a day.

but this gives an idea how ow it really is.

Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 4 0
ES: 4 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0

in 15 minutes which is 900 seconds, only 4 seconds had an error. 309 errored seconds in a day that has 86400 seconds I am averaging now 4:1 ratio on crc to errored seconds, and all seems fine. I think the crc error rate has to be quite high in bursts to be noticeable, I suspect the 16 SES I have had if I was using it during those 16 seconds I would have noticed something but I wasnt.

As this post was deleted unnecessarily and because of some bad adverts on a link I posted am reposting it. No link for now. I hope it was not PN that complained to get this removed. It was a fair review. I won't hesitate to post this review on another website if that was the case. Thankfully I have a copy in word as I typed it on there. Sorry for any bad spelling. You should be able to understand it.

Well after a hard decision, I decided to join plusnet. I really didn�t want to put up with BT�s useless Indian call centres and their vague terms and conditions. Now this has much praise but also has some criticism and thinks PN could improve in some places. You have to take the rough with the smooth, so no PN fan boys please.

Sign Up. Sign up was easy enough but the ordering a BT engineer system should be scrapped. I selected the 13th and it was an afternoon appointment. That was the earliest I could select. I was concerned about the number of people saying how, BT opeanreach failed to turn up. That worried me a bit as I hoped that it would not happen to me. So I called plusnet up about midweek and asked them to confirm the appointment I made on the 13th. Was told that the appointment was booked for the 14th. I did ask why I was not told and was explained that the appointments are not guaranteed. It takes 24Hours to go through and no guarantee. I said it was totally pointless ask customers to select a date if this is the case and should be down to the isp anyway. The adviser agreed.

Anyway the next day I received a call from matt PN to confirm date, which I thought was good of him. Wasn�t expecting it. We had a chat about the installation dates BT wires and some other things. It was a nice friendly chat.

The day. Well the day for my installation came and thankfully the BT openreach bloke turned up. It all went on time and smoothly. I was chatting with the engineer about speeds and profiles, he informed me that his paperwork and equipment said I was on 20/40. I said that�s not right but just said, that�s what he has on his job sheet.

After install. It took a few hours but I did have some trouble connecting. I was told to put the standard phone cable in the modem. I thought that was wrong. Anyway called plusnet and the first adviser was not much help. He did not seem to know what to do. It was suggested to reset the router. I did and connected the red cable. After a bit of time it worked. I called back about the 20/40 profile thing at it was confirmed, that I was on the wrong profile fibre service. Was told that someone had mess my order up and I was on fibre value what is 20/40, not extra as I ordered. I don�t know how they did that. As It was the end of the week, I was told it won�t be until Monday I was regraded to 20/80 and extra fibre. No wonder I had slow speeds and my speed test confirmed I was on 20/40 as well. I did some P2P tests before and after. Will post on the other thread about it.

Anyway On Monday morning a member of plusnet phoned me, to confirm that I am now on 20/80 extra fibre. I thought that was nice of PN to do that. Something I was not expecting.

I will post about some other things in separate posts and questions later. Other than that wrong order mess up I think I am quite happy and went well overall.

Thanks to matt and the other PN member, for calling me about the related issues, things. J

I did this.

*20/40 was ment to be 40/10 and 20/80 was ment to be 80/20, as discussed.

Edited by deleted (Tue 25-Dec-12 11:38:38)