Topic: Connection slightly higher than max attainable (Read 1126 times)

renluop · « **on:** November 05, 2020, 10:42:03 AM »

If this has been answered already apologies.
I Noticed this recently, because over the last months i physically have under par. Please what reason might there be for it?

If needed
xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 4878 Kbps, Downstream rate = 26374 Kbps
Bearer: 0, Upstream rate = 4878 Kbps, Downstream rate = 26257 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): 3.0 5.6
Attn(dB): 26.6 0.0
Pwr(dBm): 12.0 5.1

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 143
M: 1 1
T: 0 38
R: 14 8
S: 0.0000 0.9354
L: 7010 1300
D: 4 1
I: 242 76
N: 242 152
Q: 4 0
V: 0 0
RxQueue: 60 0
TxQueue: 12 0
G.INP Framing: 18 0
G.INP lookback: 12 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 43151
OHFErr: 0 193
RS: 1820642852 2645649
RSCorr: 2108216 738
RSUnCorr: 0 0
Bearer 1
OHF: 44924451 0
OHFErr: 1 0
RS: 269546335 0
RSCorr: 92 0
RSUnCorr: 1 0

Retransmit Counters
rtx_tx: 5466 0
rtx_c: 1430450 0
rtx_uc: 53099 0

G.INP Counters
LEFTRS: 2635 0
minEFTR: 26264 0
errFreeBits: 3144600594 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2077249811 0
Data Cells: 150426440 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: 27 737
SES: 26 0
UAS: 370 360
AS: 721805

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.92
OR: 0.01 28.69
AgR: 26315.05 4907.14

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: 158526/158526 16018/16027

Total time = 53 days 18 hours 46 min 0 sec
FEC: 1712779732 3813
CRC: 1341 847
ES: 27 737
SES: 26 0
UAS: 370 360
LOS: 1 0
LOF: 6 0
LOM: 0 0
Latest 15 minutes time = 60 sec
FEC: 69 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: 1340 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 = 18 hours 46 min 0 sec
FEC: 157601 21
CRC: 0 10
ES: 0 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 213833 28
CRC: 0 9
ES: 0 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 8 days 8 hours 30 min 3 sec
FEC: 2108216 738
CRC: 0 193
ES: 0 167
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

burakkucat · « **Reply #1 on:** November 05, 2020, 04:16:17 PM »

Quote from: renluop on November 05, 2020, 10:42:03 AM

If this has been answered already apologies.
I Noticed this recently, because over the last months i physically have under par. Please what reason might there be for it?

Hopefully, now, are feeling somewhat better.

Quote

. . .
Max: Upstream rate = 4878 Kbps, Downstream rate = 26374 Kbps
Bearer: 0, Upstream rate = 4878 Kbps, Downstream rate = 26257 Kbps
. . .

Looking at the above, I can only assume that you have misread those two lines.

The first line, beginning with "Max:", is a theoretical value calculated as if everything is perfect under the current conditions. It is just a guide and should not be taken as an absolute value.

The second line is a true representation of the current status of the circuit.

For the upstream rates, both of those two lines have the same value. For the downstream rates, the "Max:" is the greater of the two. Hence the current downstream rate is slightly lower than that of the theoretical maximum value.

Or have I misunderstood what is puzzling you? $:-\$

renluop · « **Reply #2 on:** November 06, 2020, 09:45:00 AM »

Here is part of Dslstats taken just now with max lower than connection.

.

Alex Atkin UK · « **Reply #3 on:** November 06, 2020, 11:09:59 AM »

Max being lower than sync simply means your line condition has deteriorated since you synced. This can happen immediately after syncing or over time, its perfectly normal.

Max/Attainable is based on the target SNRm, but as SNRm is merely a safety margin (its purpose is literally a buffer so your line quality can reduce without losing sync) you can drop below that target and thus end up a higher sync than you would otherwise have on the current line conditions. (for example, if you resynced)

burakkucat · « **Reply #4 on:** November 06, 2020, 03:46:17 PM »

It is a perfectly normal situation and can been seen on any xDSL circuit, if the statistics are regularly scrutinised.

In other words, don't worry . . . there is nothing wrong.

renluop · « **Reply #5 on:** November 06, 2020, 05:54:53 PM »

Alex Atkin UK Ah! Isee
burakkucat Not worried, just curious. Must be a familiar feeling , surely.

News:

Author Topic: Connection slightly higher than max attainable (Read 1126 times)

renluop

Connection slightly higher than max attainable

burakkucat

Re: Connection slightly higher than max attainable

renluop

Re: Connection slightly higher than max attainable

Alex Atkin UK

Re: Connection slightly higher than max attainable

burakkucat

Re: Connection slightly higher than max attainable

renluop

Re: Connection slightly higher than max attainable