dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2
share rss forum feed

Fleeced

join:2012-10-06
kudos:2
reply to orion6192

Re: [TWC] Wayland, NY - Issues switching to a SB6141 from an

Nothing wrong with those ping/tracerts. If you're only rebooting the router, it's most likely an issue with the router itself. Try bypassing it or getting a new router.


orion6192

join:2010-06-14
Wayland, NY

1 edit

I'm actually rebooting the modem. The router is a little over a year old and didn't have an issues until the new modem. But... The speed is better. Could it be an incompatibilty between the router and the modem?

Why the level 3 and 4 errors? Is that the modem failing?

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Serial Number: 3487
Firmware Build Time: Aug 18 2011 10:27:53



Insight_TW

@windstream.net

The reboots are caused by the T4 timeouts. TW needs to roll a truck to fix your signals. Would also help to get the firmware up to date but good luck in getting TW to do that.


orion6192

join:2010-06-14
Wayland, NY

What signals are bad? Posted from Meatball in another post:

So, I talked to Motorola, and this guy really sounded like he knew what he was talking about. He's saying it's the signal. The modem needs a signal more along the lines of -5 to +5 dBmV downstream, with closer to 0 being better, and 'high 30's to low 40's' dBmV upstream, with 40 being better. I'm seeing downstream power levels of +6 to +8 and upstream of +35, so he's saying the modem is rebooting because these levels are out of whack. I asked if there was any way I could get a newer firmware, but no dice, they'll only give that out to ISP's.

I'm 0 down and 45 up.

So, with leasing your own modem, your always going to have a modem with out of date firmware and if there is an issue you buy another one?



UKEE

join:2012-05-14
Lexington, KY

It may not be your power levels so much as your signal to noise ratios.

My modem was doing the same T4 timeout until they came out and cleaned up the connection (and put a booster inside my house). I still would have preferred the firmware upgrade, especially since it mentions T4 issues in the change log.


orion6192

join:2010-06-14
Wayland, NY

My log tonight right after reboot:

Jan 28 2013 19:20:15 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:52 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 19:19:01 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 19:19:01 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 19:18:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 19:18:21 4-Error C401.0 DCC-ACK not received;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 19:18:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;
Jan 28 2013 13:00:53 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:b2:e3:e2;CMTS-MAC=00:22:90:c6:6b:3b;CM-QOS=1.1;CM-VER=3.0;