My SB6141 keeps rebooting a few times a day. I’ve called my ISP to make sure it’s not something on their end and they said it looks like the modem is trying to get an update, fails to get it and then reboots.
Once it reboots everything works great. Speed is fine and all lights are normal.
Any advice on how to get the update to finish or cancel the process completely so the modem stays up?
Thanks!
Logs below:
(edit: CM-MAC information removed)
TimePriorityCodeMessageOct 26 2022 08:27:173-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:16:373-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:394-ErrorC701.0DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:375-WarningU102.0TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:373-CriticalR08.016 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:373-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:373-CriticalR08.016 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:363-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 08:06:213-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:51:263-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:50:565-WarningU102.0TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:50:565-WarningU103.0Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:50:393-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:49:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Jan 01 1970 00:00:186-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:48:183-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:44:504-ErrorC701.0DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:44:485-WarningU102.0TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:44:483-CriticalR08.016 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;Oct 26 2022 07:44:483-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:90:f0:50:00:00;CM-QOS=1.1;CM-VER=3.0;