U

Visitor

 • 

3 Messages

Wed, Jun 1, 2022 3:45 PM

Repeated Dynamic Range Window Violations and T3 timeouts

The past few weeks I've had inconsistent internet disconnections. When I log into my modem and check the event logs there are repeated events of "Dynamic Range Window Violations" and "Started Unicast Maintenance Ranging - No Response received - T3 time-out". I've called Xfinity, chatted with Xfinity, and they even sent a tech out, all to no avail. I've tried 2 Netgear modems and yesterday the tech told me that Netgear can cause issues and that an ARRIS or Motorola modem "would fix the issue". Paid $170+ for a new ARRIS modem and today I'm back to the same issues. Of course because the tech was here for 10 minutes while the internet was working he blamed it on the Netgear router. I showed him the event log and he acted like it was in a foreign language and just showed me his screen that showed everything was good and that the signal was strong. 

At this point I'm weeks in and $250 lighter with no resolution in sight and I'm THIS close to switching to Verizon as I work from home and the internet seems to always drop when I'm in a Teams or Webex call. I wish someone that I talked to would actually try to see what was happening when I had the issue. 

EG

Expert

 • 

95.7K Messages

4 m ago

What do the modem's signal stats look like ? Try getting them here; http://192.168.100.1 

Please copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.


What is the exact make and model number of the Arris modem ?

Please post those error log entries as well in their entirety (copy and paste them, don't post a screenshot), but redact the CM MAC and the CMTS MAC addresses for your privacy. They are considered to be personal information. Posting personally identifying information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically.

(edited)

Visitor

 • 

3 Messages

@EG​ 

It's an Arris SB8200 

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
34 Locked QAM256 615000000 Hz -2.0 dBmV 42.9 dB 806 1244
10 Locked QAM256 471000000 Hz -1.8 dBmV 43.5 dB 1729 1494
11 Locked QAM256 477000000 Hz -1.9 dBmV 43.5 dB 1718 1482
12 Locked QAM256 483000000 Hz -2.1 dBmV 43.3 dB 1466 1561
13 Locked QAM256 489000000 Hz -2.2 dBmV 43.3 dB 1329 1561
14 Locked QAM256 495000000 Hz -2.1 dBmV 43.1 dB 1643 1490
15 Locked QAM256 507000000 Hz -1.9 dBmV 43.2 dB 1238 1314
16 Locked QAM256 513000000 Hz -1.8 dBmV 43.5 dB 1224 1279
17 Locked QAM256 519000000 Hz -1.8 dBmV 43.2 dB 1107 1423
18 Locked QAM256 525000000 Hz -1.6 dBmV 43.5 dB 904 1522
19 Locked QAM256 531000000 Hz -1.8 dBmV 43.3 dB 1141 1501
20 Locked QAM256 537000000 Hz -1.9 dBmV 43.2 dB 1085 1376
21 Locked QAM256 543000000 Hz -1.6 dBmV 43.3 dB 839 1289
22 Locked QAM256 549000000 Hz -1.2 dBmV 43.5 dB 800 1305
23 Locked QAM256 555000000 Hz -1.6 dBmV 43.2 dB 745 1348
24 Locked QAM256 561000000 Hz -1.8 dBmV 43.2 dB 907 1253
25 Locked QAM256 567000000 Hz -1.6 dBmV 43.3 dB 864 1293
26 Locked QAM256 573000000 Hz -2.1 dBmV 43.0 dB 725 1285
27 Locked QAM256 579000000 Hz -2.1 dBmV 42.8 dB 1715 1409
28 Locked QAM256 585000000 Hz -2.0 dBmV 42.9 dB 725 1192
29 Locked Other 690000000 Hz -2.9 dBmV 40.2 dB 759809399 2023
30 Not Locked QAM256 0 Hz 0.0 dBmV 43.0 dB 717 1239
31 Locked QAM256 591000000 Hz -1.9 dBmV 42.8 dB 833 1196
32 Locked QAM256 597000000 Hz -2.0 dBmV 42.9 dB 848 1212
33 Locked QAM256 603000000 Hz -1.9 dBmV 42.9 dB 701 1232
35 Locked QAM256 609000000 Hz -1.9 dBmV 42.8 dB 668 1247
36 Locked QAM256 621000000 Hz -2.1 dBmV 42.7 dB 628 1242
37 Locked QAM256 627000000 Hz -2.0 dBmV 42.7 dB 669 1266
38 Locked QAM256 633000000 Hz -2.3 dBmV 42.5 dB 597 1298
39 Locked QAM256 639000000 Hz -2.4 dBmV 42.7 dB 593 1254
40 Locked QAM256 645000000 Hz -2.2 dBmV 42.5 dB 579 1264
41 Locked QAM256 651000000 Hz -2.6 dBmV 42.3 dB 629 1207

Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 10 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 38.0 dBmV
2 11 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 38.0 dBmV
3 12 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 38.0 dBmV
4 17 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 39.0 dBmV
5 18 Locked SC-QAM Upstream 40400000 Hz 3200000 Hz 39.0 dBmV

06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 11:28 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"

(edited)

EG

Expert

 • 

95.7K Messages

4 m ago

The signal stats were in spec at that snapshot in time. Is that all of the error log entries ? If not, please post the remainder.

Visitor

 • 

3 Messages

@EG​ 

My apologies, here's the event log in full. 

06/01/2022 12:22 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 12:22 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 12:21 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 12:21 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 12:18 2436694061 5 "Dynamic Range Window violation"
06/01/2022 12:18 82001200 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;"
06/01/2022 11:28 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:27 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:27 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;=CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:27 74010100 6 "CM-STATUS message sent. Event Type Code: 8; Chan ID: 10 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;=CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 11:26 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 74010100 6 "CM-STATUS message sent. Event Type Code: 8; Chan ID: 10 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 2436694061 5 "Dynamic Range Window violation"
06/01/2022 10:49 82001200 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;"
06/01/2022 10:49 2436694061 5 "Dynamic Range Window violation"
06/01/2022 10:49 82001200 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;"
06/01/2022 10:49 2436694061 5 "Dynamic Range Window violation"
06/01/2022 10:49 82001200 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;"
06/01/2022 10:49 2436694061 5 "Dynamic Range Window violation"
06/01/2022 10:49 82001200 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;"
06/01/2022 10:49 2436694061 5 "Dynamic Range Window violation"
06/01/2022 10:49 82001200 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;"
06/01/2022 10:49 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:49 82000200 3 "No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 82000200 3 "No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:48 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;"
06/01/2022 10:32 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;"
XfinityGabby

Official Employee

 • 

590 Messages

Hello @user_td9h43 [Edited username], we appreciate your time to reach out to our team through Forums. We certainly understand how frustrating it can be to experience issues with the service. We can definitely look into the status of the modem, to begin please send a Direct Message with your full name and address. 

 

Here are the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the "Peer to peer chat" icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message

(edited)

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
EG

Expert

 • 

95.7K Messages

4 m ago

O/k so even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.


There are other signal stat figures 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 !

Visitor

 • 

3 Messages

@EG​ We've been having a very similar issue for the past several months.  Please help!  Below is our current connection info and logs for the past couple days.  Thank you!

Connection
   Startup Sequence    
   Startup Step Status Comment

  
   Acquire Downstream Channel 693000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 31 days 22h:06m:17s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 41 693.0 1.4 40.3 14622 4625
   2 Locked QAM256 13 525.0 1.7 41.2 36515 106581
   3 Locked QAM256 14 531.0 1.9 41.0 30604 109770
   4 Locked QAM256 15 537.0 1.8 41.1 27735 102211
   5 Locked QAM256 16 543.0 1.8 41.2 11690 35286
   6 Locked QAM256 17 549.0 1.6 41.0 14690 11404
   7 Locked QAM256 18 555.0 0.2 40.4 15630 16718
   8 Locked QAM256 19 561.0 0.0 40.4 14452 17118
   9 Locked QAM256 20 567.0 0.3 40.4 15102 26990
   10 Locked QAM256 21 573.0 0.2 40.5 28108 43167
   11 Locked QAM256 22 579.0 0.3 40.4 19842 38965
   12 Locked QAM256 23 585.0 1.2 40.7 36904 117913
   13 Locked QAM256 24 591.0 2.1 40.8 35841 114685
   14 Locked QAM256 25 597.0 2.8 40.8 28092 108688
   15 Locked QAM256 26 603.0 2.4 40.6 27213 107831
   16 Locked QAM256 27 609.0 2.2 40.5 14225 52385
   17 Locked QAM256 28 615.0 2.2 40.6 13129 6979
   18 Locked QAM256 29 621.0 1.5 39.9 16655 3948
   19 Locked QAM256 30 627.0 1.4 40.3 16063 7282
   20 Locked QAM256 31 633.0 1.2 40.1 13102 17273
   21 Locked QAM256 32 639.0 0.1 39.8 18138 28824
   22 Locked QAM256 33 645.0 -0.6 39.6 13705 26369
   23 Locked QAM256 34 651.0 0.2 39.8 29401 93285
   24 Locked QAM256 35 657.0 1.4 40.2 31952 102286
   25 Locked QAM256 36 663.0 2.4 40.4 22105 81184
   26 Locked QAM256 37 669.0 2.6 40.3 25133 101943
   27 Locked QAM256 38 675.0 2.7 40.1 15246 60422
   28 Locked QAM256 39 681.0 2.4 40.4 9687 11995
   29 Locked QAM256 40 687.0 1.9 40.4 14168 1578
   30 Locked QAM256 42 699.0 1.6 40.4 14623 10216
   31 Locked QAM256 43 705.0 0.9 40.2 13257 22754
   32 Locked QAM256 44 711.0 0.5 40.0 10942 23205
   33 Locked OFDM PLC 159 768.0 0.5 40.3 23409263 241426


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 9 5120 35.6 48.0
   2 Locked SC-QAM 10 5120 29.2 47.5
   3 Locked SC-QAM 11 5120 22.8 46.0
   4 Locked SC-QAM 12 5120 16.4 44.5
   5 Locked SC-QAM 13 1280 39.6 48.0

Event Log
   Event Log  
  
    Time    Priority    Description 
    23:17:35
Mon Sep 5 2022
  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.1;
    10:30:29
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:30:29
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    10:30:29
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:30:29
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    10:30:29
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:30:29
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    10:32:05
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:32:12
Tue Sep 6 2022
  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.1;
    10:32:52
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:23:24
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:23:24
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:26:37
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:26:50
Tue Sep 6 2022
  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.1;
    11:26:50
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:26:50
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:27:03
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:29:03
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:29:03
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:31:03
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:31:03
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:31:03
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:31:03
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:31:05
Tue Sep 6 2022
  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.1;
    11:40:22
Tue Sep 6 2022
  Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:40:22
Tue Sep 6 2022
  Warning (5)   Dynamic Range Window violation
    11:42:53
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:43:43
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:59:02
Tue Sep 6 2022
  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.1;
    11:59:04
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:59:31
Tue Sep 6 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    12:07:26
Tue Sep 6 2022
  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.1;
 

 

(edited)

Official Employee

 • 

308 Messages

Hello @deloyj, and thank you for reaching out about your issue. As our expert mentioned, we are able to see most of the signal status to your modem, and also see other items like T3 timeouts. I would be happy to have a look into the issue you are having, and work towards getting it resolved for you! 

Can you send us a private message with your full name, name of account holder (if different), and service address?

To send a private message, please click the chat icon next to the bell in the upper right corner. Click the “notepad and pen” button. Send the full message to our shared support handle “Xfinity Support”. We look forward to hearing from 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

Visitor

 • 

3 Messages

Message sent.  Thank you!

Official Employee

 • 

108 Messages

You're welcome.

 

To send a direct message [private message]:

   Click "Sign In" if necessary
   Click the "Direct Message" icon or https://comca.st/3xkWyGG
   Click the "New message" (pencil and paper) icon
   The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there.
   - As you are typing a drop-down list appears. Select "Xfinity Support" from that list.
   - An "Xfinity Support" graphic replaces the "To:" line.
   Type your message in the text area near the bottom of the window
   Press Enter to send it

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

Visitor

 • 

3 Messages

Message sent but never received a response.   Help!

forum icon

New to the Community?

Start Here