O Canada! > Canadian > TekSavvy > [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

[Cable] Teksavvy Cable Constant Modem Restart [SB6120]

What do your log file say?
and signal levels?

I have the same issue but on a sb6121. I have been watching the many other threads on this problem as well. From previous experience Teksavvy support is useless. If you can't live with it, move on to someone else. Expect someone to ask you to post in the direct forum, followed by the run around of blaming your equipment or Rogers, while not capable of fixing your issues.

reply to pleco
Sorry to resurrect an old thread, but was your issue ever resolved? I've been having the same problems as you, with the same hardware:

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.1-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: 317001100601317707040001
Firmware Build Time: May 12 2011 15:15:14

Calls to tech support have been uneventful, as they ignore the actual log messages and ask me to ping things..

reply to Anon user
Why don't you sign in so we can see who you are there bud.

reply to pleco

The failure rate is extremely low for the Motorola line of modems.

I agree the failure rate on Motorola modems is low. Modems are getting swapped or replaced when there is nothing wrong with them at all. My Motorola had not rebooted at all for a year when there was 4 downstream bonded channels and 1 unbonded upstream channel. When Rogers bonded 2 upstream channels that is when the problems occurred. My modem now reboots every 18 hours like clockwork. When Rogers was working on their system about a month ago, they deactivated upstream channel bonding and my issues disappeared. This is obviously an upstream channel bonding issue with Rogers as my line stats are well within the recommended range.

Unless there's a bug in the firmware that shouldn't happen. The Moto should be perfectly able bond to up to 2 channels. Plus in this case I doubt Rogers is the cause as a various models of modems are now bonding up to 4 upstream channels on their network now.

reply to Pko200

reply to ijaaz

reply to ijaaz
Where are you located? I have been having the same issue in the Yonge & Eglinton area. It's very random, the modem looses synch for a couple of seconds, usually not less then a minute then reconnects. Using the same SB6120.

reply to tonytoronto
Folks exactly the same bad nagging performance experience and associated mis-handling of fundamental issues. Search for "Teddy Boom" here and he is near U of T also posts here. Very wonderful gentleman. Well educated and helpful. If you are physically close to be able to see him you will be pleasantly surprised to see him. He may be able to give you ideas and check things out with hardware/modem/etc.

The issue generally is Carriers trying to be too cute and throwing out implementations of dubious value (4 channel upstream bonding for 1 Mb/s service). As described in this thread finicky plant. Even when one channel has minor transient issues all the Upstream goes in limbo and dies bringing down the Downstream 4 bonded channels with it. A reboot follows till one of the Upstream bonded channels again goes into the "Aborted" or "continue" mode and all four channels in upstream bonding go down one at a time like house of cards again. Story repeats based on what you had for breakfast or how much you curse the duopoly.

Good luck.

PS: I found the following to be very probelamatic for these modems,

"Cable Modem Reboot due to T4 timeout" which invariably leads to freezes and reboots. Appears in part to do with bad software on 6120/6121 modems. Not sure fire but a key culprit.

I have this exact problem, it's been happening since Friday, I constantly timeout/ping out of IRC channels/games. It'll fix itself if I power cycle the modem but it's only a temp fix. The modem itself (SB6120) will sometimes cycle all by itself. I contacted TS about it and was told they couldn't find anything on their side but would have to send out a tech. After 15hrs of constant usage and no dropped connection or reboots I called in to cancel the technician and almost 20 minutes later the connection dropping occured again

Is this something that'll go away on its own or something a tech actually have to come by and fix?

reply to pleco
My SB612x keeps doing that to. something changed about 1-2 weeks ago. and now I can't hold a connection on cable. my voip is useless, and I can't keep a VPN open.

I get T3 and T4 error repeatedly, and get Docsis fallback to docsis 2.0 mode. with only one channel bonding. and then bonding restores again. then lost, then restores over and over.

T3 and T4 time outs are signal power related between the CMTS and your CM. In other words the CMTS sends a ranging response request to your CM and when the CM responds back the signal is too low or faint for the CMTS to 'hear' so it will continue to retry its range response requests until it is successfull. If after a certain ammount of retries the CMTS will do a remote reset of the CM to clear the slate and try its ranging request responses again until it can succeed before it is able to move onto the next step in its programmed routine which might be a system audit, a firmware push, setting channel bonding... and so on.

* The problem could be your modem is defective?
* The problem could be the signal between your modem and the CMTS could be too weak somewheres along the route.
* The problem could be the CMTS at the POI is misconfigured or a setting on their end could be too high or too low.

Fat lot of good thats going to do if its the CMTS thats the problem, they'll likely deny blaming node congestion or whatever else like signal degradation along the path to your CM. I imagine to pinpoint a problem at the CMTS would require a lot of opened tickets in your specific area to even get them to look into it. Otherwise your line or your CM is to blame from their viewpoint.
--
You see there is only one constant. One universal. It is the only real truth. Causality. Action, reaction. Cause and effect.
Twitter:Merv Chat:irc.teksavvy.ca

reply to pleco
Just a quick "Me Too"!

I haven't gone as far as checking logs, posting in direct forum etc, but symptoms are identical, and problems began when upstream bonding arrived.

I assumed it had to do with enabling upstream bonding and it would sort itself out after a few days... No such luck so far ...

Usually a modem reboot fixes it for awhile... But still irritating. What are our options? Will this need a service call, or a software update from Rogers?

Thanks!
DB