Kitz Forum
Broadband Related => ADSL Issues => Topic started by: Weaver on August 15, 2019, 07:15:00 PM
-
All four lines are spiking downstream SNRM values, and d/s target SNRMs shot up to 9-17dB reducing d/s sync rates to a fraction of what they should be.
I have fought to get the target SNRMs something sensible, at 6dB, or 3dB if possible, but am still getting packet loss (CQM visible dripping blood) after rate resets.
Live sync rates:
#1: down 2483 kbps, up 525 kbps
#2: down 2468 kbps, up 496 kbps
#3: down 2553 kbps, up 248 kbps
#4: down 2821 kbps, up 449 kbps
These numbers don’t look too bad, but that’s because they are running at 6 dB d/s where necessary not 3dB and (ii) there are crazy error rates visible in CQM now causing real packet loss.
-
I’ve been so ill over the past few days, stomach cramps, diarrhoea, shaking, nausea, pain - all to do with problems with the fentanyl that I am on, causing constipation then swinging to the opposite. Added an extra small fentanyl patch from the hospital late at night because I felt so ill and we had run out of patches, and the patch I was using ran out too soon, perhaps something to do with the diarrhoea. Then today the pharmacy screwed up the fentanyl order or lost it or something but Janet got there in the end.
Anyway, all lines are going crazy. New fb2900 doesn’t appear to work for some reason. I have got a new 4G usb ‘dongle’ nic too, and when Janet plugged in fb2900 plus 4G NIC without telling me, everything went haywire. Total chaos and I was completely overwhelmed with confusion as just nothing seemed to work, couldn’t access the new Firebrick (sometimes). So went straight back to fb2700 plus 3G NIC as I’m too ill to work out what’s happening. All this bad stuff at once.
I need to get the lines sorted out first, throw that problem at AA.
The fact that four lines have gone bad simultaneously, to different groups degrees - what does that mean? A lorry ran over the cable perhaps?
This is the month for morons pulling off the roadsides and getting stuck because they simply can’t drive. Evidenced by crazy pictures seen on the web, such as one from Trondairnis, in a picturesque glen - I forget exactly where - near Uige, and on the west coast of the Island, in Gleann Bhreatail. So it does make me wonder if a bit of off-roading might be the answer. Weather has been mild and a bit damp at times so the ground will be soft. Rocks under the cable as well on the high moor.
-
Live sync rates:
#1: down 938 kbps, up 522 kbps
#2: down 1493 kbps, up 458 kbps
#3: down 1308 kbps, up 248 kbps
#4: down 1831 kbps, up 449 kbps
Couldn’t sustain the relatively normal d/s sync rates, not even at a respectable 6dB d/s so the d/s sync rates dropped to the above values.
-
The fact that four lines have gone bad simultaneously, to different groups degrees - what does that mean? A lorry ran over the cable perhaps?
Yes, something like that would do it. :(
Do you have an idea of the approximate number of premises in Heasta? I'm trying to gauge: (1) the total number of pairs required (2) how many cables are actually used from the Broadford TE to Heasta.
-
I’m guessing about 20 premises now but there has been such a huge lot of house building very recently that I am likely to be out of date. I am the first house as you know, so if it affects me it is likely to affect others so I should perhaps ask Janet to ask around, see if anyone else is unhappy.
-
An e-mail message carrying the snapshot plots for your four lines has now been sent on its way to you. :)
As for the cable sizing, I'm tempted to assume two of fifty pair cables have been run from the Broadford TE to Heasta.
-
And amazingly the 3G link was down tonight, but came back up on its own, before going down again, so truly cursed. Hardly an MSO but the equivalent for me myself. Links are all up, but just with horrible performance. Below fault tolerance rate.
-
If one link stays up long enough for you to "get word out" to A&A that will, at least, be the first hurdle overcome.
-
All links are always up, and I have two other lots of independent 3G and 4G, on three - another link from Three on my iPad and Janet’s too and Janet’s iPhone speaks EE 4G. I also have a Solwise model something or other 4G wireless modem-router ready configured, if I can find it, as yet another backup.
So have managed to send multiple ‘nano-MSO’ type emails successfully to AA, but it’s now after hours of course. Didn’t try irc as I was too exhausted from feeling ill. Managed to eat something, a sandwich, for the first time in a day or two, so that might help.
I emailed Andrew-AA -saying I need some serious help, so AA, if you’re out there? Right now some lines are down to 30% of their expected downstream sync rate.
It’s only the enormous target SNRM downstream currently that is preventing them from dropping the link.
A big lorry came the other day to load up fat lambs and take them away, I think. But that was too late; the timing was not consistent as I think the badness had started before that; can look back in the clueless.aa.net.uk CQM pictures.
-
Picture from clueless. This image took so long to upload, it was like going back to dialup :
(https://i.ibb.co/f2GqkKd/826-B1-A99-28-AC-4054-93-A1-53-E51-B6-ABC67.jpg)
-
That image looks really fuzzy to me, horrible. What should I be doing to easily upload an image to <somewhere> so that I can link to it in posts?
Update, with huge target SNRM d/s values in force:
Live sync rates:
#1: down 938 kbps, up 522 kbps
#2: down 1493 kbps, up 458 kbps
#3: down 1308 kbps, up 248 kbps
#4: down 1831 kbps, up 449 kbps
An Ookla speed test gives me a result of 4.7 Mbps downstream, 1.3 Mbps upstream. The reference standard AA speedtest2.aa.net.uk gives eg 4.92 / 1.27.
-
OR engineer is working on a ticket to look at line 1 right now - out on the high moor in the rain.
One very confused man told Janet a load of rubbish because he got confused, thought that the internet line cwcc@a.1 822xxx is our voice line, but our published voice line number is 505xxx (which is AA voip redirected to Janet’s mobile. and he thought that the fact he was speaking to her at all proved that he had fixed things, except it meant nothing of the kind, he was talking to her mobile phone. This was possible because in addition Janet set up a redirect from 822470 to her mobile so that the old number would still work. And that really confused him. And she never told me about it, when she did that years back, which was not good, I only heard about it today.
He hasn’t finished the tests yet, but I presume he has done something.
-
I went crazy and set up bt ‘enhanced care’ on all lines - priority maintenance, as I have a bad feeling about all of this.
AA tells me this means ‘Extra level of maintenance on broadband lines with a 20 hour target fix from when we report fault in to BT.’
This is a bit mad, and then some, because it is going to cost me £12 per line per month, not sure if that is inc cat for vat to be added on top. But I will just do it for a short while until things are cleared up and seem to be staying that way, and then I will turn it all off again (which will probably waste some more money as I bet there’s a charge for turning it off for all I know)
-
Line 1 looking v. good now. AA amazingly efficient, got BT out really quickly. I delayed things myself by two days because I was so ill I couldn’t thin.
I suppose we just have to work through the other lines now. Groan.
Line 1 was the worst performer, lowest d/s sync of only 950k instead of 2800k d/s sync.
Am worried about what to do if the other lines don’t show up as ‘bad’ in some sort of bt official test sense. The target SNRM being ridiculously high is the only thing keeping them from dropping. But most significant is that the d/s rates of 2,3,4 are all FTB so I suppose that that’s officially broken, by definition? Being below the FTR, that is? (I see the FTR-breaching lines are listed in the sinners’ section at the top in clueless.aa.net.uk, which is a nice idea, as they stand out prominently as the lines that are problematic.)
There ought to be a BT FTR for upstream. It’s incredible that BT etc don’t seem to think upstream even matters. Amazing.
-
Line 3 looks very good indeed now, as well as line 1. Line 2 still pretty awful and line 4 extremely awful.
Out very own johnson’s custom stats-graphing firmware in the ZyXel modems has been invaluable during this. Many thanks to him!
Janet tells me that there has been a mini digger working right by the PCP that was used to supply cwcc@a.2 last summer and an FTTC cab -not sure which is which, I forget now, as the two green boxen are pretty close together on opposite sides of the main road roughly. Which box was which ?
Janet is wondering if that mini digger has disturbed things. The digger is by the box on the south side of the road. Anyway, the Heasta-bound links will be coming from around there on their route to/from the Broadford exchange. They are supposed to be EO lines, but I don’t think there’s any way that line 2 can be and that makes me doubt the others’ true EO status.
-
Spoke very much too soon. All lines are now back to d/s below fault threshold breach sync rates.
Live sync rates:
#1: down 1575 kbps, up 522 kbps
#2: down 1493 kbps, up 458 kbps
#3: down 1501 kbps, up 248 kbps
#4: down 1831 kbps, up 449 kbps
Burakkucat reminded me about the stealing of an E-side for the new line #2 last summer, and I do remember that much.
So now Janet is saying that the mini digger is by what Burakkucat tells me is a Huawei AIO cab, on the south side of the road. (I need a link to Google street view.)
I didn’t know of the existence of AIO cabs. Last summer I was confused because I thought that we were only supplied here by true EO lines. Does it seem likely that all my lines are in fact not EO lines at all, or used to be and now no longer are ? That is, might they all have an E side from NSBFD to the green box(en) at Harapul, by the Claymore restaurant and then from there four ultra long D sides to Heasta?
-
Quickly butting in, this curious non-feline tried to find Heasta on Google maps, but only found Heast.
The lack of detail up there is prominent.
-
Spellings vary on the maps Heasta is in my view much to be preferred, Heast is an acceptable alternative seen on maps too. The alternative ‘Heaste’ is an impossible spelling, I suspect it’s probably an English phonetic attempt based on the English word "haste".
I am at https://goo.gl/maps/HfkDuspSrnAEynxk6
The post code IV49 9BN in google maps gives you no 6 much further down in the centre of the village.
As for lack of detail on the maps, I get very detailed imager and street view works very well. Try changing map type - there’s some icon in my google maps app to change to satellite view.
There was an older thread in which Burakkucat I think posted some excellent street view shots.
-
So now Janet is saying that the mini digger is by what Burakkucat tells me is a Huawei AIO cab, on the south side of the road. (I need a link to Google street view.)
The image in my possession was captured by Mrs Weaver . . . but, try as I might, I cannot cross-reference the background to anything I see in Google Street View. (Obviously neither of the cabinets appear in Google Street View as those images were captured back in 2011.)
Last summer I was confused because I thought that we were only supplied here by true EO lines. Does it seem likely that all my lines are in fact not EO lines at all, or used to be and now no longer are ? That is, might they all have an E side from NSBFD to the green box(en) at Harapul, by the Claymore restaurant and then from there four ultra long D sides to Heasta?
"Used to be and no longer are" is what I strongly suspect. Then a yes to your speculation . . . An E-side from the Broadford TE to the cabinet(s) near the Claymore Restaurant and a D-side from the cabinet(s) to Heasta.
Call up the BT Wholesale Broadband Availability Checker (by address) (https://www.dslchecker.bt.com/adsl/ADSLChecker.addressOutput), enter just the post code (IV49 9BN) and left-click on "Submit". View the list of addresses displayed, one of which is a slightly corrupted version of that of the "Weaving Shed", left-click on that address and left-click on "Submit". What is displayed is how things originally were, with EO lines.
Now call up the BT Wholesale Broadband Availability Checker (by telephone number) (https://www.dslchecker.bt.com/pls/adsl/adslchecker.welcome), enter the relevant number assigned to each line and left-click on "Submit".
Finally call up the BT Wholesale Broadband Availability Checker (by BBEUID) (https://www.dslchecker.bt.com/pls/adsl/ADSLChecker.bbeuidform), enter the relevant BBEUID for each line and left-click on "Submit".
None of the output will mention a cabinet number. According to Magenta Systems "CodeLook" (https://www.telecom-tariffs.co.uk/codelook.htm) the post code IV49 9BN is supplied by an EO cable, numbered 8.
I have saved, in an appropriately named directory, screen-scrapes of all the output those sites have provided. I'm sure I gave a copy to you some time ago. (If you would like another copy, just say the appropriate magic incantation.)
As for that earlier thread, in which I posted some images from Google Maps Street View, I believe it is the one titled "Ultra-long line beyond 63.5 dB attn" (https://forum.kitz.co.uk/index.php/topic,16585.msg306545.html) that stretches over eight pages. The more interesting images that I discovered were attached to this post and further onwards. (https://forum.kitz.co.uk/index.php/topic,16585.msg306715.html#msg306715)
-
The lines are
1 BBEU20700042
2 BBEU29735631
3 BBEU20700055
4 BBEU20709519
Update - dsl lines looking much, much better again now.
Live sync rates:
#1: down 1575 kbps, up 522 kbps
#2: down 2726 kbps, up 505 kbps
#3: down 2520 kbps, up 419 kbps
#4: down 1831 kbps, up 449 kbps
Lines 1 and 4 were as you see still sickly-looking, FTB both.
And now all healthy again ! ;D
I don’t know what they might be like long term but I forced a retrain on these two lines by manually commanding the modems, just to get the SNRM back to normal for now.
Live sync rates:
#1: down 2508 kbps, up 525 kbps
#2: down 2726 kbps, up 505 kbps
#3: down 2520 kbps, up 419 kbps
#4: down 2832 kbps, up 452 kbps
The above are at 6, 3, 3, 3 dB SNRM downstream respectively, so in fact line 1 should be better as the old line 1 value was at 3dB downstream.
And a thank you for Burakkucat for digging up those reference and that old thread - a job that I struggle a lot with. The url able for bbeu checking gave me a 404 or similar. The url that works for me is https://www.dslchecker.bt.com/pls/adsl/adslchecker.welcome
-
And I jinxed it. On Saturday morning all lines were bad again and still are now.
-
And with Monday being a bank-holiday, there is no way for you to report the problem to A&A and for them to initiate action by Openreach. :(
-
I fell asleep on Saturday and didn’t notice that the problem had come back. So I should now re-instigate AA event reporting, where I can get an email and sms message to tell me about line-up,line-down events. I got so many of these (x4x2) that I was overwhelmed and I disabled them. But AA was working on saturday and I could have reported it to them in the morning.
I had such a bad bad feeling about this when it started, a problem on all lines simultaneously. So last week I immediately set up BT enhanced care on all lines (£12).so when it does get reported to BT I think it’s 20 hours to fix it.
-
Whatever the cause (or trigger) it has to be something common to all four circuits and external to your domain.
-
Since Sunday all lines have been pretty much ok.
Live sync rates:
#1: down 2400 kbps, up 522 kbps
#2: down 2385 kbps, up 509 kbps
#3: down 2428 kbps, up 321 kbps
#4: down 2464 kbps, up 449 kbps
These sync rates might look a bit rubbish 400k - 500k lower than before but the above figures are based on a 6dB downstream target SNRM not 3dB as before, so in fact they are not too bad.
-
Thursday all lines in a total mess, all four FTB.
Live sync rates:
#1: ?, ? (modem is down/coming up)
#2: down 1662 kbps, up 449 kbps
#3: down 1475 kbps, up 416 kbps
#4: down 2206 kbps, up 452 kbps
OR Engineer is coming out to attend to line 1 battery contact. That could well be why line 1 is down right now, because they’re working on it. Janet says it has been a horrible day - wet and blowy. I can’t hear the wind just now, but the double glazing is very effective against noise, (even though atrocious thermally and it’s even drafty,) and also I am as deaf as a post.
For line #1:
2019-08-30 11:01:33 2 Sep 11:01:33 Track fault and update customer PSTN Fault - NSY aa@aa
2019-08-30 11:01:33 2 Sep 11:01:33 Wait for supplier to confirm fault cleared PSTN Fault - NSY aa@aa
Waiting on faultbtconfirm Wait customer confirms fault closed PSTN Fault - NSY aa@aa
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Informational Message: 4058 Notification Only - Fault is assigned to Engineer. Fault status is now PONR. bt
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Status: Open - Past PONR bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Notes Field: **Line Stability:**Network Stability:**Test Outcome:Fail**MFL:LN**Term Statement:LINE TERMINATION DETECTED**Line Signature:**Distance to Fault:0**Cable length:7.95**Test Start Time:2019-08-30T12:02:37**Test Stop Time:2019-08-30T12:02:37 bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Informational Message: 4465 Please refer to the Notes field for the actual message bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Status: Open - Associating Info bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Informational Message: 4040 Notification only - Estimated Response Time. bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Informational Message: 3100 Trouble Report Accepted bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Status: Open - New bt
2019-08-30 11:01:40 Track PSTN Fault 5-8-177463831366 Message Informational 9323 The asset care level 2.5 will be applied rather than the specified service level. bt
2019-08-30 11:01:40 Track PSTN Fault 5-8-177463831366 Message Informational 3241 Notification Only - Trouble Report Creation Request is Pending
—
I never understand this asset care level thing ?
Note that it says "cable length 7.95" (km?), which would equal 4.94 miles. I’m surprised at that, it’s a bit longer than I thought. We have talked about this before. Maybe it just means I didn’t measure and include all the small wiggles in the cable as accurately as I should have. I used a web-based measuring tool (FreeMapTools) (https://www.freemaptools.com/measure-distance.htm) against a road map. (I presume it does not mean all the copper including the bit past my house all the way down to the shore? Is that even possible? Would be a bit weird then because it would not apply to my line only; you would have to say something like it’s a part of / belongs to a 7.95km line. Doesn’t seem at all likely to me.) I must just have got my length measurement wrong or I was too simplistic with it.
Line #3:
2019-08-30 11:24:03 WLR3Test NSY hws00556dat01:178074817: Pass Line Test OK - All sockets unplugged ServiceLevel:2.5, MainFaultLocation:OK, FaultReportAdvised:N, AppointmentRequired:N, LineStability:Stable, NetworkStability:Stable, StabilityStatement:Stable - no adverse line test history. CP may request an Engineer visit to investigate, test and demonstrate with the EU. Routine test & fault data available at Customer Diagnostic Tool on INFORMe under MIS>Artisan>CDT. If no fault is found clear RWT and apply Time Related Charges. aa@aa
2019-08-30 11:06:41 2019-08-30 11:07:24 BT Test xDSL Copper Test:Pass Line test failed report fault to OR. Appointment advised.Pass Line test failed report fault to OR. Appointment advised. T107:FAULT - Dis In Network aa@aa
So is that a fault or not ? AA suggested that a fault such as in line 1 involving a short may generate crosstalk seen in the other lines.
-
That's a fault .. "Dis In Network"
-
I really can't make much sense out of those log snippets from A&A for the time stamps are not chronologically ordered. :-X
Assuming an inverse chronological order and making editorial adjustments for line #1:
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Informational Message: 4058 Notification Only - Fault is assigned to Engineer. Fault status is now PONR. bt
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:04:41 Track PSTN Fault 5-8-177463831366 Status: Open - Past PONR bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Notes Field: **Line Stability:**Network Stability:**Test Outcome:Fail**MFL:LN**Term Statement:LINE TERMINATION DETECTED**Line Signature:**Distance to Fault:0**Cable length:7.95**Test Start Time:2019-08-30T12:02:37**Test Stop Time:2019-08-30T12:02:37 bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Informational Message: 4465 Please refer to the Notes field for the actual message bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:02:48 Track PSTN Fault 5-8-177463831366 Status: Open - Associating Info bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Informational Message: 4040 Notification only - Estimated Response Time. bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Informational Message: 3100 Trouble Report Accepted bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Estimated Response Time: 2019-08-31T23:59:59 bt
2019-08-30 11:01:56 Track PSTN Fault 5-8-177463831366 Status: Open - New bt
2019-08-30 11:01:40 Track PSTN Fault 5-8-177463831366 Message Informational 9323 The asset care level 2.5 will be applied rather than the specified service level. bt
2019-08-30 11:01:40 Track PSTN Fault 5-8-177463831366 Message Informational 3241 Notification Only - Trouble Report Creation Request is Pending
2019-08-30 11:01:33 2 Sep 11:01:33 Track fault and update customer PSTN Fault - NSY aa@aa
2019-08-30 11:01:33 2 Sep 11:01:33 Wait for supplier to confirm fault cleared PSTN Fault - NSY aa@aa
Waiting on faultbtconfirm Wait customer confirms fault closed PSTN Fault - NSY aa@aa
For line #3 the information is inverse chronologically ordered:
2019-08-30 11:24:03 WLR3Test NSY hws00556dat01:178074817: Pass Line Test OK - All sockets unplugged ServiceLevel:2.5, MainFaultLocation:OK, FaultReportAdvised:N, AppointmentRequired:N, LineStability:Stable, NetworkStability:Stable, StabilityStatement:Stable - no adverse line test history. CP may request an Engineer visit to investigate, test and demonstrate with the EU. Routine test & fault data available at Customer Diagnostic Tool on INFORMe under MIS>Artisan>CDT. If no fault is found clear RWT and apply Time Related Charges. aa@aa
2019-08-30 11:06:41 2019-08-30 11:07:24 BT Test xDSL Copper Test:Pass Line test failed report fault to OR. Appointment advised.Pass Line test failed report fault to OR. Appointment advised. T107:FAULT - Dis In Network aa@aa
Agreeing with aesmith, yes a disconnection fault in the network for line #3.
-
Where is the line 3 fault then, do we know?
How do we get someone to look into line 3 then? I am hoping I don’t need to start a separate support ticket as they will see that it needs attention. They were monitoring line 3 at aa anyway, we see that.
I thought that the lines are ordered most recent at the top. I did some search+replace operations - replacing stuff like today and yesterday as I know Burakkucat hates that ;D ;D and it makes it difficult to read in the future. I also did some replacements to anonymise it such as getting rid of phone numbers and the names of AA staff. (I suspect that I have been neglectful in this respect in the past, for which I am sorry.)
-
Where is the line 3 fault then, do we know?
No, I can't feel any "tingles in the whiskers". The "Dis in Network" could be anywhere between the IDCs on the NTE5 (where the aerial drop is terminated in the office) and the MDF in NSBRD.
How do we get someone to look into line 3 then? I am hoping I don’t need to start a separate support ticket as they will see that it needs attention. They were monitoring line 3 at aa anyway, we see that.
As that snippet showed the test response, with a clear directive, I would expect that A&A will act upon it. "Line test failed report fault to OR. Appointment advised. T107:FAULT - Dis In Network".
I thought that the lines are ordered most recent at the top.
In the first snippet of the two that you posted, it appears the first three lines should be located at the bottom. Once that transform is completed, the date/time stamps of all the lines are then in reverse chronological order.
-
It seems then that ‘clueless.aa.net.uk’ must be doing something funny with the ordering, because I didn’t change it. Perhaps I got something wrong somehow.
Lines 3 and 4 are very very bad just now 2029-08-31T0150. Flapping like mad.
-
Lines 3 and 4 are very very bad just now 2029-08-31T0150. Flapping like mad.
The previous test showed a hard fault on Line 3, although apparently not one that stops DSL working altogether. What does the test show for Line 4?
-
That image looks really fuzzy to me, horrible. What should I be doing to easily upload an image to <somewhere> so that I can link to it in posts?
You don't need to upload images anywhere!
When composing your post, expand the Attachments and other options and select the image from your PC to attach - it will be uploaded to the Kitz server. It will appear as a thumbnail under your post which when clicked expands to the full image.
-
If you do want to include the full image in the body of the post, firstly do as I've described above. Then view your post, expand the image and then grab a copy of the image location. Edit your post and include the image like so:
(https://forum.kitz.co.uk/index.php?action=dlattach;topic=23742.0;attach=27572;image)
Bingo!
-
That is such an excellent tip, btw. Logical thinking.
—
DLM went crazy this week driving downstream sync rates down to silly low levels, but after forcing a retrain and resetting the target SNRMs then all is well at the moment.
Live sync rates (n.b. 3dB downstream SNRM):
#1: down 2876 kbps, up 525 kbps
#2: down 2765 kbps, up 515 kbps
#3: down 2916 kbps, up 419 kbps
#4: down 2850 kbps, up 496 kbps
-
1. Since Sunday 2019-09-08 the lines have been consistently excellent, with downstream SNRM down-spiking completely gone. This really has been the month from hell. A&A worked very very hard but were perhaps overwhelmed. DLM was a disaster.
2. One new development: for the first time in a year, the daily square wave of upstream SNRM on line 3 has disappeared completely. This has improved line 3’s upstream performance and reliability a lot, and it has made the grouping of upstream speeds closer, since line 3 is now no longer hugely slower than the others, just a bit slower.
3. For some unknown reason, despite this, speed tests on upstream throughput give poor results. Since both the closer upstream sync rate grouping and increased upstream sync rate of line 3 contribute towards improved combined performance then this is unexplained and counterintuitive.
Line 1 SNRM Sun-Mon :
(https://i.ibb.co/wd3V99D/453-CF697-159-C-4587-958-D-6-C9-B8-E93-F016.png)
Line 2. Don’t yet know what the 1.5 dB u/s downstep is all about. That remains to be seen. It’s a nuisance though.
(https://i.ibb.co/p40CjyT/2-CEB29-F9-5-E7-D-4264-AAE0-75-F9-FD2-ACD8-E.png)
Line 3. No more green (upstream) daily square wave:
(https://i.ibb.co/88MPxrm/9-AE4-C387-DCFB-4432-A577-796-C2-DF4-B7-A7.png)
Line 4:
(https://i.ibb.co/4YW9Hf0/15958-C00-D45-D-46-C7-BAF6-2-C67-A93341-EB.png)
-
A later shot of line 2, Monday 9 Sep until now Tue 2019-09-10T01:00 UTC
So we have a 1.6 dB high possible daily square wave, which would be a nuisance, if it keeps up. This kind of behaviour was seen on line 2 before, but it was line 3 that was notorious for exhibiting it. So maybe this is a lesser version of ‘the new line 3’ in this respect, if it keeps up.
(https://i.ibb.co/7SB18JZ/4-A973-D78-DD41-4777-A2-CC-4-ED98-B8-B9-AF5.jpg)