tb1313's profile

Contributor

 • 

21 Messages

Sunday, September 17th, 2023 1:55 PM

Closed

Started Unicast Maintenance Ranging - No Response received - T3 time-out

My internet connection has been spotty lately.

Today I decided to check the results on ping plotter and check my cable modems logs.

Ping Plotter shows 11.4 % packet loss between me and comcasts first hop.

My cable modem's logs are full of these:
2023-09-17, 13:15:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;

All my connections are tight.  I don't see any corroded fittings.

Any suggestions?

Thanks

Expert

 • 

110.2K Messages

2 years ago

Please redact the CM MAC and the CMTS MAC addresses from your error log entry 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".


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


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

Contributor

 • 

21 Messages

Hi EG.  Redacted as requested.  My cable modem is a Netgear CM1000v2. 

Contributor

 • 

21 Messages

2 years ago

Here are my power levels: 

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 675000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 41 675000000 Hz -0.9 dBmV 40.1 dB 1578034581 12138 32274
2 Locked QAM256 13 507000000 Hz 0.7 dBmV 42.0 dB 1576924381 17236 36841
3 Locked QAM256 14 513000000 Hz 0.5 dBmV 42.1 dB 1511431461 15061 32960
4 Locked QAM256 15 519000000 Hz 0.2 dBmV 41.9 dB 1576915663 16890 37029
5 Locked QAM256 16 525000000 Hz 0.3 dBmV 42.0 dB 1576932496 16651 35598
6 Locked QAM256 17 531000000 Hz -0.1 dBmV 41.8 dB 1576941803 16477 36590
7 Locked QAM256 18 537000000 Hz -0.3 dBmV 41.7 dB 1576941831 16922 37891
8 Locked QAM256 19 543000000 Hz -0.2 dBmV 41.6 dB 1576948911 16178 37649
9 Locked QAM256 20 549000000 Hz -0.3 dBmV 41.7 dB 1576963403 16675 39315
10 Locked QAM256 21 555000000 Hz -0.5 dBmV 41.6 dB 1576968602 16507 39263
11 Locked QAM256 22 561000000 Hz -0.5 dBmV 41.5 dB 1576977728 16678 40335
12 Locked QAM256 23 567000000 Hz -0.4 dBmV 41.0 dB 1576985698 16187 38277
13 Locked QAM256 24 573000000 Hz -0.5 dBmV 41.5 dB 1576988636 14968 35536
14 Locked QAM256 25 579000000 Hz -0.4 dBmV 41.5 dB 1576991148 15623 38338
15 Locked QAM256 26 585000000 Hz 0.1 dBmV 41.7 dB 1576994109 15287 40555
16 Locked QAM256 27 591000000 Hz 0.0 dBmV 41.6 dB 1577001247 15295 38108
17 Locked QAM256 28 597000000 Hz 0.3 dBmV 41.9 dB 1577066597 14906 36673
18 Locked QAM256 29 603000000 Hz 0.6 dBmV 41.9 dB 1577073002 13912 33319
19 Locked QAM256 30 609000000 Hz 0.5 dBmV 41.7 dB 1577081329 13304 32802
20 Locked QAM256 31 615000000 Hz 0.7 dBmV 41.3 dB 1577080309 13546 34556
21 Locked QAM256 32 621000000 Hz 0.9 dBmV 41.8 dB 1577085304 13507 34847
22 Locked QAM256 33 627000000 Hz 0.8 dBmV 41.8 dB 1577089827 13219 33949
23 Locked QAM256 34 633000000 Hz 0.3 dBmV 41.6 dB 1577097326 12900 31965
24 Locked QAM256 35 639000000 Hz 0.2 dBmV 41.5 dB 1577102007 12235 29038
25 Locked QAM256 36 645000000 Hz 0.0 dBmV 41.5 dB 1577102824 12708 32593
26 Locked QAM256 37 651000000 Hz 0.0 dBmV 41.3 dB 1577106902 12456 33238
27 Locked QAM256 38 657000000 Hz -0.7 dBmV 41.2 dB 1577114484 12449 32242
28 Locked QAM256 39 663000000 Hz -0.6 dBmV 41.2 dB 1577114856 12734 33960
29 Locked QAM256 40 669000000 Hz -0.7 dBmV 41.2 dB 1577121218 12488 33041
30 Locked QAM256 42 681000000 Hz -0.8 dBmV 41.0 dB 1577127837 11491 29962
31 Locked QAM256 43 687000000 Hz -0.5 dBmV 41.1 dB 1577141413 11553 31225
32 Locked QAM256 44 693000000 Hz -0.2 dBmV 41.3 dB 1577133992 11219 30268

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 2 16400000 Hz 41.8 dBmV
2 Locked ATDMA 3 22800000 Hz 40.8 dBmV
3 Locked ATDMA 4 29200000 Hz 41.3 dBmV
4 Locked ATDMA 5 35600000 Hz 42.3 dBmV
5 Locked ATDMA 6 40400000 Hz 41.8 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0, 1, 2, 3 159 702000000 Hz 1.0 dBmV 39.8 dB 1126 ~ 2969 11269255251 3676950118 1009
2 Not Locked 0 0 0 Hz -0.1 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV

Current System Time: Sun Sep 17 10:56:24 2023
System Up Time: 88:25:25

Expert

 • 

110.2K Messages

2 years ago

OK, please also post the balance of those error log entries in their entirety (copy and paste them, don't post a screenshot) but redact the CM MAC and the CMTS MAC addresses. 

Contributor

 • 

21 Messages

Thanks EG!  Here are the log entries:

Time Priority Description
2023-09-17, 15:40:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:36:09 Warning (5) Dynamic Range Window violation
2023-09-17, 15:36:09 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:35:29 Warning (5) Dynamic Range Window violation
2023-09-17, 15:35:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:35:29 Warning (5) Dynamic Range Window violation
2023-09-17, 15:35:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:35:29 Warning (5) Dynamic Range Window violation
2023-09-17, 15:35:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:35:29 Warning (5) Dynamic Range Window violation
2023-09-17, 15:35:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 15:04:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 14:19:16 Warning (5) Dynamic Range Window violation
2023-09-17, 14:19:16 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 14:18:56 Warning (5) Dynamic Range Window violation
2023-09-17, 14:18:56 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 14:18:56 Warning (5) Dynamic Range Window violation
2023-09-17, 14:18:56 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 14:18:35 Warning (5) Dynamic Range Window violation
2023-09-17, 14:18:35 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 14:18:35 Warning (5) Dynamic Range Window violation
2023-09-17, 14:18:35 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:15:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:07:11 Warning (5) Dynamic Range Window violation
2023-09-17, 13:07:11 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:06:50 Warning (5) Dynamic Range Window violation
2023-09-17, 13:06:50 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:06:50 Warning (5) Dynamic Range Window violation
2023-09-17, 13:06:50 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:05:50 Warning (5) Dynamic Range Window violation
2023-09-17, 13:05:50 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 13:05:50 Warning (5) Dynamic Range Window violation
2023-09-17, 13:05:50 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 10:00:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 09:27:50 Warning (5) Dynamic Range Window violation
2023-09-17, 09:27:50 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 09:27:29 Warning (5) Dynamic Range Window violation
2023-09-17, 09:27:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
2023-09-17, 09:27:29 Warning (5) Dynamic Range Window violation
2023-09-17, 09:27:29 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;

Official Employee

 • 

1.6K Messages

@EG Thank you so much for looking into these and your recommendations! 

 

@tbrown1313 We appreciate you sharing these results and visiting our forums. We can pull these records and then bring back here our results and resolution for our community who experiences similar issues. 

 

Please send us a direct message with your full name and service address. 

 

  • Make sure you are signed in here in the Xfinity Forum. Click "Sign In" if necessary
  • Click the "Direct Message" icon (square chat icon in the upper right corner of your screen next to the bell icon)
  • Click the "New message" (pencil and paper) icon
  • Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "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
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

Expert

 • 

110.2K Messages

2 years ago

OK so even though the signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. And there are a fair number of uncorrectable bit errors, but that may not be significant depending on the total uptime of the modem since the last reboot. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.


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 (The Digital Care Team) who 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 check those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

Contributor

 • 

21 Messages

Thanks a ton for your time and expertise EG!

Expert

 • 

110.2K Messages

2 years ago

You're very welcome !

6 Messages

2 years ago

I am experiencing a similar problem.  I will lose internet connectivity and also loss of connectivity to my Netgear NightHawk CM2000 Modem via 192.168.100.1.  When I check the modem lights (inconveniently located in my basement), the Upstream and Downstream Links are usually UP, but the unit has lost network connectivity.

This happened last night and then again during this afternoon's football games.

Below are my modem details:

The Netgear NightHawk CM2000 Modem is running Cable Firmware Version V8.01.02 on a <60Ft RG6 Home Run.  No Splitters.

Log

Sun Sep 17 15:40:56 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 12:58:51 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 12:51:10 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 12:34:59 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 12:25:53 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:41:47 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:35:55 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:29:57 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:29:06 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:35 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:33 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:30 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:29 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:25 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:24:24 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:46 2023 (Notice (6))  DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:45 2023 (Notice (6))  TLV-11 - unrecognized OID;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:34 2023 (Notice (6))  Honoring MDD; IP provisioning mode = IPv6
Sun Sep 17 11:23:32 2023 (Critical (3))  No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:22 2023 (Warning (5))  ToD request sent - No Response received;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:22 2023 (Critical (3))  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:21 2023 (Critical (3))  No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:18 2023 (Critical (3))  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:18 2023 (Critical (3))  No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:13 2023 (Critical (3))  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:11 2023 (Critical (3))  No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:23:09 2023 (Critical (3))  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 11:22:22 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 09:15:35 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 09:13:25 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 09:13:24 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 09:12:03 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 09:11:55 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:18:05 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:22 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:19 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:17 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:16 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:12 2023 (Notice (6))  CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 17 07:11:11 2023 (Critical (3))  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CM-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

Cable Connection
Cable Diagnostic
Status:   Good
CM Status: GREEN
Downstream Status: GREEN
Upstream Status: GREEN
 
Startup Procedure
Procedure  Status  Comment
Acquire Downstream Channel  573000000 Hz  Locked
Connectivity State  OK  Operational
Boot State  OK  Operational
Security  Enabled  BPI+
IP Provisioning Mode  Honor MDD  IPv6 only

Downstream Bonded Channels
Channel  Lock Status  Modulation  Channel ID  Frequency  Power  SNR  Correctables  Uncorrectables
1 Locked QAM256 28 573000000 Hz 1.5 dBmV 43.1 dB 1511630 770199
2 Locked QAM256 1 399000000 Hz 1.6 dBmV 42.7 dB 1625218 1068938
3 Locked QAM256 2 405000000 Hz 1.6 dBmV 42.7 dB 1600546 1091710
4 Locked QAM256 3 411000000 Hz 1.8 dBmV 42.9 dB 1605595 1101504
5 Locked QAM256 4 417000000 Hz 1.8 dBmV 42.9 dB 1685083 1157854
6 Locked QAM256 5 423000000 Hz 1.6 dBmV 42.8 dB 1753268 1178191
7 Locked QAM256 6 429000000 Hz 1.5 dBmV 42.9 dB 1612812 1121154
8 Locked QAM256 7 435000000 Hz 1.6 dBmV 42.9 dB 1660660 1078943
9 Locked QAM256 8 441000000 Hz 1.6 dBmV 43.0 dB 1612212 1033747
10 Locked QAM256 9 453000000 Hz 1.7 dBmV 43.1 dB 1538546 964425
11 Locked QAM256 10 459000000 Hz 1.9 dBmV 43.2 dB 1601067 952785
12 Locked QAM256 11 465000000 Hz 1.9 dBmV 43.1 dB 1560054 954891
13 Locked QAM256 12 471000000 Hz 1.9 dBmV 43.1 dB 1481221 874387
14 Locked QAM256 13 477000000 Hz 1.9 dBmV 43.1 dB 1460535 821245
15 Locked QAM256 14 483000000 Hz 1.9 dBmV 43.2 dB 1474059 804870
16 Locked QAM256 15 489000000 Hz 1.9 dBmV 43.1 dB 1694047 894591
17 Locked QAM256 16 495000000 Hz 1.7 dBmV 43.0 dB 1404503 942505
18 Locked QAM256 17 507000000 Hz 1.6 dBmV 43.1 dB 1511742 744053
19 Locked QAM256 18 513000000 Hz 1.3 dBmV 43.1 dB 1430394 772453
20 Locked QAM256 19 519000000 Hz 1.3 dBmV 43.1 dB 1384636 690704
21 Locked QAM256 20 525000000 Hz 1.4 dBmV 43.1 dB 1494968 752961
22 Locked QAM256 21 531000000 Hz 1.1 dBmV 43.0 dB 1445211 821778
23 Locked QAM256 22 537000000 Hz 1.1 dBmV 43.0 dB 1500190 762739
24 Locked QAM256 23 543000000 Hz 1.2 dBmV 43.0 dB 1357374 749529
25 Locked QAM256 24 549000000 Hz 1.3 dBmV 43.1 dB 1437782 726700
26 Locked QAM256 25 555000000 Hz 1.2 dBmV 43.0 dB 1382580 724547
27 Locked QAM256 26 561000000 Hz 1.4 dBmV 43.1 dB 1301408 642516
28 Locked QAM256 27 567000000 Hz 1.5 dBmV 43.1 dB 1338342 640028
29 Locked QAM256 29 579000000 Hz 1.5 dBmV 43.1 dB 1348732 616784
30 Locked QAM256 30 585000000 Hz 1.5 dBmV 43.1 dB 1227355 520609
31 Locked QAM256 31 591000000 Hz 1.6 dBmV 43.1 dB 1231346 559974
32 Locked QAM256 32 597000000 Hz 1.7 dBmV 43.2 dB 1213161 514284

Upstream Bonded Channels
Channel  Lock Status  US Channel Type  Channel ID  Symbol Rate  Frequency  Power
1 Locked ATDMA 1 5120 Ksym/sec 35600000 Hz 47.0 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 47.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 46.8 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16400000 Hz 46.5 dBmV
5 Locked ATDMA 5 1280 Ksym/sec 39600000 Hz 41.8 dBmV
6 Not Locked Unknown 0 0 0 0.0 dBmV
7 Not Locked Unknown 0 0 0 0.0 dBmV
8 Not Locked Unknown 0 0 0 0.0 dBmV

Downstream OFDM Channels 
Channel  Lock Status  Modulation / Profile ID  Channel ID  Frequency  Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

Current System Time: Sun Sep 17 15:44:17 2023
System Up Time: 19 days 00:39:26

Any suggestions would be appreciated.

Contributor

 • 

21 Messages

2 years ago

getting worse tonight

Contributor

 • 

21 Messages

2 years ago

Tech coming tomorrow.  thanks again to EG and the Digital Care Team.  Hopeful this gets sorted out.

Contributor

 • 

21 Messages

I got a call this morning saying a fix was made to my configuration.  I have verified that I'm no longer experience packet loss or the T3 timeouts.   I've gone ahead and cancelled the appointment.   Thank you again for getting this sorted out for me.  I appreciate it!

Official Employee

 • 

1.6K Messages

Thank you for the update! Glad to hear things are looking better! I have confirmed the signals are within spec. at this time. We will continue to follow up for a few days to keep an eye on everything and go from there. If there are any changes please let us know. 

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
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

 • 

21 Messages

2 years ago

Things were better until tonight.   Now my connection is awful again.

Contributor

 • 

21 Messages

2 years ago

Same errors in the modem log

Started Unicast Maintenance Ranging - No Response received - T3 time-out

Expert

 • 

110.2K Messages

2 years ago

@tb1313 

Your post with that pic of the speed test was marked as being "Private" by the forum software because it contains your public IP address. That is considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. Please blot out the address or delete the pic altogether. The forum bot will not allow your post to be seen publically.

(edited)

Contributor

 • 

21 Messages

2 years ago

update... Tech Chris came a little after 12 today. He removed an unused splitter and added some filters to get power levels in line with specs. Connection has been great since he left. Will keep you posted if I see otherwise.

Official Employee

 • 

1.1K Messages

Perfect! please reach out if anything does come up. We are here for you and ready to help. Have a great night! 

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
forum icon

New to the Community?

Start Here