Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: banger on December 10, 2019, 01:53:00 AM

Title: So What Has Happened Here Then?
Post by: banger on December 10, 2019, 01:53:00 AM
Strange happenings at 1am on TT Biz line. Service status says Software Update multiple locations and the timeframe seems about right but my DSL has come back up with a 1.6db margin and higher sync of 72. I would have thought a re-sync would have brought back 3db margin and sync of around 68. Any ideas it has been in sync for 248 days, same time as modem uptime. See attached.

Quote
Stats recorded 10 Dec 2019 02:36:16

DSLAM type / SW version:   BDCM:0xa4a1 (164.161) / v0xa4a1
Modem/router firmware:     AnnexA version - A2pv6F039v.d26a
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     1 hour 43 min 28 sec
Resyncs:                   1 (since 09 Dec 2019 10:22:13)
         
            Downstream   Upstream
Line attenuation (dB):     19.7      0.0
Signal attenuation (dB):   Not monitored      
Connection speed (kbps):   72527      17566
SNR margin (dB):           1.6      4.3
Power (dBm):               12.6      7.6
Interleave depth:          8      1
INP:                       50.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.5224      0.0022
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   4.86      1.22

Also think my line card firmware has been updated.
Title: Re: So What Has Happened Here Then?
Post by: Ronski on December 10, 2019, 06:15:09 AM
If you're attainable speed is lower than your sync speed it's just reconnected quicker than other modems, nothing unusual. It'll sort itself out next resync.
Title: Re: So What Has Happened Here Then?
Post by: banger on December 10, 2019, 06:33:05 AM
If you're attainable speed is lower than your sync speed it's just reconnected quicker than other modems, nothing unusual. It'll sort itself out next resync.

Cheers Ronski, yes the attainable is 67 so next resync it will probably go back down. Shame.  :P
Title: Re: So What Has Happened Here Then?
Post by: Ronski on December 10, 2019, 10:13:29 AM
It may well stay like it for some time, enjoy it while it lasts.
Title: Re: So What Has Happened Here Then?
Post by: tiffy on December 10, 2019, 02:19:06 PM
Yes, something widespread happened in early hours of this morning, the 3 lines I monitor, RPi's/DSLStats, same exchange, different locations, all had a re-synch at 01:35 this morning.
2 Plusnet 40/10 lines and a BT 80/20 line.

The BT 80/20 line which has always been close to max. US & DS synch. speeds has re-synched at US/DS max.
DS SNRM has changed from 3.2 to 1.4 dB.
US SNRM has changed from 6.0 to 5.2 dB.

The two Plusnet 40/10 (much longer) lines have both increased US synch. speeds slightly, DS synch. speeds have remained the same.
US SNRM has decreased by 2 db. on the 40 kbps synched line and 1 dB. on the 35 kbps synched line.
DS SNRM has decreased marginally on both lines.
Title: Re: So What Has Happened Here Then?
Post by: tiffy on December 10, 2019, 04:20:17 PM
Post DLM re-synch this morning I have had a more detailed look at my stats, Plusnet 40/10 VDSL-2 service on a relatively long line.
My US synch and data speeds are the highest I have ever recorded since the free 2 to 10 upgrade by Plusnet, reflective of the the 2 dB. decrease in US SNRM.

My DS synch speed was already topped out at 40 mbps prior to the DLM re-synch so no room for improvement there.

As an aside, has anyone noticed that the BTw Performance Tester no longer offers the "Further Diagnostics" option, my last test was late November and it was offered then ?
Was still able to obtain my BRAS profiles using "Mouselike.org" with phone number, they had not changed.

I know the BTw Performance Tester is not very well respected on the forum, however, for consistancy I use this with Pale Moon browser accepting that there are issues associated with Firefox (my normal browser) and the BTw tester.   
Title: Re: So What Has Happened Here Then?
Post by: adslmax on December 11, 2019, 01:21:34 AM
My FTTC was down for 20 minutes with no dsl light. Come back on. Check the DSLStats as I can see a change in Dslam type 0xa4a1 below:

DSLAM type / SW version:   BDCM:0xa4a1 (164.161) / v0xa4a1 (before: DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c)
Modem/router firmware:     AnnexA version - A2pvfbH043q.d26u
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 35 min 43 sec
Resyncs:                   0 (since 11 Dec 2019 00:45:33)
         
            Downstream   Upstream
Line attenuation (dB):     10.6      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           12.5      18.5
Power (dBm):               12.5      1.0
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

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

xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 37335 Kbps, Downstream rate = 112314 Kbps
Bearer: 0, Upstream rate = 19999 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):        12.5             18.5
Attn(dB):        10.6            0.0
Pwr(dBm):        12.5            1.0

xdslctl info --pbParams
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 37335 Kbps, Downstream rate = 112314 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
VDSL Port Details               Upstream                Downstream
Attainable Net Data Rate:        37335 kbps             112314 kbps
Actual Aggregate Tx Power:          1.0 dBm                12.5 dBm
====================================================================================
  VDSL Band Status   U0   U1   U2   U3   U4   D1   D2   D3
  Line Attenuation(dB):   2.1   12.4   20.9   N/A   N/A   5.8   15.3   26.2
Signal Attenuation(dB):   2.1   11.4   20.1   N/A   N/A   8.1   15.2   26.3
        SNR Margin(dB):   18.9   18.6   18.6   N/A   N/A   12.7   12.6   12.6
         TX Power(dBm):   -13.4   -30.1   0.9   N/A   N/A   8.2   7.9   7.0
        kl0(dBx100):    619     660       N/A     N/A     N/A   518     622     687     
ZySH>

xdslctl info --vectoring
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 37335 Kbps, Downstream rate = 112314 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Vectoring state: 5
VCE MAC Address: 0:0:0:0:0:0
Total error samples Ethernet pkts sent: 0
Total error samples Ethernet pkts discarded: 0
Total error samples statuses sent: 0
Total error samples statuses discarded: 0
ZySH>

Downstream      Upstream
General
   rtx_tx             0                  0               
   rtx_c              0                  0               
   rtx_uc             0                  0               
   LEFTRS             0                  0               
   minEFTR            79988              0               
   errFreeBits        3601873            0               
Bearer 0
   RxQueue            60                 0               
   TxQueue            20                 0               
   G.INP Framing      18                 0               
   G.INP Lookback     20                 0               
   RRC Bits           0                  24             
   Interleave depth   16                 1               
   INP                48.00              0.00           
   INPRein            0.00               0.00           
   Delay              0                  0               
Bearer 1
   Interleave depth   3                  0               
   INP                4.00               0.00           
   INPRein            4.00               0.00           
   Delay              3                  0 

1. Downstream Test: -provides background information.

   Download Speed
   76.14 Mbps
    
0 Mbps   77.35 Mbps
Max Achievable Speed

 Download speedachieved during the test was - 76.14 Mbps
 For your connection, the acceptable range of speedsis 40 Mbps-77.35 Mbps .
 Additional Information:
 IP Profile for your line is - 77.35 Mbps

2. Upstream Test: -provides background information.

   Upload Speed
   20.72 Mbps
    
0 Mbps   20 Mbps
Max Achievable Speed

Upload speed achieved during the test was - 20.72Mbps
 Additional Information:
 Upstream Rate IP profile on your line is - 20 Mbps   


Title: Re: So What Has Happened Here Then?
Post by: Ronski on December 11, 2019, 06:09:16 AM
Has you maximum attainable speed go up quite considerably?

Quote
Max:    Upstream rate = 37335 Kbps, Downstream rate = 112314 Kbps

Perhaps a major cross talker is offline.
Title: Re: So What Has Happened Here Then?
Post by: tubaman on December 11, 2019, 09:34:22 AM
Looks like it was just a firmware upgrade on the DSLAM.
It would be interesting to know what changes between versions, but I don't suppose such information is in the public domain.
 :)
Title: Re: So What Has Happened Here Then?
Post by: j0hn on December 11, 2019, 10:47:09 AM
It reports the line card version not a firmware version.
The line cards were more than likely physically swapped.

Check the cabinet for an expansion next time you pass.
Title: Re: So What Has Happened Here Then?
Post by: underzone on December 11, 2019, 11:06:06 AM
Really? Swapped out at 1am in the morning...
Title: Re: So What Has Happened Here Then?
Post by: j0hn on December 11, 2019, 11:09:29 AM
That's the only time they do line card swaps.
They are never done during the day*

Check the forum Search function for DSLAM version changes.
Always done after midnight.

edit: clarified comment above.
*Planned line card swaps always done at night. As is most planned downtime so as to minimise disruption.
A complete failure is repaired ASAP but usually a like for like swap.
Title: Re: So What Has Happened Here Then?
Post by: adslmax on December 11, 2019, 12:15:20 PM
Yep it does changed after midnight see screenshot below

Title: Re: So What Has Happened Here Then?
Post by: adslmax on December 11, 2019, 12:16:05 PM
Check the cabinet for an expansion next time you pass.

Will do
Title: Re: So What Has Happened Here Then?
Post by: NewtronStar on December 11, 2019, 05:18:16 PM
The same happened to me early hours in the morning 1am and the Dslam S/W has changed

Code: [Select]
Stats recorded 11 Dec 2019 17:13:42

DSLAM type / SW version: BDCM:0xa4a1 (164.161) / v0xa4a1
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  16 hours 36 min 13 sec
Resyncs:                0 (since 11 Dec 2019 16:31:39)

Downstream Upstream
Line attenuation (dB):  24.7 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 40000 8178
SNR margin (dB):        4.5 1.8
Power (dBm):            11.2 -0.5
Interleave depth:        16 1
INP:                    45.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0761 0.0000
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                2.79 0
Title: Re: So What Has Happened Here Then?
Post by: adslmax on December 11, 2019, 05:34:37 PM
Check the cabinet for an expansion next time you pass.

cabinet is no expansion on both pcp cabinet nor FTTC cabinet just checked this afternoon
Title: Re: So What Has Happened Here Then?
Post by: adslmax on December 11, 2019, 05:35:37 PM
Has you maximum attainable speed go up quite considerably?

Perhaps a major cross talker is offline.

I think mine went back online 1st could be that reason.
Title: Re: So What Has Happened Here Then?
Post by: NewtronStar on December 11, 2019, 06:39:09 PM
All that has happened is the DSLAM has had a software update and all those modems at your FTTC cab will have dropped the VDSL sync all at the same time its just who has the faster modem that syncs back up will see the crosstalk effect.
Title: Re: So What Has Happened Here Then?
Post by: Ronski on December 11, 2019, 10:05:10 PM
The stats were taken 35 minutes after resync, so other modems would have come back online, so wouldn't be the cause of the high attainable. I'm sure his attainable recently was around 80Mbps, but may be wrong.
Title: Re: So What Has Happened Here Then?
Post by: PhilipD on December 12, 2019, 08:43:49 AM
Hi

Same thing posted here, perhaps merge the threads?  Just a firmware update, not a card swap.

https://forum.kitz.co.uk/index.php/topic,24129.0.html

Regards

Phil

[Moderator note: Both threads now merged, as suggested.]
Title: Re: So What Has Happened Here Then?
Post by: tiffy on December 12, 2019, 10:38:41 AM
Yes. same DSLAM software revision changes recorded here, before & after and indeed same as adslmax has recorded in his recent post.
https://forum.kitz.co.uk/index.php/topic,24134.msg406335.html#msg406335

[Moderator note: The above mentioned thread has now been merged into this topic.]

As reported earlier, the two 40/10 lines are certainly running with higher US synch/data speeds and associated lower US SNRM's, DS was already topped out on these lines so little change.

The 80/20 line is still running with a DS SNRM of just over 1 dB, was just over 3 dB before DSLAM S/W update, DS and US are at max. contract synch rates with router predicted max. rates indicating less that current synch rates.

In the case of the 3 lines I monitor the S/W update appears to have produced performance improvements all around, more so on the two 40/10 lines as there was more room for improvement on the US rates.
 
Title: Re: So What Has Happened Here Then?
Post by: NewtronStar on December 12, 2019, 06:51:57 PM
It was the crosstalk effect after the DSLAM update, Upstream SNRM back to normal same as connection speed after turning off modem and then back on again this evening  ;)

Code: [Select]
Stats recorded 12 Dec 2019 18:49:03

DSLAM type / SW version: BDCM:0xa4a1 (164.161) / v0xa4a1
Modem/router firmware:  AnnexA version - A2pv6F039g1.d24m
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  0 hour 16 min 43 sec
Resyncs:                1 (since 12 Dec 2019 15:35:00)

Downstream Upstream
Line attenuation (dB):  24.7 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 40000 6480
SNR margin (dB):        4.6 5.9
Power (dBm):            11.2 -0.7
Interleave depth:        16 1
INP:                    45.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0870 0.0000
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                1.32 13.8

Title: Re: So What Has Happened Here Then?
Post by: jelv on December 12, 2019, 07:27:33 PM
As an aside, has anyone noticed that the BTw Performance Tester no longer offers the "Further Diagnostics" option, my last test was late November and it was offered then ?

Still accessible: http://www.speedtest.btwholesale.com/PerformanceTesterWS/diagnostics.do
Title: Re: So What Has Happened Here Then?
Post by: NewtronStar on December 12, 2019, 07:32:12 PM
I can also confirm this to be true Jelv at my end but the results a very wrong.
Title: Re: So What Has Happened Here Then?
Post by: underzone on December 13, 2019, 10:56:29 AM
I got the new firmware version early this morning too:

Code: [Select]
Stats recorded 13 Dec 2019 10:50:38

DSLAM type / SW version: BDCM:0xa4a1 (164.161) / v0xa4a1
Modem/router firmware:  AnnexA version - A2pv6F039v.d26a
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  10 hours 36 min 36 sec
Resyncs:                0 (since 13 Dec 2019 06:50:36)

Downstream Upstream
Line attenuation (dB):  16.5 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 80000 19999
SNR margin (dB):        3.4 15.2
Power (dBm):            13.3 7.1
Interleave depth:        8 1
INP:                    49.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0078 0.0010
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 4.90
Title: Re: So What Has Happened Here Then?
Post by: tiffy on December 13, 2019, 11:19:50 AM
@NewtronStar:

Quote
It was the crosstalk effect after the DSLAM update, Upstream SNRM back to normal same as connection speed after turning off modem and then back on again this evening

Accept that after a DSLAM outage for whatever reason it's going to be a race on re-instatement between all the serviced devices to attain synch and some form of pecking order is bound to be established, however, as I was reporting on 3 different lines on 3 different DSLAM's I thought that the S/W change may have been a factor in the increased US synch rates recorded, most likely not the case.

I won't be forcing re-synch's on the lines as in all cases there have been speed improvements and have not noted any significant increase in error rates, DLM will intervene if deemed necessary and yes, it's most likely that the synch speeds would return to pre-DSLAM outage state if/when this occurs or the lines re-synch for whatever reason.

@jelv:

The BTw Performance Tester URL I have always used is:
http://www.speedtest.btwholesale.com/

I always run this with Pale Moon browser in view of the known issue with Firefox, my normal browser.
Until recently, this has offered the option, after initial speed test, to proceed to "Further Diagnostics", enter phone number and obtain line BRAS profiles, no longer the case.

Have tried the URL you provided, yes it does work but as NewtronStar has said the reported speeds are completely incorrect with FF browser and the test won't complete with Pale Moon browser, advises that a temporary IP & domain name change are required to complete. 
 
Title: Re: So What Has Happened Here Then?
Post by: banger on January 06, 2020, 01:58:30 AM
Another resync just now but this time my VMG-1312-B10A came back with a 0.5db SNRm and 75m sync download. Funny how it is always early hours of Monday morning. I doubt the modem will hang on long to a 0.5db SNRm so rebooted the modem and it has come back at 3.3db SNRm and 65m sync. Very strange.