New Poster
•
3 Messages
No Ranging Response received - T3 time-out; SURFboard SB6141
My modem is constantly giving me the "No Ranging Response received - T3 time-out" error. I am using a SURFboard SB6141 modem. Here are the entries in my error log.
Time | Priority | Code | Message |
---|---|---|---|
Mar 23 2020 06:36:46 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 11:03:26 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:31 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:18 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:49:23 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:18 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:42:55 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:41:21 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:40:57 | 3-Critical | T05.0 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:15:46 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:18 | 6-Notice | N/A | Cable Modem Reboot due to T4 timeout ;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:04:24 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:02:59 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 10:02:36 | 3-Critical | T05.0 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 08:55:39 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:18 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 08:11:05 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:18 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 06:45:14 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
Mar 22 2020 04:18:25 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:f9:ee:a8;CMTS-MAC=18:8b:9d:4a:28:e9;CM-QOS=1.1;CM-VER=3.0; |
mpico48
New Poster
•
3 Messages
5 years ago
Here are my signal readings.
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
0
0
EG
Expert
•
110K Messages
5 years ago
The upstream power is too high, and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
0
0
mpico48
New Poster
•
3 Messages
5 years ago
How does this look
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
[1] 16QAM
[3] 64QAM
0
0