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:

Pages: 1 2 3 [4] 5 6 ... 10

Author Topic: Badly hit by crosstalk  (Read 17041 times)

niemand

  • Kitizen
  • ****
  • Posts: 1836
Re: Badly hit by crosstalk
« Reply #45 on: June 19, 2019, 10:50:50 PM »

FTTC and G.fast do not impact each other. Any FTTC DLM settings are not related.

The error correction on your upstream is appropriate and is an attempt to protect your service. I imagine further changes will be coming, too.

Since Link time = 7 hours 48 min 43 sec
FEC:            44529437                33723917
CRC:            21              658
ES:             15              480
SES:            0               377
Logged

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #46 on: June 19, 2019, 10:57:52 PM »

@CarIT

This is latest errors as of now:

Since Link time = 1 days 11 sec
FEC:            119270905               92923313
CRC:            63              1727
ES:             35              1145
SES:            0               886
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
« Last Edit: June 20, 2019, 03:18:18 AM by adslmax »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: Badly hit by crosstalk
« Reply #47 on: June 20, 2019, 07:44:56 AM »

886 SES in a day and half is very high.  Especially if that is whilst g.inp is also enabled.
Logged

tubaman

  • Senior Kitizen
  • ******
  • Posts: 12514
Re: Badly hit by crosstalk
« Reply #48 on: June 20, 2019, 08:34:40 AM »

886 SES in a day and half is very high.  Especially if that is whilst g.inp is also enabled.

Agree, that is a lot of SES.
My line runs at about 900 - 1000 ES each day on the DS side (with G.INP and 3dB) but only has five or six SES events in the same period.
I've only ever had G.INP on the US side for very short periods so I'm not sure how much of an advantage it would be for me. It would be interesting to see though.
 :)
Logged
BT FTTC 55/10 Huawei Cab - Zyxel VMG8924-B10A

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #49 on: June 20, 2019, 10:22:09 AM »

Oh well well. DLM taken action this morning after 5am. Guess what, silly to reduced upstream from 20000Kbps to 19000Kbps and decided to change interleave depth from 4 to 2 and INP from 55.00 to 56.00. Before the new trial on upstream kicked in the upstream error was clean as a spot with zero but the last 48 hours went very badly with too many SES in the last 48 hours.

Why would Openreach trial on upstream making it lots worsen? Are they trying to reduced upload speed for many of us? Not happy with this trial. Really rubbish. :(

Since Link time = 5 hours 21 min 21 sec
FEC:            25789818                5838599
CRC:            2               44
ES:             2               56
SES:            0               26
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0



[attachment deleted by admin]
« Last Edit: June 20, 2019, 10:30:40 AM by adslmax »
Logged

tubaman

  • Senior Kitizen
  • ******
  • Posts: 12514
Re: Badly hit by crosstalk
« Reply #50 on: June 20, 2019, 01:22:14 PM »

....
Why would Openreach trial on upstream making it lots worsen? Are they trying to reduced upload speed for many of us? Not happy with this trial. Really rubbish. :(
....

I very much doubt it's the trial making things worse for you - adding G.INP to the US side where necessary should help increase the available speed, not reduce it.
Clearly something is going on with the US side of your connection right now and DLM is doing its best to deal with that.  The fact that it now has G.INP in its tool set should be making things less bad than it would be without it.
 :)
Logged
BT FTTC 55/10 Huawei Cab - Zyxel VMG8924-B10A

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: Badly hit by crosstalk
« Reply #51 on: June 20, 2019, 06:41:18 PM »

If you had the historical data that clearly showed all those upstream errors started the moment G.INP was enabled on the upstream, that might suggest that these upstream errors are due to the upstream G.INP somehow not functioning properly.
Logged

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #52 on: June 20, 2019, 11:43:24 PM »

Off to bed now I expecting another DLM change on upstream overnight

Since Link time = 18 hours 33 min 29 sec
FEC:            64773398                17052392
CRC:            2               138
ES:             2               160
SES:            0               78
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Badly hit by crosstalk
« Reply #53 on: June 20, 2019, 11:45:37 PM »

Hmm . . . I don't like that SES count.  :-\
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #54 on: June 20, 2019, 11:47:52 PM »

 :o :-[

It's clearly something wrong with G.INP on upstream with high rtx-tc with interleaved depth at 2. SES - 80 now

[attachment deleted by admin]

[attachment deleted by admin]
« Last Edit: June 20, 2019, 11:53:36 PM by adslmax »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Badly hit by crosstalk
« Reply #55 on: June 20, 2019, 11:56:35 PM »

I can't see how the DLM activation of US G.Inp can be responsible for the climbing SES count.

I would be more inclined to accept that recent work in the cabinet has disturbed the tie-pairs for your circuit and it is now malfunctioning in a non-linear sense. Whatever the malfunction, it is probably manifesting itself at the low-frequency end of the band. 
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #56 on: June 20, 2019, 11:59:17 PM »

Was told by PN earlier today that my upstream are likely to be banded at 19Mbps by DLM.  :(
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Badly hit by crosstalk
« Reply #57 on: June 21, 2019, 12:10:49 AM »

That "oscillation" visible in the SNRM plot looks very much like that which sometimes appears on Kitz' circuit after a remote circuit re-train has been instigated. The solution is to close down the circuit from the CPE end.

If you've finished for the day, the simplest thing would be to power off your modem overnight. As I've described it in the past, give the line-card port some time to "relax".
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #58 on: June 21, 2019, 12:12:30 AM »

I can't do this - modem power down or my daughter will moaned at me she want to watch Netflix in bed.
Logged

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: Badly hit by crosstalk
« Reply #59 on: June 21, 2019, 07:53:22 AM »

The line has resync after 7:30am this morning but SNR are very bad -5dB on downstream. Never see anything like this on my line since FTTC first installed in 2014.

Stats recorded 21 Jun 2019 07:52:18

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039g1.d24m
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 18 min 5 sec
Resyncs:                   1 (since 21 Jun 2019 07:36:15)
         
            Downstream   Upstream
Line attenuation (dB):     11.8      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19000
SNR margin (dB):           -4.7      11.7
Power (dBm):               12.4      0.6
Interleave depth:          16      2
INP:                       46.00      56.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)   

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 28035 Kbps, Downstream rate = 44914 Kbps
Bearer: 0, Upstream rate = 19000 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):        -4.7             11.7
Attn(dB):        11.8            0.0
Pwr(dBm):        12.4            0.6   

Since Link time = 18 min 5 sec
FEC:            1308234         216063
CRC:            15               0
ES:             12               0
SES:            35               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
 >

Downstream      Upstream
General
   rtx_tx             9901884            40282           
   rtx_c              1552               10511504       
   rtx_uc             1                  1559889         
   LEFTRS             30                 20399           
   minEFTR            79982              18996           
   errFreeBits        1713887            638051878       
Bearer 0
   RxQueue            57                 130             
   TxQueue            19                 26             
   G.INP Framing      18                 18             
   G.INP Lookback     19                 26             
   RRC Bits           24                 24             
   Interleave depth   16                 2               
   INP                46.00              56.00           
   INPRein            1.00               1.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  1               
   INP                4.00               4.00           
   INPRein            4.00               4.00           
   Delay              3                  0   

     
« Last Edit: June 21, 2019, 07:59:11 AM by adslmax »
Logged
Pages: 1 2 3 [4] 5 6 ... 10
 

anything