Start a New Discussion

Start a New Discussion

Orbi WiFi 7 RBE973
Reply

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

PickyBiker1
Aspirant
Aspirant
‎2018-06-13 09:31 AM
‎2018-06-13 09:31 AM

Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

I have had this C7000v2 modem/router for a couple months and it frequently disconnect 2g wifi. (not using 5g). Suddenlink has been out to "improve" the signal but it doesn't help. The firmware is V1.02.04. The Netgear website indicated it should be V1.02.06, but neither they, nor Suddenlink will update it. There does not seem to be an option to update it on your own.

I have tried numerous options like rebooting it, checking the connections, making certain there are no splitters on the cable coming in. Restarting al 6 computers that are connected to it. 

 

Short of buying another brand, what are my options?

Message 1 of 8
Labels:
0 Kudos
Reply
DarrenM
Sr. NETGEAR Moderator
Sr. NETGEAR Moderator
‎2018-06-18 03:48 PM
‎2018-06-18 03:48 PM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

Are you able to post your modem power levels and the event log?

 

DarrenM

Message 2 of 8
0 Kudos
Reply
PickyBiker1
Aspirant
Aspirant
‎2018-06-21 04:52 AM
‎2018-06-21 04:52 AM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

I tried to post the data you asked for twice, but It doesn't show up here?????

Message 3 of 8
0 Kudos
Reply
PickyBiker1
Aspirant
Aspirant
‎2018-06-21 04:53 AM
‎2018-06-21 04:53 AM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink


Time Priority Description
2018-6-14, 00:04:55 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-14, 00:05:00 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-14, 00:05:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-14, 00:54:33 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-14, 21:53:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-15, 12:03:04 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-16, 01:15:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-17, 00:03:17 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-17, 13:57:02 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:39:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:39:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:39:44 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:39:45 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:40:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:40:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:40:16 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:40:56 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:41:01 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:41:36 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:41:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:41:51 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:41:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 09:41:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 09:42:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 09:42:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 09:43:43 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:43:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:43:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 09:45:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 10:58:55 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;
2018-6-18, 10:59:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 10:59:48 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:40 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:48 Notice (6) Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:50 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:52 Warning (5) ToD request sent - No Response received;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0;
2018-6-18, 18:16:00 Notice (6) TLV-11 - unrecognized OID;CM-MAC=b0:39:56:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.1;CM-VER=3.0;

Message 4 of 8
0 Kudos
Reply
PickyBiker1
Aspirant
Aspirant
‎2018-06-21 04:54 AM
‎2018-06-21 04:54 AM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

Frequency 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 495000000 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 32 495000000 Hz -4.3 dBmV 38.1 dB 0 0
2 Locked QAM256 17 405000000 Hz -1.9 dBmV 38.9 dB 0 0
3 Locked QAM256 18 411000000 Hz -1.7 dBmV 39 dB 0 0
4 Locked QAM256 19 417000000 Hz -1.8 dBmV 39 dB 0 0
5 Locked QAM256 20 423000000 Hz -1.8 dBmV 38.9 dB 0 0
6 Locked QAM256 21 429000000 Hz -2.1 dBmV 38.8 dB 0 0
7 Locked QAM256 22 435000000 Hz -2.5 dBmV 38.7 dB 0 0
8 Locked QAM256 23 441000000 Hz -2.7 dBmV 38.6 dB 0 0
9 Locked QAM256 24 447000000 Hz -2.8 dBmV 38.6 dB 0 0
10 Locked QAM256 25 453000000 Hz -2.9 dBmV 38.6 dB 0 0
11 Locked QAM256 26 459000000 Hz -3 dBmV 38.5 dB 0 0
12 Locked QAM256 27 465000000 Hz -3.3 dBmV 38.3 dB 0 0
13 Locked QAM256 28 471000000 Hz -3.6 dBmV 38.4 dB 0 0
14 Locked QAM256 29 477000000 Hz -3.6 dBmV 38.5 dB 0 0
15 Locked QAM256 30 483000000 Hz -3.7 dBmV 38.4 dB 0 0
16 Locked QAM256 31 489000000 Hz -4.1 dBmV 38.3 dB 0 0
17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

 

Message 5 of 8
0 Kudos
Reply
DarrenM
Sr. NETGEAR Moderator
Sr. NETGEAR Moderator
‎2018-06-25 02:27 PM
‎2018-06-25 02:27 PM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

I am seeing some T3 timeouts which typically indicates issues on the cable lines that a tech would have to come look at. are you seeing a lot of uncorrectables on the power level page?

 

DarrenM

Message 6 of 8
0 Kudos
Reply
PickyBiker1
Aspirant
Aspirant
‎2018-06-26 05:23 AM
‎2018-06-26 05:23 AM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

I'm not certain where the power level page is. i took the advice of someone who though 52 dbvm was on the high end so I bought this device and installed it. The upstream power level is now at about 38 instead of 52.  So I will try this for a while and see what happens.

https://www.amazon.com/Motorola-Signal-Booster-1-Port-Amplifier/dp/B003T2RY7I/ref=cm_cr_arp_d_produc...

 

Message 7 of 8
0 Kudos
Reply
PickyBiker1
Aspirant
Aspirant
‎2018-07-05 02:51 PM
‎2018-07-05 02:51 PM

Re: Frequent disconnects C7000v2, FW V1.02.04, on Suddenlink

Well, so far so good.  Only had one disconnect in the last few days.

@PickyBiker1 wrote:

I'm not certain where the power level page is. i took the advice of someone who though 52 dbvm was on the high end so I bought this device and installed it. The upstream power level is now at about 38 instead of 52.  So I will try this for a while and see what happens.

https://www.amazon.com/Motorola-Signal-Booster-1-Port-Amplifier/dp/B003T2RY7I/ref=cm_cr_arp_d_produc...

 

 

Message 8 of 8
0 Kudos
Reply
Discussion stats
  • 7 replies
  • ‎2018-06-13 09:31 AM
  • 3931 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7