Topic 'Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]' in forum 'TekSavvy' - dslreports.com

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sun, 13 Jan 2013 23:49:08 EDT

anon posted : Dont use the same service, but do have charter and use the same motorola modem. When this happens I usually get several messages something like this in the log:

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Or

ToD request sent - No Response received;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

My solution:

1) GOTO the modem setup page: »192.168.100.1
2) Click on "Configuration"
3) Click on "Reset All Defaults"
4) You will get a prompt that makes you worry...Don't, it will be okay. Answer yes.
5) Go to your modem and unplug the power from it and leave it unplugged for at least five minutes.
[5 minutes have gone by]
6) Plug your modem back in.
7) It will take your modem several minutes to relearn the route paths and download the config file from your ISP.
8) If this works for you, write a confirmation post here so that others might benefit from it.

I hope this helps.

Best Regard,
PCVice

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sun, 06 Jan 2013 16:13:19 EDT

trader117 posted : My internet connection has been working normally since I got home last night, but I don't trust the likelihood of it retaining this consistency. Last time it only worked for a couple of days, before disconnecting again. I will run the excel spreadsheet as soon as the issue returns.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 05 Jan 2013 18:49:15 EDT

trader117 posted : Thanks Resa.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 05 Jan 2013 18:44:54 EDT

resa1983 posted : Gotcha.. I'll try to check back tonight or tomorrow for a log from you. :)
--
Battle.net Tech Support MVP

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 05 Jan 2013 18:33:42 EDT

trader117 posted : Not yet, Just found here today. I am so frustrated with this issue these days. I will give it a try after I get home from work tonight.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 05 Jan 2013 18:09:52 EDT

resa1983 posted :

said by trader117:

I already have the same issue for three months. Anybody got a solution to fix it?

Have you run the excel spreadsheet to log your stats? Does it show anything?
--
Battle.net Tech Support MVP

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 05 Jan 2013 17:19:29 EDT

trader117 posted : I already have the same issue for three months. Anybody got a solution to fix it?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 18 Dec 2012 21:08:08 EDT

TwiztedZero posted : Might turn out to be line attenuation or an RF issue somewheres on your line from the tap out, who knows. But yeah logging your signal levels will give a better idea over time.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 18 Dec 2012 20:48:52 EDT

resa1983 posted : Have they checked your modem stats by any chance?

Do you have Excel? If so, you can run my Excel logger which grabs modem stats every minute and charts it.. Its one way to show Rogers there's an issue with the modem itself dropping.

Err, keep in mind this only works with the SB6120 & SB6121.
--
Battle.net Tech Support MVP

SB6120 Logge···.xls.zip 229,301 bytes

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 18 Dec 2012 20:36:59 EDT

anon posted : I'm running similar issue the last month or so, since an upgrade of service in the area.

Tue Dec 18 23:08:59 2012 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Tue Dec 18 23:08:50 2012 Critical (3) No Ranging Response received - T3 time-out
Tue Dec 18 23:08:34 2012 Critical (3) DCC aborted unable to acquire new downstream channel

Roughly every 1/2 hour... Sometimes it skips...

I've done my research on this one, and getting techs arguing, REFUSING to look at the MODEM logs (only their remote logs)
They REFUSE to admit there's a problem with the line (downstream channel overlap!!!)
I just spent 20 minutes arguing with a tech that it was NOT the modem (5 replaced in the last 2-3 months), and NOT the network card on my computer (errors while modem is connected, powered on, but, unplugged from computer)

Have an ACTIVE forum post »communityforums.rogers.com/t5/fo···-id/8749 from them as well.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 15 Dec 2012 23:27:52 EDT

sbrook posted : If it's working for 3 days, then it makes perfect sense that it was fixed. That it was broken for the previous 5 weeks is irrelevant to the situation at the time of the call. Now the reality was that it wasn't fixed. But Rogers won't keep tickets open. Heck they close them after doing absolutely nothing and report NFF.

So, you have to call back in to TekSavvy and say "Hey it wasn't actually fixed ... please reopen the ticket!"

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 15 Dec 2012 22:09:52 EDT

counting7 posted : OMG so many people having exactly the same issue, and both Teksavvy and Rogers refuse to acknowledge the issue. I have been having this issue, along with occasional speed issues, since January. I have tried to get anyone interested in this issue and I've been ignored and tricked. The last ticket, they had the connection steady for about 3 days straight after which an elderly resident at my address received a call asking how the connection was. Despite saying "it was great for the past 3 days, but was terrible for 5 weeks prior to that"(paraphrasing) they closed the ticket and ignored the part about 5 weeks of constant terrible service.

I'm at my wits end and just want to switch providers, despite knowing that most other providers will just be renting their lines from Rogers or Bell anyway.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Fri, 16 Nov 2012 16:09:40 EDT

Teddy Boom posted : Very interesting news on firmwares for SB6120 and SB6121..

I upgraded a SB6120 for a customer today. It started out on firmware 1.0.1.8. It synced on 4 downstream but only 3 upstream channels. Device connected to the modem couldn't do DHCP. Upgraded and the modem went online directly with 4x4, DHCP worked fine. Who knew firmware could cause DHCP problems :)

I've noticed some 1.0.0.x firmwares won't do any channel bonding at all. I've also had several reports that upgrading from 1.0.5.x to 1.0.6.1 does help resetting problems considerably.

In general, getting a firmware upgrade is making a lot more difference than I thought it would.
--
electronicsguru.ca

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 08 Nov 2012 14:42:10 EDT

TwiztedZero posted :

said by atulb:

btw, how do you request a rogers tech. for teksavvy users?

In order to get a ticket opened for a tech visit you'll have to fill in a form in the TekSavvy Direct forum here: »TekSavvy Direct

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 08 Nov 2012 14:29:24 EDT

atulb posted : Same issue T3, Teksavvy rep not at all helpful/useful. One solution people can try is changing the coax to another point on the splitter, ie. take wire going to TV connect to modem, take wire going to modem connect to TV. I find that this delays the issue for a while (atleast for me).

btw, how do you request a rogers tech. for teksavvy users?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Wed, 22 Aug 2012 13:43:26 EDT

side1021 posted : I'm having the exact same issue. My modem will keep on reset for about an hour. Now it's fine but it has happened to me 3 times already in 1 month. It seems there is something wrong with upstream.

FYI my modem is a new SB6121.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 21 Aug 2012 00:48:41 EDT

EGM92 posted : I'm still having my disconnects, it was ok about 2 weeks ago, it would only happen late night, or mid day when no one was home, I went away on vacation for a week, returned to look at my Router logs and see the slew of DNS errors. Moments after I got settled in, I started to get disconnected again, this was around 5pm, and it lasted for about 2 hours of up and down time. I'm fed up. A majority of the people I've talked to at Teksavvy can't give me a straight answer as to what's happening, feels like I'm being led through hoops and nothing is being resolved. I've even been told that I they weren't able to help and that I should call back at a later time with some more information.

That's a BS response. Where are the Teksavvy reps? It's obvious I'm not the only one, I have friends who are experiencing this on Rogers as well in multiple regions.

I've also noticed that before all of this started, the link light would flash at a constant pace, like once per second. Now When I look at it, it'll blink once per second 5-6 times then it'll takes 5-6 long flashes lasting 2s before returning to the quick pattern. I've had TSI internet with the same modem for over a year and have never seen this before.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 20 Aug 2012 14:37:57 EDT

SergeB posted : I'm also experiencing the same issue with the 6120. I had a rogers tech come and replace the splitter and change the cable wire and told me, if that doesn't fix it, it's the modem. Naturally, 2 days later the issue came back. I just recently bought this modem so I hardly think that it is a defective modem. Not sure what else I can do at this point. The disconnects happen approximately every 31 minutes, upstream power is at 45-47, but the logs do give some sort of clue for me; these three lines repeat themselves every time I disconnect:

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b3:aa;CMTS-MAC=00:1b:54:cb:66:c5;CM-QOS=1.1;CM-VER=3.0;

No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b3:aa;CMTS-MAC=00:1b:54:cb:66:c5;CM-QOS=1.1;CM-VER=3.0;

Cable Modem Reboot due to IP loss ;CM-MAC=00:23:74:f5:b3:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

I was actually researching the issue for a while and I found that changing the splitter fixed it for some people so I went to an electrical store to buy one (before the rogers tech came) and the guy at the store said that the setup I had at home was the problem; I have the cable outlet from the wall splitting for my cable TV and my internet. Not sure how accurate that statement is but perhaps that's the problem? Which is strange because I've always had a 2 way splitter setup like this until a few weeks ago where we had to call a rogers tech to replace our TV cable box (it was old) and he changed our old splitter for a "new one".

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 18 Aug 2012 21:32:30 EDT

QQCable posted : heh I have been using that... the signal is fine and when the modem does go out the script can't access the modem to get a reading.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 18 Aug 2012 21:02:13 EDT

tonytoronto posted : theres a small program in one of the forums here, it will datalog the signal levels of the modem, i used it on the Motorola and worked great, maybe be the only way for you to show them when signals go bust!

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 18 Aug 2012 18:26:28 EDT

QQCable posted : so I caved and called TS again because the issue my internet has been cutting out every 30-35 minutes for 73 hours now..

no visible Signal/power issues... nothing in the logs..
TekkSavvy won't send a tech to look at the lines because of the signal levels..

If I'm to replace my modem... what model should I get. I really don't want another Motorola SB6120 because this problem is all over the internet with no solution.

Tekksavvy has a list of approved modems... does anyone have a good recommendation for a replacement?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Wed, 15 Aug 2012 21:11:43 EDT

tonytoronto posted : Just an update, seems like its finally stable. It looks like it was the splitter some other Rogers idiot tech installed, been fine since we put us back on the tap.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Wed, 15 Aug 2012 20:58:26 EDT

corellama posted : So the problems still happened with the new modem I got. Today the best Rogers tech ever showed up. His name was Paul. He re-did all the connecters at the tap on the pole and the house connection. No change. Then we searched in the house for any hidden splitter. Nothing. Finally he traced the wire up high that comes over to the house and low and behold there was a 3 inch piece of bare wire. He said it was probably a squirrel as it was all chewed up.

My upstream power went from 55dBmV to 41.5dBmV. Much better now. Hungry squirrels are evil!

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Wed, 15 Aug 2012 15:28:18 EDT

Doeboye posted : So I was suffering from the same 6120 dropping upstream channels/losing connection etc etc. and had Rogers come out to check things out. The tech changed the splitter in the rogers box outside my house and reduced my upstream power levels from 52+ to 47-49.

Since the visit, I have not had any nasty log messages or reboots... Perhaps others may be suffering from borderline too high upstream power levels that were tolerable with a single channel, but problematic with bonded upstream... Of course, I may still have the problem, but so far so good.... :)

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 09 Aug 2012 15:54:46 EDT

tonytoronto posted :

said by QQCable:

So after a few more days of it doing the same old thing lately once it does it for the last time I am getting a new error message

Aug 09 2012 03:34:09 6-Notice D106.0 DHCP Renew - lease parameters tftp file-bac103000106e4839959b295 modified;
Aug 09 2012 03:34:09 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;

again Signal/Power are consistent with an ok rating, and it doesn't change.

the modified message i believe it means Rogers has sent instructions to modem, if what i read is correct. I also seen that message after i had ticket open with Rogers.

Yesterday i had another tech come by, happened to be the same one as time before. You know you in for something good when he asks "which one is the Modem??" after 1 hour of being told the signal is good, i asked him if he looked at the tap outside, he didn't-- how the fk does one check for signal without starting at the source? Turns out some other rogers monkey put our connection on a 2 way splitter, not straight to tap. He fixed that and than he tells me now the signal is good!! WTF, it was good before! must be super gooder now! anyhow, hasn't reset in almost 24 hours, keeping fingers crossed, next glitch and i'm off to DSL.
BTW, i think we beat a new waiting time record, way over 1 hour and ended up not talking to anyone, wife got tired of waiting. Wife was super pissed and wants out, i can't even mention teksavvy at home anymore.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 09 Aug 2012 14:55:29 EDT

HiVolt posted :

said by QQCable:

Those are normal and not an indication of any problems. This message appears once per day at the same time.
--
GO BLUE JAYS!

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 09 Aug 2012 14:48:20 EDT

QQCable posted : So after a few more days of it doing the same old thing lately once it does it for the last time I am getting a new error message

Aug 09 2012 03:34:09 6-Notice D106.0 DHCP Renew - lease parameters tftp file-bac103000106e4839959b295 modified;
Aug 09 2012 03:34:09 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;

again Signal/Power are consistent with an ok rating, and it doesn't change.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 04 Aug 2012 00:16:51 EDT

tonytoronto posted :

said by QQCable:

Tony are you in the North york area?

Nah, Bloor and Christie-- Dupont poi

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Fri, 03 Aug 2012 23:14:14 EDT

anon posted : Tony are you in the North york area?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Fri, 03 Aug 2012 23:14:09 EDT

anon posted : Evening.

after... 3 days of perfectly normal service. the fun has resumed.

Jan 01 1970 00:00:08 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:00:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;
Jan 01 1970 00:00:01 5-Warning D04.1 ToD request sent - No Response received;
Jan 01 1970 00:01:07 3-Critical D02.0 DHCP FAILED - Request sent, No response;
Jan 01 1970 00:00:28 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to IP loss ;
Aug 04 2012 01:30:36 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;
Jan 01 1970 00:00:31 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to IP loss ;

This time as soon as it started I launched the excel status logger, it doesn't seem to show anything as far as signal/Power levels when the connection drops.

the only thing that happens is that the error rate goes through the roof.

this is right before and right after.

08/03/2012 9:31:08 PM 597 Mhz -2 dBmV 37 dB 280.0000% 256 QAM 591 Mhz -2 dBmV 37 dB 0.0000% 256 QAM 603 Mhz -2 dBmV 37 dB 0.0000% 256 QAM 609 Mhz -3 dBmV 37 dB 514.2857% 256 QAM
08/03/2012 9:30:08 PM 597 Mhz -2 dBmV 37 dB 280.0000% 256 QAM 591 Mhz -2 dBmV 37 dB 0.0000% 256 QAM 603 Mhz -2 dBmV 37 dB 0.0000% 256 QAM 609 Mhz -3 dBmV 37 dB 514.2857% 256 QAM
08/03/2012 9:29:08 PM 597 Mhz -2 dBmV 37 dB 1040.0000% 256 QAM 591 Mhz -2 dBmV 37 dB 800.0000% 256 QAM 603 Mhz -2 dBmV 37 dB 483.3333% 256 QAM 609 Mhz -3 dBmV 37 dB 585.7143% 256 QAM
08/03/2012 9:28:08 PM 597 Mhz -2 dBmV 37 dB 1040.0000% 256 QAM 591 Mhz -2 dBmV 37 dB 800.0000% 256 QAM 603 Mhz -2 dBmV 37 dB 483.3333% 256 QAM 609 Mhz -3 dBmV 37 dB 585.7143% 256 QAM
08/03/2012 9:27:08 PM 597 Mhz -2 dBmV 37 dB 1040.0000% 256 QAM 591 Mhz -2 dBmV 37 dB 800.0000% 256 QAM 603 Mhz -2 dBmV 37 dB 483.3333% 256 QAM 609 Mhz -3 dBmV 37 dB 585.7143% 256 QAM

saddly it isn't very readable.
I am reluctant to call TS again as the only response I'm going to get is "take the modem to someone elses house" which is really not possible... as I don't know anyone else in my area with a cable connection and it is one of things where I would have to wait for a day when it is happening (like right now)

do the error rates mean anything or is that strictly because the connection has dropped?
Also with the Signal readings the excel cannot connect to the modem while it is rebooting.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Thu, 02 Aug 2012 15:32:33 EDT

tonytoronto posted : well, back to same old shit. Was fine for about 6 days and now doing exactly the same thing, two channels die and down goes the modem. Trying to get it escalated.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 31 Jul 2012 09:52:28 EDT

corellama posted : I did the factory reset and unpluged the coax and let it sit for a few days. Man that messed up the modem for a while, but I'm back to the same problem.

Because Rogers sees the 1.0.5 firmware incomplatiblity they wont go anyfurther to check anything else out and the ticket was closed.

So I'm forced to buy a new modem from Teksavvy. This time it's going to be the Thompson DCM476 STAC.02.50. Hoping ths will solve it but I'm not super confident.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Tue, 31 Jul 2012 00:19:31 EDT

anon posted : Same problem here.
I had a day approximately 10 days ago where the internet completely went down.
It came back up on it's own after a while but things have been flaky since. The modem feels like it has rebooted more times in the past week or two than it has in all of the 2 years i've had it.
This is particularly frustrating since I just recently switched over to a VOIP connection.
Not only have the down speeds deteriorated significantly over the past couple months but the upload speeds are half of what they used to be.

Contemplating asking Teksavvy to send a Rogers tech. Will they ding me the $100 though for a service call?
I would do this firmware change thing that people are talking about but until recently I didn't even know how to access my modem on my browser :huh:

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 23:51:44 EDT

tonytoronto posted :

said by QQCable :

Hi Teddy

I have done the factory reset, no change after that.

from the Signal information my modem is running fine until it reboots...

unfortunately I can not access the modem while the signal drops and when I get access to it again everything is fine once again.

is there a way to log changes in signal/Power levels?

That sounds a lot like what was happening to me, i loose access to modem when goes into its funk. You could remove signal cable from modem, that will also give you access but of course you can't see the signal :) From the logs looks like yours actually reboots, mine did that some months ago before i had upstream bonding, some of your logs are similar to mine back than, turned out cable termination at pole was bad.

Update;
looks like the internet gods are on my side, for the past 5-6 days been stable, nothing on logs, internet been fine. Not sure what happened, i know for sure had nothing to do with Rogers tech, as was ok 2 days or so before he visited. Nothing else changed on my end, so either Rogers finally fixed something or the wind blowing right way last few days.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 23:47:22 EDT

Teddy Boom posted :

said by QQCable :

from the Signal information my modem is running fine until it reboots...
....
is there a way to log changes in signal/Power levels?

Not sure what to tell you in general. I do think you must have a line problem though. Try trading your modem with somebody to see if the problem goes with the modem to their place, or stays at your place even though you have their mdoem. And, let's see if anyone else chimes in on this.

In general, best to post the signal levels, even if they are obviously good values.

Some DSLR users created some cable modem logging stuff a few months ago (read thread for SB6120 stuff):
»[Cable] DCM476 Logger - Track Your Cable Modem Signal Levels, Et
--
electronicsguru.ca/for_sale/Cablemodems

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 21:51:11 EDT

anon posted : Hi Teddy

I have done the factory reset, no change after that.

from the Signal information my modem is running fine until it reboots...

unfortunately I can not access the modem while the signal drops and when I get access to it again everything is fine once again.

is there a way to log changes in signal/Power levels?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 20:45:46 EDT

Teddy Boom posted : Okay, I see.. More related than I was thinking, but I still don't think that's a firmware issue. It seems most likely that your line has an intermittent signal problem.

You should post your signal levels (as screenshot or whatever). You should also be watching your signal levels to see if they get worse while you have the problems, or if they are consistent all the time.
(go to 192.168.100.1 and click signal)

You should also try a factory reset, if you haven't done that already:
1)go to 192.168.100.1
2)click Configuration
3)click the reset button (or restore to defaults or whatever it is)
4)click the reboot button
--
electronicsguru.ca/for_sale/Cablemodems

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 20:02:20 EDT

anon posted : Hi Teddy

The first time this happened it was for around 24 hours, every hour or so my modem would completely reboot, power light went off and everything... every time for 24 hours.

Second time it happened for around 72 hours, at first every hour (full reboot) the last 24 of that weekend it was rebooting every 31 minutes... it did it while I was on the phone with a Tekksavvy rep and he still had no answers.

and again today. I've done the standard power cycle, and the normal Tekk Savvy salvo of trouble shooting steps but they don't do anything.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 19:37:16 EDT

Teddy Boom posted :

said by ftabbbb:

oh... but before I start a new thread, could you please have a look at logs see if it's reboot OR reconnect problem? Thanks a lot!

For me, looking at logs without understanding the symptoms isn't very useful. If your symptoms match what we are discussing here, say so. If your symptoms do not match, you should start a new thread.

Are you are suddenly offline today, and things have been fine until today? If that is the case, it is almost certainly not the issue being discussed here.
--
electronicsguru.ca/for_sale/Cablemodems

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 19:22:24 EDT

ftabbbb posted : oh... but before I start a new thread, could you please have a look at logs see if it's reboot OR reconnect problem? Thanks a lot!

2012-07-30 20:11:39 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:25 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-07-30 19:27:45 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 19:27:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 19:27:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:18 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 19:20:50 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 19:20:50 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 19:20:17 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:04 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:03 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 16:58:14 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 16:58:14 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 16:57:41 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:22 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 16:14:50 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 16:14:50 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 16:14:18 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:20 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 13:27:53 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 13:27:53 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 13:27:20 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 13:18:44 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 13:18:44 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 13:18:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:11 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 12:11:50 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 12:11:50 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 12:11:17 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 12:10:04 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 12:10:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 12:09:32 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 11:49:31 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 11:49:31 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 11:48:59 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:17 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:11 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 09:41:03 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 09:41:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 09:40:31 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:21 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-30 03:00:02 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-30 03:00:02 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-30 02:59:30 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:01:40 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:09 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 6-Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
2012-07-29 21:29:34 6-Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-07-29 21:29:34 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-07-29 21:29:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:08 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:06 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 19:08:10 EDT

Teddy Boom posted :

said by QQCable :

I seem to be having the same issue but my logs are showing something slightly different.

When you say "the same problem"... Have you been getting regular modem reboots (at least once per day, often dozens of times) over an extended period of time (a week, two months)?

said by QQCable :

Jan 01 1970 00:00:55 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;

This line suggests that Rogers is working on something in your neighbourhood. Or they are experiencing a local outage.
--
electronicsguru.ca/for_sale/Cablemodems

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 18:01:22 EDT

anon posted : I seem to be having the same issue but my logs are showing something slightly different.

Jul 30 2012 19:13:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jan 01 1970 00:01:21 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:55 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to IP loss ;
Jul 30 2012 18:42:10 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;
Jan 01 1970 00:00:24 3-Critical R02.0 No Ranging Response received - T3 time-out;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to IP loss
at one point it was doing this every 31 minutes like clockwork... TS said he had never seen this before and my issue has been escalated.

my signal and everything is fine and my firmware is up to date.

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.1-SCM00-NOSH

I assume the IP loss is a different monster but the issue remains the same and unresolved.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 15:23:15 EDT

anon posted : There is a BIG distinction between a modem reboot and reconnect.

A reboot is like a firmware crash due to buggy firmware where as a reconnect is when the firmware decided to give up on a bad connection and decided to reconnect still fully under control.

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 15:00:07 EDT

Teddy Boom posted :

said by ftabbbb:

I have SB5101N though.

Then you do not have THIS problem.

Maybe start a new thread about your issue so people can help you properly. Maybe call tech support.
--
electronicsguru.ca/for_sale/Cablemodems

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Mon, 30 Jul 2012 14:14:53 EDT

ftabbbb posted : I have this Modem reboot problem too. Having a VOIP phone but cut off often these months. I thought it's the phone company problem until I saw this post and check into modem log- many T3 time out there and reboot quite often. I have SB5101N though.
So currently there is no fix for this except firmware upgrade which TSI won't do it?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sun, 29 Jul 2012 23:05:48 EDT

nitzguy posted :

said by aereolis:

+1 Thumbs up absolutely correct except for the part about changing the tap spigot as normal technicians do not carry multitaps and are not allowed to change them

By that I meant moving the sub to another available spigot :). Sometimes not always available like in apartment buildings but if you're in an area with an 8-way tap or a 4-way tap and you have one free, they sometimes try the other spigot to see if that resolves the problem and then tag it to be replaced by a Network facing tech :).

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sun, 29 Jul 2012 21:53:16 EDT

zzmaster posted : Yeah, I'm at Dupont with a SB6120. I'm experiencing the restarts and the intermittent connection problems. It started on July 25 and lasted a day or so. It's back up now and very stable, but I just had to restart my modem about an hour ago. A technician came over but didn't really find anything other then saying the wiring might not be the best in the house, although it's been fine for over a year since I've had internet cable.

Would a different modem work better? Which ones are officially supported?

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 28 Jul 2012 13:34:11 EDT

aereolis posted :

said by nitzguy:

said by Waimea:

I had a solid connection for 2 years before the upstream bonding kicked in and started the same problem. It's definitely the signal that causes this.

here's how it got solved. I had two tech visits, they changed eveything at the tap: connector, spigot, jumper & trap W. No idea what those mean but that's what the tech said he did. The other tech changed the cable that connects the building's riser to my modem. We found it had a few nicks because of the staples. they may have caused intermittent interference, on the line.

Since then, stable connection even tho my upstram signal sits at 52 at its highest.

Like someone said in this thread, the bonding makes the whole thing more sensitive to signal issues. so if you have any slight weaknesses in the cables connecting you to the rogers node then you get those nasty T3 timeouts and the modem loses its mind trying to keep talking to the CMTS.

So have rogers clean up eveything that connects you to them. seems to have worked for me for about 2 months now.

Good luck!

Definitely would be the case, same with downstream as well, but usually not as bad, upstream area from "officially" 5-42mhz is generally "noisy" in comparison to the downstream signal levels, which is why TV stations didn't operate in this band originally when the service was setup back in the NTSC 50's...Channel 2 starts at 55mhz (roughly), so there's a reason why those lower frequencies weren't used but cable had no real options at the time...

Anywho, it wouldn't surprise me that 75% of these issues are signal related, but the techs themselves don't know exactly what to do because in reality they're responsible from the tap down to basically the modem (the techs that you all get to come to your houses/apartments/etc).

You'd also be surprised how much those "notch filters" aka "Trap all frequencies but internet" cause problems in the first place.
Hence with the move to all digital they won't have to have these traps in place and that'll probably solve a lot of issues.

But changing the connector at the tap, the spigot (perhaps attaching you to another spigot because changing the tap itself would be work that they wouldn't want to do as that would cause other users to be out of service, if only briefly), and the jumper which is probably the fact that if you're in an aprtment means it jumps from 1 cable patch panel to another to provide service...

52 is ok...as long as your modem is staying online, again the modem isn't 100% accurate, it may in reality be 51 or 50 dbmv, but is just reporting a bit off because its not meant to be 100% accurate...

So, definitely have them out again, since TSI can't see the modems history of going on and offline, if they could they might see the modem "flapping" and other cool CMTS type terms to see if a modem has a chronic issue....I wish they'd push for more access even at a basic level which I don't think would be an issue, simply have them know which CMTS they connect to, input the modem MAC into the tool, and simply give TSI access to run those technical reports only....but someone at TSI would have to push and someone at Rogers would have to give...same with the other cable ISPs....

But if they can't see the modem ranging and ranging and ranging all the time it is completely useless to try and do any troubleshooting....anywho, wish you guys luck with your issues.

+1 Thumbs up absolutely correct [edit]except for the part about changing the tap spigot as normal technicians do not carry multitaps and are not allowed to change them[/edit]
--
Hello

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 28 Jul 2012 12:52:58 EDT

nitzguy posted :

said by Waimea:

Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120]

Sat, 28 Jul 2012 10:02:03 EDT

Waimea posted : I had a solid connection for 2 years before the upstream bonding kicked in and started the same problem. It's definitely the signal that causes this.

here's how it got solved. I had two tech visits, they changed eveything at the tap: connector, spigot, jumper & trap W. No idea what those mean but that's what the tech said he did. The other tech changed the cable that connects the building's riser to my modem. We found it had a few nicks because of the staples. they may have caused intermittent interference, on the line.

Since then, stable connection even tho my upstram signal sits at 52 at its highest.

Like someone said in this thread, the bonding makes the whole thing more sensitive to signal issues. so if you have any slight weaknesses in the cables connecting you to the rogers node then you get those nasty T3 timeouts and the modem loses its mind trying to keep talking to the CMTS.

So have rogers clean up eveything that connects you to them. seems to have worked for me for about 2 months now.

Good luck!
--
Proud Teksavvy customer since 2007