Skip to main content

    Support

    Offers

U
user_tt1j4i
1st Topic
1st Like

4 Messages

Tuesday, May 14th, 2024 4:29 PM

Closed

CAX80 Critical/Warnings errors in log

Hi Xfinity

I am told by Netgear, that these errors in my log file is related to your service and I would like to know how and when you plan on fixing these error messages.  Netgear is stating this is an issue on your end and there is nothing with their device they can do to correct it.  I am told I should not be seeing Critical/Warning messages in the log file.  Contacting support is hopeless.

Event Log
Clear Log Refresh
 
Time Priority Description
Tue May 14 00:26:08 2024 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;
Mon May 13 23:25:36 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon May 13 23:25:35 2024 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;
Mon May 13 23:25:29 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon May 13 23:25:28 2024 Notice (6) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon May 13 23:25:27 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon May 13 23:25:01 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:52 1970 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:46 1970 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:43 1970 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon May 13 23:14:30 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:46 1970 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

Question

 • 

Updated 

1 year ago

 • Edited

139

4

0

XfinityChristy

Official Employee

 • 

2K Messages

1 year ago

 

user_tt1j4i Hello and thank you for reaching out via our Xfinity Community Forum. I would be happy to take a closer look at your network connection with you and see how we can help with this service concern. To get started, please send our team a Direct Message with your full name, the name listed on the account (if different), and the service address associated with your account. 

 

To send a "Direct Message" message:

Click "Sign In" if necessary

Click the "Direct Messaging" icon at the top of the page (looks like a text bubble)

Click the "New message" (pencil and paper) icon

Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list that 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

 

0

0

EG

Expert

 • 

110.7K Messages

1 year ago

@user_tt1j4i 

Are you actually experiencing any connectivity problems / dropouts / speed problems, or are you just focusing on those error log messages?

1

0

user_tt1j4i

4 Messages

@EG​ I experience buffering on my tv channels thru airtv and other services.  Occasionally I am experiencing dropped internet connects on work/home computer.  Speeds are not consistent. Some days I may get 300gb downloads, some days I may get 450gb.  I received notification back in March 2024 that my speed was increased to 2X the speed.  I do not see it at all.  When i signed up back in 9/23 I ordered the following:

Fast | Up to 400 Mbps download speed; Up to 100 Mbps upload speed

Then I get this message in March 2024:

We've increased your internet speeds to show you our appreciation You can now enjoy 2x faster upload speeds and improved download speeds for smoother connections when you’re working, gaming and streaming.


Increased it to what?? 800gb because they are not even close. Just like any customer, if I pay for a service that is promised to me, I think I should get it.  Maybe I am asking for too much.

(edited)

1 year ago

0

EG

Expert

 • 

110.7K Messages

1 year ago

What do the modem's signal stats look like ? Try getting them here; http://192.168.100.1 or here http://10.0.0.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 modem / gateway device ?

Is this with WiFi connections ?

(edited)

1

0

user_tt1j4i

4 Messages

@EG​ According to Netgear the download/upload should be Good Downstream power levels are within -7 to +7 dBmV. Good Upstream power levels are within 38-48 dBmV. How do I view the downstream and upstream power levels of my cable modem or modem router? - NETGEAR Support.

I had to add a -6dbm cable coax line attenuator in between the modem and ISP cable line per the Netgear support.  When I mentioned the same thing to the Xfinity tech, they said don't do that...Why is that?  If you want the downstream/upstream power levels before I added the attenuator, I still have a copy of the report. I saved a copy after the Xfinity tech was here to see if there were any changes and there were not.

Again, I was told by Netgear that Xfinity should fix these errors.  

Make and model of my router is Netgear Nighthawk CAX80, firmware is V2.1.5.2

Sporadic issues with both wired and Wi-Fi.

Cable Diagnostic

Status: Good

Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.

Internet Access: Good

Downstream Status: Good

    Downstream Power Level: Good

    Downstream SNR: Good

Upstream Status:  Good

    Upstream Power Level: Good


Current time: Sun May 19 18:22:40 2024

Startup Procedure
Acquire Downstream Channel: 651 MHz   Locked
Connectivity State:          OK       Operational
Boot State:                  OK       Operational
Security:                   Enabled   BPI+


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID  Frequency        Power       SNR   Correctables Uncorrectables     
      1     Locked     256 QAM     44     651000000 Hz     3.8 dBmV     44.3 dB     0     0
      2     Locked     256 QAM     13     465000000 Hz     4.3 dBmV     45.8 dB     0     0
      3     Locked     256 QAM     14     471000000 Hz     4.3 dBmV     45.8 dB     0     0
      4     Locked     256 QAM     15     477000000 Hz     4.5 dBmV     45.9 dB     0     0
      5     Locked     256 QAM     16     483000000 Hz     4.5 dBmV     45.8 dB     0     0
      6     Locked     256 QAM     17     489000000 Hz     4.3 dBmV     45.8 dB     0     0
      7     Locked     256 QAM     18     495000000 Hz     4.4 dBmV     45.8 dB     0     0
      8     Locked     256 QAM     19     501000000 Hz     4.4 dBmV     45.8 dB     0     0
      9     Locked     256 QAM     20     507000000 Hz     4.3 dBmV     45.7 dB     0     0
     10     Locked     256 QAM     21     513000000 Hz     4.1 dBmV     45.6 dB     0     0
     11     Locked     256 QAM     22     519000000 Hz     4.1 dBmV     45.6 dB     0     0
     12     Locked     256 QAM     23     525000000 Hz     4.2 dBmV     45.5 dB     0     0
     13     Locked     256 QAM     24     531000000 Hz     4 dBmV     45.4 dB     0     0
     14     Locked     256 QAM     25     537000000 Hz     3.8 dBmV     45.3 dB     0     0
     15     Locked     256 QAM     26     543000000 Hz     3.8 dBmV     45.3 dB     0     0
     16     Locked     256 QAM     27     549000000 Hz     3.7 dBmV     45.2 dB     0     0
     17     Locked     256 QAM     28     555000000 Hz     3.5 dBmV     45.1 dB     0     0
     18     Locked     256 QAM     29     561000000 Hz     3.5 dBmV     45 dB     0     0
     19     Locked     256 QAM     30     567000000 Hz     3.5 dBmV     45 dB     0     0
     20     Locked     256 QAM     31     573000000 Hz     3.4 dBmV     44.9 dB     0     0
     21     Locked     256 QAM     32     579000000 Hz     3.4 dBmV     44.9 dB     0     0
     22     Locked     256 QAM     33     585000000 Hz     3.4 dBmV     44.8 dB     0     0
     23     Locked     256 QAM     34     591000000 Hz     3.6 dBmV     44.9 dB     0     0
     24     Locked     256 QAM     35     597000000 Hz     3.6 dBmV     44.9 dB     0     0
     25     Locked     256 QAM     36     603000000 Hz     3.5 dBmV     44.8 dB     0     0
     26     Locked     256 QAM     37     609000000 Hz     3.6 dBmV     44.9 dB     0     0
     27     Locked     256 QAM     38     615000000 Hz     3.6 dBmV     44.9 dB     0     0
     28     Locked     256 QAM     39     621000000 Hz     3.7 dBmV     44.8 dB     0     0
     29     Locked     256 QAM     40     627000000 Hz     3.6 dBmV     44.7 dB     0     0
     30     Locked     256 QAM     41     633000000 Hz     3.6 dBmV     44.8 dB     0     0
     31     Locked     256 QAM     42     639000000 Hz     3.8 dBmV     44.8 dB     0     0
     32     Locked     256 QAM     43     645000000 Hz     3.7 dBmV     44.8 dB     0     0


Upstream Bonded Channels
Channel   LockedStatus  ChannelType ChannelID   SymbolRate        Frequency       Power     
      1       Locked       ATDMA     19       5120 Ksym/sec       29200000 Hz       38.8 dBmV
      2       Locked       ATDMA     18       5120 Ksym/sec       22800000 Hz       38.8 dBmV
      3       Locked       ATDMA     17       5120 Ksym/sec       16400000 Hz       39.3 dBmV
      4       Locked       ATDMA     20       5120 Ksym/sec       35600000 Hz       38.5 dBmV
      5       Not Locked       Unknown      0       0       0       0.0
      6       Not Locked       Unknown      0       0       0       0.0
      7       Not Locked       Unknown      0       0       0       0.0
      8       Not Locked       Unknown      0       0       0       0.0


Downstream OFDM Channels
Channel   LockedStatus  ProfileID  ChannelID    Frequency       Power       SNR/MER    ActiveSubcarrier    Unerror    Correctable   Uncorrectable
      1     Locked     0 ,1 ,2 ,3     193     690000000 Hz     4.28 dBmV     44.5 dB     508 ~ 3587     2719278828     1154971189     1731
      2     Locked     0 ,1 ,2 ,3     194     957000000 Hz     -1.12 dBmV     42.3 dB     148 ~ 3947     2712436799     1613524240     0


Upstream OFDMA Channels
Channel   LockedStatus    ProfileID    ChannelID    Frequency       Power
      1     Not Locked     0      0     0 Hz     0 dBmV
      2     Not Locked     0      0     0 Hz     0 dBmV


Event Log
         Time               Priority     Description
Sun May 19 18:19:00 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; 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;
Sun May 19 09:16:39 2024     Critical     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;
Sun May 19 09:14:39 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun May 19 09:08:26 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 12:26:22 2024     Critical     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;
Sat May 18 12:14:35 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"]:CM-QOS=1.1;CM-VER=3.1;
Sat May 18 12:13:18 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; 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;
Sat May 18 10:57:35 2024     Critical     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;
Sat May 18 10:42:12 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:37:31 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:33:28 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:29:44 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:27:30 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:24:12 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:23:13 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat May 18 10:17:29 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 14:50:23 2024     Critical     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;
Fri May 17 12:42:08 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 12:37:27 2024     Notice     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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 12:29:45 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 12:23:21 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 10:23:46 2024     Critical     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;
Fri May 17 09:33:44 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 09:30:15 2024     Notice     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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 09:20:14 2024     Notice     CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"]
Fri May 17 09:19:49 2024     Warning     MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 09:09:44 2024     Notice     CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"]
Fri May 17 09:09:36 2024     Warning     MDD message timeout;CM-MAC=94:18:65:a6:1f:63;CMTS-MAC=00:90:f0:63:04:00;CM-QOS=1.1;CM-VER=3.1;
Fri May 17 01:46:50 2024     Critical     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;
Fri May 17 01:16:33 2024     Notice     CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri May 17 01:10:49 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu May 16 21:19:46 2024     Critical     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;
Thu May 16 21:17:01 2024     Notice     CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"]
Thu May 16 21:16:39 2024     Warning     MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu May 16 18:57:44 2024     Critical     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;
Thu May 16 18:29:54 2024     Notice     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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu May 16 18:24:28 2024     Notice     CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu May 16 16:55:40 2024     Critical     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;
Thu May 16 15:23:13 2024     Notice     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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Thu May 16 15:22:05 2024     Notice     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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

(edited)

1 year ago

0

EG

Expert

 • 

110.7K Messages

1 year ago

The signal status values at that snapshot in time were good, but the error log entries indicate 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 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 those upstream receive signal stats.


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

1

user_tt1j4i

4 Messages

@EG​ Thank you @EG I appreciate the help.  However, I am concerned how I was able to obtain the status above using the -6dbm cable coax line attenuator.  Without that my connection status was poor for download power.  I have copies of the same log from before the Xfinity visit and after.  The Xfinity tech that was onsite told me I didn't need a cable coax line attenuator and told me not to do it, that would disrupt the line/service which seems to be not true, it has improved the service to some extent.  Thank you again. 

1 year ago

forum icon

New to the Community?

Start Here