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: Line drops.  (Read 3755 times)

psykix

  • Member
  • **
  • Posts: 15
Line drops.
« on: February 25, 2018, 11:24:40 AM »

I have been using a Huawei HG612 modem (unlocked) with my Ubiquiti USG3P for a while now and all has been fine.

 

In the last few months, I began to get WAN drops, and they began to get more frequent.

 

I had the ISP check the line, and there were no faults found. I also did a quiet line test which was fine.

 

It appeared that I could see the VDSL connection dropping on the HG612 so I purchased a Vigor 130 and replaced it.

 

The Vigor 130 was far worse and would drop multiple times within a day. I put the HG612 back in. I rang to get an engineer out and they were reluctant and advised I would be charged if no fault was found. They requested that I remove the VDSL filter faceplate and plug directly into the test socket behind. I removed the faceplate but could not use the test socket as it was not an RJ11. I put the faceplate back and continued to use the HG612. The WAN link was then perfect for days. I presumed there may be a fault with the VDSL filter, so purchased a new NTE5C master socket & MK4 filter.

 
The master socket arrived yesterday, and I have replaced the old master socket with a brand new NTE5C and a new MK4 faceplate. One thing I noted was that the black and green wires were used, can I use orange and white in case there is an issue with the green and black pair or will that be dead?
 

I put the Vigor 130 back in and thought everything was great.. few hours later the WAN drops were back. This time however, I am not sure if the VDSL connection is dropping on the Vigor 130 - I never manage to catch it being down, and it is hard to see from any stats what the VDSL uptime is.

 
The WAN was down multiple times in the early hours a couple of days ago, so I put the HG612 back in and the WAN is more steady, however I had another drop this morning.

Anything else I can test or check? The ISP are insisting I'll likely be charged if an engineer comes out, as they can find no fault on the line. I dunno what else I can check though!

Cheers!
« Last Edit: February 25, 2018, 11:28:11 AM by psykix »
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5717
Re: Line drops.
« Reply #1 on: February 25, 2018, 03:03:35 PM »

Welcome to the forum.

The guys may ask you to provide your connection statistics, if at all possible, but from an engineering perspective I am curious as to why the circuit is connected on the green/black wires ??

We have a set way of connecting 'pairs of wires', based around their colour code.

Pair 1 is the orange/white and if your premises has just the one circuit then it should be this pair of wires connected to the master socket. If an EU required a second line, then we would send it down the green/black pair of wires.

So, I am left wondering if pair 1 has been subject to a fault historically, and the engineer made use of pair 2 to resolve the issue ?? Which begs the next question, is your premises fed overhead via a telegraph pole, or is it an underground feed ??
If it is overhead, does the wire bounce through any foliage such as trees, bushes ??

PS - you couldn't just connect pair 1 to the master socket without connecting it at the other end as well, ie: at the top of the telegraph pole ...... not something you want to be doing.  ;) :) 

Logged

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #2 on: February 25, 2018, 03:15:21 PM »

Hiya,

I've been on the forum a while, but not posted!

I have no idea why it is on the green and black wires!

It is fed from underground. I did have 2 ADSL lines at one stage, and had them channel bonded on a Draytek Router, but that's going back to before I have FTTC which has been several years ago now.

This morning when the line dropped, I changed the RJ11 cable on the HG612 for the one that came with the Draytek, and it's been solid since.

I'm not convinced that there isn't an underlying issue though, as I can't use the Vigor 130 at all - it doesn't stay up anywhere near as long as the HG612.

I'm not sure how to get any stats from the line, but hopefully someone can point me in that direction.

Thanks for your reply!

Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5717
Re: Line drops.
« Reply #3 on: February 25, 2018, 03:36:39 PM »

Aha, that probably answers why it is on the green/black .... with you having two lines previously.

Harvesting stats is not my forte I'm afraid .... but there's plenty on here who will guide you through it.  :)
Logged

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #4 on: February 26, 2018, 11:13:33 AM »

I've set up MDWS, username is psykix

Be good if someone could take a look once it has been running a while.

Line has not dropped since yesterday morning - I note that interleaving is on the line, it never used to be as far as I am aware.
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: Line drops.
« Reply #5 on: February 26, 2018, 04:31:44 PM »

Yes, your stat's are clocking up nicely on MDWS, definately the way to go, you seem to be running DSLStats on a PC, obviously it's much more benificial if you can keep the system running 24/7, no gaps on MDWS trends.
I'am sure some of the very knowledgable forum members will be more than willing to offer support on any issues that may become apparent as the stat's history builds up.

From observation of my line and other MDWS subscriber lines, there is always DS interleaving applied when DS G.Inp is active, yours is very low @ 8 with DS INP @ 54, fairly typical of retx high profile, if the line was on retx low profile then DS interleaving would be higher and DS INP lower, in the case of my line, 16 & 45, have always found INP to be < 50 when on retx low profile.
The product of retx low/high profiles are DS data throughput ratio's of approx. 97 & 91% respectively, ie., higher DS data speed for any given DS synch speed when on retx low profile.

As stated, my opinions are from observations only, I'am sure other forum members will be able to offer much more technical insight on your line stat's as they build up.
Logged
BT FTTP 150/30, BT Smart Hub 2

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Line drops.
« Reply #6 on: February 26, 2018, 05:18:46 PM »

I've taken a quick look at the Hlog and QLN plots for your circuit. Together they show that there is nothing wrong with the physical state of the circuit. There might be a little cross-talk present but nothing really significant. I can see nothing that would warrant the visit of an Openreach technician.

Once sufficient data has been harvested and uploaded to the MDWS server, I'm sure one of or more experienced analysts will examine the information and provide an opinion upon what can be seen.
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.

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #7 on: February 26, 2018, 06:36:08 PM »

Excellent - PC is on 24/7 but I may move the software onto my Windows server and run it from there.

I guess if it stays stable then the question is what is the issue with the Vigor 130..

If DSLStats supports the Vigor 130, then I guess the next option is to switch that in and see what happens?

I've ordered a RJ11 to RJ45 twisted pair cable, as I am using a flat RJ11 cable that came with the Vigor 130.

I'll leave everything as is for a while first though.

Cheers :-)
Logged

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #8 on: February 26, 2018, 06:37:04 PM »

One thing to note though, is that I have never seen interleaving on my line before, it's always been fastpath.

I must admit, I have no clue what most of the above posts actually mean!! I have a background in network infrastructure and servers, but VDSL is all new to me at the technical level!


« Last Edit: February 26, 2018, 06:40:12 PM by psykix »
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: Line drops.
« Reply #9 on: February 26, 2018, 08:48:19 PM »

One thing to note though, is that I have never seen interleaving on my line before, it's always been fastpath.

I must admit, I have no clue what most of the above posts actually mean!! I have a background in network infrastructure and servers, but VDSL is all new to me at the technical level!

Wouldn't worry about the small amount of DS interleaving you have, if DLM decides to change your retx profile to low which is quite possible then your DS interleaving level will increase but your DS INP will decrease.
My line has never seen DS interleaving level less than 4 since G.Inp was deployed and always higher, 8 or 16 when DLM decides to apply retx low profile.

Keep monitoring the forum posts and browse the excellent forum help pages compiled by kitz, with your background you will soon pick up the processes and language associated with DSL.
Logged
BT FTTP 150/30, BT Smart Hub 2

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #10 on: February 27, 2018, 12:15:42 AM »

I've just had a connection drop around midnight or just after  if someone could take a look.

Something is not quite right, but no idea what!
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Line drops.
« Reply #11 on: February 27, 2018, 12:58:24 AM »

Would you please explain what it is you are noticing when you report "line drop(s)".

Is it a loss of synchronisation between your modem and the DSLAM? Is it a loss of the PPP session between your router and IDNet's equipment? Or something else?

By expanding the SNRM plot I can see that there was a five minute interval, from 0007 to 0012 hours, when no data appears to have been uploaded to the MDWS server . . .
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.

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #12 on: February 27, 2018, 05:34:59 AM »

I'm not sure. I was in bed at the time, and my phone showed a loss of internet connection although I was still connected to the wireless network.

Thinkbroadband shows 100% packet loss for the same period of time.

I think the modem retrained looking at the stats - but I am in the dark and not sure what I am looking for.

Code: [Select]
# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status:   0
Max:    Upstream rate = 22525 Kbps, Downstream rate = 76340 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 77047 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):        3.3             7.2
Attn(dB):        17.1            0.0
Pwr(dBm):        14.0            7.3
                        VDSL2 framing
                        Bearer 0
MSGc:           -6              20
B:              243             239
M:              1               1
T:              0               64
R:              10              0
S:              0.1008          0.3819
L:              20150           5028
D:              8               1
I:              254             120
N:              254             240
Q:              8               0
V:              0               0
RxQueue:                85              0
TxQueue:                17              0
G.INP Framing:          18              0
G.INP lookback:         17              0
RRC bits:               0               24
                        Bearer 1
MSGc:           154             -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              6.4000          0.0000
L:              40              0
D:              3               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0
                        Counters
                        Bearer 0
OHF:            0               1147430
OHFErr:         0               12
RS:             1947970536              1540227
RSCorr:         7026            0
RSUnCorr:       0               0
                        Bearer 1
OHF:            9836949         0
OHFErr:         0               0
RS:             98368871                0
RSCorr:         0               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         1014061         40
rtx_c:          75              373
rtx_uc:         96900           169660

                        G.INP Counters
LEFTRS:         20              99
minEFTR:        77027           19997
errFreeBits:    423255364               59563909

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1936287516              0
Data Cells:     1623547704              0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             22              10
SES:            21              0
UAS:            153             132
AS:             158006

                        Bearer 0
INP:            54.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            6.13
OR:             0.01            33.91
AgR:            77125.50        20033.74

                        Bearer 1
INP:            4.50            0.00
INPRein:        4.50            0.00
delay:          3               0
PER:            16.06           0.01
OR:             79.68           0.01
AgR:            79.68   0.01

Bitswap:        46347/46347             813/813

#

Code: [Select]
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status:   0
Max:    Upstream rate = 22479 Kbps, Downstream rate = 76340 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 77047 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):        3.3             7.2
Attn(dB):        17.1            0.0
Pwr(dBm):        14.0            7.3
                        VDSL2 framing
                        Bearer 0
MSGc:           -6              20
B:              243             239
M:              1               1
T:              0               64
R:              10              0
S:              0.1008          0.3819
L:              20150           5028
D:              8               1
I:              254             120
N:              254             240
Q:              8               0
V:              0               0
RxQueue:                85              0
TxQueue:                17              0
G.INP Framing:          18              0
G.INP lookback:         17              0
RRC bits:               0               24
                        Bearer 1
MSGc:           154             -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              6.4000          0.0000
L:              40              0
D:              3               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0
                        Counters
                        Bearer 0
OHF:            0               2244765
OHFErr:         0               12
RS:             2212812872              3045517
RSCorr:         7371            0
RSUnCorr:       0               0
                        Bearer 1
OHF:            10254256                0
OHFErr:         0               0
RS:             102541945               0
RSCorr:         0               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         1014067         40
rtx_c:          81              373
rtx_uc:         96900           169660

                        G.INP Counters
LEFTRS:         20              99
minEFTR:        77042           19997
errFreeBits:    431131456               59563909

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    2929446066              0
Data Cells:     1656770197              0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             22              10
SES:            21              0
UAS:            153             132
AS:             164709

                        Bearer 0
INP:            54.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            6.13
OR:             0.01            33.91
AgR:            77125.50        20033.74

                        Bearer 1
INP:            4.50            0.00
INPRein:        4.50            0.00
delay:          3               0
PER:            16.06           0.01
OR:             79.68           0.01
AgR:            79.68   0.01

Bitswap:        48476/48476             847/847

Total time = 1 days 16 hours 48 min 0 sec
FEC:            18882           76
CRC:            1163            12
ES:             22              10
SES:            21              0
UAS:            153             132
LOS:            2               0
LOF:            20              0
LOM:            0               0
Latest 15 minutes time = 3 min 0 sec
FEC:            11              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:            52              0
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 = 16 hours 48 min 0 sec
FEC:            2502            0
CRC:            0               2
ES:             0               2
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            3807            0
CRC:            0               9
ES:             0               7
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 1 days 21 hours 45 min 9 sec
FEC:            7371            0
CRC:            0               12
ES:             0               10
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
#
« Last Edit: February 27, 2018, 07:26:36 AM by psykix »
Logged

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #13 on: February 27, 2018, 06:31:17 AM »

Here's the log from my Ubiquiti USG for the same time.

I've removed my static IP.

Code: [Select]
Feb 27 00:08:30 UniFiSecurityGateway pppd[4668]: Serial link appears to be disconnected.
Feb 27 00:08:30 UniFiSecurityGateway zebra[684]: interface pppoe0 index 9 changed <POINTOPOINT,NOARP,MULTICAST>.
Feb 27 00:08:31 UniFiSecurityGateway zebra[684]: interface pppoe0 mtu changed from 1492 to 1500
Feb 27 00:08:35 UniFiSecurityGateway ntpd[25869]: ntpd exiting on signal 15
Feb 27 00:08:36 UniFiSecurityGateway pppd[4668]: Connection terminated: no multilink.
Feb 27 00:08:36 UniFiSecurityGateway zebra[684]: interface pppoe0 index 9 deleted.
Feb 27 00:08:36 UniFiSecurityGateway pppd[4668]: Modem hangup
Feb 27 00:08:37 UniFiSecurityGateway ntpd[10311]: ntpd 4.2.6p2@1.2194-o Wed Sep 27 04:27:31 UTC 2017 (1)
Feb 27 00:08:37 UniFiSecurityGateway ntpd[10312]: proto: precision = 48.346 usec
Feb 27 00:08:39 UniFiSecurityGateway ntpd_intres[10317]: host name not found: 0.ubnt.pool.ntp.org
Feb 27 00:09:41 UniFiSecurityGateway ntpd_intres[10317]: host name not found: 0.ubnt.pool.ntp.org
Feb 27 00:09:42 UniFiSecurityGateway pppd[4668]: Timeout waiting for PADO packets
Feb 27 00:10:57 UniFiSecurityGateway pppd[4668]: Timeout waiting for PADO packets
Feb 27 00:11:43 UniFiSecurityGateway ntpd_intres[10317]: host name not found: 0.ubnt.pool.ntp.org
Feb 27 00:12:12 UniFiSecurityGateway pppd[4668]: Timeout waiting for PADO packets
Feb 27 00:12:12 UniFiSecurityGateway pppd[4668]: Connected to 28:8a:1c:e9:a9:4b via interface eth0
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 index 10 <POINTOPOINT,NOARP,MULTICAST> added.
Feb 27 00:12:12 UniFiSecurityGateway pppd[4668]: Connect: ppp0 <--> eth0
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1500 to 1492
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1492 to 1500
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1500 to 1492
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1492 to 1500
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1500 to 1492
Feb 27 00:12:12 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1492 to 1500
Feb 27 00:12:13 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1500 to 1492
Feb 27 00:12:13 UniFiSecurityGateway zebra[684]: interface ppp0 mtu changed from 1492 to 1500
Feb 27 00:12:13 UniFiSecurityGateway pppd[4668]: CHAP authentication succeeded
Feb 27 00:12:13 UniFiSecurityGateway pppd[4668]: peer from calling number 28:8A:1C:E9:A9:4B authorized
Feb 27 00:12:13 UniFiSecurityGateway pppd[4668]: Unsupported protocol 'IPv6 Control Protovol' (0x8057) received
Feb 27 00:12:13 UniFiSecurityGateway zebra[684]: warning: PtP interface ppp0 with addr xxx.xxx.xxx.xxx/32 needs a peer address
Feb 27 00:12:13 UniFiSecurityGateway zebra[684]: interface index 10 was renamed from ppp0 to pppoe0
Feb 27 00:12:13 UniFiSecurityGateway zebra[684]: interface pppoe0 mtu changed from 1500 to 1492
Feb 27 00:12:14 UniFiSecurityGateway pppd[4668]: local  IP address xxx.xxx.xxx.xxx
Feb 27 00:12:14 UniFiSecurityGateway pppd[4668]: remote IP address 212.69.63.54
Feb 27 00:12:14 UniFiSecurityGateway zebra[684]: interface pppoe0 index 10 changed <UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>.
Logged

psykix

  • Member
  • **
  • Posts: 15
Re: Line drops.
« Reply #14 on: February 27, 2018, 07:47:58 AM »

Hmm.. Just got an alert that I was not uploading anything for the last 20 min to MDWS.

Looking at DSLStats, it is reporting No data returned in latest sample?

edit: I had to reboot the modem to get the stats working again. Weird.
« Last Edit: February 27, 2018, 08:28:28 AM by psykix »
Logged
Pages: [1] 2
 

anything