Training History Problem

[Sebby]

Good result, Rik.

I know I've already said it and so have others, but IDNet are such a breath of fresh air to deal with. I can just see that effort went in to getting this sorted for me, and once again, I feel that IDNet is worth every penny.  8)

[Rik]

Now you know why we purr so much, Sebby. It's a good feeling.

[Inactive]

I have never needed any support from IDNet, but Seb's little tale sure does give a nice warm glow of confidence.

[Sebby]

Hopefully I won't need it again, but if I do, I'll feel certain that it's no big deal. 

[Sebby]

I've now been connected for one day and things seem fine. Tomorrow will be the true test as the last 2 times I have been booted off at some point before the 2 day mark.

My profile has caught up now to 4000k, which is nice. 

[Wingnutz]

I think i've worked out how to read the training history on the DSL Diagnostics page.

The time / dates appear to reflect the END of that particulat sync event and not the START of it.

That's why you always get the current time and date as the last entry when you log into that screen - the sync event is still live and has not yet ended.

Does this make sense ?

Mike

[Ted]

Yep, sure does. Reply #9

[Wingnutz]

Yep, sure does. Reply #9

Oppps - missed that one - sorry 

[Ted]

No Probs, these threads get a bit long sometimes

[Sebby]

I'm pleased to report that I've now been sync'd for over 3 days at 4640k with a SNRM of no lower than 9dB at all times.

Errors seem reasonable and throughput is excellent (the maximum I can get, in fact, on a 4000k profile).

[Lance]

Great stuff!

[Sebby]

I've had my first resync in about 12 days. However, it doesn't look like a resync as such; it looks like the router rebooted (I'm sure there wasn't a power cut as all other appliances look fine). I say this because there was only one entry in the training history.

It doesn't matter in the slightest, but I just thought it was a little strange. Has anyone else experienced their 2700 reboot randomly?

[Rik]

I did, also at 12 days, Sebby. Ted thought it might be triggered by the log becoming full, the other possibility was that the modem detected it could re-sync at a higher speed (+400k).

[Ted]

Just got back from Tesco's to find we had a power cut at 2.30pm, lost all my stats for the last 17 days, sod! Still syncing at 7616 and 12db.

Sebby i can't remember which firmware version you have, check to see if you had an auto upgrade from BT. This causes a full reboot to establish the new firmware.

[Sebby]

I did, also at 12 days, Sebby. Ted thought it might be triggered by the log becoming full, the other possibility was that the modem detected it could re-sync at a higher speed (+400k).

Okay, so it's not just me. The great thing about this router is that even if there's a resync, you're almost guaranteed the same or higher sync as prior to it, unlike my SpeedTouch, which fluctuated widely.

[Sebby]

Sebby i can't remember which firmware version you have, check to see if you had an auto upgrade from BT. This causes a full reboot to establish the new firmware.

I have the SBC firmware, so it's not that.

[Rik]

I'm on SBC too - perhaps it just has a hissy fit every 12 days?

[Sebby]

It certainly sounds that way! I'll see if it happens again. It's a little annoying as otherwise this router is perfect.

[Rik]

I can live with it, providing the re-sync doesn't mess with the profile, and so far it's always been good in that respect.

[Sebby]

I'm getting close to that magic number again, so it's going to be interesting to see if the router reboots this time.

[Rik]

Of course, you stand a good chance of BT's spanner arriving in the works anytime soon...

[Sebby]

Are you talking about the DSLAM maintenance, Rik?

[Rik]

Indeed. If it hasn't happened yet, it must be getting closer to us.

[Sebby]

I have passed the 12 day mark!

[Rik]