Print

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

[burakkucat]

Ah, asked Janet which pole she meant. Today, Monday, our man went up the lower pole by the far side of the road, further away from the house. I think I misunderstood before; I was thinking that it cannot be the pole near the house as there are afaik no joints on it.

Obviously I only have a "snapshot in time" to view and then only at the lower, road-side, pole. That is the one with a BT66 at the top, to house the joints between the two aerial drops (from "The Weaving Shed") and the tail, running down the pole, linking to the D-side cables.

Finally, fixed !

Anyway, second man came out around midday and fixed the problem at that pole. The line 4 is now running at 2.832 Mbps d/s @ 3.2 dB SNRM, 550kbps upstream @ 5.8 dB SNRM.

Excellent news. (Let's hope that the haggis do not decide to climb the pole and gnaw on the freshly re-made joints.    )

[Weaver]

I’m afraid that in the past we have had evidence that haggises can climb poles. 

[Weaver]

Notes received by AA from first engineer, on saturday:

Note Engineer could not complete the work. As per his notes "I cannot complete this task because of a hazard owned by Openreach / third party. Unable to climb pole at dp72 as I am in a loan van and do not have my climbing harness is preventing further work. Please see additional information: Pair is faulty from joint feeding dp72 faulty towards Eu; unable to climb pole as I am in loan van and no harness to climb. Hence creating CSS Task and assigning the job to SN Team and completing action item. Review by date 26/08/2020."

[burakkucat]

Ah, so that was the reason and not a dangerous pole, as originally thought.

[Weaver]

The dangerous pole must have been Janet thinking about the upper pole - some confusion there anyway.

[Weaver]

And here we go again. The fix didn’t last; the fault has come back on line 4 (and line 2 - the most recently installed).


xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 515 Kbps, Downstream rate = 2552 Kbps
Bearer:   0, Upstream rate = 560 Kbps, Downstream rate = 2310 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):    6.1       5.9
Attn(dB):    65.0       41.5
Pwr(dBm):    18.1       12.4

         ADSL2 framing
         Bearer 0
MSGc:      52      13
B:      26      62
M:      8      1
T:      3      1
R:      16      14
S:      2.9414      3.5402
L:      631      174
D:      1      8

         Counters
         Bearer 0
SF:      752848      719419
SFErr:      0      1
RS:      16374447      770625
RSCorr:      601      7297
RSUnCorr:   0      0

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

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   65909686      15978087
Data Cells:   679324      183175
Drop Cells:   0
Bit Errors:   0      722

ES:      644552      1332
SES:      1771      1
UAS:      64990      63853
AS:      12095

         Bearer 0
INP:      26.00      2.50
INPRein:   0.00      0.00
delay:      8      7
PER:      15.99      16.81
OR:      29.01      9.03
AgR:      2329.95   567.23

Bitswap:   487/487      47/47

Total time = 74 days 13 hours 28 min 11 sec
FEC:      26852419      2238836
CRC:      947821      1308
ES:      644552      1332
SES:      1771      1
UAS:      64990      63853
LOS:      83      0
LOF:      438      0
LOM:      51      0
Latest 15 minutes time = 13 min 11 sec
FEC:      40      474
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:      45      507
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 = 13 hours 28 min 11 sec
FEC:      9550      10960
CRC:      484      1
ES:      18738      1
SES:      10      0
UAS:      119      109
LOS:      1      0
LOF:      9      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      0      0
CRC:      0      0
ES:      25757      9
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 3 hours 21 min 35 sec
FEC:      601      7297
CRC:      0      1
ES:      0      1
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0

[burakkucat]

I must be having another bad day. 

Please enlighten me by explaining what I am supposed to be seeing when I look at that latest statistics output. For example, I see --

ES:      644552      1332
SES:       1771         1

But that appears to be spread over --

Total time = 74 days 13 hours 28 min 11 sec

[Weaver]

You are not the only one.    What perplexes you? Are those values implausible?

[burakkucat]

A block of data, such as the above, really tells nothing. Unless there is a reference data set with which it can be compared.

I presume you have looked at the various plots and are seeing an "eroded summit", once again? Do you experience a problem when just using the service?

Hmm . . . Not sure what else I can really type. 

[Weaver]

It’s back to the same hollow at the summit, yes. The loss of downstream sync rate an as bad as it as before (not yet anyway).

for comparison, here’s modem 3:

xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 312 Kbps, Downstream rate = 3200 Kbps
Bearer:   0, Upstream rate = 376 Kbps, Downstream rate = 2861 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       6.1
Attn(dB):    65.0       41.2
Pwr(dBm):    18.2       12.4

         ADSL2 framing
         Bearer 0
MSGc:      53      11
B:      32      5
M:      4      16
T:      3      8
R:      10      14
S:      1.4508      8.0000
L:      783      110
D:      2      4

         Counters
         Bearer 0
SF:      237508496      852465
SFErr:      4587      176
RS:      1919816364      4293165
RSCorr:      1011080      99952
RSUnCorr:   23782      0

ReXmt:      520206      0
ReXmtCorr:   473853      0
ReXmtUnCorr:   25343      0

         Bearer 0
HEC:      23603      170
OCD:      576      0
LCD:      576      0
Total Cells:   140982884      3404393386
Data Cells:   1332365539      178176483
Drop Cells:   0
Bit Errors:   662586      18580

ES:      2419      161
SES:      3      0
UAS:      53      53
AS:      3839699

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      8
PER:      16.04      17.00
OR:      29.40      8.00
AgR:      2878.13   382.50

Bitswap:   939067/939151      48693/48693

Total time = 44 days 10 hours 35 min 52 sec
FEC:      1011080      99952
CRC:      4587      176
ES:      2419      161
SES:      3      0
UAS:      53      53
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 5 min 52 sec
FEC:      3      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:      5      5
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 = 10 hours 35 min 52 sec
FEC:      691      285
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      1955      1665
CRC:      5      6
ES:      3      6
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 44 days 10 hours 34 min 57 sec
FEC:      1011080      99952
CRC:      4587      176
ES:      2419      161
SES:      3      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0

[Weaver]

Here’s the modem 4 SNR-vs-tones graph :

[burakkucat]

I wish we could determine the actual, physical, cause of the "eroded summit" effect. Knowing the cause, even if it cannot be mitigated, would help alleviate so much of the head-scratching. 

[Weaver]

What we do know, for certain, is that BTOR can see the fault on their JDSUs or whatever, and can fix it successfully, but only for a while. When they have fixed it it just comes back at some point, but I’m not sure about the level-vs-time reappearance of the fault. I have never seen anything like it before this summer. Line 2 and line 4 are the two pairs in the same drop cable, btw.

[burakkucat]

Line 2 and line 4 are the two pairs in the same drop cable, btw.

The newer aerial drop of the two which rise from the low-level, road-side, pole. (I am amused by drops which actually rise.) However I do not think that the two lines, which intermittently show the problem, being in the same drop cable is significant. That is to say I think it is just a co-incidence.

The head-scratching continues.

[Weaver]

I’m wondering about when to keep reporting these two lines; as they get slower there comes an arbitrary point where I choose to report them as ‘bad’ (sufficiently). I hate to keep on bothering AA again and again, like a cracked record. But the sooner I report them, the less time I have to put up with reduced downstream speed.

What do you think is reasonable ? Wait till a line becomes an FTB ?

I can’t remember what the percentage is - Kitz will tell me somewhere - but I don’t have to remember as clueless puts it up in your face - at the very top of its main system state display page it displays a list of any lines that are in breach of the fault threshold rate, so as to alert you.

My neighbour has built a house next door to me and has presumably put in phone lines. I wonder if that is the source of all of these problems?

How would you physically run new lines into a new dwelling?