T4 / T3 errors on a C7800, is there a fix for this or should cox send out a Tech?

Question

C7800

2018-10-27, 11:04:16
Notice (6)
TLV-11 - unrecognized OID;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Warning (5)
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Notice (6)
Honoring MDD; IP provisioning mode = IPv4

Time Not Established
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

Time Not Established
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2018-10-23, 14:06:10
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-23, 14:05:54
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-23, 14:05:54
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-23, 14:03:38
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:06:50
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:06:14
Critical (3)
REG RSP not received;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:43
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:29
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:26
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:24
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:14
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:11
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:06
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:05:04
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:04:54
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:04:51
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:04:34
Critical (3)
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 14:04:31
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 13:06:37
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 12:38:48
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-14, 12:38:46
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

2018-10-13, 11:49:58
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;

becky · Answer

Hi rm_72, your modem metrics are slightly outside of our preferred specifications. Are there any splitters on the coax connection to the modem? It's possible the splitter needs to be replaced. If there are no splitters and you've ensured that the coax connection to the modem is finger-tight, I'd suggest we schedule a service call so an on-site technician can resolve this for you. -Becky, Cox Support Forums Moderator

Forum Discussion

T4 / T3 errors on a C7800, is there a fix for this or should cox send out a Tech?

Related Content

Heartbeat error 503

403.201 error.

Netgear Nighthawk c7800

Email and error loading page.

Netgear C7800 Firmware

Recent Discussions

Casa Grande, AZ Full Day Drops

Cox is absolute garbage!

Continuously having intermittent internet outage/sluggish issues

Poor Service, can't talk to a human

Betty Grant

2018-10-27, 11:04:16	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2018-10-23, 14:06:10	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-23, 14:05:54	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-23, 14:05:54	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-23, 14:03:38	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:06:50	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:06:14	Critical (3)	REG RSP not received;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:43	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:29	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:26	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:24	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:14	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:11	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:06	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:05:04	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:04:54	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:04:51	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:04:34	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 14:04:31	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 13:06:37	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 12:38:48	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-14, 12:38:46	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;
2018-10-13, 11:49:58	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:25:2f:70;CMTS-MAC=00:27:90:0c:70:f0;CM-QOS=1.1;CM-VER=3.1;