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 ... 5

Author Topic: Same old upstream story for line 3  (Read 11569 times)

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Same old upstream story for line 3
« on: July 25, 2019, 06:59:51 PM »

I’m still getting the same annoying line 3 upstream variation with 24-hour period. See pic, upstream is in green, the square wave:



The target upstream is (supposedly) set at 9dB target SNRM. Now the intention was that the upstream was supposed to drop later following retrain or boot and drop from 9dB to 5dB, not from 6dB to 2dB. Yet for some reason the modem started at 6dB after it was booted or a retrain otherwise triggered, and then later the SNRM dropped right down from that 6dB to ~2dB. So in fact now surprisingly during part of the day the green upstream is actually below the red downstream which is around 3dB where it should be.

This has happened before a good few times. The odd thing is that as far as I can tell I now seem to be getting away with running at 2dB upstream whereas before when this happened, I am pretty certain, I was getting a serious error rate on the upstream that was very detrimental to performance. Iirc I reduced the upstream sync speed and the measured throughput got a lot better.


xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 250 Kbps, Downstream rate = 3040 Kbps
Bearer:   0, Upstream rate = 412 Kbps, Downstream rate = 2788 Kbps

Link Power State:   L0
Mode:         ADSL2 Annex A
TPS-TC:         ATM Mode(0x0)
Trellis:      U:ON /D:ON
Line Status:      No Defect
Training Status:   Showtime
      Down      Up
SNR (dB):    2.9       2.7
Attn(dB):    65.5       41.4
Pwr(dBm):    18.1       12.4

         ADSL2 framing
         Bearer 0
MSGc:      51      12
B:      32      5
M:      4      16
T:      3      8
R:      10      16
S:      1.4889      7.2846
L:      763      123
D:      2      4

         Counters
         Bearer 0
SF:      14915350      255571
SFErr:      895      9
RS:      637631222      2399862
RSCorr:      36862      265027
RSUnCorr:   7046      0

ReXmt:      59688      0
ReXmtCorr:   54418      0
ReXmtUnCorr:   7309      0

         Bearer 0
HEC:      5529      8
OCD:      196      0
LCD:      196      0
Total Cells:   1572009115      232784059
Data Cells:   43202508      7628938
Drop Cells:   0
Bit Errors:   156506      1014

ES:      401      9
SES:      0      0
UAS:      57      57
AS:      239070

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      7
PER:      15.91      16.39
OR:      28.65      8.78
AgR:      2804.62   420.07

Bitswap:   41695/41697      3455/3455

Total time = 2 days 18 hours 25 min 27 sec
FEC:      36862      265027
CRC:      895      9
ES:      401      9
SES:      0      0
UAS:      57      57
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 10 min 27 sec
FEC:      31      1057
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:      63      1281
CRC:      2      0
ES:      2      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 18 hours 25 min 27 sec
FEC:      2190      57435
CRC:      5      2
ES:      5      2
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      26280      126705
CRC:      867      5
ES:      385      5
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 2 days 18 hours 24 min 29 sec
FEC:      36862      265027
CRC:      895      9
ES:      401      9
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0


The upstream errors don’t look too bad at all? What do you think.

Mind you I’m thinking that the downstream is iffy - it’s ok now but had a really bad period in the past which it could not cope with. Does that sound right?
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #1 on: September 19, 2019, 01:56:43 AM »

After an absence for a while, as I mentioned in another thread, the line 3 upstream square wave thing is back again.

Here are the line 3 stats, with target upstream SNRM set to 9dB. This snapshot is taken in the SNRM-high part of the daily cycle. By this I mean that later on, within less than 24 hours, the upstream SNRM should drop sharply in this case, by about 4dB, then so many hours later it should jump back up.

— Line 3 —
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 321 Kbps, Downstream rate = 3088 Kbps
Bearer:   0, Upstream rate = 389 Kbps, Downstream rate = 2807 Kbps

Link Power State:   L0
Mode:         ADSL2 Annex A
TPS-TC:         ATM Mode(0x0)
Trellis:      U:ON /D:ON
Line Status:      No Defect
Training Status:   Showtime
      Down      Up
SNR (dB):    3.1       9.1
Attn(dB):    65.0       41.1
Pwr(dBm):    17.9       12.4

         ADSL2 framing
         Bearer 0
MSGc:      52      11
B:      32      5
M:      4      16
T:      3      8
R:      10      16
S:      1.4792      7.7241
L:      768      116
D:      2      4

         Counters
         Bearer 0
SF:      37522      36999
SFErr:      0      0
RS:      1632222      313907
RSCorr:      9      0
RSUnCorr:   0      0

ReXmt:      2      0
ReXmtCorr:   1      0
ReXmtUnCorr:   0      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   4024079      555792
Data Cells:   58564      10216
Drop Cells:   0
Bit Errors:   0      0

ES:      26358      99
SES:      4891      0
UAS:      10777      8052
AS:      608

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      8
PER:      16.08      16.41
OR:      28.84      8.28
AgR:      2823.00   396.16

Bitswap:   192/192      8/8

Total time = 36 days 2 hours 46 min 7 sec
FEC:      263198      166305
CRC:      127201      61
ES:      26358      99
SES:      4891      0
UAS:      10777      8052
LOS:      612      0
LOF:      589      0
LOM:      1330      0
Latest 15 minutes time = 1 min 7 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:      71      0
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      55      55
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 2 hours 46 min 7 sec
FEC:      1865      2
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      55      55
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      7686      74201
CRC:      961      3
ES:      41      3
SES:      29      0
UAS:      173      162
LOS:      1      0
LOF:      9      0
LOM:      0      0
Since Link time = 10 min 7 sec
FEC:      9      0
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0


Need to compare this with the values in the u/s-SNRM-low part of the cycle, as a recheck.
« Last Edit: September 20, 2019, 01:57:59 AM by Weaver »
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #2 on: September 20, 2019, 01:55:10 AM »

Unfortunately this is the high part of the cycle again, so disregard but it might be interesting for comparison. Snapshot taken just after forcing a retrain, so the attn value shown should be current.

Will need to try to remember later on and get a snapshot at the right time

Line 3 2019-09-20T00:50:00 ; again high part of cycle? —
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 325 Kbps, Downstream rate = 3120 Kbps
Bearer:   0, Upstream rate = 389 Kbps, Downstream rate = 2774 Kbps

Link Power State:   L0
Mode:         ADSL2 Annex A
TPS-TC:         ATM Mode(0x0)
Trellis:      U:ON /D:ON
Line Status:      No Defect
Training Status:   Showtime
      Down      Up
SNR (dB):    3.2       9.0
Attn(dB):    65.0       41.1
Pwr(dBm):    17.8       12.4

         ADSL2 framing
         Bearer 0
MSGc:      53      11
B:      31      5
M:      4      16
T:      3      8
R:      12      16
S:      1.4508      7.7241
L:      772      116
D:      2      4

         Counters
         Bearer 0
SF:      0      549
SFErr:      0      0
RS:      0      4658
RSCorr:      0      0
RSUnCorr:   0      0

ReXmt:      0      0
ReXmtCorr:   0      0
ReXmtUnCorr:   0      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   0      5651
Data Cells:   0      12
Drop Cells:   0
Bit Errors:   0      0

ES:      26377      100
SES:      4900      0
UAS:      10978      8253
AS:      9

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      8
PER:      16.04      16.41
OR:      29.40      8.28
AgR:      2790.35   396.16

Bitswap:   4/4      0/0

Total time = 37 days 3 hours 2 min 51 sec
FEC:      277951      168296
CRC:      127655      62
ES:      26377      100
SES:      4900      0
UAS:      10978      8253
LOS:      613      0
LOF:      597      0
LOM:      1330      0
Latest 15 minutes time = 2 min 51 sec
FEC:      23      0
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      59      59
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      249      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 2 min 51 sec
FEC:      3492      0
CRC:      1      0
ES:      1      0
SES:      0      0
UAS:      59      59
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      13126      1993
CRC:      453      1
ES:      18      1
SES:      9      0
UAS:      197      197
LOS:      1      0
LOF:      8      0
LOM:      0      0
Since Link time = 9 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
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
« Last Edit: September 20, 2019, 01:59:48 AM by Weaver »
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #3 on: September 21, 2019, 09:57:57 PM »

This might or might not represent the low part of the cycle; there was a retrain early in the morning and I forced a retrain just before capturing this snapshot in order to make sure the reported attenuation figures would be up to date.
Line 3: 2019-09-21:






Snapshot of stats after retrain:

xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 276 Kbps, Downstream rate = 3052 Kbps
Bearer:   0, Upstream rate = 352 Kbps, Downstream rate = 2748 Kbps

Link Power State:   L0
Mode:         ADSL2 Annex A
TPS-TC:         ATM Mode(0x0)
Trellis:      U:ON /D:ON
Line Status:      No Defect
Training Status:   Showtime
      Down      Up
SNR (dB):    3.3       6.0
Attn(dB):    65.0       41.2
Pwr(dBm):    17.7       12.4

         ADSL2 framing
         Bearer 0
MSGc:      52      11
B:      31      4
M:      4      16
T:      3      9
R:      10      16
S:      1.4642      7.1111
L:      754      108
D:      2      4

         Counters
         Bearer 0
SF:      20764      19593
SFErr:      0      0
RS:      903248      187192
RSCorr:      41      2
RSUnCorr:   0      0

ReXmt:      2      0
ReXmtCorr:   2      0
ReXmtUnCorr:   0      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   2158686      273397
Data Cells:   3687      8136
Drop Cells:   0
Bit Errors:   0      0

ES:      26388      101
SES:      4910      0
UAS:      11103      8368
AS:      334

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      7
PER:      15.92      17.00
OR:      29.14      8.00
AgR:      2764.79   358.59

Bitswap:   147/147      8/8

Total time = 38 days 23 hours 12 min 59 sec
FEC:      311878      171800
CRC:      128120      64
ES:      26388      101
SES:      4910      0
UAS:      11103      8368
LOS:      614      0
LOF:      606      0
LOM:      1330      0
Latest 15 minutes time = 12 min 59 sec
FEC:      258      12
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      65      65
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      718      9
CRC:      1      0
ES:      1      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 23 hours 12 min 59 sec
FEC:      21461      1168
CRC:      465      0
ES:      11      0
SES:      10      0
UAS:      125      115
LOS:      1      0
LOF:      9      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      15958      2336
CRC:      1      2
ES:      1      1
SES:      0      0
UAS:      59      59
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 5 min 33 sec
FEC:      41      2
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
« Last Edit: September 22, 2019, 04:00:57 PM by burakkucat »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Same old upstream story for line 3
« Reply #4 on: September 21, 2019, 10:20:43 PM »

The US attenuation does not seem to have changed . . . 41.2 dB looks familiar.
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.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #5 on: September 22, 2019, 06:54:07 AM »

The time of day would suggest that is yet another high-part-of-cycle snapshot. I will try again later after I have clearly seen it drop.

So I took another look
And
hello, no cycle in the last 24 hours up to the present now! Things have become irregular!

In the following picture, the glitch in the centre was the forced retrain last night when I took the previous stats snapshot. The present time as usual is on the right. Sunday morning, the present, is the last sample.

« Last Edit: September 22, 2019, 07:18:04 AM by Weaver »
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #6 on: October 13, 2019, 01:44:06 AM »

In another thread I said the line 3 upstream diurnal cycle thing was fixed by the post lightning strike repairs. I jinxed it by speaking too soon. It’s back, and in a slightly worse form if anything; the latest jump upwards is about 5dB.



The exceptionally high values seen in the graph are no bad thing at all though. It just seems that the above picture shows an exceptionally good, very quiet period. The upstream sync speeds associated with these SNRM values are much much better, at around 500kbps for 6dB, compared with the sync rates that I was having to put up with before - of around 400k, or ~350k or even worse.
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #7 on: October 14, 2019, 02:23:32 AM »

Latest line 3 capture, very high upstream SNRM (in green) step, 6dB high, all the way down to a ridiculously low SNRM of 0.5 dB, which is worrying; however despite the low value the error count in the stats seems to be fine, so it seems that I am managing to get away with it, and it must just be a quiet line or one with a type of noise that the interleave and FEC can handle well.



I don’t know why this isn’t obeying the configured target upstream SNRM which is supposed to be 9dB. I perhaps need to get a forced retrain that is initiated externally and not from a command entered at the modem CLI, which is what I had done here earlier. I don’t know where it is getting the high step value of 6dB from, unless it’s just some fixed default. I don’t know how the clueless target SNRM is supposed to get enforced either.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Same old upstream story for line 3
« Reply #8 on: October 14, 2019, 03:48:54 PM »

So it seems that the weirdness has became even weirder. I am unable to rationalise what is taking place. (Even with some rather fantastic flights of fancy.)
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.

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33879
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Same old upstream story for line 3
« Reply #9 on: October 14, 2019, 10:55:04 PM »

 :hmm: ???

I take it there is nothing corresponding on the other lines at the same time..  either upwards or downwards?
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: Same old upstream story for line 3
« Reply #10 on: October 14, 2019, 11:35:47 PM »

the very sudden movement up and down is the type of pattern seen when a piece of equipment is turned on and off.  So a device somewhere is causing that probably.
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #11 on: October 15, 2019, 12:16:41 AM »

@kitz

The other lines :
line 1 - no pattern at all
Line 2 - irregular pattern, smaller height
Line 4 - no pattern.

Today, line 3 retrained on its own for some reason and was in the low SNRM state; it then went up to 9dB following its target set by me. But 9dB was the new ‘low’ so after so many hours it went up to 14dB and is ridiculously slow at 240kbps, about half of what it should be. That’s the problem with a variation this large, the sync speeds are usually way wrong.
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #12 on: October 15, 2019, 08:00:50 AM »

Picture for crazy line 3, now super slow u/s. The link dropped for whatever reason while in the ‘low’ state, as I mentioned before and that’s why it is now so ridiculously slow. And the 9dB target was my own idea.

Line 3:



I don’t suppose there’s any chance of identifying the source, is there? But how could it be only this one line?
« Last Edit: October 15, 2019, 08:08:03 AM by Weaver »
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Same old upstream story for line 3
« Reply #13 on: October 17, 2019, 11:57:17 PM »

Link 3 continues as useable, look how enormous the drop is, and the low value is rather worryingly low. The 9dB target is not helping me:





Line 1 is back to normal :

Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Same old upstream story for line 3
« Reply #14 on: October 18, 2019, 12:31:54 AM »

I think you might need to consult with the A&A wizards, to check if they can see anything untoward happening when monitored from their end of the circuit. I wouldn't expect anything to be seen but it would be worthwhile checking.
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.
Pages: [1] 2 3 ... 5
 

anything