Skip to main content

    Support

    Offers

U
user_53yxh3
1st Topic
1st Like
1st Reply

6 Messages

Saturday, January 13th, 2024 2:41 AM

Closed

Intermittent connection drops, 100% packet loss, Maybe bad power levels at play?

The issue

The internet keeps cutting out entirely making it impossible to work, stream, and game. I've been observing the issue this entire week and have noticed on a single day alone Monday, Jan 8, 2023 that the internet was completely out more than 22 times in a 27 hour time period. Outages happen during working hours PT and at night PT with no noticeable pattern. See below for examples of times when my firewall was detecting 100% packet loss within the last week.

Screenshot 2024-01-12 at 7.15.55 AM.png

Screenshot 2024-01-12 at 3.21.49 PM.png

Screenshot 2024-01-10 at 2.09.07 AM.png

Screenshot 2024-01-09 at 12.09.49 AM.png

The Ask

I'm assuming the issue is partly due to the power levels on my ingress coax being out of spec for my modem (despite my modem being supported by xfinity https://www.xfinity.com/support/devices/) but perhaps there are other issues at play as well.

And yes, I have tested removing each component in the system. When the connection works, it works great so it cannot be my hardware.

Can I get some help figuring out what is happening with my internet?

My network setup

MoCA Filter installed at point of entry:

GLP-1G70CW MoCA Filter - 70dB MoCA PoE filter, 5 - 1002MHz, low pass -70 filter, 6kV “combo wave” surge
https://www.ppc-online.com/product-search/filter-snlp-1g70cw 

Modem:
Netgear Nighthawk CM2000 - DOCSIS 3.1 Cable Modem, 2.5Gbps

https://www.netgear.com/home/wifi/modems/cm2000/

Firewall Appliance: 
Protectli Vault - 4x 2.5Gbps ports, Intel(R) Celeron(R) J6412 @2.00GHz (4 cores, 4 threads)

https://www.amazon.com/Protectli-Vault-VP2420-4-Firewall-Appliance/dp/B0BQ1SNXLD

Firewall: 
OPNsense 23.7.11-amd64

https://opnsense.org/


WiFi Access Point:
TP-Link AX3000 (Archer AX55 Pro) - WiFi 6 Router, 2.5Gbps

https://www.tp-link.com/us/home-networking/wifi-router/archer-ax3000/

Ethernet Cables:
GearIT Cat6 Patch Cable 6ft

Upstream and downstream power levels are bad

According to Netgear on their knowledge base (https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router), I need downstream power levels between [-7 dBmV, +7 dBmV] and upstream power levels between [38 dBmV, 48 dBmV].

Good Downstream power levels are within -7 to +7 dBmV. Good Upstream power levels are within 38-48 dBmV.

But as you can see below, my downstream power levels are not within the desired [-7 dBmV, +7 dBmV] range. The downstream power levels I'm seeing are much higher - in the 8-9 dBmV range. Similarly, my upstream power levels are not within the desired [38 dBmV, 48 dBmV] range. The upstream power levels I'm seeing are much lower - in the 34-37 dBmV range.

Downstream Bonded Channels

Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 507000000 Hz 9 41.9 7159 5738
2 Locked QAM256 4 405000000 Hz 8.4 41.8 12448 6605
3 Locked QAM256 5 411000000 Hz 8.2 41.8 10545 5704
4 Locked QAM256 6 417000000 Hz 8.3 41.9 12232 6736
5 Locked QAM256 7 423000000 Hz 8.3 41.9 8698 5485
6 Locked QAM256 8 429000000 Hz 8.6 42 7772 5516
7 Locked QAM256 9 435000000 Hz 8.1 41.9 8064 4468
8 Locked QAM256 10 441000000 Hz 8.4 42 8607 5412
9 Locked QAM256 11 447000000 Hz 8.5 41.9 8621 5400
10 Locked QAM256 12 453000000 Hz 8.8 41.9 6944 5670
11 Locked QAM256 13 459000000 Hz 8.8 41.9 6688 4384
12 Locked QAM256 14 465000000 Hz 8.9 41.8 6799 4550
13 Locked QAM256 15 471000000 Hz 9 41.9 7870 4069
14 Locked QAM256 16 477000000 Hz 9.1 41.9 9053 4636
15 Locked QAM256 17 483000000 Hz 9.2 42 6790 4848
16 Locked QAM256 18 489000000 Hz 9.2 41.9 5420 4459
17 Locked QAM256 19 495000000 Hz 9 41.8 5725 3776
18 Locked QAM256 21 513000000 Hz 9.2 42 5611 4122
19 Locked QAM256 22 519000000 Hz 9.2 42 5633 4271
20 Locked QAM256 23 525000000 Hz 9 41.9 4587 3497
21 Locked QAM256 24 531000000 Hz 9 41.9 4133 3389
22 Locked QAM256 25 543000000 Hz 9 41.9 4783 3844
23 Locked QAM256 26 549000000 Hz 8.8 41.8 4387 3454
24 Locked QAM256 27 555000000 Hz 9 41.9 4198 3817
25 Locked QAM256 28 561000000 Hz 8.5 41.6 4158 2691
26 Locked QAM256 29 567000000 Hz 8.9 41.8 4115 3215
27 Locked QAM256 30 573000000 Hz 8.8 41.8 3665 2751
28 Locked QAM256 31 579000000 Hz 8.9 41.8 3994 3755
29 Locked QAM256 32 585000000 Hz 8.9 41.8 3687 2837
30 Locked QAM256 33 591000000 Hz 9 41.8 3393 2972
31 Locked QAM256 34 597000000 Hz 8.6 41.7 3086 2328
32 Not Locked Unknown 0 0 Hz 0 0 0 0

Upstream Bonded Channels

Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 37.3 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 34.8 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 36.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 38.5 dBmV
5 Not Locked Unknown 0 0 0 0
6 Not Locked Unknown 0 0 0 0
7 Not Locked Unknown 0 0 0 0
8 Not Locked Unknown 0 0 0 0

Event logs from my modem

Note that my modem has logs where it tried to connect 16 times to the upstream CMTS and was unable to do so. This most recent outage happened today at 3:20pm PT which correlates with the timing of my firewall detecting 100% packet loss.

Time Priority Description
Fri Jan 12 15:25:36 2024 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;
Fri Jan 12 15:25:35 2024 Notice (6)
TLV-11 - unrecognized OID;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:25:27 2024 Notice (6)
Honoring MDD; IP provisioning mode = IPv6
Fri Jan 12 15:25:20 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:25:06 2024 Warning (5)
ToD request sent - No Response received;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:25:06 2024 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;
Fri Jan 12 15:25:05 2024 Critical (3)
No Ranging Response received - T3 time-out;CM--QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:25:05 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:24:55 2024 Critical (3)
No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:22:55 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:22:36 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:22:24 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:22:10 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:54 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:51 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:24 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:20 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:06 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:02 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:21:02 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:58 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:57 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:53 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:53 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:53 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:52 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:49 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:49 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:46 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:45 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 0;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:45 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:45 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:42 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:29 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 1;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:29 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:20:29 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:07:24 2024 Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:07:23 2024 Notice (6)
TLV-11 - unrecognized OID;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 12 15:07:13 2024 Notice (6)
Honoring MDD; IP provisioning mode = IPv6
Fri Jan 12 15:07:08 2024 Critical (3)
No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;


[Edited: Removed MAC Addresses]

Question

 • 

Updated 

1 year ago

 • Edited

310

3

XfinityVianney

Official Employee

 • 

2.2K Messages

1 year ago

Hi, @user_53yxh3. Thank you for reaching out. I hope you are doing well. I see you have a bit going on, and I would like to review this further on our end. With these many timeouts and hiccups, I would like to review the local plant/node as well. I ask that you reach out privately, so we can cover the details of your account. You can start by clicking the chat icon located in the top right corner of your forums page when signed in. Once there, you can direct your messages to "Xfinity Support." Please add your full name and service address to help us locate your account. Let me know if you have any questions.

4

0

user_53yxh3

6 Messages

@XfinityVianney​ Thank you. I have direct messaged "Xfinity Support" as requested.

1 year ago

0

user_53yxh3

6 Messages

My issue persists.

I ran traceroute (https://linux.die.net/man/8/traceroute) to find where the issue could be. Note that there are timeout over 5 seconds between hop 7 and hop 8.

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  router.localdomain                    9.101 ms  6.880 ms  6.661 ms
 2  96.120.---.--- (96.120.---.---)      12.868 ms  13.025 ms  13.214 ms
 3  68.87.---.--- (68.87.---.---)        11.277 ms  24.673 ms  11.279 ms
 4  162.151.---.--- (162.151.---.---)    13.109 ms  14.575 ms  26.928 ms
 5  162.151.---.--- (162.151.---.---)    16.953 ms  18.650 ms  15.611 ms
 6  68.86.---.--- (68.86.---.---)        16.378 ms
    68.86.---.--- (68.86.---.---)        22.515 ms
    68.86.---.--- (68.86.---.---)        16.224 ms
 7  96.110.---.--- (96.110.---.---)      17.082 ms
    96.110.---.--- (96.110.---.---)      14.942 ms
    96.110.---.--- (96.110.---.---)      15.364 ms
 8  * * 50.242.151.238 (50.242.151.238)  25.825 ms
 9  172.68.188.22 (172.68.188.22)        15.498 ms
    162.158.164.4 (162.158.164.4)        16.495 ms
    172.71.152.2 (172.71.152.2)          22.267 ms
10  1.1.1.1 (1.1.1.1)                    23.801 ms  16.608 ms  16.545 ms


traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  router.localdomain                    9.325 ms   7.725 ms   5.688 ms
 2  96.120.---.--- (96.120.---.---)      13.014 ms  12.561 ms  14.194 ms
 3  68.87.---.--- (68.87.---.---)        14.054 ms  12.787 ms  12.662 ms
 4  162.151.---.--- (162.151.---.---)    22.311 ms  15.264 ms  14.240 ms
 5  162.151.---.--- (162.151.---.---)    14.866 ms  16.572 ms  14.324 ms
 6  68.86.---.--- (68.86.---.---)        15.430 ms
    68.86.---.--- (68.86.---.---)        20.271 ms  17.591 ms
 7  96.110.---.--- (96.110.---.---)      16.902 ms
    96.110.---.--- (96.110.---.---)      15.928 ms
    96.110.---.--- (96.110.---.---)      15.387 ms
 8  * * 66.208.229.106 (66.208.229.106)  46.942 ms
 9  172.69.132.2 (172.69.132.2)          15.511 ms
    162.158.164.4 (162.158.164.4)        20.343 ms
    172.71.152.2 (172.71.152.2)          16.087 ms
10  1.1.1.1 (1.1.1.1)                    15.844 ms  16.829 ms  16.492 ms

See the logs from my modem below.

Time Priority Description
Tue Jan 16 18:54:35 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 2 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:54:21 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:54:05 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 2 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:58 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:37 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:37 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:37 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:37 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:36 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:35 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:34 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:25 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:24 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:24 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:23 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:16 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:13 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:12 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:09 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:09 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 18:53:09 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 09:48:02 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 09:47:36 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 09:45:31 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 09:45:18 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 09:44:11 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:46 2024 Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:45 2024 Notice (6)
TLV-11 - unrecognized OID;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:31 2024 Notice (6)
Honoring MDD; IP provisioning mode = IPv6
Tue Jan 16 05:45:22 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:12 2024 Warning (5)
ToD request sent - No Response received;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:12 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:45:02 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:44:54 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 6; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:44:54 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:44:53 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:44:18 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:43:16 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:42:58 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Tue Jan 16 05:42:46 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;

1 year ago

0

user_53yxh3

6 Messages

Downstream Bonded Channels

Note that the power levels are very high - too high for the modem spec.

Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 507000000 Hz 9.9 42.1 9382 7782
2 Locked QAM256 4 405000000 Hz 8.8 41.9 17601 8276
3 Locked QAM256 5 411000000 Hz 8.7 41.9 16287 7397
4 Locked QAM256 6 417000000 Hz 8.9 42 17055 8348
5 Locked QAM256 7 423000000 Hz 8.9 42 12056 6954
6 Locked QAM256 8 429000000 Hz 9.1 42.1 10835 6829
7 Locked QAM256 9 435000000 Hz 8.7 42 11199 5889
8 Locked QAM256 10 441000000 Hz 9 42.1 12704 6748
9 Locked QAM256 11 447000000 Hz 9.2 42 11476 6784
10 Locked QAM256 12 453000000 Hz 9.4 42.1 9118 6848
11 Locked QAM256 13 459000000 Hz 9.5 42 8523 5471
12 Locked QAM256 14 465000000 Hz 9.6 42 8524 5601
13 Locked QAM256 15 471000000 Hz 9.7 42.1 9851 5221
14 Locked QAM256 16 477000000 Hz 9.9 42.1 11285 5837
15 Locked QAM256 17 483000000 Hz 10 42.1 8981 6135
16 Locked QAM256 18 489000000 Hz 10 42 6918 5463
17 Locked QAM256 19 495000000 Hz 9.9 42 7370 4795
18 Locked QAM256 21 513000000 Hz 10.1 42.1 7002 5146
19 Locked QAM256 22 519000000 Hz 10.1 42.1 7180 5246
20 Locked QAM256 23 525000000 Hz 9.9 42 5884 4451
21 Locked QAM256 24 531000000 Hz 9.9 42 5248 4394
22 Locked QAM256 25 543000000 Hz 9.9 42 6096 4764
23 Locked QAM256 26 549000000 Hz 9.7 41.9 5527 4363
24 Locked QAM256 27 555000000 Hz 10 42 5326 4664
25 Locked QAM256 28 561000000 Hz 9.4 41.8 5348 3617
26 Locked QAM256 29 567000000 Hz 9.8 41.8 5477 4081
27 Locked QAM256 30 573000000 Hz 9.8 41.9 4831 3749
28 Locked QAM256 31 579000000 Hz 9.8 41.9 5068 4582
29 Locked QAM256 32 585000000 Hz 9.7 41.9 4729 3683
30 Locked QAM256 33 591000000 Hz 9.8 41.9 4351 3833
31 Locked QAM256 34 597000000 Hz 9.4 41.8 4183 3239
32 Not Locked Unknown 0 0 Hz 0 0 0 0

Upstream Bonded Channels

The power levels are still low.

Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 36.0 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 34.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 36.8 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 37.8 dBmV
5 Not Locked Unknown 0 0 0 0
6 Not Locked Unknown 0 0 0 0
7 Not Locked Unknown 0 0 0 0
8 Not Locked Unknown 0 0 0 0

Event logs from my modem

Lots of critical errors and warnings.

Time Priority Description
Thu Jan 18 07:53:07 2024 Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:53:07 2024 Notice (6)
TLV-11 - unrecognized OID;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:56 2024 Notice (6)
Honoring MDD; IP provisioning mode = IPv6
Thu Jan 18 07:52:50 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:38 2024 Warning (5)
ToD request sent - No Response received;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:38 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:35 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:24 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:21 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:50:30 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:50:21 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:49:59 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:49:56 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:49:29 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:49:20 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:59 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:57 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:38 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:36 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:35 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:28 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:28 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:27 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:25 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:20 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:20 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:20 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:19 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:19 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:19 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:18 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:18 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:18 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:15 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:14 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:06 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:05 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:04 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:02 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:48:02 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;

1 year ago

0

user_53yxh3

6 Messages

The problem with constant outages persists.

Downstream Bonded Channels

These power levels actually look good.

Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 507000000 Hz 7.1 42.2 9445 7875
2 Locked QAM256 4 405000000 Hz 5.5 41.7 17727 8377
3 Locked QAM256 5 411000000 Hz 4.5 41.6 16407 7503
4 Locked QAM256 6 417000000 Hz 6.1 42 17167 8448
5 Locked QAM256 7 423000000 Hz 5.7 42 12154 7053
6 Locked QAM256 8 429000000 Hz 6.4 42.2 10947 6916
7 Locked QAM256 9 435000000 Hz 4.8 41.8 11310 5986
8 Locked QAM256 10 441000000 Hz 5.9 42 12811 6845
9 Locked QAM256 11 447000000 Hz 5.9 42.1 11578 6876
10 Locked QAM256 12 453000000 Hz 7.1 42.2 9218 6940
11 Locked QAM256 13 459000000 Hz 6.5 42.1 8623 5562
12 Locked QAM256 14 465000000 Hz 6.9 42.1 8613 5696
13 Locked QAM256 15 471000000 Hz 6.4 42 9927 5312
14 Locked QAM256 16 477000000 Hz 6.9 42.2 11393 5926
15 Locked QAM256 17 483000000 Hz 7.3 42.2 9061 6223
16 Locked QAM256 18 489000000 Hz 7.8 42.2 6997 5553
17 Locked QAM256 19 495000000 Hz 7.1 42.1 7444 4888
18 Locked QAM256 21 513000000 Hz 7.6 42.3 7071 5231
19 Locked QAM256 22 519000000 Hz 7.8 42.3 7254 5343
20 Locked QAM256 23 525000000 Hz 7.4 42.1 5940 4537
21 Locked QAM256 24 531000000 Hz 7.4 42.1 5323 4475
22 Locked QAM256 25 543000000 Hz 7.5 42.1 6171 4854
23 Locked QAM256 26 549000000 Hz 7.3 42.1 5617 4444
24 Locked QAM256 27 555000000 Hz 8 42.2 5389 4744
25 Locked QAM256 28 561000000 Hz 6.7 41.8 5406 3707
26 Locked QAM256 29 567000000 Hz 7.4 42 5549 4167
27 Locked QAM256 30 573000000 Hz 6.9 42 4889 3838
28 Locked QAM256 31 579000000 Hz 7.9 42.1 5129 4667
29 Locked QAM256 32 585000000 Hz 7.4 42 4788 3763
30 Locked QAM256 33 591000000 Hz 7.9 42.1 4407 3913
31 Locked QAM256 34 597000000 Hz 6.5 41.8 4237 3331
32 Not Locked Unknown 0 0 Hz 0 0 0 0

Upstream Bonded Channels (Partial Service)

Power levels still a bit on the low side.

Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 38.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 37.3 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 39.3 dBmV
4 Not Locked Unknown 0 0 0 0
5 Not Locked Unknown 0 0 0 0
6 Not Locked Unknown 0 0 0 0
7 Not Locked Unknown 0 0 0 0
8 Not Locked Unknown 0 0 0 0

Event logs from my modem

Note: RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW

Time Priority Description
Thu Jan 18 08:52:52 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:52:33 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:52:12 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:52:02 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:40 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:32 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:21 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:15 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:02 2024 Notice (6)
CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:51:01 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:59 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:59 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:57 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:56 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:54 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:54 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:52 2024 Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:52 2024 Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:50:52 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:21:13 2024 Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:53 2024 Warning (5)
Dynamic Range Window violation
Thu Jan 18 08:19:53 2024 Warning (5)
RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:52 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:51 2024 Warning (5)
Dynamic Range Window violation
Thu Jan 18 08:19:51 2024 Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:51 2024 Warning (5)
Dynamic Range Window violation
Thu Jan 18 08:19:51 2024 Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:51 2024 Warning (5)
Dynamic Range Window violation
Thu Jan 18 08:19:51 2024 Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:50 2024 Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 08:19:48 2024 Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:53:07 2024 Notice (6)
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:53:07 2024 Notice (6)
TLV-11 - unrecognized OID;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:56 2024 Notice (6)
Honoring MDD; IP provisioning mode = IPv6
Thu Jan 18 07:52:50 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:38 2024 Warning (5)
ToD request sent - No Response received;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:38 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:35 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:24 2024 Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 07:52:21 2024 Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N\A;CM-QOS=1.1;CM-VER=3.1;

1 year ago

0

user_53yxh3

6 Messages

1 year ago

First troubleshooting step from Xfinity

Reset the modem. I'll continue to monitor the quality of the connection.

Thu Jan 18 09:21:24 2024 (Notice (6))
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 09:21:18 2024 (Notice (6))
TLV-11 - unrecognized OID;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6))
Honoring MDD; IP provisioning mode = IPv6
Time Not Established (Critical (3))
No Ranging Response received - T3 time-out;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3))
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=N/A;CMTS-MAC=N/A;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 18 09:20:05 2024 (Critical (3))
Resetting the cable modem due to docsDevResetNow

0

0

XfinityJustinC

Official Employee

 • 

1.2K Messages

1 year ago

@user_53yxh3 I am glad we were able to get a technician scheduled to your home to investigate your network connection, please let us know if you need anything else. We're available 7 days a week from 6am - 12am ET for employee support, thank you. 

0

0

forum icon

New to the Community?

Start Here