General Discussion
  >> Fibre Broadband


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User soton30
(newbie) Sat 17-Oct-15 14:41:50
Print Post

FTTC - lots of upstream errors?


[link to this post]
 
Hi,

We upgraded from ADSL to FTTC at our business address a couple of months back and since then, Google sites in particular (Maps, GMail etc) have been very slow to load. I've tried messing around with MTU values on the Draytek router but it hasn't made a difference (currently set to 1492 MTU). All other websites appear to load just fine.

Our line is sync'd at 80/20 and speed tests show 74mb down / 13~mb up. It concerned me that we can't reach 17mb or whatever the max upload on a 20mb sync'd upload would be, so I unlocked the HG612 we have and retrieved some stats.

Any help is appreciated. It seems there's an awful lot of errors on the upstream compared to downstream, also are we G.INP enabled?

--------------


# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 37386 Kbps, Downstream rate = 97212 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): 10.8 23.4
Attn(dB): 13.2 0.0
Pwr(dBm): 12.5 4.2
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 2003394
OHFErr: 0 4
RS: 631927360 3373397
RSCorr: 2547 35
RSUnCorr: 0 0
Bearer 1
OHF: 10939828 0
OHFErr: 0 0
RS: 131277198 0
RSCorr: 1 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 3411 0
rtx_c: 1620 0
rtx_uc: 43899 0

G.INP Counters
LEFTRS: 19 0
minEFTR: 79982 0
errFreeBits: 4035157508 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1263950589 0
Data Cells: 330801698 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: 10 88
SES: 10 1
UAS: 111 101
AS: 175724

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: 49527/49527 8/8


-----


# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 37378 Kbps, Downstream rate = 97212 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): 10.8 23.4
Attn(dB): 13.2 0.0
Pwr(dBm): 12.5 4.2
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 2039678
OHFErr: 0 4
RS: 643004192 601714
RSCorr: 2547 35
RSUnCorr: 0 0
Bearer 1
OHF: 10948793 0
OHFErr: 0 0
RS: 131384778 0
RSCorr: 1 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 3411 0
rtx_c: 1620 0
rtx_uc: 43899 0

G.INP Counters
LEFTRS: 19 0
minEFTR: 79982 0
errFreeBits: 4035333222 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1286104317 0
Data Cells: 330929970 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: 10 88
SES: 10 1
UAS: 111 101
AS: 175868

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: 49602/49602 8/8

Total time = 1 days 3 hours 46 min 30 sec
FEC: 31777 2329
CRC: 535 238
ES: 10 88
SES: 10 1
UAS: 111 101
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 1 min 30 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: 22 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 = 3 hours 46 min 30 sec
FEC: 116 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1577 28
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 days 51 min 7 sec
FEC: 2547 35
CRC: 0 4
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0


----

WEB BASED MANAGEMENT

Path 0
Path 1
Downstream Upstream Downstream Upstream
Line rate (kbit/s) 79999 19999 0 0
CRC errors 139 127 18 0
FEC errors 0 0 14 0
HEC errors 186 4294967290 32 0
Standard User RobertoS
(elder) Sat 17-Oct-15 15:55:58
Print Post

Re: FTTC - lots of upstream errors?


[re: soton30] [link to this post]
 
Yes, G.INP is enabled and on.

I can't see any obvious reason why your upstream speed should be low. Are you speed testing wired or wirelessly? Can you be sure no other uploading was running concurrently?

There is something very strange about the error stats. In particular, firstly:-

ES: 10 88
SES: 10 1
UAS: 111 101


Unless those refer only to Bearer 1, not the total of Bearer 1 and Bearer 0. (Bearer 1 by the way is the G.INP control).

Secondly:-

FEC: 31777 2329
CRC: 535 238
ES: 10 88
SES: 10 1

The latter ones come from the error breakdown, in the --stats listing, but are not supported by the breakdown or those for the total up time at the end of the listing. I suspect a reporting error. The total FECs at the end equal the RSCorr in the body off the stats. Not surprisingly, as they are the same thing with a different label.

There are some experts on the HG612 reporting and misreporting, and no doubt one will be along some time.

Just as an aside for the future - there is no need to post both --show and --stats. They are identical as far as the Bitswap line. The difference is that the error breakdown and total uptime is given at the end of --stats.

In this case that breakdown appears to matter. In most cases it doesn't.

The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 59999/14372kbps @ 600m. - BQM
Standard User WWWombat
(knowledge is power) Sun 18-Oct-15 02:08:49
Print Post

Re: FTTC - lots of upstream errors?


[re: soton30] [link to this post]
 
Some of the error counters don't correlate perfectly, in the "total time" section, but the "since link" section looks fine.

The amount of errors is, overall, pretty low. Start worring if your ES rate jumps to 1,000 per day.

I guess your worry about the upstream errors actually stems from the GUI report - in particular the HEC figure?

I find it best to ignore the GUI, and just check the "--stats" CLI output. Some figures are translated from the command to the GUI in the wrong places.

For the HEC figure, that value actually looks to be a 32-bit two's-complement negative number (-6, if I calculated it correctly) accidentally printed as a 32-bit unsigned integer. Poor interpretation like this often leads to infeasibly huge numbers.

HEC counts don't apply to our FTTC implementation anyway, so it is safe to ignore.

On balance, there's nothing to see here. Everything is working fine, and your issue with Google sites is caused by something else.

I have a vague recollection of something on Chrome giving me problems, which was an experimental feature that was only actually exploited by Google themselves - so made their websites slow. That needed to be turned off ... but I don't remember what it was frown

Otherwise, suspect DNS.


Register (or login) on our website and you will not see this ad.

  Print Thread

Jump to