2 Messages
No Ranging Response received - T3
Connection is going out once every few minutes due to WAN port being auto-shut off on our tp link router. I had a feeling that was due to an upstream issue. Looked at the motorola modem and found many of these T3 time-outs. All of my connections are finger tight. Given the values, should I escalate to Xfinity to get a technician on site?
Event Log
Log
Time Priority Description
Sun Jun 02 10:13:59 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:14:10 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Jun 02 10:17:23 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:21:43 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:22:04 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:22:08 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Jun 02 10:23:06 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:23:39 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:24:04 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:25:10 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:25:23 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:25:43 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:25:47 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Jun 02 10:34:42 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:39:02 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:39:24 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:39:26 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:39:31 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Jun 02 10:46:32 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:50:52 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:51:19 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:51:27 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Sun Jun 02 10:53:45 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:53:45 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:53:45 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:53:46 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:53:46 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:53:46 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:54:38 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:58:58 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 02 10:59:12 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=<>;CMTS-MAC=<>;CM-QOS=1.0;CM-VER=3.0;
Sun Jun 02 10:59:29 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 21 543.0 -4.8 40.1 15736 26322
2 Locked QAM256 1 417.0 -5.7 39.9 24589 25441
3 Locked QAM256 2 423.0 -5.7 39.8 26909 28280
4 Locked QAM256 3 429.0 -5.6 39.9 23654 26929
5 Locked QAM256 4 435.0 -5.7 39.9 23718 26201
6 Locked QAM256 5 441.0 -5.6 39.8 23007 25556
7 Locked QAM256 6 447.0 -5.5 39.9 21518 24086
8 Locked QAM256 7 453.0 -5.6 39.9 23438 25814
9 Locked QAM256 8 459.0 -5.4 39.9 19729 24376
10 Locked QAM256 9 465.0 -5.4 39.9 21275 25221
11 Locked QAM256 10 471.0 -5.2 39.5 18950 24547
12 Locked QAM256 11 477.0 -5.1 40.0 19039 23521
13 Locked QAM256 12 483.0 -5.3 40.0 19334 25314
14 Locked QAM256 13 489.0 -4.7 40.2 16632 22433
15 Locked QAM256 14 495.0 -5.2 40.1 18700 23717
16 Locked QAM256 15 507.0 -5.2 36.9 18755 23131
17 Locked QAM256 16 513.0 -4.4 41.2 17961 31841
18 Locked QAM256 17 519.0 -4.7 41.3 16439 24895
19 Locked QAM256 18 525.0 -4.6 41.2 19363 32615
20 Locked QAM256 19 531.0 -4.6 41.3 15030 23702
21 Locked QAM256 20 537.0 -4.6 41.0 18461 30780
22 Locked QAM256 22 549.0 -4.7 41.2 14501 22095
23 Locked QAM256 23 561.0 -4.5 41.1 13827 23667
24 Locked QAM256 24 567.0 -4.7 41.3 15659 28381
Total 466224 618865
Upstream Bonded Channels
Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 74 5120 22.8 50.5
2 Locked ATDMA 73 5120 16.3 50.8
3 Locked ATDMA 75 5120 29.2 50.8
4 Locked ATDMA 76 5120 35.6 50.8
5 Not Locked Unknown 0 0 0 0.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
EG
Expert
•
111.3K Messages
1 year ago
Both the downstream and the upstream power levels are borderline and they may be intermittently fluctuating even farther to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are 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 from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
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.
Good luck with it !
0
0
XfinitySara
Official Employee
•
1.8K Messages
1 year ago
Hey there, @ridgemgmt! Thanks for creating a post about your connectivity concerns. Our Digital Care Team remains here to help however we can! Have you had a chance to review our Expert, EG's, recommendations yet?
0
ridgemgmt
2 Messages
1 year ago
> check to see if there are any excess/unneeded coax cable splitters
I had a 1 (coax coming from the road) -> 3 splitter (1 of the 3 outputs goes into the modem). I have since removed the splitter and the connection has been significantly more stable (no downtime in 2 days). However, I just received another T3 timeout which caused a few seconds of downtime.
I can live with this for now, but if it occurs again in the next 2 days I will be scheduling an appointment with the tech, as this sounds like it could be a combination of issues, given the T3 timeouts are still occuring with a direct connection.
1
0
EG
Expert
•
111.3K Messages
1 year ago
@ridgemgmt
For curiosity, Please post what the signal stats look like now without the splitter being in the mix.
0
0