Please reset my line

[#1]

I really don't think the SNR reset will make a difference, so I'm going to place an order to cap your line. This will mean that your upload will be at 448 for a day, but on Monday we'll place the uncap to complete on Tuesday.

[#2]

I think the port needs resetting, there is clearly a problem with the downstream syncing at a Target of 6dB whereas the profile says it's 3dB with No Interleaving, totally contrary to the stats.

[#3]

I think you're right AO.
SNRM now down to one, 1,0000's of CRC errors but yet the upload is capped!
Download is over 18Mbps
Upload .443 (capped - almost 1/2 of the erroneous .888 figure - so something still not right)
> adsl status
 --------------------------- ATU-R Info (hw: annex A, f/w: annex A) -----------
  Running Mode            : ADSL2+(G.992.5)       State                : SHOWTI
ME
  DS Actual Rate          : 18808621 bps   US Actual Rate       :   443928 bps
  DS Attainable Rate      : 17788000 bps   US Attainable Rate   :  1212000 bps
  DS Path Mode            :        Fast    US Path Mode         :        Fast
  DS Interleave Depth     :        1       US Interleave Depth  :        1
  NE Current Attenuation  :       27 dB    Cur SNR Margin       :        1  dB
  DS actual PSD           :    20. 1 dB    US actual PSD        :    12. 1   dB
  ADSL Firmware Version   : 2471201_A
 -------------------------------- ATU-C Info ---------------------------------
  Far Current Attenuation :       14 dB    Far SNR Margin       :       30  dB
  CO ITU Version[0]       : 00004946       CO ITU Version[1]    : 0000544e
  DSLAM CHIPSET VENDOR    : < IFTN >
>

[#4]

Let me uncap the upload and if needed we can go through a faults investigation after that's complete (tomorrow).

[#5]

Thanks Chris - appreciate your help, 

[#6]

Yep 443 is a standard capped US sync speed. I've seen a few at 444, but mostly 443. It's the 21CN equivalent of 448 on ADSL(1).
See what happens tomorrow.

[#7]

Meant to say, the reason for the high errors is the very low SNRM and Interleaving now off. The "cap upstream" order will have taken effect effect during the early hours when the SNRM was probably up and down quite a lot and the sync maybe caught it on a high and it's settled to a steady (lower) daytime rate, but note these recent changes have sorted out the fact that the port seems to have responded and it's now syncing with a 3dB Target SNRM.
If I were you, I would do a graceful resync now (daytime) to allow it to goto the 3dB SNRM which will help reduce those errors, otherwise the DLM may decide to up the Target SNRM!  (Remember, graceful = Disconnect PPP session, then  power off for 10 minutes).

[#8]

Thanks! Yes, spotted the interleave was off when I saw 8,000 + errors  
Will do a graceful re-sync in a moment whilst the sun is up!
Here's hoping  
UPDATE: Back online SNR now 3.

> adsl status
 --------------------------- ATU-R Info (hw: annex A, f/w: annex A) -----------
  Running Mode            : ADSL2+(G.992.5)       State                : SHOWTI
ME
  DS Actual Rate          : 17816233 bps   US Actual Rate       :   443928 bps
  DS Attainable Rate      : 17816000 bps   US Attainable Rate   :  1200000 bps
  DS Path Mode            :        Fast    US Path Mode         :        Fast
  DS Interleave Depth     :        1       US Interleave Depth  :        1
  NE Current Attenuation  :       27 dB    Cur SNR Margin       :        3  dB
  DS actual PSD           :    20. 0 dB    US actual PSD        :    12. 9   dB
  ADSL Firmware Version   : 2471201_A
 -------------------------------- ATU-C Info ---------------------------------
  Far Current Attenuation :       14 dB    Far SNR Margin       :       30  dB
  CO ITU Version[0]       : 00004946       CO ITU Version[1]    : 0000544e
  DSLAM CHIPSET VENDOR    : < IFTN >
>

[#9]

That's looking a lot better, let's hope the CRC rate is now sensible. The Uncap order will happen in the early hours so you might find a similar situation when you look in the morning and may have to do a graceful resync to get things right.

[#10]

Thanks AO.
So far uptime is 21mins, CRC is 35, RX cells 120,478. / 8500 packets.

Yes, expecting to repeat tonight's reset tomorrow if SNR back to 1 after the uncap.

[#11]

Upstream sync = 1223

[#12]

Hey, its looking good Chris - Thanks.
SNR down to 2 so will do a gentle restart in an hr or two whilst daylight.

[#13]

Stats update:
Uptime: 3h 36
RX CRC errors: 624
RX Cells: 9487253
SNRM fluctuating between 2 and 3.

> show adsl
 --------------------------- ATU-R Info (hw: annex A, f/w: annex A) -----------
  Running Mode            : ADSL2+(G.992.5)       State                : SHOWTI
ME
  DS Actual Rate          : 17880985 bps   US Actual Rate       :  1208000 bps
  DS Attainable Rate      : 18216000 bps   US Attainable Rate   :  1208000 bps
  DS Path Mode            :        Fast    US Path Mode         :        Fast
  DS Interleave Depth     :        1       US Interleave Depth  :        1
  NE Current Attenuation  :       27 dB    Cur SNR Margin       :        3  dB
  DS actual PSD           :    20. 0 dB    US actual PSD        :    11. 9   dB
  ADSL Firmware Version   : 2471201_A
 -------------------------------- ATU-C Info ---------------------------------
  Far Current Attenuation :       14 dB    Far SNR Margin       :        6  dB
  CO ITU Version[0]       : 00004946       CO ITU Version[1]    : 0000544e
  DSLAM CHIPSET VENDOR    : < IFTN >
>
>

[#14]

Looks more promising Graham. By now your Current Line speed (Login required) should be around 15.7 if you maintain that sync speed.

[#15]

Hi,
15.7Mbps it is.
Currently seeing SNRM drifting between 2 and 3 is that a problem?
Rx CRC is 1945 for 11660817 Cells Rx'd - again is that an acceptable rate?
Thanks!
Graham.