Skip to main content

    Support

    Offers

Topper3's profile
Topper3
1st Topic

New Poster

 • 

1 Message

Tuesday, May 5th, 2020 4:00 PM

Closed

Intermittent Internet Disconnections

Hi All,

 

I am on an internet only plan, and the internet keeps going out. From what I can tell the cable modem keeps restarting. I've also confirmed there are no splits between the cable modem and the  incoming cable, and checked snugness on the connections. 

 

I dont know if this could be a signal strength issue or a modem compatibility issue.  

 

I've included modem specs, signal status. and error log below. Any help here would be appreciated. 

 

 

 

Cable Modem:

Netgear CM700

 

Signal Status:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 651000000 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 QAM 256 1 459000000 Hz -0.5 dBmV 37.6 dB 165 189
2 Locked QAM 256 2 465000000 Hz -0.7 dBmV 37.6 dB 201 1318
3 Locked QAM 256 3 471000000 Hz -0.7 dBmV 37.3 dB 467 3034
4 Locked QAM 256 4 477000000 Hz -0.5 dBmV 37.3 dB 167 188
5 Locked QAM 256 5 483000000 Hz -0.9 dBmV 37.3 dB 283 2326
6 Locked QAM 256 6 489000000 Hz -0.7 dBmV 37.6 dB 279 2277
7 Locked QAM 256 7 495000000 Hz -1.0 dBmV 37.6 dB 293 215
8 Locked QAM 256 8 507000000 Hz -1.4 dBmV 37.6 dB 220 1317
9 Locked QAM 256 9 513000000 Hz -2.4 dBmV 37.3 dB 202 1172
10 Locked QAM 256 10 519000000 Hz -2.5 dBmV 37.3 dB 181 1272
11 Locked QAM 256 11 525000000 Hz -1.9 dBmV 36.6 dB 419 1069
12 Locked QAM 256 12 531000000 Hz -2.0 dBmV 36.6 dB 878 1793
13 Locked QAM 256 13 543000000 Hz -1.2 dBmV 37.3 dB 191 173
14 Locked QAM 256 14 549000000 Hz -1.2 dBmV 37.3 dB 162 184
15 Locked QAM 256 15 555000000 Hz -1.4 dBmV 37.3 dB 222 1262
16 Locked QAM 256 16 561000000 Hz -1.5 dBmV 37.3 dB 319 2063
17 Locked QAM 256 17 567000000 Hz -1.4 dBmV 37.6 dB 689 739
18 Locked QAM 256 18 573000000 Hz -1.2 dBmV 37.6 dB 169 166
19 Locked QAM 256 19 579000000 Hz -1.0 dBmV 37.6 dB 480 2225
20 Locked QAM 256 20 585000000 Hz -0.5 dBmV 37.6 dB 435 1034
21 Locked QAM 256 21 591000000 Hz -0.2 dBmV 37.3 dB 159 178
22 Locked QAM 256 22 597000000 Hz 0.0 dBmV 37.3 dB 568 769
23 Locked QAM 256 23 603000000 Hz -0.5 dBmV 37.6 dB 246 1268
24 Locked QAM 256 24 609000000 Hz -0.5 dBmV 37.6 dB 197 169
25 Locked QAM 256 25 615000000 Hz -0.5 dBmV 37.3 dB 152 181
26 Locked QAM 256 26 621000000 Hz 0.0 dBmV 37.3 dB 166 175
27 Locked QAM 256 27 627000000 Hz 0.2 dBmV 37.3 dB 169 177
28 Locked QAM 256 28 633000000 Hz 0.7 dBmV 37.3 dB 172 711
29 Locked QAM 256 29 639000000 Hz 0.0 dBmV 37.9 dB 180 192
30 Locked QAM 256 30 645000000 Hz 0.0 dBmV 37.6 dB 190 173
31 Locked QAM 256 31 651000000 Hz 0.0 dBmV 37.6 dB 108 646
32 Locked QAM 256 32 657000000 Hz 0.5 dBmV 37.3 dB 155 727
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 17300000 Hz 48.5 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 23700000 Hz 47.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30100000 Hz 44.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36500000 Hz 42.5 dBmV
5 Locked ATDMA 5 1280 Ksym/sec 41200000 Hz 48.0 dBmV
6 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
Current System Time: Tue May 5 15:04:32 2020
System Up Time: 01:38:06

 

Error Log:

Time Priority Description
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:08:46 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 05:09:06 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 05:09:07 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 05:09:41 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
May 04 2020 09:57:10 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 10:47:00 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 10:47:01 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 10:47:20 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 10:47:21 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 12:51:09 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 12:51:09 Critical (3) No Ranging Response received - T3 time-out
May 04 2020 13:38:25 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 04 2020 13:38:25 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:52:50 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 05 2020 12:52:51 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:53:10 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 05 2020 12:53:11 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:53:47 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 05 2020 12:53:47 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:53:50 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
May 05 2020 12:53:51 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:55:41 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
May 05 2020 12:56:37 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 12:56:53 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
May 05 2020 13:20:49 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 13:27:31 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
May 05 2020 13:37:07 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 13:39:43 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out
May 05 2020 14:48:34 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 14:54:49 Critical (3) Ranging Request Retries exhausted
May 05 2020 14:54:49 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
May 05 2020 14:54:50 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 14:55:09 Critical (3) Ranging Request Retries exhausted
May 05 2020 14:55:09 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
May 05 2020 14:55:29 Critical (3) No Ranging Response received - T3 time-out
May 05 2020 14:55:49 Critical (3) Ranging Request Retries exhausted
May 05 2020 14:55:49 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
May 05 2020 14:56:09 Critical (3) Ranging Request Retries exhausted
May 05 2020 14:56:09 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Question

587

0

0

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

No Responses!
forum icon

New to the Community?

Start Here