Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: Pottsy on August 23, 2018, 10:00:54 AM
-
Apologies for being slightly non-expert...
FTTC, quiet rural cabinet, 52 down, 9 up. Replaced my HG612 with a VMG8324-B10A in bridged modem-only mode.
When I replaced it, my speed collapsed to 26/8. I left it for 24 hours and restarted. 23/8. Eeek!
Q. What should my strategy be? Leave it (my line never seems to re-sync) or re-start the connection after a certain period?
Another oddity - when I restarted the connection on the VMG8324 (using xdslctl command --down / --up), the max obtainable speed showed 26 (with a SNR of 4) and it took a couple of minutes to rise... Is that why it insists on syncing at 20 something? Is my modem dodgy in any way?
Stats below (the resyncs recorded were my re-starting my HG612 as it was unstable).
Many thanks!
Stats summary
Stats recorded 23 Aug 2018 08:50:53
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039v.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 2 days 4 hours 6 min 51 sec
Resyncs: 4 (since 29 Jul 2018 12:48:31)
Downstream Upstream
Line attenuation (dB): 22.7 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 23538 8220
SNR margin (dB): 22.6 7.8
Power (dBm): 13.0 5.9
Interleave depth: 4 1
INP: 50.00 0
G.INP: Enabled Not enabled
Vectoring status: 1 (VECT_FULL)
RSCorr/RS (%): 0.0000 0.0680
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Connection stats
xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 8172 Kbps, Downstream rate = 57536 Kbps
Bearer: 0, Upstream rate = 8220 Kbps, Downstream rate = 23538 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): 22.6 7.8
Attn(dB): 22.7 0.0
Pwr(dBm): 13.0 5.9
VDSL2 framing
Bearer 0
MSGc: -6 52
B: 227 237
M: 1 1
T: 0 33
R: 14 16
S: 0.0000 0.9195
L: 6284 2210
D: 4 1
I: 242 127
N: 242 254
Q: 4 0
V: 0 0
RxQueue: 56 0
TxQueue: 14 0
G.INP Framing: 18 0
G.INP lookback: 14 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 201857
OHFErr: 0 3
RS: 2425730292 64681
RSCorr: 697 44
RSUnCorr: 0 0
Bearer 1
OHF: 11677073 0
OHFErr: 0 0
RS: 70062070 0
RSCorr: 27 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 25036459 0
rtx_c: 111 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 1 0
minEFTR: 23534 0
errFreeBits: 123666538 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4195131101 0
Data Cells: 92103444 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 6
SES: 0 0
UAS: 176 176
AS: 187611
Bearer 0
INP: 50.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 15.23
OR: 0.01 30.46
AgR: 23589.70 8250.91
Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01
Bitswap: 23746/24122 759/763
Total time = 2 days 23 hours 26 min 19 sec
FEC: 791 61
CRC: 0 8
ES: 0 6
SES: 0 0
UAS: 176 176
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 11 min 19 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: 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 = 23 hours 26 min 19 sec
FEC: 629 28
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 36 15
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 days 4 hours 6 min 51 sec
FEC: 697 44
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>
-
If the HG612 was giving a decent connection, why replace it with another in bridge mode?
-
It had a habit of getting more and more flaky over a couple of weeks, and needed a restart. SNR margin would gradually decrease and errors increase - the restart would sync at the same speed but then all else was back to normal. I assumed (I know...) that this may have been to some instability in the custom firmware, and that the 8324 would be better (and possibly faster).
Of course, I could be wrong! But I'd hope that at the very least the new modem would kind of work properly.
-
I believe it to be a Vectoring issue.
Johnson should be along shortly. I believe he's built a firmware image for the 8924 with a newer adsl.phy which fixes various Vectoring issues.
Perhaps try uploading the firmware he'll link you to and give that a shot.
It will also give you the ability to set a 1508 MTU (aka baby jumbo frames) and multiple telnet sessions.
Failing that it's probably a dufff modem.
-
This does sound like it might be the same vectoring issue I have experienced, however with my line a sync from a full reboot of the modem was at full speed, I only experienced the half speed reconnects when a new sync happened without a reboot, i.e "xdslctl configure", DLM intervention or pulling the cable out.
But other than that you seem to be getting pretty much exactly half what you should and have vectoring, so give this firmware a go:
https://www.dropbox.com/s/5axi4otbtjztno3/8924-B10A-oldtelnet-3925.bin?dl=0
It has the newer x1 adsl_phy and fixed these problems with my vectored line. Ignore the 8924 naming, the 8924 and 8324 share firmware.
Edit: Another thing I notice looking at your stats is that the attainable is still what it should be, ie 57, which again is different from my experience, my attainable would halve as well. Hmm... still give the firmware a go if its not too much trouble, but its possible you have a duff 8324.
-
Johnson,
Thank you.
I uploaded the firmware through the GUI - and yet it didn't ask for a reboot. I rebooted it manually (via the GUI) and no change. DSLStats reports the modem firmware the same as A2pv6F039v.d26a, so I think my VMG didn't like the look of your firmware!
-
Thats most odd Pottsy. The process of flashing always results in a reboot, so it sounds like that never happened.
After selecting the new firmware from "Browse" you did click "Upload" right?
-
I did click upload, and I watched the little percentage go up at the bottom left of Chrome, then there was a wait while the GUI had a think about things, then back to where we started (firmware page).
This is a new router, so I have previously done 1 firmware update on it (to bring it up to date) which worked as expected.
-
Need to look at what Johnson said first though obviously. Because if a bug has been triggered then all bets are off.
Otherwise, the standard observation.
The downstream SNRM on that modem was absolutely massive, way way too high and if not the bug then that is the cause of the low downstream sync speed. So replacing one question with another: why then the ridiculously high downstream SNRM ? Angered the DLM gods for some reason ? Sometimes too much switching off and on without waiting 30 minutes of off time.
Question: Is it happy with the old modem right now? Because if not then you need a DLM reset? If you change back to the old modem, that means power off first not unplugging first (just in case, Kitz says it makes no difference so this is just superstition on my part) then 30 min of off time in order to enclose the n * 15 to (n+1) * 15 min time boundaries with the modem off during that whole 15 min period - eg off from 09:14 to 09:31 to enclose the 09:15-09:30 time period, or another example if the time were 09:16, then off throughout 09:16-09:46 would be needed to enclose the period 09:30-09:45. So it means doing that procedure twice if switching modems twice, to the old one then back.
-
Back to the HG612. I'll report back later when I return to the 8324.
(HG612 works fine, but I do seem to have collected a 25Mb ip profile, but I imagine that will go soon).
Stats summary
Stats recorded 24 Aug 2018 06:04:35
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 12 min 13 sec
Resyncs: 6 (since 29 Jul 2018 12:48:31)
Downstream Upstream
Line attenuation (dB): 22.6 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 54395 9837
SNR margin (dB): 4.2 6.7
Power (dBm): 12.6 6.5
Interleave depth: 4 1
INP: 54.00 0
G.INP: Enabled Not enabled
Vectoring status: 1 (VECT_FULL)
RSCorr/RS (%): 0.0575 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Connection stats
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 9826 Kbps, Downstream rate = 55564 Kbps
Bearer: 0, Upstream rate = 9837 Kbps, Downstream rate = 54395 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): 4.2 6.7
Attn(dB): 22.6 0.0
Pwr(dBm): 12.6 6.5
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 237
M: 1 1
T: 0 44
R: 10 16
S: 0.1333 0.7688
L: 14282 2643
D: 4 1
I: 238 127
N: 238 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 86442
OHFErr: 0 0
RS: 21847732 3802922
RSCorr: 12553 0
RSUnCorr: 0 0
Bearer 1
OHF: 45571 0
OHFErr: 0 0
RS: 364077 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 25036599 0
rtx_c: 0 0
rtx_uc: 410 0
G.INP Counters
LEFTRS: 1 0
minEFTR: 54399 0
errFreeBits: 607121 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 76539257 0
Data Cells: 530230 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: 82 82
AS: 733
Bearer 0
INP: 54.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.49
OR: 0.01 30.15
AgR: 54514.71 9867.50
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: 289/304 2/2
Total time = 13 min 35 sec
FEC: 12553 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 13 min 35 sec
FEC: 12553 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes 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
Latest 1 day time = 13 min 35 sec
FEC: 12553 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
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 = 12 min 11 sec
FEC: 12553 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
So I took my 8324 off the line to test the firmware linked above. It took a lot longer than normal once I hit the upload button, on the order or 3 minutes or so vs normal 50 ish seconds, but it flashed fine. I could not replicate the long flash behaviour when going back to my normal firmware and to the one linked.
The screen should look like this:
(https://i.imgur.com/ZC6TPdQ.jpg)
For a little under a minute, then:
(https://i.imgur.com/Uy1LNk6.jpg)
If you still cant seem to flash the one linked then could you please try this newer one based on the v24 release:
https://www.dropbox.com/s/mfswb0u6xnlhira/8924-B10A-AAKL24-jumboframes-oldtelnet-customcmds-x1.bin?dl=0
Edit: also no need to have you 8324 on the line to try these, no need for more resyncs to anger the DLM.
-
Johnson, I'll give it a go now.
My line does not have an ip profile, but is stuck....
-
Johnson,
That second one worked fine. :)
Now - half and hour or so before I can report back.....
-
Didn't work. Connection speed now 15!
This is the second 8324 I have tried, the first handed out DHCP addresses but had no web configuration page.
I'll just stick with the HG612 and file the 8324 in the round file.
Thank you all for being so hospitable and for the time you have spent helping. :)
Stats summary
Stats recorded 24 Aug 2018 07:25:32
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039x1.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 4 min 20 sec
Resyncs: 7 (since 29 Jul 2018 12:48:31)
Downstream Upstream
Line attenuation (dB): 23.2 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 15991 4404
SNR margin (dB): 25.3 8.2
Power (dBm): 13.2 5.3
Interleave depth: 4 1
INP: 51.00 0
G.INP: Enabled Not enabled
Vectoring status: 1 (VECT_FULL)
RSCorr/RS (%): 0.0007 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Connection stats
xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 4401 Kbps, Downstream rate = 52550 Kbps
Bearer: 0, Upstream rate = 4404 Kbps, Downstream rate = 15991 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): 25.3 8.2
Attn(dB): 23.2 0.0
Pwr(dBm): 13.2 5.3
VDSL2 framing
Bearer 0
MSGc: -6 58
B: 146 126
M: 1 1
T: 0 30
R: 16 16
S: 0.0000 0.9187
L: 4473 1254
D: 4 1
I: 163 72
N: 163 144
Q: 4 0
V: 1 0
RxQueue: 60 0
TxQueue: 15 0
G.INP Framing: 18 0
G.INP lookback: 15 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 18808
OHFErr: 0 0
RS: 3526208 1128269
RSCorr: 26 0
RSUnCorr: 0 0
Bearer 1
OHF: 16124 0
OHFErr: 0 0
RS: 96374 0
RSCorr: 1 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 25036605 0
rtx_c: 2 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 15990 0
errFreeBits: 63120 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 7964673 0
Data Cells: 42738 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: 83 83
AS: 260
Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 13.83
OR: 0.01 37.01
AgR: 16072.94 4441.31
Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01
Bitswap: 78/78 1/1
Total time = 5 min 43 sec
FEC: 26 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 83 83
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 5 min 43 sec
FEC: 26 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 83 83
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes 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
Latest 1 day time = 5 min 43 sec
FEC: 26 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 83 83
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 min 19 sec
FEC: 26 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
>
-
Wow, have never seen a modem (let alone 2) have such a negative impact.
Apologies that the firmware did not help, and seems to have made things worse. :(
Can I ask where you got your 8324 from?
-
I'm embarrassed to say - here: https://www.ebay.co.uk/itm/173427595328
I can only assume that this is a hardware fault.
-
Is there an option for toggling vectoring support on/off on the Zyxel?
-
I'm embarrassed to say - here: https://www.ebay.co.uk/itm/173427595328
I can only assume that this is a hardware fault.
That exact listing? I would definitely contact the seller and ask for a return, its within time and the item is faulty.
-
Already contacted!
-
Is there an option for toggling vectoring support on/off on the Zyxel?
I do not believe so mitchy, here are the possible options from xdslctl:
xdslctl connection [--up] [--down] [--loopback] [--reverb]
[--medley] [--noretrain] [--L3] [--diagmode] [--L0]
[--tones <r1-r2,r3-r4,...>] [--normal] [--freezeReverb] [--freezeMedley]
xdslctl configure/configure1 [--mod <a|d|l|t|2|p|e|m|M3|M5|v>] [--lpair <(i)nner|(o)uter>]
[--trellis <on|off>] [--snr <snrQ4>] [--bitswap <on|off>] [--sesdrop <on|off>]
[--sra <on|off>] [--CoMinMgn <on|off>] [--i24k <on|off>] [--phyReXmt <0xBitMap-UsDs>]
[--Ginp <0xBitMap-UsDs>] [--TpsTc <0xBitMap-AvPvAaPa>] [--monitorTone <on|off>]
[--profile <0x00 - 0xFF>|<"8a |8b |8c |8d |12a |12b |17a |30a">] [--us0 <on|off>]
[--dynamicD <on|off>] [--dynamicF <on|off>] [--SOS <on|off>] [--maxDataRate <maxDsDataRateKbps maxUsDataRateKbps maxAggrDataRateKbps>]
And the GUI certainly has no mention of vectoring.
-
I wasn't sure, I remember there being several options that you could toggle but couldn't recall if vectoring was one of them. Thanks
-
Already contacted!
I would make sure to flash the stock v.24 firmware and maybe go to the data partition and delete the "bootcmds.sh" file my firmware has created, just as a super paranoid precaution, before returning. Its unlikely the seller will interrogate the item anywhere near close enough to catch these, but best to be safe.
-
I'll return it to standard. The vendor should be pleased I have tried everything before returning it!
Is there such a thing as a quick and stable modem? Vigor 130 is slow but stable, and my HG612 is quick but unstable.
-
Believe me your experience with the 8324 is atypical. I run one on my line and its the both the highest syncing and most stable I have tried, out of many.
If you have been put off zyxel modems (understandably so) then for cheap you could try a Billion 8800NL v1 next. I have one and it was super stable, the modem code it uses did not exhibit the strange bug with vectoring, and just a bit lower sync than the zyxels.
Edit: 2 on the auction site for around £25 atm, can be had cheaper if you wait, but they are there.
I'd add that the Billion uses the same BCM63168 chipset that makes the zyxels good and is only missing the nice noise filter on the line input.
-
I'm convinced the problem was related to Vectoring. It definitely wasn't a DLM thing.
Although a slightly different bug to what Johnson had on his line, similar to what half a dozen or so other Vectoring lines have shown in the past.
I was hoping the newer DSL driver would have fixed it but unfortunately not.
It would be a no no for a GUI to offer the ability to disable Vectoring. It goes against the whole purpose of Vectoring.
Modems on a cabinet they can't Vector or aren't Vectoring friendly make enough noise on their own without poorly configured CPE adding to that.
-
I'm convinced the problem was related to Vectoring. It definitely wasn't a DLM thing.
Although a slightly different bug to what Johnson had on his line, similar to what half a dozen or so other Vectoring lines have shown in the past.
I was hoping the newer DSL driver would have fixed it but unfortunately not.
It would be a no no for a GUI to offer the ability to disable Vectoring. It goes against the whole purpose of Vectoring.
Modems on a cabinet they can't Vector or aren't Vectoring friendly make enough noise on their own without poorly configured CPE adding to that.
Makes sense when you put it like that John.
-
Wow thats not good :'(
Connection speed (kbps): 15991 4404
SNR margin (dB): 25.3 8.2
There's loads of Margin, so why isn't the modem allocating it to the sync speed, if the modem is displaying Vectoring status: 1 (VECT_FULL)
It's almost like the DSLAM has determined its running in Vector_Friendly mode rather than Full and thus only given it standard VDSL speed?
The odd thing is the VMG8324 passed Openreach's MCT. Vectoring is one of the things they test for.
5.
Compare the results obtained using the CPE at each cable length against those
obtained using the 48 BT provided CPE. Note whether the CPE under test
supports vectoring and whether there is any significant drop in performance
either to the modem or the rest of the vector group when vectoring is enabled.
Expected Outcome – “Pass” if modem is capable of supporting vectoring and does not
adversely affect the performance of the vector group, “Fail” if not.
The f/w version they tested was 1.00(AAKL.10)C0_0703
It would be a no no for a GUI to offer the ability to disable Vectoring. It goes against the whole purpose of Vectoring.
I agree with this ^. I'm sure there was a post on here a few years back when someone with a different modem tried to turn off Vectoring support and it wouldn't sync.
-
So try this firmware version Pottsy, as per Kitz:
1.00(AAKL.10)C0_0703
-
I'm sure there was a post on here a few years back when someone with a different modem tried to turn off Vectoring support and it wouldn't sync.
I think I remember reading something about this actually.
I just mentioned it as a possibility of something like that being disabled by default in the GUI. I couldn't remember the options inside the Zyxel so it was a bit of a guess if it even existed.
-
So try this firmware version Pottsy, as per Kitz:
1.00(AAKL.10)C0_0703
I certainly think trying older firmware is a good idea. I know I keep harping on about my vectoring issues, but an older firmware on a 1312 also fixed my issue, it was just less stable (lots of overnight sync drops) so I stopped using it. It had the o1 dsl code I believe.
I cant find AAKL.10 on the Zyxel ftp, but Pottsy once you have waited a day or so and can try some more resyncs, I would try either of these:
A2pv6F039i :
ftp://ftp2.zyxel.com/VMG8324-B10A/firmware/VMG8324-B10A_1.00(AAKL.7)C0.zip
A2pv6F039o1 :
ftp://ftp2.zyxel.com/VMG8924-B10A/firmware/VMG8924-B10A_1.00(AAKL.13)C0.zip
-
Kitz, Johnson, everyone - thank you. ;D
I went vintage, and chose .7 rather than .13
The GUI won't load in Chrome (stuck on the ...loading gif), but I don't care. It works at a snails pace in Edge.
My Vigor connected at 49. My HG612 at 54 (showing max 56). Now I am connected at 61.
:)
Stats summary
Stats recorded 25 Aug 2018 08:19:08
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039i.d24e
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 7 min 22 sec
Resyncs: 9 (since 29 Jul 2018 12:48:31)
Downstream Upstream
Line attenuation (dB): 0.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 61403 9731
SNR margin (dB): 5.0 7.0
Power (dBm): 12.5 6.8
Interleave depth: 4 1
INP: 56.00 0
G.INP: Enabled Not enabled
Vectoring status: 1 (VECT_FULL)
RSCorr/RS (%): 0.0003 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
Connection stats
xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 9779 Kbps, Downstream rate = 64216 Kbps
Bearer: 0, Upstream rate = 9731 Kbps, Downstream rate = 61403 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
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.0 7.0
Attn(dB): 0.0 0.0
Pwr(dBm): 12.5 6.8
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 244 237
M: 1 1
T: 0 41
R: 10 16
S: 0.1265 0.7771
L: 16122 2615
D: 4 1
I: 255 127
N: 255 254
Q: 4 0
V: 3 0
RxQueue: 140 0
TxQueue: 28 0
G.INP Framing: 18 0
G.INP lookback: 28 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 55415
OHFErr: 0 0
RS: 13855056 2270660
RSCorr: 41 0
RSUnCorr: 0 0
Bearer 1
OHF: 27455 0
OHFErr: 0 0
RS: 273930 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 25054153 0
rtx_c: 6 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 61404 0
errFreeBits: 412967 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 52074312 0
Data Cells: 623850 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: 82 82
AS: 442
Bearer 0
INP: 56.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 7.99
OR: 0.01 32.01
AgR: 61717.97 9762.96
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: 82/89 5/5
Total time = 8 min 44 sec
FEC: 41 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 44 sec
FEC: 41 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes 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
Latest 1 day time = 8 min 44 sec
FEC: 41 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 82 82
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 = 7 min 21 sec
FEC: 41 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
-
Great stuff. Perhaps Johnson will be able to give a bit more insight to the reason why.
-
GUI issues fixed by clearing the cache (pretty obvious stuff really, should have thought of that, especially with a firmware reversion).
-
Result! ;D
Great stuff. Perhaps Johnson will be able to give a bit more insight to the reason why.
I have no more of a clue than anyone, have just tried as many different firmwares on as many different modems as I could.
A2pv6F039i.d24e
This is both an older adsl_phy and an old kernel driver. In fact this is exactly the same version as the (now very old) latest stable firmware for the Billion 8800NL v1 uses.
So it seems some regression or new bug has happened in BCM DSL code for vectoring, in my case its half speed syncs after "hot" reconnects but in Pottsy's case its half speed or worse in all cases. From my testing this started with the A2pv6F039v.d26a combination, any early ones work as intended, and later in A2pv6F039x1.d26a.
If you stick around and are willing to test things Pottsy (once you have let your line settle after all these forced resyncs) it would be great to see if a firmware with an earlier adsl_phy eg A2pv6F039o1 with the later kernel driver i.e d26a vs d24e you are running now still fixes things for your particular line.
Either or, if you would like I'm sure we can cook up a latest version firmware with the correct combination of adsl_phy and kernel driver to suit your line.
Edit: Adding that we are on the same SW version at the cab:
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039x1.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
-
Johnson,
I'll be back, but I'm going to let it settle for a week or two first if that's OK. I had the 8324 in place for about a week at connection speed of 25, and now my line seems capped at 25 actual d/l speed. So I'm hoping that leaving it in a relaxed state will allow the angry gremlin to allow d/l at full speed after a while.
The cabinet I connect to is fairly new (spring 2016) - but I have seen one other oddity which may be related. Vigor publish a firmware with an "alternative modem code" to replace the (very) old modem code in their current firmware. I tried it once, and it wouldn't sync at all. I wonder if there's something odd going on in the cab - because who would publish modem code that either didn't work at all (Vigor) or made a complete mess (Zyxcel/BC)?
-
The stuck downloads sounds like an IP profile issue.
Visit this site (https://windows.mouselike.org/be/index.asp?DoAction=BrasChecker) and enter your landline number. It takes about 30 seconds but will give you your current IP profile.
-
56.89/20.
I'll call the ISP (PN) later.
-
As I thought, a quick call to PN to get the profile "unstuck".
Now all working perfectly - a few disconnects and resyncs though, it looks like it is doing the "I've detected new equipment and I'm going to experiment on you for 24 hours"...
Actual d/l of 59 is 12 faster than I have ever seen here, so very worthwhile.
-
:yay:
-
Johnson,
As a follow up, I think I'll adhere to the "not broken / no fixing" rule - thank you. That .7 firmware is rock solid and very fast. To be fair, in bridge mode with everything switched off, the box isn't really doing very much so not many fixes to miss out on. I don't even bother looking at the web UI....
Vigor 130 (slow) vs HG612 vs VMG8324 (attached)
That graph is from an agent sitting on a NAS doing 4 speed tests a day, using non optimised download sites. Because this is on the home network, if others are hammering it then it shows a trough. However, the results are pretty clear!
-
Interesting to see how the ZyXEL modem has made such an improvement. An interesting read.