[Mrk26]

Bully wrote:

Today’s stats

Something must be wrong there, you getting now much more FECs 567k and on top of that you getting a lot more CRC errors. I’m not sure if first suggestion from @Uk Sentinel about noise on the line is not correct. Also wonder if you not getting higher amount of CRCs and FECs because you line sync faster now. When line was banded these errors was under control (kind of), but snr was 8db now you are on standard 6db. There is actually option to put cap on the line to make it more stable. Let’s see how stats will looks like tomorrow.

You need to login in order to vote

[Mrk26]

Allocating port to the socket, so wan to lan 1(socket )  and lan to lan2(socket), at least how I understand this, maybe worong.

You need to login in order to vote

[Mrk26]

On mine bitswaps barely swapping, however I think I will need to stop this exercise even today, for some reason I’m getting bunch of CRCs what didn’t happened on vigor.

You need to login in order to vote

[Mrk26]

Well still running and keep an eye on it from time to time. In the mean time I was browsing internet about g.inp on eci, and found something interesting… This wonderful future enable FEC on downstream for broadcom modem on eci cabinet 😂😂 what convenience me even more to go back to draytek. Therefore not sure how it’s working on Huawei cabinet @Uk Sentinel?

You need to login in order to vote

[Mrk26]

Right, I have to rebooted zyxel modem as I have bunch of CRC error, looks like it can cope properly with snr below 6db (on 6db profile). Will keep an eye on it till rest of the day, draytek may be back on duty sooner

You need to login in order to vote

[Mrk26]

I think it may be interesting to see @Bully bitswap per minute graph as well.

Attachments:

1. 

   bitswap-per-minute.jpg
   

You need to login in order to vote

[Mrk26]

I put mine back in the name of science , so far no issues with it, slightly slower on sync speed but I knew the price. I think my cabinet going to blow up anyway, as attainable speed keep dropping pretty much every  week, what didn’t happened in the past.  No issues with vigor as you know so I may put him back next weekend ( I must be bored too ).

Below my recent stats, snr on downstream 5.8db was 6.2db when I connected but obviously attainable speed drop so snr follow. Also bitswap bit higher since connected but not much.

adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 22087 Kbps, Downstream rate = 72276 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 72470 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): 5.8 6.4
Attn(dB): 13.3 0.0
Pwr(dBm): 1.1 1.1

VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 22 5
R: 0 16
S: 0.1054 0.3771
L: 18216 5410
D: 1 1
I: 240 255
N: 240 255

Counters
Bearer 0
OHF: 8503806 2424350
OHFErr: 68 20
RS: 0 2886047
RSCorr: 0 142
RSUnCorr: 0 0

Bearer 0
HEC: 168 0
OCD: 2 0
LCD: 2 0
Total Cells: 2069172117 0
Data Cells: 44895294 0
Drop Cells: 0
Bit Errors: 0 0

ES: 24 20
SES: 0 0
UAS: 27 27
AS: 14851

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.74 6.15
OR: 109.97 202.87
AgR: 72580.48 20203.27

Bitswap: 29/29 3/3

Total time = 4 hours 7 min 58 sec
FEC: 0 142
CRC: 68 20
ES: 24 20
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 58 sec
FEC: 0 10
CRC: 2 1
ES: 2 1
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 14
CRC: 3 1
ES: 3 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 4 hours 7 min 58 sec
FEC: 0 142
CRC: 68 20
ES: 24 20
SES: 0 0
UAS: 27 27
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 = 4 hours 7 min 29 sec
FEC: 0 142
CRC: 68 20
ES: 24 20
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0

Liked by:

You need to login in order to vote

[Mrk26]

Sorry for late reply, this is mine:

DSLAM type / SW version: IFTN:0xb206 (178.6) / v0xb206

@Bully is

DSLAM type / SW version: IFTN:0xd086 (208.134) / v0xd086

You need to login in order to vote

[Mrk26]

@Bully

After I look closer I see that your card (in DLM) is on different fw than mime, that’s explain sync during the daytime. To see better differences I put zyxel on my line, and the thing which I realised straight away is bitswap, on yours is in thousands on downstream where mine looks like that

Bitswap      18/18      1/1

Don’t want to predict evil but I think there maybe some issues on your line, could be noise on some tones, that’s why bitswap working so hard, because some tones are unusable bits are swapped that is probably why you had so high amount of errors with draytek, hg612 seems to use different tones or either manage to bitswap better.

Could you please post pictures of snr graph and hlog from dsl stats program. (when you got time of course)

You need to login in order to vote

[Mrk26]

That strange, it looks like DLM did resync during the day which is not common. However it’s looking good as your line is nod banded so far, so things moving right direction 👍

You need to login in order to vote

[Mrk26]

Modem sync nearly 40Mb/s on downstream now, did you rebooted recently? 🤔

You need to login in order to vote

[Mrk26]

O.K first of all, the HG612 will not work on single cable until you finish procedure from post you linked, and actually I read through and Iptable commands are executed on HG612 modem so that may be a bit tricky. The other more safe option is configure HG612 as I described earlier with two cables connected and I guarantee that all will work as should.

For better telnet experience I recommend PuTTY

You need to login in order to vote

[Mrk26]

Did you configure HG612 as per instruction from your link? The biggest issue here is HG612 which is not configured properly, once that is sorted all should work. Thing is that if you will play with HG612 now it may reboot as configuration will be changed what is not good move now when modem settling.

Edit

Every reboot now delay positive action from DLM side, so it’s your call. If you reboot modem you start counting again from scratch. I personally will wait these couple of days.

Edit 2,

You sure you setup telnet from windows correctly? If dsl stats working telnet must working as well as dsl stats take all data from telnet.

You need to login in order to vote

[Mrk26]

Bully wrote:

This looks interesting – https://forum.kitz.co.uk/index.php?topic=17671.0

With iptables it’s always lottery, may work, may not. I think I tried in the past with Rt-ac68u and I wasn’t successful. For one cable solution best method working on asus router is the one @Uk Sentinel wrote in vigor section on this forum. If per these instructions HG612 will work on one cable then you can configure same way as vigor.

@Uk Sentinel

Could you please have look on this guide and see if HG612 configured as per instruction from link will work on one cable with asus router configured “your” way.

You need to login in order to vote

[Mrk26]

Well 111k FEC errors now compare to milions before, I personally see light in this tunnel. Let’s see if DLM will like this change, minimum 3 days, maximum 6 for any positive action. If nothing happen then we will think about how to help DLM to make right decision 😉

You need to login in order to vote

[Author]

Posts