What model modem do you have? Do you seen anything critical in the logs from around the time of the disconnects? Signal levels look good to me. A few uncorrectables but that wouldn't cause a disconnect.
ARRIS SB6190. The modem was recently reset.
Event Log:
| Time | Priority | Description |
| Thu Jan 01 00:07:44 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:27:20 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:28:32 2023 | 5 | RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:30:46 2023 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:31:08 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:33:24 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:02:06 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:04:09 1970 | 5 | B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:04:11 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:06:14 1970 | 5 | B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:40:34 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:42 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:55 2023 | 5 | RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:55 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:22:21 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:25:22 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:31:17 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:33:33 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:02:05 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:36:53 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
Arris SB6190. The modem was recently reset. Here is the event log:
| Time | Priority | Description |
| Thu Jan 01 00:07:44 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:27:20 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:28:32 2023 | 5 | RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:30:46 2023 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:31:08 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:33:24 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:02:06 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:04:09 1970 | 5 | B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:04:11 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:06:14 1970 | 5 | B-INIT-RNG Failure - Retries exceeded;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:40:34 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:42 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:55 2023 | 5 | RCS Partial Service;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 13:42:55 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:22:21 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:25:22 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:31:17 2023 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:33:33 2023 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Thu Jan 01 00:02:05 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
| Tue Feb 28 15:36:53 2023 | 6 | TLV-11 - unrecognized OID;CM-MAC=98:f7:81:53:11:75;CMTS-MAC=84:8a:8d:32:ce:43;CM-QOS=1.1;CM-VER=3.0; |
The 3 things I see in the log are T3 and T4 time-outs and the partial service error. Pretty sure that happens when the modem drops a downstream channel. The T3's happen from noise on the upstream. I think you require a technician. Hopefully you get a Cox technician and not a contractor, as they usually aren't paid/trained/etc to handle a ingress issue.
Much thanks for the reply. I have had 3 technicians (all contractors) come out will little success. I will push for a Cox technician. Thanks again.
