Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2

Author Topic: Storm Damage?  (Read 1658 times)

h0110

  • Just arrived
  • *
  • Posts: 7
Storm Damage?
« on: July 13, 2020, 02:27:06 PM »

Hey gang,

Hope you are keeping well

I've been here and there around this site but never formally made any posts.

Currently have BT FTTC 80/20 from an ECI cab which I'm approx 300m away from.

I've ran various setups including HG612, ECI running OpenWRT and finally now the 8924-B10A which seems to be preforming the best.

When Openreach came around 4-5 years ago they never found the master socket so I self upgraded to a NTE5a with the MK2 VDSL plate with no extensions wired in. Runs with a Cat 6 cable into the 8924-B10A which acts as a bridge for the RT-AC68U

Recently had the lightning storms which has kicked in interlacing and has incurred quite a few errors since from quite a stable collection. 

I'm not too clued up with the graphs and would appreciate if anybody could workout what im looking at here and what should be done to sort it out  :) :)









Code: [Select]
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 25238 Kbps, Downstream rate = 90663 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 69774 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.6 9.5
Attn(dB): 14.2 0.0
Pwr(dBm): 3.5 3.4

VDSL2 framing
Bearer 0
MSGc: 18 150
B: 45 236
M: 1 1
T: 64 5
R: 14 16
S: 0.0210 0.3771
L: 22888 5410
D: 1663 1
I: 60 255
N: 60 255

Counters
Bearer 0
OHF: 41524198 920139
OHFErr: 50 0
RS: 2040071951 941817
RSCorr: 1490858 9
RSUnCorr: 840 0

Bearer 0
HEC: 159 0
OCD: 0 0
LCD: 0 0
Total Cells: 3212607132 0
Data Cells: 239717093 0
Drop Cells: 0
Bit Errors: 0 0

ES: 12 0
SES: 0 0
UAS: 27 27
AS: 55969

Bearer 0
INP: 4.00 0.00
INPRein: 0.00 0.00
delay: 9 0
PER: 1.34 6.15
OR: 142.49 202.87
AgR: 69916.75 20203.27

Bitswap: 21461/21462 24/24

Total time = 15 hours 33 min 16 sec
FEC: 1490858 9
CRC: 50 0
ES: 12 0
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 3 min 16 sec
FEC: 37 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: 769 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 = 15 hours 33 min 16 sec
FEC: 1490858 9
CRC: 50 0
ES: 12 0
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 = 15 hours 32 min 47 sec
FEC: 1490858 9
CRC: 50 0
ES: 12 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Storm Damage?
« Reply #1 on: July 13, 2020, 03:25:48 PM »

A very warm welcome to the forum! Good to have you.

I see you’re running our own kitizen Johnson’s excellent firmware in the ZyXEL modem, as do I in my four ZyXEL VMG1312-B10A modems.

One thing I did notice is that the upstream target SNRM is really high at 9.5 dB. Your downstream SNRM at 6.5 dB is either a tiny bit high or a lot high depending on whether it normally is at a target of 3dB or 6dB. I don’t know how many VDSL2 users get 3dB target SNRM downstream - I’m very ignorant about VDSL2/FTTC, being still on ADSL2.

Those high numbers are presumably just DLM after the storm.

I see a very high interleave depth in your downstream (the D framing parameter) and a large amount of forward error correction in the form of added RS CRC bytes (the R number). Again cautionary protective measures introduced because of the storm. The high value of R is slowing the link down because of added bytes of error correction information in the data stream not just your own data.

If you reset the modem then these numbers might change to something less paranoid. There are not many ES so no problems currently. If the SNRM targets do not drop down when you do so, then it may require waiting until DLM forgets about its fear of the storm.

So what to do. Wait a while, modem off for 30 mins and then back on and then if that has not produced desired effects then it means a lot more waiting, several days, for DLM to forgive you. Other kitizens especially Kitz herself will know how long you typically have to wait in the DLM waiting game.

If you do have any specific questions about the detailed stats, or the meaning and interpretation of the graphs, then do please ask and we will be glad to help.
« Last Edit: July 13, 2020, 03:33:06 PM by Weaver »
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 4099
Re: Storm Damage?
« Reply #2 on: July 13, 2020, 03:29:43 PM »

The upstream is at a 6dB target SNRM.
It's only at a current SNRM of 9dB as the line is reaching the maximum sync of 20Mb.
That leaves 3dB "spare" SNRM.
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Storm Damage?
« Reply #3 on: July 13, 2020, 03:44:49 PM »

Ah, my mistake. I didn’t spot the fact that the upstream was at the maximum. My apologies and thanks to J0hn for spotting that.

So strike everything I said about the upstream. It’s just like that because you have excellent upstream and a good line.

Does the downstream target SNRM normally sit at 3dB or at 6dB?

If it were me I wouldn’t be worried about the large interleave depth, the interleaving mechanism it’s just doing a very good powerful job of protecting you, it doesn’t reduce the rate and merely introduces a small end-to-end delay. As I say, something which wouldn’t bother me but the slight delay is something that some people object to, especially gamers. The larger the interleave depth the greater the range of scenarios in which you are protected from (transient) burst noise.
Logged

MTW

  • Member
  • **
  • Posts: 13
Re: Storm Damage?
« Reply #4 on: July 13, 2020, 04:26:20 PM »

If it's an ECI cab then the minimum downstream target SNRM is 6dB, so you are at or close to your maximum sync with interleaving on (only Huawei cabs will go down to 3dB).

You will have lost some downstream speed due to the interleaving, but hopefully DLM will switch it off if errors remain low. From the graph there are quite a few CRCs, so unfortunately it's not guaranteed.
Logged

boozy

  • Reg Member
  • ***
  • Posts: 130
Re: Storm Damage?
« Reply #5 on: July 13, 2020, 05:41:34 PM »

You may have some star wiring in your circuit  - although the dip is quite small. Follow the bt wiring in your house from ingress to your new master socket as the offending length of wire would be between 7 and 8m in length. It could well be a change in gauge or material elsewhere though.
Logged

boozy

  • Reg Member
  • ***
  • Posts: 130
Re: Storm Damage?
« Reply #6 on: July 13, 2020, 08:59:32 PM »

Actually, just reboot the modem (and it’s not often you’ll hear that) - your max is way above your current throughput and you don’t appear to be banded. You may have resynched while there was still noise from the storm. I’m assuming you took the snapshots within 16 hours from the storm.   :fingers:
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 4099
Re: Storm Damage?
« Reply #7 on: July 13, 2020, 10:07:27 PM »

Actually, just reboot the modem (and it’s not often you’ll hear that) - your max is way above your current throughput and you don’t appear to be banded. You may have resynched while there was still noise from the storm. I’m assuming you took the snapshots within 16 hours from the storm.   :fingers:

I wouldn't recommend that.

Interleaving artificially increases the attainable rate.
The SNRM is 6.6dB  and the target is 6.3dB so very little will be gained by a resync, perhaps none.
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

mofa2020

  • Reg Member
  • ***
  • Posts: 317
Re: Storm Damage?
« Reply #8 on: July 13, 2020, 10:31:00 PM »

I wouldn't recommend that.

Interleaving artificially increases the attainable rate.
The SNRM is 6.6dB  and the target is 6.3dB so very little will be gained by a resync, perhaps none.

Totally correct, the reboot may even encourage DLM to take another action to the line making things more worse than interleaving.. I guess it is a matter of few days of line stability after the storm then DLM would apply fastpath and lower SNRm "which is increased by very little at the moment" in that case a resync. will happen to apply fastpath again and lower the SNRm.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Storm Damage?
« Reply #9 on: July 13, 2020, 10:50:04 PM »

You may have some star wiring in your circuit  - although the dip is quite small.

As nobody has, so far, commented I will mention that I am in agreement with that assessment.

There appears to be a bridging tap present . . . look at the Hlog plot (the logarithmic presentation of the channel characteristics function, H) between sub-carriers 1500 and 2250 (approximately).   
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

h0110

  • Just arrived
  • *
  • Posts: 7
Re: Storm Damage?
« Reply #10 on: July 14, 2020, 10:45:11 AM »

Wow! Thank you all for your replies!

Absolutely loving the Johnson’s firmware :P I have funnily enough bought a VMG1312-B10A yesterday just to do a bit more experimenting!
@boozy & @burakkucat you were both 100% spot on with a Bridge Tap, that was about 7-8m away from what I thought was the master socket...

Turns out what I thought was the master socket was an extension, I've crimped the correct wires together this morning and the graphs looked much better  :) (will post some pictures up a bit later on today)

In terms of crimping wires it feels a bit wrong to me as I'd normally would like to replace the whole wiring from the external junction box (which looks absolutely ancient) - any advice on this?
Logged

boozy

  • Reg Member
  • ***
  • Posts: 130
Re: Storm Damage?
« Reply #11 on: July 14, 2020, 03:38:53 PM »

I wouldn't recommend that.

Interleaving artificially increases the attainable rate.
The SNRM is 6.6dB  and the target is 6.3dB so very little will be gained by a resync, perhaps none.

Ah, I was reading it on a phone and thought there was 9.5...

But removing the tap will have brought it up to 80/20, I would think, possibly with some spare margin.
Logged

h0110

  • Just arrived
  • *
  • Posts: 7
Re: Storm Damage?
« Reply #12 on: July 14, 2020, 08:36:00 PM »

As promised! Here are the pics after the Bridge Tap has been removed, please look post 6am as last night I fluffed it a little bit.

I'm actually really impressed with 0 CRC/ES in the last 12 hours!!

Fingers crossed that DLM will be kind and put me up to the full 80/20 with that dam interlacing off :fingers:









Code: [Select]
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 26851 Kbps, Downstream rate = 93328 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71998 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.4 9.7
Attn(dB): 14.1 0.0
Pwr(dBm): 2.3 2.2

VDSL2 framing
Bearer 0
MSGc: 18 150
B: 48 236
M: 1 1
T: 64 5
R: 16 16
S: 0.0217 0.3771
L: 24016 5410
D: 1533 1
I: 65 255
N: 65 255

Counters
Bearer 0
OHF: 38079119 433927
OHFErr: 0 0
RS: 1158137500 3713368
RSCorr: 396211 4
RSUnCorr: 0 0

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

ES: 32 12
SES: 21 0
UAS: 1421 1400
AS: 52991

Bearer 0
INP: 4.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.39 6.15
OR: 138.01 202.87
AgR: 72135.69 20203.27

Bitswap: 485/485 13/13

Total time = 20 hours 3 min 35 sec
FEC: 1789495 204
CRC: 8652 24
ES: 32 12
SES: 21 0
UAS: 1421 1400
LOS: 2 0
LOF: 10 0
LOM: 0 0
Latest 15 minutes time = 3 min 35 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: 46 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 = 20 hours 3 min 35 sec
FEC: 1789495 204
CRC: 8652 24
ES: 32 12
SES: 21 0
UAS: 1421 1400
LOS: 2 0
LOF: 10 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 = 14 hours 43 min 9 sec
FEC: 396211 4
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
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Storm Damage?
« Reply #13 on: July 14, 2020, 08:43:13 PM »

The Hlog plot is agreeable to my eyes! Well done.  :)
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

h0110

  • Just arrived
  • *
  • Posts: 7
Re: Storm Damage?
« Reply #14 on: July 27, 2020, 09:31:32 AM »

Just wanted to post an update! Had a couple of resyncs and finally back up to 80/20 ;D (last resync was this morning)

Interestingly G.INP seems to be active which wasn't before?! INP is also on the way down, again interestingly seems more active on the Bearer 1??

Code: [Select]
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 25519 Kbps, Downstream rate = 84478 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 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.0 9.5
Attn(dB): 14.1 0.0
Pwr(dBm): 3.1 3.1

VDSL2 framing
Bearer 0
MSGc: -6 150
B: 178 236
M: 1 1
T: 0 5
R: 6 16
S: 0.0000 0.3771
L: 20780 5410
D: 1 1
I: 185 255
N: 185 255
Q: 16 0
V: 2 0
RxQueue: 42 0
TxQueue: 14 0
G.INP Framing: 18 0
G.INP lookback: 14 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 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 2614091
OHFErr: 0 0
RS: 895433776 2328240
RSCorr: 144 0
RSUnCorr: 0 0
Bearer 1
OHF: 996544 0
OHFErr: 0 0
RS: 11957790 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 69426 0
rtx_c: 251 0
rtx_uc: 74424 0

G.INP Counters
LEFTRS: 10 0
minEFTR: 79982 0
errFreeBits: 105722235 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2462594590 0
Data Cells: 75088010 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: 11 11
SES: 11 10
UAS: 64 53
AS: 16013

Bearer 0
INP: 46.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 6.15
OR: 0.01 202.87
AgR: 80111.28 20203.27

Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01

Bitswap: 371/371 15/16

Total time = 14 hours 16 min 53 sec
FEC: 28676 25
CRC: 567 1
ES: 11 11
SES: 11 10
UAS: 64 53
LOS: 1 0
LOF: 7 0
LOM: 0 0
Latest 15 minutes time = 1 min 53 sec
FEC: 13 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: 0 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 = 14 hours 16 min 53 sec
FEC: 28676 25
CRC: 567 1
ES: 11 11
SES: 11 10
UAS: 64 53
LOS: 1 0
LOF: 7 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 26 min 51 sec
FEC: 144 0
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
Logged
Pages: [1] 2