Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: michty_me on June 06, 2018, 07:49:51 PM

Title: Stat check on my line please
Post by: michty_me on June 06, 2018, 07:49:51 PM
Evening all,

I was wondering if I could pester you for a few minutes of your time to check the condition of my line.
A brief history of the issue I've been having:
I had a D7000 fitted to my MK3 faceplate and it was up and running for pretty much two years without a glitch. Infact, My stats kept getting better throughout this time. It was only ever reset after firmware updates.

I was working away around christmas and when I can home my D7000 had frozen but unsure for how long. I reset it and it came back online with around 17/12 which was a fair hit from 74/19. Over the next few days DLM increased my speeds but stopped at 49/15 roughly for possibly 9 weeks or so. I think it was banded going by the sync speeds.
I spoke to Zen who sent out an engineer who said I had a very clean line, Changed to a MK4 faceplate and reset my line. After a week G.inp was back on, I had very few errors and sync was around 69/17 from then on.

Roughly every month my D7000 would lock up but I was home to reboot it until a few weeks ago when I went away for a long weekend. I returned to it locked up and upon rebooting it appears my line is banded again (Stats incoming). I have since downgraded my firmware to when I know I had no issues.

So after that wall of text, Can anyone see any obvious errors as to why my line may not be unbanded in the future. I'm just checking to see if anything requires fixing so I'm not waiting for ages for no improvement.

Stats are here and I'm connected to a Huawei cabinet. To me it looks quite clean with only 1 ES in the 12 days uptime. Not too sure if anything is obvious to the more experienced of users?
Code: [Select]
adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 17841 Kbps, Downstream rate = 60510 Kbps
Bearer: 0, Upstream rate = 17000 Kbps, Downstream rate = 54999 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):        7.4             5.6
Attn(dB):        17.2            0.0
Pwr(dBm):        13.6            7.5

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              227             163
M:              1               1
T:              0               0
R:              12              12
S:              0.1319          0.3047
L:              14562           4621
D:              4               2
I:              240             176
N:              240             176
Q:              4               2
V:              0               1
RxQueue:                132             114
TxQueue:                22              19
G.INP Framing:          18              18
G.INP lookback:         22              19
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
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               0
OHFErr:         1               0
RS:             3720368364              4081427
RSCorr:         49270           657590
RSUnCorr:       0               0
                        Bearer 1
OHF:            69602739                667573
OHFErr:         0               0
RS:             556821416               321483
RSCorr:         3               2023
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9924274         17490
rtx_c:          11957           65043
rtx_uc:         3               356428

                        G.INP Counters
LEFTRS:         3               421
minEFTR:        54974           17000
errFreeBits:    937992906               1731511222

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    2283629181              0
Data Cells:     745809946               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:             1               0
SES:            0               0
UAS:            32              32
AS:             1117978

                        Bearer 0
INP:            57.00           57.00
INPRein:        1.00            1.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            55120.28        17156.70

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        36558/39273             33762/33769

Total time = 12 days 22 hours 33 min 30 sec
FEC:            49270           657590
CRC:            1               0
ES:             1               0
SES:            0               0
UAS:            32              32
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Latest 15 minutes time = 3 min 30 sec
FEC:            19              416
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 15 minutes time = 15 min 0 sec
FEC:            43              2160
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           N/A
Latest 1 day time = 22 hours 33 min 30 sec
FEC:            3131            67211
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 1 day time = 24 hours 0 sec
FEC:            2931            60590
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Since Link time = 12 days 22 hours 32 min 57 sec
FEC:            49270           657590
CRC:            1               0
ES:             1               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
Title: Re: Stat check on my line please
Post by: burakkucat on June 06, 2018, 08:29:07 PM
I've taken a look and, to me, nothing looks particularly bad. However I suggest that you wait for comments from those more experienced than I in "reading the runes".

One thing did catch my eye --

Total time = 12 days 22 hours 33 min 30 sec
FEC:            49270           657590
CRC:            1               0
ES:             1               0
SES:            0               0
UAS:            32              32
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0


You mentioned that there was just one ES recorded but what about those 32 UAS?  :-\
Title: Re: Stat check on my line please
Post by: johnson on June 06, 2018, 08:35:11 PM
That would be the 32 seconds the modem took to sync, during which the line was unavailable. No?

Edit: Echoing burakkucat, other people know better than I but:

Line looks clean, one thing of note is that you have upstream G.INP, and the retx high variant. So loosing around 8% of throughput:
Code: [Select]
                        Bearer 0
INP:            57.00           57.00
INPRein:        1.00            1.00

But its working well I guess given your near zero error count even after 12 days of connection.
Title: Re: Stat check on my line please
Post by: michty_me on June 06, 2018, 08:42:34 PM
I am unsure what that is but according to this link

https://kitz.co.uk/adsl/linestats_errors.htm

UAS - Unavailable seconds

    Ten consecutive SES's will trigger a UAS event, and will remove the path from use. The path will become usable again after 10 consecutive seconds with no SES.

    A count of UAS events can be triggered by a LOS event and will continue to accrue for each second that the system is up and the path is unavailable.
Title: Re: Stat check on my line please
Post by: spring on June 06, 2018, 09:05:49 PM
My VDSL2 AnnexB syncs on ECI have usually, and best seen, 26 UAS, which is like that from sync and doesn't change over months, but it would be 0.001% kind of differences.
I also think some number of UAS [non 0] will 99% be there, or maybe I'm wishful thinking.

Code: [Select]
ES:             0               0
SES:            0               0
UAS:            26              26
AS:             288435

Edit: My previous ADSL2 line synced in around half the time as VDSL and had 10-15 UAS so what Johnson said makes sense in terms of the UAS that is there right after a sync.

Edit2: But I honestly think it's just the unavailable seconds for use by the line, and that it probably synced at 32.

Edit3:
Quote
Unavailable Seconds (UAS)

Unavailable Seconds are calculated by counting the number of seconds that the interface is unavailable. The DS1 interface is said to be unavailable from the onset of ten contiguous SESs, or the onset of the condition leading to a failure (see Failure States). If the condition leading to the failure was immediately preceded by one or more contiguous SESs, then the DS1 interface unavailability starts from the onset of these SESs. Once unavailable, and if no failure is present, the DS1 interface becomes available at the onset of ten contiguous seconds with no SESs. Once unavailable, and if a failure is present, the DS1 interface becomes available at the onset of 10 contiguous seconds with no SESs, if the failure clearing time is less than or equal to ten seconds. If the failure clearing time is more than ten seconds, the DS1 interface becomes available at the onset of ten contiguous seconds with no SESs, or the onset period leading to the successful clearing condition, whichever occurs later. With respect to the DS1 error counts, all counters are incremented while the DS1 interface is deemed available. While the interface is deemed unavailable, the only count that is incremented is UASs.

A special case exists when the ten or more second period crosses the 900 second statistics window boundary, as the foregoing description implies that the Severely Errored Second and Unavailable Second counters must be adjusted when the Unavailable Signal State is entered. Successive "gets" of the affected dsx1IntervalSESs and dsx1IntervalUASs objects will return differing values if the first get occurs during the first few seconds of the window. This is viewed as an unavoidable side-effect of selecting the presently-defined managed objects.
Title: Re: Stat check on my line please
Post by: burakkucat on June 06, 2018, 09:24:28 PM
That would be the 32 seconds the modem took to sync, during which the line was unavailable. No?

Ah, yes. That would be it.
Title: Re: Stat check on my line please
Post by: spring on June 06, 2018, 09:39:48 PM
Other users here have locking up routers and in my country the ISP routers [bad ones] on some "rarer" mishaps, could somehow work fine the first few months and then stop working or aren't what they used to be in whatever way.
So if your power supply is good and anything possibly related is in order, it could be that the router spontaneously [or wearing off from certain factors], started acting up.
In terms of software if this first started after a firmware upgrade that didn't have some months without problems, then maybe you can revert to a firmware you had no problems with, and I recommend regenerating the config by completely resetting it if you did revert firmware.
About what you can improve, I can name just one xD, if your DSL cable is 0.3m or 0.5m that is the best length [ofc if you can do with that length]. You can see a few recommended names & types here: https://forum.kitz.co.uk/index.php/topic,20119.msg353430.html#msg353430
Title: Re: Stat check on my line please
Post by: sotonsam on June 06, 2018, 09:49:54 PM
I think your stats in the main look good. Obviously the router issues you were having hit your line hard, I wonder if it kept crashing and restarting prior to the lockup? (hence why DLM took such drastic action on your sync speed).

It seems to have recovered it though. See how it goes over the coming weeks as you may still see slight improvements, there aren't any obvious issues with the line that would be impacting you anymore. Just make sure you either replace the router or get yourself a UPS protection (if it was power surges knocking it on/off)
Title: Re: Stat check on my line please
Post by: michty_me on June 06, 2018, 09:58:46 PM
The line has never had rtx high before I don't think. It usually sits happily at a 3dB profile with very minor errors.
Every time the router has locked up, It has just locked up out of the blue. I'm noticing quite a few D7000 users reporting the same thing.
Every time I upgraded the firmware, I always disconnected it from the faceplate, Carried out a firmware upgrade then Restored to factory settings and re-entered all the information manually WITHOUT using a config file.
The firmware I reverted to previously was an early beta I was sent from Netgear engineers to test out a feature they added (Can't remember what) but I remember it being very stable and up for months. Luckily I saved them all  ;D
I do have a Zyxel on order also as a backup for if it hangs up again then I'll start the waiting period.

As long as the line has no noticeable errors then I shall see what happens once I start approaching the time frame it starts tripping over itself.
Title: Re: Stat check on my line please
Post by: re0 on June 07, 2018, 01:24:07 PM
Seems I am a little bit late to the party in this instance. :-[

As you've said, it looks like you've got some banding going on, or at least certainly for the downstream as your SNRM is above the typical target:
Bearer: 0, Upstream rate = 17000 Kbps, Downstream rate = 54999 Kbps
. . .
                Down            Up
SNR (dB):        7.4             5.6
I wouldn't be too shocked, as I imagine this was down to the modem locking up.

Otherwise, stats seem to be pretty much in check.

As @johnson said, you have a high level of G.INP which will be responsible for a small loss of throughput.

There are some redundant bytes that should also equate to a very small overhead (if the connection was not already banded):
                        VDSL2 framing
                        Bearer 0
. . .
R:              12              12
It seems to be doing its job, though:
                        Counters
                        Bearer 0
. . .
RS:             3720368364              4081427
RSCorr:         49270           657590
RSUnCorr:       0               0

Sorry if I've repeated what you already knew.
Title: Re: Stat check on my line please
Post by: j0hn on June 07, 2018, 01:27:20 PM
Quote
The line has never had rtx high before I don't think. It usually sits happily at a 3dB profile with very minor errors.

Almost all lines on a 3dB SNRM target (or any sub 6dB target) are set to retx high, so you probably just didn't notice this.

The way DLM works it's very unlikely your line will ever drop to a lower SNRM target again (unless reset).

Now that you have removed the problem modem I would try contacting your ISP and see if they are able to perform a remote DLM reset. The line would be back at 3dB in just over a week.
Title: Re: Stat check on my line please
Post by: michty_me on June 07, 2018, 02:00:14 PM
Thank you both for a little further insight.
I may have been thinking back to before I was dropped down to a 3dB profile. My mistake.

I'm not overly convinced yet that the modem issue is fixed as I'm still using the D7000 as a combi until the Zyxel appears. I want to ensure that it remains stable for some time before contacting Zen (Are they part of the remote DLM reset trial?) so I don't end up in the same situation again in a month or two.
I was partly tempted to leave the D7000 connected for the next 64 days to see how it copes and to see if the lower SNRM is reached on its own assuming it doesn't lock up again with the old firmware, but that doesn't sound hopeful now.

One thing I did recall whilst out for my lunchtime stroll was that for a while recently DLM was coming in every week and slightly adjusting my line either up or down in speeds. Maybe by only a few hundred kbps sometimes. I did wonder if the D7000 would hang sometimes on one of these re-sync. This appeared to have calmed down over the past few months though.

Edit: Just logged into my Zen account and checked the line data. It shows as having a Sync at 23:45 on the 4th of June but as per my stats yesterday, That does not show and also doesn'y show on DSLStats this happened. Unless that is for something else?
Title: Re: Stat check on my line please
Post by: michty_me on June 08, 2018, 07:14:11 AM
Looks like DLM has made a slight adjustment and adjusted the INP level on the Upstream from 57.00 down to 47.00

Small changes, Slowly but surely hopefully.
Title: Re: Stat check on my line please
Post by: Weaver on June 08, 2018, 01:18:29 PM
@michty_me  Would you be interested in posting up your QLN and bits-per-bin aka bits-per-tone aka bit-loading too? I forget what the magic runes are in the Broadcom-oriented CLI but I am sure someone will remind us if necessary.

I have to say, it looks very good, apart from what johnson said about the upstream, clearly it is needing some help there as it must be getting a good amount of noise in that band, perhaps regular spikes closely spaced in time to cause the high ReTX setting?

(Does high retx mean short DTNs? So that there is a significant overhead from per-DTN headers eg seq number, crc any other fields? I do need to go off and read the standards doc again as it all has gone out of my head.)
Title: Re: Stat check on my line please
Post by: michty_me on June 08, 2018, 03:25:11 PM
Yeah I have no problem doing that. It will have to be later/tomorrow as I'm away out with a friend shortly for some beers in the sun  ;D

Edit: Is this what you require?

(http://i.imgur.com/lP1CWkx.jpg)

(http://i.imgur.com/2UK6UWC.jpg)
Title: Re: Stat check on my line please
Post by: j0hn on June 08, 2018, 03:40:33 PM
You need to click on "change tone range" and extend it till it all fits.
That's only a tiny portion of the tones in use.
Title: Re: Stat check on my line please
Post by: michty_me on June 08, 2018, 03:53:57 PM
Apologies, I've edited the post with the graphs.
Title: Re: Stat check on my line please
Post by: Weaver on June 09, 2018, 03:02:11 PM
What would I know but nothing out of the ordinary there. Is see two big noise spikes in the low ADSL tones, below 250, I assume that their presence doesn't matter ? The result has the shape I have seen before, v-shaped notch determined by tx power cutback restrictions.
Title: Re: Stat check on my line please
Post by: michty_me on June 09, 2018, 04:26:23 PM
That's more than I would know anyway!!
I don't seem to be getting many errors anyway so I guess it seems happy enough.
Title: Re: Stat check on my line please
Post by: Weaver on June 09, 2018, 04:53:30 PM
See the two big vertical up-going spikes on the QLN graph. I didn't mean that this was a problem, certainly not, you have managed to avoid it somehow. To me, it all looks brilliant.

A line that good ( = short ) is only a dream.
Title: Re: Stat check on my line please
Post by: michty_me on June 09, 2018, 05:26:49 PM
So going by that I think it was the Netgear D7000 hanging up causing my issues. Still not received the ZyXel yet though. Hopefully it arrives monday or tuesday.
Title: Re: Stat check on my line please
Post by: michty_me on June 13, 2018, 06:52:55 AM
I had another retrain last night. Am I right in saying that G.Inp has been removed from the upstream or have I read that incorrectly?

Code: [Select]
adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 15314 Kbps, Downstream rate = 60353 Kbps
Bearer: 0, Upstream rate = 15314 Kbps, Downstream rate = 54999 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):        7.4             6.2
Attn(dB):        17.3            0.0
Pwr(dBm):        13.6            7.4

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              24
B:              227             237
M:              1               1
T:              0               64
R:              12              16
S:              0.1319          0.4944
L:              14562           4110
D:              4               1
I:              240             127
N:              240             254
Q:              4               0
V:              0               0
RxQueue:                130             0
TxQueue:                26              0
G.INP Framing:          18              0
G.INP lookback:         26              0
RRC bits:               0               24
                        Bearer 1
MSGc:           122             -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              8.0000          0.0000
L:              32              0
D:              1               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               1791822
OHFErr:         0               7
RS:             428300336               2995241
RSCorr:         258             55
RSUnCorr:       0               0
                        Bearer 1
OHF:            882427          0
OHFErr:         0               0
RS:             7058926         0
RSCorr:         0               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9939560         24603
rtx_c:          18930           71911
rtx_uc:         151728          356428

                        G.INP Counters
LEFTRS:         26              424
minEFTR:        54996           16996
errFreeBits:    3835279091              1871744164

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1499153275              0
Data Cells:     314599          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:             23              7
SES:            21              0
UAS:            118             97
AS:             14174

                        Bearer 0
INP:            54.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            7.94
OR:             0.01            30.22
AgR:            55120.28        15344.47

                        Bearer 1
INP:            2.00            0.00
INPRein:        2.00            0.00
delay:          0               0
PER:            16.06           0.01
OR:             63.75           0.01
AgR:            63.75   0.01

Bitswap:        1014/1125               247/247

Total time = 19 days 8 hours 55 min 3 sec
FEC:            92882           779038
CRC:            1179            7
ES:             23              7
SES:            21              0
UAS:            118             97
LOS:            2               0
LOF:            18              0
LOM:            0               0
Retr:           2
Latest 15 minutes time = 10 min 3 sec
FEC:            51              1
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 15 minutes time = 15 min 0 sec
FEC:            8               2
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           N/A
Latest 1 day time = 8 hours 55 min 3 sec
FEC:            1070            722
CRC:            586             7
ES:             11              7
SES:            11              0
UAS:            44              33
LOS:            1               0
LOF:            10              0
LOM:            0               0
Retr:           1
Previous 1 day time = 24 hours 0 sec
FEC:            4166            6818
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Since Link time = 3 hours 56 min 13 sec
FEC:            258             55
CRC:            0               7
ES:             0               7
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
Title: Re: Stat check on my line please
Post by: j0hn on June 13, 2018, 12:19:57 PM
That's correct and as expected.
Title: Re: Stat check on my line please
Post by: michty_me on June 13, 2018, 12:32:08 PM
That's correct and as expected.

Thanks for confirming. Still trying to get my head round all this again. Do you think I will continue seeing small minor adjustments as DLM monitors the line for stability?
Title: Re: Stat check on my line please
Post by: j0hn on June 13, 2018, 07:59:48 PM
It might drop from retransmission high to retransmission low next. If it does that would be the final change I would expect.
Title: Re: Stat check on my line please
Post by: michty_me on June 13, 2018, 08:59:37 PM
Ok thanks. Will just keep an eye on it. Mainly more interested in seeing if the D7000 will play up soon after the firmware downgrade.
Spoke to zen and it appears they are part of the remote DLM counter reset.
Title: Re: Stat check on my line please
Post by: j0hn on June 13, 2018, 09:41:57 PM
I highly recommend requesting 1 once your confident any hardware issues are fixed.

Banding gets completely stuck in a large percentage of cases.
Within a fortnight of a DLM reset you would more than likely be back up in the low-mid 70's.
Title: Re: Stat check on my line please
Post by: michty_me on June 13, 2018, 10:05:59 PM
Thanks John. They advised me to go away and do checks as they said it looked like there were a lot of errors on the line so they didn't want to request it right away.
Title: Re: Stat check on my line please
Post by: spring on June 13, 2018, 10:54:32 PM
I'd say do the reset 2 weeks after you've installed the zyxel and not prior
Title: Re: Stat check on my line please
Post by: michty_me on June 14, 2018, 07:08:32 AM
I'd say do the reset 2 weeks after you've installed the zyxel and not prior

That makes sense Spring. I'll do just that.
Title: Re: Stat check on my line please
Post by: michty_me on June 21, 2018, 07:26:13 PM
I've had another re-sync yesterday which re-added the G.Inp on my upstream.

One thing I've noticed it the following:
                     Bearer 0
INP:            57.00           47.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            55120.28        17086.26

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Is this something to be concerned about or indicate any possible issue?

Edit: I've chucked a couple of clip on ferrite cores to see if it will limit and possibly noise although I'm uncertain. It appears that the noise is coming from the modem PSU using the radio set at 612Khz. I disconnected everything else and it was still audible from 1-1.5ft from the power source. I'll be swapping over to the Zyxel hopefully at the weekend when I have some spare time.
Title: Re: Stat check on my line please
Post by: flood on June 22, 2018, 12:48:16 AM
I've had another re-sync yesterday which re-added the G.Inp on my upstream.

One thing I've noticed it the following:
                     Bearer 0
INP:            57.00           47.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            55120.28        17086.26

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Is this something to be concerned about or indicate any possible issue?

Edit: I've chucked a couple of clip on ferrite cores to see if it will limit and possibly noise although I'm uncertain. It appears that the noise is coming from the modem PSU using the radio set at 612Khz. I disconnected everything else and it was still audible from 1-1.5ft from the power source. I'll be swapping over to the Zyxel hopefully at the weekend when I have some spare time.

INP Rein shows whether you're on retransmission high or low.
INP Rein 1 = High

Your IP Profile will be 91/92% of your sync speed when on retransmission high.
Title: Re: Stat check on my line please
Post by: j0hn on June 22, 2018, 05:53:13 AM
To add to that it's the Bearer 0 INPRein that indicates with certainty if a line is retx low/High.
Title: Re: Stat check on my line please
Post by: michty_me on June 22, 2018, 06:50:35 AM
Thank you folks.
That's the first time I've seen it with a value on my line before so was a bit curious.
Title: Re: Stat check on my line please
Post by: michty_me on June 22, 2018, 06:14:18 PM
Ok, So I returned home and the D7000 had locked up again. A firmware roll back done nothing so it was the perfect opportunity to get the new Zyxel on.

D7000 stats from when it locked up this afternoon.

Code: [Select]
adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 17373 Kbps, Downstream rate = 60766 Kbps
Bearer: 0, Upstream rate = 16999 Kbps, Downstream rate = 54999 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):        7.4             6.1
Attn(dB):        17.3            0.0
Pwr(dBm):        13.7            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              227             146
M:              1               1
T:              0               0
R:              12              16
S:              0.1319          0.2742
L:              14562           4755
D:              4               4
I:              240             163
N:              240             163
Q:              4               4
V:              0               1
RxQueue:                132             44
TxQueue:                22              11
G.INP Framing:          18              18
G.INP lookback:         22              11
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             1091620380              1284485
RSCorr:         8624            53710
RSUnCorr:       0               0
                        Bearer 1
OHF:            11097276                654708
OHFErr:         0               0
RS:             88777712                1612200
RSCorr:         0               1639
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9955342         28866
rtx_c:          26198           76174
rtx_uc:         221284          356428

                        G.INP Counters
LEFTRS:         38              428
minEFTR:        54989           16996
errFreeBits:    2113429317              1917910906

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1673176745              0
Data Cells:     47058904                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:             33              7547
SES:            31              0
UAS:            160             129
AS:             178248

                        Bearer 0
INP:            57.00           47.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            55120.28        17086.26

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        5328/5823               5478/5478

Total time = 28 days 11 hours 11 min 41 sec
FEC:            122000          841260
CRC:            1719            8026
ES:             33              7547
SES:            31              0
UAS:            160             129
LOS:            3               0
LOF:            26              0
LOM:            0               0
Retr:           3
Latest 15 minutes time = 11 min 41 sec
FEC:            11              209
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 15 minutes time = 15 min 0 sec
FEC:            67              446
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           N/A
Latest 1 day time = 11 hours 11 min 41 sec
FEC:            1863            10305
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Previous 1 day time = 24 hours 0 sec
FEC:            3964            21068
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
Since Link time = 2 days 1 hours 30 min 47 sec
FEC:            8624            53710
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Retr:           0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
#
#


Zyxel 1312-B10A stats

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 17567 Kbps, Downstream rate = 62682 Kbps
Bearer: 0, Upstream rate = 16999 Kbps, Downstream rate = 54999 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):        7.9             5.9
Attn(dB):        18.1            0.0
Pwr(dBm):        13.6            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              227             146
M:              1               1
T:              0               0
R:              12              16
S:              0.0000          0.0000
L:              14562           4755
D:              4               4
I:              240             163
N:              240             163
Q:              4               4
V:              0               1
RxQueue:                130             45
TxQueue:                26              15
G.INP Framing:          18              18
G.INP lookback:         26              15
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             117130604               721285
RSCorr:         31              4505
RSUnCorr:       0               0
                        Bearer 1
OHF:            241369          242354
OHFErr:         0               0
RS:             1930459         969418
RSCorr:         0               61
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9955871         144
rtx_c:          7               76865
rtx_uc:         0               372387

                        G.INP Counters
LEFTRS:         0               433
minEFTR:        54989           16996
errFreeBits:    3252782         1922852515

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    410061537               0
Data Cells:     508981          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:             0               0
SES:            0               0
UAS:            23              23
AS:             3878

                        Bearer 0
INP:            54.00           48.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            55120.28        17086.26

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        10/10           126/126

Total time = 1 hours 5 min 1 sec
FEC:            31              4505
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            23              23
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 5 min 1 sec
FEC:            0               435
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:            7               1747
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 = 1 hours 5 min 1 sec
FEC:            31              4505
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            23              23
LOS:            0               0
LOF:            0               0
LOM:            0               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 4 min 37 sec
FEC:            31              4505
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >
Title: Re: Stat check on my line please
Post by: spring on June 22, 2018, 07:54:10 PM
Is the driver version v.d26a or x1.d26a?
Title: Re: Stat check on my line please
Post by: michty_me on June 22, 2018, 08:10:04 PM
Not sure, I've put away all my cables. It was the firmware with Johnsons adjustment.
Title: Re: Stat check on my line please
Post by: spring on June 22, 2018, 08:51:38 PM
1312-B10A-from-zyxel-jumboframes-3925adsl_phy.bin ?

or 1312-B10A-from-zyxel-jumboframes.bin ?
Title: Re: Stat check on my line please
Post by: michty_me on June 22, 2018, 10:04:50 PM
Just checked. It was the 3925 varient. That was what I was advised to install.
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 08:53:32 AM
That driver is x1 and I've made a post about it & following up on it: https://forum.kitz.co.uk/index.php/topic,21273.msg375848.html#msg375848

Before I can say which was better for me, I need another week.
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 09:10:28 AM
No Problem. I will leave as is for now and await your response and can change if need be.
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 06:28:23 PM
Something has gone a bit weird with my line since installing the Zyxel. Stats taken from the Zyxel itself. Still not got DSLstats working correctly yet.

Code: [Select]
====================================================================================
    VDSL Training Status:   Showtime
                    Mode:   VDSL2 Annex B
            VDSL Profile:   Profile 17a
                G.Vector:   Disable
            Traffic Type:   PTM Mode
             Link Uptime:   0 day: 11 hours: 4 minutes
====================================================================================
       VDSL Port Details       Upstream         Downstream
               Line Rate:     16.987 Mbps       48.996 Mbps
    Actual Net Data Rate:     16.988 Mbps       48.997 Mbps
          Trellis Coding:         ON                ON
              SNR Margin:        5.8 dB            9.5 dB
            Actual Delay:          0 ms              0 ms
          Transmit Power:        7.6 dBm          13.6 dBm
           Receive Power:       -6.5 dBm          -5.5 dBm
              Actual INP:       53.0 symbols      54.0 symbols
       Total Attenuation:        0.0 dB          18.1 dB
Attainable Net Data Rate:     17.496 Mbps       62.859 Mbps
====================================================================================
  VDSL Band Status        U0      U1      U2      U3      U4      D1      D2      D3
  Line Attenuation(dB): 7.2 25.1 37.4   N/A   N/A 13.0 29.5 45.9
Signal Attenuation(dB): 7.2 24.2 36.8   N/A   N/A 16.5 29.2 46.0
        SNR Margin(dB): 5.9 5.8 5.8   N/A   N/A 9.6 9.5 9.5
         TX Power(dBm): 0.6 -18.6 6.6   N/A   N/A 10.8 7.8 7.1
====================================================================================

            VDSL Counters

           Downstream        Upstream
Since Link time = 4 min 17 sec
FEC: 584 4529
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 1 min 33 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
Previous 15 minutes time = 15 min 0 sec
FEC: 3 38
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 = 1 hours 16 min 33 sec
FEC: 143 193
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: 2230 21442
CRC: 542 0
ES: 10 0
SES: 10 0
UAS: 55 45
LOS: 1 0
LOF: 7 0
LOM: 0 0
Total time = 1 days 1 hours 16 min 33 sec
FEC: 2373 21635
CRC: 542 0
ES: 10 0
SES: 10 0
UAS: 55 45
LOS: 1 0
LOF: 7 0
LOM: 0 0
====================================================================================

                 
Title: Re: Stat check on my line please
Post by: burakkucat on June 23, 2018, 06:32:23 PM
Something has gone a bit weird with my line since installing the Zyxel.

What is it, to which you give the "bit weird" description?  :-\
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 06:43:36 PM
It appears I've gained another 2db on the downstream and lost another 6Mb sync speed.
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 07:20:59 PM
Can you post your bitloading graph [should have SNR in it as well]?

May be attributed to x1 driver.
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 07:27:16 PM
Could well be that. I've switched it all off just now as I'm out for the night. I'll investigate tomorrow though.
Can I just ask spring, why in the config screen shots you posted (possibly in another thread) that SRA was set to disabled?
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 07:29:07 PM
Try enabling it after the ZyXEL was turned off & unplugged from DSL, because it might be that you lost sync 11 hours ago. It lowers sync rate in an event that would cause loss of sync, but I first attribute this loss of sync / line problems to the x1 because it's possible from my observation of the x1. The x1 may be more unstable. x1 instabilities are visually seen on the SNR graph.

I disabled it since most ISP's don't support it, and if not supported it's better disabled [some routers don't sync with it enabled when there's no support].
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 07:45:21 PM
I've noticed more errors than normal anyway with the x1 firmware Zyxel compared to my Netgear D7000. I don't think it would have been enough to drop the speed but what do I know.
I need to go through all my kit again, may even start from scratch and see how I get on.
I think I may install that other firmware too.
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 07:46:51 PM
The first day that I changed DSL driver [or in this case between modems] I always had more errors: but the x1 graphs are visible from the start & later on.

I don't understand what there is to go through, and I change v14 firmwares without changing anything else because they have the same configuration.

The SNR graph is the first thing to look at. If you desynced and don't want to resync with the x1 I understand that & don't recommend that either, but we'll never know how the SNR graph looked, how the x1 performed.

Edit: The SNR graph is to identify x1 as the cause, not because it's unlikely to be. If you already desynced then try this one (https://github.com/Olipro/VMG1312-B10A/releases) tomorrow.
Title: Re: Stat check on my line please
Post by: michty_me on June 23, 2018, 08:18:13 PM
Ok, for test purposes and to check out the X1 firmware. I'll get it reconnected when I get home tonight, try and get dslstats working and get any information I can that may help to prove/disprove that there may be an issue.
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 08:22:21 PM
Well, the x1 had days like this:

Code: [Select]
day 10

Latest 1 day time = 2 hours 25 min 56 sec
FEC:            14              0
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:            30              29
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0


but also this:


day 13 or 14

Latest 1 day time = 18 hours 3 min 16 sec
FEC:            13              196
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:            31              281
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

The former is what had me recommending it  :-X

For comparison, what I've got with v is :

Latest 1 day time = 15 hours 33 min 19 sec
FEC:            23              42
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            26              26
LOS:            0               0
LOF:            0               0
LOM:            0               0

Note that one is 15 hours and not 24 like the stats from x1

All that's left is the bitloading+SNR graph for seeing what's behind the issues. Nothing else can directly point at x1, and even if nothing is seen on the SNR graph the next time issues happened x1 would be replaced with v. If something is seen it's with certainty that it was caused by it.


Edit: Right now I'm leaning towards switching to v anyway [linked to in my previous posted - Don't know if I tried Johnson's but Olipro's is flawless so I'm recommending that] but it's interesting if the graphs look the same for you as they do for me - indicating x1 is problematic. I assume nothing about it bothers Johnson: https://forum.kitz.co.uk/index.php/topic,21273.msg375521.html#msg375521 But note he said he has lower downstream: my SNR graphs show the cause - loss of downstream SNR at the last few tones.
Title: Re: Stat check on my line please
Post by: burakkucat on June 23, 2018, 09:47:06 PM
It appears I've gained another 2db on the downstream and lost another 6Mb sync speed.

Ah, now that you have explained I can see it.  :-[

As you appreciate the two parameters are intimately related. It really depends upon the prevailing situation when the ZyXEL device was powered up and allowed to synchronise.

[Edited to fix the typo.]
Title: Re: Stat check on my line please
Post by: j0hn on June 23, 2018, 11:05:13 PM
I recommend you use the xDSL driver that comes with the firmware version you are using.
That's not the 3925 version, as that contains an xDSL driver from another device (the vmg3925).

With you swapping modems for stability reasons to try get DLM to remove the banding on your line this is even more a reason to use the correct xDSL driver.

Must say that's very strange seeing the SNRM go up but the attainable go down like that.
Title: Re: Stat check on my line please
Post by: spring on June 23, 2018, 11:48:41 PM
I think it boils down to what Cisco said about x3 [also x1?]:
Quote
This firmware package is released to meet the requirement of a specific Cisco customer and is not claimed to be a general availability. Other Cisco customers can download and upgrade to this firmware package but Cisco recommends customer to do their own qualification before installing it in production network.
Not 100% sure [and can't be when doing guess work] if the x1 package from 3925 isn't modified/incompatible/doesn't have a good fit, but this explanation makes perfect sense [would be nice to test A2pv6F039w1 but takes a lot of digging for that :D]. I'd also guess the widely used versions are often more stable.

Edit: Also note this
Quote
This release has PHY firmware A2pv6F039x3 for Annex A and DSL driver version 26d.
Interesting if it runs well on the 3925.

Edit2: For DSLStats, check if you did this [and LAN page group name is selected/applied as Default]:
Quote
Click Add New Interface Group which will open a new window.  add new interface group

Group Name:  Bridge
WAN Interfaces used: PTM type > VDSL/ppp1.1
Available LAN Interfaces:  Click LAN1 and move it to the Grouped LAN Interfaces

Click Apply.

or vlan group (https://forum.kitz.co.uk/index.php/topic,20226.msg353554.html#msg353554) [LAN group name applied as: Bridge], or: https://forum.kitz.co.uk/index.php/topic,21517.msg372730.html#msg372730 [bridge ip = 192.168.2.1 by default - can be seen by going to  network setting > home networking > selecting group name: Bridge]
If your router is an asus also try: https://forum.kitz.co.uk/index.php/topic,21508.msg372706.html#msg372706
last resort: https://forum.kitz.co.uk/index.php/topic,14621.msg284717.html#msg284717

LAN cable access = group name: Default [dsl stats set to connect to 192.168.1.1]
WAN cable access = group name: Bridge [dsl stats set to connect to 192.168.2.1]

Edit3: Attached what I think is the cleanest example of x1 [2 days sync] & v [3 days sync] graph differences that I've got so far because of the hour at which it was taken ::). I'm doing this even though x1 was unstable sometimes, because it sometimes worked fine. This x1 graph makes me hope that it would stop behaving this time :o.
About the bitloading entirely missing on some upstream blocks, that didn't happen before, is like that from this sync and I'll see if it happens next time I resynced in a day or two.
About whether to switch to v I'm already saying feel free to do it because of DLM, but if you want to go in details then sure :D
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 12:45:59 PM
See attached bitloading graph.
So should I change to the firmware that Spring linked to further up the thread in post #48 or change to the official release for this unit?
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 01:35:24 PM
Where's the SNR graph? Go to Configurations > Items to monitor   and tick "SNR Per Tone - Include with Bitloading"

Also, disable "Scale snapshots" in the snapshot tab.

If you will change, it would best be what I linked.


Attached this afternoon's snapshot of x1

With bitloading missing from a block of upstream tones, I get this error count:
Latest 1 day time = 8 hours 54 min 27 sec
FEC:            18              298

You don't miss bitloading, however my old logs show high upstream errors as well:
Latest 1 day time = 18 hours 3 min 16 sec
FEC:            13              196

So what I suggest is that you show the snapshot and then get the firmware I linked to, look at the time [32 minutes until next turned on] - turn off the modem from button, unplug DSL cable from it, turn it on & wait 1 minute, flash, wait until it gets you back to the gui, turn it off, turn it on 32 minutes from when you first turned it off

Guess x1 outright sucks for VDSL [I don't know ADSL ::)]. Oh well, at least we don't have to try it in the future now  :lol:
Sorry, I was naive thinking a week was enough to tell it's a good driver  :( And I forgot about the fact I made an affirmation about the not fully tested x1, as 2 weeks passed until your vmg1312 arrived, I guess it was more what I used/called best back then and was meant to be informational [misleading  :fingers:], at the moment of flashing I would have said to not use it as it was not finished testing. Moreover when you flashed I was already seeing the bad side of x1, there wasn't a question asked about it, but I didn't see right to pretend I know for sure that it would not perform well on your line once I saw you flashed to it.

Edit: The x1 package taken from vmg3925 in this firmware may be made for dsl driver d26n, while vmg1312 is d26a - so not necessarily x1 behaves like this, could be this x1 package is made for a dsl driver other than d26a [d26n is not a requirement for correct operation of x1].
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 02:22:49 PM
Please see the attached new file.
I'll change firmware just shortly.
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 02:26:46 PM
I don't know if the drop I'm seeing at the first downstream tones is caused by x1 [to be seen], but even if it looked perfect I would blame x1 anyway. It doesn't matter how it looks, just how it performs, but if the v performs similarly then the graph from the x1 could be useful.

If you can wait for longer than 32 minutes before turning on the device hooked to the DSL, then I recommend waiting for as long as you could see fit, as the switching between modem drivers will probably make your DLM go even worse.
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 04:00:23 PM
Here is the bitloading graph with the other firmware installed.
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 05:07:12 PM
Looks the same but will perform differently, but the first days will be rough as always. If it doesn't improve on the 4th day, turning off from power button & turning back on after 31 minutes is needed to verify, if it still continued it would be either 1. the modem or 2. something else changed

At the bottom of the bitloading page there's an icon of a green camera - it saves the snapshots to the location set in Configuration>Snapshots>Snapshots directory. I've set it to the same folder DSLStats is in.
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 06:34:00 PM
It is already looking a lot better with far fewer errors. So now I shall leave for stability.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 17279 Kbps, Downstream rate = 61982 Kbps
Bearer: 0, Upstream rate = 16964 Kbps, Downstream rate = 48997 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):        9.4             6.0
Attn(dB):        17.8            0.0
Pwr(dBm):        13.6            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              195             162
M:              1               1
T:              0               0
R:              12              12
S:              0.0000          0.0000
L:              13117           4585
D:              4               4
I:              208             175
N:              208             175
Q:              4               4
V:              2               0
RxQueue:                135             55
TxQueue:                27              11
G.INP Framing:          18              18
G.INP lookback:         27              11
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             391696156               187778
RSCorr:         157             6100
RSUnCorr:       0               0
                        Bearer 1
OHF:            776466          779563
OHFErr:         0               0
RS:             6211237         3118254
RSCorr:         1               1647
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9965749         4105
rtx_c:          89              90270
rtx_uc:         0               408952

                        G.INP Counters
LEFTRS:         0               446
minEFTR:        48999           16961
errFreeBits:    9316575         1962069651

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1175153637              0
Data Cells:     4641139         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:             0               0
SES:            0               0
UAS:            28              28
AS:             12474

                        Bearer 0
INP:            54.00           52.00
INPRein:        1.00            1.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            49248.62        17015.93

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        13/13           339/339

Total time = 3 hours 28 min 22 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 13 min 22 sec
FEC:            8               391
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:            0               432
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 = 3 hours 28 min 22 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               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 = 3 hours 27 min 53 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >

I still haven't got DSLstats running correctly and currently accessing it through a long ethernet cable to my PC. I did find a post about checking to make sure that the DHCP server in the default LAN setup was disabled. It was not but is now. I would imagine that I require to reboot it but will get some stability on the line first before rebooting things, And making adjustments etc.
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 06:55:54 PM
You just need to reboot the other devices, as DHCP assigns to another device and the origin is unaffected. [I think]
ZyXEL is able to change most settings on the fly unlike some devices.

Edit: Forgot to say, I'll keep using x1 for as long as I want, be it a few hours or a week, but I've lost any hope in it  :-\  Having no DLM, I wish DLM wasn't enforced on other people.
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 07:31:29 PM
My line was already banded due to a fault with my previous equipment so I'm not too worried that it has been impacted further.
If it stays at 48mbps I've a better chance of getting a reset (assuming I am now staying stable)

As for dslstats. I'll create a new thread for that. I think I'm just thick!!
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 07:36:03 PM
If it stays at 48mbps I've a better chance of getting a reset (assuming I am now staying stable)
:blush: Not so bad then  :-[
Title: Re: Stat check on my line please
Post by: michty_me on June 24, 2018, 07:41:31 PM
I want to see stability for probably a week or two and then I will request it.
Title: Re: Stat check on my line please
Post by: spring on June 24, 2018, 08:09:09 PM
Yeah after 14 days
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 09:32:51 AM
if you have sync drops you need SRA, if you don't have any drops whatsoever, it's better without [well, if you ever speak with your ISP, you can ask them to check if your line has SRA. can also enable it and see, but it should be on only if there are drops (if the ISP supports SRA and the modem has it disabled, I don't think it's a negative impact - will search about that)].

edit: it can be off in the modem even if the DSLAM supports it, without side effects (at least, it very much seems so).

edit2: what I recommend is that if you happen to find out from your ISP that it's supported & enabled, to turn it on and benefit from sync rate adaptation to noise and possible saves from sync drops [the profile rate remains the same].
Title: Re: Stat check on my line please
Post by: michty_me on June 27, 2018, 09:58:52 AM
I haven't had an drops what so ever.
I think I'm approaching the 3 day mark and have 0 errors for all CRC, ES and SES.
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 10:11:19 AM
FEC's count too but the longer you let it run until the DLM reset, the better it will re-sync after the reset

however if there is something "stuck" or not improving as it should over the first week & bitloading graph also shows it then a resync would be better: of course, if it's not the case then it's detrimental to do that. in general V doesn't need any resyncs anywhere from 3 months to 1 year [or 2 years... xD], depends. the recommendation I've read & support is every 3 months to turn off the device, so 4 resyncs per year. or every 4 months, 3 per year. whichever fits more.

you can PM me your bitloading graph and --stats whenever
Title: Re: Stat check on my line please
Post by: johnson on June 27, 2018, 10:14:38 AM
FEC's count too but the longer you let it run until the DLM reset, the better it will re-sync after the reset

FECs do not count towards DLM, they are corrected errors.
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 10:25:50 AM
FECs do not count towards DLM, they are corrected errors.
that's not what i meant..............

it was about the ongoing sync and whether it benefits a re-sync

nothing about DLM
Title: Re: Stat check on my line please
Post by: michty_me on June 27, 2018, 10:39:31 AM
The line seems happy just now at its current level anyway.
I'm wondering if when I started the thread, If the latest lockup of the D7000 caused enough errors for the DLM to kick in and increase my SNR again or if it was using the X1 firmware. Something I'll never find out anyway.

I noticed prior to last weekw lockout, DLM would appear to make an alteration every 6-7 days or so.
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 10:43:26 AM
x1 dropped your speed from 55 to 48 and i know from experience it can increase errors on the line from 5 to 15 times more, in your case caused a drop of sync & all the error types

is there something irreversible about it? assuming not, it's good right?

how to trigger DLM: flash to x1 and let it run for 4 days, done [after the first 4 days its actually been fine for me xD]
Title: Re: Stat check on my line please
Post by: johnson on June 27, 2018, 10:59:07 AM
I honestly think you are being over dramatic spring. I have been running the x1 adsl_phy on my line for weeks, with if anything reduced errors.

Weaver and j0hn have also used it, and all they saw was very slightly reduced sync speed.

You have spent a lot of time looking at your line stats and making some strange assumptions. You have a line with an attainable over twice that of your sync speed, and you take interest in things like FECs in the tens. Many perfectly stable lines have millions of FEC errors a day...

I honestly have no idea what to make of your input about the various adsl_phy, or why you feel the need to talk about it the way you do.
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 11:01:45 AM
I honestly think you are being over dramatic spring. I have been running the x1 adsl_phy on my line for weeks, with if anything reduced errors.

Weaver and j0hn have also used it, and all they saw was very slightly reduced sync speed.

You have spent a lot of time looking at your line stats and making some strange assumptions. You have a like with an attainable over twice that of your sync speed, and you take interest in things like FECs in the tens. Many perfectly stable lines have millions of FEC errors a day...

I honestly have no idea what to make of your input about the various adsl_phy, or why you feel the need to talk about it the way you do.
where did this come from just now

im going to ignore this post and yes, 10 times the average FEC that had been stable for months with V means i need to leave x1 running for longer before I can justify using it as so far it has been nothing but buggy

by the way, j0hn said it performed worse for him

also, talk about it the way I do? first you said it's nice I'm providing information, now it's somehow meaningless? I wouldn't have gone back to x1, don't want to constantly watch my line.

my line doesn't have vectoring like yours

the reason I'm leaving x1 to run is because it has days with reduced errors, I'm just trying to see how it behaves. when did I say it's going to be like that for everyone? the reason I'm being dramatic is some people have DLM.

and this information doesn't apply to ADSL , weaver is using ADSL.

and what about missing upstream bits?

btw the triggering DLM line was written as a joke not a fact
Title: Re: Stat check on my line please
Post by: johnson on June 27, 2018, 11:12:19 AM
where did this come from just now

im going to ignore this post and yes, 10 times the average FEC that had been stable for months with V means i need to leave x1 running for longer before I can justify using it as so far it has been nothing but buggy

by the way, j0hn said it performed worse for him

also, talk about it the way I do? first you said it's nice I'm providing information, now it's somehow meaningless? I wouldn't have gone back to x1, don't want to constantly watch my line.

Apologies, maybe I'm just a little grumpy.

Feedback about how the x1 adsl_phy performs is great, but you have posted so much about it in the other thread an here and say things like "10x the FEC errors" when you are going on stats from your line, so yes 50 FEC in a few days might be 10x for you but its still fairly meaningless. There is a real limit to the usefulness of your data when you have basically a line capped at half of what it can do.

Again sorry I'm probably overreacting, its just so much talk here to someone asking for basic advice about his line, just say "the x1 firmware might not work well, stick to the normal v" and move on.

still love you spring  :P

Edit:
btw the triggering DLM line was written as a joke not a fact

Ok maybe thats the part I missed.  ;D
Title: Re: Stat check on my line please
Post by: michty_me on June 27, 2018, 11:18:12 AM
Ill be sticking with what I have for now. I've been banded probably just coming up for a month and either the D7000 lockup, the Zyxel switchover or (dare I say it) firmware differences (or all 3 together) has now reduced me further so all I'm aiming to do now is prove stability for a number of weeks so I can show my ISP I've done what they asked and hopefully get my remote DLM reset.
Title: Re: Stat check on my line please
Post by: johnson on June 27, 2018, 11:29:49 AM
Ill be sticking with what I have for now. I've been banded probably just coming up for a month and either the D7000 lockup, the Zyxel switchover or (dare I say it) firmware differences (or all 3 together) has now reduced me further so all I'm aiming to do now is prove stability for a number of weeks so I can show my ISP I've done what they asked and hopefully get my remote DLM reset.

Sounds like a solid plan.

I'm really sorry if the x1 version has anything to do with your banding reducing like it has, would not of thought it possible  ???. Kind of annoyed I put it out there as it seems to have cause more annoyance than good.

Really weird that it went from the higher sync after adding the zyxel to lower like it has... roll on your DLM reset, I'm sure the zyxel with standard firmware will perform better than your D7000, given the higher sync and attainable it gave to begin with.
Title: Re: Stat check on my line please
Post by: spring on June 27, 2018, 11:33:05 AM
@jonhson   i don't know how it would be for other people, I just know what I'm saying is true for my line...
also michty_me said it's actually good that he's banded as it guarantees a DLM reset
it's useful that you released x1 firmware & it's not your fault as it seems to run flawlessly on your line
80% percent of the reason d7000 wasn't good is it has a hardware problem that makes it lock up after a month

@michty_me   all 3 but it's x1 that hit the reduction from 55 to 48 button


I've had perfect days of 30 FEC with the x1, even though I admittedly prefer V, i'm mainly trying to see its behaviour on my line
is there a chance the adsl_phy.bin from the 3925 is made for d26n? you know, in that changelog document the x3 in the package was said to be made for d26d
like, if x1 was made by zyxel for vmg1312-b10a [d26a] if it looked differently
Title: Re: Stat check on my line please
Post by: michty_me on June 27, 2018, 11:44:50 AM
I'm unsure about DLM reset being guaranteed but I'm now sitting borderline on my handback value. So with it actually dropping my speed, it may have inturn helped me out.

Zen said to give it a week after I made some changes but I'll give it a few weeks for my own peace of mind and then raise a ticket.

I'll be interested to see if the D7000 still fails around the one month area when it is router only mode.
Title: Re: Stat check on my line please
Post by: Ixel on June 27, 2018, 11:49:17 AM
I'm unsure about DLM reset being guaranteed but I'm now sitting borderline on my handback value. So with it actually dropping my speed, it may have inturn helped me out.

Zen said to give it a week after I made some changes but I'll give it a few weeks for my own peace of mind and then raise a ticket.

I'll be interested to see if the D7000 still fails around the one month area when it is router only mode.

Just to say that on one of my FTTC connections with AAISP I did manage to get a DLM reset a while ago even though the banding was, if I recall correctly, about possibly half a dozen megabits off from the attainable rate. It took some time to get it sent through though because TalkTalk Business weren't part of the trial apparently. I wasn't at or below the handback threshold either. I think you should be able to successfully get a DLM reset done as long as Zen will make the request.
Title: Re: Stat check on my line please
Post by: michty_me on June 27, 2018, 12:31:47 PM
Just to say that on one of my FTTC connections with AAISP I did manage to get a DLM reset a while ago even though the banding was, if I recall correctly, about possibly half a dozen megabits off from the attainable rate. It took some time to get it sent through though because TalkTalk Business weren't part of the trial apparently. I wasn't at or below the handback threshold either. I think you should be able to successfully get a DLM reset done as long as Zen will make the request.

Here's hoping then.
My main concern at present is that if I do it too soon, And I encounter another similar issue a few weeks down the line then I'm back to square one. I'm possibly thinking in just leaving it running for a month or possibly two and see how it copes (I'm sure it will be fine) then report back to Zen. However, I may call and raise a ticket anyway so that it is documented.
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 01:27:21 PM
Just a little update.
I was on the Zen chat to create/update the ticket a little while ago to advise that I had swapped out equipment and could they note that.
The advisor said he was happy with the small amount of errors now. I was hoping to leave it running for a few weeks before they went ahead but the advisor said he was requesting a DLM reset (Done tomorrow night as missed todays cut off).

I'll be away at the weekend so will just leave the equipment running and see what I come home too on Monday.
Title: Re: Stat check on my line please
Post by: j0hn on June 28, 2018, 04:51:44 PM
I think that's the best route. The line should have G.INP and be running at 3dB target SNRM within a couple weeks all being well.

If you haven't already done so I would recommend installing a version of the zyxel firmware with the standard dsl driver. That's either an official version from zyxel or better still 1 of the jumbo frames firmware (just not 1 labelled 3925).

Once your line has been running stable would be a better time to try different dsl driver versions.
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 04:55:28 PM
Hi John,
Here's hoping all is well. Last time it was reset, it went back to a 3db within 7 days and only reverted again when the D7000 locked up and I never caught it in time.

Just to confirm, I'm running the jumbo frame firmware without the 3925 currently. I shall triple check as soon as I get in though.
Title: Re: Stat check on my line please
Post by: spring on June 28, 2018, 05:47:34 PM
Standard/original/non-3925
Code: [Select]
Stats recorded 17 Jun 2018 10:09:16

DSLAM type / SW version: IFTN:0xb206 (178.6) / v0xb206
Modem/router firmware:  AnnexA version - A2pv6F039v.d26a <----------------------------------------
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  0 hour 9 min 51 sec
Resyncs:                0 (since 17 Jun 2018 10:09:11)

Downstream Upstream
Line attenuation (dB):  10.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 44880 3455
SNR margin (dB):        25.4 19.5
Power (dBm):            -15.1 -15.3
Interleave depth:        1 55
INP:                    44.00 2.00
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0000 0.0000
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 0



---------------------------3925---------------------------
Stats recorded 17 Jun 2018 09:01:15

DSLAM type / SW version: IFTN:0xb206 (178.6) / v0xb206
Modem/router firmware:  AnnexA version - A2pv6F039x1.d26a <----------------------------------------
DSL mode:                VDSL2 Profile 17a
Status:                  Showtime
Uptime:                  13 days 18 hours 2 min 50 sec
Resyncs:                0 (since 17 Jun 2018 09:01:09)

Downstream Upstream
Line attenuation (dB):  10.7 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 44880 3455
SNR margin (dB):        25.3 19.6
Power (dBm):            -14.9 -15.1
Interleave depth:        1 55
INP:                    44.00 2.00
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0000 0.1436
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 0
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 05:54:57 PM
Yes, It appears I am on the standard/Non-3925 firmware.

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6F039v.d26a
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    4 days 2 hours 53 min 6 sec
Resyncs:                   0 (since 27 Jun 2018 22:53:34)
         
            Downstream   Upstream
Line attenuation (dB):     17.8      0.0
Signal attenuation (dB):   Not monitored      
Connection speed (kbps):   48997      16964
SNR margin (dB):           9.4      6.0
Power (dBm):               13.6      7.5
Interleave depth:          4      4
INP:                       54.00      52.00
G.INP:                     Enabled      Enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0001      3.2695
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0


Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 05:59:32 PM
Well, That was really quick. From writing my reply, I've now gone from this:

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 17230 Kbps, Downstream rate = 62308 Kbps
Bearer: 0, Upstream rate = 16964 Kbps, Downstream rate = 48997 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):        9.4             5.9
Attn(dB):        17.8            0.0
Pwr(dBm):        13.6            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              195             162
M:              1               1
T:              0               0
R:              12              12
S:              0.0000          0.0000
L:              13117           4585
D:              4               4
I:              208             175
N:              208             175
Q:              4               4
V:              2               0
RxQueue:                135             55
TxQueue:                27              11
G.INP Framing:          18              18
G.INP lookback:         27              11
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
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               0
OHFErr:         0               0
RS:             2581776224              220311
RSCorr:         3510            109987
RSUnCorr:       0               0
                        Bearer 1
OHF:            22144186                213968
OHFErr:         0               0
RS:             177152996               3036910
RSCorr:         4               2835
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9970064         7933
rtx_c:          1669            94066
rtx_uc:         0               408952

                        G.INP Counters
LEFTRS:         0               446
minEFTR:        48999           16955
errFreeBits:    265700971               2050620157

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    3450374261              0
Data Cells:     354891517               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:             0               0
SES:            0               0
UAS:            28              28
AS:             355746

                        Bearer 0
INP:            54.00           52.00
INPRein:        1.00            1.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            49248.62        17015.93

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        5150/5150               9952/9952

Total time = 4 days 2 hours 49 min 34 sec
FEC:            3510            109987
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 4 min 34 sec
FEC:            0               3
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:            0               26
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 = 2 hours 49 min 34 sec
FEC:            31              246
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:            1034            10824
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 4 days 2 hours 49 min 5 sec
FEC:            3510            109987
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >

To this:

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 15093 Kbps, Downstream rate = 61892 Kbps
Bearer: 0, Upstream rate = 15093 Kbps, Downstream rate = 52325 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.2             6.1
Attn(dB):        17.9            0.0
Pwr(dBm):        13.6            7.4

                        VDSL2 framing
                        Bearer 0
MSGc:           18              25
B:              51              237
M:              1               1
T:              64              64
R:              12              16
S:              0.0316          0.5016
L:              16192           4051
D:              1025            1
I:              64              127
N:              64              254

                        Counters
                        Bearer 0
OHF:            77766           19581
OHFErr:         0               6
RS:             19783208                1252771
RSCorr:         0               1
RSUnCorr:       0               0

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

ES:             10              6
SES:            10              0
UAS:            60              50
AS:             158

                        Bearer 0
INP:            3.00            0.00
INPRein:        0.00            0.00
delay:          8               0
PER:            2.03            8.05
OR:             94.50           30.78
AgR:            52419.23        15124.19

Bitswap:        2/2             1/1

Total time = 4 days 2 hours 57 min 34 sec
FEC:            3630            109989
CRC:            539             6
ES:             10              6
SES:            10              0
UAS:            60              50
LOS:            1               0
LOF:            7               0
LOM:            0               0
Latest 15 minutes time = 12 min 34 sec
FEC:            120             5
CRC:            539             6
ES:             10              6
SES:            10              0
UAS:            32              22
LOS:            1               0
LOF:            7               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            0               26
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 = 2 hours 57 min 34 sec
FEC:            151             248
CRC:            539             6
ES:             10              6
SES:            10              0
UAS:            32              22
LOS:            1               0
LOF:            7               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            1034            10824
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 2 min 37 sec
FEC:            0               1
CRC:            0               6
ES:             0               6
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >
Title: Re: Stat check on my line please
Post by: spring on June 28, 2018, 06:02:02 PM
IMO the DLM reset is too hasty but if they insist what can you do :D that's why the first thing I had in my mind when I read they just went ahead and DLM resetted is that it's best to not be "honestly good" rather just "honest" [if you didn't update them you ran this for how long you wanted].

about that, well, like i said 14 days [or 21, i honestly didn't expect that loss of sync either - i meant 14 days of continuously running].

ask them if SRA is enabled on your line.

while at it, what cable length is your DSL?

btw even though it's good that the DLM is doing good things to you line, this resync just now wasn't so ideal but by tonight it should be fine
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 06:09:52 PM
I'm fairly confident the new equipment will be fine. I wouldn't of had any issues if the D7000 wouldn't randomly lock up for whatever reason. I shall be monitoring the Zyxel but leaving well alone.

I'll ask about SRA tomorrow perhaps.
Title: Re: Stat check on my line please
Post by: spring on June 28, 2018, 06:13:07 PM
I'm not concerned that it's not going to be fine, I'm just trying to be informative, at this point the 14 days would've been for the best results since it's most likely all fine
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 06:20:30 PM
I see. Well its done now  :lol: Now we wait and see.
Title: Re: Stat check on my line please
Post by: spring on June 28, 2018, 06:22:13 PM
I think they reset your line just now.... it's not doing so great now but once you get G.INP back on your line you'll have more sync

about the bitloading/SNR graph on the last sync of 4 days, things stabilize after 4 days but the bitloading/SNR graph stabilizes until usually 14 days & after a resync it's less messy so better impression on the DLM, but it doesn't matter it's all good, they are trying to be nice and end your banding quicker  :)
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 06:54:08 PM
Yup, Bang on 6pm I noticed it flagged up saying 'No DSL Connection' then it came back on with a retrain reason 1.

I must say, I am impressed with how quickly Zen have done this. I was expecting to have to wait a significant time for a reset (Which I would have been happy with)

The last time BT reset it after giving my line the all clear and it took exactly 7 days to get back up to full speed (G.Inp and 3dB profile) so hopefully this time next week I can report the same.
Title: Re: Stat check on my line please
Post by: j0hn on June 28, 2018, 07:33:45 PM
Interleaving applied as expected. G.INP will return in couple days. The banding is gone    :yay:

There is no SRA on ADSL or VDSL2 in the UK.
Title: Re: Stat check on my line please
Post by: michty_me on June 28, 2018, 07:35:26 PM
Yip!  :fingers:
Good to know and that's what I read. Saves me asking the question tomorrow.
Title: Re: Stat check on my line please
Post by: michty_me on July 11, 2018, 07:32:48 PM
So this morning I woke up and noticed I am back on a 3dB profile again. It took about 12 days to lower back down to this and seems happy enough.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    1
Last initialization procedure status:   0
Max:    Upstream rate = 15086 Kbps, Downstream rate = 71443 Kbps
Bearer: 0, Upstream rate = 15078 Kbps, Downstream rate = 70940 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.4             6.0
Attn(dB):        17.8            0.0
Pwr(dBm):        13.6            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              25
B:              243             237
M:              1               1
T:              0               64
R:              10              16
S:              0.0000          0.5021
L:              18553           4047
D:              8               1
I:              254             127
N:              254             254
Q:              8               0
V:              0               0
RxQueue:                80              0
TxQueue:                20              0
G.INP Framing:          18              0
G.INP lookback:         20              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               1471755
OHFErr:         1               76
RS:             2260661368              1179067
RSCorr:         23686           403
RSUnCorr:       0               0
                        Bearer 1
OHF:            3868762         0
OHFErr:         0               0
RS:             38687004                0
RSCorr:         2               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9978437         7990
rtx_c:          7503            94068
rtx_uc:         195964          408952

                        G.INP Counters
LEFTRS:         58              446
minEFTR:        70943           16961
errFreeBits:    3754513212              2050694977

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    4182632381              0
Data Cells:     34091469                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:             103             5813
SES:            52              0
UAS:            192             140
AS:             62152

                        Bearer 0
INP:            51.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            8.06
OR:             0.01            30.75
AgR:            71012.87        15109.26

                        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:        8508/8508               1255/1255

Total time = 17 days 4 hours 32 min 16 sec
FEC:            263725          118267
CRC:            7275            6095
ES:             103             5813
SES:            52              0
UAS:            192             140
LOS:            5               0
LOF:            37              0
LOM:            0               0
Latest 15 minutes time = 2 min 16 sec
FEC:            254             2
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:            732             5
CRC:            0               1
ES:             0               1
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 4 hours 32 min 16 sec
FEC:            8581            95
CRC:            0               22
ES:             0               21
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            20060           511
CRC:            574             92
ES:             11              87
SES:            10              0
UAS:            33              23
LOS:            1               0
LOF:            7               0
LOM:            0               0
Since Link time = 17 hours 15 min 51 sec
FEC:            23686           403
CRC:            1               76
ES:             1               71
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >