Community Forum

Modem goes offline a multiple times a day

New Poster

Modem goes offline a multiple times a day

I have examined the event logs on my Netgear CM600 and noticed that the "No Ranging Response received - T3 time-out..." message is displayed whenever my internet goes offlien. This problem happened about 3 years ago and Comcast technician had to come out and replace the cable line coming into my home. My interenet is going offline at least 2 or 3 times a day if not more.

Expert

Re: Modem goes offline a multiple times a day

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 post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.

What is the exact make and model number of the modem ?




I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: Modem goes offline a multiple times a day

My modem is the Netgear CM600 Modem. I have posted the upstream, downstream and SNR infor below. Thank you!

 

requency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 597000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 13 597000000 Hz 2.2 dBmV 38.1 dB 1 0
2 Locked QAM256 33 495000000 Hz 2.4 dBmV 38.6 dB 0 0
3 Locked QAM256 34 507000000 Hz 2.5 dBmV 36.4 dB 0 0
4 Locked QAM256 35 513000000 Hz 2.4 dBmV 38.8 dB 0 0
5 Locked QAM256 36 519000000 Hz 2.4 dBmV 38.7 dB 0 0
6 Locked QAM256 1 525000000 Hz 2.5 dBmV 38.7 dB 0 0
7 Locked QAM256 2 531000000 Hz 2.2 dBmV 38.5 dB 0 0
8 Locked QAM256 3 537000000 Hz 2.3 dBmV 38.5 dB 0 0
9 Locked QAM256 4 543000000 Hz 2.5 dBmV 38.5 dB 0 0
10 Locked QAM256 5 549000000 Hz 2.5 dBmV 38.5 dB 0 0
11 Locked QAM256 6 555000000 Hz 2.4 dBmV 38.4 dB 0 0
12 Locked QAM256 7 561000000 Hz 2.4 dBmV 38.3 dB 0 0
13 Locked QAM256 8 567000000 Hz 2.4 dBmV 38.4 dB 0 0
14 Locked QAM256 9 573000000 Hz 2.3 dBmV 38.3 dB 0 0
15 Locked QAM256 10 579000000 Hz 2.4 dBmV 38.3 dB 0 0
16 Locked QAM256 11 585000000 Hz 2.4 dBmV 38.3 dB 1 0
17 Locked QAM256 12 591000000 Hz 1.8 dBmV 38.2 dB 0 0
18 Locked QAM256 14 603000000 Hz 2.0 dBmV 38.2 dB 0 0
19 Locked QAM256 15 609000000 Hz 1.9 dBmV 38.2 dB 0 0
20 Locked QAM256 16 615000000 Hz 2.1 dBmV 38.4 dB 0 0
21 Locked QAM256 17 621000000 Hz 2.2 dBmV 38.3 dB 0 0
22 Locked QAM256 18 627000000 Hz 2.0 dBmV 38.2 dB 0 0
23 Locked QAM256 19 633000000 Hz 2.4 dBmV 38.2 dB 0 0
24 Locked QAM256 20 639000000 Hz 2.3 dBmV 38.2 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 41.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 40.5 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 41.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 41.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 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Current System Time: Wed Sep 18 12:11:26 2019
System Up Time: 2:49:31
Expert

Re: Modem goes offline a multiple times a day

Looks good. Is there a router / WiFi in the equation here ? If so, does the problem still happen with a direct connection to the CM600 ?



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: Modem goes offline a multiple times a day

I do have my own WiFi / Router setup and as far as I can tell it is working correctly. I will try using a direct connection to confirm.  However,  the timeout messages in the modem's event log do correspond to when the internet is offline.

 

 

Time

Priority

Description

2019-09-18, 11:58:29

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 10:23:12

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

2019-09-18, 10:23:03

Critical (3)

No Ranging Response received - T3 time-out;

2019-09-18, 10:22:53

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2019-09-18, 10:18:33

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 10:15:10

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

2019-09-18, 10:14:58

Critical (3)

No Ranging Response received - T3 time-out;

2019-09-18, 10:14:47

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2019-09-18, 10:10:37

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 10:10:37

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;

2019-09-18, 10:10:37

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 0;

2019-09-18, 09:30:22

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

2019-09-18, 09:30:13

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2019-09-18, 09:30:13

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:88:14:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2019-09-18, 09:25:51

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 09:20:17

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 09:20:17

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;

2019-09-18, 09:20:17

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;

2019-09-18, 04:43:34

Critical (3)

No Ranging Response received - T3 time-out;

2019-09-18, 04:43:22

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2019-09-18, 04:39:02

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 04:38:50

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 04:38:50

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;

2019-09-18, 04:38:50

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 0;

2019-09-18, 03:43:12

Critical (3)

No Ranging Response received - T3 time-out;

2019-09-18, 03:43:04

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;

2019-09-18, 03:38:44

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 03:38:39

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-18, 03:38:39

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;

2019-09-18, 03:38:39

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 0;

2019-09-17, 11:10:18

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-17, 11:10:08

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;

2019-09-17, 11:10:07

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;

2019-09-17, 11:10:02

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;

2019-09-17, 11:09:28

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-16, 18:19:04

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;

2019-09-16, 18:18:57

Critical (3)

No Ranging Response received - T3 time-out;

2019-09-16, 18:18:48

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;