Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: DLM In Action (US)  (Read 1479 times)

tiffy

  • Kitizen
  • ****
  • Posts: 1319
DLM In Action (US)
« on: February 05, 2019, 12:59:55 PM »

Some observations of DLM taking action (US G.Inp application) on BT 80/20 provision line which I remotely monitor 24/7 using a RPi & DSLStats, may be useful for reference as US G.Inp is not that common.

Line has always had DS G.Inp active (re-tx high) and synch's at close to max. DS & US, DS SNRM avg. 3.6 dB, US SNRM avg. 6.8 dB..
Has always run with US avg. 60 ES/Day & avg. 2.5 CRC's/Hr.
For whatever reason on 01/02, DS figures shot up to 5547 ES/Day & 798 CRC's/HR.

DLM intervened in the early hours of 02/02 and applied US G.Inp to the line, DS G.Inp remained acive as previous.

Code: [Select]
Stats recorded 05 Feb 2019 12:36:46

DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  3 days 10 hours 34 min 54 sec
Resyncs:                1 (since 01 Feb 2019 23:54:44)

Downstream Upstream
Line attenuation (dB):  17.3 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 74370 20000
SNR margin (dB):        3.6 6.8
Power (dBm):            12.3 7.1
Interleave depth:        8 8
INP:                    49.00 47.00
G.INP:                  Enabled Enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0409 0.1974
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 231

Current G.Inp status since DLM re-synch:

Code: [Select]
Downstream Upstream
General
rtx_tx          26893309        1946           
rtx_c            798942          1894           
rtx_uc          934455          0               
LEFTRS          1693            8               
minEFTR          74359            19997           
errFreeBits      4210143823      405618472       
Bearer 0
RxQueue          80              39             
TxQueue          20              13             
G.INP Framing    18              18             
G.INP Lookback  20              13             
RRC Bits        24              24             
Interleave depth 8                8               
INP              49.00            47.00           
INPRein          1.00            0.00           
Delay            0                0               
Bearer 1
Interleave depth 3                1               
INP              4.50            4.00           
INPRein          4.50            4.00           
Delay            3                0               

Not sure if the same criteria can be applied with respect to US Bearer 0 INPRein value (0 or 1) and it's indication of re-tx high/low state as per DS where this is known to be the case ?
Unfortunately, a DSLStats G.Inp status snapshot before DLM re-synch is not available.

With US G.Inp now applied, US ES's & CRC's have been zero ever since, G.Inp in action.

Will be interesting to see what DLM will make of this in the longer term and if US G.Inp will be removed again at some stage.

Logged
BT FTTP 150/30, BT Smart Hub 2

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: DLM In Action (US)
« Reply #1 on: February 16, 2019, 10:23:46 AM »

Update:

After 14 days running with US G.Inp applied and consequently zero US ES & CRC rates, in early hours today had a DLM re-synch and US G.Inp has been removed, DS G.Inp (re-tx high) remains active as previous.
To date, the US ES & CRC rates appears to have returned to the approx. pre disturbance levels of 01/02 as would be expected, US SNRM has decreased by approx. 1 dB.
Logged
BT FTTP 150/30, BT Smart Hub 2

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: DLM In Action (US)
« Reply #2 on: February 23, 2019, 01:59:54 PM »

Some further observations which some members may find useful on the other remote line I monitor with a RPi ZW & DSLStats (via VNC), Plusnet VDSL 40/10 provision on a Huawei cabinet , has always had DS G.Inp applied (re-tx low), just had US G.Inp applied this morning.

Current Stats:
Code: [Select]
Stats recorded 23 Feb 2019 13:28:34

DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:  AnnexA version - A2pvI042r.d26n
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  2 hours 51 min 3 sec
Resyncs:                1 (since 13 Feb 2019 23:38:32)

Downstream Upstream
Line attenuation (dB):  24.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 34999 8136
SNR margin (dB):        7.9 6.1
Power (dBm):            11.7 4.9
Interleave depth:        16 4
INP:                    48.00 46.00
G.INP:                  Enabled Enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0492 0.0006
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                6.08 40.0

Current G.Inp Data Summary:
Code: [Select]
Downstream Upstream
General
rtx_tx          15948            542             
rtx_c            8808            540             
rtx_uc          879              0               
LEFTRS          109              4               
minEFTR          35004            8138           
errFreeBits      692035264        1286731         
Bearer 0
RxQueue          21              14             
TxQueue          7                7               
G.INP Framing    18              18             
G.INP Lookback  7                7               
RRC Bits        24              24             
Interleave depth 16              4               
INP              48.00            46.00           
INPRein          0.00            0.00           
Delay            0                0               
Bearer 1
Interleave depth 1                1               
INP              2.50            4.00           
INPRein          2.50            4.00           
Delay            0                0               

Error History:
Code: [Select]
Average error rates for 23 Feb 2019

CRC erors per hour:  102 Down,  133 Up
FEC erors per hour:  28325 Down,  114 Up
HEC erors per hour:  0 Down,  0 Up
ES per hour:         5.16 Down,  128 Up
SES per hour:        2.06 Down,  0 Up
Total ES in the day: 70 Down, 1739 Up

Code: [Select]
Average error rates for 22 Feb 2019

CRC erors per hour:  73.2 Down,  209 Up
FEC erors per hour:  307002 Down,  154 Up
HEC erors per hour:  0 Down,  0 Up
ES per hour:         5.88 Down,  202 Up
SES per hour:        1.46 Down,  0 Up
Total ES in the day: 141 Down, 4842 Up

Code: [Select]
Average error rates for 21 Feb 2019

CRC erors per hour:  80.3 Down,  40.8 Up
FEC erors per hour:  671300 Down,  33.2 Up
HEC erors per hour:  0 Down,  0 Up
ES per hour:         6.08 Down,  40.0 Up
SES per hour:        1.54 Down,  0 Up
Total ES in the day: 146 Down, 959 Up

Code: [Select]
Average error rates for 20 Feb 2019

CRC erors per hour:  19.9 Down,  8.79 Up
FEC erors per hour:  122340 Down,  9.00 Up
HEC erors per hour:  0 Down,  0 Up
ES per hour:         4.42 Down,  8.25 Up
SES per hour:        0.04 Down,  0 Up
Total ES in the day: 106 Down, 198 Up

Application of US G.Inp is of course to expectation considering the steady increase of US ES's & CRC's over the last few days, I have monitored this line for over 18 months, back to the MDWS days but have never seen US G.Inp applied at any time, logic assumption being that DLM up to present has never perceived any requirement for intervention due to DS error rates.

If this line follows the form of my other remotely monitored line (different cabinet, same exchange) then US G.Inp will be removed again after approx. 14 days, difficult to know exactly what criteria is applied to that DLM decision as US error rate will be practically zero with US G.Inp applied.
Logged
BT FTTP 150/30, BT Smart Hub 2