Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: JamesK on September 13, 2018, 08:39:53 PM
-
Hi All,
Further to my previous post I've just had my line moved from an ECI to Huawei cabinet. Straight away my line speeds were better than with the ECI, with the line syncing at 38mb. Almost exactly 48 hours after the line was activated, it resync'd, and enabled G.Inp. My stats now show the line speed as being nearly 44mb. However, speed tests are still showing speeds of around 36 which I was surprised about.
Can anyone tell me if this is normal, and if the line stats below look good? Attached a few pics from DSLstats as well. At the moment I'm still using the HG612, but plan on swapping this out for a VMG1312-B10A over the next few days.
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 19 hours 21 min 55 sec
Resyncs: 1 (since 10 Sep 2018 19:01:41)
Downstream Upstream
Line attenuation (dB): 23.3 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 43972 9999
SNR margin (dB): 6.3 8.0
Power (dBm): 11.0 6.8
Interleave depth: 8 1
INP: 49.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0081 0.0069
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 1.02 0.54
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 11752 Kbps, Downstream rate = 43588 Kbps
Bearer: 0, Upstream rate = 9999 Kbps, Downstream rate = 43972 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): 6.3 8.1
Attn(dB): 23.3 0.0
Pwr(dBm): 11.0 6.8
VDSL2 framing
Bearer 0
MSGc: -6 58
B: 243 236
M: 1 1
T: 0 23
R: 10 16
S: 0.1767 0.7543
L: 11500 2694
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 36 0
TxQueue: 12 0
G.INP Framing: 18 0
G.INP lookback: 12 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 314385
OHFErr: 60 11
RS: 1574713936 968745
RSCorr: 127469 23
RSUnCorr: 0 0
Bearer 1
OHF: 4347641 0
OHFErr: 0 0
RS: 26085479 0
RSCorr: 96 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 12957 0
rtx_c: 8187 0
rtx_uc: 103 0
G.INP Counters
LEFTRS: 55 0
minEFTR: 43973 0
errFreeBits: 46831873 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1609872551 0
Data Cells: 25025099 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: 119 36
SES: 18 0
UAS: 1589 1578
AS: 69835
Bearer 0
INP: 49.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.70
OR: 0.01 58.79
AgR: 44017.03 10057.90
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: 31192/31193 18/18
Total time = 1 days 2 hours 2 min 48 sec
FEC: 2200328 91
CRC: 5348 36
ES: 119 36
SES: 18 0
UAS: 1589 1578
LOS: 1 0
LOF: 8 0
LOM: 0 0
Latest 15 minutes time = 2 min 48 sec
FEC: 43 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: 156 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 = 2 hours 2 min 48 sec
FEC: 41955 3
CRC: 4 2
ES: 1 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 368225 30
CRC: 3855 12
ES: 30 12
SES: 14 0
UAS: 36 25
LOS: 1 0
LOF: 8 0
LOM: 0 0
Since Link time = 19 hours 23 min 55 sec
FEC: 127469 23
CRC: 60 11
ES: 9 11
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
[Moderator edited to replace [quote][/quote] tags with [code][/code] tags.]
-
A few more graphs added
-
Just wait another 48hrs, you should get 5dB from DLM. Then another 48hrs later 4dB etc... until you get 3dB.
Then check your IP/BRAS profile and if needs be: leave your modem & router off overnight.
Next morning you can power up and you will still be on 3dB with a matching IP/BRAS profile.
Just be patient for now though, let DLM work its magic.
-
Out of interest what were the sync figures on the ECI cabinet with fastpath?
Do you have a copy of the ECI bitloading? Is it the same pair?
With my change from ECI to Huawei, on the same pair...
ECI
Fastpath/6dB: 55 down 6.8 up
Huawei
Fastpath/6dB: 54 down 11 up
Upstream was the biggest initial gain for me with the Huawei performing MUCH better.
3dB didn't come along till after crosstalk did its work on my line and knocked me down under 40Mb.
I'm currently synced at 45Mb @ 3dB
I was the very 1st line on my Huawei, which was added as our ECI was full.
It's no surprise I lost 18Mb to crosstalk (3dB gave me 8Mb back so overall I'm 10Mb down) as the Huawei cabinet filled very quickly.
It now has an HD expansion after less than 18 months.
The ECI took 4 years to fill.
[attachment deleted by admin]
-
Out of interest what were the sync figures on the ECI cabinet with fastpath?
Do you have a copy of the ECI bitloading? Is it the same pair?
With my change from ECI to Huawei, on the same pair...
ECI
Fastpath/6dB: 55 down 6.8 up
Huawei
Fastpath/6dB: 54 down 11 up
Upstream was the biggest initial gain for me with the Huawei performing MUCH better.
I didn't think to take a copy of the ECI stats before the line ceased. I really should've done. However, I found some historical data I kept from a couple of years ago, and the upstream/downstream rates remained static for the last few years. The comparison is as follows:
ECI
Fastpath/6dB: 38 down 9 up
Huawei
G.Inp/6dB: 44 down 11 up
So, in my case there's definite improvement in the upstream and downstream. But previously the ECI never sync'd at over 9 on the upstream, even when first installed in 2012.
Two OR engineers visited on the day of activation. The 1st had an apprentice with him, and prepared a 2nd line, and did the work at the cabinet. He said he needed a "UG engineer" to complete the work as he wasn't allowed to finish the job due to having the apprentice with him. When the 2nd engineer turned up, he just used my original line (no idea why). According to him I am the only person connected to the Huawei at present. I'd be surprised if this cabinet filled quickly. It took 6 years for ECI cabinet to fill. They've installed a large Huawei cabinet... so maybe there is the demand, or maybe there's a plan to decom the ECI.
I've run a speed test this morning, and I'm now getting nearly 41mb. I haven't seen speeds like that since the ECI cabinet first went live in 2012. The absolute maximum I managed to get was 42/43mb and that soon dropped as the cabinet filled up.
There's been no further DLM interventions overnight.
-
Hi all. It was going well with resyncs every 48 hours. The line seemed solid on 4dB, and I was expecting another resync tomorrow to get to 3dB. However, tonight at around 19:25 I had a resync (Retrain Reason 1). There was a drop in SNRM at around 17:30, but it didn't cause a resync. I couldn't see any other dips in SNRM scrolling back through the DSLstats data.
G.Inp is still active, but downstream SNRM is sitting at 6.9dB. I've attached a couple of screenshots...
Stats:
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 1 hour 12 min 51 sec
Resyncs: 3 (since 14 Sep 2018 08:16:32)
Downstream Upstream
Line attenuation (dB): 23.4 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 42733 9999
SNR margin (dB): 6.8 7.7
Power (dBm): 11.2 6.7
Interleave depth: 4 1
INP: 52.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0722 0.0004
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 2.87 1.07
Telnet Stats:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 11472 Kbps, Downstream rate = 47596 Kbps
Bearer: 0, Upstream rate = 9999 Kbps, Downstream rate = 42733 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): 6.8 7.7
Attn(dB): 23.4 0.0
Pwr(dBm): 11.2 6.7
VDSL2 framing
Bearer 0
MSGc: -6 58
B: 227 236
M: 1 1
T: 0 23
R: 10 16
S: 0.1697 0.7543
L: 11220 2694
D: 4 1
I: 238 127
N: 238 254
Q: 4 0
V: 0 0
RxQueue: 104 0
TxQueue: 26 0
G.INP Framing: 18 0
G.INP lookback: 26 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 489989
OHFErr: 18 3
RS: 99765296 1058299
RSCorr: 74026 6
RSUnCorr: 0 0
Bearer 1
OHF: 264591 0
OHFErr: 0 0
RS: 1587175 0
RSCorr: 37 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 1282182 0
rtx_c: 706956 0
rtx_uc: 163709 0
G.INP Counters
LEFTRS: 954 0
minEFTR: 42737 0
errFreeBits: 1073085360 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 348984857 0
Data Cells: 16702622 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: 319 163
SES: 168 11
UAS: 1706 1652
AS: 4251
Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.70
OR: 0.01 58.79
AgR: 42826.99 10057.90
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: 3537/3538 10/10
Total time = 1 days 1 hours 59 min 45 sec
FEC: 6296177 11969
CRC: 9370 191
ES: 319 163
SES: 168 11
UAS: 1706 1652
LOS: 4 0
LOF: 36 0
LOM: 0 0
Latest 15 minutes time = 14 min 45 sec
FEC: 37157 1
CRC: 18 1
ES: 3 1
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 89 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 59 min 45 sec
FEC: 126516 10
CRC: 932 5
ES: 23 5
SES: 23 0
UAS: 46 25
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 2039035 40
CRC: 1272 22
ES: 60 21
SES: 50 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 hours 10 min 49 sec
FEC: 74026 6
CRC: 18 3
ES: 3 3
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
G.INP Status
Downstream Upstream
General
rtx_tx 1282182 0
rtx_c 706956 0
rtx_uc 163709 0
LEFTRS 954 0
minEFTR 42737 0
errFreeBits 1073124455 0
Bearer 0
RxQueue 104 0
TxQueue 26 0
G.INP Framing 18 0
G.INP Lookback 26 0
RRC Bits 0 24
Interleave depth 4 1
INP 52.00 0.00
INPRein 1.00 0.00
Delay 0 0
Bearer 1
Interleave depth 1 0
INP 2.50 0.00
INPRein 2.50 0.00
Delay 0 0
What does this mean in terms of getting down to 3dB. Has DLM given up? Or will it try again? I was pretty surprised to see the resync happen tonight, it seems quite an aggressive response by DLM.
I'll probably swap out the HG612 for the VMG1312-B10A tomorrow.
-
There was a drop in SNRM at around 17:30, but it didn't cause a resync.
I make it to be around 1751 - 1752 hours.
What does this mean in terms of getting down to 3dB. Has DLM given up? Or will it try again? I was pretty surprised to see the resync happen tonight, it seems quite an aggressive response by DLM.
Not necessarily so. It may just have been a one-off event and the DLM process will continue its tests.
I'll probably swap out the HG612 for the VMG1312-B10A tomorrow.
It might be sensible not to do that. Just wait a while and see what the DLM does next.
-
Somewhat surprisingly DLM intervened again at around 4:45am. SNRM has been dropped straight down to 3dB. Really not sure why I had the resync last night.
Is there anything else I need to do in the future... I'd seen some posts about capping the line to go from ReTx High to ReTx Low...
Stats recorded 19 Sep 2018 08:09:34
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 3 hours 21 min 52 sec
Resyncs: 4 (since 14 Sep 2018 08:16:32)
Downstream Upstream
Line attenuation (dB): 23.4 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 51063 9999
SNR margin (dB): 3.2 7.3
Power (dBm): 11.5 6.8
Interleave depth: 4 1
INP: 52.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0402 0.0001
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 1.84 0.98
Downstream Upstream
General
rtx_tx 1302967 0
rtx_c 721780 0
rtx_uc 221984 0
LEFTRS 973 0
minEFTR 51050 0
errFreeBits 1471803646 0
Bearer 0
RxQueue 124 0
TxQueue 31 0
G.INP Framing 18 0
G.INP Lookback 31 0
RRC Bits 0 24
Interleave depth 4 1
INP 52.00 0.00
INPRein 1.00 0.00
Delay 0 0
Bearer 1
Interleave depth 1 0
INP 2.00 0.00
INPRein 2.00 0.00
Delay 0 0
dslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 11020 Kbps, Downstream rate = 50800 Kbps
Bearer: 0, Upstream rate = 9999 Kbps, Downstream rate = 51063 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.3 7.3
Attn(dB): 23.4 0.0
Pwr(dBm): 11.5 6.8
VDSL2 framing
Bearer 0
MSGc: -6 58
B: 227 236
M: 1 1
T: 0 23
R: 10 16
S: 0.1420 0.7543
L: 13407 2694
D: 4 1
I: 238 127
N: 238 254
Q: 4 0
V: 0 0
RxQueue: 124 0
TxQueue: 31 0
G.INP Framing: 18 0
G.INP lookback: 31 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 1431178
OHFErr: 8 2
RS: 348179564 1391023
RSCorr: 139359 6
RSUnCorr: 0 0
Bearer 1
OHF: 772669 0
OHFErr: 0 0
RS: 6180856 0
RSCorr: 40 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 1302961 0
rtx_c: 721774 0
rtx_uc: 221984 0
G.INP Counters
LEFTRS: 973 0
minEFTR: 51050 0
errFreeBits: 1471710167 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1218592645 0
Data Cells: 8751938 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: 336 175
SES: 180 11
UAS: 1742 1677
AS: 12412
Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.70
OR: 0.01 58.79
AgR: 51174.82 10057.90
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: 6064/6064 7/7
Total time = 1 days 13 hours 41 min 45 sec
FEC: 6527247 11994
CRC: 9962 203
ES: 336 175
SES: 180 11
UAS: 1742 1677
LOS: 5 0
LOF: 42 0
LOM: 0 0
Latest 15 minutes time = 11 min 45 sec
FEC: 6178 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: 8311 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 hours 41 min 45 sec
FEC: 357586 35
CRC: 1524 17
ES: 40 17
SES: 35 0
UAS: 82 50
LOS: 2 0
LOF: 15 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 2039035 40
CRC: 1272 22
ES: 60 21
SES: 50 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 hours 26 min 51 sec
FEC: 139359 6
CRC: 8 2
ES: 4 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
Is there anything else I need to do in the future... I'd seen some posts about capping the line to go from ReTx High to ReTx Low...
I suggest waiting for j0hn's advice. I'm sure he'll be along in due course. :)
-
I would set
xdslcmd configure --maxDataRate 40000 10000 100000
As your line is already at 3dB it is ok to add the cap now or anytime you like.
Seems like most lines need the cap to get to ReTx Low and so far nobody has posted back to say it has gone back to Retx High again.
-
I would set
xdslcmd configure --maxDataRate 40000 10000 100000
As your line is already at 3dB it is ok to add the cap now or anytime you like.
Seems like most lines need the cap to get to ReTx Low and so far nobody has posted back to say it has gone back to Retx High again.
Thanks j0hn. I'll probably leave it for a few days until the line settles down. This afternoon and tonight the line experienced a 3/4 minute dip in SNRM down to 1dB. The modem didn't lose sync, and it wasn't until DLM forced a resync that noticed there was a problem. I then get bumped back up to 6dB. See attachment for this evenings resync.
I'm surprised that DLM is forcing a resync, approximately 70ish minutes after the drop in SNRM, especially considering the modem isn't losing sync when this happens.
Anyone got any thoughts on this?
-
I'm going to throw a wild 1 out here...
I'm not 100% that it did set you back to a 6dB target the last time, or this time.
I've only ever seen DLM move the target SNRM in 1dB increments, up and down.
The last time your SNRM jumped back up it went up by 3dB, from the target 4dB to 7dB.
Then the next change it went down to 3dB.
If you look when it was at 6.8dB...
Max: Upstream rate = 11472 Kbps, Downstream rate = 47596 Kbps
Bearer: 0, Upstream rate = 9999 Kbps, Downstream rate = 42733 Kbps
That attainable suggests a 4dB target SNRM
When your target SNRM goes back to 6dB, and you sync at 6dB, the sync is just below the attainable, they match.
You haven't posted your current stats, but if I'm right then you will be synced around 44Mb, but your attainable is still around 51Mb.
A manual resync should see you return to 3dB and a sync nearer the attainable.
If I'm right about this I'm going to feel really smug lol because this is a wild shot in the dark.
Do you notice the brief 3dB drop just before the resync and 3dB increase? I believe that to be an external noise source of some kind, possibly a crosstalker?
Please post the results on info --stats if you can :)
-
If I'm right about this I'm going to feel really smug lol because this is a wild shot in the dark.
You've every right to feel smug... full stats are at the end of the post. :-)
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 9993 Kbps, Downstream rate = 51175 Kbps
Bearer: 0, Upstream rate = 9997 Kbps, Downstream rate = 44367 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Do you notice the brief 3dB drop just before the resync and 3dB increase? I believe that to be an external noise source of some kind, possibly a crosstalker?
I actually had a VNC desktop running to my Raspberry Pi while I was working yesterday afternoon. In all cases so far the drop has lasted for a few minutes. During that time the connection didn't drop, and I continued to be connected to the work VPN. It's then approximately 70/75 minutes later that a modem resync is forced with retrain reason 1. It's happened 3 times so far, and the resync delay is now predictable.
I agree with you that if I forced a manual resync, it would resync at 3dB.
So, if I'm still officially running with a 3dB profile, why is DLM or the modem resyncing to 6? If this carries on will DLM get to the point that it aborts 3dB completely on this line?
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 9993 Kbps, Downstream rate = 51122 Kbps
Bearer: 0, Upstream rate = 9997 Kbps, Downstream rate = 44367 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): 6.1 6.2
Attn(dB): 24.4 0.0
Pwr(dBm): 11.5 6.4
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 237
M: 1 1
T: 0 43
R: 10 16
S: 0.0000 0.7565
L: 11649 2686
D: 4 1
I: 238 127
N: 238 254
Q: 4 0
V: 0 0
RxQueue: 108 0
TxQueue: 27 0
G.INP Framing: 18 0
G.INP lookback: 27 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 549718
OHFErr: 387 12
RS: 926758072 3459332
RSCorr: 436368 22
RSUnCorr: 0 0
Bearer 1
OHF: 2366879 0
OHFErr: 0 0
RS: 14200903 0
RSCorr: 427 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 2934723 0
rtx_c: 553681 0
rtx_uc: 83231 0
G.INP Counters
LEFTRS: 466 0
minEFTR: 44368 0
errFreeBits: 44510919 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3242015487 0
Data Cells: 21934048 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: 100 13
SES: 71 0
UAS: 345 56
AS: 38024
Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.16
OR: 0.01 31.35
AgR: 44464.49 10028.04
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: 11312/11312 233/233
Total time = 14 hours 2 min 12 sec
FEC: 2395135 24
CRC: 2878 13
ES: 100 13
SES: 71 0
UAS: 345 56
LOS: 1 0
LOF: 7 0
LOM: 0 0
Latest 15 minutes time = 2 min 12 sec
FEC: 11 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: 120 1
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 = 14 hours 2 min 12 sec
FEC: 2395135 24
CRC: 2878 13
ES: 100 13
SES: 71 0
UAS: 345 56
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 = 10 hours 33 min 43 sec
FEC: 436368 22
CRC: 387 12
ES: 19 12
SES: 14 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
-
You've every right to feel smug... full stats are at the end of the post. :-)
j0hn sets mode to +smug :dance:
So you have a noise source that comes on briefly, and knocks the actual SNRM down by 3dB.
In the 2 examples you posted it lasted about 1 min and about 5 minutes in the 2nd example.
Then about 70-75 mins later it triggers a resync, and the 3dB noise is present during the resync/training causing you to sync 3dB lower than the target SNRM.
The strange thing is it looks like this noise source is gone by the time DslStats does the first sample after sync is achieved. The actual SNRM immediately has 3dB "spare".
Very very strange indeed.
Are you still on the HG612? I wonder if it could be a problem with the modem. Might be a good time to try that Zyxel modem!
What you could do is set a email alert in DslStats to email you if the downstream SNRM drops below x.
As you're at 6dB I would set it to about 4dB.
It will email you 70-75 minutes before the resync will come when the SNRM drops for the brief period.
If this carries on will DLM get to the point that it aborts 3dB completely on this line?
Do you get a burst of ES or LEFTERS during the brief SNRM crash?
DLM is unlikely to take action on the line for a single resync every few days.
You could either take the line down for 10 minutes at around 70 minutes after DslStats emails you, though not ideal.
It should also be safe to resync the line after it comes back up at 6dB. DLM won't take action on that if it's the only resync that day. Again that's not ideal.
Does anyone else have any opinions on what could cause SNRM to drop by 3dB for 1-5 mins, then 70-75 minutes later it causes the line to resync, coming back up 3dB higher than the target SNRM?
-
Are you still on the HG612? I wonder if it could be a problem with the modem. Might be a good time to try that Zyxel modem!
After the resync yesterday afternoon, I needed to go out. So I took the opportunity to power off the HG612. When I got back an hour later, I installed the preconfigured Zyxel. As expected on resync it went to 3dB. There were two drops early evening. One was at around 17:40, and the other at 18:50. I was was watching for a resync at around 18:55/19:00 based on the 1st drop, but it didn't happen. However, just after 20:00 it did resync, which was approx 70mins after the 18:50 drop.
What you could do is set a email alert in DslStats to email you if the downstream SNRM drops below x.
As you're at 6dB I would set it to about 4dB.
Good idea. I'll set DSLstats to do that, although at the moment it doesn't like the SMTP login for either my btinternet or google accounts.
Do you get a burst of ES or LEFTERS during the brief SNRM crash?
I've not looked at that... What's the best way of determining that from DSLstats?
Since the resync last night, DLM hasn't forced another resync to bring it back to the 3dB profile. This is what happened previously at around 4am the next day.
-
I've not looked at that... What's the best way of determining that from DSLstats?
Look at the CRC and LEFTERS graphs at the exact times the SNRM dropped. If you save snapshots you can look back at the CRC graph but LEFTERS doesn't save.
There were two drops early evening. One was at around 17:40, and the other at 18:50. I was was watching for a resync at around 18:55/19:00 based on the 1st drop, but it didn't happen. However, just after 20:00 it did resync, which was approx 70mins after the 18:50 drop.
It's not a coincidence that there's 70 mins between the 2 drops either. WTF could it be?
-
It's not a coincidence that there's 70 mins between the 2 drops either. WTF could it be?
As the retrain reason is 1, my assumption is that it's DLM initiated. I was also assuming that DLM could also set the SNRM profile, thus causing the SNRM dB down to be at 6ish dB upon resync. But as I've proven if I manually restart the modem, it syncs at 3dB.
I also thought DLM only took action several hours later, or during the next day. That's always been my previous experience when on the ECI cabinet. I've never seen it act so quickly, especially when sync on the line was never lost.
Am I correct in thinking if there was an event so bad that sync was lost entirely, the retrain reason would be zero? But it seems a stretch to think 70 mins after an SNRM dip, there would be another worse event which would cause sync to be lost entirely, and be ongoing during the modem retrain.
-
Had another drop in SNRM this evening at 19:00...
Do you get a burst of ES or LEFTERS during the brief SNRM crash
The answer to this is yes... see attached SNRM, CRC & LEFTRS graphs...
It remains to be seen as the SNRM is still 6dB whether I get a DLM initiated resync - my guess at this point is that it won't.