Regular Visitor
•
1 Message
No Ranging Response received - T3 time-out Disconnects and modem reboots
It seems to be a common problem, but I'm in need of some assistance with this issue as well...
| Time | Priority | Code | Message |
|---|---|---|---|
| Jun 22 2020 08:39:09 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 08:39:08 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 08:39:07 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 08:38:47 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 08:25:55 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:48:32 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:48:12 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:48:12 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:46:57 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:38:53 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:29:20 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:06:57 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 22 2020 07:06:56 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:32:24 | 3-Critical | R06.0 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:32:24 | 3-Critical | R03.0 | Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:32:21 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:32:20 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:31:41 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:31:40 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
| Jun 21 2020 23:31:04 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:9a:fd;CMTS-MAC=00:27:90:ff:b7:23;CM-QOS=1.1;CM-VER=3.0; |
Picture of signals just after an event.
Steps I've taken to trouble shoot thus far (issue has been on and off for a year, but has gotten progressively worse over the last few months):
-Eliminated splits between comcast line and modem.
-Repalced modem (new modem has same issue)
-unplugged router/switch/AP from modem over night, error occurred.
-Plugged modem directly into comcast line (outside in sealed container), and let sit over night, error occurred (t3 time out errors resulting in t4)
-I've plugged Ethernet directly into back of modem, and interruptions in service still happen.
Although when modem is just by itself, I can't tell if a disconnect would happen or not, the disconnect correlate with the T3 errors, so I feel confident in one is causing the other.
I think I may need to schedule a technician visit unless anyone else can think of some steps to take.
Thanks!
EG
Expert
•
111.5K Messages
5 years ago
The upstream power on channels 2 and 3 is on the high side 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