New Poster
•
1 Message
Motorola SB6141 Dropping Internet Connection Multiples Times A Day
Within the last few weeks, my Motorola SB6141 modem has begun dropping it's connection multiple times a day. Logging into the modem, it shows that it is encountering a T3 timeout with "no ranging response received". All of the connections are tight at the wall and on the mode, There is a single splitter that splits the signal to the cable box and the modem. Last year, a Comcast tech came out and completely changed out the line from the box at the street to the house, so that should not be the problem. I am trying to figure out whether this may be a modem issue and it needs to be replaced (it is going on 7 years old), or if I need to have a Comcast tech come out again (which would not be preferred under current circumstances unless all of the work needs to be done outside). Below are the logs and signal from the modem itself:
Time | Priority | Code | Message |
Oct 24 2020 12:21:13 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:13 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:13 | 3-Critical | R03.0 | Ranging Request Retries exhausted;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:13 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:06 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:06 | 3-Critical | R03.0 | Ranging Request Retries exhausted;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 11:14:06 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Oct 24 2020 10:58:18 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:06:00 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:05:35 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:04:43 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:04:34 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:03:43 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:03:34 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:02:37 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:02:23 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:01:31 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:01:22 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:25 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:01:5c:69:18:78;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:f7:45:f2;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Downstream | Bonding Channel Value | |||||||
Channel ID | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 |
Frequency | 627000000 Hz | 633000000 Hz | 639000000 Hz | 645000000 Hz | 651000000 Hz | 657000000 Hz | 663000000 Hz | 669000000 Hz |
Signal to Noise Ratio | 38 dB | 38 dB | 38 dB | 38 dB | 37 dB | 38 dB | 38 dB | 37 dB |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 |
Power Level | -3 dBmV | -3 dBmV | -3 dBmV | -5 dBmV | -5 dBmV | -4 dBmV | -5 dBmV | -5 dBmV |
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 |
Upstream | Bonding Channel Value | |||
Channel ID | 5 | 8 | 7 | 6 |
Frequency | 35600000 Hz | 16400000 Hz | 22800000 Hz | 29200000 Hz |
Ranging Service ID | 9299 | 9299 | 9299 | 9299 |
Symbol Rate | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec |
Power Level | 51 dBmV | 49 dBmV | 50 dBmV | 51 dBmV |
Upstream Modulation | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM | [2] QPSK [1] 32QAM [3] 64QAM |
Ranging Status | Success | Success | Success | Success |
Responses
EG
Expert
•
86.6K Messages
7 m ago
The upstream power is too high and it may be intermittently fluctuating even higher out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
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.
If nothing above applies, then bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home.
Good luck !
0
0