Skip to main content

    Support

    Offers

29464's profile
29464
Conversation Starter
1st Like
1st Accepted Solution

Frequent Visitor

 • 

20 Messages

Wednesday, January 24th, 2024 2:18 AM

Closed

Reboot Modem

The past two months I've had to reboot the modem every 48 to 72 hours. I have a Netgear CM 1150v. I have had this modem for several years, always worked fine. Now it needs to reboot often. Any suggestions short of renting an expensive one from Xfinity. 

Question

 • 

Updated 

11 months ago

218

6

0

EG

Expert

 • 

110.1K Messages

1 year ago

2

0

29464

Frequent Visitor

 • 

20 Messages

don't know what any of this means.

Time Priority Description
Wed Jan 24 08:49:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; 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;
Wed Jan 24 08:49:09 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Wed Jan 24 08:49:04 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;
Wed Jan 24 08:48:59 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;
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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Jan 24 08:45: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 Jan 23 17:01:06 2024 Error (4) Service Add ACK rejected - HMAC auth failure;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Tue Jan 23 16:59:01 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 Jan 22 10:00:06 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; 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;
Mon Jan 22 09:59:56 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:59:51 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 Jan 22 09:59:50 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;
Mon Jan 22 09:59:42 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Jan 22 09:59:31 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;
Mon Jan 22 09:57:53 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:57:46 2024 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:57:41 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;
Mon Jan 22 09:57:38 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:57:31 2024 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:57:15 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;
Mon Jan 22 09:56:42 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:56:38 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:56:36 2024 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:48:10 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; 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;
Mon Jan 22 09:47:19 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;
Mon Jan 22 09:46:56 2024 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:46:53 2024 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 09:35:59 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 Jan 22 08:54:25 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; 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;
Mon Jan 22 08:54:10 2024 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 08:54:05 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 Jan 22 08:54:00 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;
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=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jan 22 08:01:22 2024 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8; 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;
Mon Jan 22 08:01:11 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 Jan 22 08:00:24 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;

(edited)

1 year ago

0

XfinityMartyR

Official Employee

 • 

2K Messages

Hi, @29464. Thanks for reaching out. Taking a quick glance at the log you posted, the first thing that stands out are T3 timeouts. These timeouts are typically caused by noise or interference in either the upstream, or downstream signal levels. In some cases it may lead to a lack of signal to the modem. I would first check your cable connection from the cable outlet, to the modem. Ensure they are finger tight. Also, if you have a splitter in use eliminate it if you can, and see if anything improves.  

(edited)

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

1 year ago

0

EG

Expert

 • 

110.1K Messages

1 year ago

@29464 

Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries 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 Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

0

0

EG

Expert

 • 

110.1K Messages

1 year ago

@29464 

Have you had a chance to gather the requested signal status info ?

2

0

29464

Frequent Visitor

 • 

20 Messages

well, it worked for 5 days after I re-activated my modem but in the past 24 hours I've had to reboot the modem twice. Will try to get the signal status info tonight.

1 year ago

0

29464

Frequent Visitor

 • 

20 Messages


Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 9 507000000 Hz -1 dBmV 40.8 dB 0 0
2 Locked QAM256 1 453000000 Hz -3.6 dBmV 40.4 dB 0 0
3 Locked QAM256 2 459000000 Hz -4.1 dBmV 40 dB 0 0
4 Locked QAM256 3 465000000 Hz -2.9 dBmV 40.8 dB 0 0
5 Locked QAM256 4 471000000 Hz -2.7 dBmV 41 dB 0 0
6 Locked QAM256 5 477000000 Hz -1.6 dBmV 41.3 dB 0 0
7 Locked QAM256 6 483000000 Hz -1.6 dBmV 41.3 dB 0 0
8 Locked QAM256 7 489000000 Hz -1.4 dBmV 40.2 dB 0 0
9 Locked QAM256 8 495000000 Hz -0.6 dBmV 39.9 dB 0 0
10 Locked QAM256 10 513000000 Hz -0.9 dBmV 41.4 dB 0 0
11 Locked QAM256 11 519000000 Hz -1.4 dBmV 41.2 dB 0 0
12 Locked QAM256 12 525000000 Hz -0.4 dBmV 41.7 dB 0 0
13 Locked QAM256 13 531000000 Hz 0.1 dBmV 38.6 dB 0 0
14 Locked QAM256 14 537000000 Hz -0.9 dBmV 39.5 dB 0 0
15 Locked QAM256 15 543000000 Hz -1.5 dBmV 40.8 dB 0 0
16 Locked QAM256 16 549000000 Hz -0.3 dBmV 41.5 dB 9 0
17 Locked QAM256 17 555000000 Hz 1.1 dBmV 41.9 dB 0 0
18 Locked QAM256 18 561000000 Hz 1.2 dBmV 41.8 dB 0 0
19 Locked QAM256 19 567000000 Hz 0.3 dBmV 41.6 dB 0 0
20 Locked QAM256 20 573000000 Hz -0.7 dBmV 41.1 dB 0 0
21 Locked QAM256 21 579000000 Hz -0.8 dBmV 41.1 dB 0 0
22 Locked QAM256 22 585000000 Hz -1.1 dBmV 41.1 dB 0 0
23 Locked QAM256 23 591000000 Hz -1.8 dBmV 39.6 dB 0 0
24 Locked QAM256 38 429000000 Hz -2.1 dBmV 41.2 dB 15874 9321
25 Locked QAM256 39 435000000 Hz -2.2 dBmV 41.1 dB 0 0
26 Locked QAM256 40 441000000 Hz -2.2 dBmV 41.1 dB 0 0
27 Locked QAM256 41 447000000 Hz -2.4 dBmV 41 dB 0 0
28 Locked QAM256 42 405000000 Hz -3.1 dBmV 40.9 dB 0 0
29 Locked QAM256 43 411000000 Hz -2.3 dBmV 41.1 dB 0 0
30 Locked QAM256 44 417000000 Hz -2.1 dBmV 41.4 dB 0 0
31 Locked QAM256 45 423000000 Hz -2.9 dBmV 40.7 dB 11701 34637
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
 

                                      

upstream

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 2560 Ksym/sec 10400000 Hz 47.8 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 16400000 Hz 48 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 22800000 Hz 48 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 29200000 Hz 48.3 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown

1 year ago

0

EG

Expert

 • 

110.1K Messages

1 year ago

This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless. 

The upstream power is a bit on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

2

0

29464

Frequent Visitor

 • 

20 Messages

I find it interesting that the network was working fine until Dec, then the problems began. The line to the modem is direct, there is a splitter from the house to the modem, but that is it.  It works for a couple days after I re-activated my modem. 

1 year ago

0

XfinityArmand

Official Employee

 • 

2.1K Messages

Hi there @29464!  We are glad to assist in addressing your service concerns.  Please feel free to shoot us a private message so that we can take a closer look at what is going on.  

 

To send a "direct message" / "private message" message to Xfinity Support:

 • Click "Sign In" if necessary

 • Click the "Direct Message" icon or https://forums.xfinity.com/direct-messaging 

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

 • The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there

 •  - As you are typing a drop-down list appears. Select "Xfinity Support" from that list

 •  - An "Xfinity Support" graphic replaces the "To:" line

 • Type your message in the text area near the bottom of the window

 • Press Enter to send it

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

1 year ago

0

EG

Expert

 • 

110.1K Messages

1 year ago

@29464 @XfinityArmand 

Please circle back here and post any possible solutions for the issue here in these open forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

1

0

29464

Frequent Visitor

 • 

20 Messages

I had a tech come out last week. He said something needed to be done in the neighborhood. I'm still rebooting the modem every 24 hours.

1 year ago

0

user_4liiom

1 Message

11 months ago

I upgraded my Router, so I enabled IPv6 and when I did the Modem Log gave a code that led me here.  Any chance your problem is IPv6 related?

0

0

forum icon

New to the Community?

Start Here