Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Motorola Surfboard SB6141 Lost Connection Issues
My modem keeps dropping connection the last few days and last night it was really bad. It was constantly trying to reboot. Here is what i was able to capture before it tried to reboot again.
| Time | Priority | Code | Message |
|---|---|---|---|
| Jan 01 1970 00:28:45 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:28:44 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:28:40 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:28:24 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:28:02 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:28:02 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:42 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:41 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:22 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:21 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:02 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:27:02 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:26:44 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:26:43 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:26:30 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:26:30 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:26:16 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:25:53 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:25:34 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:25:33 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; |
gmcmenimen
New Contributor
•
Now it is working fine. In an hour it will go again. But here is the signal when it is all working:
[3] 64QAM
[2] 16QAM
[3] 64QAM
[3] 64QAM
[3] 64QAM
0
0
Accepted Solution
KipK
Former Moderator
•
Looks like your upstream transmit power level is hitting the modem's maximum capability at times. Basically, for some reason the modem is having to scream at us to get through, because something is impeding the signal.
Average upstream for your street and node doesn't seem to have any issue and I'm not showing any recent system issues recorded specific to your node, so this is probably some issue with the connections to your modem. Given that it's a relatively new modem, it's less likely to be the modem itself.
However, it could be anywhere between the back of the modem and the tap outside, so I'd recommend the standard procedure:
Double-check any cable connectors you have access to, to make sure they're secure, clean, and in good repair.
Bypass any splitters you can in order to simplify the signal path as much as possible.
Replace any wires or splitters that show signs of excessive wear or age.
If the issue continues once the wiring inside the home has been checked, it would be time for a service call. It may be a problem with something we installed like a signal amplifier, something you wouldn't be expected to replace like a wall plate, etc.
If you need a service call, we can set one up by email, or you can call your local technical support. So let us know if those steps help or if you have any other questions!
0
0
gmcmenimen
New Contributor
•
Thank you for your help. I replaced the splitter in the room where the modem sits and everything is working great now.
0
0