dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5814
share rss forum feed

Smudge1

join:2010-01-10
Salt Lake City, UT

[Connectivity] Modem reboots due to T4 timeouts

1) Your location: City and State.
Salt Lake City, UT

2) A description of the problem.
The modem is rebooting multiple times a day due to a T4 timeout

3) Is the issue intermittent, constant or does it occur at a specific time of day?
Intermittently throughout the day. Do not happen a specific times.

4) Your modem make, model & firmware version.

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB6120-1.0.2.3-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: 317001932100858805030011
Firmware Build Time: Oct 15 2009 16:52:28

HFC MAC Address: 00-22-10-2C-93-9C
5) Describe any home networking if applicable. (i.e. routers, hubs, adapters, etc.)
Modem > Linksys WRT54G wireless router then to multiple computers.

Problem still occurs when I have a single computer (Mac Laptop) wired directly to the modem.

There is a single line splitter right before the modem going to my TiVo. Problem still occurs when I have removed the splitter and the modem is directly connected. There are no other splitters between the modem and the connection outside on the pole.

6) List any firewall and/or anti-virus software you have installed.
None.

I recently upgraded to the 50/10 extreme package using a Motorola SB6120 modem.

Here are the log entries showing the T4 timeouts. T3 timeouts happen but they do not cause reboots.

Jan 01 1970 00:00:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 19:34:19 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 12:54:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 09:00:48 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 07:12:58 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:17 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 06:58:46 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 06:43:08 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 06:32:23 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 10 2010 06:04:14 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:01:5c:24:90:82;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:93:9c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
 

•and the signal
Downstream  		Bonding Channel Value
Channel ID 2 3 4
Frequency 519000000 Hz 525000000 Hz 531000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256
Power Level -4 dBmV -4 dBmV -4 dBmV

Upstream Bonding Channel Value
Channel ID 7
Frequency 34400000 Hz
Ranging Service ID 2158
Symbol Rate 5.120 Msym/sec
Power Level 42 dBmV
Upstream Modulation [3] QPSK
[3] 16QAM
Ranging Status Success

Signal Stats (Codewords) Bonding Channel Value
Channel ID 2 3 4
Total Unerrored Codewords 155233563 155233773 155233951
Total Correctable Codewords 12 0 0
Total Uncorrectable Codewords 1560 1465 1406


beachintech
There's sand in my tool bag
Premium
join:2008-01-06
kudos:5
Reviews:
·Comcast

1 edit

You need a tech visit. If there's no problems in the house, then they can get the ball rolling to have a maint tech look into the mainline.

Edit: How much cable would you guess is between the modem and the connection on the pole/pedestal outside?
--
Tech at the Beach.
I speak for myself, not my employer.


Smudge1

join:2010-01-10
Salt Lake City, UT

Ok. I'll give them a call. I was hoping it was something I could fix.

I would guess the cable run is about 300-400 feet.



Tordek
Make the outages go away
Premium
join:2009-09-07
Great White
kudos:2
reply to Smudge1

I agree with Beach, there are about ~10 T4's there that would cause problems. all of the 1970's are from modem startups.