RT-AC86U 384.16 Hi, I updated to the latest Merlin firmware this morning (about 9 am) and since doing so my NE CRC count has gone up to 326598 over 5 hours. ...

[Mrk26]

Just as comparison as I’m interleaved on downstream and right now I got 42k FEC errors for last 21h.

@Bully

When last time you had resync?

You need to login in order to vote

[UK Sentinel]

@Bully, Did you notice any changes since changing Modem Bridge Type ? are the stats/ping better / worse in your opinion ?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Bully]

@Mrk26 – I have not done any manual re-syncs or reboots.

 

@UK-Sentinel – Does not seem to have made a difference.

You need to login in order to vote

[UK Sentinel]

@Bully, could you give the modem a reboot at some point this week, just to see if that changes/improves the stats etc?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Bully]

UK Sentinel wrote:

@Bully, could you give the modem a reboot at some point this week, just to see if that changes/improves the stats etc?

 

Ok, i will do it first thing tomorrow morning and pull the stats after work.

I have been checking the stats daily over the last few months and i keep thinking the same thing, the time the CRC and FEC errors went bananas  was when i updated the Asus  RT-AC86U Merlin firmware to 384.16 from 384.15.  Is the no chance at all this could be the cause?  There is also a new firmware out 384.17, I will probably update to this at the weekend.

You need to login in order to vote

[Mrk26]

Regarding fw update I doubt, however on my son pc we have issues with WiFi one time, it causes lots of packet loss in game and at this time I had a bit more CRC errors than usually, find newest driver and after update all was fine, no more packets lost in game and CRCs go down. I agree with @Uk Sentinel to rebot at some point but not before at least 5 days constantly connected or since resync.

Edit,

Try with stock asus fw to be sure.

Edit 2

@Bully

I was running Merlin 384.13 as this was the best stable on my RT-AX88U, every newest build messed up my WiFi, so I dirty updated to latest stock asus and all nice and smooth since then.

You need to login in order to vote

[UK Sentinel]

@Bully – I thought we originally downgraded firmware to 384.15. and CRC was still there. Your CRC are downstream and are modem based CRC and not Xbox packet loss (different) which is very unlikely router will impact Modem for CRC.

But by all means try the upgrade, newer is usually better ;-)

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Bully]

Just rebooted modem, ping on speed test is now 16ms, 37 mb ds and 11 mb us.  Will posts all stats later.

Liked by:

You need to login in order to vote

[Mrk26]

Bully wrote:

Just rebooted modem, ping on speed test is now 16ms, 37 mb ds and 11 mb us. Will posts all stats later.

That is absolutely normal, I got best results just after reboot as well. However from my experience if you reboot modem to often you have low chances for getting better. As I observed DLM measure line conditions in specific periods. In my example positive actions was done after 3, 5, and 6 days after modem was connected constantly. So for example if you brake period where DLM monitor your line after 2.5 days your period was reset. Now you will need to wait at least 3 days and on day 4 should be some action taken if not then as above. If nothing change after 7 days it will not at all untill we help DLM to make right decision in this case cap on the line is the only one working solution.

You need to login in order to vote

[Bully]

Speed fell off about 2 hours ago, no one in the house could do anything online, speed went down to kbps (got a phone call while i was at work from my other half).  When i got home i was told they turned router and modem off and on again  and this fixed the problem.

Today’s stats –

xdslcmd info –stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 12298 Kbps, Downstream rate = 50204 Kbps
Bearer: 0, Upstream rate = 12216 Kbps, Downstream rate = 39994 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.7 6.1
Attn(dB): 19.5 0.0
Pwr(dBm): 13.4 6.7
VDSL2 framing
Bearer 0
MSGc: 18 20
B: 31 238
M: 1 1
T: 64 63
R: 10 16
S: 0.0255 0.6225
L: 13200 3277
D: 1283 1
I: 42 255
N: 42 255
Counters
Bearer 0
OHF: 2094011 523933
OHFErr: 0 0
RS: 803945292 2940453
RSCorr: 8189 0
RSUnCorr: 0 0

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

ES: 0 2653
SES: 0 31
UAS: 25 84199
AS: 5138

Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.45 9.84
OR: 78.26 21.13
AgR: 40072.04 12237.73

Bitswap: 3724/3743 0/0

Total time = 1 hours 26 min 3 sec
FEC: 8189 0
CRC: 0 0
ES: 0 2653
SES: 0 31
UAS: 25 84199
LOS: 0 1
LOF: 0 1
LOM: 0 0
Latest 15 minutes time = 11 min 3 sec
FEC: 1184 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: 848 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 1 hours 26 min 3 sec
FEC: 8189 0
CRC: 0 0
ES: 0 2653
SES: 0 31
UAS: 25 84199
LOS: 0 1
LOF: 0 1
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 25 min 37 sec
FEC: 8189 0
CRC: 0 0
ES: 0 2653
SES: 0 31
UAS: 0 84174
LOS: 0 1
LOF: 0 1
LOM: 0 0

Stats recorded 29 Apr 2020 17:20:18

DSLAM type / SW version: IFTN:0xd086 (208.134) / v0xd086
Modem/router firmware: AnnexA version – A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 1 hour 26 min 38 sec
Resyncs: 0 (since 29 Apr 2020 17:19:13)

Downstream Upstream
Line attenuation (dB): 19.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 39994 12216
SNR margin (dB): 6.8 6.1
Power (dBm): 13.4 6.7
Interleave depth: 1283 1
INP: 3.50 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)

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

You need to login in order to vote

[UK Sentinel]

No real change (Interleave depth is slightly less) give it a few more days if pos – if that does not show any improvements, then if the Quite Line test trick still works, a call to BT as some point is advised.

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Mrk26]

I think is worth to mention for other half that benefit of two box solution is that router can be rebooted first to check if that will not solve problem 😜

Personally understand in 100% my wife disconnected modem several times when she need power socket for something else, exactly this one, not to mention that meter away on other wall is another completely free fully working socket 😂😂

In my case awaiting for fastpath delayed for over week based on that.

If you lost patience you can always try to cap line but as in post above full 5 days for good results is absolutely must.

You need to login in order to vote

[Bully]

Looking at the Asus stats its seems it was connecting and disconnecting all the devices connecting to it and it was not the modem.  I have made it clear to only to switch the router off

Its funny how you get the facts when you get home.

You need to login in order to vote

[Mrk26]

UK Sentinel wrote:

No real change (Interleave depth is slightly less) give it a few more days if pos – if that does not show any improvements, then if the Quite Line test trick still works, a call to BT as some point is advised.

Can’t remember now, if @Bully done quiet line test on test socket only or on filtered faceplate as well. I read somewhere that filtered plate may go wrong due to power cuts or storms.

You need to login in order to vote

[UK Sentinel]

@Bully performed original quiet line test via Master Socket (faceplate socket) I believe.

Yes, I believe also faceplates can fail if line (outside) is hit with lightening etc.

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Author]

Posts