surfboard SB6141 restarts
- Thread starter billsnaz
- Start date
Solution
- Oct 11, 2014
- 34,874
- 3,323
- 146,290
Bill,
What is happening and/or what circumstances require that the modem be restarted?
Can you log into the modem using your browser? (IP address probably 192.168.100.1)
Just provide some "before and after" details. Thanks.
What is happening and/or what circumstances require that the modem be restarted?
Can you log into the modem using your browser? (IP address probably 192.168.100.1)
Just provide some "before and after" details. Thanks.
Thanks for your reply here is a copy of my sign on this morning after resetting the modem.
May 19 2015 10:03:50 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 10:03:50 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 09:37:44 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:29 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:29 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:04 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:43:33 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:43:33 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 06:19:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:14 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:13 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:12 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:12 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
Channel ID 29 30 31 32 37 38 39 40
Frequency 837000000 Hz 843000000 Hz 849000000 Hz 855000000 Hz 885000000 Hz 891000000 Hz 897000000 Hz 903000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 34 dB 34 dB 36 dB 36 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256 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
-2 dBmV -2 dBmV -3 dBmV -3 dBmV -5 dBmV -6 dBmV -6 dBmV -6 dBmV
Upstream
Bonding Channel Value
Channel ID 4 1 2 3
Frequency 36300000 Hz 18400000 Hz 23300000 Hz 29800000 Hz
Ranging Service ID 503 503 503 503
Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec
Power Level 41 dBmV 39 dBmV 39 dBmV 41 dBmV
Upstream Modulation [3] 16QAM
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] 64QAM
[3] 16QAM
[3] 64QAM
[3] 16QAM
[3] 64QAM
Ranging Status Success Success Success Success
Signal Stats (Codewords)
Bonding Channel Value
Channel ID 29 30 31 32 37 38 39 40
Total Unerrored Codewords 55424424 54811460 54829248 54846395 54802977 54805158 54807212 54804938
Total Correctable Codewords 288 446 349 335 504 27 25 28
Total Uncorrectable Codewords 1688 1722 1458 1594 578 601 661 709
May 19 2015 10:03:50 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 10:03:50 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 09:37:44 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:29 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:29 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:44:04 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:43:33 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 08:43:33 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 06:19:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:14 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:13 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:12 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:12 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
May 19 2015 05:41:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:5c:2d;CMTS-MAC=24:e9:b3:1a:f6:61;CM-QOS=1.1;CM-VER=3.0;
Channel ID 29 30 31 32 37 38 39 40
Frequency 837000000 Hz 843000000 Hz 849000000 Hz 855000000 Hz 885000000 Hz 891000000 Hz 897000000 Hz 903000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 34 dB 34 dB 36 dB 36 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256 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
-2 dBmV -2 dBmV -3 dBmV -3 dBmV -5 dBmV -6 dBmV -6 dBmV -6 dBmV
Upstream
Bonding Channel Value
Channel ID 4 1 2 3
Frequency 36300000 Hz 18400000 Hz 23300000 Hz 29800000 Hz
Ranging Service ID 503 503 503 503
Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec
Power Level 41 dBmV 39 dBmV 39 dBmV 41 dBmV
Upstream Modulation [3] 16QAM
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] 64QAM
[3] 16QAM
[3] 64QAM
[3] 16QAM
[3] 64QAM
Ranging Status Success Success Success Success
Signal Stats (Codewords)
Bonding Channel Value
Channel ID 29 30 31 32 37 38 39 40
Total Unerrored Codewords 55424424 54811460 54829248 54846395 54802977 54805158 54807212 54804938
Total Correctable Codewords 288 446 349 335 504 27 25 28
Total Uncorrectable Codewords 1688 1722 1458 1594 578 601 661 709
- Oct 11, 2014
- 34,874
- 3,323
- 146,290
Bill,
Thanks.
Lots of acronyms involved with DOCSIS.
To keep things simple (mostly for my sake....) the key is the T3-Time-out errors shown in the log.
The cable modem has been sending messages out and not receiving replies. Either the outbound message is not getting to your isp (Cox) or the reply is not getting back. It resets itself and tries again for awhile. Your resets may be forcing an early reset that may or may not succeed.
The cause of problem is likely an intermittent failing cable, splitter, or connector along the connection path into your home.
Overall the DOCSIS network communications are being interrupted and your internet connectivity suffers accordingly.
You will probably need to call Cox for support and they should be able to see the problem after a few tries. They may ask you to read the event log to them. I do not believe that the modem itself is the problem but the combined log events may prove otherwise.
Hopefully a technician will be sent to locate and repair or replace the failing components. And/or the modem.
If you are the curious sort just Google DOCSIS and read some tutorials about it all - half the battle is all of the acronyms. Othewise - just call Cox as you are paying for service.
Thanks.
Lots of acronyms involved with DOCSIS.
To keep things simple (mostly for my sake....) the key is the T3-Time-out errors shown in the log.
The cable modem has been sending messages out and not receiving replies. Either the outbound message is not getting to your isp (Cox) or the reply is not getting back. It resets itself and tries again for awhile. Your resets may be forcing an early reset that may or may not succeed.
The cause of problem is likely an intermittent failing cable, splitter, or connector along the connection path into your home.
Overall the DOCSIS network communications are being interrupted and your internet connectivity suffers accordingly.
You will probably need to call Cox for support and they should be able to see the problem after a few tries. They may ask you to read the event log to them. I do not believe that the modem itself is the problem but the combined log events may prove otherwise.
Hopefully a technician will be sent to locate and repair or replace the failing components. And/or the modem.
If you are the curious sort just Google DOCSIS and read some tutorials about it all - half the battle is all of the acronyms. Othewise - just call Cox as you are paying for service.
TRENDING THREADS
-
-
Question Intel SSD 320 series fried diode (?) CR3, one contact, should I remove it?
- Started by kornsoud
- Replies: 7
-
-
-
-
Question Can I just upgrade my graphics card or should I be upgrading my processor as well for UE5?- Started by Tolstoy1990
- Replies: 6
-
Facebook
Twitter
Instagram