| reply to pleco
Re: [Cable] Teksavvy Cable Constant Modem Restart [SB6120] 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? |
|
|
|
 nitzguyPremium
join:2002-07-11
Sudbury, ON
 ·TekSavvy DSL
| reply to aereolis
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 . |
|
| reply to pleco
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? |
|
 Teddy Boomk kudos Received
join:2007-01-29
Toronto, ON
kudos:5 | 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 |
|
| reply to ftabbbb
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. |
|
| reply to pleco
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. |
|
Teddy Boomk kudos Received
join:2007-01-29
Toronto, ON
kudos:5 | 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 |
|
| reply to Teddy Boom
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 |
|
Teddy Boomk kudos Received
join:2007-01-29
Toronto, ON
kudos:5 | 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 |
|
| reply to pleco
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. |
|
Teddy Boomk kudos Received
join:2007-01-29
Toronto, ON
kudos:5 | 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 |
|
| reply to pleco
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? |
|
Teddy Boomk kudos Received
join:2007-01-29
Toronto, ON
kudos:5 | 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 |
|
Reviews:
 ·TekSavvy Cable
| reply to QQCable
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. |
|
| reply to pleco
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  |
|
| 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. |
|
| reply to pleco
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. |
|
| reply to pleco
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. |
|
| reply to pleco
Tony are you in the North york area? |
|
| said by QQCable:Tony are you in the North york area?
Nah, Bloor and Christie-- Dupont poi |
|
