Highlighted
Not applicable

Connection keeps dropping

I connected a new wireless router and now my connection keeps dropping.
Sat Apr 27 08:06:33 2019 Notice (6) TLV-11 - unrecognized OID;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 08:06:32 2019 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 08:06:32 2019 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Tftp Init Failed - Reinitialize MAC...
Time Not Established Critical (3) TFTP Request Retries exceeded, CM unable to register
Time Not Established Critical (3) TFTP failed - Request sent - No Response;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 08:04:41 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 08:04:08 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 07:58:32 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 07:57:59 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 07:55:07 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 07:54:35 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 07:52:10 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 07:51:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 07:45:05 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 07:44:32 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Apr 27 04:40:06 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 27 04:39:34 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=78:96:84:e6:ef:70;CMTS-MAC=00:17:10:91:82:13;CM-QOS=1.1;CM-VER=3.0;
6 REPLIES 6
Helper

Re: Connection keeps dropping

Did you reboot everything after connecting the new router? 

Not applicable

Re: Connection keeps dropping

Yes. Everything was has been rebooted. Sometimes the connections will be up for a few hours, other times it will reset 3-4 times an hour. Presently we’ve been streaming constantly for 2 hours with no reset. The wireless router never drops only the modem.
Proven Sharer

Re: Connection keeps dropping

Have you considered reinstalling the previous router, just to show everyone that the old router still does work with the (unchanged) modem? That would also give you a working installation that holds its connection.  Or, if it no longer works continuously, you can check the jumper cable and connectors between the modem and dropline entry. 

Sharer

Re: Connection keeps dropping

How do the signal levels/quality of the modem look?

One somewhat common issue we see here is on the upstream side. Poor quality of signal can cause the modem to keep pushing higher levels up above 48, and if it hits the 50-52 range it triggers a restart.
Not applicable

Re: Connection keeps dropping

Here are current levels and recent event log.  My connection dropped twice while trying to upload these.

Downstream Channels.jpgEventLog.jpgUpstream.jpg

Proven Sharer

Re: Connection keeps dropping

The US and DS levels being reported by the modem's snapshot are both in the acceptable range.  The DS channel assignments don't appear 'normal,' but that could be a programming peculiarity of your local system setup.  Most CMTS nodes would be set up as 01 thru 16 or 09-24 for data speeds up to 300 Mbps, rather than 02-17.