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
•
Modem Self Reboots Throughout the Day
I just got a new modem (Neatgear C6300BD) one day ago for the same issue. The WiFi will cut out randomly throughout the day and take 15 seconds to reboot. The new modem was hopefully going to fix the issue, however the rebooting is still happening. This is the log:
| Time | Priority | Description |
| 2016-12-23, 17:38:53.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 17:38:10.0 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 16:05:40.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 15:46:17.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 09:56:36.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 09:28:29.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 09:18:30.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 08:56:01.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 08:36:24.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 06:57:36.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 05:49:07.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
| 2016-12-23, 05:09:37.0 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:83:3e:20;CMTS-MAC=60:73:5c:72:93:9d;CM-QOS=1.1;CM-VER=3.0; |
A lot of them are T4's, which means nothing to me, but they are there. Can someone please help me resolve this? Spotty WiFi isn't what I pay for. Thanks!
PolarisX
New Contributor
•
I had the same issue ever since the firmware upgraded to V2.05.12 What I did was backed up all my settings and factory reset the unit and have had no issues all day.
The Cox C6300BD is a redhead stepchild. It doesn't use the Intel Puma chipset like the other C6300BD but a Broadcom solution. What that means is sometimes the information for the Gateway Max, ect isn't accurate for our units.
0
0
AllenP
+4 more
Valued Contributor
•
frogs2, you show a lot of T4 errors, that indicates a problem with the cable or connection. Do you have any splitters in the line you can bypass? Make sure all cable connections are tight and secure.
0
0