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]

Author Topic: VDSL2 Woes  (Read 6236 times)

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #15 on: June 01, 2017, 05:31:24 PM »

The engineer also mentioned he had preformed a DLM reset.

He was, clearly, one of Black Sheep's flock. The DLM reset (the "circuit recalc") has set everything back as if it is a newly provisioned circuit. So the 24 hour period will be from the time of that reset.

Quote
Am I right in thinking G.INP could be placed on the line?

G.Inp (more correctly G.998.4) is one setting in the DLM's repertoire which can be applied to the circuit if the DLM decides to intervene. It's best not to try and second guess what might happen . . . we should know by this time tomorrow.  ;) 
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.

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #16 on: June 01, 2017, 06:34:52 PM »

He was, clearly, one of Black Sheep's flock. The DLM reset (the "circuit recalc") has set everything back as if it is a newly provisioned circuit. So the 24 hour period will be from the time of that reset.

G.Inp (more correctly G.998.4) is one setting in the DLM's repertoire which can be applied to the circuit if the DLM decides to intervene. It's best not to try and second guess what might happen . . . we should know by this time tomorrow.  ;)

Right il leave well alone!

Looks like I have another engineer coming on Saturday, not entirely sure what he will be able to do in comparison with today's engineer?

 I will wait with bated breath...
Logged

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #17 on: June 05, 2017, 05:36:29 PM »

Quick update, the engineer on Friday left this note that I don't fully understand:

I cannot complete this task because I do not have the skills required to complete the task and could not obtain assistance on the day. I am passing to an engineer with underground skills because the fault has been proven underground. The line has been proven good to the PCP, OK at PCP D159. Battery Earth and HR to DP230 pr3. Spare pairs 4 dis at 17m and 8 dis at 300m from D. Battery contact was detected towards the end customer. OK at PCP D159. Battery Earth and HR to DP230 pr3. Spare pairs 4 dis at 17m and 8 dis at 300m from DP"

And today 2 jointing engineers spent all morning trying to find the fault and this is the note that has come through tonight after they left:

BT Fault Notification Only - Further work needed - Requires duct or maintenance dig
Right When Tested; End User Equipment;All BT tests completed ok, diagnostics show no fault condition
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5717
Re: VDSL2 Woes
« Reply #18 on: June 05, 2017, 06:43:03 PM »

It's pretty much as it says, Tom ....................... there are no good spare 'pairs' between the Cabinet (PCP) and the DP (Telegraph Pole, or Underground joint ..... dependant on location).
One 'pair' is required to deliver telephony/broadband services to each customer.

As such, the job has gone to the underground engineers to deal with the fault, and they have deemed it necessary to have a section of footpath, grass verge, etc etc ..... dug up by our contractors. The chances are there will be a wet joint where this dig is to take place ??.
Logged

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #19 on: June 05, 2017, 07:22:12 PM »

It's pretty much as it says, Tom ....................... there are no good spare 'pairs' between the Cabinet (PCP) and the DP (Telegraph Pole, or Underground joint ..... dependant on location).
One 'pair' is required to deliver telephony/broadband services to each customer.

As such, the job has gone to the underground engineers to deal with the fault, and they have deemed it necessary to have a section of footpath, grass verge, etc etc ..... dug up by our contractors. The chances are there will be a wet joint where this dig is to take place ??.

Thanks for explaining Black Sheep.

Hopefully sorting this wire out will help with the broadband speed  :)
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5717
Re: VDSL2 Woes
« Reply #20 on: June 05, 2017, 07:57:02 PM »

No probs, mate.  :)
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #21 on: June 06, 2017, 05:45:53 PM »

Although the Hlog plot for Tom's circuit shows the expected rapid decline in attenuation versus sub-carrier for the distance involved, it does not show evidence of any obvious defect(s) in the metallic pathway.

The QLN plot, however, remains looking like a fine-toothed flea-comb and I suspect that the AC balance is poor.

Finally the SNRM plot (with added retrain indicators), attached, shows that all is not well. The one plus point we can see from that plot is that the ISP/CP is A&A. I don't think they will allow the metallic pathway to be left in a defective state for too long . . .  ;)
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.

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #22 on: June 06, 2017, 06:44:06 PM »

Just had another update, the A55 was submitted yesterday and will take 5 days to process.

Just a matter of time now to see what OR can find underground, hopefully it will result in the cable being replaced  :fingers:
« Last Edit: June 06, 2017, 06:52:15 PM by burakkucat »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #23 on: June 06, 2017, 06:59:47 PM »

That is good to know. Thank you for the progress report.  :)



Just a quick comment, Tom. You will find that there is a "Reply" button to the bottom right of the frame. Quite often newer members will see the "Quote" button above the post and then use that to reply . . . which results in needless duplication. Hence the reason for my edit of your last post.
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.

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #24 on: June 11, 2017, 11:18:53 AM »

OR turned up this morning, they proceeded to repair the joint. Apparently it was full of water but they have remade it and apparently all is well.

The router stats have not changed drastically, the wide range of figures relating to attenuation visible on mydslwebstats is the different routers reporting the figure in their own way, the HG612 settled on 39.5dB after the work had been done, from an original figure of 43dB with a sync around 2600kbps exactly the same as before the fault was rectified.

The router connected now is the Billion 8900ax, it seems to have not reported a change in attenuation and is still at 40.1dB with a sync speed of 3621kbps, also the same as before...

The QLN plot has not changed looking at previous screenshots, so could there be still an underlying problem?

mydslwebstats: TomPoolHD

Thanks Tom.


EDIT: I have just seen the SNR has been bumped up and also the interleave depth has changed to 71... Maybe a DLM reset will help show the line in a raw form after the fault has been fixed, highlighting any obvious gains.
« Last Edit: June 11, 2017, 11:22:02 AM by TomPoolHD »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #25 on: June 11, 2017, 03:51:58 PM »

Currently there is not a great amount of detail available to view via MDWS.

What is apparent is that the circuit is now operating in interleaved mode -- so I presume a "circuit recalc" was not performed after the joint had been re-made.

The Hlog plot shows no obvious change as the overall loop-loss remains as before. The spikes in the QLN plot do not appear to be quite so large but it still maintains its "fine-tooth flea-comb" appearance.

No doubt A&A will also continue to monitor the circuit.
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.

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #26 on: July 11, 2017, 03:05:12 PM »

Persistence seems to be getting me somewhere. Today we had 3 BT OR engineers attend and completely replace our overhead section of our line, they even found a section that had been hit by lightning that had not been spotted by the numerous engineers that have visited before.

The attainable speed seems to have risen to around 6Mbps but the HG612 will not sync any higher than the current 2199kbps, could anyone help me out and explain what's going on?
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #27 on: July 11, 2017, 04:53:04 PM »

Was a DLM reset performed (a "circuit recalc") once all the work on the infrastructure was completed? If not, it could be that the DLM process is "holding back" the circuit.
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.

TomPoolHD

  • Member
  • **
  • Posts: 13
Re: VDSL2 Woes
« Reply #28 on: July 11, 2017, 05:07:01 PM »

Ok it looks like that has now happened, looks a lot better than before!

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Last initialization procedure status:   0
Max:    Upstream rate = 1285 Kbps, Downstream rate = 5880 Kbps
Bearer: 0, Upstream rate = 1285 Kbps, Downstream rate = 6009 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):        6.1             6.7
Attn(dB):        36.5            0.0
Pwr(dBm):        6.0             10.5
                        VDSL2 framing
                        Bearer 0
MSGc:           58              26
B:              174             31
M:              1               1
T:              25              59
R:              14              0
S:              0.9268          0.7805
L:              1640            328
D:              1               1
I:              190             32
N:              190             32
                        Counters
                        Bearer 0
OHF:            347616          351212
OHFErr:         14              10
RS:             17376544                3540787
RSCorr:         34              0
RSUnCorr:       29              0

                        Bearer 0
HEC:            24              0
OCD:            8               0
LCD:            8               0
Total Cells:    46459029                0
Data Cells:     3767974         0
Drop Cells:     0
Bit Errors:     0               0

ES:             36              24
SES:            23              0
UAS:            5941            5918
AS:             4044

                        Bearer 0
INP:            0.00            0.00
INPRein:        0.00            0.00
delay:          0               0
PER:            11.63           11.55
OR:             44.02           22.15
AgR:            6052.98 1306.89

Bitswap:        1542/1542               0/0

Total time = 4 hours 9 min 30 sec
FEC:            40              0
CRC:            1093            10
ES:             36              24
SES:            23              0
UAS:            5941            5918
LOS:            1               0
LOF:            22              0
LOM:            10              0
Latest 15 minutes time = 9 min 30 sec
FEC:            9               0
CRC:            2               6
ES:             2               6
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            6               0
CRC:            6               1
ES:             4               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 4 hours 9 min 30 sec
FEC:            40              0
CRC:            1093            10
ES:             36              24
SES:            23              0
UAS:            5941            5918
LOS:            1               0
LOF:            22              0
LOM:            10              0
Previous 1 day time = 0 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
Since Link time = 1 hours 7 min 23 sec
FEC:            34              0
CRC:            14              10
ES:             11              11
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: VDSL2 Woes
« Reply #29 on: July 11, 2017, 06:01:29 PM »

Ok it looks like that has now happened, looks a lot better than before!

I'll go and take a look via MDWS.

Later edit: I'll have to remember to take a look tomorrow as, so far, there have not been sufficient uploads to MDWS.
« Last Edit: July 11, 2017, 07:17:37 PM by burakkucat »
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]