Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Weaver]

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?

[renluop]

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.

[Weaver]

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.

[burakkucat]

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), 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), enter the relevant number assigned to each line and left-click on "Submit".

Finally call up the BT Wholesale Broadband Availability Checker (by BBEUID), 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" 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" that stretches over eight pages. The more interesting images that I discovered were attached to this post and further onwards.

[Weaver]

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 !   

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

[Weaver]

And I jinxed it. On Saturday morning all lines were bad again and still are now.

[burakkucat]

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. 

[Weaver]

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.

[burakkucat]

Whatever the cause (or trigger) it has to be something common to all four circuits and external to your domain.

[Weaver]

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.

[Weaver]

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

[aesmith]

That's a fault .. "Dis In Network"

[burakkucat]

I really can't make much sense out of those log snippets from A&A for the time stamps are not chronologically ordered. 

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.

[Weaver]

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

[burakkucat]

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.