Visitor
•
5 Messages
Frequent disconnects: No Response received, T3 time-out
Hi,
I've been getting a lot of connection drops lately, some taking quite a while to recover.
Modem+Router: Netgear C7000v2
Adapter: Netgear A7000
At first I thought it had to do with the A7000 or with congested channels. After doing troubleshooting on both of those, I read some posts on this forum about similar errors found in modem logs. I'm thinking it maybe has more to do with the cable lines themselves.
After reaching the house, the line runs through two splitters. One is a 1-to-3 that only has one line running out and could probably just be coupled. Another is a 1-to-2 which runs a line to an upstairs bedroom but which I don't actually need or use. Some of the lines are rather old and bent as well. I'm thinking at least eliminating those splitters would help reliability, but I'd prefer to have a technician do it in case it's decided the lines also should be replaced.
Thanks for any help you can give. I've included what I could gather below. Please let me know if you'd like me to provide anything else.
Log
At any given point in time, the log looks similar to this (connection active/"OK"):
2023-1-24, 09:59:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:59:43 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:59:25 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:59:23 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:57:43 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:57:43 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:57:24 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:57:23 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:55:43 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:55:43 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:55:23 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:55:23 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:53:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:53:43 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:53:23 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:53:23 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:51:48 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:51:43 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:51:24 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:51:23 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:49:47 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:49:44 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:49:24 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:49:24 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:47:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:47:44 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:47:25 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:47:24 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:45:44 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:45:44 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:45:26 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:45:24 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:43:45 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
2023-1-24, 09:43:44 | Warning (5) | Dynamic Range Window violation |
2023-1-24, 09:43:26 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; |
When connection drops, I'm seeing this. (Sorry, no pretty formatting ... just copied from a text log):
2023-1-20, 16:30:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
2023-1-20, 16:30:42 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
2023-1-20, 16:30:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
2023-1-20, 16:30:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
2023-1-20, 16:29:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
2023-1-20, 16:29:10 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2023-1-20, 16:29:02 Warning (5) B-INIT-RNG Failure - Retries exceeded;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0;
2023-1-20, 16:27:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0;
2023-1-20, 16:27:21 Warning (5) B-INIT-RNG Failure - Retries exceeded;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0;
2023-1-20, 16:25:15 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.0;CM-VER=3.0;
2023-1-20, 16:25:02 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0;
Channel information (found this in Basic -> Cable Connection after searching 10 minutes through the Advanced section. Yes, certainly basic stuff, Netgear!)
Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Upstream Bonded Channels (Partial Service) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks again.
EG
Expert
•
111.4K Messages
2 years ago
@EmailMeToTheMoon
Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
1
EG
Expert
•
111.4K Messages
2 years ago
@EmailMeToTheMoon
You're good to go. The post is publicly viewable again.
That said. The signal status values at that snapshot in time were OK but the error log entries indicate that something is going on. And there are only 2 upstream channels locked in. Should be 3 to 6. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere. That can be the cause of the un-bonding of the channels.
There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
4
EG
Expert
•
111.4K Messages
2 years ago
Quite welcome !
0
0
EmailMeToTheMoon
Visitor
•
5 Messages
2 years ago
The technician came out and was able to resolve the issue. (Thread started 5 hours ago! Talk about a fast turnaround time.)
Up the pole, there were some wires exposed. When it rained, the process of collecting moisture and drying out was causing interference. I was experiencing intermittent issues, with the connection being fine for days at a time, and then seeing 4-5 disconnects in a day. Being in winter now, weather being more of a factor makes sense, seeing more disconnects in the past few wet months.
Also worth mentioning: apparently an electrical tech had installed a filter on the line in response to the exposed wire. This was why I was down to two bonded upstream channels. Now I've got 6 up, and things are looking stable.
Appreciate everyone who had a role in getting this resolved so quickly! If I should mark an answer as the solution, please let me know.
0
0
EG
Expert
•
111.4K Messages
2 years ago
Not surprised about the high pass filter. Glad that you got it squared away so quickly !
0
0