Participant

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

I should have reported back before now but, well, life took over.

 

I had good results for a few days with no T4 Timeout reboots and decent speeds. Then, they started up again along with major slowdowns that require a manual modem reboot.

 

Today has required both a manual reboot and T4 timeout reboot. Plus, the upstream speeds have been horrendous all day. The wife has had problems w/her VPN. 

 

Here are a some of the latest logs and signal pages. These are just a sample, there have been regular modem reboots.

 

Today

Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:313-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:285-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:053-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:245-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 17:06:103-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:586-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:585-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:043-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:035-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:033-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:21:025-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:20:403-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 12:12:385-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;

 

 

 

Aug 9

 

Aug 7

Aug 07 2017 15:08:426-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:08:425-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:473-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:473-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:473-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:473-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:443-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:113-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:113-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:07:103-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:06:383-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:06:383-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:06:373-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:503-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:503-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:473-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:363-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:363-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2017 15:05:353-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;

 

 

Today's DSLReports Speed Tests

 

Is this a Spectrum issue?  If so what do I tell them to increase my chances  getting action?

 

Thanks, Ken

Expert

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

you won't get a vpn to work well on a connection that bad: See if turning off IPv6 helps....

 

Need to see what channels are causing this:

 

DS Partial Service Fallback

 

It's probably broadcast tv ingress, see if you can get a signal page with skipped or high corrected/ uncorrected channels.

 

Participant

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?


MsRaye wrote:

you won't get a vpn to work well on a connection that bad: See if turning off IPv6 helps....

 

Need to see what channels are causing this:


I looked back through all of the signal page captures I have (50+), they go back to Feb. 2017.  I found several w/skipped channels from before I did the cable work (removed splitter, etc.) on July 28 and I'm attaching one of those below along with a more recent one from after 7-28.  If the pre-cable cleanup pages are valid for your troubleshooting let me know and I'll put those up too.

 

 

 

 

 

Note: I have an Excel file with modem log captures from July 17 (390 rows). Perhaps it would be useful? Rather than pasting that many rows how can I share that file with you?

Expert

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

[ Edited ]

looks like local tv ch's 31,34,36,37,39,40 ingress for a start

and per TVfool, you have ch's 31,32,33,39,42 on air there. (There's a little overlap between cable and broadcast channels above ch 14....)

 

Looks like something corroded or loose

 

Participant

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

Just so we're clear, the multi-channel ingress determination is based on the Aug. 7 signal page? If so, no corroded or loose connections on my end. I eliminated all that with the July 28 work. Used wrench on fittings too.

 

Just to be sure, please check my 7-28 posts and look at the pic of box after the work. Do you see anything there that would explain the multi-channel ingress? The TV coax carries an amplified OTA feed to that one line feeding a bedroom TV.  The other unused coax are runs to various rooms w/o TVs so no signal in those.

 

If the box looks good then guess I need to call Spectrum and tell them what???

 

**The wife just yelled at me that her VPN is acting up. Did a DSLReports test, see below. We have 60/5 internet only service.

 

Signal Page

 

Modem log has no entries for today.

Expert

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

US looks pretty bad. What do you get with TWC's speedtest tool?

 

Participant

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

That was yesterday. Speeds are ok today.

 

Still experiencing T4 timeout reboots and DS partial service fallbacks.  Here's log from last 2 days.

 

Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 21:26:483-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 21:26:425-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 21:26:403-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 21:26:193-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 18:27:545-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 16 2017 18:27:545-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:35:466-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:35:465-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:34:533-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:34:533-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:34:523-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:34:523-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:34:513-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:32:563-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:32:563-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 23:32:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
    
    
Aug 15 2017 09:16:276-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:16:275-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:313-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:285-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 09:15:053-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:255-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 15 2017 07:56:245-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=84:61:a0:7e:ab:3a;CMTS-MAC=00:17:10:88:30:8e;CM-QOS=1.1;CM-VER=3.0;

 

Where do we go from here?

Established Sharer

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

[ Edited ]

Ingress on DS18 - something going on there.  Are you sure there is no cross-connection between the OTA and cable internet?

Expert

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

Need to see a tracert to TWC's DNS @ 209.18.47.61  and what the TWC/ spectrum speedtest shows.

something is hoarding bandwidth.

Might be the VPN, don't have enough info, ingress might be causing the VPN to get flakey as well.

You're not getting anywhere close to 60/5 service and need to see what's eating up bandwidth, is something running cloud/sync, onedrive or is the infamous win 10 peer to peer update running?

 

Participant

Re: Frequent Modem Reboots - T4 Timeouts; Modem Bad or Spectrum Problem?

[ Edited ]

karlbeckman wrote:

Ingress on DS18 - something going on there.  Are you sure there is no cross-connection between the OTA and cable internet?



Look back at my July 28 posts for the pic of the spectrum box after I did the cable/splitter cleanup. That is the only location where the OTA signal comes close to the  line feeding the modem.