dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1064
share rss forum feed

orion6192

join:2010-06-14
Wayland, NY

2 edits

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

Click for full size
download6141 Doc.pdf 113,973 bytes
Click for full size
downloadDownstream.pdf 12,215 bytes
I recently switched over to Motorola SB 6141 due to the lease fee from TWC. It was brand new, not the white version from Amazon, but from eBay. Speed is great, 25-30 mbps consistently where my Arris Telephone Modem (which I still have for digital phone) was from 3mbps to 25 mbps depending on the days and time. My issue is there seems to be a lag and periods of no response where a reboot is either manually done by me or the router itself. Here is some info:

Ping:

C:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=44ms TTL=46
Reply from 8.8.8.8: bytes=32 time=34ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=37ms TTL=46

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 44ms, Average = 37ms

Tracert:

C:\>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.200.100
2 14 ms 5 ms 5 ms 10.113.176.1
3 12 ms 14 ms 10 ms gig5-1-20.nhvlny01-rtr001.cny.northeast.rr.com [
24.94.35.112]
4 39 ms 61 ms 49 ms cpe-74-74-109-170.stny.res.rr.com [74.74.109.170
]
5 28 ms 13 ms 15 ms rdc-74-74-109-66.cny.northeast.rr.com [74.74.109
.66]
6 16 ms 19 ms 16 ms cpe-74-74-109-46.stny.res.rr.com [74.74.109.46]

7 20 ms 19 ms 19 ms rdc-74-74-108-118.cny.northeast.rr.com [74.74.10
8.118]
8 29 ms 31 ms 31 ms bundle-ether1.albynyyf-rtr000.nyroc.rr.com [24.2
4.21.208]
9 34 ms 30 ms 33 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
10 33 ms 39 ms 48 ms ae-0-0.cr0.nyc30.tbone.rr.com [66.109.6.26]
11 35 ms 39 ms 39 ms 66.109.9.30
12 32 ms 38 ms 57 ms 107.14.19.135
13 91 ms 87 ms 83 ms 66.109.9.66
14 35 ms 128 ms 36 ms 209.85.252.46
15 44 ms 36 ms 39 ms 72.14.236.98
16 34 ms 35 ms 33 ms 72.14.238.82
17 43 ms 38 ms 38 ms 216.239.49.145
18 35 ms 35 ms 43 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

I've attached a PDF of the logs and info from the modem...

Thanks for any help.


kilrathi
Premium
join:2005-04-22
Rockaway Park, NY

Not sure what to say, does it occur when you use direct connection without router? If not then problem is between modem and router for whatever reason.


orion6192

join:2010-06-14
Wayland, NY

Hard to say... Everything is hooked to the router. When I reboot, everything is responsive again.

Do all of the number looks okay? What is up with all the errors and warnings in the log?

Thanks...


Fleeced

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

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;