Print

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

[boost]

The G.INP stats don't seem quite as intuitive as the old stuff?

I'd really appreciate any input on the following stats, possible

Are the ES values still applicable?
Is INP REIN 2.0 normal?
What on earth is rtx_tx and _c?

Code: [Select]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 32222 Kbps, Downstream rate = 89180 Kbps
Bearer: 0, Upstream rate = 9999 Kbps, Downstream rate = 55000 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): 16.1 22.2
Attn(dB): 12.6 0.0
Pwr(dBm): 13.3 -2.4
VDSL2 framing
Bearer 0
MSGc: -6 58
B: 117 236
M: 1 1
T: 0 23
R: 8 16
S: 0.0683 0.7543
L: 14763 2694
D: 16 1
I: 126 127
N: 126 254
Q: 16 0
V: 1 0
RxQueue: 45 0
TxQueue: 15 0
G.INP Framing: 18 0
G.INP lookback: 15 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 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 897191
OHFErr: 0 364
RS: 4212466608 3258711
RSCorr: 1366 397
RSUnCorr: 0 0
Bearer 1
OHF: 18240498 0
OHFErr: 0 0
RS: 145923486 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 7790 0
rtx_c: 490 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 2 0
minEFTR: 54992 0
errFreeBits: 245782390 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 924268774 0
Data Cells: 201750685 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 347
SES: 0 0
UAS: 26 26
AS: 292994

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.70
OR: 0.01 58.79
AgR: 55087.48 10057.90

Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01

Bitswap: 117864/117864 9/9

Total time = 1 days 9 hours 23 min 40 sec
FEC: 1366 397
CRC: 0 364
ES: 0 347
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 40 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 2
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 9 hours 23 min 40 sec
FEC: 61 38
CRC: 0 31
ES: 0 29
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 417 132
CRC: 0 113
ES: 0 107
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 days 9 hours 23 min 13 sec
FEC: 1366 397
CRC: 0 364
ES: 0 347
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#


Should also be on MDW if that's easier

Thanks!

[cliver]

Like you I'm still getting my head around them. What I know so far is...
rtx_tx = retransmitted total
rtx_c = retransmitted and corrected
rtx_uc = retransmitted uncorrected

So the rtx_uc is the important one as that translates into an error and I believe will show as an ES in the "normal stats".
That's about my limit in afraid except your stats look similar to mine and I think are OK.
Perhaps someone with more knowledge can confirm my information and fill in the gaps?

Sent from my Nexus 6P using Tapatalk

[kitz]

See ~ G.INP Retransmission Parameters & Counters

LEFTR & SEFTRs may be the ones that DLM takes notice of.

Translated very loosely because G.INP works differently
rtx_uc can/will trigger a CRC
LEFTR is like an Err/Sec
SEFTR is like severely errored seconds.

[boost]

Brill, thanks both