Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Connection Drops with Netgear cg3000d Gateway
I am having internet connection drops with the wireless devices I have in the home. It happens between 10 to 15 times. a technician has been out and replaced coax, connectors and the splitter that terms into my gateway. I checked the error history on the gateway in this iw what I am seeing. I did see other posts but I was not sure if it was the same conclusion. Perhaps you can help.
|
Time |
Priority |
Description |
|
Sat Jul 13 09:40:19 2013 |
Error (4) |
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jul 11 21:40:22 2013 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 14:06:47 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
|
Thu Jun 27 13:39:51 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:39:50 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:42 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:41 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:27 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:26 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:12 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:38:12 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 13:37:11 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 12:27:22 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 12:25:43 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Thu Jun 27 00:25:52 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Wed Jun 26 14:24:28 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Wed Jun 26 14:24:23 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Wed Jun 26 00:09:14 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 19:58:39 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 18:39:35 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 18:39:20 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 15:37:30 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 15:32:58 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 15:32:02 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 13:39:36 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 12:03:42 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 12:00:55 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Tue Jun 25 11:58:42 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Mon Jun 24 14:12:58 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Mon Jun 24 14:12:06 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Sun Jun 23 18:28:41 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0; |
|
Time Not Established |
Warning (5) |
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.0;CM-VER=3.0; |
KipK
Former Moderator
•
Hmm. The signal levels to the modem look good, and the most recent disconnect or timeout event in the modem log is 6/27, so it's probably not an issue on the cable side and more likely an issue on the wireless side.
Our main focus is the wired side of the connection, but the modem manufacturer provides some tips on improving wireless range.
0
0
Tj
New Contributor
•
Ok, but how do you explain the T4 and T3 timeouts that relate to the comm between the modem and the cmts? In doing some research it looks like it has to time out and re-initialize for some reason. It sounds like this would cause a drop in connection. And on the Sync timing synchronization failure, that appears to be related to upstream and downstream communication issues...maybe physical. These errors are fairly consistent after the T4 timeout error message. how do you explain these types of errors? Or am I not understanding something?
0
0
KipK
Former Moderator
•
Those would have been related to the cable signal, but checking it again today those still have not incremented anytime recently. The last T3, T4, or fail-to-acquire-sync is 6/27. This is the modem log our diagnostic page pulls, which condenses duplicate entries:
Title: Modem Log - 10.36.156.181
Instance: Modem Log - phoenix (68.2.16.18)
Description: Modem Log.
First Occurrence Last Occurrence Severity Count Text
2013-06-25 11:58:58 AM 2013-06-25 12:00:55 AM Critical 9 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 12:01:00 AM 2013-06-25 12:03:42 AM Critical 2 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 01:39:20 PM 2013-06-25 01:39:36 PM Critical 2 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 01:39:46 PM 2013-06-25 03:32:02 PM Critical 6 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 03:32:18 PM 2013-06-25 03:32:58 PM Critical 4 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 03:33:09 PM 2013-06-25 03:37:30 PM Critical 2 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 06:38:50 PM 2013-06-25 06:39:20 PM Critical 3 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 06:39:35 PM 2013-06-25 06:39:35 PM Critical 1 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-25 07:58:34 PM 2013-06-25 07:58:39 PM Critical 6 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-26 00:09:00 AM 2013-06-26 00:09:14 AM Critical 2 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-26 02:24:23 PM 2013-06-26 02:24:23 PM Critical 1 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-26 02:24:28 PM 2013-06-26 02:24:28 PM Critical 1 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 00:25:52 AM 2013-06-27 00:25:52 AM Critical 1 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 12:20:46 AM 2013-06-27 12:25:43 AM Critical 21 Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 12:26:50 AM 2013-06-27 12:27:22 AM Critical 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:37:08 PM 2013-06-27 01:37:11 PM Critical 4 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:37:12 PM 2013-06-27 01:38:12 PM Critical 62 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:12 PM 2013-06-27 01:38:12 PM Critical 1 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:14 PM 2013-06-27 01:38:26 PM Critical 14 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:27 PM 2013-06-27 01:38:27 PM Critical 1 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:27 PM 2013-06-27 01:38:41 PM Critical 15 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:42 PM 2013-06-27 01:38:42 PM Critical 1 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:38:42 PM 2013-06-27 01:39:50 PM Critical 69 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:39:51 PM 2013-06-27 01:39:51 PM Critical 1 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-06-27 01:39:54 PM 2013-06-27 02:06:47 PM Critical 1861 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-01-01 00:00:44 AM 1970-01-01 00:00:44 AM Warning 1 DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.0;CM-VER=3.0;
2013-07-13 12:44:44 AM 2013-07-13 12:44:44 AM Notice 11 TLV-11 - unrecognized OID;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-07-14 00:44:41 AM 2013-07-14 12:44:41 AM Error 2 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-07-14 05:19:53 PM 2013-07-14 05:45:12 PM Warning 56 Admin login authentication fail
2013-07-15 00:44:41 AM 2013-07-15 00:44:41 AM Error 1 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
2013-07-15 08:43:35 AM 2013-07-15 08:48:16 AM Warning 34 Admin login authentication fail
2013-07-15 12:44:41 AM 2013-07-15 12:44:41 AM Error 1 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=28:c6:8e:32:f3:d8;CMTS-MAC=00:14:f1:e8:cf:7e;CM-QOS=1.1;CM-VER=3.0;
Your signal up to the modem is very good and signal-related events seem to have stopped with the service call.
0
0
Tj
New Contributor
•
KipK...as a matter of order, these service events happened after the service call. I reached out to tech support by way of chat and they kept telling me I had to contact the home network support group. So I thought I would check the blogs. The service tech did say that if I am still having issues then it is related to the "junction point" serving my house and others. He said that the conduit supporting the cabling really needs to be cleaned. It was keeping him from replacing cables and connectors on some parts of the assembly. As for today, I have had 2 or 3 connection drops. I have also seen in other cox areas outside of Arizona that there may be issues related to the cox issued netgear gateway. Any truth to that? thanks
0
0