interleaving

[#1]

That sounds good to me buddy
Interleaving off and an  xDSL Status check and a CLT 
Again thanks for your time and effort. 

[#2]

Sorry for the formatting.
xDSL Status Test Summary 
Sync Status: Circuit In Sync 
General Information 
NTE Status:  NTE Power Status: PowerOn  Bypass Status: 
 
Upstream DSL Link Information  Downstream DSL Link Information 
Loop Loss:  27.3  51.0 
SNR Margin:  6.5  3.0 
Errored Seconds:  6  3 
HEC Errors:  4 
Cell Count:  4630822  103509689 
Speed:  1053  5526 
 
Maximum Stable Rate (KBPS):  4544  Fault Threshold Rate (KBPS):  3635 
Mean Time Between Retrains (Seconds):  86400  Mean Time Between Errors Upstream (Seconds):  930 
Indicative Line Quality:  A  Mean Time Between Errors Downstream (Seconds):  32 
Custom Thresholds 
MTBR_RED:  MTBE_RED: 
MTBR_GREEN:  MTBE_GREEN: 

Intereaving order being placed as I type.

[#3]

Cheers Tony.
As I suspected might be the case DLM isn't too happy, ILQ is amber, so the Target SNRM may go up at some point.
Can you post some current stats scottymc, I reckon we'll see an LoS which will have been due to a loss of US sync rather than DS -  the US sync speed has changed slightly, the DS hasn't and DLM has the DS MTBR as 86400 (seconds) which tends to support that.
Shame that line balance isn't the best (330/326 nF) - that'll be partly responsible for the higher error rate.
At least Celerity is good, comparing favourably with loop loss.

[#4]

Thanks guys
I'll post some stats when I get home.

[#5]

The interleaving should change in the early hours of tomorrow.

[#6]

Thank you tony
Here are some stats from today at 5pm
Link Information
Uptime: 0 days, 2:42:27
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,072 / 5,554
Data Transferred (Sent/Received) [GB/GB]: 1.18 / 22.39
Output Power (Up/Down) [dBm]: 12.8 / 0.0
Line Attenuation (Up/Down) [dB]: 27.3 / 51.0
SN Margin (Up/Down) [dB]: 6.1 / 3.0
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 17 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 898 / 0
FEC Errors (Up/Down): 671 / 3,691,110
CRC Errors (Up/Down): 52 / 74
HEC Errors (Up/Down): 31 / 604

again thank you for all your help

[#7]

Just a brief comment then. Currently all looks a little bit better than previously - all error rates are down a touch.
There've been 2 Losses of sync, the one I suspected based on the reported speeds from the xDSL Status check, and the 2nd one will have been the CLT which disconnects the line for just under 3 minutes whilst testing.
If I were you, I'd be a bit OCD with doing Quiet Line Tests, I have a niggly feeling there may be something going on.
Other than that, as Tony mentioned the Interleaving order should happen in the early hours (probably between about 2-3 am.) this will cause a brief loss of sync as well.
If you could post some more stats tomorrow morning, we can see how it's all going.

[#8]

stats
Link Information
Uptime: 0 days, 2:37:28
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 975 / 5,615
Data Transferred (Sent/Received) [GB/GB]: 1.54 / 26.93
Output Power (Up/Down) [dBm]: 12.4 / 0.0
Line Attenuation (Up/Down) [dB]: 27.3 / 51.0
SN Margin (Up/Down) [dB]: 6.6 / 3.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 26 / 0
Loss of Signal (Local/Remote): 3 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 8,539 / 0
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 0 / 242,266
HEC Errors (Up/Down): 0 / 52,540

[#9]

Well, that looks as though it all happened as expected. Also as anticipated the CRC rate has increased, but the ES may well be of some concern, it's a case of see how it goes.
What may be an idea is if you can do a Graceful disconnect at some point in daylight hours today at least an hour before sunset, but an hour after sunrise - stay powered off for 10 minutes and when you've powered up and connected post the new stats. All the error counters will have been reset of course - it'll be a little easier to assess how the errors are doing. Post some more stats later in the day.
Don't forget the Quiet Line Tests.

[#10]

Buddy ,
The quite line test.. I just call that number goto option 2 and listen ?
Or is running a test and I need to wait for the result ?
Sorry for being stupid

[#11]

Just dial and listen.  Periodically you'll hear a voice saying Quiet Line Test.
If you don't hear any cracking or other noises after two or three of those, hang up and try it again later.  You can hang on as long as you want.

[#12]

stats when i got in
Link Information
Uptime: 0 days, 12:57:08
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 975 / 5,615
Data Transferred (Sent/Received) [GB/GB]: 1.86 / 31.97
Output Power (Up/Down) [dBm]: 12.4 / 0.0
Line Attenuation (Up/Down) [dB]: 27.3 / 51.0
SN Margin (Up/Down) [dB]: 6.6 / 3.0
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 26 / 0
Loss of Signal (Local/Remote): 3 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 36,883 / 0
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 150 / 1,008,135
HEC Errors (Up/Down): 62 / 212,661

Stats after reset
Uptime: 0 days, 0:00:32
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,063 / 5,603
Data Transferred (Sent/Received) [kB/kB]: 59.92 / 149.78
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 27.3 / 51.0
SN Margin (Up/Down) [dB]: 3.8 / 3.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 8 / 0
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 0 / 496
HEC Errors (Up/Down): 0 / 96
I did the quite line test while the router was shut down but couldn't here a thing ,, but I'm getting a lot of error's that said my son says his gaming has been fine today ..
do you think there could be something wrong with my line?

[#13]

and some more stats
Link Information
Uptime: 0 days, 0:10:02
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,063 / 5,603
Data Transferred (Sent/Received) [MB/MB]: 3.51 / 21.33
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 27.3 / 51.0
SN Margin (Up/Down) [dB]: 5.4 / 3.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 445 / 0
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 0 / 13,742
HEC Errors (Up/Down): 0 / 3,004

[#14]

A lot of CRC and ES there as perhaps was expected, I would imagine DLM won't be too happy.
What's the current stats like? I would guess the Gaming has been ok though!

[#15]

I'll do a stats when I get in
Both boys are happy with the gaming side of things both have said their pings are around 20-30,
They said it didn't go below 50 while interleaving was on and spiked alot to 999 and lagged out.
Speed test have been giving some of the fastest speed we had seen 
So other than the errors everyone is happy
Thanks for the follow up ill post stats tonight