I have new service with a SB6121 and have been experiencing daily reboots since it was installed last Saturday (6/21/2014). Here are the errors that appear in the log:
Jun 26 2014 14:42:52 - 3-Critical - R02.0 - No Ranging Response received - T3 time-out;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:24:47 - 5-Warning - Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;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=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 - 6-Notice - N/A - Cable Modem Reboot due to T4 timeout ;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:24:02 -Critical - R06.0 - Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:24:02 - 3-Critical - R03.0 - Ranging Request Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:24:01 - 3-Critical - R02.0 - No Ranging Response received - T3 time-out;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:55 - 3-Critical - R06.0 - Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:55 -Critical 03.0 - Ranging Request Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:55 - 3-Critical - R02.0 - No Ranging Response received - T3 time-out;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:48 - 3-Critical - R06.0 - Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:48 - 3-Critical - R03.0 - Ranging Request Retries exhausted;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:23:47 - 3-Critical - R02.0 - No Ranging Response received - T3 time-out;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 14:02:45 - 5-Warning - Z00.0 - MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13
6-Notice - N/A able Modem Reboot due to T4 timeout ;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 26 2014 13:52:55
5-Warning
T202.0
Lost MDD Timeout;CM-MAC=3c:36:e4:62:0c:71;CMTS-MAC=00:01:5c:24:a0:81;CM-QOS=1.1;CM-VER=3.0;
Here is the signal info:
Downstream
Bonding Channel Value
Channel ID
1
4
6
8
Frequency
561000000 Hz
579000000 Hz
543000000 Hz
555000000 Hz
Signal to Noise Ratio
37 dB
38 dB
36 dB
37 dB
Downstream Modulation
QAM256
QAM256
QAM256
QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
1 dBmV
1 dBmV
1 dBmV
1 dBmV
Upstream
Bonding Channel Value
Channel ID
1
Frequency
36400000 Hz
Ranging Service ID
15355
Symbol Rate
5.120 Msym/sec
Power Level
45 dBmV
Upstream Modulation
[3] QPSK [3] 64QAM
Ranging Status
Success
I just had a technican come out around 2:30pm and not even 10 minutes after he left, after telling me that everything seemed fine to him, the modem rebooted. Could it be a bad modem or is there some other issue here?