Highlighted
Observer

Frequent Modem Reboots. Several Modems.

Hello,

 

I recently upgraded to the Gigabit plan that Spectrum offers and the speeds are great but i have been having terrible connection issues during late afternoons and through the nights. The modem will reboot several times a day. I host several game servers in my home, and it is becoming extremely frustrating for me and the players. I have swapped to three different Modems. First i was using the spectrum provided modem, then a Netgear CM700, and now a Netgear CM1000. All are having the same problem.

As far as i can tell the signal levels are where they should be, but I’m not a cable technician so i don't really know. I do however see some critical errors in the logs, and this has been consistent with all equipment. Research on these errors always results in "Check your signal levels". I understand that speeds may decrease during peak times with the shared bandwidth infrastructure that is cable internet, but i don't feel like it should be enough to completely kick my modem offline.

Calling the Internet & Phone support is not much help. They just want to constantly reboot the modem, poke fun at the fact that they can't help since I’m no longer using their equipment, and get me off of the phone as quick as possible to keep the boss man happy. I’m hoping i can find some competent assistance here. Thanks for taking the time!

 

 

=Frequency start Value =
Starting Frequency  807000000

=Startup Procedure=
Acquire Downstream Channel 	807000000 	Hz Locked 
Connectivity State 		OK 		Operational 
Boot State 			OK 		Operational 
Security 			Enable 		BPI+ 
IP Provisioning Mode 		Honor MDD 	IPv4 only

=Downstream Bonded Channels=
1  Locked QAM256 32 807000000 Hz  0.3 dBmV 40.6 dB 1287566461 108 218 
2  Locked QAM256 1  627000000 Hz -0.8 dBmV 41.1 dB 1278466983 204 173 
3  Locked QAM256 2  633000000 Hz -0.3 dBmV 41.0 dB 1278492648 185 166 
4  Locked QAM256 3  639000000 Hz -1.1 dBmV 40.9 dB 1278518939 165 213 
5  Locked QAM256 4  645000000 Hz -0.1 dBmV 41.1 dB 1278546542 216 179 
6  Locked QAM256 5  651000000 Hz -0.3 dBmV 40.9 dB 1278571375 185 183 
7  Locked QAM256 6  657000000 Hz -0.4 dBmV 40.9 dB 1278596620 152 150 
8  Locked QAM256 7  663000000 Hz  0.4 dBmV 41.0 dB 1278619160 107 181 
9  Locked QAM256 8  669000000 Hz -0.1 dBmV 41.0 dB 1278650304 163 151 
10 Locked QAM256 9  675000000 Hz -0.1 dBmV 40.5 dB 1278678446 157 135 
11 Locked QAM256 10 681000000 Hz -0.1 dBmV 40.7 dB 1280391786 129 163 
12 Locked QAM256 11 687000000 Hz -0.6 dBmV 40.5 dB 1280418317 104 165 
13 Locked QAM256 12 693000000 Hz -0.3 dBmV 40.5 dB 1280439969 97  163 
14 Locked QAM256 13 699000000 Hz -0.5 dBmV 40.4 dB 1280465911 119 154 
15 Locked QAM256 14 705000000 Hz -0.9 dBmV 40.1 dB 1280489474 113 166 
16 Locked QAM256 15 711000000 Hz  0.1 dBmV 40.5 dB 1280513037 115 120 
17 Locked QAM256 16 717000000 Hz  0.1 dBmV 40.5 dB 1280543623 131 117 
18 Locked QAM256 17 723000000 Hz  0.1 dBmV 40.7 dB 1280568989 99  137 
19 Locked QAM256 18 729000000 Hz  0.5 dBmV 40.4 dB 1280594621 90  127 
20 Locked QAM256 19 735000000 Hz -0.3 dBmV 40.4 dB 1280619209 128 107 
21 Locked QAM256 20 741000000 Hz -0.1 dBmV 40.4 dB 1280956258 112 102 
22 Locked QAM256 21 747000000 Hz 0.2 dBmV 40.3 dB 1280982897 86 134 
23 Locked QAM256 22 753000000 Hz -0.8 dBmV 39.9 dB 1281008222 111 116 
24 Locked QAM256 23 759000000 Hz -0.7 dBmV 39.8 dB 1281031772 105 135 
25 Locked QAM256 24 765000000 Hz -0.8 dBmV 39.8 dB 1281061259 103 115 
26 Locked QAM256 25 771000000 Hz -1.4 dBmV 39.9 dB 1281087682 115 126 
27 Locked QAM256 26 777000000 Hz -0.3 dBmV 40.1 dB 1281090711 87 99 
28 Locked QAM256 27 783000000 Hz -1.0 dBmV 40.1 dB 1281075631 101 94 
29 Locked QAM256 28 789000000 Hz -0.5 dBmV 40.2 dB 1281073683 65 120 
30 Locked QAM256 30 795000000 Hz 1.0 dBmV 40.7 dB 1280784025 77 122 
31 Locked QAM256 31 801000000 Hz -1.0 dBmV 40.5 dB 1280872056 60 103 
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 
 
=Upstream Bonded Channels=
1 Locked TDMA  49 19400000 Hz 42.5 dBmV 
2 Locked ATDMA 50 24200000 Hz 45.0 dBmV 
3 Locked ATDMA 51 30600000 Hz 46.5 dBmV 
4 Locked ATDMA 52 37000000 Hz 47.8 dBmV 
5 Not Locked Unknown 0 0 Hz 0.0 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 

=Downstream OFDM Channels=
1 Locked 0, 1, 2, 255 29 338000000 Hz -2.0 dBmV 40.8 dB 1108 ~ 2987 1330226315 1282585137 837 
2 Not Locked 0, 255 0 0 Hz -4.4 dBmV 0.0 dB 0 ~ 4095 0 0 0 

=Upstream OFDMA Channels=
1 Not Locked Unknown 0 0 Hz 0 dBmV 
2 Not Locked Unknown 0 0 Hz 0 dBmV 


=Event Log= 2019-06-27, 04:04:26 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 29 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 04:02:49 Warning (5) Dynamic Range Window violation 2019-06-27, 04:02:49 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 04:02:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:46:32 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 29 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:14 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:13 Notice (6) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:13 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:13 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:12 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:07 Notice (6) Honoring MDD; IP provisioning mode = IPv4 2019-06-27, 03:16:05 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:16:02 Notice (6) Received REG-RSP while in REG-HOLD1 state;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:59 Notice (6) Received REG-RSP while in REG-HOLD1 state;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:38 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:37 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:35 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:31 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:29 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:24 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:23 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:22 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:13 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:12 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:12 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:12 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:03 Warning (5) Dynamic Range Window violation 2019-06-27, 03:15:03 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 2019-06-27, 03:15:03 Warning (5) Dynamic Range Window violation

 

10 REPLIES 10
Sharer

Re: Frequent Modem Reboots. Several Modems.

Something may be up with upstream QoS.... big jump in power level across the channels. One may intermittently be spiking far enough over 50 to call for a reboot.
Observer

Re: Frequent Modem Reboots. Several Modems.

Thanks you for the response RAIST5150. Do you have any advise on how to handle this issue? 

Observer

Re: Frequent Modem Reboots. Several Modems.

The modem just restarted for the first time tonight. There will likely be more. I will upload another log capture before I go to sleep in hopes of helping someone recognize a pattern or the potential cause. 

 

=Downstream Bonded Channels=
1 Locked  QAM256 32 807000000 Hz -2.2 dBmV 40.1 dB 2572268531 145 362 
2 Locked  QAM256 1  627000000 Hz -0.1 dBmV 41.8 dB 2558828060 255 304 
3 Locked  QAM256 2  633000000 Hz  0.3 dBmV 41.7 dB 2558855681 207 285 
4 Locked  QAM256 3  639000000 Hz -0.5 dBmV 41.5 dB 2558883504 199 340 
5 Locked  QAM256 4  645000000 Hz  0.5 dBmV 41.8 dB 2558913382 240 314 
6 Locked  QAM256 5  651000000 Hz  0.4 dBmV 41.7 dB 2558939345 213 300 
7 Locked  QAM256 6  657000000 Hz  0.3 dBmV 41.7 dB 2558961020 207 213 
8 Locked  QAM256 7  663000000 Hz  1.0 dBmV 41.8 dB 2558985731 150 260 
9 Locked  QAM256 8  669000000 Hz  0.4 dBmV 41.6 dB 2559017610 213 204 
10 Locked QAM256 9  675000000 Hz  0.1 dBmV 40.8 dB 2559048868 220 197 
11 Locked QAM256 10 681000000 Hz  0.0 dBmV 41.1 dB 2561814751 172 258 
12 Locked QAM256 11 687000000 Hz -0.8 dBmV 40.9 dB 2561844025 146 223 
13 Locked QAM256 12 693000000 Hz -0.6 dBmV 40.9 dB 2561866996 131 218 
14 Locked QAM256 13 699000000 Hz -1.0 dBmV 40.6 dB 2561895640 141 229 
15 Locked QAM256 14 705000000 Hz -1.6 dBmV 40.5 dB 2561920926 133 221 
16 Locked QAM256 15 711000000 Hz -0.7 dBmV 40.8 dB 2561947166 132 172 
17 Locked QAM256 16 717000000 Hz -0.8 dBmV 40.7 dB 2561979093 146 167 
18 Locked QAM256 17 723000000 Hz -0.9 dBmV 40.8 dB 2562004868 135 185 
19 Locked QAM256 18 729000000 Hz -0.6 dBmV 40.8 dB 2562033493 108 181 
20 Locked QAM256 19 735000000 Hz -1.5 dBmV 40.5 dB 2562058926 143 156 
21 Locked QAM256 20 741000000 Hz -1.3 dBmV 40.6 dB 2562958313 124 143 
22 Locked QAM256 21 747000000 Hz -1.0 dBmV 40.4 dB 2562987155 108 187 
23 Locked QAM256 22 753000000 Hz -2.1 dBmV 39.8 dB 2563015162 133 159 
24 Locked QAM256 23 759000000 Hz -2.0 dBmV 40.1 dB 2563040087 121 178 
25 Locked QAM256 24 765000000 Hz -2.3 dBmV 40.0 dB 2563071488 120 160 
26 Locked QAM256 25 771000000 Hz -3.0 dBmV 39.7 dB 2563100109 134 166 
27 Locked QAM256 26 777000000 Hz -1.9 dBmV 40.1 dB 2563096808 101 141 
28 Locked QAM256 27 783000000 Hz -2.7 dBmV 40.0 dB 2563075567 111 136 
29 Locked QAM256 28 789000000 Hz -2.5 dBmV 40.3 dB 2563073491 76 173 
30 Locked QAM256 30 795000000 Hz -1.1 dBmV 40.6 dB 2562724694 89 164 
31 Locked QAM256 31 801000000 Hz -3.3 dBmV 40.0 dB 2563155409 74 146 
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 

=Upstream Bonded Channels=
1 Locked TDMA  49 19400000 Hz 37.3 dBmV 
2 Locked ATDMA 50 24200000 Hz 39.5 dBmV 
3 Locked ATDMA 51 30600000 Hz 41.3 dBmV 
4 Locked ATDMA 52 37000000 Hz 42.8 dBmV 
5 Not Locked Unknown 0 0 Hz 0.0 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 

=Downstream OFDM Channels=
1 Locked 0, 1, 2, 255 29 338000000 Hz -0.8 dBmV 41.0 dB 1108 ~ 2987 2306229043 2211556755 1178 
2 Not Locked 0, 255 0 0 Hz -1.5 dBmV 0.0 dB 0 ~ 4095 0 0 0 

=Upstream OFDMA Channels=
1 Not Locked Unknown 0 0 Hz 0 dBmV 
2 Not Locked Unknown 0 0 Hz 0 dBmV 

=Event Log=
2019-06-27, 16:14:41 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Notice (6) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:34 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:38 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:35 Notice (6) Honoring MDD; IP provisioning mode = IPv4 
2019-06-27, 16:13:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:07 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:06 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:02 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:09 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:09 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:09 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:17:18 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 29 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:08:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 14:08:09 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:08:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 14:08:09 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:08:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 14:08:09 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:08:02 Warning (5) Dynamic Range Window violation 
2019-06-27, 14:08:02 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 14:08:02 Warning (5) Dynamic Range Window violation 
2019-06-27, 14:08:02 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
Observer

Re: Frequent Modem Reboots. Several Modems.

Internet cut out again. This will be the last set of logging information ill post unless someone requests something specific. Hopefully, I have provided enough for someone to point me in the right direction. I appreciate anyone who has taken the time. 

 

==Downstream Bonded Channels==
1 Locked  QAM256 32 807000000 Hz -1.9 dBmV 39.8 dB 2912172828 145 362 
2 Locked  QAM256 1  627000000 Hz  0.6 dBmV 41.6 dB 2898103894 255 304 
3 Locked  QAM256 2  633000000 Hz  1.0 dBmV 41.6 dB 2898132354 207 285 
4 Locked  QAM256 3  639000000 Hz  0.3 dBmV 41.4 dB 2898160408 199 340 
5 Locked  QAM256 4  645000000 Hz  1.4 dBmV 41.7 dB 2898192183 240 314 
6 Locked  QAM256 5  651000000 Hz  1.3 dBmV 41.7 dB 2898218616 213 300 
7 Locked  QAM256 6  657000000 Hz  1.2 dBmV 41.7 dB 2898241010 207 213 
8 Locked  QAM256 7  663000000 Hz  1.9 dBmV 41.6 dB 2898266938 150 260 
9 Locked  QAM256 8  669000000 Hz  1.3 dBmV 41.5 dB 2898300332 213 204 
10 Locked QAM256 9  675000000 Hz  1.1 dBmV 41.2 dB 2898332029 220 197 
11 Locked QAM256 10 681000000 Hz  1.0 dBmV 40.9 dB 2901099547 174 258 
12 Locked QAM256 11 687000000 Hz  0.2 dBmV 40.8 dB 2901129873 146 223 
13 Locked QAM256 12 693000000 Hz  0.3 dBmV 40.8 dB 2901154006 131 218 
14 Locked QAM256 13 699000000 Hz  0.1 dBmV 40.8 dB 2901183361 141 229 
15 Locked QAM256 14 705000000 Hz -0.5 dBmV 40.6 dB 2901208990 133 221 
16 Locked QAM256 15 711000000 Hz  0.4 dBmV 40.8 dB 2901236716 132 172 
17 Locked QAM256 16 717000000 Hz  0.2 dBmV 40.5 dB 2901269845 146 167 
18 Locked QAM256 17 723000000 Hz  0.2 dBmV 40.8 dB 2901296060 135 185 
19 Locked QAM256 18 729000000 Hz  0.3 dBmV 40.7 dB 2901325981 108 181 
20 Locked QAM256 19 735000000 Hz -0.5 dBmV 40.5 dB 2901351907 144 156 
21 Locked QAM256 20 741000000 Hz -0.3 dBmV 40.5 dB 2902253789 124 143 
22 Locked QAM256 21 747000000 Hz -0.1 dBmV 40.3 dB 2902283754 109 187 
23 Locked QAM256 22 753000000 Hz -1.2 dBmV 39.9 dB 2902313054 133 159 
24 Locked QAM256 23 759000000 Hz -1.2 dBmV 40.0 dB 2902338428 121 178 
25 Locked QAM256 24 765000000 Hz -1.5 dBmV 39.9 dB 2902371057 120 160 
26 Locked QAM256 25 771000000 Hz -2.2 dBmV 39.6 dB 2902400356 134 166 
27 Locked QAM256 26 777000000 Hz -1.2 dBmV 40.0 dB 2902394834 101 141 
28 Locked QAM256 27 783000000 Hz -2.1 dBmV 39.8 dB 2902373353 111 136 
29 Locked QAM256 28 789000000 Hz -1.9 dBmV 40.1 dB 2902369391 76 173 
30 Locked QAM256 30 795000000 Hz -0.7 dBmV 40.2 dB 2901996516 90 164 
31 Locked QAM256 31 801000000 Hz -2.8 dBmV 39.8 dB 2902435552 74 146 
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 

==Upstream Bonded Channels==
1 Locked TDMA  49 19400000 Hz 36.3 dBmV 
2 Locked ATDMA 50 24200000 Hz 38.3 dBmV 
3 Locked ATDMA 51 30600000 Hz 40.3 dBmV 
4 Locked ATDMA 52 37000000 Hz 41.3 dBmV 
5 Not Locked Unknown 0 0 Hz 0.0 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 

==Downstream OFDM Channels==
1 Locked 0, 1, 2, 255 29 338000000 Hz 0.3 dBmV 41.0 dB 1108 ~ 2987 2353788564 2246105772 1178 
2 Not Locked 0, 255 0 0 Hz -0.4 dBmV 0.0 dB 0 ~ 4095 0 0 0 

==Upstream OFDMA Channels==
1 Not Locked Unknown 0 0 Hz 0 dBmV 
2 Not Locked Unknown 0 0 Hz 0 dBmV 


==Event Log==
2019-06-27, 19:15:29 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:28 Notice (6) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:28 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:28 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:28 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:22 Notice (6) Honoring MDD; IP provisioning mode = IPv4 
2019-06-27, 19:15:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:06 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:01 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:15:00 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 19:14:12 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:41 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Notice (6) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:40 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:34 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:14:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:38 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:35 Notice (6) Honoring MDD; IP provisioning mode = IPv4 
2019-06-27, 16:13:22 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:07 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:06 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:13:02 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:10 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:10 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:09 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 
2019-06-27, 16:12:09 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:a5:6f:48;CMTS-MAC=00:01:5c:9b:5c:64;CM-QOS=1.1;CM-VER=3.1; 
2019-06-27, 16:12:09 Warning (5) Dynamic Range Window violation 

Sharer

Re: Frequent Modem Reboots. Several Modems.

Upstream levels are all over the map.

The fact they are dipping down into the 30's on the fresh reboot looks like there is amplification/attenuation in play somewhere, and either the device (s) tuning is off-kilter, or a device is in trouble (possibly a failing power supply, or internal components that also manage power like capacitors have degraded too far).

Techs need to come on-site for a proper inspection. Keeping logs like this on hand will help demonstrate the need.
Helper

Re: Frequent Modem Reboots. Several Modems.

These kinds of problems almost never originate from a faulty modem, as you can see from your multiple modems with the same problems.  Sadly, many techs will not do their due diligence when they see a customer owned modem in place and just chalk up the problems to that. At some point it may be to your advantage to, temporarily, use a Spectrum supplied modem until the real cause can be fixed.

Proven Sharer

Re: Frequent Modem Reboots. Several Modems.

Isn't the CM1000 modem one that used either Puma6 or 7 chipsets, which had severe issues running at Gigabit speeds??  Spectrum provides their modem for Gigabit service, with the fee included in the monthly charge.  There are NO Gigabit modems listed by Spectrum on this web site as supported for customer purchase and install. 

 

There's also a separate issue lurking in the background: this user is hosting (multiple gaming) servers intended for public access and use, which is a violation of Spectrum's Terms and Conditions of Service for a residential account.  If it affects other users ability to receive the programming or internet services they are paying for, he may be told to either remove the offending equipment or switch to Business Class service. 

Helper

Re: Frequent Modem Reboots. Several Modems.


@karlbeckman wrote:

Isn't the CM1000 modem one that used either Puma6 or 7 chipsets, which had severe issues running at Gigabit speeds??  ...  There are NO Gigabit modems listed by Spectrum on this web site as supported for customer purchase and install. 

...

 

The Netgear CM1000 uses a Broadcom chipset. The CM700 uses Puma6.  I would also clarify that there are 3 gigabit modems approved for customer purchase and use, just not approved for the gigabit tier. They are all currently on the minimally approved list but most people have been successful getting them set up on Ultra. 

Proven Sharer

Re: Frequent Modem Reboots. Several Modems.

Sorry, I should have been more specific.  You are right about the chipset type, it just doesn't work at Gigabit speeds on Spectrum's network.  There are no internet modems evaluated and approved by Spectrum for customer purchase and installation operating on the Gigabit service tier. 

Use the modem that Spectrum provides, which is already included in the price you are paying for Gigabit service (it's actually 940 Mbps).  They won't credit you back if you try to use your own box instead.  If theirs doesn't perform they can't blame you or your equipment.  They must either make it work or credit your account for the service charges.