Skip to main content

    Support

    Offers

U
user_fc4er0
1st Topic
1st Like

3 Messages

Tuesday, October 22nd, 2024 5:50 PM

Closed

Intermittent drops several times a day

Multiple times a day I am getting drops. I have replaced the modem twice and still seeing the issues - now using a Netgear CM3000 modem and Netgear RAXE500 router. In my research, it appears that there could be an upstream line issue. Could this be true? Does Infinity need to come out to replace or change something outside the house? I'm seeing these lines in the modem log. 

Tue Oct 22 09:42:44 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;

Tue Oct 22 09:28:29 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 8; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:25 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;

Tue Oct 22 09:28:25 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:20 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:15 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:14 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:10 2024

(Critical (3))

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:10 2024

(Critical (3))

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:28:10 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;

Tue Oct 22 09:11:58 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 8; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:54 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; 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;

Tue Oct 22 09:11:47 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:47 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;

Tue Oct 22 09:11:46 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:37 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:35 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:31 2024

(Critical (3))

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:31 2024

(Critical (3))

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:11:31 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;

Tue Oct 22 09:09:56 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 8; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:50 2024

(Warning (5))

Dynamic Range Window violation

Tue Oct 22 09:09:50 2024

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

Tue Oct 22 09:09:47 2024

(Warning (5))

Dynamic Range Window violation

Tue Oct 22 09:09:47 2024

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

Tue Oct 22 09:09:46 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:44 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:35 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:34 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:32 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:27 2024

(Critical (3))

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:27 2024

(Critical (3))

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:27 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;

Tue Oct 22 09:09:25 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; 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;

Tue Oct 22 09:09:24 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;

Tue Oct 22 09:09:09 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:09:06 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:08:59 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:08:55 2024

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

Tue Oct 22 09:08:49 2024

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

 

Question

 • 

Updated 

8 months ago

 • Edited

58

3

0

EG

Expert

 • 

111.2K Messages

8 months ago

Please also 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.

1

0

EG

Expert

 • 

111.2K Messages

8 months ago

Yes. Thanks. The signal status values at that snapshot in time were OK but the error log entries indicate that something is going on. And there are a fair number of uncorrectable bit errors. 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 !

2

0

user_fc4er0

3 Messages

@EG​ Thank you so much!

8 months ago

XfinityBrianH

Official Employee

 • 

1.4K Messages

 

user_fc4er0 Can you please send us a DM. 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. 

 

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

8 months ago

0

EG

Expert

 • 

111.2K Messages

8 months ago

@user_fc4er0 

You're very welcome !

0

0

forum icon

New to the Community?

Start Here