Could somebody (Bald_Eagle?) take a look at my logs and see if anything looks odd please, as I think it does to me.
I seem to get a lot of disconnections/reconnection's, I unpluged the RJ11 lead yesterday about 19:00 to check wiring, and apart from a couple of times over the last couple of weeks that I've rebooted the HG612 thats all.
Today I noticed it had re-synced about 15:00, and whilst looking at the HG612 internal logs noticed the date/time had reset, and going by the time it was the same time as the re-sync, but I thought the date only went back to 2000 when the power was turned off - which mine can't of been - it's on a 1500VA UPS along with my server and other networking gear, and the server logs showed no problems.
I have seen the internal clock reset to the year 2000 after a reboot or as you say the power turned off, but not following an "on the fly" resync.
My speeds seem slower than others mention for the distance from the cab (although all lines are different), which is about 450 meters, the BT estimate was for 57/20. I initially had an attainable rate of 55, then it dropped to below 50, at one point I had a line rate of 45. I've also noticed sometimes that the attainable rate is lower than the line rate, both up and down. All lines are underground, and were installed in the mid 70s, internal cabling consists of about 3 meters of Cat5e STP from the original master socket location, where the line enters the house to the new master socket, with the modem sat just above. It probably is in quite a noisy electrical environment, here's a pic and the other side of the wall is where the consumer unit is.
When my connection was "faulty" (various issues) I would often see lower attainable rates than sync speeds.
SNRM was always very low at those times, my logs showing the connection had synced at say 6dB SNRM at a speed very close to attainable rates, as SNRM gradually tailed off to as low as 1.5dB to 2 dB or so, the attainable rates would end up lower than actual sync (& throughput) speeds.
The connection has been reliable and does seem very quick, although I did have one or two instances where the internet became very unresponsive, one case was on 26 August around 9pm, I noticed FEC errors shot up and rebooting the HG612 seemed to solve the problem. This is my TBB ping graph from that evening.
You mentioned higher up the post that you get a lot of disconnections/reconnections.
I wouldn't describe that as a reliable FTTC/VDSL2 connection.
Many FTTC users don't see a disconnection for weeks on end, with almost non-existent error counts.
Although my connection has been repaired, I still see some noise & errors (mainly RSCorr / FEC type errors), but it does now stay connected more or less until I intentionally cause a resync/reboot.
I've got BA's excellent scripts running 24/7 on my WHS2011, and the graphing performed on my office PC, all works a treat, but I did download the latest Graph6 batch file posted on Kitz today, but can't seem to fathom out where it's getting it's data from, it appears to be looking for a Plink.log file in the apps folder, but this neither exists on my server or pc. And when I run it just tells me that plink.log does not exist, and the old Graph6 batch file does the same, am I missing something?
GRAPH6.BAT is the graphing part, called at the end of TestStats2.BAT after new "snapshot" data has been harvested.
Running GRAPH6 on its own won't generate any graphs.
However, dragging & dropping a valid Plink or PuTTy log in the correct format onto it will generate graphs in the same folder as the Plink or PuTTy.log
So you could re-graph your old logs in the new format whenever you wanted to.
I have attached graphs from your Plink.log using that method.
Any new data obtained via TestStats2.BAT should be in the new format anyway (assuming the new GRAPH6.BAT is in the Scripts folder).
I've uploaded all my graphs to Dropbox and I have a live TBB ping graph here. The most recent ongoing stats cover the whole period I've had FTTC from about 20 minutes after the BT Technician left.
My HG612 was acquired off eBay and is a version 3B, when my fibre was installed BT also supplied a HG612 even though I believe we are on an ECI cab.
Sorry for the long post.
Could you post a modem_stats.log anywhere (as large as possible, say 20Mb to 30Mb or larger) that I could download it & graph the data at my end for easier study?
EDIT:Yes, I can tell from the specific tones listed in Discovery Phase of your pbParams data that you are indeed connected to an ECI DSLAM.
This is what it looks like for a Huawei DSLAM:-Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3959)