U

Contributor

 • 

17 Messages

Thursday, October 19th, 2023 3:26 AM

Closed

intermittent desyncs and disconnects getting worse

Suddenly in the last few weeks I've been experiencing intermittent desyncs and brief disconnects.

Prior to this time, I couldn't tell you when I last had issues beyond the rare widespread service outage.

The current issues seem "streaky", in that I can go hours with no issues at all, then suddenly I'm plagued with them every few minutes for an hour or two or more.           

In the last couple of days it seems to be much worse, though that's anecdotal as I have not been keeping detailed logs throughout this period.

Any insight into what the problem might be is greatly appreciated!

           

Cable Modem: MB8600

           

DOWNSTREAM

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 42 405 11.3 43.9 10990 7838
2 Locked QAM256 1 453 9.8 43.3 6608 4570
3 Locked QAM256 2 459 10.1 43.3 5841 5463
4 Locked QAM256 3 465 10 43.3 4687 4230
5 Locked QAM256 4 471 9.7 43 5681 5055
6 Locked QAM256 5 477 9.7 43 5040 4881
7 Locked QAM256 6 483 9.8 43.1 3735 3075
8 Locked QAM256 7 489 10 43.1 4345 4589
9 Locked QAM256 8 495 10 43 4661 4774
10 Locked QAM256 9 507 10.3 43 3739 3728
11 Locked QAM256 10 513 10.6 43.4 3161 3373
12 Locked QAM256 11 519 10.3 43.1 2966 2546
13 Locked QAM256 12 525 10.4 43.2 3453 4104
14 Locked QAM256 13 531 10.8 43.2 2894 3577
15 Locked QAM256 14 537 10.3 43 2399 2162
16 Locked QAM256 15 543 10.2 42.9 2904 3006
17 Locked QAM256 16 549 10.1 42.9 2468 2673
18 Locked QAM256 17 555 9.7 42.9 2421 2185
19 Locked QAM256 18 561 9.5 42.6 2624 2995
20 Locked QAM256 19 567 9.4 42.6 2036 1849
21 Locked QAM256 20 573 9 42.2 2316 2209
22 Locked QAM256 21 579 8.9 42 3043 3079
23 Locked QAM256 22 585 8.7 41.9 2114 1783
24 Locked QAM256 23 591 8.3 41.6 2143 1762
25 Locked OFDM PLC 37 690 9 40.5 179160725 2617
26 Locked QAM256 38 429 10.7 43.5 6607 5157
27 Locked QAM256 39 435 10.4 43.5 7377 5386
28 Locked QAM256 40 441 10.2 43.3 8370 6682
29 Locked QAM256 41 447 10 43.3 5849 4980
30 Locked QAM256 43 411 11.2 43.8 9415 7302
31 Locked QAM256 44 417 10.9 43.7 9452 6359
32 Locked QAM256 45 423 10.7 43.5 9770 6912
           
           
UPSTREAM

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 1 5120 35.6 46.5
2 Locked SC-QAM 2 5120 29.2 46.5
3 Locked SC-QAM 3 5120 22.8 46.5
4 Locked SC-QAM 4 5120 16.4 46.5
5 Locked SC-QAM 5 1280 39.6 47.3

           

           

EVENT LOG

Note that the first two lines here correspond to a reboot of the modem, I left out the prior lines from the reboot assuming they were fairly standard, but can easily add that if necessary.

           

Time Priority Description
19:38:42
Wed Oct 18 2023
Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
19:38:42
Wed Oct 18 2023
Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
19:38:48
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
19:38:48
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
19:38:48
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
19:38:48
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
19:38:48
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
19:38:52
Wed Oct 18 2023
Critical (3) No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:23
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:24
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
21:18:24
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
21:18:24
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
21:18:24
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
21:18:28
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:29
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:18:33
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:34
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:18:38
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:39
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:18:42
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:18:49
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:19:38
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:19:55
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
21:19:55
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
21:21:45
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:29:40
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
21:29:43
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:31:50
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
21:36:29
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
21:36:29
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
21:36:29
Wed Oct 18 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
21:36:29
Wed Oct 18 2023
Warning (5) Dynamic Range Window violation
21:36:30
Wed Oct 18 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;

Contributor

 • 

17 Messages

2 years ago

Additional logging from overnight:

Time Priority Description
22:06:08
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
22:09:09
Wed Oct 18 2023
Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
02:15:06
Thu Oct 19 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
02:15:07
Thu Oct 19 2023
Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
02:15:07
Thu Oct 19 2023
Warning (5) Dynamic Range Window violation
02:15:07
Thu Oct 19 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;

Expert

 • 

110.3K Messages

2 years ago

This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.


The downstream power is high / strong. It may be over-driving the front-end receiver circuit of the modem. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.


Is there a drop amplifier on the coax cable line leading to the modem ? If so, try removing / bypassing it and see. If not, you can try installing a -6 dB forward path-only attenuator pad such as this one on the coax port on the rear of the modem to knock that power level down and see;


https://www.amazon.com/FPA6-54-Forward-Attenuator-DOCSIS-Internet/dp/B08KTRC3XZ  


It won't affect the upstream power level which is within spec. Good luck !

Contributor

 • 

17 Messages

@EG​ For ~$10 this attenuator is easily worth a shot; should have it sometime tomorrow and will follow-up here if it helps. Thanks for taking a look and the suggestion.

Expert

 • 

110.3K Messages

2 years ago

You're welcome ! Please do post back here with how it goes, thanks.

Contributor

 • 

17 Messages

Attenuator got here nice and early today (thanks Amazon).

Downstream power levels are all now in the range of 2.2-5.6 dBmV.

Will report back again in a day or two on whether stability has improved or not.

Expert

 • 

110.3K Messages

2 years ago

@user_71gucl 

Thanks for the update. Fingers crossed ! 🤞

Contributor

 • 

17 Messages

Things are demonstrably better. I haven't personally noticed a disconnect/desync since adding the attenuator, though the modem logs indicate there are still some periodic issues.
For the moment I'm not bothered enough to continue fighting this, but for the sake of completeness I'll include the recent logs and updated downstream channel info.

Thanks again, EG, for taking time to look at this and for the suggestion of the attenuator.

           

Time Priority Description
06:26:15
Sat Oct 21 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
06:41:16
Sat Oct 21 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
13:17:46
Sat Oct 21 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
13:17:46
Sat Oct 21 2023
Warning (5) Dynamic Range Window violation
13:17:46
Sat Oct 21 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
13:17:46
Sat Oct 21 2023
Warning (5) Dynamic Range Window violation
13:20:11
Sat Oct 21 2023
Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
13:20:11
Sat Oct 21 2023
Warning (5) Dynamic Range Window violation
19:08:04
Sat Oct 21 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
22:02:48
Sat Oct 21 2023
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-QOS=1.1;CM-VER=3.1;
17:27:38
Sun Oct 22 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
           
Current status of the Downstream channels:

           

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 42 405 5.7 44.4 9481 5798
2 Locked QAM256 1 453 4.2 43.7 4404 4052
3 Locked QAM256 2 459 4.3 43.7 3392 5237
4 Locked QAM256 3 465 4.3 43.7 2704 4021
5 Locked QAM256 4 471 4 43.5 3542 4569
6 Locked QAM256 5 477 3.8 43.4 3073 4912
7 Locked QAM256 6 483 4 43.6 2168 3269
8 Locked QAM256 7 489 4.1 43.4 2741 3988
9 Locked QAM256 8 495 4 43.2 2815 4924
10 Locked QAM256 9 507 4.5 43.4 2353 3838
11 Locked QAM256 10 513 4.5 43.6 2051 3925
12 Locked QAM256 11 519 4.3 43.3 2113 3210
13 Locked QAM256 12 525 4.3 43.5 2579 4476
14 Locked QAM256 13 531 4.7 43.4 2052 3859
15 Locked QAM256 14 537 4.3 43.4 1954 2497
16 Locked QAM256 15 543 4.1 43.3 2041 4085
17 Locked QAM256 16 549 3.9 43.4 1903 3716
18 Locked QAM256 17 555 3.7 43.2 1760 3071
19 Locked QAM256 18 561 3.3 42.9 2193 3659
20 Locked QAM256 19 567 3.2 42.6 1557 2927
21 Locked QAM256 20 573 3 42.4 1806 2797
22 Locked QAM256 21 579 2.7 42.2 1808 3998
23 Locked QAM256 22 585 2.6 42.1 1444 3027
24 Locked QAM256 23 591 2.4 41.8 1752 2567
25 Locked OFDM PLC 37 690 2.8 40.6 -1056651641 16869
26 Locked QAM256 38 429 5 44 3352 4442
27 Locked QAM256 39 435 4.8 44 4501 4521
28 Locked QAM256 40 441 4.5 43.7 5386 5675
29 Locked QAM256 41 447 4.3 43.8 3513 4211
30 Locked QAM256 43 411 5.5 44.3 5983 5884
31 Locked QAM256 44 417 5.4 44.2 8725 4706
32 Locked QAM256 45 423 5.1 44.2 7593 5379

Contributor

 • 

17 Messages

1 year ago

About a month ago I report a similar issue here; thanks to forum user EG I found what I thought was the work-around (attenuator for downstream power), but in the last couple of days the problems have returned and are at least as bad (if not worse) than previously.


Original forum post for reference: https://forums.xfinity.com/conversations/your-home-network/intermittent-desyncs-and-disconnects-getting-worse/6530a1f0e05b5f65da02f615


Here are event logs (Motorola MB8600) from the last 24hrs, excluding "Notice" log level events:

Time Priority Description
18:56:34
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
18:56:35
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:20
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:20
Wed Nov 29 2023
Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:20
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:24
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
19:18:25
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:12:52
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:33
Wed Nov 29 2023
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:34
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:35
Wed Nov 29 2023
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:44
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:48
Wed Nov 29 2023
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:51
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:52
Wed Nov 29 2023
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:16:57
Wed Nov 29 2023
Critical (3) CMSTATUS:US_Diplexer_Mode_Change:Fixed Initial, 5-42MHz.
20:16:59
Wed Nov 29 2023
Critical (3) CMSTATUS:US_Diplexer_Mode_Change:TLV-9, 5-42MHz.
20:17:07
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:17:20
Wed Nov 29 2023
Critical (3) CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
20:17:20
Wed Nov 29 2023
Critical (3) CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
20:17:20
Wed Nov 29 2023
Critical (3) CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
20:47:48
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:47:48
Wed Nov 29 2023
Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:47:48
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:47:51
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:47:52
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:47:57
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:07
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:16
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:16
Wed Nov 29 2023
Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:16
Wed Nov 29 2023
Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:17
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:18
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:20
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:20
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:24
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:24
Wed Nov 29 2023
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
20:48:25
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
21:47:14
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:10:30
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:10:30
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:44
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:44
Wed Nov 29 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:44
Wed Nov 29 2023
Warning (5) Dynamic Range Window violation
22:36:44
Wed Nov 29 2023
Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:44
Wed Nov 29 2023
Warning (5) Dynamic Range Window violation
22:36:45
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:45
Wed Nov 29 2023
Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
22:36:45
Wed Nov 29 2023
Warning (5) Dynamic Range Window violation
22:36:46
Wed Nov 29 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
00:44:25
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
02:37:37
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
04:51:09
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
04:54:06
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
10:10:44
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;
11:37:49
Thu Nov 30 2023
Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[removed];CMTS-MAC=[removed];CM-QOS=1.1;CM-VER=3.1;


Downstream channel status:

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 9 507 0.3 42.9 22031 23776
2 Locked QAM256 1 453 0.4 43.1 27228 28169
3 Locked QAM256 2 459 0.5 42.7 27011 31975
4 Locked QAM256 3 465 0.4 43 24895 28490
5 Locked QAM256 4 471 0 42.9 26124 28928
6 Locked QAM256 5 477 -0.1 42.8 26575 31089
7 Locked QAM256 6 483 0.1 42.9 22073 23633
8 Locked QAM256 7 489 0.1 42.7 23592 25699
9 Locked QAM256 8 495 0 42.7 25480 30620
10 Locked QAM256 10 513 0.4 42.9 21415 24731
11 Locked QAM256 11 519 0.2 42.9 20974 21883
12 Locked QAM256 12 525 0.1 42.7 21919 25608
13 Locked QAM256 13 531 0.4 42.7 20610 24601
14 Locked QAM256 14 537 0 42.4 18717 19045
15 Locked QAM256 15 543 -0.3 42.6 20059 22509
16 Locked QAM256 16 549 -0.5 42.5 19177 24034
17 Locked QAM256 17 555 -0.8 42.3 18598 19561
18 Locked QAM256 18 561 -1.2 42 19718 21853
19 Locked QAM256 19 567 -1.3 41.9 17683 19612
20 Locked QAM256 20 573 -1.6 41.5 17627 18291
21 Locked QAM256 21 579 -1.9 41.3 19027 22764
22 Locked QAM256 22 585 -2.1 41.1 17494 19873
23 Locked QAM256 23 591 -2.3 40.9 17327 17477
24 Locked OFDM PLC 37 690 -2.2 39 1244069560 101671
25 Locked QAM256 38 429 1.4 43.6 28448 30923
26 Locked QAM256 39 435 1.1 43.6 28349 30933
27 Locked QAM256 40 441 0.8 43.3 30601 35316
28 Locked QAM256 41 447 0.5 43.2 28028 30823
29 Locked QAM256 42 405 2.2 44 33452 36276
30 Locked QAM256 43 411 2 43.9 32938 39226
31 Locked QAM256 44 417 1.8 43.9 31304 32734
32 Locked QAM256 45 423 1.5 43.5 32043 34001


Upstream channel status:

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked SC-QAM 1 2560 10.4 47.8
2 Locked SC-QAM 2 5120 16.4 47.3
3 Locked SC-QAM 3 5120 22.8 47
4 Locked SC-QAM 4 5120 29.2 47.5
5 Locked SC-QAM 5 5120 35.6 47.5
6 Locked SC-QAM 11 1280 39.6 48.3


Fingers crossed one of you wizards has another miracle in store...

Note: This comment was created from a merged conversation originally titled frequent t3 errors (disconnects, drops, errors, etc)

Contributor

 • 

17 Messages

1 year ago

Just to rule out at least one possibility, I got a newer cable modem yesterday (Arris S33), but it quite clearly has not helped.

Updated Connection status and Logs from the last ~hour or so below...

Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected
Uncorrectables
42 Locked QAM256 405000000 Hz 0 dBmV 43 dB 1791 2551
1 Locked QAM256 453000000 Hz -1 dBmV 43 dB 1400 1923
2 Locked QAM256 459000000 Hz -1 dBmV 42 dB 1487 2349
3 Locked QAM256 465000000 Hz -1 dBmV 43 dB 1396 1792
4 Locked QAM256 471000000 Hz -1 dBmV 43 dB 1504 1879
5 Locked QAM256 477000000 Hz -2 dBmV 43 dB 1569 2253
6 Locked QAM256 483000000 Hz -1 dBmV 43 dB 1169 1447
7 Locked QAM256 489000000 Hz -1 dBmV 43 dB 1305 1663
8 Locked QAM256 495000000 Hz -1 dBmV 42 dB 1438 2193
9 Locked QAM256 507000000 Hz -1 dBmV 43 dB 1174 1473
10 Locked QAM256 513000000 Hz -1 dBmV 43 dB 1140 1636
11 Locked QAM256 519000000 Hz -1 dBmV 43 dB 1011 1501
12 Locked QAM256 525000000 Hz -1 dBmV 43 dB 1373 1846
13 Locked QAM256 531000000 Hz -1 dBmV 43 dB 1135 1679
14 Locked QAM256 537000000 Hz -2 dBmV 42 dB 846 1273
15 Locked QAM256 543000000 Hz -2 dBmV 42 dB 1139 1552
16 Locked QAM256 549000000 Hz -2 dBmV 42 dB 1038 1780
17 Locked QAM256 555000000 Hz -2 dBmV 42 dB 896 1386
18 Locked QAM256 561000000 Hz -3 dBmV 42 dB 997 1586
19 Locked QAM256 567000000 Hz -3 dBmV 42 dB 854 1433
20 Locked QAM256 573000000 Hz -3 dBmV 42 dB 900 1381
21 Locked QAM256 579000000 Hz -3 dBmV 41 dB 930 1716
22 Locked QAM256 585000000 Hz -4 dBmV 41 dB 885 1505
23 Locked QAM256 591000000 Hz -4 dBmV 41 dB 842 1316
37 Locked OFDM PLC 690000000 Hz -3 dBmV 40 dB 973263858 15483
38 Locked QAM256 429000000 Hz 0 dBmV 43 dB 1470 2069
39 Locked QAM256 435000000 Hz 0 dBmV 43 dB 1444 2238
40 Locked QAM256 441000000 Hz -1 dBmV 43 dB 1541 2623
41 Locked QAM256 447000000 Hz -1 dBmV 43 dB 1513 2064
43 Locked QAM256 411000000 Hz 0 dBmV 44 dB 1898 3338
44 Locked QAM256 417000000 Hz 0 dBmV 44 dB 1659 2168
45 Locked QAM256 423000000 Hz 0 dBmV 43 dB 1716 2236

Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 10400000 Hz 3200000 47.5 dBmV
2 Locked SC-QAM 16400000 Hz 6400000 47.0 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 47.3 dBmV
4 Locked SC-QAM 29200000 Hz 6400000 47.0 dBmV
5 Locked SC-QAM 35600000 Hz 6400000 47.0 dBmV
11 Locked SC-QAM 39600000 Hz 1600000 47.5 dBmV

Date Time Event Level Description
1/12/2023
09:30:51
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:52
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:52
5 Dynamic Range Window violation
1/12/2023
09:30:52
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:52
5 Dynamic Range Window violation
1/12/2023
09:30:52
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:52
5 Dynamic Range Window violation
1/12/2023
09:30:53
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:54
5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:30:54
5 Dynamic Range Window violation
1/12/2023
09:36:12
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:36:12
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:36:12
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:36:14
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:36:17
3 Successful LAN WebGUI login from 76.26.212.207 on 23/12/01 at 9:36 AM.
1/12/2023
09:36:32
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:37:04
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:37:04
5 Dynamic Range Window violation
1/12/2023
09:37:06
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:54:34
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:55:56
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:55:56
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:55:56
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:56:04
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
09:56:08
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:08
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:08
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:08
3 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:09
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:13
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:13
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:13
3 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:26
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
10:13:33
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;

Contributor

 • 

17 Messages

1 year ago

This is starting to feel like a personal blog...

I took a look at the Comcast installed box on the side of my house, and while everything looks ok there, I did find an unnecessary splitter; I've removed it, hoping it might help the signal strength (if that's even the issue at this point), but it unfortunately hasn't seemed to help at all.

More event logs from this afternoon:

Date Time Event Level Description
1/12/2023
11:00:40
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
11:00:51
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
11:18:06
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
12:10:30
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
13:39:52
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
13:39:52
5 Dynamic Range Window violation
1/12/2023
13:39:52
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
13:39:52
5 Dynamic Range Window violation
1/12/2023
13:39:52
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:23:23
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:12
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:12
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:12
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:22
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:37
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:37
3 No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:38
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:39
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:39
5 Dynamic Range Window violation
1/12/2023
15:24:39
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:39
5 Dynamic Range Window violation
1/12/2023
15:24:39
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:39
5 Dynamic Range Window violation
1/12/2023
15:24:39
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:39
5 Dynamic Range Window violation
1/12/2023
15:24:41
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:42
5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
1/12/2023
15:24:42
5 Dynamic Range Window violation

Official Employee

 • 

1.2K Messages

Hello, @user_71gucl I appreciate the follow-up information, and sorry to hear the issues have returned after getting the recommended attenuator. At this point I think we should do some investigation on your area equipment signals being sent to your equipment, and can start troubleshooting the connection. 

 

When you have time please send a direct message, since I'll need some information to locate your account: 

 

nd a direct message: 

 

Click "Sign In" if necessary

 

• Click the "Direct Message" icon in the upper right - it looks like a chat bubble  

• Click the "New message" (pencil and paper) icon just to the right of Conversations

• Type "Xfinity Support" in the "To:" line - do not use the Employee's name!

• Type your message in the text area near the bottom of the window

• Press Enter to send it

To expedite your request, we ask that you please include your name, the account holder name (if different), and the service address. 

 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Official Employee

 • 

1.2K Messages

@user_71gucl  I appreciate you sending the direct message with the requested information, I'll follow up with you there to continue troubleshooting. Thank you.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

17 Messages

1 year ago

For anyone still following along at home, Justin kindly took a look at what he could remotely, and determined that my own signals as well as some neighbors in the area "don't look solid", so we agreed to have a technician come out to have a look. That should happen mid-day on this Tuesday the 5th, after which I'll follow-up here with what we've learned.

Thanks for your time and help today, Justin!

Contributor

 • 

17 Messages

1 year ago

tl/dr:  things are better

Last night and again this morning I received a call from Comcast Tech Support; apparently my issue had been escalated to their team. Both people I spoke with indicated "something" had been investigated and corrected, and asked if my service was now working properly. I tried to explain to both that my issue was intermittent; and, while on the phone with them things were normal, I didn't necessarily have any expectation that things would continue to be normal given the recent history. I do not wish to speak unkindly to those who were tasked with these follow-up calls, but I got the feeling they were primarily interested in cancelling the in-person tech appointment, which we ultimately agreed to do.  Assuming the issue actually has been corrected by someone/something, then they obviously were calling for the right reason.

In both cases I asked for an explanation of what had been done, and in neither did I get much of an answer; this morning's call the support person simply said that some "signal" had been sent and that now everything looked good...    I did attempt to explain that initial investigation by Justin indicated that my issue was apparent not just for me specifically but also in neighboring homes as well, which to me spoke to wider issue. Nevertheless, I couldn't seem to get any further information, though perhaps the person I was speaking with simply didn't have details on precisely what was done. I'm mentioning all of this solely for the future person who searches for resolution to a similar problem, and I'm sorry you won't find much here beyond "be persistent with your need for help and hope support is able to find 'something' to correct".

Nevertheless, things have been stable for at least the last 24hrs, so that's a step in the right direction. Thanks again to Justin for initiating, investigating, and escalating.

(edited)

Official Employee

 • 

1.6K Messages

@user_71gucl Thank you so much for getting back to us here and providing the details of your interactions with our team! We will continue to follow up here and check on the connection since, as you mentioned has previously been intermittent. If you have any new observations or changes please let us know and we will get back to you as soon as possible. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

17 Messages

1 year ago

Well, the joke's on me (again).

Beginning again this morning are more T3 timeouts, Dynamic Range Window violations, Unicast Maintenance Ranging, etc.

Can't believe I let myself be talked into cancelling the on-site tech appointment, which would have conveniently been this morning.
Hopefully I can have one rescheduled relatively quickly.
More to come...

Contributor

 • 

17 Messages

1 year ago

On-site tech was here today.

He found a loose connection at the pole near my house, and replaced it; he explained this can happen naturally over time depending on climate, weather conditions, etc.

He additionally noticed the connection to the box on the outside of my house (the coax from the pole to the house) was slightly degraded as well, and went ahead and replaced this connection; similarly to the above, this apparently can be a natural phenomenon over time and he didn't seem particularly surprised by it.

Unfortunately, within a half hour of him leaving, my modem is once again logging some t3 time out events and unicast maintenance ranging errors. I have not yet personally experienced the same loss-of-connectivity issues I've been having, but I assume the logging is not a good sign and it's only a matter of time...

Will keep monitoring and escalate again if today's visit hasn't found the true source of the errors.

Official Employee

 • 

4.1K Messages

@user_71gucl, thanks for getting back to us with this update. Although I am happy to hear that the tech was able to find and address some issues, I am very sorry to hear that you are now experiencing some timeouts and ranging errors. We would be more than happy to stick with you to ensure things get better on your end. 

 

I will respond/continue to work with you in our Direct Message. Thank you!

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

17 Messages

1 year ago

On-site tech #2 was here this afternoon (an hour early, bonus points for him!).
He was not aware another tech had already been to look into this issue, so I went through all of the history I could recall as well as what I understood had been done the day before.

He put some monitoring equipment on the inside line to the cable modem, and then again outside at the box on the side of my house, and saw nothing wrong with any of the signals/power/noise/etc.

He could think of no other reason I would be experiencing the issues I've been seeing, except for the possibility that the cable modem was overheating, so moved it to a location with better ventilation. I did explain that this was a new modem, that I had replaced it in the last week or two, and that even with the prior modem I had experienced the same set of problems/errors.

In any event, as things were "normal" while he was here, he was out of options.

In the hour or so after he left, I captured these from the modem's event logs:

Date Time Event Level Description
9/12/2023
14:30:28
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:28
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:28
5 Dynamic Range Window violation
9/12/2023
14:30:28
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:28
5 Dynamic Range Window violation
9/12/2023
14:30:28
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:28
5 Dynamic Range Window violation
9/12/2023
14:30:28
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:28
5 Dynamic Range Window violation
9/12/2023
14:30:30
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:31
5 RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:30:31
5 Dynamic Range Window violation
9/12/2023
14:44:11
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:45:15
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:45:18
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:47:23
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:49:48
6 CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:40
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:40
3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:40
3 16 consecutive T3 timeouts while trying to range on upstream channel 3;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:50
3 No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:56
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:53:59
3 No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
9/12/2023
14:54:08
3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

Connectivity has been normal for the hour following the last logged event above, and I expect it to be fine until whatever gremlin is causing the periodic issues wakes up and wreaks some more havoc.

I've since been in touch with support once again, and they've arranged for another on-site tech visit for this coming Tuesday morning, so I will once again follow-up here afterwards.

Contributor

 • 

17 Messages

1 year ago

I was off by one day, the follow-up on-site appointment was today (Monday).

Today's visit was the best by far, by a Comcast employee (as opposed to the consultants that are often used); he immediately acknowledged there were myriad signal problems in the area, and never even bothered coming in my house. He had also arranged ahead of time for a partner employee with a bucket truck to arrive with him! As at least an initial step, they reran a new coax line from the top of the pole near my house to the xfinity box on the side the house, and had me reattach a signal attenuator to the cable modem (the first on-site tech removed mine......and he kept it). Signal levels once again look good, and I will continue to monitor over the next few days.

The tech stated that while this should definitely help my recent issues, it will not necessarily completely solve them, as the signal issues in the area could still cause widespread/periodic problems; ultimately they made need to continue to do similar work as they did for me today at other residences/businesses in the area (that is, if I or enough other people keep escalating issues).


Will try to report back here in a few days with an update.

BIG thanks to today's techs, Wes and DJ.

Official Employee

 • 

1.3K Messages

Awesome, we are so happy to hear about the experience today @user_71gucl! We will be in touch in our DM's to ensure that everything remains stable. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Contributor

 • 

17 Messages

1 year ago

Things have been significantly better, almost perfect.
I've had a single error (a t3 time-out) since the techs were here on Monday, so an enormous improvement overall.

I'll obviously continue to monitor, and will re-escalate if/when things become problematic again, but for the time being things are "good".

Thanks again to all the support personnel (both online and in person) who have helped!

forum icon

New to the Community?

Start Here